System Message Guide for Cisco IOS XE Cupertino 17.7.x
Cisco System Messages Overview
This document describes system messages for Cisco software releases. During operation, the system software sends these messages to the console (and, optionally, to a logging server on another system) during operation. Not all system messages indicate problems with your system. Some are purely informational, and others may help diagnose problems with communications lines, internal hardware, or the system software.
How To Read System Error Messages
System error messages begin with a percent sign (%) and are structured as follows:%FACILITY-SUBFACILITY-SEVERITY-MNEMONIC: Message-text
-
FACILITY is a code consisting of two or more uppercase letters that indicate the facility to which the message refers. A facility can be a hardware device, a protocol, or a module of the system software.
-
SEVERITY is a single-digit code from 0 to 7 that reflects the severity of the condition. The lower the number, the more serious the situation. Table 1 lists the severity levels.
-
MNEMONIC is a code that uniquely identifies the error message.
-
Message-text is a text string describing the condition. This portion of the message sometimes contains detailed information about the event, including terminal port numbers, network addresses, or addresses that correspond to locations in the system memory address space. Because the information in these variable fields changes from message to message, it is represented here by short strings enclosed in square brackets (
[ ]). A decimal number, for example, is represented as[dec]. Table 2 lists the representations of variable fields and the type of information in them.
The following is a sample system error message:
%LINK-2-BADVCALL: Interface [chars], undefined entry point
Some error messages also indicate the card and slot reporting the error. These error messages begin with a percent sign (%) and are structured as follows:
%CARD-SEVERITY-MSG:SLOT %FACILITY-SEVERITY-MNEMONIC: Message-text
-
CARD is a code that describes the type of card reporting the error. VIP and FEIP are possible card types.
-
MSG is a mnemonic that indicates that this is a message. It is always shown as MSG.
-
SLOT indicates the slot number of the card reporting the error. It is shown as SLOT followed by a number (for example, SLOT5).
The prepended portion of the error message (%CARD-SEVERITY-MSG:SLOT) is not shown in the error message listings in this document.
Error Message Severity Levels
Error message severity levels correspond to the keywords assigned by the logging global configuration commands that define where and at what level these messages appear. The default is to log messages to the console at the debugging level (7). For more information, see the system configuration chapter and descriptions of the logging command in the configuration guide and command reference.
|
Level |
Description |
|---|---|
|
0 - emergency |
System unusable |
|
1 - alert |
Immediate action needed |
|
2 - critical |
Critical condition |
|
3 - error |
Error condition |
|
4 - warning |
Warning condition |
|
5 - notification |
Normal, but significant, condition |
|
6 - informational |
Informational message only |
|
7 - debugging |
Appears during debugging only |
Representation of Variable Fields in Error Messages
|
Representation |
Type of Information |
|---|---|
|
[atalk_address] |
AppleTalk address |
|
[atalk_net] |
AppleTalk network, either 600 or 600-601 |
|
[char] |
Single character |
|
[chars] |
Character string |
|
[dec] |
Decimal number |
|
[enet] |
Ethernet address (for example, 0000.FEED.00C0) |
|
[hex] |
Hexadecimal number |
|
[inet] |
Internet address (for example, 10.0.2.16) |
|
[int] |
Integer number |
|
[node] |
Address or node name |
|
[sci_notation] |
Scientific notation |
|
[t-line] |
Terminal line number in octal (or decimal if the decimal-TTY service is enabled) |
|
[v-name] |
VINES name; or number (hex or decimal) |
Error Message Traceback Reports
Some messages describe internal errors and contain traceback information. This information is very important and should be included when you report a problem to your technical support representative.
The following sample message includes traceback information:
-Process= "Exec", level= 0, pid= 17 -Traceback= 1A82 1AB4 6378 A072 1054 1860
System and Error Messages in Cisco IOS XE Cupertino 17.7.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 |
|
PAGP_DUAL_ACTIVE-4-NO_CHNL_GROUP |
4-Warning |
Port [chars] channel group not present while [chars] |
Extraction of the channel group from a link has failed but is expected to be present. This should not occur and may affect functionality depending on where it occurred. |
cat6k-vs-infra |
"This message should not be seen under normal operation. " "If it is appearing it is an indication of a software bug. " "Enter the commands:\n" "<CMDBOLD>show switch virtual dual-active summary<NOCMDBOLD>\n" "<CMDBOLD>show switch virtual dual-active pagp<NOCMDBOLD>\n" "Retrieve the PAgP packet contents by entering the commands:\n " "<CMDBOLD>debug condition interface <INTFC><NOCMDBOLD>\n" "<CMDBOLD>debug pagp packet<NOCMDBOLD>\n" "and " LOG_STD_SH_TECH_ACTION |
|
_NEW_APP_NAME_-3-MSG_ERR |
3-Error |
[chars] |
Error Messages |
pagent |
"try debug command" |
|
_NEW_APP_NAME_-6-MSG_INF |
6-Information |
[chars] |
Program information |
- |
- |
|
_NEW_APP_NAME_-7-MSG_DBG |
7-Debug |
[chars] |
Debug Messages |
- |
- |
|
AAA_CACHE-3-NULL_TREE_PERIODIC_PROC |
3-Error |
Cache Tree pointer is of null value |
The cache tree pointer is of null value. |
aaa |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
AAA-2-AAAMULTILINKERROR |
2-Critical |
[chars]%08X: Acct db for Id %08X absent |
AAA internal error |
aaa |
LOG_STD_ACTION |
|
AAA-2-AAAMULTILINKERROR |
2-Critical |
[chars]%08X: Acct db for Id %08X absent |
AAA internal error |
aaa |
LOG_STD_ACTION |
|
AAA-2-AAAMULTILINKERROR |
2-Critical |
[chars]%08X: Acct db for Id %08X absent |
AAA internal error |
aaa |
LOG_STD_ACTION |
|
AAA-2-FORKFAIL |
2-Critical |
Cannot fork process [chars] |
Attempted to fork a process and failed. The reason could be either hardware or software. |
aaa |
LOG_STD_ACTION |
|
AAA-2-FORKFAIL |
2-Critical |
Cannot fork process [chars] |
Attempted to fork a process and failed. The reason could be either hardware or software. |
aaa |
LOG_STD_ACTION |
|
AAA-2-FORKFAIL |
2-Critical |
Cannot fork process [chars] |
Attempted to fork a process and failed. The reason could be either hardware or software. |
aaa |
LOG_STD_ACTION |
|
AAA-3-ACCT_IOMEM_LOW |
3-Error |
AAA ACCT process suspended : low I/O memory |
AAA ACCT process has been suspended due to insufficient IO memory. |
aaa |
LOG_STD_ACTION |
|
AAA-3-ACCT_IOMEM_LOW |
3-Error |
AAA ACCT process suspended : low I/O memory |
AAA ACCT process has been suspended due to insufficient IO memory. |
aaa |
LOG_STD_ACTION |
|
AAA-3-ACCT_IOMEM_LOW |
3-Error |
AAA ACCT process suspended : low I/O memory |
AAA ACCT process has been suspended due to insufficient IO memory. |
aaa |
LOG_STD_ACTION |
|
AAA-3-ACCT_LOW_IO_MEM_TRASH |
3-Error |
AAA unable to handle accounting requests due to insufficient I/O memory and could be trashing the queued accounting records |
Dropping the accounting request as there is no enough I/O memory. Hence all queued accounting requests shall be trashed |
aaa |
LOG_STD_ACTION |
|
AAA-3-ACCT_LOW_IO_MEM_TRASH |
3-Error |
AAA unable to handle accounting requests due to insufficient I/O memory and could be trashing the queued accounting records |
Dropping the accounting request as there is no enough I/O memory. Hence all queued accounting requests shall be trashed |
aaa |
LOG_STD_ACTION |
|
AAA-3-ACCT_LOW_IO_MEM_TRASH |
3-Error |
AAA unable to handle accounting requests due to insufficient I/O memory and could be trashing the queued accounting records |
Dropping the accounting request as there is no enough I/O memory. Hence all queued accounting requests shall be trashed |
aaa |
LOG_STD_ACTION |
|
AAA-3-ACCT_LOW_MEM_UID_FAIL |
3-Error |
AAA unable to create UID for incoming calls due to insufficient processor memory |
Stop creating the AAA UID due to LOW processor memory |
aaa |
LOG_STD_ACTION |
|
AAA-3-ACCT_LOW_MEM_UID_FAIL |
3-Error |
AAA unable to create UID for incoming calls due to insufficient processor memory |
Stop creating the AAA UID due to LOW processor memory |
aaa |
LOG_STD_ACTION |
|
AAA-3-ACCT_LOW_MEM_UID_FAIL |
3-Error |
AAA unable to create UID for incoming calls due to insufficient processor memory |
Stop creating the AAA UID due to LOW processor memory |
aaa |
LOG_STD_ACTION |
|
AAA-3-ACCT_LOW_PROC_MEM_TRASH |
3-Error |
AAA unable to handle accounting requests due to insufficient processor memory and could be trashing the queued accounting records |
Dropping the accounting request as there is no enough processor memory. Hence all queued accounting requests shall be trashed |
aaa |
LOG_STD_ACTION |
|
AAA-3-ACCT_LOW_PROC_MEM_TRASH |
3-Error |
AAA unable to handle accounting requests due to insufficient processor memory and could be trashing the queued accounting records |
Dropping the accounting request as there is no enough processor memory. Hence all queued accounting requests shall be trashed |
aaa |
LOG_STD_ACTION |
|
AAA-3-ACCT_LOW_PROC_MEM_TRASH |
3-Error |
AAA unable to handle accounting requests due to insufficient processor memory and could be trashing the queued accounting records |
Dropping the accounting request as there is no enough processor memory. Hence all queued accounting requests shall be trashed |
aaa |
LOG_STD_ACTION |
|
AAA-3-ACCT_UNKNOWN_REASON_TRASH |
3-Error |
AAA unable to handle accounting requests reason unknown and could be trashing the queued accounting records |
Dropping the accounting request reason unknown. Hence all queued accounting requests shall be trashed |
aaa |
LOG_STD_ACTION |
|
AAA-3-ACCT_UNKNOWN_REASON_TRASH |
3-Error |
AAA unable to handle accounting requests reason unknown and could be trashing the queued accounting records |
Dropping the accounting request reason unknown. Hence all queued accounting requests shall be trashed |
aaa |
LOG_STD_ACTION |
|
AAA-3-ACCT_UNKNOWN_REASON_TRASH |
3-Error |
AAA unable to handle accounting requests reason unknown and could be trashing the queued accounting records |
Dropping the accounting request reason unknown. Hence all queued accounting requests shall be trashed |
aaa |
LOG_STD_ACTION |
|
AAA-3-ATTRFORMATERR |
3-Error |
Attribute with unknown format [dec] |
An attribute was found with an invalid format. |
aaa |
"Attribute with unknown format in definition. Enable AAA " "debug and try to replicate the steps to get the message. " "If the meassage appears again Check bug toolkit " "on Cisco website for the issue. If you didn't find one " "Enter <CmdBold>Show tech-support<NoCmdBold> command " "Collect all the information and error message and report " "it to your technical support representative." |
|
AAA-3-ATTRFORMATERR |
3-Error |
Attribute with unknown format [dec] |
An attribute was found with an invalid format. |
aaa |
"Attribute with unknown format in definition. Enable AAA " "debug and try to replicate the steps to get the message. " "If the meassage appears again Check bug toolkit " "on Cisco website for the issue. If you didn't find one " "Enter <CmdBold>Show tech-support<NoCmdBold> command " "Collect all the information and error message and report " "it to your technical support representative." |
|
AAA-3-ATTRFORMATERR |
3-Error |
Attribute with unknown format [dec] |
An attribute was found with an invalid format. |
aaa |
"Attribute with unknown format in definition. Enable AAA " "debug and try to replicate the steps to get the message. " "If the meassage appears again Check bug toolkit " "on Cisco website for the issue. If you didn't find one " "Enter <CmdBold>Show tech-support<NoCmdBold> command " "Collect all the information and error message and report " "it to your technical support representative." |
|
AAA-3-AUTH_LOW_IOMEM |
3-Error |
RADIUS process is unable to handle the requests due to insufficient I/O memory |
RADIUS process unable to handle request due to insufficient IO memory. Hence returning failure. |
aaa |
LOG_STD_ACTION |
|
AAA-3-AUTH_LOW_IOMEM |
3-Error |
RADIUS process is unable to handle the requests due to insufficient I/O memory |
RADIUS process unable to handle request due to insufficient IO memory. Hence returning failure. |
aaa |
LOG_STD_ACTION |
|
AAA-3-AUTH_LOW_IOMEM |
3-Error |
RADIUS process is unable to handle the requests due to insufficient I/O memory |
RADIUS process unable to handle request due to insufficient IO memory. Hence returning failure. |
aaa |
LOG_STD_ACTION |
|
AAA-3-AUTHORMLISTUNDEF |
3-Error |
Authorization method list '[chars]' is not defined. Please define it. |
A given method list was listed in a command without defining it first. The method list should be defined before use. |
aaa |
"Define the method list before using it." |
|
AAA-3-AUTHORMLISTUNDEF |
3-Error |
Authorization method list '[chars]' is not defined. Please define it. |
A given method list was listed in a command without defining it first. The method list should be defined before use. |
aaa |
"Define the method list before using it." |
|
AAA-3-AUTHORMLISTUNDEF |
3-Error |
Authorization method list '[chars]' is not defined. Please define it. |
A given method list was listed in a command without defining it first. The method list should be defined before use. |
aaa |
"Define the method list before using it." |
|
AAA-3-BADCURSOR |
3-Error |
invalid cursor index [dec] max [dec] service [chars] protocol [chars] |
A AAA client has provided an invalid attribute cursor to AAA. |
aaa |
LOG_STD_ACTION |
|
AAA-3-BADCURSOR |
3-Error |
invalid cursor index [dec] max [dec] service [chars] protocol [chars] |
A AAA client has provided an invalid attribute cursor to AAA. |
aaa |
LOG_STD_ACTION |
|
AAA-3-BADCURSOR |
3-Error |
invalid cursor index [dec] max [dec] service [chars] protocol [chars] |
A AAA client has provided an invalid attribute cursor to AAA. |
aaa |
LOG_STD_ACTION |
|
AAA-3-BADLIST |
3-Error |
invalid list AAA ID [dec] |
A AAA client has provided an invalid attribute list to AAA. |
aaa |
LOG_STD_ACTION |
|
AAA-3-BADLIST |
3-Error |
invalid list AAA ID [dec] |
A AAA client has provided an invalid attribute list to AAA. |
aaa |
LOG_STD_ACTION |
|
AAA-3-BADLIST |
3-Error |
invalid list AAA ID [dec] |
A AAA client has provided an invalid attribute list to AAA. |
aaa |
LOG_STD_ACTION |
|
AAA-3-BADMAGIC |
3-Error |
Data structure failed magic number sanity check |
A corrupted data structure has been found which was stored internally. |
aaa |
LOG_STD_ACTION |
|
AAA-3-BADMAGIC |
3-Error |
Data structure failed magic number sanity check |
A corrupted data structure has been found which was stored internally. |
aaa |
LOG_STD_ACTION |
|
AAA-3-BADMAGIC |
3-Error |
Data structure failed magic number sanity check |
A corrupted data structure has been found which was stored internally. |
aaa |
LOG_STD_ACTION |
|
AAA-3-BADMETHOD |
3-Error |
Cannot process [chars] method [dec] |
A method list function encountered a method list that was unknown or could not be handled. |
aaa |
LOG_STD_ACTION |
|
AAA-3-BADMETHOD |
3-Error |
Cannot process [chars] method [dec] |
A method list function encountered a method list that was unknown or could not be handled. |
aaa |
LOG_STD_ACTION |
|
AAA-3-BADMETHOD |
3-Error |
Cannot process [chars] method [dec] |
A method list function encountered a method list that was unknown or could not be handled. |
aaa |
LOG_STD_ACTION |
|
AAA-3-BADMETHODERROR |
3-Error |
Cannot process [chars] method [chars] |
A method list function encountered a method type that was unknown or could not be handled. |
aaa |
LOG_STD_ACTION |
|
AAA-3-BADMETHODERROR |
3-Error |
Cannot process [chars] method [chars] |
A method list function encountered a method type that was unknown or could not be handled. |
aaa |
LOG_STD_ACTION |
|
AAA-3-BADMETHODERROR |
3-Error |
Cannot process [chars] method [chars] |
A method list function encountered a method type that was unknown or could not be handled. |
aaa |
LOG_STD_ACTION |
|
AAA-3-BADSERVERTYPEERROR |
3-Error |
Cannot process [chars] server type [chars] |
A method list function encountered a server type that was unknown or could not be handled. This may be due to a server misconfiguration. |
aaa |
"Research the cause of the misconfiguration and " "attempt to correct it otherwise take the following " "action. "LOG_STD_ACTION |
|
AAA-3-BADSERVERTYPEERROR |
3-Error |
Cannot process [chars] server type [chars] |
A method list function encountered a server type that was unknown or could not be handled. This may be due to a server misconfiguration. |
aaa |
"Research the cause of the misconfiguration and " "attempt to correct it otherwise take the following " "action. "LOG_STD_ACTION |
|
AAA-3-BADSERVERTYPEERROR |
3-Error |
Cannot process [chars] server type [chars] |
A method list function encountered a server type that was unknown or could not be handled. This may be due to a server misconfiguration. |
aaa |
"Research the cause of the misconfiguration and " "attempt to correct it otherwise take the following " "action. "LOG_STD_ACTION |
|
AAA-3-BUFFER_OVERFLOW |
3-Error |
Radius I/O buffer has overflowed |
An unusually large number of RADIUS attributes has caused AAA to overflow its RADIUS I/O buffer. |
aaa |
"This is an internal software error. Check bug toolkit " "on Cisco website for the issue. If you didn't find one " "Enter <CmdBold>Show tech-support<NoCmdBold> command " "Collect all the information and error message and report " "it to your technical support representative." |
|
AAA-3-BUFFER_OVERFLOW |
3-Error |
Radius I/O buffer has overflowed |
An unusually large number of RADIUS attributes has caused AAA to overflow its RADIUS I/O buffer. |
aaa |
"This is an internal software error. Check bug toolkit " "on Cisco website for the issue. If you didn't find one " "Enter <CmdBold>Show tech-support<NoCmdBold> command " "Collect all the information and error message and report " "it to your technical support representative." |
|
AAA-3-BUFFER_OVERFLOW |
3-Error |
Radius I/O buffer has overflowed |
An unusually large number of RADIUS attributes has caused AAA to overflow its RADIUS I/O buffer. |
aaa |
"This is an internal software error. Check bug toolkit " "on Cisco website for the issue. If you didn't find one " "Enter <CmdBold>Show tech-support<NoCmdBold> command " "Collect all the information and error message and report " "it to your technical support representative." |
|
AAA-3-DROPACCTFAIL |
3-Error |
Accounting record dropped send to server failed: [chars] |
An attempt to send an accounting record to a server failed. This happens when device exhaust all its retries and retransmission. The cause for this be the servers may not be operational or the NAS is not configured properly. |
aaa |
"Check the server whether they are " "operational or not. Next check whether " "the device is configured properly. Refer to" "the server configuration section of the " "cisco IOS documentation. Finally check " "that the NAS can communicate with the server. " "If the problem persist Enter <CmdBold>show running-" "config<NoCmdBold> command contact your cisco technical " "support representative and provide all the information " "gathered to the representative." |
|
AAA-3-DROPACCTFAIL |
3-Error |
Accounting record dropped send to server failed: [chars] |
An attempt to send an accounting record to a server failed. This happens when device exhaust all its retries and retransmission. The cause for this be the servers may not be operational or the NAS is not configured properly. |
aaa |
"Check the server whether they are " "operational or not. Next check whether " "the device is configured properly. Refer to" "the server configuration section of the " "cisco IOS documentation. Finally check " "that the NAS can communicate with the server. " "If the problem persist Enter <CmdBold>show running-" "config<NoCmdBold> command contact your cisco technical " "support representative and provide all the information " "gathered to the representative." |
|
AAA-3-DROPACCTFAIL |
3-Error |
Accounting record dropped send to server failed: [chars] |
An attempt to send an accounting record to a server failed. This happens when device exhaust all its retries and retransmission. The cause for this be the servers may not be operational or the NAS is not configured properly. |
aaa |
"Check the server whether they are " "operational or not. Next check whether " "the device is configured properly. Refer to" "the server configuration section of the " "cisco IOS documentation. Finally check " "that the NAS can communicate with the server. " "If the problem persist Enter <CmdBold>show running-" "config<NoCmdBold> command contact your cisco technical " "support representative and provide all the information " "gathered to the representative." |
|
AAA-3-HA_INIT_FAILURE |
3-Error |
High availability initialization failure: [chars] |
The AAA subsystem was unable to perform necessary high-availability related initialization. In the event of switchover to a standby device sessions depending on high availability capabilities in the AAA subsystem will be forced to renegotiate. |
aaa |
LOG_STD_ACTION |
|
AAA-3-HA_INIT_FAILURE |
3-Error |
High availability initialization failure: [chars] |
The AAA subsystem was unable to perform necessary high-availability related initialization. In the event of switchover to a standby device sessions depending on high availability capabilities in the AAA subsystem will be forced to renegotiate. |
aaa |
LOG_STD_ACTION |
|
AAA-3-HA_INIT_FAILURE |
3-Error |
High availability initialization failure: [chars] |
The AAA subsystem was unable to perform necessary high-availability related initialization. In the event of switchover to a standby device sessions depending on high availability capabilities in the AAA subsystem will be forced to renegotiate. |
aaa |
LOG_STD_ACTION |
|
AAA-3-HA_INTERNAL_ERROR |
3-Error |
High availability internal error for unique id 0x%8x: [chars] |
The AAA subsystem was suffered an internal error. In the event of switchover to a standby device sessions depending on high availability capabilities in the AAA subsystem may be forced to renegotiate. |
aaa |
LOG_STD_ACTION |
|
AAA-3-HA_INTERNAL_ERROR |
3-Error |
High availability internal error for unique id 0x%8x: [chars] |
The AAA subsystem was suffered an internal error. In the event of switchover to a standby device sessions depending on high availability capabilities in the AAA subsystem may be forced to renegotiate. |
aaa |
LOG_STD_ACTION |
|
AAA-3-HA_INTERNAL_ERROR |
3-Error |
High availability internal error for unique id 0x%8x: [chars] |
The AAA subsystem was suffered an internal error. In the event of switchover to a standby device sessions depending on high availability capabilities in the AAA subsystem may be forced to renegotiate. |
aaa |
LOG_STD_ACTION |
|
AAA-3-INVALIDATTRLIST |
3-Error |
aaa attribute list CLI is not valid when configuring in sub-mode. |
An internal error has occurred |
aaa |
LOG_STD_ACTION |
|
AAA-3-INVALIDATTRLIST |
3-Error |
aaa attribute list CLI is not valid when configuring in sub-mode. |
An internal error has occurred |
aaa |
LOG_STD_ACTION |
|
AAA-3-INVALIDATTRLIST |
3-Error |
aaa attribute list CLI is not valid when configuring in sub-mode. |
An internal error has occurred |
aaa |
LOG_STD_ACTION |
|
AAA-3-INVALIDPARM |
3-Error |
invalid parameter was used when accessing AAA function |
A AAA client tried to use a AAA function with an invalid parameter. |
aaa |
LOG_STD_ACTION |
|
AAA-3-INVALIDPARM |
3-Error |
invalid parameter was used when accessing AAA function |
A AAA client tried to use a AAA function with an invalid parameter. |
aaa |
LOG_STD_ACTION |
|
AAA-3-INVALIDPARM |
3-Error |
invalid parameter was used when accessing AAA function |
A AAA client tried to use a AAA function with an invalid parameter. |
aaa |
LOG_STD_ACTION |
|
AAA-3-IPILLEGALMSG |
3-Error |
Invalid use of ip_pid[dec] |
This error means a process sent an illegal message. |
- |
"If this message recurs. Check bug toolkit " "on Cisco website for the issue. If you didn't find one " "Enter <CmdBold>Show tech-support<NoCmdBold> command " "Collect all the information and error message and report " "it to your technical support representative." |
|
AAA-3-IPILLEGALMSG |
3-Error |
Invalid use of ip_pid[dec] |
This error means a process sent an illegal message. |
- |
"If this message recurs. Check bug toolkit " "on Cisco website for the issue. If you didn't find one " "Enter <CmdBold>Show tech-support<NoCmdBold> command " "Collect all the information and error message and report " "it to your technical support representative." |
|
AAA-3-IPILLEGALMSG |
3-Error |
Invalid use of ip_pid[dec] |
This error means a process sent an illegal message. |
- |
"If this message recurs. Check bug toolkit " "on Cisco website for the issue. If you didn't find one " "Enter <CmdBold>Show tech-support<NoCmdBold> command " "Collect all the information and error message and report " "it to your technical support representative." |
|
AAA-3-ISDNINTF |
3-Error |
[chars] [chars]: Can not apply configuration to ISDN channel:\n \[chars]\ |
Configuration can not be applied to individual ISDN channels. |
aaa |
"You need virtual-profiles and virtual-access " "interfaces to apply configuration to ISDN. " "Refer to the section on \"Configuring virtual " "profile by AAA Configuration\" in the Cisco IOS " "Dial Technologies Configuration Guide." |
|
AAA-3-ISDNINTF |
3-Error |
[chars] [chars]: Can not apply configuration to ISDN channel:\n \[chars]\ |
Configuration can not be applied to individual ISDN channels. |
aaa |
"You need virtual-profiles and virtual-access " "interfaces to apply configuration to ISDN. " "Refer to the section on \"Configuring virtual " "profile by AAA Configuration\" in the Cisco IOS " "Dial Technologies Configuration Guide." |
|
AAA-3-ISDNINTF |
3-Error |
[chars] [chars]: Can not apply configuration to ISDN channel:\n \[chars]\ |
Configuration can not be applied to individual ISDN channels. |
aaa |
"You need virtual-profiles and virtual-access " "interfaces to apply configuration to ISDN. " "Refer to the section on \"Configuring virtual " "profile by AAA Configuration\" in the Cisco IOS " "Dial Technologies Configuration Guide." |
|
AAA-3-LOW_MEM |
3-Error |
[chars] process is unable to handle the incoming packet due to low memory |
Please check the processor memory or IO memory. Most likely one is them has less available memory or worst case both may have insufficient memory. |
aaa |
LOG_STD_ACTION |
|
AAA-3-LOW_MEM |
3-Error |
[chars] process is unable to handle the incoming packet due to low memory |
Please check the processor memory or IO memory. Most likely one is them has less available memory or worst case both may have insufficient memory. |
aaa |
LOG_STD_ACTION |
|
AAA-3-LOW_MEM |
3-Error |
[chars] process is unable to handle the incoming packet due to low memory |
Please check the processor memory or IO memory. Most likely one is them has less available memory or worst case both may have insufficient memory. |
aaa |
LOG_STD_ACTION |
|
AAA-3-MLIST_INTERNAL_ERROR |
3-Error |
method list '[chars]': [chars] |
This is an internal software error. |
aaa |
LOG_STD_ACTION |
|
AAA-3-MLIST_INTERNAL_ERROR |
3-Error |
method list '[chars]': [chars] |
This is an internal software error. |
aaa |
LOG_STD_ACTION |
|
AAA-3-MLIST_INTERNAL_ERROR |
3-Error |
method list '[chars]': [chars] |
This is an internal software error. |
aaa |
LOG_STD_ACTION |
|
AAA-3-MLIST_TOO_MANY_METHODS |
3-Error |
method list '[chars]' |
This is an internal software error. An AAA client attempted to add too many methods to a method list. |
aaa |
"This is an internal software error. Check bug tool-kit " "on Cisco web-site for the issue. If you didn't find one " "Collect the error message and report it to your " "technical support representative." |
|
AAA-3-MLIST_TOO_MANY_METHODS |
3-Error |
method list '[chars]' |
This is an internal software error. An AAA client attempted to add too many methods to a method list. |
aaa |
"This is an internal software error. Check bug tool-kit " "on Cisco web-site for the issue. If you didn't find one " "Collect the error message and report it to your " "technical support representative." |
|
AAA-3-MLIST_TOO_MANY_METHODS |
3-Error |
method list '[chars]' |
This is an internal software error. An AAA client attempted to add too many methods to a method list. |
aaa |
"This is an internal software error. Check bug tool-kit " "on Cisco web-site for the issue. If you didn't find one " "Collect the error message and report it to your " "technical support representative." |
|
AAA-3-NOTABLE |
3-Error |
AAA ID [dec] |
Resource failure. |
aaa |
LOG_STD_ACTION |
|
AAA-3-NOTABLE |
3-Error |
AAA ID [dec] |
Resource failure. |
aaa |
LOG_STD_ACTION |
|
AAA-3-NOTABLE |
3-Error |
AAA ID [dec] |
Resource failure. |
aaa |
LOG_STD_ACTION |
|
AAA-3-NULLCURSOR |
3-Error |
Null cursor |
A AAA client has provided a nonexistent attribute cursor to AAA. |
aaa |
LOG_STD_ACTION |
|
AAA-3-NULLCURSOR |
3-Error |
Null cursor |
A AAA client has provided a nonexistent attribute cursor to AAA. |
aaa |
LOG_STD_ACTION |
|
AAA-3-NULLCURSOR |
3-Error |
Null cursor |
A AAA client has provided a nonexistent attribute cursor to AAA. |
aaa |
LOG_STD_ACTION |
|
AAA-3-NULLVRF |
3-Error |
Null vrf entry |
A NULL VRF entry found while comparing the AAA VRF attributes. |
aaa |
LOG_STD_ACTION |
|
AAA-3-NULLVRF |
3-Error |
Null vrf entry |
A NULL VRF entry found while comparing the AAA VRF attributes. |
aaa |
LOG_STD_ACTION |
|
AAA-3-NULLVRF |
3-Error |
Null vrf entry |
A NULL VRF entry found while comparing the AAA VRF attributes. |
aaa |
LOG_STD_ACTION |
|
AAA-3-PARSEERR |
3-Error |
Error[dec] parser is unable to parse [chars] per-user command |
All attempts to parse this per_user unconfigure command failed. The unconfigure command is called when an error occurs while configuring per-user commands to revert back. The unconfiguration may fail due to parser or AAA error. |
parser and aaa |
"The given unconfigure command was not executed. " "Switch on the debug peruser command and repeat " "the steps that caused the error. If you get the error " "Report it to your technical support representative." |
|
AAA-3-PARSEERR |
3-Error |
Error[dec] parser is unable to parse [chars] per-user command |
All attempts to parse this per_user unconfigure command failed. The unconfigure command is called when an error occurs while configuring per-user commands to revert back. The unconfiguration may fail due to parser or AAA error. |
parser and aaa |
"The given unconfigure command was not executed. " "Switch on the debug peruser command and repeat " "the steps that caused the error. If you get the error " "Report it to your technical support representative." |
|
AAA-3-PARSEERR |
3-Error |
Error[dec] parser is unable to parse [chars] per-user command |
All attempts to parse this per_user unconfigure command failed. The unconfigure command is called when an error occurs while configuring per-user commands to revert back. The unconfiguration may fail due to parser or AAA error. |
parser and aaa |
"The given unconfigure command was not executed. " "Switch on the debug peruser command and repeat " "the steps that caused the error. If you get the error " "Report it to your technical support representative." |
|
AAA-3-PASSWDRESTRICTERR |
3-Error |
AAA password restriction failed.- [chars]\n |
The password/secret/key entered is not meeting the password restrictions configured |
aaa |
LOG_STD_ACTION |
|
AAA-3-PASSWDRESTRICTERR |
3-Error |
AAA password restriction failed.- [chars]\n |
The password/secret/key entered is not meeting the password restrictions configured |
aaa |
LOG_STD_ACTION |
|
AAA-3-PASSWDRESTRICTERR |
3-Error |
AAA password restriction failed.- [chars]\n |
The password/secret/key entered is not meeting the password restrictions configured |
aaa |
LOG_STD_ACTION |
|
AAA-3-SERVER_INTERNAL_ERROR |
3-Error |
Server '[chars]': [chars] |
This is an internal software error in the AAA server group subsystem. |
aaa |
"This is an internal software error. Check bug toolkit " "on Cisco website for the issue. If you didn't find one " "Enter <CmdBold>Show tech-support<NoCmdBold> command " "Collect all the information and error message and report " "it to your technical support representative." |
|
AAA-3-SERVER_INTERNAL_ERROR |
3-Error |
Server '[chars]': [chars] |
This is an internal software error in the AAA server group subsystem. |
aaa |
"This is an internal software error. Check bug toolkit " "on Cisco website for the issue. If you didn't find one " "Enter <CmdBold>Show tech-support<NoCmdBold> command " "Collect all the information and error message and report " "it to your technical support representative." |
|
AAA-3-SERVER_INTERNAL_ERROR |
3-Error |
Server '[chars]': [chars] |
This is an internal software error in the AAA server group subsystem. |
aaa |
"This is an internal software error. Check bug toolkit " "on Cisco website for the issue. If you didn't find one " "Enter <CmdBold>Show tech-support<NoCmdBold> command " "Collect all the information and error message and report " "it to your technical support representative." |
|
AAA-3-SG_DEADTIME_FORKFAIL |
3-Error |
Failed to fork process for [chars]. |
Quite likely we ran out of memory. Other explanations are possible. |
aaa |
"If this message recurs. Check bug toolkit " "on Cisco website for the issue. If you didn't find " "one Enter <CmdBold>Show tech-support<NoCmdBold> " "command collect all the information and error " "message and report it to your technical support " "representative." |
|
AAA-3-SG_DEADTIME_FORKFAIL |
3-Error |
Failed to fork process for [chars]. |
Quite likely we ran out of memory. Other explanations are possible. |
aaa |
"If this message recurs. Check bug toolkit " "on Cisco website for the issue. If you didn't find " "one Enter <CmdBold>Show tech-support<NoCmdBold> " "command collect all the information and error " "message and report it to your technical support " "representative." |
|
AAA-3-SG_DEADTIME_FORKFAIL |
3-Error |
Failed to fork process for [chars]. |
Quite likely we ran out of memory. Other explanations are possible. |
aaa |
"If this message recurs. Check bug toolkit " "on Cisco website for the issue. If you didn't find " "one Enter <CmdBold>Show tech-support<NoCmdBold> " "command collect all the information and error " "message and report it to your technical support " "representative." |
|
AAA-3-SG_INTERNAL_ERROR |
3-Error |
server group '[chars]': [chars] |
This is an internal software error in the AAA server group subsystem. |
aaa |
"This is an internal software error. Check bug " "toolkit on Cisco website for the issue. If you " "didn't find one Enter <CmdBold>Show tech-support" "<NoCmdBold> command collect all the information " "and error message report it to your technical " "support representative." |
|
AAA-3-SG_INTERNAL_ERROR |
3-Error |
server group '[chars]': [chars] |
This is an internal software error in the AAA server group subsystem. |
aaa |
"This is an internal software error. Check bug " "toolkit on Cisco website for the issue. If you " "didn't find one Enter <CmdBold>Show tech-support" "<NoCmdBold> command collect all the information " "and error message report it to your technical " "support representative." |
|
AAA-3-SG_INTERNAL_ERROR |
3-Error |
server group '[chars]': [chars] |
This is an internal software error in the AAA server group subsystem. |
aaa |
"This is an internal software error. Check bug " "toolkit on Cisco website for the issue. If you " "didn't find one Enter <CmdBold>Show tech-support" "<NoCmdBold> command collect all the information " "and error message report it to your technical " "support representative." |
|
AAA-3-SG_TESTPROC_FORKFAIL |
3-Error |
Failed to fork process for [chars]. |
Quite likely we ran out of memory. Other explanations are possible. |
aaa |
"If this message recurs. Check bug toolkit " "on Cisco website for the issue. If you didn't find one " "Enter <CmdBold>Show tech-support<NoCmdBold> command " "Collect all the information and error message and report " "it to your technical support representative." |
|
AAA-3-SG_TESTPROC_FORKFAIL |
3-Error |
Failed to fork process for [chars]. |
Quite likely we ran out of memory. Other explanations are possible. |
aaa |
"If this message recurs. Check bug toolkit " "on Cisco website for the issue. If you didn't find one " "Enter <CmdBold>Show tech-support<NoCmdBold> command " "Collect all the information and error message and report " "it to your technical support representative." |
|
AAA-3-SG_TESTPROC_FORKFAIL |
3-Error |
Failed to fork process for [chars]. |
Quite likely we ran out of memory. Other explanations are possible. |
aaa |
"If this message recurs. Check bug toolkit " "on Cisco website for the issue. If you didn't find one " "Enter <CmdBold>Show tech-support<NoCmdBold> command " "Collect all the information and error message and report " "it to your technical support representative." |
|
AAA-3-SORTFAIL |
3-Error |
[chars] :Peruser Could not sort the [chars] attributes |
Sorting of the attributes received from AAA server failed. |
aaa |
LOG_STD_ACTION |
|
AAA-3-SORTFAIL |
3-Error |
[chars] :Peruser Could not sort the [chars] attributes |
Sorting of the attributes received from AAA server failed. |
aaa |
LOG_STD_ACTION |
|
AAA-3-SORTFAIL |
3-Error |
[chars] :Peruser Could not sort the [chars] attributes |
Sorting of the attributes received from AAA server failed. |
aaa |
LOG_STD_ACTION |
|
AAA-5-LOCAL_USER_BLOCKED |
5-Notice |
User [chars] blocked for login till [chars] |
User blocked since the number of authentication failures in the watch time exceeded the configured threshold. |
aaa |
LOG_STD_ACTION |
|
AAA-5-USER_LOCKED |
5-Notice |
User [chars] locked out on authentication failure |
User locked out since the number of authentication failures exceeded the configured threshold. |
aaa |
LOG_STD_ACTION |
|
AAA-5-USER_LOCKED |
5-Notice |
User [chars] locked out on authentication failure |
User locked out since the number of authentication failures exceeded the configured threshold. |
aaa |
LOG_STD_ACTION |
|
AAA-5-USER_LOCKED |
5-Notice |
User [chars] locked out on authentication failure |
User locked out since the number of authentication failures exceeded the configured threshold. |
aaa |
LOG_STD_ACTION |
|
AAA-5-USER_RESET |
5-Notice |
User [chars] failed attempts reset by [chars] |
User's number of failed authentication attempts so far has been reset to zero |
aaa |
LOG_STD_ACTION |
|
AAA-5-USER_RESET |
5-Notice |
User [chars] failed attempts reset by [chars] |
User's number of failed authentication attempts so far has been reset to zero |
aaa |
LOG_STD_ACTION |
|
AAA-5-USER_RESET |
5-Notice |
User [chars] failed attempts reset by [chars] |
User's number of failed authentication attempts so far has been reset to zero |
aaa |
LOG_STD_ACTION |
|
AAA-5-USER_UNLOCKED |
5-Notice |
User [chars] unlocked by [chars] |
User unlocked by the system administrator. User is enabled to login to the system. |
aaa |
LOG_STD_ACTION |
|
AAA-5-USER_UNLOCKED |
5-Notice |
User [chars] unlocked by [chars] |
User unlocked by the system administrator. User is enabled to login to the system. |
aaa |
LOG_STD_ACTION |
|
AAA-5-USER_UNLOCKED |
5-Notice |
User [chars] unlocked by [chars] |
User unlocked by the system administrator. User is enabled to login to the system. |
aaa |
LOG_STD_ACTION |
|
AAA-6-ACCTSESSIDWRAP |
6-Information |
Accounting-Session-ID [dec] exceeded max value allowed |
Accounting-Session-ID value exceeded max value allowed. Now it is wrapping. |
aaa |
"This is informational only not an error." |
|
AAA-6-ACCTSESSIDWRAP |
6-Information |
Accounting-Session-ID [dec] exceeded max value allowed |
Accounting-Session-ID value exceeded max value allowed. Now it is wrapping. |
aaa |
"This is informational only not an error." |
|
AAA-6-ACCTSESSIDWRAP |
6-Information |
Accounting-Session-ID [dec] exceeded max value allowed |
Accounting-Session-ID value exceeded max value allowed. Now it is wrapping. |
aaa |
"This is informational only not an error." |
|
AAA-6-BADHDL |
6-Information |
invalid hdl AAA ID [dec] hdl [hec] [chars] |
A AAA client has provided an invalid attribute list handle to AAA. |
aaa |
LOG_STD_ACTION |
|
AAA-6-BADHDL |
6-Information |
invalid hdl AAA ID [dec] hdl [hec] [chars] |
A AAA client has provided an invalid attribute list handle to AAA. |
aaa |
LOG_STD_ACTION |
|
AAA-6-BADHDL |
6-Information |
invalid hdl AAA ID [dec] hdl [hec] [chars] |
A AAA client has provided an invalid attribute list handle to AAA. |
aaa |
LOG_STD_ACTION |
|
AAA-6-INVALIDROUTE |
6-Information |
Syntax error in route statement: [chars] |
Currently downloading route contains syntax error. |
aaa |
LOG_STD_ACTION |
|
AAA-6-INVALIDROUTE |
6-Information |
Syntax error in route statement: [chars] |
Currently downloading route contains syntax error. |
aaa |
LOG_STD_ACTION |
|
AAA-6-INVALIDROUTE |
6-Information |
Syntax error in route statement: [chars] |
Currently downloading route contains syntax error. |
aaa |
LOG_STD_ACTION |
|
AAA-6-SKIP_MOH_ATTRIBUTE |
6-Information |
Warning: Hardware idb is NULL. No Modem. MoH attribute can not be applied and it is Skipped for authorization. |
\nTo handle Modem-on-Hold attribute we need connectivity with modems supporting V.92 modem standards. If there is no modem there wouldn't be any tty without which we cannot use MOH attributes. |
aaa |
LOG_STD_ACTION |
|
AAA-6-SKIP_MOH_ATTRIBUTE |
6-Information |
Warning: Hardware idb is NULL. No Modem. MoH attribute can not be applied and it is Skipped for authorization. |
\nTo handle Modem-on-Hold attribute we need connectivity with modems supporting V.92 modem standards. If there is no modem there wouldn't be any tty without which we cannot use MOH attributes. |
aaa |
LOG_STD_ACTION |
|
AAA-6-SKIP_MOH_ATTRIBUTE |
6-Information |
Warning: Hardware idb is NULL. No Modem. MoH attribute can not be applied and it is Skipped for authorization. |
\nTo handle Modem-on-Hold attribute we need connectivity with modems supporting V.92 modem standards. If there is no modem there wouldn't be any tty without which we cannot use MOH attributes. |
aaa |
LOG_STD_ACTION |
|
AAA-6-USER_BLOCKED |
6-Information |
Enable view requires to be authenticated by non-none methods Please use the appropriate method with the login authentication |
\nNone method authentication is not allowed in CLI |
aaa |
LOG_STD_ACTION |
|
AAA-6-USER_BLOCKED |
6-Information |
Enable view requires to be authenticated by non-none methods Please use the appropriate method with the login authentication |
\nNone method authentication is not allowed in CLI |
aaa |
LOG_STD_ACTION |
|
AAA-6-USER_BLOCKED |
6-Information |
Enable view requires to be authenticated by non-none methods Please use the appropriate method with the login authentication |
\nNone method authentication is not allowed in CLI |
aaa |
LOG_STD_ACTION |
|
AAA-6-USER_FAIL_VIEW_AAA |
6-Information |
User [chars] failed to enter view '[chars]'. |
You have provided wrong User ID or Password for the requested view |
aaa |
"This message is for information only. No action" " is required." |
|
AAA-6-USER_FAIL_VIEW_AAA |
6-Information |
User [chars] failed to enter view '[chars]'. |
You have provided wrong User ID or Password for the requested view |
aaa |
"This message is for information only. No action" " is required." |
|
AAA-6-USER_FAIL_VIEW_AAA |
6-Information |
User [chars] failed to enter view '[chars]'. |
You have provided wrong User ID or Password for the requested view |
aaa |
"This message is for information only. No action" " is required." |
|
AAAA-3-AAAFORKFAIL |
3-Error |
Failed to start AAA process. AAA requests may not be processed. |
Failed to create the AAA process. |
aaa |
"Free up some memory." |
|
AAAA-3-AAAFORKFAIL |
3-Error |
Failed to start AAA process. AAA requests may not be processed. |
Failed to create the AAA process. |
aaa |
"Free up some memory." |
|
AAAA-3-AAAFORKFAIL |
3-Error |
Failed to start AAA process. AAA requests may not be processed. |
Failed to create the AAA process. |
aaa |
"Free up some memory." |
|
AAAA-3-ACCTATTR |
3-Error |
last accounting attribute: |
The data buffer overflowed while building the accounting packet.The accounting attribute that was being written to the buffer while the buffer overflow occured was logged. |
AAA |
LOG_STD_ACTION"Collect the logs with these debugs by" " using commands #debug aaa api#debug aaa attr#debug aaa accounting" |
|
AAAA-3-ACCTATTR |
3-Error |
last accounting attribute: |
The data buffer overflowed while building the accounting packet.The accounting attribute that was being written to the buffer while the buffer overflow occured was logged. |
AAA |
LOG_STD_ACTION"Collect the logs with these debugs by" " using commands #debug aaa api#debug aaa attr#debug aaa accounting" |
|
AAAA-3-ACCTATTR |
3-Error |
last accounting attribute: |
The data buffer overflowed while building the accounting packet.The accounting attribute that was being written to the buffer while the buffer overflow occured was logged. |
AAA |
LOG_STD_ACTION"Collect the logs with these debugs by" " using commands #debug aaa api#debug aaa attr#debug aaa accounting" |
|
AAAA-3-ACCTDUMP |
3-Error |
dump of accounting data: |
The data buffer overflowed while building the accounting packet as the total length of the attributes exceed the buffer size. Last 128 bytes of buffer data is dumped. |
AAA |
LOG_STD_ACTION"Collect the logs with these debugs by" " using commands #debug aaa api#debug aaa attr#debug aaa accounting" |
|
AAAA-3-ACCTDUMP |
3-Error |
dump of accounting data: |
The data buffer overflowed while building the accounting packet as the total length of the attributes exceed the buffer size. Last 128 bytes of buffer data is dumped. |
AAA |
LOG_STD_ACTION"Collect the logs with these debugs by" " using commands #debug aaa api#debug aaa attr#debug aaa accounting" |
|
AAAA-3-ACCTDUMP |
3-Error |
dump of accounting data: |
The data buffer overflowed while building the accounting packet as the total length of the attributes exceed the buffer size. Last 128 bytes of buffer data is dumped. |
AAA |
LOG_STD_ACTION"Collect the logs with these debugs by" " using commands #debug aaa api#debug aaa attr#debug aaa accounting" |
|
AAAA-3-ACCTFORKFAIL |
3-Error |
Failed to start accounting process. Accounting records may not be sent. |
Failed to create the accounting process. |
aaa |
"Free up some memory." |
|
AAAA-3-ACCTFORKFAIL |
3-Error |
Failed to start accounting process. Accounting records may not be sent. |
Failed to create the accounting process. |
aaa |
"Free up some memory." |
|
AAAA-3-ACCTFORKFAIL |
3-Error |
Failed to start accounting process. Accounting records may not be sent. |
Failed to create the accounting process. |
aaa |
"Free up some memory." |
|
AAAA-3-BADARG |
3-Error |
%% AAA: bad argument %0#4x |
We tried to NVGEN a non-existent AAA command. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-BADARG |
3-Error |
%% AAA: bad argument %0#4x |
We tried to NVGEN a non-existent AAA command. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-BADARG |
3-Error |
%% AAA: bad argument %0#4x |
We tried to NVGEN a non-existent AAA command. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-BADAUTHENSTR |
3-Error |
Bad authentication data: [chars] |
The data buffer overflowed while building the authentication packet as the total length of the attributes exceeded the buffer size. |
AAA |
LOG_STD_ACTION"Collect the logs with these debugs" " by using the commands #debug aaa api#debug aaa attr#debug aaa" " authentication" |
|
AAAA-3-BADAUTHENSTR |
3-Error |
Bad authentication data: [chars] |
The data buffer overflowed while building the authentication packet as the total length of the attributes exceeded the buffer size. |
AAA |
LOG_STD_ACTION"Collect the logs with these debugs" " by using the commands #debug aaa api#debug aaa attr#debug aaa" " authentication" |
|
AAAA-3-BADAUTHENSTR |
3-Error |
Bad authentication data: [chars] |
The data buffer overflowed while building the authentication packet as the total length of the attributes exceeded the buffer size. |
AAA |
LOG_STD_ACTION"Collect the logs with these debugs" " by using the commands #debug aaa api#debug aaa attr#debug aaa" " authentication" |
|
AAAA-3-BADCOMM |
3-Error |
Trying config command but should not be. |
An internal error has occurred |
aaa |
LOG_STD_ACTION |
|
AAAA-3-BADCOMM |
3-Error |
Trying config command but should not be. |
An internal error has occurred |
aaa |
LOG_STD_ACTION |
|
AAAA-3-BADCOMM |
3-Error |
Trying config command but should not be. |
An internal error has occurred |
aaa |
LOG_STD_ACTION |
|
AAAA-3-BADLIST |
3-Error |
%% AAA: bad [chars] list [chars] |
One of the AAA methods does not seem to have a list associated with it. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-BADLIST |
3-Error |
%% AAA: bad [chars] list [chars] |
One of the AAA methods does not seem to have a list associated with it. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-BADLIST |
3-Error |
%% AAA: bad [chars] list [chars] |
One of the AAA methods does not seem to have a list associated with it. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-BADREG |
3-Error |
Illegal registry call. |
An internal software error has occurred |
aaa |
LOG_STD_ACTION |
|
AAAA-3-BADREG |
3-Error |
Illegal registry call. |
An internal software error has occurred |
aaa |
LOG_STD_ACTION |
|
AAAA-3-BADREG |
3-Error |
Illegal registry call. |
An internal software error has occurred |
aaa |
LOG_STD_ACTION |
|
AAAA-3-BADSTATE |
3-Error |
\n%% AAA: Bad state for [chars] list name [dec] |
A AAA method list is neither default nor named. This is bad. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-BADSTATE |
3-Error |
\n%% AAA: Bad state for [chars] list name [dec] |
A AAA method list is neither default nor named. This is bad. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-BADSTATE |
3-Error |
\n%% AAA: Bad state for [chars] list name [dec] |
A AAA method list is neither default nor named. This is bad. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-BADSTR |
3-Error |
Bad accounting data: [chars] |
During AAA accounting operations the internal database of accounting information for a user was found to be corrupt. In all cases this indicates an internal software error and that accounting information for a particular user session has been lost. |
aaa |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
AAAA-3-BADSTR |
3-Error |
Bad accounting data: [chars] |
During AAA accounting operations the internal database of accounting information for a user was found to be corrupt. In all cases this indicates an internal software error and that accounting information for a particular user session has been lost. |
aaa |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
AAAA-3-BADSTR |
3-Error |
Bad accounting data: [chars] |
During AAA accounting operations the internal database of accounting information for a user was found to be corrupt. In all cases this indicates an internal software error and that accounting information for a particular user session has been lost. |
aaa |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
AAAA-3-DLRFORKFAIL |
3-Error |
Failed to fork process for [chars]. |
Quite likely we ran out of memory. Other explanations are possible. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-DLRFORKFAIL |
3-Error |
Failed to fork process for [chars]. |
Quite likely we ran out of memory. Other explanations are possible. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-DLRFORKFAIL |
3-Error |
Failed to fork process for [chars]. |
Quite likely we ran out of memory. Other explanations are possible. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-DROPACCTFULLQ |
3-Error |
Accounting record dropped due to a full aaa accounting queue: [chars]-[chars] [chars] [chars] |
An accounting record was dropped because there are too many accounting packets enqueued. |
aaa |
"Disable periodic accounting if it is on. The accounting queue may " "have grown to be large which is usually due to a non-responsive " "AAA server. Use 'show radius statistics' or 'show tacacs' to see " "if the number of timeouts is increasing or if the response delay is " "unusually high." |
|
AAAA-3-DROPACCTFULLQ |
3-Error |
Accounting record dropped due to a full aaa accounting queue: [chars]-[chars] [chars] [chars] |
An accounting record was dropped because there are too many accounting packets enqueued. |
aaa |
"Disable periodic accounting if it is on. The accounting queue may " "have grown to be large which is usually due to a non-responsive " "AAA server. Use 'show radius statistics' or 'show tacacs' to see " "if the number of timeouts is increasing or if the response delay is " "unusually high." |
|
AAAA-3-DROPACCTFULLQ |
3-Error |
Accounting record dropped due to a full aaa accounting queue: [chars]-[chars] [chars] [chars] |
An accounting record was dropped because there are too many accounting packets enqueued. |
aaa |
"Disable periodic accounting if it is on. The accounting queue may " "have grown to be large which is usually due to a non-responsive " "AAA server. Use 'show radius statistics' or 'show tacacs' to see " "if the number of timeouts is increasing or if the response delay is " "unusually high." |
|
AAAA-3-DROPACCTLOWMEM |
3-Error |
Accounting record dropped due to low memory: [chars]-[chars] [chars] [chars] |
An accounting record dropped due to low memory. |
aaa |
"Disable periodic accounting if it is on. Try to reduce the load " "on the router." |
|
AAAA-3-DROPACCTLOWMEM |
3-Error |
Accounting record dropped due to low memory: [chars]-[chars] [chars] [chars] |
An accounting record dropped due to low memory. |
aaa |
"Disable periodic accounting if it is on. Try to reduce the load " "on the router." |
|
AAAA-3-DROPACCTLOWMEM |
3-Error |
Accounting record dropped due to low memory: [chars]-[chars] [chars] [chars] |
An accounting record dropped due to low memory. |
aaa |
"Disable periodic accounting if it is on. Try to reduce the load " "on the router." |
|
AAAA-3-DROPACCTQUEUEEXCEEDED |
3-Error |
accounting record dropped output record queue full: [chars]-[chars] [chars] [chars]\n\ |
An accounting record was dropped. The record could not be enqueued because the number of records in the output queue has exceeded the system limit. |
aaa |
"Disable periodic accounting if it is on. " "<CmdBold>[no] aaa accounting update newinfo " "periodic <interval><NoCmdBold>" |
|
AAAA-3-DROPACCTQUEUEEXCEEDED |
3-Error |
accounting record dropped output record queue full: [chars]-[chars] [chars] [chars]\n\ |
An accounting record was dropped. The record could not be enqueued because the number of records in the output queue has exceeded the system limit. |
aaa |
"Disable periodic accounting if it is on. " "<CmdBold>[no] aaa accounting update newinfo " "periodic <interval><NoCmdBold>" |
|
AAAA-3-DROPACCTQUEUEEXCEEDED |
3-Error |
accounting record dropped output record queue full: [chars]-[chars] [chars] [chars]\n\ |
An accounting record was dropped. The record could not be enqueued because the number of records in the output queue has exceeded the system limit. |
aaa |
"Disable periodic accounting if it is on. " "<CmdBold>[no] aaa accounting update newinfo " "periodic <interval><NoCmdBold>" |
|
AAAA-3-DROPACCTSNDFAIL |
3-Error |
Accounting record dropped send to server failed: [chars]-[chars] [chars] [chars] |
An attempt to send an accounting record to a server failed. |
aaa |
"Check that the server TACACS+ or RADIUS is operational. Next " |
|
AAAA-3-DROPACCTSNDFAIL |
3-Error |
Accounting record dropped send to server failed: [chars]-[chars] [chars] [chars] |
An attempt to send an accounting record to a server failed. |
aaa |
"Check that the server TACACS+ or RADIUS is operational. Next " |
|
AAAA-3-DROPACCTSNDFAIL |
3-Error |
Accounting record dropped send to server failed: [chars]-[chars] [chars] [chars] |
An attempt to send an accounting record to a server failed. |
aaa |
"Check that the server TACACS+ or RADIUS is operational. Next " |
|
AAAA-3-ILLEGALNAME |
3-Error |
Illegal [chars] [chars] name \[chars]\ rejected |
A method-list name should not be the same as a method name. Please choose a different name for the method list. |
aaa |
"Pick a different method-list name that is not also a method-name." |
|
AAAA-3-ILLEGALNAME |
3-Error |
Illegal [chars] [chars] name \[chars]\ rejected |
A method-list name should not be the same as a method name. Please choose a different name for the method list. |
aaa |
"Pick a different method-list name that is not also a method-name." |
|
AAAA-3-ILLEGALNAME |
3-Error |
Illegal [chars] [chars] name \[chars]\ rejected |
A method-list name should not be the same as a method name. Please choose a different name for the method list. |
aaa |
"Pick a different method-list name that is not also a method-name." |
|
AAAA-3-ILLSGNAME |
3-Error |
Illegal server-group name [chars] type [chars]. |
The given server-group name is a name that could conflict with internally chosen lists. |
aaa |
"Please pick a different server-group name." |
|
AAAA-3-ILLSGNAME |
3-Error |
Illegal server-group name [chars] type [chars]. |
The given server-group name is a name that could conflict with internally chosen lists. |
aaa |
"Please pick a different server-group name." |
|
AAAA-3-ILLSGNAME |
3-Error |
Illegal server-group name [chars] type [chars]. |
The given server-group name is a name that could conflict with internally chosen lists. |
aaa |
"Please pick a different server-group name." |
|
AAAA-3-INTERNAL_ERROR |
3-Error |
[chars] |
This is an internal software error. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-INTERNAL_ERROR |
3-Error |
[chars] |
This is an internal software error. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-INTERNAL_ERROR |
3-Error |
[chars] |
This is an internal software error. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-INVALIDATTRLIST |
3-Error |
aaa attribute list CLI is not valid when configuring in sub-mode. |
An internal error has occurred |
aaa |
LOG_STD_ACTION |
|
AAAA-3-INVALIDATTRLIST |
3-Error |
aaa attribute list CLI is not valid when configuring in sub-mode. |
An internal error has occurred |
aaa |
LOG_STD_ACTION |
|
AAAA-3-INVALIDATTRLIST |
3-Error |
aaa attribute list CLI is not valid when configuring in sub-mode. |
An internal error has occurred |
aaa |
LOG_STD_ACTION |
|
AAAA-3-INVALIDLIST |
3-Error |
%% AAA: invalid [chars] list [dec]. |
One of the AAA methods lists has inconsistent settings |
aaa |
LOG_STD_ACTION |
|
AAAA-3-INVALIDLIST |
3-Error |
%% AAA: invalid [chars] list [dec]. |
One of the AAA methods lists has inconsistent settings |
aaa |
LOG_STD_ACTION |
|
AAAA-3-INVALIDLIST |
3-Error |
%% AAA: invalid [chars] list [dec]. |
One of the AAA methods lists has inconsistent settings |
aaa |
LOG_STD_ACTION |
|
AAAA-3-INVSTATE |
3-Error |
[chars] AUTHOR/[chars]: Internal state is invalid: astruct 0x[hec] ustruct 0x[hec] |
One of the two mentioned data-structures is not set but is needed here. This is an internal software error. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-INVSTATE |
3-Error |
[chars] AUTHOR/[chars]: Internal state is invalid: astruct 0x[hec] ustruct 0x[hec] |
One of the two mentioned data-structures is not set but is needed here. This is an internal software error. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-INVSTATE |
3-Error |
[chars] AUTHOR/[chars]: Internal state is invalid: astruct 0x[hec] ustruct 0x[hec] |
One of the two mentioned data-structures is not set but is needed here. This is an internal software error. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-LISTCREATE |
3-Error |
The list [dec] for [chars] is NULL. This should never be. |
One of the method-lists created at startup wasn't created. This may cause a reload |
aaa |
LOG_STD_ACTION |
|
AAAA-3-LISTCREATE |
3-Error |
The list [dec] for [chars] is NULL. This should never be. |
One of the method-lists created at startup wasn't created. This may cause a reload |
aaa |
LOG_STD_ACTION |
|
AAAA-3-LISTCREATE |
3-Error |
The list [dec] for [chars] is NULL. This should never be. |
One of the method-lists created at startup wasn't created. This may cause a reload |
aaa |
LOG_STD_ACTION |
|
AAAA-3-MKTIMERFAIL |
3-Error |
Failed to create periodic accounting timer for user [chars]. This user may not generate periodic accounting records. |
Failed to malloc a timer struct for periodic accounting. |
aaa |
"Free up some memory and have user re-authenticate." |
|
AAAA-3-MKTIMERFAIL |
3-Error |
Failed to create periodic accounting timer for user [chars]. This user may not generate periodic accounting records. |
Failed to malloc a timer struct for periodic accounting. |
aaa |
"Free up some memory and have user re-authenticate." |
|
AAAA-3-MKTIMERFAIL |
3-Error |
Failed to create periodic accounting timer for user [chars]. This user may not generate periodic accounting records. |
Failed to malloc a timer struct for periodic accounting. |
aaa |
"Free up some memory and have user re-authenticate." |
|
AAAA-3-MKTIMERINVALID |
3-Error |
Invalid request to create periodic accounting timer for user [chars]. Timer already exists. |
Invalid client usuage of timer struct for periodic accounting. |
aaa |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
AAAA-3-MKTIMERINVALID |
3-Error |
Invalid request to create periodic accounting timer for user [chars]. Timer already exists. |
Invalid client usuage of timer struct for periodic accounting. |
aaa |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
AAAA-3-MKTIMERINVALID |
3-Error |
Invalid request to create periodic accounting timer for user [chars]. Timer already exists. |
Invalid client usuage of timer struct for periodic accounting. |
aaa |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
AAAA-3-NOADMINPROC |
3-Error |
[chars] |
Administrative process has been enabled but somehow could not run |
- |
- |
|
AAAA-3-NOADMINPROC |
3-Error |
[chars] |
Administrative process has been enabled but somehow could not run |
- |
- |
|
AAAA-3-NOADMINPROC |
3-Error |
[chars] |
Administrative process has been enabled but somehow could not run |
- |
- |
|
AAAA-3-NOFREELISTS |
3-Error |
%% AAA: No free [chars] lists for \[chars]\ |
You have reached the maximum number of possible authentication lists for this method. |
aaa |
LOG_STD_RECUR_ACTION |
|
AAAA-3-NOFREELISTS |
3-Error |
%% AAA: No free [chars] lists for \[chars]\ |
You have reached the maximum number of possible authentication lists for this method. |
aaa |
LOG_STD_RECUR_ACTION |
|
AAAA-3-NOFREELISTS |
3-Error |
%% AAA: No free [chars] lists for \[chars]\ |
You have reached the maximum number of possible authentication lists for this method. |
aaa |
LOG_STD_RECUR_ACTION |
|
AAAA-3-NOLIST |
3-Error |
[chars]: no method list-name. |
An internal software error. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-NOLIST |
3-Error |
[chars]: no method list-name. |
An internal software error. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-NOLIST |
3-Error |
[chars]: no method list-name. |
An internal software error. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-NOREG |
3-Error |
[chars] method [dec] has no registry! |
An internal error has occurred |
aaa |
LOG_STD_ACTION |
|
AAAA-3-NOREG |
3-Error |
[chars] method [dec] has no registry! |
An internal error has occurred |
aaa |
LOG_STD_ACTION |
|
AAAA-3-NOREG |
3-Error |
[chars] method [dec] has no registry! |
An internal error has occurred |
aaa |
LOG_STD_ACTION |
|
AAAA-3-NOSERV |
3-Error |
No name for servergroup in method [chars] |
An internal error has occurred |
aaa |
LOG_STD_ACTION |
|
AAAA-3-NOSERV |
3-Error |
No name for servergroup in method [chars] |
An internal error has occurred |
aaa |
LOG_STD_ACTION |
|
AAAA-3-NOSERV |
3-Error |
No name for servergroup in method [chars] |
An internal error has occurred |
aaa |
LOG_STD_ACTION |
|
AAAA-3-NOSG |
3-Error |
No server-group passed through parser. |
An internal error has occurred |
aaa |
LOG_STD_ACTION |
|
AAAA-3-NOSG |
3-Error |
No server-group passed through parser. |
An internal error has occurred |
aaa |
LOG_STD_ACTION |
|
AAAA-3-NOSG |
3-Error |
No server-group passed through parser. |
An internal error has occurred |
aaa |
LOG_STD_ACTION |
|
AAAA-3-NULPORT |
3-Error |
Could not establish port information |
This message indicates an internal software error. AAA could not determine a valid port string based on the information provided to it via a client. |
aaa |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
AAAA-3-NULPORT |
3-Error |
Could not establish port information |
This message indicates an internal software error. AAA could not determine a valid port string based on the information provided to it via a client. |
aaa |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
AAAA-3-NULPORT |
3-Error |
Could not establish port information |
This message indicates an internal software error. AAA could not determine a valid port string based on the information provided to it via a client. |
aaa |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
AAAA-3-NULUSR |
3-Error |
accounting for null user |
This message indicates an internal software error. During shutdown of a line or interface the system tried to send accounting information via AAA but could not find the user to which the accounting information belonged. The most likely reason for this error is trying to do accounting twice for the same event. This error message can occur without any loss of accounting information. |
aaa |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
AAAA-3-NULUSR |
3-Error |
accounting for null user |
This message indicates an internal software error. During shutdown of a line or interface the system tried to send accounting information via AAA but could not find the user to which the accounting information belonged. The most likely reason for this error is trying to do accounting twice for the same event. This error message can occur without any loss of accounting information. |
aaa |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
AAAA-3-NULUSR |
3-Error |
accounting for null user |
This message indicates an internal software error. During shutdown of a line or interface the system tried to send accounting information via AAA but could not find the user to which the accounting information belonged. The most likely reason for this error is trying to do accounting twice for the same event. This error message can occur without any loss of accounting information. |
aaa |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
AAAA-3-OVERWRITE |
3-Error |
Overwrote internal buffer space [chars] |
An internal software error. |
aaa |
"Report to tac@cisco.com." |
|
AAAA-3-OVERWRITE |
3-Error |
Overwrote internal buffer space [chars] |
An internal software error. |
aaa |
"Report to tac@cisco.com." |
|
AAAA-3-OVERWRITE |
3-Error |
Overwrote internal buffer space [chars] |
An internal software error. |
aaa |
"Report to tac@cisco.com." |
|
AAAA-3-PERIODICFORKFAIL |
3-Error |
Failed to start periodic accounting process. Periodic accounting records may not be sent. |
Failed to create the periodic accounting process. |
aaa |
"Free up some memory." |
|
AAAA-3-PERIODICFORKFAIL |
3-Error |
Failed to start periodic accounting process. Periodic accounting records may not be sent. |
Failed to create the periodic accounting process. |
aaa |
"Free up some memory." |
|
AAAA-3-PERIODICFORKFAIL |
3-Error |
Failed to start periodic accounting process. Periodic accounting records may not be sent. |
Failed to create the periodic accounting process. |
aaa |
"Free up some memory." |
|
AAAA-3-PERNOTIMER |
3-Error |
AAA/ACCT/TIMER: Periodic update but no timer. |
We are trying to free a timer and the method is PERIODIC but no timer seems to exist. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-PERNOTIMER |
3-Error |
AAA/ACCT/TIMER: Periodic update but no timer. |
We are trying to free a timer and the method is PERIODIC but no timer seems to exist. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-PERNOTIMER |
3-Error |
AAA/ACCT/TIMER: Periodic update but no timer. |
We are trying to free a timer and the method is PERIODIC but no timer seems to exist. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-RELOGIN |
3-Error |
sanity check in re-login [chars] to [chars] |
A software or hardware error occurred. |
aaa |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
AAAA-3-RELOGIN |
3-Error |
sanity check in re-login [chars] to [chars] |
A software or hardware error occurred. |
aaa |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
AAAA-3-RELOGIN |
3-Error |
sanity check in re-login [chars] to [chars] |
A software or hardware error occurred. |
aaa |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
AAAA-3-SGDUPFREE |
3-Error |
Duplicate free of server group 0x[hec] |
This is an internal software error. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-SGDUPFREE |
3-Error |
Duplicate free of server group 0x[hec] |
This is an internal software error. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-SGDUPFREE |
3-Error |
Duplicate free of server group 0x[hec] |
This is an internal software error. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-STRCREATE |
3-Error |
str_create overwrote its internal buffer. |
An internal buffer used to assemble a string was exceeded thus possibly corrupting other memory. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-STRCREATE |
3-Error |
str_create overwrote its internal buffer. |
An internal buffer used to assemble a string was exceeded thus possibly corrupting other memory. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-STRCREATE |
3-Error |
str_create overwrote its internal buffer. |
An internal buffer used to assemble a string was exceeded thus possibly corrupting other memory. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-SUBTYPE |
3-Error |
Bad Subtype [dec] for \[chars]\ [dec] |
An internal software error. |
aaa |
"Report to tac@cisco.com." |
|
AAAA-3-SUBTYPE |
3-Error |
Bad Subtype [dec] for \[chars]\ [dec] |
An internal software error. |
aaa |
"Report to tac@cisco.com." |
|
AAAA-3-SUBTYPE |
3-Error |
Bad Subtype [dec] for \[chars]\ [dec] |
An internal software error. |
aaa |
"Report to tac@cisco.com." |
|
AAAA-3-TIMERNOPER |
3-Error |
AAA/ACCT/TIMER: No periodic update but timer set. |
We are trying to free a timer but the update method is not PERIODIC and so no timer should exist. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-TIMERNOPER |
3-Error |
AAA/ACCT/TIMER: No periodic update but timer set. |
We are trying to free a timer but the update method is not PERIODIC and so no timer should exist. |
aaa |
LOG_STD_ACTION |
|
AAAA-3-TIMERNOPER |
3-Error |
AAA/ACCT/TIMER: No periodic update but timer set. |
We are trying to free a timer but the update method is not PERIODIC and so no timer should exist. |
aaa |
LOG_STD_ACTION |
|
AAAA-4-BADMETHNAME |
4-Warning |
Bad [chars] method-list name \[chars]\ this is only a warning |
A method-list name should not be the same as a method name. Please choose a different name for the method list. |
aaa |
"Pick a different method-list name that is not also a method-name." |
|
AAAA-4-BADMETHNAME |
4-Warning |
Bad [chars] method-list name \[chars]\ this is only a warning |
A method-list name should not be the same as a method name. Please choose a different name for the method list. |
aaa |
"Pick a different method-list name that is not also a method-name." |
|
AAAA-4-BADMETHNAME |
4-Warning |
Bad [chars] method-list name \[chars]\ please choose another name |
A method-list name should not be the same as a method name. Please choose a different name for the method list. |
aaa |
"Pick a different method-list name that is not also a method-name." |
|
AAAA-4-BADSGNAME |
4-Warning |
Bad server-group name [chars] type [chars]. |
The given server-group name either doesn't exist or the given type does not match the defined server-group. |
aaa |
"Verify that the group exists and has the same " "type." |
|
AAAA-4-BADSGNAME |
4-Warning |
Bad server-group name [chars] type [chars]. |
The given server-group name either doesn't exist or the given type does not match the defined server-group. |
aaa |
"Verify that the group exists and has the same " "type." |
|
AAAA-4-BADSGNAME |
4-Warning |
Bad server-group name [chars] type [chars]. |
The given server-group name either doesn't exist or the given type does not match the defined server-group. |
aaa |
"Verify that the group exists and has the same " "type." |
|
AAAA-4-BADSGTYPE |
4-Warning |
Server-group [chars] is not of type [chars]. |
The given server-group name does not match the specified type |
aaa |
"Verify that the group exists and has " "the same type." |
|
AAAA-4-BADSGTYPE |
4-Warning |
Server-group [chars] is not of type [chars]. |
The given server-group name does not match the specified type |
aaa |
"Verify that the group exists and has " "the same type." |
|
AAAA-4-BADSGTYPE |
4-Warning |
Server-group [chars] is not of type [chars]. |
The given server-group name does not match the specified type |
aaa |
"Verify that the group exists and has " "the same type." |
|
AAAA-4-CLI_DEPRECATED |
4-Warning |
[chars] |
CLI deprecated. New CLI to be used |
aaa |
LOG_STD_ACTION |
|
AAAA-4-CLI_DEPRECATED |
4-Warning |
[chars] |
CLI deprecated. New CLI to be used |
aaa |
LOG_STD_ACTION |
|
AAAA-4-CLI_DEPRECATED |
4-Warning |
[chars] |
CLI deprecated. New CLI to be used |
aaa |
LOG_STD_ACTION |
|
AAAA-4-DNISGPUNDEF |
4-Warning |
Warning: DNIS group [chars] is not defined. |
The DNIS group was used without defining it first. It should be defined before use. |
aaa |
"Define the DNIS group before using it." |
|
AAAA-4-DNISGPUNDEF |
4-Warning |
Warning: DNIS group [chars] is not defined. |
The DNIS group was used without defining it first. It should be defined before use. |
aaa |
"Define the DNIS group before using it." |
|
AAAA-4-DNISGPUNDEF |
4-Warning |
Warning: DNIS group [chars] is not defined. |
The DNIS group was used without defining it first. It should be defined before use. |
aaa |
"Define the DNIS group before using it." |
|
AAAA-4-NOCACHEPROC |
4-Warning |
The aaa cache process is not created. Please configure aaa cache profile first |
Cache was listed in a method-list without defining it first. Cache profile should be defined before use. |
aaa |
"Define the cache profile before using it." |
|
AAAA-4-NOCACHEPROC |
4-Warning |
The aaa cache process is not created. Please configure aaa cache profile first |
Cache was listed in a method-list without defining it first. Cache profile should be defined before use. |
aaa |
"Define the cache profile before using it." |
|
AAAA-4-NOCACHEPROC |
4-Warning |
The aaa cache process is not created. Please configure aaa cache profile first |
Cache was listed in a method-list without defining it first. Cache profile should be defined before use. |
aaa |
"Define the cache profile before using it." |
|
AAAA-4-NOSERVER |
4-Warning |
Warning: Server [chars] is not defined. |
The given server is not on the master-list and should be defined or unexpected things might happen. |
aaa |
"Please define the server on the appropriate " "master-list as soon as possible." |
|
AAAA-4-NOSERVER |
4-Warning |
Warning: Server [chars] is not defined. |
The given server is not on the master-list and should be defined or unexpected things might happen. |
aaa |
"Please define the server on the appropriate " "master-list as soon as possible." |
|
AAAA-4-NOSERVER |
4-Warning |
Warning: Server [chars] is not defined. |
The given server is not on the master-list and should be defined or unexpected things might happen. |
aaa |
"Please define the server on the appropriate " "master-list as soon as possible." |
|
AAAA-4-SERVNOGRP |
4-Warning |
Warning: Server [inet]:[dec][dec] is not part of server group [chars]. |
The server does not belong to the specified server group |
aaa |
"Please check that the specified server belongs " "to the server group" |
|
AAAA-4-SERVNOGRP |
4-Warning |
Warning: Server [inet]:[dec][dec] is not part of server group [chars]. |
The server does not belong to the specified server group |
aaa |
"Please check that the specified server belongs " "to the server group" |
|
AAAA-4-SERVNOGRP |
4-Warning |
Warning: Server [inet]:[dec][dec] is not part of server group [chars]. |
The server does not belong to the specified server group |
aaa |
"Please check that the specified server belongs " "to the server group" |
|
AAAA-4-SERVNORADIUS |
4-Warning |
The server-group \[chars]\ is not a radius server group. Please define \[chars]\ as a radius server group. |
The protocol used by the server-group doesn't support the configured aaa action. |
aaa |
"Use a radius server-group." |
|
AAAA-4-SERVNORADIUS |
4-Warning |
The server-group \[chars]\ is not a radius server group. Please define \[chars]\ as a radius server group. |
The protocol used by the server-group doesn't support the configured aaa action. |
aaa |
"Use a radius server-group." |
|
AAAA-4-SERVNORADIUS |
4-Warning |
The server-group \[chars]\ is not a radius server group. Please define \[chars]\ as a radius server group. |
The protocol used by the server-group doesn't support the configured aaa action. |
aaa |
"Use a radius server-group." |
|
AAAA-4-SERVNOTACPLUS |
4-Warning |
The server-group \[chars]\ is not a tacacs+ server group. Please define \[chars]\ as a tacacs+ server group. |
The protocol used by the server-group doesn't support the configured aaa action. |
aaa |
"Use a tacacs+ server-group." |
|
AAAA-4-SERVNOTACPLUS |
4-Warning |
The server-group \[chars]\ is not a tacacs+ server group. Please define \[chars]\ as a tacacs+ server group. |
The protocol used by the server-group doesn't support the configured aaa action. |
aaa |
"Use a tacacs+ server-group." |
|
AAAA-4-SERVNOTACPLUS |
4-Warning |
The server-group \[chars]\ is not a tacacs+ server group. Please define \[chars]\ as a tacacs+ server group. |
The protocol used by the server-group doesn't support the configured aaa action. |
aaa |
"Use a tacacs+ server-group." |
|
AAAA-4-SERVUNDEF |
4-Warning |
The server-group \[chars]\ is not defined. Please define it. |
A given server-group was listed in a method-list without defining it first. Server-groups should be defined before use. |
aaa |
"Define the server-group before using it." |
|
AAAA-4-SERVUNDEF |
4-Warning |
The server-group \[chars]\ is not defined. Please define it. |
A given server-group was listed in a method-list without defining it first. Server-groups should be defined before use. |
aaa |
"Define the server-group before using it." |
|
AAAA-4-SERVUNDEF |
4-Warning |
The server-group \[chars]\ is not defined. Please define it. |
A given server-group was listed in a method-list without defining it first. Server-groups should be defined before use. |
aaa |
"Define the server-group before using it." |
|
AAAA-4-UNSUPWAITSTART |
4-Warning |
%% AAA: Unsupported option wait-start mapped to start-stop. |
wait-start accounting is not supported. It is being mapped to start-stop |
aaa |
"wait-start accounting is not supported. It is being mapped to start-stop" |
|
AAAA-4-UNSUPWAITSTART |
4-Warning |
%% AAA: Unsupported option wait-start mapped to start-stop. |
wait-start accounting is not supported. It is being mapped to start-stop |
aaa |
"wait-start accounting is not supported. It is being mapped to start-stop" |
|
AAAA-4-UNSUPWAITSTART |
4-Warning |
%% AAA: Unsupported option wait-start mapped to start-stop. |
wait-start accounting is not supported. It is being mapped to start-stop |
aaa |
"wait-start accounting is not supported. It is being mapped to start-stop" |
|
AAAA-6-ACCTLOCAL |
6-Information |
Username: [chars] Privilege level: [dec] Command: [chars] |
AAA local accounting log message |
aaa |
"This information is to store buffered logs" "locally and send to SYSLOG server" |
|
AAAA-6-ACCTSTART |
6-Information |
[chars] |
A AAA accounting start message. |
aaa |
"This information is for information only." |
|
AAAA-6-ACCTSTART |
6-Information |
[chars] |
A AAA accounting start message. |
aaa |
"This information is for information only." |
|
AAAA-6-ACCTSTART |
6-Information |
[chars] |
A AAA accounting start message. |
aaa |
"This information is for information only." |
|
AAAA-6-ACCTSTOP |
6-Information |
[chars] |
A AAA accounting stop message. |
aaa |
"This information is for information only." |
|
AAAA-6-ACCTSTOP |
6-Information |
[chars] |
A AAA accounting stop message. |
aaa |
"This information is for information only." |
|
AAAA-6-ACCTSTOP |
6-Information |
[chars] |
A AAA accounting stop message. |
aaa |
"This information is for information only." |
|
AAAA-6-ACCTWATCH |
6-Information |
[chars] |
A AAA accounting watchdog/update message. |
aaa |
"This information is for information only." |
|
AAAA-6-ACCTWATCH |
6-Information |
[chars] |
A AAA accounting watchdog/update message. |
aaa |
"This information is for information only." |
|
AAAA-6-ACCTWATCH |
6-Information |
[chars] |
A AAA accounting watchdog/update message. |
aaa |
"This information is for information only." |
|
AAAA-6-ADMINMSG |
6-Information |
[chars] [chars]: [chars] |
This administrative message was passed to the NAS from the AAA server |
aaa |
"No action need be taken but the message may " "contain usefull information regarding some event " "on the server" |
|
AAAA-6-ADMINMSG |
6-Information |
[chars] [chars]: [chars] |
This administrative message was passed to the NAS from the AAA server |
aaa |
"No action need be taken but the message may " "contain usefull information regarding some event " "on the server" |
|
AAAA-6-ADMINMSG |
6-Information |
[chars] [chars]: [chars] |
This administrative message was passed to the NAS from the AAA server |
aaa |
"No action need be taken but the message may " "contain usefull information regarding some event " "on the server" |
|
AAAA-6-SERVERMSG |
6-Information |
[chars] [chars]: [chars] |
This message was passed to the NAS from the AAA server |
aaa |
"No action need be taken but the message may " "contain usefull information regarding some event " "on the server" |
|
AAAA-6-SERVERMSG |
6-Information |
[chars] [chars]: [chars] |
This message was passed to the NAS from the AAA server |
aaa |
"No action need be taken but the message may " "contain usefull information regarding some event " "on the server" |
|
AAAA-6-SERVERMSG |
6-Information |
[chars] [chars]: [chars] |
This message was passed to the NAS from the AAA server |
aaa |
"No action need be taken but the message may " "contain usefull information regarding some event " "on the server" |
|
AC-3-AC_SANITY |
3-Error |
[chars] |
A unexpected sanity check failed during Attachment Circuit processing. |
ac |
LOG_STD_ACTION |
|
AC-3-AC_WS_REGISTER |
3-Error |
L2VPN WS registration failed for [chars] |
An error was encountered when attempting to register the specified Attachment Circuit type with the Layer 2 Virtual Private Network Wire Service facility. |
ac |
LOG_STD_ACTION |
|
AC-3-ACMGR_INVALID_HDL |
3-Error |
Received invalid [chars] handle |
Attachment Circuit Manager receives invalid handle. |
ac |
LOG_STD_ACTION |
|
AC-3-ACMGR_INVALID_MSG |
3-Error |
Received [chars] |
Attachment Circuit Manager receives invalid message. |
ac |
LOG_STD_ACTION |
|
AC-3-ACMGR_MISSED_CIRCUIT |
3-Error |
Circuit info missing in [chars] message. |
AC Manager received message with missing circuit info |
ac |
LOG_STD_ACTION |
|
AC-3-ACMGR_XDM_CREATE |
3-Error |
Failed to create XDM - rc [dec] |
Attachment Circuit Manager was unable to create a Dispatch Manager instance for event handling. |
ac |
LOG_STD_ACTION |
|
AC-3-L2SS_BAD_HANDLE |
3-Error |
Corrupted L2SS handle [[hec]]. |
An internal L2SS Manager occurred. |
ac |
LOG_STD_ACTION |
|
AC-3-L2SS_NULL_CONTEXT |
3-Error |
Encountered a NULL context in [chars] |
Encountered a NULL context in L2SS Manager. |
ac |
LOG_STD_ACTION |
|
AC-3-L2SS_UNEXPECTED |
3-Error |
Received unexpected [chars] message |
L2SS received unexpected message. |
ac |
LOG_STD_ACTION |
|
AC-3-L2SS_WRONG_KEYS |
3-Error |
Wrong set of keys in [chars] message |
SIP sends a wrong set of keys to L2SS Manager. |
ac |
LOG_STD_ACTION |
|
ACCESS_IE-3-INVALID_HANDLE |
3-Error |
Caller passed in invalid handle - traceback to follow. |
An invalid handle was encountered in the Access IE library. |
- |
LOG_STD_ACTION |
|
ACCESS_SESSION-3-TRACE_INIT_FAIL |
3-Error |
Initialization failed with code: [dec] |
Failed to initialize access-session trace. |
dot1x-ios |
LOG_STD_NO_ACTION |
|
ACCESS_SESSION-3-TRACE_INIT_FAIL |
3-Error |
Initialization failed with code: [dec] |
Failed to initialize access-session trace. |
dot1x-ios |
LOG_STD_NO_ACTION |
|
ACCESS_SESSION-3-TRACE_REG_FAIL |
3-Error |
Component [chars] registration failed. Error code: [dec] |
Component failed to register with access-session trace |
dot1x-ios |
LOG_STD_NO_ACTION |
|
ACCESS_SESSION-3-TRACE_REG_FAIL |
3-Error |
Component [chars] registration failed. Error code: [dec] |
Component failed to register with access-session trace |
dot1x-ios |
LOG_STD_NO_ACTION |
|
ACCESS_TUNNEL_ISSU-3-BUFFER |
3-Error |
ACCESS_TUNNEL ISSU client failed to get buffer for message error [dec] |
ACCESS_TUNNEL ISSU client failed to get buffer for building\n\ a negotiation message. Hence it can not send the negotiation\n\ message to the standby unit. When there is a problem in\n\ the negotiaiton the standby unit can not be brought up. |
accsw-p-securefab |
"show logging and show checkpoint client" |
|
ACCESS_TUNNEL_ISSU-3-CAP_INVALID_SIZE |
3-Error |
ACCESS_TUNNEL ISSU client capability list is empty. |
The ACCESS_TUNNEL ISSU client capability exchange list size\n\ is invalid. |
accsw-p-securefab |
"show issu capability entries <Client_ID>" |
|
ACCESS_TUNNEL_ISSU-3-CAP_NOT_COMPATIBLE |
3-Error |
ACCESS_TUNNEL ISSU client capability exchange result incompatible. |
The ACCESS_TUNNEL ISSU client capability exchange has negotiated\n\ as incompatible with the peer. |
accsw-p-securefab |
"show issu negotiated capability <Session_ID>" |
|
ACCESS_TUNNEL_ISSU-3-CAPABILITY |
3-Error |
ACCESS_TUNNEL ISSU client [chars] |
ACCESS_TUNNEL ISSU client observed an error during capability\n\ negotiation. When this error happens there is a mismatch\n\ between the client capability between the active and\n\ standby unit. |
accsw-p-securefab |
"show issu capability entries <client_id> and \n\ show issu session <client_id> and \n\ show issu negotiated capability <session_id>" |
|
ACCESS_TUNNEL_ISSU-3-INIT |
3-Error |
ACCESS_TUNNEL ISSU client initialization failed at [chars] error [chars] |
ACCESS_TUNNEL ISSU client could not be initiailzed this will\n\ cause catstrophic failure when ISSU upgrade or downgrade\n\ is performed. |
accsw-p-securefab |
LOG_STD_SH_TECH_ACTION |
|
ACCESS_TUNNEL_ISSU-3-MSG_NOT_OK |
3-Error |
ACCESS_TUNNEL ISSU client message [dec] is not compatible |
ACCESS_TUNNEL ISSU client received an incompatible message\n\ from the peer unit. Since the message is not compatible\n\ it can not be processed by this unit |
accsw-p-securefab |
"show issu message group <client_id> and\n\ show issu session <client_id> and \n\ show issu negotiated version <session_id>" |
|
ACCESS_TUNNEL_ISSU-3-MSG_SIZE |
3-Error |
ACCESS_TUNNEL ISSU client failed to get the message size for message [dec] |
ACCESS_TUNNEL ISSU client failed to calculate message size\n\ for the message specified. The ACCESS_TUNNEL ISSU client will not\n\ be able to send message to the standby unit. |
accsw-p-securefab |
"show issu message group <client_id> and\n\ show issu session <client_id> and \n\ show issu negotiated version <session_id>" |
|
ACCESS_TUNNEL_ISSU-3-POLICY |
3-Error |
ACCESS_TUNNEL ISSU client message type [dec] is [chars] |
ACCESS_TUNNEL ISSU client received an message type which it\n\ does not support. The policy is applied to make the session\n\ compatible. |
accsw-p-securefab |
"show issu session <client_id>" |
|
ACCESS_TUNNEL_ISSU-3-SEND_FAILED |
3-Error |
ACCESS_TUNNEL ISSU client failed to send a negotiation message error [dec] |
ACCESS_TUNNEL ISSU client could not send a session negotiation\n\ message to the peer. When there is a problem in the \n\ negotiation the standby unit can not be brought up. |
accsw-p-securefab |
"show logging and show checkpoint client" |
|
ACCESS_TUNNEL_ISSU-3-SESSION |
3-Error |
ACCESS_TUNNEL ISSU client [chars] |
ACCESS_TUNNEL ISSU client observed an error during a session\n\ negotiation with the peer unit. When there is a problem\n\ with the session the standby unit can not be brought up. |
accsw-p-securefab |
"show issu capability entries <client_id> and \n\ show issu session <client_id> and \n\ show issu negotiated capability <session_id>" |
|
ACCESS_TUNNEL_ISSU-3-SESSION_UNREGISTRY |
3-Error |
ACCESS_TUNNEL ISSU client failed to unregister session information. Error: [dec] [chars] |
The ACCESS_TUNNEL ISSU client failed to unregister session information. |
accsw-p-securefab |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ACCESS_TUNNEL_ISSU-3-TRANSFORM |
3-Error |
ACCESS_TUNNEL ISSU client [chars] transform failed error [chars] |
ACCESS_TUNNEL ISSU client could not transform the message.\n\ If the transmit transformation failed it means that the\n\ checkpoint message can not be sent to the standby unit.\n\ If the receive transformation failed it means that the\n\ checkpoint message can not be applied on the standby\n\ unit. In both cases the ACCESS_TUNNEL state will not\n\ be indentical with the active unit. |
accsw-p-securefab |
"show issu session <client_id> and \n\ show issu negotiated version <session_id>" |
|
ACE-2-CRYPTOENGERR |
2-Critical |
Crypto engine error: [chars] [dec] |
A crypto engine operation did not complete. This error condition can indicate that the crypto engine cannot bind or unbind an interface to a crypto engine. It can also indicate that the crypto engine cannot query an interface ID. |
- |
"Remove the cryptomap set from the interface by issuing " "<CmdBold>no crypto map<noCmdBold> command. Then reattach the cryptomap " "set to the interface using <CmdBold>crypto map<noCmdBold> command. " "Although removing and reattaching the crypto map might fix the " "cryptographic engine operation failure report the failure to your " "technical support representative along with the sequence of commands " "that lead to the failure". |
|
ACE-2-INTTABOPERR |
2-Critical |
Internal [chars] table error: [chars] |
Internal table operation fails. This means the state of the module is mostly like inconsistent. |
iosxe-ipsec |
"Contact your technical support representative" |
|
ACE-3-BOOTMSGERR |
3-Error |
[chars]: boot error: [chars] |
The ACE completed booting but with an error status code. ACE will not operate and it will not register with the crypto subsystem. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
ACE-3-CEAL_REGISTRATION |
3-Error |
ACE [chars] failed to register. |
The ACE failed to register with CEAL |
iosxe-ipsec |
"Reset the hw module" |
|
ACE-3-CRASHDUMPERR |
3-Error |
[chars]: crashdump retrieval error: [chars] [chars] |
An error occurred during crashdump file retrieval from ACE. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
ACE-3-CRASHDUMPSTART |
3-Error |
[chars]: crashdump retrieval initiated to file [chars] |
The ACE crashed and was rebooted. Upon reboot a crashdump file was detected and uploaded to the sup-bootflash filesystem. |
- |
"Report the crash and transfer the crashdump file to your technical" "support representative." |
|
ACE-3-HAPITRUNC |
3-Error |
[chars]: Received truncated HAPI message tlen=[dec] actual=[dec] |
An IPsec packet was unexpectedly forwarded to the RP |
iosxe-ipsec |
"If this message was seen in the context of the router booting " "enabling the hardware crypto accelerator then this message is normal " "and can be safely ignored. " "Otherwise please copy the error message exactly as it appears " "and report it to your technical support representative." |
|
ACE-3-INITFAIL |
3-Error |
[chars]: initialization failed [chars] |
An error occured in the indicated control transaction. |
iosxe-ipsec |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
ACE-3-INVTID |
3-Error |
[chars]: [chars] of invalid [chars] trans id [dec] |
An invalid transaction ID of for the indicated transaction\n\ type was encountered |
iosxe-ipsec |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
ACE-3-NOENGINESLOT |
3-Error |
Interface [chars] has no crypto engine slot |
An IKE SA was requested for a given interface but no crypto engine slot was assigned to that interface |
iosxe-ipsec |
"Configure the interface in question with the" " `crypto engine [sub]slot' command" |
|
ACE-3-NOMORETID |
3-Error |
[chars]: out of [chars] transactions |
Transaction pool for the indicated transaction type was\n\ exhausted. |
iosxe-ipsec |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
ACE-3-OUTOFID_RL |
3-Error |
Too many [chars] IDs in the system. Cannot allocate a new one |
All the IDs of the specified type are in use |
iosxe-ipsec |
"Reduce the traffic load number of IPSec tunnels and/or frequency of re-key." "If this message was seen under light loading conditions then" "copy the error message exactly as it appears and report it to your " "technical support representative." |
|
ACE-3-OUTOFRES |
3-Error |
Too many [chars] in the system. Cannot allocate a new one |
All VPN-accelerator resources of a particular are in used and thus this allocation request fails. |
iosxe-ipsec |
"Remove the cryptomap set from the interface. " "Reduce the number of that resource in the " "system. For ACL reduce the number of ACL " "permit ACE in the system. For cryptomap reduce the" "number of cryptomaps in the system. For SPD and " "SPD map reduce the number of interface with " "cryptomap set attached." |
|
ACE-4-BV_IDMGR_DESTROY |
4-Warning |
ACE failed to destroy [chars] ID manager. Leaking memory. |
The ACE failed to destroy memory space for ID management. |
iosxe-ipsec |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
ACE-6-BOOTMSGINFO |
6-Information |
[chars]: boot info: [chars] |
The ACE completed booting but with a non-zero informational status code. This does not indicate an error and ACE will run normally. |
- |
"No action is necessary." |
|
ACE-6-CRASHDUMPEND |
6-Information |
[chars]: crashdump retrieval complete |
The ACE crashed and was rebooted. Upon reboot a crashdump file was detected and uploaded to the sup-bootflash filesystem. |
- |
"Report the crash and transfer the crashdump file to your technical" "support representative." |
|
ACE-6-INFO |
6-Information |
[chars]: [chars] |
This is informational message from ACE |
iosxe-ipsec |
"This is informational message from ACE. This occurs " "in normal operation." |
|
ACE-6-SWITCHOVER |
6-Information |
VPN-SM switchover: [dec]/[dec] has been [chars] [dec]/[dec] |
An negative acknowledge occured in the indicated control transaction. |
iosxe-ipsec |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
ACL1-5-LDP |
5-Notice |
5*ERRMSG_LIMIT_SLOW |
- |
- |
- |
|
ACL-3-UNEXPECTED_PKT_TYPE |
3-Error |
type [dec] int [dec] [chars]put |
ACL logging has encountered unexpected pkt type. |
cpp-ucode |
LOG_STD_ACTION |
|
ACL-3-UNEXPECTED_STATE |
3-Error |
type [dec] int [chars] [chars]put w0: 0x%p w1: 0x[hec] |
An error has occurred in the setup of ACL hardware. |
cpp-ucode |
LOG_STD_ACTION |
|
ACL-5-LDP |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
ACLMERGE-3-CUDDERROR |
3-Error |
A CUDD Library error was detected in [chars] |
An error was detected by the CUDD Library the ACL-Merge for this invokation has failed. This could result in more traffic being switched by software. The effect of this could be lower performance for the interface for which the merge failed. |
aclmerge |
"Copy and save this message. Report this to Engineering along with the ACL configuration of this device. Use Topic to search for a similar DDTS. If none found write a DDTS for this problem" |
|
ACLMERGE-3-CUDDWARN |
3-Error |
A CUDD Library warning message for interest in this event in [chars] |
Debug message only. No action required |
aclmerge |
"Copy and save this message. Report this to Engineering along with the ACL configuration of the device. This is just a debug message of interest to engineering to investigate the case why this happened" |
|
ACLMGR-2-NOMAP |
2-Critical |
Cannot create ACL Manager data structures for VLAN Map [chars] |
The ACL Manager could not allocate the data structures needed to describe a VLAN Map in a form that can be loaded into hardware. Probably caused by lack of free memory. |
firmware |
LOG_STD_REDUCE_ACTION |
|
ACLMGR-2-NOVLB |
2-Critical |
Cannot create memory block for VLAN [dec] |
The ACL Manager was unable to save per-VLAN information needed for its correct operation. Some per-interface features such as access groups or VLAN maps will not be configured correctly. |
firmware |
"Use a less complicated configuration that " "requires less memory." |
|
ACLMGR-2-NOVMR |
2-Critical |
Cannot generate hardware representation of access list [chars] |
There were insufficient resources available for generating a hardware representation of the access list. Either lack of available logical operation units or lack of memory can cause this problem. Logical operation units are needed when a match on TCP flags is specified or when any test other than eq that is: ne gt lt or range is |
firmware |
"Modify the ACL configuration to use fewer resources." |
|
ACLMGR-3-AUGMENTFAIL |
3-Error |
Augmenting of access-map [chars] on [chars] label [dec] failed |
The system ran out of CPU DRAM when attempting to merge internally required elements with the configured access maps. |
firmware |
LOG_STD_REDUCE_ACTION |
|
ACLMGR-3-FEATUREMISMATCH |
3-Error |
[chars] can not be supported with the image running on switch-[dec] |
A feature has been configured on the stack but can not be supported on one or more switches in the stack. This feature will continue to work on the rest of the switches that support it but will not be applied to the switches that can not support it. All other features continue to work as expected on the stack. |
firmware |
"Upgrade the software running on switches that " "can not support this feature. Upgrade to a " "software version that supports this feature." |
|
ACLMGR-3-IECPORTLABELERROR |
3-Error |
ACL labels are out-of-sync on interface [chars] label [dec] is not available on asic [dec] |
An internal software error has occurred. |
firmware |
LOG_STD_ACTION |
|
ACLMGR-3-INSERTFAIL |
3-Error |
Insert of access-map [chars] #[dec] into [chars] label [dec] failed |
The system ran out of CPU DRAM when trying to merge sections of an access map. |
firmware |
LOG_STD_REDUCE_ACTION |
|
ACLMGR-3-INTTABLE |
3-Error |
Not in truth table: VLMAP [dec] RACL [dec] Rtprot [dec] Mcb [dec] Feat [dec] |
An unrecoverable software error occurred while trying to merge the configured input features. |
firmware |
"show running-config" |
|
ACLMGR-3-INVALIDL4PORTINDEX |
3-Error |
Invalid L4 port array index while processing [chars] |
ACL Manager module received invalid value for L4 port array index. The problem can be due to memory corruption or bad system memory. |
firmware |
NACL_L4OP_ERROR |
|
ACLMGR-3-INVALIDPARAM |
3-Error |
Invalid [chars] [dec] encountered |
ACL Manager has encountered an invalid parameter value. |
firmware |
"show running-config" |
|
ACLMGR-3-MAXRECURSION |
3-Error |
Too many [dec] levels of recursion while merging ACLs code [dec]. |
The configuration is too complicated for the platform specific ACL merge code to support. Most likely cause is including too many separate access lists in a single VLAN map or policy map. |
firmware |
"Reduce the number IP or MAC access lists" " considered separately in any one VLAN or policy" |
|
ACLMGR-3-MERGEFAIL |
3-Error |
[chars] ACL merge error [dec] [chars] on [chars] label [dec] |
The ACL Manager was unable to complete the merge of the configured features into a form suitable for loading into the hardware. Packets potentially affected by this feature will be sent to the CPU for processing instead. The most likely cause is specifying an ACL that is too large or too complex for the system to handle. |
firmware |
"Try specifying a smaller and less complicated " "configuration." |
|
ACLMGR-3-NOLABEL |
3-Error |
Cannot allocate [chars] label for vlan-id [dec] |
The ACL Manager was unable to allocate a label for the features on this interface. This means that the hardware cannot be programmed to implement the features and packets for this interface will be filtered in software. There is a limit of 256 labels per direction. |
firmware |
"Allocate more space to the relevant section " "of the TCAM and reboot or else use a simpler " "configuration. Use the same ACLs on multiple " "interfaces if possible." |
|
ACLMGR-3-OUTTTABLE |
3-Error |
Not in truth table: RACL [dec] VLMAP [dec] |
An unrecoverable software error occurred while trying to merge the configured output features. |
firmware |
"show running-config" |
|
ACLMGR-3-PACLTTABLE |
3-Error |
Not in truth table: IPSrcGrd [dec] PACL [dec] Rtprot [dec] |
An unrecoverable software error occurred while trying to merge the configured port acl features. |
firmware |
"show running-config" |
|
ACLMGR-3-QOSTTABLE |
3-Error |
Not in truth table: ACL [dec] in map action [dec] |
A software error occurred while trying to merge a QoS Policy Map |
firmware |
"show running-config" |
|
ACLMGR-3-UNKNOWNACTION |
3-Error |
Unknown VMR access group action 0x[hec] |
An internal software error has occurred. |
firmware |
LOG_STD_ACTION |
|
ACLMGR-3-UNKNOWNL4OPERATION |
3-Error |
Unknown L4 operation 0x[hec] |
ACL Manager module received invalid value for L4 operation. The problem can be due to memory corruption or bad system memory. |
firmware |
NACL_L4OP_ERROR |
|
ACLMGR-4-ACLTCAMFULL |
4-Warning |
[chars]ACL TCAM Full. Software Forwarding packets on [chars] label [dec] on [chars] [chars] |
The ACL configuration is too large to fit in the platform -specific ACL TCAM table. |
firmware |
"Simplify the ACLs applied to interfaces or reduce" " their number." |
|
ACLMGR-4-ACLTCAMFULL |
4-Warning |
ACL TCAM Full. [chars] [chars] [chars] [chars] |
The ACL configuration is too large to fit in the platform -specific ACL TCAM table. |
firmware |
"Simplify the ACLs applied to interfaces or reduce" " their number." |
|
ACLMGR-4-RELOADED |
4-Warning |
Reloading [chars] [chars] label [dec] [chars] [chars]feature |
The ACL Manager was able to fit more of the configured features on this label into the hardware. One or more features had previously been unloaded because of lack of space. |
firmware |
LOG_STD_NO_ACTION |
|
ACLMGR-4-RELOADEDFSPAN |
4-Warning |
Reloading [chars] session [dec] [chars] feature |
The ACL Manager was able to fit more of the configured Flow based SPAN features on this session into the hardware. One or more features had previously been unloaded because of lack of space. |
firmware |
LOG_STD_NO_ACTION |
|
ACLMGR-4-UNLOADING |
4-Warning |
Unloading [chars] [chars] label [dec] [chars] [chars]feature |
The ACL Manager was unable to fit the complete configuration into the hardware so some features will have to be applied in software. This prevents some or all of the packets in a VLAN/port from being forwarded in hardware and requires them to be forwarded by the CPU. Multicast packets may be dropped entirely instead of being forwarded. |
firmware |
"Allocate more space to the relevant section " "of the TCAM and reboot or else use a simpler " "configuration. Use the same ACLs on multiple " "interfaces if possible." |
|
ACLMGR-4-UNLOADINGFSPAN |
4-Warning |
Unloading [chars] session [dec] [chars] feature |
The ACL Manager was unable to fit the complete Flow based SPAN configuration into the hardware so this feature has been temporarily disabled for the given session. |
firmware |
"Allocate more space to the ACL section of the " "TCAM by choosing an SDM template with more ACL " "TCAM space and reboot the switch. You may also " "use a simpler ACL configuration and/or use the " "same ACLs on multiple interfaces if possible." |
|
ACR-1-ISSU_NOMEMORY |
1-Alert |
msgtxt_nomemory |
The requested operation could not be accomplished because of a low\n\ memory condition. |
ACR_DDTS_COMPONENT |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
ACR-3- ACRIFADD |
3-Error |
[chars] interface add failed for ACR group [dec]. |
Addition of interface to ACR group failed |
ACR_DDTS_COMPONENT |
"Get the output of \"show acr all \" immediately after this error." "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
ACR-3- ACRIFDEL |
3-Error |
[chars] interface del failed for ACR group [dec]. |
Delete of interface from ACR group failed |
ACR_DDTS_COMPONENT |
"Get the output of \"show acr all \" immediately after this error." "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
ACR-3- ACRPVCDISABLE |
3-Error |
PVC Disable failed for VCD= [dec] on [chars] interface of ACR interface [chars]. |
PVC disable failed on ACR physical interface. |
ACR_DDTS_COMPONENT |
"Get the output of \"show acr group \" and \"show acr group <> detail\" " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
ACR-3- ACRVPDISABLE |
3-Error |
VP Disable failed for VPI= [dec] on [chars] interface of ACR interface [chars]. |
VP disable failed on ACR physical interface. |
ACR_DDTS_COMPONENT |
"Get the output of \"show acr group \" and \"show acr group <> detail\" " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
ACR-3- ACRVPENABLE |
3-Error |
VP Enable failed for VPI= [dec] on [chars] interface of ACR interface [chars]. |
VP enable failed on ACR physical interface. |
ACR_DDTS_COMPONENT |
"Get the output of \"show acr group \" and \"show acr group <> detail\" " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
ACR-3-ISSU_SENDFAILED |
3-Error |
\nACR ISSU: send message failed rc = [dec]\n |
The sending of a message has failed. |
ACR_DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
ACR-4-ISSU_INCOMPATIBLE |
4-Warning |
\nacr-issu-compat: returned FALSE |
The compatibility checking has failed |
ACR_DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
ACR-4-ISSU_XFORM |
4-Warning |
\n[chars]: failed rc=[chars] |
The transform has failed. |
ACR_DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
ACR-6- ACRPVCADD |
6-Information |
PVC creation failed for VCD= [dec] on [chars] interface of ACR interface [chars]. |
PVC creation attempt failed on ACR physical interface. |
ACR_DDTS_COMPONENT |
"If message is seen continuously get the output of \"show acr group \" \n\ and \"show acr group <> detail\" " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
ACR-6- ACRPVCDEL |
6-Information |
PVC deletion failed for VCD= [dec] on [chars] interface of ACR group [chars]. |
PVC deletion attempt failed on ACR physical interface. |
ACR_DDTS_COMPONENT |
"If message is seen continuously get the output of \"show acr group \" \n\ and \"show acr group <> detail\" " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
ACR-6- ACRPVCENABLE |
6-Information |
PVC Enable failed for VCD= [dec] on [chars] interface of ACR interface [chars]. |
PVC enable attempt failed on ACR physical interface. |
ACR_DDTS_COMPONENT |
"If message is seen continuously get the output of \"show acr group \" \n\ and \"show acr group <> detail\" " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
ACR-6- ACRVPADD |
6-Information |
VP creation failed for VPI= [dec] on [chars] interface of ACR group [chars]. |
VP creation attempt failed on ACR physical interface. |
ACR_DDTS_COMPONENT |
"If message is seen continuously get the output of \"show acr group \" \n\ and \"show acr group <> detail\" " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
ACR-6- ACRVPDEL |
6-Information |
PVC deletion failed for VPI= [dec] on [chars] interface of ACR group [chars]. |
VP deletion attempt failed on ACR physical interface. |
ACR_DDTS_COMPONENT |
"If message is seen continuously get the output of \"show acr group \" \n\ and \"show acr group <> detail\" " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
ADDR_PROC-4-LCON |
4-Warning |
ERRMSG_NOFLAGS |
- |
- |
- |
|
ADDRQ-4-LCON |
4-Warning |
ERRMSG_NOFLAGS |
- |
- |
- |
|
ADJ_WALK_ERR-2-MPLS_TE |
2-Critical |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
ADJ-3-ADJ_XKEYS |
3-Error |
Adj extended keys error [chars]: [chars] |
An initialization error occurred for extended keys. |
- |
LOG_STD_ACTION |
|
ADJ-3-ADJGENALLOCATEFAIL |
3-Error |
Failed to allocate memory [chars] |
An internal software error occurred. This is probably because not enough memory was available. |
- |
LOG_STD_ACTION |
|
ADJ-3-ADJGENDEALLOCATEFAIL |
3-Error |
Failed to deallocate memory [chars] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
ADJ-3-ADJMGRALLOCATEFAIL |
3-Error |
Failed to allocate an adjacency summary event block |
An internal software error occurred. This is probably because not enough memory was available. |
- |
LOG_STD_ACTION |
|
ADJ-3-ADJMGRDISPATCHFAIL |
3-Error |
Failed to enqueue an adjacency summary event block |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
ADJ-3-ADJMGRREFRESHFAIL |
3-Error |
Failed to dispatch a refresh adjacency summary event |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
ADJ-3-ADJSTACK2 |
3-Error |
Adj stack2 error [chars]: [chars] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
ADJ-3-ALLOCATEFAIL |
3-Error |
Failed to allocate an adjacency |
An internal software error occurred. This is probably because not enough memory was available. |
- |
LOG_STD_ACTION |
|
ADJ-3-ALLOCATEONDOWN |
3-Error |
Allocating adj when adj subsystem down |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
ADJ-3-BADADDRLEN |
3-Error |
Zero address length detected distributing adj [chars] |
An internal software error occurred. An attempt to reference an adjacency with an unsupported address type has been made. |
- |
LOG_STD_ACTION |
|
ADJ-3-BADADDRTYPE |
3-Error |
Using an unsupported address type [dec] when trying to add/delete/modify/find an adjacency |
An internal software error occurred. An attempt to reference an adjacency with an unsupported address type has been made. |
- |
LOG_STD_ACTION |
|
ADJ-3-BADLINKTYPE |
3-Error |
Using an unsupported linktype [chars] when trying to add/delete/modify/find an adjacency |
An internal software error occurred. An attempt to reference an adjacency with an unsupported address type has been made. |
- |
LOG_STD_ACTION |
|
ADJ-3-BADMACALIGN |
3-Error |
adjacency mac string end [hec] not [chars] aligned |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
ADJ-3-BADMACALIGN2 |
3-Error |
Adjacency mac string for [chars] not byte aligned offset [hec] length [hec] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
ADJ-3-BADMAGIC |
3-Error |
adjacency [chars] is followed by bad magic |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
ADJ-3-BOARDENCAP |
3-Error |
Generation of encapsulation string for [chars] failed |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
ADJ-3-BROKERINITFAIL |
3-Error |
Failed to initialise adjacency RP broker facility |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
ADJ-3-BUNDLES |
3-Error |
Adj bundles: [chars] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
ADJ-3-CONNID_INCOMPATIBLE_ID |
3-Error |
Connection id [dec] could not be transformed: [chars] |
A connection id could not be transformed from a lower revision. |
- |
LOG_STD_ACTION |
|
ADJ-3-CONNID_INVALID |
3-Error |
Connection id [dec] not recognized [chars] |
A supplied connection id did not exist in the managed id database. |
- |
LOG_STD_ACTION |
|
ADJ-3-CONNID_INVALID_KEY |
3-Error |
Unexpected connection-id parameter: Expecting [chars] when encoding [chars] |
An application has provided an invalid key for computing a connection-id. |
- |
LOG_STD_ACTION |
|
ADJ-3-CONNID_POOL_EXHAUSTED |
3-Error |
Pool of connection ids is fully utilized. It may not be possible to encode new sets of extended keys. |
Either there are too many unique sets of extended keys in the system or ids have been leaking. |
- |
LOG_STD_ACTION |
|
ADJ-3-CONNID_TREE_MISMATCH |
3-Error |
Supplied connid [dec] and extended keys [chars] do not match |
An adjacency has a connection id and extended keys mapping that doesn't match what's in the managed connection id database. This will likely result in a rejected adjacency update or sync. |
- |
LOG_STD_ACTION |
|
ADJ-3-CONNID_TREE_OP_FAIL |
3-Error |
Tree [chars] failed for [chars] for id [dec] connid [dec] |
A tree operation failed for the connection-id manager. An inability to correctly construct a tree will have negative consequences for the system. |
- |
LOG_STD_ACTION |
|
ADJ-3-DBGFILTERALLOCATEFAIL |
3-Error |
Failed to allocate an adjacency debug filter block |
An internal software error occurred. This is probably because not enough memory was available. |
- |
LOG_STD_ACTION |
|
ADJ-3-ILALLOCATEFAIL |
3-Error |
Failed to allocate an adjacency interest list subblock |
An internal software error occurred. This is probably because not enough memory was available. |
- |
LOG_STD_ACTION |
|
ADJ-3-ILDEALLOCATEFAIL |
3-Error |
Failed to deallocate an adjacency interest list subblock |
An internal software error occurred. This is probably because not enough memory was available. |
- |
LOG_STD_ACTION |
|
ADJ-3-ILINITFAIL |
3-Error |
Failed to initialise adjacency interest list facility |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
ADJ-3-ILLEGALARGS |
3-Error |
Illegal arguments - [chars] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
ADJ-3-ISSU_REG |
3-Error |
ISSU client [chars] [dec] entity [dec] failed ISSU registration: [chars] |
ISSU negotiation failed for this XDR client. |
- |
"This error indicates a coding problem. It is an error that will occur" "every time this image is run and requires a code change to fix it." |
|
ADJ-3-LCXDRCLIENT |
3-Error |
Adjacency distribution client: [chars] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
ADJ-3-MACOVERFLOW |
3-Error |
Adjacency mac address for [chars] overflowed by [dec] bytes |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
ADJ-3-MACSTRING_PD_ERROR |
3-Error |
Platform request for header type [chars] from adjacency [chars] [chars][chars] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
ADJ-3-NOFIBIDB |
3-Error |
CEF Interface not found - [chars] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
ADJ-3-RPXDRCLIENT |
3-Error |
Adjacency distribution client: [chars] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
ADJ-3-SBINITFAIL |
3-Error |
Failed to initialise adjacency subblock facility |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
ADJ-3-STATETRANSITION |
3-Error |
Unexpected state transition from [chars] to [chars] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
ADJ-3-XKEYS_XDR_LEN |
3-Error |
Expected [dec] bytes of extended adjacency keys: decoded [dec] bytes |
The XDR message was incorrectly formatted and may contain bad xkey data. |
- |
LOG_STD_ACTION |
|
ADJ-5-ADJISSUINCOMPATIBLE |
5-Notice |
All or part of adjacency message for [chars] not sent to incompatible CEF instance for [chars] |
The adjacency is not distributed in whole to the remote CEF instance. This may impact traffic forwarding on remote CEF instance |
- |
LOG_STD_NO_ACTION |
|
ADJ-5-PARENT |
5-Notice |
Midchain parent maintenance for [chars] - [chars] |
A midchain adjacency failed to stack onto output chain because a loop was detected. Traffic through the adjacency will be dropped until the adj is restacked. This condition is typically transient and is rectified by the control plane driving stacking. E.g. if an ip tunnel destination resolves through the tunnel transiently this message would appear. The situation would be rectified either by learning the tunnel destination through an interface other than the tunnel itself or by bringing the tunnel down. Monitor 'show adjacency internal' to determine if the problem has been resolved. |
- |
LOG_STD_NO_ACTION |
|
ADJ-5-RESOLVE_REQ_FAIL |
5-Notice |
Adj resolve request failed for [chars] on [chars] |
The source e.g. ARP or ND could not resolve the address. |
- |
LOG_STD_ACTION |
|
ADV-4-LDP |
4-Warning |
ERRMSG_NOFLAGS |
- |
- |
- |
|
AGGMGR-0-NO_SPACE |
0-Emergency |
No space left for creator \[chars]\ to add data item to agg list items [dec] max [dec] remaining [dec] |
An attempt was made to add an item to an aggregation list that had just been successfully created but for some reason the add failed. This situation should never occur. If it does occur then it is the result of a program error which would be found during development and considered an internal error. There is no work around. |
cosmos |
LOG_STD_ACTION |
|
AIP-3-AIPFAILSETUPVC |
3-Error |
[chars] Failed to setup vc [dec] Cause: [chars] |
- |
- |
- |
|
AIP-3-AIPFAILSETUPVCAVG |
3-Error |
Interface [chars] Failed to setup vc [dec] Cause: [chars] Expected range [[dec] .. [dec]]Kbps for AIP Average Rate Metering. Average Rate=Peak Rate= [dec] Kbps turns Average Rate Metering OFF |
A software or hardware error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
ALARM_PERSISTENCY-3-ALARM_CHUNK_INFO_FAIL |
3-Error |
[chars] |
Failed to create the chunk-pool for the persistent alarm info |
asr900-lotr-im |
LOG_STD_ACTION |
|
ALARM_PERSISTENCY-3-ALARM_CHUNK_QUEUE_FAIL |
3-Error |
[chars] |
Failed to create the chunk-pool for the persistent alarm queue |
asr900-lotr-im |
LOG_STD_ACTION |
|
ALARM_PERSISTENCY-3-ALARM_INFO_CHUNK_DESTROY_FAIL |
3-Error |
Failed to destroy [chars] chunk pool |
Failed to destroy a chunk pool |
asr900-lotr-im |
LOG_STD_ACTION |
|
ALARM_PERSISTENCY-3-ALARM_INFO_FILE_CREATE_ERROR |
3-Error |
Failed to create [chars]/[chars] file error:[chars] |
Failed to create persistent_alarm_log file |
asr900-lotr-im |
LOG_STD_ACTION |
|
ALARM_PERSISTENCY-3-ALARM_INFO_FILE_OPEN_ERROR |
3-Error |
Failed to open [chars]/[chars] file error:[chars] |
Failed to open persistent_alarm_log file |
asr900-lotr-im |
LOG_STD_ACTION |
|
ALARM_PERSISTENCY-3-ALARM_INFO_FILE_WRITE_ERROR |
3-Error |
Failed to write to [chars]/[chars] file actual:[dec] written:[dec] error:[chars] |
Failed to open persistent_alarm_log file |
asr900-lotr-im |
LOG_STD_ACTION |
|
ALARM_PERSISTENCY-3-ALARM_INFO_NULL |
3-Error |
Persistent alarm queue alarm info is NULL |
alarm_info of the persistence queue is NULL |
asr900-lotr-im |
LOG_STD_ACTION |
|
ALARM_PERSISTENCY-3-ALARM_INFO_PROCESS_FAIL |
3-Error |
Failed to create mcprp_spa_persistence_logger process |
Failed to create mcprp_spa_persistence_logger process |
asr900-lotr-im |
LOG_STD_ACTION |
|
ALARM_PERSISTENCY-3-ALARM_PROFILE_NULL |
3-Error |
[chars] |
Alarm profile is enabled with a wrong profile name |
- |
LOG_STD_ACTION |
|
ALARM_PERSISTENCY-3-ALARM_QUEUE_NULL |
3-Error |
Persistent alarm queue info is NULL |
alarm_info of the persistence queue is NULL |
asr900-lotr-im |
LOG_STD_ACTION |
|
ALARM_PERSISTENCY-3-NULL_DATA_STRUCTURE |
3-Error |
[chars] is NULL |
Data-structure is NULL |
asr900-lotr-im |
LOG_STD_ACTION |
|
ALARM_PERSISTENCY-6-ALARM_CHUNK_INFO_CREATED |
6-Information |
[chars] |
Created the chunk-pool for the persistenct alarm info |
- |
LOG_STD_NO_ACTION |
|
ALARM_PERSISTENCY-6-ALARM_CHUNK_QUEUE_CREATED |
6-Information |
[chars] |
Created the chunk-pool for the persistent alarm queue |
- |
LOG_STD_NO_ACTION |
|
ALARM_PERSISTENCY-6-ALARM_INFO_FILE_CREATED |
6-Information |
Successfully created [chars]/[chars] file |
Successfully created alarm_persistency file |
- |
LOG_STD_NO_ACTION |
|
ALARM_PERSISTENCY-6-ALARM_INFO_FILE_ROTATED |
6-Information |
Switching to [chars] file \nafter writing [dec] records to [chars] file |
Switched to other file after reaching a specified limit |
- |
LOG_STD_NO_ACTION |
|
ALARM_PERSISTENCY-6-ALARM_INFO_PROCESS_CREATE |
6-Information |
created mcprp_spa_persistence_logger process:[dec] |
Created mcprp_spa_persistence_logger process |
- |
LOG_STD_NO_ACTION |
|
ALARM_PERSISTENCY-6-ALARM_RECORDS_FULL |
6-Information |
Persistent alarm info queue is full with [dec] elements |
persistent alarm_records in the persistence queue are full |
- |
LOG_STD_NO_ACTION |
|
ALARM-3-CLEAR |
3-Error |
[chars] [chars] [chars] [chars] [chars] |
- |
- |
"" |
|
ALARM-3-CLEAR |
3-Error |
[chars] [chars] [chars] [chars] [chars] |
- |
- |
"" |
|
ALARM-3-NOMEM |
3-Error |
OUT of Memory: [chars] |
- |
- |
"" |
|
ALARM-3-NOMEM |
3-Error |
OUT of Memory: [chars] |
- |
- |
"" |
|
ALARM-6-DEFAULT_ALARM_PROFILE |
6-Information |
[chars] |
Telcordia profile enable or disable information |
- |
LOG_STD_NO_ACTION |
|
ALARM-6-ENTITY_INFO |
6-Information |
[chars] [chars] [chars] [chars] [chars] |
Entity alarm assertion or deassertion information. |
- |
LOG_STD_NO_ACTION |
|
ALARM-6-ENTITY_INFO |
6-Information |
[chars] [chars] [chars] [chars] [chars] |
Entity alarm assertion or deassertion information. |
- |
LOG_STD_NO_ACTION |
|
ALG_COM-3-ALG_COND_DEBUG_REG_FAILED |
3-Error |
[chars] |
- |
- |
- |
|
ALG_COM-3-ALG_REGISTER_FAILED |
3-Error |
[dec] |
ALG registration failed. |
cpp-ucode |
LOG_STD_ACTION |
|
ALG_COM-3-CHUNK_CREATE_FAIL |
3-Error |
[chars] |
A request to create a chunk failed |
cpp-ucode |
LOG_STD_ACTION |
|
ALG_COM-3-CHUNK_EXTEND_FAIL |
3-Error |
[chars] |
A request to create a chunk failed |
cpp-ucode |
LOG_STD_ACTION |
|
ALG_COM-3-IPC_INIT_FAILED |
3-Error |
[dec] |
IPC handler initialization failed. |
cpp-ucode |
LOG_STD_ACTION |
|
ALG_PROXY-3-PROXY_IPC_FAIL |
3-Error |
rc= [dec] |
The ALG proxy has experienced a failure when trying to send an IPC |
cpp-ucode |
LOG_STD_ACTION |
|
ALG_PROXY-3-PROXY_MEM_EXTEND_FAILED |
3-Error |
ALG IPC subtype: [dec] |
Extending memory failed. |
cpp-ucode |
LOG_STD_ACTION |
|
ALG_PROXY-3-PROXY_MEM_REQ_FAILED |
3-Error |
ALG IPC subtype: [dec] |
Requesting more memory failed. |
cpp-ucode |
LOG_STD_ACTION |
|
ALG_PROXY-4-PROXY_IPC_INVALID_MSG |
4-Warning |
[dec] |
Invalid IPC message subtype. |
cpp-ucode |
LOG_STD_ACTION |
|
ALG_PROXY-4-PROXY_IPC_INVALID_MSG_LEN |
4-Warning |
[dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Invalid IPC message length. |
cpp-ucode |
LOG_STD_ACTION |
|
ALG-3-ALG_REGISTRY_RC |
3-Error |
An ALG registry call failed with rc[chars] |
The return code from an ALG registry call indicates an\n\ error. |
alg |
LOG_STD_ACTION |
|
ALG-3-API_FAILED |
3-Error |
NULL |
A call to the API of another component has indicated an\n\ error. |
alg |
LOG_STD_ACTION |
|
ALG-3-BAD_MAGIC |
3-Error |
Invalid magic number%#10x |
An internal data structure is corrupt. |
alg |
LOG_STD_ACTION |
|
ALG-3-EEXIST |
3-Error |
NULL |
An item unexpectedly exists already. |
alg |
LOG_STD_ACTION |
|
ALG-3-EINVAL |
3-Error |
NULL |
An unexpected input value to a function was incorrect |
alg |
LOG_STD_ACTION |
|
ALG-3-ENOENT |
3-Error |
NULL |
A lookup failed unexpectedly. |
alg |
LOG_STD_ACTION |
|
ALG-3-ENOMEM |
3-Error |
Memory allocation failed |
An attempt to allocae memory has failed. |
alg |
LOG_STD_ACTION |
|
ALG-3-INIT_FAILED |
3-Error |
An initialization failed rc[chars] |
- |
- |
- |
|
ALG-3-RUNAWAY_LOOP |
3-Error |
NULL |
A loop has exceeded the expected number of iterations. |
alg |
LOG_STD_ACTION |
|
ALG-3-UNINITIALIZED |
3-Error |
ALG feature is not properly initialized |
A function call was made when the system was not properly\n\ initialized. |
alg |
LOG_STD_ACTION |
|
ALIGN-3-CORRECT |
3-Error |
Alignment correction made at [chars] [chars]ing 0x[hec] |
A software component within the router needs memory optimization. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
ALIGN-3-CORRECT |
3-Error |
Alignment correction made at 0x[hec] [chars]ing 0x[hec] |
A software component within the router needs memory optimization. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
ALIGN-3-CORRECT_SO |
3-Error |
Alignment correction made at [chars] [chars]ing [chars] |
A software component within the router needs memory optimization. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
ALIGN-3-FULL |
3-Error |
Alignment log is full - no new entries will be recorded |
The router identified more software components in need of memory\n\ optimization than it can record. |
cpu |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
ALIGN-3-FULL |
3-Error |
Alignment log is full - no new entries will be recorded |
The router identified more software components in need of memory\n\ optimization than it can record. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
ALIGN-3-READEXCEPTION |
3-Error |
Warning : read accees failed at [chars] still continuing \n |
In ls1010 read access failures do not make the box reload. They can \n\ be caused by either a bad register value in the asp ver 3.3 or earlier\n\ or a real problem in the hardware |
- |
"If the ASP version is 3.3 or more report it to your\n\ technical support representative." |
|
ALIGN-3-RO_WRITE |
3-Error |
Spurious memory access made at [chars] writing to 0x[hec] |
An attempted but illegal access to a low memory address within a software component in the router has been temporarily blocked. |
cpu |
"Copy the error message exactly as it appears on the console or in the " "system log. Issue the <CmdBold>show alignment<noCmdBold> command to " "gather data that may help identify the nature of the error. If you " "cannot determine the nature of the error from the error message text " "or from the <CmdBold>show alignment<noCmdBold> output call your " "Cisco technical support representative and provide the representative " "with the gathered information." |
|
ALIGN-3-SPURIOUS |
3-Error |
Spurious memory access made at [chars] reading 0x[hec] |
An attempted but illegal access to a low memory address within a software component in the router has been temporarily blocked. |
cpu |
"Copy the error message exactly as it appears on the console or in the " "system log. Issue the <CmdBold>show alignment<noCmdBold> command to " "gather data that may help identify the nature of the error. If you " "cannot determine the nature of the error from the error message text " "or from the <CmdBold>show alignment<noCmdBold> output call your " "Cisco technical support representative and provide the representative " "with the gathered information." |
|
ALIGN-3-SPURIOUS |
3-Error |
Spurious memory access made at [chars] reading 0x[hec] |
An attempted but illegal access to a low memory address within a software component in the router has been temporarily blocked. |
- |
"Copy the error message exactly as it appears on the console or in the " "system log. Issue the <CmdBold>show alignment<noCmdBold> command to " "gather data that may help identify the nature of the error. If you " "cannot determine the nature of the error from the error message text " "or from the <CmdBold>show alignment<noCmdBold> output call your " "Cisco technical support representative and provide the representative " "with the gathered information." |
|
ALIGN-3-SPURIOUS |
3-Error |
Spurious memory access made at 0x[hec] reading 0x[hec] |
An attempted but illegal access to a low memory address within a software component in the router has been temporarily blocked. |
- |
"Copy the error message exactly as it appears on the console or in the " "system log. Issue the <CmdBold>show alignment<noCmdBold> command to " "gather data that may help identify the nature of the error. If you " "cannot determine the nature of the error from the error message text " "or from the <CmdBold>show alignment<noCmdBold> output call your " "Cisco technical support representative and provide the representative " "with the gathered information." |
|
ALIGN-3-SPURIOUS |
3-Error |
Spurious memory access made at [chars] reading 0x[hec] |
An attempted but illegal access to a low memory address within a software component in the router has been temporarily blocked. |
- |
"Copy the error message exactly as it appears on the console or in the " "system log. Issue the <CmdBold>show alignment<noCmdBold> command to " "gather data that may help identify the nature of the error. If you " "cannot determine the nature of the error from the error message text " "or from the <CmdBold>show alignment<noCmdBold> output call your " "Cisco technical support representative and provide the representative " "with the gathered information." |
|
ALIGN-3-SPURIOUS_SO |
3-Error |
Spurious memory access made at [chars] reading [chars] |
An attempted but illegal access to a low memory address within a software component in the router has been temporarily blocked. |
- |
"Copy the error message exactly as it appears on the console or in the " "system log. Issue the <CmdBold>show alignment<noCmdBold> command to " "gather data that may help identify the nature of the error. If you " "cannot determine the nature of the error from the error message text " "or from the <CmdBold>show alignment<noCmdBold> output call your " "Cisco technical support representative and provide the representative " "with the gathered information." |
|
ALIGN-3-TRACE |
3-Error |
-Traceback= [chars] |
A trace that shows where the previous ALIGN error occurred. |
cpu |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
ALIGN-3-TRACE |
3-Error |
-Traceback= [chars] |
A trace that shows where the previous ALIGN error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
ALIGN-3-TRACE |
3-Error |
-Traceback= %08x %08x %08x %08x %08x %08x %08x %08x |
A trace that shows where the previous ALIGN error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
ALIGN-3-TRACE |
3-Error |
-Traceback= [chars] |
A trace that shows where the previous ALIGN error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
ALIGN-3-TRACE_SO |
3-Error |
-Traceback= [chars] |
A trace that shows where the previous ALIGN error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
ALIGN-3-TRACEX |
3-Error |
[chars] |
A trace that shows where the previous ALIGN error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
ALIGN-3-TRACEX |
3-Error |
[chars] |
A trace that shows where the previous ALIGN error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
ALLOC-3-ICPM |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
ALLOC-3-LCON |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
ALPS-3-ALPSFAIL |
3-Error |
ALPS: Assertion failed: [chars] |
An internal software error has occurred. |
- |
LOG_STD_ACTION |
|
ALPS-3-ASCU_FSM_ERR |
3-Error |
ASCU %02x on interface [chars] has an internal FSM error. |
Internal error. |
- |
"Turn debug flags on capture traces & contact Cisco technical support" |
|
ALPS-3-ASCU_IF_STUCK |
3-Error |
Polling for ASCU %02x on interface [chars] is stalled. |
The polling mechanism for an ALPS interface has become stuck. |
- |
LOG_STD_NO_ACTION |
|
ALPS-5-ASCU_DISABLED_ASCU_STUCK |
5-Notice |
ASCU %02x on interface [chars] has been disabled since 4 consecutive messages were received from same SID. |
An ALPS ASCU has been automatically disabled. |
- |
LOG_STD_NO_ACTION |
|
ALPS-5-ASCU_DOWN |
5-Notice |
ASCU %02x on interface [chars] is down. |
An ALPS ASCU has transitioned from up to down. |
- |
LOG_STD_NO_ACTION |
|
ALPS-5-ASCU_UP |
5-Notice |
ASCU %02x on interface [chars] is up. |
An ALPS ASCU has transitioned from down to up. |
- |
LOG_STD_NO_ACTION |
|
ALPS-5-CIRCUIT_CLOSED |
5-Notice |
Circuit [chars] changed state to closed rsn = [chars]. |
An ALPS circuit has tranistioned from open to closed |
- |
LOG_STD_NO_ACTION |
|
ALPS-5-CIRCUIT_OPEN |
5-Notice |
Circuit [chars] changed state to open. |
An ALPS circuit has transitioned from closed to open. |
- |
LOG_STD_NO_ACTION |
|
ALPS-5-PEER_CLOSED |
5-Notice |
Peer [inet] [chars] changed state to closed. |
An ALPS peer connection is now closed. |
- |
LOG_STD_NO_ACTION |
|
ALPS-5-PEER_CLOSED_DYNAMIC_INACTIVITY |
5-Notice |
Peer [inet] [chars] closed due to inactivity. |
An ALPS peer connection is now closed due to inactivity. |
- |
LOG_STD_NO_ACTION |
|
ALPS-5-PEER_CONN_ID_CHANGE |
5-Notice |
Peer [inet] [chars] ID modified to [inet] [chars]. |
An ALPS peer connection identifier has changed. |
- |
LOG_STD_NO_ACTION |
|
ALPS-5-PEER_OPEN |
5-Notice |
Peer [inet] [chars] changed state to open. |
An ALPS peer connection is now open. |
- |
LOG_STD_NO_ACTION |
|
ALPS-6-CIRCUIT_ASCU_REJECT |
6-Information |
Circuit [chars] received a Circuit Open Confirm with a list of rejected ascus |
An ALPS circuit sent a Circuit Open Request message and\n\ received a Circuit Open Confirm with a list of rejected ascus. |
- |
LOG_STD_NO_ACTION |
|
ALPS-6-CIRCUIT_BUSY_START |
6-Information |
Circuit [chars] has entered a congested state. |
An ALPS circuit is experiencing congestion. |
- |
LOG_STD_NO_ACTION |
|
ALPS-6-CIRCUIT_OPEN_FAILED |
6-Information |
Circuit [chars] received a Circuit Open Failed message rsn = [chars]. |
An ALPS circuit sent a Circuit Open Request message and\n\ received a Circuit Open Failed message as a reply. |
- |
LOG_STD_NO_ACTION |
|
ALPS-6-CIRCUIT_UPDATE_FAILED |
6-Information |
Circuit [chars] received a Circuit Open Failed message rsn = [chars]. |
An ALPS circuit sent a Circuit Update message and\n\ received a Circuit Open Failed message as a reply. |
- |
LOG_STD_NO_ACTION |
|
ALPS-6-CIRCUIT_X25_VC_STUCK |
6-Information |
Host unresponsive on X.25 VC for circuit [chars] |
The X.25 or EMTOX host is not advancing the transmit window\n\ for extended periods of time. This may be indicative of a\n\ temporary problem with the host application. An X.25 Reset \n\ is sent to reset the transmit and receive windows to\n\ allow communication to proceed. |
- |
"None" |
|
ALPS-6-PEER_BUSY_END |
6-Information |
Peer [inet] [chars] has exited a congested state. |
An ALPS peer connection is no longer experiencing congestion. |
- |
LOG_STD_NO_ACTION |
|
ALPS-6-PEER_BUSY_START |
6-Information |
Peer [inet] [chars] has entered a congested state. |
An ALPS peer connection is experiencing congestion. |
- |
LOG_STD_NO_ACTION |
|
ALPS-6-PEER_OPEN_FAIL |
6-Information |
Peer [inet] [chars] open failed rsn = [chars] |
An ALPS peer connection attempted to open but failed to open. |
- |
LOG_STD_NO_ACTION |
|
ALPS-7-CIRCUIT_BUSY_END |
7-Debug |
Circuit [chars] has exited a congested state. |
An ALPS circuit is no longer experiencing congestion. |
- |
LOG_STD_NO_ACTION |
|
ALPS-7-CIRCUIT_DROPS_CKT_DISABLED |
7-Debug |
Threshold exceeded for circuit disabled drops for circuit [chars] |
The number of ALPS circuit drops due to circuit disabled \n\ exceeds the ALPS circuit threshold value. |
- |
LOG_STD_NO_ACTION |
|
ALPS-7-CIRCUIT_DROPS_INVALID_ASCU |
7-Debug |
Threshold exceeded for invalid ASCU drops for circuit [chars] |
The number of ALPS circuit drops due to invalid ASCU identifier \n\ exceeds the ALPS circuit threshold value. |
- |
LOG_STD_NO_ACTION |
|
ALPS-7-CIRCUIT_DROPS_LIFETIME_EXPIRED |
7-Debug |
Threshold exceeded for lifetime timer expiration drops for circuit [chars] |
The number of ALPS circuit drops due to lifetime timer \n\ expiration exceeds the ALPS circuit threshold value. |
- |
LOG_STD_NO_ACTION |
|
ALPS-7-CIRCUIT_DROPS_QUEUE_OVERFLOW |
7-Debug |
Threshold exceeded for queue overflow drops for circuit [chars] |
The number of ALPS circuit drops due to queue overflow \n\ exceeds the ALPS circuit threshold value. |
- |
LOG_STD_NO_ACTION |
|
ALPS-7-CIRCUIT_DROPS_VC_RESET |
7-Debug |
Threshold exceeded for X.25 VC Reset drops for circuit [chars] |
The number of ALPS circuit drops due to X.25 VC Reset \n\ exceeds the ALPS circuit threshold value. |
- |
LOG_STD_NO_ACTION |
|
ALPS-7-PEER_DROPS_MAX_SIZE_EXCEEDED |
7-Debug |
Threshold exceeded for maximum size exceeded drops for peer [inet] [chars]. |
- |
- |
- |
|
ALPS-7-PEER_DROPS_PEER_UNREACHABLE |
7-Debug |
Threshold exceeded for peer unreachable peer drops for peer [inet] [chars]. |
- |
- |
- |
|
ALPS-7-PEER_DROPS_QUEUE_OVERFLOW |
7-Debug |
Threshold exceeded for TCP Queue overflow peer drops for peer [inet] [chars]. |
- |
- |
- |
|
ALPS-7-PEER_DROPS_VERSION_MISMATCH |
7-Debug |
Threshold exceeded for version mismatch peer drops for peer [inet] [chars]. |
- |
- |
- |
|
AMD79C971_FE-5-FAILED_SUSPEND |
5-Notice |
Failed to suspend the amd79c971 chip |
Failed to suspend the amd79c971 chip |
Mid-Ethernet |
LOG_STD_ACTION |
|
AMDP2_FE-1-DISCOVER |
1-Alert |
Only found [dec] interfaces on bay [dec] shutting down bay |
The software could not identify the interface card. |
pas-ethernet |
"Power down reseat the interface card " "and reboot. If the message recurs call your " "technical support representative for assistance." |
|
AMDP2_FE-1-INITFAIL |
1-Alert |
[chars] CSR[dec]=0x%04x |
The software failed to initialize/restart an Ethernet/Fast Ethernet interface. |
pas-ethernet |
"Try resetting the interface by doing a <CmdBold>shutdown <NoCmdBold> followed by " "a <CmdBold>no shutdown<NoCmdBold>. If the message recurs try reseating the Port " "Adaptor. If reseating also does not work call your technical " "support representative for assistance." |
|
AMDP2_FE-1-MEMERR |
1-Alert |
[chars] CSR[dec]=0x%04x |
The interface could not access system resources for a long time. This problem may occur under very heavy loads. |
pas-ethernet |
"The system should recover. No action is required. If the message " "recurs call your technical support representative for assistance." |
|
AMDP2_FE-1-NOMII |
1-Alert |
[chars] MII transceiver not connected |
The MII transceiver was disconnected while the MII port was selected. |
pas-ethernet |
"Connect the transceiver and enter the <bold> " "shut <nobold> and <bold> no shut <nobold> commands for the " "interface in the configuration menu." |
|
AMDP2_FE-1-NOTSUPPORTED |
1-Alert |
2FE PA not supported on NPE100 shutting down bay |
2FE PA is not supported on a 7200 with NPE100. |
pas-ethernet |
"NPE150 or better is needed for 2FE PA." |
|
AMDP2_FE-2-NOISL |
2-Critical |
[chars] hardware does not support ISL |
The interface cannot be configured as an ISL trunk. |
pas-ethernet |
"Check the configuration." |
|
AMDP2_FE-3-NOTAMDP2 |
3-Error |
Slot [dec] device ID seen as [hex] expected [hex] |
The software could not recognize the interface chips. |
pas-ethernet |
"Power down reseat the interface card and " "reboot. If the message recurs call your " "technical support representative for assistance." |
|
AMDP2_FE-3-OWNERR |
3-Error |
[chars] packet buffer pak=0x[hec] |
The software detected an error in descriptor ownership. |
pas-ethernet |
"Try a later version of the software. If the message " "recurs call your technical support representative " "for assistance." |
|
AMDP2_FE-3-SPURIDON |
3-Error |
[chars] spurious chip init CSR[dec]=0x%04x |
An illegal condition indicating initialization done has occurred. |
pas-ethernet |
"Clear the interface. " "If this message recurs call your technical support " "representative for assistance." |
|
AMDP2_FE-3-TOOMANYPART |
3-Error |
Bad packet with [dec] particles pak=0x[hec] |
The software detected an invalid packet. |
pas-ethernet |
"Try a later version of the software. If the message " "recurs call your technical support representative " "for assistance." |
|
AMDP2_FE-3-UNDERFLO |
3-Error |
[chars] transmit error |
While transmitting a frame the controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally such a problem is temporary depending on transient peak loads within the system. |
pas-ethernet |
"The system should recover. No action is required." |
|
AMDP2_FE-4-BABBLE |
4-Warning |
[chars] transmit problem CSR0=[hex] |
The transmitter has been on the channel longer than the time taken to transmit the largest frame |
pas-ethernet |
"The system should recover. No action is required." |
|
AMDP2_FE-5-LATECOLL |
5-Notice |
[chars] transmit error |
Late collisions occurred on the Ethernet/Fast Ethernet interface. When a collision occurs after the preamble has been transmitted then such a collision is called a LATE collision. The packet will be retransmitted but this condition could also indicate that another device is failing to detect when the network is in use. |
pas-ethernet |
"If the interface is Fast Ethernet verify that both " "peers are in the same duplex mode. For regular " "Ethernet the system should recover. No action is " "required." |
|
AMDP2_FE-5-LOSTCARR |
5-Notice |
[chars] cable/transceiver problem? |
The cable and/or transceiver is not connected. |
pas-ethernet |
"Connect the cable and/or transceiver." |
|
AMDP2_FE-6-EXCESSCOLL |
6-Information |
[chars] TDR=[dec] TRC=[dec] |
Ethernet/Fast Ethernet is seeing multiple collisions. This may occur under heavy loads. |
pas-ethernet |
"The system should recover. No action is " "required." |
|
AMT-2-ADD_GATEWAY |
2-Critical |
Error adding new Gateway |
Can't get memory for a new Gateway [chars] port [dec] |
- |
LOG_STD_NO_ACTION |
|
AMT-2-GATEWAY_INIT |
2-Critical |
Error initializing AMT Gateway |
Insufficient memory is available to initialize Gateway |
- |
LOG_STD_SH_TECH_ACTION |
|
AMT-2-MSGTYPE_ERR |
2-Critical |
[chars] AMT message with invalid type [dec] |
AMT type is not 1-7 |
- |
LOG_STD_NO_ACTION |
|
AMT-2-PROCESS_ERR |
2-Critical |
Error initializing AMT process |
Can't start the AMT process |
- |
LOG_STD_NO_ACTION |
|
AMT-2-RELAY_INIT |
2-Critical |
Error initializing AMT Relay |
Insufficient memory is available to initialize Relay |
- |
LOG_STD_SH_TECH_ACTION |
|
AMT-2-RPT_WAVLINIT |
2-Critical |
Error initializing IGMP Unsolicited Report handler |
Insufficient memory is available to initialize the IGMP \n\ Unsolicited Report handler. |
- |
LOG_STD_SH_TECH_ACTION |
|
AN-3-ACP_CHANNEL_TO_NBR_FAILED |
3-Error |
Failed to create ACP [chars] from Device Addr [chars] |
Autonomic Network Control Plane Channel has not been created to the neighbor |
AN |
LOG_STD_NO_ACTION |
|
AN-3-ACP_DIKE_TO_NBR_FAILED |
3-Error |
Failed to create DIKE on ACP [chars] from Device Addr [chars] |
Autonomic Network Control plane - Failed to create DIKE tunnel to neighbor |
AN |
LOG_STD_NO_ACTION |
|
AN-3-ACP_IPSEC_TO_NBR_FAILED |
3-Error |
Failed to create IPSEC on ACP from device Addr [chars] |
Autonomic Network Control plane - Failed to create IPSEC tunnel to neighbor |
AN |
LOG_STD_NO_ACTION |
|
AN-3-ACP_VRF_GLOBAL_CREATE_FAIL |
3-Error |
Device UDI [chars] failed to create |
Autonomic network VRF has not been created globally |
AN |
LOG_STD_NO_ACTION |
|
AN-3-ACP_VRF_INTERFACE_CREATE_FAIL |
3-Error |
Device UDI [chars] failed to create Autonomic VRF |
Autonomic network VRF has not been created on the interface |
AN |
LOG_STD_NO_ACTION |
|
AN-3-ANR_WHITELIST_FILE_ERROR |
3-Error |
Autonomic Registrar with Addr [chars] encountered error in |
The autonomic registeration authority encountered file error when reading from whitelist file check the file name and its contents |
AN |
LOG_STD_NO_ACTION |
|
AN-3-DOMAIN_KEY_GEN_FAIL |
3-Error |
The bootstrapping device with key label [chars] |
The key pair generation failed at the device for triggering BS request message to Autonomic registrar. Can be due to failure in RSA key pair generation in the crypto library |
AN |
LOG_STD_NO_ACTION |
|
AN-3-IDP_INTENT_FILE_ERROR |
3-Error |
Device Addr [chars] encountered error [chars] when reading from |
The Intent Distribution Protocol Module encountered file error when reading from intent file check the file name and its contents |
AN |
LOG_STD_NO_ACTION |
|
AN-3-MSG_INVALID_HEADER |
3-Error |
Invalid message header type [dec] received |
The message packet header got corrupted and invalid header received |
AN |
LOG_STD_NO_ACTION |
|
AN-3-NBR_DOMAIN_CERT_EXPIRED |
3-Error |
Domain certificate of Neighbor with Addr [chars] connected on interface [chars] has expired |
The domain certificate of the neighbor device has expired |
AN |
LOG_STD_NO_ACTION |
|
AN-3-NBR_DOMAIN_CERT_INVALID |
3-Error |
Domain certificate of Neighbor with Addr [chars] connected on interface [chars] is invalid |
The domain certificate of the neighbor device is invalid |
AN |
LOG_STD_NO_ACTION |
|
AN-3-NBR_DOMAIN_CERT_REVOKED |
3-Error |
Domain certificate of Neighbor with Addr [chars] connected on interface [chars] is revoked |
The domain certificate of the neighbor device has been revoked |
AN |
LOG_STD_NO_ACTION |
|
AN-3-TLV_PARSE_ALIGN_ERROR |
3-Error |
TLV parsed Len [dec] Next TLV could be misaligned |
Parsed TLV message is not a multiple of 4 and the next TLV message can be misaligned |
AN |
LOG_STD_NO_ACTION |
|
AN-3-TLV_PARSE_LEN_INCORRECT |
3-Error |
TLV parsed len [dec] > original message length [dec] |
Parsed TLV message length is greater than original message length |
AN |
LOG_STD_NO_ACTION |
|
AN-4-ANR_SIGN_VERIFY_FAIL |
4-Warning |
Device UDI [chars] signature verification of Autonomic registrar |
The new device joining the network verified the signature of autonomic registrar as a part of mutual authentication and the verification failed |
AN |
LOG_STD_NO_ACTION |
|
AN-4-DEVICE_ALREADY_REGISTERED_BY_ANR |
4-Warning |
Device with UDI [chars] connected to Proxy Addr [chars] on interface [chars] is already registered by |
The autonomic network registration authority will not allow this device to join as it already registered with a different public key |
AN |
LOG_STD_NO_ACTION |
|
AN-4-DEVICE_NOT_IN_WHITELIST |
4-Warning |
Device with UDI [chars] |
The autonomic network registration authority will not allow this device to join as it is not in whitelist |
AN |
LOG_STD_NO_ACTION |
|
AN-4-MASA_AUDIT_LOG_FAIL |
4-Warning |
Device with udi [chars] is not in the audit log of MASA |
The manufacturer authorised signing authority audit log doesnt contain this device in its database |
AN |
LOG_STD_NO_ACTION |
|
AN-4-MASA_AUTH_FAIL |
4-Warning |
Device with udi [chars] is not authorized by MASA |
The MASA - manufacturer authorised signing authority has not authorised this device in its network |
AN |
LOG_STD_NO_ACTION |
|
AN-4-MASA_AUTH_TOKEN_PARSE_ERROR |
4-Warning |
Error while parsing authentication token from MASA server for device udi-[chars] |
Encountered error while parsing the authentication token response string from MASA server |
AN |
LOG_STD_NO_ACTION |
|
AN-5-ANR_DOWN |
5-Notice |
Disabled autonomic registrar with Addr [chars] |
The autonomic network registration authority functionality is disabled |
AN |
LOG_STD_NO_ACTION |
|
AN-5-ANR_UP |
5-Notice |
A New Autonomic Registrar has been configured in domain [chars] and it has been assigned IP Addr [chars] |
The autonomic network registration authority has been confgiured and is locally up |
AN |
LOG_STD_NO_ACTION |
|
AN-5-CD_STATE_CHANGED |
5-Notice |
[chars] Channel [dec] [chars] - Our Intf [chars] |
CD L2 or Reuse Channel Created/Removed/Expired |
AN |
LOG_STD_NO_ACTION |
|
AN-5-DEVICE_BOOTSTRAPPED_BY_ANR |
5-Notice |
Device with UDI [chars] and Addr [chars] has been boot strapped by autonomic registrar in autonomic domain [chars] |
The autonomic network registration authority has bootstrapped this device |
AN |
LOG_STD_NO_ACTION |
|
AN-5-IDP_INTENT_VER_OLD_DISCARD |
5-Notice |
Device Addr [chars] discarded the older intent version [dec] |
The device received an old intent file by Intent Distribution Protocol and is discarding it |
AN |
LOG_STD_NO_ACTION |
|
AN-5-IDP_INTENT_VER_UPDATED |
5-Notice |
Device Addr [chars] updated to a new Intent version [dec] |
The device received a new intent file by Intent Distribution Protocol |
AN |
LOG_STD_NO_ACTION |
|
AN-5-NBR_ADDED |
5-Notice |
Device with UDI [chars] is added as a Neighbor to Device with Addr [chars] on the interface [chars] |
A hello message is received and the device is added in the neighbor table |
AN |
LOG_STD_NO_ACTION |
|
AN-5-NBR_IN_DOMAIN |
5-Notice |
Neighbor with Addr [chars] connected via interface [chars] to device Addr [chars] is brought inside my domain [chars] |
The device has been admitted into the autonomic domain |
AN |
LOG_STD_NO_ACTION |
|
AN-5-NBR_LOST |
5-Notice |
Device with ACP Addr [chars] lost connectivity to its Neighbor Addr [chars] on interface [chars] |
Lost connectivity to the neighboring device & it is no longer part of autonomic domain |
AN |
LOG_STD_NO_ACTION |
|
AN-5-NBR_OUT_DOMAIN |
5-Notice |
Neighbor with Addr [chars] connected via interface [chars] |
The device is removed from the autonomic domain it can happen if the domain certificate is NULL or if the domain certificate is invalid |
AN |
LOG_STD_NO_ACTION |
|
AN-5-SERVICE_LEARNT |
5-Notice |
Device with Addr [chars] learnt Autonomic service with Service Type [dec] Service IP Addr [chars] |
- |
- |
- |
|
AN-6-ACP_CHANNEL_TO_NBR_CREATED |
6-Information |
Established ACP [chars] from Device Addr [chars] to |
Autonomic Network Control plane Channel has been created to the neighbor |
AN |
LOG_STD_NO_ACTION |
|
AN-6-ACP_CHANNEL_TO_NBR_REMOVED |
6-Information |
Removed ACP [chars] from Device Addr [chars] to |
Autonomic Network Control Plane Channel to neighbor is removed |
AN |
LOG_STD_NO_ACTION |
|
AN-6-ACP_DIKE_TO_NBR_CREATED |
6-Information |
Established DIKE on ACP [chars] from Device Addr [chars] |
Autonomic Network Control plane - DIKE tunnel established to neighbor |
AN |
LOG_STD_NO_ACTION |
|
AN-6-ACP_DIKE_TO_NBR_REMOVED |
6-Information |
Removed DIKE on ACP [chars] from Device Addr [chars] |
Autonomic Network Control plane - DIKE tunnel to neighbor is removed |
AN |
LOG_STD_NO_ACTION |
|
AN-6-ACP_IPSEC_TO_NBR_CREATED |
6-Information |
Established IPSEC on ACP from Device Addr [chars] |
Autonomic Network Control plane - IPSEC tunnel established to neighbor |
AN |
LOG_STD_NO_ACTION |
|
AN-6-ACP_IPSEC_TO_NBR_REMOVED |
6-Information |
Removed IPSEC on ACP from Device Addr [chars] to |
Autonomic Network Control plane - IPSEC tunnel to neighbor is removed |
AN |
LOG_STD_NO_ACTION |
|
AN-6-ACP_ROUTING_GLOBAL_DISABLE |
6-Information |
Removed OSPFv3 routing globally pid [dec] |
OSPF routing has been disabled globally |
AN |
LOG_STD_NO_ACTION |
|
AN-6-ACP_ROUTING_GLOBAL_ENABLED |
6-Information |
Enabled global OSPFv3 pid [dec]rid [inet]area [dec] |
OSPF routing has been enabled globally |
AN |
LOG_STD_NO_ACTION |
|
AN-6-ACP_ROUTING_INTERFACE_ENABLED |
6-Information |
OSPF routing enabled on interface: [chars] pid [dec]rid [inet] area [dec] |
OSPF routing has been enabled on all physical interface |
AN |
LOG_STD_NO_ACTION |
|
AN-6-ACP_VRF_GLOBAL_CREATE_SUCCESS |
6-Information |
Device UDI [chars] Autonomic VRF |
Autonomic network VRF has been created globally |
AN |
LOG_STD_NO_ACTION |
|
AN-6-ACP_VRF_GLOBAL_REMOVE |
6-Information |
Device UDI [chars] Autonomic VRF |
Autonomic network VRF has been removed globally |
AN |
LOG_STD_NO_ACTION |
|
AN-6-ACP_VRF_INTERFACE_CREATE_SUCCESS |
6-Information |
Device UDI [chars] |
Autonomic network VRF has been created on the interface |
AN |
LOG_STD_NO_ACTION |
|
AN-6-AN_ABORTED_BY_CONSOLE_INPUT |
6-Information |
Autonomic disabled due to User intervention on console. configure 'autonomic' to enable it. |
User entered into configuration mode So AN is disabled An process is stopped |
AN |
LOG_STD_NO_ACTION |
|
AN-6-AN_ABORTED_BY_MANUAL_CONFIG_DETECTED |
6-Information |
Autonomic disabled due to detection of new configuration. |
Some other process configures something. So AN is disabled An process is stopped |
AN |
LOG_STD_NO_ACTION |
|
AN-6-AN_ABORTED_BY_NO_AUTONOMIC |
6-Information |
Autonomic disabled due to 'no autonomic' command. |
'No autonomic' command is entered So AN is disabled An process is stopped |
AN |
LOG_STD_NO_ACTION |
|
AN-6-ANR_WHITELIST_CONFIG |
6-Information |
Autonomic registrar with Addr [chars] Domain id [chars] has whitelist- will allow only these devices in autonomic network |
The autonomic registeration authority has been configured with white list and will allow only these devices to enter its network |
AN |
LOG_STD_NO_ACTION |
|
AN-6-ANR_WHITELIST_NOT_CONFIG |
6-Information |
Autonomic registrar with Addr [chars] has no whitelist- will allow all devices |
The autonomic registeration authority has not been configured with white list and will allow all devices to enter its network |
AN |
LOG_STD_NO_ACTION |
|
AN-6-CONFIG_DOWNLOAD_FAILED |
6-Information |
Config download on the Device Addr [chars] has FAILED |
Failed to download the config file to the Running config |
AN |
LOG_STD_NO_ACTION |
|
AN-6-CONFIG_DOWNLOAD_STARTED |
6-Information |
Config download started on the Device Addr [chars] |
Config download is triggerred |
AN |
LOG_STD_NO_ACTION |
|
AN-6-CONFIG_DOWNLOAD_SUCCESS |
6-Information |
Config download at the Device Addr [chars] |
Download of the config file to the Running config is Successful |
AN |
LOG_STD_NO_ACTION |
|
AN-6-CONFIG_SAVE |
6-Information |
Issuing 'write memory' to save config |
Saving configurations to startup-config by AN process |
AN |
LOG_STD_NO_ACTION |
|
AN-6-DEVICE_ALLOWED_BY_ANR |
6-Information |
Device with udi [chars] is allowed by autonomic registrar in its Domain ID [chars] with addr [chars] and Device ID [chars] |
The autonomic network registration authority has authorised this device to enter its network |
AN |
LOG_STD_NO_ACTION |
|
AN-6-DEVICE_ENROLLED |
6-Information |
Device with UDI [chars] connected to Proxy Addr [chars] on the interface [chars] is allowed by Autonomic registrar Addr [chars] |
The autonomic network registration authority has enrolled this device |
AN |
LOG_STD_NO_ACTION |
|
AN-6-MASA_NOT_CONFIG |
6-Information |
Autonomic registrar with udi [chars] has no reachability to MASA -not configured Cant verify device udi [chars] |
The manufacturer authorised signing authority has not been configured cannot do the verification of device |
AN |
LOG_STD_NO_ACTION |
|
AN-6-MY_DOMAIN_CERT_EXPIRED |
6-Information |
Domain certificate of this device Addr [chars] has expired |
The domain certificate of this device has expired |
AN |
LOG_STD_NO_ACTION |
|
AN-6-MY_DOMAIN_CERT_RENEWED |
6-Information |
Domain certificate of device Addr [chars] has been renewed |
The domain certificate of this device is renewed |
AN |
LOG_STD_NO_ACTION |
|
AN-6-NBR_DOMAIN_CERT_VALID |
6-Information |
Domain certificate of Neighbor with Addr [chars] |
The domain certificate of the neighbor device is validated successfully |
AN |
LOG_STD_NO_ACTION |
|
AN-6-SUDI_AVAILABLE |
6-Information |
secure UDI - [chars] |
Secure unique device identification number is available on the device |
AN |
LOG_STD_NO_ACTION |
|
AN-6-UDI_AVAILABLE |
6-Information |
UDI - [chars] |
Unique device identification number is available on the device |
AN |
LOG_STD_NO_ACTION |
|
API_BAD_ARGUMENTS-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
API_BAD_RESPONSE-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
API_FAILED-3-L2VPN |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
API_FAILED-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
API_MSG-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
APM-3-CACHE_SIZE |
3-Error |
Configured cache size is too large. Value has been limited to [dec]100 x platform default. |
configured cache size is too big |
media-mon |
LOG_STD_ACTION |
|
APM-3-INIT |
3-Error |
[chars] |
Easy Perf Mon Initialization failed |
media-mon |
LOG_STD_ACTION |
|
APM-3-LIST |
3-Error |
[chars] [chars] |
List operation error occurred. |
media-mon |
LOG_STD_ACTION |
|
APM-3-MEM |
3-Error |
Memory [chars] failed - [chars] |
Memory operation failed |
media-mon |
LOG_STD_ACTION |
|
APPFW-3-HTTP_APPFW_CONF_ERROR |
3-Error |
Application Firewall configuration error -- [chars] |
An error has occurred during Application Firewall configuration. |
appfw |
"This message indicates an error during firewall configuration " "and may be a potential security problem." |
|
APPFW-3-HTTP_MAX_REQ_EXCEED |
3-Error |
Maximum of [dec] unanswered HTTP requests exceeded from [inet]:[dec] to [inet]:[dec] |
The HTTP message has been detected to violate the \n\ transfer encoding application firewall inspection rule. |
appfw |
"This message is for informational purposed only but may indicate \n\ a security problem." |
|
APPFW-4-HTTP_CONT_LENGTH |
4-Warning |
content-length |
The HTTP message has been detected to violate the content-length \n\ application firewall inspection rule. |
appfw |
"This message is for informational purposed only but may indicate \n\ a security problem." |
|
APPFW-4-HTTP_CONT_TYPE_MATCH |
4-Warning |
Sig:[dec] Content type not found - [chars] [chars] from [inet]:[dec] to [inet]:[dec] |
The HTTP message has been detected to violate the \n\ content-type-verification application firewall inspection rule. |
appfw |
"This message is for informational purposed only but may indicate \n\ a security problem." |
|
APPFW-4-HTTP_CONT_TYPE_SIZE |
4-Warning |
Sig:[dec] Content size %lu out of range - [chars] [chars] from [inet]:[dec] to [inet]:[dec] |
The HTTP message has been detected to violate the \n\ content-type-verification application firewall inspection rule. |
appfw |
"This message is for informational purposed only but may indicate \n\ a security problem." |
|
APPFW-4-HTTP_CONT_TYPE_VERIFY |
4-Warning |
Sig:[dec] Content type does not match the specified type - [chars] [chars] from [inet]:[dec] to [inet]:[dec] |
The HTTP message has been detected to violate the \n\ content-type-verification application firewall inspection rule. |
appfw |
"This message is for informational purposed only but may indicate \n\ a security problem." |
|
APPFW-4-HTTP_DEOBFUSCATE |
4-Warning |
Sig:[dec] Deobfuscation signature detected - [chars] [chars] from [inet]:[dec] to [inet]:[dec] |
The HTTP message has been detected to violate the \n\ deobfuscate application firewall inspection rule. |
appfw |
"This message is for informational purposed only but may indicate \n\ a security problem." |
|
APPFW-4-HTTP_MATCH_REQ_RESP |
4-Warning |
Sig:[dec] Content type: [chars] does not match the Accept-Type from [inet]:[dec] to [inet]:[dec] |
The HTTP message has been detected to violate the \n\ content-type-verification application firewall inspection rule. |
appfw |
"This message is for informational purposed only but may indicate \n\ a security problem." |
|
APPFW-4-HTTP_MAX_HDR_LEN |
4-Warning |
Sig:[dec] HTTP Header length exceeded. Received %lu byte of header - [chars] [chars] from [inet]:[dec] to [inet]:[dec] |
The HTTP message has been detected to violate the \n\ max-hdr-len application firewall inspection rule. |
appfw |
"This message is for informational purposed only but may indicate \n\ a security problem." |
|
APPFW-4-HTTP_MAX_URI_LEN |
4-Warning |
Sig:[dec] HTTP URI length exceeded. Received %lu byte of URL - [chars] [chars] from [inet]:[dec] to [inet]:[dec] |
The HTTP message has been detected to violate the \n\ max-uri-len application firewall inspection rule. |
appfw |
"This message is for informational purposed only but may indicate \n\ a security problem." |
|
APPFW-4-HTTP_PORT_MISUSE_IM |
4-Warning |
Sig:[dec] HTTP Instant Messenger detected - [chars] [chars] from [inet]:[dec] to [inet]:[dec] |
The HTTP message has been detected to violate the \n\ port misuse application firewall inspection rule. |
appfw |
"This message is for informational purposed only but may indicate \n\ a security problem." |
|
APPFW-4-HTTP_PORT_MISUSE_P2P |
4-Warning |
Sig:[dec] HTTP Peer-to-Peer detected - [chars] [chars] from [inet]:[dec] to [inet]:[dec] |
The HTTP message has been detected to violate the \n\ port misuse application firewall inspection rule. |
appfw |
"This message is for informational purposed only but may indicate \n\ a security problem." |
|
APPFW-4-HTTP_PORT_MISUSE_TUNNEL |
4-Warning |
Sig:[dec] HTTP Tunnel detected - [chars] [chars] from [inet]:[dec] to [inet]:[dec] |
The HTTP message has been detected to violate the \n\ port misuse application firewall inspection rule. |
appfw |
"This message is for informational purposed only but may indicate \n\ a security problem." |
|
APPFW-4-HTTP_REQ_METHOD_EXT |
4-Warning |
Sig:[dec] HTTP Extension method illegal - [chars] '[chars]' from [inet]:[dec] to [inet]:[dec] |
The HTTP message has been detected to violate the \n\ request-method application firewall inspection rule. |
appfw |
"This message is for informational purposed only but may indicate \n\ a security problem." |
|
APPFW-4-HTTP_REQ_METHOD_RFC |
4-Warning |
Sig:[dec] HTTP RFC method illegal - [chars] '[chars]' from [inet]:[dec] to [inet]:[dec] |
The HTTP message has been detected to violate the \n\ request-method application firewall inspection rule. |
appfw |
"This message is for informational purposed only but may indicate \n\ a security problem." |
|
APPFW-4-HTTP_STRICT_PROTOCOL |
4-Warning |
Sig:[dec] HTTP protocol violation detected - [chars] [chars] from [inet]:[dec] to [inet]:[dec] |
The HTTP message has been detected to violate the strict-http \n\ application firewall inspection rule. |
appfw |
"This message is for informational purposed only but may indicate \n\ a security problem." |
|
APPFW-4-HTTP_TRANSFER_ENCODE |
4-Warning |
Sig:[dec] HTTP Transfer encoding violation detected - [chars] [chars] from [inet]:[dec] to [inet]:[dec] |
The HTTP message has been detected to violate the \n\ transfer encoding application firewall inspection rule. |
appfw |
"This message is for informational purposed only but may indicate \n\ a security problem." |
|
APPFW-6-HTTP_SESSION_AUDIT_TRAIL |
6-Information |
HTTP session initiator [inet]:[dec] sends [dec] bytes - responder [inet]:[dec] sends [dec] bytes |
The HTTP message has been detected to violate the \n\ transfer encoding application firewall inspection rule. |
appfw |
"This message is for informational purposed only but may indicate \n\ a security problem." |
|
APPFW-6-IM_AOL_CLIENT_VERSION |
6-Information |
im-aol [inet]:[dec] attempting to establish connection with aol server [inet]:[dec] using an unsupported version of the client |
The AOL client version is not supported |
appfw |
"This message is for informational purposed only." |
|
APPFW-6-IM_AOL_SESSION |
6-Information |
im-aol [chars] service session initiator [inet]:[dec] [chars] [dec] bytes [chars] responder [inet]:[dec] |
The AIM well known service message has been detected. |
appfw |
"This message is for informational purposed only." |
|
APPFW-6-IM_MSN_CLIENT_VERSION |
6-Information |
im-msn [inet]:[dec] attempting to establish connection with msn server [inet]:[dec] using an unsupported version of the client |
The MSN client version is not supported |
appfw |
"This message is for informational purposed only." |
|
APPFW-6-IM_MSN_SESSION |
6-Information |
im-msn [chars] service session initiator [inet]:[dec] [chars] [dec] bytes [chars] responder [inet]:[dec] |
The MSNMSGR well known service message has been detected. |
appfw |
"This message is for informational purposed only." |
|
APPFW-6-IM_YAHOO_CLIENT_VERSION |
6-Information |
im-yahoo [inet]:[dec] attempting to establish connection with yahoo server [inet]:[dec] using an unsupported version of the client |
The YAHOO client version is not supported |
appfw |
"This message is for informational purposed only." |
|
APPFW-6-IM_YAHOO_P2P_CHAT |
6-Information |
im-yahoo text-chat service session: [inet]:[dec] establishing a direct chat with [dec].[dec].[dec].[dec] |
A specific service yyyy has been detected to establish\n\ a direct connection with another peer in a Yahoo! Instant Messenger \n\ application and the application firewall inspection policy has been\n\ configured to send an alarm for this event. Typical services are ñ \n\ text-chat voice-chat file-transfer etc. |
appfw |
"This message is for informational purposed only." |
|
APPFW-6-IM_YAHOO_SESSION |
6-Information |
The YMSGR well known service message has been detected. |
The YMSGR well known service message has been detected. |
appfw |
"This message is for informational purposed only." |
|
APPNAV_CLIENT-3-CFT_INIT_FAILED |
3-Error |
AppNav failed initialize flow table - [dec]. |
Flow table is a critical component of AppNav. The failure is likely due to lack of memory DRAM on the ESP. The |
service-controller |
LOG_STD_REDUCE_ACTION |
|
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-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-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-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-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-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-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-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-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-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-4-SC_CONVERGENCE_SUCCESS |
4-Warning |
APPNAV-CONTROLLER: Alarm #29001 cleared |
CMM convergence completed |
service-controller |
"None. All is well" |
|
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-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-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-4-SERVICE_CTX_DISABLE |
4-Warning |
SERVICE-CONTROLLER: Alarm 10001 Severity: Major \n Disabling service context [chars] |
Disabling service context |
- |
- |
|
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-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-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 |
"None. All is well" |
|
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-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" |
|
APS-1-NO_ACTIVE |
1-Alert |
No Active Port In Group [chars] |
After an active interface failure the system\n\ switches over to the standby interface if APS has\n\ been enabled. This message is posted if after a\n\ switchover the system finds no active interface\n\ i.e. both working and protection interfaces are\n\ found to be nonoperational. |
- |
"Isolate the cause of failure on both working\n\ and protection interfaces." |
|
APS-2-CHNLCFGMM |
2-Critical |
Group [chars]: Channel Config Mismatch |
Working and Protection interfaces do not point to the\n\ same path on local and remote network elements |
- |
"Configure working and protection interfaces\n\ to point to the same path on local and remote\n\ network elements" |
|
APS-2-CHNLMISMATCH |
2-Critical |
Group [chars]: Channel Mismatch - [chars] |
- |
- |
"Check for any failures on the APS commnication\n\ channel. If APS communication channel is\n\ operational contact Cisco TAC." |
|
APS-2-FEPF |
2-Critical |
Group [chars]: Far End Prot Failure - [chars] |
- |
- |
"Isolate the cause of failure on the protection\n\ channel on the remote network element." |
|
APS -2-INITSYS |
2-Critical |
[chars] |
A software error occurred during initialization of\n\ the APS subsystem |
- |
"Check for sufficient processor memory." LOG_STD_ACTION |
|
APS-2-INTRNLERR |
2-Critical |
[chars] [dec] |
APS software detected an internal error |
- |
LOG_STD_ACTION |
|
APS-2-MODEMISMATCH |
2-Critical |
Group [chars]: Mode Mismatch - [chars] |
- |
- |
"Configure the remote APS group for\n\ bidirectional operation." |
|
APS-2-NOSOCKET |
2-Critical |
Failed To Open Socket |
This message is posted when the APS subsystem fails\n\ to create a UDP socket for exchanging APS channel\n\ protocol messages over APS message channel configured\n\ for IP. This usually is due to a low memory condition\n\ in the system |
- |
LOG_STD_REDUCE_ACTION |
|
APS-2-PSBF |
2-Critical |
Group [chars]: Prot Switch Byte Failure - [chars] |
- |
- |
"Check for failures on the APS communication\n\ channel. Isolate the cause for such failures\n\ and restore the communication channel to\n\ working condition" |
|
APS-3-PORT_FAIL |
3-Error |
[chars] Port Fail On [chars] |
This message is posted when APS subsystem receives\n\ a port fail indication from the driver subsystem.\n\ This message indicates that the specified interface\n\ has detected a failure condition\n\ e.g. Loss Of Light. |
- |
"Isolate the cause of the failure and restore\n\ the interface to normal operational\n\ condition." |
|
APS-6-ADJUSTMODE |
6-Information |
Group [chars]: Mode Mismatch - [chars] |
This message is posted by the local network element\n\ if the local APS group has been configured for\n\ bidirectional operation but the associated remote\n\ APS group has been configured for unidirectional\n\ operation. This message is posted after the local\n\ network element detects the mismatch and changes\n\ the operation to unidirectional. |
- |
"Configure the remote APS group for\n\ bidirectional operation." |
|
APS-6-AUTOFOVER |
6-Information |
Auto-Failover - Group [chars] |
This message is posted if APS hardware\n\ successfully switched over to the standby interface\n\ after the failure of the active interface. This is\n\ informational only. |
- |
"Isolate the cause of failure of the previous\n\ active interface and restore it to a working\n\ condition." |
|
APS-6-BIDIRSWCH |
6-Information |
Group [chars]: Remote Request - [chars] |
This message is posted by the local network element\n\ after an APS switchover that is triggered by an APS\n\ request from the remote network element. This is\n\ informational only. |
- |
LOG_STD_NO_ACTION |
|
APS-6-CHNLACTIVE |
6-Information |
Group [chars] - [chars] channel is now ACTIVE |
This message is posted when a previously standby\n\ channel becomes the active channel. This is\n\ informational only. |
- |
LOG_STD_NO_ACTION |
|
APS-6-DISAUTFOV |
6-Information |
Disable Auto-Failover On [chars] |
APS has disabled auto-failover for the indicated\n\ group |
- |
show aps group <name> |
|
APS-6-ENAUTFOVR |
6-Information |
Enable Auto-Failover On [chars] |
This message is posted when APS software enables\n\ hardware to perform APS actions for failures\n\ detected by the hardware. This is informational\n\ only. |
- |
LOG_STD_NO_ACTION |
|
ARAP-0-DEFAULT |
0-Emergency |
TTY [dec] |
An internal software error occured. |
- |
LOG_STD_SH_TECH_ACTION |
|
ARAP-0-NOTNULLRESEND |
0-Emergency |
TTY [dec] |
An internal software error occured. |
- |
LOG_STD_SH_TECH_ACTION |
|
ARAP-0-NULLRESEND |
0-Emergency |
TTY [dec] |
An internal software error occured. |
- |
"Report this error to you technical support representative." |
|
ARAP-0-VSERROR |
0-Emergency |
TTY [dec]: VS queued error |
An internal software error occured. |
- |
LOG_STD_SH_TECH_ACTION |
|
ARAP-0-WAITBADMSG |
0-Emergency |
TTY [dec]: arg msg bad [hec] |
The router received an invalid packet during ARAP MNP4 connection\ setup phase. |
- |
"Check for excessive line noise.\ Check the ARAP client software configuration for\ possible problems." |
|
ARAP-2-NOLOG |
2-Critical |
TTY [dec]: Could not malloc log |
Memory not available for internal MNP4 logging. |
- |
LOG_STD_SH_TECH_ACTION |
|
ARAP-3-ABORTED |
3-Error |
TTY [dec]: arap callback aborted |
An unexpected message was received during the Microcom Networking\n\ Protocol version 4 MNP4 link setup. |
- |
LOG_STD_ACTION |
|
ARAP-3-BADCONFIG |
3-Error |
TTY [dec]: unhandled configuration command |
A configuration command was not recognized. |
- |
"Check the configuration file on the server for any invalid\n\ configuration commands." |
|
ARAP-3-BADPAK |
3-Error |
TTY [dec]: Bad packet type in arap_send_msg |
Internal data structures are corrupted. |
- |
"Check for abnormally high CPU usage." |
|
ARAP-3-REMOTEERROR |
3-Error |
TTY [dec]: arap input error |
ARAP connection was terminated without a known cause. |
- |
LOG_STD_ACTION |
|
ARAP-3-TIMEOUT |
3-Error |
TTY [dec]: arap expected message timeout |
The SCP process has been terminated. |
- |
"If this message recurs copy the error message exactly as it appears\n\ and report it to your technical support representative." |
|
ARAP-4-CONFAILED |
4-Warning |
TTY [dec]: ARAP connection failed: [chars] |
The ARA protocol client was denied access probably due to a\n\ configuration problem on the server. The error message should indicate\n\ the problem. This message does not indicate access denials due to bad\n\ passwords. |
- |
"Investigate the problem reported in the error message." |
|
ARAP-4-NOEXTTACACS |
4-Warning |
TTY [dec]: arap TACACS is configured but extended TACACS is not. |
- |
- |
"Configure extended TACACS." |
|
ARAP-5-INITCONFUSED |
5-Notice |
TTY [dec]: ARAP unexpected initialization packet [chars] |
The startup negotiation between a client and the ARA protocol server\n\ fell out of order. If this message is received sporadically it\n\ indicates line noise. |
- |
"If this message recurs reinstall the ARA client software." |
|
ARAP-5-PAKINVALID |
5-Notice |
TTY [dec]: ARAP invalid packet received |
This message appears only when ARA protocol logging is configured. The\n\ message notes that an ARA protocol user has logged out. |
- |
LOG_STD_NO_ACTION |
|
ARAP-6-BADEXIT |
6-Information |
TTY [dec]: exited user [chars]: [chars] |
A user was disconnected from ARA protocol at an unexpected time. The\n\ disconnection may be due to modems dropping server error client\n\ problems or any number of other difficulties. |
- |
"To determine the cause of the disconnection correlate the receipt of\n\ this message with the user problem reports." |
|
ARAP-6-LRPHASERROR |
6-Information |
TTY [dec]: Received LT in CONNECTION PHASE |
The router received an invalid packet during ARA connection setup\ phase. |
- |
"Check for excessive line noise.\ Check the ARAP client software configuration for\ possible problems." |
|
ARAP-6-MAXRESENDS |
6-Information |
TTY [dec] |
The router resent MNP4 packets maximum number of times without\ receiving an acknowledgement. |
- |
"To determine the cause of the disconnection correlate the receipt of\n\ this message with the user problem reports." |
|
ARAP-6-MNP4RCVDISC |
6-Information |
TTY [dec]: MNP4 input disconnect |
This indicates that the router received disconnect request\ from the remote Macintosh client. |
- |
LOG_STD_NO_ACTION |
|
ARAP-6-MNP4T401 |
6-Information |
TTY [dec]: T401 [dec] baud rate [dec] |
This message indicates that the router received MNP4 connection\ request. MNP4 acknowledgement timer value is also indicated. |
- |
LOG_STD_NO_ACTION |
|
ARAP-6-RCVGIANT |
6-Information |
TTY [dec]: Rcv giant. dropping frame |
The router received an oversized MNP4 frame. |
- |
"Check for excessive line noise.\ Check the ARAP client software configuration for\ possible problems." |
|
ARAP-6-RCVNOPAK |
6-Information |
TTY [dec]: Receive getbuffer failure. dropping frame |
No buffer exists for an incoming packet. |
- |
"Examine buffer usage statistics. Possibly more memory is\ required." |
|
ARAP-6-RESENDSLOW |
6-Information |
TTY [dec] |
The router repeated resending of MNP4 packets as the\ Macintosh client failed to acknowledge previously resent packets. |
- |
"If this error message persists for several ARAP connections\ report it to your technical support representative." |
|
ARAP-6-TIMERERROR |
6-Information |
TTY [dec]: MNP4 timeout error |
The router is dropping the connection after doing maximum resends. |
- |
"To determine the cause of the disconnection correlate the receipt of\n\ this message with the user problem reports." |
|
ARAP-6-XTICKLE |
6-Information |
TTY [dec]: exited user [chars]: Other side stopped answering ARAP tickles\ mnp4 pak resent [dec] mnp4 pak sent [dec] last [dec] now [dec] |
The router disconnected as the remote Macintosh client stopped\ sending ARAP tickle or data packets. |
- |
"To determine the cause of the disconnection correlate the receipt of\n\ this message with the user problem reports." |
|
ARCHIVE_CONFIG-4-ARCHIVE_DELETE_FAILED |
4-Warning |
Delete of a previously saved archive of the router configuration could not be completed. |
The router could not delete a file that was previously written. The file that was being deleted file contains an archive of the router configuration. This could occur for example if the file was manually deleted. |
- |
"None" |
|
ARCHIVE_CONFIG-4-ARCHIVE_SKIPPED |
4-Warning |
Archive of router configuration was skipped due to a previous initiation. |
Only one archive can be created at a time. Two or more simultaneous archives in progress is not allowed. This could occur for example if two users attempt to create an archive simultaneouly. |
- |
"Retry the archive creation later when the previous archive has finished being written." |
|
ARCHIVE_CONFIG-6-ARCHIVE_CREATE_FAILED_STANDBY |
6-Information |
Could not create an archive of the router configuration on the standby RP. |
The router could not create an archive file on the standby RP. The file that was being created contains an archive of the router configuration. This could occur for example if the active RP cannot communicate with the standby RP. |
- |
"None" |
|
ARCHIVE_CONFIG-6-ARCHIVE_DELETE_FAILED_STANDBY |
6-Information |
Delete of a previously saved archive of the router configuration could not be completed on the standby RP. |
The router could not delete a file that was previously written on the standby RP. The file that was being deleted file contains an archive of the router configuration. This could occur for example if the file was manually deleted. Alternatively the file could not be deleted when the active RP cannot communicate with the standby RP. |
- |
"None" |
|
ARCHIVE_DIFF-3-DIFF_CMD_INIT_FAILED |
3-Error |
Failed to register the special case [chars] command:\[chars]\ during initialization. Config Diff and Rollback cannot be used as a result of this error. |
An internal software error occurred during initialization - Config Diff and Rollback cannot be used as a result of this error. |
- |
"Copy the error message exactly as it appears. Copy down the system's " "configuration along with any other relevant information. Contact your " "technical support representative for assistance." |
|
ARCHIVE_DIFF-3-DIFF_CMD_INIT_FAILED |
3-Error |
Failed to register the special case [chars] command:\[chars]\ during initialization. Config Diff and Rollback cannot be used as a result of this error. |
An internal software error occurred during initialization - Config Diff and Rollback cannot be used as a result of this error. |
- |
"Copy the error message exactly as it appears. Copy down the system's " "configuration along with any other relevant information. Contact your " "technical support representative for assistance." |
|
ARCHIVE_DIFF-3-DIFF_INIT_FAILED |
3-Error |
Could not initialize the Config Diff and Rollback subsystem |
An internal software error occurred during initialization. Config Diff and Rollback cannot be used as a result of this error. |
- |
"Copy the error message exactly as it appears. Copy down the system's " "configuration along with any other relevant information. Contact your " "technical support representative for assistance." |
|
ARCHIVE_DIFF-3-DIFF_INIT_FAILED |
3-Error |
Could not initialize the Config Diff and Rollback subsystem |
An internal software error occurred during initialization. Config Diff and Rollback cannot be used as a result of this error. |
- |
"Copy the error message exactly as it appears. Copy down the system's " "configuration along with any other relevant information. Contact your " "technical support representative for assistance." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_BACKUP |
5-Notice |
Backing up current running config to [chars] |
The current running config is saved so that when the timer expires if no confirmation has been received from user to confirm what they've configured the system will rollback to the saved config. |
- |
"This message DOES NOT denote any error condition. It is a part of the " "normal operation of the rollback confirmed change." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_BACKUP |
5-Notice |
Backing up current running config to [chars] |
The current running config is saved so that when the timer expires if no confirmation has been received from user to confirm what they've configured the system will rollback to the saved config. |
- |
"This message DOES NOT denote any error condition. It is a part of the " "normal operation of the rollback confirmed change." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_CANCEL |
5-Notice |
User: [chars]Priv: [dec] View: [dec]: Rollback Confirmed Change is cancelled due to [chars] failure |
Rollback Confirmed Change is normally configured along with other configuration operations such as \config term\ or \config replace\. If those operation failed Rollback Confirmed Change should not be activated. |
- |
"Remove the error condition and try again later." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_CANCEL |
5-Notice |
User: [chars]Priv: [dec] View: [dec]: Rollback Confirmed Change is cancelled due to [chars] failure |
Rollback Confirmed Change is normally configured along with other configuration operations such as \config term\ or \config replace\. If those operation failed Rollback Confirmed Change should not be activated. |
- |
"Remove the error condition and try again later." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_CONFIRM |
5-Notice |
User: [chars]: Confirm the configuration change |
The configuration change is confirmed. The timer for rolling to the previously saved config is cancelled |
- |
"This message DOES NOT denote any error condition. It is a part of the " "normal operation of the rollback confirmed change." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_CONFIRM |
5-Notice |
User: [chars]: Confirm the configuration change |
The configuration change is confirmed. The timer for rolling to the previously saved config is cancelled |
- |
"This message DOES NOT denote any error condition. It is a part of the " "normal operation of the rollback confirmed change." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_RESET_ABSTIMER |
5-Notice |
User: [chars]: Reset Rollback Confirmed Change timerabsolute to %lu minute |
Reset Rollback Confirmed Change timerabsolute to a new value |
- |
"This message DOES NOT denote any error condition. It is a part of the " "normal operation of the rollback confirmed change." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_RESET_ABSTIMER |
5-Notice |
User: [chars]: Reset Rollback Confirmed Change timerabsolute to %lu minute |
Reset Rollback Confirmed Change timerabsolute to a new value |
- |
"This message DOES NOT denote any error condition. It is a part of the " "normal operation of the rollback confirmed change." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_RESET_IDLETIMER |
5-Notice |
User: [chars] Reset Rollback Confirmed Change timeridle to %lu minute |
Reset Rollback Confirmed Change timeridle to a new value |
- |
"This message DOES NOT denote any error condition. It is a part of the " "normal operation of the rollback confirmed change." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_RESET_IDLETIMER |
5-Notice |
User: [chars] Reset Rollback Confirmed Change timeridle to %lu minute |
Reset Rollback Confirmed Change timeridle to a new value |
- |
"This message DOES NOT denote any error condition. It is a part of the " "normal operation of the rollback confirmed change." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_REVERTNOW |
5-Notice |
User: [chars]: Rollback immediately. |
Rollback immediately and cancel the timer |
- |
"This message DOES NOT denote any error condition. It is a part of the " "normal operation of the rollback confirmed change." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_REVERTNOW |
5-Notice |
User: [chars]: Rollback immediately. |
Rollback immediately and cancel the timer |
- |
"This message DOES NOT denote any error condition. It is a part of the " "normal operation of the rollback confirmed change." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_ROLLBACK_RETRY |
5-Notice |
Failed to acquire configuration lock. Rollback did not start. Schedule to retry in 5 minutes |
Failed to acquire configuration lock. Rollback did not start. In this case retry will be scheduled. |
- |
"This message DOES NOT denote any error condition. It is a part of the " "normal operation of the rollback confirmed change." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_ROLLBACK_RETRY |
5-Notice |
Failed to acquire configuration lock. Rollback did not start. Schedule to retry in 5 minutes |
Failed to acquire configuration lock. Rollback did not start. In this case retry will be scheduled. |
- |
"This message DOES NOT denote any error condition. It is a part of the " "normal operation of the rollback confirmed change." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_ROLLBACK_START |
5-Notice |
Start rolling to: [chars] |
The timer for Rollback Confirmed Change has expired. System will rollback to the previously saved config. |
- |
"This message DOES NOT denote any error condition. It is a part of the " "normal operation of the rollback confirmed change." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_ROLLBACK_START |
5-Notice |
Start rolling to: [chars] |
The timer for Rollback Confirmed Change has expired. System will rollback to the previously saved config. |
- |
"This message DOES NOT denote any error condition. It is a part of the " "normal operation of the rollback confirmed change." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_START_ABSTIMER |
5-Notice |
User: [chars]Priv: [dec] View: [dec]: Scheduled to rollback to config [chars] in %lu minutes |
The system will wait for the user to confirm that they wish to keep what they've configured until the timer expires. If the confirmation is not received in time the router will rollback. |
- |
"This message DOES NOT denote any error condition. It is a part of the " "normal operation of the rollback confirmed change." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_START_ABSTIMER |
5-Notice |
User: [chars]Priv: [dec] View: [dec]: Scheduled to rollback to config [chars] in %lu minutes |
The system will wait for the user to confirm that they wish to keep what they've configured until the timer expires. If the confirmation is not received in time the router will rollback. |
- |
"This message DOES NOT denote any error condition. It is a part of the " "normal operation of the rollback confirmed change." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_START_IDLETIMER |
5-Notice |
User: [chars]Priv: [dec] View: [dec]: Scheduled to rollback to config [chars] if session has been idle for %lu minutes |
The system will wait for the user to confirm that they wish to keep what they've configured until the timer expires. If the confirmation is not received in time the router will rollback. |
- |
"This message DOES NOT denote any error condition. It is a part of the " "normal operation of the rollback confirmed change." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_START_IDLETIMER |
5-Notice |
User: [chars]Priv: [dec] View: [dec]: Scheduled to rollback to config [chars] if session has been idle for %lu minutes |
The system will wait for the user to confirm that they wish to keep what they've configured until the timer expires. If the confirmation is not received in time the router will rollback. |
- |
"This message DOES NOT denote any error condition. It is a part of the " "normal operation of the rollback confirmed change." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_WARNING_ABSTIMER |
5-Notice |
System will rollback to config [chars] in one minute. Enter \configure confirm\ if you wish to keep what you've configured |
Rollback will start in one minute. User could enter \configure confirm\ if they wish to keep what they've configured. |
- |
"This message DOES NOT denote any error condition. It is a part of the " "normal operation of the rollback confirmed change." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_WARNING_ABSTIMER |
5-Notice |
System will rollback to config [chars] in one minute. Enter \configure confirm\ if you wish to keep what you've configured |
Rollback will start in one minute. User could enter \configure confirm\ if they wish to keep what they've configured. |
- |
"This message DOES NOT denote any error condition. It is a part of the " "normal operation of the rollback confirmed change." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_WARNING_IDLETIMER |
5-Notice |
User [chars] on tty [dec] has been idle for %lu minutes. System will rollback to config [chars] in oneminute if it continues to be idle. Enter \configure confirm\ if you wish to keep what you've configured |
Rollback will start in one minute. User could enter \configure confirm\ if they wish to keep what they've configured. |
- |
"This message DOES NOT denote any error condition. It is a part of the " "normal operation of the rollback confirmed change." |
|
ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_WARNING_IDLETIMER |
5-Notice |
User [chars] on tty [dec] has been idle for %lu minutes. System will rollback to config [chars] in oneminute if it continues to be idle. Enter \configure confirm\ if you wish to keep what you've configured |
Rollback will start in one minute. User could enter \configure confirm\ if they wish to keep what they've configured. |
- |
"This message DOES NOT denote any error condition. It is a part of the " "normal operation of the rollback confirmed change." |
|
ARCHIVE_ISSU-2-GET_BUFFER |
2-Critical |
Archive ISSU client failed to get buffer for message. Error: [dec] [chars] |
The Archive 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. |
parser |
"show logging and show checkpoint client" |
|
ARCHIVE_ISSU-2-INIT |
2-Critical |
Archive ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The Archive 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. |
parser |
LOG_STD_ACTION |
|
ARCHIVE_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
Archive ISSU client failed to send negotiation message. Error: [dec] [chars] |
The Archive 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. |
parser |
"show logging and show checkpoint client" |
|
ARCHIVE_ISSU-2-SESSION_NEGO_FAIL_START |
2-Critical |
Failed to start Archive ISSU session negotiation. Error: [dec] [chars] |
The Archive ISSU client failed to start session negotition. If a problem occurs with the ISSU session start the standby device cannot be brought up properly. |
parser |
"show issu session <client_id>" |
|
ARCHIVE_ISSU-2-SESSION_REGISTRY |
2-Critical |
Archive ISSU client failed to register session information. Error: [dec] [chars] |
The Archive ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
parser |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ARCHIVE_ISSU-3-INVALID_SESSION |
3-Error |
Archive ISSU client does not have a valid registered session. |
The Archive ISSU client does not have a valid registered session. |
parser |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ARCHIVE_ISSU-3-MSG_NOT_OK |
3-Error |
Archive ISSU client 'Message Type [dec]' is not compatible |
The Archive ISSU client received an incompatible message from the peer device. The message cannot be processed. |
parser |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
ARCHIVE_ISSU-3-MSG_SIZE |
3-Error |
Archive ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The Archive ISSU client failed to calculate the MTU for the specified message. The Archive ISSU client is not able to send the message to the standby device. |
parser |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
ARCHIVE_ISSU-3-SESSION_UNREGISTRY |
3-Error |
Archive ISSU client failed to unregister session information. Error: [dec] [chars] |
The Archive ISSU client failed to unregister session information. |
parser |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ARCHIVE_ISSU-3-TRANSFORM_FAIL |
3-Error |
Archive ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The Archive 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 Archive state between the active device and the standby device is not identical. |
parser |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
ARP-3-ARPHAMSGFMT |
3-Error |
Malformed ARP HA checkpointing message size = [dec] entry count = [dec]\n |
- |
- |
- |
|
ARP-3-ARPINIT |
3-Error |
Internal software error during ARP subsystem initialization\n |
An internal software error has occurred during ARP subsystem initialization. |
ip |
LOG_STD_RECUR_ACTION |
|
ARP-3-ARPINT |
3-Error |
ARP table accessed at interrupt level [dec]\n |
ARP table is accessed at interrupt level which is forbidden. |
ip |
LOG_STD_RECUR_ACTION |
|
ARP-3-ARPINVALIDEENTRY |
3-Error |
ARP system internal error. Returns NULL arp entry on node %p\n |
An internal software error has occurred in ARP subsystem an NULL arp entry is got. |
ip |
LOG_STD_RECUR_ACTION |
|
ARP-3-NULL_IF_INPUT |
3-Error |
ARP packet with NULL if_Input |
ARP received a packet with NULL input interface |
ip |
"If this message recurs call your technical support " "representative for assistance." |
|
ARP-3-STCKYARPOVR |
3-Error |
Attempt to overwrite Sticky ARP entry: [inet] hw: [enet] by hw: [enet]\n |
Multiple stations configured with same IP in Private VLAN. Possible case of IP address stealing. |
- |
"Change the IP address of one of the two systems." |
|
ARP-3-TABLEERR |
3-Error |
Internal software error during ARP table operation for ARP entry\n |
An internal software error has occurred during an ARP table operation. |
ip |
LOG_STD_RECUR_ACTION |
|
ARP-4-ARPADJ |
4-Warning |
Received CEF Adjacency updation request on different interfaces: [inet] on [chars]\n |
A request to update CEF adjacency came on two different interfaces. |
ip |
LOG_STD_RECUR_ACTION |
|
ARP-4-ARPLEARNTHRES |
4-Warning |
Learned ARP entries have reached to threshold level %lu |
This message indicates that the number of dynamically learned ARP entries has reached a preconfigured max. limit in ARP Table. |
- |
"First inspect the ARP entries on the interface. If they are " "valid entries either increase the configured max limit or " "reconfigure the network to reduce ARP peers." |
|
ARP-4-NULL_SRC_MAC |
4-Warning |
NULL MAC address from [inet] on [chars] |
Application or peer tried to insert entry with NULL SRC MAC |
ip |
"If this message recurs call your technical support " "representative for assistance." |
|
ARP-6-ARPLEARNRESUME |
6-Information |
Resuming Learn ARP entries to install in ARP table. |
This message indicates that the number of dynamically learned ARP entries is in range of permit threshold value.System is allowing new Learned ARP entries to install in ARP table. |
- |
LOG_STD_NO_ACTION |
|
ASPP-3-NOTTY |
3-Error |
[chars]: Unable to set Rx/Tx tty async service hooks. |
This message occurs only when ASP is configured. It\n\ indicates the serial interface using ASP is configured\n\ incorrectly or does not support asynchronous mode. |
- |
"Verify the correct hardware interface type is being used." |
|
ASR1000_PTP-3-FPGA_VER_ERR |
3-Error |
Please consider upgrading the FPGA for PTP to function properly. [chars] 0x[hec] |
Router is currently running on FPGA version which is lesser than what is required by PTP to work properly |
asr1000-ptp |
LOG_STD_ACTION |
|
ASR1000_PTP-3-MSGDISPATCH |
3-Error |
Unable to dispatch received TDL message from PTP daemon [chars] - [chars] |
An unexpected condition has occurred while IOS was trying to dispatch a TDL message received from PTP daemon. |
asr1000-ptp |
LOG_STD_ACTION |
|
ASR1000_PTP-3-MSGINITFAIL |
3-Error |
Failed to initalize required PTP resource: [chars] |
During the initialization of the resources required by PTP a failure occured. This has prevented PTP from being activated. |
asr1000-ptp |
LOG_STD_ACTION |
|
ASR1000_RP_ATM_SPA-3-ATM_DPIDB_ALLOC_FAIL |
3-Error |
Failed to allocate a data plane identifier for interface [chars] for VCD [dec] |
The SPA driver is not able to allocate the datapath identifier for the VCD under the interface specified in the message. This indicates a software error. |
ask1k-atm |
LOG_STD_NO_ACTION |
|
ASR1000_RP_ATM_SPA-3-ATM_DPIDB_GET_FAIL |
3-Error |
Failed to get a data plane identifier for interface [chars] for VCD [dec] |
The SPA driver is not able to obtain the datapath identifier for the VCD under the interface specified in the message. This indicates a software error. |
ask1k-atm |
LOG_STD_NO_ACTION |
|
ASR1000_RP_ATM_SPA-3-ATM_FLOWID_GET_FAIL |
3-Error |
Failed to get a flow control identifier for interface [chars] for index [dec] |
The SPA driver is not able to obtain the datapath flow control identifier for the data path identifier under the interface specified in the message. This indicates a software error. |
ask1k-atm |
LOG_STD_NO_ACTION |
|
ASR1000_RP_ATM_SPA-3-ATM_FLOWID_OUT_OF_RANGE |
3-Error |
Flow control identifiers for interface [chars] chan lo [hec] chan hi [hec] |
The flow control identifier received for the interface is out of range. This indicates SPA driver is responding with out of range flow control identifier |
asr1k-atm |
LOG_STD_ACTION |
|
ASR1000_RP_ATM_SPA-3-ATM_PER_SPA_MAX_VC_LIMIT_REACHED |
3-Error |
total active atm vc per ATM SPA reached limitation of [dec] |
total number of active atm vc per ATM SPA has reached max limit |
- |
LOG_STD_ACTION |
|
ASR1000_RP_ATM_SPA-3-ATM_SPA_AUTOVC_FAIL |
3-Error |
[chars]: atm autovc discovery configuration failed reason: [chars] |
A command to configure the atm autovc discovery on an atm interface has failed |
- |
LOG_STD_ACTION |
|
ASR1000_RP_ATM_SPA-3-ATM_SPA_VC_MAX_LIMIT_REACHED |
3-Error |
total active atm vc reached system limitation of [dec] |
total number of active atm vc has reached max limit allowed on the system |
- |
LOG_STD_ACTION |
|
ASR1000_RP_ATM_SPA-3-ATM_TXCHANL_GET_FAIL |
3-Error |
Failed to get a valid tx_chan id for interface [chars] for VCD [dec] |
The SPA driver is not able to obtain the datapath tx channel identifier for the VCD under the interface specified in the message. This indicates a SPA occur error. |
ask1k-atm |
LOG_STD_NO_ACTION |
|
ASR1000_RP_ATM_SPA-3-ATM_VC_CFG_SEND_FAIL |
3-Error |
Error in sending message to SPA on interface [chars] when [chars] for VCD [dec] ebfc_id [dec] |
The SPA give a error response for ATM setup or response timeout in atm vc setup message. This indicates a SPA occur error. |
ask1k-atm |
LOG_STD_NO_ACTION |
|
ASR1000_RP_ATM_SPA-3-ATM_VC_CON_SET_FAIL |
3-Error |
Failed set ATM con for interface [chars] [dec]/[dec] VCD [dec] |
Could not get VC encapsulation information when get SPA VCOPEN or VCMODFY response This indicates ATM occur error. |
ask1k-atm |
LOG_STD_NO_ACTION |
|
ASR1000_RP_ATM_SPA-3-ATM_VC_CORE_GET_FAIL |
3-Error |
Failed to get a ATM VC core info for interface [chars] VCD [dec] |
Could not get VC core information when get SPA VCOPEN or VCMODIRY response. This indicates a ATM information error. |
ask1k-atm |
LOG_STD_NO_ACTION |
|
ASR1000_RP_ATM_SPA-3-ATM_VC_DPIDX_GET_FAIL |
3-Error |
Failed to get ATM dpidx for interface [chars] VCD [dec] |
Could not get VC dpidx information when get SPA VCOPEN or VCMODFY response This indicates ATM occur error. |
ask1k-atm |
LOG_STD_NO_ACTION |
|
ASR1000_RP_ATM_SPA-3-ATM_VC_EGRESSID_UPDATE_FAIL |
3-Error |
Failed to update ATM egress id for interface [chars] VCD [dec] egress_id [dec] |
Could not update VC egress id when get SPA VCOPEN or VCMODFY response This indicates ATM occur error. |
ask1k-atm |
LOG_STD_NO_ACTION |
|
ASR1000_RP_ATM_SPA-3-ATM_VC_ENCAP_GET_FAIL |
3-Error |
Failed to get ATM encapsulation for interface [chars] [dec]/[dec] VCD [dec] |
Could not get VC encapsulation information when get SPA VCOPEN or VCMODFY response This indicates ATM occur error. |
ask1k-atm |
LOG_STD_NO_ACTION |
|
ASR1000_RP_ATM_SPA-3-ATM_VC_ERROR_ENCAP_TYPE |
3-Error |
Get ATM ERROR encapsulation for interface [chars] [dec]/[dec] VCD [dec] |
Get a ERROR VC encapsulation information when get SPA VCOPEN or VCMODFY response This indicates ATM occur error. |
ask1k-atm |
LOG_STD_NO_ACTION |
|
ASR1000_RP_ATM_SPA-3-ATM_VC_INGRESS_ID_ALLOC_FAIL |
3-Error |
Failed to allocate VC ingress identifier on interface [chars] for VCD [dec] ebfc_id [dec] when [chars] |
The ATM SHIM is not able to allocate the ingress identifier for the VCD under the interface specified in the message. This indicates a software error. |
ask1k-atm |
LOG_STD_NO_ACTION |
|
ASR1000_RP_ATM_SPA-3-ATM_VC_SPA_SETUP_FAIL |
3-Error |
SPA Error response on interface [chars] when [chars] for VCD [dec] ebfc_id [dec] ret_val [dec] |
The SPA give a error response for ATM setup or response timeout in atm vc setup message. This indicates a SPA occur error. |
ask1k-atm |
LOG_STD_NO_ACTION |
|
ASR1000_RP_ATM_SPA-3-PROCESS_FAIL |
3-Error |
process creation failed for [chars] |
The Periodic one second process creation failed. This indicates a software error. |
asr1k-atm |
LOG_STD_ACTION |
|
ASR1000_RP_ATM_SPA-4-ATM_SPA_VC_ABOVE_WM_WARNING |
4-Warning |
total active atm vc approaching [dec] percent of system limitation of [dec] |
total number of active atm vc is approaching the high water mark of sysyem limitation |
- |
LOG_STD_ACTION |
|
ASR1000_RP_ATM_SPA-4-SETUPVC |
4-Warning |
Interface [chars] VC [dec] setup failed reason = [dec] |
A command to setup a VC has failed on RP. |
asr1k-spa-atm |
"The SPA ATM driver has detected a problem creating the internal OAM" "VC. Reload the indicated SPA card to reconfigure the internal OAM VC." "If the error messages persists copy the error message exactly as " "it appears. Next research and attempt to resolve the issue using " "the SPA hardware troubleshooting documentation as well as the tools " "and utilities provided at " "http://www.cisco.com/public/support/tac/tools.shtml. If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a 'show tech-support' to " "your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
ASR1000_RP_ATM_SPA-4-TEARDOWNVC |
4-Warning |
Interface [chars] VC [dec] teardown failed vc state = [dec]/[dec] |
A command to remove a VC config has failed on RP. |
asr1k-spa-atm |
"The SPA ATM driver has detected a problem tearing down the internal" "OAM VC. Reload the indicated SPA card to do a clean tear down of the " "internal OAM VC. If the error messages persists copy the error " "message exactly as it appears. Next research and attempt to resolve " "the issue using the SPA hardware troubleshooting documentation as well" " as the tools and utilities provided at " "http://www.cisco.com/public/support/tac/tools.shtml. If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a 'show tech-support' to " "your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
ASR1000_RP_ATM_SPA-5-ATM_SPA_VC_BELOW_WM_NOTICE |
5-Notice |
total active atm vc below [dec] percent of system limitation of [dec] |
total number of active atm vc below the high water mark of sysyem limitation |
asr1k-atm |
LOG_STD_ACTION |
|
ASR1000_RP_ATM_SPA-5-MPVCVPSETUP |
5-Notice |
Interface [chars] has a VC/VP [dec] configured already VC/VP [dec] cannot |
The SPA ATM driver supports configuring only one VC/VP under a point to multi point sub-interface. The sub-interface specified in the message already has VP/VC configured. |
- |
LOG_STD_NO_ACTION |
|
ASR1000_RP_CTE1_SPA-3-CCIPCFAIL |
3-Error |
Communication with the CC has failed for Interface [dec]/[dec] |
Communication with Card-Carrier down. |
mcp-io |
"Either try to configure the Sharded Port Adapter at a later time or " "reload the Card Carrier." |
|
ASR1000_RP_CTE1_SPA-3-IPCERR |
3-Error |
Internal IPC error [chars] |
Internal IPC error. |
mcp-io |
"Either try to configure the Sharded Port Adapter at a later time or " "reload the SPA and/or Card Carrier." |
|
ASR1000_RP_CTE1_SPA-3-UNSUPERR |
3-Error |
NULL |
An internal error as resulted from an unsupported or unexpected message. |
mcp-io |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
ASR1000_RP_POS_SPA-4-ALLOCFAIL |
4-Warning |
Interface [dec]/[dec] allocation failed: [chars] |
required resources unavailable. |
mcp-io |
"Either upgrade system memory or reconfigure memory usage." |
|
ASR1000_RP_POS_SPA-4-APSGETFAIL |
4-Warning |
Interface [chars] |
failed to get aps state from cc |
asr1k-spa-pos |
"Copy the error message exactly as it appears on the console\n\ or in the system log. Call your Cisco technical support\n\ representative and provide the representative\n\ with the gathered information." |
|
ASR1000_RP_POS_SPA-4-SFSDTHRESHOLDFAIL |
4-Warning |
Interface [chars] |
failed to update CC about BER_SF_SD thresholds |
asr1k-spa-pos |
"Copy the error message exactly as it appears on the console\n\ or in the system log. Call your Cisco technical support\n\ representative and provide the representative\n\ with the gathered information." |
|
ASR1000_SIP_CTE1_SPA-3-TDL_ARG_ERR |
3-Error |
Interface [dec]/[dec]/[dec]: Bad parameter in message from RP: [chars] |
Bad parameter in message from RP. |
mcp-io |
"Either try to configure the Sharded Port Adapter at a later time or " "reload the Card Carrier." |
|
ASR1000_SIP_CTE1_SPA-3-UNSUPERR |
3-Error |
NULL |
An internal error as resulted from an unsupported or unexpected message. |
mcp-io |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
ASR1000_SIP_POS_SPA-3-APS |
3-Error |
APS[dec] [chars] |
RP deadman timer expired on CC CC is sending LAIS to far end |
mcp-io |
"Copy the error message exactly as it appears on the console \n\ or in the system log. Call your Cisco technical support \n\ representative and provide the representative \n\ with the gathered information." |
|
ASR1000_SIP_POS_SPA-4-ALLOCFAIL |
4-Warning |
SPA resource allocation failed for subslot [dec]/[dec] while [chars] |
The SPA driver in the subslot specified in the message is\n\ not able to allocate a system resource. The required system resource is\n\ specified in the message. |
mcp-io |
"Copy the error message exactly as it appears on the console \n\ or in the system log. Call your Cisco technical support \n\ representative and provide the representative \n\ with the gathered information." |
|
ASR1000_SPA_ETHER_DAMSELFLY-3-PLIM_QOS |
3-Error |
Interface [chars] failed to apply PLIM QOS [chars] value = 0x%X |
Attempt to apply the configured input classification for the specified interface failed |
asr1k-io-internal |
"This indicates an internal software failure" |
|
ASR1000_SPA_ETHER_DAMSELFLY-3-UNSUPPORTED_XCVR |
3-Error |
Transceiver type [chars] is not allowed on spa [chars] port [dec] |
This transceiver is not allowed on the SPA |
asr1k-io-internal |
"Consult the documentation and ensure supported " "transceivers and plugged into the SPA" |
|
ASR1000_SPA_ETHER_LC-3-NP_HW_SW_MISMATCH |
3-Error |
The hardware and software copies of NP client do not match. This indicates reconciliation failure. |
During reconcilation phase of Minimal Disruptive Restart it is found that the software and hardware copies of a register in phy do not match. This indicates an error and the SPA will be reset as normal and impact traffic. |
asr1k-ether-lc |
"Open a case with Cisco Technical Assistance Center for further " "assistance" |
|
ASR1000_SPA_ETHER_LC-3-PHY_HW_SW_MISMATCH |
3-Error |
The hardware and software copies of a register in the phy for port [dec] do not match. This indicates reconciliation failure. |
During reconcilation phase of Minimal Disruptive Restart it is found that the software and hardware copies of a register in phy do not match. This indicates an error and the SPA will be reset as normal and impact traffic. |
asr1k-ether-lc |
"Open a case with Cisco Technical Assistance Center for further " "assistance" |
|
ASR1000_SPA_ETHER-3-HSRPDA_TCAM_REGION_FULL |
3-Error |
Failed to add in HSPRDA region for interface [chars] |
The TCAM HSRPDA table on the SPA is full The specified HSRPDA identifier will not be added to the TCAM table. |
mcp-io |
"Try to remove some of the Virtual MAC addresses for the interface by " "command." |
|
ASR1000_SPA_ETHER-3-TCAM_QINQ_VLAN_ERROR |
3-Error |
Failed to [chars] VLAN outer [dec] inner [dec]-[dec] to/from interface [chars] status = [dec] |
The access to update the TCAM VLAN filtering table on the SPA failed. The error message indicates the SPA subslot and the affected interface and the VLAN entry that failed. |
mcp-io |
LOG_STD_ACTION |
|
ASR1000_SPA_ETHER-3-TCAM_QINQ_VLAN_TABLE_FULL |
3-Error |
Failed to add VLAN outer [dec] inner [dec]-[dec] to interface [chars] |
The TCAM VLAN filtering table on the SPA is full. The error message indicates the SPA subslot and the affected interface and the VLAN entry that failed. The specified VLAN identifier will not be added to the TCAM table. |
mcp-io |
"Try to remove some of the registered VLANs for the interface by " "changing the interface configuration. To verify the VLAN IDs currently " "in use by an interface enter the <CmdBold>show vlans<NoCmdBold> " "command." |
|
ASR1000_SPA_ETHER-3-TCAM_VLAN_ERROR |
3-Error |
Failed to [chars] VLAN [dec] to/from interface [chars] status = [dec] |
The access to update the TCAM VLAN filtering table on the SPA failed. The error message indicates the SPA subslot and the affected interface and the VLAN entry that failed. |
mcp-io |
LOG_STD_ACTION |
|
ASR1000_SPA_ETHER-3-TCAM_VLAN_TABLE_FULL |
3-Error |
Failed to add VLAN [dec] to interface [chars] |
The TCAM VLAN filtering table on the SPA is full. The error message indicates the SPA subslot and the affected interface and the VLAN entry that failed. The specified VLAN identifier will not be added to the TCAM table. |
mcp-io |
"Try to remove some of the registered VLANs for the interface by " "changing the interface configuration. To verify the VLAN IDs currently " "in use by an interface enter the <CmdBold>show vlans<NoCmdBold> " "command." |
|
ASR900_PLATFORM-3-BP_AUTH_FAIL |
3-Error |
Failed to Authenticate the backplane quack deivice. This device may not be a quacked properly or not CISCO manufactured. |
During the router boot-up we check if this router is cisco manufactured or not. If this device is not quacked properly or not CISCO manufactured this error is expected. |
asr900-csl |
LOG_STD_ACTION |
|
ASR900_PLATFORM-3-PUNT_KEEPALIVE_PROP_CREATE_ERR |
3-Error |
Failed to create chasfs property [chars] rc=[dec] |
Failure occured while creating chasfs property |
asr900-system-rsp3 |
LOG_STD_ACTION |
|
ASR900_PLATFORM-3-PUNT_KEEPALIVE_PROP_SET_ERR |
3-Error |
Failed to set chasfs property [chars] with [chars] rc=[dec] |
Failure occured while updating chasfs property |
asr900-system-rsp3 |
LOG_STD_ACTION |
|
ASR900_PROTECTION-3-TDL_MSG_FAIL |
3-Error |
Failed to send the protection-physical [chars] TDL msg for protection interface [chars] and member [chars] |
Whenever there is any error while sending the TDL msg for binding/unbinding a physical controller with UPSR/ACR controller |
asr900-protection |
LOG_STD_ACTION |
|
ASR900_PTP-3-MSGDISPATCH |
3-Error |
Unable to dispatch received TDL message from PTP daemon |
An unexpected condition has occurred while IOS was trying to dispatch a TDL message received from PTP daemon. |
asr900-ptp |
LOG_STD_ACTION |
|
ASR900_PTP-3-MSGINITFAIL |
3-Error |
Failed to initalize required PTP resource: [chars] |
During the initialization of the resources required by PTP a failure occured. This has prevented PTP from being activated. |
asr900-ptp |
LOG_STD_ACTION |
|
ASR900_RP_ATM_SPA-3-ATM_PER_SPA_MAX_VC_LIMIT_REACHED |
3-Error |
total active atm vc per ATM SPA reached limitation of [dec] |
total number of active atm vc per ATM SPA has reached max limit |
- |
LOG_STD_ACTION |
|
ASR900IM-3-DIFF_IM_INSERTED |
3-Error |
[chars] - [chars] in bay [dec] |
A different IM type has been inserted in the bay which previously had another IM type. If the interfaces were set to default before swap the IM will boot up fine. If not IM will goto Out-of-service state. Kindly insert the previous IM type use hw-module subslot 0/x default and then proceed with the IM swap. If not might need to reload the box for recovery |
- |
- |
|
ASR900IM-3-INCOMPATIBLE |
3-Error |
[chars]-[dec] |
P1D and onwards Cu IM.... is not backward compatible with P1A/P1B/P1C Cu IM use the same build of Cu IM or reload the router to use the new build. |
- |
- |
|
ASR900IM-3-INVALID_COMBINATION |
3-Error |
[chars] is not allowed in bay [dec] can be supported only in bays [chars] |
The inserted IM is not supported in the specified subslot given the combination of existing IMs in the chassis. |
- |
- |
|
ASR900IM-3-INVALID_MODE |
3-Error |
[chars] with mode [chars] is not allowed in bay [dec] can be supported only in bays [chars] |
The inserted IM is not supported in the specified subslot given the combination of existing IMs in the chassis. |
- |
- |
|
ASR900IM-3-UNSUPPORTED |
3-Error |
This Interface Module is not supported in subslot [dec] |
The inserted IM is not supported in the specified subslot. Kindly check the supported slots for the IM type. |
- |
- |
|
ASR900IM-3-UNSUPPORTED_DYING_GASP |
3-Error |
Command rejected Cannnot co-exist with [chars] present in subslot [dec]. Please retry after removing IM and rebooting. |
The inserted IM cannot co-exist in the specified subslot after enabling dying gasp internal port. Kindly check the supported slots for the IM type. |
- |
- |
|
ASR900IM-3-UNSUPPORTED_IPSEC |
3-Error |
[chars] will not be operational in subslot [dec] after reboot due to payload encryption support with IPsec license |
The inserted IM will not be supported in the specified subslot after reboot due to payload encryption support with IPsec license. Kindly check the supported slots for the IM type. |
- |
- |
|
ASR900IM-3-UNSUPPORTED_PLATFORM |
3-Error |
This Interface Module is not supported in [chars] platform |
The inserted IM is not supported in the specified platform |
- |
- |
|
ASR900INTF-3-UNSUPPORTED |
3-Error |
Interface [chars] is not supported in subslot [dec] by the [chars] module |
The Interface specified in the error message is not supported in the specified Subslot by the version of the operating system currently running on the system. |
- |
- |
|
ASR903_CFC-3-PUNT_KEEPALIVE_ERR_ALLOC_CSB |
3-Error |
Failed to allocate a csb |
Can't allocate a csb when generating punt err log |
asr903-cfc |
LOG_STD_ACTION |
|
ASR903_CFC-3-PUNT_KEEPALIVE_ERR_ALLOC_TTY |
3-Error |
Failed to allocate a tty |
Can't allocate a TTY when generating punt err log |
asr903-cfc |
LOG_STD_ACTION |
|
ASR903_CFC-3-PUNT_KEEPALIVE_ERR_OPEN_FILE |
3-Error |
Failed to open file: [chars] |
Failed to open file when generating punt err log |
asr903-cfc |
LOG_STD_ACTION |
|
ASR903_CFC-3-PUNT_KEEPALIVE_ERR_WRITE_TO_FILE |
3-Error |
Write to file Id [dec] failed [dec] bytes expected [dec] bytes |
Write to file failed when generating punt err log |
asr903-cfc |
LOG_STD_ACTION |
|
ASR903_CFC-4-PUNT_KEEPALIVE_ERR_CLOSE_FILE |
4-Warning |
Failed to close file with descriptor: [dec] |
Closing of file failed when generating punt err log |
asr903-cfc |
LOG_STD_ACTION |
|
ASR903_CFC-4-PUNT_KEEPALIVE_ERR_GET_FILE_NAME |
4-Warning |
Failed to get file name |
Could not form a file name when generating punt err log |
asr903-cfc |
LOG_STD_ACTION |
|
ASR903_CFC-4-PUNT_KEEPALIVE_ERR_INV_FILE_ID |
4-Warning |
Invalid file descriptor: [dec] |
Invalid file descriptor was found when generating punt err log |
asr903-cfc |
LOG_STD_ACTION |
|
ASR903_CFC-4-PUNT_KEEPALIVE_ERR_INV_PARAM |
4-Warning |
Invalid parameter: [chars] |
Invalid parameter was passed when generating punt err log |
asr903-cfc |
LOG_STD_ACTION |
|
ASYNC_IF-0-DSR_READ_FAIL |
0-Emergency |
Failed to read DSR state.. |
Failed to read DSR Data Set Ready state. |
IIOT_COMPONENT |
LOG_ERR |
|
ASYNC_IF-0-DTR_SET_FAIL |
0-Emergency |
Failed to set DTR state.. |
Failed to set DTR Data Terminal Ready state. |
esr6k3-async |
LOG_ERR |
|
AT-1-NOMEM |
1-Alert |
Could not allocate memory for [chars] at line [dec] in [chars] |
An internal software error occurred. |
atalk |
LOG_STD_SH_TECH_ACTION |
|
AT-2-ASSERTFAILED |
2-Critical |
AppleTalk assertion failed: [chars] |
The software detected an inconsistency. Although this error is serious the router attempts to continue. AppleTalk processing might be impaired. |
atalk |
"Copy the message exactly as it appears note any AppleTalk problems " "you experience and call your technical support representative." |
|
AT-3-DOMLOOP |
3-Error |
Loop detected on domain [dec] [[chars]] |
The domain router detected a routing loop. Routing loops are not allowed. The domain router runs a background loop detection process. The domain router starts this process when it receives a new zone list from a domain that is identical to the list in the main routing table and whose network range length matches that in this list. The loop detection process sends several AppleTalk NBP loopback packets. When one of these packets is received on an interface that does not belong to the original domain the domain router first shuts off all the domains involved in the loop and then shuts off all the interfaces in these domains. The loop detection does not catch all types of loops. It is your responsibility to make sure that no loop exists. |
atalk |
"Disable the cause of the routing loop. Then use the clear appletalk " "command to restart the interfaces involved." |
|
AT-3-DOMOVERFLOW |
3-Error |
Remap range overflow for [chars] domain [dec] |
The remap range overflowed. If a network range cannot fit inside the |
atalk |
"Use the appletalk domain remap-range command to increase the remapping " "range. Then restart the interfaces." |
|
AT-3-INVNBPCMD |
3-Error |
Invalid NBPtest command [chars] |
An unrecognized command was specified in the Name Binding Protocol NBP test facility. |
atalk |
"Enter a valid command." |
|
AT-3-NOBESTPATH |
3-Error |
Could not compute best path for network %#A |
A path to the specified network could not be found. |
atalk |
"Use the show appletalk route command to verify that a path to the " "specified network exists. If it does copy the error message exactly " "as it appears and report it along with the output of the show " "appletalk route command to your technical support representative." |
|
AT-3-NOROUTE |
3-Error |
No route to destination [atalk_address] |
You attempted to remove a route from the routing table by issuing the clear appletalk route command. The command failed because the route was on a directly connected interface that is it was created when you configured the router. |
atalk |
"Remove the route by reconfiguring the directly connected interface " "with which it is associated." |
|
AT-3-NOSOCKET |
3-Error |
[chars]: client tried to open socket but failed |
- |
- |
- |
|
AT-3-NOSUCHNBR |
3-Error |
No such neighbor %#a |
You specified a nonexistent neighbor address in a show appletalk neighbor or clear appletalk neighbor. |
atalk |
"Specify a valid neighbor address that is one that appears in the " "output of the show appletalk neighbor command." |
|
AT-3-NOTRUNNING |
3-Error |
AppleTalk not running |
An AppleTalk interface that was previously shut down was restarted. |
atalk |
LOG_STD_NO_ACTION |
|
AT-3-NOVIRTUAL |
3-Error |
[chars]: client tried to connect but no virtual network is declared |
A hardware or software error occurred. |
atalk |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
AT-3-OUTOFSYNC |
3-Error |
[chars]: AURP connection out of sync...terminating |
The router detected a conflicting cable range. A router is configured with a cable range that overlaps with an existing range but does not match the entry exactly. |
aurp |
"Use the show appletalk command to identify the overlapped cable range " "and then reconfigure the misconfigured router." |
|
AT-3-SUBROUTINE_ERROR |
3-Error |
AppleTalk error: [chars] |
An internal error occurred. Specifically a programming assertion in the AppleTalk networking code was violated. |
atalk |
LOG_STD_ACTION |
|
AT-4-MACIPBADCONF |
4-Warning |
[chars]: MacIP inoperable configuration [inet] |
If the appletalk event-logging command is configured this message appears on the console when a MacIP server cannot begin or recover operations because of an invalid IP address configuration. This condition only occurs when the configured MacIP server's IP address is not valid on the same cable of any operable IP interface. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command. When this error occurs the MacIP configuration is considered invalid and is deleted. |
atalk |
LOG_STD_NO_ACTION |
|
AT-4-MACIPNOCABLE |
4-Warning |
[chars]: MacIP inoperable IP interface [inet] |
If the appletalk event-logging command is configured this message appears on the console when a MacIP server can no longer operate due to a change in the condition of the IP interface it serves. This condition can occur if IP routing is shut down on the interface or the IP address of the interface is changed so that the MacIP server's IP address is no longer valid on the same cable. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command. |
atalk |
LOG_STD_NO_ACTION |
|
AT-5-COMPATERR1 |
5-Notice |
[chars]: AppleTalk internet compatibility mode required by %#a |
Although this router has neighbors that require your internetwork to observe compatibility rules AppleTalk has learned of a route that has a cable range greater than 1. This condition can cause node inconsistencies on your AppleTalk network. |
atalk |
"Upgrade the routers that support only the original AppleTalk " "specification. In the meantime observe the compatibility rules " "for AppleTalk Phase 1 and Phase 2 routers." |
|
AT-5-FDDICOMPAT |
5-Notice |
AppleTalk FDDI neighbor %#a using obsolete FDDI addressing |
An attempt was made to configure an interface to have the same or a conflicting AppleTalk address or cable range as another interface on the same router. |
atalk |
"Verify that you are not specifying an AppleTalk address or cable range " "used previously on this router and reconfigure the interface." |
|
AT-5-NOSUCHROUTE |
5-Notice |
No such route [dec] |
You specified a nonexistent route in a show appletalk route or clear appletalk route command. |
atalk |
"Specify a valid route that is one that appears in the output of the " "show appletalk route command." |
|
AT-5-PATHCHANGE |
5-Notice |
Route to %#A is now using path of type [chars] on [chars] via %#a |
The path to a network changed because either the old path went down or the new path was better. |
atalk |
LOG_STD_NO_ACTION |
|
AT-5-RTMPSTATE |
5-Notice |
[chars]: RTMP path to %#A via %#a now in [chars] state metric [dec] [dec] hops |
A new AppleTalk path has been learned. The message indicates the source of the path its distance in hops its metric and the type of path. |
atalk |
LOG_STD_NO_ACTION |
|
AT-6-BADROUTE |
6-Information |
Route to %#A has gone bad |
The system did not detect a route within the required timeout period. Therefore the route is marked as bad. A network might have become unreachable for some reason perhaps because of a broken connection. This message does not necessarily indicate an error condition. |
atalk |
LOG_STD_NO_ACTION |
|
AT-6-MACIPDOWN |
6-Information |
[chars]: MacIP server shutting down [inet] |
If the appletalk event-logging command is configured this message appears on the console when a MacIP server is no longer operational for any reason. MacIP servers shut down in response to MacIP configuration changes or errors or a change in the condition or configuration of an AppleTalk or IP interface for which the MacIP server is providing service. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command. |
atalk |
LOG_STD_NO_ACTION |
|
AT-6-MACIPUP |
6-Information |
[chars]: MacIP server operational [inet] |
If the appletalk event-logging command is configured this message appears on the console when a MacIP server is fully initialized and is ready to accept client requests. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command. |
atalk |
LOG_STD_NO_ACTION |
|
AT-6-NBRDELETED |
6-Information |
Neighbor entry for %#a deleted |
The clear appletalk neighbor command displays this command when it completes successfully. |
atalk |
LOG_STD_NO_ACTION |
|
AT-6-PATHDEL |
6-Information |
[chars]: AppleTalk [chars] path to %#A via %#a has been deleted |
An AppleTalk node sent a GetNet Info request to this router specifying an invalid network number for the source of the GetNet Info request. This situation occurs when an AppleTalk end node is moved to another network and is therefore misconfigured for the current network. |
atalk |
LOG_STD_NO_ACTION |
|
AT-6-REGPENDING |
6-Information |
NBP registration of [chars] at [[chars]] pending |
A name registration call is being performed. |
atalk |
LOG_STD_NO_ACTION |
|
AT-7-BUGREPORT |
7-Debug |
AppleTalk bug: [chars] |
The software detected an unexpected condition. The router takes corrective action and continues. |
atalk |
"Copy the message exactly as it appears note any AppleTalk problems " "you experience and call your technical support representative." |
|
AT-7-DEBUGMSG |
7-Debug |
AppleTalk debug: [chars] |
This message is generated by a debug command and provides additional information about an AppleTalk condition. |
atalk |
"Copy the message exactly as it appears note any AppleTalk problems " "you experience and call your technical support representative." |
|
ATA-3-ATA_STATUS_ERROR |
3-Error |
Error occurred while querying the status of ATA device. Return: [dec] stat_reg: 0x[hec] |
An error occurred while querying the status of ATA device. Device not responding |
ata-filesystem |
"Replace the new ATA device and retry the operation. " "If the problem persists " "1 Run 'show tech' command." |
|
ATA-6-ATA_STATUS_TIMEOUT |
6-Information |
Timeout occurred while querying the status of ATA device. Status returned :0x[hec] event: [dec] |
A timeout occurred while querying the status of ATA device. |
- |
"Replace the new ATA device and retry the operation. " "If the problem persists " "1 Run 'show tech' command." |
|
ATM-1-ISSU_NOMEMORY |
1-Alert |
msgtxt_nomemory |
The requested operation could not be accomplished because of a low\n\ memory condition. |
atmcommon |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
ATM-1-NOPUSRAM |
1-Alert |
Unit [dec] not enough interface memory |
The specified ATM interface hardware has run out of interface memory. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATM-2-FAILATMSWDB |
2-Critical |
Fail malloc atm_swdb at [chars] |
System memory exhaustion caused an internal software error in the ATM subsystem. |
- |
"If the system exhibits any unexpected behavior as a result of " "this memory exhaustion it may need to be reset to clear the error." LOG_STD_REDUCE_ACTION |
|
ATM-3-ATM_WAVL_TREE_ERROR |
3-Error |
ATMNode1 [chars] VCD [dec] [dec]/[dec] Node2 [chars] VCD [dec] [dec]/[dec] |
A software error occured. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATM-3-FAILCREATEVC |
3-Error |
ATM failed to create VCVCD=[dec] VPI=[dec] VCI=[dec] on Interface [chars] Cause of the failure: [chars] |
- |
- |
- |
|
ATM-3-FAILREMOVESERVICEPOLICYONATMVC |
3-Error |
ATM failed to remove service policy on VCVCD=[dec] VPI=[dec] VCI=[dec] on Interface [chars] Cause of the failure: [chars] |
The DSL line rate has been changed for the PVC to support the guaranteed bandwidth configured for the virtual circuits. |
atmcommon |
LOG_STD_ACTION |
|
ATM-3-FAILREMOVEVC |
3-Error |
ATM failed to remove VCVCD=[dec] VPI=[dec] VCI=[dec] on Interface [chars] Cause of the failure: [chars] |
- |
- |
- |
|
ATM-3-ILMIINTERNALERR |
3-Error |
[chars] [chars]:[dec] |
Internal Error see message occurs during ILMI Primary to Secondary Sync |
as |
LOG_STD_SH_TECH_ACTION |
|
ATM-3-ILMISYNCINTERNERR |
3-Error |
[chars] [chars]:[dec] |
Internal Error see message occurs during ILMI Primary to Secondary Sync |
as |
LOG_STD_SH_TECH_ACTION |
|
ATM-3-ILMISYNCINTFERR |
3-Error |
[chars] [%08X=[chars]] [chars]:[dec] |
Internal Error see message occurs during ILMI Primary to Secondary Sync |
as |
LOG_STD_SH_TECH_ACTION |
|
ATM-3-ISSU_SENDFAILED |
3-Error |
\nATM ISSU: send message failed rc = [dec]\n |
The sending of a message has failed. |
atmcommon |
LOG_STD_SH_TECH_ACTION |
|
ATM-3-MLPDEQUEUE |
3-Error |
MLPPP failed CosQ=[hec] MLP=[hec] OQDQ=[hec] [hec] Cause of the failure: [chars] |
- |
- |
- |
|
ATM-3-MLPOATM_ERROR |
3-Error |
MLPoATM not configured properly on \n\ Link [chars] Bundle [chars] :[chars] |
The configuration of MLPPP-over-ATM MLPoATM on the ATM PVC is either incorrect or incomplete. |
atmcommon |
"Ensure that the service policy has been attached to " "the Virtual Template and that the queueing strategy on the ATM interface " "is per VC queueing and queueing algorithm is FIFO. To verify the " "configuration use the <CmdBold>show inteface atm <noCmdBold> and " "<CmdBold>show running-config virtual-template<noCmdBold> commands." |
|
ATM-3-OUT_OF_VCDS |
3-Error |
ATM failed to create VC on Interface [chars] |
The ATM subsystem ran out of internal resources necessary to create a new virtual circuit. This may indicate a software error. |
- |
LOG_STD_ACTION |
|
ATM-3-OVERSUBSCRIBED |
3-Error |
Interface [chars]: Total [chars] allocation [dec][chars] exceeded maximum [chars] of [dec][chars]. |
A software or hardware error occurred. |
- |
LOG_STD_ACTION |
|
ATM-3-PPPOEOA_VCFLAG |
3-Error |
ATM: [chars] PVC [dec]/[dec] : Error in PPPoE flag |
The ATM PVC PPPoE flag is still set while it should not be set. ATM uses a flag to indicate whether or not it should process PPPoE frames. In some rare conditions the flag can still be set for ATM to process PPPoE frames while it should not be. This condition can cause PPPoE frames to be processed when they should be dropped. |
atmcommon |
"In most cases no action is required as the system will set the flag " "so that ATM will not process PPPoE frames and the system " "will continue to operate normally. However If the ATM PVC " "specified in the error message is repeatedly experiencing problems " "involving PPPoE unconfigure all commands under the PVC " "and remove and then reconfigure the PVC. Enter the " "<CmdBold>interface atm<NoCmdBold> interface.subinterface-number " "command in global configuration mode to enter atm interface " "configuration mode. Then specify the PVC you would like to " "unconfigure and enter the <CmdBold>no encapsulation<NoCmdBold> " "command. Specify the PVC you just unconfigured then reconfigure " "the PVC using the <CmdBold>encapsulation<NoCmdBold> command." |
|
ATM-3-REJECTVC |
3-Error |
ATM failed to create VCVCD=[dec] VPI=[dec] VCI=[dec] on Interface [chars] Cause of the failure: [chars] |
- |
- |
- |
|
ATM-3-UNSUPPORTED_QOS_PARAMS |
3-Error |
ATM failed to create VC on Interface [chars] |
Either the configuration contains invalid traffic shaping parameters or the software ran out of rate queues. |
- |
"Check the configuration for errors." |
|
ATM-4-ILMICONFIGCHANGE |
4-Warning |
ILMI[chars]: Restarting ATM signalling and ILMI. Peer Configuration change detected. |
Configuration of adjacent peer device has been changed. |
- |
"Wait for the interface to restart itself." |
|
ATM-4-ILMIKEEPALIVEFAIL |
4-Warning |
ILMI[chars]: Restarting ATM signalling and ILMI. Keepalive failure detected. |
Adjacent peer device is not responding to ILMI Keepalive polling. |
- |
"Check the connection of the ATM interface and the status of the " "adjacent peer device. Correct them if neccessary. Wait and check " "if ILMI Keepalive comes up again. If the problem persists " "copy this warning message exactly as it appears and report it to " "your technical support representative." |
|
ATM-4-ILMISYNCINTFWARN |
4-Warning |
[chars] [%08X=[chars]] [chars]:[dec] |
Recoverable Internal Error see message occurs during ILMI Primary to Secondary Sync |
as |
LOG_STD_SH_TECH_ACTION |
|
ATM-4-ISSU_INCOMPATIBLE |
4-Warning |
\natm-issu-compat: returned FALSE |
The compatibility checking has failed |
atmcommon |
LOG_STD_SH_TECH_ACTION |
|
ATM-4-ISSU_XFORM |
4-Warning |
\n[chars]: failed rc=[chars] |
The transform has failed. |
atmcommon |
LOG_STD_SH_TECH_ACTION |
|
ATM-4-MTUCALLMISMATCH |
4-Warning |
Call from: \n ATM NSAP - [chars]\n has mismatched PDU size - forward size is [dec]\n - backward size is [dec]\n int [chars] PDU size [chars] [chars] |
The calling or called party has a maximum transmission unit MTU size |
- |
"Either change the configured MTU size on the current interface to that " "of the caller's or called party's interface or change the caller's or " "called party's interface to match the current interface." |
|
ATM-4-STUCK_VCD |
4-Warning |
clearing stuck VCD [dec] from map on [chars] |
A SVC map entry has a stuck VCD attached to it which has been previously cleared in the driver. |
- |
"No action required as the stuck VCD condition is detected " "and cleared." |
|
ATM-4-UNMATCHUNIVERSION |
4-Warning |
[dec]/[dec]/[dec]:[dec]: [chars]. Please verify peer UNI version |
The ATM peer equipment appears to be running an old version of ATM UNI. Communication with it is not possible. |
- |
"The peer equipment needs to be upgraded in " "order to communicate with this system." |
|
ATM-4-VPIVCIRANGE |
4-Warning |
VPI/VCI range parameters are dis-joint on [chars] |
MinSvccVci > MaxVci after negotiation with the peer through ILMI. |
- |
"Disable auto-cinfiguration on both sides and change the " "port configuration appropriately so that SVCCs can be setup." |
|
ATM-5-ATMSOFTSTART |
5-Notice |
Restarting ATM signalling and ILMI on [chars]. |
The command just entered causes ATM Soft Restart. |
- |
"Stand by and let ATM Signalling and ILMI to restart." |
|
ATM-5-ILMIACCFILTER |
5-Notice |
New access filter setting will be applied to registration of new addresses on [chars]. |
The command just entered sets up new ilmi access filter for address registration. It only affects new addresses to be registered. The addresses already registered will not be affected. |
- |
"Enter the shutdown and no shutdown commands on this interface to " "restart address registration if need to remove addresses already " "registered but not permitted by the new access filter." |
|
ATM-5-ILMIADDREG |
5-Notice |
Address registration on [chars] is enabled. |
The command just entered enables atm address registration. |
- |
"No action required." |
|
ATM-5-ILMIDEFACCFILTER |
5-Notice |
New global default access filter setting will be applied to registration of new addresses on interfaces using global default access filter. |
The command just entered sets up new global default access filter for addres registration. It only affects new addresses to be registered on interfaces using the global default. The addresses already registered will not be affected. |
- |
"Enter the shutdown and no shutdown commands on desired " "interfaces to restart address registration if need to remove addresses " "already registered but not permitted by the new global " "default access filter." |
|
ATM-5-ILMIINTFREDUNDENCY |
5-Notice |
ILMI[chars]: [chars] |
Informational Message for ILMI Redundency Support |
as |
LOG_STD_SH_TECH_ACTION |
|
ATM-5-ILMIREDUNDENCY |
5-Notice |
[chars] |
Informational Message for ILMI Redundency Support |
as |
LOG_STD_SH_TECH_ACTION |
|
ATM-5-UPDOWN |
5-Notice |
Interface [chars] Changing autovc [dec]/[dec] to [chars] |
The ATM Auto VC is either created removed activated \n\ or deactivated. |
- |
"No action required if status change is intended\n\ otherwise the cause for status change may deserve to be noticed.\n\ The shut and no shut CLI command deactivates/activates VC." |
|
ATM-6-AUTOPPP |
6-Information |
ATM[chars]: VCVCD=[dec] VPI=[dec] VCI=[dec] Auto Detected Encap Type is [chars]. |
ATM VC AutoPPP Encapsulation Type has been changed automatically`. |
atmcommon |
"don't do anything." |
|
ATM-6-ILMIAUTOCFGALREADY |
6-Information |
ILMI[chars]: Auto-configuration already enabled. |
Atm auto-configuration has been enabled already. 'atm auto-configuration' command just entered is ignored. |
- |
"No action required." |
|
ATM-6-ILMIAUTOCFGENABLEERR |
6-Information |
ILMI[chars]: Auto-configuration cannot be enabled. |
Auto-configuration cannot be enabled if there are some conflicting configuration on an interface. Like if there are VCs with vpi > 255 auto-configuration cannot be done till these VCs are removed as with auto-configuration enabled vpi > 255 cannot be supported. |
- |
"Undo the conflicting configuration on the interface for " "this command to succeed." |
|
ATM-6-ILMINOAUTOCFG |
6-Information |
ILMI[chars]: Auto-configuration is disabled current |
The command just entered causes auto-configuration to be disabled the most recently entered interface parameters will be used at next interface restart. |
- |
"Be aware of what parameteres have been configured." |
|
ATM-6-ILMINOAUTOCFGALREADY |
6-Information |
ILMI[chars]: Auto configuration already disabled. |
Atm auto-configuration has been enabled already. 'no atm auto-configuration' command just entered is ignored. |
- |
"No action required." |
|
ATM-6-ILMITERMINATINGPORT |
6-Information |
ILMI[chars]: This command does not apply to internal terminating port. |
Internal terminating does not need to be configured with this command. The command just entered is ignored. |
- |
"No action required." |
|
ATM-6-PVC_STATE_CHANGE |
6-Information |
ATM[chars]: PVCVCD=[dec] VPI=[dec] VCI=[dec] state changed to [chars]. |
ATM PVC status has changed. |
- |
LOG_NO_ACTION |
|
ATMCORE_RED-2-INTERNAL_CRITICAL |
2-Critical |
[chars] |
The ATM core redundancy subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMCORE_RED-3-INTERNAL_ERROR |
3-Error |
[chars] |
The ATM core redundancy subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMCORE_RED-4-INTERNAL_WARNING |
4-Warning |
[chars] |
The ATM core redundancy subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMCORE-2-INTERNAL_CRITICAL |
2-Critical |
[chars] |
The ATM core subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMCORE-3-INTERNAL_ERROR |
3-Error |
[chars] |
The ATM core subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMCORE-4-ATM_SYS_ERROR |
4-Warning |
[chars] |
The ATM core subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMCORE-4-CONFIG_ERROR |
4-Warning |
Configuration Error: [chars] |
This message indicates a configuration error. The message will display more specific information about the problem location. |
- |
"Change the configuration to correct the error." |
|
ATMCORE-4-INTERNAL_WARNING |
4-Warning |
[chars] |
This warning is generated by the ATM core subsystem to the user. This could arise because the user request may not be granted due to some existing configuration on the device. This message serves as an alert to the user. This message contains text which can be used to help identify the nature of the problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMSIG-3-ATMSIG_CUG_DELETE_FAILED |
3-Error |
ATMSIG[chars] |
A software error occurred during removal of a member from a\n\ closed user group. Other error messages appearing\n\ immediately prior to this one may be related. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMSIG-3-ATMSIG_CUG_INSERT_FAILED |
3-Error |
ATMSIG[chars] |
A software error occurred during addition of a member to a\n\ closed user group. Other error messages appearing\n\ immediately prior to this one may be related. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMSIG-3-ATMSIG_LISTEN_FAILED_DUP |
3-Error |
Duplicate LISTEN by [chars] for existing NSAP [chars] owned by [chars] |
An application attempted to either LISTEN on an NSAP owned by \n\ another application or to LISTEN for the same NSAP twice |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMSIG-3-ATMSIG_PRTY_DELETE_FAILED |
3-Error |
ATMSIG[chars] [dec][dec] - %04d/%02d avl prty del failed:svc 0x[hec] party 0x[hec] |
A software error occurred during removal of a party from a\n\ point-to-multipoint call. Other error messages appearing \n\ immediately prior to this one may be related. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMSIG-3-ATMSIG_PRTY_INSERT_FAILED |
3-Error |
ATMSIG[chars] [dec][dec] - %04d/%02d avl prty ins failed:svc 0x[hec] party 0x[hec] |
A software error occurred during addition of a party to a\n\ point-to-multipoint call. Other error messages appearing\n\ immediately prior to this one may be related. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMSIG-3-ATMSIG_SVC_DELETE_FAILED |
3-Error |
ATMSIG[chars] [dec][dec] - %04d/%02d SVC wavl del failed:svc 0x[hec] |
A software error occurred during closure of an SVC. Other error\n\ messages appearing immediately prior to this one may be related. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMSIG-3-ATMSIG_SVC_INSERT_FAILED |
3-Error |
ATMSIG[chars] [dec][dec] - %04d/%02d SVC wavl ins failed:svc 0x[hec] |
A software error occurred during creation of an SVC. Other error\n\ messages appearing immediately prior to this one may be related. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMSIG-3-DBINITFAIL |
3-Error |
Signalling control block initialization failure [chars] |
An internal software or resource error occurred |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMSIG-3-ENQFAIL |
3-Error |
process_enqueue failed [chars] |
An internal software error occurred while handling a user request. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMSIG-3-FAIL1STHALFLEG |
3-Error |
1st halfLeg failed [chars] |
An internal software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMSIG-3-FAIL2NDHALFLEG |
3-Error |
2nd halfLeg failed [chars] |
An internal software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMSIG-3-FAILASSERT |
3-Error |
Assertion failed: [chars] |
An internal software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMSIG-3-FAILHALFLEGREM |
3-Error |
halfLeg removal failed [chars] |
An internal software error occurred. This message should only\n\ be displayed when verbose debugging is enabled for an SVC. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMSIG-3-FAILXCONN |
3-Error |
Xconnect failed [chars] |
An internal software error occurred during installation of an\n\ SVC cross-connect. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMSIG-3-INVPNNIMSG |
3-Error |
Invalid msg from routing/pnni : [chars] |
This message indicates an error in the PNNI routing subsystem.\n\ It could be caused by an internal software error or by bad\n\ control information received from peer equipment. The message\n\ will contain additional information that can help locate the\n\ cause. Any message with 'NULL' probably indicates a problem\n\ with this system others probably point at the peer equipment. |
- |
"Check this system and the peer equipment for any obvious errors. " LOG_STD_RECUR_ACTION |
|
ATMSIG-3-NOCALLREF |
3-Error |
Cannot find a Callref value to allocate: [chars] |
This indicates an internal software error probably including\n\ memory exhaustion. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMSIG-3-NOSVC |
3-Error |
no SVC [chars] |
An internal software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMSIG-3-PNNI_TRACE_INTERNAL |
3-Error |
[chars] |
An internal software error or unexpected condition occured during\n\ PNNI Connection/Path Trace related processing |
- |
- |
|
ATMSIG-4-CONFIG_ERROR |
4-Warning |
Configuration Error: [chars] [chars] |
This message indicates a configuration error in the ATM Signaling\n\ subsystem. The message will display more specific information\n\ about the problem location. |
- |
"Change the configuration to correct the error." |
|
ATMSPA-2-INITFAIL |
2-Critical |
[chars] - Init Failed return code: [dec] |
The SPA failed to complete hardware initialization. One of the devices in the SPA failed to initialize successfully. Information about the failed device is specified in the message text on the console or in the system log. |
- |
"Please power down and reseat the indicated SPA card. If the condition " "persists copy the error message exactly as it appears. Next research " "and attempt to resolve the issue using the SPA hardware troubleshooting " "documentation as well as the tools and utilities provided at " "http://www.cisco.com/public/support/tac/tools.shtml. If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a 'show tech-support' to " "your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
ATMSPA-3-ATM_SPA_AUTOVC_FAIL |
3-Error |
[chars]: atm autovc discovery configuration failed reason: [chars] |
A command to configure the atm autovc discovery on an atm interface has failed |
spa-atm-all |
LOG_STD_ACTION |
|
ATMSPA-3-DATA_ERROR |
3-Error |
[chars] Error 0x[hec] [chars] |
A datapath protocol violation or sequence error has been detected. |
- |
"The message text on the console or in the " "system log provides more information " "on the specific nature of the error. " LOG_STD_SH_TECH_ACTION |
|
ATMSPA-3-FATAL_ERROR |
3-Error |
occurred on [chars]. Resetting SPA |
The SPA has been reset due to a critical error in one of its devices. The error could either be a single occurrence of an event or multiple occurrences within a period of time. The message text on the console or in the system log provides more information on the specific nature of the error. |
spa-atm-all |
"If the SPA is reset more than once copy the error " "message exactly as it appears. Next research and attempt to resolve the " "issue using the SPA hardware troubleshooting documentation as well " "as the tools and utilities provided at " "http://www.cisco.com/public/support/tac/tools.shtml. If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a 'show tech-support' to " "your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
ATMSPA-3-FPD_VER_DEPENDENCY_NOTE |
3-Error |
Cannot perform the requested FPD update operation because [chars] in subslot [dec]/[dec] has incompatible HW version [dec].[dec] with FPD image version [dec].[dec] for FPD ID [dec]. Only image version greater than [dec].[dec] can be used in the update operation of [chars] with HW version greater than [dec].[dec]. |
The version of the FPD image from the FPD image bundle or package is not compatible with the HW version of the target card |
spa-atm-all |
LOG_STD_ACTION |
|
ATMSPA-3-GEN_ERROR |
3-Error |
[chars] Error 0x[hec] [chars] |
The specified error has been detected. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMSPA-3-HW_ERROR |
3-Error |
[chars] Error 0x[hec] [chars] |
The specified hardware error has been detected. |
- |
"The message text on the console or in the " "system log provides more information " "on the specific nature of the error. " LOG_STD_SH_TECH_ACTION |
|
ATMSPA-3-KEEPALIVE_FAILURE |
3-Error |
occurred on [chars]. Resetting SPA |
One of the devices of the SPA failed to respond to keepalives due to which SPA has been reset. The message text on the console or in the system log provides more information on which device failed to respond. |
spa-atm-all |
"If the SPA is reset more than once copy the error " "message exactly as it appears. Next research and attempt to resolve the " "issue using the SPA hardware troubleshooting documentation as well " "as the tools and utilities provided at " BUG_TOOLKIT "If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " TAC_CASE_OPEN " or contact your Cisco technical " "support representative. Be sure to provide the information you have " "gathered and <cmdBold>show tech-support<nocmdBold> to your support " "representative or attach it to your case" |
|
ATMSPA-3-QOS_ALLOC_FAILED |
3-Error |
[chars] [chars] [chars]: [dec] |
Traffic shaping parameters could not be configured because the number of unique shaping parameters that are configured on the PVCs or PVPs in this specified ATM SPA is over the maximum limit. The maximum number of unique shaping parameters that can be configured on the PVCs or PVPs is 4096. |
spa-atm-all |
"Ensure that the total number of unique shaping parameters " "that are configured on both PVCs and PVPs does not exceed " "the maximum limit of 4096." |
|
ATMSPA-3-SW_ERROR |
3-Error |
[chars] Error 0x[hec] [chars] |
The specified software error has been detected. |
- |
LOG_STD_SH_TECH_ACTION |
|
ATMSPA-3-VCQ_ERROR |
3-Error |
[chars]: VC queue configuration failed due to un-initialized queue table global identifier [dec] |
Software configuration of a VC queue failed due to un-initialized queue table. |
- |
"Attempt to perform a soft OIR operation by entering the command " "that is described in the shared port adapter software configuration " "guide. If the condition persists copy the error message exactly as it " "appears and report it to your technical support representative. " "Also supply a 'show tech-support' at that time." |
|
ATMSPA-4-SETUPVC |
4-Warning |
Interface [chars] VC [dec] setup failed reason = [dec] |
A command to setup a VC has failed on RP. |
spa-atm-all |
"The SPA ATM driver has detected a problem creating the internal OAM" "VC. Reload the indicated SPA card to reconfigure the internal OAM VC." "If the error messages persists copy the error message exactly as " "it appears. Next research and attempt to resolve the issue using " "the SPA hardware troubleshooting documentation as well as the tools " "and utilities provided at " "http://www.cisco.com/public/support/tac/tools.shtml. If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a 'show tech-support' to " "your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
ATMSPA-4-TEARDOWNVC |
4-Warning |
Interface [chars] VC [dec] teardown failed reason = [dec] |
A command to remove a VC config has failed on RP. |
spa-atm-all |
"The SPA ATM driver has detected a problem tearing down the internal" "OAM VC. Reload the indicated SPA card to do a clean tear down of the " "internal OAM VC. If the error messages persists copy the error " "message exactly as it appears. Next research and attempt to resolve " "the issue using the SPA hardware troubleshooting documentation as well" " as the tools and utilities provided at " "http://www.cisco.com/public/support/tac/tools.shtml. If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a 'show tech-support' to " "your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
ATMSPA-4-VCSETUP |
4-Warning |
[chars]: VC setup command received on the LC for an existing VC VCD [dec] |
A command to set up a VC has been received for a VC that has already been set up. The VC has already been configured by a previous setup VC command from the RP. A duplicate setup command may indicate that the RP did not receive a response from the LC for the previous setup command. |
- |
LOG_STD_NO_ACTION |
|
ATMSPA-4-VCTEARDOWN |
4-Warning |
[chars]: VC tear down command received on the LC for a non-existing VC VCD [dec] |
The VC does not exist on the LC. Most likely it has been torn down by a previous teardown command from RP. A duplicate teardown command may indicate that the RP did not receive a response from the LC for the previous teardown command. |
- |
LOG_STD_NO_ACTION |
|
ATMSPA-4-VPSETUP |
4-Warning |
[chars]: VP setup command received on the LC for an existing VP VPI [dec] |
A command to set up a VP has been received for a VP that has already been set up. The VP has already been configured by a previous setup VP command from the RP. A duplicate setup command may indicate that the RP did not receive a response from the LC for the previous setup command. |
- |
LOG_STD_NO_ACTION |
|
ATMSPA-4-VPTEARDOWN |
4-Warning |
[chars]: VP tear down command received on the LC for a non-existing VP VPI [dec] |
The VP does not exist on the LC. Most likely it has been torn down by a previous teardown command from RP. A duplicate teardown command may indicate that the RP did not receive a response from the LC for the previous teardown command. |
- |
LOG_STD_NO_ACTION |
|
ATMSSCOP-3-SSCOPERR |
3-Error |
INIT SSCOP -\nIntf : [chars] Event : [chars] State : [chars]. |
A software error occurred in the ATM SSCOP subsystem. |
- |
LOG_STD_SH_CMD_ACTION |
|
ATMSSCOP-4-UNMATCHUNIVERSION |
4-Warning |
[chars]: [chars]. Please verify peer UNI version |
The ATM peer equipment appears to be running an old version of\n\ ATM UNI. Communication with it is not possible. |
- |
"The ATM peer equipment may need attention. \Please verify its UNI version is at least 3.1 and upgrade if necessary." |
|
ATMSSCOP-5-SSCOPINIT |
5-Notice |
- Intf : [chars] Event : [chars] State : [chars]. |
This message indicates a routine step of the ATM SSCOP\n\ initialization sequence. |
- |
LOG_STD_NO_ACTION |
|
ATOM_HA-3-RECOVERY |
3-Error |
[chars] |
AToM Manager High Availability recovery failed. |
xconnect |
LOG_STD_ACTION |
|
ATOM_HA-3-UPDATE |
3-Error |
[chars] |
AToM Manager High Availability update failed. |
xconnect |
LOG_STD_ACTION |
|
ATOM_NP_CLIENT-3-INFO |
3-Error |
[chars] |
ATOM NP Client failed to initialize properly which will result in\n\ improper operation of Any Transport Over MPLS feature |
vsp-mid |
"Try to reload the IOS image on the affected card or platform. If the\n\ error persists record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
ATOM_NP_CLIENT-3-NOMEM |
3-Error |
[chars] |
ATOM NP Client failed to initialize properly which will result in\n\ improper operation of Any Transport Over MPLS feature |
vsp-mid |
"This error may indicate that more memory must be installed on the\n\ affected card or platform in order to service all the features and\n\ related entities enabled via the configuration.\n\\n\ Try to reload the IOS image on the affected card or platform. If the\n\ error persists record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
ATOM_NP_CLIENT-4-WARN |
4-Warning |
[chars] [dec] [chars] |
AToM Entry could not be added because:\n\ 1. Entry passed is invalid. |
vsp-mid |
"Try to reload the IOS image on the affected card or platform. If the\n\ error persists record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
ATOM_SEG-3-CHUNKFREE |
3-Error |
Error freeing [chars] |
ATOM Segment Handler error |
mpls-mfi |
LOG_STD_ACTION |
|
ATOM_SEG-3-ILLEGALUPD |
3-Error |
Illegal label [dec] update [chars] |
AToM Segment Handler error |
mpls-mfi |
LOG_STD_ACTION |
|
ATOM_SEG-3-NOTSUPP |
3-Error |
Unsupported update [chars] |
AToM Segment Handler error |
mpls-mfi |
LOG_STD_ACTION |
|
ATOM_SEG-3-UNSUPPORTEDADDR |
3-Error |
Unsupported address type [dec] |
AToM Segment Handler error |
mpls-mfi |
LOG_STD_ACTION |
|
ATOM_TRANS-3-CONSISTENCY |
3-Error |
[chars] |
An action attempted by the layer 2 transport over MPLS implementation encountered an unexpected condition |
xconnect |
LOG_STD_ACTION |
|
ATOM_TRANS-3-INIT_FAIL |
3-Error |
Failed to start AToM Manager |
Failed to start and initialize AToM Manager. |
xconnect |
LOG_STD_ACTION |
|
ATOM_TRANS-3-LABEL_ALLOC_FAIL |
3-Error |
Failed to allocate local label for peer:[inet] vcid:[dec] |
Failed to allocate local label for specified AToM VC. |
xconnect |
LOG_STD_ACTION |
|
ATOM_TRANS-3-XDM_CREATE |
3-Error |
Failed to create XDM - rc [dec] |
ATOM Manager was unable to create a Dispatch Manager instance for event handling. |
xconnect |
LOG_STD_ACTION |
|
ATOM_TRANS-4-CONFIG |
4-Warning |
[chars] |
AToM pseudowire uses undesirable configuration. |
xconnect |
LOG_STD_ACTION |
|
ATOM_TRANS-4-PW_MAX_REACHED |
4-Warning |
[chars] |
Pseudowire maximum limit reached for the L2 subscriber author group |
xconnect |
LOG_STD_ACTION |
|
ATOM_TRANS-5-DISPOSITION_DISABLED |
5-Notice |
[chars] |
Disposition disabled for specified AToM VC. |
xconnect |
LOG_STD_NO_ACTION |
|
ATOM_TRANS-5-DISPOSITION_ENABLED |
5-Notice |
[chars] |
Disposition enabled for specified AToM VC. |
xconnect |
LOG_STD_NO_ACTION |
|
ATOM_TRANS-5-IMPOSITION_DISABLED |
5-Notice |
[chars] |
Imposition disabled specified AToM VC. |
xconnect |
LOG_STD_NO_ACTION |
|
ATOM_TRANS-5-IMPOSITION_ENABLED |
5-Notice |
[chars] |
Imposition enabled for specified AToM VC. |
xconnect |
LOG_STD_NO_ACTION |
|
ATOM_TRANS-5-PW_WATERMARK_LIMIT |
5-Notice |
[chars] |
Pseudowire max watermark limit reached for the L2 subscriber author group |
xconnect |
LOG_STD_ACTION |
|
ATOM_TRANS-6-ATOM_NO_ROUTER_ID |
6-Information |
[chars] |
No router ID is available for AToM to use and this will impact pseudowire VCCV. Please enable \l2 router-id <address>\ or enable an LDP router ID if you wish VCCV to be operational. |
xconnect |
LOG_STD_ACTION |
|
ATTN-2-MBOX_REG_FAIL |
2-Critical |
return code [dec] |
Registration of handler function for mailbox event failed mailbox event failed. |
cpp-ucode |
LOG_STD_ACTION |
|
ATTN-2-PROXY_INIT_FAIL_IPC_REG |
2-Critical |
return code [dec] |
Initialization of attention proxy failed due to error registering IPC handler function. |
cpp-ucode |
LOG_STD_ACTION |
|
ATTN-3-PROXY_IPC_ALLOC_FAILED |
3-Error |
[chars] |
Allocation of an IPC packet buffer by the attention proxy failed. |
cpp-ucode |
LOG_STD_ACTION |
|
ATTN-3-PROXY_IPC_SEND_FAILED |
3-Error |
[chars] |
Transmission of an IPC message by the attention proxy failed. |
cpp-ucode |
LOG_STD_ACTION |
|
ATTN-3-PROXY_UNHANDLED_MSG |
3-Error |
subtype [dec] |
Attention proxy received a message with an unknown subtype. |
cpp-ucode |
LOG_STD_ACTION |
|
ATTN-3-SYNC_TIMEOUT |
3-Error |
msecs since last timeout %llu missing packets [dec] |
Attention sync command timed out. |
cpp-ucode |
LOG_STD_ACTION |
|
AUDIT-1-FILE_ROLLOVER |
1-Alert |
Audit File Roll-over: [dec] |
Audit Circular File Rolled Over. |
- |
"Increase Audit filesize." |
|
AUDIT-3-FILE_RESIZE_ERR |
3-Error |
Cannot resize Audit file. |
File system error while resizing the audit file. |
- |
"Check DISK filesystems on the router." |
|
AUDIT-3-FILE_WRITE_ERR |
3-Error |
Cannot write to Audit file. |
File system error while writing to the audit file. |
- |
"Check DISK filesystems on the router." |
|
AUDIT-3-NOFILE |
3-Error |
Cannot create Audit file. |
File system error while creating the audit file. |
- |
"Check DISK filesystems on the router." |
|
AUDIT-3-NOPROC |
3-Error |
Cannot create Audit process. |
Insufficient internal resource available to create process. |
- |
"Check available memory on router." |
|
AUDIT-5-AUDIT_DISABLED |
5-Notice |
Auditing disabled |
Audit was disabled on the router. |
- |
"Check if Audit was disabled by someone authorized to do so" |
|
AUDIT-5-AUDIT_ENABLED |
5-Notice |
Auditing enabled |
Audit was enabled on the router. |
- |
"Audit logs can be verified if changes are valid" |
|
AUDIT-5-FILESYSTEM |
5-Notice |
Filesystem changed. Hash: [chars] |
FLASH/DISK Filesystems on the router changed. |
- |
"Check if it is a valid change." |
|
AUDIT-5-HARDWARE_CONFIG |
5-Notice |
Hardware changed. Hash: [chars] |
Hardware on the router changed. |
- |
"Check if it is a valid change." |
|
AUDIT-5-RUN_CONFIG |
5-Notice |
Running Configuration changed. Hash: [chars] |
Running Config on the router changed. |
- |
"Check if it is a valid change in config." |
|
AUDIT-5-RUN_VERSION |
5-Notice |
Running Version changed. Hash: [chars] |
Running Version on the router changed. |
- |
"Check if it is a valid change." |
|
AUDIT-5-STARTUP_CONFIG |
5-Notice |
Startup Configuration changed. Hash: [chars] |
Startup config on the router changed. |
- |
"Check if it is a valid change." |
|
AUTHMGR-0-CONFIG_CORRUPT |
0-Emergency |
Checksummed interface configuration corruption detected. |
Interface configuration field was modified unexpectedly. |
dot1x-ios |
LOG_STD_NO_ACTION |
|
AUTHMGR-4-ILLEGAL_TRACE_REQ |
4-Warning |
Component ID [dec] not registered. |
Attempt to log a message with unregistered ID. |
dot1x-ios |
LOG_STD_NO_ACTION |
|
AUTHMGR-4-UNAUTH_MOVE |
4-Warning |
[chars] MAC address [enet] from [chars] to [chars] |
Move while not authenticated on old IDB |
dot1x-ios |
LOG_STD_NO_ACTION |
|
AUTHMGR-5-FAIL |
5-Notice |
Authorization failed or unapplied for client [enet] on Interface [chars] |
Authorization was unsuccessful. |
dot1x-ios |
LOG_STD_NO_ACTION |
|
AUTHMGR-5-MACMOVE |
5-Notice |
MAC address [enet] moved from Interface [chars] to Interface [chars] |
Client has moved to a new interface without logging off on the previous one. |
dot1x-ios |
LOG_STD_NO_ACTION |
|
AUTHMGR-5-MACREPLACE |
5-Notice |
MAC address [enet] on Interface [chars] is replaced by MAC [enet] |
A new client has triggered a violation causing an existing client to be replaced |
dot1x-ios |
LOG_STD_NO_ACTION |
|
AUTHMGR-5-SECURITY_VIOLATION |
5-Notice |
Security violation on the interface [chars] new MAC address [enet] is seen. |
A host on the specified interface is attempting to gain access into the network or is trying to authenticate in a host mode that does not support the number of hosts attached. This is treated as a security violation and the port has been error-disabled. |
dot1x-ios |
"Ensure that the port is configured to support the " "number of hosts attached. Enter the " "<cmdbold>shutdown<nocmdbold> command followed by " "<cmdbold>no shutdown<nocmdbold> command to restart " "the port." |
|
AUTHMGR-5-START |
5-Notice |
Starting '[chars]' for client [enet] on Interface [chars] AuditSessionID [chars] |
Starting an authentication method |
dot1x-ios |
LOG_STD_NO_ACTION |
|
AUTHMGR-5-SUCCESS |
5-Notice |
Authorization succeeded for client [enet] on Interface [chars] |
Authorization was successful. |
dot1x-ios |
LOG_STD_NO_ACTION |
|
AUTHMGR-5-VLANASSIGN |
5-Notice |
VLAN [dec] assigned to Interface [chars] AuditSessionID [chars] |
VLAN assignment |
dot1x-ios |
LOG_STD_NO_ACTION |
|
AUTHMGR-7-FAILOVER |
7-Debug |
Failing over from '[chars]' for client [chars] on Interface [chars] |
Failing over from the current authentication method |
dot1x-ios |
LOG_STD_NO_ACTION |
|
AUTHMGR-7-NOMOREMETHODS |
7-Debug |
Exhausted all authentication methods for client [chars] on Interface [chars] |
All available authentication methods have been tried |
dot1x-ios |
LOG_STD_NO_ACTION |
|
AUTHMGR-7-STOPPING |
7-Debug |
Stopping '[chars]' for client [enet] on Interface [chars] AuditSessionID [chars] |
Stopping the current authentication method |
dot1x-ios |
LOG_STD_NO_ACTION |
|
AUTO_IP_RING-5-AUTOIP_ADDRESS_POOL_EXHAUST |
5-Notice |
Free IP addresses are not available in the Auto-IP Server pool. Configure additional pools to get IP addresses for the requesting |
The Auto-IP server is configured with pools of Auto-IP addresses. The IP addresses are assigned to the requesting ring ports. The Auto-IP address pool is exhaused and there are no more free addresses. |
auto_ip_ring |
"Configure additional address pools in the" " Auto-IP server by using the configuration command" " 'auto-ip-ring server' and the sub command" " 'ipv4-address-pool <auto-ip-base-address> <num of nodes in ring>" |
|
AUTO_IP_RING-5-AUTOIP_HOST_ADD_SUCCESS |
5-Notice |
IP address[inet]/31 is assigned to the ring port[chars] and |
IP address is assigned to the ring port and the device is added to the ring successfully |
auto_ip_ring |
"Use the 'show auto-ip-ring' or 'show run' command" " on the device to view the configured IP address on the ring port." |
|
AUTO_IP_RING-5-AUTOIP_HOST_INSERT_SUCCESS |
5-Notice |
IP addresses[inet]/31 [inet]/31 are assigned to the ring ports[chars] [chars] |
IP addresses are assigned to the ring ports and the device is inserted into the ring successfully |
auto_ip_ring |
"Use the 'show auto-ip-ring' or 'show run' command" " on the device to view the configured IP addresses on the ring ports." |
|
AUTO_IP_RING-5-AUTOIP_IP_ADDR_SUCCESS_PORT |
5-Notice |
IP address[inet] is assigned to the ring port[chars] successfully |
IP address is assigned to the ring port successfully. |
auto_ip_ring |
"Use the 'sh ip interface' or 'show run' command" " to view the IP address of the ring port." |
|
AUTO_IP_RING-5-DUPL_AUTOIP_ADDRESS |
5-Notice |
Neighbor device advertised the same configured Auto-IP address[inet] |
Auto-IP Ring feature requires each device to configure a unique auto-ip address different from those on other devices. The local device is configured with an Auto-IP address. However the local device has also received the same Auto-IP address from a neighbor device. This may indicate that two devices are configured with the same Auto-IP address. |
auto_ip_ring |
"Use the 'show auto-ip-ring' or 'show run' command" " on both devices to view the configured Auto-IP address. If two edge" " devices show the same configured Auto-IP address then the duplicate" " configured Auto-IP address needs to be removed." |
|
AUTO_IP_RING-5-EQUAL_AUTOIP_PRIORITY |
5-Notice |
Port[chars]: Received the same priority[dec] as the peer device |
Auto-IP Ring feature requires two neighbor devices to exchange different Auto-IP priority for IP auto-negotiation to happen. If they advertise the same Auto-IP priority then the IP auto-negotiation will not happen. This may indicate that the ring ports of the two devices are either wrongly wired or there is a missing seed configuration. |
auto_ip_ring |
"Use the 'show auto-ip-ring' or 'show run' command" " on both devices to view the IP addresses of the ring ports and the" " advertised/received Auto-IP priorities. If the Auto-IP priority is both 2" " or both 0 it represents a faulty wire connection that can be fixed by" " switching the two ring ports on one of the devices as necessary." " If the Auto-IP priority is both 1 there are two possibilities based on" " the mode. In pre-config mode manually configure an IP address on one" " device to start the Auto-IP negotiation. In auto-config mode if the" " Auto-IP server is reachable then configure 'auto-ip-ring <ring-d> seed'" " on one ring port of the device." |
|
AUTO_IP_RING-5-LLDP_NOT_ENABLE_ON_THIS_INTERFACE |
5-Notice |
port [chars]: lldp not enabled for interface please enable lldp on |
Auto-ip depends on lldp to communicate with it's peer. So configure lldp before auto-ip configuration |
auto_ip_ring |
"Configure 'lldp run' in global config mode and" " check 'sh lldp neighbors'" |
|
AUTOCFG-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
AUTOQOS_ISSU-2-GET_BUFFER |
2-Critical |
AutoQoS ISSU client failed to get buffer for message. Error: [dec] [chars] |
The AutoQoS 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. |
autoqos |
"show logging and show checkpoint client" |
|
AUTOQOS_ISSU-2-INIT |
2-Critical |
AutoQoS ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The AutoQoS 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. |
autoqos |
LOG_STD_ACTION |
|
AUTOQOS_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
AutoQoS ISSU client failed to send negotiation message. Error: [dec] [chars] |
The AutoQoS 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. |
autoqos |
"show logging and show checkpoint client" |
|
AUTOQOS_ISSU-2-SESSION_NEGO |
2-Critical |
AutoQoS ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The AutoQoS 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. |
autoqos |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
AUTOQOS_ISSU-2-SESSION_REGISTRY |
2-Critical |
AutoQoS ISSU client failed to register session information. Error: [dec] [chars] |
The AutoQoS ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
autoqos |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
AUTOQOS_ISSU-3-INVALID_SESSION |
3-Error |
AutoQoS ISSU client does not have a valid registered session. |
The AutoQoS ISSU client does not have a valid registered session. |
autoqos |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
AUTOQOS_ISSU-3-MSG_NOT_OK |
3-Error |
AutoQoS ISSU client 'Message Type [dec]' is not compatible |
The AutoQoS ISSU client received an incompatible message from the peer device. The message cannot be processed. |
autoqos |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
AUTOQOS_ISSU-3-MSG_SIZE |
3-Error |
AutoQoS ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The AutoQoS ISSU client failed to calculate the MTU for the specified message. The AutoQoS ISSU client is not able to send the message to the standby device. |
autoqos |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
AUTOQOS_ISSU-3-SESSION_UNREGISTRY |
3-Error |
AutoQoS ISSU client failed to unregister session information. Error: [dec] [chars] |
The AutoQoS ISSU client failed to unregister session information. |
autoqos |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
AUTOQOS_ISSU-3-TRANSFORM_FAIL |
3-Error |
AutoQoS ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The AutoQoS 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 AutoQoS state between the active device and the standby device is not identical. |
autoqos |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
AUTORP-2-RADIXINIT |
2-Critical |
Error initializing the Auto-RP radix tree |
An internal software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
AUTORP-4-OVERLAP |
4-Warning |
AutoRP [chars] packet group [inet] with mask [inet] removed because of multicast boundary for [inet] with mask [inet] |
The multicast boundary has a longer network mask than the AutoRP encoded group. |
- |
"Use postive permit clauses in the AutoRP Access " "Control List" |
|
AUTORP-4-PAK_ERR |
4-Warning |
AutoRP [chars] packet is received on interface [chars] with Source address=[inet] Destination address=[inet] TTL=[dec] IP length=[dec] Datagram size/UDP length=[dec] |
The AutoRP packet was received with wrong packet length. The packet has been dropped as it may be a malformed packet. |
- |
LOG_STD_NO_ACTION |
|
AUTORP-4-PRM_DEL |
4-Warning |
Error expiring semi-static RP-mapping entry [inet]/[dec] RP:[inet] |
An internal software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
AUTORP-4-RADIXINSERT |
4-Warning |
Error inserting a new entry into the RP-mapping radix tree |
An internal software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
AUTORP-5-CRP_REMOVED |
5-Notice |
C-RP [inet] on interface [chars] has been removed |
This is performed either because PIM is disabled on the interface or \n the interface card has been removed |
- |
LOG_STD_NO_ACTION |
|
AUTORP-5-MAPPING |
5-Notice |
RP for [inet]/[dec] is now [inet] |
A new RP has been elected for the subject group prefix |
- |
LOG_STD_NO_ACTION |
|
AUTORP-6-RP_MAPPING_IDB_DEL |
6-Information |
AutoRP RP-MAPPING IDB [chars] is deleted |
The configured rp-mapping idb has been deleted. |
- |
LOG_STD_NO_ACTION |
|
AUTOSEC-3-CONFSAVE_FAIL |
3-Error |
Applying AutoSecure config to running-conf failed with error [dec] |
Configuration of the AutoSecure session could not be applied to the running configuration |
security keyword:autosec |
LOG_STD_ACTION |
|
AUTOSEC-5-ENABLED |
5-Notice |
AutoSecure is configured on the device |
Security configuration of the device is done using AutoSecure. |
none |
"Notification message only. No action required." |
|
AUTOTEMPLATE_HWIDB_DELETE-5-MPLS_TE_AUTOMESH |
5-Notice |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
AUTOUPGRADE-3-BADSIGNATURE |
3-Error |
Embedded signature verification failed. |
The downloaded image is corrupted. This could be because of an invalid image name or a communication error. |
os |
"Make sure that the image name spcified refers to" " a valid IOS image and retry \"upgrade automatic\"." " If the problem" " persists please check Bug Toolkit on the" " Cisco web-site for previously filed bugs and" " upgrade code if necessary. If you do not find" " a previously-filed bug collect the outputs of" " \"show logging\" \"show version\" and" " \"show running-config\" and open a TAC case with" " the gathered information." |
|
AUTOUPGRADE-3-DELETEFAIL |
3-Error |
Auto Upgrade Manager failed to delete the previous image [chars] |
Auto Upgrade Manager attempted to delete the previous image to make enough free space for the new image in the filesystem. However an error occurred while deleting the previous image |
os |
"Please check Bug Toolkit on the Cisco web-site" " for previously filed bugs and upgrade code if" " necessary. If you do not find a previously-filed" " bug collect the console output as well as outputs" " of \"show version\"" " \"show logging\" and \"show running-config\" and" " open a TAC case for informaion on the supported" " images" |
|
AUTOUPGRADE-3-DOWNLOADFAIL |
3-Error |
Auto Upgrade Manager is unable to download new image from [chars] |
Possible reasons of this failure include: 1. temporary communication problem 2. server unavailable 3. incorrect username/password 4. the image may not exist in the location 5. there is not enough space in filesystem |
os |
"Please ensure that there is enough free space in " " a filesystem and image path username password" " information are correct. Then retry the download" " using \"upgrade automatic getversion\"." " If the new image still fails to download" " please check Bug Toolkit on the Cisco web-site" " for previously filed bugs and upgrade code if" " necessary. If you do not find a previously-filed" " bug collect the console output as well as outputs" " of \"show version\"" " \"show logging\" and \"show running-config\" and" " open a TAC case for informaion on the supported" " images" |
|
AUTOUPGRADE-3-DOWNLOADHASHFAIL |
3-Error |
Download hash verification fail |
The image downloaded from cisco.com is corrupted. This usually points to a communication error. |
os |
"Retry \"upgrade automatic\". If the problem" " persists please check Bug Toolkit on the" " Cisco web-site for previously filed bugs and" " upgrade code if necessary. If you do not find" " a previously-filed bug collect the outputs of" " \"show logging\" \"show version\" and" " \"show running-config\" and open a TAC case with" " the gathered information." |
|
AUTOUPGRADE-3-HTTPSENDFAIL |
3-Error |
HTTP send failed: [chars] |
A software error has occurred. |
os |
"Please check Bug Toolkit on the Cisco web-site" " for previously filed bugs and upgrade code if" " necessary. If you do not find a previously-filed" " bug collect the console output as well as outputs" " of \"show version\"" " \"show logging\" and \"show running-config\" and" " open a TAC case for informaion on the supported" " images" |
|
AUTOUPGRADE-3-IDAEXCEPTION |
3-Error |
Exception occurred: [chars]. Error retrieving image info from cisco.com. |
Auto upgrade manager could not obtain information about the new image from cisco.com. |
os |
"Please check Bug Toolkit on the Cisco web-site" " for previously filed bugs and upgrade code if" " necessary. If you do not find a previously-filed" " bug collect the console output as well as outputs" " of \"show version\"" " \"show logging\" and \"show running-config\" and" " open a TAC case for informaion on the supported" " images" |
|
AUTOUPGRADE-3-INVALIDCONFIG |
3-Error |
Upgraded image does not recognize [dec] lines of startup configuration |
Either the saved startup configuration has invalid lines or the upgraded image is incompatible with the previous image |
os |
"Change/Delete the invalid lines from startup" " configuration or revert back to the previous" " image" |
|
AUTOUPGRADE-3-NODISKSPACE |
3-Error |
Not enough free space in any filesystem. need [dec] bytes. |
Auto Upgrade Manager won't be able to download the specified image because there is not enough free space in any filesystem. |
os |
"Use Auto Upgrade Manager disk cleanup utility" " to cleanup a filesystem. Use \"disk-management" " confirm\" or \"disk-management auto\" options with" " \"upgrade automatic getversion\" to use the" " disk cleanup utility. Otherwise you may cleanup" " a filesystem manually." |
|
AUTOUPGRADE-3-NODOWNLOADFS |
3-Error |
Auto Upgrade Manager cannot download new image in the filesystem where current image is running |
Not enough free space in any filesystem for the new image |
os |
"Use Auto Upgrade Manager disk cleanup utility" " to cleanup a filesystem. Use \"disk-management" " confirm\" or \"disk-management auto\" options with" " \"upgrade automatic getversion\" to use the" " disk cleanup utility. Otherwise you may cleanup" " a filesystem manually." |
|
AUTOUPGRADE-3-NULLQ |
3-Error |
NULL queue pointer |
A software error has occurred. |
os |
"Please check Bug Toolkit on the Cisco web-site" " for previously filed bugs and upgrade code if" " necessary. If you do not find a previously-filed" " bug collect the console output as well as outputs" " of \"show version\"" " \"show logging\" and \"show running-config\" and" " open a TAC case for informaion on the supported" " images" |
|
AUTOUPGRADE-3-NVSAVEFAIL |
3-Error |
Failed to save in nvram |
Auto upgrade manager encountered a problem while attempting to save information to NVRAM. |
os |
"Please check Bug Toolkit on the Cisco web-site" " for previously filed bugs and upgrade code if" " necessary. If you do not find a previously-filed" " bug collect the outputs of \"show version\"" " \"show logging\" and \"show running-config\" and" " open a TAC case for informaion on the supported" " images" |
|
AUTOUPGRADE-3-RELOADFAILED |
3-Error |
Failed to reload the device with the new image. |
Auto upgrade manager could not reload the device with the new image. A common reason is insufficient RAM space. |
os |
"Please check Bug Toolkit on the Cisco web-site" " for previously filed bugs and upgrade code if" " necessary. If you do not find a previously-filed" " bug collect the console output as well as outputs" " of \"show version\"" " \"show logging\" and \"show running-config\" and" " open a TAC case for informaion on the supported" " images" |
|
AUTOUPGRADE-3-SQUEEZEFAIL |
3-Error |
Auto Upgrade Manager failed to squeeze the filesystem [chars] |
A software error has occurred |
os |
"Please check Bug Toolkit on the Cisco web-site" " for previously filed bugs and upgrade code if" " necessary. If you do not find a previously-filed" " bug collect the console output as well as outputs" " of \"show version\"" " \"show logging\" and \"show running-config\" and" " open a TAC case for informaion on the supported" " images" |
|
AUTOUPGRADE-3-STARTUPPROCFAIL |
3-Error |
Failed to create the auto upgrade startup process. |
A software error has occurred. |
os |
"Please check Bug Toolkit on the Cisco web-site" " for previously filed bugs and upgrade code if" " necessary. If you do not find a previously-filed" " bug collect the console output as well as outputs" " of \"show version\"" " \"show logging\" and \"show running-config\" and" " open a TAC case for informaion on the supported" " images" |
|
AUTOUPGRADE-6-COMPLETE |
6-Information |
Auto Upgrade of the device completed. From: [chars] To: [chars]. |
The device has been upgraded with a new IOS image by IOS Auto Upgrade Manager |
os |
"This is an informational message only." " These messages may be disabled by changing the" " logging level." |
|
AUTOUPGRADE-6-DELETEDPREVIOUS |
6-Information |
Auto Upgrade Manager deleted the previous image [chars] |
The previous image has been deleted so that there is enough free space to download the new image. |
os |
"This is an informational message only." " These messages may be disabled by changing the" " logging level." |
|
AUTOUPGRADE-6-RELOADED |
6-Information |
Successfully reloaded the new image: \[chars]\. |
The device has succesfully been reloaded with the image downloaded previously by IOS Auto Upgrade Manager. |
os |
"This is an informational message only." " These messages may be disabled by changing the" " logging level." |
|
BACKUP_INTERFACE-5-PREEMPT |
5-Notice |
Preempting interface [chars] in backup pair [chars] [chars] preemption mode is [chars] |
Preempting the current forwarding interface in the backup interface pair. |
backup_int |
LOG_STD_NO_ACTION |
|
BACKUP_INTERFACE-5-VLB_NON_TRUNK |
5-Notice |
Warning: Flexlink VLB is not allowed on non-trunk ports. Please configure [chars] to be a trunk port. |
Flexlink VLB detects a non-trunk port. |
backup_int |
LOG_STD_NO_ACTION |
|
BACKWALK-2-TOO_MANY_DEPENDENTS |
2-Critical |
UEA OCE backwalk aborted - too many dependents |
Too many dependent objects > 200k were encountered during backwalk from an OCE chain object |
rsp3-layer3 |
"Please reduce the number of IGP routes below " "200k." |
|
BACKWALK-2-TOO_MANY_DEPENDENTS |
2-Critical |
UEA OCE backwalk aborted - too many dependents |
Too many dependent objects > 200k were encountered during backwalk from an OCE chain object |
rsp3-layer3 |
"Please reduce the number of IGP routes below " "200k." |
|
BAP-4-NOSTATE |
4-Warning |
[chars] [chars] [chars] in illegal state [dec] |
An internal software error occurred. |
- |
"Call your technical support representative and report the error\n\ message the system version and the router configuration. Use the\n\ <bold> show version <nobold> command to obtain the software version." |
|
BAP-4-WAVL |
4-Warning |
Failed to initialize AVL tree BAP not started |
BAP will not be operational and will not be negotiated. |
- |
"Call your technical support representative and report the error\n\ message the system version and the router configuration. Use the\n\ <bold> show version <nobold> command to obtain the software version." |
|
BATCH_ERR-3-MPLS_TE_EXT_FWDG |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
BCM_BFD-3-BCM_BFD_CREATE_FAIL |
3-Error |
BFD endpoint create failed for ld [dec] on asic [dec] |
BCM BFD endpoint create failed |
rsp3-bfd |
"Please collect nile mgr and uea mgr pman logs" "from shell" |
|
BCM_BFD-3-BCM_BFD_CREATE_FAIL |
3-Error |
BFD endpoint create failed for ld [dec] on asic [dec] |
BCM BFD endpoint create failed |
rsp3-bfd |
"Please collect nile mgr and uea mgr pman logs" "from shell" |
|
BCM_BFD-3-BCM_BFD_DELETE_FAIL |
3-Error |
BFD endpoint create failed for ld [dec] on asic [dec] |
BCM BFD endpoint delete failed |
rsp3-bfd |
"Please collect nile mgr and uea mgr pman logs" "from shell" |
|
BCM_BFD-3-BCM_BFD_DELETE_FAIL |
3-Error |
BFD endpoint create failed for ld [dec] on asic [dec] |
BCM BFD endpoint delete failed |
rsp3-bfd |
"Please collect nile mgr and uea mgr pman logs" "from shell" |
|
BCM_INIT-3-BCM_KBP_INIT_APPL_FAIL |
3-Error |
KBP Application INIT Failure on asic [dec] |
KBP appl initialation failed during the BCM init |
rsp3-infra |
"Please collect nile mgr and uea mgr pman logs" "from shell" |
|
BCM_INIT-3-BCM_KBP_INIT_APPL_FAIL |
3-Error |
KBP Application INIT Failure on asic [dec] |
KBP appl initialation failed during the BCM init |
dominica-infra |
"Please collect uea mgr pman logs from shell" |
|
BCM_INIT-3-BCM_KBP_INIT_ILKN_FAIL |
3-Error |
KBP ILKN INIT Failure on asic [dec] |
KBP ilkn initialation failed during the BCM init |
rsp3-infra |
"Please collect nile mgr and uea mgr pman logs" "from shell" |
|
BCM_INIT-3-BCM_KBP_INIT_ILKN_FAIL |
3-Error |
KBP ILKN INIT Failure on asic [dec] |
KBP ilkn initialation failed during the BCM init |
dominica-infra |
"Please collect uea mgr pman logs from shell" |
|
BCM_TRAPS-2-BCM_SNOOP_CREATE_FAIL |
2-Critical |
Snoop command create failed for cpuq [dec] |
BCM Snoop command create failed |
rsp3-traps |
"Please collect nile mgr and uea mgr pman logs" "from shell" |
|
BCM_TRAPS-2-BCM_SNOOP_CREATE_FAIL |
2-Critical |
Snoop command create failed for cpuq [dec] |
BCM Snoop command create failed |
rsp3-traps |
"Please collect nile mgr and uea mgr pman logs" "from shell" |
|
BCM3142-3-LATE_MAP_FLUSH_INT |
3-Error |
Mg[dec] Rcvr [dec] lch [dec]: LATE_MAP_FLUSH interrupt received from BCM3142 reg_mask_lo [hec] reg_mask_hi [hec] reg_count [dec] resend_mask_lo [hec] resend_mask_hi [hec] resend_count [dec] |
A receiver LATE_MAP_FLUSH interrupt was received from the BCM3142. |
cmts-infra |
"Shut and not shut the upstream" |
|
BCM3220-1-INITFAIL |
1-Alert |
msgtxt_initfail |
The hardware failed to initialize correctly. |
- |
"Repair or replace the controller." |
|
BCM3220-3-BADUNIT |
3-Error |
msgtxt_badunit |
An internal software error occurred. |
- |
"If either message recurs call your technical support representative\n\ for assistance." |
|
BCM3220-3-OWNERR |
3-Error |
msgtxt_ownerror |
An Ethernet interface is malfunctioning or an internal software error\n\ occurred. |
- |
"Repair or replace the controller." |
|
BCM3220-3-TXERR |
3-Error |
CM trasmission error occurred. |
- |
- |
"" |
|
BCM-4-COR_ECC_HIGH |
4-Warning |
High correctable ECC error rate detected\n L2 cache data errors = [dec]\n L2 cache tag errors = [dec]\n Memory data errors = [dec]\n |
A high rate of soft-parity errors from the memory has been detected. Normal system operation may be affected. |
- |
"If there is a regular or sustained occurrence " "of this message reseat the memory or replace " "the memory with memory that is known to " "be operational. "LOG_STD_RECUR_ACTION |
|
BCM-4-ECC_L2CACHE |
4-Warning |
Corrected ECC from L2 cache |
A soft-parity error from the Layer 2 cache has been detected and corrected. Normal system operation should continue. |
- |
"If there is a regular or sustained occurrence of this message copy" "the error message exactly as it appears and report it to" "technical support representative." |
|
BCM-4-ECC_MEMORY |
4-Warning |
Corrected ECC from memory |
A soft-parity error from the memory has been detected and corrected. Normal system operation should continue. |
- |
"If there is a regular or sustained occurrence of this message copy" "the error message exactly as it appears and report it to" "technical support representative." |
|
BCM5396-3- BAD_MODEL_ID |
3-Error |
Unexpected model id: 0x%X |
The model ID of the part was not correct |
ubr10k-sw |
"Investigate possible error with Raven or GigE switch." |
|
BCM5396-3- MDIO_TIMEOUT |
3-Error |
MDIO Timeout [chars] |
No response was received from the GigE switch MDIO interface |
ubr10k-sw |
"Investigate possible Raven MDIO interface" |
|
BCM5396-3- MODEL_ID |
3-Error |
Failed to read model id |
Failed to read a register via MDIO. |
ubr10k-sw |
"Investigate possible error with Raven or GigE switch." |
|
BCM5396-3- READ_TIMEOUT |
3-Error |
Timeout waiting for read pg [dec] addr [dec] len [dec] |
Failed to read a page register via MDIO. |
ubr10k-sw |
"Investigate possible error with Raven or GigE switch." |
|
BCM5396-3- WRITE_TIMEOUT |
3-Error |
Timeout waiting for write pg [dec] addr [dec] len [dec] |
Failed to read a page register via MDIO. |
ubr10k-sw |
"Investigate possible error with Raven or GigE switch." |
|
BD_VIF-5-CREATE_DELETE |
5-Notice |
Interface [chars] is [chars] |
BD-VIF interface create/delete events. |
l2-bdomain |
LOG_STD_NO_ACTION |
|
BDI_IF-5-CREATE_DELETE |
5-Notice |
Interface [chars] is [chars] |
BDI interface create/delete events. |
l2-bdomain |
LOG_STD_NO_ACTION |
|
BDOMAIN_BE_SW-3-BDI_ENCAP_NOT_SUPPORTED |
3-Error |
BDI Encap is not supported in IOL use EFP to pop vlan tags |
- |
- |
- |
|
BDOMAIN_BE_SW-3-L2FIB_ENTRY_GENERAL |
3-Error |
[chars] |
The bridge-domain receives wrong info from L2FIB |
l2fib |
"If the error persists the router may need to " "be reloaded" |
|
BDOMAIN_BE_SW-3-L2FIB_ENTRY_INVALID |
3-Error |
Null SW Handle from L2FIB [chars] |
The bridge-domain receives a null handle from L2FIB |
l2fib |
"If the error persists the router may need to " "be reloaded" |
|
BDOMAIN_BE_SW-3-PORT_MACS_NOT_ZERO |
3-Error |
The port [chars] is being removed while MAC entries still exist |
The specified port is being removed before all learned MAC entries have been removed. |
ether-infra |
"If other error messages related to removing MAC " "entries have been reported then copy those down " "exactly. Contact your Cisco technical support " "representative and provide the gathered " "information." |
|
BDOMAIN_BE_SW-3-REM_MAC_ENTRY_FAILED |
3-Error |
Unable to remove MAC entry [enet] in bridge-domain [dec] |
The bridge-domain was unable to remove the learned MAC address entry from it's database. |
ether-infra |
"If the error persists the router may need to " "be reloaded" |
|
BDOMAIN_BE_SW-4-PORT_MAX_MAC_ENTRIES |
4-Warning |
The port [chars] has reached the maximum number of learned MAC entries [dec] |
The specified port has reached the maximum number of learned MAC entries. It will not learn more until some of the entries are removed. This may happen when the entries age out. If this error persists it may indicate that there are too many nodes on the specified port or that the age out timer is too long. |
ether-infra |
"MAC entries should be removed by the system as " "they age out. No action is required." |
|
BDOMAIN-3-MACSEC_BE_INIT_FAIL |
3-Error |
Bridge-domain MAC Security back-end subsystem did not initialize correctly Reason: [chars]. |
An internal software error occurred. |
ether-infra |
LOG_STD_ACTION |
|
BDOMAIN-3-MAT_BE_DEL_FAIL |
3-Error |
Bridge-domain back-end subsystem failed to delete BD [dec] MAC Table entry [chars] Reason: [chars]. |
An internal software error occurred. |
ether-infra |
LOG_STD_ACTION |
|
BDOMAIN-3-MAT_BE_INIT_FAIL |
3-Error |
Bridge-domain MAC Table back-end subsystem did not initialize correctly Reason: [chars]. |
An internal software error occurred. |
ether-infra |
LOG_STD_ACTION |
|
BDOMAIN-3-PP_VFI_CFG_FAIL |
3-Error |
Unable to add this neighbor to the target bridge-domain Reason: [chars]. |
An internal software error occurred. |
ether-infra |
LOG_STD_ACTION |
|
BDOMAIN-3-STAMAC_BE_INIT_FAIL |
3-Error |
Bridge-domain Static MAC back-end subsystem did not initialize correctly Reason: [chars]. |
An internal software error occurred. |
ether-infra |
LOG_STD_ACTION |
|
BDOMAIN-3-STAMAC_SSP_SSO_STAMAC_CFG_FAIL |
3-Error |
Standby-SP cannot configure Static MAC to back-end subsystem after reaching SSO mode Reason: [chars]. |
An internal software error occurred. |
ether-infra |
LOG_STD_ACTION |
|
BDOMAIN-4-MAC_LIMIT_VIOL_BD_LIMIT |
4-Warning |
Attempt to learn a new MAC on [chars] caused configured bridge-domain limit [dec] to be exceeded. |
The bridge-domain specified in the system message is not allowed to learn addresses beyond the limit specified in the system message. A service instance belonging to this bridge-domain received a frame with unknown source MAC address and if this address is learnt it would cause the bridge-domain limit to be exceeded. The address has not been learnt. |
ether-infra |
- |
|
BDOMAIN-4-MAC_LIMIT_VIOL_INST_LIMIT |
4-Warning |
Attempt to learn a new MAC on [chars] caused configured service instance limit [dec] to be exceeded. |
The ethernet service instance specified in the system message is not allowed to learn addresses beyond the limit specified in the system message. This service instance received a frame with unknown source MAC address and if this address is learnt it would cause the limit to be exceeded. The address has not been learnt. |
ether-infra |
- |
|
BDOMAIN-4-MAC_LIMIT_VIOL_SYS_LIMIT |
4-Warning |
Attempt to learn a new MAC on [chars] caused system limit [dec] to be exceeded. |
It is not allowed to learn addresses beyond the system limit. A service instance received a frame with unknown source MAC address and if this address is learnt it would cause the system limit to be exceeded. The address has not been learnt. |
ether-infra |
- |
|
BEEP-3-SESSION_ERR |
3-Error |
[chars] at [chars]:[dec] |
The BEEP subsystem had an error and may stop running. |
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 |
|
BEEP-3-SLOG_LINE |
3-Error |
[chars] [chars] |
This is an internal BEEP library error message. |
beep |
LOG_STD_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-SLOG_LINE_TB |
3-Error |
[chars] [chars] |
This is an internal BEEP library error message. |
beep |
LOG_STD_ACTION |
|
BERT-3-BERT_ALREADY_TEST |
3-Error |
A BERT is already running |
- |
- |
"" |
|
BERT-3-BERT_BAD_INTERFACE |
3-Error |
Interface [dec] is down BERT cannot be executed on this interface |
- |
- |
"" |
|
BERT-3-BERT_INVPROFILE |
3-Error |
The Profile [dec] is not Valid |
- |
- |
"" |
|
BERT-3-BERT_INVPROFILE_CHANGE |
3-Error |
Profile [dec] currently under test cannot modify |
- |
- |
"" |
|
BERT-3-BERT_NO_CONT |
3-Error |
Controller [dec] does not exist |
- |
- |
"" |
|
BERT-6-BERT_FINISH_TIMESLOTS |
6-Information |
Finished Generation of Data for timeslots [dec] to [dec] on interface [dec] using profile [dec] |
- |
- |
"" |
|
BERT-6-BERT_RESULTS |
6-Information |
[chars] |
- |
- |
"" |
|
BERT-6-BERT_START |
6-Information |
Starting BERT on Interface [dec] with Profile [chars] |
- |
- |
"" |
|
BERT-6-BERT_TIMESLOTS |
6-Information |
No Results will be generated for this Test |
- |
- |
"" |
|
BFD_CFG-3-MALLOC |
3-Error |
Malloc failure [chars] |
malloc failure |
bfd |
LOG_STD_ACTION |
|
BFD_CFG-3-MALLOC_CFG |
3-Error |
Malloc failure [chars] [chars] |
malloc failure |
bfd |
LOG_STD_ACTION |
|
BFD_CFG-3-WAVL_DELETE |
3-Error |
Wavl delete failed for %p |
wavl delete failed. |
bfd |
LOG_STD_ACTION |
|
BFD_CFG-3-WAVL_INIT_FAIL |
3-Error |
Failed initializing wavl tree |
wavl_init failed. |
bfd |
LOG_STD_ACTION |
|
BFD_CFG-3-WAVL_INSERT_FAIL |
3-Error |
Wavl insert failed [chars] [chars] |
wavl insert failed. |
bfd |
LOG_STD_ACTION |
|
BFD_DAMP-5-ZERODELAY |
5-Notice |
Dampening reuse timer is updated with 0 delay time |
Inconsistency of dampening reuse timer wheel |
bfd |
LOG_STD_NO_ACTION |
|
BFD_HA-2-CF |
2-Critical |
[chars][dec] |
CF related error |
bfd |
LOG_STD_ACTION |
|
BFD_HA-2-ET |
2-Critical |
[chars][dec] |
Enhanced-timer error |
bfd |
LOG_STD_ACTION |
|
BFD_HA-2-RESOURCE |
2-Critical |
[chars] |
System resource error occured |
bfd |
LOG_STD_ACTION |
|
BFD_ISSU-2-GET_BUFFER |
2-Critical |
BFD ISSU client failed to get buffer for message. Error: [dec] [chars] |
The BFD 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. |
bfd |
"show logging and show checkpoint client" |
|
BFD_ISSU-2-INIT |
2-Critical |
BFD ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The BFD 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. |
bfd |
LOG_STD_ACTION |
|
BFD_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
BFD ISSU client failed to send negotiation message. Error: [dec] [chars] |
The BFD 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. |
bfd |
"show logging and show checkpoint client" |
|
BFD_ISSU-2-SESSION_NEGO |
2-Critical |
BFD ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The BFD 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. |
bfd |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
BFD_ISSU-2-SESSION_REGISTRY |
2-Critical |
BFD ISSU client failed to register session information. Error: [dec] [chars] |
The BFD ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
bfd |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
BFD_ISSU-3-INVALID_SESSION |
3-Error |
BFD ISSU client does not have a valid registered session. |
The BFD ISSU client does not have a valid registered session. |
bfd |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
BFD_ISSU-3-MSG_SIZE |
3-Error |
BFD ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The BFD ISSU client failed to calculate the MTU for the specified message. The BFD ISSU client is not able to send the message to the standby device. |
bfd |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
BFD_ISSU-3-SESSION_UNREGISTRY |
3-Error |
BFD ISSU client failed to unregister session information. Error: [dec] [chars] |
The BFD ISSU client failed to unregister session information. |
bfd |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
BFD_ISSU-3-TRANSFORM_FAIL |
3-Error |
bfd ISSU client [chars] transform failed for message [dec]'. Error: [dec] [chars] |
The BFD 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 BFD state between the active device and the standby device is not identical. |
bfd |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
BFD_MAP-3-MALLOC |
3-Error |
Malloc failure [chars] |
malloc failure |
bfd |
LOG_STD_ACTION |
|
BFD_MAP-3-MALLOC_MAP |
3-Error |
Malloc failure [chars] [chars] |
malloc failure |
bfd |
LOG_STD_ACTION |
|
BFD_MAP-3-WAVL_DELETE |
3-Error |
Wavl delete failed for %p |
wavl delete failed. |
bfd |
LOG_STD_ACTION |
|
BFD_MAP-3-WAVL_INIT_FAIL |
3-Error |
Failed initializing wavl tree |
wavl_init failed. |
bfd |
LOG_STD_ACTION |
|
BFD_MAP-3-WAVL_INSERT_FAIL |
3-Error |
Wavl insert failed [chars] [chars] |
wavl insert failed. |
bfd |
LOG_STD_ACTION |
|
BFD_MPLS-3-CFC_REG_FAIL |
3-Error |
CFC registration failed rc [dec] |
CFC registration failed. |
bfd |
LOG_STD_ACTION |
|
BFD_MPLS-3-CFC_UNREG_FAIL |
3-Error |
CFC unregistration failed rc [dec] |
CFC unregistration failed. |
bfd |
LOG_STD_ACTION |
|
BFD_MPLS-3-TP_LSP |
3-Error |
Session not created for intf [chars]/lsp [dec]. In-label [dec] in use for intf [chars]/lsp [dec] |
BFD session mismatch. |
bfd |
LOG_STD_ACTION |
|
BFD_OFFLOAD-3-ALLOC_FAILED |
3-Error |
Allocation of [chars] memory failed for BFD Offload feature in QFP |
Allocation of memory by the QFP BFD Offload feature microcode failed. The name of the memory chunk is specified in the message. This indicates a software failure |
asr1k-bfd |
LOG_STD_ACTION |
|
BFD_OFFLOAD-3-HA_BULK_SYNC_FAIL |
3-Error |
rg [dec] |
There was a failure such that BFD Offload domain bulk sync did not occur |
cpp-ucode |
LOG_STD_ACTION |
|
BFD_OFFLOAD-3-HA_INVALID_STATE |
3-Error |
state [dec] |
An invalid HA state was received from the HA infrastructure. |
cpp-ucode |
LOG_STD_ACTION |
|
BFD_OFFLOAD-3-INIT_FAILED |
3-Error |
Initialization of the BFD Offload feature in QFP failed |
Initialization of the BFD Offload feature in the QFP failed. This indicates a software failure. |
asr1k-bfd |
LOG_STD_ACTION |
|
BFD_OFFLOAD-3-PKT_REPLICA_INIT_FAILED |
3-Error |
Failed to register with generic packet replication for BFD Offload feature in QFP |
BFD Offload initialization of packet replication registration failed. |
asr1k-bfd |
LOG_STD_ACTION |
|
BFD_PROXY-2-PROXY_IPC_INIT_FAILED |
2-Critical |
QFP BFD Proxy IPC interface initialization failure result: [dec]. |
Cisco internal software error. QFP BFD Proxy initialization detected that the IPC interface initialization failed. QFP BFD proxy will not be functional while this condition exists. |
asr1k-bfd keyword:bfd |
LOG_STD_ACTION |
|
BFD_PROXY-3-BFD_MEM_EXTEND_FAILED |
3-Error |
BFD IPC subtype: [dec] |
Extending memory failed. |
asr1k-bfd keyword:bfd |
LOG_STD_ACTION |
|
BFD_PROXY-3-BFD_MEM_REQ_FAILED |
3-Error |
BFD IPC subtype: [dec] |
Requesting more memory failed. |
asr1k-bfd keyword:bfd |
LOG_STD_ACTION |
|
BFD_PROXY-3-PROXY_BAD_MSG |
3-Error |
QFP BFD Proxy received bad length message type [dec] |
Cisco internal software error. QFP BFD Proxy received a corrupted message from control plane. This message will be ignored. |
asr1k-bfd keyword:bfd |
LOG_STD_ACTION |
|
BFD_PROXY-3-PROXY_IPC_ALLOC_FAILED |
3-Error |
QFP BFD Proxy [chars] message lost due to message buffer allocation failure. |
Cisco internal software error. QFP BFD Proxy message processing detected a message buffer allocation failure. The message is lost as the result of this condition. |
asr1k-bfd keyword:bfd |
LOG_STD_ACTION |
|
BFD_PROXY-3-PROXY_IPC_SEND_FAILED |
3-Error |
QFP BFD Proxy [chars] message lost due to message sent failure result: [dec]. |
Cisco internal software error. QFP BFD Proxy message processing detected a message sent failure. The message is lost as the result of this condition. |
asr1k-bfd keyword:bfd |
LOG_STD_ACTION |
|
BFD_PROXY-4-PROXY_INVALID_MSG |
4-Warning |
QFP BFD Proxy received invalid message type [dec] |
Cisco internal software error. QFP BFD Proxy received an invalid message from control plane. This message will be ignored. |
asr1k-bfd keyword:bfd |
LOG_STD_ACTION |
|
BFD_PROXY-4-PROXY_INVALID_MSG_LEN |
4-Warning |
QFP BFD Proxy IPC invalid length [dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Cisco internal software error. QFP BFD Proxy received invalid IPC message length from control plane. This message will be ignored. |
asr1k-bfd keyword:bfd |
LOG_STD_ACTION |
|
BFD_TEST-3-BAD_ADDR_TYPE |
3-Error |
Invalid address type [dec] |
invalid address type |
bfd |
LOG_STD_ACTION |
|
BFD_TEST-3-BAD_TYPE |
3-Error |
Invalid session type [dec] |
invalid session type |
bfd |
LOG_STD_ACTION |
|
BFD_TEST-3-RESOURCE |
3-Error |
Cannot add BFD TEST as RF client. Return code [dec] |
RF client id failed. |
bfd |
LOG_STD_ACTION |
|
BFD_TEST-3-RF_INIT_FAIL |
3-Error |
Failed initializing Redundnacy Facility for BFD stub client. |
stub RF init failed. |
bfd |
LOG_STD_ACTION |
|
BFD_TEST-3-WAVL_INIT_FAIL |
3-Error |
Failed initializing wavl tree. |
wavl_init failed. |
bfd |
LOG_STD_ACTION |
|
BFD_TEST-3-WAVL_INSERT_FAIL_IPV4 |
3-Error |
Failed inserting neighbor address %30i to wavl tree thread [dec] |
wavl insert failed for ipv4. |
bfd |
LOG_STD_ACTION |
|
BFD_TEST-3-WAVL_INSERT_FAIL_IPV6 |
3-Error |
Failed inserting neighbor address %30P to wavl tree thread [dec] |
wavl insert failed for ipv6. |
bfd |
LOG_STD_ACTION |
|
BFD_TEST-3-WAVL_INSERT_FAIL_PW |
3-Error |
Failed inserting neighbor address %30i and vcid %lu to wavl tree thread [dec] |
wavl insert failed for pw. |
bfd |
LOG_STD_ACTION |
|
BFD_TEST-3-WAVL_TREE |
3-Error |
Failed to malloc space for wavl tree. |
wavl tree malloc failed. |
bfd |
LOG_STD_ACTION |
|
BFD_TEST-3-WAVL_WALK_FAIL |
3-Error |
wavl_walk failed while walking wavl tree thread [dec] interface [dec] |
wavl walk of a thread failed. |
bfd |
LOG_STD_ACTION |
|
BFD-3-BUFPOOL |
3-Error |
Creation of BFD Private Buffer Pool failed |
could not create private buffer pool |
bfd |
LOG_STD_ACTION |
|
BFD-3-CHUNK |
3-Error |
Chunk malloc failure - [chars] - 0x%X |
chunk malloc failure |
bfd |
LOG_STD_ACTION |
|
BFD-3-CHUNK_DESTROY |
3-Error |
Unable to destroy [chars] [chars] |
chunk destroy failure |
bfd |
LOG_STD_ACTION |
|
BFD-3-IF_IN_USE |
3-Error |
Interface [chars][dec] already in use |
interface number is already in use |
bfd |
LOG_STD_ACTION |
|
BFD-3-ILL_IF |
3-Error |
Illegal interface [dec][chars] |
interface number is out of range for platform |
bfd |
LOG_STD_ACTION |
|
BFD-3-INVQELEM |
3-Error |
Invalid queue element - [chars] |
invalid queue element |
bfd |
LOG_STD_ACTION |
|
BFD-3-INVVER |
3-Error |
Invalid version type |
invalid version type |
bfd |
LOG_STD_ACTION |
|
BFD-3-NO_TYPE |
3-Error |
Neighbor address type not specified as ADDR_IP[dec] [dec] |
- |
- |
- |
|
BFD-3-NOBOOLEAN |
3-Error |
Failed to create watched boolean |
could not create watched boolean |
bfd |
LOG_STD_ACTION |
|
BFD-3-NOCLIENT |
3-Error |
Client not found |
client does not exist in client list |
bfd |
LOG_STD_ACTION |
|
BFD-3-NOIOUPROC |
3-Error |
Failed to create BFD IOU Process |
IOU process failed to start |
bfd |
LOG_STD_ACTION |
|
BFD-3-NOKADIS |
3-Error |
Failed to start Kadis. Status [dec] |
kadis failed to start |
bfd |
LOG_STD_ACTION |
|
BFD-3-NOKADIS_TICK |
3-Error |
Failed to get kadis timer tick to start kadis timer. |
kadis failed to get timer tick |
bfd |
LOG_STD_ACTION |
|
BFD-3-NOPPPROC |
3-Error |
Failed to create BFD PP Process |
pseudo-preemptive process failed to start |
bfd |
LOG_STD_ACTION |
|
BFD-3-PACKET |
3-Error |
bfd_pak_coalesce - [chars] failed |
could not obtain or coalesce packet buffer |
bfd |
LOG_STD_ACTION |
|
BFD-3-WAVL_DELETE_FAIL_IPV4 |
3-Error |
Failed deleting node for neighbor [inet] to wavl tree thread [dec] [chars] |
- |
- |
- |
|
BFD-3-WAVL_DELETE_FAIL_IPV6 |
3-Error |
Failed deleting node for neighbor %39P to wavl tree thread [dec] [chars] |
- |
- |
- |
|
BFD-3-WAVL_DELETE_FAIL_MPLS_PW |
3-Error |
Failed deleting node for neighbor [inet] : vcid [dec] to wavl tree thread [dec] [chars] |
- |
- |
- |
|
BFD-3-WAVL_DELETE_FAIL_MPLS_TE_GAL_LSP |
3-Error |
Failed deleting node for LSP [chars] [dec] to wavl tree thread [dec] [chars] |
- |
- |
- |
|
BFD-3-WAVL_DELETE_FAIL_MPLS_TE_SR_LSP |
3-Error |
Failed deleting node for LSP [chars] [dec] to wavl tree thread [dec] [chars] |
- |
- |
- |
|
BFD-3-WAVL_DELETE_FAIL_MPLS_TP_LSP |
3-Error |
Failed deleting node for LSP [chars] [chars] to wavl tree thread [dec] [chars] |
- |
- |
- |
|
BFD-3-WAVL_DELETE_FAIL_POCH_IPV4 |
3-Error |
Failed deleting node for neighbor [inet] to wavl tree thread [dec] [chars] |
- |
- |
- |
|
BFD-3-WAVL_INIT_FAIL |
3-Error |
Failed initializing wavl tree. |
wavl_init failed. |
bfd |
LOG_STD_ACTION |
|
BFD-3-WAVL_INSERT_FAIL_IPV4 |
3-Error |
Failed inserting node for neighbor [inet] to wavl tree thread [dec] [chars] |
- |
- |
- |
|
BFD-3-WAVL_INSERT_FAIL_IPV6 |
3-Error |
Failed inserting node for neighbor %39P to wavl tree thread [dec] [chars] |
- |
- |
- |
|
BFD-3-WAVL_INSERT_FAIL_MPLS_PW |
3-Error |
Failed inserting node for neighbor [inet] : vcid [dec] to wavl tree thread [dec] [chars] |
- |
- |
- |
|
BFD-3-WAVL_INSERT_FAIL_MPLS_TE_GAL_LSP |
3-Error |
Failed inserting node for LSP [chars] [dec] to wavl tree thread [dec] [chars] |
- |
- |
- |
|
BFD-3-WAVL_INSERT_FAIL_MPLS_TE_SR_LSP |
3-Error |
Failed inserting node for LSP [chars] [dec] to wavl tree thread [dec] [chars] |
- |
- |
- |
|
BFD-3-WAVL_INSERT_FAIL_MPLS_TP_LSP |
3-Error |
Failed inserting node for LSP [chars] [chars] to wavl tree thread [dec] [chars] |
- |
- |
- |
|
BFD-3-WAVL_INSERT_FAIL_POCH_IPV4 |
3-Error |
Failed inserting node for neighbor [inet] to wavl tree thread [dec] [chars] |
- |
- |
- |
|
BFD-3-WAVL_TREE |
3-Error |
Failed to malloc space for wavl tree. |
wavl tree malloc failed. |
bfd |
LOG_STD_ACTION |
|
BFD-6-BFD_IF_CONFIGURE |
6-Information |
BFD-SYSLOG: bfd config apply idb:[chars] |
bfd config change |
bfd |
LOG_STD_NO_ACTION |
|
BFD-6-BFD_SESS_CREATED |
6-Information |
BFD-SYSLOG: bfd_session_created neigh [chars] proc:[chars] idb:[chars] handle:[dec] [chars] |
bfd session created |
bfd |
LOG_STD_NO_ACTION |
|
BFD-6-BFD_SESS_DESTROYED |
6-Information |
BFD-SYSLOG: bfd_session_destroyed [chars] neigh proc:[chars] handle:[dec] [chars] |
bfd session destroyed |
bfd |
LOG_STD_NO_ACTION |
|
BFD-6-BFD_SESS_GET_LD |
6-Information |
BFD-SYSLOG: bfd session get local discriminator [chars] neigh proc:[chars] handle:[dec] node: [chars] |
Get bfd session local discriminator |
bfd |
LOG_STD_NO_ACTION |
|
BFD-6-BFD_VRRPV3_SW_SESS_INVALID |
6-Information |
BFD-SYSLOG: ABORT: BFD session for VRRPv3 client on interface: [chars] NOT supported in software handle:[dec] adjacency: [chars] node: [chars] |
bfd vrrpv3 sofware session offloading NOT supported |
bfd |
LOG_STD_NO_ACTION |
|
BFD-6-MAX_DESCR |
6-Information |
BFD discrminators exhausted. No more sessions can be created. |
Max. discriminators assigned |
bfd |
LOG_STD_ACTION |
|
BFD-6-MAX_SESSION |
6-Information |
Maximum session creation limit [dec] for [chars] sessions reached. |
Max. sessions created |
bfd |
LOG_STD_ACTION |
|
BFD-6-TIMER_NOT_SUPP |
6-Information |
BFD timer value on interface [chars] is below the supported value of [dec] ms |
Fast timers not supported on slow interface |
bfd |
LOG_STD_ACTION |
|
BFD-6-TIMERS_NOT_SUPPORTED |
6-Information |
BFD timer value Tx: [dec] and Rx: [dec] are not supported for software sessions |
Timers not supported for software sessions |
bfd |
LOG_STD_ACTION |
|
BFD-6-TX_ON_STANDBY |
6-Information |
BFD transmit detected on standby |
BFD packet transmission on standby |
bfd |
LOG_STD_ACTION |
|
BFDFSM-3-INVEVENT |
3-Error |
Invalid event_id 0x%X |
state machine invalid event |
bfd |
LOG_STD_ACTION |
|
BFDFSM-3-INVSTATE |
3-Error |
Invalid current state 0x%X |
state machine invalid state |
bfd |
LOG_STD_ACTION |
|
BFDFSM-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 |
bfd |
LOG_STD_ACTION |
|
BFDFSM-3-NOEVENT |
3-Error |
Unable to apply event 0x%08X |
state machine transition failure |
bfd |
LOG_STD_ACTION |
|
BFDFSM-3-NULLMACH |
3-Error |
Invalid machine pointer 0x%X |
state machine invalid pointer |
bfd |
LOG_STD_ACTION |
|
BFDFSM-6-BFD_SESS_DOWN |
6-Information |
BFD-SYSLOG: BFD session [chars] is going Down Reason: [chars] |
bfd session down |
bfd |
LOG_STD_NO_ACTION |
|
BFDFSM-6-BFD_SESS_UP |
6-Information |
BFD-SYSLOG: BFD session [chars] is going UP |
bfd session Up |
bfd |
LOG_STD_NO_ACTION |
|
BGP_LMM-3-ASSERT |
3-Error |
Assert failed at [chars]:[dec] |
An internal software error has occurred |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_LMM-3-AUTOGEN |
3-Error |
[chars] Neighbor: [chars] Interface: [chars] |
There was an error while auto-generating the mpls bgp forwarding command on an interface |
mpls-vpn |
"Manually configure the mpls bgp forwarding command" " on the interface referenced in the error message." "If the problem persists copy the message exactly as" "it appears and report it to your customer service" "representative" |
|
BGP_LMM-3-CFC1 |
3-Error |
[chars] [chars] |
Error in BGP LMM and CFC interaction |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_LMM-3-CFC2 |
3-Error |
[chars] [chars] [chars] |
Interaction error between BGP LMM and CFC |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_LMM-3-IPRMCONNECT |
3-Error |
[chars] Address-family [chars] |
BGP LMM AF registration/de-registration with IPRM failed |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_LMM-3-LSD1 |
3-Error |
[chars] [chars] |
Error in BGP LMM and LSD interaction |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_LMM-3-LSD2 |
3-Error |
[chars] [chars] [chars] |
Interaction error between BGP LMM and LSD |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_LMM-3-MEM |
3-Error |
[chars] |
Error in memory management |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_LMM-3-NBRROUTE |
3-Error |
[chars] Neighbor: [chars] Interface: [chars] |
A host route to an MPLS enabled BGP neighbor was not present in the routing table the problem was corrected by installing the route |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_LMM-3-PATH |
3-Error |
[chars] label: [dec] next hop: [dec] |
Invalid information in a BGP path |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_LMM-3-REENTRY |
3-Error |
[chars] |
A non re-entrant routine has been re-entered |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_LMM-3-SIZEMISMATCH |
3-Error |
Label table size [dec] mismatch checkpoint key creation failed |
MPLS Label Table ID size mismatch. |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_LMM-3-VRFAGGR |
3-Error |
[chars] [dec] |
Error during per VRF aggregate label processing |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_LMM-4-LABEL |
4-Warning |
[chars] [chars] |
Error during allocation/freeing of a label |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_LMM-6-AUTOGEN1 |
6-Information |
[chars] interface: [chars] |
The mpls bgp forwarding command has been automatically configured on an interface |
- |
"This is an informational message no action is " "required by the operator" |
|
BGP_LMM-6-MPLS_INIT |
6-Information |
MPLS has been [chars] for the BGP address-family [chars] |
MPLS has been enabled/disabled for a given BGP address-family |
- |
"This is an informational message no action is " "required by the operator" |
|
BGP_LMM-6-PERCE1 |
6-Information |
Per CE label global keyid wrap trigger label reallocation |
Per CE label global keyid wrap trigger label reallocation |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_MPLS-3-GEN_ERROR |
3-Error |
[chars] |
BGP MPLS related general runtime errors message contents will show the error |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_MPLS-3-IPRMCONNECT |
3-Error |
[chars] |
BGP VPNv4 failed to register to IPRM component. |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_MPLS-3-IPV4_AGGR_LABEL |
3-Error |
global aggr label: [chars] |
This is related to a common AGGREGATE LABEL for all aggregate prefixes in global routing table. |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_MPLS-3-LABELALLOC |
3-Error |
[chars] |
An MPLS label could not be allocated for a prefix due to an internal error |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_MPLS-3-LSDCONNECT |
3-Error |
[chars] |
BGP VPNv4 failed to register to MPLS Forwarding component. |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_MPLS-3-NBR_ROUTE |
3-Error |
[chars] |
Problems with manipulating the bgp neighbor route needed for MPLS operations |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_MPLS-3-PER_VRF_AGGR |
3-Error |
pervrfaggr label: [chars] |
This is related to PER VRF AGGREGATE LABEL feature |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_MPLS-3-SIZEMISMATCH |
3-Error |
Label table size [dec] mismatch checkpt key creation failed |
BGP MPLS Label Table size mismatch. |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_MPLS-3-VPN_REWRITE |
3-Error |
[chars] |
Problems with installing updating or removing a VPN rewrite entry in the MPLS forwarding table |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_MPLS-7-IASLABELALLOC |
7-Debug |
Failed to create rewrite prefix [chars] result [chars] |
BGP MPLS VPN rewrite creation failed. |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_MPLS-7-IPv4LABELALLOC |
7-Debug |
Failed to allocate label for IPv4 prefix [inet]/[dec] |
BGP MPLS IPv4 label allocation failed. |
mpls-vpn |
LOG_STD_ACTION |
|
BGP_SESSION-5-ADJCHANGE |
5-Notice |
neighbor [chars] [chars][chars][chars] topology [chars] removed from session [chars] |
A BGP neighbor topology was removed from a session. The message\n\ describes the change for it. This message appears only if the \n\ <Bold>log-neighbor-changes<nobold> command is configured for\n\ the BGP process. |
- |
"This informational message normally appears as routers and\n\ BGP 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." |
|
BGP-2-INSUFMEM |
2-Critical |
Insufficient memory for [chars] entry |
The requested operation could not be accomplished because of a low\n\ memory condition. |
- |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
BGP-3-ADDBLOCK |
3-Error |
Unable to add blocked dynamic peer [chars] |
Not able to save the specified data due to an error |
- |
LOG_STD_ACTION |
|
BGP-3-ADDCID |
3-Error |
Unable to add Cluster ID [chars]. |
A addition to a cluster ID structure could not be completed because\n\ of an error. |
- |
LOG_STD_ACTION |
|
BGP-3-ADDNETWORK |
3-Error |
Unable to add network for [chars] to radix trie |
An addition to the radix trie could not be completed because\n\ of an error. |
- |
LOG_STD_ACTION |
|
BGP-3-ADDROUTE |
3-Error |
Unable to add route for [chars] to radix trie |
An addition to the radix trie could not be completed because\n\ of an error. |
- |
LOG_STD_ACTION |
|
BGP-3-BADMASK |
3-Error |
Attempt to install route for [inet] without valid mask in [chars] |
A route can not be installed without a valid mask. |
- |
LOG_STD_ACTION |
|
BGP-3-BADROUTEMAP |
3-Error |
Bad parameters in the route-map [chars] applied for [chars] |
This means the route-map should be changed |
bgp |
"Correct the route-map" |
|
BGP-3-BGP_INCONSISTENT |
3-Error |
[chars] Inconsistent [chars] |
Inconsistency in the data structures |
bgp |
"This is a rare situation and is a result of internal problem." |
|
BGP-3-BGP_INTERNAL_ERR |
3-Error |
[chars] |
BGP Internal Error |
bgp |
LOG_STD_ACTION |
|
BGP-3-BGP_NO_REMOTE_READ |
3-Error |
[chars] connection timed out - has not accepted a message from us for [dec]ms hold time [dec] messages pending transmition. |
BGP failed to send UPDATE message to the neighbor for \n\ more than the hold timer. A Hold timer expiry NOTIFICATION \n\ is being sent and the session will be reset \n\ This message appears only if the <Bold>log-neighbor-changes<nobold> \n\ command is configured for the BGP process. |
bgp |
"BGP failed to send UPDATE message to the neighbor for \n\ more than the hold timer. A Hold timer expiry NOTIFICATION \n\ is being sent and the session will be reset." |
|
BGP-3-BGP_SR_POLICY_FAILURE |
3-Error |
BGP SR policy failed [chars] - Restarting BGP may be required |
This is a rare situation and the system likely is running out of memory. |
- |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration. If this messsage is\n\ after a configuration change the configuration should be reverted.\n\ BGP may need to be unconfigured and reconfigured to fully recover." |
|
BGP-3-BGP_SRTE_FAILURE |
3-Error |
BGP SRTE failed [chars] - Restarting BGP may be required |
This is a rare situation and the system likely is running out of memory. |
- |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration. If this messsage is\n\ after a configuration change the configuration should be reverted.\n\ BGP may need to be unconfigured and reconfigured to fully recover." |
|
BGP-3-BGP_SUBSYSTEM_INIT_FAILED |
3-Error |
BGP subsystem initialization failed: [chars] |
The BGP subsystem could not be initialized properly |
bgp |
LOG_STD_ACTION |
|
BGP-3-BMP_MEMORY |
3-Error |
BMP Memory Utilization currently at %lu exceeds threshold %lu |
BMP memory utilization tracked by BMP message alloc\n\ exceeds maximum memory allocation configured for BMP client |
- |
"Perform BMP deactivation on excessively churning\n\ BGP neighbors receiving large number of routes and reactivate\n\ after convergence" |
|
BGP-3-DELBLOCK |
3-Error |
Unable to remove blocked dynamic peer [chars] |
Not able to remove the specified data due to an error |
- |
LOG_STD_ACTION |
|
BGP-3-DELCID |
3-Error |
Unable to remove Cluster ID [chars]. |
A deletion of a cluster-id could not be completed because\n\ of an error. |
- |
LOG_STD_ACTION |
|
BGP-3-DELNETWORK |
3-Error |
Unable to remove network for [chars] from radix trie |
A deletion from the radix trie could not be completed because\n\ of an error. |
- |
LOG_STD_ACTION |
|
BGP-3-DELPATH |
3-Error |
Attempted to delete path from an empty net for [chars] |
A BGP path could not be deleted because of an error. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
BGP-3-DELROUTE |
3-Error |
Unable to remove route for [chars] from radix trie |
A deletion from the radix trie could not be completed because\n\ of an error. |
- |
LOG_STD_ACTION |
|
BGP-3-ENHANCED_REFRESH_STALEPATH |
3-Error |
Net [chars] from bgp neighbor [chars][chars][chars] [chars] is stale after [chars] rate-limited |
- |
- |
- |
|
BGP-3-EXTCOMMLIST_REFCOUNT_WRAPPING |
3-Error |
Extcommlist refcount [chars] wrapping |
- |
bgp |
- |
|
BGP-3-INSUFCHUNKS |
3-Error |
Insufficient chunk pools for [chars] requested size [dec] |
The static chunk pools size are not correct. |
bgp |
"Collect chunk and bgp summary. This is an internal software issue" |
|
BGP-3-MARTIAN_IP |
3-Error |
[chars] Martian prefix [chars] in [chars] |
Invalid MPLS label found in the BGP message |
bgp |
"This indicates that there is some problem on the remote router" |
|
BGP-3-MAXPFXEXCEED |
3-Error |
Number of prefixes received from [chars][chars][chars] afi [dec]: [dec] exceeds limit [dec] |
- |
- |
- |
|
BGP-3-MUTEX |
3-Error |
Waiting for turn to execute after [dec] seconds. |
- |
- |
LOG_STD_ACTION |
|
BGP-3-NEGCOUNTER |
3-Error |
Prefix-accepted counter negative for peer [chars] prefix [chars] |
The counter value for accepted prefixes is wrong and less than zero |
bgp |
"This is a rare situation and is a result of internal problem.\n\ Reset the session to correct it." |
|
BGP-3-NH_LABEL_INCONSISTENCY |
3-Error |
Net [chars] has Nexthop-Label inconsistency |
Bgp peers are not consistent with each other. |
- |
"Track the net copy the error message exactly as it appears and \n\ report it to your technical support representative." |
|
BGP-3-NOTIFICATION |
3-Error |
[chars] |
An error condition has been detected in the BGP session. A\n\ NOTIFICATION is being sent/received and the session will be reset.\n\ This message appears only if the <Bold>log-neighbor-changes<nobold> \n\ command is configured for the BGP process. |
bgp |
"This message represents an error in the session and its origin \n\ should be investigated. If the error is reported periodically copy\n\ it exactly as it appears and report it to your technical support \n\ representative." |
|
BGP-3-NOTIFICATION_MANY |
3-Error |
[chars] |
Notification sent to all the neighbors of the speaker.\n\ This message appears typically after doing 'clear ip bgp *'. |
bgp |
"If the error is unexpected report it to your technical support \n\ representative." |
|
BGP-3-ORF_EXTCOMMLIST |
3-Error |
Received misformatted extcommunity list ORF from [chars] |
The received prefixlist ORF is misformatted. |
bgp |
"Check the prefixlist ORF implementation on the neighboring router." |
|
BGP-3-ORF_PFXLIST |
3-Error |
Received misformatted prefixlist ORF from [chars] |
- |
- |
- |
|
BGP-3-RADIXINIT |
3-Error |
Radix trie initialization failed |
Initialization of the radix tree could not be accomplished because of\n\ a low memory condition. |
- |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
BGP-3-REFRESH_STALEPATH_COUNT |
3-Error |
[dec] stale-path[chars] deleted from bgp neighbor [chars][chars][chars] [chars] after [chars] |
BGP peers are not consistent with each other. |
- |
"BGP peers are not consistent with each other report it to your\n\ technical support representative.." |
|
BGP-3-RIBOUT_INCONSISTENCY |
3-Error |
Net [chars] in [chars][chars][chars] has rib-out inconsistency for update-group [dec] [chars]- outbound policy [chars] rib-out [chars] [chars][chars] |
Bgp peers are not consistent with each other. |
- |
"Track the net copy the error message exactly as it appears and \n\ report it to your technical support representative." |
|
BGP-4-AFIMPORT |
4-Warning |
[chars] prefixes imported to [chars] vrf reached the limit [dec] |
Number of prefixes imported from other address-family to a vrf reached configured limit |
bgp |
"Check the number of imported prefixes from the address-family and " "verify if the limit should be increased or the ip vrf import " "route-map is configured correctly." |
|
BGP-4-AO_KEYCHAIN |
4-Warning |
[chars] |
You have configured BGP AO to use a keychain which BGP can not use. |
bgp |
"Correct the key chain configuration." |
|
BGP-4-ATTRNULL |
4-Warning |
A NULL attribute has been assigned to a path |
The path should have been assigned a valid attribute but was incorrectly assigned a value of NULL |
bgp |
LOG_STD_ACTION |
|
BGP-4-BFD_NOT_ONEHOP |
4-Warning |
BFD is supported for single hop neighbors. [chars] is not single hop neighbor |
BFD is supported for single hop neighbors. The configured neighbor is not a single hop hence BFD is not enabled |
bgp |
"Deconfigure BFD from BGP as multihop " "neighbors are not supported in BFD" |
|
BGP-4-BGP_BAD_RPKI_MESSAGE |
4-Warning |
BGP received an invalid RPKI message from rpki server [chars] [chars] [chars] hex dump: [chars] |
BGP is configured to connect to an RPKI server. That server is sending malformed or incorrectly formatted messages to the router |
bgp |
"Check the configuration of our RPKI server " "and make sure that the server is updated to the " "latest version " |
|
BGP-4-BGP_GR_RELOAD_UNSAFE_HOLDTIME |
4-Warning |
GR reload unsafe configured holdtime[dec] the default safe |
You have configured an unsafe holdtime the default safe holdtime value is used instead. |
bgp |
"Configure the bgp holdtime value which is" " greater than the default safe holdtime" " value" |
|
BGP-4-BGP_GR_RELOAD_UNSAFE_SESSION_RESTART_TIME |
4-Warning |
GR reload unsafe configured session restart time[dec] |
You have configured an unsafe session restart time the default safe session restart time is used instead. |
bgp |
"Configure the bgp session restart time value " "which is greater than the default safe session" " restart time value" |
|
BGP-4-BGP_GR_RELOAD_UNSAFE_STALEPATH_TIME |
4-Warning |
GR reload unsafe configured nsf stalepath time[dec] |
You have configured an unsafe nsf stalepath time the default safe stalepath time is used instead. |
bgp |
"Configure the bgp nsf stalepath time value " "which is greater than the default safe stalepath" "time value." |
|
BGP-4-BGP_INH_POLICY |
4-Warning |
Failed to inherit [chars] policy config '[chars]': [chars]->[chars] [chars] [chars] |
BGP neighbor failed to inherit some policy configuration from a policy-template or peer-group because of some configuration imcompatibilities. The set of policy configurations that were compatible were still inherited. |
bgp |
LOG_STD_ACTION |
|
BGP-4-BGP_INH_SESSION |
4-Warning |
Failed to inherit [chars] session config '[chars]': [chars]->[chars] [chars] |
BGP neighbor failed to inherit some session configuration from a session-template or peer-group because of some configuration imcompatibilities. The set of session configurations that were compatible were still inherited. |
bgp |
LOG_STD_ACTION |
|
BGP-4-BGP_LABELS_NOT_SUPPORTED |
4-Warning |
BGP neighbor [chars] does not support sending labels |
You are attempting to configure send-label either directly or via a template for a neighbor which is connected over IPv6. Doing so is not supported |
bgp |
"Do not configure send-label for IPv6 peers" |
|
BGP-4-BGP_OUT_OF_MEMORY |
4-Warning |
BGP resetting because of memory exhaustion. |
BGP tried to perform an operation that required additional memory and was not able to allocate it. |
bgp |
"Reduce other system activity to ease memory " "demands or troubleshoot the system for memory " "fragmentation. If conditions warrant upgrade " "to a larger memory configuration." |
|
BGP-4-BGP_RF_REG_FAILED |
4-Warning |
BGP failed to register with the redundancy facility. |
BGP failed to register with the redundancy facility. If this happens stateful switchover for BGP will not work because BGP will not be able to sync any data from the active RP to the standby RP. |
bgp |
LOG_STD_ACTION |
|
BGP-4-BGP_RPKI_ERROR_MESSAGE |
4-Warning |
BGP received an RPKI Error Report PDU from rpki server [chars] [chars] [chars] hex dump [chars] |
The RPKI server that BGP is connected to is reporting. that the router sent it a malformed or incorrect PDU |
bgp |
"Check the configuration of the router and RPKI " "server and make sure that the server is updated " "to the latest version " |
|
BGP-4-BGP_SESSION_PARSE |
4-Warning |
Failed to parse [chars] neighbor config for neighbor [chars] [chars] [chars] |
BGP neighbor failed to parse neighbor configuration. |
bgp |
LOG_STD_ACTION |
|
BGP-4-INVALIDSIZE |
4-Warning |
invalid size for as_array has been entered |
- |
- |
LOG_STD_NO_ACTION |
|
BGP-4-MAX_EXTCOMM_EXCEED |
4-Warning |
Exceeded limit of [dec] extended communities per advertised prefix |
An attempt was made to advertise a prefix with an extended\n\ community attribute containing more extended communities\n\ than the allowed limit. |
bgp |
"Reduce the configured number of Route Targets or other extended\n\ communities that will be added to prefix advertisements so that\n\ the limit is not exceeded" |
|
BGP-4-MAXDYNNBR |
4-Warning |
BGP:DN: Cannot create new neighbor [chars] for\nrange [chars]: maximum number of [dec] dynamic neighbors limit reached |
Number of dynamically created subnet range neighhors reaches warning limit |
bgp |
"Check the number of listen range limit configured " "for dynamic subnet neighbors\n and verify if the " "limit should be increased." |
|
BGP-4-MAXPFX |
4-Warning |
Number of prefixes received from [chars][chars][chars] afi [dec] reaches [dec] max [dec] |
- |
- |
- |
|
BGP-4-MSGDUMP |
4-Warning |
unsupported or mal-formatted message received from [chars]: \n[chars] |
The remote BGP peer sent in a unsupported or mal-formatted message \n\ which caused the notification sent |
- |
LOG_STD_NO_ACTION |
|
BGP-4-MULTIPATH_LOOP |
4-Warning |
This may cause traffic loop if not used properly command accepted. |
Should be configured only at one of the edge routers that have ibgp \n\ peering among themselves. |
bgp |
LOG_STD_ACTION |
|
BGP-4-NBRTRACK |
4-Warning |
Route Tracking failed on memory. Neighbor tracking for route-fall-over will stop |
Route tracking system failed to allocate memory. Neighbor route fall-over will stop tracking neighbor routes. |
bgp |
"Route tracking system failed to allocate memory. Neighbor " "route fall-over will stop tracking neighbor routes so that " "it can give away some memory. If you think system is stable " "then reconfigure neighbor route fall-over. If you get this " "message neighbor route-fallover has been deconfigured." |
|
BGP-4-NORTRID |
4-Warning |
BGP could not pick a router-id. Please configure manually. |
BGP router-id has not been manually configured and BGP is unable to allocate a router ID from the IPv4 address of one of its interfaces. |
bgp |
"Make sure that there is at least one interface that is up and has a " "valid IPv4 address or configure the router-id manually." |
|
BGP-4-RIDSYNC |
4-Warning |
BGP routes are redistributed to OSPF. For synchronization to work you must manually configure the BGP router-id to be the same as the OSPF router-id. |
For synchronization to work BGP router-id must be the same as the\n OSPF router-id at all times that the router is up. |
bgp |
"If synchronization is turned on between one instance of OSPF\n" "and BGP make sure to manually configure a BGP router-id which\n" "is identical to the one of that particular OSPF instance." |
|
BGP-4-VPN_NH_IF |
4-Warning |
Nexthop [chars] may not be reachable from neigbor [chars] - not a loopback |
We are sending a vpn route to this IBGP neighbor and the nexthop is one\n\ of our directly connected physical interfaces.\n\ The label for the next hop address may be removed in the MPLS cloud\n\ one hop soon. Since the P routers don't have VPN information\n\ they don't know where to forward packets with the BGP label.\n\ This could break connectivity between VPN sites. |
bgp |
"Use loopback interfaces as the nexthops for vpn IBGP neighbors." |
|
BGP-4-VPNV4NH_MASK |
4-Warning |
Nexthop [inet] may not be reachable from neigbor [chars] - not /32 mask |
We are sending a vpnv4 route to this IBGP neighbor the nexthop\n\ address is our loopback which does not have /32 mask we are\n\ using OSPF on this loopback and the OSPF network type of this\n\ interface is LOOPBACK. OSPF advertizes this address\n\ as a host route with mask /32 regardless what mask is configured.\n\msgdef_recommended_action Configure the loopback used as the next hop with ip host mask |
- |
- |
|
BGP-5-ADJCHANGE |
5-Notice |
neighbor [chars][chars][chars][chars] [chars] |
A BGP neighbor has either come up or gone down. The message\n\ describes the change for it. This message appears only if the \n\ <Bold>log-neighbor-changes<nobold> command is configured for\n\ the BGP process. |
- |
"This informational message normally appears as routers and\n\ BGP 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." |
|
BGP-5-AGGRESSIVE_SCAN_TIME |
5-Notice |
bgp scan-time configuration less than [dec] seconds can cause high cpu usage by BGP Scanner. |
bgp scan-time configuration less than 15 seconds can cause high cpu usage by BGP Scanner. |
- |
"bgp scan-time configuration less than 15 seconds can cause high cpu " "usage by BGP Scanner. It is recommended to monitor the cpu usage of " "BGP Scanner." |
|
BGP-5-BGP_MAX_MSG_LIMIT |
5-Notice |
BGP failed to send update message because the message size reached bgp maximum message size 4096. |
BGP failed to send update message because the message size reached bgp maximum message size 4096. If this happens check the bgp paths that are learned if any of the paths have got many as-paths or ext-communities |
- |
LOG_STD_ACTION |
|
BGP-5-BGP_MAX_NSR_MSG_LIMIT |
5-Notice |
BGP failed to send update message because the IPC to support NSR is having size less than the requested size. |
BGP failed to send update message because the message size is bigger than the IPC of NSR. And the neighbor may not support route refresh capability. If this happens manually hard clear the neighbor session. |
bgp |
LOG_STD_ACTION |
|
BGP-5-BGP_UPDATE_ZERO_LENGTH |
5-Notice |
BGP failed to send update message because the message buffer size is calculated to be zero |
BGP failed to send update message because the message buffer size is calculated to be zero. If this happens check the bgp buffer size being calculated while sending the update for both 4byte/2byte speakers. |
bgp |
LOG_STD_ACTION |
|
BGP-5-BMP_ADJCHANGE |
5-Notice |
BMP Server [dec] - [chars]/[dec] connection [chars] |
A BMP server TCP connection has either come up or gone down |
- |
"This informational message normally appears as\n\ BMP servers come up or go down. If the BMP server keeps flapping\n\ its connection continuously for whatever reason flapping delay\n\ timer kicks in to regulate reconnection attempts" |
|
BGP-5-BMP_REFRESH_CAP_RCVD |
5-Notice |
Refresh cap not received from BGP nbr session [chars] BMP monitoring not possible |
BMP monitoring of neighbor session is not possible in\n\ route-refresh scheme for session if refresh cap is not negotiated |
- |
"This informational message indicates BMP" " monitoring of BGP session is not possible without upgrading BGP peer" " to a software version that supports route-refresh cap" |
|
BGP-5-DAMPENING_DECAY_TIME |
5-Notice |
Decay time from maximum penalty to suppress penalty is [dec] secs. Maximum penalty: [dec] suppress penalty: [dec] |
Configured dampening parameters may not be feasible. Time window between maximum penalty and suppress penalty may be low. |
bgp |
"If you think decay time from maximum penalty to suppress penalty " "is too low increase half-life time or maximum penalty values." |
|
BGP-5-DAMPENING_HIGH_MAX_PENALTY |
5-Notice |
Maximum penalty [dec] is more than allowed maximum [dec]. |
Configured dampening parameters may not be feasible. Maximum penalty is more than allowed maximum. Dampening will be OFF. |
bgp |
"Depending on the value of maximum penalty adjust maximum suppress " "time. Since maximum penalty is more than allowed maximum reduce " "maximum suppress time. Maximum penalty should be greater than " "suppress penalty but less than maximum allowable penalty." |
|
BGP-5-DAMPENING_LOW_MAX_PENALTY |
5-Notice |
Maximum penalty [dec] is less than suppress penalty [dec] |
Configured dampening parameters may not be feasible. Maximum penalty is less than configured suppress penalty. Dampening will be OFF |
bgp |
"Depending on the value of maximum penalty adjust maximum suppress " "time. Since maximum penalty is less than suppress penalty increase " "maximum suppress time. Maximum penalty should be greater than " "suppress penalty but less than maximum allowable penalty." |
|
BGP-5-NBR_RESET |
5-Notice |
Neighbor [chars] reset [chars] |
A BGP neighbor has been marked for reset. After all of resources assigned \n\ for the neighbor are freed the adjacency will be cleared down.\n\ This message appears only if the <Bold>log-neighbor-changes<nobold> \n\ command is configured for the BGP process. |
bgp |
"This message represents an error in the session was not reset \n\ because of administrative action of other valid event like an interface \n\ flap. If no valid event is detected report it to your technical support\n\ representative." |
|
BGP-5-SLOWPEER_DETECT |
5-Notice |
Neighbor [chars][chars][chars] [chars] has been detected as a slow peer. |
The BGP neighbor has been detected as a slow peer. |
- |
"The reason that the neighbor can not consume BGP update messages at the " "required rate should be investigated. Possible causes could be network " "congestion or high load on the peer." |
|
BGP-5-SLOWPEER_RECOVER |
5-Notice |
Slow peer [chars][chars][chars] [chars] has recovered. |
The slow BGP peer has recovered. |
- |
"This message is informational. The slow-peer has recovered." |
|
BGP-5-VERSION_WRAP |
5-Notice |
bgp version wrapped of [chars] |
The BGP table version has reached its maximum value and\n\ wrapped around. The message describes this event. |
- |
"This message is informational. However frequent occurrences\n\ of such event might indicate high error rates or high packet\n\ loss in the network and should be investigated." |
|
BGP-6-ASPATH |
6-Information |
[chars] AS path [chars] received from [chars]: [chars] |
- |
- |
- |
|
BGP-6-ATTR_DUP |
6-Information |
BGP update error: [chars] Duplicate [chars] attribute dropped by error handling |
- |
- |
- |
|
BGP-6-ATTR_FLAG |
6-Information |
BGP update error: [chars] Wrong flag 0x[hec] received for [chars] attribute fixed by error handling |
- |
- |
- |
|
BGP-6-ATTR_MISSING |
6-Information |
BGP update error: [chars] Missing mandatory attribute treat-as-withdraw by error handling |
- |
- |
- |
|
BGP-6-ATTR_WRONG_LEN |
6-Information |
BGP update error: [chars] Wrong length [dec] for [chars] dropped by error handling |
- |
- |
- |
|
BGP-6-BIGCHUNK |
6-Information |
Big chunk pool request [dec] for [chars]. Replenishing with malloc |
- |
- |
- |
|
BGP-6-MALFORMED_ATTR_SET |
6-Information |
Malformed attribute attr-set received from [chars] |
- |
- |
- |
|
BGP-6-MALFORMEDATTR |
6-Information |
Malformed attribute in [chars] |
- |
- |
- |
|
BGP-6-MSGDUMP_LIMIT |
6-Information |
unsupported or mal-formatted message received from [chars]: \n[chars] |
- |
- |
- |
|
BGP-6-NEXTHOP |
6-Information |
Invalid next hop [inet] received from [chars]: [chars] |
The remote BGP peer sent in a route with an illegal next hop.The given\n\ route was ignored. |
- |
LOG_STD_NO_ACTION |
|
BGP-6-NOT_SUPPORTED_NEXTHOP |
6-Information |
V6 nexthop not supported for afi/safi [dec]/[dec] |
The remote BGP peer sent in a route with an invalid optional transitive attribute. |
- |
"This information message appears as router detects malformed\n\ optional attributes in BGP updates. However frequent occurrences\n\ of such event should be investigated." |
|
BGP-6-ROUTER_HOLDBACK_TIMER |
6-Information |
BGP Router timed out waiting on dependant events |
BGP Router timed out waiting on dependant events and will continue with its initializations. |
bgp |
LOG_STD_NO_ACTION |
|
BIND_FAIL-2-MPLS_TE_EXT_FWDG |
2-Critical |
ERRMSG_NOFLAGS |
- |
- |
- |
|
BINDLABEL-3-BINDLABEL_ERR |
3-Error |
Bind label error [chars] |
An error happen when create/lookup bind label. |
BINDLABEL_COMPONENT |
LOG_STD_ACTION |
|
BIPC-3-SESSION_INVALID |
3-Error |
Invalid Session Slot=[dec] Session=0x%08x |
An internal software error has occured. The IPC session was incorrectly not deleted when the slot went down. |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
BIPC-6-SESSION_DOWN |
6-Information |
IPCCL Session to [chars][dec] is DOWN |
An internal software debug info to notify IPCCL session to specific slot went down. |
DDTS_COMPONENT |
"No action is required." |
|
BIPC-6-SESSION_UP |
6-Information |
IPCCL Session to [chars][dec] is UP |
An internal software debug info to notify IPCCL session to specific slot went up. |
DDTS_COMPONENT |
"No action is required." |
|
BIT-4-OUTOFRANGE |
4-Warning |
bit [dec] is not in the expected range of [dec] to [dec] |
An invalid request was detected by the bitlist subsystem. |
cosmos |
LOG_STD_SH_TECH_ACTION |
|
BOOST_PERFORMANCE-2-CONFIG_REMOVED |
2-Critical |
Boost capability removed. Throughput will be defaulted on next reload. Reason: [chars] |
Device no longer support boost throughput level |
isr-smart-lic |
- |
|
BOOT_HOST_DHCP-3-ABORTING |
3-Error |
[chars] |
- |
- |
- |
|
BOOT_HOST_DHCP-4-WARNING |
4-Warning |
[chars] |
Configure a Device via DHCP feature has experienced an unexpected condition which did not cause a failure but suggests things did not go correctly. |
- |
LOG_STD_NO_ACTION |
|
BOOT_HOST_DHCP-6-INFO |
6-Information |
[chars] |
This is an informational message generated while configuring a device via the dhcp feature. |
- |
LOG_STD_NO_ACTION |
|
BOOT-3-MODECHANGE_FAIL |
3-Error |
[chars]. Requested by [chars] |
This log indicates that device-mode operation failure While device-mode change and there are errors seen and requested by specified client |
- |
LOG_STD_NO_ACTION |
|
BOOT-6-MODECHANGE |
6-Information |
[chars] |
This log indicates that device-mode operation is successful While mode change and there are no errors seen |
- |
LOG_STD_NO_ACTION |
|
BP_CRIMSON-3-INITFAIL |
3-Error |
Initialization of the IOS BP Crimson facility failed [chars]. |
- |
- |
- |
|
BPE-3-INVALID_IDB_TYPE |
3-Error |
Invalid IDB type passed [[dec] - [chars]] |
Idb type passed is not supported by this function |
- |
LOG_STD_ACTION |
|
BPE-3-INVALID_MAC |
3-Error |
Invalid MAC for slot [[dec]/[dec]/[dec]] |
Could not get proper MAC address for a given slot/subcard/port |
- |
LOG_STD_ACTION |
|
BPE-3-INVALID_PORT |
3-Error |
Port number[[dec]] is not valid |
Port number is invalid |
- |
LOG_STD_ACTION |
|
BPE-3-INVALID_SLOT |
3-Error |
Slot number[[dec]] is not valid |
Slot number is invalid |
- |
LOG_STD_ACTION |
|
BPE-3-MALLOC_FAILURE |
3-Error |
Malloc Failed [[chars]] |
Could not allocate memory |
- |
LOG_STD_ACTION |
|
BPE-3-NOT_REGISTERED |
3-Error |
Interface[[chars]] MAC is not registered |
Interface registration with BPE driver is missing |
- |
LOG_STD_ACTION |
|
BPE-3-NULL_IDB |
3-Error |
Null idb pointer [[chars]:[hec]] |
Interface pointer is not initialized |
- |
LOG_STD_ACTION |
|
BRI-1-INITFAIL |
1-Alert |
msgtxt_initfail |
The hardware failed to initialize correctly. |
- |
"Repair or replace the controller." |
|
BRI-1-NOMEMORY |
1-Alert |
msgtxt_nomemory |
The requested operation could not be accomplished because of a low\n\ memory condition. |
- |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
BRI-4-NOSWITCH |
4-Warning |
msgtxt_initfail |
ISDN leased line requires an ISDN switch type configure. |
- |
- |
|
BRI-4-OVERSIZE_B1_MTU |
4-Warning |
Failed to set MTU of [dec] on [chars]. Can't support MTU over [dec]. |
User config IP MTU size not supported by BRI hardware. |
- |
"Reconfigure IP MTU base on the suggested range." |
|
BRI-4-OVERSIZE_B2_MTU |
4-Warning |
Failed to set MTU of [dec] on [chars]. Can't support MTU over [dec]. |
User config IP MTU size not supported by BRI hardware. |
- |
"Reconfigure IP MTU base on the suggested range." |
|
BRI-4-OVERSIZE_D_MTU |
4-Warning |
Failed to set MTU of [dec] on [chars]. Can't support MTU over [dec]. |
User config IP MTU size not supported by BRI hardware. |
- |
"Reconfigure IP MTU base on the suggested range." |
|
BRIMUX-1-BADCODE |
1-Alert |
Software error: [chars] |
An internal software error occurred. |
as |
LOG_STD_ACTION |
|
BRIMUX-3-BADBRIMUX |
3-Error |
Slot [dec] [chars] |
A BRIMUX firmware problem may be present. |
as |
LOG_STD_ACTION |
|
BRIMUX-3-BADDLACK |
3-Error |
Slot [dec] BRIC failed to acknowledge download data block [dec] |
A BRIMUX firmware problem may be present. |
as |
LOG_STD_ACTION |
|
BRIMUX-3-BADDPM |
3-Error |
Slot [dec] DPM test failed at offset 0x[hec] expect 0x[hec] read 0x[hec] |
A BRIMUX board hardware problem may be present. |
as |
LOG_STD_ACTION |
|
BRIMUX-3-BADULADDR |
3-Error |
Slot [dec] BRIC wrong upload address received 0x[hec] requested 0x[hec] |
A BRIMUX firmware problem may be present. |
as |
LOG_STD_ACTION |
|
BRIMUX-3-BADULBLK |
3-Error |
Slot [dec] BRIC wrong block [dec] for data upload expect [dec] |
A BRIMUX firmware problem may be present. |
as |
LOG_STD_ACTION |
|
BRIMUX-3-BADULLEN |
3-Error |
Slot [dec] BRIC upload data length read [dec] truncate to [dec] bytes |
A BRIMUX firmware problem may be present. |
as |
LOG_STD_ACTION |
|
BRIMUX-3-BADULREQ |
3-Error |
Slot [dec] BRIC failed to send upload data block [dec] |
A BRIMUX firmware problem may be present. |
as |
LOG_STD_ACTION |
|
BRIMUX-4-HEARTBEAT |
4-Warning |
Slot [dec] BRIC lost heartbeat for [dec] seconds |
A BRIMUX board hardware or firmware problem may be present. |
as |
LOG_STD_RECUR_ACTION |
|
BRIMUX-5-CHANUPDOWN |
5-Notice |
B[dec] of BRI[dec] on slot [dec] BRIC changed state to [chars] |
A B-channel on the BRIMUX board changed state. |
as |
LOG_STD_NO_ACTION |
|
BRIMUX-5-PORTUPDOWN |
5-Notice |
BRI[dec] on slot [dec] BRIC changed state to [chars] |
A port on the BRIMUX board changed state. |
as |
LOG_STD_NO_ACTION |
|
BRIMUX-5-UPDOWN |
5-Notice |
Slot [dec] BRIC changed state to [chars] |
A BRIMUX board changed state. |
as |
LOG_STD_NO_ACTION |
|
BSC-2-NOMEM |
2-Critical |
No buffers available on interface [chars]. |
This message indicates that memory in the router was exhausted. |
- |
"Perform diagnostics on the router to locate the subsystem or interface\n\ responsible for consuming memory. The only method that will clear this\n\ situation is to reload the router." |
|
BSC-3-BADLINESTATE |
3-Error |
Line state Tx when receiving [chars] on line [chars] |
An unexpected receive occurred during a transmission. |
- |
"Verify that the line has been consistently defined in regards to the\n\ carrier. If a message report was sent hard-on stop and start the\n\ bisynchronous interface in question." |
|
BSC-3-BADPEERTYPE |
3-Error |
Peer [chars] is incorrect type |
This message occurs only when BSC local-ack is configured. It\n\ indicates the serial interfaces that are using the BSTUN tunnel are\n\ configured incorrectly that is both have been configured as a\n\ secondary. |
- |
"Reconfigure the serial interfaces correctly to be a primary and\n\ secondary pair." |
|
BSR-4-CRP_NOT_CONFIGURED |
4-Warning |
Bootstrap message received from [inet] on [chars] SDWAN running SPT-only mode but Candidate-RP not configured locally. |
In SDWAN spt-only networks it is expected that the cEdge is the candidate RP and elected RP if PIM BSR is running. |
- |
LOG_STD_ACTION |
|
BSR-5-CBSR_REMOVED |
5-Notice |
Candidate-BSR on interface [chars] has been removed |
This is performed because the interface card has been removed |
- |
LOG_STD_NO_ACTION |
|
BSR-5-CRP_REMOVED |
5-Notice |
Candidate-RP on interface [chars] has been removed |
This is performed because the interface card has been removed |
- |
LOG_STD_NO_ACTION |
|
BSR-6-NO_FORWARD_BSR |
6-Information |
Dropping No-Forward Bootstrap message from [chars] on [chars] |
This is performed because RFC 5059 No-Forward BSM is not supported. |
- |
LOG_STD_NO_ACTION |
|
BSTUN-2-NOBUF |
2-Critical |
Interface [chars] no buffer available to [chars] |
A memory shortage existed at the time that the configuration command\n\ was issued. This condition is rare and under normal conditions\n\ temporary. |
- |
"Reconfigure the BSTUN group. If memory shortages persist call your\n\ technical support representative for assistance." |
|
BSTUN-3-BADCONN |
3-Error |
CONN: bad connection [dec] peer: [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
BSTUN-3-BADLENOP |
3-Error |
[chars]: bad len or unknown op op [dec] len [dec] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
BSTUN-3-BADMAGIC |
3-Error |
[chars]: wrong magic mine [hec] theirs [hec] [dec] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
BSTUN-3-BADMAGICTCP |
3-Error |
[chars]: peer [chars] wrong magic mine [hec] theirs [hec] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
BSTUN-3-BADPASSIVEOPEN |
3-Error |
passive open from [inet][dec] -> [dec] failed |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
BSTUN-3-CONNILLSTATE |
3-Error |
CONN: Peer [chars] illegal state [dec] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
BSTUN-3-IFNOTSETUP |
3-Error |
Could not setup interface for protocol [chars] |
BSTUN was unable to start the interface for handling the specified protocol traffic. |
- |
"If this message appears while you are configuring BSTUN check for\n\ other system errors such as no available memory in the router or the interface\n\ shutting down. If no obvious problem can be detected record all the displayed\n\ values and any other BSTUN error messages and contact your technical support\n\ representative." |
|
BSTUN-3-NOGRPDEF |
3-Error |
No bstun group defined on interface [chars] |
An action was taken that requires the previous definition of a BSTUN\n\ group number. |
- |
"Make sure "encapsulation bstun" and the "bstun group" have been\n\ defined for the interface." |
|
BSTUN-3-NOPEER |
3-Error |
No peer configured to route frame with destination address [chars] bstun group [dec] |
A BSTUN route has not been configured for the frame with a destination address. |
- |
"If this message appears while you are debugging bstun it indicates that no\n\ specific bstun route has been configured for the frames being received with\n\ the device address listed in the packet debug trace. You may choose to configure\n\ a bstun route or ignore this message." |
|
BSTUN-3-SENDPUNT |
3-Error |
[chars]: sent [chars] to [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
BSTUN-3-UNKPROTOEV |
3-Error |
Unknown protocol event [dec] on interface [chars] |
An event passed to the BSTUN layer for processing could not\n\ be decoded. |
- |
"Perform a hard restart on the indicated interface." |
|
BSTUN-4-DUPROUTE |
4-Warning |
Cannot define duplicate route on the\n\same group |
This route command is defined on another interface belonging to the\n\same group. Cannot define duplicate route on the same group |
- |
"Consider defining a new group and moving this interface onto that\n\group" |
|
BSTUN-4-PEERSTATE |
4-Warning |
Peer [chars] wrong state [dec] [dec] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
BSTUN-4-SENDPUNTTCP |
4-Warning |
[chars]: sent [chars] to [[dec]][inet] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
BSTUN-6-CONNOPENFAIL |
6-Information |
CONN: peer [chars] open failed [chars] [[dec]] |
An attempt to connect to a remote TCP BSTUN peer failed. |
- |
"Verify that the remote peer is accessible from this router that it is\n\ running software capable of supporting BSTUN and that it is configured\n\ correctly." |
|
BSTUN-6-ERR |
6-Information |
[chars]: [chars]: [chars] op [hec] len [dec] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
BSTUN-6-OPENED |
6-Information |
[chars]: peer [chars] opened [previous state [chars]] |
- |
- |
LOG_STD_NO_ACTION |
|
BSTUN-6-OPENING |
6-Information |
CONN: opening peer [chars] [dec] |
- |
- |
LOG_STD_NO_ACTION |
|
BSTUN-6-PASSIVEOPEN |
6-Information |
passive open [inet][dec] -> [dec] |
- |
- |
LOG_STD_NO_ACTION |
|
BSTUN-6-PEERSHUTDOWN |
6-Information |
shutting down peer [chars] on [chars] |
A connection to a remote peer is being shut down. This is typically\n\ the result of user intervention in BSTUN reconfiguration or disabling.\n\ This is good expected behavior. |
- |
LOG_STD_NO_ACTION |
|
BSTUN-6-PROCEXIT |
6-Information |
Process terminating. Due to signal [dec]. Subcode [dec]. Address [hec]. |
The BSTUN background process is terminating. |
- |
"If this message appears while you are unconfiguring BSTUN no action\n\ is required. Otherwise record all the displayed values and any other\n\ BSTUN error messages and contact your technical support\n\ representative." |
|
BSTUN-6-RECONNECT |
6-Information |
PHDR: reconnect from peer [chars] |
A remote peer reestablished a connection to this router. |
- |
LOG_STD_NO_ACTION |
|
BSTUN-6-TCPFINI |
6-Information |
peer [chars] closed [previous state [chars]] |
A remote peer closed a BSTUN connection with this router. |
- |
"Examine the other router to see why it closed this connection with\n\ this peer. This can be caused by normal events such as\n\ reconfiguration." |
|
BSTUN-6-TCPPEERSHUT |
6-Information |
[chars] [chars] [inet][dec] |
This route closed a BSTUN connection with a remote peer. |
- |
"Examine this router to see why it closed this connection with this\n\ peer. This can be caused by normal events such as reconfiguration." |
|
BUFCAP-3-ACTIVE_CAPPOINT |
3-Error |
Invalid operation was attempted on an active capture point [chars]. |
Invalid operation was attempted on an active \n\ capture point. |
os |
"Search for resolved software issues using the Bug Toolkit " "at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance copy the error message exactly as " "it appears on the console or in the system log enter the " "<CmdBold>show monitor capture point all<NoCmdBold> and " "<CmdBold>show tech<NoCmdBold> commands and contact your " "Cisco technical support representative providing the " "representative with the gathered information." |
|
BUFCAP-3-EXPORT_BUFFER |
3-Error |
Error exporting buffer [chars] to location [chars] |
The Buffer Capture Infrastructure is not able to export the buffer to the specified location |
os |
"Please check if a valid destination was specified. " "Or if a file by the same name already exists rename the dump file or " "remove the existing file from the destination location. " "If those actions do not resolve the problem " LOG_STD_ACTION |
|
BUFCAP-3-INVALID_CAPPOINT |
3-Error |
Invalid capture point. |
Some operation was attempted on a invalid capture point. |
os |
LOG_STD_ACTION |
|
BUFCAP-3-INVALID_PARAM |
3-Error |
Invalid parameters |
Invalid parameters were passed in to a buffer capture infrastructure function. |
os |
LOG_STD_ACTION |
|
BUFCAP-3-NO_MEM |
3-Error |
Not enough memory available for Buffer Capture Infrastructure |
The buffer capture infrastructure could not get the memory it requested. |
os |
LOG_STD_REDUCE_ACTION |
|
BUFCAP-3-NOSUCHCAPTURE |
3-Error |
Error finding capture point. |
No such capture point exists |
os |
LOG_STD_ACTION |
|
BUFCAP-5-BUFFER_FULL |
5-Notice |
Linear Buffer associated with capture buffer [chars] is full. |
The linear buffer is full. Further capture would be halted. |
os |
LOG_STD_NO_ACTION |
|
BUFCAP-5-MAX_ELEMS |
5-Notice |
Capture point [chars] disabled. The number of elements in associated capture buffer's [chars] |
The buffer contains the maximum configured number of packets. The associated capture point will be disabled. |
os |
LOG_STD_NO_ACTION |
|
BUFCAP-5-TIME_EXCEEDED |
5-Notice |
Capture Point [chars] disabled. The associated capture buffer's [chars] |
The linear buffer does not have enough space left. Hence the packet was trimmed. This is the final element in the buffer. |
os |
LOG_STD_NO_ACTION |
|
BUFCAP-6-CAPPOINT_EXISTS |
6-Information |
Capture Point [chars] already exists. |
A Capture point by the specified name already exists. |
os |
LOG_STD_NO_ACTION |
|
BUFCAP-6-CREATE |
6-Information |
Capture Point [chars] created. |
Specified capture point has been created. |
os |
LOG_STD_NO_ACTION |
|
BUFCAP-6-DELETE |
6-Information |
Capture Point [chars] deleted. |
Specified capture point has been deleted. |
os |
LOG_STD_NO_ACTION |
|
BUFCAP-6-DISABLE |
6-Information |
Capture Point [chars] disabled. |
Specified capture point has been disabled. |
os |
LOG_STD_NO_ACTION |
|
BUFCAP-6-DISABLE_ASYNC |
6-Information |
Capture Point [chars] disabled. Reason : [chars] |
Specified capture point has been disabled due to asynchronous event. |
os |
LOG_STD_NO_ACTION |
|
BUFCAP-6-ENABLE |
6-Information |
Capture Point [chars] enabled. |
Specified capture point has been enabled. |
os |
LOG_STD_NO_ACTION |
|
BUFCAP-6-RATE_LIMIT |
6-Information |
[dec] packets from capture point [chars] dropped due to rate limiting. |
Rate limiting has been enabled and the number of packets exceed the allowed configured value. |
os |
- |
|
BUFCAP-6-TOO_BIG |
6-Information |
The packet to be dumped is bigger than the buffer size of capture buffer [chars]. Packet of size [dec] dropped. |
The packet is bigger than the configured/default buffer size. |
os |
"Change the parameters of the capture buffer. " "You can try to increase the size of the buffer " "or limit the number of bytes copied." |
|
BUNDLE_INSERT-2-MPLS_TE |
2-Critical |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
BUNDLES-3-ALLOCATION |
3-Error |
Bundle allocation error: [chars] |
An internal software error occurred. It is likely that this error is caused by a low memory condition |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
BUNDLES-3-PLATFORMSPACE |
3-Error |
Platform attempted to access unreserved space |
An internal software error occurred. |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
BUNDLES-3-TYPENOTISSUAWARE |
3-Error |
Bundle type [chars] must be ISSU aware to send to slots [chars] |
- |
- |
- |
|
BW_LICENSE-4-THROUGHPUT_MAX_LEVEL |
4-Warning |
Average throughput rate approached the licensed bandwidth of [chars] during [dec] sampling periods in the last 24 hours sampling period is [dec] seconds |
- |
- |
- |
|
BW_LICENSE-5-THROUGHPUT_THRESHOLD_LEVEL |
5-Notice |
Average throughput rate exceeded [dec] percent of licensed bandwidth of [chars] during [dec] sampling periods in the last 24 hours sampling period is [dec] seconds |
- |
- |
- |
|
C2950_MONITOR-3-C2950MONITOR_UNKNOWN_PARAM |
3-Error |
Unknown trap type:[dec] received in emt_call function. |
Unknow trap type. Some feature requires this trap type to be handled |
- |
- |
|
C3PL_TARGET-4- NOREG |
4-Warning |
No [chars] callback registered for [chars]. Using default function. |
A support function for a specific kind of QoS attachment point is not available. A default behavior was applied instead. |
C3PL_TARGET_DDTS_COMPONENT |
- |
|
C4K_IOSINTF-4-INTVLANALLOCFAIL |
4-Warning |
Failed to allocate internal VLAN for interface [chars]. The interface will remain down. |
When a routed port or port channel interface is enabled it must allocate an internal VLAN in order to operate. If there are no internal VLANs available when an interface is enabled the interface remains down and this message is logged. |
- |
"An internal VLAN can be freed up by disabling some other routed port " "or port channel interface or by deleting a user configured VLAN in " "the 1006 to 4094 range. Once a VLAN is made available the interface " "will come up if it is disabled and re-enabled." |
|
C4K_IOSINTF-4-REFLEXIVEACLNOTSUPPORTED |
4-Warning |
Reflexive Acls are not supported. Ignoring the [chars] entry. |
Reflexive Acls are not supported. Aces with Evaluate and Reflect keywords are ignored. |
- |
"Do not configure Aces with Evaluate or Reflect keyword. " |
|
C4K_IOSINTF-5-NOTXVLAN |
5-Notice |
Router Port [chars] has no internal vlan assigned to transmit packet |
The L3 Interface specified does not have an internal vlan assigned. |
- |
- |
|
C4K_IOSINTF-5-STALEPHYPORT |
5-Notice |
Dropping packets to be transmitted out on port [chars] Linecard in Slot [dec] may have been removed |
During hot-swapping operations sometimes a prevously queued packet may be transmitted after a delay by which time the linecard does not exist anymore. This indicates such packets are being dropped |
- |
"This occurs when there are queued packets that are transmitted by which " "time the linecard in that slot has been removed already. If the problem " "persists even without any hotswapping operations please contact your " "Cisco Technical Support representative " |
|
C4K_IOSINTF-5-TXL3PKTONPHYPORT |
5-Notice |
Transmitting L3 packet on a physical port [chars] that is part of [chars] [dec] packets. Make sure the physical port in the L3 port |
The L3 protocols operate at the logical port level and not on physical port level. This message indicates an situation that causes L3 protocol packets to be sent on a physical port that is part of a bundle. This can happen if there is a misconfiguration. Maybe there is an ip address assigned to a physical port that is part of a layer 3 port channel |
- |
LOG_STD_ACTION |
|
C4K_IOSINTF-5-TXPKTDROPONETHERCHANNEL |
5-Notice |
Dropping transmit packet out of interface [chars] |
A packet to be transmitted out of a Port-Channel is being dropped during transitions in the Port-Channel membership |
- |
"This occurs when a packet is being transmitted out of the aggregate " "port by higher layer protocols but the software cannot find specific " "state information. This can temporarily happen when physical ports " "transition into or out of the channel. If the problem persists please " "contact your Cisco Technical Support representative" |
|
C4K_IOSSYS-7-INVALIDVALUE |
7-Debug |
[chars] Type [dec] not handled returning a default of 0 |
This message is for debugging purposes. When you see this message report it to your technical support representative. |
cat4000 |
LOG_STD_ACTION |
|
C4K_REDUNDANCY-2- IOS_VERSION_CHECK_FAIL |
2-Critical |
[chars] |
For proper operation of redundancy the system must be configured with symmetrical hardware and software. Here we have detected an IOS version mismatch between the Active and Standby. In this condition redundancy operations are not guaranteed. |
- |
"Configure the system so that the Active and Standby supervisors are running the same version of IOS." |
|
C4K_REDUNDANCY-2- NON_SYMMETRICAL_REDUNDANT_SYSTEM |
2-Critical |
[chars] |
For proper operation of redundancy the system must be configured with symmetrical hardware. Here we have detected mismatch between the Active and Standby hardware. In this condition redundancy operations are not guaranteed. |
- |
"Configure the hardware so that the Active and Standby supervisors are identical in all respects." |
|
C4K_REDUNDANCY-2- POSTFAIL |
2-Critical |
POST failure on [chars] supervisor detected |
Active supervisor failed POST. Standby supervisor will reset current active and attempt to become active. |
- |
"Please run offline diagnostics on the failed supervisor to isolate the failure" |
|
C4K_REDUNDANCY-4- CONFIGSYNCFAIL |
4-Warning |
Persistent-config Sync to Standby supervisor failed. |
Active supervisor failed to receive PLATFORM_SYNC_DONE message from Standby. Potential problem with Standby. |
- |
"" |
|
C4K_REDUNDANCY-5- CONFIGSYNC |
5-Notice |
The [chars] has been successfully synchronized to the standby supervisor |
The configuration has been successfully synchronized to the standby supervisor |
- |
"This is an informational message. No action is required." |
|
C4K_REDUNDANCY-5- CONFIGSYNC_RATELIMIT |
5-Notice |
The [chars] has been successfully synchronized to the standby supervisor |
The configuration has been successfully synchronized to the standby supervisor This is a rate limited message. These messages are logged at 1 min interval when lots of messages are generated continuously |
- |
"This is an informational message. No action is required." |
|
C4K_REDUNDANCY-6- ACTIVESUPNOTFOUND |
6-Information |
Active supervisor not found. |
Informational message on standby supervisor when it fails to communicate with active supervisor |
- |
"" |
|
C4K_REDUNDANCY-6- ATTEMPTINGTOBECOMEACTIVE |
6-Information |
Attempting to become active supervisor. |
Informational message on standby supervisor when it fails to communicate with active supervisor and attempts to takeover as active supervisor |
- |
"" |
|
C4K_REDUNDANCY-6-INIT |
6-Information |
Initializing as [chars] supervisor |
Informational message regarding the state of the supervisor |
- |
"" |
|
C4K_REDUNDANCY-6-MODE |
6-Information |
[chars] supervisor initializing for [chars] mode |
Informational message regarding the redundancy mode of the supervisor |
- |
"" |
|
C4K_REDUNDANCY-6- SWITCHOVER |
6-Information |
Switchover activity detected changing role from STANDBY to ACTIVE |
Informational message on standby supervisor when it detects switchover activity |
- |
"" |
|
C5RSP-3-C5_BADIPC |
3-Error |
bad message received from the NMP |
An unsolicited in band IPC message was received by the router from the NMP. |
- |
LOG_STD_NO_ACTION |
|
C5RSP-3-C5_MACADRFAIL |
3-Error |
can't get C5 Line Card Mac Addr |
An attempt by the RSP to query the C5IP for Vlan 0 IP address failed. |
- |
"Try these actions to remedy the problem: Reset the router from the NMP's console. If problems persist please RMA the router and or Catalyst 5000" |
|
C5RSP-3-C5_NMPMACADRFAIL |
3-Error |
can't get NMP Mac Addr |
An attempt by the RSP to query the C5IP for Vlan 0 MAC address failed. |
- |
"Try these actions to remedy the problem: Reset the router from the NMP's console. If problems persist please contact Cisco for replacement" |
|
C5RSP-3-C5_SAGE0FAIL |
3-Error |
Length error occurred on dma channel 0 |
A hardware error has occurred on dma channel 0 |
- |
"Report this error to your technical support representative." |
|
C5RSP-3-C5_SAGE1FAIL |
3-Error |
Length error occurred on dma channel 1 |
A hardware error has occurred on dma channel 1 |
- |
"Report this error to your technical support representative." |
|
C5RSP-3-C5IP_SLOTFAIL |
3-Error |
can't get Catalyst 5000 Slot number of router |
An attempt by the RSP to query the C5IP for theslot it is plugged into has failed. |
- |
"Try these actions to remedy the problem: Reset the router from the NMP's console. If problem persists please contact Cisco for replacement." |
|
C5RSP-3-CANT_CREATE_VLAN |
3-Error |
vlan [dec] can not be created. media not supported |
An attempt to create a vlan of a media that is not supported has failed |
- |
"Try these actions to remedy the problem: Configure the vlan with a different media type." |
|
C5RSP-3-INVALID_LOVE_LETTER |
3-Error |
Invalid loveletter type [dec] sent by c5ip\n |
IOS is receiving bogus messages from the C5IP. |
- |
LOG_STD_RECUR_ACTION |
|
C5RSP-3-MAXVLAN_EXCEEDED |
3-Error |
can't configure more than 256 VLANS |
The Vlan Router product can configure a maximum of 256 vlans. |
- |
"Try these actions to remedy the problem: Delete unused vlans before configure new ones." |
|
C5RSP-3-NMP_DELETE_VLAN |
3-Error |
having problems deleting vlan [dec] on the NMP |
In band IPC message to the NMP from the router to delete a vlan has failed. |
- |
"Try these actions to remedy the problem: Check the state of Vlan 0. Check the state of the C5IP via the front panel LED. Check the state of the NMP. Reset the router" |
|
C5RSP-3-NMP_INIT_FAIL |
3-Error |
can't talk to NMP during initialization |
In band IPC router initialization message to the NMP has failed |
- |
"Try these actions to remedy the problem: Check the state of Vlan 0. Check the state of the C5IP via the front panel LED. Check the state of the NMP. Reset the router" |
|
C5RSP-3-NMP_PROG_FAIL |
3-Error |
NMP won't allow vlan [dec] configuration |
In band IPC message to the NMP from the router to create a vlan has failed. |
- |
"Try these actions to remedy the problem: Check the state of Vlan 0. Check the state of the C5IP via the front panel LED. Check the state of the NMP. Reset the router" |
|
C5RSP-3-RSM_NMP_BRIDGE_INVALID |
3-Error |
NMP returned invalid bridge id [dec] for [dec]\n |
NMP returned invalid bridge id to the RSM |
- |
"Make sure that the tr-brf vlan on the RSM is configured on the NMP" |
|
C5RSP-3-RSM_NMP_CONFIG_MISMATCH |
3-Error |
RSM NMP mismatch in config for [dec] RSM [dec] NMP [dec]\n |
There is mismatch in config for this vlan on NMP and RSM |
- |
"Make sure that the params for this vlan are the same on NMP and on the RSM" |
|
C5RSP-3-UNKNOWN_NMP_PROG |
3-Error |
unknown timer for NMP programming |
An unknown timer event has expired. |
- |
LOG_STD_NO_ACTION |
|
C5RSP-6-BRIDGE_AFU |
6-Information |
vlan [dec] could/could not be configured for bridging |
A Vlan could not be reset with the proper bridging information. |
- |
"Try these actions to remedy the problem: Configure the vlan with or with bridging." |
|
C5RSP-6-NOSWIDB |
6-Information |
vlan [dec] missing IDB |
Internal data structure of the Vlan is missing. |
- |
LOG_STD_ACTION |
|
C5RSP-6-VLAN_INFO_MISSING |
6-Information |
vlan [dec] info errant. something very wrong |
Internal information about the Vlan is missing. |
- |
LOG_STD_ACTION |
|
CABLE_CLC-3-CONFIG_MISMATCH |
3-Error |
Card type mismatch. config: [chars] is not consistent with the working mode in slot [dec] |
There are several scenarios that the error message will be reported. Some cases can be recovered by CLC auto reloading. Eg. Kobal-R can work as 10GE or 100GE ifmod for DPIC-G2. If system reload with card pre-configured as DPIC-G2-10GE 'card <slot_num>/0 CBR-CCAP-LC-G2-R r-phy DPIC-G2-10GE' while .board.conf was saved as DPIC-G2 100GE mode and Kobal boot up before card precfg parsing. Some cases need to shut down the lc first then change the configuration or change the pic card Eg. if the card is pre-configured as RPHY with the command 'card <slot_num>/0 cBR-CCAP-LC-40G r-phy' but a rf-pic card was inserted to the same slot. Or the card is pre-configured as ICMTS with the command 'card <slot_num>/0 cBR-CCAP-LC-40G' but a dpic card was inserted to the same slot. Or DPIC type is pre-configured as DPIC-G2 with the command 'card <slot_num>/0 CBR-CCAP-LC-G2-R r-phy DPIC-G2-10GE' but a DPIC-G1 card was inserted to the same slot. Or DPIC type is pre-configured as DPIC-G1 with the command 'card <slot_num>/0 CBR-CCAP-LC-G2-R r-phy' but a DPIC-G2 card was inserted to the same slot. |
cmts-platform-infra |
LOG_STD_ACTION |
|
CABLE_CLC-3-UNSUPPORTED_DATA |
3-Error |
Data conversion error [chars] 0x%X |
An internal software error has occured when converting the data specified in the message from one representation to another. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
CABLE_CLC-4-LCLOG_PARSE_ERR |
4-Warning |
Error parsing logger message: [chars] from subslot [dec]/[dec] |
The carrier card passed down a logger message that could not be parsed. |
cmts-platform-infra |
LOG_STD_ACTION |
|
CABLE_CLC-4-LCLOG_TOOLONG |
4-Warning |
Message too long from slot [dec]/[dec]: [dec] bytes |
The carrier card passed down a logger message that is too long for\n\ the RP to handle. |
cmts-platform-infra |
LOG_STD_ACTION |
|
CABLE_CLC-4-LOGGERMSGTOOBIG |
4-Warning |
Logger message length [dec] bytes exceeds the maximum allowed size |
The carrier card attempted to send a large message to the Route Processor |
cmts-platform-infra |
LOG_STD_ACTION |
|
CABLE_CLC-5-LOGGER_LC_REMOVED |
5-Notice |
Carrier Card [dec] removed |
The carrier card was removed |
cmts-platform-infra |
LOG_STD_NO_ACTION |
|
CABLE_UTIL-4-DC_INVOKE_ERR |
4-Warning |
Dynamic Command [chars] invoke failure |
There are several scenarios that the error message will be reported. One case is line card boot up mode for different PIC type does not match to pre-configured PIC type. There two modes of the line card : ICMTS&RPHY and Kobal-R can work with DPIC-G1 or DPIC-G2 with different FW. Eg. if the card is pre-configured as RPHY with the command 'card <slot_num>/0 cBR-CCAP-LC-40G r-phy' but a rf-pic card was inserted to the same slot. Or the card is pre-configured as ICMTS with the command 'card <slot_num>/0 cBR-CCAP-LC-40G' but a dpic card was inserted to the same slot. Or DPIC type is pre-configured as DPIC-G2 with the command 'card <slot_num>/0 CBR-CCAP-LC-G2-R r-phy DPIC-G2-<ifmod>' but a DPIC-G1 card was inserted to the same slot. Or DPIC type is pre-configured as DPIC-G1 with the command 'card <slot_num>/0 CBR-CCAP-LC-G2-R r-phy' but a DPIC-G2 card was inserted to the same slot. Another case is Kobal-R working ifmod mismatch to precfg. Eg. if system reload with card pre-configured as DPIC-G2-10GE 'card <slot_num>/0 CBR-CCAP-LC-G2-R r-phy DPIC-G2-10GE' while .board.conf was saved as DPIC-G2 100GE mode and Kobal boot up before card precfg parsing then this error message will be reported however it can be recovered by CLC auto reloading. |
DDTS_COMPONENT |
"change the pre-config to another mode" "or replace the pic card" |
|
CAC-3-MODIFY_FAIL |
3-Error |
CAC is enabled and per-flow rate modification results in CAC inconsistency. Remove and reapply CAC action in the class. |
This is an issue in CAC. Probable cause: CAC state update fails. Check internal data bases. |
qos |
LOG_STD_ACTION |
|
CAC-3-QOS_MODIFY_FAIL |
3-Error |
CAC is already functioning and configuration modification results in CAC inconsistency. Remove and reapply CAC action in the class. |
This is an issue in CAC. Probable cause: CAC state update fails. Check internal data bases. |
qos |
LOG_STD_ACTION |
|
CAC-6-MODIFY |
6-Information |
CAC is already functioning and configuration of per flow [dec] kbps will restart CAC invalidating CAC status for all flows. |
This is a user modification. Active CAC flows will all unadmitted till reneg. After reneg flow admit/un-admit status may vary. |
qos |
LOG_STD_ACTION |
|
CAC-6-QOS_MODIFY |
6-Information |
CAC is already functioning and a configuration modification will restart CAC invalidating current status for all flows. |
This is a user modification. Active CAC flows will all unadmitted till reneg. After reneg flow admit/un-admit status may vary. |
qos |
LOG_STD_ACTION |
|
CALL_CONTROL-3-CCAPI_DB_ERR |
3-Error |
ccapi database error |
Internal CCAPI conference or call record database error. This message represents an internal software fault and may manifest itself as dropped or hung calls. |
voice-callcontrol |
"Contact your technical support representative include the full text of\n\ the error message." |
|
CALL_CONTROL-3-INVALID_PARAMETER |
3-Error |
An invalid parameter is passed to the function |
This is due to coding error. |
voice-callcontrol |
"No action is required for the users" |
|
CALL_CONTROL-3-NORAWMSG |
3-Error |
no free raw msg structure available from [chars] for signaling message |
There were no rawmsg structures remaining in the system pools to alert the\n\ router of a voice or signaling event. |
voice-callcontrol |
"Check that the voice port for which the event was reported is\n\ still operational. If not clear the voice port." |
|
CALL_CONTROL-3-STAT_MEMORY_CORRUPTED |
3-Error |
Memory corruption detected in memory=[hec] allocated for RTCP statistic |
This is due to coding error |
voice-callcontrol |
"No action is required for the users" |
|
CALL_CONTROL-6-APP_NOT_EXIST |
6-Information |
The requested application does not exist any more. The event for the callid [dec] is being discarded.\n |
The event points to a session application which does not exist any more. The event is being discarded. |
voice-callcontrol |
"No action is required for the users" |
|
CALL_CONTROL-6-APP_NOT_FOUND |
6-Information |
Application [chars] in dial-peer [dec] not found. Handing callid [dec] to the alternate app [chars].\n |
The inbound dial-peer points to an unavailable application. The call is being handed to the alternate application or is rejected. |
voice-callcontrol |
"Reconfigure the dial-peer to have a valid application name or verify " "the application is accesible at its location." |
|
CALL_CONTROL-6-CALL_LOOP |
6-Information |
The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.\n |
The incoming call has a global identifier already present in the list of currently handled calls. It means that the voice gateway has detected a loop in the call route. |
voice-callcontrol |
"Please check your configuration." |
|
CALL_CONTROL-6-MAX_CONNECTIONS |
6-Information |
Maximum number of connections reached for dial-peer [dec]\n |
The dial-peer in question has reached its maximum connections configurations. No more calls will be taken on this dial-peer. |
voice-callcontrol |
"No action is required however to increase the number of connections " "allowed to this dial peer see 'maximum connections' configuration under " "the dial-peer configuration mode." |
|
CALL_CONTROL-6-NUMBERING_TYPE_NO_MATCH |
6-Information |
The called number numbering type did not match The event for the callid [dec] is being discarded.\n |
The event points to a session application which does not exist any more. The event is being discarded. |
voice-callcontrol |
"No action is required for the users" |
|
CALL_CONTROL-6-UNKNOWN_EXT_AGENT_RESET_ATTEMPT |
6-Information |
Request to reset an uknown external agent ID [dec] attempted. |
A request to reset an external agent eg H323 Gatekeeper or MGCP CA etc |
voice-callcontrol |
LOG_STD_ACTION |
|
CALL_HOME-3-CALL_HOME_FAILED_TO_ENABLE |
3-Error |
Failed to enable call-home from Smart Agent for Licensing: [chars] |
Failed to enable call-home from Smart Agent for Licensing. Call-home and Smart Licensing could not work properly. |
call-home |
"Please enable call-home manually according to the error string." |
|
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-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 specified profile." |
|
CALL_HOME-3-DS_DIR_CREATE_FAIL |
3-Error |
Failed to create diagnostic-signature directory [chars] fail reason: [chars]. |
The diagnostic-signature directory creation failed. |
call-home |
"Please check the disk/flash status first and then create the " "diagnostic-signature directory by yourself." |
|
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-3-FAIL_TO_RETRIEVE_SCH_STATUS |
3-Error |
Fail to retrieve device registration result. Please check SCH registration status with \call-home request registration-info\ under EXEC mode. |
Fail to retrieve device registration result. Call-home will abort polling progress. |
call-home |
"Please check SCH registration status with \"call-home request " "registration-info\" under EXEC mode." |
|
CALL_HOME-3-HTTP_REQUEST_FAILED |
3-Error |
Failure to send HTTP request to: [chars] 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-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-3-REQUEST_MESSAGE_FAILED |
3-Error |
call-home request message failed to send ERR [dec] [chars] |
- |
- |
- |
|
CALL_HOME-3-SMTP_SEND_FAILED |
3-Error |
Unable to send notification using all SMTP servers ERR [dec] [chars] |
- |
- |
- |
|
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-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-5-DS_ACTION_MSG |
5-Notice |
Notification message from diagnostic-signature file [chars]: [chars] |
Notification message from call-home diagnostic-signature because the message action defined in it was performed. |
call-home |
"No action is required." |
|
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-5-SL_MESSAGE_FAILED |
5-Notice |
Fail to send out Smart Licensing message to: [chars] ERR [dec] : [chars] |
- |
- |
- |
|
CALL_HOME-6-CALL_HOME_ENABLED |
6-Information |
Call-home is enabled by Smart Agent for Licensing. |
Call-home is enabled by Smart Agent for Licensing. |
call-home |
"No action is required." |
|
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-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_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-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-6-SCH_REGISTRATION_IN_PROGRESS |
6-Information |
Device registration with Smart Call HomeSCH is in progress. |
SCH device registration is in progress after a Smart licensing registration message was received. Call-home will poll SCH server for the registration result. |
call-home |
"No action is required." |
|
CALL_HOME-6-UPDATE_SCH_REGISTRATION_STATUS |
6-Information |
Device SCH registration result: [chars]. The result has no impact on Smart Licensing registration. You can check Smart Licensing registration status by executing command \show license summary\. |
Call-home retrieved and printed out the registration result from SCH server. |
call-home |
"No action is required." |
|
CALL_MGMT-1-CALL_LIST |
1-Alert |
[chars] |
The specific message text is supplied by the Call Management\n\ software. This indicates that internal data was corrupted\n\ due to a software error |
- |
LOG_STD_SH_TECH_ACTION |
|
CALL_MGMT-1-CPM_Q_POOL |
1-Alert |
[chars] |
The specific message text is supplied by the Call Management\n\ software. This indicates a memory exhaustion condition. |
- |
LOG_STD_REDUCE_ACTION |
|
CALL_MGMT-1-INITSYS |
1-Alert |
[chars] |
The specific message text is supplied by the Call Management\n\ software. This indicates an initialization failure. When this\n\ occurs the Call Management subsystem is not operational. |
- |
LOG_STD_ACTION |
|
CALL_MGMT-4-CALL_DISC |
4-Warning |
[chars] |
The specific message text is supplied by the Call Management\n\ software. This indicates that a call record is missing from\n\ active call list |
- |
LOG_STD_ACTION |
|
CALLPROG-3-API_INIT |
3-Error |
api front init failed for [chars] |
Failed to get free element from front end queue. |
Call Progress Notification |
"Platform requires additional free elements to properly function.\n\ Stop using Call Progress Notification applications.\n\ Call TAC to report the problem" |
|
CALLRECORD-3-MCOM_TERSE_CALL_FAILED_REC |
3-Error |
[chars] |
Terse Mcom Call Failed Record |
modem-management |
LOG_STD_NO_ACTION |
|
CALLRECORD-3-MCOM_TERSE_CALL_REC |
3-Error |
[chars] |
Terse Mcom Call Record |
modem-management |
LOG_STD_NO_ACTION |
|
CALLRECORD-3-MICA_TERSE_CALL_FAILED_REC |
3-Error |
[chars] |
Terse Mica Call Failed Record |
modem-management |
LOG_STD_NO_ACTION |
|
CALLRECORD-3-MICA_TERSE_CALL_REC |
3-Error |
[chars] |
Terse Mica Call Record |
modem-management |
LOG_STD_NO_ACTION |
|
CALLRECORD-3-MODEM_CALL_REC_ERROR |
3-Error |
[chars] |
Record Generated Exceeded Syslog Capability |
modem-management |
LOG_STD_NO_ACTION |
|
CALLRECORD-3-MODEM_CALL_REC_ERROR |
3-Error |
[chars] |
Record Generated Exceeded Syslog Capability |
modem-management |
LOG_STD_NO_ACTION |
|
CALLRECORD-6-MICA_TERSE_CALL_FAILED_REC |
6-Information |
[chars] |
Terse Mica Call Failed Record |
modem-management |
LOG_STD_NO_ACTION |
|
CALLRECORD-6-MICA_TERSE_CALL_REC |
6-Information |
[chars] |
Terse Mica Call Record |
modem-management |
LOG_STD_NO_ACTION |
|
CALLTREAT_NOSIGNAL-3-HIGH_CPU_5SEC_LOAD |
3-Error |
System experiencing high cpu utilization.\n |
System does not have enough CPU resources available to allocate \n\ a new resource. |
call-treatment |
"Ensure that the call setup rate is within the supported capacity of\n\ this gateway. Enter the <CmdBold>show proc cpu<NoCmdBold>\n\ command to see which processes are consuming the most CPU\n\ capacity and if appropriate reduce other system activity to \n\ ease CPU demands. By default the system will reject calls \n\ if the five-second CPU utilization on the gateway exceeds 89%. \n\ The default value can be overridden by enabling call treatment \n\ and entering the <CmdBold>call threshold global cpu-5sec<NoCmdBold> \n\ command." |
|
CALLTREAT_NOSIGNAL-3-HIGH_CPU_AVERAGE_LOAD |
3-Error |
System experiencing high average cpu utilization.\n |
Based on the average CPU utilization over a 60-second interval or an\n\ interval configured through the <CmdBold>call threshold\n\ poll-interval<NoCmdBold> command the system does not have \n\ enough CPU resources available to accept a new call. |
call-treatment |
"Ensure that the call setup rate is within the supported capacity of\n\ this gateway. Check to see if the current call setup\n\ rate is supported on this gateway. Enter the <CmdBold>show proc\n\ cpu<NoCmdBold> command to see which processes are consuming the \n\ most CPU capacity and if appropriate reduce other system\n\ activity to ease CPU demands. By default the system will reject \n\ calls if the five-second CPU utilization on the gateway exceeds 98%.\n\ The default value can be overridden by enabling call treatment and\n\ entering the <CmdBold>call threshold global cpu-avg<NoCmdBold>\n\ command." |
|
CALLTREAT_NOSIGNAL-3-HIGH_CPU_ONE_MIN_LOAD |
3-Error |
System experiencing high cpu utilization over one minute interval.\n |
Based on the average CPU utilization over a 60 second interval \n\ the system does not have enough CPU resources available. |
call-treatment |
"Ensure that the call setup rate is within the supported capacity of\n\ this gateway. Enter the <CmdBold>show proc cpu<NoCmdBold>\n\ command to see which processes are consuming\n\ the most CPU capacity and if appropriate reduce other system\n\ activity to ease CPU demands. By default the system will reject \n\ resource allocation if the five-second CPU utilization on the gateway exceeds 98%. " |
|
CALLTREAT_NOSIGNAL-3-HIGH_IOMEM_USAGE |
3-Error |
System running low on I/O memory.\n |
The system does not have enough free I/O memory. |
call-treatment |
"Ensure that the gateway has the recommended amount of I/O memory\n\ for this Cisco IOS feature set and version. Enter the \n\ <CmdBold>show mem<NoCmdBold> and <CmdBold>show proc mem<NoCmdBold> \n\ commands to see which processes are consuming the\n\ most memory. Check to see if the memory usage is appropriate for these\n\ processes and if so reduce other system activity to ease CPU demands.\n\ The high and low thresholds for I/O memory utilization can be\n\ configured by enabling call treatment and entering the\n\ <CmdBold>call threshold global io-mem<NoCmdBold> command." |
|
CALLTREAT_NOSIGNAL-3-HIGH_MEMORY_USAGE |
3-Error |
System running low on memory. |
The system does not have enough free memory to allocated new resource. |
call-treatment |
"Ensure that the gateway has the recommended amount of memory for\n\ this Cisco IOS feature set and version. Enter the \n\ <CmdBold>show mem<NoCmdBold> and <CmdBold>show proc mem<NoCmdBold> \n\ commands to see which processes are consuming the\n\ most memory. Check to see if the memory usage is appropriate for these\n\ processes and if so reduce other system activity to ease CPU demands.\n\ By default the system will reject calls if there is less than 2% free\n\ processor memory on the gateway. This value can be overridden by \n\ enabling call treatment and entering the\n\ <CmdBold>call threshold global total-mem<NoCmdBold> command." |
|
CALLTREAT_NOSIGNAL-3-HIGH_PROCMEM_USAGE |
3-Error |
System running low on processor memory.\n |
The system does not have enough free processor memory. |
call-treatment |
"Ensure that the gateway has the recommended amount of processor memory\n\ for this Cisco IOS feature set and version. Enter the \n\ <CmdBold>show mem<NoCmdBold> and <CmdBold>show proc mem<NoCmdBold>\n\ commands to see which processes are consuming the\n\ most memory. Check to see if the memory usage is appropriate for these\n\ processes and if so reduce other system activity to ease CPU demands.\n\ The high and low thresholds for processor memory utilization can be\n\ configured by enabling call treatment and entering the\n\ <CmdBold>call threshold global proc-mem<NoCmdBold> command." |
|
CALLTREAT_NOSIGNAL-3-HIGH_TOTAL_CALLS |
3-Error |
High call volume.\n |
The system is experiencing a high call volume. |
call-treatment |
"Disable call threshold modify the call threshold global\n\ high and low values or investigate the cause of the high resource\n\ utilization. The high and low thresholds for total number of calls\n\ can be configured by enabling call treatment and entering the\n\ <CmdBold>call threshold global proc-mem<NoCmdBold> command." |
|
CALLTREAT-3-HIGH_CPU_5SEC_LOAD |
3-Error |
System experiencing high cpu utilization. Processing for callID[dec] is rejected.\n |
System does not have enough CPU resources available to accept\n\ a new call. The specified call was rejected. |
call-treatment |
"Ensure that the call setup rate is within the supported capacity of\n\ this gateway. Enter the <CmdBold>show proc cpu<NoCmdBold>\n\ command to see which processes are consuming the most CPU\n\ capacity and if appropriate reduce other system activity to \n\ ease CPU demands. By default the system will reject calls \n\ if the five-second CPU utilization on the gateway exceeds 89%. \n\ The default value can be overridden by enabling call treatment \n\ and entering the <CmdBold>call threshold global cpu-5sec<NoCmdBold> \n\ command." |
|
CALLTREAT-3-HIGH_CPU_AVERAGE_LOAD |
3-Error |
System experiencing high average cpu utilization. Processing for callID[dec] is rejected.\n |
Based on the average CPU utilization over a 60-second interval or an\n\ interval configured through the <CmdBold>call threshold\n\ poll-interval<NoCmdBold> command the system does not have \n\ enough CPU resources available to accept a new call. The specified \n\ call was rejected. |
call-treatment |
"Ensure that the call setup rate is within the supported capacity of\n\ this gateway. Check to see if the current call setup\n\ rate is supported on this gateway. Enter the <CmdBold>show proc\n\ cpu<NoCmdBold> command to see which processes are consuming the \n\ most CPU capacity and if appropriate reduce other system\n\ activity to ease CPU demands. By default the system will reject \n\ calls if the five-second CPU utilization on the gateway exceeds 98%.\n\ The default value can be overridden by enabling call treatment and\n\ entering the <CmdBold>call threshold global cpu-avg<NoCmdBold>\n\ command." |
|
CALLTREAT-3-HIGH_CPU_ONE_MIN_LOAD |
3-Error |
System experiencing high cpu utilization over one minute interval. Processing for callID[dec] is rejected.\n |
Based on the average CPU utilization over a 60 second interval \n\ the system does not have enough CPU resources available to accept\n\ a new call. The specified call was rejected. |
call-treatment |
"Ensure that the call setup rate is within the supported capacity of\n\ this gateway. Enter the <CmdBold>show proc cpu<NoCmdBold>\n\ command to see which processes are consuming\n\ the most CPU capacity and if appropriate reduce other system\n\ activity to ease CPU demands. By default the system will reject \n\ calls if the five-second CPU utilization on the gateway exceeds 98%. " |
|
CALLTREAT-3-HIGH_IOMEM_USAGE |
3-Error |
System running low on I/O memory. Processing for callID[dec] is rejected.\n |
The system does not have enough free I/O memory to accept a new call.\n\ The specified call was rejected. |
call-treatment |
"Ensure that the gateway has the recommended amount of I/O memory\n\ for this Cisco IOS feature set and version. Enter the \n\ <CmdBold>show mem<NoCmdBold> and <CmdBold>show proc mem<NoCmdBold> \n\ commands to see which processes are consuming the\n\ most memory. Check to see if the memory usage is appropriate for these\n\ processes and if so reduce other system activity to ease CPU demands.\n\ The high and low thresholds for I/O memory utilization can be\n\ configured by enabling call treatment and entering the\n\ <CmdBold>call threshold global io-mem<NoCmdBold> command." |
|
CALLTREAT-3-HIGH_MEMORY_USAGE |
3-Error |
System running low on memory. Processing for callID[dec] is rejected.\n |
The system does not have enough free memory to accept a new call. \n\ The specified call was rejected. |
call-treatment |
"Ensure that the gateway has the recommended amount of memory for\n\ this Cisco IOS feature set and version. Enter the \n\ <CmdBold>show mem<NoCmdBold> and <CmdBold>show proc mem<NoCmdBold> \n\ commands to see which processes are consuming the\n\ most memory. Check to see if the memory usage is appropriate for these\n\ processes and if so reduce other system activity to ease CPU demands.\n\ By default the system will reject calls if there is less than 2% free\n\ processor memory on the gateway. This value can be overridden by \n\ enabling call treatment and entering the\n\ <CmdBold>call threshold global total-mem<NoCmdBold> command." |
|
CALLTREAT-3-HIGH_PROCMEM_USAGE |
3-Error |
System running low on processor memory. Processing for callID[dec] is rejected.\n |
The system does not have enough free processor memory to accept a new\n\ call. The specified call was rejected. |
call-treatment |
"Ensure that the gateway has the recommended amount of processor memory\n\ for this Cisco IOS feature set and version. Enter the \n\ <CmdBold>show mem<NoCmdBold> and <CmdBold>show proc mem<NoCmdBold>\n\ commands to see which processes are consuming the\n\ most memory. Check to see if the memory usage is appropriate for these\n\ processes and if so reduce other system activity to ease CPU demands.\n\ The high and low thresholds for processor memory utilization can be\n\ configured by enabling call treatment and entering the\n\ <CmdBold>call threshold global proc-mem<NoCmdBold> command." |
|
CALLTREAT-3-HIGH_TOTAL_CALLS |
3-Error |
High call volume. Processing for callID[dec] is rejected.\n |
The system is experiencing a high call volume. There are not\n\ enough resources to accept a new call. The specified call was \n\ rejected. |
call-treatment |
"Disable call threshold modify the call threshold global\n\ high and low values or investigate the cause of the high resource\n\ utilization. The high and low thresholds for total number of calls\n\ can be configured by enabling call treatment and entering the\n\ <CmdBold>call threshold global proc-mem<NoCmdBold> command." |
|
CALLTRKR-3-CALL_REC_ERROR |
3-Error |
[chars] |
Record Generated Exceeded Syslog Capability |
CallTracker |
LOG_STD_NO_ACTION |
|
CALLTRKR-3-NO_MEM |
3-Error |
Memory allocation failed for CT [chars] [dec] bytes |
Calltracker couldn't allocate new record due to no free memory. |
CallTracker |
"Disable calltracker [no calltracker enable]. Run show memory to\n\ find out where is the memory been allocated." |
|
CALLTRKR-3-PRINT_BUFFER |
3-Error |
calltrkr cli print buffer [chars] |
calltrkr cli internal print buffer overflow. |
Calltracker |
"Stop to using calltrkr show commands call TAC to report the problem" |
|
CALLTRKR-3-PROC |
3-Error |
can't spawn [chars] |
Couldn't spawn calltracker process. |
CallTracker |
"Disable calltracker first [no calltracker enable] enable it again." |
|
CALLTRKR-6-CALL_RECORD |
6-Information |
[chars] |
Terse CallTracker Call Record |
CallTracker |
LOG_STD_NO_ACTION |
|
CALLTRKR-6-MODEM_CALL_REC |
6-Information |
[chars] |
Modem Verbose CallTracker Call Record |
CallTracker |
LOG_STD_NO_ACTION |
|
CALLTRKR-6-MODEM_INFO_CALL_REC |
6-Information |
[chars] |
Modem Information Verbose CallTracker Call Record |
CallTracker |
LOG_STD_NO_ACTION |
|
CALLTRKR-6-MODEM_LINE_CALL_REC |
6-Information |
[chars] |
Modem Line Verbose CallTracker Call Record |
CallTracker |
LOG_STD_NO_ACTION |
|
CALLTRKR-6-MODEM_NEG_CALL_REC |
6-Information |
[chars] |
Modem Negotiation Verbose CallTracker Call Record |
CallTracker |
LOG_STD_NO_ACTION |
|
CAPCHANGE_DYNAMIC-4-LDP |
4-Warning |
ERRMSG_NOFLAGS |
- |
- |
- |
|
CAPCHANGE-4-LDP |
4-Warning |
ERRMSG_NOFLAGS |
- |
- |
- |
|
CAPWAP_FRAG-2-UNENABLED |
2-Critical |
[chars] feature not enabled at interface [chars] packet cannot be processed |
Capwap Fragmentation feature as indicated not enabled by the control plane. This is a critical problem. |
qfp |
LOG_STD_ACTION |
|
CAPWAP_FRAG-3-CAPWAP_FRAG_DBG |
3-Error |
Capwap Fragmentation encountered an error: [chars] [chars] %lu [chars] %lu |
Capwap Fragmentation encountered a runtime error as indicated in the message with parameter data for debug |
qfp |
LOG_STD_ACTION |
|
CAPWAP_FRAG-3-CAPWAP_FRAG_ERR |
3-Error |
Capwap Fragmentation encountered an error: [chars] |
Capwap Fragmentation encountered a runtime error as indicated |
qfp |
LOG_STD_ACTION |
|
CAPWAP_FRAG-3-INIT_FAILED |
3-Error |
Initialization of the CAPWAP_FRAG feature in QFP failed |
Initialization of the CAPWAP_FRAG feature in the QFP failed. This indicates a software failure. |
qfp |
LOG_STD_ACTION |
|
CAPWAP_FRAG-3-INVALID_QFP_NO |
3-Error |
Invalid qfp device no.: [chars] |
Invalid qfp device no. |
qfp |
LOG_STD_ACTION |
|
CAPWAP_REASS_PROXY-3-PROXY_IPC_INIT_FAILED |
3-Error |
[dec] |
IPC handler initialization failed. |
cpp-ucode |
LOG_STD_ACTION |
|
CAPWAP_REASS_PROXY-3-PROXY_IPC_MEM_EXTEND_FAILED |
3-Error |
- |
Increasing of Capwap Reassembly memory pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
CAPWAP_REASS_PROXY-3-PROXY_IPC_MEM_INIT_FAILED |
3-Error |
- |
Initialization of Capwap Reassembly memory pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
CAPWAP_REASS_PROXY-4-PROXY_IPC_INVALID_MSG |
4-Warning |
[hec] |
Received an invalid IPC messages subtype. |
cpp-ucode |
LOG_STD_ACTION |
|
CAPWAP_REASS-2-UNENABLED |
2-Critical |
[chars] feature not enabled at interface [chars] packet cannot be processed |
Capwap Reassembly feature as indicated not enabled by the control plane. This is a critical problem. |
qfp |
LOG_STD_ACTION |
|
CAPWAP_REASS-3-ALLOC_FAILED |
3-Error |
Allocation of [chars] memory failed for CAPWAP_REASS feature in QFP |
Allocation of memory by the QFP CAPWAP_REASS feature microcode failed. The name of the memory chunk is specified in the message. This indicates a software failure |
qfp |
LOG_STD_ACTION |
|
CAPWAP_REASS-3-CAPWAP_REASS_DBG |
3-Error |
Capwap Reassembly encountered an error: [chars] [chars] %lu [chars] %lu |
Capwap Reassembly encountered a runtime error as indicated in the message with parameter data for debug |
qfp |
LOG_STD_ACTION |
|
CAPWAP_REASS-3-CAPWAP_REASS_ERR |
3-Error |
Capwap Reassembly encountered an error: [chars] |
Capwap Reassembly encountered a runtime error as indicated |
qfp |
LOG_STD_ACTION |
|
CAPWAP_REASS-3-INIT_FAILED |
3-Error |
Initialization of the CAPWAP_REASS feature in QFP failed |
Initialization of the CAPWAP_REASS feature in the QFP failed. This indicates a software failure. |
qfp |
LOG_STD_ACTION |
|
CAPWAP_REASS-3-INVALID_QFP_NO |
3-Error |
Invalid qfp device no.: [chars] |
Invalid qfp device no. |
qfp |
LOG_STD_ACTION |
|
CAPWAP_REASS-3-MEM_INIT_FAILED |
3-Error |
- |
Failure occurred initializing capwap reass memory pool. |
qfp |
LOG_STD_ACTION |
|
CAPWAP_REASS-3-MEM_REQ_FAILED |
3-Error |
- |
IPC Failure occurred when attempting to request more capwap reass pool memory. |
qfp |
LOG_STD_ACTION |
|
CARD_PROTECTION-3-BOTH_ACTIVE |
3-Error |
For Card protection group: [dec] both primary and backup are active |
DS1844 potentiometer initialization failed. It indicates a hardware failure |
gsr-oc3_12-pos-spa |
"Change the hardware or copy the error message exactly as it " "appears and report it to your technical support representative." |
|
CARD_PROTECTION-4-ACTIVE |
4-Warning |
Card protection group: [dec] is [chars] ACTIVE [chars] |
whether card protection group is ACTIVE |
- |
"None - normal situation" |
|
CARD_PROTECTION-4-CONFIG_ADD |
4-Warning |
[chars] [dec]/[dec] Member added to Card protection group [dec] |
New Member added to Card protection group |
- |
"None - normal situation" |
|
CARD_PROTECTION-4-CONFIG_GROUP |
4-Warning |
CARD_PROTECTION-Group [dec] is configured |
Card Protection group is configured |
- |
"None - normal situation" |
|
CARD_PROTECTION-4-CONFIG_VIRTUAL |
4-Warning |
Virtual IM [dec]/[dec] is created |
Virtual IM is created for Card protection group |
- |
"None - normal situation" |
|
CARD_PROTECTION-4-PROTECTION |
4-Warning |
Card protection group: [dec] [chars] [dec]/[dec] is [chars] [chars] |
Protection Switchover between members of group |
- |
"None - normal situation" |
|
CARD_STATE-3-CARD_UNSUPPORT |
3-Error |
Card in slot [dec] with type [chars] is not supported in version [dec].[dec] |
The linecard inserted does not supported in currently running software. |
cbr-platform-infra |
"Replace the unsupported card or upgrade to right " "software." |
|
CARD_STATE-3-TYPE_MISMATCH |
3-Error |
Mismatched card type [chars] in slot [dec]. Expected type [chars]. |
The linecard inserted does not match the currently provisioned card type. |
cbr-platform-infra |
"Replace wrong board type with currently provisioned " "board type or type 'no card' to allow new card " "type to be discovered." |
|
CARD_STATE-3-UNEXPECTED |
3-Error |
Unexpected error on slot [dec]: [chars] |
An unexpected error has occured while performing a linecard OIR action |
cbr-platform-infra |
LOG_STD_ACTION |
|
CARD_STATE-4-FORCE_RESET |
4-Warning |
Reset slot [dec] for reason: [chars] |
The SUP forced a linecard to reload for the reason. |
cmts-platform-infra |
LOG_STD_ACTION |
|
CARD_STATE-4-INCONSISTANT |
4-Warning |
Gemini version inconsistant: slot [dec] daughter board [dec] version [chars] slot [dec] daughter board [dec] version [chars] |
Different Gemini in chassis CBR only supports the same hardware version US modules. |
cmts-platform-infra |
"Replace the Gemini to let the version " "of the Gemini in two slots be the same." |
|
CARD_STATE-4-LEOBEN_MISMATCH |
4-Warning |
Leoben version mismatch: slot [dec] version [chars] slot [dec] version [chars] |
Different Leoben in chassis CBR only supports the same hardware version US modules. |
cbr-platform-infra |
"Replace the Leoben to let the version " "of the Leoben in two slots be the same." |
|
CARRIER-2-CT3_E1_MIX |
2-Critical |
Cannot mix E1 PRI and CT3 DFC in chassis\ do not power up invalid card in slot [dec]\n |
The user has put E1 PRI and CT3 DFC cards in the same chassis. |
- |
"Remove the extra E1 PRI or CT3 DFC card." |
|
CARRIER-2-T1_E1_MIX |
2-Critical |
Cannot mix T1 and E1 8PRI DFC cards in chassis\ do not power up invalid card in slot [dec]\n |
The user has put T1 and E1 8PRI DFC cards in the same chassis. |
- |
"Remove the extra T1 or E1 8PRI DFC card." |
|
CARRIER-2-THREE_NP108_NOT_PRESENT |
2-Critical |
3 NP108s were not found on Tetryl card [dec] detected. |
Tetryl requires 3 NP108s to be present |
tetryl |
LOG_STD_ACTION |
|
CARRIER-2-TOOMANY_8PRI |
2-Critical |
Too many 8PRI DFC cards do not power up invalid card in slot [dec]\n |
The user has put too many 8PRI DFC cards in the chassis. |
- |
"Remove the extra 8PRI DFC card." |
|
CARRIER-2-TOOMANY_CT3 |
2-Critical |
Too many CT3 DFC cards do not power up invalid card in slot [dec]\n |
The user has put too many CT3 DFC cards in the chassis. |
- |
"Remove the extra CT3 DFC card or 8PRI DFC card causing problem" |
|
CARRIER-2-TOOMANY_TRUNK |
2-Critical |
Too many trunk DFC cards do not power up invalid card in slot [dec]\n |
The user has put too many trunk DFC cards in the chassis. |
- |
"Remove the extra trunk DFC card." |
|
CARRIER-3-DFC_INIT_ALREADY |
3-Error |
DFC is already initialized - DFC [dec] |
DFC is already initialized no need to initialize again |
as |
LOG_STD_ACTION |
|
CARRIER-3-DFC_INIT_FAIL |
3-Error |
DFC initialization is failed - DFC [dec] |
DFC initialization is failed because of several reasons |
as |
LOG_STD_ACTION |
|
CARRIER-3-DFC_POWER_INT |
3-Error |
DFC Power Changed - DFC [dec] |
DFC Power is fluctuating |
as |
LOG_STD_ACTION |
|
CARRIER-3-INVALID_DFC |
3-Error |
Invalid DFC - DFC [dec] type [dec] |
DFC has invalid board id/type |
as |
LOG_STD_ACTION |
|
CARRIER-3-PLATFORM_DFC |
3-Error |
DFC Carrier Platform Init Failed - Slot [dec] |
DFC Carrier Platform Init Failed |
as |
LOG_STD_ACTION |
|
CARRIER-3-POWER_DFC |
3-Error |
DFC Power-On Failed - DFC [dec] |
DFC Power-On Failed |
as |
LOG_STD_ACTION |
|
CARRIER-3-RESET_DFC |
3-Error |
DFC Reset Failed - DFC [dec] |
During OIR Removal process DFC reset failed. |
as |
LOG_STD_ACTION |
|
CASA-2-NOMEM |
2-Critical |
Out of memory: [chars]\n |
CASA failed to allocate memory. |
casa |
LOG_STD_REDUCE_ACTION |
|
CASA-3-BADVER |
3-Error |
Incoming packet is CASA v[dec] this router is v[dec] |
A packet was received for the wrong version of CASA |
casa |
"Verify that all CASA devices are running the same version \n\of the protocol" |
|
CASA-4-BADMSG |
4-Warning |
Message parsing error: [chars] |
Failed to parse an incoming packet |
casa |
"If this message is occurring repeatedly enable 'debug ip casa error'\n\and record the output call your Cisco technical support representative\n\and provide the gathered information." |
|
CASA-4-PORTCHANGE |
4-Warning |
Wildcard overlap: [chars] |
A CASA wildcard received on one port has been overwritten \n\by a service manager sending to another port. This message may appear \n\once if you are migrating your service to a new forwarding-agent port\n\if it recurs it could indicate a configuration problem. |
casa |
LOG_STD_RECUR_ACTION |
|
CASA-4-SECURITY_FAIL |
4-Warning |
[chars] security information in CASA packet. |
Security check failed. |
casa |
"Make sure all CASA systems are configured with the same password." |
|
CASA-4-UNEXPECTED |
4-Warning |
Unexpected error: [chars] |
An unexpected error occurred while performing CASA operation |
casa |
LOG_STD_RECUR_ACTION |
|
CASA-4-WARNING |
4-Warning |
Unexpected condition: [chars] |
An unexpected condition was detected while performing CASA operation |
casa |
LOG_STD_RECUR_ACTION |
|
CBAC_C3PL-3-INIT |
3-Error |
Firewall data plane updates are disabled |
The firewall notification of objects to the data plane has failed to\n\ startup and as such data plane updates are disabled. |
inspect |
show registry brief |
|
CBAC_C3PL-4-OBJ_CREATE |
4-Warning |
Firewall [chars] object [chars] creation failed in the data plane error [dec] |
The notification of the creation of a firewall object e.g. a parameter\n\ map has failed to update the data plane and as such the application\n\ of the parameters contained within the object will not be applied to\n\ the data plane. It is also possible that the common classification\n\ may fail to locate and bind to the object rendering the configuration\n\ incomplete in terms of application. |
inspect |
show memory |
|
CBAC_C3PL-4-OBJ_DELETE |
4-Warning |
Firewall [chars] object [chars] deletion failed in the data plane error [dec] |
The notification of the deletion of a firewall object e.g. a parameter\n\ map has failed to update the data plane and as such the application\n\ of the parameters contained within the object may continue to be\n\ applied to the data plane. |
inspect |
show memory |
|
CBAC_C3PL-4-OBJ_MODIFY |
4-Warning |
Firewall [chars] object [chars] modification failed in the data plane error [dec] |
The notification of the modification of a firewall object e.g. a\n\ parameter map has failed to update the data plane and as such the\n\ application of the parameters contained within the object will not be\n\ applied to the data plane. |
inspect |
show memory |
|
CBERR-3-MPLS_TE_EXT_FWDG |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
CBR_LIC-3-APPLY_DS_FAILED |
3-Error |
Applying downstream license failed |
Unable to apply the downstream license |
cmts-application |
"Please copy traceback infomation and report to TAC" |
|
CBR_LIC-3-APPLY_LCHA_FAILED |
3-Error |
Enforcement failed |
Unable to enforce |
cmts-application |
"Please copy traceback infomation and report to TAC" |
|
CBR_LIC-3-APPLY_US_FAILED |
3-Error |
Applying upstream license failed |
Unable to apply the upstream license |
cmts-application |
"Please copy traceback infomation and report to TAC" |
|
CBR_LIC-3-APPLY_WAN_FAILED |
3-Error |
Applying upstream license failed |
Unable to apply the upstream license |
cmts-application |
"Please copy traceback infomation and report to TAC" |
|
CBR_LIC-3-CPB_OPEN_FAILED |
3-Error |
Failed to open CPB data file for reading and/or writing |
Unable to open CPB data file |
cmts-application |
"Please report to TAC" |
|
CBR_LIC-3-CPB_READ_FAILED |
3-Error |
Reading CPB data file failed |
Unable to read CPB data from file |
cmts-application |
"Please report to TAC" |
|
CBR_LIC-3-CPB_SEEK_FAILED |
3-Error |
Setting file position failed |
Unable to set file position for reading and/or writing |
cmts-application |
"Please report to TAC" |
|
CBR_LIC-3-CPB_WRITE_FAILED |
3-Error |
Writing CPB data file failed |
Unable to write CPB data to file |
cmts-application |
"Please report to TAC" |
|
CBR_LIC-3-CSB_FAIL |
3-Error |
[chars] Failed for [chars] |
An attempt to parse a license related CLI failed |
cmts-application |
"Check the linecard license details and call TAC" |
|
CBR_LIC-3-LIC_SA_MALLOC_FAILED |
3-Error |
[chars] |
Platform malloc for Smart License Agent failed |
cmts-application |
"Check the mem usage and report to TAC" |
|
CBR_LIC-3-LIC_SA_NULL_FUN_PTR |
3-Error |
[chars] |
Platform getting a null function pointer from Smart License Agent |
cmts-application |
"Report to TAC" |
|
CBR_LIC-3-LIC_SA_REGISTER_FAILED |
3-Error |
[chars] |
Smart License Agent registr failed |
cmts-application |
"Check call-home pki vrf config and the IdToken" |
|
CBR_LIC-3-NULL_LICENSE_ENTITLEMENT |
3-Error |
License entitlement DB is NULL! |
The DS license DB is NULL |
cmts-application |
"Please copy traceback infomation and report to TAC" |
|
CBR_LIC-3-NULL_LICENSE_INFO |
3-Error |
License DB is NULL! |
The license DB is NULL |
cmts-application |
"Please copy traceback infomation and report to TAC" |
|
CBR_LIC-4-CPB_LESS_RECORD |
4-Warning |
In [chars] [dec] UTC CPB samples loss is more than [dec][dec] hours |
CPB samples are less than expected. |
cmts-application |
"If it is not the first month apply CPB feature " "or maintenance window is no more than 5 hours. Please report to TAC" |
|
CBR_LIC-4-CPB_SN_MISMATCH |
4-Warning |
CPB data will be removed since they are from Chassis: [chars]. Local Chassis is: [chars]. |
CPB records were saved in other Chassis. |
cmts-application |
"This is informational message." |
|
CBR_LIC-5-CPB_EVENT_LOG |
5-Notice |
CPB event: [chars] |
Important event for CPB feature. |
cmts-application |
"This is informational message." |
|
CBR_LIC-6-CHAN_NOSHUTFAIL |
6-Information |
[chars] channel [dec] no shut is not allowed due to insufficient licenses |
Unable to no shut the channel due to insufficient licenses |
cmts-application |
"Procure more licenses report to TAC" |
|
CBR_LIC-6-CHANNEL_NO_SHUTDOWN |
6-Information |
[chars]:[dec] has been restored to no shut |
Restored previously shutdown channels to no shut state |
cmts-application |
"None" |
|
CBR_LIC-6-CHANNEL_SHUTDOWN |
6-Information |
[chars]:[dec] has been shutdown due to deactivated enforcement |
Channel shut due to enforcement |
cmts-application |
"Buy additional licenses. Please report to TAC" |
|
CBR_LIC-6-DS_LIC_ENFORCED |
6-Information |
enforce_en:[dec] [chars] is [dec] |
License contract violation! Enforced |
cmts-application |
"Buy consumed additional licenses and report to TAC" |
|
CBR_LIC-6-DS_LIC_RESTRICTED |
6-Information |
[chars] [chars]:[dec] [chars] |
License contract violation! License Restricted/Enforced |
cmts-application |
"Buy additional licenses and report to TAC" |
|
CBR_LIC-6-LCHA_CHANNEL_NO_SHUTDOWN |
6-Information |
[chars] has been restored to no shut |
Restored previously shutdown channels to no shut state |
cmts-application |
"None" |
|
CBR_LIC-6-LCHA_CHANNEL_SHUTDOWN |
6-Information |
[chars] |
Channel shut due to enforcement |
cmts-application |
"Buy additional licenses. Please report to TAC" |
|
CBR_LIC-6-LCHA_LIC_ENFORCED |
6-Information |
enforce_en:[dec] [chars] is [dec] |
License contract violation! Enforced |
cmts-application |
"Buy consumed additional licenses and report to TAC" |
|
CBR_LIC-6-LCHA_LIC_RESTRICTED |
6-Information |
[chars] [chars] |
License contract violation! License Restricted/Enforced |
cmts-application |
"Buy additional licenses and report to TAC" |
|
CBR_LIC-6-LIC_CAP_LIMIT_BELOW_CONSUMED |
6-Information |
[chars] |
Capped count cannot be set! Consumed count is higher |
cmts-application |
"Capped count cannot be set! " "Consumed count is higher" |
|
CBR_LIC-6-LIC_CAPPED_DURATION_EXPIRED |
6-Information |
Capped Enforcement duration expired. Deactivated Enforced |
Capped Enforcement duration expired after an Eval or Grace expired |
cmts-application |
"Restore communication with cisco and add " "entitlements if required" |
|
CBR_LIC-6-LIC_CAPPED_DURATION_TIMER_STARTED |
6-Information |
License [chars] period has expired. Capped enforcement is active. The router will be deactivated in 90 days |
Eval or Grace Period has expired. Capped enforced - Will be deactivated in 90 days |
cmts-application |
"Restore communication with cisco and add " "entitlements if out of compliance" |
|
CBR_LIC-6-LIC_CONFIG_LOCKED |
6-Information |
[chars] |
Configuration lock in effect! Please register the cBR and try |
cmts-application |
"Configuration lock in effect! " "Register the cBR and try" |
|
CBR_LIC-6-LIC_LIMIT_NOT_SUPPORT |
6-Information |
[chars] |
Don't support Capped Enforcement for this license tag |
cmts-application |
"License limits cannot be changed for this feature" |
|
CBR_LIC-6-LIC_LIMIT_SET_ALREADY |
6-Information |
[chars] |
To change license limits disable license limits first |
cmts-application |
"License limits cannot be changed " " without disbling license limits first" |
|
CBR_LIC-6-LIC_OOC_DURATION_EXPIRED |
6-Information |
OOC duration expired - Capped Enforced |
OOC duration has expired and hence capped enforced |
cmts-application |
"Add entitlements to stay in compliance" |
|
CBR_LIC-6-LIC_OOC_DURATION_TIMER_STARTED |
6-Information |
License OOC timer has started. All entitlements will be Capped Enforced in 270 days. Please add necessary entitlements |
OOC duration timer has started. All entitlements will be Capped Enforced in 270 days. |
cmts-application |
"Add necessary entitlements to stay in compliance" |
|
CBR_LIC-6-LIC_SA_DISABLED |
6-Information |
[chars] |
License contract is violated. The device is disabled |
cmts-application |
"Report to TAC and add sufficient licenses" |
|
CBR_LIC-6-LIC_SA_EVAL_EXPIRED |
6-Information |
[chars] |
Eval Period has expired. License agent moving to eval-expired state |
cmts-application |
"Restore communication with cisco and register " " the device" |
|
CBR_LIC-6-LIC_SA_GLOBAL_NOTIFICATION |
6-Information |
[chars] |
A global notification about an event change in the Smart License Agent was received |
cmts-application |
"None" |
|
CBR_LIC-6-LIC_SA_GRACE_EXPIRED |
6-Information |
[chars] |
Grace Period has expired. License agent moving to garce-expired state |
cmts-application |
"Restore communication with cisco" |
|
CBR_LIC-6-LIC_SA_IN_COMPLIANCE |
6-Information |
[chars] |
Smart License Agent enforcement mode changed to Incompliance |
cmts-application |
"None" |
|
CBR_LIC-6-LIC_SA_OUT_OF_COMPLIANCE |
6-Information |
[chars] |
Smart License Agent enforcement mode changed to out of compliance |
cmts-application |
"Report to TAC and add sufficient licenses" |
|
CBR_LIC-6-LIC_SA_OVERAGE |
6-Information |
[chars] |
Smart License Agent enforcement mode changed to overage |
cmts-application |
"Report to TAC and add sufficient licenses" |
|
CBR_LIC-6-LICENSE_ENFORCE |
6-Information |
Enforcement mode set to [chars] |
License Information has been applied |
cmts-application |
"No action required" |
|
CBR_LIC-6-OUT_OF_RANGE |
6-Information |
[chars] is out of range:[dec] |
License counters have reached boundary condition |
cmts-application |
"Please copy traceback infomation and report to TAC" |
|
CBR_LIC-6-US_CHANNEL_NO_SHUTDOWN |
6-Information |
[chars] has been restored to no shut |
Restored previously shutdown channels to no shut state |
cmts-application |
"None" |
|
CBR_LIC-6-US_CHANNEL_SHUTDOWN |
6-Information |
[chars] has been shutdown due to deactivated enforcement |
Channel shut due to enforcement |
cmts-application |
"Buy additional licenses. Please report to TAC" |
|
CBR_LIC-6-US_LIC_ENFORCED |
6-Information |
enforce_en:[dec] [chars] is [dec] |
License contract violation! Enforced |
cmts-application |
"Buy consumed additional licenses and report to TAC" |
|
CBR_LIC-6-US_LIC_RESTRICTED |
6-Information |
[chars] [chars] [chars] |
License contract violation! License Restricted/Enforced |
cmts-application |
"Buy additional licenses and report to TAC" |
|
CBR_LIC-6-WAN_CHANNEL_NO_SHUTDOWN |
6-Information |
[chars] has been restored to no shut |
Restored previously shutdown channels to no shut state |
cmts-application |
"None" |
|
CBR_LIC-6-WAN_CHANNEL_SHUTDOWN |
6-Information |
[chars] has been shutdown due to deactivated enforcement |
Channel shut due to enforcement |
cmts-application |
"Buy additional licenses. Please report to TAC" |
|
CBR_LIC-6-WAN_LIC_ENFORCED |
6-Information |
enforce_en:[dec] [chars] is [dec] |
License contract violation! Enforced |
cmts-application |
"Buy consumed additional licenses and report to TAC" |
|
CBR_LIC-6-WAN_LIC_RESTRICTED |
6-Information |
[chars] [chars] [chars] |
License contract violation! License Restricted/Enforced |
cmts-application |
"Buy additional licenses and report to TAC" |
|
CBR_MCAST-3-SF_RECOVER |
3-Error |
Sfid [dec] Recover failed on [chars]. |
An internal software error occurred. |
cbr-cmts-apps |
LOG_STD_SH_TECH_ACTION |
|
CBR_PLFM_HA-3-CHKPTADDCLIENT |
3-Error |
Check Point Client [dec] Add Failed - [dec] |
Failed to add checkpoint client |
ubr-sw |
LOG_STD_ACTION |
|
CBR_PLFM_HA-3-GET_DATA_PTR |
3-Error |
[chars]: checkpoint get data pointer error |
Checkpoint infra get message data pointer failed |
ubr-sw |
LOG_STD_ACTION |
|
CBR_PLFM_HA-3-REPL |
3-Error |
Failed to setup [chars] chasfs reason: [chars] |
Failed to create replication manager related chasfs entry which is used to trigger database sync |
ubr-sw |
LOG_STD_ACTION |
|
CBR_PLFM_HA-3-STATESYNC |
3-Error |
Redundancy state synchronization failure [dec]/[dec] - [chars] |
A failure occurred in trying to synchronize CBR platform information |
ubr-sw |
LOG_STD_ACTION |
|
CBR_PLFM_HA-3-STBY_FP_ERR |
3-Error |
Standby FP failed to reach sso-ready within tolerated wait time |
Standby FP failed to reach sso-ready within tolerated wait time |
ubr-sw |
LOG_STD_ACTION |
|
CBR_PLFM_HA-3-STBY_PLL_NOT_LOCK |
3-Error |
Standby PLL failed to lock active within tolerated wait time |
Standby PLL failed to lock active within tolerated wait time |
ubr-sw |
LOG_STD_ACTION |
|
CBR_PLFM_HA-6-STATE_CC |
6-Information |
Lincard [dec] will be reloaded - [chars] |
Lincard is not ready for sup-ha |
ubr-sw |
LOG_STD_NO_ACTION |
|
CBR_PTP-3-DISPATCH |
3-Error |
Unable to dispatch received TDL message from PTP daemon |
This is an Event from RPD |
cbr-ptp |
LOG_STD_NO_ACTION |
|
CBR_PTP-3-INITFAIL |
3-Error |
Failed to initalize required PTP resource: [chars] |
During the initialization of the resources required by PTP a failure occured. This has prevented PTP from being activated. |
cbr-ptp |
LOG_STD_ACTION |
|
CBR_PTP-3-NITFAIL |
3-Error |
Failed to initalize required PTP resource: [chars] |
During the initialization of the resources required by PTP a failure occured. This has prevented PTP from being activated. |
cbr-ptp |
LOG_STD_ACTION |
|
CBR_PTP-5-TOD_CHG |
5-Notice |
The TOD source changed: [chars] |
The source of time of day changed: 1. from GPS of SUP-PIC 0/1 2. from DTI of SUP-PIC 0/1 3. free run mode |
cbr-ptp |
LOG_STD_NO_ACTION |
|
CBR_SPA-0-DPIC_EMERG |
0-Emergency |
[chars]-[chars] |
Receive some EMERG message from DPIC |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-1-DPIC_ALERT |
1-Alert |
[chars]-[chars] |
Receive some ALERT message from DPIC |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-2-DPIC_CRIT |
2-Critical |
[chars]-[chars] |
Receive some CRITICAL message from DPIC |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-CORTINA_PHY_DEV_ATTACH_ERROR |
3-Error |
[chars] Cortina PHY device attach error port [dec]/[dec]/[dec] |
Unable to attach Cortina PHY device object |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-CORTINA_PHY_DEV_CREATE_ERROR |
3-Error |
[chars] Cortina PHY device create error port [dec]/[dec]/[dec] |
Unable to create Cortina PHY device object |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-CORTINA_PHY_DEV_INIT_ERROR |
3-Error |
[chars] Cortina PHY device init error port [dec]/[dec]/[dec] |
Unable to downaload firmware to Cortina PHY device |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-DPIC_BOOT_REASON |
3-Error |
DPIC [dec]/[dec]: [chars] |
DPIC Boot Error Reason |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-DPIC_ERR |
3-Error |
[chars]-[chars] |
Receive some ERR message from DPIC |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-DPIC_NGIO_ERROR |
3-Error |
NGIO connection between IOMd and DPIC [dec]/[dec] is down! |
NGIO is down between IOMd and DPIC |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-DPIC_NGIO_KEEPALIVE |
3-Error |
NGIO keepalive between IOMd and DPIC [dec]/[dec] timeout! \%lu NGIO rx %lu ping successes %lu ping failures |
NGIO keepalive is timeout. |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-DTI_CLIENT_DNLD_ERROR |
3-Error |
[chars] DTI Client error |
Unable to download DTI client firmware |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-ESI_CLK_NOT_RDY_ERR |
3-Error |
[chars] Falcon ESI Clocks reg:0x%08x |
Falcon-ESI clocks are NOT Ready |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-ESI_CLOCK_NOT_READY_ERROR |
3-Error |
[chars] Raptor ESI Clocks reg:0x%08x |
Raptor-ESI clocks are NOT Ready |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-ESI_NOT_READY_ERROR |
3-Error |
[chars] Raptor ESI Global Ready reg:0x%08x |
Raptor-ESI NOT Ready |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-ESI_PIC_PWR_NOT_GOOD_ERR |
3-Error |
[chars] Falcon SUP PIC Power not good |
Falcon-ESI PLL not locked |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-ESI_PIC_PWR_NOT_GOOD_ERROR |
3-Error |
[chars] Raptor SUP PIC Power not good |
Raptor-ESI PLL not locked |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-ESI_PIC_STATUS_REG_READ_ERR |
3-Error |
[chars] unable to read from Falcon ESI PIC STATUS REG err [dec] |
Unable to communicate with Falcon Device driver |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-ESI_PIC_STATUS_REG_READ_ERROR |
3-Error |
[chars] unable to read from Raptor ESI PIC STATUS REG err [dec] |
Unable to communicate with Raptor Device driver |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-ESI_PLL_CTRL_LOCK_ERR |
3-Error |
[chars] unable to lock Falcon ESI PLL |
Falcon-ESI PLL not locked |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-ESI_PLL_CTRL_LOCK_ERROR |
3-Error |
[chars] unable to lock Raptor ESI PLL |
Raptor-ESI PLL not locked |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-ESI_PLL_CTRL_REG_READ_ERR |
3-Error |
[chars] unable to read from Falcon ESI PLL CONTROL REG err [dec] |
Unable to communicate with Falcon Device driver |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-ESI_PLL_CTRL_REG_READ_ERROR |
3-Error |
[chars] unable to read from Raptor ESI PLL CONTROL REG err [dec] |
Unable to communicate with Raptor Device driver |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-ESI_PLL_CTRL_REG_WR_ERR |
3-Error |
[chars] unable to write to Falcon ESI PLL CONTROL REG err [dec] |
Unable to communicate with Falcon Device driver |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-ESI_PLL_CTRL_REG_WRITE_ERROR |
3-Error |
[chars] unable to write to Raptor ESI PLL CONTROL REG err [dec] |
Unable to communicate with Raptor Device driver |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-ESI_RDY_REG_READ_ERR |
3-Error |
[chars] unable to read Falcon ESI READY REG err [dec] |
Unable to communicate with Falcon Device driver |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-ESI_READY_REG_READ_ERROR |
3-Error |
[chars] unable to read Raptor ESI READY REG err [dec] |
Unable to communicate with Raptor Device driver |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-ESI_SUP_CHASSIS_SLOT_REG_WR_ERR |
3-Error |
[chars] unable to write to Falcon ESI CHASSIS SLOT ID REG err [dec] |
Unable to communicate with Falcon Device driver |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-ESI_SUP_CHASSIS_SLOT_REG_WRITE_ERROR |
3-Error |
[chars] unable to write to Raptor ESI CHASSIS SLOT ID REG err [dec] |
Unable to communicate with Raptor Device driver |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-ESI_SUP_CTRL_REG_WR_ERR |
3-Error |
[chars] unable to write to Falcon ESI CONTROL REG err [dec] |
Unable to communicate with Falcon Device driver |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-ESI_SUP_CTRL_REG_WRITE_ERROR |
3-Error |
[chars] unable to write to Raptor ESI CONTROL REG err [dec] |
Unable to communicate with Raptor Device driver |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-FALCON_EGR_BUF_LOCAL_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received from EGRESS LOCAL BUF\n\ Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-FALCON_EGR_BUF_PEER_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received from EGRESS REMOTE BUF\n\ Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-FALCON_EGR_DISPATCH_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received from EGRESS DISPATCH\n\ Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-FALCON_ESI_CLOCK_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received from CLOCK\n\ Module in Falcon-ESI FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-FALCON_ESI_PCIE_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received from PCIE Wrapper\n\ Module in Falcon-ESI FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-FALCON_FP_EGR_SCH_TOP_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received from FP\n\ EGRESS SCHDULER TOP Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-FALCON_FP_INGR_PAR_TOP_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received from FP\n\ INGRESS PARSER TOP Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-FALCON_INGR_BUF_LOCAL_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received from INGRESS LOCAL BUF\n\ Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-FALCON_INGR_BUF_PEER_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received from INGRESS REMOTE BUF\n\ Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-FALCON_INGR_PARSER_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received from INGRESS PARSER\n\ Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-FALCON_INGR_SCH_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received from INGRESS SCHDULER\n\ Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-FALCON_INIT_ERROR |
3-Error |
[chars] Falcon err [dec] |
Falcon driver initialization error |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-FALCON_MAC_ENTRY_FULL |
3-Error |
[chars] Falcon [chars] mac-filter entry full drop addr %02X.%02X.%02X.%02X.%02X.%02X |
Falcon mac filter entry full |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-FALCON_MAC_LOCAL_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received from LCOAL MAC\n\ Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-FALCON_MAC_PEER_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received from PEER MAC\n\ Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-FALCON_MODE_XCVR_MATCH_ERR |
3-Error |
SUP-PIC [dec]/1 port [dec] interface mode mismatched: QSFP type is [chars] interface mode is [chars] |
SUP250 backhaul interface support two kinds of transceiver: QSFP28 and QSFP+. If the backhaul mode is configured as 100GE mode with commad 'cable sup250-ifmod 100GE' but insert a QSFP+ transceiver. Or the backhaul mode is configured as 10GE mode with comand 'cable sup250-ifmod 10GE' but insert a QSFP28 transceiver. This error message will be reported. |
- |
"Change configration to another backhaul mode or replace other type of transceiver." |
|
CBR_SPA-3-FALCON_PAR_RST_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received from PAR RST\n\ Module in Falcon-ESI FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-FALCON_PLL_LOS |
3-Error |
[chars] |
Falcon PLL LOS |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-FALCON_PMBIST_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received from PM BIST\n\ Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-FALCON_SEM_HI_INTERRUPT |
3-Error |
[chars] [chars] err_report_reg 0x[hec] stat_reg 0x[hec] |
HIGH Priority Interrupt received from SEM\n\ Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-MAC_CFG_REG_WRITE_ERROR |
3-Error |
[chars] unable to write to Raptor MAC RX/TX CFG REG err [dec] |
Unable to communicate with Raptor Device driver |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-MAC_CLK_NOT_RDY_ERR |
3-Error |
[chars] Falcon MAC Clocks reg:0x%08x |
Falcon-MAC clocks are NOT Ready |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-MAC_CLOCK_NOT_READY_ERROR |
3-Error |
[chars] Raptor MAC Clocks reg:0x%08x |
Raptor-MAC clocks are NOT Ready |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-MAC_NOT_RDY_ERR |
3-Error |
[chars] Falcon MAC Global reg:0x%08x |
Falcon-MAC Contrpl Plane NOT Ready |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-MAC_NOT_READY_ERROR |
3-Error |
[chars] Raptor MAC Global reg:0x%08x |
Raptor-MAC Contrpl Plane NOT Ready |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-MAC_PIC_CPLD_NOT_RDY_ERR |
3-Error |
[chars] Falcon MAC PIC CPLD error |
Falcon-MAC PIC CPLD NOT Ready |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-MAC_PIC_CPLD_NOT_READY_ERROR |
3-Error |
[chars] Raptor MAC PIC CPLD error |
Raptor-MAC PIC CPLD NOT Ready |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-MAC_PIC_CTRL_REG_WR_ERR |
3-Error |
[chars] unable to write to Falcon MAC PIC CONTROL REG err [dec] |
Unable to communicate with Falcon Device driver |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-MAC_PIC_CTRL_REG_WRITE_ERROR |
3-Error |
[chars] unable to write to Raptor MAC PIC CONTROL REG err [dec] |
Unable to communicate with Raptor Device driver |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-MAC_READY_REG_READ_ERR |
3-Error |
[chars] unable to read Falcon MAC READY REG err [dec] |
Unable to communicate with Falcon Device driver |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-MAC_READY_REG_READ_ERROR |
3-Error |
[chars] unable to read Raptor MAC READY REG err [dec] |
Unable to communicate with Raptor Device driver |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-NULL_SPA_PTR |
3-Error |
- |
Pointer to a SPA object is NULL. |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-RAPTOR_ESI_CLOCK_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received from Clock\n\ Module in Raptor-ESI FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-RAPTOR_ESI_INGRESS_SCH_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received from Ingress Scheduler\n\ Module in Raptor-ESI FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-RAPTOR_ESI_PCIE_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received from PCIE Wrapper\n\ Module in Raptor-ESI FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-RAPTOR_ESI_PROCBUS_MASTER_HI_INTERRUPT |
3-Error |
[chars] [chars] |
HIGH Priority Interrupt received from ProcBus Master\n\ Module in Raptor-ESI FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-RAPTOR_ESI_PRST_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received Partial reset\n\ Module in Raptor-ESI FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-RAPTOR_ESI_SERDES_PKTBUS_HI_INTERRUPT |
3-Error |
[chars] [chars] |
Hign Priority Interrupt received from Serdes PktBus\n\ Module in Raptor-ESI FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-RAPTOR_INIT_ERROR |
3-Error |
[chars] Raptor err [dec] |
Raptor driver initialization error |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-RAPTOR_LED_ERROR |
3-Error |
SUP-PIC [dec]/[dec] LED err |
SUP-PIC LED initialization error |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-RAPTOR_MAC_CLOCK_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received from Clock\n\ Module in Raptor-MAC FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-RAPTOR_MAC_DNLD_FAILED |
3-Error |
[chars] Raptor-MAC error |
Unable to download Raptor-MAC firmware |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-RAPTOR_MAC_ENTRY_FULL |
3-Error |
[chars] Raptor [chars] mac-filter entry full drop addr %02X.%02X.%02X.%02X.%02X.%02X |
Raptor mac filter entry full |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-RAPTOR_MAC_FIFO_CTL_HI_INTERRUPT |
3-Error |
[chars] [chars] |
HIGH Priority Interrupt received from FIFO Control\n\ Module in Raptor-MAC FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-RAPTOR_MAC_MDIO_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received from MDIO\n\ Module in Raptor-MAC FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-RAPTOR_MAC_PROCBUS_SLAVE_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received from ProcBus Slave\n\ Module in Raptor-MAC FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-RAPTOR_MAC_PRST_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received Partial reset\n\ Module in Raptor-MAC FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-RAPTOR_MAC_RLDRAM_HI_INTERRUPT |
3-Error |
[chars] [chars] |
HIGH Priority Interrupt received from RLDRAM\n\ Module in Raptor-MAC FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-RAPTOR_MAC_SERDES_PKTBUS_HI_INTERRUPT |
3-Error |
[chars] [chars] |
HIGH Priority Interrupt received from Serdes PktBus\n\ Module in Raptor-MAC FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-RAPTOR_MAC_XFI_IF_HI_INTERRUPT |
3-Error |
[chars] [chars] |
High Priority Interrupt received from XFI\n\ Module in Raptor-MAC FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-RAPTOR_PLL_LOS |
3-Error |
[chars] |
Raptor PLL LOS |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-RAPTOR_PRST_HIT_CONSTANT_CRC |
3-Error |
Detected continual CRC errors on SUP-PIC [dec]/1 port [dec] or port [dec]! |
SUP160 backhaul interface's recover service was blocked because there are continual CRC errors on corresponding interface. |
- |
"Check related link including fiber line SFP module etc..." |
|
CBR_SPA-3-RAPTOR_SEM_HI_INTERRUPT |
3-Error |
[chars] [chars] err_report_reg 0x[hec] stat_reg 0x[hec] |
HIGH Priority Interrupt received from SEM\n |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-RETIMER_PHY_DEV_ATTACH_ERROR |
3-Error |
[chars] Retimer PHY device attach error quad [dec]/[dec]/[dec] |
Unable to attach Retimer PHY device object |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-RETIMER_PHY_DEV_CREATE_ERROR |
3-Error |
[chars] Retimer PHY device create error quad [dec]/[dec]/[dec] |
Unable to create Retimer PHY device object |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-RETIMER_PHY_DEV_INIT_ERROR |
3-Error |
[chars] Retimer PHY device init error quad [dec]/[dec]/[dec] |
Unable to init Retimer PHY device |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-SFP_SUB_INIT_ERROR |
3-Error |
[chars] SFP Subblock create error |
Unable to create SFP sub-block |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-SPA_DPIC_UPGRADE_NOSPACE |
3-Error |
no enough space in harddisk to store digital pic image \[dec]MB free [dec]MB needed\n |
DIGI PIC firmware can not be upgraded\n\ due to harddisk is full\n |
- |
"Free up some space in harddisk to \store digital pic image." |
|
CBR_SPA-3-SPA_PLUGIN_INIT_ABORT_ERROR |
3-Error |
[chars] SPA Plugin Init Abort error |
Unknown SPA Init phase |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-SPA_RFSW_I2C_FAILURE |
3-Error |
I2C failure on [dec]/[dec] I2C status:[chars] |
An I2C failure error received from RFSW PIC\n |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-SPA_RFSW_POWER_ERROR |
3-Error |
Power circuit error on [dec]/[dec] voltages:[chars] |
A power circuit error received from RFSW PIC\n |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-SPA_RFSW_RELAY_FAILURE |
3-Error |
Relay failure on [dec]/[dec] relay status:[chars] |
A Relay failure error received from RFSW PIC\n |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-SPA_RFSW_TEMPERATURE_ERROR |
3-Error |
Temperature Error on [dec]/[dec] temperature:[chars] |
A Temperature error received from RFSW PIC\n |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-SPA_RFSW_UPGRADE_UNSUPPORTED |
3-Error |
unsupported firmware upgrade on [dec]/[dec] firmware version :[hec]\n |
RFSW PIC firmware can not be upgraded\n |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-SPA_UNKN_INIT_ERROR |
3-Error |
[chars] Unknown SPA Init phase error |
Unknown SPA Init phase |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-XCVR_MISSING_HWIDB_ERROR |
3-Error |
[chars] XCVR Missing interface object port [dec]/[dec]/[dec] |
Unable to downaload firmware to Cortina PHY device |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-XCVR_POP_DEF_PARAMS_ERROR |
3-Error |
[chars] XCVR Unable to poulate default parameters port [dec]/[dec]/[dec] |
Unable to poulate default XCVR SM parameters |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-3-XCVR_SM_LAUNCH_ERROR |
3-Error |
[chars] XCVR Unable to launch SM port [dec]/[dec]/[dec] |
Unable to launch XCVR SM |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-4-DPIC_WARNING |
4-Warning |
[chars]-[chars] |
Receive some WARNING message from DPIC |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-4-FALCON_PLL_MIS |
4-Warning |
[chars] |
Falcon PLL clock soure not come from active RP\n |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-4-RAPTOR_PLL_MIS |
4-Warning |
[chars] |
Raptor PLL clock soure not come from active RP\n |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-4-SPA_RFSW_WATCH_DOG_TIMEOUT |
4-Warning |
Watch Dog Timeout on [dec]/[dec] |
A Watch Dog Timeout error received from RFSW PIC\n |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-5-DPIC_NOTICE |
5-Notice |
[chars]-[chars] |
Receive some NOTICE message from DPIC |
- |
LOG_STD_NO_ACTION |
|
CBR_SPA-5-DPIC_RESET |
5-Notice |
DPIC [dec]/[dec] will be recovered from unexpected state |
DPIC can not be online in 5 min |
- |
LOG_STD_NO_ACTION |
|
CBR_SPA-6-DPIC_INFO |
6-Information |
[chars]-[chars] |
Receive some INFO message from DPIC |
- |
LOG_STD_NO_ACTION |
|
CBR_SPA-6-SPA_DPIC_UPGRADE_UNSUPPORTED |
6-Information |
unsupported firmware upgrade on [dec]/[dec]\n |
DIGI PIC firmware can not be upgraded\n |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-7-DPIC_DEBUG |
7-Debug |
[chars]-[chars] |
Receive some DEBUG message from DPIC |
- |
LOG_STD_DBG_ACTION |
|
CBR_SPA-7-FALCON_EGR_BUF_LOCAL_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from EGRESS LOCAL BUF\n\ Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-7-FALCON_EGR_BUF_PEER_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from EGRESS REMOTE BUF\n\ Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-7-FALCON_EGR_DISPATCH_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from EGRESS DISPATCHER\n\ Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-7-FALCON_ESI_FC_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from ESI FC\n\ Module in Falcon-ESI FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-7-FALCON_ESI_PCIE_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from PCIE Wrapper\n\ Module in Falcon-ESI FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-7-FALCON_ESI_QPLL_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from PCIE Wrapper\n\ Module in Falcon-ESI FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-7-FALCON_FP_10G_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from FP 10G\n\ Module in Falcon-ESI FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-7-FALCON_FP_EGR_SCH_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from FP EGRESS SCHEDULER\n\ Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-7-FALCON_FP_INGR_PAR_TOP_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from FP INGRESS PARSER TOP\n\ Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-7-FALCON_GB_MDIO_IF_HI_INTERRUPT |
7-Debug |
[chars] [chars] |
High Priority Interrupt received from GB MDIO\n\ Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-7-FALCON_INGR_BUF_LOCAL_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from INGRESS LOCAL BUF\n\ Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-7-FALCON_INGR_BUF_PEER_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from INGRESS REMOTE BUF\n\ Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-7-FALCON_INGR_PARSER_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from INGRESS PARSER\n\ Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-7-FALCON_INGR_SCH_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from INGRESS SCHEDULER\n\ Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-7-FALCON_INTERRUPT_DISABLE |
7-Debug |
Interrupt throttled for: [chars] [chars] |
Interrupt throttled\n |
- |
LOG_STD_DBG_ACTION |
|
CBR_SPA-7-FALCON_INTERRUPT_ENABLE |
7-Debug |
Interrupt enabled for: [chars] [chars] |
Interrupt unthrottled\n |
- |
LOG_STD_DBG_ACTION |
|
CBR_SPA-7-FALCON_MAC_LOCAL_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from LOCAL MAC\n\ Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-7-FALCON_MAC_PEER_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from REMOTE MAC\n\ Module in Falcon FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-7-FALCON_PAR_RST_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from PAR RST\n\ Module in Falcon-ESI FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-7-FALCON_PWM_DIST_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from PWM DIST\n\ Module in Falcon-ESI FPGA |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-7-FALCON_SEM_LO_INTERRUPT |
7-Debug |
[chars] [chars] err_report_reg 0x[hec] stat_reg 0x[hec] |
Low Priority Interrupt received from SEM\n |
- |
LOG_STD_SH_TECH_ACTION |
|
CBR_SPA-7-RAPTOR_ESI_EGRESS_HDR_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from Egress\n\ Header Module in Raptor-ESI FPGA |
- |
LOG_STD_DBG_ACTION |
|
CBR_SPA-7-RAPTOR_ESI_EGRESS_SCH_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from Egress\n\ Scheduler Module in Raptor-ESI FPGA |
- |
LOG_STD_DBG_ACTION |
|
CBR_SPA-7-RAPTOR_ESI_FC_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from Flow\n\ Control Module in Raptor-ESI FPGA |
- |
LOG_STD_DBG_ACTION |
|
CBR_SPA-7-RAPTOR_ESI_INGRESS_SCH_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from Ingress\n\ Scheduler Module in Raptor-ESI FPGA |
- |
LOG_STD_DBG_ACTION |
|
CBR_SPA-7-RAPTOR_ESI_PCIE_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from PCIE Wrapper\n\ Module in Raptor-ESI FPGA |
- |
LOG_STD_DBG_ACTION |
|
CBR_SPA-7-RAPTOR_ESI_PROCBUS_MASTER_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from ProcBus Master\n\ Module in Raptor-ESI FPGA |
- |
LOG_STD_DBG_ACTION |
|
CBR_SPA-7-RAPTOR_ESI_PRST_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received Partial reset\n\ Module in Raptor-ESI FPGA |
- |
LOG_STD_DBG_ACTION |
|
CBR_SPA-7-RAPTOR_ESI_SERDES_PKTBUS_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from Serdes PacketBus\n\ Module in Raptor-ESI FPGA |
- |
LOG_STD_DBG_ACTION |
|
CBR_SPA-7-RAPTOR_INTERRUPT_DISABLE |
7-Debug |
Interrupt throttled for: [chars] [chars] |
Interrupt throttled\n |
- |
LOG_STD_DBG_ACTION |
|
CBR_SPA-7-RAPTOR_INTERRUPT_ENABLE |
7-Debug |
Interrupt enabled for: [chars] [chars] |
Interrupt unthrottled\n |
- |
LOG_STD_DBG_ACTION |
|
CBR_SPA-7-RAPTOR_MAC_10G_MAC_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from 10GE MAC\n\ Module in Raptor-MAC FPGA |
- |
LOG_STD_DBG_ACTION |
|
CBR_SPA-7-RAPTOR_MAC_FIFO_CTL_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from FIFO Control\n\ Module in Raptor-MAC FPGA |
- |
LOG_STD_DBG_ACTION |
|
CBR_SPA-7-RAPTOR_MAC_FIFO_CTRL_MUX_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from FIFO Control MUX\n\ Module in Raptor-MAC FPGA |
- |
LOG_STD_DBG_ACTION |
|
CBR_SPA-7-RAPTOR_MAC_INGRESS_QOS_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from Ingress QoS\n\ Module in Raptor-MAC FPGA |
- |
LOG_STD_DBG_ACTION |
|
CBR_SPA-7-RAPTOR_MAC_MAC_SCH_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from MAC Scheduler\n\ Module in Raptor-MAC FPGA |
- |
LOG_STD_DBG_ACTION |
|
CBR_SPA-7-RAPTOR_MAC_PROCBUS_SLAVE_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from Proc Bus\n\ Module in Raptor-MAC FPGA |
- |
LOG_STD_DBG_ACTION |
|
CBR_SPA-7-RAPTOR_MAC_PRST_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received Partial reset\n\ Module in Raptor-MAC FPGA |
- |
LOG_STD_DBG_ACTION |
|
CBR_SPA-7-RAPTOR_MAC_RLDRAM_IF_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from RLDRAM Interface\n\ Module in Raptor-MAC FPGA |
- |
LOG_STD_DBG_ACTION |
|
CBR_SPA-7-RAPTOR_MAC_SERDES_PKTBUS_LO_INTERRUPT |
7-Debug |
[chars] [chars] |
Low Priority Interrupt received from Serdes Packet Bus\n\ Module in Raptor-MAC FPGA |
- |
LOG_STD_DBG_ACTION |
|
CBR_SPA-7-RAPTOR_SEM_LO_INTERRUPT |
7-Debug |
[chars] [chars] err_report_reg 0x[hec] stat_reg 0x[hec] |
Low Priority Interrupt received from SEM\n |
- |
LOG_STD_DBG_ACTION |
|
CBR_VIDEO-3-LED_NO_RESOURCE |
3-Error |
LED Subsystem Init Failed |
Logical Edge Device subsystem init failed |
video-cp |
"Verify system memory and check is the image correct." |
|
CBR_VIDEO-6-LOGICAL_EDGE_DEVICE |
6-Information |
LED [dec] [chars]. |
Logical Edge Device Process terminated/restarted |
video-cp |
"LOG_STD_NO_ACTION" |
|
CBRCCE-3-CBR_DP_CFR_ADD_ERR |
3-Error |
Failed to add cfr for CM [enet] cfr id [dec] sfref [dec] sfid [dec] rc [dec] |
Mostly caused by cfr chunk exhausted or cm_qos not found |
cbrcce-sw |
LOG_STD_SH_TECH_ACTION |
|
CBRCCE-3-CBR_DP_DYN_QOS_ERR |
3-Error |
Failed to commit dynamic qos for CM [enet] sfid [dec] rc [dec] |
Mostly caused by dynamic qos bind failure |
cbrcce-sw |
LOG_STD_SH_TECH_ACTION |
|
CBRCCE-3-CBR_DP_FLOW_ADD_ERR |
3-Error |
Failed to add flow for CM [enet] sfid [dec] rc [dec] |
Mostly caused by flow or cm_qos chunk exhausted |
cbrcce-sw |
LOG_STD_SH_TECH_ACTION |
|
CBRCCE-3-CBR_DP_FORW_INTF_SET_ERR |
3-Error |
Failed to set forwarding interface for CM [enet] sfid [dec] rc [dec] |
Mostly caused by invalid service flow ID |
cbrcce-sw |
LOG_STD_SH_TECH_ACTION |
|
CBRCCE-3-CBR_DP_JIB_HDR_SET_ERR |
3-Error |
Failed to set JIB header for CM [enet] sfid [dec] rc [dec] |
Mostly caused by invalid service flow ID |
cbrcce-sw |
LOG_STD_SH_TECH_ACTION |
|
CBRCCE-3-CBR_DP_LOCK_ERR |
3-Error |
Failed to lock semaphore pid [dec] |
Mostly caused by a process hogging CPU |
cbrcce-sw |
LOG_STD_SH_TECH_ACTION |
|
CBRCCE-3-CBR_DP_QOS_PARAMS_SET_ERR |
3-Error |
Failed to set qos parameters for CM [chars] sfid [dec] rc [dec] |
Mostly caused by invalid service flow ID |
cbrcce-sw |
LOG_STD_SH_TECH_ACTION |
|
CBRCCE-3-CBR_DP_STA_QOS_ERR |
3-Error |
Failed to commit static qos for CM [enet] rc [dec] |
Mostly caused by qos bind failure |
cbrcce-sw |
LOG_STD_SH_TECH_ACTION |
|
CBRCCE-3-CBR_DP_TMP_DEL_ERR |
3-Error |
Failed to remove template from template_list for CM [enet] |
Mostly caused by template remove failure |
cbrcce-sw |
LOG_STD_SH_TECH_ACTION |
|
CBRCCE-4-CBR_DP_CFR_PARAM_CONFLICT |
4-Warning |
Classifier's parameters conflict: [chars] |
Mostly caused by unsupported classifier's parameters combination |
cbrcce-sw |
"Please do not configure unsupported classifier's " "parameters or unsupported classifier's parameters combination " "as the error message indicated." |
|
CBRDTI-5-DTISLOT |
5-Notice |
DTI slot [dec]/[dec]: card role changed to [chars]\n |
Change in role of DTI slot |
dti |
"Check DTI link/cable" |
|
CBRDTI-6-CHG_CLK_REF |
6-Information |
Clock reference source set to [chars] |
The reasons for the change in clock reference. 1Manual mode configuration command for DTI mode |
dti |
"Check reference source of DTI" |
|
CBUS-3-ADDRFILTR |
3-Error |
Interface [chars] address filter [chars] command failed code %#04x |
The specified address filter command sent to the specified\n\ interface failed with the displayed error code. |
cbus |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CBUS-3-AIPINVPLIM |
3-Error |
Interface [chars] Invalid PLIM detected. Interface downed |
A software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-BADRXEOFVEC |
3-Error |
[chars] ustatus: [chars] %04x %04x %04x %04x %04x |
Debugging information when an IP panics. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CBUS-3-BADTXEOFVEC |
3-Error |
[chars] ustatus: [chars] %04x %04x %04x %04x %04x |
Debugging information when an IP panics. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CBUS-3-BADTXSTATE |
3-Error |
[chars] ustatus: [chars] %04x %04x %04x %04x %04x |
Debugging information when an IP panics. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CBUS-3-BADVC |
3-Error |
[chars] [dec]/[dec] got bad VC packet \n%08x %08x %08x %08x %08x %08x %08x %08x |
An interface received a packet with bad VC encapsulation. \n\ This indicates either a software or hardware problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-BUFFER |
3-Error |
Controller [dec] Error %-04x Buffersize = [dec] Bufferpool = [dec] number [dec] |
An internal software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-CATMCFG |
3-Error |
Interface [chars] Cannot config interface CBus ATM MEM 0x[hec] status [dec] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CBUS-3-CATMRSET |
3-Error |
Interface [chars] Error %-04x [chars] - aip_reset |
A software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-CATMRSETU |
3-Error |
Unit [dec] Error %-04x [chars] - cbus_atm_reset |
A software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-CBUSBCE |
3-Error |
Failed to select a BCE response 0x%04x - cbus_bce_update_ifa |
A hardware or software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-CBUSBCEPERM |
3-Error |
Failed to select a BCE response 0x%04x - cbus_bce_permissions_update |
A hardware or software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-CCBCMDFAIL0 |
3-Error |
Controller [dec] cmd [dec] failed 0x%-04x |
A command sent from the system to an interface processor failed to\n\ complete successfully. |
- |
"The system recovered by generating an error code to the requester." |
|
CBUS-3-CCBCMDFAIL1 |
3-Error |
Controller [dec] cmd [dec] 0x%-08x failed 0x%-04x |
A command sent from the system to an interface processor failed to\n\ complete successfully. |
- |
"The system recovered by generating an error code to the requester." |
|
CBUS-3-CCBCMDFAIL3 |
3-Error |
Controller [dec] cmd [dec] 0x%-04x 0x%-04x 0x%-04x failed 0x%-04x |
A command sent from the system to an interface processor failed to\n\ complete successfully. |
- |
"The system recovered by generating an error code to the requester." |
|
CBUS-3-CCBPTIMEOUT |
3-Error |
CCB handover timed out CCB 0x[hec] slot [dec] |
A hardware or software error occurred. |
cwpa |
"Please gather the logs and tracebacks " "and contact the TAC" |
|
CBUS-3-CCBSEMINFO |
3-Error |
CCB semaphore acquired traceback:[chars]\n CCB semaphore released traceback:[chars] |
More information on the CCB semaphore. The tracebacks indicate the program counters and stack that point to the code that was the last to acquire this semaphore and the last to release this semaphore respectively |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-CE3DSX3ERR |
3-Error |
[chars]Illegal E3 value - unit is [dec] |
- |
- |
- |
|
CBUS-3-CFGCMDDROPPED |
3-Error |
Config queue is full command was dropped slot [dec] |
Sending a config command was retried. The receiving\n\ queues were still full after retries therefore the command was dropped. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CBUS-3-CMD |
3-Error |
Cmd failed: [chars] response %#04x [chars] |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CBUS-3-CMDDROPPED |
3-Error |
Cmd dropped CCB 0x[hec] slot [dec] cmd code [dec] |
A software or hardware error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-CMDTIMEOUT |
3-Error |
Cmd timed out CCB 0x[hec] slot [dec] cmd code [dec] |
A software or hardware error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-CORRUPT |
3-Error |
Controller [dec] wrote 0x%-04x read 0x%-04x loc 0x%-04x - dci_memtest |
A hardware component failed an internal diagnostic test. |
- |
"Replace the malfunctioning device." |
|
CBUS-3-CT3DSX3ERR |
3-Error |
[chars]Illegal dsx3 value - unit is [dec] |
- |
- |
- |
|
CBUS-3-CT3STAT |
3-Error |
Out of buffers--losing status information for CT3 on VIP card |
A status information message from the VIP was received.\n\ A memory buffer is required to process the status information \n\ message but the memory allocation routine due to insufficient\n\ system buffer memory. Therefore the status information message\n\ was not processed. This condition may be caused either by a heavy \n\ memory utilization at the time of the memory buffer request or by\n\ insufficient memory in the system. |
- |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration. If this \n\ message recurs or appears regularly contact your Cisco technical \n\ representative to upgrade the memory of the system." |
|
CBUS-3-CTRACHECK |
3-Error |
Interface [chars] Adapter Check Error %04x %04x %04x %04x |
The Token Ring monitor firmware detected a fatal error on the\n\ interface card. |
high-token |
"Issue a <Bold>clear interface<NoBold> command. " LOG_STD_RECUR_ACTION |
|
CBUS-3-CTRBADLOVE1 |
3-Error |
Interface [chars] SRB_COMPLETE lovenote received with unknown command 0x%04x |
The system received a message from the Token Ring interface\n\ but does not recognize the message. |
high-token |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-CTRBADLOVE1_DUMP |
3-Error |
Dump of MEMB follows\n-SRB_ADDR: %04x %04x %04x %04x %04x %04x %04x %04x |
The system is printing codes related to a previous lovenote error\n\ message. |
high-token |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-CTRCMDFAILED |
3-Error |
Interface [chars] CTR Command [chars] Failed [chars] %#04x |
A command sent from the system to the Token Ring interface failed to\n\ complete successfully. |
high-token |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-CTRCMDFAILED2 |
3-Error |
Interface [chars] CTR Command [chars] Failed Code %#04x |
A command sent from the system to the Token Ring interface failed to\n\ complete successfully. |
high-token |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-CTRINIT |
3-Error |
Interface [chars] CTR Initialization Failed - [chars] |
The Token Ring interface failed one of its internal self-tests. |
- |
"Issue a <Bold>clear interface<NoBold> command. " LOG_STD_RECUR_ACTION |
|
CBUS-3-CTRLRCMDFAIL0 |
3-Error |
Controller [dec] cmd [dec] failed 0x%-04x count [dec] |
A command sent from the system to an interface processor failed to\n\ complete successfully. |
- |
"The system recovered by generating an error code to the requester." |
|
CBUS-3-CTRLRCMDFAIL1 |
3-Error |
Controller [dec] cmd [dec] 0x%-08x failed 0x%-04x count [dec] |
A command sent from the system to an interface processor failed to\n\ complete successfully. |
- |
"The system recovered by generating an error code to the requester." |
|
CBUS-3-CTRRAMTEST |
3-Error |
Interface [chars] RAM Addressing Test Failed - [chars] |
The Token Ring interface failed its memory diagnostic tests. |
- |
"Issue a <Bold>clear interface<NoBold> command. " LOG_STD_RECUR_ACTION |
|
CBUS-3-CTRRSET |
3-Error |
Interface [chars] failed to initialize |
The Token Ring interface failed to insert into the Token Ring.\n\ The interface is placed into reset state and will not \n\ automatically try to re-insert itself. |
high-token |
"Issue a <Bold>clear interface<NoBold> command. " LOG_STD_RECUR_ACTION |
|
CBUS-3-CTRUCHECK |
3-Error |
Interface [chars] Microcode Check Error |
The Token Ring interface microcode detected an unrecoverable error. |
high-token |
"Issue a <Bold>clear interface<NoBold> command. " LOG_STD_RECUR_ACTION |
|
CBUS-3-DAUGHTER |
3-Error |
Unit [dec] daughter controller [dec] failed [chars] test - interface disabled |
- |
- |
"First check that the daughter controller card is properly seated in\n\ its Multibus and ciscoBus connectors. Next swap daughter cards and\n\ check whether the error follows the daughter card or the slot. If the\n\ message recurs call your technical support representative for\n\ assistance." |
|
CBUS-3-DAUGHTER_NO_RSP |
3-Error |
Unit [dec] daughter [dec] not responding 0x%04x - disabled |
- |
- |
"First make sure that the daughter card is properly seated in its\n\ Multibus and ciscoBus connectors. If this message recurs copy the \n\ error message exactly as it appears on the console or in the system\n\ log contact your Cisco technical support representative and provide\n\ the representative with the gathered information" |
|
CBUS-3-FCICMDFAIL0 |
3-Error |
Controller [dec] cmd [dec] failed 0x%-04x count [dec] |
A command sent from the system to an interface processor failed to\n\ complete successfully. |
- |
"The system recovered by generating an error code to the requester." |
|
CBUS-3-FCICMDFAIL1 |
3-Error |
Controller [dec] cmd [dec] 0x%-08x failed 0x%-04x count [dec] |
A command sent from the system to an interface processor failed to\n\ complete successfully. |
- |
"The system recovered by generating an error code to the requester." |
|
CBUS-3-FDDIRSET |
3-Error |
Interface [chars] Error %-04x [chars] - fddi_reset |
A hardware device did not respond appropriately to a request. |
- |
"Make sure the device is functioning and is configured correctly." |
|
CBUS-3-FDDIRSETU |
3-Error |
Unit [dec] Error %-04x [chars] - fddi_reset |
A hardware device did not respond appropriately to a request. |
- |
"Make sure the device is functioning and is configured correctly." |
|
CBUS-3-FSIPRSET |
3-Error |
Interface [chars] Error %-04x [chars] - fsip_reset |
- |
- |
"Check FSIP electrical connections cable and ciscoBus connections. An\n\ FSIP microcode reload will be required. If the check of electrical\n\ connections reveals no problems and the message recurs call your\n\ technical support representative for assistance." |
|
CBUS-3-HALSDHERR |
3-Error |
[chars]Illegal sdh value - unit is [dec] |
- |
- |
- |
|
CBUS-3-HALSTAT |
3-Error |
Out of buffers--losing status information for ChSTM-1 on VIP card |
An internal software resource has been exhausted. |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-HSSIRSET |
3-Error |
Interface [chars] Error %-04x [chars] - hssi_reset |
A command to reset an HSSI interface was issued by the RSP\n\ but the interface did not respond to the command within the\n\ expected time delay. The delay is given for the processor to\n\ return the buffers that it has allocated and to perform any\n\ necessary cleanup. This condition may be caused by a large number\n\ of buffers that have been allocated by the interface due to either\n\ heavy traffic or a hardware problem with the interface. |
- |
"Verify that the card is properly seated. If this error recurs \n\ then issue the <CmdBold>show tech-support<NoCmdBold> and\n\ <CmdBold>show logging<NoCmdBold> commands contact your Cisco \n\ technical support representative and provide the representative\n\ with the gathered information." |
|
CBUS-3-INITERR |
3-Error |
Interface [dec] Error %-04x idb %08x [dec] [chars] - cbus_init |
The switch processor or ciscoBus controller signaled an error while\n\ processing a packet or selecting an interface. This indicates a\n\ software problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-INTR |
3-Error |
Interface [dec] idb %08x [dec] [chars] - cbus_interrupt |
The switch processor or ciscoBus controller returned a nonsensical\n\ value. |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-MODULE |
3-Error |
Missing [chars] for [chars] |
A hardware or software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-NOBUF |
3-Error |
Buffer allocation failure: [chars] |
A hardware or software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-OUTHUNG |
3-Error |
[chars]: tx[chars] output hung %-04x - [chars] [chars] |
A transmission attempt on an interface failed. The interface might not\n\ be attached to a cable or there might be a software problem. |
- |
"Check that the interfaces are all connected to the proper cables. If\n\ that is not the problem call your technical support representative." |
|
CBUS-3-POLLFAIL |
3-Error |
Interface [chars] failed to respond debug info follows |
A Token Ring interface card failed to respond to periodic polling.\n\ This can indicate a software or hardware problem.\n\ See CBUS-3-POLLFAILDAT for the syntax of this message. |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-POLLFAILDAT |
3-Error |
Int [dec]: %04X %04X %04X %04X %04X %04X |
This is the debugging information for the CBUS-3-POLLFAIL error. |
- |
LOG_STD_DBG_ACTION |
|
CBUS-3-PORTTYPE |
3-Error |
Unexpected interface type for [chars][dec] port [dec] type [dec] |
A hardware or software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-POTSTAT |
3-Error |
Out of buffers--losing status information for POTENT on VIP card |
An internal software resource has been exhausted. |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-RESETNXI |
3-Error |
Reset of removed interface [hec] [chars] |
An interface reset was attempted on an interface that was removed from\n\ the router. This message appears if you use the shutdown command to\n\ bring down a removed interface. |
- |
LOG_STD_NO_ACTION |
|
CBUS-3-SELECTBADVC |
3-Error |
Select invalid vc number [dec]. |
An invalid channel number is selected |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-SENDIPCMDFAIL |
3-Error |
Send Ip Cmd Failed. Command dropped after [dec] retries CCB 0x[hec] slot [dec] cmd code [dec]\n |
Sending an ip command was retried. The receiving queues were still\n\ full after retries therefore the command was dropped. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CBUS-3-SERRSET |
3-Error |
Interface [chars] Error %-04x [chars] - serial_reset |
A software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-SRPRSET |
3-Error |
Interface [chars] Error %-04x [chars] - srp_reset |
A command to reset an SRP interface was issued by the RSP\n\ but the interface did not respond to the command within the\n\ expected time delay. The delay is given for the processor to\n\ return the buffers that it has allocated and to perform any\n\ necessary cleanup. This condition may be caused by a large number\n\ of buffers that have been allocated by the interface due to either\n\ heavy traffic or a hardware problem with the interface. |
- |
"Verify that the card is properly seated. If this error recurs \n\ then issue the <CmdBold>show tech-support<NoCmdBold> and\n\ <CmdBold>show logging<NoCmdBold> commands contact your Cisco \n\ technical support representative and provide the representative\n\ with the gathered information." |
|
CBUS-3-TESTFAIL |
3-Error |
Unit [dec] failed [chars] test - interface disabled |
A hardware component failed an internal diagnostic test. |
- |
"Check switch settings on the interface cards. Check for proper unit\n\ numbers. Reset the cards. Replace the malfunctioning device." |
|
CBUS-3-TXALLOC |
3-Error |
Error %-04x tx_allocate - cbus_init |
A hardware device did not respond appropriately to a request. |
- |
"Make sure the device is functioning and is configured correctly." |
|
CBUS-3-TXSTARTPENDACTIVE |
3-Error |
[chars] ustatus: [chars] %04x %04x %04x %04x %04x |
Debugging information when an IP panics. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CBUS-3-TXVCENCAPFAIL |
3-Error |
Detected bad tx vc encap on [chars] vc [dec]. Board encap failed [hex] [hex] [hex] |
Board encap failed on a transmit packet on a channelized serial \n\ interface which does not have the vc number encapsulation |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-UNKENC |
3-Error |
Interface [chars] unknown encaps type [hec] |
A packet was received from the CIP with an unknown encapsulation type.\n\ The packet will be dropped. |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-3-UNKNOWN |
3-Error |
[chars] ustatus: [chars] %04x %04x %04x %04x %04x |
Debugging information when an IP panics. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CBUS-4-CTRBADLOVE2 |
4-Warning |
Interface [chars] Unexpected SRB_COMPLETE lovenote command=0x%04x result=0x%04x |
The system received an unsolicited message from the Token Ring interface.\n\ The system ignored the message and continued normal processing. |
high-token |
LOG_STD_RECUR_ACTION |
|
CBUS-4-FIXBADTXVC |
4-Warning |
Detected and fixed bad tx vc encap on [chars] bad vc [dec] fixed vc [dec] |
A transmit packet on a channelized serial interface does not\n\ have the vc number encapsulation |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-4-NOCOOKIE |
4-Warning |
[chars]-[dec] controller missing configuration data - disabled |
The controller type was derived from a hardware probe. The controller\n\ number indicates the ciscoBus relative slot number. This is a hardware\n\ error |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-4-RSETFAIL |
4-Warning |
Interface [chars] failed to reset properly in [chars] code [hex] |
An interface reset command failed. This may be a software or hardware\n\ problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
CBUS-5-CBADVCSETUP |
5-Notice |
Interface [chars] setup vc failed with vci exceeding vc-per-vp - 3 |
The TI1570 chip reserves 3 RX DMA channels for OAM cells. As a result the last 3 VCIs of the last VPI block cannot be used for regular traffic. |
- |
"Avoid try different vci/vpi combinations." |
|
CBUS-5-FDDICMD |
5-Notice |
'[chars]' is not supported on [chars] |
This command is not supported on this FDDI interface. |
- |
LOG_STD_NO_ACTION |
|
CBUS-5-INPUTERR |
5-Notice |
Interface [chars] excessive input error rate |
Interface disabled because too many input errors occurred. |
- |
"Inspect condition of attached network hardware" |
|
CBUS-5-SENDIPCMDRECOV |
5-Notice |
Send Ip Cmd Succeeded after [dec] retries CCB 0x[hec] slot [dec] cmd code [dec]\n |
Sending an ip command was retried due to receiving queues being full.\n\ But after some retries command was send successfuly. |
- |
LOG_STD_NO_ACTION |
|
CCE_PI_PD-3-CLASS_NAME |
3-Error |
Map name [chars] id %08X unable to [chars] string [hec] |
- |
- |
- |
|
CCE_PI_PD-3-FILTER_LIST |
3-Error |
Failed to create class [chars] id %08X filter list |
An operation to create the filter list for a particular class has failed due to a resource issue. This may imply that the resultant notification via the API was deferred or dropped. |
cce |
"show class-map [type" " <class type>] <name>" |
|
CCE_PI_PD-4-CLASS_CLASS_GROUP_DB |
4-Warning |
Failed to [chars] class group id %08X class id %08X class group %08X [chars] database |
An operation to manipulate the record of the class groups and classes supplied via the PI/PD API has failed to perform the required action on a class group attached to a class successfully. This may imply that the resultant notification via the API was deferred or dropped. |
cce |
"show cce cpdp associations " "class-group <id>" |
|
CCE_PI_PD-4-CLASS_DB |
4-Warning |
Failed to [chars] class group id %08X class id %08X [chars] database |
An operation to manipulate the record of the class groups and classes supplied via the PI/PD API has failed to perform the required action on a class successfully. This may imply that the resultant notification via the API was deferred or dropped. |
cce |
"show cce cpdp associations " "class group <id>" |
|
CCE_PI_PD-4-CLASS_GROUP_DB |
4-Warning |
Failed to [chars] id %08X [chars] database |
An operation to manipulate the record of the class groups and classes supplied via the PI/PD API has failed to perform the required action on a class group successfully. This may imply that the resultant notification via the API was deferred or dropped. |
cce |
"show cce cpdp associations " "class-group <id>" |
|
CCE_PI_PD-4-FEATURE_BIND_DB |
4-Warning |
Failed to [chars] target id %08X class group %08X class id %08X feature [chars] binding [chars] database |
An operation to manipulate the record of the binding of a action within a policy map class to a particular target supplied via the PI/PD API has failed to perform the required action successfully. This may imply that the resultant notification via the API was deferred or dropped. |
cce |
"show cce cpdp bindings " "target <id>" |
|
CCE_PI_PD-4-TARGET_CLASS_GROUP_DB |
4-Warning |
Failed to [chars] id %08X [chars] database |
An operation to manipulate the record of the target class groups supplied via the PI/PD API has failed to perform the required action on a target class group successfully. This may imply that the resultant notification via the API was deferred or dropped. |
cce |
"show cce cpdp bindings " "target <id>" |
|
CCE_PI_PD-6-CLASS_CLASSES_DB |
6-Information |
Class group %08X class %08X [chars] contains a class group |
The class is reporting the presence of a class group upon its removal. This is informational. |
cce |
"show cce cpdp associations " "class-group <id>" |
|
CCE_PI_PD-6-CLASS_FILTER |
6-Information |
Class [chars] id %08X type [chars] filter list is unbalanced |
During the addition of a class an internal error was encountered during the construction of the match terms comprising that class. |
cce |
"show class-map" " [type <type>] <name>" |
|
CCE_PI_PD-6-CLASS_GROUP_CLASSES_DB |
6-Information |
Class group %08X contains classes |
The class group is reporting the presence of classes upon its removal. This is informational. |
cce |
"show cce cpdp associations " "class-group <id>" |
|
CCE_PI_PD-6-TARGET_BINDINGS_DB |
6-Information |
[chars] [chars] [chars] target class group %08X contains feature bindings |
The target class group is reporting the presence of feature bindings upon its removal. This is informational. |
cce |
"show cce cpdp bindings " "target <id>" |
|
CCE-3-CCE_IPV6_COMPR_CLASSIFY_FAIL |
3-Error |
Dataplane IPV6 compression classification error for interface [chars] |
Cisco internal software error. The dataplane was unable to complete processing of an IPV6 prefix classification request due to a miss on a TCAM lookup. This is likely due to a data initialization error |
cpp-ucode keyword:cce |
LOG_STD_ACTION |
|
CCE-3-CCE_NON_TCAM_CLASSIFY |
3-Error |
Dataplane classification error for interface [chars] |
Cisco internal software error. The dataplane was unable to complete processing of a classification request because an invalid form of classification was selected. This is likely due to a data initialization error |
cpp-ucode keyword:cce |
LOG_STD_ACTION |
|
CCE-3-HW_CCE_TCAM_CONFIG |
3-Error |
Control Plane classification config error: TCAM device not specified: MPLS or Layer2 [chars] [chars] |
Cisco internal software error. The dataplane was unable to complete processing of a classification request because the TCAM device was not specified. This is likely due to a data initialization error |
qfp-infra-internal keyword:cce |
LOG_STD_ACTION |
|
CCE-3-HW_CCE_TCAM_CONFIG_IPV4 |
3-Error |
Control Plane classification config error: TCAM device not specified: [chars] [chars] Ipv4 src %Ci dst %Ci |
Cisco internal software error. The dataplane was unable to complete processing of a classification request because the TCAM device was not specified. This is likely due to a data initialization error |
qfp-infra-internal keyword:cce |
LOG_STD_ACTION |
|
CCE-3-HW_CCE_TCAM_CONFIG_IPV6 |
3-Error |
Control Plane classification config error: TCAM device not specified: [chars] [chars] IPv6 src [ipv6_addr], dst [ipv6_addr], |
Cisco internal software error. The dataplane was unable to complete processing of a classification request because the TCAM device was not specified. This is likely due to a data initialization error |
qfp-infra-internal keyword:cce |
LOG_STD_ACTION |
|
CCE-3-HW_CCE_TCAM_CONFIG_IPV6_COMPR |
3-Error |
Control Plane classification config error: TCAM device not specified: [chars] [chars] IPv6 compression src [ipv6_addr], dst [ipv6_addr], |
Cisco internal software error. The dataplane was unable to complete processing of a classification request because the TCAM device was not specified. This is likely due to a data initialization error |
qfp-infra-internal keyword:cce |
LOG_STD_ACTION |
|
CCE-3-HW_CCE_TCAM_CONFIG_IPV6_EXT |
3-Error |
Control Plane classification config error: TCAM device not specified: [chars] [chars] IPv6_ext src [ipv6_addr], dst [ipv6_addr], |
Cisco internal software error. The dataplane was unable to complete processing of a classification request because the TCAM device was not specified. This is likely due to a data initialization error |
qfp-infra-internal keyword:cce |
LOG_STD_ACTION |
|
CCE-3-HW_TCAM_CONTROLLER |
3-Error |
Datapath classification program flow error: invalid TCAM controller 0x%lx |
Cisco internal software error. The dataplane detected a classification request providing an invalid TCAM controller value. The program flow Traceback |
qfp-infra-internal keyword:cce |
LOG_STD_ACTION |
|
CCH323-2-E164_LENGTH_IS_NOT_SUPPORTED |
2-Critical |
[chars]: E164 address length [dec] is not supported |
Received E164 address with the length that is not supported. |
ios-voice |
"Report this immediately to the technical support representative." |
|
CCH323-2-GTKP_UNREGSTR |
2-Critical |
Gatekeeper [chars] requested unregister from Gateway [chars] |
Gatekeeper requested unregister from Gateway |
ios-voice |
"Verify whether this is user intended or otherwise report this to the\n\ technical support representative." |
|
CCH323-2-GTWY_REGSTR_FAILED |
2-Critical |
Gateway [chars] failed to register with Gatekeeper [chars] even after [dec] retries |
Gateway failed to register with Gatekeeper |
ios-voice |
"Report this immediately to the technical support representative." |
|
CCH323-2-GTWY_REGSTR_FAILED_ALT_GK |
2-Critical |
Gateway [chars] failed attempt to register with Alternate Gatekeeper [chars] |
Gateway failed attempt to register with Alternate Gatekeeper |
ios-voice |
"Report this immediately to the technical support representative." |
|
CCH323-2-GTWY_UNREGSTR |
2-Critical |
Gateway [chars] unregistered from Gatekeeper [chars] |
Gateway unregistered from the Gatekeeper |
ios-voice |
"Verify whether this is user intended or otherwise report this to the\n\ technical support representative." |
|
CCH323-3-BAD_IP_ADDRESS |
3-Error |
[chars]: illegal destination [chars] |
The IP address passed from CCAPI in the call setup request is invalid |
ios-voice |
"Check the dial-peer configuration for the dial-peer that matches the\n\ called party number. Make sure that the session target field contains\n\ valid IP address. or DNS name" |
|
CCH323-3-CALL_SETUP_FAILED |
3-Error |
[chars]: call setup failed |
The call setup request failed |
ios-voice |
"Verify that the remote destination identified by the IP address is reachable" |
|
CCH323-3-CANNOT_ALLOCATE_CALL_INFO |
3-Error |
[chars]: cannot allocate call info data structure |
Allocation of the CCH323 call info structure failed. This is possibly due\n\ to the fact that system memory pool is exhausted. |
ios-voice |
"This call will be terminated due to lack of resource" |
|
CCH323-3-CANNOT_ALLOCATE_CCB |
3-Error |
[chars]: cannot allocate call control block |
Allocation of the CCH323 call control block failed. This is possibly due\n\ to the fact that system memory pool is exhausted. |
ios-voice |
"This can be a catastrophic error" |
|
CCH323-3-CANNOT_ALLOCATE_GW |
3-Error |
[chars]: cannot allocate gateway structure |
Allocation of the CCH323 gateway instance failed. This is possibly due\n\ to the fact that system memory pool is exhausted. |
voice-h323 |
"This can be a catastrophic error" |
|
CCH323-3-CANNOT_CREATE_CCB |
3-Error |
[chars]: cannot create the H.323 ccb Tree |
Creation of the H.323 CCB Tree failed. This is possibly due to the fact \n\ that system memory pool is exhausted. |
voice-h323 |
"This can be a catastrophic error" |
|
CCH323-3-CANNOT_CREATE_CRVHASH_TBL |
3-Error |
[chars]: cannot create the H.323 crv hash table |
Creation of the H.323 CRV Hash Table failed. This is possibly due to \n\ the fact that system memory pool is exhausted. |
voice-h323 |
"This can be a catastrophic error" |
|
CCH323-3-CANNOT_FIND_CCB |
3-Error |
[chars]: cannot find CCH323 call control block based on callID [dec] |
Cannot find a CCH323 call control block based on the specified callID |
ios-voice |
"No action is required. This is an indication that some events happen\n\ out of sequence" |
|
CCH323-3-CANNOT_INSERT_CCB |
3-Error |
[chars]: cannot insert control block 0x[hec] to tree |
Insertion of this CCH323 call control block to the RBTree failed. This\n\ can be related to a corrupted RBTree |
ios-voice |
"This can be a catastrophic error" |
|
CCH323-3-CCAPI_CONNECT_ERROR |
3-Error |
[chars]: cc_api_call_disconnected returns [dec] |
An error is returned when CCH323 attempts to call cc_api_call_connected |
ios-voice |
"None" |
|
CCH323-3-CCAPI_DISCONNECT_ERROR |
3-Error |
[chars]: cc_api_call_disconnected returns [dec] |
An error is returned when CCH323 attempts to call cc_api_call_disconnected |
ios-voice |
"None" |
|
CCH323-3-CCH323_H225_SEND_EVENT_FAILED |
3-Error |
[chars]: create send internal event [chars] to H.225 state machine failed |
create and send event to H.225 state machine failed. This is possibly due\n\ to the missing call control block or not enough memory for event buffers |
ios-voice |
"This can be a catastrophic error" |
|
CCH323-3-CCH323_H245_SEND_EVENT_FAILED |
3-Error |
[chars]: create and send event [chars] to H.245 state machine failed |
create and send event to H.245 state machine failed. This is possibly due\n\ to the missing call control block or not enough memory for event buffers |
ios-voice |
"This can be a catastrophic error" |
|
CCH323-3-CCH323_MALLOC_FAILED |
3-Error |
[chars]: cannot allocate message buffer |
Allocation of the CCH323 message buffer failed. This is possibly due\n\ to the fact that system memory pool is exhausted. |
ios-voice |
"This can be a catastrophic error" |
|
CCH323-3-CCH323_RAS_SEND_EVENT_FAILED |
3-Error |
[chars]: create and send event [chars] to RAS state machine failed |
create and send event to RAS state machine failed. This is possibly due\n\ to the missing call control block or not enough memory for event buffers |
ios-voice |
"This can be a catastrophic error" |
|
CCH323-3-CCH323_RSCMON_SETUP_FAILURE |
3-Error |
[chars][dec] |
A failure was encountered in setting up the monitoring of\n\ H323 resources. |
ios-voice |
"Try power cycling the system. " LOG_STD_RECUR_ACTION |
|
CCH323-3-CCH323_UNKNOWN_EVENT |
3-Error |
unknown event [hec] |
Unknown CCH323 Event |
ios-voice |
"No action is required" |
|
CCH323-3-H225_LIBRARY_INIT_FAILED |
3-Error |
[chars]: H.225.0 library initialization failed |
H.225.0 library initialization failed |
ios-voice |
"This can be catastrophic" |
|
CCH323-3-H225_SM_INIT_FAILED |
3-Error |
[chars]: H.225.0 State Machine integrity check failed for state [chars] |
H.225 State Machine integrity check failed |
ios-voice |
"This can be catastrophic" |
|
CCH323-3-INTERNAL_EVENT_QUEUE_INIT_FAILED |
3-Error |
[chars]: Internal event queue initialization failed |
Errors are found during initialization of internal event qeuue machanisa |
ios-voice |
"This can be a catastrophic error" |
|
CCH323-3-MAXIMUM_INTERNAL_EVENT_BUFFERS_EXCEED |
3-Error |
[chars]: Exceeding limit on allocating internal event buffers |
The limit for allocating internal event buffers has been exceeded.\n\ The condition may be caused by internal loops on\n\ sending events between state machines. |
- |
"This can be a severe error" |
|
CCH323-3-OSS_INIT_FAILED |
3-Error |
[chars]: OSS init failure: errno = [dec] |
OSS ASN1 initialization failed |
ios-voice |
"This can be catastrophic" |
|
CCH323-3-POSSIBLE_INTERNAL_EVENT_LOOP |
3-Error |
[chars]: Exceeding limit on servicing internal event for the same call |
The maximum limit on servicing internal event queue has exceeded\n\ the limit. The condition may be caused by internal loops on\n\ sending events between state machines. |
ios-voice |
"This can be a severe error" |
|
CCH323-3-STRCALLHISFAIL |
3-Error |
\ncch323_store_call_history: [chars] |
Insert an active H323 call record into call history list failed |
ios-voice |
"No action is required" |
|
CCH323-6-CALL_PRESERVED |
6-Information |
[chars]: H.323 call preserved due to socket closure or error Call Id = [dec] fd = [dec] |
An H.225.0 or H.245 socket was closed due to a TCP FIN received from the remote endpoint or a socket error. Calls using these sockets for which call preservation was configured will be preserved. This is not an error but call preservation can occasionally cause hung calls. |
voice-h323 |
"Use \"show h323 calls preserved\" command to get a " "list of all active preserved calls. Long duration preserved calls can " "then be cleared using \"clear call voice\" command." |
|
CCH323-6-LONG_DUR_CALL_DETECTED |
6-Information |
Long Duration Call is detected [chars]\n |
The call is active for configured duration of long call |
ios-voice |
LOG_STD_ACTION |
|
CCH323-6-REGSTR |
6-Information |
Gateway [chars] registered with Gatekeeper [chars] |
Gateway registered with the Gatekeeper |
none |
"no action is required" |
|
CCK_QAT-3-INIT_FAIL |
3-Error |
[chars]: initialization failed [chars] |
CCK QAT initialization sequence failed. |
iosxe-ipsec |
"Copy the error message exactly as it appears and report it to your \n\ technical support representative." |
|
CCM-3-CCMINVALEVT |
3-Error |
Client[[dec]] received an invalid event[[dec]] |
Cluster Control Manager High Availability feature on standby detected an invalid event received from active |
ccm |
LOG_STD_ACTION |
|
CCM-3-CCMNOCLIENT |
3-Error |
Client [chars][[dec]] not present |
Cluster Control Manager High Availability features for this client will not work. |
ccm |
"Refer to the documentation on configuring High Availability features" |
|
CCM-3-CCMREGFAIL |
3-Error |
High Availability Registration failed |
Cluster Control Manager High Availability features will not work. |
ccm |
LOG_STD_ACTION |
|
CCPROXY-3-NO_CONNECT_TABLE |
3-Error |
\ Unable to allocate memory for [dec] connection table entries in [chars].\n |
- |
- |
- |
|
CCPROXY-3-NO_RASREQ_TABLE |
3-Error |
\ Unable to allocate memory for [dec] RAS request table entries in [chars].\n |
- |
- |
- |
|
CCPROXY-3-NOBLOCK_EVENT |
3-Error |
\ During initialization of proxy [chars]: cannot allocate event block\n |
- |
- |
- |
|
CCPROXY-3-NOCALL_ccIFInService |
3-Error |
\ No proxy CCAPI interface found: H.323 proxy bringup failed in [chars].\n |
- |
- |
- |
|
CCPROXY-3-NOCCAPI_INTERFACE |
3-Error |
\ CCAPI new interface is not created in [chars]\n |
- |
- |
- |
|
CCPROXY-3-NOCCB_FROM_CALLID |
3-Error |
\ No call-control-block is found in [chars] for [hec].\n |
- |
- |
- |
|
CCPROXY-3-NOINIT_OSS_h225 |
3-Error |
\ [chars]: initializing h225 socket failed through ASN.1 library: error=[dec]\n |
- |
- |
- |
|
CCPROXY-3-NOINIT_OSS_h245 |
3-Error |
\ [chars]: initializing h245 socket failed through ASN.1 library: error=[dec]\n |
- |
- |
- |
|
CCPROXY-3-NOMEMORY_FRAGMENT_CACHE |
3-Error |
\ [chars]: failed to allocate cache for fragmented packets for fastswitch |
- |
- |
- |
|
CCPROXY-3-NOMM_INTERFACE |
3-Error |
\ No multimedia interface configured in [chars].\n |
- |
- |
- |
|
CCPROXY-3-NOPROCESS_CCPROXY |
3-Error |
\ The proxy process is not created in [chars]\n |
- |
- |
- |
|
CCPROXY-3-STRCALLHISFAIL |
3-Error |
[chars]: Unable to store Call History record |
- |
- |
- |
|
CCPROXY-3-UNREGISTERED_BY_GK |
3-Error |
\ H.323 Proxy registration is being removed by Gatekeeper [chars]\n Check \show proxy h323 status\ for details. |
- |
- |
- |
|
CD_FFP_IPSEC_PROXY-2-FFP_INIT_FAILED |
2-Critical |
FFP Crypto device Proxy Agent initialization failure result: [dec]. |
Cisco internal software error. FFP Crypto device Procy Agent initialization detected critical failure. FFP Crypto device software library will not be functional while this condition exists. |
ffp-ipsec keyword:datapath |
LOG_STD_ACTION |
|
CD_FFP_IPSEC_PROXY-2-FFP_PROXY_INIT_FAILED |
2-Critical |
FFP Crypto device Procy Agent Proxy IPC interface initialization failure result: [dec]. |
Cisco internal software error. FFP Crypto device Procy Agent Proxy initialization detected that the IPC interface initialization failed. FFP Crypto device Procy Agent proxy will not be functional while this conidtion exists. |
ffp-ipsec keyword:datapath |
LOG_STD_ACTION |
|
CD_FFP_IPSEC_PROXY-3-ESG_IPSEC_KAT_TEST_FAILED |
3-Error |
Cryptographic Known-Answer Test failure result: [chars] |
Cisco internal software error. Cryptographic Known-Answer Tests. Error due to one of the Cryptographic Power-on Self-tests Known-Answer Tests not returning the expected value. |
esg-ipsec keyword:datapath |
LOG_STD_ACTION |
|
CD_FFP_IPSEC_PROXY-3-FFP_PROXY_IPSEC_SA_CRT_FAILED |
3-Error |
FFP Crypto device Procy Agent Proxy IPSec SA create failure result: [dec]. |
Cisco internal software error. FFP Crypto device Procy Agent Proxy message processing detected IPSec SA create failure. The request is rejected as the result of this condition. |
ffp-ipsec keyword:datapath |
LOG_STD_ACTION |
|
CD_SW_IPSEC_SHIM-2-KAT_TEST_FAILED |
2-Critical |
QFP Crypto device software library kat test failure result: [dec]. |
Cisco internal software error. QFP Crypto device software library detected critical failure. QFP Crypto device software library will not be functional while this condition exists. |
ultra-ipsec keyword:datapath |
LOG_STD_ACTION |
|
CD_SW_IPSEC_SHIM-2-SHIM_INIT_FAILED |
2-Critical |
QFP Crypto device software library initialization failure result: [dec]. |
Cisco internal software error. QFP Crypto device software library initialization detected critical failure. QFP Crypto device software library will not be functional while this condition exists. |
ultra-ipsec keyword:datapath |
LOG_STD_ACTION |
|
CD_SW_IPSEC_SHIM-2-SHIM_PROXY_INIT_FAILED |
2-Critical |
QFP Crypto device software library Proxy IPC interface initialization failure result: [dec]. |
Cisco internal software error. QFP Crypto device software library Proxy initialization detected that the IPC interface initialization failed. QFP Crypto device software library proxy will not be functional while this conidtion exists. |
ultra-ipsec keyword:datapath |
LOG_STD_ACTION |
|
CD_SW_IPSEC_SHIM-3-SHIM_PROXY_IPSEC_SA_CRT_FAILED |
3-Error |
QFP Crypto device software library Proxy IPSec SA create failure result: [dec]. |
Cisco internal software error. QFP Crypto device software library Proxy message processing detected IPSec SA create failure. The request is rejected as the result of this condition. |
ultra-ipsec keyword:datapath |
LOG_STD_ACTION |
|
CD_SW_SSL_SHIM-2-SHIM_INIT_FAILED |
2-Critical |
QFP Crypto device software library initialization failure result: [dec]. |
Cisco internal software error. QFP Crypto device software library initialization detected critical failure. QFP Crypto device software library will not be functional while this condition exists. |
ultra-ssl keyword:datapath |
LOG_STD_ACTION |
|
CD_SW_SSL_SHIM-2-SHIM_PROXY_INIT_FAILED |
2-Critical |
QFP Crypto device software library Proxy IPC interface initialization failure result: [dec]. |
Cisco internal software error. QFP Crypto device software library Proxy initialization detected that the IPC interface initialization failed. QFP Crypto device software library proxy will not be functional while this conidtion exists. |
ultra-ssl keyword:datapath |
LOG_STD_ACTION |
|
CD_SW_SSL_SHIM-3-SHIM_PROXY_SSL_CTX_ALLOC_FAILED |
3-Error |
QFP Crypto device software library Proxy IPSec CTX create failure result: [dec]. |
Cisco internal software error. QFP Crypto device software library Proxy message processing detected IPSec CTX create failure. The request is rejected as the result of this condition. |
ultra-ssl keyword:datapath |
LOG_STD_ACTION |
|
CDP_PD-2-POWER_LOW |
2-Critical |
[chars] - [chars] [chars] [enet] on port [chars] |
System is not supplied with its maximum power |
- |
"Reconfigure or replace the source of inline power to get maximum power." |
|
CDP_PD-4-POWER_OK |
4-Warning |
[chars] - [chars] inline power source on port [chars] |
System is supplied with sufficient power. |
- |
"No recommended action." |
|
CDP-3-CHUNK |
3-Error |
Chunk_malloc Failure |
chunk malloc failure |
cdp |
LOG_STD_ACTION |
|
CDP-4-DUPLEX_MISMATCH |
4-Warning |
duplex mismatch discovered on [chars] [chars] with [chars] [chars] [chars]. |
CDP discovered a mismatch of duplex configuration |
- |
"Configure the interfaces to the same duplex full or half." |
|
CDP-4-NATIVE_VLAN_MISMATCH |
4-Warning |
Native VLAN mismatch discovered on [chars] [dec] with [chars] [chars] [dec]. |
CDP discovered a mismatch of native-VLAN configuration |
- |
"Configure the interfaces to the same native VLAN." |
|
CDP-6-TLV_LIST_GLOBALLY |
6-Information |
Tlv-list [chars] [chars] globally on all interfaces. |
CDP Tlv-list configuration Globally. |
- |
"No action required. The message is informatory in nature." |
|
CDP-6-TLV_LIST_INTERFACE |
6-Information |
Tlv-list [chars] [chars] interface [chars] |
An IPv6 process could not be started. This machine will not be able to process any IPv6 packets. |
ipv6 |
"Reduce other system activity to ease memory demands. If conditions " "warrant upgrade to a larger memory configuration." |
|
CEF_PROXY-3-PROXY_IPC_ADJ_ID_HASH_FAILED |
3-Error |
- |
Getting Hash Address failed. |
cpp-ucode |
LOG_STD_ACTION |
|
CEF_PROXY-3-PROXY_IPC_ADJ_IDX_FAILED |
3-Error |
[hec] |
Failed to get adjacency index from IPC packet. |
cpp-ucode |
LOG_STD_ACTION |
|
CEF_PROXY-3-PROXY_IPC_INIT_FAILED |
3-Error |
[dec] |
IPC handler initialization failed. |
cpp-ucode |
LOG_STD_ACTION |
|
CEF_PROXY-3-PROXY_IPC_OCE_CHAIN_PTR_FAILED |
3-Error |
[hec] |
Null OCE Chain pointer. |
cpp-ucode |
LOG_STD_ACTION |
|
CEF_PROXY-3-PROXY_IPC_PACKET_ALLOCATION_FAILED |
3-Error |
[hec] |
Failed to allocate packet buffer for IPC |
cpp-ucode |
LOG_STD_ACTION |
|
CEF_PROXY-3-PROXY_IPC_PACKET_SEND_FAILED |
3-Error |
[hec] |
Failed to send IPC packet. |
cpp-ucode |
LOG_STD_ACTION |
|
CEF_PROXY-4-PROXY_IPC_INVALID_MSG |
4-Warning |
[hec] |
Received an invalid IPC messages subtype. |
cpp-ucode |
LOG_STD_ACTION |
|
CEF_SHIM_FIB-3-FIBTOPO |
3-Error |
Error for topology [dec]: [chars] |
CEF_SHIM_FIB_INTERNAL_ERROR |
CEF_SHIM_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CEF-3-CYLON_CEF_MAX_VRF_EXCEEDED |
3-Error |
Number of VRF instances already exceeded allowed limit [dec] |
Number of vrf instances exceeded supported platform scale |
firmware |
"Please reduce the number of vrf instances" "to scale to platform supported scale" |
|
CEF-3-KBP_PREFIX_IP_MPLS_LIMIT_EXCEEDED |
3-Error |
Number of ip mpls Prefixes exceeded allowed limit [dec] on asic [dec] |
Number of ip mpls Prefixes exceeded supported scale |
rsp3-infra |
"Please reduce the number of ip mpls Prefixes" "to scale to platform supported scale" |
|
CEF-3-KBP_PREFIX_IP_MPLS_LIMIT_EXCEEDED |
3-Error |
Number of ip mpls Prefixes exceeded allowed limit [dec] on asic [dec] |
Number of ip mpls Prefixes exceeded supported scale |
dominica-infra |
"Please reduce the number of ip mpls Prefixes" "to scale to platform supported scale" |
|
CEF-3-KBP_PREFIX_IPV6_LIMIT_EXCEEDED |
3-Error |
Number of ipv6 Prefixes exceeded allowed limit [dec] on asic [dec] |
Number of ipv6 Prefixes exceeded supported scale |
rsp3-infra |
"Please reduce the number of ipv6 Prefixes" "to scale to platform supported scale" |
|
CEF-3-KBP_PREFIX_IPV6_LIMIT_EXCEEDED |
3-Error |
Number of ipv6 Prefixes exceeded allowed limit [dec] on asic [dec] |
Number of ipv6 Prefixes exceeded supported scale |
dominica-infra |
"Please reduce the number of ipv6 Prefixes" "to scale to platform supported scale" |
|
CEF-3-NILE_CEF_MAX_VRF_EXCEEDED |
3-Error |
Number of VRF instances already exceeded allowed limit [dec] |
Number of vrf instances exceeded supported platform scale |
firmware |
"Please reduce the number of vrf instances" "to scale to platform supported scale" |
|
CEF-3-NILE_CEF_MAX_VRF_EXCEEDED |
3-Error |
Number of VRF instances exceeded allowed limit [dec] |
Number of vrf instances exceeded supported platform scale |
firmware |
"Please reduce the number of vrf instances" "to scale to platform supported scale" |
|
CEF-3-NILE_CEF_MAX_VRF_EXCEEDED |
3-Error |
Number of VRF instances exceeded allowed limit [dec] |
Number of vrf instances exceeded supported platform scale |
firmware |
"Please reduce the number of vrf instances" "to scale to platform supported scale" |
|
CELLWAN-1-POOL_INIT_FAIL |
1-Alert |
cellular pool init failed for subslot [dec]/[dec] \ pool name [chars] |
The NIM cellular pool init failed for this module. |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-2-BEARER_CONGESTION_OFF |
2-Critical |
Instance id=[dec] [chars] bearer bearer_id=[dec] QCI=[dec] in [chars] is NOT congested now |
Traffic congestion has cleared in the dedicated bearer |
- |
"No action is needed" |
|
CELLWAN-2-BEARER_CONGESTION_ON |
2-Critical |
Instance id=[dec] [chars] bearer bearer_id=[dec] QCI=[dec] in [chars] is congested |
Traffic congestion present in the dedicated bearer. If it does not clear make sure the host QOS configuration matches the dedicated bearer configuration |
- |
"Check the MBR of the dedicated bearer by doing show " "cellular and configure the host QOS configuration " "to match MBR of the dedicated bearer." |
|
CELLWAN-2-BEARER_DELETED |
2-Critical |
[chars] bearer bearer_id=[dec] in [chars] is now deleted. |
default/dedicated bearer has been deleted. |
- |
"Host QOS configuration may need to be deleted" " to match the modem configuration" |
|
CELLWAN-2-BEARER_DOWN |
2-Critical |
Instance id=[dec] [chars] bearer bearer_id=[dec] QCI=[dec] in [chars] is now down. |
default/dedicated bearer has been deleted. |
- |
"Host QOS configuration may need to be modified" " to match the modem configuration" |
|
CELLWAN-2-BEARER_MODIFIED |
2-Critical |
Instance id=[dec] [chars] bearer bearer_id=[dec] QCI=[dec] configuration in [chars] is modified |
default/dedicated bearer configuration has been modified. |
- |
"Check the TFT rules of the dedicated bearer by doing" " show cellular and configure the host QOS" " configuration to match the TFT rules" |
|
CELLWAN-2-BEARER_SUSPENDED |
2-Critical |
Instance id=[dec] [chars] bearer bearer_id=[dec] QCI=[dec] in [chars] |
default/dedicated bearer has been suspended. |
- |
"Host QOS configuration may need to be suspended" " to match the modem configuration" |
|
CELLWAN-2-BEARER_UP |
2-Critical |
Instance id=[dec] [chars] bearer bearer_id=[dec] QCI=[dec] in [chars] is now UP |
default/dedicated bearer has been added. |
- |
"Check the TFT rules of the dedicated bearer by doing show cellular" " and configure the host QOS configuration to match the TFT rules" |
|
CELLWAN-2-CALL_SETUP_FAIL |
2-Critical |
[chars] data call setup failed due to [chars]. |
Data call setup failed because the IP address configured under cellular interface does not match the IP address assigned by the network |
esg-lte |
"Please check the IP address configuration under cellular" "interface" |
|
CELLWAN-2-CRASHDUMP_SUCCESS |
2-Critical |
[chars]:Crashdump successfully logged in /bootflash/ |
Cellular Modem Crashdump files successfully logged to local flash. |
esg-lte |
"" |
|
CELLWAN-2-DEDICATED_BEARER_STATUS_UNKNOWN |
2-Critical |
Instance id=[dec] [chars] bearer bearer_id=[dec] QCI=[dec] configuration in [chars] is |
Dedicated bearer configuration status is unknown. |
- |
"Check the TFT rules of the dedicated bearer by doing" " show cellular and report the TFT rules to the " "carrier." |
|
CELLWAN-2-DMLOG_FILTER_FILE_OPEN_ERROR |
2-Critical |
[chars] failed to open [chars] to read DM log filter. |
Failed to open filter file from the location configured with 'gsm|cdma|lte modem dm-log filter' under cellular controller |
esg-lte |
"Please check that the path configured under cellular " "controller is reachable" |
|
CELLWAN-2-DMLOG_OUTPUT_FILE_OPEN_ERROR |
2-Critical |
[chars] failed to open [chars] to archive DM log files. |
Saving DM packets to file system failed. Output file URL configured with 'gsm|cdma|lte modem dm-log output path' under cellular controller can not be opened |
esg-lte |
"Please check that the path configured under cellular " "controller is reachable" |
|
CELLWAN-2-DMLOG_OUTPUT_SPACE_FULL |
2-Critical |
[chars] DM log file storage is full! |
Saving DM packets to file system failed because there is no more space left on the URL configured with 'gsm|cdma|lte modem dm-log output path' under cellular controller |
esg-lte |
"Please delete existing log files from the specified URL " "'gsm|cdma|lte modem dm-log output path' or upload them " "to the server then re-enable logging." |
|
CELLWAN-2-DMLOG_OUTPUT_WRITE_ERROR |
2-Critical |
[chars] failed to write [chars] DM packets to configured file system |
Saving DM packets to file system failed because of write error to the URL configured with 'gsm|cdma|lte modem dm-log output path' under cellular controller |
esg-lte |
"Please check that the URL configured under cellular " "controller with 'gsm|cdma|lte modem dm-log output path' " "is reachable and has enough storage space" |
|
CELLWAN-2-DYING_GASP_NOT_SUPPORTED |
2-Critical |
Dying Gasp Feature is not supported in Cellular slot [dec]/[dec] |
This NIM is not supporting Dying Gasp Feature. |
esg-lte |
"Please contact TAC for Dying Gasp Feature Supported NIM" |
|
CELLWAN-2-DYING_GASP_POWER_FAILURE |
2-Critical |
Dying Gasp SMS will not be sent out by Modem in slot [dec]/[dec] due to standby power failure. Please contact TAC. |
Modem doesn't have enough power to send Dying Gasp SMS |
esg-lte |
"Please contact TAC" |
|
CELLWAN-2-DYING_GASP_POWER_SUCCESS |
2-Critical |
Modem in slot [dec]/[dec] has sufficient power to send Dying Gasp SMS |
Modem has sufficient power to send Dying Gasp SMS |
esg-lte |
"No action is needed" |
|
CELLWAN-2-GSM_PROFILE_UNDEFINED |
2-Critical |
[[chars]]: Default profile [dec][chars] does not exist. Please execute 'cellular <unit> gsm profile create <profile #>' to create the profile. |
Default profile is undefined. the profile does not exist because it is not defined or is deleted. |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-2-HEART_BEAT_TIMEOUT |
2-Critical |
No heart beat signal from [chars] |
The cellular modem is not responding. |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-2-INTERFACE_GOING_DOWN |
2-Critical |
[chars] is being shutdown temporarily due to authentication failure for [dec] secs. |
The interface is being shutdown because the call could not be connected due to PPP authentication failures. The interface will be brought up after the specified time. This is to prevent frequent calls being attempted if authentication problems are not fixed. |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-2-LINK_RECOVERY |
2-Critical |
[chars]: Cellular Modem has been power cycled : [chars] |
Link Recovery Process has detected an inconsistent state of the modem |
- |
"" |
|
CELLWAN-2-MDM_LINK_FAILURE |
2-Critical |
[chars] direct IP synchronization process fails after [dec] attempts |
Direct IP synchronization fails to come up after maximum number of attempts. |
esg-lte |
"Contact customer service if the problem persists." |
|
CELLWAN-2-MICRO_DNLD_END_FAIL |
2-Critical |
\nModem returned following error to Download End Request:[chars] |
Modem Firmware Download End Request Failed |
esg-lte |
"show flash:<noCmdBold> command " "and <CmdBold>show controller cellular x/x/x all" |
|
CELLWAN-2-MICRO_DNLD_START_FAIL |
2-Critical |
\nModem returned following error to Download Start Request:[chars] |
Modem Firmware Download Start Request Failed. It generally means that firmware binary file is wrong. |
esg-lte |
"show flash:<noCmdBold> command " "and <CmdBold>show controller cellular x/x/x all" |
|
CELLWAN-2-MICRO_FLASH_PRGM_FAIL |
2-Critical |
\nModem returned following error to Flash Program Request:[chars] |
Modem failed to launch the new firmware. |
esg-lte |
"show flash:<noCmdBold> command " "and <CmdBold>show controller cellular x/x/x all" |
|
CELLWAN-2-MICRO_FW_DNLD_FAIL |
2-Critical |
\nModem returned following error to Download Request:[chars] |
Modem Firmware Download Continue Request Failed. It generally means that firmware binary file is corrupt. |
esg-lte |
"show flash:<noCmdBold> command " "and <CmdBold>show controller cellular x/x/x all" |
|
CELLWAN-2-MODEM_DOWN |
2-Critical |
Modem in slot [dec]/[dec] is DOWN |
The cellular modem is not operational. |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-2-MODEM_INIT_TIMEOUT |
2-Critical |
Cellular modem initialization timeout for [chars] |
Modem failed to initialize. |
esg-lte |
LOG_STD_SH_TECH_ACTION |
|
CELLWAN-2-MODEM_NOT_ACTIVATED |
2-Critical |
[chars] modem has not been activated |
The cellular modem has not been activated by the cellular provider. |
esg-lte |
"Please check the user documentation on how to activate the modem. " "The cellular modem needs to be activated before it can be used on " "a cellular network." |
|
CELLWAN-2-MODEM_RADIO |
2-Critical |
[chars] Modem radio has been turned [chars] |
Modem radio has been turned on/off. |
esg-lte |
"show cellular x/x/x radio command " "and <CmdBold>show tech-support" |
|
CELLWAN-2-MODEM_TIMEOUT |
2-Critical |
Modem in [chars] not responding |
The cellular modem is not responding. |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-2-MODEM_TOO_HOT |
2-Critical |
[chars] modem will be [chars] |
Modem radio temperature has reached critical point. The call will be disconnected and the modem could be shutdown. |
esg-lte |
"Check if the router fans are working properly." |
|
CELLWAN-2-MODEM_UP |
2-Critical |
Modem in slot [dec]/[dec] is now UP |
The cellular modem is now UP. |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-2-NC_EVENT1 |
2-Critical |
[chars]: Network change event - fallback from ENDC to LTE. |
Modem fallback from ENDC to LTE |
esg-lte |
"No action" |
|
CELLWAN-2-NC_EVENT2 |
2-Critical |
[chars]: Network change event - activated 4G Carrier Aggregation. |
Modem activated 4G Carrier Aggregation |
esg-lte |
"No action" |
|
CELLWAN-2-NC_EVENT3 |
2-Critical |
[chars]: Network change event - activated 5G ENDC. |
Modem activated 5G ENDC |
esg-lte |
"No action" |
|
CELLWAN-2-NO_PROCESS |
2-Critical |
Could not start process [chars] |
Could not start one of the processes. |
esg-lte |
"Add more memory." |
|
CELLWAN-2-OMA_DM_ACTIVE |
2-Critical |
[[chars]]: OMA DM [chars] session is active |
OMA DM session state is received by modem |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-2-OMA_DM_ERROR |
2-Critical |
[[chars]]: OMA DM [chars] Failed - Error:0x[hec][chars] |
OMA DM session state is received by modem |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-2-OMA_DM_HFA_PENDING |
2-Critical |
[[chars]]: OMA DM [chars] waiting for retry in [dec] seconds |
OMA DM session state is received by modem |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-2-OMA_DM_NI_ALERT |
2-Critical |
[[chars]]: OMA DM NI Alert is received for [chars] \nPlease execute 'cellular <unit> cdma activate oma-dm ni-alert [allow | deny]' |
OMA DM Network-Initiated alert is received by modem |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-2-OMA_DM_NO_OP |
2-Critical |
[[chars]]: OMA DM [chars] could not be completed. \nPlease try again later. If the problem persists you may need to contact Customer Service. |
OMA DM session state is received by modem |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-2-OMA_DM_NO_PRL |
2-Critical |
[[chars]]: OMA DM - No PRL update available |
OMA DM session state is received by modem |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-2-OMA_DM_SUCCESS |
2-Critical |
[[chars]]: OMA DM [chars] completed successfully |
OMA DM session state is received by modem |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-2-POWER_SAVE_MODE |
2-Critical |
[[chars]]: is in Power save mode. Command ignored. |
radio is currently OFF on this NIM |
esg-lte |
LOG_STD_ACTION |
|
CELLWAN-2-QOS_ENABLED |
2-Critical |
QoS Feature in [chars] is now activated |
QoS Feature is now enabled and activated in the modem. |
- |
"QoS Feature is now enabled and activated in the modem." |
|
CELLWAN-2-QOS_NW_STATUS |
2-Critical |
Network status for QoS feature is [chars] in [chars]. |
Network status for QoS feature is either enabled or disabled by the carrier. |
- |
"check with carrier if you expect QoS feature but it is disabled" |
|
CELLWAN-2-QOS_PRI_EVENT_STATUS |
2-Critical |
QoS Event Status = [dec] for default bearer in [chars] in [chars]. |
QoS Event Status for default bearer for the cellular interface. |
- |
"check with carrier to see if the default bearer" " config is changed" |
|
CELLWAN-2-SEND_TIMEOUT |
2-Critical |
[chars] not responding |
The cellular modem is not responding. |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-2-SIM_CHV1_BLOCKED |
2-Critical |
[[chars]]: SIM is blocked. PUK is required to unblock the SIM [chars] |
SIM is blocked and no data call can be made until it is unblocked using PUK. |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-2-SIM_CHV1_CONFIG_REMOVED |
2-Critical |
[[chars]]: CHV1 verfication failed [chars] : Incorrect PIN configured. Erased the CHV1 code from router runnning configuration to avoid SIM blocking during modem reset/powercycle. \n!!!WARNING: If the incorrect PIN is saved in router start-up configuration please remove it manually to avoid SIM blocking during router reload |
SIM CHV1 verfication failed. Incorrect PIN configured. |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-2-SIM_FAILURE |
2-Critical |
[[chars]]: SIM read failed [chars] |
If the SIM is not present insert SIM in the SIM socket. If error still persists SIM needs to be replaced. |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-2-SIM_LOCKED |
2-Critical |
[[chars]]: SIM is locked [chars] |
SIM is locked and no data call can be made till it is unlocked. |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-2-SIM_MEP_LOCKED |
2-Critical |
[[chars]]: Invalid SIM or device locked to carrier [chars] |
Invalid SIM or device locked to carrier |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-2-SIM_NOT_PRESENT |
2-Critical |
[[chars]]: SIM is not present in Slot [dec] |
SIM has not been detected in the NIM SIM socket |
esg-lte |
"Insert a valid sim in the NIM SIM socket." |
|
CELLWAN-2-SIM_NOT_READY |
2-Critical |
[chars] Modem is not ready. SIM status may be not current. |
SIM access cannot be granted or may return an error when : 1 The modem is not up or during a reset. |
esg-lte |
"1 Wait till MODEM UP message is seen from the console before accessing SIM." |
|
CELLWAN-2-SIM_REJECTED |
2-Critical |
[[chars]]: SIM rejected by the network [chars] |
The SIM is not valid to be used in the network. A new valid SIM needs to be inserted in the SIM socket. |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-2-SIM_SECURITY_SHUTDOWN |
2-Critical |
[[chars]]: CHV1 PIN is configured while SIM is unlocked [chars]. Shutting down all PDP interfaces |
CHV1 is configured while SIM is unlocked The SIM is not valid to be used in the network. A new valid locked SIM needs to be inserted in the SIM socket. |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-2-SIM_SWITCH_FAILURE |
2-Critical |
[[chars]]: Failed to switch to SIM slot [dec] !! |
Failed to switch to the requested NIM SIM slot |
esg-lte |
"Examine SIM in the indicated slot" |
|
CELLWAN-2-SMS_ARCH_PATH_UNCONFIGURED |
2-Critical |
[chars] failed to archive SMS because 'gsm|cdma|lte sms archive path' under cellular controller is not configured. |
'gsm|cdma|lte sms archive path' under cellular controller must be configured first before background incoming text message archive can function properly |
esg-lte |
"Configure 'gsm|cdma|lte sms archive path' under cellular controller" |
|
CELLWAN-2-SMS_INBOX_ARCH_OPEN_ERROR |
2-Critical |
[chars] failed to open [chars] to archive incoming SMS. |
Incoming text messages archive to FTP server failed because the FTP URL configured with 'gsm|cdma|lte sms archive path' under cellular controller can not be opened |
esg-lte |
"Please check that the FTP server configured under cellular " "controller is reachable and that the directory exists" |
|
CELLWAN-2-SMS_INBOX_ARCH_WRITE_ERROR |
2-Critical |
[chars] failed to write [chars] to archive incoming SMS. |
Incoming text messages archive to FTP server failed because of write error to the FTP URL configured with 'gsm|cdma|lte sms archive path' under cellular controller |
esg-lte |
"Please check that the FTP server configured under cellular " "controller with 'gsm|cdma|lte sms archive path' is reachable and " "has enough storage space" |
|
CELLWAN-2-SMS_OUTBOX_ARCH_OPEN_ERROR |
2-Critical |
[chars] failed to open [chars] to archive an outgoing SMS. |
Outgoing text message archive to FTP server failed because the FTP URL configured with 'gsm|cdma|lte sms archive path' under cellular controller can not be opened |
esg-lte |
"Please check that the FTP server configured under cellular " "controller is reachable and that the directory exists" |
|
CELLWAN-2-SMS_OUTBOX_ARCH_WRITE_ERROR |
2-Critical |
[chars] failed to write [chars] to archive an outgoing SMS. |
Outgoing text message archive to FTP server failed because of write error to the FTP URL configured with 'gsm|cdma|lte sms archive path' under cellular controller |
esg-lte |
"Please check that the FTP server configured under cellular " "controller with 'gsm|cdma|lte sms archive path' is reachable and " "has enough storage space" |
|
CELLWAN-2-SVBLOG_OUTPUT_FILE_OPEN_ERROR |
2-Critical |
[chars] failed to open [chars] to archive SVB log files. |
Saving SVB packets to file system failed. Output file URL configured with 'gsm|cdma|lte modem dm-log output path' under cellular controller can not be opened |
esg-lte |
"Please check that the path configured under cellular " "controller is reachable" |
|
CELLWAN-2-SVBLOG_OUTPUT_SPACE_FULL |
2-Critical |
[chars] SVB log file storage is full! |
Saving SVB packets to file system failed because there is no more space left on the URL configured with 'gsm|cdma|lte modem dm-log output path' under cellular controller |
esg-lte |
"Please delete existing log files from the specified URL " "'gsm|cdma|lte modem dm-log output path' or upload them " "to the server then re-enable logging." |
|
CELLWAN-2-SVBLOG_OUTPUT_WRITE_ERROR |
2-Critical |
[chars] failed to write [chars] SVB packets to configured file system |
Saving SVB packets to file system failed because of write error to the URL configured with 'gsm|cdma|lte modem dm-log output path' under cellular controller |
esg-lte |
"Please check that the URL configured under cellular " "controller with 'gsm|cdma|lte modem dm-log output path' " "is reachable and has enough storage space" |
|
CELLWAN-2-UNSUPPORTED_CELLULAR_NIM |
2-Critical |
Unsupported Cellular NIM inserted in slot [dec]/[dec] |
This NIM is not supported for the current software release |
esg-lte |
"Please contact TAC for supported software release for this NIM" |
|
CELLWAN-2-WCDMA_ALL_BAND_UNDEFINED |
2-Critical |
[[chars]]: wcdma-all band not supported |
wcdma-all band is not supported by modem or not defined |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-3-GPS_FAIL_END_SESSION |
3-Error |
[[chars]] GPS failed to end location fix session - [chars] [0x[hec]] please try again |
Modem failed to disable GPS mode due to error indicated. Fix that error and try again. |
esg-lte |
"Fix error indicated and try disabling GPS again." |
|
CELLWAN-3-GPS_FAIL_START_TRACK |
3-Error |
[[chars]] GPS failed to start tracking - [chars] [0x[hec]] please try again |
Modem failed to enable GPS mode due to error indicated. Fix that error and try again. |
esg-lte |
"Fix error indicated and try enabling GPS again." |
|
CELLWAN-3-GSM_PROFILE_CREATION_FAILURE |
3-Error |
[[chars]] GSM profile creation fails - [chars] [0x[hec]] please try again |
Modem failed to create the GSM profile due to error indicated. Fix that error and try again. |
esg-lte |
"Fix error indicated and try creating GSM profile again." |
|
CELLWAN-4-CELLULAR_FW_UNSUPPORTED |
4-Warning |
[chars]: Unsupported or older modem firmware [chars] detected please upgrade modem to supported firmware of at least [chars] |
The current firmware on specified cellular interface is not supported. Any actions and errors that occur will not be supported until the fw is upgraded to at least the version requested |
esg-lte |
"Please upgrade to the latest FW from online using" " 'microcode reload'" |
|
CELLWAN-4-CELLULAR_MODEM_SKU_MISMATCH |
4-Warning |
[chars]: Mismatch detected between installed modem [chars][SKU ID [chars]] on SKU type [chars]. Expected modem for this SKU is [chars][SKU ID [chars]] |
Incorrect modem type has been installed on this SKU. Any actions and issues caused by it will not be supported |
esg-lte |
"Please contact the cisco customer service" "to replace the card" |
|
CELLWAN-4-DG_DETACH_CONFIG_FAILED |
4-Warning |
Dying Gasp Detach Configuration Failed. [chars] |
Dying Gasp Detach Configuration Failed. |
- |
"Please try Dying Gasp Detach Configuration later" |
|
CELLWAN-4-DG_SMS_CONFIG_FAILED |
4-Warning |
Dying Gasp SMS Configuration Failed. [chars] |
Dying Gasp SMS Configuration Failed. |
- |
"Please try Dying Gasp SMS Configuration later" |
|
CELLWAN-4-MANUAL_PLMN_SELECTION_FAILED |
4-Warning |
Manual/Force PLMN Selection Failed. [chars] |
Manual/Force PLMN Selection Failed |
- |
"Please use Different PLMN or check number of MNC Bits " "in PLMN Selection" |
|
CELLWAN-4-MODEM_COMM_FAIL |
4-Warning |
Communication between Modem and IOS failed: [chars] |
Communication between Modem and IOS Failed |
- |
" Modem Reset will recover " |
|
CELLWAN-4-MODEM_RESTART_IND |
4-Warning |
[chars] Modem restart [chars] |
Modem Restart Indication |
- |
"No action is needed" |
|
CELLWAN-4-OUTGOING_SMS_ERROR |
4-Warning |
[chars] failed to send an outgoing SMS. |
Outgoing text message failed to send from cellular interface |
esg-lte |
"Please do 'show cellular <unit> sms' to see " "error code" |
|
CELLWAN-4-OUTGOING_SMS_SERV_UNAVAIL |
4-Warning |
[chars] can't send an SMS because SMS service is not available. |
Text message service is not available on specified cellular interface |
esg-lte |
"Check modem is powered up radio is not in power " "saving mode and SIM is inserted" |
|
CELLWAN-5-DMLOG_AUTOSTOP_TIMER_CANCEL |
5-Notice |
[chars]: DM logging autostop timer canceled |
DM logging autostop timer is canceled |
esg-lte |
LOG_STD_NO_ACTION |
|
CELLWAN-5-DMLOG_AUTOSTOP_TIMER_EXPIRY |
5-Notice |
[chars]: DM logging stopped |
DM logging is stopped due to autostop trigger timer expiry |
esg-lte |
LOG_STD_NO_ACTION |
|
CELLWAN-5-DMLOG_AUTOSTOP_TRIGGER |
5-Notice |
[chars]: DM logging will be stopped in [dec] [chars] autostop trigger event [chars] set |
DM log autostop trigger event configured DM logging will be stopped after the timer expiry |
esg-lte |
LOG_STD_NO_ACTION |
|
CELLWAN-5-DMLOG_DISABLE_OIR |
5-Notice |
[chars]: OIR Detected. DM logging stopped |
DM logging is stopped due to OIR |
esg-lte |
LOG_STD_NO_ACTION |
|
CELLWAN-5-DMLOG_DISPLAY_OUTPUT_PATH_EXTERN |
5-Notice |
DM log output path = bootflash:/core/modules |
DM log output path set to bootflash:/core/modules |
esg-lte |
"" |
|
CELLWAN-5-DMLOG_DISPLAY_OUTPUT_PATH_INTEGRATED |
5-Notice |
DM log output path = bootflash: |
DM log output path set to bootflash:/ |
esg-lte |
"" |
|
CELLWAN-5-FIRMWARE_SWITCH |
5-Notice |
Firmware switchover initiated for modem in slot [dec]/[dec] |
Firmware switchover caused by user request. |
esg-lte |
LOG_STD_NO_ACTION |
|
CELLWAN-5-INCOMING_SMS |
5-Notice |
[chars] has just received new incoming SMS. |
New incoming text messages arrived at cellular interface |
esg-lte |
"Please do 'cellular <unit> gsm|cdma sms view' to read SMS" |
|
CELLWAN-5-MNO_SWITCH |
5-Notice |
MNO switchover initiated for modem in slot [dec]/[dec] |
MNO switchover caused by user request. |
esg-lte |
LOG_STD_NO_ACTION |
|
CELLWAN-5-MODEM_BOOT_READY |
5-Notice |
Modem in slot [dec]/[dec] is in Boot Ready Mode.. Please perform FW upgrade |
The cellular modem is not operational. |
esg-lte |
"show cellular x/x/x all<noCmdBold> command " "and <CmdBold>show tech-support" |
|
CELLWAN-5-NULL_BEARER |
5-Notice |
NULL Bearer Timer [chars]:Current NULL Bearer count:[dec]:Total NULL Bearer count:[dec]:Profile id:[dec]:PDN ID:[dec] |
NULL Bearer notification from modem. No action is required |
esg-lte |
LOG_STD_NO_ACTION |
|
CELLWAN-5-OUTGOING_SMS_SENT |
5-Notice |
[chars] has just sent an outgoing SMS successfully. |
Outgoing text message was sent successfully from cellular interface |
esg-lte |
LOG_STD_NO_ACTION |
|
CELLWAN-5-SIM_ACQUISITION_TIMEOUT |
5-Notice |
[[chars]]: SIM slot [dec] Acquisition Timer timeout !! |
Timeout on the SIM slot acquisition timer initiate sim switching request to the alter SIM slot |
esg-lte |
LOG_STD_NO_ACTION |
|
CELLWAN-5-SIM_ACTIVATION |
5-Notice |
[[chars]]: SIM slot [dec] is being activated !! |
The request to activate the indicated SIM slot has been sent to the modem |
esg-lte |
LOG_STD_NO_ACTION |
|
CELLWAN-5-SIM_ACTIVATION_TIMEOUT |
5-Notice |
[[chars]]: SIM slot [dec] activation request timeout !! |
Timeout on the request sent to the modem to activate the indicated SIM slot |
esg-lte |
LOG_STD_NO_ACTION |
|
CELLWAN-5-SIM_ACTIVE |
5-Notice |
[[chars]]: SIM slot [dec] is Active !! |
The indicated SIM slot is active. |
esg-lte |
LOG_STD_NO_ACTION |
|
CELLWAN-5-SIM_DETECT_COMPLETE |
5-Notice |
[[chars]]: SIM presence detection has completed !! |
SIM presence detection has completed |
esg-lte |
LOG_STD_NO_ACTION |
|
CELLWAN-5-SIM_DETECT_START |
5-Notice |
[[chars]]: SIM presence detection starts !! |
SIM presence detection has started |
esg-lte |
LOG_STD_NO_ACTION |
|
CELLWAN-5-SIM_FAILOVER_TIMEOUT |
5-Notice |
[[chars]]: SIM slot [dec] Failover Timer timeout !! |
Timeout on the SIM slot failover timer initiate sim switching request to the alter SIM slot |
esg-lte |
LOG_STD_NO_ACTION |
|
CELLWAN-5-SMS_INBOX_ARCH_DONE |
5-Notice |
[chars] has just archived all incoming SMS to FTP server successfully. |
Incoming text messages were archived to FTP server successfully from cellular interface |
esg-lte |
LOG_STD_NO_ACTION |
|
CELLWAN-5-SMS_INBOX_MSG_ARCH_DONE |
5-Notice |
[chars] has just archived an incoming SMS to FTP server successfully. |
An incoming text message was archived to FTP server successfully from cellular interface |
esg-lte |
LOG_STD_NO_ACTION |
|
CELLWAN-5-SMS_OUTBOX_ARCH_DONE |
5-Notice |
[chars] has just archived an outgoing SMS to FTP server successfully. |
An outgoing text message was archived to FTP server successfully from cellular interface |
esg-lte |
LOG_STD_NO_ACTION |
|
CELLWAN-5-SMS_SERVICE_AVAILABLE |
5-Notice |
[chars] SMS service is now available. |
You can send and receive text messages on this cellular interface |
esg-lte |
LOG_STD_NO_ACTION |
|
CELLWAN-5-SMS_SERVICE_UNAVAILABLE |
5-Notice |
[chars] SMS service is now unavailable. |
You can not send and receive text messages on this cellular interface |
esg-lte |
LOG_STD_NO_ACTION |
|
CELLWAN-5-SVBLOG_AUTOSTOP_TIMER_CANCEL |
5-Notice |
[chars]: SVB logging autostop timer canceled |
SVB logging autostop timer is canceled |
esg-lte |
LOG_STD_NO_ACTION |
|
CELLWAN-5-SVBLOG_AUTOSTOP_TIMER_EXPIRY |
5-Notice |
[chars]: SVB logging stopped |
SVB logging is stopped due to autostop trigger timer expiry |
esg-lte |
LOG_STD_NO_ACTION |
|
CELLWAN-5-SVBLOG_AUTOSTOP_TRIGGER |
5-Notice |
[chars]: SVB logging will be stopped in [dec] minutes autostop trigger event [chars] set |
SVB log autostop trigger event configured SVB logging will be stopped after the timer expiry |
esg-lte |
LOG_STD_NO_ACTION |
|
CELLWAN-6-CELLULAR_BACKOFF_START |
6-Information |
[chars]: Cellular back-off has started on PDN [dec] |
Back off has started because of certain error codes from network side |
- |
"" |
|
CELLWAN-6-CELLULAR_BACKOFF_STOP |
6-Information |
[chars]: Cellular back-off has stopped on PDN [dec] |
Back off has stopped |
- |
"" |
|
CELLWAN-6-CELLULAR_NETWORK_ATTACH_FAILURE |
6-Information |
[chars]: Cellualr network attachment failure. Reject Cause [dec] [chars]. |
Network attachment failure |
- |
"Check 3GPP Table 10.5.95/3GPP TS 24.008 for information" |
|
CELLWAN-6-FOTA_DNLD_COMPLETE |
6-Information |
[[chars]]: Firmware has been downloaded for modem in cellular slot [dec]/[dec] |
FOTA Cellular modem firmware download started. |
esg-lte |
"" |
|
CELLWAN-6-FOTA_DNLD_STARTED |
6-Information |
[[chars]]: Firmware download started in cellular slot [dec]/[dec] |
FOTA Cellular modem firmware download started. |
esg-lte |
"" |
|
CELLWAN-6-FOTA_UPGRADE_STARTED |
6-Information |
[[chars]]: Firmware upgrade started in cellular slot [dec]/[dec]. Modem will reset and come up with new firmware. |
FOTA Cellular modem firmware upgraded started. |
esg-lte |
"" |
|
CELLWAN-6-FOTA_UPGRADE_SUCESS |
6-Information |
[[chars]]: Firmware upgrade successful in cellular slot [dec]/[dec] |
FOTA Cellular modem firmware upgraded successfully. |
esg-lte |
"" |
|
CELLWAN-6-FOTA_UPGRADE_TIMEOUT |
6-Information |
[[chars]]: Firmware upgrade timed out in cellular slot [dec]/[dec] |
FOTA Cellular modem firmware upgrade timed out. |
esg-lte |
"" |
|
CELLWAN-6-SIM_INSERTED |
6-Information |
[[chars]]: SIM in slot [dec] has been \n\ inserted |
SIM is inserted to the slot. |
esg-lte |
"No action" |
|
CELLWAN-6-SIM_PRESENT |
6-Information |
[[chars]]: SIM is present in Slot [dec] |
SIM has been detected in the SIM socket |
esg-lte |
"No action" |
|
CELLWAN-6-SIM_REMOVED |
6-Information |
[[chars]]: WARNING: SIM in slot [dec] has \n\ been removed |
SIM is removed from the slot. |
esg-lte |
"No action" |
|
CEM-1-ISSU_NOMEMORY |
1-Alert |
msgtxt_nomemory |
The requested operation could not be accomplished because of a low\n\ memory condition. |
cemcommon |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
CEM-3-ISSU_SENDFAILED |
3-Error |
\nCEM ISSU: send message failed rc = [dec]\n |
The sending of a message has failed. |
cemcommon |
LOG_STD_SH_TECH_ACTION |
|
CEM-4-ISSU_INCOMPATIBLE |
4-Warning |
\ncem-issu-compat: returned FALSE |
The compatibility checking has failed |
cemcommon |
LOG_STD_SH_TECH_ACTION |
|
CEM-4-ISSU_XFORM |
4-Warning |
\n[chars]: failed rc=[chars] |
The transform has failed. |
cemcommon |
LOG_STD_SH_TECH_ACTION |
|
CEMA-3-ATM_VC_CONFIG_FAIL |
3-Error |
[chars]: connection configuration failed for VC [dec]/[dec] [chars] |
A failure occurred when sending a VC configuration command. |
- |
CEMA_CMD_FAIL_ACTION |
|
CEMA-3-ATM_VP_CONFIG_FAIL |
3-Error |
[chars]: connection configuration failed for VP [dec] [chars] |
A failure occurred when sending a VP configuration command. |
- |
CEMA_CMD_FAIL_ACTION |
|
CEMA-3-CARD_TYPE_CONFIG_FAIL |
3-Error |
[chars]: card type configuration failed [chars] |
A failure occurred when sending a card type configuration command. |
- |
CEMA_CMD_FAIL_ACTION |
|
CEMA-3-CEMA_ADD_FAIL |
3-Error |
[chars]: CEMA SB addition failed for interface [chars] |
A failure occurred when adding cema_sb to the interface shown in the error message. |
- |
SPA_CEMA_FAIL_ACTION |
|
CEMA-3-CLEAR_CONNECTION_STATS_FAIL |
3-Error |
[chars]: clear connection stats failed [chars] |
A failure occurred when sending a clear connection stats command. |
- |
CEMA_CMD_FAIL_ACTION |
|
CEMA-3-CLEAR_INTERFACE_STATS_FAIL |
3-Error |
[chars]: clear interface stats failed [chars] |
A failure occurred when sending a clear interface stats command. |
- |
CEMA_CMD_FAIL_ACTION |
|
CEMA-3-CONNECTION_DELETE_FAIL |
3-Error |
[chars]: connection delete failed [chars] |
A failure occurred when sending a connection delete command. |
- |
CEMA_CMD_FAIL_ACTION |
|
CEMA-3-INTERFACE_CONFIG_FAIL |
3-Error |
[chars]: interface configuration failed [chars] |
A failure occurred when sending an interface delete command. |
- |
CEMA_CMD_FAIL_ACTION |
|
CEMA-3-INTERFACE_DELETE_FAIL |
3-Error |
[chars]: interface delete failed [chars] |
A failure occurred when sending an interface delete command. |
- |
CEMA_CMD_FAIL_ACTION |
|
CEMOUDP_NP_CLIENT-3-INFO |
3-Error |
[chars] |
CEMOUDP NP Client failed to initialize properly which will result in\n\ improper operation of cemoudp feature |
vsp-mid |
"Try to reload the IOS image on the affected card or platform. If the\n\ error persists record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
CEMOUDP_NP_CLIENT-3-NOMEM |
3-Error |
[chars] |
CEMOUDP NP Client failed to initialize properly which will result in\n\ improper operation of cemoudp feature |
vsp-mid |
"This error may indicate that more memory must be installed on the\n\ affected card or platform in order to service all the features and\n\ related entities enabled via the configuration.\n\\n\ Try to reload the IOS image on the affected card or platform. If the\n\ error persists record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
CEMOUDP_NP_CLIENT-4-WARN |
4-Warning |
[chars] [dec] [chars] |
CEMOUDP Entry could not be added because:\n\ 1. Entry passed is invalid. |
vsp-mid |
"Try to reload the IOS image on the affected card or platform. If the\n\ error persists record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
CENT-2-IPC_INIT |
2-Critical |
IPC message handler registration failure rc [dec] |
Registering an IPC message handler for the CENT feature failed. This will cause the feature to not function. |
qfp-cent |
"This is normally a software issue. " "The consequences are that the CENT feature will not function. " LOG_STD_ACTION |
|
CENT-3-CENT_RC_AT_FO_OVERWRITE |
3-Error |
FO overwritten detected: magic [hec] table_id [hec] next_hop [hec] |
Cisco internal software error. The dataplane was unable to complete enqueuing a packet. This is likely due to a data initialization error |
cpp-ucode keyword:cent |
LOG_STD_ACTION |
|
CENT-3-IPC_NORES |
3-Error |
No space for the IPC reply size [dec] |
For a request from upper CENT software stack layers it was not possible to allocate space for a reply for the specified size. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation. |
qfp-cent |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
CENT-3-IPC_OPEN_REPLY |
3-Error |
IPC Open Reply failed request [dec] |
For a request from upper CENT software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation. |
qfp-cent |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
CERF-2-ABORT |
2-Critical |
[chars] |
This message is emitted when a cache error has occured but an attempt\n\ to recover has been aborted |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CERF-3-RECOVER |
3-Error |
[chars] |
This message is emitted when there has been a full recovery after a\n\ cache error |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CERM_DP-4-DP_RX_BW_LIMIT |
4-Warning |
Maximum Rx Bandwidth limit of [dec] Kbps reached for Crypto functionality \ with securityk9 technology package license. |
Maximum Rx Bandwidth limit reached for Crypto functionality with \ securityk9 technology package license. |
esg-ipsec |
"Obtain 'hseck9' feature license and install it." |
|
CERM_DP-4-DP_TX_BW_LIMIT |
4-Warning |
Maximum Tx Bandwidth limit of [dec] Kbps reached for Crypto functionality \ with securityk9 technology package license. |
Maximum Tx Bandwidth limit reached for Crypto functionality with \ securityk9 technology package license. |
esg-ipsec |
"Obtain 'hseck9' feature license and install it." |
|
CERM_DP-4-SSLVPN_DP_RX_BW_LIMIT |
4-Warning |
Maximum TLS Rx Bandwidth limit of [dec] Kbps reached. |
Maximum TLS Rx Bandwidth limit reached for Crypto functionality. |
qfp-sslvpn |
"" |
|
CERM_DP-4-SSLVPN_DP_TX_BW_LIMIT |
4-Warning |
Maximum TLS Tx Bandwidth limit of [dec] Kbps reached. |
Maximum TLS Tx Bandwidth limit reached for Crypto functionality. |
qfp-sslvpn |
"" |
|
CERM-4-RX_BW_LIMIT |
4-Warning |
Maximum Rx Bandwidth limit of [dec] Kbps reached for Crypto functionality \ with securityk9 technology package license. |
Maximum Rx Bandwidth limit reached for Crypto functionality with \ securityk9 technology package license. |
c2900 |
"Obtain 'hseck9' feature license and install it." |
|
CERM-4-TLS_SESSION_LIMIT |
4-Warning |
Maximum TLS session limit of [dec] reached for Crypto functionality with \ securityk9 technology package license. |
Maximum TLS session limit reached for Crypto functionality with \ securityk9 technology package license. |
c2900 |
"Obtain 'hseck9' feature license and install it." |
|
CERM-4-TUNNEL_LIMIT |
4-Warning |
Maximum tunnel limit of [dec] reached for Crypto functionality with \ securityk9 technology package license. |
Maximum tunnel limit reached for Crypto functionality with securityk9 \ technology package license. |
c2900 |
"Obtain 'hseck9' feature license and install it." |
|
CERM-4-TX_BW_LIMIT |
4-Warning |
Maximum Tx Bandwidth limit of [dec] Kbps reached for Crypto functionality \ with securityk9 technology package license. |
Maximum Tx Bandwidth limit reached for Crypto functionality with \ securityk9 technology package license. |
c2900 |
"Obtain 'hseck9' feature license and install it." |
|
CES-2-INTERNAL_CRITICAL |
2-Critical |
[chars] |
The CES subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
CES-3-INTERNAL_ERROR |
3-Error |
[chars] |
The CES subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
CES-4-INTERNAL_WARNING |
4-Warning |
[chars] |
The CES subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
CF_REGISTER_FAILED-3-MPLS_TE_HA |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
CFC_LISP-3-ADJ |
3-Error |
Request to [chars] adjacency [chars][chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-ADJ_SEQ |
3-Error |
Adjacency [chars] is still complete after interface shutdown |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-ALLOCATEFAIL |
3-Error |
Failed to allocate memory for [chars] |
An internal software error occurred. This is probably because not enough memory was available. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-BG_PROCESS |
3-Error |
Background process failed to [chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-DECAP_OCE |
3-Error |
Failed to [chars] LISP decapsulation OCE: [chars][chars] |
An operation dealing with a LISP decapsulation OCE encountered an error. The error message will indicate which operation failed and the address-family context. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-DEP_ELEM |
3-Error |
Request to [chars] dependency [chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-DEPRECATED_API |
3-Error |
Use of a deprecated API [chars][chars] |
- |
CFC_LISP_MSG_DDTS_COMP |
"Increase the MTU of the path to the remote RLOC" |
|
CFC_LISP-3-DYN_EID_IP_ADDR_CONFLICT |
3-Error |
Ignore dynamic EID detection due to IP Address conflict [chars]:[chars] on [chars] |
A dynamic EID Host attempted to register with an IP address conflicting with the XTR gateway. Refer to error message log for more details. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-ELIG_OCE |
3-Error |
Failed to [chars] LISP eligibility oce [chars][chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-FREE_WITH_DEPS |
3-Error |
Request to remove dependency sb on [chars] with dependents |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-GSMR |
3-Error |
Failed to [chars] generalised SMR attribute for [chars]/[dec] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-INVALID_INPUT |
3-Error |
Invalid input [chars] to [chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-IPL_SRC |
3-Error |
Failed to [chars] IPL source [chars] [chars]/[dec][chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-ISSU_NEGO_ERR |
3-Error |
Failed to negotiate [chars] for XDR client [chars] error [chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-ISSU_REG_ERR |
3-Error |
Failed to register [chars] for ISSU client [chars] [dec] entity [dec] error [chars] |
- |
- |
- |
|
CFC_LISP-3-ISSU_XFORM_ERR |
3-Error |
Failed to ISSU transform XDR message [chars] error [chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-LOCAL_EID |
3-Error |
Failed to [chars] local EID prefix [chars]/[dec] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-NO_ADJ |
3-Error |
Failed to find adjacency for [chars] [chars] [chars] [dec] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-NO_FIBIDB |
3-Error |
Failed to find fibidb for [chars] [chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-NO_PATH |
3-Error |
Failed to resolve path type for [chars]:[chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-NO_SB |
3-Error |
Failed to find subblock for [chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-NO_TABLE |
3-Error |
Failed to find table for [chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-NO_VIF |
3-Error |
Unable to find [chars]virtual interface [chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-PUSH_CNTR |
3-Error |
Failed to [chars] push counter for [chars][chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-REMOTE_EID |
3-Error |
Failed to [chars] remote EID prefix [chars]/[dec][chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-REMOTE_EID_PREFIX |
3-Error |
Failed to [chars] remote EID prefix [chars][chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-RLOC_VRF_IN_USE |
3-Error |
RLOC vrfid [dec] already in use by user [chars] top-id [dec] cannot assign to top-id [dec] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-SB_OPERATION_FAILED |
3-Error |
Failed to [chars] subblock on [chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-SBINIT |
3-Error |
Error initializing [chars] subblock data structure. [chars] |
Initialization of the specified subblock data structure could not be accomplished. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-SIGNAL_OCE |
3-Error |
Failed to [chars] LISP signal OCE [chars][chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-SRC_RLOC_IDX |
3-Error |
[chars] source RLOC index database[chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-TABLE_BIND |
3-Error |
Error setting [chars] table [chars] for top-id [dec] iid [dec] [chars][chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-TABLE_CONFLICT |
3-Error |
Conflicting LISP config for top-id [dec] iid [dec] [chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-TABLE_STATE |
3-Error |
Error setting state for table [chars] to top-id [dec] iid [dec] role [chars] [chars][chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-TERM_ADJ |
3-Error |
Terminal adjacency [chars][chars][chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-TIMESTAMP_CTRL_PKT |
3-Error |
Failed to timestamp LISP control packet |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-TREE_OP_FAIL |
3-Error |
Tree [chars] failed for [chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-UNABLE_TO_IDENTIFY_TABLE |
3-Error |
Unable to identify table for packet from [chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-UNEXPECTED_PATH |
3-Error |
Unexpected path type [chars]/[dec] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-UNEXPECTED_PKT |
3-Error |
[chars]: 0x%08x |
A packet with an unexpected protocol was given to the LISP datapath. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-UNKN_INSTANCE |
3-Error |
Unknown instance unable to find/create virtual interface |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-UNKNOWN_PAYLOAD |
3-Error |
Dropping LISP encapsulated packet unknown payload 0x%08x |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-VIF |
3-Error |
Unable to [chars] virtual interface [chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-WALK_DEP |
3-Error |
Walking dependents [chars][chars][chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-XDR_LEN_ERR |
3-Error |
Failed to [chars] XDR message [chars] len [dec] > max [dec] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-3-XDR_REG_ERR |
3-Error |
Failed to register XDR client [chars] [dec] error [chars] |
- |
- |
- |
|
CFC_LISP-5-ADJ_STACK |
5-Notice |
Stacking adjacency [chars] [chars][chars][chars] |
An internal software error occurred. |
CFC_LISP_MSG_DDTS_COMP |
LOG_STD_ACTION |
|
CFC_LISP-5-BELOW_MIN_MTU |
5-Notice |
Cannot set [chars] MTU for RLOC [chars] to [dec] [chars] MTU for [chars] [chars] is [dec] below minimum MTU [dec]+[dec] required for LISP encap |
Unable to set the EID payload MTU for a remote RLOC below the minimal MTU this will cause the encapsulated packet to be bigger than the MTU of the path to the remote RLOC and may cause packet loss. |
CFC_LISP_MSG_DDTS_COMP |
"Increase the MTU of the path to the remote RLOC" |
|
CFC_LISP-5-IGNOREICMPMTU |
5-Notice |
Ignoring received ICMP Type 3 Code 4 [chars]->[chars] next hop mtu [dec] due to pmtu min or max setting |
An ICMP Type 3 Code 4 fragmentation needed and DF set packet |
CFC_LISP_MSG_DDTS_COMP |
"If you want the ICMP packet to be accepted and used " "use the <CmdBold> ip lisp pmtu min NUMBER max NUMBER <NoCmdBold> " "command to decrease the minimum MTU allowed and/or increase the " "maximum MTU that is allowed." |
|
CFC_LISP-5-IGNOREICMPV6MTU |
5-Notice |
Ignoring received ICMPv6 Type 2 [chars]->[chars] next hop mtu [dec] due to pmtu min or max setting |
An ICMPv6 Type 2 Packet Too Big packet |
CFC_LISP_MSG_DDTS_COMP |
"If you want the ICMP packet to be accepted and used " "use the <CmdBold> ipv6 lisp pmtu min NUMBER max NUMBER <NoCmdBold> " "command to decrease the minimum MTU allowed and/or increase the " "maximum MTU that is allowed." |
|
CFC_MPLS_CP_APP_MSG-3-CLIENT_ERR |
3-Error |
MPLS CP APP Unsupported Client [dec] |
Unsupported client trying to use cfc apis |
mpls-mfi |
LOG_STD_ACTION |
|
CFC_MPLS_CP_ION-3-BATCHERR |
3-Error |
MPLS CP ION Batch Error [dec] for [chars] |
Error in batching ion messages between cfc and mpls clients |
mpls-mfi |
LOG_STD_ACTION |
|
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 |
|
CFC_STATS-3- BADSTATSCLIENTSEND |
3-Error |
[chars]: [chars] 0x%08X/[dec] expected 0x%08X/[dec] |
Internal error. May result in unpredictable behaviour. |
- |
"Copy the message exactly as it appears and report it to your technical " "support representative." |
|
CFC_STATS-3- BADSTATSPULL |
3-Error |
[chars]: [chars] |
Internal error. May result in unpredictable behaviour. |
- |
"Copy the message exactly as it appears and report it to your technical " "support representative." |
|
CFC_STATS-3- STATSNOMEM |
3-Error |
CFC Stats failed to allocate memory during [chars] creation. |
Allocation of memory by the XDR subsystem failed. This may result in an unpredictable behavior of XDR |
- |
"Make sure that there is enough memory for the operations being performed " "by your machine. " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
CFC_STATS-3-TESTSTATSCLIENT_DECODE |
3-Error |
XDR test stats [chars] saw error [chars]. |
- |
- |
- |
|
CFC_STATS-3-TESTSTATSCLIENT_UNEXPECTED_EVENT |
3-Error |
Selftest failure: unexpected event [hec] [hec] during |
The XDR statistics infrastructure has experienced a self test failure. This should only occur when a self test is running and a failure is detected. It does not directly imply a problem with normal operation. |
- |
"Copy the message exactly as it appears and report it to your technical " "support representative." |
|
CFC_STATS-4- BADSTATSCLIENTRECEIVE |
4-Warning |
context [dec] length [dec] from [chars] |
The XDR statistics infrastructure received a message it could not decode from a peer. This has no harmful effects but might be a evidence of a more serious problem. |
XDR_DDTS_COMPONENT |
"Copy the message exactly as it appears and report it to your technical " "support representative." |
|
CFC_STATS-4-STATSCLIENT_REGISTRATION |
4-Warning |
Unable to register XDR client [chars] client due to [chars] |
The XDR statistics infrastructure has seen an internal error. This may prevent counters to fail to be reported to the RP. |
- |
"Copy the message exactly as it appears and report it to your technical " "support representative." |
|
CFC_STATS-4- STATSCLIENTADDMCASTGRPFAIL |
4-Warning |
Stats client [chars] failed to add linecards [chars] |
The XDR statistics infrastructure has seen an internal error. This may prevent counters to fail to be reported to the RP. |
- |
"Copy the message exactly as it appears and report it to your technical " "support representative." |
|
CFC_STATS-4- STATSUNEXPECTEDEVENT |
4-Warning |
[chars] |
The XDR statistics infrastructure has seen an internal error. This may prevent counters to fail to be reported to the RP. |
- |
"Copy the message exactly as it appears and report it to your technical " "support representative." |
|
CFC_STATS-4- STATSUNEXPECTEDNEWMCASTGRP |
4-Warning |
Add req for [chars] but already sending stats to [chars] |
The XDR statistics infrastructure has seen an internal error. This may prevent counters to fail to be reported to the RP. |
- |
"Copy the message exactly as it appears and report it to your technical " "support representative." |
|
CFG_MGR-4-BOOTLOADER |
4-Warning |
[chars] for Switch [dec] |
Switch needs to be upgraded to latest Rommon version |
- |
"This is a notification message" " To upgrade the switch to latest rommon using CLI " " upgrade rom-monitor capsule primary switch [number] R0" " Please Do not Power cycle your switch during upgrade" |
|
CFGD_LBL_REGION-4-LCON |
4-Warning |
ERRMSG_NOFLAGS |
- |
- |
- |
|
CFT_API-3-CFT_ERRMSG_MAX_MEMORY |
3-Error |
[chars] [chars] [dec] |
The maximum number of concurrent flows allowed has been exceeded. Some flows might not received the provisioned level of service. |
common-flow-table |
"This is the platform limit. Either lower the network load on this device " "or upgrade to a higher capacity platform." LOG_STD_SH_TECH_ACTION |
|
CFT_API-3-CFT_ERRMSG_NO_MEMORY |
3-Error |
[chars] [chars] [dec] |
The system was unable to supply the requested memory for flow processing to continue. |
common-flow-table |
- |
|
CFT_API-3-CFT_ERRMSG_UNKNOWN |
3-Error |
[chars] [chars] [dec] |
The error message type does not match the possible enumerated definitions. |
common-flow-table |
"This is an internal software error. Please report it to your technical " "support representative." LOG_STD_SH_TECH_ACTION |
|
CFT_API-4-CFT_ERRMSG_CLIENT_PRE_CREATE_PREVENTED |
4-Warning |
[chars] [chars] [dec] |
Flow creation was prevented by a flow table client. This may be due to an explicit policy that is enabled. |
common-flow-table |
"Check your policies to ensure this what you intend." LOG_STD_SH_TECH_ACTION |
|
CFT_API-4-CFT_ERRMSG_FLOW_CREATION_PREVENTED |
4-Warning |
[chars] [chars] [dec] |
Flow creation was denied by a the system. A possible denial of service attack may have been detected. |
common-flow-table |
"Modify your denial of service policy if this is in error." LOG_STD_SH_TECH_ACTION |
|
CFT_API-5-CFT_ERRMSG_NON_FIRST_IP_FRAGMENT |
5-Notice |
[chars] [chars] [dec] |
The flow table was unable to process a TCP fragmented packet. Service for these packets may be unavailable. |
common-flow-table |
"Enable the virtual fragment reassembly VFR functionality." |
|
CFT_API-5-CFT_ERRMSG_UNSUPPORTED_L3_PROTOCOL |
5-Notice |
[chars] [chars] [dec] |
An unsupported layer 3 protocol was identified. |
common-flow-table |
"Flow based inspection does not support this protocol at this time." LOG_STD_SH_TECH_ACTION |
|
CFT_API-7-CFT_ERRMSG_CLIENT_API |
7-Debug |
[chars] [chars] [dec] |
A CFT client may have a incorrectly accessed an API. |
common-flow-table |
"This is an internal software error. Please report it to your technical " "support representative." LOG_STD_SH_TECH_ACTION |
|
CFT_CLIENT-4-CFT_MEMORY_BOUNDARY_TOUCH_CLEAR |
4-Warning |
CFT memory utilization has declined below its threshold memory is available for [chars]. |
After CFT was in memory shortage memory utilization has declined below its threshold New traffic flows will be opened properly |
qfp-cft |
LOG_STD_ACTION |
|
CFT_CLIENT-4-CFT_MEMORY_BOUNDARY_TOUCH_WARN |
4-Warning |
CFT reached maximum configured memory utilization. Can't allocate more memory for [chars]. |
Because of CFT memory shortage new flows may not be opened properly |
qfp-cft |
LOG_STD_ACTION |
|
CFT_CLIENT-4-MAX_FCS_TOUCH_CLEAR |
4-Warning |
CFT number of [chars] has declined below its threshold flow contexts are available for [chars]. |
After CFT was in flow contexts shortage the number of flow contexts has declined below its threshold. New traffic flows will be opened properly |
qfp-cft |
LOG_STD_NO_ACTION |
|
CFT_CLIENT-4-MAX_FCS_TOUCH_WARN |
4-Warning |
CFT number of [chars] threshold is reached can't allocate more memory for [chars]. |
Because of non-availability of flow contexts new traffic flows may not be opened |
qfp-cft |
LOG_STD_NO_ACTION |
|
CFT_CLIENT-4-SYS_FREE_MEMORY_LOW_WATERMARK_TOUCH_CLEAR |
4-Warning |
System free memory has increased above its lower watermark memory is available for [chars]. |
After system memory was in shortage free memory has increased above its lower watermark New traffic flows will be opened properly |
qfp-cft |
LOG_STD_ACTION |
|
CFT_CLIENT-4-SYS_FREE_MEMORY_LOW_WATERMARK_TOUCH_WARN |
4-Warning |
System free memory has reached its lower watermark. Can't allocate more memory for [chars]. |
Because of system memory shortage new flows may not be opened properly |
qfp-cft |
LOG_STD_ACTION |
|
CFT_CONGESTION_STATE-4-CPU_THRESHOLD_CHANGE |
4-Warning |
CPU Threshold has been changed to [dec]%%. |
CPU threshold has been changed. |
cpp-ucode |
LOG_STD_ACTION |
|
CFT_CONGESTION_STATE-4-MAX_BACKOFF_CHANGE |
4-Warning |
Maximum back-off timeout has been changed to [dec]. |
Maximum back-off timeout has been changed. |
cpp-ucode |
LOG_STD_ACTION |
|
CFT_CONGESTION_STATE-4-STATE_CHANGED_TO_GRADUAL_BRINGUP |
4-Warning |
CPU Utilization:[dec]%%. CPU usage regulation state is now: Gradual bring-up. |
CFT Congestion state changed to Gradual bring-up |
cpp-ucode |
LOG_STD_ACTION |
|
CFT_CONGESTION_STATE-4-STATE_CHANGED_TO_SELF_REGULATED |
4-Warning |
CPU Utilization is high:[dec]%% CPU usage regulation state is now: Self-regulated. |
CFT Congestion state changed to Self-regulated. |
cpp-ucode |
LOG_STD_ACTION |
|
CFT_CONGESTION_STATE-6-STATE_CHANGED_TO_NORMAL |
6-Information |
CPU Utilization back to normal CPU usage regulation state is now: Normal. |
CFT Congestion state back to normal. |
cpp-ucode |
LOG_STD_ACTION |
|
CFT_CONGESTION_STATE-6-STATE_DEFAULT |
6-Information |
CPU-usage regulation parameters have been changed to default. Max back-off timeout:[dec] seconds CPU threshold [dec]%%. |
Parameters to default. |
cpp-ucode |
LOG_STD_ACTION |
|
CFT-2-IPC_INIT |
2-Critical |
IPC message handler registration failure rc [dec] |
Registering an IPC message handler for the CFT feature failed. This will cause the feature to not function. |
qfp-cft |
"This is normally a software issue. " "The consequences are that the CFT feature will not function. " LOG_STD_ACTION |
|
CFT-3-HA_INVALID_BULK_SYNC |
3-Error |
Invalid message length for bulk sync got [dec] expected [dec] |
Standby received an unrecognized VRF name hash |
cpp-ucode |
LOG_STD_ACTION |
|
CFT-3-HA_INVALID_ID_BULK_SYNC |
3-Error |
Invalid feature id for bulk sync got [dec] expected [dec] |
Standby received an unrecognized VRF name hash |
cpp-ucode |
LOG_STD_ACTION |
|
CFT-3-HA_INVALID_MSG_LEN_RCVD |
3-Error |
invalid [chars] rg [dec] [dec] expected [dec] opcode [chars] [hec] |
Standby received an invalid Firewall HA message |
cpp-ucode |
LOG_STD_ACTION |
|
CFT-3-HA_INVALID_MSG_NO_V6KEY_RCVD |
3-Error |
Missing IPv6 key - rg: [dec] len: [dec] msg type: \[chars]\ [hec] flow type: [dec] |
Standby received an invalid Firewall HA message |
cpp-ucode |
LOG_STD_ACTION |
|
CFT-3-HA_INVALID_MSG_RCVD |
3-Error |
invalid [chars] [hec] opcode [chars] [hec] |
Standby received an invalid Firewall HA message |
cpp-ucode |
LOG_STD_ACTION |
|
CFT-3-HA_INVALID_MSG_VRF_HASH |
3-Error |
rg: [dec] i_vrf_hash: 0x%llx r_vrf_hash: 0x%llx |
Standby received an unrecognized VRF name hash |
cpp-ucode |
LOG_STD_ACTION |
|
CFT-3-HA_INVALID_RG_RCVD |
3-Error |
invalid [chars] opcode [chars] [dec] - rg [dec]:[dec] |
Standby received an invalid Redundancy group |
cpp-ucode |
LOG_STD_ACTION |
|
CFT-3-IPC_NORES |
3-Error |
No space for the IPC reply size [dec] |
For a request from upper CFT software stack layers it was not possible to allocate space for a reply for the specified size. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation. |
qfp-cft |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
CFT-3-IPC_OPEN_REPLY |
3-Error |
IPC Open Reply failed request [dec] |
For a request from upper CFT software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation. |
qfp-cft |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
CGC-0-CGC_EMERG |
0-Emergency |
[chars] |
CGC_INTERNAL_ERROR |
CGC_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CGC-0-CGC_EMERG |
0-Emergency |
[chars] |
CGC_INTERNAL_ERROR |
CGC_DDTS_COMPONENT |
LOG_STD_ACTION |
|
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-1-CGC_ALERT |
1-Alert |
[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-2-CGC_CRIT |
2-Critical |
[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-3-CGC_ERR |
3-Error |
[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-4-CGC_WARNING |
4-Warning |
[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-5-CGC_NOTICE |
5-Notice |
[chars] |
Normal but significant conditions |
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-6-CGC_INFO |
6-Information |
[chars] |
Informational messages |
CGC_DDTS_COMPONENT |
LOG_STD_NO_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 |
|
CGC-7-CGC_ASSERT |
7-Debug |
Assertion Failure [chars] @[chars]:[dec] : [chars] |
CGC_INTERNAL_ERROR |
CGC_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CGC-7-CGC_ASSERT |
7-Debug |
Assertion Failure [chars] @[chars]:[dec] : [chars] |
CGC_INTERNAL_ERROR |
CGC_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CGM-3-CGM_FIPS_BYPASS_TEST |
3-Error |
NIST bypass test failed for CGM object [chars]. |
Class-Group Manager Security Client database detected a discrepancy in a security sensitive object. This could be due to a hardware or software resource limitation or a software defect. |
qfp-class-internal |
"Check the logs for information on the relevant " "object download states. Remove the object or a " "parent object in question. If the problem persists " "reboot the forwarding processor ESP." |
|
CGM-3-CGM_FIPS_BYPASS_TEST |
3-Error |
- |
- |
- |
- |
|
CHASSIS-3-OPERATION_FORBIDDEN |
3-Error |
[chars] and try again. |
There are two ejcet buttons on PRE5 front panel. When both eject buttons are pulled out or a CLI plugin-card-preotec enable/disable So the software modules protected by this may fail such as write/erase based on bootflash chip |
cr10k5 |
"Please tighten the screws of the eject button." |
|
CHASSIS-3-PROCESSERR |
3-Error |
Couldn't start tempeature enviroment monitoring process |
The temperature monitoring process could not be started during initialization. |
cr10k5 |
LOG_STD_ACTION |
|
CHASSIS-4-READALERTRESERR |
4-Warning |
MAX1668 [dec] read alert response address error |
MAX1668 read alert response address failed. |
cr10k5 |
LOG_STD_ACTION |
|
CHASSIS-6-EJECT_BUTTON |
6-Information |
[chars] eject button is being screwed on/off. |
There are two ejcet buttons on PRE5 front panel. When any eject button is being screwed on/off the error message will be printed to screen to remind the user. |
cr10k5 |
LOG_STD_ACTION |
|
CHAT-3-CANTRUN |
3-Error |
[t-line] in use can't run startup script |
When the startup script attempted to run it found another process had\n\ Already been started on the line |
chat |
"Remove startup script from line configuration if it's inappropriate.\n\ Report to cisco." |
|
CHKPT-3-CHKPT_MSG_NULL |
3-Error |
The chkpt message has an empty data buffer |
This is a severe error as far as checkpointing is concerned. The chkpt message's data buffer is NULL indicating that there were no memory resources to assign while getting a buffer. |
checkpoint |
"Check whether this error goes away when the " "memory is increased else " LOG_STD_SH_TECH_ACTION |
|
CHKPT-3-ILLEGAL |
3-Error |
ILLEGAL call to CF API by client [dec] on the [chars] system |
An illegal API call was made by a CF client |
checkpoint |
"Find out the offending client using " LOG_STD_SH_TECH_ACTION |
|
CHKPT-3-INVALID_CALLBACK_ARG |
3-Error |
Attempt to add a checkpointing client with an invalid [chars] argument |
Checkpointing messages are used to carry encoded information for transfer between various High-Availabilty clients. For example to synchronize state information between redundant route processor units. An invalid argument was supplied to an internal API. The failure most likely occurred because of a software error. The message output identifies the type of error that occurred. The system state between one or more checkpointing clients might not be properly synchronized. |
checkpoint |
LOG_STD_ACTION |
|
CHKPT-3-INVALID_ENTITY_MSG_ID |
3-Error |
Invalid message event received [dec] |
- |
- |
- |
|
CHKPT-3-IPCPORT |
3-Error |
Unable to create IPC port on [chars] |
A severe checkpoint error occurred because the system was unable to allocate the resources needed to create a communications port for the Interprocess Communications IPC channel needed to |
checkpoint |
"Increase the memory. If the error persists" LOG_STD_SH_TECH_ACTION |
|
CHKPT-3-IPCREGISTER |
3-Error |
Unable to register IPC port on [chars] |
Checkpoint Facility was unable to register an IPC port. This can happen when registering a port that hasn't yet been created. |
checkpoint |
LOG_STD_SH_TECH_ACTION |
|
CHKPT-3-IPCSESSION |
3-Error |
Unable to open an IPC session with [chars] |
A severe checkpointing error occured as the system was unable to establish an interprocess communications session between the Active and the Standby peers. |
checkpoint |
"As this failure hinders any communication from taking place " "between the Active and the Standby peers reset the Standby. " "If the error persists" LOG_STD_SH_TECH_ACTION |
|
CHKPT-3-ISSU_MSG_NOT_COMPATIBLE |
3-Error |
Checkpointing message type not compatible |
Checkpointing messages are used to carry encoded information for transfer between various High-Availabilty clients. For example to synchronize state information between redundant route processor units. An error was detected when verifying the checkpointing message type compatibility between checkpointing client peers. The failure most likely occurred because of a software error. The system state between one or more checkpointing clients might not be properly synchronized. |
checkpoint |
"show checkpoint client" |
|
CHKPT-3-ISSU_NEGO_FAILED |
3-Error |
Checkpointing Facility failed to start ISSU negotiation with the peer [chars] |
Checkpointing Facility was unable to start the ISSU negotiation successfully. ISSU negotiation is done during system initialization or if the Standy system is signing in with the Active system. The failure to start negotiation is a fatal error condition and most likely occured because of a software error. |
checkpoint |
"show tech" |
|
CHKPT-3-ISSU_RCV_TRANSFORM_FAILED |
3-Error |
Checkpointing receive message header transformaton failed [chars] |
- |
- |
- |
|
CHKPT-3-ISSU_XMIT_TRANSFORM_FAILED |
3-Error |
Checkpointing transmit message header transformaton failed [chars] |
- |
- |
- |
|
CHKPT-3-NO_RESOURCES |
3-Error |
[chars] |
A run-time module could not obtain the resources that are required to complete a task. The failure most likely occurred because of a software error or a lack of system memory. Additional details on the nature of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized. |
checkpoint |
"If you determine that this condition was caused by a lack of system " "memory reduce system activity to ease memory demands or if conditions " "warrant upgrade to a larger memory configuration. Otherwise " LOG_STD_SH_TECH_ACTION |
|
CHKPT-3-NOMEM |
3-Error |
Unable to allocate resources for CF on [chars]. |
This error occurs when there are no memory resources available. This is a severe error as far as check pointing is concerned |
checkpoint |
"Reduce other system activity to ease memory demands. Add more memory. " "If enough memory is available try to see whether the problem goes away " "by reloading the router. If not then" LOG_STD_SH_TECH_ACTION |
|
CHKPT-3-REGISTERATION_FAILED |
3-Error |
Failed to register with [chars] rc = [dec] |
An internal failure associated with client registration occurred in the run-time module specified in the message output. The return code that is specified in the message output identifies the type of failure that was detected. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized. |
checkpoint |
LOG_STD_SH_TECH_ACTION |
|
CHKPT-3-RFREG |
3-Error |
Unable to register checkpoint as client of RF. |
This is a severe error as far as check pointing is concerned |
checkpoint |
LOG_STD_SH_TECH_ACTION |
|
CHKPT-3-RMI_CALLBACK |
3-Error |
Checkpointing Facility encountered an error while processing a callback from the Resource Manager RMI [chars] |
Checkpointing Facility registers with the Resource Manager RMI to |
checkpoint |
"show tech" |
|
CHKPT-3-RMI_FAILED |
3-Error |
Checkpointing Facility failed to register with the Resource Manager RMI [chars] |
Checkpointing Facility registers with the Resource Manager RMI to |
checkpoint |
"show tech" |
|
CHKPT-3-SYSMGR_LOOKUP |
3-Error |
Failed to get process Job ID from SysMgr |
Failed to get the Job ID for this ION process from SysMgr. The |
checkpoint |
"show tech" |
|
CHKPT-3-TIMER |
3-Error |
[chars] |
Checkpoint Facility was unable to retrieve the correct context for a previously saved message descriptor. This is most likely a software error caused by possible memory corruption. |
checkpoint |
LOG_STD_ACTION |
|
CHKPT-3-TRANSMIT_FAILED |
3-Error |
Checkpointing message transmission failure [chars] |
- |
- |
- |
|
CHKPT-3-UNKNOWNMSG |
3-Error |
Unknown message received from peer on the standby for client [dec]. |
This is a severe error as far as check pointing is concerned. This will be caused when one of the peers can some checkpoint message types that the other side does not understand. This is caused due to a software error as the set of messages being exchanged by either side must be the same. |
checkpoint |
LOG_STD_SH_TECH_ACTION |
|
CHKPT-4-DISABLED |
4-Warning |
Check Pointing is disabled. Client [chars] should not be calling any CF API |
This is mainly a warning and might be due to timing issue |
checkpoint |
LOG_STD_SH_TECH_ACTION |
|
CHKPT-4-DUPID |
4-Warning |
Duplicate checkpoint client ID [dec]. |
A checkpoint client is using a client ID which is already assigned to an another client. This could be due to a synchronization delay which will typically resolve itself. This would happen when an already registered Checkpointing Facility client again tries to add itself. |
checkpoint |
LOG_STD_SH_TECH_ACTION |
|
CHKPT-4-FREE_BUFFER |
4-Warning |
Checkpointing [dec] failed to free buffer |
Checkpointing failed to free a buffer. This may cause leak in memory resources. |
checkpoint |
LOG_STD_SH_TECH_ACTION |
|
CHKPT-4-GET_BUFFER |
4-Warning |
Checkpointing ISSU failed to get buffer. Dest seat id 0x[hec] |
Checkpointing ISSU failed to get a buffer. This is due to the dearth of memory resources. |
checkpoint |
"Upgrade the memory. If the error " "persists " LOG_STD_SH_TECH_ACTION |
|
CHKPT-4-INIT |
4-Warning |
Checkpoint [chars] initialization failed in RF state [chars] |
Checkpointing initialization has failed This is software error caused by an out of memory condition as there aren't enough resources available to set up the initialization data structures |
checkpoint |
"Upgrade the memory. If the error " "persists " LOG_STD_ACTION |
|
CHKPT-4-INVALID_CLIENT |
4-Warning |
Invalid checkpoint client ID [dec]. |
The client id is invalid. This error has occured since the corresponding client is not present. |
checkpoint |
LOG_STD_SH_TECH_ACTION |
|
CHKPT-4-INVALID_ENTITY |
4-Warning |
Invalid checkpoint entity ID [dec]. |
The entity id is invalid. This error has occured since the corresponding entity is not present. |
checkpoint |
LOG_STD_SH_TECH_ACTION |
|
CHKPT-4-MSG_SEND |
4-Warning |
Checkpointing ISSU failed to send message. Dest seat id 0x[hec] |
Checkpointing ISSU failed to send nego message to peer. This will be due to an out of memory condition communication with the peer being severed |
checkpoint |
LOG_STD_SH_TECH_ACTION |
|
CHKPT-4-NOCLIENT |
4-Warning |
CF client is NULL [chars] |
Checkpoint Facility cannot send the message as the client is NULL. |
checkpoint |
LOG_STD_SH_TECH_ACTION |
|
CHKPT-4-NOIPCPORT |
4-Warning |
IPC port is NULL [chars] |
Checkpoint Facility cannot send the message as the IPC port information is NULL. This message appears since since the communication session between the Checkpointing Facility peers has not yet been established. |
checkpoint |
LOG_STD_SH_TECH_ACTION |
|
CHKPT-4-NOMESSAGE |
4-Warning |
Message is NULL [chars] |
Checkpoint Facility cannot send the message as the message is NULL. |
checkpoint |
LOG_STD_SH_TECH_ACTION |
|
CHKPT-4-PAK_MGR_CONN |
4-Warning |
Failed to connect to the Packet Manager |
During Checkpoint initialization unable to create a connection to the Packet Manager. This could result in the CF infra unable to access shared memory in the client context using a virtual address. |
checkpoint |
LOG_STD_ACTION |
|
CHKPT-4-PAK_RECLAIM |
4-Warning |
Failed to reclaim packet from Packet Manager client [chars] |
After the message send failed the CF client was unable to reclaim the packet to be able to free the message. |
checkpoint |
LOG_STD_ACTION |
|
CHKPT-5-HIGHBUFFER |
5-Notice |
Checkpoint client using Large No. of Buffers in domain [dec] are [chars] |
Several IPC messages are pending to be processed by or delevered to |
checkpoint |
"show checkpoint statistics buffer-usage" |
|
CHUNK-3-CHUNK_BAD_REFCNT |
3-Error |
refcnt=[dec] data=0x[hec] |
The memory chunk manager detected a bad reference count |
cpp-ucode |
LOG_STD_ACTION |
|
CHUNK-3-INVALID_ELEM_SIZE |
3-Error |
requested [dec] |
Memory corruption was detected by the memory chunk manager |
cpp-ucode |
LOG_STD_ACTION |
|
CHUNK-3-SIBLING_ERR |
3-Error |
Tried to destroy sibling memory chunk 0x[hec] |
An invalid sibling condition was hit in the Memory Chunk Manager |
cpp-ucode |
LOG_STD_ACTION |
|
CI-1-BLOWSHUT |
1-Alert |
Blower failure shutdown in [dec] seconds |
One of the six blowers in a five-slot chassis has failed. Because each blower cools a separate region of the cards in the chassis all blowers are needed for router operation. If a blower failure persists for 2 minutes the router will shut itself down and will need to be power cycled. |
- |
LOG_STD_ACTION |
|
CI-2-ENVCRIT |
2-Critical |
[chars] measured at [chars] |
One of the measured environmental test points exceeds an extreme threshold. |
- |
"Correct the specified condition or the router may shut itself down or fail to operate properly." |
|
CI-2-INT |
2-Critical |
Unexpected interrupt - status %02x |
An unexpected interrupt occurred. This is a serious software error which will be followed by a core dump. |
- |
LOG_STD_ACTION |
|
CI-3-BLOWER |
3-Error |
[chars] fan failure |
One of the router's cooling fans failed. |
- |
"Replace the fan as soon as possible or the router may shut itself down or fail to operate properly." |
|
CI-3-CTRLRTYPE |
3-Error |
Wrong controller type %02x |
The CI was manufactured incorrectly. |
- |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
CI-3-NOACK |
3-Error |
[chars] acknowledge failure cmd %02x addr %02x data %02x |
The CI software failed to communicate with the CI hardware. |
- |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
CI-3-PSFAIL |
3-Error |
Power supply [dec] failure |
One of the router's power supplies failed. |
- |
"Replace the failed power supply as soon as possible." |
|
CI-3-SLOTCOMP |
3-Error |
Inconsistent [chars] slot %02x |
The CI software detected a possible inconsistency in the CI hardware. |
- |
"Confirm that the CI card is correctly and fully installed in the backplane. If error recurs call your technical support representative for assistance." |
|
CI-4-COND |
4-Warning |
Restarting with [dec] recent soft power shutdowns\n\t\tor system just powered-on |
A soft shutdown occurs when the router powers itself down due to a detected over temperature condition. When the temperature goes up past the board shutdown trip point the cards are shutdown but the power supplies fans and CI continue to run. <body><par>When the system cools past the restart trip point the system will restart. The system counts the number of times this happens to keep the up/down cycle from repeating indefinitely. If the above counter reaches zero the system undergoes a hard shutdown which requires a power cycle to recover. The soft shutdown counter is reset to its maximum value after the system has been up for six hours. |
- |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
CI-4-ENVWARN |
4-Warning |
[chars] measured at [chars] |
One of the measured environmental test points exceeds the warning threshold. |
- |
"Closely monitor the condition and correct if possible. If the situation worsens call your technical support representative for assistance." |
|
CI-4-MAXOUTPUT |
4-Warning |
Power supply [dec] [dec]V is at or near rated output |
This indicates that the power supply is delivering its maximum rated current. This condition is not a problem unless the current continues to increase beyond the rated limit of the power supply which can cause hardware damage. |
- |
LOG_STD_ACTION |
|
CI-4-NOTFOUND |
4-Warning |
Chassis Interface not found |
The system software could not detect the presence of a CI card. |
- |
"Verify that the CI card is correctly and fully installed in the backplane. If the error recurs call your technical support representative for assistance." |
|
CI-4-SYSLOAD |
4-Warning |
System [dec]V load exceeds single power supply [dec] capacity |
This warning message indicates that the system's electrical current usage exceeds the capacity of a single power supply. During this condition power supplies must not be removed from the system. |
- |
- |
|
CI-4-UNBALANCE |
4-Warning |
Unbalanced [dec]V output from dual power supplies |
The difference in electrical current output between the two power supplies is out of tolerance for the system design. One of the power supplies may be failing or about to fail. |
- |
LOG_STD_ACTION |
|
CI-6-BPLANE |
6-Information |
CI type [dec] differs from NVRAM type [dec] |
The chassis type as reported by the CI is different from that programmed into NVRAM. |
- |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
CI-6-PSCHANGE |
6-Information |
Power supply [dec] changed from [chars] to [chars] |
The CI reported that a power supply was either installed removed or changed. |
- |
"If the situation does not correspond with a physical change in the system's power supplies call your technical support representative for assistance." |
|
CI-6-PSNORMAL |
6-Information |
Power supply [dec] normal |
One of the router's failed power supplies are working normal now. |
- |
"If the situation does not correspond with a normal operation of the system's power supplies call your technical support representative for assistance." |
|
CIPDUMP-3-CIP_CORE_DUMP_ERROR |
3-Error |
CIP core dump error slot [dec]: [chars] |
An error occured during a CIP core dump |
- |
"None." |
|
CIPDUMP-6-CIP_CORE_DUMP_PROGRESS |
6-Information |
Dump of slot [dec] core [chars]. |
Progress messages for CIP core dump. |
- |
"None." |
|
CIRRUS-1-NOMEMORY |
1-Alert |
msgtxt_nomemory |
An operation could not be accomplished because of a low memory\n\ condition. |
- |
LOG_STD_REDUCE_ACTION |
|
CIRRUS-3-BADENCAP |
3-Error |
msgtxt_badencap |
- |
- |
"" |
|
CIRRUS-3-BADHDXFSM |
3-Error |
Interface serial [dec] Unexpected HDX state [dec] event [dec] |
An internal software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
CIRRUS-3-BADMODE |
3-Error |
Interface serial [dec] Bad mode encountered in init |
An internal software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
CIRRUS-3-BADRXISR |
3-Error |
Interface serial [dec] Unexpected situation in receive ISR |
An internal software error occurred while receiving data. |
- |
LOG_STD_SH_TECH_ACTION |
|
CIRRUS-3-BADTXISR |
3-Error |
Interface serial [dec] Unexpected situation in transmit ISR |
An internal software error occurred while transmitting data. |
- |
LOG_STD_SH_TECH_ACTION |
|
CIRRUS-3-HWNORESPONSE |
3-Error |
The CD2430 Controller is not responding power cycle the router |
The CD2430 controller has failed to respond to your request.\n\ This is due to unsupported clocking or the use\n\ of a non-standard cable. |
- |
"Check the clocking and cable. Use cisco cables only. " LOG_STD_RECUR_ACTION |
|
CIRRUS-3-RESETERR |
3-Error |
CD2430 serial controller [dec] Reset timeout error |
The async controller failed to respond to a reset command.\n\ This may indicate a hardware failure. |
- |
"Reset the interface or controller.\n\ Cycle the power if necessary. " LOG_STD_RECUR_ACTION |
|
CIRRUS-3-SETCHAN |
3-Error |
Serial[dec]: setchan called in CD2430 interrupt context |
An internal software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
CIRRUS-4-DOWNREV_NM |
4-Warning |
Network Module card in slot [dec] is incompatible with the system. |
The network module in this slot is an old revision which is not \n\ compatible with this system. Please upgrade that network module. |
- |
LOG_STD_SH_TECH_ACTION |
|
CIRRUS-5-LINEFLAP |
5-Notice |
Unit [dec] excessive modem control changes |
The specified async interface was determined to have too many\n\ automatic control changes in too short a span of time.\n\ This may indicate a hardware or software error in the interface. |
- |
"Reset the interface. " LOG_STD_RECUR_ACTION |
|
CISCO_STUN-3-INTERTNAL_ERROR |
3-Error |
Unable to process STUN message received on IP address [chars] and port [dec] failed with value [dec] |
Unable to processs the received STUN packet. Could be due to no ICE instance present to handle this packet or the STUN message has a wrong method or stray packet |
ipipgw |
LOG_STD_RECUR_ACTION |
|
CISCO_STUN-3-NORESOURCE |
3-Error |
No resources for [chars] |
An error was encountered while trying to obtain memory resources for an internal queue or table. If malloc errors where also seen then that is most likely the root of the problem. If no memory allocation errors have occurred then this may be an internal problem. |
ipipgw |
"If there were memory allocation errors at the" "same time as this error then this error can be ignored. Otherwise: " LOG_STD_SH_TECH_ACTION |
|
CISCO_STUN-3-PARSE_ERROR |
3-Error |
Parsing of STUN message received on IP address [chars] and port [dec] failed with value [dec] |
Parsing of one of STUN attribute failed due to invalid value or not present or received STUN message has invalid header |
ipipgw |
LOG_STD_RECUR_ACTION |
|
CISCO_STUN-3-QUEUE_ERROR |
3-Error |
Unable to enqueue event [chars] [dec] to a process watched queue. Current size: [dec] max size: [dec] |
- |
- |
- |
|
CISCO_STUN-4-ICE_ROLE_CONFLICT |
4-Warning |
Ice Role Conflcit detected in the received STUN message on UDP IP address [chars] port [dec] |
A STUN messages received has a role-conflcit determined as per procedures of RFC 5245. CUBE has responded with a ERROR-CODE attribute of with a value of 487 Role Conflict but retains its role. |
ipipgw |
LOG_STD_NO_ACTION |
|
CISCO_STUN-4-INVALID_MESSAGE_INTEGRITY |
4-Warning |
Invalid Message-Integrity attribute in the received STUN message on UDP IP address [chars] port [dec] |
A STUN messages received has a wrong Message-Integrity. This could mean the sending device has not computed the integrity of the STUN payload before it sends out Or it has changed the payload after it has computed the integrity and hence the integrity is wrong. CUBE has not honoured this STUN message and has responded with STUN error response with a error code 400 as per RFC 5389 |
ipipgw |
LOG_STD_NO_ACTION |
|
CISCO_STUN-4-INVALID_USERNAME |
4-Warning |
Invalid USERNAME attribute in the received STUN message on UDP IP address [chars] port [dec] |
A STUN messages received has a wrong USERNAME attribute and does not comply with RFC 5245. CUBE has not honoured this STUN messsage and has responded with a STUN error response have ERROR-ATTRIBUTE value 400 |
ipipgw |
LOG_STD_NO_ACTION |
|
CLB-4-CLB_SLAVE_DEAD |
4-Warning |
[chars] |
Slave connection is dead and is being closed. Master no longer receives updates from this Slave. |
- |
"" |
|
CLB-4-CLB_VERSION_MISMATCH |
4-Warning |
[chars] |
Version mismatch for Cluster load-balancer feature. Master could ignore some load attributes while calculating load of a Slave. |
- |
"Upgrade to an IOS image with " "latest version of Cluster " "load-balancer feature" |
|
CLB-6-CLB_SLAVE_CONNECTED |
6-Information |
[chars] |
Recevied new Slave connection. Master now receives update from this Slave. |
- |
"" |
|
CLEAR_CHKPT-5-LDP |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
CLEAR_COUNTERS-5-MPLS_TE_LM |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
CLEAR_NBRS-5-LDP |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
CLEAR-5-COUNTERS |
5-Notice |
Clear counter on [chars] [chars] by [chars] |
The counters have been cleared on the interfaces |
- |
LOG_STD_NO_ACTION |
|
CLEAR-5-EXT_COUNT |
5-Notice |
Clear extended [chars] counters on [chars] by [chars] |
The extended counters have been cleared on the interfaces |
- |
LOG_STD_NO_ACTION |
|
CLI_ADD_FAILED-3-MPLS_TE_HA |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
CLI_AGENT-1-NVGEN_ERR |
1-Alert |
Error while processing NVGEN command: [chars] |
An error occurred during an NVGEN command |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-1-NVGEN_TRACEBACK |
1-Alert |
Traceback: [chars] |
Traceback from NVGEN command |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-3-BIPC_BUFFER |
3-Error |
Error [dec] Unable to acquire a BIPC buffer for [chars] messages. |
A message was to be sent by IOS but no BIPC buffer was available. The message to be sent has been discarded and the associated operation failed. |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-3-BIPC_CONN |
3-Error |
BIPC connection is down unable to send command: [chars] |
IOS cli-agent client could not connect to cli-agent using BIPC |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-3-BIPC_ENQUEUE |
3-Error |
Error [dec] queueing TDL message '[chars]' to send to the Shell Manager |
An unexpected condition has occurred when IOS attempted to queue a TDL message to send to the Shell Manager |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-3-BIPC_INIT |
3-Error |
Unable initialize BIPC connection to cli-agent |
BIPC initialization failed BIPC infra is not available |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-3-BIPC_REMOTE |
3-Error |
BIPC connection is down while waiting for cli-agent to reply: [chars] |
Connection to cli-agent is not available IOS |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-3-BUILD_MSG |
3-Error |
Error [dec] building TDL message '[chars]' to send to the cli-agent: [chars] |
An unexpected condition has occurred while IOS is building a TDL message to send to the cli-agent |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-3-ECI_CTX |
3-Error |
Unable to get [chars] for [chars] |
Unable to get message from the queue message received from cli-agent. There might be memory issue in IOSD. |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-3-ECI_DECODER |
3-Error |
Decoder error: [chars]. |
Error in decoder ring string which is generated by ECI metadata file. ECI metadata files are generated from sdl file using sdl compiler in WCM. |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-3-ECI_ENQUEUE |
3-Error |
Unable to enqueue received message for processing [[chars]] : [chars] |
Enqueue failed due multiple reason no context found TDL get error or run out of memory |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-3-ECI_INVALID_CTX |
3-Error |
Invalid message cannot be processed ctx: %#X |
IOS recieved a message with invalid context ID. ECI cannot find the coresponding context from the table |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-3-ECI_MEM |
3-Error |
Memory Error: [chars] |
Memory related problem |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-3-ECI_MODE |
3-Error |
Submode Error [chars]: [chars] |
Unable to enter submode due to mode variable error |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-3-ECI_TIMEOUT |
3-Error |
Maximum timeout has been reached while waiting for cli-agent to respond: [dec] seconds |
CLI Agent did not reply to IOS within expected timeout |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-3-FILE_OPEN |
3-Error |
Failed to open [chars]: [chars] |
Failed to load external configuration command set |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-3-LOAD_FILE |
3-Error |
Unable to load file: [chars] |
Unable to load data required by external configuration command set |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-3-MARSHAL |
3-Error |
Error [dec] marshaling TDL message [[chars]] buffer length [dec]: [chars] |
An unexpected condition has occurred while IOS is marshaling TDL message to send to the cli-agent |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-3-MSG_DISPATCH |
3-Error |
IOS cli-agent client message dispatcher error: [chars] |
cli-agent RP message dispacher error |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-3-NOT_EOK |
3-Error |
Error [dec] in [chars]: [chars] |
The error code passed in is not EOK |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-3-NVGEN_CMD_LIMIT |
3-Error |
NVGEN error: rendered command too long - truncated '[chars]' |
Rendered command is too long and is truncated during NVGEN |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-3-TDL_CREATE |
3-Error |
Error Creating TDL message '[chars]' |
Could not create TDL message structure |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-3-TDL_GET |
3-Error |
Error [dec] handling TDL GET API from TDL message [[chars]]: [chars] |
An unexpected condition has occurred while IOS is processing a TDL message received from the cli-agent |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-4-ECI_IGNORE_MSG |
4-Warning |
Ignoring [chars] message: [chars] |
ECI in pull state and ignores the incoming mesage from cli_agent |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-4-ECI_MSG_BLK_LOW |
4-Warning |
Not enough msg block for requesting message free msg block = [dec] |
ECI have runout the message block to ask for more resp msg |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-4-ECI_UNKNOWN_EVENT |
4-Warning |
ECI recieved unknown event [dec] |
ECI got unknown event |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLI_AGENT-7-ECI_DEBUG |
7-Debug |
ECI: [chars][dec] |
ECI module debug |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
CLIENT_CLOCK_SYNC-3-CREATEBOOL |
3-Error |
watched boolean creation failure. bool [chars] |
An internal software error occurred. |
os |
"If this message recurs copy it exactly as it appears and report\n\ it to your technical support representative." |
|
CLIENT_CLOCK_SYNC-3-PORTCREATE |
3-Error |
cannot create port [chars] due to [chars] |
An internal software error occurred. |
os |
"If this message recurs copy it exactly as it appears and report\n\ it to your technical support representative." |
|
CLIENT_CLOCK_SYNC-3-PORTOPEN |
3-Error |
cannot open port [chars] due to [chars] |
An internal software error occurred. |
os |
"If this message recurs copy it exactly as it appears and report\n\ it to your technical support representative." |
|
CLIENT_CLOCK_SYNC-3-PORTREG |
3-Error |
cannot register port [chars] due to [chars] |
An internal software error occurred. |
os |
"If this message recurs copy it exactly as it appears and report\n\ it to your technical support representative." |
|
CLIENT-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
CLNS-1-BKUPERR |
1-Alert |
ISIS: [chars] in [hex] ndb_next [hex] ndb_prev [hex] lsp_next [hex] lsp_prev [hex] metric [hex] route type [chars] index [dec] [chars] [hex] |
An internal error occurred in the maintenance of the Intermediate\n\ System-to-Intermediate System ISIS backup route table. |
- |
LOG_STD_ACTION |
|
CLNS-1-LINKERR |
1-Alert |
ISIS: [chars] in [hex] lsp_next [hex] lsp_prev [hex] index [dec] ver [dec] [chars] [hex] |
An internal error occurred in the maintenance of Intermediate\n\ System-to-Intermediate System ISIS link-state packet LSP linkages. |
- |
LOG_STD_SH_TECH_ACTION |
|
CLNS-3-BADIFNUM |
3-Error |
ISIS[chars]: Bad if number pdb [hex] idb [hex] if [hex] |
- |
- |
LOG_STD_SH_TECH_ACTION |
|
CLNS-3-BADPACKET |
3-Error |
[chars][chars]: [chars] [chars][chars] from [chars] [chars] |
An invalid packet was received from a neighboring router. |
- |
LOG_STD_ACTION |
|
CLNS-3-BFDCLTERR |
3-Error |
[chars]: ISIS BFD client register fails with error[dec] |
- |
- |
- |
|
CLNS-3-CASEERROR |
3-Error |
Case statement error [dec] is out of bound |
ISIS encountered an internal programming error |
isis |
LOG_STD_ACTION |
|
CLNS-3-CKSUMERR |
3-Error |
[chars][chars]: L[dec] LSP [chars] database checksum error restarting |
A hardware or software error occurred. |
- |
LOG_STD_ACTION |
|
CLNS-3-CRYPTOERR |
3-Error |
[chars][chars]: Error in filling MD5 digest for [chars] PDU |
An internal error occurred in the Intermediate System-to-Intermediate\n\ System ISIS while filling in the crypto digest for the PDU. |
- |
LOG_STD_ACTION |
|
CLNS-3-IFLIST |
3-Error |
ISIS: [chars]: [chars] |
An internal error occurred in the Intermediate System-to-Intermediate System ISIS. |
- |
LOG_STD_ACTION |
|
CLNS-3-INTERNALERR |
3-Error |
Internal error - [chars] |
An internal software error has occured |
isis |
LOG_STD_ACTION |
|
CLNS-3-IPLIST |
3-Error |
ISIS: [chars] [hex] [inet] [inet] |
An internal error occurred in the Intermediate System-to-Intermediate System ISIS. |
- |
LOG_STD_ACTION |
|
CLNS-3-LSPCHAIN |
3-Error |
[chars][chars]: non-null [chars] pointer [hex] on freed LSP index [dec] |
An internal error occurred in the Intermediate System-to-Intermediate\n\ System ISIS. |
- |
LOG_STD_ACTION |
|
CLNS-3-LSPDB |
3-Error |
[chars][chars]: Inconsistent LSPIX entry lsp [hex] index [dec] ixentry [hex] ixentry->lsp [hex] |
An internal error occurred in the Intermediate System-to-Intermediate\n\ System ISIS. |
- |
LOG_STD_SH_TECH_ACTION |
|
CLNS-3-LSPFULL |
3-Error |
[chars][chars]: L[dec] LSP filled to capacity [chars] |
A hardware or software error occurred. |
- |
LOG_STD_ACTION |
|
CLNS-3-LSPFULL_OVERLOAD |
3-Error |
[chars][chars]: Schedule L[dec] LSP to set overload bit |
The LSP was filled to capacity and after applying any lsp-full suppress options we still can't recover out of it. So we are going to set overload bit on the LSP |
- |
LOG_STD_ACTION |
|
CLNS-3-LSPGENERROR |
3-Error |
LSPGEN cache usage is inconsistent with actual LSP space usage. \n\ Cannot add [chars] |
ISIS encountered an inconsistency between LSPGEN cache usage and the LSP space. |
isis |
LOG_STD_ACTION |
|
CLNS-3-LSPGENRCTLV |
3-Error |
LSPGEN cache space is not reserved for router capability TLV. |
ISIS encountered the LSPGEN cache space is not reserved for the router capability TLV. |
isis |
LOG_STD_ACTION |
|
CLNS-3-LSPGENSPACE |
3-Error |
LSPGEN reserved space [dec] is too small. Needed [dec]. \n\ Cannot add [inet]%m |
ISIS encountered an inconsistency between LSPGEN cache usage and the LSP space. |
isis |
LOG_STD_ACTION |
|
CLNS-3-LSPIXARRMATCH |
3-Error |
[chars][chars]: LSPix entry [dec] mismatch with LSP [hex] LSP [chars] is [dec] entry [dec] |
An internal error occurred in the Intermediate System-to-Intermediate\n\ System ISIS. |
- |
LOG_STD_ACTION |
|
CLNS-3-LSPIXARRNULL |
3-Error |
[chars][chars]: LSPix entry [dec] should be null is [hex] |
An internal error occurred in the Intermediate System-to-Intermediate\n\ System ISIS. |
- |
LOG_STD_ACTION |
|
CLNS-3-LSPIXHEAD |
3-Error |
[chars][chars]: LSPix [chars] [dec] head [hex] doesn't match first prev [hex] |
An internal error occurred in the Intermediate System-to-Intermediate\n\ System ISIS. |
- |
LOG_STD_ACTION |
|
CLNS-3-LSPLIST |
3-Error |
ISIS: [chars] [dec] index [dec] |
An internal error occurred in the Intermediate System-to-Intermediate System ISIS. |
- |
LOG_STD_ACTION |
|
CLNS-3-LSPLISTERR |
3-Error |
ISIS[chars]: LSP list traversal incomplete [chars] |
An internal error occurred in the Intermediate System-to-Intermediate System ISIS. |
- |
LOG_STD_ACTION |
|
CLNS-3-LSPTOOBIG |
3-Error |
[chars][chars]: L[dec] LSP [chars] size [dec] bigger than interface [chars] MTU [dec] LSP dropped |
A software or hardware error occurred. |
- |
LOG_STD_ACTION |
|
CLNS-3-MFIBINDERR |
3-Error |
MFI label bind error reported for [inet]%m - [chars] |
MFI reported an error when ISIS tried to bind a prefix with the label |
isis |
LOG_STD_ACTION |
|
CLNS-3-MFIERR |
3-Error |
ISIS MFI API error: [chars] [chars] |
ISIS calling MFI API failed. |
isis |
LOG_STD_ACTION |
|
CLNS-3-NONZEROHT |
3-Error |
[chars][chars]: Received L[dec] LSP [chars] with [dec] secs Remaining Lifetime that contain POI TLV |
ISIS received LSP with non-zero Remaining Lifetime that contain POI TLV |
isis |
LOG_STD_ACTION |
|
CLNS-3-NSAPES |
3-Error |
Invalid NSAP type in ES table: [hec] for [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
CLNS-3-NSF_CID_FORCE_FAILURE |
3-Error |
ISIS[chars]: [chars] circuit id force to [hec] [dec] failed |
A circuit ID forced assignment failed. The requested\n\ circuit ID is in use on another interface. |
- |
"At the current time there is no work around. The problem should\n\ disappear following the next switchover." |
|
CLNS-3-NSF_CP_ADJ_CID_MISMATCH |
3-Error |
ISIS[chars]: Checkpointed ADJ circuit id mismatch for [chars] [dec]/[dec] |
- |
- |
- |
|
CLNS-3-NSF_CP_BULK_SYNC_FAIL |
3-Error |
ISIS[chars] bulk sync failed to complete |
The bulk sync of ISIS adjacency and LSP data from the active to\n\ the standby RP failed to complete successfully. Any attempt by\n\ ISIS to perform a non-stop forwarding restart may be incomplete.\n\ Note that ISIS should still converge correctly. |
- |
"At the current time there is no work around. The adjacency and\n\ LSP databases should still sync up between the active and standby RPs\n\ following completion of the bulk sync. If they do not report\n\ the output from 'show isis nsf' 'show clns neighbor' and\n\ 'show isis database' on both RPs and contact the TAC." |
|
CLNS-3-NSF_CP_ERR |
3-Error |
ISIS[chars]: Checkpoint send error [chars] |
An unrecoverable error occurred following a request to checkpoint\n\ a new or changed adjacency or LSP. |
- |
"At the current time there is no work around. If the error message\n\ continues to occur report the problem to the TAC." |
|
CLNS-3-NSF_CP_IDB_ENCODE_FAIL |
3-Error |
ISIS[chars]: Interface [chars] cannot be encoded for nsf cisco |
Adjacency and LSP information learned from this interface cannot be checkpointed due to an interface encoding error. |
- |
"Please verify that this interface type is supported for NSF in\n\ this release. If so report the problem to the TAC." |
|
CLNS-3-NSF_CP_INIT_ERR |
3-Error |
Checkpoint initialization error [chars] |
An unrecoverable error occurred during initialization of the checkpoint\n\ client. |
- |
"At the current time there is no work around. If the error message\n\ continues to occur report the problem to the TAC." |
|
CLNS-3-ONLIST |
3-Error |
ISIS: entry already threaded prev [hex] next [hex] index [dec] ver [dec] |
An internal error occurred in the Intermediate System-to-Intermediate\n\ System ISIS. |
- |
LOG_STD_ACTION |
|
CLNS-3-PATHREG |
3-Error |
[chars]: Get all for Path registration Failed |
Get all for Path registration Failed |
isis |
"This is an informational message that appears when" "Request for get all for Path Registration from ISIS failed" |
|
CLNS-3-PDBMODE_ADJDB_INCORRECT |
3-Error |
[chars][chars]: Adjacency DB should[chars] be [hex] is [hex] |
Adjacency database must match process and does not. |
isis |
LOG_STD_ACTION |
|
CLNS-3-PDBMODE_ADJDB_NOTEMPTY |
3-Error |
[chars][chars]: Adjacency DB should be empty before deleting and is not |
Adjacency database must be empty before deleting and is not. |
isis |
show clns neighbors |
|
CLNS-3-PDBMODE_TRANS_INVALID |
3-Error |
[chars][chars]: Transition target for pdb mode is invalid: \n\ current [dec] target [dec] |
ISIS process received request to transition to invalid state |
isis |
LOG_STD_ACTION |
|
CLNS-3-SIDERR |
3-Error |
ISIS SID conflict detected for [inet]%m |
There is more than one node advertising the same prefix.\n\ But the prefix SID is different. |
isis |
LOG_STD_ACTION |
|
CLNS-3-TENT |
3-Error |
[chars][chars]: [chars] |
An internal error occurred in the Intermediate System-to-Intermediate\n\ System ISIS |
- |
LOG_STD_ACTION |
|
CLNS-3-TERRRERR |
3-Error |
[chars] called on standby |
An ISIS RRR support routine has been incorrectly called on standby |
isis |
LOG_STD_ACTION |
|
CLNS-3-TEXT |
3-Error |
[chars] |
Used to display different types of Error messages |
isis |
"This is an informational message that appears when" "there is an exception" |
|
CLNS-3-VLANRANGEERR |
3-Error |
[chars]: invalid vlan range received begin [dec] end [dec] step [dec] |
An invalid vlan range has been received in lsp |
- |
LOG_STD_ACTION |
|
CLNS-4-AREALOST |
4-Warning |
[chars][chars]: Too many IS-IS areas--can\'t route to area [chars] |
- |
- |
"Reconfigure the network so that the area has fewer area addresses or\n\ split the area into multiple areas." |
|
CLNS-4-AUTH_FAIL |
4-Warning |
[chars]: [chars][chars] authentication failed |
An ISIS packetIIH CSNP PSNP or LSP was received and did not |
- |
"If the error persists check the originating router for matching " "authentication mode and password." |
|
CLNS-4-BADINTFCLNSMTU |
4-Warning |
[chars] Invalid interface clns MTU [dec] |
This message occurs if the interface MTU becomes unusable\n\ while ISIS is running on the interface. This condition\n\ maybe temporary and recoverable. |
- |
LOG_STD_ACTION |
|
CLNS-4-BADIPMSK |
4-Warning |
ISIS[chars]: Inconsistent ip prefix and mask[inet]%#m in ISIS LSP: |
The system received a link-state packet LSP which contained a |
- |
LOG_STD_SH_TECH_ACTION |
|
CLNS-4-CORRUPTLIFETIME |
4-Warning |
[chars][chars]: possible corrupted lifetime [dec] secs for L[dec] lsp [chars] from SNPA [chars] detected |
ISIS received the remaining lifetime value which is less than ZeroAgeLifetime 60 secs |
- |
LOG_STD_ACTION |
|
CLNS-4-DISALLOWED_TLV_IN_PURGE |
4-Warning |
Received disallowed TLV [dec] in Purge LSP |
ISIS received a Purge LSP containing a disallowed TLV |
isis |
"Check ISIS routing protocol for RFC6233 compliant" |
|
CLNS-4-DUPSNPA |
4-Warning |
[chars][chars]: Duplicate SNPA [chars] detected |
This may be a configuration error. |
- |
"One of the duplicate SNPA addresses needs to be corrected." |
|
CLNS-4-DUPSYSTEM |
4-Warning |
[chars][chars]: possible duplicate system ID [chars] detected |
This is a configuration error. |
- |
"One of the duplicate IDs needs to be corrected." |
|
CLNS-4-EDATFAIL |
4-Warning |
Encapsulation failed dst= [chars] |
This message can occur when an interface is down and a static\n\ neighbor entry exists in the system's CLNS routing table. If this is\n\ not the case the message indicates an internal software error. |
- |
"Check the interface. If the interface is not down and no static\n\ neighbor entry exists for that interface call your technical support\n\ representative for assistance." |
|
CLNS-4-FLEX_CFG_OVER_LIMIT |
4-Warning |
Number of flex algos reach the limit |
Number of configured flex-algos reach the limit and configuration of addtional flex-algos is not accepted in order to avoid known issues with highly scaled configuration. Limit will be removed in one of the future release. |
isis |
"Accept configuration limit." |
|
CLNS-4-GR_FAIL |
4-Warning |
[chars] failed: Invalid PDB GR Sub-block for ISIS-[chars] |
IS-IS Graceful Reload was not completed due to invalid PDB GR Sub-Block. |
- |
"If the error persists check the IS-IS configuration for that instance" |
|
CLNS-4-GR_INVALID_CLIENT |
4-Warning |
GR_INFRA failed to assign a valie client ID to IS-IS |
IS-IS received invalid client ID from GR_INFRA |
- |
"If the error persists restart the IS-IS process" |
|
CLNS-4-GR_REG_FAIL |
4-Warning |
Failed to register with GR_INFRA rc=[dec] |
IS-IS failed to register with GR_INFRA |
- |
"If the error persists restart the IS-IS process" |
|
CLNS-4-INVALIDKCKEYID |
4-Warning |
Key ID [dec] in key chain [chars] is invalid |
They Key ID configured in the key chain is out of range for ISIS. This may happen because the key chain allows Key ID values outside of the range which is acceptable for ISIS. |
isis |
"Configure a new security association with a Key ID that is in " "the range 1-65535" |
|
CLNS-4-INVALIDKCNAME |
4-Warning |
Key chain name [chars] is invalid |
The key-chain name configured under ISIS does not match global key chain configuration. |
isis |
"Fix configuration" |
|
CLNS-4-INVALIDKEY |
4-Warning |
Key ID [dec] [chars]on interface [chars] |
The ID is not found in the configured key chain |
isis |
"Configure a new security association with the Key ID" |
|
CLNS-4-LSP_MAXSEQ |
4-Warning |
[chars][chars]: attempt to exceed LSP maximum sequence number for LSP [chars] |
Attempt was made to exceed maximum sequence number for an LSP. |
- |
"Protocol will shutdown for max-lsp-lifetime + 1 minute.\n\ This is a very unlikely natural occurrence.\n\ Investigate to find the source of any out of order reception\n\ generation or incrementing of this LSP's sequence number." |
|
CLNS-4-LSPCKSUM |
4-Warning |
[chars][chars]: Bad L[dec] [chars] LSP [chars] checksum %04x received on [chars] length [dec] should be %04x bad count [dec] |
- |
- |
"If the error is in a neighboring router's memory the problem\n\ will correct itself within 15 minutes. That router will detect\n\ its internal error and regenerate the corrupted data. This\n\ case is usually indicated by a single LSP ID appearing\n\ repeatedly in these messages. The same LSP ID might appear in\n\ this message on other routers as well.\n\\n\ If data-link corruption has caused the error check the link\n\ for errors and deal with them appropriately. This case is\n\ usually indicated by a number of different LSP IDs appearing\n\ in these messages." |
|
CLNS-4-NOVALIDKEY |
4-Warning |
No valid authentication key is available |
- |
isis |
"Configure a new key" |
|
CLNS-4-NSAPIS |
4-Warning |
Invalid NSAP type in IS table: [hec] [dec] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
CLNS-4-OTV_OVERLAY_SITE_ID_MISMATCH |
4-Warning |
[chars] Site id [chars] from neighbor [chars] does not match site id [chars] received in site hellos. |
A neighbor in the same site is sending a different site ID in its overlay hellos than in its site hellos |
- |
"Verify site id configuration and/or site connecetivity " |
|
CLNS-4-OTV_SITE_FAIL |
4-Warning |
[chars]: [chars] site info update failed |
An ISIS packetIIH CSNP PSNP was received and failed to |
- |
"If the error persists check the originating router " |
|
CLNS-4-OTV_SITE_ID_MISMATCH |
4-Warning |
Site id [chars] from neighbor [chars] does not match local site id |
OTV Site ID received from a neighbor in the same site has a different site id indicating a misconfiguration error. |
- |
"Verify site id configuration and/or site connecetivity " |
|
CLNS-4-REDIRECT |
4-Warning |
Redirect found for non-route entry dst= [chars] next-hop= [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
CLNS-4-REDIST_MAX_PFX |
4-Warning |
Redistribution prefix limit has been reached \[chars]\ - [dec] prefixes |
We have reached the maximum number of redistributed prefixes |
- |
"Check if redistribution of large number of prefixes is " "desired and has not been configured by mistake" |
|
CLNS-4-REDIST_THR_PFX |
4-Warning |
Redistribution prefix threshold has been reached \[chars]\ - [dec] prefixes |
We have reached the threshold level of number of redistributed prefixes |
- |
"Check if redistribution of large number of prefixes is " "desired and has not been configured by mistake" |
|
CLNS-4-SIDRANGE |
4-Warning |
[chars] [dec] for [inet]%m is out of SRGB range [dec] via [inet] |
ISIS tried to bind a label to a prefix that is out of SRGB range |
isis |
LOG_STD_ACTION |
|
CLNS-5-ADJCHANGE |
5-Notice |
[chars][chars]: Adjacency to [chars] [chars] [chars] [chars] |
- |
- |
"This informational message normally appears as\n\ routers and links go up or down. However unexpected adjacency loss might\n\ indicate high error rates or high packet loss in the network and should\n\ be investigated." |
|
CLNS-5-ADJCLEAR |
5-Notice |
[chars][chars]: All [chars]adjacencies cleared |
- |
- |
"This informational message appears as a normal side effect\n\ of appropriate console or configuration commands." |
|
CLNS-5-EXPIREDKEY |
5-Notice |
Packet [chars] with expired Key ID [dec]. |
The Key ID in use has a lifetime and the system time is not within that lifetime |
isis |
"Configure a new key" |
|
CLNS-5-FADJCHANGE |
5-Notice |
[chars][chars]: MPLS TE Forwarding Adjacency to [chars] [chars] [chars] [chars] |
- |
- |
"This informational message normally appears as\n\ routers and links go up or down. However unexpected adjacency loss might\n\ indicate high error rates or high packet loss in the network and should\n\ be investigated." |
|
CLNS-5-FLEX_ALGO_DISABLED_NO_DEFN |
5-Notice |
[chars]: Flex-Algo [dec] is disabled for Level-[dec] no best definition available |
Flex algorithm is disabled because best definition is not available |
isis |
"This is an informational message that appears when" "flex-algo is disabled because of no best definition" |
|
CLNS-5-FLEX_DEFN_CHANGE |
5-Notice |
[chars]: Flex-Algo [dec] Level-[dec] definition changed priority [dec] source System-ID [chars] |
Flex algorithm definition changed |
isis |
"This is an informational message that appears when" "flex-algo definition changes" |
|
CLNS-5-FLEX_DEFN_ENABLE_DISABLE |
5-Notice |
[chars]: Flex-Algo [dec] is [chars] for Level-[dec] |
Flex algorithm enabled or disabled |
isis |
"This is an informational message that appears when" "flex-algo is enabled or disabled" |
|
CLNS-5-NOCRYPTOALG |
5-Notice |
Key ID [dec] in key chain [chars] does not have a cryptographic algorithm |
ISIS has been configured to use cryptographic authentication however an algorithm has not been configured |
isis |
"Configure a cryptographic-algorithm for the security association" |
|
CLNS-5-NOKEY |
5-Notice |
Key ID [dec] in key chain [chars] does not have a key |
ISIS has been configured to use cryptographic authentication however an key password has not been configured |
isis |
"Configure a key for the security association" |
|
CLNS-5-NSF_ISSU_NEGO_FAIL |
5-Notice |
ISIS NSF cancelled - ISSU negotiation failed for NSF CISCO |
ISIS cancelled the NSF restart since ISSU negotiation failed\n\ in Cisco mode. |
- |
"Review the output of 'show issu negotiated version' command" |
|
CLNS-5-NSF_NO_RP_SIGNAL |
5-Notice |
ISIS[chars] NSF cancelled - 'nsf interval' expiration pending |
ISIS cancelled the NSF restart since either the active\n\ or standby RP had not been up long enough. In Cisco mode\n\ the active RP must signal that it has been up for a minimum\n\ of 'nsf interval' seconds. For IETF mode the standby RP must\n\ be up for a minimum of 'nsf interval' seconds. |
- |
"Review the setting of the 'nsf interval' command" |
|
CLNS-5-NSF_RESTART |
5-Notice |
ISIS[chars] NSF completion |
ISIS performed an NSF restart |
- |
"This informational message appears as a normal side effect\n\ of a restart performed while NSF is enabled" |
|
CLNS-5-NSF_STATUS |
5-Notice |
[chars][chars] NSF [chars] |
This message used to print NSF status logs |
- |
"This informational message appears while NSF is enabled" |
|
CLNS-6-DFT_OPT |
6-Information |
Protocol timers for fast convergence are [chars]. |
Routing-default-optimize state |
isis |
LOG_STD_ACTION |
|
CLNS-7-DEBUG_TRACEBACK |
7-Debug |
Debug: [chars] |
Debug information. |
- |
"No action required" |
|
CLNS-7-DEBUGMSG |
7-Debug |
[chars]: %08x %08x %08x %08x %08x %08x |
Internal use only |
clns |
"Should not be seen in the field" |
|
CLNT_REG-7-LDP |
7-Debug |
ERRMSG_NOFLAGS |
- |
- |
- |
|
CLOCK_RECOVERY-4-CLOCK_FAILED |
4-Warning |
[chars] on module [dec]/[dec] failed |
This message indicates that an active recovered or enhanced clock has failed |
- |
LOG_STD_NO_ACTION |
|
CLOCK_RECOVERY-6-CLOCK_ACTIVE |
6-Information |
[chars] on module [dec]/[dec] is now active |
This message indicates that a recovered or enhanced clock has become active |
- |
LOG_STD_NO_ACTION |
|
CLOCK-3-HW_CAL_INVALID |
3-Error |
Hardware Calendar RTC Error. |
The hardware calendar contains an invalid date. The accepted range\n\ is from 1993 to 2035. |
me3600-me3800-sys |
"To correct the invalid date use the <cmdBold>calendar set<noCmdBold>\n\ command and the <cmdBold>clock read-calendar<noCmdBold> command.\n" |
|
CLS_ACC-2-CONFIG_NV_DATA |
2-Critical |
Express setup parameter committed. Default port role will be applied |
After express setup parameters are committed switch becomes a configured switch. The default port roles are automatically applied to all ports at this moment. The port role configurations may be manually modified after this point. |
firmware |
LOG_NO_ACTION |
|
CLS_ACC-2-MODE_ENTERED |
2-Critical |
Entering consoleless access mode [chars] |
Switch enters one of the consoleless access modes |
firmware |
LOG_NO_ACTION |
|
CLS_ACC-2-MODE_EXITED |
2-Critical |
Complete consoleless access from mode [chars] |
Switch exits from one of the consoleless access modes |
firmware |
LOG_NO_ACTION |
|
CLS_ACC-2-NO_PROCESS |
2-Critical |
Process creation failure |
Failed to create process to execute consoleless access |
firmware |
LOG_NO_ACTION |
|
CLS_ACC-2-SETUP_BTN_PRS |
2-Critical |
[chars] |
Pressing the switch setup button will lead an unconfigured switch to go to express setup mode. It will not have any effect on an already configured switch. Pressing the setup button for more than 5 seconds will lead a configured switch to go to direct management mode or lead an unconfigured switch to go to express setup mode |
firmware |
LOG_NO_ACTION |
|
CLS_ACC-3-CONFIG_ERROR |
3-Error |
[chars] |
Not able to correctly configure the switch for consoleless access Can't go to access mode |
firmware |
LOG_NO_ACTION |
|
CLS_ACC-3-NO_ACC_INTF |
3-Error |
Failed to find a free interface as consoleless access interface or failed to retrieve the access interface information |
Not able to find a free interface which is fit to serve as management interface for consoleless access |
firmware |
LOG_NO_ACTION |
|
CLS_ACC-3-NOMEMORY |
3-Error |
[chars] |
Memory allocation failure for executing consoleless access switch configuration commands |
firmware |
LOG_STD_ACTION |
|
CLS_ACC-3-NOSOCKET |
3-Error |
Fail to create DNS socket for consoleless access |
Socket creation failure switch is not able to go into consoleless access mode. Abort. |
firmware |
LOG_NO_ACTION |
|
CLS_ACC-3-UNABLE_TO_RESET_CONFIG |
3-Error |
[chars] |
The system is unable to reset the configuration |
firmware |
LOG_STD_ACTION |
|
CLS_ACC-3-VLAN_CREATE_FAIL |
3-Error |
Failed to allocate a free vlan as consoleless access vlan use default mamagement vlan |
Not able to find a free vlan in the range of 2-1000 to server as management vlan for consoleless access |
firmware |
LOG_NO_ACTION |
|
CLS_ACC-4-NO_HTTP_PAGE |
4-Warning |
Failed to locate HTTP page for the consoleless access mode |
Not able to locate the HTTP page corresponding to the access mode. Page is not on flash |
firmware |
LOG_NO_ACTION |
|
CLS_ACC-4-UNEXPECTEDEVENT |
4-Warning |
Switch does not support or not ready for consoleless access mode |
Switch either does not support or is not ready to enter the requested consoleless access mode |
firmware |
LOG_NO_ACTION |
|
CLS_ACC-5-CLRCFG |
5-Notice |
User cleared switch configurations under recovery mode |
Under consoleless access mode user takes an action to reset switch configuration to factory default. |
firmware |
LOG_NO_ACTION |
|
CLS_ACC-5-RSTIMG |
5-Notice |
User reset switch image to factory default image under recovery mode |
Under consoleless access mode user takes an action to reset switch image to factory default. |
firmware |
LOG_NO_ACTION |
|
CLS_ACC-7-ACC_INTF |
7-Debug |
Selected management interface: [chars] interface number: [dec] |
Selected an interface as consoleless access interface |
firmware |
LOG_NO_ACTION |
|
CLS_ACC-7-ACC_VLAN |
7-Debug |
Selected vlan [dec] for consoleless access |
A new vlan is created to only include the management interface Vlan creation successful |
firmware |
LOG_NO_ACTION |
|
CLS_ACC-7-CONFIG |
7-Debug |
Save access intf config: if: [chars] port num: [dec] vlan [dec] admin-down?:[dec] |
Save interface configurations these configurations will be restored when consoleless access exits and returns the interface |
firmware |
LOG_NO_ACTION |
|
CLS_ACC-7-CONFIG_SUCCESS |
7-Debug |
[chars] |
Consoleless access mgmt interface successfully configured or its original configuration successfully restored |
firmware |
LOG_NO_ACTION |
|
CLS-3-BOGUSOP |
3-Error |
Unknown CLS verb for [chars] context DlcOpcodeT=%04x |
A bad opcode was generated by the DLC for the STN or CEP. |
- |
LOG_STD_ACTION |
|
CLS-3-CLSFAIL |
3-Error |
CLS: Assertion failed: [chars] |
A software or hardware error occurred. |
- |
LOG_STD_ACTION |
|
CLS-3-CLSMSG |
3-Error |
[chars] |
A software error detected while manipulating CLSIMsg objects. |
- |
LOG_STD_ACTION |
|
CLSDR-3-ERRRTN |
3-Error |
[chars] failed error 0x[hec] |
- |
- |
"Refer to CLSI software documentation for more information about this\n\ error. Report this error to your technical support representative." |
|
CLSDR-3-INCORRECTPORT |
3-Error |
Incorrect port pointer in USapId |
- |
- |
LOG_STD_ACTION |
|
CLSDR-3-MSGERR |
3-Error |
[chars] couldn't get a message |
- |
- |
LOG_STD_ACTION |
|
CLSDR-3-NOCEP |
3-Error |
Cannot found cep in free pool |
A software or hardware error occurred. |
- |
LOG_STD_ACTION |
|
CLSDR-3-NOCLSSERVER |
3-Error |
unable to start the Server process |
Could not start the CLSDRIVER process possibly due to a resource\n\ problem. The subsystem using CLSDRIVER does not work. |
- |
- |
|
CLSDR-3-NODLUCREATE |
3-Error |
Cannot create DLU for this type [dec] |
- |
- |
LOG_STD_ACTION |
|
CLSDR-3-NOINIT |
3-Error |
CLSDRIVER not initialized |
A CLSDRIVER initialization failed earlier. Trying to use the driver\n\ now results in an error condition. |
- |
- |
|
CLSDR-3-NOPORTCREATE |
3-Error |
Cannot create PORT structure |
The CLSDRIVER cannot enable this port for processing. |
- |
"Try rebooting the router. " LOG_STD_ACTION |
|
CLSDR-3-NOREMOVECEP |
3-Error |
RemoveCep : Cep 0x[hec] not on list |
- |
- |
LOG_STD_ACTION |
|
CLSDR-3-NOREMOVEPORT |
3-Error |
RemovePort: port 0x[hec] not on list |
- |
- |
LOG_STD_ACTION |
|
CLSDR-3-WRONGMSG |
3-Error |
Should never be here cls message type unknown 0x[hec] |
The CLS message type is unknown to the destination logical unit\n\ DLU. |
- |
LOG_STD_ACTION |
|
CLUE-3-CHECKSUM_ERROR |
3-Error |
CLUE record checksum error in record id [dec] record starting address [hex] new checksum [hex] previous checksum [hex] |
CLUE record stored in the CLUE memory had a bad checksum. The \n\ CLUE record was modified by a CLUE client but not committed or by \n\ unknown memory corruption. The CLUE record cannot be accessed. |
clue |
"Internal CLUE Client software may automatically rectify the error. \n\ However if the error persists reload the unit." |
|
CLUE-3-CLIENT_REGISTRY_FULL |
3-Error |
Maximum of [dec] CLUE clients registered. Cannot register callback [hex] |
- |
clue |
"Copy the error message exactly as it appears attach outputs from the \n\ show clue and show tech commands and report the error to your technical \n\ support representative." |
|
CLUE-3-COMMIT_FAILED |
3-Error |
CLUE cannot commit record id [dec] |
The given CLUE record was not committed in the CLUE storage memory.\n\ CLUE record was not allocated by the CLUE client before committing or \n\ there was an error in the internal CLUE record index table. The CLUE \n\ record cannot be accessed. |
clue |
"Internal CLUE software may automatically rectify the error. However \n\ if the error persists copy the error message exactly as it appears and \n\ report it to your technical support representative." |
|
CLUE-3-EOR_CORRUPT |
3-Error |
CLUE record corruption in end of record field record id [dec] record starting address [hex] |
CLUE record's end of record delimiter was corrupted in the CLUE \n\ storage memory. The CLUE record was over-written by the\n\ previous CLUE record or by an unknown memory corruption. The \n\ CLUE record cannot be accessed. |
clue |
"Internal CLUE Client software may automatically rectify the error. \n\ However if the error persists reload the unit." |
|
CLUE-3-INDEX_BUILD_FAIL |
3-Error |
Failed to build CLUE internal record index due to [chars] |
CLUE expected existence of valid CLUE records in CLUE storage when \n\ building internal record index table. CLUE will fail to build the index\n\ table when CLUE storage does not exist or any CLUE record within the\n\ CLUE storage has some data corruption. CLUE service will not be \n\ available and any data in the CLUE storage cannot be accessed. |
clue |
"Internal CLUE Client software may automatically rectify the error. \n\ However if the error persists reload the unit." |
|
CLUE-3-INIT_ERROR |
3-Error |
Failed to initialise the reserved memory for new CLUE context due to [chars] |
- |
clue |
"Copy the error message exactly as it appears attach outputs from the \n\ show clue and show tech commands and report the error to your technical \n\ support representative." |
|
CLUE-3-INTERNAL_SW_ERROR |
3-Error |
[chars] |
Internal Compact Local Unit Exchange CLUE software error reported |
clue |
"Copy the error message exactly as it appears attach outputs from the \n\ show clue and show tech commands and report the error to your technical \n\ support representative." |
|
CLUE-3-INVALID_AREA |
3-Error |
Either address [hex] or size [dec] reserved for CLUE storage area is invalid |
- |
clue |
"Copy the error message exactly as it appears attach outputs from the \n\ show clue and show tech commands and report the error to your technical \n\ support representative." |
|
CLUE-3-INVALID_REC_DATA_SIZE |
3-Error |
CLUE record size [dec] is invalid to allocate CLUE record [dec] |
- |
clue |
"Copy the error message exactly as it appears attach outputs from the \n\ show clue and show tech commands and report the error to your technical \n\ support representative." |
|
CLUE-3-INVALID_REC_ID |
3-Error |
Invalid CLUE record id [dec] has been received so CLUE cannot [chars] it |
- |
clue |
"Copy the error message exactly as it appears attach outputs from the \n\ show clue and show tech commands and report the error to your technical \n\ support representative." |
|
CLUE-3-NO_SIGNATURE |
3-Error |
CLUE cannot [chars] record id [dec] |
The given CLUE record was not serviced. CLUE storage was not \n\ available or the CLUE storage signature was invalid. |
clue |
"Internal CLUE software may automatically rectify the error. However \n\ if the error persists copy the error message exactly as it appears and \n\ report it to your technical support representative." |
|
CLUE-3-NOT_ENOUGH_CLUE_STORAGE |
3-Error |
CLUE storage has not enough space to allocate record id [dec] and data size [dec] |
- |
clue |
"Copy the error message exactly as it appears attach outputs from the \n\ show clue and show tech commands and report the error to your technical \n\ support representative." |
|
CLUE-3-NOT_ENOUGH_MEMORY |
3-Error |
[dec]-bytes of local memory has not enough space left to reserve [dec]-bytes of CLUE storage |
Local memory was not big enough to reserve the required Compact Local \n\ Unit Exchange CLUE storage space. |
clue |
"Add more local memory." |
|
CLUE-3-SOR_CORRUPT |
3-Error |
CLUE record corruption in start of record field record id [dec] record starting address [hex] |
CLUE record's start of record delimiter was corrupted in the CLUE \n\ storage memory. The CLUE record was over-written by the\n\ previous CLUE record or by an unknown memory corruption. The \n\ CLUE record cannot be accessed. |
clue |
"Internal CLUE Client software may automatically rectify the error. \n\ However if the error persists reload the unit." |
|
CM_MONITOR-5-DNS_KILL |
5-Notice |
Terminating DNS process |
A hardware or software error occurred. |
- |
LOG_STD_ACTION |
|
CM_MONITOR-5-DNS_RESP |
5-Notice |
Sending DNS response to [inet] request was for [inet] |
- |
- |
- |
|
CM_MONITOR-5-DNS_START |
5-Notice |
Starting DNS process |
A hardware or software error occurred. |
- |
LOG_STD_ACTION |
|
CM_REDUC_MODE-4-BM_ATTR_NOT_MAINTAIN |
4-Warning |
Attribute masks are not maintained when entering battery mode. CM MAC addr <[enet]> |
Attribute masks are not maintained when entering battery mode \n |
cbr-application |
LOG_STD_NO_ACTION |
|
CM_REDUC_MODE-4-BM_NO_AVAILABLE_DBG |
4-Warning |
Entering battery mode failed since no available RBG. CM MAC addr <[enet]> |
Entering battery mode failed since no available RBG \n |
cbr-application |
"Please inspect the configuration file and configured " "available RBG" |
|
CM_REDUC_MODE-4-BM_OPERATION_EXCEED_MAX_COUNT |
4-Warning |
Enter into/exit BM mode failed for CM MAC addr <[enet]> |
There maybe resource limitation which induce BM operation failure.\n |
cbr-application |
LOG_STD_NO_ACTION |
|
CM_REDUC_MODE-4-BM_ORG_RCC_INAVAILABLE |
4-Warning |
Exiting battery mode failed since original rcc unavailable. CM MAC addr <[enet]> |
Exiting battery mode failed since original rcc unavailable \n |
cbr-application |
LOG_STD_NO_ACTION |
|
CM_REDUC_MODE-4-DBC_REJECT_CAUSE_CM_OFFLINE |
4-Warning |
CM [enet] forcely offline because the operation failed as DBC rejected the invalid request DBC client [dec] |
DBC failed to change CM BG because the operation was rejected as one invalid request. That cause the CM was not permitted to register again to the original BG. Mark CM offline to avoid CM stuck in reduce mode |
cbr-application |
LOG_STD_NO_ACTION |
|
CM_REDUC_MODE-4-EM_ATTR_NOT_MAINTAIN |
4-Warning |
Attribute masks are not maintained when entering EM mode. CM MAC addr <[enet]> |
Attribute masks are not maintained when entering EM mode \n |
cbr-application |
LOG_STD_NO_ACTION |
|
CM_REDUC_MODE-4-EM_INVALID_EM_REQ |
4-Warning |
Receive an invalid EM request message from CM MAC addr <[enet]> request power mode [dec]. |
Receive invalid requested power mode from CM\n |
cbr-application |
LOG_STD_NO_ACTION |
|
CM_REDUC_MODE-4-EM_NO_AVAILABLE_DBG |
4-Warning |
Entering EM mode failed since no available RBG. CM MAC addr <[enet]> |
Entering EM mode failed since no available RBG \n |
cbr-application |
"Please inspect the configuration file" |
|
CM_SYNC-3-NO_BUFFER |
3-Error |
Unable to transmit message type [dec] from [chars] |
A transmit error occurred while sending msg to other CPU due to non-availability of buffer |
- |
LOG_STD_ACTION |
|
CM_SYNC-3-TRANSMIT_ERROR |
3-Error |
Unable to transmit message type [dec] from [chars] |
A transmit error occurred while sending msg to other CPU due to msg translation |
- |
LOG_STD_ACTION |
|
CM622_CM155-4-ATMCLKINT |
4-Warning |
[dec]/[dec] ATM Clock Internal Set on [dec]/[dec] too |
CM155 ATM Clock Internal is enabled for the other channel \ on the same framer too the framer defines one bit for \ both channels. |
gsr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CM622_CM155-4-FRMROP |
4-Warning |
Error: [dec]/[dec] [chars] value=0x%04x |
Linecard ATM driver framer operation errors. |
gsr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CM622_CM155-4-FWCKSUM |
4-Warning |
Port [dec]: [chars] SAR firmware selftest failure expected 0x%04x obtained 0x%04x |
Linecard ATM SAR firmware checksum errors. |
gsr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CM622_CM155-4-OP |
4-Warning |
Error: [dec]/[dec] [chars] |
Linecard ATM driver general operation errors. |
gsr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CM622_CM155-4-RPCMD |
4-Warning |
[dec]/[dec] [chars] command error: [chars] |
Linecard ATM driver handles RP command errors. |
gsr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CM622_CM155-4-RXSARIND |
4-Warning |
[dec]/[dec] RX SAR doing [chars] error: [chars] indication=0x%08x 0x%08x 0x%08x |
Linecard ATM driver RX SAR indication errors. |
gsr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CM622_CM155-4-SAROP |
4-Warning |
Port [dec]: [chars] SAR doing [chars] error: [chars] |
Linecard ATM driver SAR operation error. |
gsr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CM622_CM155-4-TXSARIND |
4-Warning |
Port [dec]: TX SAR [chars] command error: [chars] indication=0x%08x |
Linecard ATM driver TX SAR indication error. |
gsr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CM622_CM155-4-VCCLOSE |
4-Warning |
[dec]/[dec] VC:[dec] is close pending |
The VC is in the TX SAR close pending state. |
gsr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CM622_CM155-4-VCCMD |
4-Warning |
[dec]/[dec] VC:[dec] [chars] error cause: [chars] |
CM622/CM155 ATM SAR VC operation error. |
gsr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CM622_CM155-4-VCTYPE |
4-Warning |
[dec]/[dec] VC:[dec] unsupported vc encapsulation type=[dec] |
CM622/CM155 ATM SAR VC operation error. |
gsr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CMANCC-2-CRASHDUMP |
2-Critical |
Fatal error calling crashdump error: [dec] [chars] |
A fatal condition has occurred causing IOS to crashdump. IOS will\n\ be restarted automatically. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
CMANCC-2-CRASHDUMP |
2-Critical |
Fatal error calling crashdump error: [dec] [chars] |
A fatal condition has occurred causing IOS to crashdump. IOS will\n\ be restarted automatically. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
CMANCC-3-MSGDISPATCH |
3-Error |
Unable to dispatch received message from Chassis Manager |
An unexpected condition has occurred while IOS was trying to dispatch\n\ a message received from the Chassis Manager. |
iosxe-chassismgr |
"Verify that all local components are in the proper operational state.\n\ If any inconsistency is found it may be corrected by offlinine and\n\ restart of the effected component SPA Carrier Card" |
|
CMANCC-3-MSGDISPATCH |
3-Error |
Unable to dispatch received message from Chassis Manager |
An unexpected condition has occurred while IOS was trying to dispatch\n\ a message received from the Chassis Manager. |
iosxe-chassismgr |
"Verify that all local components are in the proper operational state.\n\ If any inconsistency is found it may be corrected by offlinine and\n\ restart of the effected component SPA Carrier Card" |
|
CMANCC-3-MSGIPCERR |
3-Error |
Unable to process received IPC messages from Chassis Manager\n\ error: [chars] |
An unexpected condition has occurred while IOS trying to process a\n\ received IPC message from Chassis Manager. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
CMANCC-3-MSGIPCERR |
3-Error |
Unable to process received IPC messages from Chassis Manager\n\ error: [chars] |
An unexpected condition has occurred while IOS trying to process a\n\ received IPC message from Chassis Manager. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
CMANCC-3-UNEXPECTEDEVENT |
3-Error |
UDI Auth Process received unknown event maj [hec] min [hec]. |
UDI auth process has registered to be notified when a process \n\ boolean change event occurs in the router. This message indicates \n\ that this process received an event it did not know how to handle. |
iosxe-chassismgr |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
CMANCC-3-UNEXPECTEDEVENT |
3-Error |
UDI Auth Process received unknown event maj [hec] min [hec]. |
UDI auth process has registered to be notified when a process \n\ boolean change event occurs in the router. This message indicates \n\ that this process received an event it did not know how to handle. |
iosxe-chassismgr |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
CMANRP-2-CRASHDUMP |
2-Critical |
Fatal error calling crashdump error: [dec] [chars] |
A fatal condition has occurred causing IOS to crashdump. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
CMANRP-3-CMREADFAIL |
3-Error |
Read from cpld_ha fd [dec] failed errno [dec] event cnt [dec] |
Read from cpld_ha device returned 0 bytes. |
- |
LOG_STD_NO_ACTION |
|
CMANRP-3-CMSWVERINFO |
3-Error |
Unable to process software version information using file [chars]. Reason: [chars]. Error: [dec] |
An unexpected condition has occurred while IOS was trying to process the software version information file. As a result version information may not be available to an SNMP Manager |
iosxe-chassismgr |
LOG_STD_NO_ACTION |
|
CMANRP-3-INVERR |
3-Error |
Unable to process chassis inventory for file [chars] slot [dec] [chars] error [dec]. Some SPA's may not be fully configured |
An unexpected condition has occurred while IOS is trying to process the chassis inventory on startup. IOS can not determine the type and number of all Carrier Cards and SPA's present in the system. Some configuration relating to these SPA's may not be applied and leave the system in an inconsistent state. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
CMANRP-3-INVERRSPA |
3-Error |
Unable to process chassis inventory for file [chars] SPA subslot [dec]/[dec] [chars] error [dec]. Some SPA's may not be fully configured |
An unexpected condition has occurred while IOS is trying to process the chassis inventory on startup. IOS can not determine the type and number of all Carrier Cards and SPA's present in the system. Some configuration relating to these SPA's may not be applied and leave the system in an inconsistent state. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
CMANRP-3-MSGDISPATCH |
3-Error |
Unable to dispatch received TDL message '[chars]' from Chassis Manager. LUID: [chars] |
An unexpected condition has occurred while IOS is trying to dispatch to the TDL message handler functions for received TDL messages from Chassis Manager. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
CMANRP-3-MSGDISPATCHNULL |
3-Error |
Received NULL TDL message from IOS |
An unexpected condition in which IOS has received a NULL TDL message from Chassis Manager. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
CMANRP-3-MSGIPCERR |
3-Error |
Unable to process received IPC messages from Chassis Manager error: [chars] |
An unexpected condition has occurred while IOS is trying to process a received IPC message from Chassis Manager. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
CMANRP-3-SMU_COMMITTED_FAILED |
3-Error |
'install commit' failed [dec] during reload. |
There are uncommitted SMU activity in the system reload will remove this SMU activity with user input install commit is tried but failed with the error code mentioned in message. |
iosxe-p-smu |
LOG_STD_NO_ACTION |
|
CMANRP-3-UDEVPERMS |
3-Error |
An invalid permissions value [chars] was found in a udev file |
The udev files for a particular filesystem contain a description the file system. If the permissions attribute is not recognized then this file system may run with incorrect permissions. |
iosxe-chassismgr |
LOG_STD_NO_ACTION |
|
CMANRP-4-SMU_UNCOMMITTED |
4-Warning |
There are uncommitted SMU abort reload and 'install commit' if required |
There are uncommitted SMU activity in the system reload will remove this SMU activity use 'install commit' to make it persistent. |
iosxe-p-smu |
LOG_STD_NO_ACTION |
|
CMANRP-6-CMHASTATUS |
6-Information |
RP switchover [chars] |
RP switchover events received by chassis manager. |
- |
LOG_STD_NO_ACTION |
|
CMANRP-6-CMNOTSWITCH |
6-Information |
RP is not doing switchover |
Read from cpld_ha device indicate no switchover event. |
- |
LOG_STD_NO_ACTION |
|
CMANRP-6-CMSTATUS |
6-Information |
Chassis Manager Process is [chars] |
The current status of Chassis Manager Process. |
- |
LOG_STD_NO_ACTION |
|
CMANRP-6-CMSWREAD |
6-Information |
RP switchover event triggered |
RP switchover event triggered by IOS fastpath. |
- |
LOG_STD_NO_ACTION |
|
CMANRP-6-SMU_COMMITTED |
6-Information |
'install commit' is success. |
There were uncommitted SMU activity in the system reload will remove this SMU activity with user input install commit is done. |
iosxe-p-smu |
LOG_STD_NO_ACTION |
|
CMCC-3-CFGCMDDROPPED |
3-Error |
Config queue is full command was dropped slot [dec] |
Sending a config command was retried. The receiving queues were still full after retries therefore the command was dropped. |
cip |
"Issue the<Bold>debug channel events<NoBold> command and " "try each of the following tasks in sequence. If an action " "corrects the problem the remaining tasks do not need to be " "performed.\n" "<Bullet><par>Reissue the configuration command. " "<Bullet><par>Clear the interface using the <Bold>clear interface<NoBold> " "command. " "<Bullet><par>Reload the microcode. " "<Bullet><par>Reload the router.\n" "<Body><par>If the error still occurs copy the error message exactly " "as it appears. Record the output from the following commands:\n" "<Bullet><par><Bold>show tech <NoBold> " "<Bullet><par><Bold>show log <NoBold>\n" "<Body><par>Provide this information to your technical support " "representative." |
|
CMCC-3-IPCBUFFAIL |
3-Error |
Unable to obtain IPC resources |
The InterProcess Communication IPC service used by the TN3270 |
- |
"The CMCC will not load properly. Try the reload command again. If " "this message recurs call your technical support representative for " "assistance." |
|
CMCC-3-IPCDNSFAIL |
3-Error |
DNS lookup failed - [chars] |
The InterProcess Communication IPC service used by the TN3270 |
- |
"Verify that the proper revisions of code are selected." |
|
CMCC-3-IPCINITFAIL |
3-Error |
Unable to initialize IPC [chars] services |
The InterProcess Communication IPC service used by the TN3270 |
- |
"The CMCC will not load properly. The router must be reloaded to clear " "the problem." |
|
CMCC-3-IPCINVALID |
3-Error |
Invalid IPC request [dec] received from [hec] |
The InterProcess Communication IPC service used by the TN3270 |
- |
"Verify that the proper revisions of code are selected." |
|
CMCC-3-RSETFAIL |
3-Error |
Interface [chars]: Error %-04x [chars] |
An error occurred sending an interface enable or disable command. |
cip |
"The interface was reset by the software and the condition " "rectified. If that did not occur then issue the " "<Bold>debug channel events<NoBold> command and " "try each of the following tasks in sequence. If an action " "corrects the problem the remaining tasks do not need to be " "performed.\n" "<Bullet><par>Clear the interface using the <Bold>clear interface<NoBold> " "command. " "<Bullet><par>Reload the microcode. " "<Bullet><par>Reload the router.\n" "<Body><par>If the error still occurs copy the error message exactly " "as it appears. Record the output from the following commands:\n" "<Bullet><par><Bold>show tech <NoBold> " "<Bullet><par><Bold>show log <NoBold>\n" "<Body><par>Provide this information to your technical support " "representative." |
|
CMCC-3-UNKENCAP |
3-Error |
Interface [chars]: unknown encapsulated msg[dec] len[dec] |
- |
- |
- |
|
CMCC-4-CFGFAIL |
4-Warning |
Interface [chars]: configuration command [chars] [chars] failed |
An encapsulated control message had a size smaller than the minimum expected size. The message was dropped. |
cip |
LOG_STD_SH_TECH_ACTION |
|
CMCC-4-IPCDNSNOIPADDR |
4-Warning |
DNS lookup failed - the DNS server has no entry for hostname [chars] |
The InterProcess Communication IPC service used by the TN3270 |
- |
"Verify that the DNS server entries are up to date." |
|
CMCC-5-IPCDNSQUERYTIMEDOUT |
5-Notice |
DNS lookup failed - query to DNS server [chars] timed out |
The InterProcess Communication IPC service used by the TN3270 |
- |
"Check the status of the DNS server." |
|
CMCC-5-IPCDNSSERVERUNREACHABLE |
5-Notice |
DNS lookup failed - DNS server [inet] is unreachable |
The InterProcess Communication IPC service used by the TN3270 |
- |
"Check for available routes to DNS servers." |
|
CMCC-6-ADAPTERCHNG |
6-Information |
Interface [chars]: adapter type changed from [chars] to [chars] |
The <Bold> channel-protocol <NoBold> configuration command sent after a reset failed to complete successfully. |
cip |
"The channel data transfer rate was reset to the default value. Reissue " "the configuration command." |
|
CMEXML-3-ABORTEXEC |
3-Error |
\ CME XML Client Request Aborted request [chars]\n |
- |
- |
- |
|
CMEXML-3-ERREXEC |
3-Error |
\ CME XML Client Request Failed at [dec] request [chars]\n |
- |
- |
- |
|
CMEXML-6-STARTEXEC |
6-Information |
\ CME XML Client Request Start request [chars]\n |
- |
- |
- |
|
CMM-3-CONFIG_SIZE_EXCEED_LIMIT |
3-Error |
Current config size is greater than supported size [dec]. Config CLI will not be synced to Centrally Managed Mobility Agents. |
The Maximum supported configuration size which can be synced has been reached hence no new configuration will be synced from Mobility Controller to Centrally Managed Mobility Agents. |
accsw-ease-of-use |
"Save the current configuration on the Mobility " "Controller so that the existing configuration can be synced to " "the Centrally Managed Mobility Agents." |
|
CMM-3-REGISTRY_ADD_ERR |
3-Error |
Failure in adding to [chars] registry |
Could not add a function to the registry |
accsw-ease-of-use |
LOG_STD_NO_ACTION |
|
CMM-6-CENTRAL_MANAGMENT_DISABLED |
6-Information |
This Mobility Agent is no more Centrally Managed. |
This Mobility Agent is no more Centrally Managed as the feature has either been disabled on the Controller or the Controller does not support this capability. Check the output of show wireless mobility summary on controller. |
accsw-ease-of-use |
"show wireless mobility " "summary" |
|
CMM-6-CONFIG_NOT_ALLOWED |
6-Information |
Centrally Managed MA: \[chars]\ cannot be locally configured. |
This Mobility Agent is Centrally Managed hence this CLI is not allowed. Configuration needs to be done on the Mobility Controller. |
accsw-ease-of-use |
"show cmm config" |
|
CMM-6-CONFIG_SYNC_SAVE_MSG |
6-Information |
Saving config rev#%llu received from Mobility Controller. |
On receiving config from Mobility Controller the config is automatically saved on the Mobility Agent |
accsw-ease-of-use |
- |
|
CMM-6-WIRELESS_MANAGEMENT_IP_CHANGED |
6-Information |
The Mobility Controller wireless management interface IP Address has been modified. Please reload the Mobility Controller. |
The Mobility Controller wireless management interface IP Address has been modified. Please reload the Mobility Controller as this IP Address is used as the Domain ID for Central Management. |
accsw-ease-of-use |
LOG_STD_NO_ACTION |
|
CMP-4-MEM_CMPIP_ADDR_CONFLICT |
4-Warning |
Conflict with CMP IP address [inet] Reissuing a new CMP IP address to member [dec] |
The cluster commander found a conflict with the assigned CMP IP address of the member. A new unique CMP IP address is assigned to the member. |
c2900-xl-cluster |
"This is a warning message only. The commander already assigned a new unique address to the member. Please clear any open TCP connections on the member using 'clear tcp' command." |
|
CMP-5-ADD |
5-Notice |
The Device is added to the cluster Cluster Name: [chars] CMDR IP Address [inet] |
The device is added to the cluster |
c2900-xl-cluster |
LOG_STD_NO_ACTION |
|
CMP-5-MEMBER_CONFIG_UPDATE |
5-Notice |
Received member configuration from member [dec] |
Received member configuration |
c2900-xl-cluster |
LOG_STD_NO_ACTION |
|
CMP-5-MGMT_VLAN_CHNG |
5-Notice |
The management vlan has been changed to [dec] |
The management vlan has been changed |
c2900-xl-cluster |
LOG_STD_NO_ACTION |
|
CMP-5-NBR_UPD_SIZE_TOO_BIG |
5-Notice |
Number of neighbors in neighbor update is [dec] maximum number of neighbors allowed in neighbor update is [dec] |
The number of cluster neighbors in the clustering neighbor update packet exceeds the number of neighbors supported by the clustering module design |
c2900-xl-cluster |
LOG_STD_NO_ACTION |
|
CMP-5-REMOVE |
5-Notice |
The Device is removed from the cluster Cluster Name: [chars] |
The device is removed from the cluster |
c2900-xl-cluster |
LOG_STD_NO_ACTION |
|
CMTS_INFRA_LCHA-3-DMP_MCAST_STATUS_TBL_NULL |
3-Error |
Error:mcast_flow_status_tbl is NULL! |
mcast_flow_status_tbl not initialized |
cbr-cmts-infra |
LOG_STD_SH_TECH_ACTION |
|
CMTS_INFRA_LCHA-3-SYNC_CONFIG_LIST_CREATION_FAILURE |
3-Error |
DOCSIS SYNC configuration list creation failure current slot [dec] |
Failed to create the list of LCHA DOCSIS SYNC configuration |
cbr-cmts-infra |
LOG_STD_SH_TECH_ACTION |
|
CMTS_INFRA_LCHA-3-SYNC_CONFIG_LIST_INVALID |
3-Error |
DOCSIS SYNC configuration list is invalid current slot [dec] virtual slot [dec] |
The list of LCHA DOCSIS SYNC configuration is invalid |
cbr-cmts-infra |
LOG_STD_SH_TECH_ACTION |
|
CMTS_INFRA_LCHA-4-RECONCIL_CM_CDM_MISMATCH |
4-Warning |
LCHA CDMAN to LC CM Reconciliation: Mac: [enet] Reason: [chars] |
Mis-match between CDMAN and LC CM data |
cbr-cmts-infra |
LOG_STD_SH_TECH_ACTION |
|
CMTS_INFRA_LCHA-4-RECONCIL_DMP_MISMATCH |
4-Warning |
LCHA CDMAN to LC DMP Reconciliation: HW-Flow: [dec] Reason: [chars] |
Mis-match between CDMAN and LC DMP data |
cbr-cmts-infra |
LOG_STD_SH_TECH_ACTION |
|
CMTS_INFRA_LCHA-4-RECONCIL_UMP_MISMATCH |
4-Warning |
LCHA CDMAN to LC UMP Reconciliation: Service-Flow: [dec] Reason: [chars] |
Mis-match between CDMAN and LC UMP data |
cbr-cmts-infra |
LOG_STD_SH_TECH_ACTION |
|
CMTS_INFRA-3-DBG_BG_INTF_PER_CTRL_EXCD |
3-Error |
WB interface resource on [dec]/[dec]/[dec] Exhausted |
Unable to allocate additional WB Interface. |
cbr-cmts-infra |
LOG_STD_SH_TECH_ACTION |
|
CMTS_INFRA-3-FPM_ERR |
3-Error |
[chars]: CM [enet] profile [dec] |
A service flow for the modem has been mapped to a profile that is not configured for the ofdm channel. |
cbr-cmts-infra |
"Remove or correct the ofdm-flow-to-profile " "configuration for the modem." |
|
CMTS_INFRA-3-NOENTROPY_PROC |
3-Error |
Failed to create process to create entropy |
CLC doesn't receive HW entropy from RP for the last 10 minutes. |
cbr-cmts-infra |
LOG_STD_SH_TECH_ACTION |
|
CMTS_INFRA-3-NORAND64 |
3-Error |
Failed to read entropy from CPU |
Failure to retrieve entropy for random number generator. |
cbr-cmts-infra |
LOG_STD_SH_TECH_ACTION |
|
CMTS_INFRA-3-NORANDNIST |
3-Error |
Failed to generate random number |
Failure to generate random number. |
cbr-cmts-infra |
LOG_STD_SH_TECH_ACTION |
|
CMTS_INFRA-3-NORES |
3-Error |
[chars] [dec] [dec] |
An internal software error occurred. |
cbr-cmts-infra |
LOG_STD_SH_TECH_ACTION |
|
CMTS_INFRA-3-NORES_BG_EXCD |
3-Error |
[chars] [dec] [dec] |
An internal software error occurred. |
cbr-cmts-infra |
LOG_STD_SH_TECH_ACTION |
|
CMTS_INFRA-3-NOTAMC |
3-Error |
Failed to read entropy from ACT2 for [chars] err: 0x[hec] |
Failure to retrieve entropy for random number generator. |
cbr-cmts-infra |
LOG_STD_SH_TECH_ACTION |
|
CMTS_INFRA-3-PNM_INVALID_FREQ_SPAN_CFG |
3-Error |
PNM: Capture tests cannot be started on port [dec]/[dec]/[dec] dev [dec] - Current capcfg freq: [dec]Hz span: [dec]Hz. For this user configured center freq [dec]Hz expected span value should not be more than [dec]Hz. |
PNM capture configuration has invalid values capture start rejected |
cbr-cmts-infra |
"Set the capture configuration center frequency " "and/or span to valid range as per suggested recommendations in msg to" " run captures." |
|
CMTS_INFRA-3-PNM_ZERO_FREQ_SPAN_CFG |
3-Error |
PNM: Capture tests cannot be started on port [dec]/[dec]/[dec] dev [dec] - both capture config center frequency: [dec]Hz and span: [dec]Hz should be non zero or no meaningful data can be captured by CLC. |
PNM Capture center frequency and span cannot be zero to run captures |
cbr-cmts-infra |
"Set non zero valid values for capture configuration " "center frequency and span paramters to run captures." |
|
CMTS_INFRA-3-REALLOC_VALID_FLOW |
3-Error |
Attempt to realloc valid flow: [dec] [enet] md[dec] sid[dec] sfid[dec] dsid[dec]. req: [enet] |
An internal software error occurred. |
cbr-cmts-infra |
LOG_STD_SH_TECH_ACTION |
|
CMTS_INFRA-3-RELOAD |
3-Error |
Configuration changed for Gemini 1 ports on card in slot [dec]. Please reload the card for the changes to take effect and save the configuration. |
OFDMA channel bandwidth is too small to support the minimum number of mini-slots or no minislot to schedule IR/FR |
cbr-cmts-infra |
LOG_STD_SH_TECH_ACTION |
|
CMTS_INFRA-5-DMP_INVAL_IDX |
5-Notice |
Invalid Index: [dec] >= [dec] |
An internal software error occurred and an Invalid Index value was used. Such errors typically happen due to timing issues and can be ignored if only seen infrequently. Report the error to Tech Support if seen repeatedly. |
cbr-cmts-infra |
LOG_STD_SH_TECH_ACTION |
|
CMTS_INFRA-6-CTRLR_CHAN_CONFIG_CONTINUOUS_CHANGE |
6-Information |
[chars] channel [dec]/0/[dec]:[dec] configuration is being continuously changed or it's admin state is being continuously toggled causing the system to enter an indeterminate state recommend pacing controller/channel config changes. |
Controller/channel config is being continuously changed or it's admin state is being toggled this can put the system in an indeterminate state causing the modems to fall offline online or not come online. |
cbr-cmts-infra |
"Pace controller/channel configuration changes giving the system enough time to react to these events recommeded wait time is 30 seconds between config operations on controllers/channels use the recommendation to toggle channel admin state if modems don't come online or are partially online." |
|
CMTS_INFRA-6-CTRLR_PORT_ADMIN_STATE_LOCKED |
6-Information |
User attempted to perform a no shut on Integrated-Cable [dec]/0/[dec] [dec] seconds after a shut event. This does not allow resources sufficient time to clean up. Calculated wait time was [dec] seconds between shut/no shut config operations on this controller. |
Controller is attempting to be no shut too soon after a shut event. This oepration was blocked to prevent resources from being reused before they have been cleaned up. |
cbr-cmts-infra |
- |
|
CMTS_INFRA-6-DELETE_HW_FLOW_MAC_MISMATCH |
6-Information |
[chars] [dec] [enet]:[enet] |
An internal software error occurred. |
cbr-cmts-infra |
LOG_STD_SH_TECH_ACTION |
|
CMTS_LIC-1-BAD_LICENSE_STORAGE |
1-Alert |
License Storage Error on Linecard [dec]/[dec] |
The Line card license storage status is BAD |
PLATFORM |
"Check the line card license details" " If the problem is not fixed by multiple reinstall attempts" " board RMA may be required" |
|
CMTS_LIC-3-APPLY_DS_FAILED |
3-Error |
Applying downstream license failed |
Unable to apply the downstream license |
ubr10000 |
"Internal Error check license and report to TAC" |
|
CMTS_LIC-3-APPLY_US_FAILED |
3-Error |
Applying upstream license failed |
Unable to apply the upstream license |
ubr10000 |
"Internal Error check license and report to TAC" |
|
CMTS_LIC-3-CSB_FAIL |
3-Error |
[chars] failed for [chars] |
An attempt to parse a license related CLI failed |
PLATFORM |
"Check the linecard license details and call TAC" |
|
CMTS_LIC-3-INVALID_LIC_INFO |
3-Error |
License Info Buffer is empty for [dec]/[dec] |
The license info buffer received/created from CLC is empty |
PLATFORM |
"Check the line card license details at CLC" |
|
CMTS_LIC-3-LCD_PROCESS_CREATE_FAIL |
3-Error |
Could not create Update LCD process on Linecard [dec]/[dec] |
The Line card license LCD update process create failed |
ubr10000 |
LOG_STD_DDTS_TAC_DETAILS |
|
CMTS_LIC-3-LIC_LED_ERROR |
3-Error |
Unable to set Downstream Density LED |
Unable to set Downstream Density LED |
PLATFORM |
"Try OIR the CLC and check the LED" |
|
CMTS_LIC-3-LIC_WDC_ALLOCATION_ERROR |
3-Error |
Unable to allocate memory for WDC memory storage |
Unable to allocate memory for WDC memory |
PLATFORM |
"Try the command again at a later time" |
|
CMTS_LIC-3-LICENSE_ACTIVFAIL |
3-Error |
Could not activate license module on Linecard [dec]/[dec] |
The Line card license module activation failed |
ubr10000 |
LOG_STD_DDTS_TAC_DETAILS |
|
CMTS_LIC-3-LICENSE_SEATNAME_ERROR |
3-Error |
Unable to get slotid from [chars] |
Unable to get slotid |
PLATFORM |
"No action required" |
|
CMTS_LIC-3-NULL_HWIDB |
3-Error |
Function [chars] invoked with hwidb NULL |
hwidb passed to function is NULL |
PLATFORM |
"Internal Error check license and report to TAC" |
|
CMTS_LIC-3-NULL_LICENSE_INFO |
3-Error |
Line Card [dec]/[dec] license info is NULL! |
The Line card license info is NULL |
PLATFORM |
"Check the line card license details" |
|
CMTS_LIC-3-PROTECT_INVALID |
3-Error |
Protect linecard [dec]/[dec] has lower license than the configured working |
Protect linecard has lower license than the working so HCCP configuration is now invalid for the protect linecard |
ubr10000 |
"Upgrade the license on the protect" |
|
CMTS_LIC-3-WORKING_INVALID |
3-Error |
Working linecard [dec]/[dec] has higher license than the configured protect |
Working linecard has higher license than the protect so HCCP configuration is now invalid for the working linecard |
ubr10000 |
"Upgrade the license on the protect or downgrade" " the license on the working" |
|
CMTS_LIC-3-WORKING_PARTIAL |
3-Error |
Working Linecard [dec]/[dec] License has been restricted. Please upgrade Protect Linecard License first and then reload working for complete fulfillment |
The working linecard license is now reduced because the working linecard license is higher than the protect linecard license |
ubr10000 |
"Please upgrade the license on the protect and then reload the working linecard" |
|
CMTS_LIC-4-LICENSE_PENDING |
4-Warning |
License enforcement pending for Linecard [dec]/[dec] |
The linecard license enforcement will be delayed until the linecard transitions to active |
ubr10000 |
"No action required" |
|
CMTS_LIC-6-CHAN_NOSHUTFAIL |
6-Information |
[chars] channel [dec] no shut is not allowed due to insufficient licenses |
Unable to no shut the channel due to insufficient licenses |
ubr10000 |
"Internal Error check number of licenses installed" |
|
CMTS_LIC-6-CHANNEL_NO_SHUTDOWN |
6-Information |
[chars] channel [dec] has been restored to no shut |
Restored previously shutdown channels to no shut state |
ubr10000 |
"None" |
|
CMTS_LIC-6-CHANNEL_SHUTDOWN |
6-Information |
[chars] channel [dec] has been shutdown due to insufficient licenses |
Unable to no shut the channel due to insufficient licenses |
ubr10000 |
"Internal Error check number of licenses installed" |
|
CMTS_LIC-6-LICENSE_ENFORCE |
6-Information |
Linecard [dec]/[dec] set to mode [chars] |
License Information has been applied |
PLATFORM |
"No action required" |
|
CMTS_LIC-6-OUT_OF_RANGE |
6-Information |
LC [dec]/[dec] [chars] is already [dec] |
License counters have reached boundary condition |
ubr10000 |
"Internal Error check license and report to TAC" |
|
CMTS-3-CABLE_IPC_SEND_FAILURE |
3-Error |
cable nonblocked ipc send failed msg_type[[dec]] dst_slot[[dec]] |
Cable send nonblocked ipc failed |
cbr-application |
LOG_STD_NO_ACTION |
|
CMTS-3-DYN_SRV_IPC_SEND_FAILURE |
3-Error |
[chars]_Tx: nonblocked send failed dst_slot [dec] |
Dynamic service failed to send nonblock IPC message |
cbr-application |
LOG_STD_NO_ACTION |
|
CMTS-3-INVALID_BW |
3-Error |
Invalid bandwidth configuration: cir_pct [dec] cir_sum [dec] eir_sum [dec] |
Bandwidth configuration is invalid |
cmts |
LOG_STD_ACTION |
|
CMTS-3-LIST_CREATE |
3-Error |
list create failed for list [chars] |
The Cisco CMTS router is unable to create list due to insufficient system memory |
cmts |
"Run the show memory command to verify available system memory. " "If memory is full contact your Cisco technical support " "representative and provide the representative with the " "gathered information" |
|
CMTS-3-LIST_CREATE |
3-Error |
list create failed for list [chars] |
The Cisco CMTS router is unable to create list due to insufficient system memory |
cmts |
"Run the show memory command to verify available system memory. " "If memory is full contact your Cisco technical support " "representative and provide the representative with the " "gathered information" |
|
CMTS-3-LIST_ENQUEUE |
3-Error |
list enqueue failed for list [chars] |
Unable to enqueue an entry to list |
cmts |
LOG_STD_ACTION |
|
CMTS-3-LIST_ENQUEUE |
3-Error |
list enqueue failed for list [chars] |
Unable to enqueue an entry to list |
cmts |
LOG_STD_ACTION |
|
CMTS-3-LIST_INSERT |
3-Error |
list insert failed for list [chars] |
The Cisco CMTS router is unable to insert an entry into list due to insufficient system memory or insert an exist entry |
cmts |
"Run the show memory command to verify available system memory. " "Then run the show logging command to view all system-logged " "messages. If memory is full contact your Cisco technical " "support representative and provide the representative with " "the gathered information" |
|
CMTS-3-LIST_INSERT |
3-Error |
list insert failed for list [chars] |
The Cisco CMTS router is unable to insert an entry into list due to insufficient system memory or insert an exist entry |
cmts |
"Run the show memory command to verify available system memory. " "Then run the show logging command to view all system-logged " "messages. If memory is full contact your Cisco technical " "support representative and provide the representative with " "the gathered information" |
|
CMTS-3-MCAST_SES_MISMATCH |
3-Error |
Session Request Response Mismatch for transaction ID [dec] session [chars][chars] CM [enet] |
Response from the LC does not match the session requested for. |
cmts |
LOG_STD_ACTION |
|
CMTS-3-MCAST_SES_MISMATCH |
3-Error |
Session Request Response Mismatch for transaction ID [dec] session [chars][chars] CM [enet] |
Response from the LC does not match the session requested for. |
cmts |
LOG_STD_ACTION |
|
CMTS-3-PKTCBL_GATE_RECON_START |
3-Error |
Pktcbl reconciliation [chars] in progress: |
Pktcbl Reconciliation started. |
packetcable |
LOG_STD_ACTION |
|
CMTS-4-CM_GET_RCC_FAILED_AFTER_LCHA |
4-Warning |
failed to get rcc after LCSO Attempting to get rcc[[dec]] cm[[enet]] |
Find invalid rcc while cm recover |
cmts |
LOG_STD_ACTION |
|
CMTS-4-DELETE_BONDING_MISMATCH |
4-Warning |
Error deleting upstream sid clusters CM[[enet]] docsis_prim_sid[[dec]] matches csc_sid[[dec]] |
The secondary sid should never match the primary. |
cmts |
LOG_STD_ACTION |
|
CMTS-4-DS_RESIL_FAILURE |
4-Warning |
[chars]: [chars] failed |
DS Resiliency ipc message processing failure. |
cBR |
"." |
|
CMTS-4-ENQUEUE_SID_DUPLICATE |
4-Warning |
Error enqueing sid element Attempting to enqueue sid[[dec]] onto sid_reuse_queue that already exists |
A duplicate sid should never exist in the free pool. |
cmts |
LOG_STD_ACTION |
|
CMTS-4-ENQUEUE_SID_INVALID |
4-Warning |
Error enqueing sid element Attempting to enqueue invalid sid[[dec]] onto sid_reuse_queue |
An invalid sid cannot be added to the free pool. |
cmts |
LOG_STD_ACTION |
|
CMTS-4-PKTCBL_DB_ERROR |
4-Warning |
Pktcbl failure op. [dec] type: [[dec]] gate id: [[dec]] sub_id: [[chars]] |
PacketCable database encounters an error Details embedded in message .. |
packetcable |
LOG_STD_NO_ACTION |
|
CMTS-4-PKTCBL_GATE_RECON_DONE |
4-Warning |
Reconciliation [chars] for slot [dec] finished: |
Reconciliation completed print counters. |
packetcable |
LOG_STD_ACTION |
|
CMTS-4-PKTCBL_GATE_RECON_MISMATCHED |
4-Warning |
Pktcbl reconciliation [chars] gate IE mismatched: |
Pktcbl reconciliation gate IE mismatched. |
packetcable |
LOG_STD_ACTION |
|
CMTS-4-PKTCBL_GATE_RECON_TIMEOUT |
4-Warning |
Pktcbl reconciliation for slot [dec] timeout |
Usually the reconciliation will end after all gates' info being synced between SUP and LC. If we didn't get the end normally timer mechanism will take job and clean up left gates' info |
packetcable |
LOG_STD_ACTION |
|
CMTS-4-RECONCL_CM_FINISH_CLC |
4-Warning |
Reconciliation [chars] for slot [dec] finished: |
Reconciliation finished print counters. |
cmts |
LOG_STD_ACTION |
|
CMTS-4-RECONCL_CM_FINISH_SUP |
4-Warning |
Reconciliation [chars] for slot [dec] finished: |
Reconciliation finished print counters. |
cmts |
LOG_STD_ACTION |
|
CMTS-4-RECONCL_CM_MISMATCH |
4-Warning |
Modem [enet] on Ca[dec]/0/[dec] mismatch during reconciliation delete reason: [chars] |
After the LC switchover modem info will be synced to SUP to compare if there is any info mismatcheg: modem state service flow info etc. the modem will be deleted fully. |
cmts |
LOG_STD_ACTION |
|
CMTS-4-RECONCL_CM_TIMEOUT |
4-Warning |
Reconciliation for slot [dec] timeout |
Usually the reconciliation will end after all modem info being synced between SUP and LC. If we didn't get the end normally timer mechanism will take job and clean up left modem info |
cmts |
LOG_STD_ACTION |
|
CMTS-4-RECONCL_RESET_D31_CM_FINISH |
4-Warning |
Reconciliation reset partial D31 CM for slot [dec] finished: D3.1 Online [dec] D3.1 DS partial [dec] D3.1 US partial [dec] D3.1 both partial [dec]. D3.0 DS partial [dec] D3.0 US partial [dec] D3.0 both partial [dec]. |
Reconciliation reset partial D31 CM finished print counters. |
cmts |
LOG_STD_ACTION |
|
CMTS-4-UPSTREAM_SID_MISMATCH |
4-Warning |
Error populating upstream sid clusters CM[[enet]] docsis_prim_sid[[dec]] matches csc_sid[[dec]] |
The secondary sid should never match the primary. |
cmts |
LOG_STD_ACTION |
|
CMTS-6-PKTCBL_GATE_ERROR |
6-Information |
Pktcbl failure op. [dec] type: [[dec]] gate id: [[dec]] sub_id: [[chars]] |
PacketCable encounters an error Details embedded in message .. |
packetcable |
LOG_STD_NO_ACTION |
|
CNS-3-CNS_DHCP_OP43_PROCESS_FAILED |
3-Error |
PROCESSING FAILED |
The processing of CNS DHCP Option 43 message failed. |
- |
"Need to verify the CNS DHCP option 43 message is in correct format.\n\ If not correct it and send this message again." |
|
CNS-3-FAULT |
3-Error |
[chars] |
CNS subsystem has detected an internal exception condition |
cns-agents |
LOG_STD_ACTION |
|
CNS-3-MEMORY |
3-Error |
[chars] |
CNS subsystem has experienced a problem gettting the required\n\ memory to complete this operation. |
cns_agents |
"Check system memory for other memory allocation errors and contact\n\ Technical support for problem resolution. In the absence of IOS errors\n\ upgrading the memory in the network device may be required." |
|
CNS-3-TRANSPORT |
3-Error |
[chars] |
CNS subsystem has experienced a problem contacting an external\n\ application. |
cns_agents |
"See specific message text for an indication as to what the\n\ cause might be. Check the network configuration and cables to make\n\ sure the remote application is running and the address is accessible" |
|
CNS-3-WARNING |
3-Error |
[chars] |
CNS subsystem has experienced an unexpected condition executing\n\ a set of commands which did not cause a failure but suggests things\n\ did not go totally correctly |
cns_agents |
"Check the error log for additional information. This is an informational\n\ message and does not necessarily indicate an error did happen." |
|
CNS-3-XML_SEMANTIC |
3-Error |
[chars] |
CNS subsystem has experienced an error while processing the XML \n\ encapsulation of configuration command. |
cns_configagent |
"The externally supplied XML has errors in it and connot be processed.\n\ See specific message text for an indication as to what the\n\ cause might be. This will possible require the command to be\n\ checked and reissued from the server." |
|
CNS-5-CNS_DHCP_OP43_PROCESS_DONE |
5-Notice |
PROCESSING DONE |
The processing of CNS DHCP Option 43 message succeeded. |
- |
"None." |
|
CNS-5-CONFIG_SUCCESS |
5-Notice |
SUCCESSFUL_COMPLETION |
The configuration download has been applied successfully. |
- |
"None." |
|
CNS-5-IOS_UP |
5-Notice |
- |
- |
- |
- |
|
CNS-6-NO_EVENT_AGENT |
6-Information |
CNS EVENT AGENT IS NOT CONFIGURED |
The cns event agent is not configured. The event that was to be sent to it will be dropped |
- |
"Configure the cns event agent." |
|
COBALT-3-COBERR |
3-Error |
Cobalt [chars]. |
Cobalt generated an error. |
cr10k5 |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
COFF_INFRA-3-COFF_DECRYPT_RCY_PUNT |
3-Error |
COFF attempted to punt pending decryption through RX-CR unsupported operation |
We tried to do a punt with a pending decryption scheduled |
cpp-ucode |
"File a bug with the COFF infra team" |
|
COFF_INFRA-3-COFF_MD_OOM |
3-Error |
COFF attempted to allocate an MD object and failed |
MD pool ran dry and alloc failed |
cpp-ucode |
"Check 'sh plat hard qfp act da inf coff' CLI for MD mempool statistics" |
|
COFF_INFRA-3-COFF_SQNMGMT_OOM |
3-Error |
COFF attempted to allocate an SQN Mgmt object and failed |
SQN Mgmt pool ran dry and alloc failed |
cpp-ucode |
"Check 'sh plat hard qfp act da inf coff' CLI for SQN Mgmt mempool statistics" |
|
COLLECTION-3-MODE_PRIORITY_MISMATCH |
3-Error |
Attempted to start a walk with incompatible mode and priority mode [chars] priority [chars] |
COLLECTION_INTERNAL_ERROR |
COLLECTION_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COLLECTION-3-MODE_PROCESS_MISMATCH |
3-Error |
Attempted to start a walk with incompatible mode and process mode [chars] process [chars] |
COLLECTION_INTERNAL_ERROR |
COLLECTION_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COLLECTION-3-PROC_INIT |
3-Error |
Initialization of process [chars] failed unable to [chars] |
COLLECTION_INTERNAL_ERROR |
COLLECTION_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COLLECTION-3-SUB_WALK |
3-Error |
Subwalk mismatch walk %p priority [chars] mode [chars] |
COLLECTION_INTERNAL_ERROR |
COLLECTION_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COLLECTOR-3-EXISTING_COLLECTOR |
3-Error |
Collector [chars] already exists\n |
A collector already exists. Only one collector may be configured at a time. |
media-mon - collector |
"Modify the existing collector or remove it " "and create a new one with the desired name" |
|
COLLECTOR-3-MODE_CHANGE_FAIL |
3-Error |
The collector mode is invalid |
An error occurred when attempting change the collector mode. The mode has reverted to the previous value |
media-mon - collector |
LOG_STD_ACTION |
|
COLLECTOR-3-PORT_CHANGE_FAIL |
3-Error |
Failed to set the collector port to [dec] |
An error occurred when attempting change the collector port. The port has reverted to the previous value |
media-mon - collector |
LOG_STD_ACTION |
|
COLLECTOR-3-PROCESS_FAIL |
3-Error |
Failed to start collector process |
An error occurred when attempting to start the collector |
media-mon - collector |
LOG_STD_ACTION |
|
COLLECTOR-3-REMOVE_FAIL |
3-Error |
The collector name is unrecognized |
The Collector name give does not match the collector configured |
media-mon - collector |
LOG_STD_ACTION |
|
COLLECTOR-3-RESETMODE |
3-Error |
Failed to reset csb vars |
Reset of the csb vars failed due to lack of memory |
media-mon - collector |
LOG_STD_ACTION |
|
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 |
- |
- |
- |
- |
|
COMMON_FIB-2-FIBTABLEILLEGAL |
2-Critical |
Attempt to used uninitialized CEF data structure. |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-2-HW_IF_INDEX_ILLEGAL |
2-Critical |
Attempt to create CEF interface for [chars] with illegal index: [dec] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-2-IF_NUMBER_ILLEGAL |
2-Critical |
Attempt to create CEF interface for [chars] with illegal if_number: [dec] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-2-IFINDEXBOUNDS |
2-Critical |
Attempt to use out of bounds interface index: [dec] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-ACL_PBR_NAMETOOLONG |
3-Error |
IPV6_SWSB_CTRL name length error [chars] acl_in [dec] [dec] |
IPv6 in/out ACL and IPv6 PBR name lengths for/from an IPC XDR message are invalid. The names will not be used so as to prevent any buffer overrun errors. There is a possibility that either the XDR message or an internal IPv6 FIB structure is corrupted |
IPV6FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-ASSERT |
3-Error |
Assertion '[chars]' failed in [chars] CEF [0x%08x]: [chars] [chars][chars]. |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-ASSERT_RL |
3-Error |
Assertion '[chars]' failed in [chars] CEF [0x%08x]: [chars] [chars][chars]. |
- |
- |
- |
|
COMMON_FIB-3-BFD |
3-Error |
[chars][chars][chars][chars][chars][chars][chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-BFD_SESS |
3-Error |
[chars]:[chars] failed to [chars] BFD session error [[chars]] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-BINDINGLABEL |
3-Error |
Binding label [chars]: [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-BROKER_ENCODE |
3-Error |
[chars] broker failed to encode msg type [dec] for slots [chars] |
- |
- |
- |
|
COMMON_FIB-3-CHAIN_BAD_MAGIC |
3-Error |
Bad magic for element %p 0x%08x != 0x%08x |
- |
- |
- |
|
COMMON_FIB-3-DEPENDENCY_CHAIN |
3-Error |
Missing handler for type [dec] dependency |
COMMON_FIB_INTERNAL_ERROR |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-DEPENDENCY_WALK |
3-Error |
Walk specification %p missing handler for type [dec] dependency |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-DQUEUE_ACTIVE_COLLECTION |
3-Error |
dqueue has an active collection just prior to destruction |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-DQUEUE_BAD_ELEM |
3-Error |
Unexpected element type [dec] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-DQUEUE_BAD_NEXT |
3-Error |
elem %p type 0x[hec] elem->next %p elem->next_type 0x[hec] elem->next->prev %p |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-DQUEUE_BAD_PREV |
3-Error |
elem %p type 0x[hec] elem->prev %p elem->prev_type 0x[hec] elem->prev->next %p |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-DQUEUE_NON_EMPTY |
3-Error |
dqueue is not empty just prior to destruction |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-EPOCH |
3-Error |
Failed to start [chars] of [chars]entries in table [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIB_ADJ_LINKTYPE |
3-Error |
OCE chain for [chars] terminates with [chars] linktype is [chars] not [chars] |
An OCE chain for a FIB entry terminates with a linktype other than what was expected. This will cause encapsulation problems in the dataplane. |
COMMON_FIB_DDTS_COMPONENT |
"Get the full show ip[v6] cef <vrf prefix> internal" " output of the affected FIB entry and determine" " if anything looks wrong. For instance is a label" " or a midchain adjacency missing?" |
|
COMMON_FIB-3-FIB_ATTACHED_EXPORT |
3-Error |
Attached export tracking error: [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIB_FIB_SOURCE |
3-Error |
[chars] for [chars] - [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIB_FIB_SOURCE_IPL_SB |
3-Error |
[chars] - [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIB_FIB_SOURCE_NULL_FIBIDB |
3-Error |
[chars] NULL fibidb in broadcast sb |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIB_GSB |
3-Error |
Generic subblock error: [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIB_GSB2 |
3-Error |
Generic subblock error: [chars][chars][chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIB_LOADBALANCE_MAP |
3-Error |
[chars] map [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIB_LOADBALANCE_MAP_NO_USEABLE_CHOICES |
3-Error |
No useable choices %04x bucket count [dec] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIB_LOADBALANCE_USAGE |
3-Error |
Unhandled usage flag 0x[hec] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIB_MPLS_EXT_FIND_OCE |
3-Error |
Unable to find MPLS oce for [chars] IP oce |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIB_NON_IP_ENTRY_INCR |
3-Error |
[chars] non-ip entry 0x%08x path list [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIB_OCC_DEP_DUMP |
3-Error |
[chars] |
COMMON_FIB_INTERNAL_ERROR |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIB_PATH_LIST_DB |
3-Error |
[chars] path list [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIB_XDR_BUF_OVERFLOW |
3-Error |
FIB XDR buffer overflow while encoding [chars] [[chars]] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIBCOVEREDDEPDUMP |
3-Error |
[chars] [chars] |
COMMON_FIB_INTERNAL_ERROR |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIBDEPDUMP |
3-Error |
[chars] |
COMMON_FIB_INTERNAL_ERROR |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIBHWIDB_NONAME |
3-Error |
Missing name for fibhwidb ifindex [dec] |
- |
- |
- |
|
COMMON_FIB-3-FIBHWIDBINCONS |
3-Error |
An internal software error occurred. [chars] linked to wrong hwidb [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIBIDB_DB_INTERNAL |
3-Error |
fibidb [chars] if_nb [dec] could not be [chars] db |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIBIDB_DB_MEM |
3-Error |
[chars] chunk pool could not be [chars]. Possible memory leak. |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIBIDB_DB_NULL_FIBIDB |
3-Error |
API called with NULL fibidb |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIBIDBEARLYCALL |
3-Error |
Attempt to update fibidb prior to completion of idb initialization. |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIBIDBINCONS1 |
3-Error |
An internal software error occurred. [chars] should be first fibidb |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIBIDBINCONS2 |
3-Error |
An internal software error occurred. [chars] linked to wrong idb [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIBIDBNONBASETABLE |
3-Error |
interface [chars] being set with non-base table: [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3- FIBINVPEXTLEN |
3-Error |
[chars] ext attempt to decode beyond XDR buffer cp_cur 0x[hec] cp_end 0x[hec] num_ext [dec] curr_ext_idx [dec] |
The path extension decode logic is trying to access memory beyond XDR buffer which can lead to memory corruption. |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIBLBCLPSECHAINDEPDUMP |
3-Error |
[chars] |
COMMON_FIB_INTERNAL_ERROR |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIBPLDEPDUMP |
3-Error |
[chars] |
COMMON_FIB_INTERNAL_ERROR |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIBSUBTREECONTEXT |
3-Error |
Subtree context unexpected error: app [chars]: [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIBTABLE |
3-Error |
Error for table [dec]: [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIBTOPO |
3-Error |
Error for topology [dec]: [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIBTOPOSTAT |
3-Error |
Error pulling topology stats [chars][chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIBXDRCLIENT |
3-Error |
FIB XDR Client error detected invalid wkid: [dec] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIBXDRINV |
3-Error |
Invalid XDR format. [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-FIBXDRLEN |
3-Error |
Invalid XDR length. Type [dec] [chars]. XDR/buffer len [dec]/[dec] |
- |
- |
- |
|
COMMON_FIB-3-HW_API |
3-Error |
HW API failure for [chars] CEF [0x%08x]: [chars] [chars][chars]. |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-ILIST_OP |
3-Error |
Manipulating interest list - [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-ILLEGAL_MSG_TYPE |
3-Error |
Cannot find ISSU message type for FIB [chars] [dec] [chars]SB [chars] msg |
- |
- |
- |
|
COMMON_FIB-3-ILLEGAL_TABLEID |
3-Error |
Attempt to create [chars] table with illegal tableid [dec] [chars]:[chars] |
- |
- |
- |
|
COMMON_FIB-3- ILLEGALARGS |
3-Error |
Illegal arguments - [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-INVALID_ADDR_TYPE |
3-Error |
Invalid address type [dec][chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-INVALID_AF |
3-Error |
Invalid address family [dec][chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-IPMFI_TIMING_PRESENT |
3-Error |
IPMFI Timing Tool present in image - performance will be degraded |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3- ISSU_ENUM_ERROR |
3-Error |
Enum for [chars] is not ISSU-compliant: [chars] |
The given enumeration is not ISSU-compliant for the reason given. Unpredictable behaviour will result when interoperating with different IOS versions. |
COMMON_FIB_DDTS_COMPONENT |
"This requires a code fix before the image can be shipped or ISSU will be " "broken." |
|
COMMON_FIB-3-ISSU_REG |
3-Error |
ISSU client [chars] [dec] entity [dec] failed ISSU registration: [chars] |
ISSU negotiation failed for this XDR client. |
COMMON_FIB_DDTS_COMPONENT |
"This error indicates a coding problem. It is an error that will occur" "every time this image is run and requires a code change to fix it." |
|
COMMON_FIB-3-LOADBALANCE_LOOP |
3-Error |
Detected loop while installing OCE: [chars] %p to loadinfo: [chars] %p |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-MSGISSUAWARE |
3-Error |
Message [chars] [dec] is ISSU aware so cannot use old FIB API. |
ALL FIB subblocks must be ISSU aware. The subblock code must be rewritten for ISSU. Otherwise this may lead to unpredictable behaviour when running in SSO mode with two different versions of IOS. |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-NAMETOOLONG |
3-Error |
FIB[chars]IDB name [chars] error lengths [dec] [dec] short [dec] [dec] |
- |
- |
- |
|
COMMON_FIB-3-NO_TABLE_NAME |
3-Error |
Attempt to clear the name of [chars] table with tableid [dec] previous name [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-NO_VALID_PATHS |
3-Error |
No valid paths for prefix [chars] in vrf [chars]. |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-NOBROKER |
3-Error |
[chars] distribution broker not found - distributing [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-NOHWSBDECODE |
3-Error |
No [chars] subblock control decode function for [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-NOLABELNOLABEL |
3-Error |
Unexpected disposition information for [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3- NOMEM |
3-Error |
Memory allocation failure for [chars] in [chars] CEF [0x%08x] [chars][chars]. |
- |
- |
- |
|
COMMON_FIB-3-NOPATHFIBIDB |
3-Error |
No fibidb for [chars] ignoring path during path no [dec] update for [chars] |
- |
- |
- |
|
COMMON_FIB-3-NOSUCHCAPTURE |
3-Error |
Error finding capture point. |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-NOSWSBDECODE |
3-Error |
No [chars] subblock control decode function for [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3- PATH_EXT_DUPLICATE |
3-Error |
Detected identical [chars] path extension [chars] ext %p - replacing. |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-PATH_EXT_ENCODE |
3-Error |
Failed to encode [chars] path extension [chars] |
One or more path extensions could not be encoded for distribution and will not be sent. This indicates an internal code error and may impact CEF operation for prefixes using the affected path extensions. |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-PATH_EXT_ISSU_SR_LDP |
3-Error |
Dowgrading to a version that doesn't support Segment Routing and LDP on the same path labels [[dec]|[dec]]. |
This indicates there's an issue in ISSU transformation when downgrading to a lower version. Configuration changes might be required to avoid this issue. See recommended action. |
COMMON_FIB_DDTS_COMPONENT |
"Find out the prefix which is using the two outgoing " "labels as shown in the message with 'show mpls forwarding-table'. Check " "IGP configuration and disable either LDP or SR on that prefix." |
|
COMMON_FIB-3- PATH_EXT_PLIST_CHG_DUP_SHORT |
3-Error |
Detected identical short path extension following path list change idx [dec] type [dec] [[chars] --> [chars]] conv [dec] renum [dec] total short [dec] ext list %p. |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-PATH_INVALID_REPAIR |
3-Error |
Primary or repair paths configured by RIB are of invalid type: primary: [chars] repair: [chars] |
Either the primary path or the repair path is not of the correct type i.e. an attached nexthop that provides both interface and nexthop |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-SBNOTISSUAWARE |
3-Error |
Subblock [chars] is not ISSU aware and should be! |
ALL FIB subblocks must be ISSU aware. The subblock code must be rewritten for ISSU. Otherwise this may lead to unpredictable behaviour when running in SSO mode with two different versions of IOS. |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-SBWITHOUTISSUSUPPORT |
3-Error |
[chars] [chars] subblock doesn't support ISSU and can't be used. |
The given SW subblock doesn't support ISSU so may not be processed correctly on the LC. It has not been registered by the CEF component. |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-TABLE |
3-Error |
[chars]: [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-TABLE_CONCURRENT_UPDATE |
3-Error |
[chars]: [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-UNHANDLED_UNITS |
3-Error |
No handler for units [chars] - from slot [chars] |
- |
- |
- |
|
COMMON_FIB-3-VRFID_INVALID |
3-Error |
Error invalid vrfid [chars][chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-3-VRFMGR_INVALID |
3-Error |
Error invalid [chars] [dec] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-4-AUTOREPAIR |
4-Warning |
CEF [chars] database auto-repair executed |
The CEF consistency checkers have detected an inconsistent prefix in one of the CEF forwarding databases. The auto-repair function has been executed to repair the problem. Details of the prefix can be found using the 'show cef table consistency' command. |
COMMON_FIB_DDTS_COMPONENT |
"Copy the message exactly as it appears together with the output of " "the 'show cef table consistency' command and report it to your " "technical support representative" |
|
COMMON_FIB-4-BADXDRHWSBDECODE |
4-Warning |
HW subblock decode [chars] / [dec] - wrong length read expected [dec] decoded [dec] |
- |
- |
- |
|
COMMON_FIB-4-BADXDRSWSBDECODE |
4-Warning |
SW subblock decode [chars] / [dec] - wrong length read expected [dec] decoded [dec] |
- |
- |
- |
|
COMMON_FIB-4-BROKERINVMSG |
4-Warning |
Invalid message: [chars] type [chars] len [dec] |
An invalid message has been received by this broker. |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-4-CHAIN_INSERT_INCONS1 |
4-Warning |
Attempting to insert %p after %p but it is still pointed at by %p |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-4-CHAIN_INSERT_INCONS2 |
4-Warning |
Attempting to insert %p after %p but it has prev set to %p |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-4-CHAIN_REMOVE_INCONS1 |
4-Warning |
Attempting to remove %p but prev %p points at %p instead |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-4-CHAIN_REMOVE_INCONS2 |
4-Warning |
Attempting to remove %p but it has no prev next is %p |
- |
- |
- |
|
COMMON_FIB-4-CHAIN_REMOVE_INCONS3 |
4-Warning |
Attempting to remove %p with next %p thinks its prev is %p |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-4-DISABLING |
4-Warning |
[chars] CEF is being disabled due to a fatal error. |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-4-FIB_OCC_SB_REMOVE_FAIL |
4-Warning |
Attempted to remove subblock of type '[chars]' [dec] for [chars] failed |
- |
- |
- |
|
COMMON_FIB-4-FIB_SB_ADD_FAIL |
4-Warning |
Attempted add of subblock of type '[chars]' [dec] for [chars] failed[chars] |
- |
- |
- |
|
COMMON_FIB-4-FIBHWIDB |
4-Warning |
No fibhwidb for [chars] found during [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-4-FIBHWIDBMISMATCH |
4-Warning |
Mis-match between hwidb [chars] ifindex [dec] and fibhwidb [chars] ifindex [dec] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-4-FIBIDB |
4-Warning |
No fibidb found for [chars] during [chars] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-4-FIBIDBMISMATCH |
4-Warning |
Mis-match between idb [chars] if_number [dec] and fibidb [chars] if_number [dec] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-4-FIBMISSINGHWIDB |
4-Warning |
No fibhwidb while initializing fibidb for [chars] if_number [dec] |
- |
- |
- |
|
COMMON_FIB-4-FIBMSG |
4-Warning |
Invalid message received. Type [chars] event/sub-type [dec] length [dec] |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-4-FIBNULLHWIDB |
4-Warning |
Missing hwidb for fibhwidb [chars] ifindex [dec] |
- |
- |
- |
|
COMMON_FIB-4-FIBNULLIDB |
4-Warning |
Missing idb for fibidb [chars] if_number [dec]. |
- |
- |
- |
|
COMMON_FIB-4-FIBXDR_REGISTRATION |
4-Warning |
Unable to register XDR client [chars]. |
- |
- |
- |
|
COMMON_FIB-4-HWPREFIXINCONST1 |
4-Warning |
Hardware on RP missing prefix for [chars]/[dec] in FIB table [chars] present in RP FIB [[chars]] |
A passive consistency checker discovered a prefix in the RP FIB table which is not present in the hardware forwarding table on the RP. This may be a transient condition. |
COMMON_FIB_DDTS_COMPONENT |
"If the same prefix gives repeated errors check the prefix in CEF and " "routing table. Try disable/enable CEF if the prefix is " "missing." |
|
COMMON_FIB-4-HWPREFIXINCONST2 |
4-Warning |
Hardware in slot [chars] missing prefix for [chars]/[dec] in FIB table [chars] present in LC FIB [[chars]] |
A passive consistency checker discovered a prefix in the LC FIB table which is not present in the hardware forwarding table on this linecard. This may be a transient condition. |
COMMON_FIB_DDTS_COMPONENT |
"If the same prefix gives repeated errors check the prefix in CEF and " "routing table. Try disable/enable CEF if the prefix is " "missing." |
|
COMMON_FIB-4-HWPREFIXINCONST3 |
4-Warning |
RP missing prefix for [chars]/[dec] in FIB table [chars] present in RP hardware [[chars]] |
A passive consistency checker discovered a prefix in the hardware table which is not present in the FIB forwarding table on the RP. This may be a transient condition. |
COMMON_FIB_DDTS_COMPONENT |
"If the same prefix gives repeated errors check the prefix in CEF and " "routing table. Try disable/enable CEF if the prefix is " "missing." |
|
COMMON_FIB-4-HWPREFIXINCONST4 |
4-Warning |
Slot [chars] missing prefix for [chars]/[dec] in FIB table [chars] present in LC hardware [[chars]] |
A passive consistency checker discovered a prefix in the LC hardware table which is not present in the FIB forwarding table on this linecard. This may be a transient condition. |
COMMON_FIB_DDTS_COMPONENT |
"If the same prefix gives repeated errors check the prefix in CEF and " "routing table. Try disable/enable CEF if the prefix is " "missing." |
|
COMMON_FIB-4-ISSUBUFFERTOOSHORTMSG |
4-Warning |
Message [chars] for slots [chars] is too large [dec] bytes max [dec] |
- |
- |
- |
|
COMMON_FIB-4-ISSUENCODEWRONGLEN |
4-Warning |
Message [chars] for slots [chars] is wrong length [dec] should be [dec] |
- |
- |
- |
|
COMMON_FIB-4-LCPREFIXINCONST1 |
4-Warning |
Slot [chars] missing prefix entry for [chars] in FIB table [chars] when looking up [chars] [[chars]] |
A packet arrived on the linecard but the lookup of the destination IP address failed to find this prefix in the forwarding table. However the prefix is present on the RP. This may be a transient condition. |
COMMON_FIB_DDTS_COMPONENT |
"If the same prefix gives repeated errors check the CEF prefix on the " "RP and linecard. If necessary a clear cef linecard <slot> " "will download a new CEF table to the linecard. You can also " "try a clear adjacency command to reload host prefixes." |
|
COMMON_FIB-4-LCPREFIXINCONST2 |
4-Warning |
Slot [chars] prefix entry for [chars]/[dec] in FIB table [chars] [[chars]] reason: [chars] |
A passive consistency checker discovered a prefix that is present on the RP but is inconsistent in the forwarding table of the linecard. This may be a transient condition. |
COMMON_FIB_DDTS_COMPONENT |
"If the same prefix gives repeated errors check the CEF prefix on the " "RP and linecard. If necessary a clear cef linecard <slot> " "will download a new CEF table to the linecard. You can also " "try a clear adjacency command to reload host prefixes." |
|
COMMON_FIB-4- MAX_PATHS_EXCEEDED |
4-Warning |
Prefix [chars] in vrf [chars] has paths in excess of the maximum. Some may be dropped. |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-4-RPPREFIXINCONST1 |
4-Warning |
RP prefix for [chars]/[dec] in FIB table [chars] inconsistent on slot [chars] - [chars] [[chars]] |
- |
- |
- |
|
COMMON_FIB-4-RPPREFIXINCONST2 |
4-Warning |
RP missing prefix for [inet]%m in FIB table [chars] present in routing table [[chars]] |
A passive consistency checker discovered a prefix in the routing table which is not present in the CEF forwarding table on the RP. This may be a transient condition. |
COMMON_FIB_DDTS_COMPONENT |
"If the same prefix gives repeated errors check the prefix in CEF and " "routing table. Try disable/enable CEF if the prefix is " "missing." |
|
COMMON_FIB-4-RPPREFIXINCONST3 |
4-Warning |
RP has prefix [chars]/[dec] in FIB table [chars] missing in routing table |
A passive consistency checker discovered a prefix in the CEF forwarding table which is not present in the routing table. This may be a transient condition. |
COMMON_FIB_DDTS_COMPONENT |
"If the same prefix gives repeated errors check the prefix in CEF and " "routing table. Try disable/enable CEF if the prefix is " "missing." |
|
COMMON_FIB-4-SB_STAT_ENCODE |
4-Warning |
Encoding of [chars] [chars] stats XDR too big |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-4-TOPO_STAT_ID_MGR |
4-Warning |
Id manager error [chars]. Topology statistics accounting may not show the correct result |
COMMON_FIB_INTERNAL_ERROR |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_FIB-4- UNEQUAL |
4-Warning |
Ratio of unequal path weightings [chars] prevents oce [chars] from being used. |
- |
- |
- |
|
COMMON_FIB-5-FIB_RRP_HEADLESS_MODE |
5-Notice |
%S |
The RRP lost communication with the RP but the platform still wants CEF\n\ to continue operating in headless mode. |
- |
LOG_STD_ACTION |
|
COMMON_FIB-6-FIB_GSB_TEST_MSG |
6-Information |
Test subblock error: [chars] |
The subblock test command could not be completed successfully |
COMMON_FIB_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
COMMON_FIB-6- FIB_RECURSION |
6-Information |
[chars] has too many [dec] levels of recursion during [chars] |
- |
- |
- |
|
COMMON_MFIB-3-ASSERT |
3-Error |
Assertion '[chars]' failed in [chars] MFIB [0x%08x]: [chars] [chars][chars]. |
COMMON_MFIB_INTERNAL_ERROR |
COMMON_MFIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_MFIB-3-BG_POPULATE |
3-Error |
MFIB master background process failed to populate tables for [chars] |
COMMON_MFIB_INTERNAL_ERROR |
COMMON_MFIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_MFIB-3-BROKER_ENCODE |
3-Error |
[chars] broker failed to encode msg type [dec] for slots [chars] |
- |
- |
- |
|
COMMON_MFIB-3-BROKERINITFAIL |
3-Error |
Failed to initialise [chars] RP broker facility |
COMMON_MFIB_INTERNAL_ERROR |
COMMON_MFIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_MFIB-3-EPOCH |
3-Error |
Failed to [chars] table [chars][chars] |
COMMON_MFIB_INTERNAL_ERROR |
COMMON_MFIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_MFIB-3-ILLEGAL_TABLEID |
3-Error |
Attempt to create [chars] table with illegal tableid [dec] [chars] |
- |
- |
- |
|
COMMON_MFIB-3- ILLEGALARGS |
3-Error |
Illegal arguments - [chars] |
COMMON_MFIB_INTERNAL_ERROR |
COMMON_MFIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_MFIB-3-INVALID_AF |
3-Error |
Invalid address family [dec][chars] |
COMMON_MFIB_INTERNAL_ERROR |
COMMON_MFIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_MFIB-3-MFIB_GSB |
3-Error |
Generic subblock error: [chars] |
COMMON_MFIB_INTERNAL_ERROR |
COMMON_MFIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_MFIB-3-MFIBISSU_REGISTRATION |
3-Error |
Unable to register [chars] ISSU client[dec]. |
- |
- |
- |
|
COMMON_MFIB-3-MFIBXDR_ISSUREGERROR |
3-Error |
ISSU client [chars] [dec] entity [dec] failed ISSU registration: [chars] |
COMMON_MFIB_INTERNAL_ERROR |
COMMON_MFIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_MFIB-3-MFIBXDRINV |
3-Error |
Invalid XDR format. [chars] |
COMMON_MFIB_INTERNAL_ERROR |
COMMON_MFIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_MFIB-3-MFIBXDRLEN |
3-Error |
Invalid XDR length. Type [dec] [chars]. XDR/buffer len [dec]/[dec] |
COMMON_MFIB_INTERNAL_ERROR |
COMMON_MFIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_MFIB-3-NO_TABLE_NAME |
3-Error |
Attempt to clear the name of [chars] table with tableid %p previous name [chars] |
COMMON_MFIB_INTERNAL_ERROR |
COMMON_MFIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_MFIB-3-NOBROKER |
3-Error |
[chars] distribution broker not found - distributing [chars] |
COMMON_MFIB_INTERNAL_ERROR |
COMMON_MFIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_MFIB-3- NOMEM |
3-Error |
Memory allocation failure for [chars] in [chars] MFIB [0x%08x]. |
An attempt to allocate memory has failed. Depending on the criticality of the data to be stored MFIB operation may be impacted. |
COMMON_MFIB_DDTS_COMPONENT |
"Verify that the configuration is supported by the memory present in " "the system. Copy the message exactly as it appears and report it " "to your technical support representative." |
|
COMMON_MFIB-3-TABLE |
3-Error |
[chars]: [chars] |
COMMON_MFIB_INTERNAL_ERROR |
COMMON_MFIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_MFIB-4-BROKERINVMSG |
4-Warning |
Invalid message: [chars] type [chars] len [dec] |
An invalid message has been received by this broker. |
mfib |
LOG_STD_ACTION |
|
COMMON_MFIB-4-DISABLING |
4-Warning |
[chars] MFIB is being disabled due to a fatal error. |
COMMON_MFIB_INTERNAL_ERROR |
COMMON_MFIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_MFIB-4-MFIBMSG |
4-Warning |
Invalid message received. Type [chars] event/sub-type [dec] length [dec] |
COMMON_MFIB_INTERNAL_ERROR |
COMMON_MFIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_MFIB-4-MFIBTABLE |
4-Warning |
Failed to [chars] table [chars] [chars] |
An MFIB table was found to be missing when attempting to perform a change to it. This may be a transient condition |
COMMON_MFIB_DDTS_COMPONENT |
"If the same table gives repeated warnings or generates more serious" "errors copy the message exactly as it appears and report it to " "your technical support representative" |
|
COMMON_MFIB-4-MFIBXDR_NOTREG |
4-Warning |
XDR client [chars] should be registered. |
- |
- |
- |
|
COMMON_MFIB-4-MFIBXDR_REGISTRATION |
4-Warning |
Unable to register XDR client [chars]. |
- |
- |
- |
|
COMMON_SADR-3-DEPENDENCY_WALK |
3-Error |
Walk specification %p missing handler for type [dec] dependency |
COMMON_SADR_INTERNAL_ERROR |
COMMON_SADR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_SADR-3-FIBSADRDEPDUMP |
3-Error |
[chars] |
COMMON_SADR_INTERNAL_ERROR |
COMMON_SADR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
COMMON_TAL-3- HOSTBITSSET |
3-Error |
Host bits set for [chars]/[dec]. |
TAL API has been called with prefix/len pair with host bits set. This prefix/len pair is invalid and indicates an error in the calling code. |
COMMON_TAL_DDTS_COMPONENT |
"Copy the message exactly as it appears and report it " "to your technical support representative." |
|
COMP_API-4-COMP_API_IDB_WARNING |
4-Warning |
Incorrect External interface field access API invocation |
A routine external to the IP Multicast Component accesses an\n\ interface field with invalid interface argument |
- |
"An inconsistency calling an IP Multicast interface access API occurred." LOG_STD_ACTION |
|
COMP_MATRIX-3-PRST_VBL_DELETE |
3-Error |
ISSU Compatibility Matrix was unable to delete a persistent variable from the [chars] system rc = [dec]. |
The ISSU compatibility matrix was unable to access a persistent variable. There is no way to determine if issu image-version compatibility checking should be enabled or disabled. |
ha-issu-infra |
"show persistent variable" |
|
COMP_MATRIX-3-PRST_VBL_DELETE |
3-Error |
ISSU Compatibility Matrix was unable to delete a persistent variable from the [chars] system rc = [dec]. |
The ISSU compatibility matrix was unable to access a persistent variable. There is no way to determine if issu image-version compatibility checking should be enabled or disabled. |
ha-issu-infra |
"show persistent variable" |
|
COMP_MATRIX-3-PRST_VBL_GET |
3-Error |
ISSU Compatibility Matrix was unable to read a persistent variable from the local system rc = [dec]. |
The ISSU compatibility matrix was unable to access a persistent variable. There is no way to determine if issu image-version compatibility checking should be enabled or disabled. |
ha-issu-infra |
"show persistent variable" |
|
COMP_MATRIX-3-PRST_VBL_GET |
3-Error |
ISSU Compatibility Matrix was unable to read a persistent variable from the local system rc = [dec]. |
The ISSU compatibility matrix was unable to access a persistent variable. There is no way to determine if issu image-version compatibility checking should be enabled or disabled. |
ha-issu-infra |
"show persistent variable" |
|
COMP_MATRIX-3-PRST_VBL_WRITE |
3-Error |
ISSU Compatibility Matrix was unable to write to persistent variables on the [chars] system rc = [dec]. |
The ISSU compatibility matrix was unable to access a persistent variable. There is no way to determine if issu image-version compatibility checking should be enabled or disabled. |
ha-issu-infra |
"show persistent variable" |
|
COMP_MATRIX-3-PRST_VBL_WRITE |
3-Error |
ISSU Compatibility Matrix was unable to write to persistent variables on the [chars] system rc = [dec]. |
The ISSU compatibility matrix was unable to access a persistent variable. There is no way to determine if issu image-version compatibility checking should be enabled or disabled. |
ha-issu-infra |
"show persistent variable" |
|
COMP_MATRIX-4-DISABLED |
4-Warning |
Compatibility Matrix has been disabled. No image compatibility checking will be done. |
The ISSU compatibility matrix check has been disabled via configuration command <cmdBold>no service image-version compatibility<noCmdBold>. When the standby comes up no image compatibility checking will be done which results in SSO redundancy mode even if the active and standby are running different images. |
ha-issu-infra |
"The ISSU compatibility matrix check has been disabled " "using the global configuration command " "<cmdBold>no service image-version compatibility<noCmdBold>." "Redundancy mode would be SSO. " "Please be sure this is your intention or change configuration " "using <cmdBold>service image-version compatibility<noCmdBold>." |
|
COMP_MATRIX-4-DISABLED |
4-Warning |
Compatibility Matrix has been disabled. No image compatibility checking will be done. |
The ISSU compatibility matrix check has been disabled via configuration command <cmdBold>no service image-version compatibility<noCmdBold>. When the standby comes up no image compatibility checking will be done which results in SSO redundancy mode even if the active and standby are running different images. |
ha-issu-infra |
"The ISSU compatibility matrix check has been disabled " "using the global configuration command " "<cmdBold>no service image-version compatibility<noCmdBold>." "Redundancy mode would be SSO. " "Please be sure this is your intention or change configuration " "using <cmdBold>service image-version compatibility<noCmdBold>." |
|
COMP-3-BADCOMP |
3-Error |
Interface [chars] Bad status returned from packet compression operation |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
COMP-3-COMPERR |
3-Error |
[chars]: COMPRESS: stac error! status: [dec] size in: [dec] size out: [dec] |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
COMP-3-CONFIGBAD |
3-Error |
Interface [chars] Compression internal configuration error |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
COMP-3-SIZEBAD |
3-Error |
Interface [chars] Decompression size error |
One interface is configured for predictor compression the other is\n\ not. |
- |
"Configure both interfaces for predictor compression." |
|
COMP-3-SUBBLOCKERR |
3-Error |
Interface [chars] compression subblock creation failed. |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
COMP-3-SYNCBAD |
3-Error |
Interface [chars] Decompression sync error |
One interface is configured for predictor compression the other is\n\ not. |
- |
"Configure both interfaces for predictor compression." |
|
COMP-3-VERSIONBAD |
3-Error |
Interface [chars] Compression Version mismatch expected [hec] received [hec] |
One interface is configured for predictor compression the other is\n\ not. |
- |
"Configure both interfaces for predictor compression." |
|
COMP-5-NOBUF |
5-Notice |
Interface [chars] [chars] |
Interface serial0 compression getbuffer failed causing Link Access\n\ Procedure Balanced LAPB retransmissions. |
- |
"Configure additional large and big buffers." |
|
COMPILED_ACL-2-LIST_CREATE |
2-Critical |
[chars]: failed to create row queue for node [dec] Turbo ACL has been disabled temporarily |
The system encountered an error while initializing a data structure required for the correct operation of Turbo ACL processing. Turbo ACL will be disabled until another recompilation has completed successfully. |
c7300-pxf |
RECOMMENDED_ACTION |
|
COMPILED_ACL-2-QUEUE_INIT |
2-Critical |
[chars]: failed to initialize back-pointer list for row [dec] in node [dec] Turbo ACL has been disabled temporarily |
The system encountered an error while initializing a data structure required for the correct operation of Turbo ACL processing. Turbo ACL will be disabled until another recompilation has completed successfully. |
c7300-pxf |
RECOMMENDED_ACTION |
|
COMPILED_ACL-3-INTERNAL_ERROR |
3-Error |
an unexpected internal error occured: [chars] |
An unexpected internal error occurred. This error may result in one or more flows being punted to the RP or in Turbo ACL not functioning. |
c7300-pxf |
RECOMMENDED_ACTION |
|
COMPILED_ACL-4-BACKPOINTER_OVERFLOWED_NOT_EMPTY |
4-Warning |
[chars]: the back-pointer list for row [dec] in node [dec] is marked as overflowed but is not empty |
EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING |
c7300-pxf |
RECOMMENDED_ACTION |
|
COMPILED_ACL-4-BACKPOINTER_OVERFLOWED_NOT_EMPTY_REFERENCES |
4-Warning |
[chars]: the back-pointer list for row [dec] in node [dec] is marked as overflowed but is not empty |
EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING |
c7300-pxf |
RECOMMENDED_ACTION |
|
COMPILED_ACL-4-BACKPOINTER_PROCESSING_OVERFLOWED |
4-Warning |
[chars]: processing back-pointers in row [dec] in node [dec] but the list is marked as overflowed |
EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING |
c7300-pxf |
RECOMMENDED_ACTION |
|
COMPILED_ACL-4-BACKPOINTER_WRONG |
4-Warning |
[chars]: entry at row [dec] column [dec] in node [dec] does not reference row [dec] in the node's child |
EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING |
c7300-pxf |
RECOMMENDED_ACTION |
|
COMPILED_ACL-4-BAD_PROCESS_REFERENCES |
4-Warning |
[chars]: error while processing references for row [dec] in node [dec]: [chars] |
EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING |
c7300-pxf |
RECOMMENDED_ACTION |
|
COMPILED_ACL-4-BAD_ROW_FREE |
4-Warning |
[chars]: cannot free row [dec] in node [dec]: [chars] |
EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING |
c7300-pxf |
RECOMMENDED_ACTION |
|
COMPILED_ACL-4-DEFERRED_ENTRY_CONSISTENCY |
4-Warning |
[chars]: while [chars] in row [dec] in node [dec] found deferred entry bitmap is [chars] but count is [dec] |
EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING |
c7300-pxf |
RECOMMENDED_ACTION |
|
COMPILED_ACL-4-ENTRY_COUNT |
4-Warning |
[chars]: row entry counters not allocated for node [dec] while freeing row [dec] |
EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING |
c7300-pxf |
RECOMMENDED_ACTION |
|
COMPILED_ACL-4-ROW_UPDATE |
4-Warning |
[chars]: cannot process row queue update for row [dec] in node [dec]: [chars] |
EXPLANATION_INTERNAL_ERROR EXPLANATION_IMPACT_POSSIBLE_PUNTING |
c7300-pxf |
RECOMMENDED_ACTION |
|
COMPILED_ACL-4-ROW_UPDATE_ENQUEUE |
4-Warning |
[chars]: cannot process row queue update for row [dec] in node [dec]: enqueue failed %lu/%lu entries list is [chars]valid entry is [chars]enqueued |
- |
- |
- |
|
COMPILED_ACL-5-LIST_INFO |
5-Notice |
[chars]: failed to set list information function for node [dec]'s row queue ID [dec] |
The system encountered an error while initializing a function vector used for debugging purposes. Turbo ACL will continue to function correctly but the <CmdBold>show list<NoCmdBold> <CmdArg>ID<NoCmdArg> command will not show Turbo ACL-specific information for the specified list ID number. |
c7300-pxf |
RECOMMENDED_ACTION |
|
COND_DEBUG_HA-2-GET_BUFFER |
2-Critical |
COND_DEBUG ISSU client failed to get buffer for message. Error: [dec] [chars] |
The COND_DEBUG 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. |
cond_debug |
"show logging and show checkpoint client" |
|
COND_DEBUG_HA-2-INIT |
2-Critical |
COND_DEBUG ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The COND_DEBUG 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. |
cond_debug |
LOG_STD_ACTION |
|
COND_DEBUG_HA-2-SEND_NEGO_FAILED |
2-Critical |
COND_DEBUG ISSU client failed to send negotiation message. Error: [dec] [chars] |
The COND_DEBUG 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. |
cond_debug |
"show logging and show checkpoint client" |
|
COND_DEBUG_HA-2-SESSION_NEGO |
2-Critical |
COND_DEBUG ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The COND_DEBUG 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. |
cond_debug |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
COND_DEBUG_HA-2-SESSION_REGISTRY |
2-Critical |
COND_DEBUG ISSU client failed to register session information. Error: [dec] [chars] |
The COND_DEBUG ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
cond_debug |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
COND_DEBUG_HA-3-INVALID_SESSION |
3-Error |
COND_DEBUG ISSU client does not have a valid registered session. |
The COND_DEBUG ISSU client does not have a valid registered session. |
cond_debug |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
COND_DEBUG_HA-3-MSG_SIZE |
3-Error |
COND_DEBUG ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The COND_DEBUG ISSU client failed to calculate the MTU for the specified message. The COND_DEBUG ISSU client will not able to send the message to the standby device. |
cond_debug |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
COND_DEBUG_HA-3-SESSION_UNREGISTRY |
3-Error |
COND_DEBUG ISSU client failed to unregister session information. Error: [dec] [chars] |
The COND_DEBUG ISSU client failed to unregister session information. |
cond_debug |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
COND_DEBUG_HA-3-TRANSFORM |
3-Error |
COND_DEBUG ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The COND_DEBUG 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 COND_DEBUG state between the active device and the standby device is not identical. |
cond_debug |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
CONF_SW-2-IPC_INIT |
2-Critical |
IPC message handler registration failure rc [dec] |
Registering an IPC message handler for the CONF SW feature failed. This will cause the feature not to function. The function |
cpp-conf-sw |
"This is normally a software issue. " "The consequences are that the CONF SW feature will not function. " LOG_STD_ACTION |
|
CONF_SW-3-FEAT_DOWN |
3-Error |
Invalid request [chars] while feature down conf id [dec] |
While the feature was not active an invalid request was received from another layer of the CONF_SW software stack for the specified conf ID. Some requests do not have an associated conf ID. For them the displayed conf ID is zero. |
cpp-conf-sw |
"This is a software issue. The consequences " "could be limited to only one or a few confs. " LOG_STD_RECUR_ACTION |
|
CONF_SW-3-FEAT_UP |
3-Error |
Invalid request [chars] while feature up |
While the feature was active an invalid request was received from another layer of the CONF SW software stack. |
cpp-conf-sw |
"This is a software issue. " "There are no consequences as this can only have been an Init request " "while the feature was already active. " LOG_STD_RECUR_ACTION |
|
CONF_SW-3-IPC_NORES |
3-Error |
No space for the IPC reply size [dec] |
For a request from upper CONF SW software stack layers it was not possible to allocate space for a reply for the specified size. The consequence of this could be a stuck conf that cannot be established etc. In rare cases this could also affect other operations such as feature activation deactivation modification High-Availability switchover operations. |
cpp-conf-sw |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
CONF_SW-3-IPC_OPEN_REPLY |
3-Error |
IPC Open Reply failed request [dec] |
For a request from upper CONF SW software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck conf that cannot be established etc. In rare cases this could also affect other operations such as feature activation deactivation modification High-Availability switchover operations. |
cpp-conf-sw |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
CONF_SW-3-NO_RES |
3-Error |
[chars] resource not available for the [chars] request conf id [dec] |
The specified software resource was not available or could not be located for the specified request from upper CONF SW software stack layers for the specified conf ID. |
cpp-conf-sw |
"This is a software issue. The consequences " "are that the specified request could not be performed. " LOG_STD_RECUR_ACTION |
|
CONFIG_CSRLXC-2-INIT_FAILED |
2-Critical |
CSRLXC configuration cannot occur: [chars] |
The system was unable to even attempt to apply LXC configuration for the given reason. |
ultra-ui |
LOG_STD_SH_TECH_ACTION |
|
CONFIG_CSRLXC-3-CONFIG_NOT_SAVED |
3-Error |
Configuration not saved to NVRAM. Please inspect [chars] for details. |
Out of the generated VM configuration commands the given number of commands were rejected by the IOSd parser. The configuration is only automatically saved to NVRAM if no errors are encountered so in this case it was not saved. The indicated log file will describe exactly which commands were rejected as will any accompanying CSRLXC-4-CLI_FAILURE messages in this log. |
ultra-ui |
"Inspect the current running-config of the router " "using the <CmdBold>show running-config<noCmdBold> " "command. If it appears valid you may manually save " "the configuration using <CmdBold>copy running-" "config startup-config<noCmdBold>. If it does not " "appear valid manually correct the configuration " "or use the <CmdBold>config replace nvram:startup-" "config<noCmdBold> command to revert to the " "startup-config." |
|
CONFIG_CSRLXC-3-FILE_ERROR |
3-Error |
Could not [chars] file [chars]: [chars] |
The system was unable to perform the indicated operation on the indicated file for the indicated reason |
ultra-ui |
"Make sure the given disk is correctly formatted " "and has sufficient free space available." |
|
CONFIG_CSRLXC-4-CLI_FAILURE |
4-Warning |
Configuration command failure: '[chars]' was rejected |
The indicated IOSd configuration command generated by the CSRLXC subsystem was rejected by the IOSd CLI. Look for a subsequent CSRLXC-3-CONFIG_NOT_SAVED log message which will contain a reference to a logfile containing more information about this failure. |
ultra-ui |
"Inspect the log file to determine why the command " "was rejected and how to correct it. If necessary " "manually re-issue the corrected command." |
|
CONFIG_CSRLXC-5-CONFIG_DONE |
5-Notice |
Configuration was applied and saved to NVRAM. See [chars] for more details. |
The generated configuration was successfully applied no commands were rejected by the IOSd CLI and the |
ultra-ui |
LOG_STD_NO_ACTION |
|
CONFIG-3-VFI |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
CONFIG-3-XCONNECT |
3-Error |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
CONFIG-4-ATOM_TRANS |
4-Warning |
ERRMSG_NOFLAGS |
- |
- |
- |
|
CONSISTENCY-3-ATOM_TRANS |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
CONSISTENCY-3-LCON |
3-Error |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
CONSISTENCY-3-LDP |
3-Error |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
CONSISTENCY-3-MPLS_TE |
3-Error |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
CONSISTENCY-3-MPLS_TE_LM |
3-Error |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
CONST_ISSU-2-NEGO_NOT_DONE |
2-Critical |
[chars][dec]: ISSU Negotiation not complete |
Unable to complete ISSU negotiation. |
CONST_ISSU_PLATFORM |
LOG_STD_ACTION |
|
CONST_ISSU-3-CAP_EXCHANGE |
3-Error |
[chars][dec]: Capability exchange failed with error [chars] |
The capability exchange failed the ISSU client is unable to process the received capability |
CONST_ISSU_PLATFORM |
LOG_STD_ACTION |
|
CONST_ISSU-3-CAP_REG |
3-Error |
[chars][dec]: failed to register |
The capabilities of the ISSU client could not be registered |
CONST_ISSU_PLATFORM |
LOG_STD_ACTION |
|
CONST_ISSU-3-CAPENTRY_REG |
3-Error |
[chars][dec]: failed to register a capability entry [chars] |
The ISSU client failed to register a capability entry |
CONST_ISSU_PLATFORM |
LOG_STD_ACTION |
|
CONST_ISSU-3-CAPGROUP_REG |
3-Error |
[chars][dec]: failed to register a capability group [chars] |
The ISSU client failed to register a capability group |
CONST_ISSU_PLATFORM |
LOG_STD_ACTION |
|
CONST_ISSU-3-CAPTYPE_REG |
3-Error |
[chars][dec]: failed to |
The ISSU client failed to register a capability type |
CONST_ISSU_PLATFORM |
LOG_STD_ACTION |
|
CONST_ISSU-3-CF_SEND |
3-Error |
[chars][dec]: Client failed to send message [dec] |
ISSU client cannot send a negotiation message to a peer |
CONST_ISSU_PLATFORM |
LOG_STD_ACTION |
|
CONST_ISSU-3-CLIENT_REG |
3-Error |
[chars][dec]: Client failed to register [chars] |
The ISSU Client could not be registered |
CONST_ISSU_PLATFORM |
LOG_STD_ACTION |
|
CONST_ISSU-3-CLIENT_REG_FAILED |
3-Error |
[chars][dec]: Client is not |
The ISSU Client is not yet initialized. The negotiation for this client is not yet done. |
CONST_ISSU_PLATFORM |
LOG_STD_ACTION |
|
CONST_ISSU-3-CONST_MTU_NOT_ENOUGH |
3-Error |
[chars][dec]: Requested buffer size [dec] is greater than the max MTU size |
Checkpoint buffer size requested is greater than the max MTU size checkpoint supports |
cat6000-ha |
LOG_STD_ACTION |
|
CONST_ISSU-3-ENTITY_REG |
3-Error |
[chars][dec]: failed to register |
The ISSU entity could not be registered |
CONST_ISSU_PLATFORM |
LOG_STD_ACTION |
|
CONST_ISSU-3-ENTITY_UNREG |
3-Error |
[chars][dec]: failed to unregister |
The ISSU entity could not be unregistered |
CONST_ISSU_PLATFORM |
LOG_STD_ACTION |
|
CONST_ISSU-3-ICC_SEND |
3-Error |
[chars][dec]: Client failed to send message |
ISSU client cannot send a negotiation message to a peer |
CONST_ISSU_PLATFORM |
LOG_STD_ACTION |
|
CONST_ISSU-3-MSG_MTU |
3-Error |
[chars][dec]: Client failed to get mtu for message [dec] [chars] |
[chars][dec]: client cannot get the MTU for a message type |
CONST_ISSU_PLATFORM |
LOG_STD_ACTION |
|
CONST_ISSU-3-MSG_NOT_OK |
3-Error |
[chars][dec]: ISSU message type [dec] is not compatible |
ISSU received a message not compatible with the running version. |
CONST_ISSU_PLATFORM |
"show message type <Client_ID>" |
|
CONST_ISSU-3-MSG_POLICY |
3-Error |
[chars][dec]: Client failed to negotiate version for message type [dec] error [chars] |
ISSU client cannot negotiate message to a peer |
CONST_ISSU_PLATFORM |
LOG_STD_ACTION |
|
CONST_ISSU-3-MSG_REG |
3-Error |
[chars][dec]: failed to register its messages [chars] |
Messages for the ISSU client could not be registered |
CONST_ISSU_PLATFORM |
LOG_STD_ACTION |
|
CONST_ISSU-3-MSGGROUP_REG |
3-Error |
[chars][dec]: failed to |
The ISSU client failed to register a message group |
CONST_ISSU_PLATFORM |
LOG_STD_ACTION |
|
CONST_ISSU-3-MSGTYPE_REG |
3-Error |
[chars][dec]: failed to register a message type [chars] |
The ISSU client failed to register a message type |
CONST_ISSU_PLATFORM |
LOG_STD_ACTION |
|
CONST_ISSU-3-NEGO_PROCESS |
3-Error |
[chars][dec]: Cannot create process: [chars] |
The process to negotiate the session for the specified ISSU client cannot be created. |
CONST_ISSU_PLATFORM |
LOG_STD_ACTION |
|
CONST_ISSU-3-SESSION_REG |
3-Error |
[chars][dec]: session failed to register [chars] |
The client's ISSU session could not be registered |
CONST_ISSU_PLATFORM |
LOG_STD_ACTION |
|
CONST_ISSU-3-SESSION_UNREG |
3-Error |
[chars][dec]: session [dec] |
The client's ISSU session could not be unregistered |
CONST_ISSU_PLATFORM |
LOG_STD_ACTION |
|
CONST_ISSU-3-START_NEGO_FAILED |
3-Error |
[chars][dec]: failed to |
The ISSU client cannot start its negotiation |
CONST_ISSU_PLATFORM |
LOG_STD_ACTION |
|
CONST_ISSU-3-TRANSFORM_FAILED |
3-Error |
[chars][dec]: [chars] transformation failed [chars] |
The transformation operation for the ISSU message has failed |
CONST_ISSU_PLATFORM |
LOG_STD_ACTION |
|
CONTROLLER-2-CDB_NULL |
2-Critical |
cdb is NULL |
A NULL pointer is detected |
- |
LOG_STD_SH_TECH_ACTION |
|
CONTROLLER-2-CRASHED |
2-Critical |
Interface Processor in slot [dec] not responding [hec]: shutting it down |
A controller stopped responding to commands over the cBus so it was\n\ put into shutdown mode. |
- |
"Re-enable the controllers by issuing the no shut\n\ configuration command on all controllers on the card or\n\ hotswap out the bad card and install the new one. You must\n\ still manually <CmdBold>no shut<noCmdBold> the controllers." |
|
CONTROLLER-2-DSX_NULL |
2-Critical |
dsx pointer is NULL |
A NULL pointer is detected |
- |
LOG_STD_SH_TECH_ACTION |
|
CONTROLLER-2-FIRMWARE |
2-Critical |
Controller [chars] [chars] |
A software or hardware error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
CONTROLLER-2-NOTFOUND |
2-Critical |
For controller [chars] |
An internal software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
CONTROLLER-4-ACR_DCR_CLOCK_DS1 |
4-Warning |
[chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [dec] [chars] |
DS1 Recovered clock status change message |
- |
LOG_STD_NO_ACTION |
|
CONTROLLER-4-ACR_DCR_CLOCK_DS3 |
4-Warning |
[chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [dec] [chars] |
DS3 Recovered clock status change message |
- |
LOG_STD_NO_ACTION |
|
CONTROLLER-4-ACR_DCR_CLOCK_DS3_CHANNEL |
4-Warning |
[chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [dec]/[dec] [chars] |
DS3:channelized Recovered clock status change message |
- |
LOG_STD_NO_ACTION |
|
CONTROLLER-4-ACR_DCR_CLOCK_OCN_CT3 |
4-Warning |
[chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [dec]/[dec]/[dec] [chars] |
OCN_CT3: Recovered clock status change message |
- |
LOG_STD_NO_ACTION |
|
CONTROLLER-4-ACR_DCR_CLOCK_OCN_T3 |
4-Warning |
[chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [dec]/[dec] [chars] |
OCN_T3: Recovered clock status change message |
- |
LOG_STD_NO_ACTION |
|
CONTROLLER-4-ACR_DCR_CLOCK_OCN_VT_T1 |
4-Warning |
[chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [dec]/[dec]/[dec]/[dec] [chars] |
OCN_VT_T1: Recovered clock status change message |
- |
LOG_STD_NO_ACTION |
|
CONTROLLER-4-ACR_DCR_CLOCK_STMN_CT3 |
4-Warning |
[chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [dec]/[dec]/[dec]/[dec] [chars] |
STMN_CT3: Recovered clock status change message |
- |
LOG_STD_NO_ACTION |
|
CONTROLLER-4-ACR_DCR_CLOCK_STMN_E3 |
4-Warning |
[chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [dec]/[dec]/[dec] [chars] |
STMN_E3: Recovered clock status change message |
- |
LOG_STD_NO_ACTION |
|
CONTROLLER-4-ACR_DCR_CLOCK_STMN_T3 |
4-Warning |
[chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [dec]/[dec]/[dec] [chars] |
STMN_T3: Recovered clock status change message |
- |
LOG_STD_NO_ACTION |
|
CONTROLLER-4-ACR_DCR_CLOCK_STMN_VC1x |
4-Warning |
[chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [dec]/[dec]/[dec]/[dec] [chars] |
STMN_VC1x: Recovered clock status change message |
- |
LOG_STD_NO_ACTION |
|
CONTROLLER-5-CALLDROP |
5-Notice |
Controller [chars] [chars] |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CONTROLLER-5-CLOCKSTATE |
5-Notice |
Controller [chars] [chars] |
A configurable controller clock changed its state. |
- |
LOG_STD_NO_ACTION |
|
CONTROLLER-5-DOWNDETAIL |
5-Notice |
Controller [chars] changed state to [chars] due to [chars] |
A configurable controller changed its state. |
- |
LOG_STD_NO_ACTION |
|
CONTROLLER-5-HDLC_INSUFF_RESOURCE |
5-Notice |
Insufficient HDLC resources to enable channel [dec] |
Limited number of HDLC channels can be allocated for this trunk |
- |
"Please check the number of HDLC resources supported for this trunk\n\ card. Please contact your technical support representative." |
|
CONTROLLER-5-LOOPSTATUS |
5-Notice |
Controller [chars] [chars] |
A configurable controller loopback status. |
- |
LOG_STD_NO_ACTION |
|
CONTROLLER-5-REMLOCALLOOP |
5-Notice |
Controller [chars] local loop [chars] [chars] |
A configurable controller entered local loopback. |
- |
LOG_STD_NO_ACTION |
|
CONTROLLER-5-REMLOOP |
5-Notice |
Controller [chars] remote loop [chars] [chars] |
A configurable controller entered remote loopback. |
- |
LOG_STD_NO_ACTION |
|
CONTROLLER-5-UPDOWN |
5-Notice |
Controller [chars] changed state to [chars] |
A configurable controller changed its state. |
- |
LOG_STD_NO_ACTION |
|
COPTMONMIB-3-ENTRYADDFAILED |
3-Error |
Registering of the interface with ifIndex [dec] to local data structure failed |
An attemt to make an entry for the registering interface failed |
gsr-netmgmt |
"" |
|
COPTMONMIB-3-ENTRYPRESENT |
3-Error |
An entry is already present for the registering interface with ifIndex [dec] |
An entry in the OPTICAL MONITORING MIB is already existing for the registering interface |
gsr-netmgmt |
"" |
|
CORABI-3-FATAL_N10G_ERP_ERROR |
3-Error |
ERP errors: [chars] ERP error data: 0x%02x ERP error phase: 0x%01x ERP error addr: 0x%08x |
Fatal Corabi N10G ERP interrupt |
cmts-platform |
"Copy the error message exactly as it appears and report it to your" " technical support" |
|
CORABI-3-FATAL_N10G_FAULT |
3-Error |
N10G fault reported |
Fatal Corabi N10G Fault interrupt |
cmts-platform |
"Copy the error message exactly as it appears and report it to your" " technical support" |
|
Corrupt configuration unsupported [chars] [dec] encountered |
The OC3/STM1 RP driver running configuration is corrupt |
c7600-sip-200 |
"This is a internal software error. Decode the " "traceback and get the output of <CmdBold>show " "running-config<NoCmdBold>. Check Bug Toolkit " "before calling the TAC. When calling the TAC " "please provide the above information along with " "the output of <CmdBold>show tech<NoCmdBold> " "details" |
- |
- |
|
CPP_BQS_QMOVE-3-PROXY_COMPLETE |
3-Error |
Proxy Operation: [chars] |
Operation that was flagged as timed out has now completed |
qfp-bqs-internal |
LOG_STD_ACTION |
|
CPP_BQS_QMOVE-3-PROXY_ERROR |
3-Error |
Proxy Operation Failed: [chars] |
BQS Proxy operation failed. |
qfp-bqs-internal |
LOG_STD_ACTION |
|
CPP_BQS_QMOVE-3-PROXY_TIMEOUT |
3-Error |
Proxy Operation: [chars] node_id [hec] data [hec] data [hec] |
BQS Proxy operation timeout. Proxy will continue to retry operatin. |
qfp-bqs-internal |
LOG_STD_ACTION |
|
CPP_BQS-2-MPASS_FS_REG |
2-Critical |
CPP BQS PROXY feature special vector [dec] registration failed result: [dec] |
Cisco internal software error. CPP multipass registration of a feature special processing vector for BQS Proxy failed. The BQS proxy will not be fully functional while this condition exists. |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_BQS-2-PROXY_IPC_INIT_FAILED |
2-Critical |
CPP BQS Proxy IPC interface initialization failure result: [dec]. |
Cisco internal software error. CPP BQS initialization detected that the Proxy IPC interface initialization failed. The BQS Proxy will not be functional while this condition exists. |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_BQS-3-CARVE |
3-Error |
[chars]: size [dec] SW carved out memory region initialization failed. |
A BQS proxy failed to initialize the software memory region. |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_BQS-3-CMD_ACTIVE |
3-Error |
CPP BQS Proxy Command correlator [dec] |
A BQS Proxy command was received but the correlator was still in use. Commad was not processed. |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_BQS-3-INIT_FAILED |
3-Error |
CPP BQS RM Proxy region [chars] |
BQS proxy failed due initialize or resize software managed memory. |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_BQS-3-INVALID_SUBTYPE |
3-Error |
CPP BQS RM Proxy subtype [dec] |
BQS proxy failed because of receiving invalid sub-type or failed to allocate ipc response buffer. |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_BQS-3-MAX_GPM_TX_LEN_EXCEED |
3-Error |
CPP BQS Proxy Command exceed GPM tx len [dec] |
A BQS Proxy command recycle a packet exceed GPM tx len |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_BQS-3-PROXY_IPC_SEND |
3-Error |
failure: [chars] |
BQS Proxy send response failed response was dropped. |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_BQS-3-RESIZE |
3-Error |
CPP BQS Proxy Memory Manager region [chars] |
BQS proxy failed to resize software managed memory. |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_CONF_SW-4-CPP_CONF_SW_NULL_EXMEM |
4-Warning |
Unexpected NULL shared-local EXMEM handle - ref_count [dec] |
The error will be corrected and pinhole programming will continue. |
asr1k-conf-sw |
LOG_STD_NO_ACTION |
|
CPP_FLOWDB_PROXY-3-FLOWDB_INIT_FAIL |
3-Error |
flowdb proxy init failure rc= [dec] |
The flow database proxy has experienced a failure when trying to init |
csr1kv-dp-infra |
LOG_STD_ACTION |
|
CPP_FLOWDB_PROXY-3-FLOWDB_SEND_IPC_FAIL |
3-Error |
rc= [dec] |
The flow database proxy has experience a failure when trying to send an IPC |
csr1kv-dp-infra |
LOG_STD_ACTION |
|
CPP_FLOWDB_PROXY-3-FLOWDB_UNEXPECTED_ERR |
3-Error |
rc= [dec] |
The flow database proxy has experienced an unexpected condition |
csr1kv-dp-infra |
LOG_STD_ACTION |
|
CPP_FLOWDB_PROXY-3-INVALID_IPC_SUBTYPE |
3-Error |
subtype is [dec] |
The flow database proxy has receive an IPC with an unexpected subtype |
csr1kv-dp-infra |
LOG_STD_ACTION |
|
CPP_FM-3-CPP_FM_CLIENT_WARNING |
3-Error |
Client Is Invalid: [chars] |
- |
- |
- |
|
CPP_FM-3-CPP_FM_FIPS_BYPASS_TEST |
3-Error |
NIST bypass test failed for CPP_FM object [chars]. |
Classification Feature Manager Security Client database detected a discrepancy in a security sensitive object. This could be due to a hardware or software resouce limitation or a software defect. |
qfp-class-internal |
"Check the logs for information on the relevant " "object download states. Remove the object or a " "parent object in question. If the problem persists " "reboot the forwarding processor ESP." |
|
CPP_FM-3-CPP_FM_TCAM_WARNING |
3-Error |
TCAM limit exceeded: [chars] |
- |
- |
- |
|
CPP_FM-4-CPP_FM_FIELD_IGNORED |
4-Warning |
Matching on field type [dec] [chars] value [dec] 0x[hec] |
User is trying to use a classification criterion not supported by the feature. For example user is trying to apply a with a class matching matched on an IPv6 ACL that contains a match on flow-label. The entire rule e.g. ACE containing the unsupported criterion |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPP_FM-4-CPP_FM_TCAM_MORE_INFO_WARNING |
4-Warning |
TCAM limit exceeded: [chars] |
- |
- |
- |
|
CPP_FR-2-BQS_SCRATCH_TOOSMALL |
2-Critical |
QFP BQS Scratch area too small for Frame Relay MFR feature usage size: [dec] need: [dec]. |
Cisco internal software error. QFP Frame Relay MFR initialization detected that the BQS scratch memory area is insufficient for Frame Relay MFR usage. The Frame Relay MFR Bundle interfaces will not be functional while this condition exists. |
cpp-ucode keyword:frame-relay |
LOG_STD_ACTION |
|
CPP_FR-2-PROXY_IPC_INIT_FAILED |
2-Critical |
Frame Relay Proxy IPC interface initialization failure result: [dec]. |
Cisco internal software error. FR initialization detected that the Proxy IPC interface initialization failed. The FR interfaces may not function properly while this condition exists. |
cpp-ucode keyword:frame-relay |
LOG_STD_ACTION |
|
CPP_FR-3-INV_PROXY_MSG |
3-Error |
CPP FR Proxy received invalid IPC message ID [dec] |
Cisco internal software error. CPP FR Proxy received an invalid message ID. This message will be ignored. |
cpp-ucode keyword:frame-relay |
LOG_STD_ACTION |
|
CPP_FR-3-MFR_INVALID_RX_DLCI |
3-Error |
Frame Relay MFR DLCI [dec] received from the peer |
Possible error on the peer device with Multilink FR. Received Multilink FR packet contained wrond DLCI number. |
cpp-ucode keyword:frame-relay |
LOG_STD_ACTION |
|
CPP_FR-3-PROXY_DUP_DLCI_ID |
3-Error |
QFP Frame Relay MFR Proxy [chars] [chars] duplicate DLCI [dec] for interface [chars] |
Cisco internal software error. QFP Frame Relay MFR Proxy message DLCI Add could not be processed for the indicated interface due use of a given DLCI on multiple member links within the same Frame Relay MFR Bundle. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition. |
cpp-ucode keyword:frame-relay |
LOG_STD_ACTION |
|
CPP_FR-3-PROXY_DUP_LINK_ID |
3-Error |
QFP Frame Relay MFR Proxy [chars] [chars] duplicate Link ID [dec] for interface [chars] |
Cisco internal software error. QFP Frame Relay MFR Proxy message Link Add could not be processed for the indicated interface due use of a given Link ID on multiple member links within the same Frame Relay MFR Bundle. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition. |
cpp-ucode keyword:frame-relay |
LOG_STD_ACTION |
|
CPP_FR-3-PROXY_INV_BUFFER_LIMIT |
3-Error |
QFP Frame Relay MFR Proxy [chars] [chars] indicated an invalid Rx buffer limit |
Cisco internal software error. QFP Frame Relay MFR was provided a invalid Rx buffer limit value. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition. |
cpp-ucode keyword:frame-relay |
LOG_STD_ACTION |
|
CPP_FR-3-PROXY_INV_BUNDLE_STATE |
3-Error |
QFP Frame Relay MFR Proxy [chars] [chars] invalid Bundle state [chars] [dec] for |
Cisco internal software error. QFP Frame Relay MFR Proxy message could not be processed due to the Frame Relay MFR Bundle being in an incorrect state to accept the message. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition. |
cpp-ucode keyword:frame-relay |
LOG_STD_ACTION |
|
CPP_FR-3-PROXY_INV_DLCI_INFO |
3-Error |
QFP Frame Relay MFR Proxy [chars] [chars] invalid PVC Info Base: 0x%08x Num: [dec] |
Cisco internal software error. QFP Frame Relay MFR Proxy message contained invalid Frame Relay MFR PVC information. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition. |
cpp-ucode keyword:frame-relay |
LOG_STD_ACTION |
|
CPP_FR-3-PROXY_INV_LINK_ID |
3-Error |
QFP Frame Relay MFR Proxy [chars] [chars] invalid Link ID [dec] for interface [chars] |
Cisco internal software error. QFP Frame Relay MFR Proxy message Link Add could not be processed for the indicated interface due to an invalid Link ID. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition. |
cpp-ucode keyword:frame-relay |
LOG_STD_ACTION |
|
CPP_FR-3-PROXY_INV_LINK_STATE |
3-Error |
QFP Frame Relay MFR Proxy [chars] [chars] invalid Link state [chars] [dec] for |
Cisco internal software error. QFP Frame Relay MFR Proxy message could not be processed due to the Frame Relay MFR Link being in an incorrect state to accept the message. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition. |
cpp-ucode keyword:frame-relay |
LOG_STD_ACTION |
|
CPP_FR-3-PROXY_INV_LOST_SEQ_TO |
3-Error |
QFP Frame Relay MFR Proxy [chars] [chars] indicated an invalid lost sequence |
Cisco internal software error. QFP Frame Relay MFR was provided a invalid lost sequence timeout value. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition. |
cpp-ucode keyword:frame-relay |
LOG_STD_ACTION |
|
CPP_FR-3-PROXY_INV_RX_TX_INTF_VALUE |
3-Error |
QFP Frame Relay MFR Proxy [chars] [chars] invalid Rx/Tx interface value [dec] for |
Cisco internal software error. QFP Frame Relay MFR Proxy was unable to complete the requested Frame Relay MFR Bundle state change or configuration update due to an invalid interface Rx/Tx designation in the proxy request. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition. |
cpp-ucode keyword:frame-relay |
LOG_STD_ACTION |
|
CPP_FR-3-PROXY_INV_SUB_DEV_ID |
3-Error |
QFP Frame Relay MFR Proxy [chars] [chars] invalid Sub-Device ID [dec] for interface [chars] |
Cisco internal software error. QFP Frame Relay MFR Proxy message Bundle Add could not be processed for the indicated interface due to an invalid Sub-Device ID. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition. |
cpp-mlppp keyword:none |
LOG_STD_ACTION |
|
CPP_FR-3-PROXY_INV_TX_LINK_WEIGHT |
3-Error |
QFP Frame Relay MFR Proxy [chars] [chars] indicated an invalid Tx Link weight |
Cisco internal software error. QFP Frame Relay MFR Proxy message contained invalid Tx Link weight information. The associated Frame Relay MFR Member Link and/or Bundle interface may not be fully functional as a result of this condition. |
cpp-ucode keyword:frame-relay |
LOG_STD_ACTION |
|
CPP_FR-3-PROXY_IPC_ALLOC_FAIL |
3-Error |
CPP Frame Relay Proxy response to msg id [dec] lost due to buffer allocation failure |
Cisco internal software error. CPP Frame Relay Proxy message processing detected a IPC buffer allocation failure during response processing. |
cpp-ucode keyword:frame-relay |
LOG_STD_ACTION |
|
CPP_FR-3-PROXY_NULL_BUNDLE |
3-Error |
QFP Frame Relay MFR Proxy [chars] [chars] NULL Bundle sub-block for |
Cisco internal software error. QFP Frame Relay MFR Proxy was unable to complete the requested Frame Relay MFR Bundle state change or configuration update due to an invalid or uninitialized Bundle sub-block. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition. |
cpp-ucode keyword:frame-relay |
LOG_STD_ACTION |
|
CPP_FR-3-PROXY_NULL_DLCI |
3-Error |
QFP Frame Relay MFR Proxy [chars] [chars] NULL PVC sub-block for |
Cisco internal software error. QFP Frame Relay MFR Proxy was unable to complete the requested Frame Relay MFR Member PVC state change or configuration update due to an invalid or uninitialized PVC sub-block. The associated Frame Relay MFR PVC interface may not be fully functional as a result of this condition. |
cpp-ucode keyword:frame-relay |
LOG_STD_ACTION |
|
CPP_FR-3-PROXY_NULL_LINK |
3-Error |
QFP Frame Relay MFR Proxy [chars] [chars] NULL Member Link sub-block for |
Cisco internal software error. QFP Frame Relay MFR Proxy was unable to complete the requested Frame Relay MFR Member Link state change or configuration update due to an invalid or uninitialized Member Link sub-block. The associated Frame Relay MFR Member Link interface may not be fully functional as a result of this condition. |
cpp-ucode keyword:frame-relay |
LOG_STD_ACTION |
|
CPP_FR-3-PROXY_SID_UPDATE_COMPLETE_ERROR |
3-Error |
QFP Frame Relay MFR Proxy [chars] SID Update Complete w/o Preceeding Lock |
Cisco internal software error. QFP Frame Relay MFR Proxy message processing detected a Bundle Schedule SID update sequence error. One or more interface schedules could have been affected. |
cpp-ucode keyword:frame-realy |
LOG_STD_ACTION |
|
CPP_FR-3-PROXY_SID_UPDATE_LOCK_ERROR |
3-Error |
QFP Frame Relay Proxy [chars] Multiple SID Update Locks to same interface |
Cisco internal software error. QFP Frame Relay MFR Proxy message processing detected a Bundle Schedule SID update sequence error. One or more interface schedules could have been affected. |
cpp-ucode keyword:frame_relay |
LOG_STD_ACTION |
|
CPP_FR-4-PROXY_IPC_ALLOC_FAIL2 |
4-Warning |
QFP Frame Relay MFR Proxy [chars] response lost due to buffer allocation |
Cisco internal software error. QFP Frame Relay MFR Proxy message processing detected a IPC buffer allocation failure during proxy response processing. The associated Frame Relay MFR functionality may not be fully functional as a result of this condition. |
cpp-ucode keyword:frame-relay |
LOG_STD_ACTION |
|
CPP_FR-4-PROXY_SYNC |
4-Warning |
QFP Frame Relay MFR Proxy [chars] [chars] Bundle/Link sync issue with interface [chars] |
Cisco internal software error. QFP Frame Relay MFR Proxy message processing detected a Bundle-Link state synchronization abnormality. This condition should be cosmetic. Full context of the message will aid in problem isolation. |
cpp-ucode keyword:frame-relay |
LOG_STD_ACTION |
|
CPP_FR-4-TX_BUNDLE_FLOWED_OFF |
4-Warning |
QFP Frame Relay MFR Tx Bundle [chars] flowed off for an abnormal duration due to one or more congested member links |
Possible Cisco internal software or hardware error. QFP Frame Relay MFR Tx processing detected that a Frame Relay MFR Bundle interface was flowed off for an extended period of time due to a congested member link queue. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition. |
cpp-ucode keyword:frame-relay |
LOG_STD_ACTION |
|
CPP_IPHC_PROXY-3-INVALID_IPC_INPUT |
3-Error |
[chars] CPP IPHC Client Proxy failure |
IPHC proxy failed because of receiving invalid sub-type or failed to allocate ipc response buffer. |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_LDN-2-PROXY_IPC_INIT_FAILED |
2-Critical |
CPP LDN Proxy IPC interface initialization failure result: [dec]. |
Cisco internal software error. CPP LDN initialization detected that the Proxy IPC interface initialization failed. The LDN Proxy will not be functional while this condition exists. |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_LDN-3-PROXY_GPM_RSRC_FAIL |
3-Error |
failure: [chars] |
LDN Proxy failed in performing a GPM operation. |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_LDN-3-PROXY_IPC_INVALID |
3-Error |
failure: [dec] |
LDN Proxy received an invalid IPC msg from the client. |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_LDN-3-PROXY_IPC_SEND |
3-Error |
failure: [chars] |
LDN Proxy send response failed response was dropped. |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_LDN-3-PROXY_METAPKT_ENQ |
3-Error |
subdevice id: [dec] failure: [dec] |
LDN Proxy metapacket enqueue failed. |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_MPASS-3-INVALID_VECTOR |
3-Error |
vector [dec] |
An invalid multipass vector was received |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_NAT_PROXY-3-INVALID_IPC_SUBTYPE |
3-Error |
subtype is [dec] |
The NAT proxy has receive an IPC with an unexpect subtype |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_NAT_PROXY-3-NAT_INIT_FAIL |
3-Error |
nat init failure rc= [dec] |
The NAT proxy has experience a failure when trying to init NAT |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_NAT_PROXY-3-NAT_SEND_IPC_FAIL |
3-Error |
rc= [dec] |
The NAT proxy has experience a failure when trying to send an IPC |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_NAT64_PROXY-3-INVALID_IPC_SUBTYPE |
3-Error |
subtype is [dec] |
The NAT64 proxy has received an IPC with an unexpected subtype |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_NAT64_PROXY-3-NAT_INIT_FAIL |
3-Error |
nat64 init failure rc= [dec] |
The NAT64 proxy has experience a failure when trying to init NAT64 |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_NAT64_PROXY-3-NAT64_INIT_FAIL |
3-Error |
nat64 init failure rc= [dec] |
The NAT proxy has experienced a failure when trying to initialize the NAT64 proxy |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_NAT64_PROXY-3-NAT64_IPC_FAIL |
3-Error |
rc= [dec] |
The NAT64 proxy has received an IPC with an unexpected format/data |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_NAT66_PROXY-3-INVALID_IPC_SUBTYPE |
3-Error |
subtype is [dec] |
The NAT66 proxy has received an IPC with an unexpected subtype |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_NAT66_PROXY-3-NAT66_INIT_FAIL |
3-Error |
nat66 init failure rc= [dec] |
The NAT proxy has experienced a failure when trying to initialize the NAT66 proxy |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_NAT66_PROXY-3-NAT66_IPC_FAIL |
3-Error |
rc= [dec] |
The NAT66 proxy has received an IPC with an unexpected format/data |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_NGIO-3-NGIO_FC_BADPATH |
3-Error |
NGIO flow control msg received on unexpected code path mod pid [dec] |
Flow control message received on unexpected code path |
cpp-ucode |
LOG_STD_RECUR_ACTION |
|
CPP_NGIO-3-NGIO_FC_IID |
3-Error |
NGIO flow control ID lookup failed:[chars] module pid/iid:[dec]/[dec] |
Flow control message from module contained an invalid identification field |
cpp-ucode |
LOG_STD_RECUR_ACTION |
|
CPP_NGIO-3-NGIO_MOD_PID |
3-Error |
NGIO flow control msg received with no config matching module pidmod pid:[dec] |
Flow control message received could not be matched with a module. |
cpp-ucode |
LOG_STD_RECUR_ACTION |
|
CPP_NGIO-5-NGIO_FC_PRIORITY |
5-Notice |
NGIO flow control msg processed at reduced priority mod pid:[dec] |
Flow control message from module was not properly prioritized. |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_NGIO-5-NGIO_PKT_PRIORITY |
5-Notice |
NGIO packet processed at flow control priority mod pid:[dec] |
Data packet from module was not properly prioritized. |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_PFR_PROXY-3-INVALID_IPC_SUBTYPE |
3-Error |
subtype is [dec] |
The PfR proxy has receive an IPC with an unexpected subtype |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_PFR_PROXY-3-PFR_INIT_FAIL |
3-Error |
pfr init failure rc= [dec] |
The PFR proxy has experienced a failure when trying to init PFR |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_PFR_PROXY-3-PFR_IPC_PAK_ALLOC_FAILED |
3-Error |
rc= [dec] |
Allocation of PFR IPC response pkt failed |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_PFR_PROXY-3-PFR_SEND_IPC_FAIL |
3-Error |
rc= [dec] |
The PfR proxy has experienced a failure when trying to send an IPC |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_PKT_SUBBLOCK-3-PKT_SB_MANAGE_FAIL |
3-Error |
rc=0x[hec] |
A packet subblock manage has failed |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_SBC-4-CPP_SBC_NULL_EXMEM |
4-Warning |
Unexpected NULL shared-local EXMEM handle - ref_count [dec] |
The error will be corrected and pinhole programming will continue. |
asr1k-sbc |
LOG_STD_NO_ACTION |
|
CPP_WPAN_PROXY-3-PROXY_IPC_INIT_FAILED |
3-Error |
[dec] |
IPC handler initialization failed. |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_WPAN_PROXY-3-PROXY_IPC_PACKET_ALLOCATION_FAILED |
3-Error |
[hec] |
Failed to allocate packet buffer for IPC |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_WPAN_PROXY-3-PROXY_IPC_SEND_FAILED |
3-Error |
[hec] |
Failed to send IPC packet. |
cpp-ucode |
LOG_STD_ACTION |
|
CPP_WPAN_PROXY-4-PROXY_IPC_INVALID_MSG |
4-Warning |
[hec] |
Received an invalid IPC messages subtype. |
cpp-ucode |
LOG_STD_ACTION |
|
CPPBQS-3-MULTICOMMITS |
3-Error |
Multiple outstanding [chars] commit events detected [dec] |
- |
- |
- |
|
CPPBQS-3-QMOVEFAIL |
3-Error |
CPP [dec] schedule [chars] queue move failed [hex] - SEID=[hex] SID=%#X |
A QFP BQS schedule queue move operation failed. |
qfp-bqs-internal |
LOG_STD_SH_TECH_ACTION |
|
CPPBQS-3-QMOVEQOSDIS |
3-Error |
QFP [dec] schedule [chars] queue move to [chars] unsupported QoS disabled |
QFP BQS schedule move to new output interface on different subdevice is unsupported. QoS for this schedule is disabled |
qfp-bqs-internal |
"Restore failed link or route so that schedule " "is moved back and QoS is restored. Or force the " "schedule to fail back to a link that is on " "the same subdevice the this schedule was " "originally on." |
|
CPPBQS-3-QMOVESTUCK |
3-Error |
QFP [dec] schedule [chars] queue move operation is not progressing as expected - seq [dec] |
A QFP schedule queue move operation is not proceeding as expected and can lead to packet drops. The most likely cause of a queue move operation getting stuck is having a rate based queue that has packets enqueued on it that are not being serviced very frequently or being starved due to higher priority queues causing an oversubscription of the physical output interface. |
qfp-bqs-internal |
"No action is required if QMVOEDONE message" " is also displayed following QMOVESTUCK." " If a QMOVEDONE or QMOVEPROC message is not" " displayed following QMOVESTUCK then" " collect the data from the following show" " commands:" " show platform" " show platform hardware qfp <active|standby> bqs status" " show platform hardware qfp <active|standby> bqs qmove info" " show platform hardware qfp <active|standby> bqs qmove child" " show platform hardware qfp <active|standby> bqs qmove flush" "Report the problem to the Cisco TAC providing" " the data from the above show commands." |
|
CPPBQS-3-RATE_RATIO_OPTIMIZATION |
3-Error |
QFP BQS detected invalid rate optimization nodes for [chars] |
QFP unable to optimize the rates due to missing optimization nodes |
qfp-bqs-internal |
"Enable 'platform qos optimize-rate-ratio' command " "before applying QOS." |
|
CPPBQS-3-REPARENTFAIL |
3-Error |
QFP [dec] schedule [chars] reparent failed [hex] - SEID=%#X SID=[hex] |
A QFP BQS schedule reparent operation failed. |
qfp-bqs-internal |
LOG_STD_SH_TECH_ACTION |
|
CPPBQS-3-SRT_PERR_RESORT_FAIL |
3-Error |
QFP [dec] unable to resort to correct parity error at SEID=%#X |
A QFP BQS SRT parity error occurred that was uncorrectable |
qfp-bqs-internal |
LOG_STD_NO_ACTION |
|
CPPBQS-4-MAXRATEPROFILELIMITEXCEEDED |
4-Warning |
QFP [dec].[dec] Max Rate Profile limit [dec] exceeded at [dec]. |
Max number of Max Rate Profiles supported on QFP has been exceeded. Configuration failure is possible causing unpredictable results. |
- |
"Reduce the number of unique shape rates in the configuration" |
|
CPPBQS-4-MINRATEPROFILELIMITEXCEEDED |
4-Warning |
QFP [dec].[dec] Min Rate Profile limit [dec] exceeded at [dec]. |
Max number of Min Rate Profiles supported on QFP has been exceeded. Configuration failure is possible causing unpredictable results. |
- |
"Reduce the number of unique bandwidth rates in the configuration" |
|
CPPBQS-4-QLIMITEXCEEDED |
4-Warning |
QFP [dec].[dec] QoS Queue limit [dec] exceeded at [dec]. |
Max number of QoS queues supported on QFP has been exceeded. Configuration failure is possible causing unpredictable results. |
- |
"Reduce the size of the QoS configuration" |
|
CPPBQS-4-QMOVEDONE |
4-Warning |
QFP [dec] schedule [chars] queue move done |
A QFP BQS schedule queue move operation was not proceeding in a timely manner and flagged as being stuck but has since completed. |
cpp-sw |
LOG_STD_SH_TECH_ACTION |
|
CPPBQS-4-QMOVEPROC |
4-Warning |
QFP [dec] schedule [chars] queue move in progress seq [dec] |
A QFP BQS schedule queue move operation is not proceeding or is proceeding at a slow rate which can lead to packet drops. The most likely cause of a queue move operation getting stuck is having a rate based queue that has packets enqueued on it that are not being serviced very frequently or being starved due to higher priority queues causing an oversubscription of the physical output interface. |
qfp-bqs-internal |
"No action is required if QMVOEDONE message" " is also displayed following QMOVEPROC." " If QMOVEDONE message is not displayed or" " you continue to see QMOVEPROC messages" " displayed then collect the data from" " the following show commands:" " show platform" " show platform hardware qfp <active|standby> bqs status" " show platform hardware qfp <active|standby> bqs qmove info" " show platform hardware qfp <active|standby> bqs qmove child" " show platform hardware qfp <active|standby> bqs qmove flush" "Report the problem to the Cisco TAC providing" " the data from the above show commands." |
|
CPPBQS-4-SRTMEMLOW |
4-Warning |
QFP [dec] HW [chars]:[chars] schedule resources depleted - [dec]%% available |
QFP BQS HW schedule resources have dropped below critical threshold. |
qfp-bqs-internal |
LOG_STD_REDUCE_ACTION |
|
CPPBQS-4-YODASRTMEMLOW |
4-Warning |
QFP [dec].[dec] HW [chars]:[chars]:[chars] schedule resources depleted - [dec]%% available |
QFP BQS HW schedule resources have dropped below critical threshold. |
qfp-bqs-internal |
LOG_STD_REDUCE_ACTION |
|
CPPBQS-6-QLIMITOK |
6-Information |
QFP [dec].[dec] QoS Queue limit [dec] was exceeded and is now within platform specifications at [dec]. |
Max number of QoS queues supported on QFP was exceeded. It is now within platform specifications |
- |
- |
|
CPPBQS-6-QMOVEQOSENA |
6-Information |
QFP [dec] schedule [chars] queue move to [chars] QoS enabled |
QFP BQS schedule that was disabled due to having been moved to an output interface on different subdevice has now moved back to the original subdevice and QoS is now enabled again. |
- |
- |
|
CPPBQS-6-QMRTDUMP |
6-Information |
QFP Queue Manager Real-Time trace dump - [chars] |
The QFP Queue Manager Real-Time trace data dumping to disk has either started or completed. |
- |
- |
|
CPPBQS-6-QMRTREPLAY |
6-Information |
QFP Queue Manager Real-Time event replay [chars] - [chars] |
The QFP Queue Manager Real-Time event data replay from disk file status display |
- |
- |
|
CPPCDM-3-ERROR_NOTIFY |
3-Error |
QFP [dec] thread [dec] encountered an error -Traceback= [chars] [chars] |
A QFP fault has occurred. |
cpp-ucode |
LOG_STD_NO_ACTION |
|
CPPDRV-2-HALT |
2-Critical |
[chars][dec] Interrupt : [chars] Seq:%03d Halt bit set. |
A Serious CPP hardware error has occurred. |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-ALLOC_NOTF |
3-Error |
CPP[dec]: Failed to Allocate: [chars] |
A function failed to allocate data. |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-CLEANUP_NOTF |
3-Error |
Failed to Cleanup: [chars] |
A function failed to cleanup data. |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-DESTROY_NOTF |
3-Error |
Failed to destroy connection :[chars] |
A function failed to destroy a connection. |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-FATAL_ACQUIRE_LOCK |
3-Error |
CPP[dec]: 0x[hec] Failed to acquire memory lock [chars] |
SW failed to acquire shared memory lock |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-FATAL_ALLOCATE |
3-Error |
CPP[dec]: 0x[hec] Failed to allocate [chars] - [chars] |
Failed to allocate data |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-FATAL_ATTACH |
3-Error |
CPP[dec]: 0x[hec] FAILED: to attach [chars] |
Device Failed to attach |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-FATAL_CPP_SUBDEV_ACCESS |
3-Error |
CPP[dec].[dec]: An access error has been reported. Error count [dec]. |
The system has reported an error while accessing a CPP subdevice |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-FATAL_CPU_FEATURE |
3-Error |
CPP[dec]: CPU lacks feature [chars]. Packet forwarding disabled. |
The currently installed CPU lacks a certain feature that is required by the forwarding engine. The QFP is operating with reduced functionality with packet forwarding disabled. |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-FATAL_CREATE |
3-Error |
0x[hec] Failed to create [chars] - [chars] |
Failed to create device |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-FATAL_CREATE_ID |
3-Error |
CPP[dec]: 0x[hec] Failed to create [chars] - [chars] |
Failed to create device |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-FATAL_GET_DETAILS |
3-Error |
CPP[dec]: 0x[hec] Failed to get [chars] details - [chars] |
Failed to get device details |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-FATAL_INIT |
3-Error |
0x[hec] Failed to initialize [chars] - [chars] |
Failed to init device |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-FATAL_INIT_ID |
3-Error |
CPP[dec]: 0x[hec] Failed to initialize [chars] - [chars] |
Failed to init device |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-FATAL_INTERNAL |
3-Error |
CPP[dec]: 0x[hec] Internal Error [chars] |
Internal coding error. |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-FATAL_INTERRUPT_CLEAR |
3-Error |
CPP[dec]: 0x[hec] Failed to clear [chars] interrupt |
Failed to clear an interrupt node |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-FATAL_INTERRUPT_HANDLER |
3-Error |
CPP[dec]: 0x[hec] Failed to register [chars] interrupt handler - [chars] |
Failed to register interrupt handler |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-FATAL_INTERRUPT_INIT |
3-Error |
CPP[dec]: 0x[hec] Failed to initialize [chars] interrupt - [chars] |
Failed to initialize an interrupt |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-FATAL_INTERRUPT_OPEN |
3-Error |
CPP[dec]: 0x[hec] Failed to access [chars] interrupt node - [chars] |
Failed to open an interrupt |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-FATAL_MEM_CLEAR |
3-Error |
CPP[dec]: 0x[hec] Failed to clear memory [chars] |
SW failed to clear memory location |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-FATAL_MEM_SIZE |
3-Error |
CPP[dec]: 0x[hec] Failed to acquire memory size [chars] |
SW failed to acquire the size of a block of memory |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-FATAL_MEM_WRITE |
3-Error |
CPP[dec]: 0x[hec] Failed to write to memory [chars] |
SW failed to write to a memory location |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-FATAL_MIN_CPU |
3-Error |
CPP[dec]: Insufficent number of CPUs detected = [dec] required = [dec] |
The current system lacks a sufficent number of CPUs or cores |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-FATAL_PLAT_DB |
3-Error |
CPP[dec]: 0x[hec] Platform failure accessing [chars] |
Platform DB query failed |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-FATAL_RELEASE_LOCK |
3-Error |
CPP[dec]: 0x[hec] Failed to release memory lock [chars] |
SW failed to release shared memory lock |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-FATAL_UNSUPPORT |
3-Error |
CPP[dec]: 0x[hec] - unsupported CPP TYPE. CPP TYPE:[dec] |
Unsupported CPP TYPE |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-GUEST_CPU_FEATURE |
3-Error |
CPP[dec]: Guest CPU lacks feature [chars]. |
The currently installed Guest CPU lacks a certain feature that is required by the forwarding engine but that feature is supported by the Host CPU. The QFP is operating with normal functionality using the host CPU feature but live migration to a host which lacks this feature will result in a crash. |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-HOT |
3-Error |
[chars][dec] Interrupt : [chars] Seq:%03d repeating interrupt has been disabled. |
A repeating hardware interrupt has been disabled. |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-INIT_NOTF |
3-Error |
Failed to initialize: [chars] |
A function failed to initialize. |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-INIT_NOTF_ID |
3-Error |
CPP[dec]: Failed to initialize: [chars] |
A function failed to initialize. |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-LOCKDOWN |
3-Error |
QFP[dec].[dec] CPP Driver LOCKDOWN encountered due to previous fatal error [chars]: [chars]. |
A fatal error has caused the driver to LOCKDOWN. |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-LOCKDOWN_INITIATED |
3-Error |
QFP[dec].[dec] CPP Driver LOCKDOWN being triggered due to fatal error. |
A fatal error has caused the process to initiate LOCKDOWN. |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-SRT_PERR_FAILURE |
3-Error |
[chars][dec] Failed to correct BQS SRT Parity error. |
Failed to correct a BQS SRT Parity error. |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-TCAM_PERR |
3-Error |
[chars][dec] TCAM Parity error TCAM device #[dec] at offset 0x%08X. |
A Parity error has occurred in a TCAM device. |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-3-TCAM_PERR_FAILURE |
3-Error |
[chars][dec] Failed to correct TCAM Parity error. Parity error detection disabled. |
Failed to correct a TCAM Parity error and further detection has been disabled. |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-4-ADRSPC_LIMIT |
4-Warning |
Address space limit [dec] KB reached mapping block [chars] size [dec] dynamically over limit space: [dec] KB |
The process indicated tried to map more of the Forwarding Engine's address space than was allocated for it. A slower access method will be used instead. This will lower the performance of some operations which require accesses to the Forwarding Engine |
cpp-sw |
LOG_STD_SH_TECH_ACTION |
|
CPPDRV-4-CORE_TABLE |
4-Warning |
CPP[dec] specific core dump table '[chars]' not found using minimal fallback table '[chars]' instead |
The QFP configuration found on this board did not match any of the tables which define which data has to be collected if a fatal error is detected. Instead a minimal table is used which covers most of the QFP registers. The QFP is fully operational. |
cpp-sw |
LOG_STD_SH_TECH_ACTION |
|
CPPDRV-4-CPU_FEATURE |
4-Warning |
CPP[dec]: CPU lacks feature [chars]. Performance may be sub-optimal. |
The currently installed CPU lacks a certain feature that improve performance of the forwarding engine. The QFP is fully operational but may operate at a reduced capacity. |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-4-FIXUP_OCCURRED |
4-Warning |
Alignment fixup @ PC=%p #hits=[dec] fault addr: %p. |
A misalignment was handled by a fixup signal handler |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-4-FIXUP_OCCURRED_TRACEBACK |
4-Warning |
Alignment fixup #hits=[dec] Traceback [chars] |
A misalignment was handled by a fixup signal handler |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-4-FUTURE_FATAL_CPU_FEATURE |
4-Warning |
CPP[dec]: CPU lacks feature [chars] required in a future release. |
The currently installed CPU lacks a certain feature that will be required by the forwarding engine in a future release. Caution is advised before upgrading to a newer release to ensure the CPU has the minimum set of CPU features necessary to operate. |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-4-HW_REV_OLD |
4-Warning |
Found HW revision [chars] using [chars] based on [chars]. No customer deployment. |
The specified board or chip showed an incorrect invalid or too old hardware revision. That hardware revision was possibly overridden |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-6-ACCTRC16B |
6-Information |
Access CPP [dec] address 0x%08llX Blk/Off:[chars]/0x%08llX [chars] %3d bytes |
A CPP access was traced |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-6-ACCTRC8B |
6-Information |
Access CPP [dec] address 0x%08llX Blk/Off:[chars]/0x%08llX [chars] %3d bytes |
A CPP access was traced |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPDRV-6-INTR |
6-Information |
[chars][dec] Interrupt : [chars] |
A CPP hardware interrupt has occurred. |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPEXMEM-3-NOMEM |
3-Error |
QFP: [dec] [chars] memory allocation of [dec] bytes by [chars] failed |
A request for QFP memory resource allocation has failed due to running out of memory. QFP memory is used by the datapath for packet forwarding. |
- |
"Display the memory allocation usage" " per feature to determine where most" " of the memory is being used. This can" " help identify where to adjust feature" " scaling. The following CLI will display" " the memory utilization: show platform" " hardware qfp act infrastructure exmem" " statistics user. If the system crashed" " prior to issuing this command you can" " retrieve the information from the binary" " trace log file for the process that " " generated this error message." |
|
CPPEXMEM-3-TOPUSER |
3-Error |
QFP: [dec] Top User: [chars] [chars]: [dec] Type: [chars] |
A request for QFP memory resource allocation has failed due to running out of memory. The top consumer of exmem is provided with this message to possibly identify the source for running out of memory. QFP memory is used by the datapath for packet forwarding. |
- |
LOG_STD_NO_ACTION |
|
CPPEXMEM-4-LOWMEM |
4-Warning |
CPP [dec] [chars] memory low - [dec] percent depleted |
A CPP memory resource has dropped below a critical level. |
- |
LOG_STD_NO_ACTION |
|
CPPEXMEM-5-MEM |
5-Notice |
CPP [dec] [chars] memory recovered - [dec] percent depleted |
A CPP memory resource has recovered above the low threshold level. |
- |
LOG_STD_NO_ACTION |
|
CPPFW-4-CHUNK_CREATE_FAIL |
4-Warning |
Failed to create chunk pool: [chars] : [chars] |
Could not create memory chunk pool. Configuration Failed |
iosxe-zbfw |
LOG_STD_REDUCE_ACTION |
|
CPPFW-4-L7_NBAR_TCAMID_MEM_ALLOC_FAIL |
4-Warning |
Failed to create l7 nbar tcam entry zone pair: [chars] class [chars] : [chars] |
Could not allocate memory for l7 nbar cce tcam info. Configuration Failed |
iosxe-zbfw |
LOG_STD_REDUCE_ACTION |
|
CPPFW-4-NO_CG |
4-Warning |
[chars] Could not locate class group [chars] zone_pair id [dec]:[chars] cg id: [dec] |
Could not locate class group policy inforamtion. Configuration Failed |
iosxe-zbfw |
LOG_STD_NO_ACTION |
|
CPPFW-4-NO_CLASS_CG |
4-Warning |
[chars]: Could not locate class [chars] zone_pair id [dec]:[chars] policy: [dec]:[chars] class id: [dec] |
Could not Locate class inforamtion. Configuration Failed |
iosxe-zbfw |
LOG_STD_NO_ACTION |
|
CPPFW-4-NO_FM_STAT_MAP_CG |
4-Warning |
[chars]: Could not locate fm stat map table: [chars]. zone_pair id: [dec]:[chars] cg: [dec]:[chars] |
Could not Locate CPP FM_STAT mapping table. Configuration Failed |
iosxe-zbfw |
LOG_STD_NO_ACTION |
|
CPPFW-4-NO_MEM_ZP_CG_ARY_CG |
4-Warning |
[chars]: [chars]: Could not allocate [chars] [dec] bytes x [dec] entries for [dec] bytes of memory zone pair: [dec]:[chars] policy: [dec]:[chars] |
Could not allocate an array of memory of the given size and entries. Configuation Failed |
iosxe-zbfw |
"Configureation is too large for platform." " Attempt to reduce" " size of firewall policy stats etc. " " or disable other features" |
|
CPPFW-4-WRITE_HW_L7_NBAR_TCAMID_FAIL |
4-Warning |
Failed to write l7 nbar tcamid [chars] to data plane: zone pair: [chars] class [chars] : [chars] |
Could not write l7 nbar cce tcam info to data plane. Configuration Failed |
iosxe-zbfw |
LOG_STD_REDUCE_ACTION |
|
CPPFW-4-WRITE_HW_MEM_FAIL_CG |
4-Warning |
[chars]: [chars]: [chars]: zone_pair id: [dec]:[chars] policy: [dec]:[chars] class: [chars] |
Could not write data to data plane. Configuration Failed |
iosxe-zbfw |
LOG_STD_NO_ACTION |
|
CPPFW-4-ZBFW_GENERIC_FAIL |
4-Warning |
zbfw : [chars] |
Failure in zbfw |
iosxe-zbfw |
LOG_STD_NO_ACTION |
|
CPPHA-3-BULKSYNC |
3-Error |
bulk sync processing failed to complete |
- |
- |
- |
|
CPPHA-3-CDMDONE |
3-Error |
CPP [dec] microcode crashdump creation completed. |
The CDM has completed generating microcode crashdump. |
- |
LOG_STD_SH_TECH_ACTION |
|
CPPHA-3-CHUNKALLOC |
3-Error |
Chunk allocation failed [dec] |
- |
- |
- |
|
CPPHA-3-CHUNKCREATE |
3-Error |
Chunk Create failed [dec] |
- |
- |
- |
|
CPPHA-3-CHUNKFREE |
3-Error |
Chunk free failed [dec] |
The CPP bulk synchronization processing failed on the standby. |
- |
LOG_STD_SH_TECH_ACTION |
|
CPPHA-3-EXMEMALLOC |
3-Error |
exmem allocation failed |
- |
- |
- |
|
CPPHA-3-EXMEMBIND |
3-Error |
bind to exmem failed to complete |
- |
- |
- |
|
CPPHA-3-FAILURE |
3-Error |
CPP [dec] failure [chars] detected |
A CPP failure has been detected. |
cpp-ucode |
LOG_STD_SH_TECH_ACTION |
|
CPPHA-3-FAULT |
3-Error |
CPP:[dec].[dec] desc:[chars] det:[chars] class:[chars] sev:[chars] id:[dec] cppstate:[chars] res:[chars] flags:0x[hec] cdmflags:0x[hec] |
A CPP fault has occurred. |
cpp-ucode |
LOG_STD_NO_ACTION |
|
CPPHA-3-FAULTCRASH |
3-Error |
CPP [dec].[dec] unresolved fault detected initiating crash dump. |
A unresolved fault detected initiating crash dump. |
- |
LOG_STD_SH_TECH_ACTION |
|
CPPHA-3-FAULTRATE |
3-Error |
CPP:[dec].[dec] desc:[chars] det:[chars] class:[chars] sev:[chars] id:[dec] cppstate:[chars] res:[chars] flags:0x[hec] cdmflags:0x[hec] |
A CPP fault has occurred. |
cpp-ucode |
LOG_STD_NO_ACTION |
|
CPPHA-3-FDBQUERY |
3-Error |
[chars] FDB query failed [dec] [chars] |
- |
- |
- |
|
CPPHA-3-INITFAIL |
3-Error |
CPP [dec] initialization failed - [chars] [hex] |
A CPP initialization failed. |
cpp-sw |
LOG_STD_SH_TECH_ACTION |
|
CPPHA-3-NOCDM |
3-Error |
CPP [dec] CDM not running. |
The CDM process is not running. |
- |
LOG_STD_SH_TECH_ACTION |
|
CPPHA-6-SYSINIT |
6-Information |
CPP HA system [chars]. |
CPP system initialization state. |
- |
LOG_STD_NO_ACTION |
|
CPPHA-7-READY |
7-Debug |
CPP [dec] loading and initialization complete |
A CPP has been successfully loaded and initialized\n\ ready to be configured for forwarding packets. |
- |
LOG_STD_NO_ACTION |
|
CPPHA-7-START |
7-Debug |
CPP [dec] [chars] |
A CPP is being started. |
- |
LOG_STD_NO_ACTION |
|
CPPHA-7-SYSREADY |
7-Debug |
CPP client process [chars] [dec] of [dec] ready. |
A CPP Client process has started and registered with\n\ CPP HA Server. |
- |
LOG_STD_NO_ACTION |
|
CPPOSLIB-3-CLEAN_NOTIFY |
3-Error |
Failed to cleanup: [chars] |
A function failed to cleanup data. |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPOSLIB-3-ERROR_NOTIFY |
3-Error |
[chars] encountered an error |
Print error message to console |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPOSLIB-3-GET_NOTIFY |
3-Error |
Failed to get data: [chars] |
A function failed to get data. |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPOSLIB-3-INIT_NOTIFY |
3-Error |
Failed to initialize: [chars] |
A function failed to initialize. |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPOSLIB-3-REGISTER_NOTIFY |
3-Error |
Failed to register: [chars] |
A function failed to register. |
cpp-sw |
LOG_STD_NO_ACTION |
|
CPPUI-3-ERROR_NOTIFY |
3-Error |
[chars] |
An UI fault has occurred. |
- |
LOG_STD_ACTION |
|
CPU_NET-0-QUEUE_STUCK |
0-Emergency |
The interface between the CPU and the switch has\n become stuck. The switch must now reset to clear this condition\n. Retrieval queue [dec].\n |
The CPU can no longer communicate with the network. |
- |
"Reload the system." |
|
CPU_REDUN -2-INITSYS |
2-Critical |
[chars] |
A software error occurred during initialization of the CPU redundancy subsystem |
- |
"Check for sufficient processor memory." LOG_STD_ACTION |
|
CPU_REDUN-3-4MSEC_DISABLED |
3-Error |
[chars] [dec] |
The 4msec timer interrupt was shut off for an extended period while the hardware watchdog was enabled. |
- |
LOG_STD_ACTION |
|
CPU_REDUN-3-BKPLN_IDPROM_ACCESS |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
The alarm appears when the processor can not access its backplane IDPROM. |
- |
LOG_STD_ACTION |
|
CPU_REDUN-3-CAPAB_SIZE |
3-Error |
Mismatch in [chars]. Active=[dec] Standby=[dec]. |
Standby CPU is reporting lower Capabilities than the Active CPU. See message text for type of limitation. |
- |
"Check for sufficient Standby CPU capabilities." LOG_STD_ACTION |
|
CPU_REDUN-3-CAPAB_VERS |
3-Error |
Mismatch in [chars]. Active=[dec].[dec] Standby=[dec].[dec]. |
Standby CPU is reporting lower versions than the Active CPU. See message text for type of limitation. |
- |
"Check Standby CPU version numbers." LOG_STD_ACTION |
|
CPU_REDUN-3-CAPABILITIES |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
The alarm appears when the capabilities reported by the standby processor are less than the active processor. The processors are conditionally redundant which means that a switchover could result in a partial loss of system control. |
- |
LOG_STD_ACTION |
|
CPU_REDUN-3-DRIVER_MISSING |
3-Error |
Missing [chars] driver support on Standby. Active=[dec].[dec] |
Standby CPU is missing support for one of the drivers available on the Active CPU. The corresponding linecard will go down in the event of a switchover. |
- |
"May require a software upgrade on the Standby CPU. " LOG_STD_ACTION |
|
CPU_REDUN-3-DRIVER_VERSIONS |
3-Error |
Mismatch in [chars] driver versions. Active=[dec].[dec] Standby=[dec].[dec]. |
Standby CPU is reporting lower versions than the Active CPU. See message text for type of limitation. May result in a loss of connections. |
- |
"May require a software upgrade on the Standby CPU. " LOG_STD_ACTION |
|
CPU_REDUN-3-EHSA_SVCS |
3-Error |
[chars] [chars] |
An error occurred that affects CPU Redundancy services. The details about what was attempted and what went wrong will be printed. |
- |
LOG_STD_ACTION |
|
CPU_REDUN-3-GT_STATUS_REG |
3-Error |
Parity Error on PCI Bus from PCI Device |
A Parity error on PCI bus has occurred while validating the GT64120 PCI device hanging off the PCI bus |
ons155xx-cpu |
"Check whether it is a GT64120 device.\n" LOG_STD_ACTION |
|
CPU_REDUN-3-INCONSISTENT_STATES |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
The alarm appears when the processor redundancy state is either not consistent with the peer state or the software state is not consistent with the hardware state. |
- |
LOG_STD_ACTION |
|
CPU_REDUN-3-INIT_ERROR |
3-Error |
[chars] [dec] [dec] |
A subsystem initialization error occurred. |
- |
LOG_STD_NO_ACTION |
|
CPU_REDUN-3-INTRPT_HOG |
3-Error |
[chars] [dec] sec [chars] = [hec] |
The CPU redundancy process didn't run for a long time because an interrupt routine ran too long. |
- |
LOG_STD_ACTION |
|
CPU_REDUN-3-INVALID_CPU_STATES |
3-Error |
Detected invalid redundancy states local = [chars] peer = [chars] |
Detected an invalid combination of redundant states |
- |
LOG_STD_NO_ACTION |
|
CPU_REDUN-3-INVALID_MSG |
3-Error |
Incorrectly formatted message 0x[hec] 0x[hec] received by [chars] |
Inconsistent message data was received from the peer CPU possibly due to an incompatible image version. |
- |
LOG_STD_ACTION |
|
CPU_REDUN-3-LOCK_ERR |
3-Error |
Can't get Global Lock |
Peer CPU won't relinquish the arbitration lock. |
- |
"Check that both the local and peer CPUs " "are fully seated in the backplane. Check " "the health of the Peer CPU." LOG_STD_ACTION |
|
CPU_REDUN-3-MULTI_CARD_ACCESS |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
The alarm appears when the processor has failed the linecard access test for multiple linecards. |
- |
LOG_STD_ACTION |
|
CPU_REDUN-3-PCI_STATUS_REG |
3-Error |
Status error in PCI device [dec] |
A PCI Status registry error in PCI device has been detected when validating the PCI device hanging off the PCI bus |
ons155xx-cpu |
"Check whether it is a valid PCI device Manhattan." "\n" LOG_STD_ACTION |
|
CPU_REDUN-3-PCI_TEST |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
The alarm appears when the processor has failed the online diagnostic internal PCI bus test. |
- |
LOG_STD_ACTION |
|
CPU_REDUN-3-PCI_VENDORID_MISMATCH |
3-Error |
Error/Mismatch in reading Vendor ID for PCI device [dec] |
The PCI Vendor ID error/mismatch has been detected when validating the PCI device hanging off the PCI bus |
ons155xx-cpu |
"Check the vendor ID of the PCI device attached it should of a macro value like: CLPD6729_VENDOR_ID" "\n" LOG_STD_ACTION |
|
CPU_REDUN-3-PCMCIA_TEST |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
The alarm appears when the processor has failed the online diagnostic internal PCMCIA slot test. |
- |
LOG_STD_ACTION |
|
CPU_REDUN-3-PEER_COMM |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
The alarm appears when the peer processor is present but not responding or sending keepalives. |
- |
LOG_STD_ACTION |
|
CPU_REDUN-3-PEER_MISSING |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
The alarm appears when the peer processor is either missing or can not be detected. The active processor currently is not being protected. |
- |
LOG_STD_ACTION |
|
CPU_REDUN-3-PEER_SEVERITY_ERR |
3-Error |
Invalid peer CPU severity [dec] current peer register=0x[hec] |
Peer CPU is reporting an invalid severity value. |
- |
"Check that both the local and peer CPUs " "are fully seated in the backplane. Check " "the health of the Peer CPU." LOG_STD_ACTION |
|
CPU_REDUN-3-PEER_SRC_REGS |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
The alarm appears when the active processor is detecting bad parity on the active/standby bits read from the standby processor. |
- |
LOG_STD_ACTION |
|
CPU_REDUN-3-PEER_STATE_ERR |
3-Error |
Invalid peer CPU state [chars] current peer register=0x[hec] |
Peer CPU is reporting an invalid redundancy state. |
- |
"Check that both the local and peer CPUs " "are fully seated in the backplane. Check " "the health of the Peer CPU." LOG_STD_ACTION |
|
CPU_REDUN-3-RCSF_FAIL |
3-Error |
Attempt to sync running config to standby failed |
Unable to send Running Config file to Standby CPU |
- |
LOG_STD_NO_ACTION |
|
CPU_REDUN-3-READBACK_ERR |
3-Error |
Can't change my state. desired state [chars] read-back [chars] |
Local CPU can't set its redundancy state to the desired calculated value |
- |
"Check health of local CPU." LOG_STD_ACTION |
|
CPU_REDUN-3-SLOT_IDPROM_MISMATCH |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
The alarm appears when the slot ID read from the backplane IDPROM does not match the slot ID read from the SRC. |
- |
LOG_STD_ACTION |
|
CPU_REDUN-3-SRC_TEST |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
The alarm appears when the processor has failed the online diagnostic internal SRC test. |
- |
LOG_STD_ACTION |
|
CPU_REDUN-3-STARTUP_SYNC_FAIL |
3-Error |
Attempt to sync [chars] config to standby failed |
Unable to send Startup or Private Config file to Standby CPU |
- |
LOG_STD_NO_ACTION |
|
CPU_REDUN-3-SUBSYS_COMPAT |
3-Error |
[chars] [chars] software subsystem. Active=[dec] Standby=[dec]. |
Standby CPU software subsystem is older or missing. See message text for software subsystem type. May result in feature losses in the event of a switchover. |
- |
"May require a software upgrade on the Standby CPU. " LOG_STD_ACTION |
|
CPU_REDUN-3-SW_STATE_MISMATCH |
3-Error |
Software state [chars] doesn't reflect local hardware [chars] |
Software state is not following the underlying hardware redundancy state |
- |
LOG_STD_ACTION |
|
CPU_REDUN-3-UART_FAILURE |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
This alarm appears when the processor can't transmit characters on the console UART. It indicates a probable equipment failure |
- |
"If the symptom persists following a reload " "remove and replace the processor module." |
|
CPU_REDUN-3-UNKNOWN_COMMON |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
If the alarm appears when this is asserted for a standby processor with a different software image it indicates an alarm condition on the peer that the active processor can not decode. If this is asserted for the active processor it indicates a software error condition. |
- |
LOG_STD_ACTION |
|
CPU_REDUN-3-UNKNOWN_MSG |
3-Error |
Unknown message type 0x[hec] received by [chars] |
An unknown message type was received from the peer CPU possibly due to an incompatible image version. |
- |
LOG_STD_ACTION |
|
CPU_REDUN-3-UNKNOWN_PLAT |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
If the alarm appears when this is asserted for a standby processor with a different software image it indicates an alarm condition on the peer that the active processor can not decode. If this is asserted for the active processor it indicates a software error condition. |
- |
LOG_STD_ACTION |
|
CPU_REDUN-4-REPROGRAM_ACTIVE_CPU |
4-Warning |
Active CPU FPGA has been \nreprogrammed. Please remove and re-insert the CPU in slot [dec] or\npower-cycle the box for the new FPGA to take effect. |
Active CPU FPGA has been reprogrammed. This CPU is now running with old FPGA and it needs to be hot-swapped or the system needs to be power-cycled for the new FPGA to take effect. |
- |
LOG_STD_NO_ACTION |
|
CPU_REDUN-4-STARTUP_CONFIG_MISSING |
4-Warning |
Non-volatile configuration memory is not present |
The startup-config is missing. This may be due to either a manual user erase command or an interrupted write to the startup-config. |
- |
"Do a copy running-config startup-config to save" "current system configuration. " LOG_STD_RECUR_ACTION |
|
CPU_REDUN-4-UNPROTECTED |
4-Warning |
[chars] [dec] [chars] |
System is running for an extended period in an unprotected mode even though a peer CPU is present |
- |
"Check the health of the Peer CPU. Configure as " "maintenance mode to intentionally suppress error " "messages." LOG_STD_ACTION |
|
CPU_REDUN-5-BASIC_CAPABILITY |
5-Notice |
Peer CPU hardware and software is fully compatible. |
Standby CPU H/W drivers and software subsystems have matching versions and capabilities. |
- |
LOG_STD_NO_ACTION |
|
CPU_REDUN-5-EHSA_SVCS_RESP |
5-Notice |
Sending [chars] = [dec] |
Normal response for CPU EHSA Redundancy services. The details about what was sent will be printed. |
- |
LOG_STD_NO_ACTION |
|
CPU_REDUN-5-FORCE_CLOSE |
5-Notice |
Forcibly closing fd: [dec] name:[chars] |
A file activity timeout occurred on the slave. |
- |
LOG_STD_NO_ACTION |
|
CPU_REDUN-5-NEGOTIATED_SWITCHOVER |
5-Notice |
[chars] [dec] |
Reloading due to a negotiated switchover. |
- |
LOG_STD_NO_ACTION |
|
CPU_REDUN-5-PEER_EXITED_IOS |
5-Notice |
Peer CPU has exited IOS |
Peer CPU has exited IOS. |
- |
LOG_STD_NO_ACTION |
|
CPU_REDUN-5-PEER_REMOVED |
5-Notice |
Peer CPU has been removed from the chassis |
Peer CPU has been removed from the chassis. |
- |
LOG_STD_NO_ACTION |
|
CPU_REDUN-5-RCSF_SYNCED |
5-Notice |
Running config successfully synced to standby |
Running Config file was sent to the Standby CPU |
- |
LOG_STD_NO_ACTION |
|
CPU_REDUN-5-RELOAD_COMM_DOWN |
5-Notice |
[chars] |
Reloading standby since Active CPU shows loss of comm. |
- |
LOG_STD_NO_ACTION |
|
CPU_REDUN-5-STARTUP_CONFIG_SYNCED |
5-Notice |
Startup config successfully synced to standby |
Startup Config file was sent to the Standby CPU |
- |
LOG_STD_NO_ACTION |
|
CPU_REDUN-5-STATE_MISMATCH_RELOAD |
5-Notice |
[chars] |
Reloading due to a hardware software state mismatch. |
- |
LOG_STD_NO_ACTION |
|
CPU_REDUN-5-STATUS_CHG |
5-Notice |
[chars] sev [dec] peer is [chars] sev [dec] |
A CPU hardware redundancy status change occurred. |
- |
LOG_STD_NO_ACTION |
|
CPU_REDUN-5-SWITCHOVER |
5-Notice |
Switchover occurred. Reason: [chars] |
A CPU switchover took place. The reported reason is listed in the error message text. |
- |
LOG_STD_NO_ACTION |
|
CPU_REDUN-5-UNSUPPORTED_MSG |
5-Notice |
Msgtype [chars] sent by [chars] unsupported by peer. |
Peer responded that it didn't recognize a message sent by this CPU possibly due to a different image version. |
- |
"May require a software upgrade on the Standby CPU. " LOG_STD_ACTION |
|
CPU_REDUN-6-BOOTED_AS_ACTIVE |
6-Information |
After returning to ROM by [chars] |
Informational message notifying about a system startup with no switchover. |
- |
LOG_STD_NO_ACTION |
|
CPU_REDUN-6-EHSA_SVCS_EVENT |
6-Information |
[chars] [chars] |
A significant EHSA Redundancy services event occurred. The details will be printed. |
- |
LOG_STD_NO_ACTION |
|
CPU_REDUN-6-RUNNING_CONFIG_CHG |
6-Information |
Running config on this CPU has possibly changed |
Informational message to notify of possible changes to the running-config file |
- |
LOG_STD_NO_ACTION |
|
CPU_REDUN-6-STARTUP_CONFIG_CHG |
6-Information |
Startup config on this CPU has possibly changed |
Informational message to notify of possible changes to the startup-config file |
- |
LOG_STD_NO_ACTION |
|
CR10K_CLNT-3-CR10K_ASSERT_FAILED |
3-Error |
Assert failed at line [dec] from func [chars] in file [chars] |
Detect assert failure in global level |
cmts-platform |
"Copy the error and send it to TAC.""TAC team can contact cable team to check why this error occurs" |
|
CR10K_CLNT-3-CR10K_CLNT_ASSERT_FAILED |
3-Error |
Assert failed at line [dec] from func [chars] in file [chars] for client [dec] |
Detect assert failure in client level |
cmts-platform |
"Copy the error and send it to TAC.""TAC team can contact cable team to check why this error occurs" |
|
CR10K_CLNT-3-IPCTXERR |
3-Error |
IPC send failure: client=[dec] entity=[dec] ses=[dec]/[dec] msg=[dec] err=[chars] |
IPC send failure. |
cmts-platform |
LOG_STD_ACTION |
|
CR10K_CLNT-3-MTU_UNAVAILABLE |
3-Error |
cr10k client ses is down err:[dec] |
Application code is trying to get negotiated mtu before issu negotiation is finished. err:1 means issu nego has not finished. err:2 means issu nego has not started.The traceback decode usually can pinpoint which routine is trying toget mtu too early. In most cases it is a msg send routine that triesto get the msg mtu in order to allocate a right size msg buffer. If the msg is not critical or will be resent upon send failure then the fix is to call cr10k_clnt_get_ses_up_for_apps before get mtu |
cmts-platform |
"Copy the error and send it to TAC.""TAC team can contact cable team to check why this error occurs" |
|
CR10K_CLNT-3-TIMEOUT |
3-Error |
Timeout waiting for [chars] slot [dec]/[dec] |
Timeout while waiting on the specified event. |
cmts-platform |
"Copy the error and send it to TAC.""TAC team can contact cable team to check why this error occurs" |
|
CR10K_DIAG-3-LLQDROP |
3-Error |
LLQ Drops on [chars] new_drops:[dec] total_drops:[dec] |
The health monitoring code has detected drops on the low latency queue of the specified interface. This is not expected behavior. The interface should be monitored to determine if drops continue to increase. |
platform-cmts |
LOG_STD_ACTION |
|
CR10K_DIAG-3-MEMLEAK |
3-Error |
MemLeak Monitor: [chars] [chars] |
The health monitoring code has detected potential memory leaks by the local IOS sub-system. This is not an expected behavior. The sub-system should be monitored to detect if real memory leaks continue to happen. |
platform-cmts |
LOG_STD_ACTION |
|
CR10K_DIAG-5- DIAG_LOOP_ETSEC |
5-Notice |
eTSEC loopback failure [chars] |
A loopback between eTSEC1 and eTSEC2 failed. |
ubr10k-sw |
"Monitor failed LC for excessive failures." |
|
CR10K_DIAG-5- DIAG_LOOP_MG |
5-Notice |
US PHY [dec] loopback failure [chars] [dec] |
Failed to loopback frame from CPU -> PHY -> JIB3 US -> CPU |
ubr10k-sw |
"Monitor failed LC for excessive failures." |
|
CR10K_DIAG-5- DIAG_LOOP_RXERR |
5-Notice |
US PHY [dec] loopback discrepency detected frames tx [dec] rx [dec] err [hec] |
Failed to loopback one or more frames |
ubr10k-sw |
"Monitor failed LC for excessive failures." |
|
CR10K_DIAG-5- DIAG_LOOP_SEQ |
5-Notice |
US PHY [dec] loopback failed unexpected seq [dec] exp [dec] |
Failed to loopback one or more frames |
ubr10k-sw |
"Monitor failed LC for excessive failures." |
|
CR10K_DIAG-5-PXFOVERSUB |
5-Notice |
PXF utilization is [dec]%% system is close to be overloaded. |
The health monitoring code has detected the system is close to be oversubscribed. |
platform-cmts |
LOG_STD_ACTION |
|
CR10K_DIAG-5-RU_OLDBUFF_HOLD |
5-Notice |
IO-Buff-Hoard Monitor: [chars] |
The health monitoring code has detected potential memory leaks by the local IOS sub-system. This is not an expected behavior. The sub-system should be monitored to detect if real memory leaks continue to happen. |
platform-cmts |
LOG_STD_ACTION |
|
CR10KBH-1-INITFAIL |
1-Alert |
[chars] initialization failure |
Backhaul Ethernet hardware initialization failed |
ubr10k-sw |
LOG_STD_ACTION |
|
CR10KBH-3-B2B_LINKDOWN |
3-Error |
[chars] B2B port [dec] changed state to down |
Link state changed to down for B2B interface |
ubr10k-sw |
"Check the sfp+ and wire status for B2B interface" |
|
CR10KBH-3-B2B_SFPP_MISSING |
3-Error |
[chars] B2B port [dec] SFP+ missing |
TenGigabit Ethernet SFP+ was removed from the B2B interface |
ubr10k-sw |
"Insert a TenGigabit ethernet SFP+ into the B2B interface" |
|
CR10KBH-3-INVALID_DATA_INSTANCE |
3-Error |
interface type [chars] slot [dec] subunit [dec] vc [dec] : [chars] |
Data required to support the interface is not available. |
ubr10k-sw |
LOG_STD_SH_TECH_ACTION |
|
CR10KBH-3-MAXADDR |
3-Error |
[chars] total addresses greater than [chars] |
The number of addresses in the address filter is too large |
ubr10k-sw |
LOG_STD_ACTION |
|
CR10KBH-3-RADIAN_VLANTCAM_EXCEEDED |
3-Error |
[chars] vlanid [dec] Radian VLAN TCAM table full |
Radian has a maximum of 4K vlan tcam entries |
ubr10k-sw |
LOG_STD_SH_TECH_ACTION |
|
CR10KBH-3-SFPP_BAD_HW |
3-Error |
Interface [chars] TenGigabit Ethernet module SFP+ has bad HW |
TenGigabit Ethernet SFP+ could not be read CRC error or tx fault |
ubr10k-sw |
"Insert a new TenGigabit Ethernet SFP+ into the Backhaul interface" |
|
CR10KBH-3-SFPP_MISSING |
3-Error |
Interface [chars] TenGigabit ethernet module SFP+ missing |
TenGigabit Ethernet SFP+ was removed from the Backhaul interface |
ubr10k-sw |
"Insert a TenGigabit ethernet SFP+ into the Backhaul interface" |
|
CR10KBH-3-SFPP_NON_TENGIGE |
3-Error |
Interface [chars] Inserted module not TenGigabit ethernet module SFP+ |
Non TenGigabit Ethernet SFP+ was inserted into the Backhaul interface |
ubr10k-sw |
"Insert a TenGigabit ethernet SFP+ into the Backhaul interface" |
|
CR10KBH-3-SFPP_SECURITY_FAIL |
3-Error |
Interface [chars] TenGigabit Ethernet module SFP+ is not CISCO approved |
TenGigabit Ethernet SFP+ has failed cisco-EEPROM security check |
ubr10k-sw |
"Insert a approved vendor SFP+ into the Backhaul interface" |
|
CR10KBH-3-SFPP_SPURIOUS |
3-Error |
Interface [chars] TenGigabit Ethernet module SFP+ is a duplicate spurious |
TenGigabit Ethernet SFP+ has a vendor & serial number duplicate of another |
ubr10k-sw |
"Insert a approved vendor SFP+ into the Backhaul interface" |
|
CR10KBH-3-WIRING_ERR |
3-Error |
Wrong wiring detected at [chars] interconnect portportnum: [dec] please |
This error message will be printed out when local interconnect port link status mismatches with remote interconnect port link status. We should use cable fiber to connect the corresponding interconnect ports between active and standby. When the error msg is printed out please check: 1 if |
ubr10k-sw |
LOG_STD_SH_TECH_ACTION |
|
CR10KBH-6-B2B_LINKUP |
6-Information |
[chars] B2B port [dec] changed state to up |
Link state changed to up for B2B interface |
ubr10k-sw |
LOG_STD_NO_ACTION |
|
CR10KBH-6-B2B_SFPP_OK |
6-Information |
[chars] B2B port [dec] SFP+ inserted |
TenGigabit Ethernet SFP+ was inserted into the B2B interface |
ubr10k-sw |
LOG_STD_NO_ACTION |
|
CR10KBH-6-RADIAN_MACACCT_FULL |
6-Information |
MAC accounting entries full for Radian in slot [chars] |
Radian has a maximum of 256 ingress and 256 egress MAC accounting entries |
ubr10k-sw |
LOG_STD_SH_TECH_ACTION |
|
CR10KBH-6-SFPP_OK |
6-Information |
Interface [chars] 10GBASE-[chars] TenGigabit ethernet module SFP+ inserted |
TenGigabit Ethernet SFP+ was inserted into the Backhaul interface |
ubr10k-sw |
LOG_STD_NO_ACTION |
|
CRASH_DUMP-3-FILE_OP |
3-Error |
FILE operation [chars] failed CRASH DUMP May not be successfull |
The File operation for dumping DSP crash details failed The error message could be a software issue or due to not enough disk space. |
- |
LOG_STD_NO_ACTION |
|
CRASH_DUMP-6-ABORT |
6-Information |
CRASH DUMP aborted for device [dec] |
Crash dump aborted. Crash Dump may not be successfull |
- |
LOG_STD_NO_ACTION |
|
CRASH_DUMP-6-TIMEOUT |
6-Information |
CRASH DUMP may not be successfull for the device [dec] |
Crash dump process timed out waiting for diaganostic messages |
- |
LOG_STD_NO_ACTION |
|
CRB_EVENT-3-CRB_RT_ERROR |
3-Error |
CRB Runtime Exception: [chars] |
CRB Runtime Exception |
- |
LOG_STD_ACTION |
|
CRB_EVENT-3-CRB_RT_ERROR |
3-Error |
CRB Runtime Exception: [chars] |
CRB Runtime Exception |
- |
LOG_STD_ACTION |
|
CRIMSON-3-DATABASE_MEMLEAK |
3-Error |
Database memory leak detected in [chars] database [chars]/[chars]/[chars] size: %llu byte callsite: %016llX |
A memory leak has been detected in the database memory. The leaked object is identified by name |
crimson |
LOG_STD_ACTION |
|
CRIMSON-3-INITFAIL |
3-Error |
Initialization of the IOS operational database facility failed [chars]. |
- |
- |
- |
|
CRIMSON-3-INITFAIL_OPER_FLUSH |
3-Error |
Initialization of the IOS operational database flush facility failed. |
An unexpected condition has occurred which resulted in the IOS operational database flush facililty failing to start. External agents will not be able to access the contents of the IOS operational database. |
crimson |
LOG_STD_ACTION |
|
CRIMSON-3-INITFAIL_OPER_REDO |
3-Error |
Initialization of the IOS operational database redo facility failed. |
An unexpected condition has occurred which resulted in the IOS operational database redo facililty failing to start. This is a serious problem and means that the IOS operation database facility will not be functional. |
crimson |
LOG_STD_ACTION |
|
CRIMSON-3-IOS_CONFIG_DB_GARBAGE_COLLECTION_START_FAIL |
3-Error |
Unable to start the garbage collection process for the IOS config database |
The IOS configuration database garbage collection has failed to start. Without a garbage collection process stale objects will not be cleaned up. |
crimson |
LOG_STD_ACTION |
|
CRIMSON-3-IOS_CONFIG_DB_VALIDATION_FAIL |
3-Error |
Data validation of the IOS configuration database failed [chars]. |
- |
- |
- |
|
CRIMSON-3-NESTED_LOCK |
3-Error |
Database already locked by [chars]. |
An unexpected condition has occurred wherein the already locked IOS operational database was requested to be locked again. This problem means that external entities may not receive updates when operational data changes. |
crimson |
LOG_STD_ACTION |
|
CRIMSON-3-NGIOS_CONFIG_DB_GARBAGE_COLLECTION_START_FAIL |
3-Error |
Unable to start the garbage collection process for the NGIOS config database |
The NGIOS configuration database garbage collection has failed to start. Without a garbage collection process stale objects will not be cleaned up. |
crimson |
LOG_STD_ACTION |
|
CRIMSON-3-UPDATE_FAIL |
3-Error |
Processing of a IOS operational database update failed [chars]. |
- |
- |
- |
|
CRPGC-0-REFERENCE_STUBBED |
0-Emergency |
stubbed [chars] is referenced |
- |
- |
"" |
|
CRYPTO_DEV_PROXY-2-PROXY_IPC_INIT_FAILED |
2-Critical |
QFP Crypto device Proxy IPC interface initialization failure result: [dec]. |
Cisco internal software error. QFP Crypto device Proxy initialization detected that the IPC interface initialization failed. QFP Crypto device proxy will not be functional while this condition exists. |
qfp-ipsec keyword:none |
LOG_STD_ACTION |
|
CRYPTO_DEV_PROXY-2-PROXY_REG_NULL_MSG_HNDLR |
2-Critical |
QFP Crypto device Proxy registered invalid message handlers source: [chars]. |
Cisco internal software error. QFP Crypto device Proxy registered with invalid message handler. QFP Crypto device Proxy will not be functional while this condition exists. |
qfp-ipsec keyword:none |
LOG_STD_ACTION |
|
CRYPTO_DEV_PROXY-3-PROXY_BAD_MSG |
3-Error |
QFP Crypto device Proxy received bad length message type [dec] |
Cisco internal software error. QFP Crypto device Proxy received a corrupted message from control plane. This message will be ignored. |
qfp-ipsec keyword:none |
LOG_STD_ACTION |
|
CRYPTO_DEV_PROXY-3-PROXY_INV_MSG |
3-Error |
QFP Crypto device Proxy received invalid message type [dec] |
Cisco internal software error. QFP Crypto device Proxy received an invalid message from control plane. This message will be ignored. |
qfp-ipsec keyword:none |
LOG_STD_ACTION |
|
CRYPTO_DEV_PROXY-3-PROXY_IPC_ALLOC_FAILED |
3-Error |
QFP Crypto device Proxy [chars] message lost due to message buffer allocation failure. |
Cisco internal software error. QFP Crypto device Proxy message processing detected a message buffer allocation failure. The message is lost as the result of this condition. |
qfp-ipsec keyword:none |
LOG_STD_ACTION |
|
CRYPTO_DEV_PROXY-3-PROXY_IPC_SEND_FAILED |
3-Error |
QFP Crypto device Proxy [chars] message lost due to message sent failure result: [dec]. |
Cisco internal software error. QFP Crypto device Proxy message processing detected a message sent failure. The message is lost as the result of this condition. |
qfp-ipsec keyword:none |
LOG_STD_ACTION |
|
CRYPTO_ENGINE-0-AUDITFAIL |
0-Emergency |
Encryption audit check found the wrong level of encryption in this image |
The audit check verifying encryption entitlement within the IOS image either found encryption in a non-encryption image or the wrong strength within an IOS image containing encryption. Use of the encryption may violate U.S. Export Laws and Regulations. |
- |
"Contact Cisco to obtain a replacement IOS image." |
|
CRYPTO_ENGINE-3-CSDL_COMPLIANCE_FAIL |
3-Error |
Cisco PSB security compliance violation is detected. Use of [chars] by [chars] is denied |
A security compliance violation has been detected. An attempt to use cryptography [chars] that is restricted |
- |
"Use Cisco PSB approved cryptographic methods" "or remove the compliance profile that is active at your own risk" |
|
CRYPTO_ENGINE-3-CSDL_COMPLIANCE_FAIL_RSA |
3-Error |
Cisco PSB security compliance violation is detected. Use of weak [dec] bit key is denied |
A security compliance violation has been detected. An attempt to use RSA cryptography with weak keys that is restricted by Cisco Internal Requirements and defined by the Cisco Product Security Baseline PSB has been denied. |
- |
"Use Cisco PSB approved cryptographic methods" "or remove the compliance profile that is active at your own risk" |
|
CRYPTO_ENGINE-3-FIPS_COMPLIANCE_FAIL |
3-Error |
FIPS security compliance violation is detected. Use of [chars] by [chars] is denied |
A FIPS security compliance violation has been detected. The cryptography used is considered weak and violates the requiremnet set by FIPS |
- |
"Use FIPS approved cryptographic methods" "or disable FIPS mode and reload device" |
|
CRYPTO_ENGINE-4-AUDITWARN |
4-Warning |
Encryption audit check could not be performed |
The audit check verifying encryption entitlement within the IOS image could not be performed due to incompete system configuration. |
- |
"Manually verify that this IOS image is entitled to contain " "encryption." |
|
CRYPTO_ENGINE-4-CSDL_COMPLIANCE_DISABLED |
4-Warning |
Cisco PSB security compliance has been disabled |
Cisco Internal Requirements and defined by the Cisco Product Security Baseline PSB has been disabled. |
- |
"Proceed with caution since weak cryptography will be allowed" |
|
CRYPTO_ENGINE-4-CSDL_COMPLIANCE_RSA_WEAK_KEYS |
4-Warning |
RSA keypair [chars] is in violation of Cisco security compliance guidelines and will be rejected by future releases. |
An attempt to use RSA cryptography with weak keys has been detected. Cisco recommends RSA key sizes of 2048 or greater for security. Shorter key sizes will be rejected in future releases. |
- |
"Regenerate keys specifying key size to be 2048 or greater" " to avoid future service disruption" |
|
CRYPTO_ENGINE-5-CSDL_COMPLIANCE_ENFORCED |
5-Notice |
Cisco PSB security compliance is being enforced |
Cisco Internal Requirements and defined by the Cisco Product Security Baseline PSB are being enforced. |
- |
"No action is required" |
|
CRYPTO_ENGINE-5-CSDL_COMPLIANCE_EXCEPTION_ADDED |
5-Notice |
Cisco PSB security compliance exception has been added by [chars] for use of [chars] |
Cisco Internal Requirements and defined by the Cisco Product Security Baseline PSB are being enforced. |
- |
"No action is required" |
|
CRYPTO_ENGINE-5-KEY_ADDITION |
5-Notice |
A key named [chars] has been generated or imported by [chars] |
An RSA or EC key has been generated or imported. The configuration must be saved to permanently save this key. |
- |
"No action required. Informational message" |
|
CRYPTO_ENGINE-5-KEY_DELETED |
5-Notice |
A key named [chars] has been removed from key storage |
A key has been marked for removal from storage. The configuration must be saved to permanently remove this key. |
- |
"No action required. Informational message" |
|
CRYPTO_ENGINE-5-KEY_REPLACE |
5-Notice |
A key named [chars] has been replaced by [chars] with new key data |
An RSA or EC key has been replaced. The configuration must be saved to permanently save this key. |
- |
"No action required. Informational message" |
|
CRYPTO_HA_IKE-3-FAILOVER_ERROR |
3-Error |
Attempt to failover IKE SA [inet]:[inet] failed due to [chars]. No |
The HA Active device attempted to checkpoint the state of an IKE SA to the Standby but the Standby device was unable to create the Standby IKE SA. |
ipsec-ha |
"Look for other error messages at log level WARNING or turn on debugs " "to look for the specific reason of the failure." |
|
CRYPTO_HA_IKE-4-CRYPTO_HA_NOT_SUPPORTED_BY_HW |
4-Warning |
Crypto hardware is enabled and it does not support HA operation '[chars]' |
Crypto Hardware is enabled but the hardware does not support HA operations like insert/extract of keys |
- |
"Replace Cryto hardware with one that support HA operations" " or disable the hardware to use software crypto engine" |
|
CRYPTO_HA_IPSEC-3-FAILOVER_ERROR |
3-Error |
Attempt to failover IPSec SA [inet]:[inet] failed due to [chars]. No |
The HA Active device attempted to checkpoint the state of an IKE SA to the Standby but the Standby device was unable to create the Standby IKE SA. |
ipsec-ha |
"Look for other error messages at log level WARNING or turn on debugs " "to look for the specific reason of the failure." |
|
CRYPTO_HA_IPSEC-3-HA_IPSEC_UPDATE_PROC_FAIL |
3-Error |
Start of HA IPSec update process failed |
Starting of the IPSec HA process failed Updates will not be sent from active to standby |
ipsec-ha |
"The box may need to be re-booted if this is a part " "of a IPSec HA setup" |
|
CRYPTO_HA_IPSEC-4-CRYPTO_HA_NOT_SUPPORTED_BY_HW |
4-Warning |
Crypto hardware is enabled and it does not support HA operation '[chars]' |
Crypto Hardware is enabled but the hardware does not support HA operations like insert/extract of keys |
- |
"Replace Cryto hardware with one that support HA operations" " or disable the hardware to use software crypto engine" |
|
CRYPTO_RSA_ISSU-3-GET_BUFFER |
3-Error |
Crypto RSA ISSU client failed to get buffer for message.\n\ Error: [dec] [chars] |
Crypto RSA ISSU client failed to get buffer for building\n\ a negotiation message. Hence it cannot send the negotiation\n\ message to the standby unit. When there is a problem in\n\ the negotiaiton the standby unit can not be brought up. |
crypto_rsa |
"show logging and show checkpoint client" |
|
CRYPTO_RSA_ISSU-3-INIT |
3-Error |
Crypto RSA ISSU client initialization failed to [chars]. Error: [dec] [chars] |
Crypto RSA ISSU client could not be initiailzed this will\n\ cause catstrophic failure when ISSU upgrade or downgrade\n\ is performed. |
crypto_rsa |
LOG_STD_SH_TECH_ACTION |
|
CRYPTO_RSA_ISSU-3-INVALID_SESSION |
3-Error |
Crypto RSA ISSU client does not have a valid registered session. |
Crypto RSA ISSU client does not have a valid registered session.\n\ When there is a problem with the session the standby unit cannot\n\ be brought up. |
crypto_rsa |
"show issu capability entries <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated capability <session_id>" |
|
CRYPTO_RSA_ISSU-3-MSG_NOT_OK |
3-Error |
Crypto RSA ISSU client message type [dec] is not compatible |
Crypto RSA ISSU client received an incompatible message\n\ from the peer unit. Since the message is not compatible\n\ it cannot be processed by this unit |
crypto_rsa |
"show issu message group <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
CRYPTO_RSA_ISSU-3-MSG_SIZE |
3-Error |
Crypto RSA ISSU client failed to get the MTU for message type [dec].\n\ Error: [dec] [chars] |
Crypto RSA ISSU client failed to calculate MTU\n\ for the message specified. The dot1x ISSU client will not\n\ be able to send message to the standby unit. |
crypto_rsa |
"show issu message group <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
CRYPTO_RSA_ISSU-3-SEND_NEGO_FAILED |
3-Error |
Crypto RSA ISSU client failed to send negotiation message.\n\ Error: [dec] [chars] |
Crypto RSA ISSU client failed to send a session negotiation\n\ message to the peer. When there is a problem in the ISSU\n\ negotiation the standby unit can not be brought up. |
crypto_rsa |
"show logging and show checkpoint client" |
|
CRYPTO_RSA_ISSU-3-SESSION_NEGO |
3-Error |
Crypto RSA ISSU client encountered unexpected client nego_done.\n\ Error: [dec] [chars] |
Crypto RSA ISSU client encountered an unexpected 'client\n\ negotiation done'. |
crypto_rsa |
"show issu session <client_id> and\n\ show issu negotiated capability <session_id>" |
|
CRYPTO_RSA_ISSU-3-SESSION_REGISTRY |
3-Error |
Crypto RSA ISSU client failed to register session information.\n\ Error: [dec] [chars] |
Crypto RSA ISSU client failed to register session information.\n\ When there is a problem with the session the standby unit cannot\n\ be brought up. |
crypto_rsa |
"show issu capability entries <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated capability <session_id>" |
|
CRYPTO_RSA_ISSU-3-SESSION_UNREGISTRY |
3-Error |
Crypto RSA ISSU client failed to unregister session information.\n\ Error: [dec] [chars] |
Crypto RSA ISSU client failed to unregister session information. |
crypto_rsa |
"show issu session <client_id> and\n\ show issu negotiated capability <session_id>" |
|
CRYPTO_RSA_ISSU-3-TRANSFORM_FAIL |
3-Error |
Crypto RSA ISSU client [chars] transform failed for message type [dec].\n\ Error: [dec] [chars] |
Crypto RSA ISSU client could not transform the message.\n\ If the transmit transformation failed it means that the\n\ checkpoint message can not be sent to the standby unit.\n\ If the receive transformation failed it means that the\n\ checkpoint message can not be applied on the standby\n\ unit. In both cases the Crypto RSA state will not\n\ be indentical with the active unit. |
crypto_rsa |
"show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
CRYPTO_SL_TP_LEVELS-3-INV_DEFAULT_VALUE |
3-Error |
Invalid platform default value token: [chars] |
- |
- |
LOG_STD_ACTION |
|
CRYPTO_SL_TP_LEVELS-3-INV_PLATFORM_VALUE |
3-Error |
Invalid platform level value token: [chars] |
- |
- |
LOG_STD_ACTION |
|
CRYPTO_SL_TP_LEVELS-3-NO_VALID_PLATFORM_VALUES |
3-Error |
No valid platform level values specified |
- |
- |
LOG_STD_ACTION |
|
CRYPTO_SL_TP_LEVELS-3-ROMMON_WRITE_FAILED |
3-Error |
Error in updating rommon variable |
- |
- |
LOG_STD_ACTION |
|
CRYPTO_SL_TP_LEVELS-3-VAR_SET_FAILED |
3-Error |
Update of rommon variable failed: retcode=[dec] |
Call to update rommon variable failed |
- |
LOG_STD_ACTION |
|
CRYPTO_SL_TP_LEVELS-6-INV_ROMMON_VALUE |
6-Information |
Invalid throughput option [dec] kbps foundupdating rommon to [dec] kbps |
Invalid throughput option in rommon for crypto throughputResetting the throughput option to the default value |
- |
"No action required. Informational message." |
|
CRYPTO_SL_TP_LEVELS-6-ROMMON_VAL |
6-Information |
Current rommon value: [chars] |
- |
- |
- |
|
CRYPTO_SL_TP_LEVELS-6-TIER_BASED_LIC |
6-Information |
Tier Based License Support: [dec] |
- |
- |
- |
|
CRYPTO_SL_TP_LEVELS-6-TP_LEVEL_BLOCKED |
6-Information |
Network Essentials is enabled higher throughput blocked |
- |
- |
- |
|
CRYPTO_SL_TP_LEVELS-6-TP_LEVEL_LIMITED |
6-Information |
HSECK9 is disabled: bandwidth restricted to 250Mbps |
- |
- |
- |
|
CRYPTO_SL_TP_LEVELS-6-TP_LICENSE_HSEC_REGISTER_FAILED |
6-Information |
License registration failed rc=[dec] |
License request failed. |
- |
"Look at other logs/debugs to see reason for failure." |
|
CRYPTO_SL_TP_LEVELS-6-TP_LICENSE_HSEC_REQUEST_FAILED |
6-Information |
License request failed rc=[dec] |
HSECK9 License request failed. |
- |
"Look at other logs/debugs to see reason for failure." |
|
CRYPTO_SL_TP_LEVELS-6-TP_LICENSE_TP_REQUEST_FAILED |
6-Information |
License request failed rc=[dec] sle_ret_val=[dec] |
License request failed. Data plane will use platform default throughput level |
- |
"Look at other logs/debugs to see reason for failure." |
|
CRYPTO_SL_TP_LEVELS-6-TP_THROTTLE_STATE |
6-Information |
Crypto throughput [chars] throttled. New level is [dec] |
Maximum throughput level is the same as unthrottled. All other levels are throttled |
- |
"No action required. Informational message." |
|
CRYPTO_SL_TP_LEVELS-6-VAR_NEW_STR |
6-Information |
Setting crypto bidir throughput to: [chars] |
Crypto throughput rommon var updated |
- |
"No action required. Informational message." |
|
CRYPTO_SL_TP_LEVELS-6-VAR_NEW_VALUE |
6-Information |
Setting crypto bidir throughput to: [dec] kbps |
Crypto throughput rommon var updated |
- |
"No action required. Informational message." |
|
CRYPTO-0-AUDITFAIL |
0-Emergency |
Encryption audit check found the wrong level of encryption in this image |
The device is starting the Crypto algorithms self-tests.\n\ Success or failure status will be reported when the tests complete. |
- |
"Informational only. No action required." |
|
CRYPTO-0-SELF_TEST_FAILURE |
0-Emergency |
Crypto algorithms self-test failed [chars] |
One of the crypto algorithm self-tests has failed. The crypto algorithm engine is not operable in this state. |
- |
"If the failure persists contact Cisco to " "obtain a replacement IOS image." |
|
CRYPTO-3-BADMAGIC |
3-Error |
Bad [chars] magic number %04x. |
An internal software error. |
ipsec |
LOG_STD_ACTION |
|
CRYPTO-3-ECDSA_SELFTEST_FAILED |
3-Error |
Generated ECDSA key failed self test |
An automatic test of the newly generated ECDSA keypair [chars] failed. That ECDSA key was automatically deleted. |
- |
"File a DDTS. As an immediate workaround attempt to create another pair" |
|
CRYPTO-3-ENGINE_BAD_ID |
3-Error |
Crypto Engine id [dec] is invalid |
The packet has its engine_id set to something other than software crypto or hardware crypto. Unable to determine which crypto engine to use The packet will be default sent to software crypto engine. |
ipsec |
"No action required" |
|
CRYPTO-3-EZVPN_VINTERFACE_CREATE_ERR |
3-Error |
EZVPN[chars]: Virtual-access interface creation failed |
The virtual-interface feature will not work without a virtual-access interface. The EzVPN configuration is unusable. You can choose to remove virtual-interface configuration from ezvpn as a workaround |
ipsec-ezvpn |
"If this message occurs contact your technical " "support representative." |
|
CRYPTO-3-GM_FAILCLOSE_UNSUPPORTED |
3-Error |
GETVPN failclose is not supported by the current available crypto hardware. |
An attempt was made to configure the GETVPN failclose feature which cannot be supported by the current encryption hardware. |
ipsec-mcast |
"Please remove the unsupported feature config " "or switch to a capable crypto engine." |
|
CRYPTO-3-IKE_PAK_IN_Q_TIME_LIMIT_EXCEED |
3-Error |
Pak spent too much time in the IKE input queues |
An incoming IKE packet spent too much time in the IKE input\n\ queues. This can happen when the IKE subsystem is under heavy\n\ load due to a lot of peers trying to setup SAs simultaneously\n\ and IKE is not able to handle all the incoming packets in a\n\ timely manner. |
- |
"It is important to understand why many peers are simultaneously\n\ trying to setup SAs at the same time. If possible try to avoid\n\ or minimize such network conditions." |
|
CRYPTO-3-IKEINIT |
3-Error |
[chars] |
An IKE initialization error |
ipsec |
LOG_STD_ACTION |
|
CRYPTO-3-IKMP_PEER_INIT_FAILURE |
3-Error |
IKE failed to create IKE peer tree or leaf node. |
IKE failed to allocate memory for the IKE peer tree |
- |
"More DRAM may be required in order to run the image." |
|
CRYPTO-3-IKMP_QUERY_KEY |
3-Error |
Querying key pair failed. |
Querying public key/private key using subject name failed |
- |
"Check the subject name in the certificate." |
|
CRYPTO-3-INVALID_KMI_REQUEST |
3-Error |
Invalid KMI error: kmi_client: [dec] in processing [chars] |
IPSec detected an invalid KMI |
ipsec-core |
"None" |
|
CRYPTO-3-IPSEC_PAL_FATAL_ERROR |
3-Error |
IPsec PAL Fatal Error: [chars] |
IPSec SM detected inconsistence and hence crashing the system |
ipsec-core |
"None" |
|
CRYPTO-3-IPSECV6_UNSUPPORTED |
3-Error |
IPv6 IPsec is not supported by the current available crypto hardware. |
An attempt was made to configure a feature which will use IPv6 IPsec. IPv6 IPsec cannot be supported by the current encryption hardware. The configuration change was made but will not be functional until the encryption hardware configuration is changed. |
ipsec |
"Please remove the unsupported feature config " "or switch to a capable crypto engine." |
|
CRYPTO-3-MTREE_CMD_BLOCK |
3-Error |
Mtree command [dec] was blocked from the the mtree process queue. |
An attempt was made to enqueue a command to the crypto mtree manager process even though IPsec is currently operating in HAPX mode. |
ipsec |
LOG_STD_ACTION |
|
CRYPTO-3-NOSOCKET |
3-Error |
Unable to open [chars] |
Call Admission Control is configured globally or at the IKE level on this device. Consequently an IKE SA request was denied do to the reason described in the error message. |
ipsec |
"Decrease the number of concurrent connections or " "inspect the crypto engine." |
|
CRYPTO-3-PAL_INTERNAL_ERROR |
3-Error |
Internal error: [chars] |
IPSec detected a serious internal error |
ipsec-core |
"None" |
|
CRYPTO-3-PAL_INTERNAL_ERROR_ALREADY_ALWAYS |
3-Error |
Internal error: Cannot do transition for state [chars]: ALWAYS state already defined |
IPSec detected a serious internal error |
ipsec-core |
"None" |
|
CRYPTO-3-PAL_INTERNAL_ERROR_BAD_MESSAGE |
3-Error |
Internal error: unrecognized message [dec] |
IPSec detected a serious internal error |
ipsec-core |
"None" |
|
CRYPTO-3-PAL_INTERNAL_ERROR_BAD_TRANSITION |
3-Error |
Internal error: state [chars] has unrecognized transition [dec] |
IPSec detected a serious internal error |
ipsec-core |
"None" |
|
CRYPTO-3-PAL_INTERNAL_ERROR_CANNOT_ALWAYS |
3-Error |
Internal error: Cannot do ALWAYS transition for state [chars]: transition already defined |
IPSec detected a serious internal error |
ipsec-core |
"None" |
|
CRYPTO-3-PAL_INTERNAL_ERROR_LOOP |
3-Error |
Internal error: [[chars]]: state loop detected: state = [chars] |
IPSec detected a serious internal error |
ipsec-core |
"None" |
|
CRYPTO-3-PAL_INTERNAL_ERROR_NO_NEXT_STATE |
3-Error |
Internal error: undefined next state [dec]: previous state = [chars] |
IPSec detected a serious internal error |
ipsec-core |
"None" |
|
CRYPTO-3-PAL_INTERNAL_ERROR_REQUEST_STATE |
3-Error |
Internal error: illegal request state [dec] |
IPSec detected a serious internal error |
ipsec-core |
"None" |
|
CRYPTO-3-PAL_INTERNAL_ERROR_STATE_ALREADY_DEFINED |
3-Error |
Internal error: State [dec] already defined: old_state = [chars] new_state = [chars] |
IPSec detected a serious internal error |
ipsec-core |
"None" |
|
CRYPTO-3-PAL_INTERNAL_ERROR_STATE_OVERFLOW |
3-Error |
Internal error: Table overflow new_state = [dec] [chars] |
IPSec detected a serious internal error |
ipsec-core |
"None" |
|
CRYPTO-3-PAL_INTERNAL_ERROR_TRANSITION_ALREADY |
3-Error |
Internal error: Transition [dec] already defined: state = [chars] |
IPSec detected a serious internal error |
ipsec-core |
"None" |
|
CRYPTO-3-PAL_INTERNAL_ERROR_TRANSITION_OVERFLOW |
3-Error |
Internal error: Transition table overflow transition = [dec] state = [chars] |
IPSec detected a serious internal error |
ipsec-core |
"None" |
|
CRYPTO-3-PAL_REQUEST_OUTSIDE_ACTION |
3-Error |
Internal error: [chars] called from outside action routine |
IPSec detected a serious internal error |
ipsec-core |
"None" |
|
CRYPTO-3-PAL_REQUEST_PENDING_ACTION |
3-Error |
Internal error: state [chars] has pending actions |
IPSec detected a serious internal error |
ipsec-core |
"None" |
|
CRYPTO-3-POLICY_CKSUM_ERROR |
3-Error |
Crypto policy checksum failure.\n \tCrypto access list [chars] crypto map [chars] interface [chars]\n |
Crypto policy checksum failure has been detected in this router whose traffic is protected by the crypto policy. This event may be caused by memory corruption occuring in crypto policy data or the memory area has been illegally modified. It may also be caused by software defects. As a result of this event the router has been forced to reload. |
- |
"Contact your Cisco support representatives." |
|
CRYPTO-3-RSA_SELFTEST_FAILED |
3-Error |
Generated RSA key failed self test |
An automatic test of the newly generated RSA keypair [chars] failed. That RSA key was automatically deleted. |
- |
"File a DDTS. As an immediate workaround attempt to create another pair" |
|
CRYPTO-3-TOKENADMINLOCKEDOUT |
3-Error |
Cryptographic Token [chars] Administrator PIN Locked due to too many unsuccessful login attempts |
The cryptographic token has disabled the Admin PIN due to too many login failures |
pki |
"If the user PIN is also locked out it will be necessary to reinitialize the card." "The data on the card will be lost" |
|
CRYPTO-3-TOKENADMINLOGINFAILED |
3-Error |
Cryptographic Token [chars] ADMIN Login FAILED |
The cryptographic token has rejected the administrator PIN offered by the router |
pki |
"Issue 'crypto pki token admin-pin' command to enter correct PIN" |
|
CRYPTO-3-TOKENAPIFAILURE |
3-Error |
Cryptographic Token [chars] API FAILED error = [dec] |
The cryptographic token returned an unexpected error |
pki |
LOG_STD_ACTION |
|
CRYPTO-3-TOKENCHANGEPINFAILED |
3-Error |
Cryptographic Token [chars] Change PIN FAILED |
The cryptographic token has rejected the new PIN offered by the router |
pki |
"Be sure you are logged in to the token as admin. Try a longer PIN." |
|
CRYPTO-3-TOKENLOCKEDOUT |
3-Error |
Cryptographic Token [chars] PIN Locked due to too many unsuccessful login attempts |
The cryptographic token has disabled the user PIN due to too many login failures |
pki |
"Issue 'crypto pki token admin-pin' command to enter correct ADMINISTRATOR PIN" |
|
CRYPTO-3-TOKENLOGINFAILED |
3-Error |
Cryptographic Token [chars] Login FAILED |
The cryptographic token has rejected the PIN offered by the router |
pki |
"Issue 'crypto pki token user-pin' command to enter correct PIN" |
|
CRYPTO-3-TOKENSTOREKEYFAILED |
3-Error |
Key [chars] store on Cryptographic Token [chars] Failed |
An error occurred attempting to write a new keypair out to the cryptographic token |
pki |
"Try logging in to the token. If the error persists " "try logging in as admin" |
|
CRYPTO-4-ADV_IPSERVICES_LIC_NOT_ENABLED |
4-Warning |
advipservices license is required to enable IPSec IPv6 feature. Please install the license and retry.\n |
IPSec IPv6 subsystem is bundled with advipservices license. So check if this license is enabled to include IPSec IPv6 subsystem. |
ipsec-core |
"Enable ADV_IPSERVICES license." |
|
CRYPTO-4-AUDITWARN |
4-Warning |
Encryption audit check could not be performed |
The audit check verifying encryption entitlement within the IOS image could not be performed due to incompete system configuration. |
- |
"Manually verify that this IOS image is entitled to contain " "encryption." |
|
CRYPTO-4-ENC_METHOD_NOT_SUPPORTED |
4-Warning |
Invalid encryption method for IKE policy [dec] |
Configured encryption method is not supported |
- |
"Use any of the valid encryption methods for the ISAKMP policy" |
|
CRYPTO-4-EZVPN_FAILED_TO_CONNECT |
4-Warning |
[chars] |
Ezvpn session failed to come up ezvpn is stuck in a state waiting for an event posting a reset message to recover. |
- |
"" |
|
CRYPTO-4-EZVPN_SA_LIMIT |
4-Warning |
[chars] |
The limit for maximum no of ezvpn tunnels that can be setup on the platform has reached. Active SAs shall not be terminated but no additional SAs can be established until the number of existing SAs decreases. |
- |
"" |
|
CRYPTO-4-GM_ISAKMP_OFF |
4-Warning |
Can't start GDOI registration as ISAKMP disabled |
Crypto ISAKMP is not enabled |
ipsec-mcast |
"Enable crypto ISAKMP" |
|
CRYPTO-4-GM_LOCAL_ADDRESS |
4-Warning |
Failed to determine local ip address for group [chars] on interface [chars] |
Failed to determine local address for GDOI crypto map |
ipsec-mcast |
LOG_STD_ACTION |
|
CRYPTO-4-GM_REGSTER_IF_DOWN |
4-Warning |
Can't start GDOI registeration as interface [chars] is down |
Interface is found down before registration |
ipsec-mcast |
LOG_STD_ACTION |
|
CRYPTO-4-GM_ZERO_ADDRESS |
4-Warning |
No ip address found for group [chars] on source interface [chars] |
Souce IP address for GDOI crypto map is zero |
ipsec-mcast |
LOG_STD_ACTION |
|
CRYPTO-4-IA_CLEARTEXT |
4-Warning |
Unencrypted traffic [chars] [inet] because crypto optional is configured |
Cleartext traffic is passing through an interface that is configured for encryption. This traffic is accepted because the router has the CRYPTO IPSEC OPTIONAL ENABLE setting which allows such traffic. |
ipsec |
"If you did not intend to configure the crypto " "optional setting you should reconfigure the box " "to turn it off" |
|
CRYPTO-4-IA_ENABLE |
4-Warning |
Security warning: crypto ipsec optional is configured |
Currently the router has the CRYPTO IPSEC OPTIONAL ENABLE setting which allows data which normally would be encrypted to be sent in the clear. |
ipsec |
"If you did not intend to configure the crypto " "optional setting you should reconfigure the box to turn " "it off" |
|
CRYPTO-4-IKE_DEFAULT_POLICY_ACCEPTED |
4-Warning |
IKE default policy was matched and is being used. |
The default policy is being used because the local configured policies did not match with the peer's policies. |
ipsec-isakmp |
"To avoid using the default policy " "reconfigure the local policy to match " "with peer's policy" |
|
CRYPTO-4-IKE_QUICKMODE_BAD_CERT |
4-Warning |
encrypted connection attempted with a peer without the\n configured certificate attributes |
An encrypting peer attempted to establish an IPSec session with an interface which it was not authorized for. Some might consider this a hostile event. |
- |
"Check if the peer should be authorized to connect with the" " IPSec connection. If he should be allowed it may be a" " configuration issue. Otherwise you should contact the" " peer's administrator." |
|
CRYPTO-4-IKMP_BAD_MESSAGE |
4-Warning |
IKE message from [chars] failed its sanity check or is malformed |
A quick sanity check is done on all received ISAKMP messages to verify that all component payload types are valid and that the sum of their individual lengths equals the total length of the received message. This message failed the sanity check. Persistantly bad messages could be a denial of service attack or bad decryption. |
- |
"Contact the remote peer's administrator." |
|
CRYPTO-4-IKMP_HASH_SIZE_EXCEEDED |
4-Warning |
IKE hash size exceeded with peer at [inet]. |
A hash operation required by the IKE protocol exceeded an internal limit. The IKE SA negotiation was rejected. That can happen if an inordinately large number of IKE policies were being proposed by the initiator |
- |
"Reduce the number of configured IKE policies." |
|
CRYPTO-4-IKMP_INVALID_POLICY |
4-Warning |
ISAKMP policy rsa-encr not supported by crypto HW accelerator [chars] |
rsa-encr is not supported by Hifn based crypto HW accelerators |
- |
"Use ISAKMP policy rsa-sig" |
|
CRYPTO-4-IKMP_ISR_LIMIT_MAX |
4-Warning |
INV SPI RECOV LIMIT [dec] maxed [chars] [chars] [chars] |
INVALID SPI RECOVERY SAs maximum limit has been reached. |
- |
"Possibly the local box reloaded." |
|
CRYPTO-4-IKMP_NO_SA |
4-Warning |
IKE message from [chars] has no SA and is not an initialization offer |
IKE maintains state for a communication in the form of security associations. No security association exists for this packet and it is not an initial offer from the peer to establish one. This situation could denote a denial of service attack. |
- |
"Contact the remote peer and/or his administrator" |
|
CRYPTO-4-IKMP_PKT_OVERFLOW |
4-Warning |
ISAKMP message from [chars] larger %ld than the UDP packet length %ld |
- |
- |
- |
|
CRYPTO-4-IPSEC_AAA_START_FAILURE |
4-Warning |
IPSEC Accounting was unable to send start record |
The AAA subsystem was unable to send the accounting start on behalf of IPSec. This could be due to the AAA Server being unreachable. |
ipsec |
"Ensure that the AAA server is reachable and enabled" "for accounting." |
|
CRYPTO-4-IPSEC_AAA_STOP_FAILURE |
4-Warning |
IPSEC Accounting was unable to send stop record |
The AAA subsystem was unable to send the accounting stop on behalf of IPSec. This could be due to the AAA Server being unreachable. |
ipsec |
"Ensure that the AAA server is reachable and enabled" "for accounting." |
|
CRYPTO-4-IPSEC_ENC_METHOD_NOT_SUPPORTED |
4-Warning |
Transform [chars] not valid under IPSec transform [chars] |
Configured encryption algorithm not supported |
- |
"Specify a valid encryption algorithm for the ipsec transform" |
|
CRYPTO-4-IPSEC_ENC_METHOD_NOT_SUPPORTED_FULL_SPEED |
4-Warning |
Transform [chars] will run with reduced performance because of IPSec transform [chars] |
Configured encryption algorithm will not run on the hardware encryption card. The transform is still usable but will run with reduced performance. |
- |
"If you need to use the full performance of the encryption card " "specify another encryption algorithm for the ipsec transform" |
|
CRYPTO-4-IPSEC_ENC_METHOD_NOT_SUPPORTED_WITH_IKE |
4-Warning |
Transform [chars] not usable with IKE because of IPSec transform [chars] |
Configured encryption algorithm not uable with IKE with current hardware configuration |
- |
"If you need to negotiate this with IKE specify a valid encryption " "algorithm for the ipsec transform" |
|
CRYPTO-4-ONTOKENKEYSDEACTIVATED |
4-Warning |
On-Token RSA keypairs from token [chars] and associated IPSEC sessions being deactivated now |
On-Token Router RSA keypairs and associated IPSEC sessions are being deactivated because the token containing them was removed |
pki |
"Re-insert the crypto token" |
|
CRYPTO-4-PKT_REPLAY_ERR |
4-Warning |
[chars]\n \tconnection id=[dec] sequence number=%lu\n |
Replay processing failed. This may be a temporary condition due to waiting for new SAs to be established. In the inbound case this may also be due to an actual replay attack. Some might consider this a hostile event. |
- |
"If the problem appears to be more than a transient one" " contact the peer's administrator." |
|
CRYPTO-4-RECVD_PKT_FAIL_DECOMPRESS |
4-Warning |
pcp: [dec] byte packet failed to decompress pcp: dest_addr=[inet] src_addr=[inet] |
The received IPPCP packet failed to decompress. This may be due to a decompression buffer error. |
- |
LOG_STD_ACTION |
|
CRYPTO-4-RECVD_PKT_INV_CTCP_WRAPPER |
4-Warning |
Rec'd packet has invalid cTCP wrapper protocol.\n \tcryptoflags = [hec] sa->udp_wrapper_support = [dec] transform = [hec] |
Rec'd packet either cTCP encapsulated but is not correct negotiation transform. Or it expected an cTCP encapsulated packet but it received a non-cTCP packet. There may simply be a policy setup error on the peer. Some might consider this a hostile event. |
- |
"Contact the peer's administrator to compare policy settings." |
|
CRYPTO-4-RECVD_PKT_INV_IDENTITY |
4-Warning |
[chars]\n \tip dest_addr= [inet] src_addr= [inet] prot= [dec]\n |
Decapsulated IPSEC packet not maching negotiated identity The peer is sending other traffic through this SA. It may be due to an SA selection error by the peer. Some might consider this a hostile event. |
- |
"Contact the peer's administrator to compare policy settings." |
|
CRYPTO-4-RECVD_PKT_INV_IDENTITY_ACL |
4-Warning |
ipsec check access: identity not allowed by ACL\n \tip dest_addr= [inet] src_addr= [inet] prot= [dec]\n |
After all is said and done the decaps packet fails the ACL check The peer is sending other traffic through this SA. It may be due to an SA selection error by the peer. Some might consider this a hostile event. |
- |
"Contact the peer's administrator to compare policy settings." |
|
CRYPTO-4-RECVD_PKT_INV_PROT |
4-Warning |
decapsulate: packet missing [chars] destadr=[inet] actual prot=[dec] |
Rec'd IPSEC packet missing an expected AH or ESP header The peer is sending packets that don't match the negotiated security policy. Some might consider this a hostile event. |
- |
"Contact the peer's administrator." |
|
CRYPTO-4-RECVD_PKT_INV_SPI |
4-Warning |
decaps: rec'd IPSEC packet has invalid spi for destaddr=[chars] prot=[dec] spi=0x[hec][dec] srcaddr=[chars] |
Rec'd IPSEC packet specifies SPI that doesn't exist in SADB. This may be a temporary condition due to slight differences in aging of SAs between the IPSEC peers or it may be because the local SAs have been cleared. It may also be because of bogus packets sent by the IPSEC peer. Some might consider this a hostile event. |
- |
"If the local SAs have been cleared the peer may not know" " this. In this case if a new connection is established" " from the local router the two peers may reestablish " " successfully. Otherwise if the problem occurs for more than " " a brief period either attempt to establish a new connection " " or contact the peer's administrator." |
|
CRYPTO-4-RECVD_PKT_INV_UDP_WRAPPER |
4-Warning |
Rec'd packet has invalid udp wrapper protocol.\n \tcryptoflags = [hec] sa->udp_wrapper_support = [dec] transform = [hec] |
Rec'd packet either udp encapsulated but is not correct negotiation transform. Or it expected an udp encapsulated packet but it received a non-udp packet. There may simply be a policy setup error on the peer. Some might consider this a hostile event. |
- |
"Contact the peer's administrator to compare policy settings." |
|
CRYPTO-4-RECVD_PKT_MAC_ERR |
4-Warning |
decrypt: mac verify failed for connection id=[dec][chars] |
MAC verify processing failed. This may be due to the use of the wrong key by either party during the MAC calculations. Some might consider this a hostile event. |
- |
"Contact the peer's administrator." |
|
CRYPTO-4-RECVD_PKT_MSG_LEN_ERR |
4-Warning |
decapsulate: packet has bad [chars] length destadr=[inet] prot=[dec] len=[dec] |
Rec'd IPSEC packet is malformed: possibly encapsulation error? The peer is sending malformed packets. It may be due to a decryption error. Some might consider this a hostile event. |
- |
"Contact the peer's administrator." |
|
CRYPTO-4-RECVD_PKT_NOT_IPSEC |
4-Warning |
Rec'd packet not an IPSEC packet. ip vrf/dest_addr= [chars]/[inet] src_addr= [inet] prot= [dec] |
Rec'd packet matched crypto map ACL but is not IPSEC-encapsulated. IPSEC Peer is sending unencapsulated packets. There may simply be a policy setup error on the peer. Some might consider this a hostile event. |
- |
"Contact the peer's administrator to compare policy settings." |
|
CRYPTO-4-RECVD_PKT_NOT_IPSEC_V6 |
4-Warning |
Rec'd packet not an IPSEC packet. ip vrf/dest_addr= [chars]/[chars] src_addr= [chars] prot= [dec] |
- |
- |
- |
|
CRYPTO-4-REM_CRYPTOMAP_TS |
4-Warning |
\nPlease recheck your crypto map [chars]. |
Transform set entry removed from crypto-map as it is no longer valid with hardware crypto engine enabled. |
- |
"Create and apply valid transform set to cryptomap" |
|
CRYPTO-4-TOKENKEYSDEACTIVATED |
4-Warning |
RSA keypairs from token [chars] and associated IPSEC sessions being deactivated now |
Router RSA keypairs and associated IPSEC sessions are being deactivated because the token containing them was removed |
pki |
"Re-insert the crypto token" |
|
CRYPTO-4-TOKENKEYTIMEOUT |
4-Warning |
RSA keypairs for token [chars] and associated IPSEC sessions will be deactivated in [dec] seconds |
Router RSA keypairs and associated IPSEC sessions will be deactivated when the timeout expires |
pki |
"Re-insert the crypto token before the timeout expires" |
|
CRYPTO-4-TRANSFORM_NOT_SUPPORTED |
4-Warning |
\nTransform [chars] is not supported with the current hardware configuration.\nGlobal transform [chars] will be deleted. |
System configuration modified.Some ipsec transforms which were earlier valid with software crypto are no longer valid now after switching hardware crypto. |
- |
"Create valid transform sets & update cryptomaps" |
|
CRYPTO-5-GM_CONN_NEXT_SER |
5-Notice |
GM is connecting to next key server from the list |
Connect to next key server |
ipsec-mcast |
LOG_STD_ACTION |
|
CRYPTO-5-GM_REGSTER |
5-Notice |
Start registration to KS [chars] for group [chars] using address [chars] fvrf [chars] ivrf [chars] |
Start registration for one group |
ipsec-mcast |
LOG_STD_ACTION |
|
CRYPTO-5-IKE_SA_HA_STATUS |
5-Notice |
IKE sa's if any for vip [inet] will change from [chars] to [chars] |
This is a notification message for crypto ike sa's changing their HA status |
ipsec-ha |
"No action is required" |
|
CRYPTO-5-IKEV2_SESSION_STATUS |
5-Notice |
Crypto tunnel v2 is [chars]. Peer [chars]:[dec] [chars] [chars] [chars] [chars] [chars] [chars] [chars] [chars] |
This is a notification message for IPSEC tunnel status |
- |
"No action is required" |
|
CRYPTO-5-IKMP_AG_MODE_DISABLED |
5-Notice |
Unable to initiate or respond to Aggressive Mode while disabled |
The router is configured not to accept or respond to ISAKMP aggressive mode with any peer |
ipsec-isakmp |
"If you did not intend to disable aggressive-mode" " then remove the command" |
|
CRYPTO-5-IKMP_INVAL_CERT |
5-Notice |
Certificate received from [chars] is bad: [chars] |
The certificate given by remote peer has either been revoked or expired certificate invalid or the signature check on the |
- |
"Contact the CA of the remote peer. Possibly bad CA certificate." |
|
CRYPTO-5-IKMP_SETUP_FAILURE |
5-Notice |
IKE SETUP FAILED for local:[chars] local_id:[chars] remote:[chars] remote_id:[chars] IKE profile:[chars] fvrf:[chars] fail_reason:[chars] fail_class_cnt:%ld |
IKE Negotiation Failed. |
- |
"LOG_STD_ACTION" |
|
CRYPTO-5-IPSEC_FAILURE |
5-Notice |
IPsec setup has failed local_ip: [chars] remote_ip: [chars] fail_reason: [chars] |
IPSEC Negotiation has failed |
- |
"LOG_STD_ACTION" |
|
CRYPTO-5-IPSEC_SA_HA_STATUS |
5-Notice |
IPSec sa's if any for vip [inet] will change from [chars] to [chars] |
This is a notification message for crypto ipsec sa's changing their HA status |
ipsec-ha |
"No action is required" |
|
CRYPTO-5-IPSEC_SETUP_FAILURE |
5-Notice |
IPSEC SETUP FAILED for local:[chars] local_id:[chars] remote:[chars] remote_id:[chars] IKE profile:[chars] fvrf:[chars] fail_reason:[chars] fail_class_cnt:%ld |
IPSec Negotiation Failed. |
- |
"LOG_STD_ACTION" |
|
CRYPTO-5-SELF_TEST_END |
5-Notice |
Crypto algoritms self-test completed successfully\n\ All tests passed. |
The device has completed the Crypto algorithms self-tests.\n\ All of the self-tests have passed. |
- |
"Informational only. No action required." |
|
CRYPTO-5-SESSION_STATUS |
5-Notice |
Crypto tunnel is [chars]. Peer [chars]:[dec] [chars] [chars] [chars] [chars] [chars] [chars] [chars] [chars] |
- |
- |
- |
|
CRYPTO-6-AUTOGEN |
6-Information |
Generated new [dec] bit key pair |
Auto-Enroll has generated a new router key pair |
- |
"No action required. Informational message" |
|
CRYPTO-6-CET_END_OF_LIFE |
6-Information |
CET connection msg in an IPSEC_ONLY_IMAGE |
CET has been End-of-lifed in IOS release 12.21 |
CSCds60123 |
"" |
|
CRYPTO-6-EZVPN_CONNECTION_DOWN |
6-Information |
[chars] |
Ezvpn connection is being closed. The IPsec and IKE security associations will also be brought down along with it. |
- |
"" |
|
CRYPTO-6-EZVPN_CONNECTION_UP |
6-Information |
[chars] |
Ezvpn connection is up for the client mentioned. Both IPsec and IKE security Associations are up now. |
- |
"" |
|
CRYPTO-6-GDOI_ON_OFF |
6-Information |
GDOI is [chars] |
The ISAKMP/gdoi process has been switched on or off either by CLI or because no GDOI crypto map or Key Server is applied to any interface. |
ipsec-getvpn |
"No action required." |
|
CRYPTO-6-IKE_TED_BAD_REPLY |
6-Information |
Received TED reply that did not correspond to a TED probe |
Rec'd TED reply that does not match a TED probe we currently have outstanding. This may be a one time occurance due to the TED reply being delayed. It may also be because of ill-formed packets sent by the peer. Some might consider this a hostile event. |
- |
"If the problem occurs more than once contact the peer's" " administrator." |
|
CRYPTO-6-IKMP_ADD_KEY_FAIL |
6-Information |
Unable to add public key for [chars] %15i to key ring |
Keys are stored in keyrings on the router. An attempt to add another key to the ring failed. |
- |
"Check local key rings. This is probably due to other failures." |
|
CRYPTO-6-IKMP_AUTH_FAIL |
6-Information |
Authentication method [dec] failed with host [chars] |
The IKE process was unable to authenticate its security Association with its remote peer. |
- |
"Contact the remote peer's administrator." |
|
CRYPTO-6-IKMP_BAD_CERT_USE |
6-Information |
Certificate for peer at [chars] prohibits attempted use [chars]. |
X.509v3 certificates can contain usage restrictions. These can restrict use of the certificate only for signatures or only for key exchange encryption. The peer attempted to |
- |
"Contact the remote peer and the remote peer's CA" |
|
CRYPTO-6-IKMP_BAD_DOI_NOTIFY |
6-Information |
DOI of [dec] in notify message from [chars] |
The DOI field in notify messages give the receiver a context in which to understand the message being notified. This DOI value is not understood and the message therefore cannot be understood. |
- |
"If this situation persists contact the remote peer." |
|
CRYPTO-6-IKMP_BAD_DOI_SA |
6-Information |
DOI value [dec] from SA offer from [chars] is invalid |
The DOI field of an SA offer defines how to parse the fields SAs with an unknown DOI cannot be parsed |
- |
"If this situation persists contact the remote peer's administrator" |
|
CRYPTO-6-IKMP_CRYPT_FAILURE |
6-Information |
IKE connection id [dec] unable to [chars] packet |
Encryption or decryption on a particular IKE thread failed. |
- |
"Contact remote peer" |
|
CRYPTO-6-IKMP_MODE_FAILURE |
6-Information |
Processing of [chars] mode failed with peer at [chars] |
Negotiation with the remote peer failed. |
- |
"If this situation persists contact the remote peer" |
|
CRYPTO-6-IKMP_NO_ID_CERT_ADDR_MATCH |
6-Information |
NOT ERROR BUT WARNING ONLYID of [chars] type [dec] and certificate addr with [chars] |
ISAKMP entities assume an identity to inform the peer of who or what they are. The claimed identity did not match the information gleaned from the ip address of the peer's certificate. |
- |
"Contact the remote peer if this situation persists" |
|
CRYPTO-6-IKMP_NO_ID_CERT_DN_MATCH |
6-Information |
NOT ERROR BUT WARNING ONLYID of [chars] type [dec] and certificate DN with [chars] |
ISAKMP entities assume an identity to inform the peer of who or what they are. The claimed identity did not match the information gleaned from the distinguished name of the peer's certificate. |
- |
"Contact the remote peer if this situation persists" |
|
CRYPTO-6-IKMP_NO_ID_CERT_FQDN_MATCH |
6-Information |
NOT ERROR BUT WARNING ONLYID of [chars] type [dec] and certificate fqdn with [chars] |
ISAKMP entities assume an identity to inform the peer of who or what they are. The claimed identity did not match the information gleaned from the fqdn of the peer's certificate. |
- |
"Contact the remote peer if this situation persists" |
|
CRYPTO-6-IKMP_NO_ID_CERT_USER_FQDN_MATCH |
6-Information |
NOT ERROR BUT WARNING ONLYID of [chars] type [dec] and certificate user fqdn with [chars] |
ISAKMP entities assume an identity to inform the peer of who or what they are. The claimed identity did not match the information gleaned from the user fqdn of the peer's certificate. |
- |
"Contact the remote peer if this situation persists" |
|
CRYPTO-6-IKMP_NOT_ENCRYPTED |
6-Information |
IKE packet from [chars] was not encrypted and it should've been. |
A portion of the IKE exchange takes place in the clear and a portion is encrypted. This message should have been encrypted but was not. |
- |
"Contact remote peer" |
|
CRYPTO-6-IKMP_POLICY_DEFAULT |
6-Information |
Using ISAKMP Default policies |
Since the user has not configured any ISAKMP policies and default ISAKMP policies are enabled then use default ISAKMP policies for negotiation |
- |
"" |
|
CRYPTO-6-IKMP_SA_NOT_AUTH |
6-Information |
Cannot accept Quick Mode exchange from [chars] if SA is not authenticated! |
The IKE security association with the remote peer was not authenticated yet the peer attempted to begin a Quick Mode exchange. This exchange must only be done with an authenticated security association |
- |
"Contact remote peer" |
|
CRYPTO-6-IKMP_SA_NOT_OFFERED |
6-Information |
Remote peer [chars] responded with attribute [chars] not offered or changed |
IKE peers negotiate policy by the initiator offering a list of possible alternate protection suites. The responder responded with one that the initiator did not offer |
- |
"Contact the remote peer" |
|
CRYPTO-6-IKMP_UNK_EXCHANGE |
6-Information |
IKE peer at [chars] sent a message with unknown exchange [dec] |
IKE preforms actions on messages based on defined exchanges. The message received had an unknown exchange. |
- |
"Contact the remote peer's administrator" |
|
CRYPTO-6-IPSEC_USING_DEFAULT |
6-Information |
IPSec is using default transforms |
No IPSec transform-set defined and default policy is enabled. Therefore default policies are being proposed to the peer |
ipsec-core |
"To avoid using IPSec default policy" "reconfigure a transform set to be used for " "this crypto session" |
|
CRYPTO-6-ISAKMP_MANUAL_DELETE |
6-Information |
IKE SA manually deleted. Do 'clear crypto sa peer [chars]' to manually clear IPSec SA's covered by this IKE SA. |
The IKE SA was deleted by user command. However keepalives this connection are enabled and IPSec SA's covered by this IKE SA still exist. Since this IKE SA is now deleted these IPSec SA's have no IKE SA covering them. The recommended action is to manually delete this IPSec SA's. |
ipsec |
"Use parser command "clear crypto sa" to clear " "IPSec SA's." |
|
CRYPTO-6-ISAKMP_ON_OFF |
6-Information |
ISAKMP is [chars] |
The ISAKMP process has been switched on or off either by CLI or because no crypto map or EzVPN configuration is applied to any interface. |
ipsec-isakmp |
"No action required." |
|
CRYPTO-6-LLQ_OVERSUBSCRIBE |
6-Information |
Sum of priority class bandwidth exceeds crypto engine's throughput for small packets crypto b/w=[dec] kbps allocated b/w=[dec] kbps. |
The crypto engine may be oversubscribed by priority class traffic. This happens when the user tries to provision more priority class bandwidth than what the crypto engine can handle. If each class is sending at its max rate some priority packets may be dropped |
- |
"Reduce the priority class bandwidth or reduce" "the number of priority classes in the policy-map" |
|
CRYPTO-6-PRINTABORT |
6-Information |
[chars] caused early termination of show output[chars] |
While showing a list the list was changed or elements changed. This can happen if SA's are re-negotiated at the time the show-command was paused or if someone reconfigured or cleared SA's amongst other things. This is not an error but a side-effect of a dynamic system. |
ipsec |
"In general this is merely a warning that the " "output from the show command is most likely incomplete. " "Re-running the show-command should provide the newest " "information. On a busy system with ever-changing SA's " "this may appear frequently." |
|
CRYPTO-6-PRNG_SEED_KEY_ERROR |
6-Information |
Pseudo-random number generator seed and seed key was identical |
The X9.17 random number specification requires us to check for\n\ the same value appearing as the seed and the seed key. This\n\ message indicates that the condition was discovered. |
ipsec |
"The X9.17 random number will occasionally produce this condition\n\ and this is not a problem. However if this message occurs frequently\n\ the system should be manually reloaded. If the message is persistent\n\ across reloads copy the error message exactly as it appears and\n\ report it to your technical support representative." |
|
CRYPTO-6-RANDOM |
6-Information |
A pseudo-random number was generated twice in succession by [chars] |
A pseudo-random number generator produced the same number twice\n\ in succession. |
ipsec |
"Under normal circumstances a pseudo-random number generator will\n\ occasionally produce the same number twice in succession and this\n\ is not a problem. However if this message occurs frequently the \n\ system should be manually reloaded. If the message is persistent \n\ across reloads copy the error message exactly as it appears and \n\ report it to your technical support representative." |
|
CRYPTO-6-SELF_TEST_RESULT |
6-Information |
Self test info: [chars] |
This audit prompt the results of Cryptographical selftests |
- |
"This message is for information only. No action is" " required." |
|
CRYPTO-6-TOKENADMINCHANGEPIN |
6-Information |
Cryptographic Token [chars] ADMIN PIN change Successful |
The cryptographic token has accepted the new administrator PIN offered by the router |
- |
"Informational message only. No action required." |
|
CRYPTO-6-TOKENADMINLOGIN |
6-Information |
Cryptographic Token [chars] ADMIN Login Successful |
The cryptographic token has accepted the administrator PIN offered by the router |
- |
"Informational message only. No action required." |
|
CRYPTO-6-TOKENCHANGEPIN |
6-Information |
Cryptographic Token [chars] PIN change Successful |
The cryptographic token has accepted the new PIN offered by the router |
- |
"Informational message only. No action required." |
|
CRYPTO-6-TOKENINSERTED |
6-Information |
Cryptographic token [chars] inserted in [chars] |
A cryptographic token has been detected |
- |
"Informational message only. No action required." |
|
CRYPTO-6-TOKENLOGIN |
6-Information |
Cryptographic Token [chars] Login Successful |
The cryptographic token has accepted the PIN offered by the router |
- |
"Informational message only. No action required." |
|
CRYPTO-6-TOKENLOGOUT |
6-Information |
Cryptographic Token [chars] Logout Successful |
The router has logged out from the cryptographic token |
- |
"Informational message only. No action required." |
|
CRYPTO-6-TOKENREMOVED |
6-Information |
Cryptographic token [chars] removed from [chars] |
A cryptographic token has been detected |
- |
"Informational message only. No action required." |
|
CRYPTO-6-TOKENSTOREKEY |
6-Information |
Key [chars] stored on Cryptographic Token [chars] Successfully |
A new keypair has been written out to the cryptographic token |
- |
"Informational message only. No action required." |
|
CRYPTO-6-TOKENTIMEOUTCANCELLED |
6-Information |
Cryptographic Token [chars] re-inserted. removal timeout cancelled |
A cryptographic token containing private key files has been re-inserted in time. Router RSA keypairs and associated IPSEC sessions will be NOT be deactivated |
- |
"Informational message only. No action required." |
|
CRYPTO-6-VPN_TUNNEL_STATUS |
6-Information |
[chars] |
VPN tunnel status. |
- |
"" |
|
CSG-3-ERROR |
3-Error |
Module [dec]: [chars] |
An error occurred in a CSG module. |
csg |
LOG_STD_RECUR_ACTION |
|
CSG-3-RELOADNOTOK |
3-Error |
CSG ACCOUNTING [chars] reload on module [dec] failed. |
Informational message whenever a CSG configuration\n\ is reloaded as a result of power recycling a CSG card. |
csg |
LOG_STD_NO_ACTION |
|
CSG-4-WARNING |
4-Warning |
Module [dec]: [chars] |
Some possibly undesired event occurred in a CSG module. |
csg |
LOG_STD_RECUR_ACTION |
|
CSG-6-LIRELOADOK |
6-Information |
CSG LI reload on module [dec] successful |
Informational message whenever a CSG LI configuration\n\ is reloaded as a result of power recycling a CSG card. |
csg |
LOG_STD_NO_ACTION |
|
CSG-6-RELOADOK |
6-Information |
CSG ACCOUNTING [chars] reload on module [dec] successful |
Informational message whenever a CSG configuration\n\ is reloaded as a result of power recycling a CSG card. |
csg |
LOG_STD_NO_ACTION |
|
CSM_SLB-3-ERROR |
3-Error |
Module [dec] error: [chars] |
An error occurred in a CSM-SLB module. |
laminar |
LOG_STD_RECUR_ACTION |
|
CSM_SLB-3-IDB_ERROR |
3-Error |
Unknown error occurred while configuring IDB for CSM-SLB module: [chars]. |
Unable to configure data path for CSM-SLB card. |
laminar |
LOG_STD_RECUR_ACTION |
|
CSM_SLB-3-OUTOFMEM |
3-Error |
Module [dec] memory error: [chars] |
Out of memory condition while downloading SLB configurations onto CSM card. |
laminar |
LOG_STD_RECUR_ACTION |
|
CSM_SLB-3-PORTCHANNEL |
3-Error |
Portchannel allocation failed for module [dec]. |
Unable to allocate enough portchannel groups for CSM-SLB card. |
laminar |
LOG_STD_RECUR_ACTION |
|
CSM_SLB-3-REDUNDANCY |
3-Error |
Module [dec] FT error: [chars] |
An error occurred in CSM-SLB fault tolerance. |
laminar |
LOG_STD_RECUR_ACTION |
|
CSM_SLB-3-RELOAD |
3-Error |
Module [dec] configuration reload failed: [chars] |
Configuration reload of the CSM-SLB card failed. |
laminar |
LOG_STD_RECUR_ACTION |
|
CSM_SLB-3-SCRIPT |
3-Error |
Module [dec] script error: [chars] |
An error occurred in a CSM-SLB script. |
laminar |
LOG_STD_RECUR_ACTION |
|
CSM_SLB-3-UNEXPECTED |
3-Error |
Module [dec] unexpected error: [chars] |
An unexpected error condition occurred on the CSM-SLB card while performing Server Load Balancing. |
laminar |
LOG_STD_RECUR_ACTION |
|
CSM_SLB-3-VERMISMATCH |
3-Error |
Module [dec] image version mismatch RP = [chars] CSM = [chars]: [chars] |
Router image and CSM-SLB image do not correspond. |
laminar |
LOG_STD_RECUR_ACTION |
|
CSM_SLB-4-ARPCONFIG |
4-Warning |
Module [dec] ARP configuration error: [chars] |
Error creating or removing a static ARP route. |
laminar |
LOG_STD_RECUR_ACTION |
|
CSM_SLB-4-DUPLICATEID |
4-Warning |
Module [dec] duplicate ID: [chars] |
Same ID was used to create multiple entities. |
laminar |
LOG_STD_NO_ACTION |
|
CSM_SLB-4-ERRPARSING |
4-Warning |
Module [dec] configuration warning: [chars] |
Syntax error in a URL or COOKIE regular expression in SLB configuration. |
laminar |
LOG_STD_NO_ACTION |
|
CSM_SLB-4-INVALIDID |
4-Warning |
Module [dec] invalid ID: [chars] |
The entity identified does not exist. |
laminar |
LOG_STD_NO_ACTION |
|
CSM_SLB-4-PROBECONFIG |
4-Warning |
Module [dec] probe configuration error: [chars] |
Health probe configuration failed. |
laminar |
LOG_STD_NO_ACTION |
|
CSM_SLB-4-REDUNDANCY_WARN |
4-Warning |
Module [dec] FT warning: [chars] |
Some possibly undesired event occurred in CSM-SLB fault tolerance. |
laminar |
LOG_STD_RECUR_ACTION |
|
CSM_SLB-4-REGEXMEM |
4-Warning |
Module [dec] regular expression memory error: [chars] |
A lookup table does not contain enough space to store the configured URL and COOKIE regular expressions. Use 'show ip slb memory' to determine which virtual servers were unable to be configured because of |
laminar |
LOG_STD_NO_ACTION |
|
CSM_SLB-4-SCRIPT_WARN |
4-Warning |
Module [dec] script warning: [chars] |
Some possibly undesired event occurred in CSM-SLB scripting. |
laminar |
LOG_STD_RECUR_ACTION |
|
CSM_SLB-4-TOPOLOGY |
4-Warning |
Module [dec] warning: [chars] |
There may be a problem with your network topology or configuration. |
laminar |
LOG_STD_RECUR_ACTION |
|
CSM_SLB-4-VERWILDCARD |
4-Warning |
Received CSM-SLB module version wildcard on slot [dec]. Supervisor has version [dec]. |
User issued a command from the linecard to bypass the safeguard against module version mismatch. As a result configuration may fail. |
laminar |
LOG_STD_NO_ACTION |
|
CSM_SLB-4-WARNING |
4-Warning |
Module [dec] warning: [chars] |
Some possibly undesired event occurred in a CSM-SLB module. |
laminar |
LOG_STD_RECUR_ACTION |
|
CSM_SLB-6-GATEWAYSTATE |
6-Information |
Module [dec] gateway state changed: [chars] |
A gateway changed states. |
laminar |
LOG_STD_NO_ACTION |
|
CSM_SLB-6-INFO |
6-Information |
Module [dec] info: [chars] |
Some event occurred in a CSM-SLB module. |
laminar |
LOG_STD_NO_ACTION |
|
CSM_SLB-6-REDUNDANCY_INFO |
6-Information |
Module [dec] FT info: [chars] |
Some event occurred in CSM-SLB fault tolerance. |
laminar |
LOG_STD_NO_ACTION |
|
CSM_SLB-6-RSERVERSTATE |
6-Information |
Module [dec] server state changed: [chars] |
A real server changed states failed or recovered. Possible causes might be configuration changes arp checks or health probes. |
laminar |
LOG_STD_NO_ACTION |
|
CSM_SLB-6-SCRIPT_INFO |
6-Information |
Module [dec] script info: [chars] |
Some event occurred in CSM-SLB scripting. |
laminar |
LOG_STD_NO_ACTION |
|
CSM_VOICE-3-ADDINTRFFAIL |
3-Error |
The Voice Telephony Service Provider has rejected our\n\ request to add this voice interface [dec]:[dec] |
The voice software was unable to report a new signaling\n\ interface to the Voice Telephony Service Provider |
as |
LOG_STD_SH_TECH_ACTION |
|
CSM_VOICE-3-ADDINTRFFAIL |
3-Error |
The Voice Telephony Service Provider has rejected our\n\ request to add this voice interface [dec]/[dec]:[dec] |
The voice software was unable to report a new signaling\n\ interface to the Voice Telephony Service Provider |
das |
LOG_STD_SH_TECH_ACTION |
|
CSM_VOICE-3-MALLOC |
3-Error |
No memory is available to build any internal data \n\ structure for the voice software. |
The voice software was unable allocate memory to build \n\ any internal data structures. The system may be \n\ out of memory. |
as |
LOG_STD_SH_TECH_ACTION |
|
CSM_VOICE-3-MALLOC |
3-Error |
No memory is available to build any internal data \n\ structure for the voice software. |
The voice software was unable allocate memory to build \n\ any internal data structures. The system may be \n\ out of memory. |
das |
LOG_STD_SH_TECH_ACTION |
|
CSM_VOICE-3-NOMEM |
3-Error |
No memory is available to build the voice interface [dec]:[dec] |
The voice software was unable allocate memory to build \n\ a voice interface data structure. The system may be \n\ out of memory. |
as |
LOG_STD_SH_TECH_ACTION |
|
CSM_VOICE-3-NOMEM |
3-Error |
No memory is available to build the voice interface [dec]:[dec] |
The voice software was unable allocate memory to build \n\ a voice interface data structure. The system may be \n\ out of memory. |
das |
LOG_STD_SH_TECH_ACTION |
|
CSM_VOICE-3-NOSDB |
3-Error |
No signaling data block is available to build the \n\ voice interface[dec]:[dec] |
The voice software was unable to obtain a signaling data\n\ block from the Voice Telephony Service Provider. \n\ The system may be out of memory. |
as |
LOG_STD_SH_TECH_ACTION |
|
CSM_VOICE-3-NOSDB |
3-Error |
No signaling data block is available to build the \n\ voice interface[dec]/[dec]:[dec] |
The voice software was unable to obtain a signaling data\n\ block from the Voice Telephony Service Provider. \n\ The system may be out of memory. |
das |
LOG_STD_SH_TECH_ACTION |
|
CSM_VOICE-3-NOTDMCHNL |
3-Error |
CSM failed to get a free dsp tdm channel from the DSP\n\ Resource Manager DSPRM to handle an incoming call |
The voice software was unable to obtain the tdm channel \n\ for a free dsp from the DSP Resource Manager. All of \n\ the dsp's have been used to process calls or have\n\ been taken out of service. |
as |
LOG_STD_SH_TECH_ACTION |
|
CSM_VOICE-3-TDMHPMADDFAIL |
3-Error |
CSM failed to add the CAS TDM hairpinning call |
The CSM voice software interface was unable to add\n\ this call as hairpinning because of presence of\n\ another call for the same DS0. Internal software error. |
as |
LOG_STD_SH_TECH_ACTION |
|
CSM_VOICE-3-UNDEFDSX0 |
3-Error |
Undefined dsx0 interface for controller[dec] |
The dsx0 interface for the specified controller\n\ is not defined but the voice software use it. |
as |
"Internal software fault. Contact your field service representative \n\ if this message is coincident with dropped calls." |
|
CSM_VOICE-3-UNDEFDSX0 |
3-Error |
Undefined dsx0 interface for controller[dec]/[dec] |
The dsx0 interface for the specified controller\n\ is not defined but the voice software use it. |
das |
"Internal software fault. Contact your field service representative \n\ if this message is coincident with dropped calls." |
|
CSM_VOICE-3-UNDEFVOICEINTRF |
3-Error |
Invalid voice interface controller:group[dec]:[dec] |
The voice interface defined by controller:group is not\n\ yet defined within the voice software but attempts were\n\ made to use this interface. |
as |
"Internal software fault. Contact your field service \n\ representative if this message is coincident with \n\ dropped calls." |
|
CSM_VOICE-3-UNDEFVOICEINTRF |
3-Error |
Invalid interface slot:controller:group[dec]/[dec]:[dec] |
The voice interface defined by slot:controller:group is not\n\ yet defined within the voice software but attempts were\n\ made to use this interface. |
das |
"Internal software fault. Contact your field service \n\ representative if this message is coincident with \n\ dropped calls." |
|
CSM-1-CAS_ALLOC_FAIL |
1-Alert |
Fail to add new signal channel [dec]/[dec] timeslot [dec] |
- |
- |
"" |
|
CSM-1-CSM_CALL_INFO_MISMATCH |
1-Alert |
csm_call_info contains\n\ mismatch information call info has [chars]:[dec] framer gives [dec]/[dec]:[dec] |
- |
- |
"" |
|
CSM-1-CSM_CALL_NO_RESOURCE |
1-Alert |
Failed to allocate resource for call from [dec]/[dec]:[dec] |
- |
- |
"" |
|
CSM-1-CSM_STRING_OVERRUN |
1-Alert |
String copy exceeded buffer size |
The string written into the allocated buffer exceeded the size of\n\ the buffer. This can cause memory corruption. |
- |
LOG_STD_ACTION |
|
CSM-1-DCHAN_ALLOC_FAIL |
1-Alert |
For channel [chars] |
- |
- |
"" |
|
CSM-1-HWIDB |
1-Alert |
[chars]: hwidb is NULL |
An internal software error occurred. |
as |
LOG_STD_ACTION |
|
CSM-1-HWIDB_SUBBLOCK |
1-Alert |
[chars]: hwidb subblock for b channel [dec] is in use |
An internal software error occurred. |
as |
LOG_STD_ACTION |
|
CSM-1-INITFAIL |
1-Alert |
[chars] |
- |
- |
"" |
|
CSM-1-INITPORTFAIL |
1-Alert |
Initialization of vdev [dec]/[dec]/[dec] failed |
- |
- |
"" |
|
CSM-1-INITSYS |
1-Alert |
[chars] |
Failed to create a periodic process for CSM or the number of\n\ digit collectors reported to CSM exceeds the maximum number of\n\ digit collectors. |
as |
LOG_STD_ACTION |
|
CSM-1-INVALID_DC_NUMBER |
1-Alert |
Initialization failed with invalid digit collector count |
- |
- |
"" |
|
CSM-1-MODEM_INFO |
1-Alert |
[chars]: modem_info is NULL |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
CSM-1-NEW_RBS_CHAN |
1-Alert |
A new RBS channel added |
- |
- |
"" |
|
CSM-1-NO_CSM_CALL_INFO |
1-Alert |
No call control block |
- |
- |
"" |
|
CSM-1-NO_HWIDB |
1-Alert |
No B channel associated with call |
- |
- |
"" |
|
CSM-1-RBS |
1-Alert |
[chars] at slot [dec] controller [dec] timeslot [dec] |
This is an internal software error. An attempt is made to add non\n\ existent CAS signalling interface. |
as |
LOG_STD_ACTION |
|
CSM-3-NO_VDEV |
3-Error |
No modems associated:[chars]Chan[dec]Id[dec] |
- |
- |
"" |
|
CSM-5-PRI |
5-Notice |
[chars] at slot [dec] unit [dec] channel [dec] with index [dec] |
A PRI signalling channel is added/deleted to CSM's inventory\n\ of signalling channels. |
as |
"This is a notification message only.\n\ No action is required." |
|
CSMPI-3- ADDR_MISMATCH |
3-Error |
Region address error: start @ %p end @ %p part addr @ %p |
CSMPI encountered a bnad buffer address possible corruption. |
- |
LOG_STD_ACTION |
|
CSMPI-3- BAD_INDEX |
3-Error |
bad particle index [dec] max [dec] addr %p |
CSMPI encountered a bnad buffer address possible corruption. |
- |
LOG_STD_ACTION |
|
CSMPI-3- IF_INIT_FAILED |
3-Error |
CSMPI interface initialization failed. |
Essential CSMPI initialization has failed. |
- |
LOG_STD_ACTION |
|
CSMPI-3- PLATFORM_INIT_FAILED |
3-Error |
CSMPI platform initialization failed. |
Essential CSMPI initialization has failed. |
- |
LOG_STD_ACTION |
|
CTLPROVIDERSERV-3-NOINIT |
3-Error |
Can't initialize Credentials server |
Internal problems with initializing ports for the Credentials server |
ios-callmgr |
"Make sure the Credentials server port is available on the local machine." |
|
CTLPROVIDERSERV-3-NOMEM |
3-Error |
Can't initialize memory for Credentials server |
Insufficient Memory for Credentials server |
ios-callmgr |
"Increase amount of available memory" |
|
CTLPROVIDERSERV-3-NOPROC |
3-Error |
Could not start Credentials Server |
Internal Problem in process creation |
ios-callmgr |
"None" |
|
CTLPROVIDERSERV-3-NOSOCKETS |
3-Error |
Max Number of Credentials Server sockets exceeded |
There are too many Credentials clients requesting service |
ios-callmgr |
"Reduce number of Credentials requesting service" |
|
CTOKEN-3-INITFAIL |
3-Error |
Initialization of Consent Token facility failed [chars]. |
An unexpected condition has occurred which resulted in Consent Token facility failing to start. This is a serious problem and means that Consent Token facility will not be functional. |
iosxe-ct-lib |
LOG_STD_ACTION |
|
CTOKEN-3-REQPROCFAIL |
3-Error |
Consent Token Request Processing facility failed [chars]. |
An unexpected condition has occurred which resulted in Consent Token facility failing to process a request. This means that some part of Consent Token facility will not be functional. |
iosxe-ct-lib |
LOG_STD_ACTION |
|
CTOKEN-6-AUTH_UPDATE |
6-Information |
Consent Token Update [chars]. |
Consent Token authentication state change update |
iosxe-ct-lib |
LOG_STD_NO_ACTION |
|
CTRC-3-APPCERROR |
3-Error |
[chars] |
An APPC error occurred. ctrc uses APPC API calls to\n\ SNASW to communicate with the remote database server. |
ctrc |
"This usually indicates a problem in the SNA network. Try the ctrc\n\ ping command to test connectivity to the remote database server. If\n\ the ctrc ping fails check the status of the SNA link to the\n\ remote database server with the show snasw link command. If the link\n\ is active try stopping and starting the link. If the problem persists\n\ contact your SNA network administrator for help in troubleshooting. " LOG_STD_RECUR_ACTION " If possible also provide the output of the debug ctrc appc\n\ command and an SNA line trace between the router and the remote\n\ database server for the period during which this message appeared." |
|
CTRC-3-APPCVERB |
3-Error |
Unexpected APPC error: opcode %04x primary code %04x secondary code %08lx |
An unexpected APPC error occurred. ctrc uses APPC API calls to\n\ SNASW to communicate with the remote database server. Opcode\n\ identifies the APPC API call that received the error. Primary and\n\ secondary return codes are returned by the APPC API. |
ctrc |
"This usually indicates a problem in the SNA network. Try the ctrc\n\ ping command to test connectivity to the remote database server. If\n\ the ctrc ping fails check the status of the SNA link to the\n\ remote database server with the show snasw link command. If the link\n\ is active try stopping and starting the link. If the problem persists\n\ contact your SNA network administrator for help in troubleshooting. " LOG_STD_RECUR_ACTION " If possible also provide the output of the debug ctrc appc\n\ command and an SNA line trace between the router and the remote\n\ database server for the period during which this message appeared." |
|
CTRC-3-NOBUFFS |
3-Error |
No buffers available to [chars] |
CTRC attempted to allocate a buffer while performing the \n\ operation described in the message text. A buffer pool does \n\ not contain enough items to satisfy the allocation request. |
ctrc |
"This problem most commonly occurs whenever a public buffer \n\ pool runs out of elements. Determine the which pool has run\n\ out of buffers using the \"show buffers\" command. Adjust the\n\ pool size using the buffers configuration command." |
|
CTRC-3-SNASWNOTSTARTED |
3-Error |
SNASW is not started -- unable to connect to remote database. |
A client connected to a ctrc server but ctrc was unable to\n\ connect out to the remote database because SNASW is not started.\n\ ctrc uses SNASW to connect to the remote database server. You\n\ must start SNASW before ctrc clients attempt to connect. |
ctrc |
"Start SNASW and retry the client connection." |
|
CTRC-3-SNASWSTOPPED |
3-Error |
SNASW was stopped -- existing connections have been closed. |
SNASW was stopped while ctrc connections were open. Stopping\n\ SNASW caused all open SNA connections to the remote database\n\ server to be lost. As a result all client connections were\n\ disconnected. You should not stop SNASW while there are open\n\ ctrc connections. |
ctrc |
"Restart SNASW. Disconnected clients must reconnect." |
|
CTRC-4-APPCWARN |
4-Warning |
[chars] |
An APPC error occurred. ctrc uses APPC API calls to\n\ SNASW to communicate with the remote database server. |
ctrc |
"This usually indicates a temporary problem in the SNA network. Try the ctrc\n\ ping command to test connectivity to the remote database server. If\n\ the ctrc ping fails check the status of the SNA link to the\n\ remote database server with the show snasw link command. If the link\n\ is active try stopping and starting the link. If the problem persists\n\ contact your SNA network administrator for help in troubleshooting. " LOG_STD_RECUR_ACTION " If possible also provide the output of the debug ctrc appc\n\ command and an SNA line trace between the router and the remote\n\ database server for the period during which this message appeared." |
|
CTS_PD-2-IPC_FAILURE |
2-Critical |
CTS-IPC message [chars] handler failed rc [dec] |
An IPC message handler for the CTS feature failed. This will cause the feature to not function. |
asr1k-cts |
LOG_STD_ACTION |
|
CTS_PD-3-FEAT_CTX_DOWN |
3-Error |
CTS-Invalid request [chars] [dec] while context is down |
While the feature context was not active an invalid request was received from another layer of the CTS software stack. |
asr1k-cts |
LOG_STD_RECUR_ACTION |
|
CTS_PD-3-FEAT_DOWN |
3-Error |
CTS-Invalid request [chars] [dec] while feature is down |
While the feature was not active an invalid request was received from another layer of the CTS software stack. |
asr1k-cts |
LOG_STD_RECUR_ACTION |
|
CTS_PD-3-IPC_INIT_FAILED |
3-Error |
CTS-IPC message handler registration failure rc [dec] |
Registering an IPC message handler for the CTS feature failed. This will cause the feature to not function. |
asr1k-cts |
LOG_STD_ACTION |
|
CTS_PD-3-IPC_INVALID_MSG |
3-Error |
CTS-Invalid request [dec] |
We received an invalid message from another layer of the CTS software stack. |
asr1k-cts |
LOG_STD_RECUR_ACTION |
|
CTS_PD-3-IPC_INVALID_MSG_LEN |
3-Error |
CTS-Invalid IPC length [dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Invalid IPC message length |
asr1k-cts |
LOG_STD_ACTION |
|
CTS_PD-3-IPC_NORES |
3-Error |
CTS-No space for the IPC reply size [dec] request [dec] |
For a request from upper CTS software stack layers it was not possible to allocate space for a reply for the specified size. |
asr1k-cts |
LOG_STD_RECUR_ACTION |
|
CTS_PD-3-IPC_OPEN_REPLY |
3-Error |
CTS-IPC Open Reply failed request [dec] |
For a request from upper CTS software stack layers it was not possible to open the reply buffer. |
asr1k-cts |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
CTS_PD-3-IPC_SEND_FAILED |
3-Error |
CTS-IPC [chars] [dec] send failed [dec] |
IPC message send failure |
asr1k-cts |
LOG_STD_ACTION |
|
CTS-0-AUTHZ_OUT_OF_MEM |
0-Emergency |
[chars] failed to create [chars] due to insufficient memory |
The system is experiencing insufficent memory. |
- |
LOG_STD_ACTION |
|
CTS-0-AUTHZ_OUT_OF_MEM |
0-Emergency |
[chars] failed to create [chars] due to insufficient memory |
The system is experiencing insufficent memory. |
- |
LOG_STD_ACTION |
|
CTS-0-CTS_EMERG |
0-Emergency |
[chars] |
CTS_INTERNAL_ERROR |
CTS_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CTS-0-IFC_OUT_OF_MEM |
0-Emergency |
[chars] failed to create [chars] due to insufficient memory |
The system is experiencing insufficent memory. |
- |
LOG_STD_ACTION |
|
CTS-1-CTS_ALERT |
1-Alert |
[chars] |
CTS_INTERNAL_ERROR |
CTS_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CTS-1-CTS_CRED_ACTION_NEEDED |
1-Alert |
CTS credentials are missing or inconsistent in the redundant keystore.\n Please re-configure cts credentials or execute cts change-password. |
A redundant keystore was detected as either not containing any CTS credentials or having a different set of credentials as contained in the active keystore. This means that CTS authentication will fail upon switchover unless remedial action is taken before then. Either use the \cts credentials ...\ CLI to re-configure the CTS device-id and password or use the \cts change-password ...\ CLI to initiate a password change with the AAA server. Either of these actions will cause the device-id and password to be inserted in both the active and redundant keystores. |
- |
- |
|
CTS-1-CTS_CRED_ACTION_NEEDED |
1-Alert |
CTS credentials are missing or inconsistent in the redundant keystore.\n Please re-configure cts credentials or execute cts change-password. |
A redundant keystore was detected as either not containing any CTS credentials or having a different set of credentials as contained in the active keystore. This means that CTS authentication will fail upon switchover unless remedial action is taken before then. Either use the \cts credentials ...\ CLI to re-configure the CTS device-id and password or use the \cts change-password ...\ CLI to initiate a password change with the AAA server. Either of these actions will cause the device-id and password to be inserted in both the active and redundant keystores. |
- |
- |
|
CTS-1-SXP_BINDING_EXP |
1-Alert |
Binding [chars]<[chars] [chars]> can't be expanded. Expanded [dec] and maximum allowed is [dec]\n Binding propagated in the network is not consistent. |
SXP expasion exceed maximum allowed.\n Binding propagated in the network is not consistent.\n User should remove the subnet binding. |
CTS_DDTS_COMPONENT |
"Remove this subnet if possible" |
|
CTS-2-AUTHZ_POLICY_SGACL_ACE_FAILED |
2-Critical |
Failed to [chars][chars] SGACL '[chars]' for SGT=[chars] due to ACE '[chars]' error. Download will be retried in 60 seconds |
An error occurred in the ACE while CTS attempted to acquire SGACL policy from the policy server. Retry will be attempted in 60 seconds |
- |
LOG_STD_ACTION |
|
CTS-2-CACHE_FILE_CHUNK_ALLOC_FAILURE |
2-Critical |
Failed to allocate memory for CTS Cache Filename chunks. |
Failed to allocate memory for CTS Cache Filename chunks This is an indicator of a critical memory issue. |
- |
LOG_STD_ACTION |
|
CTS-2-CTS_CRIT |
2-Critical |
[chars] |
CTS_INTERNAL_ERROR |
CTS_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CTS-2-FIPS_SW_POST_FAIL |
2-Critical |
Software crypto POST Failure |
One or more power-up software crypto algorithmic known answer tests have failed. |
- |
LOG_STD_ACTION |
|
CTS-3-AAA_NO_CONTEXT |
3-Error |
Failed to retrieve AAA context to construct AAA attribute for RADIUS request |
CTS AAA Request Add : Failed to retrieve AAA context to construct AAA attribute for RADIUS request |
- |
LOG_STD_ACTION |
|
CTS-3-AAA_NO_CONTEXT |
3-Error |
Failed to retrieve AAA context to construct AAA attribute for RADIUS request |
CTS AAA Request Add : Failed to retrieve AAA context to construct AAA attribute for RADIUS request |
- |
LOG_STD_ACTION |
|
CTS-3-AAA_NO_RADIUS_SERVER |
3-Error |
No RADIUS servers available for CTS AAA request for [chars] |
CTS AAA Request Setup : No RADIUS servers available for CTS AAA |
- |
LOG_STD_ACTION |
|
CTS-3-AAA_NO_RADIUS_SERVER |
3-Error |
No RADIUS servers available for CTS AAA request for [chars] |
CTS AAA Request Setup : No RADIUS servers available for CTS AAA |
- |
LOG_STD_ACTION |
|
CTS-3-ACL_UNCONFIGURED |
3-Error |
Access-list [chars] has been dynamically unconfigured from CTS policy because it has been [chars]. |
An access-list configured as defining CTS L3 traffic or exemption policy has been deleted or modified so that it can no longer be used for defining CTS policy. It has therefore been removed from the CTS layer3 policy configuration. |
- |
- |
|
CTS-3-AUTHZ_ACL_INFO_STALE |
3-Error |
ACL information is not valid. |
An error occurred while CTS attempted to access ACL information with invalid handle. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_ACL_LIST_STALE |
3-Error |
ACL named list having ACE information is not valid. |
An error occurred while CTS attempted to access ACL list with invalid handle. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_ADD_DATA_FAILED |
3-Error |
[chars] failed to add [chars] to [chars] |
An error occurred while CTS Authz attempted to build its database. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_ADD_DATA_FAILED |
3-Error |
[chars] failed to add [chars] to [chars] |
An error occurred while CTS Authz attempted to build its database. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_CACHE_MSGT_WRITE_FAIL |
3-Error |
[chars] failed to write Multicast SGT Table to cache file[chars] |
CTS Cache: Failed to write Multicast SGT Table to cache file |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_CACHE_MSGT_WRITE_FAIL |
3-Error |
[chars] failed to write Multicast SGT Table to cache file[chars] |
CTS Cache: Failed to write Multicast SGT Table to cache file |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_CACHE_OPEN_FAIL |
3-Error |
[chars] failed to open cache file[chars] for read |
CTS Cache read: Failed to open cache file for read |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_CACHE_OPEN_FAIL |
3-Error |
[chars] failed to open cache file[chars] for read |
CTS Cache read: Failed to open cache file for read |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_CACHE_OPEN_WRITE_FAIL |
3-Error |
[chars] failed to open cache file[chars] for write |
CTS Cache: Failed to open cache file for write |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_CACHE_OPEN_WRITE_FAIL |
3-Error |
[chars] failed to open cache file[chars] for write |
CTS Cache: Failed to open cache file for write |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_CACHE_PEER_POL_WRITE_FAIL |
3-Error |
Failed to write peer policy to cache |
CTS Authz Cache: Failed to write peer policy to cache |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_CACHE_PEER_POL_WRITE_FAIL |
3-Error |
Failed to write peer policy to cache |
CTS Authz Cache: Failed to write peer policy to cache |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_CACHE_READ_FAIL |
3-Error |
[chars] failed to read from cache file[chars] |
CTS Cache: Failed to read from cache file |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_CACHE_READ_FAIL |
3-Error |
[chars] failed to read from cache file[chars] |
CTS Cache: Failed to read from cache file |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_CACHE_SGT_POL_WRITE_FAIL |
3-Error |
Failed to write SGT policy to cache |
CTS Authz Cache: Failed to write SGT policy to cache |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_CACHE_SGT_POL_WRITE_FAIL |
3-Error |
Failed to write SGT policy to cache |
CTS Authz Cache: Failed to write SGT policy to cache |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_CACHE_SGT_WRITE_FAIL |
3-Error |
[chars] failed to write SGT SG Name Table to cache file[chars] |
CTS Cache: Failed to write SGT SG Name Table to cache file |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_CACHE_SGT_WRITE_FAIL |
3-Error |
[chars] failed to write SGT SG Name Table to cache file[chars] |
CTS Cache: Failed to write SGT SG Name Table to cache file |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_CACHE_SRV_WRITE_FAIL |
3-Error |
[chars] failed to write server list to cache file[chars] |
CTS Cache: Failed to write server list to cache file |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_CACHE_SRV_WRITE_FAIL |
3-Error |
[chars] failed to write server list to cache file[chars] |
CTS Cache: Failed to write server list to cache file |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_CACHED_DATA_READ_FAIL |
3-Error |
[chars] failed to read cached data |
CTS Cache: Failed to read cached data |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_CACHED_DATA_READ_FAIL |
3-Error |
[chars] failed to read cached data |
CTS Cache: Failed to read cached data |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_DATA_CREATE_FAILED |
3-Error |
[chars] failed to create [chars] |
An error occurred while CTS Authz attempts to create an internal data structure. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_DATA_CREATE_FAILED |
3-Error |
[chars] failed to create [chars] |
An error occurred while CTS Authz attempts to create an internal data structure. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_DATA_EXCEEDS_LIMIT |
3-Error |
[chars] encountered [chars][dec] exceeds max[dec] |
Data exceeds maximum limits allowed. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_DATA_EXCEEDS_LIMIT |
3-Error |
[chars] encountered [chars][dec] exceeds max[dec] |
Data exceeds maximum limits allowed. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_DATA_FAILED |
3-Error |
[chars] failed to obtain [chars] |
An error occurred while CTS Authz attempted to get/create a data structure |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_DATA_FAILED |
3-Error |
[chars] failed to obtain [chars] |
An error occurred while CTS Authz attempted to get/create a data structure |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_DATA_NULL |
3-Error |
[chars] encounters NULL [chars] |
An unexpected NULL pointer/data is encountered. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_DATA_NULL |
3-Error |
[chars] encounters NULL [chars] |
An unexpected NULL pointer/data is encountered. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_DATA_UNINIT |
3-Error |
[chars] appears uninitialized |
CTS Authz unexpectedly encountered an unitialized data |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_DATA_UNINIT |
3-Error |
[chars] appears uninitialized |
CTS Authz unexpectedly encountered an unitialized data |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_ENTRY_HTTP_FAILED |
3-Error |
Policy Acquisition failed to transmit HTTP request for peer[chars] sgt[chars] |
Policy acquisition failed to transmit HTTP request |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_ENTRY_RADIUS_FAILED |
3-Error |
Policy Acquisition failed to transmit RADIUS request for peer[chars] sgt[chars] |
- |
- |
- |
|
CTS-3-AUTHZ_ENTRY_RADIUS_FAILED |
3-Error |
Policy Acquisition failed to transmit RADIUS request for peer[chars] sgt[chars] |
- |
- |
- |
|
CTS-3-AUTHZ_FAILED_SYNC_RCV |
3-Error |
Standby failed receive sync msg[chars] |
An error occcured while the Standby is receiving sync data from the Active. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_FAILED_SYNC_RCV |
3-Error |
Standby failed receive sync msg[chars] |
An error occcured while the Standby is receiving sync data from the Active. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_GENERIC_FAILURE |
3-Error |
[chars] [chars] |
CTS Authz encountered internal error. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_GENERIC_FAILURE |
3-Error |
[chars] [chars] |
CTS Authz encountered internal error. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_INVALID_DATA |
3-Error |
[chars] encountered invalid [chars] |
CTS Authz encountered an unexpected invalid data type. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_INVALID_DATA |
3-Error |
[chars] encountered invalid [chars] |
CTS Authz encountered an unexpected invalid data type. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_NOT_SUPPORTED |
3-Error |
[chars] encountered [chars] not unsupported |
CTS encountered an unsupported data type or feature. This could be due to incompatibility |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_NOT_SUPPORTED |
3-Error |
[chars] encountered [chars] not unsupported |
CTS encountered an unsupported data type or feature. This could be due to incompatibility |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_POLICY_ACL_DEL_FAILED |
3-Error |
Failed to delete ACL information. Invalid ACL [chars]. |
An error occurred while CTS attempted to delete ACL info with invalid handle. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_POLICY_FAIL_TO_REMOVE |
3-Error |
Failed to remove [chars] policy from the authorization dbase |
An error occured while CTS attempted to remove the specified policy from its database. This could result in an action not being accomplished. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_POLICY_FAIL_TO_REMOVE |
3-Error |
Failed to remove [chars] policy from the authorization dbase |
An error occured while CTS attempted to remove the specified policy from its database. This could result in an action not being accomplished. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_POLICY_INGRESS_FAILED |
3-Error |
Failed to [chars] Ingress policy for [chars] |
An error occurred while CTS attempted to acquire or install an Ingress policy from the ACS. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_POLICY_INGRESS_FAILED |
3-Error |
Failed to [chars] Ingress policy for [chars] |
An error occurred while CTS attempted to acquire or install an Ingress policy from the ACS. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_POLICY_INTERNAL_FAILED |
3-Error |
Failed to acquire/install policy for [chars] due to internal error |
An error occurred while CTS attempted to acquire/install a policy which may be caused by internal software error |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_POLICY_INTERNAL_FAILED |
3-Error |
Failed to acquire/install policy for [chars] due to internal error |
An error occurred while CTS attempted to acquire/install a policy which may be caused by internal software error |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_POLICY_PEER_DOWNLOAD_FAILED |
3-Error |
Failed to download peer policy for [chars] |
An error occurred while CTS attempted to acquire peer policy from the policy server |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_POLICY_PEER_DOWNLOAD_FAILED |
3-Error |
Failed to download peer policy for [chars] |
An error occurred while CTS attempted to acquire peer policy from the policy server |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_POLICY_SGACL_ACE_FAILED |
3-Error |
Failed to [chars][chars] SGACL '[chars]' for SGT=[chars] due to ACE '[chars]' error |
An error occurred in the ACE while CTS attempted to acquire SGACL policy from the policy server. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_POLICY_SGACL_FAILED |
3-Error |
Failed to [chars][chars] SGACL [chars] for SGT=[chars] |
An error occurred while CTS attempted to acquire SGACL policy from the policy server. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_POLICY_SGACL_FAILED |
3-Error |
Failed to [chars][chars] SGACL [chars] for SGT=[chars] |
An error occurred while CTS attempted to acquire SGACL policy from the policy server. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_POLICY_WILDCARD_FAILED |
3-Error |
Failed to download default/unknown policy |
An error occurred while CTS attempted to acquire wildcard policy from the ACS. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_POLICY_WILDCARD_FAILED |
3-Error |
Failed to download default/unknown policy |
An error occurred while CTS attempted to acquire wildcard policy from the ACS. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_SESSION_SM_START_FAILED |
3-Error |
Failed to initialize the environment-data module |
Failed to initialize the environment-data module |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_SESSION_SM_START_FAILED |
3-Error |
Failed to initialize the environment-data module |
Failed to initialize the environment-data module |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_SESSION_UNINST_SGACL_FAILED |
3-Error |
Failed to detach session handle from SGACL list for sgt[chars] |
- |
- |
- |
|
CTS-3-AUTHZ_SESSION_UNINST_SGACL_FAILED |
3-Error |
Failed to detach session handle from SGACL list for sgt[chars] |
- |
- |
- |
|
CTS-3-AUTHZ_SGT_POLICY_DEL_FAILED |
3-Error |
Failed to delete sgt policy for sgt [chars]. |
An error occurred while CTS attempted to delete sgt policy with invalid handle. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_SGT_POLICY_STALE |
3-Error |
sgt policy for sgt '[chars]' is not valid. |
An error occurred while CTS attempted to access sgt policy with invalid handle. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_SM_FAILED |
3-Error |
Failed to start the authorization entry state machine to start policy acquisition for peer[chars] |
- |
- |
- |
|
CTS-3-AUTHZ_SM_FAILED |
3-Error |
Failed to start the authorization entry state machine to start policy acquisition for peer[chars] |
- |
- |
- |
|
CTS-3-AUTHZ_SYNC_FAILED |
3-Error |
Failed to send [chars] sync msg[chars] to Standby |
An error occcured while CTS Authz is performing a sync to the Standby. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_SYNC_FAILED |
3-Error |
Failed to send [chars] sync msg[chars] to Standby |
An error occcured while CTS Authz is performing a sync to the Standby. |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_TREE_MAP_INSERT_FAILED |
3-Error |
Failed to insert the authz entry info into tree map for peer[chars] |
- |
- |
- |
|
CTS-3-AUTHZ_TREE_MAP_INSERT_FAILED |
3-Error |
Failed to insert the authz entry info into tree map for peer[chars] |
- |
- |
- |
|
CTS-3-AUTHZ_UNINST_SESSION_FR_NAMELIST_FAILED |
3-Error |
Failed to locate named list to uninstall session |
Failed to locate named list to uninstall session |
- |
LOG_STD_ACTION |
|
CTS-3-AUTHZ_UNINST_SESSION_FR_NAMELIST_FAILED |
3-Error |
Failed to locate named list to uninstall session |
Failed to locate named list to uninstall session |
- |
LOG_STD_ACTION |
|
CTS-3-CACHE_FILE_OPEN_FAILED |
3-Error |
Failed to open cache file: [chars] error: [chars] |
Cache file could not be opened for read CTS cache functionality will not work as expected. |
- |
LOG_STD_ACTION |
|
CTS-3-CACHE_INVALID_DIRECTORY_PATH |
3-Error |
Cache Invalid Directory Path: [chars] exceeds maximum allowed length [dec] |
Cache invalid directory path. Cache file will not be opened for read/write and CTS cache functionality will not work as expected. |
- |
_ACTION |
|
CTS-3-CACHE_INVALID_IFS |
3-Error |
Cache Invalid IFS: Error opening [chars] - [chars] |
Failure in validating file system. Cache file will not be opened for read/write and CTS cache functionality will not work as expected. |
- |
LOG_STD_ACTION |
|
CTS-3-CACHE_READ_BAD_FILE_MAGIC |
3-Error |
Cache read failed due to bad file magic. |
Cache read failed due to bad file magic. CTS cache functionality will not work as expected. |
- |
LOG_STD_ACTION |
|
CTS-3-CACHE_READ_CRC_ERROR |
3-Error |
Cache read failed due to mismatch in CRC - file CRC[hec] calculated CRC[hec] |
- |
- |
- |
|
CTS-3-CACHE_READ_FILE_HEADER_ERROR |
3-Error |
Cache read of file [chars] failed due to file header error. |
Cache read failed due to file header error. CTS cache functionality will not work as expected. |
- |
LOG_STD_ACTION |
|
CTS-3-CAP_INVALID_SIZE |
3-Error |
CTS HA empty tlv size. |
Received empty tlv list during capability negotiation. |
CTS_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CTS-3-CAP_NOT_COMPATIBLE |
3-Error |
CTS HA capability not compatible |
CTS HA failed during capability negotiation. |
CTS_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CTS-3-CHKPT_REG_FAIL |
3-Error |
CTS HA add CTS checkpoint client failure. |
CTS HA failed to add checkpoint client. No CTS data will be synced to Standby in this case. |
CTS_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CTS-3-CORE_PROCESS_CREATION_FAILURE |
3-Error |
Failed to create CTS_CORE process |
CTS_CORE: Failed to create CTS_CORE process |
- |
LOG_STD_ACTION |
|
CTS-3-CORE_PROCESS_TERMINATED |
3-Error |
Process getting killed since queue is not created |
CTS_CORE: Process getting killed since queue is not created |
- |
LOG_STD_ACTION |
|
CTS-3-CTS_DISALLOW_L2_CONFIG |
3-Error |
[chars].\nRemoving CTS Layer2 configuration from interface[chars] |
- |
- |
- |
|
CTS-3-CTS_DISALLOW_L3_CONFIG |
3-Error |
[chars].\nRemoving CTS Layer3 TrustSec Forwarding configuration from interface[chars] |
Platform ASIC does not support CTS Layer2 and CTS layer3 TrustSec Forwarding configurations to co-exist on the same ASIC instance |
- |
LOG_STD_ACTION |
|
CTS-3-CTS_ERR |
3-Error |
[chars] |
CTS_INTERNAL_ERROR |
CTS_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CTS-3-CTS_POLICY_SERVER_CREDENTIALS |
3-Error |
Valid Policy-server credentials have not configured on device |
CTS policy-server username is not configured |
- |
LOG_STD_ACTION |
|
CTS-3-CTS_POLICY_SERVER_ENCRYPT_REVERSIBLE |
3-Error |
Password conversion failed |
CTS policy-server password conversion failed |
- |
LOG_STD_ACTION |
|
CTS-3-CTS_POLICY_SERVER_ENCRYPT_TEMP |
3-Error |
Password conversion failed |
CTS policy-server password conversion failed |
- |
LOG_STD_ACTION |
|
CTS-3-CTS_POLICY_SERVER_INVALID_CREDENTIALS |
3-Error |
Invalid Policy-server credentials have configured on device OR Server port number is incorrect |
CTS policy-server username or password are invalid |
- |
LOG_STD_ACTION |
|
CTS-3-CTS_POLICY_SERVER_SG_TBL_ALLOC |
3-Error |
Server group table memory allocation failed |
CTS HTTP based download will impact |
- |
LOG_STD_ACTION |
|
CTS-3-DOT1X_FORCE_PORT_AUTHORIZED_FAILED |
3-Error |
Failed to force dot1x port authorized for int[chars] |
An error occcured while CTS attempts to force dot1x port authorized on a CTS link |
- |
LOG_STD_ACTION |
|
CTS-3-DOT1X_UNCONFIGURE_FAILURE |
3-Error |
Failed to unconfigure dot1x on int[chars] |
CTS_CORE: Failed to unconfigure dot1x |
- |
LOG_STD_ACTION |
|
CTS-3-ENTROPY_SRC_FAILURE |
3-Error |
Entropy source failed health test |
The periodic health tests done on the CTR-DRBG crypto implementation indicated an error in obtaining entropy. Recommended action is to crash. |
- |
- |
|
CTS-3-ENV_DATA_ERROR |
3-Error |
Environment data error in [chars] state |
ENV data error |
- |
LOG_STD_NO_ACTION |
|
CTS-3-ENV_DATA_ERROR |
3-Error |
Environment data error in [chars] state |
ENV data error |
- |
LOG_STD_NO_ACTION |
|
CTS-3-ENV_DATA_INIT_FAILED |
3-Error |
Failed to initialize and start the authorization state machine |
Failed to initialize and start the authorization state machine |
- |
LOG_STD_ACTION |
|
CTS-3-ENV_DATA_INIT_FAILED |
3-Error |
Failed to initialize and start the authorization state machine |
Failed to initialize and start the authorization state machine |
- |
LOG_STD_ACTION |
|
CTS-3-FIPS_SW_SEND_POST_RESULT_FAIL |
3-Error |
Software crypto POST FAIL SCP message send failed |
Power-up crypto software algorithmic tests have failed and the SCP message |
- |
LOG_STD_ACTION |
|
CTS-3-GCM_NO_LICENSE |
3-Error |
CTS link [chars] is being shut down: please install MACSec Encryption License http:/www.cisco.com/go/license |
A MACSec Encryption License is required to use gcm-encryption on secure links. All CTS links configured to run gcm-encryption will be held in administratively down state until the gcm-encrytion is removed from the interface configuration or until a MACSec Encryption License is installed. |
- |
"Either install a MACSec Encryption License or configure all CTS " "interfaces with cipher modelists that do not include gcm." |
|
CTS-3-GENERIC_FAILURE |
3-Error |
[chars] [chars] |
CTS Core encountered internal error. |
- |
LOG_STD_ACTION |
|
CTS-3-GET_BUFFER |
3-Error |
CTS HA ISSU client failed to get buffer for message. Error: [dec] [chars] |
The CTS HA 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. |
CTS_DDTS_COMPONENT |
"show logging and show checkpoint client" |
|
CTS-3-GLOBAL_DOT1X_DISABLED |
3-Error |
Global dot1x config is currently disabled - CTS will not run |
Global dot1x is not enabled and hence CTS will not run |
- |
LOG_STD_ACTION |
|
CTS-3-IFC_ADD_SUPPLICANT_FAIL |
3-Error |
Failed to add supplicant cannot open port[chars] |
- |
- |
- |
|
CTS-3-IFC_CACHE_BAD_LEN |
3-Error |
Cache File [chars] bad length [dec] expecting [dec] |
IFC Cache file bad length may be corrupted. |
- |
LOG_STD_ACTION |
|
CTS-3-IFC_CACHE_RESTORE_FAIL |
3-Error |
Cache Restoration Failed |
IFC Cache restoration failed owing to errors in NVRAM file open operation. Even though CTS cache is enabled link bring up cannot bypass IFC state machine |
- |
LOG_STD_ACTION |
|
CTS-3-IFC_CACHE_UPDATE_FAIL |
3-Error |
Cache Update Failed |
IFC Cache update failed owing to errors in NVRAM file write operation. |
- |
LOG_STD_ACTION |
|
CTS-3-IFC_DATA_DESC_ENCODE_FAILED |
3-Error |
[chars] failed to encode the data-descriptor for int[chars] |
An error occured while the system attempted to encode the swidb into the data-descriptor |
- |
LOG_STD_ACTION |
|
CTS-3-IFC_DATA_NULL |
3-Error |
[chars] encounters NULL [chars] |
An unexpected NULL pointer/data is encountered. |
- |
LOG_STD_ACTION |
|
CTS-3-IFC_FAIL_PRGM_PSGT |
3-Error |
Could not program hardware for propagate SGT Port SGT[dec] |
IFC could not program hardware for propagate SGT |
- |
LOG_STD_ACTION |
|
CTS-3-IFC_FAILED_AUTHC_SUCCESS_NOTIFY |
3-Error |
Failed to send authentication success to the core for int[chars] |
- |
- |
- |
|
CTS-3-IFC_FAILED_AUTHZ_FAIL_NOTIFY |
3-Error |
Failed to send authorization failure to the core for int[chars] |
- |
- |
- |
|
CTS-3-IFC_FAILED_AUTHZ_SUCCESS_NOTIFY |
3-Error |
Failed to send authorization success to the core for int[chars] |
- |
- |
- |
|
CTS-3-IFC_FAILED_DISCONNECT_NOTIFY |
3-Error |
Failed to send disconnect notify to the core for int[chars] |
- |
- |
- |
|
CTS-3-IFC_FAILED_ENV_DATA_DNLD |
3-Error |
Failed to download environment data for int[chars] |
- |
- |
- |
|
CTS-3-IFC_FAILED_SAP_FAIL_NOTIFY |
3-Error |
Failed to send SAP failure to the core for int[chars] |
- |
- |
- |
|
CTS-3-IFC_FAILED_SAP_SUCCESS_NOTIFY |
3-Error |
Failed to send SAP success to the core for int[chars] |
- |
- |
- |
|
CTS-3-IFC_LINK_OBJ_FAILED |
3-Error |
[chars] failed to get link_obj for int[chars] |
An error occured while CTS IFC attempts to access the link object. |
- |
LOG_STD_ACTION |
|
CTS-3-IFC_LOST_AUTHC_REAUTH_TIMER_CXT |
3-Error |
Lost AUTHC reauth timer context |
IFC Lost AUTHC reauth timer context |
- |
LOG_STD_ACTION |
|
CTS-3-IFC_LOST_DOT1X_PAE_TIMER_CXT |
3-Error |
Lost DOT1x PAE timer context |
IFC Lost DOT1x PAE timer context |
- |
LOG_STD_ACTION |
|
CTS-3-IFC_LOST_SOCK_CLEANUP_TIMER_CXT |
3-Error |
Lost socket cleanup timer context |
IFC Lost socket cleanup timer context |
- |
LOG_STD_ACTION |
|
CTS-3-IFC_LOST_TIMER_CXT |
3-Error |
Lost Timer context |
IFC Lost Timer context |
- |
LOG_STD_ACTION |
|
CTS-3-IFC_NO_IDB_IN_AUTHORIZE_STATE |
3-Error |
Authorization State: IDB could not be retrieved: state[chars] peer[chars] |
- |
- |
- |
|
CTS-3-IFC_NO_IDB_IN_SAP_STATE |
3-Error |
SAP State: IDB could not be retrieved |
IFC SAP State: IDB could not be retrieved |
- |
LOG_STD_ACTION |
|
CTS-3-IFC_NO_IDB_IN_SWACT |
3-Error |
Failed to locate IDB in link object |
Failed to locate IDB in link object |
- |
LOG_STD_ACTION |
|
CTS-3-IFC_RX_AUTHC_SUCCESS_FAIL |
3-Error |
Received AUTHC Success for peer[chars] role[chars] int[chars] |
IFC Received AUTHC success but failed to process due to error |
- |
LOG_STD_ACTION |
|
CTS-3-IFC_SM_INIT_FAIL |
3-Error |
SM INIT failed |
IFC SM INIT failed |
- |
LOG_STD_ACTION |
|
CTS-3-IFC_SYNC_FAILED |
3-Error |
Failed to send [chars] sync msg[chars] to Standby |
An error occcured while CTS IFC is performing a sync to the Standby. |
- |
LOG_STD_ACTION |
|
CTS-3-IFC_SYNC_FAILED_2 |
3-Error |
[chars] Failed to send [chars] sync msg[chars] to Standby |
An error occcured while CTS IFC is performing a sync to the Standby. |
- |
LOG_STD_ACTION |
|
CTS-3-INIT |
3-Error |
CTS HA ISSU client initialization failed to [chars]. Error: [dec] [chars] |
CTS HA 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. |
CTS_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CTS-3-INVALID_ACL |
3-Error |
Access-list [chars] invalid for CTS policy: [chars]. |
An access-list configured as defining CTS L3 traffic or exemption policy cannot be used because of the specified reason. |
- |
- |
|
CTS-3-INVALID_CTS_OPER_MODE |
3-Error |
Invalid CTS Mode. Supported modes are Manual and Auto |
Invalid CTS Mode. Supported modes are manual and auto |
- |
LOG_STD_ACTION |
|
CTS-3-INVALID_MSGID_RCV |
3-Error |
[chars] received invalid HA/ISSU msgId[dec] |
CTS Core encountered an unexpected invalid HA/ISSU message ID. |
- |
LOG_STD_ACTION |
|
CTS-3-LSC_CA_STORE_FAIL |
3-Error |
Failed to install certificate of CA that issued our locally-significant certificate |
An error occurred while installing the certificate of our issuing CA. When this error occurs the locally-significant certificate will be discarded and CTS will continue to use its password credentials for authentication. |
- |
- |
|
CTS-3-LSC_CA_STORE_FAIL |
3-Error |
Failed to install certificate of CA that issued our locally-significant certificate |
An error occurred while installing the certificate of our issuing CA. When this error occurs the locally-significant certificate will be discarded and CTS will continue to use its password credentials for authentication. |
- |
- |
|
CTS-3-LSC_ENROLL_FAIL |
3-Error |
Failed to set re-enrollment attributes for CTS locally-significant certificate. |
An error occurred while setting the re-enrollment attributes for the new CTS certificate. When this error occurs the new certificate will be discarded and CTS will continue to use its password credentials for authentication. |
- |
- |
|
CTS-3-LSC_ENROLL_FAIL |
3-Error |
Failed to set re-enrollment attributes for CTS locally-significant certificate. |
An error occurred while setting the re-enrollment attributes for the new CTS certificate. When this error occurs the new certificate will be discarded and CTS will continue to use its password credentials for authentication. |
- |
- |
|
CTS-3-LSC_STORE_FAIL |
3-Error |
Failed to install newly-provisioned locally-significant certificate. |
An error occurred while installing our locally significant certificate to be used for CTS. This means that we cannot be authenticated using a certificate. If a CTS password is available we will continue to authenticate using the password. |
- |
- |
|
CTS-3-LSC_STORE_FAIL |
3-Error |
Failed to install newly-provisioned locally-significant certificate. |
An error occurred while installing our locally significant certificate to be used for CTS. This means that we cannot be authenticated using a certificate. If a CTS password is available we will continue to authenticate using the password. |
- |
- |
|
CTS-3-MODE_LIST_CKSUM_ERROR |
3-Error |
CTS SAP mode-list checksum failure on interface [chars].\n |
CTS SAP mode-list checksum failure has been detected on this interafce which could provide crypto services. This event may be caused by memory corruption occuring in the interface configutration or the memory area has been illegally modified. It may also be caused by software defects. As a result of this event the system has been forced to reload. |
- |
LOG_STD_ACTION |
|
CTS-3-MSG_NOT_COMPATIBLE_WITH_PEER |
3-Error |
Message [dec] in component [dec] is not compatible with the peer. |
Message not compatible with the peer. |
CTS_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CTS-3-PAC_PROVI_FAIL |
3-Error |
PAC Provisioning failed for [inet] |
PAC Provisioning failed |
- |
LOG_STD_ACTION |
|
CTS-3-PAC_PROVI_FAIL |
3-Error |
PAC Provisioning failed for [inet] |
PAC Provisioning failed |
- |
LOG_STD_ACTION |
|
CTS-3-POLICY_COA_RBACL_FAILED |
3-Error |
Failed to complete request for update-rbacl[chars]-[chars] |
An error occurred while CTS attempted to service a Change of Authorization request for the update-rbacl command |
- |
LOG_STD_ACTION |
|
CTS-3-POLICY_COA_RBACL_FAILED |
3-Error |
Failed to complete request for update-rbacl[chars]-[chars] |
An error occurred while CTS attempted to service a Change of Authorization request for the update-rbacl command |
- |
LOG_STD_ACTION |
|
CTS-3-POLICY_COA_SGT_FAILED |
3-Error |
Failed to complete CoA request for update-sgt[chars] |
An error occurred while CTS attempted to service a Change of Authorization request for the update-sgt command |
- |
LOG_STD_ACTION |
|
CTS-3-POLICY_COA_SGT_FAILED |
3-Error |
Failed to complete CoA request for update-sgt[chars] |
An error occurred while CTS attempted to service a Change of Authorization request for the update-sgt command |
- |
LOG_STD_ACTION |
|
CTS-3-POLICY_HA_PROC_FAIL |
3-Error |
Error starting up HA switchover Policy refresh process. |
A failure has occurred in switchover which has prevented the policy refresh process to be lauched. User should manually refresh policies via the \cts refresh policy\ commad |
- |
"Issue command \"cts refresh policy\" and verify policy timers" " are active If timers do not start "LOG_STD_ACTION |
|
CTS-3-POLICY_HA_PROC_FAIL |
3-Error |
Error starting up HA switchover Policy refresh process. |
A failure has occurred in switchover which has prevented the policy refresh process to be lauched. User should manually refresh policies via the \cts refresh policy\ commad |
- |
"Issue command \"cts refresh policy\" and verify policy timers" " are active If timers do not start "LOG_STD_ACTION |
|
CTS-3-POLICY_INSTALL_FAIL |
3-Error |
An error occurred while trying to program the hardware error code [dec] |
An error occurred while trying to program the hardware to implement the configured policy. |
- |
- |
|
CTS-3-PORT_AUTHORIZED_FAILED |
3-Error |
Failed to authorize Port for int[chars] |
Port failed to be authorized on a CTS link |
- |
LOG_STD_ACTION |
|
CTS-3-RECEIVE_FAILED |
3-Error |
CTS HA failed to process message recieved from Active device. CTS component Id [dec] message Id [dec] max header size [dec] size [dec] max message size [dec]. |
CTS HA client on Standby device failed to process checkpoint message. CTS state between the active device and the Standby device is not identical. |
CTS_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CTS-3-ROOT_CA_STORE_FAIL |
3-Error |
Could not install the CTS trusted-root certificate. |
An error occcured while installing the CTS trusted-root certificate. This means that CTS cannot validate AAA servers' certifcates received during EAP-FAST exchanges. |
- |
- |
|
CTS-3-ROOT_CA_STORE_FAIL |
3-Error |
Could not install the CTS trusted-root certificate. |
An error occcured while installing the CTS trusted-root certificate. This means that CTS cannot validate AAA servers' certifcates received during EAP-FAST exchanges. |
- |
- |
|
CTS-3-SAP_CIPHER_MISMATCH |
3-Error |
Cipher suite mismatch from peer on int[chars] |
SAP cipher list mismatch on the interface configured with CTS SAP. Both ends of the CTS SAP link must have matching Cipher list |
- |
LOG_STD_ACTION |
|
CTS-3-SAP_MANUAL_PMKID_MISMATCH |
3-Error |
PMKID Mismatch on int[chars] received: %08x %08x %08x %08x |
The PMKID received from peer is different from the expected PMKID |
- |
LOG_STD_ACTION |
|
CTS-3-SAP_NEG_VERSION_MISMATCH |
3-Error |
SAP negotiation error for int[chars] - Received message 2 with higher |
SAP negotiation error - peer's version higher than local version |
- |
LOG_STD_NO_ACTION |
|
CTS-3-SAP_NIST_RNG_FAILED |
3-Error |
Failed to obtain random number from CTR-DRBG block for SAP key-counter. Number of consecutive failures[dec] |
The system failed to obtain a random number for the SAP key counter which causes SAP session failure |
- |
LOG_STD_ACTION |
|
CTS-3-SEND_FAILED |
3-Error |
CTS HA failed to send checkpoint message. CTS component Id [dec] message Id [dec] header size [dec] max header size [dec] message size [dec] max size [dec]. |
The CTS HA client failed to send a checkpoint CTS state between the active device and the standby device is not identical. |
CTS_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CTS-3-SEND_MSG_TO_CORE_FAILED |
3-Error |
Failed to send msg[dec] to core process |
An error occcured while CTS attempts to send a message event to the core process |
- |
LOG_STD_ACTION |
|
CTS-3-SEND_NEGO_FAILED |
3-Error |
CTS HA ISSU client failed to send negotiation message. Error: [dec] [chars] |
The CTS HA 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. |
CTS_DDTS_COMPONENT |
"show logging and show checkpoint client" |
|
CTS-3-SESSION_REGISTRY |
3-Error |
CTS HA ISSU client failed to register session information. Error: [dec] [chars] |
The CTS HA ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
CTS_DDTS_COMPONENT |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
CTS-3-SESSION_UNREGISTRY |
3-Error |
CTS HA ISSU client failed to unregister session information. Error: [dec] [chars] |
The CTS HA ISSU client failed to unregister session information. |
CTS_DDTS_COMPONENT |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
CTS-3-SSO_NO_LICENSE |
3-Error |
CTS GCM links are being shut down. Please install a MACSec Encryption License on the new active supervisor http:/www.cisco.com/go/license |
A MACSec Encryption License is required to use gcm-encryption on secure links. If the active supervisor has a license but the standby does not then links may run GCM encryption. However on switchover all links running GCM will be shut down because the new active does not have a License. |
- |
LOG_STD_DDTS_TAC_DETAILS |
|
CTS-3-STDBY_NO_LICENSE |
3-Error |
CTS link [chars] may be shut down on switchover: please install MACSec Encryption License on the standby supervisor http:/www.cisco.com/go/license |
A MACSec Encryption License is required to use gcm-encryption on secure links. If the active supervisor has a license but the standby does not then links may run GCM encryption. However on switchover all links running GCM will be shut down because the new active does not have a License. |
- |
"Either install a MACSec Encryption License or configure all CTS " "interfaces with cipher modelists that do not include gcm." |
|
CTS-3-SXP_CONN_STATE_CHG_OFF |
3-Error |
Connection [chars]<[inet] [inet]>-[dec] state changed from [chars] to Off. |
SXP Connection with the specified instance number changed state. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-3-SXP_LISTENER |
3-Error |
Fail to start global listening socket after TCP process restart. |
SXP on this device can not accept SXP connection setup request from the remote devices. |
CTS_DDTS_COMPONENT |
"Disable and enable SXP feature to see if the global" " listening socket can be restarted." |
|
CTS-3-SXP_MSG_PARSE |
3-Error |
Connection [chars]<[inet] [inet]> [chars] |
An error occurred while parsing SXP message. |
CTS_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CTS-3-SXP_NODE_ID_CHG |
3-Error |
SXP Node ID changed from 0x%08X to 0x%08X |
SXP Node ID changed. |
CTS_DDTS_COMPONENT |
"Make sure SXP bindings that use old node ID are removed from the binding database in all SXP nodes before the new node ID is used." |
|
CTS-4-CREATE_SLIST_FAILED |
4-Warning |
[chars]: Failed to create server list. |
CTS HA failed to create server list while processing server named list sync message. |
CTS_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CTS-4-CREATE_SLIST_FAILED |
4-Warning |
[chars]: Failed to create server list. |
CTS HA failed to create server list while processing server named list sync message. |
CTS_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CTS-4-CTS_WARNING |
4-Warning |
[chars] |
CTS_INTERNAL_ERROR |
CTS_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CTS-4-IFC_RX_AUTHC_FAIL |
4-Warning |
Received AUTHC FAIL for role[chars] int[chars] |
IFC Received AUTHC FAIL |
- |
LOG_STD_ACTION |
|
CTS-4-IFC_RX_AUTHC_LOGOFF |
4-Warning |
Received AUTHC LOGOFF for peer[chars] role[chars] int[chars] state[chars] |
- |
- |
- |
|
CTS-4-IFC_RX_AUTHC_NO_RESP |
4-Warning |
Received AUTHC NO RESP for int[chars] |
IFC Received AUTHC NO RESP |
- |
LOG_STD_ACTION |
|
CTS-4-IFC_RX_AUTHC_REJECT |
4-Warning |
Received AUTHC REJECT for peer[chars] role[chars] int[chars] |
- |
- |
- |
|
CTS-4-INT_ERR |
4-Warning |
[chars] |
CTS_INTERNAL_ERROR |
CTS_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CTS-4-NO_PROV_SECRET |
4-Warning |
No shared secret available for provisioning PAC from server [inet]. |
We are unable to provision or reprovision a CTS PAC because we do not have a configured RADIUS shared secret for the server and there are no valid unexpired PACs that can be used to secure the re-provisioning exchange. |
- |
- |
|
CTS-4-NO_PROV_SECRET |
4-Warning |
No shared secret available for provisioning PAC from server [inet]. |
We are unable to provision or reprovision a CTS PAC because we do not have a configured RADIUS shared secret for the server and there are no valid unexpired PACs that can be used to secure the re-provisioning exchange. |
- |
- |
|
CTS-4-SLIST_ADD_TO_NAMED_LIST_FAILED |
4-Warning |
[chars]:tag[chars] - failed to add server[inet]:[dec] to named list. |
- |
- |
- |
|
CTS-4-SLIST_ADD_TO_NAMED_LIST_FAILED |
4-Warning |
[chars]:tag[chars] - failed to add server[inet]:[dec] to named list. |
- |
- |
- |
|
CTS-4-SLIST_ADD_TO_PREFERRED_LIST_FAILED |
4-Warning |
[chars]:tag[chars] - failed to add server[inet]:[dec] to preferred list. |
- |
- |
- |
|
CTS-4-SLIST_ADD_TO_PREFERRED_LIST_FAILED |
4-Warning |
[chars]:tag[chars] - failed to add server[inet]:[dec] to preferred list. |
- |
- |
- |
|
CTS-4-SLIST_HANDLER_FAILED |
4-Warning |
[chars]:tag[chars] - failed to locate server list handle. |
- |
- |
- |
|
CTS-4-SLIST_HANDLER_FAILED |
4-Warning |
[chars]:tag[chars] - failed to locate server list handle. |
- |
- |
- |
|
CTS-4-SLIST_INVALID_LIST_TYPE |
4-Warning |
[chars]:tag[chars] - invalid server list type[dec]. |
- |
- |
- |
|
CTS-4-SLIST_INVALID_LIST_TYPE |
4-Warning |
[chars]:tag[chars] - invalid server list type[dec]. |
- |
- |
- |
|
CTS-4-SXP_INTERNAL |
4-Warning |
CTS SXP [chars] |
The CTS SXP system encountered internal failure. |
CTS_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CTS-4-SXP_STALE_NODE_ID_CFG |
4-Warning |
Interface configuration is changed may cause adverse affect on SXP functionality |
Change in interface configuration causing device to hold stale SXP Node ID. |
CTS_DDTS_COMPONENT |
"Make sure to re-configure SXP Node ID." |
|
CTS-4-SXP_STALE_NODE_ID_GEN |
4-Warning |
Interface configuration is changed may cause adverse affect on SXP functionality |
Change in interface configuration causing device to hold stale SXP Node ID. |
CTS_DDTS_COMPONENT |
"Make sure to disable and then enable SXP global feature." |
|
CTS-5-CTS_NOTICE |
5-Notice |
[chars] |
Normal but significant conditions |
CTS_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CTS-5-DOT1X_CONFIG_FAILED |
5-Notice |
Failed to configure dot1x for int[chars] |
An error occcured while CTS attempts to configure dot1x for a CTS link |
- |
LOG_STD_ACTION |
|
CTS-5-DOT1X_INIT_FAILED |
5-Notice |
Failed to initialize dot1x for int[chars] |
An error occcured while CTS attempts to initialize dot1x for a CTS link |
- |
LOG_STD_ACTION |
|
CTS-5-DOT1X_PAE_FAILED |
5-Notice |
Failed to [chars] dot1x PAE[chars] for int[chars] |
An error occcured while CTS attempts to start/stop dot1x PAEs for |
- |
LOG_STD_ACTION |
|
CTS-5-ENV_DATA_ACQUISITION_SUCCESS |
5-Notice |
Environment data download success |
Environment data download completed |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-5-ENV_DATA_ACQUISITION_SUCCESS |
5-Notice |
Environment data download success |
Environment data download completed |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-5-ENV_DATA_INSTALL_SUCCESS |
5-Notice |
Environment data installation success |
Environment data installation completed |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-5-ENV_DATA_INSTALL_SUCCESS |
5-Notice |
Environment data installation success |
Environment data installation completed |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-5-IFC_DATA_DESC_DECODE_FAILED |
5-Notice |
[chars] failed to decode the data-descriptor - swidb unknown |
An error occured while the system attempted to decode the data-descriptor in order to obtain the swidb |
- |
LOG_STD_ACTION |
|
CTS-5-PASSWORD_CHANGE_ONE |
5-Notice |
CTS password in the keystore has been renamed \[chars]\. |
An MSCHAPv2 change-password sequence has been successfully executed and the old password is being renamed for fallback use. This is the first of a 2-part operation. Next the new password will be renamed to become the active password. |
- |
- |
|
CTS-5-PASSWORD_CHANGE_ONE |
5-Notice |
CTS password in the keystore has been renamed \[chars]\. |
An MSCHAPv2 change-password sequence has been successfully executed and the old password is being renamed for fallback use. This is the first of a 2-part operation. Next the new password will be renamed to become the active password. |
- |
- |
|
CTS-5-PASSWORD_CHANGE_TWO |
5-Notice |
A new CTS password has been installed as \[chars]\ in the keystore. |
A new CTS password has been installed in the keystore following a successful MSCHAPv2 change-password sequence. The old password has been saved for fallback use. |
- |
- |
|
CTS-5-PASSWORD_CHANGE_TWO |
5-Notice |
A new CTS password has been installed as \[chars]\ in the keystore. |
A new CTS password has been installed in the keystore following a successful MSCHAPv2 change-password sequence. The old password has been saved for fallback use. |
- |
- |
|
CTS-5-POLICY_ACQUISITION_SUCCESS |
5-Notice |
Policy Acquisition success for peer[chars] sgt[chars] |
- |
- |
- |
|
CTS-5-POLICY_ACQUISITION_SUCCESS |
5-Notice |
Policy Acquisition success for peer[chars] sgt[chars] |
- |
- |
- |
|
CTS-5-ROOT_CA_STORE_DONE |
5-Notice |
A trusted-root certificate to be used for CTS has been installed. |
A CTS trusted-root certificate was received from a AAA server during an EAP-FAST enrollment. This certificate will be used for validating all AAA servers' certificates received from here on. |
- |
- |
|
CTS-5-ROOT_CA_STORE_DONE |
5-Notice |
A trusted-root certificate to be used for CTS has been installed. |
A CTS trusted-root certificate was received from a AAA server during an EAP-FAST enrollment. This certificate will be used for validating all AAA servers' certificates received from here on. |
- |
- |
|
CTS-5-SXP_BINDING_ADD |
5-Notice |
Binding [chars]<[chars] [chars]>-<[inet] [dec]> added to SXP database. |
Binding added to the SXP database. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-5-SXP_BINDING_CHG |
5-Notice |
Binding [chars]<[chars] [chars]>-<[inet] [dec]> changed: old connection instance number:[dec] old sgt:[chars]. |
Binding changed in the SXP database. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-5-SXP_BINDING_CONFLICT |
5-Notice |
Binding [chars]<[chars] [chars]> from peer [inet] change to new sgt [chars] from peer [inet] |
SXP received conflicting sgt value from different SXP peer for the same IP prefix. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-5-SXP_BINDING_DEL |
5-Notice |
Binding [chars]<[chars] [chars]>-<[inet] [dec]> deleted in SXP database. |
Binding deleted in the SXP database. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-5-SXP_BINDING_FWD |
5-Notice |
Binding [chars]<[chars] [chars]>-<[inet] [dec]> is forwarded to the peer. |
SXP forwarded binding to the peer. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-5-SXP_BINDING_REQ |
5-Notice |
SXP received binding forwarding request [chars] binding [chars]<[chars] [chars]>. |
SXP received a binding forwarding request. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-5-SXP_BINDING_UPD |
5-Notice |
Binding [chars]<[chars] [chars]> [chars]. Update binding manager. |
SXP updated binding manager with the binding change. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-5-SXP_DFT_KEYCHAIN_CHANGE |
5-Notice |
CTS SXP key-chain changed. |
The SXP system key-chain has been changed. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-5-SXP_DFT_PASSWORD_CHANGE |
5-Notice |
CTS SXP password changed. |
The SXP system password has been changed. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-5-SXP_DFT_SRCIP_CHG |
5-Notice |
SXP default source IP is changed [inet] --> [inet]. |
SXP default source IP is changed on this device. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-5-SXP_FILTER_COUNT_REACHED_MAX |
5-Notice |
Reached maximum filter count. Could not add new filter |
SXP Filter count on the box reached the maximum. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-5-SXP_FILTER_COUNT_UPPER_THRESHOLD |
5-Notice |
CTS SXP filter rules exceed [[dec]%%] threshold. Reached count of [dec] out of [dec] |
SXP Filter count on the box exceeded upper threshold. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-5-SXP_FILTER_RULE_COUNT_REACHED_MAX |
5-Notice |
Reached maximum filter rules. Could not add new rule in filter [chars] |
SXP Filter rule count on the box reached the maximum. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-5-SXP_FILTER_RULE_COUNT_UPPER_THRESHOLD |
5-Notice |
CTS SXP filter rules exceed [[dec]%%] threshold. Reached count of [dec] out of [dec] in filter [chars]. |
SXP Filter rule count on the box exceeded upper threshold. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-5-SXP_STATE_CHANGE |
5-Notice |
CTS SXP [chars] |
The SXP feature has changed operational state. SXP feature is functioning only when the feature is enabled. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-5-SXP_VRF_DEL |
5-Notice |
SXP Connection <[inet] [inet]> configuration in VRF:[chars] is removed. |
A VRF is removed the connections configured in this VRF should be removed. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-6-AUTHZ_CACHE_READ_RESULT |
6-Information |
[chars] cache read from file[chars] [chars] |
CTS Cache read from cache file done |
- |
LOG_STD_ACTION |
|
CTS-6-AUTHZ_CACHE_READ_RESULT |
6-Information |
[chars] cache read from file[chars] [chars] |
CTS Cache read from cache file done |
- |
LOG_STD_ACTION |
|
CTS-6-AUTHZ_CACHED_DATA_EXPIRED |
6-Information |
[chars] cached data expired |
CTS Cache: Cached data expired |
- |
LOG_STD_ACTION |
|
CTS-6-AUTHZ_CACHED_DATA_EXPIRED |
6-Information |
[chars] cached data expired |
CTS Cache: Cached data expired |
- |
LOG_STD_ACTION |
|
CTS-6-AUTHZ_ENTRY_ACCESS_POLICY_STATE |
6-Information |
Policy Acquisition in ACCESS state for peer[chars] sgt[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_ENTRY_ACCESS_POLICY_STATE |
6-Information |
Policy Acquisition in ACCESS state for peer[chars] sgt[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_ENTRY_COMPLETE_STATE |
6-Information |
Policy Acquisition in COMPLETE state for peer[chars] sgt[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_ENTRY_COMPLETE_STATE |
6-Information |
Policy Acquisition in COMPLETE state for peer[chars] sgt[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_POLICY_INSTALL_STATE |
6-Information |
Policy Installation in [chars] state for int[chars] peer[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_POLICY_INSTALL_STATE |
6-Information |
Policy Installation in [chars] state for int[chars] peer[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_POLICY_INSTALL_SUCCESS |
6-Information |
Policy Installation success for int[chars] peer[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_POLICY_INSTALL_SUCCESS |
6-Information |
Policy Installation success for int[chars] peer[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_POLICY_NO_OP |
6-Information |
Policy Installation in [chars] state for int[chars] peer[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_POLICY_NO_OP |
6-Information |
Policy Installation in [chars] state for int[chars] peer[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_POLICY_SGACL_ATTACH_SUCCESS |
6-Information |
Successfully attached RBM SGACL to RBM policy for sgt[chars]:[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_POLICY_SGACL_ATTACH_SUCCESS |
6-Information |
Successfully attached RBM SGACL to RBM policy for sgt[chars]:[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_POLICY_SGACL_NO_CHANGE |
6-Information |
Policy refresh for sgt[chars] indicates no change |
- |
- |
- |
|
CTS-6-AUTHZ_POLICY_SGACL_NO_CHANGE |
6-Information |
Policy refresh for sgt[chars] indicates no change |
- |
- |
- |
|
CTS-6-AUTHZ_POLICY_SGACL_SUCCESS |
6-Information |
Successfully [chars] SGACL for sgt[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_POLICY_SGACL_SUCCESS |
6-Information |
Successfully [chars] SGACL for sgt[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_POLICY_SGACL_UPDATE |
6-Information |
SGACL[chars]gen-id[chars] updated to SGACL[chars]gen-id[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_POLICY_SGACL_UPDATE |
6-Information |
SGACL[chars]gen-id[chars] updated to SGACL[chars]gen-id[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_POLICY_UNINSTALL_SUCCESS_STATE |
6-Information |
Policy Installation in [chars] state for int[chars] peer[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_POLICY_UNINSTALL_SUCCESS_STATE |
6-Information |
Policy Installation in [chars] state for int[chars] peer[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_POLICY_UPDATED |
6-Information |
Policy update received for old SGT [chars] new SGT[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_POLICY_UPDATED |
6-Information |
Policy update received for old SGT [chars] new SGT[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_POLICY_WAIT_FOR_RBM_STATE |
6-Information |
Policy Installation in [chars] state for int[chars] peer[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_POLICY_WAIT_FOR_RBM_STATE |
6-Information |
Policy Installation in [chars] state for int[chars] peer[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_REFRESH_EXPIRY |
6-Information |
Policy refresh timer[dec] secs has expired for peer[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_REFRESH_EXPIRY |
6-Information |
Policy refresh timer[dec] secs has expired for peer[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_SM_DESTROY |
6-Information |
Policy Installation state machine destroyed in [chars] state for int[chars] peer[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_SM_DESTROY |
6-Information |
Policy Installation state machine destroyed in [chars] state for int[chars] peer[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_SM_INIT |
6-Information |
Policy Installation state machine initializing in [chars] state for int[chars] peer[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_SM_INIT |
6-Information |
Policy Installation state machine initializing in [chars] state for int[chars] peer[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_SM_REINIT |
6-Information |
Policy Installation state machine reinitialization for int[chars] peer[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_SM_REINIT |
6-Information |
Policy Installation state machine reinitialization for int[chars] peer[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_SM_RETRY_INSTALL |
6-Information |
Policy Installation retry install for int[chars] peer[chars] flag[hec] |
- |
- |
- |
|
CTS-6-AUTHZ_SM_RETRY_INSTALL |
6-Information |
Policy Installation retry install for int[chars] peer[chars] flag[hec] |
- |
- |
- |
|
CTS-6-AUTHZ_SM_RUN |
6-Information |
Policy Installation state machine running for int[chars] peer[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_SM_RUN |
6-Information |
Policy Installation state machine running for int[chars] peer[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_SM_STOP |
6-Information |
Policy Installation state machine stopped for int[chars] peer[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_SM_STOP |
6-Information |
Policy Installation state machine stopped for int[chars] peer[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_WAIT_POLICY_STATE |
6-Information |
Policy Installation in [chars] state for int[chars] peer[chars] |
- |
- |
- |
|
CTS-6-AUTHZ_WAIT_POLICY_STATE |
6-Information |
Policy Installation in [chars] state for int[chars] peer[chars] |
- |
- |
- |
|
CTS-6-CRTCL_AUTH_DISABLE |
6-Information |
Critical-Authentication disabled on interface[chars] |
CTS critical-authentication is disabled on given interface |
- |
LOG_STD_NO_ACTION |
|
CTS-6-CRTCL_AUTH_ENABLE |
6-Information |
Critical-Authentication enabled on interface[chars] |
CTS critical-autentication is enabled on given interface |
- |
LOG_STD_NO_ACTION |
|
CTS-6-CRTCL_AUTH_REAUTH |
6-Information |
Critical-Authentication starts re-authentication on interface[chars] |
CTS critical-authentication re-authenticates peer on given interface |
- |
LOG_STD_NO_ACTION |
|
CTS-6-CTS_INFO |
6-Information |
[chars] |
Informational messages |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-6-DOT1X_FORCE_PORT_AUTHORIZED_SUCCESS |
6-Information |
Successfully forced dot1x port authorized for int[chars] |
Port has been put to FORCE AUTHORIZED on a CTS link |
- |
LOG_STD_ACTION |
|
CTS-6-DOT1X_PAE_CONFIG |
6-Information |
[chars] dot1x PAE[chars] for int[chars] |
The interface has been configured for dot1x PAEs |
- |
LOG_STD_ACTION |
|
CTS-6-DOT1X_PEER_LOGOFF |
6-Information |
DOT1X reported peer LOGOFF message on int[chars] |
DOT1X reported peer LOGOFF message |
- |
LOG_STD_NO_ACTION |
|
CTS-6-DOT1X_PEER_NO_RESP |
6-Information |
DOT1X reported peer NO RESPONSE message on int[chars] |
DOT1X reported peer NO RESPONSE message |
- |
LOG_STD_NO_ACTION |
|
CTS-6-ENV_DATA_ASSESS_STATE |
6-Information |
Environment Data Download in assess state |
Environment data download in assess state |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-6-ENV_DATA_ASSESS_STATE |
6-Information |
Environment Data Download in assess state |
Environment data download in assess state |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-6-ENV_DATA_CLEAR_SUCCESS |
6-Information |
Environment data successfully cleared. |
Environment data successfully cleared. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-6-ENV_DATA_COA_REQUEST |
6-Information |
Command [chars]=[chars]-[chars] |
A Change of Authorization request command is received for update-env-data |
- |
LOG_STD_ACTION |
|
CTS-6-ENV_DATA_REFRESH_TIMER |
6-Information |
Time to refresh environment data |
ENV data refresh timer |
- |
LOG_STD_NO_ACTION |
|
CTS-6-ENV_DATA_REFRESH_TIMER |
6-Information |
Time to refresh environment data |
ENV data refresh timer |
- |
LOG_STD_NO_ACTION |
|
CTS-6-ENV_DATA_START_STATE |
6-Information |
Environment Data Download in start state |
Environment data download in start state |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-6-ENV_DATA_START_STATE |
6-Information |
Environment Data Download in start state |
Environment data download in start state |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-6-ENV_DATA_WAIT_RESP_STATE |
6-Information |
Environment Data Download in wait response state |
Environment data download in wait response state |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-6-ENV_DATA_WAIT_RESP_STATE |
6-Information |
Environment Data Download in wait response state |
Environment data download in wait response state |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-6-FIPS_SW_POST_PASS |
6-Information |
Software crypto POST PASS |
All power-up software crypto algorithmic known answer tests have passed. |
- |
LOG_STD_NO_ACTION |
|
CTS-6-HA_ENV_DATA_STALE |
6-Information |
CTS HA environment-data sync failed. Old environment-data is stale. |
The CTS HA environment-data sync to standby failed. CTS environment download could be in progress and old data is stale. |
- |
LOG_STD_NO_ACTION |
|
CTS-6-IFC_AUTHC_STATE |
6-Information |
Interface Controller in AUTHENTICATION state for int[chars] |
IFC Entering Authentication State |
- |
LOG_STD_NO_ACTION |
|
CTS-6-IFC_AUTHORIZE_STATE |
6-Information |
Interface Controller in AUTHORIZATION state [chars] for int[chars] peer[chars] |
IFC Entering Authorization State |
- |
LOG_STD_NO_ACTION |
|
CTS-6-IFC_CACHE_APPLIED |
6-Information |
Cache data applied for int[chars] |
Inform the user that the CTS link is brought up using cache data |
- |
LOG_STD_ACTION |
|
CTS-6-IFC_DISCONNECT_STATE |
6-Information |
Interface Controller in DISCONNECT state for int[chars] |
IFC Entering DISCONNECT State |
- |
LOG_STD_NO_ACTION |
|
CTS-6-IFC_HELD_STATE |
6-Information |
Interface Controller in HELD state for int[chars] |
IFC Entering HELD State |
- |
LOG_STD_NO_ACTION |
|
CTS-6-IFC_INIT_STATE |
6-Information |
Interface Controller in INITIALIZATION state for int[chars] |
IFC Entering INIT State |
- |
LOG_STD_NO_ACTION |
|
CTS-6-IFC_LICENSE_ERR_STATE |
6-Information |
Interface Controller in LICENSE ERR state for int[chars] |
IFC Entering LICENSE ERR State |
- |
LOG_STD_NO_ACTION |
|
CTS-6-IFC_OPEN_STATE |
6-Information |
Interface Controller in OPEN state for int[chars] |
IFC Entering OPEN State |
- |
LOG_STD_NO_ACTION |
|
CTS-6-IFC_RX_AUTHC_SUCCESS |
6-Information |
Received AUTHC SUCCESS for peer[chars] role[chars] sgt[chars] int[chars] |
- |
- |
- |
|
CTS-6-IFC_SAP_STATE |
6-Information |
Interface Controller in SAP NEGOTIATION state for int[chars] |
IFC Entering SAP State |
- |
LOG_STD_NO_ACTION |
|
CTS-6-IFC_SM_STATE |
6-Information |
Interface Controller state machine started for int[chars] |
IFC Started |
- |
LOG_STD_NO_ACTION |
|
CTS-6-INCOMPAT |
6-Information |
CTS HA ISSU client negotiation results incompatible |
The CTS HA ISSU client message version is not compatible on Active and Standby. No CTS data will be synced to Standby in this case |
CTS_DDTS_COMPONENT |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
CTS-6-PAC_PROVI_SUCCESS |
6-Information |
PAC Provisioning succeeded for [inet] A-ID=[chars] |
PAC Provisioning succeeded |
- |
LOG_STD_NO_ACTION |
|
CTS-6-PAC_PROVI_SUCCESS |
6-Information |
PAC Provisioning succeeded for [inet] A-ID=[chars] |
PAC Provisioning succeeded |
- |
LOG_STD_NO_ACTION |
|
CTS-6-POLICY_COA_DONE |
6-Information |
Command [chars]=[chars] completed |
A Change of Authorization request has been serviced |
- |
LOG_STD_ACTION |
|
CTS-6-POLICY_COA_DONE |
6-Information |
Command [chars]=[chars] completed |
A Change of Authorization request has been serviced |
- |
LOG_STD_ACTION |
|
CTS-6-POLICY_COA_NO_ACTION |
6-Information |
Command [chars]=[chars] has no change |
A Change of Authorization request has been received but no action was taken due to the system is already in possession of the requested data |
- |
LOG_STD_ACTION |
|
CTS-6-POLICY_COA_NO_ACTION |
6-Information |
Command [chars]=[chars] has no change |
A Change of Authorization request has been received but no action was taken due to the system is already in possession of the requested data |
- |
LOG_STD_ACTION |
|
CTS-6-POLICY_COA_NO_SESSION |
6-Information |
Command [chars]=[chars] has no session associated |
A Change of Authorization request has been received for infomration that the system is not in possession of |
- |
LOG_STD_ACTION |
|
CTS-6-POLICY_COA_NO_SESSION |
6-Information |
Command [chars]=[chars] has no session associated |
A Change of Authorization request has been received for infomration that the system is not in possession of |
- |
LOG_STD_ACTION |
|
CTS-6-POLICY_COA_RBACL_REQUEST |
6-Information |
Command [chars]=[chars]-[chars] |
A Change of Authorization request command is received for update-rbacl |
- |
LOG_STD_ACTION |
|
CTS-6-POLICY_COA_RBACL_REQUEST |
6-Information |
Command [chars]=[chars]-[chars] |
A Change of Authorization request command is received for update-rbacl |
- |
LOG_STD_ACTION |
|
CTS-6-POLICY_COA_SGT_REQUEST |
6-Information |
Command [chars]=[chars] |
A Change of Authorization request command is received for update-sgt |
- |
LOG_STD_ACTION |
|
CTS-6-POLICY_COA_SGT_REQUEST |
6-Information |
Command [chars]=[chars] |
A Change of Authorization request command is received for update-sgt |
- |
LOG_STD_ACTION |
|
CTS-6-POLICY_RBACL_MONITOR_ALL |
6-Information |
Failed to set monitor all for dynamic policies |
An error occurred while CTS attempted to set monitor flag for all dynamic installed policies. |
- |
LOG_STD_ACTION |
|
CTS-6-POLICY_RBACL_MONITOR_ALL |
6-Information |
Failed to set monitor all for dynamic policies |
An error occurred while CTS attempted to set monitor flag for all dynamic installed policies. |
- |
LOG_STD_ACTION |
|
CTS-6-PORT_AUTHORIZED_SUCCESS |
6-Information |
Port authorized for int[chars] |
Port has been authorized on a CTS link |
- |
LOG_STD_ACTION |
|
CTS-6-PORT_UNAUTHORIZED |
6-Information |
Port unauthorized for int[chars] |
Port has been unauthorized on a CTS link |
- |
LOG_STD_ACTION |
|
CTS-6-REAUTH_TIMER_EXPIRED |
6-Information |
Timer expired on int[chars] |
REAUTH Timer expired |
- |
LOG_STD_NO_ACTION |
|
CTS-6-REAUTH_TIMER_EXPIRED |
6-Information |
Timer expired on int[chars] |
REAUTH Timer expired |
- |
LOG_STD_NO_ACTION |
|
CTS-6-REAUTHENTICATION_PERIOD_CHANGED |
6-Information |
Reauthentication period is changed to [dec] |
Reauthentication period is changed while applying configuration change to the link object |
- |
LOG_STD_NO_ACTION |
|
CTS-6-SAP_DOT1X_PMKID_MISMATCH |
6-Information |
PMKID Mismatch on int[chars] received: %08x %08x %08x %08x |
The PMKID received from peer is different from the expected PMKID |
- |
LOG_STD_ACTION |
|
CTS-6-SAP_NEG_DOWNREV |
6-Information |
SAP negotiation for int[chars] switching from version[dec] to peer's version[dec] |
- |
- |
- |
|
CTS-6-SAP_NEG_DOWNREV_RESTART |
6-Information |
SAP negotiation for int[chars] - Received message 2 with lower version[dec] |
SAP negotiation switching to peer's lower version restarting message 1 |
- |
LOG_STD_NO_ACTION |
|
CTS-6-SAP_REKEY_TIMER_EXPIRED |
6-Information |
SAP Rekey Timer Expired for interface[chars] after [dec] |
SAP Rekey Timer Expired. |
- |
LOG_STD_NO_ACTION |
|
CTS-6-SAP_SUCCESS |
6-Information |
SAP Success for int[chars] selected cipher[chars] version[dec] |
- |
- |
- |
|
CTS-6-SXP_BINDING_ERR |
6-Information |
Binding [chars]<[chars] [chars]>-<[inet] [dec]> [chars] |
SXP binding update error. |
CTS_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CTS-6-SXP_CONFIG |
6-Information |
Connection [chars]<[inet][inet]> [chars] |
A SXP configuration error occurred. The connection can not be setup correctly. |
CTS_DDTS_COMPONENT |
"Ensure that the connection configure on both ends" " have the matched mode IP addresses." |
|
CTS-6-SXP_CONN_STATE_CHG |
6-Information |
Connection [chars]<[inet] [inet]>-[dec] state changed from [chars] to [chars]. |
SXP Connection with the specified instance number changed state. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-6-SXP_FILTER_COUNT_CHG |
6-Information |
CTS SXP filter rules exceed [[dec]%%] threshold. Reached count of [dec] out of [dec] |
SXP Filter count on the box changed. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-6-SXP_FILTER_COUNT_LOWER_THRESHOLD |
6-Information |
SXP filter rules dropped below [[dec]%%] threshold. Reached count of [dec] out of [dec] |
SXP Filter count on the box dropped below lower threshold. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-6-SXP_FILTER_RULE_COUNT_CHG |
6-Information |
CTS SXP filter rules exceed [[dec]%%] threshold. Reached count of [dec] out of [dec] in filter [chars]. |
SXP Filter rule count on the box changed. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-6-SXP_FILTER_RULE_COUNT_LOWER_THRESHOLD |
6-Information |
SXP filter rules dropped below [[dec]%%] threshold. Reached count of [dec] out of [dec] in filter [chars]. |
SXP Filter rule count on the box exceeded upper threshold. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-6-SXP_PEER_IP |
6-Information |
Peer IP address [chars] [inet] belongs to this device. |
- |
- |
- |
|
CTS-6-SXP_SRC_IP |
6-Information |
Source IP address [chars] [inet] does not belong to this device. |
- |
- |
- |
|
CTS-6-SXP_TIMER_START |
6-Information |
Connection [chars]<[inet] [inet]> [chars] timer started. |
The specified SXP timer started. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-6-SXP_TIMER_STOP |
6-Information |
Connection [chars]<[inet] [inet]> [chars] timer stopped. |
The specified SXP timer stopped. |
CTS_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
CTS-7-AUTHZ_ENTRY_HDL_SENDL_FAILED |
7-Debug |
Error retrieving the authorization entry handle |
Error retrieving the authorization entry handle |
- |
LOG_STD_ACTION |
|
CTS-7-AUTHZ_ENTRY_HDL_SENDL_FAILED |
7-Debug |
Error retrieving the authorization entry handle |
Error retrieving the authorization entry handle |
- |
LOG_STD_ACTION |
|
CTS-7-AUTHZ_ENTRY_PENDING_REQUEST |
7-Debug |
RADIUS request to acquire policy for peer[chars] sgt[chars] was not |
RADIUS request to acquire policy for peer was not sent due to pending request in progress |
- |
LOG_STD_ACTION |
|
CTS-7-AUTHZ_ENTRY_PENDING_REQUEST |
7-Debug |
RADIUS request to acquire policy for peer[chars] sgt[chars] was not |
RADIUS request to acquire policy for peer was not sent due to pending request in progress |
- |
LOG_STD_ACTION |
|
CTS-7-AUTHZ_ENTRY_WAIT_FOR_ACE |
7-Debug |
Policy Acquisition for peer[chars] sgt[chars] is waiting for the |
Policy acquisition for peer is waiting for the ACE download complete |
- |
LOG_STD_ACTION |
|
CTS-7-AUTHZ_ENTRY_WAIT_FOR_ACE |
7-Debug |
Policy Acquisition for peer[chars] sgt[chars] is waiting for the |
Policy acquisition for peer is waiting for the ACE download complete |
- |
LOG_STD_ACTION |
|
CTS-7-AUTHZ_PEER_POL_DEL |
7-Debug |
Deleting peer policy for peer[chars] sgt[chars] |
- |
- |
- |
|
CTS-7-AUTHZ_PEER_POL_DEL |
7-Debug |
Deleting peer policy for peer[chars] sgt[chars] |
- |
- |
- |
|
CTS-7-AUTHZ_PEER_POL_DEL_PENDING |
7-Debug |
Pending peer policy delete for peer[chars] sgt[chars] due to |
Pending peer policy delete for peer due to outstanding SGACL install/uninstall |
- |
LOG_STD_ACTION |
|
CTS-7-AUTHZ_PEER_POL_DEL_PENDING |
7-Debug |
Pending peer policy delete for peer[chars] sgt[chars] due to |
Pending peer policy delete for peer due to outstanding SGACL install/uninstall |
- |
LOG_STD_ACTION |
|
CTS-7-CTS_ASSERT |
7-Debug |
Assertion Failure [chars] @[chars]:[dec] : [chars] |
CTS_INTERNAL_ERROR |
CTS_DDTS_COMPONENT |
LOG_STD_ACTION |
|
CUBE-3-LICENSING |
3-Error |
[chars] |
CUBE Licensing Enforcement |
ipipgw |
LOG_STD_SH_TECH_ACTION |
|
CUBE-5-LICENSE_INFO |
5-Notice |
[chars] |
Periodic entitlement status |
ipipgw |
LOG_STD_ACTION |
|
CVAC-2-INIT_FAILED |
2-Critical |
Virtual appliance configuration cannot occur: [chars] |
The system was unable to even attempt to apply virtual appliance configuration for the given reason. |
virt-infra |
LOG_STD_SH_TECH_ACTION |
|
CVAC-3-CONFIG_ERROR |
3-Error |
[dec] errors while applying configs generated from file [chars]. |
Out of the generated virtual appliance configuration commands the given number of commands were rejected by the IOSd parser. The indicated log file will describe exactly which commands were rejected as will any accompanying CVAC-4-CLI_FAILURE messages in this log. |
virt-infra |
"Consult the indicated log file for details of the " "errors that were encountered. Also inspect the " "current running-config and startup-config of the " "router using the <CmdBold>show " "running-config<noCmdBold> and <CmdBold>show " "startup-config<noCmdBold> commands in order to " "confirm that the configuration is valid." |
|
CVAC-3-FILE_ERROR |
3-Error |
Could not [chars] file [chars]: [chars] |
The system was unable to perform the indicated operation on the indicated file for the indicated reason |
virt-infra |
"Make sure the given disk is correctly formatted " "and has sufficient free space available." |
|
CVAC-3-XML_ERROR |
3-Error |
Error while parsing XML from file [chars]: error '[chars]' element '[chars]' attribute '[chars]' explanation '[chars]'. File will be saved to [chars] |
The contents of the given file were not correct XML and as a result XML parsing aborted due to the given reason. No new configuration was applied to the router from this file. |
virt-infra |
"Investigate the contents of the saved file " "to determine the cause of the reported error and " "if possible fix the file contents restore it to " "its original location and reload to re-process it. " LOG_STD_RECUR_ACTION |
|
CVAC-4-CLI_FAILURE |
4-Warning |
Configuration command failure: '[chars]' was rejected |
The indicated IOSd configuration command generated by the CVAC subsystem was rejected by the IOSd CLI. Look for a subsequent CVAC-3-CONFIG_ERROR log message which will contain a reference to a logfile containing more information about this failure. |
virt-infra |
"Inspect the log file to determine why the command " "was rejected and how to correct it. If necessary " "manually re-issue the corrected command." |
|
CVAC-4-CONFIG_DONE |
4-Warning |
Configuration generated from file [chars] was applied and saved to NVRAM. See [chars] for more details. |
The generated configuration was applied and the resulting system configuration has been saved to the startup-config in NVRAM. The indicated logfile may contain additional information. |
virt-infra |
LOG_STD_NO_ACTION |
|
CVAC-4-FILE_IGNORED |
4-Warning |
Configuration file [chars] is ignored: [chars] |
The indicated configuration file was ignored and not used for configuration for the given reason. |
virt-infra |
LOG_STD_NO_ACTION |
|
CVAC-4-PROPERTY_IGNORED |
4-Warning |
Property key '[chars]' value '[chars]' ignored: [chars] |
The indicated XML configuration property was ignored for the indicated reason |
virt-infra |
"If the property was not applied due to an invalid " "key or value either change these attributes to " |
|
CVAC-4-WRITE_FAIL |
4-Warning |
Configuration generated from file [chars] was applied but could not be saved to NVRAM. See [chars] for more details. |
The generated configuration was applied but the resulting system configuration was not saved to the startup-config in NVRAM. The indicated logfile may contain additional information. |
virt-infra |
"Issue the write memory command on the IOS CLI" |
|
CVAC-5-XML_PARSED |
5-Notice |
[dec] lines of configuration generated from file [chars] |
The indicated file was successfully parsed to generate IOSd configuration commands. The generated configs have not yet been applied to the system. |
virt-infra |
LOG_STD_NO_ACTION |
|
CVLA_CLIENT-4-CVLA_MEMORY_BOUNDARY_TOUCH_CLEAR |
4-Warning |
CVLA memory utilization has declined below its threshold memory is available for [chars]. |
After CVLA was in memory shortage memory utilization has declined below its threshold New traffic flows will be opened properly |
qfp-cvla |
LOG_STD_ACTION |
|
CVLA_CLIENT-4-CVLA_MEMORY_BOUNDARY_TOUCH_WARN |
4-Warning |
CVLA reached maximum configured memory utilization. Can't allocate more memory for [chars]. |
Because of CVLA memory shortage new flows may not be opened properly |
qfp-cvla |
LOG_STD_ACTION |
|
CVLA_CLIENT-4-SYS_FREE_MEMORY_LOW_WATERMARK_TOUCH_CLEAR |
4-Warning |
System free memory has increased above its lower watermark memory is available for [chars]. |
After system memory was in shortage free memory has increased above its lower watermark New traffic flows will be opened properly |
qfp-cvla |
LOG_STD_ACTION |
|
CVLA_CLIENT-4-SYS_FREE_MEMORY_LOW_WATERMARK_TOUCH_WARN |
4-Warning |
System free memory has reached its lower watermark. Can't allocate more memory for [chars]. |
Because of system memory shortage new flows may not be opened properly |
qfp-cvla |
LOG_STD_ACTION |
|
CVLA-2-IPC_INIT |
2-Critical |
IPC message handler registration failure rc [dec] |
Registering an IPC message handler for the CVLA infra failed. This will cause the infra to not function. |
qfp-cvla |
"This is normally a software issue. " "The consequences are that the CVLA infra will not function. " LOG_STD_ACTION |
|
CVLA-3-FEAUTE_HANDLE_INVALID |
3-Error |
Invalid handle magic 0x[hec] for handle %p |
Internal error Feautre handle contains invalid magic |
cpp-ucode |
LOG_STD_ACTION |
|
CVLA-3-IPC_NORES |
3-Error |
No space for the IPC reply size [dec] |
For a request from upper CVLA software stack layers it was not possible to allocate space for a reply for the specified size. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as infra activation. |
qfp-cvla |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
CVLA-3-IPC_OPEN_REPLY |
3-Error |
IPC Open Reply failed request [dec] |
For a request from upper CVLA software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as infra activation. |
qfp-cvla |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
CWAN_CHOC_DS0-3-CDBFAIL |
3-Error |
Port [dec]/[dec] - fail to create a SONET controller data structure |
The software resource can't be allocated for this hardware |
osm-choc-ds0 |
LOG_STD_ACTION |
|
CWAN_CHOC_DS0-3-CFG_BAD_PARA |
3-Error |
[chars]: invalid config parameter [chars] |
Configuration parameter is invalid |
osm-choc-ds0 |
LOG_STD_ACTION |
|
CWAN_CHOC_DS0-3-IFCONFIG_ERR |
3-Error |
config error on port [dec]/[dec][chars] cmd [dec] [chars] |
A configuration command sent from the system to a linecard failed |
osm-choc-ds0 |
LOG_STD_ACTION |
|
CWAN_CHOC_DS0-3-PORTFAIL |
3-Error |
Port [dec]/[dec] - fail to create a port instance data structure |
The software resource can't be allocated for this hardware |
osm-choc-ds0 |
LOG_STD_ACTION |
|
CWAN_CHOC_DS0-3-RMCTRLR_UNKNOWN |
3-Error |
Slot [dec] - Unknown linecard type [dec] removed |
This hardware can't be recognized by this version of software. |
osm-choc-ds0 |
"Check software version. Make sure the software supports the hardware." |
|
CWAN_CHOC_DS0-3-T1CFG_CCBERROR |
3-Error |
CCB command error cmd [dec] arg [dec] on T1 [dec]/[dec]/[dec] |
A command sent from the system to a linecard failed |
osm-choc-ds0 |
LOG_STD_ACTION |
|
CWAN_CHOC_DS0-3-UNKNOWN_MIB_TYPE |
3-Error |
Unknown MIB type [dec] from slot [dec] |
Draco received unknown communication message from linecard |
osm-choc-ds0 |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CWAN_CHOC_DS0-3-UNKNOWNCTRLR |
3-Error |
Slot [dec] - Unknown linecard type [dec] |
This hardware can't be recognized by this version of software. |
osm-choc-ds0 |
"Check software version. Make sure the software supports the hardware." |
|
CWAN_CHOC_DS0-3-VCCFG_CCBERROR |
3-Error |
CCB command error cmd [dec] arg [dec] on port [dec]/[dec] channel [dec] |
A command sent from the system to a linecard failed |
osm-choc-ds0 |
LOG_STD_ACTION |
|
CWAN_CHOC_DS0-4-ALLOCFAIL |
4-Warning |
Interface [dec]/[dec] allocation failed: [chars] |
required resources unavailable. |
osm-choc-ds0 |
"Either upgrade system memory or reconfigure memory usage." |
|
CWAN_CHOC_DS0-4-CORRUPT |
4-Warning |
[chars] information seems to be corrupted bad value =[dec] |
wrong parameters detected internally |
osm-choc-ds0 |
"This is only a debug warning message. The unexpected value is\n\ discarded." |
|
CWAN_CHOC_DS0-4-IFCONFIG |
4-Warning |
[chars] config error [dec] lc delay:[dec] ms: [chars] |
RP received configuration error from linecard. |
osm-choc-ds0 |
"Reconfigure or shut/no shut the error channel." |
|
CWAN_CHOC_DS0-4-LCLOCK_FAIL |
4-Warning |
Interface [chars] failed to acquire semaphore for LC access: [chars] |
Other process locked the semaphore for too long. |
osm-choc-ds0 |
LOG_STD_ACTION |
|
CWAN_CHOC_DS0-4-PROV_FAIL |
4-Warning |
Interface [chars] provisioning ch[dec] failed: [chars] |
provisioning conflict or resource shortage |
osm-choc-ds0 |
"workaround: under 'controller sonet' do 'no channelized' followed\n\ by 'channelized' twice. If problem persists do a\n\ 'show controller sonet <slot>/<port>' and\n\ 'show controller {pos/serial} <slot>/<port>:<chan>' then contact\n\ cisco technical support representative." |
|
CWAN_CHOC_DS0-4-UNPROV_FAIL |
4-Warning |
Interface [chars] unprovisioning failed: [chars] |
Linecard failed to response unprovisioning command. |
osm-choc-ds0 |
LOG_STD_ACTION |
|
CWAN_CHOC_DS0-4-UNSUP |
4-Warning |
Slot [dec]: Unknown [chars] [dec] |
This value is not recognized by this version of software. |
osm-choc-ds0 |
"Check linecard version. Normally this is harmless but worth contacting\n\ cisco technical support representative." |
|
CWAN_CHOC_DS0-4-WRONG_LL |
4-Warning |
%.16s received wrong loveletter : type=[dec] length=[dec] |
wrong parameters detected internally |
osm-choc-ds0 |
"This is only a debug warning message. The unexpected messages from\n\ linecard is harmlessly discarded." |
|
CWAN_CHOC_DS0-5-LOOPSTATUS |
5-Notice |
[chars] [chars] |
A configurable loopback status. |
- |
LOG_STD_NO_ACTION |
|
CWAN_CHOC_DSX-3-ENQUEUE_FAIL |
3-Error |
[chars] |
cmd enqueue failure |
osm-ct3 for CT3 osm-t3e3 for T3/E3 osm-choc-ds0 for CHOC-12/CHOC-3 |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CWAN_CHOC_DSX-3-INVALID_SUBR_HWIDB |
3-Error |
Invalid Subrate hwidb on T3 [dec]/[dec] |
invalid subrate hwidb |
osm-ct3 for CT3 osm-t3e3 for T3/E3 osm-choc-ds0 for CHOC-12/CHOC-3 |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CWAN_CHOC_DSX-3-NODESTROYSUBBLOCK |
3-Error |
The [chars] subblock named [chars] was not removed |
A software error has occured this message is displayed when\n\ IDB subblocks cannot be removed. |
osm-ct3 for CT3 osm-t3e3 for T3/E3 \n\ osm-choc-ds0 for CHOC-12/CHOC-3 |
LOG_STD_ACTION |
|
CWAN_CHOC_DSX-3-NULLDS3MIBTABLE |
3-Error |
Null DS3 MIB table snmp_if_index [dec] |
System cannot find the DS3 MIB table pointer |
osm-ct3 for CT3 osm-t3e3 for T3/E3 osm-choc-ds0 for CHOC-12/CHOC-3 |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CWAN_CHOC_DSX-3-PROCESS_ERROR |
3-Error |
process error - [chars] |
process encountered fatal error |
osm-ct3 for CT3 osm-t3e3 for T3/E3 osm-choc-ds0 for CHOC-12/CHOC-3 |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CWAN_CHOC_DSX-3-PROCESS_FAIL |
3-Error |
process creation failed for [chars] |
process creation failed for handling cmd |
osm-ct3 for CT3 osm-t3e3 for T3/E3 osm-choc-ds0 for CHOC-12/CHOC-3 |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CWAN_CHOC_DSX-3-SEND_DRIVER_READY |
3-Error |
send driver ready msg failed for [dec] |
IPC message failure |
osm-ct3 for CT3 osm-t3e3 for T3/E3 osm-choc-ds0 for CHOC-12/CHOC-3 |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CWAN_CHOC_DSX-3-T1CFG_ERROR |
3-Error |
T1 [dec]/[dec]/[dec] config command error cmd [dec] arg [dec] retval [dec] |
A command sent from the system to a linecard failed |
osm-ct3 |
LOG_STD_ACTION |
|
CWAN_CHOC_DSX-3-T3CFG_ERROR |
3-Error |
T3 [dec]/[dec] config command error cmd [dec] arg [dec] retval [dec] |
A command sent from the system to a linecard failed |
osm-ct3 |
LOG_STD_ACTION |
|
CWAN_CHOC_DSX-3-UNKNOWN_CTRLR |
3-Error |
Slot [dec] - Unknown linecard type [dec] |
This hardware can't be recognized by this version of software. |
osm-ct3 |
"Check software version. Make sure the software supports the hardware." |
|
CWAN_CHOC_DSX-3-VC_CONFIG_ERR |
3-Error |
[chars] T1 [dec] channel group [dec] of T3 [dec]/[dec] unsuccessful error code [dec] |
channel configuration error |
osm-ct3 for CT3 osm-t3e3 for T3/E3 osm-choc-ds0 for CHOC-12/CHOC-3 |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CWAN_CHOC_DSX-3-VCCFG_ERROR |
3-Error |
VC [dec]/[dec]:[dec] config command error cmd [dec] arg [dec] retval [dec] |
A command sent from the system to a linecard failed |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12 |
LOG_STD_ACTION |
|
CWAN_CHOC_DSX-5-DEF_SUBRATE |
5-Notice |
[chars] [chars] |
Remote subrate configuration changed |
osm-ct3 for CT3 osm-t3e3 for T3/E3 osm-choc-ds0 for CHOC-12/CHOC-3 |
"Inform the network operator that subrate configuration changed by\n\ remote end" |
|
CWAN_CHOC_DSX-5-UNKNOWN_EVENT |
5-Notice |
[chars] |
Unexpected event received by the process |
osm-ct3 for CT3 osm-t3e3 for T3/E3 osm-choc-ds0 for CHOC-12/CHOC-3 |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CWAN_CHOC-4-ALLOCFAIL |
4-Warning |
Interface [dec]/[dec] allocation failed: [chars] |
required resources unavailable. |
osm-choc-ds3 |
"Either upgrade system memory or reconfigure memory usage." |
|
CWAN_CHOC-4-CORRUPT |
4-Warning |
[chars] information seems to be corrupted bad value =[dec] |
wrong parameters detected internally |
osm-choc-ds3 |
"This is only a debug warning message. The unexpected value is\n\ discarded." |
|
CWAN_CHOC-4-IFCONFIG |
4-Warning |
[chars] config error [dec] lc delay:[dec] ms: [chars] |
RP received configuration error from linecard. |
osm-choc-ds3 |
"Reconfigure or shut/no shut the error channel." |
|
CWAN_CHOC-4-LCCFG_MISMATCH |
4-Warning |
LC needs reboot due to config mismatch on [chars] rc=[dec] |
RP detects LC's channel provisioning mismatching start-config |
osm-choc-ds3 |
"reset linecard: hw-module module <slot> reset" |
|
CWAN_CHOC-4-LCLOCK_FAIL |
4-Warning |
Interface [chars] failed to acquire semaphore for LC access: [chars] |
Other process locked the semaphore for too long. |
osm-choc-ds3 |
LOG_STD_ACTION |
|
CWAN_CHOC-4-PROV_FAIL |
4-Warning |
Interface [chars] provisioning ch[dec] failed: [chars] |
provisioning conflict or resource shortage |
osm-choc-ds3 |
"workaround: under 'controller sonet' do 'no channelized' followed\n\ by 'channelized' twice. If problem persists do a\n\ 'show controller sonet <slot>/<port>' and\n\ 'show controller {pos/serial} <slot>/<port>:<chan>' then contact\n\ cisco technical support representative." |
|
CWAN_CHOC-4-UNPROV_FAIL |
4-Warning |
Interface [chars] unprovisioning failed: [chars] |
Linecard failed to response unprovisioning command. |
osm-choc-ds3 |
LOG_STD_ACTION |
|
CWAN_CHOC-4-UNSUP |
4-Warning |
Slot [dec]: Unknown [chars] [dec] |
This value is not recognized by this version of software. |
osm-choc-ds3 |
"Check linecard version. Normally this is harmless but worth contacting\n\ cisco technical support representative." |
|
CWAN_CHOC-4-WRONG_LL |
4-Warning |
%.16s received wrong loveletter : type=[dec] length=[dec] |
wrong parameters detected internally |
osm-choc-ds3 |
"This is only a debug warning message. The unexpected messages from\n\ linecard is harmlessly discarded." |
|
CWAN_CHOC-6-LCDRIVER |
6-Information |
OIR failed: slot [dec] linecard not responding to initial query |
OIR insertion aborted due to failing to contact lc |
osm-choc-ds3 |
LOG_STD_ACTION |
|
CWAN_CHOC-6-WRONG_GULF |
6-Information |
[chars] hardware version gulf v[dec] does not support OC-12 or OC-48 |
Early version of hw asic GULF2.0 and below has bugs in\n\ rx fifo depth which can not handle oc-12 or oc-48 rate.\n\ Either limiting channel provisioning or upgrading hw |
osm-choc-ds3 |
"Limit channel provisioning to DS3 and/or OC3" |
|
CWAN_CONTAINER_ACCESS-5-CWAN_NO_CONTAINER |
5-Notice |
Associated container interface does not exist for [chars] |
The container interface no longer exists for access interface. |
c7600-bb |
LOG_STD_NO_ACTION |
|
CWAN_CONTAINER_ACCESS-5-CWAN_VRF_MISMATCH |
5-Notice |
VRF of [chars] access does not match with [chars] |
VRF of access interface does not match with that of associated container interface. Either container interface is deleted or VRF of container interface is changed |
c7600-bb |
LOG_STD_NO_ACTION |
|
CWAN_HA-3-CCB_INIT_ERROR |
3-Error |
Failed to initialize CCB list for slot [dec]. |
The High Availability component for WAN modules failed to properly initialize state information for the specified slot. |
c7600-ha |
LOG_STD_ACTION |
|
CWAN_HA-3-IFCFG_CMD_NOT_UNIQUE |
3-Error |
More than one command registered for unique-key generator for interface configuration command [dec]. |
The High Availability component for WAN modules is unable to properly synchronize state information for the current configuration due to a conflict in command identifiers. |
c7600-ha |
LOG_STD_ACTION |
|
CWAN_HA-3-IFCFG_INIT_ERROR |
3-Error |
Failed to initialize Interface Configuration list for slot [dec]/[dec]. |
The High Availability component for WAN modules failed to properly initialize state information for the specified slot. |
c7600-ha |
LOG_STD_ACTION |
|
CWAN_HA-3-IFCFG_NO_UNIQUE_KEY |
3-Error |
No unique-key generator registered for interface configuration command [dec]. |
The High Availability component for WAN modules is unable to properly synchronize state information for the current configuration. |
c7600-ha |
LOG_STD_ACTION |
|
CWAN_HA-4-CCB_PLAYBACK_ERROR |
4-Warning |
CCB playback failed for slot [dec]. |
The High Availability component for WAN modules failed to synchronize some new state information for the specified slot. |
c7600-ha |
"Reload the standby supervisor module to force a fresh bulk " "synchronization. If this error recurs " LOG_STD_ACTION |
|
CWAN_HA-4-CCB_RECORD_ERROR |
4-Warning |
CCB record failed for slot [dec]. |
The High Availability component for WAN modules failed to record some new state information for the specified slot. |
c7600-ha |
LOG_STD_ACTION |
|
CWAN_HA-4-IFCFG_DFLT_LIST_ERROR |
4-Warning |
For Interface Configuration command [dec] default retval list search resulted 0x[hec] for slot [dec]/[dec] |
The High Availability component for WAN modules failed to synchronize some new state information for the specified slot. |
c7600-ha |
show platform redundancy \ if-config default-retvals |
|
CWAN_HA-4-IFCFG_PLAYBACK_ERROR |
4-Warning |
Interface Configuration command [dec] playback failed for slot [dec]/[dec]. |
The High Availability component for WAN modules failed to synchronize some new state information for the specified slot. |
c7600-ha |
LOG_STD_ACTION |
|
CWAN_HA-4-IFCFG_RECORD_ERROR |
4-Warning |
Interface Configuration command [dec] record failed for slot [dec]/[dec]. |
The High Availability component for WAN modules failed to record some new state information for the specified slot. |
c7600-ha |
LOG_STD_ACTION |
|
CWAN_HA-4-IFEVENT_BULKSYNCFAIL |
4-Warning |
[chars] ifevent: [dec] error: [dec] |
Failed CWAN if-event bulk sync. |
c7600-ha |
LOG_STD_NO_ACTION |
|
CWAN_HA-4-IFEVENT_INCRSYNCFAIL |
4-Warning |
[chars] for ifevent: [dec] with error: [dec] |
Failed CWAN if-event incremental sync. |
c7600-ha |
LOG_STD_NO_ACTION |
|
CWAN_HA-4-IFEVENT_UNEXPECTED_BULKTYPE |
4-Warning |
Unexpected value for bulk sync type [dec] received. |
Received a unexpected type in bulk sync message. |
c7600-ha |
LOG_STD_NO_ACTION |
|
CWAN_HA-4-LTLSYNCFAIL |
4-Warning |
Failed to sync LTL data during [chars] for [chars] [dec]: slot=[dec]slotunit=[dec] if_num=[dec] to standby vlan=[dec]hash=[dec]ltl=[dec]\n |
Some LTL data did not sync correctly from active to standby RP\n |
c7600-ha |
LOG_STD_ACTION |
|
CWAN_HA-4-NOSRPBULKSYNC |
4-Warning |
Failed to [chars] SRP bulk data slot=[dec] intf=[dec] type=[dec] ret code [dec]\n |
Some SRP-related state information failed to sync correctly from the active RP to the standby RP during the HA bulk-synchronization phase. |
c7600-ha |
LOG_STD_ACTION |
|
CWAN_HA-4-NOSRPSYNC |
4-Warning |
Failed to sync SRP packet slot=[dec]intf=[dec] to standby |
Some SRP-related state information failed to sync correctly from the active RP to the standby RP when the configuration changed. |
c7600-ha |
LOG_STD_ACTION |
|
CWAN_HA-4-SRPSYNC |
4-Warning |
Slot [dec]: [chars]\n |
An error occured while syncing SRP states from active RP to standby RP. |
c7600-ha |
LOG_STD_ACTION |
|
CWAN_RP-1-OVERRIDE_MAC_INVALID |
1-Alert |
[chars] has invalid override-mac-address. |
The user has issued an override-mac-address that does not match the mac address of the MSFC. This can occur if the config has been moved to new hardware or the mac-address command has been used on another interface. while the system automatically corrects this the config needs to be adjusted. |
cwan |
"Modify the override-mac-address command in the config." |
|
CWAN_RP-1-TOO_MANY_VRF |
1-Alert |
Slot [dec] can not support all the VRFs configured! |
A non-Enhanced OSM card has been inserted into a router with more than 511 IP VRFs already configured. This router cannot support more than 511 IP VRFs if there is at least one non-Enhanced OSM in the system. |
cwan |
"Replace the inserted non-Enhanced OSM with " "an Enhanced OSM or decrease the number of " "IP VRFs to 511 or fewer." |
|
CWAN_RP-3-BAD_IFCOMTYPE |
3-Error |
Bad ifcom message type=[dec] |
A WAN module passed down a message that the RP software\n\ was not prepared to handle. |
- |
LOG_STD_ACTION |
|
CWAN_RP-3-BOOTFAIL |
3-Error |
The WAN module in slot [dec]/[dec] failed to boot |
The WAN module in the slot indicated in the error messages \n\ failed to boot and will be reset. |
- |
LOG_STD_RECUR_ACTION |
|
CWAN_RP-3-CHANGE_POSEIDON_NEGOTIATION |
3-Error |
Unable to change negotiation. Failed to send message to\n\ slot [dec] port [dec]! |
MSFC2 failed to send message to change negotiation to\n\ OSM-4GE-WAN-GBIC |
- |
LOG_STD_ACTION |
|
CWAN_RP-3-CWAN_IFCOM_RMI |
3-Error |
Cwan ifcom RMI failure - [chars][dec] |
The CWAN IFCOM RMI Registration. |
c7600-env |
LOG_STD_NO_ACTION |
|
CWAN_RP-3-ERROR |
3-Error |
NULL |
This message can take many forms. It provides information about a\n\ software error. |
- |
LOG_STD_ACTION |
|
CWAN_RP-3-FAILED_CONFIG |
3-Error |
Failed to send line card config message [chars] for slot [dec] port [dec] |
The RP could not send the specified configuration message to the line card |
osm-gigwan |
LOG_STD_ACTION |
|
CWAN_RP-3-FOREVER |
3-Error |
cmd [dec] to [chars] slot [dec]/[dec] took [dec] usecs done [hec] |
A CCB command from the RP to a WAN module took longer than expected. |
- |
LOG_STD_ACTION |
|
CWAN_RP-3-GBIC_INSERTED |
3-Error |
GBIC media type [dec] inserted in [chars] |
A GBIC was inserted in the interface. |
cwan |
LOG_STD_NO_ACTION |
|
CWAN_RP-3-GBIC_REMOVED |
3-Error |
GBIC removed from [chars] |
The GBIC was removed from the interface. |
cwan |
LOG_STD_NO_ACTION |
|
CWAN_RP-3-HV_ALLOCFAIL |
3-Error |
[chars]: Failed to allocate a VLAN: [chars] |
VLAN allocation failed for the stated reason. |
- |
"First power down any unused linecards. " "Next delete any unused interfaces/subinterfaces and " "any unused L2 VLANs from the VLAN database. " "Then wait for >3 minutes and retry." |
|
CWAN_RP-3-IFCFG_CMD_NOT_OWNER |
3-Error |
Process '[chars]' waiting for interface configuration command 0x[hec] to |
A process on the RP sent an configuration command to the slot specified in the error message and a different process waited for the result. This could cause incorrect line card configuration states. |
c7600-ha |
LOG_STD_ACTION |
|
CWAN_RP-3-IFCFG_FOREVER |
3-Error |
to [chars] slot [dec]/[dec] took [dec] usecs ret_val %lu |
A interface config command from the RP to a WAN module took \n\ longer than expected. |
- |
LOG_STD_ACTION |
|
CWAN_RP-3-IFCONFIG_ERR |
3-Error |
Interface config failed on port [dec]/[dec] cmd [dec] retval [dec] |
A configuration command sent from the system to a linecard failed |
osm-ct3 |
LOG_STD_ACTION |
|
CWAN_RP-3-IPCALLOCFAIL |
3-Error |
Failed to allocate IPC buffer [chars] |
The RP failed to allocate a buffer for communication with a\n\ WAN module. |
- |
LOG_STD_ACTION |
|
CWAN_RP-3-IPCPORTFAIL |
3-Error |
Failed to open IPC port '[chars]' [chars] with error [chars] |
The RP failed to open a port for communication with a WAN\n\ module. |
- |
LOG_STD_ACTION |
|
CWAN_RP-3-IPCSENDFAIL |
3-Error |
Failed to send IPC message [chars] |
The RP failed to send a message to a WAN module. |
- |
LOG_STD_ACTION |
|
CWAN_RP-3-KEEPFAIL |
3-Error |
The WAN module in slot [dec]/[dec] is not responding to keepalives |
The WAN module was either reset or has crashed and will be reset. |
- |
LOG_STD_RECUR_ACTION |
|
CWAN_RP-3-LC_CRASHINFO |
3-Error |
[chars] copied onto RP bootflash |
The WAN module has crashed and the crashinfo file has been\n\ copied onto the RP bootflash. The crashinfo filename indicates the\n\ module's slot. The file can be viewed using the\n\ <CmdBold>more<noCmdBold> command. |
- |
LOG_STD_ACTION |
|
CWAN_RP-3-LC_CRASHINFO_BLOCKED |
3-Error |
Duplicate crashinfo upload from slot [dec]/[dec] blocked |
The WAN module has crashed and the crashinfo was not saved because\n\ the WAN module has already crashed recently. |
- |
LOG_STD_ACTION |
|
CWAN_RP-3-LC_CRASHINFO_CORRUPT |
3-Error |
Verification of crashinfo from slot [dec]/[dec] failed |
The WAN module has crashed and verification of the crashinfo it\n\ sent failed. The crashinfo has not been saved to RP bootflash. |
- |
LOG_STD_ACTION |
|
CWAN_RP-3-LC_CRASHINFO_ERR |
3-Error |
Unexpected error while receiving crashinfo from slot [dec]/[dec] |
The WAN module has crashed and an unexpected error occured while\n\ the crashinfo was being copied onto RP bootflash. |
- |
LOG_STD_ACTION |
|
CWAN_RP-3-LC_CRASHINFO_IFSERR |
3-Error |
Error [chars] [chars]: [chars] [dec] |
The WAN module has crashed and an error occured while trying to\n\ access the RP's bootflash to save the crashinfo. |
- |
LOG_STD_ACTION |
|
CWAN_RP-3-LC_CRASHINFO_NOSPACE |
3-Error |
Not enough space on RP bootflash for crashinfo from slot [dec]/[dec] [dec] bytes needed [dec] available |
The WAN module has crashed and there is not enough space on the RP\n\ bootflash to store the crashinfo. |
- |
"Free up space on the RP's bootflash by using the\n\ <CmdBold>delete<noCmdBold> and <CmdBold>squeeze<noCmdBold>\n\ commands." |
|
CWAN_RP-3-LCLOG_BADSEV |
3-Error |
Invalid message severity from slot [dec]/[dec]: [dec] |
The WAN module passed down a logger message with an invalid\n\ severity level that the RP could not handle. |
- |
LOG_STD_ACTION |
|
CWAN_RP-3-MODULE_TYPE |
3-Error |
cannot find FCI for module type [dec] in slot [dec] |
An internal software error occurred while the system was detecting the module type for the module in the specified slot. The operation of the module will be affected. |
osm-basecard |
LOG_STD_ACTION |
|
CWAN_RP-3-OIRTWICE |
3-Error |
Slot [dec] OIR insertion/removal not paired up: [chars] |
An internal OIR-related error occured for the specified WAN\n\ module. |
cwtlc |
LOG_STD_ACTION |
|
CWAN_RP-3-POWER_CYCLE |
3-Error |
Power cycling WAN module in slot [dec]/[dec]. [chars] |
The WAN module is being power cycled. |
- |
LOG_STD_NO_ACTION |
|
CWAN_RP-3-POWER_CYCLE_IMMINENT |
3-Error |
The WAN module in slot [dec]/[dec] will be power cycled in [dec] seconds. |
The WAN module in the slot specified in the error message \n\ will be power cycled in the amount of time specified in the error \n\ message |
- |
LOG_STD_NO_ACTION |
|
CWAN_RP-3-PROCMSG |
3-Error |
Process msg send failed for process[dec] |
Process message send failed. |
cwan |
LOG_STD_ACTION |
|
CWAN_RP-3-RESET_FAIL |
3-Error |
The WAN module in slot [dec] failed even after several resets |
The WAN module in the slot specified in the error \n\ message did not boot successfully even after multiple \n\ attempts. |
- |
LOG_STD_RECUR_ACTION |
|
CWAN_RP-3-SCPALLOCFAIL |
3-Error |
Failed to allocate SCP packet [chars] |
The RP failed to allocate a packet for communication with other\n\ slots in the chassis. |
- |
LOG_STD_RECUR_ACTION |
|
CWAN_RP-3-SLOTCACHE_SYNTAX |
3-Error |
Error [chars]! |
The RP failed to parse the slot configuration string. |
- |
LOG_STD_ACTION |
|
CWAN_RP-3-UPGRADE_ERROR |
3-Error |
Slot [dec]: The ROMMON upgrade failed to complete. |
An error occurred during the upgrade process. |
vpn-sm |
"If the module reloads successfully please check " "the file and try again otherwise please contact " "your Cisco technical support representative." |
|
CWAN_RP-3-WAN_BRIDGING_CFG_EXCD |
3-Error |
The number of VPLS/EoMPLS/Bridging/QinQ VCs exceeded the maximum[dec] |
Review the configuration guidelines for the features that are being configured and reduce the number of VPLS EoMPLS Bridging to the number that is supported by the platform. |
osm-bridge |
- |
|
CWAN_RP-4-CONFIG_MISMATCH |
4-Warning |
\n\nIrreconcilable Configuration difference between Active & Standby Supervisors due to OIR/Config Event for [dec]/[dec] -> Reloading Standby Supervisor to synchronize the configuration.\n\n |
Unexpected configuration difference between Supervisors. |
c7600-ha |
"None. This is expected behavior." |
|
CWAN_RP-4-EMPTY_CWANBAYS |
4-Warning |
FLEXWAN in slot [dec] is empty. Please remove the Flexwan or insert it with atleast one PA |
The FLEXWAN in the specified slot does not contain any Port Adapters. |
- |
"The FLEXWAN should be removed as this is an unsupported configuration" |
|
CWAN_RP-4-IFCFG_CMD_TIMEOUT |
4-Warning |
Interface configuration command 0x[hec] to slot [dec]/[dec] timed out |
The RP sent an configuration command to the slot specified in the error message and received no confirmation for the command. |
c7600-ha |
LOG_STD_ACTION |
|
CWAN_RP-4-INCR_CFG_SYNC_FAIL |
4-Warning |
7600 incremental running-config sync for [[dec]/[dec]] failed - [chars][dec] |
The specified 7600 incremental running-config sync failed |
c7600-ha |
"Power cycle the redundant supervisor" |
|
CWAN_RP-4-INVALID_UNIT |
4-Warning |
Invalid 7600 Unit: [[dec]/[dec]]. |
The specified 7600 slot/cpu beyonds the Chassis's limit. |
c7600-ha |
"Power cycle the redundant supervisor" |
|
CWAN_RP-4-IPCFAILED |
4-Warning |
IPC failed to send RPC message to WAN module |
The RP failed to send an RPC message via IPC to a WAN module. |
cwan |
LOG_STD_NO_ACTION |
|
CWAN_RP-4-LCLOG_TOOLONG |
4-Warning |
Message too long from slot [dec]/[dec]: [dec] bytes |
The WAN module passed down a logger message that is too long for\n\ the RP to handle. |
- |
LOG_STD_ACTION |
|
CWAN_RP-4-LL_UNKNOWN |
4-Warning |
Unknown linecard message: type [dec] [chars] |
Mismatch version between RP and LC or internal message format mismatch |
cwan |
LOG_STD_NO_ACTION |
|
CWAN_RP-4-MODULE_CONFIG_MISSING |
4-Warning |
configuration not available/not matching in startup-config for slot [dec] |
Some information regarding the configuration of the module in the specified slot is missing. Any configuration in the startup-config for the interfaces will not be applied. If the module in the specified slot is a FlexWAN the missing configuration information is details of the Port Adapters in the FlexWAN module. This information is missing from the <CmdBold>SLOTCACHE<NoCmdBold> ROMMON variable. |
osm-basecard |
- |
|
CWAN_RP-4-SEMAHOG |
4-Warning |
Process [dec] [chars] hogging [chars]! calling proc [dec] [chars] |
- |
- |
- |
|
CWAN_RP-6-ADF_FILE |
6-Information |
Slot [dec]: Using VPN-SM Upgrade File: \[chars]\ |
Booting specified upgrade image for VPN Services Module. |
- |
LOG_STD_NO_ACTION |
|
CWAN_RP-6-AUX_FILE |
6-Information |
Slot [dec]: Found VPN-SM Firmware in File: \[chars]\ |
The file specified in the message was found and will be loaded by the VPN Services Module instead of the bundled image. |
- |
LOG_STD_NO_ACTION |
|
CWAN_RP-6-CARDRECONCILE |
6-Information |
Module type changed on slot [dec]/[dec] from [dec] to [dec] |
The WAN module has booted and it has been detected that it is\n\ of a different type to the WAN module that was previously in\n\ this slot. |
- |
LOG_STD_NO_ACTION |
|
CWAN_RP-6-CARDRELOAD |
6-Information |
Module reloaded on slot [dec]/[dec] |
The WAN module has booted. |
- |
LOG_STD_NO_ACTION |
|
CWAN_RP-6-COREDUMP_ENABLED |
6-Information |
No heartbeat or keepalive resets will occur for slot [dec] since coredump has been enabled |
The module in the slot has crashed and is configured to generate a coredump file. The module will not be reset due to heartbeat and keepalive failures to ensure the coredump file generation is not prematurely terminated. |
c7600-env |
LOG_STD_NO_ACTION |
|
CWAN_RP-6-IMAGE_UPGRADE |
6-Information |
Bootflash image upgrade [chars] for slot [dec]/[dec][chars] |
The bootflash image on the WAN module has been or is being\n\ automatically upgraded. |
- |
LOG_STD_NO_ACTION |
|
CWAN_RP-6-LC_PRESENT |
6-Information |
[chars] in slot [dec] |
A WAN module was detected by the hardware. |
- |
LOG_STD_NO_ACTION |
|
CWAN_RP-6-LC_RESET |
6-Information |
The RP is reloaded resetting slot [dec] is necessary. Please ignore errors if any till the linecard comes up. |
If the system is running Catalyst operating system software on the supervisor engine and Cisco IOS software on the MSFC the WAN line cards that power up before the RP powers up will be reset automatically. |
cwpa |
LOG_STD_NO_ACTION |
|
CWAN_RP-6-NOPWRISSU |
6-Information |
Spa inserted in [chars] powered down because ISSU is in progress |
The Spa insertion detected during ISSU upgrade process. It will be acted upon completion of the ISSU process. |
- |
LOG_STD_NO_ACTION |
|
CWAN_RP-6-OUT_OF_RESOURCE |
6-Information |
[chars] configuration has exceeded available internal resources. |
The resources required for configuration are no longer available. They may have been acquired by another application. |
osm-mpb |
"If the requested resources have not been allocated " "to another application call your technical support representative " "for further assistance." |
|
CWAN_RP-6-OVERRIDE |
6-Information |
Slot [dec]: ...Overriding Intrinsic VPN-SM Firmware. |
Specified image will be used instead of bundled image. |
- |
LOG_STD_NO_ACTION |
|
CWAN_RP-6-PLAT_AVL_DEL_FAILED |
6-Information |
Platform AVL delete failed for PPPoE session due to wrong slot id [dec] |
Deletion of session related information from the AVL tree failed because the slot number used to index it is wrong |
c7600-bb |
LOG_STD_NO_ACTION |
|
CWAN_RP-6-QUIESCE_FAIL |
6-Information |
Quiesce failed for slot [dec]/[dec] |
The RP failed to contact the WAN module during failover.\n\ The WAN module will be reset. |
- |
LOG_STD_NO_ACTION |
|
CWAN_RP-6-SESS_LIMITS_CHASSIS |
6-Information |
Exceeded max number of sessions supported. \nSupported limit 32000/chassis |
Total number of subscriber sessions on this chassis exceeded the allowed limits. The supported limit is 32000 sessions per chassis |
c7600-bb |
"Avoid bringing up more number of sessions " "than the supported limit" |
|
CWAN_RP-6-SESS_LIMITS_ES_PLUS |
6-Information |
Exceeded max number of sessions supported on ES+ LC in slot [dec]. \nSupported limit 16000/ES+ |
Total number of subscriber sessions on ES+ line card exceeded the allowed limits. The supported limit is 16000 sessions per ES+ |
c7600-bb |
"Avoid bringing up more number of sessions " "than the supported limit" |
|
CWAN_RP-6-SESS_LIMITS_PORT_GROUP |
6-Information |
Exceeded max number of sessions supported on port-group Gig[dec]/[dec] to Gig[dec]/[dec].\nSupported limit 4000/port-group on ES+ LC |
Total number of subscriber sessions on a single port-group in ES+ exceeded the allowed limits. The supported limit is 4000 sessions per port-group |
c7600-bb |
"Rearrange the subscribers on ES+ in such a way " "maximum number of sessions supported in a port-group is 4000." |
|
CWAN_RP-6-SESS_LIMITS_SIP400 |
6-Information |
Exceeded max number of sessions supported on SIP400 LC in slot [dec]. \nSupported limit 8000/SIP400 |
Total number of subscriber sessions on SIP400 line card exceeded the allowed limits. The supported limits is 8000 sessions per SIP400 |
c7600-bb |
"Avoid bringing up more number of sessions " "than the supported limit" |
|
CWAN_RP-6-SESS_LIMITS_TEN_GIG_PORT |
6-Information |
Exceeded max number of sessions supported on port Te[dec]/[dec]. \nSupported limit 8000/port on a Ten Gig port on ES+ LC. |
Total number of subscriber sessions on a single Ten Gig port in ES+ exceeded the allowed limits. The supported limit is 8000 sessions per Ten Gig port. |
c7600-bb |
"Rearrange the subscribers on ES+ in such a way that " "maximum number of sessions per Ten Gig port is 8000" |
|
CWAN_RP-6-UNQUIESCE_FAIL |
6-Information |
Unquiesce failed for slot [dec]/[dec]. Error = [dec] |
The RP failed to unquiesce the WAN module. \n\ The WAN module will be reset. |
- |
show diagbus and show ipc status |
|
CWAN_RP-6-UPGRADE_COMPLETE |
6-Information |
Slot [dec]: ROMMON upgrade complete. Reset the card for the changes to take effect. |
The ROMMON upgrade has completed successfully. The card must be reloaded for the changes to take effect |
- |
LOG_STD_NO_ACTION |
|
CWAN_RP-7-SLOTCACHE_CARDTYPE |
7-Debug |
parsed slot [dec] fci_type [dec] |
Information parsed from the slot configuration string by the RP. |
- |
LOG_STD_NO_ACTION |
|
CWAN_RP-7-SLOTCACHE_PATYPE |
7-Debug |
Bay [chars] has type [dec] ports[hec] |
Information parsed from the slot configuration string by the RP. |
- |
LOG_STD_NO_ACTION |
|
CWAN_SPA-3-CREATION_FAILURE |
3-Error |
slot=[dec] subslot=[dec] spa_type=0x[hec] lc_type=0x[hec]. |
Failed to create a SPA object. |
FIX-ME |
LOG_STD_SH_TECH_ACTION |
|
CWAN_SPA-3-DIAG_CONFIG |
3-Error |
[chars] did not complete [dec]/[dec] |
An error has occured during diagnostic test. |
c7600-field-diag |
LOG_STD_SH_TECH_ACTION |
|
CWAN_SPA-3-FAILURE |
3-Error |
[chars]: SPA failure - cause: [chars] [hex] recovery action: [chars] [dec] |
The SPA failed for the specified reason |
FIX-ME |
LOG_STD_SH_TECH_ACTION |
|
CWAN_SPA-3-INTR_THROTTLE |
3-Error |
Interface [chars] MAC interrupt was throttled.\n\ Reenabling MAC interrupts via one sec spa process |
MAC interrupt burst has occurred on one of the interfaces on the link daughtercard. The error message indicates that a throttling mechanism has been applied to this port to avoid any operational damage that could be provoked by this event. The cause for this problem could be bad transceiver highly frenquent flapping optical signals or mismatched path signals e.g. receiving 10GBASE-W signal on 10GE LAN interface etc. |
c7600-esm-20 |
"Check the interface configuration and received signal characteristics. " "Also verify the XFP transceiver and receive signal path to determine the " "If this message recurs " LOG_STD_ACTION |
|
CWAN_SPA-3-INVALID_DATA_INSTANCE |
3-Error |
interface type [chars] slot [dec] port [dec] vc [dec] : [chars] |
Data required to support the interface is not available. |
FIX-ME |
LOG_STD_SH_TECH_ACTION |
|
CWAN_SPA-3-INVALID_IF_INDEX |
3-Error |
index= [dec] cardType=0x[hec] spaType=0x[hec] slot [dec] subSlot [dec] slotunit [dec] vc [dec] |
Index for the interface is not valid. |
FIX-ME |
LOG_STD_SH_TECH_ACTION |
|
CWAN_SPA-3-INVALID_INDX_RANGE |
3-Error |
index1= [dec] index2= [dec] maxIndex= [dec] |
Invalid index range. |
FIX-ME |
LOG_STD_SH_TECH_ACTION |
|
CWAN_SPA-3-MEM_ALLOC_ERROR |
3-Error |
[chars] |
Memory allocation error. |
FIX-ME |
LOG_STD_SH_TECH_ACTION |
|
CWAN_SPA-3-NULL_ATM_DB |
3-Error |
Unable to create ATM DB for [chars] |
Data required to support the interface is not available. |
FIX-ME |
LOG_STD_SH_TECH_ACTION |
|
CWAN_SPA-3-NULL_SPA_PTR |
3-Error |
- |
Pointer to a SPA object is NULL. |
FIX-ME |
LOG_STD_SH_TECH_ACTION |
|
CWAN_SPA-3-NULL_VFT |
3-Error |
[chars] virtual function table is not initialized. spaType=0x[hec] |
A required function table is not initialized |
FIX-ME |
LOG_STD_SH_TECH_ACTION |
|
CWAN_SPA-3-NULL_VFUNC |
3-Error |
[chars] vector is not initialized. spaType=0x[hec] |
A required function vector is not initialized |
FIX-ME |
LOG_STD_SH_TECH_ACTION |
|
CWAN_SPA-3-POWER_CYCLE |
3-Error |
[chars] occurred on Shared Port Adapter [dec]/[dec] |
An error has occurred which will cause the \n\ Shared Port Adapter to be power cycled |
msc-200-ha |
LOG_STD_SH_TECH_ACTION |
|
CWAN_SPA-3-SPA_CREATION_FAILURE |
3-Error |
slot=[dec] subslot=[dec] PID=[chars] lc_type=0x[hec]. |
Failed to create a SPA object. |
FIX-ME |
LOG_STD_SH_TECH_ACTION |
|
CWAN_T3E3-3-IFCONFIG_ERR |
3-Error |
Interface config error on T3 port [dec]/[dec] cmd [dec] retval [dec] |
A configuration command sent from the system to a linecard failed |
osm-t3e3 |
LOG_STD_ACTION |
|
CWANLC_ATM-3-CMDERR |
3-Error |
[chars]: [chars] IPC command fails cause: 0x%04x |
The ATM RP driver experienced IPC command error. |
cwtlc |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CWANLC_ATM-3-IPC_ERROR |
3-Error |
[chars]: IPC command \[chars]\ failure due to \[chars]\ |
The SPA ATM RP driver experienced IPC command error. |
spa-atm-all |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CWANLC_ATM-3-NOVPSPACE |
3-Error |
[chars]: out of VP space for VPI [dec] |
Out of VPs on the SAR. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CWANLC_ATM-3-VCCLOSEFAIL |
3-Error |
[chars]: Failed to remove VC [dec]/[dec] cause [dec] |
Attempt to remove VC on the linecard failed. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CWANLC_ATM-3-VPCLOSEFAIL |
3-Error |
[chars]: Failed to remove VP [dec] cause [dec] |
Attempt to remove VP on the linecard failed. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CWANLC_ATM-4-CLOSEPEND |
4-Warning |
[chars]: The TX SAR is currently freeing internal buffers previously allocated for the identical channel id. The execution of the current command is delayed. |
The TX SAR has taken longer than expected to free its internal buffers. |
- |
LOG_STD_NO_ACTION |
|
CWANLC_ATM-4-MISMATCH_VCENCAP |
4-Warning |
[chars]: Cannot mix VC encapsulation types in multipoint interfaces |
This ATM card only allows VC encapsulations of the same type on the main interface or multipoint subinterfaces |
- |
"Reconfigure the ATM interface with matching VC encapsulations" |
|
CWANLC_ATM-4-SEMHOG |
4-Warning |
[chars]: Process [dec] [chars] hogging semaphore -- called by process [dec] [chars] |
The named process has held the resource semaphore longer than\n\ expected. |
- |
LOG_STD_NO_ACTION |
|
CWANLC_ATM-4-UNSUP |
4-Warning |
[chars]: unsupported feature: [chars] |
This feature is not supported by Draco ATM RP. |
cwtlc |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CWANLC-2-PCIERROR |
2-Critical |
Fatal PCI Error [chars] seen on PCI Bus [dec] |
A Fatal PCI Error was detected on the PCI bus. Most likely it is a hardware problem. |
- |
"Call your technical support representative for " "assistance if this message persists." |
|
CWANLC-3-CWANLC_EARL_VERSION_NOTICE |
3-Error |
CWAN receives mismatch Earl version notification. New Earl[dec] vs Earl[dec] |
The RP has determined via an SCP find operation that the version of the EARL switching engine on the line card has changed. This message occurs during switchover operation. The version of the EARL switching engine is specified in the message text. |
- |
LOG_STD_ACTION |
|
CWANLC-3-FATAL |
3-Error |
[chars] |
The Optical Services Module line card has encountered a fatal error. |
- |
LOG_STD_ACTION |
|
CWANLC-3-FPD_INCOMPATIBLE |
3-Error |
FPD ID=[dec] image in this FPD package is for revision [dec].x boards. It is incompatible with current board revision of [dec].[dec] |
This FPD package does not contain images that are compatible with the current board revision. |
c7600-sip-common |
"Perform the FPD upgrade operation with a newer version of FPD " "image package that is compatible with the running Cisco IOS " "software. Consult with the FPD image package section of the " "Cisco IOS software release note to confirm if your board " "revision is supported for a particular release." |
|
CWANLC-3-HWREVREADFAIL |
3-Error |
Failed to retrieve h/w version from EEPROM |
The Linecard failed to read the hardware version from the CPU eeprom. |
- |
LOG_STD_ACTION |
|
CWANLC-3-IPCALLOCFAIL |
3-Error |
Failed to allocate IPC buffer [chars] |
The Linecard failed to allocate a buffer for communication with the Route Processor Draco. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
CWANLC-3-IPCPORT |
3-Error |
Failed to [chars] IPC port '[chars]' error [chars] |
The Linecard failed to create a port for communication with the Route Processor Draco. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
CWANLC-3-IPCPORTFAIL |
3-Error |
Failed to open IPC port '[chars]' [chars] |
The Linecard failed to open a port for communication with the Route Processor Draco. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
CWANLC-3-IPCSENDFAIL |
3-Error |
Failed to send IPC message [chars] |
The Linecard failed to send a message to the Route Processor Draco. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
CWANLC-3-LTL_NOPPEPORTMAP |
3-Error |
Failed to retrieve default port mapping for packet processor [dec] |
The linecard software initialization was not completed correctly |
- |
LOG_STD_ACTION |
|
CWANLC-3-TVPN_NOMEM |
3-Error |
Failed to start vpn not enough memory |
The OSM card could not start VPN due to a memory exhaustion |
- |
"Reduce other system activity to ease memory demands. " "If conditions warrant upgrade to a larger memory " "configuration. If this message recurs "LOG_STD_ACTION |
|
CWANLC-4-LOGMSGTOOBIG |
4-Warning |
Logger message length exceeds max [dec] bytes |
The Linecard attempted to send a large message to the Route Processor Draco. |
- |
LOG_STD_ACTION |
|
CWANLC-5-IPCPENDING |
5-Notice |
Too many messages [dec] in IPC pending queue |
The IPC pending queue is growing. Will soon deplete the IPC header cache and the IO buffers |
- |
LOG_STD_ACTION |
|
CWANLC-5-NOSCPPING |
5-Notice |
Linecard has not sent SCP PING responses for too long |
SCP ping mechanism is used by RP/SP processors to monitor if the linecard executing IOS is in a healthy state. This SCP ping response has not been sent by the line card for long time now - the line card has exported its context information to the RP and may be powercycled. The exported context is available in the output of 'show diag' |
cwpa |
"Save the 'show diag' output generated and contact your " "technical support representative if the line card is reset" |
|
CWANLC-6-BUSSTALL |
6-Information |
Constellation BUS Stall detected |
This message indicates that a stall was detected on the Constellation Bus probably due to some OIR activity on the Bus. |
- |
"No action needed Informational." |
|
CWANLC-6-BUSSTALLCLEAR |
6-Information |
Constellation BUS Stall cleared |
This message indicates that a stall was cleared on the Constellation Bus. |
- |
"No action needed Informational." |
|
CWANLC-6-LONGSTALL |
6-Information |
Long bus stall [dec] ms check for improperly seated cards |
This message indicates that a stall was detected but the backplane stall was longer than expected. |
- |
"Make sure all cards are firmly seated. If the " "problem reoccurs it may indicate a hardware failure." |
|
CWMP_DOWNLOAD-5-CONFIG_FAILURE |
5-Notice |
CWMP download: config apply operation failed [chars] |
The configuration apply operation with CWMP DOWNLOAD RPC\n\method is failed. |
- |
"No action required." |
|
CWMP_DOWNLOAD-5-CONFIG_SUCCESS |
5-Notice |
CWMP download: config file successfully downloaded and applied [chars] |
The configuration apply operation with CWMP DOWNLOAD RPC\n\method is success. |
- |
"No action required." |
|
CWPA-2-BAD_HWVERS |
2-Critical |
Unable to determine board hardware version |
The line card software cannot read the line card hardware version. This condition indicates a hardware error. |
cwpa |
LOG_STD_ACTION |
|
CWPA-2-PA_VOLFAIL |
2-Critical |
Port adapter [dec]V failed Reloading flexwan |
The line card has encountered an error involving power delivery to the line card. Likely causes for this error are an environmental condition an overtemperature condition or inconsistent voltage to the line card. |
cwpa |
"Check the input voltage and temperature of the line card. " LOG_STD_RECUR_ACTION |
|
CWPA-2-PAOIR |
2-Critical |
Port adapter OIR not supported reloading |
An OIR operation occurred on the port adapters of the specified line card. OIR operations are not supported on the port adapter. This error has caused the line card to crash and reload. |
cwpa |
"Do not attempt an OIR operation on the port adapters of the specified " "line card." |
|
CWPA-2-WHICH_INT |
2-Critical |
Unexpected [chars] interrupt INT status = 0x[hec] |
The line card specified in the error message has encountered an unexpected interrupt. |
cwpa |
LOG_STD_ACTION |
|
CWPA-3-BAD_IFCOMTYPE |
3-Error |
Bad ifcom message type=[dec] |
- |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CWPA-3-BADMALUCMD |
3-Error |
Unsupported MALU command [dec] arg=[hex] pascb=[hex] |
- |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CWPA-3-CMDNOPASCB |
3-Error |
PASCB Null for command [dec] arg=[hex] |
- |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CWPA-3-DIAGFAIL |
3-Error |
Failed to handle diag [chars] [dec] |
The FlexWAN line card failed to execute diag command. Further details are specified in the text that is displayed on the console or in the system log. |
cwpa |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
CWPA-3-IPCALLOCFAIL |
3-Error |
Failed to allocate IPC buffer [chars] |
The FlexWAN line card failed to allocate a buffer for communication with the Route Processor Draco. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
CWPA-3-IPCSENDFAIL |
3-Error |
Failed to send IPC message [chars] |
The FlexWAN line card failed to send a message to the\n\ Route Processor Draco. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CWPA-3-LVLTRTOOBIG |
3-Error |
Loveletter length exceeds max [dec] bytes |
The FlexWAN line card attempted to send a large message to the\n\ Route Processor Draco. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CWPA-3-NODISPATCH |
3-Error |
Dispatch vector Null cmd=[dec] dintf=[dec] |
No command dispatch vector was found for the specified interface. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
CWPA-3-PROCCREATEFAIL |
3-Error |
Failed to create [chars] process |
The Linecard failed to create a process which\n\ which is necessary for proper functioning of the\n\ linecard. |
cwpa |
"Copy the error message as it appears and\n\ report it to your technical support \n\ representative. If it is the 'stats export\n\ process' then you might not see input/output\n\ rate and bytes getting incremented in 'show\n\ interface' output for flexwan/flexwan2 non-\n\ channelised interfaces. However you can get\n\ the stats from 'show interface acc' or 'show\n\ interface stats'." |
|
CWPA-4-HEADER_TOO_BIG |
4-Warning |
Needs [dec] bytes with only [dec] bytes available. Packet size [dec] received from [chars] buffer [hex] packet start [hex]:\n %-08x:%08x %08x %08x %08x %08x %08x %08x %08x\n %-08x:%08x %08x %08x %08x %08x %08x %08x %08x\n |
A packet was sent from the PA to either the route processor or the line card. That packet did not have enough available space to append the header. A new particle has been linked to the packet to store the header. |
- |
LOG_STD_NO_ACTION |
|
CWPAATOM-3-BADLTL |
3-Error |
Bad LTL index 0x[hec] for vlan [dec] local_vc_label [dec] |
Local Target Logic index value is invalid |
7600-mpls |
"If your EoMPLS traffic is fine then ignore this \n\ If not then contact your Cisco technical support representative." |
|
CWRPSPA-3-HWIDB_FAILURE |
3-Error |
Creation: slot [dec] subSlot [dec] port [dec] vc [dec] |
Failed to create an interface hwidb. |
cwan |
LOG_STD_SH_TECH_ACTION |
|
CWRPSPA-3-INVALID_PORT_NUM |
3-Error |
slot=[dec] port=[dec] hwidbType=0x[hec] max_port_num=[dec] LCtype=0x[hec] |
The port number is out of range. |
cwan |
LOG_STD_SH_TECH_ACTION |
|
CWRPSPA-3-MAX_SPA |
3-Error |
Power to IPSEC-SPA-2G in [chars] is denied because it has exceeded the number allowed[dec] |
The number of IPSEC-SPA-2G in a chassis is limited. This message is displayed when the number of IPSEC-SPA-2G in the chassis has exceeded this limit. |
cwan |
"Use only the number of supported IPSEC-SPA-2G" |
|
CWRPSPA-3-NO_HOST_INFO |
3-Error |
slot [dec] subSlot [dec] spaType 0x[hec] |
Failed to get information about the host linecard. |
cwan |
LOG_STD_SH_TECH_ACTION |
|
CWRPSPA-3-SPA_NO_HOST_INFO |
3-Error |
slot [dec] subSlot [dec] PID [chars] |
Failed to get information about the host linecard. |
cwan |
LOG_STD_SH_TECH_ACTION |
|
CWRPSPA-4-SPA_CMD_NO_RESP |
4-Warning |
[chars]: No response for interface configuration command \[chars]\ |
A timeout occurred while RP was waiting for a response from line card. This may happen due to line card CPU being too busy to respond to the command. |
cwan |
LOG_STD_NO_ACTION |
|
CWRPSPA-4-SPA_RESP_CMD_MISMATCH |
4-Warning |
[chars]: Expecting response to interface configuration command \[chars]\ but received response to command \[chars]\. |
An internal synchronization error occurred while configuring the interface. The configuration may not have succeeded. |
cwan |
"Check that the running configuration for the " "interface is correct. If this message occurred on the standby try " "reloading the standby to ensure that its configuration is in sync. " "If this message is repeatable please " LOG_STD_SH_TECH_ACTION |
|
CWRPSPA-5-OUT_OF_RESOURCES |
5-Notice |
[chars]: Unable to create [chars] due to SPA resource limitations. |
The SPA was unable to create the requested resource due to limited hardware or software resources |
- |
LOG_STD_NO_ACTION |
|
CWRPSPA-6-CARDRELOAD |
6-Information |
Module [dec] reload due to SPA insert in [dec]/[dec]. |
When inserting a SPA on this carrier card the card is reset. |
- |
LOG_STD_NO_ACTION |
|
CWS-2-IPC_INIT_FAILED |
2-Critical |
CWS-IPC message handler registration failure rc [dec] |
Registering an IPC message handler for the CWS feature failed. This will cause the feature to not function. |
cws-xe |
LOG_STD_ACTION |
|
CWS-3-IPC_INVALID_MSG |
3-Error |
CWS-Invalid request [dec] |
Received Invalid message from CWS client proxy |
cws-xe |
LOG_STD_RECUR_ACTION |
|
CWS-3-IPC_NORES |
3-Error |
CWS-No space for the IPC reply size [dec] request [chars] |
For a request from CWS client proxy it was not possible to allocate space for a reply for the specified size. |
cws-xe |
LOG_STD_RECUR_ACTION |
|
CWS-3-IPC_OPEN_REPLY |
3-Error |
CWS-IPC Open Reply failed request [chars] |
For a request from CWS client proxy opening the reply buffer failed |
cws-xe |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
CWS-3-IPC_SEND_FAILED |
3-Error |
CWS-IPC [chars] [chars] send failed [dec] |
IPC message send failure |
cws-xe |
LOG_STD_ACTION |
|
CWS-5-CWS_INVALID_REF_COUNT |
5-Notice |
Invalid ref count [dec] in chunk [hex] |
CTR has seen an invalid ref count in the NSH pool\n |
cpp-ucode |
LOG_STD_NO_ACTION |
|
CWS-5-CWS_ON_PATH_DEBUG |
5-Notice |
NSH D-bit set for SIP: [inet] DIP: [inet] Src_node: [dec] Src_If_Id: [dec] Tenant_Id: [dec] |
CTR has seen an NSH header with D-bit set\n |
- |
LOG_STD_NO_ACTION |
|
CXSC-2-IPC_FAILURE |
2-Critical |
CXSC-IPC message [chars] handler failed rc [dec] |
An IPC message handler for the CXSC feature failed. This will cause the feature to not function. |
qfp-cxsc |
LOG_STD_ACTION |
|
CXSC-2-IPC_INIT_FAILED |
2-Critical |
CXSC-IPC message handler registration failure rc [dec] |
Registering an IPC message handler for the CXSC feature failed. This will cause the feature to not function. |
qfp-cxsc |
LOG_STD_ACTION |
|
CXSC-3-CXSC_COND_DEBUG_REG_FAILED |
3-Error |
[chars] |
Failure occurred when attempting to Register/Initialize conditional debugging. |
qfp-ucode |
LOG_STD_ACTION |
|
CXSC-3-FEAT_CTX_DOWN |
3-Error |
CXSC-Invalid request [chars] [dec] while context is down |
While the feature context was not active an invalid request was received from another layer of the CXSC software stack. |
qfp-cxsc |
LOG_STD_RECUR_ACTION |
|
CXSC-3-FEAT_DOWN |
3-Error |
CXSC-Invalid request [chars] [dec] while feature is down |
While the feature was not active an invalid request was received from another layer of the CXSC software stack. |
qfp-cxsc |
LOG_STD_RECUR_ACTION |
|
CXSC-3-IPC_INVALID_MSG |
3-Error |
CXSC-Invalid request [dec] |
We received an invalid message from another layer of the CXSC software stack. |
qfp-cxsc |
LOG_STD_RECUR_ACTION |
|
CXSC-3-IPC_INVALID_MSG_LEN |
3-Error |
CXSC-Invalid IPC length [dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Invalid IPC message length |
qfp-cxsc |
LOG_STD_ACTION |
|
CXSC-3-IPC_NORES |
3-Error |
CXSC-No space for the IPC reply size [dec] request [dec] |
For a request from upper CXSC software stack layers it was not possible to allocate space for a reply for the specified size. |
qfp-cxsc |
LOG_STD_RECUR_ACTION |
|
CXSC-3-IPC_OPEN_REPLY |
3-Error |
CXSC-IPC Open Reply failed request [dec] |
For a request from upper CXSC software stack layers it was not possible to open the reply buffer. |
qfp-cxsc |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
CXSC-3-IPC_SEND_FAILED |
3-Error |
CXSC-IPC [chars] [dec] send failed [dec] |
IPC message send failure |
qfp-cxsc |
LOG_STD_ACTION |
|
DAPR_BR-4-FLOW_LIMIT_EXCEEDED |
4-Warning |
curr [dec] max [dec] |
DAPR Flows exceeded |
dapr |
LOG_STD_NO_ACTION |
|
DAPR_BR-4-PREFIX_LIMIT_EXCEEDED |
4-Warning |
curr [dec] max [dec] |
DAPR RIB prefixes exceeded |
dapr |
LOG_STD_NO_ACTION |
|
DAPR_BR-4-RMAP_LIMIT_EXCEEDED |
4-Warning |
curr [dec] max [dec] |
DAPR route-map entries exceeded max allowed |
dapr |
LOG_STD_NO_ACTION |
|
DAPR_BR-5-EGRESS_INTF_NOT_VIABLE |
5-Notice |
[chars] curr-bwkbps %lu min-bwkbps %ld |
DAPR egress interface not viable |
dapr |
LOG_STD_NO_ACTION |
|
DAPR_BR-5-EGRESS_INTF_THRESHOLD_EXCEED |
5-Notice |
[chars] curr-util %llu%% max-util %ld%% |
DAPR egress interface utilization threshold exceeded |
dapr |
LOG_STD_NO_ACTION |
|
DAPR_BR-5-EGRESS_INTF_UPDOWN |
5-Notice |
[chars] [chars] |
DAPR egress interface status |
dapr |
LOG_STD_NO_ACTION |
|
DAPR_BR-5-INGRESS_INTF_UPDOWN |
5-Notice |
[chars] [chars] |
DAPR ingress interface status |
dapr |
LOG_STD_NO_ACTION |
|
DAPR_BR-5-NBR_ROUTE_INVALID |
5-Notice |
Neighbor-BR [inet] |
Invalid route to neighbor Border-Router |
dapr |
LOG_STD_NO_ACTION |
|
DAPR_BR-5-NBR_TUNNEL_UPDOWN |
5-Notice |
Neighbor-BR [inet] tunnel [chars] |
Status of tunnel to neighbor Border-Router |
dapr |
LOG_STD_ACTION |
|
DAPR_BR-5-RESET |
5-Notice |
reason: [chars] |
Border-Router reset due to mentioned reason |
dapr |
LOG_STD_NO_ACTION |
|
DAPR_BR-5-RM_ROUTE_INVALID |
5-Notice |
No route or route is via egress |
Invalid route from Border-Router to Route-Manager |
dapr |
LOG_STD_ACTION |
|
DAPR_BR-5-STATUS |
5-Notice |
[chars] |
Border-Router status |
dapr |
LOG_STD_NO_ACTION |
|
DAPR_RM-3-APP_RT_COMPUTE_FAILED |
3-Error |
[chars] |
App route compute failed for flow-group |
dapr |
LOG_STD_NO_ACTION |
|
DAPR_RM-3-BR_REG_FAILED |
3-Error |
BR [chars] reason: [chars] |
BR Registration failed |
dapr |
LOG_STD_ACTION |
|
DAPR_RM-3-BR_RESET |
3-Error |
BR [chars] reason: [chars] |
RM reset the BR due to mentioned reason |
dapr |
LOG_STD_ACTION |
|
DAPR_RM-3-FLOW_EXP_PKTS_MISSED |
3-Error |
BR [chars] missed-pkts [dec] |
Flow export packets missed |
dapr |
LOG_STD_ACTION |
|
DAPR_RM-3-FLOW_INVALID_EGRESS |
3-Error |
flow-group [chars]/[chars]/[dec] state [chars] uptime [dec]s last-transition [dec]s ingress-BR [chars] expected-egress [chars]/[dec] reported-egress [chars]/[dec] |
Flow discovered from unexpected egress |
dapr |
LOG_STD_ACTION |
|
DAPR_RM-4-APP_REROUTE_FAILED |
4-Warning |
[chars] |
App route re-compute failed for flow-group |
dapr |
LOG_STD_NO_ACTION |
|
DAPR_RM-4-FLOW_DATA_RECS_IGNORED |
4-Warning |
BR [chars] reason: [chars] |
Flow data records ignored |
dapr |
LOG_STD_ACTION |
|
DAPR_RM-4-FLOW_EXP_PKT_INVALID_SEQ |
4-Warning |
BR [chars] last-seq [dec] curr-seq [dec] |
Unexpected seq num in flow export pkt |
dapr |
LOG_STD_ACTION |
|
DAPR_RM-4-FLOW_INVALID_INGRESS |
4-Warning |
flow-group [chars]/[chars]/[dec] state [chars] uptime [dec]s last-transition [dec]s ingress-BR [chars] egress-BR/intf [chars]/[dec] ingress-intf [chars] |
Flow discovered from unexpected ingress |
dapr |
LOG_STD_ACTION |
|
DAPR_RM-4-FLOW_MULTI_EGRESS |
4-Warning |
flow-group [chars]/[chars]/[dec] state [chars] uptime [dec]s num-egress [dec] prev-egress [chars]/[dec] curr-egress [chars]/[dec] |
New flow discovered from multiple egresses |
dapr |
LOG_STD_ACTION |
|
DAPR_RM-4-NO_VIABLE_PATH |
4-Warning |
[chars] |
No viable path found for flow-group |
dapr |
LOG_STD_NO_ACTION |
|
DAPR_RM-4-RIB_MISMATCH |
4-Warning |
route-count: old [dec] new [dec] |
Mismatch of RIB database between BRs and RM |
dapr |
LOG_STD_ACTION |
|
DAPR_RM-5-BR_STATUS |
5-Notice |
BR [chars] [chars] |
Border-Router status on RM |
dapr |
LOG_STD_NO_ACTION |
|
DAPR_RM-5-RM_STATUS |
5-Notice |
[chars] |
Route-Manager status |
dapr |
LOG_STD_NO_ACTION |
|
DAPR_RM-6-APP_RT_DEL |
6-Information |
[chars] BW:[dec] |
App route deleted for flow-group |
dapr |
LOG_STD_NO_ACTION |
|
DAPR_RM-6-APP_RT_INSTALL |
6-Information |
[chars] BW:[dec] [chars] |
App route installed for flow-group |
dapr |
LOG_STD_NO_ACTION |
|
DAPR_RM-6-BR_EVENT |
6-Information |
BR [chars] event: [chars] |
RM received event from BR |
dapr |
LOG_STD_ACTION |
|
DAPR_RM-6-RM_RESET |
6-Information |
reason: [chars] |
RM reset due to the mentioned reason |
dapr |
LOG_STD_ACTION |
|
DAPR-4-INTERNAL_ERROR |
4-Warning |
[chars] |
Internal error |
dapr |
LOG_STD_ACTION |
|
DATA_DESCR-3-CTRLR_DECODE |
3-Error |
Lookup Failure: %0-8x.%0-8x.%0-8x.%0-8x.%0-8x [dec]-[dec]/[dec] |
- |
- |
- |
|
DATA_DESCR-3-DEFER_FAILURE |
3-Error |
Defer failure on [chars] for descriptor [dec]-[dec]/[dec]/[dec]/[dec] |
Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An error occurred during the processing of a data descriptor. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized. |
ha-idb-sync |
LOG_STD_ACTION |
|
DATA_DESCR-3-ENTRY_EXPIRED |
3-Error |
Found expired message entry for descriptor [dec]-[dec]/[dec]/[dec]/[dec] |
Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An error occurred during the processing of a data descriptor. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized. |
ha-idb-sync |
LOG_STD_ACTION |
|
DATA_DESCR-3-GENERIC_DECODE |
3-Error |
Lookup Failure: %0-8x.%0-8x.%0-8x.%0-8x.%0-8x [dec]-[dec]/[dec]/[dec]/[dec]/[dec] |
- |
- |
- |
|
DATA_DESCR-3-GENERIC_ENCODE |
3-Error |
Encode failure: [chars] descriptor type=[dec] |
An internal data descriptor could not be encoded for synchronization for the interface or controller in the run-time module specified in the message output. The failure most likely occurred because of a software error. The descriptor type specified in the message output identifies the type of failure. The system state between the active and standby units might not be properly synchronized. |
ha-idb-sync |
LOG_STD_ACTION |
|
DATA_DESCR-3-GENERIC_VIRTUAL_DECODE |
3-Error |
Lookup Failure: %0-8x.%0-8x.%0-8x.%0-8x.%0-8x [dec]-[dec]/[dec]/[dec] |
- |
- |
- |
|
DATA_DESCR-3-HWIDB_DECODE |
3-Error |
Lookup Failure: %0-8x.%0-8x.%0-8x.%0-8x.%0-8x [dec]-[dec]/[dec]/[dec]/[dec] |
- |
- |
- |
|
DATA_DESCR-3-QUEUE_INTERNAL_ERROR |
3-Error |
Internal error on data descriptor queue: [chars] |
Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An error occurred during the processing of a data descriptor. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized. |
ha-idb-sync |
LOG_STD_ACTION |
|
DATA_DESCR-3-SWIDB_DECODE |
3-Error |
Lookup Failure: %0-8x.%0-8x.%0-8x.%0-8x.%0-8x [dec]-[dec]/[dec]/[dec]/[dec]/[dec] |
- |
- |
- |
|
DB_INIT_FAILED-3-MPLS_TE_HA |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
DB_LOCK_MGR-3-INITFAIL |
3-Error |
Initialization of the Database Lock Manager facility failed [chars]. |
An unexpected condition has occurred which resulted in the Database lock manager facililty failing to start. This is a serious problem and means that the Database lock manager facility will not be functional. |
crimson |
LOG_STD_ACTION |
|
DB_LOCK_MGR-3-OPERFAIL |
3-Error |
Database Lock Manager Operational failure [chars]. |
An unexpected condition has occurred which resulted in the Database lock manager detecting an operational failure. This means Database lock manager has detected and corrected an unexpected failure condition. |
crimson |
LOG_STD_ACTION |
|
DB_NTFY_MGR-3-INITFAIL |
3-Error |
Initialization of the Database Notification Manager facility failed [chars]. |
An unexpected condition has occurred which resulted in the Database notification manager facility failing to start. This is a serious problem and means that the Database notification manager facility will not be functional. |
crimson |
LOG_STD_ACTION |
|
DB_NTFY_MGR-3-REQPROCFAIL |
3-Error |
Database Notification Manager Request Processing facility failed [chars]. |
An unexpected condition has occurred which resulted in the Database notification manager facility failing to process a request. This means that some part of Database notification manager facility will not be functional. |
crimson |
LOG_STD_ACTION |
|
DBCONN-3-BADLICENSEKEY |
3-Error |
Bad license key configured for Database Connection. |
The license key configured with the dbconn license configuration\n\ command is not valid. |
dbconn |
"Check that the license key was entered correctly in the dbconn\n\ license configuration command. Refer to the dbconn feature documentation\n\ for information on how to obtain a valid license key." |
|
DBCONN-3-BADMODE |
3-Error |
Unknown mode '[chars]' configured for server [chars] |
The mode configured for the dbconn server was rejected by the\n\ remote database server. |
dbconn |
"Contact your SNA network administrator to determine the correct\n\ name of the mode to use to connect to DB2 on the remote database\n\ server." |
|
DBCONN-3-BADRLU |
3-Error |
Bad remote LU '[chars]' configured for server [chars] |
The remote LU configured for the dbconn server is incorrect. |
dbconn |
"Contact your SNA network administrator to determine the correct\n\ name of the remote LU for DB2 on the remote database server. Be sure to\n\ check that the SNA network name is correct as well as the LU name." |
|
DBCONN-3-BADTPNAME |
3-Error |
Bad TP name configured for server [chars] |
The tpname configured for the dbconn server is not recognized by the\n\ remote database server. |
dbconn |
"Configure a TP name that is available on the remote database server.\n\ Most DB2 systems will accept the DRDA default TP name of \x076DB\n\ except for SQL/DS. Contact your SNA network administrator and/or\n\ your DB2 administrator to determine the TP name used by your DB2.\n\ To use the DRDA default do not explicitly configure a TP name for your\n\ dbconn server." |
|
DBCONN-3-DRDASYNTAX |
3-Error |
DRDA protocol error from server [chars] SYNERRCD x'%02X' |
An unexpected DRDA protocol error occurred between dbconn and the\n\ remote database server. |
dbconn |
LOG_STD_ACTION " If possible also provide the output of the debug dbconn drda\n\ command and an SNA line trace between the router and the remote\n\ database server for the period during which this message appeared." |
|
DBCONN-3-LICENSEEXPERROR |
3-Error |
License is expired for Database and Transaction Connection. |
This system is using a temporary key for its Database and Transaction\n\ Connection. The license is expired. |
dbconn |
"Contact StarQuest Software to acquire a permanent key." |
|
DBCONN-3-LICENSEEXPWARNING |
3-Error |
License is about to expire for Database and Transaction Connection. |
This system is using a temporary key for its Database and Transaction\n\ Connection. The license is about to expire. |
dbconn |
"Contact StarQuest Software to acquire a permanent key." |
|
DBCONN-3-LICENSEHWWARNING |
3-Error |
Number of connections for TXCONN and DBCONN is at 90%% license limit. |
The number of allowed Database and Transaction Connection client \n\ in this system is reaching the limit. |
dbconn |
"Contact StarQuest Software to acquire more license." |
|
DBCONN-5-IDLETIMEOUT |
5-Notice |
Client [inet] connected to server [chars] has timed out after %TE. |
The client was idle for too long and the idle timeout configured\n\ for the dbconn server expired. |
dbconn |
"This is an informational message only. " LOG_STD_NO_ACTION |
|
DBCONN-5-PWDEXPIRED |
5-Notice |
APPC security failed client [inet] using userid '[chars]' for server [chars] |
The password passed in by the client was rejected by the remote database \n\ server because it's expired. |
dbconn |
"This is an informational message only. " LOG_STD_NO_ACTION |
|
DBCONN-5-PWDINVALID |
5-Notice |
APPC security failed client [inet] using userid '[chars]' for server [chars] |
The password passed in by the client was rejected by the remote database \n\ server. |
dbconn |
"This is an informational message only. " LOG_STD_NO_ACTION |
|
DBCONN-5-PWDMISSING |
5-Notice |
APPC security failed client [inet] using userid '[chars]' for server [chars] |
The remote database server requires a userid and password but the \n\ password was not provided. |
dbconn |
"This is an informational message only. " LOG_STD_NO_ACTION |
|
DBCONN-5-SECFAIL |
5-Notice |
APPC security failed client [inet] using userid '[chars]' for server [chars] |
The userid and/or password passed in by the client were rejected by\n\ the remote database server. |
dbconn |
"This is an informational message only. " LOG_STD_NO_ACTION |
|
DBCONN-5-SECUNKNOWN |
5-Notice |
APPC security failed client [inet] using userid '[chars]' for server [chars] |
An unspecified security failure has occurred. The database host system may\n\ be able to provide more specific information. |
dbconn |
"This is an informational message only. " LOG_STD_NO_ACTION |
|
DBCONN-5-UIDINVALID |
5-Notice |
APPC security failed client [inet] using userid '[chars]' for server [chars] |
The userid used to connect to the remote database server is not valid. |
dbconn |
"This is an informational message only. " LOG_STD_NO_ACTION |
|
DBCONN-5-UIDMISSING |
5-Notice |
APPC security failed client [inet] using userid '[chars]' for server [chars] |
The remote database server requires a userid but the \n\ userid was not provided. |
dbconn |
"This is an informational message only. " LOG_STD_NO_ACTION |
|
DBCONN-5-UIDREVOKED |
5-Notice |
APPC security failed client [inet] using userid '[chars]' for server [chars] |
The userid used to connect to the remote database server has been revoked. |
dbconn |
"This is an informational message only. " LOG_STD_NO_ACTION |
|
DBCONN-5-WLMDOWN |
5-Notice |
All WLM routes on server [chars] have become unavailable. Recovery is in progress. |
A load balanced WLM server has lost connectivity to all destinations in its server list. All client\n\ connections to this server will be rejected until a host in the complex becomes available again. |
dbconn |
"This is an informational message only. " LOG_STD_NO_ACTION |
|
DBCONN-5-WLMMISMATCH |
5-Notice |
WLM transport type mismatch on server [chars]. |
The transport type within a server list received from a Workload Manager \n\ load balanced database does not match the transport type of the corresponding \n\ dbconn server. If the conflicting server list specifies SNA transport type the \n\ default mode #INTER will be used to establish the connection. |
dbconn |
"This is an informational message only. " LOG_STD_NO_ACTION |
|
DBMS-2- INITIALIZATION_FAILED |
2-Critical |
DBLIB initialization failed for [chars] |
Initialization of the database library failed. |
cmts-platform-infr |
LOG_STD_RECUR_ACTION |
|
DBMS-3- API |
3-Error |
[chars] |
The specified operation in the api component failed. |
cmts-platform-infr |
LOG_STD_NO_ACTION |
|
DBMS-3- BUNDLE |
3-Error |
[chars] |
The specified operation in the bundle component failed. |
cmts-platform-infr |
LOG_STD_NO_ACTION |
|
DBMS-3- CONNECTION |
3-Error |
[chars] |
The specified operation in the connection component failed. |
cmts-platform-infr |
LOG_STD_NO_ACTION |
|
DBMS-3- DATABASE |
3-Error |
[chars] |
The specified operation in the database component failed. |
cmts-platform-infr |
LOG_STD_NO_ACTION |
|
DBMS-3- ENGINE |
3-Error |
[chars] |
The specified operation in the engine component failed. |
cmts-platform-infr |
LOG_STD_NO_ACTION |
|
DBMS-3- IPC_ERROR |
3-Error |
DBLIB ipc failure : [chars] |
An internal inter-process communication error has occurred. |
cmts-platform-infr |
LOG_STD_ACTION |
|
DBMS-3- KEY |
3-Error |
[chars] |
The specified operation in the key component failed. |
cmts-platform-infr |
LOG_STD_NO_ACTION |
|
DBMS-3- MALLOC_FAILED |
3-Error |
DBLIB malloc failed for [chars] size [dec] |
An internal memory allocation has failed. |
cmts-platform-infr |
LOG_STD_RECUR_ACTION |
|
DBMS-3- MESSAGE |
3-Error |
[chars] |
The specified operation in the message component failed. |
cmts-platform-infr |
LOG_STD_NO_ACTION |
|
DBMS-3- PORT |
3-Error |
[chars] |
The specified operation in the port component failed. |
cmts-platform-infr |
LOG_STD_NO_ACTION |
|
DBMS-3- REPLICATION |
3-Error |
[chars] |
The specified operation in the replication component failed. |
cmts-platform-infr |
LOG_STD_NO_ACTION |
|
DBMS-3- SHADOW |
3-Error |
[chars] |
The specified operation in the shadow component failed. |
cmts-platform-infr |
LOG_STD_NO_ACTION |
|
DBMS-3- SNAPSHOT |
3-Error |
[chars] |
The specified operation in the snapshot component failed. |
cmts-platform-infr |
LOG_STD_NO_ACTION |
|
DBMS-3- TABLE |
3-Error |
[chars] |
The specified operation in the table component failed. |
cmts-platform-infr |
LOG_STD_NO_ACTION |
|
DBMS-3- TDL_ERROR |
3-Error |
DBLIB TDL error : [chars] |
A TDL messaging error has been detected. |
cmts-platform-infr |
LOG_STD_ACTION |
|
DBMS-5- CONNECTION_DROP |
5-Notice |
DBLIB connection from [chars] to [chars] dropped |
An internal socket connection has been dropped. |
cmts-platform-infr |
LOG_STD_RECUR_ACTION |
|
DBUS-2-UNKNOWN |
2-Critical |
Slot [dec] unknown controller type 0x[hec] ignoring |
A processor reported a controller type that is unknown to the system.\n\ The processor will not be used and needs to be repaired. |
- |
LOG_STD_SH_TECH_ACTION |
|
DBUS-3-BADCTRLRTYPE |
3-Error |
Invalid controller type [dec] in slot [dec] |
An interface processor responded with an unknown or illegal controller\n\ type when queried. This should not happen unless the running software\n\ does not support the interface processor in question or the interface\n\ processor fails. |
- |
LOG_STD_ACTION |
|
DBUS-3-BADEEPROM |
3-Error |
Invalid EEPROM data found for card in slot [dec] card disabled |
The ID EEPROM on the indicated card is not programmed correctly. |
- |
"Call your Cisco technical support representative for a replacement." |
|
DBUS-3-BADHSACONF |
3-Error |
Down rev RSP EPROM found HSA system upgrade EPROM or remove one RSP |
A software or hardware error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
DBUS-3-CXBUSERR |
3-Error |
Slot [dec] CBus Error |
- |
- |
"Reinstall the processor or download the microcode. " LOG_STD_RECUR_ACTION |
|
DBUS-3-DAUGHTER_STATS |
3-Error |
Slot [dec] control 0x[hec] status 0x[hec] |
A processor reported an error. This message is sent out in conjunction\n\ with other error messages to provide additional information. |
- |
LOG_STD_SH_TECH_ACTION |
|
DBUS-3-DBUSDISABLED |
3-Error |
Slot [dec] disabled will be restarted. |
A processor was disabled due to an error. The processor will be reset\n\ and not used until the next OIR event or microcode download when it\n\ will be retested. |
- |
"Reinstall the processor or download the microcode. " LOG_STD_RECUR_ACTION |
|
DBUS-3-DBUSINTERR |
3-Error |
Slot [dec] Internal Error |
A processor reported an internal error. The processor will be reset\n\ and not used until the next OIR event or microcode download when it\n\ will be retested. |
- |
"Reinstall the processor or download the microcode. " LOG_STD_RECUR_ACTION |
|
DBUS-3-DBUSINTERRSWSET |
3-Error |
Slot [dec] Internal Error due to VIP crash |
A processor reported an error. The processor will be reset\n\ and not used until the next OIR event or microcode download when it\n\ will be retested. |
- |
"Reinstall the processor or download the microcode. " LOG_STD_RECUR_ACTION |
|
DBUS-3-MSGOVERFLOW |
3-Error |
Slot [dec] too many DBUS messages |
A board in the slot identified in the error message tried to send\n\ too many logger messages. |
- |
LOG_STD_SH_TECH_ACTION |
|
DBUS-3-MSGPABADCONFIG |
3-Error |
Slot [dec] has an unsucessfully configured PA in bay [dec] |
The PA in the slot is not sucessfully configured either because the VIP is\n\ incompatible with it or because the IOS has no pertinent drivers. |
- |
"Please refer to the documentation of the PA to get a list of compatible\n\ VIP's. If the VIP that contains the PA is listed as supported please refer to\n\ the CCO page for IOS versions that support the PA. Otherwise seat the PA in one\n\ of the supported VIP's and verify that the IOS version supports the PA." |
|
DBUS-3-MSGPAUNSUP |
3-Error |
Slot [dec] has an unsupported PA in bay [dec] |
The PA in the slot is not supported either because the VIP is\n\ incompatible with it or because the IOS has no pertinent drivers. |
- |
"Please refer to the documentation of the PA to get a list of compatible\n\ VIP's. If the VIP that contains the PA is listed as supported please refer to\n\ the CCO page for IOS versions that support the PA. Otherwise seat the PA in one\n\ of the supported VIP's and verify that the IOS version supports the PA." |
|
DBUS-3-NOMAGIC |
3-Error |
No magic number found in RP1 EEPROM |
The structure containing the system MAC address needed by the OIR\n\ facility cannot be found in the RP EEPROM. The RP must be returned for\n\ reprogramming. |
- |
"Return the RP for reprogramming and call your Cisco technical\n\ support representative for assistance." |
|
DBUS-3-NORESP |
3-Error |
bad or no response slot [dec] |
A board in the slot identified in the error message failed to\n\ respond. |
- |
LOG_STD_SH_TECH_ACTION |
|
DBUS-3-NOSUPPORT |
3-Error |
No driver support in this image for [chars] in slot [dec] card type [dec] - disabled |
The Cisco IOS image does not have driver support code\n\ for the specified interface processor. |
- |
"Remove the unsupported interface processor card or\n\ reload the router with a Cisco IOS image that has driver\n\ support code for that interface processor card." |
|
DBUS-3-ORFS_NOTINITIALIZED |
3-Error |
ORFS is not initialized |
When oir-remove-failing-slot is invoked the software attempts to initialize parameters. This initialization failed and the service will not be available. |
rsp |
"If this message is seen please try entering the service " "oir-remove-failing-slot command again. This message should " "not cause any functional failures. If the message does cause " "an IOS performance issue please check Bug Toolkit on the web " "for existing bugs and if none are found " LOG_STD_SH_TECH_ACTION |
|
DBUS-3-SLOTCOMP |
3-Error |
Slot [dec] dbus error slot 0x[hec] and complement 0x[hec] do not match |
A processor reported a mismatch between the contents of the slot\n\ register and its complement. This condition indicates a hardware\n\ failure in the diagnostic bus controller on that processor or on the\n\ diagnostic bus. The processor will be reset and not used until the next\n\ OIR event or microcode download when it will be retested. |
- |
LOG_STD_SH_TECH_ACTION |
|
DBUS-3-SW_NOTRDY |
3-Error |
DBUS software not ready for slot [dec] after [chars] elapsed [dec] status 0x[hec] |
An interface processor failed to come online after being reset. A software or hardware error occurred. |
rsp c5rsm |
"Please refer to Bug Toolkit on the Cisco web-site to check for " "existing bugs. If you do not find one obtain the output of show " "tech and show log and open a TAC case." |
|
DBUS-3-WCSCTRLRERR |
3-Error |
Slot [dec] WCS Controller Instruction Error |
- |
- |
LOG_STD_SH_TECH_ACTION |
|
DBUS-3-WCSERR |
3-Error |
Slot [dec] WCS controller in error state 0x[hec] resetting |
- |
- |
"Reset the processor and load new microcode. " LOG_STD_RECUR_ACTION |
|
DBUS-3-WCSFLOW |
3-Error |
Slot [dec] flow cntrl error loading WCS last data 0x[hec] pos [dec] |
A processor indicated an error condition while downloading microcode.\n\ The status cmd/data and pos numbers shown in the message reflect the\n\ error condition the last byte of microcode loaded and the position in\n\ the file respectively. If this error appears the microcode download\n\ is aborted and the ROM microcode is loaded. |
- |
LOG_STD_RECUR_ACTION |
|
DBUS-3-WCSLDERR |
3-Error |
Slot [dec] error loading WCS status 0x[hec] cmd/data 0x[hec] pos [dec] |
A processor indicated an error condition while downloading microcode.\n\ The status cmd/data and pos numbers shown in the message reflect the\n\ error condition the last byte of microcode loaded and the position in\n\ the file respectively. If this error appears the microcode download\n\ is aborted and the ROM microcode is loaded. |
- |
LOG_STD_RECUR_ACTION |
|
DBUS-3-WCSPARERR |
3-Error |
Slot [dec] WCS Controller Parity Error |
A processor reported a WCS parity error. The processor will be reset\n\ and not used until the next OIR event or microcode download when it\n\ will be retested. |
- |
"Replace the processor or download microcode. If this message recurs\n\ call your Cisco technical support representative for assistance." |
|
DBUS-3-XILINX |
3-Error |
ready wait timeout slot [dec] |
The field-programmable gate arrays on an interface processor failed to\n\ load after being reset. This indicates a probable software or hardware\n\ problem. |
- |
LOG_STD_ACTION |
|
DC-3-BUILTIN_INIT_FAIL |
3-Error |
[chars] |
Initilization of Device classifier Built-in database failed. So the device classifier will be operationally down. |
dc |
LOG_STD_ACTION |
|
DC-3-BUILTIN_INIT_FAIL |
3-Error |
[chars] |
Initilization of Device classifier Built-in database failed. So the device classifier will be operationally down. |
dc |
LOG_STD_ACTION |
|
DC-3-BUILTIN_INIT_FAIL |
3-Error |
[chars] |
Initilization of Device classifier Built-in database failed. So the device classifier will be operationally down. |
dc |
LOG_STD_ACTION |
|
DC-3-BUILTIN_INIT_FAIL |
3-Error |
[chars] |
Initilization of Device classifier Built-in database failed. So the device classifier will be operationally down. |
dc |
LOG_STD_ACTION |
|
DC-3-CHECK_INIT_FAIL |
3-Error |
[chars] |
Loading of the Checks databae in Device classifier failed. |
dc |
LOG_STD_ACTION |
|
DC-3-CHECK_INIT_FAIL |
3-Error |
[chars] |
Loading of the Checks databae in Device classifier failed. |
dc |
LOG_STD_ACTION |
|
DC-3-CHECK_INIT_FAIL |
3-Error |
[chars] |
Loading of the Checks databae in Device classifier failed. |
dc |
LOG_STD_ACTION |
|
DC-3-CHECK_INIT_FAIL |
3-Error |
[chars] |
Loading of the Checks databae in Device classifier failed. |
dc |
LOG_STD_ACTION |
|
DC-3-DB_INIT_FAIL |
3-Error |
Device Classifier disabled. [chars] initialization failed |
Initilization of Device classifier Internal database failed So the device classifier will be operationally down. |
dc |
LOG_STD_ACTION |
|
DC-3-DB_INIT_FAIL |
3-Error |
Device Classifier disabled. [chars] initialization failed |
Initilization of Device classifier Internal database failed So the device classifier will be operationally down. |
dc |
LOG_STD_ACTION |
|
DC-3-DB_INIT_FAIL |
3-Error |
Device Classifier disabled. [chars] initialization failed |
Initilization of Device classifier Internal database failed So the device classifier will be operationally down. |
dc |
LOG_STD_ACTION |
|
DC-3-DB_INIT_FAIL |
3-Error |
Device Classifier disabled. [chars] initialization failed |
Initilization of Device classifier Internal database failed So the device classifier will be operationally down. |
dc |
LOG_STD_ACTION |
|
DC-3-DC_ADD_USR_CHK |
3-Error |
Addition of custom checks failed : [chars]. |
Internal error returned during addition of custom checks. |
dc |
- |
|
DC-3-DC_ADD_USR_PROFILE |
3-Error |
Addition of custom profiles failed : [chars]. |
Internal error returned during addition of custom profiles. |
dc |
- |
|
DC-3-DC_ADD_USR_RULE |
3-Error |
Addition of custom rules failed : [chars]. |
Internal error returned during addition of custom rules. |
dc |
- |
|
DC-3-DC_DISABLED |
3-Error |
[chars]. |
The device classifier is disabled due to an error condition encountered during initialization or parsing the profiles |
dc |
"The specified error message is logged." "After the error condition is resolved" "re-enable the device classifier" |
|
DC-3-DC_DISABLED |
3-Error |
[chars]. |
The device classifier is disabled due to an error condition encountered during initialization or parsing the profiles |
dc |
"The specified error message is logged." "After the error condition is resolved" "re-enable the device classifier" |
|
DC-3-DC_DISABLED |
3-Error |
[chars]. |
The device classifier is disabled due to an error condition encountered during initialization or parsing the profiles |
dc |
"The specified error message is logged." "After the error condition is resolved" "re-enable the device classifier" |
|
DC-3-DC_DISABLED |
3-Error |
[chars]. |
The device classifier is disabled due to an error condition encountered during initialization or parsing the profiles |
dc |
"The specified error message is logged." "After the error condition is resolved" "re-enable the device classifier" |
|
DC-3-DISABLE_FAIL |
3-Error |
Failed to disable DC. |
Internal error occured trying to disable Device Classifier. |
dc |
"Please run the command: show macro auto monitor clients and try disabling" "the clients" |
|
DC-3-DISABLE_FAIL |
3-Error |
Failed to disable DC. |
Internal error occured trying to disable Device Classifier. |
dc |
"Please run the command: show macro auto monitor clients and try disabling" "the clients" |
|
DC-3-DISABLE_FAIL |
3-Error |
Failed to disable DC. |
Internal error occured trying to disable Device Classifier. |
dc |
"Please run the command: show macro auto monitor clients and try disabling" "the clients" |
|
DC-3-DISABLE_FAIL |
3-Error |
Failed to disable DC. |
Internal error occured trying to disable Device Classifier. |
dc |
"Please run the command: show macro auto monitor clients and try disabling" "the clients" |
|
DC-3-ENABLE_FAIL |
3-Error |
Failed to enable DC. |
Internal error occured trying to enable Device Classifier. |
dc |
"Please check the previous DC error messages and take the relevant action" |
|
DC-3-ENABLE_FAIL |
3-Error |
Failed to enable DC. |
Internal error occured trying to enable Device Classifier. |
dc |
"Please check the previous DC error messages and take the relevant action" |
|
DC-3-ENABLE_FAIL |
3-Error |
Failed to enable DC. |
Internal error occured trying to enable Device Classifier. |
dc |
"Please check the previous DC error messages and take the relevant action" |
|
DC-3-ENABLE_FAIL |
3-Error |
Failed to enable DC. |
Internal error occured trying to enable Device Classifier. |
dc |
"Please check the previous DC error messages and take the relevant action" |
|
DC-3-FILE_CHECKSUM |
3-Error |
Checksum [chars] failed for the profile file: [chars] |
Checksum computation or verification failed for the profiles file. The profiles in the errored file cannot be loaded into the device classifier. |
dc |
- |
|
DC-3-FILE_CHECKSUM |
3-Error |
Checksum [chars] failed for the profile file: [chars] |
Checksum computation or verification failed for the profiles file. The profiles in the errored file cannot be loaded into the device classifier. |
dc |
- |
|
DC-3-FILE_CHECKSUM |
3-Error |
Checksum [chars] failed for the profile file: [chars] |
Checksum computation or verification failed for the profiles file. The profiles in the errored file cannot be loaded into the device classifier. |
dc |
- |
|
DC-3-FILE_CHECKSUM |
3-Error |
Checksum [chars] failed for the profile file: [chars] |
Checksum computation or verification failed for the profiles file. The profiles in the errored file cannot be loaded into the device classifier. |
dc |
- |
|
DC-3-FILE_READ_ERROR |
3-Error |
Error [chars] the profile file: [chars] |
There was an error reading the profile file contents. The profiles in the errored file cannot be loaded into the device classifier. |
dc |
- |
|
DC-3-FILE_READ_ERROR |
3-Error |
Error [chars] the profile file: [chars] |
There was an error reading the profile file contents. The profiles in the errored file cannot be loaded into the device classifier. |
dc |
- |
|
DC-3-FILE_READ_ERROR |
3-Error |
Error [chars] the profile file: [chars] |
There was an error reading the profile file contents. The profiles in the errored file cannot be loaded into the device classifier. |
dc |
- |
|
DC-3-FILE_READ_ERROR |
3-Error |
Error [chars] the profile file: [chars] |
There was an error reading the profile file contents. The profiles in the errored file cannot be loaded into the device classifier. |
dc |
- |
|
DC-3-HRPC_SYNC |
3-Error |
Error on member switch [dec] error_code = [dec] |
Internal error occured while trying to sync Device Classifier.state |
dc |
"Please check the state of the stack members" |
|
DC-3-HRPC_SYNC |
3-Error |
Error on member switch [dec] error_code = [dec] |
Internal error occured while trying to sync Device Classifier.state |
dc |
"Please check the state of the stack members" |
|
DC-3-HRPC_SYNC |
3-Error |
Error on member switch [dec] error_code = [dec] |
Internal error occured while trying to sync Device Classifier.state |
dc |
"Please check the state of the stack members" |
|
DC-3-HRPC_SYNC |
3-Error |
Error on member switch [dec] error_code = [dec] |
Internal error occured while trying to sync Device Classifier.state |
dc |
"Please check the state of the stack members" |
|
DC-3-INCOMPATIBLE_PROFILE_VERSION |
3-Error |
Incompatible version of Profile detected in [chars]. Expected version:[dec] Version found:[dec] |
An incompatible profile version is detected. The device classifier feature will be operationally down. |
dc |
"Reload the expected version of device profiles file to the " "system and re-enable the device classifier " |
|
DC-3-INCOMPATIBLE_PROFILE_VERSION |
3-Error |
Incompatible version of Profile detected in [chars]. Expected version:[dec] Version found:[dec] |
An incompatible profile version is detected. The device classifier feature will be operationally down. |
dc |
"Reload the expected version of device profiles file to the " "system and re-enable the device classifier " |
|
DC-3-INCOMPATIBLE_PROFILE_VERSION |
3-Error |
Incompatible version of Profile detected in [chars]. Expected version:[dec] Version found:[dec] |
An incompatible profile version is detected. The device classifier feature will be operationally down. |
dc |
"Reload the expected version of device profiles file to the " "system and re-enable the device classifier " |
|
DC-3-INCOMPATIBLE_PROFILE_VERSION |
3-Error |
Incompatible version of Profile detected in [chars]. Expected version:[dec] Version found:[dec] |
An incompatible profile version is detected. The device classifier feature will be operationally down. |
dc |
"Reload the expected version of device profiles file to the " "system and re-enable the device classifier " |
|
DC-3-MAX_OUI_EXCEEDED |
3-Error |
[chars]. |
The maximum number of OUI codes that can be defined in device profiles exceeded the maximum limit. The device classifier will be operationally down if failure occured for the Embedded profiles. |
dc |
"Reduce the number of rules in the device profiles file and" "reload it into the " "system and re-enable the device classifier" |
|
DC-3-MAX_OUI_EXCEEDED |
3-Error |
[chars]. |
The maximum number of OUI codes that can be defined in device profiles exceeded the maximum limit. The device classifier will be operationally down if failure occured for the Embedded profiles. |
dc |
"Reduce the number of rules in the device profiles file and" "reload it into the " "system and re-enable the device classifier" |
|
DC-3-MAX_OUI_EXCEEDED |
3-Error |
[chars]. |
The maximum number of OUI codes that can be defined in device profiles exceeded the maximum limit. The device classifier will be operationally down if failure occured for the Embedded profiles. |
dc |
"Reduce the number of rules in the device profiles file and" "reload it into the " "system and re-enable the device classifier" |
|
DC-3-MAX_OUI_EXCEEDED |
3-Error |
[chars]. |
The maximum number of OUI codes that can be defined in device profiles exceeded the maximum limit. The device classifier will be operationally down if failure occured for the Embedded profiles. |
dc |
"Reduce the number of rules in the device profiles file and" "reload it into the " "system and re-enable the device classifier" |
|
DC-3-MAX_PROFILES_EXCEEDED |
3-Error |
[chars]. |
The maximum number of profiles that can be defined in device profiles exceeded the maximum limit. The device classifier will be operationally down if failure occured for the Embedded profiles. |
dc |
"Reduce the number of rules in the device profiles file and" "reload it into the " "system and re-enable the device classifier" |
|
DC-3-MAX_PROFILES_EXCEEDED |
3-Error |
[chars]. |
The maximum number of profiles that can be defined in device profiles exceeded the maximum limit. The device classifier will be operationally down if failure occured for the Embedded profiles. |
dc |
"Reduce the number of rules in the device profiles file and" "reload it into the " "system and re-enable the device classifier" |
|
DC-3-MAX_PROFILES_EXCEEDED |
3-Error |
total profiles [dec] exceeds the max supported [dec] |
The maximum number of profiles that can be defined in device profiles exceeded the maximum limit. The device classifier will be operationally down if failure occured for the Embedded profiles. |
dc |
"Reduce the number of rules in the device profiles file and" "reload it into the " "system and re-enable the device classifier" |
|
DC-3-MAX_PROFILES_EXCEEDED |
3-Error |
[chars]. |
The maximum number of profiles that can be defined in device profiles exceeded the maximum limit. The device classifier will be operationally down if failure occured for the Embedded profiles. |
dc |
"Reduce the number of rules in the device profiles file and" "reload it into the " "system and re-enable the device classifier" |
|
DC-3-MAX_RULES_EXCEEDED |
3-Error |
[chars]. |
The maximum number of rules that can be defined in device profiles exceeded the maximum limit. The device classifier will be operationally down if failure occured for the Embedded profiles. |
dc |
"Reduce the number of rules in the device profiles file and" "reload it into the " "system and re-enable the device classifier" |
|
DC-3-MAX_RULES_EXCEEDED |
3-Error |
[chars]. |
The maximum number of rules that can be defined in device profiles exceeded the maximum limit. The device classifier will be operationally down if failure occured for the Embedded profiles. |
dc |
"Reduce the number of rules in the device profiles file and" "reload it into the " "system and re-enable the device classifier" |
|
DC-3-MAX_RULES_EXCEEDED |
3-Error |
[chars]. |
The maximum number of rules that can be defined in device profiles exceeded the maximum limit. The device classifier will be operationally down if failure occured for the Embedded profiles. |
dc |
"Reduce the number of rules in the device profiles file and" "reload it into the " "system and re-enable the device classifier" |
|
DC-3-MAX_RULES_EXCEEDED |
3-Error |
[chars]. |
The maximum number of rules that can be defined in device profiles exceeded the maximum limit. The device classifier will be operationally down if failure occured for the Embedded profiles. |
dc |
"Reduce the number of rules in the device profiles file and" "reload it into the " "system and re-enable the device classifier" |
|
DC-3-NO_MEM |
3-Error |
[chars]. |
There is no memory left to allocate in the system The device classifier will be operationally down if failure occured for the Embedded profiles. |
dc |
"Increase the memory size in the system and " "re-enable the device classifier" |
|
DC-3-NO_MEM |
3-Error |
[chars]. |
There is no memory left to allocate in the system The device classifier will be operationally down if failure occured for the Embedded profiles. |
dc |
"Increase the memory size in the system and " "re-enable the device classifier" |
|
DC-3-NO_MEM |
3-Error |
[chars]. |
There is no memory left to allocate in the system The device classifier will be operationally down if failure occured for the Embedded profiles. |
dc |
"Increase the memory size in the system and " "re-enable the device classifier" |
|
DC-3-NO_MEM |
3-Error |
[chars]. |
There is no memory left to allocate in the system The device classifier will be operationally down if failure occured for the Embedded profiles. |
dc |
"Increase the memory size in the system and " "re-enable the device classifier" |
|
DC-3-OUI_INIT_FAIL |
3-Error |
OUI Table initialization failed for [chars] |
Loading of the OUI databae in Device classifier failed. |
dc |
LOG_STD_ACTION |
|
DC-3-OUI_INIT_FAIL |
3-Error |
OUI Table initialization failed for [chars] |
Loading of the OUI databae in Device classifier failed. |
dc |
LOG_STD_ACTION |
|
DC-3-OUI_INIT_FAIL |
3-Error |
OUI Table initialization failed for [chars] |
Loading of the OUI databae in Device classifier failed. |
dc |
LOG_STD_ACTION |
|
DC-3-OUI_INIT_FAIL |
3-Error |
OUI Table initialization failed for [chars] |
Loading of the OUI databae in Device classifier failed. |
dc |
LOG_STD_ACTION |
|
DC-3-PATTERN_NOT_FOUND |
3-Error |
[chars] |
The device profiles file parsing failed. This indicates that the file may be corrupt. The device classifier will be operationally down if failure occured for the Embedded profiles. |
dc |
"Reload the Device Profiles file to the flash and re-enable the device classifier" |
|
DC-3-PATTERN_NOT_FOUND |
3-Error |
[chars] |
The device profiles file parsing failed. This indicates that the file may be corrupt. The device classifier will be operationally down if failure occured for the Embedded profiles. |
dc |
"Reload the Device Profiles file to the flash and re-enable the device classifier" |
|
DC-3-PATTERN_NOT_FOUND |
3-Error |
[chars] |
The device profiles file parsing failed. This indicates that the file may be corrupt. The device classifier will be operationally down if failure occured for the Embedded profiles. |
dc |
"Reload the Device Pr/scratch/stevenl/polaris/wab_amur_eedge_polaris/novaofiles file to the flash and re-enable the device classifier" |
|
DC-3-PATTERN_NOT_FOUND |
3-Error |
[chars] |
The device profiles file parsing failed. This indicates that the file may be corrupt. The device classifier will be operationally down if failure occured for the Embedded profiles. |
dc |
"Reload the Device Pr/scratch/stevenl/polaris/wab_amur_eedge_polaris/novaofiles file to the flash and re-enable the device classifier" |
|
DC-3-SM_API |
3-Error |
[chars] return [chars]. |
Internal error returned by Session Manager api. |
dc |
- |
|
DC-3-SM_API |
3-Error |
[chars] return [chars]. |
Internal error returned by Session Manager api. |
dc |
- |
|
DC-3-SM_API |
3-Error |
[chars] return [chars]. |
Internal error returned by Session Manager api. |
dc |
- |
|
DC-3-SM_API |
3-Error |
[chars] return [chars]. |
Internal error returned by Session Manager api. |
dc |
- |
|
DC-3-SM_GET |
3-Error |
Failed to get [chars]. |
Internal error occured during communication with Session Manager. This may cause the show command not to display the device classification results. |
dc |
- |
|
DC-3-SM_GET |
3-Error |
Failed to get [chars]. |
Internal error occured during communication with Session Manager. This may cause the show command not to display the device classification results. |
dc |
- |
|
DC-3-SM_GET |
3-Error |
Failed to get [chars]. |
Internal error occured during communication with Session Manager. This may cause the show command not to display the device classification results. |
dc |
- |
|
DC-3-SM_GET |
3-Error |
Failed to get [chars]. |
Internal error occured during communication with Session Manager. This may cause the show command not to display the device classification results. |
dc |
- |
|
DC-3-SM_INIT_FAIL |
3-Error |
Device Classifier disabled. [chars] initialization failed |
Registraton of Device classifier with SM failed. So the device classifier will be operationally down. |
dc |
LOG_STD_ACTION |
|
DC-3-SM_INIT_FAIL |
3-Error |
Device Classifier disabled. [chars] initialization failed |
Registraton of Device classifier with SM failed. So the device classifier will be operationally down. |
dc |
LOG_STD_ACTION |
|
DC-3-SM_INIT_FAIL |
3-Error |
Device Classifier disabled. [chars] initialization failed |
Registraton of Device classifier with SM failed. So the device classifier will be operationally down. |
dc |
LOG_STD_ACTION |
|
DC-3-SM_INIT_FAIL |
3-Error |
Device Classifier disabled. [chars] initialization failed |
Registraton of Device classifier with SM failed. So the device classifier will be operationally down. |
dc |
LOG_STD_ACTION |
|
DC-3-SM_UPDATE |
3-Error |
Failed to update [chars]. |
Internal error occured during device classification . This may cause the device to be unknown. |
dc |
- |
|
DC-3-SM_UPDATE |
3-Error |
Failed to update [chars]. |
Internal error occured during device classification . This may cause the device to be unknown. |
dc |
- |
|
DC-3-SM_UPDATE |
3-Error |
Failed to update [chars]. |
Internal error occured during device classification . This may cause the device to be unknown. |
dc |
- |
|
DC-3-SM_UPDATE |
3-Error |
Failed to update [chars]. |
Internal error occured during device classification . This may cause the device to be unknown. |
dc |
- |
|
DC-4-FILE_OPEN_WARNING |
4-Warning |
Not able to open [chars] |
The device classifier did not find the default profile file or it may be corrupted. DC is working using built-in profiles. |
dc |
" Perform archive download using the tar bundle image to install " " the profile file in the flash. " " Reload the switch with the image to see the warning message is gone. " |
|
DC-4-FILE_OPEN_WARNING |
4-Warning |
Not able to open [chars] |
The device classifier did not find the default profile file or it may be corrupted. DC is working using built-in profiles. |
dc |
" Perform archive download using the tar bundle image to install " " the profile file in the flash. " " Reload the switch with the image to see the warning message is gone. " |
|
DC-4-FILE_OPEN_WARNING |
4-Warning |
Not able to open [chars] |
The device classifier did not find the default profile file or it may be corrupted. DC is working using built-in profiles. |
dc |
" Perform archive download using the tar bundle image to install " " the profile file in the flash. " " Reload the switch with the image to see the warning message is gone. " |
|
DC-4-FILE_OPEN_WARNING |
4-Warning |
Not able to open [chars] |
The device classifier did not find the default profile file or it may be corrupted. DC is working using built-in profiles. |
dc |
" Perform archive download using the tar bundle image to install " " the profile file in the flash. " " Reload the switch with the image to see the warning message is gone. " |
|
DC-6-DEFAULT_INIT_INFO |
6-Information |
[chars] |
The default profiles are not loaded and those devices will not be classified. Device classifier will continue to work with built-in profiles. |
dc |
LOG_STD_ACTION |
|
DC-6-DEFAULT_INIT_INFO |
6-Information |
[chars] |
The default profiles are not loaded and those devices will not be classified. Device classifier will continue to work with built-in profiles. |
dc |
LOG_STD_ACTION |
|
DC-6-DEFAULT_INIT_INFO |
6-Information |
[chars] |
The default profiles are not loaded and those devices will not be classified. Device classifier will continue to work with built-in profiles. |
dc |
LOG_STD_ACTION |
|
DC-6-DEFAULT_INIT_INFO |
6-Information |
[chars] |
The default profiles are not loaded and those devices will not be classified. Device classifier will continue to work with built-in profiles. |
dc |
LOG_STD_ACTION |
|
DCA_INFRA-2-DCA_PROXY_IPC_INIT_FAILED |
2-Critical |
DCA IPC initialization failure result: [dec]. |
Cisco internal software error. DCA initialization detected that the Proxy IPC interface initialization failed. |
esg-dp-infra |
"File a bug with the platform DCA infra team" |
|
DCA_INFRA-2-DCA_PROXY_IPC_SEND_FAIL |
2-Critical |
DCA IPC response send failure result: [dec]. |
Cisco internal software error. DCA detected an error when sending a IPC response. |
esg-dp-infra |
"File a bug with the platform DCA infra team" |
|
DCA_INFRA-3-DCA_ASYN_CB_ERROR_RSP |
3-Error |
DCA received an asyn callback with an error response trans_id: [dec] Result: [dec] |
DCA received an asyn callback with an error response |
esg-dp-infra |
"File a bug with the platform DCA infra team" |
|
DCA_INFRA-3-DCA_ASYN_CB_SEQ_MISMATCH |
3-Error |
DCA received an asyn callback with an unexpected sequence number trans_id: [dec] |
DCA received an asyn callback with an unexpected sequence number |
esg-dp-infra |
"File a bug with the platform DCA infra team" |
|
DCA_INFRA-3-DCA_ASYN_CB_STATE_MISMATCH |
3-Error |
DCA received an asyn callback while in an unexpected state trans_id: [dec] |
DCA received an asyn callback while in an unexpected state |
esg-dp-infra |
"File a bug with the platform DCA infra team" |
|
DCA_INFRA-3-DCA_INV_PROXY_MSG |
3-Error |
DCA Proxy received invalid Message ID [dec] |
Cisco internal software error. DCA Proxy received an invalid Message ID. This message will be ignored. |
esg-dp-infra |
"File a bug with the platform DCA infra team" |
|
DCA_INFRA-3-DCA_PROXY_IPC_ALLOC_FAIL |
3-Error |
DCA Proxy [chars] response lost due to buffer allocation failure |
Cisco internal software error. DCA Proxy message processing detected a IPC buffer allocation failure during response processing. The associated DCA functionality may not be fully functional as a result of this condition. |
esg-dp-infra |
"File a bug with the platform DCA infra team" |
|
DCA_INFRA-3-DCA_REQUEST_WHILE_BUSY |
3-Error |
DCA received a new request while previous request in progress |
DCA received a new request while previous request in progress |
esg-dp-infra |
"File a bug with the platform DCA infra team" |
|
DCA_INFRA-3-DCA_STATE_TRANS_ERROR |
3-Error |
DCA encountered an error during state transition processing trans_id: [dec] |
DCA encountered an error during state transition processing |
esg-dp-infra |
"File a bug with the platform DCA infra team" |
|
DCA_INFRA-3-DCA_STATE_TRANS_FAIL |
3-Error |
DCA encountered an state transition error trans_id: [dec] Result: [dec] |
DCA encountered an state transition error |
esg-dp-infra |
"File a bug with the platform DCA infra team" |
|
DEAD-4-SCARLET |
4-Warning |
* Interface [chars]: I knew without asking she was into the blues |
- |
- |
- |
|
DEAD-4-SCARLET |
4-Warning |
- |
- |
- |
- |
|
DEAD-4-SCARLET |
4-Warning |
* Interface [chars]: I knew without asking she was into the blues |
- |
- |
- |
|
DEAD-4-SCARLET |
4-Warning |
- |
- |
- |
- |
|
DEAD-4-SCARLET |
4-Warning |
* Interface [chars]: I knew without asking she was into the blues |
- |
- |
- |
|
DEAD-4-SCARLET |
4-Warning |
- |
- |
- |
- |
|
DEAD-4-SCARLET |
4-Warning |
* Interface [chars]: I knew without asking she was into the blues |
- |
- |
- |
|
DEAD-4-SCARLET |
4-Warning |
- |
- |
- |
- |
|
DEADADJ-3-LCON |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
DEC21140-1-INITFAIL |
1-Alert |
msgtxt_initfail |
The Fast Ethernet port initialization failed. This can be\n\ caused by disconnected cabling or a failure to detect the\n\ media in use. |
- |
"Check the cabling. Try initializing the port again. " LOG_STD_SH_TECH_ACTION |
|
DEC21140-3-RXFIFO |
3-Error |
Unit [dec] receive FIFO overflow |
The Fast Ethernet receiver was unable to hand received data to a\n\ hardware buffer because the input rate exceeded the receiver's\n\ ability to handle the data. This could be caused by excessive\n\ system load. |
- |
LOG_STD_RECUR_ACTION |
|
DEC21140-3-UNDERFLO |
3-Error |
Unit [dec] Tx FIFO underflow |
The Fast Ethernet transmitter was ready to transmit before a packet\n\ was in the buffer. This could be caused by excessive system load. |
- |
LOG_STD_RECUR_ACTION |
|
DEC21140-5-COLL |
5-Notice |
Unit [dec] excessive collisions |
A Fast Ethernet packet has been dropped because too many\n\ attempts to transmit it were stopped by collisions. This can\n\ be caused by a Fast Ethernet segment which is full to capacity\n\ or by other equipment on the LAN malfunctioning. |
- |
LOG_STD_NO_ACTION |
|
DEC21140-5-JABBER |
5-Notice |
Unit [dec] jabber timeout |
The transmitter for the port adapter's Fast Ethernet port has\n\ timed out and caused the transmission of a packet to fail. |
- |
LOG_STD_RECUR_ACTION |
|
DEC21140-5-LATECOLL |
5-Notice |
Unit [dec] late collision error |
Late collisions happen when a collision occurs after transmitting \n\ the preamble. The packet will be retransmitted but this could \n\ indicate that another device is failing to detect when the network \n\ is in use. |
- |
"If this recurs check for malfunctions in other devices on the \n\ Fast Ethernet." |
|
DEC21140-5-LOSTCARR |
5-Notice |
Unit [dec] lost carrier |
The Fast Ethernet port lost carrier while transmitting\n\ meaning that it is no longer receiving signals from the LAN.\n\ This can be caused by disconnected Fast Ethernet cabling or\n\ a transceiver failure. |
- |
"If the message recurs check your Fast Ethernet cabling and port\n\ adapter first. If the problem cannot be located follow these\n\ directions. " LOG_STD_RECUR_ACTION |
|
DEC21140-5-NOCARR |
5-Notice |
Unit [dec] no carrier |
The Fast Ethernet port did not find a carrier when preparing to\n\ transmit a packet meaning that it is no longer receiving signals\n\ from the LAN. This can be caused by disconnected Fast Ethernet\n\ cabling or a transceiver failure. |
- |
"Check your Fast Ethernet cabling and port adapter. " LOG_STD_RECUR_ACTION |
|
DEC21140-5-WATCHDOG |
5-Notice |
Unit [dec] enormous packet received |
A packet received via Fast Ethernet was dropped due to excessive \n\ size. |
- |
"Adjust the MTU of the interface if necessary. Otherwise\n\ no action is required." |
|
DECLASSIFICATION-3-UNABLE_TO_RESET_CONFIG |
3-Error |
[chars] |
The system is unable to reset the configuration |
firmware |
LOG_STD_ACTION |
|
DECLASSIFICATION-3-UNABLE_TO_RESET_CONFIG |
3-Error |
[chars] |
The system is unable to reset the configuration |
firmware |
LOG_STD_ACTION |
|
DECLASSIFICATION-3-UNABLE_TO_RESET_CONFIG |
3-Error |
[chars] |
The system is unable to reset the configuration |
firmware |
LOG_STD_ACTION |
|
DECLASSIFICATION-5-CONFIG_IS_RESET |
5-Notice |
[chars] |
The configuration is reset and the system will now reboot |
firmware |
LOG_STD_ACTION |
|
DECLASSIFICATION-5-CONFIG_IS_RESET |
5-Notice |
[chars] |
The configuration is reset and the system will now reboot |
firmware |
LOG_STD_ACTION |
|
DECLASSIFICATION-5-CONFIG_IS_RESET |
5-Notice |
[chars] |
The configuration is reset and the system will now reboot |
firmware |
LOG_STD_ACTION |
|
DECONFIG_SHUTDOWN-6-LDP |
6-Information |
ERRMSG_NOFLAGS |
- |
- |
- |
|
DEFCASE_BINDING_PIE-3-LCON |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
DEREG_FAIL-3-MPLS_TE_EXT_FWDG |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
DFP-4-AGENT_NOT_FOUND |
4-Warning |
[chars] Service has not been registered with DFP. |
No such service registered with DFP subystem. |
dfp |
LOG_STD_RECUR_ACTION |
|
DFP-4-BAD_LISTEN |
4-Warning |
Service [chars] - Listen failed |
Listen for DFP Manager failed. |
dfp |
LOG_STD_RECUR_ACTION |
|
DFP-4-BAD_POINTER |
4-Warning |
[chars] Application did not set pointer |
Application passed invalid pointer to DFP subsystem |
dfp |
LOG_STD_RECUR_ACTION |
|
DFP-4-BAD_SEND |
4-Warning |
Manager [inet]:[dec] - Send failed |
Sending a message to DFP Manager failed |
dfp |
LOG_STD_RECUR_ACTION |
|
DFP-4-BIND_FAIL |
4-Warning |
Failure binding port [dec] to socket for service [chars]. |
Problem with call to socket bind. |
dfp |
LOG_STD_RECUR_ACTION |
|
DFP-4-ENQUEUE |
4-Warning |
Process enqueue failed: [chars] |
An unexpected error occurred while enqueueing a DFP element |
dfp |
LOG_STD_RECUR_ACTION |
|
DFP-4-NO_PARSE |
4-Warning |
Manager [inet]: Service [chars] - Could not parse message |
Could not parse message from DFP Manager |
dfp |
LOG_STD_RECUR_ACTION |
|
DFP-4-NO_PROCESS_START |
4-Warning |
Could not start process for service [chars] |
Could not start DFP Process for service [chars] |
dfp |
LOG_STD_RECUR_ACTION |
|
DFP-4-NO_QUEUE_REQUEST |
4-Warning |
Could not queue request for [chars] for service [chars] |
Could not queue request to the DFP process for specific action |
dfp |
LOG_STD_RECUR_ACTION |
|
DFP-4-NUM_TOO_LARGE |
4-Warning |
[chars] Application sent too many values |
Application sent too many values to DFP subsystem |
dfp |
LOG_STD_RECUR_ACTION |
|
DFP-4-PACKET_TOO_SMALL |
4-Warning |
The DFP packet is too small from manager [inet] service [chars]. |
A DFP packet has been received that is too small. |
dfp |
LOG_STD_RECUR_ACTION |
|
DFP-4-READ_ERR |
4-Warning |
Manager [inet]: Service [chars] - Too many read errors |
Too many errors reading message header from DFP Manager |
dfp |
LOG_STD_RECUR_ACTION |
|
DFP-4-REPEAT_SERVICE_INIT |
4-Warning |
Service [chars] is already intialized cannot re-initialize |
The application has atempted to re-initialize a service |
dfp |
LOG_STD_RECUR_ACTION |
|
DFP-4-SECURITY_FAIL |
4-Warning |
[chars] security information in CASA packet from manager [inet] service [chars]. |
Security check failed. |
casa |
"Make sure all CASA/DFP systems are configured with the same password." |
|
DFP-4-SOCK_ERR |
4-Warning |
Manager [inet]: Service [chars] - Socket_recv error [dec] |
Socket_recv error receiving message from DFP Manager |
dfp |
LOG_STD_RECUR_ACTION |
|
DFP-4-STRING_TOO_LONG |
4-Warning |
The string [chars] exceeds 15 characters - too long for service name. |
The user input a service string that exceeds 15 characters |
dfp |
LOG_STD_RECUR_ACTION |
|
DFP-4-SUBSYS_NOT_UP |
4-Warning |
Service [chars] - attempted to register before DFP Subsytem is up. |
Problem with order of subsystem initialization. |
dfp |
LOG_STD_RECUR_ACTION |
|
DFP-4-UKN_CON |
4-Warning |
Manager [inet] Service [chars] - Unknown connection state [dec] |
Unknown connection state processing DFP timer |
dfp |
LOG_STD_RECUR_ACTION |
|
DFP-4-UNK_TYPE |
4-Warning |
Manager [inet]: Service [chars] - Unknown message type [dec] |
Message from DFP Manager has unknown type |
dfp |
LOG_STD_RECUR_ACTION |
|
DHCP_SNOOPING_CAT3550-3-MVR_INSTALL |
3-Error |
Cannot install [chars] ACLs for DHCP Snooping probably no TCAM space |
When DHCP Snooping is enabled ACLs need to be installed into the TCAM. This will fail if there is insufficient space in the TCAM. |
firmware |
"Reduce the number of input and/or output" "PACLs and/or VACLs to make space in the TCAM." |
|
DHCP_SNOOPING_CAT3550-3-UNEXPECTED_EVENT |
3-Error |
Process received unknown event major [hec] minor [hec]. |
- |
- |
- |
|
DHCP_SNOOPING_ISSU-2-GET_BUFFER |
2-Critical |
DHCP Snooping ISSU client failed to get buffer for message. Error: [dec] [chars] |
The DHCP Snooping 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. |
dhcp-snooping |
"show logging and show checkpoint client" |
|
DHCP_SNOOPING_ISSU-2-INIT |
2-Critical |
DHCP Snooping ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The DHCP Snooping 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. |
dhcp-snooping |
LOG_STD_ACTION |
|
DHCP_SNOOPING_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
DHCP Snooping ISSU client failed to send negotiation message. Error: [dec] [chars] |
The DHCP Snooping 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. |
dhcp-snooping |
"show logging and show checkpoint client" |
|
DHCP_SNOOPING_ISSU-2-SESSION_NEGO |
2-Critical |
DHCP Snooping ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The DHCP Snooping 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. |
dhcp-snooping |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
DHCP_SNOOPING_ISSU-2-SESSION_REGISTRY |
2-Critical |
DHCP Snooping ISSU client failed to register session information. Error: [dec] [chars] |
The DHCP Snooping ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
dhcp-snooping |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
DHCP_SNOOPING_ISSU-3-INVALID_SESSION |
3-Error |
DHCP Snooping ISSU client does not have a valid registered session. |
The DHCP Snooping ISSU client does not have a valid registered session. |
dhcp-snooping |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
DHCP_SNOOPING_ISSU-3-MSG_NOT_OK |
3-Error |
DHCP Snooping ISSU client 'Message Type [dec]' is not compatible |
The DHCP Snooping ISSU client received an incompatible message from the peer device. The message cannot be processed. |
dhcp-snooping |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
DHCP_SNOOPING_ISSU-3-MSG_SIZE |
3-Error |
DHCP Snooping ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The DHCP Snooping ISSU client failed to calculate the MTU for the specified message. The DHCP Snooping ISSU client is not able to send the message to the standby device. |
dhcp-snooping |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
DHCP_SNOOPING_ISSU-3-SESSION_UNREGISTRY |
3-Error |
DHCP Snooping ISSU client failed to unregister session information. Error: [dec] [chars] |
The DHCP Snooping ISSU client failed to unregister session information. |
dhcp-snooping |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
DHCP_SNOOPING_ISSU-3-TRANSFORM_FAIL |
3-Error |
DHCP Snooping ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The DHCP Snooping 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 DHCP Snooping state between the active device and the standby device is not identical. |
dhcp-snooping |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
DHCP_SNOOPING-3-DHCP_SNOOPING_INTERNAL_ERROR |
3-Error |
DHCP Snooping internal error [chars] |
A software sanity check failed in the DHCP Snooping process. |
dhcp-snooping |
LOG_STD_SH_TECH_ACTION |
|
DHCP_SNOOPING-4-AGENT_OPERATION_FAILED |
4-Warning |
DHCP snooping binding transfer failed. [chars] |
This message provides the reason of failure when a database transfer\n\ has failed. |
dhcp-snooping |
LOG_STD_NO_ACTION |
|
DHCP_SNOOPING-4-AGENT_OPERATION_FAILED_N |
4-Warning |
DHCP snooping binding transfer failed[dec]. [chars] |
This message provides the reason of failure when a database transfer\n\ has failed. This log message is rate limited. |
dhcp-snooping |
LOG_STD_NO_ACTION |
|
DHCP_SNOOPING-4-DHCP_SNOOPING_DATABASE_FLASH_WARNING |
4-Warning |
Saving DHCP snooping bindings to [chars] can fill up your device causing the writes of bindings to device to fail. |
Saving DHCP Snooping bindings to a flash file system such as\n\ bootflash or slot0 could cause the flash to fill up. Possible\n\ consequences include the long delay to regain console write\n\ failures for database config regular squeeze requirements and\n\ reduced life of flash due to regular squeeze operations etc. |
dhcp-snooping |
"Alternate destination locations for database agent " "include tftp ftp rcp etc. Please see the help " "at command line for a complete list of options." |
|
DHCP_SNOOPING-4-DHCP_SNOOPING_ERRDISABLE_WARNING |
4-Warning |
DHCP Snooping received [dec] DHCP packets on interface [chars] |
DHCP Snooping detected a DHCP packet rate limit violation on a particular interface. The interface will be error disabled. |
dhcp-snooping |
LOG_STD_NO_ACTION |
|
DHCP_SNOOPING-4-DHCP_SNOOPING_PVLAN_WARNING |
4-Warning |
DHCP Snooping configuration may not take effect on secondary vlan [dec]. [chars] |
If private vlan feature is enabled DHCP Snooping configuration on primary vlan will automatically propagate to all secondary vlans. |
dhcp-snooping |
LOG_STD_NO_ACTION |
|
DHCP_SNOOPING-4-DHCP_SNOOPING_RATE_LIMIT_EXCEEDED |
4-Warning |
The interface [chars] is receiving more than the threshold set |
This message indicates that a DHCP packets are coming into cpu\n\ at a much higher rate than the specified threshold. |
dhcp-snooping |
LOG_STD_NO_ACTION |
|
DHCP_SNOOPING-4-INVALID_RELEASE_OR_DECLINE_PKT |
4-Warning |
The interface [chars] has received a DHCP Release/Decline packet \n\ with no existing binding entry for it |
This message indicates that a DHCP Release/Decline packet was received \n\ with no corresponding binding entry. |
dhcp-snooping |
LOG_STD_NO_ACTION |
|
DHCP_SNOOPING-4-IP_SOURCE_BINDING_NON_EXISTING_VLAN_WARNING |
4-Warning |
IP source binding is configured on non existing vlan [dec]. |
IP source binding is configured on a non existing vlan. |
dhcp-snooping |
"Please make sure that the L2 VLAN is configured before configuring a " "DHCP Snooping Binding. If you see this message even though L2 VLAN is " "configured in the system please contact Cisco Technical Assistance " "Center." |
|
DHCP_SNOOPING-4-IP_SOURCE_BINDING_PVLAN_WARNING |
4-Warning |
IP source filter may not take effect on secondary vlan [dec] where IP source binding is configured. [chars] |
If private vlan feature is enabled IP source filter on primary vlan will automatically propagate to all secondary vlans. |
dhcp-snooping |
LOG_STD_NO_ACTION |
|
DHCP_SNOOPING-4-OPTION82_INSERTION_FAIL |
4-Warning |
The interface [chars] is not able to insert opt82 into the packet\n\ because of insufficient space in the packet |
This message indicates that a DHCP packet was not inserted with\n\ opt82 data due to insufficient space in the packet. |
dhcp-snooping |
LOG_STD_NO_ACTION |
|
DHCP_SNOOPING-4-QUEUE_FULL |
4-Warning |
Fail to enqueue DHCP packet into processing queue: [chars] the queue is most likely full and packet will be dropped. |
If the DHCP snooping bindings are loaded by the DHCP snooping database agent and NTP is not sync then the calculated lease duration for the bindings will be incorrect. |
firmware |
"Synchronize NTP on the switch to provide an accurate " "time and date for the system clock. Then disable and " "re-enable DHCP snooping to clear the bindings database." |
|
DHCP_SNOOPING-4-SSO_SYNC_ACK_ERROR |
4-Warning |
Error is encountered in processing acknowledgement for DHCP snooping binding sync [chars]. ack message txn id: 0x[hec] |
This message indicates that there is an error in handling of the\n\ dhcp snooping binding sync acknowledgement. In most of these cases\n\ the ack message is ignored. |
dhcp-snooping |
LOG_STD_NO_ACTION |
|
DHCP_SNOOPING-4-STANDBY_AGENT_OPERATION_FAILED |
4-Warning |
DHCP snooping binding transfer failed on the Standby Supervisor. [chars] |
This message provides the reason of failure when a database transfer\n\ has failed on the Standby Supervisor. |
dhcp-snooping |
LOG_STD_NO_ACTION |
|
DHCP_SNOOPING-5-DHCP_SNOOPING_FAKE_INTERFACE |
5-Notice |
[chars] drop message with mismatched source interface the binding is not updated message type: [chars] MAC sa: [enet] |
DHCP Snooping discovers some host is trying to act as another host\n\ on the network and trying to carry out a DOS attack on that host. |
dhcp-snooping |
LOG_STD_NO_ACTION |
|
DHCP_SNOOPING-5-DHCP_SNOOPING_MATCH_MAC_FAIL |
5-Notice |
[chars] drop message because the chaddr doesn't match source mac message type: [chars] chaddr: [enet] MAC sa: [enet] |
DHCP Snooping enables match-source-mac validation and the check is\n\ failed. There maybe a malicious host trying to carry out a DOS\n\ attack on the DHCP server. |
dhcp-snooping |
LOG_STD_NO_ACTION |
|
DHCP_SNOOPING-5-DHCP_SNOOPING_NONZERO_GIADDR |
5-Notice |
[chars] drop message with non-zero giaddr or option82 value on untrusted port message type: [chars] MAC sa: [enet] |
DHCP Snooping discovers DHCP packet with certain option value not\n\ allowed on the untrusted port some host maybe trying to act as a DHCP\n\ relay or server. |
dhcp-snooping |
LOG_STD_NO_ACTION |
|
DHCP_SNOOPING-5-DHCP_SNOOPING_UNTRUSTED_PORT |
5-Notice |
[chars] drop message on untrusted port message type: [chars] MAC sa: [enet] |
DHCP Snooping discovers certain types of DHCP message not allowed on\n\ the untrusted interface some host maybe trying to act as a DHCP server. |
dhcp-snooping |
LOG_STD_NO_ACTION |
|
DHCP_SNOOPING-6-AGENT_OPERATION_SUCCEEDED |
6-Information |
DHCP snooping database [chars] succeeded. |
This message indicates that the given binding transfer has succeeded.\n\ This message is logged only once after some failure to indicate that the\n\ switch has recovered from failures. |
dhcp-snooping |
LOG_STD_NO_ACTION |
|
DHCP_SNOOPING-6-BINDING_COLLISION |
6-Information |
Binding collision. [dec] bindings ignored |
This message indicates that the given number of bindings from the \n\ database file have been ignored when the file is read. The bindings\n\ are ignored because the system has a binding for the given mac address\n\ and vlan combination by the time the switch read the ignored binding\n\ from the file. |
dhcp-snooping |
LOG_STD_NO_ACTION |
|
DHCP_SNOOPING-6-INTERFACE_NOT_VALID |
6-Information |
Interface not valid. [dec] bindings ignored. |
This message indicates that the given number of bindings from the\n\ database file have been ignored when the file is read. The bindings\n\ are ignored because the interface indicated by the ignored binding\n\ either does not exist in the system or it's a router or dhcp \n\ snooping trusted port. |
dhcp-snooping |
LOG_STD_NO_ACTION |
|
DHCP_SNOOPING-6-LEASE_EXPIRED |
6-Information |
Lease Expired. [dec] bindings ignored. |
This message indicates that the given number of bindings from the\n\ database file have been ignored when the file is read. The bindings\n\ are ignored because their lease has expired. |
dhcp-snooping |
LOG_STD_NO_ACTION |
|
DHCP_SNOOPING-6-PARSE_FAILURE |
6-Information |
Parsing failed for [dec] bindings. |
This message indicates that the given number of bindings from the\n\ database file have been ignored when the file is read. The bindings\n\ are ignored because of parsing failures. |
dhcp-snooping |
LOG_STD_NO_ACTION |
|
DHCP_SNOOPING-6-VLAN_NOT_SUPPORTED |
6-Information |
Vlan not supported. [dec] bindings ignored. |
This message indicates that the given number of bindings from the\n\ database file have been ignored when the file is read. The bindings\n\ are ignored because the vlan indicated by the ignored binding\n\ no longer exists in the system. |
dhcp-snooping |
LOG_STD_NO_ACTION |
|
DHCP-3-HA_INIT_FAIL |
3-Error |
Function [chars] in DHCP client failed to initialize: [chars]\n |
A high availability related function in the DHCP client failed to initialize properly. If you are using a platform with a redundant processor or box-to-box redundancy DHCP client settings may fail to be preserved if the main processor fails forcing use of the standby. |
dhcp |
"Please contact the TAC for assistance." |
|
DHCP-5-RESTART |
5-Notice |
Interface [chars] is being restarted by DHCP\n |
DHCP is restarting the interface. |
dhcp |
LOG_STD_NO_ACTION |
|
DHCP-6-ADDRESS_ASSIGN |
6-Information |
Interface [chars] assigned DHCP address [inet] mask [inet] hostname [chars]\n |
The interface has been allocated an address via DHCP |
- |
"This is an informational message. No action is required" |
|
DHCPD-2-MALLOC_ERROR |
2-Critical |
There is inadequate memory for DHCP services. |
DHCP could not allocate mandatory data structures. |
- |
"Add more memory." |
|
DHCPD-2-NO_PROCESS |
2-Critical |
DHCP could not start its [chars] process. |
DHCP could not start one of its processes. |
- |
"Add more memory." |
|
DHCPD-2-READ_DEADLOCK |
2-Critical |
DHCP has detected a deadlock condition excessive read failures. |
The DHCP server could not read bindings from any database agent. All\n\ read attempts have failed. To prevent a possible deadlock the server\n\ has made all pool addresses available for assignment. |
- |
"Verify that all URLs are correct and connectivity exists between the \n\ server and all database agents. Check for corrupt database files. All\n\ files must contain the *time* and *end* keywords. Execute the command \n\ \"show ip dhcp database.\" If there are aborted file transfers increase \n\ the appropriate timeouts. Restart the DHCP server." |
|
DHCPD-2-RECVMSG_ERROR |
2-Critical |
Recvmsg failed unexpectedly. DHCP services have been terminated. |
Reason for failure is unknown. |
dhcp-server |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
DHCPD-2-SOCKET_ERROR |
2-Critical |
DHCP could not open UDP port [dec]. |
DHCP could not open UDP port 67 bootps. |
- |
"Check if another application is using UDP port 67. If the port is\n\ available add more memory." |
|
DHCPD-3-HA_INIT_FAIL |
3-Error |
Function [chars] in DHCP server failed to initialize: [chars]\n |
A high availability related function in the DHCP server failed to initialize properly. If you are using a platform with a redundant processor or box-to-box redundancy DHCP server data may fail to be preserved if the main processor fails forcing use of the standby. |
dhcp |
"Please contact the TAC for assistance." |
|
DHCPD-3-NO_AAA_CONTEXT |
3-Error |
AAA configured but no AAA context in [chars]\n |
DHCP is attempting to use AAA to grant a DHCP lease but no AAA context is associated with the binding |
dhcp |
"Please contact the TAC for assistance." |
|
DHCPD-3-READ_ERROR |
3-Error |
DHCP could not read bindings from [chars]. |
The DHCP server could not read bindings from the specified database \n\ agent. |
- |
"Verify that the URL is correct and connectivity exists between the \n\ server and database agent. Check for a corrupt database file. The\n\ file must contain the *time* and *end* keywords. Execute the command \n\ \"show ip dhcp database.\" If there are aborted file transfers increase \n\ the database transfer timeout." |
|
DHCPD-3-WRITE_ERROR |
3-Error |
DHCP could not write bindings to [chars]. |
The DHCP server could not write bindings to the specified database \n\ agent. |
- |
"Verify that the URL is correct and connectivity exists between the \n\ server and database agent. Execute the command \"show ip dhcp database.\"\n\ If there are aborted file transfers increase the database transfer \n\ timeout." |
|
DHCPD-4-DECLINE_CONFLICT |
4-Warning |
DHCP address conflict: client [chars] declined %I. |
The DHCP client has detected an address conflict. Another host is using\n\ the specified IP address. After resolving the conflict execute the\n\ command \clear ip dhcp conflict.\ |
- |
"Resolve the misconfiguration. Clear the conflict from the DHCP \n\ database." |
|
DHCPD-4-HA_CONFIG_MISMATCH |
4-Warning |
DHCP pool [chars] configuration on Active is not matched on the Standby. |
Reason for failure is unknown. |
dhcp |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
DHCPD-4-PING_CONFLICT |
4-Warning |
DHCP address conflict: server pinged %I. |
The DHCP server has detected an address conflict. Another host is using\n\ the specified IP address. After resolving the conflict execute the\n\ command \clear ip dhcp conflict.\ |
- |
"Resolve the misconfiguration. Clear the conflict from the DHCP \n\ database." |
|
DHCPD-4-RELAY_ONLY |
4-Warning |
DHCP will run as a relay agent only. |
DHCP could not start its database process. The server component has \n\ been disabled. Only the relay agent is active. |
- |
"Add more memory." |
|
DHCPD-6-HIGH_UTIL |
6-Information |
Pool \[chars]\ is in high utilization state [dec] addresses used out of [dec]. Threshold set at [dec]%%. |
The pool's utilization has exceeded the user configured high watermark. |
dhcp |
"Examine the DHCP pool and determine if the pool needs more IP addresses" " than currently allocated." |
|
DHCPD-6-LOW_UTIL |
6-Information |
Pool \[chars]\ is in low utilization state [dec] addresses used out of [dec]. Threshold set at [dec]%%. |
The pool's utilization has fallen below the user configured high watermark. |
dhcp |
"Examine the DHCP pool and determine if the pool needs more IP addresses" " than currently allocated." |
|
DHCPD-6-MALFORMED_OPTION |
6-Information |
Invalid option [dec] message type [dec] received from client [chars]\n |
DHCP client sent malformed option. |
dhcp |
"Check if DHCP client can be configured to send valid option." |
|
DHCPV6C-3-NOPACKET |
3-Error |
Cannot setup or duplicate a socket packet |
Most likely a resource problem within the system. |
dhcp |
LOG_STD_REDUCE_ACTION |
|
DHCPV6C-3-NOSOCKET |
3-Error |
Cannot create DHCPv6 client socket |
Most likely no IP enabled on any interface or a resource problem within the system. |
dhcp |
LOG_STD_REDUCE_ACTION |
|
DHCPV6C-4-ZEROXID |
4-Warning |
Calculated DHCPv6 Lease Query xid is zero. Nothing is wrong just drop the LQv6 msg |
After multiple tries the generated LQv6 msg xid is zero by accident. Just drop the LQv6 msg. |
dhcp |
LOG_STD_REDUCE_ACTION |
|
DHCPV6R-3-INVALID_USR_LINKADDR |
3-Error |
Invalid user specified link-address %P idb [chars] in ipv6 dhcp relay CLI.\n Removing user specified invalid address from the CLI. |
Invalid link-address has been provisioned in the ipv6 relay destination CLI. |
dhcp |
LOG_STD_REDUCE_ACTION |
|
DHCPV6R-3-INVALID_USR_SRCADDR |
3-Error |
Invalid user specified source-address %P idb [chars] in ipv6 dhcp relay CLI.\n Removing user specified invalid address from the CLI and auto-computing source with SAS. |
Invalid source-address has been provisioned in the ipv6 relay destination CLI. |
dhcp |
LOG_STD_REDUCE_ACTION |
|
DHCPV6S-3-DBNOTLOADED |
3-Error |
Binding database not loaded |
Fail to load the DHCPv6 binding database. |
dhcp |
LOG_STD_ACTION |
|
DHCPV6S-3-DBOPEN |
3-Error |
Openning [chars]: [chars] |
Fail to open a DHCPv6 binding database file. |
dhcp |
LOG_STD_ACTION |
|
DHCPV6S-3-DBREAD |
3-Error |
Reading file: [chars] |
Fail to read a DHCPv6 binding database file. |
dhcp |
LOG_STD_ACTION |
|
DHCPV6S-3-DBWRITE |
3-Error |
Writing file: [chars] |
Fail to write a DHCPv6 binding database file. |
dhcp |
LOG_STD_ACTION |
|
DHCPV6S-3-NOPACKET |
3-Error |
Cannot setup or duplicate a DHCPv6 server socket packet |
Most likely a resource problem within the system. |
dhcp |
LOG_STD_REDUCE_ACTION |
|
DIAG-3-ALWAYS_ENABLE_TEST |
3-Error |
[chars]: The users are not allow to disable monitoring for Test #[dec] |
The specified health monitoring test must be run and cannot be disabled. |
gold |
"Nothing. The specific health monitoring test cannot be disabled by " "design. The system is working properly." |
|
DIAG-3-CARD_ABSENT |
3-Error |
[chars] is not detected |
A line card could not be located in a slot where a diagnostic action was requested. |
gold |
"Ensure the targeted line card is properly seated in the specified slot. " "If the line card is properly seated ensure the correct slot was " "indicated in the command-line interface. If the line card is well-seated " "and the correct slot was specified copy the error message exactly as it " "appears on the screen as well as the output of show tech-support and " "paste the output into a separate file. Contact your technical support " "representative with the gathered information." |
|
DIAG-3-CREATE_PROCESS_FAIL |
3-Error |
Create process [chars] failed |
An internal software error occurred. |
gold |
"Copy the error message exactly as it appears on the screen and gather " "the output of show tech-support and any other relevant information. " "Contact your technical support representative with the gathered " "information." |
|
DIAG-3-DIAG_RUNNING |
3-Error |
[chars]: Diagnostic is currently running |
A diagnostic test is currently being run on the specified card and additional tests cannot be run until the previously requested tests have been completed. |
gold |
"The system is working properly and no user action is required. If you " "want to run the specified diagnostic test either wait for the current " "diagnostic test to finish and then run the test or stop the current " "test and run the new test." |
|
DIAG-3-ENQUEUE_FAIL |
3-Error |
[chars]: process_enqueue failed |
An internal software error occurred. |
gold |
"Copy the error message exactly as it appears on the screen and gather " "the output of show tech-support and any other relevant information. " "Contact your technical support representative with the gathered " "information." |
|
DIAG-3-FIXED_INTERVAL_TEST |
3-Error |
[chars]: The users are not allow to change monitoring interval of Test #[dec] |
The specified health monitoring test interval is not user-configurable and therefore cannot be changed. |
gold |
"Nothing. The specific health monitoring interval is not user-" "configurable by design so nothing can be done to change the interval." |
|
DIAG-3-GET_ARGU_FAIL |
3-Error |
Get argument failed |
An internal software error occurred. |
gold |
"Copy the error message exactly as it appears on the screen and gather " "the output of show tech-support and any other relevant information. " "Contact your technical support representative with the gathered " "information." |
|
DIAG-3-INVALID_DEVICE |
3-Error |
Invalid device number : [chars] |
A diagnostic request is being made on a device that does not exist |
gold |
"Ensure that the specified device number 1-based exists and is valid" |
|
DIAG-3-INVALID_MONITORING_INTERVAL |
3-Error |
[chars]: The [chars][ID=[dec]] monitoring interval must be at least %lld millisec |
The specified test monitoring interval is too small. |
gold |
"The system is working properly and no user action is required. If you " "want to specify a smaller testing interval the error message text " "provides the lowest possible configurable interval for the specified " "monitoring interval." |
|
DIAG-3-INVALID_PORT |
3-Error |
Invalid port number : [chars] |
A diagnostic request is being made on a port that does not exist. |
gold |
"Ensure the specified port number exists and that the correct port number " "is being specified." |
|
DIAG-3-INVALID_TEST |
3-Error |
Invalid test: [chars] |
A test that does not exist was requested. |
gold |
"Ensure the specified test is supported by the line card. The " "list of available tests and their associated test IDs can be retrieved " "using show diagnostic content." |
|
DIAG-3-MAJOR |
3-Error |
[chars]: [chars] detected a Major Error. Please use 'show diagnostic result <target>' to see test results. |
A major error was detected during diagnostic testing. |
gold |
"Re-seat the card and retry the test. If the same result occurs after " "reseating the card and retrying the test copy the error message " "exactly as it appears on the screen and gather the output of show " "tech-support and any other relevant information. Contact your " "technical support representative with the gathered information." |
|
DIAG-3-MINOR |
3-Error |
[chars]: [chars] detected a Minor Error. Please use 'show diagnostic result <target>' to see test results. |
A minor error was detected during diagnostic testing. |
gold |
"Re-seat the card and retry the test. If the same result occurs after " "reseating the card and retrying the test copy the error message " "exactly as it appears on the screen and gather the output of show " "tech-support and any other relevant information. Contact your " "technical support representative with the gathered information." |
|
DIAG-3-MONITOR_DISABLE |
3-Error |
[chars]: Monitoring test:[dec] is disabled since default interval is zero |
The specified test is no longer a health monitoring test because health monitoring has been disabled. |
gold |
"The system is working properly and no user action is required. If you " "want the requested test to be a health monitoring test enable health " "monitoring and ensure your test is enabled as a health monitoring test." |
|
DIAG-3-MONITOR_INTERVAL_ZERO |
3-Error |
[chars]: Monitoring interval is 0. Cannot enable monitoring for Test #[dec] |
Health Monitoring cannot be enabled for the specified test because the interval for the test has been set to 0. |
gold |
"If you are comfortable not running the specified health monitoring test " "nothing. If you would like to enable the specified test for health " "monitoring reset the interval to a number other than 0." |
|
DIAG-3-NO_DIAG_RUNNING |
3-Error |
[chars]: Diagnostic is not running |
An attempt to stop a diagnostic test that was not running was made. |
gold |
"None. This is an informational message." |
|
DIAG-3-NOT_MONITORING_TEST |
3-Error |
[chars]: The test:[dec] cannot be used as health monitoring test |
The specified test number cannot be used as a health monitoring test. |
gold |
"Nothing. The system is working properly and the specified test cannot " "be configured as a health monitoring test." |
|
DIAG-3-SET_ARGU_FAIL |
3-Error |
Set argument failed |
An internal software error occurred. |
gold |
"Copy the error message exactly as it appears on the screen and gather " "the output of show tech-support and any other relevant information. " "Contact your technical support representative with the gathered " "information." |
|
DIAG-3-TEST_FAIL |
3-Error |
[chars]: [chars]{ID=[dec]} has failed. Error code = 0x[hec] [chars] |
A diagnostic test has found an error on the line card. |
gold |
"Ensure the line card is firmly in the slot reseat if necessary and " "attempt to run the test again if the line card is not seated properly " "in the slot. If the line card was properly seated in the slot copy the " "error message exactly as it appears on the console gather the output " "of show tech-support and contact your Cisco technical support " "representative with the gathered information." |
|
DIAG-3-TEST_NOT_SUPPORT |
3-Error |
[chars]: [chars]{ID=[dec]} is not supported |
The diagnostic test is not supported on current chassis configuration. |
gold |
"Nothing. The test cannot be run but this message does not indicate a " "problem with the system." |
|
DIAG-3-TEST_SKIPPED |
3-Error |
[chars]: [chars]{ID=[dec]} is skipped |
The specified diagnostic test cannot be run. |
gold |
"Nothing. Although the test cannot be run this message does not indicate " "a problem." |
|
DIAG-3-UNKNOWN_OPCODE |
3-Error |
[chars]: Unknown opcode %ld is received |
An internal software error occurred. |
gold |
"Copy the error message exactly as it appears on the screen and gather " "the output of show tech-support and any other relevant information. " "Contact your technical support representative with the gathered " "information." |
|
DIAG-4-CONFIG_REAPPLY |
4-Warning |
Please reapply config command '[chars]' after the card is online. |
The specified config command cannot be applied. |
gold |
"The system is working properly and the specified command cannot" "be applied. Please reapply the config command after the module" "is online." |
|
DIAG-6-BYPASS |
6-Information |
[chars]: Diagnostics is bypassed |
This is an informational message stating that diagnostics testing was not performed on the card because diagnostic testing was disabled in the user configuration. |
gold |
"This behavior is consistent with the user configuration and no action " "needs to be taken. If you want to run bootup diagnostics enable bootup" " diagnostics by using the diagnostic bootup command." |
|
DIAG-6-DIAG_OK |
6-Information |
[chars]: Passed [chars] |
The diagnostic tests did not detect any error on the card. |
gold |
"Nothing. This is an informational message stating that the line card " "passed the diagnostic tests." |
|
DIAG-6-DIAG_STOPPED |
6-Information |
[chars]: Diagnostic is stopped. |
Diagnostic test has stopped. |
gold |
"Nothing. This is an informational message stating that diagnostic " "testing has been stopped. If you want the test to run to completion " "rerun the test." |
|
DIAG-6-NO_TEST |
6-Information |
[chars]: No test to run |
The diagnostic test cannot find tests to run. |
gold |
"In some cases on some platforms a Field Diagnostic image needs to be " "loaded onto the line card if you want to run the test. If applicable " "download a Field Diagnostic image onto the line card. In other cases " "the test is simply not available. This message is an informational and " "does not require user action." |
|
DIAG-6-RUN_COMPLETE |
6-Information |
[chars]: Running Complete Diagnostics... |
Complete Diagnostic is running on the card |
gold |
"Nothing. This is an informational message and the system is working " "properly." |
|
DIAG-6-RUN_MINIMUM |
6-Information |
[chars]: Running Minimal Diagnostics... |
Minimum Diagnostic is running on the card |
gold |
"Nothing. This is an informational message and the system is working " "properly." |
|
DIAG-6-SCHED_COMPLETE |
6-Information |
[chars]: Scheduled Online Diagnostic is completed |
The scheduled Diagnostic test is complete. |
gold |
"Check the results and proceed accordingly. This is an information " "message only to indicate that Diagnostic testing is complete. The router " "is working properly and no action is needed based on this message." |
|
DIAG-6-SCHED_RUNNING |
6-Information |
[chars]: Performing Scheduled Online Diagnostic... |
The scheduled diagnostic test is running. |
gold |
"Nothing. The diagnostic test is being run as configured and the system " "is working properly." |
|
DIAG-6-SCHED_STOPPED |
6-Information |
[chars]: Scheduled Online Diagnostic is stopped |
The scheduled Diagnostic test has been stopped. |
gold |
"If you do not want the test to run nothing. If you want the test to " "run schedule the test or run the test manually." |
|
DIAG-6-SCHEDULE_IS_REMOVED |
6-Information |
[chars]: Schedule Diagnostic for [[chars] [chars] %2ld:%02ld.] is removed |
The scheduled online diagnostic tests are no longer configured. This message usually appears after a scheduled test is removed by the user or a card is removed from the chassis. |
gold |
"If you want the scheduling tests to be removed nothing. If you want " "the scheduled tests to still be run reconfigure the scheduled tests." |
|
DIAG-6-SIMULATED_TEST_RESULT |
6-Information |
[chars]: [chars] test result is simulated. |
The specified test's result is simulated. The failure does not indicate software nor hardware fault |
gold |
"Nothing. The test failure is simulated as specified by the user." |
|
DIAG-6-SKIP_ONDEMAND_ACTIVE_TO_STANDBY_TEST |
6-Information |
[chars]: [chars] cannot be executed for active device. |
The specified test can only be run from the active supervisor to test standby supervisor. |
gold |
"Nothing. The test cannot be run but the system is working properly." |
|
DIAG-6-SKIP_ONDEMAND_STANDBY_CARD_TEST |
6-Information |
[chars]: [chars] cannot be executed. |
The specified test can only be run on a standby supervisor from the standby supervisor. |
gold |
"Nothing. The test cannot be run but the system is working properly." |
|
DIAG-6-TEST_OK |
6-Information |
[chars]: [chars]{ID=[dec]} has completed successfully |
Diagnostic testing was completed and no errors were found on the line card. |
gold |
"This is an informational message indicating that Field Diagnostic " "testing has completed successfully. The system is working properly and " "no action is required based on this error message." |
|
DIAG-6-TEST_RUNNING |
6-Information |
[chars]: Running [chars]{ID=[dec]} ... |
Diagnostic testing is running a test on the card |
gold |
"Nothing. This is an informational message and the system should be " "working properly." |
|
DIAG-6-TEST_SKIPPED_FROM_ACTIVE |
6-Information |
[chars]: [chars] cannot be executed from active supervisor. |
The specified test cannot be run from active supervisor. |
gold |
"Nothing. The test cannot be run but the system is working properly." |
|
DIALER_LIST_PROXY-3-PROXY_ALLOC_PAK_FAILED |
3-Error |
alloc pak failed |
alloc pak failed. |
cpp-ucode |
LOG_STD_ACTION |
|
DIALER_LIST_PROXY-3-PROXY_IPC_FAILED |
3-Error |
[chars] failed to send ipc rc: [dec] |
send ipc failed. |
cpp-ucode |
LOG_STD_ACTION |
|
DIALER_LIST_PROXY-3-PROXY_IPC_INIT_FAILED |
3-Error |
[dec] |
IPC handler initialization failed. |
cpp-ucode |
LOG_STD_ACTION |
|
DIALER_LIST_PROXY-3-PROXY_MEM_EXTEND_FAILED |
3-Error |
IPC subtype: [dec] |
add more memory failed. |
cpp-ucode |
LOG_STD_ACTION |
|
DIALER_LIST_PROXY-4-PROXY_IPC_INVALID_MSG |
4-Warning |
[hec] |
Received an invalid IPC messages subtype. |
cpp-ucode |
LOG_STD_ACTION |
|
DIALER_LIST_PROXY-4-PROXY_IPC_INVALID_MSG_LEN |
4-Warning |
[dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Invalid IPC message length. |
cpp-ucode |
LOG_STD_ACTION |
|
DIALER_LIST-3-CHUNK_CREATE_FAIL |
3-Error |
DIALER LIST - fialed to create chunk pool |
Chunk create failed. Dialer List will not be able to finish initialization. |
cpp-ucode |
LOG_STD_ACTION |
|
DIALER_LIST-3-CHUNK_DESTROY_FAIL |
3-Error |
DIALER LIST - fialed to destroy chunk pool |
Chunk destroy failed. |
cpp-ucode |
LOG_STD_ACTION |
|
DIALER-2-CIRCUITCOUNT |
2-Critical |
Dialer count 0 on [chars] |
An internal software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
DIALER-2-NOSWIDB |
2-Critical |
No software interface associated with hw interface [chars] |
An internal software error occurred. |
- |
"Call your technical support representative and report the error\n\ message the system version and the router configuration. Use the\n\ show version command to obtain the software version." |
|
DIALER-2-NULLPTR |
2-Critical |
Unexpected null pointer in [chars] |
An internal software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
DIALER-3-SBINIT |
3-Error |
Error initializing [chars] subblock data structure. [chars] |
Initialization of the specified subblock data structure could not be accomplished. |
- |
LOG_STD_ACTION |
|
DIALER-4-MTU_WARNING |
4-Warning |
Current MTU setting of [dec] on [chars] is being overwritten by setting of [dec] defined by [chars]. |
This is a warning message indicating that an interface setting is changed based on a dialer rotary group memebership. |
- |
LOG_STD_NO_ACTION |
|
DIALER-6-BIND |
6-Information |
Interface [chars] bound to profile [chars] |
This is a status message indicating that a dialer interface has\n\ been bound to a dialer profile. |
- |
LOG_STD_NO_ACTION |
|
DIALER-6-UNBIND |
6-Information |
Interface [chars] unbound from profile [chars] |
This is a status message indicating that a dialer interface has\n\ been unbound to a dialer profile. |
- |
LOG_STD_NO_ACTION |
|
DIALPEER_DB-3-ADDPEER_MEM_THRESHOLD |
3-Error |
Addition of dial-peers limited by available memory\n |
The available memory does not permit the addition of more dial-peers. |
ios-voice |
"Increase the processor memory in order to be able to add more\n\ dialpeers." |
|
DIALPEER_DB-3-ADDPEER_PLATFORM_LIMIT |
3-Error |
Addition of dial-peers limited by platform\n |
This platform does not permit the addition of more dial-peers. |
ios-voice |
"Reduce the number of dial-peers in your numbering plan." |
|
DIALPEER_DB-3-DIALPEER_ACCOUNTING |
3-Error |
Connections for dial-peer [dec] is negative. Resetting connections to 0.\n |
Active Connections for dial-peer is negative. |
ios-voice |
"Verify if dial-peers were removed with active calls associated to them\n\ and added back while the calls were still connected." |
|
DIALPEER_DB-3-DP_MALLOC_FAIL |
3-Error |
Could not allocate memory in [chars] for tag [dec]\n |
Ran out of memory |
voice-dialpeer |
"Observe why memory is exhausted" |
|
DIALPEER_DB-3-NODEPMAP |
3-Error |
Could not load e164-pattern-map [dec]\n url=[chars]\n errno=[dec]=[chars] |
Could not read in the e164-pattern-map |
voice-dialpeer |
"Check that map exists on the server and is readable." |
|
DIALPEER_DB-3-NOE164TRANSURL |
3-Error |
Could not load e164-translation [dec]\n url=[chars]\n error=[chars][dec] |
Could not get the voice class e164-translation url data file |
voice-dialpeer |
"Check that url data file exists on the server and is readable." |
|
DIALPEER_DB-3-NOMAP |
3-Error |
Could not load dnis-map [chars]\n url=[chars]\n errno=[dec]=[chars] |
Could not read in the dnis-map |
ios-voice |
"Check that map exists on the server and is readable." |
|
DIALPEER_DB-6-ADDPEER_WARNING |
6-Information |
Addition of too many dial-peers may affect performance\n |
The number of dial-peers is high. This will have an effect on the\n\ dial-peer lookup time resulting in longer call setup time. |
ios-voice |
"Use the minimum number of dial-peers necessary for your numbering plan." |
|
DIALPEER_DB-6-FB_ENTRY_NOT_CREATED |
6-Information |
Could not create probe for tag [dec]\n |
Fallback cache full |
voice-dialpeer |
"Increase Fallaback cache size" |
|
DIALSHELF-2-DSCDOWN |
2-Critical |
DSC in slot [dec] changes state to down. |
DSC in dial shelf went down. |
- |
- |
|
DIALSHELF-2-TIMEOUT |
2-Critical |
[chars] slot [dec] after [dec] secs in state '[chars]' |
The specified dial shelf slot timed out as per the message.\n\ Either a software or a hardware component has failed. |
- |
"Try removing and reinserting the card. If that does not help\n\ try a different card. If problem persists contact your\n\ technical support representative." |
|
DIALSHELF-2-UNDEFCARD |
2-Critical |
Card type [dec] in slot [dec] |
The software does not have a driver for the card in specified\n\ slot. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
DIALSHELF-3-EVENT |
3-Error |
Unknown event [dec] for slot [dec] |
The software generated an unknown event for the specified\n\ slot. This is a software error. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
DIALSHELF-3-INVALIDMSG |
3-Error |
[chars] [dec] |
The router shelf received an invalid message from the DSC in\n\ the dial shelf. This is a software error or compatibility issue.\n\ Check the software versions on the router shelf and the DSC. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
DIALSHELF-3-MSG |
3-Error |
Unknown message type [dec] from DSC |
The router shelf received an unknown message from the DSC in\n\ the dial shelf. This is a software error or compatibility issue.\n\ Check the software versions on the router shelf and the DSC. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
DIALSHELF-3-SLOTSTATUS |
3-Error |
Invalid change from [chars] [dec] to [chars] [dec] for slot [dec] |
The software detected an invalid state change for the specified\n\ slot. This is a software error. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
DIALSHELF-4-UNRECOMMENDED |
4-Warning |
Number of [chars] may exceed recommended configuration |
On NPE200 more than one CT3 or more than two T1/E1 are installed\n\ this exceeds the recommended configuration. |
- |
"Stay within recommended limit of CT3/T1/E1 or install split \n\ dial-shelf configuration or upgrade router-shelf to NPE300." |
|
DIALSHELF-6-RELOAD |
6-Information |
Reload requested for card in shelf [dec] slot [dec]. |
The command \'hw-module slot <shelf>/<slot> reload\' was entered.\n\ This is a confirmation that the command is being processed. |
- |
"None" |
|
DIGISIGN-2-MISMATCH_KEYS |
2-Critical |
%%CRITICAL: System identified a mismatch between the show version output and the key type used in signing. [chars] is a signed [chars] software\n |
System identified a mismatch in software type. This might be a modified software. |
digi-sign-infra |
"Do not use this file. The file might be corrupted or modified." "Open a case with the Technical Assistance Center via the " "Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl " "and contact your Cisco technical support representative with the " "image and version information you have gathered." |
|
DIGISIGN-2-MISMATCH_KEYS |
2-Critical |
%%CRITICAL: System identified a mismatch between the show version output and the key type used in signing. [chars] is a signed [chars] software\n |
System identified a mismatch in software type. This might be a modified software. |
digi-sign-infra |
"Do not use this file. The file might be corrupted or modified." "Open a case with the Technical Assistance Center via the " "Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl " "and contact your Cisco technical support representative with the " "image and version information you have gathered." |
|
DIGISIGN-3-DEVIMAGE_NOSUPPORT |
3-Error |
Cannot verify [chars] as it is signed with special key\n |
The software image cannot be verified because it is signed with a special key. |
digi-sign-infra |
"To allow booting a specially-signed image use the" "software authenticity special command" |
|
DIGISIGN-3-DEVIMAGE_NOSUPPORT |
3-Error |
Cannot verify [chars] as it is signed with special key\n |
The software image cannot be verified because it is signed with a special key. |
digi-sign-infra |
"To allow booting a specially-signed image use the" "software authenticity special command" |
|
DIGISIGN-3-INVALID_ENVELOPE |
3-Error |
%%ERROR: Failure in processing signature envelope for system image: [chars]\n |
The loaded Cisco IOS software image has an invalid digital signature envelope. A valid digital signature envelope ensures the integrity of the image. The loaded Cisco IOS software image might be corrupted or modified. The failure type is one of the following: 1 Signature envelope version is not supported |
digi-sign-infra |
"Do not use this file. The file might be corrupted or modified." "Please attempt to copy the file again or download the file again " "from the http://www.cisco.com page before copying it." "If you continue to get this error message open a case with" "the Technical Assistance Center via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl and " "contact your Cisco technical support representative with the " "image and version information you have gathered." |
|
DIGISIGN-3-INVALID_ENVELOPE |
3-Error |
%%ERROR: Failure in processing signature envelope for system image: [chars]\n |
The loaded Cisco IOS software image has an invalid digital signature envelope. A valid digital signature envelope ensures the integrity of the image. The loaded Cisco IOS software image might be corrupted or modified. The failure type is one of the following: 1 Signature envelope version is not supported |
digi-sign-infra |
"Do not use this file. The file might be corrupted or modified." "Please attempt to copy the file again or download the file again " "from the http://www.cisco.com page before copying it." "If you continue to get this error message open a case with" "the Technical Assistance Center via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl and " "contact your Cisco technical support representative with the " "image and version information you have gathered." |
|
DIGISIGN-3-INVALID_SIGNATURE |
3-Error |
%%ERROR: Digital signature is not valid for file [chars]: [chars]\n |
The specified Cisco IOS Software image has an invalid digital signature. A valid digital signature ensures the integrity of the image. |
digi-sign-infra |
"Do not use this file. The file might be corrupted or " "modified. Please attempt to copy the file again or download " "the file again from the http://www.cisco.com page before " "copying it. If you continue to get this error message " "open a case with the Technical Assistance Center via the " "Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl " "and contact your Cisco technical support representative with the " "information you have gathered." |
|
DIGISIGN-3-INVALID_SIGNATURE |
3-Error |
%%ERROR: Digital signature is not valid for file [chars]: [chars]\n |
The specified Cisco IOS Software image has an invalid digital signature. A valid digital signature ensures the integrity of the image. |
digi-sign-infra |
"Do not use this file. The file might be corrupted or " "modified. Please attempt to copy the file again or download " "the file again from the http://www.cisco.com page before " "copying it. If you continue to get this error message " "open a case with the Technical Assistance Center via the " "Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl " "and contact your Cisco technical support representative with the " "information you have gathered." |
|
DIGISIGN-3-KEY_NOT_FOUND |
3-Error |
%%ERROR: No keys found for verifying the digital signature in file [chars] |
No keys found in the device key storage for validating the digital signature. A valid key is needed to validate the digital signature in the image. |
digi-sign-infra |
"The device does not have a vlaid key to verify the digital" "signature. Open a case with the Technical Assistance Center" "via the internet at" "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl " "and contact your Cisco technical support representative with the " "information you have gathered." |
|
DIGISIGN-3-KEY_NOT_FOUND |
3-Error |
%%ERROR: No keys found for verifying the digital signature in file [chars] |
No keys found in the device key storage for validating the digital signature. A valid key is needed to validate the digital signature in the image. |
digi-sign-infra |
"The device does not have a vlaid key to verify the digital" "signature. Open a case with the Technical Assistance Center" "via the internet at" "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl " "and contact your Cisco technical support representative with the " "information you have gathered." |
|
DIGISIGN-3-NET_BOOT |
3-Error |
Netbooted software used for key revocation\n |
System was netbooted using a software in a remote device. It is recommended to boot the system using a software in the local device for the key revocation process. |
digi-sign-infra |
"Please copy the software to local device. Reboot " "the system with the copied software and retry the key revocation." |
|
DIGISIGN-3-NET_BOOT |
3-Error |
Netbooted software used for key revocation\n |
System was netbooted using a software in a remote device. It is recommended to boot the system using a software in the local device for the key revocation process. |
digi-sign-infra |
"Please copy the software to local device. Reboot " "the system with the copied software and retry the key revocation." |
|
DIGISIGN-3-OBSOLETE_SW |
3-Error |
[chars] software signed using obsolete key [chars]\n |
System identified that a software was signed using an obsolete key. Key revocation cannot be possible when the system is still using a software signed using an obsolete key. |
digi-sign-infra |
"Please obtain the latest signed copy of this " "software from cisco.com and upgrade the system module." |
|
DIGISIGN-3-OBSOLETE_SW |
3-Error |
[chars] software signed using obsolete key [chars]\n |
System identified that a software was signed using an obsolete key. Key revocation cannot be possible when the system is still using a software signed using an obsolete key. |
digi-sign-infra |
"Please obtain the latest signed copy of this " "software from cisco.com and upgrade the system module." |
|
DIGISIGN-3-VERIFICATION_FAILED |
3-Error |
%%ERROR: Digital signature verification failed for file [chars]: [chars]\n |
Validation failure while verifying the digital signature. |
digi-sign-infra |
"Do not use this file. The file might be corrupted or " "modified. Please attempt to copy the file again or download " "the file again from the http://www.cisco.com page before " "copying it. If you continue to get this error message " "open a case with the Technical Assistance Center via the " "Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl " "and contact your Cisco technical support representative with the " "information you have gathered." |
|
DIGISIGN-3-VERIFICATION_FAILED |
3-Error |
%%ERROR: Digital signature verification failed for file [chars]: [chars]\n |
Validation failure while verifying the digital signature. |
digi-sign-infra |
"Do not use this file. The file might be corrupted or " "modified. Please attempt to copy the file again or download " "the file again from the http://www.cisco.com page before " "copying it. If you continue to get this error message " "open a case with the Technical Assistance Center via the " "Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl " "and contact your Cisco technical support representative with the " "information you have gathered." |
|
DIGISIGN-3-WPG_BOOT |
3-Error |
Key revocation not allowed while running warm upgraded software\n |
System was booted using warm upgrade. Key revocation process is not supported when the system is booted using warm upgrade. It is recommended to cold boot the system using a software in the local device for the key revocation process. |
digi-sign-infra |
"Please copy the software to local device. Reboot " "the system with the copied software and retry the key revocation." |
|
DIGISIGN-3-WPG_BOOT |
3-Error |
Key revocation not allowed while running warm upgraded software\n |
System was booted using warm upgrade. Key revocation process is not supported when the system is booted using warm upgrade. It is recommended to cold boot the system using a software in the local device for the key revocation process. |
digi-sign-infra |
"Please copy the software to local device. Reboot " "the system with the copied software and retry the key revocation." |
|
DIGISIGN-4-DEV_IMAGE |
4-Warning |
[chars] software signed using special key version [chars]\n |
System identified that a software was signed using special key. If this is unintentional please obtain the latest signed copy of the production software from cisco.com and upgrade the system module. |
digi-sign-infra |
"Get the latest signed copy of production image from cisco.com and upgrade " "the respective module" |
|
DIGISIGN-4-DEV_IMAGE |
4-Warning |
[chars] software signed using special key version [chars]\n |
System identified that a software was signed using special key. If this is unintentional please obtain the latest signed copy of the production software from cisco.com and upgrade the system module. |
digi-sign-infra |
"Get the latest signed copy of production image from cisco.com and upgrade " "the respective module" |
|
DIGISIGN-4-DEVIMAGE_CFG_NOSUPPORT |
4-Warning |
[chars] signed with special key will not be booted\n |
With this configuration enabled the system will be unable to boot software that is signed with a special key. |
digi-sign-infra |
"Use the [no] form of this configuration no software authenticity special" |
|
DIGISIGN-4-DEVIMAGE_CFG_NOSUPPORT |
4-Warning |
[chars] signed with special key will not be booted\n |
With this configuration enabled the system will be unable to boot software that is signed with a special key. |
digi-sign-infra |
"Use the [no] form of this configuration no software authenticity special" |
|
DIGISIGN-4-FUR_BOOT |
4-Warning |
Field upgradable rommon used for key revocation\n |
System identified that the field upgradable rommon was used to boot the image. It is recommended that the readonly rommon be used for the key revocation process. |
digi-sign-infra |
"Recommended action is to boot the image used for key revocation process " "with readonly rommon. This is a warning message." "Command/process will still go through in the current state." |
|
DIGISIGN-4-FUR_BOOT |
4-Warning |
Field upgradable rommon used for key revocation\n |
System identified that the field upgradable rommon was used to boot the image. It is recommended that the readonly rommon be used for the key revocation process. |
digi-sign-infra |
"Recommended action is to boot the image used for key revocation process " "with readonly rommon. This is a warning message." "Command/process will still go through in the current state." |
|
DIGISIGN-4-INVALID_KEY |
4-Warning |
%%WARNING: Digital signature verification failed for file [chars]: [chars]\n |
Validation failure due to invalid key while verifying the digital signature. |
digi-sign-infra |
"Do not use this file. The file might be corrupted or " "modified. Please attempt to copy the file again or download " "the file again from the http://www.cisco.com page before " "copying it. If you continue to get this error message " "open a case with the Technical Assistance Center via the " "Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl " "and contact your Cisco technical support representative with the " "device information you have gathered." |
|
DIGISIGN-4-INVALID_KEY |
4-Warning |
%%WARNING: Digital signature verification failed for file [chars]: [chars]\n |
Validation failure due to invalid key while verifying the digital signature. |
digi-sign-infra |
"Do not use this file. The file might be corrupted or " "modified. Please attempt to copy the file again or download " "the file again from the http://www.cisco.com page before " "copying it. If you continue to get this error message " "open a case with the Technical Assistance Center via the " "Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl " "and contact your Cisco technical support representative with the " "device information you have gathered." |
|
DIGISIGN-4-SIGNATURE_NOT_PRESENT |
4-Warning |
%%WARNING: Digital signature is not found in file [chars]\n |
The specified image file does not have a digital signature. Only Cisco IOS Software Images are digitally signed. If you enter <CmdBold>verify<NoCmdBold> <CmdBold>copy<NoCmdBold> or <CmdBold>reload<NoCmdBold> command and the specified file is not a digitally signed Cisco IOS Software Image the system displays this warning message because the file does not have a signature. A valid digital signature ensures the integrity of the image. |
digi-sign-infra |
"If the specified file is an unsigned Cisco IOS Software image " "be cautious when deciding " "whether or not to use this file. The system will not boot using " "this image." |
|
DIGISIGN-4-SIGNATURE_NOT_PRESENT |
4-Warning |
%%WARNING: Digital signature is not found in file [chars]\n |
The specified image file does not have a digital signature. Only Cisco IOS Software Images are digitally signed. If you enter <CmdBold>verify<NoCmdBold> <CmdBold>copy<NoCmdBold> or <CmdBold>reload<NoCmdBold> command and the specified file is not a digitally signed Cisco IOS Software Image the system displays this warning message because the file does not have a signature. A valid digital signature ensures the integrity of the image. |
digi-sign-infra |
"If the specified file is an unsigned Cisco IOS Software image " "be cautious when deciding " "whether or not to use this file. The system will not boot using " "this image." |
|
DIGISIGN-6-KEY_UPGRADE |
6-Information |
[chars]\n |
System identified a key version mismatch between the key which was used to sign the image and the keys stored on the device |
digi-sign-infra |
"If the image is signed with a key version newer than the device" "keys then follow the procedure for key revocation which is" "which is documented at cisco.com. If the image is signed with a" "key version that is now obsolete please obtain the latest signed" "copy of this image from cisco.com" |
|
DIGISIGN-6-KEY_UPGRADE |
6-Information |
[chars]\n |
System identified a key version mismatch between the key which was used to sign the image and the keys stored on the device |
digi-sign-infra |
"If the image is signed with a key version newer than the device" "keys then follow the procedure for key revocation which is" "which is documented at cisco.com. If the image is signed with a" "key version that is now obsolete please obtain the latest signed" "copy of this image from cisco.com" |
|
DIRECTOR-3-BADCOMPL |
3-Error |
plug-in returned orphan status |
A software or hardware error occurred. |
dist-director |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
DIRECTOR-3-DRPDOWN |
3-Error |
DRP [inet] was down %TE ago in the last [dec] minute period ! There may be problems related to this DRP agent. |
The remote DRP agent has not responded within the time period reported |
- |
"Make sure the remote DRP agent is running and that it is accessible\n\ from the system reporting the problem." |
|
DIRECTOR-3-HTTPOVERLOAD |
3-Error |
Excessive HTTP request overloading: dropping HTTP req from <cli [inet]>. |
HTTP requests are overloading the web redirector |
dist-director |
"Web redirector is automatically discarding HTTP request traffic." |
|
DIRECTOR-3-NOALIAS |
3-Error |
[chars] can not create ip alias |
Most likely a resource problem within the system. |
dist-director |
"Reboot the system as soon as possible. If the problem continues\n\ to occur report it to your technical support representative." |
|
DIRECTOR-3-NOPORT |
3-Error |
[chars] port in use |
The IP address requested has been found to be already in use on\n\ some interface connected to the system or within the system itself. |
dist-director |
"Either select another IP address for use or locate the system making\n\ use of this address and reconfigure it to use another." |
|
DIRECTOR-3-NOPROC |
3-Error |
unable to create [chars] process |
Most likely a resource problem within the system. |
dist-director |
"Reboot the system as soon as possible. If the problem continues\n\ to occur report it to your technical support representative." |
|
DIRECTOR-3-NOSOCKET |
3-Error |
[chars] unable to create socket |
A software or hardware error occurred. |
dist-director |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
DIRECTOR-3-NOTCONF |
3-Error |
Metric [chars] referenced but not found |
- |
dist-director |
- |
|
DIRECTOR-3-NOWRITE |
3-Error |
[chars] unable to write to socket |
A software or hardware error occurred. |
dist-director |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
DIRECTOR-3-URLELSEWHERE |
3-Error |
URL is elsewhere '[chars]' Code [dec] - [chars] |
The HTTP return code indicates the page is not actually on this server |
dist-director |
"Check the URL configured. Check the configured HTTP server." |
|
DIRECTOR-3-URLSVRERR |
3-Error |
Server error '[chars]' Code [dec] - [chars] |
The HTTP return code indicates a server failure error |
dist-director |
"Check the URL configured. Check the configured HTTP server." |
|
DIRECTOR-5-SVRUPDOWN |
5-Notice |
server [inet] on port [dec] has gone [chars] |
The remote server has gone up or down |
dist-director |
"None." |
|
DIRECTOR-6-DNSNORSP |
6-Information |
answer type [chars] host [chars] cli [inet] id# [dec] none |
DNS reply logging: no server found. |
dist-director |
"None." |
|
DIRECTOR-6-DNSQUERY |
6-Information |
query type [chars] host [chars] cli [inet] id# [dec] |
DNS query logging. |
dist-director |
"None." |
|
DIRECTOR-6-DNSRESPN |
6-Information |
answer type [chars] host [chars] cli [inet] id# [dec] svr [inet] |
DNS reply logging with server found. |
dist-director |
"None." |
|
DIRECTOR-6-SVRNSELCT |
6-Information |
no answer for host [chars] cli [inet] type [chars] id# [dec] [chars] |
No server found. |
dist-director |
"None." |
|
DIRECTOR-6-SVRSELECT |
6-Information |
select [inet] host [chars] cli [inet] type [chars] id# [dec] [chars] |
Report server selection process. |
dist-director |
"None." |
|
DISPOSITION_DISABLED-5-ATOM_TRANS |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
DISPOSITION_ENABLED-5-ATOM_TRANS |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
DLC-2-NOMEMORY |
2-Critical |
no memory for [chars] |
There was not enough free memory to complete the operation. |
- |
LOG_STD_ACTION |
|
DLC-3-BADPARAM |
3-Error |
Function [chars]: value [hex] passed in parameter [chars] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
DLC-3-INVPCEP |
3-Error |
Close Station invalid P_CEP |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
DLC-3-WPUTERR |
3-Error |
unknown port type [hec] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
DLEP_MSG-4-CONNECT_ERROR |
4-Warning |
TCP connect to Radio [inet] failed via [chars]. Error code: [chars] |
TCP Connect to IP address and port of the Radio failed. |
DLEP_DDTS_COMPONENT |
"Take action based on the error code shown." " Reconfigure correct IP address and port " " if necessary." |
|
DLEP_SET_MSG-6-DLEP_HEARTBEAT_THRESHOLD |
6-Information |
new Threshold value configured will have effect for the new sessions only not for the currently running DLEP sessions |
If the threshold value should be updated at Router side it must be configured before the Radio launch |
dlep |
"Once the DLEP session is established and if you" " want to change the threshold value kill the" " Radio and reconfigure the dlep on Router" " interface and make the Radio UP to see" " the updated threshold value " |
|
DLEP_SET_MSG-6-DLEP_NBR_ACTIVITY_TIMEOUT |
6-Information |
new nbr-activity-timeout value configured will have effect for the new sessions only not for the currently running DLEP sessions |
If the nbr-activity-timeout value should be updated at Router side it must be configured before the Radio launch |
dlep |
"Once the DLEP session is established and if you" " want to change the nbr-activity-timeout value" " kill the Radio and reconfigure the dlep on" " Router interface and make the Radio UP to see" " the updated value " |
|
DLEP_SET_MSG-6-DLEP_NBR_DOWN_ACK_TIMEOUT |
6-Information |
new nbr-down-ack-timeout value configured will have effect for the new sessions only not for the currently running DLEP sessions |
If the nbr-down-ack-timeout value should be updated at Router sideit must be configured before the Radio launch |
dlep |
"Once the DLEP session is established and if you want" " to change the nbr-down-ack-timeout value kill the " "Radio and reconfigure the dlep on Router interface " "and make the Radio UP to see the updated Value " |
|
DLEP_SET_MSG-6-DLEP_PEER_TERMINATE_ACK_TIMEOUT |
6-Information |
new peer-terminate-ack-timeout value configured will have effect for the new sessions only not for the currently running DLEP sessions |
If the peer-terminate-ack-timeout value should be updated Router side it must be configured before the Radio launch |
dlep |
"Once the DLEP session is established and if you want" " to change the peer-terminate-ack-timeout value" " kill the Radio and reconfigure the dlep on Router" " interface and make the Radio UP to see the updated value " |
|
DLINK-3-BAD_QELEM |
3-Error |
Bad queue elem - %08x: flink %08x blink %08x flink->blink %08x blink->flink %08x |
An internal software error occurred. |
DLINK_UTIL_DDTS_COMPONENT |
LOG_STD_RECUR_ACTION |
|
DLINK-3-NULL_QELEM |
3-Error |
Null queue elem |
An internal software error occurred. |
DLINK_UTIL_DDTS_COMPONENT |
LOG_STD_RECUR_ACTION |
|
DLR-2-GWFAULT |
2-Critical |
Ring [dec]: The redundant gateway device is now in FAULT state |
The redundant gateway device is in fault state |
accsw-layer2 |
"A redundant gateway device goes to fault state if " "all its uplinks are down. Check the status of all uplinks. Restore the connection if possible." |
|
DLR-2-GWPARTIALFAULT |
2-Critical |
Ring [dec]: The redundant gateway device is now in PARTIAL FAULT state |
The redundant gateway is in partial fault state |
accsw-layer2 |
"A redundant gateway device goes to partial fault " "state if it receives messages indicating that a redundant gateway device with lower precedence" " is active. Make sure that there's bidirectional connectivity between all redundant gateway devices" " and then clear the partial fault condition." |
|
DLR-2-MACFAILURE |
2-Critical |
Ring [dec]: [chars] |
Failed to update the supervisor MAC. |
accsw-layer2 |
"Remove and reconfigure the DLR ring. Make sure that a VLAN interface has been created for the VLAN that " "the ring ports belong to. Contact TAC if the problem persists." |
|
DLR-2-NOPROC |
2-Critical |
Failed to start [chars] process [chars] |
Unable to create DLR process. Reloading the device might resolve the issue. Without a reload DLR will not function properly. |
accsw-layer2 |
"Reload the device" |
|
DLR-2-RINGFAULT |
2-Critical |
Ring [dec]: The DLR ring is now in FAULT state |
The DLR ring is in FAULT state. This typically happens if a link or node in the ring goes down. |
accsw-layer2 |
"Determine the location of the fault and restore " "connectivity. The ring should resume functioning automatically" |
|
DLR-2-SUPPARTIALFAULT |
2-Critical |
Ring [dec]: The supervisor device is now in PARTIAL FAULT state |
The supervisor device goes to partial fault state if it detects loss of beacon frames in one direction only. |
accsw-layer2 |
"Determine the source of the problem and fix it. The device will resume normal operation automatically." |
|
DLR-2-SUPRAPIDFAULT |
2-Critical |
Ring [dec]: The supervisor device is now in RAPID FAULT state |
The supervisor device is in fault state. This happens if the device transitions from Normal to Fault state more than 5 times in 30 seconds. |
accsw-layer2 |
"Locate the source of the faults and fix the problem before clearing the rapid fault condition" |
|
DLR-3-EVENTFAILURE |
3-Error |
[chars] |
A DLR event could not be handled properly. |
accsw-layer2 |
"It could have been a temporary condition. Remove " "and reconfigure the DLR ring if the problem persists." |
|
DLR-3-GWCFGFAIL |
3-Error |
Ring [dec]: [chars] |
There was an issue with the DLR redundant gateway configuration. The redundant gateway may not function properly. |
accsw-layer2 |
"Remove and reconfigure DLR redundant gateway functionality. Contact TAC if the problem persists." |
|
DLR-3-GWUPLNKCFGFAIL |
3-Error |
Ring [dec]: [chars] |
There was an issue with the DLR redundant gateway uplink configuration. The redundant gateway may not function properly. |
accsw-layer2 |
"Remove and reconfigure DLR redudant gateway " "uplink configuration from the interface. Contact TAC if the problem persists." |
|
DLR-3-RINGCFGFAIL |
3-Error |
Ring [dec]: [chars] |
There was an issue with the DLR ring configuration. The ring may not function properly. |
accsw-layer2 |
"Remove and reconfigure the DLR ring. Contact TAC if the problem persists." |
|
DLR-3-SWSWITCH |
3-Error |
Ring [dec]: [chars] frames are being software switched |
Frames which should be hardware switched are being software switched. It's normal to see this message once or twice during configuration changes but not otherwise. It can make the ring unstable and drive up the CPU utilization. |
accsw-layer2 |
"Remove and reconfigure the DLR ring. Contact TAC if the problem persists." |
|
DLR-6-GWSTATECHG |
6-Information |
Ring [dec]: The device is now the [chars] redundant gateway |
The state of redundant gateway has changed |
accsw-layer2 |
"This is an informational message. The device is functioning as expected." |
|
DLR-6-RINGNORMAL |
6-Information |
Ring [dec]: The DLR ring is now in NORMAL state |
The state of the DLR ring has changed to NORMAL. |
accsw-layer2 |
"This is an informational message. The device is functioning as expected." |
|
DLR-6-SUPSPTPARAM |
6-Information |
Ring [dec]: Supported beacon parameters received |
This backup supervisor received beacons with supported parameters from active supervisor which can be supported by this device. |
accsw-layer2 |
"This backup supervisor device can take the role of active supervisor with current beacon parameters." |
|
DLR-6-SUPSTATECHG |
6-Information |
Ring [dec]: The device is now the [chars] supervisor |
The state of the supervisor device has changed |
accsw-layer2 |
"This is an informational message. The device is functioning as expected." |
|
DLR-6-SUPUNSPTPARAM |
6-Information |
Ring [dec]: Unsupported beacon parameters received |
This backup supervisor received beacons with parameters from active supervisor which cannot be supported by this device. |
accsw-layer2 |
"This backup supervisor device cannot take the " "role of active supervisor with current beacon parameters." |
|
DLSWC-3-BADCLSI |
3-Error |
[chars] primitive not valid for dlsw [chars] [chars] |
A data-link switching system error occurred. |
- |
LOG_STD_ACTION |
|
DLSWC-3-BADCLSICNF |
3-Error |
[chars] Invalid confirm [chars] [chars] |
A data-link switching system error occurred. |
- |
LOG_STD_ACTION |
|
DLSWC-3-BADCLSIIND |
3-Error |
[chars] Invalid indication [chars] [chars] |
A data-link switching system error occurred. |
- |
LOG_STD_ACTION |
|
DLSWC-3-BADCLSIRET |
3-Error |
[chars] Invalid ret code 0x[hec] [chars] [chars] |
A data-link switching system error occurred. |
- |
LOG_STD_ACTION |
|
DLSWC-3-BADCLSISAP |
3-Error |
[chars] Bad clsi SAP id = [hec] [chars] |
A data-link switching system error occurred. |
- |
LOG_STD_ACTION |
|
DLSWC-3-BADPEEROP |
3-Error |
bad peer op in peer_to_core [dec] |
A data-link switching system error occurred. |
- |
LOG_STD_ACTION |
|
DLSWC-3-BADSSPHDR |
3-Error |
bad ssp hdr in proc ssp - [chars] = 0x[hec] |
- |
- |
"If the remote peer is a nonCisco router confirm that it supports the\n\ DLSw RFC 1795 standard." |
|
DLSWC-3-IDMGR |
3-Error |
[chars] |
A data-link switching system error occurred. |
- |
LOG_STD_ACTION |
|
DLSWC-3-NODLSW |
3-Error |
[chars] [dec] |
A data-link switching system error occurred. |
- |
LOG_STD_ACTION |
|
DLSWC-3-NOPEER |
3-Error |
[chars] |
A data-link switching system error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
DLSWC-3-RECVSSP |
3-Error |
SSP OP = [dec][chars] [chars] from [chars] |
- |
- |
LOG_STD_NO_ACTION |
|
DLSWC-3-SENDSSP |
3-Error |
SSP OP = [dec][chars] [chars] to [chars] [chars] |
A Silicon Switch Program SSP frame was sent to the remote peer. |
- |
LOG_STD_NO_ACTION |
|
DLSWMasterSlave-3-DLSWMS |
3-Error |
[chars] |
DLSw Master-Slave Error |
- |
LOG_STD_NO_ACTION |
|
DLSWMasterSlave-3-DLSWMSCSM |
3-Error |
[chars] [chars] |
DLSw Master-Slave Error |
- |
LOG_STD_NO_ACTION |
|
DLSWMasterSlave-3-DLSWMSDLX |
3-Error |
[chars] [hec] from [enet] |
DLSw Master-Slave Error |
- |
LOG_STD_NO_ACTION |
|
DLSWMasterSlave-3-DLSWMSFSM |
3-Error |
[chars]: [chars] from [enet] |
DLSw Master-Slave Error |
- |
LOG_STD_NO_ACTION |
|
DLSWMasterSlave-3-DLSWMSRCV |
3-Error |
[chars] from [enet] |
DLSw Master-Slave Error |
- |
LOG_STD_NO_ACTION |
|
DLSWMasterSlave-3-DLSWMSSAP |
3-Error |
[chars]: [chars] |
DLSw Master-Slave Error |
- |
LOG_STD_NO_ACTION |
|
DLSWMasterSlave-3-DLSWMSTX |
3-Error |
[chars]: [chars] to [enet] |
DLSw Master-Slave Error |
- |
LOG_STD_NO_ACTION |
|
DLSWP-3-PBADVALUE |
3-Error |
[chars]: invalid [chars] [dec] |
A bad parameter value was passed to function chars1 - invalid\n\ parameter chars2 with value. This error should not cause any network\n\ problems unless it happens repeatedly. |
- |
LOG_STD_ACTION |
|
DLSWP-3-PCAPMISMATCH |
3-Error |
[chars]: [chars] |
The largest frame size configured in the DLSW remote peer definition\n\ is being changed because the MTU size configured\n\ on the interface used by DLSW is less than the configured value of\n\ the largest frame on DLSW remote peer definition. The largest frame size\n\ is being changed to that configured on the interface. |
- |
"If you wish to use this largest frame size for DLSW increase the\n\ MTU on the interface to a value larger than the configured largest\n\ frame size." |
|
DLSWP-3-PEERFAILURE |
3-Error |
[chars] [chars] |
A DLSW peer failed:\n\\n\ - keepalive failure dlsw between cisco peers is sending a peer keepalive\n\ by default every 30 sec. After missing 3 consecutive keepalives the peer\n\ is taken down.\n\ - We are not promiscuous Rej conn from peer a.b.c.d\n\ The local dlsw peer is not configured for promiscuous and we receive\n\ a request to open a dlsw peer for which we have no corresponding dlsw\n\ remote peer statement.\n\ - received tcp fini dlsw peer code has received a tcp fini from the \n\ underlaying tcp subsystem. To obey the tcp fini dlsw wring bring down \n\ the peer connection for which the tcp fini was received. |
- |
"- keepalive failure\n\ Check end to end connectivity between the DLSW peers\n\ - We are not promiscuous Rej conn from peer a.b.c.d\n\ correct your configuration. \n\ - received tcp fini\n\ Check the underlaying tcp connection between the two dlsw peers." |
|
DLSWP-3-PGENERAL |
3-Error |
[chars] |
A general error condition was detected as described in the message\n\ text. This error should not cause any network problems unless it\n\ happens repeatedly. |
- |
LOG_STD_ACTION |
|
DLSWP-3-PNOCOOKIE |
3-Error |
uninitalized peer [chars] from [inet][dec] to [inet][dec] |
DLSw received a packet on an uninitialized peer connection. |
- |
"Verify configuration and DLSw peer status on both routers". |
|
DLSWP-3-PNOMEM |
3-Error |
No memory to [chars] |
The router ran out of system memory for operation as described in the\n\ message text. Most likely the router image requires more system memory\n\ RAM than the router contains. |
- |
"Consult with your Cisco technical support representative\n\ about memory requirements for a specific image." |
|
DLSWP-3-PPASSIVE |
3-Error |
passive open failed from [inet][dec] -> [dec] |
- |
- |
"Consult with your Cisco technical support representative\n\ about memory requirements for a specific image." |
|
DLSWP-5-PEERUPDOWN |
5-Notice |
[chars] [chars] |
A DLSW peer is either connected or disconnected |
- |
"None informational message only." |
|
DMA-1-DRQ_EMPTY_PAK |
1-Alert |
Empty packet is being sent to backplane. particle_ptr=[hex] |
drq_io receives a packet that has particle count 0. coding error --\n\ hurt performance |
high-vip2 |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative. If possible also provide the\n\ show log on the reporting VIP" |
|
DMA-1-DRQ_STALLED |
1-Alert |
DRQ stalled. Dumping DRQ. |
The path from VIP to backplane has stalled. The DRQ table is \n\ being dumped for debugging |
high-vip2 |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative. If possible also provide the hex\n\ dump following this message" |
|
DMA-1-LOW_DMA_PCI_MEM |
1-Alert |
Not enough pci memory left over for DMA |
Misconfiguration has resulted in overutilization of PCI memory |
high-vip2 |
"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 show diag and show controller cbus" |
|
DMA-1-LOW_DMA_PROC_MEM |
1-Alert |
Not enough processor memory left over for DMA |
This error message appears only in custom built images when a sanity\n\ check fails. A packet that was too large was sent over the backplane\n\ by a VIP. |
high-vip2 |
"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 show tech." |
|
DMA-3-DTQ_DISPATCH_DIRTY_PAK |
3-Error |
pak not cleaned up by Egress processing appId [dec] |
After dtq dispatched a packet to Egress processing packet is not cleaned up by application |
high-vip2 |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative. If possible also provide the\n\ show log on the reporting VIP" |
|
DMB-0-DMB_EMERG |
0-Emergency |
[chars] |
DMB_INTERNAL_ERROR |
DMB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
DMB-1-DMB_ALERT |
1-Alert |
[chars] |
DMB_INTERNAL_ERROR |
DMB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
DMB-2-DMB_CRIT |
2-Critical |
[chars] |
DMB_INTERNAL_ERROR |
DMB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
DMB-3-DMB_ERR |
3-Error |
[chars] |
DMB_INTERNAL_ERROR |
DMB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
DMB-4-DMB_WARNING |
4-Warning |
[chars] |
DMB_INTERNAL_ERROR |
DMB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
DMB-5-DMB_NOTICE |
5-Notice |
[chars] |
Normal but significant conditions |
DMB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
DMB-6-DMB_INFO |
6-Information |
[chars] |
Informational messages |
DMB_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
DMB-7-DMB_ASSERT |
7-Debug |
Assertion Failure [chars] @[chars]:[dec] : [chars] |
DMB_INTERNAL_ERROR |
DMB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
DMTDSL-1-INITFAIL |
1-Alert |
DMTDSL[dec]/[dec] Init failed [chars] |
The ADSL network module hardware may be bad |
- |
LOG_STD_ACTION |
|
DMTDSL-3-BADINITDSL |
3-Error |
DMTDSL[dec]/[dec]interface not initialized. |
The ATM network module hardware may be bad |
pm-atm25 |
LOG_STD_ACTION |
|
DMTDSL-3-DMTHWBAD |
3-Error |
DMTDSL[dec]/[dec] Hardware failed self test |
The DSL chipset failed its self test |
- |
LOG_STD_ACTION |
|
DMTDSL-3-FAILFINDATM |
3-Error |
DMTDSL Could not find ATM interface. |
The DSL network module hardware may be bad |
pm-atm25 |
LOG_STD_ACTION |
|
DMTDSL-3-NOMEM |
3-Error |
DMTDSL[dec]/[dec] Out of memory |
The router does not have enough memory installed to run this image |
- |
LOG_STD_ACTION |
|
DMVPN-3-DMVPN_NHRP_ERROR |
3-Error |
[chars]: [chars] [chars] Reason: [chars] [dec] on Tunnel: [chars] NBMA: [chars] |
NHRP Error messages |
nhrp |
LOG_STD_ACTION |
|
DMVPN-3-DMVPN_NHRP_MULTICAST_ERR |
3-Error |
[chars]: [chars] on Tunnel: [chars] NBMA: [chars] |
NHRP Multicast Replication Error messages |
nhrp |
LOG_STD_ACTION |
|
DMVPN-3-NHRP_ERROR |
3-Error |
[chars]: [chars] failed for [chars] [chars] [dec] for Tunnel: [chars] NBMA: [chars] on Tunnel: [chars] NBMA: [chars] |
Unable to send/receive packets. |
nhrp |
LOG_STD_ACTION |
|
DMVPN-3-NHRP_REGISTRATION_ERROR |
3-Error |
[chars]: [chars] [chars] Error indication for [chars] - [chars][dec] Src Tunnel: [chars] NBMA: [chars] Dest Tunnel: [chars] NBMA: [chars] |
NHRP Registration send/receive Error Indication packets. |
nhrp |
LOG_STD_ACTION |
|
DMVPN-3-NHRP_RESOLUTION_ERROR |
3-Error |
[chars]: [chars] [chars] Error indication for [chars] - [chars][dec] Src Tunnel: [chars] NBMA: [chars] Dest Tunnel: [chars] NBMA: [chars] |
NHRP Resolution send/receive Error Indication packets. |
nhrp |
LOG_STD_ACTION |
|
DMVPN-4-NHRP_QUOTA |
4-Warning |
[chars]: Max-send Quota of [dec]pkts/[dec]sec exceeded on Tunnel: [chars] NBMA: [chars] |
nhrp quota exceeded |
nhrp |
LOG_STD_ACTION |
|
DMVPN-5-CRYPTO_SS |
5-Notice |
[chars]: local address : [chars] remote address : [chars] socket is [chars] |
DMVPN Crypto UP/DOWN Syslog Event |
nhrp |
LOG_STD_ACTION |
|
DMVPN-5-NHRP_NETID_UNCONFIGURED |
5-Notice |
[chars]: NETID : [dec] [chars] Tunnel: [chars] NBMA: [chars] |
NETID Unconfigured |
nhrp |
LOG_STD_ACTION |
|
DMVPN-5-NHRP_NHC_DOWN |
5-Notice |
[chars]: Next Hop [chars] : Tunnel: [chars] NBMA: [chars] for Tunnel: [chars] NBMA: [chars] is [chars] Reason: [chars]NHRP: [chars] |
Next Hop Client changed the state. |
nhrp |
LOG_STD_ACTION |
|
DMVPN-5-NHRP_NHC_UP |
5-Notice |
[chars]: Next Hop [chars] : Tunnel: [chars] NBMA: [chars] for Tunnel: [chars] NBMA: [chars] is [chars] |
Next Hop Client changed the state. |
nhrp |
LOG_STD_ACTION |
|
DMVPN-5-NHRP_NHP_DOWN |
5-Notice |
[chars]: Next Hop [chars] : Tunnel: [chars] NBMA: [chars] for Tunnel: [chars] NBMA: [chars] is [chars] Reason: [chars]NHRP: [chars] |
Next Hop Peer changed the state. |
nhrp |
LOG_STD_ACTION |
|
DMVPN-5-NHRP_NHP_UP |
5-Notice |
[chars]: Next Hop [chars] : Tunnel: [chars] NBMA: [chars] for Tunnel: [chars] NBMA: [chars] is [chars] |
Next Hop Peer changed the state. |
nhrp |
LOG_STD_ACTION |
|
DMVPN-5-NHRP_NHS_DOWN |
5-Notice |
[chars]: Next Hop [chars] : Tunnel: [chars] NBMA: [chars] for Tunnel: [chars] NBMA: [chars] is [chars] Reason: [chars]NHRP: [chars] |
Next Hop Client changed the state. |
nhrp |
LOG_STD_ACTION |
|
DMVPN-5-NHRP_NHS_UP |
5-Notice |
[chars]: Next Hop [chars] : Tunnel: [chars] NBMA: [chars] for Tunnel: [chars] NBMA: [chars] is [chars] |
Next Hop Client changed the state. |
nhrp |
LOG_STD_ACTION |
|
DMVPN-5-NHRP_RES_REPLY |
5-Notice |
[chars]: [chars] [chars] sent via Tunnel: [chars] NBMA: [chars] to Tunnel: [chars] NBMA: [chars] |
A NHRP Resolution Reply sent via the NHS Path |
nhrp |
LOG_STD_ACTION |
|
DMVPN-5-NHRP_RES_REPLY_IGNORE |
5-Notice |
[chars]: resolution reply received on [chars] for dst : [chars] is dropped crypto session failed to come up |
A NHRP Resolution Reply received through Hub which is dropped - crypto session failed to come up |
nhrp |
LOG_STD_ACTION |
|
DMVPN-5-NHRP_ROUTING |
5-Notice |
Peer with Tunnel: [chars] NBMA: [chars] on [chars] [chars] with Reason :[chars] . |
A short cut switching entry has been created |
nhrp |
LOG_STD_ACTION |
|
DMVPN-6-NHRP_RES |
6-Information |
[chars]: Host with Tunnel: [chars] NBMA: [chars] [chars] Tunnel: [chars] NBMA: [chars] |
A NHRP Resolution Request has been received |
nhrp |
LOG_STD_ACTION |
|
DMVPN-6-NHRP_RES_TIMEOUT |
6-Information |
[chars]: [chars] for Address : [chars] is Timed-out |
A NHRP Resolution Request has timed-out |
nhrp |
LOG_STD_ACTION |
|
DMVPN-6-NHRP_RESOLUTION_REPLY |
6-Information |
[chars]: Host with Tunnel: [chars] NBMA: [chars] [chars] Tunnel: [chars] NBMA: [chars] |
A NHRP Resolution Reply has been received |
nhrp |
LOG_STD_ACTION |
|
DMVPN-7-NHRP_EVENT |
7-Debug |
[chars]: [chars] [chars] [chars] [chars] [chars] |
A Registration/Resolution Request/Reply Received/Sent |
nhrp |
LOG_STD_ACTION |
|
DNET-3-HEARSELF |
3-Error |
Hello type [hec] for my address from [dec].[dec] via [chars] |
The system is receiving its own DECnet packets. Either a serial line\n\ is looped back or another host with the same DECnet address is already\n\ present on the LAN. |
- |
"Check the serial lines if present and the DECnet configuration." |
|
DNET-3-NOMEMORY |
3-Error |
Insufficient memory for DECnet accounting entry |
The traffic information for a particular pair of DECnet nodes \n\ cannot be recorded due to a low memory condition. |
decnet |
LOG_STD_REDUCE_ACTION |
|
DNET-4-DUPENTRY |
4-Warning |
Duplicate DECnet Accounting List Entry for nodes [dec].[dec] - [dec].[dec] |
A synchronization problem has occurred whilst a new transit \n\ DECnet Accounting List Entry was being added and a duplicate entry\n\ has been found. |
decnet |
show decnet accounting |
|
DNET-4-MAPCON |
4-Warning |
Map entry [dec].[dec] conflicts with adjacency to [dec].[dec] |
Your DECnet configuration is incorrect. A host that is specified as\n\ nonlocal is present on your local network. |
- |
"Correct the configuration. Call your technical support representative\n\ if you need assistance." |
|
DNLD-3-ERROR |
3-Error |
[chars] |
Error on DNLD module. |
- |
LOG_STD_SH_TECH_ACTION |
|
DNLD-6-DSPFARM_REGISTER_FAILED |
6-Information |
Failed to register DNLD Application with DSPFARM\n |
Failed to register DNLD Application with DSPFARM. |
- |
LOG_STD_SH_TECH_ACTION |
|
DNSSERVER-3-BADQUERY |
3-Error |
Bad DNS query from [inet] |
A client sent a DNS query to the server which has been found to be incorrectly formatted. |
- |
"Check the DNS server and the network attached to it." |
|
DNSSERVER-3-NOINIT |
3-Error |
Can't initialize DNS server |
Internal problems with initializing ports for the DNS server |
- |
"Make sure the DNS server port is available on the local machine." |
|
DNSSERVER-3-TCPDNSOVERLOAD |
3-Error |
Low available memory: dropping TCP request from <cli [inet]>. |
There is not enough free memory to handle DNS queries. |
- |
"DNS server is automatically discarding DNS request traffic." |
|
DNSSERVER-3-TOOSHORT |
3-Error |
DNS query from [inet] too short |
A client sent a short DNS query packet to the server |
- |
"Check the client and the network attached to it." |
|
DNSSERVER-3-UDPDNSOVERLOAD |
3-Error |
Low available memory: dropping <id# [dec]> from <cli [inet]>. |
There is not enough free memory to handle DNS queries. |
- |
"DNS server is automatically discarding DNS request traffic." |
|
DOMAIN-2-GLOBALS_XML_FAILURE |
2-Critical |
[chars] |
Failed to decode xml message containing global parameters |
ng-pfr |
"Check if software versions are compatible" |
|
DOMAIN-2-IME |
2-Critical |
Immitigable event occured. IME-ID=[dec]: Details: [chars]\n |
Error encounterd during TCA processing. The flow could not be placed on alternate path. |
ng-pfr |
"Troubleshoot the network for performance/bandwidth issues." |
|
DOMAIN-2-IME_DETAILS |
2-Critical |
IME-ID=[dec]: [chars]\n |
Error encounterd during TCA processing. The flow could not be placed on alternate path. |
ng-pfr |
"Troubleshoot the network for performance/bandwidth issues." |
|
DOMAIN-2-PMI_XML_FAILURE |
2-Critical |
[chars] |
Failed to decode xml message containing pmi parameters |
ng-pfr |
"Check if software versions are compatible" |
|
DOMAIN-2-POLICY_XML_FAILURE |
2-Critical |
[chars] |
Failed to decode xml message containing policy definition |
ng-pfr |
"On Hub MC check if invalid characters are used in policy name" |
|
DOMAIN-3-HUB_SITE_ID_ERR |
3-Error |
[chars] |
Hub site-id error notification. |
ng-pfr |
"Correct the Hub MC ip-address configuration" |
|
DOMAIN-3-INVALID_EXIT |
3-Error |
[chars] |
Inavlid Exit notification. |
ng-pfr |
"Correct the PLR interface configuration" |
|
DOMAIN-3-PLR_INT_CFG |
3-Error |
[chars] |
Conflicting Domain configuration exists on the selected WAN interface on border. |
ng-pfr |
"Correct the domain path configuration on selected WAN interface on border and retry." |
|
DOMAIN-4-BR_SHUTDOWN |
4-Warning |
Reason=[chars] |
Border Shutdown Warning Message. |
ng-pfr |
LOG_STD_NO_ACTION |
|
DOMAIN-4-DCA_DOMAIN_MAP |
4-Warning |
[chars] |
DCA domain map error notification. |
ng-pfr |
"Correct the branch MC domain-map configuration." |
|
DOMAIN-4-MC_SHUTDOWN |
4-Warning |
Reason=[chars] |
Master Controller Shutdown Warning Message. |
ng-pfr |
LOG_STD_NO_ACTION |
|
DOMAIN-4-PDP_PREFIX_REACH |
4-Warning |
[chars] |
Prefix not reachable on the channel |
ng-pfr |
"Verify the reachability of the prefix" |
|
DOMAIN-4-SITE_PREFIX |
4-Warning |
[chars] |
Improper site prefix configuration detected. |
ng-pfr |
"Correct your site prefix configuration" |
|
DOMAIN-4-SMP |
4-Warning |
[chars] |
Smart-Probe config is being changed |
ng-pfr |
LOG_STD_NO_ACTION |
|
DOMAIN-4-TUN_SRC_OVERLAPPED |
4-Warning |
[chars] |
Tunnel source overlapped notification. |
ng-pfr |
"Correct the source configuration." |
|
DOMAIN-4-WAN_INTERFACE |
4-Warning |
Interface \[chars]\ received probes but no \dynamic-path\ configured |
- |
- |
- |
|
DOMAIN-4-WAN_INTERFACE_TYPE_CONFLICT |
4-Warning |
Interface \[chars]\ discoveried as WAN interface. But DCA already configured. |
Branch site border router WAN interface must have dynamic-path configured |
ng-pfr |
"configure domain <domain name> dynamic-path on WAN interface" |
|
DOMAIN-5-BR_STATUS |
5-Notice |
[chars] |
Border Status Notification. |
ng-pfr |
LOG_STD_NO_ACTION |
|
DOMAIN-5-MC_STATUS |
5-Notice |
[chars] |
Master Controller Status Notification. |
ng-pfr |
LOG_STD_NO_ACTION |
|
DOMAIN-5-TC_PATH_CHG |
5-Notice |
Traffic class Path Changed. Details: [chars]\n |
A Path chage is made. |
ng-pfr |
LOG_STD_NO_ACTION |
|
DOMAIN-5-TCA |
5-Notice |
[chars] Received. Details: [chars]\n |
A threshold crossing alarm is raised. |
ng-pfr |
LOG_STD_NO_ACTION |
|
DOMAIN-6-INIT |
6-Information |
[chars] |
Informational Message. Domain master controller initialization completed |
ng-pfr |
LOG_STD_NO_ACTION |
|
DOMAIN-6-MC_POLICY_DOWNLOAD |
6-Information |
Master Controller policy downloaded: site_id=[inet] domain=[chars] vrf=[chars] |
Master Controller policy downloaded. |
ng-pfr |
LOG_STD_NO_ACTION |
|
DOMAIN-6-MC_TC_ID_RESET |
6-Information |
Master Controller traffic class id counter got reset: site_id=[inet] domain=[chars] vrf=[chars] |
Master Controller traffic class id counter got reset. |
ng-pfr |
LOG_STD_NO_ACTION |
|
DOMAIN-6-TC_CTRL |
6-Information |
Traffic Class Controlled. Details: [chars]\n |
A Traffic Class is Controlled. |
ng-pfr |
LOG_STD_NO_ACTION |
|
DOMAIN-6-TC_NEW |
6-Information |
Traffic Class Learned. Details: [chars]\n |
A Traffic Class is Learned. |
ng-pfr |
LOG_STD_NO_ACTION |
|
DOSFS-3-RESETERR |
3-Error |
[chars] [chars] |
disk could not be reset while the system is initiated reload. This will cause a transient disk error disk timeout error when the ROMMON initialization code tries to reads the DIB. This is a transient error and the system will be able to access the disk and continue normal operation. |
- |
LOG_STD_NO_ACTION |
|
DOSFS-4-DFS_FSCK_ERR |
4-Warning |
Error while running fsck on the file [chars]. |
Fsck is running in a loop while walking through the cluster chain of a file and has aborted. |
ata-filesystem |
LOG_STD_DDTS_TAC_DETAILS |
|
DOSFS-5-DFS_CLOSE_ERR |
5-Notice |
Error during close of the file [chars]. [chars] |
An error occured during a file close operation. |
- |
"Enter the <CmdBold>fsck<NoCmdBold> <CmdArg>filesystem prefix:<NoCmdArg> " "command to check and attempt to repair the disk. If this does not " "fix the problem format the disk." |
|
DOSFS-5-DIBERR |
5-Notice |
[chars] [chars] |
The system cannot boot a image from the Flash disk because the Device Information Block is different. The Flash disk can be read by the router but will require formatting by the router before an image can be booted from it. |
- |
"Follow any instructions provided in the error " "message. Before storing a image in the Flash disk " "and trying to boot from this device enter the " "format command to format the flash disk from the " "router. Then copy the desired image to the Flash " "disk and then boot from this device." |
|
DOT1AD-4-DOT1QTUNNEL_PORT |
4-Warning |
Port [chars] is a dot1q-tunnel port it conflicts with Dot1ad configuration |
Dot1ad configuration cannot co-exist with dot1q-tunnel ports. |
dot1ad |
"Turn off dot1q-tunnel configuration on the ports before enabling Dot1ad." |
|
DOT1AD-4-DOT1X_PORT |
4-Warning |
Port [chars] is configured for DOT1X it conflicts with Dot1ad configuration |
Dot1ad configuration cannot co-exist with DOT1X enabled ports. |
dot1ad |
"Turn off DOT1X configuration on the ports before enabling Dot1ad." |
|
DOT1AD-4-ETHERTYPEMISMATCH_PORT |
4-Warning |
Port [chars] ethertype cannot be changed to Dot1ad ethertype it conflicts with Dot1ad configuration |
The ethertype on the port cannot be changed to Dot1ad ethertype. |
dot1ad |
"Replace the module with one which can support ethertype change or " "power down the module before enabling Dot1ad." |
|
DOT1AD-4-L2PT_PORT |
4-Warning |
Port [chars] is a l2protocol-tunnel port it conflicts with Dot1ad configuration |
Dot1ad configuration cannot co-exist with l2protocol-tunnel ports. |
dot1ad |
"Turn off l2protocol-tunnel configuration on the ports before enabling " "Dot1ad." |
|
DOT1AD-4-LACP_PORT |
4-Warning |
Port [chars] is a part of an LACP channel it conflicts with Dot1ad configuration |
Dot1ad configuration cannot co-exist with LACP ports. |
dot1ad |
"Turn off LACP configuration on the ports before enabling Dot1ad." |
|
DOT1AD-4-OAM_PORT |
4-Warning |
Port [chars] is configured for OAM it conflicts with Dot1ad configuration |
Dot1ad configuration cannot co-exist with OAM enabled ports. |
dot1ad |
"Turn off OAM configuration on the ports before enabling Dot1ad." |
|
DOT1AD-4-PLATFORM_RESOURCE_UNAVAILABLE |
4-Warning |
Platform does not have resouces to support dot1ad configuration |
In the 6500 platform hardware match registers are not available for dot1ad use. |
dot1ad |
"Unconfigure the features using the match registers cfm cgvrp and " |
|
DOT1AD-4-STP_CONFLICT |
4-Warning |
STP mode conflicts with Dot1ad configuration as it is not in MST mode |
Current STP mode conflicts with Dot1ad configuration. |
dot1ad |
"Change the STP mode to MST before enabling Dot1ad." |
|
DOT1Q_TUNNELLING-4-MTU_WARNING |
4-Warning |
\nSystem MTU of [dec] might be insufficient for 802.1Q tunnelling.\n 802.1Q tunnelling requires system MTU size of [dec] to handle maximum size ethernet frames.\n\n |
With 802.1Q tunnelling the system MTU setting needs to take into account the four byte overhead associated with the additional 802.1Q tag. |
firmware |
"Issue the <CmdBold>system mtu<noCmdBold> " "global configuration command to adjust system MTU to take into " "account the additional 802.1Q tag." |
|
DOT1X_MOD-3-NULLPTR |
3-Error |
Unexpected null pointer in [chars] at [dec] |
An internal software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
DOT1X_SWITCH-4-PROC_START_ERR |
4-Warning |
Unable to start dot1x switch process. |
The system failed to create the Dot1x switch process. |
- |
"Reload the device" |
|
DOT1X_SWITCH-5-ERR_ADDING_ADDRESS |
5-Notice |
Unable to add address [enet] on [chars] AuditSessionID [chars] |
The authenticated host's address could not be added. This is likely because either the TCAM is full or the address exists as a secure address on another port. |
- |
"If the TCAM is full clear some dynamic addresses to make " "room for the host's address. If the host's address is " "secured on another port manually remove it from that port." |
|
DOT1X_SWITCH-5-ERR_INVALID_PRIMARY_VLAN |
5-Notice |
Attempt to assign primary VLAN [chars] to 802.1x port [chars] AuditSessionID [chars] |
An attempt was made to assign a primary VLAN to an 802.1x port which is not allowed. |
- |
"Update the configuration to use a different VLAN." |
|
DOT1X_SWITCH-5-ERR_INVALID_SEC_VLAN |
5-Notice |
Attempt to assign invalid secondary VLAN [chars] to PVLAN host 802.1x port [chars] AuditSessionID [chars] |
An attempt was made to assign a non-secondary VLAN to a PVLAN host 802.1x port. |
- |
"Change the mode of the port so that it is no longer a PVLAN host " "port or use a valid secondary VLAN." |
|
DOT1X_SWITCH-5-ERR_PRIMARY_VLAN_NOT_FOUND |
5-Notice |
Attempt to assign VLAN [chars] whose primary VLAN does not exist or is shutdown to 802.1x port [chars] AuditSessionID [chars] |
An attempt was made to assign a private VLAN whose primary VLAN does not exist or is shutdown. |
- |
"Make sure the primary VLAN exists and is not shutdown. Also verify that " "the private VLAN is associated with a primary VLAN." |
|
DOT1X_SWITCH-5-ERR_SEC_VLAN_INVALID |
5-Notice |
Attempt to assign secondary VLAN [chars] to non-PVLAN host 802.1x port [chars] AuditSessionID [chars] |
An attempt was made to assign a secondary VLAN to a port that is not a PVLAN host port which is not allowed. |
- |
"Change the mode of the port so that it is configured as a PVLAN host " "port or use a different VLAN that is not configured as a secondary " "VLAN." |
|
DOT1X_SWITCH-5-ERR_SPAN_DST_PORT |
5-Notice |
Attempt to assign VLAN [chars] to 802.1x port [chars] which is configured as a SPAN destination AuditSessionID [chars] |
An attempt was made to assign a VLAN to an 802.1x port which is configured as a SPAN destination port |
- |
"Change the SPAN configuration so that the port is no longer a " "SPAN destination port or change the configuration so that no " "VLAN is assigned." |
|
DOT1X_SWITCH-5-ERR_VLAN_EQ_MDA_INACTIVE |
5-Notice |
Multi-Domain Authentication cannot activate because Data and Voice VLANs are the same on port AuditSessionID [chars] |
Multi-Domain Authentication host mode cannot activate if the configured Data VLAN on a port is the same as Voice VLAN. |
- |
"Change either the Voice VLAN or the access VLAN on " "the interface so they are not equal anymore. This will cause " "Multi-Domain authentication to activate." |
|
DOT1X_SWITCH-5-ERR_VLAN_EQ_VVLAN |
5-Notice |
Data VLAN [chars] on port [chars] cannot be equivalent to the Voice VLAN AuditSessionID [chars] |
An attempt was made to assign a data VLAN to an 802.1x port that is the same as the voice VLAN. |
- |
"Change either the Voice VLAN or the access/802.1x assigned VLAN on " "the interface so they are not equal anymore. This will cause the " "authentication to proceed normally on the next retry." |
|
DOT1X_SWITCH-5-ERR_VLAN_INTERNAL |
5-Notice |
Attempt to assign internal VLAN [chars] to 802.1x port [chars] AuditSessionID [chars] |
An attempt was made to assign an invalid VLAN to an 802.1x port. The VLAN specified is used internally and cannot be assigned to this port. |
- |
"Update the configuration not to use this VLAN." |
|
DOT1X_SWITCH-5-ERR_VLAN_INVALID |
5-Notice |
Attempt to assign invalid VLAN [chars] to 802.1x port [chars] AuditSessionID [chars] |
An attempt was made to assign an invalid VLAN to an 802.1x port. The VLAN specified is out of range and cannot be assigned to this port. |
- |
"Update the configuration to use a valid VLAN." |
|
DOT1X_SWITCH-5-ERR_VLAN_NOT_FOUND |
5-Notice |
Attempt to assign non-existent or shutdown VLAN [chars] to 802.1x port [chars] AuditSessionID [chars] |
An attempt was made to assign a VLAN to an 802.1x port but the VLAN was not found in the VTP database. |
- |
"Make sure the VLAN exists and is not shutdown or use another VLAN." |
|
DOT1X_SWITCH-5-ERR_VLAN_ON_ROUTED_PORT |
5-Notice |
Attempt to assign VLAN [chars] to routed 802.1x port [chars] AuditSessionID [chars] |
An attempt was made to assign a VLAN to a routed 802.1x port which is not allowed. |
- |
"Change the mode of the port so that it is no longer a routed port " "or change the configuration so that no VLAN is assigned." |
|
DOT1X_SWITCH-5-ERR_VLAN_PROMISC_PORT |
5-Notice |
Attempt to assign VLAN [chars] to promiscuous 802.1x port [chars] AuditSessionID [chars] |
An attempt was made to assign a VLAN to a promiscuous 802.1x port which is not allowed. |
- |
"Change the mode of the port so that it is no longer a promiscuous port " "or change the configuration so that no VLAN is assigned." |
|
DOT1X_SWITCH-5-ERR_VLAN_RESERVED |
5-Notice |
Attempt to assign reserved VLAN [chars] to 802.1x port [chars] AuditSessionID [chars] |
An attempt was made to assign an invalid VLAN to an 802.1x port. The VLAN specified is a reserved VLAN and cannot be assigned to this port. |
- |
"Update the configuration not to use this VLAN." |
|
DOT1X_SWITCH-5-ERR_VLAN_RSPAN |
5-Notice |
Attempt to assign RSPAN VLAN [chars] to 802.1x port [chars]. 802.1x is incompatible with RSPAN AuditSessionID [chars] |
An attempt was made to assign a Remote SPAN VLAN to an 802.1x port. Remote SPAN should not be enabled on a VLAN in which ports are configured with 802.1x enabled. |
- |
"Either disable Remote SPAN configuration on the VLAN OR disable " "802.1x on all the ports in this VLAN." |
|
DOT1X-4-MEM_UNAVAIL |
4-Warning |
Memory was not available to perform the 802.1X action. AuditSessionID [chars] |
Insufficient system memory is available to perform the Dot1x Authentication. |
- |
"Reduce other system activity to ease memory " "demands. If conditions warrant upgrade to " "a larger memory configuration." |
|
DOT1X-4-PROC_START_ERR |
4-Warning |
Dot1x unable to start. |
The system failed to create the Dot1x process. |
- |
"Restart Dot1x process by entering <cmd>dot1x " "system-auth-control<cmd> command. If this message " "recurs Reload the device." |
|
DOT1X-4-UNKN_ERR |
4-Warning |
An unknown operational error occurred. |
The Dot1x process cannot operate due to an internal system error. |
- |
"Reload the device" |
|
DOT1X-5-FAIL |
5-Notice |
Authentication failed for client [chars] on Interface [chars] |
Authentication was unsuccessful. |
- |
LOG_STD_NO_ACTION |
|
DOT1X-5-IGNORE_LARGER_EAPOL |
5-Notice |
EAPOL packet size[dec] to be sent is larger than MTU |
Targetted EAPOL packet size is larger than mtu size of the port on which client is connected and hence ignoring the packet to be sent out |
802.1x |
"Configure AAA server to fragement eap-method" " data so that EAPOL size is smaller than interface MTU size" |
|
DOT1X-5-RESULT_OVERRIDE |
5-Notice |
Authentication result overridden for client [chars] on Interface [chars] |
Authentication result was overridden |
- |
LOG_STD_NO_ACTION |
|
DOT1X-5-SUCCESS |
5-Notice |
Authentication successful for client [chars] on Interface [chars] |
Authentication was successful. |
- |
LOG_STD_NO_ACTION |
|
DOT1X-6-INFO_EAPOL_PING_RESPONSE |
6-Information |
The interface [chars] has an 802.1x capable client with MAC [enet] |
An EAPOL ping was sent out on this port to determine 802.1x readiness of the client attached. An EAPOL response has been received by the device such as a PC. |
802.1x |
"No action required." |
|
DPP_SYSLOG-3-EVENT_ERR |
3-Error |
Pipeline event - [chars] [chars] |
Output to syslog from pipeline |
- |
"" |
|
DPP_SYSLOG-4-EVENT_WARNING |
4-Warning |
Pipeline event - [chars] [chars] |
Output to syslog from pipeline |
- |
"" |
|
DPP_SYSLOG-6-EVENT_INFO |
6-Information |
Pipeline event - [chars] [chars] |
Output to syslog from pipeline |
- |
"" |
|
DPSS-2-IPC_INIT |
2-Critical |
IPC message handler registration failure rc [dec] |
Registering an IPC message handler for the DPSS feature failed. This will cause the feature to not function. |
qfp-dpss |
"This is normally a software issue. " "The consequences are that the DPSS feature will not function. " LOG_STD_ACTION |
|
DPSS-3-DPSS_INIT_FAILED |
3-Error |
DPSS [chars] Register failed |
DPSS Initialization of registration failed. |
cpp-ucode |
LOG_STD_ACTION |
|
DPSS-3-IPC_NORES |
3-Error |
No space for the IPC reply size [dec] |
For a request from upper DPSS software stack layers it was not possible to allocate space for a reply for the specified size. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation. |
qfp-dpss |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
DPSS-3-IPC_OPEN_REPLY |
3-Error |
IPC Open Reply failed request [dec] |
For a request from upper DPSS software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation. |
qfp-dpss |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
DPSS-3-MEM_INIT_FAILED |
3-Error |
Allocation of [chars] memory failed for DPSS |
DPSS Initialization of channel pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
DPSS-3-PKT_REPLICA_INIT_FAILED |
3-Error |
Register to Generic Packet Replication failed for DPSS |
DPSS Initialization of packet replication registration failed. |
cpp-ucode |
LOG_STD_ACTION |
|
DRIP-3-DRIPFAIL |
3-Error |
DRIP: Assertion failed: [chars] |
An internal software error has occurred. |
- |
LOG_STD_ACTION |
|
DRIP-6-DRIP_CONFLICT |
6-Information |
DRIP conflict with CRF [dec]. |
A DRIP conflict has occured. The virtual ring or pseudo ring's\n\ CRF is being re-used in the network. |
- |
"Make sure that the CRF vlanid of the virtual ring and the \n\ pseudo ring is unique in the network." |
|
DRMI-3-IPC_ERROR |
3-Error |
[chars][chars] [hec] rc:[chars] |
ERM Framework is experiencing errors when communicating to Line Cards using IPC |
rmi |
"show ipc ports" |
|
DRMI-3-ISSU_ERR |
3-Error |
[chars] error:[dec] |
ERM Framework is experiencing ISSU Errors |
rmi |
"show ipc ports" |
|
DRMI-3-ISSU_MTU |
3-Error |
Client id:[dec] MTU failed error:[dec] |
ERM Framework is experiencing Errors when performing ISSU GET MTU during a transmit operation |
rmi |
"show issu nego" |
|
DRMI-3-ISSU_RCV |
3-Error |
Client id:[dec] receive failed error:[dec] |
ERM Framework is experiencing Errors when performing ISSU Transformation during a receive operation |
rmi |
"show ipc ports" |
|
DRMI-3-ISSU_XMIT |
3-Error |
Client id:[dec] xmit failed error:[dec] |
ERM Framework is experiencing Errors when performing ISSU Transformation during a transmit operation |
rmi |
"show ipc ports" |
|
DROP-3-DOUBLE_DROP |
3-Error |
First drop error cause [dec] update stat cause [dec] trace: [hec] [hec] |
The drop infrastructure was called for a packet that was previously dropped. |
cpp-ucode |
LOG_STD_ACTION |
|
DROP-3-RESERVED |
3-Error |
[chars] |
An invalid drop cause was passed to the drop infrastructure. |
cpp-ucode |
LOG_STD_ACTION |
|
DRP-3-MULTICOMMAND |
3-Error |
multiple DRP commands encountered |
Multiple DRP commands were found in a single DRP packet. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
DRP-3-NOSOCKET |
3-Error |
Unable to open socket |
The requested operation could not be accomplished because of a low\n\ memory condition. |
- |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
DRP-3-NOWRITE |
3-Error |
unable to send response to [inet]:[dec] |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
DRP-3-SUBNETTED |
3-Error |
unable to determine metric for [inet] [inet] subnetted |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
DRP-7-NOROUTE |
7-Debug |
no route for destination [inet] |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
DS_MODEM-3-BADCB |
3-Error |
Unexpected DSIP data callback for modem |
An unexpected software event occurred. |
- |
LOG_STD_ACTION |
|
DS_MODEM-3-FLOW_CONTROL |
3-Error |
DS-RS flow control has got out of sync connection has too many particles free.\n\ slot:[dec] ttynum:[dec] parts_avail:[dec] |
Indicates the flow control accounting on the DS has got out of sync.\n\ |
- |
LOG_STD_ACTION |
|
DS_MODEM-3-NORXPAK |
3-Error |
Static receive paktype unavailable |
Temporarily unable to allocate particle for sending traffic to\n\ modem module indicates a break down of flow control between RS-DS. |
- |
LOG_STD_ACTION |
|
DS_PHY-2-UPX_SPI_ERR |
2-Critical |
[chars] |
- |
- |
- |
|
DS_PHY-3-RM_JIB_IF_ERROR |
3-Error |
Remora hw reset failure - [chars] |
Cannot hw reset DS PHY |
ubr10k-sw |
"Copy the error message exactly as it appears and report it to your " "technical support" |
|
DS_PHY-3-UPX_UPGRADE_ERROR |
3-Error |
check/upgrade failure - [chars] |
upconverter - can't check version or upgrade |
ubr10k-sw |
"check type of upconverter" |
|
DS_TDM-3-ASSERT_FAIL |
3-Error |
Slot [dec]: Assertion failed: file `[chars]' line [dec] |
An internal sanity check failed. |
- |
"" |
|
DS_TDM-3-BAD_CONN |
3-Error |
Slot [dec]: unrecognized TDM connect message received [dec] on |
An unrecognized TDM connect message was received. |
- |
"" |
|
DS_TDM-3-BAD_DISCONN |
3-Error |
Slot [dec]: unrecognized TDM disconnect message received [dec] on |
An unrecognized TDM disconnect message was received. |
- |
"" |
|
DS_TDM-3-BAD_DSIP |
3-Error |
Slot [dec]: unrecognized DSIP message received [dec] on [chars] feature board |
An unrecognized DSIP message was received. |
- |
"" |
|
DS_TDM-3-BAD_MAPPING |
3-Error |
Slot [dec]: Legacy FB [chars] with static port-to-DS0 mapping |
A software error lead to dynamic port-to-DS0 mapping info being passed to a statically-mapped FB. |
- |
"" |
|
DS_TDM-3-BAD_S4_POWER_UP |
3-Error |
Slot [dec]: [chars] powered-up with one or more incorrect default settings [chars] |
- |
- |
"" |
|
DS_TDM-3-CONV_CLOSE |
3-Error |
Slot [dec]: open MT8986 addr: 0x[hec] connection failed - STo[dec] CHo[dec] |
An attempt to disable a rate converted connection failed. |
- |
"" |
|
DS_TDM-3-CONV_OPEN |
3-Error |
Slot [dec]: open MT8986 addr: 0x[hec] [chars] connection failed - |
An attempt to establish a rate converted connection failed. |
- |
"" |
|
DS_TDM-3-DISC_FOR_NO_CONN |
3-Error |
Slot [dec]: got disc msg for non-existent conn: [chars]-st%02u-ts%03u/gts>%04u><%04u</[chars]-st%02u-ts%03u |
The FB was asked to disconnect a connection that it didn't know about. |
- |
"" |
|
DS_TDM-3-RECOMB_BUS_TS_BAD_USE |
3-Error |
Slot [dec]: convention broken for Mezz's Recomb. bus t'slots: [chars]-st%02u-ts%03u/gts>%04u><%04u</[chars]-st%02u-ts%03u |
- |
- |
"" |
|
DS_TDM-3-S4_INT |
3-Error |
Slot [dec]: [chars] generated interrupt [chars] |
Raiko-based FB's TDM Mezzanine card has no free Recombination bus DS0s. |
- |
"" |
|
DS_TDM-3-TDM_CLOSE |
3-Error |
Slot [dec]: close MT90820 addr: 0x[hec] connection failed - STo[dec] CHo[dec] |
An attempt to disable a digitally-switched connection failed. |
- |
"" |
|
DS_TDM-3-TDM_OPEN |
3-Error |
Slot [dec]: open MT90820 addr: 0x[hec] connection failed - |
An attempt to establish a digitally-switched connection failed. |
- |
"" |
|
DS_TDM-3-UNEXPECTED_INT |
3-Error |
Slot [dec]: got unexpected interrupt from masked-out source '[chars]' |
An interrupt was received from the specified source despite it being masked-out. |
- |
"" |
|
DS_TDM-3-UNSUPPORTED_MEZZ_VER |
3-Error |
Slot [dec]: the detected version [dec] of Mezzanine card is not |
The software does not support the Mezzanine card currently installed on the Raiko card. |
- |
"" |
|
DS_TDM-3-VERIFY_DISCONN |
3-Error |
Slot [dec]: [chars] failed to veryify disconnect: sto = [dec] ch_out = [dec] |
An attempt to verify a TDM hardware component failed. |
- |
"" |
|
DS_TDM-3-VERIFY_HILOWMEM |
3-Error |
Slot [dec]: [chars] failed to veryify himem or lowmem: sto = [dec] ch_out = [dec] sti = [dec] ch_in = [dec] |
An attempt to verify a TDM hardware component failed. |
- |
"" |
|
DS_TDM-3-VERIFY_IMS |
3-Error |
Slot [dec]: [chars] failed to veryify IMS: 0x[hec] |
An attempt to verify a TDM hardware component failed. |
- |
"" |
|
DS0_DUMP-3-INIT_FAIL |
3-Error |
DS0 PCM Tracer is not initialized. |
DS0 dump process can't be initialized. |
DS0_DUMP_DDTS_COMPONENT |
"Make sure there is enough memory in the system and IOS is properly " "installed." |
|
DS0_DUMP-3-MALLOC_PROC_MEM |
3-Error |
Process memory allocation failed for PCM capture: size 0x%08X. |
The free process memory in the system is not enough for the PCM capture session. |
DS0_DUMP_DDTS_COMPONENT |
"Refer to the user guide for the estimation of process memory needed " "for PCM capture. Do 'show memory' to make sure there is enough memory " "before PCM capture starts." |
|
DS0_DUMP-3-PCM_TRACE_NOT_SUPPORTED |
3-Error |
PCM Trace/ds0 dump is not supported on slot [dec]. |
Can't execute this command on the slot number specified. |
DS0_DUMP_DDTS_COMPONENT |
"Refer to the user guide for which slot ds0 dump is supported on." |
|
DS0_DUMP-3-PCM_TRACE_START_FAILED |
3-Error |
PCM capture start failed. |
Failed to start the ds0 dump in the TDM driver. |
DS0_DUMP_DDTS_COMPONENT |
"Make sure there is no hardware defect and there is no other " "ds0 dump/test tdm dump session going on." |
|
DS0_DUMP-3-PCM_TRACER_RUNNING |
3-Error |
A previous session of PCM capture is in progress. |
Can't start new PCM capture session since there is one going on now. |
DS0_DUMP_DDTS_COMPONENT |
"Make sure there is no other PCM capture session going on before " "start the new capture." |
|
DS0_DUMP-6-PCM_TRACE_RSP_ERROR |
6-Information |
module fail and terminate the pcm capture for [dec]/[dec]/[dec]/[dec] |
- |
- |
- |
|
DS0_DUMP-6-PCM_TRACE_RSP_STARTED |
6-Information |
module start PCM capture for [dec]/[dec]/[dec]/[dec] |
- |
- |
- |
|
DS0_DUMP-6-PCM_TRACE_RSP_STOPPED |
6-Information |
module stop or complete PCM capture for [dec]/[dec]/[dec]/[dec] |
- |
- |
- |
|
DS0_DUMP-6-PCM_TRACE_RSP_UNKNOWN |
6-Information |
module send unkonwn pcm capture response [dec] for [dec]/[dec]/[dec]/[dec] |
- |
- |
- |
|
DS0_DUMP-6-PCM_TRACE_STARTED |
6-Information |
PCM capture started. |
- |
- |
- |
|
DS0_DUMP-6-PCM_TRACE_STOP_FAILED |
6-Information |
failed to stop PCM capture |
- |
- |
- |
|
DS0_DUMP-6-PCM_TRACE_STOPPING |
6-Information |
stopping PCM capture |
- |
- |
- |
|
DS0_DUMP-6-PCM_TRACER_NOT_RUNNING |
6-Information |
no PCM capture is in progress. |
- |
- |
- |
|
DSA_PROXY-3-PROXY_CHUNK_CLEAR_FAILED |
3-Error |
- |
Chunk clear failed. |
cpp-ucode |
LOG_STD_ACTION |
|
DSA_PROXY-3-PROXY_CHUNK_CREATION_FAILED |
3-Error |
- |
Chunk creation failed. |
cpp-ucode |
LOG_STD_ACTION |
|
DSA_PROXY-3-PROXY_DEBUG_REG_FAILED |
3-Error |
- |
DSA Conditional Debugging registration failed. |
cpp-ucode |
LOG_STD_ACTION |
|
DSA_PROXY-3-PROXY_IP_CLEAR_FAILED |
3-Error |
[dec] |
IP Cache clear failed. |
cpp-ucode |
LOG_STD_ACTION |
|
DSA_PROXY-3-PROXY_IP_CLEAR_TO_FAILED |
3-Error |
[dec] [dec] |
IP Cache clear failed. |
cpp-ucode |
LOG_STD_ACTION |
|
DSA_PROXY-3-PROXY_IPC_ALLOC_FAILED |
3-Error |
- |
Generating IPC failed. |
cpp-ucode |
LOG_STD_ACTION |
|
DSA_PROXY-3-PROXY_IPC_INIT_FAILED |
3-Error |
[dec] |
IPC handler initialization failed. |
cpp-ucode |
LOG_STD_ACTION |
|
DSA_PROXY-3-PROXY_IPC_INVALID_PARAM |
3-Error |
- |
IPC Invalid parameters. |
cpp-ucode |
LOG_STD_ACTION |
|
DSA_PROXY-3-PROXY_IPC_SEND_CLEAR_FAILED |
3-Error |
[dec] |
DSA clear ip cache failed. |
cpp-ucode |
LOG_STD_ACTION |
|
DSA_PROXY-3-PROXY_IPC_SEND_INIT_FAILED |
3-Error |
[dec] |
Send initialization IPC failed. |
cpp-ucode |
LOG_STD_ACTION |
|
DSA_PROXY-3-PROXY_IPC_SEND_UNINIT_FAILED |
3-Error |
[dec] |
DSA Send UNINIT IPC failed. |
cpp-ucode |
LOG_STD_ACTION |
|
DSA_PROXY-3-PROXY_LOW_MEM_REQ_FAILED |
3-Error |
- |
Send low mem IPC failed. |
cpp-ucode |
LOG_STD_ACTION |
|
DSA_PROXY-3-PROXY_MEM_EXTEND_FAILED |
3-Error |
- |
Extending memory failed. |
cpp-ucode |
LOG_STD_ACTION |
|
DSA_PROXY-3-PROXY_NO_IP_POOL_MEM |
3-Error |
- |
IP Cache pool is not allocated. |
cpp-ucode |
LOG_STD_ACTION |
|
DSA_PROXY-3-PROXY_RETURN_MEM_FAILED |
3-Error |
- |
return mem IPC failed. |
cpp-ucode |
LOG_STD_ACTION |
|
DSA_PROXY-3-PROXY_TBL_INIT_FAILED |
3-Error |
- |
IP Cache table init failed. |
cpp-ucode |
LOG_STD_ACTION |
|
DSA_PROXY-3-PROXY_UNINIT_FAILED |
3-Error |
- |
UNINIT cleanup failed. |
cpp-ucode |
LOG_STD_ACTION |
|
DSA_PROXY-4-PROXY_IPC_INVALID_MSG |
4-Warning |
- |
Invalid IPC message |
cpp-ucode |
LOG_STD_ACTION |
|
DSA_PROXY-4-PROXY_IPC_INVALID_MSG_LEN |
4-Warning |
[dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Invalid IPC message length. |
cpp-ucode |
LOG_STD_ACTION |
|
DSC_REDUNDANCY-3-BAD_ASPECT |
3-Error |
illegal red. entity history aspect [dec] passed to [chars] |
- |
- |
"" |
|
DSC_REDUNDANCY-3-BAD_ROLE |
3-Error |
illegal red. entity role [dec] found in history queue by [chars] |
- |
- |
"" |
|
DSC_REDUNDANCY-3-BAD_STATE |
3-Error |
unexpected [chars] state in [chars] |
- |
- |
"" |
|
DSC_REDUNDANCY-3-BICLINK |
3-Error |
[chars] |
- |
- |
"" |
|
DSC_REDUNDANCY-3-DSIP_TX_ERR |
3-Error |
reliable IPC msg not tx'd by DSIP on [chars] |
- |
- |
"" |
|
DSC_REDUNDANCY-3-EVENT |
3-Error |
Redundancy event: [chars] |
- |
- |
"" |
|
DSC_REDUNDANCY-3-MODECONFLICT |
3-Error |
Other DSC/router in split mode |
There is another router connected to the dial shelf. In this situation\n\ both must be configured in split mode |
- |
"Configure the other router in split mode" |
|
DSC_REDUNDANCY-3-Q_EMPTY |
3-Error |
expected [dec] elements in queue but found none |
- |
- |
"" |
|
DSC_REDUNDANCY-3-SLOTCONFLICT |
3-Error |
Slot ownership conflict detected for slot [dec] |
There is another router connected to the dial shelf it is claiming\n\ ownership of a slot that this router is also claiming |
- |
"Fix the ownership conflict by reconfiguring one of the routers\n\ so that it doesn't own the slot" |
|
DSC_REDUNDANCY-3-STATUSCHANGE |
3-Error |
DSC in slot [dec] [chars] |
- |
- |
"" |
|
DSC_REDUNDANCY-3-TDMSPLITCONFLICT |
3-Error |
Tdm Split conflict detectedmy tdm [dec] other rs [dec] |
There is another router connected to the dial shelf it is claiming\n\ ownership of backplane timeslots that this router requires. This is probably due to\n\ OIR activity moving trunk cards from one half of the split to the other. |
- |
"Fix the ownership conflict by reloading the router whose tdm number\n\ is greater than the trunk capacity for that router. In some cases\n\ it may be necessary to reset both routers." |
|
DSCCLOCK-3-DUP_PRI |
3-Error |
Duplicate priority [dec] clock sources: slot [dec] port [dec] and slot [dec] port [dec]. |
- |
- |
LOG_STD_ACTION |
|
DSCCLOCK-3-FAIL |
3-Error |
The System Primary Clock is down. Moving to HOLDOVER state and waiting to see if it comes up |
This message is generated whenever the current primary clock \n\ goes bad. The TDM clock circuit goes into HOLDOVER mode and \n\ a holdover timer is started to see if the bad clock turns \n\ good within the holdover time. |
- |
LOG_STD_ACTION |
|
DSCCLOCK-3-NOMEMORY |
3-Error |
Failed to allocate memory for the DSC clocks |
The clock switching software has failed to allocate memory\n\ while adding a clock. |
- |
LOG_STD_ACTION |
|
DSCCLOCK-3-SWITCH_ERROR1 |
3-Error |
Failed to select any clock as the system clock. Remaining in HOLDOVER mode |
The clock selection algorithm has failed to select any clock as \n\ the TDM primary clock. |
- |
LOG_STD_ACTION |
|
DSCCLOCK-3-SWITCH2 |
3-Error |
Clock moving to FREERUN from HOLDOVER |
The current primary TDM clock has been deleted and hence the\n\ system primary has switched to the DSC local oscillator which\n\ is the current highest priority good clock. \n\ Phase continuity is maintained during the switchover. |
- |
LOG_STD_ACTION |
|
DSCCLOCK-3-SWITCH3 |
3-Error |
Clock moving to NORMAL from HOLDOVER selected clock is on slot [dec] port [dec] line [dec] |
The current primary TDM clock has been deleted and hence the\n\ system primary has switched to the clock coming in via the\n\ trunk specified by the slot/port which is the current \n\ highest priority good clock. Phase continuity is maintained \n\ during the switchover. |
- |
LOG_STD_ACTION |
|
DSCCLOCK-3-SWITCH4 |
3-Error |
Switching to the user configured clock on slot [dec] port [dec] line [dec] |
- |
- |
LOG_STD_ACTION |
|
DSCCLOCK-3-SWITCH5 |
3-Error |
Switching to the clock on slot [dec] port [dec] line [dec] |
The TDM primary clock is switching to the clock coming in via\n\ the trunk specified most likely after the router-shelf\n\ and hence feature boards reload. The phase of the output TDM \n\ clock is forced to align with the input reference during the \n\ switchover. |
- |
LOG_STD_ACTION |
|
DSCCLOCK-3-SWITCH6 |
3-Error |
Switching to the clock on slot [dec] port [dec] line [dec] as the current primary has gone bad |
The TDM primary clock has switched to a backup clock coming in \n\ via the specified trunk as the current primary clock has gone\n\ bad. |
- |
LOG_STD_ACTION |
|
DSCCLOCK-3-SWITCH7 |
3-Error |
Moving to NORMAL mode from HOLDOVER mode clock is slot [dec] port [dec] line [dec] |
The TDM primary clock which is in HOLDOVER mode and whose source \n\ was a trunk port has switched to the same trunk port and moved\n\ to NORMAL mode with a phase alignment between input \n\ source clock and output TDM reference clock. Most likely the \n\ router-shelf and hence the feature boards have reloaded. |
- |
LOG_STD_ACTION |
|
DSCCLOCK-3-SWITCH8 |
3-Error |
Moving to NORMAL mode from HOLDOVER mode without phase correction clock is slot [dec] port [dec] line [dec] |
The source trunk port of the TDM primary clock which had gone bad \n\ has turned good again before the holdover timer expiry. Hence the \n\ primary has moved from HOLDOVER to NORMAL state without phase \n\ correction between input trunk reference and the output TDM clock. |
- |
LOG_STD_ACTION |
|
DSCCLOCK-3-UP |
3-Error |
The System Primary Clock is up. Moving to NORMAL state from HOLDOVER |
The TDM primary clock which had gone bad has turned good within\n\ the holdover time. Hence the TDM primary clock switches to the \n\ NORMAL mode from the HOLDOVER mode. |
- |
LOG_STD_ACTION |
|
DSCCLOCK-5-SWITCH1 |
5-Notice |
Clock moving to NORMAL from FREERUN selected clock is on slot [dec] port [dec] line [dec] |
The primary TDM clock which has been running off the \n\ local oscillator of DSC in FREERUN mode has switched to the line \n\ clock coming in via the specified trunk. |
- |
LOG_STD_ACTION |
|
DSCEXTCLK-3-SWITCH3 |
3-Error |
Clock moving to NORMAL from HOLDOVER selected clock is external clock on DSC |
The current primary TDM clock has been deleted and hence the\n\ system primary has switched to the clock coming in via the\n\ external network reference clock on the DSC front panel which \n\ is the current highest priority good clock. Phase \n\ continuity is maintained during the switchover |
- |
LOG_STD_ACTION |
|
DSCEXTCLK-3-SWITCH4 |
3-Error |
Switching to the user configured external clock on DSC |
- |
- |
LOG_STD_ACTION |
|
DSCEXTCLK-3-SWITCH5 |
3-Error |
Switching to the external clock on DSC |
The TDM primary clock is switching to the clock coming in via\n\ the DSC front panel most likely after the router-shelf\n\ and hence feature boards reload. The phase of the output TDM \n\ clock is forced to align with the input reference during the\n\ switchover. |
- |
LOG_STD_ACTION |
|
DSCEXTCLK-3-SWITCH6 |
3-Error |
Switching to the external clock on DSC as the current primary has gone bad |
The TDM primary clock has switched to a backup clock coming in \n\ via the DSC front panel external clock feed as the current primary \n\ clock has gone bad. |
- |
LOG_STD_ACTION |
|
DSCEXTCLK-3-SWITCH7 |
3-Error |
Moving to NORMAL mode from HOLDOVER mode selected external clock on DSC |
The TDM primary clock which is in HOLDOVER mode and whose source \n\ was a the DSC front panel clock has switched to the same clock \n\ and moved to the NORMAL mode. |
- |
LOG_STD_ACTION |
|
DSCEXTCLK-3-SWITCH8 |
3-Error |
Moving to NORMAL mode from HOLDOVER mode without phase correction selected external clock on DSC |
The DSC front panel clock which is the source of the current TDM \n\ primary clock and which had gone bad has turned good again before \n\ the holdover timer expiry. Hence the primary has moved from HOLDOVER \n\ to NORMAL state without phase correction between input reference and \n\ the output TDM clock. |
- |
LOG_STD_ACTION |
|
DSCEXTCLK-5-SWITCH1 |
5-Notice |
Clock moving to NORMAL from FREERUN selected clock is external clock on DSC |
The primary TDM clock which has been running off the \n\ local oscillator of DSC in FREERUN mode has switched to the \n\ external network reference clock being fed from the DSC front\n\ panel. |
- |
LOG_STD_ACTION |
|
DSCREDCLK-2-BACTFAIL |
2-Critical |
Clock on other DSC has failed - immediate clock takeover |
The backup DSC clock has detected failure on the other DSC clock \ hardware \ and is taking over to become the active clock manager. |
- |
LOG_STD_ACTION |
|
DSCREDCLK-2-BACTGONE |
2-Critical |
Removal of other DSC detected - immediate clock takeover |
The backup DSC clock has detected removal of the other DSC \ |
- |
"Reinstall a DSC in other DSC slot to provide DSC." |
|
DSCREDCLK-2-BCLKCMDFAIL |
2-Critical |
Clock command hardware failed |
The |
- |
LOG_STD_ACTION |
|
DSCREDCLK-3-BACTIOSF |
3-Error |
Other DSC IOS keepalive failure - clock takeover |
The other DSC has failed to respond to keepalives to the current \ DSC and so the current DSC is taking over to become the active \ clock manager. |
- |
"Recover DSC in other DSC slot to provide backup DSC." |
|
DSCREDCLK-3-BTAKEDELAY |
3-Error |
Active DSC requests backup to takeover clock - delaying for sync |
The other DSC has requested the current DSC to take over active \ clock management \ but the current DSC is waiting for clock hardware synchronization \ before doing so to avoid call loss. |
- |
LOG_STD_NO_ACTION |
|
DSCREDCLK-3-BTAKEOVER |
3-Error |
Active DSC requests backup to takeover clock - done |
- |
- |
"" |
|
DSCREDCLK-5-BNORMAL |
5-Notice |
Backup clock moving to NORMAL to phase lock to active clock |
The backup DSC has detected a change to the clock |
- |
LOG_STD_NO_ACTION |
|
DSCREDCLK-5-BSWITCHE |
5-Notice |
Backup clock matched to active clock reference external clock on DSC |
The backup DSC has detected a change in the selected clock reference \ on the active DSC and has changed it's own clock hardware to match \ the new selection. \ The selected clock reference is now from the DSC front panel external \ clock feed. |
- |
LOG_STD_NO_ACTION |
|
DSCREDCLK-5-BSWITCHT |
5-Notice |
Backup clock matched to active clock reference slot [dec] line [dec] |
The backup DSC has detected a change in the selected clock reference \ on the active DSC and has changed it's own clock hardware to match \ the new selection. \ The selected clock reference is now from the specified trunk line. |
- |
LOG_STD_NO_ACTION |
|
DSG-3-DSG_DA_TO_DSID_DUPLICATED |
3-Error |
DA [enet] to DSID table duplicated when operation [chars] DSID %X on |
DSG DA_TO_DSID table in LC should be unique for DA on a interface. |
cmts-application |
"Issue the show tech-support command to gather data " "that may help identify the nature of the error.\n" "Then reconfigure DSG in the mac domain to refresh " "all DSG configurations in the interface." |
|
DSG-3-DSG_DCD_UPDATE_FAILURE |
3-Error |
Faild to DCD message on [chars] |
DSG DCD update failure |
cmts-application |
"Check if DSG traffic is blocked on the " "influenced mac domain.\n" "If so contact your Cisco technical support representative for help." |
|
DSG-3-DSG_DEL_DSID_FAILURE |
3-Error |
dsg delete dsid failure [[chars]: [chars] [chars] [enet]] |
dsg delete dsid failure |
cmts-application |
LOG_STD_DDTS_TAC_DETAILS |
|
DSG-3-DSG_DIFFERENT_DSG_DSID |
3-Error |
different dsid [dec] assign to dsg da2dsid entry [dec] |
DSG DSID Allocate Err |
cmts-application |
LOG_STD_DDTS_TAC_DETAILS |
|
DSG-3-DSG_ZERO_DSG_DSID |
3-Error |
zero dsid found in dsg da2dsid entry for [[chars] [chars] [enet]] |
Zero DSG DSID Found |
cmts-application |
LOG_STD_DDTS_TAC_DETAILS |
|
DSG-5-CFR_CONFLICT |
5-Notice |
classifier <[chars]> is put into conflict state because of errors |
classifier is already applied but we cannot update the classifier with changed destination IP address or source IP address because of errors. So we put the classifier into conflict state. |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-CFR_CONFLICT |
5-Notice |
classifier <[chars]> is put into conflict state because of errors |
classifier is already applied but we cannot update the classifier with changed destination IP address or source IP address because of errors. So we put the classifier into conflict state. |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-CFR_NOT_APPLIED |
5-Notice |
classifier <[chars]> cannot be applied because of errors |
classifier cannot be applied because of errors. |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-CFR_NOT_APPLIED |
5-Notice |
classifier <[chars]> cannot be applied because of errors |
classifier cannot be applied because of errors. |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-CFRRMTUNNEL |
5-Notice |
cfr [dec] becomes unresolved it will be removed from the tunnel it belongs to |
cfr becomes unresolved it will be removed from the tunnel it belongs to |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-CFRRMTUNNEL |
5-Notice |
cfr [dec] becomes unresolved it will be removed from the tunnel it belongs to |
cfr becomes unresolved it will be removed from the tunnel it belongs to |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-DSG_INFO_DB_LOOKUP_FAILURE |
5-Notice |
Faild to find the entry from the DSG Info DB for [chars] [chars] [chars] |
DSG Info DB lookup failure |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-DSG_INFO_DB_LOOKUP_FAILURE |
5-Notice |
Faild to find the entry from the DSG Info DB for [chars] [chars] [chars] |
DSG Info DB lookup failure |
cmts-application |
LOG_STD_DDTS_TAC_DETAILS |
|
DSG-5-IDENTICAL_CFR |
5-Notice |
cfr [dec] and [dec] are identical |
two cfrs are identical |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-IDENTICAL_CFR |
5-Notice |
cfr [dec] and [dec] are identical |
two cfrs are identical |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-ILLEGAL_MCASTADDR |
5-Notice |
IP address <[inet]> is not a multicast address or is a reserved multicast address |
IP address is not an multicast address or is a reserved multicast address |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-ILLEGAL_MCASTADDR |
5-Notice |
IP address <[inet]> is not a multicast address or is a reserved multicast address |
IP address is not an multicast address or is a reserved multicast address |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-ILLEGAL_SOURCEADDR |
5-Notice |
IP address <[inet]> is an illegal source address |
IP address is an illegal source address |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-ILLEGAL_SOURCEADDR |
5-Notice |
IP address <[inet]> is an illegal source address |
IP address is an illegal source address |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-MAC_ADDR |
5-Notice |
cfr [dec] and cfr [dec] have the same destination IP address [inet] but different MAC addresses [enet] and [enet] |
two cfrs have the same destination IP address but different MAC addresses |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-MAC_ADDR |
5-Notice |
cfr [dec] and cfr [dec] have the same destination IP address [inet] but different MAC addresses [enet] and [enet] |
two cfrs have the same destination IP address but different MAC addresses |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-NAME_CHANGED |
5-Notice |
hostname <[chars]> is changed from <[inet]> to <[inet]> |
IP address of a hostname is changed. |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-NAME_CHANGED |
5-Notice |
hostname <[chars]> is changed from <[inet]> to <[inet]> |
IP address of a hostname is changed. |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-NAME_UNRESOLVED |
5-Notice |
hostname <[chars]> cannot be resolved |
DNS query for a hostname is not successful. |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-NAME_UNRESOLVED |
5-Notice |
hostname <[chars]> cannot be resolved |
DNS query for a hostname is not successful. |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-SEMAPHORE_ERROR |
5-Notice |
failed to obtain the DSG semaphore |
failed to get the semaphore |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-SEMAPHORE_ERROR |
5-Notice |
failed to obtain the DSG semaphore |
failed to get the semaphore |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-SOURCE_LEN |
5-Notice |
cfr [dec]: source IP address [inet] and source prefix length [dec] don't match |
source IP address and source prefix length of the cfr don't match |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-SOURCE_LEN |
5-Notice |
cfr [dec]: source IP address [inet] and source prefix length [dec] don't match |
source IP address and source prefix length of the cfr don't match |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-SSM_SOURCE_PREFIX |
5-Notice |
destination IP address is <[inet]> in SSM range source IP address prefix length must be [dec] |
dest-ip is in SSM range src-ip prefix length should match |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-SSM_SOURCE_PREFIX |
5-Notice |
destination IP address is <[inet]> in SSM range source IP address prefix length must be [dec] |
dest-ip is in SSM range src-ip prefix length should match |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-SSM_SOURCE_ZERO |
5-Notice |
destination IP address is <[inet]> in SSM range source IP address cannot be zero |
dest-ip is in SSM range src-ip cannot be zero |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-SSM_SOURCE_ZERO |
5-Notice |
destination IP address is <[inet]> in SSM range source IP address cannot be zero |
dest-ip is in SSM range src-ip cannot be zero |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-STATICJOINERR |
5-Notice |
cfr [dec] cannot be enabled because there already exists a non-DSG static join for S [inet] or * [inet] in interface [chars] |
cfr cannot be enabled because there already exists a non-DSG static join for the multicast group |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-5-STATICJOINERR |
5-Notice |
cfr [dec] cannot be enabled because there already has been a non-DSG static join for S [inet] or * [inet] in interface [chars] |
cfr cannot be enabled because there already exists a non-DSG static join for the multicast group |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-6-CFR_APPLIED |
6-Information |
classifier <[chars]> is applied successfully |
classifier is applied successfully. |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-6-CFR_APPLIED |
6-Information |
classifier <[chars]> is applied successfully |
classifier is applied successfully. |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-6-CFR_UPDATED |
6-Information |
classifier <[chars]> is updated |
classifier is updated |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-6-CFR_UPDATED |
6-Information |
classifier <[chars]> is updated |
classifier is updated |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-6-LIST_ERR |
6-Information |
[chars] [dec] |
Infomational only |
ubr7200 |
LOG_STD_NO_ACTION |
|
DSG-6-LIST_ERR |
6-Information |
[chars] [dec] |
Infomational only |
ubr7200 |
LOG_STD_NO_ACTION |
|
DSG-6-NAME_RESOLVED |
6-Information |
hostname <[chars]> is resolved as <[inet]> |
DNS query for a hostname is successful. |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-6-NAME_RESOLVED |
6-Information |
hostname <[chars]> is resolved as <[inet]> |
DNS query for a hostname is successful. |
cmts-application |
LOG_STD_NO_ACTION |
|
DSG-6-NO_TG |
6-Information |
tg <[dec]> removal will remove all tg \conf on bundle and mac-domain. |
remove global tg is successful. |
cmts-application |
LOG_STD_NO_ACTION |
|
DSIP-3-CLIENT_ADD_FAIL |
3-Error |
Adding client [dec] after DSIP has started. |
- |
- |
"" |
|
DSIP-3-CLIENT_VERSION_MISMATCH |
3-Error |
Some clients on this feature board are running versions which are incompatible with RS. Not initializing any DSIP clients. You can find the incompatible clients by executing the show dsip version command |
- |
- |
"" |
|
DSIP-3-CLIVERSDBASE_MALLOC_FAILURE |
3-Error |
Failed to get memory for the DSIP clicnets version database |
\n\ |
- |
"" |
|
DSIP-3-GET_INTRAPI_BUF_FAILURE |
3-Error |
Failed to get interrupt api buffers |
\n\ |
- |
"" |
|
DSIP-3-GET_VERSBUF_FAILURE |
3-Error |
Failed to get version buffers |
\n\ |
- |
"" |
|
DSIP-3-GETPAK |
3-Error |
Failed to get packet buffer |
\n\ |
- |
"" |
|
DSIP-3-INCOMPATIBLE_CLIENT |
3-Error |
Incompatible client [chars] on DS slot [dec] with major version [dec] and minor version [dec]. Shutting down all the DSIP clients on this slot |
- |
- |
"" |
|
DSIP-3-INTRAPI_BUF_MALLOC_FAILURE |
3-Error |
Failed to get memory for the DSIP interrupt api buffers |
\n\ |
- |
"" |
|
DSIP-3-IPC_CLIENT |
3-Error |
IPC subsystem API error[chars] [chars] [dec] |
- |
- |
"" |
|
DSIP-3-IPC_PORT |
3-Error |
IPC subsystem API error[chars] [chars] [chars] |
- |
- |
"" |
|
DSIP-3-IPC_SEAT |
3-Error |
IPC subsystem API error can not create seat by \n\ the seatid [dec] for the slot [dec] |
Nitro Interconnect Protocol reliable stack \n\ has failed to create seat for the specified slot. |
- |
"" |
|
DSIP-3-NO_MAJOR_VERSION |
3-Error |
Client addition to DSIP has failed [chars] [dec] |
- |
- |
"" |
|
DSIP-3-PRIVPOOL |
3-Error |
Failed to create DSIP private buffer pool |
\n\ |
- |
"" |
|
DSIP-3-RANGE |
3-Error |
DSIP parameter range error [chars] [dec] |
- |
- |
"" |
|
DSIP-3-TXCONTEXT |
3-Error |
[chars] slot [dec] client [dec] |
\n\ |
- |
"" |
|
DSIP-3-TXCONTEXT_ACTIVE_USE |
3-Error |
Waiting for the active transmit contexts to become inactive |
\n\ |
- |
"" |
|
DSIP-3-VERSBUF_MALLOC_FAILURE |
3-Error |
Failed to get memory for the DSIP version buffers |
\n\ |
- |
"" |
|
DSIP-3-VERSDBASE_MALLOC_FAILURE |
3-Error |
Failed to get memory for the DSIP version database |
\n\ |
- |
"" |
|
DSIPPF-3-BASE_FTBL_MALLOC_FAIL |
3-Error |
Failed to allocate memory for the base fucntion table |
- |
- |
"" |
|
DSIPPF-3-DSIP_SEND_FAILURE |
3-Error |
Failed to send DSIP message - number of failures [dec] |
This message indicates that Nitro Interconnect Protocol\n\ has encountered an error while sending a message and that the\n\ message has been discarded after three unsuccessful resends. |
- |
"" |
|
DSIPPF-5-DS_HELLO |
5-Notice |
DSIP Hello from shelf [dec] slot [dec] Succeeded |
- |
- |
"" |
|
DSIPPF-5-DS_KEEPALIVE_LOSS |
5-Notice |
DSIP Keepalive Loss from shelf [dec] slot [dec] |
- |
- |
"" |
|
DSIPPF-5-HELLO_ERROR |
5-Notice |
DSIP Hello from shelf [dec] slot [dec] failed due to DSIP version mismatch |
- |
- |
"" |
|
DSIPPF-5-RS_HELLO |
5-Notice |
DSIP Hello from router shelf [dec] Succeeded |
- |
- |
"" |
|
DSIPPF-5-RS_KEEPALIVE_LOSS |
5-Notice |
DSIP Keepalive Loss from router shelf [dec] |
- |
- |
"" |
|
DSM-3-DSP_TIMEOUT |
3-Error |
DSP timeout on channel [chars] event 0x[hec]: DSP ID=0x[hec]: [chars] |
Timeout on DSP response. |
ios-voice |
"The DSP has been automatically reset. If problem persists contact" "your technical support representative" |
|
DSM-3-DSPALARM |
3-Error |
channel [chars] DSP ID 0x[hec]: status=0x[hec] message=0x[hec] text=[chars] |
The DSP reported a fatal error. All sessions on the DSP were dropped and a DSP reload was attempted. |
ios-voice |
"Contact your technical support\n\ representative include the full text of the error message." |
|
DSM-3-INTERNAL |
3-Error |
Internal Error : [chars] |
DSM Internal error |
ios-voice |
"Contact your technical support representative" |
|
DSM-3-MSGSNDFAIL |
3-Error |
channel:[chars] DSP ID:0x[hec] Message ID:0x[hec] |
A message could not be sent to the DSP. The session continued but may have experienced problems. |
ios-voice |
"Contact your technical " "support representative include the full text of the error message." |
|
DSM-3-NOEVENT |
3-Error |
no free event structure available from [chars] for DSM message |
There were no event structures remaining in the system pools to alert the router of a voice or signaling event. |
ios-voice |
"Contact your technical support " "representative include the full text of the error message." |
|
DSM-6-SESSION_DATABASE_FAILED |
6-Information |
Cannot create DSM session database\n |
Failed to create DSM session. |
ios-voice |
"Check the size of free memory to make sure there is enough memory." |
|
DSMIB-3-CLIENT_TYPE |
3-Error |
Type [dec] is invalid for collision [chars] |
The specified type of client is an invalid value which indicates that there is no support for the generation of an internal identifier. This is an internal software error. |
dsmib |
"LOG_STD_ACTION" |
|
DSMIB-3-CLIENT_TYPE |
3-Error |
Type [dec] is invalid for collision [chars] |
The specified type of client is an invalid value which indicates that there is no support for the generation of an internal identifier. This is an internal software error. |
dsmib |
LOG_STD_ACTION |
|
DSMIB-3-RECV_CONF |
3-Error |
Error receiving configuration in DSMIB. |
The configuration is not received properly from shim. This indicates that the operation to receive the configurations from shim has failed. This condition will result in out-of-sync information in dsmib with respect to shim. |
dsmib |
"LOG_STD_ACTION" |
|
DSMIB-3-RECV_CONF |
3-Error |
Error receiving configuration in DSMIB. |
The configuration is not received properly from shim. This indicates that the operation to receive the configurations from shim has failed. This condition will result in out-of-sync information in dsmib with respect to shim. |
dsmib |
LOG_STD_ACTION |
|
DSMIB-3-RECV_STAT |
3-Error |
Error in decoding statistics in DSMIB. |
The counters are not received properly from shim. This indicates that the operation to receive the statistics from shim has failed. This condition will result in counters out-of-sync between MQC and dsmib. |
dsmib |
"LOG_STD_ACTION" |
|
DSMIB-3-RECV_STAT |
3-Error |
Error in decoding statistics in DSMIB. |
The counters are not received properly from shim. This indicates that the operation to receive the statistics from shim has failed. This condition will result in counters out-of-sync between MQC and dsmib. |
dsmib |
LOG_STD_ACTION |
|
DSMIB-3-TIMER_START |
3-Error |
[chars] |
This indicates that the operation to start/restart a timer has failed. This condition will result in counters out-of-sync between MQC and dsmib. |
dsmib |
"LOG_STD_ACTION" |
|
DSMIB-3-TIMER_START |
3-Error |
[chars] |
This indicates that the operation to start/restart a timer has failed. This condition will result in counters out-of-sync between MQC and dsmib. |
dsmib |
LOG_STD_ACTION |
|
DSMIB-3-UID_DELETE |
3-Error |
[chars] unable to remove index %08X |
The specified entity is unable to removed the specified index. This is an internal software error. |
dsmib |
"LOG_STD_ACTION" |
|
DSMIB-3-UID_DELETE |
3-Error |
[chars] unable to remove index %08X |
The specified entity is unable to removed the specified index. This is an internal software error. |
dsmib |
LOG_STD_ACTION |
|
DSMIB-3-UID_EXISTS |
3-Error |
[chars] attempt to add index %08X [chars] |
The specified entity is unable to add an entry due to the detection of an existing entry with the same index or name. This is an internal software error. |
dsmib |
"LOG_STD_SH_CMD_ACTIONshow dsmib db id" |
|
DSMIB-3-UID_EXISTS |
3-Error |
[chars] attempt to add index %08X [chars] |
The specified entity is unable to add an entry due to the detection of an existing entry with the same index or name. This is an internal software error. |
dsmib |
"show dsmib db id" |
|
DSMIB-3-WRED_PARENT |
3-Error |
There is a child policy under class [chars] in policy-map [chars] where random-detect is configured which is not supported while diffservmib RFC 2475 is enabled |
Random-detect is not supported in parent class of a HQOS policy when diffservmib RFC 2475 is enabled |
dsmib |
"LOG_STD_ACTION" |
|
DSMIB-3-WRED_PARENT |
3-Error |
There is a child policy under class [chars] in policy-map [chars] where random-detect is configured which is not supported while diffservmib RFC 2475 is enabled |
Random-detect is not supported in parent class of a HQOS policy when diffservmib RFC 2475 is enabled |
dsmib |
LOG_STD_ACTION |
|
DSMIB-3-XMIT_CONF |
3-Error |
[chars] |
The configuration is not transmitted properly from shim. This indicates that the operation to transmit the configurations from shim has failed. This condition will result in out-of-sync information in dsmib with respect to shim. |
dsmib |
LOG_STD_ACTION |
|
DSMIB-3-XMIT_MSG |
3-Error |
[chars] |
The IPC message was not transmitted. This condition will result in counters out-of-sync between MQC and dsmib or some config being out of sync. |
dsmib |
"LOG_STD_ACTION" |
|
DSMIB-3-XMIT_MSG |
3-Error |
[chars] |
The IPC message was not transmitted. This condition will result in counters out-of-sync between MQC and dsmib or some config being out of sync. |
dsmib |
LOG_STD_ACTION |
|
DSMIB-3-XMIT_STAT |
3-Error |
Error in statistics query and encoding in DSMIB. |
The counters are not encoded and transmitted properly from shim. This indicates that the operation to encode the statistics from shim has failed. This condition will result in counters out-of-sync between MQC and dsmib. |
dsmib |
"LOG_STD_ACTION" |
|
DSMIB-3-XMIT_STAT |
3-Error |
Error in statistics query and encoding in DSMIB. |
The counters are not encoded and transmitted properly from shim. This indicates that the operation to encode the statistics from shim has failed. This condition will result in counters out-of-sync between MQC and dsmib. |
dsmib |
LOG_STD_ACTION |
|
DSMIBPROV-3-CLASSNOTFOUND |
3-Error |
class: [chars] is not present in db. |
This is a configuration error for dsmib.It indicates that dsmib shim does not get the notification when the classmap is configured on the box through MQC. This also potentially means the dsmib db will be out-of-sync with respect to MQC configurations.Capture the log in the console with class name for any possible debugging. |
dsmib |
"LOG_STD_ACTION" |
|
DSMIBPROV-3-CLASSNOTFOUND |
3-Error |
class: [chars] is not present in db. |
This is a configuration error for dsmib. It indicates that dsmib shim does not get the notification when the classmap is configured on the box through MQC. This also potentially means the dsmib db will be out-of-sync with respect to MQC configurations. Capture the log in the console with class name for any possible debugging. |
dsmib |
LOG_STD_ACTION |
|
DSMIBPROV-3-POLICYNOTFOUND |
3-Error |
policy: [chars] is not present in db. |
This is a configuration error for dsmib.It indicates that dsmib shim does not get the notification when the policymap is configured on the box through MQC. This also potentially means the dsmib db will be out-of-sync with respect to MQC configurations.Capture the log in the console with policy name for any possible debugging. |
dsmib |
"LOG_STD_ACTION" |
|
DSMIBPROV-3-POLICYNOTFOUND |
3-Error |
policy: [chars] is not present in db. |
This is a configuration error for dsmib. It indicates that dsmib shim does not get the notification when the policymap is configured on the box through MQC. This also potentially means the dsmib db will be out-of-sync with respect to MQC configurations. Capture the log in the console with policy name for any possible debugging. |
dsmib |
LOG_STD_ACTION |
|
DSMIBPROV-3-XMIT_CONF |
3-Error |
[chars] |
The configuration is not transmitted properly from shim. This indicates that the operation to transmit the configurations from shim has failed. This condition will result in out-of-sync information in dsmib with respect to shim. |
dsmib |
"LOG_STD_ACTION" |
|
DSMIBPROV-6-UNSUPPORTED |
6-Information |
[chars] |
This is a provisioning error for dsmib. It indicates that dsmib does not support the configuration entered. See the error message printed out on the console for possible supported configurations.Then try with different configurations valid for dsmib. |
dsmib |
"LOG_STD_NO_ACTION" |
|
DSMIBPROV-6-UNSUPPORTED |
6-Information |
[chars] |
This is a provisioning error for dsmib. It indicates that dsmib does not support the configuration entered. See the error message printed out on the console for possible supported configurations. Then try with different configurations valid for dsmib. |
- |
LOG_STD_NO_ACTION |
|
DSMP-3-DSP_TIMEOUT |
3-Error |
DSP timeout on DSP [chars]: event 0x[hec] [chars] |
Timeout on DSP response. |
ios-voice |
"The DSP has been automatically reset. If problem persists contact" "your technical support representative" |
|
DSMP-3-DSPALARM |
3-Error |
Alarm on DSP [chars]: status=0x[hec] message=0x[hec] text=[chars] |
The DSP reported a fatal error. All sessions on the DSP were dropped and a DSP reload was attempted. |
ios-voice |
"Contact your technical support\n\ representative include the full text of the error message." |
|
DSMP-3-INTERNAL |
3-Error |
Internal Error : [chars] |
DSMP Internal error |
ios-voice |
"Contact your technical support representative" |
|
DSMP-3-INVALID_EVENT |
3-Error |
Unhandled event: current state:[chars] event:[chars] |
The event is not handled in the DSMP gateway state machine specification |
ios-voice |
"Contact your technical support representative" |
|
DSMP-3-MSGSNDFAIL |
3-Error |
channel:[chars] DSP ID:0x[hec] Message ID:0x[hec] |
A message could not be sent to the DSP. The session continued but may have experienced problems. |
ios-voice |
"Contact your technical support \n\ representative include the full text of the error message." |
|
DSMP-3-NOEVENT |
3-Error |
no free event structure available from [chars] for DSMP message |
There were no event structures remaining in the system pools to alert the router of a voice or signaling event. |
ios-voice |
"Contact your technical support " "representative include the full text of the error message." |
|
DSMP-3-NOLICENSE |
3-Error |
[chars]:No License available Tivan Recording could not be Triggered |
There are no recording license remaining in the license pool |
ios-voice |
" Check your configuration for smart license availability" |
|
DSMP-3-PRG_ERROR |
3-Error |
Programming Error : [chars] |
Progaramming error in DSMP subsys |
ios-voice |
"Contact your technical support representative" |
|
DSMP-3-SUBSYS_UNINITIALIZED |
3-Error |
Internal Error : [chars] |
DSMP Subsystem not initialized |
ios-voice |
"Contact your technical support representative" |
|
DSMP-4-WARNING |
4-Warning |
Warning : [chars] |
Resource temporarily not available |
ios-voice |
"Contact your technical support representative if condition lasts" |
|
DSMP-6-SESSION_DATABASE_FAILED |
6-Information |
Cannot create DSMP session database\n |
Failed to create DSMP session. |
ios-voice |
"Check the size of free memory to make sure there is enough memory." |
|
DSP_SPA-2-INITFAIL |
2-Critical |
Not Enough Resources:[chars] |
The shared port adaptor failed to complete software initialization. |
SPA-DSP |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
DSP_SPA-3-BUFF_FAIL |
3-Error |
Not Enough MEM Buffers [chars] |
Not enought memory buffers for shared port adaptor operation. |
SPA-DSP |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
DSP_SPA-3-FILE_OP_FAIL |
3-Error |
Failed to open file [chars] : [chars] |
Failed to open file |
SPA-DSP |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
DSP_SPA-3-FILE_RD_FAIL |
3-Error |
Failed to read [dec] bytes from file: [chars] |
Failed to read data from file |
SPA-DSP |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
DSP_SPA-3-HW_ERROR |
3-Error |
[chars]: A Hardware device error was detected. Trying to recover the SPA by reload. Error information : [chars] |
An internal hardware device error has occurred on the services SPA. The error message indicates the slot subslot the SPA type and the name of the hardware device. The SPA has been deactivated and reactivated to resolve the problem. If the error occurs more than five times within an hour no further attempts to reactivate the SPA will be made. This message is likely due to an unrecoverable hardware failure. |
spa-dsp |
"Perform OIR of the SPA located in the specified subslot. Before removing " "the SPA enter the <CmdBold>hw-module subslot stop<NoCmdBold> command. " "Remove the SPA wait 5 seconds and reinsert the SPA. If " "the problem persists copy the error message text exactly as it appears " "on the console or in the system log enter the <CmdBold>show diag" "<NoCmdBold> command contact your Cisco technical support representative " "and provide the representative with the gathered information." |
|
DSP_SPA-3-HW_ERROR_INFO |
3-Error |
[chars]: Non fatal hardware device error was detected. Error information : [chars] |
An internal hardware device error has occurred on the services SPA. The error message indicates the slot subslot the SPA type and the name of the hardware device. This message is likely due to a recoverable hardware failure. |
spa-dsp |
"Perform OIR of the SPA located in the specified subslot. Before removing " "the SPA enter the <CmdBold>hw-module subslot stop<NoCmdBold> command. " "Remove the SPA wait 5 seconds and reinsert the SPA. If " "the problem persists copy the error message text exactly as it appears " "on the console or in the system log enter the <CmdBold>show diag" "<NoCmdBold> command contact your Cisco technical support representative " "and provide the representative with the gathered information." |
|
DSP_SPA-3-NULL_FAIL |
3-Error |
Non-Initialized ptr: [chars] |
About to Access non-initialized pointer |
SPA-DSP |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
DSP-3-DSP_ALARM |
3-Error |
DSP device [dec] is not responding. Trying to recover DSP device by reloading |
A DSP device on DSP-SPA is not responding. The error message indicates the slot subslot the SPA type and the name of the hardware device. |
spa-dsp |
"Software will try to recover by reloading the failed DSP. " "If the problem persists then perform OIR of the SPA located in the " "specified subslot. Before removing the SPA enter " "the <CmdBold>hw-module subslot stop<NoCmdBold> command. Remove the SPA " "wait 5 seconds and reinsert the SPA. If the problem persists copy " "the error message text exactly as it appears on the console or in the " "system log enter the <CmdBold>show diag <NoCmdBold> command contact " "your Cisco technical support representative and provide the " "representative with the gathered information." |
|
DSP-3-DSP_DNLD |
3-Error |
DSP device [dec] DNLD process exited. Trying to recover DSP device by rebooting the DSP |
A DSP device on DSP-SPA is not responding. The error message indicates the slot subslot the SPA type and the name of the hardware device. |
spa-dsp |
"Software will try to recover by reloading the failed DSP. " "If the problem persists then perform OIR of the SPA located in the " "specified subslot. Before removing the SPA enter " "the <CmdBold>hw-module subslot stop<NoCmdBold> command. Remove the SPA " "wait 5 seconds and reinsert the SPA. If the problem persists copy " "the error message text exactly as it appears on the console or in the " "system log enter the <CmdBold>show diag <NoCmdBold> command contact " "your Cisco technical support representative and provide the " "representative with the gathered information." |
|
DSP-3-DSP_KEEPALIVE |
3-Error |
DSP device [dec] is not responding. Trying to recover DSP device by reloading |
A DSP device on DSP-SPA is not responding. The error message indicates the slot subslot the SPA type and the name of the hardware device. |
spa-dsp |
"Software will try to recover by reloading the failed DSP. " "If the problem persists then perform OIR of the SPA located in the " "specified subslot. Before removing the SPA enter " "the <CmdBold>hw-module subslot stop<NoCmdBold> command. Remove the SPA " "wait 5 seconds and reinsert the SPA. If the problem persists copy " "the error message text exactly as it appears on the console or in the " "system log enter the <CmdBold>show diag <NoCmdBold> command contact " "your Cisco technical support representative and provide the " "representative with the gathered information." |
|
DSP-3-DSP_WATCHDOG |
3-Error |
DSP device [dec] is not responding. Trying to recover DSP device by reloading |
A DSP device on DSP-SPA is not responding. The error message indicates the slot subslot the SPA type and the name of the hardware device. |
spa-dsp |
"Software will try to recover by reloading the failed DSP. " "If the problem persists then perform OIR of the SPA located in the " "specified subslot. Before removing the SPA enter " "the <CmdBold>hw-module subslot stop<NoCmdBold> command. Remove the SPA " "wait 5 seconds and reinsert the SPA. If the problem persists copy " "the error message text exactly as it appears on the console or in the " "system log enter the <CmdBold>show diag <NoCmdBold> command contact " "your Cisco technical support representative and provide the " "representative with the gathered information." |
|
DSP-3-FIRMWARE_VER_INFO |
3-Error |
Downloading streamware... for device [dec]. DSP firmwarever:[dec].[dec] contained in image has different version from |
DSP firmware version check |
- |
LOG_STD_NO_ACTION |
|
DSP-3-TIMER |
3-Error |
[chars] timer expired for DSP [dec] |
DSP timer has expired |
- |
LOG_STD_NO_ACTION |
|
DSP-5-DNLD |
5-Notice |
DNLD started for device [dec] |
DSP bootloader DNLD starte |
- |
LOG_STD_NO_ACTION |
|
DSP-5-UPDOWN |
5-Notice |
DSP [dec] is [chars] |
DSP device changed state up/down |
- |
LOG_STD_NO_ACTION |
|
DSPDUMP-5-DUMPSTART |
5-Notice |
DSP [dec] 0x[hec] in slot [dec] starting dump |
The DSP resource is beginning crash dump collection |
- |
LOG_STD_NO_ACTION |
|
DSPDUMP-5-RX_CONTROL_DROP |
5-Notice |
DSP [dec] in slot [dec] Rx Control Message Dropped by DSP |
The DSP has reported that a Rx Control Message was dropped |
- |
LOG_STD_NO_ACTION |
|
DSPDUMP-5-TX_CONTROL_DROP |
5-Notice |
DSP [dec] in slot [dec] Tx Control Message Dropped by DSP |
The DSP has reported that a Tx Control Message was dropped |
- |
LOG_STD_NO_ACTION |
|
DSPFARM-3-ERROR |
3-Error |
[chars] |
Error on DSPFARM module. |
- |
LOG_STD_SH_TECH_ACTION |
|
DSPFARM-3-ERROR |
3-Error |
Errors on DSPFARM module [chars]\n |
Errors on DSPFARM module |
dspfarm |
" Check sh dspfarm all" |
|
DSPFARM-4-INFO |
4-Warning |
Info on DSPFARM module [chars]\n |
Info on DSPFARM module |
dspfarm |
" Check sh dspfarm" |
|
DSPFARM-4-NOTICE |
4-Warning |
Failure on DSPFARM module [chars]\n |
Failure on DSPFARM module |
dspfarm |
" Check sh dspfarm" |
|
DSPFARM-4-WARNING |
4-Warning |
Warning on DSPFARM module [chars]\n |
Warning on DSPFARM module |
dspfarm |
" Check sh dspfarm all" |
|
DSPRM-2-DSPALARM |
2-Critical |
Received alarm indication from dsp [dec]/[dec]. Resetting the DSP. |
Fatal error detected in DSP. |
voice-dsp |
"contact your technical support representative." |
|
DSPRM-2-FORKFAIL |
2-Critical |
Process creation of [chars] failed. |
Failed to create the process. |
c3800 |
LOG_STD_ACTION |
|
DSPRM-3-DSPALARMINFO |
3-Error |
[chars] |
DSP Alarm Data |
- |
"" |
|
DSPRM-3-INSUFFICIENT |
3-Error |
Insufficient DSP resources for timeslot [dec] on port [chars] |
The configuration requires more DSP resources than are available. |
- |
"Change the configuration to specify fewer used timeslots.\n\ Install additional DSP resources to allow more complex\n\ configurations." |
|
DSPRM-3-INSUFFICIENT_DSP |
3-Error |
\nvoice-port : [chars] Not initialized due to insufficient DSP resources |
More DSP resources are needed to initialize the analog voice-port |
- |
"Install additional DSP resources to allow voice-port initialization" |
|
DSPRM-5-DSP_VIC_CONFIG_NAK |
5-Notice |
Received VIC config NAK from DSP[dec]/[dec] resetting the DSP. |
Receieved NAK message from DSP. Re-attempt initialization. |
- |
LOG_STD_NO_ACTION |
|
DSPRM-5-DSPFAIL |
5-Notice |
DSP [dec] in slot [chars] is in the failed state |
The DSP entered the FAILED state due to alarm indications. |
- |
"Replace the DSP resource." |
|
DSPRM-5-DSPMSGFAIL |
5-Notice |
Failed to get dsprm msg for msg id [chars] |
Unable to get dsprm control message |
- |
LOG_STD_NO_ACTION |
|
DSPRM-5-JUKEBOX |
5-Notice |
Jukebox transmit overlay resp [dec] on slot [chars] failed |
The Jukebox received failed response code. |
- |
"" |
|
DSPRM-5-JUKEBOX_UPDOWN |
5-Notice |
DSP Jukebox[dec] in slot [chars] changed state to [chars] |
The DSP JUKEBOX changed state. |
- |
LOG_STD_NO_ACTION |
|
DSPRM-5-KEEPALIVE |
5-Notice |
DSP [dec] in slot [chars] NOT RESPONDING - auto restart[dec] times |
The DSP failed the background keep-alive test. |
- |
LOG_STD_NO_ACTION |
|
DSPRM-5-NULLIDB_CREATE_FAIL |
5-Notice |
VoIP Null IDB creation failed. |
VoIP nullidb creation failed. |
- |
"" |
|
DSPRM-5-SETCODEC |
5-Notice |
Configured codec [dec] is not supported with this dsp image. |
Codec negotiation failed. |
- |
"" |
|
DSPRM-5-UP_DOWN |
5-Notice |
DSP [dec] in subslot [chars] changed state to [chars] |
The DSP resource changed state. |
- |
LOG_STD_NO_ACTION |
|
DSPRM-5-UPDOWN |
5-Notice |
DSP [dec] in slot [dec] changed state to [chars] |
The DSP resource changed state. |
- |
LOG_STD_NO_ACTION |
|
DSPU-3-ActpuNegResponse |
3-Error |
ACTPU Neg rsp received from PU [chars] |
Remote PU rejected the router's request for an SSCP-PU session. |
- |
"Verify PU configuration parameters at the router and at the remote PU.\n\ Determine whether the problem exists at the remote PU and correct it.\n\ If the problem persists call your Cisco technical support\n\ representative for assistance." |
|
DSPU-3-CLSIBadAdptCorr |
3-Error |
CLSI bad Adaptor correlator header= [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
DSPU-3-CLSIBadIdentifier |
3-Error |
CLSI bad identifier header= [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
DSPU-3-CLSIBadIdentifierType |
3-Error |
CLSI bad identifier type header= [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
DSPU-3-CLSIBadLength |
3-Error |
CLSI bad length header= [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
DSPU-3-CLSIBadPrimitiveCmd |
3-Error |
CLSI bad primitive command header= [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
DSPU-3-CLSIBadPrimitiveType |
3-Error |
CLSI bad primitive type header= [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
DSPU-3-CLSIBadReturnCode |
3-Error |
CLSI bad return code: [dec] header= [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
DSPU-3-CLSIUnexpctActSapCnf |
3-Error |
CLSI unexpected ActivateSapCnf header= [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
DSPU-3-CLSIUnexpctDeactSapCnf |
3-Error |
CLSI unexpected DeactivateSapCnf header= [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
DSPU-3-CLSIUnexpctEnableCnf |
3-Error |
CLSI unexpected EnableCnf header= [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
DSPU-3-CLSIUnexpctIdStnInd |
3-Error |
CLSI unexpected IdStnInd header= [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
DSPU-3-DSPU_BufferCorrupted |
3-Error |
DSPU could not free buffer - buffer corrupted |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
DSPU-3-LSConnInFailed |
3-Error |
Connect in from remote address [chars] failed. |
Connection with the remote station could not be established because of\n\ insufficient memory in the router. |
- |
"Correct low memory problem in the router. If the problem persists\n\ call your technical support representative for assistance." |
|
DSPU-3-LSConnInFromHostFailed |
3-Error |
Connect in from host [chars] with remote address [chars] failed. |
Connection with the remote host could not be established. |
- |
"Verify host configuration parameters at the router and at the host.\n\ Determine whether the router is configured to accept connection from\n\ this host." |
|
DSPU-3-LSConnInFromPuFailed |
3-Error |
Connect in from pu [chars] with remote address [chars] failed. |
Connection with the remote PU could not be established. |
- |
"Verify PU configuration parameters at the router and at the remote PU.\n\ Determine whether the router is configured to accept connectIn from\n\ this remote PU." |
|
DSPU-3-LSConnOutToHostFailed |
3-Error |
Connect out to host [chars] failed. |
Connection with the remote host could not be established. |
- |
"Verify host configuration parameters at the router and at the host.\n\ Determine whether the host is active and responding to connection\n\ requests." |
|
DSPU-3-LSConnOutToPuFailed |
3-Error |
Connect out to pu [chars] failed. |
Connection with the remote PU could not be established. |
- |
"Verify PU configuration parameters at the router and at the remote PU.\n\ Determine whether the remote PU is active and responding to connection\n\ requests." |
|
DSPU-3-LSInvalidMaxIFrame |
3-Error |
Connection attempt failed from XID= [chars] Invalid MaxIFrame= [dec] |
- |
- |
"Correct link station configuration at the remote station." |
|
DSPU-3-LSInvalidWindowSize |
3-Error |
Connection attempt failed from XID= [chars] Invalid WindowSize= [dec] |
- |
- |
"Correct link station configuration at the remote station." |
|
DSPU-3-LSNoACTPUCapability |
3-Error |
Connection attempt failed from XID= [chars] ACTPU not supported |
- |
- |
- |
|
DSPU-3-LSXIDNegotiationError |
3-Error |
XID Negotiation Error bad byte= [dec] bad bit= [dec] sense data= [chars] |
- |
- |
"Determine from the CV 22 byte or bit information which field in the\n\ XID3 is rejected by the remote station and correct the link station\n\ configuration parameters at either the router or the remote station." |
|
DSPU-3-NotifyNegRsp |
3-Error |
LU [dec] received a Notify Neg Resp from host [chars] |
Remote host rejected the router's request to activate/deactivate an\n\ SSCP-LU session. |
- |
"Verify host configuration parameters at the router and at the remote\n\ host. Determine whether the problem exists at the remote host and\n\ correct it. If the problem persists call your technical support\n\ representative for assistance." |
|
DSPU-3-SnaBadData |
3-Error |
Bad SNA data received from PU [chars] data= [chars] |
Unrecognized SNA data was received from the remote PU. |
- |
"Correct the problem at the remote PU. If the problem persists call\n\ your Cisco technical support representative for assistance." |
|
DSPU-3-UnknownXid |
3-Error |
XID Format not supported XID= [chars] |
- |
- |
- |
|
DSS-3-ACK_FAIL |
3-Error |
Ack failed for dsp_id [dec]\n\ seq_no [dec] |
DSP core not responding to host messages |
- |
LOG_STD_NO_ACTION |
|
DSS-3-DSPID_INVALID |
3-Error |
Invalid DSPID [dec] |
Invalid DSP ID detetced in the message |
- |
LOG_STD_NO_ACTION |
|
DSS-3-TIMER |
3-Error |
[chars] timer expired for DSPID [dec] |
DSS timer has expired |
- |
LOG_STD_NO_ACTION |
|
DSS-5-UPDOWN |
5-Notice |
DSP core [dec] is [chars] |
DSP core changed state up/down |
- |
LOG_STD_NO_ACTION |
|
DSX0-5-RBSLINEDBUSYOUT |
5-Notice |
RBS of slot [dec] controller [dec] timeslot [dec] is dynamic busyout |
- |
- |
LOG_STD_NO_ACTION |
|
DSX0-5-RBSLINEDOWN |
5-Notice |
RBS of controller [dec] timeslot [dec] is down |
- |
- |
LOG_STD_NO_ACTION |
|
DSX0-5-RBSLINESBUSYOUT |
5-Notice |
RBS of slot [dec] controller [dec] timeslot [dec] is static busyout |
- |
- |
LOG_STD_NO_ACTION |
|
DSX0-5-RBSLINEUNBUSYOUT |
5-Notice |
RBS of slot [dec] controller [dec] timeslot [dec] is unbusyout |
- |
- |
LOG_STD_NO_ACTION |
|
DSX0-5-RBSLINEUP |
5-Notice |
RBS of controller [dec] timeslot [dec] is up |
- |
- |
LOG_STD_NO_ACTION |
|
DSX1-1-FIRMWARE_RESTART_FAILED |
1-Alert |
Trunk Firmware in slot [dec] reset failed |
Trunk could not be restarted. |
dsx1 |
LOG_STD_ACTION |
|
DSX1-1-FIRMWARE_RUNNING |
1-Alert |
T1/E1 Firmware in slot [dec] is running |
T1/E1 Firmware is now running after recovering from critical error. |
dsx1 |
LOG_STD_ACTION |
|
DSX1-1-FIRMWARE_STOPPED |
1-Alert |
T1/E1 Firmware in slot [dec] is not running |
Critical error occurred in the T1/E1 Firmware and it stopped running. \n\ Access server needs to be reloaded. |
dsx1 |
LOG_STD_ACTION |
|
DSX1-1-M32_INPUT_CONGEST |
1-Alert |
Munich 32 channel input queue is congested |
Can't allocate receive buffers since input queue is at its maximum this indicates\n\ data is coming faster than the receiver can handle. |
dsx1 |
"Reduce data goes into this channel and or increase the number of input queue." |
|
DSX1-3-FIRMWARE_RESTART |
3-Error |
T1/E1 Firmware in slot [dec] restarted |
T1/E1 Firmware restarted. All the active calls on the T1/E1 lines\n\ will be disconnected and the controllers will come back up within\n\ few seconds |
dsx1 |
LOG_STD_ACTION |
|
DSX1-3-M32_AR_FAILURE |
3-Error |
MSG_TRACEBACK|MSG_PROCESS |
- |
- |
- |
|
DSX1-3-M32_AR_TIMEOUT |
3-Error |
MSG_TRACEBACK|MSG_PROCESS |
- |
- |
- |
|
DSX1-3-M32_BAD_BITRATE |
3-Error |
MSG_TRACEBACK|MSG_PROCESS |
- |
- |
- |
|
DSX1-3-M32_BAD_INTQ |
3-Error |
MSG_TRACEBACK|MSG_PROCESS |
- |
- |
- |
|
DSX1-3-M32_BAD_STATE |
3-Error |
MSG_TRACEBACK|MSG_PROCESS |
- |
- |
- |
|
DSX1-3-M32_ERR |
3-Error |
MSG_TRACEBACK|MSG_PROCESS |
- |
- |
- |
|
DSX1-3-M32_ILLEGAL_CHANNEL |
3-Error |
MSG_TRACEBACK|MSG_PROCESS |
- |
- |
- |
|
DSX1-3-M32_MEM_ALLOC |
3-Error |
MSG_TRACEBACK|MSG_PROCESS |
- |
- |
- |
|
DSX1-3-M32_NO_TIMESLOT |
3-Error |
MSG_TRACEBACK|MSG_PROCESS |
- |
- |
- |
|
DSX1-3-M32_TIMESLOT_IN_USE |
3-Error |
MSG_TRACEBACK|MSG_PROCESS |
- |
- |
- |
|
DSX1-3-NOMEMORY |
3-Error |
MSG_TRACEBACK|MSG_PROCESS |
- |
- |
- |
|
DSX1-6-CLOCK_CHANGE |
6-Information |
[chars] clock is now selected as clock source |
- |
- |
LOG_STD_NO_ACTION |
|
DSX-4-ALARM |
4-Warning |
[chars] [chars]: [chars] |
The specified T1/E1 or T3/E3 Alarm has been asserted or cleared |
- |
"The recommended action is to isolate and repair the" " source of the asserted alarm" |
|
DTI-3-DTI_ERROR |
3-Error |
DTI Error |
First DTI error message |
rfgw-sw-sup |
LOG_STD_NO_ACTION |
|
DTLS-3-REPLAY_ERROR_DTLS |
3-Error |
DTLS anti-replay error src_addr: %Ci src_port: [dec] dest_addr: %Ci dst_port: [dec] |
Anti-replay error is encountered for this DTLS session. |
qfp-ipsec |
LOG_STD_ACTION |
|
DTLS-3-REPLAY_ERROR_IPV6_DTLS |
3-Error |
DTLS anti-replay error ipv6 src_addr: [ipv6_addr], src_port: [dec] ipv6 dest_addr: [ipv6_addr], dst_port: [dec] |
Anti-replay error is encountered for this DTLS session. |
qfp-ipsec |
LOG_STD_ACTION |
|
DTP-4-MEM_UNAVAIL |
4-Warning |
Memory was not available to perform the trunk negotiation action |
Unable to negotiate trunks because of a lack of memory |
- |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
DTP-4-TMRERR |
4-Warning |
An internal timer error occurred when trunking on interface [chars] |
There might be some instances in which a timer used by the trunking\n\ protocol expires at a time when it is unexpected. This problem is\n\ corrected internally. |
- |
"There is likely no long-term ramifications from this problem. However\n\ if further problems with trunking are seen it is recommended that you\n\ reload the device." |
|
DTP-4-UNKN_ERR |
4-Warning |
An unknown operational error occurred |
Unable to negotiate trunks because an internal operation\n\ generated an error which was not expected to ever happen. |
- |
"Because of the unexpected nature of the problem the only recommended\n\ action is to reload the device" |
|
DTP-5-DOMAINMISMATCH |
5-Notice |
Unable to perform trunk negotiation on port [chars] because of VTP domain mismatch. |
The two ports involved in trunk negotiation belong to different \n\ VTP domains. Trunking is possible only when the ports involved belong to\n\ the same VTP domain. |
dtp |
"Ensure that the two ports that are involved in trunk negotiation belong to\n\ the same VTP domain." |
|
DTP-5-ILGLCFG |
5-Notice |
Illegal configonisl--ondot1q on [chars] |
The two ports on the link are set to the ON mode but one is set to\n\ 802.1Q encapsulation while the other is set to ISL encapsulation.\n\ When both ports on a link are set to the ON mode their encapsulation\n\ types must match |
- |
"Configure both ports on the link to have the same encapsulation." |
|
DTP-5-NONTRUNKPORTON |
5-Notice |
Port [chars] has become non-trunk |
The specified port has changed from being a trunk port to an access\n\ port. |
- |
"" |
|
DTP-5-TRUNKPORTCHG |
5-Notice |
Port [chars] has changed from [chars] trunk to [chars] trunk |
The specified trunk port has changed the encapsulation type is uses. |
- |
"" |
|
DTP-5-TRUNKPORTON |
5-Notice |
Port [chars] has become [chars] trunk |
The specified port has changed from being an access port to a trunk\n\ port using the specified encapsulation. |
- |
"" |
|
dtsec-1-BAD_IDB |
1-Alert |
Invalid Interface Descriptor Block |
The driver tried to fetch the interface's IDB and failed |
high-gig-ethernet |
"Software bug - open a case with Development Engineering." LOG_STD_SH_TECH_ACTION |
|
dtsec-1-BAD_MEDIA |
1-Alert |
Unknown media-type in subblock |
The media-type specified in the driver subblock is invalid |
high-gig-ethernet |
"Software bug - open a case with Development Engineering." LOG_STD_SH_TECH_ACTION |
|
dtsec-1-BAD_PARTICLE |
1-Alert |
Problem getting particle size |
The driver was unable to get the particle size for this interface |
high-gig-ethernet |
"Software bug - open a case with Development Engineering." LOG_STD_SH_TECH_ACTION |
|
dtsec-1-BAD_PLUGIN |
1-Alert |
Plugin function table incomplete or missing |
The driver could not access the PA's specific function table |
high-gig-ethernet |
"Software bug - open a case with Development Engineering." LOG_STD_SH_TECH_ACTION |
|
dtsec-1-BAD_POOL |
1-Alert |
Could not init buffer pools |
The driver failed to get a pool of buffers from IOS |
high-gig-ethernet |
"Software bug - open a case with Development Engineering." LOG_STD_SH_TECH_ACTION |
|
dtsec-1-BAD_SB_NOMEM |
1-Alert |
[chars] - Cannot create IDB subblock due to insufficient memory |
There was insufficent system memory to create the subblock. |
high-gig-ethernet |
"The router requires more main memory." LOG_STD_SH_TECH_ACTION |
|
dtsec-1-BAD_STRUCT |
1-Alert |
Could not initialize structure |
The driver failed to initialize a structure |
high-gig-ethernet |
"Software bug - open a case with Development Engineering." LOG_STD_SH_TECH_ACTION |
|
dtsec-1-BAD_SUBBLOCK |
1-Alert |
[chars] - Could not install or use IDB subblock |
An internal IOS error prevented the IDB subblock from being installed or used. |
high-gig-ethernet |
"Software bug - open a case with Development Engineering." LOG_STD_SH_TECH_ACTION |
|
dtsec-1-IDBTYPE_UNK |
1-Alert |
Unknown IDBTYPE while starting driver |
The IDBTYPE in the interface's instance structure is undefined for this driver |
high-gig-ethernet |
"Software bug - open a case with Development Engineering." LOG_STD_SH_TECH_ACTION |
|
dtsec-1-INITFAIL_NOMEM |
1-Alert |
[chars] initialization failed no buffer memory |
The Ethernet port initialization failed due to insufficient memory |
high-gig-ethernet |
"The router requires more packet memory - consider upgrade." LOG_STD_RECUR_ACTION |
|
dtsec-1-MODE_INVALID |
1-Alert |
Unknown or invalid chip mode MII/TBI |
The driver subblock contains an invalid or undefined chip operating mode MII or TBI mode |
high-gig-ethernet |
"Software bug - open a case with Development Engineering." LOG_STD_SH_TECH_ACTION |
|
dtsec-1-RESET |
1-Alert |
MAC Still in Reset |
An attempt was made to access the MAC while it was in reset |
high-gig-ethernet |
LOG_STD_SH_TECH_ACTION |
|
dtsec-2-NOISL |
2-Critical |
Interface [chars] does not support ISL |
ISL is not supported on the specified interface's hardware. |
- |
LOG_STD_NO_ACTION |
|
dtsec-3-BAD_GBIC_EEPROM |
3-Error |
[chars] - GBIC contains a bad EEPROM |
Interface contains a GBIC with a bad EEPROM. This causes the link to be down. |
high-gig-ethernet |
"Please make sure the GBIC type is compatible with the interface. " "Verify that the GBIC was obtained from Cisco or a supported vendor" |
|
dtsec-3-DUPLICATE |
3-Error |
[chars] - duplicate GBIC |
The GBIC module for the interface specified in the error message is a duplicate of another GBIC in the system. As a result of the error both modules are disabled. |
high-gig-ethernet |
"Remove the duplicate module. If the problem persists LOG_STD_ACTION." |
|
dtsec-3-ERRINT |
3-Error |
[chars] error interrupt mac_status = 0x%016llx |
The MAC controller has signalled an error condition. |
high-gig-ethernet |
LOG_STD_ACTION |
|
dtsec-3-MAC_LIMIT_EXCEEDED |
3-Error |
Unable to add mac address [enet] |
Max number of allowed mac entries reached. Cannot add any more. |
- |
"Try removing some of the own mac addresses for example used by each" "unique hsrp group configuration. standby use-bia could be used to " "limit the usage" |
|
dtsec-3-NOT_SUPPORTED |
3-Error |
[chars] - unsupported GBIC |
The GBIC 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. |
high-gig-ethernet |
"Replace the module with a Cisco-supported GBIC. If the problem " "persists LOG_STD_ACTION." |
|
dtsec-3-TOOBIG |
3-Error |
[chars] packet too big [dec] from [enet] |
The interface detects a packet larger than what is defined by MTU |
high-gig-ethernet |
"Check the other station's MTU setting" LOG_STD_NO_ACTION |
|
dtsec-3-UNKNOWN_GBIC |
3-Error |
[chars] - Unknown GBIC type |
Interface contains a GBIC of unknown type. This causes the link to be down. |
high-gig-ethernet |
"Please make sure the GBIC type is compatible with the interface. " "Verify that the GBIC was obtained from Cisco or a supported vendor" |
|
DUAL-3-ANCHORCOUNT |
3-Error |
Anchor count negative |
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-3-BADCOUNT |
3-Error |
Route [chars] [dec] successors [dec] rdbs |
A hardware or software error occurred. |
- |
LOG_STD_ACTION |
|
DUAL-3-BADCOUNT |
3-Error |
Route [chars] [dec] successors [dec] rdbs |
A hardware or software error occurred. |
- |
LOG_STD_ACTION |
|
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-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-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-INTERNAL |
3-Error |
[chars] [dec]: Internal Error |
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-3-LINKSEXIST |
3-Error |
Interface [chars] going down and [dec] links exist |
- |
- |
LOG_STD_ACTION |
|
DUAL-3-LINKSEXIST |
3-Error |
Interface [chars] going down and [dec] links exist |
- |
- |
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-LINKSTILLUP |
3-Error |
Link [dec] [chars] still exists on [chars] |
A hardware or software 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-MULTIFLOW |
3-Error |
Flow control error [chars] on [chars] |
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-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-NOHANDLE |
3-Error |
Handle [dec] is not allocated in pool. |
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-NOMATCH |
3-Error |
Nexthop and infosource don't match. N = [chars] I = [chars] |
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-NOSOCKET |
3-Error |
Unable to open socket for AS [dec] |
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-PEERSEXIST |
3-Error |
[dec] peers exist on IIDB [chars] |
A software or hardware 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-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-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-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-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-REFCOUNT |
3-Error |
Negative refcount in pakdesc [hec] |
A software or hardware 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-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-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-UNKTIMER |
3-Error |
Unknown timer type [dec] expiration |
A hardware or software error occurred. |
- |
LOG_STD_ACTION |
|
DUAL-3-UNKTIMER |
3-Error |
Unknown timer type [dec] expiration |
A hardware or software error occurred. |
- |
LOG_STD_ACTION |
|
DUAL-4-PFXLIMITTHR |
4-Warning |
[chars] [dec]: [chars] threshold prefix level[dec] reached. |
- |
- |
- |
|
DUAL-4-PFXLIMITTHR |
4-Warning |
[chars] [dec]: [chars] threshold prefix level[dec] reached. |
- |
- |
- |
|
DUAL-5-NBRCHANGE |
5-Notice |
[chars] [dec]: Neighbor [chars] [chars] is [chars]: [chars] |
A neighbor went up or down. |
- |
LOG_STD_NO_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-EVENT |
6-Information |
[chars] [chars] |
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-6-NBRINFO |
6-Information |
[chars] [dec]: Neighbor [chars] [chars] is [chars]: [chars] |
Information regarding a neighbor. |
- |
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 |
|
DUP_ADDR_RCVD-3-LCON |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
DUP_IP_ADDRESS-2-MPLS_TE_PCALC |
2-Critical |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
DUP_RRR_ID-2-MPLS_TE_PCALC |
2-Critical |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
DWDM-3-CLEAR_G709_CTR |
3-Error |
Unable to clear g709 \ counter in slot [dec] rc = [dec] |
The SPA driver was unable to clear the G.709 OTN protocol counters for bit errors |
spa-eth-10ge |
"Please check the configuration of the interfaces and controllers " "and correct the configuration if necessary. If the problem persists " "contact your Cisco technical support representative" |
|
DWDM-3-CONFIG_ALARM_REPORT |
3-Error |
Failed to config report\n\ alarm [chars] slot [dec] rc = [dec] |
The SPA driver could not configure one of the reporting status of the alarms |
spa-eth-10ge |
"Please check the configuration of the interfaces and controllers " "and correct the configuration if necessary. If the problem persists " "contact your Cisco technical support representative" |
|
DWDM-3-CONFIG_ALARM_THRESHOLD |
3-Error |
Failed to config threshold \n\ alarm [chars] slot [dec] rc = [dec] |
The SPA driver could not configure one of the threshold alarms for the optical data or transport unit |
spa-eth-10ge |
"Please check the configuration of the interfaces and controllers " "and correct the configuration if necessary. If the problem persists " "contact your Cisco technical support representative" |
|
DWDM-3-CONFIG_OVERHEAD_TTI |
3-Error |
Failed to config [chars] [chars] slot [dec] rc = [dec] |
The LC driver could not configure the tail trace identifier for the optical data or transport unit |
- |
"Please check the configuration of the interfaces and controllers " "and correct the configuration if necessary. If the problem persists " "contact your Cisco technical support representative" |
|
DWDM-3-CONFIG_PM |
3-Error |
Failed to config [chars] [chars] slot [dec] rc = [dec] |
The LC driver could not configure the PM parameters for the optical data or transport unit |
- |
"Please check the configuration of the interfaces and controllers " "and correct the configuration if necessary. If the problem persists " "contact your Cisco technical support representative" |
|
DWDM-3-CONFIG_TX_POWER |
3-Error |
Failed to config \ transmit power [dec] on slot [dec] rc = [dec] |
The SPA driver detected a error in configuring the Tx power level for the UT2 transponder module |
spa-eth-10ge |
"Please power down and reseat the indicated SPA card. " "If the condition persists copy the error message exactly as " "it appears. Next research and attempt to resolve the issue using " "the SPA hardware troubleshooting documentation as well as the tools " "and utilities provided at " "http://www.cisco.com/public/support/tac/tools.shtml. If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a 'show tech-support' to " "your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
DWDM-3-DWDM_CONFIG_FAIL |
3-Error |
Failed to [chars] [chars] in slot [dec] rc = [dec] |
The SPA driver detected failure during configuring one of the DWDM parameters |
spa-eth-10ge |
"Reload the SPA card and if the problem" "persists call the tachnical assistance centre" |
|
DWDM-3-DWDM_GET_INFO_FAIL |
3-Error |
Failed receiving [chars] \ from slot [dec] rc = [dec] |
The SPA driver did not receive the necessary optics information from the slot |
spa-eth-10ge |
"Please check the configuration of the interfaces and controllers " "and correct the configuration if necessary. If the problem persists " "contact your Cisco technical support representative" |
|
DWDM-3-DWDM_NULL_INFO |
3-Error |
DWDM info is NULL in [dec] |
The SPA driver detected NULL information for DWDM |
spa-eth-10ge |
"Reload the SPA and if the problem persists" "contact the technical support representative" |
|
DWDM-3-IPC_SHIM_INIT |
3-Error |
DWDM IPC SHIM init failed |
The SPA driver detected failure during DWDM IPC SHIM initialization |
spa-eth-10ge |
"Please power down and reseat the indicated SPA card" "If the problem persists please contact your" "technical support representative" |
|
DWDM-3-LC_ERR_STATS |
3-Error |
error sending LC stats to RP |
The SPA driver encountered an error while sending the LC stats to the RP |
spa-eth-10ge |
"Reload the SPA card and if the problem persists" "call the technical support representative" |
|
DWDM-3-MALLOC_FAIL |
3-Error |
malloc failure creating \ G.709 port on slot [dec] |
The SPA driver detected a memory error on the SPA card |
spa-eth-10ge |
"Reload the card and if the problem persists " " call TAC" |
|
DWDM-3-OTN_STATS_CREATE_IF_FAIL |
3-Error |
stats for interface index [dec] could not be created with status [dec] |
- |
snmp-otn |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
DWDM-3-OTN_STATS_CREATE_IF_FAILED_TO_ALLOCATE |
3-Error |
stats for interface index [dec] could not be created with status [dec] |
- |
snmp-otn |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
DWDM-3-OTN_STATS_DELETE_IF_FAIL |
3-Error |
stats for interface index [dec] could not be deleted with status [dec] |
- |
spa-eth-10ge |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
DWDM-3-RPC_FAILED |
3-Error |
Application error rc = [dec]: |
The system failed to retrieve the information required to \n\ execute the command |
g709-dwdm |
show version |
|
DWDM-3-RPC_INIT_FAIL |
3-Error |
DWDM 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 \n\ some \show\ commands could fail. |
g709-dwdm |
show version |
|
DWDM-3-RPC_PROCESSING_ERROR |
3-Error |
DWDM RPC error: [chars] |
Non Fatal error occured in processing an RPC messsage. |
g709-dwdm |
show version |
|
DWDM-3-RX_G709_INFO |
3-Error |
Failed receiving G709 info \ from slot [dec] rc = [dec] |
The SPA driver did not receive the necessary G.709 OTN protocol information from the slot |
spa-eth-10ge |
"Please check the configuration of the interfaces and controllers " "and correct the configuration if necessary. If the problem persists " "contact your Cisco technical support representative" |
|
DWDM-3-RX_LOS_THRESHOLD |
3-Error |
Failed to config \ rx los threshold = [dec] on slot [dec] rc = [dec] |
The SPA driver detected an error in configuring the transponder receive power threshold |
spa-eth-10ge |
"Reload the SPA card and if the problem persists" "call TAC" |
|
DWDM-3-TIMER_ERR |
3-Error |
Timer error |
The Driver did not obtain an expired timer from the timer tree for the DWDM process |
spa-eth-10ge |
"The SPA driver has encountered an error event on the SPA card." "If the condition persists copy the error message exactly as " "it appears or contact " "your technical support representative" |
|
DWDM-4-G709ALARM |
4-Warning |
[chars]: [chars] [chars] |
The specified G709 Alarm has been declared or released |
g709-dwdm |
"Recommended action is to repair the source of the alarm." |
|
DWL-3-LOOP_BACK_DETECTED |
3-Error |
Loop-back detected on [chars]. |
Loop-back may be caused by accidentally plugging a balun cable into the port or there may be a misconfiguration in the network. |
firmware |
"Correct the problem causing the loopback " "condition. Then bring the port up by entering the shutdown " "then no shutdown interface configuration commands." |
|
DYINGGASP-0-POWER_LOSS |
0-Emergency |
Shutdown due to power loss |
This is a fail over message which is logged if this unit is about to shutdown due to power loss. |
- |
"Verify that the unit is powered on and power cables are" " connected correctly." |
|
DYINGGASP-6-HOST_NOT_SUPP |
6-Information |
[chars] host [inet] is not supported for dyinggasp notification due to [chars]\n |
This message id logged if dying gasp ignores either SNMP or Syslog host for dying gasp notification. |
- |
"No action necessary" |
|
DYNCMD-3-CHAINADDFAIL |
3-Error |
Parse chain link add failed for '[chars]' |
An error has occurred when a dynamic command is being added to the IOS command set. The commands specified will not be available. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-CHAINDELFAIL |
3-Error |
Parse chain link delete failed for '[chars]' |
An error has occurred when a dynamic command is being removed from the IOS command set. The commands specified will stil not be available. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-FLAGSINUSE |
3-Error |
New feature flags list [dec] invalid while feature flags in use [dec] |
IOS received a message to set the feature flags for the CLI. The message received to set the feature flags changed the number of feature flags which is unexpected. The message is ignored. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-FLAGSINVALID |
3-Error |
New feature flag list values [dec] different than expected [dec] |
- |
- |
- |
|
DYNCMD-3-INIT |
3-Error |
Dynamic command subsystem failed to initialize '[chars]' |
Some features depend on portions of the dynamic command infrastructure. Such features will be unavailable. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-LINKINVALIDALT |
3-Error |
Link alternate node message received for node '[chars]' which cannot have an alternate. |
IOS received a message to add a command into the CLI. One of the messages to link nodes instructed IOS to link nodes which would result in an invalid construction. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-LINKINVALIDTRANS |
3-Error |
Link transition '[chars]' message received for node '[chars]' which cannot have such a transition. |
IOS received a message to add a command into the CLI. One of the messages to link nodes instructed IOS to link nodes which would result in an invalid construction. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-LINKOUTOFSEQ |
3-Error |
Create node message received when in mode '[chars]' |
IOS received a message to add a command node into the CLI. The message was received out of sequence |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-LINKUNKNOWNACCEPTNODE |
3-Error |
Link node message received for unknown accept [chars] node '[dec]' |
- |
- |
- |
|
DYNCMD-3-LINKUNKNOWNALTNODE |
3-Error |
Link node message received for unknown alternate node '[dec]' |
IOS received a message to add a command into the CLI. One of the messages to link nodes referenced a node unknown to IOS |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-LINKUNKNOWNNODE |
3-Error |
Link node message received for unknown node '[dec]' |
IOS received a message to add a command into the CLI. One of the messages to link nodes referenced a node unknown to IOS |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-MSGBIPCBUFFER |
3-Error |
Unable to acquire a BIPC buffer for sending messages. |
A message was to be sent by IOS but no BIPC buffer was available. The message to be sent has been discarded and the associated operation failed. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-MSGBIPCERR |
3-Error |
Unable to process received BIPC messages for Dynamic Commands error: [chars] |
An unexpected condition has occurred while IOS was trying to process a received BIPC message for Dynamic Commands. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-MSGBUILDERROR |
3-Error |
Error '[dec]' building TDL message '[chars]' to send to the Shell Manager |
An unexpected condition has occurred while IOS is building a TDL message to send to the Shell Manager |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-MSGDISPATCH |
3-Error |
Unable to dispatch received TDL messages for Dynamic Commands |
An unexpected condition has occurred while IOS is trying to dispatch to the TDL message handler functions for received TDL messages for Dynamic Commands. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-MSGDISPATCHNULL |
3-Error |
Received NULL TDL message |
An unexpected condition in which IOS has received a NULL TDL message for Dynamic Commands. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-MSGENQUEUEERROR |
3-Error |
Error queueing TDL message '[chars]' to send to the Shell Manager |
An unexpected condition has occurred when IOS attempted to queue a TDL message to send to the Shell Manager |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-MSGERROR |
3-Error |
Error '[chars]' handling a received TDL message '[chars]' for Dynamic Commands |
An unexpected condition has occurred while IOS is processing a received Dynamic Command TDL message |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-MSGINVALIDFIELDINT |
3-Error |
Invalid field '[chars]' in TDL message '[chars]' received: value '[dec]' for Dynamic Commands |
A message with an invalid field value was received for Dynamic Command creation |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-MSGINVALIDFIELDSTR |
3-Error |
Invalid field '[chars]' value '[chars]' in TDL message '[chars]' received for Dynamic Commands |
A message with an invalid field value was received for Dynamic Command creation |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-MSGMARSHALERROR |
3-Error |
Error '[dec]' marshaling TDL message '[chars]' to send to the Shell Manager |
An unexpected condition has occurred while IOS is marshaling TDL message to send to the Shell Manager |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-MSGMISSINGFIELD |
3-Error |
Missing field '[chars]' in TDL message '[chars]' received from the Shell Manager |
A message missing a required field was received from the Shell Manager |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-NODEDUPLICATE |
3-Error |
Create node message received for duplicate node '[dec]' |
IOS received a message to add a command into the CLI. One of the command nodes to be created has an identifier of an existing node. The new node is ignored. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-NODEOUTOFSEQ |
3-Error |
Create node message received when in mode '[chars]' |
IOS received a message to add a command node into the CLI. The message was received out of sequence |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-NODETYPEUNKNOWN |
3-Error |
Create node message received for unknown node type '[dec]' '[chars]' |
IOS received a message to add a command into the CLI. One of the command nodes to be created is of a type unknown to IOS |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-PKGERR_LOG_FAIL |
3-Error |
Failed to log errors for package '[chars]' |
An error has occurred updating the commandset for a newly installed package. The commands which failed to transfer could not be saved for further analysis. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-PKGHANDLER_FILE_REMOVE |
3-Error |
Package '[chars]' failed to remove: [chars] [chars] |
- |
- |
- |
|
DYNCMD-3-PKGHANDLER_FILE_WRITE |
3-Error |
Package '[chars]' failed to write: [chars] [chars] |
- |
- |
- |
|
DYNCMD-3-PKGINT_API |
3-Error |
Package interface failure for package '[chars]': [chars] |
Some features' configuration depends on a packaging infrastructure. Packaged configuration for the specified package will be unavailable. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-PKGINT_ARG |
3-Error |
Incorrect argument type for package '[chars]' operation '[chars]': [chars] [dec] |
- |
- |
- |
|
DYNCMD-3-PKGINT_ARG_NUMBERVAL |
3-Error |
Invalid argument value for package '[chars]' operation '[chars]': [dec] [dec] |
- |
- |
- |
|
DYNCMD-3-PKGINT_ARG_OPAQUEVAL |
3-Error |
Invalid argument value for package '[chars]' operation '[chars]': %p [dec] |
- |
- |
- |
|
DYNCMD-3-PKGINT_ARGS |
3-Error |
Incorrect argument count for package '[chars]' operation '[chars]': [dec] not [dec] |
An error has occurred loading the commandset for a newly installed package. The package is not compatible with the running IOS instance. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-PKGINT_DIR_CREATE |
3-Error |
Package integration failed to create directory: [chars] [chars] |
- |
- |
- |
|
DYNCMD-3-PKGINT_DIR_MOVE |
3-Error |
Package integration failed to move directory: [chars] to [chars] [chars] |
- |
- |
- |
|
DYNCMD-3-PKGINT_DIR_OPEN |
3-Error |
Package integration failed to open directory: [chars] [chars] |
- |
- |
- |
|
DYNCMD-3-PKGINT_DIR_REMOVE |
3-Error |
Package integration failed to remove directory: [chars] [chars] |
- |
- |
- |
|
DYNCMD-3-PKGINT_FILE_OPEN |
3-Error |
Package integration failed to open file: [chars] [chars] |
- |
- |
- |
|
DYNCMD-3-PKGINT_FILE_REMOVE |
3-Error |
Package integration failed to remove: [chars] [chars] |
- |
- |
- |
|
DYNCMD-3-PKGINT_INSTALL |
3-Error |
Failed to install '[chars]': [chars] |
Some features' configuration depends on a packaging infrastructure. Packaged configuration for the specified package will be unavailable. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-PKGINT_LOAD |
3-Error |
Failed to load '[chars]': [chars] |
Some features' configuration depends on a packaging infrastructure. Packaged configuration for the specified package will be unavailable. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-PKGINT_LOCK |
3-Error |
Failed to acquire package list lock for [chars]: [chars] |
An error occurred when a configuration package was being installed or removed. This may indicate a timeout which may be a temporary condition. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-PKGINT_OFFSET |
3-Error |
Invalid offset argument for package '[chars]' operation '[chars]': [chars] [dec] |
- |
- |
- |
|
DYNCMD-3-PKGINT_PKGLOCK |
3-Error |
[chars] failed to acquire package lock for [chars] |
An error occurred when locking a configuration package. The package needs to be locked for processing configuration commands or timer-based processing of configuration data. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-PKGINT_SYMBOL |
3-Error |
Package [chars] incompatible: symbol '[chars]' is of type [chars] expected [chars] |
Some features' configuration depends on a packaging infrastructure. Packaged configuration for the specified package will be unavailable. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-PKGINT_UNLOCK |
3-Error |
Failed to release the package list lock: [chars] |
An error occurred when a configuration package was being installed or removed. This should not occur. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-PKGINT_VALIDATE |
3-Error |
Failed to validate '[chars]': [chars] |
Some features' configuration depends on a packaging infrastructure. Packaged configuration for the specified package will be unavailable. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-PKGNODE_ADD_FAIL |
3-Error |
Parse node add failed for package '[chars]' [chars] [dec] |
- |
- |
- |
|
DYNCMD-3-TREETOP |
3-Error |
Unable to link top-level keyword '[chars]' into parse tree |
IOS received a message to add a command into the CLI. The appropriate location to link in the command could not be found. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-3-TREETOPNOTKW |
3-Error |
The top-level parser transition '[chars]' is not a keyword |
IOS received a message to add a command into the CLI. The top-level node must be a keyword node. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
DYNCMD-7-CMDSET_LOADED |
7-Debug |
The Dynamic Command set has been loaded from the Shell Manager |
IOS has completed loading the set of commands published and processed by components running in packages other than the IOS package. |
iosxe-shellmgr |
LOG_STD_NO_ACTION |
|
DYNCMD-7-CMDSET_UNLOADED |
7-Debug |
The Dynamic Command set from the Shell Manager has been unloaded |
IOS has completed unloading the Dynamic Command set. This should only occur when a new package has been installed and should shortly be followed by a message indicating that the new Dynamic Command set has been loaded. |
iosxe-shellmgr |
LOG_STD_NO_ACTION |
|
DYNCMD-7-PKGINT_INSTALLED |
7-Debug |
The command package '[chars]' has been succesfully installed |
IOS has completed installation of the specified command package. Configuration commands for the package are now available. |
iosxe-shellmgr |
LOG_STD_NO_ACTION |
|
DYNCMD-7-PKGINT_UNINSTALLED |
7-Debug |
The command package '[chars]' has been succesfully uninstalled |
IOS has completed uninstallation of the specified command package. Configuration commands for the package are no longer available. |
iosxe-shellmgr |
LOG_STD_NO_ACTION |
|
E_CFM-2-INIT_ALLOC_FAIL |
2-Critical |
Failed to allocate memory required for initialization. |
CFM failed to allocate a memory required for the feature to operate correctly. This likely indicates a resource limitation or an attempt to use the software on unsupported hardware. |
ethernet-cfm |
"Confirm that the configured scale does not exceed the permitted limits " "for the hardware and that any other resource issues are resolved. If " "problems are still observed copy the error message exactly as it " "appears on the console or in the system log call your Cisco technical " "support representative and provide the representative with the " "gathered information. " |
|
E_CFM-2-PD_CAPABILITY_UPDATE |
2-Critical |
Platform has indicated an invalid capability update which has been ignored. |
Platform code has indicated that its capabilities have changed based on a configuration knob but the updated values were inconsistent. |
ethernet-cfm |
"This likely indicates a programming error in Platform code but should " "not present a problem unless either of MA Alias and SLM over xconnect " "features are required. See documentation for this platform/release." |
|
E_CFM-3-CONFIG_ERROR |
3-Error |
CFM mis-configuration in the network. Continuity-check message is received from mac-address [enet] with duplicated mpid [dec] as configured locally for service MA name [chars] with [chars] of domain [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 MA. |
ethernet-cfm |
"Configure the CFM maintenance end points properly " "by giving unique mpid in a particular maintenance " "domain or association." |
|
E_CFM-3- CONFIG_LOST |
3-Error |
Failed to update CFM internal state to reflect configuration change: [chars] |
CFM failed to save the CFM configuration in response to the recent change. The reason for this may be due to a memory shortage. The user should resolve any memory problems and then check the CFM configuration and if necessary re-add any config that is missing. |
ethernet-cfm |
"Collect the output of <CmdBold>show tech-support ethernet-cfm<noCmdBold> " "as soon as possible after the problem is seen. " LOG_STD_ACTION |
|
E_CFM-3-CROSS_CONNECTED_SERVICE |
3-Error |
Continuity Check message is received from remote MEP mpid [dec] with service MA name [chars] [chars] MAC: [enet] for service MA name [chars] of domain [chars] level [dec]. |
The Continuity Check message whose MA name or MA level 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 MA name or MA level properly across " "the network." |
|
E_CFM-3-CROSSCHECK_MEP_MISSING |
3-Error |
The device does not receive any CC messages from a remote MEP with mpid [dec] MA name [chars] that it was expecting to be part of the [chars] in the domain [chars]. |
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 MA. |
ethernet-cfm |
"There could be a possible fault in the network. " "Check the CFM cross check configurations are " "proper. " |
|
E_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 MA name [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 MA. |
ethernet-cfm |
"Check whether the CFM crosscheck configurations " "are proper." |
|
E_CFM-3-FAULT_ALARM |
3-Error |
A fault has occurred in the network for the local MEP having mpid [dec] [chars] for service MA name [chars] 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 MEP'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 MA. |
ethernet-cfm |
"There could be a possible fault in the network. " "Check whether the cfm configurations are proper." |
|
E_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 MA name [chars]. |
The device is receiving its own CC messages for a particular vlan or evc within the same MA. |
ethernet-cfm |
"Configure the CFM maintenance points properly " "to avoid the forwarding loop." |
|
E_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." |
|
E_CFM-3- MAC_STATUS_CHANGE_FAIL |
3-Error |
Failed to set MAC layer operational state for [chars] to [chars]. |
CFM failed to update the state of the MAC layer for the specified interface in response to a change in the errors detected on the interface. If the MAC layer state is incorrect it is possible that data traffic flow through the interface will be affected either by traffic unexpectedly being allowed to pass through the interface or by traffic unexpectedly being dropped. |
ethernet-cfm |
"Collect the output of <CmdBold>show tech-support ethernet-cfm<noCmdBold> " "as soon as possible after the problem is seen. " LOG_STD_ACTION |
|
E_CFM-3- OIR_RESTORE |
3-Error |
Failed to restore CFM configuration on OIR insertion: [chars] |
CFM failed to restore the CFM configuration that was previously present on the interface prior to the OIR event. The user may need to be manually reconfigure the interface instead. |
ethernet-cfm |
"Collect the output of <CmdBold>show tech-support ethernet-cfm<noCmdBold> " "as soon as possible after the problem is seen. " LOG_STD_ACTION |
|
E_CFM-3- OIR_SAVE |
3-Error |
Failed to save CFM configuration on OIR removal: [chars] |
CFM failed to save the CFM configuration that was previously present on the interface prior to the OIR event. The user may need to be manually reconfigure the interface on reinsertion. |
ethernet-cfm |
"Collect the output of <CmdBold>show tech-support ethernet-cfm<noCmdBold> " "as soon as possible after the problem is seen. " LOG_STD_ACTION |
|
E_CFM-3-REMOTE_MEP_DOWN |
3-Error |
Remote MEP mpid [dec] [chars] MA name [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." |
|
E_CFM-3- TIMEOUT_TOO_SMALL |
3-Error |
Attempted to start a timer with a value less than the minimum permitted [dec]ms defaulting to [dec]ms. |
- |
- |
- |
|
E_CFM-6-CROSSCHECK_SERVICE_UP |
6-Information |
The device received CC messages from all remote MEPs within a given MA name [chars] in the maintenance domain [chars]. |
The service configured either MA is up as it receives CC messages from all remote statically configured MEPs. |
ethernet-cfm |
"Information message only." |
|
E_CFM-6-DATAPLANE_LATCHING_LOOPBACK_CONT_STATE_CHANGE |
6-Information |
Ethernet Dataplane Latching Loopback state change [chars] |
Dataplane Latching Loopback state changed for the specified service |
ethernet-cfm |
"LOG_STD_NO_ACTION" |
|
E_CFM-6-DATAPLANE_LATCHING_LOOPBACK_CONT_TIMER_EXPIRED |
6-Information |
Ethernet Dataplane Latching Loopback timer expired [chars] |
Dataplane Latching Loopback timer is expired for the specified service |
ethernet-cfm |
"LOG_STD_NO_ACTION" |
|
E_CFM-6-DATAPLANE_LATCHING_LOOPBACK_START |
6-Information |
Ethernet Dataplane Latching Loopback Start on [chars] |
Dataplane Latching Loopback is activated for the specified service |
ethernet-cfm |
"LOG_STD_NO_ACTION" |
|
E_CFM-6-DATAPLANE_LATCHING_LOOPBACK_STOP |
6-Information |
Ethernet Dataplane Latching Loopback Stop on [chars] |
Dataplane Latching Loopback is de-activated for the specified service |
ethernet-cfm |
"LOG_STD_NO_ACTION" |
|
E_CFM-6-DATAPLANE_LATCHING_LOOPBACK_TIMER_EXPIRED |
6-Information |
Ethernet Dataplane Latching Loopback timer expired on [chars] |
Dataplane Latching Loopback timer is expired for the specified service |
ethernet-cfm |
"LOG_STD_NO_ACTION" |
|
E_CFM-6-DATAPLANE_LATCHING_LOOPBACK_TIMER_RESTARTED |
6-Information |
Ethernet Dataplane Latching Loopback timer restarted on [chars] |
Dataplane Latching Loopback timer is restarted for the specified service |
ethernet-cfm |
"LOG_STD_NO_ACTION" |
|
E_CFM-6-ENTER_AIS |
6-Information |
local mep with mpid [dec] level [dec] [chars] 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 service id. |
ethernet-cfm |
"LOG_STD_NO_ACTION" |
|
E_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" |
|
E_CFM-6-ENTER_LCK |
6-Information |
local mep with mpid [dec] level [dec] [chars] dir [chars] Interface [chars] enters LCK defect condition |
Ethernet cfm mep has entered LCK Maintenance condition. Id refers to local mep service id. |
ethernet-cfm |
"LOG_STD_NO_ACTION" |
|
E_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" |
|
E_CFM-6-EXIT_AIS |
6-Information |
local mep with mpid [dec] level [dec] [chars] 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 service id. |
ethernet-cfm |
"LOG_STD_NO_ACTION" |
|
E_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" |
|
E_CFM-6-EXIT_LCK |
6-Information |
local mep with mpid [dec] level [dec] [chars] dir [chars] Interface [chars] exited LCK defect condition |
Ethernet cfm mep has exited LCK Maintenance condition. Id refers to local mep service id. |
ethernet-cfm |
"LOG_STD_NO_ACTION" |
|
E_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" |
|
E_CFM-6-MAX_MEPS_EXCEEDED |
6-Information |
Maximum MEPs threshold exceeded in [chars] for domain [chars] service [chars] mac [enet] mpid [dec] |
The number of remote MEP entries in CC database has exceeded the maximum MEPs configured. The current remote MEP is not saved in the CC database. |
ethernet-cfm |
"Verify that the correct number for maximum MEPs is specified in the " "configuration. If correct number of maximum MEPs is configured " "verify if any unexpected remote MEP is not part of the service via " "'show ethernet cfm maintenance remote' or 'show ethernet cfm mpdb' " "command" |
|
E_CFM-6-REMOTE_MEP_UP |
6-Information |
Continuity Check message is received from a remote MEP with mpid [dec] [chars] MA name [chars] domain [chars] interface status [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 MA. |
ethernet-cfm |
"Information message only." |
|
E911-3-MISSING_DEFAULT_NUMBER |
3-Error |
It is mandatory to configure an ELIN under 'voice emergency response settings.' |
The administrator has enabled the Enhanced 911 feature without configuring\n\ a default ELIN under 'voice emergency response settings.' |
voice-ivr |
"The administrator should enter the 'voice emergency response settings' \n\ mode and configure a value for the 'elin' CLI." |
|
E911-4-CALLBACK_UNREACHABLE |
4-Warning |
Unable to contact the last emergency caller at [chars]. |
A call has been made to an emergency response number. \n\ This message simply informs system administrators of the call. |
voice-ivr |
"The administrator determines the policy for\n\ outbound emergency calls. The administrator\n\ may set-up an application to page or email\n\ a technician everytime this message is emitted." |
|
EAP-2-PROCESS_ERR |
2-Critical |
[chars] |
This is critical condition where the router could not perform EAP\n\ process related operation. |
eap |
"Reload the device." |
|
EAP-4-BADPKT |
4-Warning |
IP=[inet]| HOST=[chars] |
This messages informs that the router received an invalid or malformed\n\ EAP packet from the specified host. |
eap |
"Check specified host for EAP operation." |
|
EAP-6-MPPE_KEY |
6-Information |
IP=[chars]| MPPE_RECV_KEY_LENGTH=[dec] |
This messages informs that the router received MPPE KEY for the specified\n\ host. |
eap |
"No action is required." |
|
EC-3-BWMISMATCH |
3-Error |
[chars] should be removed from the Port-channel[dec] |
The member-link shouldn't have been part of the port-channel bundle\n\ because the bandwidth of the member-link doesn't match the bandwidth\n\ of the bundle. This configuration shouldn't have been allowed. This error\n\ indicates it was allowed due to some software issue. |
fec |
"Remove the member-link from the port-channel for\n\ proper operation." |
|
EC-5-MINLINKS_MET |
5-Notice |
Port-channel [chars] is up as its bundled ports [dec] meets min-links |
The administrative configuration of minimum links is equal or less than\n\ the number of bundled ports. Therefore this port channel has been\n\ brought up |
fec |
"None." |
|
EC-5-MINLINKS_NOTMET |
5-Notice |
Port-channel [chars] is down bundled ports [dec] doesn't meet min-links |
The administrative configuration of minimum links is greater than the\n\ number of bundled ports. Therefore this port channel has been brought\n\ down |
fec |
"Reduce the min-links configuration for this group\n\ or add more ports to this port-channel to have\n\ them bundle." |
|
ECC-2-MALLOC |
2-Critical |
Attempt to malloc [dec] bytes for the ECC error log failed.\n ECC errors will only be reported and not recorded.\n |
Malloc for the ECC error log failed. A memory upgrade would be advisable or is recommended. |
- |
LOG_STD_ACTION |
|
ECC-3-SBE_HARD |
3-Error |
Single bit *hard* error detected at 0x%08x |
A single-bit uncorrectable error [hard error] was detected on a CPU\n\ read from DRAM. 'show ecc' will dump the Single-bit errors logged thus\n\ far and will also indicate detected hard error address locations. |
- |
"Monitor system through 'show ecc' and replace DRAM if too many\n\ such errors." |
|
ECC-3-SBE_LIMIT |
3-Error |
Single bit error detected and corrected\nat 0x%08x |
A single-bit correctable error was detected on a CPU read from DRAM. |
- |
LOG_STD_ACTION |
|
ECC-3-SBE_RMW_LIMIT |
3-Error |
Single bit error detected and corrected at 0x%08x on a read-modify-write cycle |
A single-bit correctable error was detected on during a read-modify-\n\ write cycle on a CPU read from DRAM for a non 8-byte access.\n\ 'show ecc' can be used to dump Single-bit errors logged thus far. |
- |
LOG_STD_ACTION |
|
ECC-3-SYNDROME_SBE_LIMIT |
3-Error |
8-bit Syndrome for the detected Single-bit error: 0x[hec] |
The 8-bit syndrome for detected single-bit error. This value does not\n\ indicate the exact positions of the bits in error but can be used to\n\ approximate their positions. |
- |
LOG_STD_ACTION |
|
ECFM_HA-2-GET_BUFFER |
2-Critical |
ECFM ISSU client failed to get buffer for message. Error: [dec] [chars] |
The ECFM 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. |
ecfm |
"show logging and show checkpoint client" |
|
ECFM_HA-2-INIT |
2-Critical |
ECFM ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The ECFM 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. |
ecfm |
LOG_STD_ACTION |
|
ECFM_HA-2-SEND_NEGO_FAILED |
2-Critical |
ECFM ISSU client failed to send negotiation message. Error: [dec] [chars] |
The ECFM 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. |
ecfm |
"show logging and show checkpoint client" |
|
ECFM_HA-2-SESSION_NEGO |
2-Critical |
ECFM ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The ECFM 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. |
ecfm |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ECFM_HA-2-SESSION_REGISTRY |
2-Critical |
ECFM ISSU client failed to register session information. Error: [dec] [chars] |
The ECFM ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
ecfm |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ECFM_HA-3-INVALID_SESSION |
3-Error |
ECFM ISSU client does not have a valid registered session. |
The ECFM ISSU client does not have a valid registered session. |
ecfm |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ECFM_HA-3- ISSU |
3-Error |
YO |
Hi |
ecfm |
"Hello " LOG_STD_ACTION |
|
ECFM_HA-3-MSG_NOT_OK |
3-Error |
ECFM ISSU client 'Message Type [dec]' is not compatible |
The ECFM ISSU client received an incompatible message from the peer device. The message cannot be processed. |
ecfm |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
ECFM_HA-3-MSG_SIZE |
3-Error |
ECFM ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The ECFM ISSU client failed to calculate the MTU for the specified message. The ECFM ISSU client will not able to send the message to the standby device. |
ecfm |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
ECFM_HA-3-SESSION_UNREGISTRY |
3-Error |
ECFM ISSU client failed to unregister session information. Error: [dec] [chars] |
The ECFM ISSU client failed to unregister session information. |
ecfm |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ECFM_HA-3-TRANSFORM |
3-Error |
ECFM ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The ECFM 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 ECFM state between the active device and the standby device is not identical. |
ecfm |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
ECFM_HSBY-5-FAIL |
5-Notice |
Communication lost with remote ODU for link protection group [dec] on [chars] |
Communication was lost with the remote outdoor unit ODU due to either a CC message timeout or the interface going down. |
uea-eoam |
LOG_STD_NO_ACTION |
|
ECFM_HSBY-5-FAILOVER |
5-Notice |
Failover from [chars] to [chars] in link protection group [dec]. |
The active outdoor unit ODU in the link protection group either has sent a message to the indoor unit IDU |
uea-eoam |
LOG_STD_NO_ACTION |
|
ECFM_HSBY-5-KO |
5-Notice |
Remote ODU for link protection group [dec] on [chars] has indicated a failure |
The remote outdoor unit ODU has raised its Sender KO flag indicating a failure. |
uea-eoam |
LOG_STD_NO_ACTION |
|
ECFM_HSBY-5-OK |
5-Notice |
Remote ODU for link protection group [dec] on [chars] is now ok. |
The previously failed remote outdoor unit ODU has recovered. |
uea-eoam |
LOG_STD_NO_ACTION |
|
ECFM_HSBY-5-PORT_ACTIVE |
5-Notice |
[chars] link protection group [dec] now forwarding traffic |
The remote outdoor unit ODU connected to this interface is now active. This interface is now forwarding traffic to/from the remote ODU. |
uea-eoam |
LOG_STD_NO_ACTION |
|
ECFM_HSBY-5-SUSPEND |
5-Notice |
Remote ODU for link protection group [dec] on [chars] is now suspended. |
The remote outdoor unit ODU has requested monitoring of CC messages be temporarily suspended. |
uea-eoam |
LOG_STD_NO_ACTION |
|
ECFM_PROXY-2-PROXY_IPC_INIT_FAILED |
2-Critical |
QFP ECFM Proxy IPC interface initialization failure result: [dec]. |
Cisco internal software error. QFP ECFM Proxy initialization detected that the IPC interface initialization failed. QFP ECFM proxy will not be functional while this condition exists. |
asr1k-ecfm keyword:ecfm |
LOG_STD_ACTION |
|
ECFM_PROXY-3-ECFM_MEM_EXTEND_FAILED |
3-Error |
ECFM IPC subtype: [dec] |
Extending memory failed. |
asr1k-ecfm keyword:ecfm |
LOG_STD_ACTION |
|
ECFM_PROXY-3-ECFM_MEM_REQ_FAILED |
3-Error |
ECFM IPC subtype: [dec] |
Requesting more memory failed. |
asr1k-ecfm keyword:ecfm |
LOG_STD_ACTION |
|
ECFM_PROXY-3-PROXY_BAD_MSG |
3-Error |
QFP ECFM Proxy received bad length message type [dec] |
Cisco internal software error. QFP ECFM Proxy received a corrupted message from control plane. This message will be ignored. |
asr1k-ecfm keyword:ecfm |
LOG_STD_ACTION |
|
ECFM_PROXY-3-PROXY_IPC_ALLOC_FAILED |
3-Error |
QFP ECFM Proxy [chars] message lost due to message buffer allocation failure. |
Cisco internal software error. QFP ECFM Proxy message processing detected a message buffer allocation failure. The message is lost as the result of this condition. |
asr1k-ecfm keyword:ecfm |
LOG_STD_ACTION |
|
ECFM_PROXY-3-PROXY_IPC_SEND_FAILED |
3-Error |
QFP ECFM Proxy [chars] message lost due to message sent failure result: [dec]. |
Cisco internal software error. QFP ECFM Proxy message processing detected a message sent failure. The message is lost as the result of this condition. |
asr1k-ecfm keyword:ecfm |
LOG_STD_ACTION |
|
ECFM_PROXY-4-PROXY_INVALID_MSG |
4-Warning |
QFP ECFM Proxy received invalid message type [dec] |
Cisco internal software error. QFP ECFM Proxy received an invalid message from control plane. This message will be ignored. |
asr1k-ecfm keyword:ecfm |
LOG_STD_ACTION |
|
ECFM_PROXY-4-PROXY_INVALID_MSG_LEN |
4-Warning |
QFP ECFM Proxy IPC invalid length [dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Cisco internal software error. QFP ECFM Proxy received invalid IPC message length from control plane. This message will be ignored. |
asr1k-ecfm keyword:ecfm |
LOG_STD_ACTION |
|
ECODE_DOWNLOAD-0-INTERNAL_PANIC |
0-Emergency |
[chars] |
A Panic Condition. |
- |
"" |
|
ECODE_DOWNLOAD-1-INITFAIL |
1-Alert |
msgtxt_initfail |
- |
- |
- |
|
ECODE_DOWNLOAD-1-NOMEMORY |
1-Alert |
msgtxt_nomemory |
- |
- |
- |
|
ECODE_DOWNLOAD-3-INTERNAL_ERROR |
3-Error |
[chars] |
Errors |
- |
"" |
|
ECODE_DOWNLOAD-7-INTERNAL_ASSERT |
7-Debug |
[chars]: [chars] Assertion Failure - File [chars] Line [dec] |
Assertion |
- |
"" |
|
EDSP-4-CEF_TOOLONG |
4-Warning |
CEF to SCCP devices may be disabled! See message below. |
Given up waiting for CEF initialization to complete. |
cme-ephone |
"Check the message about CEF and the EDSP0 interface below. If the" " vector is EVENTUALLY set to Null CEF RTP sending for SCCP devices is" " disabled. You may try to recover by restarting \"ip cef\" in IOS" " configuration." |
|
EDSP-6-CEF_WAIT |
6-Information |
Waiting for CEF initialization to complete first ... [dec] |
Initialization of CEF RTP sending relies on system's CEF readiness. |
cme-ephone |
LOG_STD_NO_ACTION |
|
EDSP-6-IPV6_ENABLED |
6-Information |
IPv6 on interface [chars] added. |
IPv6 capability has been enabled for the sub-interface. |
cme-ephone |
LOG_STD_NO_ACTION |
|
EDSP-6-IPV6_FAILED |
6-Information |
IPv6 on interface [chars] failed. |
IPv6 initialization has failed for the sub-interface. |
cme-ephone |
"Please check IPv6 and interface related configurations." |
|
EDSP-6-VEC_CHANGE |
6-Information |
EDSP0's LES switching vector set to [chars] |
To monitor CEF initialization for the hidden interface. |
cme-ephone |
LOG_STD_NO_ACTION |
|
EHSA-2-EHSALOAD |
2-Critical |
[chars] |
Netbooting was attempted on an EHSA Secondary |
- |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
EHSA-2-EHSASW |
2-Critical |
[chars] |
Primary has crashed or is unresponsive. Secondary is taking over |
- |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
EHSA-3-EHSABADST |
3-Error |
[chars] [[dec]] [[dec]] |
EHSA internal error. |
Determine the component from the stack trace and process name displayed in the error message. Use Topic to search for a similar DDTS. If you find none write a DDTS for this problem. |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
EHSA-3-EHSAINT |
3-Error |
'[chars]' at level [dec] |
EHSA internal error. |
Determine the component from the stack trace and process name displayed in the error message. Use Topic to search for a similar DDTS. If you find none write a DDTS for this problem. If the stack trace indicates that the scheduler was called from an interrupt handler choose the DDTS component based on the interrupt handler. Otherwise use the process name to determine the DDTS component. |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
EHSA-3-IPCERR |
3-Error |
[chars] [[chars]] |
IPC failed for EHSA. EHSA messages cannot be transmitted . |
- |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
EHSA-3-KEEPTO |
3-Error |
No keepalive seen in [[dec]] secs: Failover [chars] |
EHSA keepalive failure. |
- |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
EHSA-3-NOBUF |
3-Error |
[chars] |
The IPC ran out of memory buffers. |
- |
"Reduce the number of applications currently running on the IPC. Copy the error message exactly as it appears and report it to your technical support representative." |
|
EHSA-3-STCHNG |
3-Error |
[chars] [[dec]] |
EHSA State change detected |
- |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
EIO-3- NOCDB |
3-Error |
Unable to create controller cdb. |
failed to create controller cdb. |
- |
LOG_STD_ACTION |
|
EIO-3- NOCHUNK |
3-Error |
Unable to create memory chunk. |
failed to create memory chunk. |
- |
LOG_STD_ACTION |
|
EIO-3- NOMEM |
3-Error |
out of memory. |
failed to malloc memory. |
- |
LOG_STD_ACTION |
|
EIO-3- NOPROC |
3-Error |
Unable to create process. |
failed to create eio process. |
- |
LOG_STD_ACTION |
|
EIO-3- NOQUEUE |
3-Error |
Unable to create queue. |
failed to create queue. |
- |
LOG_STD_ACTION |
|
EIO-4- EMPTY_CHUNK |
4-Warning |
Chunk is empty. |
failed to malloc chunk entry due to empty chunk. |
- |
LOG_STD_ACTION |
|
EIO-4- INVALID_CDB |
4-Warning |
Invalid eio controller cdb. |
encountered an invalid controller cdb. |
- |
LOG_STD_ACTION |
|
EIO-4- INVALID_SLOT |
4-Warning |
Invalid eio slot instance. |
encountered an invalid eio slot instance. |
- |
LOG_STD_ACTION |
|
ELB_HA-2-GET_BUFFER |
2-Critical |
ELB ISSU client failed to get buffer for message. Error: [dec] [chars] |
The ELB 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-oam |
"show logging and show checkpoint client" |
|
ELB_HA-2-INIT |
2-Critical |
ELB ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The ELB 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-oam |
LOG_STD_ACTION |
|
ELB_HA-2-SEND_NEGO_FAILED |
2-Critical |
ELB ISSU client failed to send negotiation message. Error: [dec] [chars] |
The ELB 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-oam |
"show logging and show checkpoint client" |
|
ELB_HA-2-SESSION_NEGO |
2-Critical |
ELB ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The ELB 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-oam |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ELB_HA-2-SESSION_REGISTRY |
2-Critical |
ELB ISSU client failed to register session information. Error: [dec] [chars] |
The ELB 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-oam |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ELB_HA-3-INVALID_SESSION |
3-Error |
ELB ISSU client does not have a valid registered session. |
The ELB ISSU client does not have a valid registered session. |
ethernet-oam |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ELB_HA-3-MSG_SIZE |
3-Error |
ELB ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The ELB ISSU client failed to calculate the MTU for the specified message. The ELB ISSU client will not able to send the message to the standby device. |
ethernet-oam |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
ELB_HA-3-SESSION_UNREGISTRY |
3-Error |
ELB ISSU client failed to unregister session information. Error: [dec] [chars] |
The ELB ISSU client failed to unregister session information. |
ethernet-oam |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ELB_HA-3-TRANSFORM |
3-Error |
ELB ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The ELB 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 ELB state between the active device and the standby device is not identical. |
ethernet-oam |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
ELC_L2_ACL-3-ERRORSW |
3-Error |
[chars] |
The elc l2 acl client detected software error event that is specified in the message |
asr1k-ether-lc |
LOG_STD_SH_TECH_ACTION |
|
ELC_L2_ACL-3-NOMEM |
3-Error |
Memory Allocation Failure - [chars] : [chars]0x[hec] |
Memory required by l2 acl client to service one or more Network Processors could not be allocated. |
asr1k-ether-lc |
"This error may indicate that more memory must be installed on the " "affected card or platform in order to service all the features and " "related entities enabled via the configuration. " LOG_STD_SH_TECH_ACTION |
|
EM_ISSU-2-GET_BUFFER |
2-Critical |
Event Manager ISSU client failed to get buffer for message. Error: [dec] [chars] |
The Event Manager 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. |
em |
"show logging and show checkpoint client" |
|
EM_ISSU-2-INIT |
2-Critical |
Event Manager ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The Event Manager 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. |
em |
LOG_STD_ACTION |
|
EM_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
Event Manager ISSU client failed to send negotiation message. Error: [dec] [chars] |
The Event Manager 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. |
em |
"show logging and show checkpoint client" |
|
EM_ISSU-2-SESSION_NEGO |
2-Critical |
Event Manager ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The Event Manager 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. |
em |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
EM_ISSU-2-SESSION_REGISTRY |
2-Critical |
Event Manager ISSU client failed to register session information. Error: [dec] [chars] |
The Event Manager ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
em |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
EM_ISSU-3-INVALID_SESSION |
3-Error |
Event Manager ISSU client does not have a valid registered session. |
The Event Manager ISSU client does not have a valid registered session. |
em |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
EM_ISSU-3-MSG_NOT_OK |
3-Error |
Event Manager ISSU client 'Message Type [dec]' is not compatible |
The Event Manager ISSU client received an incompatible message from the peer device. The message cannot be processed. |
em |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
EM_ISSU-3-MSG_SIZE |
3-Error |
Event Manager ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The Event Manager ISSU client failed to calculate the MTU for the specified message. The Event Manager ISSU client is not able to send the message to the standby device. |
em |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
EM_ISSU-3-OPAQUE_MSG_NOT_OK |
3-Error |
Event Manager ISSU client 'Opaque Message Type [dec]' is not compatible |
The Event Manager ISSU client received an incompatible message from the peer device. The opaque message cannot be processed. |
em |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
EM_ISSU-3-SESSION_UNREGISTRY |
3-Error |
Event Manager ISSU client failed to unregister session information. Error: [dec] [chars] |
The Event Manager ISSU client failed to unregister session information. |
em |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
EM_ISSU-3-TRANSFORM_FAIL |
3-Error |
Event Manager ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The Event Manager 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 Event Manager state between the active device and the standby device is not identical. |
em |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
EM-3-EXCEED |
3-Error |
EM exceed maximum open events [dec]. |
The total number of open events exceeded the maximum number of possible open events. The maximum number that the EM server permits is specified in the error message. EM clients are either opening too many events or not closing events within the permitted time period. |
- |
show em state | inc <em_type> |
|
EM-3-FAIL |
3-Error |
The specified EM Function failed [chars]. |
The specified EM function failed. This condition might be caused by incorrect logic or a memory corruption. |
- |
"Copy the error message exactly as it appears on the console or " "in the system log. Enter the <CmdBold>show em state<NoCmdBold> " "command or the <CmdBold>show em status<NoCmdBold> command to " "gather data that may help Cisco technical support to identify " "the nature of the error. Contact your Cisco technical support " "representative and provide the representative with the gathered " "information." |
|
EM-3-NOMEM |
3-Error |
The EM failed to allocate memory resources for the specified\nEM \function [chars]. |
A timeout occurred. This condition is minor and should not affect the functionality of the switch. |
- |
"This message should not affect switch functionality but can be " "sign of a software bug condition. Please check Bug Toolkit on " "the Cisco web-site for relevant bugs against this message. If " "you do not find any please contact the TAC with the output of " "<CmdBold>show em client<NoCmdBold>" |
|
EM-3-NULLPTR |
3-Error |
The pointer in a specified EM function [chars] is incorrectly NULL. |
The pointer in the specified EM function is incorrectly NULL. This condition might be caused by incorrect logic or a memory corruption. |
- |
"Copy the error message exactly as it appears on the console or " "in the system log. Enter the <CmdBold>show em state<NoCmdBold> " "command or the <CmdBold>show em status<NoCmdBold> command to " "gather data that may help Cisco technical support to identify " "the nature of the error. Contact your Cisco technical support " "representative and provide the representative with the gathered " "information." |
|
EM-4-INVALID |
4-Warning |
The specified EM function [chars] received Invalid operands <[dec]>. |
The EM client used invalid API parameters. |
- |
"Copy the error message exactly as it appears on the console or " "in the system log. Enter the <CmdBold>show em state<NoCmdBold> " "command or the <CmdBold>show em status<NoCmdBold> command to " "gather data that may help Cisco technical support to identify " "the nature of the error. Contact your Cisco technical support " "representative and provide the representative with the gathered " "information." |
|
EM-4-LIMIT |
4-Warning |
EM exceed open events limit [dec]. |
The EM has exceeded the permitted number of open events. The open event limit is 5000. |
- |
LOG_STD_ACTION |
|
EM-4-NOTUP |
4-Warning |
The EM is not available [chars]. |
The specified EM function could not find the specified open event. This condition might be caused by a memory corruption. |
- |
"Copy the error message exactly as it appears on the console or " "in the system log. Enter the <CmdBold>show em state<NoCmdBold> " "command or the <CmdBold>show em status<NoCmdBold> command to " "gather data that may help Cisco technical support to identify " "the nature of the error. Contact your Cisco technical support " "representative and provide the representative with the gathered " "information." |
|
EM-4-SENDFAILED |
4-Warning |
The specified EM client type=[dec] failed to send messages to standby. |
Because the specified EM client failed to send messages to the standby supervisor engine the standby supervisor engine is not updated. Do not attempt to failover to standby supervisor engine. |
- |
show checkpoint clients |
|
ENSP-1-NOMEMORY |
1-Alert |
msgtxt_nomemory |
The requested operation could not be accomplished because of a low\n\ memory condition. |
- |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
ENSP-2-FMAIL_INTERNAL_ERROR |
2-Critical |
Internal software error |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
ENSP-2-FMAIL_NO_AUTH_STARTED |
2-Critical |
AAA authentication startup failed |
AAA authentication startup failed |
- |
LOG_STD_RECUR_ACTION |
|
ENSP-2-INTERNAL_ERROR |
2-Critical |
FAX- Internal software error: [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
ENSP-4-FMAIL_BAD_MESSAGE |
4-Warning |
FAXMAIL- Bad message received |
An unexpected message was received. |
- |
LOG_STD_RECUR_ACTION |
|
ENSP-4-FMAIL_NO_SMTP |
4-Warning |
FAXMAIL- Can not connect\n\to the SMTP server |
No connection was able to be created to any of the specified\n\SMTP servers. |
- |
LOG_STD_RECUR_ACTION |
|
ENSP-4-FMAIL_NO_SMTP_SEND |
4-Warning |
FAXMAIL- Could not\n\send data to the SMTP server |
A connection was made to the SMTP server but no data can be sent. |
- |
LOG_STD_RECUR_ACTION |
|
ENSP-4-SMTP_NOT_CONNECTED |
4-Warning |
SMTP- failed [chars] [dec] |
A connection attempt to a remote mail server was not successful.\n\ This unexpected behavior. |
- |
LOG_STD_NO_ACTION |
|
ENSP-6-SMTP_OPEN |
6-Information |
SMTP- opening [chars] [dec] |
A connection attempt ... |
- |
LOG_STD_NO_ACTION |
|
ENT_API-3-NOCREAT |
3-Error |
EntityApiProcess not created - Entity MIB will not be \n\ initialised |
Attempt to start EntityApiProcess failed when the entity subsystem \n\ was initialised. The Entity MIB will not be populated. |
snmp |
"The Entity MIB API process was not created possibly due to\n\ lack of memory. If you want to use the Entity MIB API \n\ reconfigure the box so that less memory is used by\n\ other features or add more memory to the system. Reload the box\n\ after reconfiguring." |
|
ENT_API-3-NOPARENTDEL |
3-Error |
Parent physical entity [dec] did not exist when trying to delete\n\ child physical entity [dec] phyDescr = [chars] phyName = [chars]. RootIdx = [dec] |
An attempt to reassign parent's child pointer reference failed during\n\ the node deletion because the node's parent reference is NULL. The node\n\ and all of its sibling nodes and their childeren will be deleted. This\n\ is an unususal scenario and may happen due to any hardware malfunction\n\ such as device flapping. |
snmp |
"Copy the error message exactly as it appears on the console\n\ or in the system log call your Cisco technical support\n\ representative and provide the representative with the\n\ gathered information. Using your NMS tool also provide the\n\ content of the Entity MIB table." |
|
ENT_API-4-MULTIPLEREG |
4-Warning |
Multiple registration request with same entity name = [chars] \n\ using entity index [dec] and phyDescr = [chars]. |
An attempt to register a physical entity happened and failed \n\ because the same entity name is being used for which a registration \n\ has already been done. |
snmp |
"Need to raise a DDTS with the component responsible for the \n\ for the registration to use different entity names for registering \n\ different entities." |
|
ENT_API-4-NOALIAS |
4-Warning |
[chars] entity not found when adding an alias with \n\ physical index = [dec] and logical index = [dec] to the Entity MIB |
An attempt to add an alias entry to the Entity MIB was made.\n\ The logical or physical entity with the specified index does\n\ not exist and so the alias entry creation failed. |
snmp |
"Copy the error message exactly as it appears on the console\n\ or in the system log call your Cisco technical support\n\ representative and provide the representative with the\n\ gathered information. Using your NMS tool also provide the\n\ content of the Entity MIB table." |
|
ENT_API-4-NOENT |
4-Warning |
Trying to add or delete an unknown entity to the Entity MIB |
An attempt to add/delete an unknown entity to the Entity MIB \n\ was made. The request could not be processed. |
snmp |
"Copy the error message exactly as it appears on the console\n\ or in the system log call your Cisco technical support\n\ representative and provide the representative with the\n\ gathered information. Using your NMS tool also provide the\n\ content of the Entity MIB table." |
|
ENT_API-4-NOLPMAP |
4-Warning |
[chars] entity not found when adding an LPMapping entry with \n\ logical index = [dec] and physical index = [dec] to the Entity MIB |
An attempt to add an LPMapping entry to the Entity MIB was made.\n\ The logical or physical entity with the specified index does\n\ not exist and so the LPMapping entry creation failed. |
snmp |
"Copy the error message exactly as it appears on the console\n\ or in the system log call your Cisco technical support\n\ representative and provide the representative with the\n\ gathered information. Using your NMS tool also provide the\n\ content of the Entity MIB table." |
|
ENT_API-4-NOPARENT |
4-Warning |
Parent physical entity [dec] did not exist when trying to add\n\ child physical entity [dec] phyDescr = [chars] phyName = [chars]. |
An attempt to add a physical entity failed because its\n\ parent physical entity did not exist in the entPhysicalTable\n\ of the Entity MIB. |
snmp |
"Copy the error message exactly as it appears on the console\n\ or in the system log call your Cisco technical support\n\ representative and provide the representative with the\n\ gathered information. Using your NMS tool also provide the\n\ content of the Entity MIB table." |
|
ENT_API-4-NOPORT |
4-Warning |
Physical entity does not have a Port PhysicalClass when \n\ adding an alias with physical index = [dec] logical index = [dec]\n\ phyDescr = [chars] phyName = [chars]\n\ phyClass = [dec] phyContainedIn = [dec] to the Entity MIB |
- |
snmp |
"Copy the error message exactly as it appears on the console\n\ or in the system log call your Cisco technical support\n\ representative and provide the representative with the\n\ gathered information. Using your NMS tool also provide the\n\ content of the Entity MIB table." |
|
ENTITY_ALARM-6-INFO |
6-Information |
[chars] [chars] [chars] [chars] [chars] |
Alarm assertion or deassertion information. |
- |
LOG_STD_NO_ACTION |
|
ENTROPY-0-ENTROPY_ERROR |
0-Emergency |
Unable to collect sufficient entropy |
On bootup the device attempts to collect entropy to initialize its random number generator. This device has failed to do so. Because of this most security protocols will not run |
- |
"This is probably a hardware failure" |
|
ENTROPY-0-ENTROPY_FAILURE |
0-Emergency |
Unable to collect sufficient entropy |
On bootup the router attempts to collect entropy to initialize its random number generator. This router has failed to do so. Because of this most security protocols will not run |
- |
"This is probably a hardware failure" |
|
ENTRY_MOVE_FAILED-3-MPLS_TE_HA |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
ENVIRONMENT-2-FAN_FAULT |
2-Critical |
System Fault: FAN FAULT is detected. |
- |
- |
- |
|
ENVIRONMENT-2-PS_A_HIGHVOLTAGE |
2-Critical |
[chars] [chars] [chars] [chars] |
Power supply input voltage exceeding threshold |
cgs2520 |
"Please save system configuration and power down system" "to prevent damage causes by over voltage." |
|
ENVIRONMENT-2-PS_A_LOWVOLTAGE |
2-Critical |
[chars] [chars] [chars] [chars] |
Power supply input voltage is below low threshold |
cgs2520 |
"Please save system configuration and power down system" "to prevent damage causes by low voltage." |
|
ENVIRONMENT-2-PS_B_HIGHVOLTAGE |
2-Critical |
[chars] [chars] [chars] [chars] |
Power supply input voltage exceeding threshold |
cgs2520 |
"Please save system configuration and power down system" "to prevent damage causes by over voltage." |
|
ENVIRONMENT-2-PS_B_LOWVOLTAGE |
2-Critical |
[chars] [chars] [chars] [chars] |
Power supply input voltage is below low threshold |
cgs2520 |
"Please save system configuration and power down system" "to prevent damage causes by low voltage." |
|
ENVIRONMENT-3-AC1_TRIGGER |
3-Error |
[chars] [chars] [chars] [chars] |
External Alarm Contact 1 triggered |
- |
- |
|
ENVIRONMENT-3-AC1_TRIGGER |
3-Error |
[chars] [chars] [chars] [chars] |
External Alarm Contact 1 triggered |
- |
- |
|
ENVIRONMENT-3-AC2_TRIGGER |
3-Error |
[chars] [chars] [chars] [chars] |
External Alarm Contact 2 triggered |
- |
- |
|
ENVIRONMENT-3-AC2_TRIGGER |
3-Error |
[chars] [chars] [chars] [chars] |
External Alarm Contact 2 triggered |
- |
- |
|
ENVIRONMENT-3-AC3_TRIGGER |
3-Error |
[chars] [chars] [chars] [chars] |
External Alarm Contact 3 triggered |
- |
- |
|
ENVIRONMENT-3-AC3_TRIGGER |
3-Error |
[chars] [chars] [chars] [chars] |
External Alarm Contact 3 triggered |
- |
- |
|
ENVIRONMENT-3-AC4_TRIGGER |
3-Error |
[chars] [chars] [chars] [chars] |
External Alarm Contact 4 triggered |
- |
- |
|
ENVIRONMENT-3-AC4_TRIGGER |
3-Error |
[chars] [chars] [chars] [chars] |
External Alarm Contact 4 triggered |
- |
- |
|
ENVIRONMENT-3-LIC_FILE_CORRUPT |
3-Error |
[chars] [chars] [chars] [chars] |
License file is corrupted |
- |
- |
|
ENVIRONMENT-3-LIC_FILE_CORRUPT |
3-Error |
[chars] [chars] [chars] [chars] |
License file is corrupted |
- |
- |
|
ENVIRONMENT-3-OVERTEMP |
3-Error |
[chars] [chars] [chars] [chars] |
The chassis inside temperature exceeds the max temperature threshold |
- |
- |
|
ENVIRONMENT-3-OVERTEMP |
3-Error |
[chars] [chars] [chars] [chars] |
The chassis inside temperature exceeds the max temperature threshold |
- |
- |
|
ENVIRONMENT-3-OVERTEMP |
3-Error |
[chars] [chars] [chars] [chars] |
The chassis inside temperature exceeds the max temperature threshold |
- |
- |
|
ENVIRONMENT-3-OVERTEMP |
3-Error |
[chars] [chars] [chars] [chars] |
The chassis inside temperature exceeds the max temperature threshold |
- |
- |
|
ENVIRONMENT-3-OVERVOLT |
3-Error |
[chars] [chars] [chars] [dec] |
The voltage rail is above the max voltage threshold |
- |
- |
|
ENVIRONMENT-3-POWER_ERROR |
3-Error |
[chars] |
Power supply error. |
- |
" Make sure that the power supply connected are supported." " If the problem still persists then please contact TAC." |
|
ENVIRONMENT-3-POWER_ERROR |
3-Error |
[chars] |
Power supply error. |
- |
" Make sure that the power supply connected are supported." " If the problem still persists then please contact TAC." |
|
ENVIRONMENT-3-RPS_FAILED |
3-Error |
[chars] [chars] [chars] [chars] |
Only one power supply was detected for system in dual power mode or\n\ power supply is failing |
- |
- |
|
ENVIRONMENT-3-RPS_FAILED |
3-Error |
[chars] [chars] [chars] [chars] |
Only one power supply was detected for system in dual power mode or\n\ power supply is failing |
- |
- |
|
ENVIRONMENT-3-RPS_FAILED |
3-Error |
[chars] [chars] [chars] [chars] |
Only one power supply was detected for system in dual power mode or power supply is failing |
- |
- |
|
ENVIRONMENT-3-RPS_FAILED |
3-Error |
[chars] [chars] [chars] [chars] |
Only one power supply was detected for system in dual power mode or \ power supply is failing |
- |
- |
|
ENVIRONMENT-3-SD_CARD |
3-Error |
[chars] [chars] [chars] [chars] |
SD card is not present |
- |
- |
|
ENVIRONMENT-3-SD_CARD |
3-Error |
[chars] [chars] [chars] [chars] |
SD card is not present |
- |
- |
|
ENVIRONMENT-3-SD_CARD_BOOTFLASH |
3-Error |
[chars] [chars] [chars] [chars] |
SD card is not present. Image booted from on-board flash. |
- |
- |
|
ENVIRONMENT-3-SD_CARD_BOOTFLASH |
3-Error |
[chars] [chars] [chars] [chars] |
SD card is not present. Image booted from on-board flash. |
- |
- |
|
ENVIRONMENT-3-SD_CARD_CORRUPT |
3-Error |
[chars] [chars] [chars] [chars] |
SD card is corrupted |
- |
- |
|
ENVIRONMENT-3-SD_CARD_CORRUPT |
3-Error |
[chars] [chars] [chars] [chars] |
SD card is corrupted |
- |
- |
|
ENVIRONMENT-3-SD_CARD_CORRUPT_BOOTFLASH |
3-Error |
[chars] [chars] [chars] [chars] |
SD card is corrupted. Image booted from on-board flash. |
- |
- |
|
ENVIRONMENT-3-SD_CARD_CORRUPT_BOOTFLASH |
3-Error |
[chars] [chars] [chars] [chars] |
SD card is corrupted. Image booted from on-board flash. |
- |
- |
|
ENVIRONMENT-3-SD_CARD_FILES_CORRUPT |
3-Error |
[chars] [chars] [chars] [chars] |
Image File on SD card is corrupted |
- |
- |
|
ENVIRONMENT-3-SD_CARD_FILES_CORRUPT |
3-Error |
[chars] [chars] [chars] [chars] |
Image File on SD card is corrupted |
- |
- |
|
ENVIRONMENT-3-SD_CARD_FILES_CORRUPT_BOOTFLASH |
3-Error |
[chars] [chars] [chars] [chars] |
Image File on SD card is corrupted. Image booted from on-board flash. |
- |
- |
|
ENVIRONMENT-3-SD_CARD_FILES_CORRUPT_BOOTFLASH |
3-Error |
[chars] [chars] [chars] [chars] |
Image File on SD card is corrupted. Image booted from on-board flash. |
- |
- |
|
ENVIRONMENT-3-SD_CARD_UNSUPPORTED |
3-Error |
[chars] [chars] [chars] [chars] |
SD card is not supported |
- |
- |
|
ENVIRONMENT-3-SD_CARD_UNSUPPORTED |
3-Error |
[chars] [chars] [chars] [chars] |
SD card is not supported |
- |
- |
|
ENVIRONMENT-3-SD_CARD_UNSUPPORTED_BOOTFLASH |
3-Error |
[chars] [chars] [chars] [chars] |
SD card is not supported. Image booted from on-board flash. |
- |
- |
|
ENVIRONMENT-3-SD_CARD_UNSUPPORTED_BOOTFLASH |
3-Error |
[chars] [chars] [chars] [chars] |
SD card is not supported. Image booted from on-board flash. |
- |
- |
|
ENVIRONMENT-3-UNDERTEMP |
3-Error |
[chars] [chars] [chars] [chars] |
The chassis inside temperature is below the min temperature threshold |
- |
- |
|
ENVIRONMENT-3-UNDERTEMP |
3-Error |
[chars] [chars] [chars] [chars] |
The chassis inside temperature is below the min temperature threshold |
- |
- |
|
ENVIRONMENT-3-UNDERTEMP |
3-Error |
[chars] [chars] [chars] [chars] |
The chassis inside temperature is below the min temperature threshold |
- |
- |
|
ENVIRONMENT-3-UNDERTEMP |
3-Error |
[chars] [chars] [chars] [chars] |
The chassis inside temperature is below the min temperature threshold |
- |
- |
|
ENVIRONMENT-3-UNDERVOLT |
3-Error |
[chars] [chars] [chars] [dec] |
The voltage rail is below the min voltage threshold |
- |
- |
|
ENVIRONMENT-4-CONFIG_OVERTEMP |
4-Warning |
[chars] [chars] [chars] [chars] |
The chassis inside temperature exceeds the configured threshold but less or equal to the max inside temperature |
- |
- |
|
ENVIRONMENT-4-SECONDARY_OVERTEMP |
4-Warning |
[chars] [chars] [chars] [chars] |
The chassis inside temperature exceeds the configured threshold\n\ but less or equal to the max inside temperature |
- |
- |
|
ENVIRONMENT-4-SECONDARY_OVERTEMP |
4-Warning |
[chars] [chars] [chars] [chars] |
The chassis inside temperature exceeds the configured threshold\n\ but less or equal to the max inside temperature |
- |
- |
|
ENVIRONMENT-4-SECONDARY_OVERTEMP |
4-Warning |
[chars] [chars] [chars] [chars] |
The chassis inside temperature exceeds the configured threshold \ but less or equal to the max inside temperature |
- |
- |
|
ENVIRONMENT-4-SECONDARY_OVERVOLT |
4-Warning |
[chars] [chars] [chars] [dec] |
The voltage rail returns to normal range from above max voltage threshold |
- |
- |
|
ENVIRONMENT-4-SECONDARY_UNDERTEMP |
4-Warning |
[chars] [chars] [chars] [chars] |
The chassis inside temperature is below the configured min temperature \n\ threshold but less or equal to the max inside temperature |
- |
- |
|
ENVIRONMENT-4-SECONDARY_UNDERTEMP |
4-Warning |
[chars] [chars] [chars] [chars] |
The chassis inside temperature is below the configured min temperature \n\ threshold but less or equal to the max inside temperature |
- |
- |
|
ENVIRONMENT-4-SECONDARY_UNDERTEMP |
4-Warning |
[chars] [chars] [chars] [chars] |
The chassis inside temperature is below the configured min temperature \ threshold but less or equal to the max inside temperature |
- |
- |
|
ENVIRONMENT-4-SECONDARY_UNDERVOLT |
4-Warning |
[chars] [chars] [chars] [dec] |
The voltage rail returns to normal range from below low voltage threshold |
- |
- |
|
ENVIRONMENTAL-1-ALERT |
1-Alert |
[chars] Location: [chars] State: [chars] Reading: [dec] [chars] |
One of the sensors in the system is reading an out of normal\n\ value. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
ENVIRONMENTAL-1-SENSORFAIL |
1-Alert |
[chars] Location [chars] State: fail |
One of the sensors in the system has detected a failure condition\n\ from which it can not recover. This sensor is no longer reporting\n\ readings to the environmental monitoring subsystem. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
ENVIRONMENTAL-3-ALERT |
3-Error |
Critical limit reached for PVT temperature sensor on Asic: [dec] Reading: [dec] Celsius |
Informational message for relating to Asic PVT sensor value |
asr900-system-rsp3 |
"No action required" |
|
ENVIRONMENTAL-3-CHASFSERR |
3-Error |
Sensor [chars] on FRU [chars] has an invalid chasfs device state [chars] |
The system does not understand the state that the sensor is \n\ reporting. This is most likely a filesystem corruption or\n\ ISSU problem. You may try rebooting the router to see if the\n\ problem corrects itself. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
ENVIRONMENTAL-3-TDLERROR |
3-Error |
Error processing TDL message. [dec] |
An unexpected condition in which IOS has received a TDL\n\ message which it can not process. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
ENVIRONMENTAL-5-SENSOROK |
5-Notice |
[chars] Location: [chars] State: normal |
One of the sensors in the system had been in a failure condition\n\ but is now operating normally. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
ENVIRONMENTAL-6-INFO |
6-Information |
[chars] |
Informational message of ambient sensor reading |
iosxe-chassismgr |
LOG_STD_ACTION |
|
ENVIRONMENTAL-6-NOTICE |
6-Information |
[chars] Location: [chars] State: [chars] Reading: [dec] [chars] |
Informational message on the sensor reading |
iosxe-chassismgr |
LOG_STD_ACTION |
|
ENVM-0-SHUT |
0-Emergency |
Environmental Monitor initiated shutdown |
The enviromental monitor has initiated a system shutdown. |
- |
"Look at previous environmental messages to determine cause of \n\ shutdown and correct if possible. " LOG_STD_ACTION |
|
ENVM-2-ENVCRIT |
2-Critical |
[chars] measured at [chars] |
One of the measured environmental test points exceeds an extreme \n\ threshold. |
- |
"Correct the specified condition or the system may shut itself down\n\ as a preventive measure.\n\ This condition could cause the system to fail to operate properly. " LOG_STD_RECUR_ACTION |
|
ENVM-3-BLOWER |
3-Error |
[chars] may have failed |
One of the router's cooling fans may be close to failure. |
- |
"Replace the fan as soon as possible or the system may shut itself \n\ down or fail to operate properly." |
|
ENVM-3-LASTENV |
3-Error |
[chars] |
Non volatile EEPROM storage of environmental statistics failed.\n\ This may be due to an EEPROM hardware failure. |
- |
LOG_STD_ACTION |
|
ENVM-3-NOACK |
3-Error |
Access to [chars] failed |
One of the temperature sensors was not ready for \n\ the initiation of temperature environmental monitoring.\n\ Software is attempting to restart the sensor. |
- |
LOG_STD_RECUR_ACTION |
|
ENVM-3-NOFORK |
3-Error |
Could not create environmental polling process |
- |
- |
"" |
|
ENVM-3-NOFORK |
3-Error |
Could not start environment polling process |
The software could not spawn the enviromental monitoring\n\ process possibly because of low memory - no monitoring\n\ will be performed. |
- |
LOG_STD_REDUCE_ACTION |
|
ENVM-4-ENVWARN |
4-Warning |
[chars] measured at [chars] |
One of the measured environmental test points exceeds the warning \n\ threshold. |
- |
"Closely monitor the condition and correct if possible. " LOG_STD_RECUR_ACTION |
|
ENVM-4-LONGBUSYREAD |
4-Warning |
C2W Interface busy for long time reading temperature sensor [dec] |
- |
- |
"" |
|
ENVM-4-LONGBUSYWRITE |
4-Warning |
C2W Interface busy for long time writing temperature sensor [dec] |
- |
- |
"" |
|
ENVM-4-READERROR |
4-Warning |
Error reading temperature sensor [dec] |
- |
- |
"" |
|
ENVM-4-WRITEERROR |
4-Warning |
Error writing temperature sensor [dec] |
- |
- |
"" |
|
ENVM-6-PSCHANGE |
6-Information |
[chars] changed from [chars] to [chars] |
This message indicates the absence or detection\n\ of a new type of power supply in the system.\n\ This can be expected when hot-swapable power supplies are swapped.\n\ This is an informational message only. |
- |
LOG_STD_NO_ACTION |
|
ENVM-6-PSLEV |
6-Information |
[chars] state changed from [chars] to [chars] |
One of the power supply test points underwent a state change. |
- |
"Closely monitor the condition and correct if possible. " LOG_STD_RECUR_ACTION |
|
ENVMON-1-CPU_CRITICAL_UNDERTEMP |
1-Alert |
Critical Warning: CPU temperature [dec]C is below [dec]C threshold. Please resolve operating environment temperature to prevent system damage. |
System CPU temperature is below the threshold |
cgs2520 |
"Please save system configuration and power down system " "to prevent damage causes by operational environment or faulty components." LOG_STD_ACTION |
|
ENVMON-1-CPU_WARNING_OVERTEMP |
1-Alert |
Warning: CPU temperature [dec]C exceeds threshold [dec]C. Please resolve system cooling immediately to prevent system damage |
System CPU temperature is over the threshold |
cgs2520 |
"Please save system configuration and power down system" "to prevent damage causes by over heating." LOG_STD_ACTION |
|
ENVMON-1-CPU_WARNING_OVERTEMP_HDD |
1-Alert |
Warning: CPU temperature [dec]C exceeds threshold [dec]C. [chars] hard disk drive may become unusable if continuously operated at this temperature. Please resolve system cooling immediately to prevent system damage |
System CPU temperature is over the threshold |
cgs2520 |
"Please save system configuration and power down system" "to prevent damage causes by over heating." LOG_STD_ACTION |
|
ENVMON-1-NO_PROCESS |
1-Alert |
Failed to create environmental monitor process |
Failed to create environmental monitor process. |
cgs2520 |
"The amount of memory available in the router may not be sufficient. " LOG_STD_ACTION |
|
ENVMON-1-POWER_HIGH_VOLTAGE |
1-Alert |
Critical Warning: PSU[dec] Input Voltage [dec]V exceeds high threshold [dec]V. The system may not continue operation. Immediate operator action is required. |
Power supply input voltage exceeding threshold |
cgs2520 |
"Please save system configuration and power down system" "to prevent damage causes by over voltage." LOG_STD_ACTION |
|
ENVMON-1-POWER_LOW_VOLTAGE |
1-Alert |
Critical Warning: PSU[dec] Input Voltage [dec]V is below low threshold [dec]V. The system may not continue operation. Immediate operator action is required. |
Power supply input voltage is below low threshold |
cgs2520 |
"Please save system configuration and power down system" "to prevent damage causes by low voltage." LOG_STD_ACTION |
|
ENVMON-1-POWER_WARNING |
1-Alert |
: [chars] |
An error has occured in the power supply. |
cgs2520 |
"Make sure that the power supply is connected to input source." "Also check if the Power Supply Unit and Redundant Power Supply" "are supported by this router." "If the problem still persists then please contact TAC." |
|
ENVMON-1-RPS_ACCESS |
1-Alert |
[chars] |
RPS communication error detected |
cgs2520 |
LOG_STD_ACTION |
|
ENVMON-1-RPS_FAN_FAILED |
1-Alert |
[chars] |
RPS fan failure detected |
rps |
"Disconnect any routers or switches connected " "to the RPS and replace the fan immediately" |
|
ENVMON-1-RPS_OVER_CURRENT |
1-Alert |
[chars] |
RPS overcurrent condition detected |
rps |
"Unplug the routers or switches that are being " "backed off" |
|
ENVMON-1-RPS_PS_MISMATCH |
1-Alert |
[chars] |
Power supplies inserted in RPS are incompatible |
cgs2520 |
"Remove either one of the power supplies or " "insert compatible power supplies" |
|
ENVMON-1-RPS_THERMAL_CRITICAL |
1-Alert |
RPS temperature has reached critical threshold |
The temperature sensor value inside RPS has reached the critical threshold. RPS cannot function normally |
rps |
"The external temperature is very high." " Reduce the temperature in the room immediately" |
|
ENVMON-1-RPS_WARNING |
1-Alert |
: [chars] |
RPS related event notification. |
cgs2520 |
"Make sure that the correct RPS with supported FRUs is connected" " to the router. Check if RPS FRUs are connnected to the power source." "Please refer to technical document or contact TAC for" " further clarification." |
|
ENVMON-1-WARN_DOWN_REV_ROMMON |
1-Alert |
Warning: Router's ROMMON needs to be upgraded to suppport proper operation of module [chars]. Operation [chars] without upgrading ROMMON may cause the module hard disk driver to become unstable. |
This router's ROMMON is down-rev and there is a module with hard disk drives installed in the system. Warn user about upgrading ROMMON. |
c3900 |
"Upgrade ROMMON" |
|
ENVMON-1-WARN_HDD_FAN_HIGH |
1-Alert |
Warning: system temperature [dec] C is high |
Fan speed has reached level3 or above and there is a service module with hard disk drives installed in the system. Warn user about hard disks. |
c3900 |
"Resolve environmental alarm or shutdown the service module." |
|
ENVMON-1-WARN_HDD_HIGH_TEMP |
1-Alert |
Critical Warning: sensor temperature [dec] C exceeds 40 C. |
Ambient temperature exceeds 40 C and there is a service module with hard disk drives installed in the system. Warn user about hard disks. |
c3900 |
"Cool down room temperature or increase air flow to the router." |
|
ENVMON-2-CPU_CRITICAL_OVERTEMP |
2-Critical |
Critical: CPU temperature [dec]C exceeds [dec]C threshold. Please resolve system cooling immediately to prevent system damage. |
System CPU temperature is over the threshold |
cgs2520 |
"Please save system configuration and power down system " "to prevent damage causes by over heating." LOG_STD_ACTION |
|
ENVMON-2-CPU_CRITICAL_OVERTEMP_HDD |
2-Critical |
Critical: CPU temperature [dec]C exceeds [dec]C threshold. [chars] hard disk drive may become unusable if continuously operated at this temperature. Please resolve system cooling immediately to prevent system damage. |
System CPU temperature is over the threshold |
cgs2520 |
"Please save system configuration and power down system " "to prevent damage causes by over heating." LOG_STD_ACTION |
|
ENVMON-2-FAN_TRAY_MISSING |
2-Critical |
Critical Warning: Fan tray was removed. Please re-insert fan tray to prevent system from overheating. |
The environmental monitor can not detect fan tray on system chassis. |
cgs2520 |
"Make sure the fan tray is properly inserted. " "If the problem persists replacement of fan tray is necessary " |
|
ENVMON-2-IN_OUTLET_OVERTEMP |
2-Critical |
Warning: [chars] Temperature [dec]C Exceeds [dec]C. Please resolve system cooling to prevent system damage. |
Temperature sensor exceed overtemp threshold. |
cgs2520 |
"Please resolve system cooling or and power down system" "to prevent damage causes by over heating." LOG_STD_ACTION |
|
ENVMON-2-IN_OUTLET_OVERTEMP_HDD |
2-Critical |
Warning: [chars] Temperature [dec]C Exceeds [dec]C. [chars] hard disk drive may become unusable if continuously operated at this temperature. Please resolve system cooling to prevent system damage. |
Temperature sensor exceed overtemp threshold. |
cgs2520 |
"Please resolve system cooling or and power down system" "to prevent damage causes by over heating." LOG_STD_ACTION |
|
ENVMON-2-MODULE_OVERTEMP |
2-Critical |
Warning: [chars] Temperature [dec]C Exceeds [dec]C. Please resolve system heating to prevent system damage. |
Temperature measured by sensor exceeds high temperature threshold. |
cgs2520 |
"Please resolve system heating or and power down system" "to prevent damage causes by over heating." LOG_STD_ACTION |
|
ENVMON-2-ONBOARD_OVERTEMP |
2-Critical |
Warning: [chars] Temperature [dec]C Exceeds [dec]C. Please resolve system heating to prevent system damage. |
Temperature measured by sensor exceeds high temperature threshold. |
cgs2520 |
"Please resolve system heating or and power down system" "to prevent damage causes by over heating." LOG_STD_ACTION |
|
ENVMON-2-POWER_OVERTEMP |
2-Critical |
Warning: [chars] temperature [dec]C exceeds threshold [dec]C. Please resolve system cooling to prevent system damage |
Power supply temperature exceeding threshold |
cgs2520 |
"Please save system configuration and power down system" "to prevent damage causes by over heating." LOG_STD_ACTION |
|
ENVMON-2-POWER_OVERTEMP_SHUTDOWN |
2-Critical |
Crital Warning: [chars] temperature [dec]C exceeds threshold [dec]C. The power supply will shutdown automatically if the hight temperature condition is not resolved. |
Power supply temperature exceeding critial temperature threshold |
cgs2520 |
"Please save system configuration and power down system" "to prevent damage causes by over heating." LOG_STD_ACTION |
|
ENVMON-2-RPS_THERMAL_WARNING |
2-Critical |
RPS temperature has reached warning threshold |
The temperature sensor value inside RPS has reached the warning threshold. RPS can function normally until the temperature reaches the critical threshold |
rps |
"The external temperature is high." " Reduce the temperature in the room" |
|
ENVMON-2-SYSTEM_FAN_FAILED |
2-Critical |
Critical Warning: System Fan has failed. Please replace the fan to prevent system overheating. |
System fan is not rotating. |
cgs2520 |
"Make sure the fan power cable is properly attached to " "the mainboard fan power connector. If problem persists " "system fan may need to be replace." |
|
ENVMON-3-INTAKE_ABNORMTEMP |
3-Error |
Warning: [chars] Temperature [dec]C Exceeds [dec]C. Please resolve system cooling. |
Temperature sensor exceed abnormal temp threshold. |
cgs2520 |
"Please resolve system cooling or and power down system" "to prevent damage causes by over heating." LOG_STD_ACTION |
|
ENVMON-3-INTAKE_ABNORMTEMP_HDD |
3-Error |
Warning: [chars] Temperature [dec]C Exceeds [dec]C. [chars] hard disk drive may become unusable if continuously operated at this temperature. Please resolve system cooling. |
Temperature sensor exceed abnormal temp threshold. |
cgs2520 |
"Please resolve system cooling or and power down system" "to prevent damage causes by over heating." LOG_STD_ACTION |
|
ENVMON-3-POWER_ERROR |
3-Error |
: [chars] |
Power supply error. |
cgs2520 |
" Make sure that the power supply connected are supported." " If the problem still persists then please contact TAC." |
|
ENVMON-3-RPS_POST_FAILED |
3-Error |
[chars] |
RPS POST failure detected |
rps |
"LOG_STD_NO_ACTION" |
|
ENVMON-3-XFR_ENV_INIT_ERROR |
3-Error |
Fails to initialize MCU Environmental Control Unit |
Attempt to initialize MCU Environmentcal Control Unit fails |
xformers |
LOG_STD_ACTION |
|
ENVMON-4-MULTI_FAN_LOW_RPM |
4-Warning |
Critical Warning: More than two fans are running at low RPM. Rotation speed is now high for all other fans. Please replace fan tray to prevent system from overheating. |
Multiple fan failures detected. |
cgs2520 |
"Make sure the fan power cable is properly attached to " "the mainboard fan tray power connector. If problem persists " "Please replace fan tray." |
|
ENVMON-4-MULTI_FAN_LOW_RPM_HDD |
4-Warning |
Critical Warning: More than two fans are running at low RPM. Rotation speed is now high for all other fans. [chars] hard disk drive may become unusable if continuously operated at this temperature. Please replace fan tray to prevent system from overheating. |
Multiple fan failures detected. |
cgs2520 |
"Make sure the fan power cable is properly attached to " "the mainboard fan tray power connector. If problem persists " "Please replace fan tray." |
|
ENVMON-4-ONE_FAN_LOW_RPM |
4-Warning |
Warning: Fan [dec] is running at low RPM. Rotation speed is now high for all other fans. Fan Tray replacement is recommended. |
One of the fan is not rotating. |
cgs2520 |
"Make sure the fan power cable is properly attached to " "the mainboard fan power connector. If problem persists " "Pease replace system fan tray." |
|
ENVMON-4-ONE_FAN_LOW_RPM_HDD |
4-Warning |
Warning: Fan [dec] is running at low RPM. Rotation speed is now high for all other fans. [chars] hard disk drive may become unusable if continuously operated at this temperature. Fan Tray replacement is recommended. |
One of the fan is not rotating. |
cgs2520 |
"Make sure the fan power cable is properly attached to " "the mainboard fan power connector. If problem persists " "Pease replace system fan tray." |
|
ENVMON-4-TWO_FAN_LOW_RPM |
4-Warning |
Warning: Two fans are running at low RPM. Rotation speed is now high for all other fans. Fan tray replacement is recommended. |
Two fan failures detected. |
cgs2520 |
"Make sure the fan power cable is properly attached to " "the mainboard fan tray power connector. If problem persists " "Please replace fan tray." |
|
ENVMON-4-TWO_FAN_LOW_RPM_HDD |
4-Warning |
Warning: Two fans are running at low RPM. Rotation speed is now high for all other fans. [chars] hard disk drive may become unusable if continuously operated at this temperature. Fan tray replacement is recommended. |
Two fan failures detected. |
cgs2520 |
"Make sure the fan power cable is properly attached to " "the mainboard fan tray power connector. If problem persists " "Please replace fan tray." |
|
ENVMON-5-POWER_NOTICE |
5-Notice |
: [chars] |
Power supply notice. |
cgs2520 |
" This is an informational message only. No action is required." |
|
ENVMON-6-CPU_TEMP_OK |
6-Information |
CPU temperature normal |
The CPU is operating at a normal temperature. |
cgs2520 |
"The CPU previously detected an over-temperature condition " "which has now cleared. This is most likely due to high ambient " "temperature where the router is located." |
|
ENVMON-6-FAN_OK |
6-Information |
Fan [dec] is functioning normal now |
Previously failed fan is functioning normal now. |
cgs2520 |
"No action is required." |
|
ENVMON-6-FAN_TRAY_OK |
6-Information |
Fan tray is detected. |
Fan tray previously reported as missing but it is now installed |
cgs2520 |
"This is an informational error. No action is required." |
|
ENVMON-6-IN_OUTLET_TEMP_OK |
6-Information |
[chars] temperature normal |
The inlet/outlet sensor is operating at a normal temperature. |
cgs2520 |
"The in/outlet sensor previously detected an over-temperature condition " "which has now cleared. This is most likely due to high ambient " "temperature where the router is located." |
|
ENVMON-6-MODULE_TEMP_OK |
6-Information |
[chars] temperature normal |
The module card is operating at a normal temperature. |
cgs2520 |
"The module card previously detected an over-temperature" "condition which has now cleared. This is most likely due to" "high ambient temperature where the router is located." |
|
ENVMON-6-ONBOARD_TEMP_OK |
6-Information |
[chars] temperature normal |
The riser/ddr2/sfp sensors are operating at a normal temperature. |
cgs2520 |
"The riser/ddr2/sfp sensors previously detected an over-temperature" "condition which has now cleared. This is most likely due to" "high ambient temperature where the router is located." |
|
ENVMON-6-POWER_EXTILP |
6-Information |
: [chars] |
External Inline Power supply info. |
c1900 |
" Make sure that the power supply connected is supported." " If the problem still persists then please contact TAC." |
|
ENVMON-6-POWER_TEMP_OK |
6-Information |
[chars] temperature normal |
The Power Supply Unit is operating at a normal temperature. |
cgs2520 |
"The Power Supply Unit was in over-temperature level " "It is now at normal level" |
|
ENVMON-6-POWER_VOLTAGE_OK |
6-Information |
PSU[dec] input voltage is normal |
The Power Supply Unit input voltage is within normal limit. |
cgs2520 |
"The Power Supply Unit input voltage was not within threshold limits " "It is now at normal level" |
|
ENVMON-6-SYSTEM_FAN_OK |
6-Information |
Fan [dec] Functional now |
Sytem fan is functioning normal now. |
cgs2520 |
"No action is required." |
|
EPAMCM-0-INTERNAL_PANIC |
0-Emergency |
[chars] |
A Panic Condition. |
- |
"" |
|
EPAMCM-1-INITFAIL |
1-Alert |
msgtxt_initfail |
- |
- |
- |
|
EPAMCM-1-NOMEMORY |
1-Alert |
msgtxt_nomemory |
- |
- |
- |
|
EPAMCM-3-INTERNAL_ERROR |
3-Error |
[chars] |
Errors |
- |
"" |
|
EPAMCM-7-INTERNAL_ASSERT |
7-Debug |
[chars]: [chars] Assertion Failure - File [chars] Line [dec] |
Assertion |
- |
"" |
|
EPBR_PROXY-2-EPBR_MSG_PROXYINIT_FAILURE |
2-Critical |
EPBR - Failed to register IPC message handler result code [dec] |
QFP EPBR feature failed to register an IPC message handler for communication with control plane. This will cause the featue not to function. |
EPBR_COMP_NAME |
LOG_STD_ACTION |
|
EPBR_PROXY-3-EPBR_MSG_PROXY_ALLOC_FAILURE |
3-Error |
EPBR - Failed to get [dec] bytes space for IPC reply message |
QFP ET-Anallytics feature detected buffer allocation failure while sending reply to a message from another layer of EPBR feature's software stack. |
EPBR_COMP_NAME |
LOG_STD_ACTION |
|
EPBR_PROXY-3-EPBR_MSG_PROXY_DEBUG_REG_FAILED |
3-Error |
- |
EPBR Conditional Debugging Registration failed. |
EPBR_COMP_NAME |
LOG_STD_ACTION |
|
EPBR_PROXY-3-EPBR_MSG_PROXY_INVALID_MSGLEN |
3-Error |
EPBR - Received an invalid length IPC message |
QFP EPBR feature received an incorrect length of IPC message from anoter layer of EPBR feature's software stack m_enum [dec] m_subtype [dec] m_len [dec] m_flags 0x[hec] m_source [dec]. |
EPBR_COMP_NAME |
LOG_STD_ACTION |
|
EPBR_PROXY-3-EPBR_MSG_PROXY_IPCSEND_FAIL |
3-Error |
EPBR - Failed to send IPC message result code [dec] |
QFP EPBR feature failed to send IPC message to another layer of EPBR feature's software stack. |
EPBR_COMP_NAME |
LOG_STD_ACTION |
|
EPBR_PROXY-3-EPBR_MSG_PROXY_OPENREPLY_FAIL |
3-Error |
EPBR - Failed to open reply message part of IPC packet |
QFP EPBR feature failed to open message part of IPC packet while sending a reply to another layer of EPBR feature's software stack. |
EPBR_COMP_NAME |
LOG_STD_ACTION |
|
EPBR_PROXY-3-EPBR_MSG_PROXY_UNKNOWN_IPCMSG |
3-Error |
EPBR - Received an unknown type code [dec] IPC message |
QFP EPBR feature received an unknown message from another layer of EPBR feature's software stack. |
EPBR_COMP_NAME |
LOG_STD_RECUR_ACTION |
|
EPBR_PROXY-4-PROXY_IPC_INVALID_MSG_LEN |
4-Warning |
[dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Invalid EPBR IPC message length. |
cpp-ucode |
LOG_STD_ACTION |
|
EPC-3-MEM_INIT_FAILED |
3-Error |
Allocation of [chars] memory failed for EPC |
EPC Initialization of channel pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
EPC-3-PKT_REPLICA_INIT_FAILED |
3-Error |
Register to Generic Packet Replication failed for EPC |
EPC Initialization of packet replication registration failed. |
cpp-ucode |
LOG_STD_ACTION |
|
EPIF_PORT-0-INTERNAL_PANIC |
0-Emergency |
[chars] |
A Panic Condition. |
- |
"" |
|
EPIF_PORT-1-INITFAIL |
1-Alert |
msgtxt_initfail |
- |
- |
- |
|
EPIF_PORT-1-INTERNAL_ALERT |
1-Alert |
[chars] |
A condition that should be corrected immediately. |
- |
"" |
|
EPIF_PORT-1-NOMEMORY |
1-Alert |
msgtxt_nomemory |
- |
- |
- |
|
EPIF_PORT-2-INTERNAL_CRITICAL |
2-Critical |
[chars] |
Critical Conditions |
- |
"" |
|
EPIF_PORT-3-INTERNAL_ERROR |
3-Error |
[chars] |
Errors |
- |
"" |
|
EPIF_PORT-4-INTERNAL_INTERFACE_WARNING |
4-Warning |
Interface [chars] [chars] |
Per interface Warning |
- |
"" |
|
EPIF_PORT-4-INTERNAL_WARNING |
4-Warning |
[chars] |
Warning |
- |
"" |
|
EPIF_PORT-6-INTERNAL_EVENT |
6-Information |
[chars] |
Informational |
- |
"" |
|
EPIF_PORT-7-INTERNAL_ASSERT |
7-Debug |
[chars]: [chars] Assertion Failure - File [chars] Line [dec] |
Assertion |
- |
"" |
|
EPM-3-SEND_MSG_FAILURE |
3-Error |
Process send msg failure for session hdl [hec] [chars] |
This message indicates a process send msg failure |
eedge-epm |
"No action required" |
|
EPM-4-POLICY_APP_FAILURE |
4-Warning |
Policy Application Failed for Client [[chars]] MAC [[enet]] AuditSessionID [[chars]] for POLICY_TYPE [chars] POLICY_NAME [chars] REASON [chars] |
This message indicates that the displayed policy for the client\n\ could not be applied by the EPM |
pem |
"Policy application failure could happen due to multiple reasons.The \n\ reason for the failure is notified to the client and the client has to\n\ take appropriate action based on it" |
|
EPM-4-POLICY_APP_FAILURE |
4-Warning |
Policy Application Failed for Client [[chars]] MAC [[enet]] AuditSessionID [[chars]] for POLICY_TYPE [chars] POLICY_NAME [chars] REASON [chars] |
This message indicates that the displayed policy for the client\n\ could not be applied by the EPM |
pem |
"Policy application failure could happen due to multiple reasons.The \n\ reason for the failure is notified to the client and the client has to\n\ take appropriate action based on it" |
|
EPM-6-AAA |
6-Information |
POLICY [chars]| EVENT [chars] |
This message indicates a download request has been sent/downloaded\n\ successfully for the specified dACL |
pem |
"No action required" |
|
EPM-6-AAA |
6-Information |
POLICY [chars]| EVENT [chars] |
This message indicates a download request has been sent/downloaded\n\ successfully for the specified dACL |
pem |
"No action required" |
|
EPM-6-ACL_CONFIG_ERROR |
6-Information |
ACL NAME '[chars]' | ACE SEQUENCE %ld | RESULT FAILURE | REASON '[chars]' |
This message indicates that adding an ACE to the specified ACL\n\ was ignored because of wrong configuration |
pem |
"Change ACE configuration for the specifed ACL" |
|
EPM-6-ACL_CONFIG_ERROR |
6-Information |
ACL NAME '[chars]' | ACE SEQUENCE %ld | RESULT FAILURE | REASON '[chars]' |
This message indicates that adding an ACE to the specified ACL\n\ was ignored because of wrong configuration |
pem |
"Change ACE configuration for the specifed ACL" |
|
EPM-6-ACL_CONFIG_ERROR |
6-Information |
ACL NAME '[chars]' | ACE SEQUENCE %ld | RESULT FAILURE | REASON '[chars]' |
This message indicates that adding an ACE to the specified ACL\n\ was ignored because of wrong configuration |
pem |
"Change ACE configuration for the specifed ACL" |
|
EPM-6-AUTH_ACL |
6-Information |
POLICY [chars]| EVENT [chars] |
This message indicates a AUTH_DEF_ACL or AUTH_DEF_ACL_OPEN has been \n\ applied or removed |
pem |
"No action required" |
|
EPM-6-AUTH_ACL |
6-Information |
POLICY [chars]| EVENT [chars] |
This message indicates a AUTH_DEF_ACL or AUTH_DEF_ACL_OPEN has been \n\ applied or removed |
pem |
"No action required" |
|
EPM-6-AUTH_ACL |
6-Information |
POLICY [chars]| EVENT [chars] |
This message indicates a AUTH_DEF_ACL or AUTH_DEF_ACL_OPEN has been \n\ applied or removed |
pem |
"No action required" |
|
EPM-6-IPEVENT |
6-Information |
IP [chars]| MAC [enet]| AuditSessionID [chars]| EVENT [chars] |
This message indicates the IP event Wait/Release/Assignment that\n\ has occured with respect to the specified host |
pem |
"No action required" |
|
EPM-6-IPEVENT |
6-Information |
IP [chars]| MAC [enet]| AuditSessionID [chars]| EVENT [chars] |
This message indicates the IP event Wait/Release/Assignment that\n\ has occured with respect to the specified host |
pem |
"No action required" |
|
EPM-6-POLICY_APP_SUCCESS |
6-Information |
Policy Application succeded for Client [[chars]] MAC [[enet]] AuditSession ID [[chars]] for POLICY_TYPE [[chars]] POLICY_NAME [[chars]] |
This message indicates that the displayed policy for the client has been\n\ applied successfully by the EPM |
pem |
"No action required" |
|
EPM-6-POLICY_APP_SUCCESS |
6-Information |
Policy Application succeded for Client [[chars]] MAC [[enet]] AuditSession ID [[chars]] for POLICY_TYPE [[chars]] POLICY_NAME [[chars]] |
This message indicates that the displayed policy for the client has been\n\ applied successfully by the EPM |
pem |
"No action required" |
|
EPM-6-POLICY_REQ |
6-Information |
IP [chars]| MAC [enet]| AuditSessionID [chars]| EVENT [chars] |
This message indicates that a policy application/remove request has been\n\ received by the EPM |
pem |
"No action required" |
|
EPM-6-POLICY_REQ |
6-Information |
IP [chars]| MAC [enet]| AuditSessionID [chars]| EVENT [chars] |
This message indicates that a policy application/remove request has been\n\ received by the EPM |
pem |
"No action required" |
|
EQPT_ALARM_PERSISTENCY-3-EQPT_ALARM_INFO_NULL |
3-Error |
Persistent alarm queue alarm info is NULL |
- |
- |
- |
|
EQPT_ALARM_PERSISTENCY-3-EQPT_ALARM_QUEUE_NULL |
3-Error |
Persistent alarm queue info is NULL |
- |
- |
- |
|
EQPT_ALARM_PERSISTENCY-3-EQPT_NULL_DATA_STRUCTURE |
3-Error |
[chars] is NULL |
- |
- |
- |
|
ERP_G8032-3-APS_CHANNEL_INACTIVE |
3-Error |
No longer receiving R-APS messages for ethernet ring [chars] instance [dec] |
A ring node has not received R-APS messages on the APS channel for an extended period of time. A properly functioning ring will have an R-APS message transmitted nominally every 5 seconds. This indicates that the requesting transmitting remote node on the ring such as |
ethernet-g8032 |
"Confirm the remote node is transmitting R-APS " "messages and that there is network connectivity on " "the APS channel between the remote node and this " "node." |
|
ERP_G8032-3-PORT_STATE_REQ_ACK_FAILED |
3-Error |
Port state negative ACK received for port [chars] state [dec] |
A port state change request was sent to the hardware successfully but a negative acknowledgement was received for this request. |
ethernet-g8032 |
"This error message likely indicates an internal IOS " "software issue. Try shutting and then bringing up " "the port. If this continues reboot the device. " "If the previous instructions didn't work use the " "Cisco software defect search tool to " "determine if this issue has been " "fixed in a later software release. If no defect is " "found then please contact your Cisco technical " "support representative and provide the " "representative with the exact error message seen " "as well as the version of IOS being used." |
|
ERP_G8032-3-PORT_STATE_REQ_ACK_TIMER_EXPIRED |
3-Error |
No port state ACK received for ring [chars] instance [dec] port [dec] state [dec] |
A port state change request was sent to the hardware successfully but an acknowledgement was never received for this request. This means that there is a problem in the hardware. |
ethernet-g8032 |
"This error message likely indicates an internal IOS " "software issue. Try shutting and then bringing up " "the port. If this continues reboot the device. " "If the previous instructions didn't work use the " "Cisco software defect search tool to " "determine if this issue has been " "fixed in a later software release. If no defect is " "found then please contact your Cisco technical " "support representative and provide the " "representative with the exact error message seen " "as well as the version of IOS being used." |
|
ERP_G8032-3-PORT_STATE_REQ_MAX_LIMIT |
3-Error |
Port state request has been sent many times and the desired state has not been achieved for port [chars] |
A port state change request was sent to the hardware successfully and acknowledgement was received but the desired state was not achieved. |
ethernet-g8032 |
"This error message likely indicates an internal IOS " "software issue. Try shutting and then bringing up " "the port. If this continues reboot the device. " "If the previous instructions didn't work use the " "Cisco software defect search tool to " "determine if this issue has been " "fixed in a later software release. If no defect is " "found then please contact your Cisco technical " "support representative and provide the " "representative with the exact error message seen " "as well as the version of IOS being used." |
|
ERP_G8032-4-FOP_PM_LOWER_LEVEL |
4-Warning |
Node received an R-APS message with Node Id [chars] level [dec] which is lower than configured level [dec] for Ethernet ring [chars] instance [dec] |
A ring node detects an R-APS message with a lower level than the configured G.8032 instance level for that APS Channel. This is a Failure of Protocol - Provisioning Mismatch - Level due to a misconfiguration of the APS level of nodes in the ring. |
ethernet-g8032 |
"Identify the other node with Node Id and " "reconfigure it with a matching APS level." |
|
ERP_G8032-4-FOP_PM_MULTIPLE_RPL_OWNER |
4-Warning |
RPL Owner node received an R-APSNRRB message from another RPL |
RPL Owner node detects a No Request R-APS message with the RPL Blocked status flag set and the Node Id differs from its own. This is a Failure of Protocol - Provision Mismatch due to a misconfiguration where there are multiple RPL Owner nodes configured in the ring. |
ethernet-g8032 |
"Identify the other RPL Owner node with Node Id and " "reconfigure it to be a non-RPL Owner node." |
|
ERP_G8032-6-CLEAR_REMINDER |
6-Information |
Non-revertive ethernet ring [chars] instance [dec] is ready to be cleared by user |
Faults have disappeared from a non-revertive ethernet ring instance so now it is ready to be cleared by the user. A non-revertive ring instance by definition requires user action because it does not revert automatically. The act of clearing the ring will cause the location of the block to move to the RPL link and the state to transition to Idle. |
ethernet-g8032 |
"Once ready to move the block to the RPL link the " "ring instance can be cleared with the " "<CmdBold>ethernet ring g8032 clear<noCmdBold> " "command." |
|
ERP_G8032-6-STATE_CHANGED |
6-Information |
Ethernet ring [chars] instance [dec] changed state to [chars] |
Informational message to notify the state transitions for a ring instance |
ethernet-g8032 |
"None. This is an informational message to indicate " "an event may have triggered some ring protection " "action." |
|
ERROR-3-OF_AGENT |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
ERROR-3-OVS |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
Error in handling FRR: [chars] [chars] [hec] [hec] |
Error in FRR processing |
c7600-sip-common |
"This is a internal software error. If this " "error happened while configuring FRR try " "reconfiguring the interface. If the error " "persists or occurred during normal operation " "decode the traceback and " LOG_STD_ACTION |
- |
- |
|
ERSPAN-3-MEM_INIT_FAILED |
3-Error |
Allocation of [chars] memory failed for ERSPAN |
ERSPAN Initialization of channel pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
ERSPAN-3-PKT_REPLICA_INIT_FAILED |
3-Error |
Register to Generic Packet Replication failed for ERSPAN |
ERSPAN Initialization of packet replication registration failed. |
cpp-ucode |
LOG_STD_ACTION |
|
ESF_MPLS-3-EREVENT |
3-Error |
[chars] |
An internal software error occurred. |
firmware |
LOG_STD_ACTION |
|
ESF_MPLS-3-ESF_FIB_ADD_FAILED |
3-Error |
Attempt to add ESF tagged route [inet]/[dec] Table %lu failed |
An internal software error occurred. |
firmware |
LOG_STD_ACTION |
|
ESG_MEMORY_UPGRADE-3-CONF_FAILED |
3-Error |
Configuration of memory failed. |
An error occurred when memory configuration was attempted. |
iosxe-csl |
- |
|
ESS_FEATURE-3-ESF_STUB |
3-Error |
CPP ESS per-session feature [chars] executes stub entry in [chars] direction |
Cisco internal software error. CPP ESS per-session feature stub entry got executed. The packet will be dropped. |
qfp-bb keyword:none |
LOG_STD_ACTION |
|
ESS_FEATURE-4-ESF_DROP_POLICY |
4-Warning |
CPP ESS feature encounted unexpected linktype=[dec] |
Cisco internal software error. CPP ESS per-session feature encounted unexpected linktype when executing output drop policy |
qfp-bb keyword:none |
LOG_STD_ACTION |
|
ESS_IPSUB-3-ESS_IPSUB_STUB |
3-Error |
CPP ESS IPSUB executes stub entry in [chars] direction |
Cisco internal software error. CPP ESS IPSUB stub entry got executed. The packet will be dropped. |
qfp-bb keyword:none |
LOG_STD_ACTION |
|
ESS_IPSUB-3-FSOL_THROTTLE_ERR |
3-Error |
Allocation of [chars] memory failed for ESS IP Subscriber |
Allocation of memory resource demanded by ESS IPSUB FSOL throttle failed. This is a serious problem at the ESS IPSUB FSOL initialization for throttling. |
qfp-bb keyword:none |
LOG_STD_ACTION |
|
ESS_PROXY-2-IPC_THROTTLE_ERR |
2-Critical |
Allocation of [chars] memory failed for ESS Proxy unsolicited event throttling |
Allocation of memory resource demanded by ESS Proxy throttle failed. This is a serious problem at the ESS Proxy IPC initialization for unsolicited event throttling. |
qfp-bb keyword:none |
LOG_STD_ACTION |
|
ESS_PROXY-2-KA_CHANNEL_ALLOC_FAILED |
2-Critical |
CPP ESS Proxy Session Keepalive channel creation failure. |
Cisco internal software error. CPP ESS Proxy Session Keepalive detected that the channel creation failed. CPP ESS proxy session keepalive will not be functional while this condition exists. |
qfp-bb keyword:none |
LOG_STD_ACTION |
|
ESS_PROXY-2-KA_PKT_REPLICA_REG_FAILED |
2-Critical |
CPP ESS Proxy Session Keepalive packet replication registration failure result: [dec]. |
Cisco internal software error. CPP ESS Proxy Session Keepalive detected that the packet replication registration failed. CPP ESS proxy session keepalive will not be functional while this condition exists. |
qfp-bb keyword:none |
LOG_STD_ACTION |
|
ESS_PROXY-2-KA_PKT_TMPL_BFR_ALLOC_FAILED |
2-Critical |
CPP ESS Proxy Session Keepalive packet template allocation failure [chars] buffer length: [dec]. |
Cisco internal software error. CPP ESS Proxy Session Keepalive detected that the packet template buffer allocation failed. CPP ESS proxy session keepalive will not be functional while this condition exists. |
qfp-bb keyword:none |
LOG_STD_ACTION |
|
ESS_PROXY-2-KA_TIMER_INIT_FAILED |
2-Critical |
CPP ESS Proxy Session Keepalive timer initialization failure. |
Cisco internal software error. CPP ESS Proxy Session Keepalive detected that the timer initialization failed. CPP ESS proxy session keepalive will not be functional while this condition exists. |
qfp-bb keyword:none |
LOG_STD_ACTION |
|
ESS_PROXY-2-PROXY_IPC_INIT_FAILED |
2-Critical |
CPP ESS Proxy IPC interface initialization failure result: [dec]. |
Cisco internal software error. CPP ESS Proxy initialization detected that the IPC interface initialization failed. CPP ESS proxy will not be functional while this condition exists. |
qfp-bb keyword:none |
LOG_STD_ACTION |
|
ESS_PROXY-3-PROXY_BAD_MSG |
3-Error |
CPP ESS Proxy received bad length message type [dec] |
Cisco internal software error. CPP ESS Proxy received a corrupted message from control plane. This message will be ignored. |
qfp-bb keyword:none |
LOG_STD_ACTION |
|
ESS_PROXY-3-PROXY_INV_MSG |
3-Error |
CPP ESS Proxy received invalid message type [dec] |
Cisco internal software error. CPP ESS Proxy received an invalid message type from control plane. This message will be ignored. |
qfp-bb keyword:none |
LOG_STD_ACTION |
|
ESS_PROXY-3-PROXY_IPC_ALLOC_FAILED |
3-Error |
CPP ESS Proxy [chars] message lost due to message buffer allocation failure. |
Cisco internal software error. CPP ESS Proxy message processing detected a message buffer allocation failure. The message is lost as the result of this condition. |
qfp-bb keyword:none |
LOG_STD_ACTION |
|
ESS_PROXY-3-PROXY_IPC_NO_HDLR |
3-Error |
CPP ESS Proxy received unregistered message type [dec] |
Cisco internal software error. CPP ESS Proxy received a message from control plane but there is no registered handler. The message is lost as the result of this condition. |
qfp-bb keyword:none |
LOG_STD_ACTION |
|
ESS_PROXY-3-PROXY_IPC_SEND_FAILED |
3-Error |
CPP ESS Proxy [chars] message lost due to message sent failure result: [dec]. |
Cisco internal software error. CPP ESS Proxy message processing detected a message sent failure. The message is lost as the result of this condition. |
qfp-bb keyword:none |
LOG_STD_ACTION |
|
ESS_SWITCH-3-ESS_STUB |
3-Error |
CPP ESS switching [chars] feature executes stub entry in [chars] direction |
Cisco internal software error. CPP ESS Switching feature stub entry got executed. The packet will be dropped. |
qfp-bb keyword:none |
LOG_STD_ACTION |
|
ESS_SWITCH-3-STATS_INVALID_PTR |
3-Error |
CPP ESS Switching invalid statistics block for session [chars]. |
Cisco internal software error. CPP ESS Switching session contains an invalid statistics block. The session statistics is lost. |
qfp-bb keyword:none |
LOG_STD_ACTION |
|
ETC-3-NULL_AG_UNKNOWN_GROUP |
3-Error |
The system does not find port-channel group information |
The system is trying to retrieve the port-channel group information for a specific port channel but it cannot find it. |
PF_DDTS_COMPONENT |
LOG_STD_ACTION |
|
ETC-4-NOMEM |
4-Warning |
Not enough memory available for [chars] |
The PAgP/LACP Shim/EC could not obtain the memory it needed. |
fec |
LOG_STD_SH_TECH_ACTION |
|
ETC-5-BUNDLE |
5-Notice |
Interface [chars] joined port-channel [chars] |
Interface joined the bundle. |
- |
- |
|
ETC-5-CANNOT_ALLOCATE_AGGREGATOR |
5-Notice |
Aggregator limit reached cannot allocate aggregator for group [dec] |
New aggregator cannot be allocated in the group. Change the port attributes of the ports in the group so that they match and join the same aggregator. |
- |
- |
|
ETC-5-CANNOT_BUNDLE_LACP |
5-Notice |
[chars] is not compatible with aggregators in channel [dec] and cannot attach to them [chars] |
The port has different port-attributes that of port-channel or ports within the port-channel. For the port to join the bundle change the ports attributes so that it matches the port. |
- |
"Match the port-attributes to that of port-channel" |
|
ETC-5-CANNOT_BUNDLE_QOS |
5-Notice |
Removed [chars] from port channel because a QoS policy cannot be supported across multiple DFC cards. |
The Port specified in the error message cannot join port channel because the QoS policy attached to the port channel cannot support multiple DFC cards. |
fec |
"Place the port in another port channel or remove " "the QoS policy from the port channel." |
|
ETC-5-CANNOT_BUNDLE_QOS1 |
5-Notice |
Removed [chars] from port channel as QoS attributes of port and port-channel are different. |
The Port specified in the error message cannot join port channel because the QoS attributes of this port are not consistent with the QoS attributes of the port-channel. |
fec |
"Match the QoS attributes of the specified port to the QoS " "attributes of other member ports in the port channel. Use the " "<CmdBold>show queueing interface<NoCmdBold> command to display " "the QoS attributes of a port." |
|
ETC-5-CANNOT_BUNDLE1 |
5-Notice |
Port-channel [chars] is down port [chars] will remain stand-alone. |
The state of the aggregation port is down. The port will remain\n\ stand-alone until the state of the aggregation port is up. |
- |
"Ensure that the other ports in the bundle have the\n\ same configuration." |
|
ETC-5-CANNOT_BUNDLE2 |
5-Notice |
[chars] is not compatible with [chars] and will be suspended [chars] |
The attributes of the specified port are different from the attributes of the port-channel or the attributes of the ports within the port-channel. |
- |
"Match the attributes of the specifed port to the attributes of the " "port-channel so that the specified port can join the bundle". |
|
ETC-5-COMPATIBLE |
5-Notice |
[chars] is compatible with port-channel members |
The specified port was not operational earlier because its attributes were different from the attributes of the port-channel or the attributes of the ports within the port-channel. The system detects that the attributes of the specified port now match the port-channel attributes. |
- |
LOG_STD_NO_ACTION |
|
ETC-5-DONTBNDL |
5-Notice |
[chars] suspended: incompatible remote port with [chars] |
The configuration of the remote port is different from the configuration of other remote ports in the bundle. A port can only join the bundle when the configuration of the local port and the configuration of the remote port are the same as other ports already in the bundle. |
fec |
"Ensure that the configuration of the remote ports " "is the same for all ports in the bundle" |
|
ETC-5-ERRPROT |
5-Notice |
Channel protocol mismatch for interface [chars] in group [dec]: the interface can not be added to the channel group |
The interface can not be added to the channel-group with the specified mode |
fec |
"Change the channel-group or the mode for the " "interface" |
|
ETC-5-ERRPROT2 |
5-Notice |
Command rejected: the interface [chars] is already part of a channel with a different type of protocol enabled |
The interface can not be selected for the specified protocol since is already part of a channel with a different type of protocol enabled |
fec |
"Remove the interface from the channel group" |
|
ETC-5-ERRPROT3 |
5-Notice |
Command rejected: the interface [chars] is already part of a channel |
The interface can not be unselected for the specified protocol since is already part of a channel |
fec |
"Remove the interface from the channel group" |
|
ETC-5-L3DONTBNDL1 |
5-Notice |
[chars] suspended: PAgP not enabled on the remote port. |
PAgP is enabled on an L3 interface but it has been detected that the remote port does not have PAgP enabled. In this mode the port is put in a suspended state. |
fec |
"Enable PAgP on remote side" |
|
ETC-5-L3DONTBNDL2 |
5-Notice |
[chars] suspended: LACP currently not enabled on the remote port. |
LACP is enabled on an L3 interface but it has been detected that the remote port does not have LACP enabled. In this mode the port is put in a suspended state. |
fec |
"Enable LACP on the remote side" |
|
ETC-5-MINLINKS_MET |
5-Notice |
Port-channel [chars] is up as its bundled ports [dec] meets min-links |
The administrative configuration of minimum links is equal or less than the\n\ number of bundled ports. Therefore this port channel has been brought\n\ up |
fec |
"This is an informational message only.\n\ No action is required" |
|
ETC-5-MINLINKS_NOTMET |
5-Notice |
Port-channel [chars] is down bundled ports [dec] doesn't meet min-links |
The administrative configuration of minimum links is greater than the\n\ number of bundled ports. Therefore this port channel has been brought\n\ down |
fec |
"Reduce the min-links configuration for this group\n\ or add more ports to this port-channel to create a\n\ bundle." |
|
ETC-5-NOLACP |
5-Notice |
Invalid EC mode LACP not enabled |
LACP is not included in the image. Cannot set EC mode to active/passive |
fec |
"Get an image with LACP included or set mode to On" |
|
ETC-5-NOPAGP |
5-Notice |
Invalid EC mode PAgP not enabled |
PAgP is not included in the image. Cannot set EC mode to desirable/auto |
fec |
"Get an image with PAgP included or set mode to On" |
|
ETC-5-PORTDOWN |
5-Notice |
Shutting down [chars] as its port-channel is admin-down |
The administrative state of the port is controlled by the administrative state of its aggregate port. If the administrative state of the aggregate port is down the administrative state of the port will also be forced to be down |
fec |
"Enter the <CmdBold>no shutdown<NoCmdBold> command " "on the aggregate port to activate unshut the " |
|
ETC-5-STAYDOWN |
5-Notice |
[chars] will remain down as its port-channel [chars] is admin-down |
The administrative state of the aggregation port overrides that of the port. If the aggregation port is administratively down all ports in the aggregation port will also be forced to be administratively down. |
fec |
"Enter the <CmdBold>no shutdown<NoCmdBold> command " "on the aggregation port to activate unshut the " |
|
ETC-5-UNBUNDLE |
5-Notice |
Interface [chars] left the port-channel [chars] |
Interface fell off the bundle |
- |
- |
|
ETC-5-UNSUITABLE |
5-Notice |
[chars] will not join any port-channel [chars] |
Configuring any of Port-fast VMPS Dest-SPAN are considered unsuitable for etherchannel. Please unconfigure them. |
- |
- |
|
ETH_SPA_GEN-3-CU_SFP_NOT_SUPP |
3-Error |
CU-SFP is not supported on SPA-2x1GE-V2 / SPA-2x1GE-SYNCE |
CU-SFP is not supported on SPA-2x1GE-V2 / SPA-2x1GE-SYNCE |
spa-eth-all |
"Use PHY based ports for CU Connections " |
|
ETH_SPA_GEN-3-UNSUPPORTED_XCVR |
3-Error |
Transceiver type GLC-GE-100FX is not supported on SPA-8xGE-V2 |
Transceiver type GLC-GE-100FX is not supported on SPA-8xGE-V2 |
spa-eth-all |
"Consult the documentation and ensure supported " "transceivers are plugged into the SPA" |
|
ETH_SPA_GILA_FUGU-3-DATA_VER_MISMATCH |
3-Error |
TCAM checkpointed data version [dec] differs from current version [dec]. |
During Minimal Disruptive Restart version of checkpointed tcam data is found to be different from the data in the current version. The SPA will be reset as normal and hence will impact traffic. |
spa-eth-v2 |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
ETH_SPA_GILA_FUGU-3-ELT_NOT_IN_CUR_VER |
3-Error |
The element at address [dec] in [chars] tcam is found missing during Minimal Disruptive Restart reconcilation. |
During the reconcilation phase of Minimumal Disruptive Restart an element was found to be present in the old IOS but not present in the new IOS image. This indicates that the config for this element was not played down from the RP during config-replay. This is an error condition and the SPA will be reset as normal and hence will impact traffic. |
spa-eth-v2 |
"Open a case with Cisco Technical Assistance Center for further " "assistance" |
|
ETH_SPA_GILA_FUGU-3-HDR_PARAMS_MISMATCH |
3-Error |
TCAM checkpointed header values differs from values in current version. |
During Minimal Disruptive Restart values of fields in the checkpointed tcam header is found to be differnt from the values in the current version of IOS. The SPA will be reset as normal and hence will impact traffic. |
spa-eth-v2 |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
ETH_SPA_GILA_FUGU-3-HDR_VER_MISMATCH |
3-Error |
TCAM checkpointed header version [dec] differs from current version [dec]. |
During Minimal Disruptive Restart version of checkpointed tcam header is found to be different from the header in the current version. The SPA will be reset as normal and hence will impact traffic. |
spa-eth-v2 |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
ETH_SPA_GILA_FUGU-3-HW_SW_MISMATCH |
3-Error |
The hardware and software copies of the element at address [dec] in tcam [chars] do not match. This indicates reconcilation failure. |
During reconcilation phase of Minimal Disruptive Restart it is found that the software and hardware copies of an element in tcam do not match. This indicates an error and the SPA will be reset as normal and impact traffic. |
spa-eth-v2 |
"Open a case with Cisco Technical Assistance Center for further " "assistance" |
|
ETH_SPA_GILA_FUGU-3-RECONFIG_FAILURE |
3-Error |
Fugu reconfiguration failed for SPA in slot [dec] bay [dec] during Minimal Disruptive Restart. |
During Minimal Disruptive Restart fugu reconfiguration error has occured. This indicates an error and the SPA will be reset as normal and impact traffic. |
spa-eth-v2 |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
ETH_SPA_GILA_FUGU-3-RESTART_FAILURE |
3-Error |
Fugu restart failed for SPA in slot [dec] bay [dec] with error [dec] during Minimal Disruptive Restart. |
During Minimal Disruptive Restart fugu restart error has occured. This indicates an error and the SPA will be reset as normal and impact traffic. |
spa-eth-v2 |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
ETH_SPA_GILA_FUGU-3-SPI4_MCALPRTY_ERR |
3-Error |
[chars] : [chars] Calender memory Parity error |
An internal SPI4 error SPI4 calender memory parity error occurred |
spa-eth-all |
"If the issue persists it may be a case of bad hardware. Please open " "a case with Cisco technical support personnel for further assistance." |
|
ETH_SPA_GILA_FUGU-3-SPI4_MCALRBPRTY_ERR |
3-Error |
[chars] : [chars] Calender memory read back Parity error |
An internal SPI4 error SPI4 Calender memory read back parity error |
spa-eth-all |
"Try reseating the SPA and if the issue persists open a case with the " "Cisco Technical Assistance Center." |
|
ETH_SPA_GILA_FUGU-3-SPI4_MCNTPRTY_ERR |
3-Error |
[chars] : [chars] Memory Parity error |
An internal SPI4 error SPI4 Control FIFO Memory Parity error |
spa-eth-all |
"If the issue persists open a case with Cisco Technical Assistance " "Center for further assistance." |
|
ETH_SPA_GILA_FUGU-3-SPI4_MDATAPRTY_ERR |
3-Error |
[chars] : [chars] Memory Parity error |
An internal SPI4 error SPI4 DATA FIFO Memory Parity error |
spa-eth-all |
"If the issue persists open a case with Cisco Technical Assistance " "Center for further assistance." |
|
ETH_SPA_GILA_FUGU-3-SPI4_OVF_ERR |
3-Error |
[chars] : [chars] Overflow Error |
An internal SPI4 error SPI4 Overflow Error occured in the SPA. |
spa-eth-all |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
ETH_SPA_GILA_FUGU-3-SPI4_RDOOF_ERR |
3-Error |
[chars] : [chars] Rdata Out of Frame error |
An internal SPI4 error SPI4 Rdata Out of Frame error occured in |
spa-eth-all |
"If the issue persists open a case with the Cisco Technical Assistance " "Center." |
|
ETH_SPA_GILA_FUGU-3-SPI4_SYNC_FAIL |
3-Error |
[chars] : Sync check failed in [chars] SPI4 interafce |
Synchronization check failed in the Gila/Fugu SPI4 interafce |
spa-eth-all |
"Try reseating the SPA. If the issue persists contact Cisco Technical " "Assistance Center." |
|
ETH_SPA_GILA_FUGU-3-TCAM_RECONFIG_FAILURE |
3-Error |
Fugu TCAM reconfiguration failed for SPA in slot [dec] bay [dec] with error [dec] reconfig_needed [dec] during Minimal Disruptive Restart. |
During Minimal Disruptive Restart fugu tcam reconfiguration error has occure. This indicates an error and SPA will be reset as normal and impact traffic. |
spa-eth-v2 |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
ETH_SPA_GILA_FUGU-3-TCAM_RESTART_FAILURE |
3-Error |
TCAM restart failed for SPA in slot [dec] bay [dec] with error [dec] during Minimal Disruptive Restart. |
During Minimal Disruptive Restart fugu tcam restart has failed. This indicates an error and SPA will be reset as normal and impact traffic. |
spa-eth-v2 |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
ETH_SPA_GILA_FUGU-3-VLAN_TCAM_ERR |
3-Error |
TCAM programming error at offset [dec] |
An error was encountered when programming the VLAN TCAM. Two tcam entries are seen to have the same logical address so traffic drop will be seen on these subinterfaces |
spa-eth-all |
"Reload the Linecard. If the issue persists please " "open a case with Cisco TAC for further assistance." |
|
ETH_SPA_GILA_FUGU-6-ELT_IS_NEW |
6-Information |
The element at address [dec] in [chars] tcam is found to be new during Minimal Disruptive Restart reconcilation. |
During the reconcilation phase of Minimumal Disruptive Restart an element was found to be present in the new IOS but not present in the old IOS image. This is not an error condition the SPA driver will program this new entry into the hardware. |
spa-eth-v2 |
"Open a case with Cisco Technical Assistance Center for further " "assistance" |
|
ETH_SPA_MAC-3-INTR_MAX_BURST |
3-Error |
Bursts of interrupts from [chars] have crossed maximum limit [dec] for port [dec]/[dec]/[dec] |
Burst of interrupts that have crossed the maximum limit are detected by the SPA. |
spa-eth-all |
"Check the interface configuration and receive signal characteristics. " "Also verify the XFP transceiver and receive signal path. " "Re-enable the interface after corrective action." |
|
ETH_SPA_MAC-3-PHY_RECONFIG_FAILURE |
3-Error |
PHY reconfiguration failed for SPA in slot [dec] bay [dec] with error [dec] during Minimal Disruptive Restart. This indicates an error and the SPA will be reset as normal and impact traffic. |
- |
spa-eth-v2 |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
ETH_SPA_MAC-3-PHY_RESTART_FAILURE |
3-Error |
PHY restart failed for SPA in slot [dec] bay [dec] with error [dec] during Minimal Disruptive Restart. |
During Minimal Disruptive Restart phy restart error has occured. This indicates an error and the SPA will be reset as normal and impact traffic. |
spa-eth-v2 |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
ETH_SPA_MAC-3-RECONFIG_FAILURE |
3-Error |
MAC reconfiguration failed for SPA in slot [dec] bay [dec] during Minimal Disruptive Restart. |
During Minimal Disruptive Restart a mac reconfiguration error has occured.This indicates an error and the SPA will be reset as normal and impact traffic. |
spa-eth-v2 |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
ETH_SPA_MAC-3-RESTART_FAILURE |
3-Error |
MAC restart failed for SPA in slot [dec] bay [dec] with error [dec] during Minimal Disruptive Restart. |
During Minimal Disruptive Restart mac restart error has occured. This indicates an error and the SPA will be reset as normal and impact traffic. |
spa-eth-v2 |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
ETH_SPA_MAC-3-SPI4_ERROR |
3-Error |
[chars] : SPI4 Error occured in the MAC |
SPI4 error occured in the MAC. |
spa-eth-all |
"SPI error reported in the SPA. Try reseating the SPA if the error " "occurs multiple times. If you further need assistance please open a " "case with Cisco TAC at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl" |
|
ETH_SPA_MAC-3-SPI4_SINK_INIT_ERR |
3-Error |
[chars] : Marvel spi4.1 sink init failed PL410 global status <lock> not set |
An internal SPI4 error occurred in the SPA. |
spa-eth-all |
"If the issue persists return the SPA using the RMA process." |
|
ETH_SPA_MAC-3-UNREC_ECC_ERR |
3-Error |
[chars] : An unrecoverable ECC error occured in the MAC |
An unrecoverable ECC error occured in the MAC. |
spa-eth-all |
"Try to reload the SPA to recover from the failure. If the problem " "persist contact Cisco Technical Assistance Center for assistance." |
|
ETH_SPA_MAC-6-INTR_BURST |
6-Information |
Interrupts from [chars] have crossed burst limit of [dec] in [dec] msec for port [dec]/[dec]/[dec] |
Interrupts that have crossed the burst limit are detected by the SPA. |
spa-eth-all |
"Check the interface configuration and receive signal characteristics. " "Also verify the XFP transceiver and receive signal path. " "Re-enable the interface after corrective action." |
|
ETH_SPA_SERDES-3-RECONFIG_FAILURE |
3-Error |
Serdes reconfiguration failed for SPA in slot [dec] bay [dec] during Minimal Disruptive Restart. |
During Minimal Disruptive Restart serdes reconfiguration error has occured. This indicates an error and the SPA will be reset as normal and impact traffic. |
spa-eth-v2 |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
ETH_SPA_SERDES-3-RESTART_FAILURE |
3-Error |
Serdes restart failed for SPA in slot [dec] bay [dec] during Minimal Disruptive Restart. |
During Minimal Disruptive Restart serdes restart error has occured. This indicates an error and the SPA will be reset as normal and impact traffic. |
spa-eth-v2 |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
ETHCNTR-2-MOLSENDTIMEOUT |
2-Critical |
Molecule send timeout queue [dec] molecule 0x[hec] 0x[hec] |
An attempt to read or write one or more of the hardware settings failed. |
firmware |
LOG_STD_ACTION |
|
ETHCNTR-3-FLOWCONTROL_DUPLEX_ERROR |
3-Error |
Flowcontrol will not take effect until duplex is set to auto. |
- |
firmware |
"Configure duplex auto" |
|
ETHCNTR-3-HALF_DUX_COLLISION_EXCEED_THRESHOLD |
3-Error |
Half-duplex loopback detected collision threshold exceeded on [chars]. |
The collisions on a half-duplex port exceeded the threshold with no valid data packets. The port is considered to be in a loopback condition. This may be caused by accidentally plugging a balun cable into the port |
firmware |
"Correct the problem causing the " "loopback condition. Then bring the port up by entering " "the shutdown then no shutdown interface configuration " "commands. The port will be automatically restarted " "after a timeout if errdisable recovery cause loopback " "is configured." |
|
ETHCNTR-3-HALF_DUX_COLLISION_EXCEED_THRESHOLD |
3-Error |
Half-duplex loopback detected collision threshold exceeded on [chars]. |
The collisions on a half-duplex port exceeded the threshold with no valid data packets. The port is considered to be in a loopback condition. This may be caused by accidentally plugging a balun cable into the port |
firmware |
"Correct the problem causing the loopback condition. Then " "bring the port up by entering the shutdown then no shutdown " "interface configuration commands. The port will be " "automatically restarted after a timeout if errdisable " "recovery cause loopback is configured." |
|
ETHCNTR-3-INTERNAL_ERROR |
3-Error |
Internal Error [chars] |
An internal error occurred. |
firmware |
LOG_STD_RECUR_ACTION |
|
ETHCNTR-3-INVALIDMAP |
3-Error |
Invalid map [dec] for address [enet] |
An attempt to bridge a packet in software obtained an invalid result. |
firmware |
LOG_STD_RECUR_ACTION |
|
ETHCNTR-3-LOOP_BACK_DETECTED |
3-Error |
Keepalive packet loop-back detected on [chars]. |
Loop-back may be caused by accidentally plugging a balun cable into the port or there may be a misconfiguration in the network. |
firmware |
"Correct the problem causing the loopback " "condition. Then bring the port up by entering the shutdown " "then no shutdown interface configuration commands. The port " "will be automatically restarted after a timeout if errdisable " "recovery cause loopback is configured." |
|
ETHCNTR-3-LOOP_BACK_DETECTED |
3-Error |
Keepalive packet loop-back detected on [chars]. |
Loop-back may be caused by accidentally plugging a balun cable into the port or there may be a misconfiguration in the network. |
firmware |
"Correct the problem causing the loopback condition. Then " "bring the port up by entering the shutdown then no shutdown " "interface configuration commands. The port will be " "automatically restarted after a timeout if errdisable " "recovery cause loopback is configured." |
|
ETHCNTR-3-MOLSENDINT |
3-Error |
Molecule send from interrupt handler |
An interrupt handler is accessing the hardware in a manner that is not permissible in an interrupt handler. |
firmware |
LOG_STD_ACTION |
|
ETHCNTR-3-RA_ALLOC_ERROR |
3-Error |
RAM Access [chars] [chars] memory allocation failure |
A request to read/write RAM failed memory allocation |
firmware |
LOG_STD_RECUR_ACTION |
|
ETHCNTR-3-RA_REPLY_ERROR |
3-Error |
Invalid reply to RAM Access [chars] request 0x%08x from satellite [dec] |
A request to read/write RAM on satellite access produced unexpected reply. |
firmware |
LOG_STD_RECUR_ACTION |
|
ETHCNTR-3-UNEXPECTED_EVENT |
3-Error |
Request 0x%08x encountered event [dec] in state [dec] |
An unexpected event occurred for a ram access request. |
firmware |
LOG_STD_RECUR_ACTION |
|
ETHCNTR-7-RAM_ACCESS_CMD_GROWING |
7-Debug |
Ethernet Controller: Growing RAM Access [chars] Command |
The command buffer for RAM Access is being grown dynamically because the original buffer was not big enough |
firmware |
LOG_STD_RECUR_ACTION |
|
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" |
|
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-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-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-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-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-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-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-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-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-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-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-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-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-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-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_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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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_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-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-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-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-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-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-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-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-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-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_INFRA_HA-2-GET_BUFFER |
2-Critical |
Ether INFRA ISSU client failed to get buffer for message. Error: [dec] [chars] |
The Ether INFRA 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. |
ether-infra |
"show logging and show checkpoint client" |
|
ETHER_INFRA_HA-2-INIT |
2-Critical |
Ether INFRA ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The Ether INFRA 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. |
ether-infra |
LOG_STD_ACTION |
|
ETHER_INFRA_HA-2-SEND_NEGO_FAILED |
2-Critical |
Ether INFRA ISSU client failed to send negotiation message. Error: [dec] [chars] |
The Ether INFRA 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. |
ether-infra |
"show logging and show checkpoint client" |
|
ETHER_INFRA_HA-2-SESSION_NEGO |
2-Critical |
Ether INFRA ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The Ether INFRA 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. |
ether-infra |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ETHER_INFRA_HA-2-SESSION_REGISTRY |
2-Critical |
Ether INFRA ISSU client failed to register session information. Error: [dec] [chars] |
The Ether INFRA ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
ether-infra |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ETHER_INFRA_HA-3-INVALID_SESSION |
3-Error |
Ether INFRA ISSU client does not have a valid registered session. |
The Ether INFRA ISSU client does not have a valid registered session. |
ether-infra |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ETHER_INFRA_HA-3-MSG_NOT_OK |
3-Error |
Ether INFRA ISSU client 'Message Type [dec]' is not compatible |
The Ether INFRA ISSU client received an incompatible message from the peer device. The message cannot be processed. |
ether-infra |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
ETHER_INFRA_HA-3-MSG_SIZE |
3-Error |
Ether INFRA ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The Ether INFRA ISSU client failed to calculate the MTU for the specified message. The Ether INFRA ISSU client will not able to send the message to the standby device. |
ether-infra |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
ETHER_INFRA_HA-3-SESSION_UNREGISTRY |
3-Error |
Ether INFRA ISSU client failed to unregister session information. Error: [dec] [chars] |
The Ether INFRA ISSU client failed to unregister session information. |
ether-infra |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ETHER_INFRA_HA-3-TRANSFORM |
3-Error |
Ether INFRA ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The Ether INFRA 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 INFRA state between the active device and the standby device is not identical. |
ether-infra |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
ETHER_LMI_HA-2-GET_BUFFER |
2-Critical |
Ether LMI ISSU client failed to get buffer for message. Error: [dec] [chars] |
The Ether LMI HA client failed to get buffer space for building chkpt message. Message cannot be sent to standby device. If a problem occurs the standby device cannot be brought up properly. |
ethernet-lmi |
"show logging and show checkpoint client" |
|
ETHER_LMI_HA-2-INIT |
2-Critical |
Ether LMI ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The Ether LMI ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure there will be downtime during software upgrade or downgrade. |
ethernet-lmi |
LOG_STD_ACTION |
|
ETHER_LMI_HA-2-SEND_NEGO_FAILED |
2-Critical |
Ether LMI ISSU client failed to send negotiation message. Error: [dec] [chars] |
The Ether LMI ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation the standby device cannot be brought up properly. |
ethernet-lmi |
"show logging and show checkpoint client" |
|
ETHER_LMI_HA-2-SESSION_NEGO |
2-Critical |
Ether LMI ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The Ether LMI ISSU client encountered a 'client negotiation done' state that was unexpected. If a problem occurs with the ISSU session negotiation the standby device cannot be brought up properly. |
ethernet-lmi |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ETHER_LMI_HA-2-SESSION_REGISTRY |
2-Critical |
Ether LMI ISSU client failed to register session information. Error: [dec] [chars] |
The Ether LMI ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
ethernet-lmi |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ETHER_LMI_HA-3-INVALID_SESSION |
3-Error |
Ether LMI ISSU client does not have a valid registered session. |
The Ether LMI ISSU client does not have a valid registered session. |
ethernet-lmi |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ETHER_LMI_HA-3-MSG_NOT_OK |
3-Error |
Ether LMI ISSU client 'Message Type [dec]' is not compatible |
The Ether LMI ISSU client received an incompatible message from the peer device. The message cannot be processed. |
ethernet-lmi |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
ETHER_LMI_HA-3-MSG_SIZE |
3-Error |
Ether LMI ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The Ether LMI ISSU client failed to calculate the MTU for the specified message. The Ether LMI ISSU client will not able to send the message to the standby device. |
ethernet-lmi |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
ETHER_LMI_HA-3-SESSION_UNREGISTRY |
3-Error |
Ether LMI ISSU client failed to unregister session information. Error: [dec] [chars] |
The Ether LMI ISSU client failed to unregister session information. |
ethernet-lmi |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ETHER_LMI_HA-3-TRANSFORM |
3-Error |
Ether LMI ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The Ether LMI ISSU client could not transform the specified message type. If the transmit transformation failed the checkpoint message was not sent to the standby device. If the receive transformation failed the checkpoint message was not applied on the standby device. In both cases the Ether LMI state between the active device and the standby device is not identical. |
ethernet-lmi |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
ETHER_MODULE-3-INVALID_DATA_INSTANCE |
3-Error |
interface type [chars] slot [dec] port [dec] vc [dec] : [chars] |
Data required to support the interface is not available. |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
ETHER_MODULE-3-UNSUPPORTED_DATA |
3-Error |
Data conversion error [chars] 0x%X |
An internal software error has occured when converting the data specified in the message from one representation to another. |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
ETHER_PLATFORM_SW-3-BD_NULL |
3-Error |
Unable to get bridge-domain [dec] information for EFP [dec] |
The software dataplane was unable to get the bridge-domain information for the EFP. |
ether-infra |
"This error may be transient. If the error " "persists you may need to reload the router." |
|
ETHER_PLATFORM_SW-3-DOT1AH_CHNK_LCK_FAILED |
3-Error |
Unable to lock memory while learning C-MAC to B-MAC mapping |
The Ethernet Software Platform was unable to lock a particular piece of memory while attempting to learn a C-MAC to B-MAC mapping |
ether-infra |
"This error may be transient. If the error " "persists you may need to reload the router." |
|
ETHER_PLATFORM_SW-3-DOT1AH_DEL_MAP_FAILED |
3-Error |
Unable to remove 802.1ah mapping entry for B-MAC [enet] C-MAC [enet]. |
The Ethernet Software Platform was unable to remove an 802.1ah mapping entry from the tree of entries. |
ether-infra |
"This error may be transient. If the error " "persists you may need to reload the router." |
|
ETHER_PLATFORM_SW-3-DOT1AH_PROC_ENQ_FAILED |
3-Error |
Unable to enqueue a request to learn a C-MAC to B-MAC mapping |
An error occurred while trying to enqueue a request to learn a C-MAC to B-MAC mapping. |
ether-infra |
"This error may be transient. If the error " "persists you may need to reload the router." |
|
ETHER_PLATFORM_SW-3-EFP_CANNOT_CLEAR_DIM |
3-Error |
Unable to clear EFP's encapsulation data |
An error occurred while trying to clear the encapsulation data for an EFP. |
ether-infra |
"Enable debugging with 'debug ethernet service " "instace'. Retry the operation that caused the " "error to see if additional debugging messages " "are provided. If the error persists you may need " "to reload the router." |
|
ETHER_PLATFORM_SW-3-NO_PD_EFP |
3-Error |
Unable to find software platform EFP information for EFP ID [dec] |
The software dataplane was unable to get the platform dependent EFP information for the EFP with the given ID. |
ether-infra |
"This error may indicate a bug in the software " "dataplane implementation. If the error " "occurs after a specific configuration was performed " "then precisely record those configuration steps. " "Contact your Cisco technical support " "representative and provide the gathered " "information." |
|
ETHER_PLATFORM_SW-3-REWRITE_FAILED |
3-Error |
Unable to apply rewrite to packet |
An error occurred while trying to perform an ingress rewrite operation on a frame. |
ether-infra |
"This error may be transient. If the error " "persists you may need to reload the router." |
|
ETHER_SERVICE_IPC-3-IPC_RESP_ERROR |
3-Error |
IPC send response error [chars] |
An error was detected in the response for an IPC message that was transmitted to the peer. |
ether-infra |
"This error could be transient. If this error persists " "copy the error message exactly as it appears " "and report it to your technical support representative." |
|
ETHER_SERVICE_IPC-3-IPC_TRANSMIT_FAILED |
3-Error |
IPC message transmission failure [chars] |
An error was detected when transmitting an IPC message between Standby RP and SP. The failure most likely occurred because of a software error. The message output identifies the type of error that occurred. |
ether-infra |
"This could be a transient error. If this error persists " "copy the error message exactly as it appears and report it " "to your technical support representative." |
|
ETHER_SERVICE_IPC-3-IPCPORT_CREATE |
3-Error |
Unable to create IPC port [chars]. |
Ethernet Service was unable to create an IPC port |
ether-infra |
"Copy the error message exactly as it appears and " "report it to your technical support representative." |
|
ETHER_SERVICE_IPC-3-IPCPORT_REGISTER |
3-Error |
Unable to register IPC port [chars]. |
Ethernet Service was unable to register an IPC port |
ether-infra |
"Copy the error message exactly as it appears and " "report it to your technical support representative." |
|
ETHER_SERVICE_IPC-3-IPCPORT_REMOVE |
3-Error |
Unable to remove IPC port [chars]. |
Ethernet Service was unable to remove an IPC port |
ether-infra |
"Copy the error message exactly as it appears and " "report it to your technical support representative." |
|
ETHER_SERVICE_IPC-3-IPCPROCESSES |
3-Error |
Unable to create IPC processes on [chars]. |
Ethernet Service was unable to create IPC processes |
ether-infra |
"Copy the error message exactly as it appears and " "report it to your technical support representative." |
|
ETHER_SERVICE_IPC-3-IPCSESSION |
3-Error |
Unable to open an IPC session for communicating with [chars]. Error: [chars] |
This is an internal error |
ether-infra |
"Copy the error message exactly as it appears and report it to your" " technical support representative." |
|
ETHER_SERVICE_IPC-3-NOIPCDESC |
3-Error |
Unable to allocate IPC descriptor for Ethernet Service on [chars]. |
This is an internal error |
ether-infra |
"Copy the error message exactly as it appears and report it to your" " technical support representative." |
|
ETHER_SERVICE_IPC-3-NOMEM |
3-Error |
Unable to allocate memory for Ethernet Service on [chars]. |
This is an internal error |
ether-infra |
"Copy the error message exactly as it appears and report it to your" " technical support representative." |
|
ETHER_SERVICE_IPC-3-RMI_CALLBACK |
3-Error |
Ethernet Infra encountered an error while processing a callback from the Resource Manager RMI [chars] |
Ethernet Infra registers with the Resource Manager RMI to |
ether-infra |
"show tech" |
|
ETHER_SERVICE_IPC-3-RMI_FAILED |
3-Error |
Ethernet Infra failed to register with the Resource Manager RMI [chars] |
Ethernet Infra registers with the Resource Manager RMI to |
ether-infra |
"show tech" |
|
ETHER_SERVICE_IPC-4-NOIPCDATA |
4-Warning |
IPC Message has no data area [chars] |
Cannot find data area in an IPC message. This is a warning message no action is required |
ether-infra |
"Copy the error message exactly as it appears and " "report it to your technical support representative." |
|
ETHER_SERVICE_IPC-4-NOIPCPORT |
4-Warning |
IPC port is NULL [chars] |
Ethernet Service cannot send the message as the IPC port information is NULL. This is a warning message no action is required. |
ether-infra |
"Copy the error message exactly as it appears and " "report it to your technical support representative." |
|
ETHER_SERVICE_IPC-4-NOMESSAGE |
4-Warning |
Message is NULL [chars] |
Cannot send the message as the message is NULL. This is a warning message no action is required |
ether-infra |
"Copy the error message exactly as it appears and " "report it to your technical support representative." |
|
ETHER_SERVICE-3-EFP_DEBUG_INIT_FAILURE |
3-Error |
The Ether Infra Trace and Debug Library Failed to initialize successfully due to error: [dec] |
All trace and debug may not work |
ether-infra |
"No Action" |
|
ETHER_SERVICE-3-EFP_INVALID_TYPE |
3-Error |
[chars] : [chars] is INVALID |
invalid type |
ether-infra |
"Copy the error and send it to TAC" |
|
ETHER_SERVICE-3-EFP_NO_MEMORY |
3-Error |
[chars] : memory allocation failed for [chars] |
memory allocation failed |
ether-infra |
"'show proc mem' or 'show buffs' to check if memory \n\or buffer is full. shutdown unused tasks or reset cards usually can recover \n\those memory leak problem. Copy the error and send it to TAC if those actions \n\does not help." |
|
ETHER_SERVICE-3-EFP_NULL_POINTER |
3-Error |
[chars] : [chars] pointer is NULL |
NULL pointer |
ether-infra |
"Copy the error and send it to TAC" |
|
ETHER_SERVICE-3-ETHER_CHAN_SERV_INSTANCE_POLICY_REMOVED |
3-Error |
[chars] service policy [chars] has been removed from service instance [dec] of ethernet channel [chars] due to failure to install the policy on member link [chars]. |
The member link does not support the service policy or installation failed due to resources limitation at the time. |
ether-infra |
"Check for any error message that indicates incompatiblity between " "the policy and the member link. Remove the member link from the " "ethernet channel and reconfigure the policy on the service instance. " "If the problem persists copy the error exactly as it appears and " "report it to your technical support representative." |
|
ETHER_SERVICE-4-UNSUP_MIRPENABLE |
4-Warning |
%% Not supported since \no ethernet mac-flush notification mirp\ command is configured. |
\no ethernet mac-flush notification mirp\ is configured. |
ether-infra |
"Configure \"ethernet mac-flush notification mirp\" command." |
|
ETHER_SERVICE-6-ERR_DISABLED |
6-Information |
[chars] - shutdown service instance [dec] at [chars] |
Service instance shutdown due to errdisable |
ether-infra |
"No Action" |
|
ETHER_SERVICE-6-EVC_STATUS_CHANGED |
6-Information |
status of [chars] changed to [chars] |
EVC status has changed |
ether-infra |
"No Action" |
|
ETHER_SERVICE-6-EVC_VLAN_NOT_CONFIGURED |
6-Information |
VLANs [chars] not configured at [chars] but is in a CEVLAN/EVC map |
VLANs part of the CEVLAN/EVC map for an EVC associated to an interface but the interface doesn't have those VLANs configured |
ether-infra |
"Verify configurations of VLANs on the interface" |
|
ETHER_SERVICE-6-UPDOWN |
6-Information |
Service instance [dec] on interface [chars] changed to [chars] |
Service instance shutdown due to errdisable |
ether-infra |
"No Action" |
|
ETHERCHANNEL_LB-3-MSG_SEND_FAIL |
3-Error |
The load-balance message [dec] has failed to send |
The load-balancing feature has detected an error while trying to send an internal message. |
ether-channel |
"If this message was the result of performing a " "configuration command then try unconfiguring " "and reconfiguring the same command. If the error " "message continues to be displayed then it may " "indicate that the system is low on memory. The " "show memory free command should be used to check " "if the system has sufficient available memory. " "If the system appears to have available memory and " "the error continues to be displayed then please " "contact your Cisco technical support representative " "and provide the representative with the exact error " "message being seen as well as the version of IOS " "being used." |
|
ETHERCHANNEL_LB-3-XDR_MSG_XMIT_FAIL |
3-Error |
Failed to transmit XDR message of size [dec] to slot [dec] |
An error occurred while attempting to send a load-balancing XDR message to the specified slot. |
ether-channel |
"Because the message failed to send the specified " "slot may now be out of sync with the rest of the " "system. To correct the issue the card in the " "specified slot may be rebooted at which point " "the full configuration will be re-synced with the " "card in that slot. If the specified slot is zero " "then that message was intended for cards in all " "slots and the router should be reloaded to re-sync" "the entire system." |
|
ETHERCHANNEL-2-PROXY_IPC_INIT_FAILED |
2-Critical |
QFP Etherchannel Proxy IPC interface initialization failure result: [dec]. |
Cisco internal software error. QFP Etherchannel initialization detected that the Proxy IPC interface initialization failed. The EC Bundle interfaces will not be functional while this condition exists. |
qfp-ethernet keyword:gec |
LOG_STD_ACTION |
|
ETHERCHANNEL-3-INV_PROXY_MSG |
3-Error |
QFP ETHERCHANNEL Proxy received invalid Message ID [dec] |
Cisco internal software error. QFP Etherchannel Proxy received an invalid Message ID. This message will be ignored. |
qfp-ethernet keyword:gec |
LOG_STD_ACTION |
|
ETHERCHANNEL-3-LOCK_ERROR |
3-Error |
QFP EC Lock Failure: retval:[dec] tries[dec] |
Cisco internal software error. QFP EC Lock Failure locking attempt failed |
qfp-ethernet keyword:gec |
LOG_STD_ACTION |
|
ETHERCHANNEL-3-LOCK_STATE_ERROR |
3-Error |
QFP EC Lock State Failure: retval:[dec] |
Cisco internal software error. QFP EC Lock State Failure Illegal lock state |
qfp-ethernet keyword:gec |
LOG_STD_ACTION |
|
ETHERCHANNEL-3-PROXY_IPC_ALLOC_FAIL |
3-Error |
QFP ETHERCHANNEL Proxy [chars] response lost due to buffer allocation |
Cisco internal software error. QFP ETHERCHANNEL Proxy message processing detected a IPC buffer allocation failure during response processing. The associated ETHERCHANNEL interface may not be fully functional as a result of this condition. |
qfp-ethernet keyword:gec |
LOG_STD_ACTION |
|
ETHERCHANNEL-3-PROXY_SID_UPDATE_COMPLETE_ERROR |
3-Error |
QFP EC Proxy [chars] SID Update Complete w/o Preceeding Lock |
Cisco internal software error. QFP EC Proxy message processing detected a Bundle Schedule SID update sequence error. One or more interface schedules could have been affected. |
qfp-ethernet keyword:gec |
LOG_STD_ACTION |
|
ETHERCHANNEL-3-PROXY_SID_UPDATE_LOCK_ERROR |
3-Error |
QFP EC Proxy [chars] Multiple SID Update Locks to same interface |
Cisco internal software error. QFP EC Proxy message processing detected a Bundle Schedule SID update sequence error. One or more interface schedules could have been affected. |
qfp-ethernet keyword:gec |
LOG_STD_ACTION |
|
ETHERNET_EVENT-4-MW_BW_CHANGE |
4-Warning |
Available microwave bandwidth for link with source MAC [chars] link ID [dec] on [chars] has changed due to [chars] current is [dec]Mbps nominal is [dec]Mbps. |
The available microwave bandwidth has changed. The message indicates the reason why the bandwidth changed as well as the currently available bandwidth. If the message indicates that the change was due to VSM then an ITU-T Y.1731 Vendor-Specific Message has been received causing the available microwave bandwidth to be updated. If the message indicates that the change was due to periodic timeout then the local system has not received a VSM within the expected time period and so it has reset the bandwidth back to its nominal value. The current bandwidth represents the bandwidth currently available on the link while the nominal bandwidth represents the maximum bandwidth supported by the link when the microwave signal is not degraded. |
ethernet-cfm |
"If the current bandwidth is unexpectedly less than " "the nominal bandwidth then action may be required " "to restore the microwave bandwidth to its fully " "supported capacity." |
|
ETHERNET_LACP-1-ISSU_NOMEMORY |
1-Alert |
msgtxt_nomemory |
The requested operation could not be accomplished because of a low memory condition. |
lacp |
"Reduce other system activity to ease memory demands. If conditions " "warrant upgrade to a larger memory configuration." |
|
ETHERNET_LACP-3-ISSU_SENDFAILED |
3-Error |
\nLACP ISSU: send message failed rc = [dec]\n |
The sending of a message has failed. This is an informational message only. |
lacp |
LOG_STD_SH_TECH_ACTION |
|
ETHERNET_LACP-4-ISSU_INCOMPATIBLE |
4-Warning |
\nlacp-issu-compat: returned FALSE |
The ISSU compatibility matrix check has failed. This is an informational message only. |
lacp |
LOG_STD_SH_TECH_ACTION |
|
ETHERNET_LACP-4-ISSU_XFORM |
4-Warning |
\n[chars]: failed rc=[chars] |
The ISSU transform has failed. This is an informational message only. |
lacp |
LOG_STD_SH_TECH_ACTION |
|
ETHERNET_LACP-4-RF_CLIENT_BUNDLE |
4-Warning |
\nLACP HA: Unable initiate checkpoint bundle mode.\n |
LACP is unable to initialize checkpoint bundle mode. This is an informational message only. |
lacp |
LOG_STD_SH_TECH_ACTION |
|
ETHERNET_LACP-4-RF_CLIENT_INIT |
4-Warning |
\nLACP HA: Unable to initiate RF client.\n |
LACP is unable to initialize as a RF client. This is an informational message only. |
lacp |
LOG_STD_SH_TECH_ACTION |
|
ETHERNET_MLACP-3-PEER_ICCP_VERSION_INCOMPATIBLE |
3-Error |
Peer ICCP version [dec] is incompatible with local ICCP version [dec]. |
mLACP peer is running with a different version of ICCP. Incompatible ICCP would prevent mLACP from working properly. |
lacp |
"Reboot peer with identical IOS version would " "correct the issue. Compatible ICCP version between " "different IOS images can still be achieved by doing " "show lacp multichassis group on the both devices to " "check if ICCP versions are compatible. If ICCP " "versions are incompatible repeat IOS image loading " " and CLI above until a compatible image is loaded." |
|
ETHERNET_MLACP-3-SYS_CFG_DUPL_ID |
3-Error |
Remote mLACP peer has duplicate mLACP node-id [dec] |
A remote mLACP peer is configured with the same mLACP node-id as this device. |
lacp |
"Reconfigure the mLACP node-id to be unique between the two " "devices with the <CmdBold>mlacp node-id<NoCmdBold> configuration " "command. Refer to the mLACP configuration section of the Cisco " "IOS documentation for more information on configuring mLACP." |
|
ETHERNET_MLACP-3-SYS_CFG_INVALID_ID |
3-Error |
Received invalid mLACP node-id [dec] from peer |
A remote mLACP peer is configured with an invalid mLACP node-id. |
lacp |
"Reconfigure the peer to send a valid mLACP node-id with the " "<CmdBold>mlacp node-id<NoCmdBold> configuration command. Refer " "to the mLACP configuration section of the Cisco IOS documentation " "for more information on configuring mLACP." |
|
ETHERNET_MLACP-4-CORE_CONNECTED |
4-Warning |
mLACP has recovered from a core isolation failure. Attempting to recover [dec] LAGs in redundancy group [dec] |
mLACP has recovered from core isolation and has attempted to recover the LAGs in the redundancy group. |
lacp |
"This message may not require any action. However the " "<CmdBold>show lacp multi-chassis group<NoCmdBold> and " "<CmdBold>show lacp multi-chassis port-channel<NoCmdBold> commands " "may be used to verify the state of the mLACP port-channels. Reference " "the mLACP section of the IOS documentation for details on core isolation " "failures and related configuration commands." |
|
ETHERNET_MLACP-4-CORE_ISOLATION |
4-Warning |
mLACP Core isolation failure: Attempting to failover [dec] LAGs in redundancy group [dec] |
mLACP has detected isolation from the core and has attempted to failover. |
lacp |
"Use the <CmdBold>show interchassis redundancy<NoCmdBold> command to determine " "which core facing interface has triggered the isolation failure. Correct the " "failure for the given interface this will clear the mLACP core isolation " "failure. Reference the mLACP section of the IOS documentation for more " "information on core isolation failures and related configuration commands." |
|
ETHERNET_MLACP-4-ICRM_CLIENT_RECV_BAD_LEN |
4-Warning |
Received an mLACP TLV with bad length [dec] total message length [dec] |
The mLACP TLV length is longer than the total message length. |
lacp |
"Issue the <CmdBold>show version<NoCmdBold> command on the local and remote " "devices to get the versions of IOS that are running. Reference the mLACP section " "of the IOS documentation to verify that mLACP is compatible between the IOS " "versions on the two devices. If the versions are compatible and the message still " "appears then please contact your Cisco technical support representative. Provide " "the representative with the exact message being seen as well as the output of the " "following commands <CmdBold>show version<NoCmdBold> <CmdBold>show run<NoCmdBold> " "<CmdBold>show lacp multi-chassis group<NoCmdBold> and <CmdBold>show lacp " "multi-chassis port-channel<NoCmdBold>." |
|
ETHERNET_MLACP-4-ICRM_CLIENT_RECV_NO_TYPELEN |
4-Warning |
Received an mLACP TLV without a type and/or length field [dec] |
mLACP received an improperly formatted TLV from the peer. As a result the local and peer devices may have mismatched state data. |
lacp |
"Issue the <CmdBold>show version<NoCmdBold> command on the local and remote " "devices to get the versions of IOS that are running. Reference the mLACP " "section of the IOS documentation to verify that mLACP is compatible between " "the IOS versions on the two devices. If the versions are compatible and the " "message still appears then please contact your Cisco technical support " "representative and provide the representative with the exact error message " "being seen as well as the versions of IOS from both devices." |
|
ETHERNET_MLACP-4-ICRM_CLIENT_RECV_REJ |
4-Warning |
Received rejected mLACP TLV from peer with message ID [dec] |
A remote mLACP peer has rejected an mLACP TLV. |
lacp |
"Issue the <CmdBold>show version<NoCmdBold> command on the local and remote " "devices to get the versions of IOS that are running. Reference the mLACP " "section of the IOS documentation to verify that mLACP is compatible between " "the IOS versions on the two devices. If the versions are compatible and the " "message still appears then please contact your Cisco technical support " "representative and provide the representative with the exact error message " "being seen as well as the versions of IOS from both devices." |
|
ETHERNET_MLACP-4-PC_CHANGE |
4-Warning |
mLACP [chars] status changed to [chars] |
A mLACP port-channel state change event has occurred. This might have been caused by a mLACP failure or recovery event on the local or peer POA in the same redundancy group. It is normal to get these messages during provisioning and administrative actions on the mLACP port-channel. |
lacp |
"User should debug further to analyze root cause of the event. Use " "<CmdBold>show redundancy interchassis <NoCmdBold> " "<CmdBold>show lacp multi-chassis port-channel<NoCmdBold> " "<CmdBold>show lacp multi-chassis group<NoCmdBold> and " "<CmdBold>show lacp internal <NoCmdBold> on both POAs to check " "mLACP port-channel health. If any failure exists appropriate " "actions should be taken to recover port-channel from failure. " "If failure persists then please contact your Cisco technical " "support representative and provide the collected information." |
|
ETHERNET_MLACP-4-PEER_DISCONNECT |
4-Warning |
An mLACP peer has disconnected from redundancy group [dec] attempting to reconnect |
mLACP has detected that a peer device from the specified redundancy group has disconnected. mLACP will attempt to reconnect to the device until successful. |
lacp |
"This message is typically caused by a configuration event on the peer router and " "so no action may be necessary. However if this message is unexpected then issue " "the <CmdBold>show redundancy interchassis<NoCmdBold> command on both the local and " "peer mLACP devices to determine which peer member IP has lost communication. Use this " "information to further debug the network communication issue and re-enable communication " "with the peer. Reference the mLACP section of the IOS documentation for more information " "on peer down failures." |
|
ETHERNET_MLACP-4-PEER_DOWN |
4-Warning |
mLACP Peer down failure: Attempting to make [dec] local LAGs active in redundancy group [dec] |
mLACP has detected a peer down failure and has attempted to make the local port-channels become active. |
lacp |
"The peer down failure should be corrected by re-enabling communication " "with the peer mLACP device. Use the <CmdBold>show redundancy interchassis<NoCmdBold> " "command on both the local and peer mLACP devices to determine which peer member IP " "has lost communication. Use this information to further debug the network communication " "issue and re-enable communication with the peer. Reference the mLACP section of the IOS " "documentation for more information on peer down failures." |
|
ETHERNET_MLACP-4-PEER_RECONNECT_FAILED |
4-Warning |
The attempt to reconnect to the peer in redundancy group [dec] has failed |
After an mLACP peer device disconnected an attempt was made to reconnect however that attempt has failed. |
lacp |
"To reinitialize the connection unconfigure <CmdBold>mlacp interchassis group<NoCmdBold> " "from the port-channel and then reconfigure it. After doing that issue " "<CmdBold>show redundancy interchassis<NoCmdBold> to get the peer member IP " "connection status and the mLACP connection state. If the peer member IP " "connection status is not CONNECTED then there is a more basic communication " "issue that needs to be fixed. Otherwise if the peer member IP is CONNECTED but " "the mLACP state is not CONNECTED then there could be a software issue. In that " "case collect the output of <CmdBold>show redundancy interchassis<NoCmdBold> " "<CmdBold>show lacp multi-chassis group<NoCmdBold> and " "<CmdBold>show lacp multi-chassis port-channel<NoCmdBold>. Then please contact your " "Cisco technical support representative and provide the collected information." |
|
ETHERNET_MLACP-4-PEER_UP |
4-Warning |
mLACP has recovered from a peer down failure in redundancy group [dec] |
mLACP is now in communication with the peer device and has recovered from a previous peer down failure. |
lacp |
"This message may not require any action. However the " "<CmdBold>show lacp multi-chassis group<NoCmdBold> and " "<CmdBold>show lacp multi-chassis port-channel<NoCmdBold> commands may be used " "to verify the state of the mLACP port-channels. Reference the mLACP section " "of the IOS documentation for details on peer down failures and related " "configuration commands." |
|
ETHERNET_MLACP-6-PEER_CONNECT |
6-Information |
mLACP peer is now connected in redundancy group [dec] |
This message indicates that the local mLACP device is now connected to a peer device in the specified redundancy group. |
lacp |
"No action is required. To view the peer information the command " "<CmdBold>show lacp multi-chassis port-channel<NoCmdBold> or " "<CmdBold>show lacp multi-chassis group<NoCmdBold> may be issued." |
|
ETHERNET_OAM-2-CRIT_ERR |
2-Critical |
The Ethernet OAM protocol has encountered the critical error: [chars]. |
The protocol has run into a critical error. The reason should be given in the brackets. |
ether-oam |
LOG_STD_ACTION |
|
ETHERNET_OAM-2-GET_BUFFER |
2-Critical |
ETHERNET OAM ISSU client failed to get buffer for message. Error: [dec] [chars] |
The ETHERNET OAM ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation the standby device cannot be brought up properly. |
ether-oam |
"show logging and show checkpoint client" |
|
ETHERNET_OAM-2-INIT |
2-Critical |
ETHERNET OAM ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The ETHERNET OAM ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure there will be downtime during software upgrade or downgrade. |
ether-oam |
LOG_STD_ACTION |
|
ETHERNET_OAM-2-SEND_NEGO_FAILED |
2-Critical |
ETHERNET OAM ISSU client failed to send negotiation message. Error: [dec] [chars] |
The ETHERNET OAM ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation the standby device cannot be brought up properly. |
ether-oam |
"show logging and show checkpoint client" |
|
ETHERNET_OAM-2-SESSION_NEGO |
2-Critical |
ETHERNET OAM ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The ETHERNET OAM ISSU client encountered a 'client negotiation done' state that was unexpected. If a problem occurs with the ISSU session negotiation the standby device cannot be brought up properly. |
ether-oam |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ETHERNET_OAM-2-SESSION_REGISTRY |
2-Critical |
ETHERNET OAM ISSU client failed to register session information. Error: [dec] [chars] |
The ETHERNET OAM ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
ether-oam |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ETHERNET_OAM-3-INVALID_SESSION |
3-Error |
ETHERNET OAM ISSU client does not have a valid registered session. |
The ETHERNET OAM ISSU client does not have a valid registered session. |
ether-oam |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ETHERNET_OAM-3-LOOPBACK_ERROR |
3-Error |
Loopback operation on interface [chars] has encountered an error[chars]. |
Because of the specified error the loopback operation has ended abnormally. |
ether-oam |
LOG_STD_NO_ACTION |
|
ETHERNET_OAM-3-MSG_SIZE |
3-Error |
ETHERNET OAM ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The ETHERNET OAM ISSU client failed to calculate the MTU for the specified message. The ETHERNET OAM ISSU client is not able to send the message to the standby device. |
ether-oam |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
ETHERNET_OAM-3-SESSION_UNREGISTRY |
3-Error |
ETHERNET OAM ISSU client failed to unregister session information. Error: [dec] [chars] |
The ETHERNET OAM ISSU client failed to unregister session information. |
ether-oam |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ETHERNET_OAM-3-TRANSFORM_FAIL |
3-Error |
ETHERNET OAM ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The ETHERNET OAM ISSU client could not transform the specified message type. If the transmit transformation failed the checkpoint message was not sent to the standby device. If the receive transformation failed the checkpoint message was not applied on the standby device. In both cases the ETHERNET OAM state between the active device and the standby device is not identical. |
ether-oam |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
ETHERNET_OAM-4-ISSU_INCOMPATIBLE |
4-Warning |
\nether_oam-issu-compat: returned FALSE |
The compatibility checking has failed |
ether-oam |
LOG_STD_SH_TECH_ACTION |
|
ETHERNET_OAM-5-EVENTTLV |
5-Notice |
[chars] is received from the remote client on interface [chars]. |
An Event TLV is received from the remote OAM client. It must have detected errors in receiving frames from this local interface. |
ether-oam |
LOG_STD_NO_ACTION |
|
ETHERNET_OAM-5-LINK_MONITOR |
5-Notice |
[chars] detected over the last [chars] on interface [chars]. |
A monitored error has been detected to have crossed the user-specified threshold. |
ether-oam |
LOG_STD_NO_ACTION |
|
ETHERNET_OAM-6-CRITICAL_EVENT |
6-Information |
The client on interface [chars] has received a Critical Event indication from its remote peer action = [chars] |
An OAMPDU has been received from the remote client that indicates a Critical Event has occurred. The indicated action will be performed. If the action is error-block the link will go into error-block state where data traffic is blocked but link-oam can still be exchanged. If the action is error-disable the link is brought down. |
ether-oam |
"Investigate the issue on the remote peer" |
|
ETHERNET_OAM-6-CRITICAL_EVENT_CLEAR |
6-Information |
The client on interface [chars] has received a clear of the Critical Event indication from its remote peer action = [chars] |
An OAMPDU has been received from the remote client that indicates that the Critical Event condition previously seen has cleared. If the action was error-block traffic on the link will now be re-enabled. Error-disable state can only be cleared by performing a shut/no shut of the interface. |
ether-oam |
LOG_STD_NO_ACTION |
|
ETHERNET_OAM-6-DYING_GASP |
6-Information |
The client on interface [chars] has received a Dying Gasp indication from its remote peer failure reason = [chars] action = [chars] |
An OAMPDU has been received from the remote client that indicates a Dying Gasp which may signal that the remote client is about to go down. The indicated action will be performed. If the action is error-block the link will go into error-block state where data traffic is blocked but link-oam can still be exchanged. If the action is error-disable the link is brought down. |
ether-oam |
"Investigate the issue on the remote peer" |
|
ETHERNET_OAM-6-DYING_GASP_CLEAR |
6-Information |
The client on interface [chars] has received a clear of the Dying Gasp indication from its remote peer action = [chars] |
An OAMPDU has been received from the remote client that indicates that the Dying Gasp condition previously seen has cleared. If the action was error-block traffic on the link will now be re-enabled. Error-disable state can only be cleared by performing a shut/no shut of the interface. |
ether-oam |
LOG_STD_NO_ACTION |
|
ETHERNET_OAM-6-ENTER_SESSION |
6-Information |
The client on interface [chars] has entered the OAM session. |
Ethernet OAM client on the specified interface has detected a remote client and has entered the OAM session. |
ether-oam |
LOG_STD_NO_ACTION |
|
ETHERNET_OAM-6-EXIT_SESSION |
6-Information |
The client on interface [chars] has left the OAM session. |
Ethernet OAM client on the specified interface has experienced some state change. |
ether-oam |
LOG_STD_NO_ACTION |
|
ETHERNET_OAM-6-LINK_FAULT |
6-Information |
The client on interface [chars] has received a Link Fault indication from its remote peer action = [chars] |
An OAMPDU has been received from the remote client that indicates a Link Fault has been detected. This indicates a fault has occurred in the receive direction of the sending client. The indicated action will be performed. If the action is error-block the link will go into error-block state where data traffic is blocked but link-oam can still be exchanged. If the action is error-disable the link is brought down. |
ether-oam |
"Check the wiring between the two interfaces." |
|
ETHERNET_OAM-6-LINK_FAULT_CLEAR |
6-Information |
The client on interface [chars] has received a clear of the Link Fault indication from its remote peer action = [chars] |
An OAMPDU has been received from the remote client that indicates that the Link Fault condition previously seen has cleared. If the action was error-block traffic on the link will now be re-enabled. Error-disable state can only be cleared by performing a shut/no shut of the interface. |
ether-oam |
LOG_STD_NO_ACTION |
|
ETHERNET_OAM-6-LINK_TIMEOUT |
6-Information |
The client on interface [chars] has timed out and exited the OAM session. |
The Ethernet OAM client on the specified interface has not received any OAMPDUs in the number of seconds for timeout that were configured by the user. The client has exited the OAM session. |
ether-oam |
LOG_STD_NO_ACTION |
|
ETHERNET_OAM-6-LOOPBACK |
6-Information |
Interface [chars] has [chars] the [chars] loopback mode. |
The specified interface has entered or exited loopback mode because of protocol control or an external event such as the interface link going down. |
ether-oam |
LOG_STD_NO_ACTION |
|
ETHERNET_PMLACP-3-PEER_ICCP_VERSION_INCOMPATIBLE |
3-Error |
Peer ICCP version [dec] is incompatible with local ICCP version [dec]. |
P-mLACP peer is running with a different version of ICCP. Incompatible ICCP would prevent P-mLACP from working properly. |
lacp |
"Reboot peer with identical IOS version would " "correct the issue. Compatible ICCP version between " "different IOS images can still be achieved by doing " "show lacp multichassis load-balance group on the both" " devices to check if ICCP versions are compatible. If ICCP " "versions are incompatible repeat IOS image loading " " and CLI above until a compatible image is loaded." |
|
ETHERNET_PMLACP-3-SYS_CFG_DUPL_ID |
3-Error |
Remote P-mLACP peer has duplicate P-mLACP node-id [dec] |
A remote P-mLACP peer is configured with the same P-mLACP node-id as this device. |
lacp |
"Reconfigure the P-mLACP node-id to be unique between the two " "devices with the <CmdBold>mlacp node-id<NoCmdBold> configuration " "command. Refer to the P-mLACP configuration section of the Cisco " "IOS documentation for more information on configuring P-mLACP." |
|
ETHERNET_PMLACP-3-SYS_CFG_INVALID_ID |
3-Error |
Received invalid P-mLACP node-id [dec] from peer |
A remote P-mLACP peer is configured with an invalid P-mLACP node-id. |
lacp |
"Reconfigure the peer to send a valid P-mLACP node-id with the " "<CmdBold>mlacp node-id<NoCmdBold> configuration command. Refer " "to the P-mLACP configuration section of the Cisco IOS documentation " "for more information on configuring P-mLACP." |
|
ETHERNET_PMLACP-4-CORE_CONNECTED |
4-Warning |
P-mLACP has recovered from a core isolation failure. Attempting to recover [dec] ports in redundancy group [dec] |
P-mLACP has recovered from core isolation and has attempted to recover the ports in the redundancy group. |
lacp |
"This message may not require any action. However the " "<CmdBold>show lacp multi-chassis load-balance group<NoCmdBold> and " "<CmdBold>show lacp multi-chassis load-balance port-channel<NoCmdBold> commands " "may be used to verify the state of the P-mLACP port-channels. Reference " "the P-mLACP section of the IOS documentation for details on core isolation " "failures and related configuration commands." |
|
ETHERNET_PMLACP-4-CORE_ISOLATION |
4-Warning |
P-mLACP Core isolation failure: Attempting to failover [dec] ports in redundancy group [dec] |
P-mLACP has detected isolation from the core and has attempted to failover. |
lacp |
"Use the <CmdBold>show interchassis redundancy<NoCmdBold> command to determine " "which core facing interface has triggered the isolation failure. Correct the " "failure for the given interface this will clear the P-mLACP core isolation " "failure. Reference the P-mLACP section of the IOS documentation for more " "information on core isolation failures and related configuration commands." |
|
ETHERNET_PMLACP-4-ICRM_CLIENT_RECV_BAD_LEN |
4-Warning |
Received an P-mLACP TLV with bad length [dec] total message length [dec] |
The P-mLACP TLV length is longer than the total message length. |
lacp |
"Issue the <CmdBold>show version<NoCmdBold> command on the local and remote " "devices to get the versions of IOS that are running. Reference the P-mLACP section " "of the IOS documentation to verify that P-mLACP is compatible between the IOS " "versions on the two devices. If the versions are compatible and the message still " "appears then please contact your Cisco technical support representative. Provide " "the representative with the exact message being seen as well as the output of the " "following commands <CmdBold>show version<NoCmdBold> <CmdBold>show run<NoCmdBold> " "<CmdBold>show lacp multi-chassis load-balance group<NoCmdBold> and <CmdBold>show lacp " "multi-chassis load-balance port-channel<NoCmdBold>." |
|
ETHERNET_PMLACP-4-ICRM_CLIENT_RECV_NO_TYPELEN |
4-Warning |
Received an P-mLACP TLV without a type and/or length field [dec] |
P-mLACP received an improperly formatted TLV from the peer. As a result the local and peer devices may have mismatched state data. |
lacp |
"Issue the <CmdBold>show version<NoCmdBold> command on the local and remote " "devices to get the versions of IOS that are running. Reference the P-mLACP " "section of the IOS documentation to verify that P-mLACP is compatible between " "the IOS versions on the two devices. If the versions are compatible and the " "message still appears then please contact your Cisco technical support " "representative and provide the representative with the exact error message " "being seen as well as the versions of IOS from both devices." |
|
ETHERNET_PMLACP-4-ICRM_CLIENT_RECV_REJ |
4-Warning |
Received rejected P-mLACP TLV from peer with message ID [dec] |
A remote P-mLACP peer has rejected an P-mLACP TLV. |
lacp |
"Issue the <CmdBold>show version<NoCmdBold> command on the local and remote " "devices to get the versions of IOS that are running. Reference the P-mLACP " "section of the IOS documentation to verify that P-mLACP is compatible between " "the IOS versions on the two devices. If the versions are compatible and the " "message still appears then please contact your Cisco technical support " "representative and provide the representative with the exact error message " "being seen as well as the versions of IOS from both devices." |
|
ETHERNET_PMLACP-4-PEER_DISCONNECT |
4-Warning |
An P-mLACP peer has disconnected from redundancy group [dec] attempting to reconnect |
P-mLACP has detected that a peer device from the specified redundancy group has disconnected. P-mLACP will attempt to reconnect to the device until successful. |
lacp |
"This message is typically caused by a configuration event on the peer router and " "so no action may be necessary. However if this message is unexpected then issue " "the <CmdBold>show redundancy interchassis<NoCmdBold> command on both the local and " "peer P-mLACP devices to determine which peer member IP has lost communication. Use this " "information to further debug the network communication issue and re-enable communication " "with the peer. Reference the P-mLACP section of the IOS documentation for more information " "on peer down failures." |
|
ETHERNET_PMLACP-4-PEER_DOWN |
4-Warning |
P-mLACP Peer down failure: Attempting to make [dec] local ports active in redundancy group [dec] |
P-mLACP has detected a peer down failure and has attempted to make the local port-channels become active. |
lacp |
"The peer down failure should be corrected by re-enabling communication " "with the peer P-mLACP device. Use the <CmdBold>show redundancy interchassis<NoCmdBold> " "command on both the local and peer P-mLACP devices to determine which peer member IP " "has lost communication. Use this information to further debug the network communication " "issue and re-enable communication with the peer. Reference the P-mLACP section of the IOS " "documentation for more information on peer down failures." |
|
ETHERNET_PMLACP-4-PEER_RECONNECT_FAILED |
4-Warning |
The attempt to reconnect to the peer in redundancy group [dec] has failed |
After an P-mLACP peer device disconnected an attempt was made to reconnect however that attempt has failed. |
lacp |
"To reinitialize the connection unconfigure <CmdBold>mlacp interchassis group<NoCmdBold> " "from the port-channel and then reconfigure it. After doing that issue " "<CmdBold>show redundancy interchassis<NoCmdBold> to get the peer member IP " "connection status and the P-mLACP connection state. If the peer member IP " "connection status is not CONNECTED then there is a more basic communication " "issue that needs to be fixed. Otherwise if the peer member IP is CONNECTED but " "the P-mLACP state is not CONNECTED then there could be a software issue. In that " "case collect the output of <CmdBold>show redundancy interchassis<NoCmdBold> " "<CmdBold>show lacp multi-chassis load-balance group<NoCmdBold> and " "<CmdBold>show lacp multi-chassis load-balance port-channel<NoCmdBold>. Then please contact your " "Cisco technical support representative and provide the collected information." |
|
ETHERNET_PMLACP-4-PEER_UP |
4-Warning |
P-mLACP has recovered from a peer down failure in redundancy group [dec] |
P-mLACP is now in communication with the peer device and has recovered from a previous peer down failure. |
lacp |
"This message may not require any action. However the " "<CmdBold>show lacp multi-chassis load-balance group<NoCmdBold> and " "<CmdBold>show lacp multi-chassis load-balance port-channel<NoCmdBold> commands may be used " "to verify the state of the P-mLACP port-channels. Reference the P-mLACP section " "of the IOS documentation for details on peer down failures and related " "configuration commands." |
|
ETHERNET_PMLACP-6-PEER_CONNECT |
6-Information |
P-mLACP peer is now connected in redundancy group [dec] |
This message indicates that the local P-mLACP device is now connected to a peer device in the specified redundancy group. |
lacp |
"No action is required. To view the peer information the command " "<CmdBold>show lacp multi-chassis load-balance port-channel<NoCmdBold> or " "<CmdBold>show lacp multi-chassis load-balance group<NoCmdBold> may be issued." |
|
ETHERNET_PROXY-2-PROXY_IPC_INIT_FAILED |
2-Critical |
CPP ETHERNET Proxy IPC interface initialization failure result: [dec]. |
Cisco internal software error. CPP ETHERNET Proxy initialization detected that the IPC interface initialization failed. CPP ETHERNET proxy will not be functional while this condition exists. |
qfp-bb keyword:none |
LOG_STD_ACTION |
|
ETHERNET_PROXY-3-PROXY_BAD_MSG |
3-Error |
CPP ETHERNET Proxy received bad length message type [dec] |
Cisco internal software error. CPP ETHERNET Proxy received a corrupted message from control plane. This message will be ignored. |
qfp-bb keyword:none |
LOG_STD_ACTION |
|
ETHERNET_PROXY-3-PROXY_INV_MSG |
3-Error |
CPP ETHERNET Proxy received invalid message type [dec] |
Cisco internal software error. CPP ETHERNET Proxy received an invalid message type from control plane. This message will be ignored. |
qfp-bb keyword:none |
LOG_STD_ACTION |
|
ETHERNET_PROXY-3-PROXY_IPC_ALLOC_FAILED |
3-Error |
CPP ETHERNET Proxy [chars] message lost due to message buffer allocation failure. |
Cisco internal software error. CPP ETHERNET Proxy message processing detected a message buffer allocation failure. The message is lost as the result of this condition. |
qfp-bb keyword:none |
LOG_STD_ACTION |
|
ETHERNET_PROXY-3-PROXY_IPC_NO_HDLR |
3-Error |
CPP ETHERNET Proxy received unregistered message type [dec] |
Cisco internal software error. CPP ETHERNET Proxy received a message from control plane but there is no registered handler. The message is lost as the result of this condition. |
qfp-bb keyword:none |
LOG_STD_ACTION |
|
ETHERNET_PROXY-3-PROXY_IPC_SEND_FAILED |
3-Error |
CPP ETHERNET Proxy [chars] message lost due to message sent failure result: [dec]. |
Cisco internal software error. CPP ETHERNET Proxy message processing detected a message sent failure. The message is lost as the result of this condition. |
qfp-bb keyword:none |
LOG_STD_ACTION |
|
ETHERNET-1-NOMEMORY |
1-Alert |
msgtxt_nomemory |
Insufficient memory exists to allocate the necessary memory pools. |
- |
"If this message recurs call your technical support representative for assistance." |
|
ETHERNET-1-TXERR |
1-Alert |
[chars]: Fatal transmit error. Restarting... |
A fatal transmit error occurred on the Ethernet line causing the line to be restarted. |
- |
"If this message recurs call your technical support representative for assistance." |
|
ETHERNET-3-ETHERNET_INIT_FAIL |
3-Error |
Dataplane ETHERNET init error for [chars] |
Cisco internal software error. This is likely due to a dataplane memory exhaust |
cpp-ucode keyword:ethernet |
LOG_STD_ACTION |
|
ETHERNET-4-UNSUPINTFC |
4-Warning |
Interface Ethernet[dec] not supported by [chars] image |
The specific ethernet interface is not supported by the operating system currently running. |
- |
"If the hardware configuration is supported by a newer version of the operating system it will be necessary to upgrade the software in order to support this interface." |
|
EVENT_TRACE-3-CLOSE_FILE |
3-Error |
Error closing file [chars] |
The Event Trace subsystem can not close the specified file |
Trace |
"No action required. This will not affect " "system functionality" |
|
EVENT_TRACE-3-CONTINUOUS |
3-Error |
Enable trace before setting continuous display |
The specified event trace must be enabled before continuous display could occurs. |
Trace |
"Enable the specified event trace." |
|
EVENT_TRACE-3-GROUP_ID |
3-Error |
Duplicate registration of group-id [dec] |
Software subsystem is trying to register a group id for event trace which has already been used by another subsystem. |
Trace |
LOG_STD_ACTION |
|
EVENT_TRACE-3-NO_FILENAME |
3-Error |
Dump file not specified. |
No filename has been specified as output for the event trace. |
Trace |
"You must specify the trace dump filename. To specify the trace dump " "filename enter the monitor event-trace comp dump-file filename command " "in global configuration mode" |
|
EVENT_TRACE-3-NO_MEM |
3-Error |
Not enough memory for [dec] trace elements. |
The system memory is insufficient for the number of trace elements specified. |
Trace |
"Reduce the size of the event trace" |
|
EVENT_TRACE-3-NO_TRACE_NAME |
3-Error |
Invalid trace name [chars] |
There is no trace buffer configured by the name entered. |
Trace |
"Check whether there is an event trace buffer " "configured by the name entered and then enter the correct trace " "buffer name." |
|
EVENT_TRACE-3-NUM_ELEM |
3-Error |
Number of trace element = [dec] is greater than number = [dec] allowed |
The number of trace entries exceed the allowed amount |
Trace |
"Reduce the number of trace entries" |
|
EVENT_TRACE-3-OPEN |
3-Error |
[chars]: Trace failed to open |
Initialization of the specified event trace has failed. |
Trace |
LOG_STD_ACTION |
|
EVENT_TRACE-3-OPEN_FILE |
3-Error |
Couldn't open [chars]... |
The Event Trace subsystem could not open a file for the specified event trace dump. |
Trace |
"If a file by the same name already exists rename the dump file or " "remove the existing file from the file system." |
|
EVENT_TRACE-3-RESIZE |
3-Error |
Enable trace before resizing |
The specified event trace must be enabled before resizing occurs. |
Trace |
"Enable the specified event trace." |
|
EVENT_TRACE-3-SIZE_ELEM |
3-Error |
Size of trace element = [dec] is greater than size = [dec] allowed |
The size of the specified individual trace entry is greater than the allowed size. |
Trace |
"Reduce the individual trace entry size so as not " "to exceed the max while initializing the event trace" |
|
EVENT_TRACE-3-SIZE_FILENAME |
3-Error |
Trace filename size = [dec] greater than size = [dec] allowed |
The length of the specified Event Trace filename exceeds the allowed. |
Trace |
"Shorten the filename." |
|
EVENT_TRACE-3-WRITE_FILE |
3-Error |
Error writing to file [chars] |
Event trace is not able to write to the specified filesystem |
Trace |
"The filesystem might not be available. Try " "changing the destination filesystem and dumping there. " "If none work copy the error message exactly as it and " "call your Cisco technical support representative" |
|
EVENT_TRACE-6-ENABLE |
6-Information |
Trace already enabled. |
Specified event trace has already been enabled |
Trace |
LOG_STD_DBG_ACTION |
|
EVENT_TRACE-6-NO_FORMATTER |
6-Information |
[chars]: no formatter provided binary dumping. |
No formatter function was provided during the initialization of the specified event trace. |
Trace |
LOG_STD_NO_ACTION |
|
EVENT-3-INSERT_FAILURE |
3-Error |
Failed to insert [chars] |
The event process failed to insert the newly created row in\n\ its linked list data structure |
snmp |
"Copy the error message exactly as it appears and report it to\n\ your technical support representative." |
|
EVENT-3-NULL_ELEMENT |
3-Error |
Null pointer in the watched queue for [chars] test |
The process was woken up with an NULL element |
snmp |
"Copy the error message exactly as it appears and report it to\n\ your technical support representative." |
|
EVENT-3-NULL_STRUCT |
3-Error |
Null pointer to the [chars] structure |
The process was woken up with an element which had a null pointer to\n\ the test structure |
snmp |
"Copy the error message exactly as it appears and report it to\n\ your technical support representative." |
|
EVENTLIB-3-CPUHOG |
3-Error |
[chars]: [dec]ms Traceback=[chars] |
This error occurs when a particular event consumes an unfair share of the CPU that may degrade overall system response time. |
asr1k-xe-infra |
show platform software process event |
|
EVENTLIB-3-EVFDREAD |
3-Error |
Event notification read failed with err [chars] |
This occurs when we fail to read a thread notify event |
polaris-infra |
LOG_STD_DDTS_TAC_DETAILS |
|
EVENTLIB-3-HISTELEM |
3-Error |
elem[[dec]] event: [chars] [chars] set: %llums unset: %llums hog check: [dec] caller: %p app-info: [chars] |
This event element is part of a CPUHOG or TIMEHOG error providing diagnostic details useful to engineering. Save all element messages along with the HOG error. |
mcp-infra |
LOG_STD_DDTS_TAC_DETAILS |
|
EVENTLIB-3-HISTSUMM |
3-Error |
dispatch start: %llums elapsed time: %llums detected hog: [dec] set count: [dec] |
This event summary is part of a CPUHOG or TIMEHOG error providing diagnostic details useful to engineering. Save this summary message along with the HOG error. |
mcp-infra |
LOG_STD_DDTS_TAC_DETAILS |
|
EVENTLIB-3-RUNHOG |
3-Error |
[chars]: [dec]ms Traceback=[chars] |
This error occurs when a particular event consumes an overall unfair share of the CPU that may degrade overall system response time. |
asr1k-xe-infra |
show platform software process event |
|
EVENTLIB-3-TIMEHOG |
3-Error |
[chars]: %llums Traceback=[chars] |
This error occurs when a particular event takes an unusually long time to complete. This may affect overall system response time. |
asr1k-xe-infra |
show platform software process event |
|
EVENTQ-3-LCON |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
EVPN-3-CORE_ISOLATION |
3-Error |
Bringing down multi-homing access interface [chars] |
EVPN is bringing down the multi-homing access interface due to core isolation failure detected. |
evpn-mgr |
"Diagnose and recover from core isolation failure then EVPN will bring " "the multi-homing access interface up automatically." |
|
EVPN-3-DUP_IP |
3-Error |
Duplicate IP address [chars] EVI [dec] [chars] [dec] detected on [chars] and [chars] |
EVPN has detected a duplicate IP address in the network. This occurs when the same IP address is learned from multiple different MAC addresses more than N times within M seconds where N is the configured IP duplication limit which defaults to 5 and M is the configured IP |
evpn-mgr |
"Locate and remove the duplicate IP address then use the command " "'clear l2vpn evpn ip duplicate <bridge domain ID> <IP address>' to " "resume IP learning for that address." |
|
EVPN-3-DUP_MAC |
3-Error |
Duplicate [chars]MAC address [enet] EVI [dec] [chars] [dec] detected on [chars] and [chars] |
EVPN has detected a duplicate MAC address in the network. This occurs when the same MAC address is learned from both a local port and a remote device more than N times within M seconds where N is the configured MAC duplication limit which defaults to 5 and M is the configured MAC |
evpn-mgr |
"Locate and remove the duplicate MAC address then use the command " "'clear l2vpn evpn mac duplicate <bridge domain ID> <MAC address>' to " "resume MAC learning for that address." |
|
EVPN-3-ES_ENCAP_MISMATCH |
3-Error |
ES route with encapsulation mismatch received from [chars]/[chars] |
Local and remote EVPN instances must have the same encapsulation type. |
evpn-mgr |
"Correct the configuration by changing the encapsulation type of local " "or remote EVPN instance" |
|
EVPN-3-INCOMPATIBLE_MCAST_GROUP |
3-Error |
Incompatible multicast group configuration for L2 VNI [dec] |
A Layer 2 VNI used for EVPN must have not an associated multicast group for Broadcast Unknown Unicast and Multicast traffic when ingress replication is configured. |
evpn-mgr |
"Correct the configuration by removing the " "mcast-group keyword from the 'member vni' command " "in the NVE interface sub-mode." |
|
EVPN-3-INCOMPATIBLE_REPLICATION |
3-Error |
Incompatible replication configuration for EVI [dec] [chars] [dec] |
An EVPN instance with MPLS encapsulation must not be configured if the replication type is static. |
evpn-mgr |
"Correct the configuration by changing the " "replication type configuration to ingress." |
|
EVPN-3-INTERNAL |
3-Error |
Internal error: [chars] |
An internal software error has occurred. |
evpn-mgr |
LOG_STD_ACTION |
|
EVPN-3-MAX_PEERS_EXCEEDED |
3-Error |
Maximum number of peers [dec] exceeded for Ethernet Segment [chars] in |
EVPN has received a peer nexthop update from BGP which would push the number of peers in the Ethernet Segment past the supported limit for single-active redundancy mode. The newly discovered peer will not be added to the peer list so as not to impact current peering and designated forwarder election results. |
evpn-mgr |
"Take one of the PE's out of the Ethernet Segment by modifying or " "removing its ESI configuration. If it's a PE already peering need to " "toggle the access interface or reconfigure ESI on the newly discovered " "peer to ensure it is re-advertised." |
|
EVPN-3-MAX_PEERS_EXCEEDED_ES_DISABLED |
3-Error |
Maximum number of peers [dec] exceeded for Ethernet Segment [chars] in |
EVPN has received a peer nexthop update from BGP which would push the number of peers in the Ethernet Segment past the supported limit for single-active redundancy mode. The Ethernet Segment will be disabled. |
evpn-mgr |
"Take one of the PE's out of the Ethernet Segment by modifying or " "removing its ESI configuration. If it's a PE already peering need to " "toggle the access interface or reconfigure ESI on the newly discovered " "peer to ensure it is re-advertised." |
|
EVPN-3-MISSING_MCAST_GROUP |
3-Error |
Missing multicast group configuration for L2 VNI [dec] |
A Layer 2 VNI used for EVPN must have an associated multicast group for Broadcast Unknown Unicast and Multicast traffic when static replication is configured. |
evpn-mgr |
"Correct the configuration by adding the " "mcast-group keyword to the 'member vni' command " "in the NVE interface sub-mode." |
|
EVPN-3-UNSUPPORTED_MIX_ENCAP |
3-Error |
EVIs with different encapsulation types are not supported in the same Ethernet Segment[[chars]] |
All EVPN instances associated with an Ethernet Segment must have the same encapsulation type. |
evpn-mgr |
"Correct the configuration by changing the encapsulation type of the " "EVPN instances associated with the Ethernet Segment to be the same." |
|
EVPN-5-AA_IRB_TRAFFIC_MAY_DROP |
5-Notice |
Traffic may drop on the CE side depending on the CE behavior |
On the CE side traffic may drop depending on the CE behavior traffic could be hashed to a specific link in the MC-LAG group. |
evpn-mgr |
LOG_STD_NO_ACTION |
|
EVPN-5-CORE_CONNECTED |
5-Notice |
Bringing up multi-homing access interface [chars] |
EVPN has recovered from a core isolation failure and is bringing up the multi-homing access interface. |
evpn-mgr |
LOG_STD_NO_ACTION |
|
EVPN-5-DUP_CLEAR_IP |
5-Notice |
Cleared duplicate IP address [chars] EVI [dec] [chars] [dec] |
EVPN has cleared the duplicate condition on a IP address that was previously detected as a duplicate. |
evpn-mgr |
LOG_STD_NO_ACTION |
|
EVPN-5-DUP_CLEAR_MAC |
5-Notice |
Cleared duplicate MAC address [enet] EVI [dec] [chars] [dec] |
EVPN has cleared the duplicate condition on a MAC address that was previously detected as a duplicate. |
evpn-mgr |
LOG_STD_NO_ACTION |
|
EVPN-5-ES_LOCAL_RED_MOD_CHANGE_NOT_ALLOWED |
5-Notice |
Local redundancy mode change is not allowed for Ethernet Segment [chars] because it has two or more forwarders. |
Local redundancy mode change is not allowed for Ethernet Segments with two or more forwarders. Configuration is updated while local redundancy mode is kept unchanged. Local redundancy mode will be updated when the number of forwarders drops to less than two. |
evpn-mgr |
"Reduce the number of forwarders to less than two to allow local " "redundancy mode change." |
|
EVPN-5-ES_LOCAL_RED_MOD_CHANGED |
5-Notice |
Local redundancy mode has been changed to [chars] for Ethernet Segment [chars]. |
An event has occurred that has caused local redundancy mode to change. |
evpn-mgr |
LOG_STD_NO_ACTION |
|
EVPN-5-L3RIB_CONFLICT |
5-Notice |
Detected a static route already installed for VRF ID destination IP [%lu [chars]] with full prefix length. EVPN will install a static route which may be overridden in RIB by the other static route. |
EVPN installs a static route for learned local and proxy MAC/IPs with the IP as the destination prefix and full prefix length. A static route matching this has already been installed either by the configuration CLI or another application owner. The EVPN one is installed with lower administrative distance and may be overridden by routes with the same prefix length. |
evpn-mgr |
"If an IPv4 or IPv6 static route for this VRF prefix and full prefix " "length has been configured intentionally this message can be ignored. " "If not intentionally remove the configuration so that the EVPN RIB " "entries can be activated." |
|
EVPN-5-PEER_STATUS |
5-Notice |
Peer [chars] [chars] is [chars] |
An event has occurred that has caused the peer to change status |
evpn-mgr |
LOG_STD_NO_ACTION |
|
EVPN-5-VC_STATUS |
5-Notice |
EVPN[[dec] [dec]/[dec]]: VC state [chars] |
An event has occurred that has caused the vc to change status |
evpn-mgr |
LOG_STD_NO_ACTION |
|
EVTMON_PROXY-3-PROXY_IPC_INIT_FAILED |
3-Error |
[dec] |
IPC handler initialization failed. |
qfp-evtmon |
LOG_STD_ACTION |
|
EVTMON_PROXY-4-PROXY_IPC_EVTMON_FEAT_UPDATE_FAILED |
4-Warning |
feature user failed to [chars] because of [chars] |
Event monitor feature user failed to attach or detach. |
qfp-evtmon |
LOG_STD_ACTION |
|
EVTMON_PROXY-4-PROXY_IPC_EVTMON_REC_UPDATE_FAILED |
4-Warning |
event record update failed |
Event monitor failed to attach or detach event record. |
qfp-evtmon |
LOG_STD_ACTION |
|
EVTMON_PROXY-4-PROXY_IPC_INVALID_MSG |
4-Warning |
[hec] |
Received an invalid IPC messages subtype. |
qfp-evtmon |
LOG_STD_ACTION |
|
EWLC_CAPWAP_IDB-3-IFINDEX_ZERO |
3-Error |
[chars] : ifindex is zero for interface [chars]. Unit : [dec] Slot : [dec] |
IFINDEX of a capwap idb is zero. |
- |
"show idb" |
|
EWLC_L2_ISSU-3-BUFFER |
3-Error |
EWLC L2 ISSU client failed to get buffer for message error [dec] |
EWLC L2 ISSU client failed to get buffer for building\n\ a negotiation message. Hence it can send the negotiation\n\ message to the standby unit. When there is a problem in\n\ the negotiaiton the standby unit can not be brought up. |
platform-ha |
"show logging and show checkpoint client" |
|
EWLC_L2_ISSU-3-CAP_INVALID_SIZE |
3-Error |
EWLC L2 ISSU client capability list is empty. |
The EWLC L2 ISSU client capability exchange list size\n\ is invalid. |
platform-ha |
"show issu capability entries <Client_ID>" |
|
EWLC_L2_ISSU-3-CAP_NOT_COMPATIBLE |
3-Error |
EWLC L2 ISSU client capability exchange result incompatible. |
The EWLC L2 ISSU client capability exchange has negotiated\n\ as incompatible with the peer. |
platform-ha |
"show issu negotiated capability <Session_ID>" |
|
EWLC_L2_ISSU-3-CAPABILITY |
3-Error |
EWLC L2 ISSU client [chars] |
EWLC L2 ISSU client observed an error during capability\n\ negotiation. When this error happens there is a mismatch\n\ between the client capability between the active and\n\ standby unit. |
platform-ha |
"show issu capability entries <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated capability <session_id>" |
|
EWLC_L2_ISSU-3-INIT |
3-Error |
EWLC L2 ISSU client initialization failed at [chars] error [chars] |
EWLC L2 ISSU client could not be initiailzed this will\n\ cause catstrophic failure when ISSU upgrade or downgrade\n\ is performed. |
platform-ha |
LOG_STD_SH_TECH_ACTION |
|
EWLC_L2_ISSU-3-MSG_NOT_OK |
3-Error |
EWLC L2 ISSU client message [dec] is not compatible |
EWLC L2 ISSU client received an incompatible message\n\ from the peer unit. Since the message is not compatible\n\ it can be processed by this unit |
platform-ha |
"show issu message group <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
EWLC_L2_ISSU-3-MSG_SIZE |
3-Error |
EWLC L2 ISSU client failed to get the message size for message [dec] |
EWLC L2 ISSU client failed to calculate message size\n\ for the message specified. The EWLC L2 ISSU client will not\n\ be able to send message to the standby unit. |
platform-ha |
"show issu message group <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
EWLC_L2_ISSU-3-POLICY |
3-Error |
EWLC L2 ISSU client message type [dec] is [chars] |
EWLC L2 ISSU client received an message type which it\n\ does not support. The policy is applied to make the session\n\ compatible. |
platform-ha |
"show issu session <client_id>" |
|
EWLC_L2_ISSU-3-SEND_FAILED |
3-Error |
EWLC L2 ISSU client failed to send a negotiation message error [dec] |
EWLC L2 ISSU client could not send a session negotiation\n\ message to the peer. When there is a problem in the\n\ negotiation the standby unit can not be brought up. |
platform-ha |
"show logging and show checkpoint client" |
|
EWLC_L2_ISSU-3-SESSION |
3-Error |
EWLC L2 ISSU client [chars] |
EWLC L2 ISSU client observed an error during a session\n\ negotiation with the peer unit. When there is a problem\n\ with the session the standby unit can not be brought up. |
platform-ha |
"show issu capability entries <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated capability <session_id>" |
|
EWLC_L2_ISSU-3-SESSION_UNREGISTRY |
3-Error |
EWLC L2 ISSU client failed to unregister session information. Error: [dec] [chars] |
The EWLC L2 ISSU client failed to unregister session information. |
platform-ha |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
EWLC_L2_ISSU-3-TRANSFORM |
3-Error |
EWLC L2 ISSU client [chars] transform failed error [chars] |
EWLC L2 ISSU client could not transform the message.\n\ If the transmit transformation failed it means that the\n\ checkpoint message can not be sent to the standby unit.\n\ If the receive transformation failed it means that the\n\ checkpoint message can not be applied on the standby\n\ unit. In both cases the EWLC L2 state will not\n\ be indentical with the active unit. |
platform-ha |
"show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
EWLC_L2-3-BULK_SYNC |
3-Error |
[chars] |
Bulk sync failure the reason for the failure will be provided in the string |
platform-ha |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
EWLC_L2-3-FILE_OPEN_FAILURE |
3-Error |
File [chars] open failed |
File Open failed |
platform-ha |
LOG_STD_SH_TECH_ACTION |
|
EWLC_L2-3-INVALID_MSG_RECEIVED |
3-Error |
Invalid [chars] message received |
A message that is used for state synchronization was not received correctly. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized. |
platform-ha |
LOG_STD_SH_TECH_ACTION |
|
EWLC_L2-3-MAC_FAILURE |
3-Error |
Mac Failure |
NULL MAC |
platform-ha |
LOG_STD_SH_TECH_ACTION |
|
EWLC_L2-3-MALLOC_FAILURE |
3-Error |
[chars] |
Failed to allocated memory for a structure or event |
platform-ha |
LOG_STD_SH_TECH_ACTION |
|
EWLC_L2-3-OIR_FAILURE |
3-Error |
Message:[chars]Error:[dec] |
EWLC L2 failures due to various reasons |
platform-ha |
LOG_STD_SH_TECH_ACTION |
|
EWLC_L2-3-REG_FAILURE |
3-Error |
Message:[chars]Error:[dec] |
Registration Failure |
platform-ha |
LOG_STD_SH_TECH_ACTION |
|
EWLC_PLATFORM-3-PROCESS_CREATE_FAILED |
3-Error |
System resource check failed. |
System resource check failed. System could be running on unsupported hardware resources |
- |
LOG_STD_NO_ACTION |
|
EWLC_PLATFORM-4-FIPS_OBJSTORE_CREATE |
4-Warning |
Creating fips objstore key failed [chars] |
FIPS objstore key create failed |
- |
LOG_STD_NO_ACTION |
|
EWLC_PLATFORM-4-FIPS_OBJSTORE_DELETE |
4-Warning |
Deleting fips objstore key failed [chars] |
FIPS objstore key delete failed |
- |
LOG_STD_NO_ACTION |
|
EWLC_PLATFORM-4-FIPS_OBJSTORE_OPEN |
4-Warning |
Opening fips objstore key failed [chars] |
FIPS Objstore key could not be opened. |
- |
LOG_STD_NO_ACTION |
|
EWLC_PLATFORM-4-FIPS_OBJSTORE_READ |
4-Warning |
Reading fips objstore key failed [chars] |
FIPS objstore key could not be read |
- |
LOG_STD_NO_ACTION |
|
EWLC_PLATFORM-4-FIPS_OBJSTORE_READ_INCORRECT_LEN |
4-Warning |
Reading of objstore key failed due to incorrect length [dec] [dec] |
FIPS objstore key read failed |
- |
LOG_STD_NO_ACTION |
|
EWLC_PLATFORM-4-FIPS_OBJSTORE_WRITE |
4-Warning |
Writing fips objstore key failed [chars] |
FIPS objstore key write failed |
- |
LOG_STD_NO_ACTION |
|
EWLC_PLATFORM-4-REC_CPU |
4-Warning |
System is running with CPUs lower than recommended. Current no of CPUs: [dec] Recommended no of CPUs: [dec] |
System is running with CPUs lower than recommended. Please refer to release notes. |
- |
LOG_STD_NO_ACTION |
|
EWLC_PLATFORM-4-REC_DISK |
4-Warning |
System is running on a disk lower than recommended. Current Disk Size: [dec]GB Recommended Disk Size: [dec]GB |
System is running on a disk lower than recommended. Please refer to release notes. |
- |
LOG_STD_NO_ACTION |
|
EWLC_PLATFORM-4-REC_MEM |
4-Warning |
System is running with memory lower than recommended. Current Memory: [dec]GB Recommended Memory: [dec]GB |
System is running with memory lower than recommended. Please refer to release notes. |
- |
LOG_STD_NO_ACTION |
|
EWLC_PLATFORM-4-UNKNOWN_EVENT |
4-Warning |
Unknown event [dec] [dec] |
Unknown event occurred. |
- |
LOG_STD_NO_ACTION |
|
EWLC_PLATFORM-5-EWC_MESH_DAY0_CONVERSION |
5-Notice |
Conversion of internal AP to bridge mode in progress: [chars] |
The AP mode change steps will be executed once the AP completes day-0 initialization. |
- |
LOG_STD_NO_ACTION |
|
EXAR7503-3-EXAR7503_INIT_ERR |
3-Error |
Exar7503 LIU channel:[dec] init error |
Error present during Exar LIU initialization |
osm-ct3 for CT3 osm-t3e3 for T3/E3 |
LOG_STD_ACTION |
|
EXAR7503-3-EXAR7503_NUM_ERR |
3-Error |
INvalid Exar7503 LIU number error: [chars] |
Error present while inavlid EXAR number present |
osm-ct3 for CT3 osm-t3e3 for T3/E3 |
LOG_STD_ACTION |
|
EXAR7503-3-EXAR7503_PROG_ERR |
3-Error |
Exar7503 LIU programming error: [chars] |
Error present while read/write to Exar LIU |
osm-ct3 for CT3 osm-t3e3 for T3/E3 |
LOG_STD_ACTION |
|
EXFREE-2-EXMEMFREE |
2-Critical |
Free a non allocated ptr [hec] size [dec]. |
Trying to free a memory which not all of it marked as allocated. |
mem |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
EXFREE-2-EXMEMINIT |
2-Critical |
EXMEM [dec]: [chars] |
The requested external memory allocator failed to be initialized.\n\ Reasons are not clear. |
mem |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
EXFREE-2-EXMEMLOCK |
2-Critical |
[chars] detected error ptr [hec] size [dec]. |
Attempting to lock or unlock a memory location which was\n\ either already locked or unlocked. |
mem |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
EXFREE-2-EXMEMPARAM |
2-Critical |
Bad parameter [dec] when calling to the allocator utility |
Illegal parameter is used when called to allocator. may represent \n\ data some corruption. |
mem |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
EXFREE-2-EXMEMRESET |
2-Critical |
EXMEM [dec]: [chars] |
The requested external memory allocator failed to be reset.\n\ Reasons are not clear. |
mem |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
EXFREE-4-EXMALLOCFAIL |
4-Warning |
External memory allocation of [dec] bytes failed from EXMEM [dec] |
The requested memory allocation is not available from the specified\n\ memory pool. The current system configuration network environment or\n\ possibly a software error might have exhausted or fragmented the\n\ router's memory. |
mem |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
EXIT_HANDLER-1-CRASHINFO |
1-Alert |
signo=[dec] |
- |
- |
- |
|
EXPRESS_SETUP-3-UNABLE_TO_RESET_CONFIG |
3-Error |
[chars] |
The system is unable to reset the configuration |
firmware |
LOG_STD_ACTION |
|
EXPRESS_SETUP-5-CONFIG_IS_RESET |
5-Notice |
[chars] |
The configuration is reset and the system will now reboot |
firmware |
LOG_STD_ACTION |
|
EXPRESS_SETUP-6-MODE_BUTTON_RESET_IGNORED |
6-Information |
[chars] |
mode button pressed for more than 10Sec and startup config is present hence not reloading |
firmware |
LOG_NO_ACTION |
|
EXPRESS_SETUP-6-MODE_ENTERED |
6-Information |
- |
Express setup mode is now active |
firmware |
LOG_NO_ACTION |
|
EXPRESS_SETUP-6-MODE_EXITED |
6-Information |
- |
Express setup mode is no longer active |
firmware |
LOG_NO_ACTION |
|
EXPRESSION-3-BADTYPE |
3-Error |
Found data type [hec] in expression should be [chars] type |
While evaluating an expression an operand was found with an unexpected\n\ datatype. Evaluation of this expression has been aborted. |
snmp |
"Copy the error message exactly as it appears and report it to\n\ your technical support representative." |
|
EXPRESSION-3-FAILASSERT |
3-Error |
Assertion failed: [chars] |
An operation within the Expression MIB subsystem encountered\n\ a data value that is out of range or of an unexpected value\n\ indicative of a logic error within the subsystem. |
snmp |
"Copy the error message exactly as it appears and report it to\n\ your technical support representative." |
|
EXTASSIGNER-3-ERRSYNC |
3-Error |
\ Failed to sync tag[dec] to standby CME\n |
- |
- |
- |
|
EXTASSIGNER-3-ERRSYNC2 |
3-Error |
\ Failed to sync re-assign tag [dec] for [dec] to standby CME\n |
- |
- |
- |
|
EXTASSIGNER-3-ERRTAG |
3-Error |
\ Invalid tag[dec]\n |
- |
- |
- |
|
EXTASSIGNER-3-NOACTPHONE |
3-Error |
\ Failed to find the calling phone\n |
- |
- |
- |
|
EXTASSIGNER-3-NOCB |
3-Error |
\ Failed to find the skinnyCB\n |
- |
- |
- |
|
EXTASSIGNER-3-NOMEM |
3-Error |
\ Failed to malloc\n |
- |
- |
- |
|
EXTASSIGNER-3-NULLPTR |
3-Error |
\ Null pointer [chars]:[dec]\n |
- |
- |
- |
|
EXTASSIGNER-6-ASSIGNED |
6-Information |
\ Extension assignment successful for phone:SEP[chars]. New pool[dec]. \ |
Successfully assigned the pool |
- |
LOG_STD_NO_ACTION |
|
EXTASSIGNER-6-UNASSIGNED |
6-Information |
\ Extension unassignment successful for phone:SEP[chars]. \ Unassigned pool[dec].\n |
Successfully unassigned the pool |
- |
LOG_STD_NO_ACTION |
|
Failed to send APS command [hec] to [chars] retcode [hec] |
APS command sending failed |
c7600-sip-200 |
"This is a internal software error. If this " "error happened while configuring APS try " "reconfiguring the interface. If the error " "persists or occurred during normal operation " "decode the traceback and " LOG_STD_ACTION |
- |
- |
|
FALLBACK-3-CACHE_FULL |
3-Error |
Function name [chars]: Cache is full |
Fallback cache has overflowed and unable to dump entries |
- |
"Increase the fallback cache size." |
|
FALLBACK-3-INTERNAL_ERROR |
3-Error |
[chars]: Internal error. |
An internal error occured. |
- |
LOG_STD_NO_ACTION |
|
FALLBACK-3-MALLOC_FAIL |
3-Error |
[chars]: Memory allocation failed. |
Allocation of memory failed. This is possibly due to the fact that system memory pool is exhausted. |
- |
LOG_STD_NO_ACTION |
|
FALLBACK-3-NO_RTP_PORT |
3-Error |
Function name [chars]: No available RTP ports. |
No available voice RTP ports were found. |
- |
LOG_STD_NO_ACTION |
|
FALLBACK-3-NO_STATS |
3-Error |
[chars]: No stats were returned.\n |
No statistic information was returned with probe |
- |
LOG_STD_NO_ACTION |
|
FALLBACK-3-PROBE_FAILURE |
3-Error |
A probe error to [inet] occured - [chars] |
A probe error occured. Possibly responder on remote router is not enabled or no machine is on specified IP |
- |
"Check the destination router." |
|
FALLBACK-3-RTR_CREATE_FAIL |
3-Error |
[chars]: Creation of probe failed. Return code [dec] |
An RTR probe could no be created. This can cause inaccurate ICPIF values and cause VoIP calls to be hairpined when they should not |
- |
LOG_STD_NO_ACTION |
|
FALLBACK-3-RTR_START_FAIL |
3-Error |
[chars]: probe could not be started. Return code [dec] |
An RTR probe could no be started. This can cause inaccurate delay/loss/jitter and icpif values and cause VoIP calls to be hairpined when they should not |
- |
LOG_STD_NO_ACTION |
|
FALLBACK-3-RTR_STATS_FAIL |
3-Error |
[chars]: Could not retrive statistics from the probe. Return code [dec] \n |
Could not retrive RTR statistics from the probe. This can cause inaccurate ICPIF values and cause VoIP calls to be hairpined when they should not |
- |
LOG_STD_NO_ACTION |
|
FALLBACK-4-CACHE_OVERFLOW |
4-Warning |
Function name [chars]: Cache has overflowed. |
Fallback cache has overflowed and dumped 1/4 of the entries. |
- |
"Increase the fallback cache size." |
|
FALLBACK-5-AVBO_PROBE |
5-Notice |
A probe to [inet] is [chars] - codec [chars] icpif [dec] loss [dec] delay [dec] |
AVBO rtr proble status change. |
- |
"use the grace_period option to avoid trasit error" |
|
FALLBACK-5-TEST_PROBE_ALREADY_RUNNING |
5-Notice |
A test probe is already running. |
Only one test probe may run at a time. |
- |
"Wait until the first test probe is finished." |
|
FARM_DSPRM-4-NOC5510WARN |
4-Warning |
dsp service dspfarm can not be configured for this card type. |
There is C549 NM-HDV card configured for dspfarm service.\n\ Only one dspfarm card type is allowed. |
- |
"If C5510 card type dspfarm is desired then remove C549 NM-HDV dspfarm \n\ service and reconfigure dspfarm service for this card. " |
|
FARM_DSPRM-4-NOC5510WARN |
4-Warning |
dsp service dspfarm can not be configured for this card type. |
There is C549 NM-HDV card configured for dspfarm service.\n\ Only one dspfarm card type is allowed. |
- |
"If C5510 card type dspfarm is desired then remove C549 NM-HDV dspfarm \n\ service and reconfigure dspfarm service for this card. " |
|
FARM_DSPRM-6-CALLDROPINFO |
6-Information |
dspfarm active calls on this card dsp [dec] channel [dec] will be dropped. |
The card has been removed. Dspfarm active calls on this card\n\ will be dropped. |
- |
"No action is required." |
|
FARM_DSPRM-6-CALLDROPINFO |
6-Information |
dspfarm active calls on this card dsp [dec] channel [dec] will be dropped. |
The card has been removed. Dspfarm active calls on this card\n\ will be dropped. |
- |
"No action is required." |
|
FARM_DSPRM-6-CARDINSERTINFO |
6-Information |
dspfarm card slot [dec] is inserted. |
dspfarm card type is inserted into the slot. |
- |
"No action is required." |
|
FARM_DSPRM-6-CARDINSERTINFO |
6-Information |
dspfarm card slot [dec] is inserted. |
dspfarm card type is inserted into the slot. |
- |
"No action is required." |
|
FARM_DSPRM-6-CARDREMOVEINFO |
6-Information |
dspfarm card slot [dec] is removed. |
dspfarm card type is remvoed from the slot. |
- |
"No action is required." |
|
FARM_DSPRM-6-CARDREMOVEINFO |
6-Information |
dspfarm card slot [dec] is removed. |
dspfarm card type is remvoed from the slot. |
- |
"No action is required." |
|
FASTBLK-4-CREATE_ERR |
4-Warning |
Fastblk pool creation error: [chars] |
An unexpected error occurred while performing a fastblk memory\n\pool creation operation |
slb |
LOG_STD_RECUR_ACTION |
|
FASTBLK-4-DEALLOC_ERR |
4-Warning |
Fastblk deallocation error: [chars] |
An unexpected error occurred while performing a fastblk memory\n\deallocation operation |
slb |
LOG_STD_RECUR_ACTION |
|
FASTBLK-4-GROW_ERR |
4-Warning |
Fastblk pool growth error: [chars] |
An unexpected error occurred while performing a fastblk memory\n\pool growth operation |
slb |
LOG_STD_RECUR_ACTION |
|
FASTBLK-4-QUEUE_ERR |
4-Warning |
Fastblk queue error: [chars] |
An unexpected error occurred while performing a fastblk memory\n\queue operation |
slb |
LOG_STD_RECUR_ACTION |
|
FASTBLK-4-SHRINK_ERR |
4-Warning |
Fastblk pool shrink error: [chars] |
An unexpected error occurred while performing a fastblk memory\n\pool shrink operation |
slb |
LOG_STD_RECUR_ACTION |
|
FASTBLK-4-WARNING |
4-Warning |
Unexpected condition: [chars] |
An unexpected condition was detected while performing a fastblk memory\n\operation |
slb |
LOG_STD_RECUR_ACTION |
|
FASTHELLO-2-FH_DOWN |
2-Critical |
Fast-Hello interface [chars] lost dual-active detection capability\n |
FASTHELLO STATUS CHANGED to DOWN with more detail status |
cat4k-vss |
LOG_STD_NO_ACTION |
|
FASTHELLO-3-FH_MANAGED_CHUNK_FAILED |
3-Error |
Unable to create managed chunk\[chars]\ |
Unable to create the specified watched boolean due to unknown reasons |
cat4k-vss |
LOG_STD_NO_ACTION |
|
FASTHELLO-3-FH_QUEUE_CREATE_FAILED |
3-Error |
Unable to create watched queue \[chars]\ |
Unable to create the specified watched queue because of unknown reasons |
cat4k-vss |
LOG_STD_NO_ACTION |
|
FASTHELLO-3-REGISTRY_ADD_ERR |
3-Error |
Failure in adding to [chars] registry |
Could not add a function to the registry |
cat4k-vss |
LOG_STD_NO_ACTION |
|
FASTHELLO-5-FH_DUAL_ACTIVE_CAP |
5-Notice |
Fast-Hello interface [chars] became dual-active detection capable\n |
FASTHELLO STATUS became dual-active detection capable with more detail status |
cat4k-vss |
LOG_STD_NO_ACTION |
|
FASTHELLO-5-FH_UP |
5-Notice |
Fast-Hello interface [chars] status changed to link up\n |
FASTHELLO STATUS CHANGED to UP with more detail status |
cat4k-vss |
LOG_STD_NO_ACTION |
|
FASTHELLO-6-FH_BAD_CONFIG |
6-Information |
Fast-hello PDU received on unconfigured interface. Peer_slot: [dec]Peer_port: [dec] |
Informational messages regarding the configuration of the dual-active fast-hello interface |
cat4k-vss |
"Investigate and correct this misconfiguration" |
|
FASTHELLO-6-FH_DIFF_DOMAIN |
6-Information |
Fast-hello PDU received from different domain. Peer_slot: [dec]Peer_port: [dec] |
Informational messages regarding the configuration of the dual-active fast-hello interface |
cat4k-vss |
"Investigate and correct this misconfiguration" |
|
FASTHELLO-6-FH_SAME_SWITCH |
6-Information |
Fast-hello PDU received from interface configured on same switch. Slot: [dec]Port: [dec] |
Informational messages regarding the configuration of the dual-active fast-hello interface |
cat4k-vss |
"Investigate and correct this misconfiguration" |
|
FASTHELLO-6-FH_VERSION_MISMATCH |
6-Information |
Local switch protocol version :[dec] Peer switch protocol version : [dec] |
Informational messages regarding the software versions running on the switch |
cat4k-vss |
LOG_STD_ACTION |
|
FB_COREDUMP-3-NOMEMORY |
3-Error |
No Memory or buffer for [chars] to be send to [dec] |
Sufficient memory was unavailble for Router Shelf to send any command or \n\ acknowledment to the feature boards. |
- |
LOG_STD_ACTION |
|
FDDI-1-NOMEMORY |
1-Alert |
msgtxt_nomemory |
- |
mid-fddi |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
FDDI-3-BADSLOT |
3-Error |
Unit [dec] Slot [dec] does not exist. |
The main processor detects an invalid slot location for one of the\n\ network interface cards. This should never happen. |
mid-fddi |
"Call your technical support representative about obtaining a\n\ replacement card." |
|
FDDI-3-BADUNIT |
3-Error |
msgtxt_badunit |
This error message is displayed when the system cannot find\n\ the chipset registers where it expects them to be.\n\ This is most likely a hardware error. |
mid-fddi |
LOG_STD_SH_TECH_ACTION |
|
FDDI-3-FDDIFAIL |
3-Error |
Interface [chars] [chars] [chars] = [hex] |
The FDDI interface failed. |
mid-fddi |
"Save the output of the error message and call your technical support\n\ representative for assistance." |
|
FDDI-3-FDDIFAIL2 |
3-Error |
Interface [chars] [chars] [chars] = [hex] [chars] = [hex] |
The FDDI interface failed. This is the second line of the preceding\n\ FDDIFAIL message. This line contains debug information. |
mid-fddi |
"Save the output of the error message and call your technical support\n\ representative for assistance." |
|
FDDI-3-NOCAM |
3-Error |
Unit [dec] No CAM exists for this interface. |
A hardware or software error occurred. |
mid-fddi |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
FEC_ISSU-3- BUFFER |
3-Error |
FEC ISSU client failed to get buffer for message error [dec] |
FEC ISSU client failed to get buffer for building a negotiation message. Hence it can send the negotiation message to the standby unit. When there is a problem in the negotiaiton the standby unit can not be brought up. |
L2 |
"show logging and show checkpoint client" |
|
FEC_ISSU-3- CAPABILITY |
3-Error |
FEC ISSU client [chars] |
FEC SWITCH ISSU client observed an error during capability negotiaiton. When this error happens there is a mismatch between the client capability between the active and standby unit. |
L2 |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
FEC_ISSU-3- INIT |
3-Error |
FEC ISSU client initialization failed at [chars] error [chars] |
FEC ISSU client could not be initiailzed this will cause catstrophic failure when ISSU upgrade or downgrade is performed. |
L2 |
LOG_STD_SH_TECH_ACTION |
|
FEC_ISSU-3- MSG_NOT_OK |
3-Error |
FEC ISSU client message [dec] is not compatible |
FEC ISSU client received an incompatible message from the peer unit. Since the message is not compatible it can be processed by this unit |
L2 |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
FEC_ISSU-3- MSG_SIZE |
3-Error |
FEC ISSU client failed to get the message size for message [dec] |
FEC ISSU client failed to calculate message size for the message specified. The OIR ISSU client will not be able to send message to the standby unit. |
L2 |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
FEC_ISSU-3- POLICY |
3-Error |
FEC ISSU client message type [dec] is [chars] |
FEC ISSU client received an message type which it does not support. The policy is applied to make the session compatible. |
L2 |
"show issu session <client_id>" |
|
FEC_ISSU-3- SEND_FAILED |
3-Error |
FEC ISSU client failed to send a negotiation message error [dec] |
FEC ISSU client could not send a session negotiation message to the peer. When there is a problem in the negotiation the standby unit can not be brought up. |
L2 |
"show logging and show checkpoint client" |
|
FEC_ISSU-3-SESSION |
3-Error |
FEC ISSU client [chars] |
FEC ISSU client observed an error during a session negotiation with the peer unit. When there is a problem with the session the standby unit can not be brought up. |
L2 |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
FEC_ISSU-3- SESSION_UNREGISTRY |
3-Error |
FEC ISSU client failed to unregister session information. Error: [dec] [chars] |
The FEC ISSU client failed to unregister session information. |
L2 |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
FEC_ISSU-3- TRANSFORM |
3-Error |
FEC ISSU client [chars] transform failed error [chars] |
FEC ISSU client could not transform the message. If the transmit transformation failed it means that the checkpoint message can not be sent to the standby unit. If the receive transformation failed it means that the checkpoint message can not be applied on the standby unit. In both cases the FEC state will not be indentical with the active unit. |
L2 |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
FFP_HW_IRQ-3-NON_FATAL_INTERRUPT |
3-Error |
%lu errors in the last %lu seconds |
Accumulation of Cavium hardware-generated error |
cpp-ucode |
LOG_STD_ACTION |
|
FFP_HW_IRQ-3-TOO_MANY_NON_FATAL_INTERRUPTS |
3-Error |
- |
Aborting due to too many Cavium hardware-generated errors |
cpp-ucode |
LOG_STD_ACTION |
|
FGPT-3-INCONSISTENT_FGPT |
3-Error |
[container fingerprint: [chars]] [nvram fingerprint: [chars]] [chars] |
Fingerprint inconsistency is detected between the license file in this VM and nvram configuration |
virt-infra |
LOG_STD_NO_ACTION |
|
FGPT-6-EVENT |
6-Information |
[container fingerprint: [chars]] [nvram fingerprint: [chars]] [chars] |
Normal container fingerprint event in system initialization |
virt-infra |
LOG_STD_NO_ACTION |
|
FHRP_LOG_ERROR-3-FHRP_LOG |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
FHRP_LOG_INFO-6-FHRP_LOG |
6-Information |
ERRMSG_NOFLAGS |
- |
- |
- |
|
FHRP_LOG_WARN-4-FHRP_LOG |
4-Warning |
ERRMSG_NOFLAGS |
- |
- |
- |
|
FHRP-3-ERROR |
3-Error |
Internal error [chars] |
An internal software error occurred. |
fhrp |
LOG_STD_ACTION |
|
FHRP-4-WARN |
4-Warning |
Internal warning [chars] |
An internal software warning occurred. |
fhrp |
LOG_STD_ACTION |
|
FHRP-6-INFO |
6-Information |
Internal info [chars] |
An internal software information message occurred. |
fhrp |
LOG_STD_ACTION |
|
FHS-3-FHS_CLASSIFY_FAIL |
3-Error |
Dataplane FHS classification error for interface [chars] |
Cisco internal software error. The dataplane was unable to complete processing of FHS Snoop due to a classification failure. This is likely due to a data initialization error |
cpp-ucode keyword:fhs |
LOG_STD_ACTION |
|
FHS-3-FHS_FILTER_FAIL |
3-Error |
Dataplane FHS filter error for interface [chars] |
Cisco internal software error. The FHS pktsb shouldn't be set in use before. This is likely due to a data initialization error |
cpp-ucode keyword:fhs |
LOG_STD_ACTION |
|
FHS-3-FHS_INIT_FAIL |
3-Error |
Dataplane FHS init error for [chars] |
Cisco internal software error. This is likely due to a dataplane memory exhaust |
cpp-ucode keyword:fhs |
LOG_STD_ACTION |
|
FHS-3-FHS_MISS_ACTION_FAIL |
3-Error |
Dataplane FHS miss action error for interface [chars] |
Cisco internal software error. The dataplane was unable to complete processing of FHS Snoop due to a invalid miss action. This is likely due to a data initialization error |
cpp-ucode keyword:fhs |
LOG_STD_ACTION |
|
FIB-2-DFIBSWITCH |
2-Critical |
Error trying to turn on Distributed CEF without CEF on |
IPV4FIB_INTERNAL_ERROR |
IPV4FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
FIB-2-FIB_OVERLENGTH_XDR |
2-Critical |
Overlength CEF XDR message - len [dec] > [dec] from [chars] |
An internal software error occurred preventing the sending of an CEF XDR message. |
IPV4FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
FIB-2-FIBDISABLE |
2-Critical |
Fatal error slot [chars]: [chars] |
An internal software error has occurred because of an IPC problem between the LC and the RP. CEF switching has been disabled on the specified slot. |
IPV4FIB_DDTS_COMPONENT |
"Enter the <bold>clear cef linecard [slot no]<nobold> command " "then check the status of the line card by entering the " "<bold>show cef linecard<nobold> command. If the status shows " "that the line card is still disabled disable and re-enable DCEF " "and check the status of the line card again. " LOG_STD_RECUR_ACTION |
|
FIB-2-FIBDOWN |
2-Critical |
CEF has been disabled due to a low memory condition. It can be re-enabled by configuring \ip cef [distributed]\ |
CEF was disabled because of a low memory condition. |
IPV4FIB_DDTS_COMPONENT |
"Reduce other system activity to ease memory demands. If conditions " "warrant upgrade the RP so that it has more DRAM." |
|
FIB-2-FIBFEATSESINIT |
2-Critical |
Error initializing CEF repop feature session queue |
Initialization of a CEF feature session queue could not be accomplished because of a low memory condition. |
IPV4FIB_DDTS_COMPONENT |
"Reduce other system activitiy to ease memory demands. If conditions " "warrant upgrade to a larger memory configuration." |
|
FIB-2-IDBQINIT |
2-Critical |
Error initializing CEF IDB queue |
Initialization of the CEF IDB queue could not be accomplished because of a low memory condition. |
IPV4FIB_DDTS_COMPONENT |
"Reduce other system activitiy to ease memory demands. If conditions " "warrant upgrade to a larger memory configuration." |
|
FIB-2-LINECARDINIT |
2-Critical |
Error initializing CEF Linecard queue |
Initialization of the CEF linecard queue could not be accomplished because of a low memory condition. |
IPV4FIB_DDTS_COMPONENT |
"Reduce other system activitiy to ease memory demands. If conditions " "warrant upgrade to a larger memory configuration." |
|
FIB-2-XDRINIT |
2-Critical |
Error initializing CEF xdr chunks |
Initialization of the CEF xdr chunks could not be accomplished because of a low memory condition. |
IPV4FIB_DDTS_COMPONENT |
"Reduce other system activitiy to ease memory demands. If conditions " "warrant upgrade to a larger memory configuration." |
|
FIB-3-FIBBADXDRSLOT |
3-Error |
Invalid XDR slot. Type/len/slot [dec]/[dec]/[chars]. XDR at 0x%08x |
IPV4FIB_INTERNAL_ERROR |
IPV4FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
FIB-3-FIBPENDINGLIST |
3-Error |
Error queueing interface [chars] to CEF pending event list. |
Queueing an interface to the CEF pending up event list failed |
IPV4FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
FIB-3-FIBSBINIT |
3-Error |
Error initializing [chars] subblock data structure. [chars] |
Initialization of the specified CEF subblock data structure could not be accomplished. |
IPV4FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
FIB-3-FIBSBNOFN |
3-Error |
Missing [chars] subblock [chars] function for [chars] |
Functions for distributing this subblock are missing from the image. |
IPV4FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
FIB-3-FIBXDRLEN |
3-Error |
Invalid XDR length. Type [dec][chars]. XDR/buffer len [dec]/[dec] |
IPV4FIB_INTERNAL_ERROR |
IPV4FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
FIB-3-INVALIDSTATE |
3-Error |
Slot [chars] in invalid transition from [chars] to [chars] |
An internal software error ocurred. Linecard is in incorrect state |
IPV4FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
FIB-3-MAC_ACCT |
3-Error |
[chars]: [chars] |
IPV4FIB_INTERNAL_ERROR |
IPV4FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
FIB-3-PREC_ACCT |
3-Error |
[chars]: [chars] |
IPV4FIB_INTERNAL_ERROR |
IPV4FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
FIB-4-FIBCBLK |
4-Warning |
Missing cef table for tableid [dec] during [chars] event |
IPV4FIB_INTERNAL_ERROR |
IPV4FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
FIB-4-FIBEVENT |
4-Warning |
Invalid event. Type [chars] event [dec] |
IPV4FIB_INTERNAL_ERROR |
IPV4FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
FIB-4-FIBLCTUNSEQ |
4-Warning |
[chars] Error Initializing/Updating Linecard Tunnel Configuration |
Configuration of a Tunnel on this linecard may not have been successful because of an internal software error. |
IPV4FIB_DDTS_COMPONENT |
"Reconfigure the Tunnel concerned. If problem persists copy the message " "exactly as it appears and report it to your technical support " "representative." |
|
FIB-4-FIBSPECIALPREFIX |
4-Warning |
Invalid Special Prefix Type. Type [dec] |
IPV4FIB_INTERNAL_ERROR |
IPV4FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
FIB-4-FIBXDRINV |
4-Warning |
Invalid format. [chars] [chars] [dec] |
IPV4FIB_INTERNAL_ERROR |
IPV4FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
FIB-6-FIBLCTUNDELSEQ |
6-Information |
Update received on a linecard for a deleted tunnel[chars] - |
An update was received on a linecard for a tunnel that has already been deleted and the update was ignored. |
IPV4FIB_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
FILESYS_RFS-3-IPC |
3-Error |
[chars] [chars]: msg_type [[dec]] sub_type [[dec]]: IPC error [[chars]] |
RFS operation failed due to an IPC error. |
- |
- |
|
FILESYS_RFS-4-RFS_REQUEST_TIMEOUT |
4-Warning |
Timeout has occurred while executing the RFS request on file [chars] [[dec]]. |
A RFS request is sent to server from the client. While executing the request on the server side timeout has occurred at the client side. |
- |
LOG_STD_NO_ACTION |
|
FILESYS-3-FLASH |
3-Error |
[chars] [chars] error [dec] |
A file system error has occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
FILESYS-3-IPC |
3-Error |
[chars] [chars]: IPC error [[chars]] |
RFS operation failed due to an IPC error. |
- |
- |
|
FILESYS-4-CLPDINT |
4-Warning |
Management interrupts are [chars] for pcmcia device in socket [dec]. [chars] |
A faulty PCMCIA flash device might be generating spurious insert or remove interrupts continiously. The pcmcia controller will be set temporarily to disable interrupt generation and will be reenabled after a few seconds. This is to avoid storming CPU with spurious interrupts. If the alternate pcmcia device is |
- |
"Replace the pcmcia flash device with an alternate one" |
|
FILESYS-4-RCSF |
4-Warning |
[chars] [dec] <[chars]> |
A Running config sync file error has occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
FILESYS-5-CFLASH |
5-Notice |
Compact flash card [chars] [chars] |
A file system's status has changed. Follow any instructions provided with the message. |
- |
- |
|
FILESYS-5-DEV |
5-Notice |
PCMCIA flash card [chars] [chars] |
A file system's status has changed. Follow any instructions provided with the message. |
- |
LOG_STD_NO_ACTION |
|
FILESYS-5-IFLASH |
5-Notice |
Internal Flash [chars] [chars] |
A file system's status has changed. Follow any instructions provided with the message. |
- |
LOG_STD_NO_ACTION |
|
FILESYS-5-MISMATCH |
5-Notice |
[chars] device programming algorithm mismatch detected reformat is recommended |
The flash device programming algorithm written to the device when the flash was formatted is different from what the current running software detected. A reformat of the flash device will solve the problem. |
- |
LOG_STD_NO_ACTION |
|
FILESYS-5-UNKNDEV |
5-Notice |
Unknown device [chars] [chars] |
A file system's status has changed. Follow any instructions provided with the message. |
- |
LOG_STD_NO_ACTION |
|
FLASH-3-CISERR |
3-Error |
Error reading cis of Device [dec] : [dec] bytes read instead of [dec] bytes |
Error was detected in reading the cis of device. |
high-flash |
"Report this error to your technical support representative." |
|
FLASH-3-DEVERR |
3-Error |
Error accessing the device : Device number = [dec] Error number = [dec] |
Error was detected in accessing the device. |
high-flash |
"Report this error to your technical support representative." |
|
FLASH-4-CLPDINT |
4-Warning |
Management interrupts are [chars] for pcmcia device in socket [dec]. [chars] |
A faulty PCMCIA flash device might be generating spurious insert or remove interrupts continiously. The pcmcia controller will be set temporarily to disable interrupt generation and will be reenabled after a few seconds. This is to avoid storming CPU with spurious interrupts. If the alternate pcmcia device is |
- |
"Replace the pcmcia flash device with an alternate one" |
|
FLASH-4-SIMM |
4-Warning |
System Flash Simms unequal. Simm1: [dec]M Simm2: [dec]M |
The System has detected an unsupported flash configuration. |
- |
"Replace Flash Simms with equal sizes or remove Simm from System " "Flash Slot two." |
|
FLEX_DNLD-1-INCORRECT_DSP_ID |
1-Alert |
AIM VOICE at slot [dec] receives data from incorrect DSP-ID [dec]. |
The DSP ID provided by FPGA for download is not valid. |
- |
" Call your technical support representative for assistance." |
|
FLEX_DNLD-1-NO_RING_DESCRIPTORS |
1-Alert |
No more ring descriptors available on slot [dec] dsp [dec]. |
The dspfw dnld driver cannot queue messages upto the egress queue for FPGA to transmit. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative. Reset the DSP's on this port \n\ module." |
|
FLEX_DNLD-1-NOPCIMEMORY |
1-Alert |
VPM [dec]/[dec] PCI memory unavailable. |
The router or access server could not allocate memory for the\n\ descriptors. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
FLEX_DNLD-1-TOOBIG |
1-Alert |
[chars] packetsize [dec] too big. |
A packet greater than the 264 bytes received on this interface. |
- |
"The system should recover. No action is required.\n\ \n\ If the problem reccurs it indicates an error that might be\n\ related to data traffic patterns. Copy the error message exactly as it\n\ appears and report it to your technical support representative." |
|
FLEX_DNLD-3-ERROR_ANALYZE |
3-Error |
Error analyzing the device in slot [dec]. |
The Port module in this slot could not be recognized. |
- |
"Power down reinsert Port Module and reboot.\n\ If message recurs call your technical support representative for\n\ assistance." |
|
FLEX_DNLD-3-ERROR_FIRMWARE_DNLD |
3-Error |
DSP firmware download fails for slot [dec] dsp_id [dec] |
Error initializing the DSP with the application firmware. |
- |
" Power down reinsert Port Module and reboot.\n\ If message recurs call your technical support representative for\n\ assistance." |
|
FLEX_DNLD-3-NO_FIRMWARE_DNLD |
3-Error |
No DSP firmware download invoked for slot [dec] no DSPs on the card |
No DSP on the card. |
- |
"Plug in DSP on the Network Module" |
|
FLEXDSPRM-3-TDM_CONNECT |
3-Error |
failed to connect voice-port [dec]/[dec]/[dec] to dsp_channel[dec]/[dec]/[dec] |
TDM connection between Analog/VWIC and the DSP has failed |
c2800 or c3800 |
LOG_STD_ACTION |
|
FLEXDSPRM-3-UNSUPPORTED_CODEC |
3-Error |
codec [chars] is not supported on dsp [dec]/[dec] |
Call failed due to the dsp does not support the codec. |
PVDM3 |
"Check dsp capability and make the call on supported dsp" |
|
FLEXDSPRM-5-CB_UPDOWN |
5-Notice |
Channel Bank [chars] state is [chars] |
Channel Bank status has been changed |
guido |
"See if the voice ports in the channel bank are UP" |
|
FLEXDSPRM-5-OUT_OF_RESOURCES |
5-Notice |
[chars] |
Flex DSPRM temporarily fail to allocate a DSP for this call. A oversubscription has happened and the current free DSP MIPS/Credits are not sufficient to admit a new call. |
hdv2 or pvdm3 |
"Check availability of router DSP resource" " and DSP sharing configurations" |
|
FLEXDSPRM-5-TDM_SLOT |
5-Notice |
voice channel is being shared from slot [dec]. Configure network-clock-participate slot [dec] |
Configure network-clock-participate slot for sharing DSPs |
c2800 or c3800 |
LOG_STD_ACTION |
|
FLEXDSPRM-6-DSP_USAGE |
6-Information |
DSP [chars] usage has reached [dec]%% |
Usage of DSP resources has reached a certain percentage. |
pvdm3 |
"Examine whether or not enough " "DSP resources are reserved." |
|
FLEXVPN-4-FLEXVPN_FAILED_TO_CONNECT |
4-Warning |
[chars] |
FlexVPN session failed to come up FlexVPN is stuck in a state waiting for an event posting a disconnect message to recover. |
- |
"" |
|
FLEXVPN-6-FLEXVPN_CONNECTION_DOWN |
6-Information |
[chars] |
FlexVPN connection is being closed. The IPsec and IKE security associations will also be brought down along with it. |
- |
"" |
|
FLEXVPN-6-FLEXVPN_CONNECTION_UP |
6-Information |
[chars] |
FlexVPN connection is up for the client mentioned. Both IPsec and IKE security Associations are up now. |
- |
"" |
|
FLOWMON-1-ALERT_CRI_CLEAR |
1-Alert |
[[chars]]: SRC_IP:[inet] SRC_PORT:%lu DST_IP:[inet] DST_PORT:%lu [chars][chars] [chars] [chars] |
Generated when the Flow monitoring threshold has gone below the configured limit and the condition is being cleared |
flomon |
"NA" |
|
FLOWMON-1-ALERT_CRI_SET |
1-Alert |
[[chars]]: SRC_IP:[inet] SRC_PORT:%lu DST_IP:[inet] DST_PORT:%lu [chars][chars] [chars] [chars] |
Generated when the Flow monitoring threshold has crossed the configured limit and the condition is being set |
flomon |
"NA" |
|
FLOWMON-2-ALERT_ERROR_CLEAR |
2-Critical |
[[chars]]: SRC_IP:[inet] SRC_PORT:%lu DST_IP:[inet] DST_PORT:%lu [chars][chars] [chars] [chars] |
Generated when the Flow monitoring threshold has gone below the configured limit and the condition is being cleared |
flomon |
"NA" |
|
FLOWMON-2-ALERT_ERROR_SET |
2-Critical |
[[chars]]: SRC_IP:[inet] SRC_PORT:%lu DST_IP:[inet] DST_PORT:%lu [chars][chars] [chars] [chars] |
Generated when the Flow monitoring threshold has crossed the configured limit and the condition is being set |
flomon |
"NA" |
|
FLOWMON-2-FLOW_ALERT |
2-Critical |
Performance_Traffic_ALERT[[chars]]: [[chars]] |
Generated when the Flow monitoring alert are detected |
flomon |
"NA" |
|
FLOWMON-2-FLOW_THRESHOLD_EXCEEDED |
2-Critical |
Performance_Traffic_TCA[[chars]]: Exceeded configured [dec] current [dec] |
Generated when the Flow monitoring threshold has crossed the configured limit |
flomon |
"NA" |
|
FLOWMON-2-FLOW_THRESHOLD_RANGE_EXCEEDED |
2-Critical |
Performance_Traffic_TCA[[chars]]: Exceeded configured range[dec] [dec] current [dec] |
Generated when the Flow monitoring threshold has crossed into the configured range limit |
flomon |
"NA" |
|
FLOWMON-3-ALERT_NOTIFY_CLEAR |
3-Error |
[[chars]]: SRC_IP:[inet] SRC_PORT:%lu DST_IP:[inet] DST_PORT:%lu [chars][chars] [chars] [chars] |
Generated when the Flow monitoring threshold has gone below the configured limit and the condition is being cleared |
flomon |
"NA" |
|
FLOWMON-3-ALERT_NOTIFY_SET |
3-Error |
[[chars]]: SRC_IP:[inet] SRC_PORT:%lu DST_IP:[inet] DST_PORT:%lu [chars][chars] [chars] [chars] |
Generated when the Flow monitoring threshold has crossed the configured limit and the condition is being set |
flomon |
"NA" |
|
FLOWMON-4-ALERT_ALERT_CLEAR |
4-Warning |
[[chars]]: SRC_IP:[inet] SRC_PORT:%lu DST_IP:[inet] DST_PORT:%lu [chars][chars] [chars] [chars] |
Generated when the Flow monitoring threshold has gone below the configured limit and the condition is being cleared |
flomon |
"NA" |
|
FLOWMON-4-ALERT_ALERT_SET |
4-Warning |
[[chars]]: SRC_IP:[inet] SRC_PORT:%lu DST_IP:[inet] DST_PORT:%lu [chars][chars] [chars] [chars] |
Generated when the Flow monitoring threshold has crossed the configured limit and the condition is being set |
flomon |
"NA" |
|
FLOWMON-4-ALERT_EMERGENCY_CLEAR |
4-Warning |
[[chars]]: SRC_IP:[inet] SRC_PORT:%lu DST_IP:[inet] DST_PORT:%lu [chars][chars] [chars] [chars] |
Generated when the Flow monitoring threshold has gone below the configured limit and the condition is being cleared |
flomon |
"NA" |
|
FLOWMON-4-ALERT_EMERGENCY_SET |
4-Warning |
[[chars]]: SRC_IP:[inet] SRC_PORT:%lu DST_IP:[inet] DST_PORT:%lu [chars][chars] [chars] [chars] |
Generated when the Flow monitoring threshold has crossed the configured limit and the condition is being set |
flomon |
"NA" |
|
FLOWMON-4-ALERT_INFM_CLEAR |
4-Warning |
[[chars]]: SRC_IP:[inet] SRC_PORT:%lu DST_IP:[inet] DST_PORT:%lu [chars][chars] [chars] [chars] |
Generated when the Flow monitoring threshold has gone below the configured limit and the condition is being cleared |
flomon |
"NA" |
|
FLOWMON-4-ALERT_INFM_SET |
4-Warning |
[[chars]]: SRC_IP:[inet] SRC_PORT:%lu DST_IP:[inet] DST_PORT:%lu [chars][chars] [chars] [chars] |
Generated when the Flow monitoring threshold has crossed the configured limit and the condition is being set |
flomon |
"NA" |
|
FLOWMON-4-ALERT_SCALE_LIMIT |
4-Warning |
Flow scale limit reached on LC. New Flows can get learnt when existing flows timeout |
Generated when the Flow scale limit is reached on LC and new flow tries to learn |
flomon |
"NA" |
|
FLOWMON-4-ALERT_WAR_CLEAR |
4-Warning |
[[chars]]: SRC_IP:[inet] SRC_PORT:%lu DST_IP:[inet] DST_PORT:%lu [chars][chars] [chars] [chars] |
Generated when the Flow monitoring threshold has gone below the configured limit and the condition is being cleared |
flomon |
"NA" |
|
FLOWMON-4-ALERT_WAR_SET |
4-Warning |
[[chars]]: SRC_IP:[inet] SRC_PORT:%lu DST_IP:[inet] DST_PORT:%lu [chars][chars] [chars] [chars] |
Generated when the Flow monitoring threshold has crossed the configured limit and the condition is being set |
flomon |
"NA" |
|
FM-1-INIT |
1-Alert |
Feature Manager subsystem initialization failure |
The Feature Manager subsystem failed to initialize. Most likely cause is insufficient memory at init time. Probably either the hardware has failed or this image is being run on a platform it was not intended for. |
firmware |
"Replace failing hardware or obtain the correct " "IOS image for this platform whichever is " "appropriate." |
|
FM-2-NOMAP |
2-Critical |
Cannot create Feature Manager data structures for VLAN Map [chars] |
The Feature Manager could not allocate the data structures needed to describe a VLAN Map in a form that can be loaded into hardware. Probably caused by lack of free memory. |
firmware |
LOG_STD_REDUCE_ACTION |
|
FM-2-NOSB |
2-Critical |
Cannot create subblock for interface [chars] |
The Feature Manager was unable to save per-interface information needed for its correct operation. Some per-interface features such as access groups or VLAN maps will not be configured correctly. |
firmware |
"Use a less complicated configuration that " "requires less memory." |
|
FM-2-NOVLB |
2-Critical |
Cannot create memory block for VLAN [dec] |
The Feature Manager was unable to save per-VLAN information needed for its correct operation. Some per-interface features such as access groups or VLAN maps will not be configured correctly. |
firmware |
"Use a less complicated configuration that " "requires less memory." |
|
FM-2-NOVMR |
2-Critical |
Cannot create VMR data structures for access list [chars] |
The Feature Manager could not allocate the data structures needed to describe an ACL in a form that can be loaded into hardware. Probably caused by lack of available memory. |
firmware |
"Use a less complicated configuration that " "requires less memory." |
|
FM-3-AUGMENTFAIL |
3-Error |
Augmenting of access-map [chars] on [chars] label [dec] failed |
The system ran out of CPU memory when attempting to merge internally required elements with the configured access maps. |
firmware |
LOG_STD_REDUCE_ACTION |
|
FM-3-CONFLICT |
3-Error |
[chars] [chars] conflicts with [chars] |
Port access lists PACLs may not be applied when input router access lists or VLAN maps have been applied and vice versa |
firmware |
"Remove the conflicting feature or features" |
|
FM-3-GOTLABEL |
3-Error |
Got label for [chars] |
The Feature Manager has now been able to allocate a hardware label for the interface. The interface had needed a label before but none was available. |
- |
LOG_STD_NO_ACTION |
|
FM-3-GOTVLABEL |
3-Error |
Got label for VLAN #[dec] |
The Feature Manager has now been able to allocate a hardware label for the VLAN. The VLAN had needed a label before but none was available. |
- |
LOG_STD_NO_ACTION |
|
FM-3-ILLEGALCOPY |
3-Error |
Illegal copy of [chars] access group [chars] from [chars] label [dec] to [dec] |
An internal software error has occurred |
firmware |
"show running-config" |
|
FM-3-INITLABEL |
3-Error |
Special initialization of label [dec] failed |
Initialization of the access list hardware failed. Prioritization of routing protocol packets above other kinds of packets may not occur on some VLANs or routed ports. |
firmware |
LOG_STD_ACTION |
|
FM-3-INSERTFAIL |
3-Error |
Insert of access-map [chars] #[dec] into [chars] label [dec] failed |
The system ran out of CPU memory when trying to merge sections of an access map. |
firmware |
"Reduce other system activity to ease the memory demands. For example " "remove any ACLs that have been defined but are not now used. Use " "simpler ACLs with fewer access control entries ACEs. Use fewer " |
|
FM-3-INTTABLE |
3-Error |
Not in truth table: VLMAP [dec] RACL [dec] Rtprot [dec] Redir [dec] Mcb [dec] Feat [dec] |
An unrecoverable software error occurred while trying to merge the configured input features. |
firmware |
"show running-config" |
|
FM-3-LABELERROR |
3-Error |
Incorrect label to [chars] vlan label attribute copy callback srclabel [dec] dstlabel [dec] |
The Feature Manager attribute copy callback was called with an incorrect source or destination label. |
firmware |
"show running-config" |
|
FM-3-MAXRECURSION |
3-Error |
Too many [dec] levels of recursion while merging [chars] code [dec]. |
The configuration is too complicated for the platform specific ACL merge code to support. Most likely cause is including too many separate access lists in a single VLAN map or policy map. |
- |
"Reduce the number IP or MAC access lists" " considered separately in any one VLAN or policy" |
|
FM-3-MERGEFAIL |
3-Error |
[chars] ACL merge error [dec] [chars] on [chars] label [dec] |
The Feature Manager was unable to complete the merge of the configured features into a form suitable for loading into the hardware. Packets potentially affected by this feature will be sent to the CPU for processing instead. The most likely cause is specifying an ACL that is too large or too complex for the system to handle. |
firmware |
"Try specifying a smaller and less complicated " "configuration." |
|
FM-3-NOLABEL |
3-Error |
Cannot allocate [chars] label for interface [chars] |
The Feature Manager was unable to allocate a label for the features on this interface. This means that the hardware cannot be programmed to implement the features and packets for this interface will be filtered in software. There is a limit of 256 labels per direction. |
firmware |
"Allocate more space to the relevant section " "of the TCAM and reboot or else use a simpler " "configuration. Use the same ACLs on multiple " "interfaces if possible." |
|
FM-3-NOLABELVL |
3-Error |
Cannot allocate [chars] label for VLAN [dec] |
The Feature Manager was unable to allocate a label for the features on this VLAN. This means that the hardware cannot be programmed to implement the features and packets on this VLAN will be filtered in softtware. There is a limit of 256 labels per direction. |
firmware |
"Allocate more space to the relevant section " "of the TCAM and reboot or else use a simpler " "configuration. Use the same VLAN Maps on multiple " "VLANs if possible." |
|
FM-3-NOTEMPTY |
3-Error |
Illegal copy of attribute to non empty [chars] vlan label [dec] |
The Feature Manager attribute copy callback was called with a destination label already being used by a VLAN or routed port. |
firmware |
"show running-config" |
|
FM-3-NOTOBJECT |
3-Error |
Invalid object VLAN [dec] IDB [hec] used in Feature Manager operation |
An internal software error has occurred |
firmware |
"show running-config" |
|
FM-3-OUTTTABLE |
3-Error |
Not in truth table: RACL [dec] VLMAP [dec] |
An unrecoverable software error occurred while trying to merge the configured output features. |
firmware |
"show running-config" |
|
FM-3-QOSTTABLE |
3-Error |
Not in truth table: ACL [dec] in map action [dec] |
A software error occurred while trying to merge a QoS Policy Map |
firmware |
"show running-config" |
|
FM-3-RELOADED |
3-Error |
Reloading [chars] label [dec] feature in [chars] |
The Feature Manager was able to fit more of the configured features on this label into the hardware. One or more features had previously been unloaded because of lack of space. |
- |
LOG_STD_NO_ACTION |
|
FM-3-TOSCOST |
3-Error |
Minimize monetary cost TOS bit unsupported in hardware ignored |
This hardware platform supports filtering based on DSCP rather than TOS and precedence. The DSCP field does not include the minimize monetary cost bit from the TOS field so hardware will ignore this bit when checking for a match to an ACE. This can lead to unintended filtering actions. |
firmware |
"Design filters that do not test for minimum " "monetary cost TOS." |
|
FM-3-UNKNOWNACTION |
3-Error |
Unknown VMR access group action 0x[hec] |
An internal software error has occurred. |
firmware |
LOG_STD_ACTION |
|
FM-3-UNLOADING |
3-Error |
Unloading [chars] label [dec] feature from [chars] |
The Feature Manager was unable to fit the complete configuration into the hardware so some features will have to be applied in software. This prevents some or all of the packets from being forwarded in hardware and requires them to be forwarded by the CPU. Multicast packets may be dropped entirely instead of being forwarded. |
firmware |
"Allocate more space to the relevant section " "of the TCAM and reboot or else use a simpler " "configuration. Use the same ACLs on multiple " "interfaces if possible." |
|
FM-3-WRONGLABEL |
3-Error |
Inconsistent records of label for [chars]: FM has [dec] LM has [dec] |
An internal software error has occurred. |
firmware |
"show running-config" |
|
FM-4-EXCESSSECONDARY |
4-Warning |
More than [dec] secondary IP addresses configured on interface [chars] |
When secondary IP addresses are configured on an interface the hardware is usually programmed so that the ICMP redirect functionality on the CPU is not notified of packets sent between two subnets configured on the same interface. If many secondary IP addresses are configured on the same interface it becomes impractical to program the hardware in this manner this message is logged and the CPU will be notified of every packet sent between two subnets on this interface. No ICMP redirects will be sent in error but the CPU usage may increase because of the additional notifications. The user may wish to configure \no ip redirects\ on the interface to reduce the CPU load on the system. |
firmware |
"configure the \"no ip redirects\" command on " "this interface" |
|
FM-7-TRANSDEF |
7-Debug |
No augmentation function found for VMR |
An Internal Error occured. An Access Control List was not interpretted correctly. The Value-Mask Result is incorrect. |
firmware |
LOG_STD_ACTION |
|
FMANRP_ACL-3-EXPOGACLLIMITERR |
3-Error |
Expanded OGACL [chars] size [dec] exceeded MAX ACL limit [dec] |
Expanded OGACL size exceeded the maximum ACL limit. Command rejected |
iosxe-acl |
"Reduce # of ACEs in the ACL" |
|
FMANRP_ACL-4-INVALIDV4ACETYPE |
4-Warning |
v4 ACE type is invalid |
An unexpected condition has occurred which is due to the type of v4 ACE\n\ created |
iosxe-acl |
"show ip access-list" |
|
FMANRP_ACL-4-INVALIDV6OP |
4-Warning |
Operation is invalid |
An unexpected condition has occurred which is due to the operation \n\ performed |
iosxe-acl |
"show ipv6 access-list" |
|
FMANRP_ACL-4-NOACL |
4-Warning |
ACL is null |
An unexpected condition has occurred which is due to the absence of\n\ an ACL structure. |
iosxe-acl |
"show ip access-list" |
|
FMANRP_ACL-4-NOMACACE |
4-Warning |
mac ACE is null |
An unexpected condition has occurred which is due to the absence of\n\ an mac ACE structure. |
iosxe-acl |
"show access-list" |
|
FMANRP_ACL-4-NOSB |
4-Warning |
Subblock on interface [chars] 0x[hec] is null |
An unexpected condition has occurred which is due to the absence of\n\ a subblock structure on interface. |
iosxe-acl |
"show ip interface" |
|
FMANRP_ACL-4-NOSWIDB |
4-Warning |
Sub-interface is null |
An unexpected condition has occurred which is due to the absence of\n\ a swidb structure. |
iosxe-acl |
"show ip interface" |
|
FMANRP_ACL-4-NOV4ACE |
4-Warning |
v4 ACE is null |
An unexpected condition has occurred which is due to the absence of\n\ an v4 ACE structure. |
iosxe-acl |
"show ip access-list" |
|
FMANRP_ACL-4-NOV6ACE |
4-Warning |
v6 ACE is null |
An unexpected condition has occurred which is due to the absence of\n\ an v6 ACE structure. |
iosxe-acl |
"show ipv6 access-list" |
|
FMANRP_ACL-4-TMPLACLDISABLEERR |
4-Warning |
Not enough resources to disable template ACL |
Not enough resurces to store individual ACLs |
iosxe-acl |
"show ip access-list template summary" |
|
FMANRP_ACL-4-TMPLACLINITERR |
4-Warning |
Template ACL initialization error |
An unexpected condition has occurred on template ACL initialization |
iosxe-acl |
"show memory" |
|
FMANRP_ACL-4-TMPLACLNOMEMERR |
4-Warning |
Template ACL no memory error |
An unexpected condition has occurred on template ACL processing |
iosxe-acl |
"show memory" |
|
FMANRP_ACL-4-UPDMACSTATSERR |
4-Warning |
Update mac ACL statistics error |
An unexpected condition has occurred when updating mac ACL statistics |
iosxe-acl |
"show access-list" |
|
FMANRP_ACL-4-UPDV4STATSERR |
4-Warning |
Update v4 ACL statistics error |
An unexpected condition has occurred when updating v4 ACL statistics |
iosxe-acl |
"show ip access-list" |
|
FMANRP_ACL-4-UPDV6STATSERR |
4-Warning |
Update v6 ACL statistics error |
An unexpected condition has occurred when updating v6 ACL statistics |
iosxe-acl |
"show ipv6 access-list" |
|
FMANRP_ALG-3-API_FAILED |
3-Error |
NULL |
A call to the API of another component has indicated an\n\ error. |
iosxe-alg |
LOG_STD_ACTION |
|
FMANRP_ALG-3-EINVAL |
3-Error |
NULL |
An unexpected input value to a function was incorrect |
iosxe-alg |
LOG_STD_ACTION |
|
FMANRP_DPSS-3-DPSSFOIOSDENQUEUE |
3-Error |
Failed to enqueue dpss feature object 0x[hec] config message for transmission |
This operation to enqueue an IPC message for sending has failed. |
asr1k-dpss |
LOG_STD_ACTION |
|
FMANRP_DPSS-3-DPSSFOIPCALLOC |
3-Error |
Failed to alloc IPC buffer for dpss feature object 0x[hec] config\n\ message |
This operation to allocate IPC buffer for dpss feature object \n\ configuration has failed. |
asr1k-dpss |
LOG_STD_ACTION |
|
FMANRP_DPSS-3-DPSSFOTDLCREATE |
3-Error |
Failed to create tdl msg for dpss feature object 0x[hec] config message |
This operation to create an TDL message has failed. |
asr1k-dpss |
LOG_STD_ACTION |
|
FMANRP_DPSS-3-DPSSFOTDLMSGMARSHAL |
3-Error |
Failed to copy dpss feature object config message to IPC buffer for\n\ fo_hdl 0x[hec] |
This operation to build a TDL message for dpss feature object \n\ configuration has failed. |
asr1k-dpss |
LOG_STD_ACTION |
|
FMANRP_DPSS-3-DPSSFOTDLSET |
3-Error |
Failed to set tdl msg detail for dpss feature object 0x[hec] config message |
This operation to set an TDL message has failed. |
asr1k-dpss |
LOG_STD_ACTION |
|
FMANRP_DPSS-3-DPSSGLOBALIOSDENQUEUE |
3-Error |
Failed to enqueue dpss global config message for transmission |
This operation to enqueue an IPC message for sending has failed. |
asr1k-dpss |
LOG_STD_ACTION |
|
FMANRP_DPSS-3-DPSSGLOBALIPCALLOC |
3-Error |
Failed to alloc IPC buffer for dpss global config\n\ message |
This operation to allocate IPC buffer for dpss global \n\ configuration has failed. |
asr1k-dpss |
LOG_STD_ACTION |
|
FMANRP_DPSS-3-DPSSGLOBALTDLCREATE |
3-Error |
Failed to create tdl msg for dpss global config message |
This operation to create an TDL message has failed. |
asr1k-dpss |
LOG_STD_ACTION |
|
FMANRP_DPSS-3-DPSSGLOBALTDLMSGMARSHAL |
3-Error |
Failed to copy dpss global config message to IPC buffer |
This operation to build a TDL message for dpss global \n\ configuration has failed. |
asr1k-dpss |
LOG_STD_ACTION |
|
FMANRP_DPSS-3-DPSSGLOBALTDLSET |
3-Error |
Failed to set tdl msg detail for dpss global config message |
This operation to set an TDL message has failed. |
asr1k-dpss |
LOG_STD_ACTION |
|
FMANRP_ESS-3-ENQUEFAIL |
3-Error |
[chars] [hex] [hex] |
- |
- |
- |
|
FMANRP_ESS-3-ERREVENT |
3-Error |
[chars] [hex] |
- |
- |
- |
|
FMANRP_ESS-3-ERREVENT2 |
3-Error |
[chars] [hex] / [hex] |
- |
- |
- |
|
FMANRP_ESS-4-EVSICREAT |
4-Warning |
[chars] sip_ess_segment= [hex] segment_id= [dec] fsp_ess_segment= [hex] segment_id= [dec] evsi= [dec] |
A failure has occured in creating a session interface. |
iosxe-bb |
" The session creation is rejected." " If you determine that the system is" " adversely affected then" LOG_STD_ACTION |
|
FMANRP_ESS-4-FULLVAI |
4-Warning |
Session creation failed due to Full Virtual-Access Interfaces not being supported. Check that all applied Virtual-Template and RADIUS features support Virtual-Access sub-interfaces. swidb= [hex] ifnum= [dec] |
A failure has occured in creating a session interface due to a Full Virtual-Access Interface being created. Full Virtual-Access Interface are created if a Virtual-Template or RADIUS feature does not support Virtual-Access sub-interfaces. This platform only supports Virtual-Access sub-interfaces. Refer to Action to isolate offending feature. |
iosxe-bb |
" The session creation is rejected." " Steps to isolate unsupported Session feature:\n" " Run 'test Virtual-Template # subinterface' where" " # is the Virtual-Template number being used to" " create the session. Remove any identified" " features that are not sub-interface compliant.\n" " For RADIUS features:\n" " Configure \"aaa policy interface-config" " allow-subinterface\" on the router or\n" " cisco-avpair=\"lcp:allow-subinterface=yes\" needs" " to be specified in the subscriber profile on the" " Radius server." |
|
FMANRP_ESS-4-MAXSESS |
4-Warning |
[chars] [dec] |
- |
- |
- |
|
FMANRP_ESS-4-SEGFAIL |
4-Warning |
[chars] Seghandle 0x[hec] of Type [dec] |
A failure has occured with a segment operation. |
iosxe-bb |
" The session creation is rejected." " If you determine that the system is" " adversely affected then" LOG_STD_ACTION |
|
FMANRP_ESS-4-SEGFAIL2 |
4-Warning |
[chars] Seghandle 0x[hec] of Type [dec] ess_segment= [hex] |
A failure has occured with a segment operation. |
iosxe-bb |
" The session creation is rejected." " If you determine that the system is" " adversely affected then" LOG_STD_ACTION |
|
FMANRP_ESS-4-SESSCNT |
4-Warning |
[chars] [hex] |
- |
- |
- |
|
FMANRP_ESS-4-WRNEVENT |
4-Warning |
[chars] [hex] |
- |
- |
- |
|
FMANRP_ESS-4-WRNEVENT2 |
4-Warning |
[chars] [hex] / [hex] |
- |
- |
- |
|
FMANRP_ESS-4-WRNPARAM |
4-Warning |
[chars] |
A failure has occured relating to an incorrect functional parameters. |
iosxe-bb |
" The session creation is rejected." " If you determine that the system is" " adversely affected then" LOG_STD_ACTION |
|
FMANRP_ESS-4-WRNPARAM_2U |
4-Warning |
[chars] [dec] / [dec] |
- |
- |
- |
|
FMANRP_ESS-4-WRNPARAM_2X |
4-Warning |
[chars] [hex] / [hex] |
- |
- |
- |
|
FMANRP_ESS-4-WRNPARAM_2X2S |
4-Warning |
[chars] [hex] / [hex] / [chars] / [chars] |
- |
- |
- |
|
FMANRP_ESS-4-WRNPARAM_2XD |
4-Warning |
[chars] [hex] / [hex] / [dec] |
- |
- |
- |
|
FMANRP_ESS-4-WRNPARAM_3X |
4-Warning |
[chars] [hex] / [hex] / [hex] |
- |
- |
- |
|
FMANRP_ESS-4-WRNPARAM_D |
4-Warning |
[chars] [dec] |
- |
- |
- |
|
FMANRP_ESS-4-WRNPARAM_DU |
4-Warning |
[chars] [dec] / [dec] |
- |
- |
- |
|
FMANRP_ESS-4-WRNPARAM_F2S |
4-Warning |
[chars]: [chars] [chars] / [chars] |
- |
- |
- |
|
FMANRP_ESS-4-WRNPARAM_F2X |
4-Warning |
[chars]: [chars] [hex] / [hex] |
- |
- |
- |
|
FMANRP_ESS-4-WRNPARAM_FU |
4-Warning |
[chars]: [chars] [dec] |
- |
- |
- |
|
FMANRP_ESS-4-WRNPARAM_S |
4-Warning |
[chars]: [chars] |
A failure has occured relating to an incorrect functional parameters. |
iosxe-bb |
" The session creation is rejected." " If you determine that the system is" " adversely affected then" LOG_STD_ACTION |
|
FMANRP_ESS-4-WRNPARAM_U |
4-Warning |
[chars] [dec] |
- |
- |
- |
|
FMANRP_ESS-4-WRNPARAM_U2X |
4-Warning |
[chars] [dec] / [hex] / [hex] |
- |
- |
- |
|
FMANRP_ESS-4-WRNPARAM_UXD |
4-Warning |
[chars] [dec] / [hex] / [dec] |
- |
- |
- |
|
FMANRP_ESS-4-WRNPARAM_XU |
4-Warning |
[chars] [hex] / [dec] |
- |
- |
- |
|
FMANRP_EVPN-3-UNSPOP |
3-Error |
Unsupport operation |
An unexpected operation is get during EVPN configuration |
iosxe-evpn |
LOG_STD_ACTION |
|
FMANRP_IPSEC-3-HAPI_PCP_UNEXP_REPLY |
3-Error |
[chars]: PCP trans 0x[hec] opcode 0x[hec]: unexpected reply from crypto |
An unexpected internal software error. Engineering must be reported and investigate this occurrence. |
iosxe-ipsec |
LOG_STD_DDTS_TAC_DETAILS |
|
FMANRP_IPSEC-6-HAPI_PCP_NACK |
6-Information |
[chars]: PCP NACK trans 0x[hec] opcode 0x[hec] errcode 0x[hec]: crypto |
A failure has occured during security policy downloading in crypto hardware. The command is rejected. |
iosxe-ipsec |
"The configuration may be ignorable or recovered " "automatically in crypto hardware. The session may " "still be functional but less than optimal " "performance. If you determine that the system is " "adversely affected then Embedded Services Processor " "ESP tracelog should be collected. " |
|
FMANRP_MFR-3-BLCFGFAIL |
3-Error |
Unable to [chars] link [chars] [chars] |
An unexpected condition has occurred at Bundle link configuration [chars] |
iosxe-mlfr |
LOG_STD_ACTION |
|
FMANRP_MFR-3-BLFAIL |
3-Error |
Unable to [chars] link [chars] [chars] |
An unexpected condition has occurred at Bundle link configuration [chars] |
iosxe-mlfr |
LOG_STD_ACTION |
|
FMANRP_MFR-3-BNDLFAIL |
3-Error |
Unable to [chars] bundle [chars] |
An unexpected condition has occurred at Bundle configuration |
iosxe-mlfr |
LOG_STD_ACTION |
|
FMANRP_MFR-3-TDLFAIL |
3-Error |
Unable to send [chars] [chars] message to Forwarding Manager Process [chars] |
An unexpected condition has occurred which resulted in a configuration \n\ not being sent to the Forwarding Manager Processs. |
iosxe-mlfr |
LOG_STD_ACTION |
|
FMANRP_MPLS-3-ENQUEFAIL |
3-Error |
Unable to send [chars] [chars] message to Forwarding Manager Process |
An unexpected condition has occurred which resulted in a configuration \n\ not being sent to the Forwarding Manager Processs. |
asr1k-fwdmgr |
LOG_STD_ACTION |
|
FMANRP_MPLS-3-NOOBJ |
3-Error |
Object entry is null |
An unexpected condition has occurred which is due to the absence of\n\ an object entry structure. |
asr1k-fwdmgr |
"show mpls" |
|
FMANRP_MPLS-3-UNSPTYPE |
3-Error |
Not supported bundle type [dec] |
An unexpected condition has occurred which is due to an operation request\n\ to an unsupported bundle oce type is received. |
asr1k-fwdmgr |
LOG_STD_ACTION |
|
FMANRP_NAT-3-AVLDELETE |
3-Error |
Failed to delete node from NAT [chars] database for [inet] |
This operation to perform delete processing has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-AVLDELETE |
3-Error |
Failed to delete node from NAT [chars] database for [inet] |
This operation to perform delete processing has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-AVLTREEWALK |
3-Error |
Failed to walk NAT [chars] database for [chars] |
This operation to perform stale processing has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-AVLTREEWALK |
3-Error |
Failed to walk NAT [chars] database for [chars] |
This operation to perform stale processing has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-DEBUGTDLMSGMARSHAL |
3-Error |
Failed to copy debug NAT request message to IPC buffer |
This operation to build a TDL message for debug NAT command \n\ has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-DEBUGTDLMSGMARSHAL |
3-Error |
Failed to copy debug NAT request message to IPC buffer |
This operation to build a TDL message for debug NAT command \n\ has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-IFADDRTDLMSGMARSHAL |
3-Error |
Failed to copy interface address change message to IPC buffer for\n\ interface [chars] new address [inet] |
This operation to build a TDL message for NAT interface address\n\ configuration has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-IFADDRTDLMSGMARSHAL |
3-Error |
Failed to copy interface address change message to IPC buffer for\n\ interface [chars] new address [inet] |
This operation to build a TDL message for NAT interface address\n\ configuration has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-IFTDLMSGMARSHAL |
3-Error |
Failed to copy interface config essage to IPC buffer for \n\ Interface [chars] 0x[hec] domain [chars] operation [chars] |
This operation to build a TDL message for interface configuration\n\ has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-IFTDLMSGMARSHAL |
3-Error |
Failed to copy interface config essage to IPC buffer for \n\ Interface [chars] 0x[hec] domain [chars] operation [chars] |
This operation to build a TDL message for interface configuration\n\ has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-INVALID_ADDRESS |
3-Error |
Received an invalid address [inet] |
An unsupported address for the given config was received. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-INVALID_ADDRESS |
3-Error |
Received an invalid address [inet] |
An unsupported address for the given config was received. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-IOSDENQUEUE |
3-Error |
Failed to enqueue NAT [chars] message for transmission |
This operation to enqueue an IPC message for sending has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-IOSDENQUEUE |
3-Error |
Failed to enqueue NAT [chars] message for transmission |
This operation to enqueue an IPC message for sending has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-IPALIASTDL |
3-Error |
Error with ipalias message received from data path |
An unexpected condition has occurred with received ipalias \n\ message from data path |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-IPALIASTDL |
3-Error |
Error with ipalias message received from data path |
An unexpected condition has occurred with received ipalias \n\ message from data path |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-IPALIASTYPE |
3-Error |
Received ipalias message from data path with unsupported \n\ address type [dec] |
An unexpected condition has occurred with received ipalias \n\ message from data path with unsupported address type |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-IPALIASTYPE |
3-Error |
Received ipalias message from data path with unsupported \n\ address type [dec] |
An unexpected condition has occurred with received ipalias \n\ message from data path with unsupported address type |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-IPSTATICROUTETDL |
3-Error |
Error with static ip route message received from data path |
An unexpected condition has occurred with received static\n\ ip route message from data path |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-IPSTATICROUTETDL |
3-Error |
Error with static ip route message received from data path |
An unexpected condition has occurred with received static\n\ ip route message from data path |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-IPSTATICROUTETYPE |
3-Error |
Received ip static route message from data path with\n\ unsupported address type |
An unexpected condition has occurred with received static \n\ ip route message from data path with unsupported address type |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-IPSTATICROUTETYPE |
3-Error |
Received ip static route message from data path with\n\ unsupported address type |
An unexpected condition has occurred with received static \n\ ip route message from data path with unsupported address type |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-MAPPINGTDLMSGMARSHAL |
3-Error |
Failed to copy mapping config message to IPC buffer for\n\ mapping id [dec] vrf table id [dec] |
This operation to build a TDL message for mapping configuration\n\ has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-MAPPINGTDLMSGMARSHAL |
3-Error |
Failed to copy mapping config message to IPC buffer for\n\ mapping id [dec] vrf table id [dec] |
This operation to build a TDL message for mapping configuration\n\ has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-MAXENTRYTDLMSGMARSHAL |
3-Error |
Failed to copy max entry config message to IPC buffer for\n\ type [chars] entry data 0x[hec] max_limit [dec] |
This operation to build a TDL message for max entry add/delete\n\ has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-MAXENTRYTDLMSGMARSHAL |
3-Error |
Failed to copy max entry config message to IPC buffer for\n\ type [chars] entry data 0x[hec] max_limit [dec] |
This operation to build a TDL message for max entry add/delete\n\ has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-MIBEVENT |
3-Error |
Failed to get NAT MIB response message: [chars] |
An unsupported error occured with waiting for NAT MIB respsonse \n\ message. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-MIBEVENT |
3-Error |
Failed to get NAT MIB response message: [chars] |
An unsupported error occured with waiting for NAT MIB respsonse \n\ message. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-MSGALLOCERR |
3-Error |
Failed to allocate message |
When attempting to send message to dataplane there was not enough memory to allocate the message. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-MSGALLOCERR |
3-Error |
Failed to allocate message |
When attempting to send message to dataplane there was not enough memory to allocate the message. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-NATSETTDLMSGFAIL |
3-Error |
When download [chars] failed to set a field in message |
sotware error. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-NATSETTDLMSGFAIL |
3-Error |
When download [chars] failed to set a field in message |
sotware error. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-POOLTDLMSGMARSHAL |
3-Error |
Failed to copy pool config message to IPC buffer for\n\ pool [chars] id [dec] |
This operation to build a TDL message for pool configuration\n\ has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-POOLTDLMSGMARSHAL |
3-Error |
Failed to copy pool config message to IPC buffer for\n\ pool [chars] id [dec] |
This operation to build a TDL message for pool configuration\n\ has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-PORTLISTPROTO |
3-Error |
Protocol type [dec] for global addr [inet] in the portlist allocation request is not supported |
An unexpected protocol type has occurred with received portlist\n\ allocation request message from data path |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-PORTLISTPROTO |
3-Error |
Protocol type [dec] for global addr [inet] in the portlist allocation request is not supported |
An unexpected protocol type has occurred with received portlist\n\ allocation request message from data path |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-PORTLISTTDL |
3-Error |
Error with portlist allocation request message received from data path |
An unexpected condition has occurred with received portlist\n\ allocation request message from data path |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-PORTLISTTDL |
3-Error |
Error with portlist allocation request message received from data path |
An unexpected condition has occurred with received portlist\n\ allocation request message from data path |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-PORTLISTTDLMSGMARSHAL |
3-Error |
Failed to copy portlist config message to IPC buffer for\n\ addr [inet] proto [dec] start_port [dec] end_port [dec] |
This operation to build a TDL message for portlist add/delete\n\ has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-PORTLISTTDLMSGMARSHAL |
3-Error |
Failed to copy portlist config message to IPC buffer for\n\ addr [inet] proto [dec] start_port [dec] end_port [dec] |
This operation to build a TDL message for portlist add/delete\n\ has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-PORTLISTTYPE |
3-Error |
Address type [dec] for global address in the portlist allocation request is not supported |
An unexpected address type has occurred with received portlist\n\ allocation request message from data path |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-PORTLISTTYPE |
3-Error |
Address type [dec] for global address in the portlist allocation request is not supported |
An unexpected address type has occurred with received portlist\n\ allocation request message from data path |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-RANGETDLMSGMARSHAL |
3-Error |
Failed to copy pool address range config message to IPC buffer for\n\ pool [chars] range start [inet] range end [inet] |
This operation to build a TDL message for address range configuration\n\ has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-RANGETDLMSGMARSHAL |
3-Error |
Failed to copy pool address range config message to IPC buffer for\n\ pool [chars] range start [inet] range end [inet] |
This operation to build a TDL message for address range configuration\n\ has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-SERTDLMSGMARSHAL |
3-Error |
Failed to copy service config message to IPC buffer for\n\ application type [dec] protocol type [dec] port [dec] |
This operation to build a TDL message for service configuration\n\ has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-SERTDLMSGMARSHAL |
3-Error |
Failed to copy service config message to IPC buffer for\n\ application type [dec] protocol type [dec] port [dec] |
This operation to build a TDL message for service configuration\n\ has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-SERVICERM |
3-Error |
Failed to delete NAT services for appl type [chars] protocol [chars]\n\ port [dec] |
An unexpected condition has occurred which is due to the failure\n\ to remove data structures for NAT special services. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-SERVICERM |
3-Error |
Failed to delete NAT services for appl type [chars] protocol [chars]\n\ port [dec] |
An unexpected condition has occurred which is due to the failure\n\ to remove data structures for NAT special services. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-STATSUPDTDL |
3-Error |
Failed to update NAT [chars] statistics |
An unexpected condition has occurred when updating statistics |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-STATSUPDTDL |
3-Error |
Failed to update NAT [chars] statistics |
An unexpected condition has occurred when updating statistics |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-TIMEOUTTDLMSGMARSHAL |
3-Error |
Failed to copy timeout config message to IPC buffer for\n\ timeout type [dec] |
This operation to build a TDL message for timeout configuration\n\ has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-TIMEOUTTDLMSGMARSHAL |
3-Error |
Failed to copy timeout config message to IPC buffer for\n\ timeout type [dec] |
This operation to build a TDL message for timeout configuration\n\ has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-VRFDELTDLMSGMARSHAL |
3-Error |
Failed to copy VRF delete message to IPC buffer for vrf table id [dec] |
This operation to build a TDL message for vrf deletion configuration\n\ has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-VRFDELTDLMSGMARSHAL |
3-Error |
Failed to copy VRF delete message to IPC buffer for vrf table id [dec] |
This operation to build a TDL message for vrf deletion configuration\n\ has failed. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-WLANSESSIDB |
3-Error |
Received WLAN session message from data path with nil \n\ input interface for inside local host [inet] |
An unexpected condition has occurred with received WLAN session \n\ message from data path with nil input interface |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-WLANSESSIDB |
3-Error |
Received WLAN session message from data path with nil \n\ input interface for inside local host [inet] |
An unexpected condition has occurred with received WLAN session \n\ message from data path with nil input interface |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-WLANSESSTDL |
3-Error |
Error with WLAN session message received from data path |
An unexpected condition has occurred with received WLAN session \n\ message from data path |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-WLANSESSTDL |
3-Error |
Error with WLAN session message received from data path |
An unexpected condition has occurred with received WLAN session \n\ message from data path |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-WLANSESSTYPE |
3-Error |
Received WLAN session message from data path with unsupported \n\ address type [dec] |
An unexpected condition has occurred with received WLAN session \n\ message from data path with unsupported address type |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-3-WLANSESSTYPE |
3-Error |
Received WLAN session message from data path with unsupported \n\ address type [dec] |
An unexpected condition has occurred with received WLAN session \n\ message from data path with unsupported address type |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT-4-BADACTION |
4-Warning |
Invalid action [dec] for NAT configuration |
An unexpected condition has occurred which is invalid action \n\ for a NAT configuration. |
iosxe-nat |
LOG_STD_SH_CMD_ACTION |
|
FMANRP_NAT-4-BADACTION |
4-Warning |
Invalid action [dec] for NAT configuration |
An unexpected condition has occurred which is invalid action \n\ for a NAT configuration. |
iosxe-nat |
LOG_STD_SH_CMD_ACTION |
|
FMANRP_NAT-4-LOGGING_PARAM |
4-Warning |
Highspeed logging export [chars] [dec] unsupported |
An unsupported exporting paremeter for highspeed logging\n\ on data path is received. |
iosxe-nat |
"show running" |
|
FMANRP_NAT-4-LOGGING_PARAM |
4-Warning |
Highspeed logging export [chars] [dec] unsupported |
An unsupported exporting paremeter for highspeed logging\n\ on data path is received. |
iosxe-nat |
"show running" |
|
FMANRP_NAT-4-NOACL |
4-Warning |
Access list is null |
An unexpected condition has occurred which is due to the absence of\n\ an access list structure. |
iosxe-nat |
"show ip access-lists" |
|
FMANRP_NAT-4-NOACL |
4-Warning |
Access list is null |
An unexpected condition has occurred which is due to the absence of\n\ an access list structure. |
iosxe-nat |
"show ip access-lists" |
|
FMANRP_NAT-4-NOLOGGINGPARAM |
4-Warning |
Highspeed logging structure is nil |
An unexpected condition has occurred which is due to the absence of\n\ a logging parameter structure. |
iosxe-nat |
"show running" |
|
FMANRP_NAT-4-NOLOGGINGPARAM |
4-Warning |
Highspeed logging structure is nil |
An unexpected condition has occurred which is due to the absence of\n\ a logging parameter structure. |
iosxe-nat |
"show running" |
|
FMANRP_NAT-4-NOMAPPING |
4-Warning |
A mapping structure is null |
An unexpected condition has occurred which is due to the absence of\n\ a NAT mapping structure. |
iosxe-nat |
LOG_STD_SH_CMD_ACTION |
|
FMANRP_NAT-4-NOMAPPING |
4-Warning |
A mapping structure is null |
An unexpected condition has occurred which is due to the absence of\n\ a NAT mapping structure. |
iosxe-nat |
LOG_STD_SH_CMD_ACTION |
|
FMANRP_NAT-4-NONATSERVICE |
4-Warning |
Service structure is null |
An unexpected condition has occurred which is due to the absence of\n\ a NAT service structure. |
iosxe-nat |
LOG_STD_SH_CMD_ACTION |
|
FMANRP_NAT-4-NONATSERVICE |
4-Warning |
Service structure is null |
An unexpected condition has occurred which is due to the absence of\n\ a NAT service structure. |
iosxe-nat |
LOG_STD_SH_CMD_ACTION |
|
FMANRP_NAT-4-NOPOOL |
4-Warning |
Pool structure is null |
An unexpected condition has occurred which is due to the absence of\n\ a NAT pool structure. |
iosxe-nat |
LOG_STD_SH_CMD_ACTION |
|
FMANRP_NAT-4-NOPOOL |
4-Warning |
Pool structure is null |
An unexpected condition has occurred which is due to the absence of\n\ a NAT pool structure. |
iosxe-nat |
LOG_STD_SH_CMD_ACTION |
|
FMANRP_NAT-4-NORANGE |
4-Warning |
Pool address range structure is null |
An unexpected condition has occurred which is due to the absence of\n\ a NAT pool address range structure. |
iosxe-nat |
LOG_STD_SH_CMD_ACTION |
|
FMANRP_NAT-4-NORANGE |
4-Warning |
Pool address range structure is null |
An unexpected condition has occurred which is due to the absence of\n\ a NAT pool address range structure. |
iosxe-nat |
LOG_STD_SH_CMD_ACTION |
|
FMANRP_NAT-4-NOREPLICATEPARAM |
4-Warning |
Session replication structure is nil |
An unexpected condition has occurred which is due to the absence of\n\ a session replication parameter structure. |
iosxe-nat |
"show running" |
|
FMANRP_NAT-4-NOREPLICATEPARAM |
4-Warning |
Session replication structure is nil |
An unexpected condition has occurred which is due to the absence of\n\ a session replication parameter structure. |
iosxe-nat |
"show running" |
|
FMANRP_NAT-4-NOSWIDB |
4-Warning |
Sub-interface is null |
An unexpected condition has occurred which is due to the absence of\n\ a swidb structure. |
iosxe-nat |
"show ip interface" |
|
FMANRP_NAT-4-NOSWIDB |
4-Warning |
Sub-interface is null |
An unexpected condition has occurred which is due to the absence of\n\ a swidb structure. |
iosxe-nat |
"show ip interface" |
|
FMANRP_NAT64-3-API_FAILED |
3-Error |
NULL |
A call to the API of another component has indicated an\n\ error. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT64-3-EINVAL |
3-Error |
NULL |
An unexpected input value to a function was incorrect |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT66-3-API_FAILED |
3-Error |
NULL |
A call to the API of another component has indicated an\n\ error. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NAT66-3-EINVAL |
3-Error |
NULL |
An unexpected input value to a function was incorrect |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_NETFLOW-3-AGGRCACHENULL |
3-Error |
The pointer for aggregation cache type [dec] is NULL |
An unexpected condition has occurred which is due to the absence of\n\ an aggregation cache data structure. |
iosxe-netflow |
"show ip cache flow" |
|
FMANRP_NETFLOW-3-CACHETDLMSGMARSHAL |
3-Error |
Failed to copy cache config message to IPC buffer for cache type [dec] |
The operation of building a TDL message for cache configuration\n\ has failed. |
iosxe-netflow |
LOG_STD_ACTION |
|
FMANRP_NETFLOW-3-CLRSTATSTDLMSGMARSHAL |
3-Error |
Failed to copy clear statistics message to IPC buffer |
The operation of building a TDL message for clearing statistics \n\ in the data path has failed. |
iosxe-netflow |
LOG_STD_ACTION |
|
FMANRP_NETFLOW-3-EXPORTERSRCIFINVALID |
3-Error |
Management interface [chars] cannot be used as source for an exporter |
Exporter configuration failed because the management interface cannot be configured as source interface |
iosxe-netflow |
LOG_STD_ACTION |
|
FMANRP_NETFLOW-3-EXPORTERTDLMSGMARSHAL |
3-Error |
Failed to copy exporter config message to IPC buffer for cache \n\ type [dec] |
The operation of building a TDL message for exporter configuration\n\ has failed. |
iosxe-netflow |
LOG_STD_ACTION |
|
FMANRP_NETFLOW-3-EXPORTERVRFINVALID |
3-Error |
Management vrf [chars] cannot be used as exporter destination |
Exporter configuration failed because management vrf cannot be used as exporter destination |
iosxe-netflow |
LOG_STD_ACTION |
|
FMANRP_NETFLOW-3-IFFLOWTDLMSGMARSHAL |
3-Error |
Failed to copy interface flow config message to IPC buffer for [chars] |
The operation of building a TDL message for interface flow configuration\n\ has failed. |
iosxe-netflow |
LOG_STD_ACTION |
|
FMANRP_NETFLOW-3-INVALIDFLOWDEFCPP |
3-Error |
CPP Flow definition can not be created [dec] |
The operation of building a flow definition using flow fields received from CPP has failed. |
iosxe-netflow |
LOG_STD_ACTION |
|
FMANRP_NETFLOW-3-NOSAMPLER |
3-Error |
Sampler for sampler-map name [chars] is null |
An unexpected condition has occurred which is due to the absence of\n\ a sampler-map structure |
iosxe-netflow |
"show sampler" |
|
FMANRP_NETFLOW-3-NOSAMPLERNAME |
3-Error |
Sampler-map name is null |
An unexpected condition has occurred which is due to the absence of\n\ a sampler-map name. |
iosxe-netflow |
"show sampler" |
|
FMANRP_NETFLOW-3-SAMPLERTDLMSGMARSHAL |
3-Error |
Failed to copy sampler-map config message to IPC buffer for [chars] |
The operation of building a TDL message for sampler-map configuration\n\ has failed. |
iosxe-netflow |
LOG_STD_ACTION |
|
FMANRP_NETFLOW-3-STATSUPDTDL |
3-Error |
Failed to update netflow [chars] statistics |
An unexpected condition has occurred when updating statistics |
iosxe-netflow |
LOG_STD_ACTION |
|
FMANRP_NETFLOW-3-UNKNOWNCACHECMD |
3-Error |
Unknown aggregation cache command [dec] received |
The aggregation cache configuration command has failed due to \n\ unknown command. |
- |
LOG_STD_ACTION |
|
FMANRP_NETFLOW-3-UNKNOWNCACHETYPE |
3-Error |
Unknown cache type [dec] received |
The cache configuration command has failed due to unknown\n\ cache scheme type. |
- |
LOG_STD_ACTION |
|
FMANRP_NETFLOW-4-EXPORTERVERSION |
4-Warning |
Failed to change default exporter version to [dec] |
The operation of changing the default exporter version has failed. |
iosxe-netflow |
"show ip flow export" |
|
FMANRP_NETFLOW-4-NOFIBIDB |
4-Warning |
fibdb for interface [chars] is null |
An unexpected condition has occurred which is due to the absence\n\ of a fibidb structure. |
iosxe-netflow |
"show ip interface" |
|
FMANRP_NETFLOW-4-NOSWIDB |
4-Warning |
Sub-interface is null |
An unexpected condition has occurred which is due to the absence of\n\ a swidb structure. |
iosxe-netflow |
"show ip interface" |
|
FMANRP_PBR-3-INVALIDIF |
3-Error |
The interface specified for '[chars]' is not valid |
An non-existent interface is specified for the policy based routing route-map operation specified in the message. |
iosxe-pbr |
"show interface" |
|
FMANRP_PBR-3-RTMAP_NAME_NULL |
3-Error |
The route-map name for [chars] is NULL |
An unexpected condition has occurred due to the absence of an internal route-map data structure. |
iosxe-pbr |
"show route-map" |
|
FMANRP_PBR-3-RTMAPNULL |
3-Error |
The route-map structure for [chars] is NULL |
An unexpected condition has occurred due to the absence of an internal route-map data structure. |
iosxe-pbr |
"show route-map" |
|
FMANRP_PBR-3-UNSUPPORTED_RMAP |
3-Error |
Route-map [chars] has unsupported options for Policy-Based Routing. It has been removed from the interface if applied. |
- |
- |
- |
|
FMANRP_PBR-3-UNSUPPORTED_RMAP_COMMAND |
3-Error |
This Policy-Based Routing command is not supported on this platform. Use the no form of this command to remove it from configurations |
Policy-Based Routing is not supported on this platform |
hardware |
"Remove this command" |
|
FMANRP_PBR-3-UNSUPPORTED_RMAP_SET_INTF |
3-Error |
Route-map [chars] has unsupported options for Policy-Based Routing and has been removed from the interface if applied. \set interface [chars]\ is not a supported interface type for route-map. |
- |
- |
- |
|
FMANRP_PBR-3-UNSUPPORTED_RMAP_SET_SAME_INTF |
3-Error |
Route-map [chars] has unsupported options for Policy-Based Routing and has been removed from the interface if applied. \set interface [chars]\ cannot be the same interface where route-map is being applied [chars]. |
The route-map attached to an interface for policy routing contains an action that is not supported on this platform. This is a hardware limitation. |
hardware |
"Reconfigure the route-map. Use only 'permit' " "entries and 'set ip next-hop' action in the " "route-map." |
|
FMANRP_PFR-4-NOINTF |
4-Warning |
PfR Interface [chars] not exist can't be [chars] |
An unexpected condition has occurred which is due to the absence of\n\ MCP PfR interface info. |
iosxe-pfr |
"show oer border" |
|
FMANRP_PFR-4-NULLINPUT |
4-Warning |
NULL input [chars] |
An unexpected condition has occurred which is due to the NULL value\n\ of the input parameter. |
iosxe-pfr |
"show oer border" |
|
FMANRP_PFR-4-UNSUPPORTED |
4-Warning |
Unsupported action [chars] |
An unexpected condition has occurred which is due to and unsupported action being executed. |
iosxe-pfr |
"show oer border" |
|
FMANRP_QOS-3-ACTNOCLASSMAP |
3-Error |
Class-map information not found |
An unexpected condition has occured when trying to determine class-map information for one of the classes in a policy-map. |
asr1k-qos |
"show policy-map" |
|
FMANRP_QOS-3-ACTNOPOLICYMAP |
3-Error |
Policy-map information not found |
An unexpected condition has occured when trying to determine policy-map information for one of the service policies attached to an interface. |
asr1k-qos |
"show policy-map" |
|
FMANRP_QOS-3-CHILDPOLICYCHECK |
3-Error |
Only 2 level policy is supported.\n\ Service-policy : [chars] |
Error occured while attaching a hierarchical policy |
polaris-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-3-CLPOLFAIL |
3-Error |
No support for client policy with policing in class-default and marking in custom class |
An internal error occured during installing qos policy. |
polaris-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-3-CONFACTCHECK |
3-Error |
Conform-action in a policer can only be transmit.\n\ Policy Rejected. |
Error occured while performing conform action\n\ check on the policer. |
polaris-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-3-HIERPOLICYCHECK |
3-Error |
Hierarchical Policy must have child under all user defined\n\ classes for wired ports. Service-policy : [chars] |
Error occured while attaching a hierarchical policy |
polaris-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-3-HWIDBCHECK |
3-Error |
Configuring service-policy on interface [chars] is not allowed |
Error occured while attaching policy on gigethernet0/0. |
polaris-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-3-MARKDOWNCHECK |
3-Error |
Only markdown with a table-map is supported. |
Error occured while performing exceed\n\ action check on the policy attached |
polaris-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-3-NOACCOUNTSTATS |
3-Error |
account stats entry not found for class [dec].[dec] target [dec] |
An internal error occured when looking up account\n\ statistics. |
asr1k-qos |
"show policy-map interface" |
|
FMANRP_QOS-3-NOPOLICERSTATS |
3-Error |
policer stats entry not found for class [dec].[dec] target [dec] |
An internal error occured when looking up policer\n\ statistics. |
asr1k-qos |
"show policy-map interface" |
|
FMANRP_QOS-3-NOSETSTATS |
3-Error |
set stats entry not found for class [dec].[dec] target [dec] |
An internal error occured when looking up set\n\ statistics. |
asr1k-qos |
"show policy-map interface" |
|
FMANRP_QOS-3-PRILEVELSUPPORT |
3-Error |
Priority with level 3 is not supported.\n\ Service-policy : [chars] |
Priority level 3 support is only for AVB policy.\n\ Hence configuration is rejected. |
polaris-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-3-QBUFFERSCHECK |
3-Error |
Sum of configured qbuffer ratios should be less than 100.\n\ Configuration not accepted. Service-policy : [chars]\n\ Info : classes for which qbuffer ratio is not configured\n\ is given a buffer ratio 1 |
Error occured while performing queue buffers\n\ policy install check. Wrong configuration |
polaris-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-3-QOSAPIPARAM |
3-Error |
Internal QOS API error. |
An internal API error occured. QOS configuration may be limited. |
asr1k-qos |
LOG_STD_SH_TECH_ACTION |
|
FMANRP_QOS-3-QOSCLASSDEL |
3-Error |
Error trying to remove class [chars] from policymap [chars] |
An operation to remove a class from a policy \n\ has failed due to an internal error. |
asr1k-qos |
"show policy-map" |
|
FMANRP_QOS-3-QOSGIDBSP |
3-Error |
Service policy [[chars]] installation error: invalid interface type [dec] |
An invalid interface type was encountered when trying to configure a service policy. This service policy could not be installed. |
asr1k-qos |
"show policy-map" |
|
FMANRP_QOS-3-QOSIDBSP |
3-Error |
Service policy [[chars]] installation error: invalid interface type [dec] |
An invalid interface type was encountered when trying to configure a service policy. This service policy could not be installed. |
asr1k-qos |
"show policy-map" |
|
FMANRP_QOS-3-QOSTDLMARSHAL |
3-Error |
Failed to copy more than [dec] bytes of message [chars] length [dec] into IPC buffer |
An internal error occured when trying to build an IPC message. |
asr1k-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-3-QOSTMPLCREATEFAIL |
3-Error |
QoS template interface creation failed for policy [chars]: [chars] |
An error occured during template interface creation |
ewlc-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-3-QOSTMPLDBERROR |
3-Error |
Failed to [chars] record for policymap [chars] err [chars] |
Database operation failed for record of the policymap |
ewlc-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-3-QOSTMPLDELETEFAIL |
3-Error |
QoS template interface deletion failed for policy [chars]: [chars] |
An error occured during template interface deletion |
ewlc-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-3-QOSTMPLINUSE |
3-Error |
[chars]: [chars] |
record of the policymap is already in use |
ewlc-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-3-QOSTMPLNONEXIST |
3-Error |
QoS template does not exist in [chars] for policymap [chars] |
QoS template information does not exist |
ewlc-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-3-SHAPEBWSUPPORT |
3-Error |
Shape and bandwidth in the same class is unsupported.\n\ Policy Rejected. Service-policy : [chars] |
Error occured while performing qos policy check. |
polaris-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-4-CLMODIFYFAIL |
4-Warning |
classmap [chars] is currently used by policymap please remove policymap from all targets before the modification |
An internal error occured when classmap being modified |
asr1k-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-4-COPPMODIFY |
4-Warning |
Police rate modification for COPP system class [chars] is discouraged. |
User modified police rate for COPP system classes. |
accsw-p-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-4-COPPMODRANGE |
4-Warning |
Police rate modification for COPP system class [chars] is out-of-range. |
User modified police rate for COPP system classes. |
accsw-p-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-4-COPPREMOVE |
4-Warning |
Police rate removal for COPP system class [chars] is discouraged. |
User removed police rate for COPP system classes. |
accsw-p-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-4-MPOLCHECK |
4-Warning |
\nOnly class-default shaper in flat policy-map on parent interface [chars] can co-exist with Qos on sub targets |
QoS attaching validation check for MPOL |
qfp-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-4-MPOLCHECKDETAIL |
4-Warning |
\nOnly class-default shaper in flat policy-map on parent interface [chars] can co-exist with QoS on sub targets\n so policy-map [chars] on parent interface and its sub policy-maps all failed to attach please check it. |
QoS attaching validation check for MPOL |
qfp-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-4-MPOLDMVPNGRE |
4-Warning |
Only Shape and/or BRR is allowed on the QoS policy on GRE tunnel on MPoL hierarchy |
An error occurred during MPoL check between DMVPN and GRE tunnel QoS policy |
asr1k-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-4-NOFAIRQONVC |
4-Warning |
fair-queue can not be configured on the parent queue of an ATM VC use child queue instead |
Configuring fair-queue on the parent queue of an ATM VC is not supported |
asr1k-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-4-QIDGENFAIL |
4-Warning |
qid generation failed reverting to default |
An internal error occured during platform qos \n\ initialization. |
asr1k-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-4-QOSSTACK |
4-Warning |
Failed to install all classes for policymap [chars] excessive stack usage |
An operation to configure the classes within a policymap \n\ has failed due to a resource issue. QoS configuration\n\ for this policymap is unlikely to work. |
asr1k-qos |
"show policy-map" |
|
FMANRP_QOS-4-QOSUBR |
4-Warning |
qos can not be attached to the target with UBR configured |
An error occured to attach qos to ATM VC/VP\n\ target with UBR configured |
asr1k-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-4-STACKBUFFER |
4-Warning |
Stack-buffer configuration has been modified. Current setting is stack-buffer [chars]. This change will take an effect once the configuration is written in flash write memory and then reload the switch. |
Stack-buffer configurations in Catalyst 9300D switches. |
accsw-p-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-6-BUFFERSHARE |
6-Information |
The QoS share-buffer is [chars]. Traffic might be impacted momentarily due to policy reattachment. |
QoS unified buffer configurations in CAT9K switches. |
accsw-p-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-6-QOSCLASSEXIST |
6-Information |
class [chars] id [dec] in policymap [chars] id [dec] already exists |
This is an informational message and no action \n\ is required. |
asr1k-qos |
"show policy-map" |
|
FMANRP_QOS-7-QOSEVPNPOLICYCHECK |
7-Debug |
Unsupported QoS policy format in policy: [chars] |
QoS policy validation check for EVPN policy |
accsw-p-qos |
LOG_STD_ACTION |
|
FMANRP_QOS-7-QOSPROFILE |
7-Debug |
The QoS profile has been modified to [chars]. The QoS policy-map's counters may not be updated accurately during the modification. |
QoS profile configurations in CAT9K switches. |
accsw-p-qos |
LOG_STD_ACTION |
|
FMANRP_SC-3-BULKSNTDLMSGMARSHAL |
3-Error |
Failed to copy Bulk SN Entry message to IPC buffer |
This operation to build a TDL message for Bulk SN Entry \n\ has failed. |
iosxe-service_controller |
LOG_STD_ACTION |
|
FMANRP_SC-3-DBGTDLMSGMARSHAL |
3-Error |
Failed to copy debug SC request message to IPC buffer |
This operation to build a TDL message for debug SC command \n\ has failed. |
iosxe-service_controller |
LOG_STD_ACTION |
|
FMANRP_SC-3-INTFTDLMSGMARSHAL |
3-Error |
Failed to copy interface config message to IPC buffer for \n\ Interface [chars] 0x[hec] operation [chars] |
This operation to build a TDL message for interface configuration\n\ has failed. |
iosxe-service_controller |
LOG_STD_ACTION |
|
FMANRP_SC-3-SCIOSDENQUEUE |
3-Error |
Failed to enqueue SC [chars] message for transmission |
This operation to enqueue an IPC message for sending has failed. |
iosxe-service_controller |
LOG_STD_ACTION |
|
FMANRP_SC-3-SCTXTDLMSGMARSHAL |
3-Error |
Failed to copy service context config message to IPC buffer for\n\ sctx_name id [dec] |
This operation to build a TDL message for service context \n\ configuration has failed. |
iosxe-service_controller |
LOG_STD_ACTION |
|
FMANRP_SC-4-NOSERVICECTX |
4-Warning |
A mapping structure is null |
An unexpected condition has occurred which is due to the absence of\n\ a SC mapping structure. |
iosxe-service_controller |
LOG_STD_SH_CMD_ACTION |
|
FMANRP_SC-4-SCBADACTION |
4-Warning |
Invalid action [dec] for SC configuration |
An unexpected condition has occurred which is invalid action \n\ for a SC configuration. |
iosxe-service_controller |
LOG_STD_SH_CMD_ACTION |
|
FMANRP_SC-4-SCNOSWIDB |
4-Warning |
Sub-interface is null |
An unexpected condition has occurred which is due to the absence of\n\ a swidb structure. |
iosxe-service_controller |
"show ip interface" |
|
FMANRP_SSLVPN-3-AAATDLERR |
3-Error |
[chars][chars]. [chars] |
An unexpected condition has occurred in processing AAA request/reply message causing AAA handling failure. |
iosxe-sslvpn |
LOG_STD_ACTION |
|
FMANRP_SSLVPN-3-CFGSTATUSERR |
3-Error |
[chars]: [chars] |
An unexpected condition has occurred when got status of\n\ configuration |
iosxe-sslvpn |
LOG_STD_ACTION |
|
FMANRP_SSLVPN-3-CONDDEBERR |
3-Error |
[chars]. [chars] |
An unexpected condition has occurred in processing conditional debug message |
iosxe-sslvpn |
LOG_STD_ACTION |
|
FMANRP_SSLVPN-3-GWERR |
3-Error |
Failed [chars]: [chars] |
An unexpected condition has occurred in configuration processing \n\ causing configuration failure. |
iosxe-sslvpn |
LOG_STD_ACTION |
|
FMANRP_SSLVPN-3-PKIERR |
3-Error |
Failed [chars]: [chars] |
An unexpected condition has occurred in configuration processing \n\ causing configuration failure. |
iosxe-sslvpn |
LOG_STD_ACTION |
|
FMANRP_SSLVPN-3-RRICHUNKERR |
3-Error |
[chars] |
Error has occurred when requested memory for SSLVPN route handling |
iosxe-sslvpn |
LOG_STD_ACTION |
|
FMANRP_SSLVPN-3-RRITDLERR |
3-Error |
[chars][chars]. [chars] |
An unexpected condition has occurred in processing of SSLVPN route inject/remove message |
iosxe-sslvpn |
LOG_STD_ACTION |
|
FMANRP_SSLVPN-3-STATSCLEARERR |
3-Error |
Unable to send clear WEB VPN context stats message. [chars] [dec] |
This operation to build a TDL messages for WEB VPN context stats \n\ clearing has failed. |
iosxe-sslvpn |
LOG_STD_ACTION |
|
FMANRP_SSLVPN-3-STATSGUPDERR |
3-Error |
Update WEB VPN context stats error. [chars] [dec] |
An unexpected condition has occurred when updating global sslvpn \n\ statistics |
iosxe-sslvpn |
LOG_STD_ACTION |
|
FMANRP_SSLVPN-3-STATSWVUPDERR |
3-Error |
[chars]: [chars] |
An unexpected condition has occurred when updating ssl web vpn \n\ context statistics |
iosxe-sslvpn |
LOG_STD_ACTION |
|
FMANRP_SSLVPN-3-VWCONFERR |
3-Error |
Failed [chars]: [chars] |
An unexpected condition has occurred during WebVPN Context configuration\n\ causing failure. |
iosxe-sslvpn |
LOG_STD_ACTION |
|
FMANRP_SSLVPN-4-AAAFRIPWARN |
4-Warning |
[chars]Invalid framed ip address [inet] received from AAA. Not sending user config |
Wrong AAA server config. |
iosxe-sslvpn |
LOG_STD_ACTION |
|
FMANRP_VRF-3-API_FAILED |
3-Error |
NULL |
A call to the API of another component has indicated an\n\ error. |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_VRF-3-EINVAL |
3-Error |
NULL |
An unexpected input value to a function was incorrect |
iosxe-nat |
LOG_STD_ACTION |
|
FMANRP_VRF-3-ENOMEM |
3-Error |
NULL |
Not enough memory memory pre allocation failed |
picasso-infra |
LOG_STD_ACTION |
|
FMCORE-2-ACL_FAILURE |
2-Critical |
Interface [chars] traffic will not comply with ACLs in [chars] directions |
ACLs will not be applied on traffic for this interface due to TCAM\n\ resource contention. |
fm |
"The configured ACLs are too large to all fit in the hardware TCAM.\n\ Use mls tcam priority command to prioritize interfaces for hardware\n\ switching. Try and share the same ACLs across multiple interfaces\n\ in order to reduce TCAM resource contention." |
|
FMCORE-2-VACL_FAILURE |
2-Critical |
Interface [chars] traffic will not comply with VACLs in [chars] directions |
VACLs will not be applied on traffic for this interface due to TCAM\n\ resource contention. |
fm |
"The configured ACLs are too large to all fit in the hardware TCAM.\n\ Use mls tcam priority command to prioritize interfaces for hardware\n\ switching. Try and share the same ACLs across multiple interfaces\n\ in order to reduce TCAM resource contention." |
|
FMCORE-4-RACL_REDUCED |
4-Warning |
Interface [chars] routed traffic will be software switched in [chars] direction |
TCAM resource contention prevents ACLs from being applied in the TCAM\n\ for this interface. The traffic on this interface will be sent to\n\ software in order that the ACLs can be applied. |
fm |
"The configured ACLs are too large to all fit in the hardware TCAM.\n\ Use mls tcam priority command to prioritize interfaces for hardware\n\ switching. Try and share the same ACLs across multiple interfaces\n\ in order to reduce TCAM resource contention." |
|
FMCORE-6-RACL_ENABLED |
6-Information |
Interface [chars] routed traffic is hardware switched in [chars] direction |
Earlier TCAM resource contention may have prevented ACLs from being applied in the TCAM for this interface. It has been enabled and traffic on this interface is hardware switched. |
fm |
"No need to take an action for this as it is an informational" "message not an error message." |
|
FMD_ISSU-2-GET_BUFFER |
2-Critical |
FMD ISSU client failed to get buffer for message. Error: [dec] [chars] |
The FMD 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. |
medianet-metadata |
"show logging and show checkpoint client" |
|
FMD_ISSU-2-INIT |
2-Critical |
FMD ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The FMD 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. |
medianet-metadata |
LOG_STD_ACTION |
|
FMD_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
FMD ISSU client failed to send negotiation message. Error: [dec] [chars] |
The FMD 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. |
medianet-metadata |
"show logging and show checkpoint client" |
|
FMD_ISSU-2-SESSION_NEGO |
2-Critical |
FMD ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The FMD 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. |
medianet-metadata |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
FMD_ISSU-2-SESSION_REGISTRY |
2-Critical |
FMD ISSU client failed to register session information. Error: [dec] [chars] |
The FMD ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
medianet-metadata |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
FMD_ISSU-3-CAP_INVALID_SIZE |
3-Error |
FMD ISSU client capability list is empty. |
The FMD ISSU client capability exchange list size is invalid. |
medianet-metadata |
"show issu capability entires <Client_ID>" |
|
FMD_ISSU-3-CAP_NOT_COMPATIBLE |
3-Error |
FMD ISSU client capability exchange result incompatible. |
The FMD ISSU client capability exchange have negotiated as incompatible with the peer. |
medianet-metadata |
"show issu negotiated capability <Session_ID>" |
|
FMD_ISSU-3-INVALID_SESSION |
3-Error |
FMD ISSU client does not have a valid registered session. |
The FMD ISSU client does not have a valid registered session. |
medianet-metadata |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
FMD_ISSU-3-MSG_NOT_COMPATIBLE_WITH_PEER |
3-Error |
'Message Type [dec]' is not supported by FMD ISSU client at peer |
The FMD ISSU client at the peer supervisor is not compatible for this message type. The FMD client will be marked as incompatible with the peer. |
medianet-metadata |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
FMD_ISSU-3-MSG_NOT_OK |
3-Error |
FMD ISSU client 'Message Type [dec]' is not compatible |
The FMD ISSU client received an incompatible message from the peer device. The message cannot be processed. |
medianet-metadata |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
FMD_ISSU-3-MSG_SIZE |
3-Error |
FMD ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The FMD ISSU client failed to calculate the MTU for the specified message. The FMD ISSU client is not able to send the message to the standby device. |
medianet-metadata |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
FMD_ISSU-3-SESSION_UNREGISTRY |
3-Error |
FMD ISSU client failed to unregister session information. Error: [dec] [chars] |
The FMD ISSU client failed to unregister session information. |
medianet-metadata |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
FMD_ISSU-3-TRANSFORM_FAIL |
3-Error |
FMD ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The FMD 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 FMD state between the active device and the standby device is not identical. |
medianet-metadata |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
FMD-1-MALPINITFAILED |
1-Alert |
MAL process failed creation |
System is going through a software error and has failed to create a process |
- |
LOG_STD_SH_TECH_ACTION |
|
FMD-2-IPC_INIT |
2-Critical |
IPC message handler registration failure rc [dec] |
Registering an IPC message handler for the FMD feature failed. This will cause the feature to not function. |
qfp-fmd |
"This is normally a software issue. " "The consequences are that the FMD feature will not function. " LOG_STD_ACTION |
|
FMD-3-DBINITFAILED |
3-Error |
Database Init failed |
This message can occur for the following unrelated reasons. Each reason is accompanied by a recommended action.\n Due to resource unavailability the INIT would have been failed.\n |
- |
"If none of the previous actions fix the problem copy the error " "message exactly as it appears and report it to your Cisco " "technical support representative." |
|
FMD-3-DELETENODEFAILED |
3-Error |
Lookup failed for the flow of source_ip: [dec] dest_ip: [dec] source_port: [dec] dest_port: [dec] l4_protocol: [dec] class_id: [dec] vrf_table_id: [dec] |
This message can occur for the following unrelated reasons. Each reason is accompanied by a recommended action.\n This entry is not present in the Flow Table for the 4 Tuple to delete the node It might because the Table is not populated for the flow \n The flow would have been deleted \n |
- |
"If none of the previous actions fix the problem copy the error " "message exactly as it appears and report it to your Cisco " "technical support representative." |
|
FMD-3-IPC_NORES |
3-Error |
No space for the IPC reply size [dec] |
For a request from upper FMD software stack layers it was not possible to allocate space for a reply for the specified size. The consequence of this could be a stuck binding that cannot be established etc. In rare cases this could also affect other operations such as feature activation. |
qfp-fmd |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
FMD-3-IPC_OPEN_REPLY |
3-Error |
IPC Open Reply failed request [dec] |
For a request from upper FMD software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck binding that cannot be established etc. In rare cases this could also affect other operations such as feature activation. |
qfp-fmd |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
FMD-3-LOOKUPFAILED |
3-Error |
Lookup failed for the flow of source_ip: [dec] dest_ip: [dec] source_port: [dec] dest_port: [dec] l4_protocol: [dec] class_id: [dec] vrf_table_id: [dec] |
This message can occur for the following unrelated reasons. Each reason is accompanied by a recommended action.\n This entry is not present in the Flow Table for the 4 Tuple It might because the Table is not populated for the flow \n The flow would have been deleted \n |
- |
"If none of the previous actions fix the problem copy the error " "message exactly as it appears and report it to your Cisco " "technical support representative." |
|
FMD-3-MEMALLOCFAILED |
3-Error |
Memory Allocation failed |
This message can occur for the following unrelated reasons. Each reason is accompanied by a recommended action.\n The memory might be full due to Flow Limit Exceeded.\n The Memory Leak would have happened.\n |
- |
"If none of the previous actions fix the problem copy the error " "message exactly as it appears and report it to your Cisco " "technical support representative." |
|
FMD-3-NULL |
3-Error |
System receieved an invalid NULL pointer |
This message can occur for the following unrelated reasons. Each reason is accompanied by a recommended action.\n Due to a software error.\n |
- |
"If none of the previous actions fix the problem copy the error " "message exactly as it appears and report it to your Cisco " "technical support representative." |
|
FMD-3-TRANSPORT |
3-Error |
Operation [chars] on transport layer failed due to [chars] |
This message can occur for the following unrelated reasons. Each reason is accompanied by a recommended action.\n Due to a software error.\n |
- |
"If none of the previous actions fix the problem copy the error " "message exactly as it appears and report it to your Cisco " "technical support representative." |
|
FME_DP-3-DEBUG_REG_FAILED |
3-Error |
Flow Metric Engine fails to registrate with Conditional Debugging. |
Flow Metric Engine fails to registrate with Conditional Debugging infra. |
asr1k-avc |
LOG_STD_ACTION |
|
FME-2-IPC_INIT |
2-Critical |
IPC message handler registration failure rc [dec] |
Registering an IPC message handler for the FME feature failed. This will cause the feature to not function. |
qfp-mmon |
"This is normally a software issue. " "The consequences are that the FME feature will not function. " LOG_STD_ACTION |
|
FME-3-IPC_NORES |
3-Error |
No space for the IPC reply size [dec] |
For a request from upper FME software stack layers it was not possible to allocate space for a reply for the specified size. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation. |
qfp-mmon |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
FME-3-IPC_OPEN_REPLY |
3-Error |
IPC Open Reply failed request [dec] |
For a request from upper FME software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation. |
qfp-mmon |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
FMEA-4-DS_JIB_ERRLOG |
4-Warning |
DS JIB Santana FPGA Err log [chars] [chars] |
DS JIB Santana FPGA FMEA failure log |
cmts-infra |
"Minor non-fatal recoverable failure event" |
|
FNF_PROXY-3-EVAL_FREC_FIELD_LIST |
3-Error |
Failed with return code: [dec] |
Netflow failed to process an evaluate flow record field list request. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF_PROXY-3-EXPORTER_FORCE_TEMPLATE_REFRESH |
3-Error |
Failed with return code: [dec] |
Netflow failed to force a template refresh for an exporter. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF_PROXY-3-EXPORTER_INIT |
3-Error |
Failed with return code: [dec] |
Netflow failed to initialize the exporter. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF_PROXY-3-EXPORTER_OPTION_TEMPLATE_BIND |
3-Error |
Failed for exporter: [hec] with return code: [dec] |
Netflow failed to bind an option template. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF_PROXY-3-EXPORTER_OPTION_TEMPLATE_UNBIND |
3-Error |
Failed for exporter: [hec] with return code: [dec] |
Netflow failed to unbind an option template. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF_PROXY-3-EXPORTER_OPTION_TIMER_START |
3-Error |
Failed for exporter: [hec] with return code: [dec] |
Netflow failed to start an option timer. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF_PROXY-3-EXPORTER_OPTION_TIMER_STOP |
3-Error |
Failed for exporter: [hec] with return code: [dec] |
Netflow failed to stop an option timer. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF_PROXY-3-EXPORTER_SHUT |
3-Error |
Failed with return code: [dec] |
Netflow failed to shutdown the exporter. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF_PROXY-3-FLOW_CACHE_WALK |
3-Error |
Failed for session: [hec] with return code: [dec] |
Netflow failed to process a flow cache walk request. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF_PROXY-3-FLOW_CACHE_WALK_FLEXIBLE |
3-Error |
Failed for session: [hec] with return code: [dec] |
Netflow failed to process a flow cache walk/flexible request. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF_PROXY-3-FNF_CWALK_TOP_TALKERS_INVALID_SORT |
3-Error |
This field can't be used for sort |
Show Top Talkers command contains sort field specification that is not supported. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF_PROXY-3-IPC_UNHANDLED |
3-Error |
type [dec] |
An unknown message was received by the Netflow Client Proxy. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF_PROXY-3-MON_CACHE_AGER_INIT |
3-Error |
Failed with return code: [dec] |
Netflow failed to initialize the ager. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF_PROXY-3-MON_CACHE_AGER_SHUT |
3-Error |
Failed with return code: [dec] |
Netflow failed to shutdown the ager. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF_PROXY-3-MON_CACHE_CLEAN |
3-Error |
Failed with return code: [dec] |
Netflow failed to perform cache cleanup. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF_PROXY-3-MON_CACHE_FORCE_FLUSH |
3-Error |
Failed with return code: [dec] |
Netflow failed to force a cache flush. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF_PROXY-3-MON_CACHE_FREE_LIST_INIT |
3-Error |
Failed with return code: [dec] |
Netflow failed to initialize the free list. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF_PROXY-3-MON_CACHE_FREE_LIST_POOL_ADD |
3-Error |
Failed with return code: [dec] |
Netflow failed to populate the free list. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF_PROXY-3-OBJ_MODIFY |
3-Error |
Failed with return code: [dec] |
Netflow failed to process an object modify request. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF_PROXY-3-PROCESS_FREC_FIELD_LIST |
3-Error |
Failed with return code: [dec] |
Netflow failed to process a process flow record field list request. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF_PROXY-3-PROXY_IPC_PAK_ALLOC_FAILED |
3-Error |
- |
Allocation of IPC packet failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF_PROXY-3-PROXY_IPC_SEND_FAILED |
3-Error |
[dec] |
Could not send IPC reply for proxy request. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF_PROXY-3-STATS |
3-Error |
Failed with return code: [dec] |
Netflow failed to process a stats request. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF-3-CFT_REG_FAILED |
3-Error |
FNF fails to connect to CFT infra. |
FNF fails to connect to CFT infra. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF-3-CLEANUP_ENTRY |
3-Error |
Failed |
Netflow failed to clean up a record for reuse. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF-3-DEBUG_REG_FAILED |
3-Error |
FNF fails to registrate with Conditional Debugging. |
FNF fails to registrate with Conditional Debugging infra. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF-3-FNF_CWALK_FLEXIBLE_UNEXPECTED_LAYOUT |
3-Error |
Failed copy to CLI buffer PI will receive zero buffer |
Failed copy to CLI buffer during the walk process fill the buffer with 0 |
cpp-ucode |
LOG_STD_ACTION |
|
FNF-3-FNF_EXPORT_BUILD_TYPE_FAILED |
3-Error |
Format: [dec] |
FNF Exporter build failed. unknown type. |
cpp-ucode |
- |
|
FNF-3-FNF_FIELD_LIST_MEM_INSUFFICIENT |
3-Error |
Insufficient memory [dec] for field_list |
Internal error netflow client provided insufficient memory to process a field list |
cpp-ucode |
LOG_STD_ACTION |
|
FNF-3-FNF_FIELD_LIST_TOO_LARGE |
3-Error |
Field_list too large max [dec] |
Netflow field list contains too many fields. At most 32 fields are supported including any hidden fields automatically added as necessary for record keeping |
cpp-ucode |
LOG_STD_ACTION |
|
FNF-3-FNF_FIELD_LIST_TS_CNT_KEY |
3-Error |
Field_id [dec] must be non-key |
Netflow Field list specified timestamp/counter field as a key field which is not supported |
cpp-ucode |
LOG_STD_ACTION |
|
FNF-3-FNF_FIELD_LIST_VAR_INVALID |
3-Error |
Unknown field variety [dec] for field_id [dec] |
Internal error Netflow field list entry mapped to unknown field variety |
cpp-ucode |
LOG_STD_ACTION |
|
FNF-3-FNF_FIELD_UNEXPECTED_SIZE |
3-Error |
Unexpected size for field_id [dec] expected [dec]/got [dec] |
Netflow specified unexpected size for field_id |
cpp-ucode |
LOG_STD_ACTION |
|
FNF-3-FNF_FREC_LAYOUT_TOO_LARGE |
3-Error |
Flow record layout too large max [dec] |
Netflow field list results in a flow record layout which is too large. At most 128 bytes of flow record data is supported including any padding and any hidden fields automatically added as necessary for record keeping |
cpp-ucode |
LOG_STD_ACTION |
|
FNF-3-FNF_UNSUPPORTED_AGG_FMT |
3-Error |
Format: [dec] |
Netflow doesn't support this aggregation type. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF-3-FNF_UNSUPPORTED_EXP_FMT |
3-Error |
Format: [dec] |
Netflow doesn't support this export format. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF-3-FNF_UNSUPPORTED_MMA_FIELD |
3-Error |
MMA global ID [dec] Netflow field [dec] is not supported by MMA |
- |
- |
- |
|
FNF-3-FNF_UNSUPPORTED_OPTION |
3-Error |
Option: [dec] |
Netflow doesn't support this export option. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF-3-FREE_LIST_ADD |
3-Error |
Failed for record: 0x[hec] |
Netflow failed to return a record to the free list. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF-3-INVALID_CMD |
3-Error |
Flow builder encountered an invalid command: [dec]. |
Flow builder doesn't support the command encountered in the instruction stream. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF-3-INVALID_FO |
3-Error |
FNF FO is not valid |
FNF feature object is not valid. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF-3-IPFIX_UNSUPPORTED_MON_TYPE |
3-Error |
Monitor type: [dec] |
IPFIX doesn't support this monitor type. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF-3-KEY_SIZE_INVALID |
3-Error |
Unexpected key fields size: [dec] |
Netflow attempted to install a flow with an invalid key fields size. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF-3- LC_STATUS |
3-Error |
Flow monitor [chars] can not be added to [chars] rejected on module [chars] : [chars] |
The flow monitor has been rejected on the specified module. It will have been removed from the RP configuration too. This can happen for example when a monitor is removed and added again immediately before the tidy has been completed or in the case where a flow monitor is waiting at automore when the monitor is removed from the interface then reapplied |
flexible-netflow |
"Check the configuration of the Flow Monitor that" " was applied for errors. If the rejection was" " due to the LC not having finished cleaning up after" " a previous removal of a Flow Monitor wait until" " the cleaning up has finished then reapply the" " config." |
|
FNF-3- PROVISIONING |
3-Error |
[chars] failed to provision '[chars] flow monitor [chars] [chars]' on [chars]: [chars] |
The attachment of the Flow Monitor to has had a problem on the device identified. It may be working on other devices and the configuration is retained. |
flexible-netflow |
"Check the device identified is working as expected" " and that it can support the configuration of the" " Flow Monitor to the chosen attachment point." |
|
FNF-3-REFCNT_TIMEOUT |
3-Error |
never reached 0 for entry [hec] |
Netflow timed out waiting for an flow cache entries refcnt. to hit 0. The entry was forced out |
cpp-ucode |
LOG_STD_ACTION |
|
FNF-3-REFCNT_UNDERFLOW |
3-Error |
refcnt underflow for entry [hec] |
Netflow error caused flow cache entry reference count to go negative. The decrement was rescinded |
cpp-ucode |
LOG_STD_ACTION |
|
FNF-3-UNSUPPORTED_PROT |
3-Error |
[chars] |
This protocol is unsupported. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF-4-FREE_LIST_EMPTY |
4-Warning |
Monitor: 0x[hec] |
Netflow attempted to install a flow but no free flow records were available. |
cpp-ucode |
LOG_STD_ACTION |
|
FNF-6- AGER_OVERRIDE |
6-Information |
Flow [chars] time modified by [chars] to [dec] |
The aging timer has been modified and may be different from configured value. |
flexible-netflow |
LOG_STD_NO_ACTION |
|
FNF-6- CONFIGURATION |
6-Information |
Invalid FNF configuration: [chars] |
An invalid FNF configuration was detected. |
flexible-netflow |
"Review the FNF configuration before repeating the action." |
|
FNF-6-DYNAMIC_MONITORS_OVER_SUBSCRIPTION |
6-Information |
Interface [chars] dir=[chars]: the number of monitors that should run on |
QFP maximum supported number of monitors per packet was exceeded. As a result the excess number of monitors will not run on the packet. Static monitors always take priority over policy-map monitors. |
cpp-ucode |
LOG_STD_DBG_ACTION |
|
FNF-6- ERROR |
6-Information |
FNF error: [chars] |
An FNF error occurred. |
flexible-netflow |
"For more information repeat the action with FNF debugging enabled." |
|
FNF-6-SYNC_CACHE_TOO_MANY_RECS_FOR_INTERVAL |
6-Information |
For synchronized cache the number of records is larger than can be exported in configured interval. |
The number of records is too large for the configured interval. As a result some records may not be exported in a timely manner. Consider reducing cache size or increasing interval length. |
cpp-ucode |
LOG_STD_DBG_ACTION |
|
FORCE_RPR-3-PEER_OPER_MODE |
3-Error |
Peer node has reset [dec] times. [chars] |
The peer node has reset the maximum number allowed before reaching STANDBY-HOT state. The 'redundancy force-rpr' command is enabled and will try to set the peer system to RPR operating mode. |
redundancy-rf |
LOG_STD_ACTION FORCE_RPR_STD_ACTION |
|
FORCE_RPR-3-RF_REGISTER |
3-Error |
RF error = [dec]. [chars] |
During system initialization Force RPR component was unable to register with the Redundancy Facility. |
redundancy-rf |
LOG_STD_ACTION FORCE_RPR_STD_ACTION |
|
FORCE_RPR-4-NOT_ON_ACTIVE |
4-Warning |
[chars] |
Only the Active node may enable this feature. Make sure you're on the Active system before trying to enable this command |
redundancy-rf |
LOG_STD_ACTION FORCE_RPR_STD_ACTION |
|
FPD_MGMT-2-CREATE_FAIL |
2-Critical |
Couldn't create [chars]. |
The system does not have enough free main memory to create the specified resource. |
spa-infra-fpd |
FPD_NO_FREE_MEMORY_STD_ACTION |
|
FPD_MGMT-2-CREATE_FAIL |
2-Critical |
Couldn't create [chars]. |
The system does not have enough free main memory to create the specified resource. |
- |
FPD_NO_FREE_MEMORY_STD_ACTION |
|
FPD_MGMT-3-BNDL_CARD_TYPE_MISMATCH |
3-Error |
The [chars] file does not contain the card type [hex] in the image bundle |
The image bundle in the indicated file does not contain a correct card type value for the target card. |
spa-infra-fpd |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-BNDL_CARD_TYPE_MISMATCH |
3-Error |
The [chars] file does not contain the card type [hex] in the image bundle |
The image bundle in the indicated file does not contain a correct card type value for the target card. |
- |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-BNDL_CRC_CHECK_FAIL |
3-Error |
The [chars] file contains a corrupted image bundle - CRC mismatch: current value [hex] expected value [hex]. Please make sure that this is a valid FPD image [chars] file for card in [chars]. |
The file failed the CRC checking process. This failure indicates a corrupt FPD image bundle or package file. |
spa-infra-fpd |
"Try to download again the required package from the Cisco " "Software Center website as the indicated one might be corrupted. " "If the problem persists copy the error message exactly as it appears " "and gather the output of the <CmdBold>show hw-module subslot fpd" "<NoCmdBold> <CmdBold>show upgrade fpd table<NoCmdBold> and <CmdBold>" "show upgrade fpd file<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> commands " "then contact your technical support representative with the gathered " "information." |
|
FPD_MGMT-3-BNDL_CRC_CHECK_FAIL |
3-Error |
The [chars] file contains a corrupted image bundle - CRC mismatch: current value [hex] expected value [hex]. Please make sure that this is a valid FPD image [chars] file for card in [chars]. |
The file failed the CRC checking process. This failure indicates a corrupt FPD image bundle or package file. |
- |
"Try to download again the required package from the Cisco " "Software Center website as the indicated one might be corrupted. " "If the problem persists copy the error message exactly as it appears " "and gather the output of the <CmdBold>show hw-module subslot fpd" "<NoCmdBold> <CmdBold>show upgrade fpd table<NoCmdBold> and <CmdBold>" "show upgrade fpd file<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> commands " "then contact your technical support representative with the gathered " "information." |
|
FPD_MGMT-3-BNDL_NAME_PREFIX_MISMATCH |
3-Error |
The [chars] file contains a bundle name prefix [chars] that does not match |
The content of the selected FPD image bundle does not match its filename. |
spa-infra-fpd |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-BNDL_NAME_PREFIX_MISMATCH |
3-Error |
The [chars] file contains a bundle name prefix [chars] that does not match |
The content of the selected FPD image bundle does not match its filename. |
- |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-BNDL_WRONG_HDR_LEN |
3-Error |
The [chars] file contains wrong header length for the image bundle: [dec] bytes expected [dec] bytes. Please make sure that this is a valid |
The indicated file might not be a valid FPD image bundle or package file for the target card. |
spa-infra-fpd |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-BNDL_WRONG_HDR_LEN |
3-Error |
The [chars] file contains wrong header length for the image bundle: [dec] bytes expected [dec] bytes. Please make sure that this is a valid |
The indicated file might not be a valid FPD image bundle or package file for the target card. |
- |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-BNDL_WRONG_MAGIC_NUM |
3-Error |
The [chars] file contains a wrong magic number for the image bundle: [hex] expected [hex]. Please make sure that this is a valid FPD image [chars] |
The indicated file might not be a valid FPD image bundle or package file for the target card or the file could be corrupted. |
spa-infra-fpd |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-BNDL_WRONG_MAGIC_NUM |
3-Error |
The [chars] file contains a wrong magic number for the image bundle: [hex] expected [hex]. Please make sure that this is a valid FPD image [chars] |
The indicated file might not be a valid FPD image bundle or package file for the target card or the file could be corrupted. |
- |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-BNDL_WRONG_SIZE |
3-Error |
The [chars] file contains incorrect image bundle size: [dec] bytes expected [dec] bytes. Please make sure that this is a valid FPD image [chars] file |
The indicated file might not be a valid FPD image bundle or package file for the target card. |
spa-infra-fpd |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-BNDL_WRONG_SIZE |
3-Error |
The [chars] file contains incorrect image bundle size: [dec] bytes expected [dec] bytes. Please make sure that this is a valid FPD image [chars] file |
The indicated file might not be a valid FPD image bundle or package file for the target card. |
- |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-BUNDLE_EXTRACT_ERROR |
3-Error |
Cannot extract the [chars] bundle from [chars] - [chars] |
Bundle file extraction error. The cause of the failure is indicated in the error message. The indicated file might not be a valid FPD image package file. |
spa-infra-fpd |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-BUNDLE_EXTRACT_ERROR |
3-Error |
Cannot extract the [chars] bundle from [chars] - [chars] |
Bundle file extraction error. The cause of the failure is indicated in the error message. The indicated file might not be a valid FPD image package file. |
- |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-CARD_DISABLED |
3-Error |
[chars] card in [chars] is being disabled because of an incompatible FPD image version. Note that the [chars] package will be required if you want to perform the upgrade operation. |
The indicated card contains an incompatible FPD image version and is being disabled to avoid operational problems with the existing Cisco IOS software. This can happen if the automatic upgrade feature has not been enabled with the <CmdBold>upgrade fpd auto<NoCmdBold> global configuration command or if the automatic upgrade operation failed to perform the required upgrade or because it could not find the necessary FPD image package file. The incompatible image will need to be upgraded in order for the system to enable the card. |
spa-infra-fpd |
"The FPD image upgrade can be performed automatically by making sure that " "the automatic upgrade feature is enabled with the <CmdBold>upgrade fpd " "auto<NoCmdBold> global configuration command and the necessary FPD image " "package file is located in the system's default filesystem e.g. disk0: " |
|
FPD_MGMT-3-CARD_DISABLED |
3-Error |
[chars] card in [chars] is being disabled because of an incompatible FPD image version. Note that the [chars] package will be required if you want to perform the upgrade operation. |
The indicated card contains an incompatible FPD image version and is being disabled to avoid operational problems with the existing Cisco IOS software. This can happen if the automatic upgrade feature has not been enabled with the <CmdBold>upgrade fpd auto<NoCmdBold> global configuration command or if the automatic upgrade operation failed to perform the required upgrade or because it could not find the necessary FPD image package file. The incompatible image will need to be upgraded in order for the system to enable the card. |
- |
"The FPD image upgrade can be performed automatically by making sure that " "the automatic upgrade feature is enabled with the <CmdBold>upgrade fpd " "auto<NoCmdBold> global configuration command and the necessary FPD image " "package file is located in the system's default filesystem e.g. disk0: " |
|
FPD_MGMT-3-CLOSE_FAILED |
3-Error |
Failed to close [chars] file. |
FPD_INTERNAL_SW_ERR_STD_EXPLANATION |
spa-infra-fpd |
LOG_STD_ACTION |
|
FPD_MGMT-3-CLOSE_FAILED |
3-Error |
Failed to close [chars] file. |
FPD_INTERNAL_SW_ERR_STD_EXPLANATION |
- |
LOG_STD_ACTION |
|
FPD_MGMT-3-DUPLICATE_UPGRADE_RESULT |
3-Error |
Upgrade result already received for the FPD image upgrade of FPD ID [dec] for [chars] card in [chars]. |
FPD_INTERNAL_SW_ERR_STD_EXPLANATION |
spa-infra-fpd |
LOG_STD_ACTION |
|
FPD_MGMT-3-DUPLICATE_UPGRADE_RESULT |
3-Error |
Upgrade result already received for the FPD image upgrade of FPD ID [dec] for [chars] card in [chars]. |
FPD_INTERNAL_SW_ERR_STD_EXPLANATION |
- |
LOG_STD_ACTION |
|
FPD_MGMT-3-FPD_UPGRADE_CANCELED |
3-Error |
Rest of the FPD upgrade sequence for [chars] card in [chars] has been canceled due to upgrade failure with [chars] FPD ID=[dec] image. |
The FPD image upgrade process for additional FPD images has been canceled due to upgrade error in the indicated device. |
spa-infra-fpd |
"Retry the upgrade operation again. If the affected card remains " "disabled by the system after attempts to retry the upgrade then copy " "the error message exactly as it appears and gather the output of " "<CmdBold>show hw-module subslot fpd<NoCmdBold> and contact your " "technical support representative with the gathered information." |
|
FPD_MGMT-3-FPD_UPGRADE_CANCELED |
3-Error |
Rest of the FPD upgrade sequence for [chars] card in [chars] has been canceled due to upgrade failure with [chars] FPD ID=[dec] image. |
The FPD image upgrade process for additional FPD images has been canceled due to upgrade error in the indicated device. |
- |
"Retry the upgrade operation again. If the affected card remains " "disabled by the system after attempts to retry the upgrade then copy " "the error message exactly as it appears and gather the output of " "<CmdBold>show hw-module subslot fpd<NoCmdBold> and contact your " "technical support representative with the gathered information." |
|
FPD_MGMT-3-FPD_UPGRADE_FAILED |
3-Error |
[chars] FPD ID=[dec] image upgrade for [chars] card in [chars] has FAILED. |
The FPD image upgrade process has failed for the indicated device. |
spa-infra-fpd |
"Retry the upgrade operation again. If the affected card remains " "disabled by the system after attempts to retry the upgrade then copy " "the error message exactly as it appears and gather the output of " "<CmdBold>show hw-module subslot fpd<NoCmdBold> and contact your " "technical support representative with the gathered information." |
|
FPD_MGMT-3-FPD_UPGRADE_FAILED |
3-Error |
[chars] FPD ID=[dec] image upgrade for [chars] card in [chars] has FAILED. |
The FPD image upgrade process has failed for the indicated device. |
- |
"Retry the upgrade operation again. If the affected card remains " "disabled by the system after attempts to retry the upgrade then copy " "the error message exactly as it appears and gather the output of " "<CmdBold>show hw-module subslot fpd<NoCmdBold> and contact your " "technical support representative with the gathered information." |
|
FPD_MGMT-3-IMG_CRC_CHECK_FAILED |
3-Error |
The FPD image for [chars] FPD ID [dec] in [chars] file is corrupted - CRC |
The image failed the CRC checking process this indicates a corrupt FPD image bundle or package file. |
spa-infra-fpd |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-IMG_CRC_CHECK_FAILED |
3-Error |
The FPD image for [chars] FPD ID [dec] in [chars] file is corrupted - CRC |
The image failed the CRC checking process this indicates a corrupt FPD image bundle or package file. |
- |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-IMG_DATA_UNCOMPRESS_ERROR |
3-Error |
Could not uncompress [chars] FPD image for [chars] in [chars]. |
An error has been detected during the uncompress operation of the compressed FPD image data. |
spa-infra-fpd |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-IMG_DATA_UNCOMPRESS_ERROR |
3-Error |
Could not uncompress [chars] FPD image for [chars] in [chars]. |
An error has been detected during the uncompress operation of the compressed FPD image data. |
- |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-IMG_VER_NOT_FOUND |
3-Error |
FPD image version information is not available for [chars] card in [chars]. All the FPD images will be upgraded to recover from this error. |
The FPD image version information for the indicated card is not available because the system was not able to extract this information for all the FPDs in the card. This could be the result of a corrupted FPD image from a power failure. |
spa-infra-fpd |
FPD_VERSION_ERROR_STD_ACTION |
|
FPD_MGMT-3-IMG_VER_NOT_FOUND |
3-Error |
FPD image version information is not available for [chars] card in [chars]. All the FPD images will be upgraded to recover from this error. |
The FPD image version information for the indicated card is not available because the system was not able to extract this information for all the FPDs in the card. This could be the result of a corrupted FPD image from a power failure. |
- |
FPD_VERSION_ERROR_STD_ACTION |
|
FPD_MGMT-3-INCOMP_BNDL_VER |
3-Error |
The selected [chars] file contain an image bundle that has a version number that is incompatible for this IOS release - [chars]. Selected version = [dec].[dec] minimum compatible version = [dec].[dec]. Please make sure that this is a valid FPD image [chars] file for card in [chars]. The SPA type is [chars]. |
The version of the selected FPD image bundle does not contain a valid version number that is compatible for the IOS release. The major version number should be the same and the minor version number should be at least equal to the minimal required version. |
spa-infra-fpd |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-INCOMP_BNDL_VER |
3-Error |
The selected [chars] file contain an image bundle that has a version number that is incompatible for this IOS release - [chars]. Selected version = [dec].[dec] minimum compatible version = [dec].[dec]. Please make sure that this is a valid FPD image [chars] file for card in [chars]. |
The version of the selected FPD image bundle does not contain a valid version number that is compatible for the IOS release. The major version number should be the same and the minor version number should be at least equal to the minimal required version. |
- |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-INCOMP_IMG_VER |
3-Error |
Incompatible [chars] FPD ID=[dec] image version detected for [chars] card |
An incompatible FPD image version has been detected. The FPD image needs to be upgraded either automatically or manually to make the card operational. If the automatic upgrade feature is not enabled or if the system cannot find the necessary FPD image package file then the card will be disabled. |
spa-infra-fpd |
FPD_VERSION_ERROR_STD_ACTION |
|
FPD_MGMT-3-INCOMP_IMG_VER |
3-Error |
Incompatible [chars] FPD ID=[dec] image version detected for [chars] card |
An incompatible FPD image version has been detected. The FPD image needs to be upgraded either automatically or manually to make the card operational. If the automatic upgrade feature is not enabled or if the system cannot find the necessary FPD image package file then the card will be disabled. |
- |
FPD_VERSION_ERROR_STD_ACTION |
|
FPD_MGMT-3-INVALID_IMAGE_SIZE |
3-Error |
The [chars] FPD image from [chars] file does not have a valid image size: expected size = [dec] bytes actual size = [dec] bytes. |
The size of the indicated FPD image does not have the expected size. The FPD image bundle or package might not be a valid file. |
spa-infra-fpd |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-INVALID_IMAGE_SIZE |
3-Error |
The [chars] FPD image from [chars] file does not have a valid image size: expected size = [dec] bytes actual size = [dec] bytes. |
The size of the indicated FPD image does not have the expected size. The FPD image bundle or package might not be a valid file. |
- |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-INVALID_IMG_FORMAT |
3-Error |
Invalid image format '[chars]' detected for FPD ID=[dec]. |
The selected FPD image to upgrade the indicated field programmable device does not have the right image format that can be used by the system to perform the upgrade operation. |
spa-infra-fpd |
"Please check if the FPD image package used in the upgrade is for the " "correct platform. This can be checked by using the <CmdBold>show upgrade " "fpd package default<NoCmdBold> privileged EXEC command." |
|
FPD_MGMT-3-INVALID_IMG_FORMAT |
3-Error |
Invalid image format '[chars]' detected for FPD ID=[dec]. |
The selected FPD image to upgrade the indicated field programmable device does not have the right image format that can be used by the system to perform the upgrade operation. |
- |
"Please check if the FPD image package used in the upgrade is for the " "correct platform. This can be checked by using the <CmdBold>show upgrade " "fpd package default<NoCmdBold> privileged EXEC command." |
|
FPD_MGMT-3-INVALID_IMG_VER |
3-Error |
Invalid [chars] FPD ID=[dec] image version detected for [chars] card in [chars]. |
The indicated field programmable device contains an invalid version for the FPD image because the system was not able to extract this information from the indicated card. A failed upgrade attempt might have corrupted the FPD image identification on the device. |
spa-infra-fpd |
FPD_VERSION_ERROR_STD_ACTION |
|
FPD_MGMT-3-INVALID_IMG_VER |
3-Error |
Invalid [chars] FPD ID=[dec] image version detected for [chars] card in [chars]. |
The indicated field programmable device contains an invalid version for the FPD image because the system was not able to extract this information from the indicated card. A failed upgrade attempt might have corrupted the FPD image identification on the device. |
- |
FPD_VERSION_ERROR_STD_ACTION |
|
FPD_MGMT-3-INVALID_PKG_FILE |
3-Error |
The indicated file [chars] is not a valid FPD image package file - [chars] |
The file format does not appear to be a valid FPD image package. |
spa-infra-fpd |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-INVALID_PKG_FILE |
3-Error |
The indicated file [chars] is not a valid FPD image package file - [chars] |
The file format does not appear to be a valid FPD image package. |
- |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-INVALID_PKG_FILE_SIZE |
3-Error |
The indicated file [chars] does not have a valid FPD image package |
The file size of the indicated FPD image package does not meet the required minimum size. The file is too small to be a valid FPD image package file. |
spa-infra-fpd |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-INVALID_PKG_FILE_SIZE |
3-Error |
The indicated file [chars] does not have a valid FPD image package |
The file size of the indicated FPD image package does not meet the required minimum size. The file is too small to be a valid FPD image package file. |
- |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-INVALID_UPGRADE_RESULT |
3-Error |
Invalid upgrade result '[dec]' received for the FPD image upgrade of [chars] FPD ID=[dec] for [chars] card in [chars]. |
FPD_INTERNAL_SW_ERR_STD_EXPLANATION |
spa-infra-fpd |
LOG_STD_ACTION |
|
FPD_MGMT-3-INVALID_UPGRADE_RESULT |
3-Error |
Invalid upgrade result '[dec]' received for the FPD image upgrade of [chars] FPD ID=[dec] for [chars] card in [chars]. |
FPD_INTERNAL_SW_ERR_STD_EXPLANATION |
- |
LOG_STD_ACTION |
|
FPD_MGMT-3-IPC_FAILED |
3-Error |
Failed to send IPC message to [chars] in [chars] - [chars] |
The system failed to send a message via IPC to the indicated card. The cause of the specific IPC failure is inicated in the message. |
spa-infra-fpd |
LOG_STD_ACTION |
|
FPD_MGMT-3-IPC_FAILED |
3-Error |
Failed to send IPC message to [chars] in [chars] - [chars] |
The system failed to send a message via IPC to the indicated card. The cause of the specific IPC failure is inicated in the message. |
- |
LOG_STD_ACTION |
|
FPD_MGMT-3-MAJOR_VER_MISMATCH |
3-Error |
Major image version mismatch detected with [chars] FPD ID=[dec] for [chars] card |
A major image version mismatch has been detected. This incompatibility will need to be resolved by doing an upgrade or downgrade operation either automatically or manually to make the card operational. If the automatic upgrade feature is not enabled or if the system cannot find the necessary FPD image package file then the card will be disabled. |
spa-infra-fpd |
FPD_VERSION_ERROR_STD_ACTION |
|
FPD_MGMT-3-MAJOR_VER_MISMATCH |
3-Error |
Major image version mismatch detected with [chars] FPD ID=[dec] for [chars] card |
A major image version mismatch has been detected. This incompatibility will need to be resolved by doing an upgrade or downgrade operation either automatically or manually to make the card operational. If the automatic upgrade feature is not enabled or if the system cannot find the necessary FPD image package file then the card will be disabled. |
- |
FPD_VERSION_ERROR_STD_ACTION |
|
FPD_MGMT-3-MISSING_BUNDLE_ENTRY |
3-Error |
Failed to find a matching entry in the programmable device bundle information table for [chars] in [chars]. Card type or HW version [dec].[dec] |
FPD_INTERNAL_SW_ERR_STD_EXPLANATION |
spa-infra-fpd |
LOG_STD_ACTION |
|
FPD_MGMT-3-MISSING_BUNDLE_ENTRY |
3-Error |
Failed to find a matching entry in the programmable device bundle information table for [chars] in [chars]. Card type or HW version [dec].[dec] |
FPD_INTERNAL_SW_ERR_STD_EXPLANATION |
- |
LOG_STD_ACTION |
|
FPD_MGMT-3-MISSING_DEV_INFO |
3-Error |
Could not find [chars] FPD ID=[dec] in the list of FPD IDs populated |
FPD_INTERNAL_SW_ERR_STD_EXPLANATION |
spa-infra-fpd |
LOG_STD_ACTION |
|
FPD_MGMT-3-MISSING_DEV_INFO |
3-Error |
Could not find [chars] FPD ID=[dec] in the list of FPD IDs populated |
FPD_INTERNAL_SW_ERR_STD_EXPLANATION |
- |
LOG_STD_ACTION |
|
FPD_MGMT-3-MISSING_IMAGE |
3-Error |
Could not find the required [chars] image FPD ID=[dec] and FPD version=[dec].[dec] compatible with HW version=[dec].[dec] from the [chars]-fpd.bndl bundle in [chars] |
The indicated FPD image bundle or package file might not be the correct one. IF this is a FPD image package file then an incompatible package file might have been renamed with a filename that matched with the one that the system is expecting for this Cisco IOS software release. You should never rename an FPD image package file name. |
spa-infra-fpd |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-MISSING_IMAGE |
3-Error |
Could not find the required [chars] image FPD ID=[dec] and FPD version=[dec].[dec] compatible with HW version=[dec].[dec] from the [chars]-fpd.bndl bundle in [chars] |
The indicated FPD image bundle or package file might not be the correct one. IF this is a FPD image package file then an incompatible package file might have been renamed with a filename that matched with the one that the system is expecting for this Cisco IOS software release. You should never rename an FPD image package file name. |
- |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-OPEN_FAILED |
3-Error |
Failed to open [chars] [chars]. Please make sure that the required file |
The system cannot access the required file from the indicated URL. |
spa-infra-fpd |
"Make sure that the indicated URL is a valid path and the system " "has access to the filesystem where the file has been placed." |
|
FPD_MGMT-3-OPEN_FAILED |
3-Error |
Failed to open [chars] [chars]. Please make sure that the required file |
The system cannot access the required file from the indicated URL. |
- |
"Make sure that the indicated URL is a valid path and the system " "has access to the filesystem where the file has been placed." |
|
FPD_MGMT-3-OUT_OF_MEMORY |
3-Error |
Could not allocate the required [dec] bytes of memory. |
The system does not have enough free main memory to download the bundle file. |
spa-infra-fpd |
FPD_NO_FREE_MEMORY_STD_ACTION |
|
FPD_MGMT-3-OUT_OF_MEMORY |
3-Error |
Could not allocate the required [dec] bytes of memory. |
The system does not have enough free main memory to download the bundle file. |
- |
FPD_NO_FREE_MEMORY_STD_ACTION |
|
FPD_MGMT-3-PKG_FILE_SEARCH_FAILED |
3-Error |
FPD image package [chars] cannot be found in system's flash card or |
By default if the <CmdBold>upgrade fpd path<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> global configuration command is not configured then the system will try to locate the required FPD image package file from removable flash cards or disks that are accessible by the system for FPD upgrade. This message indicates that the system could not find the package file. |
spa-infra-fpd |
"Make sure that the indicated FPD image package file is copied into a " "flash card or disk that is accessible by the system then restart the " "FPD upgrade by reinsertion of the target card to the system or use of " "a system command to reload or power-cycle the target card." |
|
FPD_MGMT-3-PKG_FILE_SEARCH_FAILED |
3-Error |
FPD image package [chars] cannot be found in system's flash card or |
By default if the <CmdBold>upgrade fpd path<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> global configuration command is not configured then the system will try to locate the required FPD image package file from removable flash cards or disks that are accessible by the system for FPD upgrade. This message indicates that the system could not find the package file. |
- |
"Make sure that the indicated FPD image package file is copied into a " "flash card or disk that is accessible by the system then restart the " "FPD upgrade by reinsertion of the target card to the system or use of " "a system command to reload or power-cycle the target card." |
|
FPD_MGMT-3-PKG_VER_FILE_EXTRACT_ERROR |
3-Error |
Cannot extract the [chars] version file from [chars] - [chars] |
Package version file extraction error. The cause of the failure is indicated in the error message. The indicated file might not be a valid FPD image package file. |
spa-infra-fpd |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-PKG_VER_FILE_EXTRACT_ERROR |
3-Error |
Cannot extract the [chars] version file from [chars] - [chars] |
Package version file extraction error. The cause of the failure is indicated in the error message. The indicated file might not be a valid FPD image package file. |
- |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-PKG_VER_MISMATCH_NOTE |
3-Error |
The FPD image package being used [chars] is not the right version for |
The indicated FPD image package that is being used in FPD automatic upgrade does not contain the correct version information for the IOS version that is running in the system. This condition can occur if a different version of the FPD image package was renamed to match the filename that the IOS image is expecting to use. The upgrade operation will still be performed by trying to find the required FPD image from the renamed package file. |
spa-infra-fpd |
"If the upgrade operation fails because the required FPD image cannot be " "found with the renamed FPD image package replace the wrong package " "file with a valid one and perform the upgrade operation again." |
|
FPD_MGMT-3-PKG_VER_MISMATCH_NOTE |
3-Error |
The FPD image package being used [chars] is not the right version for |
The indicated FPD image package that is being used in FPD automatic upgrade does not contain the correct version information for the IOS version that is running in the system. This condition can occur if a different version of the FPD image package was renamed to match the filename that the IOS image is expecting to use. The upgrade operation will still be performed by trying to find the required FPD image from the renamed package file. |
- |
"If the upgrade operation fails because the required FPD image cannot be " "found with the renamed FPD image package replace the wrong package " "file with a valid one and perform the upgrade operation again." |
|
FPD_MGMT-3-READ_BNDL_HDR_ERROR |
3-Error |
Failed to read the FPD bundle header from [chars] file. |
The indicated file might not be a valid FPD image bundle or package file. |
spa-infra-fpd |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-READ_BNDL_HDR_ERROR |
3-Error |
Failed to read the FPD bundle header from [chars] file. |
The indicated file might not be a valid FPD image bundle or package file. |
- |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-READ_ERROR |
3-Error |
Could not read the [chars] file. |
The system cannot read the required file from the indicated URL. |
spa-infra-fpd |
"Make sure that the indicated URL is a valid path and the system " "has access to the filesystem where the file has been placed." |
|
FPD_MGMT-3-READ_ERROR |
3-Error |
Could not read the [chars] file. |
The system cannot read the required file from the indicated URL. |
- |
"Make sure that the indicated URL is a valid path and the system " "has access to the filesystem where the file has been placed." |
|
FPD_MGMT-3-SEND_IMG_FAILED |
3-Error |
[chars] FPD ID=[dec] image for [chars] card in [chars] has failed to be sent |
The FPD image was not able to be sent for the upgrade operation. The system might be too busy to handle this operation. The affected card will be disabled by this failure. |
spa-infra-fpd |
"Wait until the system load is lower to try again with the manual upgrade " "procedure by using the <CmdBold>upgrade hw-module<NoCmdBold> privileged " "EXEC command. If the symptom persists copy the error message " "exactly as it appears and gather the output of the <CmdBold>show " "tech-support<NoCmdBold> command and contact your technical support " "representative with the gathered information." |
|
FPD_MGMT-3-SEND_IMG_FAILED |
3-Error |
[chars] FPD ID=[dec] image for [chars] card in [chars] has failed to be sent |
The FPD image was not able to be sent for the upgrade operation. The system might be too busy to handle this operation. The affected card will be disabled by this failure. |
- |
"Wait until the system load is lower to try again with the manual upgrade " "procedure by using the <CmdBold>upgrade hw-module<NoCmdBold> privileged " "EXEC command. If the symptom persists copy the error message " "exactly as it appears and gather the output of the <CmdBold>show " "tech-support<NoCmdBold> command and contact your technical support " "representative with the gathered information." |
|
FPD_MGMT-3-SW_ERROR |
3-Error |
NULL |
FPD_INTERNAL_SW_ERR_STD_EXPLANATION |
spa-infra-fpd |
LOG_STD_ACTION |
|
FPD_MGMT-3-SW_ERROR |
3-Error |
NULL |
FPD_INTERNAL_SW_ERR_STD_EXPLANATION |
- |
LOG_STD_ACTION |
|
FPD_MGMT-3-TOO_MANY_FPD_ENTRIES |
3-Error |
Too many FPD entries for the FPD Bundle Info Table. Required number of entries = [dec] maximum number of entries allowed = [dec]. |
FPD_INTERNAL_SW_ERR_STD_EXPLANATION |
spa-infra-fpd |
LOG_STD_ACTION |
|
FPD_MGMT-3-TOO_MANY_FPD_ENTRIES |
3-Error |
Too many FPD entries for the FPD Bundle Info Table. Required number of entries = [dec] maximum number of entries allowed = [dec]. |
FPD_INTERNAL_SW_ERR_STD_EXPLANATION |
- |
LOG_STD_ACTION |
|
FPD_MGMT-3-UNKNOWN_BNDL_HDR_FORMAT |
3-Error |
Unknown header format version: [hex] |
FPD_INTERNAL_SW_ERR_STD_EXPLANATION |
spa-infra-fpd |
LOG_STD_ACTION |
|
FPD_MGMT-3-UNKNOWN_BNDL_HDR_FORMAT |
3-Error |
Unknown header format version: [hex] |
FPD_INTERNAL_SW_ERR_STD_EXPLANATION |
- |
LOG_STD_ACTION |
|
FPD_MGMT-3-UPGRADE_LIST_FULL |
3-Error |
Could not add a new entry in the FPD Management Upgrade List. No upgrade will be performed for the [chars] card in [chars]. |
FPD_INTERNAL_SW_ERR_STD_EXPLANATION |
spa-infra-fpd |
LOG_STD_ACTION |
|
FPD_MGMT-3-UPGRADE_LIST_FULL |
3-Error |
Could not add a new entry in the FPD Management Upgrade List. No upgrade will be performed for the [chars] card in [chars]. |
FPD_INTERNAL_SW_ERR_STD_EXPLANATION |
- |
LOG_STD_ACTION |
|
FPD_MGMT-3-WRONG_IMG_DATA_LEN |
3-Error |
The FPD image for [chars] FPD ID [dec] in [chars] file contains wrong data |
The indicated file might not be a valid FPD image bundle or package file for the card. |
spa-infra-fpd |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-WRONG_IMG_DATA_LEN |
3-Error |
The FPD image for [chars] FPD ID [dec] in [chars] file contains wrong data |
The indicated file might not be a valid FPD image bundle or package file for the card. |
- |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-WRONG_IMG_HDR_LEN |
3-Error |
The FPD image for [chars] FPD ID [dec] in [chars] file contains wrong header |
The indicated file might not be a valid FPD image bundle or package file for the card. |
spa-infra-fpd |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-WRONG_IMG_HDR_LEN |
3-Error |
The FPD image for [chars] FPD ID [dec] in [chars] file contains wrong header |
The indicated file might not be a valid FPD image bundle or package file for the card. |
- |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-WRONG_IMG_MAGIC_NUM |
3-Error |
The FPD image for [chars] FPD ID [dec] in [chars] file contains wrong magic |
The indicated file might not be a valid FPD image bundle or package file for the card. |
spa-infra-fpd |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-WRONG_IMG_MAGIC_NUM |
3-Error |
The FPD image for [chars] FPD ID [dec] in [chars] file contains wrong magic |
The indicated file might not be a valid FPD image bundle or package file for the card. |
- |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-WRONG_IMG_MAJOR_VER |
3-Error |
The selected FPD image for upgrade contains wrong FPD image major version number = '[dec]' expected number = '[dec]' for [chars] FPD ID [dec]. |
The file used for upgrade might not be a valid FPD image bundle or package file for the card. |
spa-infra-fpd |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-3-WRONG_IMG_MAJOR_VER |
3-Error |
The selected FPD image for upgrade contains wrong FPD image major version number = '[dec]' expected number = '[dec]' for [chars] FPD ID [dec]. |
The file used for upgrade might not be a valid FPD image bundle or package file for the card. |
- |
FPD_WRONG_PKG_STD_ACTION |
|
FPD_MGMT-4-BYPASS_AUTO_UPGRADE |
4-Warning |
The automatic FPD image upgrade feature is not enabled bypassing the image upgrade for [chars] card in [chars]. |
The automatic FPD image upgrade feature is not enabled. The incompatible image will not be automatically upgraded. The card will be disabled until the image is upgraded to a compatible version. |
spa-infra-fpd |
"Enable the automatic FPD image upgrade with the <CmdBold>upgrade fpd " "auto<NoCmdBold> global configuration command or use the <CmdBold>upgrade " "hw-module<NoCmdBold> privileged EXEC command for a manual upgrade " "operation. For more information about these commands refer to the " FPD_DOCUMENT_NAME "." |
|
FPD_MGMT-4-BYPASS_AUTO_UPGRADE |
4-Warning |
The automatic FPD image upgrade feature is not enabled bypassing the image upgrade for [chars] card in [chars]. |
The automatic FPD image upgrade feature is not enabled. The incompatible image will not be automatically upgraded. The card will be disabled until the image is upgraded to a compatible version. |
- |
"Enable the automatic FPD image upgrade with the <CmdBold>upgrade fpd " "auto<NoCmdBold> global configuration command or use the <CmdBold>upgrade " "hw-module<NoCmdBold> privileged EXEC command for a manual upgrade " "operation. For more information about these commands refer to the " FPD_DOCUMENT_NAME "." |
|
FPD_MGMT-4-CFG_NOT_SYNCED |
4-Warning |
Failed to sync \[chars]\ command to standby: [chars] |
A FPD configuration command failed to get synced to standby RP due to the indicated error condition. Usually this can happen if the standby RP hardware doesn't support the type of filesystem supported on the active one. |
spa-infra-fpd |
"Configure again the command with a filesystem that is supported on " "both standby and active RP. To find out if a specific filesystem is " "also supported on standby RP the <CmdBold>dir ?<NoCmdBold> command " "can be used to display a list of filesytem supported on both standby " "and active RP." |
|
FPD_MGMT-4-CFG_NOT_SYNCED |
4-Warning |
Failed to sync \[chars]\ command to standby: [chars] |
A FPD configuration command failed to get synced to standby RP due to the indicated error condition. Usually this can happen if the standby RP hardware doesn't support the type of filesystem supported on the active one. |
- |
"Configure again the command with a filesystem that is supported on " "both standby and active RP. To find out if a specific filesystem is " "also supported on standby RP the <CmdBold>dir ?<NoCmdBold> command " "can be used to display a list of filesytem supported on both standby " "and active RP." |
|
FPD_MGMT-4-UPGRADE_EXIT |
4-Warning |
Unexpected exit of FPD image upgrade operation for [chars] card in [chars]. |
The FPD image upgrade operation was interrupted by the physical removal of the card from the system or by the use of other commands that have interrupted the normal operation of the target card. The partial upgrade operation might have left the card unusable because of corrupted FPD images. |
spa-infra-fpd |
"If the card does not come up after reinserting into the system then " "perform the recovery upgrade operation by using the <CmdBold>upgrade " "hw-module<NoCmdBold> privileged EXEC command. With this command the " "system will attempt the reprogramming of the image to recover from the " "previous partial upgrade operation. For more information about " "performing a recovery upgrade operation refer to the " FPD_DOCUMENT_NAME "." |
|
FPD_MGMT-4-UPGRADE_EXIT |
4-Warning |
Unexpected exit of FPD image upgrade operation for [chars] card in [chars]. |
The FPD image upgrade operation was interrupted by the physical removal of the card from the system or by the use of other commands that have interrupted the normal operation of the target card. The partial upgrade operation might have left the card unusable because of corrupted FPD images. |
- |
"If the card does not come up after reinserting into the system then " "perform the recovery upgrade operation by using the <CmdBold>upgrade " "hw-module<NoCmdBold> privileged EXEC command. With this command the " "system will attempt the reprogramming of the image to recover from the " "previous partial upgrade operation. For more information about " "performing a recovery upgrade operation refer to the " FPD_DOCUMENT_NAME "." |
|
FPD_MGMT-4-VERSION_CHECK_ABORTED |
4-Warning |
FPD image version check operation has been aborted for [chars] card in [chars] because manual upgrade has already being started. |
The FPD image version check operation required for the automatic upgrade feature is not being performed for the indicated card because the <CmdBold>upgrade hw-module<NoCmdBold> privileged EXEC command has already being executed. These two operations cannot be performed at the same time. |
spa-infra-fpd |
"If an automatic upgrade operation is required do not enter the " "<CmdBold>upgrade hw-module<NoCmdBold> privileged EXEC command for the " "manual upgrade while the target card is initializing. Enter the " "<CmdBold>show hw-module subslot fpd<NoCmdBold> command and ensure that " "the target card is displayed in the command output before proceeding " "with the manual upgrade." |
|
FPD_MGMT-4-VERSION_CHECK_ABORTED |
4-Warning |
FPD image version check operation has been aborted for [chars] card in [chars] because manual upgrade has already being started. |
The FPD image version check operation required for the automatic upgrade feature is not being performed for the indicated card because the <CmdBold>upgrade hw-module<NoCmdBold> privileged EXEC command has already being executed. These two operations cannot be performed at the same time. |
- |
"If an automatic upgrade operation is required do not enter the " "<CmdBold>upgrade hw-module<NoCmdBold> privileged EXEC command for the " "manual upgrade while the target card is initializing. Enter the " "<CmdBold>show hw-module subslot fpd<NoCmdBold> command and ensure that " "the target card is displayed in the command output before proceeding " "with the manual upgrade." |
|
FPD_MGMT-5-CARD_POWER_CYCLE |
5-Notice |
[chars] card in [chars] is being power cycled for the FPD image upgrade to take effect. |
The indicated card is being power cycled after the FPD image upgrade. This action allows the target card to be operational with the new upgraded FPD image or images. |
spa-infra-fpd |
LOG_STD_NO_ACTION |
|
FPD_MGMT-5-CARD_POWER_CYCLE |
5-Notice |
[chars] card in [chars] is being power cycled for the FPD image upgrade to take effect. |
The indicated card is being power cycled after the FPD image upgrade. This action allows the target card to be operational with the new upgraded FPD image or images. |
- |
LOG_STD_NO_ACTION |
|
FPD_MGMT-5-POST_UPGRADE_REMINDER |
5-Notice |
[chars] card in [chars] will require a [chars] for the FPD image upgrade to take effect. |
The indicated card will require manual intervention after the FPD image upgrade. The specified operation is required for the upgraded FPD image to take effect. |
spa-infra-fpd |
LOG_STD_NO_ACTION |
|
FPD_MGMT-5-POST_UPGRADE_REMINDER |
5-Notice |
[chars] card in [chars] will require a [chars] for the FPD image upgrade to take effect. |
The indicated card will require manual intervention after the FPD image upgrade. The specified operation is required for the upgraded FPD image to take effect. |
- |
LOG_STD_NO_ACTION |
|
FPD_MGMT-5-POSTPONE_POWER_CYCLE |
5-Notice |
[chars] card in [chars] will be power cycled after bulk sync completion. |
Currently Bulk sync is in Progress. Once the new standby reaches HOT state the indicated card will be power cycled to be operational with the new upgraded FPD image. |
spa-infra-fpd |
LOG_STD_NO_ACTION |
|
FPD_MGMT-5-UPGRADE_ATTEMPT |
5-Notice |
Attempting to automatically upgrade the FPD images for [chars] card |
The automatic FPD image upgrade feature is enabled with the <CmdBold> upgrade fpd auto<NoCmdBold> global configuration command. The system is currently upgrading an incompatible image version automatically. |
spa-infra-fpd |
"No action is required. The upgrade process can take a long time.The " "FPD_MGMT-6-UPGRADE_TIME message gives an estimate of the total " "upgrade time" |
|
FPD_MGMT-5-UPGRADE_ATTEMPT |
5-Notice |
Attempting to automatically upgrade the FPD images for [chars] card |
The automatic FPD image upgrade feature is enabled with the <CmdBold> upgrade fpd auto<NoCmdBold> global configuration command. The system is currently upgrading an incompatible image version automatically. |
- |
"No action is required. The upgrade process can take a long time.The " "FPD_MGMT-6-UPGRADE_TIME message gives an estimate of the total " "upgrade time" |
|
FPD_MGMT-6-BUNDLE_DOWNLOAD |
6-Information |
Downloading FPD image bundle for [chars] card in [chars] ... |
The system is downloading the field programmable device image bundle to the system main memory. |
spa-infra-fpd |
LOG_STD_NO_ACTION |
|
FPD_MGMT-6-BUNDLE_DOWNLOAD |
6-Information |
Downloading FPD image bundle for [chars] card in [chars] ... |
The system is downloading the field programmable device image bundle to the system main memory. |
- |
LOG_STD_NO_ACTION |
|
FPD_MGMT-6-OVERALL_UPGRADE |
6-Information |
All the attempts to upgrade the required FPD images have been completed for [chars] card in [chars]. Number of successful/failure upgrades: |
All the FPD image upgrades have completed for the indicated card. |
spa-infra-fpd |
LOG_STD_NO_ACTION |
|
FPD_MGMT-6-OVERALL_UPGRADE |
6-Information |
All the attempts to upgrade the required FPD images have been completed for [chars] card in [chars]. Number of successful/failure upgrades: |
All the FPD image upgrades have completed for the indicated card. |
- |
LOG_STD_NO_ACTION |
|
FPD_MGMT-6-PENDING_UPGRADE |
6-Information |
[dec] more FPD image upgrade operation will be required on [chars] in [chars] after additional power-cycle operation on the target card. |
All upgrade operations have not completed and additional power-cycle operations are required before the upgraded or new FPD image will be applied to the system configuration. The message text indicates the number of pending upgrade operations that will be performed. More than one power-cycle operation might be required to complete the overall upgrade process. |
spa-infra-fpd |
LOG_STD_NO_ACTION |
|
FPD_MGMT-6-PENDING_UPGRADE |
6-Information |
[dec] more FPD image upgrade operation will be required on [chars] in [chars] after additional power-cycle operation on the target card. |
All upgrade operations have not completed and additional power-cycle operations are required before the upgraded or new FPD image will be applied to the system configuration. The message text indicates the number of pending upgrade operations that will be performed. More than one power-cycle operation might be required to complete the overall upgrade process. |
- |
LOG_STD_NO_ACTION |
|
FPD_MGMT-6-UPGRADE_PASSED |
6-Information |
[chars] FPD ID=[dec] image in the [chars] card in [chars] has been successfully |
The FPD image upgrade process has completed successfully for the indicated device. |
spa-infra-fpd |
LOG_STD_NO_ACTION |
|
FPD_MGMT-6-UPGRADE_PASSED |
6-Information |
[chars] FPD ID=[dec] image in the [chars] card in [chars] has been successfully |
The FPD image upgrade process has completed successfully for the indicated device. |
- |
LOG_STD_NO_ACTION |
|
FPD_MGMT-6-UPGRADE_RETRY |
6-Information |
Attempting to recover from the failed upgrades ... |
Because of an image upgrade failure the system will attempt again the upgrade operation for the same FPD image. |
spa-infra-fpd |
LOG_STD_NO_ACTION |
|
FPD_MGMT-6-UPGRADE_RETRY |
6-Information |
Attempting to recover from the failed upgrades ... |
Because of an image upgrade failure the system will attempt again the upgrade operation for the same FPD image. |
- |
LOG_STD_NO_ACTION |
|
FPD_MGMT-6-UPGRADE_START |
6-Information |
[chars] FPD ID=[dec] image upgrade in progress for [chars] card in [chars]. |
The FPD image upgrade process has started. Do not interrupt the upgrade operation as any interruption could render the target card unusable. Avoid actions like removing the target card from the system powering off the system or using commands that can power-cycle the target card during the upgrade process. |
spa-infra-fpd |
LOG_STD_NO_ACTION |
|
FPD_MGMT-6-UPGRADE_START |
6-Information |
[chars] FPD ID=[dec] image upgrade in progress for [chars] card in [chars]. |
The FPD image upgrade process has started. Do not interrupt the upgrade operation as any interruption could render the target card unusable. Avoid actions like removing the target card from the system powering off the system or using commands that can power-cycle the target card during the upgrade process. |
- |
LOG_STD_NO_ACTION |
|
FPD_MGMT-6-UPGRADE_TIME |
6-Information |
Estimated total FPD image upgrade time for [chars] card in [chars] = %TS. |
The estimated total time for all FPD images to be upgraded is displayed for the indicated card. |
spa-infra-fpd |
LOG_STD_NO_ACTION |
|
FPD_MGMT-6-UPGRADE_TIME |
6-Information |
Estimated total FPD image upgrade time for [chars] card in [chars] = %TS. |
The estimated total time for all FPD images to be upgraded is displayed for the indicated card. |
- |
LOG_STD_NO_ACTION |
|
FR_EEK-5-FAILED |
5-Notice |
Interface [chars] - DLCI [dec] |
The end-to-end keepalive protocol has failed for the indicated PVC. A failure occurs when the DLCI is ACTIVE and end-to-end keepalives are enabled but the number of errors due to timeouts or sequence number mismatches has reached the failure threshold. The DLCI is taken out of operation until the protocol recovers. |
fr |
"A persistent failure may indicate a mismatched end-to-end keepalive " "configuration at each end of the PVC. A transient failure may be due " "to a temporary loss of connectivity or heavy congestion in the network. " "This is a rate-limited log message so not all failures may be logged. " "The <CmdBold>show frame-relay end-to-end keepalive failures<NoCmdBold> " "command can be used to obtain further information on what PVCs have " "experienced failures." |
|
FR_ELMI-3-INCORRECT_ID |
3-Error |
Incorrect ID |
Incorrect ID in QOS parameter message. |
- |
"" |
|
FR_ELMI-3-INCORRECT_IE |
3-Error |
Incorrect IE |
Enhanced LMI is not configured on the interface. The frame was dropped. |
- |
"" |
|
FR_FRAG-3-BADPAK |
3-Error |
Inconsistent packet: size [dec] linktype [chars] input [chars] output [chars] |
A packet being fragmented has inconsistent size and data |
fr |
"Inform Cisco technical support representative" |
|
FR_HA -3-ISSU |
3-Error |
[chars]: [chars] |
A Frame Relay ISSU error occurred. |
fr |
LOG_STD_SH_TECH_ACTION |
|
FR_HA -3-SYNC |
3-Error |
[chars]: code [dec] |
An error occurred when syncing Frame Relay state to the Standby Route Processor. This may affect Non-Stop Forwarding capability on Frame Relay interfaces during and after switchover until the state is recovered through normal protocol operation. |
fr |
"Reset the standby processor to attempt the sync again. " LOG_STD_RECUR_ACTION |
|
FR_LC_XDR-3-PULL_SEND_ERROR |
3-Error |
Error occurred sending FR PVC stats to the RP: error code [dec] |
An error occurred while updating the RP with FR PVC stats.\n\ Some of the FR PVC counters may be inaccurate. |
fr |
"Some FR PVC stats may be lost. This may be a temporary failure.\n\ If ths error message continues to be seen please contact Cisco TAC" |
|
FR_LC_XDR-3-UNIT_SZ_TOO_BIG |
3-Error |
Error occurred sending FR PVC stats to the RP: [chars]: DLCI [dec]: unit sz [dec] |
An error occurred while updating the RP with FR PVC stats.\n\ Some of the FR PVC counters may be inaccurate. |
fr |
"Some FR PVC stats may be lost. This may be a temporary failure.\n\ If ths error message continues to be seen please contact Cisco TAC" |
|
FR_LMI-3-INCORRECT_IE |
3-Error |
Enhanced LMI not configured incorrect IE |
An unexpected LMI information element has been received. |
fr |
"Verify the configuration for enhanced LMI on the switch matches the c onfiguration on the router." |
|
FR_LMI-3-MSG_TOO_BIG |
3-Error |
[chars] [chars] Status message too big status of PVCs with dlci values |
LMI STATUS message size is too big to fit into interface MTU. |
fr |
"LMI type - cisco - does not support segmentation of STATUS message " "so either increase the interface MTU or use LMI types - ansi or " "q933a." |
|
FR_RP_STATS-3-CORRUPT_MSG |
3-Error |
FR IPC stats msg is corrupted: buffer [hec]: length [dec] |
An error occurred while processing a FR IPC stats message. \n\ Some of the FR PVC counters may be inaccurate. |
fr |
"This could be a temporary failure.\n\ But there could be a possibility that some of the FR PVC counters may\n\ not have updated correctly.\n\ If the error message is seen multiple times please inform Cisco \n\ technical support representative." |
|
FR_RP_STATS-3-INVALID_STAT_UNIT |
3-Error |
Error processing FR IPC stats msg: DLCI is out of bounds |
An error occurred while processing a FR IPC stats message.\n\ Some of the FR PVC counters may be inaccurate. |
fr |
"This could be a temporary failure that may or may not affect the\n\ accuracy of PVC stats. If this error message continues to be seen\n\ multiple times please inform Cisco technical support representative." |
|
FR_RP_STATS-3-INVALID_UNIT_COUNT |
3-Error |
FR IPC stats msg is corrupted: unit count [dec] |
An error occurred while processing a FR IPC stats message.\n\ Some of the FR PVC counters may be inaccurate. |
fr |
"This could be a temporary failure.\n\ But there could be a possibility that some of the FR PVC counters may\n\ not have updated correctly.\n\ If the error message is seen multiple times please inform Cisco \n\ technical support representative." |
|
FR_RP_XDR-3-CLIENT_INIT_ERROR |
3-Error |
FR XDR client initialization error: error code [dec] |
An error occurred while registering the FR RP XDR client. \n\ Distributed packet forwarding over FR will not work. |
fr |
"This is a serious error. Without the FR XDR client distributed \n\ packet forwarding over FR will not work. Please inform a Cisco \n\ technical support representative" |
|
FR_RP_XDR-3-INTERFACE_SETUP_ERROR |
3-Error |
Unable to setup FR XDR for interface [chars] |
An error occurred while setting up FR XDR for a FR interface.\n\ This will affect distributed packet forwarding over this interface. |
fr |
"This is a serious error. Without FR XDR support distributed \n\ packet forwarding over the FR interface in question will not work. \n\ Please inform a Cisco technical support representative" |
|
FR_VCB-3-ADJ_SRC_ERROR |
3-Error |
Error sourcing adjacency - vc-bundle [chars] dlci [dec] |
An error occurred while setting up the adj for a member pvc |
fr |
"Try reconfiguring the vc-bundle" |
|
FR_VCB-3-BUMPING |
3-Error |
Bumping error - vcb [chars] - [chars] |
An error occurred while bumping traffic in a vc-bundle |
fr |
"As a workaround reconfigure the vc-bundle to avoid bumping" |
|
FR_VCB-3-CONFIG |
3-Error |
Configuration error - vcb [chars] - [chars] |
An error occurred while interpreting vc-bundle configuration |
fr |
"Try reconfiguring the vc-bundle" |
|
FR_VCB-3-FIBSW_MISSING_TABLE_ENTRY |
3-Error |
FIB switching error - vc-bundle [chars] |
An error occurred while FIB switching packets across vc-bundle |
fr |
"As a workaround delete the vc-bundle and employ a PVC to substitute " "for the vc-bundle" |
|
FR_VCB-3-PROCESS_SWITCHING |
3-Error |
Switching error - vcb [chars] - [chars] |
An error occurred while switching packets across vc-bundle |
fr |
"As a workaround delete the vc-bundle and employ a PVC to substitute " "for the vc-bundle" |
|
FR_VCB-5-UPDOWN |
5-Notice |
FR VC-Bundle [chars] changed state to [chars] |
The state of a frame-relay vc-bundle changed to up/down |
fr |
"Notification message only. No action required" |
|
FR_VIP-3-INCONSISTENT |
3-Error |
Invalid state on VIP: DLCI [dec]: Slot [dec]: Error code [dec] |
An error occurred while processing FR state on the VIP |
fr |
"Shut - no shut the frame-relay encapsulated interface for the" "slot in question" |
|
FR_VIP-3-MISSING_STATE |
3-Error |
Missing state on VIP: DLCI [dec]: Slot [dec] |
An error occurred while preparing an IPC stats unit |
fr |
"Shut - no shut the frame-relay encapsulated interface for the" "slot in question" |
|
FR_VIP-3-SWITCHING |
3-Error |
[chars] DLCI [dec]: [chars] |
An error was detected while switching a packet on the VIP |
fr |
"Shut - no shut of the interface in question or unconfigure then\n\ re-configure may solve the problem. Copy and save the message\n\ and call your technical support representative for assistance" |
|
FR_VIP-5-FLUSH |
5-Notice |
Flushing frame relay state |
Clearing up frame relay state on the VIP card |
fr |
"Notification message only. No action required." |
|
FR-3-BQ_DEQ_ERR |
3-Error |
fr_bq_proc: unknown packet on broadcast queue packet dropped! |
Invalid packet on FR broadcast queue packet dropped! |
fr |
"If the router or some features are not operational due to this" "condition attempt to disable the Frame Relay broadcast queue by " "entering the <CmdBold>no frame-relay broadcast-queue<NoCmdBold>" "command in interface configuration mode for a immediate workaround." "And "LOG_STD_ACTION |
|
FR-3-BQ_DEQ_PTR |
3-Error |
fr_br_proc: hdr-[hec] size-[dec] dlci-%4x %8x %8x |
The Frame Relay broadcast queue contains a datagram that is invalid. The packet has been dropped. |
fr |
"Inform Cisco technical support representative" |
|
FR-3-BQ_ENQ_ERR |
3-Error |
fr_oqueue: Invalid datagramstart [hec] [hec] pak dropped |
A broadcast packet was detected in the Frame Relay output queue that contained an invalid datagram header. The packet has been dropped. |
fr |
"If the router or some features are not operational due to this" "condition attempt to disable the Frame Relay broadcast queue by " "entering the <CmdBold>no frame-relay broadcast-queue<NoCmdBold>" "command in interface configuration mode for a immediate workaround." "And "LOG_STD_ACTION |
|
FR-3-FR_INV_OUTPUT_VECTOR |
3-Error |
An invalid output vector detected on interface [chars] |
An invalid internal function vector is installed on a Frame Relay interface which affects the ability of processing outbound traffic on the device. |
fr |
"Remove and re-apply Frame Relay encapsulation on the interface to " "recover from the error." |
|
FR-3-FR_PVC_STATUS_Q_CREATE_ERROR |
3-Error |
FR PVC status event queue error: failed to create queue |
Unable to create FR PVC status event queue |
fr |
LOG_STD_ACTION |
|
FR-3-FRTSZEROCIR |
3-Error |
FRTS: attempt to configure zero CIR |
It should not be possible to configure a zero CIR. To do so would prevent data transmission on the VC. |
fr |
"Inform Cisco technical support representative" |
|
FR-3-MAP_DELETE_ERROR |
3-Error |
[chars] |
An error occurred while deleting a frame-relay map |
fr |
LOG_STD_ACTION |
|
FR-3-MFR_UNEXPECTEDEVENT |
3-Error |
MFR Timer process error: event table is NULL for event [dec] state [dec] |
The event was ignored because the state transition table is NULL. Normal processing continue. |
fr |
"Please refer to Bug Toolkit on CCO to check for existing bugs. " "If you need further assistance please provide 'show version' and " "'show running' and any configurations that were being done at the " "time the message was seen. Copy the message text exactly as it " "appears on the console or in the system log. Inform Cisco technical " "support representative and provide the representative with the " "gathered information." |
|
FR-3-MLPOFR_ERROR |
3-Error |
MLPoFR not configured properly on Link [chars] Bundle [chars] :[chars] |
The configuration of MLPPP-over-Frame-Relay MLPoFR |
fr |
"Ensure that FRTS has been configured on physical interface and that " "the service policy has been attached to the Virtual Template. To " "verify the configuration use the <CmdBold>show running-config serial " "inteface<noCmdBold> and <CmdBold>show running-config " "virtual-template<noCmdBold> commands." |
|
FR-3-NOMEMORY |
3-Error |
No memory for [chars] |
The requested operation could not be accomplished because of a low memory condition. |
- |
"Reduce other system activity to ease memory demands. If conditions " "warrant upgrade to a larger memory configuration." |
|
FR-3-NULL_PTR_DEREF |
3-Error |
Dereferencing NULL pointer [chars] |
Dereferencing a NULL pointer |
fr |
"Inform Cisco technical support representative" |
|
FR-3-SVC_SETUP |
3-Error |
[chars]: interface [chars]: DLCI [dec] |
An error occurred while attempting to setup a Frame-Relay SVC. There may have been an attempt to setup a SVC using a DLCI thats already in use |
fr |
"Check if the DLCI is already in use. For example: A PVC may be " "configured to use the same DLCI " "use <CmdBold>show frame-relay pvc<CmdBold> to verify. " |
|
FR-4-DLCIDELETE |
4-Warning |
Interface [chars] - DLCI [dec] - PVC use count [dec] |
Trying to remove PVC DLCI while it is still being used. |
fr |
"If this error can be easily recreated enter the " "<CmdBold>debug frame-relay event<NoCmdBold> command and recreate " "the condition that caused this error. " "Copy all the debug messages text and the system message text " "exactly as it appears on the console or in the system log enter " "the show tech-support command contact your Cisco technical support " "representative and provide the representative with the gathered " "information." |
|
FR-4-NNISUBINTF |
4-Warning |
Subinterface not supported on Frame Relay NNI |
Trying to change the state of a subinterface on FR NNI. |
fr |
"Reconfigure the Frame Relay link type or remove the subinterface." |
|
FR-5-CONVERT_ROUTE |
5-Notice |
Converting route pair to connect |
A pair of Frame Relay routes are being converted to connections. |
- |
LOG_STD_NO_ACTION |
|
FR-5-DLCICHANGE |
5-Notice |
Interface [chars] - DLCI [dec] state changed to [chars] |
The state of the Frame Relay PVC specified by the DLCI changed. |
fr |
"Notification message only. No action required." |
|
FRAG_DESC_PROXY-3-PROXY_IPC_FRAG_MEM_EXTEND_FAILED |
3-Error |
- |
Increasing of fragment descriptor pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FRAG_DESC_PROXY-3-PROXY_IPC_FRAG_MEM_INIT_FAILED |
3-Error |
- |
Initialization of fragment descriptor pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FRAG_DESC_PROXY-3-PROXY_IPC_INIT_FAILED |
3-Error |
[dec] |
IPC handler initialization failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FRAG_DESC_PROXY-3-PROXY_IPC_VFR_MEM_EXTEND_FAILED |
3-Error |
- |
Increasing of vFR state pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FRAG_DESC_PROXY-3-PROXY_IPC_VFR_MEM_INIT_FAILED |
3-Error |
- |
Initialization of vFR state pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FRAG_DESC_PROXY-4-PROXY_IPC_INVALID_MSG |
4-Warning |
[hec] |
Invalid IPC message subtype. |
cpp-ucode |
LOG_STD_ACTION |
|
FRAG-2-UNENABLED |
2-Critical |
[chars] feature not enabled at interface [chars] packet cannot be processed |
Reassembly or fragmentation feature as indicated not enabled by the control plane. This is a critical problem. |
qfp |
LOG_STD_ACTION |
|
FRAG-3-FRAG_DESC_MEM_INIT_FAILED |
3-Error |
- |
Failure occurred initializing fragment descriptor pool. |
qfp |
LOG_STD_ACTION |
|
FRAG-3-FRAG_DESC_MEM_REQ_FAILED |
3-Error |
- |
IPC Failure occurred when attempting to request more fragment descriptor pool memory. |
qfp |
LOG_STD_ACTION |
|
FRAG-3-FRAG_STATE_MEM_INIT_FAILED |
3-Error |
- |
Failure occurred initializing fragment state pool. |
qfp |
LOG_STD_ACTION |
|
FRAG-3-FRAG_STATE_MEM_REQ_FAILED |
3-Error |
- |
IPC failure occurred when attempting to request more fragment state pool memory. |
qfp |
LOG_STD_ACTION |
|
FRAG-3-INVALID_MTU |
3-Error |
[chars] feature failed at interface [chars] due to invalid L3 MTU %lu |
Fragmentation was not able to be performed due to invalid adj L3 MTU given by the control plane. |
qfp |
LOG_STD_ACTION |
|
FRAG-3-INVALID_QFP_NO |
3-Error |
Invalid qfp device no.: [chars] |
Invalid qfp device no. |
qfp |
LOG_STD_ACTION |
|
FRAG-3-REASSEMBLY_DBG |
3-Error |
Reassembly/VFR encountered an error: [chars] [chars] %lu [chars] %lu |
Reassembly/VFR encountered a runtime error as indicated in the message with parameter data for debug |
qfp |
LOG_STD_ACTION |
|
FRAG-3-REASSEMBLY_ERR |
3-Error |
Reassembly/VFR encountered an error: [chars] |
Reassembly/VFR encountered a runtime error as indicated |
qfp |
LOG_STD_ACTION |
|
FRATM_RED-3-INTERNAL_CRITICAL |
3-Error |
[chars] |
- |
- |
- |
|
FRATM_RED-3-INTERNAL_ERROR |
3-Error |
[chars] |
- |
- |
- |
|
FRATM-2-INTERNAL_CRITICAL |
2-Critical |
[chars] |
- |
- |
LOG_STD_SH_TECH_ACTION |
|
FRATM-3-CONFIG_ERROR |
3-Error |
[chars] |
- |
- |
LOG_STD_SH_TECH_ACTION |
|
FRATM-3-INTERNAL_ERROR |
3-Error |
[chars] |
- |
- |
LOG_STD_SH_TECH_ACTION |
|
FRATM-4-INTERNAL_WARNING |
4-Warning |
[chars] |
- |
- |
LOG_STD_SH_TECH_ACTION |
|
FRDM336-3-ANYPHYALLOCFAILED |
3-Error |
Anyphy allocation failed for [chars] |
Encountered an error while configuring the ASIC in Linecard. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"'show controller' in Linecard and RP" "'show platform multilink' in Linecard" |
|
FRDM336-3-BUNDLEEXIST |
3-Error |
Unexpected bundle0x[hec] present in freedm |
Encountered an error while provisioning a bundle |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"'show controller' in Linecard and RP" "'show platform multilink' in Linecard" |
|
FRDM336-3-BUNDLERANGE |
3-Error |
bundle0x[hec] not within range |
Encountered an error while configuring an ASIC in Linecard. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"'show controller' in Linecard and RP" "'show platform multilink' in Linecard" |
|
FRDM336-3-CC_RESEQ_FIFO_ACT_NOT_CLEAR |
3-Error |
FRDM336 base addr 0x[hec]: Removing CI0x[hec] of channel |
Encountered an error in the ASIC of line card while unprovisioning a channel or Multilink interface. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"'show controller' " "in Linecard and RP" |
|
FRDM336-3-CIALLOCFAILED |
3-Error |
CI allocation failure for tag=[dec] dlciCos=[dec] |
Encountered an error while configuring an ASIC in Linecard. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"'show controller' in Linecard and RP" "'show platform multilink' in Linecard" |
|
FRDM336-3-CITAGMISMATCH |
3-Error |
CI0x[hec] does not belong to tag0x[hec] |
Encountered an error while configuring an ASIC in Linecard. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"'show controller' in Linecard and RP" "'show platform multilink' in Linecard" |
|
FRDM336-3-DEFAULTCI |
3-Error |
Unexpected default CI for channel 0x[hec] |
Encountered an error while configuring an ASIC in the Linecard. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"'show controller' in Linecard and RP" |
|
FRDM336-3-DLCICOSRANGE |
3-Error |
DLCICOS0x[hec] not within range |
Encountered an error while configuring an ASIC in the Linecard. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"'show controller' in Linecard and RP" |
|
FRDM336-3-EQM_SIZE_NOT_ZERO |
3-Error |
HDLC%04d : %#010x %#010x %#010x %#010x |
Encountered an error while configuring or unconfiguring an ASIC in the Linecard. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"'show controller' in Linecard and RP" |
|
FRDM336-3-INITERR |
3-Error |
FRDM336 chip initialization failed errcode=[dec]: [chars] |
Required resources to initialize the ASIC in Linecard unavailable. This is normally due to hardware issue |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"Reinsert the linecard. If still fails " "swap hardware and LOG_STD_SH_TECH_ACTION" |
|
FRDM336-3-INVALIDANYPHY |
3-Error |
Anyphy0x[hec] number is not in range |
Encountered an error while configuring the ASIC in Linecard. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"'show controller' in Linecard and RP " "'show platform multilink' in Linecard" |
|
FRDM336-3-INVALIDCI |
3-Error |
Either CI0x[hec] range not ok or not allocated |
Encountered an error while configuring an ASIC in Linecard. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"'show controller' in Linecard and RP" "'show platform multilink' in Linecard" |
|
FRDM336-3-LLAPI_PROVERR |
3-Error |
FRDM336 base addr 0x[hec]: Channel provisioning SBI no:[dec] SPE no:[dec] |
Encountered an error while configuring an ASIC in Linecard. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"'show controller' in Linecard and RP" "'show platform multilink' in Linecard" |
|
FRDM336-3-LLINT_DET_TSMSKUSEERR |
3-Error |
FRDM336 base addr 0x[hec]: TS mask in use SBI no:[dec] SPE no:[dec] |
Encountered an error while configuring an ASIC in Linecard. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"'show controller' in Linecard and RP" "'show platform multilink' in Linecard" |
|
FRDM336-3-LLINT_TSMSKUSEERR |
3-Error |
FRDM336 base addr 0x[hec]: TS mask in use SBI no:[dec] SPE no:[dec] |
Encountered an error while configuring an ASIC in Linecard. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"'show controller' in Linecard and RP" "'show platform multilink' in Linecard" |
|
FRDM336-3-NCHUNKSNONZERO |
3-Error |
FRDM336 base addr 0x[hec]: disabling channelHDLC channel no:[dec] |
Encountered an error in the ASIC of line card This mostly occurs while unprovisioning a channel or shuting interface. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"Collect the details that triggered the issue say like any " "config change switchover etc and then" LOG_STD_SH_TECH_ACTION |
|
FRDM336-3-NCHUNKSNONZERO_CC_RESEQ_FIFO_ACT_SET |
3-Error |
FRDM336 base addr 0x[hec]: disabling channelHDLC channel no:[dec] |
Encountered an error in the ASIC of line card This mostly occurs while unprovisioning a channel or shuting interface. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"Collect the details that triggered the issue say like any " "config change switchover etc and then" LOG_STD_SH_TECH_ACTION |
|
FRDM336-3-NOANYPHYALLOCATED |
3-Error |
No Anyphy number for channel=[dec] |
Encountered an error while configuring an ASIC in Linecard. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"'show controller' in Linecard and RP" "'show platform multilink' in Linecard" |
|
FRDM336-3-NOCIALLOCATED |
3-Error |
No CI number for tag=[dec] dlciCos=[dec] |
Encountered an error while configuring an ASIC in Linecard. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"'show controller' in Linecard and RP" "'show platform multilink' in Linecard" |
|
FRDM336-3-PDDBNULL |
3-Error |
Device data block null |
Encountered an error while accessing an ASIC in Linecard |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"'show controller' in Linecard and RP" "'show platform multilink' in Linecard" |
|
FRDM336-3-POLLTO |
3-Error |
FRDM336 indirect poll timeout. base addr:[hex] offset:[hex] value:[hex] mask:[hex] delay:[hex] |
Not able to access a register in the ASIC of Linecard this is normally hardware problem |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
LOG_STD_SH_TECH_ACTION |
|
FRDM336-3-PROVERR |
3-Error |
FRDM336 Channel provisioning SBI no:[dec] SPE no:[dec] TRIB no:[dec] HDLC channel no:[dec] failed errcode=[dec]: [chars] |
Encountered an error while configuring an ASIC in the Linecard. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"'show controller' in " "Linecard and RP" |
|
FRDM336-3-RHDL_TAVAIL_NOT_CLEAR |
3-Error |
FRDM336 base addr 0x[hec]: disabling channelHDLC channel no:[dec] |
Encountered an error while configuring an ASIC in the Linecard. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"Collect the details that triggered the issue say like any " "config change switchover etc and then" LOG_STD_SH_TECH_ACTION |
|
FRDM336-3-SET_CHANPARAM_ERR |
3-Error |
FRDM336 setting parameters of a Channel failed HDLC channel no:[dec] |
- |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"'show controller' in " "Linecard and RP" |
|
FRDM336-3-SET_SPE_ERR |
3-Error |
FRDM336 setting configuration of SPE SBI no:[dec] SPE no:[dec] to [dec] failed |
Encountered an error while configuring an ASIC in the Linecard. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"Collect the details that triggered the issue say like any " "config change switchover etc and then" LOG_STD_SH_TECH_ACTION |
|
FRDM336-3-SET_TRIB_ERR |
3-Error |
FRDM336 setting configuration of tributary SBI no:[dec] SPE no:[dec] TRIB no:[dec] to [dec] failed errcode=[dec]: [chars] |
Encountered an error while configuring an ASIC in the Linecard. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"Collect the details that triggered the issue say like any " "config change switchover etc and then" LOG_STD_SH_TECH_ACTION |
|
FRDM336-3-THDL_AVAIL_NOT_CLEAR |
3-Error |
FRDM336 base addr 0x[hec]: disabling channelHDLC channel no:[dec] |
Encountered an error while configuring an ASIC in the Linecard. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"Collect the details that triggered the issue say like any " "config change switchover etc and then" LOG_STD_SH_TECH_ACTION |
|
FRDM336-3-TRIB_ENAB_DIS_ERR |
3-Error |
FRDM336 [chars] tributary SBI no:[dec] SPE no:[dec] TRIB no:[dec] failed |
Encountered an error while configuring an ASIC in the Linecard. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"Collect the details that triggered the issue say like any " "config change switchover etc and then" LOG_STD_SH_TECH_ACTION |
|
FRDM336-5-NOBUNDLEPRESENT |
5-Notice |
bundle0x[hec] not present in freedm |
Encountered an error while configuring an ASIC in Linecard. |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"'show controller' in Linecard and RP" "'show platform multilink' in Linecard" |
|
FRDM336-6-EQM_ML_INFO |
6-Information |
ML%04d : %#010x %#010x %#010x %#010x |
Multilink information |
osm-ct3 for CT3 osm-choc-ds0 for CHOC-12/DS0 |
"No action is required" |
|
FREEDM-2-FATALEVENT |
2-Critical |
Freedm [chars] fatal event occured: 0x[hec] |
A catastrophic Freedm error occured |
- |
"" |
|
FREEDM-3-BUSYTIMEOUT |
3-Error |
Freedm [chars] busy bit of register 0x[hec] never cleared |
Driver timedout waiting for the Freedm to acknowlege a request |
- |
"" |
|
FREEDM-3-HDLC_ALLOC_FAIL |
3-Error |
Freedm [chars]: Allocation of HDLC controller [dec] for channel [dec] failed |
Allocation of an HDLC controller failed |
- |
"" |
|
FREEDM-3-HDLC_INUSE |
3-Error |
Freedm [chars]: HDLC controller [dec] already in use on channel [dec] |
An attempt was made to use an HDLC controller which was already in use |
- |
"" |
|
FREEDM-3-INITFAIL |
3-Error |
Freedm [chars] initialization failed: [chars] |
Freedm device failed initialization |
- |
"" |
|
FREEDM-3-NOTFREEDM |
3-Error |
Freedm [chars] returned device/vendor of [hex] |
PCI get device id returned an unrecognized value |
- |
"" |
|
FREEDM-3-REG_READ_TIME_OUT |
3-Error |
Busy Out Error of FREEDM [dec] [chars] |
Trying to read FREEDM internal RAM Busy bit is still set for\n\ more than 10 seconds. |
as |
LOG_STD_SH_TECH_ACTION |
|
FRNTEND_CTRLR-1-MGR_TXQ_FULL |
1-Alert |
The front end controller Tx queue reached watermark level |
The queue between microcontroller controlling the front end and IOS has reached the watermark level. Too many messages are pending in the queue |
firmware |
"Please try reloading the switch. If it does not fix the " "problem this could be a bad hardware. Contact the Cisco " "technical support representative" |
|
FRNTEND_CTRLR-1-RELOAD_REQD |
1-Alert |
A UCODE upgrade has taken place without a reload. There must be a reload in order to complete the upgrade. Some features will not work properly until the reload is performed. |
The UCODE images were upgraded during an archive download software upgrade but the switch was not reloaded as part of the upgrade. The switch must be reloaded to complete the upgrade. Until the switch is reloaded PoE thermal power supply and stack-power features will not be completely supported. |
firmware |
"Please reload the switch at the earliest convenience." |
|
FRNTEND_CTRLR-2-SUB_INACTIVE |
2-Critical |
The front end controller [dec] is inactive |
The microcontroller controlling the front end has become inactive. This controls the Port LEDs Uplink LEDs Power over ethernet and thermal/fan control functionality. These functionalities will not work on the ports controlled by this microcontroller. This does not have any impact on data traffic |
hardware |
"Please try a reset of the hardware. If it does not fix the " "problem this could be a bad hardware. Contact the Cisco " "technical support representative" |
|
FRR_OCE-3-ERROR_BFD_SESSION |
3-Error |
[chars]BFD returned [dec] node %p handle %p interface [dec] |
An internal software error occurred. |
OCE_DDTS_COMPONENT |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release." |
|
FRR_OCE-3-GENERAL |
3-Error |
[chars] |
An internal software error occurred. |
OCE_DDTS_COMPONENT |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release." |
|
FRR_OCE-3-INVALID_ADDRTYPE |
3-Error |
addrtype to xdr: [dec] [dec] |
An internal software error occurred. |
OCE_DDTS_COMPONENT |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release." |
|
FRR_OCE-3-INVALID_BFD_EVT |
3-Error |
Error in BFD event retrieval bfd notification handle is %p session handle is %p |
An internal software error occurred. |
OCE_DDTS_COMPONENT |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release." |
|
FRR_OCE-3-INVALID_BFD_HNDL |
3-Error |
[chars] bfd notification handle is %p |
An internal software error occurred. |
OCE_DDTS_COMPONENT |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release." |
|
FRR_OCE-3-INVALID_BFD_SESSION |
3-Error |
BFD session db node mismatch: bfd context db node is %p frr db node is %p |
An internal software error occurred. |
OCE_DDTS_COMPONENT |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release." |
|
FRR_OCE-3-INVALIDPAR |
3-Error |
Parent OCE %p[chars] is [chars] |
An internal software error occurred. |
OCE_DDTS_COMPONENT |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release." |
|
FRR_OCE-3-NULLPOINTER |
3-Error |
[chars] |
An internal software error occurred. |
OCE_DDTS_COMPONENT |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release." |
|
FRR_OCE-4-INVALID_BACKUP_OCE |
4-Warning |
Invalid backup oce is found because interface %lu is removed or reloading |
The interface or line card is reloading or removed. |
OCE_DDTS_COMPONENT |
"Check whether the line card is present and the interface is up." |
|
FRR_OCE-4-NULL_PRIMARY_OCE |
4-Warning |
[chars] |
The interface or line card is reloading or pulled off. |
OCE_DDTS_COMPONENT |
"Check whether the line card is in online and the interface is up." |
|
FRR_OCE-5-ISSULOG |
5-Notice |
FRR is not ISSU compatible notified by [chars] |
MPLS failed to set offset within packet |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
FRR-5-MPLS_TE |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
FRRMGR-3-FRRMGR_INTERNAL_ERR |
3-Error |
[chars] |
FRRMGR_INT_ERR_EXPLANATION |
ribinfra |
LOG_STD_RECUR_ACTION |
|
FS_IPHC-2-LC_IPHC_SETUP_FAIL |
2-Critical |
Failed to initialise or allocate memory for IP Compression database. |
IP Compression main database not created due to lack of memory resources.\n\ |
iphc |
"The Line Card cannot allocate memory for an IP Compression database.\n\ Add more memory if possible to the VIP. \n\ Free up memory on the VIP by reducing features used or " "buffer allocations.\n\ Reduce the number of contexts configured on all interfaces on\n\ the affected line card using the interface configuration \n\ <CmdBold>ip rtp compression-connections<NoCmdBold>" |
|
FS_IPHC-2-LC_PROC_INIT |
2-Critical |
LC Failed to initialise distributed IP Hdr Comp Process |
IP Compression Process not created on Line Card. |
iphc |
"A possible reason for a process failing to start is lack of resources.\n\ Check memory allocation on line card and either upgrade line card memory\n\ or reduce feature burden in it's interface configurations." |
|
FS_IPHC-2-RP_NOLCINFO |
2-Critical |
Unable to malloc state table for LC |
An internal data structure is missing due to lack of memory resources. |
iphc |
"The Route Processor is dangerously low on memory resources. Free up \n\ memory by removing unwanted feature configuration or upgrade the memory\n\ on the system router processor" |
|
FS_IPHC-3-LC_INVALID_MSG |
3-Error |
Received IPC message of unknown type |
IP compression on Line Card has received an unknown message from Route\n\ Processor. |
iphc |
"If this message occurs regularly copy the error message exactly as it\n\ appears and report it to your technical support representative." |
|
FS_IPHC-3-MSG_TOO_LARGE |
3-Error |
Received IPC message too large to handle [dec] |
IP compression has received an IPC message of a size larger than expected.\n\ |
iphc |
"If this message occurs regularly copy the error message exactly as it\n\ appears and report it to your technical support representative." |
|
FS_IPHC-4-IPC_NO_CHUNK |
4-Warning |
IPC Chunk pool empty slot [dec] VIP junked RSP msg |
IP compression private memory pool for IPC messages exhausted. |
iphc |
"If this message occurs regularly copy the error message exactly as it\n\ appears and report it to your technical support representative." |
|
FS_IPHC-4-LC_IPCSENDFAIL |
4-Warning |
LC unable to send IPHC msg to RP [dec] |
Line card was unable to send an IP header compression \n\ information message to the route processor. |
iphc |
"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 <CmdBold>debug ip rtp head<NoCmdBold> and <CmdBold>debug ip tcp head<NoCmdBold>\n\ commands for the period during which this message appeared." |
|
FS_IPHC-4-LC_NOIPCBUFFER |
4-Warning |
Unable to malloc IPC msg buffer [dec] on line card |
Line card unable to send IPHC information to Route Processor due to lack\n\ of memory in it's private memory pool. |
iphc |
"If this message occurs regularly copy the error message exactly as it\n\ appears and report it to your technical support representative." |
|
FS_IPHC-4-RP_IPCSENDFAIL |
4-Warning |
RP unable to send IPHC msg to LC [dec] |
Route processor was unable to send an IP header compression \n\ configuration message to a line card interface. |
iphc |
"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 <CmdBold>debug ip rtp head<NoCmdBold> and <CmdBold>debug ip tcp head<NoCmdBold>\n\ commands for the period during which this message appeared." |
|
FS_IPHC-4-RP_NOIPCBUFFER |
4-Warning |
Unable to malloc IPC msg buffer [dec] on RP |
Route Processor unable to send IPHC information to Line Card due to lack\n\ of memory in it's private memory pool. |
iphc |
"If this message occurs regularly copy the error message exactly as it\n\ appears and report it to your technical support representative." |
|
FTC_TRUNK-1-NOMEMORY |
1-Alert |
msgtxt_nomemory |
The MPC860/PowerQUICC CPU was unable to access the memory it needs to carry out its functions. Here are some possible causes. The network is large requiring a lot of memory for routing tables and so on. The router configuration has many features enabled each of which require a certain amount of memory. A software error memory leak exists. |
- |
"Reduce system activity to ease the memory demand or upgrade to a larger memory configuration." |
|
FTC_TRUNK-1-RELOAD |
1-Alert |
Must reload to config Interface [chars] as ftc-trunk again |
If the operator first configures an interface to 'encapsulation ftc-trunk' then re-configures it later to some other encapsulation such as HDLC then attempts to re-configure it again to 'encap ftc-trunk' then this error messages is displayed to notify the operator that the 'reload' command must be entered first before attempting to configure the interface to 'encap ftc-trunk' again. |
- |
"Issue the 'reload' command." |
|
FTC_TRUNK-3-CID_IN_USE |
3-Error |
[chars] connection-id [dec] is busy try other cid |
When setting up a new session-trunk if the operator attempts to use a connection-ID that is already assigned and in-use then the error message is displayed to indicate that the selected connection-id cannot be used for this session-trunk. |
- |
"Try again with a connection-ID which is not already in use." |
|
FTC_TRUNK-3-TOOMANY |
3-Error |
Cannot config more than [dec] ftc-trunks |
When the operator enters the 'encap ftc-trunk' configuration command if there are already 4 interfaces configured for encap ftc-trunk this message is displayed to indicate that no more can be configured. |
- |
"Free one of the other interfaces first or if conditions warrant upgrade to a larger configuration with more interfaces." |
|
FTC_TRUNK-3-TOOMANY_SESSION |
3-Error |
Cannot config more than [dec] session-trunks |
When the operator enters the 'encap ftc-trunk' configuration command if there are already 4 interfaces configured for encap ftc-trunk then the message is displayed to indicate that no more can be configured. |
- |
"Free one of the existing interfaces before trying again or if conditions warrant upgrade to a larger configuration." |
|
FTP_ALG-3-BAD_L7_DATA |
3-Error |
- |
Receive Bad L7 data from either FW or NAT. |
cpp-ucode |
LOG_STD_ACTION |
|
FTP_ALG-3-CHUNK_CREATE_FAIL |
3-Error |
- |
Chunk create failed. FTP ALG will not be able to finish initialization. |
cpp-ucode |
LOG_STD_ACTION |
|
FTP_ALG-3-INCOMPATIBLE_HA_MSG_LEN |
3-Error |
rcvd:[hec] expect:[hec] |
Incompatible HA Message Length. FTP ALG will reject sync data. |
cpp-ucode |
LOG_STD_ACTION |
|
FTP_ALG-3-INCOMPATIBLE_HA_VERSION |
3-Error |
rcvd:[hec] expect:[hec] |
Incompatible HA Version. FTP ALG will reject sync data. |
cpp-ucode |
LOG_STD_ACTION |
|
FTP_ALG-3-INCORRECT_HA_MAGIC |
3-Error |
rcvd:[hec] expect:[hec] |
Incorrect HA MAGIC. FTP ALG will reject sync data. |
cpp-ucode |
LOG_STD_ACTION |
|
FTP_ALG-3-INVALID_HA_OPCODE |
3-Error |
rcvd:[hec] expect:[hec] |
Invalid HA opcode. FTP ALG will reject sync data. |
cpp-ucode |
LOG_STD_ACTION |
|
FTP_ALG-3-L7_DATA_CREATE_ERROR |
3-Error |
- |
Error during L7 data creation. |
cpp-ucode |
LOG_STD_ACTION |
|
FTP_ALG-3-WRITEBACK_ERROR |
3-Error |
- |
Error during writeback. |
cpp-ucode |
LOG_STD_ACTION |
|
FTP64_ALG-3-BAD_L7_DATA |
3-Error |
- |
Receive Bad L7 data from either FW or NAT. |
cpp-ucode |
LOG_STD_ACTION |
|
FTP64_ALG-3-CHUNK_CREATE_FAIL |
3-Error |
- |
Chunk create failed. FTP64 ALG will not be able to finish initialization. |
cpp-ucode |
LOG_STD_ACTION |
|
FTP64_ALG-3-INCOMPATIBLE_HA_MSG_LEN |
3-Error |
rcvd:[hec] expect:[hec] |
Incompatible HA Message Length. FTP64 ALG will reject sync data. |
cpp-ucode |
LOG_STD_ACTION |
|
FTP64_ALG-3-INCOMPATIBLE_HA_VERSION |
3-Error |
rcvd:[hec] expect:[hec] |
Incompatible HA Version. FTP64 ALG will reject sync data. |
cpp-ucode |
LOG_STD_ACTION |
|
FTP64_ALG-3-INCORRECT_HA_MAGIC |
3-Error |
rcvd:[hec] expect:[hec] |
Incorrect HA MAGIC. FTP64 ALG will reject sync data. |
cpp-ucode |
LOG_STD_ACTION |
|
FTP64_ALG-3-INVALID_HA_OPCODE |
3-Error |
rcvd:[hec] expect:[hec] |
Invalid HA opcode. FTP64 ALG will reject sync data. |
cpp-ucode |
LOG_STD_ACTION |
|
FTP64_ALG-3-L7_DATA_CREATE_ERROR |
3-Error |
- |
Error during L7 data creation. |
cpp-ucode |
LOG_STD_ACTION |
|
FTPSE-3-MSG_ERR |
3-Error |
[chars] |
Error Messages |
pagent |
"try debug command" |
|
FTPSE-6-MSG_INF |
6-Information |
[chars] |
Program information |
- |
- |
|
FTPSE-6-NETWRTFAILED |
6-Information |
FTPSE Server:connection / tcp_write failed. |
A TCP write failed while sending an FTP command reply to the client. |
- |
"Verify network connection from client to server and verify ftp client operation." |
|
FTPSE-7-MSG_DBG |
7-Debug |
[chars] |
Debug Messages |
- |
- |
|
FTPSERVER-4-XFER_WARNING |
4-Warning |
File may not have transferred correctly |
Extra linefeeds were received in ASCII mode |
- |
- |
|
FTPSERVER-6-CONNCLOSED |
6-Information |
Connection closed after [dec] seconds. '[chars]' |
The FTP connection to a client was closed after 5 minutes inactivity. |
- |
"Client inactivity will cause the server to shutdown the connection." |
|
FTPSERVER-6-CWDFAILED |
6-Information |
setcwd failed [chars]. |
FTP client request failed to change to requested directory. |
- |
"Verify correct path for desired directory." |
|
FTPSERVER-6-NETRDFAILED |
6-Information |
FTP control connection / tcp_read failed. |
An error occured reading the command line from the ftp client. |
- |
"Verify network connection from client to server and verify ftp client operation." |
|
FTPSERVER-6-NETWRTFAILED |
6-Information |
FTP Server:connection / tcp_write failed. |
A TCP write failed while sending an FTP command reply to the client. |
- |
"Verify network connection from client to server and verify ftp client operation." |
|
FTPSERVER-6-NEWCONN |
6-Information |
FTP Server - new connection made. |
An new ftp server connection has opened. |
- |
"FTP Server connections can be disabled by config 'no ftp-server enable'." |
|
FTPSERVER-6-REPLYLOGN |
6-Information |
REPLY [dec] |
This is an informational message only.\n\ An FTP login has occurred. |
- |
"Informational messages can be disabled by changing logging level." |
|
FTPSERVER-6-REPLYLOGTEXT |
6-Information |
[dec][chars] |
This is an informational message only.\n\ This text was sent to the FTP client. |
- |
"Informational messages can be disabled by changing logging level." |
|
FTPSERVER-6-TOPDIRTEST |
6-Information |
Input path failed Top-dir[chars] test. |
An operation attempted to use a path not within the tree under the ftp-server topdir config parameter. |
- |
"Re-configure the server 'topdir' parameter or select another path." |
|
FTSP-1-NOMEMORY |
1-Alert |
msgtxt_nomemory |
The requested operation could not be accomplished because of a low\n\ memory condition. |
- |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
FTSP-2-INTERNAL_ERROR |
2-Critical |
Internal software error. [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
FTSP-4-FMAIL_FAILED_AUTHENTICATION |
4-Warning |
Authentication for > [chars] < failed\n |
Authenticating the specified user failed |
- |
LOG_STD_RECUR_ACTION |
|
FTSP-4-FMAIL_NO_ACCOUNTING |
4-Warning |
FAXMAIL- Accounting\n\for tty[dec] failed |
Accounting failed for the specified tty. |
- |
LOG_STD_RECUR_ACTION |
|
FTSP-4-HARDWARE_ERROR |
4-Warning |
tty [dec] |
A hardware interface was not configured when a fax call was\n\ answered or attempted. |
- |
LOG_STD_RECUR_ACTION |
|
FTSP-4-UNEXPECTEDEVENT |
4-Warning |
Bad event received\n\[dec] [dec] |
An unexpected event was received. |
- |
LOG_STD_RECUR_ACTION |
|
FTSP-6-FAX_CONNECT |
6-Information |
[chars] |
Fax carrier detected |
- |
LOG_STD_NO_ACTION |
|
FTSP-6-FAX_DISCONNECT |
6-Information |
[chars] |
Fax call disconnected |
- |
LOG_STD_NO_ACTION |
|
FTTM-3-ERROR |
3-Error |
[chars] |
Full Ternary TCAM Manager Error |
- |
LOG_STD_SH_TECH_ACTION |
|
FW_HA-3-CF_REG_FAILED |
3-Error |
Firewall High availability registration to CF failed |
Firewall High Availability could not register as a Checkpoint Facility\n\ client |
ios-firewall |
"Firewall HA subsys registration as Checkpoint Facility client failed \n\ verify if this image is capable of doing Box-Box redundancy. \n\ Collect the image version information and report the probelm to\n\ Cisco Technical assistance centre" |
|
FW_HA-3-RF_REG_FAILED |
3-Error |
Firewall High availability registration to RF failed |
Firewall High Availability could not register as a Redundancy Facility\n\ client |
ios-firewall |
"Firewall HA subsys registration as Redundancy Facility client failed \n\ verify if this image is capable of doing Box-Box redundancy. \n\ Collect the image version information and report the probelm to\n\ Cisco Technical assistance centre" |
|
FW_HA-3-SUBSYS_INIT_FAILED |
3-Error |
Firewall High availability subsystem initialization failed |
Firewall High Availability subsystem initialization failed |
ios-firewall |
"Firewall HA subsystem initialization failed under unsual circumstances \n\ Check the available memory and CPU utilization on the router and verify \n\ that it satisfies the requirements for the feature \n\ If the requirement are satisfied collect the output of show tac and \n\ report it to Cisco Technical assistance centre." |
|
FW_HA-3-TW_INIT_FAILED |
3-Error |
Firewall High availability update timer initialization failed |
Firewall High Availability update timer initialization failed |
ios-firewall |
"Firewall HA update timer initialization failed under unsual circumstances \n\ Check the available memory and CPU utilization on the router and verify \n\ that it satisfies the requirements for the feature \n\ If the requirement are satisfied collect the output of show tac and \n\ report it to Cisco Technical assistance centre." |
|
FW_HA-6-AUDIT_TRAIL_STDBY_START |
6-Information |
[chars]Start [chars] standby session: initiator [inet]:[dec] -- responder [inet]:[dec] |
This message documents the opening of an inspection session on \n\ standby router. The message is issued at the start of each\n\ inspected session and it records the source/destination\n\ addresses and ports. |
ios-firewall |
"This message is for informational purposed only and can be used\n\ to collect the basic accounting for inspected sessions." |
|
FW_HA-6-AUDIT_TRAIL_STDBY_STOP |
6-Information |
[chars]Stop [chars] standby session: initiator [inet]:[dec] -- responder [inet]:[dec] |
This message documents the deletion of an inspection session on\n\ standby router. The message is issued at the end of each\n\ inspected session and it records the source/destination\n\ addresses and ports. |
ios-firewall |
"This message is for informational purposed only and can be used\n\ to collect the basic accounting for inspected sessions." |
|
FW_HA-6-AUDIT_TRAIL_STDBY_TO_ACT |
6-Information |
Sessions matching HSRP group [chars] are being transitioned from Standby to Active state |
This message documents sessions on standby router that\n\ match this hsrp group name are changed to active. The message\n\ is issued when the standby router becomes active |
ios-firewall |
"This message is for informational purposed only and can be used\n\ to collect the basic accounting for inspected sessions." |
|
FW_HA-6-NO_HSRP_GNAME_ON_STDBY |
6-Information |
Firewall High availability - Inpsect redundancy group is not configured on standby for interface [chars] dir in/out |
NO hsrp group name on standby is configured on same interface and\n\ inspect dir configured on active |
ios-firewall |
"Please check firewall configuration on standby and make sure it \n\ is same with active's configuration" |
|
FW_HA-6-NO_INSPECT_RULE_ON_STDBY |
6-Information |
Firewall High availability - inspect rule is not configured on standby for interface [chars] dir in/out |
NO inspect rule on standby is configured on same interface and inspect\n\ dir configured on active |
ios-firewall |
"Please check firewall configuration on standby and make sure it should \n\ be same with active's configuration" |
|
FW_HA-6-PROT_MISMATCH |
6-Information |
Firewall High availability - L4/L7 protocol mismatch between active and standby |
Firewall High Availability configuration of inspect rule or hsrp group \n\ name does not match between the Active and Standby devices |
ios-firewall |
"Firewall High Availability configuration between the Active and Standby\n\ devices are not automatically synched. Check to see if the configuration\n\ of the Active and Standby are in synch. Check the configuration guidelines\n\ for all areas that should match." |
|
FW-2-BLOCK_HOST |
2-Critical |
[chars]Blocking new TCP connections to host [inet] for [dec] minute[chars] half-open count [dec] exceeded. |
This message indicates that any subsequent new TCP connection \n\ attempts to the specified host will be denied because the \n\ max-incomplete host threshold of half-open TCP connections is \n\ exceeded and the blocking option is configured to block the \n\ subsequent new connections. The blocking will be removed when the \n\ configured block-time expires. |
firewall |
"This message is for informational purposes only but may indicate \n\ that a SYN flood attack was attempted." |
|
FW-2-BLOCK_HOST |
2-Critical |
target:class-[chars]:[chars]:Blocking new TCP connections to host [inet] for [dec] minute[chars] half-open count [dec] exceeded. [chars] |
This message indicates that any subsequent new TCP connection \n attempts to the specified host will be denied because the \n max-incomplete host threshold of half-open TCP connections is \n exceeded and the blocking option is configured to block the \n subsequent new connections. The blocking will be removed when the \n configured block-time expires. |
cpp-ucode |
"This message is for informational purposes only but may indicate \n"" that a SYN flood attack was attempted." |
|
FW-3-FTP_NON_MATCHING_IP_ADDR |
3-Error |
[chars]Non-matching address [inet] used in [chars] -- FTP client [inet] FTP server [inet] |
An FTP client attempted to use a PORT command or the FTP server \n\ attempted to use the response to a PASV command to trick the \n\ firewall into opening access to a third-party host that is \n\ different from the two hosts engaged in the FTP connection. \n\ This message indicates that a suspicious violation was detected \n\ while attempting to modify the security policy in the firewall. \n\ The command is rejected and the connection is reset by the \n\ firewall. |
firewall |
"This message is for informational purposes only but may indicate \n\ that an attempt was made to grant or open access to unauthorized \n\ hosts." |
|
FW-3-FTP_PRIV_PORT |
3-Error |
[chars]Privileged port [dec] used in [chars] -- FTP client [inet] FTP server [inet] |
An FTP client attempted to use a PORT command or the FTP server \n\ attempted to use the response to a PASV command to trick the \n\ firewall into opening access to a privileged port. This message \n\ indicates that a suspicious violation was detected from the FTP \n\ client/server attempting to modify the security policy in the \n\ firewall. The command is rejected and the connection is reset by \n\ the firewall. |
firewall |
"This message is for informational purposes only but may indicate that an attempt was made to gain access to privileged ports." |
|
FW-3-FTP_SESSION_NOT_AUTHENTICATED |
3-Error |
[chars]Command issued before the session is authenticated -- FTP client [inet] FTP server [inet] |
An FTP client attempted to use the PORT command or an FTP server \n\ attempted to use the response to a PASV command to open a data \n\ channel in the firewall prior to the client's successful \n\ authentication with the server. This is a suspicious attempt by \n\ the client/server to trick the firewall into opening a hole \n\ so that outside attackers can take advantage of the firewall \n\ opening. This message indicates that a suspicious violation was \n\ detected and the PORT or PASV command/response is rejected \n\ by the firewall. The data channel in the firewall will not be \n\ opened until the authentication is done successfully. |
firewall |
"This message is for informational purposes only but may indicate \n\ that an illegal attempt was made to modify the firewall security \n\ policy." |
|
FW-3-HTTP_JAVA_BLOCK |
3-Error |
[chars]JAVA applet is blocked from [inet]:[dec] to [inet]:[dec]. |
A Java applet was seen in the HTTP channel and the firewall \n\ configuration indicates that the applet from this Web site should \n\ be prohibited. The message indicates that the applet is being \n\ downloaded from one of the prohibited sites and its entrance to \n\ the protected network is not allowed. The connection is reset and \n\ the transmission of the detected applet is aborted immediately. |
firewall |
"This message is for informational purposes only but may indicate a security problem." |
|
FW-3-INTERNAL_ERROR |
3-Error |
IP Firewall internal failure -- [chars] |
This message indicates the misc errors in the IP FW subsystem |
firewall |
"This message indicates the misc errors in the IP FW subsystem" |
|
FW-3-NOTFOUND |
3-Error |
[chars]Session context for [inet]:[dec] => [inet]:[dec] not found. |
The CBAC code was searching its database for information for a \n\ particular inspection session but this information was not found. |
firewall |
"If this message recurs copy it down exactly as it appears and \n\ contact your technical support representative for assistance." |
|
FW-3-RESPONDER_WND_SCALE_INI_NO_SCALE |
3-Error |
Dropping packet - Invalid Window Scale option for session [inet]:[dec] to [inet]:[dec] Initiator scale [dec] Responder scale [dec] |
Firewall detected the packet from Responder to Initiator \n\ has windows scaling option but did not have the scaling \n\ option in the SYN packet from Initiator to responder. \n\ This is an error according to RFC 1323 |
firewall |
"Turn on window scaling option on both Initiator" " and Responderor Turn off window scaling on the" " Responder" |
|
FW-3-SMTP_INVALID_COMMAND |
3-Error |
[chars]Invalid SMTP command [chars]total [dec] chars from initiator [inet]:[dec] |
The CBAC code detected an invalid SMTP command in the inspected \n\ SMTP connection. This message indicates that a suspicious violation \n\ was detetected that may be an attack to the mail server system. \n\ The command is rejected and the connection is reset by the firewall \n\ immediately. |
firewall |
"This message is for informational purposes only but may indicate\n\ a security problem." |
|
FW-3-TIMER_WHEEL_INIT_FAILED |
3-Error |
Timer Wheel initialization failed |
This message indicates that Timer Wheel initialization is\n\ failed in the FW subsystem |
- |
"This message indicates a series problem with IOS Firewall. \n\ On seeing this error message copy the message exactly as \n\ it appears and report it to your technical support \n\ representative." |
|
FW-4-AGG_AGE_PERIOD_OFF |
4-Warning |
[chars] session count has dipped below the aggressive aging low watermark [dec] [chars] |
The number of per-box half-open or total sessions has gone \n below the aggressive aging low threshold. This message indicates \n end of aggressive aging period. |
cpp-ucode |
"This message is for informational purposed only but may indicate \n"" a security problem." |
|
FW-4-AGG_AGE_PERIOD_ON |
4-Warning |
[chars] session count has exceeded the aggressive aging high watermark [dec] [chars] |
Start aggressive aging period. The aggressive aging high threshold \n of per-box halfopen or total sessions has been exceeded. \n This message indicates that a DOS attack may be in progress hence \n aggressive aging feature will take affect. The feature protects \n the firewall sessions resources by allowing idle sessions to be \n exist for a shorter period of time. |
cpp-ucode |
"This message is for informational purposed only but may indicate \n"" a security problem." |
|
FW-4-ALERT_OFF |
4-Warning |
[chars][chars] count [dec]/[dec] current 1-min rate: [dec] |
Either the number of half-open connections or the new connection \n\ initiation rate has gone below the max-incomplete low threshold. \n\ This message indicates that the rate of incoming new connections \n\ has slowed down and is issued only when the max-incomplete low \n\ threshold is crossed. |
firewall |
"This message is for informational purposed only but may indicate \n\ that an attack has stopped." |
|
FW-4-ALERT_OFF |
4-Warning |
target:class-[chars]:[chars]:[chars] count [dec]/[dec] current rate: [dec] [chars] |
Either the number of half-open connections or the new connection \n initiation rate has gone below the max-incomplete low threshold. \n This message indicates that the rate of incoming new connections \n has slowed down and is issued only when the max-incomplete low \n threshold is crossed. |
cpp-ucode |
"This message is for informational purposed only but may indicate \n"" that an attack has stopped." |
|
FW-4-ALERT_ON |
4-Warning |
[chars][chars] count [dec]/[dec] current 1-min rate: [dec] |
Either the max-incomplete high threshold of half-open connections \n\ or the new connection initiation rate has been exceeded. This error \n\ message indicates that an unusually high rate of new connections is \n\ coming through the firewall and a DOS attack may be in progress. \n\ This message is issued only when the max-incomplete high threshold \n\ is crossed. |
firewall |
"This message is for informational purposed only but may indicate \n\ a security problem." |
|
FW-4-ALERT_ON |
4-Warning |
target:class-[chars]:[chars]:[chars] count [dec]/[dec] current rate: [dec] [chars] |
Either the max-incomplete high threshold of half-open connections \n or the new connection initiation rate has been exceeded. This error \n message indicates that an unusually high rate of new connections is \n coming through the firewall and a DOS attack may be in progress. \n This message is issued only when the max-incomplete high threshold \n is crossed. |
cpp-ucode |
"This message is for informational purposed only but may indicate \n"" a security problem." |
|
FW-4-HALFOPEN_LIMIT_EXCEEDED |
4-Warning |
[chars] half open session limit exceeded. configured limit [dec] |
The halfopen session limit of a specific layer 4 protocol or the total \n halfopen session limit exceeded. \n This error message indicates that an unusually high rate of new \n connections is coming through the firewall and a DOS attack may be in \n progress. \n This message is issued only when the max-incomplete high threshold \n is crossed. |
cpp-ucode |
"This message is for informational purposed only but may indicate \n"" a security problem." |
|
FW-4-HOST_TCP_ALERT_ON |
4-Warning |
[chars]Max tcp half-open connections [dec] exceeded for host [inet]. |
The max-incomplete host limit of half-open TCP connections has been \n\ exceeded. This message indicates that a high number of half-open \n\ connections is coming to the protected server and may indicate \n\ that a SYN flood attack is in progress and is targeted to the \n\ specified server host. |
firewall |
"This message is for informational purposes only but may indicate \n\ that a SYN flood attack was attempted. If this alert is issued \n\ frequently and identified to be mostly false alarms then the \n\ max-incomplete host threshold value is probably set too low \n\ and there is a lot of legitimate traffic coming in to that server. \n\ In this case the max-incomplete host parameter should be set to \n\ a higher number to avoid false alarms." |
|
FW-4-HOST_TCP_ALERT_ON |
4-Warning |
target:class-[chars]:[chars]:Max tcp half-open connections [dec] exceeded for host [inet][chars]. [chars] |
- |
- |
- |
|
FW-4-SESSION_THRESHOLD_EXCEEDED |
4-Warning |
[chars]Number of sessions for the firewall rule '[chars]' applied on interface '[chars]' exceeds the configured threshold [dec] |
This message indicates that the number of established CBAC\n\ sessions have crossed the configured threshold. |
firewall |
"This message is for informational purpose only but may indicate\n\ a security problem. This might also mean that the session threshold\n\ is set to a low value in which case the threshold value could be\n\ increased through CLI command" |
|
FW-4-SESSIONS_MAXIMUM |
4-Warning |
Number of sessions for the firewall policy on target:class-[chars]:[chars] exceeds |
This message indicates that the number of established ZBF\n sessions have crossed the configured sessions maximum limit |
cpp-ucode |
"This message is for informational purpose only but may indicate\n"" a security problem. This might also mean that the sessions maximum \n"" is set to a low value in which case the sessions maximum value could be\n"" increased through paramter-map type inspect CLI" |
|
FW-4-TCP_MAJORDOMO_EXEC_BUG |
4-Warning |
[chars]Majordomo Execute Attack - from [inet] to [inet] |
A bug in the Majordomo program will allow remote users to\n\ execute arbitrary commands at the privilege level of the\n\ server. |
firewall |
"For security reasons users should not \n\be allowed to execute programs via e-mail servers. This is a very \n\serious indication that your network may be under attack and the \n\source should be shunned immediately." |
|
FW-4-TCP_SENDMAIL_BAD_FROM_SIG |
4-Warning |
[chars]Sendmail Invalid Sender - from [inet] to [inet] |
- |
firewall |
"For security reasons users should not \n\be allowed to execute programs via e-mail servers. This is a very \n\serious indication that your network may be under attack and the \n\source should be shunned immediately." |
|
FW-4-TCP_SENDMAIL_BAD_TO_SIG |
4-Warning |
[chars]Sendmail Invalid Recipient - from [inet] to [inet] |
- |
firewall |
"For security reasons users should not \n\be allowed to execute programs via e-mail servers. This is a very \n\serious indication that your network may be under attack and the \n\source should be shunned immediately." |
|
FW-4-TCP_SENDMAIL_DECODE |
4-Warning |
[chars]Sendmail Decode Alias - from [inet] to [inet] |
Triggers on any mail message with '': decode@'' in the header.\n\ The decode alias is used to uudecode files and is primarily\n\ implemented as a convenience for system administration. |
firewall |
"For security reasons users should not \n\be allowed to execute programs via e-mail servers. This is a very \n\serious indication that your network may be under attack and the \n\source should be shunned immediately." |
|
FW-4-TCP_SENDMAIL_INVALID_COMMAND |
4-Warning |
[chars]Invalid SMTP command - [inet] to [inet] |
Triggers on an invalid SMTP command in the \n\ SMTP connection. This message indicates that a suspicious violation \n\ was detetected that may be an attack to the mail server system. |
firewall |
"This is unusual traffic and may warrant\n\investigation." |
|
FW-4-TCP_SENDMAIL_OLD_SIG |
4-Warning |
[chars]Archaic Sendmail Attacks - from [inet] to [inet] |
Triggers when ''wiz'' or ''debug'' commands are sent to the SMTP port. |
firewall |
"For security reasons users should not \n\be allowed to execute programs via e-mail servers. This is a very \n\serious indication that your network may be under attack and the \n\source should be shunned immediately." |
|
FW-4-UNBLOCK_HOST |
4-Warning |
[chars]New TCP connections to host [inet] no longer blocked |
New TCP connection attempts to the specified host are no longer \n\ blocked. This message indicates that the blocking of new TCP \n\ attempts to the specified host has been lifted. |
firewall |
"This message is for informational purposed only but may indicate \n\ a SYN flood attack was attempted to the host." |
|
FW-4-UNBLOCK_HOST |
4-Warning |
target:class-[chars]:[chars]:New TCP connections to host [inet][chars] no longer blocked [chars] |
New TCP connection attempts to the specified host are no longer \n blocked. This message indicates that the blocking of new TCP \n attempts to the specified host has been lifted. |
cpp-ucode |
"This message is for informational purposed only but may indicate \n"" a SYN flood attack was attempted to the host." |
|
FW-4-VRF_AGG_AGE_PERIOD_OFF |
4-Warning |
[chars] session count of VRF id [dec] has dipped below the aggressive aging low watermark [dec] [chars] |
The number of VRF half-open or total sessions has gone \n below the aggressive aging low threshold. This message indicates \n end of aggressive aging period. |
cpp-ucode |
"This message is for informational purposed only but may indicate \n"" a security problem." |
|
FW-4-VRF_AGG_AGE_PERIOD_ON |
4-Warning |
[chars] session count of VRF id [dec] has exceeded the aggressive aging high watermark [dec] [chars] |
Start aggressive aging period for VRF. The aggressive aging high \n threshold of VRF halfopen or total sessions has been exceeded. \n This message indicates that a DOS attack may be in progress hence \n aggressive aging feature will take affect. The feature protects \n the firewall sessions resources by allowing idle sessions to be \n exist for a shorter period of time. |
cpp-ucode |
"This message is for informational purposed only but may indicate \n"" a security problem." |
|
FW-4-VRF_HALFOPEN_LIMIT_EXCEEDED |
4-Warning |
VRF id [dec] [chars] half open session limit exceeded. configured limit [dec] [chars] |
The halfopen session limit of a specific layer 4 protocol or the total \n halfopen session limit exceeded for a specific vrf id. \n This error message indicates that an unusually high rate of new \n connections is coming through the firewall and a DOS attack may be in \n progress. \n This message is issued only when the max-incomplete high threshold \n is crossed. |
cpp-ucode |
"This message is for informational purposed only but may indicate \n"" a security problem." |
|
FW-5-EMAIL_DROP_FRAGMENT |
5-Notice |
[chars]Dropping [chars] command fragment from initiator [inet]:[dec] |
- |
- |
- |
|
FW-5-IMAP_INVALID_COMMAND |
5-Notice |
[chars]Invalid IMAP command from initiator [inet]:[dec]: [chars] |
- |
- |
- |
|
FW-5-IMAP_NON_SECURE_LOGIN |
5-Notice |
[chars]LOGON IMAP command from initiator [inet]:[dec]: [chars] |
The CBAC code detected a cleartext logon attempt in the inspected IMAP\n\ connection while secure-login is configured.\n\ The command is rejected and the connection is reset by the firewall\n\ immediately. |
firewall |
"This message is for informational purposes only but may indicate a\n\ security problem." |
|
FW-5-POP3_INVALID_COMMAND |
5-Notice |
[chars]Invalid POP3 command from initiator [inet]:[dec]: [chars] |
- |
- |
- |
|
FW-5-POP3_NON_SECURE_LOGIN |
5-Notice |
[chars]LOGON POP3 command from initiator [inet]:[dec]: [chars] |
The CBAC code detected a cleartext logon attempt in the inspected POP3\n\ connection while secure-login is configured.\n\ The command is rejected and the connection is reset by the firewall\n\ immediately. |
firewall |
"This message is for informational purposes only but may indicate a\n\ security problem." |
|
FW-6-DROP_PKT |
6-Information |
Dropping [chars] pkt [inet]:[dec] => [inet]:[dec] |
Packet dropped by firewall inspection. |
firewall |
"This message is for informational purposes only. \n\ It may be used to verify that packets were dropped by the firewall." |
|
FW-6-DROP_PKT |
6-Information |
Dropping [chars][chars] pkt from [chars] [inet][chars]:[dec] => [inet][chars]:[dec] target:class-[chars]:[chars] [chars] [chars] with ip ident [dec] [chars] [chars] [chars] [chars] [chars] |
- |
- |
- |
|
FW-6-LOG_SUMMARY |
6-Information |
[dec] [chars] packet[chars] [chars] from [chars] [inet][chars]:[dec] => [inet][chars]:[dec] target:class-[chars]:[chars] [chars] [chars] |
- |
- |
- |
|
FW-6-PASS_PKT |
6-Information |
Passing [chars] pkt from [chars] [inet][chars]:[dec] => [inet][chars]:[dec] target:class-[chars]:[chars] [chars] [chars] with ip ident [dec] [chars] |
- |
- |
- |
|
FW-6-PRE_ALLOCATED_MEDIA_CHANNEL |
6-Information |
[chars]Pre-Allocated [chars] channel from [inet][[dec]:[dec]] to [inet][[dec]:[dec]] |
Firewall inspection is configured on at least one interface in the\n\ startup config. |
firewall |
"This message is for informational purposes only. \n\ It may be used to verify whether firewall inspection is on at startup." |
|
FW-6-SESS_AUDIT_TRAIL |
6-Information |
[chars]Stop [chars] session: initiator [inet]:[dec] sent [dec] bytes -- responder [inet]:[dec] sent [dec] bytes |
This message documents the per-session transaction log of network \n\ activities. The message is issued at the end of each inspected \n\ session and it records the source/destination addresses and ports \n\ as well as the number of bytes transmitted by the client and \n\ server. |
firewall |
"This message is for informational purposed only and can be used \n\ to collect the basic accounting for the inspected sessions." |
|
FW-6-SESS_AUDIT_TRAIL |
6-Information |
target:class-[chars]:[chars]:Stop [chars] session: initiator [inet][chars]:[dec] |
This message documents the per-session transaction log of network \n activities. The message is issued at the end of each inspected \n session and it records the source/destination addresses and ports \n as well as the number of bytes transmitted by the client and \n server. |
cpp-ucode |
"This message is for informational purposed only and can be used \n"" to collect the basic accounting for the inspected sessions." |
|
FW-6-SESS_AUDIT_TRAIL_START |
6-Information |
[chars]Start [chars] session: initiator [inet]:[dec] -- responder [inet]:[dec] |
This message documents the opening of an inspection session.\n\ The message is issued at the start of each inspected session\n\ and it records the source/destination addresses and ports. |
firewall |
"This message is for informational purposed only and can be used \n\ to collect the basic accounting for inspected sessions." |
|
FW-6-SESS_AUDIT_TRAIL_START |
6-Information |
target:class-[chars]:[chars]:Start [chars] session: initiator [inet][chars]:[dec] |
This message documents the opening of an inspection session.\n The message is issued at the start of each inspected session\n and it records the source/destination addresses and ports. |
cpp-ucode |
"This message is for informational purposed only and can be used \n"" to collect the basic accounting for inspected sessions." |
|
FWALL_PROXY-3-PROXY_DEBUG_REG_FAILED |
3-Error |
[dec] |
FW Conditional Debugging registration failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_FWALL_DOUBLE_INIT |
3-Error |
Data plane double initialization request. |
Coding error - second attempt to initialize data plane. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_FWALL_FBD_NOT_ENABLED |
3-Error |
FBD Not enabled.. cannot initialize data plane. |
Mismatch in FBD capabiities between client and data plane. Coding error. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_FWALL_INIT_FAILED |
3-Error |
[dec] |
Firewall initialization failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_FWALL_VFR_REG_FAILED |
3-Error |
[chars] err: [dec] |
FW VFR registration failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_HA_MEM_EXTEND_FAILED |
3-Error |
- |
Increasing of ha retry pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_HA_MEM_INIT_FAILED |
3-Error |
- |
Initialization of ha retry pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_HOSTDB_MEM_EXTEND_FAILED |
3-Error |
- |
Increasing of host database pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_HOSTDB_MEM_INIT_FAILED |
3-Error |
- |
Initialization of host database pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_HSL_ADD_DEST_FAILED |
3-Error |
- |
HSL add destination failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_HSL_BIND_FAILED |
3-Error |
- |
HSL bind failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_HSL_BIND_TEMPLATE_FAILED |
3-Error |
[dec] |
HSL bind tempalte failed at given index. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_HSL_CREATE_FAILED |
3-Error |
- |
HSL creation failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_HSL_ENABLE_FAILED |
3-Error |
- |
HSL enable failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_HSL_MODIFY_DEST_FAILED |
3-Error |
- |
HSL modify destination failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_HSL_MODIFY_FAILED |
3-Error |
- |
HSL modification failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_ICMP_ERROR_MEM_EXTEND_FAILED |
3-Error |
- |
Increasing of ICMP Error pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_ICMP_ERROR_MEM_INIT_FAILED |
3-Error |
- |
Initialization of ICMP Error control block pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_IPC_ALLOC_FAILED |
3-Error |
[dec] |
IPC allocation failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_IPC_ERM_CONF_CHANGE_FAILED |
3-Error |
[dec] |
FW IPC send failed to reply for event rate monitoring configuration change. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_IPC_FAILED |
3-Error |
[chars] [dec] |
IPC message allocation for firewall failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_IPC_INIT_FAILED |
3-Error |
[dec] |
IPC handler initialization failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_IPC_SEND_CLEAR_FAILED |
3-Error |
[dec] |
IPC send failed to reply for firewall session clear. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_IPC_SEND_DEBUG_FAILED |
3-Error |
[dec] |
IPC send failed to reply for firewall session debug. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_IPC_SEND_FAILED |
3-Error |
[dec]:[chars] |
IPC send failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_IPC_SEND_INIT_FAILED |
3-Error |
[chars] [dec] |
IPC failed to reply for firewall initialization status. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_IPC_SEND_SCB_QUERY_FAILED |
3-Error |
[dec] |
IPC send failed to reply for firewall scb query. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_IPC_SEND_SESSION_FAILED |
3-Error |
[dec] |
IPC send failed to reply for firewall session query. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_IPC_SEND_STATS_FAILED |
3-Error |
[dec] |
IPC send failed to reply for firewall status. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_SCB_MEM_EXTEND_FAILED |
3-Error |
- |
Increasing of session control block pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_SCB_MEM_INIT_FAILED |
3-Error |
- |
Initialization of session control block pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_TBL_INIT_FAILED |
3-Error |
[chars] |
Failed to initialize table. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_TEARDOWN_MEM_EXTEND_FAILED |
3-Error |
- |
Increasing of teardown pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-3-PROXY_TEARDOWN_MEM_INIT_FAILED |
3-Error |
- |
Initialization of teardown pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-4-PROXY_HSL_ALREADY_INIT |
4-Warning |
- |
HSL logger already initialized |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-4-PROXY_HSL_NOT_INIT |
4-Warning |
[dec] |
HSL logger not initialized |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-4-PROXY_IPC_INVALID_MSG |
4-Warning |
[hec] |
Invalid IPC message subtype. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-4-PROXY_IPC_INVALID_MSG_LEN |
4-Warning |
[dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Invalid IPC message length. |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-4-PROXY_IPC_UNINIT_POOL_FAILED |
4-Warning |
[chars]: [dec] |
Could not destroy chunk pool |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL_PROXY-4-PROXY_UNINIT_SESSIONS |
4-Warning |
in use [dec] [dec] |
Not all sessions freed |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL-3-FW_ALG_INVALID_TYPE |
3-Error |
[chars] [dec]:[dec] |
Invalid alg type passed from alg to firewall |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL-3-FW_NO_MATCH_INDEX_STATS |
3-Error |
[dec]---[dec] |
Client has not provided stats for the given match_index |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL-3-FW_NO_STATS |
3-Error |
[dec]:[dec] zone pair [chars] class [chars] |
Client has not provided stats for the given protocol:applicaton id |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL-3-HA_INVALID_MSG_RCVD |
3-Error |
invalid [chars] [hec] expected [hec] opcode [chars] [hec] |
Standby received an invalid Firewall HA message |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL-3-HA_INVALID_STATE |
3-Error |
[dec] |
Invalid state |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL-7-FW_NO_ALERT_CAUSE |
7-Debug |
[dec] |
Unsupported alert cause |
cpp-ucode |
LOG_STD_ACTION |
|
FWALL-7-FW_NO_DROP_CAUSE |
7-Debug |
[dec] |
Unsupported drop cause |
cpp-ucode |
LOG_STD_ACTION |
|
GBIC_SECURITY_CRYPT-4-ID_MISMATCH |
4-Warning |
Identification check failed for GBIC in port [dec] |
The GBIC was identified as a Cisco GBIC but the system was unable to verify its identity |
firmware |
"Check to see if the Cisco IOS software running on the system supports " "the GBIC. If the GBIC is newer a system software upgrade might be " "required. Otherwise verify that the GBIC was obatined from Cisco or " "from a supported vendor." |
|
GBIC_SECURITY_CRYPT-4-UNRECOGNIZED_VENDOR |
4-Warning |
GBIC in port [dec] manufactured by an unrecognized vendor |
The GBIC was identified as a Cisco GBIC but the system was unable to match its manufacturer with one on the known list of Cisco GBIC vendors |
firmware |
"Check to see if the Cisco IOS software running on the system supports " "the GBIC. If the GBIC is newer a system software upgrade might be " "required." |
|
GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR |
4-Warning |
GBIC in port [dec] has bad crc |
The GBIC was identified as a Cisco GBIC but it does not have valid CRC in the EEPROM data. |
firmware |
"Check to see if the Cisco IOS software running on the system supports " "the GBIC. If the GBIC is newer a system software upgrade might be " "required. Even if the GBIC is unrecognized by the system the GBIC " "may still operate properly but might have limited functionality." |
|
GBIC_SECURITY_UNIQUE-3-DUPLICATE_GBIC |
3-Error |
GBIC interface [dec]/[dec] is a duplicate of GBIC interface [dec]/[dec] |
The GBIC was identified as a Cisco GBIC but its vendor ID and serial number match that of another interface on the system. |
firmware |
"Cisco GBICs are assigned unique serial numbers. Verify that the GBIC " "was obtained from Cisco or a supported vendor" |
|
GBIC_SECURITY_UNIQUE-4-DUPLICATE_SN |
4-Warning |
GBIC interface [dec]/[dec] has the same serial number as another GBIC interface |
The GBIC was identified as a Cisco GBIC but its serial number matches that of another interface on the system. |
firmware |
"Cisco GBICs are assigned unique serial numbers. Verify that the GBIC " "was obtained from Cisco or a supported vendor" |
|
GBIC_SECURITY-4-EEPROM_CRC_ERR |
4-Warning |
EEPROM checksum error for GBIC in [chars] |
The GBIC in the port specified in the error message has invalid EEPROM data. |
- |
"Remove the GBIC from the specified port." |
|
GBIC_SECURITY-4-EEPROM_READ_ERR |
4-Warning |
Error in reading GBIC serial ID in [chars] |
Error when reading GBIC type from EEPROM |
- |
"Please remove GBIC from this Port" |
|
GBIC_SECURITY-4-EEPROM_SECURITY_ERR |
4-Warning |
GBIC in [chars] failed security check |
The GBIC in the port specified in the error message has invalid EEPROM data. |
- |
"Remove the GBIC from the specified port." |
|
GBIC_SECURITY-4-GBIC_INTERR |
4-Warning |
Internal error occurred in setup for GBIC interface [chars] |
The system could not allocate resources or had some other problem in the setup for the specified GBIC interface. |
firmware |
"Reload the system. If the problem persists " "contact TAC." |
|
GBIC-4-CHECK_SUM_FAILED |
4-Warning |
GBIC EEPROM data check sum failed for GBIC interface [chars] |
The GBIC was identified as a Cisco GBIC but the system was unable to read vendor-data information to verify its correctness. |
firmware |
"Remove and reinsert the GBIC. If it fails " "again in the same way the GBIC may be defective." |
|
GBIC-4-CHECK_SUM_FAILED |
4-Warning |
GBIC EEPROM data check sum failed for GBIC interface [chars] |
The GBIC was identified as a Cisco GBIC but the system was unable to read vendor-data information to verify its correctness. |
firmware |
"Remove and reinsert the GBIC. If it fails " "again in the same way the GBIC may be defective." |
|
GBIC-4-NOREAD_VNAME |
4-Warning |
Unable to read vendor name for GBIC interface [chars] |
The GBIC was identified as a Cisco GBIC but the system was unable to read the name of the GBIC's vendor. |
firmware |
"Remove and reinsert the GBIC. If it fails " "again in the same way the GBIC may be defective." |
|
GBIC-4-NOREAD_VNAME |
4-Warning |
Unable to read vendor name for GBIC interface [chars] |
The GBIC was identified as a Cisco GBIC but the system was unable to read the name of the GBIC's vendor. |
firmware |
"Remove and reinsert the GBIC. If it fails " "again in the same way the GBIC may be defective." |
|
GBIC-4-NOREAD_VSDATA |
4-Warning |
Unable to read vendor-specific data for GBIC interface [chars] |
The GBIC was identified as a Cisco GBIC but the system was unable to read identifying vendor-specific information to verify its authenticity. |
firmware |
"Remove and reinsert the GBIC. If it fails " "again in the same way the GBIC may be defective." |
|
GBIC-4-NOREAD_VSDATA |
4-Warning |
Unable to read vendor-specific data for GBIC interface [chars] |
The GBIC was identified as a Cisco GBIC but the system was unable to read identifying vendor-specific information to verify its authenticity. |
firmware |
"Remove and reinsert the GBIC. If it fails " "again in the same way the GBIC may be defective." |
|
GBIC-4-NOREAD_VSERNUM |
4-Warning |
Unable to read serial number for GBIC interface [chars] |
The GBIC was identified as a Cisco GBIC but the system was unable to read the GBIC's serial number. |
firmware |
"Remove and reinsert the GBIC. If it fails " "again in the same way the GBIC may be defective." |
|
GBIC-4-NOREAD_VSERNUM |
4-Warning |
Unable to read serial number for GBIC interface [chars] |
The GBIC was identified as a Cisco GBIC but the system was unable to read the GBIC's serial number. |
firmware |
"Remove and reinsert the GBIC. If it fails " "again in the same way the GBIC may be defective." |
|
GBIC-4-UNRECOGNIZED_EXTTYPE |
4-Warning |
GBIC interface [chars] has unrecognized extended type |
The GBIC was identified as a Cisco GBIC but the system does not recognize its reported extended type code. |
firmware |
"Check the list of supported GBICs for this version " "of the system software. An upgrade may be required " "for newer GBICs. Even if unrecognized the GBIC " "may still operate properly perhaps with limited " "functionality." |
|
GBIC-4-UNRECOGNIZED_EXTTYPE |
4-Warning |
GBIC interface [chars] has unrecognized extended type |
The GBIC was identified as a Cisco GBIC but the system does not recognize its reported extended type code. |
firmware |
"Check the list of supported GBICs for this version " "of the system software. An upgrade may be required " "for newer GBICs. Even if unrecognized the GBIC " "may still operate properly perhaps with limited " "functionality." |
|
GBIC-4-XCVR_INTERR |
4-Warning |
Internal error occurred in setup for GBIC interface [chars] |
The system could not allocate resources or had some other problem in the setup for the specified GBIC interface. |
firmware |
"Reload the system. If the problem persists " "contact TAC." |
|
GBIC-4-XCVR_INTERR |
4-Warning |
Internal error occurred in setup for GBIC interface [chars] |
The system could not allocate resources or had some other problem in the setup for the specified GBIC interface. |
firmware |
"Reload the system. If the problem persists " "contact TAC." |
|
GBIC-6-SERDES_MODULE_UNKNOWN |
6-Information |
Unrecognizable GBIC found in [chars] module mask 0x%02x |
The GBIC presented data to the system which did not correctly identify the type of the GBIC. It will be handled as a 'generic' GBIC. |
firmware |
"If the GBIC fails to become operational " "carefully reinsert it in the slot. If it " "continues to fail after reinsertion " "the GBIC may be defective or incompatible " "with the switch." |
|
GBIC-6-SERDES_MODULE_UNKNOWN |
6-Information |
Unrecognizable GBIC found in [chars] module mask 0x%02x |
The GBIC presented data to the system which did not correctly identify the type of the GBIC. It will be handled as a 'generic' GBIC. |
firmware |
"If the GBIC fails to become operational " "carefully reinsert it in the slot. If it " "continues to fail after reinsertion " "the GBIC may be defective or incompatible " "with the switch." |
|
GBIC-6-SERDES_SERIAL_INV_DATA |
6-Information |
Unrecognizable GBIC found in [chars] serial data 0x%02x |
The GBIC presented data to the system which did not correctly identify the type of the GBIC. It will be handled as a 'generic' GBIC. |
firmware |
"If the GBIC fails to become operational " "carefully reinsert it in the slot. If it " "continues to fail after reinsertion " "the GBIC may be defective or incompatible " "with the switch." |
|
GBIC-6-SERDES_SERIAL_INV_DATA |
6-Information |
Unrecognizable GBIC found in [chars] serial data 0x%02x |
The GBIC presented data to the system which did not correctly identify the type of the GBIC. It will be handled as a 'generic' GBIC. |
firmware |
"If the GBIC fails to become operational " "carefully reinsert it in the slot. If it " "continues to fail after reinsertion " "the GBIC may be defective or incompatible " "with the switch." |
|
GDOI-1-GDOI_ACE_DENY |
1-Alert |
A Group Member ACL policy containing deny was attempted. This is not supported. |
A Group Member ACL policy containing deny was attempted. This is not supported. |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-1-GDOI_ACL_NUM |
1-Alert |
The ACL has too many entries.\n GDOI will honor only the first 100 ACL entries specified. |
The ACL has too many entries. GDOI will honor only the first 100 ACL entries specified. |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-1-KS_NO_RSA_KEYS |
1-Alert |
RSA Key - [chars] : Not found Required for group [chars] |
Rsa Keys were not found in Key Server and they are required for signing and verifying rekey messages |
ipsec-getvpn |
"Contact the Key Server's administrator and ask him to do create" " the RSA Key pair" |
|
GDOI-1-UNAUTHORIZED_IDENTITY |
1-Alert |
Group [chars] received registration from unauthorized identity: [chars] |
The registration request was dropped because the requesting device was not authorized to join the group. |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-1-UNAUTHORIZED_IPADDR |
1-Alert |
Group [chars] received registration from unauthorized ip address: [chars] |
The registration request was dropped because the requesting device was not authorized to join the group. |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-1-UNREGISTERED_INTERFACE |
1-Alert |
Group [chars] received registration from unregistered interface. |
Receiving registration from unregistered interface. Stop processing it. |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-2-COOP_MINOR_VERSION_MISMATCH |
2-Critical |
COOP-KS Minor version mistmatch in group [chars]. My COOP version is [dec].[dec].[dec] peer [chars] has version [dec].[dec].[dec]. Upgrade [chars] [chars] to COOP version [dec].[dec].[dec] to prevent COOP outage. |
Coop KS has different minor version. |
ipsec-getvpn |
"show crypto gdoi ks coop" |
|
GDOI-3-COOP_ANN_SEQ_FAILURE |
3-Error |
COOP Ann msg seq check failed for group [chars] ann seq# [dec] sess seq# [dec] |
COOP Ann msg seq check failed |
ipsec-getvpn |
"Contact Administrator" |
|
GDOI-3-COOP_CONFIG_MISMATCH |
3-Error |
WARNING: Group [chars] [chars] configuration between Primary KS and Secondary KS are mismatched |
The configuration between Primary KS and Secondary KS are mismatched |
ipsec-getvpn |
"Contact the Key Sever's administrator" |
|
GDOI-3-COOP_KS_CANNOT_FIND_PROFILE |
3-Error |
Coop KS in group [chars] has a configured IKEv2 profile '[chars]' that doesn't exist. The COOP will not come up until this error is fixed. |
The KS COOP coniguration redunadancy ikve2-profile specifies a profile that doesn't exist. The COOP will not come up. |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-3-COOP_KS_SEND_WINDOW_LIMIT_REACHED |
3-Error |
The COOP KS has reached its window limit for the peer addresses local [chars] remote [chars]. This is due to connectivity issues between the key servers in question. |
The COOP KS running over IKEv2 has a limit to the number of pending messages that can be sent. This limit has been reached which is an indication that there is a connectivity issue between the key servers |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-3-COOP_KS_TOO_MANY_GROUPS_SHARE_IKE_SA |
3-Error |
The COOP KS has too many groups sharing the same IKE SA for the peer addresses local [chars] remote [chars]. Connectivity could be compromised. Please reduce to [dec]. |
There is a limit to the number of COOP KS groups that can share the. same IKE SA. This can lead to intermittent connectivity for the COOP KS in congested networks |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-3-COOP_KS_UNREACH |
3-Error |
Cooperative KS [chars] Unreachable in group [chars]. IKE SA Status = [chars] |
The reachability between the configugred cooperative key servers is lost. Some might consider this a hostile event. |
ipsec-getvpn |
"Contach the Administrators of the configured key servers." |
|
GDOI-3-COOP_KSSID_OVERLAP |
3-Error |
Overlapping KS Sender Identifiers KSSID {[chars]} |
Another COOP-KS peer in the group has been configured with a KSSID value that is the same as one configured on this KS. GM registration is blocked as a result until the overlap is fixed. |
ipsec-getvpn |
"Check the configured KSSIDs for all COOP-KS peers by issuing " |
|
GDOI-3-COOP_LIMIT_REACHED |
3-Error |
Peer [chars] has reached COOP limit of maximum number of gms. COOP GM database sync fails. Upgrade to COOP version [dec].[dec].[dec] and above |
COOP-KS has a non-compatible peer. |
ipsec-getvpn |
"Check COOP version compatibility on peer KS" |
|
GDOI-3-COOP_MAJOR_VERSION_MISMATCH |
3-Error |
COOP-KS Major Version mismatch in group [chars]. My version is [dec].[dec].[dec] peer [chars] has version [dec].[dec].[dec] |
COOP-KS has a non-compatible major version. |
ipsec-getvpn |
"Check COOP version compatibility on KS" |
|
GDOI-3-COOP_PACKET_DROPPED |
3-Error |
Announcement message dropped due to packet size [dec] bytes. |
Hard limit set on the driver buffer size prevents sending packets of this size or bigger |
ipsec-getvpn |
"Informational message" |
|
GDOI-3-GDOI_ACL_RANGE |
3-Error |
The ACL [chars] contains port range which is NOT supported. WARNING: No TEK policy will be created. |
GDOI does not support port range in the ACL policy. |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-3-GDOI_REKEY_FAILURE |
3-Error |
Processing of REKEY payloads failed on GM [chars] in the group [chars] with peer at [chars] |
During GDOI rekey the payload parsing failed on this GM from the Key Server. |
ipsec-getvpn |
"Contact the Group member's administrator." |
|
GDOI-3-GDOI_REKEY_SEQ_FAILURE |
3-Error |
Failed to process rekey seq # [dec] in seq payload for group [chars] last seq # [dec] |
During GDOI rekey the seq payload parsing failed on this GM from the Key Server. |
ipsec-getvpn |
"Contact the Group member's administrator." |
|
GDOI-3-GM_ACL_PERMIT |
3-Error |
GM doesn't support permit configured under local access-list. Traffic from [chars] to [chars] will be dropped. |
GM can only support ACL for deny. Any traffic matching the permit entry will be dropped. |
ipsec-getvpn |
"Remove the permit entry from the ACL used by GDOI crypto map" |
|
GDOI-3-GM_FAILED_TO_INITIALISE |
3-Error |
GDOI GM Process has failed to initialise |
GDOI Group Member process has failed to initialise on this Network Element |
ipsec-getvpn |
- |
|
GDOI-3-GM_INCOMPLETE_CFG |
3-Error |
Registration: incomplete config for group [chars] |
Registration can not be completed since the GDOI group configuration may be missing the group id server id or both |
ipsec-getvpn |
"Contact the Group member's administrator." |
|
GDOI-3-GM_IPD3P_AND_CMD_CANT_COEXIST |
3-Error |
GETVPN group-member does not support coexistance of IPD3P and Cisco-metadata features |
GETVPN group-member does not support the enabling of IPD3P and Cisco-metadata features e.g TBAR-PST SGT at the |
ipsec-getvpn |
"Contact the Administrators to correct the key server policy." |
|
GDOI-3-GM_IPD3P_NO_IPV6_SUPPORT |
3-Error |
GETVPN group-member does not support IP-D3P for IPv6. |
GETVPN group-member does not support IP-D3P for IPv6. |
ipsec-getvpn |
"Contact the Administrators to correct the key server policy." |
|
GDOI-3-GM_IPD3P_NO_TRANSPORT_SUPPORT |
3-Error |
GETVPN group-member does not support IPD3P transport mode |
GETVPN group-member does not support IPD3P transport mode |
ipsec-getvpn |
"Contact the Administrators to correct the key server policy." |
|
GDOI-3-GM_MAJOR_VERSION_MISMATCH |
3-Error |
GM [inet] registration rejected due to major version mismatch. GM must be using major version [dec] in order to be compatible with this KS |
GM has a non-compatible major version. |
ipsec-getvpn |
"Check GDOI version compatibility on KS and GMs" |
|
GDOI-3-GM_NO_CRYPTO_ENGINE |
3-Error |
No crypto engine is found due to lack of resource or unsupported feature requested |
Failed to select a suitable crypto engine because requested packet path not available or requested feature not supported |
ipsec-getvpn |
"Check policy configured on KS" |
|
GDOI-3-GM_NO_IPSEC_FLOWS |
3-Error |
IPSec FLOW limit possibly reached |
Hardware Limitation for IPSec Flow limit Reached. Cannot create any more IPSec SAs |
ipsec-getvpn |
"Contact the Group member's administrator." |
|
GDOI-3-IPSEC_INITIATE_GM_REGISTER_IGNORE |
3-Error |
IPSEC triggering registration for group [chars] too frequently. Ignore the request as registartion has already been scheduled to occur in [dec] msec. |
GM detects IPSEC triggering registration for the group too frequently. GDOI will ignore the request as registration has already been scheduled. |
ipsec-getvpn |
"Contact the Group member's administrator." |
|
GDOI-3-IPSEC_INITIATE_GM_REGISTER_POSTPONE |
3-Error |
IPSEC triggering registration for group [chars] too frequently. Postpone the registration to occur in [dec] msec. |
GM detects IPSEC triggering registration for the group too frequently. GDOI will rate-limit and postpone the registration. |
ipsec-getvpn |
"Contact the Group member's administrator." |
|
GDOI-3-KS_BAD_ID |
3-Error |
Registration: [chars] config mismatch between KS and the GM [inet] in the group [chars]. |
During GDOI registration protocol a configuration mismatch between local key server and group member. |
ipsec-getvpn |
"Contact the Group member's administrator." |
|
GDOI-3-KS_BLACKHOLE_ACK |
3-Error |
KS blackholing GM [inet] in group [chars]. |
Key server has reached a condition of blackholing messages from GM Some might consider this a hostile event. |
ipsec-getvpn |
- |
|
GDOI-3-KS_GM_REVOKED |
3-Error |
Re-Key: GM [inet] revoked by KS in the group [chars]. |
During Re-key protocol an unauthorized member tried to join a group. Some might consider this a hostile event. |
ipsec-getvpn |
"Contact the Key Server's administrator." |
|
GDOI-3-KS_MAJOR_VERSION_MISMATCH |
3-Error |
COOP-KS Major Version mismatch in group [chars]. My version is [dec].[dec].[dec] peer [chars] has version [dec].[dec].[dec] |
COOP-KS has a non-compatible major version. |
ipsec-getvpn |
"Check GDOI version compatibility on KS" |
|
GDOI-3-KS_NO_SID_AVAILABLE |
3-Error |
GMs for group [chars] need SIDs but this KS has no KS SIDs configured or no more SIDs available. |
This KS has a counter-mode transform configured requiring SIDs and either has no KSSIDs configured or has run out of SIDs. Registering GMs will not be able to register successfully until more KSSIDs are configured on this KS. |
ipsec-getvpn |
"Check the configured KSSIDs for this KS by issuing " |
|
GDOI-3-KS_REKEY_AUTH_KEY_LENGTH_INSUFFICIENT |
3-Error |
Rejected [chars] change: using sig-hash algorithm [chars] requires an authentication key length of at least [dec] bits [dec] blocks in bytes |
Using a sig-hash algorithm for rekeys requires that the RSA key modulus length for the rekey authentication be at least the length of the hash generated by the sig-hash algorithm plus some padding bytes. If the RSA key modulus length is not large enough the Key Server administrator needs to generate a new RSA key pair wit a sufficient length. |
ipsec-getvpn |
"Contact the Key Server's administrator to re-generate the RSA " "key pair with at least the modulus length given in the syslog." |
|
GDOI-3-KS_UNAUTHORIZED |
3-Error |
Registration: Unauthorized [inet] tried to join the group [chars]. |
During GDOI registration protocol an unauthorized member tried to join a group Some might consider this a hostile event. |
ipsec-getvpn |
"Contact the Key Server's administrator." |
|
GDOI-3-P2P_KGS_INFRA_ERROR |
3-Error |
PIP session with [chars] failed because of KGS Infra failure. Reason = [chars] |
A Group Member has encountered a KGS Infra failure. |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-3-P2P_PEER_MIGRATE_FAILED |
3-Error |
Failed to install P2P rekey SA with peer [chars] in group [chars] |
Installation of P2P Rekey SA with an existing peer has failed |
ipsec-getvpn |
"Check the status of all peers using the command " " 'show crypto gdoi gm p2p peers' and wait for PIP initiation between " "the failed peers. Traffic distruption may occur." |
|
GDOI-3-PIP_PSEUDO_TIME_ERROR |
3-Error |
An Anti-Replay check has failed for PIP in group [chars]: my_pseudotime = [chars] peer_pseudotime = [chars] replay_window = %lld sec src_addr = [chars] dst_addr = [chars] |
- |
- |
- |
|
GDOI-3-PSEUDO_TIME_LARGE |
3-Error |
Pseudotime difference between KS [dec] sec and GM [dec] sec |
A Group member has received pseudotime which has large difference as compared to own pseudotime |
ipsec-getvpn |
- |
|
GDOI-3-PSEUDO_TIME_TOO_OLD |
3-Error |
Rekey received in group [chars] is too old and fail PST check: my_pst is [dec] sec peer_pst is [dec] sec allowable_skew is [dec] sec |
A Group member has received pseudotime which has large difference as compared to own pseudotime |
ipsec-getvpn |
- |
|
GDOI-3-SA_KEK_INSATALL_FAILED |
3-Error |
Failed to install KEK SA |
KEK SA instalation has failed |
ipsec-getvpn |
"Informational message." |
|
GDOI-3-UNEXPECTED_SIGKEY |
3-Error |
Unexpected Signature Key detected: freeing it |
Unexpected Signature Key found: freeing the signature key |
ipsec-getvpn |
"Informational message" |
|
GDOI-3-UNSUPPORTED_TEK_PROTO |
3-Error |
Unexpected TEK Protocol : [dec] |
Unexpected TEK PROTOCOL |
ipsec-getvpn |
"Informational message" |
|
GDOI-4-COOP_KS_CHECKPT_MISMATCH |
4-Warning |
Coop KS [chars] in group [chars] received Checkpoint Mismatch message. |
The KS COOP had received a checkpoint mismatch from a KS COOP peer |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-4-COOP_KS_CKM_INCOMPATIBLE |
4-Warning |
Found incompatible COOP-KS that cannot support CKM in group [chars]. Please check 'show crypto gdoi feature ckm'and upgrade the incompatible KS immediately. |
Found incompatible COOP-KS that cannot support CKM in the group. Network administrator should check 'show crypto gdoi feature ckm'and upgrade the incompatible KS immediately |
- |
LOG_STD_ACTION |
|
GDOI-4-COOP_KS_RBLY_FAILED |
4-Warning |
Coop KS [chars] in group [chars] session Reassembly failed in TransID [dec] |
The KS COOP had an error reassmbling a packet from a peer KS |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-4-COOP_KS_UNAUTH |
4-Warning |
Contact from unauthorized KS [chars] in group [chars] at local address [chars] Possible MISCONFIG of peer/local address |
- |
- |
- |
|
GDOI-4-GDOI_ANN_INCONSISTENT_TBAR |
4-Warning |
COOP_KS ANN received from [chars] in group [chars] has inconsistent TBAR setting inconsistent than mine |
The KS has received an ANN msg from a secondary KS in which the timestamp is too old |
ipsec-getvpn |
- |
|
GDOI-4-GDOI_ANN_TIMESTAMP_LARGE |
4-Warning |
COOP_KS ANN received from KS [chars] in group [chars] has PST bigger than myself. Adjust to new PST:\n my_old_pst is %llu sec peer_pst is %llu sec |
- |
ipsec-getvpn |
- |
|
GDOI-4-GDOI_ANN_TIMESTAMP_LARGE_NO_UPDATE |
4-Warning |
COOP_KS ANN received from KS [chars] in group [chars] has PST bigger than myself:\n my_pst is %llu sec peer_pst is %llu sec |
- |
ipsec-getvpn |
- |
|
GDOI-4-GDOI_ANN_TIMESTAMP_TOO_OLD |
4-Warning |
COOP_KS ANN from KS [chars] in group [chars] is too old and fail PST check:\n my_pst is %llu sec peer_pst is %llu sec allowable_skew is [dec] sec |
The KS has received an ANN msg from a primary KS in which the timestamp is too old |
ipsec-getvpn |
- |
|
GDOI-4-GM_DELETE |
4-Warning |
GM [chars] deleted from group [chars]. |
A group member has been deleted in a group from Key Server |
ipsec-getvpn |
"Informational message" |
|
GDOI-4-GM_HASH_FAIL |
4-Warning |
Registration: BadNo hash in message sent by the KS [inet] |
During GDOI registration protocol a message sent by the Key server has bad or no hash . |
ipsec-getvpn |
"Contact the Key Server's administrator." |
|
GDOI-4-GM_MINOR_VERSION_MISMATCH |
4-Warning |
GM [inet] Minor Version mismatch. Use 'show crypto gdoi ks members' to see GM versions |
GM has different minor version. |
ipsec-getvpn |
"show crypto gdoi ks members" |
|
GDOI-4-GM_PFS_RE_REGISTER |
4-Warning |
Start PFS triggered re-registration to KS [chars] for group [chars] using address [chars] fvrf [chars] ivrf [chars] |
Received PFS Rekey Hence re-registring to download new policy. |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-4-GM_RE_REGISTER |
4-Warning |
The IPSec SA created for group [chars] may have expired/been cleared or didn't go through. Re-register to KS. |
The IPSec SA created for one group may have expired/been cleared or didn't go through need to re-register to KS. |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-4-GM_RECOVERY_REGISTRATION |
4-Warning |
GM recovery re-registration for group [chars] will start in a randomly chosen period of [dec] sec |
GM recovery feature detects dataplane error and will re-register to KS to refresh keys and policy |
- |
"Informational message." |
|
GDOI-4-GM_RECOVERY_REGISTRATION_POSTPONED |
4-Warning |
Detects data error in group [chars] but the previous recovery/rekey has occured within the last recovery-check interval. Postpone recovery registration to start in [dec] sec |
GM recovery feature detects dataplane error and will re-register to KS to refresh keys and policy |
- |
"Informational message." |
|
GDOI-4-GM_RECV_DELETE |
4-Warning |
GM received delete-msg from KS in group [chars]. TEKs lifetime are reduced and re-registration will start before SA expiry |
A messages sent by the KS to delete the GM has been received. |
ipsec-getvpn |
"Informational message." |
|
GDOI-4-GM_RECV_DELETE_IMMEDIATE |
4-Warning |
GM receive REMOVAL-NOW in group [chars] to cleanup downloaded policy now. Re-registration will start in a randomly chosen period of [dec] sec |
A messages sent by the KS to delete the GM has been received. |
ipsec-getvpn |
"Informational message." |
|
GDOI-4-GM_RECV_POLICY_REPLACE_NOW |
4-Warning |
GM received policy replace now rekey from KS in group [chars]. |
A messages sent by the KS to immediately replace SAs policies on the GM has been received. |
ipsec-getvpn |
"Informational message." |
|
GDOI-4-GM_RECV_RE_AUTH |
4-Warning |
GM received Re-auth-msg from KS in group [chars]. re-registration will start before SA expiry |
A message sent by the KS to have a GM re-auth has been received. |
ipsec-getvpn |
"Informational message." |
|
GDOI-4-GM_REJECTING_SA_PAYLOAD |
4-Warning |
Registration: Policy in SA payload sent by KS [inet] rejected by GM in the group [chars] reason [chars]. |
During GDOI registration protocol a proposal sent by the key server was refused by the local group member. |
ipsec-getvpn |
"Contact the Key server's administrator." |
|
GDOI-4-GM_REKEY_NOT_RECD |
4-Warning |
GM did not receive rekey from KS [inet] in group [chars]. |
GM has not received a rekey message from a key server in a group Currently Unimplemented. |
ipsec-getvpn |
"Informational message" |
|
GDOI-4-GM_SA_TRACK_SET_EOT_ERROR |
4-Warning |
Group [chars] encountered error in setting EOT object ID [dec] to state [chars]. |
GM SA TRACK state change occur but fail to update EOT object ID accordingly |
- |
"Informational message. Check to make sure the EOT " "object ID is configured properly" |
|
GDOI-4-KS_GM_REJECTS_SA_PAYLOAD |
4-Warning |
Registration: GM [inet] rejected a policy in the SA proposal sent by KS in the group [chars]. |
During GDOI registration protocol a proposal sent by the key server was refused by the group member. |
ipsec-getvpn |
"Contact the Group member's administrator." |
|
GDOI-4-KS_HASH_FAIL |
4-Warning |
Registration: BadNo Hash in Message sent by the GM [inet] |
During GDOI registration protocol a message sent by the Group member has bad or no hash . |
ipsec-getvpn |
"Contact the Group member's administrator." |
|
GDOI-4-KS_MINOR_VERSION_MISMATCH |
4-Warning |
COOP-KS Minor Version mistmatch in group [chars]. My version is [dec].[dec].[dec] peer [chars] has version [dec].[dec].[dec] |
Coop KS has different minor version. |
ipsec-getvpn |
"show crypto gdoi ks coop" |
|
GDOI-4-KS_UNSOL_ACK |
4-Warning |
KS received unsolicited ACK from GM [inet] in group [chars]. |
Key server has received an unsolicited ACK from a past GM or is under a DOS attack. Some might consider this a hostile event. |
ipsec-getvpn |
- |
|
GDOI-4-LKH_GM_DELETE |
4-Warning |
GM [inet] deleted from LKH in group [chars]. |
A Group member has been deleted in a group from LKH |
ipsec-getvpn |
- |
|
GDOI-4-NEWER_GM_VERSION_REGISTER |
4-Warning |
WARNING: GM [chars] registers to group [chars] with newer GDOI version than KS. Please check'show crypto gdoi ks members' and 'show crypto gdoi feature' to ensure all GMs can support the GETVPN features enabled. |
- |
ipsec-getvpn |
"Check GMs can support all GETVPN features enabled " "in KS. Also check output of 'show crypto gdoi " "feature' and 'debug crypto gdoi ks infra detail' " "note: high volume of debugs. " |
|
GDOI-4-REJECT_GM_CKM_REGISTER |
4-Warning |
Reject registration of GM [inet] in group [chars] as it has CKM enabled but this secondaryKS has not sync up all KGS params yet |
Reject GM registration because this is a secondaryKS and it has not received KGS seed and rekey-epoch from primaryKS yet |
- |
LOG_STD_ACTION |
|
GDOI-4-REJECT_GM_VERSION_REGISTER |
4-Warning |
Reject registration of GM [inet] ver 0x[hec] in group [chars] as it |
Reject GM registration because it cannot support the GETVPN features enabled in the group. |
ipsec-getvpn |
"Check GMs can support all GETVPN features enabled " "in KS. Also check output of 'show crypto gdoi " "feature' and 'debug crypto gdoi ks infra detail' " "note: high volume of debugs. " |
|
GDOI-4-RSA_KEYS_MODIFIED |
4-Warning |
WARNING: GMs for group [chars] will re-register due to signature verification failure |
Rekeys will be dropped by GM as signature verification would fail due to modification of RSA Keys |
ipsec-getvpn |
"Informational message" |
|
GDOI-4-TIMEBASED_REPLAY_FAILED |
4-Warning |
An anti replay check has failed in group [chars]: my_pseudotime = [chars] peer_pseudotime = [chars] replay_window = [dec] sec src_ip = [inet] dst_ip = [inet] |
- |
- |
- |
|
GDOI-4-TIMEBASED_REPLAY_FAILED_IPV6 |
4-Warning |
An anti replay check has failed in group [chars]: my_pseudotime = [chars] peer_pseudotime = [chars] replay_window = [dec] sec src_ip = %P dst_ip = %P |
- |
- |
- |
|
GDOI-5-COOP_KS_ADD |
5-Notice |
[chars] added as COOP Key Server in group [chars]. |
A key server has been added to the list of cooperative key servers in a group |
ipsec-getvpn |
"Informational message" |
|
GDOI-5-COOP_KS_ADMN_USRP_PRI |
5-Notice |
Primary role Usurped by KS [chars] in group [chars]. |
A network adminstrator has made the local KS as primary by means of a CLI command. Currently Unimplemented. |
ipsec-getvpn |
"Informational message" |
|
GDOI-5-COOP_KS_BLOCK_NEW_GM_REGISTER_ANN |
5-Notice |
This KS temporarily blocks GM with ip-addr [chars] from registering in group [chars] as it has not received an ANN with valid PST for prolonged period |
No valid ANN message has been received in this secondary KS for a prolong period. Temporarily blocking new GM registrations until a valid ANN is received |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-5-COOP_KS_BLOCK_NEW_GM_REGISTER_ELECTION |
5-Notice |
This KS temporarily blocks GM with ip-addr [chars] from registering in group [chars] as the KS election is underway |
The KS is in the process of electing a primary. Temporarily blocking new GM registrations until the election is complete |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-5-COOP_KS_BLOCK_NEW_GM_REGISTER_KSSID |
5-Notice |
This KS is blocking GM with ip-addr [chars] from registering in group [chars] as it has overlapping KS Sender Identifiers KSSID with |
Another COOP-KS peer in the group has been configured with a KSSID value that is the same as one configured on this KS. GM registration is blocked as a result until the overlap is fixed. |
ipsec-getvpn |
"Check the configured KSSIDs for all COOP-KS peers by issuing " |
|
GDOI-5-COOP_KS_ELECTION |
5-Notice |
KS entering election mode in group [chars] Previous Primary = [chars] |
The local Key server has entered the election process in a group |
ipsec-getvpn |
"Informational message" |
|
GDOI-5-COOP_KS_REACH |
5-Notice |
Reachability restored with Cooperative KS [chars] in group [chars]. |
The reachability between the configugred cooperative key servers is restored. |
ipsec-getvpn |
"Informational message" |
|
GDOI-5-COOP_KS_REMOVE |
5-Notice |
[chars] removed as COOP Key Server in group [chars]. |
A key server has been removed from the list of cooperative key servers in a group |
ipsec-getvpn |
"Informational message" |
|
GDOI-5-COOP_KS_RESUME_NEW_GM_REGISTER |
5-Notice |
This KS will now resume new GM registration functionality in group [chars] |
This KS will now resume new GM registration functionality |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-5-COOP_KS_TRANS_TO_PRI |
5-Notice |
KS [chars] in group [chars] transitioned to Primary Previous Primary = [chars] |
The local Key server transitioned to a primary role from being a secondary server in a group |
ipsec-getvpn |
"Informational message" |
|
GDOI-5-COOP_KS_VALID_ANN_TIMER_EXPIRED |
5-Notice |
This sec-KS has NOT received an ANN with valid PST for an extended period in group [chars]. It will block new GMs registration temporarily until a valid ANN is received |
No valid ANN message has been received in this secondary KS for a prolong period. Temporarily blocking new GM registrations until a valid ANN is received |
ipsec-getvpn |
"Informational message" |
|
GDOI-5-COOP_KSSID_OVERLAP_RESOLVED |
5-Notice |
Resolved overlapping KS Sender Identifiers KSSID |
Another COOP-KS peer in the group had been configured with a KSSID value that was the same as one configured on this KS but has been resolved so that GM registration is allowed again. |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-5-ESON_POLICY_CHANGE_RESTART1 |
5-Notice |
ESON group [chars] policy has changed. Must use 'clear crypto gdoi ks members now' to restart the group |
Reminder message that ESON configuration has changed. |
eson-ckm |
LOG_STD_ACTION |
|
GDOI-5-ESON_POLICY_CHANGE_RESTART2 |
5-Notice |
ESON group [chars] policy has changed. Must use 'crypto gdoi ks replace now' to restart the group |
Reminder message that ESON configuration has changed. |
eson-ckm |
LOG_STD_ACTION |
|
GDOI-5-GM_ACL_MERGE |
5-Notice |
ACL betweem KS and GM in group [chars] merged. |
The ACL differences between GM and KS are resolved and a merge took place |
ipsec-getvpn |
- |
|
GDOI-5-GM_CLEAR_REGISTER |
5-Notice |
Config: GM cleared gdoi configuration for the group [chars]. |
clear crypto gdoi command has been executed by the local GM |
ipsec-getvpn |
"Informational message." |
|
GDOI-5-GM_CM_ATTACH |
5-Notice |
Crypto map attached for GM in group [chars]. |
A crypto map has been attached for the local group member. |
ipsec-getvpn |
"Informational message." |
|
GDOI-5-GM_CM_DETACH |
5-Notice |
Crypto map detached for GM in group [chars]. |
A crypto map has been detached for the local group member. |
ipsec-getvpn |
"Informational message." |
|
GDOI-5-GM_CONV_SA_DUPLEX |
5-Notice |
IPSec SAs converted to Duplex in group [chars] on the GM. |
IPSec SAs have been converted to bidirectional mode in a group on a GM |
ipsec-getvpn |
- |
|
GDOI-5-GM_CONV_SA_DUPLEX_LOCAL |
5-Notice |
IPSec SAs converted to Duplex in group [chars] on a GM by a local event. |
IPSec SAs have been converted to bidirectional mode in a group on a GM by a CLI command |
ipsec-getvpn |
- |
|
GDOI-5-GM_DELETE_EXPIRED_KEK |
5-Notice |
KEK expired for group [chars] and was deleted |
Deleting Expired KEK |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-5-GM_DELETE_EXPIRED_P2P |
5-Notice |
P2P SA with epoch hash 0x[chars] expired for group [chars] and was deleted |
Deleting Expired P2P |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-5-GM_DELETE_EXPIRED_PIP |
5-Notice |
PIP with SPI 0x[chars] expired for group [chars] and was deleted |
Deleting Expired PIP |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-5-GM_ENABLE_GDOI_CM |
5-Notice |
GM has enabled ACL on GDOI crypto map in group [chars]. |
Group member has enabled ACL on a GDOI Crypto map in a group with a key server |
ipsec-getvpn |
- |
|
GDOI-5-GM_FAILED_TO_INSTALL_POLICIES |
5-Notice |
FAILED: Installation of Reg/Rekey policies from KS [chars] for group [chars] & gm identity [chars] |
Failed Policy installation |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-5-GM_INSTALL_POLICIES_SUCCESS |
5-Notice |
SUCCESS: Installation of Reg/Rekey policies from KS [chars] for group [chars] & gm identity [chars] fvrf [chars] ivrf [chars] |
Policy Installation Success |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-5-GM_IV_EXHAUSTED |
5-Notice |
GM for group [chars] exhausted its IV space for interface [chars] and will re-register. |
This GM is registering to an IPv6 group but erroneously receiving IPv4 policies in rekey |
ipsec-getvpn |
"Check GMs can support all GETVPN features enabled " "in KS. Also check output of 'show crypto gdoi " "feature' and 'debug crypto gdoi ks infra detail' " "note: high volume of debugs. " |
|
GDOI-5-GM_POLICY_CLEANUP |
5-Notice |
KS downloaded Policy Cleared and Fail Close policy installed for GM [chars] in group [chars] |
As the Fail close revert option is configured and KS is not reachable or registartion is failed we will remove the KS downloaded policy and apply the Fail close policy back on this GM |
ipsec-getvpn |
"Informational message." |
|
GDOI-5-GM_RECV_REKEY |
5-Notice |
Received Rekey for group [chars] from [chars] to [chars] with seq # [dec] spi 0x[hec][hec][hec][hec] |
Received Rekey |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-5-GM_REGISTER_UPDATE_TBAR |
5-Notice |
Platform HA forwarding-plane comes online group [chars] gm-identity [chars] fvrf [chars] ivrf [chars] re-register to refresh TBAR info. |
HA forwarding-plane comes online group [chars] gm-identity [chars] fvrf [chars] ivrf [chars] is re-registering to refresh TBAR info. |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-5-GM_REGS_COMPL |
5-Notice |
Registration to KS [chars] complete for group [chars] using address [chars] fvrf [chars] ivrf [chars] |
Complete registration |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-5-GM_REKEY_CIPHER_HASH_CHECK_FAIL |
5-Notice |
Rekey cipher/hash [chars] used in Group [chars] is unacceptable |
The key-server has chosen KEK rekey cipher/hash algorithms which are not acceptable by this group-member |
- |
"Contact the Key server's administrator." |
|
GDOI-5-GM_REKEY_TRANS_2_MULTI |
5-Notice |
Group [chars] transitioned to multicast rekey. |
GM has transitioned from using unicast rekey mechanism to multicast mechanism |
ipsec-getvpn |
"Informational message" |
|
GDOI-5-GM_REKEY_TRANS_2_UNI |
5-Notice |
Group [chars] transitioned to Unicast Rekey. |
GM has transitioned from using multicast rekey mechanism to unicast mechanism |
ipsec-getvpn |
"Informational message" |
|
GDOI-5-GM_REKEY_TRANSFORMSET_CHECK_FAIL |
5-Notice |
The transformset [chars] for data-protection in Group [chars] is |
The key-server has chosen a TEK transformset which is not acceptable by this group-member |
- |
"Contact the Key server's administrator." |
|
GDOI-5-GM_SA_INGRESS |
5-Notice |
Receive only ACL received from KS [inet] in group [chars]. |
Received only acl has been received by GM from a KS in a group |
ipsec-getvpn |
- |
|
GDOI-5-GM_UNREGISTER |
5-Notice |
GM left the group [chars]. |
A Group member has left the group. |
ipsec-getvpn |
"Informational message." |
|
GDOI-5-IPSEC_INITIATE_GM_REGISTER |
5-Notice |
IPSEC initiate GDOI group [chars] to register |
IPSEC initiate a GM registration for the group |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-5-KS_CLEAR_REGISTER |
5-Notice |
Config: KS cleared gdoi configuration for the group [chars]. |
clear crypto gdoi command has been executed by the local KS |
ipsec-getvpn |
"Informational message." |
|
GDOI-5-KS_CONV_SAS_DUPLEX |
5-Notice |
IPSec SAs converted to Duplex in group [chars]. |
IPSec SAs have been converted to bidirectional mode in a group |
ipsec-getvpn |
- |
|
GDOI-5-KS_CONV_SAS_INGRESS |
5-Notice |
IPSec SAs converted to Ingress in group [chars]. |
IPSec SAs have been converted to receive only mode in a group |
ipsec-getvpn |
- |
|
GDOI-5-KS_GROUP_ADD |
5-Notice |
Config: KS [inet] added to the Group [chars]. |
A Config command has been executed to add a Key Server in a group |
ipsec-getvpn |
"Informational message." |
|
GDOI-5-KS_GROUP_DELETE |
5-Notice |
Config: KS [inet] removed from the Group [chars]. |
A Config command has been executed to remove a Key Server from a group |
ipsec-getvpn |
"Informational message." |
|
GDOI-5-KS_NACK_GM_EJECT |
5-Notice |
KS ejected GM [inet] in group [chars]. |
Key server has reached a condition of not receiving an ACK from GM and has been ejected |
ipsec-getvpn |
"Informational message" |
|
GDOI-5-KS_REGS_COMPL |
5-Notice |
KS completed successful registration in group [chars] with GM [inet]. |
Key server has successfully completed a registration in a group |
ipsec-getvpn |
- |
|
GDOI-5-KS_REINIT_FINISH |
5-Notice |
Re-initialization of group [chars] completed. |
A previously triggered re-initialization as signified by a \%GDOI-5-KS_REINIT_GROUP syslog has completed after the expiry of the old TEK. |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-5-KS_REINIT_GROUP |
5-Notice |
[chars] for group [chars] and will re-initialize the group. |
KS has reached one of the following conditions indicated by the first part of the message requiring re-initialization of the group:\n |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-5-KS_REKEY_SYNCUP_2_REPLACE |
5-Notice |
Group [chars] transitioned to primary but no policy generated yet continuing with POLICY REPLACE rekey |
KS Group has transitioned to new Primary but no policy generated yet to recover from this situation continuing with POLICY REPLACE rekey |
ipsec-getvpn |
"Informational message" |
|
GDOI-5-KS_REKEY_TRANS_2_MULTI |
5-Notice |
Group [chars] transitioned to multicast rekey. |
Group has transitioned from using unicast rekey mechanism to multicast mechanism |
ipsec-getvpn |
"Informational message" |
|
GDOI-5-KS_REKEY_TRANS_2_UNI |
5-Notice |
Group [chars] transitioned to Unicast Rekey. |
Group has transitioned from using multicast rekey mechanism to unicast mechanism |
ipsec-getvpn |
"Informational message" |
|
GDOI-5-KS_SEND_MCAST_REKEY |
5-Notice |
Sending Multicast Rekey [chars]for group [chars] from address [chars] to [chars] with seq # [dec] spi: 0x[hec][hec][hec][hec] |
Sending Multicast Rekey |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-5-KS_SEND_UNICAST_REKEY |
5-Notice |
Sending Unicast Rekey [chars]for group [chars] from address [chars] with seq # [dec] spi: 0x[hec][hec][hec][hec] |
Sending Unicast Rekey |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-5-KS_USING_DEFAULT_TRANSFORM |
5-Notice |
GETVPN is using default transforms for profile [chars] |
Using default transformset |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-5-LKH_DISABLE |
5-Notice |
LKH disabled in group [chars]. |
LKH has been disabled in a group |
ipsec-getvpn |
- |
|
GDOI-5-LKH_ENABLE |
5-Notice |
LKH enabled in group [chars]. |
LKH has been enabled in a group |
ipsec-getvpn |
- |
|
GDOI-5-POLICY_CHANGE |
5-Notice |
GDOI group [chars] policy has changed. Use 'crypto gdoi ks rekey' to send a rekey or the changes will be send in the next scheduled rekey |
Reminder message that GDOI configuration has changed. |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-5-POLICY_CHANGE_ERROR_MULTIPLE_PORTS |
5-Notice |
Multiple ports detected for ACL [chars] which is not supported. WARNING: No TEK policy will be created. |
Informs user that there is an error in the ACL with regards to the number of ports. |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-5-POLICY_CHANGE_TO_SUITEB |
5-Notice |
Group [chars] changed to Suite-B policy. Use 'crypto gdoi ks rekey' to generate the new Suite-B policy and cause all GMs to re-register to download SIDs or this will happen in the next scheduled rekey |
Migrating from non-Suite-B to Suite-B policy requires that the user issues 'crypto gdoi ks rekey' like any other POLICY_CHANGE but this will cause a re-initialization rather than just a rekey. |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-5-SA_KEK_UPDATED |
5-Notice |
SA KEK was updated 0x%08X%08X%08X%08X |
KEK was updated in the Registration/Rekey and a new KEK SA was created |
ipsec-getvpn |
"Informational message." |
|
GDOI-5-SA_PIP_UPDATED |
5-Notice |
SA PIP was updated 0x[chars] |
PIP was updated in Registration/Rekey and a new PIP SA was created |
ipsec-getvpn |
"Informational message." |
|
GDOI-5-SA_TEK_UPDATED |
5-Notice |
SA TEK was updated |
TEK was updated in the Registration/Rekey and a new TEK IPSEC SA was created |
ipsec-getvpn |
"Informational message." |
|
GDOI-5-TEK_ATD_TIMER_STARTED |
5-Notice |
TEK ATD Timer started for [dec] seconds New TEK will be installed once ATD timer expires |
TEK ATD timer started and new TEK will be installed after atd timer expiry |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-6-COOP_KS_VER_TRANSIT |
6-Information |
Coop KS [chars] protocol version transits from version 1.0.1 to 2.0.0 |
The KS is transitioning to a new version. |
ipsec-getvpn |
LOG_STD_ACTION |
|
GDOI-6-KS_FIRST_GM |
6-Information |
Re-key: First GM [inet] seen by KS in the group [chars]. |
Local key server has received the first group member joining the group |
ipsec-getvpn |
"Informational message." |
|
GDOI-6-KS_LAST_GM |
6-Information |
Re-key: Last GM [inet] left the group [chars]. |
Last group member has left the group on the local key server |
ipsec-getvpn |
"Informational message." |
|
GE_LINK-3-MDIO_ERR |
3-Error |
[chars] error for controller [dec] port [dec] |
Error in accessing GigE Transceiver |
cmts-platform |
"Copy the error message exactly as it appears and report it to your " "technical support" |
|
GE_LINK-3-SW_ERR |
3-Error |
[chars] error in GE pair [dec] port [dec] |
Internal software error |
cmts-platform |
"Copy the error message exactly as it appears and report it to your " "technical support" |
|
GE_LINK-4-SWITCHOVER_ERR |
4-Warning |
switchover to primary port in GE pair is suppressed due to port instability |
- |
cmts-platform |
"check GE link" |
|
GE_LINK-5-AUTONEGOTIATION |
5-Notice |
Waiting for completed A/N in GE pair [dec] primary port |
- |
cmts-platform |
"If persistent check peer GigabitEthernet port" |
|
GE_LINK-5-SWITCHOVER_PRI |
5-Notice |
primary port set active for GE pair [dec] |
GE link is restored for primary port |
cmts-platform |
"if not expected check secondary port in GE pair" |
|
GE_LINK-5-SWITCHOVER_SEC |
5-Notice |
secondary port set active for GE pair [dec] |
GE link is lost for primary port |
cmts-platform |
"if not expected check secondary port in GE pair" |
|
GE_LINK-5-UPDOWN |
5-Notice |
Link status is [chars] for GE pair [dec] port [dec] |
Link Status Change detected for GigE Transceiver |
cmts-platform |
"If not expected check GIGE link" |
|
GE_LINK-6-PHY_EVENT |
6-Information |
PHY [chars] event detected for phy [dec] port [dec] |
Link Event detected for non-SFP port of GigE Transceiver |
cmts-platform |
"Copy the error message exactly as it appears and report it to your " "technical support" |
|
GEN_DB-3-INVALID_CLIENT_TYPE |
3-Error |
[chars]: Invalid client type got [dec] must be between 0 and [dec] |
This message indicates that client type is outside the expected range |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
GEN_DB-3-INVALID_RECORD_KEY |
3-Error |
[chars]: invalid record key * |
This message indicates that the record key is invalid |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
GEN_DB-3-KEY_FUNC_DOESNT_EXIST |
3-Error |
[chars]: Key function does not exist |
This message indicates that key function being considered does not exist in the database definition |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
GEN_DB-3-LIST_FAIL |
3-Error |
[chars]:[chars] |
This message indicates that a list operations such as enqueue dequeu failed |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
GEN_DB-3-LIST_FAIL_FOR_RECORD |
3-Error |
[chars]:[dec]:[chars] |
This message indicates that a list operations such as enqueue dequeu failed |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
GEN_DB-3-NO_KEY_FUNC |
3-Error |
[chars]: [chars][chars] |
This message indicates that key functions are missing from the database handle or key function is a NULL Pointer |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
GEN_DB-3-NULL_DB_HNDL |
3-Error |
NULL Database Handle [chars] |
This message indicates the database handle was NULL |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
GEN_DB-3-NULL_DB_HNDL_ELEMENT |
3-Error |
[chars]: NULL Database Element [chars] |
This message indicates the database handle element was NULL |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
GEN_DB-3-NULL_TREE_NODE |
3-Error |
Node is NULL [chars] |
This message indicates that the tree node being examined is NULL |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
GEN_DB-3-PARSER_INIT_FAIL |
3-Error |
[chars]:[dec]: Parser Could not be initialized |
This message indicates that the IOS Parser command could not be initialized |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
GEN_DB-3-RECORD_DELETE_FAIL |
3-Error |
[chars]:[chars] |
This message indicates that a record could not be deleted |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
GEN_DB-3-UNKNOWN_PARSER_CMD |
3-Error |
[chars]:[dec]: Unknown Parser Command |
This message indicates that the IOS Parser command was not recognized |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
GEN_DB-3-WAVL_FAIL |
3-Error |
[chars]: [chars] |
This message indicates that a wavl tree operation failed |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
GEN_PROXY-3-GPM_ALLOC_FAILED |
3-Error |
GPM allocation for reply failed pak_size [hec] reply_size [hec] |
GPM could not be allocated for reply. |
cpp-ucode |
LOG_STD_ACTION |
|
GEN_PROXY-3-IPC_SEND_FAILED |
3-Error |
IPC send reply failed [chars] |
GEN proxy failed to send of reply to IPC msg. |
cpp-ucode |
LOG_STD_ACTION |
|
GEN_PROXY-3-IPC_UNHANDLED |
3-Error |
failure |
An unknown message type: [dec] was received by the Generic Client Proxy. |
cpp-ucode |
LOG_STD_ACTION |
|
GEN_PROXY-3-REPLY_MSG |
3-Error |
wrong version [dec] |
An incorrect SBS message was received by the Generic Client Proxy. |
cpp-ucode |
LOG_STD_ACTION |
|
GEN_PROXY-3-STACK_ALLOC_FAILED |
3-Error |
Stack allocation for reply failed reply_size [hec] |
Stack space could not be allocated for reply. |
cpp-ucode |
LOG_STD_ACTION |
|
GENERAL-3-LDP |
3-Error |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
GENERAL-3-LDPLIB |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
GENERIC_SUBBLOCK-2-BUILDXDR |
2-Critical |
Failed to build message for GSB: [chars] |
An attempt to build a message for distribution of generic subblock failed |
- |
LOG_STD_ACTION |
|
GENERIC_SUBBLOCK-2-GSBNOTISSUAWARE |
2-Critical |
GSB [chars] is not ISSU aware. Cannot distribute it to ISSU-aware slots |
This GSB is expected to be ISSU aware but it is not. It cannot be distributed safely to ISSU-aware slots as it may not be correctly interpreted |
- |
LOG_STD_ACTION |
|
GENERIC_SUBBLOCK-2-LATE_REGISTER |
2-Critical |
Late registration of GSB type [chars] with id [dec] |
An attempt to register a new generic subblock type was received after subblocks have already been allocated from the control structure with previously registered types |
- |
LOG_STD_ACTION |
|
GENERIC_SUBBLOCK-2-UNPACKXDR |
2-Critical |
Unpacked [dec] bytes and attempted to consume [dec] bytes for GSB: [chars] |
A discrepancy was detected between length of message expected versus length of message received |
- |
LOG_STD_ACTION |
|
GENERIC-3-MPLS_TE_EXT_FWDG |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
GEO_PROXY-3-PROXY_DEBUG_REG_FAILED |
3-Error |
- |
GEO Conditional Debugging registration failed. |
cpp-ucode |
LOG_STD_ACTION |
|
GIGASTACK-1-NO_LOOP_DETECT |
1-Alert |
The link neighbor of link [dec] of Gigastack GBIC in [chars] did not respond to the loop detection request. If loop topology is deployed make sure all switches in the stack are running the latest software.\n |
No acknowledgement for Gigastack loop detection request is received from one of the links on a Gigastack GBIC. Either the neighboring switch does not support Gigastack Loop breaking algorithm or the link between the two Gigastack GBICs is broken. Under this condition a Gigastack loop topology will not be automatically detected and the connectivity between switches in the stack could be lost. |
- |
"If loop topology is used in the Gigastack make sure the latest software is running on all switches in the stack. Check the Gigastack GBICs involved to make sure they are functioning." |
|
GIGASTACK-1-NO_LOOP_DETECT |
1-Alert |
The link neighbor of link [dec] of Gigastack GBIC in [chars] did not respond to the loop detection request. If loop topology is deployed make sure all switches in the stack are running the latest software.\n |
No acknowledgement for Gigastack loop detection request is received from one of the links on a Gigastack GBIC. Either the neighboring switch does not support Gigastack Loop breaking algorithm or the link between the two Gigastack GBICs is broken. Under this condition a Gigastack loop topology will not be automatically detected and the connectivity between switches in the stack could be lost. |
- |
"If loop topology is used in the Gigastack make sure the latest software is running on all switches in the stack. Check the Gigastack GBICs involved to make sure they are functioning." |
|
GIGASTACK-3-INIT_FAILURE |
3-Error |
Gigastack GBIC in [chars] initialization failed. |
Gigastack GBIC failed POST. |
firmware |
"Remove the Gigastack GBIC and re-insert it into the GBIC slot." |
|
GIGASTACK-3-INIT_FAILURE |
3-Error |
Gigastack GBIC in [chars] initialization failed. |
Gigastack GBIC failed POST. |
firmware |
"Remove the Gigastack GBIC and re-insert it into the GBIC slot." |
|
GIGASTACK-6-LOOP_BROKEN |
6-Information |
Link loss is detected in the Gigastack loop \nLink 2 of the Gigastack GBIC in [chars] is re-enabled. |
Loop formed by Gigastack modules is broken because of link loss. Link 2 of the Master Loop Breaker is re-enabled to replace the broken link |
- |
LOG_STD_NO_ACTION |
|
GIGASTACK-6-LOOP_BROKEN |
6-Information |
Link loss is detected in the Gigastack loop \nLink 2 of the Gigastack GBIC in [chars] is re-enabled. |
Loop formed by Gigastack modules is broken because of link loss. Link 2 of the Master Loop Breaker is re-enabled to replace the broken link |
- |
LOG_STD_NO_ACTION |
|
GIGASTACK-6-LOOP_DETECTED |
6-Information |
Gigastack GBIC in [chars] is selected as Master Loop Breaker. \nLink 2 of the Gigastack GBIC is disabled to break the loop. |
Loop is detected in the Gigastack and this Gigastack GBIC is selected as the Master Loop Breaker. Link 2 of this Gigastack GBIC is disabled to break the loop. |
- |
LOG_STD_NO_ACTION |
|
GIGASTACK-6-LOOP_DETECTED |
6-Information |
Gigastack GBIC in [chars] is selected as Master Loop Breaker. \nLink 2 of the Gigastack GBIC is disabled to break the loop. |
Loop is detected in the Gigastack and this Gigastack GBIC is selected as the Master Loop Breaker. Link 2 of this Gigastack GBIC is disabled to break the loop. |
- |
LOG_STD_NO_ACTION |
|
GK_OSP-3-GK_OSP_INIT_NOMEM |
3-Error |
\ Not enough emory to initialize GK_OSP subsystem: [chars]. |
Unable to initialize the gatekeeper OSP subsystem because of low memory conditions. |
- |
"Upgrade memory capacity on the router." |
|
GK_OSP-3-GK_OSP_PARSE_CHAIN_FAIL |
3-Error |
\ Could not install gatekeeper osp CLI. |
An internal error has occured. |
- |
"None. Please report this to customer support." |
|
GK-3-ALTGK_CONFIG_ERROR |
3-Error |
\ An error in the alternate gatekeeper configuration was detected. Remote gatekeeper [chars] claims to be part of zone [chars] |
- |
- |
- |
|
GK-3-ALTGK_CONFIG_ERROR_LOCAL |
3-Error |
\ An alternate gatekeeper indicates an alt-gk configuration error on a local zone.\n |
- |
- |
- |
|
GK-3-CANNOT_TURN_OFF_ATTRIB |
3-Error |
\ Subnet attributes are currently turned ON for\n |
- |
- |
- |
|
GK-3-CONFLICTING_DATA |
3-Error |
\ Static-alias command failed. Endpoint already exists with different [chars].\n Use the \show gatekeeper endpoints\ command to check on existing endp\n\oints. |
- |
- |
- |
|
GK-3-ENDPT_NOT_FOUND |
3-Error |
\ Endpoint not found for specified IP address [inet]. |
- |
- |
- |
|
GK-3-EXCEED_MAX_LOCAL_ZONE_ALLOWED |
3-Error |
\ Exceeded maximum number of local zones [dec] allowed. |
- |
- |
- |
|
GK-3-GK_GUP_INIT_ERROR |
3-Error |
\ An error occurred trying to initialize the Gatekeeper Update Protocol GUP. |
- |
- |
- |
|
GK-3-GK_SRV_LISTEN_FAIL |
3-Error |
\ Failed to open Gatekeeper Server listening socket. |
- |
- |
- |
|
GK-3-GK_TMSG_NOMEM |
3-Error |
\ No memory for gk-server transport message block. |
- |
- |
- |
|
GK-3-GKTMP_SERVER_MARKED_UNUSABLE |
3-Error |
GKTMP Server: [chars][chars] connected to GK: [chars] is marked unusable |
The Gatekeeper has marked a GKTMP server as unusable when flow\n\ control is configured.The reason for this action could be that the\n\ average response time of the GMTMP server is very high or the number\n\ of messages queued to be sent to the GKTMP server is very high. These\n\ conditions could be caused by an overloaded server or a problem with\n\ the TCP connection between the server and the Gatekeeper. |
voice-h323 |
"Check the operational status of of the GKTMP server and the\n\ network link between the server and the Gatekeeper. If both are\n\ operational enter the <CmdBold>show running-config<NoCmdBold> and\n\ <CmdBold>show gatekeeper servers<NoCmdBold> commands and verify\n\ the status of the GKTMP server. Enter the <CmdBold>debug gatekeeper\n\ server<NoCmdBold> on the Gatekeeper to enable debugging on the\n\ gatekeeper server. Gather this information contact your Cisco\n\ technical support representative and provide the representative\n\ with the gathered information." |
|
GK-3-GKTMP_SERVER_OFFLINE |
3-Error |
GKTMP Server: [chars][chars] is disconnected with Gatekeeper: [chars] |
- |
voice-h323 |
"Check the operational status of the Gatekeeper and the GKTMP\n\ server. If both are operational check the TCP connection between\n\ the server and the Gatekeeper. Check the output of the <CmdBold>show\n\ running-config<NoCmdBold> and <CmdBold>show gatekeeper\n\ servers<NoCmdBold> and verify the status of the GKTMP server. Enter\n\ the <CmdBold>debug gatekeeper server<NoCmdBold> command on the\n\ Gatekeeper to enable debugging on the gatekeeper server. Collect\n\ this information contact your Cisco technical support\n\ representative and provide the representative with the gathered\n\ information." |
|
GK-3-GW_PROXY_ADD_COST_FAIL |
3-Error |
\ GW/Proxy add cost failed. Could be out of memory. |
- |
- |
- |
|
GK-3-GW_PROXY_ALIAS_NOT_FOUND |
3-Error |
\ GW/Proxy not found for specified alias name [chars]. |
- |
- |
- |
|
GK-3-GW_PROXY_ENDPT_NOT_FOUND |
3-Error |
\ GW/PROXY may not be registered. Add cost failed. |
- |
- |
- |
|
GK-3-GW_PROXY_IP_NOT_FOUND |
3-Error |
\ GW/Proxy not found for specified IP adddress [inet]. |
- |
- |
- |
|
GK-3-INVALID_GK_CMD |
3-Error |
\ To shutdown Gatekeeper use the \shutdown\ command in the Gatekeeper mode. |
- |
- |
- |
|
GK-3-MSGCB_TIMER_RUNNING |
3-Error |
\ Message CB freed while timer still running: msgcb state=[dec] status=[dec] timer type=[dec] |
- |
- |
- |
|
GK-3-NO_DISC_PORT |
3-Error |
\ Unable to open or bind to gatekeeper discovery port. Bringup failed. |
- |
- |
- |
|
GK-3-NO_RAS_PORT |
3-Error |
\ Unable to open or bind to RAS well-known port. Bringup failed. |
- |
- |
- |
|
GK-3-PARTIAL_STATIC_ALIAS |
3-Error |
\ Not all aliases were successfully created. Use the \show gatekeeper endpt\ command to check on successful aliases. |
- |
- |
- |
|
GK-3-PROC_CB_NOMEM |
3-Error |
\ No memory for process control block. Gatekeeper bringup failed. |
- |
- |
- |
|
GK-3-PROC_EV_NOMEM |
3-Error |
\ No memory for free event queue. Gatekeeper bringup failed. |
- |
- |
- |
|
GK-3-PROC_LRQARRAY_NOMEM |
3-Error |
\ No memory for lrq array. Gatekeeper bringup failed. |
- |
- |
- |
|
GK-3-PROC_MSGCB_NOMEM |
3-Error |
\ No memory for IPC message control block. Gatekeeper bringup failed. |
- |
- |
- |
|
GK-3-PROC_MSGRING_NOMEM |
3-Error |
\ No memory for msgring. Gatekeeper bringup failed. |
- |
- |
- |
|
GK-3-PROC_NOCREAT |
3-Error |
\ Unable to create gatekeeper process. Gatekeeper bringup failed. |
- |
- |
- |
|
GK-3-PROC_NOTDOWN |
3-Error |
\ Invalid state [chars]: bringup is only permitted after shut down. |
- |
- |
- |
|
GK-3-PROC_NOTUP |
3-Error |
\ Invalid state [chars]: shutdown is only permitted after bringup. |
- |
- |
- |
|
GK-3-SHUTDOWN_WITH_CALLS |
3-Error |
\ Cannot shutdown gatekeeper because there are calls in progress. |
- |
- |
- |
|
GK-3-STATIC_ALIAS_FAILED |
3-Error |
\ static-alias command failed. Could not create endpoint in endpoint dbase. |
- |
- |
- |
|
GK-3-STATIC_ALIAS_GW_FAILED |
3-Error |
\ A static endpoint was added into the database but failed to create a gateway.\n |
- |
- |
- |
|
GK-3-SUBNET_FAILED |
3-Error |
\ Failed to add/modify subnet information for specified subnet [inet]/[inet]. |
- |
- |
- |
|
GK-3-SUBNET_NO_ATTRIBUTES |
3-Error |
\ Please specify attribute [default | explicit] for this command. |
- |
- |
- |
|
GK-3-SUBNET_NOT_FOUND |
3-Error |
\ Subnet not found under specified IP address [inet]/[inet]. |
- |
- |
- |
|
GK-3-ZONE_ACTIVE |
3-Error |
\ There are endpoints currently registered in zone [chars]. Zone remove failed |
- |
- |
- |
|
GK-3-ZONE_NOT_FOUND |
3-Error |
\ Zone not found for specified Gatekeeper name [chars]. |
- |
- |
- |
|
GK-4-PROC_NOTALL |
4-Warning |
\ Unable to create more than [dec] gk thread processes. |
- |
- |
- |
|
GK-5-GKTMP_SERVER_MARKED_USABLE |
5-Notice |
GKTMP Server: [chars][chars] connected to GK: [chars] is marked usable |
The Gatekeeper has marked the GKTMP server as usable when flow\n\ control is configured. |
voice-h323 |
LOG_STD_NO_ACTION |
|
GK-5-GKTMP_SERVER_ONLINE |
5-Notice |
GKTMP Server: [chars][chars] is connected with Gatekeeper: [chars] |
A connection between a GKTMP server and a gatekeeper has been\n\ established. The connection establishment could be initiated by\n\ either the Gatekeeper or a GKTMP server. |
voice-h323 |
LOG_STD_NO_ACTION |
|
GK-5-RX_LRQ_PASSWORD_UPDATED |
5-Notice |
\ LRQ receive password for security password-group '[chars]' has been updated. |
The Gatekeeper was configured with a LRQ security password-goup that contained the 'effective' keyword. This keyword allows the user to specify a time at which the requested password is to take effect. The log is displayed to inform the user that the time period has expired and the updated password is now in effect. |
- |
"This log is only for informational purposes. The user should verify " "that all remote zones associated with this password-group are now " "providing the password in its LRQ messages. Failure to do so will " "result in a LRJ containing a reason of invalid_permission." |
|
GK-6-ARQ_ACL_BLOCKED_MSG |
6-Information |
\ AnswerCall ARQ with source IP [chars] was blocked by ARQ access list |
- |
- |
- |
|
GK-6-GK_CLI_RAS_IP_CHANGED |
6-Information |
\ The IP address which\n has been changed was the gatekeeper's configured RAS address.\n Existing RAS clients will no longer be able to reach the gatekeeper.\n |
The IP address being changed at the interface was statically assigned to the gatekeeper for its RAS signaling via the \zone local\ command. This action will automatically replace the gatekeeper's static RAS address with the new IP address. Since the gatekeeper's old RAS address is no longer valid existing clients which have registered to this gatekeeper via the old RAS address will no longer be able to communicate with this gatekeeper. |
- |
"It is the user's responsibility to notify existing RAS clients to " "re-register their systems to the gatekeeper's new RAS address as " "shown in the \"show gatekeeper zone status\" display" |
|
GK-6-GK_CLI_RAS_IP_REMOVED |
6-Information |
\ The IP address which\n has been removed was the gatekeeper's configured RAS address. The\n system will automatically assign a new IP address if available to\n |
The IP address being removed at the interface was statically assigned to the gatekeeper for its RAS signaling via the \zone local\ command. This action will automatically remove the gatekeeper's static RAS address. Since the gatekeeper no longer has a configured RAS address the router will automatically assign an IP address if there is any to the gatekeeper. Existing clients which have registered to |
- |
"It is the user's responsibility to notify existing RAS clients to " "re-register their systems to the gatekeeper's new RAS address as " "shown in the \"show gatekeeper zone status\" display" |
|
GK-6-GK_CLOSE_SRV_CONNECTION |
6-Information |
\ The connection to GKTMP server [chars][inet] appears to be hung |
Messages are being backed up in the gatekeeper's write queue in the connection with the specified server name. The connection is assumed to have gone bad and the gatekeeper is closing the connection. This implies that messages will not be sent to that server for processing until either the gatekeeper or the server re-initiates the connection. |
- |
"Check with the specified server for possible connection error." |
|
GK-6-GK_FLOAT_RAS_IP_CHANGED |
6-Information |
\ The gatekeeper's RAS address\n has been automatically changed by the system. Existing RAS clients\n may no longer be able to reach the gatekeeper.\n |
The IP address being changed at the interface causes the system to look for a better IP address to be used for the gatekeeper's RAS address. existing clients which have registered to this gatekeeper via the old RAS address may no longer be able to communicate with this gatekeeper. |
- |
"It is the user's responsibility to notify existing RAS clients to " "re-register their systems to the gatekeeper's new RAS address as " "shown in the \"show gatekeeper zone status\" display" |
|
GK-6-LRQ_ACL_BLOCKED_MSG |
6-Information |
\ LRQ from IP [chars] was blocked by LRQ access list |
- |
- |
- |
|
GLBP-3-MISCONFIG |
3-Error |
Cannot add MAC address [enet] to interface [chars] - not supported |
A software or hardware error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
GLBP-4-BADAUTH |
4-Warning |
Bad authentication received from [chars] group [dec] |
Two routers participating in a Gateway Load Balancing Protocol group disagree on the valid authentication string. |
- |
"Use the glbp authentication interface command to repair the " "GLBP authentication discrepancy between the local system " "and the one whose IP address is reported." |
|
GLBP-4-BADVIP |
4-Warning |
[chars] Grp [dec] address [chars] is in the wrong subnet for this interface |
The GLBP virtual IP address contained in the Hello message cannot be learnt as it is not within a subnet configured on the interface. |
- |
"Check the configuration on all GLBP routers and ensure " "that the virtual IP address is within a configured subnet." |
|
GLBP-4-DIFFVIP1 |
4-Warning |
[chars] Grp [dec] active routers virtual IP address [chars] is different to the locally configured address [chars] |
The GLBP virtual IP address contained in the Hello message from the Active router is different to that configured locally. |
- |
"Check the configuration on all GLBP routers." |
|
GLBP-4-DUPADDR |
4-Warning |
Duplicate address [chars] on [chars] sourced by [enet] |
The IP address in a GLBP message received on the interface is the same as the router's own IP address. This may be because of misconfiugration or because of a malfunctioning switch |
- |
"Check the configurations on all the GLBP routers and make sure that " "any switches you have are functioning properly." |
|
GLBP-4-DUPVIP1 |
4-Warning |
[chars] Grp [dec] address [chars] is already assigned to [chars] group [dec] |
The GLBP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to a different GLBP group. |
- |
"Check the configuration on all GLBP routers." |
|
GLBP-4-DUPVIP2 |
4-Warning |
[chars] Grp [dec] address [chars] is already assigned on this interface |
The GLBP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to this interface. |
- |
"Check the configuration on all GLBP routers." |
|
GLBP-4-DUPVIP3 |
4-Warning |
[chars] Grp [dec] address [chars] is already assigned to or overlaps with an address on another interface or application |
The GLBP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to or overlaps with an address on another interface or application. |
- |
"Check the configuration on all GLBP routers." |
|
GLBP-6-FWDSTATECHANGE |
6-Information |
[chars] Grp [dec] Fwd [dec] state [chars] -> [chars] |
The GLBP forwarder has changed state |
- |
LOG_STD_NO_ACTION |
|
GLBP-6-STATECHANGE |
6-Information |
[chars] Grp [dec] state [chars] -> [chars] |
The GLBP gateway has changed state |
- |
LOG_STD_NO_ACTION |
|
GMPLS_UNSUPPORTED_RESOURCE-3-MPLS_TE_LM |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
GPRSFLTMG-0-GPRS_DHCP |
0-Emergency |
\ [chars] |
Two reasons for this error message\n\ 1. DHCP Client failed to get started this could be because of malloc\n\ failures.\n\ 2. GPRS DHCP Process failed to start |
gprs |
"If this error message is seen it is recommended not to use this \n\ GGSN for PDP session establishment with SGSN with dynamic IP request.\n\ Check the available memory in the box and for the first reason try \n\ to get 'debug dhcp detail' before the failure.\n\ Contact your technical support representative with the error \n\ message you got." |
|
GPRSFLTMG-0-GPRS_SERVICE |
0-Emergency |
\ GSN: [inet] TID: %08x%08x APN: [chars] Reason: [dec] [chars] |
You get this error messages because of one of the following reasons :\n\ 1. Path fail - No echo message is received from the GSN peer \n\ and time out. \n\ 3. GGSN service up - GGSN service starts.\n\ 4. GGSN service down - GGSN service shutdown.\n\ 5. Primary Charging Gateway down - Primary charging gateway is not \n\ reachable or unconfigured.\n\ 6. Primary Charging Gateway up - Primary Charging gateway is up or \n\ its configured .\n\ 7. Secondary Charging Gateway up - Secondary Charging Gateway is up \n\ or its configured.\n\ 8. Secondary Charging Gateway becomes unreachable or unconfigured. |
gprs |
"Error messages with reasons 36 and 7 are informational.\n\ For error messages with the other reasons contact your technical \n\ supportrepresentative with the error message you got." |
|
GPRSFLTMG-0-GTPv1NORESOURCE |
0-Emergency |
\ GSN: [inet] TEID: [hec] APN: [chars] Reason: [dec] [chars] |
Available resources exhausted to continue GGSN service because of\n\ the following reasons :\n\ 1. Number of pending signaling messages reaches limit.\n\ 2. Out of Memory - Insuffient in GGSN.\n\ 3. System failure - Permenant system failure has occured. |
gprs |
"1. Check whether you can increase number of PDP that can be handled\n\ by GGSN.\n\ If the problem recurs contact your technical support representative\n\ with the error message you got and with the output of\n\ 'show gprs gtp status'." |
|
GPRSFLTMG-0-NOPROCESS |
0-Emergency |
\ [chars] |
A Process could not be started |
- |
"Please contact your technical support representative \n\ with the error message you got and with the output of \n\ 'show gprs gtp status'." |
|
GPRSFLTMG-0-RESOURCE |
0-Emergency |
\ GSN: [inet] TID: %08x%08x APN: [chars] Reason: [dec] [chars] |
Available resources exhausted to continue GGSN service because of \n\ the following reasons :\n\ 1. Number of PDP reaches Limit.\n\ 2. Number of Network Initiated PDP reached percentage - Insuffient \n\ in GGSN.\n\ 3. Number of IP PDP regenerated PPP reaches limit. |
gprs |
"1. Check whether you can increase number of PDP that can be handled \n\ by GGSN.\n\ If the problem recurs contact your technical support representative \n\ with the error message you got and with the output of \n\ 'show gprs gtp status'." |
|
GPRSFLTMG-4-AAAFAIL_PDPACTIVATIONFAIL |
4-Warning |
\ GSN: [inet] TID: %08x%08x APN: [chars] Reason: [dec] [chars] |
A PDP Activation has been failed because of one of the \n\ following reasons: \n\\n\ 1. No RADIUS server present for Authentication - No RADIUS server is \n\ configured or configured RADIUS server is not reachable.\n\ 2. Authentication fail - Authentication failed for invalid username \n\ or password.\n\ 3. Missing PAP/CHAP in non-transparent mode - PAP/CHAP IE is missing in \n\ the packet in non-transparent mode.\n\ 4. Missing username - User name field is not present in the PDP \n\ activation Request sent. |
gprs |
"1. Check whether RADIUS server is configured properly and able to \n\ ping it.\n\ 2. Check whether RADIUS server is configured properly. \n\ For the other reasons copy and save the error message with the output \n\ of 'show running' command. and contact your technical support \n\ representative." |
|
GPRSFLTMG-4-APNRELATEDERROR_PDPACTIVATIONFAIL |
4-Warning |
\ GSN: [inet] TID: %08x%08x APN: [chars] Reason: [dec] [chars] |
PDP activation has failed due to one of the APN related problem :\n\ 1. APN not configured - The APN requested in the PDP Request is not\n\ configured in the GGSN router.\n\ 2. Subscribe mode on APN but selection mode field not verified.\n\ 3. Duplicate static IP address to access same APN.\n\ 4. Session already exists for a different APN. |
gprs |
"Check the APN configuration correspondingly. If that can't solve the \n\ problem get the output of 'sh run' and 'sh gprs access-point all' \n\ copy the error message exactly as it appears and report to your \n\ technical support representative." |
|
GPRSFLTMG-4-CHARGING |
4-Warning |
\ GSN: [inet] TID: %08x%08x APN: [chars] Reason: [dec] [chars] |
You get this syslog message due to one of the following reasons :\n\ 1. Primary/Secondary Charging gateway configured/unconfigured.\n\ 2. GSN GTP' Transfer Failure - Failure in sending CDRs to \n\ Charging gateway configured.\n\ 3. GSN CGF Echo Request Failure/Restored - Failure/Success of \n\ Echo messages sent charging gateway to check the connectivity of \n\ the Charging gateway configured. \n\ 4. GSN CDR Capacity Full/Free - Status of GSN CDR buffer full/free \n\ the subsequent packet might be dropped if the buffer is full.\n\ 5. GSN CDR Discard Notification - a status whether the GSN CDRs are\n\ getting discard/buffered. |
gprs |
"1. This is informational .\n\ 2. Check whether the charging gateways are configured correctly \n\ and are active with the charging functionality. \n\ 3. If the configured charging gateway is up and reachable from the GSN \n\ check whether charging function is enabled in the gateway.\n\ 45. If you have configured "gprs char charging-send-buffer-size" with minimum bytes you may configure maximum bytes.\n\ \n\ If the problem recurs contact your technical support representative \n\ with the error message you got" |
|
GPRSFLTMG-4-GTPv1AAAFAIL_PDPACTIVATIONFAIL |
4-Warning |
\ GSN: [inet] TEID: [hec] APN: [chars] Reason: [dec] [chars] |
A PDP Activation has been failed because of one of the \n\ following reasons: \n\\n\ 1. No RADIUS server present for Authentication - No RADIUS server is \n\ configured or configured RADIUS server is not reachable.\n\ 2. Authentication fail - Authentication failed for invalid username \n\ or password.\n\ 3. Missing PAP/CHAP in non-transparent mode - PAP/CHAP IE is missing in \n\ the packet in non-transparent mode.\n\ 4. Missing username - User name field is not present in the PDP \n\ activation Request sent. |
gprs |
"1. Check whether RADIUS server is configured properly and able to \n\ ping it.\n\ 2. Check whether RADIUS server is configured properly. \n\ For the other reasons copy and save the error message with the output \n\ of 'show running' command. and contact your technical support \n\ representative." |
|
GPRSFLTMG-4-GTPv1APNRELATEDERROR_PDPACTIVATIONFAIL |
4-Warning |
\ GSN: [inet] TEID: [hec] APN: [chars] Reason: [dec] [chars] |
PDP activation has failed due to one of the APN related problem :\n\ 1. APN not configured - The APN requested in the PDP Request is not\n\ configured in the GGSN router.\n\ 2. Subscribe mode on APN but selection mode field not verified.\n\ 3. Duplicate static IP address to access same APN.\n\ 4. Session already exists for a different APN. |
gprs |
"Check the APN configuration correspondingly. If that can't solve the \n\ problem get the output of 'sh run' and 'sh gprs access-point all' \n\ copy the error message exactly as it appears and report to your \n\ technical support representative." |
|
GPRSFLTMG-4-GTPv1IPALLOCATIONFAIL_PDPACTIVATIONFAIL |
4-Warning |
\ GSN: [inet] TEID: [hec] APN: [chars] Reason: [dec] [chars] |
Failed to allocate IP address dynamically because of one of the \n\ following reason:\n\\n\ 1. a. DHCP/RADIUS server IP address has been wrongly configured in GGSN.\n\ b. DHCP/RADIUS server is reachable but the configuration to \n\ allocate IP address might be wrong. or \n\ c. Properly configured DHCP/RADIUS server is unreachable.\n\ 2. Dynamic IP allocation is disabled in the APN configuration .\n\ 3. Missing PAP/CHAP information from radius client in \n\ transparent mode - Username and Password is missing in the \n\ PDP Activation Request. |
gprs |
"1.a. Check whether the GGSN is conifugred with the valid DHCP/RADIUS \n\ server IP address.\n\ b. Check whether DHCP/RADIUS server is configured properly to \n\ allocate IP address .\n\ c. If the configurations are fine then check whether the server \n\ is reachable from GGSN.\n\ 2. Configure IP allocation pool as either DHCP proxy client or RADIUS \n\ client in the APN .\n\ If you could not solve the problem still contact your technical support\n\ representative with the error message you got." |
|
GPRSFLTMG-4-GTPv1MOBILITY |
4-Warning |
GSN: [inet] TEID: [hec] APN: [chars] Reason: [dec] [chars] |
One of the following Mobility Related problem has occured :\n\ 1. MS GPRS Detached.\n\ 2. MS GPRS present.\n\ 3. MS not GPRS responding for network initiated PDP - MS does not \n\ respond for packets initiated by external network. \n\ 4. MS Refused for network initiated PDP.\n\ 5. IMSI unknown for network initiated PDP. |
gprs |
"If the problem recurs contact your technical support representative\n\ with the error message you got " |
|
GPRSFLTMG-4-GTPv1QOSFAIL_PDPACTIVATIONFAIL |
4-Warning |
\ GSN: [inet] TEID: [hec] APN: [chars] Reason: [dec] [chars] |
QoS negotitaion/update has failed since resources not available. |
gprs |
"Contact your technical support representative with the error messages \n\ and the output of command 'sh gprs gtp status' ." |
|
GPRSFLTMG-4-IPALLOCATIONFAIL_PDPACTIVATIONFAIL |
4-Warning |
\ GSN: [inet] TID: %08x%08x APN: [chars] Reason: [dec] [chars] |
Failed to allocate IP address dynamically because of one of the \n\ following reason:\n\\n\ 1. a. DHCP/RADIUS server IP address has been wrongly configured in GGSN.\n\ b. DHCP/RADIUS server is reachable but the configuration to \n\ allocate IP address might be wrong. or \n\ c. Properly configured DHCP/RADIUS server is unreachable.\n\ 2. Dynamic IP allocation is disabled in the APN configuration .\n\ 3. Missing PAP/CHAP information from radius client in \n\ transparent mode - Username and Password is missing in the \n\ PDP Activation Request. |
gprs |
"1.a. Check whether the GGSN is conifugred with the valid DHCP/RADIUS \n\ server IP address.\n\ b. Check whether DHCP/RADIUS server is configured properly to \n\ allocate IP address .\n\ c. If the configurations are fine then check whether the server \n\ is reachable from GGSN.\n\ 2. Configure IP allocation pool as either DHCP proxy client or RADIUS \n\ client in the APN .\n\ If you could not solve the problem still contact your technical support\n\ representative with the error message you got." |
|
GPRSFLTMG-4-MOBILITY |
4-Warning |
\ GSN: [inet] TID: %08x%08x APN: [chars] Username: [chars] Reason: [dec] [chars] |
One of the following Mobility Related problem has occured :\n\ 1. MS GPRS Detached.\n\ 2. MS GPRS present.\n\ 3. MS not GPRS responding for network initiated PDP - MS does not \n\ respond for packets initiated by external network. \n\ 4. MS Refused for network initiated PDP.\n\ 5. IMSI unknown for network initiated PDP. |
gprs |
"If the problem recurs contact your technical support representative\n\ with the error message you got " |
|
GPRSFLTMG-4-QOSFAIL_PDPACTIVATIONFAIL |
4-Warning |
\ GSN: [inet] TID: %08x%08x APN: [chars] Reason: [dec] [chars] |
QoS negotitaion/update has failed since resources not available. |
gprs |
"Contact your technical support representative with the error messages \n\ and the output of command 'sh gprs gtp status' ." |
|
GPS_DR-0-MODULE_FAIL_AUTHENTICATION |
0-Emergency |
Failed to authenticate the GPS/DR module: [chars] return code 0x[hec]. |
Failed to authenticate the GPS/DR module. |
TAMPER_COMPONENT |
LOG_STD_ACTION |
|
GPS_DR-0-MODULE_FAIL_INIT |
0-Emergency |
Failed to initialize the GPS/DR module. |
Failed to initialize the GPS/DR module. |
- |
LOG_STD_ACTION |
|
GR_IOS_DB-3-DB_EXIST |
3-Error |
Persist DB [chars][dec] not deleted!!!\n |
GR_IOS_DB was not deleted from boot flash! |
- |
GR_IOS_DB_ERR_ACTION |
|
GR_IOS_DB-3-OPEN_DB |
3-Error |
Failed to open path: [chars] handle: 0x[hec] err: [chars] [dec]\n |
Failed to open GR_IOS_DB database |
- |
GR_IOS_DB_ERR_ACTION |
|
GR_IOS_DB-3-PATH_FAILED |
3-Error |
Failed to get database path for [chars]\n |
Failed to get database path. |
- |
GR_IOS_DB_ERR_ACTION |
|
GR_IOS_DB-3-VFT_SET |
3-Error |
Failed to set VFT path: [chars] handle: 0x[hec] err: [chars] [dec]\n |
Failed to set VFT for GR_IOS_DB database |
- |
GR_IOS_DB_ERR_ACTION |
|
GR_VRF_TOPO-3-TOPO_DEL |
3-Error |
Failed to delete Topology record 0x[hec] number: [dec] |
Failed to delete topology mapping entry. |
- |
GR_IOS_DB_ERR_ACTION |
|
GR_VRF_TOPO-3-TOPO_GET |
3-Error |
Failed to get vrf_id: 0x[hec] afi: [dec] topology: [chars] topo_id: 0x[hec] err: [chars] [dec]\n |
Failed to get topology mapping entry. |
- |
GR_IOS_DB_ERR_ACTION |
|
GR_VRF_TOPO-3-TOPO_SET |
3-Error |
Failed to set vrf_id: 0x[hec] afi: [dec] topology: [chars] topo_id: 0x[hec] err: [chars] [dec]\n |
Failed to set topology mapping entry. |
- |
GR_IOS_DB_ERR_ACTION |
|
GR_VRF_TOPO-3-TOPO_TBL_FREE |
3-Error |
Failed to free topology table err: [chars] [dec]\n |
Failed to free topology mapping table. |
- |
GR_IOS_DB_ERR_ACTION |
|
GR_VRF_TOPO-3-TOPO_TBL_OPEN |
3-Error |
Failed to open table type: [dec] root: 0x[hec] err: [chars] [dec]\n |
Failed to open topology mapping table. |
- |
GR_IOS_DB_ERR_ACTION |
|
GR_VRF_TOPO-3-VRF_DEL |
3-Error |
Failed to delete VRF record 0x[hec] number: [dec] |
Failed to delete VRF mapping entry. |
- |
GR_IOS_DB_ERR_ACTION |
|
GR_VRF_TOPO-3-VRF_GET |
3-Error |
Failed to get vrf_name: [chars] vrf_id: 0x[hec] err: [chars] [dec]\n |
Failed to get VRF mapping entry. |
- |
GR_IOS_DB_ERR_ACTION |
|
GR_VRF_TOPO-3-VRF_SET |
3-Error |
Failed to set vrf_name: [chars] vrf_id: 0x[hec] err: [chars] [dec]\n |
Failed to set VRF mapping entry. |
- |
GR_IOS_DB_ERR_ACTION |
|
GR_VRF_TOPO-3-VRF_TBL_FREE |
3-Error |
Failed to free VRF table err: [chars] [dec]\n |
Failed to free VRF mapping table. |
- |
GR_IOS_DB_ERR_ACTION |
|
GR_VRF_TOPO-3-VRF_TBL_OPEN |
3-Error |
Failed to open table type: [dec] root: 0x[hec] err: [chars] [dec]\n |
Failed to open VRF mapping table. |
- |
GR_IOS_DB_ERR_ACTION |
|
GR-5-LDP |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
GRIP-2-BADROUTE |
2-Critical |
Error [chars] route - null table |
A hardware or software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
GRIP-3-BADPATHS |
3-Error |
Invalid number of paths [dec] for %q |
An internal inconsistency was detected in the XNS routing table\n\ structure. |
- |
"Note the parameters associated with this message and call your\n\ technical support representative for assistance." |
|
GROUP_POLICY-2-STEERING_ACE_FAILED |
2-Critical |
Failed to [chars][chars] steering policy '[chars]' for SGT=[chars] due to ACE '[chars]' error. Download will be retried in 60 seconds |
An error occurred in the ACE while GPP attempted to acquire steering policy from the policy server. Retry will be attempted in 60 seconds |
- |
LOG_STD_ACTION |
|
GROUP_POLICY-3-STEERING_INSTALL_FAILED |
3-Error |
Failed to [chars][chars] steering policy [chars] for SGT=[chars] |
An error occurred while GPP attempted to acquire steering policy from the policy server. |
- |
LOG_STD_ACTION |
|
GROUP_POLICY-3-STEERING_PEER_DOWNLOAD_FAILED |
3-Error |
Failed to download peer policy for [chars] |
An error occurred while GPP attempted to acquire peer policy from the policy server |
- |
LOG_STD_ACTION |
|
GROUP_POLICY-3-STEERING_POLICY_DEFN_DEL_FAILED |
3-Error |
Failed to delete steering policy definition. Invalid steering policy [chars]. |
An error occurred while GPP attempted to delete steering policy info with invalid handle. |
- |
LOG_STD_ACTION |
|
GROUP_POLICY-3-STEERING_POLICY_DEFN_INFO_STALE |
3-Error |
Steering policy definition is not valid. |
An error occurred while GPP attempted to access steering policy definition with invalid handle. |
- |
LOG_STD_ACTION |
|
GROUP_POLICY-3-STEERING_POLICY_DEFN_LIST_STALE |
3-Error |
Steering policy named list having policy definition is not valid. |
An error occurred while GPP attempted to access steering policy list with invalid handle. |
- |
LOG_STD_ACTION |
|
GROUP_POLICY-3-STEERING_POLICY_SERVER_ENCRYPT_FAILURE |
3-Error |
GPP policy-server password encryption failed |
GPP policy-server password encryption failed |
- |
LOG_STD_ACTION |
|
GROUP_POLICY-3-STEERING_POLICY_SERVER_INVALID_CREDENTIALS |
3-Error |
Invalid policy-server credentials have configured on device OR Server port number is incorrect |
GPP policy-server username or password are invalid |
- |
LOG_STD_ACTION |
|
GROUP_POLICY-3-STEERING_SESSION_UNINST_FAILED |
3-Error |
Failed to detach session handle from steering policy list for sgt[chars] |
- |
- |
- |
|
GROUP_POLICY-3-STEERING_SGT_POLICY_STALE |
3-Error |
Steering policy for sgt '[chars]' is not valid. |
An error occurred while GPP attempted to access sgt policy with invalid handle. |
- |
LOG_STD_ACTION |
|
GROUP_POLICY-3-STEERING_SM_FAILED |
3-Error |
Failed to start the entry state machine to start policy acquisition for name[chars] |
- |
- |
- |
|
GROUP_POLICY-3-STEERING_SYNC_FAILED |
3-Error |
Failed to send [chars] sync msg[chars] to Standby |
An error occcured while GPP is performing a sync to the Standby. |
- |
LOG_STD_ACTION |
|
GROUP_POLICY-3-STEERING_TREE_MAP_INSERT_FAILED |
3-Error |
Failed to insert the entry info into tree map for name[chars] |
- |
- |
- |
|
GROUP_POLICY-6-STEERING_ATTACH_SUCCESS |
6-Information |
Successfully attached steering policy to PDM for sgt[chars]:[chars] |
- |
- |
- |
|
GROUP_POLICY-6-STEERING_POLICY_DEFN_UPDATE |
6-Information |
Steering policy definition[chars]-[chars] updated to new definition[chars]-[chars] |
- |
- |
- |
|
GSMAMRNB_ENABLER-3-GSMAMRNB_LICENSE_EULA_NOT_ACCEPTED |
3-Error |
\n********************************************************* \ \nWARNING: GSM AMR-NB License is not yet activated. \ \nPlease configure 'license feature gsmamrnb-codec-pack'\ \nand accept the EULA to activate the license. \ \n*********************************************************\n |
EULA is not accepted for the license |
ios-licensing-atg |
LOG_STD_ACTION |
|
GT64010-1-DMASTALL |
1-Alert |
DMA interrupt stalled restarted engine [dec] |
The driver timed out waiting for completion of DMA task. \n\ The DMA engine has been restarted. |
- |
LOG_STD_RECUR_ACTION |
|
GT64010-3-DMA |
3-Error |
Interrupt error c=[hex] m=[hex] rc=[hex] |
An unexpected interrupt was registered from a DMA \n\ engine that was not initialized by software. |
- |
LOG_STD_ACTION |
|
GT64010-3-NOCHANNEL |
3-Error |
Referencing unused DMA channel [dec] |
An access to an uninitialized DMA engine was attempted. |
- |
LOG_STD_ACTION |
|
GT64010-3-TIMER |
3-Error |
Interrupt error c=[hex] m=[hex] rc=[hex] |
An unexpected timer interrupt was received from\n\ a timer element that was not initialized by software. |
- |
LOG_STD_ACTION |
|
GT64010-3-TIMERINSTALL |
3-Error |
Attempt to install already installed timer [dec] |
An attempt was made to initialize a timer element that\n\ is already in use. |
- |
LOG_STD_ACTION |
|
GTP_AIC-3-CHUNK_CREATE_FAIL |
3-Error |
- |
This message indicates that the packet is dropped by GTP AIC. |
cpp-ucode |
"This message is for informational purposed only but may indicate " "a security problem." |
|
GTP-0-GTPv1PACKETPARSINGERROR |
0-Emergency |
\ GSN: [inet] TEID: [hec] APN: [chars] Reason: [chars] |
A PDP context activation failed at the packet parsing state for one\n\ of the following reasons:\n\ 1. Mandatory IE is missing in the PDP .\n\ 2. Mandatory IE incorrect - Mandatory IE has invalid range of value.\n\ 3. Mandatory IE out of sequence - The Mandatory IEs are not in sequence.\n\ 4. Invalid message format.\n\ 5. Optional IE incorrect - Optional IE present in the packet has\n\ invalid range of value.\n\ 6. Version not support - The GGSN Node does not support the GTP\n\ version recieved.\n\ 7. Non-charging msg in charging path.\n\ 8. Charging msg in GTP path.\n\ 9. Unknown GTP message.\n\ 10.Message too short - GTP message received is too short to contain\n\ all expected inform IE.\n\ 11.Unexpected message seen. |
gprs |
"Copy the error message exactly as it appears and report to your\n\ technical support representative." |
|
GTP-0-NORESOURCE |
0-Emergency |
\ GSN: [inet] TID: [hec][hec] APN: [chars] Reason: [chars] |
Available resources exhausted to continue GGSN service because of\n\ the following reasons :\n\ 1. Number of pending signaling messages reaches limit.\n\ 2. Out of Memory - Insuffient in GGSN.\n\ 3. System failure - Permenant system failure has occured. |
gprs |
"1. Check whether you can increase number of PDP that can be handled\n\ by GGSN.\n\ If the problem recurs contact your technical support representative\n\ with the error message you got and with the output of\n\ 'show gprs gtp status'." |
|
GTP-0-PACKETPARSINGERROR |
0-Emergency |
\ GSN: [inet] TID: [hec][hec] APN: [chars] Reason: [chars] |
A PDP context activation failed at the packet parsing state for one\n\ of the following reasons:\n\ 1. Mandatory IE is missing in the PDP .\n\ 2. Mandatory IE incorrect - Mandatory IE has invalid range of value.\n\ 3. Mandatory IE out of sequence - The Mandatory IEs are not in sequence.\n\ 4. Invalid message format.\n\ 5. Optional IE incorrect - Optional IE present in the packet has\n\ invalid range of value.\n\ 6. Version not support - The GGSN Node does not support the GTP\n\ version recieved.\n\ 7. Non-charging msg in charging path.\n\ 8. Charging msg in GTP path.\n\ 9. Unknown GTP message.\n\ 10.Message too short - GTP message received is too short to contain\n\ all expected inform IE.\n\ 11.Unexpected message seen. |
gprs |
"Copy the error message exactly as it appears and report to your\n\ technical support representative." |
|
GTP-2-GSNSERVICEUPDOWN |
2-Critical |
GSN service [chars] changed state to [chars] |
SGSN service starts or shutdown |
gprs |
"If this message recurs contact your technical support representative." |
|
GTP-2-GTPv1PDPACTIVATIONFAIL |
2-Critical |
GTP PDP activation/update failed GSN: [inet] TEID: [hec] Reason: [chars] |
A PDP context activation failed |
gprs |
"If this message recurs contact your technical support representative." |
|
GTP-2-PDPACTIVATIONFAIL |
2-Critical |
GTP PDP activation/update failed GSN: [inet] TID: [hec][hec] Reason: [chars] |
A PDP context activation failed |
gprs |
"If this message recurs contact your technical support representative." |
|
GTP-3-INCOMPLETECONFIG |
3-Error |
\ APN: [chars] Reason: [chars] |
A required configuration is missing |
gprs |
"Please make sure the missing commands are configured" |
|
GTP-4-RECOVERYIEDIFF |
4-Warning |
\ GSN: [inet] TID: [hec][hec] APN: [chars] Reason: [chars] |
GGSN has recieved PDP update request with different Recovery\n\ Information Element in the same path. |
gprs |
"Contact your technical support representative with the error messages\n\ you got." |
|
GTP-6-PDP_PURGED |
6-Information |
\ GSN: [inet] TID: [hec][hec] APN: [chars] Reason: [chars] |
PDP context purged because of PDP context idle timeout |
- |
"This is purely informational " |
|
GULF2488-3-INITERR |
3-Error |
gulf2488 chip initialization failed errcode=[dec]: [chars] |
required resources unavailable. |
osm-choc-ds3 |
"Reinsert the linecard. If still fails do\n\ 'test cwtlc show seeprom red' swap hardware and\n\ Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
GULF2488-3-PROVERR |
3-Error |
gulf2488 channel provisioning failed slice:[dec] ch:[dec]: [chars] |
required resources unavailable. |
osm-choc-ds3 |
LOG_STD_ACTION |
|
GULF2488-3-UNPROVERR |
3-Error |
gulf2488 channel unprovisioning failed slice:[dec] ch:[dec]: [chars] |
required resources unavailable. |
osm-choc-ds3 |
LOG_STD_ACTION |
|
GVRP-3-ADD_REGISTRY_FAILED |
3-Error |
GVRP subsystem fails to add callback function [chars] |
Other subsystem must have mistakenly add its own callback functions. This syslog is for debugging purpose. |
gvrp |
LOG_STD_NO_ACTION |
|
GVRP-3-ENABLE_FAILED |
3-Error |
GVRP can't be enabled because [chars] |
GVRP can't be enabled for some reason. |
gvrp |
"Action may be taken according to the given " "reason. If for instance the problem is " "due to lack of memory the user should " "add more memory to his system." |
|
GVRP-3-HA_INIT_FAILED |
3-Error |
GVRP High Availability subsystem fails to be initialized and hence GVRP won't support HA stateful switchover. |
Either GVRP CF client or GVRP RF client fails to be initialized. |
gvrp |
"Enter the " "<CmdBold>show redundancy clients<NoCmdBold> " "and <CmdBold>show checkpoint clients<NoCmdBold> to " "find out which client is not initialized." |
|
GVRP-3-SUBSYS_INIT_FAILED |
3-Error |
GVRP subsystem failed in initialization[chars] and GVRP won't |
This is extremely unlikely to occur on a customer device. If it does occur the cause is most likely due to the lack of memory so the software failed to create data structures. User should see many |
gvrp |
"Most likely the system has crashed by then " "if the problem is due to lack of memory. " "If the system miraculously came up then" "user can run <CmdBold>show memory summary" "<NoCmdBold> to check the memory usage. " "Please contact the TAC with the output of " "<CmdBold>show memory summary<NoCmdBold> " "<CmdBold>show version<NoCmdBold> and " "<CmdBold>show run<NoCmdBold> and the " "associated syslog messages from the time " "of the problem." |
|
GVRP-6-MODECHANGE |
6-Information |
The operating mode is changed to [chars] mode on interface [chars]. |
As a result of protocol negotiation the operating mode changed to the specified mode on the specified interface. |
gvrp |
LOG_STD_NO_ACTION |
|
H323_ALG-3-CHUNK_CREATE_FAIL |
3-Error |
- |
Chunk create failed. H323 ALG will not be able to finish initialization. |
cpp-ucode |
LOG_STD_ACTION |
|
H323_ALG-3-CHUNK_MEM_LEAK |
3-Error |
- |
Chunk memory is not being freed by H.323 ALG. |
cpp-ucode |
LOG_STD_ACTION |
|
HA_CLIENT-3-BS_TO_STBY_FAILED |
3-Error |
The [chars] HA client's Bulk Sync phase was unsuccessful |
The nominated HA client could not get a buffer from the Checkpointing Facility CF in which to put some checkpointing |
as5850-redundancy |
LOG_STD_ACTION |
|
HA_CLIENT-3-CF_REG_FAILED |
3-Error |
CF registration for the [chars] HA client failed with return code [dec] |
The specified HA client failed to register properly with the Checkpointing Facility CF. This should not happen and suggests |
as5850-redundancy |
LOG_STD_ACTION |
|
HA_CLIENT-3-CLIENT_INIT_FAILED |
3-Error |
Initialisation of the [chars] HA client failed required fields missing |
The HA client utilities code could not initialise the specified client because some fields required by the utilities code were not provided by the client. This should not happen and suggests a software problem. |
as5850-redundancy |
LOG_STD_ACTION |
|
HA_CLIENT-3-CP_TO_STBY_FAILED |
3-Error |
Delivery of a checkpointing CP message from the [chars] HA client failed |
The nominated HA client on the Active unit was told by the Checkpointing Facility CF that one of its checkpointing messages |
as5850-redundancy |
LOG_STD_ACTION |
|
HA_CLIENT-3-IF_INDEX_ADD_FAILURE |
3-Error |
Unable to add an interface index to a table: [chars] rc=[dec] |
The interface index could not be added to a table. This should not normally happen and should be reported. |
as5850-redundancy |
LOG_STD_ACTION |
|
HA_CLIENT-3-NO_BS_PROCESS |
3-Error |
The [chars] HA client failed to create a Bulk Sync process rc [dec] |
The nominated HA client could not create an IOS process that it needed in order to perform its Bulk Sync. This means the client's Bulk Sync did not occur. Hence the Standby unit is now out-of-sync. This should not occur and should be reported. |
as5850-redundancy |
LOG_STD_ACTION |
|
HA_CLIENT-3-NO_RF_BUFFER |
3-Error |
The [chars] HA client failed to get a buffer len=[dec] from RF |
- |
- |
- |
|
HA_CLIENT-3-PROTO_VER_INCOMPAT |
3-Error |
The HA client '[chars]' is incompatible with the peer |
The named HA client can not communicate with the client on the peer unit. These units can not be used in a warm or hot standby environment. |
as5850-redundancy |
LOG_STD_ACTION |
|
HA_CLIENT-3-RF_MSG_NOT_SENT |
3-Error |
Delivery of an RF message from the [chars] HA client failed rc=[dec] |
The nominated HA client was told by the Redundancy Facility RF |
as5850-redundancy |
LOG_STD_ACTION |
|
HA_CLIENT-3-RF_REG_FAILED |
3-Error |
RF registration for the [chars] HA client failed with return code [dec] |
The specified HA client failed to register properly with the Redundancy Facility RF. This should not happen and suggests |
as5850-redundancy |
LOG_STD_ACTION |
|
HA_CLIENT-3-VALIDITY_CHECK_FAILURE |
3-Error |
The HA client detected a validity check failure: [chars] |
The HA client performed a validity check. This check failed and may indicate a serious problem. A reload may be required to recover from this situation |
as5850-redundancy |
LOG_STD_ACTION |
|
HA_CLIENT-4-CF_NOT_BUNDLED |
4-Warning |
CF failed to go into bundled mode for the [chars] HA client rc [dec] |
The Checkpointing Facility CF did not allow the specified HA |
as5850-redundancy |
LOG_STD_ACTION |
|
HA_CLIENT-4-IF_INDEX_LOOKUP_FAILURE |
4-Warning |
Unable to find an interface index: rc=[dec] [chars] |
The interface index could not be found. This is a rare but possible situation and it should be able to correct itself. |
as5850-redundancy |
LOG_STD_NO_ACTION |
|
HA_CLIENT-4-RESOURCE_RECOVERY_LIST_FAILURE |
4-Warning |
Failed to create [chars] resource recovery list |
The specified resource recovery list could not be created. This means resource recovery cannot be performed upon switchover which will most likely leave some of the relevant resources unusable. This should not normally happen and should be reported. |
as5850-redundancy |
LOG_STD_ACTION |
|
HA_CONFIG_SYNC-3-BOOTVAR |
3-Error |
Cannot communicate boot variable to standby [chars] |
Active failed to send the boot variable specified to standby. A reload or a switchover operation will likely result in the standby booting a wrong image. |
config-sync |
LOG_STD_ACTION |
|
HA_CONFIG_SYNC -3-BULK_CFGSYNC |
3-Error |
[chars] |
Bulk config sync failure the reason for the failure will be provided in the string |
config-sync |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
HA_CONFIG_SYNC-3-CONFREG |
3-Error |
Cannot communicate config register to standby |
Active failed to send the config register to standby. The active and standby supervisors won't have the same config registers. |
config-sync |
LOG_STD_ACTION |
|
HA_CONFIG_SYNC -3-FS_BULK_CFGSYNC |
3-Error |
[chars] [[chars]] |
Bulk config sync filesys failure the reason for the failure will be provided in the string |
config-sync |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
HA_CONFIG_SYNC -3-GENERAL |
3-Error |
[chars] |
General Config Sync Problem |
config-sync |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
HA_CONFIG_SYNC -3-IPC |
3-Error |
IPC operation failed for [ [chars] ] with error code [ [chars] ] |
A config sync error occurred. The details about\n\ what was attempted and what went wrong will be printed. |
config-sync |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
HA_CONFIG_SYNC -3-ISSU_MTU |
3-Error |
CONFIG SYNC Failed to get MTU Size for session[[dec]] msg_type[[dec]] MTU[[dec]] rc[[dec]] |
An ISSU Config Sync failed to get Messge MTU. The details about\n\ what was attempted and what went wrong will be printed. |
config-sync |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
HA_CONFIG_SYNC -3-ISSU_REG |
3-Error |
[chars] with error code [ [chars] ] |
An ISSU Config Sync Registration Error occurred. The details about\n\ what was attempted and what went wrong will be printed. |
config-sync |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
HA_CONFIG_SYNC -3-ISSU_XFORM |
3-Error |
CONFIG SYNC [chars] msg_type[[dec]] rc[[dec]] |
An ISSU Config Sync failed to transform messge. The details about\n\ what was attempted and what went wrong will be printed. |
config-sync |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
HA_CONFIG_SYNC -3-LBL_CFGSYNC |
3-Error |
[chars] |
Line by Line sync failure what was attempted and what went wrong \n\ will be printed. |
config-sync |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
HA_CONFIG_SYNC -3-LBL_POLICY |
3-Error |
[chars] |
Active and Standby configuration out of sync LBL\n\ what was attempted and what went wrong will be printed. |
config-sync |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
HA_CONFIG_SYNC -6-BULK_CFGSYNC_SUCCEED |
6-Information |
Bulk Sync succeeded |
Bulk Sync has succeeded |
config-sync |
"No action necessary" |
|
HA_CONFIG_SYNC -6-LBL_PRC_SUBCODE |
6-Information |
CONFIG SYNC : Subcode not matching for command [chars] Active subcode[0x[hec]] Standby subcode[0x[hec]] |
The line by line synchronization of a command has succeeded. A command entered on the active system was successfully synchronized with the standby system. However the sub code of Parser Return Code that were returned by the Active and Standby systems were different. However the sub code of Parser Return Code that were returned by the Active and Standby systems where different. |
config-sync |
"Normally no action is required. If however any " "problems with line by line synchronization are found " "copy this message exactly as it appears on the console " "or in the system log and contact your Cisco technical " "support representative." |
|
HA_EM-3-ACTION_CNS_OPEN_FAIL |
3-Error |
[chars]: Unable to open connection to CNS Event Agent: [dec] |
The CNS Action process failed to open CNS handle to Event Agent. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMC_CBH_PROCESS_CREATE |
3-Error |
[chars]: callback handler process create failed for eid: [dec] |
The process_create function reported an error trying to create the callback handler process. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMC_FH_INIT |
3-Error |
[chars]: fh_init failed : [dec] |
The strdup function reported an error. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMFD_EMPTY_QUEUE |
3-Error |
[chars]: The [chars] event detector I/O queue empty. |
The SNMP message failed to be created |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMFD_OID_UNAVAIL |
3-Error |
[chars]: The following oid has become unavailable: [chars] |
The enqueue function reported an error. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMFD_SNMP_MIB_OBJ_REP_FAIL |
3-Error |
[chars]: SNMP MIB object info replace failed [dec] |
The SNMP MIB object info replace function has failed. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMFD_SNMP_OBJECT_UNKNOWN_RESPONSE_CODE |
3-Error |
[chars]: Unknown SNMP object response code [dec] |
The SNMP MIB object response code is unknown. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMFD_TTY_NUM |
3-Error |
[chars]: Error occurred while fetching TTY number. |
The Embedded Event Manager failed to fetch a TTY number. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMPD_ACTION |
3-Error |
[chars]: Error occurred while performing action: [chars]. |
The Embedded Event Manager Policy Director failed to perform an action for the registered event. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMPD_ACTION_INFO |
3-Error |
[chars]: Error occurred while fetching action information: [dec]. |
The Embedded Event Manager applet attempted to set the state of a tracking object that does not exist. |
ha/eem |
"Only set the state of tracking objects that have already been " "configured in the system. If the " "message continues to occur copy the message exactly as it appears " "and report it your technical support representative." |
|
HA_EM-3-FMPD_CHECKSUM_MISMATCH |
3-Error |
[chars]: file checksum mismatch |
The checksum value of an installed policy does not match the value provided by the installation manager. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMPD_CLI_CONNECT |
3-Error |
Unable to establish CLI session: [chars] |
Unable to establish CLI session. |
ha/eem |
"" |
|
HA_EM-3-FMPD_CLI_DISCONNECT |
3-Error |
Error disconnecting from CLI session: [chars] |
An error occurred while disconnecting from the CLI session. |
ha/eem |
"" |
|
HA_EM-3-FMPD_CLI_NOTTY |
3-Error |
Error attempting to access an unopened CLI session: [chars] |
An error occurred attempting to access an unopened CLI session: [chars] |
ha/eem |
"" |
|
HA_EM-3-FMPD_CLI_READ |
3-Error |
Unable to read CLI response: [chars] |
Unable to read CLI response. |
ha/eem |
"" |
|
HA_EM-3-FMPD_CLI_WRITE |
3-Error |
Unable to send CLI command: [chars] |
Unable to send CLI command. |
ha/eem |
"" |
|
HA_EM-3-FMPD_ERROR |
3-Error |
Error executing applet [chars] statement [chars] |
The Embedded Event Manager policy director found an error when processing an applet. |
ha/eem |
"Check syntax of applet statement. If the " "message continues to occur copy the message exactly as it appears " "and report it your technical support representative." |
|
HA_EM-3-FMPD_EXECUTE_CALLBACK |
3-Error |
[chars]: failed to execute callback |
Failed to execute callback routine. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMPD_FH_INIT |
3-Error |
[chars]: could not initialize Embedded Event Manager service: [chars] |
An internal error was detected when initializing Embedded Event Manager service. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMPD_IPC_PORT_CREATE |
3-Error |
[chars]: failed to create an IPC port: [chars] |
Embedded Event Manager failed to create an IPC port. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMPD_IPC_PORT_OPEN |
3-Error |
[chars]: failed to open an IPC port: [chars] |
Embedded Event Manager failed to open an IPC port. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMPD_IPC_PORT_REGISTER |
3-Error |
[chars]: failed to register an IPC port: [chars] |
Embedded Event Manager failed to register an IPC port. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMPD_NO_PROC |
3-Error |
[chars]: Failed to create process |
The process create function reports an error |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMPD_NOEID |
3-Error |
[chars]: No such event id found. |
An internal software error occurred. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMPD_NOESID |
3-Error |
[chars]: No such event spec id found. |
The Embedded Event Manager Policy Director could not find the event for the event spec. ID. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMPD_PROCESS_XML |
3-Error |
[chars]: error processing xml buffer |
An error occurred processing the event publish information xml buffer. |
ha/eem |
"Copy the message exactly as it appears and report it your technical\n\ support representative." |
|
HA_EM-3-FMPD_QUEUE_INIT |
3-Error |
[chars]: could not initialize queue |
An internal error was detected when initializing Embedded Event Manager queue. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMPD_REQINFO |
3-Error |
[chars]: Error attempting to fetch event information: [chars]. |
The Embedded Event Manager Policy Director failed to receive event info for a callback. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMPD_SET_INFO |
3-Error |
[chars]: Error occurred while fetching variable information: [dec]. |
The Embedded Event Manager Policy Director was unable to set the variable with the requested information. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMPD_SMTP |
3-Error |
Error occurred when sending mail to SMTP server: [chars] : [chars] |
An unexpected error occurred when sending mail to SMTP server. |
ha/eem |
"" |
|
HA_EM-3-FMPD_SMTP_SEND |
3-Error |
Unable to send notification using all SMTP servers |
An unexpected error occurred when sending mail to all SMTP servers. |
ha/eem |
"" |
|
HA_EM-3-FMPD_UNKNOWN_ENV |
3-Error |
[chars]: could not find environment variable: [chars] |
The Embedded Event Manager policy director could not find the environment variable specified in the action message. |
ha/eem |
"Only use well known Embedded Event Manager environment variables. If the " "message continues to occur copy the message exactly as it appears " "and report it your technical support representative." |
|
HA_EM-3-FMPD_UNKNOWNTYPE |
3-Error |
[chars]: Unknown event type found in applet. |
The Embedded Event Manager applet had an unknown event type. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMPD_WRONGTYPE |
3-Error |
[chars]: Published event type does not match event spec. |
The Embedded Event Manager Policy Director detected a mis-match in event type between the published event and the event spec. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMS_CNS_FAIL |
3-Error |
[chars]: Failed to perform CNS action: [chars] |
The Embedded Event Manager failed attempting to send a CNS message. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMS_EMPTY_QUEUE |
3-Error |
[chars]: The I/O queue empty. |
The I/O queue is empty at this point and should not be. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMS_ENQUEUE_FAIL |
3-Error |
[chars]: The Unable to enqueue packet onto queue. |
The queue is not in a state to handle enqueues. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMS_NO_TRACK |
3-Error |
Use of the \track\ keyword in the correlate statement is not supported in this image. |
The Embedded Event Manager Track ED is not supported in this image. |
ha/eem |
"Track ED is not available in this image" |
|
HA_EM-3-FMS_POLICY_CHECKSUM |
3-Error |
[chars]: Checksum error for policy [chars] - this policy will not be run |
The checksum computed for the specified policy does not match the original checksum computed when the policy was registered. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMS_POLICY_LOOKUP_FAIL |
3-Error |
[chars]: Failed to look up in the table the registration specification for policy [chars]. |
The realloc function reported an error. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMS_QUEUE_INIT |
3-Error |
[chars]: The Unable to initialize queue. |
An attempt to publish an event failed because there is no more room in the publish queue. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-3-FMS_SWITCH_NOT_RF_ACTIVE |
3-Error |
[chars]: This processor is not in ACTIVE state state = [dec]. Switchover must be performed on ACTIVE processor. |
Switchovers must occur on ACTIVE unit not STANDBY unit. |
ha/eem |
"" |
|
HA_EM-4-FMFD_SNMP_NO_OBJECT_VALUE |
4-Warning |
[chars]: SNMP MIB object value not provided |
The SNMP MIB object value is not provided for substitution. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-4-FMPD_DSIG_TYPE_CHANGE |
4-Warning |
Cisco Signature not found or invalid. [chars] has been registered as a user policy. |
Cisco Signature not found or invalid. |
ha/eem |
"Sign with Cisco signature." |
|
HA_EM-4-FMPD_EVENT_CREATE |
4-Warning |
[chars]: failed to create an event: [chars] |
Failed to create an Embedded Event Manager event. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-4-FMPD_EVENT_REG |
4-Warning |
[chars]: failed to register an event: [chars] |
Failed to register an Embedded Event Manager event. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-4-FMPD_IPC_GET_PAK |
4-Warning |
[chars]: failed to allocate an IPC buffer |
Embedded Event Manager failed to allocate a buffer from IPC. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-4-FMPD_IPC_SEND_MSG |
4-Warning |
[chars]: failed to send an IPC message: [chars] |
Embedded Event Manager failed to send a message through IPC. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-4-FMPD_NO_ACTION |
4-Warning |
No action configured for applet [chars] |
No action has been configured for this applet. |
ha/eem |
"Configure at least one action for this applet." |
|
HA_EM-4-FMPD_NO_EVENT |
4-Warning |
No event configured for applet [chars] |
No event has been configured for this applet. |
ha/eem |
"Configure an event for this applet." |
|
HA_EM-4-FMPD_NOTAGNAME |
4-Warning |
[chars]: No tag [chars] found corresponding to this event publish. |
The Embedded Event Manager policy director could not associate the tagname with a published event. |
ha/eem |
"Only use tagnames in the action info type event reqinfo command which correspond to the published event." |
|
HA_EM-4-FMS_NO_SCHED_THREAD |
4-Warning |
No threads are configured to service event class [chars] |
The Embedded Event Manager has no scheduler threads to service this event class. |
ha/eem |
"Configure threads for the event class using the 'event manager scheduler' command." |
|
HA_EM-6-FMPD_CONTEXT_RETRIEVE |
6-Information |
Failed to retrieve context for key [chars]: [chars] |
Failed to context retrieve variable information for event. |
ha/eem |
"Ensure context information with the given key is saved. " "If the message continues to occur copy the message exactly as it appears " "and report it your technical support representative." |
|
HA_EM-6-FMPD_CONTEXT_SAVE |
6-Information |
Failed to save variable context for key [chars]: [chars] |
Failed to context save variable information for event. |
ha/eem |
"Ensure context information with the same key is not already saved. " "If the message continues to occur copy the message exactly as it appears " "and report it your technical support representative." |
|
HA_EM-6-FMPD_DIVIDE_ZERO |
6-Information |
Invalid operand in arithmetic division cannot divide by zero |
Arithmetic division does not allow divide by zero. |
ha/eem |
"Ensure denominator provided to division action is non-zero." |
|
HA_EM-6-FMPD_EEM_CONFIG |
6-Information |
[chars]: [chars] |
The Embedded Event Manager reports an error on Event Manager configuration |
ha/eem |
"Check the EEM applet or policy configuration" |
|
HA_EM-6-FMPD_OPERAND_INVALID |
6-Information |
Invalid operand in action expected value within range %ld to %ld received: [chars] |
Arithmetic actions only accept valid long integer values. |
ha/eem |
"Ensure value provided to action is long integer." |
|
HA_EM-6-FMPD_REGCOMP |
6-Information |
Error compiling regular expression: [chars] |
An error was encountered when compiling the given regular expression. |
ha/eem |
"Check syntax of regular expression pattern. If the " "message continues to occur copy the message exactly as it appears " "and report it your technical support representative." |
|
HA_EM-6-FMPD_SNMP_DUP_OID |
6-Information |
[chars]: duplicate oid |
The oid is a duplicate |
ha/eem |
"Check the EEM applet or policy configuration" |
|
HA_EM-6-FMPD_SNMP_NO_VAR |
6-Information |
[chars]: No variable [chars] |
The variable is not defined. |
ha/eem |
"Check the EEM applet or policy configuration" |
|
HA_EM-6-FMPD_SNMP_TRAPVAR_ADD |
6-Information |
[chars]: Error adding trapvar to queue [chars] |
The trap variable was not added to the queue. |
ha/eem |
"Check the EEM applet or policy configuration" |
|
HA_EM-6-FMPD_SNMP_VARS_EXCEEDED |
6-Information |
[chars]: number of values exceeded [dec] |
The number of values per variable exceeded the maximum |
ha/eem |
"Check the EEM applet or policy configuration" |
|
HA_EM-6-FMPD_SWITCH_HARDWARE |
6-Information |
[chars]: Policy has requested a hardware switchover |
An Embedded Event Manager policy requested that a hardware switchover occur. |
ha/eem |
"None" |
|
HA_EM-6-FMPD_UPDATE_POLICY_COPY |
6-Information |
Policy update has copied [dec] bytes from [chars] to [chars] |
An EEM policy has been copied as a result of an event manager update command |
ha/eem |
"" |
|
HA_EM-6-FMPD_UPDATE_POLICY_REGISTER |
6-Information |
Policy update has successfully re-registered policy [chars] |
An EEM policy has been successfully re-registered as a result of an event manager update command |
ha/eem |
"" |
|
HA_EM-6-FMPD_UPDATE_POLICY_REGISTER_FAIL |
6-Information |
Policy update has failed to register policy [chars] [chars] |
An EEM policy has failed to be registered as a result of an event manager update command |
ha/eem |
"" |
|
HA_EM-6-FMPD_UPDATE_POLICY_UNREGISTER_FAIL |
6-Information |
Policy update has failed to unregister policy [chars] [chars] |
An EEM policy has failed to be unregistered as a result of an event manager update command |
ha/eem |
"" |
|
HA_EM-6-FMS_LAST_POLICY |
6-Information |
[chars]: Cannot change a class [chars] [chars] to priority LAST. LAST is for default policies only |
Embedded Event Manager Scheduler Command can only change a default policy to priority LAST. |
ha/eem |
"The command is applicable to default policies only." |
|
HA_EM-6-FMS_MODIFY_LAST_POLICY |
6-Information |
[chars]: Cannot modify a LAST policy to class [chars]. LAST policies are for class default only. |
Embedded Event Manager LAST policy is for default class only. |
ha/eem |
"The command is applicable to default policies only." |
|
HA_EM-6-FMS_MODIFY_POLICY |
6-Information |
[chars]: unable to modify the policy to class [chars]: scheduling rule unavailable. |
There is no scheduler rule configured to service this event class. |
ha/eem |
"Please configure a scheduler rule before modifying the event." |
|
HA_EM-6-FMS_RUNNING_POLICY |
6-Information |
[chars]: cannot [chars] a running policy with jobid [dec]. |
Embedded Event Manager Scheduler Command cannot change a running policy. |
ha/eem |
"The command is not applicable to a running policy." |
|
HA_EM-6-FMS_SWITCH_HARDWARE |
6-Information |
[chars]: Policy has requested a hardware switchover |
An Embedded Event Manager policy requested that a hardware switchover occur. |
ha/eem |
"" |
|
HA_EM-7-ACTION_CNS_AGENT_UNAVAIL |
7-Debug |
[chars]: CNS Event Agent not available: [dec] |
The enqueue function reported an error. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-ACTION_WB_CREATE |
7-Debug |
[chars]: create_watched_boolean failed: [chars] |
The create_watched_boolean function reported an error trying to create the watched boolean. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-ACTION_WB_DELETE |
7-Debug |
[chars]: delete_watched_boolean failed: [chars] |
The delete_watched_boolean function reported an error trying to delete the watched boolean. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMC_INV_REPLY |
7-Debug |
[chars]: Application client library unable to handle message receive. |
The CNS Action process failed to set the restart callback. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMC_REG_CBH_PULSE |
7-Debug |
[chars]: Unable to locate reg callback entry for pulse code [dec] |
The registration callback handler was unable to validate the pulse code received. |
ha/eem |
"The pthread_create function reported an error." |
|
HA_EM-7-FMC_REG_CBH_SEND |
7-Debug |
[chars]: Unable to send response for FH_MSG_CALLBACK_DONE [chars] |
The registration callback handler was unable to send the FH_MSG_CALLBACK_DONE message to the Embedded Event Manager Server. |
ha/eem |
"The pthread_create function reported an error." |
|
HA_EM-7-FMFD_DE_FETCH |
7-Debug |
[chars]: [chars][[dec]] |
Internal error. The event detector has failed to fetch a data element from the statistics data engine. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMFD_HIST_QERR |
7-Debug |
[chars] |
Internal error. The event detector has failed to get a free history list entry. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMFD_INV_COMPARE_OP |
7-Debug |
[chars]: invalid comparison operator: [dec] |
Internal error. The value comparison operator is invalid or not supported. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMFD_INV_STATS_TYPE |
7-Debug |
[chars]: invalid statistics value type: [dec] |
Internal error. The statistics data type is invalid or not supported. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMFD_INV_TM |
7-Debug |
[chars]: invalid timer: type=[dec] timer=%p |
Internal error. The timer value is invalid or not as expected. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMFD_INV_TM_TYPE |
7-Debug |
[chars]: invalid timer type: [dec] |
Internal error. The timer type is invalid or not supported. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMFD_MET_RBLD |
7-Debug |
[chars]: [chars] |
Internal error. The event detector has failed to rebuild the metric list from the checkpointed records. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMFD_MSGSEND_RETRY_ERR |
7-Debug |
[chars]: [dec] |
The event detector has exceeded its maximum number of retries to send a pulse to the embedded event manager to notify of an event publish. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMFD_OE_CREATE |
7-Debug |
[chars]: could not create an occurrence entry |
Internal error. The event detector has failed to create an entry for the matched occurrence list. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMFD_OE_REMOVE |
7-Debug |
[chars]: could not remove an occurrence entry |
Internal error. The event detector has failed to remove an entry for the matched occurrence list. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMFD_PUB_TM_ALLOC |
7-Debug |
[chars]: Unable to allocate memory for event publish timer block |
Internal error. The event detector has failed to allocate memory for the event publish timer block. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMFD_SNMP_ADDR_ILLEGAL |
7-Debug |
[chars]: Illegal SNMP address type |
The SNMP address is illegal. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMFD_SNMP_ADDR_IPV6 |
7-Debug |
[chars]: SNMP IPV6 address is not supported |
The IPV6 address is not supported. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMFD_SNMP_BUILD_PDU_FAILED |
7-Debug |
[chars]: SNMP build pdu failed |
The SNMP pdu build has failed. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMFD_SNMP_ERRCODE |
7-Debug |
[chars]: [chars] |
The SNMP error code. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMFD_SNMP_MAKE_PDU_FAILED |
7-Debug |
[chars]: SNMP make pdu failed |
The SNMP pdu make has failed. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMFD_SNMP_OID_INVALID |
7-Debug |
[chars]: Invalid SNMP oid length [dec] |
The SNMP oid has invalid length |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMFD_SNMP_REQ_FAILED |
7-Debug |
[chars]: SNMP request failed |
The SNMP request has failed. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMFD_SNMP_RESP_CANCEL |
7-Debug |
[chars]: SNMP response cancelled |
The SNMP response has been cancelled. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMFD_SNMP_RESP_Q_EMPTY |
7-Debug |
[chars]: SNMP proxy exec got event but queue is empty |
The SNMP proxy got event but the queue is empty. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMFD_SNMP_RESP_TIMEOUT |
7-Debug |
[chars]: SNMP response has timed out |
The SNMP response has error. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMFD_SNMP_UNKNOWN_TYPE |
7-Debug |
[chars]: Unknown SNMP operation or response type [dec] |
The operation or response type is unknown. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMFD_SNMP_VARBIND_FAIL |
7-Debug |
[chars]: Unable to create a SNMP varbind |
The oid failed to make into a SNMP varbind |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMFD_TM_LEAF_NEW |
7-Debug |
[chars]: could not create a leaf timer |
Internal error. The event detector has failed to create a managed leaf timer. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMPD_EVENT_TYPE |
7-Debug |
[chars]: unknown event type [dec] |
An unknown Embedded Event Manager even type was detected. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMPD_FORMAT_TIME |
7-Debug |
[chars]: error attemting to format time string |
Format time failure. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMPD_LAST_POLICY |
7-Debug |
[chars]: invalid last policy name replied [chars] |
Internal error. The last policy name the script director replied to show fm policy registered command is an invalid policy name. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMPD_NO_MEM |
7-Debug |
[chars]: not enough memory: [chars] |
Allocating memory failed due to a low-memory condition. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMPD_SWITCH_FAIL |
7-Debug |
[chars]: The system is unable to switch to standby processor. Switchover cancelled. |
Switchovers must occur when STANDBY is available and ready. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMS_FDC_OPEN |
7-Debug |
[chars]: Failed to open Event Detector context control block |
The malloc function reported an error. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMS_INV_ARG_STRING |
7-Debug |
[chars]: Invalid argument string: [chars] |
The fh_hash_md5_fd function reported the specified error. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMS_NULL_SCRIPT_NAME |
7-Debug |
[chars]: The script name is NULL |
An invalid script name was passed as an argument into the specified function. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_EM-7-FMS_POLICY_EXEC |
7-Debug |
[chars]: Policy execution [chars] |
An Embedded Event Manager policy requested that the system be reloaded. |
ha/eem |
"" |
|
HA_EM-7-FMS_SWITCH_FAIL |
7-Debug |
[chars]: The system is unable to switch to standby processor. Switchover cancelled. |
Switchovers must occur when STANDBY is available and ready. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
HA_PROXY-2-HA_FIND_SERVICE_FAILED |
2-Critical |
[chars]: unable to find [chars] service |
HA could not find the specified service |
cpp-ucode |
LOG_STD_ACTION |
|
HA_PROXY-2-HA_SESSION_ALLOC_FAILED |
2-Critical |
[chars]: unable to allocate entry for [chars] binding |
HA could not allocate a control block to manage the service |
cpp-ucode |
LOG_STD_ACTION |
|
HA_PROXY-3-HA_DUP_SERVICE_INDEX |
3-Error |
[chars]: Duplicate service index: [dec] on bind |
Duplicate service index on ha service bind |
cpp-ucode |
LOG_STD_ACTION |
|
HA_PROXY-3-HA_DUP_SERVICE_NAME |
3-Error |
[chars]: Duplicate service name: [chars] on bind |
Duplicate service name on ha service bind |
cpp-ucode |
LOG_STD_ACTION |
|
HA_PROXY-3-HA_INVALID_REQUEST |
3-Error |
[chars]: Unknown request: [dec] |
HA control services received unknown request |
cpp-ucode |
LOG_STD_ACTION |
|
HA_PROXY-3-HA_MALFORMED_PKT |
3-Error |
Malformed packet bad [chars] [hec] |
HA Sync packet was malformed may not have been fully processed |
cpp-ucode |
LOG_STD_ACTION |
|
HA_PROXY-3-PROXY_IPC_PAK_ALLOC_FAILED |
3-Error |
- |
Allocation of IPC packet failed. |
cpp-ucode |
LOG_STD_ACTION |
|
HA_PROXY-4-HA_PKT_ERROR |
4-Warning |
Error processing HA sync pkt rg [hec] |
HA Sync packet was dropped while processing |
cpp-ucode |
LOG_STD_ACTION |
|
HA_PROXY-4-HA_UNKNOWN_SERVICE |
4-Warning |
Sync msg for unknown service [hec] rg [hec] |
HA Sync received a message for an unknown service |
cpp-ucode |
LOG_STD_ACTION |
|
HA_TLV-2-LDP |
2-Critical |
ERRMSG_NOFLAGS |
- |
- |
- |
|
HA-2-CCB_PLAYBACK_ERROR |
2-Critical |
CCB playback failed. |
This is a critical error message about a High Availability System status or condition. |
- |
"Copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance." |
|
HA-2-CCB_RECORD_ERROR |
2-Critical |
CCB record failed. |
This is a critical error message about a High Availability System status or condition. |
- |
"Copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance." |
|
HA-2-CUTOVER_ERROR |
2-Critical |
[chars] |
This is a critical error message about a High Availability System cutover status or condition. A message of this type indicates that a critical failure occurred during cutover of the standby system to the active system. Messages of this type indicate that the active system relinquished system control that the standby system failed to properly take over as the active. |
- |
"Copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance." |
|
HA-2-CUTOVER_NOTICE |
2-Critical |
[chars] |
This is an important High Availability System notice logging the state of a system cutover of the standby system to the active system. Messages of this type indicate that the active system reliquished system control and that the standby system is taking over as active. |
- |
"If the message is due to a failure condition copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance. If the message is not due to a failure condition no action is required." |
|
HA-2-INIT_ERROR |
2-Critical |
[chars] |
This is a critical error message about a High Availability System initilization status or condition. A message of this type indicates that a failure occured during high availability system initialization. |
- |
"Copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance." |
|
HA-2-IPC_ERROR |
2-Critical |
[chars] [chars] |
This is a critical error message about a High Availability System interprocess communication status or condition. A message of this type indicates that an interprocess communication failure occurred between the active system and the standby system. |
- |
"Copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance." |
|
HA-2-MAX_NO_QUIESCE |
2-Critical |
[dec] linecards not quiesced exceeds limit of [dec] all slots will be reloaded. |
- |
- |
"If you OIR removed the active RSP or have legacy IPs installed in the system this message is normal. Otherwise copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance." |
|
HA-2-NO_QUIESCE |
2-Critical |
Slot [dec] did not quiesce it will be disabled and then reloaded. |
This is a cutover notice about a High Availability System linecard error condition. The linecard did not quiesce properly. |
- |
"This message is normal if the slot contains a legacy IP. Otherwise copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance." |
|
HA-3-ERROR |
3-Error |
[chars] |
This is a error message about a High Availability System status or condition. |
- |
"Copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance." |
|
HA-3-RF_EVENT_FAILED |
3-Error |
RF event not processed till [dec] milliseconds. Code = [dec] |
The event sent to the redundancy facility was not processed till the specific time delay. |
- |
"Copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance." |
|
HA-3-SYNC_ERROR |
3-Error |
[chars] |
This is a error message about a High Availability System state syncronization error status or condition. |
- |
"Copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance." |
|
HA-4-CHKPT |
4-Warning |
Platform CF - [chars] |
Failure in some UNIX checkpointing activity. |
UNIXRP_DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
HA-4-CHKPTSEND |
4-Warning |
[chars] rc [dec] event [chars] |
Failure to send UNIX checkpointing data. |
UNIXRP_DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
HA-4-CONFIG_NOT_LOCKED |
4-Warning |
Unable to lock the configuration session. |
This is a warning message indicating that the configuration session could not be locked. Simultaneous configuration sessions can corrupt the configuration. |
- |
"Copy the message exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance." |
|
HA-4-NOPROCESS |
4-Warning |
Creation of [chars] process failed |
Creation of a platform high availability process failed. |
UNIXRP_DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
HA-4-SYNC |
4-Warning |
[chars] |
An error was encountered in a data sync operation |
UNIXRP_DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
HA-4-WARNING |
4-Warning |
[chars] |
This is a warning message about a High Availability System status condition or event. |
- |
"Copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance." |
|
HA-5-HA_IOS_VERSION |
5-Notice |
Active IOS version differs from standby IOS version |
This is a notice about High Availablility System version mismatch between the active and standby systems. |
- |
"No action required." |
|
HA-5-HA_VERSION |
5-Notice |
Active HA version [dec].[dec] differs from standby HA version [dec].[dec] |
This is a notice about High Availablility System version mismatch between the active and standby systems. |
- |
"No action required." |
|
HA-5-HWMOD_IMG_NOTICE |
5-Notice |
[chars] hw-module slot [dec] image [chars] : [chars] |
This is a notice message about a High Availability System hardware module configuration status condition or event. |
- |
"Copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance." |
|
HA-5-MODE |
5-Notice |
Operating mode is [chars] [chars]mode is [chars]. |
This is a notice about the High Availablility System mode. |
- |
"Make sure that both the active system and standby systems are correctly configured and operational." |
|
HA-5-NOTICE |
5-Notice |
[chars] |
This is a notice message about a High Availability System status condition or event. |
- |
"No action required." |
|
HA-5-RF_RELOAD_NOTICE |
5-Notice |
Unable to reload the standby. [chars] |
The active RSP was unable to reload the standby because of the reason indicated in the message. This may be because the slave is in unplugged state or because there is a redundancy forced switchover process in progress or because the reload function is incorrectly called from the standby to the active. |
- |
- |
|
HA-5-SYNC_NOTICE |
5-Notice |
[chars] |
This is a notice message about a High Availability System syncronization status condition or event. |
- |
"No action required." |
|
HA-5-SYNC_RETRY |
5-Notice |
Reloading standby and retrying sync operation retry [dec]. |
This is a notice message about a High Availability System syncronization status condition or event. The syncronization operation will be retried. |
- |
"No action required." |
|
HA-5-SYNC_RETRY_FAIL |
5-Notice |
Maximum sync retries exceeded. Reloading standby and cancelling sync. |
This is a notice message about a High Availability System syncronization status condition or event. The syncronization operation failed. |
- |
"Copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance." |
|
HA-6-FALLBACK |
6-Information |
[chars] - configured mode[chars] fallback mode[chars] |
This RP redundancy mode fell back to the indicated mode |
UNIXRP_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
HA-6-MODE |
6-Information |
Operating RP redundancy mode is [chars]\n |
Operational redundancy mode information |
UNIXRP_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
HA-6-STANDBY_READY |
6-Information |
Standby RP in slot [dec] is operational in [chars] mode\n |
Indicates standby route processor readiness |
UNIXRP_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
HA-6-SWITCHOVER |
6-Information |
Route Processor switched from standby to being active |
This RP switched to become the active RP |
- |
LOG_STD_NO_ACTION |
|
HA-6-TOOBIG |
6-Information |
Running config too big config sync failed |
The running config was too big to be synced |
- |
LOG_STD_NO_ACTION |
|
HA-6-TOOBIG |
6-Information |
Running config too big config sync failed |
The running configuration was too big to be synced |
UNIXRP_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
HAL_GENMEM-2-BAD_OPCODE |
2-Critical |
Opcode=[hec] |
A bad Opcode was received by the general memory manager. |
cpp-ucode |
LOG_STD_ACTION |
|
HAL_GENMEM-3-HAL_MISMATCHED_GENMEM |
3-Error |
VADDR:%lu LINE: [dec] |
Mismatched genmem. |
cpp-ucode |
LOG_STD_ACTION |
|
HAL_GPM-3-PREALLOC_FAIL |
3-Error |
offset 0x%08lx retcode [dec] |
A critical failure occurred when trying pre-allocate GPM |
cpp-ucode |
LOG_STD_ACTION |
|
HAL_PACKET-3-HAL_GATHER_ASYNC_WAIT_TIMEOUT |
3-Error |
seqnum=%lu pak-type=%lu |
Packet Hardware Transmit Error |
cpp-ucode |
LOG_STD_ACTION |
|
HAL_PKTMEM-2-ALLOC_FAIL |
2-Critical |
rc 0x[hec] |
A critical failure occurred when trying to obtain packet memory |
cpp-ucode |
LOG_STD_ACTION |
|
HAL_PKTMEM-2-ALLOC_FAIL |
2-Critical |
rc 0x[hec] |
A critical failure occurred when trying to obtain packet memory |
cpp-ucode |
LOG_STD_ACTION |
|
HAL_PKTMEM-2-OUT_OF_RESOURCES |
2-Critical |
Packet buffer memory is low packets are being dropped |
Packet buffer memory is low packets are being dropped |
cpp-ucode |
LOG_STD_ACTION |
|
HAL_PKTMEM-2-OUT_OF_RESOURCES |
2-Critical |
- |
Packet buffer memory is low packets are being dropped |
cpp-ucode |
LOG_STD_ACTION |
|
HAL_PKTMEM-3-UTILIZATION_SEVERE |
3-Error |
making very aggressive adjustments to conserve [chars] buffer resources. |
Packet buffer utilization is at a severe level. |
cpp-ucode |
LOG_STD_ACTION |
|
HAL_PKTMEM-4-UTILIZATION_WARNING |
4-Warning |
making more aggressive adjustments to conserve [chars] buffer resources. |
Packet buffer utilization is at a risky level. |
cpp-ucode |
LOG_STD_ACTION |
|
HAL_PKTMEM-5-UTILIZATION_NOTICE |
5-Notice |
making adjustments to conserve [chars] buffer resources. |
Packet buffer utilization is substantial. |
cpp-ucode |
LOG_STD_ACTION |
|
HARDWARE-3-ASICNUM_ERROR |
3-Error |
Port-ASIC number [dec] is invalid |
Each Port-ASIC is identified by an ID. The port ASIC number used is invalid and this is an internal error |
firmware |
LOG_STD_ACTION |
|
HARDWARE-3-PORTNUM_ERROR |
3-Error |
port number [dec] is invalid |
Each interface in a given Port-ASIC is identified using an index value. The port-number used is not valid out of range |
firmware |
LOG_STD_ACTION |
|
HCCP_LC_ISSU_SHIM-3-CLC_HIGH_CPU_UTILIZATION |
3-Error |
High CPU utilization on line card [dec]/[dec] line card ISSU may fail. |
Line card ISSU may fail due to high CPU utilization on the line card. |
cmts-platform |
"Attempt line card ISSU when line card has lower CPU load" |
|
HCCP_LC_ISSU_SHIM-3-REVERTIVE_CFG |
3-Error |
HCCP revertive configuration exists for interfaces on slot [dec]/[dec]. |
HCCP revertive is enabled for the protect interfaces on the given line card. For ISSU to function without being disrupted by automatic revert backs please configure interfaces to be non-revertive. |
cmts-platform |
"Configure interfaces to be non-revertive." |
|
HCCP_LC_ISSU_SHIM-3-RP_HIGH_CPU_UTILIZATION |
3-Error |
High CPU utilization on PRE line card ISSU may fail. |
Line card ISSU may fail due to high CPU utilization on the PRE. |
cmts-platform |
"Attempt line card ISSU when PRE has lower CPU load" |
|
HCCP_LC_ISSU_SHIM-3-SWITCHOVER_FAILURE_EXTERNAL_RF_SWITCH |
3-Error |
Switchover from line card [dec]/[dec] aborted. |
HCCP switchover from the give slot is aborted due to external RF switch error in the HCCP LC ISSU shim layer. |
cmts-platform |
"Check the network connection between the router and " "the external RF switch." |
|
HCCP-3-BADCHAN |
3-Error |
HCCP [chars] Mbr [dec] [chars]: channel switch \[chars]\ failed retries exhausted. |
HCCP LC member notifies failure in its channel switch. |
- |
"Make sure channel switch is functioning." |
|
HCCP-3-BADMSG |
3-Error |
Grp [dec] Mbr [dec] [chars]: received wrong type of message-[chars]. |
Certain types of HCCP message are not supposed to be received by Working or Protect. |
- |
"Check configuration on this interface and the sender's interface" |
|
HCCP-3-BADSTATE |
3-Error |
HCCP [chars] Grp [dec] inconsistant state !! |
HCCP state inconsistancy after control plane switchover |
- |
"Reset the interface" |
|
HCCP-3-CFG_FAIL |
3-Error |
Configuration failed. [chars] |
An error occurred during configuration. |
- |
LOG_STD_SH_TECH_ACTION |
|
HCCP-3-CFR_LIST |
3-Error |
Remove an element before destroy [chars]: cfrid=[dec] direction=[dec] state=[dec] ip_sadd=[inet] ip_daddr=[inet] dest_macaddr=[enet] src_macaddr=[enet] ip_prot=[dec] eport=[dec] |
Remove an element from interdb cfr_list before destroy the list. |
ubr10000 |
"Reset the system" |
|
HCCP-3-CONFIGSYNC_ERROR |
3-Error |
Enable config-sync when it is not disabled |
HCCP internal flag configsync the software is trying to enable this flag set to 0 while it is already enabled 0. |
ubr10000 |
"Reset the system" |
|
HCCP-3-CTRL_PLANE_READY |
3-Error |
HCCP ctrl plane for [chars] member [dec] is ready. |
HCCP ctrl plane is ready to receive lc2rp sync for the groups in list. |
- |
"." |
|
HCCP-3-DATA_PLANE_READY |
3-Error |
HCCP data plane for [chars] member [dec] is ready. |
HCCP lc2rp sync for the groups in list is completed. |
- |
"." |
|
HCCP-3-INVALID_PROTECT |
3-Error |
ERROR!LC-RED: License of protect card [dec]/[dec] is incompatible with working card [dec]/[dec]. |
The protect linecard has lower license. |
- |
"Please upgrade the license on the protect" |
|
HCCP-3-MISS_CTRLPLANE_READY |
3-Error |
HCCP [chars] member [dec]: Ctrl Plane Ready is missed because [chars] |
HCCP ctrl plane ready is missed because of message missed or ctrl plane error. |
- |
"Check the status of ctrl plane" |
|
HCCP-3-MISS_DATAPLANE_READY |
3-Error |
HCCP [chars] member [dec]: Data Plane Ready is missed because [chars] |
HCCP data plane ready is missed because of message missed or data plane error. |
- |
"Check the status of data plane" |
|
HCCP-3-MISS_STATICSYNC_DONE |
3-Error |
HCCP [chars] member [dec]: Static Sync Done is missed because [chars] Redo static sync through CLI. |
HCCP static sync done is missed because of switch over happened or STATICSYNCDONE message missed. |
- |
"Perform static sync through CLI." |
|
HCCP-3-OUT_OF_ORDER_LC_MSG |
3-Error |
HCCP slot [dec] member [dec] status [chars]: NULL hp/mp encountered. |
HCCP software has detected that messages are Out of Order. |
- |
LOG_STD_ACTION |
|
HCCP-3-OUT_OF_ORDER_LC2RP |
3-Error |
Grp [dec] Mbr [dec] status [chars]: Received LC to RP sync in standby state. Message rejected. |
HCCP software has detected that messages are Out of Order. |
- |
LOG_STD_ACTION |
|
HCCP-3-OUT_OF_ORDER_MSG |
3-Error |
Grp [dec] Mbr [dec] status [chars]: NULL hp encountered. |
HCCP software has detected that messages are Out of Order. |
- |
LOG_STD_ACTION |
|
HCCP-3-PROTECTING_TOO_MANY |
3-Error |
Grp [dec] Mbr [dec] status [chars]: Protecting too many Workings. |
HCCP detected that protect is asked to protect too many working i/fs. |
- |
LOG_STD_ACTION |
|
HCCP-3-UNKNOWN_TLV |
3-Error |
Grp [dec] Mbr [dec] [chars]: received Unknown TLV type-[dec]. |
HCCP software has detected Unknown TLV typesthis may not affect the functionality |
- |
LOG_STD_ACTION |
|
HCCP-4-NOREVERT |
4-Warning |
HCCP [chars] Mbr [dec]: Revert operation cancelled. |
HCCP LC member will not attempt to revert back to the Working interface. |
- |
"it may have occurred because last time switchover is not finished. " "Make sure the current hccp state is in warm state" |
|
HCCP-4-NOSWOVER |
4-Warning |
HCCP [chars] Mbr [dec]: switchover is not triggered because [chars]. |
HCCP LC member will not attempt to revert back to the Working interface. |
- |
"it may have occurred because last time switchover is not finished. " "Make sure the current hccp state is in warm state" |
|
HCCP-4-PEERBUSY |
4-Warning |
HCCP [chars] member [dec] Switchover aborted. Protect [chars] is already ACTIVE for member [dec]. |
HCCP software has detected that the PROTECT linecard is already Active for another Working |
- |
"Please free up the Protect interface by reverting back to the " "other Working and try this switchover again" |
|
HCCP-5-BULKSYNCINCOMP |
5-Notice |
Grp [dec] Mbr [dec] [chars]: During PRE bulk syncing ignore LC failover. |
Ignore LC failover event when active PRE is syncing data to standby PRE. |
cmts-redundancy |
- |
|
HCCP-5-CHANOFF |
5-Notice |
HCCP [chars] Mbr [dec] [chars]: turning off channel. |
HCCP LC member notifies that it turns off channel switch. |
- |
"Make sure peer controls the channel." |
|
HCCP-5-CHANON |
5-Notice |
HCCP [chars] Mbr [dec] [chars]: turning on channel. |
HCCP LC member notifies that it turns on channel switch. |
- |
"Make sure peer relinquishes the channel." |
|
HCCP-5-LC_ACTIVE |
5-Notice |
HCCP [chars] Mbr [dec] [chars]: change state to active due to: [chars]. |
HCCP LC member notifies that it changes to active. |
- |
"Make sure peer relinquishes the channel." |
|
HCCP-5-LC_STANDBY |
5-Notice |
HCCP [chars] Mbr [dec] [chars]: change state to standby due to: [chars]. |
HCCP LC member notifies that it changes to standby. |
- |
"Make sure peer controls the channel." |
|
HCCP-5-STANDBY |
5-Notice |
Grp [dec] Mbr [dec] [chars]: change state from active to standby cause: [chars]. |
HCCP group member notifies that it changes from active to standby. |
- |
"Make sure peer controls the channel." |
|
HCCP-5-SWITCHOVERREADY |
5-Notice |
HCCP [chars] Mbr [dec] [chars]: ready to switchover. |
HCCP LC member suspend timer expires ready to switchover. |
- |
"." |
|
HCCP-6-HCCP_CHAN_RFSW_SNMP_ERROR |
6-Information |
[chars] error: [chars]. |
HCCP channel process errors related SNMP. |
- |
"." |
|
HCCP-6-HCCP_CHAN_RFSW_SNMP_INFO |
6-Information |
[chars]: [chars]. |
SNMP response. |
- |
"." |
|
HCCP-6-IGNORE_MD_UP |
6-Information |
The member [chars] [dec][[dec]] is already up ignore repeated event. |
The mac domain is already active ignore the repeated up events. |
- |
"." |
|
HCCP-6-LC_RPLC_CFGSYNC_CONFIG |
6-Information |
HCCP [dec] [dec] [chars]: LC [chars] rplc_cfgsync configuration recover is failed PRE will download LC configurations again. |
HCCP recover LC rplc_cfgsync configurations is failed because last rplc_cfgsync configuration is not success. |
- |
"PRE should download LC configurations otherwise it is a critical bug." |
|
HCCP-6-LC_RPLC_CFGSYNC_CONFIG_PARSER |
6-Information |
Parser Error: [dec] |
HCCP recover LC rplc_cfgsync configurations parser error. |
- |
"." |
|
HCCP-6-LC_RPLC_CFGSYNC_CONFIG_RECOVER |
6-Information |
HCCP [dec] [dec] [chars]: LC [chars] rplc_cfgsync configuration recover is succeed. |
HCCP recover LC rplc_cfgsync configurations is succeed. |
- |
"." |
|
HCCP-6-STATICSYNC_COMPLETED |
6-Information |
HCCP static sync for [chars] member [dec] is completed in [dec] ms. |
HCCP static sync for the groups in list is completed. |
- |
"." |
|
HD-1-BADLOOPCABLE |
1-Alert |
Loopback not supported for a 4T DTE/X.21 port [dec] in slot [dec] |
Loopback mode is not allowed when using an X.21 DTE cable on a Quad\n\ serial NIM port. |
- |
"Do not enable loopback or use a different cable type." |
|
HD-1-BADPORTADAPTER |
1-Alert |
4T Port Adapter fault on port [dec] in slot [dec] |
A hardware or software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
HD-1-BADRING |
1-Alert |
msgtxt_badringsize |
An internal software error occurred. |
- |
"If message recurs call your technical support representative for\n\ assistance." |
|
HD-5-LINEFLAP |
5-Notice |
Unit [dec] excessive modem control changes |
Too many modem control interrupts have been received. The port was\n\ disabled to prevent excessive use of the CPU. |
- |
"Check the cable on the serial port." |
|
HDLC-1-ISSU_NOMEMORY |
1-Alert |
msgtxt_nomemory |
The requested operation could not be accomplished because of a low memory condition. |
- |
"Reduce other system activity to ease memory demands. If conditions " "warrant upgrade to a larger memory configuration." |
|
HDLC-4-ISSU_INCOMPATIBLE |
4-Warning |
\nhdlc-issu-compat: returned FALSE |
The compatibility checking has failed |
- |
LOG_STD_SH_TECH_ACTION |
|
HDLC-4-ISSU_SENDFAILED |
4-Warning |
\nHDLC ISSU: send message failed rc = [dec]\n |
The sending of a message has failed. |
- |
LOG_STD_SH_TECH_ACTION |
|
HDLC-4-ISSU_XFORM |
4-Warning |
\n[chars]: failed rc=[chars] |
The transform has failed. |
- |
LOG_STD_SH_TECH_ACTION |
|
HDSPA_LIC-3-BOOLTIMEOUT |
3-Error |
Fail to wait for boolean [chars] |
This boolean is not set true before timeout |
APPLICATION |
"This boolean is not set true before timeout" "Please check the process that set this boolean" |
|
HDSPA_LIC-3-CSB_FAIL |
3-Error |
[chars] failed for [chars] |
An attempt to parse a license related CLI failed |
APPLICATION |
"Check the HDSPA license details and call TAC" |
|
HDSPA_LIC-3-FLASHERROR |
3-Error |
[chars] |
Unexpected flash error happend |
APPLICATION |
"Check SPA license flash" |
|
HDSPA_LIC-5-EXCEED_HW_CAP |
5-Notice |
DS_License installed[dec] on a single HDSPA exceeds |
Some of the licenses are wasted. |
APPLICATION |
"This could happen after license rehost. " "Please transfer the excess licenses to another PRE." |
|
HDSPA_LIC-5-EXCESS_LIC |
5-Notice |
Installed license count[dec] exceeds hardware capability[dec] |
Some licenses are wasted currently |
APPLICATION |
"If this is caused by intentional action or RMA " "please transfer excess SPA_DS_License licenses to " "another PRE otherwise please call TAC" |
|
HDSPA_LIC-6-NOSHUT |
6-Information |
[chars] channel [dec] has been restored to no shut |
Restored previously shutdown channels to no shut state |
APPLICATION |
"None" |
|
HDSPA_LIC-6-NOSHUTFAIL |
6-Information |
[chars] channel [dec] no shut is not allowed due to insufficient licenses |
Unable to no shut the channel due to insufficient licenses |
APPLICATION |
"Check number of licenses installed" |
|
HDSPA_LIC-6-OUT_OF_RANGE |
6-Information |
SPA [dec]/[dec] [chars] is already [dec] |
License counters have reached boundary condition |
APPLICATION |
"Internal Error check license and report to TAC" |
|
HDSPA_LIC-6-SHUT |
6-Information |
[chars] channel [dec] has been shutdown due to insufficient licenses |
Unable to no shut the Channel due to insufficient licenses |
APPLICATION |
"Check number of licenses installed" |
|
HDX-3-BADFSM |
3-Error |
On int [dec]/[dec] unexpected state [dec] event [dec] |
A bad state event pair is detected in the rx/tx half duplex state\n\ machine. |
pm-fecpm |
LOG_STD_ACTION |
|
HMANRP-3-MSG_CREATE_FAIL |
3-Error |
Message creation failed [chars] |
Could not create tdl message |
polaris-emp-relay |
LOG_STD_ACTION |
|
HMANRP-3-MSG_GET_FAIL |
3-Error |
Message read failed [chars] |
Could not fetch tdl message |
polaris-emp-relay |
LOG_STD_ACTION |
|
HMANRP-3-MSG_GET_VALUE_FAIL |
3-Error |
Message get value failed [chars] |
Could not fetch value from tdl message |
polaris-emp-relay |
LOG_STD_ACTION |
|
HMANRP-3-MSG_SEND_FAIL |
3-Error |
Message send failed [chars] |
Could not send tdl message |
polaris-emp-relay |
LOG_STD_ACTION |
|
HMANRP-3-SET_MSG_VALUE_FAIL |
3-Error |
TDL set value failed [chars] |
Could not tdl message values |
polaris-emp-relay |
LOG_STD_ACTION |
|
HMANRP-5-CHASSIS_DOWN_EVENT |
5-Notice |
Chassis [dec] gone DOWN! |
Chassis removed event |
polaris-emp-relay |
LOG_STD_ACTION |
|
HMANRP-6-ACTIVE_FLAG_SET |
6-Information |
EMP_RELAY: Status received from active setting active status flag |
Setting active status flag prioritizes active switch for election |
polaris-emp-relay |
LOG_STD_ACTION |
|
HMANRP-6-EMP_ELECTION_INFO |
6-Information |
EMP active switch [dec] elected: [chars] |
EMP election algorithm has been run and a switch has been elected as active EMP |
polaris-emp-relay |
LOG_STD_ACTION |
|
HMANRP-6-EMP_NO_ELECTION_INFO |
6-Information |
Could not elect active EMP switch setting emp active switch to 0: [chars] |
Could not elect active EMP switch |
polaris-emp-relay |
LOG_STD_ACTION |
|
HMANRP-6-EMP_PROCESS_EVT_STOP |
6-Information |
EMP_RELAY: Stopping and killing the monitoring process: [chars] |
The monitoring process has hit an event. The process has fulfilled its purpose it can now be killed. |
polaris-emp-relay |
LOG_STD_ACTION |
|
HMANRP-6-EMP_PROCESS_PREEMPT |
6-Information |
EMP_RELAY: Preempting and killing the monitoring process: [chars] |
An event has occured which has rendered the watching process useless. So the system will kill this process since it is not needed anymore. |
polaris-emp-relay |
LOG_STD_ACTION |
|
HMANRP-6-EMP_PROCESS_START |
6-Information |
EMP_RELAY: Starting process for event monitoring |
IOS-HMAN channel gone down possibly due to HMAN process dying. The EMP IOS process monitors if this channel has come upHMAN respawned |
polaris-emp-relay |
LOG_STD_ACTION |
|
HMANRP-6-EMP_STATUS_RCVD |
6-Information |
EMP status [dec] received from switch [dec] |
EMP status received from member HMAN |
polaris-emp-relay |
LOG_STD_ACTION |
|
HMANRP-6-HMAN_IOS_CHANNEL_INFO |
6-Information |
HMAN-IOS channel event for switch [dec]: [chars] |
Info on HMAN-IOS events |
polaris-emp-relay |
LOG_STD_ACTION |
|
HMANRP-6-RESET_ACTIVE_FLAG |
6-Information |
EMP_RELAY: Resetting active status flag IOS config'd shut/no shut admin_state = [dec] |
Resetting active status flag prioritizes active switch for election |
polaris-emp-relay |
LOG_STD_ACTION |
|
HMR-3-HASH_SIZE_ZERO |
3-Error |
count [dec] poly [dec] |
An invalid hash table size of 0 was detected |
cpp-ucode |
LOG_STD_ACTION |
|
HOOD-3-BADUNIT |
3-Error |
msgtxt_badunit |
An internal software error occurred. |
- |
"If the message recurs call your technical support representative\n\ for assistance." |
|
HOOD-5-CABLEERR |
5-Notice |
Unit [dec] HP100VG cable error. Training failed |
A 100VG cable or hub is faulty. |
- |
"If the message recurs and either the cable or hub appears to be\n\ good repair or replace the router module." |
|
HOOD-5-COLL |
5-Notice |
Unit [dec] excessive collisions |
An Ethernet cable is broken or unterminated or the transceiver is\n\ unplugged. |
- |
"If the transceiver appears to be properly terminated repair or\n\ replace the router." |
|
HOOD-5-LOSTCARR |
5-Notice |
Unit [dec] lost carrier. Transceiver problem? |
An Ethernet transceiver is unplugged or faulty. |
- |
"Repair or replace the controller." |
|
HOOD-5-NOCABLE |
5-Notice |
Unit [dec] HP100VG no tone detected. Check cable hub |
A 100VG cable is faulty. |
- |
"If the message recurs and either the cable or hub appears to be \n\ good repair or replace the router module." |
|
HPI-3-CODEC_NOT_LOADED |
3-Error |
channel:[chars] DSP ID:0x[hec] command failed as codec not loaded [dec] |
Sending messages to DSP without a loaded codec can result with the DSP failing |
ios-voice |
LOG_STD_ACTION |
|
HPI-3-FAILED_START |
3-Error |
channel:[chars] DSP ID:0x[hec] failed mode [dec] for service [dec] |
Failed to start DSP services |
ios-voice |
LOG_STD_ACTION |
|
HPI-3-GSMAMRNB_LICENSE_NOT_ACTIVATED |
3-Error |
\n********************************************************* \ \nGSM AMR-NB License is not yet activated. \ \nPlease configure 'license feature gsmamrnb-codec-pack' \ \nand accept the EULA to activate the license. \ \n*********************************************************\n |
Failed to start DSP services for GSM AMR-NB codec |
ios-licensing-atg |
LOG_STD_ACTION |
|
HPI-3-INVALID_PAYLOAD |
3-Error |
wrong payload size channel:[chars] DSP ID:0x[hec] failed mode [dec] for service [dec] |
Failed to start DSP services |
ios-voice |
LOG_STD_ACTION |
|
HPI-3-NACK_HIGH |
3-Error |
DSP to IOS Nack message with severity [chars] [chars] [chars] |
DSP to IOS Nack message with high severity |
ios-voice |
- |
|
HPI-3-SRTP_EVAL_FREE_ERROR |
3-Error |
Error encountered on release SRTP bandwidth and tunnels reservation |
Error encountered on release SRTP bandwidth and tunnels |
xformers-csl |
LOG_STD_NO_ACTION |
|
HPI-4-INVALID_CODEC_LOAD |
4-Warning |
channel:[chars] DSP ID:0x[hec] invalid hpi mode [dec] for loading codec [dec] |
Attempt to load codec when the DSP is in an invalid mode which can result with DSP failure |
ios-voice |
LOG_STD_ACTION |
|
HPI-4-INVALID_ECAN_TYPE |
4-Warning |
[chars] ECAN is not available in voice-card [dec] [chars] ECAN will be used |
All voice cards participated in DSPFarm must have the same echo canceller type |
- |
"Make sure all voice cards participated in DSPFarm have the same echo canceller type configured" |
|
HPI-4-NACK_MED |
4-Warning |
DSP to IOS Nack message with severity [chars] [chars] [chars] |
DSP to IOS Nack message with medium severity |
ios-voice |
"Check the NACKed message's parameters for " \"minor configuration errors. " |
|
HPI-4-NO_CLOSE |
4-Warning |
channel:[chars] DSP ID:0x[hec] |
Attempt to release DSP without sending close message |
ios-voice |
LOG_STD_ACTION |
|
HPI-6-NACK |
6-Information |
DSP to IOS Nack message [chars] [chars] |
DSP to IOS Nack message with no severity in order to work with dspware without Nack severity implementation |
ios-voice |
"Information only displaying NACKed messages." |
|
HPI-6-NACK_LOW |
6-Information |
DSP to IOS Nack message with severity [chars] [chars] [chars] |
DSP to IOS Nack message with low severity |
ios-voice |
"Information only displaying NACKed messages " \"that are for debugging purposes." |
|
HPI-6-SRTP_EVAL_LIMIT |
6-Information |
The SRTP bandwidth and tunnels usage exceed the license limits |
The SRTP bandwidth and tunnels exceed the license limits |
xformers-csl |
LOG_STD_NO_ACTION |
|
HQF-3-OH_FRAG_NOT_ALLOWED_TOGETHER |
3-Error |
Can't configure Overhead Accounting and fragmentation together! |
Overhead Accouting feature currently is not allowed to coexist with fragmentation configration. |
qos |
"Remove either Overhead Accouting or fragmentation\n " |
|
HQF-4-NOT_ENOUGH_BW |
4-Warning |
interface [chars]: available bandwidth may not meet bandwidth guarantees on direction [chars] |
The interface bandwidth is less than the total bandwidth that is required for HQF queuing features on this interface.\n |
- |
"Increase the bandwidth available on the interface.\n" |
|
HQF-6-ENOUGH_BW |
6-Information |
interface [chars]: available bandwidth now meet bandwidth guarantees on direction [chars] |
The interface bandwidth is now enough for the total bandwidth that is required for HQF queuing features on this interface.\n |
- |
"Do nothing.\n" |
|
HQF-6-TUNNEL_POLICY_INST_FAILED |
6-Information |
\nHQF-TUN: [chars] move failed to [chars] suspending policy |
- |
qos |
"The service-policy will be automatically restored " "if the tunnel adjacency changes again. " "Run 'show policy-map interface <tunnel>' " "to see if the service policy is still suspended. " "If a service-policy remains suspended longer than expected " "then check for other messages in the log that may " "clarify the source of the problem " "e.g. insufficient bandwidth to meet bandwidth guarantees. " |
|
HSR_ALARM-2-HSR_RINGFAULT |
2-Critical |
The HSR ring is now in FAULT state |
HSR Ring Down: The HSR ring is in FAULT state. This typically happens when both ring ports are down because of link or node failure. |
- |
- |
|
HSR_ALARM-3-HSR_PARTIALFAULT |
3-Error |
The HSR ring is now in PARTIAL FAULT state |
HSR Port Down: The HSR ring is in PARTIAL FAULT state. This typically happens when one of the ring port is down because of link or node failure. The Ring is still functional but needs attention as it can not handle further faults. |
petra-hsr |
- |
|
HSRP-3-MISCONFIG |
3-Error |
Attempt to change [chars] MAC address to [enet] when DECNET already running |
An HSRP group attempted to become active on an interface that can only support a single MAC address and which is running DECnet. If standby use-bia is not configured then HSRP would normally set the interface MAC address to the HSRP virtual MAC address but this is not allowed if DECnet is running. |
hsrp |
"Enable standby use-bia on the interface." |
|
HSRP-3-NOSOCKET |
3-Error |
Unable to open socket |
The system was unable to initialize an IP connection for the Hot Standby protocol. |
hsrp |
"Make sure that there is at least one interface configured to run " "IP." |
|
HSRP-4-BADAUTH |
4-Warning |
Bad authentication from [chars] group [dec] remote state [chars] |
Two routers participating in HSRP disagree on the valid authentication string. |
hsrp |
"Use the standby authentication command to repair the HSRP authentication \n\ discrepancy between the local system and the one whose IP address \n\ is reported." |
|
HSRP-4-BADAUTH2 |
4-Warning |
Bad authentication from [chars] |
Two routers participating in HSRP disagree on the valid authentication string. |
hsrp |
"Use the standby authentication command to repair the HSRP authentication " "discrepancy between the local system and the one whose IP address " "is reported." |
|
HSRP-4-BADVIP |
4-Warning |
[chars] Grp [dec] address [chars] is in the wrong subnet for this interface |
The HSRP virtual IP address contained in the Hello message cannot be learnt as it is not within a subnet configured on the interface. |
hsrp |
"Check the configuration on all HSRP routers and ensure " "that the virtual IP address is within a configured subnet." |
|
HSRP-4-DIFFVIP1 |
4-Warning |
[chars] Grp [dec] active routers virtual IP address [chars] is different to the locally configured address [chars] |
The HSRP virtual IP address contained in the Hello message from the Active router is different from the virtual IP address configured locally. |
hsrp |
"Check the configuration on all HSRP routers in the group " "and ensure they are all configured with the same virtual " "IP address." |
|
HSRP-4-DUPADDR |
4-Warning |
Duplicate address [chars] on [chars] sourced by [enet] |
The IP address in an HSRP message received on the specified interface is the same as the IP address of the router. Another router might be configured with the same IP address. The most likely cause is a network loop or a misconfigured switch that is causing the router to see its own HSRP Hello messages. |
hsrp |
"Check the configurations on all the HSRP routers to ensure " "that the interface IP addresses are unique. Check that no " "network loops exist. If port channels are configured check " "that the switch is correctly configured for port-channels. " "Enable standby use-bia so that the error message displays " "the interface MAC address of the sending router. This can " "be used to determine if the error message is caused by a " "misconfigured router or a network loop." |
|
HSRP-4-DUPVIP1 |
4-Warning |
[chars] Grp [dec] address [chars] is already assigned to [chars] group [dec] |
The HSRP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to a different HSRP group. |
hsrp |
"Check the configuration on all HSRP routers and ensure " "that the virtual IP address of each HSRP group is unique." |
|
HSRP-4-DUPVIP2 |
4-Warning |
[chars] Grp [dec] address [chars] is already assigned on this interface |
The HSRP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to this interface. |
hsrp |
"Check the configuration on all HSRP routers and ensure " "that the virtual IP address of each HSRP group is unique." |
|
HSRP-4-DUPVIP3 |
4-Warning |
[chars] Grp [dec] address [chars] is already assigned to or overlaps with an address on another interface or application |
The HSRP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to or overlaps with an address on another interface or application. |
hsrp |
"Check the configuration on all HSRP routers and ensure " "that the virtual IP address of each HSRP group is unique." |
|
HSRP-5-STATECHANGE |
5-Notice |
[chars] Grp [dec] state [chars] -> [chars] |
The router has changed state |
hsrp |
LOG_STD_NO_ACTION |
|
HTSP-3-CADENCENOTSUPPORTED |
3-Error |
voice port [chars]: ring cadence not suitable for caller id. on_time_first=[dec] off_time_first=[dec] on_time_second=[dec] off_time_second=[dec] |
Ring off period is not sufficient for caller id transmission.\n\ If caller id transmission during ring is configured make sure\n\ that the ring off duration is long enough. |
- |
"If caller id transmission during ring is configured make sure\n\ that the ring off duration is long enough. Make sure that the\n\ cptone setting and caller-id alerting settings are correct." |
|
HTSP-3-CAPABILITYMISMATCH |
3-Error |
voice port [chars]: call connection id [0x[hec] 0x[hec] 0x[hec] 0x[hec]] |
There was a capabilities mismatch between the two call legs.\n\ capabilities are negotiated between call legs for CODEC VAD and\n\ FAX rate. |
- |
"Check that the dial peer configuration is appropriate for the interface\n\ in question. Also check that and configuration on the interface is\n\ correct." |
|
HTSP-3-DSPALARM |
3-Error |
voice port [chars]: status=0x[hec] message=0x[hec] text=[chars] |
The DSP reported a fatal error. All calls on the DSP were dropped\n\ and a DSP reload was attempted. |
- |
"Verify that the DSP reloaded properly by attempting to place a call\n\ on the affected voice port. Contact your technical support\n\ representative include the full text of the error message." |
|
HTSP-3-NOEVENT |
3-Error |
no free event structure available from [chars] for DSP message |
There were no event structures remaining in the system pools to alert the\n\ router of a voice or signaling event. |
- |
"Check that the voice port for which the event was reported is\n\ still operational. If not clear the voice port." |
|
HTSP-3-TRUNKNOTSUPPORTED |
3-Error |
voice port [chars]: Ground Start trunking not supported |
This voice port does not support the 'connection trunk' command when\n\ ground start signaling is configured. Trunking mode on this voice\n\ is supported when using loop start signaling. |
- |
"Shut down the voice port remove the 'connection trunk' and/or\n\ 'signal groundStart' command from the voice port configuration\n\ and unshut the voice port." |
|
HTSP-5-UPDOWN |
5-Notice |
Trunk portchannel [[chars]] is [chars] |
Trunk port:channel changed state. |
- |
LOG_STD_NO_ACTION |
|
HTSP-5-VPM_BUSYOUT |
5-Notice |
voice port [chars]: [chars] busyout |
voice port busyout status changed |
- |
"use SHOW VOICE BUSYOUT to find out the reason why voice port busyout\n\ monitoring is triggered" |
|
HTSP-5-VPM_CABLE_STAT |
5-Notice |
voice port [chars]: cable [chars] |
Cable for analog voice port is reconnected or removed |
- |
"Check the cable connection for this analog voice port" |
|
HTSP-5-VPM_PCM_CAPTURE |
5-Notice |
User trigger PCM capture is [chars] on voice port [chars] |
User trigger PCM capture is enabled or disable on this voice port |
- |
"This is just for information only" |
|
HTTP_ALG-3-CHUNK_CREATE_FAIL |
3-Error |
- |
This message indicates detection of an HTTP Java applet in a response |
cpp-ucode |
"This message is for informational purposed only but may indicate" " a security problem." |
|
HTTP-3-INIT_FAIL |
3-Error |
\ HTTP Process Init failed. |
Initialization of the HTTP Subsystem has failed |
http |
"Reduce other system activity to ease memory demands. If " "conditions warrant upgrade to a larger memory configuration. " |
|
HTTP-3-OUTOF_MEM |
3-Error |
\ HTTP out of memory. |
An error occurred during initialization of the HTTP process. The HTTP process could not create crucial internal data structures that are required for operation of the HTTP subsystem. The most likely reason for this condition is an exhaustion of system memory. |
http |
"Reduce other system activity to ease memory demands. if " "conditions warrant upgrade to a larger memory configuration. " |
|
HTTP-3-PROC_NOCREAT |
3-Error |
\ Unable to create HTTP process. |
An error occurred during initialization of the HTTP process. The HTTP process that processes all HTTP requests and responses could not be created. |
- |
"Reduce other system activity to ease memory demands. If " "conditions warrant upgrade to a larger memory configuration. " |
|
HTTP-4-SERVER_CONN_RATE_EXCEED |
4-Warning |
\ Number of connections per minute has exceeded the maximum limit[dec] |
The message indicates that the current number of connections requested per minute has exceeded the limit specified by the platform. HTTP server will resume accepting the connections 15 seconds from the time the message is issued. This restriction is done as per the HTTP throttling functionality. |
http |
"Reduce connection rate to the server." |
|
HTTP-6-SERVER_SETUP_FAILED |
6-Information |
\ Server setup failed |
Setup of the HTTPS server to listen on the specified port number has failed. |
http |
"Disable the server verify that port number is correct " "and enable the server." "Reduce other system activity to ease memory demands. If " "conditions warrant upgrade to a larger memory configuration. " |
|
HTTPC-3-CACHE_MEM |
3-Error |
\ HTTP Client Cache Init out of memory. |
- |
- |
- |
|
HTTPC-3-CONNECT_NULL |
3-Error |
\ NULL connection structure for fd[dec] - closing socket. |
The HTTP Client is receiving the socket READ event but it fails to locate the connection structure for this file descriptorfd. |
- |
"Record the error and traceback and report it to the system administrator." |
|
HTTPC-3-COOKIE_MEM |
3-Error |
\ HTTP Client runs out of allowable memory to store cookies. |
The total memory allocated for storing cookies has run out. All cookies received from the HTTP server will be dropped. Users may no longer be able to interact with a session-based origin server until memory is freed up. |
- |
"Users may want to try their requests at a later time or contact the " "system administrator to increase the maximum RAM allowed for saving " "HTTP cookies." |
|
HTTPC-3-INIT_FAIL |
3-Error |
\ HTTP Client Process Init failed. |
- |
- |
- |
|
HTTPC-3-OUTOF_MEM |
3-Error |
\ HTTP Client out of memory. |
- |
- |
- |
|
HTTPC-3-OUTOF_SYNC |
3-Error |
\ HTTP Client header tables out of sync. |
- |
- |
- |
|
HTTPC-3-PROC_NOCREAT |
3-Error |
\ Unable to create HTTP Client process. |
- |
- |
- |
|
HTTPC-3-RECEIVE_SOCK_READ_EVENT_WHILE_DISABLED |
3-Error |
\ Received socket read event while read interest is disabled callID[dec] fd[dec] - closing socket. |
The HTTP Client is receiving the socket READ event while the READ interest is being disabled. Something has gone wrong between the http client and the socket interfaced. |
- |
"Record the error and report it to the system administrator." |
|
HTTPC-6-CLOSE_SRV_CONNECT |
6-Information |
\ The connection to server [inet] appears to be hung and will be closed. |
Messages are being backed up in the HTTP Client's write queue in the connection with the specified server. The connection is assumed to have gone bad and the HTTP Client is closing the connection. |
- |
"Check with the specified server for possible connection error." |
|
HTTPC-6-CONNECT_FAILED |
6-Information |
\ The connection to server [inet] failed |
- |
- |
- |
|
HTTPC-6-REQUEST_FAILED |
6-Information |
\ request URI [chars] failed |
- |
- |
- |
|
HUJR-3-RDWRFAIL |
3-Error |
Read/write failed [[chars]] |
A read/write error occurred when accessing the hardware |
- |
LOG_STD_ACTION |
|
HUNTGRP-3-INVALID_URL |
3-Error |
Could not open the file provided in URL: <[chars]> |
URL path provided can't be accessed. This usually indicates\n\ that path provided is invalid but may also be because the the\n\ path doesn't allow anonymous access to create files or open it\n\ in write mode |
cme-callcontrol |
"Check that the url path provided is valid" |
|
HUNTGRP-3-WRITE_FAIL |
3-Error |
Could not write data to the URL: <[chars]>\n\t %%bytes written=[dec] out of [dec] |
Write attempt to the url path provided was unsuccessful. This usually \n\ indicates that the file was successfully opened with write and append \n\ permissions but writing all the content from buffer or may be some of \n\ it to the file failed. |
cme-callcontrol |
"" |
|
HW_API-3-BACKWALK_REQUEST |
3-Error |
Backwalk request failed [chars] |
A request to walk internal data structures has failed. Depending on criticality of the data accuracy of forwarding may impacted. |
COMMON_HW_API_DDTS_COMPONENT |
LOG_STD_ACTION |
|
HW_API-3-BACKWALK_REQUEST_VALUE |
3-Error |
Backwalk request failed [chars] 0x[hec] |
- |
- |
- |
|
HW_API-3-INIT_FAIL |
3-Error |
HW-API init [chars] failed[chars] |
HW_API_INTERNAL_ERROR |
HW_API_DDTS_COMPONENT |
LOG_STD_ACTION |
|
HW_API-3-INVALID_CONTEXT |
3-Error |
Invalid context 0x[hec] |
HW_API_INTERNAL_ERROR |
HW_API_DDTS_COMPONENT |
LOG_STD_ACTION |
|
HW_API-3-INVALID_OBJ |
3-Error |
Invalid object 0x[hec] |
HW_API_INTERNAL_ERROR |
HW_API_DDTS_COMPONENT |
LOG_STD_ACTION |
|
HW_API-3-INVALID_TYPE |
3-Error |
Invalid type [dec] |
HW_API_INTERNAL_ERROR |
HW_API_DDTS_COMPONENT |
LOG_STD_ACTION |
|
HW_API-3-INVALID_WALK_SPEC |
3-Error |
Invalid walk spec 0x[hec] |
HW_API_INTERNAL_ERROR |
HW_API_DDTS_COMPONENT |
LOG_STD_ACTION |
|
HW_API-3-NO_OBJ_TYPE_LIST_ENTRY |
3-Error |
Invalid sw_obj_type [dec] used with obj_type_list |
- |
- |
- |
|
HW_API-3-NO_OBJ_TYPE_LIST_ENTRY2 |
3-Error |
Invalid sw_obj_link_type [dec] used with obj_type_list |
- |
- |
- |
|
HW_API-3-RESILIENCE_NO_HANDLER |
3-Error |
No handlers in place for [chars] sw object creation failure. |
COMMON_HW_API_INTERNAL_ERROR |
COMMON_HW_API_DDTS_COMPONENT |
LOG_STD_ACTION |
|
HW_API-3-VECTOR |
3-Error |
Failed to set [chars] vector for [chars] [chars] |
HW_API_INTERNAL_ERROR |
COMMON_HW_API_DDTS_COMPONENT |
LOG_STD_ACTION |
|
HW_API-3-WALK_MODE_UNSUPPORTED |
3-Error |
Walk mode '[chars]' unsupported |
HW_API_INTERNAL_ERROR |
HW_API_DDTS_COMPONENT |
LOG_STD_ACTION |
|
HW_FLOWDB-3-HW_FLOWDB_DBLDEL_FEATOBJ |
3-Error |
FlowDB featobj cannot be deleted twice. |
A feature attempted to remove a feature object pointer in flowDB that was already removed |
- |
"Bug in feature code track down why this happened" |
|
HW_FLOWDB-3-HW_FLOWDB_DBLINSTALL_FEATOBJ |
3-Error |
FlowDB featobj cannot be installed twice. |
A feature attempted to install a feature object pointer in flowDB that was already populated |
- |
"Bug in feature code track down why this happened" |
|
HW_FLOWDB-3-HW_FLOWDB_IMPRECISE_INVALID_PROTOCOL |
3-Error |
FlowDB imprecise API detected invalid protocol '[dec]'. |
A feature attempted to install an imprecise flow using an invalid protocol |
- |
"Bug in feature code track down why this happened" |
|
HW_FLOWDB-3-HW_FLOWDB_INVALID_FEATOBJ |
3-Error |
FlowDB core [dec] detected invalid featobj owned by core [dec]. |
A feature attempted to validate a BAD feature object pointer in flowDB |
- |
"Bug in feature code track down why this happened" |
|
HW_FLOWDB-3-HW_FLOWDB_NOT_OWNER |
3-Error |
FlowDB featobj remove attempted on core not owning flow. |
A feature attempted to remove a featobj from a BAD flowDB entry |
- |
"Bug in feature code track down why this happened" |
|
HW_FLOWDB-3-HW_FLOWDB_NULL_FEATOBJ |
3-Error |
FlowDB featobj install attempted with invalid pointer. |
A feature attempted to install a NULL feature object pointer in flowDB |
- |
"Bug in feature code track down why this happened" |
|
HW_FLOWDB-3-HW_FLOWDB_OOM |
3-Error |
FlowDB memory usage exceeded 95%% usage. OOM condition can occur. |
FlowDB running low on memory. Out-of-memory condition can occur |
cpp-ucode |
"Check sw-distrib for actual utilization of FlowDB memory" |
|
HW_FLOWDB-3-HW_FLOWDB_OOM_RECOVER |
3-Error |
FlowDB memory usage recovered. Memory usage no longer exceeds 95%% |
FlowDB recovered from low memory. |
cpp-ucode |
"Check sw-distrib for actual utilization of FlowDB memory" |
|
HW_FLOWDB-3-HW_FLOWDB_STALE_FEATOBJ |
3-Error |
FlowDB featobj remove attempted on stale entry. |
A feature attempted to remove a feature object pointer in flowDB from a stale flow |
- |
"Bug in feature code track down why this happened" |
|
HW_FLOWDB-3-HW_FLOWDB_VALIDATE_NO_MATCH |
3-Error |
FlowDB failed to find matching flow during validation. |
A feature attempted to validate an installed flow. |
- |
"No recommended action. Output is used as a debug aid." |
|
HW_TIME-2-HB_TICK_DISCARD |
2-Critical |
%llums since last timer heartbeat processed |
Something caused us to go long durations without processing timer heartbeats |
- |
"sh plat hard qfp act da inf time basic"msgdef_tac_details |
|
HW-2-OBSOLETE_HW_VER |
2-Critical |
Module Version in [chars] is obsolete\n\ *********************************************************************\n\ * IMPORTANT !!! *\n\ * The module in [chars] is obsolete and must be returned *\n\ * via RMA to Cisco Manufacturing. If it is a lab unit * \n\ * it must be returned to Proto Services for upgrade. *\n\ *********************************************************************\n |
The Smart Cookie is obsolete and need to be replaced ASAP. |
c2800 |
"Contact TAC" LOG_STD_RECUR_ACTION |
|
HWMATM_MOD-3-NULLPTR |
3-Error |
Unexpected null pointer in [chars] at [dec] |
An internal software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
I2C-3-ACCESS_ERR |
3-Error |
I2C access error [chars] for device [dec] |
I2C device initialization error |
cmts-platform |
"Copy the error message exactly as it appears and report it to your " "technical support" |
|
I2C-3-CONFIG_ERR |
3-Error |
I2C config failure [chars] for device [dec] value 0x[hec] |
I2C device configuration error |
cmts-platform |
"Copy the error message exactly as it appears and report it to your " "technical support" |
|
I2C-5-LTC4306 |
5-Notice |
sanity check failed: device 0x[hec] channel [dec] action [chars] retry [dec] read back 0x[hec] |
- |
cmts-platform |
- |
|
IAMP-4-CLIENT_ID_EXIST |
4-Warning |
Client id [[dec]] already exists |
client id already exists in the database. Choose unique ID to solve this issue |
mediatrace |
"Applications could be re-registering or client id is in use by " "other application. If it is not due to duplicate registration " "it may be advisable to contact your Cisco technical support " "representative." |
|
IAMP-4-CLIENT_REG_FAILED |
4-Warning |
Client id [[dec]] could not be registered |
Error occured while registering the client. |
mediatrace |
"Collect show memory summary and contact your Cisco " "technical support representative." |
|
ICC-2-JOIN |
2-Critical |
ICC mcast joining failed member <0x[hec]> to group <0x[hec]> with ipc error <[chars]> |
ICC was not able to join a member for the mcast group |
c7600-system |
"collect output 'show icc mcast status' from RP" |
|
ICC-2-NOMEM |
2-Critical |
No memory available for [chars] |
The ICC subsystem could not obtain the memory it needed. |
icc |
LOG_STD_SH_TECH_ACTION |
|
ICC-2-OPEN |
2-Critical |
ICC Create Session Failed for card <0x[hec]> Queue <[chars]> |
ICC was not able to create a session for the destination seat |
icc |
"collect output from 'show oir debug swover_global_mask' from SP" |
|
ICC-3-MAST_BAD_FREE |
3-Error |
ICC multicast memory already freed |
One of the ICC multicast request's memory was found to be free when response arrived |
icc |
LOG_STD_SH_TECH_ACTION |
|
ICC-4-BAD_ACCOUNTING |
4-Warning |
ICC received a bad class [dec] |
A communication failure has occurred between this card and\n\ another card in the system. |
icc |
LOG_STD_SH_TECH_ACTION |
|
ICC-4-COMM |
4-Warning |
Communication failure occurred while [chars] |
- |
- |
- |
|
ICC-4-CONSISTENCY |
4-Warning |
Internal consistency check: [chars] |
An internal inconsistency was found in some ICC data structures. |
icc |
LOG_STD_SH_TECH_ACTION |
|
ICC-4-HEARTBEAT |
4-Warning |
Card [dec] failed to respond to heartbeat |
A communication failure has occurred between the primary and\n\ the specified line card. |
icc |
LOG_STD_SH_TECH_ACTION |
|
ICC-5-HUGE_BUFFER |
5-Notice |
Class [[chars]] with Request id [dec] requested a huge buffer of Size [dec]. |
Huge packet requests would deplete the memory at the linecards |
- |
"ICC client is trying to request huge packet buffer " "Please use the command Show icc internal to get " "get the traceback and file a DDTS against the component" |
|
ICC-5-WATERMARK |
5-Notice |
[dec] [chars] [chars] pkts for class [chars] are waiting to be processed |
Processor got packets for the class and are waiting to be procssed |
icc |
LOG_STD_SH_TECH_ACTION |
|
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 |
|
IDB_IDENTITY-3-MALLOC |
3-Error |
Memory allocation failure for HWIDB type [dec] |
A memory allocation failure occured when trying to allocate the identity for this HWIDB. This HWIDB will not be allocated an IF Index which will prevent it from being used for forwarding data. |
ha-ifindex-sync |
LOG_STD_ACTION |
|
IDB_SGI-2-MEMREQ |
2-Critical |
[chars] |
An internal software error occurred. |
idb |
LOG_STD_ACTION |
|
IDB_SGI-2-XDRREG |
2-Critical |
[chars] |
An internal software error occurred. |
idb |
LOG_STD_ACTION |
|
IDB_SGI-3-BADPTR |
3-Error |
[chars] of interface with ifindex [dec] is invalid |
An internal software error occurred. |
Owners of the interface |
LOG_STD_ACTION |
|
IDB_SGI-3-MEMFAIL |
3-Error |
[chars] |
An internal software error occurred. |
idb |
LOG_STD_ACTION |
|
IDB_SGI-3-XDRREQ |
3-Error |
[chars] |
An internal software error occurred. |
xdr |
LOG_STD_ACTION |
|
IDB_SGI-4-INTERR |
4-Warning |
[chars] for interface with ifindex [dec] |
An internal software error occurred. |
idb |
LOG_STD_ACTION |
|
IDB_SGI-4-MEMBERREQ |
4-Warning |
member request failure for interface with ifindex [dec]\n returned err - [chars] |
An internal software error occurred. |
sgi |
LOG_STD_ACTION |
|
IDB_SGI-4-UNEXPINP |
4-Warning |
[chars] |
An internal software error occurred. |
idb |
LOG_STD_ACTION |
|
IDBINDEX_SYNC_KEY-3-UNKNOWN_TYPE |
3-Error |
Interface type is unknown and cannot be synced: \[chars]\ [dec] |
An internal software error has occurred. |
IDBINDEX_SYNC_DDTS_COMP |
LOG_STD_ACTION |
|
IDBINDEX_SYNC-3-IDBINDEX_ASSIGN |
3-Error |
Failed to assign an index to IDB type [dec] for interface \[chars]\ rc=[dec] |
An IF-Index can not be allocated for this interface due to an internal software error. This is an unrecoverable error that results in this interface not being usable for traffic. |
IDBINDEX_SYNC_DDTS_COMP |
LOG_STD_ACTION IDBINDEX_SYNC_LOG_STD_ACTION |
|
IDBINDEX_SYNC-3-IDBINDEX_ENTRY_MISMATCH |
3-Error |
An interface index mismatched its active table entry: \[chars]\ type [dec] table index=[dec] interface index=[dec] |
An interface index was found which didn't match the active interface index table entry with the corresponding sync key due to an internal software error. |
IDBINDEX_SYNC_DDTS_COMP |
LOG_STD_ACTION IDBINDEX_SYNC_LOG_STD_ACTION |
|
IDBINDEX_SYNC-3-IDBINDEX_INITKEY |
3-Error |
Cannot initialize interface index table lookup key: \[chars]\ [dec] |
An internal software error has occurred. |
IDBINDEX_SYNC_DDTS_COMP |
LOG_STD_ACTION IDBINDEX_SYNC_LOG_STD_ACTION |
|
IDBINDEX_SYNC-3-IDBINDEX_LINK |
3-Error |
Driver for IDB type '[dec]' changed the Identity of interface \[chars]\ without deleting the old Identity first rc=[dec] |
The IF-Index Table can not be updated with the new Identity provided for this interface due to an internal software error. Most likely the old Identity was not deleted first by the driver or that the driver accidentily changed the Identity. |
IDBINDEX_SYNC_DDTS_COMP |
LOG_STD_ACTION IDBINDEX_SYNC_LOG_STD_ACTION |
|
IDBINDEX_SYNC-3-IDBINDEX_RETRIEVE |
3-Error |
Cannot retrieve if-index for this interface: \[chars]\ [dec] [chars] [chars] |
The interface index number was not found in the interface index table for the interface specified in the error message. This condition might have been caused by the interface index number not being properly synchronized by the primary processor card. |
IDBINDEX_SYNC_DDTS_COMP |
LOG_STD_ACTION IDBINDEX_SYNC_LOG_STD_ACTION |
|
IDBINDEX_SYNC-3-INIT_ERR |
3-Error |
[chars] |
The interface index sync ISSU client has an initialization error. |
IDBINDEX_SYNC_DDTS_COMP |
LOG_STD_ACTION IDBINDEX_SYNC_LOG_STD_ACTION |
|
IDBINDEX_SYNC-3-IPC_ERR |
3-Error |
[chars]: [chars] in domain [dec]. |
The interface index sync IPC session has error. |
IDBINDEX_SYNC_DDTS_COMP |
LOG_STD_ACTION IDBINDEX_SYNC_LOG_STD_ACTION |
|
IDBINDEX_SYNC-3-ISSU_ERR |
3-Error |
[chars][chars] rc=[dec] |
The interface index sync ISSU client has error. |
IDBINDEX_SYNC_DDTS_COMP |
LOG_STD_ACTION IDBINDEX_SYNC_LOG_STD_ACTION |
|
IDBINDEX_SYNC-3-LIST_REMOVE |
3-Error |
Failed to remove node from the if-index entry list |
When an if-index lookup failed on the Standby the process waits on timer till the standby receives the if-index or the timer expires To know which processes are waiting a list will be maintained and when any of the above mentioned events occured the corresponding node from the list will be removed |
IDBINDEX_SYNC_DDTS_COMP |
LOG_STD_ACTION IDBINDEX_SYNC_LOG_STD_ACTION |
|
IDBINDEX_SYNC-3-RF_ERR |
3-Error |
[chars] [dec] . |
The interface index sync RF client has an error. |
IDBINDEX_SYNC_DDTS_COMP |
LOG_STD_ACTION IDBINDEX_SYNC_LOG_STD_ACTION |
|
IDBINDEX_SYNC-3-TRANSFORM |
3-Error |
Require IF-Index ISSU transformation function [chars] [chars] |
IF-Index Sync has identified a missing ISSU transformation function which may lead to unpredictable results. This must be resolved before the code is released. |
IDBINDEX_SYNC_DDTS_COMP |
"Contact IF-Index Sync development team with the contents of the " "configuration and error message so that the driver may be identified." |
|
IDBINDEX_SYNC-3-VALIDATE |
3-Error |
Cannot validate if-index for this interface: \[chars]\ [dec] [chars] [chars] |
The identity of this interface could not be validated against the stored identity within the IDB Index table. This condition is likely to have occured due to the identity of the IDB changing without first explicitly unlinking the previous identity. |
IDBINDEX_SYNC_DDTS_COMP |
LOG_STD_ACTION IDBINDEX_SYNC_LOG_STD_ACTION |
|
IDBINDEX_SYNC-4-RESERVE |
4-Warning |
Failed to lookup existing ifindex for an interface on the Standby allocating a new ifindex from the Active ifindex=[dec] idbtype=[chars] |
Encountered a lookup failure for an interface on the Standby. An attempt has been amde to resolve the issue by reserving a possibly new ifindex on the Active. If this situation was encountered due to a defect in the key encoding then traffic may stop on this interface should the system switchover. |
IDBINDEX_SYNC_DDTS_COMP |
LOG_STD_ACTION IDBINDEX_SYNC_LOG_STD_ACTION |
|
IDBINDEX_SYNC-4-TRUNCATE |
4-Warning |
Overflow in [chars] when encoding interface sync key got [dec] maximum is [dec] |
When creating a unique sync key to represent an interface it has been detected that one of the attributes making up the key was truncated to fit in the allocated space in the key. This may lead to overlapping key allocations which would cause an error. |
IDBINDEX_SYNC_DDTS_COMP |
LOG_STD_ACTION IDBINDEX_SYNC_LOG_STD_ACTION |
|
IDBMAN-3-AGGPORTMISMATCH |
3-Error |
[chars][dec] / [dec] does match internal slot/port state [chars][dec] / [dec] |
There is an internal error that caused an invalid aggregate port\n\ to be used by the software. |
<platform> |
LOG_STD_ACTION |
|
IDBMAN-3-DELETEDAGGPORT |
3-Error |
[chars][dec] / [dec] Group [dec] has been deleted but is being reused. |
There is an internal error that caused an interface that has been deleted\n\ to be reused for a new aggregate port. |
<platform> |
LOG_STD_ACTION |
|
IDBMAN-3-IIF_ID_REGISTRATION_FAILED |
3-Error |
IIF_ID registration failed for Port [chars] due to memory allocation failure. Port has been shutdown |
The system is low on memory due to which IIF-ID registration failed. This results in failure to apply polices such as QoS and Security acls on this port. |
<platform> |
LOG_STD_REDUCE_ACTION "Once memory is available " "run 'no shutdown' on the port." |
|
IDBMAN-3-INVALIDAGGPORTBANDWIDTH |
3-Error |
[chars][dec] / [dec] has an invalid bandwidth value of [dec] |
There is an internal error that caused an invalid bandwidth to be used\n\ for an aggregate port. |
<platform> |
LOG_STD_ACTION |
|
IDBMAN-3-INVALIDPORT |
3-Error |
[chars]: trying to use invalid port number [dec] Max [dec] |
There is an internal error that caused an invalid port numer to be used\n\ by the software. |
<platform> |
LOG_STD_ACTION |
|
IDBMAN-3-INVALIDVLAN |
3-Error |
[chars]: trying to use invalid Vlan [dec] |
There is an internal error that caused an invalid Vlan to be used \n\ by the software. |
<platform> |
LOG_STD_ACTION |
|
IDBMAN-3-NOTANAGGPORT |
3-Error |
[chars] [dec] / [dec] is not an aggregate port |
There is an internal error that caused an interface that is not an aggregate\n\ port to be used for aggregate port operations |
<platform> |
LOG_STD_ACTION |
|
IDBMAN-3-PORTNOTINAGGPORT |
3-Error |
[chars][dec] / [dec] is not present in Aggport [chars][dec] / [dec] |
There is an internal error that caused an invalid port to be referred\n\ to be part of an aggregate port. |
<platform> |
LOG_STD_ACTION |
|
IDBMAN-3-VLANINUSE |
3-Error |
[chars]: Vlan [dec] is in use by [chars] |
Each L3 interface has a Vlan associated with it. This message indicates \n\ that the Vlan associated with the interface is being used by some other \n\ L3 Interface which is not anticipated to happen |
<platform> |
LOG_STD_NO_ACTION |
|
IDBMAN-3-VLANNOTSET |
3-Error |
[chars]: Vlan [dec] not set since it already has Vlan [dec] |
There is an internal error that caused an interface to not have its\n\ Vlan set to the requested value |
<platform> |
LOG_STD_ACTION |
|
IDBMAN-4-ACTIVEPORTSINAGGPORT |
4-Warning |
[chars] [dec] / [dec] has [dec] active ports but is being removed |
There is an internal error that caused an aggregate port with active ports\n\ to be removed |
<platform> |
LOG_STD_ACTION |
|
IDBMAN-4-REMOVED_NONDEFAULT_CONFIG |
4-Warning |
Removed non default configuration for interfaces in [chars] |
In SSO mode the non-default configuration for any removed linecard is\n\ not synced to the standby during the bulk sync and it is removed from\n\ the configuration to avoid a config mismatch between active and standby\n\ supervisors. |
<platform> |
LOG_STD_NO_ACTION |
|
IDBMAN-6-VLANMAPPED |
6-Information |
Vlan [dec] is mapped to [chars] |
Informational message indicating that the given Vlan is mapped \n\ to the given interface |
<platform> |
LOG_STD_NO_ACTION |
|
IDENT-4-LDP |
4-Warning |
ERRMSG_LIMIT_SLOW*15 |
- |
- |
- |
|
IDMGR-3-ID_MANAGER_INTERNAL_ERROR |
3-Error |
[chars] |
Internal Error occured with ID Manager. |
os |
LOG_STD_ACTION |
|
IDMGR-3-INTERRUPT |
3-Error |
[chars] |
An id_get attempted at interrupt level. |
- |
LOG_STD_ACTION |
|
IDMGR-3-INVALID_ID |
3-Error |
bad id in [chars] id: 0x%lX |
An ID Manager error occurred. |
- |
LOG_STD_ACTION |
|
IDMGR-3-INVALID_ID_TABLE_SIZE |
3-Error |
bad new ID table size |
A bad new table request to ID Manager occurred. |
- |
LOG_STD_ACTION |
|
IDMGR-3-MALLOC_FAILURE |
3-Error |
[chars] |
A malloc failure occured in ID Manager. |
- |
LOG_STD_ACTION |
|
IDMNGR-3-CORECTXALLOC |
3-Error |
Error: Unable to handle request %08x |
Unable to handle a client request |
identity |
"Contact support" |
|
IDMNGR-3-EMPTYREQ |
3-Error |
Error: empty request received |
Unable to handle a client request/event |
identity |
"Contact support" |
|
IDMNGR-3-INVALIDARG |
3-Error |
Error: Argument [chars] with NIL value |
Internal software error |
identity |
"Contact support" |
|
IDMNGR-3-INVALIDEVENT |
3-Error |
Error: Invalid process event received [dec] |
Internal process error |
identity |
"Contact support" |
|
IDMNGR-3-INVALIDREQUEST |
3-Error |
Error: Invalid request type received [dec] |
Unable to handle a client request |
identity |
"Contact support" |
|
IDMNGR-3-NOPROCESS |
3-Error |
Error: NO idmgr process |
Internal software error |
identity |
"Contact support" |
|
IDMNGR-3-PROCNAME |
3-Error |
Error: Unable to get idmgr process name for request %08x |
Unable to handle a client request/event |
identity |
"Contact support" |
|
IDMNGR-7-ALLOCFAIL |
7-Debug |
Error: Failed to allocate memory for [chars] |
Internal software error |
identity |
"Contact support" |
|
IDS-4-ICMP_ECHO_REPLY_SIG |
4-Warning |
Sig:2000:ICMP Echo Reply - from [inet] to [inet] |
- |
ids |
"This is extremely common network traffic. Suspicion should be\n\raised when a large number of these packets are found on the network. If no\n\legitimate reason for this traffic can be identified prudent security\n\practices would suggest that the source be shunned." |
|
IDS-4-ICMP_ECHO_SIG |
4-Warning |
Sig:2004:ICMP Echo Request - from [inet] to [inet] |
- |
ids |
"The ICMP Echo Request is issued by the source to determine\n\if the destination is ''alive''. When the destination receives the request\n\it will reply with an ICMP Echo Reply. This request/reply pair is most\n\commonly implemented via the ''ping'' utility. Many network management tools\n\use this utility or some derivative. This is extremely common network\n\traffic. Suspicion should be raised when a large number of these packets are\n\found on the network. If no legitimate reason for this traffic can be\n\identified prudent security practices would suggest that the source be\n\shunned." |
|
IDS-4-ICMP_FRAGMENT_SIG |
4-Warning |
Sig:2150:Fragmented ICMP Traffic - from [inet] to [inet] |
- |
ids |
"IP datagrams may be fragmented normally as they are\n\transported across the network but ICMP is rarely fragmented. The traffic\n\should be investigated. If no legitimate reason for the fragmentation can be\n\found and especially if the packets seem to be originating from a single\n\source prudent security practices would suggest that the host be shunned." |
|
IDS-4-ICMP_INFO_REPLY_SIG |
4-Warning |
Sig:2010:ICMP Information Reply - from [inet] to [inet] |
Triggers when a IP datagram is received with the \n\ ''protocol'' field of the IP header set to 1 ICMP |
ids |
"This datagram type is obsolete and should not be\n\encountered. When non-specific network traffic of this type is encountered\n\the most prudent action from a security perspective is to shun or disallow\n\it. If the source of this traffic is legitimate the user will then identify\n\him or herself." |
|
IDS-4-ICMP_INFO_SIG |
4-Warning |
Sig:2009:ICMP Information Request - from [inet] to [inet] |
- |
ids |
"This datagram type is obsolete and should not be\n\encountered. When non-specific network traffic of this type is encountered\n\the most prudent action from a security perspective is to shun or disallow\n\it. If the source of this traffic is legitimate the user will then identify\n\him or herself." |
|
IDS-4-ICMP_MASK_REPLY_SIG |
4-Warning |
Sig:2012:ICMP Address Mask Reply - from [inet] to [inet] |
- |
ids |
"The ICMP Address Mask Request/Reply pair can be used to\n\determine the sublet mask used on the network. The requesting system issues\n\the Address Mask Request bound for a destination the destination system\n\responds with an Address Mask Reply message. This is normal network traffic\n\but is uncommon on most networks. Suspicion should be raised when a large\n\number of these packets are found on the network. If no legitimate reason\n\for this traffic can be identified prudent security practices would suggest\n\that the source be shunned." |
|
IDS-4-ICMP_MASK_SIG |
4-Warning |
Sig:2011:ICMP Address Mask Request - from [inet] to [inet] |
- |
ids |
"The ICMP Address Mask Request/Reply pair can be used to\n\determine the subnet mask used on the network. The requesting system issues\n\the Address Mask Request bound for a destination the destination system\n\responds with an Address Mask Reply message. This is normal network traffic\n\but is uncommon on most networks. Suspicion should be raised when a large\n\number of these packets are found on the network. If no legitimate reason\n\for this traffic can be identified prudent security practices would suggest\n\that the source be shunned." |
|
IDS-4-ICMP_PARAMPROB_SIG |
4-Warning |
Sig:2006:ICMP Parameter Problem on Datagram - from [inet] to [inet] |
Triggers when a IP datagram is received with the \n\ ''protocol'' field of the IP header set to 1 ICMP |
ids |
"ICMP Parameter Problem datagrams are issued when a router\n\has had to drop a datagram because it was malformed. This is a normal and\n\necessary type of network traffic. Large numbers of this datagram type on\n\the network are indicative of network difficulties or may be indicative of\n\hostile actions. If no network problems can be identified to account for the\n\traffic prudent security practices would suggest that the source be shunned." |
|
IDS-4-ICMP_PING_OF_DEATH_SIG |
4-Warning |
Sig:2154:ICMP Ping of Death Attack - from [inet] to [inet] |
- |
ids |
"This indicates a denial of service attack. It is likely that the source\n\address has been spoofed making shunning ineffective" |
|
IDS-4-ICMP_REDIRECT_SIG |
4-Warning |
Sig:2003:ICMP Redirect - from [inet] to [inet] |
- |
ids |
"The redirect message may be issued from a router to inform\n\a host of a better route to a requested destination. The host then updates\n\its routing table to include this route. This method of updating routing\n\tables is an uncommon practice today. When non-specific network traffic of\n\this type is encountered the most prudent action from a security\n\perspective is to shun or disallow it. If the source of this traffic is\n\legitimate the user will then identify him or herself." |
|
IDS-4-ICMP_SOURCEQUENCH_SIG |
4-Warning |
Sig:2002:ICMP Source Quench - from [inet] to [inet] |
- |
ids |
"This datagram may be used in network management to provide\n\congestion control. A source quench packet will be issued when a router is\n\beginning to lose packets due to the transmission rate of a source. The\n\source quench is a request to the source to reduce the rate of datagram\n\transmission. This datagram type is rarely if ever seen on networks and some\n\systems do not even support it. Large numbers of this datagram type on the\n\network are indicative of network difficulties or may be indicative of\n\hostile actions. If no network problems can be identified to account for the\n\traffic prudent security practices would suggest that the source be shunned." |
|
IDS-4-ICMP_TIME_REPLY_SIG |
4-Warning |
Sig:2008:ICMP Timestamp Reply - from [inet] to [inet] |
- |
ids |
"The ICMP Timestamp Request/Reply pair can be used to\n\synchronize system clocks on the network. The requesting system issues the\n\Timestamp Request bound for a destination the destination system responds\n\with a Timestamp Reply message. This is normal network traffic but is\n\uncommon on most networks. Suspicion should be raised when a large number of\n\these packets are found on the network. If no legitimate reason for this\n\traffic can be identified prudent security practices would suggest that the\n\source be shunned." |
|
IDS-4-ICMP_TIME_SIG |
4-Warning |
Sig:2007:ICMP Timestamp Request - from [inet] to [inet] |
- |
ids |
"The ICMP Timestamp Request/Reply pair can be used to\n\synchronize system clocks on the network. The requesting system issues the\n\Timestamp Request bound for a destination the destination system responds\n\with a Timestamp Reply message. This is normal network traffic but is\n\uncommon on most networks. Suspicion should be raised when a large number of\n\these packets are found on the network. If no legitimate reason for this\n\traffic can be identified prudent security practices would suggest that the\n\source be shunned." |
|
IDS-4-ICMP_TIMXCEED_SIG |
4-Warning |
Sig:2005:ICMP Time Exceeded for a Datagram - from [inet] to [inet] |
Triggers when a IP datagram is received with the \n\ ''protocol'' field of the IP header set to 1 ICMP and the ''type'' \n\msgdef_recommended_actionICMP Time Exceeded datagrams are issued when a router has\n\had to drop a datagram whose Time to Live |
- |
- |
|
IDS-4-ICMP_TOOLARGE_SIG |
4-Warning |
Sig:2151:Large ICMP Traffic - from [inet] to [inet] |
While it is possible to receive ICMP datagrams that have a\n\ size greater than 1024 bytes this is a highly unusual\n\ occurrence that warrants investigation. |
ids |
"While it is possible to receive ICMP datagrams that have a\n\size greater than 1024 bytes this is a highly unusual occurrence that\n\warrants investigation. If no legitimate reason for the large packet size\n\can be found and especially if the packets seem to be originating from a\n\single source prudent security practices would suggest that the host be\n\shunned." |
|
IDS-4-ICMP_UNREACH_SIG |
4-Warning |
Sig:2001:ICMP Host Unreachable - from [inet] to [inet] |
- |
ids |
"This is the common response provided to a client when there\n\is no path available to the requested host. This is a very common type of\n\network traffic. Large numbers of this datagram type on the network are\n\indicative of network difficulties or may be indicative of hostile actions.\n\If no network problems can be identified to account for the traffic prudent\n\security practices would suggest that the source be shunned." |
|
IDS-4-IP_IMPOSSIBLE_SIG |
4-Warning |
Sig:1102:Impossible IP Packet - from [inet] to [inet] |
This triggers when an IP packet arrives with source\n\ equal to destination address. This signature will\n\ catch the so-called Land Attack. |
ids |
"This should never occur in legitimate traffic." |
|
IDS-4-IP_UNKNOWN_PROTO_SIG |
4-Warning |
Sig:1101:Unknown IP Protocol - from [inet] to [inet] |
Triggers when an IP datagram is received with the protocol\n\ field set to 101 or greater. The use of these protocol\n\ types is highly unusual and should be investigated. |
ids |
"Locally developed protocols that may use \n\these protocol types will trigger the signature. The use of these \n\protocol types is highly unusual and should be investigated. When \n\non-specific network traffic of this type is encountered the most \n\prudent action from a security perspective is to shun or disallow it.\n\If the source of this traffic is legitimate the user will then \n\identify him or herself." |
|
IDS-4-IPFRAG_ATTACK_SIG |
4-Warning |
Sig:1100:IP Fragment Attack - from [inet] to [inet] |
Triggers when any IP datagram is received with the\n\ 'more fragments' flag set to 1 or if there is an\n\ offset indicated in the offset field. |
ids |
"IP datagrams may be fragmented normally as they\n\are transported across the network. This is not uncommon but is \n\unusual enough that the traffic should be investigated. This is \n\especially important if the network is protected by a packet \n\filtering firewall." |
|
IDS-4-IPOPT_LSRR_SIG |
4-Warning |
Sig:1004:IP options-Loose Source Route - from [inet] to [inet] |
Triggers on receipt of an IP datagram where the IP option\n\ list for the datagram includes option 3 Loose Source \n\ Route. This option may be misused to defeat |
ids |
"While network troubleshooting may require the \n\legitimate use of this feature this type of traffic is rarely if ever \n\noted and should comprise much less than 1% of network traffic. Small \n\amounts of source routed traffic most probably indicates that a \n\network problem is being investigated. Large amounts of source \n\routed traffic is more suspicious and a thorough investigation of the \n\source and reason is indicated." |
|
IDS-4-IPOPT_RR_SIG |
4-Warning |
Sig:1001:IP options-Record Packet Route - from [inet] to [inet] |
The IP options list contains one or more options that\n\ perform various network management or debugging tasks.\n\ This alarm may indicate a reconnaissance attack is in\n\ progress against your network. |
ids |
"While network troubleshooting may require \n\the legitimate use of this feature this is unusual traffic that warrants\n\investigation. When non-specific network traffic of this type is \n\encountered the most prudent action from a security perspective is \n\to shun or disallow it. If the source of this traffic is legitimate \n\the user will then identify him or herself." |
|
IDS-4-IPOPT_SATID_SIG |
4-Warning |
Sig:1005:IP options-SATNET ID - from [inet] to [inet] |
Triggers on receipt of an IP datagram where the IP\n\ option list for the datagram includes option 8 SATNET\n\ stream identifier. No known exploit exists. |
ids |
"This option is obsolete and should not be encountered. When\n\non-specific network traffic of this type is encountered the most \n\prudent action from a security perspective is to shun or disallow \n\it. If the source of this traffic is legitimate the user will then \n\identify him or herself." |
|
IDS-4-IPOPT_SECURITY_SIG |
4-Warning |
Sig:1003:IP options-Provide schtcc - from [inet] to [inet] |
Triggers on receipt of an IP datagram where the IP option\n\ list for the datagram includes option 2. No known \n\ exploit exists. |
ids |
"This signature will trigger if you have \n\implemented IP security options on your network However this is \n\rarely if ever implemented . When non-specific network traffic \n\of this type is encountered the most prudent action from a security \n\perspective is to shun or disallow it. If the source of this traffic \n\is legitimate the user will then identify him or herself." |
|
IDS-4-IPOPT_SSRR_SIG |
4-Warning |
Sig:1006:IP options-Strict Source Route - from [inet] to [inet] |
- |
ids |
"While network troubleshooting may require the legitimate use of this\n\feature this type of traffic is rarely if ever noted and should \n\comprise much less than 1% of network traffic. Small amounts of source \n\routed traffic most probably indicates that a network problem is being \n\investigated. Large amounts of source routed traffic is more suspicious \n\and a thorough investigation of the source and reason is indicated." |
|
IDS-4-IPOPT_TS_SIG |
4-Warning |
Sig:1002:IP options-TimeStamp - from [inet] to [inet] |
- |
ids |
"While network troubleshooting may require \n\the legitimate use of this feature this is unusual traffic that warrants\n\investigation. When non-specific network traffic of this type is \n\encountered the most prudent action from a security perspective is \n\to shun or disallow it. If the source of this traffic is legitimate \n\the user will then identify him or herself." |
|
IDS-4-IPOPTS_BAD_SIG |
4-Warning |
Sig:1000:Bad IP Option List - from [inet] to [inet] |
Triggers on receipt of an IP datagram where the list of IP \n\ options in the IP datagram header is incomplete or malformed.\n\ No known exploits purposely incorporate this option. |
ids |
"There is no legitimate use for malformed \n\datagrams. This may be indicative of systems that are experiencing \n\problems with their kernel or NIC cards. This is unusual traffic and \n\warrants investigation. When non-specific network traffic of this \n\type is encountered the most prudent action from a security perspective \n\is to shun or disallow it. If the source of this traffic is legitimate \n\the user will then identify him or herself." |
|
IDS-4-LOST_CONNECT |
4-Warning |
Connection to HostID:[dec] OrgID:[dec] |
Triggers when a connection drops and there is no previous \n\connection. |
ids |
"This message indicates that the IDS cannot communicate with the \n\Director. Check connectivity to the Director and check Postoffice\n\configuration on both the router and the Director." |
|
IDS-4-RPC_CALLIT_REQUEST |
4-Warning |
Sig:6103:Proxied RPC Request - from [inet] to [inet] |
Triggers when a proxied RPC request is sent to the portmapper\n\ of a target host. |
ids |
"If this procedure is allowed on your network those users\n\that employ it will trigger the signature. This may be a serious attempt at\n\gaining unauthorized access and if the source of the attempt is not within\n\your network they should be shunned." |
|
IDS-4-RPC_DUMP_REQUEST |
4-Warning |
Sig:6102:RPC Dump - from [inet] to [inet] |
Triggers when an RPC dump request isissued to a target host. |
ids |
"This is a common procedure performed by many system\n\administrators and wary users to determine which RPC services are being\n\offered. Executing this procedure is most likely due to curiosity on the\n\part of a novice user or a system administrator performing system\n\maintenance. If upon investigation no valid user can be associated with this\n\event prudent security practices would suggest shunning the source." |
|
IDS-4-RPC_PORTREQ_MOUNTD |
4-Warning |
Sig:6155:RPC mountd Portmap Request - from [inet] to [inet] |
Triggers when a request is made to the portmapper for the\n\ mount daemon mountd port. |
ids |
"If this procedure is allowed on your network those users\n\that employ it will trigger the signature. This may be a serious attempt at\n\gaining unauthorized access and if the source of the attempt is not within\n\your network they should be shunned." |
|
IDS-4-RPC_PORTREQ_REXD |
4-Warning |
Sig:6175: RPC rexd Portmap Request - from [inet] to [inet] |
- |
ids |
"If this procedure is allowed on your network those users\n\who employ it will trigger the signature. This may be a serious attempt at\n\gaining unauthorized access and if the source of the attempt is not within\n\your network it should be shunned." |
|
IDS-4-RPC_PORTREQ_YPBIND |
4-Warning |
Sig:6151:RPC ypbind Portmap Request - from [inet] to [inet] |
Triggers when a request is made to the portmapper for the YP\n\ bind daemon ypbind port. |
ids |
"If this procedure is allowed on your network those users\n\that employ it will trigger the signature. This may be a serious attempt at\n\gaining unauthorized access and if the source of the attempt is not within\n\your network they should be shunned." |
|
IDS-4-RPC_PORTREQ_YPPASSWDD |
4-Warning |
Sig:6152:RPC ypbind yppasswdd Portmap Request - from [inet] to [inet] |
Triggers when a request is made to the portmapper for the YP\n\ password daemon yppasswdd port. |
ids |
"If this procedure is allowed on your network those users\n\that employ it will trigger the signature. This may be a serious attempt at\n\gaining unauthorized access and if the source of the attempt is not within\n\your network they should be shunned." |
|
IDS-4-RPC_PORTREQ_YPSERV |
4-Warning |
Sig:6150:RPC ypserv Portmap Request - from [inet] to [inet] |
Triggers when a request is made to the portmapper for the YP\n\ server daemon ypserv port. |
ids |
"If this procedure is allowed on your network those users\n\that employ it will trigger the signature. This may be a serious attempt at\n\gaining unauthorized access and if the source of the attempt is not within\n\your network they should be shunned." |
|
IDS-4-RPC_PORTREQ_YPUPDATED |
4-Warning |
Sig:6153:RPC ypupdated Portmap Request - from [inet] to [inet] |
Triggers when a request is made to the portmapper for the YP\n\ update daemon ypupdated port. |
ids |
"If this procedure is allowed on your network those users\n\that employ it will trigger the signature. This may be a serious attempt at\n\gaining unauthorized access and if the source of the attempt is not within\n\your network they should be shunned." |
|
IDS-4-RPC_PORTREQ_YPXFRD |
4-Warning |
Sig:6154:RPC ypxfrd Portmap Request - from [inet] to [inet] |
Triggers when a request is made to the portmapper for the\n\ YP transfer daemon ypxfrd port. |
ids |
"If this procedure is allowed on your network those users\n\that employ it will trigger the signature. This may be a serious attempt at\n\gaining unauthorized access and if the source of the attempt is not within\n\your network they should be shunned." |
|
IDS-4-RPC_REXD_REQUEST |
4-Warning |
Sig:6180:RPC rexd Attempt - from [inet] to [inet] |
Triggers when a call to the rexd program is made. The remote execution \n\daemon is the server responsible for remote program execution. This\n\may be indicative of an attempt to gain unauthorized access to system \n\resources. |
ids |
"If this service is being used legitimately this alarm will\n\fire. For security purposes this service really should not be used." |
|
IDS-4-RPC_SET_REQUEST |
4-Warning |
Sig:6100:RPC Port Registration - from [inet] to [inet] |
Triggers when attempts are made to register new RPC services\n\ on a target host. |
ids |
"No benign triggers exist for this signature. Prudent\n\security practices suggest that the source of this attempt should be\n\shunned." |
|
IDS-4-RPC_STATD_OVFLW |
4-Warning |
Sig:6190:statd Buffer Overflow - from [inet] to [inet] |
Triggers when a large statd request is sent. |
ids |
"You should not see this in legitimate traffic." |
|
IDS-4-RPC_UNSET_REQUEST |
4-Warning |
Sig:6101:RPC Port Unregistration - from [inet] to [inet] |
Triggers when attempts are made to unregister new RPC services\n\ on a target host. |
ids |
"No benign triggers exist for this signature. Prudent\n\security practices suggest that the source of this attempt should be\n\shunned." |
|
IDS-4-STR_MATCH_SIG |
4-Warning |
Sig:8000:FTP Retrieve Password File - from [inet] to [inet] |
Triggers on string ''passwd'' issued during an FTP session. |
ids |
"System administrators might use this service to update\n\system files. It is a high security risk if this is normal practice and\n\should be avoided. No other benign triggers exist for this signature. If\n\after investigation the alarm was not generated by a system administrator\n\prudent security practices would suggest that the source be shunned." |
|
IDS-4-TCP_FIN_ONLY_SIG |
4-Warning |
Sig:3042:TCP - FIN bit with no ACK bit in flags - from [inet] to [inet] |
Triggers when a TCP packet is received with the \n\ FIN bit set but with no ACK bit set in the flags field. |
ids |
"There is no legitimate use for malformed TCP datagrams. This is \n\unusual traffic and warrants investigation. Hacker tools will generate\n\TCP packets with the FIN bit set but with no ACK bit set in the flags \n\field in an attempt to elude intrusion dection. When non-specific network \n\traffic of this type is encountered the most prudent action from a \n\security perspective is to shun or disallow it. If the source of this \n\traffic is legitimate the user will then identify him or herself." |
|
IDS-4-TCP_FTP_CWDROOT_SIG |
4-Warning |
Sig:3152:FTP CWD |
root - from [inet] to [inet] |
Triggers when someone tries to execute the CWD |
root command. |
|
IDS-4-TCP_FTP_PORT_BADADDR_SIG |
4-Warning |
Sig:3153:FTP Improper Address Specified - from [inet] to [inet] |
Triggers if a port command is issued with an address that is not the same \n\as the requesting host. |
ids |
"Triggers if a port command is issued with an address that is\n\not the same as the requesting host." |
|
IDS-4-TCP_FTP_PORT_BADPORT_SIG |
4-Warning |
Sig:3154:FTP Improper Port Specified - from [inet] to [inet] |
Triggers if a port command is issued with a data port specified that is \n\<1024 or >65535. |
ids |
"Triggers if a port command is issued with a data port specified\n\that is <1024 or >65535." |
|
IDS-4-TCP_FTP_SITE_SIG |
4-Warning |
Sig:3150:FTP Remote Command Execution - from [inet] to [inet] |
Triggers when someone tries to execute the FTP SITE command. |
ids |
"The FTP Site command allows a user to execute a limited\n\number of commands via the FTP server on the host machine. No authentication\n\is required to execute the command. The commands that may be executed vary\n\from system to system and on many systems the SITE command is not\n\implemented. Recommend that the SITE command be disabled on FTP servers if\n\possible. If this signature is triggered from a source outside of your\n\network prudent security practices would suggest that the source be shunned." |
|
IDS-4-TCP_FTP_SYST_SIG |
4-Warning |
Sig:3151:FTP SYST Command Attempt - from [inet] to [inet] |
Triggers when someone tries to execute the FTP SYST command. |
ids |
"The FTP SYST command returns the type of operating system\n\that the FTP server is running. Authentication is not required to execute\n\this command. SYST provides information that may be used to refine attack\n\methods. FTP from Linux causes SYST signature to fire. Some proxies such as\n\the TIS Toolkit issue the SYST command as a matter of course. Running an\n\FTP version with SYST disabled." |
|
IDS-4-TCP_MAJORDOMO_EXEC_BUG |
4-Warning |
Sig:3107:Majordomo Execute Attack - from [inet] to [inet] |
A bug in the Majordomo program will allow remote users to\n\ execute arbitrary commands at the privilege level of the\n\ server. |
ids |
"Prudent security practices would suggest that the source of this \n\attempt be shunned." |
|
IDS-4-TCP_NO_FLAGS_SIG |
4-Warning |
Sig:3040:TCP - No bits set in flags - from [inet] to [inet] |
Triggers when a TCP packet is received with no bits set\n\ in the flags field. |
ids |
"There is no legitimate use for malformed TCP datagrams. This is \n\unusual traffic and warrants investigation. Hacker tools will generate\n\TCP packets with no bits set in the flags field in an attempt to elude\n\intrusion dection. When non-specific network traffic of this\n\type is encountered the most prudent action from a security perspective\n\is to shun or disallow it. If the source of this traffic is legitimate\n\the user will then identify him or herself." |
|
IDS-4-TCP_SENDMAIL_BAD_FROM_SIG |
4-Warning |
Sig:3102:Sendmail Invalid Sender - from [inet] to [inet] |
- |
ids |
"For security reasons users should not be allowed to execute\n\programs via e-mail servers. This is a very serious indication that your\n\network may be under attack and the source should be shunned immediately." |
|
IDS-4-TCP_SENDMAIL_BAD_TO_SIG |
4-Warning |
Sig:3101:Sendmail Invalid Recipient - from [inet] to [inet] |
- |
ids |
"For security reasons users should not be allowed to execute\n\programs via e-mail servers. This is a very serious indication that your\n\network may be under attack and the source should be shunned immediately." |
|
IDS-4-TCP_SENDMAIL_BOUNCE_SIG |
4-Warning |
Sig:3100:Smail Attack - from [inet] to [inet] |
Triggers on the very common ''smail'' attack against e-mail\n\ servers. This attack attempts to cause e-mail servers to\n\ execute programs on the attacker's behalf. |
ids |
"For security reasons users should not be allowed to execute\n\programs via e-mail servers. This is a very serious indication that your\n\network may be under attack and the source should be shunned immediately. " |
|
IDS-4-TCP_SENDMAIL_DECODE |
4-Warning |
Sig:3105:Sendmail Decode Alias - from [inet] to [inet] |
Triggers on any mail message with '': decode@'' in the header.\n\ The decode alias is used to uudecode files and is primarily\n\ implemented as a convenience for system administration. |
ids |
"The decode alias is used to uudecode files and is primarily\n\implemented as a convenience for system administration. For security\n\purposes this should not be allowed and the service should be disabled. If\n\allowed users that mail to the alias will trigger this signature. Recommend\n\shunning of hosts that attempt to mail to this alias especially if they are\n\outside of your network." |
|
IDS-4-TCP_SENDMAIL_INVALID_COMMAND |
4-Warning |
Invalid SMTP command - from [inet] to [inet] |
Triggers on an invalid SMTP command in the \n\ SMTP connection. This message indicates that a suspicious violation \n\ was detetected that may be an attack to the mail server system. |
ids |
"This is unusual traffic and may warrant investigation." |
|
IDS-4-TCP_SENDMAIL_OLD_SIG |
4-Warning |
Sig:3104:Archaic Sendmail Attacks - from [inet] to [inet] |
Triggers when ''wiz'' or ''debug'' commands are sent to the SMTP port. |
ids |
"There is no reason for this type of traffic to be seen on\n\modern networks. There is little chance that there will be any adverse\n\effects from someone attempting these ''old'' hacks. Prudent security\n\practices would suggest that the source of this attempt be shunned." |
|
IDS-4-TCP_SENDMAIL_SPAM_SIG |
4-Warning |
Sig:3106:Excessive Rcpt to: SPAM - from [inet] to [inet] |
Parse for RCPT TO: in header. Alarm on threshold. |
ids |
"Some mailing list software may trigger this signature." |
|
IDS-4-TCP_SENDMAIL_VRFY_SIG |
4-Warning |
Sig:3103:Sendmail Reconnaissance - from [inet] to [inet] |
Triggers when ''expn'' or ''vrfy'' commands are issued to\n\ the SMTP port. |
ids |
"These commands are commonly used to verify that a user mail\n\account exists on the server or to expand an alias to determine who the\n\actual recipients of a message may be. Users that use the EXPN and VRFY\n\functions for legitimate purposes will trigger this signature. The\n\information that can be obtained is useful but not dangerous on its own.\n\Monitoring of future traffic for patterns of misuse is recommended." |
|
IDS-4-TCP_SYN_ATTACK_SIG |
4-Warning |
Sig:3050:Half-Open Syn Flood - from [inet] to [inet] |
Triggers when the number of half-open TCP connections\n\ exceeds the high-water mark or the one minute high rate mark |
ids |
"There are no known sources that would legitimately generate\n\this traffic pattern. This may be indicative of some type of network problem\n\and should be investigated. To avoid depletion of your network resources it\n\is recommended that the source be shunned during the course of the\n\investigation. If no network problems are discovered prudent security\n\practices would suggest that the source be shunned permanently." |
|
IDS-4-TCP_SYN_FIN_SIG |
4-Warning |
Sig:3041:TCP - SYN and FIN bits set - from [inet] to [inet] |
Triggers when a TCP packet is received with both the SYN\n\ and FIN bits set in the flags field. |
ids |
"There is no legitimate use for malformed TCP datagrams. This is \n\unusual traffic and warrants investigation. Hacker tools will generate\n\TCP packets with the SYN and FIN bits set in the flags field in an \n\attempt to elude\n\intrusion dection. When non-specific network traffic of this\n\type is encountered the most prudent action from a security perspective\n\is to shun or disallow it. If the source of this traffic is legitimate\n\the user will then identify him or herself." |
|
IDS-4-UDP_BOMB_SIG |
4-Warning |
Sig:4050:UDP Bomb - from [inet] to [inet] |
Triggers when the UDP length specified is less than the IP\n\ length specified. This malformed packet type is associated\n\ with a denial of service attempt. |
ids |
"There is no legitimate use for malformed datagrams. This\n\may be indicative of systems that are experiencing problems with their\n\kernel or NIC cards. This is unusual traffic and warrants investigation.\n\When non-specific network traffic of this type is encountered the most\n\prudent action from a security perspective is to shun or disallow it. If the\n\source of this traffic is legitimate the user will then identify him or\n\herself." |
|
IDS-4-UDP_TFTP_PASSWD_SIG |
4-Warning |
Sig:4100:Tftp Passwd File - from [inet] to [inet] |
Triggered when someone tries to tftp a password file. |
ids |
"System administrators might use this service to update\n\system files. It is a high security risk if this is normal practice and\n\should be avoided. No other benign triggers exist for this signature. If\n\after investigation the alarm was not generated by a system administrator\n\prudent security practices would suggest that the source be shunned." |
|
IDTATM25-1-DISCOVER |
1-Alert |
Only found [dec] interfaces on bay [dec] shutting down bay |
The ATM25 network module hardware may be bad |
pm-atm25 |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
IDTATM25-1-INITFAIL |
1-Alert |
IDTATM25[dec]/[dec] Init failed at [chars]. |
The ATM25 network module hardware may be bad |
pm-atm25 |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
IDTATM25-3-FAILSETUPVC |
3-Error |
Interface [chars] Failed to setup vc [dec] Cause: [chars] |
The ATM25 network module hardware may be bad |
pm-atm25 |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
IDTATM25-3-FAILTEARDOWNVC |
3-Error |
Interface [chars] Failed to down vc [dec] Cause: [chars] |
The ATM25 network module hardware may be bad |
pm-atm25 |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
IDTATM25-3-NOTIDTATM25 |
3-Error |
Device reported [hex] |
The ATM25 network module hardware may be bad |
pm-atm25 |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
IDTATM25-3-RXLOSTSYNC |
3-Error |
IDB= [chars] RX lost sync Interface reset |
RX hang |
c1400 |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
IDTATM25-3-TXHANG |
3-Error |
IDB= [chars] TX hang Interface reset |
TX hang |
c1400 |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
IDTATM25-3-UNSUPPORTED |
3-Error |
Interface [chars] [chars] not supported |
The ATM25 network module hardware may be bad |
pm-atm25 |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
IDTATM25-6-TXLIMIT |
6-Information |
ATM transmit bandwidth is limited to smallest shaped value. |
Any PVC configured with traffic shaping will limit the entire ATM interface to not exceed the bandwidth of any traffic shaped pvc. |
- |
"" |
|
IDWL-3-LOOP_BACK_DETECTED |
3-Error |
Loop-back detected on [chars]. |
Loop-back may be caused by accidentally plugging a balun cable into the port or there may be a misconfiguration in the network. |
firmware |
"Correct the problem causing the loopback " "condition. Then bring the port up by entering the shutdown " "then no shutdown interface configuration commands." |
|
IE3X00_LICENSE-4-FEAT_EVAL_EXPIRED |
4-Warning |
Evaluation Period Expired for [chars] |
Eval Period has expired. License agent moving to eval-expired state |
- |
"Restore communication with cisco and register " " the device" |
|
IE3X00_LICENSE-4-FEAT_OOC |
4-Warning |
Feature [chars] Out Of Compliance Existing feature configurations would be disabled on net reboot |
Smart License Agent enforcement mode changed to out of compliance |
- |
"Report to TAC and add sufficient licenses" |
|
IE3X00_LICENSE-5-FEAT_EVAL_MODE |
5-Notice |
Feature [chars] is operating in Eval Mode |
Smart License Agent enforcement mode changed to EVAL MODE |
- |
"None" |
|
IE3X00_LICENSE-5-FEAT_IN_COMPLIANCE |
5-Notice |
Feature [chars] is Authorized |
Smart License Agent enforcement mode changed to Incompliance |
- |
"None" |
|
IEDGE-3-CH_INTERNAL_ERROR |
3-Error |
Internal error in command processing - session handle=[hex] |
There has been an internal error relating to CoA command processing. |
policy |
"Copy the error message exactly as it appears and " "report it to your technical support " "representative." |
|
IEDGE-3-CH_REGISTER_ERROR |
3-Error |
CoA registration error in command processing - type '[chars]' |
There has been an internal error relating to CoA command processing. |
policy |
"Copy the error message exactly as it appears and " "report it to your technical support " "representative." |
|
IEDGE-4-CLOCK_CHANGE_TIMER_INV |
4-Warning |
A Local clock change has caused a running timer to be invalid |
A change in local clock has made a currently running timer to be invalid |
sss |
"Check the clock configuration" |
|
IEDGE-4-PBHK_DEPLETED_INDICES |
4-Warning |
No more portbundles can be allocated |
The source interfaces configured for Portbundle Hostkey feature are not sufficient and the number of portbundles available are all used up. Add more source interfaces in the configuration. |
sss |
"Check configuration on the ISG" |
|
IEDGE-4-TC_UNDEFINED_ACL |
4-Warning |
Traffic class ACL [chars] is not defined creating permit all ACL |
The ACL specified for classification of traffic is not configured on the ISG. Creating a permit all ACL. ACL should be configured on the ISG. |
sss |
"Configure the ACL on the ISG" |
|
IF_FAIL-2-MPLS_TE_EXT_FWDG |
2-Critical |
ERRMSG_NOFLAGS |
- |
- |
- |
|
IF_L3_SVC_ASSOC-4-L2VPN |
4-Warning |
ERRMSG_NOFLAGS |
- |
- |
- |
|
IF_MULTIPLE_SVC_ASSOC-4-L2VPN |
4-Warning |
ERRMSG_NOFLAGS |
- |
- |
- |
|
IF_PW_LIMIT_EXCEEDED-5-L2VPN |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
IF_SET_CFG_RESP_FAILED-3-L2VPN |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
IF-2-IDB_TABLE_INIT |
2-Critical |
Malloc failed while initializing idb table |
- |
- |
- |
|
IF-3-BAD_MTU |
3-Error |
Internal error. MTU on [chars] too large or negative. Truncating from %ld to %lu.\n |
An internal software error occurred. The system attempted\n\ to set the MTU on an interface to an invalid value. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
IF-3-BADHWUNLOCK |
3-Error |
[chars] attempted to unlock [chars] [dec]. Locked by [chars] [dec]. |
Attempt to release semaphore held by another process. |
- |
"LOG_STD_ACTION" |
|
IF-3-BADLOCK |
3-Error |
Invalid lock use for [chars]: [chars][chars] |
Application layer code attempted to access an unlocked interface. |
- |
"LOG_STD_ACTION" |
|
IF-3-BADMACADDRTYPE |
3-Error |
illegal mac address type [dec] |
This is an interal error that was recovered gracefully. |
idb |
"LOG_STD_ACTION" |
|
IF-3-IDB_LIST_BAD_REF_COUNT |
3-Error |
A bad reference count was encountered in an idb list element. |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
IF-3-SEMAHOG |
3-Error |
[chars] could not get [chars] semaphore. Held by [chars]. |
Unable to obtain interface semaphore. |
- |
"LOG_STD_ACTION" |
|
IF-4-BACKWARD_COUNTERS |
4-Warning |
Corrected for backward [chars] counters %llu -> %llu on [chars] |
- |
- |
- |
|
IF-4-NOBGPROCESS |
4-Warning |
Network background process not running. [chars] |
A process which manages network interface background processing is not yet running but another system process has tried to send the process a message. |
idb |
"An interface on the router may have missed a request to bring " "itself up. If that happens it may be necessary to reset the " "interface using a <CmdBold>shutdown<NoCmdBold> operation and " "then a <CmdBold>no shutdown<NoCmdBold>. " |
|
IFDAMP-5-UPDOWN |
5-Notice |
interface [chars] update [chars] state to [chars] interface is [chars]suppressed |
dampening interface changed state. |
ip |
LOG_STD_NO_ACTION |
|
IFDAMP-5-ZERODELAY |
5-Notice |
dampening reuse timer is updated with 0 delay time |
Inconsistency of dampening reuse timer wheel |
ip |
LOG_STD_NO_ACTION |
|
IFM_SHIM-3-AVL_TREE |
3-Error |
AVL tree [chars] action failed for [chars] iif-id 0x%016llx |
AVL tree operation failure for specific interface object in IFM-SHIM software module. This usually implies a duplicate node already existing or the tree data structure corruption. |
accsw-platform |
LOG_STD_SH_TECH_ACTION |
|
IFM_SHIM-3-INIT_FAILURE |
3-Error |
[chars] |
IFM-SHIM has experienced initialization failure. |
accsw-platform |
LOG_STD_SH_TECH_ACTION |
|
IFM_SHIM-3-INTIF_CREATE_FAILURE |
3-Error |
[chars] |
Internal interface not created |
accsw-platform |
LOG_STD_SH_TECH_ACTION |
|
IFM_SHIM-3-MALLOC_FAILURE |
3-Error |
Memory allocation failure when [chars] |
Failed to allocated memory for a structure or event. |
accsw-platform |
LOG_STD_SH_TECH_ACTION |
|
IFM_SHIM-3-SEND_FAILURE |
3-Error |
[chars] |
IFM-SHIM is experiencing message send failure. |
accsw-platform |
LOG_STD_SH_TECH_ACTION |
|
IFM_SHIM-3-SPI_FAILURE |
3-Error |
[chars] |
IFM-SHIM is experiencing SPI failure. |
accsw-platform |
LOG_STD_SH_TECH_ACTION |
|
IFMAP-3-CAUSE_CFG |
3-Error |
hash table not initialized |
PAL interface handle to uidb hash table not initialized |
cpp-ucode |
LOG_STD_ACTION |
|
IFMGR-3-BADIFINDEXTABLE |
3-Error |
The file nvram:ifIndex-table is corrupt. |
The file is not in the expected format. |
none |
"If possible please delete the file." |
|
IFMGR-3-IFDB |
3-Error |
IF manager interface database [chars] failure- [dec] |
- |
if_mgr |
"TBD" |
|
IFMGR-3-IFINDEX_PERSIST_ENTRY_CORRUPT |
3-Error |
[chars] seems to be corrupted. Trying to read [dec] size |
The ifIndex-table seems to be corrupted. |
if_mgr |
"Delete the ifindex-table." |
|
IFMGR-3-IFTDB |
3-Error |
IF manager interface table database [chars] failure- [dec] |
- |
if_mgr |
"TBD" |
|
IFMGR-3-INVALID_PERSISTENT_DATA |
3-Error |
Invalid persistent data |
Trying to write invalid persistent data |
snmp-if |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
IFMGR-3-NOIMACP |
3-Error |
IF manager control process failed to start |
- |
if_mgr |
"TBD" |
|
IFMGR-3-NOTYPEVECTOR |
3-Error |
Interface manager failed to allocate IF type vector. size [dec] |
The interface type vector was not able to be allocated with the number of elements required--initially or resize. |
if_mgr |
"TBD" |
|
IFMGR-3-NOVECTOR |
3-Error |
Interface manager failed to allocate IF vector. size [dec] |
The interface vector was not able to be allocated with the number of elements required--initially or resize see size in the error message. |
if_mgr |
"TBD" |
|
IFMGR-3-VECTOREXD |
3-Error |
IF manager attempted to use interface [dec] outside vector range. |
This message indicates that an interface with too large of an ifIndex value was attempted to be added to the IF-MGR DB. |
if_mgr |
"Additional IF-MGR warning and/or error messages should accompany" "indication of this error. These additional messages should provide more" "details on the effected interface." |
|
IFMGR-3-VECTORPOSUSED |
3-Error |
IF manager attempted to add interface [dec] which was already added. |
This message comes from the IF-MGR DB when it is trying to add an ifIndex value for this interface which already exists in the ifIndex DB. |
if_mgr |
"TBD" |
|
IFMGR-4-NOIFINDEX |
4-Warning |
All SNMP if indices are exhausted |
All SNMP MIB indices have been exhausted. Interfaces will\n\ not be able to obtain an interface index that they can \n\ use to register with the interface MIB. |
if_mgr |
"Attempt a system reload. If the problem persists after the\n\ system reload copy the message exactly as it appears on\n\ the console or in the system log contact your Cisco\n\ technical support representative and provide the\n\ representative with the gathered information." |
|
IFMGR-4-NOSYNC |
4-Warning |
ifIndex not being synced between active and standby |
When the standby comes up then the tuple of ifIndex and ifDescr\n\ is synced so that when interfaces comes up they get the same ifIndex.\n\ This error happens when the interface doesn't get the ifIndex for\n\ the given ifDescr |
if_mgr |
"Inform the technical support to raise the ddts" |
|
IFMGR-4-STACK_RELATIONSHIP_ADD_ERROR |
4-Warning |
[chars]: Request for creating invalid stack relationship [dec] [dec] |
Interfaces have same ifIndex in IF-MGR assigned list. The 2nd interface registered with IF-MGR will be assigned with new index |
if_mgr |
"1. No Action if ifIndex persist is not required." "2. Reload the standby RP if ERR msg only seen in standby RP" "3. Reload the router with the proper ifindex-table and image" |
|
IFMGR-4-VECTORIFSUSPECT |
4-Warning |
IF manager added interface [dec] which is unexpectedly large. |
The ifIndex allocation scheme gives out sequential ifIndex values. This message comes from the IF-MGR DB when it is trying to add an ifIndex value much larger than the former greatest ifIndex value in the DB. |
if_mgr |
"TBD" |
|
IFMGR-5-RESTART |
5-Notice |
[chars] |
The IF MGR process has restarted |
if_mgr |
"This is an informational message. The system should recover on its" " own." |
|
IFMGR-7-NO_IFINDEX_FILE |
7-Debug |
Unable to open [chars] [chars] |
This is a informational message. This means system found no saved ifIndex information and ifIndex is not persisted across reboots. The ifIndices will be reassigned. |
if_mgr |
"1. No Action if 'snmp-server ifIndex persist' is not configured. " "2. If 'snmp-server ifindex persist' is configured then copy the error" " message exactly as it appears and report it to your technical" " support representative." |
|
IFS-3-FS_CREATE_FAIL |
3-Error |
Failed to create [chars] file system [chars] |
An internal software error occurred. |
Determine the component from the traceback displayed in the\n\ error message. |
"Call your technical support representative for assistance." |
|
IFS-3-FS_CREATE_FAIL2 |
3-Error |
Failed to create [chars] simple file system [chars] |
An internal software error occurred. |
Determine the component from the traceback displayed in the\n\ error message. |
"Call your technical support representative for assistance." |
|
IFS-3-FS_MISSING_FUNCTIONS |
3-Error |
'[chars]' file system missing required functions not created |
Some file systems require a certain set of function to be present in\n\ order to be usable. This file sustem does not support all the\n\ mandatory functionality. |
Determine the component from the traceback displayed in the\n\ error message. |
"Call your technical support representative for assistance." |
|
IFS-3-FS_STRUCT_ERROR |
3-Error |
Data does not match expected internal representation |
A mismatch exists between the representation of data extracted from the filesystem and the expectation of its formatting. This may occur when running in a dual-RP environment with different IOS versions running on the two RPs. |
ifs |
"Ensure both RPs are running the IOS same version if running in " "a dual-RP environment. If not call your technical support " "representative for assistance." |
|
IFS-3-FSDUP |
3-Error |
Failed to add [chars] filesystem prefix exists |
A file system cound not be added because another file system exists\n\ with the same name. |
Determine the component from the traceback displayed in the\n\ error message. |
"Contact your technical support representative." |
|
IFS-3-FSMAX |
3-Error |
Failed to add [chars] maximum filesystems [dec] |
The router has reached the maximum number of file systems that\n\ can be supported at one time. |
ifs |
"Contact your technical support representative." |
|
IFS-4-FILEMAX |
4-Warning |
Failed to open [chars] maximum open files [dec] |
The router has reached the maximum number of files that may\n\ be open at one time. |
ifs |
"Close some files and try again. If this messages recurs contact your\n\ technical support representative." |
|
IGMP_QUERIER-4-NO_IP_ADDR_CFG |
4-Warning |
The IGMP querier cannot send out General Query messages in VLAN [dec] because there is no IP address configured on the system. |
An IP address should be specified for the IGMP querier either at the global or per VLAN level. |
igmp |
"Configure a source IP address for the IGMP querier. " |
|
IGMP_QUERIER-4-PIM_ENABLED |
4-Warning |
The IGMP querier is operationally disabled in VLAN [dec] because PIM has been enabled on the SVI. |
PIM has been detected on the SVI. The IGMP querier function should not be operationally enabled when PIM is enabled on the SVI. |
igmp |
"Ensure that PIM is disabled on the SVI. " |
|
IGMP_QUERIER-4-QUERIER_MROUTER_DETECTED |
4-Warning |
An external IGMP querier or a multicast router has been detected in VLAN [dec] on port [chars]. |
An external querier or multicast router has been detected in the VLAN. The IGMP querier function should not be enabled when there is external querier or multicast router present in the VLAN. |
igmp |
"Either manually disable the IGMP querier on this system or disable " "querier or PIM/DVMRP on the multicast routers identified. The IGMP " |
|
IGMP_QUERIER-4-SAME_SRC_IP_ADDR |
4-Warning |
An IGMP General Query packet with the same source IP address [inet] |
The IGMP querier has received an IGMP General Query message with a source IP address identical to that configured for the IGMP querier itself. This is considered a network configuration error. |
igmp |
"Check IGMP querier source IP address configuration on the router " "or switch connected via the port identified." "Ensure unique source IP addresses are configured on each system. " |
|
IGMP_QUERIER-4-SNOOPING_DISABLED |
4-Warning |
The IGMP querier is operationally disabled in VLAN [dec] because IGMP snooping has been disabled in this VLAN. |
IGMP snooping has been detected as being disabled on this VLAN. The IGMP querier function should not be operationally enabled when IGMP snooping is disabled. |
igmp |
"Ensure that IGMP snooping is enabled globally and on the VLAN " "reported. " |
|
IGMP_QUERIER-4-VLAN_NOT_FWD |
4-Warning |
The IGMP querier is operationally disabled in VLAN [dec] because VLAN is not in forwarding state. |
The IGMP querier function is not be operationally enabled when VLAN is not forwarding. |
igmp |
"Check spanning tree state for this VLAN." |
|
IGMP_QUERIER-4-ZERO_SRC_IP_ADDR |
4-Warning |
An IGMP General Query packet with source IP address that contained all zeroes is received in VLAN [dec] on port [chars]. |
The IGMP querier has received an IGMP General Query message with a source IP address that contained all zeroes. Some IGMP clients cannot process General Query with source IP address that contained all zeroes. |
igmp |
"Check the source IP address of the IGMP querier that is on the router " "or switch connected to the port specified in the message. " |
|
IGMP_QUERIER-6-NO_QUERIER_MROUTER_DETECTED |
6-Information |
The IGMP querier is now operationally enabled in VLAN [dec] because no external querier or multicast router has been detected. |
No external querier or multicast router has been detected. As a result the IGMP querier function has now been enabled. |
igmp |
"No action is required." |
|
IGMP_QUERIER-6-PIM_DISABLED |
6-Information |
The IGMP querier is now operationally enabled in VLAN [dec] because PIM is no longer enabled on the SVI. |
PIM has been disabled on the SVI and as a result the IGMP querier function has now been enabled. |
igmp |
"No action is required." |
|
IGMP_QUERIER-6-SNOOPING_ENABLED |
6-Information |
The IGMP querier is now operationally enabled in VLAN [dec] because IGMP snooping is no longer disabled. |
IGMP snooping has now been enabled and as a result the IGMP querier function has now been enabled. |
igmp |
"No action is required." |
|
IGMP_QUERIER-6-VLAN_FWD |
6-Information |
The IGMP querier is now operationally enabled in VLAN [dec] because the VLAN has entered forwarding state. |
The VLAN has been placed in the forwarding state and as a result the IGMP querier function has now been enabled. |
igmp |
"No action is required." |
|
IGMP_SNOOP_ISSU-2-GET_BUFFER |
2-Critical |
IGMP Snooping ISSU client failed to get buffer for message. Error: [dec] [chars] |
The IGMP Snooping 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. |
igmp-snooping |
"show logging and show checkpoint client" |
|
IGMP_SNOOP_ISSU-2-GET_BUFFER |
2-Critical |
IGMP Snooping ISSU client failed to get buffer for message. Error: [dec] [chars] |
The allocation of explicit-tracking entries is bounded to avoid\n\ the IGMP/MLD snooping hogs the system resources |
igmp/mld snooping |
"Disable and re-enable L2 multicast snooping on the VLAN." |
|
IGMP_SNOOP_ISSU-2-INIT |
2-Critical |
IGMP Snooping ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The IGMP Snooping 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. |
igmp-snooping |
LOG_STD_ACTION |
|
IGMP_SNOOP_ISSU-2-INIT |
2-Critical |
IGMP Snooping ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The IGMP Snooping 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. |
igmp-snooping |
LOG_STD_ACTION |
|
IGMP_SNOOP_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
IGMP Snooping ISSU client failed to send negotiation message. Error: [dec] [chars] |
The IGMP Snooping 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. |
igmp-snooping |
"show logging and show checkpoint client" |
|
IGMP_SNOOP_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
IGMP Snooping ISSU client failed to send negotiation message. Error: [dec] [chars] |
The IGMP Snooping 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. |
igmp-snooping |
"show logging and show checkpoint client" |
|
IGMP_SNOOP_ISSU-2-SESSION_NEGO |
2-Critical |
IGMP Snooping ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The IGMP Snooping 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. |
igmp-snooping |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
IGMP_SNOOP_ISSU-2-SESSION_NEGO |
2-Critical |
IGMP Snooping ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The IGMP Snooping 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. |
igmp-snooping |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
IGMP_SNOOP_ISSU-2-SESSION_REGISTRY |
2-Critical |
IGMP Snooping ISSU client failed to register session information. Error: [dec] [chars] |
The IGMP Snooping ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
igmp-snooping |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
IGMP_SNOOP_ISSU-2-SESSION_REGISTRY |
2-Critical |
IGMP Snooping ISSU client failed to register session information. Error: [dec] [chars] |
The IGMP Snooping ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
igmp-snooping |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
IGMP_SNOOP_ISSU-3-INVALID_SESSION |
3-Error |
IGMP Snooping ISSU client does not have a valid registered session. |
The IGMP Snooping ISSU client does not have a valid registered session. |
igmp-snooping |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
IGMP_SNOOP_ISSU-3-INVALID_SESSION |
3-Error |
IGMP Snooping ISSU client does not have a valid registered session. |
The IGMP Snooping ISSU client does not have a valid registered session. |
igmp-snooping |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
IGMP_SNOOP_ISSU-3-MSG_NOT_OK |
3-Error |
IGMP Snooping ISSU client 'Message Type [dec]' is not compatible |
The IGMP Snooping ISSU client received an incompatible message from the peer device. The message cannot be processed. |
igmp-snooping |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
IGMP_SNOOP_ISSU-3-MSG_NOT_OK |
3-Error |
IGMP Snooping ISSU client 'Message Type [dec]' is not compatible |
The IGMP Snooping ISSU client received an incompatible message from the peer device. The message cannot be processed. |
igmp-snooping |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
IGMP_SNOOP_ISSU-3-MSG_SIZE |
3-Error |
IGMP Snooping ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The IGMP Snooping ISSU client failed to calculate the MTU for the specified message. The IGMP Snooping ISSU client is not able to send the message to the standby device. |
igmp-snooping |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
IGMP_SNOOP_ISSU-3-MSG_SIZE |
3-Error |
IGMP Snooping ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The IGMP Snooping ISSU client failed to calculate the MTU for the specified message. The IGMP Snooping ISSU client is not able to send the message to the standby device. |
igmp-snooping |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
IGMP_SNOOP_ISSU-3-SESSION_UNREGISTRY |
3-Error |
IGMP Snooping ISSU client failed to unregister session information. Error: [dec] [chars] |
The IGMP Snooping ISSU client failed to unregister session information. |
igmp-snooping |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
IGMP_SNOOP_ISSU-3-SESSION_UNREGISTRY |
3-Error |
IGMP Snooping ISSU client failed to unregister session information. Error: [dec] [chars] |
The IGMP Snooping ISSU client failed to unregister session information. |
igmp-snooping |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
IGMP_SNOOP_ISSU-3-TRANSFORM_FAIL |
3-Error |
IGMP Snooping ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The IGMP Snooping 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 IGMP Snooping state between the active device and the standby device is not identical. |
igmp-snooping |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
IGMP_SNOOP_ISSU-3-TRANSFORM_FAIL |
3-Error |
IGMP Snooping ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The IGMP Snooping 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 IGMP Snooping state between the active device and the standby device is not identical. |
igmp-snooping |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
IGMP -3-DNS_ERROR |
3-Error |
DNS lookup time out. DNS lookup for ssm mapping will be disabled for 60 sec. |
DNS source lookup time out. DNS server did not respond \n\ to the DNS query this may be due to DNS server is down. \n\ DNS lookup will be stopped for next 60 sec. |
- |
"Disable DNS lookup for ssm mapping till the DNS " "server comes up." LOG_STD_ACTION |
|
IGMP-3-IGMP_CLIENT_ID_ERR |
3-Error |
Invalid Client Id usage [dec]. |
Invalid Client Id usage |
- |
"Check the Client Id" LOG_STD_NO_ACTION |
|
IGMP-3-IGMP_LIST_DEL_STATIC |
3-Error |
Failed to delete static groups for interface [chars]. |
Repeated attempts to walk the list failed. |
mcast-igmp |
LOG_STD_ACTION |
|
IGMP-3-IGMP_LIST_RESET_SOURCE_FLAGS |
3-Error |
Failed to reset source flags for [inet]. |
Repeated attempts to reset the flags failed. |
mcast-igmp |
LOG_STD_ACTION |
|
IGMP-3-NO_DNS_SERVER |
3-Error |
No DNS server is configured. \nDNS-based SSM mapping should be disabled if no DNS server is configured. |
There is no DNS server present. Processing IGMP \n\ packets may be delayed if the DNS-lookup is done continuosly. |
- |
"Disable DNS-based SSM mapping if there is \n\ no DNS-server present in the network." LOG_STD_ACTION |
|
IGMP-3-QUERY_INT_MISMATCH |
3-Error |
Received a non-matching query interval [dec] from querier address [inet] |
Mismatch of IGMP version found between routers. |
- |
"Configure both the interfaces with same IGMP version." LOG_STD_ACTION |
|
IGMP-4-MROUTE_IC_FLAG |
4-Warning |
While adding or deleting multicast state some state may not correctly have local interest flag set or cleared. |
Repeated attempts to adjust local interest flag were running over time and some state may not have been adjusted. |
- |
LOG_STD_SH_TECH_ACTION |
|
IGMP-4-NO_INPUT |
4-Warning |
IGMP packet without input interface received from [inet] for [inet] |
An unexpected IGMP packet without input interface was received. |
ipmulticast |
"Consider taking note of source and destination present in syslog." LOG_STD_ACTION |
|
IGMP-6-IGMP_CHANNEL_LIMIT |
6-Information |
IGMP limit exceeded for channel [inet] [inet] on [chars] by host [inet] |
- |
- |
- |
|
IGMP-6-IGMP_GROUP_LIMIT |
6-Information |
IGMP limit exceeded for group * [inet] on [chars] by host [inet] |
- |
- |
- |
|
IGNITION-4-IGN_FAILED_CMD |
4-Warning |
Ignition Management hardware failed to execute the '[chars]' command. Code: [dec] |
The hardware MCU responsible for the ignition power management is not responding properly to software commands. |
aventus-platform |
LOG_STD_RECUR_ACTION |
|
IGNITION-4-IGN_OVER_VOLTAGE |
4-Warning |
The input voltage is at [dec].[dec] V. The overvoltage threshold of [dec].[dec] V has been tripped recently. Shutdown sequence will begin. |
The input voltage became higher than the overvoltage threshold and the router might shutdown shortly. |
aventus-platform |
"Reduce the input power supply voltage." |
|
IGNITION-4-IGN_REJECT_SETTING |
4-Warning |
Incompatible 'under voltage' setting [dec].[dec] V was not applied. The |
The under voltage threshold value was set to a higher value then actual input voltage and applying this setting would cause the router to shutdown shortly |
aventus-platform |
LOG_STD_RECUR_ACTION |
|
IGNITION-4-IGN_UNDER_VOLTAGE |
4-Warning |
The input voltage below the undervoltage threshold of [dec].[dec] V was detected. The system may shutdown. |
The input voltage became lower than the undervoltage threshold and the router might shutdown shortly. |
aventus-platform |
"Increase the input power supply voltage." |
|
IGNITION-4-IGN_UNDER_VOLTAGE_END |
4-Warning |
The input voltage above the undervoltage threshold of [dec].[dec] V was detected. |
The input voltage became higher than the undervoltage threshold. |
aventus-platform |
LOG_STD_NO_ACTION |
|
IGNITION-5-IGN_DEBUG_SET |
5-Notice |
Ignition Management debugging [chars] is turned [chars] |
The system's debugging facility is turned on or off |
aventus-platform |
LOG_STD_NO_ACTION |
|
IGNITION-5-IGN_ENABLE_CMD |
5-Notice |
The Ignition Power Management is [chars] |
The system administrator has enabled the Ignition Power Management feature. |
aventus-platform |
LOG_STD_NO_ACTION |
|
IGNITION-5-IGN_RELOAD_SYS |
5-Notice |
The Ignition Power Management is preparing for shutdown |
The Ignition Power Management is about to shut the system down. |
aventus-platform |
LOG_STD_NO_ACTION |
|
IGNITION-5-IGN_SENSE_CMD |
5-Notice |
The Ignition Voltage Sense is [chars] |
The system administrator has enabled the Ignition Voltage Sense feature. |
aventus-platform |
LOG_STD_NO_ACTION |
|
IGNITION-5-IGN_TURNED_ON_OFF |
5-Notice |
The ignition is turned [chars] |
The ignition state changed between ON and OFF. |
aventus-platform |
LOG_STD_NO_ACTION |
|
IIOT_ALARM_CONTACT-0-EXTERNAL_ALARM_CONTACT_ASSERT |
0-Emergency |
External alarm/digital IO port [chars] asserted\n |
External alarm/digital IO port alert is detected |
- |
"No action recommended" LOG_STD_ACTION |
|
IIOT_ALARM_CONTACT-0-EXTERNAL_ALARM_CONTACT_CLEAR |
0-Emergency |
External alarm/digital IO port [chars] cleared\n |
External alarm/digital IO port alert is cleared |
SPARROW_COMPONENT |
"No action recommended" LOG_STD_ACTION |
|
IKEV2-1-SEND_COOKIE_CHALLENGE |
1-Alert |
NULL |
- |
ipsec-ikev2 |
- |
|
IKEV2-3-NEG_ABORT |
3-Error |
NULL |
- |
ipsec-ikev2 |
- |
|
IKEV2-5-INCREASE_PEER_WINDOW_SIZE |
5-Notice |
NULL |
- |
ipsec-ikev2 |
- |
|
IKEV2-5-IPSEC_COLLISION |
5-Notice |
NULL |
- |
ipsec-ikev2 |
- |
|
IKEV2-5-OSAL_INITIATE_TUNNEL |
5-Notice |
NULL |
- |
ipsec-ikev2 |
- |
|
IKEV2-5-RECV_CONNECTION_REQUEST |
5-Notice |
NULL |
- |
ipsec-ikev2 |
- |
|
IKEV2-5-SA_DOWN |
5-Notice |
NULL |
- |
ipsec-ikev2 |
- |
|
IKEV2-5-SA_REJECTED_LIMIT_REACHED |
5-Notice |
[chars] |
- |
ipsec-ikev2 |
- |
|
IKEV2-5-SA_REJECTED_RESOURCE_LOW |
5-Notice |
NULL |
- |
ipsec-ikev2 |
- |
|
IKEV2-5-SA_UP |
5-Notice |
NULL |
- |
ipsec-ikev2 |
- |
|
ILACC-1-INITFAIL |
1-Alert |
msgtxt_initfail |
The hardware failed to initialize correctly. |
- |
"Repair or replace the controller." |
|
ILACC-1-MEMERR |
1-Alert |
msgtxt_memoryerror |
An Ethernet interface detected a hardware problem. |
- |
"Repair or replace the controller." |
|
ILACC-3-BADUNIT |
3-Error |
msgtxt_badunit |
An internal software error occurred. |
- |
"If this message recurs contact your technical support representative." |
|
ILACC-3-OWNERR |
3-Error |
msgtxt_ownerror |
An Ethernet interface is malfunctioning or an internal software error\n\ occurred. |
- |
"Repair or replace the controller." |
|
ILACC-3-SPURIDON |
3-Error |
Unit [dec] spurious IDON interrupt csr[dec]=0x%04x |
An Ethernet interface generated a spurious Initialization Done\n\ interrupt. |
- |
"Repair or replace the controller." |
|
ILACC-3-UNDERFLO |
3-Error |
Unit [dec] underflow error |
The Ethernet hardware is requesting data faster than the system can\n\ supply it. This condition might indicate that the system is at the\n\ limit of its performance. |
- |
"A small number of underflows might not be a cause for concern. You can\n\ monitor underflows with the <Bold>show interface<NoBold> command. Reducing the load\n\ on the router or installing a higher-performance router should\n\ alleviate this problem." |
|
ILACC-4-BABBLE |
4-Warning |
Unit [dec] babble error csr0 = 0x[hec] |
An Ethernet interface is malfunctioning. |
- |
"Determine whether the malfunction stems from a software or hardware\n\ error by turning off all fast switching. Error messages showing that the packet is too large for the link\n\ indicate a software error at a high level. Copy the error message exactly as it appears and report it to your\n\ technical support representative. Receiving no error messages indicates a hardware error. \n\ Repair or replace the controller." |
|
ILACC-5-COLL |
5-Notice |
Unit [dec] excessive collisions. TDR=[dec] |
- |
- |
"If the transceiver appears to be properly terminated repair or\n\ replace the Ethernet interface card." |
|
ILACC-5-LATECOLL |
5-Notice |
Unit [dec] late collision error |
An Ethernet transceiver is malfunctioning the Ethernet is overloaded\n\ or the Ethernet cable is too long. |
- |
"Repair or replace the controller." |
|
ILACC-5-LOSTCARR |
5-Notice |
Unit [dec] lost carrier. Transceiver problem? |
An Ethernet transceiver is unplugged or faulty. |
- |
"Repair or replace the controller." |
|
ILLEGAL-3-VFI |
3-Error |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
ILLEGAL-3-XCONNECT |
3-Error |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
ILP_ISSU-3-BUFFER |
3-Error |
Platform ILPower ISSU client failed to get buffer for msg error [dec] |
Platform Inline Power ISSU client failed to get buffer for building\n\ a negotiation message. Hence it can send the negotiation\n\ message to the standby unit. When there is a problem in\n\ the negotiaiton the standby unit can not be brought up. |
platform-ha |
"show logging and show checkpoint client" |
|
ILP_ISSU-3-CAP_INVALID_SIZE |
3-Error |
Platform Inline Power ISSU client capability list is empty. |
The Platform Inline Power ISSU client capability exchange list size\n\ is invalid. |
platform-ha |
"show issu capability entries <Client_ID>" |
|
ILP_ISSU-3-CAP_NOT_COMPATIBLE |
3-Error |
Platform Inline Power ISSU client capability exchange result incompatible. |
The Platform ILPower ISSU client capability exchange has negotiated\n\ as incompatible with the peer. |
platform-ha |
"show issu negotiated capability <Session_ID>" |
|
ILP_ISSU-3-CAPABILITY |
3-Error |
Platform Inline Power ISSU client [chars] |
Platform Inline Power ISSU client observed an error during capability\n\ negotiation. When this error happens there is a mismatch\n\ between the client capability between the active and\n\ standby unit. |
platform-ha |
"show issu capability entries <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated capability <session_id>" |
|
ILP_ISSU-3-INIT |
3-Error |
Platform Inline Power ISSU client initialization failed at [chars] error [chars] |
Platform ILP ISSU client could not be initiailzed this will\n\ cause catstrophic failure when ISSU upgrade or downgrade\n\ is performed. |
platform-ha |
LOG_STD_SH_TECH_ACTION |
|
ILP_ISSU-3-MSG_NOT_OK |
3-Error |
Platform Inline Power ISSU client message [dec] is not compatible |
Platform Inline Power ISSU client received an incompatible message\n\ from the peer unit. Since the message is not compatible\n\ it can be processed by this unit |
platform-ha |
"show issu message group <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
ILP_ISSU-3-MSG_SIZE |
3-Error |
Platform Inline Power ISSU client failed to get the message size for message [dec] |
Platform Inline Power ISSU client failed to calculate message size\n\ for the message specified. The Platform ILPower ISSU client will not\n\ be able to send message to the standby unit. |
platform-ha |
"show issu message group <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
ILP_ISSU-3-POLICY |
3-Error |
Platform Inline Power ISSU client message type [dec] is [chars] |
Platform Inline Power ISSU client received an message type which it\n\ does not support. The policy is applied to make the session\n\ compatible. |
platform-ha |
"show issu session <client_id>" |
|
ILP_ISSU-3-SEND_FAILED |
3-Error |
Platform Inline Power ISSU client failed to send a negotiation message error [dec] |
Platform ILPower ISSU client could not send a session negotiation\n\ message to the peer. When there is a problem in the\n\ negotiation the standby unit can not be brought up. |
platform-ha |
"show logging and show checkpoint client" |
|
ILP_ISSU-3-SESSION |
3-Error |
Platform ILPower ISSU client [chars] |
Platform Inline Power ISSU client observed an error during a session\n\ negotiation with the peer unit. When there is a problem\n\ with the session the standby unit can not be brought up. |
platform-ha |
"show issu capability entries <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated capability <session_id>" |
|
ILP_ISSU-3-SESSION_UNREGISTRY |
3-Error |
Platform ILPower ISSU client failed to unregister session information. Error: [dec] [chars] |
The Platform Inline Power ISSU client failed to unregister session information. |
platform-ha |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ILP_ISSU-3-TRANSFORM |
3-Error |
Platform Inline Power ISSU client [chars] transform failed error [chars] |
Platform Inline Power ISSU client could not transform the message.\n\ If the transmit transformation failed it means that the\n\ checkpoint message can not be sent to the standby unit.\n\ If the receive transformation failed it means that the\n\ checkpoint message can not be applied on the standby\n\ unit. In both cases the Platform Inline Power state will not\n\ be indentical with the active unit. |
platform-ha |
"show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
ILPOWER_ISSU-3-GET_BUFFER |
3-Error |
Inline power ISSU client failed to get buffer for message.\n\ Error: [dec] [chars] |
Inline power ISSU client failed to get buffer for building\n\ a negotiation message. Hence it cannot send the negotiation\n\ message to the standby unit. When there is a problem in\n\ the negotiaiton the standby unit can not be brought up. |
ilpower |
"show logging and show checkpoint client" |
|
ILPOWER_ISSU-3-INIT |
3-Error |
Inline power ISSU client initialization failed to [chars].Error: [dec] [chars] |
Inline power ISSU client could not be initiailzed this will\n\ cause catstrophic failure when ISSU upgrade or downgrade\n\ is performed. |
ilpower |
LOG_STD_SH_TECH_ACTION |
|
ILPOWER_ISSU-3-INVALID_SESSION |
3-Error |
Inline power ISSU client does not have a valid registered session. |
Inline power ISSU client does not have a valid registered session.\n\ When there is a problem with the session the standby unit cannot\n\ be brought up. |
ilpower |
"show issu capability entries <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated capability <session_id>" |
|
ILPOWER_ISSU-3-MSG_NOT_OK |
3-Error |
Inline power ISSU client message type [dec] is not compatible |
Inline power ISSU client received an incompatible message\n\ from the peer unit. Since the message is not compatible\n\ it cannot be processed by this unit |
ilpower |
"show issu message group <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
ILPOWER_ISSU-3-MSG_SIZE |
3-Error |
Inline power ISSU client failed to get the MTU for message type [dec].\n\ Error: [dec] [chars] |
Inline power ISSU client failed to calculate MTU\n\ for the message specified. The dot1x ISSU client will not\n\ be able to send message to the standby unit. |
ilpower |
"show issu message group <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
ILPOWER_ISSU-3-SEND_NEGO_FAILED |
3-Error |
Inline power ISSU client failed to send negotiation message.\n\ Error: [dec] [chars] |
Inline power ISSU client failed to send a session negotiation\n\ message to the peer. When there is a problem in the ISSU\n\ negotiation the standby unit can not be brought up. |
ilpower |
"show logging and show checkpoint client" |
|
ILPOWER_ISSU-3-SESSION_NEGO |
3-Error |
Inline power ISSU client encountered unexpected client nego_done.\n\ Error: [dec] [chars] |
Inline power ISSU client encountered an unexpected 'client\n\ negotiation done'. |
ilpower |
"show issu session <client_id> and\n\ show issu negotiated capability <session_id>" |
|
ILPOWER_ISSU-3-SESSION_REGISTRY |
3-Error |
Inline power ISSU client failed to register session information.\n\ Error: [dec] [chars] |
Inline power ISSU client failed to register session information.\n\ When there is a problem with the session the standby unit cannot\n\ be brought up. |
ilpower |
"show issu capability entries <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated capability <session_id>" |
|
ILPOWER_ISSU-3-SESSION_UNREGISTRY |
3-Error |
Inline power ISSU client failed to unregister session information.\n\ Error: [dec] [chars] |
Inline power ISSU client failed to unregister session information. |
ilpower |
"show issu session <client_id> and\n\ show issu negotiated capability <session_id>" |
|
ILPOWER_ISSU-3-TRANSFORM_FAIL |
3-Error |
Inline power ISSU client [chars] transform failed for message type [dec].\n\ Error: [dec] [chars] |
Inline power ISSU client could not transform the message.\n\ If the transmit transformation failed it means that the\n\ checkpoint message can not be sent to the standby unit.\n\ If the receive transformation failed it means that the\n\ checkpoint message can not be applied on the standby\n\ unit. In both cases the Inline power state will not\n\ be indentical with the active unit. |
ilpower |
"show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
ILPOWER-2-PRIO_CRIT_LIMIT |
2-Critical |
Priority [dec] reached critical limit. Load shedding can lead to chassis reload. Please avoid configuring any more ports at this priority level. Maximum interface power is used for this calculation. |
This priority level reached maximum allowed wattage |
inline-power |
"Please distribute ports to another priority" |
|
ILPOWER-2-PRIO_CRIT_LIMIT_SVL |
2-Critical |
On Chassis [dec] priority [dec] reached critical limit. Load shedding can lead to chassis reload. Please avoid configuring any more ports at this priority level. Maximum interface power is used for this calculation. |
This priority level reached maximum allowed wattage |
inline-power |
"Please distribute ports to another priority" |
|
ILPOWER-3-CONTROLLER_ERR |
3-Error |
Controller error Controller number [dec]: [chars] |
An error reported or caused by the Power over Ethernet PoE controller is detected. |
inline-power |
LOG_STD_SH_TECH_ACTION |
|
ILPOWER-3-CONTROLLER_ERR |
3-Error |
Controller error Controller number [dec]: [chars] |
An error reported or caused by the Power over Ethernet PoE controller is detected. |
inline-power |
LOG_STD_SH_TECH_ACTION |
|
ILPOWER-3-CONTROLLER_IF_ERR |
3-Error |
Controller interface error [chars]: [chars] |
An interface error is detected between the Power over Ethernet PoE controller and system. |
inline-power |
LOG_STD_SH_TECH_ACTION |
|
ILPOWER-3-CONTROLLER_IF_ERR |
3-Error |
Controller interface error [chars]: [chars] |
An interface error is detected between the Power over Ethernet PoE controller and system. |
inline-power |
LOG_STD_SH_TECH_ACTION |
|
ILPOWER-3-CONTROLLER_PORT_ERR |
3-Error |
Controller port error Interface [chars]: [chars] |
A port error reported by the Power over Ethernet PoE controller is detected. |
inline-power |
LOG_STD_SH_TECH_ACTION |
|
ILPOWER-3-CONTROLLER_PORT_ERR |
3-Error |
Controller port error Interface [chars]: [chars] |
A port error reported by the Power over Ethernet PoE controller is detected. |
inline-power |
LOG_STD_SH_TECH_ACTION |
|
ILPOWER-3-CONTROLLER_POST_ERR |
3-Error |
Inline Power Feature is disabled on this switch because\n\ Power On Self Test POST failed on this switch.\n\msgdef_explanation An error reported or caused by the Power over Ethernet |
- |
- |
- |
|
ILPOWER-3-CONTROLLER_POST_ERR |
3-Error |
Inline Power Feature is disabled on this switch because\n\ Power On Self Test POST failed on this switch.\n\msgdef_explanation An error reported or caused by the Power over Ethernet |
- |
- |
- |
|
ILPOWER-3-ILPOWER_INTERNAL_IF_ERROR |
3-Error |
Inline Power internal error interface [chars]: [chars] |
A software check failed during Power over Ethernet PoE processing. |
inline-power |
LOG_STD_SH_TECH_ACTION |
|
ILPOWER-3-ILPOWER_INTERNAL_IF_ERROR |
3-Error |
Inline Power internal error interface [chars]: [chars] |
A software check failed during Power over Ethernet PoE processing. |
inline-power |
LOG_STD_SH_TECH_ACTION |
|
ILPOWER-3-SHUT_OVERDRAWN |
3-Error |
Interface [chars] is shutdown as it is consuming more than the maximum configured power [dec] milliwatts. |
Interface is shutdown because it is consuming more than the maximum configured power |
inline-power |
"Make sure correct power is budgeted for this interfac\n\e based on the power device electrical specifications or ratings. It is recommended to change the police cutoff power to a higher value to keep the device powered on" |
|
ILPOWER-3-SHUT_OVERDRAWN |
3-Error |
Interface [chars] is shutdown as it is consuming more than the maximum configured power [dec] milliwatts. |
Interface is shutdown because it is consuming more than the maximum configured power |
inline-power |
"Make sure correct power is budgeted for this interfac\n\e based on the power device electrical specifications or ratings. It is recommended to change the police cutoff power to a higher value to keep the device powered on" |
|
ILPOWER-4-ILPOWER_POWER_SUPPLY |
4-Warning |
PoE Power Supply [chars]: [chars] |
The power supply for PoE is OIR |
inline-power |
"Make sure power supply to PoE input is inserted after removal" |
|
ILPOWER-4-ILPOWER_POWER_SUPPLY |
4-Warning |
PoE Power Supply [chars]: [chars] |
The power supply for PoE is OIR |
inline-power |
"Make sure power supply to PoE input is inserted after removal" |
|
ILPOWER-4-ILPOWER_PS_ABSENCE |
4-Warning |
PoE module Power Supply not present \n\ Inline Power Feature is disabled on [chars] because Power On Self Test POST failed \n : [chars] |
The power supply for PoE expansion module is not present or not inserted properly or faulty |
inline-power |
"Make sure power supply to expansion module is inserted properly\ and reload the switch with PoE power supply present" |
|
ILPOWER-4-ILPOWER_PS_ABSENCE |
4-Warning |
PoE module Power Supply not present \n\ Inline Power Feature is disabled on [chars] because Power On Self Test POST failed \n : [chars] |
The power supply for PoE expansion module is not present or not inserted properly or faulty |
inline-power |
"Make sure power supply to expansion module is inserted properly\ and reload the switch with PoE power supply present" |
|
ILPOWER-4-LOG_OVERDRAWN |
4-Warning |
Interface [chars] is overdrawing power. it is consuming [dec] milliwatts where as maximum configured power is [dec] milliwatts. |
- |
inline-power |
"Make sure correct power is budgeted for this interface based on the power device electrical specifications or ratings. Otherwise you might risk overloading the switch. It is recommended to change the police cutoffpower appropriately if needed" |
|
ILPOWER-4-LOG_OVERDRAWN |
4-Warning |
Interface [chars] is overdrawing power. it is consuming [dec] milliwatts where as maximum configured power is [dec] milliwatts. |
- |
inline-power |
"Make sure correct power is budgeted for this interface based on the power device electrical specifications or ratings. Otherwise you might risk overloading the switch. It is recommended to change the police cutoffpower appropriately if needed" |
|
ILPOWER-4-PRIO_WARN_LIMIT |
4-Warning |
Priority [dec] is reaching critical limit. Maximum interface power is used for this calculation. |
This priority level reached warning limit wattage |
inline-power |
"Please don't configure any more ports " "at this priority." |
|
ILPOWER-4-PRIO_WARN_LIMIT_SVL |
4-Warning |
On Chassis [dec] priority [dec] is reaching critical limit. Maximum interface power is used for this calculation. |
This priority level reached warning limit wattage |
inline-power |
"Please don't configure any more ports at this priority" |
|
ILPOWER-4-WARNING |
4-Warning |
Power-over-Ethernet is disabled on this switch \n\ PoE functionality requires a power input of 44 to 57 Volts DC |
The power supply voltage is NOT in range 44 V-57 V to support PoE/PoE+ |
inline-power |
"Make sure the power supply Voltage is in range 44 V-57 V if intend to use PoE/PoE+" |
|
ILPOWER-5-CLR_OVERDRAWN |
5-Notice |
Interface [chars] is NOT overdrawing power. it is consuming [dec] milliwatts where as maximum configured value is [dec] milliwatts. |
- |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-CLR_OVERDRAWN |
5-Notice |
Interface [chars] is NOT overdrawing power. it is consuming [dec] milliwatts where as maximum configured value is [dec] milliwatts. |
- |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-DET_SHORT_SPARE_PAIR |
5-Notice |
Interface [chars]: spare pair short detected |
spare pair short detect error has occurred power on spare pair will not be supplied |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-DET_SHORT_SPARE_PAIR |
5-Notice |
Interface [chars]: spare pair short detected |
spare pair short detect error has occurred power on spare pair will not be supplied |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-DET_TIMEOUT_SPARE_PAIR |
5-Notice |
Interface [chars]: spare pair detect timeout |
spare pair timeout detect error has occurred power on spare pair will not be supplied |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-DET_TIMEOUT_SPARE_PAIR |
5-Notice |
Interface [chars]: spare pair detect timeout |
spare pair timeout detect error has occurred power on spare pair will not be supplied |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-DETECT |
5-Notice |
Interface [chars]: Power Device detected: [chars] |
The switch has detected the attached power device. |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-IEEE_DISCONNECT |
5-Notice |
Interface [chars]: PD removed |
The powered device is no longer connected to the\n\ switch or the connected powered device is being powered by an\n\ external AC power source. The switch is no longer providing power on\n\ the interface. |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-IEEE_DISCONNECT |
5-Notice |
Interface [chars]: PD removed |
The powered device is no longer connected to the\n\ switch or the connected powered device is being powered by an\n\ external AC power source. The switch is no longer providing power on\n\ the interface. |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-ILPOWER_POWER_CDP_SHUT |
5-Notice |
Interface [chars]: inline power shut |
- |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-ILPOWER_POWER_CDP_SHUT |
5-Notice |
Interface [chars]: inline power shut |
- |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-ILPOWER_POWER_DENY |
5-Notice |
Interface [chars]: inline power denied. Reason: [chars] |
There is not enough power remaining in the switch to supply to\n\ the Power over Ethernet PoE port. |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-ILPOWER_POWER_DENY |
5-Notice |
Interface [chars]: inline power denied. Reason: [chars] |
There is not enough power remaining in the switch to supply to\n\ the Power over Ethernet PoE port. |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-IMAX_SPARE_PAIR |
5-Notice |
Interface [chars]: spare pair power error: IMAX |
spare pair imax error has occurred power on spare pair will not be supplied |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-INVALID_IEEE_CLASS |
5-Notice |
Interface [chars]: has detected invalid IEEE class: [dec] device. Power denied |
The power device has invalid IEEE class. switch won't power\n\up the device |
- |
LOG_STD_NO_ACTION |
|
ILPOWER-5-INVALID_IEEE_CLASS |
5-Notice |
Interface [chars]: has detected invalid IEEE class: [dec] device. Power denied |
The power device has invalid IEEE class. switch won't power\n\up the device |
- |
LOG_STD_NO_ACTION |
|
ILPOWER-5-LINKDOWN_DISCONNECT |
5-Notice |
Interface [chars]: Link down disconnect |
The powered device is no longer connected to the\n\ switch or the connected powered device is being powered by an\n\ external AC power source. The switch is no longer providing power on\n\ the interface. |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-LINKDOWN_DISCONNECT |
5-Notice |
Interface [chars]: Link down disconnect |
The powered device is no longer connected to the\n\ switch or the connected powered device is being powered by an\n\ external AC power source. The switch is no longer providing power on\n\ the interface. |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-LLDP_SHUTDOWN |
5-Notice |
Interface [chars]: PD requested shutdown for [dec] sec via LLDP MDI TLV |
Inline power is removed because \n\ PD requested shutdown via LLDP MDI TLV |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-PD_ENTRY_REMOVAL |
5-Notice |
Interface [chars]: power device entry removed admin_state=[chars] oper_state=[chars] |
received power device removal event from controller |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-PD_POWER_DEMOTE |
5-Notice |
Interface [chars] requested power=[dec]w hardware limit=[dec]w |
Requested power is greater than the hardware limit |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-PGOOD_TIMEOUT_SPARE_PAIR |
5-Notice |
Interface [chars]: spare pair power good timeout error |
spare pair power good timeout error has occurred power on spare pair will not be supplied |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-PGOOD_TIMEOUT_SPARE_PAIR |
5-Notice |
Interface [chars]: spare pair power good timeout error |
spare pair power good timeout error has occurred power on spare pair will not be supplied |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-POLICE_POWER_INVALID |
5-Notice |
Interface [chars]: invalid power police [dec] milliwatts current [dec] mA voltage [dec] mV |
power policing current or voltage value is invalid. |
- |
LOG_STD_SH_TECH_ACTION |
|
ILPOWER-5-POLICE_POWER_INVALID |
5-Notice |
Interface [chars]: invalid power police [dec] milliwatts current [dec] mA voltage [dec] mV |
power policing current or voltage value is invalid. |
- |
LOG_STD_SH_TECH_ACTION |
|
ILPOWER-5-POWER_GRANTED |
5-Notice |
Interface [chars]: Power granted |
There is enough power available in the switch and\n\ the switch is providing power on the interface. |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-POWER_GRANTED |
5-Notice |
Interface [chars]: Power granted |
There is enough power available in the switch and\n\ the switch is providing power on the interface. |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-PWRGOOD_SPARE_PAIR |
5-Notice |
Interface [chars]: spare pair power good |
Spare pair power request was successful and power is available on spare pair |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-PWRGOOD_SPARE_PAIR |
5-Notice |
Interface [chars]: spare pair power good |
Spare pair power request was successful and power is available on spare pair |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-SENSE_POWER_INVALID |
5-Notice |
Interface [chars]: invalid power sense [dec] milliwatts current [dec] mA voltage [dec] mV |
power sensing current or voltage value is invalid. |
inline-power |
LOG_STD_SH_TECH_ACTION |
|
ILPOWER-5-SENSE_POWER_INVALID |
5-Notice |
Interface [chars]: invalid power sense [dec] milliwatts current [dec] mA voltage [dec] mV |
power sensing current or voltage value is invalid. |
inline-power |
LOG_STD_SH_TECH_ACTION |
|
ILPOWER-5-SINGLE_PAIRSET_FAULT |
5-Notice |
Interface [chars]: shutting down [chars] pairset due to [chars] fault |
The dual signature PD on this port has hit a critcal fault on one pairset and hence that pairset will be shutdown |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-TSTART_SPARE_PAIR |
5-Notice |
Interface [chars]: spare pair power error: TSTART |
spare pair tstart error has occurred power on spare pair will not be supplied |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-5-TSTART_SPARE_PAIR |
5-Notice |
Interface [chars]: spare pair power error: TSTART |
spare pair tstart error has occurred power on spare pair will not be supplied |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-6-SET_ILPOWER |
6-Information |
Set power allocated to POE to [dec] for slot [dec] |
The power allocated to POE has changed |
inline-power |
LOG_STD_NO_ACTION |
|
ILPOWER-7-DETECT |
7-Debug |
Interface [chars]: Power Device detected: [chars] |
The switch has detected the attached power device. |
inline-power |
LOG_STD_NO_ACTION |
|
IM_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 IM EEPROM. The format of the EEPROM of the indicated IM might not be up to date. |
spa-infra |
SPA_EEPROM_STD_BUG_ACTION |
|
IM_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 IM. The type of error is indicated in the error message. |
asr900-im |
SPA_EEPROM_STD_BUG_ACTION |
|
IM-3-UNSUPPORTED_DATA |
3-Error |
Data conversion error [chars] 0x%X |
An internal software error has occured when converting the data specified in the message from one representation to another. |
asr900-im |
LOG_STD_SH_TECH_ACTION |
|
IMAP_ALG-3-CHUNK_CREATE_FAIL |
3-Error |
- |
IMAP code has detected a cleartext logon attempt in the inspected IMAP connection while secure-login is configured. This command has been rejected. |
cpp-ucode |
"This message is for informational purposed only but may indicate" "a security problem." |
|
IMPOSITION_DISABLED-5-ATOM_TRANS |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
IMPOSITION_ENABLED-5-ATOM_TRANS |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
IMSP_ACLMGR-2-NOMEM |
2-Critical |
[chars]. Out of memory |
System is out of Memory |
imsp-acl |
LOG_STD_ACTION |
|
IMSP_ACLMGR-2-NOVMR |
2-Critical |
Cannot generate hardware representation of access list [chars] |
There were insufficient resources available for generating a hardware representation of the access list. Either lack of available logical operation units or lack of memory can cause this problem. Logical operation units are needed when a match on TCP flags is specified or when any test other than eq that is: ne gt lt or range is |
firmware |
"Modify the ACL configuration to use fewer resources." |
|
IMSP_ACLMGR-3-INVALIDACL |
3-Error |
[chars] failed |
Addition/Deletion Failed |
imsp-acl |
LOG_STD_ACTION |
|
IMSP_ACLMGR-3-INVALIDPARAM |
3-Error |
Invalid [chars] [dec] encountered |
ACL Manager has encountered an invalid parameter value. |
firmware |
"show running-config" |
|
IMSP_ACLMGR-3-MAXACE |
3-Error |
MAX ACE count [dec] exceeded |
No. ACEs configured is beyond limit |
imsp-acls |
LOG_STD_ACTION |
|
IMSP_ACLMGR-3-UNKNOWNACTION |
3-Error |
Unknown VMR access group action 0x[hec] |
An internal software error has occurred. |
firmware |
LOG_STD_ACTION |
|
IMSP_ACLMGR-3-UNKNOWNL4OPERATION |
3-Error |
Unknown L4 operation 0x[hec] |
ACL Manager module received invalid value for L4 operation. The problem can be due to memory corruption or bad system memory. |
firmware |
IMSP_ACL_L4OP_ERROR |
|
IMSP_ACLMGR-4-ACLTCAMFULL |
4-Warning |
[chars]ACL TCAM Full. Software Forwarding packets on |
The ACL configuration is too large to fit in the platform -specific ACL TCAM table. |
firmware |
"Simplify the ACLs applied to interfaces or reduce" " their number." |
|
IMSP_CTS-3-SGACL_PROGRAM_ERR |
3-Error |
Unable to [chars] SGACLs for sgt [dec] dgt [dec] with reason [chars] |
An unexpected condition has occurred while programming SGACL |
petra-cts |
"Reconfigure the SGACL" |
|
IMSP_CTS-3-SGT_PROGRAM_ERR |
3-Error |
[chars] binding [chars] failed for [chars] with reason [chars]\n |
An unexpected condition has occurred while programming IP SGT |
- |
"Reconfigure the IP SGT binding" |
|
IMSP_CTS-6-INVALID_ACE |
6-Information |
Platform can suppor match only ip protocol tcp/udp src or dst port |
Invalid match criteria |
- |
"Remove one or more entries from ACES\n" |
|
IMSP_CTS-6-SGACL_POLICIES |
6-Information |
Platform can not support more than [dec] ACEs per cell. |
SGACL policy entries limit exceeded |
- |
"Remove one or more entries from ACES\n" |
|
IMSP_CTS-6-SGACL_TABLE_FULL |
6-Information |
Platform can not support more than [dec] SGT/DGT pairs |
SGACL table resource full |
- |
"Remove SGACL\n" |
|
IMSP_CTS-6-SGT_TABLE_FULL |
6-Information |
Platform can not support more than [dec] [chars] bindings |
IP/SUBNET SGT table resource full |
- |
"Remove SGT binding\n" |
|
IMSP_EPM-3-EPM_ACE_MAX_CROSS |
3-Error |
EPM - Reached max ace limit255 |
An unexpected condition has occurred since max ACE limit reached |
l2security |
"Correct the config which can have max of 255 ACEs\ per port" |
|
IMSP_IPSG-3-IPSG_ADDRS_FULL |
3-Error |
IPSG Platform Address list is null |
An unexpected condition has occurred which is due to the absence of\n\ resource available in IPSG address list |
l2security |
"Correct the config which can have max of 254 IP address" |
|
INBAND_or_EOBC-3-INVALID_SEND |
3-Error |
Invalid send operation packet on [chars] |
Internal error caused illegal call to device driver:normal operation continues |
msfc2 |
LOG_STD_RECUR_ACTION |
|
INBAND-3-BAD_PAK |
3-Error |
Possibly un-encapsulated packet passed to Mistral: int [chars] type [dec] stat 0x[hec] flags 0x[hec] size [dec] offset [dec] requeue_token [dec] r1 [dec] r2 [dec] total detected [dec] |
Badly encapsulated packet from process level |
msfc2 |
LOG_STD_ACTION |
|
INBAND-3-INV_TX_PACKET |
3-Error |
[chars]: packet neither on IBL nor on OBL |
The packet to be transmitted is neither on the IBL nor on the OBL:normal operation continues |
msfc2 |
LOG_STD_RECUR_ACTION |
|
INBAND-3-INVALID_PAK |
3-Error |
Sent from [chars] with invalid [chars] of [dec] bytes with source vlan:[dec] and packetsize:[dec] |
Badly formed packet in inband fastpath or process level |
msfc2 |
LOG_STD_ACTION |
|
INBAND-3-NOBUF |
3-Error |
Dropping the packet. |
The system controller receive buffer pool has been exhausted. No further input packets can be handled until some buffers are returned to the pool:normal operation continues |
msfc2 |
LOG_STD_RECUR_ACTION |
|
INBAND-6-BAD_IDB |
6-Information |
Bad idb for vector [chars]: [chars] vlan [dec] total [dec] |
Bad idb returned from get_l3_swidb |
msfc2 |
LOG_STD_RECUR_ACTION |
|
INDXOBJ-3-ADD_ERROR |
3-Error |
index add for [chars] failed: [chars] |
index object routine error |
- |
LOG_STD_ACTION |
|
INDXOBJ-3-INTERRUPT |
3-Error |
index object routine [chars] called from interrupt context |
inappropriate index object routine called from interrupt routine. |
- |
LOG_STD_ACTION |
|
INFO-5-LDP |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
INFO-6-OF_AGENT |
6-Information |
ERRMSG_NOFLAGS |
- |
- |
- |
|
INFO-6-OVS |
6-Information |
ERRMSG_NOFLAGS |
- |
- |
- |
|
INFRA_ARL-3-BAD_ART_ID |
3-Error |
art_id=[hec] |
An internal error occurred |
cpp-ucode |
LOG_STD_ACTION |
|
INFRA_STATS-3-OUT_OF_RANGE |
3-Error |
[chars] [dec] out of max size [dec] STATS work improperly |
Data invalid from DMA |
cmts-application |
LOG_STD_RECUR_ACTION |
|
INFRA_STATS-3-OUT_OF_SHMEM |
3-Error |
out of max size [dec] start %p curloc %p type [dec] len [dec] next %lld |
Data invalid from NONDMA |
cmts-application |
LOG_STD_RECUR_ACTION |
|
INFRA_STATS-4-PROCESS_OVERTIME |
4-Warning |
NON_DMA has been processing for [dec]ms check if CPU high |
Process NONDMA Stats overtime it is probably related to CPU high utilization. It is normal to see a small amount of it right after LCHA with scale modems due to low priority of this process and high CPU |
cmts-application |
LOG_STD_RECUR_ACTION |
|
INFRA-3-INVALID_GPM_ACCESS |
3-Error |
Invalid GPM [chars] at [hec] HAL start [hec] HAL end [hec] INFRA start [hec] INFRA [hec] NET [hec] |
Processing packet went beyond valid packet data packet was possibly invalid ppe info and encrypted pkt dump follow |
cpp-ucode |
LOG_STD_ACTION |
|
INFRA-3-INVALID_GPM_ACCESS |
3-Error |
Invalid GPM [chars] at [hec] HAL start [hec] HAL end [hec] INFRA start [hec] INFRA [hec] NET [hec] |
Processing packet went beyond valid packet data packet was possibly invalid ppe info and encrypted pkt dump follow |
cpp-ucode |
LOG_STD_ACTION |
|
INFRA-3-INVALID_GPM_ACCESS_DATA |
3-Error |
- |
Packet associated with previous exception error The packet data has been encrypted |
cpp-ucode |
LOG_STD_ACTION |
|
INFRA-3-INVALID_GPM_ACCESS_DATA |
3-Error |
- |
Packet associated with previous exception error The packet data has been encrypted |
cpp-ucode |
LOG_STD_ACTION |
|
INFRA-3-INVALID_GPM_ACCESS_INFO |
3-Error |
%08x %08x %08x %08x %08x %08x %08x %08x %08x %08x %08x %08x %08x %08x %08x %08x |
Registers associated with previous exception error |
- |
LOG_STD_ACTION |
|
INFRA-3-INVALID_GPM_ACCESS_INFO |
3-Error |
%08x %08x %08x %08x %08x %08x %08x %08x %08x %08x %08x %08x %08x %08x %08x %08x |
Registers associated with previous exception error |
- |
LOG_STD_ACTION |
|
INFRA-3-L0I_FETCH_ERROR |
3-Error |
thread=[dec] PC=0x[hec] |
Level-0 instruction cache fetch error possibly recoverable |
cpp-ucode |
LOG_STD_ACTION |
|
INFRA-3-L1L2_ICACHE_ERROR |
3-Error |
thread=[dec] reg=[chars] addr=0x%llx val=0x[hec] |
L1/L2 ICACHE error possibly recoverable |
cpp-ucode |
LOG_STD_ACTION |
|
INIT_FAIL-3-ATOM_TRANS |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
INIT_TAG_ALLOC-4-LCON |
4-Warning |
ERRMSG_NOFLAGS |
- |
- |
- |
|
INIT-3-LCON |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
INIT-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
INIT-3-LDPLIB |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
INIT-3-MPLS_TE_PCALC |
3-Error |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
INTERCHASSIS_REDUNDANCY-4-STDBY_PRESENT |
4-Warning |
Removal of standby RP in location [chars] is recommended for inter-chassis redundancy configuration |
Removal of standby RP from the chassis is recommended for inter-chassis redundancy |
iosxe-b2b-ha |
LOG_STD_ACTION |
|
INTERFACE_API-1-NAMESTRTOOLONG |
1-Alert |
Interface name [chars].[dec] exceeded maximum allowed length [dec] |
An internal software error occurred. |
idb |
LOG_STD_ACTION |
|
INTERFACE_API-1-NOMORE_HASWIDBS |
1-Alert |
No more IDBS can be created. \nThe maximum allowed numbers [dec] has been reached on Standby \nPlease force redundancy mode to RPR if full Active Capacity [dec] is needed |
No more Software IDB numbers can be Created. The maximum allowed numbers has been reached for this High Available System.\n |
idb |
- |
|
INTERFACE_API-1-NOMOREHWIDBNUMBERS |
1-Alert |
No more hardware IDB numbers can be issued. The maximum allowed numbers [dec] has been reached for this platform.\n |
No more hardware IDB numbers can be issued. The maximum allowed numbers has been reached for this platform.\n |
idb |
"In addition to the following copy the information " "from <CmdBold>show idb<NoCmdBold>. " LOG_STD_ACTION |
|
INTERFACE_API-1-NOMORESWIDB |
1-Alert |
No more SWIDB can be allocated maximum allowed [dec] |
No more Interfaces can be created because the maximum number \n\ of SWIDB allowed for this platform has been reached |
Obtain from traceback. |
LOG_STD_ACTION |
|
INTERFACE_API-1-NOMORESWIDBNUMBERS |
1-Alert |
No more software IDB numbers can be issued. The maximum allowed numbers [dec] has been reached for this platform.\n |
No more software IDB numbers can be issued. The maximum allowed numbers has been reached for this platform.\n |
idb |
"In addition to the following copy the information " "from <CmdBold>show idb<NoCmdBold>. " LOG_STD_ACTION |
|
INTERFACE_API-3-BADIDBSTATUSCHANGECALL |
3-Error |
Invalid function call at interrupt level. |
An internal function was illegally called at interrupt level. This error might be caused by incorrectly coded creation or deletion of an interface or during an OIR operation.\n |
idb |
"Perform a search of the Bug Toolkit " BUG_TOOLKIT "." "If you still require assistance copy the error message " "exactly as it appears on the console or in the system log. " "Issue the <CmdBold>show tech<NoCmdBold> command and copy the " "output. If you performed any actions before the error message " "appeared make a note of this. Open a case with the Technical " "Assistance Center via the Internet " TAC_CASE_OPEN " or contact " "your Cisco technical support representative and provide the " "representative with the gathered information." |
|
INTERFACE_API-3-CANNOTGETMTU |
3-Error |
Error [dec] received while getting MTU: [chars]. Using default [dec] |
A software error has occurred while attempting to retrieve the MTU value from the interface. |
Obtain from traceback. |
LOG_STD_ACTION |
|
INTERFACE_API-3-HWIDBQREENTRANT |
3-Error |
[chars] in progress of being inserted/removed ignoring new request to [chars] |
A software error has occurred while attempting to insert or remove the interface into the system as there's already another attempt in progress to insert or remove this interface. The first attempt must complete before a new attempt can be started. The user should retry this operation at a later time. |
idb |
LOG_STD_ACTION |
|
INTERFACE_API-3-IFNUMTOIDBERROR |
3-Error |
Error occurred while using the ifnum to idb table for interface [chars] if number [dec] during [chars] |
A software error has occurred. This message is displayed when an operation on the if_number to idb mapping table could not be performed successfully. |
idb |
LOG_STD_ACTION |
|
INTERFACE_API-3-INVALIDSUBBLOCKPARAMETERS |
3-Error |
Invalid subblock parameters for [chars] were supplied. |
An internal software error occurred. |
idb |
"Copy the error message exactly as it appears on the console or in " "the system log. Issue the show idb and show tech-support " "commands to gather data that may help identify the nature of " "the error. Also perform a search of the Bug Toolkit " BUG_TOOLKIT "." "If you still require assistance open a case with the " "Technical Assistance Center via the Internet " TAC_CASE_OPEN " or contact your Cisco technical support representative and " "provide the representative with the gathered information." |
|
INTERFACE_API-3-NOADDSUBBLOCK |
3-Error |
The [chars] subblock named [chars] was not added to [chars] |
A software error has occured this message is displayed when IDB subblocks cannot be added. |
Obtain from traceback. |
LOG_STD_ACTION |
|
INTERFACE_API-3-NODESTROYSUBBLOCK |
3-Error |
The [chars] subblock named [chars] was not removed |
A software error has occured this message is displayed when \n\ IDB subblocks cannot be removed. |
Obtain from traceback. |
LOG_STD_ACTION |
|
INTERFACE_API-3-NOSUBBLOCK |
3-Error |
[chars] subblock does not exist on interface [chars] |
An internal software error occurred. |
Obtain from traceback. |
LOG_STD_ACTION |
|
INTERFACE_API-3-SUBNUMDBERR |
3-Error |
subnum [hec] error in [chars] |
A software error has occured this message is displayed when a problem has occured with a sub_number db. |
Obtain from traceback. |
LOG_STD_ACTION |
|
INTERFACE_API-4-BADPAKINPUT |
4-Warning |
pak->if_input is not initialized |
An internal software error occurred. |
Obtain from traceback. |
LOG_STD_RECUR_ACTION |
|
INTERFACE_API-4-BADPAKOUTPUT |
4-Warning |
pak->if_output is not initialized on interface [chars] |
An internal software error occurred. |
Obtain from traceback. |
LOG_STD_RECUR_ACTION |
|
INTERFACE_API-4-BADPOINTER |
4-Warning |
Function [chars] detected an invalid [chars] pointer of %08lX ignoring |
A software error has occurred this message is displayed when \n\ an invalid pointer is detected. |
Obtain from traceback. |
"LOG_STD_SH_TECH_ACTION" |
|
INTERFACE_API-4-BADSWIDB |
4-Warning |
[chars] may not be referencing the correct swidb |
An internal software error occurred. |
Obtain from traceback. |
LOG_STD_RECUR_ACTION |
|
INTERFACE_API-4-TBLERROR |
4-Warning |
A error occurred while using the Index Table utility for [chars]. |
- |
Obtain from traceback. |
LOG_STD_ACTION |
|
Interface [chars]: [chars] |
The CHOCX RP driver queries the LC for SONET information the LC didn't reply. |
c7600-sip-200 |
"This is a internal software error. Decode the " "traceback. Enable <CmdBold>debug hw-module subslot " "<slot>/<bay> command<NoCmdBold>. Check Bug Toolkit " "before calling the TAC. When calling the TAC " "please provide the above information along with the " "output of <CmdBold>show logging<NoCmdBold> and the " "output of <CmdBold>show tech<NoCmdBold details." |
- |
- |
|
INTF_SYNC -2-INITSYS |
2-Critical |
[chars] |
A software error occurred during initialization of the Interface Sync RF subsystem |
- |
"Check for sufficient processor memory." LOG_STD_ACTION |
|
INTF_SYNC-3-INVALID_MSG |
3-Error |
Incorrectly formatted message 0x[hec] 0x[hec] received by [chars] |
Inconsistent message data was received from the peer CPU possibly due to an incompatible image version. |
- |
LOG_STD_ACTION |
|
INTF_SYNC-3-NO_BUFFER |
3-Error |
Unable to transmit message type [dec] from [chars] |
A transmit error occurred while sending msg to other CPU due to non-availability of buffer |
- |
LOG_STD_ACTION |
|
INTF_SYNC-3-TRANSMIT_ERROR |
3-Error |
Unable to transmit message type [dec] from [chars] |
A transmit error occurred while sending msg to other CPU due to msg translation |
- |
LOG_STD_ACTION |
|
INTF_SYNC-3-UNKNOWN_MSG |
3-Error |
Unknown message type 0x[hec] received by [chars] |
An unknown message type was received from the peer CPU possibly due to an incompatible image version. |
- |
LOG_STD_ACTION |
|
INTF_SYNC-5-UNSUPPORTED_MSG |
5-Notice |
Msgtype [chars] sent by [chars] unsupported by peer. |
Peer responded that it didn't recognize a message sent by this CPU possibly due to a different image version. |
- |
"May require a software upgrade on the Standby CPU. " LOG_STD_ACTION |
|
INTR_MGR-3-BURST |
3-Error |
[chars] [chars] [[dec]] |
A burst of hardware interrupts of the type indicated has occurred. |
- |
"The message text on the console or in the " "system log provides more information " "on the specific nature of the error. " LOG_STD_SH_TECH_ACTION |
|
INTR_MGR-3-INTR |
3-Error |
[chars] [chars] |
The specified interrupt event has been detected. |
- |
"The message text on the console or in the " "system log provides more information " "on the specific nature of the error. " LOG_STD_SH_TECH_ACTION |
|
INTR_MGR-3-MAXBURST |
3-Error |
[chars] [chars] [[dec]] |
The specified hardware interrupt has exceeded the maximum allowed number of bursts. |
- |
"The message text on the console or in the " "system log provides more information " "on the specific nature of the error. " LOG_STD_SH_TECH_ACTION |
|
INVALID_LSP-3-MPLS_TE_LM |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
INVALID_MSG-3-L2VPN |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
INVEVENT-3-TENSRFSM |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
INVLD_RTR_FRAGMENT-2-MPLS_TE_PCALC |
2-Critical |
ERRMSG_NOFLAGS |
- |
- |
- |
|
INVLD_RTR_ID-2-MPLS_TE_PCALC |
2-Critical |
ERRMSG_NOFLAGS |
- |
- |
- |
|
INVSTATE-3-TENSRFSM |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
INVTRANS-3-TENSRFSM |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
IOMD-2-INITFAIL |
2-Critical |
IOMD initialization error: [chars] Slot [dec] Subslot [dec] |
A failure occurred during initialization of IOMD. The line card that generated the message is not functional. |
iomd |
IOMD_AUTO_RECOVERY_ACTION |
|
IOMD-2-INITFAIL |
2-Critical |
IOMD initialization error: [chars] Slot [dec] Subslot [dec] |
A failure occurred during initialization of IOMD. The line card that generated the message is not functional. |
iomd |
IOMD_AUTO_RECOVERY_ACTION |
|
IOMD-2-IPC_ERR |
2-Critical |
IOMD IPC error: [chars] Slot [dec] Subslot [dec] |
A failure in communication occurred to another process |
iomd |
IOMD_AUTO_RECOVERY_ACTION |
|
IOMD-2-M3_FAKE_SWOVER |
2-Critical |
Asic [dec] on slot [dec] detected a spurious switchover |
ASIC on the linecard detected a fake switchover event. Check if it is a prototype board |
iomd |
IOMD_STD_ACTION |
|
IOMD-2-PCIE_ACCESS_FAIL |
2-Critical |
[chars] on Slot [dec] Subslot [dec]. PCIe access failed HW faulty shutting down this slot. |
A failure occurred during read/write of PCIe registers from HW. This board is not usable in current state. |
iomd |
IOMD_STD_ACTION |
|
IOMD-2-POE_FW_MISMATCH |
2-Critical |
[chars] on Slot [dec] Subslot [dec]. POE is not functional on this line card\n To recover from issue power-cycle the linecard using the CLI: hw-module subslot <Slot>/<Subslot> oir power-cycle |
The Firmware version on this Linecard is not supported by the Software. POE is not functional on this line card The linecard should be power-cycled to recover from this issue. |
iomd |
IOMD_POE_FW_MISMATCH_ACTION |
|
IOMD-2-POE_INIT_FAIL |
2-Critical |
[chars] on Slot [dec] Subslot [dec]. POE functionality will not work on this LC |
A failure occurred during initialization of LC for POE. POE is not functional on the line card that generated the message. |
iomd |
IOMD_STD_ACTION |
|
IOMD-2-POE_RW_FAIL |
2-Critical |
[chars] on Slot [dec] Subslot [dec]. POE functionality will not continue to work on this LC |
A failure occurred during read/write of POE registers from HW. POE is not functional on the line card that generated the message. |
iomd |
IOMD_STD_ACTION |
|
IOMD-2-TIMERFAIL_CXT |
2-Critical |
IOMD timer context error |
A failure occurred during context retrieval for a timer |
iomd |
IOMD_AUTO_RECOVERY_ACTION |
|
IOMD-3-CREATE_TDLH_FAILURE |
3-Error |
Failed to create SPA [dec]/[dec] handle |
Failed to create message handle for SPA communication. |
asr900-im |
LOG_STD_SH_TECH_ACTION |
|
IOMD-3-CREATE_TDLMSG_FAILURE |
3-Error |
Failed to create [chars] message for [chars]. |
Failed to create/allocate necessary TDL message for SPA communication. |
asr900-im |
LOG_STD_SH_TECH_ACTION |
|
IOMD-3-DISPATCH_INIT_TDLH_FAILURE |
3-Error |
Failed to initialize dispatch path for SPA [dec]/[dec] handle |
Failed to initialize dispatch path handle for SPA communication. |
asr900-im |
LOG_STD_SH_TECH_ACTION |
|
IOMD-3-DOMAIN_TDLH_FAILURE |
3-Error |
[chars] rc = [dec] |
Failed to bind message handle for SPA communication. |
asr900-im |
LOG_STD_SH_TECH_ACTION |
|
IOMD-3-HAIPC_FAIL |
3-Error |
Failed to [chars] reason: [chars]. |
Failure in handling IOMD HA IPC. |
asr900-im |
LOG_STD_SH_TECH_ACTION |
|
IOMD-3-HARFROLE_FAIL |
3-Error |
Failed to [chars]. |
Failure to establish start client or server. |
asr900-im |
LOG_STD_SH_TECH_ACTION |
|
IOMD-3-INVALID_HANDLE |
3-Error |
Failed to get a valid IPC handle for type [dec] slot [dec] subslot [dec]. |
The client handle was found to be NULL for the given type/slot/subslot. |
asr900-im |
LOG_STD_SH_TECH_ACTION |
|
IOMD-3-INVALID_SLOT_NUM |
3-Error |
slot= [dec] max slot = [dec] |
An invalid slot number is specified in one of the internal APIs. |
asr900-im |
LOG_STD_SH_TECH_ACTION |
|
IOMD-3-INVALID_SUBSLOT_NUM |
3-Error |
subslot= [dec] max subslot = [dec] |
An invalid subslot number is specified in one of the internal APIs. |
asr900-im |
LOG_STD_SH_TECH_ACTION |
|
IOMD-3-INVALID_TDL_CCAPI_USAGE |
3-Error |
- |
Incorrect usage of an internal API that should only be used on CC. |
asr900-im |
LOG_STD_SH_TECH_ACTION |
|
IOMD-3-IPCALLOCFAIL |
3-Error |
Failed to allocate IPC buffer [chars] |
The SPA failed to allocate a buffer for communication with\n\ the Route Processor ASR1000-RP. |
asr900-im |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
IOMD-3-ISR_RC_ERROR |
3-Error |
ISR return code out of range. rc=[dec] |
The ISR error return code is out of range. |
asr900-im |
LOG_STD_SH_TECH_ACTION |
|
IOMD-3-MARSHAL_ERR |
3-Error |
Failed to marshal [chars]. |
Failure to marshal tdl message |
asr900-im |
LOG_STD_SH_TECH_ACTION |
|
IOMD-3-MESSAGE_ERROR |
3-Error |
Bay [dec]: [chars] |
An unexpected error has occurred. |
asr900-im |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance " LOG_STD_ACTION |
|
IOMD-3-MODULE_MESSAGE |
3-Error |
[chars] |
An error is detected by the firmware running on the module in the slot and subslot specified in the message |
esg-io-infra |
LOG_STD_SH_TECH_ACTION |
|
IOMD-3-NEBS_ACCESS_PID_FAIL |
3-Error |
Failed to acess NGIO PID list for [chars] on slot/bay [dec]/[dec] in NEBS mode |
The access to NGIO PID list failed in NEBS mode and module will not be powered on |
esg-io-infra |
LOG_STD_SH_TECH_ACTION |
|
IOMD-3-NRU_OIR_DRAIN_FAIL |
3-Error |
NRU OIR EPF Fifo drain failed for mac [dec] on slot [dec] |
A failure occurred during NRU OIR EPF Fifo drain. NRU datapath may not functional. |
iomd |
IOMD_STD_ACTION |
|
IOMD-3-QUEUE_FAIL |
3-Error |
Failed to dequeue because [chars]. |
Failure to handle events in queue. |
asr900-im |
LOG_STD_SH_TECH_ACTION |
|
IOMD-3-RFROLE_FAIL |
3-Error |
Failed to update IM role for reason: [chars] |
Failure to handle role update. |
asr900-im |
LOG_STD_SH_TECH_ACTION |
|
IOMD-3-SETUP_TDLH_FAILURE |
3-Error |
Failed to set the alloc/free handler for SPA [dec]/[dec] handle |
Failed to set the alloc/free handler for SPA communication. |
asr900-im |
LOG_STD_SH_TECH_ACTION |
|
IOMD-3-SIGBUS_ERROR |
3-Error |
SIGBUS received for IM in slot: [dec] |
SIGBUS error encountered for IM |
asr900-im |
LOG_STD_SH_TECH_ACTION |
|
IOMD-3-TIMER_FAIL |
3-Error |
Failed to [chars]. |
Failure in timer processing. |
asr900-im |
LOG_STD_SH_TECH_ACTION |
|
IOMD-3-UNSUPPORTED_DATA |
3-Error |
Data conversion error [chars] 0x%X |
An internal software error has occured when converting the data specified in the message from one representation to another. |
asr900-im |
LOG_STD_SH_TECH_ACTION |
|
IOMD-3-UNSUPPORTED_LEGACY_SWITCH |
3-Error |
The previous generation switch module [chars] in slot [dec] bay [dec] is not compatible with current next-gen switching mode |
Legacy and next-gen switch modules have different feature set and cli behaviors which require system to determine corresponding switching mode at system boot time. Current mode selection is to check whether next-gen switch module locates in the chassis at boot time if yes system will come up in ngswitch mode otherwise in legacy mode. Users need to reload system to change system switching mode if it is neccessary |
esg-io-infra |
LOG_STD_SH_TECH_ACTION |
|
IOMD-3-UNSUPPORTED_MODULE |
3-Error |
The module [chars] in slot [dec] bay [dec] is not supported on this platform |
The module inserted is not supported on this platform and will not be powered on |
esg-io-infra |
LOG_STD_SH_TECH_ACTION |
|
IOMD-3-UNSUPPORTED_MODULE_IN_NEBS |
3-Error |
The module [chars] in slot [dec] bay [dec] is not supported in NEBS mode |
The module inserted is not supported in NEBS mode and will not be powered on |
esg-io-infra |
LOG_STD_SH_TECH_ACTION |
|
IOMD-3-UNSUPPORTED_NGSWITCH |
3-Error |
The next-gen switch module [chars] in slot [dec] bay [dec] needs a system reload to take effect because current system is in legacy switching mode |
Legacy and next-gen switch modules have different feature set and cli behaviors which require system to determine corresponding switching mode at system boot time. Current selection algorithm is to check whether next-gen switch module locates within chassis at boot time if yes system come up in ngswitch mode otherwise in legacy mode. Users need to reload system to change system switching mode. |
esg-io-infra |
LOG_STD_SH_TECH_ACTION |
|
IOMD-6-TDLMSG_INCOMPATIBLE |
6-Information |
Failed to copy message [chars] to buffer not allowed for current domain. |
Failure to marshal a message indicates an incompatibility with the intended recipient. |
asr900-im |
LOG_STD_SH_TECH_ACTION |
|
IOS_LICENSE_IMAGE_APPLICATION-3-FAILED |
3-Error |
[chars] |
The ios licensing subsystem failed to create a process/watched boolean etc to watch request from the remote show subsys license commands |
ios-licensing |
"please capture the error msg and forward it to the appropriate licensing component" |
|
IOS_LICENSE_IMAGE_APPLICATION-3-FAILED |
3-Error |
[chars] |
The ios licensing subsystem failed to create a process/watched boolean etc to watch request from the remote show subsys license commands |
ios-licensing |
"please capture the error msg and forward it to the appropriate licensing component" |
|
IOS_LICENSE_IMAGE_APPLICATION-3-UNKNOWN_EVENT |
3-Error |
[chars] |
The ios image licensing subsystem received an event which it does not understand or recognizes |
ios-licensing |
"please capture the error msg and forward it to the appropriate licensing component" |
|
IOS_LICENSE_IMAGE_APPLICATION-3-UNKNOWN_EVENT |
3-Error |
[chars] |
The ios image licensing subsystem received an event which it does not understand or recognizes |
ios-licensing |
"please capture the error msg and forward it to the appropriate licensing component" |
|
IOS_LICENSE_IMAGE_APPLICATION-3-UNKNOWN_VERSION |
3-Error |
[chars] |
The ios image licensing subsystem received an event for an unknown version of a feature |
ios-licensing |
"please capture the error msg and forward it to the appropriate licensing component" |
|
IOS_LICENSE_IMAGE_APPLICATION-3-UNKNOWN_VERSION |
3-Error |
[chars] |
The ios image licensing subsystem received an event for an unknown version of a feature |
ios-licensing |
"please capture the error msg and forward it to the appropriate licensing component" |
|
IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_CONFIG |
6-Information |
EULA must be accepted for license level = [chars] |
This is an informational message to inform user that the user needs to reissue the command from an interactive terminal |
ios-licensing |
"This is an informational message no action is required" |
|
IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_CONFIG |
6-Information |
EULA must be accepted for license level = [chars] |
This is an informational message to inform user that the user needs to reissue the command from an interactive terminal |
ios-licensing |
"This is an informational message no action is required" |
|
IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL |
6-Information |
Module name = [chars] Next reboot level = [chars] and License = [chars] |
This is an informational message to display the change in the next reboot license level |
ios-licensing |
"This is an informational message no action is required" |
|
IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL |
6-Information |
Module name = [chars] Next reboot level = [chars] and License = [chars] |
This is an informational message to display the change in the next reboot license level |
ios-licensing |
"This is an informational message no action is required" |
|
IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL_CONFIG |
6-Information |
Please issue 'license boot' config command to make extension license [chars] available for use. |
This is an informational message to info user that to make extension license available to support image level licensing image level needs to be configured |
ios-licensing |
"This is an informational message no action is required" |
|
IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL_CONFIG |
6-Information |
Please issue 'license boot' config command to make extension license [chars] available for use. |
This is an informational message to info user that to make extension license available to support image level licensing image level needs to be configured |
ios-licensing |
"This is an informational message no action is required" |
|
IOS_LICENSE_IMAGE_APPLICATION-6-NO_LICENSE |
6-Information |
[chars] [chars]. |
There is no valid license available on the box and we are running on a default feature |
ios-licensing |
"please purchase a license to activate required features" |
|
IOS_LICENSE_IMAGE_APPLICATION-6-NO_LICENSE |
6-Information |
[chars] [chars]. |
There is no valid license available on the box and we are running on a default feature |
ios-licensing |
"please purchase a license to activate required features" |
|
IOS_LICENSE-2-NO_LICENSE |
2-Critical |
No valid license avaiable to run any feature |
The Ios licensing subsystem could not get a valid license to run any feature on the box please purchase a license. |
ios-licensing |
"Purchase a valid license to run the features you requier on the " "box. You should contact the cisco portal or a TAC engineer to get " "a license. You can do a <CmdBold>show license<noCmdBold> at the " "privileged command line prompt to get the list of availabe feature " "in the box " |
|
IOS_LICENSE-2-NO_LICENSE |
2-Critical |
No valid license avaiable to run any feature |
The Ios licensing subsystem could not get a valid license to run any feature on the box please purchase a license. |
ios-licensing |
"Purchase a valid license to run the features you requier on the " "box. You should contact the cisco portal or a TAC engineer to get " "a license. You can do a <CmdBold>show license<noCmdBold> at the " "privileged command line prompt to get the list of availabe feature " "in the box " |
|
IOS_LICENSE-2-NO_MEM |
2-Critical |
No memory available for [chars] |
The Ios licensing subsystem could not obtain the memory it needed. |
ios-licensing |
"If this error message recurs attempt to reduce memory usage by " "reducing the number of router features or interfaces enabled. " "Alternatively add more memory. " "\n\nTo display total memory usage for a router enter " "<CmdBold>show memory summary<noCmdBold> at the privileged " "command line prompt. To display buffer usage enter " "<CmdBold>show buffers<noCmdBold> at the prompt." |
|
IOS_LICENSE-2-NO_MEM |
2-Critical |
No memory available for [chars] |
The Ios licensing subsystem could not obtain the memory it needed. |
ios-licensing |
"If this error message recurs attempt to reduce memory usage by " "reducing the number of router features or interfaces enabled. " "Alternatively add more memory. " "\n\nTo display total memory usage for a router enter " "<CmdBold>show memory summary<noCmdBold> at the privileged " "command line prompt. To display buffer usage enter " "<CmdBold>show buffers<noCmdBold> at the prompt." |
|
IOS_LICENSE-3-FAILED |
3-Error |
[chars] |
The ios licensing subsystem failed to create a process/watched boolean etc to watch request from the remote show subsys license commands |
ios-licensing |
"please capture the error msg and forward it to the appropriate licensing component" |
|
IOS_LICENSE-3-FAILED |
3-Error |
[chars] |
The ios licensing subsystem failed to create a process/watched boolean etc to watch request from the remote show subsys license commands |
ios-licensing |
"please capture the error msg and forward it to the appropriate licensing component" |
|
IOS_LICENSE-3-IPC_FAILED |
3-Error |
[chars] failed with an error = [chars] |
The ipc calls in the Ios licensing subsystem failed for some reason please capture the error msg and forward it to the appropriate licensing component |
ios-licensing |
"please capture the error msg and forward it to the appropriate licensing component" |
|
IOS_LICENSE-3-IPC_FAILED |
3-Error |
[chars] failed with an error = [chars] |
The ipc calls in the Ios licensing subsystem failed for some reason please capture the error msg and forward it to the appropriate licensing component |
ios-licensing |
"please capture the error msg and forward it to the appropriate licensing component" |
|
IOS_LICENSE-3-RTTYS_FAILED |
3-Error |
[chars] failed |
The rttys calls in the Ios licensing subsystem failed for some reason please capture the error msg and forward it to the appropriate licensing component |
ios-licensing |
"please capture the error msg and forward it to the appropriate licensing component" |
|
IOS_LICENSE-3-RTTYS_FAILED |
3-Error |
[chars] failed |
The rttys calls in the Ios licensing subsystem failed for some reason please capture the error msg and forward it to the appropriate licensing component |
ios-licensing |
"please capture the error msg and forward it to the appropriate licensing component" |
|
IOS_LICENSE-3-UNKNOWN_MSG_TYPE |
3-Error |
an unknown message type was received dropping it msg_type = [dec] |
Ios licensing subsystem received a msg type which it does not recognizes or support |
ios-licensing |
"please capture the error msg and forward it to the appropriate licensing component" |
|
IOS_LICENSE-3-UNKNOWN_MSG_TYPE |
3-Error |
an unknown message type was received dropping it msg_type = [dec] |
Ios licensing subsystem received a msg type which it does not recognizes or support |
ios-licensing |
"please capture the error msg and forward it to the appropriate licensing component" |
|
IOSD_INFRA-3-IFS_DEVICE_DETECT_FAIL |
3-Error |
Device [chars] [chars] |
USB detection failed |
- |
"USB Insertion could not be handled completely." "Device needs to be removed and re-inserted" |
|
IOSD_INFRA-6-IFS_DEVICE_OIR |
6-Information |
Device [chars] [chars] |
USB inserted/removed |
- |
LOG_STD_NO_ACTION |
|
IOSXE_APS-3-CCCONFIGFAILED |
3-Error |
Pair config for interface [chars] Group [dec] failed |
Pair config for interface has failed |
iosxe-spa-pos |
LOG_STD_ACTION |
|
IOSXE_APS-3-CONFIG_FAIL |
3-Error |
config change for interface [chars] Group [dec] failed |
config for an interface to forwarding plane has failed |
iosxe-spa-pos |
LOG_STD_ACTION |
|
IOSXE_APS-3-DOWNLOADFAIL |
3-Error |
Unable to download [chars] message to [chars] |
An unexpected condition has occurred which resulted in a configuration \n\ not being sent to the reported process. |
iosxe-spa-pos |
LOG_STD_ACTION |
|
IOSXE_APS-3-FLOWCONFIGTOCCFAILED |
3-Error |
Flow id to cc for interface [chars] Group [dec] failed |
Flow id to cc for an interface has failed |
iosxe-spa-pos |
LOG_STD_ACTION |
|
IOSXE_APS-3-FLOWIDALLOCFAILED |
3-Error |
Allocation of APS flow ID with manager failed for interface [chars] group [dec] |
An unexpected condition has occurred that allocation of\n\ APS flow ID. failed |
iosxe-spa-pos |
"show interface" |
|
IOSXE_APS-3-FLOWIDDELETIONFAILED |
3-Error |
Deletion of APS flow ID with manager failed for interface [chars] group [dec] |
An unexpected condition has occurred that deletion of\n\ APS flow ID. |
iosxe-spa-pos |
"show interface" |
|
IOSXE_APS-3-GROUP_CONFIG_FAIL |
3-Error |
Group change for interface [chars] Group [dec] failed |
Group change for interface has failed |
iosxe-spa-pos |
LOG_STD_ACTION |
|
IOSXE_APS-3-PAIR_CONFIG_FAIL |
3-Error |
Pair config for interface [chars] Group [dec] failed |
Pair config for interface has failed |
iosxe-spa-pos |
LOG_STD_ACTION |
|
IOSXE_AUTHENTICATE-2-AUTHENTICATE_FAILED |
2-Critical |
The platform authentication failed |
WDC authentication failed |
iosxe-csl |
"Check if WDC is programmed on this device" |
|
IOSXE_CIDB-3-ALLOC |
3-Error |
Failed to allocate message for CIDB message |
When attempting to program the dataplane with a CIDB object there was not enough memory to allocate the message. |
iosxe-cidb |
LOG_STD_ACTION |
|
IOSXE_CIDB-3-MESSAGE |
3-Error |
Failed to send message for CIDB object |
When the cidb object was being prepared to be sent to the data plane there was an error. |
iosxe-cidb |
LOG_STD_ACTION |
|
IOSXE_CRYPTOBW-3-CONF_FAILED |
3-Error |
Configuration failed |
An error occurred when the crypto throughput configuration was attempted. |
iosxe-csl |
- |
|
IOSXE_CRYPTOBW-3-EULA_NOT_ACCEPTED |
3-Error |
The EULA has to be accepted prior to crypto throughput configuration. |
Users need to accept EULA to activate the license |
iosxe-csl |
"Accept EULA for crypto throughput license" |
|
IOSXE_CRYPTOBW-3-INVALID_CONFIG |
3-Error |
No valid license found for the configured crypto throughput level: [chars] kbps |
The boot up crypto throughput has been set to non-default level without having the valid license. |
iosxe-csl |
"Install valid crypto throughput license" |
|
IOSXE_CRYPTOBW-6-LEVEL |
6-Information |
Crypto Throughput level has been set to [chars] bps |
Crypto Throughput level has been set to a number |
iosxe-csl |
- |
|
IOSXE_CRYPTOBW-6-RESET |
6-Information |
Crypto Throughput level has been reset to default [chars] bps |
Crypto Throughput level has been reset |
iosxe-csl |
- |
|
IOSXE_CSLIFS-3-ERROR_SETTING |
3-Error |
Error setting default file system [dec] |
There is an error happened after calling function ifs_set_default_directory |
iosxe-csl |
"Check the csl filesystem" |
|
IOSXE_CSLIFS-3-ERROR_SETTING |
3-Error |
Error setting default file system [dec] |
There is an error happened after calling function ifs_set_default_directory |
iosxe-csl |
"Check the csl filesystem" |
|
IOSXE_CXSC-3-ACTION |
3-Error |
Unknown proposition action [dec] |
- |
- |
- |
|
IOSXE_CXSC-3-ALLOC |
3-Error |
Failed to allocate message for proposition |
When attempting to program the dataplane with a CXSC proposition object there was no enough memory to allocate the message. |
iosxe-cxsc |
LOG_STD_ACTION |
|
IOSXE_CXSC-3-BAD_PROPOSITION |
3-Error |
Proposition obj corrupt |
When the proposition was being sent to the data plane the object itself is corrupt. |
iosxe-cxsc |
LOG_STD_ACTION |
|
IOSXE_CXSC-3-BAD_PROTOCOLPACK |
3-Error |
Invalid Protocol Pack object |
When the Protocol Pack was being sent to the data plane the object's contents were invalid. |
iosxe-cxsc |
LOG_STD_ACTION |
|
IOSXE_CXSC-3-BAD_SUMMARY |
3-Error |
Summary obj corrupt |
When the proposition summary was being sent to the data plane the object itself is corrupt. |
iosxe-cxsc |
LOG_STD_ACTION |
|
IOSXE_CXSC-3-FILESYSTEM_ERR |
3-Error |
FileSystem Error [chars]: Unable to Copy File from |
Unable to copy the NBAR Protocol Pack File to the file system for subsequent loading. The system will revert to the previously loaded Protocol Pack. |
iosxe-cxsc |
LOG_STD_ACTION |
|
IOSXE_CXSC-3-INSUFFICIENT_ALLOC_IOSXE_VER |
3-Error |
Insufficent memory allocated for IOSXE version String |
The input IOSXE Version String has insufficient memory to hold the IOSXE Version. |
iosxe-cxsc |
LOG_STD_ACTION |
|
IOSXE_CXSC-3-INSUFFICIENT_ALLOC_NBAR_VER |
3-Error |
Insufficent memory allocated for NBAR Engine Version String |
The input NBAR Engine Version string has insufficient memory to hold the NBAR Engine Version. |
iosxe-cxsc |
LOG_STD_ACTION |
|
IOSXE_CXSC-3-MESSAGE |
3-Error |
Failed to send message for proposition |
When the proposition was being prepared for sending to the data plane there was an error. |
iosxe-cxsc |
LOG_STD_ACTION |
|
IOSXE_CXSC-3-PLATFORM_TYPE |
3-Error |
Unrecognised platform type. CPU ID [dec] |
The platform that the cxsc service is being installed on is not recognised. The most likely cause is that this platform is not supported. |
iosxe-cxsc |
LOG_STD_ACTION |
|
IOSXE_CXSC-3-RF_INIT |
3-Error |
Failed to initialize CXSC Redundancy Facility client |
An unexpected condition occurred where the CXSC Redundancy Facility failed to initialize. |
iosxe-cxsc |
LOG_STD_ACTION |
|
IOSXE_CXSC-3-STATISTICS_ALLOCATION |
3-Error |
Unable to allocate space for statistics |
During initialization there was failure in the allocation of the memory to gather the statistics. It is non fatal but after seeing this message the CXSC subsystem will not be able to gather statistics. |
iosxe-cxsc |
LOG_STD_ACTION |
|
IOSXE_CXSC-3-STILE_ACTIVATE |
3-Error |
Failed to activate NBAR classification: [dec] |
An unexpected condition occurred where the CXSC NBAR protocol classification failed to activate. |
iosxe-cxsc |
LOG_STD_ACTION |
|
IOSXE_CXSC-4-DUAL_RP_UNSUPPORTED |
4-Warning |
Dual RPs are not supported in conjunction with CXSC |
CXSC is not supported in a dual RP environment. To resolve this warning either unconfigure CXSC or remove the redundant Route Processor. |
iosxe-cxsc |
LOG_STD_ACTION |
|
IOSXE_DNS-3-UPDATE_FAILED |
3-Error |
Update resolv.conf vrf [chars] rc [dec] |
An unexpected condition has occurred while updating the DNS file |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_DNS-3-VRF_FAILED |
3-Error |
Operation [chars] on /etc/netns/[chars] rc [dec] |
An unexpected condition has occurred while updating the DNS directory |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_DSP-3-ENQUEFAIL |
3-Error |
Enqueue of TDL message failed [chars]. |
- |
- |
- |
|
IOSXE_EPA-3-ACT2_AUTHENTICATION_FAILURE |
3-Error |
slot=[dec] subslot=[dec] spa_type=0x[hec] lc_type=0x[hec]. |
ACT2 dev authentication Failed. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_EPA-3-AUTONEG_CFG_ERR |
3-Error |
interface [chars] autoneg state '[chars]' is incompatible with transciever. Remove \'[chars]\' to allow the transceiver. |
Autoneg Config is not compatible. Remove autoneg config on the interface to allow the transceiver |
DDTS_COMPONENT |
"Remove the negotiation auto config or " "reinsert the previously enabled transceiver." |
|
IOSXE_EPA-3-CARD_PORT_NUM_FAILURE |
3-Error |
Failure in getting card port number from spa port [dec] for EPA in [dec]/[dec] |
Failed to get card port number from spa port number |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_EPA-3-CREATION_FAILURE |
3-Error |
slot=[dec] subslot=[dec] spa_type=0x[hec] lc_type=0x[hec]. |
Failed to create a SPA object. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_EPA-3-EPA_PROHIBIT |
3-Error |
Insertion of [chars] not allowed in [dec]/[dec] post-boot |
The SPA in the specified subslot cannot be inserted once the system boots up in controller mode |
- |
LOG_STD_NO_ACTION |
|
IOSXE_EPA-3-MAC_FAULT |
3-Error |
MAC link on [chars] is down due to [chars] |
MAC fault reason local/remote fault |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_EPA-3-NULL_ALS_PTR |
3-Error |
- |
Pointer to a als object is NULL. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_EPA-3-NULL_DEVOBJ_PTR |
3-Error |
- |
Pointer to a DEVOBJ object is NULL. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_EPA-3-NULL_DEVPSEQ_PTR |
3-Error |
- |
Pointer to a DEVPSEQ object is NULL. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_EPA-3-NULL_DS_PTR |
3-Error |
- |
Pointer to a ether instanace is NULL. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_EPA-3-NULL_EPA_MODE_SB_PTR |
3-Error |
- |
Pointer to an EPA mode subblock is NULL. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_EPA-3-NULL_EPA_PORT_CFG_PTR |
3-Error |
- |
Pointer to an epa port cfg is NULL. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_EPA-3-NULL_EPA_PTR |
3-Error |
- |
Pointer to an EPA object is NULL. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_EPA-3-NULL_EPASENSOR_PTR |
3-Error |
- |
Pointer to a DEVSENSOR object is NULL. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_EPA-3-NULL_FPGA_PTR |
3-Error |
- |
Pointer to a FPGA object is NULL. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_EPA-3-NULL_HWIDB_PTR |
3-Error |
- |
Pointer to a HWIDB object is NULL. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_EPA-3-NULL_PORT_PTR |
3-Error |
- |
Pointer to a PORT object is NULL. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_EPA-3-NULL_VFT |
3-Error |
- |
Pointer to a DEVSENSOR object is NULL. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_EPA-3-NULL_VSC_PHY_INFO_PTR |
3-Error |
- |
Pointer to a VSC PHY INFO object is NULL. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_EPA-3-SPA_PORT_NUM_FAILURE |
3-Error |
Failure in getting spa port number from card port [dec] for EPA in [dec]/[dec] |
Failed to get spa port number from card port number |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_EPA-3-UNSUPPORTED_XCVR |
3-Error |
Transceiver type [chars] is not allowed on spa [chars] port [dec] |
This transceiver is not allowed on the SPA |
DDTS_COMPONENT |
"Consult the documentation and ensure supported " "transceivers are plugged into the SPA" |
|
IOSXE_EPA-3-XCVR_EC_BWMISMATCH |
3-Error |
Trasnsceiver bandwidth is incompatible with Port-channel[dec] allowed bandwidth. Remove \'channel-group [dec]\' config for interface [chars] to allow the transceiver |
The interface port into which the transceiver is inserted is part of a Port-channel. The Port-channel has member links whose bandwidth doesn't match with the inserted transceier's bandwidth. Since port-channel cannot allow heterogenous bandwidth links this transceiver is not allowed in to the port. |
DDTS_COMPONENT |
"Remove the channel-group config for the port where " "transceiver is inserted or insert a transceiver " "whose bandwidth is compatible with the port-channel " "bandwidth" |
|
IOSXE_EPA-3-XCVR_PROHIBIT |
3-Error |
Transceiver is prohibited to come online for interface [chars] |
XCVR is prohibited on the interface |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_ETHERCHAN-3-LINK_MTU_FAIL |
3-Error |
Failure in changing MTU of interface [chars] to port-channel [chars] MTU |
The MTU for the interface mentioned in the message cannot be changed to match the MTU configured on the port channel interface |
iosxe-fwdmgr |
"Remove the link mentioned in the message from " "the port-channel group" |
|
IOSXE_ETHERCHAN-6-LINK_MTU |
6-Information |
Interface [chars] MTU set to port-channel [chars] MTU [dec] |
The MTU for the interface mentioned in the message is changed to match the MTU configured on the port channel interface |
- |
LOG_STD_NO_ACTION |
|
IOSXE_EWLC_LICENSE-2-MSGDEVICENOTREG |
2-Critical |
Unregistered 9800-CL can only be used in lab. For production usage please register this device in [dec] days. Failure to do so will result in a limited number [dec] of Access Points being allowed post this. |
Device is required to be registered with license manager within the licensing period. |
ewlc-licensing |
LOG_STD_ACTION |
|
IOSXE_EZMENU-3-VIRT_SRVC_REGISTER |
3-Error |
Failed to register '[chars]' with virtual service manager |
An unexpected error has occured while trying to register this virtual service with the virtual service manager. This has prevented the virtual service from being enabled/disabled. |
vman |
LOG_STD_ACTION |
|
IOSXE_FMANRP_ADJ-3-ENCSIZE |
3-Error |
Invalid encap length [dec] which is larger than max allowed [dec] bytes |
An unexpected condition has occurred which is due to invalid\n\ adjacency encapsulation size being larger than the maximum value\n\ allowed. |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP_ADJ-3-ENQUEFAIL |
3-Error |
Unable to send [chars] [chars] message to Forwarding Manager Process |
An unexpected condition has occurred which resulted in a configuration \n\ not being sent to the Forwarding Manager Processs. |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP_ADJ-3-NOADJ |
3-Error |
Adjacency entry is null |
An unexpected condition has occurred which is due to the absence of\n\ an adjacency entry structure. |
iosxe-fwdmgr |
"show adjacency" |
|
IOSXE_FMANRP_ADJ-3-NOFIBHWIDB |
3-Error |
FIB Interface [chars] is null |
An unexpected condition has occurred which is due to the absence of\n\ a FIB interface structure. |
iosxe-fwdmgr |
"show adj" |
|
IOSXE_FMANRP_CCE-3-CCE_CLASS_CREATE |
3-Error |
Unable to create class [dec].[dec] |
An error occured when trying to create a class-map. |
iosxe-fwdmgr |
"show policy-map\n\ [type <policy type> <name>]" |
|
IOSXE_FMANRP_CCE-3-CCE_FILTER_OVERFLOW |
3-Error |
Filter list overflow at type [chars] |
An internal error occured when trying to build class-map information for one of the classes in a policy-map. |
iosxe-fwdmgr |
"show class-map \n\ [type <class type> <name>]" |
|
IOSXE_FMANRP_CCE-3-CCE_INVALID_FILTER_RELN |
3-Error |
Invalid filter relation [dec] |
An internal error occured when trying to build class-map information for one of the classes in a policy-map. |
iosxe-fwdmgr |
"show policy-map \n\ [type <policy type> <name>]" |
|
IOSXE_FMANRP_CCE-4-CCE_NESTED_CLASS_LIMIT |
4-Warning |
Nested class [dec] layers cannot exceed 4 |
When configure nested classes as match statements \n\ the total levels of nested classes cannot exceed 4 layers |
iosxe-fwdmgr |
"show class-map [type\n\ <class type> <name>]" |
|
IOSXE_FMANRP_CCE-4-CCE_STACK_LIMIT |
4-Warning |
Failed to create class [dec] filter list |
An operation to send a filter list to the forwarding \n\ processor for a particular class has failed due to a \n\ resource issue. This may imply that the notification was\n\ dropped. |
iosxe-fwdmgr |
"show class-map [type\n\ <class type> <name>]" |
|
IOSXE_FMANRP_CCK-4-FMANRP_INCONSISTENT |
4-Warning |
Consistency Check for [chars] cannot be completed for all entries. Check 'show consistency-checker run-id [dec] detail'. |
Unexpected counts of updates happened during the CCK Run. |
iosxe-fwdmgr |
"show consistency-checker run-id " |
|
IOSXE_FMANRP_CCK-6-FMANRP_COMPLETED |
6-Information |
Consistency Check for Run-Id [dec] is completed. Check 'show consistency-checker run-id [dec]'. |
Informational syslog indicating that consistency check has completed. |
iosxe-fwdmgr |
"show consistency-checker run-id " |
|
IOSXE_FMANRP_CEF-3-ENQUEFAIL |
3-Error |
Unable to send [chars] [chars] message to Forwarding Manager Process |
An unexpected condition has occurred which resulted in a configuration \n\ not being sent to the Forwarding Manager Processs. |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP_CEF-3-NOFIB |
3-Error |
FIB entry is null |
An unexpected condition has occurred which is due to the absence of\n\ a FIB entry structure. |
iosxe-fwdmgr |
"show ip cef" |
|
IOSXE_FMANRP_CEF-3-NOFIBIDB |
3-Error |
FIB interface is null |
An unexpected condition has occurred which is due to the absence of\n\ a FIB interface structure. |
iosxe-fwdmgr |
"show ip cef" |
|
IOSXE_FMANRP_CEF-3-NOFIBPUSHCNT |
3-Error |
FIB push counter is null |
An unexpected condition has occurred which is due to the absence of\n\ a FIB push counter structure. |
iosxe-fwdmgr |
"show ip cef" |
|
IOSXE_FMANRP_CEF-3-NOFIBSB |
3-Error |
FIB SB entry is null |
An unexpected condition has occurred which is due to the absence of\n\ a FIB SB entry structure. |
iosxe-fwdmgr |
"show ip cef" |
|
IOSXE_FMANRP_CEF-3-NOFIBSIGNAL |
3-Error |
FIB signal is null |
An unexpected condition has occurred which is due to the absence of\n\ a FIB signal structure. |
iosxe-fwdmgr |
"show ip cef" |
|
IOSXE_FMANRP_CEF-3-NOFIBTABLE |
3-Error |
FIB table is null |
An unexpected condition has occurred which is due to the absence of\n\ a FIB table structure. |
iosxe-fwdmgr |
"show ip cef" |
|
IOSXE_FMANRP_CEF-3-NONATADDR |
3-Error |
NAT address is null |
An unexpected condition has occurred which is due to the absence of\n\ an NAT address. |
iosxe-fwdmgr |
"show ip alias" |
|
IOSXE_FMANRP_CEF-3-ROUTEMSGMARSHAL |
3-Error |
Failed to copy route essage to IPC buffer for prefix [chars]/[dec] - [chars] |
This operation to build a TDL messages for route download has failed. |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP_CEF-4-UPDFRAGSTATSERR |
4-Warning |
Update IP Fragmentation statistics error |
An unexpected condition has occurred when updating fragmentation \n\ statistics |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP_CEF-4-UPDREASSSTATSERR |
4-Warning |
Update IP Reassembly statistics error |
An unexpected condition has occurred when updating reassembly \n\ statistics |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP_CEF-4-UPDSTATSERR |
4-Warning |
Update CEF statistics error |
An unexpected condition has occurred when updating cef statistics |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP_EFP-3-EFP_ACCOUNTING_ERROR |
3-Error |
[chars] FMAN EFP support has encounterd an EFP accounting error on [chars]: [chars] |
An inavlid EFP count found during EFP accouting in IOSXE FMAN EFP support. |
asr1k-evc |
show ethernet service instance detail |
|
IOSXE_FMANRP_EFP-3-EFP_AVL_DELETE |
3-Error |
Failed to delete EFP node with id [dec] in [chars] |
An unexpected condition during configuration change |
asr1k-evc |
LOG_STD_ACTION |
|
IOSXE_FMANRP_EFP-3-EFP_CFM_ERROR |
3-Error |
IOSXE FMAN EFP has encounterd an unsupported encap for CFM. Please remove any CFM configuration befor applying this encap. |
The encapuslation type is not supported for CFM on IOSXE. |
asr1k-ecfm |
"Remove any CFM config and reapply encapusation" |
|
IOSXE_FMANRP_EFP-3-INVALID_VALUE |
3-Error |
Configuration specified invalid value [dec] for [chars] |
An unexpected condition in which configuration has accepted an invalid value. |
asr1k-evc |
LOG_STD_ACTION |
|
IOSXE_FMANRP_EOAM-3-IOSXE_FMANRP_EOAM_CONFIG |
3-Error |
MIP Filtering enable/disable will take into affect only if it is applied before applying any cfm config. |
MIP filtering enable/disable should be applied before applying cfm config. Otherwise the command will have no affect on CFM Filtering. |
asr1k-ecfm |
"show platform software eoam fp active cfm global" |
|
IOSXE_FMANRP_ETHER_DPLB-3-INVALIDIF |
3-Error |
Configuration specified invalid value [dec] for [chars] |
An non-existent interface is specified for ETHER_DPLB operation. |
iosxe-ether-dplb |
"show interface" |
|
IOSXE_FMANRP_ETHER_DPLB-3-IOSXE_FMANRP_ETHER_DPLB_STATS |
3-Error |
Invalid stats update. type [dec] id [dec] |
An invalid stats update is received by ETHER_DPLB. |
iosxe-ether-dplb |
"show platform software ether_dplb" |
|
IOSXE_FMANRP_FPM-3-NOSTATUPDATE |
3-Error |
Failed to update class-map statistics during periodic update |
A statistics update for a class-map has failed. |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP_FPM-4-INVALIDACTION |
4-Warning |
FPM feature action is invalid [dec] |
An unexpected condition has occurred which is due to the invalid\n\ action type when trying to bind FPM action with target class group. |
iosxe-fwdmgr |
LOG_STD_SH_CMD_ACTION |
|
IOSXE_FMANRP_FPM-4-INVALIDLENTYPE |
4-Warning |
Field length type in PHDF file is invalid |
An unexpected condition has occurred which is due to the invalid\n\ field length type in PHDF file. |
iosxe-fwdmgr |
LOG_STD_SH_CMD_ACTION |
|
IOSXE_FMANRP_FPM-4-INVALIDMATCHTYPE |
4-Warning |
FPM match type is invalid [dec] |
An unexpected condition has occurred which is due to the invalid\n\ FPM match type in one of FPM class-map filter match entry |
iosxe-fwdmgr |
LOG_STD_SH_CMD_ACTION |
|
IOSXE_FMANRP_IPHC-4-INVALIDSTATSTYPE |
4-Warning |
IP header compression statistic message received has invalid stats type |
When receiving an IP header compression statistic update for an \n\ interface or sub-interface in IOS the statistic type in that \n\ message is invalid. |
iosxe-fwdmgr |
LOG_STD_SH_CMD_ACTION |
|
IOSXE_FMANRP_IPHC-4-NOIDB |
4-Warning |
IOS interface [chars] is not available for an IP header compression |
When receiving an IP header compression statistic update for an \n\ interface or sub-interface in IOS one of data structures in IOS\n\ to store those IP header compression statistics is NULL |
iosxe-fwdmgr |
LOG_STD_SH_CMD_ACTION |
|
IOSXE_FMANRP_IPHC-4-STATSERR |
4-Warning |
There is error when processing IP header compression statistic message received on IOS |
When receiving an IP header compression statistic update for an \n\ interface or sub-interface in IOS an unexpected error occurred |
iosxe-fwdmgr |
LOG_STD_SH_CMD_ACTION |
|
IOSXE_FMANRP_L2FIB-3-INVALIDIF |
3-Error |
Configuration specified invalid value [dec] for [chars] |
An non-existent interface is specified for L2FIB operation. |
iosxe-l2fib |
"show interface" |
|
IOSXE_FMANRP_L2FIB-3-IOSXE_FMANRP_L2FIB_STATS |
3-Error |
Invalid stats update. type [dec] id [dec] |
An invalid stats update is received by L2FIB. |
iosxe-l2fib |
"show platform software l2fib" |
|
IOSXE_FMANRP_LISP_SFLTR-3-UPDENTRYSTATSERR |
3-Error |
Update LISP-SFLTR Entry statistics error |
An unexpected condition has occurred when updating lisp-sfltr entry statistics |
asr1k-lisp |
LOG_STD_ACTION |
|
IOSXE_FMANRP_LISP_SFLTR-3-UPDTABLESTATSERR |
3-Error |
Update LISP-SFLTR Table statistics error |
An unexpected condition has occurred when updating lisp-sfltr table statistics |
asr1k-lisp |
LOG_STD_ACTION |
|
IOSXE_FMANRP_MACSEC-3-INVALIDIF |
3-Error |
Configuration specified invalid value [dec] for [chars] |
An non-existent interface is specified for MACSEC operation. |
iosxe-macsec |
"show interface" |
|
IOSXE_FMANRP_MACSEC-3-IOSXE_FMANRP_MACSEC_STATS |
3-Error |
Invalid stats update. type [dec] id [dec] |
An invalid stats update is received by MACSEC. |
iosxe-macsec |
"show platform software macsec" |
|
IOSXE_FMANRP_MCAST-3-FMANRP_BADMAF |
3-Error |
Unknown Multicast AF [dec] |
An unexpected condition has occurred due to the download\n\ of an unknown MFIB address family code. |
iosxe-fwdmgr |
"show mfib" |
|
IOSXE_FMANRP_MCAST-3-FMANRP_DELID |
3-Error |
Failed to remove Multicast ID [dec] |
An unexpected condition has occurred due to the failure\n\ to delete an internal identifier that is no longer in use. |
iosxe-fwdmgr |
"show mfib" |
|
IOSXE_FMANRP_MCAST-3-FMANRP_MCAP |
3-Error |
Multicast Capability [chars]:[chars] error [chars] |
An unexpected condition has occurred due to the failure to set\n\ a multicast capability for this platform. |
iosxe-fwdmgr |
"show mfib state cap" |
|
IOSXE_FMANRP_MCAST-3-FMANRP_MSTATS |
3-Error |
Can't process multicast stats upload from fman. type [dec] id [dec] |
An unexpected condition has occurred preventing interpretation\n\ of the stats message from the forwarding manager. This will\n\ prevent the statistics for the affected multicast entries from\n\ being updated. |
iosxe-fwdmgr |
"show ip mroute count" |
|
IOSXE_FMANRP_MCAST-3-FMANRP_NOID |
3-Error |
No Multicast ID for [inet] [inet]/[dec] action [inet] |
- |
iosxe-fwdmgr |
"show ip mroute count" |
|
IOSXE_FMANRP_MCAST-3-FMANRP_UPDINTF |
3-Error |
Failed to update flag count for [chars] due to [chars] |
An unexpected condition has occurred due to the failure\n\ to update the interface flag count |
iosxe-fwdmgr |
"show mfib" |
|
IOSXE_FMANRP_MCAST-3-MCASTID |
3-Error |
Multicast ID management error |
An unexpected condition has occurred causing an internal\n\ ID to not be properly handled or disposed of |
iosxe-fwdmgr |
"show ip mroute count" |
|
IOSXE_FMANRP_OBJID2-3-DUPCREATE |
3-Error |
Duplicate forwarding object creation obj_handle 0x[hec] type [dec] existing obj_id 0x[hec] type [dec] |
An unexpected condition has occurred which results in duplicate\n\ forwarding object creation with different object types. |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP_OBJID-5-DUPCREATE |
5-Notice |
Duplicate forwarding object creation obj_handle 0x[hec] type [dec] existing obj_id 0x[hec] type [dec] |
An unexpected condition has occurred which results in duplicate\n\ forwarding object creation. |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP_RTMAP-3-INVALID_LIST |
3-Error |
NULL |
An internal list structure has been detected as invalid. |
iosxe-pbr |
LOG_STD_SH_CMD_ACTION |
|
IOSXE_FMANRP_RTMAP-3-RTMAP_UNSUPPORTED |
3-Error |
Routemap [chars] contain unsupported match/set clause ignored |
- |
- |
- |
|
IOSXE_FMANRP_RTMAP-3-RTMAPNULL |
3-Error |
The route-map structure for [chars] is null |
An unexpected condition has occurred which is due to the absence of\n\ a route-map data structure. |
iosxe-fwdmgr |
"show route-map" |
|
IOSXE_FMANRP_RTMAP-4-UNKOWNCLIANT |
4-Warning |
Unknown client type [dec] received |
An unexpected known client type is received for route-map download. |
iosxe-fwdmgr |
LOG_STD_SH_CMD_ACTION |
|
IOSXE_FMANRP_URPF-3-INVALIDIFHDL |
3-Error |
Invalid interface handle [dec] for interface number= [dec] swidb= [hex] name= [chars] |
An unexpected condition has occurred which is due to an invalid \n\ interface handle |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP_URPF-4-NOV4SWIDB |
4-Warning |
v4 sub-interface is null |
An unexpected condition has occurred which is due to the absence of\n\ a v4 swidb structure. |
iosxe-fwdmgr |
"show ip interface" |
|
IOSXE_FMANRP_URPF-4-NOV6SWIDB |
4-Warning |
v6 sub-interface is null |
An unexpected condition has occurred which is due to the absence of\n\ a v6 swidb structure. |
iosxe-fwdmgr |
"show ipv6 interface" |
|
IOSXE_FMANRP_URPF-4-UPDV4STATSERR |
4-Warning |
Update v4 URPF statistics error |
An unexpected condition has occurred when updating v4 URPF statistics |
iosxe-fwdmgr |
"show ip interface <name>" |
|
IOSXE_FMANRP_URPF-4-UPDV6STATSERR |
4-Warning |
Update v6 URPF statistics error |
An unexpected condition has occurred when updating v6 URPF statistics |
iosxe-fwdmgr |
"show ipv6 interface <name>" |
|
IOSXE_FMANRP_VPLS-3-INVALID_VALUE |
3-Error |
Invalid value for [chars] |
An unexpected condition in which an invalid value is get during VPLS configuration. |
iosxe-vpls |
LOG_STD_ACTION |
|
IOSXE_FMANRP_ZONES-3-NOSTATUPDATE |
3-Error |
Failed to update zone-pair statistics during periodic update \n\ zone [chars] class [dec] |
A statistics update for a zone-pair has failed. |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP-3-EPOCHTDLMSGMARSHAL |
3-Error |
Failed to copy epoch TDL message to IPC buffer epoch number [dec] |
This operation to build a TDL messages for epoch message has failed. |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP-3-EPOCHTDLMSGMARSHAL |
3-Error |
Failed to copy epoch TDL message to IPC buffer epoch number [dec] |
This operation to build a TDL messages for epoch message has failed. |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP-3-MSGENQERR |
3-Error |
Unable to enqueue IPC messages to IOS IPC queue. Message: [chars]. |
An unexpected condition has occurred while IOS trying to enqueue \n\ IPC message to IOS IPC queue in order to send the message to\n\ Forwarding Manager. |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP-3-MSGENQERR |
3-Error |
Unable to enqueue IPC messages to IOS IPC queue. Message: [chars]. |
An unexpected condition has occurred while IOS trying to enqueue \n\ IPC message to IOS IPC queue in order to send the message to\n\ Forwarding Manager. |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP-3-MSGMARSHALERR |
3-Error |
Unable to copy IPC messages into transport buffer. Message: [chars] |
An unexpected condition has occurred while IOS trying to copy \n\ IPC message to transport buffer in order to send the message\n\ from IOSd to Forwarding Manager. |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP-3-MSGMARSHALERR |
3-Error |
Unable to copy IPC messages into transport buffer. Message: [chars] |
An unexpected condition has occurred while IOS trying to copy \n\ IPC message to transport buffer in order to send the message\n\ from IOSd to Forwarding Manager. |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP-4-MSGDISPATCH |
4-Warning |
Unable to dispatch received TDL message '[chars]' from Forwarding Manager. LUID: [chars] |
An unexpected condition has occurred while IOS trying to dispatch\n\ the TDL message handler functions for received TDL messages from \n\ Forwarding Manager. |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP-4-MSGDISPATCH |
4-Warning |
Unable to dispatch received TDL message '[chars]' from Forwarding Manager. LUID: [chars] |
An unexpected condition has occurred while IOS trying to dispatch\n\ the TDL message handler functions for received TDL messages from \n\ Forwarding Manager. |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP-4-MSGDISPATCHNULL |
4-Warning |
TDL messages NULL from IOS. |
An unexpected condition has occurred while IOS trying to dispatch\n\ the TDL message handler functions for received TDL messages from \n\ Forwarding Manager. |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP-4-MSGDISPATCHNULL |
4-Warning |
TDL messages NULL from IOS. |
An unexpected condition has occurred while IOS trying to dispatch\n\ the TDL message handler functions for received TDL messages from \n\ Forwarding Manager. |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP-4-MSGIPCERR |
4-Warning |
Unable to process received IPC messages from Forwarding Manager\n\ error: [chars]. |
An unexpected condition has occurred while IOS trying to process\n\ received IPC message from Forwarding Manager. |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP-4-MSGIPCERR |
4-Warning |
Unable to process received IPC messages from Forwarding Manager\n\ error: [chars]. |
An unexpected condition has occurred while IOS trying to process\n\ received IPC message from Forwarding Manager. |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_FMANRP-4-MSGNONTDLSTATSERR |
4-Warning |
Unable to process received non-TDL stats message from \ Forwarding Manager\n\ error: [chars] [dec]. |
- |
- |
- |
|
IOSXE_FMANRP-4-MSGNONTDLSTATSERR |
4-Warning |
Unable to process received non-TDL stats message from \ Forwarding Manager\n\ error: [chars] [dec]. |
- |
- |
- |
|
IOSXE_IMCC_CAPI-2-CRASHDUMP |
2-Critical |
Fatal error calling crashdump error: [dec] [chars] |
A fatal condition has occurred causing IOS to crashdump. |
iosxe-intfmgr |
LOG_STD_ACTION |
|
IOSXE_IMCC_CAPI-3-MSGDISPATCH |
3-Error |
Unable to dispatch received TDL message name = [chars] from |
An unexpected condition has occurred while IOS is trying to dispatch\n\ to the TDL message handler functions for received TDL messages from \n\ Interface Manager. |
iosxe-intfmgr |
LOG_STD_ACTION |
|
IOSXE_IMCC_CAPI-3-MSGDISPATCHNULL |
3-Error |
Received NULL TDL message from IOS |
An unexpected condition in which IOSD has received a NULL TDL \n\ message from Interface Manager. |
iosxe-intfmgr |
LOG_STD_ACTION |
|
IOSXE_IMCC_CAPI-3-MSGIPCERR |
3-Error |
Unable to process received IPC messages from Interface Manager\n\ error: [chars] |
An unexpected condition has occurred while IOS trying to process a\n\ received IPC message from Interface Manager. |
iosxe-intfmgr |
LOG_STD_ACTION |
|
IOSXE_IMCC_CAPI-6-CMSTATUS |
6-Information |
Interface Manager Process is [chars] |
The current status of Interface Manager Process. |
- |
LOG_STD_NO_ACTION |
|
IOSXE_IMSP_ADJ-3-ENCSIZE |
3-Error |
Invalid encap length [dec] which is larger than max allowed [dec] bytes |
An unexpected condition has occurred which is due to invalid\n\ adjacency encapsulation size being larger than the maximum value\n\ allowed. |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_IMSP_ADJ-3-ENQUEFAIL |
3-Error |
Unable to send [chars] [chars] message to Forwarding Manager Process |
An unexpected condition has occurred which resulted in a configuration \n\ not being sent to the Forwarding Manager Processs. |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_IMSP_ADJ-3-NOADJ |
3-Error |
Adjacency entry is null |
An unexpected condition has occurred which is due to the absence of\n\ an adjacency entry structure. |
iosxe-fwdmgr |
"show adjacency" |
|
IOSXE_IMSP_ADJ-3-NOFIBHWIDB |
3-Error |
FIB Interface [chars] is null |
An unexpected condition has occurred which is due to the absence of\n\ a FIB interface structure. |
iosxe-fwdmgr |
"show adj" |
|
IOSXE_INFRA-2-FATAL_NO_PUNT_KEEPALIVE |
2-Critical |
Keepalive not received for [dec] seconds resetting |
Punt Inject keepalive message was not received |
mcp-infrastructure |
LOG_STD_ACTION |
|
IOSXE_INFRA-2-FATAL_PUNT_LINK_DOWN |
2-Critical |
Punt Inject link went down resetting |
Punt Inject link went down |
mcp-infrastructure |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-APP_SESS_OPEN_FAILED |
3-Error |
An attempt to open [chars] with handle number [dec] has failed [dec] |
Application session between processes failed to estabish. |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-BAD_GLIBC_BUF_FREE |
3-Error |
An IOS buffer is freed into GLIBC buffer pool buffer blockmagic 0x[hec] flags 0x[hec] |
An IOS buffer is freed into GLIBC buffer pool. |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-BIPC_MGS_ALLOC_FAIL |
3-Error |
Allocating [dec] byte for IPC [chars] msg failed: out of memory |
system is out of memory |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-BSO_MSG_CACHE_ERR |
3-Error |
BSO message query cache update error - [chars] |
BSO message query cache update error |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-BSO_MSG_HDR_LENGTH_ERR |
3-Error |
BSO message header length [dec] is incorrect |
BSO message header length is incorrect |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-BSO_MSG_HDR_MSGTYPE_ERR |
3-Error |
BSO message header msgtype [dec] is incorrect |
BSO message header msgtype is incorrect |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-BSO_MSG_UNMARSHAL_ERR |
3-Error |
BSO message unmarshalling has failed |
BSO message unmarshalling has failed |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-CONSOLE_DBUG_DROP |
3-Error |
System dropped [dec] bytes of console debug messages.\n |
Debugging messages are being generated faster than they can be displayed on the console. The messages can not be guaranteed to be seen so this message replaces the lost messages. |
- |
"Consider using conditional debugging or turning off console logging." |
|
IOSXE_INFRA-3-CYAN_API_ERROR |
3-Error |
Failed to retrieve platform dependent value of [chars] err=[dec] |
CYAN API function failed |
polaris-plat-abs |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-GET_BUFFER_ERR |
3-Error |
Interrupt processing of Punt received packets over socket failed to get a packet buffer for len [dec] |
Failed to get a packet buffer from the specified pool. |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-IDB_CREATE_ERR |
3-Error |
Failed to create IDBInterface Descriptor Block for Punt/Inject |
Creating an idb corresponding to an interface failed. |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-IDB_INIT_ERR |
3-Error |
Failed to initialize IDBInterface Descriptor Block for Punt/Inject |
Hit error when we initialize idb. |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-IFS_DFLT_FS_REG_FAIL |
3-Error |
Unable to set [chars] as a default file system.\n |
IOSXE's platform dependent code failed to register the default file system. |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-IFS_EXTLINK_ADD_FAIL |
3-Error |
Could not add filesystem [chars] to IFS links |
Attempt to add filesystem root to allow for links failed |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-IFS_INIT_HIDDEN_FAIL |
3-Error |
IOSXE shim layer initialization failed: Can not create receiving queues |
IOSXE IOS shim layer initialization of hidden path watch failed |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-IFS_UDEV_REMOVE_FAIL |
3-Error |
Could not remove udev device [chars] |
Attempt to remove udev device failed |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-INJECT_EMBEDDED_HDR_LENGTH_ERR |
3-Error |
Can't allot space needed for embedded inject hdr size [dec] exceeds limit |
Can't allot space needed for embedded inject header exceeds pak header space |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-INJECT_FEATURE_ESS_ERR |
3-Error |
ESS segment not found type [dec] hdl 0x%8x |
Packets to be injected to an unsupported ESS segment |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-INJECT_GSB_CTL_INIT_FAIL |
3-Error |
Inject adjacency subblock init failed |
Adj subblock control or register failed |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-INJECT_HDR_LENGTH_ERR |
3-Error |
Inject hdr size [dec] exceeds limit |
Inject header length exceeds pak header space |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-INJECT_HEADER_ERR |
3-Error |
Transmit packet to the socket failed as packet header length is greater than datagram size. It's an incorrect packet and cannot proceed sending. header length is [dec] datagram size is [dec]. |
Packet header length is wrong. |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-INJECT_NO_IF_OUTPUT_ERR |
3-Error |
Output intf is NULL [chars] |
Output intf is requred to proceed else skip the feautre |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-INVALID_ERRMSG |
3-Error |
Error message type [dec] not defined |
Error message type used is not defined in IOSXE infrastruction |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-INVALID_RUNTIME_IDX |
3-Error |
Thread runtime index [dec] is not valid |
Export the thread's running time failed. |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-LIIN_TUN_MSG_ERR |
3-Error |
LIIN error - [chars] [chars] [dec] |
LIIN in Tunnel mode experiencing error |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-MALLOC_FAST_ERR |
3-Error |
Failed to allocate memory for Punt/Inject socket instance |
malloc_fast failed to allocate memory. |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-MCPRP_INIT_PUNTPATH_FD_ERR |
3-Error |
Initializing the ipc control for the puntpath fd failed |
Initializing the ipc control for the puntpath fd failed |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-PI_SOCKET_RAW_INIT_ERR |
3-Error |
Punt/Inject socket initialization failed |
PI Socket Raw initialization failed. |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-PI_SOCKET_RAW_PRE_INIT_ERR |
3-Error |
Punt/Inject socket pre-initializationIDB creation failed |
PI Socket Raw pre-initialization failed. |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-PI_TUN_INIT_ERR |
3-Error |
Punt/Inject TUN initialization - [chars] failed |
PI TUN initialization failed. |
picasso-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-PUNT_ADDR_RES_ENCAP_ERR |
3-Error |
Punted address resolution packet with unknown encap [chars] |
Punted packet for ARP/ND with encap not supported |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-PUNT_INCOMP_WRONG_ADJID |
3-Error |
Punted address resolution packet linktype [chars] adj-id [dec] is with linktype [chars]\n |
CPP needs to punt incomplete adjacency for resolution by specifying the adjacency-id but the included adjacency-id does not match the incomplete adjacency this packet triggered. |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-PUNT_KEEPALIVE_LOG_ERR_ALLOC_CSB |
3-Error |
Failed to allocate a csb |
Can't allocate a csb when generating punt err log |
mcp-infrastructure |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-PUNT_KEEPALIVE_LOG_ERR_ALLOC_TTY |
3-Error |
Failed to allocate a tty |
Can't allocate a TTY when generating punt err log |
mcp-infrastructure |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-PUNT_KEEPALIVE_LOG_ERR_OPEN_FILE |
3-Error |
Failed to open file: [chars] |
Failed to open file when generating punt err log |
mcp-infrastructure |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-PUNT_KEEPALIVE_LOG_ERR_PARSE_CMD |
3-Error |
Failed to parse command: [chars] |
Failed to parse a command when generating punt err log |
mcp-infrastructure |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-PUNT_KEEPALIVE_LOG_ERR_WRITE_TO_FILE |
3-Error |
Write to file Id [dec] failed [dec] bytes expected [dec] bytes |
Write to file failed when generating punt err log |
mcp-infrastructure |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-PUNT_SVC_PROC_ERR |
3-Error |
Punt service [chars] create failed |
Punt service process can not be created |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-PUNT_SVC_TYPE_UNKNOWN |
3-Error |
Punted packet with unknown service type [dec] |
Punted pak with an unsupported service type |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-RELOAD_INFO_SAVE_FAIL |
3-Error |
Unable to save reload information: [dec]: [chars].\n |
IOSXE's platform dependent code failed to save the reload information. |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-SHIM_INIT_DISPATCH_INIT_FAIL |
3-Error |
IOSXE shim layer initialization dispatch path init failed. |
IOSXE IOS shim layer initialization of TDL disatch path |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-SHIM_INIT_MEM_FAIL |
3-Error |
IOSXE shim layer initialization failed: Memory initialization failed. |
IOSXE IOS shim layer initialization of memory failed |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-SHIM_INIT_PROC_FAIL |
3-Error |
IOSXE shim layer initialization failed: Dispatch process creation failed |
IOSXE IOS shim layer initialization creating dispatch process failed |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-SHIM_INIT_TDL_FAIL |
3-Error |
IOSXE shim layer initialization TDL Lib [chars] failed. |
IOSXE IOS shim layer initialization of TDL library |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-SHIM_INIT_WQ_CHASFS_FAIL |
3-Error |
IOSXE shim layer initialization failed: Can not create receiving chasfs watched queue |
IOSXE IOS shim layer initialization of watched queue failed |
iosxe-chassismgr |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-SHIM_INIT_WQ_FAIL |
3-Error |
IOSXE shim layer initialization failed: Can not create receiving queues |
IOSXE IOS shim layer initialization of watched queue failed |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-SHIM_IPC_NOT_PROCESSED |
3-Error |
msg handler returned FALSE for IPC msg for fd [dec] seq_num [dec] service [chars] |
- |
- |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-SHIM_NO_IPC_DISPATCH_HDL |
3-Error |
IOSXE shim layer [chars] process message without IPC dispatch handler. |
IOSXE IOS shim layer has no ipc dispatch handler set |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-SHIM_RXMSG_NO_IPC_HDL |
3-Error |
IOSXE shim layer without IPC handler for fd [dec] seqnum [dec]. |
IOSXE IOS shim layer cannot find ipc handler |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-SN_IPFRR_PROC_ERR |
3-Error |
Static Nexthop IPFRR [chars] create failed |
SN IPFRR process can not be created |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-SOCKET_PEEK_ERR |
3-Error |
Interrupt processing of Punt received packets over socket failed as peek of packet returned error: [chars] |
Peek at incoming message hit error |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-SOCKET_RECV_ERR |
3-Error |
Interrupt processing of Punt received packets over socket failed as receive packet hit error: [chars] |
Hit error when receives packet from a socket. |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-SOCKET_SEND_ERR |
3-Error |
Transmit packet to the socket hit error: [chars] |
Transmit a packet to another socket hit error. |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-SWIFT_ORCH_PROC_FAIL |
3-Error |
IOSXE SWIFT Orchestrator process creation failed |
The SWIFT Orchestrator process could not be created |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-TLS_TUN_HOST_IF_ERR |
3-Error |
TLS tunnel to host interface hit error: [chars] |
TLS tunnel to host interface hit error |
picasso-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-TLSCD_IF_ERR |
3-Error |
[chars] |
TLS client daemon interface hit error |
tlscd-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-TUN_RECV_ERR |
3-Error |
Interrupt processing of Punt received packets over TUN interface failed as read hit error: [chars] |
Hit error when receives packet from TUN. |
picasso-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-TUN_SEND_ERR |
3-Error |
Transmit packet to the TUN interface hit error: [chars] |
Transmit packet to the TUN interface hit error. |
picasso-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-VM_PAGE_TABLE_ERR |
3-Error |
VM guarded page operation failed address 0x[hec] [chars] |
VM guarded page avl tree operation error |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-3-VRF_OPEN_CNTRL_FD_ERR |
3-Error |
Control fd open failed for VRF [chars] with error: [chars] |
Control fd open failed for a specified VRF |
picasso-infra |
LOG_STD_ACTION |
|
IOSXE_INFRA-4-BSO_MSG_RIB_WATCH_WARN |
4-Warning |
BSO message RIB watch start error |
BSO message RIB watch start error |
iosxe-p-punject |
LOG_STD_ACTION |
|
IOSXE_INFRA-4-INJECT_TUN_NONIP_WARN |
4-Warning |
pak with linktype [chars] gets into non-ip tunnel |
IP/IPv6/MPLS packet should to go through GRE tunnel for non-IP payload |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-4-NO_PUNT_KEEPALIVE |
4-Warning |
Keepalive not received for [dec] seconds |
Punt Inject keepalive message was not received |
mcp-infrastructure |
LOG_STD_ACTION |
|
IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_CLOSE_FILE |
4-Warning |
Failed to close file with descriptor: [dec] |
Closing of file failed when generating punt err log |
mcp-infrastructure |
LOG_STD_ACTION |
|
IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_GET_FILE_NAME |
4-Warning |
Failed to get file name: [chars] |
Punt keepalive log error seen |
mcp-infrastructure |
LOG_STD_ACTION |
|
IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_GET_PROCID |
4-Warning |
Failed to get process id |
Can't get identifier of the process generating punt err log |
mcp-infrastructure |
LOG_STD_ACTION |
|
IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_INV_FILE_ID |
4-Warning |
Invalid file descriptor: [dec] |
Invalid file descriptor was found when generating punt err log |
mcp-infrastructure |
LOG_STD_ACTION |
|
IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_INV_PARAM |
4-Warning |
Invalid parameter: [chars] |
Invalid parameter was passed when generating punt err log |
mcp-infrastructure |
LOG_STD_ACTION |
|
IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_INV_PROCID |
4-Warning |
Invalid proc id [dec] expected [dec] |
Invalid process trying to generate punt err log |
mcp-infrastructure |
LOG_STD_ACTION |
|
IOSXE_INFRA-5-PUNT_SVC_CANT_ENQUEUE |
5-Notice |
Punted pak can't be enqueued for service |
Punted pak enqueue failed |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-5-PUNT_SVC_INVALID_OPT_PKT |
5-Notice |
Invalid IPv4 options packet punted to RP |
Invalid IPv4 options packet dropped in RP |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-6-AUXTHD_REQUEST |
6-Information |
Too many outstanding requests for file system access |
Resource temporarily unavailable |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-6-CHASFS_CLOCK_SET_FAIL |
6-Information |
Failed to set Chasfs property on system time change |
Unable to set chasfs property on system time change |
iosxe-chassismgr |
LOG_STD_ACTION |
|
IOSXE_INFRA-6-CONSOLE_ACTIVE |
6-Information |
[chars] |
Indicates that the current instance of IOS is assuming active control of the console. This is informational. |
- |
LOG_STD_NO_ACTION |
|
IOSXE_INFRA-6-HARDWARE_CLOCK_SET_FAIL |
6-Information |
Failed to set Hardware clock on system time change |
Unable to set Hardware clock on system time change |
iosxe-chassismgr |
LOG_STD_ACTION |
|
IOSXE_INFRA-6-PLATFORM_RELOAD |
6-Information |
[chars] |
Indicates that the current instance of IOS is being reset by the platform code. This is part of a normal reset sequence and the message is informational. |
- |
LOG_STD_NO_ACTION |
|
IOSXE_INFRA-6-PROCPATH_CLIENT_HOG |
6-Information |
IOS shim client '[chars]' has taken %ld msec runtime: %ld msec to process |
The specified IOSXE IOS shim client has taken too long to process a received IPC or chasfs message |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-6-SHIM_RXMSG_IPC_INFO |
6-Information |
IOS shim layer process IPC msg for fd [dec] seq_num [dec] ipc_status [dec] |
- |
- |
LOG_STD_ACTION |
|
IOSXE_INFRA-6-THEAD_SELECT_ERR |
6-Information |
Inbound message or packet select error [chars]. |
Socket select operation error in threads |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_INFRA-6-TLSCD_IF_INFO |
6-Information |
[chars] |
Some info from TLS client daemon interface |
tlscd-infra |
LOG_STD_ACTION |
|
IOSXE_LICENSE_POLICY_MANAGER-2-BAY_MALLOC_FAILED |
2-Critical |
[chars]: Policy Mgr Bay DB malloc failed for [dec]/[dec] |
Memory allocation for SPA/EPA failed |
asr1k-smart-lic |
LOG_STD_ACTION |
|
IOSXE_LICENSE_POLICY_MANAGER-2-CONFIG_NULL |
2-Critical |
[chars]: Configuration is unavailable |
License Configuration is undefined for this platform. |
asr1k-smart-lic |
LOG_STD_ACTION |
|
IOSXE_LICENSE_POLICY_MANAGER-2-FEATURE_CONFIG_NULL |
2-Critical |
[chars]: Feature Configuration is unavailable |
Feature Configuration is undefined for this platform. |
asr1k-smart-lic |
LOG_STD_ACTION |
|
IOSXE_LICENSE_POLICY_MANAGER-2-FEATURE_MALLOC_FAILED |
2-Critical |
[chars]: Policy Mgr Feature Registration struct malloc failed |
Memory allocation for Feature Registration Struct failed |
asr1k-smart-lic |
LOG_STD_ACTION |
|
IOSXE_LICENSE_POLICY_MANAGER-2-FEATURE_NAME_NULL |
2-Critical |
[chars]: Feature name is NULL |
License feature name string is NULL |
asr1k-smart-lic |
LOG_STD_ACTION |
|
IOSXE_LICENSE_POLICY_MANAGER-2-IF_MALLOC_FAILED |
2-Critical |
[chars]: Policy Mgr IF DB malloc failed for [dec]/[dec] |
Memory allocation for SPA/EPA interfaces failed |
asr1k-smart-lic |
LOG_STD_ACTION |
|
IOSXE_LICENSE_POLICY_MANAGER-2-LIC_REG_FAILED |
2-Critical |
[chars]: Failed to register [chars] license feature result = [hex] |
License Registration failed |
asr1k-smart-lic |
LOG_STD_ACTION |
|
IOSXE_LICENSE_POLICY_MANAGER-2-LIC_REL_FAILED |
2-Critical |
[chars]: [dec]/[dec]: Lic release failed idx:[dec] feature=[chars] lic_cnt=[dec] |
License Release failed |
asr1k-smart-lic |
LOG_STD_ACTION |
|
IOSXE_LICENSE_POLICY_MANAGER-2-LIC_REL_GEN_FAIL |
2-Critical |
[chars]: [dec]/[dec]: Lic request failed |
License Release failed |
asr1k-smart-lic |
LOG_STD_ACTION |
|
IOSXE_LICENSE_POLICY_MANAGER-2-LIC_REQ_FAILED |
2-Critical |
[chars]: [dec]/[dec]: Lic request failed idx:[dec] feature=[chars] lic_cnt=[dec] |
License Request failed |
asr1k-smart-lic |
LOG_STD_ACTION |
|
IOSXE_LICENSE_POLICY_MANAGER-2-LIC_REQ_GEN_FAIL |
2-Critical |
[chars]: [dec]/[dec]: Lic request failed |
License Request failed |
asr1k-smart-lic |
LOG_STD_ACTION |
|
IOSXE_LICENSE_POLICY_MANAGER-4-DISABLE_MACSEC |
4-Warning |
[chars]: Disabling MACsec configuration due to insufficient license |
Disabling MACsec configuration from port due to insufficient MACsec license |
asr1k-port-lic |
"Purchase/Install MACsec license" |
|
IOSXE_LICENSE_POLICY_MANAGER-4-INSUF_LIC |
4-Warning |
[dec]/[dec]/[dec]: Insufficient [chars] license skipping license request assuming customer has honor license |
Permanent/Evaluation licenses have exhausted skipping license request asuming customer has purchased license |
DDTS_COMPONENT |
"Nothing the system is working properly" |
|
IOSXE_LICENSE_POLICY_MANAGER-6-LIC_REL_SUC |
6-Information |
[dec]/[dec]/[dec]: License release is successful for [chars] feature |
License release is successful port allowed to go down |
DDTS_COMPONENT |
"Nothing the system is working properly" |
|
IOSXE_LICENSE_POLICY_MANAGER-6-LIC_REQ_SUC |
6-Information |
[dec]/[dec]/[dec]: License request is successful for [chars] feature |
License release is successful port allowed to go down |
DDTS_COMPONENT |
"Nothing the system is working properly" |
|
IOSXE_LICENSE_RP-3-UNREGISTER_FAIL |
3-Error |
License unregistration not successful for feature [chars] |
Unregistration failed as license was not released. |
iosxe-csl |
"License has to be released before unregistering" |
|
IOSXE_LMANRP-3-MSGDISPATCH |
3-Error |
Unable to dispatch received TDL message from lman daemon. |
An unexpected condition has occurred while IOS was trying to dispatch a TDL message received from lman daemon. |
iosxe-csl |
LOG_STD_ACTION |
|
IOSXE_LMANRP-3-MSGINITFAIL |
3-Error |
Failed to initalize required lman resource: [chars] |
During the initialization of the resources required by lman a failure occured. This has prevented lman from being activated. |
iosxe-csl |
LOG_STD_ACTION |
|
IOSXE_LMANRP-3-MSGOPERATION |
3-Error |
Unable to [chars] the [chars] to license manager i.e. lman daemon. Error: [dec] |
An unexpected condition has occurred while IOS was trying to send a TDL message to lman daemon. |
iosxe-csl |
LOG_STD_ACTION |
|
IOSXE_MGMTVRF-3-AFI_ATTACH_FAIL |
3-Error |
Management VRF AFI [chars] attach failed |
Can not create afi subblock for mgmt vrf |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_MGMTVRF-3-INTF_ATTACH_FAIL |
3-Error |
Management VRF attach to mgmt [chars] failed |
Can not associate mgmt port to mgmt vrf |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_MGMTVRF-3-PROCESS_CREATE_FAIL |
3-Error |
Management VRF process creation failed [chars] |
Can not create IOS process for mgmt port init |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_MGMTVRF-3-SET_TABLEID_FAIL |
3-Error |
Installing [chars] Management interface tableid 0x[hec] failed |
Fail to set mgmt port tableid into Linux kernel |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_MGMTVRF-3-VRF_CREATE_FAIL |
3-Error |
Management VRF creation failed [chars] |
Can not create mgmt vrf during system init |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_MGMTVRF-6-CREATE_SUCCESS_INFO |
6-Information |
Management vrf [chars] created with ID [dec] ipv4 table-id 0x[hec] ipv6 table-id 0x[hec] |
mgmt vrf and ipv4 ipv6 tables created for mgmt port |
iosxe-iosd-infra |
- |
|
IOSXE_MLP-2-DB_ALLOC_FAIL |
2-Critical |
MLP link db allocation failed |
MLP link database error. Memory chunk creation for MLP link database has failed. |
iosxe-mlppp |
"Check for accurate memory management. " "Perform memory leak checks " "and look for memory corruption causes. " "Execute 'show proc memory' command." |
|
IOSXE_MLP-2-DB_DELETE_FAIL |
2-Critical |
MLP link db entry delete for link [chars] failed |
MLP link database error. Removal of entry from MLP link database has failed. |
iosxe-mlppp |
"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. " |
|
IOSXE_MLP-2-DB_DESTROY_FAIL |
2-Critical |
MLP link database destroy failed |
MLP link database error. Memory chunk destroy has failed for MLP link database. |
iosxe-mlppp |
"Check for accurate memory management. " "Perform memory leak checks " "and look for memory corruption causes. " "Execute show proc memory command." |
|
IOSXE_MLP-2-DB_ENTRY_ALLOC_FAIL |
2-Critical |
MLP link db entry allocation for link [chars] failed |
MLP link database error. Memory chunk allocation for MLP link database entry has failed. |
iosxe-mlppp |
"Check for accurate memory management. " "Perform memory leak checks and " "look for memory corruption causes. " "Execute 'show proc memory' command." |
|
IOSXE_MLP-2-DB_ENTRY_FREE_FAIL |
2-Critical |
MLP link entry free failed |
MLP link database error. Memory chunk free of MLP link database entry has failed. |
iosxe-mlppp |
"Check for accurate memory management. " "Perform memory leak checks " "and look for memory corruption causes. " "Execute 'show proc memory' command." |
|
IOSXE_MLP-2-DB_INSERT_FAIL |
2-Critical |
MLP link db entry add for interface [chars] failed |
MLP link database error. Insertion of a new entry into MLP link database has failed. |
iosxe-mlppp |
"Check for accurate memory management. " "Perform memory leak checks " "look for memory corruption causes " "verify correct database management. " "Execute 'show proc memory' command." |
|
IOSXE_MLP-3-ENQUEFAIL |
3-Error |
Unable to send [chars] [chars] message to Forwarding Manager Process |
An unexpected condition has occurred which resulted in a configuration \n\ not being sent to the Forwarding Manager Processs. |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_MLP-4-UPDSTATSERR |
4-Warning |
Update MLP statistics error |
An unexpected condition has occurred when updating mlp statistics |
iosxe-fwdmgr |
LOG_STD_ACTION |
|
IOSXE_MMA_FMP-3-ENQUEFAIL |
3-Error |
Enqueue of TDL message failed [chars]. |
- |
- |
- |
|
IOSXE_MMA-3-ENQUEFAIL |
3-Error |
Enqueue of TDL message failed [chars]. |
- |
- |
- |
|
IOSXE_MOCK_SIMULATION-3-BAD_GLIBC_BUF_FREE |
3-Error |
An IOS buffer is freed into GLIBC buffer pool buffer blockmagic 0x[hec] flags 0x[hec] |
An IOS buffer is freed into GLIBC buffer pool. |
iosxe-mock-simulation |
LOG_STD_ACTION |
|
IOSXE_MOCK_SIMULATION-3-CALLED_FROM_INT |
3-Error |
API call incorrectly made from interrupt level |
- |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_MOCK_SIMULATION-3-NULLQ |
3-Error |
Invalid API parameter |
An external routine provided by the ASR1000 scheduler was incorrectly called with an invalid NULL pointer. |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_OIR-3-CARDERR |
3-Error |
Could not read state property for [chars] slot [dec] |
The OIR facility detected a failure for exceeding the number of retries to find state chasfs property. |
- |
LOG_STD_NO_ACTION |
|
IOSXE_OIR-3-MODULE |
3-Error |
Missing [chars] for [chars] |
A hardware or software error occurred. |
iosxe-iosd-infra |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_OIR-3-OIRTWICE |
3-Error |
Subslot [dec]/[dec] OIR insertion/removal not paired up: [chars] |
An internal OIR-related error occured for the specified SPA. |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_OIR-3-POWER_CYCLE_IMMINENT |
3-Error |
The SPA in subslot [dec]/[dec] will be power cycled in [dec] seconds. |
The SPA in the specified subslot will be power cycled in the amount of time specified in the error message. |
- |
LOG_STD_NO_ACTION |
|
IOSXE_OIR-3-PROCMSG |
3-Error |
Process msg send failed for process[dec] |
Process message send failed. |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_OIR-3-QUIESCE_FAIL |
3-Error |
Quiesce failed for subslot [dec]/[dec] error = [dec] |
The RP failed to contact the SPA during failover. The SPA will be reset. |
iosxe-iosd-infra |
LOG_STD_NO_ACTION |
|
IOSXE_OIR-3-SPA_INTF_ID_ALLOC_FAILED |
3-Error |
Failed to allocate interface identifiers for SPA[chars] in slot/bay: [dec]/[dec] |
Failed to get CC buffer and flow control identifiers for the SPA in the specified subslot Traffic cannot flow through the SPA under this failure condition. This can happen if the system runs out of available identifiers. |
iosxe-spa-infra |
"Try to reduce the number of interfaces" "configured in the system either by physically removing the SPAs" "or by changing the system configuration" |
|
IOSXE_OIR-3-SPA_MDR_FAIL |
3-Error |
Minimal Disruptive Restart process failed for SPA in subslot [dec]/[dec] reason [chars]. |
The SPA in the subslot failed Minimal Disruptive Restart. Minimal Disruptive Restart process is aborted and an attempt will be made to recover the SPA by resetting the SPA hardware. |
iosxe-binos-ha |
LOG_STD_NO_ACTION |
|
IOSXE_OIR-3-UNQUIESCE_FAIL |
3-Error |
Unquiesce failed for subslot [dec]/[dec] error = [dec] |
The RP failed to unquiesce the SPA in the specified subslot. The SPA will be reset. |
iosxe-iosd-infra |
LOG_STD_NO_ACTION |
|
IOSXE_OIR-6-CARDRECONCILE |
6-Information |
SPA type changed on subslot [dec]/[dec] from [dec] to [dec] |
The SPA in the specified subslot has been initialized and it has been detected that it is of a different type to the SPA that was previously in this subslot. |
- |
LOG_STD_NO_ACTION |
|
IOSXE_OIR-6-CLEAR_FAKE_SPA |
6-Information |
Insert Event received for subslot [dec]/[dec] FAKE_SPA->NONE |
The OIR facility detected the insertion of a SPA from the subslot number specified in the message. SPA insertion happened while standby Supervisor is booting up. This results into config mismatch which software can't handle and this will cause standby to go for reload. |
- |
LOG_STD_NO_ACTION |
|
IOSXE_OIR-6-INSCARD |
6-Information |
Card [chars] inserted in [chars]slot [chars] |
The OIR facility detected the insertion of a card in the slot number specified in the message. |
- |
LOG_STD_NO_ACTION |
|
IOSXE_OIR-6-INSSPA |
6-Information |
SPA inserted in [chars]/[dec] |
The OIR facility detected the insertion of a SPA in the subslot number specified in the message. |
- |
LOG_STD_NO_ACTION |
|
IOSXE_OIR-6-INSSSFP |
6-Information |
Smart SFP inserted in port [chars] |
The OIR facility detected the insertion of TSoP/VCoP SSFP in the port number specified in the message. |
- |
LOG_STD_NO_ACTION |
|
IOSXE_OIR-6-OFFLINECARD |
6-Information |
Card [chars] offline in [chars]slot [chars] |
The OIR facility detected the state change to offline for the card in the slot number specified in the message. |
- |
LOG_STD_NO_ACTION |
|
IOSXE_OIR-6-ONLINECARD |
6-Information |
Card [chars] online in [chars]slot [chars] |
The OIR facility detected the state change to online for the card in the slot number specified in the message. |
- |
LOG_STD_NO_ACTION |
|
IOSXE_OIR-6-REMCARD |
6-Information |
Card [chars] removed from [chars]slot [chars] |
The OIR facility detected the removal of a card from the slot number specified in the message. |
- |
LOG_STD_NO_ACTION |
|
IOSXE_OIR-6-REMSPA |
6-Information |
SPA removed from [chars]/[dec] interfaces disabled |
The OIR facility detected the removal of a SPA from the subslot number specified in the message. The interfaces on that processor 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 |
|
IOSXE_OIR-6-REMSSFP |
6-Information |
Smart SFP removed from port [chars] |
The OIR facility detected the removal of TSoP/VCoP SSFP in the port number specified in the message. |
- |
LOG_STD_NO_ACTION |
|
IOSXE_OIR-6-SOFT_RELOADSPA |
6-Information |
SPA[chars] reloaded on [chars] |
The SPA in the specified subslot is reloaded by the command <CmdBold>hw-module subslot<NoCmdBold> <CmdArg>slot#/subslot#<NoCmdArg> <CmdBold>reload<NoCmdBold> |
- |
LOG_STD_NO_ACTION |
|
IOSXE_OIR-6-SOFT_STARTSPA |
6-Information |
SPA[chars] restarted in [chars] |
The SPA in the specified subslot is restarted by the command <CmdBold>hw-module subslot<NoCmdBold> <CmdArg>slot#/subslot#<NoCmdArg> <CmdBold>start<NoCmdBold> |
- |
LOG_STD_NO_ACTION |
|
IOSXE_OIR-6-SOFT_STOPSPA |
6-Information |
SPA[chars] stopped in [chars] interfaces disabled |
The SPA in the specified subslot is stopped by the command <CmdBold>hw-module subslot<NoCmdBold> <CmdArg>slot#/subslot#<NoCmdArg> <CmdBold>stop<NoCmdBold> The interfaces on that processor 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 |
|
IOSXE_OIR-6-SPARELOAD |
6-Information |
SPA reloaded on subslot [dec]/[dec] |
The SPA in the specified subslot is reloaded. |
- |
LOG_STD_NO_ACTION |
|
IOSXE_OIR-6-SYNCSPA |
6-Information |
SPA [chars] reloading to come up in [chars] mode |
The SPA in the specified subslot is reloaded by the command <CmdBold>hw-module subslot<NoCmdBold> <CmdArg>slot#/subslot#<NoCmdArg> <CmdBold>reload<NoCmdBold> |
- |
LOG_STD_NO_ACTION |
|
IOSXE_PEM-3-FAN_FAIL_SHUTDOWN |
3-Error |
More than one [chars] has failed Leads to shutdown the system |
The Temperature sensor reaching maximum threshold value working properly. |
- |
LOG_STD_ACTION |
|
IOSXE_PEM-3-FANFAIL |
3-Error |
The fan in [chars]/[dec] is encountering a failure condition |
The fan's hardware is reporting that the fan is failing. This is most likely because the hardware detects the fan as spinning below the minimum speed. |
- |
LOG_STD_ACTION |
|
IOSXE_PEM-3-PEMCHASFSERR |
3-Error |
The PEM in [chars] has encountered a system software error. |
The PEM's underlying software for storing PEM state is not working properly. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
IOSXE_PEM-3-PEMFAIL |
3-Error |
The Power Supply in [chars] is switched off or encountering a failure condition. |
The PEM hardware has been either switched off or is reporting a failure condition. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
IOSXE_PEM-3-PEMREDALARM |
3-Error |
Cannot enable power redundancy mode [chars] because the system is in software alarm state caused by previous active power-supply failures while in redundancy |
Configuration set by user cannot be accepted as there are previous active power supply failures while in redundancy. Letting redundancy with failed supplies would reduce the total available power |
- |
"Insert additional power supplies or restore all the previously failed supplies " "in active slots before the system went in Alarm state" |
|
IOSXE_PEM-3-PEMREDLOWSTANDBY |
3-Error |
Cannot activate [chars] configuration. Total power budget of standby power supplies is [dec]W. Standby power must be greater than or equal to the largest power supply capacity [dec]W. |
Operating in unprotected mode Should insert at least one ps in standby slots with a capacity greater than or equal to the largest capacity power supply in the system. The configuration will be applied automatically once requirements are met. |
- |
LOG_STD_ACTION |
|
IOSXE_PEM-3-PEMREDNOPWR |
3-Error |
Cannot enable power redundancy mode [chars] because config would create mode with insufficient [chars] power |
Configuration set by user is not valid as power supplies in the active slots do not contain enough power to meet the power requirements |
- |
"Insert additional power supplies and configure them to be active or " "configure current standby power supplies to active such that " "power requirements are met" |
|
IOSXE_PEM-3-SSFP_TEMPERATURE_RAISE |
3-Error |
[chars] transceiver temperature reached threshold value Leads to shutdown of the system |
The Temperature sensor reaching maximum threshold value working properly. |
- |
LOG_STD_ACTION |
|
IOSXE_PEM-3-TEMPERATURE_RAISE |
3-Error |
Sensor [chars] has reached maximum temperature value Leads to shutdown of the system |
The Temperature sensor reaching maximum threshold value working properly. |
- |
LOG_STD_ACTION |
|
IOSXE_PEM-6-FANOK |
6-Information |
The fan in [chars]/[dec] is functioning properly |
The fan was reporting a failure condition. This message indicates that the fan is no longer reporting a failure |
- |
LOG_STD_ACTION |
|
IOSXE_PEM-6-INSPEM_FM |
6-Information |
PEM/FM [chars] inserted |
The platform detected the insertion of a power/fan module in the slot number specified in the message. |
- |
LOG_STD_NO_ACTION |
|
IOSXE_PEM-6-PEMOK |
6-Information |
The PEM in [chars] is functioning properly |
The PEM hardware may have been either switched off or reporting a failure condition. This message indicates that the PEM is no longer either switched off or reporting a failure |
- |
LOG_STD_ACTION |
|
IOSXE_PEM-6-REMPEM_FM |
6-Information |
Power Supply/Fantray module [chars] removed |
The platform detected the removal of a power/fan module in the slot number specified in the message. |
- |
LOG_STD_NO_ACTION |
|
IOSXE_PLATFORM_RESOURCE_DCA-3-DCA_CFG_ERROR |
3-Error |
Platform Resource Dynamic Core Allocation Configuration Error [chars] |
Eror occured while configuring dynamic core allocation across system components. |
iosd-infra |
"Check System Core Allocations" |
|
IOSXE_PLATFORM_RESOURCE_DCA-3-DCA_ENABLE_FAIL |
3-Error |
Platform Resource Dynamic Core Allocation Failure |
An unexpected error occurred during attempt to dynamically apply a platform resource template configuration. System reboot required. |
iosd-infra |
"Reboot the system" |
|
IOSXE_PLATFORM_RESOURCE_DCA-5-DCA_ENABLE_NOTICE |
5-Notice |
Platform Resource profile [chars] : [chars] |
Informational message to indicate the start and completion of dynamically applying platform resource template configuration. |
iosd-infra |
LOG_STD_ACTION |
|
IOSXE_PLATFORM-3-WDC_INVALID_LENGTH |
3-Error |
WDC length can not be determined: [dec] |
WDC length was not retrieved properly |
iosxe-csl |
"Check if WDC is programmed on this device" |
|
IOSXE_PLATFORM-3-WDC_NOT_FOUND |
3-Error |
WDC returned length: [dec] |
WDC length was set to 0 which specifies probably WDC does not exist |
iosxe-csl |
"Check if WDC is programmed on this device" |
|
IOSXE_PLATFORM-3-WDC_TLV_NOT_FOUND |
3-Error |
WDC TLV could not be read from the Quack device |
WDC TLV couldn't be read from the Quack device |
iosxe-csl |
"Check if WDC is programmed on this device" |
|
IOSXE_PROCMIB -4-MSGERR |
4-Warning |
[chars] Error with process mib message from sub-slot [dec]/[dec] |
When processing a process MIB message from the specified subslot the specified error has occurred. |
iosxe-mibs |
LOG_STD_ACTION |
|
IOSXE_PROCMIB -4-SENDMSGERR |
4-Warning |
Failure in sending process mib information from subslot [dec]/[dec] to RP [chars] |
A failure is encountered when sending process MIB statistics from the IOS driver for the subslot specified in the message to RP IOS. This indicates a software failure. |
iosxe-mibs |
LOG_STD_ACTION |
|
IOSXE_QFP-2-LOAD_EXCEED |
2-Critical |
Slot: [dec] QFP:[dec] Load [dec]%% exceeds the setting threshold [dec]%%.\n 5 secs traffic rate on QFP: Total Input: %llu pps %llu.%llu kpps %llu bps %llu.%llu mbps |
QFP Load exceeds setting threshold. |
- |
"Monitor the traffic load." |
|
IOSXE_QFP-2-LOAD_RECOVER |
2-Critical |
Slot: [dec] QFP:[dec] Load [dec]%% recovered.\n 5 secs traffic rate on QFP: Total Input: %llu pps %llu.%llu kpps %llu bps %llu.%llu mbps |
QFP Load recovered. |
- |
"No action required normal operation." |
|
IOSXE_RP_ALARM-2-ESP |
2-Critical |
[chars] [chars] [chars]: [chars] [chars] |
- |
- |
- |
|
IOSXE_RP_ALARM-2-ESP |
2-Critical |
[chars] [chars] [chars] [chars] [chars] |
No ESP running alarm information |
- |
LOG_STD_NO_ACTION |
|
IOSXE_RP_ALARM-2-PEM |
2-Critical |
[chars] [chars] [chars]: [chars] [chars] |
- |
- |
- |
|
IOSXE_RP_ALARM-2-PEM |
2-Critical |
[chars] [chars] [chars] [chars] [chars] |
Power Entity Module missing information |
- |
LOG_STD_NO_ACTION |
|
IOSXE_RP_ALARM-6-INFO |
6-Information |
[chars] [chars] [chars]: [chars] [chars] |
- |
- |
- |
|
IOSXE_RP_ALARM-6-INFO |
6-Information |
[chars] [chars] [chars] [chars] [chars] |
Alarm assertion or deassertion information. |
- |
LOG_STD_NO_ACTION |
|
IOSXE_RP_CFG_INFO-6-MCPRP_ASCII_CFG_APPLIED |
6-Information |
System configuration : ASCII |
System is using ASCII config during startup |
polaris-mgbl-infra |
LOG_NO_ACTION |
|
IOSXE_RP_CFG_INFO-6-MCPRP_BINARY_CFG_APPLIED |
6-Information |
System configuration : Binary |
System is using binary config during startup |
polaris-mgbl-infra |
LOG_NO_ACTION |
|
IOSXE_RP_CFG_NOT-2-MSGIPCINITERROR |
2-Critical |
Error initializing IPC queue |
An unexpected condition in which IOS could not initialize\n\ a message queue to the PSD. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_CFG_NOT-2-MSGNOEXP |
2-Critical |
Can not construct a '[chars]' message for configuration export: [chars] |
This error usually indicates either an out of memory condition or a TDL error. If ample memory is available then the the TDL error may indicate a version conflict with respect to configuration. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_CFG_NOT-2-MSGTDLERROR |
2-Critical |
Error processing TDL message. [dec] |
An unexpected condition in which IOS has received a TDL \n\ message which it can not process. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_CFG_NOT-2-MSGTDLINITERROR |
2-Critical |
Configuration Notification messaging module initialization failed: Unable to initialize messaging: [chars] |
The Configuration Notification subsystem has failed to initialize the infrastructure for messaging with the Pluggable Services Daemon. Notification of configuration to critical modules cannot proceed. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_CFG_NOT-3-BOOT_IMAGE_NOT_COMPATIBLE |
3-Error |
Primary image is not compatible the system is going to reload as per user request. |
Primary image which is set in boot statement is not compatible with system. Primary image incompatible it should prompt the user to see if they wish to proceed. Aborting reload. |
esg-chassismgr |
LOG_STD_ACTION |
|
IOSXE_RP_CFG_NOT-3-BOOT_IMAGE_NOT_FOUND |
3-Error |
Primary image is not found the system is going to reload as per user request. |
Primary image which is set in boot statement either does not exist or not found. Primary image is not found it should prompt the user to see if they wish to proceed. Aborting reload. |
asr1k-chassismgr |
LOG_STD_ACTION |
|
IOSXE_RP_CFG_NOT-3-BOOT_IMAGE_VALIDATE_UNSUPPORTED_PLATFORM |
3-Error |
Boot image validate function does not recognize the current platform type. This is likely due to new chassis/platform variant being introduced. The reload operation is not affected however presence of this syslog indicates that esg-chassismgr component owner should investigate and determine root cause. |
Boot image validate function does not recognize the current platform type. This is likely due to new chassis/platform variant being introduced. The reload operation is not affected however presence of this syslog indicates that esg-chassismgr component owner should investigate and determine root cause. |
esg-chassismgr |
LOG_STD_ACTION |
|
IOSXE_RP_CFG_NOT-3-BOOT_VAR_NOT_SET |
3-Error |
Either the boot variable does not exist or the buffer is too small. Keep it blank. |
Boot variable either does not exist or buffer is too small. Not able to set boot variable. Ignoring it.Aborting reload. |
asr1k-chassismgr |
LOG_STD_ACTION |
|
IOSXE_RP_CFG_NOT-3-MCP_DBPERSIST_ERROR |
3-Error |
System configuration update could not complete |
When a 'reload' operation occurs this chasfs property is read to determine the status of the DB persist/restore/delete operation. This message indicates that the operation failed. |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
IOSXE_RP_CFG_NOT-3-MCP_DBPERSIST_STAT |
3-Error |
Failed to read [chars] property: [dec] |
When a 'reload' operation occurs this chasfs property is read to determine the status of the DB persist/restore/delete operation. This message indicates that the read failed. |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
IOSXE_RP_CFG_NOT-3-MCP_FRU_INVALID |
3-Error |
Unknow FRU location: [chars] |
Unknown FRU location |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
IOSXE_RP_CFG_NOT-3-MCP_FRU_LOCATION |
3-Error |
Failed to get local FRU location: [dec] |
Unable to get local FRU location |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
IOSXE_RP_CFG_NOT-3-MCPRP_BINARY_CFG_DEL_FAILED |
3-Error |
System could not delete binary startup-config error: [chars] |
Each time that you erase startup-config binary-config is also erased. This message indicates that system failed to erase binary-configuration. |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
IOSXE_RP_CFG_NOT-3-MCPRP_BINARY_CFG_GEN_FAILED |
3-Error |
System could not generate binary startup-config error: [chars] |
Each time that you save running-config to startup-config a binary file is created and the ASCII file is updated. A valid binary configuration file reduces the overall boot time significantly. This message indicates that system failed to generate binary-configuration. |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
IOSXE_RP_CFG_NOT-3-MCPRP_BINARY_CFG_REPLAY_FAILED |
3-Error |
System could not apply binary startup-config error: [chars] |
During reload system uses binary startup configuration. A valid binary configuration file reduces the overall boot time significantly. This message indicates that system failed to apply binary-configuration. |
polaris-mgbl-infra |
LOG_STD_ACTION |
|
IOSXE_RP_CFG_NOT-3-MSGENCRYPTINVALID |
3-Error |
The mcprp_cfg_notify subsystem has seen an encryption type it does\n\ not recognize. [dec] |
An unexpected condition has occurred while IOS is trying to process\n\ a username command. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_CFG_NOT-3-MSGIPCTXERROR |
3-Error |
IPC transmit error. [dec] |
An unexpected condition in which IOS encountered an error\n\ trying to send a message to another process. [dec] |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_CFG_NOT-3-MSGNOCAND |
3-Error |
Can not construct a candidate entry for configuration export |
This error usually indicates either an out of memory condition or a TDL error. If ample memory is available then the the TDL error may indicate a version conflict with respect to configuration. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_CFG_NOT-3-MSGNOPWARR |
3-Error |
Can not construct an array for configuration export |
This error usually indicates either an out of memory condition or a TDL error. If ample memory is available then the the TDL error may indicate a version conflict with respect to configuration. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_CFG_NOT-3-MSGNOREPLMSG |
3-Error |
Can not construct a replace message for configuration export |
This error usually indicates either an out of memory condition or a TDL error. If ample memory is available then the the TDL error may indicate a version conflict with respect to configuration. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_CFG_NOT-3-MSGNOUPDATEMSG |
3-Error |
Can not construct an update message for configuration export |
This error usually indicates either an out of memory condition or a TDL error. If ample memory is available then the the TDL error may indicate a version conflict with respect to configuration. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_CFG_NOT-3-MSGOBJNULL |
3-Error |
An unexpected condition in which IOS has received a null\n\ pointer that it expects to be non-null. |
An unexpected condition has occurred while IOS is trying to process\n\ a username command. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_CFG_NOT-3-NVWRITE_EXPORT |
3-Error |
Failed to export [chars] notification: [dec] |
When a 'write memory' or 'write erase' operation occurs the Configuration Notification subsystem exports this event into the chassis file system. This message indicates that the export failed. |
access |
LOG_STD_ACTION |
|
IOSXE_RP_CFG_NOT-6-IOX_SERVICE_NOTSUPPORTED |
6-Information |
IOx service not supported. |
IOx service is not supported in this platform currently. This may be either due to the feature unavailability or due the current inadequate license level of the system. |
iox-caf |
- |
|
IOSXE_RP_CFG_NOT-6-MCPRP_BINARY_CFG_MISSING |
6-Information |
Binary configuration missing. |
System is booted with ASCII based startup configuration. Please perform \write mem\ to generate binary configuration. System uses binary-config internally to reduce overall bootime significantly. |
polaris-mgbl-infra |
- |
|
IOSXE_RP_DIAG_TEST-3-MSGDIAGCANTENQUEUE |
3-Error |
Online diagnostics could not enqueue a diagnostic test response. |
The iosxe online diagnostics failed to respond properly to a \n\ request by the system to perform a diagnostic test. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
IOSXE_RP_DIAG_TEST-3-MSGDIAGTIMEOUT |
3-Error |
A timeout occured while waiting for an online diagnostic \n\ test to finish. |
The iosxe online diagnostics failed to respond properly to a \n\ request by the system to perform a diagnostic test. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
IOSXE_RP_DIAG_TEST-3-MSGIPCTXERROR |
3-Error |
IPC transmit error. [dec] |
An unexpected condition in which IOS encountered an error \n\ trying to send a message to another process. [dec] |
iosxe-chassismgr |
LOG_STD_ACTION |
|
IOSXE_RP_DIAG_TEST-3-MSGOBJNULL |
3-Error |
An unexpected condition in which IOS has received a null\n\ pointer that it expects to be non-null. |
An unexpected condition has occurred while IOS is trying to perform \n\ online diagnostics work. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
IOSXE_RP_DIAG_TEST-3-MSGRESPTDLERR |
3-Error |
A diagnostic test result could not be read properly. |
The iosxe online diagnostics failed to respond properly to a \n\ request by the system to perform a diagnostic test. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
IOSXE_RP_DIAG_TEST-3-MSGTDLERROR |
3-Error |
Error processing TDL message. [dec] |
An unexpected condition in which IOS has received a TDL \n\ message which it can not process. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
IOSXE_RP_DIAG_TEST-4-ERR_CNTR_HM_TEST_DATA |
4-Warning |
ERROR_COUNTER_DATA: ID:[dec] IN:%D PO:[dec] RE:[dec] RM:[dec] DV:[dec] EG:[dec] CF:[dec] TF:[dec] |
Error Counter Monitoring test has failed on one of the cards of IOSXE Corresponding Data is printed. |
iosxe-sch-gold |
LOG_STD_ACTION |
|
IOSXE_RP_DIAG_TEST-4-ERR_CNTR_HM_TEST_FAIL |
4-Warning |
ERROR_COUNTER_WARNING: Slot [chars] Error counter exceeds threshold system operation continue. |
Error Counter Monitoring test has failed on the given card of IOSXE. |
iosxe-sch-gold |
LOG_STD_ACTION |
|
IOSXE_RP_DIAG_TEST-6-MSGOUTOFORDER |
6-Information |
Received a test result after IOS had timed out. [[dec][dec]] |
When a diagnostic test is performed IOS waits for the result \n\ be returned. If it does not return in a specified period of \n\ IOS times out on that test request and moves on. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
IOSXE_RP_DIAG_TEST-6-MSGUNEXPECTEDEVENT |
6-Information |
Unexpected event recieved. |
When a diagnostic test is performed IOS waits for the result\n\ be returned. While waiting for the result IOS unexpectedly\n\ received an event it does not recognize and so IOS stopped\n\ waiting for the result. The test continued IOS does not know\n\ what the results are and hence can not report them. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
IOSXE_RP_DPIDB-3-BULK_SYNC |
3-Error |
Failed to send [chars] information to peer |
- |
iosxe-infmgr |
LOG_STD_ACTION |
|
IOSXE_RP_DPIDB-3-CF |
3-Error |
Datapath IDB CF operation failed - [chars] |
Failure in some datapath ID CF activity. |
iosxe-infmgr |
"show interface" |
|
IOSXE_RP_DPIDB-3-DECODE |
3-Error |
Decode via [chars] of [chars] failed |
The active route processor has sent a notification to the standby\n\ to inform of the completion of the bulk synchronization of the DPIDX\n\ configuration. The standby has failed to respond to the active\n\ informing that it received the notification noting the reason for\n\ the failure. The resultant action taken by the standby route\n\ processor is an attempt to resynchronize. |
iosxe-infmgr |
LOG_STD_ACTION |
|
IOSXE_RP_DPIDB-3-DOWNLOADFAIL |
3-Error |
Unable to download [chars] message to [chars] |
An unexpected condition has occurred which resulted in a configuration \n\ not being sent to the reported process. |
iosxe-infmgr |
LOG_STD_ACTION |
|
IOSXE_RP_DPIDB-3-DYN_SYNC |
3-Error |
Failed to process [chars] dynamic state |
The incremental synchronization of the DPIDX configuration to the\n\ standby RP has failed to complete successfully. This implies that the\n\ configuration state between the active and standby RP is\n\ inconsistent. |
iosxe-infmgr |
"show interfaces" |
|
IOSXE_RP_DPIDB-3-EFPSTATSFAILED |
3-Error |
EFP stats message data get error: [dec] for EFP [dec] on [chars] |
An unexpected error occurred extracting fields from an EFP stats\n\ message. |
iosxe-infmgr |
LOG_STD_ACTION |
|
IOSXE_RP_DPIDB-3-FASTNOTIFY |
3-Error |
Fast notify failed for [chars] |
A fast notify message failed |
iosxe-infmgr |
"show interface" |
|
IOSXE_RP_DPIDB-3-FRRLDFLOWIDDELETIONFAILED |
3-Error |
Deletion of fast-reroute flow ID with manager failed |
An unexpected condition has occurred that deletion of\n\ fast-reroute flow ID. |
iosxe-infmgr |
"show interface" |
|
IOSXE_RP_DPIDB-3-IDBBADTYPE |
3-Error |
Datapath IDB type [dec] is not valid |
An unexpected condition has occurred as the type of\n\ a datapath IDB is not valid. |
iosxe-infmgr |
"show interface" |
|
IOSXE_RP_DPIDB-3-IDBEXIST |
3-Error |
Datapath IDB already exists in this mapping entry: [chars]-[dec] |
An unexpected condition has occurred that an attempt is made\n\ to save datapath IDB in a mapping entry filled by another. |
iosxe-infmgr |
"show interface" |
|
IOSXE_RP_DPIDB-3-IDBNONEXIST |
3-Error |
Datapath IDB does not exist in this mapping entry: [chars]-[dec] |
Datapath IDB lookup points to empty mapping entry. |
iosxe-infmgr |
"show interface" |
|
IOSXE_RP_DPIDB-3-IDBNOTVAI |
3-Error |
Invalid API call for [chars] |
Failure in an internal API |
iosxe-infmgr |
"show interface" |
|
IOSXE_RP_DPIDB-3-IDXALLOCFAILED |
3-Error |
Datapath IDB index allocation failed: [chars] |
An unexpected condition has occurred as all the available of\n\ datapath IDB indices are used. |
iosxe-infmgr |
"show interface" |
|
IOSXE_RP_DPIDB-3-IDXBADRANGE |
3-Error |
Datapath IDB index [dec] is not in a valid range |
An unexpected condition has occurred as the index of\n\ a datapath IDB is not valid. |
iosxe-infmgr |
"show interface" |
|
IOSXE_RP_DPIDB-3-IDXDELETIONFAILED |
3-Error |
Deletion of datapath IDB index from the database failed \n\ [chars] - 0x[hec] rc [dec] |
An unexpected condition has occurred that deletion of\n\ datapath IDB indices failed. |
iosxe-infmgr |
"show interface" |
|
IOSXE_RP_DPIDB-3-IDXINSERTFAILED |
3-Error |
Insertion of datapath IDB index [dec] into database failed |
An unexpected condition has occurred that insertion of\n\ datapath IDB indices failed. |
iosxe-infmgr |
"show interface" |
|
IOSXE_RP_DPIDB-3-IDXLOOKUPFAILED |
3-Error |
Lookup of datapath IDB index from the database failed [chars] |
An unexpected condition has occurred that lookup of\n\ datapath IDB indices failed. |
iosxe-infmgr |
"show interface" |
|
IOSXE_RP_DPIDB-3-IP_MTU_ALLOC_FAIL |
3-Error |
No hardware resources for [dec] byte IP MTU on [chars] |
We reached to the threshold of maximum supported unique IP MTU \ on this platform. |
- |
LOG_STD_NO_ACTION |
|
IOSXE_RP_DPIDB-3-LIST |
3-Error |
List [chars] failed for [chars] |
List enqueue or removal failed |
iosxe-infmgr |
"show interface" |
|
IOSXE_RP_DPIDB-3-MTU_ALLOC_FAIL |
3-Error |
No hardware resources for [dec] byte MTU on [chars] |
We reached to the threshold of maximum supported unique MTU on \ this platform. |
- |
LOG_STD_NO_ACTION |
|
IOSXE_RP_DPIDB-3-NOHWSUBBLOCK |
3-Error |
HWIDB [chars] does not have a hardware subblock |
An unexpected condition has occurred that no hardware subblock\n\ was previously allocated for a HWIDB. |
iosxe-infmgr |
"show interface" |
|
IOSXE_RP_DPIDB-3-NOSWSUBBLOCK |
3-Error |
SWIDB [chars] does not have a software subblock |
An unexpected condition has occurred that no software subblock\n\ was previously allocated for a SWIDB. |
iosxe-infmgr |
"show interface" |
|
IOSXE_RP_DPIDB-3-NULLTIMER |
3-Error |
NULL timer |
A timer is NULL |
iosxe-infmgr |
"show interface" |
|
IOSXE_RP_DPIDB-3-RECEIVE |
3-Error |
Message via [chars] is [chars] |
The ISSU negotiation with the peer failed to start for either the CF or\n\ IPC transport with the reason specified. |
iosxe-infmgr |
LOG_STD_ACTION |
|
IOSXE_RP_DPIDB-3-RF |
3-Error |
Datapath IDB RF operation failed - [chars] |
Failure in some datapath ID RF activity. |
iosxe-infmgr |
"show interface" |
|
IOSXE_RP_DPIDB-3-RPC |
3-Error |
Datapath IDB RPC operation failed - [chars] |
An operation pertaining to the ISSU support for DPIDX failed to complete\n\ using either the CF or IPC transport context with the reason\n\ specified |
iosxe-infmgr |
LOG_STD_ACTION |
|
IOSXE_RP_DPIDB-3-TRANSFORM |
3-Error |
[chars] of [chars] via [chars] failed for dpidx [dec] |
An attempt to either encode or decode a versioned synchronization\n\ message has failed due to an internal error encountered by the ISSU\n\ component. |
iosxe-infmgr |
LOG_STD_ACTION |
|
IOSXE_RP_DPIDB-5-MTU_ADVISORY |
5-Notice |
[chars] - [chars] |
MTU Advisory |
- |
LOG_STD_NO_ACTION |
|
IOSXE_RP_DPIDB-6-READY |
6-Information |
[chars] peer not ready discarding [chars] |
The synchronization attempt for the message has determined that the\n\ transport has lost communication with its peer. This is a normal\n\ situation which indicates that the standby route-processor is currently\n\ out of service implying a simplex redundancy mode. |
- |
- |
|
IOSXE_RP_DPIDB-6-RELOAD |
6-Information |
[chars] reloading [chars] |
A synchronization attempt between the active and standby RP peers has\n\ failed with the reason indicated. The standby peer is reloaded in an\n\ attempt to resynchronize when operating in a stateful redundant\n\ mode. |
iosxe-infmgr |
LOG_STD_ACTION |
|
IOSXE_RP_DPIDB-6-TIMEOUT |
6-Information |
Bulk sync is flow controlled by [chars] |
The bulk synchronization of the DPIDX configuration to the standby RP\n\ has encountered a flow control condition which has effected a timeout\n\ awaiting the condition to clear. This will result in a reload of the\n\ standby RP to allow the bulk synchronization to restart. |
iosxe-infmgr |
LOG_STD_ACTION |
|
IOSXE_RP_EWLC_NOT-2-EWLC_STARTUP |
2-Critical |
Starting EWLC process [dec] |
Sending TLD message to start up all eWLC processes |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_EWLC_NOT-2-MSGIPCINITERROR |
2-Critical |
Error initializing IPC queue |
An unexpected condition in which IOS could not initialize\n\ a message queue to the PSD. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_EWLC_NOT-2-MSGTDLERROR |
2-Critical |
Error processing TDL message. [dec] |
An unexpected condition in which IOS has received a TDL \n\ message which it can not process. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_EWLC_NOT-2-MSGTDLINITERROR |
2-Critical |
eWLC startup module initialization failed: Unable to initialize messaging: [chars] |
The eWLC startup subsystem has failed to initialize the infrastructure for messaging with the Pluggable Services Daemon. Notification of configuration to critical modules cannot proceed. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_IF_FLOW_IDS-3-BUFF_OFFSET_NULL |
3-Error |
Unable to utilize the memory buffer provided by the Checkpoint Facility. This [chars] CF client has failed to Bulk Sync. |
This error indicates the Checkpoint Facility is having problems recognizing its own buffer layout. If this occurs during Bulk Sync then Bulk Sync will terminate without completing. Otherwise the incremental Sync will fail. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
IOSXE_RP_IF_FLOW_IDS-3-CF_CANNOT_REGISTER |
3-Error |
The call to add this [chars] CF client to the Checkpoint Facility failed with the error [chars]. This client is unable to proceed and will not be registered. |
For some reason the Checkpoint Facility will not register this client. As a result the Standby will never receive synchronized state from this CF client on the Active RP The system is not capable of SSO and HA switchover. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
IOSXE_RP_IF_FLOW_IDS-3-CF_SEND_BULK_NONBLOCKED |
3-Error |
The Checkpoint Facility reported the error [chars] while attempting to send a message. Bulk Sync of this [chars] CF client is terminating. |
This error indicates the Checkpoint Facility has internal problems related to IPC and cannot perform a non-blocked send operation. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
IOSXE_RP_IF_FLOW_IDS-3-CF_SEND_INCR_NONBLOCKED |
3-Error |
The Checkpoint Facility reported the error [chars] while attempting to send a non-blocked message. The Incremental Sync transaction for this [chars] CF client cannot be sent to the Standby RP. |
This error indicates the Checkpoint Facility has internal problems related to IPC. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
IOSXE_RP_IF_FLOW_IDS-3-DECODE |
3-Error |
Decode via CF of [chars] failed |
A message sent via the CF transport failed in its attempt\n\ to be decoded on the standby. The resultant action taken by the\n\ standby route processor is an attempt to resynchronize. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
IOSXE_RP_IF_FLOW_IDS-3-DEFERRED_DURING_BULK_SYNC |
3-Error |
Encountered error [chars] while trying to place an [chars] transaction on the Deferred list during Bulk Sync for the [chars] CF client. |
Unable to cache a deferred transaction while Bulk Sync is underway. This can adversely impact SSO state on the Standby RP. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
IOSXE_RP_IF_FLOW_IDS-3-NO_BUFF_FOR_SYNC |
3-Error |
The Checkpoint Faclity reported the error [chars] during a request for a buffer length of [dec]. This [chars] CF client has failed to synchronize a transaction to the Standby RP. |
This error indicates that the buffer management within the Checkpoint Facility has either run out of buffers or has some other problem. If this occurs during Bulk Sync then Bulk Sync will terminate without completing. Otherwise the incremental Sync will fail. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
IOSXE_RP_IF_FLOW_IDS-3-RECEIVE |
3-Error |
Client reports message CF is [chars] |
An attempt to receive and process a versioned negotiation or\n\ synchronization message has failed due to an internal error\n\ being detected by the information received from the CF component. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
IOSXE_RP_IF_FLOW_IDS-3-RF_ADD_CLIENT_FAILED |
3-Error |
The RF facility failed to add this [chars] client reason given is [chars]. |
An operation pertaining to the ISSU support for SPA MARMOT IDs failed \n\ to complete using the CF transport context with the reason specified |
iosxe-binos-ha |
LOG_STD_ACTION |
|
IOSXE_RP_IF_FLOW_IDS-3-RF_IF_ID_REGEN_ERROR |
3-Error |
Error code [dec] encountered trying to regenerate interface flow-control identifer. If id [dec] resides in slot/subslot/port [dec]/[dec]/[dec]. |
- |
- |
- |
|
IOSXE_RP_IF_FLOW_IDS-3-RF_PEER_EVENT_BUFFER |
3-Error |
This [chars] RF client is unable to acquire an event buffer to send an RF peer message the error [chars] was returned. |
This indicates the RF facility is unable to provide a message buffer needed to communicate with the RF peer. As a consequence the RF progression may be compromised. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
IOSXE_RP_IF_FLOW_IDS-3-RF_POOL_REGEN_ERROR |
3-Error |
Id Pool Regeneration encountered error code [dec] cannot switchover. |
The background process which performs Flow Control Id Pool regeneration encountered an error. As a consequence the Standby does not have valid Flow Id pools and cannot progress to Active state. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
IOSXE_RP_IF_FLOW_IDS-3-RF_POOL_REGEN_PROCESS_FAILED |
3-Error |
The [chars] RF client Failed to create the Id Pool Regeneration process. |
The background process which performs Flow Control Id Pool regeneration failed to start. As a consequence the Standby will never obtain the relevent SSO state to enable HA switchover. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
IOSXE_RP_IF_FLOW_IDS-3-RF_PROCESS_FAILED |
3-Error |
This [chars] RF client Failed to create the Bulk Sync Process. |
The background process which performs the RF Bulk Sync failed to be created. As a consequence the Standby will never obtain the relevent SSO state to enable HA switchover. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
IOSXE_RP_IF_FLOW_IDS-3-RF_SEND_PEER |
3-Error |
This [chars] RF client encountered error [chars] when attempting to send a peer message. |
This indicates the RF facility could not send a message to the RF peer. As a consequence the RF progression may be compromised. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
IOSXE_RP_IF_FLOW_IDS-3-RF_SPA_ID_REGEN_ERROR |
3-Error |
Error code [dec] encountered trying to regenerate spa [chars] identifier in slot/subslot [dec]/[dec] |
- |
- |
- |
|
IOSXE_RP_IF_FLOW_IDS-3-SEND_FAIL_RELOAD |
3-Error |
Checkpoint Facility Failed to send a [chars] transaction for this [chars] CF client. Reloading the Standby RP. |
This indicates the underlying Checkpoint Facility could not deliver a message sent from the active RP to the standby RP. The process will automatically reload the standby RP. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
IOSXE_RP_IF_FLOW_IDS-3-TRANSFORM |
3-Error |
[chars] of [chars] via CF failed |
The ISSU negotiation with the peer failed to start for either the CF or\n\ IPC transport with the reason specified. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
IOSXE_RP_IF_FLOW_IDS-4-DEF_LIST_REMOVE |
4-Warning |
Failed to remove one entry from the Deferred Sync list for the [chars] CF client. |
An unexpected condition occured during list maintenance. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
IOSXE_RP_IF_FLOW_IDS-6-CFPEER_CANNOT_RECV |
6-Information |
The Checkpoint Peer is not ready to receive messages. The Incremental Sync transaction for this [chars] CF client will not occur. |
This error indicates the Checkpoint Facility has signalled the peer has gone away. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
IOSXE_RP_IF_FLOW_IDS-6-READY |
6-Information |
[chars] peer not ready discarding [chars] |
The synchronization attempt for the message has determined that the\n\ transport has lost communication with its peer. This is a normal\n\ situation which indicates that the standby route-processor is currently\n\ out of service implying a simplex redundancy mode. |
- |
- |
|
IOSXE_RP_MGMTE_INV-3-PROCESS_CREATE_FAIL |
3-Error |
Management ethernet inventory process creation failed |
Can not create IOS process for RP management ethernet inventory updation |
bb-intrepid-drv |
LOG_STD_ACTION |
|
IOSXE_RP_MGMTE-3-MSGCREATENULL |
3-Error |
Cannot allocate [chars] TDL message |
An unexpected condition in which IOS cannot allocate TDL message for Management ethernet. |
iosxe-tdl |
LOG_STD_ACTION |
|
IOSXE_RP_MGMTE-3-MSGTDLINITERROR |
3-Error |
Management ethernet interface messaging module initialization failed: Unable to initialize messaging: [chars] |
The Management ethernet interface subsystem has failed to initialize the infrastructure for messaging with the Pluggable Services Daemon. Configuration of management ethernet modules cannot proceed. |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_RP_MGMTE-3-PROCESS_CREATE_FAIL |
3-Error |
Management ethernet statistics process creation failed |
Can not create IOS process for RP management ethernet port statistics collection |
iosxe-iosd-fastpath |
LOG_STD_ACTION |
|
IOSXE_RP_NV-3-BACKUP_NV_ACCESS_FAIL |
3-Error |
Initial read of backup NVRAM contents failed |
This error happens when the contents of the backup NVRAM cannot be read during system initialization. The failure may be due to data corruption of the backup NVRAM contents. The primary nvram contents will be backed up here again. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
IOSXE_RP_NV-3-NV_ACCESS_FAIL |
3-Error |
Initial read of NVRAM contents failed |
This error happens when the contents of the NVRAM cannot be read during system initialization. The failure may be due to data corruption of the NVRAM contents. The initial configuration dialog will be entered and the configuration must be restored. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
IOSXE_RP_ONLINE_DIAG-3-MSGMAXCARDS |
3-Error |
Online diagnostics maximum number of cards exceeded |
An unexpected condition in which IOS has attempted to \n\ register more hardware cards for diagnostics than it\n\ expects the maximum to be. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
IOSXE_RP_ONLINE_DIAG-3-MSGOBJNULL |
3-Error |
An unexpected condition in which IOS has received a null\n\ pointer that it expects to be non-null. |
An unexpected condition has occurred while IOS is trying to perform\n\ online diagnostics work. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
IOSXE_RP_ONLINE_DIAG-3-MSGTDLERROR |
3-Error |
Error processing TDL message. [dec] |
An unexpected condition in which IOS has received a TDL\n\ message which it can not process. |
iosxe-chassismgr |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-0-INVALID_ETHERNET_MSG_HANDLER_FVT |
0-Emergency |
Invalid Ethernet Message handler Function Vector Table for [chars] Module [dec]/[dec] |
TDL Message handler vector table is not registered for Ethernet Module |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-3-BAD_IFCOMTYPE |
3-Error |
Bad ifcom message type=[dec] |
A SPA module passed down a message that the RP software\n\ was not prepared to handle. |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-3-CI_UPDATE_FAIL |
3-Error |
Failed to update connection identifier for interface [chars] |
The SPA driver is not able to update the datapath connection identifier for the interface specified in the message. This indicates a software error. |
DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
IOSXE_RP_SPA-3-DPIDX_LKUP_FAIL |
3-Error |
Failed to retrieve datapath identifier for interface [chars] |
The SPA driver is not able to retrieve the datapath identifier for the interface specified in the message. This indicates a software error. |
DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
IOSXE_RP_SPA-3-ERROR |
3-Error |
common_str_empty_str |
This message can take many forms. It provides information about a\n\ software error. |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-3-ERROR_INFO |
3-Error |
common_str_empty_str |
This message can take many forms. It provides information about a\n\ software error without traceback. |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-3-FLOWID_ALLOC_FAIL |
3-Error |
Failed to allocate a flow control identifier for interface [chars] |
The SPA driver is not able to allocate the datapath flow control identifier for the interface specified in the message. This indicates a software error. |
DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
IOSXE_RP_SPA-3-FLOWID_RELEASE_FAIL |
3-Error |
Failed to release a flow control identifier for interface [chars] status = [dec] |
The SPA driver is not able to release the datapath flow control identifier for the interface specified in the message. This indicates a software error. |
DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
IOSXE_RP_SPA-3-FOREVER |
3-Error |
cmd [dec] to [chars] slot [dec]/[dec] took [dec] usecs done [hec] |
A CCB command from the RP to a SPA module took longer than expected. |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-3-FRR_CFG_REC_FAIL |
3-Error |
Failed to record fast reroute conifguration on [chars]: [chars] |
This message is displayed when a fast reroute configuration is not properly recorded. |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-3-HWIDB_FAILURE |
3-Error |
Creation: slot [dec] subSlot [dec] port [dec] vc [dec] |
Failed to create an interface hwidb. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_RP_SPA-3-HWIDB_INIT_FAIL |
3-Error |
Failed to initialize data structure for SPA port [dec]/[dec]/[dec] |
A SPA driver was not able to properly initialize a data structure mentioned in the message. This indicates a software error. |
DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
IOSXE_RP_SPA-3-IFCFG_CMD_NOT_OWNER |
3-Error |
Process '[chars]' waiting for interface configuration command 0x[hec] to |
A process on the RP sent an configuration command to the slot specified in the error message and a different process waited for the result. This could cause incorrect line card configuration states. |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-3-IFCFG_FOREVER |
3-Error |
to [chars] slot [dec]/[dec] took [dec] usecs ret_val %lu |
A interface config command from the RP to a SPA module took\n\ longer than expected. |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-3-IFCFG_NO_UNIQUE_KEY |
3-Error |
No unique-key generator registered for interface configuration command [dec]. |
The High Availability component for SPA modules is unable to properly synchronize state information for the current configuration. |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-3-INVALID_ETHERNET_MSG_HANDLER |
3-Error |
Invalid Message Handler for [chars] on [dec]/[dec] [chars] Module |
TDL Message handler is not registered for Ethernet Module |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-3-INVALID_PORT_NUM |
3-Error |
slot=[dec] port=[dec] hwidbType=0x[hec] max_port_num=[dec] LCtype=0x[hec] |
The port number is out of range. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_RP_SPA-3-IOMD_CONFIG_FAIL |
3-Error |
The IOMD return value for BAY: [dec] CMD [dec]: code:%0x msg:[chars] |
Failed to configure in IOMD. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_RP_SPA-3-IPCALLOCFAIL |
3-Error |
Failed to allocate IPC buffer [chars] |
The RP failed to allocate a buffer for communication with a SPA |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-3-IPCPORT |
3-Error |
Failed to [chars] IPC port '[chars]' error [chars] |
The standby has failed to notify the active that its bulks\n\ synchronization of the SPA TSM has completed. The resultant action\n\ taken by the standby route processor is an attempt to resynchronize. |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-3-IPCPORTFAIL |
3-Error |
Failed to open IPC port '[chars]' with error [chars] |
The RP failed to open a port for communication with a SPA\n\ module. |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-3-IPCSENDFAIL |
3-Error |
Failed to send IPC message [chars] |
The RP failed to send a message to a SPA module. |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-3-LIC_REG_FAILED |
3-Error |
[dec]/[dec]/[dec]: Failed to register license feature [chars] err=[hex] |
License registration has been denied by license manager |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-3-LIC_REL_FAILED |
3-Error |
[dec]/[dec]/[dec]: Failed to release license feature [chars] handle=0x[hec] err=[hex] |
License release has been denied by license manager |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-3-LIC_REQ_FAILED |
3-Error |
[dec]/[dec]/[dec]: Interface enable not allowed - license request failed err=[hex] |
A 10 Gig License is required to enable this port. License request has been denied by license manager |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-3-MAC_FILTER_ADD_FAIL |
3-Error |
All the available [dec] mac filters for [chars] have been consumed. Failed to add [enet] for interface [chars] |
The hardware cannot support any more filters. |
DDTS_COMPONENT |
"The interface configuration should be reworked " "to not cross the limit set by the hardware." "If the error is still seen please " LOG_STD_SH_TECH_ACTION |
|
IOSXE_RP_SPA-3-MAX_SPA |
3-Error |
Power to IPSEC-SPA-2G in [chars] is denied because it has exceeded the number allowed[dec] |
The number of IPSEC-SPA-2G in a chassis is limited. This message is displayed when the number of IPSEC-SPA-2G in the chassis has exceeded this limit. |
DDTS_COMPONENT |
"Use only the number of supported IPSEC-SPA-2G" |
|
IOSXE_RP_SPA-3-MISSING_SPA_PKG_ERR |
3-Error |
sipspa[chars] package is not installed for slot = [dec] and subslot = [dec] SPA bootup failed. |
This message is displayed when attempting to bootup a SPA without installing a subpackage required for the same. |
- |
"Download the sub-package required for the " "affected SPA from the Cisco CCO software download site and install " "the same. This SPA can be booted in sub-package mode only. Please " "refer to the Cisco ASR platform documentation for " "obtaining and installing sub-packages." |
|
IOSXE_RP_SPA-3-MISSING_SPA_PKG_WARN |
3-Error |
sipspa[chars] package is not installed in standby for slot = [dec] and subslot = [dec]. |
This message is displayed in standby console when attempting to bootup or restart or reload a WMA SPA without installing a subpackage in the standby RP although the SPA is or will be operational due to prior wma spa package installation in active RP. If switchover takes place the WMA SPA will still be operational. But any subsequent soft or hard oir of the SPA will fail due to missing sub package required to boot up the SPA. Hence it is recommended to complete the wma spa package installation in standby also before switchover or immidiately after switchover. |
- |
"Download the sub-package required for the " "affected SPA from the Cisco CCO software download site and install " "the same for the standby RP as is done on active RP. Please refer " "to the Cisco ASR platform documentation for obtaining and installing " "sub-packages." |
|
IOSXE_RP_SPA-3-NO_HOST_INFO |
3-Error |
slot [dec] subSlot [dec] spaType 0x[hec] |
Failed to get information about the host linecard. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_RP_SPA-3-NULL_DATA_STRUCTURE |
3-Error |
common_str_empty_str |
A SPA driver is not able to retrieve the data structure mentioned in the message. This indicates a software error. |
DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
IOSXE_RP_SPA-3-SEND_L2_HDR_MSG_FAIL |
3-Error |
slot [dec] subslot [dec] |
Failed to send ngio L2 header to iomd. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_RP_SPA-3-SEND_NGIO_MSG_FAIL |
3-Error |
NGIO Module message send failed for slot [dec] subslot [dec] |
Failed to send ngio msg to iomd. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_RP_SPA-3-SONET_ALARM_PROC_ERR |
3-Error |
[chars] Error has occurred while processing in the sonet alarm-proc |
Either free/create of the memory failed in SONET alarm proc |
- |
- |
|
IOSXE_RP_SPA-3-SPA_NO_HOST_INFO |
3-Error |
slot [dec] subSlot [dec] PID [chars] |
Failed to get information about the host linecard. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_RP_SPA-3-SPA_WRONGTYPE |
3-Error |
Mismatched SPA type [dec] in slot [dec]/[dec]. Expected type [dec]. |
The SPA inserted does not match the currently provisioned SPA type. |
- |
"Replace wrong SPA with currently provisioned SPA type or type 'no card' " "to allow new card type to be discovered." |
|
IOSXE_RP_SPA-3-UNSUPPORTED_SRVCS_SPA |
3-Error |
Service SPA %#X in [dec]/[dec] is not supported. SPA bootup failed. |
This message is displayed when attempting to bootup any service SPA in router running non K9 image i.e. non-crypto image. |
- |
"Download the K9 IOS XE sub-packages and the " "required sub-package for the given service SPA from the Cisco CCO " "software download site and install the same. This SPA can be booted " "in sub-package mode only. Please refer to the Cisco ASR platform " "documentation for obtaining and installing sub-packages." |
|
IOSXE_RP_SPA-3-VC_FLOWID_ALLOC_FAIL |
3-Error |
Failed to allocate a flow control identifier for VC [dec] under interface [chars] |
The SPA driver is not able to allocate the datapath flow control identifier for the VC/interface specified in the message. This indicates a software error. |
DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
IOSXE_RP_SPA-3-VC_INGID_ALLOC_FAIL |
3-Error |
Failed to allocate a ingress identifier for VC [dec] interface [chars] |
The SPA driver is not able to allocate the datapath ingress identifier for the VC/interface specified in the message. This indicates a software error. |
DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
IOSXE_RP_SPA-3-VC_PROV_FAIL |
3-Error |
Failed to provision interface [chars] |
The SPA driver is not able to provision the interface specified in the message. Verify that the SPA hardware is not provisioned above the supported limit. Otherwise this indicates a hardware error. |
DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
IOSXE_RP_SPA-4-CCB_PLAYBACK_ERROR |
4-Warning |
CCB playback failed for slot [dec]. |
The High Availability component for SPA modules failed to synchronize some new state information for the specified slot. |
DDTS_COMPONENT |
"Reload the standby supervisor module to force a fresh bulk " "synchronization. If this error recurs " LOG_STD_ACTION |
|
IOSXE_RP_SPA-4-CCB_RECORD_ERROR |
4-Warning |
CCB record failed for slot [dec]. |
The High Availability component for SPA modules failed to record some new state information for the specified slot. |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-4-IFCFG_CMD_TIMEOUT |
4-Warning |
Interface configuration command 0x[hec] to slot [dec]/[dec] timed out |
The RP sent an configuration command to the slot specified in the error message and received no confirmation for the command. |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-4-IFCFG_DFLT_LIST_ERROR |
4-Warning |
For Interface Configuration command [dec] default retval list search resulted 0x[hec] for slot [dec]/[dec] |
The High Availability component for SPA modules failed to synchronize some new state information for the specified slot. |
DDTS_COMPONENT |
show platform redundancy \ if-config default-retvals |
|
IOSXE_RP_SPA-4-IFCFG_PLAYBACK_ERROR |
4-Warning |
Interface Configuration command [dec] playback failed for slot [dec]/[dec]. |
The High Availability component for SPA modules failed to synchronize some new state information for the specified slot. |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-4-IFCFG_RECORD_ERROR |
4-Warning |
Interface Configuration command [dec] record failed for slot [dec]/[dec]. |
The High Availability component for SPA modules failed to record some new state information for the specified slot. |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-4-INCR_CFG_SYNC_FAIL |
4-Warning |
[chars] incremental running-config sync for [[dec]/[dec]] failed - [chars][dec] |
The specified IOSXE incremental running-config sync failed |
DDTS_COMPONENT |
"Power cycle the redundant supervisor" |
|
IOSXE_RP_SPA-4-IPCFAILED |
4-Warning |
IPC failed to send RPC message to SPA module |
The RP failed to send an RPC message via IPC to a SPA module. |
DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
IOSXE_RP_SPA-4-LCLOG_PARSE_ERR |
4-Warning |
Error parsing logger message: [chars] from subslot [dec]/[dec] |
The SPA module passed down a logger message that could not be parsed. |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-4-LCLOG_TOOLONG |
4-Warning |
Message too long from slot [dec]/[dec]: [dec] bytes |
The SPA module passed down a logger message that is too long for\n\ the RP to handle. |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_RP_SPA-4-SEMAHOG |
4-Warning |
Process [dec] [chars] hogging [chars]! calling proc [dec] [chars] |
- |
- |
- |
|
IOSXE_RP_SPA-4-SPA_CMD_NO_RESP |
4-Warning |
[chars]: No response for interface configuration command [dec] |
A timeout occurred while RP was waiting for a response from line card. This may happen due to line card CPU being too busy to respond to the command. |
DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
IOSXE_RP_SPA-4-SPA_RESP_CMD_ERR |
4-Warning |
[chars]: Received response to interface configuration command [chars] with wrong return value [dec]. |
An internal error occurred while configuring the interface. The configuration may not have succeeded. |
DDTS_COMPONENT |
"Check that the running configuration for the " "interface is correct. If this message is repeatable please " LOG_STD_SH_TECH_ACTION |
|
IOSXE_RP_SPA-4-SPA_RESP_CMD_MISMATCH |
4-Warning |
[chars]: Expecting response to interface configuration command [dec] but received response to command [dec]. |
An internal synchronization error occurred while configuring the interface. The configuration may not have succeeded. |
DDTS_COMPONENT |
"Check that the running configuration for the " "interface is correct. If this message occurred on the standby try " "reloading the standby to ensure that its configuration is in sync. " "If this message is repeatable please " LOG_STD_SH_TECH_ACTION |
|
IOSXE_RP_SPA-6-CARDRELOAD |
6-Information |
Module [dec] reload due to SPA insert in [dec]/[dec]. |
When inserting a SPA on this carrier card the card is reset. |
- |
LOG_STD_NO_ACTION |
|
IOSXE_RP_SPA-6-CTRLRSWITCH |
6-Information |
switching controller type from [chars][dec] to [chars][dec] for subslot [dec]/[dec]. |
When IOSXE-SIP40 is inserted in the slot previously occupied by IOSXE-SIP10 or vice-versa the controller type of the card is overwritten to reflect the current SIP. |
- |
LOG_STD_NO_ACTION |
|
IOSXE_RP_SPA-6-MEDIA_AUTOFAILOVER |
6-Information |
Media Fail over from [chars] to [chars] |
Gige Media Failover. |
- |
"This is inforamtional message Not an error message." "Use 'show interface gig'" "to see the current active media type." |
|
IOSXE_RP_VTYMGT-3-MSGBIPCBUFFER |
3-Error |
Unable to acquire a BIPC buffer of length [dec] for sending messages. |
A message was to be sent by IOS but no BIPC buffer was available. The message to be sent has been discarded and the associated operation failed. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_VTYMGT-3-MSGBIPCERR |
3-Error |
Unable to process received BIPC messages for Vty Management error: [chars] |
An unexpected condition has occurred while IOS was trying to process a received BIPC message for Vty Management. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_VTYMGT-3-MSGBUILDERROR |
3-Error |
Error '[dec]' building TDL Vty Management message '[chars]': [chars] |
An unexpected condition has occurred while IOS is building a TDL response message for Vty Management |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_VTYMGT-3-MSGDISPATCH |
3-Error |
Unable to dispatch received TDL messages for Vty Management |
An unexpected condition has occurred while IOS is trying to dispatch to the TDL message handler functions for received TDL messages for Vty Management. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_VTYMGT-3-MSGDISPATCHNULL |
3-Error |
Received NULL TDL message |
An unexpected condition in which IOS has received a NULL TDL message for Vty Management. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_VTYMGT-3-MSGENQUEUEERROR |
3-Error |
Error queueing TDL Vty Management message '[chars]' |
An unexpected condition has occurred when IOS attempted to queue a TDL response message for Vty Management |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_VTYMGT-3-MSGERROR |
3-Error |
Error '[dec]' handling a received TDL message '[chars]' for Vty Management: [chars] |
An unexpected condition has occurred while IOS is processing a received Vty Management TDL message |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_VTYMGT-3-MSGEXTAPPUPDATE |
3-Error |
Unable to update external application data for line '[dec]' |
An attempt to update the external application for a line failed unexpectedly. The line update failed and if the line number specified is valid the line was released. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_VTYMGT-3-MSGINVALIDFIELDINT |
3-Error |
Invalid field '[chars]' in TDL message '[chars]' received: value '[dec]' for Vty Management |
A message with an invalid field value was received for Vty Management |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_VTYMGT-3-MSGINVALIDFIELDSTR |
3-Error |
Invalid field '[chars]' value '[chars]' in TDL message '[chars]' received for Vty Management |
A message with an invalid field value was received for Vty Management |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_VTYMGT-3-MSGMARSHALERROR |
3-Error |
Error '[dec]' marshaling TDL Vty Management message '[chars]': [chars] |
An unexpected condition has occurred while IOS is marshaling TDL response message for Vty Management |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_VTYMGT-3-MSGMISSINGFIELD |
3-Error |
Missing field '[chars]' in TDL Vty Management message '[chars]' received |
A message missing a required field was received for Vty Management |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_VTYMGT-3-MSGVTYCOUNT |
3-Error |
Invalid vty count [dec] detected on initialization |
Upon initialization the Vty Management subsystem checks that the number of available vtys for the platform is valid. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_VTYMGT-3-MSGVTYSVCINIT |
3-Error |
Unable to initialize the Vty Management service listen port |
The platform IPC services failed to register the Vty Management service's need for a listen port. The Vty Management service will be unable to process requests. IOS services will be unavailable to external access methods. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_RP_VTYMGT-3-SET_ACCESS_FAIL |
3-Error |
Installing LIIN interface access control failed |
This error happens when the Vty Management subsystem failed to set the access control function for the LIIN possibly due to IOS out of memory or corruption. Persistent access features into IOS will not work. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
IOSXE_SCHED-3-AVL_INSERT_FAIL |
3-Error |
Could not insert pid [dec] into process tree |
An avl_insert failed to add a process structure to the ASR1000 |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_SCHED-3-BACKOFF_PRODUCER |
3-Error |
Tx data in message queue '[chars]' appears to have stalled. Producer info: '[chars]' pid [dec] current queue depth: [dec] bytes |
Based upon internal state derived from calls to mcp_queue_produced |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_SCHED-3-CALLED_FROM_INT |
3-Error |
API call incorrectly made from interrupt level |
- |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_SCHED-3-CONTINUE_PRODUCER |
3-Error |
Stall for message queue '[chars]' have been cleared current queue depth: [dec] bytes |
This is to inform that the condition for a message queue which had previously caused back-off of producer processs has been cleared |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_SCHED-3-NEGATIVE_DEPTH |
3-Error |
Queue '[chars]' consumed more than it produced [dec] |
- |
- |
- |
|
IOSXE_SCHED-3-NULLQ |
3-Error |
Invalid API parameter |
An external routine provided by the ASR1000 scheduler was incorrectly called with an invalid NULL pointer. |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_SDWAN_CONFIG-2-MASTER_KEY_FAILED |
2-Critical |
A new type 6 encryption master key has failed to generate |
A type 6 encryption master key was not found on this device. A new key failed to generate. |
cedge-dfp |
LOG_STD_DDTS_TAC_DETAILS |
|
IOSXE_SDWAN_CONFIG-3-MASTER_KEY_MISSING |
3-Error |
Type 6 master key is missing. A new key will be generated. |
- |
cedge-dfp |
LOG_NO_ACTION |
|
IOSXE_SDWAN_CONFIG-4-KEY_ENCRYPT_CHANGE |
4-Warning |
A type 7 key was detected for [chars] which supports type 6. Re-encrypting to type 6. |
A type 7 key was configured. Type 7 usage is discouraged when the component also supports type 6. The type 7 key will be descripted and re-encrypted to type 6. |
cedge-dfp |
LOG_NO_ACTION |
|
IOSXE_SDWAN_CONFIG-4-MASTER_KEY_GENERATED |
4-Warning |
A new type 6 encryption master key has been generated. |
A type 6 encryption master key was not found on this device. A new key has been generated. |
cedge-dfp |
LOG_NO_ACTION |
|
IOSXE_SDWAN_CONFIG-5-MASTER_KEY_PRESENT |
5-Notice |
Type 6 master key is present on the device. |
A type 6 key encryption has been requested by config-manager and an existing type 6 master key will be used for encryption/decryption. |
cedge-dfp |
LOG_NO_ACTION |
|
IOSXE_SERVICE_ENGINE-3-MSGINITFAIL |
3-Error |
Initialization of interface [chars] failed |
The initialization of the interface mentioned in the error message has failed. |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_SERVICE_ENGINE-3-MSGOPENFAIL |
3-Error |
Cannot open interface [chars] [dec] |
During the creation of a Service-Engine interface it is necessary to program the system parameters in the driver. The driver cannot be opened. |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_SERVICE_ENGINE-3-MSGSETFAIL |
3-Error |
Set id on interface [chars] [dec] |
During the creation of a Service-Engine interface it is necessary to program the system parameters in the driver. The failed to accept the programming. |
DDTS_COMPONENT |
LOG_STD_ACTION |
|
IOSXE_SERVICE_ENGINE-5-SRVENGNOTAVL |
5-Notice |
Service Engine Not Available |
The Service Engine Not Available. |
- |
LOG_STD_NO_ACTION |
|
IOSXE_SIP_SPA-3-APS_CFG_FAIL |
3-Error |
Failed to configure APS on [chars]: [chars]. |
The SPA driver failed to configure APS on an interface. |
asr1k-spa-infra |
LOG_STD_ACTION |
|
IOSXE_SIP_SPA-3-APS_PGP_FAIL |
3-Error |
APS PGP Message send failed toslot/tobay [dec]: [dec]. |
The SPA ETHER process is not able to write to ezman as ezman is blocked for writes. Copy the error message exactly as it appears and report it to your technical support representative. |
asr1k-spa-infra |
LOG_STD_ACTION |
|
IOSXE_SIP_SPA-3-ASR1000IPCALLOCFAIL |
3-Error |
Failed to allocate Common IPC buffer [chars] |
The Carrier Card failed to allocate a buffer for\n\ communication with the Route Processor. |
asr1k-spa-infra |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
IOSXE_SIP_SPA-3-BAD_IFCOMTYPE |
3-Error |
Bad ifcom message type=[dec] |
- |
asr1k-spa-infra |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
IOSXE_SIP_SPA-3-BADMALUCMD |
3-Error |
Unsupported MALU command [dec] arg=[hex] pascb=[hex] |
- |
asr1k-spa-infra |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
IOSXE_SIP_SPA-3-BADMALUCMD2 |
3-Error |
Unsupported MALU cmd/arg0=0x%04x%04x arg1arg2=0x%04x%04x hwidb=[chars] |
- |
asr1k-spa-infra |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
IOSXE_SIP_SPA-3-C2W_MAIN_INIT_FAIL |
3-Error |
Failed to initialize SPA main c2w bus for subslot [dec] status = [dec] |
The SPA driver is not able to initialize SPA main c2w. This indicates a hardware error. |
asr1k-spa-infra |
LOG_STD_NO_ACTION |
|
IOSXE_SIP_SPA-3-CMDNOINT |
3-Error |
HWIDB Null for command [dec] port [hex] |
The Route Processor passed down a port number that is unknown on the\n\ carrier card. |
asr1k-spa-infra |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
IOSXE_SIP_SPA-3-DEVICE_ERROR |
3-Error |
subSlot [dec] spatype 0x[hec]. Device error: [chars] |
An error related to a device on the SPA is detected. |
asr1k-spa-infra |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SIP_SPA-3-EFC_CHAN_ERR |
3-Error |
EFC error - interface [chars] vc [dec] anyphy [dec] err_code [dec] : [chars] |
Failed to configure efc channel/parameters |
asr1k-spa-infra |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance " LOG_STD_ACTION |
|
IOSXE_SIP_SPA-3-EFC_FC_MAP_FAIL |
3-Error |
Failed to update EFC flow control identifier for interface [chars] status = [dec] |
The SPA driver is not able to update the datapath EFC flow control identifier for the interface specified in the message. This indicates a hardware error. |
asr1k-spa-infra |
LOG_STD_NO_ACTION |
|
IOSXE_SIP_SPA-3-EFC_PROV_FAIL |
3-Error |
Failed to provision EFC for interface [chars] status = [dec] |
The SPA driver is not able to provision EFC for the interface specified in the message. This indicates a hardware error. |
asr1k-spa-infra |
LOG_STD_NO_ACTION |
|
IOSXE_SIP_SPA-3-EFC_UNPROV_FAIL |
3-Error |
Failed to unprovision EFC for VC [chars] status = [dec] |
The SPA driver is not able to unprovision EFC for the interface specified in the message. This indicates a hardware error. |
asr1k-spa-infra |
LOG_STD_NO_ACTION |
|
IOSXE_SIP_SPA-3-FAST_NOTIFY_ERROR |
3-Error |
Failed to send fast notification to [chars] for [chars] [chars]. |
The SPA driver failed to deliver a fast notification. |
asr1k-spa-infra |
LOG_STD_ACTION |
|
IOSXE_SIP_SPA-3-FCI_NOT_SET |
3-Error |
Bay [dec] - FCI type not set |
An FCI type of zero was detected |
asr1k-spa-infra |
LOG_STD_ACTION |
|
IOSXE_SIP_SPA-3-FRR_CFG_FAIL |
3-Error |
Failed to configure fast reroute on [chars]: [chars]. |
The SPA driver failed to configure fast rerouting on an interface. |
asr1k-spa-infra |
LOG_STD_ACTION |
|
IOSXE_SIP_SPA-3-HWIDB_FAILURE |
3-Error |
Creation: port [dec] vc [dec] |
Failed to create a hwidb. |
asr1k-spa-infra |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SIP_SPA-3-INVALID_ANYPHY |
3-Error |
Bay [dec] - Invalid anyphy number [dec] for vc [dec] |
Interface has invalid anyphy mumber |
asr1k-spa-infra |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance open a case with the Technical Assistance " "Center via the Internet at " " http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a 'show tech-support' to " "your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
IOSXE_SIP_SPA-3-INVALID_IF |
3-Error |
Attempted to access HWIDB for port [dec] on slot [dec] subSlot [dec] |
The ASR1000 attempted to access the HWIDB associated with\n\ a non-existent port. |
asr1k-spa-infra |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
IOSXE_SIP_SPA-3-IPCALLOCFAIL |
3-Error |
Failed to allocate IPC buffer [chars] |
The SPA failed to allocate a buffer for communication with\n\ the Route Processor ASR1000-RP. |
asr1k-spa-infra |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
IOSXE_SIP_SPA-3-IPCPORT |
3-Error |
Failed to [chars] IPC port '[chars]' error [chars] |
The Linecard failed to create a port for\n\ communication with the Route Processor ASR1000-RP. |
asr1k-spa-infra |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
IOSXE_SIP_SPA-3-IPCPORT |
3-Error |
Failed to [chars] IPC port '[chars]' error [chars] |
The Linecard failed to create a port for\n\ communication with the Route Processor ASR1000-RP. |
asr1k-spa-infra |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
IOSXE_SIP_SPA-3-IPCPORTFAIL |
3-Error |
Failed to open IPC port '[chars]' [chars] with error [chars] |
The RP failed to open a port for communication with a SPA\n\ module. |
asr1k-spa-infra |
LOG_STD_ACTION |
|
IOSXE_SIP_SPA-3-IPCPORTFAIL |
3-Error |
Failed to open IPC port '[chars]' [chars] with error [chars] |
The RP failed to open a port for communication with a SPA\n\ module. |
asr1k-spa-infra |
LOG_STD_ACTION |
|
IOSXE_SIP_SPA-3-IPCSENDFAIL |
3-Error |
Failed to send IPC message [chars] |
The Linecard failed to send a message to the\n\ Route Processor ASR1000-RP. |
asr1k-spa-infra |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
IOSXE_SIP_SPA-3-IPCSENDFAIL |
3-Error |
Failed to send IPC message [chars] |
The Linecard failed to send a message to the\n\ Route Processor ASR1000-RP. |
asr1k-spa-infra |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
IOSXE_SIP_SPA-3-ISR_RC_ERROR |
3-Error |
ISR return code out of range. rc=[dec] |
The ISR error return code is out of range. |
asr1k-spa-infra |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SIP_SPA-3-LINKREC_ERROR |
3-Error |
Link record error - Bay [dec] vc [dec] error code [dec] |
Error processing link record structure |
asr1k-spa-infra |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance open a case with the Technical Assistance " "Center via the Internet at " " http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a 'show tech-support' to " "your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
IOSXE_SIP_SPA-3-LVLTRTOOBIG |
3-Error |
Loveletter length exceeds max [dec] bytes |
The ASR1000-SIP line card attempted to send a large message to the\n\ Route Processor ASR1000-RP. |
asr1k-spa-infra |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
IOSXE_SIP_SPA-3-MESSAGE_ERROR |
3-Error |
Bay [dec]: [chars] |
An unexpected error has occurred. |
asr1k-spa-infra |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance " LOG_STD_ACTION |
|
IOSXE_SIP_SPA-3-NETCLK_FAIL |
3-Error |
Failed to [chars] SPA reference clock on [chars] |
The SPA driver is not able to correctly configure the SPA reference clock on the specified interface. This indicates a hardware error. |
asr1k-spa-infra |
LOG_STD_NO_ACTION |
|
IOSXE_SIP_SPA-3-NODISPATCH |
3-Error |
Dispatch vector Null cmd=[dec] dintf=[dec] |
No command dispatch vector was found for the specified interface. |
asr1k-spa-infra |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
IOSXE_SIP_SPA-3-POWER |
3-Error |
Bay [dec] 12V power is [chars] |
SPA 12V power fault indicator |
asr1k-spa-infra |
LOG_STD_ACTION |
|
IOSXE_SIP_SPA-3-SONET_CLOCK_FAILED |
3-Error |
SPA Sonet clock has failed status = 0x%08x |
The SPA SONET clock has failed. SPAs that rely on the SPA SONET clock for proper operation such as POS and ATM will be affected. |
asr1k-spa-infra |
"If the SPA Sonet clock does not recover perform an " "OIR. "LOG_STD_RECUR_ACTION |
|
IOSXE_SIP_SPA-3-SONET_CLOCK_RECOVERED |
3-Error |
SPA Sonet clock has recovered status = 0x%08x |
SPA Sonet clock has recovered |
asr1k-spa-infra |
LOG_STD_NO_ACTION |
|
IOSXE_SIP_SPA-3-SPA_CTRL_EFC_CONFIG_FAILURE |
3-Error |
Subslot spa controller EFC configuration failure error [dec] |
Failed to configure SPA controller EFC |
asr1k-spa-infra |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance " LOG_STD_ACTION |
|
IOSXE_SIP_SPA-3-SPA_CTRL_INIT_FAILURE |
3-Error |
Subslot [dec] spa controller initialisation failure error [dec] |
Failed to initialise SPA controller |
asr1k-spa-infra |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance " LOG_STD_ACTION |
|
IOSXE_SIP_SPA-3-SPA_INTF_ID_CC_ALLOC_FAILED |
3-Error |
Failed to allocate interface identifiers for SPA [chars] |
Failed to get CC buffer and flow control identifiers for the SPA in the specified subslot Traffic cannot flow through the SPA under this failure condition. This can happen if the system runs out of available identifiers. |
asr1k-spa-infra |
"Try to reduce the number of interfaces" "configured in the system either by physically removing the SPAs" "or by changing the system configuration" |
|
IOSXE_SIP_SPA-3-SPI4_CONFIG_FAILURE |
3-Error |
Bay [dec] spi4 configuration failure error [dec] |
Failed to configure SPI4 interface |
asr1k-spa-infra |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance " LOG_STD_ACTION |
|
IOSXE_SIP_SPA-3-SPI4_INIT_FAILURE |
3-Error |
Bay [dec] initialization failure |
Failed to create SPI4 subblock |
asr1k-spa-infra |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance " LOG_STD_ACTION |
|
IOSXE_SIP_SPA-3-SPI4_NOTSYNC |
3-Error |
[chars]: Can not synchronize SPI4 bus host: src [chars]in sync sink [chars]in sync spa: src [chars]in sync sink [chars]in sync. |
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. |
- |
"Ensure that the SPA is properly seated " "in its subslot and reseat it if required." |
|
IOSXE_SIP_SPA-4-MAX_BANDWIDTH |
4-Warning |
Total SPA bandwidth exceeds line card capacity of %lu Mbps |
The total bandwidth of SPAs exceeds the rated capacity of this line card. |
asr1k-spa-infra |
"Refer to the line card guidelines for the maximum allowed" "aggregated SPA bandwidth for the line card" |
|
IOSXE_SIP_SPA-4-MAX_BANDWIDTH_NS |
4-Warning |
Total SPA bandwidth exceeds line card capacity full utilization of installed SPA interfaces is not supported |
The total bandwidth of SPAs exceeds the rated capacity of this line card. |
asr1k-spa-infra |
"Refer to the line card guidelines for the maximum allowed" "aggregated SPA bandwidth for the line card" |
|
IOSXE_SIP_SPA-4-SPABUS |
4-Warning |
Subslot [dec] [chars] SPA BUS access failed. timeout=[dec] err=[dec] par=[dec] err_c=0x[hec] addr=0x%08x data =0x[hec] |
SPABUS has reported an error. |
asr1k-spa-infra |
LOG_STD_ACTION |
|
IOSXE_SIP_SPA-4-SPABUS2 |
4-Warning |
Subslot [dec] SPA BUS access failed. No SPA present error |
SPABUS has reported an error. |
asr1k-spa-infra |
LOG_STD_ACTION |
|
IOSXE_SIP_SPA-6-LOGGERMSGTOOBIG |
6-Information |
Logger message length [dec] bytes exceeds the maximum allowed size |
The carrier card attempted to send a large message to the Route Processor |
asr1k-spa-infra |
LOG_STD_ACTION |
|
IOSXE_SIP_SPA-6-OIR |
6-Information |
Bay [dec] [chars] changed to [chars] |
SPA OIR Sequence |
asr1k-spa-infra |
LOG_STD_NO_ACTION |
|
IOSXE_SMART_AGENT-3-NOTIFY_NOT_AUTHORIZED |
3-Error |
Requested count [dec] for license level [chars] is in 'not authorized' state. |
Authorization Code needs to be installed using 'license smart reservation install' CLI |
iosxe-smart-agent |
- |
|
IOSXE_SMART_AGENT-3-NOTIFY_OOC |
3-Error |
Pool is out of compliance |
This pool is Out Of Compliance |
iosxe-smart-agent |
"The pool is out of compliance. Customer needs" "to update his license pool" |
|
IOSXE_SMART_AGENT-6-NOTIFY_DISABLED |
6-Information |
Smart Licensing is now Disabled |
Smart Licensing is Disabled |
iosxe-smart-agent |
- |
|
IOSXE_SMART_AGENT-6-NOTIFY_ENABLED |
6-Information |
Smart Licensing is now Enabled |
Smart Licensing is Enabled |
iosxe-smart-agent |
- |
|
IOSXE_SMART_AGENT-6-NOTIFY_GRACEWILLEXPIRE |
6-Information |
Grace Period will Expire |
Grace Period will expire |
iosxe-smart-agent |
- |
|
IOSXE_SMART_AGENT-6-NOTIFY_InC |
6-Information |
Pool is now in Compliance |
Smart Licensing Pool in Compliance |
iosxe-smart-agent |
- |
|
IOSXE_SMART_AGENT-6-STANDBY_NOT_AUTHORIZED |
6-Information |
Standby is in 'not authorized' state for license [chars] |
Authorization Code needs to be installed using 'license smart reservation install' CLI on standby |
iosxe-smart-agent |
- |
|
IOSXE_SPA-3-ABANDON_SPA_CONFIGURATION |
3-Error |
Abandon configuration for subslot [dec]/[dec] the SPA type[dec] is NOT match |
Abandon SPA configuration. |
DDTS_COMPONENT |
"Please check the startup configuration use \"no " "card\" command to override wrong card configuration and update card " "type." |
|
IOSXE_SPA-3-CREATE_TDLH_FAILURE |
3-Error |
Failed to create SPA [dec]/[dec] handle |
Failed to create message handle for SPA communication. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-CREATE_TDLMSG_FAILURE |
3-Error |
Failed to create [chars] message for [chars]. |
Failed to create/allocate necessary TDL message for SPA communication. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-CREATION_FAILURE |
3-Error |
slot=[dec] subslot=[dec] spa_type=0x[hec] lc_type=0x[hec]. |
Failed to create a SPA object. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-DIAG_CONFIG |
3-Error |
[chars] did not complete [dec]/[dec] |
An error has occured during diagnostic test. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-DISPATCH_INIT_TDLH_FAILURE |
3-Error |
Failed to initialize dispatch path for SPA [dec]/[dec] handle |
Failed to initialize dispatch path handle for SPA communication. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-DOMAIN_TDLH_FAILURE |
3-Error |
[chars] rc = [dec] |
Failed to bind message handle for SPA communication. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-INVALID_CPU_NUM |
3-Error |
cpu= [dec] max cpu = [dec] |
An invalid CPU number is specified in one of the internal APIs. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-INVALID_DATA_INSTANCE |
3-Error |
interface type [chars] slot [dec] port [dec] vc [dec] : [chars] |
Data required to support the interface is not available. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-INVALID_DB_NUM |
3-Error |
db = [dec] max db = [dec] db intf = [dec] max db intf = [dec] |
An invalid daughter board number is specified in one of the internal APIs. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-INVALID_HANDLE |
3-Error |
Failed to get a valid IPC handle for type [dec] slot [dec] subslot [dec]. |
The client handle was found to be NULL for the given type/slot/subslot. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-INVALID_IF_INDEX |
3-Error |
index= [dec] spaType=0x[hec] slot [dec] subSlot [dec] slotunit [dec] vc [dec] |
Index for the interface is not valid. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-INVALID_INDX_RANGE |
3-Error |
index1= [dec] index2= [dec] maxIndex= [dec] |
An invalid index range is specified in one of the internal APIs. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-INVALID_RP_SLOT_NUM |
3-Error |
slot= [dec] max slot = [dec] |
An invalid RP slot number is specified in one of the internal APIs. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-INVALID_SLOT_NUM |
3-Error |
slot= [dec] max slot = [dec] |
An invalid slot number is specified in one of the internal APIs. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-INVALID_SLOTUNIT_NUM |
3-Error |
cardwide-port = [dec] max cardwide-port = [dec] |
An invalid cardwide-port number is specified in one of the internal APIs. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-INVALID_SPA_TDL_CCAPI_USAGE |
3-Error |
- |
Incorrect usage of an internal API that should only be used on CC. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-INVALID_SUBSLOT_NUM |
3-Error |
subslot= [dec] max subslot = [dec] |
An invalid subslot number is specified in one of the internal APIs. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-IPC_FAILURE |
3-Error |
IPC failure while [chars] |
An error has occurred while prepareing or sending an IPC message. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-MEM_ALLOC_ERROR |
3-Error |
[chars] |
Memory allocation error. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-NULL_BAY_PTR |
3-Error |
- |
Pointer to SPA bay is NULL. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-NULL_SPA_PTR |
3-Error |
- |
Pointer to a SPA object is NULL. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-NULL_VFT |
3-Error |
[chars] virtual function table is not initialized. spaType=0x[hec] |
A required function table is not initialized |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-NULL_VFUNC |
3-Error |
[chars] vector is not initialized. spaType=0x[hec] |
A required function vector is not initialized |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-POWER_CYCLE |
3-Error |
[chars] occurred on Shared Port Adapter [dec]/[dec] |
An error has occurred which will cause the \n\ Shared Port Adapter to be power cycled |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-SENDCFGFAIL |
3-Error |
Failed to send configuration for [chars] to carrier-card for subslot=[dec]/[dec] |
Sending configuration failed. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-SETUP_TDLH_FAILURE |
3-Error |
Failed to set the alloc/free handler for SPA [dec]/[dec] handle |
Failed to set the alloc/free handler for SPA communication. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-SPA_CREATION_FAILURE |
3-Error |
slot=[dec] subslot=[dec] PID=[chars] lc_type=0x[hec]. |
Failed to create a SPA object. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-SPA_SETUP_FAILURE |
3-Error |
Failed to properly setup for SPA communication on slot [dec] subslot [dec]. |
Discovery of the linux interface used to communicate with a SPA failed |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-3-UNSUPPORTED_DATA |
3-Error |
Data conversion error [chars] 0x%X |
An internal software error has occured when converting the data specified in the message from one representation to another. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-4-COMMUNICATION_DISCONNECTED |
4-Warning |
Communication with IM in [dec]/[dec] stalled. Retrying. IM will reboot if situation persists |
Retransmit IPC communication request between IOS and IOMD. |
DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
IOSXE_SPA-4-COMMUNICATION_ESTABLISHED |
4-Warning |
Communication with IM in [dec]/[dec] restored. |
IPC communication between IOS and specified IM has been restored. |
DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
IOSXE_SPA-6-DUAL_RATE_CHANGE |
6-Information |
[chars]: [chars] |
Change in rate of the link. |
DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
IOSXE_SPA-6-TDLMSG_INCOMPATIBLE |
6-Information |
Failed to copy message [chars] to buffer not allowed for current domain. |
Failure to marshal a message indicates an incompatibility with the intended recipient. |
iosxe-spa-infra |
LOG_STD_SH_TECH_ACTION |
|
IOSXE_SPA-6-UPDOWN |
6-Information |
Interface [chars] link down due to [chars] |
Ethernet link is down due to remote/local fault. |
DDTS_COMPONENT |
"Replace the faulty cable." |
|
IOSXE_SPA-6-UPDOWN1 |
6-Information |
Interface [chars] link down due to [chars] [chars][dec].[dec] dbm |
Ethernet link is down due to mac LF/RF/phy line/host side fault. Optics Rx power is ok/low/hi |
DDTS_COMPONENT |
"Debug mac/phy/optics block" |
|
IOSXE_SPA-6-UPDOWN2 |
6-Information |
Interface [chars] link down due to [chars] [chars][dec] |
Ethernet link is down due to macLF/RF/phy line/hostside fault. Dom is not supported by the optics |
DDTS_COMPONENT |
"Debug phy/optics block" |
|
IOSXE_SPA-6-UPDOWN3 |
6-Information |
Interface [chars] link down due to [chars] ln0:[chars][dec].[dec] dbmln1:[chars][dec].[dec] dbmln2:[chars][dec].[dec] dbmln3:[chars][dec].[dec] dbm |
Ethernet link is down due to macLF/RF/phy line/host side fault. Optics Rx power lane is ok/low/high. |
DDTS_COMPONENT |
"Debug phy/optics block" |
|
IOSXE_SPA-6-UPDOWN4 |
6-Information |
Interface [chars] link down due to [chars] -40dbm |
Ethernet link is down due to macLF/RF/phy line/host side fault.Optics Rx power is zero. |
DDTS_COMPONENT |
"Debug mac/phy/optics block" |
|
IOSXE_SPA-6-UPDOWN5 |
6-Information |
Interface [chars] link down due to [chars] ln0:[chars][dec].[dec] dbmln1:[chars][dec].[dec] dbmln2:[chars][dec].[dec] dbmln3:[chars][dec].[dec] dbmln4:[chars][dec].[dec] dbmln5:[chars][dec].[dec] dbmln6:[chars][dec].[dec] dbmln7:[chars][dec].[dec] dbmln8:[chars][dec].[dec] dbmln9:[chars][dec].[dec] dbm |
Ethernet link is down due to macLF/RF/phy line/host side fault. Optics Rx power lane is ok/low/high. |
DDTS_COMPONENT |
"Debug phy/optics block" |
|
IOSXE_SUBSYS_EX-2-SUBSYS_EX_INIT_FAIL |
2-Critical |
Subsys exclusion init failed. Invalid subsys list. |
Fail to initialize excluded subsystems to NULL. \n\ an abnormal condition |
DDTS_COMPONENT |
"This message means a software error had happened. \n" "The list of subsystems to be removed is not initialized. \n" "\n\n When reporting this message copy the message text exactly as\n\ it appears include the stack trace and report to your technical\n\ support representative" |
|
IOSXE_SUBSYS_EX-2-SUBSYS_LIST_NOT_TERMINATED |
2-Critical |
Subsystems in exclusion list is not terminated correctly. |
The subsystem exclusion list is not termianted \ by a NULL entry. \n It is \ an abnormal condition |
DDTS_COMPONENT |
"This message may be related to a memory corruption or hardware issue.\n\ \n\n When reporting this message copy the message text exactly as\n\ it appears include the stack trace and report to your technical\n\ support representative" |
|
IOSXE_SUBSYS_EX-2-SUBSYS_REMOVE_FAIL |
2-Critical |
Unable to remove excluded subsystems. |
Fail to remove excluded subsystems. \n\ an abnormal condition |
DDTS_COMPONENT |
"This message may be related to a memory corruption. \n" "\n\n When reporting this message copy the message text exactly as\n\ it appears include the stack trace and report to your technical\n\ support representative" |
|
IOSXE_SYS_INFRA-3-BIPC_CREATE_FAIL |
3-Error |
Failed to open IPC port '[chars]' for service '[chars]' with error [chars]. |
BIPC connect failed |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_SYS_INFRA-3-BIPC_DISCONNECT_FAIL |
3-Error |
Failed to disconnect IPC port '[chars]' for service '[chars]' with error [chars]. |
BIPC disconnect failed |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_SYS_INFRA-3-EFP_EPOLL_WAIT |
3-Error |
Fastpath thread epoll wait failed errno [dec] |
Fastpath epoll wait failed |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_SYS_INFRA-3-EFP_EVDISPATCH |
3-Error |
Fastpath thread event dispatch failed ev_ret [dec] errno [dec] |
fastpath thread event dispatch failed |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_SYS_INFRA-3-EFP_EVGETNEXT |
3-Error |
Fastpath thread get next event failed ev_ret [dec] errno [dec] |
Fastpath thread get next event failed |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_SYS_INFRA-3-EFP_IPC_EPOLL_CTL_FAILED |
3-Error |
Fastpath thread [chars] [chars] for IPC channel [chars] ipc id [dec] ipc fd [dec] seqnum [dec] failed efd [dec] errno [dec] |
Fastpath epoll_ctl operation for an IPC channel failed |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_SYS_INFRA-3-EFP_IPC_EPOLL_NO_IPC_ENTRY |
3-Error |
IPC entry not found for ipc fd [dec] seq [dec] events 0x[hec] while processing [chars] from epoll fd [dec] |
Fastpath failed to find IPC entry after epoll_wait |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_SYS_INFRA-3-EFP_TOP_EPOLL_CTL_FAILED |
3-Error |
Fastpath thread top level efd epoll [chars] failed fd [dec] errno [dec] |
Fastpath top level efd epoll_ctl operation failed |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_SYS_INFRA-3-EIOS_EVDISPATCH |
3-Error |
IOS scheduler event dispatch failed ev_ret [dec] errno [dec] |
IOS scheduler event dispatch failed |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_SYS_INFRA-3-EIOS_EVGETNEXT |
3-Error |
IOS scheduler get next event failed ev_ret [dec] errno [dec] |
IOS scheduler get next event failed |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_SYS_INFRA-3-EIOS_POLL |
3-Error |
IOS thread poll on event lib and wakeup fds failed errno [dec] |
IOS thread poll on event lib and wakeup fds failed |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_SYS_INFRA-3-EOBC_SOCK |
3-Error |
Socket event for [chars] |
An internal socket level event has returned an error which\n\ is indicated. This may have been the result of a bind\n\ peek receive or send operation with respect to the EOBC\n\ interface listed. |
iosxe-iosd-infra |
"show eobc\n\ show platform software\n\ infrastructure bipc" |
|
IOSXE_SYS_INFRA-3-EREAD_EVENT_FD |
3-Error |
[chars] read from wakeup fd failed errno [dec] |
A thread reading from its wakeup fd failed |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_SYS_INFRA-3-EVLIB_EPOLL_ARGS |
3-Error |
evGetEpollArgs returned fd [dec] |
Evlib retuned a huge FD value that IOS can not handle. |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_SYS_INFRA-3-EWRITE_EVENT_FD |
3-Error |
Write to [chars] wakeup fd failed errno [dec] current signal/wakeup cnt: %llu/%llu |
Trigering a thread by writing to its wakeup fd failed |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_SYS_INFRA-4-BIPC_CLEAR_CONN |
4-Warning |
IPC channel fd [dec] seq_num [dec] for service '[chars]' cleared by user |
BIPC disconnect requested by an user with clear command |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_SYS_INFRA-4-BIPC_RX_IN_APPL_THRESHOLD |
4-Warning |
Number of IPC messages held in the application reached the \n\ maximum channel threshold. IPC channel '[chars]': \n\ ipc_ctl_id [dec] ipc_fd [dec] seq_num [dec] curr IPC msg hel in appl [dec] |
- |
- |
- |
|
IOSXE_SYS_INFRA-4-BIPC_TX_Q_THRESHOLD |
4-Warning |
BIPC transmit queue threshold reached for the channel '[chars]':\n\ ipc_ctl_id [dec] ipc_fd [dec] seq_num [dec] Tx Q size [dec] |
- |
- |
- |
|
IOSXE_SYS_INFRA-6-BIPC_CREATE |
6-Information |
bipc connect succeeded for [chars] ipc_ctl_id [dec] ipc_fd [dec] seq [dec] |
BIPC connect succeeded |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_SYS_INFRA-6-BIPC_DISCONNECT |
6-Information |
disconnect by application for [chars] bring down IPC |
BIPC disconnect requested by an application |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_SYS_INFRA-6-BIPC_READ_ERR |
6-Information |
connection read error from [chars] rc [dec] bring down IPC id [dec] for fd [dec] seq [dec] |
BIPC error during IPC read |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_SYS_INFRA-6-BIPC_READBUF_ERR |
6-Information |
process receive buffer error from [chars] rc [dec] bring down IPC |
BIPC error during IPC read from buffer |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_SYS_INFRA-6-BIPC_WRITE_ERR |
6-Information |
write bipc error for [chars] rc [dec] bring down IPC |
BIPC error during IPC read |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_SYS_INFRA-6-EOBC_ADDR_CACHE |
6-Information |
EOBC ip-table cache: [chars] |
Unable to setup internal address for eobc communication |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_SYS_INFRA-6-FP_IPC_DISCONNECT |
6-Information |
IPC channel disconnect for [chars] ipc_ctl_id [dec] fd [dec] seq_num [dec] loc [chars] err [dec] [chars] |
An IPC channel in fastpath is terminated |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_SYS_INFRA-6-IOS_FREE_IPC_CTL |
6-Information |
IPC control blk free: name [chars] ipc_ctl_id [dec] refcount [dec] |
An IPC control block is freed |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_SYS_INFRA-6-IOS_IPC_CTL_DESTROY |
6-Information |
IPC control blk destroy: name [chars] ipc_ctl_id [dec] refcout [dec] need_free [dec] |
An IPC control block is requested to be destroyed |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_THROUGHPUT-3-CONF_FAILED |
3-Error |
Configuration failed. Installed license does not support the throughput level. Please install the valid license |
An error occurred when the throughput configuration was attempted. |
iosxe-csl |
- |
|
IOSXE_THROUGHPUT-3-EULA_NOT_ACCEPTED |
3-Error |
The EULA has to be accepted prior to throughput configuration. |
Users need to accept EULA to activate the license |
iosxe-csl |
"Accept EULA for throughput license" |
|
IOSXE_THROUGHPUT-3-INVALID_CONFIG |
3-Error |
No valid license found for the configured throughput level: [chars] kbps |
Users has the boot up throughput set to non-default level without having the valid license. |
iosxe-csl |
"Install valid throughput license" |
|
IOSXE_THROUGHPUT-3-INVALID_LEVEL |
3-Error |
An invalid throughput level: [chars] kbps was selected. |
The configured throughput level is unknown |
iosxe-csl |
- |
|
IOSXE_THROUGHPUT-3-SETUP_FAILED |
3-Error |
Throughput level setup failed. Boot up will be at the default throughput |
An error occurred when licensing tried to setup the througput |
iosxe-csl |
- |
|
IOSXE_THROUGHPUT-6-LEVEL |
6-Information |
Throughput level has been set to [dec]00000 kbps |
Throughput level has been set to a number |
iosxe-csl |
- |
|
IOSXE_TIMESTAMP_ENGINE-3-TSU_ERR |
3-Error |
An unexpected condition has occurred at module [chars] |
An unexpected condition has occurred at the Interface Module TSU. |
asr900-ptp |
LOG_STD_ACTION |
|
IOSXE_TIMESTAMP_ENGINE-4-ERROR |
4-Warning |
NULL |
An unexpected condition has occurred. |
asr900-ptp |
LOG_STD_ACTION |
|
IOSXE_UEA-3-INVALID_EEPROM |
3-Error |
MAC count from BP is supposed to be 512 for NCS. Actual MAC count[dec] |
For UEA NCS platforms MAC count must be 512 |
uea-systems |
"Please program the EEPROM to correct MAC count" |
|
IOSXE_USB-3-ESHOW_USB |
3-Error |
Internal Error locating database for USB Devices. |
The mcp_usb_devices is incorrect and needs to be changed |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
IOSXE_UTD-2-VERSION_UNSUPPORTED |
2-Critical |
UTD package version \[chars]\ is not supported recommended version is \[chars]\ |
The UTD package version does not match the required UTD version embedded in this IOS-XE version. This is an unsupported configuration and may behave unexpectedly. |
iosxe-utd |
LOG_STD_ACTION |
|
IOSXE_UTD-3-ALLOC |
3-Error |
Failed to allocate message |
When attempting to program the dataplane there was not enough memory to allocate the message. |
iosxe-utd |
LOG_STD_ACTION |
|
IOSXE_UTD-3-MESSAGE |
3-Error |
Failed to send message |
When the message was being prepared for sending to the data plane there was an error. |
iosxe-utd |
LOG_STD_ACTION |
|
IOSXE_UTD-4-MT_CONFIG_DOWNLOAD |
4-Warning |
UTD MT configuration download has [chars] |
In UTD multitenancy mode the configuration download to the container can take a while. Please be patient. |
iosxe-utd |
LOG_STD_ACTION |
|
IOSXE_UTD-4-MT_CONTAINER_MESSAGE_NAK |
4-Warning |
Container responded to UTD message with an error: [dec] |
The container rejected the UTD message |
iosxe-utd |
LOG_STD_ACTION |
|
IOSXE_UTD-4-MT_CONTAINER_MESSAGE_TIMEOUT |
4-Warning |
UTD message sent to the container has timed out |
The UTD message sent to the container has timed out. |
iosxe-utd |
LOG_STD_ACTION |
|
IOSXE_UTD-4-MT_CONTAINER_SESSION_TIMEOUT |
4-Warning |
UTD container download has timed out |
The container did not respond with an up/down status before the session timed out. |
iosxe-utd |
LOG_STD_ACTION |
|
IOSXE_UTD-4-MT_CONTAINER_STATUS_DOWN |
4-Warning |
UTD poll: container status is DOWN |
The container sent a down status to the poll message |
iosxe-utd |
LOG_STD_ACTION |
|
IOSXE_UTD-4-OVA_DEPRECATION |
4-Warning |
The UTD OVA is being deprecated in an upcoming release. Please migrate to IOX to use the UTD TAR |
The UTD OVA is being deprecated in an upcoming release. Support for the virtual-service command suite will end. To use UTD going forward please migrate to IOX infrastructure. See the 'Migrating to IOx Container' section on the following link for more information: http://cs.co/UtdSnortIPS |
iosxe-utd |
LOG_STD_ACTION |
|
IOSXE_UTD-4-SIG_UPDATE_CFG |
4-Warning |
UTD signature updates have been configured - A brief service interruption at the time of update is expected |
The UTD service will be restarted if a new signature package is found. During this time if fail-close has been configured recommended traffic that would be inspected by |
iosxe-utd |
LOG_STD_ACTION |
|
IOSXE_UTD-4-SIG_UPDATE_CFG_INCOMPLETE |
4-Warning |
UTD signature update configuration is incomplete |
UTD signature updates have been partially configured. Both the signature update server and occur-at frequency are required. |
iosxe-utd |
LOG_STD_ACTION |
|
IOSXE_UTD-4-SIG_UPDATE_EXEC |
4-Warning |
UTD signature update has been executed - A brief service interruption is expected |
The UTD service will be restarted if a new signature package is found. During this time if fail-close has been configured recommended traffic that would be inspected by |
iosxe-utd |
LOG_STD_ACTION |
|
IOSXE_UTD-4-VERSION_INCOMPATIBILITY |
4-Warning |
UTD package version \[chars]\ does not match recommended UTD package version \[chars]\ |
The UTD package version does not match the recommended UTD package version embedded in this IOS-XE version. |
iosxe-utd |
LOG_STD_ACTION |
|
IOSXE_VMAN-3-MSGDISPATCH |
3-Error |
Unable to dispatch received TDL message from Virt-manager |
An unexpected condition has occurred while IOS was trying to dispatch a TDL message received from Virt-manager. |
vman |
LOG_STD_ACTION |
|
IOSXE_VMAN-3-MSGINITFAIL |
3-Error |
Failed to initialize required Virt-manager resource: [chars] |
During the initialization of the resources required by Virt-manager a failure occurred. This has prevented virtual services from being activated. |
vman |
LOG_STD_ACTION |
|
IOSXE_VMAN-3-RSPMSGHDLR |
3-Error |
Failed to deliver response message: [chars] |
An unexpected condition has occurred while IOS was trying to deliver a response message to a virtual service received from Virt-manager. |
vman |
LOG_STD_ACTION |
|
IOSXE_WCCP-4-ACELIMIT |
4-Warning |
Too many ACEs in MASK ACL please switch to Hash mode |
Mask merged ACL generate too many ACEs. |
asr1k-wccp |
"show ip access-lists" |
|
IOSXE_WCCP-4-BADACE |
4-Warning |
Access list contains invalid ace |
An unexpected condition has occurred which is due to an invalid\n\ statement in the access list structure. |
asr1k-wccp |
"show ip access-lists" |
|
IOSXE_WCCP-4-NOACL |
4-Warning |
Access list is null |
An unexpected condition has occurred which is due to the absence of\n\ an access list structure. |
asr1k-wccp |
"show ip access-lists" |
|
IOSXE_WCCP-4-NOINPUT |
4-Warning |
NULL input [chars] |
An unexpected condition has occurred which is due to the NULL value\n\ of the input parameter. |
asr1k-wccp |
"show ip wccp" |
|
IOSXE_WCCP-4-NOINTF |
4-Warning |
No [chars] interface info for Service Group [dec] [dec] [dec] |
An unexpected condition has occurred which is due to the absence of\n\ MCP WCCP interface info for the specific service group. |
asr1k-wccp |
"show platform software wccp" |
|
IOSXE_WCCP-4-NOSTATS |
4-Warning |
WCCP [chars] message error |
An unexpected condition has occurred which is due to the error in \n\ receiving WCCP stats update message. |
asr1k-wccp |
"show platform software wccp <id> counters" |
|
IOSXE_WCCP-4-NOSTATSINTF |
4-Warning |
Interface handle [dec] not exsit for the stats message |
An unexpected condition has occurred which can't find the interface handle\n\ for the interface stats message. |
asr1k-wccp |
"show platform software wccp <id> int counters" |
|
IOSXE_WCCP-4-NOSTATSSVC |
4-Warning |
Service Group [dec] [dec] [dec] not exist for the stats message |
An unexpected condition has occurred which can't find the service group\n\ for the service group stats message. |
asr1k-wccp |
"show platform software wccp" |
|
IOSXE_WCCP-4-NOSVCGRP |
4-Warning |
[chars] Service Group [dec] [dec] [dec] NOT exist |
An unexpected condition has occurred which is due to the absence of\n\ the service group structure. |
asr1k-wccp |
"show ip wccp" |
|
IOSXE_WCCP-4-UNKNOWNDIR |
4-Warning |
Unknown [chars] interface direction 0x[hec] for Service Group [dec] [dec] [dec] |
An unexpected condition has occurred which is due to the unknown direction\n\ has been applied to the interface for the service group. |
asr1k-wccp |
"show platform software wccp" |
|
IOSXE_WD-2-HEARTBEAT_FAIL |
2-Critical |
Heartbeat is not emitted. Heartbeat count:[dec] |
Failure in IOS to generate a heartbeat is\n\ an abnormal condition |
DDTS_COMPONENT |
"This message may be related to an abnormal configuration\n\ and system load or transient high processing demand." "\n\n When reporting this message copy the message text exactly as\n\ it appears include the stack trace and report to your technical\n\ support representative" |
|
IOSXE_WD-2-HOG_DETECT_FAIL |
2-Critical |
CPUHOG detection failed to start. |
Failure in setting up CPUHOG detection mechanism is\n\ an abnormal condition |
DDTS_COMPONENT |
"This message may be related to an abnormal configuration\n\ and system load or transient high processing demand." "\n\n When reporting this message copy the message text exactly as\n\ it appears include the stack trace and report to your technical\n\ support representative" |
|
IOXN_APP-3-CFGFAIL |
3-Error |
[chars] [chars] |
An unexpected condition resulted into failure to apply auto config |
iox-caf |
LOG_STD_ACTION |
|
IOXN_APP-3-CLEANUPFAIL |
3-Error |
Failed to create chasfs property to indicate cleanup of previous app installation rc = [chars] |
- |
- |
- |
|
IOXN_APP-3-GSFAIL |
3-Error |
[chars] [dec] |
An unexpected condition resulted into failure to start an application. |
iox-caf |
LOG_STD_ACTION |
|
IOXN_APP-3-INITFAIL |
3-Error |
Failed to create chasfs property ioxman rc =[chars] or caf rc = [chars] is not up |
- |
- |
- |
|
IOXN_APP-3-IOX_CONFIG_FAIL |
3-Error |
IOX configuration change not allowed while running\n |
Error in iox configuration |
- |
LOG_STD_ACTION |
|
IOXN_APP-3-IPCINITFAIL |
3-Error |
[chars]\n |
A critical IPC initialization error occured |
iox-caf |
LOG_STD_ACTION |
|
IOXN_APP-3-MSGFAIL |
3-Error |
Message dispatch failure [chars]. |
- |
- |
- |
|
IOXN_APP-3-PREVOPFAIL |
3-Error |
Overriding previous operation [chars] iox that is taking longer than [dec] |
An unexpected condition resulted in failure to apply iox config |
iox-caf |
LOG_STD_ACTION |
|
IOXN_APP-3-STARTUP_CONFIG_FAIL |
3-Error |
[chars] [chars]\n |
Error while creating startup config |
- |
LOG_STD_ACTION |
|
IOXN_APP-6-APP_HOSTING_SUPPORT |
6-Information |
[chars] |
Informational logs to show App Gigabit Interface is not supported on 10 Slot Catalyst 9400 |
- |
LOG_STD_ACTION |
|
IOXN_APP-6-IOX_START_STOP_REQ |
6-Information |
[chars]\n |
Informational logs for IOX Start/Stop request. |
- |
LOG_STD_ACTION |
|
IOXN_APP-6-LICENCE_CHECK_INFO |
6-Information |
[chars]\n |
Informational log about license. |
- |
LOG_STD_ACTION |
|
IOXN_APP-6-PRE_INIT_DAY0_GS_INFO |
6-Information |
[chars]\n |
Informational logs for Day0 GS initialization. |
- |
LOG_STD_ACTION |
|
IOXN_APP-6-SLOT_NOTIFICATION |
6-Information |
[chars] [dec] |
Slot addition or removal information |
- |
LOG_STD_NO_ACTION |
|
IOXN_APP-6-STARTUP_CONFIG_CHASSIS_INFO |
6-Information |
[chars] [dec]/[chars]/[dec]/[dec]\n |
Chassis information at startup config injection. |
- |
LOG_STD_NO_ACTION |
|
IOXN_APP-6-STARTUP_CONFIG_INFO |
6-Information |
[chars]\n |
Informational logs for startup config injection. |
- |
LOG_STD_ACTION |
|
IP_DEVICE_TRACKING_HA-3-FAIL_SEND_MSG_TO_ACTIVE |
3-Error |
Failed to send [chars] message to active for [chars] [chars] |
The specified synchronization message which is an internal IPC message could not be sent to the active unit in the specified run-time module. The failure most likely occurred because of a software error. Additional details on the nature of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized. |
- |
LOG_STD_SH_TECH_ACTION |
|
IP_DEVICE_TRACKING_HA-3-NO_RESOURCES |
3-Error |
[chars] |
A run-time module could not obtain the resources that are required to complete a task. The failure most likely occurred because of a software error or a lack of system memory. Additional details on the nature of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized. |
- |
"If you determine that this condition was caused by " "a lack of system memory reduce system activity to " "ease memory demands or if conditions warrant upgrade " "to a larger memory configuration. Otherwise " LOG_STD_SH_TECH_ACTION |
|
IP_DEVICE_TRACKING_HA-4-ENTRY_OUT_OF_SYNC |
4-Warning |
Host mac-address [enet] ip-address [inet] interface [chars] event_type: [chars] entry_type: [chars] |
An inconsistency has been detected in the IP device tracking table for this host between active and standby |
- |
LOG_STD_NO_ACTION |
|
IP_DEVICE_TRACKING-4-TABLE_LOCK_FAILED |
4-Warning |
Table already locked by process-id [dec][chars] |
The IP device tracking table could not be updated due to a lock held by another process |
- |
LOG_STD_NO_ACTION |
|
IP_HOST_ISSU-2-GET_BUFFER |
2-Critical |
IP Host ISSU client failed to get buffer for message. Error: [dec] [chars] |
The IP Host 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. |
- |
"show logging and show checkpoint client" |
|
IP_HOST_ISSU-2-INIT |
2-Critical |
IP Host ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The IP Host 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. |
- |
LOG_STD_ACTION |
|
IP_HOST_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
IP Host ISSU client failed to send negotiation message. Error: [dec] [chars] |
The IP Host 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. |
- |
"show logging and show checkpoint client" |
|
IP_HOST_ISSU-2-SESSION_NEGO |
2-Critical |
IP Host ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The IP Host 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. |
- |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
IP_HOST_ISSU-2-SESSION_REGISTRY |
2-Critical |
IP Host ISSU client failed to register session information. Error: [dec] [chars] |
The IP Host ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
- |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
IP_HOST_ISSU-3-CAP_INVALID_SIZE |
3-Error |
IP_HOST ISSU client capability list is empty. |
The IP_HOST ISSU client capability exchange list size is invalid. |
- |
"show issu capability entires <Client_ID>" |
|
IP_HOST_ISSU-3-CAP_NOT_COMPATIBLE |
3-Error |
IP Host ISSU client capability exchange result incompatible. |
The IP Host ISSU client capability exchange have negotiated as incompatible with the peer. |
- |
"show issu negotiated capability <Session_ID>" |
|
IP_HOST_ISSU-3-INVALID_SESSION |
3-Error |
IP Host ISSU client does not have a valid registered session. |
The IP Host ISSU client does not have a valid registered session. |
- |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
IP_HOST_ISSU-3-MSG_NOT_OK |
3-Error |
IP Host ISSU client 'Message Type [dec]' is not compatible |
The IP Host ISSU client received an incompatible message from the peer device. The message cannot be processed. |
- |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
IP_HOST_ISSU-3-MSG_SIZE |
3-Error |
IP Host ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The IP Host ISSU client failed to calculate the MTU for the specified message. The IP Host ISSU client is not able to send the message to the standby device. |
- |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
IP_HOST_ISSU-3-SESSION_UNREGISTRY |
3-Error |
IP Host ISSU client failed to unregister session information. Error: [dec] [chars] |
The IP Host ISSU client failed to unregister session information. |
- |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
IP_HOST_ISSU-3-TRANSFORM_FAIL |
3-Error |
IP Host ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The IP Host 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 IP Host state between the active device and the standby device is not identical. |
- |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
IP_PORT_SECURITY-4-DENY_INVALID_PACKET |
4-Warning |
Detected and dropped illegal traffic on port [chars] and vlan [dec] the non-cumulative packet dropped count is %ld. |
IP Port Security only permits traffic with the correct source IP to MAC\n\ binding on the port or VLAN. There may be a malicious host trying to\n\ carry out a denial of service attack using another host's source address.\n\ The illegal traffic is dropped by the IP Port Security feature. |
ipsg |
"Identify the source of the illegal traffic " "and stop it." |
|
IP_SNMP-3-SOCKET |
3-Error |
can't open UDP socket |
The SNMP server was unable to open a port for receiving or\n\ transmitting SNMP requests. This usually happens when the SNMP\n\ server is started using the snmp-server community configuration\n\ command on a router or communication server with an interface that\n\ has no IP address configured. Another possible cause is low memory. |
- |
"Configure at least one interface with an IP address or specify the no\n\ snmp-server command to remove the SNMP server process. Call your\n\ technical support representative if problems persist or if it becomes\n\ necessary to add memory." |
|
IP_SNMP-4-NOTRAPIP |
4-Warning |
SNMP trap source [chars] has no ip address |
The user entered an snmp-server trap-source command. The interface\n\ requested for use as the source address has no ipv4 address\n\ associated with it. The SNMP trap is being sent anyway but\n\ without the source address that the user intended. |
- |
"There are two possible solutions. Either enter a no snmp-server\n\ trap-source command to disable the request for a specific source IP\n\ address or add an IP address to the interface referenced in the\n\ snmp-server trap-source configuration command." |
|
IP_SNMP-4-NOTRAPIPV6 |
4-Warning |
SNMP trap source [chars] has no ipv6 address |
The user entered an snmp-server trap-source command. The\n\ interface requested for use as the source address has no ipv6\n\ address associated with it. The SNMP trap is being sent\n\ anyway but without the source address that the user intended. |
- |
"There are two possible solutions. Either enter a no snmp-server\n\ trap-source command to disable the request for a specific source\n\ IP address or add an IPV6 address to the interface referenced\n\ in the snmp-server trap-source configuration command." |
|
IP_SNMP-4-TOOBIG |
4-Warning |
Oversize message from [inet] datagram size [dec] udp length [dec] |
An incoming SNMP packet had a length field so large that\n\ the system had to assume it was in error. This system made a\n\ correct reaction to bad external data.\n\ Since SNMP packets should originate from systems under the\n\ same administration this may indicate that the network host\n\ used to originate the SNMP request had a problem in its\n\ networking layer.\n\ Alternatively if the SNMP packet originated from outside\n\ the local administrative domain it could indicate an\n\ failed attempt at security penetration and that site should\n\ be watched more closely. |
- |
"If the origin is local no action is required.\n\ If the origin is determined to be malicious either contact the\n\ administrator of the originating site or install filters to\n\ prevent access by that site as circumstances warrant." |
|
IP_SOURCE_GUARD-4-DENY_INVALID_PACKET |
4-Warning |
Detected and dropped illegal traffic on port [chars] and vlan [dec] the non-cumulative packet dropped count is %ld. |
IP Source Guard only permits traffic with the correct source IP to MAC\n\ binding on the port or VLAN. There may be a malicious host trying to\n\ carry out a denial of service attack using another host's source address.\n\ The illegal traffic is dropped by the IP Source Guard feature. |
ipsg |
"Identify the source of the illegal traffic " "and stop it." |
|
IP_TUNNEL-2-IPC_INIT |
2-Critical |
IPC message handler registration failure rc [dec] |
Registering an IPC message handler for the Tunnel feature failed. This may cause the feature to not function. |
qfp-ip-tunnel |
"This is normally a software issue. " "The consequences are that the tunnel feature may not function. " LOG_STD_ACTION |
|
IP_TUNNEL-3-IPC_NORES |
3-Error |
No space for the IPC reply size [dec] |
For a request from upper TUNNEL software stack layers it was not possible to allocate space for a reply for the specified size. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation. |
qfp-ip-tunnel |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
IP_TUNNEL-3-IPC_OPEN_REPLY |
3-Error |
IPC Open Reply failed request [dec] |
For a request from upper TUNNEL software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation. |
qfp-ip-tunnel |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
IP_TUNNEL-3-VRF_HOST_MEM_EXTEND_FAILED |
3-Error |
QFP TUNNEL Proxy IPC VRF host mem extend failed |
Extending memory failed. |
qfp-tunnel keyword:tunnel |
LOG_STD_ACTION |
|
IP_TUNNEL-3-VRF_HOST_MEM_REQ_FAILED |
3-Error |
QFP TUNNEL Proxy IPC VRF host mem req failed |
Requesting more memory failed. |
qfp-tunnel keyword:tunnel |
LOG_STD_ACTION |
|
IP_TUNNEL-4-INVALID_MSG_LEN |
4-Warning |
QFP TUNNEL Proxy IPC invalid length [dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Cisco internal software error. QFP TUNNEL Proxy received invalid IPC message length from control plane. This message will be ignored. |
qfp-tunnel keyword:tunnel |
LOG_STD_ACTION |
|
IP_VFR-3-INVALID_FRAG_LENGTH |
3-Error |
[chars]: fragment length invalid - received from [inet] destined to [inet] |
This message indicates that the router has encountered a ping-of-death sort of an attack |
ios-firewall |
"To prevent further attacks its highly recommendated that an ACL " "be configured to drop any traffic from the sender" |
|
IP_VFR-3-OVERLAP_FRAGMENTS |
3-Error |
[chars]: from the host [inet] destined to [inet] |
This message is logged whenever the router encounters overlap fragments. Overlap fragment means offset of one fragment overlaps the offset of another fragment. For example if first fragment's offset is 0 and length is 800 then the second fragments offset must be 800. If second fragment's offset is less than 800 that means the second fragment overlaps the first fragment. |
ios-firewall |
"This could possibly be an attack configure a static ACL to prevent " "further overlap fragments from the sender" |
|
IP_VFR-3-SYSTEM_ERROR |
3-Error |
[chars]: IP VFR System failure - [chars] |
This message indicates the misc errors in the VFR subsystem |
ios-firewall |
- |
|
IP_VFR-4-FRAG_TABLE_OVERFLOW |
4-Warning |
[chars]: the fragment table has reached its maximum threshold [dec] |
This means the number of datagrams reassembled at a time reached its maximum limit increase the value of max-reassemblies using ip virtual-reassembly max-reassemblies <number> |
ios-firewall |
- |
|
IP_VFR-4-TINY_FRAGMENTS |
4-Warning |
[chars]: from the host [inet] destined to [inet] |
This message indicates that the router is receiving tiny fragments - meaning the initial fragment does not have complete layer 4 header |
ios-firewall |
"This is an informational message" |
|
IP_VFR-4-TOO_MANY_FRAGMENTS |
4-Warning |
[chars]: Too many fragments per datagram more than [dec] - sent by [inet] |
This message indicates the datagram being reassembled has received more fragments than its threshold value |
ios-firewall |
"Check if the fragments received are from a genuine source if so " "increase the value of max-fragments using the CLI " "ip virtual-reassembly max-fragments <number>" |
|
IP_VRF-3-MAX_VRF |
3-Error |
[chars] |
Related to MAX number of VRFs |
vrfinfra |
LOG_STD_ACTION |
|
IP_VRF-3-VRF_AF_ACTIVATE |
3-Error |
Unable to activate VRF support for address family [chars] |
The VRF subsystem was unable to initialize support for the indicated address family |
vrfinfra |
LOG_STD_ACTION |
|
IP_VRF-3-VRF_AF_ENABLE_ERROR |
3-Error |
Failed to enable address-family [chars] in VRF [chars]: [chars] |
Failed to enable AF in a VRF |
vrfinfra |
LOG_STD_ACTION |
|
IP_VRF-3-VRF_CCA_ERROR |
3-Error |
VRF-CCA: [chars] |
VRF manager encountered a command inheritance error |
vrfinfra |
LOG_STD_ACTION |
|
IP_VRF-3-VRF_CMN_INVALID_PARAM |
3-Error |
[chars] |
Invalid parameter. |
vrfinfra |
LOG_STD_ACTION |
|
IP_VRF-3-VRF_CONFIG_IF_LOCK_ERROR |
3-Error |
Failed to acquire interface configuration lock |
VRF interface association failed |
vrfinfra |
LOG_STD_ACTION |
|
IP_VRF-3-VRF_CREATE_FAIL |
3-Error |
[chars] |
IP VRF creation failed. |
vrfinfra |
LOG_STD_ACTION |
|
IP_VRF-3-VRF_GET_LOCK_COUNT_ERROR |
3-Error |
Failed to get lock count for VRF [chars]: [chars] |
Failed to lock count from a VRF |
vrfinfra |
LOG_STD_ACTION |
|
IP_VRF-3-VRF_HDVRF_ERROR |
3-Error |
HDVRF: [chars] |
HDVRF related error messages |
vrfinfra |
LOG_STD_ACTION |
|
IP_VRF-3-VRF_ID_INVALID_ERROR |
3-Error |
Invalid VRF id 0x[hec] in [chars] |
VRF ID Invalid |
vrfinfra |
LOG_STD_ACTION |
|
IP_VRF-3-VRF_IFLIST_ADD |
3-Error |
Error adding [chars] to interface list of VRF [chars] |
VRF interface association failed |
vrfinfra |
LOG_STD_ACTION |
|
IP_VRF-3-VRF_IFLIST_DEL |
3-Error |
Error removing [chars] from interface list of VRF [chars] |
VRF interface disassociation failed |
vrfinfra |
LOG_STD_ACTION |
|
IP_VRF-3-VRF_IFLIST_NOT_EMPTY |
3-Error |
VRF [chars] iflist is not empty in [chars] |
VRF iflist is not empty |
vrfinfra |
LOG_STD_ACTION |
|
IP_VRF-3-VRF_IVRF_ERROR |
3-Error |
[chars] |
VRF infrastructure failure for Platform VRFs. |
vrfinfra |
LOG_STD_ACTION |
|
IP_VRF-3-VRF_LCKMGR_CONTEXT_INIT_ERROR |
3-Error |
Failed to initialize lock manager context for vrf [chars][dec] with error [chars] |
VRF lock manager initialization failure |
vrfinfra |
LOG_STD_ACTION |
|
IP_VRF-3-VRF_LCKMGR_INIT_ERROR |
3-Error |
[chars] |
VRF lock manager initialization failure |
vrfinfra |
LOG_STD_ACTION |
|
IP_VRF-3-VRF_LOCK_ERROR |
3-Error |
Failed to lock VRF [chars]: [chars] |
Failed to lock a VRF |
vrfinfra |
LOG_STD_ACTION |
|
IP_VRF-3-VRF_MT_UPDATE_ERROR |
3-Error |
Failed to update multicast multi-topology mode for address-family [chars] in VRF [chars]: [chars] |
Failed to update multicast multi-topology mode in a VRF |
vrfinfra |
LOG_STD_ACTION |
|
IP_VRF-3-VRF_SUBSYSTEM_INIT_FAILED |
3-Error |
VRF subsystem initialization failed: [chars] |
The VRF subsystem could not be initialized |
vrfinfra |
LOG_STD_ACTION |
|
IP_VRF-3-VRF_TABLEID_INCONSISTENT |
3-Error |
[chars] |
VRF tableid inconsistent between two RPs. |
vrfinfra |
LOG_STD_ACTION |
|
IP_VRF-3-VRF_UNLOCK_ERROR |
3-Error |
Failed to unlock VRF [chars]: [chars] |
Failed to unlock a VRF |
vrfinfra |
LOG_STD_ACTION |
|
IP_VRF-4-VRF_CONFIG_IF_LOCK_DELAY |
4-Warning |
Unexpected delay while acquiring interface configuration lock |
Unexpected delay in VRF interface association |
vrfinfra |
LOG_STD_NO_ACTION |
|
IP_VRF-4-VRF_CONFIG_IF_LOCK_IGNORED |
4-Warning |
Ignored interface configuration lock [dec] times |
Processing is continuing without obtaining the VRF interface configuration lock |
vrfinfra |
LOG_STD_NO_ACTION |
|
IP_VRF-4-VRF_CONFIG_IF_LOCK_TAKEN |
4-Warning |
Acquired interface configuration lock |
Unexpected delay in VRF interface association |
vrfinfra |
LOG_STD_NO_ACTION |
|
IP-3-BADIPALIGN |
3-Error |
Invalid alignment in packet for IP. [chars]=[hex] |
The packet data structure is misaligned. This condition may result in\n\ a small amount of overhead in processing IP traffic. |
- |
"Enter a show hardware command and report the output along with this\n\ error message to your technical support representative." |
|
IP-3-BADSROUTE |
3-Error |
Improper source route. Length [dec] Ptr [dec] |
A hardware or software error occurred. |
- |
LOG_STD_ACTION |
|
IP-3-CNTRFULL |
3-Error |
IP counter block is full setting protocol [dec] |
An internal software error occured. |
- |
LOG_STD_SH_TECH_ACTION |
|
IP-3-DESTHOST |
3-Error |
src=[inet] dst=[inet] NULL desthost |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
IP-3-ICMPRATELIMIT |
3-Error |
[dec] unreachables rate-limited within [dec] milliseconds on [chars]. [dec] log messages suppressed since last log message displayed on [chars] |
An excessive number of packets are triggering log messages on this interface |
- |
"change the log threshold with the icmp rate-limit command or " "find the source of the packets and block the packets from this router" |
|
IP-3-ICMPRATELIMITDF |
3-Error |
[dec] DF unreachables rate-limited within [dec] milliseconds on [chars]. [dec] DF log messages suppressed since last log message displayed on [chars] |
An excessive number of packets are triggering log messages on this interface |
- |
"change the log threshold with the icmp rate-limit command or " "find the source of the packets and block the packets from this router" |
|
IP-3-IPTOPOID |
3-Error |
Topology ID 0x[hec] is invalid can't get the base topology ID. |
An internal software error occurred |
- |
LOG_STD_ACTION |
|
IP-3-LOOPOUTIF |
3-Error |
Output interface for packet has been changed for [dec] times and dropped - \nsrc=[inet] dst=[inet] hl=[dec] tl=[dec] prot=[dec] \nin=[chars] nexthop=[inet] out=[chars] |
A software error occurred. |
- |
LOG_STD_ACTION |
|
IP-3-LOOPPAK |
3-Error |
Looping packet detected and dropped - \nsrc=[inet] dst=[inet] hl=[dec] tl=[dec] prot=[dec] sport=[dec] dport=[dec] \nin=[chars] nexthop=[inet] out=[chars]\noptions=[chars] |
A software error occurred. |
- |
LOG_STD_ACTION |
|
IP-3-MAXIRDP |
3-Error |
Attempt to send IRDP to proxies exceeding configurable limit: [dec] interface: [chars] secondary = [dec] proxy = [dec]\n |
The sum of configured secondary addresses and configured proxy addresses exceeds the number of total addresses that the IRDP can support in its implementation. |
- |
"Reduce the number of either the secondary IP addresses or proxy" " addresses configured for the interface." |
|
IP-3-NONALIAS |
3-Error |
non-alias address [inet] in table [chars] found in IP alias list |
The IP alias list holds IP aliases only but non-alias entries are found. |
ip |
LOG_STD_ACTION |
|
IP-3-NOOUTINTF |
3-Error |
Output interface not available. source address: [inet] destination address: [inet] routing type: [dec] |
The output interface for this packet is not set |
ip |
LOG_STD_ACTION |
|
IP-3-SBINIT |
3-Error |
Error initializing [chars] subblock data structure. [chars] |
Initialization of the specified subblock data structure could not be accomplished. |
ip |
LOG_STD_ACTION |
|
IP-4-CLASS |
4-Warning |
Bad IP address and mask [inet]%m in class_resolve |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
IP-4-DUPADDR |
4-Warning |
Duplicate address [inet] on [chars] sourced by [enet] |
Another system is using your IP address. |
- |
"Change the IP address of one of the two systems." |
|
IP-4-IPPOOLS |
4-Warning |
Detected a local pool and a DHCP pool with the same name: [chars] |
A local pool and a DHCP pool have been configured with the same name. This may cause conflict during address allocations. |
- |
"Change the name of one of the two pools" |
|
IP-4-UNICASTRPF |
4-Warning |
IP unicast reverse-path check disabled on [chars] |
The IP verify unicast reverse-path feature was disabled because CEF was disabled either through configuration or due to an internal error. |
- |
LOG_STD_SH_TECH_ACTION |
|
IP-4-ZERO_ADDR |
4-Warning |
Zero MAC address for [inet] in ARP cache |
An entry in the ARP cache have a NULL MAC address |
- |
"If this message recurs call your technical support\n\ representative for assistance." |
|
IP-5-ACL |
5-Notice |
[chars] |
Error occured in IP access checks. |
- |
LOG_STD_SH_TECH_ACTION |
|
IP-5-TURBOACL |
5-Notice |
[chars] |
Error occured in intialisation of TURBOACL. |
- |
show process |
|
IP-5-WEBINST_COMP |
5-Notice |
Selected IP address [inet] |
A hardware or software error occurred. |
- |
LOG_STD_ACTION |
|
IP-5-WEBINST_KILL |
5-Notice |
Terminating DNS process |
A hardware or software error occurred. |
- |
LOG_STD_ACTION |
|
IP-5-WEBINST_RESP |
5-Notice |
Sending DNS response to [inet] request was for [inet] |
- |
- |
- |
|
IP-5-WEBINST_START |
5-Notice |
Attempting web install from host [inet] |
A hardware or software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
IP-6-L2MCASTDROP |
6-Information |
Layer 2 Multicast packet detected and dropped src=[inet] dst=[inet] |
Layer 2 Multicast packet with Layer3 Unicast Destination was dropped. |
ip |
LOG_STD_NO_ACTION |
|
IP-6-PHYBCASTDROP |
6-Information |
Physical broadcast packet detected and dropped src=[inet] dst=[inet] |
Physical broadcast packet was dropped. |
ip |
LOG_STD_NO_ACTION |
|
IPACCESS-2-NOMEMORY |
2-Critical |
Alloc fail for acl-config buffer. Disabling distributed mode on lc |
Unable to malloc a buffer to send access-list configuration down\n\ to linecards. |
ip-acl |
"Enter a show chunks command and report the output along with this\n\ error message to your technical support representative." |
|
IPACCESS-2-WRONGREQUEST |
2-Critical |
Invalid request to allocate chunk of size [dec] |
We only allow acl chunks of max size IPACCESS_LARGE_CHUNK_SZ |
ip-acl |
" " |
|
IPACCESS-2-WRONGSIZE |
2-Critical |
Incorrect length acl ipc xdr of type=[chars] len=[dec] received |
Received an acl message of the wrong size for that type |
ip-acl |
"Report this error message to your tech support representative." |
|
IPACCESS-3-ACL_ACE_LIMIT_EXCEEDED |
3-Error |
Exceeding the max aces[dec] per ACL configurable |
Error is occurred when aces limit per ACL is exceeding the ACL ace limit set. |
ip-acl |
LOG_STD_ACTION |
|
IPACCESS-3-ACL_LIMIT_EXCEEDED |
3-Error |
Exceeding max acl limit[dec] configurable failed to create ACL |
- |
- |
- |
|
IPACCESS-3-GLOBAL_ACE_LIMIT_EXCEEDED |
3-Error |
Exceeding the global max ace limit configurable[dec] |
Error is occurred when the global ace limit is exceeded than the global ace limit set. |
ip-acl |
LOG_STD_ACTION |
|
IPACCESS-3-SANITY_ERROR |
3-Error |
[chars] |
A sanity error occurred while the ACL was being configured on the RP or while the ACL configuration was being downloaded to the line card. |
ip-acl |
LOG_STD_ACTION |
|
IPACCESS-3-XDRREGISTRATION |
3-Error |
Failed to register [chars] XDR client due to [chars] |
Failure to register the said XDR client. |
ip-acl |
"Copy the message exactly as it appears and report it to your " "technical support representative." |
|
IPACCESS-4-INVALIDACL |
4-Warning |
Invalid ACL field: [chars] is [dec] |
An internal software error occurred. |
ip-acl |
"Copy the message exactly as it appears and report it to your\n\ technical support representative." |
|
IPAD-3-BLOCKEMPTY |
3-Error |
Block does not exist. |
Try to access a block that does not exist. |
ip |
"" |
|
IPAD-3-CTXTMASKTYPE |
3-Error |
Search context mask type or sub type not recognized: [dec] [dec]. Search\n\ context last found IP address [inet] search context target IP address [inet]. |
An internal IPAD error occurred. Search contex mask type not defined. |
ip |
"" |
|
IPAD-3-LISTTYPE |
3-Error |
Double-linked list DLL type not recognized: [dec]. |
An internal IPAD error occurred. DLL type not defined. |
ip |
"" |
|
IPAD-3-MEMORY |
3-Error |
Can not allocate memory for a block in IPAD: [chars] |
The operation may have failed due to lack of memory. |
ip |
"" |
|
IPAD-3-TRIM |
3-Error |
Access on level [dec] to the left of index [dec]. |
IPAD is not trimmed properly. |
ip |
"" |
|
IPC_RSP_CBUS-3-CARDERR |
3-Error |
[chars] |
An IPC card has registered itself to the IPC master twice. The card malfunctioned and its IPC is not active. |
- |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
IPC_RSP_CBUS-3-INVNUM |
3-Error |
[chars] [dec] |
The IPC application tried to send a message that was larger than IPC could handle. The message was not transmitted. |
- |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
IPC_RSP_CBUS-3-MSGERR |
3-Error |
[chars] [dec] |
System controller Bengal has reported an error/event |
RSP |
"Read error reports. SBE are generally not fatal. Most others are" |
|
IPC_RSP_CBUS-3-NOBUF |
3-Error |
[chars] |
The IPC ran out of memory device MEMD buffers. |
- |
"Reduce the number of applications currently running on the IPC. Copy the error message exactly as it appears and report it to your technical support representative." |
|
IPC_RSP_CBUS-3-NOHWQ |
3-Error |
Hardware queue for card at slot [dec] not found |
IPC messages cannot be transmitted due to a missing hardware queue. The messages were discarded and subsequent messages will not be transmitted to that card. |
- |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
IPC_RSP_CBUS-3-SEATERR |
3-Error |
[chars] [dec] |
The ID associated with an IPC card is either missing duplicated or cannot be created. |
- |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
IPC_TEST-3-INVALID_SUBTYPE |
3-Error |
CPP IPC TEST Proxy subtype [dec] |
IPC test proxy failed because of receiving invalid sub-type. |
cpp-ucode |
LOG_STD_ACTION |
|
IPC_TEST-3-MEM_ALLOC_FAILED |
3-Error |
CPP IPC TEST Proxy mem alloc |
IPC test proxy failed because the GPM allocation failed. |
cpp-ucode |
- |
|
IPC_TEST-3-REPLY_FAILED |
3-Error |
CPP IPC TEST Proxy send reply |
IPC test proxy failed because the reply failed to send. |
cpp-ucode |
- |
|
IPC-2-BADSHARE |
2-Critical |
Bad refcount in [chars] ptr=[hec] count=[dec] |
A reference count is used to track the usage of IPC messages. A function increments the count when it begins to use a message and decrements it when it finishes. When the count becomes zero the data structure is freed. This message indicates that when the count was accessed it was found to be zero or negative. |
ipc |
"show tech-support ipc" |
|
IPC-2-BADSHARE |
2-Critical |
Bad refcount in [chars] ptr=[hec] count=[dec] |
A reference count is used to track the usage of IPC messages. A function increments the count when it begins to use a message and decrements it when it finishes. When the count becomes zero the data structure is freed. This message indicates that when the count was accessed it was found to be zero or negative. |
ipc |
"show tech-support ipc" |
|
IPC-2-CANT_SEND |
2-Critical |
[chars]: Cannot send IPC message from 0x[hec] to 0x[hec]: info 0x[hec] |
An error occurred when sending IPC message |
ipc |
"show tech-support ipc" |
|
IPC-2-CANT_SEND |
2-Critical |
[chars]: Cannot send IPC message from 0x[hec] to 0x[hec]: info 0x[hec] |
An error occurred when sending IPC message |
ipc |
"show tech-support ipc" |
|
IPC-2-INITFAILED |
2-Critical |
[chars] |
IPC Resource Management Initialization failed |
ipc |
"This is a critical failure for IPC functionality." "Capture 'sh version' and contact TAC" |
|
IPC-2-INITFAILED |
2-Critical |
[chars] |
IPC Resource Management Initialization failed |
ipc |
"This is a critical failure for IPC functionality." "Capture 'sh version' and contact TAC" |
|
IPC-2-INVALIDSEAT |
2-Critical |
Invalid IPC Seat 0x[hec]. |
Some operation is attempted on a seat ID not known to IPC |
ipc |
"show tech-support ipc" |
|
IPC-2-INVALIDZONE |
2-Critical |
Invalid IPC Zone 0x[hec]. |
Some operation is attempted on a zone ID not known to IPC |
ipc |
"show tech-support ipc" |
|
IPC-2-INVALIDZONE |
2-Critical |
Invalid IPC Zone 0x[hec]. |
Some operation is attempted on a zone ID not known to IPC |
ipc |
"show tech-support ipc" |
|
IPC-2-LOCK |
2-Critical |
Lock done a deleted element 0x[hec] |
An internal inconsistency was found in some IPC data structures. |
ipc |
"show tech-support ipc" |
|
IPC-2-LOCK |
2-Critical |
Lock done a deleted element 0x[hec] |
An internal inconsistency was found in some IPC data structures. |
ipc |
"show tech-support ipc" |
|
IPC-2-NO_ACK_HANDLER |
2-Critical |
No handler for ACK with data for port [hec]. |
The IPC receiver appended data to an ACK. But at the sender there is no corresponding ACK handler. |
ipc |
"show tech-support ipc" |
|
IPC-2-NO_ACK_HANDLER |
2-Critical |
No handler for ACK with data for port [hec]. |
The IPC receiver appended data to an ACK. But at the sender there is no corresponding ACK handler. |
ipc |
"show tech-support ipc" |
|
IPC-2-NOBLOCK |
2-Critical |
Invalid blocking operation in interrupt context or process blocking is disabled: [chars] [hec] |
Debug Message. An IPC application has attempted an IPC action which has been prohibited from being performed at interrupt level or when process has disabled blocking |
ipc |
show ipc ports |
|
IPC-2-NOBOOL |
2-Critical |
Boolean NULL in IPC message: [hec]. |
A watched boolean that was allocated while sending the message is found to be NULL when an ACK arrived. |
ipc |
show ipc status |
|
IPC-2-NOBOOL |
2-Critical |
Boolean NULL in IPC message: [hec]. |
A watched boolean that was allocated while sending the message is found to be NULL when an ACK arrived. |
ipc |
show ipc status |
|
IPC-2-NODISPATCH |
2-Critical |
Message for [hec].[hec] has no receive queue or dispatch routine |
The IPC user failed to provide any means of handling the received message. |
ipc |
show ipc ports |
|
IPC-2-NODISPATCH |
2-Critical |
Message for [hec].[hec] has no receive queue or dispatch routine |
The IPC user failed to provide any means of handling the received message. |
ipc |
show ipc ports |
|
IPC-2-NOMEM |
2-Critical |
No memory available for [chars] |
The IPC protocol subsystem could not obtain the memory it needed. |
ipc |
"If this error message recurs attempt to reduce memory usage by " "reducing the number of router features or interfaces enabled. " "Alternatively add more memory. " "\n\nTo display total memory usage for a router enter " "<CmdBold>show memory summary<noCmdBold> at the privileged " "command line prompt. To display buffer usage enter " "<CmdBold>show buffers<noCmdBold> at the prompt. To display IPC " "usage enter <CmdBold>show ipc queue<noCmdBold> at the prompt" |
|
IPC-2-NOMEM |
2-Critical |
No memory available for [chars] |
The IPC protocol subsystem could not obtain the memory it needed. |
ipc |
"If this error message recurs attempt to reduce memory usage by " "reducing the number of router features or interfaces enabled. " "Alternatively add more memory. " "\n\nTo display total memory usage for a router enter " "<CmdBold>show memory summary<noCmdBold> at the privileged " "command line prompt. To display buffer usage enter " "<CmdBold>show buffers<noCmdBold> at the prompt. To display IPC " "usage enter <CmdBold>show ipc queue<noCmdBold> at the prompt" |
|
IPC-2-ONINT |
2-Critical |
Invalid operation at interrupt level: [chars] [hec] |
Debug Message. An IPC application has attempted an IPC action which has been prohibited from being performed at the interrupt level. |
ipc |
show ipc ports |
|
IPC-2-ONINT |
2-Critical |
Invalid operation at interrupt level: [chars] [hec] |
Debug Message. An IPC application has attempted an IPC action which has been prohibited from being performed at the interrupt level. |
ipc |
show ipc ports |
|
IPC-2-PRECLOSE |
2-Critical |
IPC port pre-closure overflow : 0x[hec] : 0x[hec] |
An application attempts to close an ipc port when there are messages pending in retransmit queue and ipc defer table overflows. |
ipc |
"show ipc ports open" |
|
IPC-2-PRECLOSE |
2-Critical |
IPC port pre-closure overflow : 0x[hec] : 0x[hec] |
An application attempts to close an ipc port when there are messages pending in retransmit queue and ipc defer table overflows. |
ipc |
"show ipc ports open" |
|
IPC-2-SPI_IOSD_IPC_INIT_FAILED |
2-Critical |
SPI IOSd IPC init failed - [chars]. |
SPI IOSd IPC initialization failed |
spi |
"show tech-support ipc" |
|
IPC-2-TEST |
2-Critical |
IPC test: [chars] |
The IPC test routines. |
ipc |
"IPC test only - no action required." |
|
IPC-2-TEST |
2-Critical |
IPC test: [chars] |
The IPC test routines. |
ipc |
"IPC test only - no action required." |
|
IPC-2-UNLOCK |
2-Critical |
Unlock done on already unlocked element 0x[hec] |
An internal inconsistency was found in some IPC data structures. |
ipc |
"show tech-support ipc" |
|
IPC-2-UNLOCK |
2-Critical |
Unlock done on already unlocked element 0x[hec] |
An internal inconsistency was found in some IPC data structures. |
ipc |
"show tech-support ipc" |
|
IPC-3-ACKALLOC |
3-Error |
couldn't send to [chars] |
Allocating an IPC acknowledgement failed with the likely result that some software on the specified source node will timeout. |
cpp-ucode |
LOG_STD_ACTION |
|
IPC-3-ACKSEND |
3-Error |
sending to [chars]: [chars] |
Sending an acknowledgement reply to the specified source failed for the given reason with the likely result that some software on the source will timeout. |
cpp-ucode |
LOG_STD_ACTION |
|
IPC-3-APP_IPC_FAIL |
3-Error |
[chars] failed. IPC Error: [chars] [dec] |
IPC Application Process failed to do some operation with the IPC Layer. The message includes the error code from ipc layer |
ipc |
show ipc status |
|
IPC-3-APP_IPC_FAIL |
3-Error |
[chars] failed. IPC Error: [chars] [dec] |
IPC Application Process failed to do some operation with the IPC Layer. The message includes the error code from ipc layer |
ipc |
show ipc status |
|
IPC-3-BADLENGTH |
3-Error |
IPC length [dec] > received length [dec] to sub device [dec] with fc code [dec] |
The length field in an IPC packet was larger than the number of bytes actually in the packet. |
cpp-ucode |
LOG_STD_ACTION |
|
IPC-3-BADMSG |
3-Error |
received type [dec] |
An IPC message was received containing an invalid message type. |
cpp-ucode |
LOG_STD_ACTION |
|
IPC-3-BADRSTATE |
3-Error |
Received ICP msg state [dec] |
Received IPC message while connection not ACTIVE |
cpp-ucode |
LOG_STD_ACTION |
|
IPC-3-BADSEQ |
3-Error |
got [dec] expected [dec] from [chars] |
- |
- |
- |
|
IPC-3-CNTALLOC |
3-Error |
IPC control msg subtype [dec] |
Allocating an IPC control message failed. |
cpp-ucode |
LOG_STD_ACTION |
|
IPC-3-CNTSEND |
3-Error |
sending ICP msg subtype [dec] to [chars]: [chars] |
Sending an ICP control message to the specified source failed for the given reason. Message should will be retried |
cpp-ucode |
LOG_STD_ACTION |
|
IPC-3-CONTROL |
3-Error |
Unhandled message subtype [dec] |
An IPC control message was received containing an unrecognized type. |
cpp-ucode |
LOG_STD_ACTION |
|
IPC-3-CREATEFAIL |
3-Error |
IPC CREATE msg failed invalid [chars] [dec] |
IPC Create message had invalid parameter |
cpp-ucode |
LOG_STD_ACTION |
|
IPC-3-DELETED |
3-Error |
Attempt to delete an IPC message 0x[hec] a second time |
- |
- |
- |
|
IPC-3-DELETED |
3-Error |
Attempt to delete an IPC message 0x[hec] a second time |
- |
- |
- |
|
IPC-3-GIANT |
3-Error |
Request for giant IPC packet denied. Request size = [dec] |
Someone requested a message that was too large for the IPC system |
ipc |
"show tech-support ipc" |
|
IPC-3-GIANT |
3-Error |
Request for giant IPC packet denied. Request size = [dec] |
Someone requested a message that was too large for the IPC system |
ipc |
"show tech-support ipc" |
|
IPC-3-INIT_IN_PROGRESS |
3-Error |
IPC Message received before init complete |
Cannot process IPC packet until init stage is complete |
- |
LOG_STD_ACTION |
|
IPC-3-ISSU_API_ERR |
3-Error |
[chars] failed with error code [dec] |
ISSU API failed to do some operation for IPC layer The message includes the error code from ISSU library |
os-ipc |
show issu client |
|
IPC-3-ISSU_API_ERR |
3-Error |
[chars] failed with error code [dec] |
ISSU API failed to do some operation for IPC layer The message includes the error code from ISSU library |
os-ipc |
show issu client |
|
IPC-3-ISSU_ERROR |
3-Error |
[chars] failed with error code [dec] for seat [hec] |
ISSU API failed to do some operation for IPC layer The message includes the error code from ISSU library |
os-ipc |
show issu fsm |
|
IPC-3-ISSU_ERROR |
3-Error |
[chars] failed with error code [dec] for seat [hec] |
ISSU API failed to do some operation for IPC layer The message includes the error code from ISSU library |
os-ipc |
show issu fsm |
|
IPC-3-LOG_ERR |
3-Error |
[chars] CPP QoS Client Proxy failure |
QoS proxy failed because of receiving invalid sub-type or failed to allocate ipc response buffer. |
cpp-ucode |
LOG_STD_ACTION |
|
IPC-3-LOWBUFF |
3-Error |
The main IPC message header cache below application reserve count [dec]. |
- |
- |
- |
|
IPC-3-LOWBUFF |
3-Error |
The main IPC message header cache below application reserve count [dec]. |
- |
- |
- |
|
IPC-3-NOBUFF |
3-Error |
The [chars] IPC message header cache is empty |
The specified IPC message header cache is empty and an incoming IPC message may be dropped as a result. |
ipc |
"show tech-support ipc" |
|
IPC-3-NOBUFF |
3-Error |
The [chars] IPC message header cache is empty |
The specified IPC message header cache is empty and an incoming IPC message may be dropped as a result. |
ipc |
"show tech-support ipc" |
|
IPC-3-NOHANDLER |
3-Error |
message type [dec] from [chars] |
An IPC message was received containing an unrecognized type. |
cpp-ucode |
LOG_STD_ACTION |
|
IPC-3-NOSRC |
3-Error |
packet from id [dec] |
Received an IPC packet from an unrecognized source node with the specified ID. |
cpp-ucode |
LOG_STD_ACTION |
|
IPC-3-NULL_SESSION |
3-Error |
unable to process ipc mcast message - no member session for dest_port_info %p group 0x[hec] session [dec] For appclass [chars] |
IPC Mcast message has been received for a NULL session |
ipc |
show ipc mcast session verbose |
|
IPC-3-PGENALLOC |
3-Error |
[dec] bytes |
Allocating a packet of the specified size failed. |
cpp-ucode |
LOG_STD_ACTION |
|
IPC-3-PGENSEND |
3-Error |
[chars] |
Sending a generated packet failed for the specified reason. |
cpp-ucode |
LOG_STD_ACTION |
|
IPC-3-PROXY_IPC_ALLOC_FAILED |
3-Error |
Allocate IPC message by [chars] failed - [chars] |
Allocation of an IPC packet buffer by proxy failed. |
cpp-ucode |
LOG_STD_ACTION |
|
IPC-3-PROXY_IPC_SEND_FAILED |
3-Error |
Attempt to send IPC message by [chars] failed with [chars] |
Transmission of an IPC message by proxy failed. |
cpp-ucode |
LOG_STD_ACTION |
|
IPC-3-REPLY |
3-Error |
unexpected from [chars] |
An unexpected reply was received from the specified source. |
cpp-ucode |
LOG_STD_ACTION |
|
IPC-3-TOOBIG |
3-Error |
message type [dec] length [dec] offset [hec] from [chars] |
The length field in an IPC message was found to extend beyond the packet that contained it. |
cpp-ucode |
LOG_STD_ACTION |
|
IPC-3-TOOSMALL |
3-Error |
message type [dec] length [dec] offset [hec] from [chars] |
The length field in an IPC message was smaller than the IPC msg header length. |
cpp-ucode |
LOG_STD_ACTION |
|
IPC-4-CONSISTENCY |
4-Warning |
Consistency check failed for [chars] 0x[hec] |
Debug Message. An action attempted by the IPC module has encountered an unexpected state in its/clients data structures. |
ipc |
"show tech-support ipc" |
|
IPC-4-CONSISTENCY |
4-Warning |
Consistency check failed for [chars] 0x[hec] |
Debug Message. An action attempted by the IPC module has encountered an unexpected state in its/clients data structures. |
ipc |
"show tech-support ipc" |
|
IPC-4-GET_PAK_MSG |
4-Warning |
Failed for message size [dec] |
System unable to allocate IPC message of required size. |
ipc |
"If this error message recurs copy the error message exactly" " as it appears on the console or in the system log contact" " your Cisco technical support representative with the" " gathered information." "\n\nTo display total memory usage for a router enter " "<CmdBold>show memory summary<noCmdBold> at the privileged " "command line prompt. To display buffer usage enter " "<CmdBold>show buffers<noCmdBold> at the prompt. To display IPC " "usage enter <CmdBold>show ipc queue<noCmdBold> at the prompt" |
|
IPC-4-GET_PAK_MSG |
4-Warning |
Failed for message size [dec] |
System unable to allocate IPC message of required size. |
ipc |
"If this error message recurs copy the error message exactly" " as it appears on the console or in the system log contact" " your Cisco technical support representative with the" " gathered information." "\n\nTo display total memory usage for a router enter " "<CmdBold>show memory summary<noCmdBold> at the privileged " "command line prompt. To display buffer usage enter " "<CmdBold>show buffers<noCmdBold> at the prompt. To display IPC " "usage enter <CmdBold>show ipc queue<noCmdBold> at the prompt" |
|
IPC-4-MESSAGE_ERR |
4-Warning |
Consistency check failed for IPC Message. IPC message 0x[hec] and port information 0x[hec] differ |
Debug Message. An action attempted by the IPC module has encountered an unexpected state in its/clients data structures. |
ipc |
"show ipc ports" |
|
IPC-4-MESSAGE_ERR |
4-Warning |
Consistency check failed for IPC Message. IPC message 0x[hec] and port information 0x[hec] differ |
Debug Message. An action attempted by the IPC module has encountered an unexpected state in its/clients data structures. |
ipc |
"show ipc ports" |
|
IPC-4-NOPORT |
4-Warning |
Port Not Found. [hec] --> [hec] Index:[hec] Seq: [dec] flags: [hec] size: [dec] |
IPC Received a message which is destined for a port that cannot be found by IPC |
ipc |
"Capture 'sh ipc status' 'sh ipc ports' and" " 'deb ipc errors' outputs and contact TAC" |
|
IPC-4-NOPORT |
4-Warning |
Port Not Found. [hec] --> [hec] Index:[hec] Seq: [dec] flags: [hec] size: [dec] |
IPC Received a message which is destined for a port that cannot be found by IPC |
ipc |
"Capture 'sh ipc status' 'sh ipc ports' and" " 'deb ipc errors' outputs and contact TAC" |
|
IPC-5-FC_OFF |
5-Notice |
SEAT FC is turned off for Seat [hec] Port ID [hec] Port Index [dec] Portinfo [hec] Last sent [dec] Last Heard [dec] Last xmitted [dec] Last Ack [dec] Ack Pending [dec] Last AckXmitted [dec] |
SEAT FC is being turned off |
ipc |
"show tech-support ipc" |
|
IPC-5-FC_ON |
5-Notice |
SEAT FC is turned on for Seat [hec] Port ID [hec] Port Index [dec] Portinfo [hec] Last sent [dec] Last Heard [dec] Last xmitted [dec] Last Ack [dec] Ack Pending [dec] Last Ack xmitted [dec] |
SEAT FC is being turned on Wait for it to be turned off . |
ipc |
"show tech-support ipc" |
|
IPC-5-INVALID |
5-Notice |
[chars] Dest Port 0x[hec] Session 0x[hec] Source 0x[hec] |
While processing an incoming message IPC encountered invalid data in its internal data structures. |
ipc |
"show tech-support ipc" |
|
IPC-5-INVALID |
5-Notice |
[chars] Dest Port 0x[hec] Session 0x[hec] Source 0x[hec] |
While processing an incoming message IPC encountered invalid data in its internal data structures. |
ipc |
"show tech-support ipc" |
|
IPC-5-INVALIDINPUT |
5-Notice |
[chars] |
IPC API is called with invalid argument. |
os-ipc |
LOG_STD_RECUR_ACTION |
|
IPC-5-INVALIDINPUT |
5-Notice |
[chars] |
IPC API is called with invalid argument. |
os-ipc |
LOG_STD_RECUR_ACTION |
|
IPC-5-MSG_NULL |
5-Notice |
[chars] |
IPC message returned is Null |
ipc |
"show tech-support ipc" |
|
IPC-5-MSG_NULL |
5-Notice |
[chars] |
IPC message returned is Null |
ipc |
"show tech-support ipc" |
|
IPC-5-NOCALLBACK |
5-Notice |
[chars]: Flow control callback function is not provided by IPC Client [chars] |
An IPC application cannot be controlled if flow need to be slowed down. This might result in drop of IPC packets |
ipc |
"show ipc ports" |
|
IPC-5-NOCALLBACK |
5-Notice |
[chars]: Flow control callback function is not provided by IPC Client [chars] |
An IPC application cannot be controlled if flow need to be slowed down. This might result in drop of IPC packets |
ipc |
"show ipc ports" |
|
IPC-5-NODELFUNC |
5-Notice |
Failed to intialize IPC client |
An IPC application cannot be initialized because its initialization\n function does not appear in the IPC initialization list. |
ipc |
"show tech-support ipc" |
|
IPC-5-NODELFUNC |
5-Notice |
Failed to intialize IPC client |
An IPC application cannot be initialized because its initialization\n function does not appear in the IPC initialization list. |
ipc |
"show tech-support ipc" |
|
IPC-5-NULL |
5-Notice |
[chars] [chars]=0x[hec] [chars] 0x[hec] |
IPC module could not find an IPC entity that is expected to be existing always |
ipc |
"show tech-support ipc" |
|
IPC-5-NULL |
5-Notice |
[chars] [chars]=0x[hec] [chars] 0x[hec] |
IPC module could not find an IPC entity that is expected to be existing always |
ipc |
"show tech-support ipc" |
|
IPC-5-NULL_HEADER |
5-Notice |
[chars] MSG: ptr: %p flags: 0x[hec] |
IPC message header accessed from IPC message is NULL |
ipc |
"show tech-support ipc" |
|
IPC-5-NULLBPHANDLER |
5-Notice |
Passed Null backpressure handler |
The maximum message timeout for an IPC message exceeds 2 minutes |
ipc |
"Capture 'sh version' and contact TAC" |
|
IPC-5-NULLBPHANDLER |
5-Notice |
Passed Null backpressure handler |
The maximum message timeout for an IPC message exceeds 2 minutes |
ipc |
"Capture 'sh version' and contact TAC" |
|
IPC-5-NULLDELFUNC |
5-Notice |
Invalid registration |
An IPC application has attempted to register NULL function in the IPC initialization list. |
ipc |
"show tech-support ipc" |
|
IPC-5-NULLDELFUNC |
5-Notice |
Invalid registration |
An IPC application has attempted to register NULL function in the IPC initialization list. |
ipc |
"show tech-support ipc" |
|
IPC-5-QFULL |
5-Notice |
Q=0x[hec] [chars] [dec] |
IPC queue is full. |
os-ipc |
LOG_STD_SH_TECH_ACTION |
|
IPC-5-QFULL |
5-Notice |
Q=0x[hec] [chars] [dec] |
IPC queue is full. |
os-ipc |
LOG_STD_SH_TECH_ACTION |
|
IPC-5-REGPORTFAIL |
5-Notice |
[chars] [chars]=0x[hec] [chars]=0x[hec] |
Several IPC messages are pending to be processed. If the number increases it may result in the IPC header cache or buffers being exhausted. |
ipc |
"show tech-support ipc" |
|
IPC-5-REGPORTFAIL |
5-Notice |
[chars] [chars]=0x[hec] [chars]=0x[hec] |
IPC failed to register the control port |
ipc |
LOG_STD_RECUR_ACTION |
|
IPC-5-RPCFULL |
5-Notice |
Cannot hold RPC message port: [hex] index: [dec] type: [hex] |
An RPC request for an application could not be added to the RPC request table because pending requests have filled the RPC request table. |
ipc |
"show tech-support ipc" |
|
IPC-5-RPCFULL |
5-Notice |
Cannot hold RPC message port: [hex] index: [dec] type: [hex] |
An RPC request for an application could not be added to the RPC request table because pending requests have filled the RPC request table. |
ipc |
"show tech-support ipc" |
|
IPC-5-SEND_APP_MSG_FAILED |
5-Notice |
Send message to peer for [chars] failed. Reason: [chars] |
Client using IPC App Port has not been able to send message |
ipc |
"If the reason is 'no such port' then this may be caused because" " of the difference in the versions of IOS running on Active" " and the standby. Any other reason please collect 'sh ipc stat'" " 'sh ipc rpc' 'sh ipc port' on active and standby RPs and " " contact tac" |
|
IPC-5-SEND_APP_MSG_FAILED |
5-Notice |
Send message to peer for [chars] failed. Reason: [chars] |
Client using IPC App Port has not been able to send message |
ipc |
"If the reason is 'no such port' then this may be caused because" " of the difference in the versions of IOS running on Active" " and the standby. Any other reason please collect 'sh ipc stat'" " 'sh ipc rpc' 'sh ipc port' on active and standby RPs and " " contact tac" |
|
IPC-5-SLAVELOG |
5-Notice |
VIP-[chars] |
The Cisco IOS software running on a Versatile Interface Processor VIP card generated this message. The error message has been |
high-vip |
"This is actually a Cisco IOS error message from a VIP. Handle " "it as indicated by the text after the 'VIP-' string in the " "error message." |
|
IPC-5-SLAVELOG |
5-Notice |
VIP-[chars] |
The Cisco IOS software running on a Versatile Interface Processor VIP card generated this message. The error message has been |
high-vip |
"This is actually a Cisco IOS error message from a VIP. Handle " "it as indicated by the text after the 'VIP-' string in the " "error message." |
|
IPC-5-WATERMARK |
5-Notice |
[dec] messages pending in [chars] for the port [chars][hec].[hec] from source seat [hec] |
- |
- |
- |
|
IPC-6-ACKRETRY |
6-Information |
required [dec] retries |
Allocating an IPC acknowledgement failed on the first attempt but succeeded on a later attempt. |
cpp-ucode |
LOG_STD_ACTION |
|
IPC-6-KEEPALIVE |
6-Information |
Rcvd keepalive from seat 0x[hec] msglen=[dec] |
An IPC Keepalive message sent for every 10 sec |
ipc |
"This is normal behavior" |
|
IPC-6-MAXRPCTIMEOUT |
6-Information |
Maximum RPC timeout value [dec] seconds set for port 0x[hec] |
The maximum RPC timeout for an IPC message exceeds the maximum expected value of 10 minutes |
ipc |
"Capture 'show techsupport ipc' and contact TAC" |
|
IPC-6-MAXRPCTIMEOUT |
6-Information |
Maximum RPC timeout value [dec] seconds set for port 0x[hec] |
The maximum RPC timeout for an IPC message exceeds the maximum expected value of 10 minutes. If you are using MOS IPC it may report some fake RPC timeouts at the receiver |
ipc |
"Capture 'show techsupport ipc' and contact TAC" |
|
IPC-6-STATEFUL |
6-Information |
[chars] |
A Stateful IPC Event occurred |
ipc |
"This is not a bug but just an informational message." |
|
IPC-6-STATEFUL |
6-Information |
[chars] |
A Stateful IPC Event occurred |
ipc |
"" |
|
IPC-7-RECYCLE_HEADER_ALLOC_FAIL |
7-Debug |
Unable to alloc gpm for recycle header |
An IPC message need memory to build recycle header. |
cpp-ucode |
LOG_STD_ACTION |
|
IPC-7-RECYCLE_TAIL_DROP |
7-Debug |
Dropping IPC packet due to recycle queue full |
An IPC message can't recycled due to queue full. |
cpp-ucode |
LOG_STD_ACTION |
|
IPCGRP-3-CARDERR |
3-Error |
[chars] |
An IPC card has registered itself to the IPC master twice. The card malfunctioned and its IPC is not active. |
ubr7200-sw |
LOG_STD_ACTION |
|
IPCGRP-3-CMDOP |
3-Error |
IPC command [dec] slot[dec]/[dec]: [chars] |
IPC command processing operational errors. |
ubr7200-sw |
LOG_STD_ACTION |
|
IPCGRP-3-CREATE_FAIL |
3-Error |
[chars] [chars] |
Failed to create IPC port on RP. |
ubr7200-sw |
LOG_STD_ACTION |
|
IPCGRP-3-ENQFAIL |
3-Error |
enqueue failed! queue:[chars] size:[dec] |
process_enqueue failed. |
ubr7200-sw |
LOG_STD_ACTION |
|
IPCGRP-3-ERROR |
3-Error |
[chars]: [chars] |
An IPC error was detected |
ubr7200-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
IPCGRP-3-EVENTOP |
3-Error |
Event [dec] from slot[dec]/[dec]: [chars] |
IPC event processing operational errors. |
ubr7200-sw |
LOG_STD_ACTION |
|
IPCGRP-3-EXECCMDMSG |
3-Error |
Incorrect msg size size=[dec] |
Wrong size of a REXEC-On IPC command. |
ubr7200-sw |
LOG_STD_ACTION |
|
IPCGRP-3-INVALID_PARAMS |
3-Error |
Invalid interface[dec]/[dec]/[dec] |
Invalid interface addressed by the corresponding IPC message. |
ubr7200-sw |
LOG_STD_ACTION |
|
IPCGRP-3-INVNUM |
3-Error |
[chars] [dec] |
- |
- |
- |
|
IPCGRP-3-LOADQUACKFAIL |
3-Error |
slot [dec] load quack data failed! |
load quack data failed. |
ubr7200-sw |
LOG_STD_ACTION |
|
IPCGRP-3-MSGERR |
3-Error |
[chars] [dec] |
The slave IPC cannot register with master. It cannot exchange messages with the master. |
ubr7200-sw |
LOG_STD_ACTION |
|
IPCGRP-3-NBLKCMD |
3-Error |
[chars] |
Nonblocking IPC command queue initialization failure. |
ubr7200-sw |
LOG_STD_ACTION |
|
IPCGRP-3-NOHWIDB |
3-Error |
Cannot find hwidb for interface[dec]/[dec] |
Interface identifier does not exist for the interface addressed by the corresponding IPC message. |
ubr7200-sw |
LOG_STD_ACTION |
|
IPCGRP-3-NULLMSG |
3-Error |
Null [chars] ipc message |
An empty IPC message which is not expected to be received. |
ubr7200-sw |
LOG_STD_ACTION |
|
IPCGRP-3-NULLREXECCMD |
3-Error |
Received empty ipc rexec cmd message |
REXEC-On IPC command failure. |
ubr7200-sw |
LOG_STD_ACTION |
|
IPCGRP-3-REXEC |
3-Error |
[chars] |
REXEC-On IPC command failure. |
ubr7200-sw |
LOG_STD_ACTION |
|
IPCGRP-3-SEATERR |
3-Error |
[chars] [dec] |
The ID associated with an IPC card is either missing duplicated or cannot be created. |
ubr7200-sw |
LOG_STD_ACTION |
|
IPCGRP-3-SYSCALL |
3-Error |
System call for command [dec] slot[dec]/[dec] : [chars] Cause: [chars] |
- |
- |
- |
|
IPCGRP-6-NBLKCMD_Q_FULL |
6-Information |
Nonblocking IPC command queue full [dec] commands |
- |
- |
- |
|
IPCOIR-2-CARD_UP_DOWN |
2-Critical |
Card in slot [dec]/[dec] is [chars]. Notifying [chars] driver. |
Notification of a Line Card coming Up or Down. |
ubr7200-sw |
LOG_STD_NO_ACTION |
|
IPCOIR-2-CREATEFAIL |
2-Critical |
Couldn't create [chars] |
Could not create specified resource |
ubr7200-sw |
"Contact customer support." |
|
IPCOIR-2-NULL_PTR |
2-Critical |
[chars]: pointer is null |
Unexpected NULL pointer to a data structure. |
ubr7200-sw |
LOG_STD_SH_TECH_ACTION |
|
IPCOIR-2-PLUGIN_PREANALYZE_FAIL |
2-Critical |
Unable to preanalyze driver plugin in slot [dec]/[dec]. |
A valid linecard driver preanalyze failed. |
ubr7200-sw |
"Possibly incompatible card types" |
|
IPCOIR-3-BADIPHOST |
3-Error |
Bad IP address or host name [chars] |
The IP address or host name is incorrect or unknown. |
ubr7200-sw |
"Check the IP address or hostname." |
|
IPCOIR-3-BADLCAPI |
3-Error |
Incorrect API message version 0x[hec] |
The linecard and IOS images are badly out of phase. |
ubr7200-sw |
"Contact customer support." |
|
IPCOIR-3-BADMESSVER |
3-Error |
Incorrect message version obj 0x[hec] op 0x[hec] version 0x[hec] |
The linecard and IOS images are badly out of phase. |
ubr7200-sw |
"Contact customer support." |
|
IPCOIR-3-BOGUSCARD |
3-Error |
Bogus cardtype [dec] |
The indicated cardtype is unknown to the software. |
ubr7200-sw |
LOG_STD_SH_TECH_ACTION |
|
IPCOIR-3-CARD_BADIDPROM |
3-Error |
Card in slot [dec]/[dec] has an invalid card type in IDPROM |
The linecard IDPROM is unprogrammed or has failed. |
ubr7200-sw |
"Contact customer support." |
|
IPCOIR-3-CARD_GET_VERSION_RESPONSE |
3-Error |
Unsolicited response from slot [dec]/[dec] oir_state = [chars] |
Unexpected message from a Line Card. |
ubr7200-sw |
LOG_STD_SH_TECH_ACTION |
|
IPCOIR-3-CARD_UNSUPPORTED |
3-Error |
Unsupported card type 0x[hec] in slot [dec]/[dec]. |
The linecard is not supported by this version of IOS |
ubr7200-sw |
"Contact customer support." |
|
IPCOIR-3-CARDCRASH |
3-Error |
Card crashed in slot [dec]/[dec]. |
IPC message reporting wrong version received from an operational card. |
ubr7200-sw |
LOG_STD_SH_TECH_ACTION |
|
IPCOIR-3-CRE_INIT_FAIL |
3-Error |
Unable to initialize PRE ports. |
The PRE plugin init sequence failed. |
ubr7200-sw |
"Determine and fix cause." |
|
IPCOIR-3-FLASHFAIL |
3-Error |
Couldn't load [chars]...\n |
The indicated image is inaccessible |
ubr7200-sw |
"Check the filename." |
|
IPCOIR-3-IMAGEVERSION |
3-Error |
Image version stamp missing |
The loaded image did not contain a recognizable version stamp |
ubr7200-sw |
"Replace the image with known-good bits and try again." |
|
IPCOIR-3-IPC_GET_MSG_BUF_FAIL |
3-Error |
Unable to get an IPC msg buffer in [dec] tries: slot [dec]/[dec] |
The IOS IPC buffer pool was empty for a sustained period of time. |
ubr7200-sw |
"Install more processor SDRAM in the PRE." |
|
IPCOIR-3-KEEPALIVE |
3-Error |
A keepalive timeout occurred on slot [dec]/[dec].\n Last process: [chars] 4ms time = [dec]ms Intr. Busy Count: [dec] Sched Flag Count: [dec] |
The line card has stopped responding to keepalive polls while in the RUN state. The attached debug information was provided by the line card. |
ubr7200-sw |
"Monitor the LC for a persistent problem. Keep the console log of " "each occurrence and if the problem occurs again forward the log to " "Cisco." |
|
IPCOIR-3-LC4MS |
3-Error |
The watchdog timer on slot [dec]/0 has stopped. |
The line card has stopped servicing it's watchdog timer. |
ubr7200-sw |
"The condition may be temporary or may be caused by a crash. " "Check the LC's bootflash for crashinfo files and monitor " "the LC for a watchdog timeout." |
|
IPCOIR-3-LCCRASH |
3-Error |
The card in slot [dec]/[dec] has crashed. Cause Register: 0x%0x Signal: %0u |
The line card in the specified slot has crashed. |
ubr7200-sw |
"Wait for the LC to come back up then connect to the remote console and " "extract the crashinfo file from bootflash. Forward the file the " "output from a show tech command and the NPE console log to Cisco." |
|
IPCOIR-3-LOADER_DNLD_NOBUF |
3-Error |
Buffer allocation failed |
The buffer downloader couldn't allocate a message buffer. |
ubr7200-sw |
"Reboot the chassis." |
|
IPCOIR-3-LOADER_DNLD_REJECT |
3-Error |
Buffer download to slot [dec]/[dec] rejected |
The linecard buffer download server rejected the download. |
ubr7200-sw |
LOG_STD_ACTION |
|
IPCOIR-3-LOADER_IPC_FAIL |
3-Error |
IPC failed [chars] [chars] slot [dec]/[dec] |
The IOS IPC protocol reported an unexpected error. |
ubr7200-sw |
"Make sure the indicated card is still plugged in." |
|
IPCOIR-3-LOADER_SERVER_FAIL |
3-Error |
Remote server refused to load slot [dec]/[dec] |
Unable to load a Line Card. Load will be attempted again. |
ubr7200-sw |
LOG_STD_ACTION |
|
IPCOIR-3-PLUGIN_INIT_FAIL |
3-Error |
Unable to create driver plugin in slot [dec]/[dec]. |
A valid linecard driver plugin create failed. |
ubr7200-sw |
"Perhaps a memory allocation failure should not happen." |
|
IPCOIR-3-STATE_MACHINE_BUG |
3-Error |
card_oir_loading called should never happen recovering. |
An internal software error occurred. Will recover. |
ubr7200-sw |
LOG_STD_SH_TECH_ACTION |
|
IPCOIR-3-STATE_MACHINE_BUG2 |
3-Error |
card_oir_insert_card: already have 0x[hec] removing. |
An internal software error occurred. |
ubr7200-sw |
LOG_STD_SH_TECH_ACTION |
|
IPCOIR-3-TFTPFAIL |
3-Error |
TFTP of [chars] from [chars] failed...\n |
The indicated image is inaccessible |
ubr7200-sw |
"Check file permissions network connectivity." |
|
IPCOIR-3-TIMEOUT |
3-Error |
Timeout waiting for a response from slot [dec]/[dec]. |
NPE lost connection with a Line Card. Line Card might have crashed. |
ubr7200-sw |
LOG_STD_SH_TECH_ACTION |
|
IPCOIR-3-WRONGCARDTYPE |
3-Error |
Wrong card type in slot [dec]/[dec]. |
IPC message reporting wrong card type received from an operational card. |
ubr7200-sw |
LOG_STD_SH_TECH_ACTION |
|
IPCOIR-4-IPC_GET_MSG_BUF |
4-Warning |
Get IPC msg buf failed [dec] times: slot [dec]/[dec] - retry in [dec] sec |
The IOS IPC buffer pool was temporarily empty. |
ubr7200-sw |
"Consider installing more processor SDRAM in the PRE." |
|
IPCOIR-4-REPEATMSG |
4-Warning |
IPC handle already exists for [dec]/[dec] |
IPC communication between the NPE and a Line Card already setup |
ubr7200-sw |
"Reload the specified linecard. If the message recurs call your " "techical support representative for assistance." |
|
IPCOIR-5-CARD_DETECTED |
5-Notice |
Card type [chars] 0x[hec] in slot [dec]/[dec] |
A card was detected in the indicated slot. |
ubr7200-sw |
LOG_STD_NO_ACTION |
|
IPCOIR-5-CARD_LOADING |
5-Notice |
Loading card in slot [dec]/[dec] |
Notification of a Line Card download with MD5 data. |
ubr7200-sw |
LOG_STD_NO_ACTION |
|
IPCOIR-6-LCWAITINFO |
6-Information |
CLC [dec]/[dec]> [chars] |
The NPE OIR handler received a console error message from a distributed line card while in the crashwait state. The handler enters this state when it detects a Keepalive timeout on a distributed line card. During the crash wait period the LC is expected to collect and store crash information. At the end of the wait period the NPE will reload the LC. During this time it's possible that the LC will try to send error messages to it's console. Normally these would be sent to the NPE via the logger. However during the wait period the IPC link between the NPE and the LC is down so the OIR debug code provides a rudimentary method of collecting and displaying these messages |
ubr7200-sw |
"Report the problem to Cisco. Include the log messages along with the " "output of the show tech command and crashinfo file from the LC." |
|
IPDR-2-ERROR_SOCKET |
2-Critical |
\n Receive a wrong socket id [dec] |
The socket to close is not exist or belong to the ipdr process |
cmts-application |
LOG_STD_SH_TECH_ACTION |
|
IPDR-2-GENERAL_ERR_SOCKET |
2-Critical |
\n [chars] |
encounter some error when binding listening or receiving the event from the socket fd |
cmts-application |
LOG_STD_SH_TECH_ACTION |
|
IPE-2-HOST_SECURITY_VIOLATION |
2-Critical |
Security violation occurred caused by IP address [inet] on port [chars]. |
An unauthorized device attempted to connect on a secure port. The IP address of the unauthorized device and the secure port are specified in the error message. |
ipe |
"Determine the device that attempted to connect on the secure port." "Notify your network system administrator of this condition." |
|
IPE-3-DUPLICATE_CONFIG_MASTER |
3-Error |
Multiple Configuration Masters in domain [chars]. Use \show ipe errors\ command to check for errors. |
There must be one Configuration Masters in every IPe domain. |
ipe |
"Make sure that there is only one Forwarder configured as the " "Configuration Master in a domain. Use \"show ipe errors\" " "command to identify the forwarders and fix the error condition" |
|
IPE-3-PG_ACL_RESOURCE |
3-Error |
Failed to allocate an internal ACL resource needed for Policy Gateway |
An attempt to allocate an internal ACL failed. |
ipe |
LOG_STD_ACTION |
|
IPE-3-PG_VLAN_RESOURCE |
3-Error |
Failed to allocate an internal vlan resource needed for Policy Gateway |
An attempt to allocate an internal vlan failed. |
ipe |
"Please check the config and make sure that vlan resources " "are available" |
|
IPE-3-SBINIT |
3-Error |
Error initializing [chars] subblock data structure. [chars] |
Initialization of the specified subblock data structure could not be accomplished. |
ipe |
LOG_STD_ACTION |
|
IPE-3-STATICHOST |
3-Error |
Failed to add [chars] entry for host [inet] of tableid [dec] |
An internal software error occurred. |
ipe |
LOG_STD_ACTION |
|
IPE-4-DUPLICATE_HOST |
4-Warning |
Host [inet] is attached to multiple forwarders. Use \show ipe errors\ command to check for possible errors. |
In a host move scenario it is possible that a host is transiently attached to multiple forwarders during IPe convergence. However it is an error if a host continues to be attached to multiple forwarders. |
ipe |
"Use \"show ipe errors\" command to identify the forwarders where " "the host is reported to be attached and fix the error condition." |
|
IPE-4-DUPLICATE_LOCAL_HOST |
4-Warning |
Host [inet] on interface [chars] has duplicate ip address. |
If existing host has been removed it is possible that this is a transient condition. An expedited ARP track is started on existing host to remove the entry if the host is no longer there. Once existing entry is removed host addition will be possible. However it is an error if multiple hosts continue to use duplicate address. |
ipe |
"Use \"show ip host mapping\" command to identify the interface where " "the host is reported to be attached and remove the duplicate ip " "address from one of the hosts." |
|
IPFAST-2-FAILOPENIPCPORT |
2-Critical |
Could not open the IPC ports. [chars] |
ipfast could not open the ipc port to communicate to the LC/RRP/SP. |
- |
LOG_STD_SH_TECH_ACTION |
|
IPFAST-2-INVALSIZE |
2-Critical |
The IP fast path received an IPC message with an invalid sizesize/type - [dec]/[dec] |
- |
- |
- |
|
IPFAST-2-IPCACHEINIT |
2-Critical |
Error initializing IP fast cache structures |
A programming error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
IPFAST-2-MSGDROP |
2-Critical |
IPC queue limit is reached and message is dropped. queue limit = [dec] cumulative drops = [dec] |
IPC raw queue limit for IP fast path is reached. |
- |
LOG_STD_ACTION |
|
IPFAST-2-RADIXINIT |
2-Critical |
Error initializing IP fast cache structures |
A programming error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
IPFAST-6-PAKSHORT |
6-Information |
Packet too short from [inet] datagram size [dec] tl [dec] |
An IP packet which is too short was received |
- |
LOG_STD_NO_ACTION |
|
IPFLOW-2-CACHEINIT |
2-Critical |
Error initializing IP flow cache |
Initialization of the Flow cache could not be accomplished because of \n\ a low memory condition. |
netflow-switch |
LOG_STD_SH_TECH_ACTION |
|
IPFLOW-2-EXPORTINIT |
2-Critical |
Error initializing Flow Export queue |
Initialization of the Flow export queue could not be accomplished \n\ because of a low memory condition. |
netflow-switch |
"Reduce other system activitiy to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
IPFLOW-2-PROCESSINIT |
2-Critical |
Error initializing Flow background process |
Initialization of the Flow background process could not be accomplished because of a low memory condition. |
netflow-switch |
"Reduce other system activitiy to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
IPFLOW-2-QUEUEINIT |
2-Critical |
Error initializing Flow feature queue |
Initialization of the Flow feature queue could not be accomplished because of a low memory condition. |
netflow-switch |
"Reduce other system activitiy to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
IPFLOW-2-TEMPLATETBL_INIT |
2-Critical |
Error initializing Flow Export Template Table |
Initialization of the Flow export template table could not be \n\ accomplished because of a low memory condition. |
netflow-switch |
"Reduce other system activitiy to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
IPFLOW-3-DISABLEFLOWEXPORT |
3-Error |
NULL |
Flow export is disabled because export destination address matches with one of the interface's IP addresses |
netflow-switch |
"IP addresses of all the interfaces must be checked to make sure none \n\ of them matches with flow export destination IP address." |
|
IPFLOW-3-SBINIT |
3-Error |
Error initializing [chars] subblock data structure. [chars] |
Initialization of the specified subblock data structure could not be accomplished. |
netflow-switch |
- |
|
IPFLOW-4-V9_TEMPLATE_EXPORT |
4-Warning |
Error creating [chars] |
Version 9 export template length is zero |
netflow-switch |
LOG_STD_DBG_ACTION |
|
IPMCAST_LIB_GIR-3-MCAST_GIR_CLIENT_NOT_FOUND |
3-Error |
Failed to find multicast GIR client for vrf [chars] |
Failed to find multicast GIR client |
ipmulticast |
LOG_STD_ACTION |
|
IPMCAST_LIB_RPF-3-DUPLICATE_RW_CONTEXT |
3-Error |
Specified multicast route watch client registration context is already in use. |
The context specified for a multicast route watch client registration request is already in use. The client registration request can not be processed. Multicast traffic flow may be degraded by failure to correctly determine RPF state information. |
ipmulticast |
LOG_STD_ACTION |
|
IPMCAST_LIB_RPF-3-INTERNAL_ERROR |
3-Error |
An internal error has occured while obtaining RPF information [chars] |
RPF handling Internal error |
ipmulticast |
LOG_STD_RECUR_ACTION |
|
IPMCAST_LIB_RPF-3-INVALID_RW_CONTEXT |
3-Error |
Invalid context specified for a multicast route watch client. |
An invalid context was specified for handling a multicast route watch update. Multicast traffic flow may be degraded by failure to correctly determine RPF state information. |
ipmulticast |
LOG_STD_ACTION |
|
IPMCAST_LIB_RPF-3-RIB_REGISTER_FAIL |
3-Error |
Failed to register with RIB multicast RPF lookups will not function |
Multicast could not register with RIB to obtain RPF information later. This will cause severe problem when there is multicast traffic flow since it will not be possible to obtain RPF information |
ipmulticast |
LOG_STD_ACTION |
|
IPMCAST_LIB_RPF-3-RW_INIT_FAIL |
3-Error |
Failed to START/STOP Route-watch debugging for '[chars]' |
Multicast could not START or STOP Route-watch debugging for the specific Address-family IPv4/IPv6 listed. |
ipmulticast |
LOG_STD_ACTION |
|
IPMCAST_LIB_RPF-3-RW_START_FAIL |
3-Error |
Error trying to start RPF route watch for prefix [chars] in table [dec] [chars] RPF information will not be obtained |
- |
- |
- |
|
IPMCAST_LIB_RPF-3-STOP_FAIL |
3-Error |
Error trying to stop RPF watch for a prefix |
Internal error has occured while trying to stop obtaining RPF change information |
ipmulticast |
LOG_STD_RECUR_ACTION |
|
IPMCAST_LIB_RPF-4-RIB_UNREGISTER_FAIL |
4-Warning |
Multicast failed to unregister with RIB |
Multicast could not unregister with RIB when multicast is disabled. There will not be any existing traffic flow since multicast is already disabled. However if enabled again and if problem is seen with multicast traffic flow it should be reported |
ipmulticast |
LOG_STD_ACTION |
|
IPMCAST_LIB_RPF-4-RTMGR_TOPO_ERR |
4-Warning |
Unexpected error accessing topology specific information |
An internal error has occured while accessing topology specific information. The RPF information may not be obtained resulting in problems with multicast flows |
ipmulticast |
LOG_STD_ACTION |
|
IPMCAST_LIB_STR-3-MCAST_STRING_COPY_ERROR |
3-Error |
Multicast string copy failure |
Multicast string copy failure |
ipmulticast |
LOG_STD_ACTION |
|
IPMCAST_LIB_STR-4-MCAST_STRING_COPY_BUF_OVERFLOW |
4-Warning |
Multicast string copy overflow |
Multicast string copy overflow |
ipmulticast |
LOG_STD_ACTION |
|
IPMCAST_LIB-3-IPMCAST_LIMIT_SYNC |
3-Error |
Failed to sync multicast limit state to the standby RP |
An internal failure prevented sending of multicast limit information to the standby RP. Some multicast traffic disruption is possible following a route processor failover. |
ipmulticast |
LOG_STD_NO_ACTION |
|
IPMCAST_LIB-3-MEMORY_ERR |
3-Error |
Not enough memory. [chars] |
Memory not available for allocating requested object. |
ipmulticast |
LOG_STD_ACTION |
|
IPMCAST_LIB-3-TIMER_ERR |
3-Error |
Unexpected error in the timer library: [chars] |
Internal error |
ipmulticast |
LOG_STD_ACTION |
|
IPMCAST_LIB-3-VRF_CTX_ERR |
3-Error |
[chars] Ctx: 0x[hec] |
Failure in updating the LIB VRF Context structures. |
ipmulticast |
LOG_STD_ACTION |
|
IPMCAST_LIB-4-IPMCAST_LIMIT |
4-Warning |
Adding [chars] interface '[chars]' denied for [chars][chars] |
The maximum number of times the given interface appears as incoming or outgoing for some multicast state is reached. |
ipmulticast |
LOG_STD_NO_ACTION |
|
IPMCAST_LIB-4-IPMCAST_LIMIT_THRESHOLD |
4-Warning |
[chars] interface '[chars]' for [chars][chars] [chars] %lld |
The maximum number of times the given interface appears as incoming or outgoing for some multicast state has reached threshold of its configured limit. |
ipmulticast |
"The configured multicast limit for some interface" " has reached the threshold of its configured mCAC" " limit. Please take proactive measures at this point" " like increasing the mCAC limit." |
|
IPMCAST_LIB-4-UNEXPECTED_CONDITION |
4-Warning |
Unexpected condition: [chars] |
An un expected condition situation state or event has been detected. |
ipmulticast |
LOG_STD_NO_ACTION |
|
IPMCAST_LIB-4-UNKNOWN_EVENT_ERR |
4-Warning |
Unexpected event received: [dec] |
No handler found for event |
ipmulticast |
LOG_STD_ACTION |
|
IPMCAST_LIB-6-EVENT_Q_SIZE |
6-Information |
The event queue size has exceeded [dec] |
Processing may become slower |
ipmulticast |
LOG_STD_NO_ACTION |
|
IPMCAST_LIB-6-TIMER_BUSY |
6-Information |
Timer drift is accumulating [dec] msecs |
There is large amount of processin load and the timers are accumulating delay. |
ipmulticast |
LOG_STD_RECUR_ACTION |
|
IPMCAST_RPF-3-INTERNAL_ERROR |
3-Error |
An internal error has occured while obtaining RPF information [chars] |
RPF handling Internal error |
ipmulticast |
LOG_STD_RECUR_ACTION |
|
IPMCAST_RPF-4-FOREIGN_VRF |
4-Warning |
RPF for [inet] VRF [chars] resolves in a foreign VRF [chars] |
- |
- |
- |
|
IPMCAST_RPF-4-RPF_LOOKUP_LOOP |
4-Warning |
RPF route lookup loop for [inet] |
A routing loop occurred during the recursive resolution of an RPF address |
ipmulticast |
"Check routing tables used for RPF" |
|
IPMCAST_RPF-5-RPF_LISP_INIT_FAILURE |
5-Notice |
RPF lookup: LISP registration for [chars] not completed |
LISP watch info initialization not ready |
ipmulticast |
LOG_STD_NO_ACTION |
|
IPMOBILE-0-IPMOBILE_DHCP |
0-Emergency |
\ [chars] |
Two reasons for this error message\n\ 1. DHCP Client failed to get started this could be because of malloc\n\ failures.\n\ 2. IPMOBILE DHCP Process failed to start |
mobileip |
"If this error message is seen it is recommended not to use this\n\ HA for binding creation with DHCP Address Allocation.\n\ Check the available memory in the box and for the first reason try\n\ to get 'debug dhcp detail' before the failure.\n\ Contact your technical support representative with the error\n\ message you got." |
|
IPMOBILE-0-NOPROCESS |
0-Emergency |
\ [chars] |
A Process could not be started |
- |
"Please contact your technical support representative\n\ with the error message you got and with the output of\n\ 'show process '." |
|
IPMOBILE-2-ASSERTFAILED |
2-Critical |
IPMOBILE assertion failed: [chars] |
The software detected an inconsistency. This is considered a\n\ serious error. The router attempts to continue but IP Mobility\n\ processing may be impaired. |
mobileip |
"Copy the error message exactly as it appears noting any IP Mobility\n\ problems that you are experiencing and report it to your technical\n\ support representative." |
|
IPMOBILE-3-CONFIGERROR |
3-Error |
Standby FA configuration is not in sync with the active |
The software detected an inconsistency in configuration between\n\ the standby and the active. Standby FA may not proceed with the\n\ sync for this visitor. |
mobileip |
"Re-configure standby FA and make sure the configuration between\n\ the standby and the active is in sync." |
|
IPMOBILE-3-NOSOCKET |
3-Error |
Unable to open socket |
The requested operation could not be accomplished because of a low\n\ memory condition. |
mobileip |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
IPMOBILE-3-NOTUNNEL |
3-Error |
Maximum number of tunnels [dec] reached |
The number of Mobile IP tunnels allowed on the box is reached. |
mobileip |
"This occures if the HA/FA is overloaded. \n\ If you suspect this condition contact technical\n\ support representative with the output of show tech" |
|
IPMOBILE-3-SA_PARSE_FAILED |
3-Error |
Error in parsing the security association for [chars] |
The Mobile IP Home Agent encountered an error while processing the Security Association in the RADIUS Access-Accept message. |
mobileip |
"Check the Radius profile config for the Mobile Node for which " "the processing of the Security Association failed." |
|
IPMOBILE-5-MIP_TUNNELDELETE |
5-Notice |
Mobile IP tunnel [chars] deleting |
The Mobile IP tunnel is going to be deleted. |
mobileip |
"This occurs if the active mobile ip binding is \n\ deleted.\n\ If you suspect this condition contact technical\n\ support representative with the output of show tech" |
|
IPMOBILE-6-REDUPDATEFAIL |
6-Information |
Too many redundancy update failures [dec] in the last minute. |
A mobile router's attempt to dynamically add or delete a\n\ mobile network failed because that mobile network was already\n\ configured as a virtual network in the home agent. |
mobileip |
"To avoid duplication errors make sure that the virtual networks\n\ configuration on the home agent and the dynamic mobile network\n\ configuration on the mobile router do not have any overlapping\n\ network prefixes." |
|
IPMOBILE-6-SECURE |
6-Information |
Security violation on [chars] from [chars] [chars] - errcode [chars] [dec] |
A security violation occurred during registration attempt. |
mobileip |
"This is for informational purpose only." |
|
IPMUX-3-V4_CACHE_FULL |
3-Error |
IPMux V4 Cache full - replacing active entry |
The IPMux V4 cache is full and has replaced a current cache entry. \n\ IP Multiplexing performance may be impacted if this continues. |
ipmux |
"Increase the size of the cache using the \n\ 'ip mux cache' configuration command." |
|
IPMUX-3-V6_CACHE_FULL |
3-Error |
IPMux V6 Cache full - replacing active entry |
The IPMux V6 cache is full and has replaced a current cache entry. \n\ IP Multiplexing performance may be impacted if this continues. |
ipmux |
"Increase the size of the cache using the \n\ 'ipv6 mux cache' configuration command." |
|
IPNAT_HA-3-ATTRIBUTE |
3-Error |
Bulk sync of [chars] via [chars] [chars] is invalid for [chars] |
An attempt to bulk sync an address pool or a dynamic/static\n\ translation has detected that the entity which is to be sent to the\n\ standby RP when acting in a stateful redundant mode contains an\n\ invalid owner property and hence cannot be synchronized. The detection\n\ of this case will result in a failure of the bulk sync. |
nat |
LOG_STD_ACTION |
|
IPNAT_HA-3-BULK_SYNC |
3-Error |
Failed to send [chars] information to peer |
- |
nat |
LOG_STD_ACTION |
|
IPNAT_HA-3-CLIENT |
3-Error |
Failed to register with [chars] [chars] |
The NAT High Availability has failed to register with the specified\n\ component during initialization. This is an internal error which\n\ indicates that the NAT HA services will be unavailable. |
nat |
LOG_STD_ACTION |
|
IPNAT_HA-3-DECODE |
3-Error |
Decode via [chars] of [chars] failed |
A message of the transport and type described failed in its attempt\n\ to be decoded on the standby. The resultant action taken by the\n\ standby route processor is an attempt to resynchronize. |
nat |
LOG_STD_ACTION |
|
IPNAT_HA-3-DYN_DEFERQ |
3-Error |
[chars] failed to defer[chars] |
The incremental synchronization of the NAT dynamic state to the standby\n\ RP has failed to add the information to the deferral queue for later\n\ processing during the time where the standby RP is progressing to it's\n\ hot standby redundant state. This implies that the runtime state\n\ between the active and standby RP would be inconsistent once the\n\ standby has been fully initialized. |
nat |
"show ip nat ha" |
|
IPNAT_HA-3-DYN_SYNC |
3-Error |
Failed to process [chars] dynamic state |
The incremental synchronization of the NAT configuration to the standby\n\ RP has failed to complete successfully. This implies that the\n\ configuration state between the active and standby RP is\n\ inconsistent. |
nat |
"show ip nat ha" |
|
IPNAT_HA-3-INTERFACE_TYPE |
3-Error |
[chars] type/slot %lx unit %lu num %lu channel %lu value [dec] |
An attempt to sync a dynamic translation or address change has\n\ detected that the interface which was encoded on the active RP\n\ has a different type the standby RP. The detection of this\n\ case will result in a failure of the bulk or LBL sync. |
nat |
LOG_STD_ACTION |
|
IPNAT_HA-3-MISMATCH |
3-Error |
[chars] [chars] mismatch with id [dec] |
The specified synchronization operation has failed to complete on the\n\ standby route processor due to an inconsistency in the internal id\n\ which would have resulted in an inconsistent configuration between\n\ active and standby. The resultant action taken by the standby route\n\ processor is an attempt to resynchronize. |
nat |
LOG_STD_ACTION |
|
IPNAT_HA-3-PURGE |
3-Error |
Failed to purge [chars] information |
- |
nat |
LOG_STD_ACTION |
|
IPNAT_HA-3-RECEIVE |
3-Error |
Message via [chars] is [chars] |
An ISSU registration for the set of initial capabilities and sessions\n\ failed due to the reason specified. This will have the effect of the\n\ NAT ISSU support being unavailable between peers. |
nat |
LOG_STD_ACTION |
|
IPNAT_HA-3-TRANSFORM |
3-Error |
[chars] of [chars] via [chars] failed [chars] |
An attempt to either encode or decode a versioned synchronization\n\ message has failed due to an internal error encountered by the ISSU\n\ component. |
nat |
LOG_STD_ACTION |
|
IPNAT_HA-6-ADDR_CHANGE |
6-Information |
[chars] unable to encode data descriptor for interface [chars] |
An attempt to sync an address change to the standby RP has\n\ detected that the interface which was to be encoded on the\n\ active RP is no longer present or does not support encoding. \n\ The interface may have been removed from the configuration or \n\ may not support encoding. |
- |
LOG_STD_ACTION |
|
IPNAT_HA-6-INTERFACE |
6-Information |
[chars] type/slot %lx uint %lu num %lu channel %lu |
An attempt to sync a dynamic translation or address change has\n\ detected that the interface which was encoded on the active RP\n\ is not present on the standby RP. The detection of this case\n\ may result in a failure of the bulk or LBL sync. |
nat |
LOG_STD_ACTION |
|
IPNAT_HA-6-MAPPING_COMPARE |
6-Information |
[chars] [chars] [chars] mapping id [dec] comparing [chars] [chars] [chars] mapping id [dec] |
The specified synchronization operation on the standby route processor\n\ has detected an internal condition with respect to the properities of\n\ dynamic mappings. This is informational. |
nat |
LOG_STD_ACTION |
|
IPNAT_HA-6-MAPPING_EXISTS |
6-Information |
[chars] [chars] [chars] mapping id [dec] |
The specified synchronization operation on the standby route processor\n\ has detected the presence of an existing matching mapping. This may\n\ be associated with any observed PRC failures on the standby. |
nat |
LOG_STD_ACTION |
|
IPNAT_HA-6-READY |
6-Information |
[chars] peer not ready discarding [chars] |
The synchronization attempt for the message has determined that the\n\ transport has lost communication with its peer. This is a normal\n\ situation which indicates that the standby route-processor is currently\n\ out of service implying a simplex redundancy mode. |
- |
- |
|
IPNAT_HA-6-RELOAD |
6-Information |
[chars] reloading [chars] |
A synchronization attempt between the active and standby RP peers has\n\ failed with the reason indicated. The standby peer is reloaded in an\n\ attempt to resynchronize when operating in a stateful redundant\n\ mode. |
nat |
LOG_STD_ACTION |
|
IPNAT_HA-6-RELOAD_DISABLED |
6-Information |
Standby reload has been disabled NAT RP state is out of sync and the standby should be reloaded manually |
The active and standby RPs are out of sync and the standby RP would have been reloaded but this reload was suppressed based on the configured environment. |
nat |
LOG_STD_ACTION |
|
IPNAT_HA-6-TIMEOUT |
6-Information |
Bulk sync is flow controlled by [chars] |
The bulk synchronization of the NAT configuration to the standby RP\n\ has encountered a flow control condition which has effected a timeout\n\ awaiting the condition to clear. This will result in a reload of the\n\ standby RP to allow the bulk synchronization to restart. |
nat |
LOG_STD_ACTION |
|
IPNAT-3-BADMAPPINGTYPE |
3-Error |
NAT mapping type [dec] for mapping statistics from platform is \n\ invalid |
The mapping type for passing mapping statistics from platform is \n\ not for static nor dynamic mapping type which is invalid. This \n\ condition can cause the statistic counters for NAT mapping to be\n\ inaccurate on the RP |
nat |
LOG_STD_ACTION |
|
IPNAT-3-CENTRAL_POLICY |
3-Error |
Central policy setting failed: [chars] |
Central policy setting can not be changed due to incompatible configuration. |
nat |
"Remove existing NAT routes and mappings." |
|
IPNAT-3-CONFIG |
3-Error |
Unable to [chars] the configuration of dynamic mappings |
An internal operation relating to the configuration of the\n\ dynamic mappings has failed. This may imply that the mapping\n\ has not been installed. |
nat |
LOG_STD_ACTION |
|
IPNAT-3-CSBNULL |
3-Error |
Parser structure for route-map [chars] configuration is nul |
The parser structure for route-map configuraion is nul which is invalid. This condition can cause the new translations to fail in \n\ the data path |
nat |
LOG_STD_ACTION |
|
IPNAT-3-IF_UP |
3-Error |
Error in sending interface UP event for [chars] to the ager process |
An internal operation relating to the interface UP event\n\ has failed which is unexpected. |
nat |
LOG_STD_ACTION |
|
IPNAT-3-LIMITSTATSNULL |
3-Error |
NAT mexentry statistics structure from platform is nul |
The structure for passing maxentry limit statistics from platform is \n\ nul which is invalid. This condition can cause the statistic\n\ counters for NAT maxentry limit to be inaccurate on the RP |
nat |
LOG_STD_ACTION |
|
IPNAT-3-MAPPING_NULL |
3-Error |
Unexpected NULL pointer received as input. |
An internal operation relating to notifying the platform about a\n\ mapping has provided an unexpected input. |
nat |
LOG_STD_ACTION |
|
IPNAT-3-MAPPINGSTATSNULL |
3-Error |
NAT mapping statistics structure from platform is nul |
The structure for passing mapping statistics from platform is \n\ nul which is invalid. This condition can cause the statistic\n\ counters for NAT mapping to be inaccurate on the RP |
nat |
LOG_STD_ACTION |
|
IPNAT-3-POOLSTATSNULL |
3-Error |
NAT pool statistics structure from platform is nul |
The structure for passing global/systems stats from platform \n\ is nul which is invalid. This condition can cause the statistic\n\ counters for NAT pool to be inaccurate on the RP |
nat |
LOG_STD_ACTION |
|
IPNAT-3-PORTLISTNULL |
3-Error |
Portlist for address [inet] proto [dec] is nul |
The portlist for the address which requests more port blocks \n\ is nul which is invalid. This condition can cause the new \n\ translations to fail in the data path |
nat |
LOG_STD_ACTION |
|
IPNAT-3-PORTNULL |
3-Error |
Start port or end port for port block allocation request is nul |
Start port or end port for port block allocation request is nul\n\ This condition can cause the new translations to fail in the \n\ data path |
nat |
LOG_STD_ACTION |
|
IPNAT-3-RTMAPNAMENULL |
3-Error |
Route-map name for [chars] configuration is nul |
The route-map name is nul which is invalid. This condition can cause the new translations to fail in the data path |
nat |
LOG_STD_ACTION |
|
IPNAT-3-RTMAPNULL |
3-Error |
route-map for configuration download is nul |
The route-map structure is nul which is invalid. This condition\n\ can cause the new translations to fail in the data path |
nat |
LOG_STD_ACTION |
|
IPNAT-3-SBINIT |
3-Error |
Error initializing [chars] subblock data structure. [chars] |
Initialization of the specified subblock data structure could not be accomplished. |
nat |
- |
|
IPNAT-3-SYSSTATSNULL |
3-Error |
NAT global/system statistics structure from platform is nul |
The structure for passing global/systems statistics from platform \n\ is nul which is invalid. This condition can cause the NAT global\n\ statistic counters in inaccurate on the RP |
nat |
LOG_STD_ACTION |
|
IPNAT-3-UNEXPECTED_ADDRESS |
3-Error |
NULL |
An address contained an unexpected value. |
nat |
LOG_STD_ACTION |
|
IPNAT-3-UNEXPECTED_MAPPING_FLAG |
3-Error |
Unexpected mapping flag %#04x received |
An internal operation relating to notifying the platform about a\n\ mapping has provided an unexpected input. |
nat |
LOG_STD_ACTION |
|
IPNAT-3-WLANSESSNULL |
3-Error |
NAT WLAN session structure for session [chars] from platform is nul |
The structure for passing WLAN session from platform is \n\ nul which is invalid. This condition can cause the NAT WLAN\n\ session to fail in the data path |
nat |
LOG_STD_ACTION |
|
IPNAT-4-ADDR_ALLOC_FAILURE |
4-Warning |
Address allocation failed for [inet] pool [chars] might be exhausted |
An address could not be allocated from the IP NAT pool. This condition can cause a translation failure and might result in packets being dropped. The counter for misses will be incremented for these packets. |
nat |
"Check to see if the NAT pool has been exhausted. To reuse any existing " "addresses in the NAT pool for new packet flows clear the current NAT " "entries using clear ip nat translation *" |
|
IPNAT-6-ENTRIES |
6-Information |
Static translation count reset inside/outside source/destination %llu/%llu %llu/%llu |
Upon the removal of the last remaining static translation from the\n\ configuration it has been determined that there is a discrepancy\n\ with the internal accounting as regards the previous provisioning\n\ of inside source/destination versus outside source entries. The\n\ internal accounting has been reset to indicate that there are no\n\ translations of any type currently. |
nat |
LOG_STD_ACTION |
|
IPNAT-6-ID |
6-Information |
[chars] identifier has wrapped |
The identifier which is assigned to that which is resultant from\n\ the configuration in question has cycled through the available\n\ number space and is now allocating from its initial value again. |
nat |
LOG_STD_NO_ACTION |
|
IPNAT-6-PORT_ALLOC |
6-Information |
Port allocation via [chars] for [dec] [chars] [chars] ports min [dec] max [dec] |
A port allocation request for the specified range of ports has been\n\ attempted from the named party on the standby RP. This is an\n\ informational message which tracks the request source. |
nat |
LOG_STD_ACTION |
|
IPRT-2-COMPRESS |
2-Critical |
Bad route_compress call sdb= [hec] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-2-IPTABLEERROR |
2-Critical |
IP routing table [chars] initialization failure - [chars] |
An internal software error occurred preventing the creation of new IP routing table. |
- |
"Copy the message exactly as it appears and report it to your " "technical support representative." |
|
IPRT-3-BAD_MSGTYPE_ERROR |
3-Error |
ION RIB error: [chars] [dec]/[hec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-BAD_PDB_HANDLE |
3-Error |
Pdb handle error %04x %04x [hec] %08x %04x %02x |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-BAD_PDB_INDEX |
3-Error |
Pdb index error %08x %04x [hec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-BADCOMLIST |
3-Error |
Community list check with bad list [dec] |
A user specified an invalid BGP community list number. |
- |
"Check the system configuration to make sure that the community list " "specified falls within the valid range." |
|
IPRT-3-BADRFREG |
3-Error |
Unable to register IP Routing as a client of RF. |
This is a severe error as far as IP routing NSF is concerned |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
IPRT-3-CFORK |
3-Error |
Old-style routing processes no longer supported |
RIB_INT_ERR_EXPLANATION |
ip |
LOG_STD_RECUR_ACTION |
|
IPRT-3-CSB_SAVE_DATA_BAD_MAGIC |
3-Error |
Bad magic for CSB Data [hec] |
RIB_INT_ERR_EXPLANATION |
ribinfra |
LOG_STD_RECUR_ACTION |
|
IPRT-3-GETEACHROUTE_BAD_MAGIC |
3-Error |
Bad magic for ip_geteachroute |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-HMI_INIT_ERROR |
3-Error |
Unable to init HMI database |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-INCONSISTENT_TOPOID_ERROR |
3-Error |
Inconsistent topology id topoid:0x[hec] and topoid:0x[hec] are found for the topology[chars] |
- |
- |
- |
|
IPRT-3-INVALID_NEXTHOP |
3-Error |
[chars] ID 0x[hec] [inet]%m from [chars] Gwy: [inet] [chars] Binding Label: [chars] Type:0x[hec] Attr 0x[hec] Has Repair Path: [dec] Repair Gwy: [inet] [chars] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-INVALID_RIBUPDATE_STATE |
3-Error |
Invalid RIB State for update 0x[hec] [inet]%m [chars] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-INVALIDTOPO |
3-Error |
Bad topology [chars] table in static routing entry [inet]%m |
An error has occurred when a static route failed to find corresponding topology routing table. |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-INVALIDVRF_BFD |
3-Error |
Bad vrf_id 0x[hec] in static BFD neighbor [chars] [inet] |
A static BFD neighbor failed to find corresponding vrf. |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-IPDB_DEL_ERROR |
3-Error |
i_pdb delete error [chars] [hec] [hec] [hec] [hec] [hec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-IPTABLEINIT |
3-Error |
IP routing table creation failure - [chars] |
An internal software error occurred preventing the creation of new IP routing table. |
- |
"Copy the message exactly as it appears and report it to your " "technical support representative." |
|
IPRT-3-MAXALLOWEDLIMITREACHED |
3-Error |
Maximum allowed static route count reached: [dec] \n ip_addstatic_route failed \n |
The maximum number of static routes that can be configured is reached. No further routes will be added to the table |
- |
"Remove the unwanted static routes to add more routes" |
|
IPRT-3-NDB_BAD_MAGIC |
3-Error |
Bad magic for NDB structure [hec]/[hec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-NDB_CREATE_ERROR |
3-Error |
Error creating an NDB - [chars] [dec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-NDB_DEL_ERROR |
3-Error |
Error Removing an NDB [chars] [inet]%m tid 0x[hec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-NDB_NRP_IN_PROGRESS |
3-Error |
Invalid action on NDB while in NRP in progress: [chars] 0x[hec] [inet]%m state [dec] flags [hec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-NDB_ONQ |
3-Error |
Queue elem on queue - [inet]%m |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-NDB_PDB_MATCH_INVALID |
3-Error |
Invalid ndb_pdb_match_type 0x[hec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-NDB_REPLIC_INVALID_OP |
3-Error |
Invalid operation on replicated NDB [chars]: |
RIB_INT_ERR_EXPLANATION |
ribinfra |
LOG_STD_RECUR_ACTION |
|
IPRT-3-NDB_STATE_ERROR |
3-Error |
NDB state error [chars] 0x[hec] [inet]%m state [dec] event [hec]->[hec] nh_type [hec] flags [hec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-NDBSHR_BAD_MAGIC |
3-Error |
Bad magic for NDBSHR structure [hec]/[hec]/[hec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-NEXTHOPS_LIST_ERROR |
3-Error |
[chars]: [inet]%m [dec] [hec] [hec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-NEXTHOPS_LIST_MISMATCH |
3-Error |
[chars]: [chars] [inet]%m nhtype: [hec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-NO_BACKUP_MEM |
3-Error |
No Backup Route memory available for [chars] |
The addition of a Backup Route failed because of a low memory condition. Backup may not be available if the Primary Route is removed |
- |
"Reduce other system activity to ease memory demands. If conditions " "warrant upgrade to a larger memory configuration." |
|
IPRT-3-NO_MAJORNET_NDB |
3-Error |
No majornet found: [chars] [inet]%m |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-NO_PDB_INDEX |
3-Error |
Pdb index not available for [chars] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-NO_REPLIC_MEM |
3-Error |
No Route Replication memory available for [inet]%m |
The replication of a Route failed because of a low memory condition. The route will not be replicated in the destination table at this time. |
- |
"Reduce other system activity to ease memory demands. If conditions " "warrant upgrade to a larger memory configuration." |
|
IPRT-3-NO_RIB_TABLE |
3-Error |
RIB table lookup failure: [hec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-NOMEMORY |
3-Error |
No memory available for [chars] |
The requested operation failed because of a low memory condition. |
- |
"Reduce other system activity to ease memory demands. If conditions " "warrant upgrade to a larger memory configuration." |
|
IPRT-3-NOTEXIST_BFD |
3-Error |
Static BFD neighbor does not exist: [chars] [chars] [inet] |
Failed to find corresponding static BFD neighbor. |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-NOTREG_BFD |
3-Error |
Unexpected reachability notification: [chars] [chars] [inet] |
Gateway is not tracked by BFD. |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-NOTSAMEOWNER |
3-Error |
SAME_PROTO dist_status [dec] from [chars] for route owned by [chars] |
- |
- |
- |
|
IPRT-3-NULL_NDB |
3-Error |
Unexpected null NDB |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-NULL_NDBSHR |
3-Error |
Unexpected null NDBSHR [hec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-NULL_RDB |
3-Error |
Unexpected null RDB |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-NULL_RDBSHR |
3-Error |
Unexpected null RDBSHR [hec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-PARSER_REG_ERROR |
3-Error |
Unable to register [chars] submode translation callback mode = 0x%X |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-PATHIDX |
3-Error |
Bad path pointer of [hec] for [inet] [dec] max |
A software error occurred. |
- |
LOG_STD_ACTION |
|
IPRT-3-PDB_DEL_ERROR |
3-Error |
Pdb delete error [chars] [hec] [hec] [hec] [hec] [hec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-PDB_STATIC_ERROR |
3-Error |
Static pdb procinfo is NULL |
RIB_INT_ERR_EXPLANATION |
ip |
LOG_STD_RECUR_ACTION |
|
IPRT-3-PROTOFLTR_INVALID_ACL_TYPE |
3-Error |
Invalid ACL type [dec] is configured. |
RIB_INT_ERR_EXPLANATION |
ribinfra |
LOG_STD_RECUR_ACTION |
|
IPRT-3-PROTOFLTR_ROUTE_MAP_CONFIG_ERROR |
3-Error |
Protocol filter routemap [chars] configuration failed |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-PROTOFLTR_SB_ADD_ERROR |
3-Error |
Topology 0x[hec] interface [chars] add sub-block failed for sb_type [dec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-RDB_BAD_MAGIC |
3-Error |
Bad magic for RDB structure [hec]/[hec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-RDBSHR_BAD_MAGIC |
3-Error |
Bad magic for RDBSHR structure [hec]/[hec]/[hec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-RESPAWN_COUNT_ERROR |
3-Error |
Unable to get process respawn count |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-RIB_ACC_HDLR_INIT |
3-Error |
Error Registering [chars] RIB handlers with RIB Access Infra |
An internal software error occurred preventing Access to RIB Data. |
ribinfra |
"Copy the message exactly as it appears and report it to your " "technical support representative." |
|
IPRT-3-RIB_INTERNAL_ERR |
3-Error |
[chars] |
RIB_INT_ERR_EXPLANATION |
ribinfra |
LOG_STD_RECUR_ACTION |
|
IPRT-3-RIB_LOOP |
3-Error |
Resolution loop formed by routes in RIB |
RIB route producers have installed routes in the RIB that form a loop during resolution. |
- |
"Resolve the RIB route resolution loop:\n" "1 Determine which routes are involved in the loop by issuing the " |
|
IPRT-3-RIBTABLEERROR |
3-Error |
RIB error [dec] on [chars] - [chars] |
An internal software error occurred processing an event associated with a routing table. |
- |
"Copy the message exactly as it appears and report it to your " "technical support representative." |
|
IPRT-3-ROUTEINSERTERROR |
3-Error |
Error inserting routing entry [inet]%m into IP [chars] routing table |
An error has occurred when a routing entry was being inserted into the IP routing table. |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-ROUTELIMITEXCEEDED |
3-Error |
IP routing table limit exceeded - [chars] |
The number of routes in the named IP routing table has reached the configured limit. No further routes will be added to the table |
- |
"Reduce the number of routes in the table or reconfigure the limit" |
|
IPRT-3-ROUTELIMITWARNING |
3-Error |
IP routing table limit warning - [chars] |
The number of routes in the named IP routing table has reached the configured warning limit. |
- |
"Reduce the number of routes in the table or reconfigure the limit" |
|
IPRT-3-ROUTEREPLACEERROR |
3-Error |
Error replacing route to [inet]%m with better route in IP [chars] routing table |
Copy the message exactly as it appears and report it to your technical support representative. |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-STATIC_GWIF_INCONSISTENCE |
3-Error |
Inconsistence static route database [chars] [chars] [inet] |
- |
- |
- |
|
IPRT-3-STATIC_SR_POLICY_INCONSISTENCE |
3-Error |
Inconsistence static route database due to [chars] on [inet]%m via policy [chars] [dec] |
- |
- |
- |
|
IPRT-3-STATICDBINCONSISTENCE |
3-Error |
Inconsistent static route database due to [chars] on [inet]%m on [chars] via [inet] |
An error has occurred due to inconsistence on static route table. |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-STATICROUTES_ADDFAILED |
3-Error |
Failed to add static route to database [chars] on [inet]%m on [chars] via [inet] |
An error has occurred due to failed add on static route table. |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-STATICROUTES_FAILED_RW_START |
3-Error |
Failed to start route watch for topology [chars] gateway [inet]%m flag 0x[hec] rc [dec] |
An error has occurred failed to start route watch for this static route. |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-STATICROUTES_FAILED_RW_STOP |
3-Error |
Failed to stop route watch for static route handle [hec] route watch handle [hec] gateway [inet] interface [chars] rc [dec] |
An error has occurred due to failed to stop route watch for this static route. |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-STATICROUTES_RWATCH_FAILED_GET_INFO |
3-Error |
Failed to get the route info through route watch |
An internal error has occurred which could cause inconsistence routing table due to route watch |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-STATICROUTES_RWATCH_FAILED_LOOP |
3-Error |
Route watch failed to determine to keep a loop or not |
An internal error has occurred which could cause inconsistence routing table due to route watch |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-STATICROUTES_RWATCH_FAILED_SIG |
3-Error |
Failed to get the correct route watch signature [hec] |
An internal error has occurred which could cause inconsistence routing table due to route watch |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-STATICROUTES_TOPOLOCK |
3-Error |
Unable to lock topology [chars] table in static route |
An error has occurred when a static route failed to lock corresponding topology routing table. |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-TOPO_HANDLE_ERROR |
3-Error |
Unable to get topology handler topoid = [dec] [chars] |
RIB_INT_ERR_EXPLANATION |
ip |
LOG_STD_RECUR_ACTION |
|
IPRT-3-VIAUPD_ALLOC_ERROR |
3-Error |
Error allocating [dec] next hops for [inet]%m via [inet]%m |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-3-VIAUPD_ERROR |
3-Error |
Error [dec] inserting additional path for [inet]%m via [inet]%m |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-4-BADRIBDB |
4-Warning |
Attempt to remove a next hop from the wrong table. Attempted: [chars] should be: [chars] prefix: [inet] |
Attempt to remove a next hop from the wrong routing table |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-4-BADTRACKOBJECTTYPE |
4-Warning |
can't track this type of object |
Route maps only support STATE type track objects. This object is not a STATE object |
- |
"Reconfigure the track object to make it a STATE object." |
|
IPRT-4-INVALID_NRP_CONTEXT |
4-Warning |
Invalid context type: [dec] state: [dec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-4-NDB_STATE_CHANGE |
4-Warning |
NDB state change: [inet]%m [hec]->[hec] [dec]->[dec] [hec] refcnt [dec] tid [dec] cnt [dec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-4-RECURSIVE_ERASE |
4-Warning |
Recursive erase [dec] [hec]/[hec] [hec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-4-REDIST_MAX_PFX |
4-Warning |
Redistribution prefix limit has been reached \[chars]\ - [dec] prefixes |
We have reached the maximum number of redistributed prefixes |
- |
"Check if redistribution of large number of prefixes is " "desired and has not been configured by mistake" |
|
IPRT-4-REDIST_THR_PFX |
4-Warning |
Redistribution prefix threshold has been reached \[chars]\ - [dec] prefixes |
We have reached the threshold level of number of redistributed prefixes |
- |
"Check if redistribution of large number of prefixes is " "desired and has not been configured by mistake" |
|
IPRT-4-RIB_DEBUG_ERROR |
4-Warning |
Generic RIB error: [hec] [hec] [hec] [hec] [hec] [hec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-4-RIB_DELETE_PENDING_ERROR |
4-Warning |
RIB Marked Delete Pending in wrong state: [hec] [dec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-4-ROUTECOUNTNEGATIVE |
4-Warning |
IP route counter negative - [chars] [inet] Attempt: [dec] |
Attempt to decrement IP route counter into negative value |
ribinfra |
"Use "clear ip route *" command to reset the route counter. If " "the message still comes out consistently copy the messages exactly " "as they appear and report it to your technical support " "representative." |
|
IPRT-4-RWATCH_BFDNEIGHBOR_CREATE_ERROR |
4-Warning |
RIB Rwatch failed to create bfd neighbor session proctype [dec] src_topoid [hec] dst_topoid [hec] [chars][chars][chars] neighbor [chars] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-4-RWATCH_BFDNEIGHBOR_SESS_WAVL_INSERT_ERROR |
4-Warning |
RIB Rwatch failed to insert bfd neighbor session into WAVL tree proctype [dec] topoid [hec] [chars] neighbor [chars] |
RIB_INT_ERR_EXPLANATION |
ribinfra |
LOG_STD_RECUR_ACTION |
|
IPRT-4-RWATCH_NEIGHBOR_WAVL_DELETE_ERROR |
4-Warning |
RIB Rwatch neighbor not found in WAVL tree for deletion client : [chars] topoid : [hec] interface : [chars] binding label: [chars] address : [chars] |
RIB_INT_ERR_EXPLANATION |
ribinfra |
LOG_STD_RECUR_ACTION |
|
IPRT-4-RWATCH_TRKSN_DELETE_ERROR |
4-Warning |
RIB Rwatch tracked sequence number [dec] not found for client : [chars] topoid : [hec] prefix : [chars] prefix_len : [dec] |
RIB_INT_ERR_EXPLANATION |
ribinfra |
LOG_STD_RECUR_ACTION |
|
IPRT-4-RWATCH_UPCALL_INIT_ERROR |
4-Warning |
RIB Rwatch failed to initialize the upcall table afi [dec] |
RIB_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
IPRT-4-RWATCHUSAGEWARN |
4-Warning |
Route watch client-[chars] is calling the API from RIB context !! |
Improper usage of the API spotted from the caller.\n Check if the api was called directly from a notification callback |
- |
"Ideal usage is to enqueue the RWATCH notifications to a client process and the api should be called from client context" |
|
IPRT-5-STATICROUTES_BFD_EVENT |
5-Notice |
BFD session [chars][[chars]] |
An ipv4 static route BFD session has either come up or gone down \n The message describes the change for it. This message appears only if the <Bold>log<nobold> command is configured for the ipv4 static route BFD process. |
- |
"This informational message normally appears as routers and \n\ ipv4 static route BFD sessions go up or down." |
|
IPRT-6-DELETEINGTOP |
6-Information |
topology [chars] is deleting in static routing entry [inet]%m |
A static route found a corresponding deleting topology routing table. |
- |
"The action is not taken due to topology deleting state" |
|
IPRT-6-STATICROUTESACROSSTOPO |
6-Information |
Cannot install inter- topology static route [inet]%m topology [chars] on outgoing interface [chars] |
Restricting the access of static routes that point across topologies |
- |
"Remove the static routes that are pointing accross topology interfaces" |
|
IPRT-6-STATICROUTESACROSSVRF |
6-Information |
Un-installing static route [inet]%m from [chars] routing table with outgoing interface [chars] |
Restricting the access of static routes that point across vrfs |
- |
"Remove the static routes that are pointing accross VRF interfaces" |
|
IPSEC-3-ANTI_REPLAY |
3-Error |
SA 0x[hec]0x[hec] |
Anti Replay check failed for the SA. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-CHUNK_CREATE_FAIL |
3-Error |
- |
Chunk creation failed |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-CHUNK_DESTROY_ERROR |
3-Error |
- |
Chunk destroy error force cleanup |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-CHUNK_DESTROY_FAIL |
3-Error |
- |
Chunk destroy failed |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-DROP |
3-Error |
result type 0x[hec] |
Classification results in Drop. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-FOR_US_CLEARTEXT_POLICY_FAIL |
3-Error |
- |
Policy fail for For-Us cleartext packet. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-FRAG_ERROR |
3-Error |
IPSec SA received fragmented ESP packet DP Handle [dec] src_addr %Ci dest_addr %Ci SPI 0x[hec] |
Fragmented ESP packet is received for this IPSec session. |
qfp-ipsec |
LOG_STD_ACTION |
|
IPSEC-3-FRAG_ERROR_IPV6 |
3-Error |
IPSec SA received fragmented ESP packet DP Handle [dec] ipv6 src_addr [ipv6_addr], ipv6 dest_addr [ipv6_addr], SPI 0x[hec] |
Fragmented ESP packet is received for this IPSec session. |
qfp-ipsec |
LOG_STD_ACTION |
|
IPSEC-3-FRAG_MPASS |
3-Error |
- |
Multipass Error |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-HMAC_ERROR |
3-Error |
IPSec SA receives HMAC error DP Handle [dec] src_addr %Ci dest_addr %Ci SPI 0x[hec] |
HMAC calculation error is encountered for this IPSec session. |
qfp-ipsec |
LOG_STD_ACTION |
|
IPSEC-3-HMAC_ERROR_V6 |
3-Error |
IPSec SA receives HMAC error DP Handle [dec] ipv6 src_addr [ipv6_addr], ipv6 dest_addr [ipv6_addr], SPI 0x[hec] |
HMAC calculation error is encountered for this IPSec session. |
qfp-ipsec |
LOG_STD_ACTION |
|
IPSEC-3-IKE_TED_MSG_LIMIT |
3-Error |
cnt [dec] sp 0x[hec] cp sp 0x[hec] |
IKE TED Message Limit exceeded. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-IKE_TED_MSG_RATE |
3-Error |
cnt [dec] sp 0x[hec] cp sp 0x[hec] |
IKE TED Message Rate exceeded. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-IN_POLICY_FAIL |
3-Error |
out sa 0x[hec]0x[hec] out sp 0x[hec]0x[hec] in sa 0x[hec]0x[hec] in sp 0x[hec]0x[hec] |
In-Out SP mis-match. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-IN_POLICY_MISS |
3-Error |
sa 0x[hec] cp sa 0x[hec] |
TCAM miss. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-INTF_NOT_CFG |
3-Error |
- |
Got an encrypted packet on an interface on which ipsec is not configured. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-INVALID_PROT |
3-Error |
invalid ipsec prot 0x[hec] |
Got an invalid IPSEC protocol value. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-INVALID_SA |
3-Error |
sa 0x[hec] cp sa 0x[hec] |
SA is invalid. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-INVALID_SPI |
3-Error |
spi 0x[hec] |
Got an invalid SPI value. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-INVALID_VAL |
3-Error |
val 0x[hec] |
Invalid value seen. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-IPC_ERR_SA |
3-Error |
rc 0x[hec] |
An error has occurred sending SA Byte Lifetime expiry event. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-IPC_HANDLER_ERR |
3-Error |
rc 0x[hec] |
Error setting IPC Handler. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-IPC_INVALID_MSG_LEN |
3-Error |
[dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Invalid IPC message length |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-IPC_PAK_ALLOC |
3-Error |
sp 0x[hec] cp sp 0x[hec] |
IPC pak allocation failed. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-IPC_PAK_ALLOC_SA_EVENT |
3-Error |
event 0x[hec] sa 0x%llx |
IPC pak allocation failed. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-IPC_PAK_SEND |
3-Error |
rc 0x[hec] sp 0x[hec] cp sp 0x[hec] |
IPC send failed. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-IPC_PAK_SEND_SA_EVENT |
3-Error |
rc 0x[hec] event 0x[hec] sa 0x%llx |
IPC send failed. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-MEM_ALLOC_REACHED_LIMIT |
3-Error |
IPC type 0x[hec] |
Cannot allocate more memory to store state for IPSec Traffic reached upper limit. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-MEM_EXTEND_FAILED |
3-Error |
IPC type 0x[hec] |
Extending memory failed |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-MEM_REQ_FAILED |
3-Error |
IPC type 0x[hec] |
Requesting more memory failed. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-NO_MEMORY |
3-Error |
No memory 0x[hec] |
No memory to send response back. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-PKT_TOO_BIG |
3-Error |
IPSec Packet size [dec] larger than maximum supported size [dec] hence dropping it |
Maximum size for packet with IPSEC encapsulation is 9K This packet exceeded the size limit hence dropping it. |
qfp-ipsec |
LOG_STD_ACTION |
|
IPSEC-3-RECVD_PKT_NOT_IPSEC |
3-Error |
Rec'd packet not an IPSEC packet dest_addr= %Ci src_addr= %Ci prot= [dec]\n |
Rec'd packet matched crypto map ACL but is not IPSEC-encapsulated. |
qfp-ipsec |
LOG_STD_ACTION |
|
IPSEC-3-RECVD_PKT_NOT_IPSECV6 |
3-Error |
Rec'd packet not an IPSEC packet dest_addr= [ipv6_addr], src_addr= [ipv6_addr], prot= [dec]\n |
Rec'd packet matched crypto map ACL but is not IPSEC-encapsulated. |
qfp-ipsec |
LOG_STD_ACTION |
|
IPSEC-3-REPLAY_ERROR |
3-Error |
IPSec SA receives anti-replay error DP Handle [dec] src_addr %Ci dest_addr %Ci SPI 0x[hec] |
Anti-replay error is encountered for this IPSec session. |
qfp-ipsec |
LOG_STD_ACTION |
|
IPSEC-3-REPLAY_ERROR_IPV6 |
3-Error |
IPSec SA receives anti-replay error DP Handle [dec] ipv6 src_addr [ipv6_addr], ipv6 dest_addr [ipv6_addr], SPI 0x[hec] |
Anti-replay error is encountered for this IPSec session. |
qfp-ipsec |
LOG_STD_ACTION |
|
IPSEC-3-SA_HARD_BYTE |
3-Error |
SA 0x[hec]0x[hec] |
SA Hardbyte Lifetime expiry event. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-SA_NOT_FOUND |
3-Error |
- |
SA not found. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-SA_SOFT_BYTE |
3-Error |
SA 0x[hec]0x[hec] |
SA Softbyte Lifetime expiry event. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-SEQNO_OVERFLOW |
3-Error |
SA 0x[hec]0x[hec] |
Sequence Number overflow for the SA. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-TRANSIT_POLICY_FAIL |
3-Error |
- |
Policy fail for transit ipsec packet. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSEC-3-UNEXPECTED_ERROR |
3-Error |
orh.w0 0x[hec] error_op 0x[hec] SA 0x[hec]0x[hec] |
Unexpected error for the SA. |
cpp-ucode |
LOG_STD_ACTION |
|
IPSECV6-4-PKT_PROTOCOL_MISMATCH |
4-Warning |
IP protocol in packet mismatched with tunnel mode packet from [chars] to [chars] dropped by [chars] |
We tried to send an IPv4 packet into an IPSec-IPv6 tunnel or an IPv6 packet into an IPSec-IPv4 tunnel. The tunnel cannot handle this type of packet and so the packet is dropped. |
- |
"Modify the tunnel configuration either by removing the" " incorrect IP address type from the tunnel interface or by" " changing the tunnel mode to match the IP address type." |
|
IPSECV6-4-RECVD_PKT_NOT_IPSECV6 |
4-Warning |
Rec'd packet not an IPSEC packet.\n \tip dest_addr= %P src_addr= %P prot= [dec] |
- |
- |
- |
|
IPSECV6-4-RECVD_PKT_V6_INV_PROT |
4-Warning |
decapsulate: packet missing [chars] destadr=%P actual prot=[dec] |
Rec'd IPSEC packet missing an expected AH or ESP header The peer is sending packets that don't match the negotiated security policy. Some might consider this a hostile event. |
- |
"Contact the peer's administrator." |
|
IPSECV6-4-RECVD_PKT_V6_INV_SPI |
4-Warning |
decaps: rec'd IPSEC packet has invalid spi for\n \tdestaddr=%P prot=[dec] spi=0x[hec][dec] srcaddr=%P |
- |
- |
- |
|
IPSECV6-4-RECVD_PKT_V6_MSG_LEN_ERR |
4-Warning |
decapsulate: packet has bad [chars] length destadr=%P prot=[dec] len=[dec] |
Rec'd IPSEC packet is malformed: possibly encapsulation error? The peer is sending malformed packets. It may be due to a decryption error. Some might consider this a hostile event. |
- |
"Contact the peer's administrator." |
|
IPV4_FORWARDING-2-CAUSE_THROTTLE_ERR |
2-Critical |
Allocation of ipv4 throttle [chars] memory failed |
Allocation of memory resource use by ipv4 throttle fail |
cpp-ucode |
LOG_STD_ACTION |
|
IPV4_FORWARDING-3-CAUSE_LINKTYPE_ERR |
3-Error |
Unsupported link type - linktype = [dec] dropping packet |
Link type is unsupported at the current time. |
cpp-ucode |
LOG_STD_ACTION |
|
IPV4_FORWARDING-3-TABLE_ID_SZ_ERR |
3-Error |
Table ID size configured incorrectly: [dec] |
Table ID size must be less than or equal to 16 or 32 bits. |
cpp-ucode |
LOG_STD_ACTION |
|
IPV4_FORWARDING-3-TRAFFIC_IDX_ERR |
3-Error |
Traffic index invalid value: [dec] Buckets allocated: [dec] |
Traffic index is greater than or equal to the buckets allocated |
cpp-ucode |
LOG_STD_ACTION |
|
IPV4_FORWARDING-4-CHECKSUM_ERR |
4-Warning |
Checksum buffer walk failed |
Internal problem occured during calculating segmented packet checksum. |
cpp-ucode |
LOG_STD_ACTION |
|
IPV4_REASS_PROXY-3-PROXY_IPC_FRAG_INFO_MEM_EXTEND_FAILED |
3-Error |
- |
Increasing of fragment information pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
IPV4_REASS_PROXY-3-PROXY_IPC_FRAG_INFO_MEM_INIT_FAILED |
3-Error |
- |
Initialization of fragment information pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
IPV4_REASS_PROXY-3-PROXY_IPC_INIT_FAILED |
3-Error |
[dec] |
IPC handler initialization failed. |
cpp-ucode |
LOG_STD_ACTION |
|
IPV4_REASS_PROXY-4-PROXY_IPC_INVALID_MSG |
4-Warning |
[hec] |
Received an invalid IPC messages subtype. |
cpp-ucode |
LOG_STD_ACTION |
|
IPV4_URPF-4-DROP |
4-Warning |
Dropping [chars] from [chars] |
This message indicates that the router dropped a packet due to Unicast Reverse Path Forwarding check failure |
qfp-ipucast |
"This is an informational message" |
|
IPV4_VFR-4-CONFIG |
4-Warning |
Dropping [chars] from [chars] due to system config. |
This message indicates that the router drops fragment packet due to ip virtual-reassembly drop-fragments |
qfp-ipucast |
"This is an informational message" |
|
IPV4_VFR-4-FRAG_TABLE_OVERFLOW |
4-Warning |
Dropping [chars] from [chars] due to fragment table overflow. |
This means the number of datagrams reassembled at a time reached its maximum limit increase the value of max-reassemblies using ip virtual-reassembly max-reassemblies <number> |
qfp-ipucast |
- |
|
IPV4_VFR-4-INVALID_DROP_LOG_TYPE |
4-Warning |
Dropping [chars] from [chars]. Invalid drop log type [dec] |
Unsupported drop log type |
qfp-ipucast |
LOG_STD_ACTION |
|
IPV4_VFR-4-INVALID_FRAG_LENGTH |
4-Warning |
Dropping [chars] from [chars] due to invalid fragment length. |
This message indicates that the router has encountered a fragment with invalid packet length |
qfp-ipucast |
"To prevent further attacks its highly recommended that an ACL " "be configured to drop any traffic from the sender" |
|
IPV4_VFR-4-OVERLAP_FRAGMENTS |
4-Warning |
Dropping [chars] from [chars] due to overlap fragment. |
This message is logged whenever the router encounters overlap fragments. Overlap fragment means offset of one fragment overlaps the offset of another fragment. For example if first fragment's offset is 0 and length is 800 then the second fragments offset must be 800. If second fragment's offset is less than 800 that means the second fragment overlaps the first fragment. |
qfp-ipucast |
"This could possibly be an attack configure a static ACL to prevent " "further overlap fragments from the sender" |
|
IPV4_VFR-4-TIMEOUT |
4-Warning |
Dropping [chars] from [chars] due to virtual reassembly timeout. |
This message indicates that the router is trying to do virtual-reassembly for fragments but got timeout before receiving all the fragments for a datagram |
qfp-ipucast |
"This is an informational message" |
|
IPV4_VFR-4-TINY_FRAGMENTS |
4-Warning |
Dropping [chars] from [chars] due to tiny fragment. |
This message indicates that the router is receiving tiny fragments - meaning the initial fragment does not have complete layer 4 header |
qfp-ipucast |
"This is an informational message" |
|
IPV4_VFR-4-TOO_MANY_FRAGMENTS |
4-Warning |
Dropping [chars] from [chars] due to too many fragments for the datagram. |
This message indicates the datagram being reassembled has received more fragments than its threshold value |
qfp-ipucast |
"Check if the fragments received are from a genuine source if so " "increase the value of max-fragments using the CLI " "ip virtual-reassembly max-fragments <number>" |
|
IPV4MCAST-3-MCAST_CFG_ERR |
3-Error |
[chars] |
Processing MCAST packet failed due to incorrect config to HW Data structures. |
cpp-ucode |
LOG_STD_ACTION |
|
IPV4MCAST-3-MCAST_MLRE_ERR |
3-Error |
Non MLRE friendly FIA on interface [chars] |
Unexpected flowlock id following feature execution |
cpp-ucode |
LOG_STD_ACTION |
|
IPV4MCAST-3-MCAST_PA_REPLICATE_FAILED |
3-Error |
[chars] |
m-cast replication failure for PA described packet. |
cpp-ucode |
LOG_STD_ACTION |
|
IPV4MCAST-3-MCAST_REPLICATE_GATHER_FAILED |
3-Error |
[chars] [inet] |
m-cast replication failure due to a bad Multicast Gather parameter. |
cpp-ucode |
LOG_STD_ACTION |
|
IPV4MCAST-3-SANITY_CHECK_FAILED |
3-Error |
PIM register from [inet] for [inet] [inet] |
- |
- |
- |
|
IPV6_ADDRESS-3-ADDRESS_CFG |
3-Error |
%P/[dec] can not be configured on [chars] [chars] |
An error was encountered while configuring an IPv6 address |
ipv6 |
LOG_STD_ACTION |
|
IPV6_ADDRESS-3-INTERNAL |
3-Error |
Internal error [chars] |
An internal software error occurred. |
ipv6 |
LOG_STD_ACTION |
|
IPV6_ADDRESS-3-NO_UNIQUE_IDENTIFIER |
3-Error |
Cannot determine an unique IPv6 identifier for the system. IPv6 will not be started. |
An IPv6 process could not be started. This machine will not be able to process any IPv6 packets. |
ipv6 |
"Reduce other system activity to ease memory demands. If conditions " "warrant upgrade to a larger memory configuration." |
|
IPV6_ADDRESS-3-NULLIDB |
3-Error |
Uninitialized interface pointer - [chars] |
An internal software error occurred. |
ipv6 |
LOG_STD_ACTION |
|
IPV6_ADDRESS-3-OPINPROGRESS |
3-Error |
Operation in progress - [chars] |
An internal software error occurred. |
ipv6 |
LOG_STD_ACTION |
|
IPV6_ADDRESS-3-RESERVED_INTFID |
3-Error |
Removing %P from [chars] - contains reserved interface identifier. [chars] |
Removing IPv6 global address contains the reserved interface identifier |
ipv6 |
LOG_STD_ACTION |
|
IPV6_ADDRMGR-3-INTERNAL |
3-Error |
Internal error [chars] |
An internal software error occurred. |
ipv6 |
LOG_STD_ACTION |
|
IPV6_FORWARDING-2-CAUSE_THROTTLE_ERR |
2-Critical |
Allocation of ipv6 throttle [chars] memory failed |
Allocation of memory resource use by ipv6 throttle fail |
cpp-ucode |
LOG_STD_ACTION |
|
IPV6_FORWARDING-3-CAUSE_LINKTYPE_ERR |
3-Error |
Unsupported link type [chars] dropping packet |
Link type is unsupported at the current time. |
cpp-ucode |
LOG_STD_ACTION |
|
IPV6_FORWARDING-3-NULLIDB |
3-Error |
Uninitialized interface pointer - [chars] |
An internal software error occurred. |
ipv6 |
LOG_STD_ACTION |
|
IPV6_FORWARDING-3-NULLPAK |
3-Error |
Uninitialized buffer pointer - [chars] |
An internal software error occurred. |
ipv6 |
LOG_STD_ACTION |
|
IPV6_FORWARDING-3-TABLE_ID_SZ_ERR |
3-Error |
Table ID size configured incorrectly: [dec] |
Table ID size must be less than or equal to 16 or 32 bits. |
cpp-ucode |
LOG_STD_ACTION |
|
IPV6_FORWARDING-3-UNFRAGMENTABLE |
3-Error |
Cannot fragment packet: unfragmentable part length [dec] MTU of [dec] |
An internal software error occurred. A single packet originated by this system could not be fragmented and has been dropped. Normal system operation continues. |
ipv6 |
- |
|
IPV6_FORWARDING-4-CHECKSUM_ERR |
4-Warning |
Checksum buffer walk failed |
Internal problem occured during calculating segmented packet checksum. |
cpp-ucode |
LOG_STD_ACTION |
|
IPV6_FORWARDING-4-MULTICAST |
4-Warning |
Application does not support multicast destination address %P packet dropped. |
- |
- |
- |
|
IPV6_ICMP-3-NULLPAK |
3-Error |
Uninitialized buffer pointer - [chars] |
An internal software error occurred. |
ipv6 |
LOG_STD_ACTION |
|
IPV6_INTF-3-INTERNAL |
3-Error |
Internal error [chars] |
An internal software error occurred. |
ipv6 |
LOG_STD_ACTION |
|
IPV6_INTF-3-MIN_MTU |
3-Error |
The link MTU of [chars] is below the [dec]-byte minimum IPv6 link MTU. |
As specified in the standard IPv6 requires that every link has an MTU of at least 1280. Since this link's MTU is below that IPv6 is held down on this interface. |
ipv6 |
LOG_STD_NO_ACTION |
|
IPV6_INTF-3-NO_PROCESS |
3-Error |
Cannot start IPv6 Interface Process. |
The IPv6 Interface Process could not be started. Interfaces will not be enabed for IPv6 Processing. This machine will not be able to process any IPv6 packets. |
ipv6 |
"Reduce other system activity to ease memory demands. If conditions " "warrant upgrade to a larger memory configuration." |
|
IPV6_INTF-3-SET_MTU |
3-Error |
The link MTU of [chars] is below the [dec]-byte user set IPv6 link MTU. |
The interface link MTU is below the user set IPv6 link MTU. IPv6 is held down on this interface. |
ipv6 |
LOG_STD_NO_ACTION |
|
IPV6_INTF-4-L2_MISMATCH |
4-Warning |
High load on interface events [chars] auto-recovery complete. |
- |
- |
- |
|
IPV6_ND-3-CONFLICT |
3-Error |
Router %P on [chars] conflicting ND setting [chars] |
Another router on the link sent router advertisements\n\ with conflicting parameters to ours. |
ipv6 |
"Verify that all IPv6 routers on the link have the same parameters\n\ in the router advertisement for hop-limit managed-config-flag\n\ other-config-flag reachable-time and ns-interval and that\n\ preferred and valid lifetimes for the same prefix advertised\n\ by several routers are the same. Use the command show ipv6 interface\n\ to list the parameters per interface." |
|
IPV6_ND-3-INTERNAL |
3-Error |
Internal error [chars] |
An internal software error occurred. |
ipv6_nd |
LOG_STD_ACTION |
|
IPV6_ND-3-IPV6PAKENCAP |
3-Error |
Dest host is IPv4 in IPv6 packet - [chars] |
IPv6 packet encapsulation called with IPv4 destination host |
ipv6 |
"Use an IPv6 address in neighbour for IPv6 packet flow on the router" "if the problem persists or you feel this should be supported then " "please contact the TAC with the failing command line." |
|
IPV6_ND-3-ND_ROUTER_NUM |
3-Error |
Router list not empty [dec]. Recounting routers autocorrecting |
There is a missmatch between the number of routers known to ND and\n\ the number of routers known to the interface. The issue will\n\ auto-correct itself |
ipv6 |
NOG_STD_NO_ACTION |
|
IPV6_ND-3-NULLDATA |
3-Error |
Uninitialized data - [chars] |
An IPv6 process could not be started. This machine will not be able to process any IPv6 packets. |
ipv6 |
"Reduce other system activity to ease memory demands. If conditions " "warrant upgrade to a larger memory configuration." |
|
IPV6_ND-4-DUPLICATE |
4-Warning |
Duplicate address %P on [chars] |
Another system is using your IPv6 address. |
ipv6 |
"Change the IPv6 address of one of the " "two systems." |
|
IPV6_ND-4-DUPLICATE_OPTIMISTIC |
4-Warning |
Duplicate address %P on [chars] |
You have elected not to run DAD but another system is using your IPv6 address. |
ipv6 |
"Change the IPv6 address of one of the " "two systems." |
|
IPV6_ND-4-DUPOLPFX |
4-Warning |
Prefix %P/[dec] advertised in RA on [chars] was previously learnt on another interface |
This warning indicates that an on-link prefix advertised in an IPv6 ND RA on the specified interface has previously been learnt from an RA on another interface. The prefix will be ignored on the current interface |
ipv6_nd |
" Learning the same on-link prefix via IPv6 ND RA" " on multiple interfaces indicates a likely" " configuration error on adjacent routers." " Review network topology and adjacent router" " configuration and correct as appropriate" |
|
IPV6_ND-4-INTFLIMIT |
4-Warning |
Attempt to exceed interface limit on [chars] for %P |
An ND resolution request was received on the specified interface for the specified destination. Satisfying the request would have exceeded the ND cache entry limit configured on the interface. The request was ignored |
ipv6 |
"No action is necessary. Review the interface" " ND cache entry limit configured via" " ipv6 nd cache interface-limit if appropriate" |
|
IPV6_ND-4-LLA_CONFLICT |
4-Warning |
LLA conflict for static neighbor %P on [chars] : [chars] |
This error indicates that an ND message from the specified neighbor carries a Link Layer Address other than that configured via static neighbor |
ipv6 |
"Reconfigure the static neighbor with correct LLA" |
|
IPV6_ND-4-LOOPBACK |
4-Warning |
Looped back NSDAD packet detected for %P on [chars] |
A looped back DAD NS packet was detected for %P on [chars] |
ipv6 |
"A neighbor solicitation packet was received for an " "address on which this router is performing duplicate " "address detection. The packet was ignored because it " "originated from this router and was looped back." |
|
IPV6_ND-4-OLPFXCON |
4-Warning |
Prefix %P/[dec] advertised in RA on [chars] has been previously configured on another interface |
This warning indicates that an on-link prefix advertised in an IPv6 ND RA on the specified interface has previously been configured on another interface. The prefix will be ignored on the current prefix |
ipv6_nd |
" Learning an on-link prefix via IPv6 ND RA" " when the same prefix has previously been" " configured on another interface indicates a" " likely configuration error either on the" " current router or on the neighbor router" " advertising the ND RA. Review network topology" " current router and adjacent router configuration" " and correct as appropriate" |
|
IPV6_ND-4-RA_TIMERS_INCONSISTENT |
4-Warning |
Configured Router Advertisements interval exceeds the configured RA lifetime on [chars]. |
This warning indicates that the value configured for the Router Advertisements interval exceeds the value configured for Router Advertisements lifetime on the given interface. This is not recommended as it will lead to hosts timing out the router between Router Advertisement transmissions. |
ipv6_nd |
" Check the router configuration on the interface" " and correct it so that RA lifetime is greater" " than RA interval." |
|
IPV6_ND-4-RESOURCE_LIMIT |
4-Warning |
[chars] resource limit prevents creation of ND entry |
This warning indicates that an ND cache entry could not be created because the indicated platform resource limit has been reached. |
ipv6_nd |
"Check the size of the ND cache table. " "Consider using ND cache sizing to explicitly " "configure the size of the ND cache on each " "interface" |
|
IPV6_ND-4-RSRV_ADDRESS |
4-Warning |
[chars]: [chars]: [chars] |
IPv6 address contains reserved interface identifiers. |
ipv6 |
NOG_STD_NO_ACTION |
|
IPV6_ND-6-ADDRESS |
6-Information |
%P/[dec] can not generate auto-configured address on [chars] [chars][chars] |
IPv6 address could not be auto-configured. |
ipv6 |
NOG_STD_NO_ACTION |
|
IPV6_ND-6-DUPLICATE_INFO |
6-Information |
DAD attempt detected for %P on [chars] |
Another system attempted to configure an IPv6 address already configured on this interface. The configuration of the other system was denied. |
ipv6 |
"No action is required on this system." |
|
IPV6_POLICY_API-4-IPV6_LOCALPOLICYOVERIDE |
4-Warning |
Local dynamic policy overriding static local policy |
Static policy and dynamic local policy are configured. The dynamic local policy will override the static local policy. |
ipv6 |
"Remove the static local policy config if desired." |
|
IPV6_POLICY_API-4-IPV6_POLICYOVERIDE |
4-Warning |
Dynamic policy overriding static on intf:[chars] |
Static policy and dynamic policy are configured on the interface. The dynamic policy will override the static policy. |
ipv6 |
"Remove the static policy config if desired." |
|
IPV6_REASS_PROXY-3-PROXY_IPC_FRAG_INFO_MEM_EXTEND_FAILED |
3-Error |
- |
Increasing of fragment information pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
IPV6_REASS_PROXY-3-PROXY_IPC_FRAG_INFO_MEM_INIT_FAILED |
3-Error |
- |
Initialization of fragment information pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
IPV6_REASS_PROXY-3-PROXY_IPC_INIT_FAILED |
3-Error |
[dec] |
IPC handler initialization failed. |
cpp-ucode |
LOG_STD_ACTION |
|
IPV6_REASS_PROXY-4-PROXY_IPC_INVALID_MSG |
4-Warning |
[hec] |
Received an invalid IPC messages subtype. |
cpp-ucode |
LOG_STD_ACTION |
|
IPV6_RIP-3-ALLOC_ERR |
3-Error |
Memory allocation problem - RIPv6 |
An internal software error occurred. |
ipv6 |
LOG_STD_ACTION |
|
IPV6_RIP-3-ALLOC_IPDB |
3-Error |
Can't alloc iPDB structure - RIPv6 |
An internal software error occurred. |
ipv6 |
LOG_STD_ACTION |
|
IPV6_RIP-3-ALLOC_PDB |
3-Error |
Can't alloc PDB structure - RIPv6 |
An internal software error occurred. |
ipv6 |
LOG_STD_ACTION |
|
IPV6_RIP-3-NULLIDB |
3-Error |
Uninitialized interface pointer - RIPv6 |
An internal software error occurred. |
ipv6 |
LOG_STD_ACTION |
|
IPV6_RIP-3-NULLIPDB |
3-Error |
Uninitialized iPDB pointer - RIPv6 |
An internal software error occurred. |
ipv6 |
LOG_STD_ACTION |
|
IPV6_RIP-3-NULLPAK |
3-Error |
Uninitialized packet pointer - RIPv6 |
An internal software error occurred. |
ipv6 |
LOG_STD_ACTION |
|
IPV6_RIP-3-NULLPDB |
3-Error |
Uninitialized PDB pointer - RIPv6 |
An internal software error occurred. |
ipv6 |
LOG_STD_ACTION |
|
IPV6_RIP-3-NULLPROTO |
3-Error |
Uninitialized protocol pointer - RIPv6 |
An internal software error occurred. |
ipv6 |
LOG_STD_ACTION |
|
IPV6_RIP-3-NULLSOC |
3-Error |
Uninitialized socket pointer - RIPv6 |
An internal software error occurred. |
ipv6 |
LOG_STD_ACTION |
|
IPV6_RIP-3-PROCESS_CREATE |
3-Error |
Can't create process - RIPv6 |
An internal software error occurred. |
ipv6 |
LOG_STD_ACTION |
|
IPV6_RIP-3-PROCESS_MSG_SEND |
3-Error |
Can't send message to process - RIPv6 |
An internal software error occurred. |
ipv6 |
LOG_STD_ACTION |
|
IPV6_ROUTING-3-INTERNAL |
3-Error |
Internal error [chars] |
An internal software error occurred. |
ipv6 |
LOG_STD_ACTION |
|
IPV6_ROUTING-3-RIB |
3-Error |
[chars] |
An internal software error occurred. |
ipv6 |
LOG_STD_ACTION |
|
IPV6_ROUTING-3-ROUTELIMITEXCEEDED |
3-Error |
IPv6 routing table limit exceeded - [chars] |
The number of routes in the named IPv6 routing table has reached the configured limit. No further routes will be added to the table |
ipv6 |
"Reduce the number of routes in the table or reconfigure the limit" |
|
IPV6_ROUTING-3-ROUTELIMITWARNING |
3-Error |
IPv6 routing table limit warning - [chars] |
The number of routes in the named IPv6 routing table has reached the configured warning limit. |
ipv6 |
"Reduce the number of routes in the table or reconfigure the limit" |
|
IPV6_ROUTING-4-MAXPDB |
4-Warning |
Exceeded maximum supported IPv6 Routing Protocol instances |
This error indicates that configuration of a Routing Protocol has failed because it would exceed the maximum supported number of Routing Protocols |
ipv6 |
"Reduce the number of IPv6 Routing Protocol" " instances configured" |
|
IPV6_ROUTING-4-REDIST_MAX_PFX |
4-Warning |
Redistribution prefix limit has been reached \[chars]\ - [dec] prefixes |
We have reached the maximum number of redistributed prefixes |
- |
"Check if redistribution of large number of prefixes is " "desired and has not been configured by mistake" |
|
IPV6_ROUTING-4-REDIST_THR_PFX |
4-Warning |
Redistribution prefix threshold has been reached \[chars]\ - [dec] prefixes |
We have reached the threshold level of number of redistributed prefixes |
- |
"Check if redistribution of large number of prefixes is " "desired and has not been configured by mistake" |
|
IPV6_ROUTING-6-ROUTELIMITRECOVERED |
6-Information |
IPv6 routing table limit recovered - [chars] |
The number of routes in the named IPv6 routing table has fallen below the configured limit. The routing table has recovered |
ipv6 |
LOG_STD_NO_ACTION |
|
IPV6_URPF-4-DROP |
4-Warning |
Dropping [chars] from [chars]. |
This message indicates that the router dropped a packet due to Unicast Reverse Path Forwarding check failure |
qfp-ipucast |
"This is an informational message" |
|
IPV6_VFR-4-CONFIG |
4-Warning |
Dropping [chars] from [chars] due to system config. |
This message indicates that the router drops fragment packet due to ipv6 virtual-reassembly drop-fragments |
qfp-ipucast |
"This is an informational message" |
|
IPV6_VFR-4-FRAG_TABLE_OVERFLOW |
4-Warning |
Dropping [chars] from [chars] due to fragment table overflow. |
This means the number of datagrams reassembled at a time reached its maximum limit increase the value of max-reassemblies using ipv6 virtual-reassembly in/out max-reassemblies <number> |
qfp-ipucast |
- |
|
IPV6_VFR-4-INVALID_DROP_LOG_TYPE |
4-Warning |
Dropping [chars] from [chars]. Invalid drop log type [dec] |
Unsupported drop log type |
qfp-ipucast |
LOG_STD_ACTION |
|
IPV6_VFR-4-INVALID_FRAG_LENGTH |
4-Warning |
Dropping [chars] from [chars] due to invalid fragment length. |
This message indicates that the router has encountered a fragment with invalid packet length |
qfp-ipucast |
"To prevent further attacks its highly recommended that an ACL " "be configured to drop any traffic from the sender" |
|
IPV6_VFR-4-OVERLAP_FRAGMENTS |
4-Warning |
Dropping [chars] from [chars] due to overlap fragment. |
This message is logged whenever the router encounters overlap fragments. Overlap fragment means offset of one fragment overlaps the offset of another fragment. For example if first fragment's offset is 0 and length is 800 then the second fragments offset must be 800. If second fragment's offset is less than 800 that means the second fragment overlaps the first fragment. |
qfp-ipucast |
"This could possibly be an attack configure a static ACL to prevent " "further overlap fragments from the sender" |
|
IPV6_VFR-4-TIMEOUT |
4-Warning |
Dropping [chars] from [chars] due to virtual reassembly timeout. |
This message indicates that the router is trying to do virtual-reassembly for fragments but got timeout before receiving all the fragments for a datagram |
qfp-ipucast |
"This is an informational message" |
|
IPV6_VFR-4-TINY_FRAGMENTS |
4-Warning |
Dropping [chars] from [chars] due to tiny fragment. |
This message indicates that the router is receiving tiny fragments - meaning the initial fragment does not have complete layer 4 header |
qfp-ipucast |
"This is an informational message" |
|
IPV6_VFR-4-TOO_MANY_FRAGMENTS |
4-Warning |
Dropping [chars] from [chars] due to too many fragments for the datagram. |
This message indicates the datagram being reassembled has received more fragments than its threshold value |
qfp-ipucast |
"Check if the fragments received are from a genuine source if so " "increase the value of max-fragments using the CLI " "ipv6 virtual-reassembly in/out max-fragments <number>" |
|
IPV6FIB-3-GLOBALSTATE |
3-Error |
Inconsistent global state '[chars]' [chars] |
IPV6FIB_INTERNAL_ERROR |
IPV6FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
IPV6FIB-4-FIBCBLK |
4-Warning |
Missing cef table for tableid %lu during [chars] event |
IPV6FIB_INTERNAL_ERROR |
IPV6FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
IPV6FIB-4-FIBIDB |
4-Warning |
Missing cef idb for [chars] during [chars] |
IPV6FIB_INTERNAL_ERROR |
IPV6FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
IPV6FIB-4-FIBXDRINV |
4-Warning |
Invalid format. [chars] |
IPV6FIB_INTERNAL_ERROR |
IPV6FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
IPV6FIB-4-FIBXDRLEN |
4-Warning |
Invalid XDR length. Type/event [dec]/[chars]. XDR [dec] buffer [dec] |
IPV6FIB_INTERNAL_ERROR |
IPV6FIB_DDTS_COMPONENT |
LOG_STD_ACTION |
|
IPV6MCAST-3-MCAST_CFG_ERR |
3-Error |
[chars] |
Processing MCAST packet failed due to incorrect config to HW Data structures. |
cpp-ucode |
LOG_STD_ACTION |
|
IPV6MCAST-3-MCAST_ERR |
3-Error |
[chars] 0x[hec] 0x[hec] 0x[hec] 0x[hec] |
A Mcast replica error has occurred |
cpp-ucode |
LOG_STD_ACTION |
|
IPV6MCAST-3-SANITY_CHECK_FAILED |
3-Error |
PIM register from [inet] for [inet] [inet] |
- |
- |
- |
|
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-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-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-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-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-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-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-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-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-7-DEBUGMSG |
7-Debug |
[chars]: %08x %08x %08x %08x %08x |
Internal use only |
novell |
"Should not be seen in the field" |
|
IR8340_ALARM_CONTACT-0-EXTERNAL_ALARM_CONTACT_ASSERT |
0-Emergency |
External alarm/digital IO port [chars] asserted\n |
External alarm/digital IO port alert is detected |
- |
"No action recommended" LOG_STD_ACTION |
|
IR8340_ALARM_CONTACT-0-EXTERNAL_ALARM_CONTACT_CLEAR |
0-Emergency |
External alarm/digital IO port [chars] cleared\n |
External alarm/digital IO port alert is cleared |
- |
"No action recommended" LOG_STD_ACTION |
|
IRECAGENTSERVER-3-NOINIT |
3-Error |
Can't initialize iREC agent server |
Internal problems with initializing ports for the iREC agent\n\server |
ios-callmgr |
"Make sure the iREC agent server port is available on the local\n\machine." |
|
IRECAGENTSERVER-3-NOMEM |
3-Error |
Can't initialize memory for iREC agent server |
Insufficient Memory for iREC agent server |
ios-callmgr |
"Increase amount of available memory" |
|
IRECAGENTSERVER-3-NOPROC |
3-Error |
Could not start iREC agent Server |
Internal Problem in process creation |
ios-callmgr |
"None" |
|
IRECAGENTSERVER-3-NOSOCKETS |
3-Error |
Max Number of iREC agent Server sockets exceeded |
There are too many iREC agent clients requesting service |
ios-callmgr |
"Reduce number of iREC agent requesting service" |
|
ISDN-1-NOMEMORY |
1-Alert |
no memory for [chars] |
The requested operation could not be accomplished because of a low\n\ memory condition. |
- |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
ISDN-2-ISDN_EXIT |
2-Critical |
[chars] |
The ISDN task has terminated execution for the specified reason and may cause CISCO IOS to terminate. |
- |
LOG_STD_ACTION |
|
ISDN-2-ISDN_FATAL |
2-Critical |
ISDN FATAL ERROR: file [chars] function [chars] message: [chars] |
ISDN has detected a fatal system error. |
- |
LOG_STD_ACTION |
|
ISDN-2-ISDN_GENERAL_TRACEBACK |
2-Critical |
[chars]:[dec] |
A debug - traceback condition has occurred |
- |
LOG_STD_NO_ACTION |
|
ISDN-3-ISDN_CCB_FREE |
3-Error |
[chars]: CCB with call id 0x%04X on b channel [dec] was leaked but has been freed by ISDN Housekeeping. Reason: [chars] |
A data structure internal to ISDN has leaked. |
isdn |
LOG_STD_NO_ACTION |
|
ISDN-3-ISDN_CCB_FREE_FAILS |
3-Error |
[chars]: CCB with call id 0x%04X on b channel [dec] was leaked reason: [chars] and can't be free'd by ISDN Housekeeping. |
A data structure internal to ISDN has leaked and we can't fix it for some reason. |
isdn |
LOG_STD_NO_ACTION |
|
ISDN-3-ISDN_NLCB_FREE |
3-Error |
[chars]: NLCB with call id 0x%04X was leaked but has been freed by ISDN Housekeeping. Reason: [chars] |
A data structure internal to ISDN has leaked. |
isdn |
LOG_STD_NO_ACTION |
|
ISDN-3-ISDN_RESOURCE_UNAVAILABLE |
3-Error |
[chars]: Resource not available at [chars]:[dec] |
Hardware resource could not be allocated |
- |
LOG_STD_ACTION |
|
ISDN-3-LAYER2_DOWN |
3-Error |
Layer 2 for Interface [chars] TEI [dec] changed to down |
This is an informational message but being logged as ERR at request\n\ from some customers. It is sent when an ISDN Layer2 logical link is \n\ down. It also shows the TEI associated with this logical link. |
- |
LOG_STD_NO_ACTION |
|
ISDN-3-LAYER2_UP |
3-Error |
Layer 2 for Interface [chars] TEI [dec] changed to up |
This is an informational message but being logged as an ERR at request\n\ from some customers. It is sent when an ISDN Layer2 logical link is up.\n\ It also shows the TEI associated with this logical link. |
- |
LOG_STD_NO_ACTION |
|
ISDN-4-BAD_DSL_FOR_CREATE_DELETE_L2 |
4-Warning |
[chars]: isdn_create_delete_signalling_channel: Unknown DSL [dec] for\n\ [chars] |
The Creation/Deletion service for the L2 Signalling handler\n\for the given DSL is missing |
- |
LOG_STD_SH_TECH_ACTION |
|
ISDN-4-GET_STATUS_STATE_FAIL |
4-Warning |
[chars]: isdn_get_status_state: Unknown DSL [dec] |
An attempt to retrieve the status of a DSL that \n\is not currently configured. |
- |
LOG_STD_SH_TECH_ACTION |
|
ISDN-4-INVALID_CALLEDNUMBER |
4-Warning |
Interface [chars] Ignoring call LDN and Called Party Number mismatch |
The incoming ISDN call is ignored because the Called Party Number does\n\ not match the LDN numbers configured in the router. |
- |
"Correct the LDN in the router to match the Called Party\n\ Number delivered in the incoming setup message." |
|
ISDN-4-INVALID_EID |
4-Warning |
Interface [chars] Ignoring call EndPoint Identifier EID mismatch |
The incoming ISDN call is ignored because the EID delivered in the\n\ incoming setup message cannot be matched. |
- |
"If EID is delivered in the setup message use the <bold> isdn\n\ debugs <nobold> and <bold> show isdn status <nobold> commands\n\ to determine the current EID values. You may need to contact\n\ the service provider." |
|
ISDN-4-INVALID_EVENT |
4-Warning |
[chars]: Bad Event Received For Current State |
The State Transition for the ISDN L2 Socket Process failed. |
- |
LOG_STD_SH_TECH_ACTION |
|
ISDN-4-INVALID_SPID |
4-Warning |
Interface [chars] Spid[dec] was rejected |
The SPID configured in the router has been rejected by the switch. |
- |
"Determine the correct SPID reenter the SPID and clear the\n\ BRI interface." |
|
ISDN-4-ISDN_CCB_LEAK |
4-Warning |
[chars]: CCB with callid 0x%04X on b channel [dec] has been leaked. Reason: [chars] |
A data structure internal to ISDN has been leaked |
isdn |
LOG_STD_NO_ACTION |
|
ISDN-4-ISDN_L2_INTERFACE_NOT_REGISTERED |
4-Warning |
[chars]: isdn_to_L2: Unknown DSL [dec] for command [chars] |
The ISDN Stack has not registered its L2 Message Handler |
- |
LOG_STD_SH_TECH_ACTION |
|
ISDN-4-ISDN_NLCB_LEAK |
4-Warning |
[chars]: NLCB leak detected. nlcb %X call id 0x%04X reason: [chars] |
A data structure internal to ISDN has not been freed |
isdn |
LOG_STD_NO_ACTION |
|
ISDN-4-ISDN_UNEXPECTED_EVENT |
4-Warning |
[chars]: Occurred at [chars]:[dec] |
An unexpected event of significance has occurred |
- |
LOG_STD_SH_TECH_ACTION |
|
ISDN-4-OPEN_TEMP_SOCKET_FAIL |
4-Warning |
[chars]: Failed to Open Required Temporary Socket[chars] |
- |
- |
LOG_STD_SH_TECH_ACTION |
|
ISDN-4-RESTART |
4-Warning |
Interface [chars] [chars] [chars] message with restart class of [chars] chan [dec] |
This is an informational message but will logged as a \n\ warning message if so configured. |
- |
"No action is required." |
|
ISDN-4-RLM_STATUS_CHANGE |
4-Warning |
ISDN SC [chars]: Status Changed to: [chars]. |
ISDN has been notified by the RLM component of a \n\status change in the RLM link |
- |
LOG_STD_NO_ACTION |
|
ISDN-4-SERV_AUDIT_C1 |
4-Warning |
Interface [chars] service audit trigger condition [dec] on channel [dec] |
This is an informational message but will be logged as a warning message if so configured. |
- |
"No action is required." |
|
ISDN-4-SERVICE |
4-Warning |
Interface [chars] [chars] [chars] message for chan [dec] state [chars] |
This is an informational message but will be logged as a \n\ warning message if so configured. |
- |
"No action is required." |
|
ISDN-4-SPURIOUS_CONNECT |
4-Warning |
[chars]: Spurious Connection Accepted and Closed on port [dec] |
An unknown TCP connection was accepted and refused. |
- |
LOG_STD_SH_TECH_ACTION |
|
ISDN-4-STATUS |
4-Warning |
Interface [chars] [chars] [chars] st 0x[hec] ev 0x[hec] cid 0x[hec] cref 0x[hec] |
This is an informational message but being logged as a \n\ warning message if so configured. |
- |
"No action is required." |
|
ISDN-5-SERV_AUDIT_C2 |
5-Notice |
Interface [chars] service audit trigger condition [dec] on channel [dec] |
This is an informational message but will be logged as a warning message if so configured. |
- |
"No action is required." |
|
ISDN-6-CALL_COLLISION |
6-Information |
Interface [chars] Call Cid 0x[hec] Cref 0x[hec] collision on Channel [dec] in_use_cid 0x[hec] cref 0x[hec] Channel awarded to the received call |
This is an informational message. It is sent when a Call is\n\ received that collides with an existing call on the same channel. |
- |
"No action is required." |
|
ISDN-6-CHAN_UNAVAILABLE |
6-Information |
Interface [chars] Requested Channel [dec] is not available |
This is an informational message. It is sent when the requested\n\ channel is not available. |
- |
"No action is required." |
|
ISDN-6-CONNECT |
6-Information |
Interface [chars] is now connected to [chars] [chars] |
- |
- |
LOG_STD_NO_ACTION |
|
ISDN-6-DISCONNECT |
6-Information |
Interface [chars] disconnected from [chars] [chars] call lasted [dec] seconds |
- |
- |
LOG_STD_NO_ACTION |
|
ISDN-6-INVALID_TIMER |
6-Information |
[chars]: Invalid Timer Handle caller 0x[hec] handle %3d |
This could be an indication of low memory. It is sent when \n\ an invalid ISDN timer handle is passed on for timer operations |
- |
"capture the show isdn mem show isdn status output for possible \n\ debugging information. Reduce other system activity to ease the \n\ memory demands in the system." |
|
ISDN-6-LAYER2DOWN |
6-Information |
Layer 2 for Interface [chars] TEI [dec] changed to down |
This is an informational message. It is sent when an ISDN Layer2\n\ logical link is down. It also shows the TEI associated with this\n\ logical link. |
- |
LOG_STD_NO_ACTION |
|
ISDN-6-LAYER2UP |
6-Information |
Layer 2 for Interface [chars] TEI [dec] changed to up |
This is an informational message. It is sent when an ISDN Layer2\n\ logical link is up. It also shows the TEI associated with this\n\ logical link. |
- |
LOG_STD_NO_ACTION |
|
ISDN-6-NFAS_STATUS_CHANGE |
6-Information |
[chars] [chars] [chars] [chars] |
The NFAS D-channel status has changed. |
- |
LOG_NO_ACTION |
|
ISDN-6-NO_TIMER |
6-Information |
No Free Timer Entry caller 0x[hec] timers used [dec] |
This could be an indication of low memory. It is sent when the ISDN \n\ protocol cannot start new timers for it's operation. |
- |
"capture the show isdn mem show isdn status output for possible \n\ debugging information. Reduce other system activity to ease the \n\ memory demands in the system." |
|
ISDN-6-REPEATED_SETUP |
6-Information |
Interface [chars] Call Cid 0x%04X Cref 0x%04X received a retransmitted setup on channel [dec] in_use_cid 0x%04X cref 0x%04X. |
This is an informational message sent when a duplicate SETUP message is received on a B-channel. This indicates that the rate of calls being received is momentarily greater than the rate calls can be processed. No action is required. |
- |
LOG_STD_NO_ACTION |
|
ISDN-6-SERV_AUDIT_C3 |
6-Information |
Interface [chars] service audit trigger condition [dec] on channel [dec] |
This is an informational message but will be logged as a warning message if so configured. |
- |
"No action is required." |
|
ISISL2-3-MCAST_EVENT_UPD_FAILURE |
3-Error |
[chars]-RIBInfo[chars]: [chars] client failed to send Multicast event [dec] [dec] update request with error [chars] |
- |
- |
- |
|
ISISL2-3-MCAST_RT_UPD_REP_FAILURE |
3-Error |
[chars]-RIBInfo[chars]: [chars] client receives the response of Multicast RT [chars] message with code:[dec] topoid:[dec] |
ISISL2 client receives the response of Multicast RT update failure |
ISISL2_DDTS_COMPONENT |
LOG_STD_ACTION |
|
ISISL2-3-MCAST_RT_UPD_REQ_FAILURE |
3-Error |
[chars]-RIBInfo[chars]: Multicast RT [dec] [chars] [chars]: Failed to send the |
ISISL2 client failed to send the Multicast route update request to MLMRIB |
ISISL2_DDTS_COMPONENT |
LOG_STD_ACTION |
|
ISISL2-3-UNICAST_EVENT_UPD_FAILURE |
3-Error |
[chars]-RIBInfo[chars]: [chars] client failed to send Unicast event [dec] [dec] update request with error [chars] |
- |
- |
- |
|
ISISL2-3-UNICAST_RT_UPD_REP_FAILURE |
3-Error |
[chars]-RIBInfo[chars]: [chars] client receives the response of Unicast RT [chars] message with code:[dec] topoid:[dec] |
ISISL2 client receives the response of Unicast RT update failure |
ISISL2_DDTS_COMPONENT |
LOG_STD_ACTION |
|
ISISL2-3-UNICAST_RT_UPD_REQ_FAILURE |
3-Error |
[chars]-RIBInfo[chars]: Unicast RT [dec] [chars]: Failed to send the |
ISISL2 client failed to send Unicast route update request to MLURIB |
ISISL2_DDTS_COMPONENT |
LOG_STD_ACTION |
|
ISR_THROUGHPUT-3-CONF_FAILED |
3-Error |
Configuration failed |
An error occurred when the throughput configuration was attempted. |
iosxe-csl |
- |
|
ISR_THROUGHPUT-3-EULA_NOT_ACCEPTED |
3-Error |
The EULA has to be accepted prior to throughput configuration. |
Users need to accept EULA to activate the license |
iosxe-csl |
"Accept EULA for throughput license" |
|
ISR_THROUGHPUT-3-INVALID_CONFIG |
3-Error |
An invalid throughput config: [chars] kbps was selected. |
The configured throughput is unknown |
iosxe-csl |
- |
|
ISR_THROUGHPUT-3-SETUP_FAILED |
3-Error |
Throughput upgrade license set up failed |
An error occurred when setting up the throughput upgrade licenses. |
iosxe-csl |
- |
|
ISR_THROUGHPUT-6-CRYPTO |
6-Information |
Crypto level has been set to [dec]00 kbps |
Crypto level has been set to a number |
iosxe-csl |
- |
|
ISR_THROUGHPUT-6-LEVEL |
6-Information |
Throughput level has been set to [dec]00 kbps |
Throughput level has been set to a number |
iosxe-csl |
- |
|
ISR_THROUGHPUT-6-UNTHROTTLED |
6-Information |
Crypto level is unthrottled |
Crypto level has been unthrottled |
iosxe-csl |
- |
|
ISR4000_RP_NGIO_ATM-3-ATM_DPIDB_ALLOC_FAIL |
3-Error |
Failed to allocate a data plane identifier for interface [chars] for VCD [dec] |
The SPA driver is not able to allocate the datapath identifier for the VCD under the interface specified in the message. This indicates a software error. |
esg-io-infra |
LOG_STD_NO_ACTION |
|
ISR4000_RP_NGIO_ATM-3-ATM_DPIDB_GET_FAIL |
3-Error |
Failed to get a data plane identifier for interface [chars] for VCD [dec] |
The SPA driver is not able to obtain the datapath identifier for the VCD under the interface specified in the message. This indicates a software error. |
esg-io-infra |
LOG_STD_NO_ACTION |
|
ISR4000_RP_NGIO_ATM-3-ATM_FLOWID_GET_FAIL |
3-Error |
Failed to get a flow control identifier for interface [chars] for index [dec] |
The SPA driver is not able to obtain the datapath flow control identifier for the data path identifier under the interface specified in the message. This indicates a software error. |
esg-io-infra |
LOG_STD_NO_ACTION |
|
ISR4000_RP_NGIO_ATM-3-ATM_FLOWID_OUT_OF_RANGE |
3-Error |
Flow control identifiers for interface [chars] chan lo [hec] chan hi [hec] |
The flow control identifier received for the interface is out of range. This indicates SPA driver is responding with out of range flow control identifier |
esg-io-infra |
LOG_STD_ACTION |
|
ISR4000_RP_NGIO_ATM-3-ATM_PER_SPA_MAX_VC_LIMIT_REACHED |
3-Error |
total active atm vc per ATM SPA reached limitation of [dec] |
total number of active atm vc per ATM SPA has reached max limit |
- |
LOG_STD_ACTION |
|
ISR4000_RP_NGIO_ATM-3-ATM_SPA_AUTOVC_FAIL |
3-Error |
[chars]: atm autovc discovery configuration failed reason: [chars] |
A command to configure the atm autovc discovery on an atm interface has failed |
- |
LOG_STD_ACTION |
|
ISR4000_RP_NGIO_ATM-3-ATM_SPA_VC_MAX_LIMIT_REACHED |
3-Error |
total active atm vc reached system limitation of [dec] |
total number of active atm vc has reached max limit allowed on the system |
- |
LOG_STD_ACTION |
|
ISR4000_RP_NGIO_ATM-3-ATM_TXCHANL_GET_FAIL |
3-Error |
Failed to get a valid tx_chan id for interface [chars] for VCD [dec] |
The SPA driver is not able to obtain the datapath tx channel identifier for the VCD under the interface specified in the message. This indicates a SPA occur error. |
esg-io-infra |
LOG_STD_NO_ACTION |
|
ISR4000_RP_NGIO_ATM-3-ATM_VC_CFG_SEND_FAIL |
3-Error |
Error in sending message to SPA on interface [chars] when [chars] for VCD [dec] ebfc_id [dec] |
The SPA give a error response for ATM setup or response timeout in atm vc setup message. This indicates a SPA occur error. |
esg-io-infra |
LOG_STD_NO_ACTION |
|
ISR4000_RP_NGIO_ATM-3-ATM_VC_CON_SET_FAIL |
3-Error |
Failed set ATM con for interface [chars] [dec]/[dec] VCD [dec] |
Could not get VC encapsulation information when get SPA VCOPEN or VCMODFY response This indicates ATM occur error. |
esg-io-infra |
LOG_STD_NO_ACTION |
|
ISR4000_RP_NGIO_ATM-3-ATM_VC_CORE_GET_FAIL |
3-Error |
Failed to get a ATM VC core info for interface [chars] VCD [dec] |
Could not get VC core information when get SPA VCOPEN or VCMODIRY response. This indicates a ATM information error. |
esg-io-infra |
LOG_STD_NO_ACTION |
|
ISR4000_RP_NGIO_ATM-3-ATM_VC_DPIDX_GET_FAIL |
3-Error |
Failed to get ATM dpidx for interface [chars] VCD [dec] |
Could not get VC dpidx information when get SPA VCOPEN or VCMODFY response This indicates ATM occur error. |
esg-io-infra |
LOG_STD_NO_ACTION |
|
ISR4000_RP_NGIO_ATM-3-ATM_VC_EGRESSID_UPDATE_FAIL |
3-Error |
Failed to update ATM egress id for interface [chars] VCD [dec] egress_id [dec] |
Could not update VC egress id when get SPA VCOPEN or VCMODFY response This indicates ATM occur error. |
esg-io-infra |
LOG_STD_NO_ACTION |
|
ISR4000_RP_NGIO_ATM-3-ATM_VC_ENCAP_GET_FAIL |
3-Error |
Failed to get ATM encapsulation for interface [chars] [dec]/[dec] VCD [dec] |
Could not get VC encapsulation information when get SPA VCOPEN or VCMODFY response This indicates ATM occur error. |
esg-io-infra |
LOG_STD_NO_ACTION |
|
ISR4000_RP_NGIO_ATM-3-ATM_VC_ERROR_ENCAP_TYPE |
3-Error |
Get ATM ERROR encapsulation for interface [chars] [dec]/[dec] VCD [dec] |
Get a ERROR VC encapsulation information when get SPA VCOPEN or VCMODFY response This indicates ATM occur error. |
esg-io-infra |
LOG_STD_NO_ACTION |
|
ISR4000_RP_NGIO_ATM-3-ATM_VC_INGRESS_ID_ALLOC_FAIL |
3-Error |
Failed to allocate VC ingress identifier on interface [chars] for VCD [dec] ebfc_id [dec] when [chars] |
The ATM SHIM is not able to allocate the ingress identifier for the VCD under the interface specified in the message. This indicates a software error. |
esg-io-infra |
LOG_STD_NO_ACTION |
|
ISR4000_RP_NGIO_ATM-3-ATM_VC_SPA_SETUP_FAIL |
3-Error |
SPA Error response on interface [chars] when [chars] for VCD [dec] ebfc_id [dec] ret_val [dec] |
The SPA give a error response for ATM setup or response timeout in atm vc setup message. This indicates a SPA occur error. |
esg-io-infra |
LOG_STD_NO_ACTION |
|
ISR4000_RP_NGIO_ATM-3-PROCESS_FAIL |
3-Error |
process creation failed for [chars] |
The Periodic one second process creation failed. This indicates a software error. |
esg-io-infra |
LOG_STD_ACTION |
|
ISR4000_RP_NGIO_ATM-4-ATM_SPA_VC_ABOVE_WM_WARNING |
4-Warning |
total active atm vc approaching [dec] percent of system limitation of [dec] |
total number of active atm vc is approaching the high water mark of sysyem limitation |
- |
LOG_STD_ACTION |
|
ISR4000_RP_NGIO_ATM-4-SETUPVC |
4-Warning |
Interface [chars] VC [dec] setup failed reason = [dec] |
A command to setup a VC has failed on RP. |
esg-io-infra |
"The SPA ATM driver has detected a problem creating the internal OAM" "VC. Reload the indicated SPA card to reconfigure the internal OAM VC." "If the error messages persists copy the error message exactly as " "it appears. Next research and attempt to resolve the issue using " "the SPA hardware troubleshooting documentation as well as the tools " "and utilities provided at " "http://www.cisco.com/public/support/tac/tools.shtml. If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a 'show tech-support' to " "your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
ISR4000_RP_NGIO_ATM-4-TEARDOWNVC |
4-Warning |
Interface [chars] VC [dec] teardown failed vc state = [dec]/[dec] |
A command to remove a VC config has failed on RP. |
esg-io-infra |
"The SPA ATM driver has detected a problem tearing down the internal" "OAM VC. Reload the indicated SPA card to do a clean tear down of the " "internal OAM VC. If the error messages persists copy the error " "message exactly as it appears. Next research and attempt to resolve " "the issue using the SPA hardware troubleshooting documentation as well" " as the tools and utilities provided at " "http://www.cisco.com/public/support/tac/tools.shtml. If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a 'show tech-support' to " "your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
ISR4000_RP_NGIO_ATM-5-ATM_SPA_VC_BELOW_WM_NOTICE |
5-Notice |
total active atm vc below [dec] percent of system limitation of [dec] |
total number of active atm vc below the high water mark of sysyem limitation |
esg-io-infra |
LOG_STD_ACTION |
|
ISR4000_RP_NGIO_ATM-5-MPVCVPSETUP |
5-Notice |
Interface [chars] has a VC/VP [dec] configured already VC/VP [dec] cannot |
The SPA ATM driver supports configuring only one VC/VP under a point to multi point sub-interface. The sub-interface specified in the message already has VP/VC configured. |
- |
LOG_STD_NO_ACTION |
|
ISRHOG-2-NOMEM |
2-Critical |
No memory available for configuring ISRHOG |
The ISRHOG protocol subsystem could not obtain the memory it needed. |
The leak may be generic or by any of the IOS processes consult the \n\ Technical Engineer. Use Topic to search for a similar DDTS.\n\ If you find none write a DDTS for this problem. |
"Copy the message exactly as it appears and report it your technical\n\ support representative." |
|
ISRHOG-4-MASK |
4-Warning |
Process masked interrupts for more than [dec] microsecs\nProcess-Block-Time [dec] microsecs |
The process blocked interrupts for more than the latency threshold set\n\ for the ISRHOG tool. |
Determine the component from the traceback displayed in\n\ the error message. Use Topic to search for a similar DDTS.\n\ If you find none write a DDTS for this problem. |
"Copy the message exactly as it appears and report it your technical\n\ support representative." |
|
ISSU_ERROR-2-CLIENT_INCOMPATIBLE |
2-Critical |
[chars][dec]: ISSU Client |
ISSU Client incompatible. |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-2-NEGO_NOT_DONE |
2-Critical |
[chars][dec]: ISSU Negotiation not complete |
Unable to complete ISSU negotiation. |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-2-NTI_EP_TYPE_REG |
2-Critical |
[chars][dec]: |
Client could not register endpoint type with NTI. |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-2-NTI_EP_TYPE_UNREG |
2-Critical |
[chars][dec]: |
Client could not unregister endpoint type with NTI. |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-2-NTI_REG |
2-Critical |
[chars][dec]: Failed to register with |
Could not register client with NTI. |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-2-NTI_UNREG |
2-Critical |
[chars][dec]: |
Could not unregister client with NTI. |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-3-CAP_EXCHANGE |
3-Error |
[chars][dec]: Capability exchange failed with error [chars] |
The capability exchange failed the ISSU client is unable to process the received capability |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-3-CAP_REG |
3-Error |
[chars][dec]: failed to register |
The capabilities of the ISSU client could not be registered |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-3-CAPENTRY_REG |
3-Error |
[chars][dec]: failed to register a capability entry [chars] |
The ISSU client failed to register a capability entry |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-3-CAPGROUP_REG |
3-Error |
[chars][dec]: failed to register a capability group [chars] |
The ISSU client failed to register a capability group |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-3-CAPTYPE_REG |
3-Error |
[chars][dec]: failed to |
The ISSU client failed to register a capability type |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-3-CF_SEND |
3-Error |
[chars][dec]: Client failed to send message [dec] |
ISSU client cannot send a negotiation message to a peer |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-3-CLIENT_REG |
3-Error |
[chars][dec]: Client failed to register [chars] |
The ISSU Client could not be registered |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-3-CLIENT_REG_FAILED |
3-Error |
[chars][dec]: Client is not |
The ISSU Client is not yet initialized. The negotiation for this client is not yet done. |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-3-ENTITY_REG |
3-Error |
[chars][dec]: failed to register |
The ISSU entity could not be registered |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-3-ENTITY_UNREG |
3-Error |
[chars][dec]: failed to unregister |
The ISSU entity could not be unregistered |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-3-ICC_SEND |
3-Error |
[chars][dec]: Client failed to send message |
ISSU client cannot send a negotiation message to a peer |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-3-MSG_MTU |
3-Error |
[chars][dec]: Client failed to get mtu for message [dec] [chars] |
[chars][dec]: client cannot get the MTU for a message type |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-3-MSG_NOT_OK |
3-Error |
[chars][dec]: ISSU message type [dec] is not compatible |
ISSU received a message not compatible with the running version. |
ISSU_CLIENT_COMP |
"show message type <Client_ID>" |
|
ISSU_ERROR-3-MSG_POLICY |
3-Error |
[chars][dec]: Client failed to negotiate version for message type [dec] error [chars] |
ISSU client cannot negotiate message to a peer |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-3-MSG_REG |
3-Error |
[chars][dec]: failed to register its messages [chars] |
Messages for the ISSU client could not be registered |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-3-MSGGROUP_REG |
3-Error |
[chars][dec]: failed to |
The ISSU client failed to register a message group |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-3-MSGTYPE_REG |
3-Error |
[chars][dec]: failed to register a message type [chars] |
The ISSU client failed to register a message type |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-3-MTU_NOT_ENOUGH |
3-Error |
[chars][dec]: Requested buffer size [dec] is greater than the max MTU size |
Checkpoint buffer size requested is greater than the max MTU size checkpoint supports |
cat6000-ha |
LOG_STD_ACTION |
|
ISSU_ERROR-3-NEGO_PROCESS |
3-Error |
[chars][dec]: Cannot create process: [chars] |
The process to negotiate the session for the specified ISSU client cannot be created. |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-3-REG_ARBITRATE_CALLBACK |
3-Error |
[chars][dec]: |
- |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-3-SESSION_REG |
3-Error |
[chars][dec]: session failed to register [chars] |
The client's ISSU session could not be registered |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-3-SESSION_UNREG |
3-Error |
[chars][dec]: session [dec] |
The client's ISSU session could not be unregistered |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-3-START_NEGO_FAILED |
3-Error |
[chars][dec]: failed to |
The ISSU client cannot start its negotiation |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-3-TRANSFORM_FAILED |
3-Error |
[chars][dec]: [chars] transformation failed [chars] |
The transformation operation for the ISSU message has failed |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_ERROR-3-TRANSFORM_FAILED_DETAILED |
3-Error |
[chars][dec]: [chars] transformation failed for message [dec] endpoint [dec] [chars] |
The transformation operation for the ISSU message has failed |
ISSU_CLIENT_COMP |
LOG_STD_ACTION |
|
ISSU_INIT_FAILED-3-MPLS_TE_HA |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
ISSU_PROCESS-3-ABORT |
3-Error |
[chars] |
Provides abort status information |
install |
"Observe the status message" |
|
ISSU_PROCESS-3-ABORTVERSION |
3-Error |
issu abortversion: [chars] |
The ISSU abortversion command can be run only from the LoadVersion or RunVersion state |
install |
"Please proceed to reinitializing the ISSU process" |
|
ISSU_PROCESS-3-FILESYS |
3-Error |
'[chars]' filesystem does not exist\n |
Verification of the filesystem failed |
install |
"The file needs to be downloaded to the flash disk" |
|
ISSU_PROCESS-3-IMAGE |
3-Error |
[chars] is loading the wrong image [ [chars] ] expected image [ [chars] ] |
Wrong image is being loaded during ISSU process. |
install |
"Check the detail state of ISSU process make sure " "the right images are loaded on Active and " "on Standby" |
|
ISSU_PROCESS-3-IPC_AGENT |
3-Error |
[chars] [ [chars] ] |
The ISSU process IPC agent had an error. |
install |
"Copy the error and send it to TAC." |
|
ISSU_PROCESS-3-IPC_MSG |
3-Error |
[chars] |
The ISSU process IPC MSG Queue Setup encountered an error. |
install |
"Copy the error and send it to TAC." |
|
ISSU_PROCESS-3-LOADVERSION |
3-Error |
[chars] |
The ISSU commitversion command did not fulfill the necessary criteria. This can happen due to the following conditions not being met. \n1. Current ISSU state is not RunVersion \n2. Secondary Version doesn't exist on Standby \n3. Standby BOOT variable doesn't exist \n4. The new image is not the first in BOOT on Standby \n5. Active BOOT variable is not set \n6. Primary Version on Active doesn't exist \n7. New image is not the first in Active BOOT \n8. Configuration register is not 0x2102 |
install |
"Fix the error and try the command again" |
|
ISSU_PROCESS-3-NVRAM |
3-Error |
[chars] |
NVRAM variables are not set properly. |
install |
"The issu commands or the hw-module command did not " "set the variables properly." |
|
ISSU_PROCESS-3-PARAMETERS |
3-Error |
[chars] [chars] parameters are wrong |
The system could not be configured for ISSU |
install |
"Fix the error and try the command again" |
|
ISSU_PROCESS-3-PEER |
3-Error |
[chars] |
The ISSU process cannot continue with negotiation as it can't verify the peer's state.\n |
install |
"Make sure the peer is present and try again.\n" "If the problem persists send the output of " "'show issu state' and 'show version' to TAC." |
|
ISSU_PROCESS-3-PRST |
3-Error |
[chars] |
Persistent variables are not set properly. |
install |
"The issu commands or the hw-module command did not " "set the variables properly." |
|
ISSU_PROCESS-3-RF |
3-Error |
[chars] [ [chars] ] |
The ISSU process RF client had an error. |
install |
"Copy the error and send it to TAC." |
|
ISSU_PROCESS-3-ROLLBACK_TIMER |
3-Error |
[chars] |
The rollback timer could not be configured |
install |
"Fix the error and try the command again" |
|
ISSU_PROCESS-3-SYSTEM |
3-Error |
[chars] |
The configuration register value should not be changed while the ISSU process is in progress |
install |
"The low order byte of the configuration register " "should be 0x02 during the upgrade process" |
|
ISSU_PROCESS-3-TRANSFORM |
3-Error |
[chars] [ [chars] ] |
The ISSU process transform utility had an error. |
install |
"Send the output of 'show version' from the Active " "and the Standby and send it to TAC." |
|
ISSU_PROCESS-3-UAM |
3-Error |
[chars] [chars] |
Return code failure from calling UAM API. |
install |
"Got unexpected rc from calling UAM API." |
|
ISSU_PROCESS-4-ABORT_ISSU |
4-Warning |
[chars] |
The peer has been determined to be incompatible and hence is being reloaded. |
install |
"Send the output of 'show redundancy history' from " "the Active to TAC." |
|
ISSU_PROCESS-4-ACCEPTVERSION_WARNING |
4-Warning |
ISSU auto-rollback will be initiated in [dec] minutes. |
It shows the warning message several minutes before the expiration of rollback timer |
install |
"Issue the acceptversion command before the " "expiration of rollback timer" |
|
ISSU_PROCESS-6-COMMITVERSION_INFO |
6-Information |
[chars] |
Provides the issu state information |
install |
"Observe the status message" |
|
ISSU_PROCESS-6-LOADVERSION_INFO |
6-Information |
[chars] |
Provides the issu state information |
install |
"Observe the status message" |
|
ISSU_PROCESS-6-RUNVERSION_INFO |
6-Information |
[chars] |
Provides the issu state information |
install |
"Observe the status message" |
|
ISSU_PROCESS-6-SELF_RELOAD |
6-Information |
slot [dec] countdown to self-reload started [dec] second delay\n |
Self reload from Upgrade Director's instructions |
install |
"Log the circumstances" |
|
ISSU_PROCESS-6-SELF_RELOAD_CANCEL |
6-Information |
Self-reload cancelled on slot [dec]\n |
Cancel of self-reload from user 'abort' instruction |
install |
"Log the circumstances" |
|
ISSU_PROCESS-7-DEBUG |
7-Debug |
[chars] |
Debug commands for the ISSU process. The system is \nattempting to recover from an unknown error.\n |
install |
"Send the output of 'show logging' to TAC for " "debugging purposes." |
|
ISSU_XFORM-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
ISSU-3-BAD_PARAMS |
3-Error |
[chars] |
Bad parameters are being passed |
ha-issu-infra |
"Copy the error and send it to TAC. TAC team can contact ISSU infrastructure team to investigate the problem." |
|
ISSU-3-BASE_CLIENT_CHECK_COMPATIBILITY |
3-Error |
[chars] |
Error found during checking of ISSU base client compatibility |
ha-issu-infra |
"Copy the error and send it to TAC. TAC team can contact ISSU infrastructure team to investigate the problem." |
|
ISSU-3-CAP_TABLE_OUT_OF_BOUND |
3-Error |
Cap_table_count [dec] is out of bound max is [dec] for |
The cap_table_count is out of bound for the cap_entry_id. |
ha-issu-infra |
"Copy the error and send it to TAC. TAC team " "can contact ISSU infrastructure team to check why the count " "is out of bound for the cap_entry_id." |
|
ISSU-3-CLIENT_OR_ENTITY_NOT_REG |
3-Error |
Client [chars][dec] or entity[dec] is not registered [chars]. |
- |
- |
- |
|
ISSU-3-CLIENT_REG_DIST |
3-Error |
Failed to [chars] distributed client [dec] |
Distributed client reservation or unreservation failed |
ha-issu-infra |
"Copy the error and send it to TAC. TAC team can contact ISSU infrastructure team to investigate the problem." |
|
ISSU-3-DEBUG_ERROR |
3-Error |
[chars] |
Error happens when turning on ISSU debug. |
ha-issu-infra |
"'show issu client | include <client id>' \n\copy the error and send it to TAC. TAC team can contact ISSU client team to \n\check why reported item is used if client problem reported. \n\Otherwise contact ISSU infrastructure team instead" |
|
ISSU-3-DUMMY_VERSION_OUT_OF_RANGE |
3-Error |
Dummy msg version [dec] is out of range for msg[dec] under client [chars][dec] and entity[dec]. |
dummy msg version is out of range |
ha-issu-infra |
"'show issu message type | include <client id> <entity_id> <msg_type>' and copy the error and send it to TAC. TAC team can contact ISSU team to check why reported item is registered already" |
|
ISSU-3-DUMY_ENTRY_NOT_LAST |
3-Error |
Dumy cap entry is not last one for cap group[dec] registration |
Dumy cap entry is not last one for cap group registration |
ha-issu-infra |
"'show issu client | include <client id>' and \n\copy the error and send it to TAC. TAC team can contact ISSU client team \n\to check why dumy entry is not last one during registration" |
|
ISSU-3-DUP_DUMMY_VERSION_REG |
3-Error |
[chars] is already registered under client [chars][dec] entity[dec] and msgtype[dec] |
Item is registered already under that msg type. |
ha-issu-infra |
"'show issu message type | include <client id> <entity_id> <msgtype>' and copy the error and send it to TAC. TAC team can contact ISSU team to check why reported item is registered already" |
|
ISSU-3-DUP_ENTITY_REG |
3-Error |
Entity[dec] is registered already under client [chars][dec] |
- |
- |
- |
|
ISSU-3-DUP_ITEM_IN_REG_UNDER_ENTITY |
3-Error |
[chars] is duplicated [chars] under client [chars][dec] and entity[dec] |
- |
- |
- |
|
ISSU-3-DUP_REG_ENDPOINT |
3-Error |
Endpoint is registered already. |
Endpoint is registered already. |
ha-issu-infra |
"'show issu endpoint' to check if ISSU subsystem \n\is initialized twice." |
|
ISSU-3-DUP_REG_UNDER_ENDPOINT |
3-Error |
[chars][dec] is registered already under endpoint. |
Item is registered already under endpoint. |
ha-issu-infra |
"'show issu client | include <client id>' \n\copy the error and send it to TAC. TAC team can contact ISSU client team \n\to check why reported item is registered already if client problem reported. \n\Otherwise contact ISSU infrastructure team instead" |
|
ISSU-3-DUP_REG_UNDER_ENTITY |
3-Error |
[chars][dec] is registered already under client [chars][dec] and |
Item is registered already under client and entity. |
ha-issu-infra |
"'show issu client | include <client id>' and \n\copy the error and send it to TAC. TAC team can contact ISSU client team \n\to check why reported items under entity is registered already" |
|
ISSU-3-EMPTY_DUMMY_VERSION |
3-Error |
[chars] is empty under client [chars][dec] entity[dec]. |
dummy version is empty. |
ha-issu-infra |
"copy the error and send it to TAC. TAC team can contact ISSU team to check why reported item is registered already" |
|
ISSU-3-EMPTY_UNDER_CLIENT |
3-Error |
[chars] is empty under client [chars][dec]. |
Item is empty in client. |
ha-issu-infra |
"'show issu client | include <client id>' and \n\copy the error and send it to TAC. TAC team can contact ISSU client team \n\to check why reported item under client is empty" |
|
ISSU-3-EMPTY_UNDER_ENDPOINT |
3-Error |
[chars] is empty under endpoint. |
Item is empty under endpoint. |
ha-issu-infra |
"'show issu client | include <client id>' \n\copy the error and send it to TAC. TAC team can contact ISSU client team to \n\check why reported item is empty if client problem reported. \n\Otherwise contact ISSU infrastructure team instead" |
|
ISSU-3-EMPTY_UNDER_ENTITY |
3-Error |
[chars] is empty [chars] under client [chars][dec] and entity[dec]. |
- |
- |
- |
|
ISSU-3-ENDPOINT_NOT_REG |
3-Error |
Endpoint is not registered yet. |
Endpoint is not registered yet. |
ha-issu-infra |
"Copy the error and send it to TAC. \n\TAC team can contact ISSU infrastruture team to check why endpoint is not registered" |
|
ISSU-3-ERP_AGENT |
3-Error |
[chars] |
The send message function call failed. |
ha-issu-infra |
"Copy the error and send it to TAC.\n\TAC team can contact ISSU infrastructure team to check \n\why one of the primary functions for the ERP agent failed" |
|
ISSU-3-ERP_CLIENT |
3-Error |
For context ID [dec] [chars] |
One of the primary functions for the ERP client failed. |
ha-issu-infra |
"Copy the error and send it to TAC.\n\TAC team can contact ISSU infrastructure team to check \n\why one of the primary functions for the ERP client failed" |
|
ISSU-3-ERP_CLIENT_EVENT |
3-Error |
Unknown [chars] event - [dec] |
An unknown event was received |
ha-issu-infra |
"Copy the error and send it to TAC.\n\TAC team can contact ISSU infrastructure team to check \n\why an unknown event was received" |
|
ISSU-3-EXTERNAL_MATRIX_FILE_ERR |
3-Error |
Line [dec]: [chars] |
External matrix file data is corrupted |
ha-issu-infra |
"An error was found in the external " "matrix data file. Open a case with TAC and attach output of " "<CmdBold>more ivfs:/<matrix_cm_file><NoCmdBold> command " "where <matrix_cm_file> is the output of <CmdBold>dir " "system:image<NoCmdBold> command." |
|
ISSU-3-FAILED_TO_ALLOC_CHUNK_MEMORY |
3-Error |
chunk allocation for [chars] failed. |
Chunk malloc failed. |
ha-issu-infra |
"copy the error and send it to TAC. TAC team can \n\contact ISSU client team" |
|
ISSU-3-FAILED_TO_ALLOC_DUMMY_VERSION |
3-Error |
Can not allocate [chars] under client [chars][dec] and entity[dec] |
Can not allocate dummy version under client and entity. |
ha-issu-infra |
"'show proc mem' or 'show buffs' to check if memory \n\or buffer is full. shutdown unused tasks or reset cards usually can recover \n\those memory leak problem. Copy the error and send it to TAC if those actions \n\does not help." |
|
ISSU-3-FAILED_TO_ALLOC_ENTITY |
3-Error |
Can not allocate entity[dec] under client [chars][dec] |
Can not allocate entity control block under client. |
ha-issu-infra |
"'show proc mem' or 'show buffs' to check if memory \n\or buffer is full. shutdown unused tasks or reset cards usually can recover \n\those memory leak problem. Copy the error and send it to TAC if those actions \n\does not help." |
|
ISSU-3-FAILED_TO_ALLOC_FUNCT_UNDER_ENDPOINT |
3-Error |
Can not allocate [chars][dec] [chars]. |
Can not allocate function callback. |
ha-issu-infra |
"'show proc mem' or 'show buffs' to check if memory \n\or buffer is full. shutdown unused tasks or reset cards usually can recover \n\those memory leak problem. 'show issu client | include <client id>' \n\copy the error and send it to TAC. TAC team can contact ISSU client team \n\if client problem reported. Otherwise contact ISSU infrastructure team instead" |
|
ISSU-3-FAILED_TO_ALLOC_FUNCT_UNDER_ENTITY |
3-Error |
Can not allocate [chars] under client [chars][dec] and entity[dec] |
- |
- |
- |
|
ISSU-3-FAILED_TO_ALLOC_MEMORY |
3-Error |
memory allocation for [chars] failed. |
malloc failed. |
ha-issu-infra |
"copy the error and send it to TAC. TAC team can \n\contact ISSU client team" |
|
ISSU-3-FAILED_TO_ALLOC_UNDER_ENDPOINT |
3-Error |
Can not allocate [chars] [chars][dec] control block. |
Can not allocate control block. |
ha-issu-infra |
"'show proc mem' or 'show buffs' to check if memory \n\or buffer is full. shutdown unused tasks or reset cards usually can recover \n\those memory leak problem. 'show issu client | include <client id>' \n\copy the error and send it to TAC. TAC team can contact ISSU client team \n\if client problem reported. Otherwise contact ISSU infrastructure team instead" |
|
ISSU-3-FAILED_TO_ALLOC_UNDER_ENTITY |
3-Error |
Can not allocate [chars][dec] under client [chars][dec] and entity[dec] |
- |
- |
- |
|
ISSU-3-FAILED_TO_ALLOC_UNDER_GROUP |
3-Error |
Can not allocate [chars][dec] for [chars][dec] registration under client |
Can not allocate item for group registration under client and entity. |
ha-issu-infra |
"'show proc mem' or 'show buffs' to check if memory \n\or buffer is full. shutdown unused tasks or reset cards usually can recover \n\those memory leak problem. Copy the error and send it to TAC if those actions \n\does not help." |
|
ISSU-3-FAILED_TO_ALLOC_UNDER_MSG |
3-Error |
Can not allocate [chars] for msg [dec] registration under client |
Can not allocate control block for msg registration. |
ha-issu-infra |
"'show proc mem' or 'show buffs' to check if memory \n\or buffer is full. shutdown unused tasks or reset cards usually can recover \n\those memory leak problem. Copy the error and send it to TAC if those actions \n\does not help." |
|
ISSU-3-FAILED_TO_ALLOC_UNDER_MSG_SES |
3-Error |
Can not allocate [chars] for msg session[dec] registration under |
Can not allocate control block for msg session registration. |
ha-issu-infra |
"'show proc mem' or 'show buffs' to check if memory \n\or buffer is full. shutdown unused tasks or reset cards usually can recover \n\those memory leak problem. Copy the error and send it to TAC if those actions \n\does not help." |
|
ISSU-3-FAILED_TO_CREATE_ID32_SPACE |
3-Error |
Failed to create ID32 space. |
Failed to create ID32 space. |
ha-issu-infra |
"'show proc mem' or 'show buffs' to check if memory \n\or buffer is full. shutdown unused tasks or reset cards usually can recover \n\those memory leak problem. Copy the error and send it to TAC if those actions \n\does not help." |
|
ISSU-3-FAILED_TO_INIT_ISSU_PROTO |
3-Error |
Failed to initialize ISSU proto. |
Failed to initialize ISSU proto. |
ha-issu-infra |
"Copy the error and send it to TAC.\n\TAC team can contact ISSU infrastructure team to check \n\why ISSU protocol can not initialize correctly" |
|
ISSU-3-FAILED_TO_UNREG_SES |
3-Error |
Failed to unregister [chars] session under client [chars][dec] and |
Failed to unregister session. |
ha-issu-infra |
"'show proc mem' or 'show buffs' to check if memory \n\or buffer is full. shutdown unused tasks or reset cards usually can recover \n\those memory leak problem. Copy the error and send it to TAC if those actions \n\does not help." |
|
ISSU-3-FOF_NEGO_RESULT_INCONSISTENT |
3-Error |
FOF owner msg type [dec] of owner client [chars][dec] entity [dec]. |
An owner FOF message of interest to an using client has inconsistent negotiation results in different owner sessions under the same entity |
ha-issu-infra |
"Copy the error and send it to TAC. TAC team can " "contact ISSU infrastructure team to investigate " "the problem." |
|
ISSU-3-FSM_BADMSG |
3-Error |
Peer session [dec] while receiving message [chars] is wrong. |
Session are mismatched on peers or not found. |
ha-issu-infra |
"'show issu session | include <session id>' and \n\copy the error and send it to TAC. TAC team can contact ISSU client team \n\to make sure that receiving path uses correct session id." |
|
ISSU-3-FSM_DUP_UID |
3-Error |
Duplicate unique_id on session [dec]: my_uid [dec] peer_uid [dec]. |
Violate the requirement that each endpoint must have distinctive \n\ identifier. |
ha-issu-infra |
"Copy the error and send it to TAC. \n\TAC team can contact platform team to provide distinctive identifier \n\for endpoint" |
|
ISSU-3-FSM_INIT |
3-Error |
Fail to create process during FSM init. |
The creation of FSM timer process fails. |
ha-issu-infra |
"User should check system resource during bootup\n\ time." |
|
ISSU-3-FSM_MISMATCH_MTU |
3-Error |
ISSU nego failed for client [chars][dec] entity_id [dec] session [dec] due to mismatch of mtu size [dec] & [dec]. |
- |
- |
- |
|
ISSU-3-FSM_NEGO_SEND_ERR |
3-Error |
Client '[chars]' with ID [dec] encountered '[chars]' in session [dec]. |
Creation/removal of the named port failed for IPC. |
ha-issu-infra |
"Copy the error and send it to TAC.\n\TAC team can contact ISSU infrastructure team to check \n\why creation/removal of the named port failed for IPC" |
|
ISSU-3-FSM_RUNTIME_ERR |
3-Error |
Client '[chars]' with ID [dec] has '[chars]' in session [dec]. |
Runtime error occurs during FSM negotiation. |
ha-issu-infra |
"'show issu session | include <session id>' and \n\copy the error and send it to TAC. TAC team can contact ISSU client team \n\to check why this runtime error occurs. Use 'show issu fsm | include <session id>'\n\to get error reason for futher debug." |
|
ISSU-3-HANDLE_SIZE |
3-Error |
Handle buffer size is [dec] should be [dec] |
Statically defined handle buffer size is incorrect |
ha-issu-infra |
"Copy the error and send it to TAC. TAC team can contact ISSU infrastructure team to investigate the problem." |
|
ISSU-3-IN_USE_UNDER_ENDPOINT |
3-Error |
[chars][dec] is in use under endpoint |
Item is in use under endpoint. |
ha-issu-infra |
"'show issu client | include <client id>' \n\copy the error and send it to TAC. TAC team can contact ISSU client team to \n\check why reported item is used if client problem reported. \n\Otherwise contact ISSU infrastructure team instead" |
|
ISSU-3-IN_USE_UNDER_ENTITY |
3-Error |
[chars][dec] is in use under client [chars][dec] and entity[dec] |
- |
- |
- |
|
ISSU-3-INCOMPATIBLE_BASE_CLIENTS |
3-Error |
[chars]\n |
List of ISSU base clients found incompatible |
ha-issu-infra |
"Copy the error and send it to TAC. TAC team can contact ISSU infrastructure team to investigate the problem." |
|
ISSU-3-INCOMPATIBLE_PEER_UID |
3-Error |
Setting image [chars] version [chars] on peer uid [dec] as incompatible |
Peer is incompatible |
ha-issu-infra |
"A runtime exception occurred in the previous run.\n\Clear the condition according to the client eg. config-sync and reload \n\the Standby" |
|
ISSU-3-INCONSISTENT_MSG_TYPE |
3-Error |
[chars] |
Foreign owned field transformation failed |
ha-issu-infra |
"Copy the error and send it to TAC." |
|
ISSU-3-INTERRUPT_LEVEL_SESSION_OPERATION |
3-Error |
[chars] [chars] [dec] [chars] [dec] |
ISSU session registeration or unregisteration should not be done at interrupt level |
ha-issu-infra |
"Copy the error and send it to TAC. TAC team can contact ISSU infrastructure team to investigate the problem." |
|
ISSU-3-INVALID_ITEM_UNDER_ENDPOINT |
3-Error |
Invalid [chars] under endpoint |
Invalid item under endpoint |
ha-issu-infra |
"'show issu client | include <client id>' \n\copy the error and send it to TAC. TAC team can contact ISSU client team to \n\check why invalid item is used if client problem reported. \n\Otherwise contact ISSU infrastructure team instead" |
|
ISSU-3-INVALID_ITEM_UNDER_ENTITY |
3-Error |
Invalid [chars] under client [chars][dec] and entity[dec] |
- |
- |
- |
|
ISSU-3-INVALID_PARAM_UNDER_SES |
3-Error |
Invalid params [chars] under session[dec] |
Invalid parameters under session |
ha-issu-infra |
"'show issu session | include <session id>' \n\to find out which client's session is causing this error msg. \n\copy the error and send it to TAC. TAC team can contact ISSU team to \n\check why invalid params is used if problem reported. \n\Otherwise contact ISSU infrastructure team instead" |
|
ISSU-3-INVALID_VERSION_LOWHIGH |
3-Error |
Invalid low[dec] and high[dec] value for msg[dec] under client |
Invalid low and high value for group registration. |
ha-issu-infra |
"'show issu client | include <client id>' and \n\copy the error and send it to TAC. TAC team can contact ISSU client team \n\to check why invalid low or high version is used for group registration" |
|
ISSU-3-ISSU_INIT_NOT_COMPLETE |
3-Error |
[chars] |
ISSU initialization has not been completed |
ha-issu-infra |
"Copy the error and send it to TAC. TAC team can contact ISSU infrastructure team to investigate the problem." |
|
ISSU-3-JID |
3-Error |
Failed to get the local process JID with err [dec] |
The system manager call to collect the job-id failed |
ha-issu-infra |
"Copy the error and send it to TAC. TAC team can contact ISSU infrastructure team to investigate the problem." |
|
ISSU-3-MISSING_ITEM_IN_REG |
3-Error |
[chars][dec] is not available [chars] under client [chars][dec] and entity[dec] |
- |
- |
- |
|
ISSU-3-MSG_NEGO_RESULT_CHUNK |
3-Error |
Failed to [chars] element [hec] |
Failed to lock or free the message negociation result chunk element |
ha-issu-infra |
"MSG negociation result element is locked and unlocked during avl_walk_extended of msg_nego_result_cb_root. The failure to lock or free of the element indicates invalid element or corrupted chunk memory. Copy the error and send it to TAC. TAC team can contact ISSU infrastructure team to investigate the problem." |
|
ISSU-3-MSG_SES_IN_MSG_NOT_FOUND |
3-Error |
The intended session [dec] specified in received [chars] for client [chars][dec] is not found. |
Cannot find the session with the session id\n\ specified in the received message. |
ha-issu-infra |
"'show issu session | include <session id>' and \n\copy the error and send it to TAC. TAC team can contact ISSU client team \n\to make sure that receiving path uses correct session id." |
|
ISSU-3-NO_PEER_UID |
3-Error |
No peer uid found at [chars] |
No peer uid with this value found registered in ISSU Database |
ha-issu-infra |
"Copy the error and send it to TAC.\n\TAC team can contact ISSU infrastructure team to check \n\why no peer uid with this value foundi registered in ISSU Database" |
|
ISSU-3-NO_UID |
3-Error |
No uid [dec] registered with ISSU at [chars] |
No uid with this value found registered in ISSU Database |
ha-issu-infra |
"Copy the error and send it to TAC.\n\TAC team can contact ISSU infrastructure team to check \n\why no uid with this value found registered in ISSU Database" |
|
ISSU-3-NON_ISSU_ID_UNDER_ENDPOINT |
3-Error |
Non ISSU [chars] |
Peer endpoint does not support ISSU |
ha-issu-infra |
"Copy the error and send it to TAC.\n\TAC team can contact ISSU infrastruture team to check why non-issu ID is used" |
|
ISSU-3-NOT_DUMY_CAP_TYPE |
3-Error |
Cap type[dec] is not dumy one. |
Cap type is not dumy one. |
ha-issu-infra |
"'show issu cap type | include <cap type>' and \n\copy the error and send it to TAC. TAC team can contact ISSU client team \n\to check why dummy cap type is not used" |
|
ISSU-3-NOT_FIND_FUNCT_UNDER_SESSION |
3-Error |
Can not find [chars] under [chars] session[dec]. |
Can not find function under session. |
ha-issu-infra |
"'show issu session | include <session id>' and \n\copy the error and send it to TAC. TAC team can contact ISSU client team \n\to check why control block under session can not be found" |
|
ISSU-3-NOT_FIND_MSG_SES |
3-Error |
Can not find message session[dec] [chars]. |
- |
- |
- |
|
ISSU-3-NOT_FIND_UNDER_ENDPOINT |
3-Error |
Can not find [chars]0x[hec] control block under endpoint. |
- |
- |
- |
|
ISSU-3-NOT_FIND_UNDER_ENTITY |
3-Error |
Can not find [chars][dec] control block under client [chars][dec] and |
Can not find control block under client and entity. |
ha-issu-infra |
"'show issu client | include <client id>' and \n\copy the error and send it to TAC. TAC team can contact ISSU client team \n\to check why control blcok can not be found" |
|
ISSU-3-NOT_FIND_UNDER_SESSION |
3-Error |
Can not find [chars][dec] under [chars] session[dec]. |
Can not find item under session. |
ha-issu-infra |
"'show issu session | include <session id>' and \n\copy the error and send it to TAC. TAC team can contact ISSU client team \n\to check why control block under session can not be found" |
|
ISSU-3-NOT_REG_UNDER_ENDPOINT |
3-Error |
[chars][dec] is not registered under endpoint. |
Item is not registered under endpoint. |
ha-issu-infra |
"'show issu client | include <client id>' \n\copy the error and send it to TAC. TAC team can contact ISSU client team to \n\check why reported item is not registered if client problem reported. \n\Otherwise contact ISSU infrastructure team instead" |
|
ISSU-3-NOT_REG_UNDER_ENTITY |
3-Error |
[chars][dec] is not registered under client [chars][dec] and entity[dec] |
- |
- |
- |
|
ISSU-3-NULL_CALLBACK_UNDER_ENDPOINT |
3-Error |
[chars] callback is NULL for registration. |
Callback is NULL for registration |
ha-issu-infra |
"'show issu client | include <client id>' \n\copy the error and send it to TAC. TAC team can contact ISSU client team to \n\check why reported callback is NULL if client problem reported. \n\Otherwise contact ISSU infrastructure team instead" |
|
ISSU-3-NULL_CALLBACK_UNDER_ENTITY |
3-Error |
[chars] callback is NULL for msg session registration under client [chars][dec] and entity[dec] |
Callback is NULL for msg session registration. |
ha-issu-infra |
"'show issu client | include <client id>' and \n\copy the error and send it to TAC. TAC team can contact ISSU client team \n\to check why reported callback is NULL" |
|
ISSU-3-NULL_CALLBACK_UNDER_SESSION |
3-Error |
Can not register null [chars] callback in [chars] session[dec]. |
- |
- |
- |
|
ISSU-3-PEER_IMAGE_INCOMPATIBLE |
3-Error |
Peer image [chars] version [chars] on peer uid [dec] is incompatible |
Peer is incompatible |
ha-issu-infra |
"A runtime exception occurred in the previous run.\n\Clear the condition according to the client eg. config-sync and reload \n\the Standby" |
|
ISSU-3-PEER_IMAGE_NOT_IN_INCOMP_LIST |
3-Error |
Peer image [chars] version [chars] on peer uid [dec] is not in the |
Peer is incompatible |
ha-issu-infra |
"A runtime exception occurred in the previous run.\n\Clear the condition according to the client eg. config-sync and reload \n\the Standby" |
|
ISSU-3-PEER_IMAGE_REM_FROM_INCOMP_LIST |
3-Error |
Peer image [chars] version [chars] on peer uid [dec] being removed |
Peer is incompatible |
ha-issu-infra |
"A runtime exception occurred in the previous run.\n\Clear the condition according to the client eg. config-sync and reload \n\the Standby" |
|
ISSU-3-PEER_INCOMP_SET |
3-Error |
Peer incompatibility set for image [chars] version [chars] on peer |
Peer is incompatible |
ha-issu-infra |
"A runtime exception occurred in the previous run.\n\Clear the condition according to the client eg. config-sync and reload \n\the Standby" |
|
ISSU-3-PEER_UID_CB_IS_NULL |
3-Error |
Peer uid control block is NULL |
Peer is incompatible |
ha-issu-infra |
"A runtime exception occurred in the previous run.\n\Clear the condition according to the client eg. config-sync and reload \n\the Standby" |
|
ISSU-3-PROTO_CLIENT_ENTITY_UNREG |
3-Error |
Proto Client entity unreg for [chars] has failed |
Protocol client has failed to unregister its entity with ISSU |
ha-issu-infra |
"Copy the error and send it to TAC.\n\TAC team can contact ISSU infrastructure team to check \n\why protocol client has failed to unregister its entity with ISSU" |
|
ISSU-3-PROTO_CLIENT_REG |
3-Error |
Proto Client registration for [chars] has failed |
Protocol client has failed to register with ISSU |
ha-issu-infra |
"Copy the error and send it to TAC.\n\TAC team can contact ISSU infrastructure team to check \n\why protocol client has failed to register with ISSU" |
|
ISSU-3-REF_TREE |
3-Error |
[chars] reference tree [chars] failed |
The AVL based ISSU reference tree operation failed |
ha-issu-infra |
"Copy the error and send it to TAC. TAC team can contact ISSU infrastructure team to investigate the problem." |
|
ISSU-3-SESSION_ID_ERROR |
3-Error |
Failed to [chars] session id [dec] for [chars] |
Session ID related operation failed |
ha-issu-infra |
"Copy the error and send it to TAC. TAC team can contact ISSU infrastructure team to investigate the problem." |
|
ISSU-3-SESSION_RENEGOTIATE |
3-Error |
Client Attempting to renegotiate on session [dec] |
Client Attempting to renegotiate session |
ha-issu-infra |
"A Client is attempting to renegotiate on session\n\without unregistering it and do the negotiation over again. This is not allowed\n\and is considered an error condition. The client should unregister the msg\n\session first and then re-register and attempt the negotiation." |
|
ISSU-3-SET_UNKNOWN_UID |
3-Error |
Unknown unique_id is set. |
Platform team should provide distinctive identifier for endpoint. |
ha-issu-infra |
"Copy the error and send it to TAC. \n\TAC team can contact platform team to provide distinctive identifier \n\for endpoint" |
|
ISSU-3-TRANSPORT_ERP_UID_CB_IS_NULL |
3-Error |
Transport ERP uid control block is NULL |
Peer is incompatible |
ha-issu-infra |
"A runtime exception occurred in the previous run.\n\Clear the condition according to the client eg. config-sync and reload \n\the Standby" |
|
ISSU-3-UNKNOWN_DOMAIN_ID |
3-Error |
Unknown domain id [dec] under client [chars][dec] entity [dec] |
- |
- |
- |
|
ISSU-3-UNKNOWN_ENTITY_ID |
3-Error |
Unknown entity id under client [chars][dec] |
Unknown entity id under client |
ha-issu-infra |
"'show issu client | include <client id>' and \n\copy the error and send it to TAC. TAC team can contact ISSU client team \n\to check why unknown entity id is used during registration" |
|
ISSU-3-UNKNOWN_ID_UNDER_ENDPOINT |
3-Error |
Can not use unknown [chars]. |
Can not use unknown id. |
ha-issu-infra |
"Copy the error and send it to TAC.\n\TAC team can contact ISSU infrastruture team to check why unknown ID is used" |
|
ISSU-3-UNKNOWN_ID_UNDER_ENTITY |
3-Error |
Unknown [chars] under client [chars][dec] and entity[dec] |
- |
- |
- |
|
ISSU-3-VERSION_LOWHIGH_NOT_MATCH_TABLE_SIZE |
3-Error |
Version low[dec] and high[dec] value for msg[dec] does not |
Version low and high value for msg does not match table size. |
ha-issu-infra |
"'show issu client | include <client id>' and \n\copy the error and send it to TAC. TAC team can contact ISSU client team \n\to check why low/high version is not macth table size for msg registration" |
|
ISSU-3-VERSION_OUT_OF_ORDER |
3-Error |
Msg version[dec][dec] is out of order for msg[dec] under client |
Msg version is out of order for group registration. |
ha-issu-infra |
"'show issu client | include <client id>' and \n\copy the error and send it to TAC. TAC team can contact ISSU client team \n\to check why version is out of order for msg registration" |
|
ISSU-3-VERSION_OUT_OF_RANGE |
3-Error |
Msg version[dec][dec] is out of range for msg[dec] under client |
Msg version is out of range for group registration. |
ha-issu-infra |
"'show issu client | include <client id>' and \n\copy the error and send it to TAC. TAC team can contact ISSU client team \n\to check why version is out of range for group registration" |
|
ISSU-3-XFORM_CALLBACK |
3-Error |
No [chars] callback specified for client [chars][dec] msg [dec] from version [dec] to version [dec] in session [dec] . |
Client didn't specify transformation function |
ha-issu-infra |
"Copy the error and send it to TAC. TAC team\n\ can contact ISSU client team to check why reported\n\ callback is not specified" |
|
ISSU-4-FSM_INCOMP |
4-Warning |
Version of local ISSU client [chars][dec] in session [dec] is |
The protocol versions of the local and remote clients are\n\ incompatible. These clients can not communicate with each\n\ other. |
ha-issu-infra |
"Use 'show version' and 'show issu clients' to help\n\ verify that the software images are incompatible. Upgrade\n\ the software images on each unit to versions that are \n\ compatible. " LOG_STD_RECUR_ACTION |
|
ISSU-4-MSG_INCOMP |
4-Warning |
Message[dec] is incompatible under msg session[dec]. |
- |
- |
- |
|
ISSU-4-NEGO_NOT_FINISHED |
4-Warning |
Negotiation is not finished for client [chars][dec] msg session[dec]. |
- |
- |
- |
|
ISYNC_CHKPT-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
ISYNC-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
ITEM_SIZE_TOO_BIG-3-MPLS_TE_HA |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
IVR_MSB-3-INVALID_MAX_PROMPTS |
3-Error |
[chars]: This version of IOS does not support prompt playout for IVR applications.\n |
This error will be displayed if an IVR application is used on a gateway that does\n\ not support IVR prompt playout. |
voice-ivr |
"Ensure that this platform and IOS version support the IVR feature set." |
|
IVR_MSB-3-INVALID_PROMPT_SIZE |
3-Error |
[chars]: Bad size for the prompt file [chars]. Read size [dec]. Expected size [dec].\n |
Prompt file size error. File may be corrupted. |
voice-ivr |
"Replace the bad prompt file." |
|
IVR_MSB-3-NO_IO_MEMORY |
3-Error |
[chars]: Failed to create pool_group [hec] buffer_pool [hec] platform_mc_buf_pool_count [dec]\n |
No IO memory to create IVR private pak pool |
voice-ivr |
"Check to see if there is enough IO memory." |
|
IVR_MSB-3-NOPROMPT |
3-Error |
Could not create IVR prompt\n [chars]\n errno=[dec]=[chars] |
Could not read in the IVR prompt |
voice-ivr |
"Check that prompt exists on the server and is readable." |
|
IVR-1-APP_PARALLEL_INVALID_LIST |
1-Alert |
Call terminated. Huntgroup '[dec]' does not contain enough valid SIP end-points to proceed with a parallel call. \n |
The call to a parallel hunt-group was denied because less than \n\ two valid SIP end-points were found in the huntgroup list. |
voice-ivr |
"Check the hunt-group list's numbers. Remove any incorrect numbers \n\ or numbers that have a non-SIP dial-peer. If the numbers are from\n\ SIP phones then verify whether the phones have registered to the\n\ system yet." |
|
IVR-2-APP_CRIT |
2-Critical |
[chars]\n |
A critical message was reported by an IVR Tcl application. |
voice-scripts |
"The remedy of the problem is application specific." |
|
IVR-2-APP_CRIT_R |
2-Critical |
[chars]\n |
A critical message was reported by an IVR Tcl application. |
voice-scripts |
"The remedy of the problem is application specific." |
|
IVR-2-INVALID_DSAPP_DIALPEER |
2-Critical |
Service dsapp contains an invalid dial peer tag: [chars] |
An invalid dial peer tag has been configured for the dsapp service. The tag either is not in the range from 1 to 2147483647 or it belongs to a non-existent dial-peer. |
voice-ivr |
"Enter the <CmdBold>show running-config<NoCmdBold> " "or the <CmdBold>show dial-peer voice<NoCmdBold> " "command to find a valid dial peer tag. " "Reconfigure the dial peer with a valid tag or " "remove the dial peer tag completely to allow the " "system to match from the system dial peers." |
|
IVR-3-ABNORMAL_EXIT |
3-Error |
TCL IVR Process for this call with CallID [dec] exits bad event: [chars] received\n |
The TCL IVR call process exited for the specified call. The call \n\ process did not clear a prior call properly so other events could \n\ not be handled. Only the specified call is affected |
voice-ivr |
"If problem persists for subsequent callscopy the message exactly \n\ as it appears on the console or in the system log contact your \n\ Cisco technical support representative and provide the representative \n\ with the gathered information." |
|
IVR-3-APP_ERR |
3-Error |
[chars]\n |
An error message was reported by an IVR Tcl application. |
voice-scripts |
"The remedy of the problem is application specific." |
|
IVR-3-APP_ERR_R |
3-Error |
[chars]\n |
An error message was reported by an IVR Tcl application. |
voice-scripts |
"The remedy of the problem is application specific." |
|
IVR-3-BAD_IVR_VERSION |
3-Error |
Script requires version [dec].[dec] image supports [dec].[dec]\n |
IVR Script requires a higher IVR infrastructure version |
voice-ivr |
"Upgrade IOS or use a different script" |
|
IVR-3-BADSCRIPT |
3-Error |
Could not parse malformed IVR script: [chars]\n |
Could not parse malformed IVR script |
voice-ivr |
"Check the script and fix the syntax error." |
|
IVR-3-LOW_MEMORY |
3-Error |
IVR: Sytem running on low memory. Free memory: %l bytes. Call is rejected.\n |
System does not have enough CPU resources available to accept\n\ a new call |
voice-ivr |
"Ensure that the call setup rate is within the supported capacity of\n\ this gateway." |
|
IVR-3-NOSCRIPT |
3-Error |
Could not load IVR script\n [chars]\n errno=[dec]=[chars] |
Could not read in the IVR script |
voice-ivr |
"Check that script exists on the server and is readable." |
|
IVR-4-APP_WARN |
4-Warning |
[chars]\n |
A warning message was reported by an IVR Tcl application. |
voice-scripts |
"The remedy of the problem is application specific." |
|
IVR-4-APP_WARN_R |
4-Warning |
[chars]\n |
A warning message was reported by an IVR Tcl application. |
voice-scripts |
"The remedy of the problem is application specific." |
|
IVR-4-INVALID_DSAPP_BLINDTIME |
4-Warning |
Blind-xfer-wait-time [dec] is invalid. Resetting to [dec] seconds. |
The configured value for blind-xfer-wait-time was outside of the acceptable range 0-10 and has been reset to |
voice-ivr |
"If the new value for blind-xfer-wait-time is " "unacceptable you can change it from the command " " line interface." |
|
IVR-4-INVALID_DSAPP_TOGGLE_TIME |
4-Warning |
Disc-toggle-time [dec] is invalid. Resetting to [dec] seconds. |
The configured value for disc-toggle-time was outside of the acceptable range 10-30 and has been reset |
voice-ivr |
"If the new value for disc-toggle-time " "is unacceptable you can change it from the " "command line interface." |
|
IVR-5-APP_CALL_PREEMPTION |
5-Notice |
CallID [dec] is being preempted\n |
A notification message was reported by an IVR application on detecting callID [dec] being preempted. |
voice-ivr |
"This is not a problem but notifying syslog about preempted call." |
|
IVR-5-APP_LOG_DUR_CALL_DETECTED |
5-Notice |
[chars]\n |
System does not have enough CPU capacity to spawn a new instance of \n\ IVR application |
voice-ivr |
"Ensure that the call setup rate is within the supported capacity of\n\ this gateway." |
|
IVR-5-APP_MED_INACT_DETECTED |
5-Notice |
[chars]\n |
A notification message was reported by an IVR application on detecting media inactivity. |
voice-scripts |
"This is not a problem but notifying syslog about media inactivity." |
|
IVR-5-APP_MED_REACT_DETECTED |
5-Notice |
[chars]\n |
A notification message was reported by an IVR application on detecting media activity. |
voice-scripts |
"This is not a problem but notifying syslog about media activity." |
|
IVR-6-APP_INFO |
6-Information |
[chars]\n |
An informational message was reported by an IVR Tcl application. |
voice-scripts |
"The remedy of the problem is application specific." |
|
IVR-6-APP_INFO_R |
6-Information |
[chars]\n |
An informational message was reported by an IVR Tcl application. |
voice-scripts |
"The remedy of the problem is application specific." |
|
IVR-6-APP_PARALLEL |
6-Information |
Cannot use dial-peer [dec] parallel hunt-group for a rotary or |
The dial-peer for parallel hunt-groups must have a unique pilot number. |
voice-ivr |
"Create a unique dial-peer destination-number for the parallel \n\ hunt-group." |
|
IVR-6-APP_SEQ_HUNT |
6-Information |
Pilot hunt-group '[chars]' found in hunt-group list. Nested hunt-groups are allowed only as the hunt-group's final number.\n |
Nested sequential hunt-group detected in dial-peer rotary. \n\ Nested hunt-groups is unsupported. |
voice-ivr |
"Do not create hunt-group lists that contain hunt-group pilot numbers." |
|
IXP_MAP-3-ACR |
3-Error |
[chars] error detected: [chars] [chars] 0x[hec] 0x[hec] |
A software programming error for the ACR ESF Network Processor Client\n\ Mapper was detected. |
c7600-sip-400-clnt |
"This software programming error is not considered fatal to the\n\ operation of the ESF Network Processors. The software is designed to\n\ detect and report the error condition. If the error persists reset\n\ the affected device.\n\\n\ Record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-ATOM |
3-Error |
[chars] error detected: [chars] [chars] 0x[hec] 0x[hec] |
A software programming error for the ATOM ESF Network Processor Client\n\ Mapper was detected. |
c7600-sip-400-clnt |
"This software programming error is not considered fatal to the\n\ operation of the ESF Network Processors. The software is designed to\n\ detect and report the error condition. If the error persists reset\n\ the affected device.\n\\n\ Record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-CEM |
3-Error |
[chars] error detected: [chars] [chars] 0x[hec] 0x[hec] |
A software programming error for the CEM ESF Network Processor\n\ Client Mapper was detected. |
c7600-sip-400-clnt |
"This software programming error is not considered fatal to the\n\ operation of the ESF Network Processors. The software is designed to\n\ detect and report the error condition. If the error persists reset\n\ the affected device.\n\ \n\ Record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-CEMOUDP |
3-Error |
[chars] error detected: [chars] [chars] 0x[hec] 0x[hec] |
A software programming error for the CEMOUDP ESF Network Processor Client\n\ Mapper was detected. |
c7600-sip-400 |
"This software programming error is not considered fatal to the\n\ operation of the ESF Network Processors. The software is designed to\n\ detect and report the error condition. If the error persists reset\n\ the affected device.\n\\n\ Record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-DROP_BLOCK |
3-Error |
[chars] error detected - 0x[hec] 0x[hec] [dec] [dec] |
Error detected processing ESF Network Processor drop block\n\ allocations. |
c7600-sip-400-clnt |
"This is a software programming error. Record the \n\ Output from the following show commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-EXMEM |
3-Error |
[chars] [chars] error detected - [chars] [dec] |
Error detected managing the external memory of a Network Processor. |
c7600-sip-400-clnt |
"This is a software programming error. Record the \n\ Output from the following show commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-FRR_VLAN |
3-Error |
Error detected: [chars] [chars] 0x[hec] 0x[hec] |
A software programming error for the FRR Vlan ESF Network Processor Client\n\ Mapper was detected. |
c7600-sip-400-clnt |
"This software programming error is not considered fatal to the\n\ operation of the ESF Network Processors. The software is designed to\n\ detect and report the error condition. If the error persists reset\n\ the affected device.\n\\n\ Record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-HQF |
3-Error |
[chars] error detected: [chars] [chars] 0x[hec] 0x[hec] |
A software programming error for the HQF ESF Network Processor Client\n\ Mapper was detected. |
c7600-sip-400-clnt |
"This software programming error is not considered fatal to the\n\ operation of the ESF Network Processors. The software is designed to\n\ detect and report the error condition. If the error persists reset\n\ the affected device. \n\ \n\ Record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-INITFAIL |
3-Error |
Initialization Failed - [chars]: [chars] [chars] |
Memory needed to service one or more Network Processors\n\ could not be initialized. |
c7600-sip-400-clnt |
"Try to reload the IOS image on the affected \n\ card or platform.\n\ If the error persists record the output\n\ from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-INTF |
3-Error |
[chars] error detected: [chars] [chars] 0x[hec] 0x[hec] |
A software programming error for the Interface ESF Network Processor\n\ Client Mapper was detected. |
c7600-sip-400-clnt |
"This software programming error is not considered fatal to the\n\ operation of the ESF Network Processors. The software is designed to\n\ detect and report the error condition. If the error persists reset\n\ the affected device. \n\ \n\ Record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-IPSESS |
3-Error |
[chars] error detected: [chars] [chars] 0x[hec] 0x[hec] |
A configuration error for the IP Sessions ESF Network Processor Client\n\ Mapper was detected. |
c7600-sip-400-clnt |
"This configuration error is not considered fatal to the\n\ operation of the ESF Network Processors. The software is designed to\n\ detect and report the error condition. If the error persist reset\n\ the affected device.\n\\n\ Record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-L2SRC |
3-Error |
[chars] error detected: [chars] [chars] 0x[hec] 0x[hec] |
A configuration error for the L2SRC ESF Network Processor\n\ Client Mapper was detected. |
c7600-sip-400-clnt |
"This configuration error is not considered fatal to the\n\ operation of the ESF Network Processors. The software is designed to\n\ detect and report the error condition.\n\ \n\ If the error persist record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-L2TPV3 |
3-Error |
[chars] error detected: [chars] [chars] 0x[hec] 0x[hec] |
A software programming error for the L2TPV3 ESF Network Processor Client\n\ Mapper was detected. |
c7600-sip-400-clnt |
"This software programming error is not considered fatal to the\n\ operation of the ESF Network Processors. The software is designed to\n\ detect and report the error condition. If the error persists reset\n\ the affected device.\n\\n\ Record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-LOCK_BLOCK |
3-Error |
[chars] error detected - 0x[hec] [dec] [dec] [dec] |
Error detected processing ESF Network Processor lock bit\n\ allocations. |
c7600-sip-400-clnt |
"This is a software programming error. Record the \n\ Output from the following show commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-LOCK_LIST |
3-Error |
[chars] error detected - 0x[hec] [dec] [dec] [dec] |
Error detected processing ESF Network Processor lock bit list\n\ allocations. |
c7600-sip-400-clnt |
"This is a software programming error. Record the \n\ Output from the following show commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-MAXEXCEED |
3-Error |
ESF NP Mapper Max Services Exceeded - [chars]: [chars] [dec] |
The maximum number ESF Network Processor Client Mapper services have\n\ been exceeded. |
c7600-sip-400-clnt |
"Change the configuration to reduce the number of services configured.\n\ \n\ If the error persists record the output\n\ from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-MPLSOGRE |
3-Error |
[chars] error detected: [chars] [chars] 0x[hec] 0x[hec] |
A software programming error for the MPLSOGRE ESF Network Processor\n\ Client Mapper was detected. |
c7600-sip-400-clnt |
"This software programming error is not considered fatal to the\n\ operation of the ESF Network Processors. The software is designed to\n\ detect and report the error condition. If the error persists reset\n\ the affected device.\n\ \n\ Record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-MPLSOMGRE |
3-Error |
[chars] error detected: [chars] [chars] 0x[hec] 0x[hec] |
A software programming error for the MPLSOGRE ESF Network Processor\n\ Client Mapper was detected. |
c7600-sip-400-clnt |
"This software programming error is not considered fatal to the\n\ operation of the ESF Network Processors. The software is designed to\n\ detect and report the error condition. If the error persists reset\n\ the affected device.\n\ \n\ Record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-NOMEM |
3-Error |
Memory Allocation Failure - [chars] : [chars]0x[hec] |
Memory required to service one or more Network Processors\n\ could not be allocated. |
c7600-sip-400-clnt |
"This error may indicate that more memory \n\ must be installed on the affected card \n\ or platform in order to service all the\n\ features and related entities enabled via \n\ the configuration.\n\ \n\ Try to reload the IOS image on the affected \n\ card or platform.\n\ If the error persists record the output\n\ from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-NOMEM_S |
3-Error |
Memory Allocation Failure - [chars]: [chars] [chars] |
Memory required to service one or more Network Processors could not\n\ be allocated. |
c7600-sip-400-clnt |
"This error may indicate that more memory \n\ must be installed on the affected card \n\ or platform in order to service all the\n\ features and related entities enabled via \n\ the configuration.\n\ \n\ Try to reload the IOS image on the affected \n\ card or platform.\n\ If the error persists record the output\n\ from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-NOTFOUND |
3-Error |
ESF NP Client Mapper - [chars]: [chars] 0x[hec] |
The ESF Network Processor Client Mapper could not locate a required \n\ software element. |
c7600-sip-400-clnt |
"Try to reload the IOS image on the affected \n\ card or platform.\n\\n\ If the error persists record the output\n\ from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-NPMEM |
3-Error |
[chars] [chars] error detected |
Error detected with external memory of a ESF Network Processor. |
c7600-sip-400-clnt |
"This is a software programming error. Record the \n\ Output from the following show commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-NPUNKNOWN |
3-Error |
Unsupported NP - [chars]: [chars] [chars] |
An unsupported Network Processor has been detected. |
c7600-sip-400-clnt |
"Verify that the correct IOS image is loaded on the affected \n\ card or platform for the configured features.\n\ If the error persists record the output\n\ from the following commands:\n\\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-PPPOESESS |
3-Error |
[chars] error detected: [chars] [chars] 0x[hec] 0x[hec] |
A configuration error for the PPPOE Sessions ESF Network Processor\n\ Client Mapper was detected. |
c7600-sip-400-clnt |
"This configuration error is not considered fatal to the\n\ operation of the ESF Network Processors. The software is designed to\n\ detect and report the error condition.\n\ \n\ If the error persist record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-QOS |
3-Error |
[chars] error detected: [chars] [chars] 0x[hec] 0x[hec] |
A software programming error for the QOS ESF Network Processor Client\n\ Mapper was detected. |
c7600-sip-400-clnt |
"This software programming error is not considered fatal to the\n\ operation of the ESF Network Processors. The software is designed to\n\ detect and report the error condition. If the error persists reset\n\ the affected device.\n\ \n\ Record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-QOS_CONFIG |
3-Error |
[chars] error detected: [chars] [chars] 0x[hec] 0x[hec] |
A configuration error for the QOS ESF Network Processor Client\n\ Mapper was detected. |
c7600-sip-400-clnt |
"This configuration error is not considered fatal to the\n\ operation of the ESF Network Processors. The software is designed to\n\ detect and report the error condition. Change the configuration to \n\ correct the QOS ACL configuration problem.\n\ \n\ If the error persist record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-SACL |
3-Error |
[chars] error detected: [chars] [chars] 0x[hec] 0x[hec] |
A software programming error for the Security ACL ESF Network\n\ Processor Client Mapper was detected. |
c7600-sip-400-clnt |
"This software programming error is not considered fatal to the\n\ operation of the ESF Network Processors. The software is designed to\n\ detect and report the error condition. If the error persists reset\n\ the affected device.\n\ \n\ Record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-SACL_CONFIG |
3-Error |
[chars] error detected: [chars] [chars] 0x[hec] 0x[hec] |
A configuration error for the Security ACL ESF Network Processor Client\n\ Mapper was detected. |
c7600-sip-400-clnt |
"This configuration error is not considered fatal to the\n\ operation of the ESF Network Processors. The software is designed to\n\ detect and report the error condition. Change the configuration to \n\ correct the QOS ACL configuration problem.\n\ \n\ If the error persist record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-STATS_BLOCK |
3-Error |
[chars] error detected - 0x[hec] 0x[hec] [dec] [dec] [dec] |
Error detected processing ESF Network Processor stats block\n\ allocations. |
c7600-sip-400-clnt |
"This is a software programming error. Record the \n\ Output from the following show commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-TCAM |
3-Error |
[chars] error detected: [chars] [chars] 0x[hec] 0x[hec] |
A software programming error for the NetLogic NSE TCAM was detected. |
c7600-sip-400-clnt |
"This software programming error is not considered fatal to the\n\ operation of the ESF Network Processors. The software is designed to\n\ detect and report the error condition. If the error persists reset\n\ the affected device.\n\ \n\ Record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-VPLS |
3-Error |
Error detected: [chars] [chars] 0x[hec] 0x[hec] |
A software programming error for the VPLS ESF Network Processor Client\n\ Mapper was detected. |
c7600-sip-400-clnt |
"This software programming error is not considered fatal to the\n\ operation of the ESF Network Processors. The software is designed to\n\ detect and report the error condition. If the error persists reset\n\ the affected device.\n\\n\ Record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-3-WRED |
3-Error |
[chars] error detected: [chars] [chars] 0x[hec] 0x[hec] |
A software programming error for the WRED ESF Network Processor Client\n\ Mapper was detected. |
c7600-sip-400-clnt |
"This software programming error is not considered fatal to the\n\ operation of the ESF Network Processors. The software is designed to\n\ detect and report the error condition. If the error persists reset\n\ the affected device.\n\ \n\ Record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-4-CONNECTION_EXCEED |
4-Warning |
The number of connections has reached the capacity of the line card [dec]. |
- |
- |
- |
|
IXP_MAP-4-IPC_FAIL |
4-Warning |
ESF IPC Command failed - [chars] NP=[chars] cmd=[dec] me=[dec] rc=[dec] |
An IPC command sent to the ESF Network Processor failed. |
c7600-sip-400-clnt |
"This error indicates a possible problem with the\n\ Network Processor hardware or microcode. Reload\n\ the affected HW to clear the condition.\n\ \n\ If the error persists record the output\n\ from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-4-QUEUE_LIMIT_EXCEED |
4-Warning |
Warning: Line card default queue-limit exceeds the maximum transmit packet buffers [dec]. To ensure high priority traffic is |
An error for the HQF ESF Network Processor Client\n\ Mapper was detected. The total of the default queue-limits\n\ exceeds the maximum transmit packet buffers for this line card.\n\ Under high traffic conditions the line card may run out of \n\ packet buffers and drop high priority traffic. |
c7600-sip-400-clnt |
"This configuration error is not considered fatal to the\n\ operation of the ESF Network Processors. The software is designed to\n\ detect and report the error condition. Apply the QOS policy\n\ configuration in the output direction of each interface.\n\ Adjust the queue-limit so that the total of the queue-limits\n\ on this line card is less than the maximum transmit packet buffers.\n\ \n\ <Bullet><par>policy-map qlimit\n\ <Bullet><par>class class-default\n\ <Bullet><par> queue-limit 100000\n\\n\ <Bullet><par>interface Gig1/0/0\n\ <Bullet><par> service-policy output qlimit\n\\n\ If the error persist record the output from the following commands:\n\\n\ <Bullet><par><Bold>show policy-map interface <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
IXP_MAP-4-STUCK |
4-Warning |
Client ID0x[hec] 0x%08X not ready on [chars] |
During reset of the ESF Network Processor one or more Network\n\ Processor Clients had not completed stop processing. |
c7600-sip-400-clnt |
"The system should still operate normally however statistics\n\ or state collected before the ESF Network Processor was reset\n\ may have been lost.\n\\n\ If the error persists record the output\n\ from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
KA_NOMEMORY-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
KERBEROS-3-FORKFAIL |
3-Error |
Failed to fork process for [chars]. |
Quite likely we ran out of memory. Other explanations are possible. |
aaa |
"If this message recurs call your technical support " "representative for assistance." |
|
KEYMAN-4-KEYSTR_BAD_CRYPTO |
4-Warning |
Bad encrypted keystring for key id [dec]. |
The system could not successfully decrypt an encrypted keystring. The keystring may have been corrupted during system configuration. |
- |
"Re-enter the key-string command and reconfigure the key string." |
|
KEYMAN-4-KEYSTR_CRYPTO_TYPE |
4-Warning |
Type [dec] encryption unknown. Interpreting keystring as literal |
The format type was not recognized by the system. A keystring format type value of 0 unencrypted keystring or 7 hidden keystring |
- |
"Use the correct format for the value type or remove the space following " "the value type" |
|
KEYSTORE_AE46C1-3-SELF_TEST_FAILURE |
3-Error |
Keystore power on self test failure. [chars] |
keystore pass power on self test failure for SHA1 or HMAC-SHA1. The chips is not usable in this state. |
- |
"Report this error to your Cisco technical support representative " "and arrange to have the hardware keystore on the supervisor " "card replaced." |
|
KEYSTORE_AE46C1-3-SELF_TEST_FAILURE |
3-Error |
Keystore power on self test failure. [chars] |
keystore pass power on self test failure for SHA1 or HMAC-SHA1. The chips is not usable in this state. |
- |
"Report this error to your Cisco technical support representative " "and arrange to have the hardware keystore on the supervisor " "card replaced." |
|
KEYSTORE_AE46C1-3-SELF_TEST_FAILURE |
3-Error |
Keystore power on self test failure. [chars] |
keystore pass power on self test failure for SHA1 or HMAC-SHA1. The chips is not usable in this state. |
- |
"Report this error to your Cisco technical support representative " "and arrange to have the hardware keystore on the supervisor " "card replaced." |
|
KEYSTORE_AE46C1-6-RANDOM |
6-Information |
A pseudo-random number was generated twice in succession[dec]. |
A pseudo-random number generator produced the same number twice\n\ in succession. |
- |
"Under normal circumstances a pseudo-random number generator will\n\ occasionally produce the same number twice in succession and this\n\ is not a problem. However if this message occurs frequently the \n\ system should be manually reloaded. If the message is persistent \n\ across reloads copy the error message exactly as it appears and \n\ report it to your technical support representative." |
|
KEYSTORE_AE46C1-6-RANDOM |
6-Information |
A pseudo-random number was generated twice in succession[dec]. |
A pseudo-random number generator produced the same number twice\n\ in succession. |
- |
"Under normal circumstances a pseudo-random number generator will\n\ occasionally produce the same number twice in succession and this\n\ is not a problem. However if this message occurs frequently the \n\ system should be manually reloaded. If the message is persistent \n\ across reloads copy the error message exactly as it appears and \n\ report it to your technical support representative." |
|
KEYSTORE_AE46C1-6-RANDOM |
6-Information |
A pseudo-random number was generated twice in succession[dec]. |
A pseudo-random number generator produced the same number twice\n\ in succession. |
- |
"Under normal circumstances a pseudo-random number generator will\n\ occasionally produce the same number twice in succession and this\n\ is not a problem. However if this message occurs frequently the \n\ system should be manually reloaded. If the message is persistent \n\ across reloads copy the error message exactly as it appears and \n\ report it to your technical support representative." |
|
KEYSTORE_AE46C1-6-SELF_TEST_PASS |
6-Information |
Keystore pass power on self test |
keystore pass power on self test for both SHA1 and HMAC-SHA1 |
- |
- |
|
KEYSTORE_AE46C1-6-SELF_TEST_PASS |
6-Information |
Keystore pass power on self test |
keystore pass power on self test for both SHA1 and HMAC-SHA1 |
- |
- |
|
KEYSTORE_AE46C1-6-SELF_TEST_PASS |
6-Information |
Keystore pass power on self test |
keystore pass power on self test for both SHA1 and HMAC-SHA1 |
- |
- |
|
KEYSTORE-3-BAD_MAGIC |
3-Error |
Bad magic number 0x%08x in software keystore file \[chars]\. |
Keystore data file appears to have been corrupted. Keys can not be retrieved from persistent memory. |
- |
- |
|
KEYSTORE-3-BAD_MAGIC |
3-Error |
Bad magic number 0x%08x in software keystore file \[chars]\. |
Keystore data file appears to have been corrupted. Keys can not be retrieved from persistent memory. |
- |
- |
|
KEYSTORE-3-BAD_MAGIC |
3-Error |
Bad magic number 0x%08x in software keystore file \[chars]\. |
Keystore data file appears to have been corrupted. Keys can not be retrieved from persistent memory. |
- |
- |
|
KEYSTORE-3-BAD_MAGIC |
3-Error |
Bad magic number 0x%08x in software keystore file \[chars]\. |
Keystore data file appears to have been corrupted. Keys can not be retrieved from persistent memory. |
- |
- |
|
KEYSTORE-3-BAD_MAGIC |
3-Error |
Bad magic number 0x%08x in software keystore file \[chars]\. |
Keystore data file appears to have been corrupted. Keys can not be retrieved from persistent memory. |
- |
- |
|
KEYSTORE-3-IFS_OPEN_R |
3-Error |
Failed to open file \[chars]\ for reading software keystore. [chars] |
An error occurred while opening the keystore file for reading. CTS keys could not be retrieved. |
- |
- |
|
KEYSTORE-3-IFS_OPEN_R |
3-Error |
Failed to open file \[chars]\ for reading software keystore. [chars] |
An error occurred while opening the keystore file for reading. CTS keys could not be retrieved. |
- |
- |
|
KEYSTORE-3-IFS_OPEN_R |
3-Error |
Failed to open file \[chars]\ for reading software keystore. [chars] |
An error occurred while opening the keystore file for reading. CTS keys could not be retrieved. |
- |
- |
|
KEYSTORE-3-IFS_OPEN_R |
3-Error |
Failed to open file \[chars]\ for reading software keystore. [chars] |
An error occurred while opening the keystore file for reading. CTS keys could not be retrieved. |
- |
- |
|
KEYSTORE-3-IFS_OPEN_R |
3-Error |
Failed to open file \[chars]\ for reading software keystore. [chars] |
An error occurred while opening the keystore file for reading. CTS keys could not be retrieved. |
- |
- |
|
KEYSTORE-3-IFS_OPEN_W |
3-Error |
Failed to open file \[chars]\ for writing software keystore. [chars] |
An error occurred while opening a file for persistent storage. CTS keys could not be saved to persistent storage. |
- |
- |
|
KEYSTORE-3-IFS_OPEN_W |
3-Error |
Failed to open file \[chars]\ for writing software keystore. [chars] |
An error occurred while opening a file for persistent storage. CTS keys could not be saved to persistent storage. |
- |
- |
|
KEYSTORE-3-IFS_OPEN_W |
3-Error |
Failed to open file \[chars]\ for writing software keystore. [chars] |
An error occurred while opening a file for persistent storage. CTS keys could not be saved to persistent storage. |
- |
- |
|
KEYSTORE-3-IFS_OPEN_W |
3-Error |
Failed to open file \[chars]\ for writing software keystore. [chars] |
An error occurred while opening a file for persistent storage. CTS keys could not be saved to persistent storage. |
- |
- |
|
KEYSTORE-3-IFS_OPEN_W |
3-Error |
Failed to open file \[chars]\ for writing software keystore. [chars] |
An error occurred while opening a file for persistent storage. CTS keys could not be saved to persistent storage. |
- |
- |
|
KEYSTORE-3-IFS_READ |
3-Error |
An error [chars] occurred while reading from the software |
CTS keys could not be retrieved from persistent storage. |
- |
- |
|
KEYSTORE-3-IFS_READ |
3-Error |
An error [chars] occurred while reading from the software |
CTS keys could not be retrieved from persistent storage. |
- |
- |
|
KEYSTORE-3-IFS_READ |
3-Error |
An error [chars] occurred while reading from the software |
CTS keys could not be retrieved from persistent storage. |
- |
- |
|
KEYSTORE-3-IFS_READ |
3-Error |
An error [chars] occurred while reading from the software |
CTS keys could not be retrieved from persistent storage. |
- |
- |
|
KEYSTORE-3-IFS_READ |
3-Error |
An error [chars] occurred while reading from the software |
CTS keys could not be retrieved from persistent storage. |
- |
- |
|
KEYSTORE-3-IFS_WRITE |
3-Error |
An error occurred while writing to the software keystore file. |
CTS keys could not be saved to persistent storage. |
- |
- |
|
KEYSTORE-3-IFS_WRITE |
3-Error |
An error occurred while writing to the software keystore file. |
CTS keys could not be saved to persistent storage. |
- |
- |
|
KEYSTORE-3-IFS_WRITE |
3-Error |
An error occurred while writing to the software keystore file. |
CTS keys could not be saved to persistent storage. |
- |
- |
|
KEYSTORE-3-IFS_WRITE |
3-Error |
An error occurred while writing to the software keystore file. |
CTS keys could not be saved to persistent storage. |
- |
- |
|
KEYSTORE-3-IFS_WRITE |
3-Error |
An error occurred while writing to the software keystore file. |
CTS keys could not be saved to persistent storage. |
- |
- |
|
KEYSTORE-3-IPC_NO_PROC |
3-Error |
Could not create a process to receive keystore redundancy messages. |
An error was encountered when trying to create a process to handle incoming keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPC_NO_PROC |
3-Error |
Could not create a process to receive keystore redundancy messages. |
An error was encountered when trying to create a process to handle incoming keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPC_NO_PROC |
3-Error |
Could not create a process to receive keystore redundancy messages. |
An error was encountered when trying to create a process to handle incoming keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPC_NO_PROC |
3-Error |
Could not create a process to receive keystore redundancy messages. |
An error was encountered when trying to create a process to handle incoming keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPC_NO_PROC |
3-Error |
Could not create a process to receive keystore redundancy messages. |
An error was encountered when trying to create a process to handle incoming keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPCNOCONN |
3-Error |
No IPC communication path to peer available for keystore [chars]. |
No IPC connection to the peer was available for keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPCNOCONN |
3-Error |
No IPC communication path to peer available for keystore [chars]. |
No IPC connection to the peer was available for keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPCNOCONN |
3-Error |
No IPC communication path to peer available for keystore [chars]. |
No IPC connection to the peer was available for keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPCNOCONN |
3-Error |
No IPC communication path to peer available for keystore [chars]. |
No IPC connection to the peer was available for keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPCNOCONN |
3-Error |
No IPC communication path to peer available for keystore [chars]. |
No IPC connection to the peer was available for keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPCOPEN |
3-Error |
Failed to open IPC port to peer for keystore redundancy: [chars] |
An error was encountered when trying to open an IPC port for keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPCOPEN |
3-Error |
Failed to open IPC port to peer for keystore redundancy: [chars] |
An error was encountered when trying to open an IPC port for keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPCOPEN |
3-Error |
Failed to open IPC port to peer for keystore redundancy: [chars] |
An error was encountered when trying to open an IPC port for keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPCOPEN |
3-Error |
Failed to open IPC port to peer for keystore redundancy: [chars] |
An error was encountered when trying to open an IPC port for keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPCOPEN |
3-Error |
Failed to open IPC port to peer for keystore redundancy: [chars] |
An error was encountered when trying to open an IPC port for keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPCPORT |
3-Error |
Failed to create IPC port [chars] for keystore redundancy. [chars]. |
An error was encountered when trying to create an IPC port. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPCPORT |
3-Error |
Failed to create IPC port [chars] for keystore redundancy. [chars]. |
An error was encountered when trying to create an IPC port. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPCPORT |
3-Error |
Failed to create IPC port [chars] for keystore redundancy. [chars]. |
An error was encountered when trying to create an IPC port. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPCPORT |
3-Error |
Failed to create IPC port [chars] for keystore redundancy. [chars]. |
An error was encountered when trying to create an IPC port. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPCPORT |
3-Error |
Failed to create IPC port [chars] for keystore redundancy. [chars]. |
An error was encountered when trying to create an IPC port. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPCSEND |
3-Error |
IPC send error [chars] while sending [chars]. |
An error occurred while sending an IPC message to the peer during a keystore redundancy operation. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPCSEND |
3-Error |
IPC send error [chars] while sending [chars]. |
An error occurred while sending an IPC message to the peer during a keystore redundancy operation. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPCSEND |
3-Error |
IPC send error [chars] while sending [chars]. |
An error occurred while sending an IPC message to the peer during a keystore redundancy operation. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPCSEND |
3-Error |
IPC send error [chars] while sending [chars]. |
An error occurred while sending an IPC message to the peer during a keystore redundancy operation. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-IPCSEND |
3-Error |
IPC send error [chars] while sending [chars]. |
An error occurred while sending an IPC message to the peer during a keystore redundancy operation. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
- |
- |
|
KEYSTORE-3-ISSU_INCOMPAT |
3-Error |
Standby incompatible for SSO. |
The image on the standby failed ISSU message version negotiation. As a result we will not be able to sync keystore updates to it and so it is disallowed from reaching \hot\ standby status in SSO mode. |
- |
- |
|
KEYSTORE-3-ISSU_INCOMPAT |
3-Error |
Standby incompatible for SSO. |
The image on the standby failed ISSU message version negotiation. As a result we will not be able to sync keystore updates to it and so it is disallowed from reaching \hot\ standby status in SSO mode. |
- |
- |
|
KEYSTORE-3-ISSU_INCOMPAT |
3-Error |
Standby incompatible for SSO. |
The image on the standby failed ISSU message version negotiation. As a result we will not be able to sync keystore updates to it and so it is disallowed from reaching \hot\ standby status in SSO mode. |
- |
- |
|
KEYSTORE-3-ISSU_INCOMPAT |
3-Error |
Standby incompatible for SSO. |
The image on the standby failed ISSU message version negotiation. As a result we will not be able to sync keystore updates to it and so it is disallowed from reaching \hot\ standby status in SSO mode. |
- |
- |
|
KEYSTORE-3-ISSU_INCOMPAT |
3-Error |
Standby incompatible for SSO. |
The image on the standby failed ISSU message version negotiation. As a result we will not be able to sync keystore updates to it and so it is disallowed from reaching \hot\ standby status in SSO mode. |
- |
- |
|
KEYSTORE-3-NO_KEYSTORE |
3-Error |
CTS hardware keystore is not responsive and software emulation is not enabled. |
The CTS hardware keystore on the switch has failed and needs to be inspected.\n Since CTS credentials are stored in the keystore this means that CTS authentication and authorization operations will fail. \n The following action is recommended: If the defect is shown on the Active Supervisor try to switchover to Standby Supervisor. If the defect is shown on Standby Supervisor try to reset the Standby. If the defect persists there may be damage to the hardware keystore chip please take appropriate action. In the meantime you can configure the switch to use software keystore emulation. After you have enabled software keystore emulation please re-configure CTS credentials to populate the software keystore. |
- |
- |
|
KEYSTORE-3-NO_KEYSTORE |
3-Error |
CTS hardware keystore is not responsive and software emulation is not enabled. |
The CTS hardware keystore on the switch has failed and needs to be inspected.\n Since CTS credentials are stored in the keystore this means that CTS authentication and authorization operations will fail. \n The following action is recommended: If the defect is shown on the Active Supervisor try to switchover to Standby Supervisor. If the defect is shown on Standby Supervisor try to reset the Standby. If the defect persists there may be damage to the hardware keystore chip please take appropriate action. In the meantime you can configure the switch to use software keystore emulation. After you have enabled software keystore emulation please re-configure CTS credentials to populate the software keystore. |
- |
- |
|
KEYSTORE-3-NO_KEYSTORE |
3-Error |
CTS hardware keystore is not responsive and software emulation is not enabled. |
The CTS hardware keystore on the switch has failed and needs to be inspected.\n Since CTS credentials are stored in the keystore this means that CTS authentication and authorization operations will fail. \n The following action is recommended: If the defect is shown on the Active Supervisor try to switchover to Standby Supervisor. If the defect is shown on Standby Supervisor try to reset the Standby. If the defect persists there may be damage to the hardware keystore chip please take appropriate action. In the meantime you can configure the switch to use software keystore emulation. After you have enabled software keystore emulation please re-configure CTS credentials to populate the software keystore. |
- |
- |
|
KEYSTORE-3-NO_KEYSTORE |
3-Error |
CTS hardware keystore is not responsive and software emulation is not enabled. |
The CTS hardware keystore on the switch has failed and needs to be inspected.\n Since CTS credentials are stored in the keystore this means that CTS authentication and authorization operations will fail. \n The following action is recommended: If the defect is shown on the Active Supervisor try to switchover to Standby Supervisor. If the defect is shown on Standby Supervisor try to reset the Standby. If the defect persists there may be damage to the hardware keystore chip please take appropriate action. In the meantime you can configure the switch to use software keystore emulation. After you have enabled software keystore emulation please re-configure CTS credentials to populate the software keystore. |
- |
- |
|
KEYSTORE-3-NO_KEYSTORE |
3-Error |
CTS hardware keystore is not responsive and software emulation is not enabled. |
The CTS hardware keystore on the switch has failed and needs to be inspected.\n Since CTS credentials are stored in the keystore this means that CTS authentication and authorization operations will fail. \n The following action is recommended: If the defect is shown on the Active Supervisor try to switchover to Standby Supervisor. If the defect is shown on Standby Supervisor try to reset the Standby. If the defect persists there may be damage to the hardware keystore chip please take appropriate action. In the meantime you can configure the switch to use software keystore emulation. After you have enabled software keystore emulation please re-configure CTS credentials to populate the software keystore. |
- |
- |
|
KEYSTORE-3-SESSION |
3-Error |
KeyStore ISSU client [chars] |
KeyStore ISSU client observed an error during a session negotiation with the peer unit. When there is a problem with the session the standby unit can not be brought up. |
- |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
KEYSTORE-3-UNEXPECTED_EOF |
3-Error |
Unexpected end of file while reading software keystore \[chars]\. |
Keystore data file appears to have been truncated. One or more keys can not be retrieved from persistent memory. |
- |
- |
|
KEYSTORE-3-UNEXPECTED_EOF |
3-Error |
Unexpected end of file while reading software keystore \[chars]\. |
Keystore data file appears to have been truncated. One or more keys can not be retrieved from persistent memory. |
- |
- |
|
KEYSTORE-3-UNEXPECTED_EOF |
3-Error |
Unexpected end of file while reading software keystore \[chars]\. |
Keystore data file appears to have been truncated. One or more keys can not be retrieved from persistent memory. |
- |
- |
|
KEYSTORE-3-UNEXPECTED_EOF |
3-Error |
Unexpected end of file while reading software keystore \[chars]\. |
Keystore data file appears to have been truncated. One or more keys can not be retrieved from persistent memory. |
- |
- |
|
KEYSTORE-3-UNEXPECTED_EOF |
3-Error |
Unexpected end of file while reading software keystore \[chars]\. |
Keystore data file appears to have been truncated. One or more keys can not be retrieved from persistent memory. |
- |
- |
|
KINEPAK-3-CONTIGUOUS |
3-Error |
Contiguous packet sent for transmit |
A software error occurred resulting in an unexpected packet being\n\ set up for transmission and the packet was dropped. |
- |
LOG_STD_RECUR_ACTION |
|
KINEPAK-3-ERR_DSPWARE_DNLD |
3-Error |
dsp[dec] cannot download dspware [chars] |
A software error occurred resulting in failure to download a \n\ dspware component. |
- |
LOG_STD_ACTION |
|
KINEPAK-3-ERR_DSPWARE_IMG |
3-Error |
Cannot find dspware [chars] component |
A software error occurred resulting in failure to download a \n\ dspware component. |
- |
LOG_STD_ACTION |
|
KINEPAK-3-NODSPENTRY |
3-Error |
No dsp entry in dsp list |
The software structure that is used to maintain the DSP \n\ instance is missing. |
- |
LOG_STD_RECUR_ACTION |
|
KINEPAK-3-NOMAILELEMENTS |
3-Error |
Cannot create message buffer |
A software error occurred resulting in failure to create a \n\ message buffer to send messages among processes. |
- |
LOG_STD_ACTION |
|
KINEPAK-3-NOPARTICLE |
3-Error |
No particle available for ingress packet |
A software error occurred resulting in failure to obtain a \n\ particle to hold an ingress packet from DSP. |
- |
LOG_STD_RECUR_ACTION |
|
KINEPAK-3-NOPARTICLEPOOL |
3-Error |
Cannot create particle pool |
A software error occurred resulting in failure to create a \n\ particle pool to receive packets from DSP. |
- |
LOG_STD_ACTION |
|
KINEPAK-3-NORXPAK |
3-Error |
Static receive paktype unavailable |
A software structure was found in an unexpected state during\n\ run-time for the indicated DSP. |
- |
LOG_STD_ACTION |
|
L2BD_PROXY-2-PROXY_IPC_INIT_FAILED |
2-Critical |
QFP L2BD Proxy IPC interface initialization failure result: [dec]. |
Cisco internal software error. QFP L2BD Proxy initialization detected that the IPC interface initialization failed. QFP L2BD proxy will not be functional while this condition exists. |
qfp-l2bd keyword:l2bd |
LOG_STD_ACTION |
|
L2BD_PROXY-3-L2BD_MEM_EXTEND_FAILED |
3-Error |
L2BD IPC subtype: [dec] |
Extending memory failed. |
qfp-l2bd keyword:l2bd |
LOG_STD_ACTION |
|
L2BD_PROXY-3-L2BD_MEM_REQ_FAILED |
3-Error |
L2BD IPC subtype: [dec] |
Requesting more memory failed. |
qfp-l2bd keyword:l2bd |
LOG_STD_ACTION |
|
L2BD_PROXY-3-PROXY_BAD_MSG |
3-Error |
QFP L2BD Proxy received bad length message type [dec] |
Cisco internal software error. QFP L2BD Proxy received a corrupted message from control plane. This message will be ignored. |
qfp-l2bd keyword:l2bd |
LOG_STD_ACTION |
|
L2BD_PROXY-3-PROXY_IPC_ALLOC_FAILED |
3-Error |
QFP L2BD Proxy [chars] message lost due to message buffer allocation failure. |
Cisco internal software error. QFP L2BD Proxy message processing detected a message buffer allocation failure. The message is lost as the result of this condition. |
qfp-l2bd keyword:l2bd |
LOG_STD_ACTION |
|
L2BD_PROXY-3-PROXY_IPC_SEND_FAILED |
3-Error |
QFP L2BD Proxy [chars] message lost due to message sent failure result: [dec]. |
Cisco internal software error. QFP L2BD Proxy message processing detected a message sent failure. The message is lost as the result of this condition. |
qfp-l2bd keyword:l2bd |
LOG_STD_ACTION |
|
L2BD_PROXY-4-PROXY_INVALID_MSG |
4-Warning |
QFP L2BD Proxy received invalid message type [dec] |
Cisco internal software error. QFP L2BD Proxy received an invalid message from control plane. This message will be ignored. |
qfp-l2bd keyword:l2bd |
LOG_STD_ACTION |
|
L2BD_PROXY-4-PROXY_INVALID_MSG_LEN |
4-Warning |
QFP L2BD Proxy IPC invalid length [dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Cisco internal software error. QFP L2BD Proxy received invalid IPC message length from control plane. This message will be ignored. |
qfp-l2bd keyword:l2bd |
LOG_STD_ACTION |
|
L2CAC-5-VC_BW_NOT_ENOUGH |
5-Notice |
VC [dec]/[dec] bandwidth is not enough to add this Trunk portchannel. Total bandwidth is [dec] cps but requires [dec] cps to add this Trunk portchanel |
VC bandwidth is not enough Need to increase the bandwidth . |
- |
"To support this call VC bandwidh the sustained cell rate has to be increased to accomidate the new calls." |
|
L2CTRL-3-ADD_REGISTRY_FAILED |
3-Error |
Subsystem [chars] fails to add callback function [chars] |
Other subsystem must have mistakenly add its own callback functions. This syslog is for debugging purpose. |
l2ctrl |
LOG_STD_NO_ACTION |
|
L2FIB-3-BAD_PARAM |
3-Error |
[chars] |
Invalid parameter |
l2fib |
LOG_STD_ACTION |
|
L2FIB-3-EVPN_ERROR |
3-Error |
[chars] |
EVPN encap error |
l2fib |
LOG_STD_ACTION |
|
L2FIB-3-IMET_ENCAP_MISMATCH |
3-Error |
IMET Encapsulation Mismatch on bridge domain [dec] from [chars] |
- |
- |
- |
|
L2FIB-3-IMET_REPTYPE_MISMATCH |
3-Error |
IMET Replication Mismatch on bridge domain [dec] from [chars] Local is Static |
- |
l2fib |
LOG_STD_ACTION |
|
L2FIB-3-MAC_ENCAP_MISMATCH |
3-Error |
MAC [chars] Encapsulation Mismatch on bridge domain [dec] from [chars] |
Incompatible Encapsulation Type in MAC/IP Route RT-2 received from remote peer |
l2fib |
LOG_STD_ACTION |
|
L2FIB-3-MAC_ERROR |
3-Error |
MAC address [chars] is reserved for [chars] output list bit is produced by [chars] on bridge domain [dec] |
- |
l2fib |
LOG_STD_ACTION |
|
L2MC_QUERIER-4-NO_IP_ADDR_CFG |
4-Warning |
The [chars] querier cannot send out General Query messages in VLAN [dec] because there is no IP address configured on the system. |
The allocation of explicit-tracking entries is bounded to avoid\n\ the IGMP/MLD snooping hogs the system resources |
igmp/mld snooping |
"Disable and re-enable L2 multicast snooping on the VLAN." |
|
L2MC_QUERIER-4-NO_IP_ADDR_CFG |
4-Warning |
The [chars] querier cannot send out General Query messages in VLAN [dec] because there is no IP address configured on the system. |
An IP address should be specified for the IGMP/MLD querier either at the global or per VLAN level. |
l2mcast |
"Configure a source IP address for the IGMP/MLD querier. " |
|
L2MC_QUERIER-4-PIM_ENABLED |
4-Warning |
The [chars] querier is operationally disabled in VLAN [dec] because PIM has been enabled on the SVI. |
PIM has been detected on the SVI. The IGMP/MLD querier function should not be operationally enabled when PIM is enabled on the SVI. |
l2mcast |
"Ensure that PIM is disabled on the SVI. " |
|
L2MC_QUERIER-4-PIM_ENABLED |
4-Warning |
The [chars] querier is operationally disabled in VLAN [dec] because PIM has been enabled on the SVI. |
PIM has been detected on the SVI. The IGMP/MLD querier function should not be operationally enabled when PIM is enabled on the SVI. |
l2mcast |
"Ensure that PIM is disabled on the SVI. " |
|
L2MC_QUERIER-4-SAME_SRC_IP_ADDR |
4-Warning |
An [chars] General Query packet with the same source IP address [chars] |
The querier has received an IGMP/MLD General Query message with a source IP address identical to that configured for the IGMP/MLD querier itself. This is considered a network configuration error. |
l2mcast |
"Check IGMP/MLD querier source IP address configuration on the router " "or switch connected via the port identified." "Ensure unique source IP addresses are configured on each system. " |
|
L2MC_QUERIER-4-SNOOPING_DISABLED |
4-Warning |
The [chars] querier is operationally disabled in VLAN [dec] because [chars] snooping has been disabled in this VLAN. |
IGMP/MLD snooping has been detected as being disabled on this VLAN. The IGMP/MLD querier function should not be operationally enabled when IGMP/MLD snooping is disabled. |
l2mcast |
"Ensure that IGMP/MLD snooping is enabled globally and on the VLAN " "reported. " |
|
L2MC_QUERIER-4-SNOOPING_DISABLED |
4-Warning |
The [chars] querier is operationally disabled in VLAN [dec] because [chars] snooping has been disabled in this VLAN. |
IGMP/MLD snooping has been detected as being disabled on this VLAN. The IGMP/MLD querier function should not be operationally enabled when IGMP/MLD snooping is disabled. |
l2mcast |
"Ensure that IGMP/MLD snooping is enabled globally and on the VLAN " "reported. " |
|
L2MC_QUERIER-4-ZERO_SRC_IP_ADDR |
4-Warning |
An [chars] General Query packet with source IP address that contained all zeroes is received in VLAN [dec] on port [chars]. |
The IGMP/MLD querier has received an IGMP/MLD General Query message with a source IP address that contained all zeroes. Some IGMP/MLD clients cannot process General Query with source IP address that contained all zeroes. |
l2mcast |
"Check the source IP address of the IGMP/MLD querier that is on the router " "or switch connected to the port specified in the message. " |
|
L2MC_QUERIER-6-PIM_DISABLED |
6-Information |
The [chars] querier is now operationally enabled in VLAN [dec] because PIM is no longer enabled on the SVI. |
PIM has been disabled on the SVI and as a result the IGMP/MLD querier function has now been enabled. |
l2mcast |
"No action is required." |
|
L2MC_QUERIER-6-PIM_DISABLED |
6-Information |
The [chars] querier is now operationally enabled in VLAN [dec] because PIM is no longer enabled on the SVI. |
PIM has been disabled on the SVI and as a result the IGMP/MLD querier function has now been enabled. |
l2mcast |
"No action is required." |
|
L2MC_QUERIER-6-SNOOPING_ENABLED |
6-Information |
The [chars] querier is now operationally enabled in VLAN [dec] because [chars] snooping is no longer disabled. |
IGMP/MLD snooping has now been enabled and as a result the IGMP/MLD querier function has now been enabled. |
l2mcast |
"No action is required." |
|
L2MC_QUERIER-6-SNOOPING_ENABLED |
6-Information |
The [chars] querier is now operationally enabled in VLAN [dec] because [chars] snooping is no longer disabled. |
IGMP/MLD snooping has now been enabled and as a result the IGMP/MLD querier function has now been enabled. |
l2mcast |
"No action is required." |
|
L2MC_QUERIER-6-SWITCHOVER_NOTIFICATION |
6-Information |
The [chars] querier is now operationally enabled in VLAN [dec] because switchover has occured. |
Switchover has occured and the IGMP/MLD querier function has now been enabled. |
l2mcast |
"No action is required." |
|
L2MCAST_WIRELESS_ISSU-2-GET_BUFFER |
2-Critical |
L2mcast Wireless ISSU client failed to get buffer for message. Error: [dec] [chars] |
The L2mcast Wireless 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. |
ewlc-multicast |
"show logging and show checkpoint client" |
|
L2MCAST_WIRELESS_ISSU-2-INIT |
2-Critical |
L2mcast Wireless ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The L2mcast Wireless 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. |
ewlc-multicast |
LOG_STD_ACTION |
|
L2MCAST_WIRELESS_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
L2mcast Wireless ISSU client failed to send negotiation message. Error: [dec] [chars] |
The L2mcast Wireless 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. |
ewlc-multicast |
"show logging and show checkpoint client" |
|
L2MCAST_WIRELESS_ISSU-2-SESSION_NEGO |
2-Critical |
L2mcast Wireless ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The L2mcast Wireless 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. |
ewlc-multicast |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
L2MCAST_WIRELESS_ISSU-2-SESSION_REGISTRY |
2-Critical |
L2mcast Wireless ISSU client failed to register session information. Error: [dec] [chars] |
The L2mcast Wireless ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
ewlc-multicast |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
L2MCAST_WIRELESS_ISSU-3-INVALID_SESSION |
3-Error |
L2mcast Wireless ISSU client does not have a valid registered session. |
The L2mcast Wireless ISSU client does not have a valid registered session. |
ewlc-multicast |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
L2MCAST_WIRELESS_ISSU-3-MSG_NOT_OK |
3-Error |
L2mcast Wireless ISSU client 'Message Type [dec]' is not compatible |
The L2mcast Wireless ISSU client received an incompatible message from the peer device. The message cannot be processed. |
ewlc-multicast |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
L2MCAST_WIRELESS_ISSU-3-MSG_SIZE |
3-Error |
L2mcast Wireless ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The L2mcast Wireless ISSU client failed to calculate the MTU for the specified message. The L2mcast Wireless ISSU client is not able to send the message to the standby device. |
ewlc-multicast |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
L2MCAST_WIRELESS_ISSU-3-SESSION_UNREGISTRY |
3-Error |
L2mcast Wireless ISSU client failed to unregister session information. Error: [dec] [chars] |
The L2mcast Wireless ISSU client failed to unregister session information. |
ewlc-multicast |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
L2MCAST_WIRELESS_ISSU-3-TRANSFORM_FAIL |
3-Error |
L2mcast Wireless ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The L2mcast Wireless 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 L2mcast Wireless state between the active device and the standby device is not identical. |
ewlc-multicast |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
L2TM-3-ACCESS_ERR |
3-Error |
Tcam access failed while [chars] |
Failed to read/write from/to tcam. |
hardware |
LOG_STD_ACTION |
|
L2TM-7-INTERNAL_ERR |
7-Debug |
Internal error: [chars] |
An internal error occured. |
firmware |
LOG_STD_ACTION |
|
L2TP_HA -3-ISSU |
3-Error |
[chars]: [chars] |
A L2TP ISSU error occurred. |
l2tp |
LOG_STD_SH_TECH_ACTION |
|
L2TP_HA -3-SYNC |
3-Error |
[chars]: code [dec] |
An error occurred when syncing L2TP state to the Standby Route Processor. This may affect Non-Stop Forwarding capability on L2TP-based interfaces during and after switchover until the state is recovered through normal protocol operation. |
fr |
"Reset the standby processor to attempt the sync again. " LOG_STD_RECUR_ACTION |
|
L2TP-3-CRITICAL |
3-Error |
[chars] |
An critical event has been processed by the L2TP subsystem. |
L2TP |
LOG_STD_NO_ACTION |
|
L2TP-3-ILLEGAL |
3-Error |
[chars]: [chars] |
An illegal event has been processed by the L2TP subsystem. |
L2TP |
LOG_STD_NO_ACTION |
|
L2TP-5-IGNOREICMPMTU |
5-Notice |
Ignoring received ICMP Type 3 Code 4 due to pmtu min or max setting |
An ICMP Type 3 Code 4 fragmentation needed and DF set packet |
L2TP |
"If you want the ICMP packet to be accepted and used to " "decrease or increase the MTU then use the " "<CmdBold>vpdn pmtu min <NoCmdBold> command to " "decrease the minimum MTU allowed and enter the " "<CmdBold> vpdn pmtu max <NoCmdBold> command to " "increase the maximum MTU that is allowed. The minimum value " "specified is the minimum MTU that is allowed and the " "maximum value specified is the maximum MTU that is " "allowed." |
|
L2TPV3_NP_CLIENT-3-INFO |
3-Error |
[chars] |
L2TPv3 NP Client failed to initialize properly which will result in\n\ improper operation of l2tpv3 feature |
vsp-mid |
"Try to reload the IOS image on the affected card or platform. If the\n\ error persists record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
L2TPV3_NP_CLIENT-3-NOMEM |
3-Error |
[chars] |
L2TPv3 NP Client failed to initialize properly which will result in\n\ improper operation of l2tpv3 feature |
vsp-mid |
"This error may indicate that more memory must be installed on the\n\ affected card or platform in order to service all the features and\n\ related entities enabled via the configuration.\n\\n\ Try to reload the IOS image on the affected card or platform. If the\n\ error persists record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
L2TPV3_NP_CLIENT-4-WARN |
4-Warning |
[chars] [dec] [chars] |
L2TPv3 Entry could not be added because:\n\ 1. Entry passed is invalid. |
vsp-mid |
"Try to reload the IOS image on the affected card or platform. If the\n\ error persists record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
L2TUN-3-ILLEGAL |
3-Error |
[chars] |
An illegal event has been processed by the L2TUN subsystem. |
L2TUN |
LOG_STD_NO_ACTION |
|
L2VPN_GLOBAL_OP-5-XCONNECT |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
L3MM-4-AP_DB_ADD |
4-Warning |
Failed to add AP to DB { AP: [enet] [inet]} |
The L3MM failed to add the entry for the specified AP into the AP database |
cat6000-wireless |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
L3MM-4-AP_DB_DEL |
4-Warning |
Failed to delete AP from DB { AP: [enet] [inet]} |
The L3MM failed to initialize due to the specified reason |
cat6000-wireless |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
L3MM-4-DUP_AP_IPADDR |
4-Warning |
AP [enet] is requesting ip [inet] which is being used by another AP |
The L3MM detected that an access point requested an IP address that is being used by another access point in the network. |
- |
"Change the IP address of one of the two access " "points" |
|
L3MM-4-DUP_IPADDR |
4-Warning |
MN [enet] is requesting ip [inet] which is being used by MN [enet] |
The L3MM detected that a mobile node requested an IP address that is being used by another mobile node in the network. |
- |
"Change the IP address of one of the two mobile " "nodes" |
|
L3MM-4-MALLOC_FAIL |
4-Warning |
Memory allocation failure [chars] |
The L3MM failed to allocate memory which was needed to perform a given operation and/or respond to an event |
- |
"Increase the memory on the RP of the supervisor" |
|
L3MM-4-MN_IPDB_ADD |
4-Warning |
Failed to add MN to MN DB { MN: [enet] [inet]} |
The L3MM failed to add the entry for the specified MN into the MN IP database |
cat6000-wireless |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
L3MM-4-MN_IPDB_DEL |
4-Warning |
Failed to delete MN from IP DB { MN: [enet] [inet]} |
The L3MM failed to delete the entry for the specified MN from the MN IP database |
cat6000-wireless |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
L3MM-4-MN_MACDB_ADD |
4-Warning |
Failed to add MN to MAC DB { MN: [enet] AP: [inet] } |
The L3MM failed to add the entry for the specified MN into the MN MAC database |
cat6000-wireless |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
L3MM-4-MN_MACDB_DEL |
4-Warning |
Failed to delete MN from MAC DB { MN: [enet] [inet] AP: [inet] WNID: [dec] } |
The L3MM failed to delete the entry for the specified MN from the MN MAC database |
cat6000-wireless |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
L3MM-5-WLAN |
5-Notice |
Wireless LAN Module in slot [dec] is [chars] |
The L3MM detected a change in the state of the Wireless LAN module in the specified slot. If the module is now on line L3MM starts accepting access-point and mobile-node registrations from the WDS on the module. If the module is now off line L3MM purges all access points and mobile nodes received from the module. |
- |
LOG_STD_NO_ACTION |
|
L3MM-5-WLAN_COMM_ABORT |
5-Notice |
Communication with Wireless LAN Module in slot [dec] aborted [chars] |
The Layer 3 Mobility Manager detected communication failure with the Wireless LAN module specified in the error message above and will respond as if the module went offline by purging its access point and mobile node databases. However the module will not be reset by the Layer 3 Mobility Manager |
- |
LOG_STD_NO_ACTION |
|
L3MM-5-WLAN_PWR_DN |
5-Notice |
Wireless LAN Module in slot [dec] will be powered down another module is already active |
The L3MM detected a Wireless LAN module trying to come online while another module was already functional as the active Wireless LAN module. The L3MM does not support more than one Wireles LAN module online in the chassis at a given time which is why this module will be powered down |
- |
LOG_STD_NO_ACTION |
|
L3TCAM-3-SIZE_CONFLICT |
3-Error |
[chars] requires enabling extended routing |
In order to support this feature TCAM entry needs to be configured to extended routing enable. |
firmware |
"Modify the Switch Database Management SDM " "template to enable the switch to support the " "144-bit Layer 3 TCAM. Use the sdm prefer " "extended-match sdm prefer access extended-match " "or sdm prefer routing extended-match global " "configuration command and then reload the switch " "by using the reload privileged EXEC command." |
|
L3TCAM-3-TOO_MANY_VRF |
3-Error |
Exceed the maximum number of VRF allowed |
The number of VPN exceeds the maximum number of allowed VPN routing/forwarding table on this hardware platform. |
firmware |
"Reconfigure your switch to limit the number " "of VRFs. Do not define name more than seven " |
|
L4_INSPECT-3-INVALID_CHUNK_ID |
3-Error |
Invalid chunk ID for protocol [dec] |
Failed to determine chunk ID for specified protocol. Unable to free CFT feature object. |
qfp-cxsc |
LOG_STD_ACTION |
|
L4-3-HA_INVALID_MSG_LEN_RCVD |
3-Error |
invalid [chars] rg [dec] [dec] expected [dec] opcode [chars] [hec] |
Standby received an invalid Firewall HA message |
cpp-ucode |
LOG_STD_ACTION |
|
L4-3-HA_INVALID_MSG_RCVD |
3-Error |
invalid [chars] [hec] expected [hec] opcode [chars] [hec] |
Standby received an invalid Layer 4 HA message |
cpp-ucode |
LOG_STD_ACTION |
|
L4F-2-INVALIDFLOW |
2-Critical |
Invalid L4F flow: 0x[hec] |
An invalid L4F flow entry was detected. |
layer4-forwarding |
"If this message recurs copy it down exactly as it appears and contact\n\ your technical support representative for assistance." |
|
L4F-2-SEMLOCKFAILURE |
2-Critical |
Cannot lock TCP semaphore on flow 0x[hec] with tcb 0x[hec] |
Cannot obtain the semaphore lock for a TCB we expect to be able to lock. |
layer4-forwarding |
"If this message recurs copy it down exactly as it appears and contact\n\ your technical support representative for assistance." |
|
L4F-4-L4F_REINJECT_HANDLE_ERROR |
4-Warning |
L4F reinject [chars] |
L4F reinjection handle creation or update failed. |
layer4-forwarding |
"If this message recurs copy it down exactly as it appears and contact\n\ your technical support representative for assistance." |
|
L4F-5-NOBUFFER |
5-Notice |
Cannot allocate buffer to send data on the flows [chars]:[dec] -> [chars]:[dec] |
A buffer could not be allocated while trying to send data on the\n\ indicated flow. The issue could be due to low or fragmented memory.\n\ If the memory issue doesn't resolve automatically it could result\n\ in connection resets. |
layer4-forwarding |
"This is an informational message that potential points to low or\n\ fragmented memory which could happen if the router is running beyond\n\ its resource limits. Check the number of flows and the traffic rate\n\ going through the router and contact your technical support\n\ representative with that info for assistance." |
|
L4F-6-L4F_FLOW_CREATION_FAILED |
6-Information |
L4F flow creation failed [chars] |
L4F flow entry creation failed due to an error. |
layer4-forwarding |
"If this message recurs copy it down exactly as it appears and contact\n\ your technical support representative for assistance." |
|
L4F-6-L4F_FLOW_LIMIT_EXCEED |
6-Information |
L4F flow limit was exceeded:[dec] |
This is an informational message. L4F flow max limit was exceeded. |
layer4-forwarding |
"Issue the" "<CmdBold>show l4f statistics <NoCmdBold> command and " "contact your technical support representative and \n\ provide the representative with the gathered information." |
|
LABEL_ALLOC_FAIL-3-ATOM_TRANS |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
LABEL_REGION-3-LCON |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
LANCE-1-INITFAIL |
1-Alert |
msgtxt_initfail |
The hardware failed to initialize correctly. |
- |
"Repair or replace the controller." |
|
LANCE-1-MEMERR |
1-Alert |
msgtxt_memoryerror |
An Ethernet interface detected a hardware problem. |
- |
"Repair or replace the controller." |
|
LANCE-3-BADCABLE |
3-Error |
msgtxt_badcable |
Ethernet cable is not connected. |
- |
"Check Ethernet cable connection." |
|
LANCE-3-BADUNIT |
3-Error |
msgtxt_badunit |
An internal software error occurred. |
- |
"If either message recurs call your technical support representative\n\ for assistance." |
|
LANCE-3-OWNERR |
3-Error |
msgtxt_ownerror |
An Ethernet interface is malfunctioning or an internal software error\n\ occurred. |
- |
"Repair or replace the controller." |
|
LANCE-3-SPURIDON |
3-Error |
Unit [dec] spurious IDON interrupt csr[dec]=0x%04x |
An Ethernet interface generated a spurious Initialization Done\n\ interrupt. |
- |
"Repair or replace the controller." |
|
LANCE-3-UNDERFLO |
3-Error |
Unit [dec] underflow error |
The Ethernet hardware is requesting data faster than the system can\n\ supply it. This condition might indicate that the system is at the\n\ limit of its performance. |
- |
"A small number of underflows might not be a cause for concern. You can\n\ monitor underflows with the show interface command. Reducing the load\n\ on the router or installing a higher-performance router should\n\ alleviate this problem." |
|
LANCE-4-BABBLE |
4-Warning |
Unit [dec] babble error csr0 = 0x[hec] |
An Ethernet interface is malfunctioning. |
- |
"Determine whether the malfunction stems from a software or hardware\n\ error by turning off all fastswitching.\n\\n\ Error messages showing that the packet is too large for the link\n\ indicate a software error at a high level.\n\\n\ Copy the error message exactly as it appears and report it to your\n\ technical support representative.\n\\n\ Receiving no error messages indicates a hardware error. \n\\n\ Repair or replace the controller." |
|
LANCE-5-COLL |
5-Notice |
Unit [dec] excessive collisions. TDR=[dec] |
- |
- |
"If the transceiver appears to be properly terminated repair or\n\ replace the Ethernet interface card." |
|
LANCE-5-LATECOLL |
5-Notice |
Unit [dec] late collision error |
An Ethernet transceiver is malfunctioning the Ethernet is overloaded\n\ or the Ethernet cable is too long. |
- |
"Repair or replace the controller." |
|
LANCE-5-LOSTCARR |
5-Notice |
Unit [dec] lost carrier. Transceiver problem? |
An Ethernet transceiver is unplugged or faulty. |
- |
"Repair or replace the controller." |
|
LANE-3-BADILMI |
3-Error |
Unexpected ILMI event [dec] |
An internal error occurred. |
- |
"This error should not occur. Download the system error log then call\n\ your technical support representative and provide the log the error\n\ message and the router configuration." |
|
LANE-3-BADNAME |
3-Error |
ELAN name must be 1-32 characters long |
A name which is longer than 32 characters identifying a LANE \n\ component has been entered by the user. |
- |
"Re-enter a shorter name." |
|
LANE-3-BADTYPE |
3-Error |
Inappropriate LAN type |
An unexpected LAN type has been specified for a LANE component.\n\ Only ethernet and token-ring elans are supported. |
- |
"Specify a valid LAN type." |
|
LANE-3-LANE_ERROR |
3-Error |
[chars] |
An internal error has occured which reflects an inconsistency\n\ in the system and needs attention. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
LANE-3-LANE_SIG_ERR |
3-Error |
[chars] |
An internal error occurred while system routines were handling ATM\n\ signaling messages for LANE. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
LANE-3-LEC_BAD_CTL_DIST_TYPE |
3-Error |
[chars] CTL DIST blli type wrong |
Wrong BLLI value specified on the incoming circuit. |
- |
"The originator of the circuit is not using the correct BLLI value\n\ for this type of circuit. LANE standard defines these values and\n\ the originator is violating the standard." |
|
LANE-3-LEC_BADAD |
3-Error |
[chars] LEC unable to compute ATM address |
The client cannot obtain an ATM address from the given configuration\n\ or auto-assignment failed to get an ATM prefix from the switch. |
- |
- |
|
LANE-3-LEC_CFG |
3-Error |
[chars] CFG_REQ failed [chars] LECS returned [dec] |
The master LECS refused the LEC's configuration request. |
- |
"Check your LECS configurations." |
|
LANE-3-LEC_CONTROL_MSG |
3-Error |
Received bad control message on interface [chars] |
The LANE client received an unexpected or inappropriate control message \n\ over one of its vc's. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
LANE-3-LEC_ERR |
3-Error |
[chars] |
A LANE client software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
LANE-3-LEC_JOIN |
3-Error |
[chars] JOIN failed [chars] LES returned [dec] |
LANE client was rejected the Join request to join its elan. |
- |
"This is usually because of user configuration errors: LANE client\n\ attempting to join an incorrect elan or elan not configured\n\ in the LES or validation failures with the LECS etc..." |
|
LANE-3-LEC_LISTEN |
3-Error |
[chars] listen failed on [chars] |
The LANE client could not register its address with ATM signalling\n\ to be able to accepts calls on that address. |
- |
"Reconfigure the client ATM address. It may be conflicting with another\n\ component with the same ATM address." |
|
LANE-3-LEC_RD_REGISTER |
3-Error |
[chars] RD REGISTER failed for Route Descriptor [hec] |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
LANE-3-LEC_REGISTER |
3-Error |
[chars] REGISTER failed [chars] LES returned [dec] |
attempt to register a mac-atm address binding with LES failed. |
- |
"The LES has already registered the requested mac addr - atm addr binding." |
|
LANE-3-LEC_SIGNAL |
3-Error |
Unexpected SigAPI event [dec] |
ATM signaling sent the LANE client an unexpected message type. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
LANE-3-LEC_WRONG_ELAN_ID |
3-Error |
[chars]: elan id mismatch: LECS indicates [dec] LES indicates [dec] |
The elan-id returned by LES does not match the value given by LECS or\n\ via the CLI |
- |
"Check configuration of elan ids specified in the LECS database and\n\ the LES. The mismatch must be occuring as a result of misconfiguration." |
|
LANE-3-LECS_ERROR |
3-Error |
MSG_TRACEBACK | MSG_PROCESS |
- |
- |
- |
|
LANE-3-LES_ERROR |
3-Error |
[chars] |
A serious internal occured with LES/BUS. |
- |
"This error should not occur. Download the system error log then call\n\ your technical support representative and provide the log the error\n\ message and the router configuration." |
|
LANE-3-LSV_BADAD |
3-Error |
[chars] elan [chars] unable to compute [chars] ATM address |
- |
- |
"Enter a correct ATM address template for the LANE component \"BUS\"\n\ \"server\" or \"config server\" named in the error message." |
|
LANE-3-LSV_CRASH |
3-Error |
[chars] elan [chars] unrecoverable error [chars] |
A very serious LES/BUS internal error occurred. |
- |
"This error should not occur. Download the system error log then call\n\ your technical support representative and provide the log the error\n\ message and the router configuration." |
|
LANE-3-NAMECHG |
3-Error |
A LANE Client is already running here using another elan name |
Both the LANE client and the LANE server/BUS may have an emulated LAN\n\ name specified in the configuration via the lane server-bus and lane\n\ client commands. If both specify the emulated LAN name then the name\n\ cannot be changed by re-entering just one of the commands. |
- |
"Use the no lane server-bus command to delete the server-bus or the no\n\ lane client command to delete the client. Then the other of the two\n\ commands can be re-entered with another emulated LAN name. Finally\n\ re-enter the deleted command with the new emulated LAN name." |
|
LANE-3-NOILMI |
3-Error |
ILMI service registration failed |
- |
- |
"This error should not occur. Download the system error log then call\n\ your technical support representative and provide the log the error\n\ message and the router configuration." |
|
LANE-3-NOINT |
3-Error |
[chars] still destroying old sub-interface |
An attempt was made to create a new subinterface while a previous\n\ version of the subinterface was still being destroyed. |
- |
"Wait a minute and try again. If failure still occurs try shutting\n\ down the main interface. Rebooting may be required to recover in\n\ extreme cases." |
|
LANE-3-NOREGILMI |
3-Error |
[chars] [chars] cannot register %Cj with ILMI |
An attempt to register the given ATM address with the ATM switch\n\ failed. This failure can occur because the ATM switch is down or\n\ misconfigured. The registration will be retried. |
- |
"If the situation persists after a number of attempts and the switch\n\ is up the configuration of the switch and router should be examined. A \n\ likely cause is that the ATM address being registered is not\n\ compatible with the parameters configured in the switch. Correct the configuration." |
|
LANE-3-TYPECHG |
3-Error |
A LANE Client is already running here using another elan type |
- |
- |
"Use the no lane server-bus command to delete the server-bus or the no\n\ lane client command to delete the client. Then the other of the two\n\ commands can be re-entered with a new type. Finally re-enter the\n\ deleted command with the new type." |
|
LANE-4-LECS_WARNING |
4-Warning |
[chars] |
- |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
LANE-4-LSV_ADDR |
4-Warning |
[chars] elan [chars] unable to register LES/BUS ATM addr |
LANE Server or BUS could not register its address with ILMI. |
- |
"Try and investigate why. Some of the reasons are: user defined\n\ override address does not conform to the switch prefix or that\n\ there is a problem with the ATM switch with whom the entity is \n\ registering." |
|
LANE-4-LSV_LECID |
4-Warning |
[chars] elan [chars] LECIDs exhausted |
The LANE server specified has 65279 clients. No more can be added. |
- |
"Change the configurations to avoid trying to have more than 65279 LANE\n\ clients on this server." |
|
LANE-5-UPDOWN |
5-Notice |
[chars] [chars] [chars]: [chars] changed state to [chars] |
A LANE component changed state to up/down. |
- |
"If this event is expected then take no action. Otherwise\n\ please contact a technical support representative." |
|
LANE-6-INFO |
6-Information |
[chars] |
LANE subsystem simple informational messages. |
- |
"None." |
|
LANE-6-LEC_INFO |
6-Information |
[chars] |
LANE client informational messages. |
- |
"None." |
|
LANE-6-LECS_INFO |
6-Information |
[chars] |
Simple informational LECS messages. |
- |
"None." |
|
LANE-6-LES_INFO |
6-Information |
[chars] |
Simple informational LES messages. |
- |
"None." |
|
LANMGR-2-NOMEMORY |
2-Critical |
No memory available: [chars] |
The requested operation failed because of a low memory condition. |
- |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
LANMGR-4-BADRNGNUM |
4-Warning |
Ring number mismatch on [chars] shutting down the interface |
- |
- |
"Check all bridges connected to this Token Ring and ensure that they\n\ are using the same assigned ring number." |
|
LANMGR-4-BADUPCALL |
4-Warning |
Unexpected call [chars] from LLC2 for Bridge %03x-[hec]-%03x |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
LANMGR-4-NORING |
4-Warning |
No ring info for [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
LANMGR-4-OLDTRAMON |
4-Warning |
Cannot run RPS on [chars] Old TRAMON code. |
The software on this interface cannot support the functions required\n\ for LAN Network Manager. |
- |
"Call your Cisco technical support representative about a\n\ firmware upgrade for this interface card." |
|
LAPB-2-NOBUF |
2-Critical |
Interface [chars] no buffer available to [chars] |
There was insufficient memory for the LAPB protocol engine to send a\n\ message. |
lapb |
"This message is acceptable if it occurs infrequently because the LAPB\n\ protocol is designed to handle loss of frames. Frequent occurrences can\n\ cause disruption of service. The system can be configured to ease\n\ memory demands or if conditions warrant the system can be upgraded to\n\ a larger memory configuration." |
|
LAPB-3-BADPAYLOAD |
3-Error |
Interface [chars] Invalid payload value: [chars] |
An internal software error occurred. |
lapb |
"If either of these messages recur call your technical support\n\ representative for assistance." |
|
LAPB-3-CONTEXTERR |
3-Error |
[chars]: [chars] |
An internal software error occurred. |
lapb |
"If either of these messages recur call your technical support\n\ representative for assistance." |
|
LAPB-3-NOINPIDB |
3-Error |
Input idb not set |
An internal software error occurred. |
lapb |
"If either of these messages recur call your technical support\n\ representative for assistance." |
|
LAPB-3-NULLPAK |
3-Error |
Interface [chars] NULL packet ptr rvr [dec] vs [dec] vr [dec] |
An internal software error occurred. |
lapb |
"If either of these messages recur call your technical support\n\ representative for assistance." |
|
LAPB-3-TIMERERR |
3-Error |
LAPB timer task cannot be created |
An internal software error occurred. |
lapb |
"If either of these messages recur call your technical support\n\ representative for assistance." |
|
LAPB-4-CTRLBAD |
4-Warning |
Interface [chars] Invalid control field |
A received FRMR reported a frame with an invalid control code. |
lapb |
"Check the serial line and the devices attached to the line." |
|
LAPB-4-FRAMEERR |
4-Warning |
Interface [chars] Frame error: CF [hex] VS [dec] [chars] VR [dec] Reason [hex] |
- |
lapb |
- |
|
LAPB-4-INFOBAD |
4-Warning |
Interface [chars] Info field not permitted |
A received FRMR frame reported that an information field was present\n\ in a frame where no information field is allowed. |
lapb |
"Check the serial line and the device attached to the line." |
|
LAPB-4-INVNR |
4-Warning |
Interface [chars] Invalid NR value |
A received FRMR reported a frame with an invalid NR value. |
lapb |
"Verify that the equipment attached to the serial line is configured\n\ with the same K value maximum number of outstanding I frames." |
|
LAPB-4-N1TOOBIG |
4-Warning |
Interface [chars] N1 too large |
A received FRMR reported an information frame that was too long. |
lapb |
"Verify that the equipment attached to the serial line is configured\n\ with the same N1 value. N1 is in bits and includes the entire frame\n\ plus 16 bits of CRC. However some equipment may require configuration\n\ in octets the omission of the two CRC octets or the omission of the\n\ three octets of LAPB control information." |
|
LAPP_OFF-1-NOMEMORY |
1-Alert |
msgtxt_nomemory |
The requested operation could not be accomplished because of a low\n\ memory condition. |
- |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
LAPP_OFF-2-INTERNAL_ERROR |
2-Critical |
Internal software error [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
LAPP_OFF-2-LAPP_OFF_INTERNAL_ERROR |
2-Critical |
Internal software error [chars] cid=[dec] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
LAPP_OFF-4-LAPP_OFF_BAD_MESSAGE |
4-Warning |
LAPP_OFF- Bad message received |
An unexpected message was received. |
- |
LOG_STD_RECUR_ACTION |
|
LAPP_OFF-4-LAPP_OFF_NO_SMTP |
4-Warning |
mmsp- Can't connect to the SMTP server |
No connection was created to the specified SMTP server. |
- |
LOG_STD_RECUR_ACTION |
|
LAPP_OFF-4-LAPP_OFF_NO_SMTP_SEND |
4-Warning |
FAXMAIL- Could not\n\send data to the SMTP server |
A connection was made to the SMTP server but no data can be sent. |
- |
LOG_STD_RECUR_ACTION |
|
LAPP_OFF-4-SMTP_NOT_CONNECTED |
4-Warning |
SMTP- failed [chars] [dec] |
A connection attempt to a remote mail server was not successful.\n\ This unexpected behavior. |
- |
LOG_STD_NO_ACTION |
|
LAPP_OFF-6-LAPP_OFF_CAUSE_ABNORMAL |
6-Information |
Call aborted cause = 0x[hec] |
Call Aborted due to abnormal error |
- |
LOG_STD_NO_ACTION |
|
LAPP_OFF-6-SMTP_OPEN |
6-Information |
SMTP- opening [chars] [dec] |
A connection attempt ... |
- |
LOG_STD_NO_ACTION |
|
LAPP_ON_MSGS-6-LAPP_ON_CAUSE_AUTH_FAILED |
6-Information |
User authentication failed |
Call aborted due to user authentication failure |
- |
LOG_STD_NO_ACTION |
|
LAPP_ON_MSGS-6-LAPP_ON_CAUSE_DMSP_DISCONNECTED |
6-Information |
Document Media Service DMSP disconnected |
Call aborted due to Document Media Service DMSP disconnect |
- |
LOG_STD_NO_ACTION |
|
LAPP_ON_MSGS-6-LAPP_ON_CAUSE_DMSP_DISCONNECTED_NO_ROUTE |
6-Information |
DMSP - no route - likely - ESMTP client did not connect to remote server |
Call aborted due to DMSP no route disconnect - likely reason being no ESMTP connection to remote server |
- |
LOG_STD_NO_ACTION |
|
LAPP_ON_MSGS-6-LAPP_ON_CAUSE_FMSP_DISCONNECTED |
6-Information |
Fax protocol FMSP disconnected |
Call aborted due to Fax sessionFMSP disconnect |
- |
LOG_STD_NO_ACTION |
|
LAPP_ON_MSGS-6-LAPP_ON_CAUSE_INTERNAL |
6-Information |
Internal error occured |
Call aborted due to an internal error |
- |
LOG_STD_NO_ACTION |
|
LAPP_ON_MSGS-6-LAPP_ON_CAUSE_NO_ESMTP_CONNECT |
6-Information |
ESMTP client did not connect or lost connection to remote server |
Call aborted due to loss of outbound ESMTP connection to remote server |
- |
LOG_STD_NO_ACTION |
|
LAPP_ON_MSGS-6-LAPP_ON_CAUSE_NO_MEMORY |
6-Information |
No memory available |
Call aborted due to insufficient memory being available |
- |
LOG_STD_NO_ACTION |
|
LAPP_ON_MSGS-6-LAPP_ON_CAUSE_NORMAL |
6-Information |
Normal call clearing |
Call clearing occurred normally |
- |
LOG_STD_NO_ACTION |
|
LAPP_ON_MSGS-6-LAPP_ON_CAUSE_VTSP_DISCONNECTED |
6-Information |
Telephony interface VTSP disconnected |
Call termination due to Telephony interface disconnect |
- |
LOG_STD_NO_ACTION |
|
LAT-3-BADDATA |
3-Error |
Tty[t-line] Data pointer does not correspond to current packet |
An internal software error occurred. |
- |
"If this message recurs contact your technical support representative." |
|
LAT-3-BUFFULL |
3-Error |
Tty[t-line] data buffer full with count [dec] |
An internal software error occurred. |
- |
"If this message recurs contact your technical support representative." |
|
LAT-3-NOSYNC |
3-Error |
Tty[t-line] Output data ptrs out of sync with byte count |
An internal software error occurred. |
- |
"If this message recurs contact your technical support representative." |
|
LAT-3-NULLIDB |
3-Error |
Null IDB pointer with destination [enet] |
An internal software error occurred. |
- |
"If this message recurs contact your technical support representative." |
|
LAT-3-QBSPACED |
3-Error |
Queue block at [hec] not found for HI connection |
An internal software error occurred. |
- |
"If this message recurs contact your technical support representative." |
|
LAT-3-REUSE |
3-Error |
Tty[t-line] Attempt to re-use slot array empty = [dec] fill = [dec] |
An internal software error occurred. |
- |
"If this message recurs contact your technical support representative." |
|
LATREVNUMWRAP-3-LCON |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
LAYER2_BRIDGE-3-ALLOC_FAILED |
3-Error |
Allocation of [chars] memory failed for layer 2 bridging feature in QFP |
Allocation of memory by the QFP layer 2 bridging feature microcode failed. The name of the memory chunk is specified in the message. This indicates a software failure |
qfp-bridging |
LOG_STD_ACTION |
|
LAYER2_BRIDGE-3-HA_BULK_SYNC_FAIL |
3-Error |
rg [dec] |
There was a failure such that Layer 2 bridge domain bulk sync did not occur |
cpp-ucode |
LOG_STD_ACTION |
|
LAYER2_BRIDGE-3-HA_INVALID_STATE |
3-Error |
state [dec] |
An invalid HA state was received from the HA infrastructure. |
cpp-ucode |
LOG_STD_ACTION |
|
LAYER2_BRIDGE-3-INIT_FAILED |
3-Error |
Initialization of the layer 2 bridging feature in QFP failed |
Initialization of the layer 2 bridging feature in the QFP failed. This indicates a software failure. |
qfp-bridging |
LOG_STD_ACTION |
|
LAYER2_BRIDGE-3-PKT_REPLICA_INIT_FAILED |
3-Error |
Failed to register with generic packet replication for layer 2 bridging feature in QFP |
Layer 2 bridging initialization of packet replication registration failed. |
qfp-bridging |
LOG_STD_ACTION |
|
LAYER2_SVI-3-ALLOC_FAILED |
3-Error |
Allocation of [chars] memory failed for SVI feature in QFP |
Allocation of memory by the QFP SVI feature microcode failed. The name of the memory chunk is specified in the message. This indicates a software failure |
qfp-switch-infra |
LOG_STD_ACTION |
|
LAYER2_SVI-3-INIT_FAILED |
3-Error |
Initialization of the SVI feature in QFP failed |
Initialization of the SVI feature in the QFP failed. This indicates a software failure. |
qfp-switch-infra |
LOG_STD_ACTION |
|
LAYER2_SVI-3-PKT_REPLICA_INIT_FAILED |
3-Error |
Failed to register with generic packet replication for SVI feature in QFP |
SVI initialization of packet replication registration failed. |
qfp-switch-infra |
LOG_STD_ACTION |
|
LB-3-ACL_FCB_REG_ERROR |
3-Error |
Failed to registered Link Bundle ACL feature control block |
For the given interface failed to register the ACL feature control block. |
gsr-link-bundling |
LOG_STD_ACTION |
|
LB-3-CHUNK_CREATE_FAIL |
3-Error |
[chars]channel: failed to create chunk |
An internal data structure called a chunk and used for channel route processor - line card interprocess communications failed to be created. Such interprocss communication may be impeded. |
gsr-link-bundling |
LOG_STD_ACTION |
|
LB-3-ECHAN_ADDR_ALLOC_ERROR |
3-Error |
Channel [dec] error in MAC address allocation configured MAC address [enet] actual MAC address [dec] |
For the given channel number addition of the first member caused a failure in changing the MAC address of the channel to that of this first member. |
gsr-link-bundling |
LOG_STD_ACTION |
|
LB-3-ECHAN_CMDREP_REG_FAILURE |
3-Error |
Failed to register bundle interface [chars] for Command Replay service |
For the given link bundle interface failed to register it for the Command Replay service. |
gsr-link-bundling |
LOG_STD_ACTION |
|
LB-3-ECHAN_FCB_ERROR |
3-Error |
Bundle creation feature callback failed for [chars] |
For the given link bundle interface failed to create its feature callback. |
gsr-link-bundling |
LOG_STD_ACTION |
|
LB-3-FEATURE_ACL_APPLY_ERROR |
3-Error |
Failed to apply ACL [dec] to interface [chars]. Removing new ACL config reapplying old ACL [dec]. |
For the given member interface or subinterface failed to apply the given ACL. This new ACL configuration is removed from the bundle and the old ACL configuration if any is reapplied to the bundle. The new ACL that failed to be applied is removed in order to maintain consistent state for the whole bundle. |
gsr-link-bundling |
LOG_STD_ACTION |
|
LB-3-FEATURE_ACL_REG_ERROR |
3-Error |
Failed to register ACL control block with Link Bundle subinterface module |
For the given interface failed to register the ACL feature control block. This happened during install ACL support for link bundling. ACL support installation for link bundling is aborted. |
gsr-link-bundling |
LOG_STD_ACTION |
|
LB-3-FEATURE_INSTALL_ERROR |
3-Error |
One or more NULL feature control block members |
In installing link bundling feature support there were one or more NULL function pointers used in a feature control block. Installation of the feature support is aborted. |
gsr-link-bundling |
LOG_STD_ACTION |
|
LB-3-FEATURE_MODULE_INIT_ERROR |
3-Error |
Failed to create Link Bundle Feature ListQ |
In initializing link bundling feature support an internal list queue failed to be created. |
gsr-link-bundling |
LOG_STD_ACTION |
|
LB-3-FEATURE_REG_ERROR |
3-Error |
One or more NULL feature callbacks in the passed in Feature Control Block |
In registering a feature for services from link bundling feature support there were one or more NULL function pointers used as function callbacks. Aborted the feature registration as a result. |
gsr-link-bundling |
LOG_STD_ACTION |
|
LB-3-FUNCTION_VECTOR_EMPTY |
3-Error |
Empty link bundling function vectors |
One or more function vectors used in generic etherchannel and poschannel code was null i.e. not initialized. This is a severe error resulting from a coding error. Crash will happen because this error prevents the proper functioning of the ether or pos channel features. |
gsr-link-bundling |
LOG_STD_ACTION |
|
LB-3-POSCHAN_CMDREP_REG_FAILURE |
3-Error |
Failed to register bundle interface [chars] for Command Replay service |
For the given link bundle interface failed to register it for the Command Replay service. |
gsr-link-bundling |
LOG_STD_ACTION |
|
LB-3-POSCHAN_FCB_ERROR |
3-Error |
Bundle creation feature callback failed for [chars] |
For the given link bundle interface failed to create its feature callback. |
gsr-link-bundling |
LOG_STD_ACTION |
|
LB-3-SUBINT_ERROR |
3-Error |
[chars] [chars] |
There was a subinterfce error for the given interface. |
gsr-link-bundling |
LOG_STD_ACTION |
|
LB-3-SUBINT_INSTALL_SUPPORT_FAILURE |
3-Error |
Failed to registered Link Bundle subinterface control block |
In initializing link bundling subinterface feature support could not register for notifications from the common link bundle infrastructure. |
gsr-link-bundling |
LOG_STD_ACTION |
|
LB-3-SUBINT_NOTIF_INIT_FAILURE |
3-Error |
Failed to create Link Bundle Subinterface ClientQ |
In initializing link bundling subinterface feature support an internal subinterface client queue failed to be created. |
gsr-link-bundling |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
LB-3-SUBINT_NOTIF_REG_FAILURE |
3-Error |
NULL notification callback |
In registering a client for service from the Link Bundling subinterface module the callback notification callback function was NULL. |
gsr-link-bundling |
LOG_STD_ACTION |
|
LB-5-CHAN_MEMBER_ADD_PASSIVE |
5-Notice |
[chars] added as passive member to [chars]channel[dec] |
The given interface was added as a passive member in the given channel number. |
gsr-link-bundling |
LOG_STD_NO_ACTION |
|
LB-5-CHAN_MEMBER_IN |
5-Notice |
[chars] added as member-[dec] to [chars]channel[dec] |
The given channel member interface was added to the given channel number. |
gsr-link-bundling |
LOG_STD_NO_ACTION |
|
LB-5-CHAN_MEMBER_MOVED_ACTIVE |
5-Notice |
[chars] moved to active state as member-[dec] in [chars]channel[dec] |
The given etherchannel member interface became an active member in the given channel number. |
gsr-link-bundling |
LOG_STD_NO_ACTION |
|
LB-5-CHAN_MEMBER_MOVED_PASSIVE |
5-Notice |
[chars] moved to passive state in [chars]channel[dec] |
The given channel member interface became a passive member in the given channel number. |
gsr-link-bundling |
LOG_STD_NO_ACTION |
|
LB-5-CHAN_MEMBER_OUT |
5-Notice |
[chars] taken out of [chars]channel[dec] |
The given channel member interface was taken out of the given channel number. |
gsr-link-bundling |
LOG_STD_NO_ACTION |
|
LCB-3-LOCKFAILURE |
3-Error |
Multiple LCB event processes scheduled |
This message occurs when LCB event process fails to lock the\n\ semaphore which is used to prevent multiple LCB processes from \n\ running. This implies that multiple LCB processes have been \n\ scheduled to run which should not happen |
- |
"Try executing the command again after a few minutes. If the problem\n\ persists contact Cisco Technical support" |
|
LCB-3-QUEUEFAILURE |
3-Error |
LCB process unable to create event queue |
Unable to create LCB event queue. LCB process quit. The operating\n\ system was unable to allocate RAM space for the queue |
- |
"Try executing the command again after a few minutes. If the problem\n\ persists it indicates a lack of RAM space. Most likely the router \n\ image requires more system memory RAM than the router contains." |
|
LCD_DISPLAY-3-CHAR_ERROR |
3-Error |
Invalid character |
This character is not supported by card LCD |
cmts-platform |
"Copy the error message exactly as it appears and report it to your " "technical support" |
|
LCD_DISPLAY-4-INPUT_ERROR |
4-Warning |
Invalid input DS [dec] US [dec] channels |
Wrong number of D/S or U/S channels |
cmts-platform |
"Copy the error message exactly as it appears and report it to your" " technical support" |
|
LCD_DISPLAY-4-STATUS_ERROR |
4-Warning |
Invalid status |
Invalid status bit |
cmts-platform |
"Copy the error message exactly as it appears and report it to your" " technical support" |
|
LCHA_INFRA-3-UNEXPECTED |
3-Error |
[chars] |
An unexpected error has occured while performing a linecard HA action |
iosxe-iosd-lcha |
LOG_STD_LCHA_SUP_ACTION |
|
LCHA_INFRA-4-CUTOVER |
4-Warning |
Cutover request received from slot [dec] |
A cutover interrupt received from a failing linecard |
cmts-platform-infra |
"Check core files and crashinfo files. Collect tech-support logs. Collect the system log using CLI 'show logging' and LCHA log on SUP using CLI 'show lcha logging level noise'." |
|
LCHA_INFRA-4-FORCE_RESET |
4-Warning |
Reset slot [dec] for reason: [chars] |
The SUP forced a linecard to reload for the given reason. |
cmts-platform-infra |
LOG_STD_LCHA_SUP_ACTION |
|
LCHA_INFRA-5-SW_RESET |
5-Notice |
Soft-reset slot [dec] [chars] |
The SUP software reset linecard's processes without HW reset it. |
cmts-platform-infra |
LOG_STD_NO_ACTION |
|
LCHA_INFRA-6-LCHA_INFO |
6-Information |
[chars] |
lcha information for better monitor chassis lcha relates status |
- |
LOG_STD_NO_ACTION |
|
LCHA-3-CFR_LIST |
3-Error |
Remove an element before destroy [chars]: cfrid=[dec] direction=[dec] state=[dec] ip_sadd=[inet] ip_daddr=[inet] dest_macaddr=[enet] src_macaddr=[enet] ip_prot=[dec] eport=[dec] |
Remove an element from interdb cfr_list before destroy the list. |
iosxe-iosd-lcha |
"Reset the system" |
|
LCHA-4-DYN_SRV |
4-Warning |
CM [enet] [chars] transcation id [dec] is not end before lc switch |
Dynamic service not finished |
iosxe-iosd-lcha |
LOG_STD_NO_ACTION |
|
LCHA-4-RF_RESIL_IDX_OUT_OF_RANGE |
4-Warning |
CM [enet] RF channel id [dec] is out of range [dec] |
RF channel index out of range |
iosxe-iosd-lcha |
LOG_STD_NO_ACTION |
|
LCINFO-3-CRASH |
3-Error |
Line card in slot [dec]/[dec] crashed |
The line card in the slot indicated crashed and sent a CRASH_START message to the PRE. The PRE is now waiting for the rest of the crash information from the line card to be sent via the BPE stack trace context version etc.. This should |
ubr10k-sw |
"Report this defect with as much information about the line card " "in question including the output of show context summary show " "context slot N and show tech-support N as well as the usual show " "tech-support from the PRE." |
|
LCINFO-3-INVDEV |
3-Error |
Invalid line card number in BPE callback LC=[dec]/[dec] |
The line card crash information subsystem on the PRE was called from the BPE subsystem with an invalid slot/subslot. The slot or subslot number is out of range. This indicates a software defect in the system. |
ubr10k-sw |
"Report this defect with as much information about the BPE " "subsystem as possible. There is no adverse effect to the PRE -- " "it ignores the bad callback and continues. If the problem " "persists reboot the router. It is unlikely but possible that " "the problem is due to bad BPE hardware somewhere in the system." |
|
LCINFO-3-INVSTATE |
3-Error |
Line card crash server in bad state LC=[dec]/[dec]state=[dec] |
- |
- |
- |
|
LCINFO-3-NOBUF |
3-Error |
Could not malloc line card crash structures on PRE size=[dec] |
The PRE could not malloc data structures for line card crash data structures at startup time. This is not in and of itself a Serious problem but the underlying memory shortage at startup time will probably prevent the router from running well if at all. |
ubr10k-sw |
"Add more memory and/or debug the memory shortage problem." |
|
LCINFO-3-NOBUFLC |
3-Error |
Could not malloc line card crash info buffer on PRE bufnum=[dec]size=[dec] |
- |
- |
- |
|
LCINFO-3-NOLCHANGPROC |
3-Error |
Failed creating line card hang cure process |
When creating the LC hang cure process for checking prolonged CLC down states the create_process call failed. This should not happen. It is probably due to a software defect or hardware failure. This failure should only happen during initialization. |
ubr10k-sw |
"Rebooting the system should fix this. If the condition persists " "on subsequent reloads of the system a bug should be filed and " "the system should be reloaded with a different image." |
|
LCINFO-3-NOPROCESS |
3-Error |
Failed creating line card complete process |
When creating the crash complete process for the crash information subsystem the create_process call failed. This should not happen. It is probably due to a software defect or hardware failure. This failure should only happen during initialization. |
ubr10k-sw |
"Rebooting the system should fix this. If the condition persists " "on subsequent reloads of the system a bug should be filed and " "the system should be reloaded with a different image." |
|
LCINFO-3-TIMEOUT |
3-Error |
Timeout waiting for crash info from slot [dec]/[dec] |
The crash information complete timer expired. When a line card crashes it sends information to the PRE for debugging and analysis. When the START OF CRASH message is recieved a timer is set for approx 10 seconds. The line card has 10 seconds to send all the crash information to the PRE. This is not a crash dump -- this is a small amount of information that usually includes context stack trace etc. It is less than 8K bytes of information. If an END OF CRASH information message is not received before the timer goes off the crash information record is closed contains partial information this message is |
ubr10k-sw |
"No action is required specifically because this message was " "displayed. Because the line card was crashing there might be " "other defects to report. If this message is seen without a line " "card crashing report this defect with the output of the usual " "commands includeing show tech-support on the PRE *AND* on the line " "card that didn't crash but was mentioned in this error " "message." |
|
LCINFO-4-LCHUNG |
4-Warning |
Slot [[dec]/[dec]] down on last [dec] checks. HW RESET # [dec] ... |
A line card can get hung in some IOS operation and is not able to recover or when rommon can get stuck while initiating tftp bootload. This is the time when an external monitoring process on RP checks for health of each line card. And if the line card is found stuck for more than 150 seconds a hardware reset is issued for that subslot. ANd while issuing a hard reset this error message is displayed onto the console. |
ubr10k-sw |
"Report this LC defect with as much information about the LC" |
|
LCINFO-4-TRUNC |
4-Warning |
Crash record [dec]=[chars] truncated expected=[dec]actual=[dec] |
A line card crashed an was sending crash information to the PRE. The PRE received a CRASH RECORD START message that indicated the data would be \expected\ bytes long. Before that many bytes were received the PRE received another CRASH RECORD START message indicating the start of another record. The current record is marked as truncated and the next record is received but the anomoly is noted in this error message. This is a problem but because what started this process was a line card crashing this might only be a symptom of another underlying problem. |
ubr10k-sw |
"Report this defect with as much information about the BPE subsystem " "and the line card crash information subsystem possible." |
|
LCINFO-4-UNXMSG |
4-Warning |
Unexpected crash info msg type [chars] in state [chars] LC=[dec]/[dec] |
The line card crash information subsystem received an unexpected message for the state it is in. The state and message type are given in the error message. This does not have any adverse effect on the PRE since it ignores and/or recovers from this occurrence. Because the sender of these messages is a line card that is crashing it is not completely unbelievable that this might happen. The source of the crash on the line card is more interesting. If this occurs without a line card crashing it is due to a stray/errant BPE message that should be persued. This could also be due to a dropped BPE message. |
ubr10k-sw |
"Find the source of the crash on the line card if one was crashing " "when the message occurred. If no line card was crashing report " "this defect with as much information about the BPE subsystem and " "the line card crash information subsystem as possible. If this " "message persists rebooting the router might help remove this " "message." |
|
LCINFO-6-LCRESET |
6-Information |
PRE switchover. Reset empty slot [[dec]/[dec]] |
When the standby PRE becomes active it resets all the slots which it thinks is empty. This prevents any linecards which was coming up during the PRE switchover from getting stuck |
ubr10k-sw |
"" |
|
LCLOG-3-INVDEV |
3-Error |
Invalid slot/subslot number in logger API callback LC=[dec]/[dec] |
The line card crash info subsystem on the PRE was called from the BPE subsystem with an invalid slot/subslot. This indicates a software defect in the system. |
ubr10k-sw |
"Report this defect with as much information about the subsystem as " "possible. There is no adverse effect to the PRE -- it ignores the " "bad callback and continues. If the problem is recurring " "rebooting the router is recommended." |
|
LCLOG-3-INVSTATE |
3-Error |
LC logger in bad state LC=[dec]/[dec]state=[chars]msg=[chars] |
- |
- |
- |
|
LCLOG-3-MSGGIANT |
3-Error |
LC log msg larger than max allowed LC=[dec]/[dec]length=[dec] |
- |
- |
- |
|
LCLOG-3-MSGTOOBIG |
3-Error |
LC log msg longer than expected LC=[dec]/[dec]len=[dec]exp=[dec] |
The PRE part of the line card logger server has received more text for a message than the start message indicated. This is probably due to a software defect. |
ubr10k-sw |
"Report this defect with as much information about the line card " "logger subsystem possible." |
|
LCLOG-3-OVERFLOW |
3-Error |
LC log msg longer than msg buffer LC=[dec]/[dec]len=[dec]max=[dec] |
The PRE part of the line card logger server has received more text for a message than will fit in the message log buffer. This is probably due to a software defect. |
ubr10k-sw |
"Report this defect with as much information about the line card " "logger subsystem possible." |
|
LCLTAG_ALLOC-3-LCON |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
LCMDC-3-ACCESS_FAIL |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
Submit An alarm - Prints out descriptive message |
- |
LOG_STD_ACTION |
|
LCMDC-3-DEBUG_INTF_CREATE_FAILED |
3-Error |
Transparent Interface Creation Failed for slot [[dec]] |
Interface data structure creation/initialization failed |
- |
LOG_STD_ACTION |
|
LCMDC-3-EOP_NOLG_ALM |
3-Error |
Egress Loss of Light: [chars] |
Egress side No Light |
- |
LOG_STD_ACTION |
|
LCMDC-3-EOP_NOLG_PALM |
3-Error |
Egress Loss of Light Prealarm: [chars] |
CDL Drop FIFO Overflow Prealarm |
- |
LOG_STD_ACTION |
|
LCMDC-3-ETH_DCC_LPBK_FAIL |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
Submit An alarm - Prints out descriptive message |
- |
LOG_STD_ACTION |
|
LCMDC-3-FPGA_ACCESS_FAIL |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
Submit An alarm - Prints out descriptive message |
- |
LOG_STD_ACTION |
|
LCMDC-3-IDPROM_ACCESS_FAIL |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
Submit An alarm - Prints out descriptive message |
- |
LOG_STD_ACTION |
|
LCMDC-3-IDPROMCRCFAIL |
3-Error |
IDPROM CRC check failed [[chars]] |
CRC check failed for IDPROM |
- |
LOG_STD_ACTION |
|
LCMDC-3-IDPROMMATCHFAIL |
3-Error |
IDPROM mismatch read failed [[chars]] |
check with catched value fail |
- |
LOG_STD_ACTION |
|
LCMDC-3-IDPROMRDFAIL |
3-Error |
IDPROM read failed [[chars]].\n \tThe card may not be inserted correctly. Please ensure that card is\n \tinserted completely and then please fasten the screws completely. |
The read error occurred when accessing the IDPROM |
- |
LOG_STD_ACTION |
|
LCMDC-3-INT_LPBK_FAIL |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
Submit An alarm - Prints out descriptive message |
- |
LOG_STD_ACTION |
|
LCMDC-3-INTF_CREATE_FAILED |
3-Error |
Interface Create Failed [[chars]] |
Interface data structure creation/initialization failed |
- |
LOG_STD_ACTION |
|
LCMDC-3-INTF_DELETE_FAILED |
3-Error |
Interface Delete Failed [[chars]] |
Interface data structure deletion failed |
- |
LOG_STD_ACTION |
|
LCMDC-3-INTRPENDING |
3-Error |
Pending unexpected interrupt [addr [hex] = [hex]] |
One or more pending unexpected interrupts |
- |
LOG_STD_ACTION |
|
LCMDC-3-INVALIDCLKRATE |
3-Error |
Non supported clock rate [dec] Khz |
The entered clock rate in Khz is not supported |
- |
LOG_STD_ACTION |
|
LCMDC-3-INVALIDSIGRATE |
3-Error |
Non supported signal rate [dec] |
The entered enum signal rate is invalid |
- |
LOG_STD_ACTION |
|
LCMDC-3-LASER_DEGRADE |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
Submit An alarm - Prints out descriptive message |
- |
LOG_STD_ACTION |
|
LCMDC-3-LASER_DEVIATION |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
Submit An alarm - Prints out descriptive message |
- |
LOG_STD_ACTION |
|
LCMDC-3-LINE_LASER_FAIL |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
Submit An alarm - Prints out descriptive message |
- |
LOG_STD_ACTION |
|
LCMDC-3-LPBK_THRU_PSC_FAIL |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
Submit An alarm - Prints out descriptive message |
- |
LOG_STD_ACTION |
|
LCMDC-3-LRCMAGICREGRESET |
3-Error |
Magic Register Reset Slot [dec] |
Magic Register Reset for Linecard in slot |
- |
LOG_STD_ACTION |
|
LCMDC-3-MDSUBCARD_IDPROM_FAIL |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
Submit An alarm - Prints out descriptive message |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_CDL_HEC_ALM |
3-Error |
CDL HEC Err count [chars] [chars] [chars] |
CDL HEC error count threshold exceeded |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_CDL_RFOF_IND |
3-Error |
CDL Drop FIFO OvrFL [chars] [chars] [chars] |
CDL Drop FIFO Overflow Prealarm |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_ECDRLK_ALM |
3-Error |
Egress CDR Locking error [chars] [chars] [chars] |
CDR is having trouble locking onto the signal. |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_EOP_NOLG_ALM |
3-Error |
Egress Loss of Light [chars] [chars] [chars] |
Egress side No Light |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_EOP_NOLG_PALM |
3-Error |
Egress Loss of Light Prealarm [chars] [chars] [chars] |
- |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_EOP_TKSW_ALM |
3-Error |
Egress Trunk Switch Mech. Failure [chars] [chars] [chars] |
Egress side switch failed to switch position during auto-failover |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_ESERDESLK_ALM |
3-Error |
Egress Serdes Locking error [chars] [chars] [chars] |
Serdes has trouble locking onto the signal |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_ESERPHERR_ALM |
3-Error |
Egress Serdes Phase Error [chars] [chars] [chars] |
Serdes has a phase error. |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_FH_ECETX_ALM |
3-Error |
Egress Fiber Channel/ESCON Line Err [chars] [chars] [chars] |
Fiber Channel/ESCON Line code error count exceeded threshold |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_FH_ELOSY_ALM |
3-Error |
Egress FC/ESCON Loss of Sync [chars] [chars] [chars] |
Fiber Channel/ESCON Syncronization error |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_FH_ICETX_ALM |
3-Error |
Ingress FC/ESCON Line Code err [chars] [chars] [chars] |
Ingress FC/ESCON Line code error count threshold exceeded |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_FH_ILOSY_ALM |
3-Error |
Ingress FC/ESCON Loss of Sync [chars] [chars] [chars] |
Ingress Fiber Channel/ESCON Loss of Syncronization |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_GE_ECETX |
3-Error |
Egress GE Line Code Err count [chars] [chars] [chars] |
GE Line Code error count exceeded threshold |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_GE_ELOSY_ALM |
3-Error |
Egress GE Loss of Sync [chars] [chars] [chars] |
GE Loss of Syncronization error |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_GE_ILOSY_ALM |
3-Error |
Ingress GE Loss of Sync [chars] [chars] [chars] |
Ingress GE Loss of the Syncronization |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_GH_ICETX_ALM |
3-Error |
Ingress GE Line Code Err [chars] [chars] [chars] |
Ingress Line Code error count threshold exceeded |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_ICDRLK_ALM |
3-Error |
Ingress CDR Locking error [chars] [chars] [chars] |
Ingress CDR failed to lock onto signal |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_IOP_NOLG_ALM |
3-Error |
Ingress Loss of Light [chars] [chars] [chars] |
Loss of Light |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_ISERDESLK_ALM |
3-Error |
Ingress Serdes Locking Error [chars] [chars] [chars] |
Ingress Serdes signal lock error |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_ISERPHERR_ALM |
3-Error |
Ingress Serdes Phase error [chars] [chars] [chars] |
Ingress Serdes out of Phase error |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_LN_OFC_IND |
3-Error |
Line OFC IND [chars] [chars] [chars] |
Ingress OFC Indication |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_LN_TX_ALM |
3-Error |
Line Laser Failure [chars] [chars] [chars] |
Laser failure |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_SH_EBIP_ALM |
3-Error |
Egress SONET BIP Err count [chars] [chars] [chars] |
SONET BIP Err count exceeded threshold |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_SH_ELOF_ALM |
3-Error |
Egress SONET Loss of Frame [chars] [chars] [chars] |
SONET Loss of Frame error |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_SH_ESEF_ALM |
3-Error |
Egress SONET SEF Prealarm [chars] [chars] [chars] |
Egress SONET Severely Errored Frame threshold exceeded |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_SH_IBIP_ALM |
3-Error |
Ingress SONET BIP error [chars] [chars] [chars] |
Ingress SONET BIP error count threshold exceeded |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_SH_ILOF_ALM |
3-Error |
Ingress SONET Loss of Frame [chars] [chars] [chars] |
Ingress SONET Loss of frame |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_SH_ISEF_ALM |
3-Error |
Ingress SONET SEF [chars] [chars] [chars] |
Ingress SONET Severely Errored Frame threshold exceeded |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_TK_OFC_IND |
3-Error |
Trunk OFC IND [chars] [chars] [chars] |
Egress OFC Indication |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_TK_TX_ALM |
3-Error |
Transmit Failure [chars] [chars] [chars] |
Transmit failure |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_TK_TX_LDGR |
3-Error |
Laser Degrade Trunk side [chars] [chars] [chars] |
Laser Degrade failure on the transmit side |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_TK_TX_WD |
3-Error |
Wavelength Deviation [chars] [chars] [chars] |
Wavelength deviation error |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_TK_WDEGRADE_ALM |
3-Error |
Trunk laser degrade: [chars] [chars] [chars] |
Trunk laser wavelength degrade |
- |
LOG_STD_ACTION |
|
LCMDC-3-MIB_TK_WDEVIATION_ALM |
3-Error |
Trunk Laser wavelength deviation: [chars] [chars] [chars] |
Trunk laser wavelength deviation |
- |
LOG_STD_ACTION |
|
LCMDC-3-OPT_SWITCH_0_FAIL |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
Submit An alarm - Prints out descriptive message |
- |
LOG_STD_ACTION |
|
LCMDC-3-OPT_SWITCH_1_FAIL |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
Submit An alarm - Prints out descriptive message |
- |
LOG_STD_ACTION |
|
LCMDC-3-OPT_SWITCH_2_FAIL |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
Submit An alarm - Prints out descriptive message |
- |
LOG_STD_ACTION |
|
LCMDC-3-OPT_SWITCH_3_FAIL |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
Submit An alarm - Prints out descriptive message |
- |
LOG_STD_ACTION |
|
LCMDC-3-OSC_HW_FAIL |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
Submit An alarm - Prints out descriptive message |
- |
LOG_STD_ACTION |
|
LCMDC-3-PORT_CREATE_FAILED |
3-Error |
Port Creation Failed [[chars]] |
Port data structure creation/initialization failed |
- |
LOG_STD_ACTION |
|
LCMDC-3-PORTFAILASSERTED |
3-Error |
Unexpected portfail asserted |
One or more unexpected portfails asserted |
- |
LOG_STD_ACTION |
|
LCMDC-3-RDWRFAIL |
3-Error |
Read/write failed [[chars]] |
A read/write error occurred when accessing the hardware |
- |
LOG_STD_ACTION |
|
LCMDC-3-READYPRESENT |
3-Error |
Card [slot [dec]] present but not ready |
Egress side switch failed to switch position during auto-failover |
- |
LOG_STD_ACTION |
|
LCMDC-3-STDBYOP_NOLG_ALM |
3-Error |
Loss of Light on Standby: [chars] |
Ingress SONET BIP error count threshold exceeded |
- |
LOG_STD_ACTION |
|
LCMDC-3-TK_WDEGRADE_ALM |
3-Error |
Trunk laser degrade: [chars] |
Trunk laser wavelength degrade |
- |
LOG_STD_ACTION |
|
LCMDC-3-TK_WDEVIATION_ALM |
3-Error |
Trunk Laser wavelength deviation: [chars] |
Trunk laser wavelength deviation |
- |
LOG_STD_ACTION |
|
LCMDC-3-TRUNK_LASER_DEGRADE |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
Submit An alarm - Prints out descriptive message |
- |
LOG_STD_ACTION |
|
LCMDC-3-TRUNK_LASER_DEVIATION |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
Submit An alarm - Prints out descriptive message |
- |
LOG_STD_ACTION |
|
LCMDC-3-WAVELENGTH_DEVIATION |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
Submit An alarm - Prints out descriptive message |
- |
LOG_STD_ACTION |
|
LCMDC-3-WAVELENGTH_MISMATCH |
3-Error |
Alarm: [chars] [chars] [chars] [chars] [chars] |
Submit An alarm - Prints out descriptive message |
- |
LOG_STD_ACTION |
|
LCMDC-3-WLENCKFAIL |
3-Error |
Unexpected trunk laser wavelength: [chars] |
Trunk laser wavelength is incorrect |
- |
LOG_STD_ACTION |
|
LCMDC-4-RATEMISMATCH |
4-Warning |
Encap rate mismatched: [chars] |
The entered encap rate is not matched with xcvr type |
- |
LOG_STD_ACTION |
|
LCMDC-5-DEFWAVELEN |
5-Notice |
Default wavelength selected: [chars] |
The inserted transponder can not support cached hwsb->itu_num so the default wavelength is used instead |
- |
LOG_STD_NO_ACTION |
|
LCMDC-6-TX_ALARM_SOAK |
6-Information |
[chars]\n |
Submit An alarm - Prints out descriptive message |
- |
LOG_STD_ACTION |
|
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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-LDPID |
3-Error |
peer [chars] LDP Id/Addr mapping problem [chars] |
EXPLANATION_ADDR_TBL_TAGCON |
mpls-ldp |
ACTION_TOGGLE_TAG_IP_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-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-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-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-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-RADIXTREE |
3-Error |
[chars]LIB walk failed [chars] |
- |
mpls-ldp |
ACTION_COPY_REPORT_TAGCON |
|
LCON-3-RADIXTREE |
3-Error |
[chars]LIB walk failed [chars] |
- |
mpls-ldp |
ACTION_COPY_REPORT_TAGCON |
|
LCON-3-REGISTRY |
3-Error |
Unexpected [chars] for reg_invoke_[chars] |
- |
mpls-ldp |
- |
|
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-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-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-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." |
|
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." |
|
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-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-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." |
|
LCPR_INFRA-3-UNEXPECTED |
3-Error |
[chars] |
An unexpected error has occured while performing linecard IOSD or CDMAN process restart. |
iosxe-iosd-lcpr |
"Check the IPC status of the platform. Collect the system log using CLI 'show logging' and LCHA log on SUP using CLI 'show lcha logging level noise'. Collect the lchaman iosd-clc and cdman btrace logs." |
|
LCPR_INFRA-5-PROGRESSION |
5-Notice |
[chars] |
LCPR generic progression information. |
iosxe-iosd-lcpr |
LOG_STD_NO_ACTION |
|
LCRED-2-RECEIVE_SYNC_MESSAGE_FAILED |
2-Critical |
Checkpointing sync message was received on Standby RP but it was corrupted or there was an error processing it. |
A sync message was sent from the Active RP and received on the Standby RP. The message was either empty corrupted or could not be processed by Standby client. If system is NOT in bulk sync mode then Standby RP will be reset. |
ha-lcred-infra |
"Informational. The linecard recovery " "infrastructure will take recovery actions." |
|
LCRED-2-SEND_SYNC_MESSAGE_FAILED |
2-Critical |
Checkpointing sync message to client on Standby RP was not received. |
A sync message was sent from the Active RP but it was never received or was received in corrupted form on the Standby RP. The platform code has been notified and platform-specific recovery actions will be taken. |
ha-lcred-infra |
"Informational. The linecard recovery " "infrastructure will take recovery actions." |
|
LCRED-2-SUBSYSTEM_INIT_FAILED |
2-Critical |
Subsystem failed during init phase with error [chars]. |
During subsystem initialization for LCRED Line Card Redundancy subsystem an unrecoverable error occurred. The system will come up and run fine but linecard redundancy will not be available for configuration and will not come up if it was already configured in start-config. |
ha-lcred-infra |
"You can continue to use the system without " "linecard redundancy. At your earliest convenience reloading the " "system might allow linecard redundancy subsystem to come up. In " "any case report the error message to TAC and include the " "following: 'show run' 'show redundancy linecard history' " "'show redundancy linecard all' and 'show version'." |
|
LCRED-2-SYNC_FAILURE_NO_BUFFER |
2-Critical |
Could not get sync buffer to checkpoint data. |
An attempt to get a sync buffer failed when trying to sync data from Active RP to Standby. This is likely a system memory issue. The platform code has been notified to take possible corrective action. |
ha-lcred-infra |
"Informational. The system will correct " "if possible." |
|
LCRED-3-CANT_SET_ROLE |
3-Error |
Couldn't set or clear slot or port roles for Line card [chars] idx=[dec]. |
Failed when attempting to set or clear the slot or port Active/Standby roles for a Line Card . |
ha-lcred-infra |
"This indicates an error during redundant " "linecard state progression. User should check redundancy config " "and try to remedy via CLI if not correct. Check config by " "'show redundancy linecard all' and 'show redundancy linecard " "group all'. If redundancy config cannot be corrected then " "open a TAC case attaching the info above and also 'show " "redundancy linecard history' 'show version' and 'show run'." |
|
LCRED-3-COULDNT_ADD_REDUNDANT_IF |
3-Error |
Error occurred while configuring redundant interface [dec]/[dec]: [chars] |
While configuring a redundant i/f the specified error occurred. This means the redundant configuration command was NOT successfully completed. |
ha-lcred-infra |
"First verify the command was correct and " "verify the current redundancy config with 'show redundancy " "linecard all' and 'show redundancy linecard group all'. If you " "feel the command was correct and failed anyway file a TAC " "case with the following: 'show run' 'show redundancy linecard " "history' 'show redundancy linecard all' 'show proc mem' and " "'show version'." |
|
LCRED-3-EREVENT1 |
3-Error |
[chars] 0x[hec] |
This message is used for reporting invalid values for parameters or database members. |
ha-lcred-infra |
"Check the redundancy configuration for the " "slot with 'show redundancy linecard all' and 'show " "redundancy linecard group all'. Fix the configuration " "if required and re-execute the command making sure " "any command parameters are correct. If it's still in " "error then file a case with TAC. In addition to the " "usual system information provide them with the output " "from above commands and 'show redundancy linecard " "history'." |
|
LCRED-3-HWIDB_SUBBLOCK_CREATE_FAIL |
3-Error |
Creation of hwidb subblock for [chars] i/f [chars] failed. |
Each redundant i/f whether active standby or virtual has a hwidb subblock that stores redundancy information about that i/f. If this subblock cannot be created then creation of the redundant i/f will fail. |
ha-lcred-infra |
"Try the CLI that triggered it again. If the " "error occurs again open a case with TAC. Report the output of " "'show redundancy linecard group all' and 'show redundancy " "linecard all' in addition to usual system configuration " "information." |
|
LCRED-3-INVALID_DEBUG |
3-Error |
Invalid debug type parameter [dec] specified. |
The function responsible for turning debugging on/off was called with an invalid debug type code. |
ha-lcred-infra |
"Verify the debug command is available " "by 'debug redundancy lc ?' and try it again." |
|
LCRED-3-IPC |
3-Error |
\n[chars] |
General IPC error. |
ha-lcred-infra |
"Check redundancy configuration with " "'show redundancy linecard all'. If the configuration is not " "what you expected try the commands again. If the configuration " "is correct and you get this message try switching over the " "linecard if the standby LC is configured and ready. Otherwise " "try resetting the linecard in the slot specified. If you still " "get the error submit a TAC case with the system information " "'show redundancy linecard all' and 'show proc mem'." |
|
LCRED-3-IPCPORT |
3-Error |
Can't Create IPC port [chars] error [chars] IPC err[chars]. |
Can't create IPC to receive traffic from peer. |
ha-lcred-infra |
"Check redundancy configuration with " "'show redundancy linecard all'. If the configuration is not " "what you expected try the commands again. If the configuration " "is correct and you get this message try switching over the " "linecard if the standby LC is configured and ready. Otherwise " "try resetting the linecard in the slot specified. If you still " "get the error submit a TAC case with the system information " "'show redundancy linecard all' and 'show proc mem'." |
|
LCRED-3-LC_CANT_SET_TXRX |
3-Error |
Unable to set Active/Standby Tx/Rx selection for Line Card [chars] idx=[dec]. |
Platform driver rejected a request to set the Tx/Rx selectors for a redundant linecard. |
ha-lcred-infra |
"This indicates the platform was unable to " "initialize linecard Active/STandby states. User should check " "redundancy config and try to remedy via CLI if not correct. " "Check config by 'show redundancy linecard all' and 'show " "redundancy linecard group all'. If redundancy config cannot " "be corrected then open a TAC case attaching the info above " "and also 'show redundancy linecard history' 'show version' " "and 'show run'." |
|
LCRED-3-LC_CARD_MISMATCH |
3-Error |
Mismatch is seen between Inserted card type0x%X [dec] and |
Inserted card type is rejected by lcred component due to mismatch between inserted card type and reserved card type |
ha-lcred-infra |
"This indicates the reserved card type is " "different than inserted card type. Check the reserve-cardtype setting " "in show run. Insert the card type same of reserve card type " "If the cards are of same type but still it shows mismatch then open " "a TAC case attaching output of 'show run' " "'redundancy linecard group all' 'redundancy lincard group <group#>.'" |
|
LCRED-3-LC_PROG_RETURNED_ERROR |
3-Error |
Progression attempt returned error for Line Card [chars] idx=[dec]. |
Attempt to complete progression failed. |
ha-lcred-infra |
"This indicates an error during redundant " "linecard state progression. User should check redundancy " "config and try to remedy via CLI if not correct. Check " "config by 'show redundancy linecard all' and 'show " "redundancy linecard group all'. If redundancy config cannot " "be corrected then open a TAC case attaching the info above " "and also 'show redundancy linecard history' 'show version' " "and 'show run'." |
|
LCRED-3-LC_PROG_TO_INIT_ERROR |
3-Error |
Unable to reset progression to INIT for Line Card [chars] idx=[dec]. |
Attempt to reinitialize progression failed. |
ha-lcred-infra |
"This indicates an error during redundant " "linecard state progression. User should check redundancy config " "and try to remedy via CLI if not correct. Check config by " "'show redundancy linecard all' and 'show redundancy linecard " "group all'. If redundancy config cannot be corrected then " "open a TAC case attaching the info above and also 'show " "redundancy linecard history' 'show version' and 'show run'." |
|
LCRED-3-LC_ROLE_NEG_DONE_WITH_ILLEGAL_ROLE |
3-Error |
Illegal Line Card redundancy role assignments found following role negotiation. |
When LC role negotiation is done illegal Line Card redundancy role was assigned to it and/or its peer. There are four kinds of roles can be assigned to a LC: Active Standby Wait or None. The only legal combination of roles for a slot and its peer are: Active-NONE Active-Standby WAIT-NONE. The rest are all illegal. |
ha-lcred-infra |
"Informational only. The LC Redundancy system " "will take recovery action." |
|
LCRED-3-LC_STATE_PROG_ERROR |
3-Error |
Illegal event in redundant Line Card [chars] idx=[dec] state progression. |
Illegal event in redundant Line Card state progression. |
ha-lcred-infra |
"This is informational. The LCRED system " "will reset the linecard to recover. No action is required " "unless the error keeps re-occurring. If it keeps happening " "then open a TAC case. Include 'show redundancy linecard all' " "'show redundancy linecard group all' and 'show redundancy " "linecard history'." |
|
LCRED-3-LC_STATE_PROG_FAILED |
3-Error |
Redundant Line Card [chars] idx=[dec] state progression failure. Line |
Redundant Line Card state progression failure. |
ha-lcred-infra |
"This is informational. The LCRED system " "will reset the linecard to recover. No action is required " "unless the error keeps re-occurring. If it keeps happening " "then open a TAC case. Include 'show redundancy linecard all' " "'show redundancy linecard group all' and 'show redundancy " "linecard history'." |
|
LCRED-3-LC_STATE_PROG_HARD_FAILURE |
3-Error |
Redundant Line Card [chars] idx=[dec] state progression failed more than [dec] |
Redundant Line Card state progression failure rate exceeds threshold. |
ha-lcred-infra |
"Open a TAC case attaching the following: " "'show redundancy linecard all' 'show redundancy linecard group " "all' 'show redundancy linecard history' 'show version' and " "'show run'." |
|
LCRED-3-LC_UP_WITH_ILLEGAL_ROLE |
3-Error |
Illegal Line Card redundancy role assignments during linecard up. |
When LC comes up illegal Line Card redundancy role was assigned to it and/or its peer. There are four kinds of roles can be assigned to a LC: Active Standby Wait or None. The only legal combination of roles for a slot and its peer are: Active-NONE Active-Standby WAIT-NONE. The rest are all illegal. |
ha-lcred-infra |
"Informational only. The system will reset " "both linecards in the redundant pair to recover." |
|
LCRED-3-MEMBERTWICE |
3-Error |
LC: Request to add slot member [dec] twice to group [dec]. |
An attempt was made to add a member from the specified slot to a redundant interface group which already contains a member from that slot. |
ha-lcred-infra |
"This is a user error. Please double-check " "the configuration with 'show redundancy linecard group " "all' and try the command again." |
|
LCRED-3-NO_HWIDB_RED_SUBBLOCK |
3-Error |
No redundancy subblock is found for i/f [chars]. |
Each redundant i/f whether active standby or virtual has a hwidb subblock that stores redundancy information about that i/f. If this subblock cannot be found then an error is reported. |
ha-lcred-infra |
"Try the CLI that triggered it again. If the " "error occurs again open a case with TAC. Report the output of " "'show redundancy linecard group all' 'show redundancy " "linecard all' and 'show redundancy linecard sub-block all' " "in addition to usual system configuration information." |
|
LCRED-3-NO_MORE_PREALLOCATED_SUBBLOCK_MEMORY |
3-Error |
Could not allocate redundancy subblock. Pre-allocated memory for subblock creation of [dec] is exhausted. |
The platform pre-allocates a pool of memory for creating redundancy subblocks via registry plfm_get_max_redundancy_sb. This pool has been |
ha-lcred-infra |
"Open a case with TAC. Report the contents " "of this message including the preallocation size value. " "Provide TAC with the following information: 'show run' " "'show ver' 'show hardware' and 'show proc mem'. TAC " "will need to get the platform in question to increase " "the pre-allocated pool of memory." |
|
LCRED-3-NO_SLOT_TO_DELETE |
3-Error |
LC: Request to delete non-member slot [dec] from redundancy group [dec]. |
An attempt was made to delete a slot from a redundant line card group which does not contain the specified slot as a member. |
ha-lcred-infra |
"Check the configuration with 'show " "redundancy linecard group all' and try command again." |
|
LCRED-3-NOINITMEM |
3-Error |
Subsystem Init [chars] Failed due to unavailability of memory of |
Initialization of LCRED subsystem failed due to insufficient memory. |
ha-lcred-infra |
"This is indicative of system memory " "shortage. The problem is likely unrelated to linecard " "redundancy. You should initiate recovery procedures as " "you would for any system that does not have sufficient " "memory to perform actions." |
|
LCRED-3-NOIPCMEM |
3-Error |
Cannot Allocate IPC memory to get message. |
Can't allocate memory to send redundancy control message. |
ha-lcred-infra |
"This is indicative of system memory " "shortage. The problem is likely unrelated to linecard " "redundancy. You should initiate recovery procedures as " "you would for any system that does not have sufficient " "memory to perform actions." |
|
LCRED-3-REMOVE_SLOT_OR_IF_FAILURE |
3-Error |
Removal of redundant interface caused an unexpected condition for i/f [chars]. |
While removing a redundant i/f possibly during redundant LC removal a SW bug was encountered. LC redundancy |
ha-lcred-infra |
"Verify LC Redundancy config with 'show " "redundancy linecard all' and 'show redundancy linecard group " "all'. Try to fix config with CLI. Open TAC case with above " "output as well as 'show run' 'show ver' and 'show redundancy " "history'." |
|
LCRED-3-SYNC_FAILURE_ISSU_NOT_OK |
3-Error |
Could not send checkpoint message during [chars] sync because issu infrastructure deemed ISSU state is incorrect. |
The ISSU infrastructure deemed the ISSU state of Linecard Redundancy's ISSU client peer is incorrect. |
ha-lcred-infra |
"If this message occurs once ISSU client " "negotiation is complete and system is up and running " "you need to reset the Standby RP. If it occurs during " "system bringup nothing needs to be done. The HA " "infrastructure should recover without intervention." |
|
LCRED-3-UNMAPPED_IFINDEX |
3-Error |
NULL/Invalid [chars] ifindex 0x[hec] downloaded for interface group number [dec]. |
The interface identifier specified for a member or virtual interface of a redundant interface group does not correspond to a known interface. |
ha-lcred-infra |
"Open a TAC case. Attach the output of " "'show redundancy linecard all' 'show redundancy " "linecard group all' and 'show redundancy linecard " "history'." |
|
LCRED-3-UPDATENOTSENT |
3-Error |
The update message was not sent to the linecards |
- |
- |
- |
|
LCRED-3-VIF_HWIDB_CREATE_FAIL |
3-Error |
Virtual hwidb creation failed from physical i/f [chars]: [chars]. |
Creation of virtual hwidb failed with specified error. |
ha-lcred-infra |
"Without the virtual hwidb VIF the i/f " |
|
LCRED-3-VIFTWICE |
3-Error |
LC: Request to add a second virtual interface to group [dec]. |
An attempt was made to add a virtual interface to a redundant interface group which already has a configured virtual interface. |
ha-lcred-infra |
"If this error was in response to a user " "command then check the command and try again if it " "appears correct. If the error seems to be from some " "undefined action then file a TAC case and attach the " "output from 'show redundancy linecard group all' and " "'show redundancy linecard history'." |
|
LCRED-4-LC_PLFM_SUPPRESS_SWITCHOVER |
4-Warning |
Platform has requested to temporarily suppress switchover for Line card redundancy group Group Index=[dec]. |
Attempt to switchover is suppress. This is just the informative message and not the error |
ha-lcred-infra |
"This indicates an informative error message " "during switchover.If secondary is never becoming Active for the " "failed or removed primary after Chassis reload then open a TAC " "case." |
|
LCRED-4-PARTIAL_CONFIG_LOSS |
4-Warning |
Partial redundancy config loss while configuring redundant interface [dec]/[dec] |
During system reload could not get hwidb for the Secondary i/f so the Secondary redundancy configuration will be lost. The Primary i/f will be Active if it was parsed correctly. |
ha-lcred-infra |
"Verify that Primary i/f is configured. " "Reconfigure Secondary i/f for redundancy." |
|
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-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-CONSISTENCY |
3-Error |
[chars] |
- |
mpls-ldp |
ACTION_COPY_REPORT_TDP |
|
LDP-3-CONSISTENCY |
3-Error |
[chars] |
- |
mpls-ldp |
ACTION_COPY_REPORT_TDP |
|
LDP-3-GENERAL |
3-Error |
[chars] |
- |
mpls-ldp |
ACTION_COPY_REPORT_TDP |
|
LDP-3-GENERAL |
3-Error |
[chars] |
- |
mpls-ldp |
ACTION_COPY_REPORT_TDP |
|
LDP-3-ISSU_XFORM |
3-Error |
ISSU [chars] transformation failed for msg type [dec][chars]. |
- |
- |
- |
|
LDP-3-ISSU_XFORM |
3-Error |
ISSU [chars] transformation failed for msg type [dec][chars]. |
- |
- |
- |
|
LDP-3-ISYNC |
3-Error |
[chars] |
An unexpected error happened in LDP-IGP Synchronization operation. |
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-3-ISYNC_CHKPT |
3-Error |
[chars]:: [chars] request failed [chars] |
An unexpected condition happened while uncheckpointing |
mpls-ldp |
ACTION_COPY_REPORT_TDP |
|
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-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-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-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-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-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-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-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-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-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_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-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-4-ADV |
4-Warning |
Label advertisement mode DU/DoD mismatch with peer [chars] resolved to [chars]. |
- |
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-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 |
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-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." |
|
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." |
|
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-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-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-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-ACL |
5-Notice |
mpls ldp advertise-labels has no effect for lc-atm |
EXPLANATION_ACL_TDP |
mpls-ldp |
"No action is required." |
|
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-5-ACL1 |
5-Notice |
mpls ldp advertise-labels has no effect for lc-atm |
EXPLANATION_ACL_TDP |
mpls-ldp |
ACTION_COPY_REPORT_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-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-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-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-5-GR |
5-Notice |
[chars] |
An informational LDP notice was generated for a Graceful Restart event. |
mpls-ldp |
LOG_STD_NO_ACTION |
|
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-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-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-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-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-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-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-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-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-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-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-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-SP |
5-Notice |
[chars] |
An informational LDP notice was generated for a Session Protection event. |
mpls-ldp |
LOG_STD_NO_ACTION |
|
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-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-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 |
|
LDPID-3-LCON |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
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-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." |
|
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." |
|
LES_FDDI-2-ILLEGAL |
2-Critical |
msgtxt_fddi_illegal |
This error message is displayed when the router does not have\n\ enough I/O memory to support a FDDI interface. The FDDI interface\n\ requires at least 4MB of I/O memory. |
mid-fddi |
"Install the required amount of I/O memory. For maximum performance\n\ Cisco reccommends installing 8Mb of I/O memory for a single FDDI NIM\n\ and 16MB of I/O memory if 2 FDDI NIMs are installed.\n\ \n\ With 4MB of I/O memory the system will create 256 FDDI buffers for a one\n\ FDDI interface or 384 buffers for two FDDI interfaces.\n\ \n\ With 8MB of I/O memory the system will create 512 FDDI buffers for\n\ either one or two FDDI interfaces.\n\ \n\ With 16MB of I/O memory the system will create 512 FDDI buffers for\n\ a one FDDI interface or 1024 buffers for two FDDI interfaces." |
|
LEX-3-NOTSENT |
3-Error |
Serial line down [chars] : [chars] not sent |
The serial line went down and the specified command was not sent to\n\ the LAN Extender. |
- |
"Determine why the serial line went down. For example was the cable\n\ was pulled or the LAN Extender powered off? The command will\n\ automatically be re-sent once the serial interface is operational." |
|
LEX-3-RCMDNAK |
3-Error |
[chars] : [chars] could not be processed by LAN Extender |
The LAN Extender could not process the command from the host router.\n\ Possible causes are:\n\\n\ The LAN Extender ran out of memory.\n\\n\ The message from the host router is malformed.\n\\n\ A request to write flash occurred while the LAN Extender was busy\n\ writing flash for a previous request.\n\\n\ The size of a file to be downloaded is greater than the amount of flash\n\ memory available. |
- |
"If the command was copy tftp lex unit-number or copy flash lex\n\ unit-number make sure that the correct file that is a FLEX image\n\ file is specified. Only a single copy request can be handled at one\n\ time. If the problem was caused by a temporary out-of-memory condition\n\ on the LAN Extender re-enter the command." |
|
LEX-3-RCMDREJ |
3-Error |
[chars] : [chars] could not be processed by LAN Extender |
The LAN Extender did not recognize the code for the specified remote\n\ command. This might occur if the user is running old LAN Extender\n\ software with newer host router software that has support for new LEX\n\ remote commands. |
- |
"Update the LAN Extender software." |
|
LEX-3-TIMEOUT |
3-Error |
Retry count exceeded for [chars] : [chars] |
The host router re-sent the given message as many times as specified\n\ in the lex retry-count command configuration variable without\n\ receiving an acknowledgment from the LAN Extender. At this point the\n\ host router gives up trying to send this particular remote command\n\ message. |
- |
"Use the LEDs on the LAN Extender to determine if it is operational.\n\ Confirm that the lex timeout configuration command is set appropriately\n\ for the speed of the link." |
|
LFD-2-AVL |
2-Critical |
[chars] [hec] |
AVL tree operation error |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-2-FPIHANDLER3 |
2-Critical |
[chars] [hec] [hec] [hec] |
FPI Handler error |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-BADEXEC |
3-Error |
Unexpected Code Execution: [chars] [dec] |
Unexpected Code Execution |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-BADFRRTYPE |
3-Error |
illegal frr type: [dec] |
FRR request type error |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-BADLABELADD |
3-Error |
Cannot add label - [chars]. |
Unable to create label due to reason given. |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-BADSHORTLABELADD |
3-Error |
Cannot add short label: path_idx [dec] moi_type [dec] |
Unable to create MFI feature space in FIB entry so unable to store short path extension information there. |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-BROKERINITFAIL |
3-Error |
Failed to initialise lte RP broker facility |
An internal software error occurred. |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-CHUNKMGR |
3-Error |
chunk mgr: [chars] 0x[hec] |
Chunk manager error |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-CHUNKMGRALLOC |
3-Error |
failed chunk alloc: [chars] |
Chunk alloc failed |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-CHUNKMGRDEALLOC |
3-Error |
failed chunk dealloc: [chars] |
Chunk free failed |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-CORRUPTED_PKT |
3-Error |
[chars] |
lfd received corrupted packet |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-EVTLOGBADSOURCE |
3-Error |
Illegal log event source: [dec] |
Illegal event found in log buffer |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-FIB_SRC |
3-Error |
Label [[dec]/[dec]] [chars] [chars] [chars] |
The fib entry could not be sourced for label in question. |
mpls-mfi |
"If there is no matching bug for this problem " "please collect the output of " "<CmdBold>show mpls forwarding-table internal<NoCmdBold> and " "<CmdBold>show ip route [vrf <name>] <prefix> <NoCmdBold> and " "the error message traceback and file a bug" |
|
LFD-3-FIBIPINVALID |
3-Error |
[chars] table: [dec] label: [dec] |
IP path information is invalid for the indicated label table entry |
mpls-mfi |
LOG_STD_SH_TECH_ACTION |
|
LFD-3-FIBIPINVALIDAF |
3-Error |
AF: [dec] [chars] table: [dec] label: [dec] |
IP path information AF is invalid for the indicated label table entry |
mpls-mfi |
LOG_STD_SH_TECH_ACTION |
|
LFD-3-FIBNONIPINVALID |
3-Error |
[chars] table: [dec] label: [dec] |
Non IP path information is invalid for the indicated label table entry |
mpls-mfi |
LOG_STD_SH_TECH_ACTION |
|
LFD-3-FPIHANDLER |
3-Error |
LFD SSS Handler: [chars] |
Error in fpi handler |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-FPITYPEWRONG |
3-Error |
Require fpi type [chars] get fpi type [chars] |
Unmatched FPI type |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-INTFDB |
3-Error |
intf db: [chars] [hec] |
Interface db error |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-INTFDB2 |
3-Error |
intf db: [chars] [hec] [hec] |
Interface db error |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-INVIPLABELTYPE |
3-Error |
Wrong label type [dec] for IP Label [dec] table [dec] prefix [chars] vrf [chars] |
Label type is invalid for the indicated label table entry |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release. If not gather the output of" " <CmdBold>show version<NoCmdBold> " "and <CmdBold>show running-config<NoCmdBold> and" "contact your Cisco technical support representative." |
|
LFD-3-INVLABELTYPE |
3-Error |
Wrong label type [dec] for non-ip LTE [dec]/[dec] |
Label type invalid for non-ip label table entry |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-INVLABELUPDTYPE |
3-Error |
Wrong label type [dec] for label [dec] table [dec] [chars] [chars] |
An invalid Label type was encountered during the specified operation |
mpls-mfi |
"If there is no matching bug for this problem " "please collect the output of <CmdBold>show mpls" " forwarding-table label <label> internal<NoCmdBold>" " and the error message traceback and file a bug" " report." |
|
LFD-3-INVPATHLBL |
3-Error |
[chars] [chars] |
An invalid outgoing label is attached to the prefix |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release. If not gather the output of" " <CmdBold>show version<NoCmdBold> " "and <CmdBold>show running-config<NoCmdBold> and" "contact your Cisco technical support representative." |
|
LFD-3-INVPEXTLEN |
3-Error |
[chars] path ext : attempt to decode beyond XDR buffer cp 0x[hec] cp_end 0x[hec] msg_type [dec] msg_size [dec] padding [dec] |
Accessing memory beyond XDR buffer length while decoding path extensions |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-INVPLIST |
3-Error |
Wrong path list type [dec] for label [dec]/[dec] [chars] |
The path list type is set incorrectly for the label in quest\n\ion |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-INVPLISTTYPE |
3-Error |
Wrong plist_type expected [dec] for [dec]/[dec] update was [dec] |
Rewrite PLISTTYPE invalid for non-ip label table entry |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-INVRWID |
3-Error |
Wrong rwid [dec] for non-ip LTE [dec]/[dec] |
Rewrite ID invalid for non-ip label table entry |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-KEY_DB_INSERTFAIL |
3-Error |
[chars] entry 0x[hec] existing 0x[hec] |
The element could not be inserted into the LFD's key database. |
mpls-mfi |
"If there is no matching bug for this problem " "please collect the output of " "<CmdBold>show mpls forwarding-table internal<NoCmdBold> and " "the error message traceback and file a bug" |
|
LFD-3-LABEL_BLOCK_CHUNK |
3-Error |
[chars] |
lfd label block chunk entry corrupted |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-LCXDRCLIENT |
3-Error |
LTE distribution client: [chars] |
An internal software error occurred. |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-LTABLEMEM |
3-Error |
Cannot allocate new mpls table [dec] of size [dec] needed for entry [dec] |
Not enough contiguous memory for mpls forwarding table |
mpls-mfi |
LOG_STD_REDUCE_ACTION |
|
LFD-3-NONIPINFO |
3-Error |
Non-ip info: [chars] |
An internal software error occurred. |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-NOOCE |
3-Error |
Attempt to get labels from OCE failed - [chars]. |
Calling function has provided insufficient information to get labels. |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-NORESOURCE |
3-Error |
[chars] [dec] |
Resource Failure: [chars] [dec] |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-NULLADJACENCY |
3-Error |
NULL Adjacency |
NULL adjacency encountered |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-NULLFIBIDB |
3-Error |
NULL FIB IDB: [chars] [dec] |
NULL FIB IDB encountered |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-OCE_CHAIN |
3-Error |
[chars] |
NULL OCE in chain |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-ORPHANLTE |
3-Error |
Label [dec]/[dec] plist [dec] LDM: 0x[hec] |
The LTE for the label was supposed to be deleted but is still present |
mpls-mfi |
"Collect the running configuration and output of " "<CmdBold>show mpls forwarding-table labels<NoCmdBold> " "<CmdArg>label-num<NoCmdArg> command and contact cisco " "technical service representative. " |
|
LFD-3-PATHEXTENCODE |
3-Error |
[chars] [chars] path list: %p path ext: %p |
MPLS path extensions could not be encoded for distribution |
mpls-mfi |
LOG_STD_SH_TECH_ACTION |
|
LFD-3-REWMGR |
3-Error |
Rewrite Manager: [chars] [hec] |
Rewrite Manager error |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-REWMGR2 |
3-Error |
[chars] 0x%08x 0x%08x |
Rewrite lookup failed due to FPI inconsisency |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-RPXDRCLIENT |
3-Error |
Invalid XDR Client: [chars] |
An internal software error occurred. |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-RUNNING_TIMER |
3-Error |
[chars] [dec] [chars] [dec] |
The MPLS forwarding entry for the specified label was deleted prior to the expiry of its associated timer |
mpls-mfi |
"If there is no matching bug for this problem " "please collect the output of <CmdBold>show mpls" " forwarding-table label <label> internal<NoCmdBold>" " and the error message traceback and file a bug" " report." |
|
LFD-3-SM |
3-Error |
[chars] [dec] |
State Machine error: [chars] [dec] |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-SMBADEVENT |
3-Error |
Unexpected event [chars] for state [chars] |
The LFD received an unexpected event for its state. The state of the LFD and the unexpected event are specified in the message text. |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-UNSUPPORT_OCE |
3-Error |
Not support - [chars] [dec] |
Unsupported OCE |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-UNSUPPORTED_XDR |
3-Error |
[chars] |
Decoding of an XDR message revealed data or format that is unsupported in the current release. |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-UPDATEHANDLER2 |
3-Error |
[chars] [hec] [hec] |
Error in update handler |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-UPDATEHANDLER3 |
3-Error |
[chars] [hec] [hec] [hec] |
Error in update handler |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-UPDATEHANDLERFPI |
3-Error |
No handler installed: fpi=[dec] handler type=[chars] |
No handler installed |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-3-XDRBADMAGIC |
3-Error |
xdr message for [chars] spilled out of allocated static storage |
An internal software error occurred. |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-4-FIB_SRC1 |
4-Warning |
Label [[dec]/[dec]] [chars] [chars] [chars] |
The fib entry could not be sourced for label in question. |
mpls-mfi |
"If there is no matching bug for this problem " "please collect the output of " "<CmdBold>show mpls forwarding-table internal<NoCmdBold> and " "<CmdBold>show ip route [vrf <name>] <prefix> <NoCmdBold> and " "the error message traceback and file a bug" |
|
LFD-4-NOFIBIDB |
4-Warning |
[chars] - ifnum [dec] |
fibidb missing on linecard |
mpls-mfi |
LOG_STD_RECUR_ACTION |
|
LFD-4-OWNCHANGED |
4-Warning |
Owner changed for [chars] [dec]/[dec] from [dec] to [dec] |
Label was previously installed by different installer |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-4-RE_ENTRANT |
4-Warning |
Re-entrancy detected: [chars] |
lfd non ip recalculation has re-entrancy |
mpls-mfi |
LOG_STD_ACTION |
|
LFD-4-UNSUPPORTEDRW |
4-Warning |
Unexpected rewrites seen where MPLS is not supported by platform for this slot |
MPLS is either not needed or not handled by the platform for this card and should not handle rewrites |
mpls-mfi |
LOG_STD_NO_ACTION |
|
LFD-6-RESOURCE |
6-Information |
[chars] |
MPLS software is disabled on LC |
mpls-mfi |
LOG_STD_NO_ACTION |
|
LI-3-MEM_INIT_FAILED |
3-Error |
Allocation of [chars] memory failed for LI |
LI Initialization of channel pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
LI-3-PKT_REPLICA_INIT_FAILED |
3-Error |
Register to Generic Packet Replication failed for LI |
LI Initialization of packet replication registration failed. |
cpp-ucode |
LOG_STD_ACTION |
|
LI-4-DEDICATED_MODE |
4-Warning |
Slot [dec] can not switch to LI dedicated mode because ther are SPAs in it. |
A SIP-400 can be configured as LI dedicated service card. But it can only switch to dedicated mode if all SPAs in it are un-plugged. Otherwise it will stay in non-dedicated mode. |
c7600-acl |
"Un-plug all the SPAs in the SIP-400. It will automatically switch " "to LI dedicated mode." |
|
LIBT2F-2-NEW_CONTEXT |
2-Critical |
A new text2fax context could not be created |
An internal error occurred in the initialization of the\n\text2fax engine. The fax transmission will be aborted. |
- |
LOG_STD_ACTION |
|
LIBT2F-3-ENGINE_FAILED |
3-Error |
The text2fax engine failed |
This occcurred most likely due to a memory limitation or\n\illegal data being passed into the text2fax engine. The fax\n\transmission will be aborted |
- |
LOG_STD_ACTION |
|
LIBT2F-3-GETBUFFER_FAILED |
3-Error |
Cannot allocate a packet\n\from shared memory |
The system is running low on packet memory. The fax cannot be\n\sent correctly. |
- |
LOG_STD_ACTION |
|
LIBT2F-3-NULL_BUFFER |
3-Error |
A text buffer is NULL |
An internal error occurred in the text buffer processing. The\n\fax tranmission be aborted. |
- |
LOG_STD_ACTION |
|
LIBTIFF-3-BAD_DIALPEER |
3-Error |
Invalid dial peer tag [dec] |
Invalid mmoip dial peer tag |
- |
LOG_STD_ACTION |
|
LIBTIFF-3-ENGINE_FAILED |
3-Error |
The tiff engine failed |
This occcurred most likely due to a memory limitation or\n\illegal data being passed into the tiff engine. The fax transmission will be aborted |
- |
LOG_STD_ACTION |
|
LIBTIFF-3-GETBUFFER_FAILED |
3-Error |
Cannot allocate a packet\n\from shared memory |
The system is running low on packet memory. The\n\fax cannot be sent correctly |
- |
- |
|
LIBTIFF-3-INVALID_BUFFER |
3-Error |
A tiff buffer is invalid |
An internal error occurred in the tiff buffer\n\processing. The fax tranmission will be aborted. |
- |
LOG_STD_ACTION |
|
LIBTIFF-3-NEW_CONTEXT |
3-Error |
A new tiff context could not be created |
An internal error occurred in the initialization of the\n\tiff engine. The fax transmission will be aborted. |
- |
LOG_STD_ACTION |
|
LIBTIFF-3-NULL_BUFFER |
3-Error |
A tiff buffer is NULL |
An internal error occurred in the tiff buffer\n\processing. The fax tranmission will be aborted. |
- |
LOG_STD_ACTION |
|
LIBTIFF-4-COPY_QUALITY |
4-Warning |
Bad copy quality on tty\n\[dec] |
Noisy phone lines or a bad modem caused this error |
- |
LOG_STD_RECUR_ACTION |
|
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-MEMORY |
3-Error |
[chars] |
License Agent subsystem has experienced a problem gettting the required\n\ memory to complete this operation. |
lic_agent |
"Check system memory for other memory allocation errors and contact\n\ Technical support for problem resolution. In the absence of IOS errors\ n\ 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." |
|
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." |
|
LICENSE_C5920-2-INIT_ERROR |
2-Critical |
Platform licensing initialization failure - licensing disabled. |
An error occurred during the initialization of the platform support for licensing. This will prevent licensing support from being enabled and prevent network interfaces from forwarding packets. |
SWR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
LICENSE_C5920-3-ACTIVATION_ERROR |
3-Error |
Activation of license for feature [chars] failed. Error code: [dec] |
An error occurred while attempting to activate a license that was just installed. |
SWR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
LICENSE_C5920-3-CAP_RETRIEVE_ERROR |
3-Error |
Error retrieving hardware capabilities data |
An error occurred while retrieving hardware capabilities data required for software licensing validation. |
SWR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
LICENSE_C5920-3-CSL_INIT_FAILED |
3-Error |
Error [dec] occurred while attempting to initialize the licensing infrastructure. |
An error occurred while attempting to initialize the IOS licensing infrastructure. |
SWR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
LICENSE_C5920-3-FEATURE_REGISTER_ERROR |
3-Error |
Error [dec] occurred while registering a feature. |
An error occurred while registering a licensed feature with the IOS licensing infrastructure. |
SWR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
LICENSE_C5920-3-INVALID_UDI_FORMAT |
3-Error |
Format of UDI retrieved from persistent storage is not correct. UDI: [chars] |
The Unique Device Identifier retrieved from persistent storage is not formatted properly. The proper format is <Product ID>:<Serial Number> |
SWR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
LICENSE_C5920-3-INVALID_UDI_PID |
3-Error |
PID in UDI retrieved from persistent storage not valid for image. PID: [chars] |
The Product ID in the Unique Device Identifier retrieved from persistent storage is not valid for this image. |
SWR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
LICENSE_C5920-3-LEGACY_LIC_NOT_SUPPORTED |
3-Error |
Legacy license file install is not supported when C5922 running within a Virtual Machine |
When C5922 is running on Virtual Machine to avoid duplicate licenses the Legacy license file install is not allowed. |
SWR_DDTS_COMPONENT |
"Enable smart licensing when C5922 running" "in a Virtual Machine" |
|
LICENSE_C5920-3-MODULE_REGISTER_ERROR |
3-Error |
Error [dec] occurred while registering module. |
An error occurred while registering the platform with the IOS licensing infrastructure. |
SWR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
LICENSE_C5920-3-NODELOCK_CHECK_ERROR |
3-Error |
Error occurred while validating the licensing node lock |
The node lock signature originally generated for this Cisco 592x installation does not match the signature generated during IOS initialization. Because of this any installed license is considered invalid. |
SWR_DDTS_COMPONENT |
"This error will occur when files associated with a " "Cisco 5922 installation are copied to another " "device. If this is not the case open a case with " "the Technical Assistance Center via the Internet " TAC_CASE_OPEN " or contact your Cisco technical " "support representative and provide the " "representative with the gathered information." |
|
LICENSE_C5920-3-NODELOCK_CHECK_ERROR_IN_VM |
3-Error |
Error occurred while validating the licensing node lock in Virtual Machine |
The node lock signature originally generated for this Cisco 592x installation does not match the signature generated during IOS initialization. Because of this any installed license will become invalid and new vUDI will get generated |
SWR_DDTS_COMPONENT |
"In VM This error is due to either vUDI" " or SMBIOS UUID change in cloned VM." "i.e. cloning after Cisco 5922 is installed." "if this is the case we can modify the .vmx file to retain" "the same UUID else need to install another licnese" "with newly generated vUDI. if nothing works then open" "a case with the Technical Assistance Center via" "the Internet TAC_CASE_OPEN or contact your Cisco technical" " support representative and provide the " "representative with the gathered information." |
|
LICENSE_C5920-3-NODELOCK_CREATE_ERROR |
3-Error |
Error occurred while creating a node lock |
An error occurred while attempting to create information needed for node locked licenses. |
SWR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
LICENSE_C5920-3-PERSISTENT_RETRIEVE_ERROR |
3-Error |
Error retrieving persistent data needed for licensing. |
An error occurred while retrieving data critical to software licensing from persistent storage. |
SWR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
LICENSE_C5920-3-PROCESS_INIT_FAILED |
3-Error |
Error occurred while attempting to create licensing process. |
An error occurred while attempting to create a process critical to licensing validation. |
SWR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
LICENSE_C5920-3-STORAGE_CREATE_ERROR |
3-Error |
Error occurred while creating license storage. [chars] |
An error occurred while creating storage for licensing information. |
SWR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
LICENSE_C5920-3-STORAGE_REGISTER_ERROR |
3-Error |
Error [dec] occurred while registering license storage. |
An error occurred while registering the licensing storage location with the IOS licensing infrastructure. |
SWR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
LICENSE_C5920-3-UDI_RETRIEVE_ERROR |
3-Error |
Error retrieving UDI. Error code: [dec] |
An error occurred while retrieving an existing Unique Device Identifier UDI from persistent storage. |
SWR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
LICENSE_C5920-3-UDI_STORE_ERROR |
3-Error |
Error storing UDI. Error code: [dec] |
An error occurred while storing a Unique Device Identifier UDI in persistent storage. |
SWR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
LICENSE_C5920-4-DEFAULT_BANDWIDTH_NOT_ACTIVATED |
4-Warning |
Unable to forward bandwidth to [dec] Kbps. Reason: [chars] |
Default bandwidth was not activated due to the condition noted in the message. |
SWR_DDTS_COMPONENT |
"Based on the message reason ensure that the " "conditions required to activate default bandwidth " "is met." |
|
LICENSE_C5920-4-HW_CAPABILITIES_INCREASE |
4-Warning |
Increase in hardware capabilities detected in use license no longer supported. |
An increase in the hardware capabilities was detected and has resulted in the deactivation of an in use license. The hardware capabilities increase has occurred since this license was allowed to be activated. One possibility is that an additional CPU was brought online after the license was installed and activated. |
SWR_DDTS_COMPONENT |
"Take one of the hardware CPUs offline." |
|
LICENSE_C5920-4-LOAD_THRESHOLD |
4-Warning |
Traffic load has reached [dec]%% of enforced rate. |
The router traffic rate has reached or exceeded the the reported percentage of the rate allowed by the installed license. |
SWR_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
LICENSE_C5920-4-NO_ACTIVE_LICENSE |
4-Warning |
No valid license was found. Traffic forwarding has been disabled |
A valid license was not found during system initialization. Traffic forwarding will not be enabled until a valid license is installed. |
SWR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
LICENSE_C5920-4-NOT_ACTIVATED |
4-Warning |
Installed license for feature [chars] was not placed in use. Reason: [chars] |
A valid license was installed but was not activated its state was not moved to 'In Use' due to the condition |
SWR_DDTS_COMPONENT |
"Based on the message reason ensure that the " "conditions required to activate the license are " "met. This may require the installation of a " "different license." |
|
LICENSE_C5920-4-RATE_EXCEEDED |
4-Warning |
Traffic load has exceeded the enforced rate. Rate is [dec] Mbps [dec]%% of enforced rate |
The total traffic load has exceeded the rate allowed by the installed license |
SWR_DDTS_COMPONENT |
"Install a license with a higher enforced rate." |
|
LICENSE_C5920-6-DEFAULT_BANDWIDTH_ACTIVATED |
6-Information |
Forwarding bandwidth limited to [dec] Kbps |
Default bandwidth activated its state is 'In Use' . Traffic forwarding will be rate limited |
SWR_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
LICENSE_C5920-6-HW_CAPABILITIES_DECREASE |
6-Information |
Decrease in hardware capabilities detected inactive license activated. |
An decrease in the hardware capabilities was detected and has resulted in the activation of an installed license that was not is use due to previous hardware capabilities. |
SWR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
LICENSE_C5920-6-LICENSE_ACTIVATED |
6-Information |
Installed license for feature [chars] now in use. Forwarding bandwidth limited to [dec] Mbps |
A valid license was installed and activated its state is 'In Use' . Traffic forwarding will be rate limited |
SWR_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
LICENSE_C5920-6-LICENSE_DEACTIVATED |
6-Information |
License for feature [chars] is no longer in use. |
The state of the feature license is now 'Not in Use'. |
SWR_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
LICENSE_C5920-6-UDI_GENERATED |
6-Information |
New UDI generated. UDI: [chars] |
A new Unique Device Identifier UDI was generated due to the absence of a stored UDI in persistent storage. |
SWR_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
LICENSE_C5920-6-UDI_RETRIEVED |
6-Information |
Existing UDI retrieved. UDI: [chars] |
An existing Unique Device Identifier UDI was retrieved from persistent storage. |
SWR_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
LICENSE_C5920-6-UNLIMITED_LICENSE_ACTIVATED |
6-Information |
Installed license for feature [chars] now in use. |
A valid license was installed and activated its state is 'In Use'. |
SWR_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
LICENSE-1-ENFORCEMENT |
1-Alert |
Feature [chars] [chars] running without a License. UDI=[chars] |
End User License Agreement was accepted on this device |
none |
"none" |
|
LICENSE-1-ENFORCEMENT |
1-Alert |
Feature [chars] [chars] running without a License. UDI=[chars] |
End User License Agreement was accepted on this device |
none |
"none" |
|
LICENSE-1-EXPIRED |
1-Alert |
License for feature [chars] [chars] has expired [chars]. UDI=[chars] |
License for the feature specified has expired |
ios-licensing |
"If this message recurs customer should buy the license from Cisco " "since feature will not run" |
|
LICENSE-1-EXPIRED |
1-Alert |
License for feature [chars] [chars] has expired [chars]. UDI=[chars] |
License for the feature specified has expired |
ios-licensing |
"If this message recurs customer should buy the license from Cisco " "since feature will not run" |
|
LICENSE-1-EXPIRING |
1-Alert |
License for feature [chars] [chars] will expire in [chars]. UDI=[chars] |
License for the feature specified will expire in the specified time. |
ios-licensing |
"If this message recurs customer should buy license for the feature" " from Cisco since feature will not run after license expiry" |
|
LICENSE-1-EXPIRING |
1-Alert |
License for feature [chars] [chars] will expire in [chars]. UDI=[chars] |
License for the feature specified will expire in the specified time. |
ios-licensing |
"If this message recurs customer should buy license for the feature" " from Cisco since feature will not run after license expiry" |
|
LICENSE-1-REQUEST_FAILED |
1-Alert |
License request for feature [chars] [chars] failed. UDI=[chars] |
Your system is trying to run a feature without a license. |
none |
"Please buy and install the license for the feature immediately" |
|
LICENSE-1-REQUEST_FAILED |
1-Alert |
License request for feature [chars] [chars] failed. UDI=[chars] |
Your system is trying to run a feature without a license. |
none |
"Please buy and install the license for the feature immediately" |
|
LICENSE-1-TRANSITION |
1-Alert |
EvalRightToUse License for feature [chars] [chars] will transition to RightToUse in [chars]. UDI=[chars] |
License for the feature specified will transition in the numer of days displayed in the syslog message. |
ios-licensing |
"Customer is expected to purchase this license if" " usage is planned beyond the trial period which" " expires in the number of days displayed in the syslog message." " This license will automatically convert to a Right to Use at" " the end of the trial period" |
|
LICENSE-1-TRANSITION_COMPLETE |
1-Alert |
RightToUse License for feature [chars] [chars] has become active. UDI=[chars] |
The transition of the license from EvalRightToUse to Right to Use RTU is completed |
ios-licensing |
"The trial period for this license has ended. This" " trial license has been automatically converted to" " a Right to Use License. Customer is required to" " purchase this license to continue usage" |
|
LICENSE-1-VALIDITY_ENDED |
1-Alert |
Feature [chars] [chars] [chars]. UDI=[chars] |
- |
- |
- |
|
LICENSE-1-VALIDITY_ENDED |
1-Alert |
Feature [chars] [chars] [chars]. UDI=[chars] |
- |
- |
- |
|
LICENSE-1-VALIDITY_ENDING |
1-Alert |
Feature [chars] [chars] will expire on [chars]. UDI=[chars] |
- |
- |
- |
|
LICENSE-1-VALIDITY_ENDING |
1-Alert |
Feature [chars] [chars] will expire on [chars]. UDI=[chars] |
- |
- |
- |
|
LICENSE-1-VALIDITY_EXT_ENDING |
1-Alert |
Feature [chars] [chars] in grace period. UDI=[chars] |
- |
- |
- |
|
LICENSE-1-VALIDITY_EXT_ENDING |
1-Alert |
Feature [chars] [chars] in grace period. UDI=[chars] |
- |
- |
- |
|
LICENSE-2-IPC_INIT |
2-Critical |
License IPC subsystem could not be initialized: [chars] |
License IPC subsystem could not be initialized. The reason for failure is displayed after : |
ios-licensing |
"If this error message recurs please copy the message and " "and contact the customer service See whether the system resources" "are available" |
|
LICENSE-2-IPC_INIT |
2-Critical |
License IPC subsystem could not be initialized: [chars] |
License IPC subsystem could not be initialized. The reason for failure is displayed after : |
ios-licensing |
"If this error message recurs please copy the message and " "and contact the customer service See whether the system resources" "are available" |
|
LICENSE-2-LIC_STORAGE |
2-Critical |
[chars] |
The IOS licensing subsystem does not have a primary storage |
ios-licensing |
"If this error message recurs please copy the message and " "and contact the customer service" |
|
LICENSE-2-LIC_STORAGE |
2-Critical |
[chars] |
The IOS licensing subsystem does not have a primary storage |
ios-licensing |
"If this error message recurs please copy the message and " "and contact the customer service" |
|
LICENSE-2-LIC_STORAGE_CORRUPT |
2-Critical |
[chars] UDI=[chars] |
The IOS licensing subsystem detected corrupted storage |
ios-licensing |
"If this error message occurs please reinstall all the licenses." "If you do not have the licenses please contact Cisco with the correct" "UDI to get all the licenses issued for this particular device" |
|
LICENSE-2-LIC_STORAGE_CORRUPT |
2-Critical |
[chars] UDI=[chars] |
The IOS licensing subsystem detected corrupted storage |
ios-licensing |
"If this error message occurs please reinstall all the licenses." "If you do not have the licenses please contact Cisco with the correct" "UDI to get all the licenses issued for this particular device" |
|
LICENSE-2-NO_MEM |
2-Critical |
No memory available for [chars] |
The IOS licensing subsystem could not obtain the memory it needed. |
ios-licensing |
"If this error message recurs attempt to reduce memory usage by " "reducing the number of router features or interfaces enabled. " "Alternatively add more memory. " "\n\nTo display total memory usage for a router enter " "<CmdBold>show memory summary<noCmdBold> at the privileged " "command line prompt. To display buffer usage enter " "<CmdBold>show buffers<noCmdBold> at the prompt." |
|
LICENSE-2-NO_MEM |
2-Critical |
No memory available for [chars] |
The IOS licensing subsystem could not obtain the memory it needed. |
ios-licensing |
"If this error message recurs attempt to reduce memory usage by " "reducing the number of router features or interfaces enabled. " "Alternatively add more memory. " "\n\nTo display total memory usage for a router enter " "<CmdBold>show memory summary<noCmdBold> at the privileged " "command line prompt. To display buffer usage enter " "<CmdBold>show buffers<noCmdBold> at the prompt." |
|
LICENSE-2-UDI_CHANGED |
2-Critical |
UDI of this instance changed from OLD: [chars]:[chars] to New: [chars]:[chars] |
License UDI has changed - caused mainly because of too many configuration changes. |
ios-licensing |
"show license udi history" |
|
LICENSE-2-UNRECOVERABLE |
2-Critical |
The IOS license storage on this device was not recovered. UDI=[chars] |
The IOS license storage on this device was not recovered |
ios-licensing |
"If this error message occurs please reinstall all the licenses." |
|
LICENSE-2-VLS_ERROR |
2-Critical |
'[chars]' failed with an error - rc = [dec] - '[chars]' |
The IOS licensing subsystem encountered an error with the VLS api |
ios-licensing |
"If this error message recurs please copy the message and " "and contact the customer service" |
|
LICENSE-2-VLS_ERROR |
2-Critical |
'[chars]' failed with an error - rc = [dec] - '[chars]' |
The IOS licensing subsystem encountered an error with the VLS api |
ios-licensing |
"If this error message recurs please copy the message and " "and contact the customer service" |
|
LICENSE-3-BULK_SYNC_FAILED |
3-Error |
License bulk sync operation [chars] for feature [chars] [chars] failed on standby rc=[chars] |
- |
- |
- |
|
LICENSE-3-BULK_SYNC_INFO |
3-Error |
License bulk sync operation [chars] for feature [chars] [chars] Info on standby rc=[chars] |
Licensing is experiencing Errors when performing bulk sync |
ios-licensing |
"show license" |
|
LICENSE-3-FEATURE_INCONSISTENT |
3-Error |
License mismatch for feature [chars] [chars]: Active has [chars] and standby has [chars] |
Licensing is experiencing Errors when performing consistency checker |
ios-licensing |
"show license" |
|
LICENSE-3-IMPLICIT_LIC |
3-Error |
[chars] |
The IOS licensing subsystem encountered an error while initializing/handling the implicit licenses |
ios-licensing |
"If this error message recurs please copy the message and " "and contact the customer service" |
|
LICENSE-3-IMPLICIT_LIC |
3-Error |
[chars] |
The IOS licensing subsystem encountered an error while initializing/handling the implicit licenses |
ios-licensing |
"If this error message recurs please copy the message and " "and contact the customer service" |
|
LICENSE-3-IPC_ERROR |
3-Error |
[chars][chars] [hec] rc:[chars] |
Licensing is experiencing errors when communicating to Line Cards using IPC |
ios-licensing |
"show ipc ports" |
|
LICENSE-3-IPC_ERROR |
3-Error |
[chars][chars] [hec] rc:[chars] |
Licensing is experiencing errors when communicating to Line Cards using IPC |
ios-licensing |
"show ipc ports" |
|
LICENSE-3-IPC_PORT |
3-Error |
License [chars] IPC port [chars] failed: [chars] |
License IPC port could not be created. The reason for failure is displayed after : |
ios-licensing |
"If this error message recurs please copy the message and " "and contact the customer service See whether the system resources" "are available" |
|
LICENSE-3-IPC_PORT |
3-Error |
License [chars] IPC port [chars] failed: [chars] |
License IPC port could not be created. The reason for failure is displayed after : |
ios-licensing |
"If this error message recurs please copy the message and " "and contact the customer service See whether the system resources" "are available" |
|
LICENSE-3-ISSU_ERR |
3-Error |
[chars] error:[dec] |
Licensing is experiencing ISSU Errors |
ios-licensing |
"show ipc ports" |
|
LICENSE-3-ISSU_ERR |
3-Error |
[chars] error:[dec] |
Licensing is experiencing ISSU Errors |
ios-licensing |
"show ipc ports" |
|
LICENSE-3-ISSU_MTU |
3-Error |
Client id:[dec] MTU failed error:[dec] |
Licensing is experiencing Errors when performing ISSU GET MTU during a transmit operation |
ios-licensing |
"show issu nego" |
|
LICENSE-3-ISSU_MTU |
3-Error |
Client id:[dec] MTU failed error:[dec] |
Licensing is experiencing Errors when performing ISSU GET MTU during a transmit operation |
ios-licensing |
"show issu nego" |
|
LICENSE-3-ISSU_RCV |
3-Error |
Client id:[dec] type = [dec] receive failed error:[dec] |
Licensing is experiencing Errors when performing ISSU Transformation during a receive operation |
ios-licensing |
"show ipc ports" |
|
LICENSE-3-ISSU_RCV |
3-Error |
Client id:[dec] type = [dec] receive failed error:[dec] |
Licensing is experiencing Errors when performing ISSU Transformation during a receive operation |
ios-licensing |
"show ipc ports" |
|
LICENSE-3-ISSU_XMIT |
3-Error |
Client id:[dec] type = [dec] xmit failed error:[dec] |
Licensing is experiencing errors when performing ISSU Transformation during a transmit operation |
ios-licensing |
"show ipc ports" |
|
LICENSE-3-ISSU_XMIT |
3-Error |
Client id:[dec] type = [dec] xmit failed error:[dec] |
Licensing is experiencing errors when performing ISSU Transformation during a transmit operation |
ios-licensing |
"show ipc ports" |
|
LICENSE-3-LIC_PROCESS_CREATION_FAILED |
3-Error |
[chars] |
The IOS licensing subsystem was unable to create a process |
ios-licensing |
"If this error message recurs please copy the message and " "and contact the customer service See whether the system resources" "are available" |
|
LICENSE-3-LIC_PROCESS_CREATION_FAILED |
3-Error |
[chars] |
The IOS licensing subsystem was unable to create a process |
ios-licensing |
"If this error message recurs please copy the message and " "and contact the customer service See whether the system resources" "are available" |
|
LICENSE-3-SLAVE_REGISTER |
3-Error |
License Slave device registration failed : [chars] |
License Slave registration failed. The reason for failure is displayed after : |
ios-licensing |
"If this error message recurs please copy the message and " "and contact the customer service See whether the system resources" "are available" |
|
LICENSE-3-SLAVE_REGISTER |
3-Error |
License Slave device registration failed : [chars] |
License Slave registration failed. The reason for failure is displayed after : |
ios-licensing |
"If this error message recurs please copy the message and " "and contact the customer service See whether the system resources" "are available" |
|
LICENSE-3-SYNC_FAILED |
3-Error |
License command [chars] for feature [chars] [chars] failed on standby rc=[chars] |
Licensing is experiencing Errors when performing incremental sync |
ios-licensing |
"show license" |
|
LICENSE-4-LIC_AGENT_OFF |
4-Warning |
License Agent is turned off. UDI=[chars] |
The License Agent on this device is not running |
none |
"Please check the device configuration " "if you need to enable it." |
|
LICENSE-4-LIC_AGENT_OFF |
4-Warning |
License Agent is turned off. UDI=[chars] |
The License Agent on this device is not running |
none |
"Please check the device configuration " "if you need to enable it." |
|
LICENSE-4-PRECEDENCE |
4-Warning |
Setting precedence for feature [chars] failed with error : [dec] |
A license is revoked from the system |
none |
"This is just an informational message to" " log a message when a license has been revoked" |
|
LICENSE-4-PRECEDENCE |
4-Warning |
Setting precedence for feature [chars] failed with error : [dec] |
A license is revoked from the system |
none |
"This is just an informational message to" " log a message when a license has been revoked" |
|
LICENSE-4-UDI_MISMATCH |
4-Warning |
The source license udi[chars]:[chars] differs from the platform udi[chars]:[chars] please save the running config. |
The source license udi mismatches with the platform udi |
none |
"Please save running-config." |
|
LICENSE-4-UDI_MISMATCH |
4-Warning |
The source license udi[chars]:[chars] differs from the platform udi[chars]:[chars] please save the running config. |
The source license udi mismatches with the platform udi |
none |
"Please save running-config." |
|
LICENSE-6-COUNT |
6-Information |
Feature [chars] [chars] license count changed from [dec] to [dec]. |
The feature's maximum licensable count has changed |
none |
"This is just an informational message to" "denote count change for particular feature" |
|
LICENSE-6-COUNT |
6-Information |
Feature [chars] [chars] license count changed from [dec] to [dec]. |
The feature's maximum licensable count has changed |
none |
"This is just an informational message to" "denote count change for particular feature" |
|
LICENSE-6-EULA_ACCEPT_ALL |
6-Information |
The Right to Use End User License Agreement is accepted |
This message indicates that the customer has configured 'license agree end user agreement' in the system to indicate that EULA for all licenses are accepted. And that they accept the Right to use End Use License Agreement found at: http://www.cisco.com/en/US/docs/general/warranty/English/EU1KEN_.html |
ios-licensing |
- |
|
LICENSE-6-RECOVERED |
6-Information |
The IOS license storage on this device was recovered. UDI=[chars] |
The IOS license storage on this device was recovered |
ios-licensing |
"none" |
|
LICENSE-6-RECOVERED |
6-Information |
The IOS license storage on this device was recovered. UDI=[chars] |
The IOS license storage on this device was recovered |
ios-licensing |
"none" |
|
LICENSE-6-UNRECOVERABLE |
6-Information |
The IOS license storage on this device is being corrected. UDI=[chars] |
The IOS license storage on this device is being corrected |
ios-licensing |
"If this message occurs please ignore." |
|
LICENSE-6-VIOLATION |
6-Information |
Feature [chars] [chars] count violation - count = [dec] usage count = [dec]. |
The feature's count is less than the current usage count |
none |
"This is just an informational message to" "denote count change for particular feature" |
|
LICENSE-6-VIOLATION |
6-Information |
Feature [chars] [chars] count violation - count = [dec] usage count = [dec]. |
The feature's count is less than the current usage count |
none |
"This is just an informational message to" "denote count change for particular feature" |
|
LICENSING-6-LIC_MISMATCH |
6-Information |
Configured license image level [chars] does not match the current level [chars]. Reload is required to bring the system up in [chars] |
During boot-up of system the configured license image level might mismatch with the current level. This could happen when customer copy a different startup-config to the system. |
polaris-license |
"Reload is required to bring the system up in " "the configured license image level." |
|
LIIN-3-SET_ACCESS_FAIL |
3-Error |
Installing LIIN interface access control failed |
This error happens when IOS failed to set the access control function for the LIIN possibly due to IOSd out of memory or corruption. In this case LIIN interface setup will not proceed will not operate properly and cannot be recovered. Persistent access features and interactive commands will not work. |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
LIIN-3-SET_TABLEID_FAIL |
3-Error |
Installing [chars] LIIN interface tableid failed |
This error happens when IOS failed to set tableid into linux kernel possibly due to either IOSd or kernel out of memory or corruption. In this case LIIN interface will not have VRF installed for the associated address family. The LIIN interface will not operate properly and cannot be recovered. Persistent access features and interactive commands will not work. |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
LIIN-3-VRFADD_FAIL |
3-Error |
Problem creating vrf |
The LIIN config process failed to allocate a mandatory iVRF. The LIIN interface will not operate properly and cannot be recovered. Persistent access features and interactive commands will not work. |
- |
LOG_STD_ACTION |
|
LIIN-3-VRFMODIFY_FAIL |
3-Error |
Problem adding LIIN interface to vrf table |
The LIIN config process failed to assign the LIIN interface to its mandatory iVRF. The LIIN interface will not operate properly and cannot be recovered. Persistent access features and interactive commands will not work. |
- |
LOG_STD_ACTION |
|
LIIN-6-TELNET_ALLOWED |
6-Information |
Telnet access allowed due to romvar: SR_INIT_SHELL |
Telnet from shell to IOS allowed because rommon variable SR_INIT_SHELL is set with value aux_do_system_shell. Remove this value from SR_INIT_SHELL or unset SR_INIT_SHELL to disable the telnet access |
- |
LOG_STD_NO_ACTION |
|
LINEPROTO-5-UPDOWN |
5-Notice |
Line protocol on Interface [chars] changed state to [chars] |
The data link level line protocol changed state. |
- |
LOG_STD_NO_ACTION |
|
LINK-0-REENTER |
0-Emergency |
MSG_PROCESS | MSG_TRACEBACK |
- |
- |
- |
|
LINK-2-BADVCALL |
2-Critical |
Interface [chars] undefined entry point |
An internal software error occurred. The high-level system code tried\n\ to use an unimplemented entry point with the virtual interface\n\ descriptor block IDB driver. |
- |
LOG_STD_ACTION |
|
LINK-2-INTVULN |
2-Critical |
MSG_PROCESS | MSG_TRACEBACK |
- |
- |
- |
|
LINK-2-LINEST |
2-Critical |
No linestate vector for [chars] |
An internal software inconsistency occurred. |
- |
LOG_STD_ACTION |
|
LINK-2-NOSOURCE |
2-Critical |
Source idb not set |
An internal software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
LINK-3-BADENCAP |
3-Error |
Interface [chars] Bad encapsulation code [dec] |
- |
- |
- |
|
LINK-3-BADMACREG |
3-Error |
Interface [chars] non-existent MACADDR registry for link [dec] |
An attempt to map a network level address to a MAC level address\n\ failed. |
- |
LOG_STD_ACTION |
|
LINK-3-BOGUSENCAP |
3-Error |
msgtxt_badencap |
A serial interface has been configured with an unknown\n\ encapsulation. |
- |
LOG_STD_ACTION |
|
LINK-3-COMPREG |
3-Error |
Interface [chars] non-existent decompression registry. |
A software or hardware error occurred. |
- |
LOG_STD_ACTION |
|
LINK-3-FCS_ERROR |
3-Error |
[chars] [chars] [chars] [chars] |
The FCS Error rate exceeds the configured threshold |
- |
LOG_STD_ACTION |
|
LINK-3-IDBLISCRE |
3-Error |
Unable to create [chars] interface list |
This message indicates an internal software error. |
- |
LOG_STD_ACTION |
|
LINK-3-IDBLISINS |
3-Error |
Not able to insert interface [chars] into [chars] list |
This message indicates an internal software error. |
- |
LOG_STD_ACTION |
|
LINK-3-LINK_FAULT |
3-Error |
[chars] [chars] [chars] [chars] |
The link state for the port is down |
- |
LOG_STD_ACTION |
|
LINK-3-TOOSMALL |
3-Error |
Interface [chars] Output runt packet of [dec] bytes |
An output packet was detected that was smaller than the minimum\n\ allowable datagram size. An error in another driver or an error in \n\ the system software probably triggered this error message. |
- |
LOG_STD_ACTION |
|
LINK-3-UPDOWN |
3-Error |
Interface [chars] changed state to [chars] |
The interface hardware went either up or down. |
- |
"If the state change was unexpected confirm the configuration settings\n\ for the interface." |
|
LINK-4-BADQID |
4-Warning |
Interface [chars] bad output queue ID specified [dec]. |
This message indicates an internal software error. |
- |
LOG_STD_ACTION |
|
LINK-4-BRIDGECONFLICT |
4-Warning |
Interface [chars] encapsulated BPDU recvd from [enet] |
An FCIT running in nonencapsulating transparent mode detected an FDDI\n\ bridge running in encapsulation mode on the same fiber. This is an\n\ unstable situation and should be corrected. The incoming interface is\n\ displayed along with the FDDI MAC address in standard form. |
- |
"Upgrade the errant interface to full transparent mode. Copy the error\n\ message exactly as it appears and report it to your Cisco\n\ technical support representative." |
|
LINK-4-FDDISTAT |
4-Warning |
Interface [chars] FDDI state [chars] detected |
There was a state change on the FDDI ring. |
- |
LOG_STD_ACTION |
|
LINK-4-NOMAC |
4-Warning |
A random default MAC address of [enet] has\n been chosen. Ensure that this address is unique or specify MAC\n addresses for commands such as 'novell routing' that allow the\n |
An addressing inconsistency occurred. |
- |
"Make sure that this address is unique or specify MAC addresses for\n\ commands such as novell routing that allow the use of this address as a\n\ default." |
|
LINK-4-NOSSB |
4-Warning |
SSB deleted with timer running |
An internal software error occurred.\n Problem has been corrected and router operation\n has not been impaired. |
- |
LOG_STD_ACTION |
|
LINK-4-TOOBIG |
4-Warning |
Interface [chars] Output packet size of [dec] bytes too big |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
LINK-5-BOOTP |
5-Notice |
[chars] address [inet] resolved by [inet] |
An interface's IP address was successfully learned dynamically through\n\ BootP. The first address is the learned IP address. The second IP\n\ address is the IP address of the BootP server that provided the\n\ information. |
- |
LOG_STD_ACTION |
|
LINK-5-CHANGED |
5-Notice |
Interface [chars] changed state to [chars] |
The interface hardware changed state. |
- |
LOG_STD_ACTION |
|
LINK-5-LOOPSTATUS |
5-Notice |
Interface [chars] [chars] |
The interface entered or exited loopback. |
- |
LOG_STD_ACTION |
|
LINK-5-RARP |
5-Notice |
[chars] address [inet] resolved by [inet] |
- |
- |
LOG_STD_ACTION |
|
LINK-5-REMLOOP |
5-Notice |
Interface [chars] remote loop [chars] [chars] |
The interface entered or exited a remote loopback. |
- |
LOG_STD_ACTION |
|
LINK-5-SLARP |
5-Notice |
[chars] address [inet] resolved by [inet] |
- |
- |
LOG_STD_ACTION |
|
LINK-6-BERTMSGS |
6-Information |
[chars] |
BERT related information messages. |
- |
LOG_STD_ACTION |
|
LINK-6-BERTSTATUS |
6-Information |
Interface [chars] [chars] |
BERT is completed for this interface. |
- |
LOG_STD_ACTION |
|
LINK-6-DOWNSHIFT |
6-Information |
Experienced Channel Quality Impairment on interface [chars] Downshifting Speed to [chars] |
Speed Downshift Detected. |
firmware |
"No action is required." |
|
LISP_PROXY-3-PROXY_IPC_GET_STATS_FAILED |
3-Error |
lisp proxy get stats failed for type[[chars]] idx = [dec] ppe_addr[0x[hec]]. |
Getting lisp default entry stats failed. |
cpp-ucode |
LOG_STD_ACTION |
|
LISP_PROXY-3-PROXY_IPC_INIT_FAILED |
3-Error |
lisp proxy init failed rc = [dec] |
IPC handler initialization failed. |
cpp-ucode |
LOG_STD_ACTION |
|
LISP_PROXY-3-PROXY_IPC_PACKET_ALLOCATION_FAILED |
3-Error |
lisp proxy alloc reply pak failed |
Failed to allocate packet buffer for IPC |
cpp-ucode |
LOG_STD_ACTION |
|
LISP_PROXY-3-PROXY_IPC_PACKET_SEND_FAILED |
3-Error |
lisp proxy send failed rc = [dec] |
Failed to send IPC packet. |
cpp-ucode |
LOG_STD_ACTION |
|
LISP_PROXY-3-PROXY_IPC_REQUEST_MSG_INVALID |
3-Error |
lisp proxy request msg invalid. |
Failed to get lisp default entry stats req from IPC packet. |
cpp-ucode |
LOG_STD_ACTION |
|
LISP_PROXY-4-PROXY_IPC_INVALID_MSG |
4-Warning |
invalid lisp proxy msg [dec] |
Received an invalid IPC messages subtype. |
cpp-ucode |
LOG_STD_ACTION |
|
LISP-3-MAP_CACHE_EXTRANET_SITE_REG_ERR |
3-Error |
Config map-cache site-registration should not be configured on lisp extranet instance [dec] |
Config map-cache site-registration is not supported on lisp instances part of extranet |
- |
"Remove config map-cache site-registration from " "lisp instances part of extranet. Consider using " "config map-cache extranet-registration under " "provider instance" |
|
LISP-3-TCP_AO_KEYCHAIN_CHANGED |
3-Error |
TCP Authentication Option keychain [chars] no longer valid |
This message is a warning that the TCP keychain configuration was changed while it was in use. |
- |
"The TCP keychain configuration was changed while " "being used by LISP session. Correct the " "configuration to restore session" |
|
LISP-3-TCP_MSG_TOO_LARGE |
3-Error |
Received too large TCP message type [dec] length [dec] > [dec] resetting the session |
This message is a warning that a too large TCP message is received. LISP resets the session |
- |
- |
|
LISP-4-ASSERT |
4-Warning |
Internal LISP error [chars][chars]\n |
LISP control plane code execution encountered an unexpected condition. |
lisp |
"show {ip | ipv6} lisp" |
|
LISP-4-CEF_DISABLED |
4-Warning |
Disabling [chars] CEF will impact configured LISP functionality. |
CEF has been disabled whilst LISP has configuration which depends on CEF being enabled. |
- |
"Re-enable CEF using the command " "<CmdBold>{ip|ipv6} cef [distributed]<noCmdBold>." |
|
LISP-4-CONFIG_INVALID_PREFIX_SOURCE_WITH_DEFAULT_ETR |
4-Warning |
This message is a warning that the eid-prefix [chars] being used by default-etr is imported into LISP by another configuration. |
PxTR doesn't allow the eid-prefix that is being used by default-etr to be imported into LISP by another source. |
- |
"Remove configuration causing conflict for the eid-" "prefix source from the PxTR/xTR" |
|
LISP-4-CONFIGURED_MAX_LOCAL_HOSTS_LIMIT_REACHED |
4-Warning |
The LISP [chars] configured Local EID limit [dec] has been reached. |
- |
- |
- |
|
LISP-4-DATABASE_MAPPING_LIMIT_DYNAMIC_REACHED |
4-Warning |
The LISP dynamic database-mapping limit[chars] [dec]/[dec] dynamic entries for eid-table [chars] has been reached. |
- |
- |
- |
|
LISP-4-DATABASE_MAPPING_PLATFORM_LIMIT_REACHED |
4-Warning |
The LISP database-mapping platform limit of [dec] has been reached. Current count is [dec]. |
This message is a warning that the local database size has hit the platform limit. The limit may be reached during normal operation if a xTR discovers a large number of dynamic hosts in the EID-prefix ranges enabled for dynamic learning. If the dynamic local database size limit is reached new hosts will not be discovered. It is worth noting that it is normal for the local database to have a limit for dynamic entries for example to set an upper limit on the amount of memory required. To diagnose this issue it may be helpful to inspect the local database using show ip[v6] lisp [eid-table <vrf>] database. The entries can also be cleared with clear lisp[eid-table <vrf>] dynamic-eid. |
- |
"If this warning persists and traffic drops are " "experienced please contact TAC." |
|
LISP-4-DYNAMIC_RSRC_PLATFORM_LIMIT_REACHED |
4-Warning |
The LISP [chars] EID platform limit [dec] percent has been reached. |
This message is a warning that the EID resource size has hit the platform limit. The limit may be reached during normal operation if a xTR has a large number of Local hosts/and or Remote map-caches entries. To diagnose this issue it may be helpful to inspect the platform resource usage using show lisp platform |
- |
"If this warning persists traffic drops can be " "experienced please contact TAC." |
|
LISP-4-DYNAMIC_RSRC_PLATFORM_WARNING_LIMIT_REACHED |
4-Warning |
The LISP [chars] EID warning limit greater than [dec] percent for platform |
This message is a warning that the EID resource size has hit the platform warning limit. The limit may be reached during normal operation if a xTR has a large number of Local hosts/and or Remote map-caches entries. To diagnose this issue it may be helpful to inspect the platform resource usage using show lisp platform |
- |
"If this warning persists traffic drops can be " "experienced please contact TAC." |
|
LISP-4-EXTRANET_OVERLAPPING_PREFIX |
4-Warning |
[dec] Map-Server detected overlapping prefix [chars] in extranet [chars] |
An extranet prefix configured or dynamically learnt on one extranet IID cannot overlap with a prefix in another extranet. |
- |
"If it is not for specific purposes like firewall " "or service insertion please remove configuration " "causing overlapping extranet prefix to be learnt " "with different instance ID or in a different " "extranet." |
|
LISP-4-INTERRUPT |
4-Warning |
Internal LISP error during interrupt [chars] |
- |
- |
- |
|
LISP-4-LISP_TOP_RLOC_AUDIT |
4-Warning |
[dec] router lisp instances [router lisp [chars]] are not |
This message is a warning that the one or more configured router lisp <x> instances are missing the locator-table config. Without this locator-table the lisp instance is not operational. |
- |
"The operator must configure the " "locator-table below the router lisp instances or " |
|
LISP-4-LOCAL_EID_MAP_REGISTER_FAILURE |
4-Warning |
[dec] IID [dec] Failed to receive map-notify from map-server [chars] |
This implies the map-sever may not have received/processed the map-register from this ETR or the map-server failed to successfully deliver the map-notify to the ETR. |
- |
"Ensure map-server is configured to accept " "map-register for this EID prefix ETR is " "configured with the correct map-server key and " "bidirectional traffic can flow between ETR and " "map-server." |
|
LISP-4-LOCAL_EID_NO_ROUTE |
4-Warning |
No route to local EID database prefix [chars]. |
There is no RIB route that covers or is a more specific of the configured local EID database prefix. This means that the ETR will not be able to forward decapsulated packets to their destination. |
- |
"Check the network connectivity and routing " "configuration within the LISP site and re-establish " "a route to destinations covered by the configured " "EID prefix." |
|
LISP-4-LOCAL_EID_RLOC_INCONSISTENCY |
4-Warning |
Inconsistent LISP routing locator configuration detected in the local EID database for instance-ID [dec] [chars] address family. |
All the LISP local EID prefixes for an address family must be configured with the same set of routing locators. LISP detected that there are routing locators configured on some local EID prefixes and not on other local EID prefixes of the same address family. |
- |
"Issue the <CmdBold>show {ip | ipv6} lisp database" "<noCmdBold> command and look for routing " "locators marked as <CmdBold>missing<noCmdBold>. " "Configure the missing routing locators for the " "remaining local EID prefixes. If a routing locator" "must not be used for inbound traffic to a local " "EID prefix then a priority of 255 can be " "specified." |
|
LISP-4-MAP_CACHE_CREATE_FAILURE |
4-Warning |
Failed to create map cache entry for EID prefix [chars] under Lisp instance-id [dec] Cause: [chars] |
This message is a notification that the map cache creation for an EID prefix has failed. Probable reasons could be failure to create or lookup a corresponding map cache entry due to inconsistent states low memory conditions or commonly if map-cache-limit is explicitly set to a low value. If the cache size limit is reached new entries will replace old/inactive ones as required. If the map-cache limit is set too low actively used EID-to-RLOC mappings may be replaced continously which causes traffic to be dropped while these mappings are re- |
- |
"If this limit is reached and traffic drops are " "experienced consider re-evaluating the map-cache " "limit and configure a higher limit." |
|
LISP-4-MAP_CACHE_WARNING_THRESHOLD_REACHED |
4-Warning |
The LISP map-cache limit warning threshold [dec]/[dec] entries for instance-id [dec] has been reached. |
- |
- |
- |
|
LISP-4-MAP_REGISTER_WARNING |
4-Warning |
Map-Server received registration for a /0 subnet which specifies an attempt to register all prefix range |
This message is a warning that the Map-Server received a registration message for a /0 subnet. An XTR may be attempting to receive all traffic of the network |
- |
"Check the router lisp configuration on XTR. " "Consider removing/changing the /0 eid-prefix in " "database mapping entry on XTR" |
|
LISP-4-MAP_REQUEST_NO_USABLE_ITR_RLOC |
4-Warning |
IID [dec] No usable ITR RLOC unable to send map-request. |
This message is a warning that the device does not have any usable ITR RLOC for map-request transmission. When this condition occurs new traffic is impacted. |
- |
"Verify there is any least one static local EID " "configured or a dynamic EID is detected or " "\"map-request itr-rlocs\" is configured or the " "device is configured as a proxy-itr. If the " "message persists then verify the RLOC is local " "and in UP state." |
|
LISP-4-MAP_SERVER_CONVERGING |
4-Warning |
IID [dec] Map-server is converging unable to send negative map-reply. |
This message is a warning that the map-server is converging after reload or HA event. During this time the map-server would not send negative map-reply hence traffic would be impacted. It typically takes 3-6 minutes for the map-server to converge. |
- |
"Ensure there is at least two map-servers " "in the network for redundancy. When reload is " "required then ensure the peering map-server is " "fully converged before triggering reload." |
|
LISP-4-MAP_SERVER_EXTRANET_EID_PREFIX_PLATFORM_LIMIT |
4-Warning |
Map-server Extranet policy EID platform limit for [chars] is reached [dec]: prefix [chars] in [dec] IID [dec] Extranet [chars] blocked |
- |
- |
- |
|
LISP-4-MAP_SERVER_SITE_EID_PREFIX_LIMIT |
4-Warning |
[dec] IID [dec] Site [chars] Map-server site dynamic EID prefix |
Map-server cannot create any more dynamic EID prefix entry result accept-more-specifics. Consequently the map-register is not processed. |
- |
"Increase the map-server dynamic EID prefix " "entry limit." |
|
LISP-4-MAP_SERVER_SITE_EID_PREFIX_LIMIT_CONFIG |
4-Warning |
Configured limit [dec] is less than current EID prefix count |
The newly configured limit is less than the current EID prefix count. |
- |
"Issue \"clear lisp site\" for limit to " "take effect." |
|
LISP-4-MAP_SERVER_SITE_EID_PREFIX_LIMIT_THRESHOLD |
4-Warning |
[dec] IID [dec] Site [chars] Map-server site dynamic EID prefix |
Dynamic EID prefix entry count has reached or exceeded the configured threshold. This is used to warn the adminstrator that corrective action may need to be taken to avoid reaching the map-server EID prefix limit. |
- |
"No immediate action is required unless the " "entry count is very close to the configured " "limit at which point the limit on the map-server " "needs to be adjusted." |
|
LISP-4-MAP_SERVER_SITE_EID_PREFIX_PLATFORM_LIMIT |
4-Warning |
Map-server site EID prefix entry platform limit for [chars] is reached [dec]: prefix [chars] in [dec] IID [dec] Site [chars] blocked |
- |
- |
- |
|
LISP-4-PETR_EXTRANET_LOCATOR |
4-Warning |
[dec] Map-Resolver detected the PETR locator [chars] with |
Map resolver does not allow PETR locator's instance outside of the instances configured as extranet Policy |
- |
"Remove configuration causing locator-set with " "extranet prefix to be advertised to instances " "outside of extranet." |
|
LISP-4-REMOTE_EID_EVICTION_TRIGGERED |
4-Warning |
The LISP [chars] EID platform limit reached. Remote EID eviction triggered to make space for Local EIDs. The eviction will continue till the Local EID Reserved [dec] percentage is reached. |
- |
- |
- |
|
LISP-4-REMOTE_EID_OVERSUBSCRIBED |
4-Warning |
Created map cache entry for EID prefix [chars] under Lisp instance-id [dec] Cause: [chars] |
This message is a notification that the must have map cache for an EID prefix has been created. The platform may not accept this map-cache as its limit may have exceeded. To diagnose this issue it may be helpful to inspect the sources of map-cache using show lisp instance-id <id> <ipv4 | ipv6> map-cache. |
- |
"If this warning persists check platform " "limits and please contact TAC." |
|
LISP-4-REMOTE_RLOC_ROUTE_REJECTED |
4-Warning |
LISP remote locator [chars] route rejected due to locator reachability minimum-mask-length check. |
LISP locator not reachable as per shortest mask prefix configured to accept when looking up a remote RLOC in the RIB |
- |
"Ensure LISP locator reachability is consistent with " "minimum-mask configuration" |
|
LISP-4-ROUTE_IMPORT_RIB_EVENT_DROPPED |
4-Warning |
LISP [chars] RIB [chars] route import events dropped after reaching queue size of [dec]. Re-evaluation scheduled in [dec] minutes. |
The transient event queue used by LISP to store received RIB route import events reached the limit specified through the <CmdBold>{ipv4 | ipv6} route-import maximum-prefix <limit><noCmdBold> configuration. Subsequent RIB events were dropped. There may now be an inconsistency between the routes present in the RIB and those imported by LISP. A re-evaluation of LISP route import for the affected EID table has been scheduled to attempt to automatically recover from this condition. |
- |
"Modify the LISP <CmdBold>route-import<noCmdBold> " "configuration for the specified EID table to " "apply a route-map that only allows the desired RIB " "routes. If more routes are desired than the " "current limit you can increase it through the " "<CmdBold>maximum-prefix<noCmdBold> command. If " "error was a transient condition in the RIB you can " "force a re-evaluation of route import through the " "<CmdBold>clear {ip | ipv6} lisp route-import" "<noCmdBold>" |
|
LISP-4-ROUTE_IMPORT_WARN |
4-Warning |
LISP [chars] RIB import warning[chars] [chars] reached [dec] routes limit set to [dec]. |
- |
- |
- |
|
LISP-4-SITE_REGISTRATION_LIMIT_EXCEEDED |
4-Warning |
Configured site-registration limit [dec] has been reached or |
Map-server cannot create any more site registrations which are not explicitly configured. Consequently at least one map-register has been dropped. |
- |
"Increase the site registration limit using " "<CmdBold>site-registration limit <limit><noCmdBold> " "or limit the number of registrations from ETRs." |
|
LISP-4-SITE_REGISTRATION_LIMIT_EXCEEDED_ON_CONFIG |
4-Warning |
Configured site-registration limit [dec] is less than or equal |
The newly configured limit is less than the current count of registrations. |
- |
"Issue <CmdBold>clear lisp <id> site<noCmdBold> for " "limit to take immediate effect." |
|
LISP-4-SITE_REGISTRATION_LIMIT_WARNING |
4-Warning |
Configured site-registration warning threshold [dec]/[dec] > [dec]%% |
Site registration count has reached or exceeded the configured threshold. This is used to warn the adminstrator that corrective action may need to be taken to avoid reaching the configured site registration limit. |
- |
"No immediate action is required. Administrator may " "want to consider whether ETR registrations should " "be limited or capacity provisioned to accomodate " "growth in registration count." |
|
LISP-4-SITE_XTR_RLOC_INCONSISTENCY |
4-Warning |
[chars] RLOC [chars] in EID database configuration in record for [chars] from [chars]. |
While probing other xTRs in our own site we received a map reply mapping record listing a different set of locators than those we have configured in database commands. |
- |
"Issue the <CmdBold>show {ip | ipv6} lisp database" "<noCmdBold> command on both this xTR and the other " "site xTR that sent us the map reply to locate the " "mis-configuration. Add or remove locators in the " "config of one or both xTRs to make them have the " "same list of configured locators." |
|
LISP-4-UNSUPPORTED_LOCAL_RLOC |
4-Warning |
This platform does not support local [chars] RLOCs [chars] will be marked as down. |
The platform has indicated it does not support local RLOCs of this address family. |
- |
"Deconfigure the RLOC or move it to another xTR at " "the site which does not have this platform " "limitation." |
|
LISP-5-LISP_TCP_SESSION_STATE_CHANGE |
5-Notice |
Lisp session to peer address [chars] peer port [dec] changed to [chars]. |
This message is a notification that the specified session has gone up/down. |
- |
"If the session is expected to go up/down then" "no action is required. Otherwise investigation" "regarding the session going up/down should be" "done." |
|
LISP-5-MAP_RESOLVER_MAP_REQUEST_FILTERED |
5-Notice |
[dec] IID [dec] Map-resolver filtered map-request from [chars]. |
- |
- |
- |
|
LISP-5-MAP_RESOLVER_REACHABILITY_CHANGE |
5-Notice |
[dec] IID [dec] Map-resolver [chars] is [chars]. |
No route to reach map-resolver hence map-cache will not get resolved. |
- |
"Ensure ITR has connectivity to map-resolver." |
|
LISP-5-MAP_SERVER_MAP_REQ_NO_ITR_ETR_REACHABILITY |
5-Notice |
Map request received for EID[chars] but map server does not |
This message is to alert the user to the fact that a map request for an EID prefix is received by the map server and it doesn't have reacheablity to any ITR or ETR that registered this prefix so it cannot provide a useable locator to complete the EID-to-locator mapping. |
- |
"Normally this should not happen but if this " "condition persists it shows a connectivity problem " "between the map server and locators connected to the " "network." |
|
LISP-5-MAP_SERVER_REACHABILITY_CHANGE |
5-Notice |
[dec] IID [dec] Map-server [chars][chars] is [chars]. |
No route to reach map-server so local EID database prefix will not get registered. |
- |
"Ensure ETR has connectivity to map-server." |
|
LISP-5-MAP_SERVER_REGISTER_ALLOWED_LOCATOR_MISMATCH |
5-Notice |
[dec] IID [dec] Site [chars] Allowed locator mismatch in map-register |
The map-register contains RLOC that is not in the site's allowed locator list. |
- |
"Ensure map-server has the registering RLOCs " "added to the site's allowed locator list." |
|
LISP-5-MAP_SERVER_REGISTER_AUTHENTICATION_FAILURE |
5-Notice |
[dec] IID [dec] Site [chars] Failed to authenticate map-register for |
Map-server failed to authenticate map-register for EID prefix. This is potentially caused by different shared keys configured on ETR and map-server. |
- |
"Ensure ETR and map-server have the same " "configured shared key." |
|
LISP-5-MAP_SERVER_REGISTER_NO_CONFIG_EID_PREFIX |
5-Notice |
[dec] IID [dec] No site configuration to accept |
No site is configured to accept registration for EID prefix. |
- |
"Configure EID prefix in map-server site to " "enable registration." |
|
LISP-5-PROXY_ETR_REACHABILITY_CHANGE |
5-Notice |
[dec] IID [dec] Proxy ETR [chars] is [chars]. |
No route to reach proxy ETR so traffic drop is expected. |
- |
"Ensure router has connectivity to proxy ETR." |
|
LISP-5-SSO_SWITCHOVER_TIMEOUT |
5-Notice |
LISP SSO switchover timeout expired |
LISP is running in the Hot Standby mode and after switchover RIB did not converge in 3 minutes |
- |
"BGP has many routes to process with " "as RIB has many routes ensure all of them " "were processed." |
|
LISP-6-DDT_BAD_XTR_NONCE |
6-Information |
DDT resolver received two Map-Requests from [chars] for different EID prefixes but with the same nonce. |
An xTR issuing LISP Map-Requests includes a nonce value in each request. The xTR must use a different nonce value for each Map-Request for a new EID prefix. The identified xTR has sent us two Map-Requests each for a different EID prefix and they both carried the same nonce value. When querying the DDT hierarchy duplicate nonce values prevent the DDT resolver from associating received Map-Referral messages with the correct request. To protect against this problem the DDT resolver has dropped the second of the two received requests. |
- |
"Contact the operator of the ITR that is issuing " "the Map-Requests so that they can fix the problem " "by upgrading their system." |
|
LISP-6-MAP_SERVER_SITE_ALL_REGISTRATION_EXPIRED |
6-Information |
[dec] IID [dec] Map-Server site [chars] all registrations expired |
- |
- |
- |
|
LLC-2-UNEXPECT |
2-Critical |
LLC2: [chars] UNEXPECTED EVENT |
An internal software error was found. A software component is trying\n\ to use LLC2 structures that do not exist. |
- |
"Record the configuration and any information that would be useful in\n\ recreating the error and call your technical support representative." |
|
LLDP-4-LLDP_NEW_ENTRY |
4-Warning |
Neighbor record not committed - malloc failure |
LLDP entry creation failed |
ethernet-lldp |
"Run memory diagnostics" |
|
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." |
|
LLIST-3-OFFLIST |
3-Error |
[chars] from 0x[hec] 0x[hec] not on list |
An internal inconsistency was detected when an attempt was made to\n\ remove an item from a list not on the list. |
tag-switch |
"Copy the message exactly as it appears and report it to your technical\n\ service representative." |
|
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-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." |
|
LNMC-3-BADCLSI |
3-Error |
[chars] primitive not valid for lnm [chars] [chars] |
A LAN network manager system error occurred. |
- |
LOG_STD_ACTION |
|
LNMC-3-BADCLSICNF |
3-Error |
[chars] Invalid confirm [chars] [chars] |
A LAN network manager system error occurred. |
- |
LOG_STD_ACTION |
|
LNMC-3-BADCLSIDATALEN |
3-Error |
[chars] Bad data len = [dec] [chars] |
A LAN network manager system error occurred. |
- |
LOG_STD_ACTION |
|
LNMC-3-BADCLSIHDRLEN |
3-Error |
[chars] Bad header len = 0x[hec] [chars] |
A LAN network manager system error occurred. |
- |
LOG_STD_ACTION |
|
LNMC-3-BADCLSIIDTYPE |
3-Error |
[chars] Invalid ID type = 0x[hec] [chars] |
A LAN network manager system error occurred. |
- |
LOG_STD_ACTION_ERR |
|
LNMC-3-BADCLSIIND |
3-Error |
[chars] Invalid indication [chars] [chars] |
A LAN network manager system error occurred. |
- |
LOG_STD_ACTION |
|
LNMC-3-BADCLSIPRIMTYPE |
3-Error |
[chars] Invalid primitive type = 0x[hec] [chars] |
A LAN network manager system error occurred. |
- |
LOG_STD_ACTION |
|
LNMC-3-BADCLSIRET |
3-Error |
[chars] Invalid ret code 0x[hec] [chars] [chars] |
A LAN network manager system error occurred. |
- |
LOG_STD_ACTION |
|
LNMC-3-BADCLSISAP |
3-Error |
[chars] Bad clsi SAP id = [hec] [chars] |
A LAN network manager system error occurred. |
- |
LOG_STD_ACTION |
|
LOCK_COUNT-3-MPLS_TE_AUTO_TUN |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
LOCK_DOUBLE-3-MPLS_TE_AUTO_TUN |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
LOCK_ZERO-3-MPLS_TE_AUTO_TUN |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
LOGGER-3-ASSERT |
3-Error |
failure at %08X:[chars]:[dec] [chars] |
- |
- |
- |
|
LOGGER-3-IPC_INIT |
3-Error |
failure |
Logger client proxy IPC registration failed. |
cpp-ucode |
LOG_STD_ACTION |
|
LOGGER-3-IPC_UNHANDLED |
3-Error |
failure |
An unknown message was received by the logger client proxy. |
cpp-ucode |
LOG_STD_ACTION |
|
LOGGER-3-TEST1 |
3-Error |
Non rate limited message test |
- |
- |
- |
|
LOGGER-3-TEST1 |
3-Error |
Non rate limited message test |
- |
- |
- |
|
LOGGER-3-TEST2 |
3-Error |
Rate limited message test |
- |
- |
- |
|
LOGGER-3-TEST2 |
3-Error |
Rate limited message test |
- |
- |
- |
|
LOGGER-6-DROPPED |
6-Information |
[dec] messages |
Due to a lack of available buffers one or more log messages were dropped. |
cpp-ucode |
LOG_STD_ACTION |
|
LOGGER-6-IPC_ALLOC |
6-Information |
failure |
Logger client IPC alloc failed messages were droppped. |
cpp-ucode |
LOG_STD_ACTION |
|
LOGGER-6-IPC_SEND |
6-Information |
failure: [chars] |
Logger client IPC send failed messages were dropped. |
cpp-ucode |
LOG_STD_ACTION |
|
LOGGING_REDIRECT_ISSU-2-GET_BUFFER |
2-Critical |
Logging Redirect ISSU client failed to get buffer for message. Error: [dec] [chars] |
The Logging Redirect 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. |
logging-redirect |
"show logging and show checkpoint client" |
|
LOGGING_REDIRECT_ISSU-2-INIT |
2-Critical |
Logging Redirect ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The Logging Redirect 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. |
logging-redirect |
LOG_STD_ACTION |
|
LOGGING_REDIRECT_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
Logging Redirect ISSU client failed to send negotiation message. Error: [dec] [chars] |
The Logging Redirect 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. |
logging-redirect |
"show logging and show checkpoint client" |
|
LOGGING_REDIRECT_ISSU-2-SESSION_NEGO |
2-Critical |
Logging Redirect ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The Logging Redirect 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. |
logging-redirect |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
LOGGING_REDIRECT_ISSU-2-SESSION_REGISTRY |
2-Critical |
Logging Redirect ISSU client failed to register session information. Error: [dec] [chars] |
The Logging Redirect ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
logging-redirect |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
LOGGING_REDIRECT_ISSU-3-INVALID_SESSION |
3-Error |
Logging Redirect ISSU client does not have a valid registered session. |
The Logging Redirect ISSU client does not have a valid registered session. |
logging-redirect |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
LOGGING_REDIRECT_ISSU-3-MSG_NOT_OK |
3-Error |
Logging Redirect ISSU client Message Type [dec] is not compatible |
The Logging Redirect ISSU client received an incompatible message from the peer device. The message cannot be processed. |
logging-redirect |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
LOGGING_REDIRECT_ISSU-3-MSG_SIZE |
3-Error |
Logging Redirect ISSU client failed to get the MTU for Message Type [dec] . Error: [dec] [chars] |
The Logging Redirect ISSU client failed to calculate the MTU for the specified message. The Logging Redirect ISSU client is not able to send the message to the standby device. |
logging-redirect |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
LOGGING_REDIRECT_ISSU-3-SESSION_UNREGISTRY |
3-Error |
Logging Redirect ISSU client failed to unregister session information. Error: [dec] [chars] |
The Logging Redirect ISSU client failed to unregister session information. |
logging-redirect |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
LOGGING_REDIRECT_ISSU-3-TRANSFORM_FAIL |
3-Error |
Logging Redirect ISSU client [chars] transform failed for Message Type [dec] . Error: [dec] [chars] |
The Logging Redirect 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 Logging Redirect state between the active device and the standby device is not identical. |
logging-redirect |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
LOGIN-3-TOOMANY_AUTHFAILS |
3-Error |
Too many Login Authentication failures have occurred in the last one minute on the line [dec]. |
A large number of authentication failures greater than the configured limit have occurred in the last one |
security keyword:autosec |
"Make sure it is not by any malicious attempt to gain" " access to the device" |
|
LOOPDETECT-4-ERR_DISABLE |
4-Warning |
loopdetect frame sent on [chars] is received on [chars] err-disabling [chars] |
- |
- |
- |
|
LOOPDETECT-4-INVALID_HWIDB |
4-Warning |
invalid hwidb for src_mac [enet] |
Unable to translate the source macaddress in the loopdetect frame to a valid interface |
loopdetect |
LOG_STD_SH_TECH_ACTION |
|
LOOPDETECT-4-SYSLOG |
4-Warning |
loopdetect frame sent on [chars] is received on [chars] loopdetection on port [chars] |
This is a defensive measure that will put the interface in err-disable state when it detects a loop in the current or connected swtich. A recovery will be attempted after the configured retry time default 5 minutes if auto recovery is enabled. |
loopdetect |
LOG_STD_SH_TECH_ACTION |
|
LOTR_DBG-3-LOTR_RSRS_HA_ERR |
3-Error |
[chars] |
Resource dynamically allocated are synced to standby.\ Due to error mentioned sync failed.\n\ So standby won't be having same database as active |
asr900-tdm-combo |
- |
|
LOTR_DBG-4-LOTR_RSRS_HA_WARNING |
4-Warning |
[chars] |
Cem programming is not completed |
asr900-tdm-combo |
LOTR_RSRS_HA_INTERNAL_SW_WARNING_ACTION |
|
LOTR_DBG-6-LOTR_RSRS_HA_INFO |
6-Information |
[chars] |
Cem programming completed |
asr900-tdm-combo |
- |
|
LPD-3-MANYLF |
3-Error |
Line [t-line] packet has too many newlines to convert |
An internal buffer did not have enough room to add all the necessary\n\ carriage returns to a packet of LPD data destined for a printer\n\ configured with a newline-convert command. This message is unlikely to\n\ occur with a file containing valid data. |
- |
"Check the file being printed to see whether it contains valid\n\ printable data." |
|
LRE_CPE-3-INVALIDMODE |
3-Error |
\nCPE on interface [chars] is in invalid mode [chars]. |
- |
fw-hawaii |
"Use the command \"show controllers lre cpe mfg \" " "to verify that the CPE Model Number string is " "correct. Use the command \"hw-module slot <slot> " "lre upgrade remote \" to ensure that the CPE has " "the latest supported firmware. If the CPE's Model " "Number and firmware are correct use the interface " "configuration command \"shutdown\" followed " "by \"no shutdown\" to force the switch to re-read " "CPE information. If the problem persists contact " "your technical support representative." |
|
LRE_CPE-3-INVALIDPATCH |
3-Error |
\nCPE on interface [chars] has invalid LRE firmware. |
The LRE firmware header does not have a valid signature or the header information on the specified firmware is inconsistent with the contents of the firmware |
fw-hawaii |
"Upgrade the firmware on the CPE to the latest " "supported one by using the command " "\"hw-module slot <slot> upgrade lre remote\"." |
|
LRE_CPE-3-INVALIDPHY |
3-Error |
\nCPE on interface [chars] has an unsupported Ethernet PHY. |
The Ethernet PHY device on the CPE attached to the interface specified in the error message is not supported. This error occurs when the switch cannot recognize the PHY identifier of the PHY devices |
fw-hawaii |
"Verify that the CPE is a Cisco-supported one. " "Use the command \"show controllers lre cpe " "mfg\" to verify that the CPE Model Number " "string is correctly set. If the IOS version and " "CPE model number look correct issue the interface " "configuration command \"shutdown\" followed by " "\"no shutdown\" to force the switch to read the " "PHY identifer again. As a last resort power cycle " "the CPE. If the error persists contact your " "technical support representative." |
|
LRE_CPE-3-NOVERCKSUM |
3-Error |
\nCould not fetch CPE firmware version and checksum on interface [chars]. |
The system could not obtain the CPE firmware version and checksum. If the CPE has the latest firmware and the CPE Model Number is correct the most likely cause for this error is that the LRE link between the switch and the CPE is of poor quality. |
fw-hawaii |
"Use the command \"show controllers lre cpe mfg \" " "to verify that the CPE Model Number string is " "correctly set for this CPE. Use the command " "\"hw-module slot <slot> lre upgrade remote\" to " "ensure that the CPE has the latest firmware. " "Use the interface configuration command \"shutdown\" " "followed by \"no shutdown\" to force the switch " "to re-fetch the CPE firmware version and checksum. " "As a last resort power cycle the CPE. If the " "problem persists contact your technical support " "representative." |
|
LRE_CPE-3-UNKNOWNMODEL |
3-Error |
\nCPE has unrecognizable model number [chars] on interface [chars] |
The model number string in the CPE does not match a known CPE model number. |
fw-hawaii |
"Use the \"show controllers lre cpe mfg\" command " "to examine the Model Number of the CPE. " "Verify that the Model Number is a Cisco-supported " "one. Use the interface configuration command " "\"shutdown\" followed by a \"no shutdown\" to " "force the switch to re-read the CPE Model Number. " "If the error message persists record the output " "of the previously used show command and report the " "problem to your technical support representative." |
|
LRE_CPE-3-WRONGAPPVER |
3-Error |
\nCPE on interface [chars] reported unsupported version of application firmware [chars].\nMinimum application firmware version needed [chars] |
Each CPE requires a currently-supported application firmware version for it to function correctly. This CPE has a application firmware version that predates the earliest supported version. |
fw-hawaii |
"Application firmware is not currently used " "on the CPE. This error message is for future use." |
|
LRE_CPE-3-WRONGBOOTVER |
3-Error |
\nCPE on interface [chars] reported unsupported version of bootloader firmware [chars].\nMinimum bootloader firmware version needed [chars] |
Each CPE requires a currently-supported bootloader firmware version for it to function correctly. This CPE has a bootloader firmware version that predates the earliest supported version. |
fw-hawaii |
"Upgrade the bootloader firmware on the CPE to " "a recent version that supports the current " "requirements by using the command \"hw-module " "slot <slot> lre upgrade remote\". If the " "CPE firmware upgrade does not solve the problem " "force the switch to re-read the bootloader " "firmware version by issuing the interface " "configuration command \"shutdown\" followed " "by the command \"no shutdown\". As a last " "resort power cycle the CPE. If the problem " "persists contact your technical support " "representative." |
|
LRE_CPE-3-WRONGPATCH |
3-Error |
\nCPE on interface [chars] has wrong patch version [hec]. \nPatch version [hec] or higher is needed for this CPE. |
Each CPE requires a currently-supported patch version for it to function. This CPE has a patch version that predates the earliest supported version.This condition might occur because the switch was upgraded with the latest Cisco IOS Software image but the CPE firmware has not been upgraded. |
fw-hawaii |
"Upgrade the patch on the CPE to the latest " "supported version by using the command " "\"hw-module slot <slot> upgrade lre remote\"" |
|
LRE_CPE-5-SSNCHANGED |
5-Notice |
\nCPE unit on interface [chars] changed. |
The CPE system serial number changed. This condition usually means that the CPE unit on this interface was replaced. |
fw-hawaii |
"No action is required." |
|
LRE_LINK-3-PROFILE_FAILURE |
3-Error |
Interface [chars] profile [chars] failure |
The interface specified in the error message did not achieve link with attached profile. |
- |
"If the link failure was unexpected confirm the profile settings " "for the interface." |
|
LRE_LINK-3-UPDOWN |
3-Error |
Interface [chars] changed state to [chars] |
The interface hardware either has become active came up |
- |
"If the state change was unexpected confirm the configuration " "settings for the interface." |
|
LRE_LINK-4-HEALTH_MON |
4-Warning |
Interface [chars] had crossed certain monitored thresholds |
The link status monitor for the interface specified in the error messages has detected conditions that have crossed the configured thresholds. |
- |
"Enter the <CmdBold>show controllers lre link monitor<NoCmdBold> command to obtain more information on this error. If the change in operating conditions was unexpected confirm the configuration settings for the interface." |
|
LRE_LOG-7-LRE_LOGGING |
7-Debug |
LRE Log:Interface [chars]: State: [chars] Event: [chars] Data: [chars]. |
The system has changed its state. The error message text provides more information on the nature of the change. |
- |
LOG_STD_NO_ACTION |
|
LRE_UPGRADE-2-LOCAL_LOAD_FAILURE |
2-Critical |
The system failed to load the firmware for local PHY controller:[dec] |
An internal system error has occurred while loading the firmware for a local PHY controller. |
- |
"Power cycle the switch. If this message persists " "copy the message exactly as it occurs on the " "console or in the system log contact your " "Cisco technical support representative and " "provide the representative with the gathered " "information." |
|
LRE_UPGRADE-3-INIT_SYSTEM |
3-Error |
Upgrade module failed to initialize |
The LRE Upgrade module failed to initialize |
- |
LOG_STD_ACTION |
|
LRE_UPGRADE-3-LOCAL_FAILURE |
3-Error |
Upgrade of local controller [chars] failed |
LRE upgrade is unable to download firmware to a local controller |
- |
LOG_STD_ACTION |
|
LRE_UPGRADE-4-INIT_RESOURCE |
4-Warning |
[chars] |
The LRE Upgrade module cannot locate a required resource |
- |
"Report this message to your service representative" |
|
LRE_UPGRADE-4-TERMINATE |
4-Warning |
Upgrade on [chars] terminated |
The CPE was disconnected or changed in the middle of an upgrade. |
- |
"Verify that the CPE currently connected to the link requires an upgrade." |
|
LSA-3-MPLS_TE_PCALC |
3-Error |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
LSD_CLIENT-2-MSGHANDLERERR |
2-Critical |
Client=[dec] Msg type=[dec] Error=[chars] |
LSD Client API message handler error encountered |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release. If not gather the output of <CmdBold>show version<NoCmdBold> " "and <CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
LSD_CLIENT-2-XDREXEC |
2-Critical |
[chars] [dec] |
Illegal code execution in XDR path |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release. If not gather the output of <CmdBold>show version<NoCmdBold> " "and <CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
LSD_CLIENT-2-XDREXEC2 |
2-Critical |
[chars] [hec] [hec] |
Illegal code execution in XDR path |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release. If not gather the output of <CmdBold>show version<NoCmdBold> " "and <CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
LSD_CLIENT-3-CLIENTAPI |
3-Error |
Client API error: [chars] [dec] |
Unexpected Client API error |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release. If not gather the output of <CmdBold>show version<NoCmdBold> " "and <CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
LSD_CLIENT-3-INVALID_VAR |
3-Error |
[chars] |
Function received invalid parameters |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release. If not gather the output of <CmdBold>show version<NoCmdBold> " "and <CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
LSD_CLIENT-3-ISSU_ENUM_ERROR |
3-Error |
Enum for [chars] is not ISSU-compliant: [chars] |
The given enumeration is not ISSU-compliant for the reason given. Unpredictable behaviour will result when interoperating with different IOS versions. |
mpls-mfi |
"This requires a code fix before the image can be shipped or ISSU will be " "broken." |
|
LSD_CLIENT-3-ISSU_MSG_CONV |
3-Error |
[chars] [dec] [dec] |
Could not convert received message type to known message |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release. If not gather the output of <CmdBold>show version<NoCmdBold> " "and <CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
LSD_CLIENT-3-ISSU_REG |
3-Error |
ISSU client [chars] [dec] entity [dec] failed ISSU registration: [chars] |
ISSU negotiation failed for this XDR client. |
mpls-mfi |
"This error indicates a coding problem. It is an error that will occur" "every time this image is run and requires a code change to fix it." |
|
LSD_CLIENT-3-PCHUNK2 |
3-Error |
[chars]: [chars] [hec] [hec] |
Parameterized Chunk Manager error occurred |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release. If not gather the output of <CmdBold>show version<NoCmdBold> " "<CmdBold>show running-config<NoCmdBold> and <CmdBold>show process memory<NoCmdBold> " "and contact your Cisco technical support representative." |
|
LSD_CLIENT-3-UTIL2 |
3-Error |
[chars]: [hec] [hec] |
MFI Utilities error occurred |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release. If not gather the output of <CmdBold>show version<NoCmdBold> " "and <CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
LSD_HA-2-RESOURCE |
2-Critical |
[chars] |
System resource error occured |
mpls-mfi |
LOG_STD_REDUCE_ACTION |
|
LSD_HA-2-RF |
2-Critical |
[chars][dec] |
RF related error |
mpls-mfi |
LOG_STD_ACTION |
|
LSD_HA-3-GENERAL |
3-Error |
[chars] |
Function received invalid parameters |
mpls-mfi |
LOG_STD_ACTION |
|
LSD_HA-3-INVALID_VAR |
3-Error |
[chars] |
Function received invalid parameters |
mpls-mfi |
LOG_STD_ACTION |
|
LSD_HA-3-LABEL_RANGE_DB |
3-Error |
[chars] |
Error happen in label range db |
mpls-mfi |
LOG_STD_ACTION |
|
LSD_HA-3-UNSENT_MSG_DB |
3-Error |
[chars] |
Error happen in unsent msg db |
mpls-mfi |
LOG_STD_ACTION |
|
LSD_HA-4-CF |
4-Warning |
[chars][dec] |
CF related error |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-2-APP_NOTSUPP |
2-Critical |
[chars] interface does not support app [chars] |
Interface does not support app |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-2-AVL |
2-Critical |
[chars] [hec] |
AVL tree operation error |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-2-FPIHANDLER |
2-Critical |
[chars] [hec] |
FPI Handler error |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-2-INVALID_VAR |
2-Critical |
[chars] |
Function received invalid parameters |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-2-INVALID_VAR2 |
2-Critical |
[chars] 0x[hec] 0x[hec] |
Function received invalid parameters |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-2-RESOURCE |
2-Critical |
[chars] |
System resource error occured |
mpls-mfi |
LOG_STD_REDUCE_ACTION |
|
LSD-2-TESTAPP2 |
2-Critical |
Test app error: [chars]: [hec] [hec] |
Test application error |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-3-APPMGR |
3-Error |
[chars] 0x[hec] |
App Mansger error |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-3-BADEXEC |
3-Error |
Unexpected Code Execution: [chars] [dec] |
Unexpected Code Execution |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-3-CHUNKMGR |
3-Error |
chunk mgr: [chars] 0x[hec] |
Chunk manager error |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-3-CLIENT_CONN |
3-Error |
[chars] |
Client connection error |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-3-CLIENT_CONN2 |
3-Error |
[chars] [hec] [hec] |
Client connection error |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-3-EVTLOGBADSOURCE |
3-Error |
Illegal log event source: [dec] |
Illegal event found in log buffer |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-3-INTF_DB |
3-Error |
[chars] |
interface db error |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-3-INTF_DB2 |
3-Error |
[chars] [hec] [hec] |
interface db error |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-3-INVALID_PROC_EVT |
3-Error |
Unexpected process event [dec] for pid [dec] |
The LSD component received an unexpected process event notification for the process with the specified ID |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-3-LABEL |
3-Error |
[chars][dec] |
label operation error |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-3-LABEL_TBL_ERR |
3-Error |
Failed to create new label table due to [chars] |
Label space is not carved properly. This is likely due to platform capabilities. |
mpls-mfi |
"Check platform capabilities to make sure max label values are set correctly." |
|
LSD-3-LABEL2 |
3-Error |
[chars] [hec] [hec] |
label error |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-3-MULTISERVICEREQ |
3-Error |
Multiple outstanding service requests: [dec] [dec] |
Server request attempted with one already outstanding |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-3-OS_NOTIFY |
3-Error |
Process id [dec] [chars] error code [dec] |
LSD was unable to notify the operating system about unregistration |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this condition " "has been previously reported and resolved in a later release. If not " "gather the output of <CmdBold>show version<NoCmd Bold> " "<CmdBold>show running-config<NoCmdBold> " "<CmdBold>show mpls infrastructure lsd apps<NoCmdBold> and contact " "your Cisco technical support representative." |
|
LSD-3-OUTLABEL_RESV_ERROR |
3-Error |
[chars] Platform-outlabels:[dec] prim:[dec] application-outlabels:[dec] |
- |
- |
- |
|
LSD-3-REWMGR |
3-Error |
Rewrite Manager: [chars] 0x[hec] |
Rewrite Manager error |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-3-REWMGR2 |
3-Error |
[chars] 0x%08x 0x%08x |
Rewrite lookup failed due to FPI inconsisency |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-3-UPDATELISTMGR2 |
3-Error |
[chars] [dec] [dec] |
General error |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-3-UPDATELISTMGREXEC |
3-Error |
Illegal exec: [chars] [hec] |
Illegal code execution |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-4-BADAPI |
4-Warning |
[chars] from [chars] |
LSD recieved message with invalid parameters |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-4-HW_RESOURCE_EXHAUSTED |
4-Warning |
Hardware resource exhausted on [chars] of type [dec] |
The platform has run out of hardware resources. |
mpls-mfi |
"Reduce the mpls configuration." |
|
LSD-4-INVALID_VAR_WARN |
4-Warning |
[chars] |
Function received invalid parameters |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-4-LABEL_RESOURCE |
4-Warning |
label range [dec]-[dec] exhausted |
MPLS application is trying to allocate more labels than configuration will allow |
mpls-mfi |
LOG_STD_ACTION |
|
LSD-4-LABELFREETO |
4-Warning |
requested free timeout [dec] ms by [chars] limited to: [dec] ms |
MPLS application label free timeout exceed max allowed |
mpls-mfi |
LOG_STD_ACTION |
|
LSLIB-3-INIT |
3-Error |
Unable to initialize LS LIB. [chars] |
A software error occurred during initialization. |
ls-lib |
LOG_STD_ACTION |
|
LSLIB-3-INTERNAL |
3-Error |
[chars] |
An internal software error occurred. |
ls-lib |
LOG_STD_ACTION |
|
LSLIB-4-ATTR_MERGE |
4-Warning |
[chars] |
An attribute of a node or a link or a prefix does not contain values from all groups LSA in case of OSPF and LSP in case of ISIS of an LS LIB producer |
ls-lib |
LOG_STD_ACTION |
|
LSLIB-4-EOD |
4-Warning |
[chars] |
An LS LIB producer did not send EOD or an LS LIB consumer did not read EOD |
ls-lib |
LOG_STD_NO_ACTION |
|
LSMPI-4-INJECT_FEATURE_ESCAPE |
4-Warning |
Egress [chars] packet delivered via legacy inject path |
A packet with a CPP supported L3 encapsulation such as IP was |
- |
LOG_STD_ACTION |
|
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_GPID_REQUESTED-3-MPLS_TE_LM |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
LSP_BAD_GPID-3-MPLS_TE_LM |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
LSP_BAD_SWITCHING_TYPE_REQUESTED-3-MPLS_TE_LM |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
LSP_BAD_SWITCHING_TYPE-3-MPLS_TE_LM |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
LSP_VIF-2-CHUNK_ERR |
2-Critical |
Error initializing LSP_VIF chunks |
Internal error |
- |
LOG_STD_NO_ACTION |
|
LSP_VIF-2-RADIX_ERR |
2-Critical |
Error initializing RADIX tree |
The get_fd function reported an error trying to allocate a Event Detector context control block. |
ha/eem |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
LSP-5-MPLS_TE |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
LSPREJECT-4-MPLS_TE |
4-Warning |
ERRMSG_NOFLAGS |
- |
- |
- |
|
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-COMM_UNKNOWN_RC |
3-Error |
Unexpected oce return code |
Comm module - unexpected oce return code encountered |
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 |
|
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 |
|
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 |
|
LSS-0-INTERNAL_PANIC |
0-Emergency |
[chars] |
A Panic Condition. |
- |
"" |
|
LSS-1-INTERNAL_ALERT |
1-Alert |
[chars] |
A condition that should be corrected immediately. |
- |
"" |
|
LSS-1-SDM |
1-Alert |
[chars] [chars] |
LSS SDM Alert - protocol region reached limit. Cannot accept\n\ anymore entries. Need to reconfigure protocol regions and\n\ reload |
Switching Database Manager |
"Reconfigure SDM region sizes and reload" |
|
LSS-2-INTERNAL_CRITICAL |
2-Critical |
[chars] |
Critical Conditions |
- |
"" |
|
LSS-3-CHANNELSTUCK |
3-Error |
[chars] channel [dec] [chars] is stuck.\n This port has stuck [dec] times since last boot.\n |
Informational |
- |
"If portstuck reload is not enabled manually reload the interface or \n\ OIR the card." |
|
LSS-3-CONN_EMPTY_STATUS |
3-Error |
Conn empty detected [chars].\n This port has had conn empty problems [dec] times \n since last boot\n |
Informational |
- |
"If portstuck reload is not enabled manually reload the interface or \n\ OIR the card." |
|
LSS-3-CONN_PKT_STATUS |
3-Error |
[chars] [chars] |
Informational |
- |
"" |
|
LSS-3-CONN_STATUS |
3-Error |
[chars] [chars] |
Informational |
- |
"" |
|
LSS-3-INTERNAL_ERROR |
3-Error |
[chars] |
Errors |
- |
"" |
|
LSS-3-PORTSTUCK |
3-Error |
Interface [chars] is portstuck\n This port has stuck [dec] times since last boot.\n |
Informational |
- |
"If portstuck reload is not enabled manually reload the interface or \n\ OIR the card" |
|
LSS-3-PORTSTUCK_LIMIT |
3-Error |
This port has exceeded the port-stuck/\n conn-empty limit of [dec] as configured by the epc\n portstuck-reload-count command. This port will remain\n in init state until a OIR or user initiated download\n is done.\n |
- |
- |
"" |
|
LSS-4-HARDWARE_WARNING |
4-Warning |
\n******************************************************** \n ATM Router ModuleARM not supported with ASP hardware |
Cat8510 ASP hardware with version less than 6.0 doesnot support ATM Router ModulesARM |
- |
"Upgrade ASP hardware version to atleast 6.0 with FC-PFQ card. " |
|
LSS-4-INTERFACE |
4-Warning |
Interface [chars] [chars] |
Per interface Warning |
- |
"" |
|
LSS-4-INTERNAL_WARNING |
4-Warning |
[chars] |
Warning |
- |
"" |
|
LSS-4-LSIPC |
4-Warning |
[chars] [dec] |
LSIPC warning - LSIPC is timing out. uCode on that interface may\n\ not be responding |
E-PAM uCode |
"Possibly E-PAM is not responding" |
|
LSS-4-MACIPC |
4-Warning |
[chars] [dec] |
MAC Learn/Age IPC warning - MAC Learn or Age IPC dropped.\n\ The IOS bridge table and the L2 Cam entries are inconsistant |
cat2948g-bridging |
"Do clear bridge" |
|
LSS-6-INTERNAL_EVENT |
6-Information |
[chars] |
Informational |
- |
"" |
|
LSS-7-INTERNAL_ASSERT |
7-Debug |
[chars]: [chars] Assertion Failure - File [chars] Line [dec] |
Assertion |
- |
"" |
|
LSS-7-LEAFNULL |
7-Debug |
NUll leaf_p: vpi [dec] vci [dec] |
LSS IFCB2IDB Alert |
- |
"" |
|
LSS-7-VC_IDB |
7-Debug |
Interface: [chars] |
LSS VC_IDB Alert |
- |
"" |
|
LSS-7-VC2LEG |
7-Debug |
VC to LEG translation failure: vpi [dec] vci [dec] |
LSS VC2LEG Alert |
- |
"" |
|
LTC2978-4-CML_FAULT |
4-Warning |
Communication Fault is reported by LTC2978. [chars] |
LTC2978 reported Communication Fault |
cmts-platform |
"Copy the error message exactly as it appears and report it to your" " technical support" |
|
LTC2978-4-LOG_CLEAR_MAX_RETRIES |
4-Warning |
Tried [dec] times to read transfer status after clearing log for 2978-[dec] and the read was unsuccessful |
Log clear didn't work for LTC2978 |
cmts-platform |
"Copy the error message exactly as it appears and report it to your" " technical support" |
|
LTC2978-4-LOG_RESTORE_MAX_RETRIES |
4-Warning |
Tried [dec] times to read log data after log restore for 2978-[dec] and the read was unsuccessful |
Fatal Recoverable Raven interrupt |
cmts-platform |
"Copy the error message exactly as it appears and report it to your" " technical support" |
|
LTC2978-4-LTC2978_ALERT |
4-Warning |
LTC2978power fault monitor open drain alert for device #[dec] |
Interrupt from LTC2978 |
cmts-platform |
"Copy the error message exactly as it appears and report it to your" " technical support" |
|
LTC2978-4-VIN_FAULT |
4-Warning |
Input Voltage Fault is reported by LTC2978. [chars] |
LTC2978 reported Input Voltage Fault |
cmts-platform |
"Copy the error message exactly as it appears and report it to your" " technical support" |
|
LTC2978-4-VOUT_FAULT |
4-Warning |
Output Voltage Fault is reported by LTC2978. [chars] |
LTC2978 reported Output Voltage Fault |
cmts-platform |
"Copy the error message exactly as it appears and report it to your" " technical support" |
|
LTC2978-5-POWER_FAILURE |
5-Notice |
Power failure happened in previous power cycle. Check OBFL logs for details. |
LTC2978 recorded power failure in previous power cycle. |
cmts-platform |
"Copy the error message exactly as it appears and report it to your" " technical support" |
|
LTC2978-5-TEMPERATURE_FAULT |
5-Notice |
Temperature Fault is reported by LTC2978. [chars] |
LTC2978 reported Temperature Fault. [chars] |
cmts-platform |
"Copy the error message exactly as it appears and report it to your" " technical support along with the temperature values reported by MAX1668" " using test cable envm temp dump [1|2|3] command on LC console" |
|
M32X-1-AR_TIMEOUT |
1-Alert |
M32X controller [dec] channel 0x[hec]: No Reponse from device. Action Request Timeout |
The Action Request for a particular has failed after retry. |
- |
LOG_STD_NO_ACTION |
|
M32X-1-DWNLDCKSM |
1-Alert |
M32X: Download checksum error sent = 0x[hec] received = 0x[hec] |
The download of the internal microcode to the M32X failed to\n\ checksum correctly. This usually indicates a hardware failure of\n\ the M32X. |
- |
"Perform a power cycle. " LOG_STD_RECUR_ACTION |
|
M32X-1-DWNLDFL |
1-Alert |
M32X down load failed. |
The M32X trunk card failed. It could not download its \n\ operational microcode. |
- |
"Perform a power cycle. " LOG_STD_RECUR_ACTION |
|
M32X-1-INITFAIL |
1-Alert |
M32X slot [dec]: Init Failed at [chars] |
The M32x trunk card failed to complete hardware\n\ initialization. |
- |
LOG_STD_ACTION |
|
M32X-1-NOTCMPLT |
1-Alert |
M32X download failed to complete. |
The M32X trunk card has failed. It could not download its\n\ operational microcode. |
- |
LOG_STD_ACTION |
|
M32X-1-NOTREADY |
1-Alert |
Not ready for download. |
The M32X trunk card did not respond when commanded to\n\ download its operational microcode. |
- |
"Perform a power cycle. " LOG_STD_RECUR_ACTION |
|
M32X-1-STARTFAIL |
1-Alert |
[chars]: Channel enable failed |
A software or hardware error occurred. The M32X trunk card\n\ is not responding to commands used to initialize it. |
- |
LOG_STD_ACTION |
|
M32X-1-STOPFAIL |
1-Alert |
[chars]: Channel disable failed |
A software or hardware error occurred. The M32X trunk card\n\ failed to respond to a request to disable an interface. |
- |
LOG_STD_ACTION |
|
M32X-3-MBXREAD |
3-Error |
M32X: Stale msg in [chars] - mbx0:%lx mbx1:%lx mbx2:%lx |
The M32X has not responded to a message within a specified time. |
- |
LOG_STD_ACTION |
|
M32X-3-NOTM32X |
3-Error |
Device reported [hex] |
A hardware error occurred involving the PCI interface for\n\ an M32X trunk card. |
- |
"If it is an M32X trunk card then this is due to a malfunction.\n\ Or another PCI device may have been mistaken for an M32X. " LOG_STD_ACTION |
|
M32X-3-PANIC |
3-Error |
M32X: Exception [dec] trace [dec] |
A software or hardware error has occurred in the M32X trunk card. |
- |
LOG_STD_ACTION |
|
M32X-3-TOOSMALL |
3-Error |
M32X: [chars] - packet was less than two bytes |
An output packet was detected that was smaller than the minimum\n\ allowable datagram size. An error in another driver or an error in \n\ the system software probably triggered this error message. |
- |
LOG_STD_ACTION |
|
M32X-5-REMLOOP |
5-Notice |
M32X controller [dec] channel [dec]: remote loopback [chars] [chars] |
The interface entered or exited a remote loopback. |
- |
LOG_STD_NO_ACTION |
|
MAB-5-FAIL |
5-Notice |
Authentication failed for client [chars] on Interface [chars] |
Authentication was unsuccessful. |
- |
LOG_STD_NO_ACTION |
|
MAB-5-SUCCESS |
5-Notice |
Authentication successful for client [chars] on Interface [chars] |
Authentication was successful. |
- |
LOG_STD_NO_ACTION |
|
MAC_LIMIT-4-PORT_DROP |
4-Warning |
[chars] with Configured limit %ld has currently %ld entries |
The Number of entries for the port has gone below or\n\ is equal to the allowed number |
l2 |
"Depends of the Network admin" |
|
MAC_LIMIT-4-PORT_ENFORCE |
4-Warning |
Enforcing limit on [chars] with Configured limit %ld |
The Number of entries for the port has exceeded the\n\ allowed number and the enforce to limit action is configured |
l2 |
"Depends of the Network admin" |
|
MAC_LIMIT-4-PORT_EXCEED |
4-Warning |
[chars] with configured limit %ld has currently %ld entries |
The Number of entries for the port has exceeded the\n\ allowed number |
l2 |
"Depends of the Network admin" |
|
MAC_LIMIT-4-VLAN_DROP |
4-Warning |
Vlan [dec] with configured limit %ld has currently %ld entries |
The Number of entries for a vlan has gone below or\n\ is equal to the allowed number |
l2 |
"Depends of the Network admin" |
|
MAC_LIMIT-4-VLAN_ENFORCE |
4-Warning |
Enforcing limit on Vlan [dec] with configured limit %ld |
The Number of entries for a vlan has exceeded the\n\ allowed number and the enforce to limit action is configured |
l2 |
"Depends of the Network admin" |
|
MAC_LIMIT-4-VLAN_EXCEED |
4-Warning |
Vlan [dec] with configured limit %ld has currently %ld entries |
The Number of entries for a vlan has exceeded the\n\ allowed number |
l2 |
"Depends of the Network admin" |
|
MAC_MOVE-4-NOTIF |
4-Warning |
Host [enet] in vlan [dec] is flapping between port [chars] and port [chars] |
The system has found the specified host moving between the specified ports. |
cat6000-l2 |
"Check the network for possible loops." |
|
MACDB-3-ERROR |
3-Error |
Internal error [chars] |
An internal software error occurred. |
fhrp: macdb |
LOG_STD_ACTION |
|
MACDB-4-WARN |
4-Warning |
Internal warning [chars] |
An internal software warning occurred. |
fhrp: macdb |
LOG_STD_ACTION |
|
MACDB-6-INFO |
6-Information |
Internal info [chars] |
An internal software information message occurred. |
fhrp: macdb |
LOG_STD_ACTION |
|
MACSEC-3-VIOLATION_RESTR_RELEARN |
3-Error |
Attempt to move [enet] from [[chars]] to [[chars]] |
The MAC address specified in the system message is currently learned on the first ethernet service instance specified in the system message. An ethernet frame with the same MAC address has now been encountered on the second ethernet service instance. This is a violation of MAC Security policy. |
ether-infra |
"If the MAC address has to be permitted to be re-learnt on the second " "service instance remove the address from the list of addresses " "permitted on the first service instance if applicable and clear the " |
|
MACSEC-3-VIOLATION_SHUT_INST_DENIED |
3-Error |
Attempt to learn denied address [enet] on [chars]. Service instance will be shutdown. |
The ethernet service instance specified in the system message has been configured for shutdown-mode MAC Security and has been configured to deny the MAC address specified in the system message. A frame was received from this denied MAC address. The address has not been learnt and additionally the service instance has been shutdown. |
ether-infra |
- |
|
MACSEC-3-VIOLATION_SHUT_INST_LIMIT |
3-Error |
Attempt to learn [enet] on [chars] caused configured service instance limit [dec] to be exceeded. Service instance will be shutdown. |
- |
- |
- |
|
MACSEC-3-VIOLATION_SHUT_RELEARN |
3-Error |
Attempt to move [enet] from [[chars]] to [[chars]] shutting down the latter |
The MAC address specified in the system message is currently learned on the first ethernet service instance specified in the system message. An ethernet frame with the same MAC address has now been encountered on the second ethernet service instance. This is a violation of MAC Security policy and as a result the second service instance will be shut down. |
ether-infra |
"If the MAC address has to be permitted to be re-learnt on the second " "service instance remove the address from the list of addresses " "permitted on the first service instance if applicable and clear the " |
|
MACSEC-4-IPMTU_OVERSIZE |
4-Warning |
MACsec enabled interface [chars] IP MTU can't be more than [dec] |
User config IP MTU size over MACsec enabled interface allows. |
- |
"Reconfigure IP MTU base on the suggested range." |
|
MACSEC-4-RX_SC_EXCEED |
4-Warning |
RX SCI %llx : TX SCI %llx : vport [dec] : secy vport [dec]\n |
Multiple In Late Packets Received. |
- |
"No action required normal operation." |
|
MACSEC-4-TX_SC_EXCEED |
4-Warning |
TX SCI %llx : vport [dec]\n |
TX SC exceeds hardware limit. |
- |
"No action required normal operation." |
|
MACSEC-4-VIOLATION_RESTR_BD_LIMIT |
4-Warning |
Attempt to learn [enet] on [chars] caused configured bridge-domain limit [dec] to be exceeded. |
The bridge-domain specified in the system message is not allowed to learn addresses beyond the limit specified in the system message. A service instance belonging to this bridge-domain received a frame with unknown source MAC address and if this address is learnt it would cause the bridge-domain limit to be exceeded. The address has not been learnt. |
ether-infra |
- |
|
MACSEC-4-VIOLATION_RESTR_INST_DENIED |
4-Warning |
Attempt to learn denied address [enet] on [chars]. |
The ethernet service instance specified in the system message has been configured for restrict-mode MAC Security and has been configured to deny the MAC address specified in the system message. A frame was received from this denied MAC address. The address has not been learnt. |
ether-infra |
- |
|
MACSEC-4-VIOLATION_RESTR_INST_LIMIT |
4-Warning |
Attempt to learn [enet] on [chars] caused configured service instance limit [dec] to be exceeded. |
The ethernet service instance specified in the system message has been configured for restrict-mode MAC Security and is not allowed to learn addresses beyond the limit specified in the system message. This service instance received a frame with unknown source MAC address and if this address is learnt it would cause the limit to be exceeded. The address has not been learnt. |
ether-infra |
- |
|
MACSEC-4-VIOLATION_RESTR_SYS_CFG_LIMIT |
4-Warning |
Attempt to learn [enet] on [chars] caused system limit [dec] to be exceeded. |
It is not allowed to learn addresses beyond the system limit that allows number of permitted + sticky addresses to be configured in the system. A service instance received a frame with unknown source MAC address and if this address is learnt it would cause the system limit to be exceeded. The address has not been learnt. |
ether-infra |
- |
|
MACSEC-4-VIOLATION_RESTR_SYS_LIMIT |
4-Warning |
Attempt to learn [enet] on [chars] caused system limit [dec] to be exceeded. |
It is not allowed to learn addresses beyond the system limit. A service instance received a frame with unknown source MAC address and if this address is learnt it would cause the system limit to be exceeded. The address has not been learnt. |
ether-infra |
- |
|
MACSEC-5-TX_SA_PN_EXPIRE |
5-Notice |
TX SCI %llx : AN [dec] TX SA PN about to expire.\n |
TX SA PN about to expire. Send a request to MKA to perform a SAK Rekey for the given TX SCI and AN. |
- |
"No action required normal operation." |
|
MACSEC-5-UNSUPPORTED_SUP |
5-Notice |
MACsec is not supported on supervisor HW version [dec] in slot [dec] |
This log indicates that Macsec is not supported on a given port |
coresw-macsec |
LOG_STD_NO_ACTION |
|
MACSEC-6-CREATE_RX_SC |
6-Information |
[chars] RX SCI %llx : TX SCI %llx : vport [dec] : secy vport [dec]\n |
MKA request MACsec PD to create a RX SC on the given RX SCI and vport. |
- |
"No action required normal operation." |
|
MACSEC-6-CREATE_TX_SC |
6-Information |
[chars] TX SCI %llx : vport [dec]\n |
MKA request MACsec PD to create a TX SC on the given TX SCI and vport. |
- |
"No action required normal operation." |
|
MACSEC-6-DEL_RX_SA |
6-Information |
[chars] RX SCI %llx : vport [dec] : an [dec]\n |
MKA request MACsec PD to delete a RX SA on the given RX SCI vport and an. |
- |
"No action required normal operation." |
|
MACSEC-6-DEL_RX_SC |
6-Information |
[chars] RX SCI %llx : vport [dec]\n |
MKA request MACsec PD to delete a RX SC on the given RX SCI and vport. |
- |
"No action required normal operation." |
|
MACSEC-6-DEL_TX_SC |
6-Information |
[chars] TX SCI %llx : vport [dec]\n |
MKA request MACsec PD to delete a TX SC on the given TX SCI and vport. |
- |
"No action required normal operation." |
|
MACSEC-6-INSTALL_RX_SA |
6-Information |
[chars] RX SCI %llx : vport [dec] : an [dec] : secy_vport [dec]\n |
MKA request MACsec PD to install a RX SA on the given RX SCI vport and an. |
- |
"No action required normal operation." |
|
MACSEC-6-INSTALL_TX_SA |
6-Information |
[chars] TX SCI %llx : vport [dec] : an [dec] : next_pn 0x[hec]\n |
MKA request MACsec PD to install a TX SA on the given TX SCI vport and an. |
- |
"No action required normal operation." |
|
MACSEC-6-POST_FAIL |
6-Information |
[chars] Power-On-System-Test failure in Trial No.[dec]\n |
MACSEC power-on-system-test failed |
- |
"No action required normal operation." |
|
MACSEC-6-POST_SUCC |
6-Information |
[chars] Power-On-System-Test success in Trial No.[dec]\n |
MACSEC power-on-system-test successful |
- |
"No action required normal operation." |
|
MAILBOX-3-BADCHKSUM |
3-Error |
Checksum failed. Expected = 0x%02x calculated = 0x%02x. Ignoring PDU. |
A hardware or software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
MAILBOX-3-BADECHO |
3-Error |
Echo-response did not match echo-request! |
- |
- |
"Confirm the router module installation. Make sure the software\n\ revision on the management module and the router module carrier card is\n\ up-to-date. If the error persists call your technical support\n\ representative for assistance." |
|
MAILBOX-3-BADPDU |
3-Error |
PDU of type [chars] received. Invalid or unsupported. Ignoring. |
- |
- |
"Informational message only. No action required." |
|
MAILBOX-3-INITFAIL |
3-Error |
Mailbox initialization failure. [chars] Mailbox offline. |
A catastrophic failure involving the initialization of the\n\ administrative mailbox occurred. The mailbox will be taken offline and\n\ remain in that state until a router module reset or a system reload\n\ occurs At that time initialization will again be attempted. Note that\n\ the functionality of the router that is it's ability to receive and\n\ forward packets is not affected by this error. |
- |
"Confirm the router module installation. Make sure the software\n\ revision on the management module and the router module carrier card is\n\ up-to-date. If the error persists call your technicalsupport\n\ representative for assistance." |
|
MAILBOX-3-NOECHO |
3-Error |
Echo-request timed out. No response received. Mailbox offline. |
An ECHO_RESPONSE was not received in the appropriate time after the\n\ generation of an ECHO_REQUEST. This failure only occurs during mailbox\n\ initialization and indicates a problem between the communication path\n\ of the router module and its carrier card. |
- |
"Confirm the router module installation. Make sure the software\n\ revision on the management module and the router module carrier card is\n\ up-to-date. If the error persists call your technical support\n\ representative for assistance." |
|
MAILBOX-3-OFFLINE |
3-Error |
[chars] mailbox is offline. Interrupt ignored. |
This message is generated when an attempt is made by the management\n\ module to communicate with an offline mailbox. When it appears it\n\ indicates a problem exists between the perceived state of the mailbox\n\ from the router's side versus the management module's side. |
- |
"Issue a system-wide reset on the management module. If the error\n\ persists call your technical support representative for assistance." |
|
MAILBOX-3-TIMEOUT |
3-Error |
Intra-PDU timeout occurred on [chars] mailbox data. |
A timeout occurred while sending or receiving the characters of a\n\ protocol data unit PDU. The entire PDU will be ignored. |
- |
"Informational message only. No action required" |
|
MAILBOX-6-INITOK |
6-Information |
Mailbox initialization successful. |
This message is generated after a router reload to indicate the\n\ mailbox was successfully initialized. |
- |
"Informational message only. No action required." |
|
MAILBOX-7-MBOXDEBUG |
7-Debug |
[chars] |
This message header is paired with general debugging messages used to\n\ provide information about the functionality of the mailbox. To enable\n\ mailbox debugging issue the command debug mailbox. |
- |
"Advisory message only. No action required." |
|
MAILBOX-7-ONLINE |
7-Debug |
[chars] mailbox coming online. |
This message is generated only when mailbox debugging is enabled. It\n\ provides information about the state of each incoming or outgoing\n\ mailbox. |
- |
"Advisory message only. No action required." |
|
MAILBOX-7-READ |
7-Debug |
Reading 0x%02x from carrier. |
This message is generated only when mailbox debugging is enabled. It\n\ provides very low-level information about the incoming mailbox data\n\ stream. |
- |
"Advisory message only. No action required." |
|
MAILBOX-7-WRITE |
7-Debug |
Writing 0x%02x to carrier. |
This message is generated only when mailbox debugging is enabled. It\n\ provides very low-level information about the outgoing mailbox data\n\ stream. |
- |
"Advisory message only. No action required." |
|
MAIN_INIT_FAILED-3-MPLS_TE_HA |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
MALLOC-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
MAT_LIMIT-4-DROPPED |
4-Warning |
bdomain [dec] with configured limit %ld has currently %ld entries |
The Number of mac entries for a bdomain has gone below or\n\ is equal to the allowed number |
l2 |
"Depends of the Network admin" |
|
MAT_LIMIT-4-EXCEEDED |
4-Warning |
bdomain [dec] with configured limit %ld has currently %ld entries |
The Number of mac entries for a bdomain has exceeded the\n\ allowed number |
l2 |
"Depends of the Network admin" |
|
MATM_CF-4-QUEUE_OVERLIMIT |
4-Warning |
MATM CF dropped message type [dec] as queue limit has reached |
MATM checkpoint client could not send some messages because\n\ an internal queue was full. Mac address table on the standby\n\ might not be in sync and can impact behavior upon switchover. |
mac_addresses |
LOG_STD_SH_TECH_ACTION |
|
MATM_ISSU-3-BUFFER |
3-Error |
MATM ISSU client failed to get buffer for message error [dec] |
MATM ISSU client failed to get buffer for building\n\ a negotiation message. Hence it can send the negotiation\n\ message to the standby unit. When there is a problem in\n\ the negotiaiton the standby unit can not be brought up. |
mac_addresses |
"show logging and show checkpoint client" |
|
MATM_ISSU-3-CAP_INVALID_SIZE |
3-Error |
MATM ISSU client capability list is empty. |
The MATM ISSU client capability exchange list size\n\ is invalid. |
mac_addresses |
"show issu capability entries <Client_ID>" |
|
MATM_ISSU-3-CAP_NOT_COMPATIBLE |
3-Error |
MATM ISSU client capability exchange result incompatible. |
The MATM ISSU client capability exchange has negotiated\n\ as incompatible with the peer. |
mac_addresses |
"show issu negotiated capability <Session_ID>" |
|
MATM_ISSU-3-CAPABILITY |
3-Error |
MATM ISSU client [chars] |
MATM ISSU client observed an error during capability\n\ negotiation. When this error happens there is a mismatch\n\ between the client capability between the active and\n\ standby unit. |
mac_addresses |
"show issu capability entries <client_id> and \n\ show issu session <client_id> and \n\ show issu negotiated capability <session_id>" |
|
MATM_ISSU-3-INIT |
3-Error |
MATM ISSU client initialization failed at [chars] error [chars] |
MATM ISSU client could not be initiailzed this will\n\ cause catstrophic failure when ISSU upgrade or downgrade\n\ is performed. |
mac_addresses |
LOG_STD_SH_TECH_ACTION |
|
MATM_ISSU-3-MSG_NOT_OK |
3-Error |
MATM ISSU client message [dec] is not compatible |
MATM ISSU client received an incompatible message\n\ from the peer unit. Since the message is not compatible\n\ it can be processed by this unit |
mac_addresses |
"show issu message group <client_id> and\n\ show issu session <client_id> and \n\ show issu negotiated version <session_id>" |
|
MATM_ISSU-3-MSG_SIZE |
3-Error |
MATM ISSU client failed to get the message size for message [dec] |
MATM ISSU client failed to calculate message size\n\ for the message specified. The MATM ISSU client will not\n\ be able to send message to the standby unit. |
mac_addresses |
"show issu message group <client_id> and\n\ show issu session <client_id> and \n\ show issu negotiated version <session_id>" |
|
MATM_ISSU-3-POLICY |
3-Error |
MATM ISSU client message type [dec] is [chars] |
MATM ISSU client received an message type which it\n\ does not support. The policy is applied to make the session\n\ compatible. |
mac_addresses |
"show issu session <client_id>" |
|
MATM_ISSU-3-SEND_FAILED |
3-Error |
MATM ISSU client failed to send a negotiation message error [dec] |
MATM ISSU client could not send a session negotiation\n\ message to the peer. When there is a problem in the \n\ negotiation the standby unit can not be brought up. |
mac_addresses |
"show logging and show checkpoint client" |
|
MATM_ISSU-3-SESSION |
3-Error |
MATM ISSU client [chars] |
MATM ISSU client observed an error during a session\n\ negotiation with the peer unit. When there is a problem\n\ with the session the standby unit can not be brought up. |
mac_addresses |
"show issu capability entries <client_id> and \n\ show issu session <client_id> and \n\ show issu negotiated capability <session_id>" |
|
MATM_ISSU-3-SESSION_UNREGISTRY |
3-Error |
MATM ISSU client failed to unregister session information. Error: [dec] [chars] |
The MATM ISSU client failed to unregister session information. |
mac_addresses |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MATM_ISSU-3-TRANSFORM |
3-Error |
MATM ISSU client [chars] transform failed error [chars] |
MATM ISSU client could not transform the message.\n\ If the transmit transformation failed it means that the\n\ checkpoint message can not be sent to the standby unit.\n\ If the receive transformation failed it means that the\n\ checkpoint message can not be applied on the standby\n\ unit. In both cases the MATM state will not\n\ be indentical with the active unit. |
mac_addresses |
"show issu session <client_id> and \n\ show issu negotiated version <session_id>" |
|
MAXMSGSIZE-4-LDP |
4-Warning |
ERRMSG_LIMIT_SLOW*15 |
- |
- |
- |
|
MBOX-3-DEREG_FAIL_BAD_PARM |
3-Error |
event 0x[hec] |
Deregistration of handler function for a mailbox event failed due to a bad parameter. |
cpp-ucode |
LOG_STD_ACTION |
|
MBOX-3-DEREG_FAIL_NO_HANDLER |
3-Error |
event 0x[hec] handler 0x[hec] |
Deregistration of handler function for a mailbox event failed because no handler was registered for the event. |
cpp-ucode |
LOG_STD_ACTION |
|
MBOX-3-NO_HANDLER_FOR_EVENT |
3-Error |
events 0x[hec] bad bit number [dec] |
Mailbox event is pending but no handler is registered for event. |
cpp-ucode |
LOG_STD_ACTION |
|
MBOX-3-REG_FAIL_BAD_PARM |
3-Error |
event 0x[hec] handler 0x[hec] |
Registration of handler function for a mailbox event failed due to a bad parameter. |
cpp-ucode |
LOG_STD_ACTION |
|
MBOX-3-REG_FAIL_HANDLER_EXISTS |
3-Error |
event 0x[hec] handler 0x[hec] |
Registration of handler function for a mailbox event failed because a handler is already registered for the event. |
cpp-ucode |
LOG_STD_ACTION |
|
MCAST_MQC-3-CMAP_SDB_REGISTER |
3-Error |
Error initialising class-map of type multicast-flows. |
Could not register the component related to the class-map of type \n\ multicast-flows to the string database. |
ipmulticast |
"LOG_STD_ACTION" |
|
MCAST-3-MCAST_MLRE_ERR |
3-Error |
Non MLRE friendly FIA on interface [chars] |
Unexpected flowlock id following feature execution |
cpp-ucode |
LOG_STD_ACTION |
|
MCAST-3-MCAST_PA_REPLICATE_FAILED |
3-Error |
[chars] |
m-cast replication failure for PA described packet. |
cpp-ucode |
LOG_STD_ACTION |
|
MCAST-3-MCAST_REPLICATE_GATHER_FAILED |
3-Error |
[chars] [inet] |
m-cast replication failure due to a bad Multicast Gather parameter. |
cpp-ucode |
LOG_STD_ACTION |
|
MCASTRED-3-ACKQMSG |
3-Error |
Failed attempt to enqueue sync message type [dec] in confirmation queue |
An attempt to link a new sync message into the sync message confirmation queue failed. This indicates corruption of the linkage within the queue. It is not possible to track message confirmation or to initiate a recovery action if confirmation is not received. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-ACKUNQMSG |
3-Error |
Failed to remove sync request type [dec] from pending ACK queue |
An attempt failed to unlink a completed sync request from the queue for requests awaiting confirmation of receipt from the standby RP. This indicates corruption of the linkage within the pending acknowledgement queue. False timeout error messages and memory leakage are likely. Loss of standby RP sync is possible. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-AF_NULL_PRM |
3-Error |
NULL parameter specified for setting PIM HA address family [dec] context. |
A function handling a PIM NSF state machine transition specified an invalid NULL address for one or more pointers to PIM NSF |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-ALCSYNCTYP |
3-Error |
Attempt to allocate sync request for invalid sync type [dec] |
The sync data type specified by the function attempting to perform a sync operation is not a valid type. No sync operation can be performed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-ALLOC_CAP_TLV |
3-Error |
Failed attempt to allocate memory for [chars] client capability TLV |
The callback function responsible for creating an ISSU capability type TLV list was unable to allocate memory to hold the TLV list. Capability negotiation can not proceed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-ALLOCMSG |
3-Error |
Sync message buffer allocation failed for sync info type [dec] |
An attempt to allocate a buffer for sync message transmission failed. Loss of sync on the standby RP is likely. |
- |
LOG_STD_SH_TECH_ACTION " Attempt standby RP synchronization by reloading " "the standby RP. " |
|
MCASTRED-3-BAD_ADDR_TYPE |
3-Error |
Invalid Address Type [dec] for PIM SSO handling. |
An IP multicast SSO function received an invalid Address Type input parameter. Synching of the affected database type to the standby RP can not be completed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-BAD_AF |
3-Error |
Invalid Address Family [dec] for PIM SSO handling. |
An IP multicast SSO function received an invalid Address Family input parameter. A subsequent timeout error and routing convergence delay is likely. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-BAD_DBG_PRM |
3-Error |
Invalid parameter value in multicast redundancy debug command handling. |
An invalid NULL or out of bounds value was specified in a call |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-BAD_EVENT_TYPE |
3-Error |
Defrd sync event type [dec] is invalid. |
An invalid value was specified in a call to handle events which deferred sync elements are waiting for. The value is greater than PIM_SYNC_WAIT_FOR_EVENT_MAX. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-BAD_SYNC_TYPE |
3-Error |
PIM sync type [dec] is invalid or too large. |
An out of bounds value was specified in a call to set or get pim sync type bit array. The value is either greater than PIM_SYNC_TYPE_MAX or greater than the length of the bit array. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-BLKNOBOOL |
3-Error |
Failed to create [chars] watched boolean for bulk sync |
An attempt to create a watched boolean to monitor bulk sync of state information to the standby RP has failed. It is not possible to verify successful completion of the bulk sync operation. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-BLKNOFUNC |
3-Error |
No bulk sync function defined for sync type [dec] |
There is no function defined for bulk synching of database information of this type. It is possible that some required information may not be synched to the standby RP. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-BULK_COMPLETE_INCOMPATIBLE |
3-Error |
Skipping sending of bulk sync completion message to peer: Incompatible message type. |
The message code designated for peer RP confirmation of bulk sync completion was not recognized by the ISSU infrastructure as a compatible PIM HA message type. Although PIM bulk sync may have succeeded bulk sync confirmation is not possible. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-BULK_COMPLETE_XFORM_FAIL |
3-Error |
ISSU xmit transform failed for bulk send complete message. |
ISSU transformation failed on the message used for peer RP confirmation of bulk sync completion. Although PIM bulk sync may have succeeded bulk sync confirmation is not possible. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-BULKRQTIME |
3-Error |
Timeout sending bulk sync requests to standby |
The maximum wait time has expired for transmission of enqueued bulk sync messages to the standby RP. It is possible that not all required sync messages have been successfully sent. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-CAP_PROC_NULL_CTX |
3-Error |
NULL client context for ISSU capability TLV processing. |
The callback function responsible for processing a capability type TLV was invoked by the ISSU infrastructure with a NULL client context. Capability negotiation can not proceed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-CAP_PROP_NULL_CTX |
3-Error |
NULL client context for ISSU capability TLV setup. |
The callback function responsible for creating a capability type TLV was invoked by the ISSU infrastructure with a NULL client context. Capability negotiation can not proceed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-DDE_REPLAY_BAD_AF |
3-Error |
Invalid Address Family for PIM NSF data driven event replay completion. |
Notification for completion of MFIB data driven event DDE |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-DDE_REPLAY_FAILSAFE |
3-Error |
PIM NSF Data Driven Event failsafe timer expired. First waiting table/VRF is \[chars]\ |
MFIB replay of data driven events and subsequent MRIB update processing has not completed within the maximum allowed time interval. PIM is forcing termination of the DDE replay monitoring period but some multicast routing information may not have been restored. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-DDE_REPLAY_NULL_TABLE |
3-Error |
NULL table specified for [chars] DDE replay. |
An invalid NULL value was specified in a call to handle |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-DECODEFUNC |
3-Error |
No decode function exists for sync data type [dec] |
There is no function defined for handling sync data of the specified type. No sync action is possible on the standby RP for the sync message that specified this data type. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-DECODENULL |
3-Error |
No message buffer specified for standby sync of database type [dec] or unsupported address type. |
A function was invoked to perform a database sync operation on the standby RP but the caller did not specify the address of the sync message containing the information required for performing the sync operation. Or the address type is unsupported. The sync operation for this database entity type can not proceed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-DEFER_SYNC_FAILURE |
3-Error |
Sync failure in standby defer sync operation. |
An element which was scheduled to be synched later has failed to sync either upon arrival of the event it was waiting for or it has waited in the deferred sync queue for more than 1 minute. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-DELNULLREQ |
3-Error |
No sync request specified in sync request deletion attempt. |
In a call to delete a sync request entry the caller failed to specify the location of the sync request to be deleted. A memory leak is likely. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-DELSYNCTYP |
3-Error |
Attempt to delete sync request for invalid sync type [dec] |
The sync data type specified by the function attempting to delete a sync request is not a valid type. The sync request can not be deleted. A memory leak is likely. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-DUP_ENQUEUE |
3-Error |
This element is already in queue. |
The element is already in queue. The current logic does not allow this to happen. Please investigate why the element is in queue. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-EMPTY_CAP_GROUP |
3-Error |
Empty capability group for [chars] ISSU client capability TLV setup. |
The callback function responsible for creating an ISSU capability type TLV found that the count of capability entries in its client context table was zero. Capability negotiation can not proceed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-EMPTY_CAP_PROPOSE_TABLE |
3-Error |
Empty capability table for ISSU capability TLV setup. |
The callback function responsible for creating a capability type TLV was invoked by the ISSU infrastructure with a capability table containing no capability types. Capability negotiation can not proceed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-EMPTY_FUN_CALL |
3-Error |
The default empty function [chars] is called. |
The default empty function called the real function seems have not been hooked up yet. This happens when function called before function hooked up. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-EOXBADRC |
3-Error |
Invalid completion code [dec] for sync message transmission type [dec] |
An undefined completion code was specified for end of sync message transmission handling. Memory leakage false timeouts and other subsequent errors may result. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-EOXNOREQ |
3-Error |
End of sync message transmission: no sync request specified |
End of sync message transmission handling was invoked with no sync request specified. Cleanup for successful transmission can not proceed. Retry for unsuccessful transmission can not proceed. Memory leakage is likely and loss of sync on the standby RP is possible. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-FINDNULLENT |
3-Error |
No target specified for sync entity search. |
In a call to invoke a search for a database entity requiring synching to the standby RP the caller failed to specify a descriptor for the entity to be synched. The sync operation entity can not proceed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-FMTFUNC |
3-Error |
No sync message format function defined for sync type [dec] |
No function is defined to create a sync messages for this type of database information. Loss of sync on the standby RP is likely. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-FMTGENNOBF |
3-Error |
No message buffer specified for generic sync message info |
A function was invoked to store generic sync message information into an outgoing message buffer but the caller did not specify the outgoing message buffer address. The sync operation for this database entity type can not proceed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-FMTMSG |
3-Error |
Failed to format a sync message for sync type [dec] |
An attempt to format create a sync message has failed. The |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-FMTNULLPRM |
3-Error |
Missing parameters in sync message format request for data type [dec] |
A function was invoked to store sync message information into an outgoing message buffer but the caller failed to specify either the location of the search key for the the database entity to be synched or the address of the outgoing message buffer The sync operation for this database entity type can not proceed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-HASHNQ |
3-Error |
Failed attempt to enqueue sync request type [dec] in hash table |
An attempt to link a new sync request into the sync request hash table failed. This indicates corruption of the linkage within the hash table. The sync operation can not proceed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-HLD_RLS_NO_TABLE |
3-Error |
No table for tableid 0x[hec] specified for multicast NSF holdoff release. |
A table ID for which no table exists was specified as an input to a function registered for releasing of a multicast NSF holdoff lock. If the calling client has a real holdoff extension request pending for some table the lock will not be released until the holdoff failsafe timer expires. This could delay completion of multicast reconvergence following an RP failover. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-HLP_BAD_TYPE |
3-Error |
Invalid helper type [dec] specified for [chars] PIM sync helper registration. |
The PIM sync infrastructure specified an invalid helper type in a call to a pim sync helper registration function. No PIM sync helper functions can be registered for this helper type for this address family. As a result PIM SSO functionality will be impaired for this address family. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-HLP_NULL_PRM |
3-Error |
NULL parameter specified for [chars] PIM sync helper registration. |
The PIM sync infrastructure specified one or more NULL pointers to the output parameters in a call to a pim sync helper registration function. No PIM sync helper functions can be registered for this address family. As a result no PIM SSO functionality can be provided for this address family. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-HLP_NULL_REG |
3-Error |
NULL list registered for PIM sync helper functions. |
In a request to register helper functions for the owner of one or more PIM sync databases a NULL value was specified for the list of functions to be registered. PIM sync operations may be inhibited for the affected database types. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-HLP_REG_COUNT |
3-Error |
Invalid count [dec] specified for PIM sync helper registration. |
In a request to register helper functions for the owner of one or more PIM sync databases an invalid value was specified for the count of functions to be registered. PIM sync operations may be inhibited for the affected database types. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-HLP_REG_SYNC_TYPE |
3-Error |
Invalid sync type [dec] specified for PIM sync helper registration. |
In a request to register helper functions for the owner of one or more PIM sync databases an invalid value was specified for the sync database type of at least one of the functions to be registered. PIM sync operations may be inhibited for the affected database types. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-HLP_REG_TYPE |
3-Error |
Invalid type [dec] specified for PIM sync helper registration. |
In a request to register helper functions for the owner of one or more PIM sync databases an invalid value was specified for the helper function type of the functions to be registered. PIM sync operations may be inhibited for the affected database types. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-HOLDOFF_FAILSAFE |
3-Error |
[chars] PIM NSF failsafe timer expired. Holding client mask = 0x[hec] |
One or more clients requested extension of the PIM NSF holdoff period but did not release the holdoff within the maximum allowed time interval. PIM is forcing termination of the NSF holdoff period and resumption of normal flow of multicast routing information but one or more clients may not be ready to resume normal operation. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-INITNOBOOL |
3-Error |
Failed to create [chars] watched boolean during multicast redundancy initialization |
An attempt to create a watched boolean during multicast PIM |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-INITNOQUEUE |
3-Error |
Failed to create [chars] watched queue during multicast redundancy initialization |
An attempt to create a watched queue during multicast PIM |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-INV_CKPT_MSG |
3-Error |
Received invalid CF message. client = [dec] entity = [dec] type = [dec] |
An invalid Checkpoint Facility message was received by the PIM HA checkpoint client. The message can not be processed. A possible loss of database syncrhronization between the primary and standby RPs is possible. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-INV_PORT_TYPE |
3-Error |
Invalid communication port identifier [dec] specified for ISSU port up/down handling |
The communication port identifier specified for PIM ISSU tranport up/down handling has an undefined value. PIM ISSU communication port up/down handling can not proceed. PIM ISSU functionality may be impaired or lost. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-INVALID_CAP_PROPOSE_TABLE |
3-Error |
Invalid capability table for [chars] client ISSU capability TLV setup. |
The callback function responsible for creating a capability type TLV was invoked by the ISSU infrastructure with a capability table that did not match any of the registered entries for this client. Capability negotiation can not proceed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-INVSYNCTYP |
3-Error |
Attempt to initiate sync request for invalid sync type |
The sync data type specified by the function attempting to initiate a sync operation is not a valid type. No sync operation can be performed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-ISSU_EMPTY_TLV |
3-Error |
Empty TLV list received for ISSU [chars] client capability processing |
The callback function responsible for processing an ISSU capability type TLV list received an empty TLV list. Capability negotiation can not proceed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-ISSU_PROC_CAP_TYPE |
3-Error |
Invalid capability type found in [chars] client capability entry. |
The callback function responsible for processing an ISSU capability type TLV list encountered a capability type for which no handling is available. Capability negotiation can not proceed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-ISSU_TLV_INSERT |
3-Error |
Failed to insert entry in ISSU capability TLV list for [chars] client |
The callback function responsible for creating an ISSU capability type TLV list encountered a failure when attempting to insert an entry into a TLV list. Capability negotiation can not proceed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-LOCFUNC |
3-Error |
No database entity search function defined for sync type [dec] |
A function was invoked to store sync message information into an outgoing message buffer but no function exists for locating a database entry of the specified type. The sync operation for this database entity type can not proceed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-LOCNULLENT |
3-Error |
No destination specified in search for sync entity of type [dec] |
A function was invoked to search for a database entity of the specified type. The caller failed to specify a destination for storing the search result. The sync operation for this database entity type can not proceed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-LOCNULLHND |
3-Error |
No search handle specified in search for sync entity of type [dec] |
A function was invoked to search for a database entity of the specified type. The caller failed to specify a search handle key |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-MCAC_COST |
3-Error |
Deleted mCAC reservation cost for [chars] [chars] if_number [dec] |
The accumulated total source or group cost for the affected mCAC reservation DB should always be the greater than the cost of any reservation within the database. This logic error means that the accounting is incorrect. As a result the amount of bandwidth initially reserved for multicast state previously admitted by the current mCAC configuration may be incorrect following an RP failover. This may lead to some disruption of multicast traffic following an RP failover. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-MCAC_DELETE_ALL_NO_IDB |
3-Error |
Failed to find IDB for mCAC [chars] reservation DB delete. AF = [dec] Reason: [chars] |
Lookup of the IDB for the specified input parameters failed either because of an invalid input parameter or incorrect/missing entries in tables used for the lookup. The requested DB delete operation can not proceed. Extraneous mCAC reservations may exist temporarily following an RP failover. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-MCAC_NO_IDB |
3-Error |
No IDB for if_number [dec] in mCAC reservation sync attempt for SG [chars] [chars] |
- |
- |
- |
|
MCASTRED-3-MCAC_RADIX_DELETE |
3-Error |
Failed to delete radix tree node for mCAC reservation [chars] DB. Address [chars] Mask [chars] |
During handling of an mCAC reservation database element deletion an attempt to delete the affected element from the mCAC reservation database radix tree failed. As a result the amount of bandwidth initially reserved for multicast state previously admitted by the current mCAC configuration may be incorrect following an RP failover. This may lead to some disruption of multicast traffic following an RP failover. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-MCAC_RADIX_INIT |
3-Error |
Failed to update radix tree for mCAC reservation [chars] DB for [chars] [chars] mCAC reservation on interface number [dec] |
- |
- |
- |
|
MCASTRED-3-MCAC_SEQ |
3-Error |
Missing standby mCAC configuration for [chars] [chars] mCAC |
During handling of an mCAC reservation sync request on the standby RP the corresponding mCAC limit configuration was not found. This is probably a result of a sequencing problem between synching of multicast configuration information and synching of dynamic state information. As a result the amount of bandwidth initially reserved for multicast state previously admitted by the current mCAC configuration may be incorrect following an RP failover. This may lead to some disruption of multicast traffic following an RP failover. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-MDT_DATA_RCV_DECAP_INV_OP |
3-Error |
Invalid operation type [dec] specified for an MDT data receive decap message. |
The sync operation type specified in a message to sync MDT data group receive decapsulation information was not a defined type for this message. The requested action can not be performed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-MDT_NO_MDB |
3-Error |
Failed to find or create an MDB during MDT data send group [chars] sync for group [inet] source [inet] MVRF [chars] |
The standby RP could not create the MDB required for building an MDT data group send entry. Interruption of MVPN data flow is possible if an RP failover occurs. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-MDT_NO_SND_GRP |
3-Error |
Failed to create an MDT send group entry during MDT data send group sync for group [inet] source [inet] MVRF [chars] |
The standby RP could not create the specified MDT data group send entry. Interruption of MVPN data flow is possible if an RP failover occurs. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-MRIB_PEND_UPD_CHK_BAD_AF |
3-Error |
Invalid Address Family for PIM pending mrib update check |
Registry service invocation to check for pending PIM mrib updates specified an invalid Address Family. The check can not be completed. Some pending updates may not be handled correctly resulting in delayed multicast re-convergence. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-MRIB_UPD_NULL_TABLE |
3-Error |
NULL table pointer specified for MRIB update notification. |
A NULL table address was specified in a function call to notify the PIM HA process that all pending updates have been read for a given multicast routing table. The process will attempt to continue with RP switchover handling despite this error. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-MSGHDL |
3-Error |
Could not obtain sync handle for completed sync message type [dec] [dec] |
- |
- |
- |
|
MCASTRED-3-MSGNOREQ |
3-Error |
Could not find sync request for completed sync message type [dec] |
The sync request corresponding to a completed sync message could not be determined. Memory leakage false timeouts and other subsequent errors may result. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-MSGSEQNUM |
3-Error |
Out of order sequence number in received sync message for sync data type [dec] received epoch/seq [dec]/[dec] expected [dec]/[dec] |
The sequence number specified in a sync message received by the standby RP is not the expected sequence number for the next received sync message. Some sync messages may have been lost. |
- |
LOG_STD_SH_TECH_ACTION " Attempt standby RP synchronization by reloading " "the standby RP. " |
|
MCASTRED-3-MVRF_NAME |
3-Error |
MVRF lookup for VRF [chars] failed. |
An MVRF lookup failed for a VRF name known to be associated with an existing MVRF table. This indicates incorrect setup of search parameters. A PIM data synch operation has been aborted. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-MVRF_TABLEID |
3-Error |
MVRF lookup for tableid [dec] failed. |
An MVRF lookup failed for a table ID known to be associated with an existing MVRF table. This indicates incorrect setup of search parameters. A PIM data synch operation has been aborted. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-NEGOMSGINV |
3-Error |
Invalid negotiation status for [chars] client message |
ISSU infrastructure evaluation of a received message for this client failed to identify the message as a negotiation message or a user message. The message can not be processed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-NO_SR_CONFIG_SYNC |
3-Error |
The Service Reflect Rule is being synced before Config sync is done. |
The Service Reflect Rule sync handled by Mcast HA requires Config sync to have already happened. Since the config sync has not yet happened we are ignoring the Service Reflect Rule sync. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-NOSYNCARG |
3-Error |
NULL argument pointer specified for PIM data sync type [dec]. |
A function was invoked to sync PIM information but the caller did not provide a valid data pointer. The sync operation for this database entity type can not proceed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-NULL_PIM_RED_CB |
3-Error |
Invalid [chars] address family PIM redundancy control block. |
During initialization of PIM redundancy control blocks an invalid NULL value was provided for one of the address family |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-PRM_LOOKUP |
3-Error |
PIM RP mapping range lookup for VRF [chars] range [chars]/[dec] failed. |
A PIM RP mapping range lookup failed for a range that is known to exist. This indicates incorrect setup of search parameters. A PIM data synch operation has been aborted. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-RCVNODATA |
3-Error |
No data pointer returned for received checkpoint message |
On reception of a checkpoint message at the standby RP an attempt to obtain the location of the data for the message returned a NULL pointer. No message contents are available for this message. |
- |
LOG_STD_SH_TECH_ACTION " Attempt standby RP synchronization by reloading " "the standby RP. " |
|
MCASTRED-3-RPDF_NO_IDB |
3-Error |
No IDB for if_number [dec] in Bidir RP DF sync attempt for RP address [inet]. |
The IDB if_number specified in a function call to trigger synching of Bidir RP DF information does not map to any existing IDB. The sync operation can not proceed. The DF information may no longer be correct following an RP failover. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-RPDF_NULL_IDB |
3-Error |
NULL IDB pointer in Bidir RP DF sync attempt for RP address [inet]. |
A NULL IDB address was specified in a function call to trigger synching of Bidir RP DF information. The DF information may no longer be correct following an RP failover. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-RTRYLIMIT |
3-Error |
Retry limit reached for sync type [dec] |
The maximum allowable number or transmission retries has failed for a database entity of this type. The retry can not be executed. The standby RP may no longer be synchronized with the active RP. |
- |
LOG_STD_SH_TECH_ACTION " Attempt standby RP synchronization by reloading " "the standby RP. " |
|
MCASTRED-3-RTRYNOREQ |
3-Error |
Sync retry requested with no sync request specified |
Retry for transmission of a sync message was requested but no sync request information was specified. The retry can not be executed. The standby RP may no longer be synchronized with the active RP. |
- |
LOG_STD_SH_TECH_ACTION " Attempt standby RP synchronization by reloading " "the standby RP. " |
|
MCASTRED-3-SEARCH_LOGIC |
3-Error |
Conflicting results for database search during a sync operation for sync type [dec] |
The function invoked to search for a database entity of the specified type provided a search return code that is inconsistent with the information returned by the search. Information that should be available was not provided. The sync operation |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-SNDMSG |
3-Error |
Failed to send a sync message for sync type [dec] |
An attempt to send a sync message has failed. The message transmission will be automatically retried. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-SNDNODATA |
3-Error |
No data pointer provided in checkpoint message to be sent. |
After allocation of a checkpoint message buffer in the primary RP an attempt to obtain the location of the data for the message returned a NULL pointer. The message can not be sent. Loss of standby sync is likely. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-SPURIOUS_MGD_TIMER_EXP |
3-Error |
Managed timer wakeup received by the PIM HA process with no expired timers. |
The PIM HA process received a wakeup for managed timer expiration but the API to obtain the first expired timer returned a NULL pointer. The timer expiration can not be handled. Possible loss of state synchronization between the primary and standby RP may occur. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-SYNC_REQ_ORPHAN |
3-Error |
Orphaned queue links found in sync request hash table search for sync type [dec] |
An attempt to find a matching entry for a new sync request in the sync request hash table failed because of corruption of the linkage within the hash table. The sync operation can not proceed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-SYNCNULLPRM |
3-Error |
Missing parameters in sync message format or decode request for data type [dec] |
For a function invoked to execute a sync update on the standby RP the caller failed to specify a valid pointer for holding the result of a search for the database information to be updated. The sync operation for this database entity type can not proceed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-TABLE_INVALID_CAP_TYPE |
3-Error |
Invalid capability type found in [chars] client capability entry. |
The callback function responsible for creating an ISSU capability type TLV list encountered a capability type for which no handling is available. Capability negotiation can not proceed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-TUNSYNCMSG |
3-Error |
Received invalid termination message for mvrf[dec] while |
Confirmation has failed for standby RP reception of an MDT tunnel message. This message is needed to provide the standby RP with MDT tunnel sync information required for creation of the MDT tunnel on the standby RP. |
- |
LOG_STD_SH_TECH_ACTION " Attempt standby RP synchronization by reloading " "the standby RP. " |
|
MCASTRED-3-TUNSYNCRCV |
3-Error |
[chars] failure in reception of MDT tunnel sync information for mvrf [chars] on the standby RP. |
Confirmation has failed for standby RP reception of an MDT tunnel message. This message is needed to provide the standby RP with MDT tunnel sync information required for creation of the MDT tunnel on the standby RP. |
- |
LOG_STD_SH_TECH_ACTION " Attempt standby RP synchronization by reloading " "the standby RP. " |
|
MCASTRED-3-TUNSYNCTIME |
3-Error |
Timeout waiting for confirmation of mdt tunnel sync for mvrf[dec] [chars] |
- |
- |
- |
|
MCASTRED-3-TUNSYNCXMIT |
3-Error |
Failed to transmit sync MDT tunnel information for mvrf [chars] to the standby RP. |
An IPC transmission attempt has failed to send an IPC message to provide the standby RP with MDT tunnel sync information required for creation of the MDT tunnel on the standby RP. |
- |
LOG_STD_SH_TECH_ACTION " Attempt standby RP synchronization by reloading " "the standby RP. " |
|
MCASTRED-3-UCAST_CONV_STBY |
3-Error |
Spurious unicast convergence notification received on standby RP for table [chars]. |
Unicast convergence notification was erroneously signalled on the standby RP for the specified multicast table or VRF. This convergence notification is being ignored. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-UNKNWOWN_CONV_AFI |
3-Error |
Failed to determine converged address family for topoid 0x[hec] |
On reception of unicast convergence notification for a specified routing table the PIM HA process attempted to obtain the address family ID AFI for the converged table. This attempt received a |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTRED-3-WAITQ_ORPHAN |
3-Error |
Orphaned queue links found in the [hec] MVRF wait queue. |
An attempt to perform state transition handling for MVRFs in this queue failed because of queue corruption or because one or more queue link entries did not specify the address of the corresponding MVRF. Multicast route convergence following an RP failover may be delayed or impaired. |
- |
LOG_STD_SH_TECH_ACTION |
|
MCASTV4-3-OUT_OF_TCAM_IPV4_MCAST |
3-Error |
Out of tcam space |
Number of IPv4 mcast routes installed exceeded supported scale |
firmware |
"Please reduce the number of IPv4 mcast routes " "configured to supported scale" |
|
MCASTV4-3-OUT_OF_TCAM_IPV4_MCAST |
3-Error |
Out of tcam space |
Number of IPv4 mcast routes installed exceeded supported scale |
firmware |
"Please reduce the number of IPv4 mcast routes " "configured to supported scale" |
|
MCASTV4-3-OUT_OF_TCAM_IPV4_MCAST |
3-Error |
[chars] : Out of tcam space. Current Tcam Count is [dec] |
Number of IPv4 mcast routes installed exceeded supported scale |
firmware |
"Please reduce the number of IPv4 mcast routes " "configured to supported scale" |
|
MCASTV4-3-OUT_OF_TCAM_IPV4_MCAST |
3-Error |
[chars] : Out of tcam space. Current Tcam Count is [dec] |
Number of IPv4 mcast routes installed exceeded supported scale |
firmware |
"Please reduce the number of IPv4 mcast routes " "configured to supported scale" |
|
MCASTV6-3-OUT_OF_TCAM_IPV6_MCAST |
3-Error |
Out of tcam space |
Number of IPv6 mcast routes installed exceeded supported scale |
firmware |
"Please reduce the number of IPv6 mcast routes " "configured to supported scale" |
|
MCASTV6-3-OUT_OF_TCAM_IPV6_MCAST |
3-Error |
Out of tcam space |
Number of IPv6 mcast routes installed exceeded supported scale |
firmware |
"Please reduce the number of IPv6 mcast routes " "configured to supported scale" |
|
MCASTV6-3-OUT_OF_TCAM_IPV6_MCAST |
3-Error |
[chars]: Out of tcam space. Current v6MC Count: [dec] |
Number of IPv6 mcast routes installed exceeded supported scale |
firmware |
"Please reduce the number of IPv6 mcast routes " "configured to supported scale" |
|
MCASTV6-3-OUT_OF_TCAM_IPV6_MCAST |
3-Error |
[chars]: Out of tcam space. Current v6MC Count: [dec] |
Number of IPv6 mcast routes installed exceeded supported scale |
firmware |
"Please reduce the number of IPv6 mcast routes " "configured to supported scale" |
|
MCPRP_DAI-4-ERR_DISABLE |
4-Warning |
DAI detected error on [chars] putting [chars] to err-disable |
Dynamic ARP inspection has detected an error condition because ARP packets have exceeded the configured rate or burst |
dai |
LOG_STD_ACTION |
|
MCT1E1-2-CMD_DROP |
2-Critical |
[chars] cmd: [dec] arg0: [dec] arg1: [dec] arg2: [dec] arg3: [dec] vc: [dec] reason: [chars] |
The SPA driver dropped a configuration command. One or more interfaces or controllers associated with the SPA may not be configured correctly. |
- |
"Please check the configuration of the interfaces and controllers " "and correct the configuration if necessary. If the condition persists " "copy the error message exactly as it appears and report it to your " "technical support representative. Please also supply a " "<CmdBold>show tech-support<NoCmdBold> at that time." |
|
MCT1E1-2-EV_DROP |
2-Critical |
[chars] cmd: [dec] arg0: [dec] arg1: [dec] arg2: [dec] arg3: [dec] reason [chars] |
The SPA driver dropped an event notification command. Counters or line protocols for one or more interfaces or controllers may be incorrect. |
- |
"Please restart any interfaces or controllers that are down. " "If the condition persists copy the error message exactly as " "it appears and report it to your technical support representative. " "Please also supply a <CmdBold>show tech-support<NoCmdBold> at that " "time." |
|
MCT1E1-3-AUTODNR |
3-Error |
[chars] failed for slot [dec] bay [dec] err [dec] |
AUTODNR/USNDNR process has failed. The SPA and SIP are out of synchronization. This condition indicates a software error. |
spa-ser-te1 |
LOG_STD_ACTION |
|
MCT1E1-3-BAD_SIZE_ERR |
3-Error |
[chars]: [dec] [chars] events on HDLC Controller were encountered. The SPA is being Restarted. |
The SPA driver detected an error event on the HDLC controller. |
- |
CTE1_STD_ACTION |
|
MCT1E1-3-BATCH_CMD_INVALID_TAG |
3-Error |
[chars]: Invalid tag value [dec] at index [dec]. |
The SPA driver detected invalid tag value in a batch command. |
spa-ser-te1 |
"The SPA driver has detected invalid command format from RP. " "If the ports on the SPA are not operating as expected power down and " "reseat the indicated SPA card. " CTE1_STD_ACTION |
|
MCT1E1-3-BERT_OPERATION_ERR |
3-Error |
[chars]: BERT operation error on interface [chars] - [chars]. |
The SPA reported failure during BERT operation. The current BERT operation will be terminated but the affected interface might not be operational if that is the case try to 'shutdown' and then 'no shutdown' the interface to recover from this failure. |
spa-ser-te1 |
"If manual 'shutdown' and then 'no shutdown' of the interface does " "not restore the operation then SPA will need to be reloaded to " "recover from this failure state." |
|
MCT1E1-3-BERT_STOP_ERR |
3-Error |
[chars]: Failed to stop BERT operation on interface [chars] - [chars]. |
The SPA failed to stop the BERT operation on the indicated interface. The interface might not be functional after this event if that is the case try to 'shutdown' and then 'no shutdown' the interface to recover from this failure. |
spa-ser-te1 |
"If manual 'shutdown' and then 'no shutdown' of the interface does " "not restore the operation then SPA will need to be reloaded to " "recover from this failure state." |
|
MCT1E1-3-CMD_FAILED |
3-Error |
[chars]: Failed to send command '[chars]' to SPA - [chars]. |
The SPA driver could not successfully send a cmd to firmware. |
spa-ser-te1 |
"The SPA driver has detected a command failure. " "If the ports on the SPA are not operating as expected power down and " "reseat the indicated SPA card. " CTE1_STD_ACTION |
|
MCT1E1-3-COR_MEM_ERR |
3-Error |
[chars]: [dec] correctable [chars] memory errors encountered. |
The SPA driver detected a correctable memory error on the SPA card. |
- |
"The SPA has encountered a correctable memory error on the SPA card. " "The error has been corrected and normal processing should continue. " "The hexadecimal memory address of the most recent error is specified " "in the message text on the console or in the system log. " CTE1_STD_ACTION |
|
MCT1E1-3-FPGA_CNTR_ERR |
3-Error |
[chars]: [dec] [chars] errors encountered. |
- |
- |
- |
|
MCT1E1-3-FRMR_CLKFAIL |
3-Error |
[chars]: Framer input clock failure detected CTCLK = [chars]CTIVE LREFCLK = [chars]CTIVE SREFCLK = [chars]CTIVE ctclk count [dec] lrefclk count [dec] srefclk count [dec] |
The SPA driver detected failure of one ore more input clocks to the framer chip. The T1/E1 Ports may not operate as expected. |
- |
"The SPA driver has detected input clock failures on the framer chip. " "If the ports on the SPA are not operating as expected power down and " "reseat the indicated SPA card. " CTE1_STD_ACTION |
|
MCT1E1-3-HDLC_CTRL_ERR |
3-Error |
[chars]: [dec] [chars] events on HDLC Controller were encountered. |
The SPA driver detected an error event on the HDLC Controller. |
- |
"The SPA driver has encountered an error event on the SPA card. " CTE1_STD_ACTION |
|
MCT1E1-3-INITFAIL |
3-Error |
MCT1E1 bay [dec] Init Failed at [chars] - line [dec] arg [hec] |
The SPA failed to complete hardware initialization. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
MCT1E1-3-LOOP_UNSUPPORTED |
3-Error |
[chars]: [chars] on port [dec]/[dec]/[dec] and it is not supported on SPA. |
The SPA driver received 'loopback payload' request from the remote device on the SPA card. SPA does not support loopback payload. |
- |
"The SPA driver has received 'loopback payload' request from the remote " "device on the SPA card. SPA does not support loopback payload. " "The remote request is ignored. Please unconfigure the command on the " "remote device. " |
|
MCT1E1-3-LOOPBACK_CFG_ERR |
3-Error |
[chars]: Loop [chars] configuration error on controller [chars] - [chars][chars]. |
The SPA reported failure during setting of loop up/down operation. The current loopback will be terminated but the affected controller might not be operational if that is the case try to 'shutdown' and then 'no shutdown' the controller to recover from this failure. |
spa-ser-te1 |
"If manual 'shutdown' and then 'no shutdown' of the controller does " "not restore the operation then SPA will need to be reloaded to " "recover from this failure state." |
|
MCT1E1-3-PERIODIC_PROCESS |
3-Error |
[chars]: periodic process error [chars]. |
The SPA driver detected an error with periodic processing routine. |
spa-ser-te1 |
"The SPA driver has detected problem with periodic routine. " "If the ports on the SPA are not operating as expected power down and " "reseat the indicated SPA card. " CTE1_STD_ACTION |
|
MCT1E1-3-QUEUE_HALT_FAIL |
3-Error |
[chars]: Could not suspend message [dec] or command [dec] queue |
- |
- |
- |
|
MCT1E1-3-SPI4_HW_ERR |
3-Error |
[chars]: [chars] Hardware error was encountered. |
The SPA driver detected a Hardware error condition on the SPA card. This might result in improper operation. |
- |
"The SPA driver has encountered a Hardware error on the SPA's SPI4 bus." "Please power down and reseat the indicated SPA card. " CTE1_STD_ACTION |
|
MCT1E1-3-TIMEOUT |
3-Error |
[chars]: [chars] failed: [dec] state: [dec] ml_id: [dec] progress: [dec] |
Linkrec is stuck at non ready. This condition indicates a software error. |
spa-ser-te1 |
LOG_STD_ACTION |
|
MCT1E1-3-UNCOR_MEM_ERR |
3-Error |
[chars]: [dec] uncorrectable [chars] memory errors encountered. |
The SPA driver detected an uncorrectable memory error condition on the SPA card. Packet corruption may result. |
- |
"The SPA driver has encountered an uncorrectable memory error on the SPA " "card. The hexadecimal memory address of the most recent error is " "specified in the message text on the console or in the system log. " "Please power down and reseat the indicated SPA card. " CTE1_STD_ACTION |
|
MCT1E1-3-UNCOR_PARITY_ERR |
3-Error |
[chars]: [dec] [chars] parity errors encountered. |
The SPA driver detected an uncorrectable parity error condition on the SPA card. Packet corruption may result. |
- |
"Please power down and reseat the indicated SPA card. " CTE1_STD_ACTION |
|
MDNS_HA_ISSU-3-BUFFER |
3-Error |
mDNS HA ISSU client failed to get buffer for message error [dec] |
mDNS HA ISSU client failed to get buffer for building\n\ a negotiation message. Hence it can send the negotiation\n\ message to the standby unit. When there is a problem in\n\ the negotiaiton the standby unit can not be brought up. |
dns |
"show logging and show checkpoint client" |
|
MDNS_HA_ISSU-3-CAP_INVALID_SIZE |
3-Error |
mDNS HA ISSU client capability list is empty. |
The BG3K OIR ISSU client capability exchange list size\n\ is invalid. |
dns |
"show issu capability entries <Client_ID>" |
|
MDNS_HA_ISSU-3-CAP_NOT_COMPATIBLE |
3-Error |
mDNS HA ISSU client capability exchange result incompatible. |
The mDNS HA ISSU client capability exchange has negotiated\n\ as incompatible with the peer. |
dns |
"show issu negotiated capability <Session_ID>" |
|
MDNS_HA_ISSU-3-CAPABILITY |
3-Error |
mDNS HA ISSU client [chars] |
mDNS HA ISSU client observed an error during capability\n\ negotiation. When this error happens there is a mismatch\n\ between the client capability between the active and\n\ standby unit. |
dns |
"show issu capability entries <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated capability <session_id>" |
|
MDNS_HA_ISSU-3-INIT |
3-Error |
mDNS HA ISSU client initialization failed at [chars] error [chars] |
mDNS HA ISSU client could not be initiailzed this will\n\ cause catstrophic failure when ISSU upgrade or downgrade\n\ is performed. |
dns |
LOG_STD_SH_TECH_ACTION |
|
MDNS_HA_ISSU-3-MSG_NOT_OK |
3-Error |
mDNS HA ISSU client message [dec] is not compatible |
mDNS HA ISSU client received an incompatible message\n\ from the peer unit. Since the message is not compatible\n\ it can be processed by this unit |
dns |
"show issu message group <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
MDNS_HA_ISSU-3-MSG_SIZE |
3-Error |
mDNS HA ISSU client failed to get the message size for message [dec] |
mDNS HA ISSU client failed to calculate message size\n\ for the message specified. The mDNS HA ISSU client will not\n\ be able to send message to the standby unit. |
dns |
"show issu message group <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
MDNS_HA_ISSU-3-POLICY |
3-Error |
mDNS HA ISSU client message type [dec] is [chars] |
mDNS HA ISSU client received an message type which it\n\ does not support. The policy is applied to make the session\n\ compatible. |
dns |
"show issu session <client_id>" |
|
MDNS_HA_ISSU-3-SEND_FAILED |
3-Error |
mDNS HA ISSU client failed to send a negotiation message error [dec] |
mDNS HA ISSU client could not send a session negotiation\n\ message to the peer. When there is a problem in the\n\ negotiation the standby unit can not be brought up. |
dns |
"show logging and show checkpoint client" |
|
MDNS_HA_ISSU-3-SESSION |
3-Error |
mDNS HA ISSU client [chars] |
mDNS HA ISSU client observed an error during a session\n\ negotiation with the peer unit. When there is a problem\n\ with the session the standby unit can not be brought up. |
dns |
"show issu capability entries <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated capability <session_id>" |
|
MDNS_HA_ISSU-3-SESSION_UNREGISTRY |
3-Error |
mDNS HA ISSU client failed to unregister session information. Error: [dec] [chars] |
The mDNS HA ISSU client failed to unregister session information. |
dns |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MDNS_HA_ISSU-3-TRANSFORM |
3-Error |
mDNS HA ISSU client [chars] transform failed error [chars] |
mDNS HA ISSU client could not transform the message.\n\ If the transmit transformation failed it means that the\n\ checkpoint message can not be sent to the standby unit.\n\ If the receive transformation failed it means that the\n\ checkpoint message can not be applied on the standby\n\ unit. In both cases the mDNS HA state will not\n\ be indentical with the active unit. |
dns |
"show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
MDNSPROXY-3-API_FAIL_MDNS |
3-Error |
[chars] API failed |
An error occurred while calling the APIs. |
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-CHUNK_MEMORY_FAIL |
3-Error |
Chunk memory allocation failed |
Chunk memory allocation failed for Cache element |
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-INIT_MDNS_FAIL |
3-Error |
[chars] Initialisation failure. |
An internal error occurred during mDNS initialisation. |
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-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" |
|
MDNSPROXY-3-OS_API_FAIL_MDNS |
3-Error |
IOS API [chars] failed |
Encountered an error while calling the API. |
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-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-STATIC_SERVICE_FAIL_MDNS |
3-Error |
Static Service: [chars] |
Encountered an error while processing Static Service. |
mDNS |
LOG_STD_ACTION |
|
MDNSPROXY-4-INIT_MDNS_FAIL |
4-Warning |
[chars] Initialisation failure. |
An internal error occurred during mDNS initialisation. |
mDNS |
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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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_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-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-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_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_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-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-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-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-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-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-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-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-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-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-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-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-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-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-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_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_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-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-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-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-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_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_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-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_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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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 |
|
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 |
|
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-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-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-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 |
|
MDS-2-INIT |
2-Critical |
Error initializing MDS structures |
An error has occurred when the system tried to initialize MDS structures |
- |
LOG_STD_SH_TECH_ACTION |
|
MDS-2-LC_FAILED_IPC_ACK |
2-Critical |
RP failed in getting Ack for IPC message of size [dec] to LC in slot [dec] with sequence [dec] error = [chars] |
The Route Processor has failed in getting IPC acknowledgement |
- |
LOG_STD_SH_TECH_ACTION |
|
MDS-2-LC_FAILED_IPC_OPEN |
2-Critical |
LC in slot [dec] failed to open IPC port to RP error = [chars] |
The linecard has failed to open IPC port towards the Route Processor |
- |
LOG_STD_SH_TECH_ACTION |
|
MDS-2-LC_FAILED_SEND_LC_READY |
2-Critical |
LC in slot [dec] failed to send LC ready to RP error = [chars] |
The linecard has failed to send Ready message to the Route Processor |
- |
LOG_STD_SH_TECH_ACTION |
|
MDS-2-LC_INIT |
2-Critical |
Error initializing linecard |
System resources could not be allocated on the linecard |
- |
LOG_STD_SH_TECH_ACTION |
|
MDS-2-LC_INVALID_HWIDB_INDEX |
2-Critical |
Invalid if_index for HWIDB [chars] |
Invalid if_index for HWIDB |
- |
LOG_STD_SH_TECH_ACTION |
|
MDS-2-LC_INVALID_HWIDBQ_SIZE |
2-Critical |
Invalid Q count value |
Invalid Q count value |
- |
LOG_STD_SH_TECH_ACTION |
|
MDS-2-LC_INVALID_INPUT_IF_INDEX |
2-Critical |
Invalid input if_index 0x[hec] for HWIDB [chars] |
The input hardware IDB interface index is invalid |
- |
LOG_STD_SH_TECH_ACTION |
|
MDS-2-LC_INVALID_INPUT_IFNUM |
2-Critical |
Invalid input if_num 0x[hec] for SWIDB [chars] |
The input software IDB interface number is invalid |
- |
LOG_STD_SH_TECH_ACTION |
|
MDS-2-LC_INVALID_MROUTE_MSG |
2-Critical |
Unknown message [dec] received from RP |
Unrecognized route event has been sent down from the Route Processor |
- |
LOG_STD_SH_TECH_ACTION |
|
MDS-2-LC_INVALID_MSG |
2-Critical |
Unknown IPC type [dec] received from RP |
Unrecognized message type has been sent down from the Route Processor |
- |
LOG_STD_SH_TECH_ACTION |
|
MDS-2-LC_INVALID_SIZE |
2-Critical |
Invalid IPC size [dec] received from RP |
Unrecognized IPC size has been sent down from the Route Processor |
- |
LOG_STD_SH_TECH_ACTION |
|
MDS-2-LC_INVALID_SWIDB_IFNUM |
2-Critical |
Invalid if_num for SWIDB [chars] |
Invalid if_num for SWIDB |
- |
LOG_STD_SH_TECH_ACTION |
|
MDS-2-LC_INVALID_SWIDBQ_SIZE |
2-Critical |
Invalid Q count value |
Invalid Q count value |
- |
LOG_STD_SH_TECH_ACTION |
|
MDS-2-LC_NOIPCBUFFR |
2-Critical |
No IPC buffers available for messages to be sent to the RP |
The system has run out of buffers for IPC |
- |
LOG_STD_SH_TECH_ACTION |
|
MDS-2-LC_SPDLISTCORR |
2-Critical |
SPD list corrupted |
The list of Selective Packet Discard is corrupted |
- |
LOG_STD_SH_TECH_ACTION |
|
MDS-2-LC_SWIDB_UPDATE_NULL_MVRF |
2-Critical |
LC received swidb update for if_number [hec] [chars] tableid [hec]. |
The linecard received a software IDB update from the Route Processor specifying a multicast VRF table ID for which no multicast VRF exists in the linecard. |
- |
LOG_STD_SH_TECH_ACTION |
|
MDS-2-RP |
2-Critical |
[chars] |
The Route Processor either cannot allocate memeory or it has missing data |
- |
LOG_STD_SH_TECH_ACTION |
|
MDS-2-RP_FAILED_IPC_CREATE |
2-Critical |
RP failed in creating IPC port error = [chars] |
The Route Processor failed to create MDS Interprocess Communications port |
- |
LOG_STD_SH_TECH_ACTION |
|
MDS-2-RP_RCV_IPC_ERR_SIZE |
2-Critical |
RP received oversized IPC size = [dec] type = [dec] |
The Route Processor has received oversized IPC message from the linecard |
- |
LOG_STD_SH_TECH_ACTION |
|
MDS-3-ROUTECOUNT_ZERO |
3-Error |
Multicast route count reached zero |
The running count of multicast routes reached zero when it should be non-zero. |
- |
"An error in maintaining the multicast route count has occurred." LOG_STD_ACTION |
|
MDS-4-ROUTELIMIT |
4-Warning |
Current count of [dec] exceeds multicast route-limit of [dec] |
The number of multicast routes exceeds the configured maximum allowed. New routes cannot be added unless the configuration is changed. |
- |
"If multicast traffic is of any priority among the traffic carried by this router then use the 'ip multicast route-limit' command to increase the number of multicast routes. Otherwise no action is required." |
|
MDS-4-ROUTELIMIT_ATTEMPT |
4-Warning |
Attempt to exceed multicast route-limit of [dec] |
The number of multicast routes equals the configured maximum allowed. New routes cannot be added unless the configuration is changed. |
- |
"If multicast traffic is of any priority among the traffic carried by this router then use the 'ip multicast route-limit' command to increase the number of multicast routes. Otherwise no action is required." |
|
MDT-2-MVPN_BGP_LEAF_AD_UPDATE_CHUNK_ERR |
2-Critical |
Error initializing MVPN BGP Leaf AD Update chunk |
Chunk memory for MVPN BGP Leaf AD Update cannot be initialized |
- |
LOG_STD_NO_ACTION |
|
MDT-2-MVPN_BGP_UPDATE_CHUNK_ERR |
2-Critical |
Error initializing MVPN BGP Update chunk |
Chunk memory for MVPN BGP Update cannot be initialized |
- |
LOG_STD_NO_ACTION |
|
MDT-2-MVPN_PE_CHUNK_ERR |
2-Critical |
Error initializing MVPN PE chunk |
Chunk memory for MVPN PE cannot be initialized |
- |
LOG_STD_NO_ACTION |
|
MDT-2-MVPN_REPL_CHUNK_ERR |
2-Critical |
Error initializing MVPN repl db chunks |
Error initializing MVPN repl db chunks |
- |
LOG_STD_NO_ACTION |
|
MDT-2-MVPN_REPL_RADIX_BRANCH_ERR |
2-Critical |
Error initializing MVPN replication branch radix tree |
Internal error |
- |
LOG_STD_NO_ACTION |
|
MDT-2-PE_LSPVIF_CREATE_FAIL |
2-Critical |
[chars] - LSPVIF creation for PE [chars] failed. |
The creation of LSPVIF for a remote PE for strong RPF check has failed. |
mcast-mvpn |
LOG_STD_ACTION |
|
MDT-2-TDB_ID_INIT_FAIL |
2-Critical |
[chars] - Failed initializing tdb id. |
Internal identification number of MVPN tdb cannot be initialized. |
mcast-mvpn |
LOG_STD_ACTION |
|
MDT-2-TDB_ID_MISMATCH |
2-Critical |
[chars] - Mismatch between current tdb id [dec] and synced id [dec]. |
Internal identification number of MVPN tdb is mismatched with synced id. |
mcast-mvpn |
LOG_STD_ACTION |
|
MDT-3-ALLOC_SHOW_ENTRY |
3-Error |
Attempt to allocate show entry for invalid show type [dec] |
The show data type specified by the function attempting to perform a show operation is not a valid type. The show operation can not be performed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MDT-3-BAD_TABLEID |
3-Error |
Invalid VRF table ID 0x[hec] |
This MVPN configuration command can not be executed because \n\ the received VRF table ID is not valid. |
- |
LOG_STD_ACTION |
|
MDT-3-IDB_ROUTE_DISABLE |
3-Error |
Tunnel Groups: [chars]: [chars] |
BGP AD update contains tunnel type that's different from the locally configured group to tunnel type mapping. |
ip-tunnels |
"Ensure the group to tunnel type mapping is consistent between PE peers." |
|
MDT-3-INVALID_ADDR_COPY |
3-Error |
Invalid or incompatible address copy type [dec] and length [dec] |
An IP address copy operation for an MVPN data state transition failed because the specified address type and address length did not match any defined IP address category. |
- |
LOG_STD_SH_TECH_ACTION |
|
MDT-3-LPBACK_CONV |
3-Error |
Loopback Conversion Failed. |
Installation of required MVPN forwarding interfaces may have \n\ failed for one or more MDT groups. |
- |
LOG_STD_ACTION |
|
MDT-3-NO_CORE_TDB |
3-Error |
No core table descriptor block for MVPN address family [chars] |
MVPN configuration commands can not be executed because \n\ there are is no MVPN core table for the specified address family. |
- |
LOG_STD_ACTION |
|
MDT-3-NODETAIL |
3-Error |
Missing detail information |
The detailed information requested for the currently executing \n\ show command was not collected as required. The show command \n\ processing is aborted. |
- |
LOG_STD_ACTION |
|
MDT-3-NOPDB |
3-Error |
No protocol descriptor block for MVPN protocol type [dec] |
MVPN configuration commands can not be executed because \n\ there are no functions registered for handling this command \n\ address family. |
- |
LOG_STD_ACTION |
|
MDT-3-POOL_GROUP |
3-Error |
Failed attempt to find MDT group [chars] in pool for mvrf [chars] |
An attempt to allocate an MDT data pool entry on a standby RP using an MDT data group address previously allocated on the active RP has failed. The specified group address does not exist in the group address pool for this MVRF on the standby RP. MVPN traffic may be impeded for this MVRF following an RP failover. |
- |
LOG_STD_ACTION |
|
MDT-3-SHUTDOWN_ERR |
3-Error |
Error in [chars] : [chars] |
Internal error |
mcast-vpn |
LOG_STD_RECUR_ACTION |
|
MDT-3-WAVL_INIT_FAIL |
3-Error |
Failed initializing [chars] wavl tree. |
wavl_init failed. |
mcast-mvpn |
LOG_STD_ACTION |
|
MDT-4-LBSRC |
4-Warning |
MDT [chars] uses source address [inet] from a non-loopback interface |
The local peering interface used to set up MDT tunnel is not a\n loopback Interface. This may cause blackholes if the interface is\n in the outgoing list of the MDT group. |
- |
"Change the configuration of bgp update-source and use a loopback\n" "interface as the local peering interface" |
|
MDT-4-MVPN_ROUTELIMIT_ATTEMPT |
4-Warning |
MVPN update caused attempt to exceed multicast route-limit of [dec] |
The number of multicast routes equals the configured maximum allowed.\n\ A new multicast route creation request that was triggered by an\n\ MVPN BGP/PIM update from a peering PE router by an MVPN\n\ configuration action on this router or by an MDT default/data\n\ transition on this router could not be added. No new routes can\n\ be added unless the configuration is changed. |
- |
"If multicast traffic is of any priority among the traffic carried\n\ by this router then use the 'ip multicast route-limit' command to\n\ increase the number of multicast routes.\n\ Otherwise no action is required." |
|
MDT-4-NO_GROUP_LINK |
4-Warning |
MDT entry [chars]:[inet][inet] linked by source but not linked by group |
- |
- |
- |
|
MDT-4-NO_TDB_PDB |
4-Warning |
No protocol descriptor block for TDB at 0x[hec]: [chars] failed |
The operation can not be executed because the MVPN table is not \n\ fully initialized |
- |
LOG_STD_ACTION |
|
MDT-4-PIM_TDB_TRANS |
4-Warning |
MVPN TDB to [chars] translation failed for AF [chars] |
The operation can not be executed because a NULL or incorrect \n\ MVPN table was specified. |
- |
LOG_STD_ACTION |
|
MDT-4-RD_CONFLICT |
4-Warning |
MDT entry [chars]:[inet][inet] received an update for RD [chars] |
- |
- |
- |
|
MDT-4-TDB_WALK_ERR |
4-Warning |
Error Walking list of TDB's |
Walk of all pim tdb's associated with a given pim pdb cannot be completed |
- |
LOG_STD_NO_ACTION |
|
MDT-4-UPDATED_RD_CONFLICT |
4-Warning |
MDT entry [chars]:[inet][inet] received an update for RD [chars] |
- |
- |
- |
|
MDT-4-VRFSRC |
4-Warning |
The source interface of the MDT tunnels [chars] is not in the global table |
The local peering interface must not be an interface in a VRF. |
- |
"Change the configuration of bgp update-source and use a loopback\n" "interface in the global table" |
|
MDT-5-DATA_MDT_REUSED |
5-Notice |
Data MDT [chars] is reused |
A data MDT group can be reused by a particular host that sources\n\ user traffic in an VPN if all pre-defined data MDT groups are used |
- |
LOG_STD_NO_ACTION |
|
MDT-5-TDB_ID_NOT_INIT |
5-Notice |
[chars] - tdb id not initialized. |
Internal identification number of MVPN tdb is not initialized. |
- |
LOG_STD_NO_ACTION |
|
MEDIATRACE-3-I_INFRA |
3-Error |
Initiator Error: [chars] |
An internal error in initiator event processing has occurred. |
mediatrace |
"This may be a transient error condition. If the " "problem persists contact your Cisco technical " "support representative." |
|
MEDIATRACE-3-I_PROFILE_DB |
3-Error |
Operation failure in profile DB |
Profile DB operation failed. |
mediatrace |
"Contact your Cisco technical support " "representative." |
|
MEDIATRACE-3-I_SES_IAMP |
3-Error |
session = [dec]: reason = [chars] |
An error occurred while Mediatrace application was trying to initiate a session send a data fetch request or terminate the session. |
mediatrace |
"Contact your Cisco technical support " "representative." |
|
MEDIATRACE-3-I_SES_SOFT |
3-Error |
session = [dec]: reason = [chars] |
Session failure due to some Mediatrace internal software error. |
mediatrace |
"Contact your Cisco technical support " "representative." |
|
MEDIATRACE-3-R_DELIVERY_FAILED |
3-Error |
Response delivery to target IP [chars] failed for global |
This message is seen when IAMP or RSVP reported problem in sending response for Responder. |
mediatrace |
"Turn on 'debug iamp error' to see more details on what IAMP layer is " "complaining." |
|
MEDIATRACE-3-R_REQ_DROPPED_QMAXED |
3-Error |
Request with global session id [dec] was dropped because |
The maximum number of Responder sessions has been exceeded and there is no more sessions available for new periodical requests. This request was dropped. |
mediatrace |
"Assess the router resource to see if it can take on more " "sessions as more sessions can take away some CPU and memory from " "the system. If it's OK to increase the max sessions for the " "local node then use the `mediatrace responder max-sessions' CLI " "to increase the local Responder's max sessioins. As a good practice " "keep session life cycle shorter so to share the sessions." |
|
MEDIATRACE-3-R_REQ_DUPLICATED_GSID |
3-Error |
Request with duplicated global session id [dec] was detected from |
There should not be 2 concurrent sessions with identical global session id from the same Initiator node. If found it's an error condition. |
mediatrace |
"To help resolve this error condition capture the " "output of `show run all | sec mediatrace' and send it to " "Cisco Technical Support." |
|
MEDIATRACE-3-R_SESS_ALLOC_FAILED |
3-Error |
memory allocation of session object failed for [chars] for |
Before a request can be processed a session object needs to be allocated first. This message reports that such malloc failed due to the system is momentarily short of memory. |
mediatrace |
"Check system memory situation and do minor tunings at various " "feature CLIs so to reduce memory demand level." |
|
MEDIATRACE-3-R_SESS_FORCED_REMOVAL |
3-Error |
User issued a forced shutdown. All Mediatrace Responder sessions are removed. |
Only user can issue the `no mediatrace responder force' CLI. This is a non-graceful shutdown of Mediatrace sessions. All sessions are purged when this message is seen. |
mediatrace |
"Only when some inconsistency in session count is observed between " "Mediatrace Responder and VM or when the local node is under " "stress and need to remove all Mediatrace sessions." |
|
MEDIATRACE-3-R_SESS_REMOVE_FAILED |
3-Error |
failed to remove a session with global session id [dec] from queue |
This message indicates that there is a problem in removing the concerned session from the session queue. This is very rare. |
mediatrace |
"Do nothing. If this message is seen more than once then user can " "`no mediatrace responder force' CLI to purge the session queue." |
|
MEDIATRACE-3-R_SESS_SERVL_ALLOC_FAILED |
3-Error |
memory allocation of servlet object failed for global session id [dec] |
Before a request can be processed a servlet memory object needs to be allocated first. This message reports that such memory allocation failed because the system is momentarily short of memory. |
mediatrace |
"Check system memory situation and do minor tunings at various " "feature CLIs so to reduce memory demand level." |
|
MEDIATRACE-3-R_SNMP_COMM_STR_MISSING |
3-Error |
'snmp-server community public ro' is not configured or access is denied. session id [dec]. |
Some Mediatrace Initiator has sent System Data requests to this node but the snmp get requests have failed because the running config is missing the CLI 'snmp-server community public ro' or there is additional config blocking read access. |
mediatrace |
"Configure a snmp server community to allow requests using 'snmp-server " "community public RO' command or check no other configuration is blocking " "SNMP reads." |
|
MEDIATRACE-4-I_SES_RESTART |
4-Warning |
session = [dec]: [chars] |
A condition affecting normal Mediatrace session operation detected. Session needs to be restarted. |
mediatrace |
"Reschedule the session identified by giving " "no mediatrace schedule command followed by " "mediatrace schedule command." |
|
MEDIATRACE-4-R_EMPTY_REQ |
4-Warning |
request has empty payload. |
For unknown reason a request is received with empty payload. |
mediatrace |
"Do nothing. This is a very rare but harmless event." |
|
MEDIATRACE-4-R_RC_INTF_DAMPENING |
4-Warning |
Dampening IAMP event [chars] received for global session id [dec]. |
To prevent path flip flop and cause unnecessary stop and re-start on monitoring objects any same subsequent route change or interface change event is subject to a dampening timer before required actions are taken by Responder for the impacted sessions. During the dampening window same kind of event notice will be ignored. |
mediatrace |
"Start from using RSVP related CLI to troubleshoot why flip flop on " "a route is happening." |
|
MEDIATRACE-4-R_RC_INTF_EVENT |
4-Warning |
IAMP event [chars] is received for [chars]. |
When RSVP-TP layer detects a route change or interface change for the local node IAMP relays the notice as IAMP_EVENT_TYPE_RC_LOCAL or IAMP_EVENT_TYPE_IF_CHANGE notice to Responder. Responder will search all impacted sessions to stop and re-start the monitoring. |
mediatrace |
"Do nothing. This message is emitted when detecting a rare RSVP " "product behavior. Mediatrace is designed to handle this notice." |
|
MEDIATRACE-5-I_SES_START |
5-Notice |
Local-ID = [dec] Global-ID = [dec] [chars] |
A new mediatrace session is scheduled. |
mediatrace |
"This is notification of Mediatrace session start " "no action is required." |
|
MEDIATRACE-5-R_SESS_DOWN |
5-Notice |
Responder received a SESSION_DOWN event for [chars] |
When Initiator removes a configured session via IAMP it informs RSVP to tear down the session object and hence SESSION_DOWN notice is propagated down the path to all Responders. |
mediatrace |
"Do nothing. This is part of normal behavior." |
|
MEDIATRACE-6-I_SES_EVENT |
6-Information |
session = [dec]: ignored event: [dec] |
This is informational. The ignored event number is printed. |
mediatrace |
"Do nothing." |
|
MEDIATRACE-6-R_SESS_PERIODICAL_CREATE_SUCCESS |
6-Information |
New periodical session with global session id [dec] is added. |
This message is produced when a new periodical session is configured for a new request with specified global session id. |
mediatrace |
"Do nothing." |
|
MEDIATRACE-6-R_SESS_REMOVE_ALL_DVMC_SESSIONS |
6-Information |
No more active sessions at the moment. DVMC API was called to purge all Mediatrace sessions. |
This is only an informational message. This message is produced after informing DVMC that there is no more active sessions in Mediatrace Responder. |
mediatrace |
"Do nothing." |
|
MEDIATRACE-6-R_SESS_TRANSIENT_REMOVE_SUCCESS |
6-Information |
A transient session of [chars] with global session id [dec] successfully |
This is an informational syslog message for reporting that an one-shot transient request sessions is successfully removed. |
mediatrace |
"Do nothing." |
|
MEM_BLK-2-CTXERROR |
2-Critical |
The context information 0x%8x is not valid. |
An application to the memory block manager has passed \n\ either a context pointer that is not valid. |
memblkmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
MEM_BLK-2-MEMBLKERROR |
2-Critical |
Memory block 0x%8x is not valid. |
An application to the memory block manager has passed \n\ a memory block that is not valid. |
memblkmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
MEM_BLK-2-MEMFREEERROR |
2-Critical |
Memory block 0x%8x has already been freed. |
An application to the memory block manager has attempted \n\ to free or lock a memory block that is not allocated. |
memblkmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
MEM_BLK-2-MEMORDINALERROR |
2-Critical |
The memory block manager has detected an ordinal error.\n\ Memory block 0x%8x has an ordinal of 0x%4x and a size of 0x%4x.\n\ Its corresponding lower sibling memory block 0x%8x has \n\ an ordinal of 0x%4x and a size of 0x%4x. |
The lower sibling ordinal should be equal to the \n\ difference between the higher sibling's ordinal and \n\ size. |
memblkmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
MEM_BLK-2-MEMTWINBLKERROR |
2-Critical |
An attempt to coalesce memory block 0x%8x with its \n\ sibling memory block 0x%8x has failed because the sibling\n\ block is not valid. |
An attempt to coalesce two memory blocks\n\ has failed because a memory block is not valid. |
memblkmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
MEM_DDR-0-MS_ERR |
0-Emergency |
DDR Memory Select error detected at 0x%08x |
This error is detected if the address from the memory request does \n\ not fall into any of the enabled programmed chip select address \n\ ranges. This could be a DDR configuration error or some application is\n\ trying to access an address for which the target is DDR but it's not \n\ within the configured address range |
- |
LOG_STD_ACTION |
|
MEM_DDR-1-AC_ERR |
1-Alert |
DDR automatic calibration error detected at 0x%08x |
This error is set if the memory controller detects an error during\n\ its training sequence. This kind of an error is not one that the DDR\n\ Ctrl shouldn't report under its normal operating conditions and \n\ when it does it most probably indicates a malfunctioning DDR module\n\ that needs replacement. |
- |
LOG_STD_ACTION |
|
MEM_ECC-1-BADADDR_MBE |
1-Alert |
Invalid MBE dram address: 0x%08x latched by ECC Ctrl |
The address latched by the ECC Ctrl when detecting an MBE is not a\n\ valid dram address. This kind of an error is not one that the\n\ ECC Ctrl shouldn't report under its normal operating conditions\n\ and when it does it most probably indicates a malfunctioning\n\ ECC Ctrl that needs replacement. |
- |
LOG_STD_ACTION |
|
MEM_ECC-2-BADADDR_SBE |
2-Critical |
Invalid ECC SBE dram address: 0x%08x latched by ECC Ctrl |
The address latched by the ECC Ctrl when detecting a SBE is not a\n\ valid dram address. This kind of an error is not one that the\n\ ECC Ctrl shouldn't report under its normal operating conditions\n\ and when it does it most probably indicates a malfunctioning\n\ ECC Ctrl that needs replacement. |
- |
LOG_STD_ACTION |
|
MEM_ECC-2-MALLOC |
2-Critical |
Attempt to malloc [dec] bytes for the ECC error log failed.\n ECC errors will only be reported and not recorded.\n |
Malloc for the ECC error log failed. If system has only 32Mbytes of memory an upgrade would be advisable or is recommended. |
- |
LOG_STD_ACTION |
|
MEM_ECC-2-MBE |
2-Critical |
Multiple bit error detected at 0x%08x |
A multi-bit uncorrectable error was detected on a CPU read from DRAM. |
- |
LOG_STD_ACTION |
|
MEM_ECC-2-MBE |
2-Critical |
Multiple bit error detected at 0x%08x |
A multi-bit uncorrectable error was detected on a CPU read from DRAM. |
- |
LOG_STD_ACTION |
|
MEM_ECC-2-MBE_RMW |
2-Critical |
Multiple bit error detected\nat 0x%08x on a read-modify-write cycle |
A multi-bit uncorrectable error was detected during a read-modify- write cycle on a CPU read from DRAM for a non 8-byte access. |
- |
LOG_STD_ACTION |
|
MEM_ECC-2-MBE_RMW |
2-Critical |
Multiple bit error detected\nat 0x%08x on a read-modify-write cycle |
A multi-bit uncorrectable error was detected during a read-modify- \n\ write cycle on a CPU read from DRAM for a non 8-byte access. |
- |
LOG_STD_ACTION |
|
MEM_ECC-2-PARITY |
2-Critical |
Parity error on CPU write to address: 0x%08x |
Bad parity on data was detected by the ECC Ctrl during a CPU write operation. |
- |
LOG_STD_ACTION |
|
MEM_ECC-2-PARITY |
2-Critical |
Parity error on CPU write to address: 0x%08x |
Bad parity on data was detected by the ECC Ctrl during a CPU\n\ write operation. |
- |
LOG_STD_ACTION |
|
MEM_ECC-2-PARITY_INFO |
2-Critical |
Parity error was detected on the \nfollowing bytes of a double word: [chars] [chars] [chars] |
Indicates which bytes of a 64 bit word had bad parity that caused the ECC Ctrl to generated an interrupt. |
- |
LOG_STD_ACTION |
|
MEM_ECC-3-BADADDR_MBE |
3-Error |
Invalid MBE dram address: 0x%08x latched by ECC Ctrl |
The address latched by the ECC Ctrl when detecting an MBE is not a valid dram address. This kind of an error is not one that the ECC Ctrl shouldn't report under its normal operating conditions and when it does it most probably indicates a malfunctioning ECC Ctrl that needs replacement. |
- |
LOG_STD_ACTION |
|
MEM_ECC-3-BADADDR_MBE_RMW |
3-Error |
Invalid MBE dram address: 0x%08x latched by ECC Ctrl\n during a RMW cycle |
The address latched by the ECC Ctrl when detecting an MBE during a Read-Modify-Write cycle isn't a valid dram address. This kind of an error is not one that the ECC Ctrl shouldn't report under its normal operating conditions and when it does it most probably indicates a malfunctioning ECC Ctrl that needs replacement. |
- |
LOG_STD_ACTION |
|
MEM_ECC-3-BADADDR_SBE |
3-Error |
Invalid SBE dram address: 0x%08x latched by ECC Ctrl |
The address latched by the ECC Ctrl when detecting a SBE is not a valid dram address. This kind of an error is not one that the ECC Ctrl shouldn't report under its normal operating conditions and when it does it most probably indicates a malfunctioning ECC Ctrl that needs replacement. |
- |
LOG_STD_ACTION |
|
MEM_ECC-3-BADADDR_SBE_RMW |
3-Error |
Invalid SBE dram address: 0x%08x latched by ECC Ctrl\n during a RMW cycle |
The address latched by the ECC Ctrl when detecting an SBE during a Read-Modify-Write cycle isn't a valid dram address. This kind of an error is not one that the ECC Ctrl shouldn't report under its normal operating conditions and when it does it most probably indicates a malfunctioning ECC Ctrl that needs replacement. |
- |
LOG_STD_ACTION |
|
MEM_ECC-3-SBE |
3-Error |
Single bit error detected and corrected at 0x%08x |
A single-bit correctable error was detected on a read from DRAM. 'show ecc' can be used to dump Single-bit errors logged thus far. |
- |
LOG_STD_ACTION |
|
MEM_ECC-3-SBE_HARD |
3-Error |
Single bit *hard* error detected at 0x%08x |
A single-bit uncorrectable error [hard error] was detected on a CPU read from DRAM. 'show ecc' will dump the Single-bit errors logged thus far and will also indicate detected hard error address locations. |
- |
"Monitor system through 'show ecc' and replace DRAM if too many such errors." |
|
MEM_ECC-3-SBE_LIMIT |
3-Error |
Single bit error detected and corrected\nat 0x%08x |
A single-bit correctable error was detected on a CPU read from DRAM. |
- |
LOG_STD_ACTION |
|
MEM_ECC-3-SBE_RMW |
3-Error |
Single bit error detected and corrected at\n0x%08x on a read-modify-write cycle |
A single-bit correctable error was detected on during a read-modify- write cycle on a CPU read from DRAM for a non 8-byte access. 'show ecc' can be used to dump Single-bit errors logged thus far. |
- |
LOG_STD_ACTION |
|
MEM_ECC-3-SBE_RMW_HARD |
3-Error |
Single bit *hard* error detected at\n0x%08x on a read-modify-write cycle |
A single-bit uncorrectable hard error was detected during a read-modify- write cycle on a CPU read from DRAM for a non 8-byte access. <CmdBold>show ecc<noCmdBold> can be used to dump Single-bit errors logged thus far. |
rsp gsr-diags |
"Monitor system through <CmdBold>show ecc<noCmdBold> and replace DRAM" " if too many such errors occur." |
|
MEM_ECC-3-SBE_RMW_LIMIT |
3-Error |
Single bit error detected and corrected at 0x%08x on a read-modify-write cycle |
A single-bit correctable error was detected on during a read-modify- write cycle on a CPU read from DRAM for a non 8-byte access. 'show ecc' can be used to dump Single-bit errors logged thus far. |
- |
LOG_STD_ACTION |
|
MEM_ECC-3-SYNDROME_MBE |
3-Error |
8-bit Syndrome for the detected Multi-bit error: 0x[hec] |
The 8-bit syndrome for detected Multi-bit error. This value does not indicate the exact positions of the bits in error but can be used to approximate their positions. |
- |
LOG_STD_ACTION |
|
MEM_ECC-3-SYNDROME_MBE |
3-Error |
8-bit Syndrome for the detected Multi-bit error: 0x[hec] |
The 8-bit syndrome for detected Multi-bit error. This value does not\n\ indicate the exact positions of the bits in error but can be used to \n\ approximate their positions. |
- |
LOG_STD_ACTION |
|
MEM_ECC-3-SYNDROME_SBE |
3-Error |
8-bit Syndrome for the detected Single-bit error: 0x[hec] |
The 8-bit syndrome for detected single-bit error. This value does not indicate the exact positions of the bits in error but can be used to approximate their positions. |
- |
LOG_STD_ACTION |
|
MEM_ECC-3-SYNDROME_SBE_LIMIT |
3-Error |
8-bit Syndrome for the detected Single-bit error: 0x[hec] |
The 8-bit syndrome for detected single-bit error. This value does not indicate the exact positions of the bits in error but can be used to approximate their positions. |
- |
LOG_STD_ACTION |
|
MEM_MGR-2-DRAM_POOL_CREATE_ERR |
2-Critical |
return code [dec] |
Creation of public DRAM memory pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
MEM_MGR-2-DUP_DRAM_POOL_CREATE |
2-Critical |
pool exists |
Request to create public DRAM memory pool failed because pool already exists. |
cpp-ucode |
LOG_STD_ACTION |
|
MEM_MGR-2-DUP_SRAM_POOL_CREATE |
2-Critical |
pool exists |
Request to create public SRAM memory pool failed because pool already exists. |
cpp-ucode |
LOG_STD_ACTION |
|
MEM_MGR-2-ELEMENT_CORRUPT |
2-Critical |
pool handle 0x[hec] addr 0x5x magic value 0x[hec] ref cnt [dec] |
Memory element has been corrupted. |
cpp-ucode |
LOG_STD_ACTION |
|
MEM_MGR-2-POOL_CORRUPT |
2-Critical |
pool handle 0x[hec] magic value 0x[hec] |
Memory pool data structure has been corrupted. |
cpp-ucode |
LOG_STD_ACTION |
|
MEM_MGR-2-SRAM_POOL_CREATE_ERR |
2-Critical |
return code [dec] |
Creation of public SRAM memory pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
MEM_MGR-3-DESTROY_PARM_ERR |
3-Error |
pool handle 0x[hec] |
Request to delete memory pool failed due to bad parameter value. |
cpp-ucode |
LOG_STD_ACTION |
|
MEM_MGR-3-FREE_PARM_ERR |
3-Error |
pool handle 0x[hec] addr 0x[hec] |
Memory deallocation request failed due to bad parameter value. |
cpp-ucode |
LOG_STD_ACTION |
|
MEM_MGR-3-LOCK_MAX_REF_CNT |
3-Error |
pool handle 0x[hec] addr 0x[hec] |
Request to lock memory pool element failed due to reference count for element already being at the maximum value. |
cpp-ucode |
LOG_STD_ACTION |
|
MEM_MGR-3-LOCK_MAX_REF_CNT |
3-Error |
- |
- |
- |
- |
|
MEM_MGR-3-LOCK_PARM_ERR |
3-Error |
pool handle 0x[hec] addr 0x[hec] |
Request to lock memory pool element failed due to bad parameter value. |
cpp-ucode |
LOG_STD_ACTION |
|
MEM_MGR-3-MALLOC_NO_MEM |
3-Error |
pool handle 0x[hec] size [dec] |
Memory pool allocation request failed due to insufficient memory being available. |
cpp-ucode |
LOG_STD_ACTION |
|
MEM_MGR-3-MALLOC_PARM_ERR |
3-Error |
pool handle 0x[hec] size [dec] |
Memory allocation request failed due to bad parameter value. |
cpp-ucode |
LOG_STD_ACTION |
|
MEM_MGR-3-MEM_MGR_EXCEED_MAX |
3-Error |
memory pool exceeds maximum [dec] bytes allowed. |
An attempt was made to allocate a buffer\n\ from the specified memory pool which has\n\ reached its maximum limit |
- |
LOG_STD_ACTION |
|
MEM_MGR-3-MEM_MGR_INVALID |
3-Error |
The Memory Management code encounters an invalid parameter. |
It appears that the Memory Management code has\n\ received an invalid parameter from its caller. |
- |
"Copy the error message exactly has it appears\n\ and report it to your technical support\n\ representative." |
|
MEM_MGR-3-MEM_MGR_NOMEM |
3-Error |
Out of memory |
System out of memory. |
- |
LOG_STD_ACTION |
|
MEM_MGR-3-POOL_APPEND_PARM_ERR |
3-Error |
pool handle 0x[hec] addr 0x[hec] size [dec] |
Append of additional memory to pool failed due to bad parameter value. |
cpp-ucode |
LOG_STD_ACTION |
|
MEM_MGR-3-POOL_CREATE_PARM_ERR |
3-Error |
addr 0x[hec] size [dec] |
Creation of memory pool failed due to bad parameter value. |
cpp-ucode |
LOG_STD_ACTION |
|
MEM_MGR-3-POOL_STATS_PARM_ERR |
3-Error |
pool handle 0x[hec] stats addr 0x[hec] |
Read of memory pool statistics failed due to bad parameter value. |
cpp-ucode |
LOG_STD_ACTION |
|
MEM_PROXY-3-PROXY_IPC_PAK_ALLOC_FAILED |
3-Error |
- |
Allocation of IPC packet failed. |
cpp-ucode |
LOG_STD_ACTION |
|
MEM_PROXY-3-PROXY_IPC_SEND_FAILED |
3-Error |
[chars] |
Could not send IPC request for more memory. |
cpp-ucode |
LOG_STD_ACTION |
|
MEM-2-MPLS_TE_PCALC |
2-Critical |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
MEMPOOL-3-IPC |
3-Error |
[chars] [chars] |
An IPC error has occurred on polling the Enhanced MempoolMIB |
- |
"Copy the error message exactly as it appears on the\n\ console or in the system log contact your Cisco technical support\n\ representative and provide the representative with the gathered\n\ information." |
|
MEMSCAN-2-BSSREG |
2-Critical |
Parity error0x[hec] found in imagebss region |
A parity error was found in the BSS region of memory. |
mem |
"Schedule a reboot of the system to clear memory AS SOON AS POSSIBLE. If this parity error is touched in normal operation of the router the router will crash. If more parity errors are found at this address after the reboot replace the DRAM in the router or the processor board." |
|
MEMSCAN-2-DATAREG |
2-Critical |
Parity error0x[hec] found in imagedata region |
A parity error was found in the data region of memory. |
mem |
"Schedule a reboot of the system to clear memory AS SOON AS POSSIBLE. If this parity error is touched in normal operation of the router the router will crash. If more parity errors are found at this address after the reboot replace the DRAM in the router or the processor board." |
|
MEMSCAN-2-TEXTREG |
2-Critical |
Parity error0x[hec] found in imagetext region |
A parity error was found in the text region of memory. |
mem |
"Schedule a reboot of the system to clear memory AS SOON AS POSSIBLE. If this parity error is touched in normal operation of the router the router will crash. If more parity errors are found at this address after the reboot replace the DRAM in the router or the processor board." |
|
MEMSCAN-3-DUPERR |
3-Error |
Another parity error0x[hec] found in bolck0x[hec]. Not scrubed |
Multiple errors have been found in a meory block. |
mem |
"Schedule a reboot of the system to clear memory AS SOON AS POSSIBLE. If this parity error is touched in normal operation of the router the router will crash. If more parity errors are found at this address after the reboot replace the DRAM in the router or the processor board." |
|
MEMSCAN-3-INHEAD |
3-Error |
Parity error0x[hec] found in block header |
A parity error has been found in a critical field of a block header. |
mem |
"Schedule a reboot of the system to clear memory AS SOON AS POSSIBLE. If this parity error is touched in normal operation of the router the router will crash. If more parity errors are found at this address after the reboot replace the DRAM in the router or the processor board." |
|
MEMSCAN-3-INPREV |
3-Error |
Parity error0x[hec] found in block field **previous |
A parity error has been found in a critical field of a block header. |
mem |
"Schedule a reboot of the system to clear memory AS SOON AS POSSIBLE. If this parity error is touched in normal operation of the router the router will crash. If more parity errors are found at this address after the reboot replace the DRAM in the router or the processor board." |
|
MEMSCAN-3-INUSE |
3-Error |
Parity error0x[hec] found in busy bolck0x[hec] |
A parity error has been found in a busy block which cannot be scrubbed nor moved to the bad list. |
mem |
"Schedule a reboot of the system to clear memory AS SOON AS POSSIBLE. If this parity error is touched in normal operation of the router the router will crash. If more parity errors are found at this address after the reboot replace the DRAM in the router or the processor board." |
|
MEMSCAN-3-NOHEAD |
3-Error |
No block header for parity error0x[hec] until 0x[hec] |
A parity error has been found for an address which has no block header |
mem |
"Schedule a reboot of the system to clear memory AS SOON AS POSSIBLE. If this parity error is touched in normal operation of the router the router will crash. If more parity errors are found at this address after the reboot replace the DRAM in the router or the processor board." |
|
MEMSCAN-3-UNKNOWN |
3-Error |
Parity error0x[hec] found in otherunknown region |
A parity error was found in other region of memory. |
mem |
"Schedule a reboot of the system to clear memory AS SOON AS POSSIBLE. If this parity error is touched in normal operation of the router the router will crash. If more parity errors are found at this address after the reboot replace the DRAM in the router or the processor board." |
|
MEMSCAN-6-LINKED |
6-Information |
Error0x[hec] block0x[hec] linked size [dec] |
A parity error was found in a free block which could not\n\be scrubbed. The Free block has been moved to a bad list so that it cannot be used again. |
mem |
"Schedule a reboot of the system to clear memory. If\n\more parity errors are found at this address after the reboot replace the DRAM in the router or the processor board." |
|
MEMSCAN-6-MSCRUBED |
6-Information |
Parity error0x[hec] scrubed multiple times |
Multiple parity errors found at this address. |
mem |
"Take down router and replace DRAM" |
|
MEMSCAN-6-SCRUBED |
6-Information |
Parity error0x[hec] scrubed |
Memory parity error found and scrubed. |
mem |
"None" |
|
MEMSCAN-6-SPLIT |
6-Information |
Error0x[hec] block0x[hec] split bad block0x[hec] linked size 0x[hec] |
A parity error was found in a free block which could not be scrubbed. The free block has been fragmented and the fragment with the parity error has been moved to a dead list so that it cannot be used again. |
mem |
"Schedule a reboot of the system to clear memory. If more parity errors are found at this address after the reboot replace the DRAM in the router or the processor board." |
|
METOPT_DI-1-ALARM |
1-Alert |
[chars]:[chars] |
The specified alarm has occured or cleared |
- |
"The recommeded action is to repair the source of the alarm." |
|
METOPT_DI-3-INTERNAL_ERROR |
3-Error |
[chars][dec]:[chars] |
The Metro Optical CDL defect indiation subsystem encountered\n\ an internal software error. The error message contains text\n\ useful to identify the nature of the problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
METOPT_DRV-3-REPROGRAM_ERROR |
3-Error |
[chars]\n |
The Metro Optical Reprogram driver encountered\n\ an error. The error message contains text\n\ useful to identify the nature of the problem. |
Reprogram |
"Retry the reprogram of the card. If the reprogram fails again remove the card and reinsert it. If the card does not come up save the console log and contact Cisco TAC for further assistance." |
|
METOPT_DRV-3-TP_INTERNAL_ERROR |
3-Error |
[chars][dec]:[chars] [dec] |
The Metro Optical Transponder driver subsystem encountered\n\ an internal software error. The error message contains text\n\ useful to identify the nature of the problem. |
Xponder |
"Please verify whether the Interface exists in the\n\ system. If the card is OIR'ed or EOIR is done then we will see\n\ such NULL strings in the system.Ensure that the interface exists in\n\ the system" |
|
METOPT-2-FABRIC_PORTFAIL |
2-Critical |
Port Fail event received from [chars] switch card on fabric port associated with interface [chars]\n |
Fabric Port Failed due to some problem\n |
- |
LOG_STD_ACTION |
|
METOPT-2-NOMEMORY |
2-Critical |
No memory available for [chars] |
An attempt at memory allocation failed. |
- |
"Try these actions to remedy the problem:\n\ \n\ Add memory.\n\ \n\ Disable some features.\n\ \n\ Apply filtering to decrease the size of system data structures - the\n\ routing table for example.\n\ \n\ In general reduce other system activities to ease memory demands. If\n\ conditions warrant upgrade to a larger memory configuration." |
|
METOPT-2-NOPAKBUFFER |
2-Critical |
No packet buffer available for [chars] interface to send this packet to higher layer |
An attempt to allocate packet buffer failed. |
- |
"Try these actions to remedy the problem:\n\ \n\ Reload the system.\n\\n\ Perform a CPU switchover if you\n\ have a redundant CPU system" |
|
METOPT-2-ZEROLEN_MSG |
2-Critical |
Zero length while [chars] linecard. Datalen [dec]\n |
Due to some internal error a zero length transaction is being made from/to the Line card |
- |
LOG_STD_ACTION |
|
METOPT-3-IDPROM_MISMATCH |
3-Error |
Mismatch in backplane IDPROM [chars]: Active-side=[dec] Sby-side=[dec] |
There are two backplane IDPROMS. Each is readable by one of the two redundant CPUs. Most IDPROM fields should be programmed by manufacturing to contain identical information. Only the first mismatched field is shown. Use a CLI show command to see additional mismatches. |
- |
LOG_STD_SH_TECH_ACTION |
|
METOPT-3-IDPROM_STR_MISMATCH |
3-Error |
Mismatch in backplane IDPROM [chars]: Active-side=[chars] Sby-side=[chars] |
There are two backplane IDPROMS. Each is readable by one of the two redundant CPUs. Most IDPROM fields should be programmed by manufacturing to contain identical information. Only the first mismatched string is shown. Use a CLI show command to see additional mismatches. |
- |
LOG_STD_SH_TECH_ACTION |
|
METOPT-3-NOACK |
3-Error |
Access to [chars] temperature sensor failed |
Accesses to chassis temperature sensor failed. |
- |
LOG_STD_SH_TECH_ACTION |
|
METOPT-3-NOMAC |
3-Error |
Can't allocate MAC address for interface [dec]/[dec] |
MAC address allocation failed because of an incorrect slot and port combination which exceeds the maximum available hardware |
man-optical-sw |
"Check whether all the available MAC addresses for the system have been allocated" "Make sure that this address is unique or specify MAC addresses for commands such as novell routing that allow the use of this address as a default.\n" LOG_STD_ACTION |
|
METOPT-3-UNEXP_INTR |
3-Error |
Interrupt [chars] not expected masking off |
An interrupt of a certain type was signalled but the \n\ interrupt handler for this type of interrupt is not yet installed. |
- |
"This problem should be self-correcting but indicates either\n\ a hardware or a software defect. If it's a hardware defect\n\ further problems are to be expected. If it's a software\n\ problem certain types of error and alarm conditions may be\n\ left undetected. \n\ Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
METOPT-4-COOKIE |
4-Warning |
Corrupt or missing MAC address cookie using random base [enet]\n |
The contents of MAC address EEPROM are invalid. The system is providing random MAC addresses |
man-optical-sw |
"show rpm eeprom" "\n" LOG_STD_RECUR_ACTION |
|
METOPT-4-NOCPUVER |
4-Warning |
Invalid CPU ID assuming revision 1 |
The CPU ID could not be read from EEPROM.\n\ This is probably due to a hardware failure. |
- |
LOG_STD_ACTION |
|
METOPT-6-DI_ASSERTED |
6-Information |
CDL Defect Indication: [chars] Asserted on interface [chars]\n |
This message indicates some CDL Defect \n\ Indication bits were Asserted on this interface \n |
- |
"Closely monitor CDL Defect Indication Status \n\ if Defect Indication was asserted" |
|
METOPT-6-DI_CLEARED |
6-Information |
CDL Defect Indication: [chars] cleared on interface [chars]\n |
This message indicates CDL Defect \n\ Indication Status Changed\n |
- |
LOG_STD_NO_ACTION |
|
METS-2-INITFAIL |
2-Critical |
Can't start analysis |
The requested operation failed due to lack of resource maybe temporarily |
analysis |
"Reduce system resource/memory usage and retry for the commands." |
|
METS-3-BADMETHOD |
3-Error |
Cannot process [chars] method [dec] |
A method list function encountered a method list that was unknown\n\ or could not be handled. |
analysis |
LOG_STD_ACTION |
|
METS-3-NOREGION |
3-Error |
No region found: [chars] |
Resource failure: No region found. |
analysis |
LOG_STD_ACTION |
|
METS-3-NULLPOOL |
3-Error |
Can't process null pool: [chars] |
Resource failure: Null pool in the region |
analysis |
LOG_STD_ACTION |
|
MFI_LABEL_BROKER-3-DELETE_MOI_FAIL |
3-Error |
Label [dec] in table [dec] [chars] [chars] |
The MFI Label Broker could not honor a request to immediately handle the process restart of the application indicated. It will try to handle it in the background |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this condition " "has been previously reported and resolved in a later release. If not " "gather the output of <CmdBold>show version<NoCmd Bold> " "<CmdBold>show running-config<NoCmdBold> and " "<CmdBold>show mpls infrastructure label-broker ldm<NoCmdBold>" " this latter command is present only when" " <CmdBold>service internal<NoCmdBold> is enabled and contact your Cisco" |
|
MFI_LABEL_BROKER-3-DUPREG_LDM |
3-Error |
[chars] |
An MPLS application is registering multiple times with the label broker. |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this condition " "has been previously reported and resolved in a later release. If not " "gather the output of <CmdBold>show version<NoCmd Bold> and " "<CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
MFI_LABEL_BROKER-3-IMMEDIATE_LDM_RESTART |
3-Error |
application [chars] |
- |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this condition " "has been previously reported and resolved in a later release. If not " "gather the output of <CmdBold>show version<NoCmd Bold> and " "<CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
MFI_LABEL_BROKER-3-INVALID_LABEL |
3-Error |
[dec] |
The MFI Label Broker received a request to allocate an invalid label. |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this condition " "has been previously reported and resolved in a later release. If not " "gather the output of <CmdBold>show version<NoCmd Bold> and " "<CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
MFI_LABEL_BROKER-3-INVALID_LDM |
3-Error |
[dec] |
The MFI Label Broker received a unregistration request from an invalid |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this condition " "has been previously reported and resolved in a later release. If not " "gather the output of <CmdBold>show version<NoCmd Bold> and " "<CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
MFI_LABEL_BROKER-3-INVALID_PARAM |
3-Error |
[chars] |
The MFI Label Broker received an invalid parameter in a request to allocate or free a local label. |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this condition " "has been previously reported and resolved in a later release. If not " "gather the output of <CmdBold>show version<NoCmd Bold> and " "<CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
MFI_LABEL_BROKER-3-INVALID_PID |
3-Error |
LDM[dec] PID[dec] |
The MFI Label Broker received a registration request with invalid PID. |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this condition " "has been previously reported and resolved in a later release. If not " "gather the output of <CmdBold>show version<NoCmd Bold> and " "<CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
MFI_LABEL_BROKER-3-INVALID_PROC_EVT |
3-Error |
[chars][dec][chars][dec] |
The MFI Label Broker received an invalid process event from the IOS-on-Neutrino infrastructure. |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this condition " "has been previously reported and resolved in a later release. If not " "gather the output of <CmdBold>show version<NoCmd Bold> and " "<CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
MFI_LABEL_BROKER-3-LABEL_PROGRAM_FAIL |
3-Error |
Label [dec] in table [dec] for [chars] |
The MFI Label Broker was unable to program the label in question for the mentioned FEC. |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this condition " "has been previously reported and resolved in a later release. If not " "gather the output of <CmdBold>show version<NoCmd Bold> " "<CmdBold>show running-config<NoCmdBold> " "<CmdBold>show mpls forwarding-table internal<NoCmdBold> and contact " "your Cisco technical support representative." |
|
MFI_LABEL_BROKER-3-MULTIPLE_BIND |
3-Error |
Label [dec] in table [dec] [chars] [chars] [p/bm [dec]/0x[hec]]ldm request info: [chars] |
The MFI Label Broker received a request to bind the label to a prefix but the label is already bound to another prefix. |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this condition " "has been previously reported and resolved in a later release. If not " "gather the output of <CmdBold>show version<NoCmd Bold> " "<CmdBold>show running-config<NoCmdBold> and " "<CmdBold>show mpls forwarding-table<NoCmdBold> and contact your Cisco" " technical support representative." |
|
MFI_LABEL_BROKER-3-NO_ACTIVE_LABEL |
3-Error |
[chars] Label [dec] in table [dec] [chars] 0x[hec] |
The MFI Label Broker encountered a situation where there is no currently active label for applications to use for the FEC indicated. |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this condition " "has been previously reported and resolved in a later release. If not " "gather the output of <CmdBold>show version<NoCmd Bold> " "<CmdBold>show running-config<NoCmdBold> " "<CmdBold>show mpls forwarding-table internal<NoCmdBold> and contact " "your Cisco technical support representative." |
|
MFI_LABEL_BROKER-3-NULL_KEY |
3-Error |
- |
The MFI Label Broker received a null key pointer |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this condition " "has been previously reported and resolved in a later release. If not " "gather the output of <CmdBold>show version<NoCmd Bold> and " "<CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
MFI_LABEL_BROKER-3-OS_NOTIFY |
3-Error |
Process id [dec] [chars] error code [dec] |
The MFI Label Broker was unable to notify the operating system about unregistration of the specified process. |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this condition " "has been previously reported and resolved in a later release. If not " "gather the output of <CmdBold>show version<NoCmd Bold> " "<CmdBold>show running-config<NoCmdBold> " "<CmdBold>show mpls infrastructure label-broker ldm<NoCmdBold> and contact " "your Cisco technical support representative." |
|
MFI_LABEL_BROKER-3-UNREG_LDM |
3-Error |
[chars] |
An MPLS application requested label broker services without registering first. |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this condition " "has been previously reported and resolved in a later release. If not " "gather the output of <CmdBold>show version<NoCmd Bold> and " "<CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
MFI-3-BADREADUPDATESIZE |
3-Error |
Read update reply message from RP has bad size: [dec] |
read update message does not match the read message parse result |
mpls-mfi |
LOG_STD_ACTION |
|
MFI-3-CLIENT_INTF |
3-Error |
[chars]: [hec] [hec] |
Client Interface |
mpls-mfi |
LOG_STD_ACTION |
|
MFI-3-EVTLOGCAPTURE |
3-Error |
Event Logger Capture Error [dec] [dec] |
Failure during Event Logger capture |
mpls-mfi |
LOG_STD_ACTION |
|
MFI-3-EVTLOGCLIENT |
3-Error |
Invalid client [dec] |
Invalid client accessed the Event Logger |
mpls-mfi |
LOG_STD_ACTION |
|
MFI-3-EVTLOGCONTROL |
3-Error |
[chars]: [dec] |
General Event Logger Controller error |
mpls-mfi |
LOG_STD_ACTION |
|
MFI-3-EVTLOGREGISTER |
3-Error |
Event Logger Registration Error [dec] [dec] [dec] |
Failure during Event Logger client registration |
mpls-mfi |
LOG_STD_ACTION |
|
MFI-3-LCPULSE |
3-Error |
LC pulse failed: [chars] [dec] |
LC pulse request operation failed |
mpls-mfi |
LOG_STD_ACTION |
|
MFI-3-MFICOMM |
3-Error |
[chars] |
MFI General Communication Module |
mpls-mfi |
LOG_STD_ACTION |
|
MFI-3-MFICOMM2 |
3-Error |
[chars]: [hec] [hec] |
MFI General Communication Module |
mpls-mfi |
LOG_STD_ACTION |
|
MFI-3-MFICOMM3 |
3-Error |
[chars]: [hec] [hec] [hec] |
MFI General Communication Module |
mpls-mfi |
LOG_STD_ACTION |
|
MFI-3-MPLS_MTU_SET |
3-Error |
[chars] [dec] [chars] [chars] [chars] [dec][chars] |
Most drivers will be able to support baby giants and will gracefully drop packets that are too large. Certain drivers will have packet forwarding problems including data corruption. |
mpls-mfi |
"Please increase the interface mtu on all routers connected " "to this interface to the needed mtu size using <CmdBold>mtu<NoCmdBold> <CmdArg>bytes<NoCmdArg> command. " |
|
MFI-3-PNDMSGMGR |
3-Error |
[chars] [chars] [dec] [dec] [dec] |
Only one outstanding request is allowed from same process |
mpls-mfi |
LOG_STD_ACTION |
|
MFI-3-REDISTMGR |
3-Error |
Redistribution Manager: [chars] [hec] |
Redistribution Manager error |
mpls-mfi |
LOG_STD_ACTION |
|
MFI-3-REDISTMGR2 |
3-Error |
Redistribution Manager: [chars] [hec] [hec] |
Redistribution Manager error |
mpls-mfi |
LOG_STD_ACTION |
|
MFI-3-REPLYMSGSIZE |
3-Error |
Reply message is too large: [chars]: [dec] |
read update message won't fit into xdr buffer |
mpls-mfi |
LOG_STD_ACTION |
|
MFI-4-MFICOMM_WARN_1 |
4-Warning |
[chars]: [hec] |
MFI General Communication Module |
mpls-mfi |
LOG_STD_ACTION |
|
MFI-4-NOCLIENTREQ |
4-Warning |
[chars] [chars]: [dec] [dec] [dec] |
Client reply could not find an outstanding request |
mpls-mfi |
LOG_STD_ACTION |
|
MFI-4-REDISTMGR3 |
4-Warning |
Redistribution Manager: [chars] [hec] |
Redistribution Manager error |
mpls-mfi |
LOG_STD_ACTION |
|
MFIB_DB-3-FREE_FREED_TABLE |
3-Error |
%p %p/[chars] as %lu entries %lu ioitems |
- |
- |
- |
|
MFIB_DB-3-LEAKED_OCCUPIED_TABLE |
3-Error |
%p %p/[chars] as %lu entries %lu ioitems |
- |
- |
- |
|
MFIB_DB-3-LEAKED_TABLE |
3-Error |
%p %lx due to discard failure |
- |
- |
- |
|
MFIB_DB-6-INVALID_TABLEID |
6-Information |
Table %p %p/[chars] : [chars] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
MFIB_DB-6-MOFRR_ERROR |
6-Information |
[chars] |
An MoFRR internal error occurred. |
- |
LOG_STD_ACTION |
|
MFIB_IPC-3-MFIB_BAD_MSG_TYPE |
3-Error |
An IPC message was received with an incorrect type [dec]. |
- |
- |
- |
|
MFIB_IPC-3-MFIB_CREATE_PORT_FAILED |
3-Error |
Failed to create local IPC port error = [chars] |
An IPC port could not be created. This may prevent MFIB statistics being gathered from one or more linecards. |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_IPC-3-MFIB_LC_FAILED_IPC_ACK |
3-Error |
RP did not receive Ack for IPC message of type = [dec] error = [chars] |
The Route Processor did not receive and acknowledgement for an IPC message that was sent to a linecard. |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_IPC-3-MFIB_LC_FAILED_IPC_OPEN |
3-Error |
LC in slot [dec] failed to open IPC port to RP error = [chars]. |
The linecard has failed to open IPC port towards the Route Processor. No MFIB statistics will be collected from this line card as a result. |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_IPC-3-MFIB_LC_NO_PROCESS |
3-Error |
The LC failed to create a required process. |
The linecard failed to create a process required to manage linecard IPC connections to the RP. No MFIB statistics will be collected from this linecards |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_IPC-3-MFIB_LC_READY_NOIPC |
3-Error |
LC failed tp allocate IPC buffer to send LC ready slot = [dec] |
The linecard failed to allocate and IPC buffer for the Ready message. MFIB statistics will not be gathered from this linecard. |
- |
LOG_STD_REDUCE_ACTION |
|
MFIB_IPC-3-MFIB_LC_REG_FAIL |
3-Error |
LC failed to register IPC port: [chars] |
The route processor could not register its IPC port. No MFIB statistics will be gathered from linecards. |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_IPC-3-MFIB_LC_SEND_READY_FAILED |
3-Error |
LC in slot [dec] failed to send LC Ready MSG to RP error = [chars]. |
The linecard has failed to send a Ready message to the Route Processor. No MFIB statistics will be collected from this linecard. |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_IPC-3-MFIB_RCV_FAIL |
3-Error |
An IPC message was received with an error status: [chars]. |
An IPC message was received but could not be processed due to an IPC error condition. |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_IPC-3-MFIB_RP_FAILED_BAD_LC_SLOT |
3-Error |
RP failed to send IPC message to linecard in slot [dec]. |
The Route Processor could not send an IPC message to a linecard because the slot number is incorrect. |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_IPC-3-MFIB_RP_FAILED_IPC_ACK |
3-Error |
LC did not receive Ack for IPC message of size = [dec] type = [dec] error = [chars]. |
The linecard did not receive an acknowledgement for an IPC message it sent to the Route Processor. |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_IPC-3-MFIB_RP_FAILED_IPC_SEND |
3-Error |
IPC message for stats or rates failed code = [dec] |
Sending of IPC message for stats or rates failed possibly because of congestion. Stats or rates values may be temporarily affected. |
- |
LOG_STD_RECUR_ACTION |
|
MFIB_IPC-3-MFIB_RP_FAILED_LC_PORT_INFO |
3-Error |
RP failed to create linecard IPC port info structure slot = [dec] |
The Route Processor has failed to create an IPC port for distributed statistics collection |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_IPC-3-MFIB_RP_FAILED_LC_PORT_OPEN |
3-Error |
RP failed to open an IPC port for communication with the linecard in slot [dec]. |
The Route Processor has failed to open an IPC port for distributed statistics collection. |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_IPC-3-MFIB_RP_NO_MEMORY |
3-Error |
The RP failed to allocate an internal data structure. |
The Route Processor failed to allocate memory required to managed linecard IPC connections. No MFIB statistics will be collected from linecards. |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_IPC-3-MFIB_RP_NO_PROCESS |
3-Error |
The RP failed to create a required process. |
The Route Processor failed to create a process required to manage linecard IPC connections. No MFIB statistics will be collected from linecards. |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_IPC-3-MFIB_RP_REG_FAIL |
3-Error |
RP failed to register IPC port: [chars] |
The route processor could not register its IPC port. No MFIB statistics will be gathered from linecards. |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_IPC-4-MFIB_UNRECOGNISED_MSG |
4-Warning |
An IPC message was received with an unrecognised subtype [dec] |
- |
- |
- |
|
MFIB_MRIB-3-FAILED_CONNID_FIND |
3-Error |
For [chars] %p [[chars]/[chars]] in table %p %p/[chars] |
- |
- |
- |
|
MFIB_MRIB-3-FAILED_CONNID_LOCK |
3-Error |
Failure code [dec] on attempt to lock connid 0x[hec] for interface [chars] of entry [chars] in table ID 0x[hec]. Actual connid is 0x[hec] |
Failed to acquire an MFIB lock for a connection ID on the standby RP or on an LC. Forwarding for the affected multicast flow may be affected after an RP failover. |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_MRIB-3-FAILED_CONNID_RESERVE |
3-Error |
For [chars] %p [[chars]/[chars]] in table %p %p/[chars] |
- |
- |
- |
|
MFIB_MRIB-3-FAILED_ENTRY_CREATE |
3-Error |
For [chars] in table %p %p/[chars] |
- |
- |
- |
|
MFIB_MRIB-3-FAILED_ENTRY_POST |
3-Error |
For [chars] in table %p %p/[chars] with [chars]%lx |
- |
- |
- |
|
MFIB_MRIB-3-FAILED_IOITEM_CREATE |
3-Error |
For [chars] [chars] in table %p %p/[chars] |
- |
- |
- |
|
MFIB_MRIB-3-FAILED_IOITEM_POST |
3-Error |
For [chars] [chars] in table %p %p/[chars] with [chars]%lx |
- |
- |
- |
|
MFIB_MRIB-3-FAILED_TABLE_FILTER |
3-Error |
In table %p %p/[chars] with [chars]%lx |
The MFIB failed to configure an MRIB connection. |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_MRIB-3-FAILED_TABLE_OPEN |
3-Error |
In table %p %p/[chars] with [chars]%lx |
An MFIB table failed to connect to the MRIB |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_MRIB-3-FAILED_TABLE_REGISTER |
3-Error |
In table %p %p/[chars] with [chars]%lx |
An MFIB table failed to register with the MRIB |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_MRIB-3-FAILED_TABLE_UNBIND |
3-Error |
In table %p %p/[chars] with [chars]%lx |
An MFIB table failed to disconnect from the MRIB |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_MRIB-3-FAILED_WIRE_FIND |
3-Error |
For [chars] %p [[chars]/[chars]] in table %p %p/[chars] |
- |
- |
- |
|
MFIB_MRIB-3-FAILED_WIRE2IF_NUMBER |
3-Error |
For [chars] %p [[chars]/[chars]] in table %p %p/[chars] |
- |
- |
- |
|
MFIB_MRIB-3-GENERATED_NULLIFHNDL |
3-Error |
For [chars] [chars] in table %p %p/[chars] |
- |
- |
- |
|
MFIB_MRIB-3-GIVEN_NULLIFHNDL |
3-Error |
For [chars] in table %p %p/[chars] |
- |
- |
- |
|
MFIB_MRIB-3-TABLE_MESSAGE |
3-Error |
In table %p %p/[chars] : [chars] |
MFIB has encountered an error while processing a message sent by MRIB. |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_MRIB-3-TABLE_UPDATE |
3-Error |
In table %p %p/[chars] : [chars] |
MFIB has encountered an error while processing an MRIB database update. |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_PLTF-3-ANNOT_TOO_LONG |
3-Error |
[chars] %p [dec] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
MFIB_PLTF-3-CALLBACK_RETURN_INVALID |
3-Error |
[chars]. %p %p %p |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
MFIB_PLTF-3-ENTRY_HANDLE_BAD |
3-Error |
[chars]. %p |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
MFIB_PLTF-3-ENTRY_LOCK_FAIL |
3-Error |
[chars]. [chars] entry %p [chars] [%p %p/[chars]] |
- |
- |
- |
|
MFIB_PLTF-3-ENTRY_UNLOCK_FAIL |
3-Error |
[chars]. [chars] entry %p [chars] [%p %p/[chars]] |
- |
- |
- |
|
MFIB_PLTF-3-HANDLE_CONSTRAINT |
3-Error |
[chars] %p |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
MFIB_PLTF-3-IOITEM_DUPLICATE_ADD |
3-Error |
[chars] ioitem [chars] [chars] [%p %lx/[chars]] |
- |
- |
- |
|
MFIB_PLTF-3-IOITEM_HANDLE_BAD |
3-Error |
[chars]. %p |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
MFIB_PLTF-3-IOITEM_LOCK_FAIL |
3-Error |
[chars]. [chars] ioitem %p [chars] [chars] [%p %p/[chars]] |
- |
- |
- |
|
MFIB_PLTF-3-IOITEM_UNLOCK_FAIL |
3-Error |
[chars]. [chars] ioitem %p [chars] [chars] [%p %p/[chars]] |
- |
- |
- |
|
MFIB_PLTF-3-SBINIT |
3-Error |
Error initializing [chars] subblock data structure. [chars] |
Initialization of the specified subblock data structure could not be accomplished. |
- |
LOG_STD_ACTION |
|
MFIB_PLTF-3-TABLE_HANDLE_BAD |
3-Error |
[chars]. %p |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
MFIB_PLTF-3-TABLE_LOCK_FAIL |
3-Error |
[chars]. [chars] table %p %p %p/[chars] |
- |
- |
- |
|
MFIB_PLTF-3-TABLE_UNLOCK_FAIL |
3-Error |
[chars]. [chars] table %p %p %p/[chars] |
- |
- |
- |
|
MFIB_PLTF-3-TRANSACTION_MEMORY |
3-Error |
[dec] [dec] |
Failed to allocate memory for platform transaction. |
- |
LOG_STD_REDUCE_ACTION |
|
MFIB_PLTF-3-UPDATE_SET_MEMORY |
3-Error |
[chars] %p -> [chars] [%p %p/[chars]] |
Failed to allocate memory for platform transaction. |
- |
LOG_STD_REDUCE_ACTION |
|
MFIB_PLTF-3-XDRISSUREGERROR |
3-Error |
ISSU client [chars] [dec] entity [dec] failed ISSU registration: [chars] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
MFIB_PLTF-7-ENTRY_DUPLICATE_ADD |
7-Debug |
[chars] entry [chars] [%p %p/[chars]] |
- |
- |
- |
|
MFIB_STATS-3-MFIB_STATS_FAILED_CREATE_MUTEX |
3-Error |
Hardware stats destructor failed to create watched boolean |
Hardware stats failed to create a mutex when deleting a hardware stats structure. |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_STATS-3-MFIB_STATS_FAILED_GET_MUTEX |
3-Error |
Hardware stats destructor failed to push event list |
Hardware stats failed to hold a mutex when deleting a hardware stats structure. |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_STATS-3-MFIB_STATS_LC_FAILED_GET_IPC_MSG |
3-Error |
Linecard failed allocating ipc message buffer |
The Linecard failed in allocating buffer for sending statistics |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_STATS-3-MFIB_STATS_LC_FAILED_SEND_MSG |
3-Error |
Linecard failed in sending msg to the Route Processor error = [chars] |
The Linecard has failed in sending statistics message to the Route Processor |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_STATS-3-MFIB_STATS_LC_MSG_TOO_BIG |
3-Error |
Linecard failed to return counters message buffer too small. |
The Linecard has failed to return counters because the minimum message size exceeds the maximum IPC buffer size. |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_STATS-3-MFIB_STATS_RP_FAILED_GET_IPC_MSG |
3-Error |
RP failed allocating ipc message buffer for linecard slot = [dec] |
The Route Processor failed in allocating buffer for getting linecard statistics |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_STATS-3-MFIB_STATS_RP_FAILED_REPLY_MSG |
3-Error |
RP received reply with error status from linecard slot = [dec] |
The Route Processor has received reply with error in statistics message from a linecard |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB_STATS-3-MFIB_STATS_RP_FAILED_SEND_IPC_MSG |
3-Error |
RP failed in sending ipc msg to the linecard slot = [dec] error = [chars] |
The Route Processor has failed in sending a statistics message to the Linecard |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB-2-NOMEMORY |
2-Critical |
Out of memory for IP multicast MFIB. Used: %lu Free: %lu |
Insufficient memory for the IP multicast forwarding\n\ information base. Multicast packets may not be properly\n\ routed. |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB-3-ADJ_GSB_INIT |
3-Error |
- |
Could not initialise the adjacency GSB memory pool |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB-3-ADJ_GSB_REGISTER |
3-Error |
- |
Could not register an adjacency GSB identifier |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB-3-DECAP_OCE_CREATION_FAILED |
3-Error |
Decap OCE creation failed for [chars] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
MFIB-3-ILLEGALARGS |
3-Error |
Illegal arguments - [chars] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
MFIB-3-MFIB_CTXT_DEPTH_EXCEEDED |
3-Error |
- |
MFIB has exceeded maximum number of switching contexts |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB-3-MRIB_PROCESS |
3-Error |
[chars][chars] |
The MFIB process which intefaces with the MRIB failed to start. The MFIB will be unusable. |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB-3-SBINIT |
3-Error |
Error initializing [chars] subblock data structure. [chars] |
Initialization of the specified subblock data structure could not be accomplished. |
- |
LOG_STD_ACTION |
|
MFIB-3-SR_ADJ_GSB_INIT |
3-Error |
- |
Could not initialise the SR adjacency GSB memory pool |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB-3-SR_ADJ_GSB_REGISTER |
3-Error |
- |
Could not register an SR adjacency GSB identifier |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB-3-SR_ADJ_INCORRECT_ADD |
3-Error |
A different MFIB Service Reflect adj is being added |
A different SR adjacency subblock is being added to the \ adjacency without first removing the existing one. This \ indicates that SR forwarding may no longer work correctly |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB-3-WIRE_LOOKUP_OR_ALLOC_FAILED |
3-Error |
Lookup or allocation of MFIB wire failed |
Lookup or allocation of MFIB wire failed |
- |
LOG_STD_ACTION |
|
MFIB-6-MFIB_HEADER_LIMIT_EXCEEDED |
6-Information |
[dec] at [chars] |
MFIB attempted to exceed maximum number of replicated packet header buffers |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB-6-MFIB_POOL_GETBUFFER_FAILURE |
6-Information |
- |
MFIB has failed in an attempt to retrieve a particular type of memory. The MFIB will continue using another memory area |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB-6-PAK_TOO_SHORT |
6-Information |
Packet too short from [chars] datagram size [dec] tl [dec] |
The MFIB failed to set offset within packet |
- |
LOG_STD_SH_TECH_ACTION |
|
MFIB-6-PAK_TTL_ONE_V4 |
6-Information |
IPV4 Multicast Packet received with ttl <= 1 |
An IP non-linklocal multicast packet received with ttl 1 |
- |
LOG_STD_NO_ACTION |
|
MFIB-6-PAK_TTL_ONE_V6 |
6-Information |
IPV6 Multicast Packet received with ttl <= 1 |
An IPv6 non-linklocal multicast packet received \ with ttl 1 |
- |
LOG_STD_NO_ACTION |
|
MFIERROR-3-MPLS_TE |
3-Error |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
MGCP_RF-3-RF_REG_FAILED |
3-Error |
RF registration for the MGCP RF client failed with return code [dec] |
The MGCP RF client failed to register properly with RF. This should not occur and should be reported. |
mgcp-redundancy |
LOG_STD_ACTION |
|
MGCP_RF-3-SEND_MSG_FAILED |
3-Error |
The MGCP RF client failed to send a message to the peer system op [dec] |
The MGCP RF client could not send a message to the peer Standby or Active system and bulk synchronization may not be complete. |
mgcp-redundancy |
LOG_STD_ACTION |
|
MGCP-2-INTERNAL_CRITICAL |
2-Critical |
[chars] |
The MGCP subsystem encountered an internal software\n\ error. The error message contains text which can be used\n\ to help identify the nature of the problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
MGCP-3-INTERNAL_ERROR |
3-Error |
[chars] |
The MGCP subsystem encountered an internal software\n\ error. The error message contains text which can be used\n\ to help identify the nature of the problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
MGCP-4-INTERNAL_WARNING |
4-Warning |
[chars] |
The MGCP subsystem encountered an internal software\n\ error. The error message contains text which can be used\n\ to help identify the nature of the problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
MIC-2-RF_REG_FAIL |
2-Critical |
Failed to register with RF status [dec]. |
The MIC failed to register with RF. |
- |
LOG_STD_NO_ACTION |
|
MIC-3-INVALID_CLIENT_TYPE |
3-Error |
Caller specified invalid MIC client type [dec]. |
The MIC client type is out of range. |
- |
LOG_STD_NO_ACTION |
|
MICA-1-BOOTFLASH |
1-Alert |
[chars] |
MICA modem FIRMWARE download file is not found in BOOTFLASH. |
as |
"Record the reason at the end of the message and report the problem." |
|
MICA-1-BRDCRASHED |
1-Alert |
Slot [dec] MICA Board Crashed Going to Recover |
A MICA modem board has crashed. The router will automatically\n\ restart and reload it. |
as |
LOG_STD_RECUR_ACTION |
|
MICA-1-BRDINITFAIL |
1-Alert |
Slot [dec] MICA Board Init Failed : [chars] |
A MICA modem board has failed to reset and initialize. |
as |
LOG_STD_RECUR_ACTION |
|
MICA-3-BADIMAGE |
3-Error |
Cannot download version [chars] on module [dec] |
The block information that is necessary to download modem firmware\n\ was missing for the indicated firmware version. |
- |
LOG_STD_ACTION |
|
MICA-3-BADMODEM |
3-Error |
Modem [dec] went bad |
Run-time checks for modem health determined that the indicated modem\n\ was no longer functional due to a hardware or software error. |
- |
LOG_STD_RECUR_ACTION |
|
MICA-3-BADMODEMNUM |
3-Error |
Error: Trying to access an invalid modem [dec] |
The requested operation could not be accomplished because of a bad modem number. Call your technical support representative for assistance |
modem-management |
LOG_STD_ACTION |
|
MICA-3-BADMODULE |
3-Error |
Module in socket [dec] is of unknown type board-id=[dec] |
The modem module in the socket indicated by the message is\n\ inappropriate for the modem card it is on. |
- |
LOG_STD_SH_TECH_ACTION |
|
MICA-3-BADMSG |
3-Error |
Bad msg from modem[dec]/[dec]: opcode/arg = 0x[hec]/0x[hec] |
A message received from the modem was not expected by the driver.\n\ If the hardware is newer than the software this could mean a\n\ new response cannot be handled. Otherwise it is possible that\n\ data corruption has occurred in the hardware. |
as |
LOG_STD_SH_TECH_ACTION |
|
MICA-3-BADPARAM |
3-Error |
Modem [dec]: [chars] while handling [chars]. |
The modem state machine received a bad parameter as indicated\n\ by the error message. |
- |
LOG_STD_RECUR_ACTION |
|
MICA-3-BADRXCOUNT |
3-Error |
Bad count from modem [dec]: count = [dec] |
A message was received from the indicated modem which had an\n\ illegal count . |
- |
LOG_STD_RECUR_ACTION |
|
MICA-3-BADRXOPCODE |
3-Error |
Bad mail message opcode from modem [dec]: opcode = 0x[hec] |
A message was received from the indicated modem which had an\n\ illegal opcode. |
- |
LOG_STD_RECUR_ACTION |
|
MICA-3-BADTXOPCODE |
3-Error |
Bad tx mail message opcode = 0x[hec] |
A message was attempted to be transmitted to the indicated\n\ modem which had an illegal opcode. |
- |
LOG_STD_RECUR_ACTION |
|
MICA-3-BOARD_DL_FAIL |
3-Error |
Slot [dec] Boardware download failed because of [chars] all modems are marked bad |
- |
as |
"Try powercycling the router. " LOG_STD_RECUR_ACTION |
|
MICA-3-CONTIGUOUS |
3-Error |
Contiguous packet sent for transmit |
A software error occurred resulting in an unexpected packet being\n\ set up for transmission and the packet was dropped. |
- |
LOG_STD_RECUR_ACTION |
|
MICA-3-CRASH |
3-Error |
Runtime error on MICA module [dec] Hex [dec] |
A software error occurred on the modem firmware executing on the\n\ indicated modem module. |
- |
LOG_STD_ACTION |
|
MICA-3-INBAND_UNKNOWN_OPCODE |
3-Error |
Inband message with unknown opcode received from modem [dec] -- payload 0x[hec] 0x[hec] 0x[hec] 0x[hec] 0x[hec] 0x[hec] 0x[hec] 0x[hec] |
An inband message with unknown opcode was received from the \n\ indicated modem |
- |
LOG_STD_RECUR_ACTION |
|
MICA-3-INBANDNAK |
3-Error |
Inband NAK from modem [dec]/[dec]: opcode = 0x[hec] |
A inband message sent to the indicated modem was rejected. |
as |
LOG_STD_RECUR_ACTION |
|
MICA-3-INBANDNAK |
3-Error |
Inband NAK from modem [dec] -- payload 0x[hec] 0x[hec] 0x[hec] 0x[hec] 0x[hec] 0x[hec] 0x[hec] 0x[hec] |
A inband message sent to the indicated modem was rejected. |
- |
LOG_STD_RECUR_ACTION |
|
MICA-3-INVALID_PARAM |
3-Error |
Mica sent invalid stack address or length MICA module [dec] addr 0x[hec] length [dec] |
Runtime error occured on MICA MICA sent invalid stack address or \n\ length. |
- |
LOG_STD_ACTION |
|
MICA-3-MODEMBAD |
3-Error |
Modem number [dec]/[dec] is bad Error code is [hec] |
Message from the MICA modem driver indicates that the modem is bad. |
as |
LOG_STD_ACTION |
|
MICA-3-NAK |
3-Error |
NAK from modem [dec] in state [dec] -- payload 0x[hec] |
A message sent to the indicated modem was rejected. |
- |
LOG_STD_RECUR_ACTION |
|
MICA-3-NOBOARDWARE |
3-Error |
Boardware is not bundled in this IOS image |
- |
as |
LOG_STD_ACTION |
|
MICA-3-NOBUF |
3-Error |
No msg buffer for Modem[dec]/[dec] in [chars]:[dec] |
The MICA software was unable to allocate a packet buffer. The system\n\ may be out of memory. |
as |
LOG_STD_SH_TECH_ACTION |
|
MICA-3-NOENTRIES |
3-Error |
Exhausted [chars] DMA entries for module [dec] |
- |
- |
LOG_STD_RECUR_ACTION |
|
MICA-3-NOIDB |
3-Error |
No IDB structure for modem [dec] |
A software structure was found in an unexpected state during\n\ run-time for the indicated modem. |
- |
LOG_STD_ACTION |
|
MICA-3-NOMAILELEMENTS |
3-Error |
Exhausted free mail elements for modem_num [dec]. Current use: [dec] |
The software structures that are used to receive and transmit\n\ messages from the MICA modems were temporarily exhausted. |
- |
LOG_STD_RECUR_ACTION |
|
MICA-3-NOMEMORY |
3-Error |
MSG_TRACEBACK|MSG_PROCESS |
- |
- |
- |
|
MICA-3-NOMEMORY |
3-Error |
MSG_TRACEBACK|MSG_PROCESS |
- |
- |
- |
|
MICA-3-NOPPPCTX |
3-Error |
No PPP context structure for modem [dec] |
A software structure was found in an unexpected state during\n\ run-time for the indicated modem. |
- |
LOG_STD_ACTION |
|
MICA-3-NORXPAK |
3-Error |
Static receive paktype unavailable |
A software structure was found in an unexpected state during\n\ run-time for the indicated modem. |
- |
LOG_STD_ACTION |
|
MICA-3-NOTPLX |
3-Error |
Bad vendor id from PLX 9060SD -- value was 0x[hec] |
A hardware error occurred involving the PCI interface chip. |
- |
LOG_STD_ACTION |
|
MICA-3-NOTTY |
3-Error |
No TTY structure for modem [dec] |
A software structure was found in an unexpected state during\n\ run-time for the indicated modem. |
- |
LOG_STD_ACTION |
|
MICA-3-PORTWARE |
3-Error |
Bad version [chars] portware: [chars] |
Modem firmware of the indicated version bundled into the modem \n\ card image did not pass the sanity tests done to verify a \n\ firmware image. |
- |
LOG_STD_ACTION |
|
MICA-3-PWDNLDTO |
3-Error |
Portware download timed out for module [dec] |
The diagnostic message that is expected back from a MICA modem\n\ after successful download and initialization of the modem firmware\n\ was never received. |
- |
LOG_STD_ACTION |
|
MICA-3-RCR |
3-Error |
Slot [dec] Looking for [hec] but reading [hec] |
The MICA driver timed out waiting for a specific response. |
as |
LOG_STD_RECUR_ACTION |
|
MICA-3-RESTART |
3-Error |
Attempting restart of modem module [dec] |
The indicated modem module suffered a run-time error and had to \n\ be reset and an attempt is now being made to restart the modem \n\ module. |
- |
LOG_STD_NO_ACTION |
|
MICA-3-TXDESCLIMIT |
3-Error |
Packet descriptor count [dec] exceeds transmit ring size |
The packet to be transmitted needed more descriptors than are\n\ available on the transmit ring and the packet was dropped. |
- |
LOG_STD_RECUR_ACTION |
|
MICA-3-UNEXPEVT |
3-Error |
Modem[dec]/[dec] Unexpected Event: [chars] in [chars] |
An error was reported from the modem hardware which was not\n\ expected by the driver. |
as |
"The seriousness of this problem has not been determined.\n\ If the determination is not obvious from the error message\n\ provided from the device follow these instructions: " LOG_STD_ACTION |
|
MICA-3-UNKNINBAND |
3-Error |
Unknown inband msg from modem [dec]/[dec]: opcode = 0x[hec] |
An unknown inband message is received from the indicated modem. |
as |
LOG_STD_RECUR_ACTION |
|
MICA-4-DCCHANRESET |
4-Warning |
OOB comand in Slot[dec] took too long to complete. Reseting port |
The OOB port was locked because a command took too long\n\ to complete. The port was recovered by reseting internal\n\ datastructures. |
as |
"If there are frequent occurances of this event\n\ turn on debug modem oob for the slot and report\n\ the problem with these logs" |
|
MICA-4-PWDL_FILENOTFOUND |
4-Warning |
Slot [dec] Module numbers [chars] are running default IOS image file [chars] not found in flash |
- |
as |
LOG_STD_NO_ACTION |
|
MICA-5-BOARDWARE_RUNNING |
5-Notice |
Slot [dec] is running boardware version [chars].[chars].[chars].[chars] |
This is a status message to indicate the successful start-up\n\ of the on-board software boardware on one MICA modem port. |
as |
LOG_STD_NO_ACTION |
|
MICA-5-MODEM_RECOVERY |
5-Notice |
Modem [dec]/[dec] is being recovered by [chars] |
Modem is consecutively failing to Connect so being recovered |
as |
"None" |
|
MICA-5-MODEM_RECOVERY_FAIL |
5-Notice |
Modem [dec]/[dec] recovery failed: [chars] |
Modem recovery failed |
as |
"None" |
|
MICA-5-UNKNMODEM |
5-Notice |
Unknown modem module in Slot [dec] - Modem Module [dec] |
A MICA modem module has an uninitialized cookie. This can be due to\n\ a manufacturing error or more likely it is due to a problem on\n\ the modem module itself. |
as |
"Please seek a replacement for this modem module. For\n\ some reason this module no longer is able to identify itself" LOG_STD_NO_ACTION |
|
MICA-6-INIT |
6-Information |
Modem module [dec] initialized |
The indicated modem module was successfully initialized. |
- |
LOG_STD_NO_ACTION |
|
MK5-1-BADRING |
1-Alert |
msgtxt_badringsize |
An internal software error occurred. |
- |
"If either of these messages recur call your technical support\n\ representative for assistance." |
|
MK5-1-INITFAIL |
1-Alert |
msgtxt_initfail |
The hardware failed to initialize correctly. |
- |
"Repair or replace the controller." |
|
MK5-1-INITNOPPRIM |
1-Alert |
Unit [dec] initialization failure - No CSR1_PPRIM_INIT_CONF csr1 = 0x%04x |
The hardware failed to initialize correctly. |
- |
"Repair or replace the controller." |
|
MK5-1-INITUERR |
1-Alert |
Unit [dec] initialization CSR1_UERR failure csr1=0x%04x |
The hardware failed to initialize correctly. |
- |
"Repair or replace the controller." |
|
MK5-1-MEMERR |
1-Alert |
msgtxt_memoryerror |
A network serial interface detected a hardware problem. |
- |
"Repair or replace the controller." |
|
MK5-1-NOMEMORY |
1-Alert |
msgtxt_nomemory |
The requested operation could not be accomplished because of a low\n\ memory condition. |
- |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
MK5-3-OUTENCAP |
3-Error |
Unit [dec] bad output packet encapsulation: 0x[hec] |
An internal software error occurred. |
- |
"If either of these messages recur call your technical support\n\ representative for assistance." |
|
MK5-3-PLOSTERR |
3-Error |
Unit [dec] provider primitive lost csr0=0x%04x csr1=0x%04x |
A network serial interface detected a hardware problem. |
- |
"Repair or replace the controller." |
|
MK5-3-PPRIMERR |
3-Error |
Unit [dec] unexpected provider primitive csr0=0x%04x csr1=0x%04x |
A network serial interface detected a hardware problem. |
- |
"Repair or replace the controller." |
|
MK5-3-SPURPPRIMERR |
3-Error |
Unit [dec] spurious provider primitive interrupt csr0=0x%04x csr1=0x%04x |
A network serial interface detected a hardware problem. |
- |
"Repair or replace the controller." |
|
MK5-3-UPRIMERR |
3-Error |
Unit [dec] user primitive error csr0=0x%04x csr1=0x%04x |
A network serial interface detected a hardware problem. |
- |
"Repair or replace the controller." |
|
MK5-5-LINEFLAP |
5-Notice |
Unit [dec] excessive modem control changes |
Too many modem control interrupts have been received. The port was\n\ disabled to prevent excessive use of the CPU. |
- |
"Check the cable on the serial port." |
|
MKA-3-CAK_DERIVE_FAILURE |
3-Error |
[chars] : [dec] Unable to derive CAK for RxSCI [chars] AuditSessionID [chars] |
Internal failure - MKA failed to derive the Connectivity Association Key CAK from the received MSK through EAP |
mka |
"`debug mka trace` and `debug mka error` may help " "to diagnose the problem internal failure." |
|
MKA-3-CKN_DERIVE_FAILURE |
3-Error |
[chars] : [dec] Unable to derive CKN for RxSCI [chars] AuditSessionID [chars] |
Internal failure - MKA failed to derive the Connectivity Association Key Name CKN from the received EAP |
mka |
"`debug mka trace` and `debug mka error` may help " "to diagnose the problem internal failure." |
|
MKA-3-DUPLICATE_AUTH_MGR_HANDLE |
3-Error |
[chars] Received a new SESSION_START request with Auth-Mgr Handle |
MKA received a SESSION_START request from the IOS Authentication Manager Auth-Mgr with an Auth-Mgr Handle |
mka |
"File a defect for the dot1x-ios component." |
|
MKA-3-HASH_KEY_GENERATE_FAILURE |
3-Error |
[chars] : [dec] Unable to generate MACsec Hash Key AN [dec] for RxSCI [chars] |
Internal failure - MKA failed to generate the MACsec Hash Key for the MKA Session with the given RxSCI Audit Session ID and CKN. The Hash Key is used by MACsec to authenticate frames i.e. provide integrity checking support and is installed in the Rx/Tx |
mka |
"`debug mka trace` and `debug mka error` may help " "to diagnose the problem internal failure." |
|
MKA-3-ICK_DERIVE_FAILURE |
3-Error |
[chars] : [dec] Unable to derive ICK for RxSCI [chars] AuditSessionID [chars] |
Internal failure - MKA failed to derive the Integrity Check Value ICV Key ICK from the derived CAK & CKN |
mka |
"`debug mka trace` and `debug mka error` may help " "to diagnose the problem internal failure." |
|
MKA-3-INTERNAL_ERR |
3-Error |
[chars] : [dec] Internal MKA Error - failed to [chars] for RxSCI [chars] |
The MKA Session identified by the given RxSCI Audit Session ID and CKN encountered an internal error specified by the given action. |
mka |
"Provide the traceback and if possible " "`debug mka trace` and `debug mka error` output " "internal error." |
|
MKA-3-INVALID_ANNOUNCEMENT_PARAM_SET |
3-Error |
[chars] : [dec] Announcement Paramter Set was invalid in a MKPDU for |
MKA failed to process the Announcement Parameter Set of a received MKPDU. |
mka |
"No action required internal error." |
|
MKA-3-INVALID_BASIC_PARAM_SET |
3-Error |
[chars] : [dec] Basic Paramter Set was invalid in a MKPDU for |
MKA failed to process the Basic Parameter Set of a received MKPDU. |
mka |
"No action required internal error." |
|
MKA-3-INVALID_CA |
3-Error |
CA entry not found while [chars]. |
MKA was unable to find the CA entry during the indicated action. This is an internal error. |
mka |
"Provide the traceback and if possible " "`debug mka trace` and `debug mka error` output " "internal error." |
|
MKA-3-INVALID_CAK |
3-Error |
[chars] : [dec] CAK was invalid while [chars] for RxSCI [chars] |
The MKA Session identified by the given RxSCI Audit Session ID and CKN failed to perform the indicated action because of an invalid CAK i.e. zero CAK. |
mka |
"Provide the traceback and if possible " "`debug mka trace` and `debug mka error` output " "internal error." |
|
MKA-3-INVALID_CKN |
3-Error |
[chars] : [dec] CKN was invalid while [chars] for RxSCI [chars] |
The MKA Session identified by the given RxSCI and Audit Session ID failed to perform the indicated action because of an invalid CKN i.e. zero CKN. |
mka |
"Provide the traceback and if possible " "`debug mka trace` and `debug mka error` output " "internal error." |
|
MKA-3-INVALID_DIST_SAK_PARAM_SET |
3-Error |
[chars] : [dec] Distributed SAK Paramter Set was invalid in a MKPDU |
MKA failed to process the Distributed SAK Parameter Set of a received MKPDU. |
mka |
"No action required internal error." |
|
MKA-3-INVALID_PARAM_SET |
3-Error |
[chars] : [dec] Unknown Parameter Set in a MKPDU for RxSCI [chars] |
MKA Session failed to process an Unknown Parameter Set of a received MKPDU. |
mka |
"No action required internal error." |
|
MKA-3-INVALID_PEER_LIST_PARAM_SET |
3-Error |
[chars] : [dec] Peer List Paramter Set was invalid in a MKPDU for |
MKA failed to process the SAK-Use Parameter Set of a received MKPDU. |
mka |
"No action required internal error." |
|
MKA-3-INVALID_SAK_USE_PARAM_SET |
3-Error |
[chars] : [dec] SAK-Use Paramter Set was invalid in a MKPDU for |
MKA failed to process the SAK-Use Parameter Set of a received MKPDU. |
mka |
"No action required internal error." |
|
MKA-3-INVALID_SESSION |
3-Error |
MKA Session entry not found while [chars]. |
MKA was unable to find the MKA Session entry during the indicated action. This is an internal error. |
mka |
"Provide the traceback and if possible " "`debug mka trace` and `debug mka error` output " "internal error." |
|
MKA-3-INVALID_VP |
3-Error |
VP entry not found while [chars]. |
MKA was unable to find the VP entry during the indicated action. This is an internal error. |
mka |
"Provide the traceback and if possible " "`debug mka trace` and `debug mka error` output " "internal error." |
|
MKA-3-KEK_DERIVE_FAILURE |
3-Error |
[chars] : [dec] Unable to derive KEK for RxSCI [chars] AuditSessionID [chars] |
Internal failure - MKA failed to derive the Key Encrypting Key KEK from the derived CAK & CKN |
mka |
"`debug mka trace` and `debug mka error` may help " "to diagnose the problem internal failure." |
|
MKA-3-MKPDU_ICV_VERIFICATION_FAILURE |
3-Error |
[chars] : [dec] ICV Verification of a MKPDU failed for RxSCI [chars] |
The ICV Verification failed of MKPDU received for the MKA Session Identified by the given RxSCI Audit Session ID and CKN failed. The reason for the same could be the following: - The CAK is misconfigured on the RxSCI in case of PSK\n - The MKPDU data is tampered during transmission. |
mka |
"Check the configured CAK on RxSCI" "To validate MKPDU data tampering `debug mka " "{ packet }` at both side may help to diagnose " "the problem." |
|
MKA-3-MKPDU_VALIDATE_FAILURE |
3-Error |
[chars] : [dec] Validation of a MKPDU failed for RxSCI [chars] |
A MKPDU received for the MKA Session identified by the give RxSCI Audit Session ID and CKN failed one or more of the follwoing validation checks:\n - MKPDU Integrity\n - Packet length reported equals actual packet length\n - Valid CKN Algorithm Agility\n - ICV Verification\n - Correct paramset order & existence of MKA payloads\n - MI verification if peers exist\n - MN verification if peers exist. |
mka |
"`debug mka { packet | trace | error }` may help to " "diagnose the problem. Also any packet traces and " "captures may help too internal failure." |
|
MKA-3-SAK_CIPHER_MISMATCH |
3-Error |
[chars] : [dec] Received [chars] cipher it is not configured |
The received cipher is not configured or supported |
mka |
"If received cipher is supported change configuration " "at receive side or change cipher at KS to include " "the supported cipher" |
|
MKA-3-SAK_GENERATE_FAILURE |
3-Error |
[chars] : [dec] Unable to generate SAK AN [dec] KN [dec] for RxSCI [chars] |
Internal failure - MKA failed to generate the Secure Association Key SAK from the derived CAK & given Key |
mka |
"`debug mka trace` and `debug mka error` may help " "to diagnose the problem internal failure." |
|
MKA-3-UNEXPECTED_HA_MESSAGE |
3-Error |
Received unexpected message during MKA HA process |
Undefined message event encountered. |
mka |
"No action required internal error." |
|
MKA-4-INVALID_MACSEC_CAPABILITY |
4-Warning |
[chars] : [dec] Terminating MKA Session because no peers had the |
MKA Session was terminated because no peers in the CA had a high enough MACsec Capability value set in MKPDUs received to use SAKs distributed by this Key Server. The required minimum MACsec Capability is dictated by the configured MACsec options. |
mka |
"Check the MACsec Capability of the peers' hardware " "or lower the requirements for MACsec Capability by " "changing the MACsec configuration for this " "interface." |
|
MKA-4-KEEPALIVE_TIMEOUT |
4-Warning |
[chars] : [dec] Peer has stopped sending MKPDUs for RxSCI [chars] |
For a Pairwise CA i.e. one peer MKA has not received a MKPDU from its Live Peer for at least 6 seconds so the MKA Session will be terminated. If this is a Group CA i.e. multilple peers MKA has not received a MKPDU from |
mka |
"Check connection to peer and if peer is still up " "and responding. Also check for MKPDU Validation " "Failures." |
|
MKA-4-MKA_MACSEC_CIPHER_MISMATCH |
4-Warning |
[chars] : [dec] Lower strength MKA-cipher than macsec-cipher for RxSCI [chars] |
Higher strength Macsec Cipher is configured than the MKA cipher. This is not recommended from a security purpose. |
mka |
"Review the MKA cipher config and the macsec cipher " "config and ensure that the MKA cipher is either of " "the same or higher strength than macsec cipher" |
|
MKA-4-SAK_TRANSMIT |
4-Warning |
[chars] : [dec] Installing new TxSA AN [dec] but not all peers have |
For a Pairwise CA i.e. one peer MKA acting as the Key Server has distributed a SAK for use in MACsec to a peer with the minimum required MACsec Capability but has not received a SAK-Use payload back from the peer indicating that the peer is receiving using the newly distributed SAK withing 6 seconds MKA Life Time so MKA will go |
mka |
"Check connection to peers & for any MKPDU " "Validation errors. Also check the MKA/MACsec " "implementation on the peers' systems." |
|
MKA-4-SESSION_UNSECURED |
4-Warning |
[chars] : [dec] MKA Session was stopped by [chars] and not secured for RxSCI [chars] |
The MKA Session identified by the RxSCI Audit Session ID and CKN given was unable to be secured before being terminated. Possible reasons include no MACsec support on the specified interface invalid MACsec configuration for the specified interface the peer identified by the given RxSCI not having enough MACsec Capability or other internal failure prior to the establishment of Rx/Tx Secure Channels and installation of Rx/Tx Secure Associations in MACsec. MKA will report back to the IOS Authentication Manager that it was unable to secure the session to indicate either Authz Failed for a LinkSec policy of `must-secure` or to be hosted unsecured for a LinkSec policy of `should-secure`. |
mka |
"If the MKA Session should have been secured check " "for other MKA system logs that indicate the reason " "for not being secured. Check MACsec support on " "the interface & peer MACsec configuration and " "connectivity. `debug mka trace` and " "`debug mka error` may help to diagnose the " "problem." |
|
MKA-5-CAK_REKEY |
5-Notice |
[chars] : [dec] MKA Session is beginning a CAK Rekey [chars] for RxSCI [chars] |
MKA has received a request to perform a CAK Rekey for the MKA Session identified by the given RxSCI Audit Session ID and CKN. A new key is available either from keychain infra or Authentication manager new MSK & EAP Session ID received from EAP Authentication |
mka |
"No action required normal operation." |
|
MKA-5-SESSION_SECURED |
5-Notice |
[chars] : [dec] MKA Session was secured for RxSCI [chars] |
MKA was able to secure the MKA Session identified by the Audit Session ID & CKN given with the peer identified by the RxSCI given. SESSION_SECURED happens in a successful response to a SESSION_START from the IOS Authentication Manager only after MACsec Secure Channels and Secure Associations have been installed and enabled for both Rx and Tx. |
mka |
"No action required normal operation." |
|
MKA-5-SESSION_SECURED_FALLBACK |
5-Notice |
[chars] : [dec] MKA Session was secured with the fallback CA for RxSCI [chars] |
MKA was able to secure the MKA Session identified by the Audit Session ID & CKN given with the peer identified by the RxSCI given. SESSION_SECURED happens in a successful response to a SESSION_START from the IOS Authentication Manager only after MACsec Secure Channels and Secure Associations have been installed and enabled for both Rx and Tx. |
mka |
"No action required normal operation." |
|
MKA-5-SESSION_START |
5-Notice |
[chars] : [dec] MKA Session started for RxSCI [chars] AuditSessionID [chars] |
The IOS Authentication Manager has requested for MKA to begin a new MKA Session for a peer that has successfully authenticated with the RxSCI and Audit Session ID given. MKA will begin initialization and setup by creating a new Virtual Port for the given interface & Virtual Port ID. Also all keying information specific to the MSK and EAP Session ID received will be derived. |
mka |
"No action required normal operation." |
|
MKA-5-SESSION_STOP |
5-Notice |
[chars] : [dec] MKA Session stopped by [chars] for RxSCI [chars] AuditSessionID [chars] |
After being secured the MKA Session identified by the RxSCI Audit Session ID and CKN given was ended or terminated. Possible reasons include using the `clear auth sess` or `clear mka {all | sess}` command keepalive timeout reauth failure or other internal failure. |
mka |
"If the MKA Session was not supposed to terminate " "check the command history or other system logs " "to find out the specific termination reason. " "`debug mka trace` and `debug mka error` may help " "diagnose the problem if the MKA Session was not " "supposed to terminate. Otherwise no action " "required normal operation." |
|
MKA-6-CAK_REKEY_SUCCESS |
6-Information |
[chars] : [dec] MKA Session CAK rekey is successful for RxSCI [chars] |
MKA was able to Rekey the MKA Session identified by the Audit Session ID & CKN given for the peer identified by the RxSCI given successfully. CAK_REKEY_SUCCESS happens in a successful response to a SESSION_REAUTH from the IOS Authentication manager only after the MKA Session has seamlessly switched to a new CAK/SAK after rekeying the CAK & SAK. |
mka |
"No action required normal operation." |
|
MKA-6-SAK_REKEY |
6-Information |
[chars] : [dec] MKA Session is beginning a SAK Rekey |
MKA has received a request to perform a SAK Rekey for the MKA Session identified by the given RxSCI Audit Session ID and CKN. The current Latest Association Number AN and Key Number KN correspond to the |
mka |
"No action required normal operation." |
|
MKA-6-SAK_REKEY_SUCCESS |
6-Information |
[chars] : [dec] MKA Session successfully completed a SAK Rekey |
MKA has successfully performed a SAK Rekey for the MKA Session identified by the given RxSCI Audit Session ID and CKN. The new Latest Association Number AN and Key Number KN correspond to the new Rx/Tx |
mka |
"No action required normal operation." |
|
MLD_PROT-3-INTERNAL_ERR |
3-Error |
[chars] |
Internal error |
ipmulticast |
LOG_STD_RECUR_ACTION |
|
MLD_PROT-3-PAK_ERR |
3-Error |
An internal error occured while processing a packet queue |
Managed queue event received without a packet. Internal Error |
ipmulticast |
LOG_STD_RECUR_ACTION |
|
MLD_PROT-3-SHUTDOWN_ERR |
3-Error |
Error in [chars] : [chars] |
Internal error |
ipmulticast |
LOG_STD_RECUR_ACTION |
|
MLD_PROT-3-STARTUP_ERR |
3-Error |
Unable to start to MLD process |
Internal error |
ipmulticast |
LOG_STD_RECUR_ACTION |
|
MLD_PROT-3-TABLE_ERR |
3-Error |
[chars] |
Errors related to IGMP table creation and management |
ipmulticast |
LOG_STD_RECUR_ACTION |
|
MLD_PROT-4-LIMIT_REACHED |
4-Warning |
State limit reached report on [chars] ignored for [chars] |
MLD report ignored because state limit was reached. |
ipmulticast |
LOG_STD_NO_ACTION |
|
MLD_PROT-4-SUSPEND_RESUME_WARNING |
4-Warning |
Failed to resume suspended IGMP/MLD context. |
A loop in IGMP/MLD code was temporarily suspended to avoid hogging the CPU. When it was time to resume the loop the system was unable to do so. Possible reasons for this are that a VRF was deleted or an interface was deleted while the loop was suspended. |
ipmulticast |
LOG_STD_NO_ACTION |
|
MLD_PROT-6-IDB_ENABLE |
6-Information |
Interface [chars] does not support multicast not enabled |
IGMP/MLD not enabled on an interface that does not support mcast |
ipmulticast |
LOG_STD_NO_ACTION |
|
MLD_SNOOP_ISSU-2-GET_BUFFER |
2-Critical |
MLD Snooping ISSU client failed to get buffer for message. Error: [dec] [chars] |
The MLD Snooping 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. |
mld-snooping |
"show logging and show checkpoint client" |
|
MLD_SNOOP_ISSU-2-GET_BUFFER |
2-Critical |
MLD Snooping ISSU client failed to get buffer for message. Error: [dec] [chars] |
The MLD Snooping 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. |
mld-snooping |
"show logging and show checkpoint client" |
|
MLD_SNOOP_ISSU-2-INIT |
2-Critical |
MLD Snooping ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The MLD Snooping 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. |
mld-snooping |
LOG_STD_ACTION |
|
MLD_SNOOP_ISSU-2-INIT |
2-Critical |
MLD Snooping ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The MLD Snooping 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. |
mld-snooping |
LOG_STD_ACTION |
|
MLD_SNOOP_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
MLD Snooping ISSU client failed to send negotiation message. Error: [dec] [chars] |
The MLD Snooping 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. |
mld-snooping |
"show logging and show checkpoint client" |
|
MLD_SNOOP_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
MLD Snooping ISSU client failed to send negotiation message. Error: [dec] [chars] |
The MLD Snooping 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. |
mld-snooping |
"show logging and show checkpoint client" |
|
MLD_SNOOP_ISSU-2-SESSION_NEGO |
2-Critical |
MLD Snooping ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The MLD Snooping 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. |
mld-snooping |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MLD_SNOOP_ISSU-2-SESSION_NEGO |
2-Critical |
MLD Snooping ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The MLD Snooping 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. |
mld-snooping |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MLD_SNOOP_ISSU-2-SESSION_REGISTRY |
2-Critical |
MLD Snooping ISSU client failed to register session information. Error: [dec] [chars] |
The MLD Snooping ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
mld-snooping |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MLD_SNOOP_ISSU-2-SESSION_REGISTRY |
2-Critical |
MLD Snooping ISSU client failed to register session information. Error: [dec] [chars] |
The MLD Snooping ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
mld-snooping |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MLD_SNOOP_ISSU-3-INVALID_SESSION |
3-Error |
MLD Snooping ISSU client does not have a valid registered session. |
The MLD Snooping ISSU client does not have a valid registered session. |
mld-snooping |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MLD_SNOOP_ISSU-3-INVALID_SESSION |
3-Error |
MLD Snooping ISSU client does not have a valid registered session. |
The MLD Snooping ISSU client does not have a valid registered session. |
mld-snooping |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MLD_SNOOP_ISSU-3-MSG_NOT_OK |
3-Error |
MLD Snooping ISSU client 'Message Type [dec]' is not compatible |
The MLD Snooping ISSU client received an incompatible message from the peer device. The message cannot be processed. |
mld-snooping |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
MLD_SNOOP_ISSU-3-MSG_NOT_OK |
3-Error |
MLD Snooping ISSU client 'Message Type [dec]' is not compatible |
The MLD Snooping ISSU client received an incompatible message from the peer device. The message cannot be processed. |
mld-snooping |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
MLD_SNOOP_ISSU-3-MSG_SIZE |
3-Error |
MLD Snooping ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The MLD Snooping ISSU client failed to calculate the MTU for the specified message. The MLD Snooping ISSU client is not able to send the message to the standby device. |
mld-snooping |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
MLD_SNOOP_ISSU-3-MSG_SIZE |
3-Error |
MLD Snooping ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The MLD Snooping ISSU client failed to calculate the MTU for the specified message. The MLD Snooping ISSU client is not able to send the message to the standby device. |
mld-snooping |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
MLD_SNOOP_ISSU-3-SESSION_UNREGISTRY |
3-Error |
MLD Snooping ISSU client failed to unregister session information. Error: [dec] [chars] |
The MLD Snooping ISSU client failed to unregister session information. |
mld-snooping |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MLD_SNOOP_ISSU-3-SESSION_UNREGISTRY |
3-Error |
MLD Snooping ISSU client failed to unregister session information. Error: [dec] [chars] |
The MLD Snooping ISSU client failed to unregister session information. |
mld-snooping |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MLD_SNOOP_ISSU-3-TRANSFORM_FAIL |
3-Error |
MLD Snooping ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The MLD Snooping 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 MLD Snooping state between the active device and the standby device is not identical. |
mld-snooping |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
MLD_SNOOP_ISSU-3-TRANSFORM_FAIL |
3-Error |
MLD Snooping ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The MLD Snooping 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 MLD Snooping state between the active device and the standby device is not identical. |
mld-snooping |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
MLDP-2-CHUNK_ERR |
2-Critical |
Error initializing MLDP db chunks |
Error initializing MLDP db chunks |
- |
LOG_STD_NO_ACTION |
|
MLDP-2-FEC_CHUNK_ERR |
2-Critical |
Error initializing MLDP FEC chunks |
Error initializing MLDP FEC chunks |
- |
LOG_STD_NO_ACTION |
|
MLDP-2-FEC_ERR |
2-Critical |
Error the FEC size is too large |
The FEC size is too large |
- |
LOG_STD_NO_ACTION |
|
MLDP-2-FEC_NTF_ERR |
2-Critical |
Error initializing MLDP FEC notifier |
Error initializing MLDP FEC notifier |
- |
LOG_STD_NO_ACTION |
|
MLDP-2-FEC_TBL_ERR |
2-Critical |
Error initializing MLDP FEC tbl |
Error initializing MLDP FEC tbl |
- |
LOG_STD_NO_ACTION |
|
MLDP-2-FILTER_CHUNK_ERR |
2-Critical |
Error initializing MLDP filter chunks |
Error initializing MLDP filter chunks |
- |
LOG_STD_NO_ACTION |
|
MLDP-2-FILTER_NTF_ERR |
2-Critical |
Error registering MLDP filter FEC notifier |
Error registering MLDP filter FEC notifier |
- |
LOG_STD_NO_ACTION |
|
MLDP-2-FILTER_TBL_ERR |
2-Critical |
Error initializing MLDP filter tbl |
Error initializing MLDP filter tbl |
- |
LOG_STD_NO_ACTION |
|
MLDP-2-HA_INSERT_ERR |
2-Critical |
Error inserting node into MLDP HA radix tree |
Error inserting node into MLDP HA radix tree |
- |
LOG_STD_NO_ACTION |
|
MLDP-2-ID_RESERVE_ERR |
2-Critical |
Error reserving id for mldp database |
Error reserving id for mldp database |
- |
LOG_STD_NO_ACTION |
|
MLDP-2-INTERNAL_ERR |
2-Critical |
Internal mLDP error |
Internal error |
- |
LOG_STD_NO_ACTION |
|
MLDP-2-MRIB_PROCESS_ERR |
2-Critical |
Error initializing MLDP MRIB process |
Can't start the MLDP MRIB process |
- |
LOG_STD_NO_ACTION |
|
MLDP-2-PEER_ERR |
2-Critical |
Received attached address [inet] but there is no LDP peer |
Internal error |
- |
LOG_STD_NO_ACTION |
|
MLDP-2-PEER_NOT_FOUND |
2-Critical |
Peer doesn't exist while syncing to standby |
Peer doesn't exist while syncing to standby |
- |
LOG_STD_NO_ACTION |
|
MLDP-2-PROCESS_ERR |
2-Critical |
Error initializing MLDP process |
Can't start the MLDP process |
- |
LOG_STD_NO_ACTION |
|
MLDP-2-RADIX_BRANCH_ERR |
2-Critical |
Error initializing MLDP BRANCH radix tree |
Internal error |
- |
LOG_STD_NO_ACTION |
|
MLDP-2-RADIX_DB_ERR |
2-Critical |
Error initializing MLDP DB radix tree |
Error initializing MLDP_DB radix ree |
- |
LOG_STD_NO_ACTION |
|
MLDP-2-ROOT_NOT_FOUND |
2-Critical |
Root doesn't exist while syncing to standby. |
Root doesn't exist while syncing to standby |
- |
LOG_STD_NO_ACTION |
|
MLDP-4-DB_BRANCH_DEL_PENDING |
4-Warning |
[chars] tree with LSM ID: %X has both IPv4 and IPv6 del_pending set |
An mLDP database entry has both the IPv4 and IPv6 del_pending \n\ flags set to TRUE -- This is an inconsistent state |
- |
LOG_STD_ACTION |
|
MLDP-4-RW_GET_NOTIF_FAIL |
4-Warning |
mLDP failed to get information from the unicast RIB -- RIB Error Code - 0x[hec] |
prefix from the RIB due to some reason. |
mldp |
LOG_STD_ACTION |
|
MLDP-4-RW_REGISTER_FAIL |
4-Warning |
mLDP failed to register to the unicast RIB |
routing update in the network. |
mldp |
LOG_STD_ACTION |
|
MLDP-4-RW_TRACK_START_FAIL |
4-Warning |
mLDP failed to start tracking a prefix in the unicast RIB |
in the RIB due to some reason. |
mldp |
LOG_STD_ACTION |
|
MLDP-4-RW_TRACK_STOP_FAIL |
4-Warning |
mLDP failed to stop tracking a prefix in the unicast RIB |
in the RIB due to some reason. |
mldp |
LOG_STD_ACTION |
|
MLDP-4-RW_UNREGISTER_FAIL |
4-Warning |
mLDP failed to un-register to the unicast RIB |
or Route-watch process due to some reason. |
mldp |
LOG_STD_ACTION |
|
MLDP-5-ADD_BRANCH |
5-Notice |
[chars] Root: [inet] Add [chars] branch [chars] [chars] |
Logging of changes to mLDP branch |
- |
LOG_STD_NO_ACTION |
|
MLDP-5-DELETE_BRANCH |
5-Notice |
[chars] Root: [inet] Delete [chars] branch [chars] [chars] |
Logging of changes to mLDP branch |
- |
LOG_STD_NO_ACTION |
|
MLDP-5-MODIFY_BRANCH |
5-Notice |
[chars] Root: [inet] Modify [chars] branch [chars] [chars] |
Logging of changes to mLDP branch |
- |
LOG_STD_NO_ACTION |
|
MLDP-5-MODIFY_NBR |
5-Notice |
[chars] Root: [inet] Modify [chars] entry peer [chars] [chars] |
Logging of changes to mLDP entry peer |
- |
LOG_STD_NO_ACTION |
|
MLDP-5-ROUTING_LOOP |
5-Notice |
There is a routing loop for this root. |
There is a routing loop for this root |
- |
LOG_STD_NO_ACTION |
|
MLRIB-3-MLRIB_L2_ERROR_DELETING_TOPOLOGY |
3-Error |
Error deleting routing topology scope [dec] information from routing database |
This condition occurs when the information about a routing topology scope in the routing database gets corrupted and does not fully match with the expected information of the routing topology to be deleted. |
l2rib |
"Consider reconfiguring the routing topology scope. " "If the error persists reload the router " |
|
MLRIB-3-MLRIB_L2_ERROR_DELETING_VPN |
3-Error |
Error deleting private network [dec] information from routing database |
This occurs when the information about a private network in the routing database gets corrupted and does not fully match with the expected information of the private network to be deleted. |
l2rib |
"Consider reconfiguring the private network. If " "the error persists reload the router" |
|
MLRIB-4-MLRIB_CLIENT1_ROUTE_REPOPULATION_TIME_EXCEEDED |
4-Warning |
A routing database client id [dec] failed to complete route repopulation: Layer [dec] sub address family [dec] and routing client instances [dec] |
Routing database client did not complete route repopulation within the allotted amount of time after a system failover. |
ether-infra |
"Contact TAC for further investigation of this " "issue and provide them with the following logs: " "show mlrib layer2 log event all show mlrib layer2 " "log error all show mlrib layer2 log trace all " "show mlrib common log event all show mlrib " "common log error all and show logging " |
|
MLRIB-4-MLRIB_CLIENT2_ROUTE_REPOPULATION_TIME_EXCEEDED |
4-Warning |
A routing database client id [dec] failed to complete route repopulation: Layer [dec] sub address family [dec] and routing client instances [dec] |
Routing database client did not complete route repopulation within the allotted amount of time after a system failover. |
asr1k-igmpsn |
"Contact TAC for further investigation of this " "issue and provide them with the following logs: " "show mlrib layer2 log event all show mlrib layer2 " "log error all show mlrib layer2 log trace all " "show mlrib common log event all show mlrib " "common log error all and show logging " |
|
MLRIB-4-MLRIB_CLIENT3_ROUTE_REPOPULATION_TIME_EXCEEDED |
4-Warning |
A routing database client id [dec] failed to complete route repopulation: Layer [dec] sub address family [dec] and routing client instances [dec] |
Routing database client did not complete route repopulation within the allotted amount of time after a system failover. |
isis |
"Contact TAC for further investigation of this " "issue and provide them with the following logs: " "show mlrib layer2 log event all show mlrib layer2 " "log error all show mlrib layer2 log trace all " "show mlrib common log event all show mlrib " "common log error all and show logging " |
|
MLRIB-4-MLRIB_CLIENT4_ROUTE_REPOPULATION_TIME_EXCEEDED |
4-Warning |
A routing database client id [dec] failed to complete route repopulation: Layer [dec] sub address family [dec] and routing client instances [dec] |
Routing database client did not complete route repopulation within the allotted amount of time after a system failover. |
ios-otv-app |
"Contact TAC for further investigation of this " "issue and provide them with the following logs: " "show mlrib layer2 log event all show mlrib layer2 " "log error all show mlrib layer2 log trace all " "show mlrib common log event all show mlrib " "common log error all and show logging " |
|
MLRIB-4-MLRIB_ROUTE_REPOPULATION_TIME_EXCEEDED |
4-Warning |
All routing database client failed to complete route repopulation |
None of the routing database client completed route repopulation within the allotted amount of time after a system failover. |
l2rib |
"Contact TAC for further investigation of this " "issue and provide them with the following logs: " "show mlrib layer2 log event all show mlrib layer2 " "log error all show mlrib layer2 log trace all " "show mlrib common log event all show mlrib " "common log error all and show logging " |
|
MLRIB-4-SYSTEM_ROUTE_HIGHWATER_MARK_REACHED |
4-Warning |
Route system [dec] has reached its high water mark of [dec] |
The number of routes installed in a routing database has exceeded a threshold. This condition indicates a high density of routes within this system. |
- |
"Consider balancing some destinations using " "additional routing devices" |
|
MLRIB-4-SYSTEM_ROUTE_LIMIT_REACHED |
4-Warning |
Routing system [dec] has reached its maximum route capacity of [dec] |
The number of routes installed in a routing system has exceeded a preset limit. This condition indicates a high density of routes within this system. No more routes can be installed within this system until the number goes below high water mark of 95% of preset limit |
- |
"Consider balancing some destinations using " "additional routing devices" |
|
MLRIB-4-TOPOLOGY_ROUTE_HIGHWATER_MARK_REACHED |
4-Warning |
Route topology scope [dec] has reached its high water mark of [dec] |
The number of routes installed in a routing topology scope has exceeded a threshold. This condition indicates a high density of routes within this routing topology scope. |
- |
"Consider routing some destination via other " "route topology scopes" |
|
MLRIB-4-TOPOLOGY_ROUTE_LIMIT_REACHED |
4-Warning |
Route topology scope [dec] has reached its maximum route capacity of [dec] |
The number of routes installed in a route scope topology has exceeded a preset limit. This condition indicates a high density of routes within this scope. No more routes can be installed within this scope until the number goes below high water mark of 95% of preset limit |
- |
"Consider routing some destination via other " "route topology scopes" |
|
MLRIB-6-MLRIB_L2_PREEMPTIVE_PRIV_NETWORK_NOTIFICATION |
6-Information |
A notification was sent preemptively for the private network [dec] and client id [dec] |
This condition occurs when the client experiences a large number of notifications |
- |
- |
|
MLRIB-6-MLRIB_REDUNDANCY_PREEMPTIVE_NOTIFICATION |
6-Information |
A notification was sent preemptively for the private network [dec] and client id % after redundancy switchover |
This condition occurs when the client experiences a large number of notifications |
- |
- |
|
MLSM-2-IPC_ERROR |
2-Critical |
MMLS: IPC failure detected between RP and SP |
This can happen when EOBC channel is too busy or NMP is too busy so that draco side does not get response even after few retries by IPC layer. |
cat6000 |
"Under some stressful condition when communication between RP and SP side can not be maintained this message will be printed. MMLS will keep trying to recover from situation by sending message to SP. The restart message to SP has exponential back off upto 160 second" |
|
MLSM-6-CONFIG_MISMATCH |
6-Information |
Multicast hardware switching config mis-match between RP and NMP. It is likely to be disabled on the NMP |
MLS multicast hardware switching has been enabled on the RP but likely disabled on the NMP |
cat6000 |
"Correct the mis-config by enabling IGMP snooping and MMLS on the NMP" |
|
MLSM-6-CONFIG_MISMATCH_RECOVERED |
6-Information |
Multicast hardware switching mismatch recovered from earlier config mis-match |
MMLS Config mismatch between RP and SP recovered from mismatch. The MLS multicast hardware switching is likely to be enabled on the NMP |
cat6000-mmls |
"Modify the network config such that hardware resource limitation is not hit and ensure that sg or *g entry is installed." |
|
MLSM-6-ERROR_RECOVERED |
6-Information |
MMLS: Communication channel between RP and SP recovered from failure |
Communication between RP and SP recovered from earlier IPC / SCP failure. MMLS will install HW switched entries on backoff timer expiration. The backoff time is min10 sec * # of times error occurred^2 160 |
cat6000 |
"Note the difference between the time the error occurred to the current message. It indicates the time when no HW switched entries existed in the switch" |
|
MLSM-6-LC_SCP_FAILURE |
6-Information |
NMP encountered internal communication failure for [inet][inet][dec] |
This message happens SP was not able to update CEF tables on atleast one of the EARLs on Linecards. |
cat6000-mmls |
"Under some condition SP was not able to communicate with Linecard to update the multicast-CEF table. And this causes inconsistency in the CEF table among different line cards. This shortcut is deleted so that inconsistent state is purged. And this flow will get software forwarded." |
|
MLSM-6-MFD_COUNT_ERR |
6-Information |
MFD Count error : [inet][inet][dec] first mfd: [dec]vlan extra RPF-MFD |
This message happens when there are multiple MFD in hardware switched state. |
cat6000-mmls |
"This is just a informative message. If there are to many packets going to CPU the MTU on the interfaces should be changed appropriately to take advantage of hardware replication." |
|
MLSM-6-MIN_MTU_UNSUPPORTED |
6-Information |
Outgoing interfaces with MTU less than the RPF interface will be multicast replicated to in software |
- |
cat6000-mmls |
"This is just a informative message. If there are to many packets going to CPU the MTU on the interfaces should be changed appropriately to take advantage of hardware replication." |
|
MLSM-6-MLSM_PMS |
6-Information |
MMLS: MLSM is suspending the caller process [chars] |
This message is to remind the user that MLSM is suspending the caller process. This happens when the MLSM routines are called from PIM/Mwheel context and MLSM routines does an process suspend |
cat6000-mmls |
"When MLSM suspends the caller process there is a possibility of data corruption for the data handled by the caller process" |
|
MLSM-6-MMLS_EGRESS_INFO |
6-Information |
MMLS: Please make sure no multicast traffic is going through egress incapable line cards when system is operating in egress mode |
This message is to remind the user that there should be no multicast traffic going through egress incapable line cards while the system is operating in egress replication mode. |
cat6000 |
"Check to see if there are any egress incapable line cards in the system. If there are egress incapable line cards make sure that there is no multicast traffic going through these cards" |
|
MLSM-6-MMLS_LEGACY_INSERTED |
6-Information |
MMLS: Legacy Linecard Inserted Egress Replication Mode will be disabled |
Egress Replication is not supported with Legacy Cards system will transition to Ingress Mode please note that the transition will cause temporary loss of traffic |
cat6000 |
"If the system is required to operate in Egress Replication Mode the Legacy lincard should be removed" |
|
MLSM-6-MMLS_MODE_CHANGE |
6-Information |
MMLS: Replication Mode Changed to [chars] mode [chars] |
When auto detection of replication mode is enabled the system will transition to ingress mode when an egress incapable linecard is inserted. The system will transition back to egress mode when the last egress incapable linecard is removed |
cat6000 |
"Transition between ingress and egress mode will cause temporary loss of traffic to prevent this use the command mls ip replication-mode ingress" |
|
MLSM-6-MMLS_NO_EGRESS_LOCAL_IN_INGRESS |
6-Information |
MMLS: Egress Local feature is NOT applicable in Ingress mode |
When the system transistions from Egress replication mode to ingress the Egress Local feature will become non-applicable even if the Egress Local feature is enabled. |
cat6000 |
"This is only to inform the user that Egress Local feature is not applicable in Ingress mode. If the Egress Local feature is required actions need to be taken to restore the system replication mode to egress" |
|
MLSM-6-PVLAN_INSTALL_FAILURE |
6-Information |
Unable to locate secondary-vlan for [inet][inet][dec] |
This message happens when RP was not able to determine the secondary vlan for the source in secondary vlan. After finite retries RP gives up installing the shortcut in hardware. This can happen when a new flow is installed or when there is a RPF change. In such situations flow will be software switched. |
cat6000-mmls |
"Make sure ARP table is populated for sources in secondary vlan by explicity 'ping'ing the source and the ARP table should contain the primary as well as secondary vlan information. To enable creation of hardware shortcut do a 'clear ip mroute <group> <source>' for the specific flow." |
|
MLSM-6-SCP_ERROR |
6-Information |
MMLS: SCP failure detected between RP and SP |
This can happen when EOBC channel is too busy or NMP is too busy so that draco side does not get response even after few retries by ICC layer. |
cat6000 |
"Under some stressful condition when communication between RP and SP side can not be maintained this message will be printed. MMLS will keep trying to recover from situation by sending message to SP. The restart message to SP has exponential back off upto 160 second" |
|
MLSM-6-SM_INSTALL_FAILURE |
6-Information |
interface/mask entry installation failed on [inet]/[dec] vlan[dec] |
This message happens when Interface/mask entry to punt directly connected sources to the router could not be installed in HW-CEF table. This happens system is running out of available CEF entries. In this situation there might be blackholing of traffic for the directly connected sources on this interface |
cat6000-mmls |
"Modify the network config such that hardware resource limitation is not hit and ensure that interface/mask entry is installed." |
|
MLTMGR-3-MLTMGR_INTERNAL_ERR |
3-Error |
[chars] |
MLTMGR_INT_ERR_EXPLANATION |
- |
LOG_STD_RECUR_ACTION |
|
MMA_DP-3-DEBUG_REG_FAILED |
3-Error |
Metric Mediation Agent fails to registrate with Conditional Debugging. |
Metric Mediation Agent fails to registrate with Conditional Debugging infra. |
asr1k-avc |
LOG_STD_ACTION |
|
MMA_DP-3-INIT |
3-Error |
Error during initialization error [chars] |
Error happened during initialization of MMA Data plane |
media-mon |
LOG_STD_ACTION |
|
MMA_DP-3-LIST |
3-Error |
Failed to [chars] list [chars] |
A list operation failed. This could be caused by memory corruption |
media-mon |
LOG_STD_ACTION |
|
MMA_DP-3-MEM |
3-Error |
Memory [chars] failed - [chars] |
Memory creation failed during the initialization |
media-mon |
LOG_STD_ACTION |
|
MMA_DP-3-TEMPLATE |
3-Error |
Create flow template error [chars] |
Error happened during creating MMA PD flow def template |
media-mon |
LOG_STD_ACTION |
|
MMA-2-IPC_INIT |
2-Critical |
IPC message handler registration failure rc [dec] |
Registering an IPC message handler for the MMA feature failed. This will cause the feature to not function. |
qfp-mma |
"This is normally a software issue. " "The consequences are that the MMA feature will not function. " LOG_STD_ACTION |
|
MMA-3-CACHE_OVERFLOW |
3-Error |
The number of flows has exceeded 95%% of the configured size monitor [chars] please increase cache size\n |
This is warning message if the flow size exceeds the maximum value |
media-mon |
LOG_STD_ACTION |
|
MMA-3-CHUNKCREATE |
3-Error |
Failed to chunk create memory for [chars] |
Unable to chunk create memory chunk |
media-mon |
LOG_STD_ACTION |
|
MMA-3-CHUNKDESTROY |
3-Error |
Failed to chunk destroy memory for [chars] |
Unable to chunk destroy memory chunk |
media-mon |
LOG_STD_ACTION |
|
MMA-3-CHUNKMALLOC |
3-Error |
Failed to malloc chunk memory for [chars] |
Unable to malloc memory chunk malloc failed |
media-mon |
LOG_STD_ACTION |
|
MMA-3-DB |
3-Error |
[chars] |
Error during managing MMA database |
media-mon |
LOG_STD_ACTION |
|
MMA-3-FIELD |
3-Error |
[chars] |
Error during initializing a field |
media-mon |
LOG_STD_ACTION |
|
MMA-3-FLOW_EXCEED |
3-Error |
The number of flows has exceeded 95%% of the configured maximum flow. [chars]\n |
This is warning message if the flow size exceeds the maximum value |
media-mon |
LOG_STD_ACTION |
|
MMA-3-FLOW_NONEXCEED |
3-Error |
The number of flows is below 85%% of the configured maximum flow. [chars]\n |
This is info message if the flow size falls below the maximum value |
media-mon |
LOG_STD_ACTION |
|
MMA-3-INV_ACTION_OBJ |
3-Error |
action object is not valid - [chars] |
This is an internal error the saved action object info is corrupted |
media-mon |
LOG_STD_ACTION |
|
MMA-3-INV_ARG |
3-Error |
The argument is not valid - [chars] |
An internal error occurred. The argument for an internal API is not valid |
media-mon |
LOG_STD_ACTION |
|
MMA-3-INV_COMMON_MONITOR |
3-Error |
The common monitor pointer is invalid |
An internal error occurred. The common monitor pointer saved in the performance-monitor monitor is NULL |
media-mon |
LOG_STD_ACTION |
|
MMA-3-INV_DB_OBJ |
3-Error |
Internal error mma db pointer invalid |
No valid pointer to mma db |
media-mon |
LOG_STD_ACTION |
|
MMA-3-INV_MONITOR |
3-Error |
The flow monitor pointer is invalid |
An internal error occurred. The performance-monitor monitor pointer saved in the common monitor is NULL |
media-mon |
LOG_STD_ACTION |
|
MMA-3-INV_MONITOR_TYPE |
3-Error |
The monitor type [dec] is invalid |
An internal error occurred. The monitor type is out of the range |
media-mon |
LOG_STD_ACTION |
|
MMA-3-INV_REACT |
3-Error |
react is not valid - [chars] |
This is an internal error the saved react info is corrupted |
media-mon |
LOG_STD_ACTION |
|
MMA-3-IPC_NORES |
3-Error |
No space for the IPC reply size [dec] |
For a request from upper MMA software stack layers it was not possible to allocate space for a reply for the specified size. The consequence of this could be a stuck binding that cannot be established etc. In rare cases this could also affect other operations such as feature activation. |
qfp-mma |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
MMA-3-IPC_OPEN_REPLY |
3-Error |
IPC Open Reply failed request [dec] |
For a request from upper MMA software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck binding that cannot be established etc. In rare cases this could also affect other operations such as feature activation. |
qfp-mma |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
MMA-3-LIST |
3-Error |
Failed to [chars] list [chars] |
A list operation failed. This could be caused by memory corruption |
media-mon |
LOG_STD_ACTION |
|
MMA-3-MCOL |
3-Error |
[chars] |
Error during collecting metrics in MMA PI |
media-mon |
LOG_STD_ACTION |
|
MMA-3-MEM |
3-Error |
Memory [chars] failed - [chars] |
Memory creation failed during the initialization |
media-mon |
LOG_STD_ACTION |
|
MMA-3-NULLFLOW |
3-Error |
A flow does not exist |
An internal error occurred. Try to access a null flow |
media-mon |
LOG_STD_ACTION |
|
MMA-3-NULLHIST |
3-Error |
A history bucket does not exist |
An internal error occurred. Try to access a null history |
media-mon |
LOG_STD_ACTION |
|
MMA-3-PARSER |
3-Error |
[chars] |
Error during register parser or parsing CLI |
media-mon |
LOG_STD_ACTION |
|
MMA-3-PROV |
3-Error |
[chars] |
A fatal error happened during provision |
media-mon |
LOG_STD_ACTION |
|
MMA-3-RM_SET |
3-Error |
[chars] |
An error happened during setting of Resource Manager event |
media-mon |
LOG_STD_ACTION |
|
MMODE_ISSU-2-GET_BUFFER |
2-Critical |
MMODE ISSU client failed to get buffer for message. Error: [dec] [chars] |
MMODE 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. |
polaris-gir |
"show logging and show checkpoint client" |
|
MMODE_ISSU-2-INIT |
2-Critical |
MMODE ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The MMODE 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. |
polaris-gir |
LOG_STD_ACTION |
|
MMODE_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
MMODE ISSU client failed to send negotiation message. Error: [dec] [chars] |
The MMODE 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. |
polaris-gir |
"show logging and show checkpoint client" |
|
MMODE_ISSU-2-SESSION_ARBITRATE |
2-Critical |
MMODE ISSU client failed to register arbitrate callback. Error: [dec] [chars] |
The MMODE ISSU client failed to register arbitrate callback. If a problem occurs with the callback registration the standby device cannot be brought up properly. |
polaris-gir |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MMODE_ISSU-2-SESSION_NEGO |
2-Critical |
MMODE ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The MMODE 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. |
polaris-gir |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MMODE_ISSU-2-SESSION_REGISTRY |
2-Critical |
MMODE ISSU client failed to register session information. Error: [dec] [chars] |
The MMODE ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
polaris-gir |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MMODE_ISSU-3-INVALID_CAPABILITY |
3-Error |
MMODE ISSU client: invalid capability list |
MMODE ISSU client observed an error during capability negotiaiton. When this error happens there is a mismatch in the client capability between the active and standby unit. |
polaris-gir |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MMODE_ISSU-3-INVALID_SESSION |
3-Error |
MMODE ISSU client does not have a valid registered session. |
The MMODE ISSU client does not have a valid registered session. |
polaris-gir |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MMODE_ISSU-3-MSG_NOT_OK |
3-Error |
MMODE ISSU client 'Message Type [dec]' is not compatible |
The MMODE ISSU client received an incompatible message from the peer device. The message cannot be processed. |
polaris-gir |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
MMODE_ISSU-3-MSG_SIZE |
3-Error |
MMODE ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The MMODE ISSU client failed to calculate the MTU for the specified message. The MMODE ISSU client is not able to send the message to the standby device. |
polaris-gir |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
MMODE_ISSU-3-POLICY_NOT_SUPPORTED |
3-Error |
MMODE ISSU client does not support Message Type [dec] |
MMODE ISSU client received an message type which it does not support. The policy is applied to make the session incompatible. |
polaris-gir |
"show issu session <client_id>" |
|
MMODE_ISSU-3-REJECTED_CAPABILITY |
3-Error |
MMODE ISSU client rejected capability '[chars]' |
MMODE ISSU client rejected a capability during negotiaiton. When this error happens there is a mismatch in the client capability between the active and standby unit. |
polaris-gir |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MMODE_ISSU-3-REJECTING_CAPABILITY |
3-Error |
MMODE ISSU client rejecting capability '[chars]' |
MMODE ISSU client is rejecting a capability during negotiaiton. When this error happens there is a mismatch in the client capability between the active and standby unit. |
polaris-gir |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MMODE_ISSU-3-SESSION_UNREGISTRY |
3-Error |
MMODE ISSU client failed to unregister session information. Error: [dec] [chars] |
The MMODE ISSU client failed to unregister session information. |
polaris-gir |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MMODE_ISSU-3-TRANSFORM_FAIL |
3-Error |
MMODE ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The MMODE 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 MMODE state between the active device and the standby device is not identical. |
polaris-gir |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
MMODE-3-MMODE_CLASS_TRANSITION_TIMED_OUT |
3-Error |
Maintenance failed to [chars] class [chars] due to timeout |
This message will be seen if client fails to finish transition. |
polaris-gir |
"Use Show system mode maintenance clients to \n\ find which clients failed." |
|
MMODE-3-MMODE_CLIENT_TRANSITION_FAILED |
3-Error |
Maintenance failed to [chars] client [chars] |
This message will be seen if client returns nack. |
polaris-gir |
- |
|
MMODE-6-MMODE_CLIENT_NOT_FOUND |
6-Information |
Maintenance client [chars] not found |
This message will be seen if client listed in template sequence\n\ but not registered. |
polaris-gir |
- |
|
MMODE-6-MMODE_CLIENT_TRANSITION_COMPLETE |
6-Information |
Maintenance [chars] complete for [chars] |
This message will be seen if client completes transition. |
polaris-gir |
- |
|
MMODE-6-MMODE_CLIENT_TRANSITION_START |
6-Information |
Maintenance [chars] start for [chars] |
This message will be seen if client starts transition. |
polaris-gir |
- |
|
MMODE-6-MMODE_INSERTED |
6-Information |
System is in Normal Mode |
This message will be seen if system comes out of maintenance\n\ successfully by operator issued command or maintenance window is over. |
- |
- |
|
MMODE-6-MMODE_ISOLATED |
6-Information |
System is in Maintenance |
This message will be seen if maintenance mode intitated\n\ by operator is successful. |
- |
- |
|
MMODE-6-MMODE_SNAPSHOT_CREATE_ENTER_MMODE |
6-Information |
Generating current snapshot 'before_maintenance' |
This message will be seen for a snapshot created before entering mmode. |
polaris-gir |
- |
|
MMODE-6-MMODE_SNAPSHOT_CREATE_EXIT_MMODE |
6-Information |
Generating current snapshot 'after_maintenance' \n\nPlease use 'show system snapshots compare before_maintenance after_maintenance' to check the health of the system |
This message will be seen for a snapshot created before exiting mmode. |
polaris-gir |
- |
|
MN_SPA_PTP-3-BITS_CLOCK |
3-Error |
[chars] : SPA bits transmit clock has encountered error : 0x[hec] .\n |
Error message regarding BITS transmit clock failure |
spa-synce-all |
"OIR the SPA if the error is consistent" |
|
MN_SPA_PTP-3-GMII_LINKUP_DOWN |
3-Error |
GMII Links are [chars] and [chars] for ports 1 and 2 respectively on the SPA. |
Error Message: GMII link status has changed on the SPA. |
spa-synce-all |
"OIR the SPA to recover from the error." |
|
MN_SPA_PTP-3-SEMAHOG |
3-Error |
SEMAHOG by SPA [chars] Process holding Sema is [chars] |
SEMAPHORE LOCK ERROR |
spa-synce-all |
" Remove the config which caused this" |
|
MN_SPA_PTP-4-PTP_CLOCK_MODE |
4-Warning |
SPA [dec]/[dec] is working in PTP SLAVE or Boundary mode external clock on BITS port would be PTP recovered clock |
Info regarding external clock in PTP slave mode |
spa-synce-all |
"No further action required. This is an\n\ INFORMATION message not an error Message." |
|
MN_SPA_PTP-6-CONFIG_CHANGE |
6-Information |
Change in ToP configuration on [dec]/[dec]. This will result \n\ into Termination of all existing PTP sessions on [dec]/[dec]. |
To take effect of new/changed configuration requrie \n\ restart of PTP session |
spa-synce-all |
"No further action required. This is an \n\ INFORMATION message not an error Message." |
|
MN_SPA_PTP-6-SPLL_STATE_CHANGE |
6-Information |
Recovered clock in [dec]/[dec] status changed to [chars] |
Recovered clock status change info |
spa-synce-all |
"No further action required. This is an \n\ INFORMATION message not an error Message." |
|
MODEM_HIST-7-CONTROL |
7-Debug |
\n[chars]: Control Reply: 0x%02x%02x |
This is a tracing message indicating a reply to a control message\n\ was received. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-CSM_IC_CALLED_NUM |
7-Debug |
\n[chars]: ISDN incoming called number: [chars] |
This is a tracing message indicating the number of the ISDN\n\ line recieving a call. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-CSM_IC_CALLING_NUM |
7-Debug |
\n[chars]: ISDN incoming caller number: [chars] |
This is a tracing message indicating the number of an incoming\n\ ISDN caller. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-CSM_OC_CALLED_NUM |
7-Debug |
\n[chars]: ISDN outgoing called number: [chars] |
This is a tracing message indicating a dialed ISDN number. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-MICA_DEBUG_EVT |
7-Debug |
\n[chars]: [chars]: |
This is a tracing message indicating a host debug event reported by\n\ the specified MICA modem. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-MICA_DYNAMIC_EVT |
7-Debug |
\n[chars]: [chars]: [chars] |
This is a tracing message indicating a dynamic event reported by\n\ the specified MICA modem. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-MICA_END_CONN_EVT |
7-Debug |
\n[chars]: [chars]: [chars] |
This is a tracing message indicating an end-connection event\n\ from the specified MICA modem. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-MICA_LEAD_EVT |
7-Debug |
\n[chars]: [chars]: [chars] [chars] [chars] [chars] |
This is a tracing message indicating a lead event reported by\n\ the specified MICA modem. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-MICA_OOS_EVT |
7-Debug |
\n[chars]: [chars] \n%*s Cause: [chars] |
This is a tracing message indicating an out-of-service event\n\ from the specified MICA modem. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-MICA_STARTUP_EVT |
7-Debug |
\n[chars]: [chars] [chars]. \n%*s Modem firmware = [dec].[dec].[dec].[dec] |
This is a tracing message indicating successful startup of the\n\ specified MICA modem. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-MICA_STATE_EVT |
7-Debug |
\n[chars]: [chars] \n%*s State: [chars] |
This is a tracing message indicating a state event reported by\n\ the specified MICA modem. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-MICA_STATIC_EVT |
7-Debug |
\n[chars]: [chars]: [chars] |
This is a tracing message indicating a static event reported by\n\ the specified MICA modem. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-MICA_STATUS_EVT |
7-Debug |
\n[chars]: [chars]: [chars]. \n%*s Modem firmware = [dec].[dec].[dec].[dec] |
This is a tracing message indicating a status event reported by\n\ the specified MICA modem. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-POLL_ANALOG |
7-Debug |
\n[chars]: Modem Analog signal event: TX = [dec] RX = [dec] Signal to noise = [dec] |
This is a tracing message indicating a change in analog signal\n\ status. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-POLL_CALLER_ID |
7-Debug |
\n[chars]: Caller ID event: [chars] |
This is a tracing message indicating caller ID data received. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-POLL_CONN_1 |
7-Debug |
\n[chars]: Connection event: TX/RX Speed = [dec]/[dec] Modulation = [chars] |
This is a tracing message indicating establishment of a connection. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-POLL_CONN_2 |
7-Debug |
\n Direction = [chars] Protocol = [chars] Compression = [chars] |
This is a continuation of the connection state tracing message. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-POLL_CONX_UPDATE |
7-Debug |
\n[chars]: Connection update event: TX/RX Speed = [dec]/[dec] Modulation = [chars] |
This is a tracing message indicating a connection state change. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-POLL_DTR |
7-Debug |
\n[chars]: DTR event: [chars] |
This is a tracing message indicating a change in the DTR signal. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-POLL_END_1 |
7-Debug |
\n[chars]: End connection event: Retransmits for MNP block TX/RX = [dec]/[dec] |
This is a tracing message indicating end-of-connection status. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-POLL_END_2 |
7-Debug |
\n Duration = [dec]:%-02d:%-02d Number of TX/RX char = [dec]/[dec] |
This is a continuation of the end-of-transmission status message. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-POLL_END_3 |
7-Debug |
\n Local Disc Reason = [chars] Remote Disc Reason = [chars] |
This is another continuation of the end-of-transmission status\n\ message. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-POLL_ERROR |
7-Debug |
\n[chars]: Polling protocol error event: 0x%02x |
This is a tracing message indicating a polling protocol error. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-POLL_EVT_LOST |
7-Debug |
\n[chars]: Status event lost: 0x%02x |
This is a tracing message indicating a polling event was lost. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-POLL_INACT |
7-Debug |
\n[chars]: Modem Activity event: [chars] |
This is a tracing message indicating a change in data activity\n\ status. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-POLL_MODEM_STATE |
7-Debug |
\n[chars]: Modem State event: [chars] |
This is a tracing message indicating a modem state change. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-POLL_NO_RESP |
7-Debug |
\n[chars]: No poll response event: 0x%02x |
This is a tracing message indicating that no response was received\n\ to a poll. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-POLL_PHONE |
7-Debug |
\n[chars]: Phone number event: [chars] |
This is a tracing message indicating a phone number being dialed. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-POLL_PROGRESS |
7-Debug |
\n[chars]: Call Progress event: [chars] |
This is a tracing message indicating status of a call in progress. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-POLL_RS232 |
7-Debug |
\n[chars]: RS232 event: [chars][chars] [chars][chars] [chars][chars] [chars][chars] [chars][chars] [chars][chars] [chars][chars] |
This is a tracing message indicating RS232 events. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-POLL_TX_RX |
7-Debug |
\n[chars]: TX/RX event: TXD=[chars] RXD=[chars] |
This is a tracing message indicating transmit and receive events. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-POLL_UNKNOWN |
7-Debug |
\n[chars]: Unknown or lost event 0x%02x |
This is a tracing message indicating that the modem event history\n\ contained an unrecognized event. One or more events may be missing\n\ from the trace. |
- |
"This could be caused by insufficient space to store the modem\n\ history. If these events are desirable a possible remedy is to\n\ shorten the number of events recorded between history dumps. " LOG_STD_REDUCE_ACTION |
|
MODEM_HIST-7-STARTUP |
7-Debug |
\n[chars]: Startup Response: [chars]. \nModem boot firmware = [dec].[dec].[dec] [dec].[dec].[dec] |
This is a tracing message indicating successful startup of the\n\ specified modem. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-TRACE_HDR |
7-Debug |
\n\n[chars] Modem [chars] Events Log: |
This is the initial message for the trace of the specified modem.\n\ The modem's stored trace messages will follow. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_HIST-7-UNKNOWN_FRAME |
7-Debug |
\n[chars]: Error in events log |
This is a tracing message indicating a formatting error in the\n\ modem event history. One or more events may be missing from\n\ the trace. |
- |
LOG_STD_DBG_ACTION |
|
MODEM_NV-5-FLEXIBLE |
5-Notice |
[chars] |
This message type is created for all those messages which\n\ have simple ASCII text and does not take any parameter.\n\ Message tells what the problem is. |
as |
LOG_STD_ACTION |
|
MODEM-1-BADEVENT |
1-Alert |
Invalid modem management [chars] event 0x%02x for modem[chars] |
The modem management facility received an unrecognize event. |
- |
LOG_STD_ACTION |
|
MODEM-1-BADMODEM |
1-Alert |
Modem [chars] failed [chars] |
A software or hardware problem has been detected on a modem.\n\ The specific modem and reason are listed in the message. |
- |
LOG_STD_ACTION |
|
MODEM-1-DL_FAIL |
1-Alert |
Firmware download failed for slot [dec] module_mask [hec] |
The modem modules did not send back an Initialized message\n\ after the download. |
- |
LOG_STD_ACTION |
|
MODEM-1-DL_FAIL_BADFREE |
1-Alert |
Item to be freed is in queues [chars]. Slot [dec] module_mask 0x[hec] |
The attempt to free the dnld info structure was aborted. |
- |
LOG_STD_ACTION |
|
MODEM-1-DL_FAIL_FILE_XFER |
1-Alert |
Firmware download failed for slot [dec] module_mask 0x[hec] due to file transfer error |
The download of a portware file to the modem card over DSIP as\n\ part of a modem firmware upgrade attempt timed out and failed\n\ to complete successfully |
- |
"LOG_STD_ACTION" |
|
MODEM-1-DL_LOSS_FAIL |
1-Alert |
Firmware download failure for slot [dec] module [dec] |
The portware download for the module was previously deferred\n\ but when later ready to be performed the information needed\n\ for the download had been lost |
- |
"" |
|
MODEM-1-DL_PROC_FAIL |
1-Alert |
Portware download process creation failed |
- |
- |
"LOG_STD_ACTION" |
|
MODEM-3-BADMODEMNUM |
3-Error |
Error: Trying to access an invalid modem [dec] |
The requested operation could not be accomplished because of a bad modem number. Call your technical support representative for assistance |
modem-management |
LOG_STD_ACTION |
|
MODEM-3-MODEM_INFO_CREATE_FAIL |
3-Error |
Unable to create modem infos for slot [dec] |
During OIR of this board the modem infos attempted to be created but failed due to lack of memory |
- |
"If this message is seen then save the output of show memory showing\n\ the amount of processor and IO memory usage only along with show\n\ version and call your technical support representativ for\n\ assistance." |
|
MODEM-3-MODEMSTART_OUTOFMEM |
3-Error |
Error -- Unable to allocate memory to startup modem board in slot [dec] |
Running out of memory during modem board startup. |
- |
"If this message is seen then save the output of show memory showing\n\ the amount of processor and IO memory usage only along with show\n\ version and call your technical support representativ for\n\ assistance." |
|
MODEM-3-PWDNLDPROC |
3-Error |
Portware download manager process start-up failed |
The attempt to start up the portware download manager process at\n\ initialization time failed and so portware download requests cannot\n\ be handled. |
- |
LOG_STD_ACTION |
|
MODEM-3-UNEXPECTED_STATUS_EV |
3-Error |
Error -- status state machine received unexpected event=[dec] for modem[chars] |
The modem management subsystem's status-polling state machine\n\ received an undefined event for or from the specified modem. |
- |
LOG_STD_ACTION |
|
MODEM-3-UNEXPECTED_STATUS_STATE |
3-Error |
Error -- status state machine in unknown state=[dec] for modem[chars] |
The modem management subsystem's status-polling state machine\n\ for the specified modem entered an undefined state. |
- |
LOG_STD_ACTION |
|
MODEM-4-B2BABORT |
4-Warning |
Modems [chars] and [chars] back-to-back test: aborted |
This is a tracing message indicating a back-to-back test\n\ failed between the two specified MICA modems. |
- |
"Perform more back to back tests by pairing the failed modems with\n\ other modems to determine which modem is bad. Check the failed\n\ modems again after performing a power cycle. " LOG_STD_RECUR_ACTION |
|
MODEM-4-BADMODEMS |
4-Warning |
Modems [chars] and [chars] failed back-to-back test: [chars] |
The two modems reported in the message failed a back-to-back test.\n\ At least one of them has failed. |
- |
"Perform more back to back tests by pairing the failed modems with\n\ other modems to determine which modem is bad. Check the failed\n\ modems again after performing a power cycle. " LOG_STD_RECUR_ACTION |
|
MODEM-4-NO_TIME_FOR_DC |
4-Warning |
Warning -- Not enough time to process DC session |
- |
- |
LOG_STD_RECUR_ACTION |
|
MODEM-5-B2BCONNECT |
5-Notice |
Modems [chars] and [chars] connected in back-to-back test: [chars] |
A back to back test connection has been made between the selected\n\ modems. The test is still in progress. |
- |
LOG_STD_NO_ACTION |
|
MODEM-5-B2BINIT |
5-Notice |
Auto Back-to-Back test initiated by [chars] |
This is a tracing message indicating an automatic back-to-back\n\ test was initiated by the specified MICA modem. |
- |
LOG_STD_DBG_ACTION |
|
MODEM-5-B2BMODEMS |
5-Notice |
Modems [chars] and [chars] completed back-to-back test: success/packets = [dec]/[dec] |
The reported modems have passed the back to back test without any\n\ errors. |
- |
LOG_STD_NO_ACTION |
|
MODEM-5-CONFIG |
5-Notice |
Configurations \fast-answer\ and \country [chars]\ conflict.\n Configuration \fast-answer\ disabled. |
The fast-answer configuration conflicts with the country setting.\n\ The country was given priority and fast-answer was disabled. |
- |
LOG_STD_NO_ACTION |
|
MODEM-5-DL_GOOD |
5-Notice |
Modem [chars] completed firmware download: [chars] |
The specified modem has succeeded downloading its internal microcode. |
- |
LOG_STD_NO_ACTION |
|
MODEM-5-DL_START |
5-Notice |
Modem [chars] started firmware download |
The specified modem has begun downloading its internal microcode. |
- |
LOG_STD_NO_ACTION |
|
MODEM-5-MODEM_OK |
5-Notice |
Modem [chars] passed the test |
Tests on the specified modem were successful. |
- |
LOG_STD_NO_ACTION |
|
MODEM-5-MODEM_RECOVERY |
5-Notice |
Modem [chars] [chars] |
Modem recovery has been triggered. Configured action will\n\ take place on given modem |
- |
"" |
|
MODEM-5-MODEM_RECOVERY_DL |
5-Notice |
Slot [dec] Module [dec]: [chars] |
Module download information |
- |
"" |
|
MODEM-5-MODEM_RECOVERY_PROCESS |
5-Notice |
[chars] |
Modem Recovery Process information |
- |
"" |
|
MODEMCALLRECORD-3-PM_CALL_RECORD_ERROR |
3-Error |
[chars] |
Record Generated Exceeded Syslog Capability |
port-mgmt |
LOG_STD_NO_ACTION |
|
MODEMCALLRECORD-3-PM_NO_CALL_RECORD_BUF |
3-Error |
[chars] |
The Recovery Download Maintenance messages cannot be sent. |
port-mgmt |
LOG_STD_ACTION |
|
MODEMCALLRECORD-6-PM_TERSE_CALL_FAILED_RECORD |
6-Information |
[chars] |
Terse Modem Call Failed Record |
port-mgmt |
LOG_STD_NO_ACTION |
|
MODEMCALLRECORD-6-PM_TERSE_CALL_RECORD |
6-Information |
[chars] |
Terse Modem Call Record |
port-mgmt |
LOG_STD_NO_ACTION |
|
MODULE_STATE-3-MOD_TIMEOUT |
3-Error |
Timeout waiting for modules to come on-line. |
One or more modules can not come on-line. |
esg-chassismgr |
- |
|
MODULE_STATE-6-ALL_MODULES_UP |
6-Information |
All modules are now on-line. |
All modules are now on-line. |
esg-chassismgr |
- |
|
MONITOR-3-VARRESTFAIL |
3-Error |
ROM monitor variable restoration of \[chars]\ failed. |
The new ROM monitor variable could not be written to memory and the\n\ ROM monitor variable could not be restored to its original value. |
high-rommon |
"Copy the error message exactly as it appears on the console or in the\n\ system log. Issue the <CmdBold>show tech-support<NoCmdBold> and\n\ <CmdBold>show bootvar<NoCmdBold> commands to gather data that may help\n\ identify the nature of the error. If you cannot determine the nature\n\ of the error from the error message text or from the <CmdBold>show\n\ tech-support<NoCmdBold> and <CmdBold>show bootvar<NoCmdBold> command\n\ output contact your Cisco technical support representative and\n\ provide the representative with the gathered information." |
|
MONITOR-3-VARSETFAIL |
3-Error |
ROM monitor variable set of \[chars]\ failed. |
The system could not set a ROM Monitor variable. This condition\n\ typically occurs when no ROM monitor memory is available to save\n\ the variable. The ROM monitor memory is most likely already filled\n\ with configuration <CmdBold>boot<NoCmdBold> commands. |
high-rommon |
"Enter the <CmdBold>show bootvar<NoCmdBold> command and\n\ check the output to see if there is anything unusual with the system.\n\ Try to reduce the number of configuration boot commands." |
|
MONITOR-3-VPN_EVENT |
3-Error |
ipsec : [chars] : [dec] events |
Crypto failure count hits limit. This message is just a warning not an error. |
cpp-ucode |
LOG_STD_ACTION |
|
MPLS_ADJ_SB-3-MPLS_ADJ_GENERAL |
3-Error |
[chars] |
mpls adj sb error message |
mpls-mfi |
LOG_STD_ACTION |
|
MPLS_ADJ_SB-4-MPLS_ADJ_SB_ECMP |
4-Warning |
[chars] - slot [chars] |
MPLS ADJ ECMP not supported on Peers |
mpls-mfi |
LOG_STD_ACTION |
|
MPLS_ADJ_SB-4-MULTI_LABEL_STACK |
4-Warning |
[chars] - slot [chars] |
Multi-Label Stack not supported on Peers |
mpls-mfi |
LOG_STD_ACTION |
|
MPLS_ADJ_SB-4-NO_BACKUP_INTF |
4-Warning |
[chars] - ifnum [dec] |
Backup interface cannot be programmed |
mpls-mfi |
LOG_STD_ACTION |
|
MPLS_ADJ_SB-4-PATH_PRO_CUTOVER |
4-Warning |
[chars] - adj 0x[hec] sb 0x[hec] |
MFI adj or adj_sb error during path protection cutover |
mpls-mfi |
LOG_STD_ACTION |
|
MPLS_ADJ_SB-4-UNMATCHED_PRO_PATH |
4-Warning |
[chars] - adj 0x[hec] |
MFI adj_sb uses unmatched protect lsp from CEF adj parent |
mpls-mfi |
LOG_STD_ACTION |
|
MPLS_FORWARDING-2-CAUSE_THROTTLE_ERR |
2-Critical |
Allocation of mpls throttle [chars] memory failed |
Allocation of memory resource use by mpls throttle fail |
cpp-ucode |
LOG_STD_ACTION |
|
MPLS_IPRM-3-DB |
3-Error |
[chars] |
- |
- |
- |
|
MPLS_IPRM-3-DB |
3-Error |
[chars] |
There is an inconsistency in the information required to request labels from or to process labels received from an IP label distribution module |
mpls-iprm |
LOG_STD_ACTION |
|
MPLS_IPRM-3-DB_PATH |
3-Error |
[chars] |
- |
- |
- |
|
MPLS_IPRM-3-DB_PATH |
3-Error |
[chars] |
There is an inconsistency in the information about a prefix path required to request labels from or to process labels received from an IP label distribution module |
mpls-iprm |
LOG_STD_ACTION |
|
MPLS_IPRM-3-DB_PNDG_DISC |
3-Error |
[chars] |
- |
- |
- |
|
MPLS_IPRM-3-DB_PNDG_DISC |
3-Error |
[chars] |
There is an inconsistency in the information about a temporarily deferred action required to populate MPLS forwarding data structures for a prefix |
mpls-iprm |
LOG_STD_ACTION |
|
MPLS_IPRM-3-DB_TABLE |
3-Error |
[chars] |
- |
- |
- |
|
MPLS_IPRM-3-DB_TABLE |
3-Error |
[chars] |
There is an inconsistency in the information about a vrf tableid |
mpls-iprm |
LOG_STD_ACTION |
|
MPLS_IPRM-3-DB_TRANS |
3-Error |
[chars] |
- |
- |
- |
|
MPLS_IPRM-3-DB_TRANS |
3-Error |
[chars] |
There is an inconsistency in the information about an ongoing transaction required to populate MPLS forwarding data structures for a prefix |
mpls-iprm |
LOG_STD_ACTION |
|
MPLS_IPRM-3-INTERNAL |
3-Error |
[chars] |
- |
- |
- |
|
MPLS_IPRM-3-INTERNAL |
3-Error |
[chars] |
An operation required for proper operation of the IP rewrite manager has failed. |
mpls-iprm |
"LOG_STD_ACTION" |
|
MPLS_IPRM-3-PATH_LABEL_DEL |
3-Error |
[chars] |
- |
- |
- |
|
MPLS_IPRM-3-PATH_LABEL_DEL |
3-Error |
[chars] |
An attempt to delete MPLS forwarding information for the specified prefix has failed. |
mpls-iprm |
LOG_STD_ACTION |
|
MPLS_IPRM-3-PATH_LABEL_GET |
3-Error |
[chars] |
- |
- |
- |
|
MPLS_IPRM-3-PATH_LABEL_GET |
3-Error |
[chars] |
An attempt to access MPLS forwarding information for the specified prefix has failed. |
mpls-iprm |
LOG_STD_ACTION |
|
MPLS_IPRM-3-PATH_LABEL_UPD |
3-Error |
[chars] |
- |
- |
- |
|
MPLS_IPRM-3-PATH_LABEL_UPD |
3-Error |
[chars] |
An attempt to update MPLS forwarding information for the specified prefix has failed. |
mpls-iprm |
LOG_STD_ACTION |
|
MPLS_IPRM-3-WALK |
3-Error |
[chars] |
- |
- |
- |
|
MPLS_IPRM-3-WALK |
3-Error |
[chars] |
A request by an IP label distribution module e.g. LDP BGP to walk |
mpls-iprm |
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_PACKET-3-FWDDISABLE |
3-Error |
MPLS [chars] forwarding path disabled |
MPLS forwarding plane disabled |
mpls-mfi |
"This log entry is informational only." |
|
MPLS_PACKET-3-FWDREENABLE |
3-Error |
MPLS [chars] forwarding path reenabled |
MPLS forwarding plane reenabled |
mpls-mfi |
"This log entry is informational only." |
|
MPLS_PACKET-3-LABELCACHE |
3-Error |
[chars] [dec]/[dec] |
label cache error |
mpls-mfi |
LOG_STD_ACTION |
|
MPLS_PACKET-3-WRONGIDB |
3-Error |
MPLS packet input sub interface hwidb [chars] does not match with |
Internal software error occurred |
mpls-mfi |
LOG_STD_ACTION |
|
MPLS_PACKET-4-NOLFDSB |
4-Warning |
MPLS packet received on non MPLS enabled interface [chars] L3 type 0x%04x label {[dec] [dec] [dec] [dec]} |
MPLS packets received on an interface are being dropped as the interface is not setup to handle MPLS. This message may be seen when a mpls application is disabled on a interface and should go away when the upstream neighbor has reprogrammed its cef/mpls entries. |
mpls-mfi |
"If a MPLS application has just be disabled and traffic is flowing" "then the message is expected and should be ignored." "If the message recurs in steady state the operator should monitor" "the network for attacks and report the occurence to Cisco." |
|
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_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_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-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-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_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_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-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_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_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-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_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_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_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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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_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-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-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_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-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-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_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_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-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-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-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_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_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_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_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_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_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-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-LSP_BAD_GPID_REQUESTED |
3-Error |
[chars]: LSP requests G-PID unsupported or invalid |
- |
- |
- |
|
MPLS_TE_LM-3-LSP_BAD_GPID_REQUESTED |
3-Error |
[chars]: LSP requests G-PID unsupported or invalid |
- |
- |
- |
|
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_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_SWITCHING_TYPE_REQUESTED |
3-Error |
[chars]: LSP requests switching type [[chars]] unsupported on link [[chars]] |
- |
- |
- |
|
MPLS_TE_LM-3-LSP_BAD_SWITCHING_TYPE_REQUESTED |
3-Error |
[chars]: LSP requests switching type [[chars]] unsupported on link [[chars]] |
- |
- |
- |
|
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-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_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" |
|
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" |
|
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_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_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-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_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-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-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_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-MEM |
2-Critical |
[chars] [dec] |
A failure at an attempt to alloc memory was detected |
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-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-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-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-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-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-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-2-ADJ_WALK_ERR |
2-Critical |
[chars] |
Error during bundle adjacency walk |
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-2-BUNDLE_INSERT |
2-Critical |
[chars] [chars] |
Request for inserting a traffic engineering tunnel bundle failed. |
mpls-te |
LOG_STD_ACTION |
|
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-UNSUPPORTED_LINK_TYPE |
2-Critical |
[chars] |
Unsupported link type |
mpls-te |
LOG_STD_ACTION |
|
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-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-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-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-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-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-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-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-TUNNELKILL |
3-Error |
Tunnel removal attempt by [chars] failed for tunnel [chars]: [chars] |
- |
- |
- |
|
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-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-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-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-4-PCEP_REPORT_FAILED |
4-Warning |
LSP TID:[dec] LID:[dec] wasn't reported to the PCE server |
- |
- |
- |
|
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 |
- |
- |
- |
|
MPLS_TE-4-PCEP_REQUEST_FAILED |
4-Warning |
Unable to request path for LSP TID:[dec] LID:[dec] from PCE server |
- |
- |
- |
|
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-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-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-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-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_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 |
|
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_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_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-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_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_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_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_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_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-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-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_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_VPN_HA-3-CF_GEN_ERROR |
3-Error |
[chars] |
MPLS VPN HA client CF related general error. |
mpls-vpn |
LOG_STD_ACTION |
|
MPLS_VPN_HA-3-CLIENTREG |
3-Error |
[chars] |
MPLS VPN HA failed to register to CF. |
mpls-vpn |
LOG_STD_ACTION |
|
MPLS_VPN_HA-3-DBOPERATION |
3-Error |
[chars] RD [chars] [inet]/[dec] label [dec] |
MPLS VPN HA Checkpoint database operation error. |
mpls-vpn |
LOG_STD_ACTION |
|
MPLS_VPN_HA-3-SIZEMISMATCH |
3-Error |
Label table size [dec] mismatch get label tableid failed. |
MPLS VPN HA Label Table size mismatch. |
mpls-vpn |
LOG_STD_ACTION |
|
MPLS_VPN_HA-7-LABELFREE |
7-Debug |
[chars] [dec] |
MPLS VPN Label Manager failed to free label. |
mpls-vpn |
LOG_STD_ACTION |
|
MPLS_VPN_HA-7-MALLOCFAIL |
7-Debug |
[chars] |
MPLS VPN HA failed to allocate memory |
mpls-vpn |
LOG_STD_ACTION |
|
MPLS_VPN_HA-7-XMITFAIL |
7-Debug |
[chars] message seq no [dec] current seq no [dec] |
MPLS VPN Label Manager failed to deliver a message |
mpls-vpn |
LOG_STD_ACTION |
|
MPLS_VPN_ISSU-3-CF_ERR |
3-Error |
[chars] 0x[hec] |
MPLS VPN ISSU client CF related error. |
mpls-vpn |
LOG_STD_ACTION |
|
MPLS_VPN_ISSU-3-GENERR |
3-Error |
[chars] |
MPLS VPN ISSU client general error. |
mpls-vpn |
LOG_STD_ACTION |
|
MPLS_VPN_ISSU-3-ISSU_RC_ERR |
3-Error |
[chars] [chars] |
MPLS VPN ISSU client ISSU infra related error. |
mpls-vpn |
LOG_STD_ACTION |
|
MPLS-3-FRR_BDI_UNSUPPORTED |
3-Error |
FRR not enabled on [chars]. Unsupported EFP and trunk EFP count [dec]. Supported 1 |
LFA FRR support on ASR903 for BDI interface is available with just one EFP or trunk EFP |
asr903-mpls |
"shutdown the BDI interface. Remove all the " " EFPs/TEFPs under the BDI. Create just one EFP or TEFP." " no shutdown the BDI interface" |
|
MPLS-3-FRR_BDI_UNSUPPORTED |
3-Error |
FRR not enabled on [chars]. Unsupported EFP and trunk EFP count [dec]. Supported 1 |
LFA FRR support on ASR903 for BDI interface is available with just one EFP or trunk EFP |
asr903-mpls |
"shutdown the BDI interface. Remove all the " " EFPs/TEFPs under the BDI. Create just one EFP or TEFP." " no shutdown the BDI interface" |
|
MPLS-3-FRR_BDI_UNSUPPORTED |
3-Error |
FRR not enabled on [chars]. Unsupported EFP and trunk EFP count [dec]. Supported 1 |
LFA FRR support on ASR903 for BDI interface is available with just one EFP or trunk EFP |
asr903-mpls |
"shutdown the BDI interface. Remove all the " " EFPs/TEFPs under the BDI. Create just one EFP or TEFP." " no shutdown the BDI interface" |
|
MPLS-3-FRR_BDI_UNSUPPORTED |
3-Error |
FRR not enabled on [chars]. Unsupported EFP and trunk EFP count [dec]. Supported 1 |
LFA FRR support on ASR903 for BDI interface is available with just one EFP or trunk EFP |
asr903-mpls |
"shutdown the BDI interface. Remove all the " " EFPs/TEFPs under the BDI. Create just one EFP or TEFP." " no shutdown the BDI interface" |
|
MPLS-3-INCORRECT_LENTRY_ENCAP |
3-Error |
[chars]: mplsd swap 1 encap [dec] |
Lentry has incorrect encap |
asr903-mpls |
"Please collect this error message tracebacks " "and nile mgr logs" |
|
MPLS-3-MAX_PW_EXCEEDED |
3-Error |
Number of PW's exceeded supported limit [dec] |
Number of empls intd labels exceeded supported scale |
asr903-mpls |
"Please reduce the number of PW's to supported scale" |
|
MPLS-3-MAX_PW_EXCEEDED |
3-Error |
Number of PW's exceeded supported limit [dec] |
Number of PW's exceeded supported scale |
rsp2-mpls |
"Please reduce the number of PW's to supported scale" |
|
MPLS-3-MAX_PW_EXCEEDED |
3-Error |
Number of PW's exceeded supported limit [dec] |
Number of empls intd labels exceeded supported scale |
firmware |
"Please reduce the number of PW's to supported scale" |
|
MPLS-3-MAX_PW_EXCEEDED |
3-Error |
Number of PW's exceeded supported limit [dec] |
Number of empls intd labels exceeded supported scale |
firmware |
"Please reduce the number of PW's to supported scale" |
|
MPLS-3-MAX_ROUTED_PW_EXCEEDED |
3-Error |
Number of Routed PW's exceeded supported limit [dec] |
Number of Routed PW's exceeded supported scale |
rsp2-mpls |
"Please reduce the number of " "Routed PW's to supported scale" |
|
MPLS-3-MAX_RPW_EXCEEDED |
3-Error |
Number of Routed PW's exceeded supported limit [dec] |
Number of Routed PW exceeded supported scale |
firmware |
"Please reduce the number of Routed PW's to " "supported scale" |
|
MPLS-3-MPLS_MTU_ALLOC_FAIL |
3-Error |
Out of resource to allocate mpls mtu |
mpls mtu exceeded supported scale |
asr903-mpls |
"Please reduce the number of mpls mtu configured values" "to supported scale" |
|
MPLS-3-MPLS_MTU_ALLOC_FAIL |
3-Error |
Out of resource to allocate mpls mtu |
mpls mtu exceeded supported scale |
asr903-mpls |
"Please reduce the number of mpls mtu configured values" "to supported scale" |
|
MPLS-3-MPLS_MTU_ALLOC_FAIL |
3-Error |
Out of resource to allocate mpls mtu |
mpls mtu exceeded supported scale |
asr903-mpls |
"Please reduce the number of mpls mtu configured values" "to supported scale" |
|
MPLS-3-MPLS_MTU_ALLOC_FAIL |
3-Error |
Out of resource to allocate mpls mtu |
mpls mtu exceeded supported scale |
asr903-mpls |
"Please reduce the number of mpls mtu configured values" "to supported scale" |
|
MPLS-3-MPLS_STALE_LABEL |
3-Error |
Stale Label : [dec] Neither Allocated nor Deallocated |
Stale Label Neither Allocated nor Deallocated |
asr903-mpls |
"Don't collect the stats for this instance" |
|
MPLS-3-MPLS_STALE_LABEL |
3-Error |
Stale Label : [dec] Neither Allocated nor Deallocated |
Stale Label Neither Allocated nor Deallocated |
rsp2-mpls |
"Don't collect the stats for this instance" |
|
MPLS-3-OUT_OF_LABEL_SPACE |
3-Error |
Out of resource to create labels |
Number of empls intd labels exceeded supported scale |
asr903-mpls |
"Please reduce the number of empls intd labels to " "supported scale" |
|
MPLS-3-OUT_OF_LABEL_SPACE |
3-Error |
Out of resource to create labels |
Number of empls intd labels exceeded supported scale |
rsp2-mpls |
"Please reduce the number of empls intd labels to " "supported scale" |
|
MPLS-3-OUT_OF_LABEL_SPACE |
3-Error |
Out of resource to create labels |
Number of empls intd labels exceeded supported scale |
firmware |
"Please reduce the number of empls intd labels to " "supported scale" |
|
MPLS-3-OUT_OF_LABEL_SPACE |
3-Error |
Out of resource to create labels |
Number of empls intd labels exceeded supported scale |
firmware |
"Please reduce the number of empls intd labels to " "supported scale" |
|
MPLS-3-OUT_OF_LABEL3_SPACE |
3-Error |
Out of resource to create labels |
Number of empls 3d labels exceeded supported scale |
asr903-mpls |
"Please reduce the number of empls 3d labels to " "supported scale" |
|
MPLS-3-OUT_OF_LABEL3_SPACE |
3-Error |
Out of resource to create labels |
Number of empls 3d labels exceeded supported scale |
rsp2-mpls |
"Please reduce the number of empls 3d labels to " "supported scale" |
|
MPLS-3-OUT_OF_LABEL3_SPACE |
3-Error |
Out of resource to create labels |
Number of empls 3d labels exceeded supported scale |
firmware |
"Please reduce the number of empls 3d labels to " "supported scale" |
|
MPLS-3-OUT_OF_LABEL3_SPACE |
3-Error |
Out of resource to create labels |
Number of empls 3d labels exceeded supported scale |
firmware |
"Please reduce the number of empls 3d labels to " "supported scale" |
|
MPLS-3-VPLS_PORT_DEFAULT_LIF_LEARNING_ENABLE |
3-Error |
Default lif learning enable issue on lif 0x[hec] intf [chars] |
Learning set/unset in port and default lif |
rsp3-mpls |
"Please enable/disable mpls ip " |
|
MPLS-3-VPLS_PORT_DEFAULT_LIF_LEARNING_ENABLE |
3-Error |
Default lif learning enable issue on lif 0x[hec] intf [chars] |
Learning set/unset in port and default lif |
dominica-mpls |
"Please enable/disable mpls ip " |
|
MPLS-3-VPLS_PORT_LEARNING_ENABLE |
3-Error |
Port Learning enable issue on port [chars] |
Learning set/unset in port and default lif |
rsp3-mpls |
"Please enable/disable mpls ip on port" |
|
MPLS-3-VPLS_PORT_LEARNING_ENABLE |
3-Error |
Port Learning enable issue on port [chars] |
Learning set/unset in port and default lif |
dominica-mpls |
"Please enable/disable mpls ip on port" |
|
MPLS-4-PIC_BDI_UNSUPPORTED |
4-Warning |
BGP PIC not enabled on [chars]: [chars] |
Hardware could not be programmed for BGP PIC support on BDI interface |
asr903-mpls |
"Collect the logs and contect Cisco TAC" |
|
MPLS-4-PIC_BDI_UNSUPPORTED |
4-Warning |
BGP PIC not enabled on [chars]: [chars] |
Hardware could not be programmed for BGP PIC support on BDI interface |
asr903-mpls |
"Collect the logs and contect Cisco TAC" |
|
MPLS-4-PIC_BDI_UNSUPPORTED |
4-Warning |
BGP PIC not enabled on [chars]: [chars] |
Hardware could not be programmed for BGP PIC support on BDI interface |
asr903-mpls |
"Collect the logs and contect Cisco TAC" |
|
MPLSIFMIB-3-GENERAL |
3-Error |
[chars] |
Probable memory corruption of mpls layer subblock -- cause unknown. |
mpls-mib |
LOG_STD_ACTION |
|
MPLSMFISTATIC-3-CHUNKMGR |
3-Error |
[chars] [hec] |
MPLS MFI Static Application chunk manager error has occurred. |
mpls-mfi |
"Problem may be due to a low memory condition on the device. " "Check system memory and minimum memory requirements for this " "release and configuration and add memory if required. If " "memory appears to be sufficient and problem persists refer " "to the Bug Navigator at www.cisco.com to see if this condition " "has been previously reported and resolved in a later release. " "If not gather the output of <CmdBold>show process memory<NoCmdBold> <CmdBold>show " "version<NoCmdBold> and <CmdBold>show running-config<NoCmdBold> and contact your Cisco " "technical support representative." |
|
MPLSMFISTATIC-3-FCALLFAILED |
3-Error |
[chars] |
MPLS MFI Static Application function call return error |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release. If not gather the output of <CmdBold>show version<NoCmdBold> " "and <CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
MPLSMFISTATIC-3-INVALIDPRAMS |
3-Error |
[chars] [dec] |
Unexpected MPLS MFI Static Application parameter error |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release. If not gather the output of <CmdBold>show version<NoCmdBold> " "and <CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
MPLSMFISTATIC-3-WRONGCODEPATH |
3-Error |
[chars] |
Unexpected MPLS MFI Static Application code path error |
mpls-mfi |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release. If not gather the output of <CmdBold>show version<NoCmdBold> " "and <CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
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-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-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-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 |
|
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 |
|
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 |
|
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-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-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 |
|
MPOA-3-MPC_ERROR |
3-Error |
[chars] |
A software error has occurred in the multiprotocol-over-ATM client MPC software. |
- |
LOG_STD_SH_TECH_ACTION |
|
MPOA-3-MPOA_ERROR |
3-Error |
[chars] |
A software error has occurred in the multiprotocol-over-ATM subsystem. |
- |
LOG_STD_SH_TECH_ACTION |
|
MPOA-3-MPS_ERROR |
3-Error |
[chars] |
\n\ A software error has occurred in the multiprotocol-over-ATM server MPS software. |
- |
LOG_STD_SH_TECH_ACTION |
|
MPOA-4-MPC_WARNING |
4-Warning |
[chars] |
This is a non-fatal warning from the multiprotocol-over-ATM client MPC software probably the result of an incorrect |
- |
"Try to determine if a configuration or operator " "error has caused this warning." LOG_STD_RECUR_ACTION |
|
MPOA-4-MPS_WARNING |
4-Warning |
[chars] |
This is a non-fatal warning from the multiprotocol-over-ATM server MPS software probably the result of an incorrect |
- |
"Try to determine if a configuration or operator " "error has caused this warning." LOG_STD_RECUR_ACTION |
|
MPOA-5-UPDOWN |
5-Notice |
[chars] |
A multiprotocol-over-ATM entity was brought up or down. This is only a status message. |
- |
LOG_STD_NO_ACTION |
|
MPOA-6-MPC_INFORMATION |
6-Information |
[chars] |
This is a multiprotocol-over-ATM client MPC |
- |
LOG_STD_NO_ACTION |
|
MPOA-6-MPS_INFORMATION |
6-Information |
[chars] |
This is a multiprotocol-over-ATM server MPS |
- |
LOG_STD_NO_ACTION |
|
MRIB_API-3-ASYNC_ERR |
3-Error |
Asynchronous error: [chars]. errno 0x[hec] |
An unhandled asynchromous error occurred in the MRIB API |
ipmulticast |
LOG_STD_ACTION |
|
MRIB_API-3-CORRPT |
3-Error |
Corrupted update: [chars] |
A corrupted update was received form the MRIB by the MRIB API |
ipmulticast |
LOG_STD_ACTION |
|
MRIB_API-3-REG_FAIL |
3-Error |
Server unexpected error: [chars] |
An internal error occurred in a registry call from the MRIB API |
ipmulticast |
LOG_STD_ACTION |
|
MRIB_API-7-ASYNC_WAR |
7-Debug |
Warning: [chars] |
A recoverable error condition occurred in the MRIB API |
ipmulticast |
LOG_STD_NO_ACTION |
|
MRIB_PROXY-2-MRIB_INTERNAL |
2-Critical |
The unrecoverable error \[chars]\ occurred in the MRIB-IPC subsystem. |
An unrecoverable error occurred restart the MRIB subsystem. |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
MRIB_PROXY-2-MRIB_LC_FAILED_GET_IPC |
2-Critical |
LC failed allocating IPC buffer which may lead to data loss or inconsistent MFIB states slot = [dec] |
The Linecard has failed in allocating interprocessor communication buffer. |
ipmulticast |
LOG_STD_REDUCE_ACTION |
|
MRIB_PROXY-2-MRIB_LC_FAILED_IDB_MAP |
2-Critical |
LC failed in mapping interface number [dec] |
The linecard failed in mapping an interface from the global representation to the local one |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
MRIB_PROXY-2-MRIB_LC_FAILED_NO_TABLE_NAME |
2-Critical |
LC in slot [dec] failed to connect to RP due to missing table name. |
The linecard could not instigate a connection to the RP for this instance as it was not supplied a table name. |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
MRIB_PROXY-2-MRIB_LC_FETCH_FAIL |
2-Critical |
LC in slot [dec] failed to send an RPC fetch request to the RP: [chars] |
The linecard attempted to read mroute updates from the route processor but the RPC request failed. The linecard MFIB state may now be inconsistent or frozen. |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
MRIB_PROXY-2-MRIB_LC_NOT_OPENED |
2-Critical |
LC in slot [dec] attempted to contact the RP without having opened the connection first |
The linecard called an MRIB API that required the connection with the MRIB in the RP to be opened but no connection had been established. |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
MRIB_PROXY-2-MRIB_LC_UPDATE_IGNORED |
2-Critical |
LC in slot [dec] ignored one or more mroute updates |
The linecard ignored one or more mroute updates because the buffer containing them failed a sanity check. The linecard MFIB state may now be inconsistent. |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
MRIB_PROXY-2-MRIB_RP_CREPRC_FAILED |
2-Critical |
The Route Processor failed to create a required process. |
The Route Processor could not create the MRIB RP proxy process. Distributed multicast will not be started on this system. |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
MRIB_PROXY-2-MRIB_RP_FAILED_GET_IPC |
2-Critical |
RP failed allocating IPC buffer which may lead to data loss or inconsistent MFIB states |
The Route Processor has failed in allocating interprocessor communication buffer. |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
MRIB_PROXY-2-MRIB_RP_FAILED_IDB_MAP |
2-Critical |
RP failed in mapping interface |
The route processor failed in mapping an interface from the global representation to the local one or vice-versa |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
MRIB_PROXY-2-MRIB_RP_FAILED_IPC_CREATE |
2-Critical |
RP failed in creating IPC port error = [chars] |
The Route Processor failed to create MFIB Interprocess Communications port |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
MRIB_PROXY-2-MRIB_RP_FAILED_LC_PORT_INFO |
2-Critical |
RP failed in creating linecard port info for distributed mode slot = [dec] |
The Route Processor has failed in creating linecard port info for distributed mode |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
MRIB_PROXY-3-MRIB_LC_CREPRC_FAILED |
3-Error |
LC in slot [dec] failed to create a required process. Verify MRIB updates are being distributed to this LC. |
The linecard could not create a process to perform delayed IPC initialization. The MFIB will not be started on this linecard. |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
MRIB_PROXY-3-MRIB_LC_FAILED_IPC_OPEN |
3-Error |
LC in slot [dec] failed to open IPC port to RP error = [chars]. Verify MRIB updates are being distributed to this LC. |
The linecard has failed to open IPC port towards the Route Processor |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
MRIB_PROXY-3-MRIB_LC_FAILED_SEND_LC_READY |
3-Error |
LC in slot [dec] failed to send LC ready to RP error = [chars]. Verify MRIB updates are being distributed to this LC. |
The linecard has failed to send Ready message to the Route Processor |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
MRIB_PROXY-3-MRIB_LC_READY_NOIPC |
3-Error |
LC in slot [dec] failed allocating IPC buffer to send LC ready Verify MRIB updates are being distributed to this LC. |
The Linecard has failed in allocating interprocessor communication buffer to send the ready message. |
ipmulticast |
LOG_STD_REDUCE_ACTION |
|
MRIB_PROXY-3-MRIB_RP_FAILED_LC_PORT_OPEN |
3-Error |
RP failed in opening linecard port info for distributed mode slot = [dec]. Verify MRIB updates are being distributed to this LC. |
The Route Processor has failed in opening linecard port info for distributed mode |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
MRIB_PROXY-4-MRIB_LC_IO_CLOSE_PENDING_FETCH |
4-Warning |
LC CCB : \[chars]\ close deferred |
MRIB LC connection to MFIB close attempted while MRIB update fetch in progress connection close deferred. |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
MRIB_PROXY-4-MRIB_LC_IO_CLOSE_PENDING_WRITE |
4-Warning |
LC CCB : \[chars]\ close deferred |
MRIB LC connection to MFIB close attempted while MRIB update write in progress connection close deferred. |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
MRIB-2-NOMEMORY |
2-Critical |
No memory for [chars] in [chars] |
The requested operation could not be accomplished because of a low\n\ memory condition. |
ipmulticast |
LOG_STD_REDUCE_ACTION |
|
MRIB-3-BNDL_NOMEM_FATAL |
3-Error |
Update-Set fatal allocation error [chars] |
Allocation of memory failed during the processing of an Update-Set. This failure my result in database inconsistency. |
- |
LOG_STD_REDUCE_ACTION |
|
MRIB-3-GENCOMMERR |
3-Error |
Communication error: [chars] [chars] in [chars] |
A Inter Process Communication error occurred. |
ipmulticast |
LOG_STD_ACTION |
|
MRIB-3-GENINITFAIL |
3-Error |
Initialization failed: [chars] [chars] |
An unrecoverable error occurred at system initialization time. |
ipmulticast |
LOG_STD_ACTION |
|
MRIB-3-INTERNALERR |
3-Error |
Internal error: [chars] in [chars] line [dec] [chars] |
An internal software error occurred. |
ipmulticast |
LOG_STD_ACTION |
|
MRIB-3-MESG_NOMEM_FATAL |
3-Error |
Allocation of memory failed for an incoming message |
Allocation of memory failed during the processing of an incoming message. This failure my have unpredictable results. |
- |
LOG_STD_REDUCE_ACTION |
|
MRIB-3-REDUCEDFUNCT |
3-Error |
Initialization of \[chars]\ functionality failed |
The initialization of a functionality failed. This component might\n\ still operate without the functionality. |
ipmulticast |
LOG_STD_REDUCE_ACTION |
|
MRIB-4-BNDL_ID_INUSE |
4-Warning |
An old Update-Set ID is still in use [hec] |
While allocating Update-Set IDs the MRIB found an old ID still in use. This could be due to a programming error. |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
MRIB-4-BNDL_MSG |
4-Warning |
Update-Set invalid message [chars] |
An invalid message was received during the processing of an Update-Set. |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
MRIB-4-BNDL_NOMEM |
4-Warning |
Update-Set allocation error [chars] |
Allocation of memory failed during the processing of an Update-Set. This failure my result in inefficient processing of route-updates. |
ipmulticast |
LOG_STD_REDUCE_ACTION |
|
MRIB-4-DEBUGERR |
4-Warning |
Debugging error: [chars] in [chars] line [dec] [chars] |
An error related to the debugging subsystem occurred. |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
MRIB-4-FILTRVIOLERR |
4-Warning |
Filter violation error: conn [dec] [chars]:[chars] in [chars] |
A client tried to modify a route attribute not owned by it. |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
MRIB-4-INCORRECTPARS |
4-Warning |
Illegal parameter in function call [chars] in [chars] |
An externally accessible function has been called with illegal\n\ parameters. the parameters has been casted to an acceptable value. |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
MRIB-4-NOMEMORYW |
4-Warning |
No memory for [chars] in [chars]. Handling: [chars] |
The requested operation could not be accomplished because of a low\n\ memory condition but the problem has ben handled locally. |
ipmulticast |
LOG_STD_REDUCE_ACTION |
|
MROUTE-2-RADIXINIT |
2-Critical |
Error initializing IP multicast radix for [inet] |
Insufficient memory is available to initialize the IP multicast\n\ routing table. |
- |
LOG_STD_SH_TECH_ACTION |
|
MROUTE-2-TOPO_WAVLINIT |
2-Critical |
Error initializing IP multicast wavl handler for [inet] |
Insufficient memory is available to initialize the IP multicast\n\ multi-topology routing table. |
- |
LOG_STD_SH_TECH_ACTION |
|
MROUTE-3-IGMP_LATE_PROCESS_ERR |
3-Error |
IGMP process is not up yet |
An error occured accessing IGMP process watched queue |
ipmulticast |
"An error in accessing IGMP process watched queue." LOG_STD_ACTION |
|
MROUTE-3-IGMP_NOT_FOUND |
3-Error |
IGMP group [inet] to delete from interface [chars] not found |
The group to be deleted from the interface could not be found in the\n\ IGMP cache. |
- |
"An inconsistency in maintaining the IGMP cache occurred." LOG_STD_ACTION |
|
MROUTE-3-IGMP_TWHEEL_INIT_ERR |
3-Error |
Error trying to initialize the IGMP timer wheel |
An error occured intializing a timer twheel |
- |
"An error in maintaining the timer wheel occurred." LOG_STD_ACTION |
|
MROUTE-3-IGMP_WAVL_ERROR |
3-Error |
IGMP wavl [chars] failed for group [inet] in interface [chars] |
The addition/deletion of igmp group in wavl tree failed. |
igmp |
"Collect 'show tech ipmulticast' output." LOG_STD_ACTION |
|
MROUTE-3-MIDB_QUEUE_ERR |
3-Error |
Interface [chars] not in [inet] [inet] |
This is an error condition. The midb has the highest expiration timer but is not in the mdb->midb |
- |
"An error in maintaining the multicast route table occurred." LOG_STD_ACTION |
|
MROUTE-3-NO_PIM_NBR |
3-Error |
There is no PIM neighbor on this IDB: [chars] |
Probably PIM is not configured correctly on this interface or on interfaces of the nexthop routers. |
- |
"Check PIM configurations on local and neighbor routers." LOG_STD_ACTION |
|
MROUTE-3-NOT_IN_MDB_OR_GDB_CACHE |
3-Error |
*G or SG being deleted for group [inet] does not exist in the |
An error occured due to which the gdb or mdb being deleted does not \n\ exist in it's respective cache |
- |
"An error has occurred in maintaining mdb." LOG_STD_ACTION |
|
MROUTE-3-RECUR_ROUTE_DEPTH_ERR |
3-Error |
Recursive route lookup has reached its max depth for: [inet] |
Recursive route lookup has a pre-defined depth limit and it has been reached. |
- |
"If possible reduce rounds of next hop lookup needed for the network address in question." LOG_STD_ACTION |
|
MROUTE-3-ROUTECOUNT_ZERO |
3-Error |
Multicast route count reached zero |
The running count of multicast routes reached zero when it \n\ should be non-zero. |
- |
"An error in maintaining the multicast route count occurred." LOG_STD_ACTION |
|
MROUTE-3-TWHEEL_DELAY_ERR |
3-Error |
Exceeded maximum delay [dec] ms requested: [dec] |
Because of the way the timer wheel works there is a maximum delay defined. If we try to schedule a function with a higher delay we still schedule it using the maximum delay possible |
- |
"An error in maintaining the timer wheel occurred." LOG_STD_ACTION |
|
MROUTE-3-TWHEEL_ERR |
3-Error |
Timer wheel internal error |
Timer wheel internal error |
- |
"An error in maintaining the timer wheel occurred." LOG_STD_ACTION |
|
MROUTE-3-TWHEEL_INIT_ERR |
3-Error |
Trying to re-initialize an already initialized timer wheel |
An error occured intializing a timer twheel |
- |
"An error in maintaining the timer wheel occurred." LOG_STD_ACTION |
|
MROUTE-3-TWHEEL_INSERT_ERR |
3-Error |
An error occured after inserting or executing a timer wheel event |
An error occured after inserting or executing a timer wheel event |
- |
"An error in maintaining the timer wheel occurred." LOG_STD_ACTION |
|
MROUTE-3-TWHEEL_INT_ERR |
3-Error |
Timer wheel error at interrupt level [dec] |
Timer wheel internal error |
- |
"An error in maintaining the timer wheel occurred." LOG_STD_ACTION |
|
MROUTE-3-TWHEEL_SLOT_ERR |
3-Error |
Timer wheel event:[hec] slot:[dec] func:[hec] unequal to exec slot: [dec] |
Timer wheel event has inconsistent slot number |
- |
"Clear ip mroute *" LOG_STD_ACTION |
|
MROUTE-3-WAVLINIT |
3-Error |
Could not initialize WAVL tree for [inet][inet] |
When the WAVL tree can not be initialized we can't search for midbs\n\ so there is no reason to keep the mdb around. |
- |
"An error in initializing the multicast routing occurred." LOG_STD_ACTION |
|
MROUTE-4-INCONSISTENT_IDB_TABLEID |
4-Warning |
PIM detected inconsistency in table-id information on [chars]. |
PIM detected that the interface tableid is not the same as the value\n\ maintained by the multicast code |
mcast-vpn |
"LOG_STD_ACTION" |
|
MROUTE-4-IPMC_INVALID_SB |
4-Warning |
Unexpected access to IP Multicast interface subblock field |
IOS attempts to access the value of an IP Multicast interface field\n\ whose interface subblock is not yet created. |
- |
"An inconsistency accessing an IP Multicast interface subblock occurred." LOG_STD_ACTION |
|
MROUTE-4-MROUTELIMIT |
4-Warning |
Exceeded multicast limit for group [inet] source [inet] on interface [chars] |
The allowed number of multicast routes having the incoming or outgoing\n\ interface reached the limit specified by a configured access-list.\n\ New routes cannot be added unless the interface configuration is changed. |
- |
"If multicast traffic over the interface is of any priority\n\ among the traffic carried by this router then use the 'ip multicast limit'\n\ interface command to increase the number of multicast routes.\n\ Otherwise no action is required.\n\ Use 'debug ip mroute limit' and/or 'show ip multicast limit'\n\ to find exactly which multicast interface limit was exceeded." |
|
MROUTE-4-MTU_MISMATCH |
4-Warning |
WARNING: With IP multicast enabled interfaces which transmit traffic from larger to smaller MTU interfaces may not be hardware switched due to fragmentation. A degradation in performance may occur. |
WARNING: With IP multicast enabled interfaces which transmit traffic\n\ from larger to smaller MTU interfaces may not be hardware switched due\n\ to fragmentation. A degradation in performance may occur. |
- |
"Set MTU values on all interfaces to be identical. " |
|
MROUTE-4-RADIXDELETE |
4-Warning |
Error trying to delete multicast route entry [inet]/[dec] for [inet] expected [hex] got [hex] |
An error in the multicast routing table occurred. A route could not be\n\ deleted from the routing table. |
- |
"Execute a clear ip mroute command. Determine whether the router is low\n\ on memory. " LOG_STD_RECUR_ACTION |
|
MROUTE-4-RADIXINSERT |
4-Warning |
Error trying to add multicast route entry [inet]/[dec] for [inet] expected [hex] got [hex] |
An error in the multicast routing table occurred. A route could not be\n\ inserted in to the routing table. |
- |
"Execute a clear ip mroute command. Determine whether the router is low\n\ on memory. " LOG_STD_RECUR_ACTION |
|
MROUTE-4-REGISTER_SOURCE_CONFIG |
4-Warning |
Removing pim register source configuration for [chars] |
The register source interface was deleted had its IP address removed or its vrf forwarding changed. |
- |
"No action required just check 'ip pim register-source' configuration." LOG_STD_ACTION |
|
MROUTE-4-ROUTELIMIT |
4-Warning |
Current count of [dec] exceeds multicast route-limit of [dec] |
The number of multicast routes equals the configured maximum allowed.\n\ New routes cannot be added unless the configuration is changed. |
- |
"If multicast traffic is of any priority among the traffic carried\n\ by this router then use the 'ip multicast route-limit' command to\n\ increase the number of multicast routes.\n\ Otherwise no action is required." |
|
MROUTE-4-ROUTELIMIT_ATTEMPT |
4-Warning |
Attempt to exceed multicast route-limit of [dec] |
The number of multicast routes equals the configured maximum allowed.\n\ New routes cannot be added unless the configuration is changed. |
- |
"If multicast traffic is of any priority among the traffic carried\n\ by this router then use the 'ip multicast route-limit' command to\n\ increase the number of multicast routes.\n\ Otherwise no action is required." |
|
MROUTE-4-ROUTELIMITWARNING |
4-Warning |
multicast route-limit warning curr [dec] threshold [dec] |
- |
- |
- |
|
MROUTE-4-SNMP_RADIX_ERR |
4-Warning |
Failed to [chars] snmp node [chars] snmp radix tree for multicast group * [inet]. |
An error occured while adding or deleting snmp node in snmp \n\ radix tree when mroute is created or deleted. |
- |
"An error in adding or deleting snmp node in snmp radix tree \n\ occurred." LOG_STD_ACTION |
|
MROUTE-6-LARGE_TWHEEL_DELAY |
6-Information |
Exceeded maximum delay [dec] ms requested: [dec] |
Because of the way the timer wheel works there is a maximum delay defined. If we try to schedule a function with a higher delay we still schedule it using the maximum delay possible minus a small delay offset. |
- |
"A timer with large delay was requested. Check if a large igmp query-interval" " is set. Some timers may refresh periodically to allow for the large delay.\n\" LOG_STD_NO_ACTION |
|
MROUTE-6-MVRF_NOTEXISTS |
6-Information |
MRT[dec] MVRF does not exist |
- |
- |
- |
|
MRP-2-RINGFAULT |
2-Critical |
Ring [dec]: The MRP ring is now in FAULT state |
The MRP ring is in FAULT state. This typically happens if a link or node in the ring goes down. |
accsw-layer2 |
"Determine the location of the fault and restore " "connectivity. The ring should resume functioning " "automatically" |
|
MRP-3-RINGERROR |
3-Error |
Miscabling detected Port [chars] does not belong to the MRP ring [dec]. |
The MRP ring is in FAULT state. This happens when a cable is wrongly connected on another ring |
petra-mrp |
"Check the wiring and re-connect the cables again. " "Enable recovery of the err-disabled port using" "'errdisable recovery cause mrp-miscabling'." |
|
MRP-6-MODE_MANAGER_DEPRECATED |
6-Information |
MRP \mode manager\ is deprecated executing \mode auto-manager\ instead. |
MRP mode manager is no longer supported and is replaced by mode auto-manager. |
accsw-layer2 |
"This is an informational message. The device is " "functioning as expected." |
|
MRP-6-RINGNORMAL |
6-Information |
Ring [dec]: The MRP ring is now in NORMAL state [chars] is Blocked |
The state of the MRP ring has changed to NORMAL. |
accsw-layer2 |
"This is an informational message. The device is " "functioning as expected." |
|
MRP-6-RINGNORMAL_RECEIVED |
6-Information |
Ring [dec]: The MRP ring is now in NORMAL state |
The state of the MRP ring has changed to NORMAL. |
accsw-layer2 |
"This is an informational message. The device is " "functioning as expected." |
|
MSDP-4-PKT_TOO_BIG |
4-Warning |
Message size violation on [dec]-byte packet from [inet] discarded |
A message larger than the maximum MSDP message size was received. \n\ There is also a possibilty that this is an internal error. |
- |
"show version" |
|
MSDP-4-SA_LIMIT |
4-Warning |
SA from peer [inet] RP [inet] for [inet] [inet] exceeded sa-limit of [dec] |
- |
- |
- |
|
MSDP-5-PEER_IS_SELF |
5-Notice |
Peering with self [inet] |
- |
- |
- |
|
MSDP-5-PEER_UPDOWN |
5-Notice |
Session to peer [inet] going [chars] |
Session to peer going up or down |
- |
"Determine whether the router is low on memory." |
|
msg_ACCESS_SESSION-3-TRACE_INIT_FAIL |
3-Error |
Initialization failed with code: [dec] |
Failed to initialize access-session trace. |
dot1x-ios |
LOG_STD_NO_ACTION |
|
msg_ACCESS_SESSION-3-TRACE_REG_FAIL |
3-Error |
Component [chars] registration failed. Error code: [dec] |
Component failed to register with access-session trace |
dot1x-ios |
LOG_STD_NO_ACTION |
|
MSG_FIFO-2-MSG_FIFO_CREATE |
2-Critical |
[chars]: Bad parameter to message fifo creaate [chars] = 0x%08x |
Failed to create message fifo invalid memory size or other parameter. |
cpp-ucode |
LOG_STD_ACTION |
|
MSG_MGR_INIT_FAILED-3-MPLS_TE_HA |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
MSG_POS_OC3_OC12_SPA-3-RESOURCE_ERROR |
3-Error |
[chars] 0x[hec] 0x[hec] 0x[hec] [chars] |
Tranceiver analyze failed |
gsr-oc3_12-pos-spa |
"Remove the tranceiver module and insert a valid module " "with rate that is supported on the SPA." |
|
MSP_ISSU-2-GET_BUFFER |
2-Critical |
MSP ISSU client failed to get buffer for message. Error: [dec] [chars] |
The MSP 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. |
msi-proxy |
"show logging and show checkpoint client" |
|
MSP_ISSU-2-INIT |
2-Critical |
MSP ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The MSP 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. |
msi-proxy |
LOG_STD_ACTION |
|
MSP_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
MSP ISSU client failed to send negotiation message. Error: [dec] [chars] |
The MSP 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. |
msi-proxy |
"show logging and show checkpoint client" |
|
MSP_ISSU-2-SESSION_NEGO |
2-Critical |
MSP ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The MSP 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. |
msi-proxy |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MSP_ISSU-2-SESSION_REGISTRY |
2-Critical |
MSP ISSU client failed to register session information. Error: [dec] [chars] |
The MSP ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
msi-proxy |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MSP_ISSU-3-CAP_INVALID_SIZE |
3-Error |
MSP ISSU client capability list is empty. |
The MSP ISSU client capability exchange list size is invalid. |
msi-proxy |
"show issu capability entires <Client_ID>" |
|
MSP_ISSU-3-CAP_NOT_COMPATIBLE |
3-Error |
MSP ISSU client capability exchange result incompatible. |
The MSP ISSU client capability exchange have negotiated as incompatible with the peer. |
msi-proxy |
"show issu negotiated capability <Session_ID>" |
|
MSP_ISSU-3-INVALID_SESSION |
3-Error |
MSP ISSU client does not have a valid registered session. |
The MSP ISSU client does not have a valid registered session. |
msi-proxy |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MSP_ISSU-3-MSG_NOT_COMPATIBLE_WITH_PEER |
3-Error |
'Message Type [dec]' is not supported by MSP ISSU client at peer |
The MSP ISSU client at the peer supervisor is not compatible for this message type. The MSP client will be marked as incompatible with the peer. |
msi-proxy |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
MSP_ISSU-3-MSG_NOT_OK |
3-Error |
MSP ISSU client 'Message Type [dec]' is not compatible |
The MSP ISSU client received an incompatible message from the peer device. The message cannot be processed. |
msi-proxy |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
MSP_ISSU-3-MSG_SIZE |
3-Error |
MSP ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The MSP ISSU client failed to calculate the MTU for the specified message. The MSP ISSU client is not able to send the message to the standby device. |
msi-proxy |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
MSP_ISSU-3-SESSION_UNREGISTRY |
3-Error |
MSP ISSU client failed to unregister session information. Error: [dec] [chars] |
The MSP ISSU client failed to unregister session information. |
msi-proxy |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MSP_ISSU-3-TRANSFORM_FAIL |
3-Error |
MSP ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The MSP 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 MSP state between the active device and the standby device is not identical. |
msi-proxy |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
MSPI-1-MSPI_BAD_CONFIG |
1-Alert |
MSPI-bad configuration [chars] |
A configuration error was detected. |
- |
"Add or fix the Dial Peer configuration" |
|
MSPI-1-NOMEMORY |
1-Alert |
msgtxt_nomemory |
The requested operation could not be accomplished because of a low\n\ memory condition. |
- |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
MSPI-2-MSPI_BAD_CONTEXT |
2-Critical |
MSPI-bad context pointer [chars] |
A bad context pointer was passed. |
- |
LOG_STD_RECUR_ACTION |
|
MSPI-2-MSPI_INTERNAL_ERROR |
2-Critical |
MSPI-Internal software error cid=[dec] [chars] |
An internal software error occurred. This would happen when the IOS software runs into any null pointer invalid state or event or other failed operation |
- |
LOG_STD_RECUR_ACTION |
|
MSPI-4-MSPI_BAD_MESSAGE |
4-Warning |
MSPI- Bad message received: [chars] |
An unexpected message was received. |
- |
LOG_STD_RECUR_ACTION |
|
MSPI-4-MSPI_NO_SMTP |
4-Warning |
MSPI- Can't connect to the SMTP server cid=[dec] [chars] |
No connection was created to the specified SMTP server. |
- |
"Please use the following commands to collect the information: show call active " "voice show call active fax show call history voice show call history fax " "debug mspi send debug mspi receive or debug fax mspi all" |
|
MSPI-4-MSPI_NO_SMTP_SEND |
4-Warning |
MSPI- Could not\n\send data to the SMTP server cid=[dec] [chars] |
A connection was made to the SMTP server but no data can be sent. |
- |
"Please use the following commands to collect the information on why no data " "can be sent: show call active voice show call active fax show call history " "voice show call history fax debug mta send all debug mta receive all or " "debug fax mta all" |
|
MSPI-4-SMTP_NOT_CONNECTED |
4-Warning |
SMTP- failed [chars] [dec] |
A connection attempt to a remote mail server was not successful.\n\ This unexpected behavior. |
- |
LOG_STD_NO_ACTION |
|
MSPI-6-SMTP_OPEN |
6-Information |
SMTP- opening [chars] [dec] |
A connection attempt ... |
- |
LOG_STD_NO_ACTION |
|
MSRPC_ALG-3-CHUNK_CREATE_FAIL |
3-Error |
- |
Chunk create failed. MS RPC ALG will not be able to finish initialization. |
cpp-ucode |
LOG_STD_ACTION |
|
MSRPC_ALG-3-L7_DATA_CREATE_ERROR |
3-Error |
- |
Error during L7 data creation. |
cpp-ucode |
LOG_STD_ACTION |
|
MTRIE-4-MTRIECORRUPTLEAF |
4-Warning |
[inet]/[dec] - [chars] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
MTRIE-4-MTRIELEAFOPFAIL |
4-Warning |
[inet]/[dec] - [chars] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
MTRIE-4-MTRIEMISALIGNEDNODEPTR |
4-Warning |
0x[hec] - [chars] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
MTRIE-4-PLACEALLOC |
4-Warning |
Failed to allocate place holder |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
MTS_BIND-3-L2VPN |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
MTS_DROP-3-L2VPN |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
MTS_DROP-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
MTS_Q-3-L2VPN |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
MTS_RECV-3-L2VPN |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
MTS_RECV-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
MTS_REG-3-L2VPN |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
MTS_SEND-3-L2VPN |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
MTS_UNKNOWN_MSG-6-LDP |
6-Information |
ERRMSG_NOFLAGS |
- |
- |
- |
|
MUESLIX-1-CLOCKRATE |
1-Alert |
[chars]:Link is brought [chars] due to clock rate change threshold configured = [dec] received clock rate = [dec] |
The received clock rate is changed from below the threshold\n\ configured to above or vice versa.. |
pas-serial |
"Check the received clock rate from the provider end if the clock rate falls below the threshold configured" |
|
MUESLIX-1-DWNLDFL |
1-Alert |
Mueslix microcode down load failed. |
The Mueslix serial hardware failed. Hardware could not download \n\ microcode into mueslix chip. |
mid-serial |
LOG_STD_ACTION |
|
MUESLIX-1-DWNLDFL |
1-Alert |
Mx serial bay [dec]: PA down load failed |
The Mx serial hardware failed. It could not download its \n\ operational microcode. |
pas-serial |
"Try to reseat the PA properly in the system slots. If the error\n\ still happens then verify for the hardware failure including \n\ the 7200 chasis in case of 7200 or vip in case of RSP and the PA \n\ as this error will come only if there is a failure in hardware." |
|
MUESLIX-1-FAILURE_CAUSE |
1-Alert |
[chars]: [chars][chars]: 0x%08x 0x%08x |
Pull the info from the port adaptor to show what error caused\n\ the STOPFAIL/STARTFAIL problem. |
pas-serial |
"Enable 'debug serial mueslix' debug command. Then collect the \n\ 'show tech' and 'show log' information and send them \n\ to the technical support representative. After that you can \n\ disable the 'debug serial mueslix' command." |
|
MUESLIX-1-HALT |
1-Alert |
Mx serial: [chars] TPU halted: cause 0x%2x status 0x%08x shadow 0x%08x |
The Mx serial firmware is not in sync with the driver. |
pas-serial |
"This conditions will clear by itself. Enable 'debug serial mueslix' \n\ debug command. Then collect the 'show tech' and 'show log' \n\ information and send them to the DE team or CSE team. After \n\ that you can disable the 'debug serial mueslix' command." |
|
MUESLIX-1-INITFAIL |
1-Alert |
MUESLIX slot [dec]: Init Failed at [chars] |
The Mueslix serial board failed to complete hardware \n\ initialization. |
mid-serial |
LOG_STD_ACTION |
|
MUESLIX-1-INITFAIL |
1-Alert |
Mx serial bay [dec] Init Failed at [chars] |
The Mx serial port adaptor failed to complete hardware \n\ initialization. |
pas-serial |
"Try to reseat the PA properly in the system slots. If the error\n\ still happens then verify for the hardware failure including \n\ the 7200 chasis in case of 7200 or vip in case of 7500 and the PA \n\ as this error will come only if there is a failure in hardware." |
|
MUESLIX-1-STARTFAIL |
1-Alert |
[chars]: Start Failed at [chars] |
The Mueslix serial interface is not responding to commands used to \n\ initialize it. |
mid-serial |
LOG_STD_ACTION |
|
MUESLIX-1-STARTFAIL |
1-Alert |
Mx serial [chars] Start Failed at [chars] |
A software or hardware error occurred. The Mx microcode is not\n\ responding to the enable command used to restart the serial interface |
pas-serial |
"Enable 'debug serial mueslix' debug command. Then collect the \n\ 'show tech' and 'show log' information and send them \n\ to the DE team or CSE team. After that you can disable the \n\ 'debug serial mueslix' command." |
|
MUESLIX-1-STOPFAIL |
1-Alert |
[chars]: Stop Failed at [chars] |
The Mueslix serial board failed to respond to a request to \n\ disable an interface. |
mid-serial |
LOG_STD_ACTION |
|
MUESLIX-1-STOPFAIL |
1-Alert |
Mx serial [chars] Stop Failed at [chars] |
A software or hardware error occurred. The Mx microcode is not\n\ responding to the disable command used to stop the serial port. |
pas-serial |
"Enable 'debug serial mueslix' debug command. Then collect the \n\ 'show tech' and 'show log' information and send them \n\ to the technical support representative. After that you can \n\ disable the 'debug serial mueslix' command." |
|
MUESLIX-3-DISCOVER |
3-Error |
Mx serial bay [dec]: Interface found: [dec] |
The system couldn't able to recognize all the Mueslix devices\n\ that are there on the system |
pas-serial |
"Try to reseat the PA properly in the system slots. If the error\n\ is still happening then verify for the hardware failure including \n\ the 7200 chasis in case of 7200 or vip in case of RSP and the PA \n\ as this error will come only if there is a failure in hardware." |
|
MUESLIX-3-ERROR |
3-Error |
[chars] |
General error information. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
MUESLIX-3-NOTMUESLIX |
3-Error |
Mx serial bay [dec]: Device reported [hex] |
The system hardware failed. A non-Mx serial device pointed at the\n\ Mx serial software. |
pas-serial |
"Check the system configuration for the failure in the bay number \n\ that is reported in the error message. If it is not a mueslix \n\ based PA then contact the appropriate component to which that PA \n\ belongs. If it is a mueslix based PA then try to reseat the PA \n\ once agian and if the error still comes then collect the 'show tech' \n\ and 'show log' information at the time of this problem and send it\n\ to the technical support representative" |
|
MUESLIX-3-OWNERR |
3-Error |
Unit [dec] buffer ownership error pak = 0x[hec] |
The Mueslix serial driver detected that the transmit ring is in an \n\ inconsistent state. |
mid-serial |
LOG_STD_ACTION |
|
MUESLIX-3-OWNERR |
3-Error |
[dec] packet buffer pak=0x[hec] |
A software or hardware error occurred. The Mx serial driver detected\n\ that the transmit ring is in an inconsistent and unrecoverable state. |
pas-serial |
"Enable 'debug serial mueslix' debug command. Then collect the \n\ 'show tech' and 'show log' information and send them \n\ to the DE team or CSE team. After that you can disable the \n\ 'debug serial mueslix' command." |
|
MUESLIX-4-DEF_SUBRATE |
4-Warning |
[chars] [chars] |
User has changed the dsu bandwidth using DS3 remote\n\ management commands. This won't change the user configured dsu bandwidth |
pas-serial |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
MVR_ISSU-2-GET_BUFFER |
2-Critical |
MVR ISSU client failed to get buffer for message. Error: [dec] [chars] |
The MVR 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. |
mvr |
"show logging and show checkpoint client" |
|
MVR_ISSU-2-GET_BUFFER |
2-Critical |
MVR ISSU client failed to get buffer for message. Error: [dec] [chars] |
The MVR 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. |
mvr |
"show logging and show checkpoint client" |
|
MVR_ISSU-2-INIT |
2-Critical |
MVR ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The MVR 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. |
mvr |
LOG_STD_ACTION |
|
MVR_ISSU-2-INIT |
2-Critical |
MVR ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The MVR 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. |
mvr |
LOG_STD_ACTION |
|
MVR_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
MVR ISSU client failed to send negotiation message. Error: [dec] [chars] |
The MVR 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. |
mvr |
"show logging and show checkpoint client" |
|
MVR_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
MVR ISSU client failed to send negotiation message. Error: [dec] [chars] |
The MVR 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. |
mvr |
"show logging and show checkpoint client" |
|
MVR_ISSU-2-SESSION_NEGO |
2-Critical |
MVR ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The MVR 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. |
mvr |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MVR_ISSU-2-SESSION_NEGO |
2-Critical |
MVR ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The MVR 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. |
mvr |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MVR_ISSU-2-SESSION_REGISTRY |
2-Critical |
MVR ISSU client failed to register session information. Error: [dec] [chars] |
The MVR ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
mvr |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MVR_ISSU-2-SESSION_REGISTRY |
2-Critical |
MVR ISSU client failed to register session information. Error: [dec] [chars] |
The MVR ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
mvr |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MVR_ISSU-3-INVALID_SESSION |
3-Error |
MVR ISSU client does not have a valid registered session. |
The MVR ISSU client does not have a valid registered session. |
mvr |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MVR_ISSU-3-INVALID_SESSION |
3-Error |
MVR ISSU client does not have a valid registered session. |
The MVR ISSU client does not have a valid registered session. |
mvr |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MVR_ISSU-3-MSG_NOT_OK |
3-Error |
MVR ISSU client 'Message Type [dec]' is not compatible |
The MVR ISSU client received an incompatible message from the peer device. The message cannot be processed. |
mvr |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
MVR_ISSU-3-MSG_NOT_OK |
3-Error |
MVR ISSU client 'Message Type [dec]' is not compatible |
The MVR ISSU client received an incompatible message from the peer device. The message cannot be processed. |
mvr |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
MVR_ISSU-3-MSG_SIZE |
3-Error |
MVR ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The MVR ISSU client failed to calculate the MTU for the specified message. The MVR ISSU client is not able to send the message to the standby device. |
mvr |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
MVR_ISSU-3-MSG_SIZE |
3-Error |
MVR ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The MVR ISSU client failed to calculate the MTU for the specified message. The MVR ISSU client is not able to send the message to the standby device. |
mvr |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
MVR_ISSU-3-SESSION_UNREGISTRY |
3-Error |
MVR ISSU client failed to unregister session information. Error: [dec] [chars] |
The MVR ISSU client failed to unregister session information. |
mvr |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MVR_ISSU-3-SESSION_UNREGISTRY |
3-Error |
MVR ISSU client failed to unregister session information. Error: [dec] [chars] |
The MVR ISSU client failed to unregister session information. |
mvr |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MVR_ISSU-3-TRANSFORM_FAIL |
3-Error |
MVR ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The MVR 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 MVR state between the active device and the standby device is not identical. |
mvr |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
MVR_ISSU-3-TRANSFORM_FAIL |
3-Error |
MVR ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The MVR 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 MVR state between the active device and the standby device is not identical. |
mvr |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
MVRP_CONST-3-MAC_MATCH_REG_FAILED |
3-Error |
Unable to reserve needed MAC match register - cannot run MVRP on interfaces of slot [dec] [chars] |
MVRP attempted to reserve a MAC match register for the slot indicated and there is no dedicated register or programmable register available. MVRP cannot be activated on interfaced of this card. |
mvrp |
"Either conflicting protocols that use the MAC " "match register must be disabled or a different " "card type that supports MVRP must be used." |
|
MVRP_CONST-6-FEATURE_CONFLICT |
6-Information |
Failed to enable MVRP on [chars] because conflicting feature [chars] is enabled on the interface |
MVRP failed to be enabled on the given interface because of conflicting features. For instance unknown unicast flooding blockingUUFB and MVRP |
mvrp |
LOG_STD_NO_ACTION |
|
MVRP_CONST-6-MAC_LEARNING |
6-Information |
MAC learning on VLAN [chars] is [chars] |
MVRP detects network topology change dynamically. If only two MVRP ports are forwarding and not pruned in a VLAN MVRP will disable MAC learning on that VLAN so as to save room in the MAC table which is limited and system-wide resource. This is an informative message. No action needs to be taken. |
mvrp |
LOG_STD_NO_ACTION |
|
MVRP_CONST-6-MAC_LRN_SETTING_FAILED |
6-Information |
Failed to [chars] MAC learning on VLAN [chars] |
MVRP failed to enable or disable MAC learning on the given VLANs. This is probably due to the fact that MAC learning had already been configured by administrator. Use <CmdBold>show mac-address-table learning<NoCmdBold> to check. |
mvrp |
LOG_STD_NO_ACTION |
|
MVRP_ISSU-2-GET_BUFFER |
2-Critical |
MVRP ISSU client failed to get buffer for message. Error: [dec] [chars] |
The MVRP 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. |
mvrp |
"show logging and show checkpoint client" |
|
MVRP_ISSU-2-INIT |
2-Critical |
MVRP ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The MVRP 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. |
mvrp |
LOG_STD_ACTION |
|
MVRP_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
MVRP ISSU client failed to send negotiation message. Error: [dec] [chars] |
The MVRP 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. |
mvrp |
"show logging and show checkpoint client" |
|
MVRP_ISSU-2-SESSION_NEGO |
2-Critical |
MVRP ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The MVRP 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. |
mvrp |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MVRP_ISSU-2-SESSION_REGISTRY |
2-Critical |
MVRP ISSU client failed to register session information. Error: [dec] [chars] |
The MVRP ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
mvrp |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MVRP_ISSU-3-INVALID_SESSION |
3-Error |
MVRP ISSU client does not have a valid registered session. |
The MVRP ISSU client does not have a valid registered session. |
mvrp |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MVRP_ISSU-3-MSG_NOT_OK |
3-Error |
MVRP ISSU client 'Message Type [dec]' is not compatible |
The MVRP ISSU client received an incompatible message from the peer device. The message cannot be processed. |
mvrp |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
MVRP_ISSU-3-MSG_SIZE |
3-Error |
MVRP ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The MVRP ISSU client failed to calculate the MTU for the specified message. The MVRP ISSU client is not able to send the message to the standby device. |
mvrp |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
MVRP_ISSU-3-SESSION_UNREGISTRY |
3-Error |
MVRP ISSU client failed to unregister session information. Error: [dec] [chars] |
The MVRP ISSU client failed to unregister session information. |
mvrp |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
MVRP_ISSU-3-TRANSFORM_FAIL |
3-Error |
MVRP ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The MVRP 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 MVRP state between the active device and the standby device is not identical. |
mvrp |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
MVRP-3-ADD_REGISTRY_FAILED |
3-Error |
MVRP subsystem fails to add callback function [chars] |
Other subsystem must have mistakenly add its own callback functions. This syslog is for debugging purpose. |
mvrp |
LOG_STD_NO_ACTION |
|
MVRP-3-ENABLE_FAILED |
3-Error |
MVRP can't be enabled because [chars] |
MVRP can't be enabled for some reason. |
mvrp |
"Action may be taken according to the given " "reason. If for instance the problem is " "due to lack of memory the user should " "add more memory to his system." |
|
MVRP-3-HA_INIT_FAILED |
3-Error |
MVRP High Availability subsystem fails to be initialized and hence MVRP won't support HA stateful switchover. |
Either MVRP CF client or MVRP RF client fails to be initialized. |
mvrp |
"Enter the " "<CmdBold>show redundancy clients<NoCmdBold> " "and <CmdBold>show checkpoint clients<NoCmdBold> to " "find out which client is not initialized." |
|
MVRP-3-SUBSYS_INIT_FAILED |
3-Error |
MVRP subsystem failed in initialization[chars] and MVRP won't |
This is extremely unlikely to occur on a customer device. If it does occur the cause is most likely due to the lack of memory so the software failed to create data structures. User should see many |
mvrp |
"Most likely the system has crashed by then " "if the problem is due to lack of memory. " "If the system miraculously came up then" "user can run <CmdBold>show memory summary" "<NoCmdBold> to check the memory usage. " "Please contact the TAC with the output of " "<CmdBold>show memory summary<NoCmdBold> " "<CmdBold>show version<NoCmdBold> and " "<CmdBold>show run<NoCmdBold> and the " "associated syslog messages from the time " "of the problem." |
|
MVRP-6-MODECHANGE |
6-Information |
The operating mode is changed to [chars] mode on interface [chars]. |
As a result of protocol negotiation the operating mode changed to the specified mode on the specified interface. |
mvrp |
LOG_STD_NO_ACTION |
|
MX-3-BADFEAT |
3-Error |
[chars]: [dec] |
Software detected the use of an invalid feature enumeration which may be the result of incompatible software versions on different system components. |
cpp-ucode |
LOG_STD_ACTION |
|
MX-3-BADMAGIC |
3-Error |
[chars]: %04x in [hec] |
A data structure inconsistency was detected in a buffer header perhaps as the result of memory corruption. A buffer has been dropped because of this resulting in a memory leak and potential system unreliability. |
cpp-ucode |
"Please report the problem Cisco technical support along with the " "text of the error message. " "If the system becomes unstable restarting or reloading the affected " "component should correct the instability." |
|
MX-3-BADPOOL |
3-Error |
[chars]: [dec] |
Software detected the use of an invalid pool index which may be the result of incompatible software versions on different system components. |
cpp-ucode |
LOG_STD_ACTION |
|
MX-3-BADSTART |
3-Error |
[chars]: [hec] current [hec] size [dec] |
A software error was detected during an attempt to increase the size of an external memory region. |
cpp-ucode |
LOG_STD_ACTION |
|
MX-3-CARVE |
3-Error |
[chars]: size [dec] too small |
A software error resulted in an attempt to create buffers in an area of memory that was too small. |
cpp-ucode |
LOG_STD_ACTION |
|
MX-3-INITBUFHDR |
3-Error |
[chars]: mgmt memory allocation failure size [dec] |
insufficient mgmt memory provided for initialization of the external memory manager which will cause features that manage packets in multiple pieces or that directly export data not to work properly. |
cpp-ucode |
LOG_STD_ACTION |
|
MX-3-MAXPOOLS |
3-Error |
too low |
A source code inconsistency was detected. |
cpp-ucode |
"Increase the number of pools allowed." |
|
MX-3-RESIZE |
3-Error |
[chars]: non-contiguous resize: orig [hec]/[hec] new [hec]/[hec] |
A software error was detected during a resize operation on the specified memory region. |
cpp-ucode |
LOG_STD_ACTION |
|
MX-3-SUBRGNINDX |
3-Error |
[chars]: Subregion Index allocation failure |
Unable to obtain a sub region index so unable add sw managed memory |
cpp-ucode |
LOG_STD_ACTION |
|
MX-6-NOBUFHDR |
6-Information |
[chars] |
An attempt to add buffers within a memory region failed. |
cpp-ucode |
LOG_STD_ACTION |
|
MX-6-NOMEM |
6-Information |
[chars] bufhdr allocation failure |
An attempt to allocate memory failed. This could cause features that manage packets in multiple pieces or that directly export data not to work properly in some cases. |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-ALLOC_FAIL |
3-Error |
data 0x[hec] |
A request exceeded for memory allocation failed |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-CHUNK_ID_MISMATCH |
3-Error |
id %p not found |
The chunk ID provided by the client doesn't match any of the available chunk IDs. Hence a valid chunk could not be found for the given chunk ID. |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-DP_REL_FAIL |
3-Error |
DP REL FAIL retry count [dec] exceeded max |
The dp release fail due to too many retry on freeing session chunk |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-DYN_MAP_ADD_FAIL |
3-Error |
[chars] |
The add of a dynamic mapping failed. This will generally mean that the IOS configuration is now out of sync with the data plane. The mapping should be removed and then re-added to try to get things back in sync. |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-DYN_PAT_MAP_UPD_OR_ADD_FAIL |
3-Error |
rc [dec] |
The add or update of a dynamic pat mapping failed with the assoicated return code. This will generally mean that the IOS configuration is now out of sync with the data plane. The mapping should be removed from the configuration to try to get things back in sync. |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-EMPTY_CHUNK |
3-Error |
id %p |
The memory provided by the client to the datapath initilization is NULL |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-HA_BULK_SYNC_FAIL |
3-Error |
flags 0x[hec] rg [dec] |
There was a failure such that NAT Bulk Sync did not occur |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-HA_COULD_NOT_ALLOC_ADDR |
3-Error |
addr %Ci port [hec] |
The standby NAT could not allocate the address requested by the active |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-HA_COULD_NOT_CREATE_BIND |
3-Error |
idomain [dec] orig adr [hec] port [hec] trans adr [hec] port [hec] vrf [hec] prot [hec] rg [dec] |
Standby could not create the bind indicated by the HA message |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-HA_COULD_NOT_CREATE_SESS |
3-Error |
in_orig adr [hec] port [hec] out_trans adr [hec] port [hec] vrf [hec] prot [hec] cook %llu rg [dec] |
Standby could not create the session indicated by the HA message |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-HA_COULD_NOT_FIND_POOL |
3-Error |
pool_id [dec] |
The standby NAT could find the pool indicated by the active |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-HA_COULD_NOT_FIND_SESS |
3-Error |
in_orig adr [hec] port [hec] out_trans adr [hec] port [hec] vrf [hec] prot [hec] cook [hec] [hec] |
Standby could not find the matching session indicated by the HA message |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-HA_COULD_NOT_LOCK_PARENT |
3-Error |
in_orig adr [hec] port [hec] out_trans adr [hec] port [hec] vrf [hec] prot [hec] cook %llu |
- |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-HA_INVALID_MSG_RCVD |
3-Error |
invalid value [dec] opcode 0x[hec] version 0x[hec] |
Standby received an invalid NAT HA message |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-HA_INVALID_STATE |
3-Error |
state [dec] |
An invalid HA state was received from the HA infrastructure. |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-HA_NO_BUF |
3-Error |
- |
There was not enough memory to send the HA record |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-HA_STANDBY_CLR_DB_FAILED |
3-Error |
rc=[dec] |
Standby failed trying to clear databased with indicated return code |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-HSL_ALLOC_FAIL |
3-Error |
[chars] |
High Speed logging memory allocation failed. When this happens the event\n will not be exported to the collector. This indicates a temporary \n condition when the system runs low on memory. The failure does not have \n any effects on the operation of NAT \n |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-MAPPING_REFCNT_FAIL |
3-Error |
refcount [dec] |
The mapping reference count is below zero. This indicates that the reference count incrementing and decrementing operations are out of sync |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-PER_VFR_HSL_ADD_FAILED |
3-Error |
- |
The attempt to turn on NAT HSL for a vrfid [dec] failed. Please remove configuration and try again.\n |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-POOL_ADD_FAIL |
3-Error |
pool-id [dec] rc [dec] |
A request from the active to process a clear translation failed.\n Please retry.\n |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-RMAP_OP_FAIL |
3-Error |
Routemap hash table not set up attempted [chars] |
- |
- |
- |
|
NAT-3-SHOW_LIMIT_FAIL |
3-Error |
unable to show [dec] entries from bucket [dec] |
This is an information message which occurs when NAT is unable to show all address binds due to an internal error. Please try operation again. |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-SHOW_TRANS_FAIL |
3-Error |
unable to show [dec] entries from bucket [dec] |
Unable to show some entries from session database. If using verbose try using non-verbose. Otherwise situation is likely to be temporary. Or it may be wise to do 'clear ip nat trans *' as a very odd session distribution has occurred.\n |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-STATIC_MAP_ADD_FAIL |
3-Error |
local addr %Ci global addr %Ci [chars] |
This is an information message which occurs when NAT is configured and a frame is dropped due to the default maximum entries limit. Starting with release 5 XNE NAT will use a default max-entries in the data plane based on the ESP type. This will not show in the configuration and is overriden by any user configuration of 'ip nat trans max-entries <value>'. The purpose of the default data plane limit is to protect the box from memory exhaustion which could occur if no limit is enforced. |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-3-STATIC_MAP_ADD_FAILED |
3-Error |
local addr %Ci global addr %Ci [chars] %Ci %Ci |
- |
- |
- |
|
NAT-4-ALL_HOST_MAX_ENTRIES |
4-Warning |
all-host maximum limit of [dec] reached for [chars]. |
This message indicates that maximum limit for all-host entries was reached. |
cpp-ucode |
- |
|
NAT-4-ALL_VRF_MAX_ENTRIES |
4-Warning |
all-vrf maximum limit of [dec] reached for [dec]. |
This message indicates that maximum limit for all-vrf entries was reached. |
cpp-ucode |
- |
|
NAT-4-FORCED_DEL_BIND_FAILED |
4-Warning |
Unable to find bind to forcibly delete |
This is an information message which occurs when NAT is unable to find a bind even though IOS thinks the bind exists. Please try other methods of clearing transaction. |
cpp-ucode |
- |
|
NAT-4-HA_INVALID_MSGVER_RCVD |
4-Warning |
invalid version [dec] |
Standby received an invalid NAT HA message |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-4-PER_HOST_MAX_ENTRIES |
4-Warning |
per-host maximum limit of [dec] reached for [chars]. |
This message indicates that maximum limit for per-host entries was reached. |
cpp-ucode |
- |
|
NAT-4-PER_VRF_MAX_ENTRIES |
4-Warning |
per-vrf maximum limit of [dec] reached for [dec]. |
This message indicates that an address could not be allocated from a pool because there were no free addresses in the pool at that time. |
cpp-ucode |
- |
|
NAT-4-SEQ_DELTA_LIST_CORRUPT |
4-Warning |
Sequence Delta list tail pointer null in error |
For unknown reasons sequence delta list tail pointer is null |
cpp-ucode |
LOG_STD_ACTION |
|
NAT64-3-API_FAILED |
3-Error |
NULL |
A call to the API of another component has indicated an\n\ error. |
nat64 |
LOG_STD_ACTION |
|
NAT64-3-BAD_MAGIC |
3-Error |
Invalid magic number%#10x |
An internal data structure is corrupt. |
nat64 |
LOG_STD_ACTION |
|
NAT64-3-CHUNK_ID_MISMATCH |
3-Error |
id [dec] not found |
The chunk ID provided by the client doesn't match any of the available chunk IDs. Hence a valid chunk could not be found for the given chunk ID. |
cpp-ucode |
LOG_STD_ACTION |
|
NAT64-3-CLEAR_FAIL_TRANS_IN_USE |
3-Error |
- |
The requested clear failed because the transaction was in use.\n Some clear commands support a 'forced' keyword which allows you \n to override this.\n |
cpp-ucode |
LOG_STD_ACTION |
|
NAT64-3-EEXIST |
3-Error |
NULL |
An item unexpectedly exists already. |
nat64 |
LOG_STD_ACTION |
|
NAT64-3-EINVAL |
3-Error |
NULL |
An unexpected input value to a function was incorrect |
nat64 |
LOG_STD_ACTION |
|
NAT64-3-EMPTY_CHUNK |
3-Error |
id [dec] |
The memory provided by the client to the datapath initilization is NULL |
cpp-ucode |
LOG_STD_ACTION |
|
NAT64-3-ENOENT |
3-Error |
NULL |
A lookup failed unexpectedly. |
nat64 |
LOG_STD_ACTION |
|
NAT64-3-ENOMEM |
3-Error |
Memory allocation failed |
A attempt to allocae memory has failed. |
nat64 |
LOG_STD_ACTION |
|
NAT64-3-HA_BULK_SYNC_FAIL |
3-Error |
flags 0x[hec] rg [dec] |
There was a failure such that NAT64 Bulk Sync did not occur |
cpp-ucode |
LOG_STD_ACTION |
|
NAT64-3-HA_INVALID_MSG_RCVD |
3-Error |
invalid value [dec] opcode 0x[hec] version 0x[hec] |
Standby received an invalid NAT64 HA message |
cpp-ucode |
LOG_STD_ACTION |
|
NAT64-3-HA_INVALID_STATE |
3-Error |
state [dec] |
An invalid HA state was received from the HA infrastructure. |
cpp-ucode |
LOG_STD_ACTION |
|
NAT64-3-INIT_FAILED |
3-Error |
An initialization failed rc[chars] |
- |
- |
- |
|
NAT64-3-NAT64_MAPPING_REFCNT_FAIL |
3-Error |
refcount [dec] |
A request from the active to process a clear translation failed.\n Please retry.\n |
cpp-ucode |
LOG_STD_ACTION |
|
NAT64-3-NAT64_POOL_ADD_FAIL |
3-Error |
pool-id [dec] rc [dec] |
This message indicates that an address could not be allocated from a pool because there were no free addresses in the pool at that time. |
cpp-ucode |
LOG_STD_ACTION |
|
NAT64-3-NAT64_REGISTRY_RC |
3-Error |
A NAT64 registry call failed with rc[chars] |
The return code from a NAT64 registry call indicates an\n\ error. |
nat64 |
LOG_STD_ACTION |
|
NAT64-3-RUNAWAY_LOOP |
3-Error |
NULL |
A loop has exceeded the expected number of iterations. |
nat64 |
LOG_STD_ACTION |
|
NAT64-3-UNINITIALIZED |
3-Error |
NAT64 feature is not properly initialized |
A function call was made when the system was not properly\n\ initialized. |
nat64 |
LOG_STD_ACTION |
|
NAT64-4-STATIC_MAP_ADD_FAIL |
4-Warning |
[chars] v4 addr %Ci v6 addr [ipv6_addr], [chars] |
An add of a static NAT64 mapping failed due to listed reason.\n This mapping will be in the IOS configuration but is not active\n in the data plane. It is recommended to remove the mapping \n from the configuration\n |
cpp-ucode |
LOG_STD_ACTION |
|
NAT64-5-ALIAS_NOT_FOUND |
5-Notice |
Unable to find alias address[inet] table_id[dec] |
An attempt was made to remove an IP alias for a NAT64 address and the alias does not exist. This is a notification that such an event happened and should not have any functional impact. This could happen under heavy load if for example a previous best effort message to add the alias was dropped. |
nat64 |
LOG_STD_ACTION |
|
NAT64-6-DEFAULT_MAX_ENTRIES |
6-Information |
default max entries value [dec] |
This is an information message which occurs when NAT is configured and a frame is dropped due to the default maximum entries limit. Starting with release 5 XNE NAT will use a default max-entries in the data plane based on the ESP type. This will not show in the configuration and is overriden by any user configuration of 'ip nat trans max-entries <value>'. The purpose of the default data plane limit is to protect the box from memory exhaustion which could occur if no limit is enforced. |
cpp-ucode |
- |
|
NAT64-6-HA_FLOW_CTRL_TIMEOUT |
6-Information |
Bulk sync is flow controlled by [chars] |
The bulk synchronization of the NAT64 configuration to the standby RP has encountered a flow control condition which has effected a timeout awaiting the condition to clear. This will result in a reload of the standby RP to allow the bulk synchronization to restart. |
nat64 |
LOG_STD_ACTION |
|
NAT64-6-HA_PEER_READY |
6-Information |
NULL |
The synchronization attempt for the message has determined that the transport has lost communication with its peer. This is a normal situation which indicates that the standby route-processor is currently out of service implying a simplex redundancy mode. |
- |
- |
|
NAT64-6-HA_RELOAD |
6-Information |
Reloading [chars] reason[chars] |
A synchronization attempt between the active and standby RP peers has failed with the reason indicated. The standby peer is reloaded in an attempt to resynchronize when operating in a stateful redundant mode. |
nat64 |
LOG_STD_ACTION |
|
NAT64-6-HA_RELOAD_DISABLED |
6-Information |
Standby reload has been disabled NAT64 RP state is out of sync and the standby should be reloaded manually |
The active and standby RPs are out of sync and the standby RP would have been reloaded but this reload was suppressed based on the configured environment. |
nat64 |
LOG_STD_ACTION |
|
NAT64-6-LOOPV4 |
6-Information |
src IP %Ci dest IP %Ci |
IPv4 packet has been dropped due to looping inside of NAT64. See recommended action |
cpp-ucode |
"There are 2 most likely items that should be checked for this error:\n" "1 check that none of the NAT64 interfaces are disabled\n" |
|
NAT64-6-LOOPV6 |
6-Information |
src IP [ipv6_addr], dest IP [ipv6_addr], |
IPv6 packet has been dropped due to looping inside of NAT64. See recommended action |
cpp-ucode |
"There are 2 most likely items that should be checked for this error:\n" "1 check that none of the NAT64 interfaces are showdown " |
|
NAT64-6-MAP_E |
6-Information |
NULL |
An unexpected input value to a function was incorrect |
nat64 |
LOG_STD_ACTION |
|
NAT64-6-SHOW_TRANS_FAIL |
6-Information |
unable to show [dec] entries from bucket % |
Unable to show some entries from session/bind database. If using verbose try using non-verbose. Otherwise situation is likely to be temporary. Or it may be wise to do 'clear ip nat trans *' as a very odd session distribution has occurred.\n |
cpp-ucode |
LOG_STD_ACTION |
|
NAT64-6-V4UDP_0CSUM_FRAG |
6-Information |
source IP %Ci dest IP %Ci source port [dec] dest port [dec] |
A first fragment of an IPv4 UDP packet with 0 checksum has been dropped |
cpp-ucode |
LOG_STD_ACTION |
|
NAT66-3-API_FAILED |
3-Error |
NULL |
A call to the API of another component has indicated an\n\ error. |
nat66 |
LOG_STD_ACTION |
|
NAT66-3-BAD_MAGIC |
3-Error |
Invalid magic number%#10x |
An internal data structure is corrupt. |
nat66 |
LOG_STD_ACTION |
|
NAT66-3-EEXIST |
3-Error |
NULL |
An item unexpectedly exists already. |
nat66 |
LOG_STD_ACTION |
|
NAT66-3-EINVAL |
3-Error |
NULL |
An unexpected input value to a function was incorrect |
nat66 |
LOG_STD_ACTION |
|
NAT66-3-ENOENT |
3-Error |
NULL |
A lookup failed unexpectedly. |
nat66 |
LOG_STD_ACTION |
|
NAT66-3-ENOMEM |
3-Error |
Memory allocation failed |
A attempt to allocae memory has failed. |
nat66 |
LOG_STD_ACTION |
|
NAT66-3-INIT_FAILED |
3-Error |
An initialization failed rc[chars] |
- |
- |
- |
|
NAT66-3-NAT66_REGISTRY_RC |
3-Error |
A NAT66 registry call failed with rc[chars] |
The return code from a NAT66 registry call indicates an\n\ error. |
nat66 |
LOG_STD_ACTION |
|
NAT66-3-RUNAWAY_LOOP |
3-Error |
NULL |
A loop has exceeded the expected number of iterations. |
nat66 |
LOG_STD_ACTION |
|
NAT66-3-UNINITIALIZED |
3-Error |
NAT66 feature is not properly initialized |
A function call was made when the system was not properly\n\ initialized. |
nat66 |
LOG_STD_ACTION |
|
NAT-6-CLEAR_FAIL_TRANS_IN_USE |
6-Information |
- |
The requested clear failed because the transaction was in use.\n Some clear commands support a 'forced' keyword which allows you \n to override this.\n |
cpp-ucode |
LOG_STD_ACTION |
|
NAT-6-LOG_TRANSLATION |
6-Information |
[chars] Translation [chars] %Ci:[dec] %Ci:[dec] %Ci:[dec] %Ci:[dec] [dec] |
A translation was created as a result of either a configuration or traffic\n flowing through the NAT subsystem |
cpp-ucode |
"This message is for debugging purposes only and gets logged only when \n" "logging is turned on" |
|
NAT-6-NON_PAT_TRANS_DETECT |
6-Information |
Non-PATable translation for [chars]: on pool [dec] orig_ip %Ci trans_ip %Ci alg_type [dec][chars] input intf [chars] mapping id [dec] created by pkt: |
This message indicates that an address could not be allocated from a pool for a specific client address because there were no free addresses in the pool at that time. |
cpp-ucode |
- |
|
NAT-6-POOL_WATERMARK_HIGH |
6-Information |
[chars] High watermark reached for pool [dec] |
This message indicates that pool usage has crossed its high watermark. Pool may exhaust soon. |
- |
- |
|
NAT-6-POOL_WATERMARK_LOW |
6-Information |
[chars] Low watermark reached for pool [dec] |
This message indicates that pool usage has crossed its low watermark. Pool should have enough address. |
cpp-ucode |
- |
|
NATMIB_HELPER-3-NOCREAT |
3-Error |
NATMIB Helper Process not created - NAT MIB will not work properly |
Attempt to start NATMIB Helper Process failed when\n\the natmib subsystem was initialised. |
snmp |
"The NATMIB Helper process was not\n\createdpossibly due to lack of memory. If you want to use the NATMIB \n\reconfigure the box so that less memory is used by\n\other features or add more memory to the system. Reload the box\n\after reconfiguring." |
|
NBAR_HA-5-NBAR_INFO |
5-Notice |
[chars] |
- |
- |
- |
|
NBAR-1-LINKNEXTCORRUPTED |
1-Alert |
link->next not NULL when allocated. link->next = [chars]\n |
An attempt was made to get a link from the free bucket\n\ which is pointing to another resource. Links within\n\ the free bucket should be NULL therefore this link is corrupted and\n\ should not be used |
high-ipqos |
"Configure the router with the <CmdBold>ip nbar resources\n\ <noCmdBold> to allocate a larger initial pool of resources." |
|
NBAR-1-LINKPREVCORRUPTED |
1-Alert |
link->prev not NULL when allocated. link->prev = [chars]\n |
An attempt was made to get a link from the free bucket\n\ which is pointing to another resource. Links within\n\ the free bucket should be NULL therefore this link is corrupted and\n\ should not be used |
high-ipqos |
"Configure the router with the <CmdBold>ip nbar resources\n\ <noCmdBold> to allocate a larger initial pool of resources." |
|
NBAR-1-MAXMEMORYUSED |
1-Alert |
Reached maximum amount of memory allocated for stile\n |
This platform allows NBAR to use a limited amount of memory for\n\ classification and that amount has been used up because of high \n\ traffic conditions.\n |
high-ipqos |
"Increase amount of memory in router.\n" |
|
NBAR-1-NODESIZEMISMATCH |
1-Alert |
Nodes size mismatch between parsing and sending:[chars] \n |
Failure during the distribution of NBAR graph nodes from the route processor to the linecards. Failure is related to node size changes between parsing and sending phase |
high-ipqos |
"Disable nbar protocols" |
|
NBAR-2-HEURISTIC_XDR_FAILED |
2-Critical |
Failure in the heuristic subsystem of NBAR: [chars] |
Failure during the distribution of NBAR heuristic data structures\n\ from the route processor to the linecards. |
high-ipqos |
"Disable heuristic protocols" |
|
NBAR-2-NOMEMORY |
2-Critical |
No memory available for [chars] |
An attempt at memory allocation failed. |
high-ipqos |
"Try these actions to remedy the problem:\n\\n\ Add memory.\n\\n\ Disable some features.\n\\n\ Apply filtering to decrease the size of system data structures - the\n\ routing table for example.\n\\n\ In general reduce other system activities to ease memory demands. If\n\ conditions warrant upgrade to a larger memory configuration." |
|
NBAR-2-NOSTATEMEM |
2-Critical |
Memory for maintaining state used up |
NBAR uses memory to maintain state information about stateful\n\ flows. There is a maximum limit on how much memory NBAR can use\n\ for this purpose and this limit has been reached. |
high-ipqos |
"Increase memory on platform" |
|
NBAR-2-RMINVALIDCONFIG |
2-Critical |
NBAR resource manager : too many buckets [dec] |
- |
- |
- |
|
NBAR-2-RMNORESOURCE |
2-Critical |
NBAR resources exhausted |
In order to save stateful information on protocols NBAR must\n\ use dynamic resources. These resources have been exhausted. |
high-ipqos |
"Configure the router with the <CmdBold>ip nbar resources\n\ <noCmdBold> to allocate a larger initial pool of resources.\n\ The default number of initial resources is 10000. Also try\n\ configuring a shorter max-idle time." |
|
NBAR-3-CACHE_SYNC_ERR |
3-Error |
[chars] |
- |
- |
- |
|
NBAR-3-PP_AUTO_UPDATE_FILE_COPY_FAIL |
3-Error |
failed to copy file \[chars]\ |
NBAR protocol-pack Auto-Update failed to update the PPACK file |
nbar |
"Check PPack auto-update server address" |
|
NBAR-3-PP_AUTO_UPDATE_FILE_VALIDITY_FAIL |
3-Error |
failed to verify file \[chars]\ |
NBAR protocol-pack Auto-Update failed to verify file validity |
nbar |
"Check PPack auto-update server address" |
|
NBAR-3-PP_AUTO_UPDATE_GENERIC_ERR |
3-Error |
Generic PP_UPDATE Error: \[chars]\ |
NBAR protocol-pack Auto-Update error |
nbar |
"None" |
|
NBAR-4-AUTO_CUSTOM_GENERIC_HOST_WARNING |
4-Warning |
[chars] |
- |
- |
- |
|
NBAR-4-AUTO_CUSTOM_UNCLASSIFIED_PORT_WARNING |
4-Warning |
[chars] |
- |
- |
- |
|
NBAR-4-CACHE_SYNC_WARN |
4-Warning |
[chars] |
- |
- |
- |
|
NBAR-4-PP_AUTO_UPDATE_GENERIC_WARNING |
4-Warning |
Generic PP_UPDATE Warning: \[chars]\ |
NBAR protocol-pack Auto-Update warning |
nbar |
"None" |
|
NBAR-4-STILE_MAX_PD_INTF |
4-Warning |
NBAR protocol-discovery is enabled on maximum number of interfaces [dec] supported by this platform |
This platform allows NBAR to enable protocol-discovery on a limited number of interfaces and that limit has reached. |
nbar |
"Need to disable protocol-discovery from an interface to enable " "protocol-discovery on any new interface." |
|
NBAR-5-PP_AUTO_UPDATE_FILE_COPY_SUCCESS |
5-Notice |
succesfully copied file \[chars]\ |
NBAR protocol-pack Auto-Update succesfully updated the PPACK file |
- |
"No action required. Informational message" |
|
NBAR-6-CACHE_SYNC_INFO |
6-Information |
[chars] |
- |
- |
- |
|
NBAR-6-INACTIVE_PROTOCOL_PACK |
6-Information |
[chars] is successfully loaded as an Inactive Protocol Pack |
The NBAR Engine Version of the protocol pack is either less than the Minimum Backward Compatible Engine Version or is greater than the NBAR Engine Version of the image and therefore it will be loaded as an Inactive Protocol Pack |
nbar |
"Since the protocol pack is loaded as an Inactive Protocol Pack" "signatures in this pack will not be available for any classification." "To use the protocol pack upgrade/downgrade to an image " "which is compatible with the NBAR Engine Version of the " "protocol pack." |
|
NBAR-6-PDL_ERRORS |
6-Information |
PDL parsing error: [chars] |
Unable to parse PDL issue in syntax |
nbar |
"PL need to fine tune or modify PDL." |
|
NBAR-6-PORT_MAP_DEPRECATION |
6-Information |
[chars] command will be deprecated soon.\n\ In future it will not be necessary to configure port-map on a Protocol to create a new\n\ Custom protocol onto the same well known port. |
In future releases it will not be necessary to configure\n\ port-map on a Protocol to create a new Custom protocol onto\n\ the same well known port. Port-map command will be\n\ deprecated in future releases. |
nbar |
"No action required." |
|
NBAR-6-PP_AUTO_UPDATE_FILE_VALIDITY_SUCCESS |
6-Information |
succefully verified file \[chars]\ |
NBAR protocol-pack Auto-Update succesfully checked file validity |
- |
"No action required. Informational message" |
|
NBAR-6-PP_AUTO_UPDATE_GENERIC_INFO |
6-Information |
Generic PP_UPDATE Information: \[chars]\ |
NBAR protocol-pack Auto-Update information |
- |
"None" |
|
NBAR-6-PP_AUTO_UPDATE_PREV_PP_DELETE_FAIL |
6-Information |
failed to delete previous PP file \[chars]\ |
NBAR protocol-pack Auto-Update failed to delete the prevously loaded protocol pack |
nbar |
"Check if previous ppack still exists and if the disk is write protected" |
|
NBAR-6-PP_AUTO_UPDATE_PREV_PP_DELETE_SUCCESS |
6-Information |
succefully deleted previous PP file \[chars]\ |
NBAR protocol-pack Auto-Update succefully deleted the prevously loaded protocol pack |
- |
"No action required. Informational message" |
|
NBRCHG-5-LDP |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
NCS4200_PTP-3-MSGDISPATCH |
3-Error |
Unable to dispatch received TDL message from PTP daemon |
An unexpected condition has occurred while IOS was trying to dispatch a TDL message received from PTP daemon. |
ncs4200-ptp |
LOG_STD_ACTION |
|
NCS4200_PTP-3-MSGINITFAIL |
3-Error |
Failed to initalize required PTP resource: [chars] |
During the initialization of the resources required by PTP a failure occured. This has prevented PTP from being activated. |
ncs4200-ptp |
LOG_STD_ACTION |
|
NCS4200_RP_ATM_SPA-3-ATM_PER_SPA_MAX_VC_LIMIT_REACHED |
3-Error |
total active atm vc per ATM SPA reached limitation of [dec] |
total number of active atm vc per ATM SPA has reached max limit |
- |
LOG_STD_ACTION |
|
NCS4200IM-3-DIFF_IM_INSERTED |
3-Error |
[chars] - [chars] in bay [dec] |
A different IM type has been inserted in the bay which previously had another IM type. If the interfaces were set to default before swap the IM will boot up fine. If not IM will goto Out-of-service state. Kindly insert the previous IM type use hw-module subslot 0/x default and then proceed with the IM swap. If not might need to reload the box for recovery |
- |
- |
|
NCS4200IM-3-INCOMPATIBLE |
3-Error |
[chars]-[dec] |
P1D and onwards Cu IM.... is not backward compatible with P1A/P1B/P1C Cu IM use the same build of Cu IM or reload the router to use the new build. |
- |
- |
|
NCS4200IM-3-INVALID_COMBINATION |
3-Error |
[chars] is not allowed in bay [dec] can be supported only in bays [chars] |
The inserted IM is not supported in the specified subslot given the combination of existing IMs in the chassis. |
- |
- |
|
NCS4200IM-3-INVALID_MODE |
3-Error |
[chars] with mode [chars] is not allowed in bay [dec] can be supported only in bays [chars] |
The inserted IM is not supported in the specified subslot given the combination of existing IMs in the chassis. |
- |
- |
|
NCS4200IM-3-UNSUPPORTED |
3-Error |
This Interface Module is not supported in subslot [dec] |
The inserted IM is not supported in the specified subslot. Kindly check the supported slots for the IM type. |
- |
- |
|
NCS4200IM-3-UNSUPPORTED_PLATFORM |
3-Error |
This Interface Module is not supported in [chars] platform |
The inserted IM is not supported in the specified platform |
- |
- |
|
NCS4200INTF-3-UNSUPPORTED |
3-Error |
Interface [chars] is not supported in subslot [dec] by the [chars] module |
The Interface specified in the error message is not supported in the specified Subslot by the version of the operating system currently running on the system. |
- |
- |
|
NCS4206_CFC-3-PUNT_KEEPALIVE_ERR_ALLOC_CSB |
3-Error |
Failed to allocate a csb |
Can't allocate a csb when generating punt err log |
ncs4206-cfc |
LOG_STD_ACTION |
|
NCS4206_CFC-3-PUNT_KEEPALIVE_ERR_ALLOC_TTY |
3-Error |
Failed to allocate a tty |
Can't allocate a TTY when generating punt err log |
ncs4206-cfc |
LOG_STD_ACTION |
|
NCS4206_CFC-3-PUNT_KEEPALIVE_ERR_OPEN_FILE |
3-Error |
Failed to open file: [chars] |
Failed to open file when generating punt err log |
ncs4206-cfc |
LOG_STD_ACTION |
|
NCS4206_CFC-3-PUNT_KEEPALIVE_ERR_WRITE_TO_FILE |
3-Error |
Write to file Id [dec] failed [dec] bytes expected [dec] bytes |
Write to file failed when generating punt err log |
ncs4206-cfc |
LOG_STD_ACTION |
|
NCS4206_CFC-4-PUNT_KEEPALIVE_ERR_CLOSE_FILE |
4-Warning |
Failed to close file with descriptor: [dec] |
Closing of file failed when generating punt err log |
ncs4206-cfc |
LOG_STD_ACTION |
|
NCS4206_CFC-4-PUNT_KEEPALIVE_ERR_GET_FILE_NAME |
4-Warning |
Failed to get file name |
Could not form a file name when generating punt err log |
ncs4206-cfc |
LOG_STD_ACTION |
|
NCS4206_CFC-4-PUNT_KEEPALIVE_ERR_INV_FILE_ID |
4-Warning |
Invalid file descriptor: [dec] |
Invalid file descriptor was found when generating punt err log |
ncs4206-cfc |
LOG_STD_ACTION |
|
NCS4206_CFC-4-PUNT_KEEPALIVE_ERR_INV_PARAM |
4-Warning |
Invalid parameter: [chars] |
Invalid parameter was passed when generating punt err log |
ncs4206-cfc |
LOG_STD_ACTION |
|
NET_SERV-4-UNEXPECTED |
4-Warning |
Unexpected error: [chars] |
An unexpected error occurred while performing a services timer operation |
slb |
LOG_STD_RECUR_ACTION |
|
NET_SERV-4-WARNING |
4-Warning |
Unexpected condition: [chars] |
An unexpected condition was detected while performing a services timer\n\ operation |
slb |
LOG_STD_RECUR_ACTION |
|
NETCLK-3-ESMC_EVENT_CREATE_FAIL |
3-Error |
Failed to create ESMC event. |
Failed to create an ESMC event to be queued. |
sync-e |
LOG_STD_NO_ACTION |
|
NETCLK-3-ESMC_EVENT_ENQUEUE_FAIL |
3-Error |
Failed to enqueue ESMC event. |
Failed to add an ESMC event to the event queue. |
sync-e |
LOG_STD_NO_ACTION |
|
NETCLK-3-ESMC_EVENT_QUEUE_ALLOC_FAIL |
3-Error |
Failed to allocate memory for ESMC event queue. |
Failed to allocate memory for the ESMC event queue. |
sync-e |
LOG_STD_NO_ACTION |
|
NETCLK-3-ESMC_EVENT_QUEUE_INIT_FAIL |
3-Error |
Failed to initialize ESMC event queue. |
Failed to initialize the ESMC event queue. |
sync-e |
LOG_STD_NO_ACTION |
|
NETCLK-4-FAIL |
4-Warning |
The Network Clock protocol has encountered the error: [chars]. |
The protocol has run into a failure condition. The reason should be given in the parenthesis. |
sync-e |
"show network-clock synchronization and " "show network-clock synchronization detail and " "show module" |
|
NETCLK-4-NETCLK_CMD_FAIL |
4-Warning |
NULL |
This message indicates that a network clock command from RP to IOS-SR or SPAs has failed |
asr1k-iosd-infra |
"show logging and show network-clocks" |
|
NETCLK-4-PD_REG |
4-Warning |
[chars] [dec] |
The platform has failed to provide the protocol one of the mandatory functions. |
sync-e |
LOG_STD_ACTION |
|
NETCLK-5-NETCLK_CHANGE |
5-Notice |
Network clock source transitioned from priority [dec] [chars] to priority [dec] [chars]\n |
This notice indicates a change in the clock source. |
asr1k-iosd-infra |
"No action required." |
|
NETCLK-5-NETCLK_MODE_CHANGE |
5-Notice |
Network clock source not available. The network clock has changed to [chars]\n |
- |
asr1k-iosd-infra |
"No action required" |
|
NETCLK-5-NETCLK_PHASE_LOST |
5-Notice |
Network clock source not available. Phase-lost on clock priority [dec] [chars]\n |
- |
asr1k-iosd-infra |
"No action required" |
|
NETCLK-6-ALL_SRC_REM |
6-Information |
All synchronization sources have been removed from [chars] selection process. |
All synchronization sources are removed from synchronization source selection processes i.e. T0 or selection process per T4. |
sync-e |
LOG_STD_NO_ACTION |
|
NETCLK-6-ENTER_HOLDOVER |
6-Information |
System Internal synchronization source is selected. |
System Internal synchronization source Internal is selected as all other nominated synchronization source are not valid for Synchronization selection process. |
sync-e |
LOG_STD_NO_ACTION |
|
NETCLK-6-INV_QL |
6-Information |
invalid QL [chars] received for [chars] on network option [chars]. |
The platform has notify RP the clock quality of an input source. But the value appears to be invalid based on the current configured network option. |
sync-e |
LOG_STD_NO_ACTION |
|
NETCLK-6-QL_CHANGE |
6-Information |
Input QL for [chars] is [chars] |
The input QL used for a network-clock input changed |
sync-e |
LOG_STD_NO_ACTION |
|
NETCLK-6-SEL_CLOCK_SRC |
6-Information |
Synchronization source [chars][chars] is selected by selection processT0 |
Synchronization source selection process has selected source q receive clock to synchronize the system and generate T0transmit SEC clock. T0 clock is used as TX clock on all |
sync-e |
LOG_STD_NO_ACTION |
|
NETCLK-6-SEL_T4_CLOCK_SRC |
6-Information |
Synchronization source [chars] is selected by selection process to synchronize the system and generate T4[chars] output[chars] |
Synchronization source selection process for T4external interface |
sync-e |
LOG_STD_NO_ACTION |
|
NETCLK-6-SRC_ADD |
6-Information |
Synchronization source [chars] is added to [chars] selection process. |
Synchronization source is added to synchronization source selection processes i.e. T0 or selection process per T4. |
sync-e |
LOG_STD_NO_ACTION |
|
NETCLK-6-SRC_REM |
6-Information |
Synchronization source [chars] is removed from [chars] selection process. |
Synchronization source is removed from synchronization source selection processes i.e. T0 or selection process per T4. |
sync-e |
LOG_STD_NO_ACTION |
|
NETCLK-6-SRC_UPD |
6-Information |
Synchronization source [chars] status [chars] is posted to all selection process. |
Synchronization source status event is updated to synchronization |
sync-e |
LOG_STD_NO_ACTION |
|
NETCONF-3-MEMORY |
3-Error |
[chars] |
Netconf subsystem has experienced a problem gettting the required\n\ memory to complete this operation. |
netconf |
"Check system memory for other memory allocation errors and contact\n\ Technical support for problem resolution. In the absence of IOS errors\n\ upgrading the memory in the network device may be required." |
|
NETFLOWLITE-4-NETFLOWLITE_CONNECTORTYPE_UPDATE |
4-Warning |
Netflow-Lite monitor configuration is not compatible with connector type on interface [chars] [chars] |
A new interface connector type has been detected it is not\n\ compatible with the netflow-lite monitor configuration on the\n\ original interface. The conflicting netflow-lite monitor\n\ configuration will be removed no user action is required. |
netflow-lite |
LOG_STD_NO_ACTION |
|
NETWORK_CLOCK_SYNCHRONIZATION-4-NETCLK_FAIL |
4-Warning |
Active network clock source [chars] priority [dec] failure |
This warning message indicates that there has been a failure of active clock source |
PI-netclk |
"No action required" |
|
NETWORK_CLOCK_SYNCHRONIZATION-6-NETCLK_ACTIVE |
6-Information |
Active network clock source is [chars] priority [dec] |
This indicates the presence of an active network clock along with its priority |
PI-netclk |
"This is an informational message only no action required." |
|
NETWORK_PORT_SATELLITE-3-PHY_LOCKUP |
3-Error |
Repeated phy lockup seen on [chars]. Interface will be shut down. |
Phy lockup was detected too many times in a row. Interface is shutdown to avoid continuous link flapping. |
firmware |
"To re-enable interface issue 'shutdown' followed " "by 'no shutdown' command in interface " "configuration mode." |
|
NETWORK_PORT_SATELLITE-6-MAC_LOCKUP |
6-Information |
Transmit lock up is detected in [chars]. This port is adminstratively down. |
When the PHY is powered on and off the MAC cycles from Gigabit to 100 and the port might lock up and stop sending packets. The PHY refers to the physical layer device on the switch which sends and receives optical signals and provides framing and line integrity. |
hardware |
"Shut down the port by using the shutdown interface configuration " "command and bring it back up by using the no shutdown interface " "configuration command" |
|
NETWORK_RF_API-3-CHKPT_ENTITY_FAIL |
3-Error |
A checkpointing entity [chars] operation failed rc=[dec] |
An internal operation that is associated with checkpointing failed. The return code that is specified in the message output identifies the type of failure. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized. |
ha-idb-sync |
"Issue 'show checkpoint entities' and " "'show checkpoint clients' to " "determine the problem" |
|
NETWORK_RF_API-3-CLIENT_REGISTER_FAIL |
3-Error |
Failed to register with [chars] rc =[dec] |
A redundancy client could not be registered. An internal failure associated with client registration occurred in the run-time module specified in the message output. The return code that is specified in the message output identifies the type of failure that was detected. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized. |
ha-idb-sync |
LOG_STD_SH_TECH_ACTION |
|
NETWORK_RF_API-3-FAILDECODEDATADESC |
3-Error |
Cannot decode data descriptor for [chars] descriptor type=[chars] |
An internal data descriptor could not be decoded for synchronization for the interface or controller in the run-time module specified in the message output. The failure most likely occurred because of a software error. The descriptor type specified in the message output identifies the type of descriptor the failure occurred with. The system state between the active and standby units might not be properly synchronized. |
ha-idb-sync |
"show redundancy idb-sync-history" |
|
NETWORK_RF_API-3-FAILSENDMSGTOACTIVE |
3-Error |
Failed to send [chars] message to active for [chars] [chars] |
The specified synchronization message which is an internal IPC message could not be sent to the active unit in the specified run-time module. The failure most likely occurred because of a software error. Additional details on the nature of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized. |
ha-idb-sync |
LOG_STD_SH_TECH_ACTION |
|
NETWORK_RF_API-3-FAILSENDMSGTOSTDBY |
3-Error |
Failed to send [chars] message to standby for [chars] rc=[dec] |
The specified synchronization message which is an internal IPC message could not be sent to the standby unit in the specified run-time module. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the type of failure. The system state between the active and standby units might not be properly synchronized. |
ha-idb-sync |
LOG_STD_SH_TECH_ACTION |
|
NETWORK_RF_API-3-INVALID_CHKPT_STATUS_CODE |
3-Error |
Invalid checkpointing status code received rc=[dec] |
An invalid checkpoint status code has been detected. An internal status code that is associated with checkpointing was found to be invalid. The return code that is specified in the message output identifies the invalid code that was detected. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized. |
ha-idb-sync |
LOG_STD_SH_TECH_ACTION |
|
NETWORK_RF_API-3-INVALID_MSG_RECEIVED |
3-Error |
Invalid [chars] message received |
A message that is used for state synchronization was not received correctly. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized. |
ha-idb-sync |
LOG_STD_SH_TECH_ACTION |
|
NETWORK_RF_API-3-ISSU_MSG_MTU_INVALID |
3-Error |
The ISSU message MTU is invalid: [chars] |
A message buffer size that is used for state synchronization was found to be invalid. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. Additional details on the nature of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized. |
ha-idb-sync |
LOG_STD_SH_TECH_ACTION |
|
NETWORK_RF_API-3-ISSU_MSG_TYPE_INCOMPAT |
3-Error |
The active and standby ISSU message types are incompatible |
A message that is used for state synchronization is deemed to be incompatible. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized. |
ha-idb-sync |
LOG_STD_SH_TECH_ACTION |
|
NETWORK_RF_API-3-ISSU_REG_SES_INFO |
3-Error |
Failed to register ISSU session information: [chars] |
The system failed to register the ISSU session information required to complete version exchange between the active and standby units. The failure most likely occurred because of a software error. Additional details on the nature of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized. |
ha-idb-sync |
LOG_STD_SH_TECH_ACTION |
|
NETWORK_RF_API-3-ISSU_START_NEGO_SES |
3-Error |
Failed to start ISSU session: [chars] |
The system failed to start the ISSU negotiation session required to complete version exchange between the active and standby units. The failure most likely occurred because of a software error. Additional details on the nature of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized. |
ha-idb-sync |
LOG_STD_SH_TECH_ACTION |
|
NETWORK_RF_API-3-ISSU_TRANSFORM_FAIL |
3-Error |
The ISSU message [chars] transformation failed: [chars] |
A message that is used for state synchronization could not be transformed correctly. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. Additional details on the nature of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized. |
ha-idb-sync |
LOG_STD_SH_TECH_ACTION |
|
NETWORK_RF_API-3-ISSU_UNREG_SES_INFO |
3-Error |
Failed to register ISSU session information: [chars] |
The system failed to unregister the ISSU session information required to complete version exchange between the active and standby units. The failure most likely occurred because of a software error. Additional details on the nature of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized. |
ha-idb-sync |
LOG_STD_SH_TECH_ACTION |
|
NETWORK_RF_API-3-NO_CHKPT_BUFFER |
3-Error |
No checkpointing buffer for [chars] rc=[dec] |
A message data buffer that is used for state synchronization could not be obtained. An internal data structure could not be allocated for synchronization in the run-time module specified in the message output. The return code that is specified in the message output identifies the type of failure. The failure most likely occurred because of a software error or a lack of system memory. The system state between the active and standby units might not be properly synchronized. |
ha-idb-sync |
"If you determine that this condition was caused by " "a lack of system memory reduce system activity to " "ease memory demands or if conditions warrant upgrade " "to a larger memory configuration. Otherwise " LOG_STD_SH_TECH_ACTION |
|
NETWORK_RF_API-3-NO_MSG_BUFFER |
3-Error |
No message buffer for [chars] |
A message data buffer that is used for state synchronization could not be obtained. An internal data structure could not be allocated for synchronization in the run-time module specified in the message output. The failure most likely occurred because of a software error or a lack of system memory. The system state between the active and standby units might not be properly synchronized. |
ha-idb-sync |
"If you determine that this condition was caused by " "a lack of system memory reduce system activity to " "ease memory demands or if conditions warrant upgrade " "to a larger memory configuration. Otherwise " LOG_STD_SH_TECH_ACTION |
|
NETWORK_RF_API-3-NO_RESOURCES |
3-Error |
[chars] |
A run-time module could not obtain the resources that are required to complete a task. The failure most likely occurred because of a software error or a lack of system memory. Additional details on the nature of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized. |
ha-idb-sync |
"If you determine that this condition was caused by " "a lack of system memory reduce system activity to " "ease memory demands or if conditions warrant upgrade " "to a larger memory configuration. Otherwise " LOG_STD_SH_TECH_ACTION |
|
NETWORK_RF_API-6-IDB_TRANSITIONS_PENDING |
6-Information |
Switchover terminated with [dec] transitions pending after there was no transition activity for [dec] seconds |
The system terminated the switchover idb transitioning phase with a number of idb transitions still pending because no switchover related IDB transitions were logged during the specified time interval. Some connected routes may experience a temporary loss of traffic. |
ha-idb-sync |
LOG_STD_NO_ACTION |
|
NG3K_OIR_ISSU-3-BUFFER |
3-Error |
NG3K OIR ISSU client failed to get buffer for message error [dec] |
NG3K OIR ISSU client failed to get buffer for building\n\ a negotiation message. Hence it can send the negotiation\n\ message to the standby unit. When there is a problem in\n\ the negotiaiton the standby unit can not be brought up. |
platform-ha |
"show logging and show checkpoint client" |
|
NG3K_OIR_ISSU-3-CAP_INVALID_SIZE |
3-Error |
NG3K OIR ISSU client capability list is empty. |
The BG3K OIR ISSU client capability exchange list size\n\ is invalid. |
platform-ha |
"show issu capability entries <Client_ID>" |
|
NG3K_OIR_ISSU-3-CAP_NOT_COMPATIBLE |
3-Error |
NG3K OIR ISSU client capability exchange result incompatible. |
The NG3K OIR ISSU client capability exchange has negotiated\n\ as incompatible with the peer. |
platform-ha |
"show issu negotiated capability <Session_ID>" |
|
NG3K_OIR_ISSU-3-CAPABILITY |
3-Error |
NG3K OIR ISSU client [chars] |
NG3K OIR ISSU client observed an error during capability\n\ negotiation. When this error happens there is a mismatch\n\ between the client capability between the active and\n\ standby unit. |
platform-ha |
"show issu capability entries <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated capability <session_id>" |
|
NG3K_OIR_ISSU-3-INIT |
3-Error |
NG3K OIR ISSU client initialization failed at [chars] error [chars] |
NG3K OIR ISSU client could not be initiailzed this will\n\ cause catstrophic failure when ISSU upgrade or downgrade\n\ is performed. |
platform-ha |
LOG_STD_SH_TECH_ACTION |
|
NG3K_OIR_ISSU-3-MSG_NOT_OK |
3-Error |
NG3K OIR ISSU client message [dec] is not compatible |
NG3K OIR ISSU client received an incompatible message\n\ from the peer unit. Since the message is not compatible\n\ it can be processed by this unit |
platform-ha |
"show issu message group <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
NG3K_OIR_ISSU-3-MSG_SIZE |
3-Error |
NG3K OIR ISSU client failed to get the message size for message [dec] |
NG3K OIR ISSU client failed to calculate message size\n\ for the message specified. The NG3K OIR ISSU client will not\n\ be able to send message to the standby unit. |
platform-ha |
"show issu message group <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
NG3K_OIR_ISSU-3-POLICY |
3-Error |
NG3K OIR ISSU client message type [dec] is [chars] |
NG3K OIR ISSU client received an message type which it\n\ does not support. The policy is applied to make the session\n\ compatible. |
platform-ha |
"show issu session <client_id>" |
|
NG3K_OIR_ISSU-3-SEND_FAILED |
3-Error |
NG3K OIR ISSU client failed to send a negotiation message error [dec] |
NG3K OIR ISSU client could not send a session negotiation\n\ message to the peer. When there is a problem in the\n\ negotiation the standby unit can not be brought up. |
platform-ha |
"show logging and show checkpoint client" |
|
NG3K_OIR_ISSU-3-SESSION |
3-Error |
NG3K OIR ISSU client [chars] |
NG3K OIR ISSU client observed an error during a session\n\ negotiation with the peer unit. When there is a problem\n\ with the session the standby unit can not be brought up. |
platform-ha |
"show issu capability entries <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated capability <session_id>" |
|
NG3K_OIR_ISSU-3-SESSION_UNREGISTRY |
3-Error |
NG3K OIR ISSU client failed to unregister session information. Error: [dec] [chars] |
The NG3K OIR ISSU client failed to unregister session information. |
platform-ha |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
NG3K_OIR_ISSU-3-TRANSFORM |
3-Error |
NG3K OIR ISSU client [chars] transform failed error [chars] |
NG3K OIR ISSU client could not transform the message.\n\ If the transmit transformation failed it means that the\n\ checkpoint message can not be sent to the standby unit.\n\ If the receive transformation failed it means that the\n\ checkpoint message can not be applied on the standby\n\ unit. In both cases the NG3K OIR state will not\n\ be indentical with the active unit. |
platform-ha |
"show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
NG3K_OIR-3-BULK_SYNC |
3-Error |
[chars] |
Bulk sync failure the reason for the failure will be provided in the string |
platform-ha |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
NG3K_OIR-3-FILE_OPEN_FAILURE |
3-Error |
File [chars] open failed |
File Open failed |
platform-ha |
LOG_STD_SH_TECH_ACTION |
|
NG3K_OIR-3-INVALID_MSG_RECEIVED |
3-Error |
Invalid [chars] message received |
A message that is used for state synchronization was not received correctly. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized. |
platform-ha |
LOG_STD_SH_TECH_ACTION |
|
NG3K_OIR-3-MAC_FAILURE |
3-Error |
Mac Failure |
NULL MAC |
platform-ha |
LOG_STD_SH_TECH_ACTION |
|
NG3K_OIR-3-MALLOC_FAILURE |
3-Error |
[chars] |
Failed to allocated memory for a structure or event |
platform-ha |
LOG_STD_SH_TECH_ACTION |
|
NG3K_OIR-3-OIR_FAILURE |
3-Error |
Message:[chars]Error:[dec] |
OIR failures due to various reasons |
platform-ha |
LOG_STD_SH_TECH_ACTION |
|
NG3K_OIR-3-REG_FAILURE |
3-Error |
Message:[chars]Error:[dec] |
Registration Failure |
platform-ha |
LOG_STD_SH_TECH_ACTION |
|
NGMOD_OBFL-5-DISABLED |
5-Notice |
[chars] Onboard Failure Logging disabled on slot [dec] |
SWC Sensor Registration failed! |
- |
"This message is for informational purposes only" |
|
NGWC_FEC_ISSU-3-BUFFER |
3-Error |
NGWC FEC ISSU client failed to get buffer for message error [dec] |
NGWC FEC ISSU client failed to get buffer for building\n\ a negotiation message. Hence it can send the negotiation\n\ message to the standby unit. When there is a problem in\n\ the negotiaiton the standby unit can not be brought up. |
platform-ha |
"show logging and show checkpoint client" |
|
NGWC_FEC_ISSU-3-CAP_INVALID_SIZE |
3-Error |
NGWC FEC ISSU client capability list is empty. |
The NGWC FEC ISSU client capability exchange list size\n\ is invalid. |
platform-ha |
"show issu capability entries <Client_ID>" |
|
NGWC_FEC_ISSU-3-CAP_NOT_COMPATIBLE |
3-Error |
NGWC FEC ISSU client capability exchange result incompatible. |
The NGWC FEC ISSU client capability exchange has negotiated\n\ as incompatible with the peer. |
platform-ha |
"show issu negotiated capability <Session_ID>" |
|
NGWC_FEC_ISSU-3-CAPABILITY |
3-Error |
NGWC FEC ISSU client [chars] |
NGWC FEC ISSU client observed an error during capability\n\ negotiation. When this error happens there is a mismatch\n\ between the client capability between the active and\n\ standby unit. |
platform-ha |
"show issu capability entries <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated capability <session_id>" |
|
NGWC_FEC_ISSU-3-INIT |
3-Error |
NGWC FEC ISSU client initialization failed at [chars] error [chars] |
NGWC FEC ISSU client could not be initiailzed this will\n\ cause catstrophic failure when ISSU upgrade or downgrade\n\ is performed. |
platform-ha |
LOG_STD_SH_TECH_ACTION |
|
NGWC_FEC_ISSU-3-MSG_NOT_OK |
3-Error |
NGWC FEC ISSU client message [dec] is not compatible |
NGWC FEC ISSU client received an incompatible message\n\ from the peer unit. Since the message is not compatible\n\ it can be processed by this unit |
platform-ha |
"show issu message group <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
NGWC_FEC_ISSU-3-MSG_SIZE |
3-Error |
NGWC FEC ISSU client failed to get the message size for message [dec] |
NGWC FEC ISSU client failed to calculate message size\n\ for the message specified. The NGWC FEC ISSU client will not\n\ be able to send message to the standby unit. |
platform-ha |
"show issu message group <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
NGWC_FEC_ISSU-3-POLICY |
3-Error |
NGWC FEC ISSU client message type [dec] is [chars] |
NGWC FEC ISSU client received an message type which it\n\ does not support. The policy is applied to make the session\n\ compatible. |
platform-ha |
"show issu session <client_id>" |
|
NGWC_FEC_ISSU-3-SEND_FAILED |
3-Error |
NGWC FEC ISSU client failed to send a negotiation message error [dec] |
NGWC FEC ISSU client could not send a session negotiation\n\ message to the peer. When there is a problem in the\n\ negotiation the standby unit can not be brought up. |
platform-ha |
"show logging and show checkpoint client" |
|
NGWC_FEC_ISSU-3-SESSION |
3-Error |
NGWC FEC ISSU client [chars] |
NGWC FEC ISSU client observed an error during a session\n\ negotiation with the peer unit. When there is a problem\n\ with the session the standby unit can not be brought up. |
platform-ha |
"show issu capability entries <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated capability <session_id>" |
|
NGWC_FEC_ISSU-3-SESSION_UNREGISTRY |
3-Error |
NGWC FEC ISSU client failed to unregister session information. Error: [dec] [chars] |
The NGWC FEC ISSU client failed to unregister session information. |
platform-ha |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
NGWC_FEC_ISSU-3-TRANSFORM |
3-Error |
NGWC FEC ISSU client [chars] transform failed error [chars] |
NGWC FEC ISSU client could not transform the message.\n\ If the transmit transformation failed it means that the\n\ checkpoint message can not be sent to the standby unit.\n\ If the receive transformation failed it means that the\n\ checkpoint message can not be applied on the standby\n\ unit. In both cases the NGWC FEC state will not\n\ be indentical with the active unit. |
platform-ha |
"show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
NGWC_FEC-3-BULK_SYNC |
3-Error |
[chars] |
Bulk sync failure the reason for the failure will be provided in the string |
platform-ha |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
NGWC_FEC-3-FILE_OPEN_FAILURE |
3-Error |
File [chars] open failed |
File Open failed |
platform-ha |
LOG_STD_SH_TECH_ACTION |
|
NGWC_FEC-3-INVALID_MSG_RECEIVED |
3-Error |
Invalid [chars] message received |
A message that is used for state synchronization was not received correctly. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized. |
platform-ha |
LOG_STD_SH_TECH_ACTION |
|
NGWC_FEC-3-MAC_FAILURE |
3-Error |
Mac Failure |
NULL MAC |
platform-ha |
LOG_STD_SH_TECH_ACTION |
|
NGWC_FEC-3-MALLOC_FAILURE |
3-Error |
[chars] |
Failed to allocated memory for a structure or event |
platform-ha |
LOG_STD_SH_TECH_ACTION |
|
NGWC_FEC-3-OIR_FAILURE |
3-Error |
Message:[chars]Error:[dec] |
NGWC FEC failures due to various reasons |
platform-ha |
LOG_STD_SH_TECH_ACTION |
|
NGWC_FEC-3-REG_FAILURE |
3-Error |
Message:[chars]Error:[dec] |
Registration Failure |
platform-ha |
LOG_STD_SH_TECH_ACTION |
|
NGWC_FMANRP_IPSEC-3-UNSUPPORT_CONFIGURATION |
3-Error |
This configuration is not supported on [chars] |
This operation is not supported on the system |
accsw-p-security |
"show platform" |
|
NGWC_FMANRP_IPSEC-3-UNSUPPORT_DATAPATH |
3-Error |
IPSEC datapath is not supported as mixed stacking was detected. Reload is required when stacking is changed to unmixed |
This operation is not supported on mixed stacking |
accsw-p-security |
"show platform" |
|
NGWC_FMANRP_IPSEC-4-UNSUPPORT_MIXSTACKING |
4-Warning |
Mixed stacking is detected. [chars] for IPSEC |
IPSEC feature is not supported on mixed stacking system |
accsw-p-security |
"show platform" |
|
NGWC_ILP_ISSU-3-BUFFER |
3-Error |
Platform Inline Power ISSU client failed to get buffer for message error [dec] |
Platform Inline Power ISSU client failed to get buffer for building\n\ a negotiation message. Hence it can send the negotiation\n\ message to the standby unit. When there is a problem in\n\ the negotiaiton the standby unit can not be brought up. |
platform-ha |
"show logging and show checkpoint client" |
|
NGWC_ILP_ISSU-3-CAP_INVALID_SIZE |
3-Error |
Platform Inline Power ISSU client capability list is empty. |
The Platform Inline Power ISSU client capability exchange list size\n\ is invalid. |
platform-ha |
"show issu capability entries <Client_ID>" |
|
NGWC_ILP_ISSU-3-CAP_NOT_COMPATIBLE |
3-Error |
Platform Inline Power ISSU client capability exchange result incompatible. |
The Platform Inline Power ISSU client capability exchange has negotiated\n\ as incompatible with the peer. |
platform-ha |
"show issu negotiated capability <Session_ID>" |
|
NGWC_ILP_ISSU-3-CAPABILITY |
3-Error |
Platform Inline Power ISSU client [chars] |
Platform Inline Power ISSU client observed an error during capability\n\ negotiation. When this error happens there is a mismatch\n\ between the client capability between the active and\n\ standby unit. |
platform-ha |
"show issu capability entries <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated capability <session_id>" |
|
NGWC_ILP_ISSU-3-INIT |
3-Error |
Platform Inline Power ISSU client initialization failed at [chars] error [chars] |
Platform Inline Power ISSU client could not be initiailzed this will\n\ cause catstrophic failure when ISSU upgrade or downgrade\n\ is performed. |
platform-ha |
LOG_STD_SH_TECH_ACTION |
|
NGWC_ILP_ISSU-3-MSG_NOT_OK |
3-Error |
Platform Inline Power ISSU client message [dec] is not compatible |
Platform Inline Power ISSU client received an incompatible message\n\ from the peer unit. Since the message is not compatible\n\ it can be processed by this unit |
platform-ha |
"show issu message group <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
NGWC_ILP_ISSU-3-MSG_SIZE |
3-Error |
Platform Inline Power ISSU client failed to get the message size for message [dec] |
Platform Inline Power ISSU client failed to calculate message size\n\ for the message specified. The Platform Inline Power ISSU client will not\n\ be able to send message to the standby unit. |
platform-ha |
"show issu message group <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
NGWC_ILP_ISSU-3-POLICY |
3-Error |
Platform Inline Power ISSU client message type [dec] is [chars] |
Platform Inline Power ISSU client received an message type which it\n\ does not support. The policy is applied to make the session\n\ compatible. |
platform-ha |
"show issu session <client_id>" |
|
NGWC_ILP_ISSU-3-SEND_FAILED |
3-Error |
Platform Inline Power ISSU client failed to send a negotiation message error [dec] |
Platform Inline Power ISSU client could not send a session negotiation\n\ message to the peer. When there is a problem in the\n\ negotiation the standby unit can not be brought up. |
platform-ha |
"show logging and show checkpoint client" |
|
NGWC_ILP_ISSU-3-SESSION |
3-Error |
Platform Inline Power ISSU client [chars] |
Platform Inline Power ISSU client observed an error during a session\n\ negotiation with the peer unit. When there is a problem\n\ with the session the standby unit can not be brought up. |
platform-ha |
"show issu capability entries <client_id> and\n\ show issu session <client_id> and\n\ show issu negotiated capability <session_id>" |
|
NGWC_ILP_ISSU-3-SESSION_UNREGISTRY |
3-Error |
Platform Inline Power ISSU client failed to unregister session information. Error: [dec] [chars] |
The Platform Inline Power ISSU client failed to unregister session information. |
platform-ha |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
NGWC_ILP_ISSU-3-TRANSFORM |
3-Error |
Platform Inline Power ISSU client [chars] transform failed error [chars] |
Platform Inline Power ISSU client could not transform the message.\n\ If the transmit transformation failed it means that the\n\ checkpoint message can not be sent to the standby unit.\n\ If the receive transformation failed it means that the\n\ checkpoint message can not be applied on the standby\n\ unit. In both cases the Platform Inline Power state will not\n\ be indentical with the active unit. |
platform-ha |
"show issu session <client_id> and\n\ show issu negotiated version <session_id>" |
|
NGWC_OBFL-5-DISABLED |
5-Notice |
[chars] Onboard Failure Logging disabled on switch [dec] |
Onboard Failure Logging has been disabled |
obfl |
LOG_STD_NO_ACTION |
|
NGWC_SWITCH_OOR-3-RP_CRITICAL_CPU_UTILIZATION |
3-Error |
Alarm: Critical CPU utilization over [dec]%% system may fail. |
Switch may fail due to extremely high CPU utilization. |
polaris-platform |
"Try to lower the CPU load" |
|
NGWC_SWITCH_OOR-3-RP_CRITICAL_MEM_UTILIZATION |
3-Error |
Alarm: Critical memory utilization over [dec]%% system may fail. |
Switch may fail due to extremely high memory utilization. |
polaris-platform |
"Try to lower the memory load" |
|
NGWC_SWITCH_OOR-3-RP_HIGH_CPU_UTILIZATION |
3-Error |
High CPU utilization over [dec]%% system performance may be degraded. |
Switch performance may be degraded due to high CPU utilization. |
polaris-platform |
"Try to lower the CPU load" |
|
NGWC_SWITCH_OOR-3-RP_HIGH_MEM_UTILIZATION |
3-Error |
Warning: Memory utilization over [dec]%% system performance may be degraded. |
Switch performance may be degraded due to high memory utilization. |
polaris-platform |
"Try to lower the memory load" |
|
NGWC_SWITCH_OOR-3-RP_NORMAL_CPU_UTILIZATION |
3-Error |
Normal CPU utilization under [dec]%% system is normal. |
CPU utilization is in normal range. |
polaris-platform |
LOG_STD_NO_ACTION |
|
NGWC_SWITCH_OOR-3-RP_NORMAL_MEM_UTILIZATION |
3-Error |
Normal memory utilization under [dec]%% system is normal. |
Memory utilization is in normal range. |
polaris-platform |
LOG_STD_NO_ACTION |
|
NGWC_USB_CONSOLE-3-NO_DNLD |
3-Error |
Switch [dec]: Firmware download failed |
USB Console firmware download failed. There will be no USB console connectivity. |
firmware |
"Please re-execute the command to download the firmware." LOG_STD_RECUR_ACTION |
|
NGWC_USB_CONSOLE-5-RUNNING_DNLD |
5-Notice |
Switch [dec]: Firmware download already in progress |
Only one download may be running at a time |
- |
"Wait for the original download to complete " "and print a status message" |
|
NGWC_USB_CONSOLE-6-CONFIG_DISABLE |
6-Information |
Switch [dec]: Console media-type forced to RJ45 |
Console media type is forced to RJ45 by system configuration. |
- |
"No action is necessary" |
|
NGWC_USB_CONSOLE-6-CONFIG_ENABLE |
6-Information |
Switch [dec]: Console media-type changed to default |
Media type change requested was invalid |
- |
LOG_STD_NO_ACTION |
|
NGWC_USB_CONSOLE-6-INACTIVITY_DISABLE |
6-Information |
Switch [dec]: Console media-type USB inactivity timeout disabled |
Console media type is forced to RJ45 by system configuration. |
- |
"No action is necessary" |
|
NGWC_USB_CONSOLE-6-INACTIVITY_ENABLE |
6-Information |
Switch [dec]: Console media-type USB configured for inactivity timeout of [dec] minutes |
Console media type is forced to RJ45 by system configuration. |
- |
"No action is necessary" |
|
NGWC_USB_CONSOLE-6-INACTIVITY_REACHED |
6-Information |
Switch [dec]: Console media-type USB disabled due to inactivity media-type reverted to RJ45. |
Console media type is forced to RJ45 by system configuration. |
- |
"No action is necessary" |
|
NGWC_USB_CONSOLE-6-MEDIA_RJ45 |
6-Information |
Switch [dec]: Console media-type is RJ45. |
The USB console is not active. |
- |
"No action is necessary" |
|
NGWC_USB_CONSOLE-6-MEDIA_USB |
6-Information |
Switch [dec]: Console media-type is USB. |
The USB console is currently active. |
- |
"No action is necessary" |
|
NGWC_USB_CONSOLE-6-OK_DNLD |
6-Information |
Switch [dec]: Firmware download successful |
This is for information purposes only. The download is successful and no action needs to be taken. |
firmware |
LOG_STD_NO_ACTION |
|
NGWC_USB_CONSOLE-6-USB_INSERT |
6-Information |
Switch [dec]: USB cable inserted. Console media-type USB is in effect |
USB console cable inserted |
- |
LOG_STD_NO_ACTION |
|
NGWC_USB_CONSOLE-6-USB_REMOVE |
6-Information |
Switch [dec]: USB cable removed. Console media-type RJ45 is in effect |
USB console cable inserted |
- |
LOG_STD_NO_ACTION |
|
NHRP-3-CACHE_FAILURE |
3-Error |
Failed to cache [chars] packet - [chars][dec] |
Caching of information from NHRP packet failed. |
nhrp |
LOG_STD_ACTION |
|
NHRP-3-PAKERROR |
3-Error |
Received [chars] from [chars] code: [chars][dec] trigger src: [chars] |
Received an error notification packet indicating that the last packet the system sent was bad or not understood by the recipient. |
nhrp |
LOG_STD_ACTION |
|
NHRP-3-PAKREPLY |
3-Error |
Receive [chars] packet with error - [chars][dec] |
An NHS rejects or fails to serve our request packet. |
nhrp |
LOG_STD_ACTION |
|
NHRP-3-QOS_POLICY_APPLY_FAILED |
3-Error |
Failed to apply QoS policy [chars] mapped to NHRP group [chars] on interface [chars] to tunnel [chars] due to [chars] |
The application of QoS policy to tunnel failed. The failure could be due to internal error or policy installation failure. Policy installation can fail if the policy configuration is not supported for a tunnel. |
nhrp |
LOG_STD_ACTION |
|
NHRP-3-TIMERLOOP |
3-Error |
Timer process looping [dec]/[dec]/[dec]/[dec]/[dec]/[dec]. |
- |
- |
- |
|
NHRP-3-TRACE_ILLEGAL_EVENT |
3-Error |
[chars] |
nhrp trace event type is invalid |
nhrp |
LOG_STD_ACTION |
|
NHRP-4-MAX_RECURSIVE_ROUTE_DEPTH_REACHED |
4-Warning |
Route lookup failed reached maximum recursive depth [dec] |
The ECMP recursive look up reached the maximum depth |
nhrp |
LOG_STD_ACTION |
|
NHRP-4-NHRP_ROUTER_AF_IMPORT |
4-Warning |
BGP AS specified in router nhrp import config is not running or not configured yet. Configuring router bgp with AS number [dec] |
BGP AS number specified in import command of NHRP is not yet configured |
nhrp |
LOG_STD_ACTION |
|
NHRP-4-QUOTA |
4-Warning |
Max-send quota of [dec]pkts/[dec]Sec. exceeded on [chars]. |
Quota for sending NHRP packets on the interface exceeds the limit. |
nhrp |
LOG_STD_ACTION |
|
NHRP-5-NHOP_UNREACHABLE |
5-Notice |
Nexthop address [chars] for [chars]/%lu is not routable |
The nexthop address for a shortcut is not routable |
nhrp |
"If this is not a transient routing change check the" " routing design/config to make sure that the nexthop" " corresponding to the shortcut has a covering route!" |
|
NHRP-5-NO_ROUTE |
5-Notice |
Not installing NHO for [chars]/[dec] due to the presence of an authoritatively learnt nexthop [chars] on [chars] |
NHO was not installed because of an already existing route entry |
nhrp |
LOG_STD_ACTION |
|
NHRPSNMP-3-TREEINVALID |
3-Error |
Setting tree to Invalid State @ - [dec] |
NHRP SNMP agent tree is not behaving as excepted. |
nhrp |
LOG_STD_ACTION |
|
NHRPSNMP-5-TREERECOVERD |
5-Notice |
Tree recovered fromInvalid State @ - [dec] |
NHRP SNMP agent tree is not behaving as excepted. |
nhrp |
LOG_STD_ACTION |
|
NICKEL10G-3-N10GERRD |
3-Error |
[chars]: [chars] - [dec] |
Nickel10g non-fatal generic error |
ubr10k-sw |
"LOG_STD_ACTION" |
|
NICKEL10G-3-N10GERRDD |
3-Error |
[chars]: [chars] - [dec] [dec] |
Nickel10g non-fatal error |
ubr10k-sw |
"LOG_STD_ACTION" |
|
NICKEL10G-3-N10GERREVT |
3-Error |
[chars] - ERR EVENT [chars] port [dec] |
Non fatal errors occured on Nickel10g |
ubr10k-sw |
"LOG_STD_ACTION" |
|
NICKEL10G-3-N10GERRS |
3-Error |
[chars] |
Nickel10g non-fatal generic error |
ubr10k-sw |
"LOG_STD_ACTION" |
|
NICKEL10G-3-N10GERRSEND |
3-Error |
[chars] - ERR EVENT [chars] port [dec] reporting to PRE |
Fatal errors occured on Nickel10g reported to PRE |
ubr10k-sw |
"LOG_STD_ACTION" |
|
NICKEL10G-3-N10GERRSSUSPEND |
3-Error |
Too many Nickel10g ERR EVENTS [dec] suspending reporting |
Too many errors reported on Nickel10g |
ubr10k-sw |
"LOG_STD_ACTION" |
|
NICKEL10G-3-N10GFIBNR |
3-Error |
FIB is not Running reporting it to PRE |
FIB is not in RUNNING state report to PRE for further action |
ubr10k-sw |
"LOG_STD_ACTION" |
|
NICKEL10G-3-N10GINVIRB |
3-Error |
[chars] |
Invalid Ironbus mode [dec] defaulting to QUAD |
ubr10k-sw |
"LOG_STD_ACTION" |
|
NICKEL10G-3-N10GNOTUP |
3-Error |
N10G is not operationally up |
Nickel10g is not operationally up |
ubr10k-sw |
"LOG_STD_ACTION" |
|
NICKEL10G-3-N10GPREMISMATCH |
3-Error |
PRE-A/B mismatch in N10G - driver:[dec] fpga:[dec] |
PRE-A/B mismatch in N10G driver |
ubr10k-sw |
"LOG_STD_ACTION" |
|
NICKEL10G-3-N10GSPIFAIL |
3-Error |
N10G-Waxbill SPI link is out of sync |
- |
ubr10k-sw |
"LOG_STD_ACTION" |
|
NILE_ASIC-2-BIT_INTR_INITIATOR_ABORT |
2-Critical |
PCI device [dec] failing to initiate |
The system detected initiation errors. If the error persists reload the hardware. If the box is stuck in this state replace the hardware. |
hardware |
"Reload switch." |
|
NILE_ASIC-2-BIT_INTR_PCI_INITIATOR_FATAL_ERROR |
2-Critical |
PCI device [dec] received fatal errors on initiation |
The system detected initiation errors. If the error persists reload the hardware. If the box is stuck in this state replace the hardware. |
hardware |
"Reload switch." |
|
NILE_ASIC-2-BIT_INTR_PCI_INITIATOR_PARITY_ERROR |
2-Critical |
PCI device [dec] received parity errors |
The system is receiving corrupted packets on PCI device. This could be due to improper NILE ASIC access. If the box is stuck in this state reload the hardware. |
me360x-me380x-system |
"Reload switch." |
|
NILE_ASIC-2-BIT_INTR_TX_ERROR |
2-Critical |
PCI device [dec] receiving TX Interrrupt Errors |
The system detected errors while responding to interrupts on the PCI device. This can result in erroneous behaviour. If the error persists reload the hardware. |
me360x-me380x-system |
"Reload switch." |
|
NILE_ASIC-2-BIT_INTR_TX_TRANSFER_INT |
2-Critical |
PCI device [dec] receiving TX transfer interrupt errors |
The system detected errors while transferring in the tx direction on the PCI device. This can result in erroneous behaviour. If the error persits reload the hardware |
me360x-me380x-system |
"Reload switch." |
|
NILE_ASIC-2-TCAM_PARITY_ARRAY_ERR |
2-Critical |
TCAM4 Parity Array Error at Asic: [dec] TCAM Index: 0x[hec] Application: [chars] Region [chars] |
The system detected a parity error in the TCAM4 and the entry was invalidated. This will result in unexpected traffic forwarding behavior. |
hardware |
"Reload switch." |
|
NILE_ASIC-2-TCAM_PARITY_IO_ERR |
2-Critical |
TCAM4 Parity IO Error at Asic: [dec] |
The system detected a parity error in the TCAM4 IO. This will result in unexpected traffic forwarding behavior. |
hardware |
"Reload switch." |
|
NILE_ASIC-2-TCAM_PHASE_ERR |
2-Critical |
TCAM4 Phase Error Detected at Asic: [dec]. |
The system detected a phase error in the TCAM4. This is considered a fatal error. |
hardware |
"Reload switch." |
|
NILE_PTP-3-MSGDISPATCH |
3-Error |
Unable to dispatch received IPC message from PTP daemon |
An unexpected condition has occurred while IOS was trying to dispatch a IPC message received from PTP daemon. |
me3600-ptp |
LOG_STD_ACTION |
|
NILE_PTP-3-MSGINITFAIL |
3-Error |
Failed to initalize required PTP resource: [chars] |
During the initialization of the resources required by PTP a failure occured. This has prevented PTP from being activated. |
me3600-ptp |
LOG_STD_ACTION |
|
NILE_PTP-3-SP_STATUS_UPDATE |
3-Error |
PTP is down as PTP processor is rebooting |
PTP is down as Sideband processor is rebooting. Saved PTP configuration will be applied again once SP is up. |
me3600-ptp |
LOG_STD_NO_ACTION |
|
NIM-2-BADNIMREV |
2-Critical |
Unsupported version of [chars] NIM in slot [dec] Version 0x[hec]\n |
- |
- |
"Upgrade the NIM to the proper level." |
|
NIM-2-BADSLOT |
2-Critical |
Illegal reference to non-existent slot [dec]\n |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
NIM-2-BADSUBUNIT |
2-Critical |
Illegal reference to non-existent subunit [dec] in slot [dec]\n |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
NIM-2-DEADICHAINQ |
2-Critical |
Attempted to manipulate uninitialized ichainQ in [chars]\n |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
NIM-2-LOSTICHAINQ |
2-Critical |
Couldn't find idb 0x[hec] in ichainQ in [chars]\n |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
NIM-2-NOHWADDRESS |
2-Critical |
All hardware addresses have been allocated - maximum of [dec]\n |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
NIM-2-UNSUPNIM |
2-Critical |
Unsupported [chars] NIM in slot [dec]\n |
The indicated NIM is not supported on this platform. |
- |
"Remove the NIM." |
|
NOEVENT-3-TENSRFSM |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
NOMEM-2-MPLS_TE_EXT_FWDG |
2-Critical |
ERRMSG_NOFLAGS |
- |
- |
- |
|
NOMEMORY-2-MPLS_TE_SYS |
2-Critical |
ERRMSG_NOFLAGS |
- |
- |
- |
|
NOPROCID-3-TENSRFSM |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
NOTIFY_BUFFER-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
NP_BS-2-THREE_NP108_NOT_PRESENT |
2-Critical |
DFC in slot [dec] does not have three NP108s! |
DFC does not have three NP108s which is an illegal configuration |
- |
LOG_STD_ACTION |
|
NP_BS-3-CRC_FAIL |
3-Error |
NextPort Module [dec]/[dec]/[dec] failed firmware image validation |
NextPort BootStrap and Crash Monitor detected an a failed NextPort firmware CRC validation |
- |
LOG_STD_ACTION |
|
NP_BS-3-INITSYS |
3-Error |
[chars] |
Failed NextPort BootStrap and Crash Monitor Initialization. |
- |
LOG_STD_ACTION |
|
NP_BS-3-INVALID_FW |
3-Error |
Invalid NextPort Firmware for [dec]/[dec]/[dec] |
NextPort BootStrap and Crash Monitor detected an invalid NextPort firmware |
- |
LOG_STD_ACTION |
|
NP_BS-3-INVALID_IDT |
3-Error |
NextPort Module [dec]/[dec]/[dec] detected an invalid IDT |
NextPort BootStrap and Crash Monitor detected an invalid IDT |
- |
LOG_STD_ACTION |
|
NP_BS-3-INVALID_MC_POST |
3-Error |
NextPort Module [dec]/[dec]/[dec] detected a module POST failure 0x[hec] |
NextPort BootStrap and Crash Monitor detected an a module POST failure |
- |
LOG_STD_ACTION |
|
NP_BS-3-MEM_TEST_FAIL |
3-Error |
NextPort Module [dec]/[dec]/[dec] memory test failed |
NextPort BootStrap and Crash Monitor detected a failed NextPort module memory test |
- |
LOG_STD_ACTION |
|
NP_BS-3-MODULE_ACCESS_ERR |
3-Error |
Failed to access NextPort module [dec]/[dec]/[dec] crash info |
NextPort BootStrap and Crash Monitor failed to access\n\ crash information |
- |
LOG_STD_NO_ACTION |
|
NP_BS-3-NO_KEEPALIVE |
3-Error |
NextPort module [dec]/[dec]/[dec] failed to respond to keepalive message |
NextPort BootStrap and Crash Monitor detected a module failed to\n\ respond to keepalive message |
- |
LOG_STD_NO_ACTION |
|
NP_BS-3-NO_SUCH_MODULE |
3-Error |
[chars] nonexisting NP module [dec]/[dec]/[dec] |
NextPort BootStrap and Crash Monitor detected an internal database error |
- |
LOG_STD_NO_ACTION |
|
NP_BS-3-NOMEM |
3-Error |
[chars] |
NextPort BootStrap and Crash Monitor Could not allocate memory \n\ for internal module database |
- |
LOG_STD_NO_ACTION |
|
NP_BS-3-NULL_FW_PTR |
3-Error |
NULL NextPort Firmware pointer for [dec]/[dec]/[dec] |
NextPort BootStrap and Crash Monitor detected a NULL NextPort firmware pointer |
- |
LOG_STD_ACTION |
|
NP_BS-3-Q_FAILURE |
3-Error |
NextPort Module [dec]/[dec]/[dec] control queue creation failure |
NextPort BootStrap and Crash Monitor detected an control queue creation failure |
- |
LOG_STD_ACTION |
|
NP_BS-6-MODULE_STARTED |
6-Information |
NextPort module [dec]/[dec]/[dec] Started - [dec].[dec].[dec].[dec] |
NextPort BootStrap and Crash Monitor successfully started module |
- |
LOG_STD_NO_ACTION |
|
NP_BS-6-MODULE_STOPPED |
6-Information |
NextPort module [dec]/[dec]/[dec] Stopped |
NextPort BootStrap and Crash Monitor stopped module |
- |
LOG_STD_NO_ACTION |
|
NP_CLIENT-2-FATAL |
2-Critical |
NP Client [chars] : [chars] [dec] [dec] |
NP Client software detected a critical programming error. |
SIP2_CLIENT_DDTS_COMP |
"Record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
NP_CLIENT-3-ALLEXISTS |
3-Error |
NP Client Previously Defined Software Element - [chars]: [chars] [chars] |
The NP Client has detected a previously defined software element. |
SIP2_CLIENT_DDTS_COMP |
"Try to reload the IOS image on the affected \n\ card or platform.\n\ If the error persists record the output\n\ from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
NP_CLIENT-3-INITFAIL |
3-Error |
NP Client Initialization Failed - [chars]: [chars] [chars] |
NP Client could not initialize memory\n\ needed to service one or more Network Processors. |
SIP2_CLIENT_DDTS_COMP |
"This error may indicate that an incompatibility exists\n\ between the NP firmware and the associate IOS image.\n\ \n\ Try to reload the IOS image on the affected \n\ card or platform.\n\ If the error persists record the output\n\ from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
NP_CLIENT-3-INTF |
3-Error |
[chars] [chars] on [chars] - [chars] if_number=[dec] |
Interface NP Client detected an error. |
SIP2_CLIENT_DDTS_COMP |
"Record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
NP_CLIENT-3-MAXEXCEED |
3-Error |
NP Client Max Services Exceeded - [chars]: [chars] [chars] |
The maximum number NP Client services have been exceeded. |
SIP2_CLIENT_DDTS_COMP |
"Change the configuration to reduce the number of services configured.\n\ \n\ If the error persists record the output\n\ from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
NP_CLIENT-3-METADATA |
3-Error |
[chars] failed: [chars] [[chars]] [chars] |
Processing of the Metadata for the specified Network\n\ Processor failed. The specified Network Processor will \n\ fail to operate. |
SIP2_CLIENT_DDTS_COMP |
"Try to reload the Network Processor microcode.\n\ If the error persists record the output\n\ from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
NP_CLIENT-3-NOMEM |
3-Error |
Memory Allocation Failure - [chars]: [chars] [chars] |
NP Client could not allocate required memory\n\ needed to service one or more Network Processors. |
SIP2_CLIENT_DDTS_COMP |
"This error may indicate that more memory \n\ must be installed on the affected card \n\ or platform in order to service all the\n\ features and related entities enabled via \n\ the configuration.\n\ \n\ Try to reload the IOS image on the affected \n\ card or platform.\n\ If the error persists record the output\n\ from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
NP_CLIENT-3-NOTFOUND |
3-Error |
NP Client Software Element Not Found - [chars]: [chars] [chars] |
The NP Client could not locate a required software element. |
SIP2_CLIENT_DDTS_COMP |
"Try to reload the IOS image on the affected \n\ card or platform.\n\\n\ If the error persists record the output\n\ from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
NP_CLIENT-3-NOTSUP |
3-Error |
NP Client Feature Not Supported - [chars]: [chars] [chars] |
The NP Client does not support the specified feature. |
SIP2_CLIENT_DDTS_COMP |
"Verify that the correct IOS image is loaded on the affected \n\ card or platform for the configured features.\n\ If the error persists record the output\n\ from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
NP_CLIENT-3-NPUNKNOWN |
3-Error |
NP Client Unsupported NP - [chars]: [chars] [chars] |
NP Client detected an unsupported NP. |
SIP2_CLIENT_DDTS_COMP |
"Verify that the correct IOS image is loaded on the affected \n\ card or platform for the configured features.\n\ If the error persists record the output\n\ from the following commands:\n\\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
NP_CLIENT-3-UNEXPECTED |
3-Error |
NP Client Unexpected - [chars]: [chars] [chars] [dec] [dec] |
NP Client unexpected error condition. |
SIP2_CLIENT_DDTS_COMP |
"Record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
NP_EST-3-MSG_ERR |
3-Error |
[chars] |
EST detected an internal error |
- |
LOG_STD_NO_ACTION |
|
NP_EST-6-CTRL_NAK_RSP |
6-Information |
[chars] |
EST Control No-Acknowledge Notification is sent to IOS to convey additional debug data regarding a NAK that occurred on the Control Queue |
- |
LOG_STD_NO_ACTION |
|
NP_EST-6-DIAG_POST_NTF |
6-Information |
[chars] |
EST Diagnostic/POST Notification is sent to IOS to convey additional information about the power-on self-test or a diagnostic test result |
- |
LOG_STD_NO_ACTION |
|
NP_EST-6-RUNTIME_ERR_NTF |
6-Information |
[chars] |
EST Run-time Error Notification is sent to IOS to convey additional debug data that may help to identify the cause of the error |
- |
LOG_STD_NO_ACTION |
|
NP_MD-0-NO_MODULE_ELEMENTS |
0-Emergency |
Cannot bring up the module [dec]/[dec]/[dec] due to lack of module elements |
NextPort Modem Driver cannot allocate an important data structure called\n\ module element which is necessary to bring up the module. This should\n\ not normally happen and possibly indicates an error condition |
async_drivers |
LOG_STD_ACTION |
|
NP_MD-0-NO_SUCH_LINE |
0-Emergency |
Attempt to [chars] a data channel on the unexisting line [dec]/[dec] |
An internal software error occured that probably resulted in corrupted\n\ modem database |
as |
LOG_STD_ACTION |
|
NP_MD-0-NO_SUCH_MODEM |
0-Emergency |
Attempt to [chars] a data channel on the unexisting modem [dec]/[dec] |
An internal software error occured that probably resulted in corrupted\n\modem database |
as |
LOG_STD_ACTION |
|
NP_MD-0-NO_SUCH_SLOT |
0-Emergency |
Slot [dec] is not present in the system |
An internal software error occured that possibly resulted in corrupted\n\ slot database. |
as |
LOG_STD_ACTION |
|
NP_MD-0-NOHWIDBS |
0-Emergency |
Cannot allocate interface Async[dec]/%02d |
Allocation of interface structure failed. Either there is not\n\ enough memory or the maximum number of interfaces was exceeded |
as |
LOG_STD_ACTION |
|
NP_MD-0-NOMEMORY |
0-Emergency |
Cannot allocate [dec] bytes of memory for [chars] |
The system failed to allocate an important data structure due\n\ to the lack of memory |
as |
"show mem" |
|
NP_MD-0-NOPAKS |
0-Emergency |
TTY [chars]: Cannot allocate [chars] |
An important buffer cannot be allocated due to the shortage of packet\n\ memory. |
as |
LOG_STD_ACTION |
|
NP_MD-0-NOTTYS |
0-Emergency |
Cannot allocate TTY[dec] [dec]/%02d |
Allocation of TTY structure failed. Either there is not enough memory\n\ or the TTY number is too big |
as |
LOG_STD_ACTION |
|
NP_MD-0-SLOT_ALREADY_PRESENT |
0-Emergency |
Slot [dec] is already present in the system |
An internal software error occured that possibly resulted in corrupted\n\ slot database. |
as |
LOG_STD_ACTION |
|
NP_MD-1-UNKNOWN_ESCAPE_CHAR |
1-Alert |
TTY [chars]: Attempt to set an unknown special character type [dec] |
NextPort Modem Driver received a request for hardware detection of an\n\ unknown type of a special character due to an internal software error |
as |
LOG_STD_ACTION |
|
NP_MD-3-BADENCAP |
3-Error |
Unknown encapsulation [dec] on interface [chars] |
A software error occurred resulting in an unknown encapsulation\n\ type on the interface specified by the error message. |
as |
LOG_STD_ACTION |
|
NP_MD-3-CONTIGUOUS |
3-Error |
Contiguous packet sent for transmit |
A software error occurred resulting in an unexpected packet being\n\ set up for transmission and the packet was dropped by the NextPort \n\ Modem Driver |
as |
LOG_STD_RECUR_ACTION |
|
NP_MD-3-DATA_CHAN_RX_OVERFLOW |
3-Error |
Too many buffers [dec] rxd for port [dec] |
NextPort Module sent more buffers than is allowed for this channel |
as |
LOG_STD_ACTION |
|
NP_MD-3-DATA_QUEUE_SEND_FAIL |
3-Error |
Could not send to data queue for port [dec] inflight tx buffers [dec] |
NextPort Modem Driver could not send buffer to Interface driver |
as |
LOG_STD_ACTION |
|
NP_MD-3-MODEM_SLOT_CREATION_FAIL |
3-Error |
Modem slot structure for slot [dec] could not be created |
NextPort modem driver could not create the modem slot structure which is required for modem services of this card |
as |
LOG_STD_ACTION |
|
NP_MD-3-NO_SEED_BUFFER |
3-Error |
No buffer to seed data queue for module [dec]/[dec]/[dec] |
NextPort Modem Driver could not obtain a buffer whilst trying to\n\ seed the module data queue. Due to packet memory shortage |
as |
LOG_STD_ACTION |
|
NP_MD-3-NOTXPAK |
3-Error |
Static transmit paktype unavailable |
A software structure was found in an unexpected state during\n\ run-time for the indicated modem. |
as |
LOG_STD_ACTION |
|
NP_MD-3-NULL_PTR |
3-Error |
[chars] is NULL in [chars] for port [dec] |
Unexpected NULL pointer at specified location |
as |
LOG_STD_ACTION |
|
NP_MD-3-RETURN_DATA_BUFF_FAIL |
3-Error |
Failed to return data buffer for port [dec] |
Call to NextPort Interface Driver to replenish data buffer for this channel failed |
as |
LOG_STD_ACTION |
|
NP_MD-3-SEED_BUFFER_FAIL |
3-Error |
Could not seed data queue for module [dec]/[dec]/[dec] |
NextPort Modem Driver could not seed the data queue with buffers |
as |
LOG_STD_ACTION |
|
NP_MD-3-TX_INBAND_MSG_FAILURE |
3-Error |
Failed to send inband message for TTY [chars] |
Call to send inband message on data queue failed |
as |
LOG_STD_ACTION |
|
NP_MD-3-TXQUEUE_EMPTY |
3-Error |
TTY [chars]: No buffers available to set up the transmit queue |
A software error occurred resulting in an invalid state for the\n\ RTS modem signal |
as |
LOG_STD_ACTION |
|
NP_MD-3-UNKNOWN_INBAND |
3-Error |
TTY [chars]: Unknown NextPort in-band message msg_id %04x received |
NextPort Modem driver received an unknown message from a NextPort module.\n\This can happen if new firmware is used with an obsolete version of IOS |
as |
LOG_STD_ACTION |
|
NP_MD-6-MODULE_DOWN |
6-Information |
NextPort module [dec]/[dec]/[dec] down |
NextPort Modem Driver detected a module going down |
- |
LOG_STD_NO_ACTION |
|
NP_MD-6-MODULE_UP |
6-Information |
NextPort module [dec]/[dec]/[dec] up |
NextPort Modem Driver detected a module coming up |
- |
LOG_STD_NO_ACTION |
|
NP_MD-6-SLOT_INSERTED |
6-Information |
Slot [dec] [dec] ports max inserted |
NextPort Modem driver detected a slot being inserted in the system.\n\ During the startup all slots that are present in the system are treated\n\ as being inserted |
- |
LOG_STD_NO_ACTION |
|
NP_MD-6-SLOT_REMOVED |
6-Information |
Slot [dec] removed |
Slot has been removed from the system |
- |
LOG_STD_NO_ACTION |
|
NP_MM-3-COUNTRY_CODE_FAILURE |
3-Error |
Module country code failure [dec]/[dec]/[dec] |
NextPort Module Manager failed to set the country code |
- |
LOG_STD_ACTION |
|
NP_MM-3-DATA_Q_FAILED |
3-Error |
Failed to create Data Q for NP module [dec]/[dec]/[dec] |
NextPort Module Manager failed to create Data Queue |
- |
LOG_STD_ACTION |
|
NP_MM-3-INVALID_ACK_RSP |
3-Error |
Unsupported module ACK response [dec]/[dec]/[dec]: msg len = [dec] session ID = [dec] msg tag = [dec] msg ID = [dec] cmd msg ID = [dec] result code = [dec] |
NextPort Module Manager received an unsupported message response |
- |
LOG_STD_ACTION |
|
NP_MM-3-INVALID_NPADDRESS |
3-Error |
Invalid NP_ADDRESS [dec]/[dec]/[dec]/[dec] - [chars] |
NextPort Module Manager detected invalid NP_ADDRESS |
- |
LOG_STD_ACTION |
|
NP_MM-3-INVALID_RSP |
3-Error |
Unsupported module response [dec]/[dec]/[dec]: msg len = [dec] session ID = [dec] msg tag = [dec] msg ID = [dec] |
NextPort Module Manager received an unsupported message response |
- |
LOG_STD_ACTION |
|
NP_MM-3-INVALID_STATE |
3-Error |
Invalid NP module state[chars] [dec]/[dec]/[dec] - [chars] |
NextPort Module Manager detected invalid NP module state |
- |
LOG_STD_ACTION |
|
NP_MM-3-MEM_ERR |
3-Error |
Failed to allocate control message buffer for NP module [dec]/[dec]/[dec] - [chars] |
NextPort Module Manager failed to allocate control message buffer |
- |
LOG_STD_ACTION |
|
NP_MM-3-MODULE_CRASH |
3-Error |
Module Crash detected [dec]/[dec]/[dec]: state = [dec] cause code = [dec] |
NextPort Module Manager detected a crashed module |
- |
LOG_STD_ACTION |
|
NP_MM-3-RESTART_EXCEEDED |
3-Error |
Module exceeded restart threshold [dec]/[dec]/[dec] |
NextPort Module exceeded the restart threshold |
- |
LOG_STD_ACTION |
|
NP_MM-3-RUNTIME_ERR |
3-Error |
Module Run Time Error [dec]/[dec]/[dec] : recovery = 0x[hec] error = 0x[hec] |
NextPort Module Manager received a module run time error |
- |
LOG_STD_ACTION |
|
NP_MM-3-SEND_FAILED |
3-Error |
Failed to send [chars] message to NP module [dec]/[dec]/[dec] |
NextPort Module Manager failed to send control message |
- |
LOG_STD_ACTION |
|
NP_SIGLIB-3-CPTONE_FORMAT_FAIL |
3-Error |
Format of cp tone failed for tone-id [dec] port [dec]/[dec] |
Formatting of the call processing tone message to the nextport module\n\ failed |
- |
LOG_STD_ACTION |
|
NP_SPE_DS-3-NOMEMORY |
3-Error |
Cannot allocate [dec] bytes of memory for [chars] |
The system failed to allocate an important data structure due\n\ to the lack of memory |
- |
"show mem" |
|
NP_SPE_DS-3-SPE_DNLD_FAIL |
3-Error |
SPE [dec]/[dec]/[dec]/[dec]: [chars] |
SPE download code failed - download aborted |
- |
LOG_STD_NO_ACTION |
|
NP_SPE_DS-3-SPE_DNLD_INIT_FAIL |
3-Error |
[chars] |
SPE download code failed to initialise - SPE download will fail |
- |
LOG_STD_NO_ACTION |
|
NP_SSM-0-NOMEMORY |
0-Emergency |
Cannot allocate [dec] bytes of memory for [chars] |
The system failed to allocate an important data structure due\n\ to the lack of memory |
as |
"show mem" |
|
NP_SSM-3-INVALID_HANDLE |
3-Error |
SSM[dec]/[dec]: Invalid Session/Service Instance Handle |
Session and Service Manager Received failed to obtain its instance\n\ handle for the slot/port |
- |
LOG_STD_NO_ACTION |
|
NP_SSM-3-INVALID_MSG |
3-Error |
SSM: Invalid Session/Service Message ID = 0x[hec] |
Session and Service Manager Received an invalid message from the\n\ NextPort Message Dispatcher |
- |
LOG_STD_NO_ACTION |
|
NP_SSM-3-RUNTIME_ERROR |
3-Error |
SSM[dec]/[dec]: Session Runtime Error Code = [dec] Recovery Action = [dec] |
Session and Service Manager Received a Runtime Error for the slot\n\ and port |
- |
LOG_STD_NO_ACTION |
|
NP_SSM-6-NULL_SSM_INFO |
6-Information |
NULL SSM Info Handle for slot [dec] port [dec] |
NextPort Session and Service Manager failed to obtain a control information handle for the indicated slot and port numbers |
- |
LOG_STD_ACTION |
|
NP_SSM-6-NULL_VDEV_COMMON |
6-Information |
NULL Vdev Common Handle for slot [dec] port [dec] |
NextPort Session and Service Manager failed to obtain a Voice Device Information handle for the indicated slot and port numbers |
- |
LOG_STD_ACTION |
|
NP_UCODE-3-INVALID_FILE |
3-Error |
NP microcode [chars] for device [chars] is invalid [chars] |
The file containing the microcode for an NP is not specified\n\ or not accessible. This could be due to an invalid configuration\n\ or because the microcode is missing in this image. |
vsp-mid |
LOG_STD_SH_TECH_ACTION |
|
NP-3-CTRL_POOL_CREATION_FAIL |
3-Error |
Control buffer pool could not be created |
NextPort driver could not create the control buffer pool required for tx and rx of NP control messages |
as |
LOG_STD_ACTION |
|
NP-3-MODNOTEXIST |
3-Error |
Slot [dec] DFC [dec] Module [dec] not exist. |
No Virtual Console opens for this module. |
as |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
NP-3-NAKRSP |
3-Error |
NAK Response Received - command 0x[hec] result code 0x[hec] msg id 0x[hec] session id 0x[hec] msg tag 0x[hec] |
A NAK response was sent by the NextPort module. |
as |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
NP-3-NOTMSGID |
3-Error |
Message Id [hec] not supported. |
The Nextport does not supported this control message id. |
as |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
NP-3-QUEUEFULL |
3-Error |
[chars] queue is full for Slot [dec] DFC [dec] Module [dec]. |
TX queue is full for this module. |
as |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
NP-3-RESET_DFC |
3-Error |
DFC Reset-Cleared Failed - DFC [dec] |
DFC Reset-Cleared Failed |
as |
LOG_STD_ACTION |
|
NTI-3-AGENT_ERR |
3-Error |
[chars] Notifying platform about AGENT ERROR [chars] AGENT EP ID 0x[hec] for EP ID 0x[hec] EP type [chars] EP group [chars] |
An NTI AGENT error has occured |
nti |
LOG_STD_ACTION |
|
NTI-3-CLIENT_NOT_REGSTRD_FOR_EPTYPE |
3-Error |
[chars] Client #[dec] - [chars] has NOT registered for platform EP type [chars] |
A Client has not registered for a platform EP type |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_AGENT_LIST_ALLOC |
3-Error |
Failed to allocate agent bitlist for endpoint 0x[hec] |
NTI ISSU failed to allocate the agents bitlist for an endpoint. The endpoint will most likely be reset. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_DUMMY_MSG_FAILED |
3-Error |
Failed to send a dummy nego msg to endpoint 0x[hec] |
NTI ISSU failed to send a dummy negotiation message to trigger negotiation on the peer. The endpoint will most likely be reset. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_EXISTING_SESSION |
3-Error |
Session already exists for ep 0x[hec] |
NTI ISSU session already exists for endpoint. The endpoint will most likely be reset. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_INVALID_MEDMAN |
3-Error |
Invalid MEDMan data |
MEDMan Multiple Endpoint Data Manager data is invalid. The endpoint will most likely be reset. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_INVALID_MSG_TRANS |
3-Error |
NTI ISSU transformation function got an invalid message in argument |
NTI ISSU transformation function got an invalid message in argument. The message can't be transformed and won't be processed. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_INVALID_RC |
3-Error |
Invalid ISSU rc argument for endpoint 0x[hec] |
NTI ISSU got an invalid ISSU return code argument. ISSU negotiation will fail the endpoint will most likely be reset. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_INVALID_RCVD_MSG |
3-Error |
NTI ISSU received an invalid message for transformation from endpoint 0x[hec] |
NTI ISSU received an invalid message for transformation. The message can't be processed. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_INVALID_SESSION |
3-Error |
Invalid session for ep 0x[hec] |
NTI ISSU session is invalid for endpoint. The endpoint will most likely be reset. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_MEDMAN_CREATE |
3-Error |
Failed to create MEDMan data for endpoint 0x[hec] |
NTI ISSU failed to create MEDMan data for an endpoint. Negotiation can't be done the endpoint will most likely be reset. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_MEDMAN_GET |
3-Error |
Failed to get MEDMan data for endpoint 0x[hec] [chars] |
NTI ISSU failed to retreive MEDMan data for an endpoint. ISSU negotiation will failed with this endpoint and it will most likely be reset. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_MTU_FAILED |
3-Error |
NTI ISSU failed to get MTU for message type [dec] [chars] |
NTI ISSU failed to get the message MTU for transformation. The message can't be sent. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_NEGO_ALREADY_STARTED |
3-Error |
NTI ISSU negotiation already started endpoint 0x[hec] |
Tried to start the NTI ISSU negotiation but it started already. The endpoint will most likely be reset. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_NEGO_ASYNC_ERROR |
3-Error |
Async error during nego with 0x[hec] [chars] |
NTI ISSU got an asynchronous error during negotiation with an endpoint. The endpoint will most likely be reset. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_NEGO_INCOMPATIBLE |
3-Error |
Negotiation incompatible for endpoint 0x[hec] |
NTI ISSU was incompatible for this endpoint. The endpoint will most likely be reset. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_NOT_INIT |
3-Error |
NTI ISSU is not initialized endpoint 0x[hec]. |
NTI ISSU is not initialized. The endpoint will most likely be reset. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_PLATFORM_TRANSPORT_NEGO_GET_REQ_PAK |
3-Error |
NTI ISSU failed to get an platform transport nego message |
NTI ISSU failed to get an platform transort nego message. The endpoint will most likely be reset. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_PLATFORM_TRANSPORT_NEGO_SEND |
3-Error |
NTI ISSU failed to send an platform transport nego message to 0x[hec] |
NTI ISSU failed to send a negotiation message using the platform transport. The endpoint will most likely be reset. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_RCV_FAILED |
3-Error |
NTI ISSU failed to transform message type [dec] for receive from 0x[hec] [chars] |
NTI ISSU failed to transform the message for receive. The message can't be processed. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_RCVD_NEGO_NOT_DONE |
3-Error |
NTI ISSU negotiation not done when received a message from 0x[hec] |
NTI ISSU not done when received a message. The message can't be processed. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_RCVD_TRANS_FAILED |
3-Error |
NTI ISSU failed to transform received message from 0x[hec] |
NTI ISSU failed to transform a received message. The message can't be processed. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_RCVD_UNKNOWN_MSG |
3-Error |
NTI ISSU received an unknown message type [dec] from 0x[hec] |
NTI ISSU received a message whose type is unknown. The message can't be processed. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_REG_ADD |
3-Error |
NTI ISSU failed to hook to the registry [chars] |
NTI ISSU failed to hook to a registry. This endpoint will most likely be reset. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_REG_RECEIVE_NEGO_MSG |
3-Error |
NTI ISSU failed call the platform receive nego message registry |
NTI ISSU failed to NTI ISSU failed call the platform receive nego message registry. The endpoint will most likely be reset. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_TRIG_NEGO_NOT_DONE |
3-Error |
NTI ISSU negotiation not done when getting a trigger from 0x[hec] |
NTI ISSU negotiation should have been done when getting a trigger from this endpoint. The trigger will be ignored |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_UNKNOWN_MSG_TYPE |
3-Error |
NTI ISSU got an unknown message type: [dec] |
NTI ISSU got an unknown message type when trying to get the message MTU. The message can't be sent. |
nti |
LOG_STD_ACTION |
|
NTI-3-ISSU_XMIT_FAILED |
3-Error |
NTI ISSU failed to transform message type [dec] for transmit to 0x[hec] [chars] |
NTI ISSU failed to transform the message for transmit. The message can't be sent. |
nti |
LOG_STD_ACTION |
|
NTI-3-TRIG_ABORT_ALL_CLIENTS |
3-Error |
[chars] Aborting trigger processing for all clients as requested by the platform EP ID 0x[hec] trigger type [chars] trigger group [chars] |
Trigger processing has been aborted for all clients due to a platform request |
nti |
LOG_STD_ACTION |
|
NTI-3-TRIG_CLIENT_NOTINLIST |
3-Error |
[chars] Cannot trigger NTI client [dec] for this EP: could not find client |
Could not Trigger NTI Client for an EP as it is not in the list |
nti |
LOG_STD_ACTION |
|
NTI-3-TRIG_PROCESSING |
3-Error |
[chars] Trigger processing ERROR for client #[dec] - [chars] EP ID 0x[hec] trigger |
An NTI Trigger Processing Error has occured |
nti |
LOG_STD_ACTION |
|
NTP-4-PEERUNREACH |
4-Warning |
Peer [inet] is unreachable |
The NTP peer is unreachable. |
- |
"Check network connection to the peer and if NTP is running on the peer." |
|
NTP-4-UNSYNC |
4-Warning |
NTP sync is lost |
NTP synchronization to its peer is lost. |
- |
"Check network connection to the peer if NTP is running on the peer\n\ if the peer itself is synchronized to a stable time source and if NTP\n\ packets from the peer have passed validity tests specified in the\n\ RFC1305 etc." |
|
NTP-4-V6DISABLED |
4-Warning |
IPv6 is not running on interface [chars]. Cannot send NTP message. |
This informational message logs availability transitions in the Service Assurance Agent probes. This messages appears when the <CmdBold>ip sla logging trap<NoCmdBold> command is entered |
rsps-time-rptr |
"If this message is not necessary enter the " "<CmdBold>no ip sla logging trap<NoCmdBold> command to disable " "logging. Otherwise no action is required" |
|
NTP-5-PEERSYNC |
5-Notice |
NTP synced to peer [inet] |
NTP has synchronized the local clock to a new peer. |
- |
LOG_STD_NO_ACTION |
|
NTP-6-PEERREACH |
6-Information |
Peer [inet] is reachable |
The NTP peer is reachable. |
- |
LOG_STD_NO_ACTION |
|
NTP-6-RESTART |
6-Information |
NTP process starts |
NTP process has just started or re-started. |
- |
LOG_STD_NO_ACTION |
|
NTP-6-STOP |
6-Information |
NTP process stops |
NTP is disabled. |
- |
"Check if NTP is disabled by administrator purposely." |
|
NULLMACH-3-TENSRFSM |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
Null ssb for [chars] |
The hwidb subblock is NULL |
c7600-sip-200 |
"This is a internal software error. Decode the " "traceback and get the output of <CmdBold>show " "running-config<NoCmdBold>. Check Bug Toolkit " "before calling the TAC. When calling the TAC " "please provide the above information along with " "the output of <CmdBold>show running<NoCmdBold> " "and <CmdBold>show tech<NoCmdBold> details." |
- |
- |
|
NWPI_PROXY-2-IPC_INIT |
2-Critical |
IPC message handler registration failure rc [dec] |
Registering an IPC message handler for the NWPI feature failed. This will cause the feature to not function. |
NWPI_COMP_NAME |
"This is normally a software issue. " "The consequences are that the NWPI feature will not function. " LOG_STD_ACTION |
|
NWPI_PROXY-3-DOMAIN_MEM_EXTEND_FAILED |
3-Error |
QFP NWPI Proxy IPC Domain mem extend failed |
Extending memory failed. |
NWPI_COMP_NAME |
LOG_STD_ACTION |
|
NWPI_PROXY-3-DOMAIN_MEM_REQ_FAILED |
3-Error |
QFP NWPI Proxy IPC Domain mem req failed |
Requesting more memory failed. |
NWPI_COMP_NAME |
LOG_STD_ACTION |
|
NWPI_PROXY-3-IPC_ALLOC_FAILED |
3-Error |
CPP NWPI Proxy [chars] message lost due to message buffer allocation failure. |
Proxy internal software error. QFP NWPI Proxy message processing detected a message buffer allocation failure. The message is lost as the result of this condition. |
NWPI_COMP_NAME |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
NWPI_PROXY-3-IPC_NORES |
3-Error |
No space for the IPC reply size [dec] |
For a request from upper NWPI software stack layers it was not possible to allocate space for a reply for the specified size. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation. |
NWPI_COMP_NAME |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
NWPI_PROXY-3-IPC_OPEN_REPLY |
3-Error |
IPC Open Reply failed request [dec] |
For a request from upper NWPI software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation. |
NWPI_COMP_NAME |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
NWPI_PROXY-3-IPC_SEND_FAILED |
3-Error |
QFP NWPI Proxy [chars] message lost due to message sent failure result: [dec]. |
Cisco internal software error. QFP NWPI Proxy message processing detected a message sent failure. The message is lost as the result of this condition. |
NWPI_COMP_NAME |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
NWPI_PROXY-4-INVALID_MSG_LEN |
4-Warning |
QFP NPWI Proxy IPC invalid length [dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Cisco internal software error. QFP NPWI Proxy received invalid IPC message length from control plane. This message will be ignored. |
NWPI_COMP_NAME |
LOG_STD_ACTION |
|
OBFL_ERRMSG-5-FILECREATEFAIL |
5-Notice |
OBFL [chars] App failed to open/create file [chars] . Errno = [dec] |
The file O_CREATE operation failed |
obfl |
LOG_STD_NO_ACTION |
|
OBFL_ERRMSG-5-FILEFSTATFAIL |
5-Notice |
OBFL [chars] App failed to fstat file [chars] . Errno = [dec] |
The file fstat operation failed |
obfl |
LOG_STD_NO_ACTION |
|
OBFL_ERRMSG-5-FILELSEEKFAIL |
5-Notice |
OBFL [chars] App failed to Lseek file [chars] . Errno = [dec] |
The file lseek operation failed |
obfl |
LOG_STD_NO_ACTION |
|
OBFL_ERRMSG-5-FILEMINFREEFAIL |
5-Notice |
OBFL [chars] App failed to set coalesce min free |
Failed to set coalese min free value |
obfl |
LOG_STD_NO_ACTION |
|
OBFL_ERRMSG-5-FILEOPENFAIL |
5-Notice |
OBFL [chars] App failed to open file [chars] . Errno = [dec] |
The file open operation failed |
obfl |
LOG_STD_NO_ACTION |
|
OBFL_ERRMSG-5-FILEREADFAIL |
5-Notice |
OBFL [chars] App read failure on file [chars] . Errno = [dec] |
The file read operation failed |
obfl |
LOG_STD_NO_ACTION |
|
OBFL_ERRMSG-5-HISTFILESMALL |
5-Notice |
OBFL [chars] App: history file is exceedingly small |
The history file for this app has been detected to be very small |
obfl |
LOG_STD_NO_ACTION |
|
OBFL-3-BFLASHINITERR |
3-Error |
Failed to initialize the PRE5 OBFL storage device. |
PRE5 OBFL storage device init failed. |
cr10k5 |
LOG_STD_ACTION |
|
OBFL-5-DISABLED |
5-Notice |
Onboard Failure Logging disabled |
Onboard Failure Logging has been disabled |
obfl |
LOG_STD_NO_ACTION |
|
OBFL-6-OBFLSENSORACCESS |
6-Information |
PRE5 OBFL: [chars] sensor access failure for sensor [chars]ID:[dec] |
- |
- |
- |
|
OBFL-6-OBFLSTORAGECCESS |
6-Information |
PRE5 OBFL: [chars] operation on OBFL storage failed OBFL address: 0x%X num bytes: [dec] |
PRE5 OBFL flash access error. |
cr10k5 |
LOG_STD_ACTION |
|
OBJGROUP-3-CLASSMAP |
3-Error |
Failed to perform classmap filter [chars] operation |
Operation to modify classmap filter has failed. |
asr1k-cts |
LOG_STD_ACTION |
|
OBJGROUP-3-CREATEFAIL |
3-Error |
Failed to create/initialize internal data structures |
Operation to create/initialize internal data structures has failed. |
asr1k-cts |
LOG_STD_ACTION |
|
OBJGROUP-3-QFAIL |
3-Error |
Failed to perform queue operation '[chars]' |
Operation to perform processing on internal queue has failed. |
asr1k-cts |
LOG_STD_ACTION |
|
OBJGROUP-4-BADCHILD |
4-Warning |
Object-group '[chars]' has bad child '[chars]' |
Object-group has reference to invalid child object-group |
asr1k-cts |
LOG_STD_ACTION |
|
OBJGROUP-4-BADCLASSMAP |
4-Warning |
Internal match structure points to invalid class-map '[chars]' |
Object-group has reference to invalid child object-group |
asr1k-cts |
LOG_STD_ACTION |
|
OBJGROUP-4-BADMATCH |
4-Warning |
Invalid internal match structure in class-map '[chars]' type [dec] |
Object-group has reference to invalid match |
asr1k-cts |
LOG_STD_ACTION |
|
OBJGROUP-4-BADOG |
4-Warning |
Reference to non-existent object-group '[chars]' |
Internal structure references non-existent object-group |
asr1k-cts |
LOG_STD_ACTION |
|
OBJGROUP-4-BADREFCNT |
4-Warning |
Bad reference counter classmap '[chars]' sgtid [dec] filter [dec] |
Reference counter value indicates database inconsistency. |
asr1k-cts |
LOG_STD_ACTION |
|
OBJGROUP-4-EINVAL |
4-Warning |
Unexpected input value |
An unexpected input value to a function was incorrect |
asr1k-cts |
LOG_STD_ACTION |
|
OBJGROUP-4-INVALIDCMD |
4-Warning |
Invalid subcommand [dec] |
Attempt to configure invalid subcommand |
asr1k-cts |
LOG_STD_ACTION |
|
OBJGROUP-4-INVALIDFILTER |
4-Warning |
Invalid filter type [dec] for classmap '[chars]' |
Filter type for match statement was unknown/invalid. |
asr1k-cts |
LOG_STD_ACTION |
|
OBJGROUP-4-TOOMANYEXPOG |
4-Warning |
ACL '[chars]' expansion will exceed Maximum Expanded ACEs %lu/%lu |
Local domain pattern length cannot exceed 100 for DSA. |
xe-opendns-conn |
"This message is for informational purposed only" |
|
OBJGROUP-4-TOOMANYSGT |
4-Warning |
Exceeded maximum allowed SGT's [dec] in a class-map group-object |
The cumulative number of SGTs in a class-map match statement has exceeded the maximum allowed. The number of SGTs includes those in object-groups as well as child object-groups within the heirarchy. |
asr1k-cts |
"Limit the number of SGTs in the object-group " "heirarchy referenced by the class-map match " "statement" |
|
OC3/STM1 [dec]/[dec] [chars] allocation failure |
CHOCX controller or channel memory allocation failure |
c7600-sip-200 |
"This is a internal software error. Decode the " "traceback. Enable <CmdBold>debug hw-module subslot " "<slot>/<bay> oir plugin<NoCmdBold> when the problem " "is happening. Check Bug Toolkit before calling the " "TAC. When calling the TAC please provide the above" "information along with output of <CmdBold>show " "logging<NoCmdBold> and the output of <CmdBold>show " "tech<NoCmdBold> details." |
- |
- |
|
OCE_FORWARDING-2-CAUSE_FRR_BACKUP_LABEL_ERR |
2-Critical |
FRR OCE node protection error no backup label |
No backup label available for FRR when node protection is invoked |
cpp-ucode |
LOG_STD_ACTION |
|
OCE_FORWARDING-2-CAUSE_FRR_STATE_ERR |
2-Critical |
Illegal FRR OCE state - FRR OCE state = [dec] |
Invalid FRR OCE state |
cpp-ucode |
LOG_STD_ACTION |
|
OCE_FORWARDING-2-CAUSE_ILLEGAL_OBJ_ERR |
2-Critical |
ILLEGAL OCE - unexpected oce |
This object should not be seen by the forwarding code |
cpp-ucode |
LOG_STD_ACTION |
|
OCE_FORWARDING-2-CAUSE_OCE_LINKTYPE_ERR |
2-Critical |
LINKTYPE ERROR OCE - Linktype error in oce |
Link type not supported in OCE |
cpp-ucode |
LOG_STD_ACTION |
|
OCE_FORWARDING-3-CAUSE_IPV6_ERR |
3-Error |
IPv6 not supported dropping packet |
IPV6 over MPLS not supported |
cpp-ucode |
LOG_STD_ACTION |
|
OCE_FORWARDING-3-CAUSE_OCE_ADJ_ID |
3-Error |
hash table not initialized |
OCE adjacency id handle hash table not initialized |
cpp-ucode |
LOG_STD_ACTION |
|
OCE_FORWARDING-3-CAUSE_OCE_BUNDLE_ERR |
3-Error |
OCE Bundle unsupported link error [chars] 0x%X |
A request exceeded the feature invocation call stack |
cpp-ucode |
LOG_STD_ACTION |
|
OCE_FORWARDING-3-CAUSE_OCE_CHAIN_ERR |
3-Error |
OCE chain error dropping packet |
OCE chain pointer contain an error |
cpp-ucode |
LOG_STD_ACTION |
|
OCE_FORWARDING-3-CAUSE_OCE_CHOICE_ERR |
3-Error |
OCE Choice unsupported link error [chars] 0x%X |
OCE Choice unsupported link error |
cpp-ucode |
LOG_STD_ACTION |
|
OCE_FORWARDING-3-CAUSE_OCE_COUNTER_EXCEED_STACK |
3-Error |
OCE counter stack exceed |
OCE counter exceed the allocated stack size |
cpp-ucode |
LOG_STD_ACTION |
|
OCE_FORWARDING-3-CAUSE_OCE_INJECT_ADJ |
3-Error |
unexpected subtype |
OCE adjacency id - unknown fixup subtype |
cpp-ucode |
LOG_STD_ACTION |
|
OCE_PUNT_PROCESS-3-LABEL_CACHE_INVALID |
3-Error |
[chars] |
MPLS label cache was invalid failed to handle exception |
mpls-mfi |
LOG_STD_ACTION |
|
OCE_PUNT_PROCESS-3-NORESOURCE |
3-Error |
[chars] [dec] |
Resource Failure: [chars] [dec] |
mpls-mfi |
LOG_STD_ACTION |
|
OCE-3-DECREASE_ZERO_REFCOUNT |
3-Error |
Try to decrease zero refcount for [chars] oce %p |
Attempt to decrease the refcount of oce when it is already zero |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
OCE-3-EXCEED_OCE_COUNTER_LIMIT |
3-Error |
Exceeded OCE push counter limit functs:%p counter:%p |
- |
- |
- |
|
OCE-3-GENERAL |
3-Error |
[chars] |
An internal software error occurred. |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
OCE-3-INTERRUPT_LEVEL_LAST_LOCK |
3-Error |
Try to remove last lock for [chars] oce %p at interrupt |
Attempt to delete oce while not at process level |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
OCE-3-LOOP |
3-Error |
A loop in the OCE chain has been detected at: [chars][%p] |
A loop in the OCE chain has been detected |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
OCE-3-MISSING_HANDLER_FOR_SW_OBJ |
3-Error |
Missing handler for '[chars]' function |
An internal API request has been ignored because it was unexpected |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
OCE-3-MISSING_HANDLER_FOR_SW_OBJ_TYPE |
3-Error |
Missing handler for '[chars]' function for type [chars] |
An internal API request has been ignored because it was unexpected |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
OCE-3-OCE_CHANGED_BY_APPLY_FUNCTION |
3-Error |
Target OCE %p changed to %p by apply function %p |
An internal disposition counter measure request has been ignored because it was unexpected |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
OCE-3-OCE_SET_WRONG_PATH |
3-Error |
Attempting to add an oce to the set contributed by path/list %p/%p while set set belongs to %p |
Failed to enqueue a unlock for an oce this may lead to a memory leak |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
OCE-3-OCEDEPDUMP |
3-Error |
[chars] |
An error condition triggered display of oce dependents |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
OCE-3-QUEUE_UNLOCK |
3-Error |
Failed to [chars] unlock[chars] for [chars] oce %p |
Failed to enqueue a unlock for an oce this may lead to a memory leak |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
OCE-3-UNINITIALIZED_VECTOR |
3-Error |
Improperly initialized [chars] vector in [chars] OCE bundle %p packet dropped |
An OCE bundle vector was improperly initialized |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
ODB-3-ODB_INTERNAL_ERR |
3-Error |
[chars] |
ODB_INT_ERR_EXPLANATION |
ribinfra |
LOG_STD_RECUR_ACTION |
|
ODM-3-CPU_TEST_FAIL |
3-Error |
CPU card[chars] [chars] Failed |
Online diagnostic test failed for this CPU |
- |
LOG_STD_ACTION |
|
ODM-3-DIAG_DISABLE |
3-Error |
Online Diags disabled for all slots without specific config |
Online Diagnostic tests were disabled for all slots except those with specific config |
- |
LOG_STD_ACTION |
|
ODM-3-DIAG_ENABLE |
3-Error |
Online Diags enabled for all slots without specific config |
Online Diagnostic tests were enabled for all slots except those with specific config |
- |
LOG_STD_ACTION |
|
ODM-3-LC_DIAGS_DISABLED |
3-Error |
Slot [dec] after [dec] Failures |
Online diagnostic tests were disabled because of \n\ multiple failures |
- |
LOG_STD_ACTION |
|
ODM-3-LC_TEST_FAIL |
3-Error |
Slot [dec] [chars] [chars] Failed |
Online diagnostic test failed for the card |
- |
LOG_STD_ACTION |
|
ODM-3-PEER_INCOMPATIBLE |
3-Error |
Online Diags Peer Version is different |
Version of the peer Online Diagnostics Manager is different |
- |
LOG_STD_ACTION |
|
ODM-3-SC_DIAGS_DISABLED |
3-Error |
Slot [dec] Subcard [dec] after [dec] Failures |
Online diagnostic tests were disabled because of \n\ multiple failures |
- |
LOG_STD_ACTION |
|
ODM-3-SC_TEST_FAIL |
3-Error |
Slot [dec] Subcard [dec][chars] [chars] Failed |
Online diagnostic test failed for the subcard |
- |
LOG_STD_ACTION |
|
OER_BR-1-ALERT |
1-Alert |
NULL |
- |
oer |
"" |
|
OER_BR-3-ERROR |
3-Error |
NULL |
- |
oer |
"" |
|
OER_BR-3-INTERNAL_ERROR |
3-Error |
[chars]:[chars] |
- |
PfR |
"" |
|
OER_BR-4-WARNING |
4-Warning |
NULL |
- |
oer |
"" |
|
OER_BR-5-NOTICE |
5-Notice |
NULL |
- |
oer |
"" |
|
OER_BR-6-INFO |
6-Information |
NULL |
- |
oer |
"" |
|
OER_MC-0-EMERG |
0-Emergency |
NULL |
- |
oer |
"" |
|
OER_MC-1-ALERT |
1-Alert |
NULL |
- |
oer |
"" |
|
OER_MC-3-ERROR |
3-Error |
NULL |
- |
oer |
"" |
|
OER_MC-4-WARNING |
4-Warning |
NULL |
- |
oer |
"" |
|
OER_MC-5-NOTICE |
5-Notice |
NULL |
- |
oer |
"" |
|
OER_MC-6-INFO |
6-Information |
NULL |
- |
oer |
"" |
|
OER_TT_FLOW-2-OER_TT_FLOW_BR_CACHEINIT |
2-Critical |
Error initializing OER TT Flow BR cache |
Initialization of the OER TT Flow BR cache could not be accomplished because of a low memory condition. |
- |
"Reduce other system activitiy to ease memory demands. If conditions " "warrant upgrade to a larger memory configuration." |
|
OER_TT_FLOW-2-OER_TT_FLOW_BR_EXPORTINIT |
2-Critical |
Error initializing OER TT Flow BR Export queue |
Initialization of the OER TT Flow BR export queue could not be accomplished because of a low memory condition. |
- |
"Reduce other system activitiy to ease memory demands. If conditions " "warrant upgrade to a larger memory configuration." |
|
OER_TT_FLOW-4-OER_TT_FLOW_BR_FLOWEXPORT |
4-Warning |
Error exporting [chars] |
flows to RP |
- |
LOG_STD_DBG_ACTION |
|
OFP-3-ASSERT |
3-Error |
[chars] |
OpenFlow Agent has experienced an internal software problem. |
openflow-agent |
LOG_STD_ACTION |
|
OFP-3-ERR |
3-Error |
[chars] |
OpenFlow Agent has experienced an internal software problem. |
openflow-agent |
LOG_STD_ACTION |
|
OFP-4-WARN |
4-Warning |
[chars] |
OpenFlow Agent warning information action may be required. |
openflow-agent |
LOG_STD_ACTION |
|
OFP-5-CONFIG |
5-Notice |
[chars] |
OpenFlow Agent information usually configuration command. |
openflow-agent |
"None" |
|
OFP-6-INFO |
6-Information |
[chars] |
OpenFlow Agent information action may not be required. |
openflow-agent |
"None" |
|
OIR-3-BADFPGAIMG |
3-Error |
Controller in in slot [dec] does not have a valid FPGA image |
Invalid FPGA image in slot\n |
- |
"Contact customer support." |
|
OIR-3-BADIDPROM |
3-Error |
IDPROM in slot [dec] not properly programmed |
IDPROM is not programmed correctly |
- |
"Contact customer support." |
|
OIR-3-CRASH |
3-Error |
The module in slot [dec] has crashed |
The module in the slot indicated has crashed and will be rebooted by\n\ the supervisor. |
- |
"Collect the crashinfo file from the crashed module and contact\n\ support." |
|
OIR-3-DEACTIVATED |
3-Error |
Slot [dec] [chars] [dec]: subcard [dec] deactivated |
Deactivated subcard in a slot |
- |
"" |
|
OIR-3-DETECT |
3-Error |
Detected [chars] in slot [dec] |
Type of card detected in slot\n |
- |
"" |
|
OIR-3-INVALID_ALERT_COMBINATION |
3-Error |
Invalid alert combination received with lrc version [dec] src version [dec] |
Invalid LRC alert combination\n |
- |
"" |
|
OIR-3-INVALID_ALERT_FORMAT |
3-Error |
Invalid LRC alert format received from slot [dec] format [hex] |
Invalid LRC alert format\n |
- |
"" |
|
OIR-3-INVALID_OPER_TYPE |
3-Error |
Invalid operation on slot [dec] op_type [hex] |
Invalid operation type from SRC/LRC\n |
- |
"" |
|
OIR-3-LINECARD_NOT_READY |
3-Error |
Line card in slot [dec] not becoming ready after OIR |
After OIR Line is not becoming ready\n |
- |
"Contact customer support." |
|
OIR-3-LONGSTALL |
3-Error |
Long bus stall [dec] ms check for improperly seated cards |
An online insertion or removal of an interface processor card has stalled the backplane bus for longer duration than expected. |
- |
"Make sure all interface processor cards are inserted or removed. " LOG_STD_ACTION_ERR |
|
OIR-3-OSC_SUBCARDDETECT |
3-Error |
Slot [dec] [chars] [dec]: subcard [dec] inserted |
OSC Subcard detected in slot\n |
- |
"" |
|
OIR-3-OSC_SUBCARDREMOVE |
3-Error |
Slot [dec] [chars] [dec]: subcard [dec] removed |
OSC Subcard removed from slot |
- |
"" |
|
OIR-3-PSM_SUBCARDDETECT |
3-Error |
Slot [dec] [chars] [dec]: subcard [dec] inserted |
PSM Subcard detected in slot\n |
- |
"" |
|
OIR-3-PSM_SUBCARDREMOVE |
3-Error |
Slot [dec] [chars] [dec]: subcard [dec] removed |
PSM Subcard removed from slot |
- |
"" |
|
OIR-3-REMOVE |
3-Error |
Removed [chars] in slot [dec] |
Type of card removed from slot |
- |
"" |
|
OIR-3-RF_REGISTRTN_FAILED |
3-Error |
OIR Client failed to register with RF |
Due to some error OIR Client Failed to register with the RF |
- |
"Contact customer support." |
|
OIR-3-SEATED |
3-Error |
Insert/removal failed for slot [dec] check card seating |
The OIR facility detected an incorrectly seated card\n\ causing the insertion or removal of this card to fail. |
- |
"Reseat the card in the indicated slot." |
|
OIR-3- SUBCARD_BAD |
3-Error |
Slot [dec] [chars] [dec]: subcard [dec] does not meet operating specifications |
Subcard does not meet operating specifications |
- |
"Contact customer support." |
|
OIR-3- SUBCARD_BAD_IDPROM |
3-Error |
Slot [dec] [chars] [dec]: subcard [dec] IDPROM not programmed correctly |
IDPROM is not programmed correctly |
- |
"Contact customer support." |
|
OIR-3- SUBCARD_BAD_PORT |
3-Error |
Slot [dec] [chars] [dec]: subcard [dec] did not initialize correctly |
Subcard did not initialize correctly |
- |
"Contact customer support." |
|
OIR-3-SUBCARD_DEACT |
3-Error |
Slot [dec]: [[chars] [dec]] subcards deactivated |
Deactivated subcards in a slot |
- |
"" |
|
OIR-3-SUBCARD_DISC |
3-Error |
Slot [dec]: [[chars] [dec]] subcards discovery |
Discovered subcards in a slot |
- |
"" |
|
OIR-3-SUBCARD_SCANERR |
3-Error |
Error in scanning subcards in slot [dec] |
Error in scanning subcards\n |
- |
"" |
|
OIR-3-SUBCARDDETECT |
3-Error |
Slot [dec] [chars] [dec]: subcard [dec] inserted |
Type of card detected in slot\n |
- |
"" |
|
OIR-3-SUBCARDREMOVE |
3-Error |
Slot [dec] [chars] [dec]: subcard [dec] removed |
Type of card removed from slot |
- |
"" |
|
OIR-3-XCVRDETECT |
3-Error |
Slot [dec] Subcard [dec] port [dec]: line transceiver inserted |
Type of card detected in slot\n |
- |
"" |
|
OIR-3-XCVRREMOVE |
3-Error |
Slot [dec] Subcard [dec] port [dec]: line transceiver removed |
Type of card removed from slot |
- |
"" |
|
OIR-4-NOEOIR |
4-Warning |
[chars] [chars] version [dec].[dec] not capable of EOIR |
- |
- |
"Try to restrict insertion or removal of this card to times when a\n\ CBUS complex restart will be least disruptive.\n\ Or upgrade the card to the latest revision which supports EOIR." |
|
OIR-6-INSCARD |
6-Information |
Card inserted in slot [dec] interfaces administratively shut down |
The OIR facility detected a newly inserted processor. The interfaces associated with that processor 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 |
|
OIR-6-REMCARD |
6-Information |
Card removed from slot [dec] interfaces disabled |
The OIR facility detected the removal of a processor from the slot number specified in the error message. The interfaces on that processor 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 |
|
OIRLIB-4-NOTRACE |
4-Warning |
OIR-LIB trace initialization failed[dec] |
- |
- |
- |
|
OLM-3-LMPNONBR |
3-Error |
Internal error: Couldn't find neighbor while [chars] |
An LMP processing that requires to access information about the neighbor has found that no such neighbor exists. This could be due to internal error. |
ocp |
"Turn on generic and packet level debugging using " "the command debug ip lmp and gather LMP configuration using the " "command show ip olm and gather the displayed information and " "contact Cisco technical assistance." |
|
OLM-3-LMPSDMISMATCH |
3-Error |
Service Discovery: Attribute [chars] incompatible with neighbor [chars] |
Specified service attribute does not match with neighbor. The neighbor and/or the local node may not be properly configured. |
ocp |
"" |
|
OLM-3-LMPSDPORTFAILED |
3-Error |
Service Discovery: Attributes for port [chars] incompatible with nbr [chars] |
Port-level service attribute does not match with those of the neighbor. The neighbor and/or the local node may not be properly configured. |
ocp |
"" |
|
OLM-3-LMPSNDFAIL |
3-Error |
Failed to send LMP msg to [chars] |
- |
ocp |
LOG_STD_ACTION |
|
OLM-5-LMPMSGSEQ |
5-Notice |
LMP [chars] msg id [dec] not 1+[dec] |
An LMP message has been received with message id that is not sequential within the Control channel or TE Link. This situation is not caused by the known cases that cause message id sequence to be broken including local node reboot neighbor node reboot and neighbor retransmission |
ocp |
"Enter the show ip olm stat command when this " "problem occurs and gather the information displayed and call the " "Cisco technical assistance." |
|
OLM-5-LMPNONBR1 |
5-Notice |
No such neighbor to assign |
An internal consistency error has been encountered during the said processing. |
ocp |
LOG_STD_ACTION |
|
OLM-5-LMPUNKSRC |
5-Notice |
LMP rcvd msg from unknown src ip 0x[inet] link % |
An LMP message has been received with invalid TLV length. This suggests that we have a broken LMP implementation on the sending neighbor. |
ocp |
"Locate the sending neighbor and turn on packet " "level debugging using the debug ip lmp packets command. On seeing " "an ill-formed LMP packet gather displayed information and contact " "the Cisco technical assistance." |
|
OLM-5-LSUMBADTEL |
5-Notice |
Invalid TE Link ID [dec] in Link Summary message |
This is generally caused by race conditions wherein an LMP message is received from a neighbor before the first control channel goes UP [locally]. This conditions usually happens when a node reboots. |
ocp |
"If the problem persists even after the node has " "completed initialization enter sho ip olm command to find the LMP " "configuration and use the debug ip lmp packets and debug ip lmp " "generic command to gather additional context type information and " "call Cisco technical assistance." |
|
OLM-5-LSUMMISMATCH |
5-Notice |
Link Summary parameter[chars] mismatch |
An LMP message has been received with invalid message type. This suggests that we have a broken LMP implementation on the sending neighbor |
ocp |
"Locate the sending neighbor and turn on packet " "level debugging using the debug ip lmp packets command. On seeing " "an ill-formed LMP packet gather displayed information and contact " "the Cisco technical assistance." |
|
OMP_AGENT-3-IPDB_SEARCH_FAIL |
3-Error |
Topo-id 0x[hec] - instance PDB search failure. |
instance PDB search failure |
cedge-routing |
LOG_STD_SH_TECH_ACTION |
|
OMP_AGENT-3-MCAST_NO_REPL |
3-Error |
No replicator selected for VPN-%lld |
SDWAN Multicast is configured but a reachable multicast replicator is not available. |
- |
"Assure an SDWAN multicast replicator is " "configured and reachable." |
|
OMP_AGENT-3-MCAST_REPL_ADD_FAIL |
3-Error |
Topo-id: 0x[hec] - SDWAN multicast replicator [inet] addition failed. |
Intenal error - SDWAN multicast replicator could not be added. |
cedge-routing |
LOG_STD_SH_TECH_ACTION |
|
OMP_AGENT-3-MCAST_REPL_DELETE_FAIL |
3-Error |
Topo-id: 0x[hec] - SDWAN multicast replicator [inet] deletion failed. |
Internal error -SDWAN multicast replicator could not be deleted. |
cedge-routing |
LOG_STD_SH_TECH_ACTION |
|
OMP_AGENT-3-MCAST_SPT_ONLY_MISMATCH |
3-Error |
Multicast spt-only [chars]abled locally and [chars]abled on SDWAN router [inet] in VPN-%lld |
SDWAN Multicast spt-only mode must be configured consistently for all SDWAN multicast routers in the VPN. Failure to do will prevent Any Source Multicast ASM from functioning properly. |
- |
"Assure an SDWAN multicast spt-only mode is " "configured consistently." |
|
OMP_AGENT-3-MTENANT_INIT_FAIL |
3-Error |
Multi-Tenant initialization failure |
SDWAN Multi-Tenant capability couldn't be initialized |
- |
"Examine other log messages to " "determine the reason for the failure." |
|
OMP_AGENT-3-MTENANT_TENANT_NOT_FOUND |
3-Error |
Multi-Tenant tenant ID [dec] not found on [chars] |
SDWAN Multi-Tenant tenant not found in specified situation |
cedge-routing |
LOG_STD_SH_TECH_ACTION |
|
OMP_AGENT-3-TREE_DELETE_FAIL |
3-Error |
Topo-id 0x[hec] - Tree deletion failure for [chars]. |
Internal error - AVL tree deletion for specified object failed. |
cedge-routing |
LOG_STD_SH_TECH_ACTION |
|
OMP_AGENT-3-TREE_INSERT_FAIL |
3-Error |
Topo-id 0x[hec] - Tree insertion failure for [chars]. |
Internal error - AVL tree insertion for specified object failed. |
cedge-routing |
LOG_STD_SH_TECH_ACTION |
|
OMP_AGENT-3-VPN_CONVERT_FAIL |
3-Error |
Topo-id 0x[hec] - VPN Conversion failure for [chars]. |
Internal error - Topology to VPN conversion failure for specified object. |
cedge-routing |
LOG_STD_SH_TECH_ACTION |
|
OMP_AGENT-3-VPN_NOT_FOUND |
3-Error |
Topo-id 0x[hec] - VPN for [chars] topo-id not found. |
Internal error - VPN for the specified object's topology should exist but doesn't. |
cedge-routing |
LOG_STD_SH_TECH_ACTION |
|
OMP_AGENT-4-MCAST_JOIN_COUNT_OFF |
4-Warning |
Topo-id 0x[hec] - [chars] C-Multicast route count off for SDWAN router [inet] joins: [dec] prunes: [dec] |
SDWAN multicast count of active joins is off as it should never be negative. |
cedge-routing |
"This can occur during transient conditions and " "should are not indicative of a failure unless " "there is also an SDWAN multicast outage." |
|
ONEP_BASE-3-AUTHEN_ERR |
3-Error |
[[chars]]: Authentication/authorization failed. [chars] |
The session authentication has failed |
onep |
"Check user's credentials are matched against the AAA/local " "users configured on the Netwk Element." |
|
ONEP_BASE-3-BUSY_ERR |
3-Error |
[[chars]]: The requested resource is currently busy. [chars]. |
The usage of the resource has exceeded the configured threshold value |
onep |
"Check the current resource usage and configured resource threshold." " cpu threshold rising <value> falling <value> interval <seconds>" "Retry the operation if resource usage is below the threshold." |
|
ONEP_BASE-3-DISABLED_ERR |
3-Error |
[[chars]]: [chars] is disabled. |
The requested service set is in disabled state. All the service requests for that service set will be rejected. |
onep |
"Make sure the service set is enabled. " "onep " " service set <name>" |
|
ONEP_BASE-3-DUPLICATE_ERR |
3-Error |
[[chars]]: Requested entity [chars] already exists. |
The connection request to the network element already exists |
onep |
"Make sure the uniqueness of the application name." "One session per application is allowed on a network element." |
|
ONEP_BASE-3-SESSION_ERR |
3-Error |
[[chars]]: ONEP session maximum is exceeded. [chars]. |
The application session has exceeded the configured maximum |
onep |
"Check the configured session maximum value and adjust accordingly." ">session max <value>" "Retry the session establishment or adjust the configured session maximum." |
|
ONEP_BASE-3-STARTUP_ERR |
3-Error |
[[chars]]: Start up ONEP failed. [chars]. |
Fail to start ONEP due to error |
onep |
"Check transport is configured correctly or reboot the device" |
|
ONEP_BASE-3-VERSION_ERR |
3-Error |
[[chars]]: ONE-P version incompatible between client and network element. [chars] |
The ONE-P client service set version is incompatible with the one installed on the network element |
onep |
"Make sure the version running on the client side is compatible " "with the one installed on the network element " |
|
ONEP_BASE-4-CLEAR_TEXT_TRANSPORT_WARN |
4-Warning |
[[chars]]: Clear text transport being enabled. This is not recommended for production environment. [chars] |
Clear text transport being enabled. This is not recommended for production environment. |
onep |
"Please configure secure transport such as TLS." |
|
ONEP_BASE-6-CONNECT |
6-Information |
[[chars]]: ONEP session [chars] has connected. |
A new ONEP session has been established with network element. |
onep |
"No action is required if this is an authorized session." |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
[[chars]]: ONEP session [chars] |
ONEP session has been disconnected. A disconnect can happen when application has finished execution or there was a problem during execution including issue with network transport. If reconnect timer is configured Network Element will wait for application to reconnect within configured time before cleaning up session resources. |
onep |
"No action is required if it is a expected disconnected. If reconnect" " timer is configured session will wait for application to attempt" " reconnect request" "Use show tech-support onep to collect logs from Network Element" |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
The ONE-P client service set version is incompatible with the one installed on the network element |
SRVNAME_ONEP |
"Make sure the version running on the client side is compatible " "with the one installed on the network element " |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
The requested service set is in disabled state. All the service requests for that service set will be rejected. |
SRVNAME_ONEP |
"Make sure the service set is enabled. " "connectedapps " " service set <name>" |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
The connection request to the network element already exists |
SRVNAME_ONEP |
"Make sure the uniqueness of the application name." "One session per application is allowed on a network element." |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
The session authentication has failed |
SRVNAME_ONEP |
"Check user's credentials are matched against the AAA/local " "users configured on the Netwk Element." |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
The usage of the resource has exceeded the configured threshold value |
SRVNAME_ONEP |
"Check the current resource usage and configured resource threshold." " cpu threshold rising <value> falling <value> interval <seconds>" "Retry the operation if resource usage is below the threshold." |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
Clear text transport being enabled. This is not recommended for production environment. |
SRVNAME_ONEP |
"Please configure secure transport such as TLS." |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
Administrator has disabled ONEP feature while application sessions were active. All active sessions have been terminated. To enable ONEP again use \'feature onep\' command in configuration mode. |
SRVNAME_ONEP |
"No action is required if this was deliberate operation. To enable " "ONEP again use \'feature onep\' command in configuration mode." |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
This syslog message is used to display onePK history messages when the 'history syslog' onep command is enabled. |
SRVNAME_ONEP |
"No action is required. Use 'no history syslog' at the onep " "configuration prompt to turn off this logging if desired." |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
The Network Element and Persistent Storage for the running-config are out of sync. If no other error has occurred the Network Element configuration will take precedence. |
SRVNAME_ONEP |
"Try reconfiguring the item possibly using the [no] form to restore " "a default value if a new one doesn't take. The 'show running-config' " "command should be used to see if this error persists." |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
The Network Element and Persistent Storage for the running-config are out of sync. If no other error has occurred the Network Element configuration will take precedence. |
SRVNAME_ONEP |
"Try reconfiguring the item possibly using the [no] form to restore " "a default value if a new one doesn't take. The 'show running-config' " "command should be used to see if this error persists." |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
The requested service set is in disabled state. All the service requests for that service set will be rejected. |
SRVNAME_ONEP |
"Make sure the service set is enabled. " "connectedapps " " service set lisp" |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
The service set has been set to an enabled state. The features of the service set will be available for use. |
SRVNAME_ONEP |
"If the enablement was intentional no action is required." |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
The service set has been set to a disabled state. All service requests for that service set will be rejected. |
SRVNAME_ONEP |
"If the disablement was intentional no action is required." "If not then enable the service set:" "onep " " service set <name>" |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
The Onepsync 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. |
SRVNAME_ONEP |
LOG_STD_ACTION |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
The Onepsync ISSU client received an incompatible message from the peer device. The message cannot be processed. |
SRVNAME_ONEP |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
The Onepsync ISSU client failed to calculate the MTU for the specified message. The Onepsync ISSU client is not able to send the message to the standby device. |
SRVNAME_ONEP |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
The Onepsync ISSU client does not have a valid registered session. |
SRVNAME_ONEP |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
The Onepsync ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
SRVNAME_ONEP |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
The Onepsync ISSU client failed to unregister session information. |
SRVNAME_ONEP |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
The Onepsync ISSU client failed to start session negotition. If a problem occurs with the ISSU session start the standby device cannot be brought up properly. |
SRVNAME_ONEP |
"show issu session <client_id>" |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
The Onepsync 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. |
SRVNAME_ONEP |
"show logging and show checkpoint client" |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
The Onepsync 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. |
SRVNAME_ONEP |
"show logging and show checkpoint client" |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
A new ONEP session has been established with network element. |
SRVNAME_ONEP |
"No action is required if this is an authorized session." |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
ONEP session has been reconnected after being disconnected temporarly. This disconnect can happen due to intermittent network connectivity issues. |
SRVNAME_ONEP |
"No action is required if this is an authorized session." |
|
ONEP_BASE-6-DISCONNECT |
6-Information |
- |
ONEP session has been disconnected. A disconnect can happen when application has finished execution or there was a problem during execution including issue with network transport. If reconnect timer is configured Network Element will wait for application to reconnect within configured time before cleaning up session resources. |
SRVNAME_ONEP |
"No action is required if it is a expected disconnected. " "Use show tech-support onep to collect logs from Network Element" |
|
ONEP_BASE-6-HISTORY |
6-Information |
[chars] |
This syslog message is used to display onePK history messages when the 'history syslog' onep command is enabled. |
onep |
"No action is required. Use 'no history syslog' at the onep " "configuration prompt to turn off this logging if desired." |
|
ONEP_BASE-6-RECONNECT |
6-Information |
[[chars]]: ONEP session [chars] has reconnected. |
ONEP session has been reconnected after being disconnected temporarly. This disconnect can happen due to intermittent network connectivity issues. |
onep |
"No action is required if this is an authorized session." |
|
ONEP_BASE-6-SS_DISABLED |
6-Information |
ONEP: [chars] |
The service set has been set to a disabled state. All service requests for that service set will be rejected. |
onep |
"If the disablement was intentional no action is required." "If not then enable the service set:" "onep " " service set <name>" |
|
ONEP_BASE-6-SS_ENABLED |
6-Information |
ONEP: [chars] |
The service set has been set to an enabled state. The features of the service set will be available for use. |
onep |
"If the enablement was intentional no action is required." |
|
ONEP_LISP-3-DISABLED_ERR |
3-Error |
[[chars]]: [chars] is disabled. |
The requested service set is in disabled state. All the service requests for that service set will be rejected. |
onep |
"Make sure the service set is enabled. " "onep " " service set lisp" |
|
ONEPSYNC_ISSU-2-GET_BUFFER |
2-Critical |
Onepsync ISSU client failed to get buffer for message. Error: [dec] [chars] |
The Onepsync 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. |
onep |
"show logging and show checkpoint client" |
|
ONEPSYNC_ISSU-2-INIT |
2-Critical |
Onepsync ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The Onepsync 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. |
onep |
LOG_STD_ACTION |
|
ONEPSYNC_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
Onepsync ISSU client failed to send negotiation message. Error: [dec] [chars] |
The Onepsync 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. |
onep |
"show logging and show checkpoint client" |
|
ONEPSYNC_ISSU-2-SESSION_NEGO_FAIL_START |
2-Critical |
Failed to start Onepsync ISSU session negotiation. Error: [dec] [chars] |
The Onepsync ISSU client failed to start session negotition. If a problem occurs with the ISSU session start the standby device cannot be brought up properly. |
onep |
"show issu session <client_id>" |
|
ONEPSYNC_ISSU-2-SESSION_REGISTRY |
2-Critical |
Onepsync ISSU client failed to register session information. Error: [dec] [chars] |
The Onepsync ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
onep |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ONEPSYNC_ISSU-3-INVALID_SESSION |
3-Error |
Onepsync ISSU client does not have a valid registered session. |
The Onepsync ISSU client does not have a valid registered session. |
onep |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ONEPSYNC_ISSU-3-MSG_NOT_OK |
3-Error |
Onepsync ISSU client 'Message Type [dec]' is not compatible |
The Onepsync ISSU client received an incompatible message from the peer device. The message cannot be processed. |
onep |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
ONEPSYNC_ISSU-3-MSG_SIZE |
3-Error |
Onepsync ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The Onepsync ISSU client failed to calculate the MTU for the specified message. The Onepsync ISSU client is not able to send the message to the standby device. |
onep |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
ONEPSYNC_ISSU-3-SESSION_UNREGISTRY |
3-Error |
Onepsync ISSU client failed to unregister session information. Error: [dec] [chars] |
The Onepsync ISSU client failed to unregister session information. |
onep |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
OPENDNS_PROXY-2-OPENDNS_MSG_PROXYINIT_FAILURE |
2-Critical |
UMBRELLA - Failed to register IPC message handler result code [dec] |
QFP Umbrella feature failed to register an IPC message handler for communication with control plane. This will cause the featue not to function. |
OPENDNS_COMP_NAME |
LOG_STD_ACTION |
|
OPENDNS_PROXY-3-OPENDNS_MSG_PROXY_ALLOC_FAILURE |
3-Error |
UMBRELLA - Failed to get [dec] bytes space for IPC reply message |
QFP Umbrella feature detected buffer allocation failure while sending reply to a message from another layer of Umbrella feature's software stack. |
OPENDNS_COMP_NAME |
LOG_STD_ACTION |
|
OPENDNS_PROXY-3-OPENDNS_MSG_PROXY_DEBUG_REG_FAILED |
3-Error |
- |
Umbrella Conditional Debugging Registration failed. |
OPENDNS_COMP_NAME |
LOG_STD_ACTION |
|
OPENDNS_PROXY-3-OPENDNS_MSG_PROXY_INVALID_MSGLEN |
3-Error |
UMBRELLA - Received an invalid length IPC message |
QFP Umbrella feature received an incorrect length of IPC message from anoter layer of Umbrella feature's software stack m_enum [dec] m_subtype [dec] m_len [dec] m_flags 0x[hec] m_source [dec]. |
OPENDNS_COMP_NAME |
LOG_STD_ACTION |
|
OPENDNS_PROXY-3-OPENDNS_MSG_PROXY_IPCSEND_FAIL |
3-Error |
UMBRELLA - Failed to send IPC message result code [dec] |
QFP Umbrella feature failed to send IPC message to another layer of Umbrella feature's software stack. |
OPENDNS_COMP_NAME |
LOG_STD_ACTION |
|
OPENDNS_PROXY-3-OPENDNS_MSG_PROXY_OPENREPLY_FAIL |
3-Error |
UMBRELLA - Failed to open reply message part of IPC packet |
QFP Umbrella feature failed to open message part of IPC packet while sending a reply to another layer of Umbrella feature's software stack. |
OPENDNS_COMP_NAME |
LOG_STD_ACTION |
|
OPENDNS_PROXY-3-OPENDNS_MSG_PROXY_UNKNOWN_IPCMSG |
3-Error |
UMBRELLA - Received an unknown type code [dec] IPC message |
QFP Umbrella feature received an unknown message from another layer of Umbrella feature's software stack. |
OPENDNS_COMP_NAME |
LOG_STD_RECUR_ACTION |
|
OPTICAL_IF_ALARMS-3-HIGH_ALM_THR |
3-Error |
High Alarm Threshold for [chars] on port [chars] [chars] |
High alarm threshold was exceeded. |
- |
LOG_STD_ACTION |
|
OPTICAL_IF_ALARMS-3-HIGH_WARN_THR |
3-Error |
High Warning Threshold for [chars] on port [chars] [chars] |
High warning threshold was exceeded. |
- |
LOG_STD_ACTION |
|
OPTICAL_IF_ALARMS-3-LOW_ALM_THR |
3-Error |
Low Alarm Threshold for [chars] on port [chars] [chars] |
Low alarm threshold was exceeded. |
- |
LOG_STD_ACTION |
|
OPTICAL_IF_ALARMS-3-LOW_WARN_THR |
3-Error |
Low Warning Threshold for [chars] on port [chars] [chars] |
Low warning threshold was exceeded. |
- |
LOG_STD_ACTION |
|
OPTICAL_IF-1-ALARM |
1-Alert |
[chars] [chars]: [chars] |
The specified Alarm has been declared or cleared |
- |
"Recommended action is to repair the source of the alarm." |
|
OPTICAL_IF-3-INTERNAL_ERROR |
3-Error |
[chars] |
The metopt subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
OPTICAL_MONITOR-4-FAILED |
4-Warning |
[chars] [chars] |
Monitoring cannot be turned on for rate specified with current h/w version. |
- |
LOG_STD_ACTION |
|
OSCP-3-INTERNAL_ERROR |
3-Error |
[chars] [hec] |
An internal software error occurred. The message contains more\n\ information that can be used to identify the problem. |
- |
LOG_STD_ACTION |
|
OSCP-4-BADPACKET |
4-Warning |
Invalid pkt: [chars] [dec] [dec] |
An invalid packet was received from a network peer. |
- |
"Check the originating device for a cause of the corrupted\n\ packets." |
|
OSCP-4-CONFIG_ERROR |
4-Warning |
Configuration Error: [chars] |
This message indicates a configuration error in the OSCP subsystem.\n\ The message will display more specific information about the\n\ cause of problem. |
- |
"Change the configuration to correct the error." |
|
OSCP-7-DEBUG |
7-Debug |
[chars] |
This is an informational message only. It is used by Cisco\n\ for testing. |
- |
"Informational messages can be disabled by changing logging level." |
|
OSM_MULTILINK-3-PROCESS_FAIL |
3-Error |
Process creation failed for [chars] |
A Process has failed to be created. The probable cause of this condition is that the system is low on memory. |
osm-ct3 for CT3 and osm-choc-ds0 for CHOC-12/CHOC-3 |
"Reduce other system activity to ease memory demands. If conditions" " warrant upgrade to a larger memory configuration." |
|
OSM_MULTILINK-4-BUNDLEERROR |
4-Warning |
Bundle[chars] is not distributed |
The Bundle specified in the error message is not associated with the OSM. |
osm-ct3 for CT3 and osm-choc-ds0 for CHOC-12/CHOC-3 |
LOG_STD_SH_TECH_ACTION |
|
OSM_MULTILINK-4-BUNDLENULL |
4-Warning |
Unexpected bundle missing in [chars] searching for [chars] |
A software error has occured. |
osm-ct3 for CT3 and osm-choc-ds0 for CHOC-12/CHOC-3 |
LOG_STD_SH_TECH_ACTION |
|
OSM_MULTILINK-4-BUNDLEVC |
4-Warning |
[chars] for vc [dec] and if_index [dec] |
A software error has occured while a bundle was being provisioned. |
osm-ct3 for CT3 and osm-choc-ds0 for CHOC-12/CHOC-3 |
LOG_STD_SH_TECH_ACTION |
|
OSM_MULTILINK-4-IDBNULL |
4-Warning |
Unexpected hwidb missing in [chars] |
A software error has occurred. |
osm-ct3 for CT3 and osm-choc-ds0 for CHOC-12/CHOC-3 |
LOG_STD_SH_TECH_ACTION |
|
OSM_MULTILINK-4-IPCNOTREADY |
4-Warning |
Bundle process on the line card is not ready to handle message of type [dec] |
Bundle is being deleted on the line card due to <CmdBold>ip cef disable<CmdBold> command and is not ready to process other messages. The most likely cause of this condition is that CEF was disabled and enabled in a very quick succession. |
osm-ct3 for CT3 and osm-choc-ds0 for CHOC-12/CHOC-3 |
"Reset the line card." |
|
OSM_MULTILINK-4-MLPLINK_NULL |
4-Warning |
Unexpected mlp link missing in [chars] |
A software error has occurred. |
osm-ct3 for CT3 and osm-choc-ds0 for CHOC-12/CHOC-3 |
LOG_STD_SH_TECH_ACTION |
|
OSM_MULTILINK-4-MLPSBNULL |
4-Warning |
Unexpected subblock missing for [chars] |
A software error has occurred. |
osm-ct3 for CT3 and osm-choc-ds0 for CHOC-12/CHOC-3 |
LOG_STD_SH_TECH_ACTION |
|
OSM_MULTILINK-4-NUMLINKS |
4-Warning |
The bundle had an unexpected number of links[dec] in [chars] |
A softwate error has occured. |
osm-ct3 for CT3 and osm-choc-ds0 for CHOC-12/CHOC-3 |
LOG_STD_SH_TECH_ACTION |
|
OSM_MULTILINK-4-QUEUE_BUNDLE |
4-Warning |
Not able to queue the bundle [chars] Num. of bundles [dec] |
A software error has occured while a bundle was being inserted in queue. |
osm-ct3 for CT3 and osm-choc-ds0 for CHOC-12/CHOC-3 |
LOG_STD_SH_TECH_ACTION |
|
OSM_MULTILINK-5-BUNDLEEXCEEDED |
5-Notice |
Bundle[chars] cannot be associated with link[chars] max [dec] |
The number of bundles has been exceeded for the group belonging to the link. The bundle specified in the error message will not work in distributed mode. If the line card is CT3 OSM-CT3 line card then ports 1-12 belong to one group. If the |
osm-ct3 for CT3 and osm-choc-ds0 for CHOC-12/CHOC-3 |
"Remove the multilink interface that is causing this condition." |
|
OSM_MULTILINK-5-CFGERROR |
5-Notice |
Cannot set up this bundle link-- [chars] to bundle [chars]\n\treason:[chars]\n |
The bundle link could not be set up. A configuration of resource limit has been reached. The bundle may be forced to become inactive go down. If the line card is a CT3 line card OSM-CT3 line card |
osm-ct3 for CT3 and osm-choc-ds0 for CHOC-12/CHOC-3 |
"Ensure that all links belong to the same group and slot. Check" " the number of links in the bundle and number of bundles in the" " group. After the configuration has been corrected enter the" " <CmdBold>shutdown<CmdBold> and <CmdBold>no shutdown<CmdBold>" " comands on the multilink interface to shut down and restart" " the interface." |
|
OSPF_NSR-2-ISSU_INIT |
2-Critical |
ISSU client initialization failed to [chars] error: [dec] [chars] |
The OSPF 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. |
ospf |
LOG_STD_ACTION |
|
OSPF_NSR-3-CF_ADD_CLIENT |
3-Error |
Error adding OSPF checkpoint client: [chars] |
OSPF was not able to register as a client of the checkpoint facility |
ospf |
show tech-support ospf |
|
OSPF_NSR-3-CF_NOMEM |
3-Error |
Unable to allocate checkpoint buffer: [chars] |
NSR operation may be degraded to a lack of memory. |
ospf |
show tech-support ospf |
|
OSPF_NSR-3-CF_NOMSG |
3-Error |
No space in checkpoint buffer |
NSR operation may be degraded to a lack of memory. |
ospf |
show tech-support ospf |
|
OSPF_NSR-3-CHKPT_MSG |
3-Error |
Invalid checkpoint message: [chars] [chars] |
NSR will not operate due to an error in a checkpoint message. |
ospf |
show tech-support ospf |
|
OSPF_NSR-3-ISSU_MSG_SIZE |
3-Error |
OSPF[chars] ISSU client failed to get the MTU for message type [chars] [dec]: |
The OSPF ISSU client failed to calculate the MTU for the specified message. The OSPF ISSU client is not able to send the message to the standby device. |
ospf |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
OSPF_NSR-3-ISSU_SESSION_UNREGISTR |
3-Error |
OSPF[chars] ISSU client failed to unregister session information error: [dec] [chars] |
The OSPF ISSU client failed to unregister session information. |
ospf |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
OSPF_NSR-3-ISSU_TRANSFORM_FAIL |
3-Error |
OSPF[chars] ISSU client [chars] transform failed for message type [dec] [chars]: [dec] [chars] |
The OSPF 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 Archive state between the active device and the standby device is not identical. |
ospf |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
OSPF-3-BAD_LSA_BUILD |
3-Error |
OSPF-[dec]: Bad build request for LSA type [dec] LSID [inet] mask [inet] |
LSA was not originated due to internal software error |
ospf |
show tech-support ospf |
|
OSPF-3-CF_NOMEM |
3-Error |
Unable to allocate checkpoint buffer: [chars] |
NSR operation may be degraded to a lack of memory. |
ospf |
show tech-support ospf |
|
OSPF-3-CF_NOMSG |
3-Error |
No space in checkpoint buffer |
NSR operation may be degraded to a lack of memory. |
ospf |
show tech-support ospf |
|
OSPF-3-CFG_NBR_ALLOC_FAILED |
3-Error |
Could not find or allocate neighbor [inet] |
An internal error occurred. |
ospf |
LOG_STD_ACTION |
|
OSPF-3-CFG_OSPF_FAILED |
3-Error |
Only [dec] OSPF process is allowed |
The limit of number of allowed OSPF instances has reached |
ospf |
"Don't configure more than allowed instances" |
|
OSPF-3-CHKPT_IDB_DECODE_FAIL |
3-Error |
Interface cannot be decoded for NSR: [chars] |
Adjacency and interface information for an interface cannot be checkpointed due to an interface decoding error. |
ospf |
"Please verify that this interface type is supported for NSR in " "this release. If so report the problem to the TAC." |
|
OSPF-3-CHKPT_IDB_ENCODE_FAIL |
3-Error |
Interface [chars] cannot be encoded for NSR |
Adjacency and interface information learned from this interface cannot be checkpointed due to an interface encoding error. |
ospf |
"Please verify that this interface type is supported for NSR in " "this release. If so report the problem to the TAC." |
|
OSPF-3-CHKPT_MSG |
3-Error |
Invalid checkpoint message: [chars] [chars] |
NSR will not operate due to an error in a checkpoint message. |
ospf |
show tech-support ospf |
|
OSPF-3-CHKPT_MSG_LOST |
3-Error |
Checkpoint message lost |
NSR will not operate due to a dropped checkpoint message. |
ospf |
show tech-support ospf |
|
OSPF-3-CHKPT_NOMEM |
3-Error |
Unable to allocate checkpoint queue entry |
NSR will not operate due to a failure communicating with the standby. |
ospf |
show tech-support ospf |
|
OSPF-3-CHKPT_SEND_FAIL |
3-Error |
Checkpoint message send failed: [chars] |
NSR will not operate due to a failure communicating with the standby. |
ospf |
show tech-support ospf |
|
OSPF-3-CHKPT_STATUS_LOST |
3-Error |
Checkpoint status lost |
NSR will not operate due to a missing checkpoint status message. |
ospf |
show tech-support ospf |
|
OSPF-3-CHKPT_STBY_LSDB_INVALID |
3-Error |
Standby link-state database validation failed expected/found count: [dec]/[dec] chksum: 0x%llx/0x%llx |
NSR will not operate due to an error on the standby. |
ospf |
show tech-support ospf |
|
OSPF-3-CHKPT_STBY_NO_LSA_BUFFER |
3-Error |
Standby synchronization error: no LSA buffer |
NSR will not operate due to an internal error. |
ospf |
show tech-support ospf |
|
OSPF-3-CHKPT_STBY_NO_LSDB |
3-Error |
Standby synchronization error: could not add lsa type [dec] |
NSR will not operate due to an internal error. |
ospf |
show tech-support ospf |
|
OSPF-3-CHKPT_STBY_NO_NBR |
3-Error |
Standby synchronization error: could not find neighbor [chars] [inet] [inet] |
NSR will not operate due to an internal error. |
ospf |
show tech-support ospf |
|
OSPF-3-CHKPT_STBY_NO_NBR_IF |
3-Error |
Standby synchronization error: interface not attached to add neighbor [chars] [inet] [inet] |
NSR will not operate due to an internal error. |
ospf |
show tech-support ospf |
|
OSPF-3-CHKPT_STBY_SYNC_LOST |
3-Error |
Standby synchronization lost for OSPF-[dec] was: [chars] |
Synchronization between the active and standby OSPF has been lost. |
ospf |
show tech-support ospf |
|
OSPF-3-DBEXIST |
3-Error |
area [chars] lsid [inet] mask [inet] type [dec] |
OSPF is trying to add existing LSA to the database. |
ospf |
LOG_STD_SH_TECH_ACTION |
|
OSPF-3-INT_ATTACHED_MULTI_AREAS |
3-Error |
Interface [chars] is attached to more than one area |
The interface is on the interface list for an area other than the one which the interface links to. |
ospf |
LOG_STD_SH_TECH_ACTION |
|
OSPF-3-INT_INIT_FAILED |
3-Error |
Init failed for interface [chars] [chars]. |
The interface initialization failed. Possible reasons: 1 The area to which the interface is being attached is being |
ospf |
"Remove the configuration command that covers the interface " "and then try it again. " LOG_STD_RECUR_ACTION |
|
OSPF-3-INTERNALERR |
3-Error |
Internal error: [chars] |
An internal software error occurred. |
ospf |
LOG_STD_ACTION |
|
OSPF-3-ISSU_NEGOTIATION |
3-Error |
ISSU negotiation[chars] error: [dec] [chars] |
The OSPF ISSU session could not complete negotiation. This 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. |
ospf |
LOG_STD_ACTION |
|
OSPF-3-LSA_LEN |
3-Error |
Area [chars] router-LSA of length [dec] bytes plus update overhead bytes is too large to flood. |
The router tried to build a router-LSA which is larger than the huge system buffer size or the OSPF protocol imposed maximum. |
ospf |
"If the reported total length LSA size plus " "overhead is larger than the huge system " |
|
OSPF-3-NO_SNMP_IFINDEX |
3-Error |
Interface [chars] does not have an SNMP MIB ifIndex and has been disabled |
The OSPF process has been configured to use the SNMP MIB ifIndex value for the interface IDs. However the ifIndex is not set on this interface so the interface can not be enabled. |
ospf |
"Unconfigure interface-id snmp-if-index for this OSPF process" |
|
OSPF-3-NOBACKBONE |
3-Error |
Flagged as being an ABR without a backbone area |
The router was flagged as an Area Border Router ABR without backbone |
ospf |
"Restart the OSPF process." |
|
OSPF-3-NOSELF |
3-Error |
[chars] iterface [chars] interface state [dec] |
An internal error occurred. |
ospf |
LOG_STD_SH_TECH_ACTION |
|
OSPF-3-NOSTART |
3-Error |
Unable to start OSPF: [chars] |
An internal software error occurred. |
ospf |
LOG_STD_ACTION |
|
OSPF-3-NSR_FAILED |
3-Error |
NSR can not recover checkpointed data for process [dec] |
An NSR failover could not be performed because OSPF on the standby was not synchronized |
ospf |
show tech-support ospf |
|
OSPF-3-RECONF_VL |
3-Error |
OSPF process [dec] is changing router-id. Reconfigure virtual link neighbors with our new router-id |
OSPF process is being reset and it is going to select a new router-id. This will bring down all virtual links. To make them work again virtual link configuration needs to be changed on all virtual link neighbors. |
ospf |
"Change virtual link configuration on all the virtual link " "neighbors to reflect our new router-id." |
|
OSPF-3-UNKNOWNSTATE |
3-Error |
Reached unknown state in neighbor state machine |
An internal software error in this router has resulted in an invalid neighbor state during database exchange. |
ospf |
LOG_STD_SH_TECH_ACTION |
|
OSPF-4-AREA_ALLOC_FAIL |
4-Warning |
Can not allocate memory for area structure |
An internal error occurred. |
ospf |
LOG_STD_SH_TECH_ACTION |
|
OSPF-4-ASBR_WITHOUT_VALID_AREA |
4-Warning |
Router is currently an ASBR while having only one area which is a stub area |
An ASBR must be attached to an area which can carry AS External or NSSA LSAs |
ospf |
"Make the area to which the router is attached into an NSSA or " "regular area." |
|
OSPF-4-BADLENGTH |
4-Warning |
Invalid length [dec] in OSPF packet type [dec] from [inet] ID [inet] [chars] |
The system received an OSPF packet with a length field of less than normal header size or inconsistent with the size of the IP packet in which it arrived. This indicates an error in the sender of the packet. |
ospf |
LOG_STD_SH_TECH_ACTION |
|
OSPF-4-BADLSAMASK |
4-Warning |
Bad LSA mask: Type [dec] LSID [inet] Mask [inet] from [inet] \n NOTE: This route will not be installed in the routing table. |
The router received an LSA with an invalid LSA mask. The cause is likely due to wrong configuration from the LSA originator. |
ospf |
"Find the originating router of this LSA with bad mask correct " "any misconfiguration of this LSA's network. For further debugging " "call your Cisco technical support representative for assistance." |
|
OSPF-4-BADLSATYPE |
4-Warning |
Invalid lsa: [chars] Type [dec] Length [dec] LSID [inet] from [inet] [inet] [chars] |
The router received an LSA with invalid data. LSA contains invalid LSA type wrong checksum or wrong length. The cause is either memory corruption or unexpected behavior on a router. |
ospf |
"From a neighboring address locate the problem router. " "1 Collect a running configuration of the router by entering the" |
|
OSPF-4-CF_UNKNOWN_STATUS |
4-Warning |
Unknown checkpoint status: [dec] |
An internal error occured. |
ospf |
show tech-support ospf |
|
OSPF-4-CFG_NBR_DEFAULT_OPT_ON_NBMA |
4-Warning |
[chars] Configured neighbor [inet] - Ignore incompatible configured options use default. Allowed options on NBMA interfaces are poll-interval and priority |
The configured neighbor was found on a NBMA network and either the cost or database-filter option was configured. These options are only allowed on point-to-multipoint type networks. |
ospf |
"Check the configuration options for the neighbor command and correct " "the options or the network type for the neighbor's interface." |
|
OSPF-4-CFG_NBR_DEFAULT_OPT_ON_P2MP |
4-Warning |
[chars] Configured neighbor [inet] - Ignore incompatible configured options use default. Allowed options on P2MP interfaces are cost and database-filter |
The configured neighbor was found on a point-to-multipoint network and either the poll-interval or priority option was configured. These options are only allowed on NBMA type networks. |
ospf |
"Check the configuration options for the neighbor command and correct " "the options or the network type for the neighbor's interface." |
|
OSPF-4-CFG_NBR_INVALID_NET_TYPE |
4-Warning |
Can not use configured neighbor [inet] on [chars]. Neighbor command only allowed on NBMA and P2MP networks |
The configured neighbor was found on a network for which the network type was neither NBMA nor point-to-multipoint |
ospf |
LOG_STD_NO_ACTION |
|
OSPF-4-CFG_NBR_INVALID_OPT_ON_NBMA |
4-Warning |
Can not use configured neighbor [inet] on [chars] for topology [chars]. Neighbor command only allowed on P2MP network for non-base topology |
The configured neighbor was found on a NBMA network for a non-base topology. Neighbor can not be configured under this topology. |
ospf |
"Check the configuration for the neighbor command and correct it" "or change the network type for the neighbor's interface." |
|
OSPF-4-CFG_NBR_INVALID_OPT_ON_P2MP |
4-Warning |
Can not use configured neighbor [inet] on [chars]. Cost or database-filter is required |
The configured neighbor was found on a point-to-multipoint broadcast network. Either the cost or database-filter option needs to be configured. |
ospf |
"Check the configuration options for the neighbor command and correct " "the options or the network type for the neighbor's interface." |
|
OSPF-4-CFG_NBR_INVALID_OPT_ON_P2MP_NB |
4-Warning |
Can not use configured neighbor [inet] on [chars] for topology [chars]. Neighbor needs to be configured under base topology |
The configured neighbor was found on a point-to-multipoint non-broadcast network for a non-base topology. Neighbor needs to be configured under base topology. |
ospf |
"Check the configuration options for the neighbor command and correct " "the options or the network type for the neighbor's interface." |
|
OSPF-4-CHKPT_MSG_SEQ |
4-Warning |
Invalid checkpoint message sequence number: received [dec] expected [dec] |
NSR has detected a duplicate checkpoint message. |
ospf |
show tech-support ospf |
|
OSPF-4-CHKPT_UNKNOWN_TYPE |
4-Warning |
Invalid checkpoint message type: [dec] |
An internal error occurred. |
ospf |
show tech-support ospf |
|
OSPF-4-CONFLICTING_LSAID |
4-Warning |
Process [dec] area [chars]: LSA origination prevented by LSA with same LSID but a different mask\n Existing Type [dec] LSA: LSID [inet]%m\n New Destination: [inet]%m |
An LSA origination was prevented by a conflicit with an existing\n LSA with the same LSID but a different mask. The algorithm in\n RFC 2328 Appendix E is used to resolve conflicts when multiple\n LSAs with the same prefix and differing masks are advertised.\n When using this algorithm and host routes are advertised there\n are situations where conflict resolution is impossible and either\n the host route or the conflicting prefix is not advertised. |
ospf |
"Locate the prefix that is not advertised and the conflicting prefix\n" "using <CmdBold>show ip route<NoCmdBold> and " "<CmdBold>show ip ospf database<NoCmdBold>.\n" "Decide which route or prefix is more important to advertise and take\n" "steps to prevent advertising the conflicting route or prefix.\n" "If you cannot determine the nature of the error from the collected\n\ information contact your Cisco technical support representative\n\ and provide the representative with the gathered information." |
|
OSPF-4-DUP_RTRID_AREA |
4-Warning |
Detected router with duplicate router ID [inet] in area [chars] |
OSPF has detected a router in the area that has the same router ID as this routing process. Duplicate router IDs may result in network instability causing some destinations to be unreachable. |
ospf |
"The OSPF router ID should be unique. Make sure all routers in the " "area have unique router ID." |
|
OSPF-4-DUP_RTRID_NBR |
4-Warning |
OSPF detected duplicate router-id [inet] from [inet] on interface [chars] |
OSPF has received hello packet from a neighbor that has the same router ID as this routing process. A full adjacency cannot be established. |
ospf |
"The OSPF router ID should be unique. Change the router ID of the " "neighbor." |
|
OSPF-4-ERRRCV |
4-Warning |
Received invalid packet: [chars] from [inet] [chars] |
An invalid OSPF packet was received. Details are included in the error message. The cause might be a misconfigured OSPF or an internal error in the sender. |
ospf |
"Check the OSPF configuration of the receiver and the sender for " "inconsistency." |
|
OSPF-4-FLOOD_WAR |
4-Warning |
Process [dec] [chars] LSA ID [inet] type-[dec] adv-rtr [inet] in area [chars] |
Router is extensively re-originating or flushing the LSA reported by this error message |
ospf |
"If this router is flushing the network LSA it means the " "router received a network LSA whose LSA ID conflicts with " "the IP address of one of the router's interfaces and flushed " "the LSA out of the network. For OSPF to function correctly " "the IP addresses of transit networks must be unique. " "Conflicting routers are the router reporting this error " "message and the router with the OSPF router ID reported as " "adv-rtr in this message. " "If this router is re-originating an LSA highly probably some " "other router is flushing this LSA out of the network. Find " "that router and avoid the conflict. Conflict for type-2 LSA " "may be due to duplicate LSA ID for type-5 LSA it may be " "duplicate router-id on the router reporting this error message" " and on the routers connected to the different area." "In an unstable network this message may also warn of " "extensive re-origination of LSA for some other reason. " "Contact your Cisco technical support representative " "to investigate such a case." |
|
OSPF-4-INV_LSA_BLD_FLG |
4-Warning |
Invalid build flag [hec] for LSA [inet] type [dec] |
An internal error occurred. |
ospf |
LOG_STD_SH_TECH_ACTION |
|
OSPF-4-INVALID_METRIC |
4-Warning |
OSPF-[dec] Area [chars]: Router [inet] originating invalid type [dec] LSA ID [inet] Metric [dec] on Link ID [inet] Link Type [dec] |
The router indicated in this message has originated an LSA with invalid metric. If this is an router LSA and link metric is zero there's a risk of routing loops and traffic loss in the network |
ospf |
"Configure valid metric for given LSA type and link type on " "the router originating reported LSA" |
|
OSPF-4-INVALIDKCKEYID |
4-Warning |
Key ID [dec] in key chain [chars] is invalid |
They Key ID configured in the key chain is out of range for OSPF. This may happen because the key chain allows Key ID values outside of the range which is acceptable for OSPF. |
ospf |
"Configure a new security association with a Key ID that is in " "the range 1-255" |
|
OSPF-4-INVALIDKCNAME |
4-Warning |
Key chain name [chars] on [chars] is invalid |
The key-chain name configured under OSPF interface does not match global key chain configuration. |
ospf |
"Fix configuration. Either remove ospf authentication command " "or configure key chain in global configuration mode." |
|
OSPF-4-INVALIDKEY |
4-Warning |
Key ID [dec] [chars]on interface [chars] |
The ID is not found in the configured key chain |
ospf |
"Configure a new security association with the Key ID" |
|
OSPF-4-NET_TYPE_MISMATCH |
4-Warning |
Received Hello from [inet] on [chars] indicating a potential \n\ network type mismatch |
OSPF received hello packet from a neighbor which has a non-zero \n\ value in the DR or BDR field but this router is configured as \n\ point-to-point on this interface. This indicates a network type \n\ mismatch. |
- |
"The network type must be configured the same for all devices \n\ attached to the same link." |
|
OSPF-4-NO_IPADDRESS_ON_INT |
4-Warning |
No IP address for interface [chars] |
Interface is not point-to-point and is unnumbered |
ospf |
"Change interface type or give the interface an IP address" |
|
OSPF-4-NO_OUTPUTQ |
4-Warning |
Packet not written to the output queue |
An internal error occurred. |
ospf |
LOG_STD_SH_TECH_ACTION |
|
OSPF-4-NONEIGHBOR |
4-Warning |
Received [chars] from unknown neighbor [inet] |
OSPF hello database description or database request packet was received but the router could not identify the sender. |
ospf |
"This situation should correct itself. " LOG_STD_RECUR_ACTION |
|
OSPF-4-NORTRID |
4-Warning |
OSPF process [dec] failed to allocate unique router-id and cannot start |
OSPF failed while attempting to allocate a unique router-id from the IP addresses of its interfaces. |
ospf |
"Ensure that at least one interface is active up and has a valid IP " |
|
OSPF-4-NOVALIDKEY |
4-Warning |
No valid authentication [chars]key is available on interface [chars] |
- |
ospf |
"Configure a new key" |
|
OSPF-4-NSSA_NO_FA |
4-Warning |
OSPF process [dec] lacks forwarding address for type 7 LSA [inet] in NSSA [chars] - P-bit cleared |
There is no viable forwarding address in the NSSA area. Hence the P-bit must be cleared and the type 7 LSA will not be translated to a type 5 LSA by the NSSA translator. Refer to RFC 3101. |
ospf |
"Configure at least one interface in the NSSA with " "an advertised IP address. A loopback is preferable " "since advertisement will not be dependent on the " "underlying layer 2 state." |
|
OSPF-4-NULL_LINKAGE |
4-Warning |
Doubly linked list linkage is NULL |
An internal error occurred. |
ospf |
LOG_STD_SH_TECH_ACTION |
|
OSPF-4-NULL_PREV_LINKAGE |
4-Warning |
Doubly linked list prev linkage is NULL [hec] |
An internal error occurred. |
ospf |
LOG_STD_SH_TECH_ACTION |
|
OSPF-4-OSPF_MAX_LSA |
4-Warning |
Maximum number of non self-generated LSA has been exceeded \ospf [dec]\ - [dec] LSAs |
Maximum number of non self-generated LSA has been exceeded |
ospf |
"Check if some router in the network is " "generating large number of LSAs as a result " "of misconfiguration" |
|
OSPF-4-OSPF_MAX_LSA_THR |
4-Warning |
Threshold for maximum number of non self-generated LSA has been reached \ospf [dec]\ - [dec] LSAs |
Threshold for maximum number of non self-generated LSA has been reached |
ospf |
"Check if some router in the network is " "generating large number of LSAs as a result " "of misconfiguration" |
|
OSPF-4-RTRID_IN_USE |
4-Warning |
Router-ID [inet] is in use by ospf process [dec] |
Attempted to assign a Router ID which is in use by another process |
ospf |
"Configure another Router ID for one of the " "processes." |
|
OSPF-4-SR_APP_GET_ATTR_FAIL |
4-Warning |
[chars] failed to get SR attributes from SR_APP with error [dec] |
OSPF process failed to get SR attributes. |
ospf |
"Reconfigure segment routing attributes." |
|
OSPF-4-SR_APP_REG_FAIL |
4-Warning |
[chars] failed to register with SR_APP with error [dec] |
OSPF process registration with SR APP failed. |
ospf |
"Reconfigure segment routing and Restart OSPF process." |
|
OSPF-4-SR_MFI_REG_FAIL |
4-Warning |
[chars] failed to register with MFI with error [dec] |
Disable/Re-Enable segment-routnig in this OSPF Process. |
ospf |
"Disable/Re-Enable segment-routing in this OSPF process." |
|
OSPF-4-UNREC_TIMER |
4-Warning |
Unrecognized timer [dec] in OSPF [chars] |
An internal error occurred. |
ospf |
LOG_STD_SH_TECH_ACTION |
|
OSPF-4-VIRTUAL_IN_NON_BACKBONE |
4-Warning |
Virtual link information found in non-backbone area: [chars] |
An internal software error has caused this router to generate a Router LSA that has a virtual link in a non-backbone area. |
ospf |
LOG_STD_SH_TECH_ACTION |
|
OSPF-5-ADJCHG |
5-Notice |
Process [dec] Nbr [inet] on [chars] from [chars] to [chars] [chars] |
An OSPF neighbor has changed state. The message describes the change and the reason for it. This message appears only if the <Bold>log-adjacency-changes<NoBold> command is configured for the OSPF process. |
ospf |
LOG_STD_NO_ACTION |
|
OSPF-5-EXPIREDKEY |
5-Notice |
Packet [chars] on interface [chars] with expired Key ID [dec]. |
The Key ID in use has a lifetime and the system time is not within that lifetime |
ospf |
"Configure a new key" |
|
OSPF-5-LASTKEYEXP |
5-Notice |
The last key has expired for interface [chars] packets sent using last valid key. |
None of the security associations have a lifetime that include the current system time. |
ospf |
"Configure a new security association or alter the lifetime of a " "current security association" |
|
OSPF-5-NOCRYPTOALG |
5-Notice |
Key ID [dec] in key chain [chars] does not have a cryptographic algorithm |
OSPF has been configured to use cryptographic authentication however an algorithm has not been configured |
ospf |
"Configure a cryptographic-algorithm for the security association" |
|
OSPF-5-NOKEY |
5-Notice |
Key ID [dec] in key chain [chars] does not have a key |
OSPF has been configured to use cryptographic authentication however an key password has not been configured |
ospf |
"Configure a key for the security association" |
|
OSPF-6-AREACHG |
6-Information |
[inet]%m changed from area [chars] to area [chars] |
An OSPF configuration change has caused a network range to change areas. |
ospf |
LOG_STD_NO_ACTION |
|
OSPF-6-BAD_LSA_COUNT |
6-Information |
OSPF-[dec] Area [chars]: LSA ID [inet] Type [dec] Adv-rtr [inet] LSA counter [chars] |
An internal error has been self corrected. There's no operational impact related to this error message. |
ospf |
show tech-support ospf |
|
OSPF-6-BADCHKSUM |
6-Information |
Checksum Failure in database in area [chars]\n Link State Id [inet] Old Checksum [hex] New Checksum [hex]\n |
OSPF has detected a checksum error in the database due to memory corruption. |
ospf |
"Restart OSPF process." |
|
OSPF-6-DFT_OPT |
6-Information |
Protocol timers for fast convergence are [chars]. |
Routing-default-optimize state |
ospf |
LOG_STD_ACTION |
|
OSPF-6-DISTLS_DUPID |
6-Information |
OSPF-[dec] is already using Link state distribution instance [dec]. Please configure a unique value |
Link state distribution instance-id should be unique across all OSPF instances |
ospf |
LOG_STD_NO_ACTION |
|
OSPF-6-LRIB_WRONG_REFCNT |
6-Information |
[chars] Invalid reference count for [chars] |
Negative database reference count |
ospf |
show tech-support ospf |
|
OSPF-6-MODECHG |
6-Information |
Base topology enabled on interface [chars] attached to MTR compatible mode area [chars] |
OSPF Interfaces attached to MTR compatible OSPF areas require the base topology to be enabled |
ospf |
LOG_STD_NO_ACTION |
|
OSPF-6-NSF_COMPLETE |
6-Information |
OSPF-[dec] NSF completed |
NSF completed notification |
ospf |
LOG_STD_NO_ACTION |
|
OSPF-6-NSF_START |
6-Information |
OSPF-[dec] NSF started |
NSF start notification |
ospf |
LOG_STD_NO_ACTION |
|
OSPF-6-NSF_TERMINATE |
6-Information |
OSPF-[dec] NSF terminated |
NSF terminated notification |
ospf |
LOG_STD_NO_ACTION |
|
OSPF-6-PROC_REM_FROM_INT |
6-Information |
OSPF process [dec] removed from interface [chars] |
The OSPF process was removed from the interface due to IP VRF removal. |
ospf |
LOG_STD_NO_ACTION |
|
OSPF-6-RTR_WRONG_REFCNT |
6-Information |
OSPF-[dec] Invalid reference count for [inet] |
Negative database reference count |
ospf |
show tech-support ospf |
|
OSPF-6-SRMS_DB_FREE |
6-Information |
[chars] LSA [dec]/[inet]/[inet] freed while linked to srms entry [inet]/[dec] range [dec] |
OSPF process free LSA which is still linked to SRMS. \n Necessary actions has been taken and message has no functional impact |
ospf |
"Contact your Cisco technical support representative." |
|
OSPF-6-UNREC_VIRT_INT_TYPE |
6-Information |
Unrecognized virtual interface [chars]. Treat it as loopback stub route |
The virtual interface type was not recognized by OSPF so it will be treated as a loopback interface stub route. |
ospf |
LOG_STD_NO_ACTION |
|
OSPF-6-ZERO_BANDWIDTH |
6-Information |
interface [chars] has zero bandwidth |
The interface has reported its bandwidth as zero. |
ospf |
LOG_STD_NO_ACTION |
|
OSPFv3-3-CF_NOMEM |
3-Error |
Unable to allocate checkpoint buffer: [chars] |
NSR operation may be degraded to a lack of memory. |
ospf |
show tech-support ospfv3 |
|
OSPFv3-3-CF_NOMSG |
3-Error |
No space in checkpoint buffer |
NSR operation may be degraded to a lack of memory. |
ospf |
show tech-support ospfv3 |
|
OSPFv3-3-CFG_NBR_ALLOC_FAILED |
3-Error |
[chars] Could not allocate or find the neighbor |
An internal error occurred. |
ospf |
LOG_STD_ACTION |
|
OSPFv3-3-CFG_OSPF_FAILED |
3-Error |
Only [dec] OSPFv3 process is allowed |
The maximum number of OSPFv3 instances permitted for this IOS image has been reached |
- |
"Upgrade to an unrestricted IOS image" |
|
OSPFv3-3-CHKPT_IDB_DECODE_FAIL |
3-Error |
Interface cannot be decoded for NSR: [chars] |
Adjacency and interface information for an interface cannot be checkpointed due to an interface decoding error. |
ospf |
"Please verify that this interface type is supported for NSR in " "this release. If so report the problem to the TAC." |
|
OSPFv3-3-CHKPT_IDB_ENCODE_FAIL |
3-Error |
Interface [chars] cannot be encoded for NSR |
Adjacency and interface information learned from this interface cannot be checkpointed due to an interface encoding error. |
ospf |
"Please verify that this interface type is supported for NSR in " "this release. If so report the problem to the TAC." |
|
OSPFv3-3-CHKPT_MSG |
3-Error |
Invalid checkpoint message: [chars] [chars] |
NSR will not operate due to an error in a checkpoint message. |
ospf |
show tech-support ospfv3 |
|
OSPFv3-3-CHKPT_MSG_LOST |
3-Error |
Checkpoint message lost |
NSR will not operate due to a dropped checkpoint message. |
ospf |
show tech-support ospfv3 |
|
OSPFv3-3-CHKPT_NOMEM |
3-Error |
Unable to allocate checkpoint queue entry |
NSR will not operate due to a failure communicating with the standby. |
ospf |
show tech-support ospfv3 |
|
OSPFv3-3-CHKPT_SEND_FAIL |
3-Error |
Checkpoint message send failed: [chars] |
NSR will not operate due to a failure communicating with the standby. |
ospf |
show tech-support ospfv3 |
|
OSPFv3-3-CHKPT_STATUS_LOST |
3-Error |
Checkpoint status lost |
NSR will not operate due to a missing checkpoint status message. |
ospf |
show tech-support ospfv3 |
|
OSPFv3-3-CHKPT_STBY_LSDB_INVALID |
3-Error |
Standby link-state database validation failed expected/found count: [dec]/[dec] chksum: 0x%llx/0x%llx |
NSR will not operate due to an error on the standby. |
ospf |
show tech-support ospfv3 |
|
OSPFv3-3-CHKPT_STBY_NO_LSA_BUFFER |
3-Error |
Standby synchronization error: no LSA buffer |
NSR will not operate due to an internal error. |
ospf |
show tech-support ospfv3 |
|
OSPFv3-3-CHKPT_STBY_NO_LSDB |
3-Error |
Standby synchronization error: could not add lsa type [dec] |
NSR will not operate due to an internal error. |
ospf |
show tech-support ospfv3 |
|
OSPFv3-3-CHKPT_STBY_NO_NBR |
3-Error |
Standby synchronization error: could not find neighbor [chars] [inet] %P |
NSR will not operate due to an internal error. |
ospf |
show tech-support ospfv3 |
|
OSPFv3-3-CHKPT_STBY_SYNC_LOST |
3-Error |
Standby synchronization lost for OSPFv3-[dec] AFI [chars] VRF [chars] was: [chars] |
Synchronization between the active and standby OSPFv3 has been lost. |
ospf |
show tech-support ospfv3 |
|
OSPFv3-3-DBEXIST |
3-Error |
[chars] DB already exist : area [chars] lsid [inet] adv [inet] type 0x[hec] |
OSPF has a problem locating the LSA which could lead to a memory leak. |
ospf |
LOG_STD_SH_TECH_ACTION |
|
OSPFv3-3-INIT_IDB |
3-Error |
OSPF is enabled on [chars] during idb initialization |
An internal error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
OSPFv3-3-INT_ATTACHED_MULTI_AREAS |
3-Error |
[chars] Interface [chars] is attached to more than one area |
The interface is on the interface list for an area other than the one which the interface links to. |
ospf |
LOG_STD_SH_TECH_ACTION |
|
OSPFv3-3-INT_INIT_FAILED |
3-Error |
[chars] Init failed for interface [chars] [chars]. |
The interface initialization failed. Possible reasons: 1 The area to which the interface is being attached is being |
ospf |
"Remove the configuration command that covers the interface " "and then try it again. " LOG_STD_RECUR_ACTION |
|
OSPFv3-3-INTERNALERR |
3-Error |
[chars] Internal error: [chars] [chars] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
OSPFv3-3-INVALID_ENCR_KEY |
3-Error |
Invalid encrypted key [chars]. |
The specified encrypted key is not valid. |
- |
"Either specify a cleartext key and enter the <CmdBold>service " "password-encryption<NoCmdBold> command for encryption or ensure " "that the specified encrypted key is valid. If the specified " "encrypted key is not valid an error message will be displayed " "during system configuration." |
|
OSPFv3-3-IPSEC_CLOSE_SS_ERROR |
3-Error |
[chars] Unable to close secure socket with SPI [dec] on interface [chars] |
An IPsec API error occurred. This message indicates an internal error |
- |
LOG_STD_RECUR_ACTION |
|
OSPFv3-3-IPSEC_CREATE_POLICY_ERROR |
3-Error |
[chars] [chars] error occured when attempting to create an IPsec policy for SPI [dec] |
An IPsec API error occurred. This message indicates an internal error |
- |
LOG_STD_RECUR_ACTION |
|
OSPFv3-3-IPSEC_ERROR_MSG_ABORT |
3-Error |
[chars] IPsec sent a [chars] message [chars] to OSPFv3 for interface [chars]. Recovery aborted |
An internal software error has occurred. The maximum number of recovery attempts have been exceeded. |
- |
LOG_STD_SH_TECH_ACTION |
|
OSPFv3-3-IPSEC_ERROR_MSG_RETRY |
3-Error |
[chars] IPsec sent a [chars] message [chars] to OSPFv3 for interface [chars]. Recovery attempt [dec] |
An internal error occurred. The system is attempting to re-open the secure socket. |
- |
"The system is attempting to recover. No action needs to be taken." |
|
OSPFv3-3-IPSEC_GENERAL_ERROR |
3-Error |
IPsec reported a GENERAL ERROR: message [chars] count [dec] |
An internal error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
OSPFv3-3-IPSEC_POLICY_ALREADY_EXIST |
3-Error |
[chars] SPI [dec] is already in use with ospf |
An attempt was made to use a SPI that has already been used. |
- |
"Choose a different SPI" |
|
OSPFv3-3-IPSEC_POLICY_INVALID_KEY_LEN |
3-Error |
[chars] The key length used with SPI [dec] is not valid |
The key length was incorrect. |
- |
"Choose a valid IPsec key. An IPsec authentication key must be " "32MD5 or 40SHA-1 hexidecimal digits long." |
|
OSPFv3-3-IPSEC_POLICY_NOT_EXIST |
3-Error |
SPI [dec] is not being used by ospf process [chars]. |
An attempt was made to unconfigure a SPI that is not being used with OSPFv3. |
- |
"Enter a show command to see which SPIs are used by OSPFv3" |
|
OSPFv3-3-IPSEC_POLICY_SPI_IN_USE |
3-Error |
[chars] SPI [dec] is already in use by a process other than ospf |
An attempt was made to use a SPI that has already been used. |
- |
"Choose a different SPI. Enter the <CmdBold>show crypto ipv6 " "ipsec sa<NoCmdBold> command to view a list of SPIs that are " "already being used." |
|
OSPFv3-3-IPSEC_POLICY_SPI_REUSE |
3-Error |
[chars] [chars] is already configured with SPI [dec]. |
An attempt was made to use a SPI that has already been used |
- |
"Unconfigure the SPI first or choose a different one." |
|
OSPFv3-3-IPSEC_POLICY_STILL_IN_USE |
3-Error |
[chars] The policy for SPI [dec] could not be removed because it is in use. |
An attempt was made to remove the policy for the indicated SPI but the policy was still being used by a secure socket. |
- |
LOG_STD_NO_ACTION |
|
OSPFv3-3-IPSEC_REGISTER_CLIENT |
3-Error |
OSPFv3 was unable to register with IPsec |
An internal error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
OSPFv3-3-IPSEC_REMOVE_POLICY_ERROR |
3-Error |
[chars] [chars] error occured when attemtping to remove the IPsec policy with SPI [dec] |
An IPsec API error occurred. This message indicates an internal error |
- |
LOG_STD_RECUR_ACTION |
|
OSPFv3-3-ISSU_NEGOTIATION |
3-Error |
ISSU negotiation[chars] error: [dec] [chars] |
The OSPFv3 ISSU session could not complete negotiation. This 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. |
ospf |
LOG_STD_ACTION |
|
OSPFv3-3-NO_SNMP_IFINDEX |
3-Error |
Interface [chars] does not have an SNMP MIB ifIndex and has been disabled |
The OSPF process has been configured to use the SNMP MIB ifIndex\n\ valuefor the interface IDs. However the ifIndex is not set on this\n\ interface so the interface can not be enabled. |
- |
"Unconfigure interface-id snmp-if-index for this OSPF process" |
|
OSPFv3-3-NOBACKBONE |
3-Error |
[chars] Flagged as being an ABR without a backbone area |
- |
- |
"Restart the OSPF process." |
|
OSPFv3-3-NOSTART |
3-Error |
Unable to start process: [chars] |
An internal software error occurred. |
ospf |
LOG_STD_ACTION |
|
OSPFv3-3-NSR_FAILED |
3-Error |
NSR can not recover checkpointed data for process [dec] |
An NSR failover could not be performed because OSPFv3 on the standby was not synchronized |
ospf |
show tech-support ospfv3 |
|
OSPFv3-3-RECONF_VL |
3-Error |
Process [chars] is changing router-id. Reconfigure virtual link neighbors with our new router-id |
OSPF process is being reset and it is going to select a new router-id. This will bring down all virtual links. To make them work again virtual link configuration needs to be changed on all virtual link neighbors. |
- |
"Change virtual link configuration on all the virtual link " "neighbors to reflect our new router-id." |
|
OSPFv3-4-AREA_MISMATCH |
4-Warning |
[chars] Received packet with incorrect area from %P [chars] area [inet] packet area [inet] |
An OSPF packet was received with an area ID in its header which does not match the area of this interface. |
- |
"Check the OSPF configuration of the receiver and the sender " "for inconsistency." |
|
OSPFv3-4-ASBR_WITHOUT_VALID_AREA |
4-Warning |
Router [chars] is currently an ASBR while having only one area which is a stub area |
An ASBR must be attached to an area which can carry AS External or NSSA LSAs |
ospf |
"Make the area to which the router is attached into an NSSA " "or regular area." |
|
OSPFv3-4-BADLENGTH |
4-Warning |
[chars] Invalid length [dec] in [chars] OSPF packet type [dec] from %P ID [inet] [chars] |
- |
- |
- |
|
OSPFv3-4-BADLSATYPE |
4-Warning |
[chars] Invalid lsa: [chars]: Type 0x[hec] Length 0x[hec] LSID [dec] from [inet] %P [chars] |
The router received an LSA with invalid data. LSA contains invalid LSA type wrong checksum or wrong length. The cause is either memory corruption or unexpected behavior on a router. |
- |
"From a neighboring address locate the problem router.\n" "1 Collect a running configuration of the router by entering the" |
|
OSPFv3-4-CF_UNKNOWN_STATUS |
4-Warning |
Unknown checkpoint status: [dec] |
An internal error occured. |
ospf |
show tech-support ospfv3 |
|
OSPFv3-4-CHKPT_MSG_SEQ |
4-Warning |
Invalid checkpoint message sequence number: received [dec] expected [dec] |
NSR has detected a duplicate checkpoint message. |
ospf |
show tech-support ospfv3 |
|
OSPFv3-4-CHKPT_UNKNOWN_TYPE |
4-Warning |
Invalid checkpoint message type: [dec] |
An internal error occurred. |
ospf |
show tech-support ospfv3 |
|
OSPFv3-4-DB_NOT_FOUND |
4-Warning |
[chars] Can't find LSA database type [hec] area [chars] interface [chars] |
An internal error occured. |
ospf |
LOG_STD_SH_TECH_ACTION |
|
OSPFv3-4-DBD_ALLOC_FAIL |
4-Warning |
[chars] Could not allocate DBD packet |
An internal error occurred. |
ospf |
LOG_STD_SH_TECH_ACTION |
|
OSPFv3-4-DUP_RTRID_AREA |
4-Warning |
[chars] Detected router with duplicate router ID [inet] in area [chars] |
OSPF received hello packet from a neighbor which has the same\n\ router-id as this routing process. A full adjacency cannot be \n\ established. |
- |
"OSPF router-id should be unique. Change the neighbors router-id" |
|
OSPFv3-4-DUP_RTRID_NBR |
4-Warning |
[chars] detected duplicate router-id [inet] from %P on interface [chars] |
- |
- |
- |
|
OSPFv3-4-ERRRCV |
4-Warning |
[chars] Received invalid packet: [chars] from %P [chars] |
An invalid OSPF packet was received. Details are included in the error\n\ message. The cause might be a misconfigured OSPF or an internal error\n\ in the sender. |
- |
"Check the OSPF configuration of the receiver and the sender for\n\ inconsistency." |
|
OSPFv3-4-INV_LSA_BLD_FLG |
4-Warning |
[chars] Invalid build flag [hec] for LSA [inet] type 0x[hec] |
An internal error occurred. |
ospf |
LOG_STD_SH_TECH_ACTION |
|
OSPFv3-4-INVALID_METRIC |
4-Warning |
[chars] Area [chars]: Router [inet] originating invalid type 0x[hec] LSA ID [dec] Metric [dec] on Link ID [dec] Link Type [dec] |
The router indicated in this message has originated an LSA with invalid metric. If this is an router LSA and link metric is zero there's a risk of routing loops and traffic loss in the network |
ospf |
"Configure valid metric for given LSA type and link type on " "the router originating reported LSA" |
|
OSPFv3-4-INVALIDKCKEYID |
4-Warning |
Key ID [dec] in key chain [chars] is invalid |
They Key ID configured in the key chain is out of range for OSPF. This may happen because the key chain allows Key ID values outside of the range which is acceptable for OSPFv3. |
ospf |
"Configure a new security association with a Key ID that is in " "the range 1-65535" |
|
OSPFv3-4-INVALIDKCNAME |
4-Warning |
Key chain name [chars] is invalid |
The key-chain name configured under OSPF interface does not match global key chain configuration. |
ospf |
"Fix configuration. Either remove ospf authentication command " "or configure key chain in global configuration mode." |
|
OSPFv3-4-INVALIDSAID |
4-Warning |
SA ID '0' [chars]on interface [chars] |
The SA ID '0' is considered invalid |
ospf |
"Configure a new security association with the valid Key ID" |
|
OSPFv3-4-MANET_VER_MISMATCH |
4-Warning |
Non-standard MANet implementation detected on neighbor [inet] |
An OSPF packet was received with LLS data but without a Type 1 Extended Options and Flags TLV indicating an older MANet implementation. |
- |
"Check the version of software running on the neighbor." |
|
OSPFv3-4-MAX_LSA_LIM |
4-Warning |
[chars] Maximum number of non self-generated LSA has been exceeded - [dec] LSAs |
Maximum number of non self-generated LSA has been exceeded |
ospf |
"Check if some router in the network is generating large number of " "LSAs as a result of misconfiguration" |
|
OSPFv3-4-MAX_LSA_THR |
4-Warning |
[chars] Threshold for maximum number of non self-generated LSA has been reached - [dec] LSAs |
Threshold for maximum number of non self-generated LSA has been reached |
ospf |
"Check if some router in the network is generating large number of " "LSAs as a result of misconfiguration" |
|
OSPFv3-4-NET_TYPE_MISMATCH |
4-Warning |
Received Hello from [inet] on [chars] indicating a potential \n\ network type mismatch |
OSPF received hello packet from a neighbor which has a non-zero \n\ value in the DR or BDR field but this router is configured as \n\ point-to-point on this interface. This indicates a network type \n\ mismatch. |
- |
"The network type must be configured the same for all devices \n\ attached to the same link." |
|
OSPFv3-4-NO_GLOBAL_ADDR |
4-Warning |
[chars] Could not select a global IPv6 address. Virtual links require at least one global IPv6 address. |
A virtual link was configured. For the virtual link to function a global IPv6 address must be available. However no global IPv6 address could be found on the router. |
ospf |
"Configure a global IPv6 address on an interface on this router." |
|
OSPFv3-4-NO_OUTPUTQ |
4-Warning |
[chars] Packet not written to the output queue |
An internal error occurred. |
ospf |
LOG_STD_SH_TECH_ACTION |
|
OSPFv3-4-NONEIGHBOR |
4-Warning |
[chars] Received [chars] from unknown neighbor [inet] |
OSPF hello database description or database request packet was\n\ received but the router could not identify the sender. |
- |
"This situation should correct itself. " LOG_STD_RECUR_ACTION |
|
OSPFv3-4-NORTRID |
4-Warning |
Process [chars] could not pick a router-id please configure manually |
OSPFv3 failed while attempting to allocate a router ID from the IP\n\ address of one of its interfaces. |
- |
"Ensure that at least one interface is active up and has a valid IP " |
|
OSPFv3-4-NOVALIDKEY |
4-Warning |
No valid authentication key under key-chain [chars] |
- |
ospf |
"Configure a new key" |
|
OSPFv3-4-NSSA_NO_FA |
4-Warning |
[chars] Process lacks forwarding address for type 7 LSA [inet] in NSSA [chars] - P-bit cleared |
There is no viable forwarding address in the NSSA area. Hence the P-bit must be cleared and the type 7 LSA will not be translated to a type 5 LSA by the NSSA translator. Refer to RFC 3101. |
ospf |
"Configure at least one interface in the NSSA with " "an advertised IPv4 for IPv4 address family or IPv6 global " |
|
OSPFv3-4-UNREC_TIMER |
4-Warning |
[chars] Unrecognized timer [dec] in OSPF [chars] |
An internal error occurred. |
ospf |
LOG_STD_SH_TECH_ACTION |
|
OSPFv3-4-VIRTUAL_IN_NON_BACKBONE |
4-Warning |
[chars] Virtual link information found in non-backbone area: [chars] |
An internal error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
OSPFv3-5-ADJCHG |
5-Notice |
Process [dec][chars][chars] Nbr [inet] on [chars] from [chars] to [chars] [chars] |
An OSPF neighbor has changed state. The message describes \n\ the change and the reason for it. This message appears only \n\ if the <Bold>log-adjacency-changes<NoBold> command is\n\ configured for the OSPF process. |
- |
LOG_STD_NO_ACTION |
|
OSPFv3-5-EXPIREDKEY |
5-Notice |
Packet [chars] on interface [chars] with expired Key ID [dec]. |
The Key ID in use has a lifetime and the system time is not within that lifetime |
ospf |
"Configure a new key" |
|
OSPFv3-5-INVALIDSADATA |
5-Notice |
Key chain [chars] key [dec]. Data not valid to [chars] packet on [chars] |
OSPFv3 has been configured to use cryptographic authentication using key-chain configuration option. SA data are not however completelly valid and can not be used to authenticate sent packet or verify received received packet |
ospf |
"Verify global key chain configuration. Is it configured with " "key ID and algoritm supported by OSPFv3 and is key string specified?" |
|
OSPFv3-5-LASTKEYEXP |
5-Notice |
The last key has expired in key-chain [chars]. |
None of the security associations have a lifetime that include the current system time. |
ospf |
"Configure a new security association or alter the lifetime of a " "current security association" |
|
OSPFv3-5-NOCRYPTOALG |
5-Notice |
Key ID [dec] in key chain [chars] does not have a valid cryptographic algorithm |
OSPF has been configured to use cryptographic authentication however an algorithm has not been configured |
ospf |
"Configure a cryptographic-algorithm for the security association" |
|
OSPFv3-5-NOKEY |
5-Notice |
Key ID [dec] in key chain [chars] does not have a key |
OSPF has been configured to use cryptographic authentication however an key password has not been configured |
ospf |
"Configure a key for the security association" |
|
OSPFv3-6-BADCHKSUM |
6-Information |
[chars] Checksum Failure in database in area [chars]: LSA Type [hec] Link State Id [inet] Old Checksum [hex] New Checksum [hex]\n |
OSPF has detected a checksum error in the database due to memory\n\ corruption. |
- |
"Restart OSPF process." |
|
OSPFv3-6-DFT_OPT |
6-Information |
Protocol timers for fast convergence are [chars]. |
Routing-default-optimize state |
ospf |
LOG_STD_ACTION |
|
OSPFv3-6-INPUT_TO_BE_DEPRECATED |
6-Information |
[chars] will be deprecated |
The value will be deprecated in a future version |
ospf |
"Refer to current command reference" |
|
OSPFv3-6-NSF_COMPLETE |
6-Information |
OSPFv3-[dec] NSF completed |
NSF completed notification |
ospf |
LOG_STD_NO_ACTION |
|
OSPFv3-6-NSF_START |
6-Information |
OSPFv3-[dec] NSF started |
NSF start notification |
ospf |
LOG_STD_NO_ACTION |
|
OSPFv3-6-NSF_TERMINATE |
6-Information |
OSPFv3-[dec] NSF terminated |
NSF terminated notification |
ospf |
LOG_STD_NO_ACTION |
|
OSPFv3-6-SHUTDOWN_COMPLETE |
6-Information |
[chars] Shutdown completed |
OSPFv3 process has finished the shutdown procedure. |
- |
LOG_STD_NO_ACTION |
|
OSPFv3-6-SHUTDOWN_START |
6-Information |
[chars] Shutdown started |
OSPFv3 process has started the shutdown procedure. Another message will be logged when it completes. |
- |
"Wait for shutdown to complete." |
|
OSPFv3-6-UNEXPECTED_MESSAGE |
6-Information |
OSPFv3 has received an unexpected message: %0x / %0x |
OSPFv3 has received an unexpected interprocess message. |
- |
LOG_STD_SH_TECH_ACTION |
|
OSPFv3-6-UNPROCESSED_IPV4_CALLBACK |
6-Information |
IPv4 process call ignored. |
An internal error occurred. |
ospf |
LOG_STD_ACTION |
|
OSPFv3-6-UNREC_VIRT_INT_TYPE |
6-Information |
Unrecognized virtual interface [chars]. Treat it as loopback stub route |
The virtual interface type was not recognized by OSPFv3 so it will be treated as a loopback interface stub route. |
ospf |
LOG_STD_NO_ACTION |
|
OSPFv3-6-ZERO_BANDWIDTH |
6-Information |
[chars] interface [chars] has zero bandwidth |
The interface reports its bandwidth as zero. |
- |
LOG_STD_NO_ACTION |
|
OTNMGR-3-OTN_STATS_CREATE_IF_FAIL |
3-Error |
stats for interface index [dec] could not be created with status [dec] |
- |
snmp-otn |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
OTNMGR-3-OTN_STATS_CREATE_IF_FAILED_TO_ALLOCATE |
3-Error |
stats for interface index [dec] could not be created with status [dec] |
- |
snmp-otn |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
OTNMGR-3-OTN_STATS_DELETE_IF_FAIL |
3-Error |
stats for interface index [dec] could not be deleted with status [dec] |
- |
snmp-otn |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
OTV_APP-3-INVALID_CLIENT_REG |
3-Error |
OTV was unable to register with RIB |
This is an RIB error triggered when an OTV Application routine tried to register as a client with MLRIB. |
ios-otv-app |
"This error message likely indicates an internal IOS " "software issue. As a result the internal state of " "the device may now be incorrect and one should " "reboot the device. If this continues use the " "Cisco software defect search tool to " "determine if this issue has been " "fixed in a later software release. If no defect is " "found then please contact your Cisco technical " "support representative and provide the " "representative with the exact error message seen " "as well as the version of IOS being used." |
|
OTV_APP-3-INVALID_DELETE_MAC_FLOOD |
3-Error |
otv mac flood [enet] was not deleted from the RIB the return code was [hec] |
This is a RIB error which was triggered when an OTV Application routine tried to delete a route to the data base. |
ios-otv-app |
"This error message likely indicates an internal IOS " "software issue. As a result the internal state of " "the device may now be incorrect and one should " "reconfigure otv mac flood and try deleting it. If " "this error continues use the Cisco software defect " "search tool to determine if this issue has been " "fixed in a later software release. If no " "defect is found then please contact your " "Cisco technical support representative and " "provide the representative with the exact error " "message seen as well as the version of IOS being " "used." |
|
OTV_APP-3-INVALID_EVENT_THREAD |
3-Error |
An OTV Application routine was called by an invalid thread |
This is an internal error triggered when an OTV Application routine is called incorrectly. |
ios-otv-app |
"This error message likely indicates an internal IOS " "software issue. As a result the internal state of " "the device may now be incorrect and a reboot of the " "device should be performed. Use the Cisco software " "defect search tool to determine if this issue has " "been fixed in a later software release. If no " "defect is found then please contact your Cisco " "technical support representative and provide the " "representative with the exact error message seen " "as well as the version of IOS being used." |
|
OTV_APP-3-INVALID_MCAST_MAPPING |
3-Error |
OTV was unable to process ISIS mapping received |
This is an ISIS error triggered when an ISIS tries to send an invalid mapping to OTV. |
ios-otv-app |
"This error message likely indicates an internal IOS " "software issue. As a result the internal state of " "the device may now be incorrect and one should " "reboot the device. If this continues use the " "Cisco software defect search tool to " "determine if this issue has been " "fixed in a later software release. If no defect is " "found then please contact your Cisco technical " "support representative and provide the " "representative with the exact error message seen " "as well as the version of IOS being used." |
|
OTV_APP-3-INVALID_ROUTE_REDIST_REG |
3-Error |
OTV was unable to register for route redistribution |
This is a RIB error which was triggered when an OTV Application routine tried to send a redistribution request. |
ios-otv-app |
"This error message likely indicates an internal IOS " "software issue. As a result the internal state of " "the device may now be incorrect and one should " "reconfigure the overlay. If this continues " "use the Cisco software defect search tool " "to determine if this issue has been " "fixed in a later software release. If no defect is " "found then please contact your Cisco technical " "support representative and provide the " "representative with the exact error message seen " "as well as the version of IOS being used." |
|
OTV_APP-3-INVALID_UPDATE_MAC_FLOOD |
3-Error |
otv mac flood [enet] was not added to the RIB the return code was [hec] |
This is a RIB error whic was triggered when an OTV Application routine tried to add a route to the data base. |
ios-otv-app |
"This error message likely indicates an internal IOS " "software issue. As a result the internal state of " "the device may now be incorrect and one should " "reconfigure otv mac flood. If this error continues " "to occur use the Cisco software defect search " "tool to determine if this issue has been " "fixed in a later software release. If no defect is " "found then please contact your Cisco technical " "support representative and provide the " "representative with the exact error message seen " "as well as the version of IOS being used." |
|
OUNIC-4-APIERR |
4-Warning |
[chars][chars]: [chars] |
RSVP API routine return error |
ocp |
"Copy the error message exactly as it appears and " "report it to your technical support representative." |
|
OUNIC-4-PORTERR |
4-Warning |
failed getting local_port_id for: neighor [inet] remote_port_id=[dec] |
An LMP state machine has encountered an event that is not legal or allowed in the current state. |
ocp |
"Write down the state and the event and " "call your Cisco technical support representative for assistance " |
|
OUNIC-4-QERR |
4-Warning |
[chars] |
IOS OS API routine return error |
ocp |
"Copy the error message exactly as it appears and " "report it to your technical support representative." |
|
OUTPUT_CLK_SEL-3-GEN_FRM_FRCL |
3-Error |
BITS Framer Receive Carrier Loss |
This msg reports interrupt changes |
- |
LOG_STD_NO_ACTION |
|
OUTPUT_CLK_SEL-3-GEN_FRM_RLOS |
3-Error |
BITS Receive Loss of Sync |
This msg reports interrupt changes |
- |
LOG_STD_NO_ACTION |
|
OUTPUT_CLK_SEL-3-GEN_FRM_RUA1 |
3-Error |
BITS Receive Unframed All One's T1 Blue Alarm E1 AIS |
This msg reports interrupt changes |
- |
LOG_STD_NO_ACTION |
|
OUTPUT_CLK_SEL-6-T4DPLL_CLK_STATE_CHANGE |
6-Information |
Output clock state changed to [chars]. |
Output clock state changed. |
ran-opt |
LOG_STD_NO_ACTION |
|
PA_PKT_PROXY-2-PROXY_IPC_INIT_FAILED |
2-Critical |
[dec] |
Could not initialize IPC handler. |
cpp-ucode |
LOG_STD_ACTION |
|
PA_PKT_PROXY-3-PROXY_IPC_EXTENDED_PKT_MEM_INIT_FAILED |
3-Error |
[dec] |
Initialization of extended packet memory failed. |
cpp-ucode |
LOG_STD_ACTION |
|
PA_PKT_PROXY-3-PROXY_IPC_INVALID_MSG |
3-Error |
[dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Invalid length for IPC message. |
cpp-ucode |
LOG_STD_ACTION |
|
PA_PKT_PROXY-3-PROXY_IPC_PBUF_EXTEND_FAILED |
3-Error |
[dec] |
Extending of packet buffer header memory failed. |
cpp-ucode |
LOG_STD_ACTION |
|
PA_PKT_PROXY-3-PROXY_IPC_PBUF_MEM_INIT_FAILED |
3-Error |
[dec] |
Initialization of packet buffer header memory failed. |
cpp-ucode |
LOG_STD_ACTION |
|
PA_PKT_PROXY-3-PROXY_IPC_PKT_DRAM_EXTEND_FAILED |
3-Error |
[dec] |
Extending of extended packet memory failed. |
cpp-ucode |
LOG_STD_ACTION |
|
PA_PKT_PROXY-3-PROXY_IPC_SEG_DLIST_EXTEND_FAILED |
3-Error |
[dec] |
Extending of segmented packet dlist memory failed. |
cpp-ucode |
LOG_STD_ACTION |
|
PA_PKT_PROXY-3-PROXY_IPC_SEG_DLIST_MEM_INIT_FAILED |
3-Error |
[dec] |
Initialization of segmented packet dlist memory failed. |
cpp-ucode |
LOG_STD_ACTION |
|
PA_PKT_PROXY-4-PROXY_IPC_UNKNOWN_SUBTYPE |
4-Warning |
[dec] |
Unknown IPC message detected. |
cpp-ucode |
LOG_STD_ACTION |
|
PA_PKT-3-PA_ADJUST_FIRST_FRAG_FAILURE |
3-Error |
[chars] |
PA unaware feature doing pkt_head_clip more than first pbuf on PA pkt. |
cpp-ucode |
LOG_STD_ACTION |
|
PA_PKT-3-PA_DLIST_MEM_REQ_FAILED |
3-Error |
- |
Failure occurred when attempting to request segmented packet memory. |
cpp-ucode |
LOG_STD_ACTION |
|
PA_PKT-3-PA_MCST_DUP_FAILURE |
3-Error |
[chars] |
PA M-Cast replication failed to allocate duplicate the requisite PA structures. |
cpp-ucode |
LOG_STD_ACTION |
|
PA_PKT-3-PA_MCST_GPM_ALLOC_FAILURE |
3-Error |
[chars] |
PA M-Cast replication failed to allocate required GPM. |
cpp-ucode |
LOG_STD_ACTION |
|
PA_PKT-3-PA_MCST_REPL_DESC_OVERFL |
3-Error |
[chars] |
PA M-Cast Gather descriptor list exceeded limit of 255 entries. |
cpp-ucode |
LOG_STD_ACTION |
|
PA_PKT-3-PA_PUT_FAILURE |
3-Error |
[chars] |
The PA API layer failed to complete a requested WRITE into pkt memory. |
cpp-ucode |
LOG_STD_ACTION |
|
PA_PKT-3-PA_VFR_CALLBACK_ARGS_ERROR |
3-Error |
[chars] 0x[hec] |
PA vFR callback input args error. |
cpp-ucode |
LOG_STD_ACTION |
|
PA_PKT-5-PA_DLIST_ALLOC_FAILED |
5-Notice |
- |
Could not allocate segmented packet list header. |
cpp-ucode |
LOG_STD_ACTION |
|
PA-0-RUPTCONFLICT |
0-Emergency |
Conflict detected when trying to install [chars] interrupt handler bay [dec]. |
An attempt was made to register an interrupt handler for\n\ either a non existent port adaptor or the wrong interrupt\n\ prority level. |
- |
LOG_STD_ACTION |
|
PA-2-BADDAT |
2-Critical |
PA interface data incorrect [hex] |
Incorrect PA interface data found |
- |
LOG_STD_ACTION |
|
PA-2-BADIDB |
2-Critical |
PA interface idb incorrect [hex] |
The port adapter system control block PASCB data structure |
- |
LOG_STD_ACTION |
|
PA-2-BADINTERFACE |
2-Critical |
Out of range PCI Port Adaptor interface [dec] on bay [dec] |
The software specified an out-of-range port adapter interface. |
- |
LOG_STD_ACTION |
|
PA-2-BADPA |
2-Critical |
PA interface pa incorrect [hex] |
Incorrect PA interface specified |
- |
LOG_STD_ACTION |
|
PA-2-BADPA2 |
2-Critical |
PA null adapter [hex] |
Null PA interface specified |
- |
LOG_STD_ACTION |
|
PA-2-BADPABAY |
2-Critical |
Out of range PCI Port Adaptor bay [dec] |
The software specified an out-of-range port adapter bay. |
- |
LOG_STD_ACTION |
|
PA-2-BADPASCB |
2-Critical |
PA interface pascb incorrect [hex] |
The port adapter system control block PASCB data structure was |
- |
LOG_STD_ACTION |
|
PA-2-BADPINST |
2-Critical |
PA interface port_inst incorrect [hex] |
Failure to access port instance internal data |
- |
LOG_STD_ACTION |
|
PA-2-BADVCONT |
2-Critical |
PA interface vcont incorrect [hex] |
Incorrect VC interface specified |
- |
LOG_STD_ACTION |
|
PA-2-ILLEGALPA |
2-Critical |
Illegal Port Adaptor type [dec] in bay [dec] of [chars]. |
The port adapter is not supported by the controller to which it is plugged into. |
- |
"Remove the port adapter and return the controller to its original " "configuration." |
|
PA-2-INCORRECTBRIDGEREG |
2-Critical |
Bad default register[hec] setting[hec] in PA bridge |
The software is unable to configure certain settings for the port adapter protocol control information bridge in the specified bay. |
- |
LOG_STD_ACTION |
|
PA-2-PABRIDGE |
2-Critical |
Failed to config bridge for PA [dec] |
The system side PCI bridge for this PA failed initialization.\n\ The PA will not be operational because of this. |
- |
LOG_STD_ACTION |
|
PA-2-PARECUR |
2-Critical |
Recursive loop while getting the daughtercard info for PA type [dec] |
While getting the daughter card info for the chassismib the platform snmp code goes into an infinite loop. |
- |
LOG_STD_ACTION |
|
PA-2-QOVERFLOW |
2-Critical |
PA queue overflow cmd [hex] |
- |
- |
LOG_STD_ACTION |
|
PA-2-UNDEFIO |
2-Critical |
Unsupported I/O Controller type [dec] in I/O Bay. |
The software does not have a driver for the port adapter type in the specified bay. |
- |
"Make sure the image you are running is supposed to support this card. " "Newer I/O Controllers will only work with the -kboot- image. " LOG_STD_RECUR_ACTION |
|
PA-2-UNDEFPA |
2-Critical |
Undefined Port Adaptor type [dec] in bay [dec] |
The software does not have a driver for the port adapter type in the specified bay. |
- |
"Make sure the image you are running is supposed to support this card. " "Check that the card is properly seated. " LOG_STD_RECUR_ACTION |
|
PA-2-UNDEFPABRIDGE |
2-Critical |
Unsupported Port Adaptor Bridge [hex] in bay [dec] |
The software does not have a driver for that port adapter protocol control information bridge in the specified bay. |
- |
LOG_STD_ACTION |
|
PA-3-BRINGUPFAIL |
3-Error |
port adapter in bay [[dec]] failed to reset. |
An attempt to reset and initialize the port adapter timed out. |
- |
LOG_STD_SH_TECH_ACTION |
|
PA-3-CONFIG |
3-Error |
Recommended port adapter configuration exceeded |
The total bandwidth of fast and medium bandwidth port adapters\n\ exceed the rated capacity of this system. |
- |
"Refer to the configuration guidelines for the maximum allowed\n\ high and medium bandwidth port adapters for the system." |
|
PA-3-DEACTIVATED |
3-Error |
port adapter in bay [[dec]] powered off. |
The port adapter is being powered off. |
- |
LOG_STD_SH_TECH_ACTION |
|
PA-3-IMPROPER_INSERT |
3-Error |
Improper insertion for slot [dec]. Remove and then re-insert the PA |
PCI Activation of PA has failed thus the PA is deactivated\n\ and must be removed and then re-inserted. |
- |
"Remove and then re-insert the PA firmly into the slot." |
|
PA-3-NOTSUPPORTED |
3-Error |
PA in slot[dec] [chars] is not supported on this [chars] |
This port adaptor is not supported on this chassis/cpucard. |
- |
LOG_STD_ACTION |
|
PA-3-PACREATE |
3-Error |
Unable to create driver for Port Adaptor type [dec] in bay [dec] |
Possible memory shortage or adaptor hardware error |
- |
LOG_STD_ACTION |
|
PA-3-REVNOTSUPPORTED |
3-Error |
PA in slot[dec] [chars] requires base h/w revision of [dec].[dec] |
A newer hardware revision of the port adaptor is required for\n\ functional operation on this chassis. |
- |
LOG_STD_ACTION |
|
PA-3-SLOTNOTSUPPORTED |
3-Error |
This PA type [chars] is not supported in slot[dec] of this [chars] |
This port adaptor is not supported on this slot of this chassis/cpucard. |
- |
LOG_STD_ACTION |
|
PA-4-IMPROPER_REMOVAL |
4-Warning |
Improper removal for slot [dec]. |
PA was inserted and then removed while being initialised. |
- |
"After an insertion the PA should be pulled out only after the\n\ initialisation is complete. If there is any traffic running\n\ through the router the initialisation can take up to 30 seconds" |
|
PA-4-PCIVALID |
4-Warning |
PCI activation failed bay [dec] 0x[hec] |
The system received an invalid PCI signal from the port adapter.\n\ This is probably due to a hardware failure. |
- |
LOG_STD_ACTION |
|
PAC-3-LIST_CREATE_FAIL |
3-Error |
LIST creation for instance failed. |
This is a system problem. Probable cause: low resources in the system. Free up some memory. |
- |
LOG_STD_ACTION |
|
PAC-3-SYNC_ERROR |
3-Error |
cannot [chars] sync data: [chars] [dec] [dec] |
Unable to send sync data on active RP or receive and process sync data on standby RP. QoS policy accounting may not work correctly after switch-over. |
qos |
LOG_STD_ACTION |
|
PAC-3-WAVL_INIT_FAIL |
3-Error |
WAVL initialization for [chars] failed. |
This is a system problem. Probable cause: low resources in the system. Free up some memory. |
- |
LOG_STD_ACTION |
|
PACKET_SRVCS-3-PARTICLEPAKDUPFAIL |
3-Error |
Particle packet duplication attempted on non-particle packet\n |
Duplication of packet with particles routine is called\n\ without the packet containing particles. |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-2-ACCESSERROR |
2-Critical |
Client process %ld attempted to access packet [hec] owned by process %ld |
A packet manager client can only access and modify packets that have been assigned to its process |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-2-BLOCKERROR |
2-Critical |
Client process %ld has packet 0x%8x the buffer 0x%8x has been corrupted. |
Data has been written past the end of the previous \n\ buffer causing memory to be corrupted. |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-2-CHANCREATEFAIL |
2-Critical |
Packet server fails to create a channel and event manager error: [chars] |
Packet server fails to create an event manager and \n\ channel. Clients will be unable to connect to packet \n\ server and packet server will be unable to send and \n\ receive messages. |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-2-CHUNKCREATEFAIL |
2-Critical |
chunk_create for [chars] pool failed |
The packet manager encountered a chunk creation failure\n\ while creating the packet header chunk |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-2-CONNECTFAIL |
2-Critical |
Client process %ld failed to connect to Packet Manager reason [chars] |
- |
- |
- |
|
PACKET-2-CTXERROR |
2-Critical |
The context information 0x%8x is not valid. |
An application to the memory block manager has passed\n\ either a context pointer that is not valid. |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-2-DEQUEUEFAIL |
2-Critical |
Fail to remove client %ld from pak_client_list at [chars] |
Can not remove the client from client list queue. \n\ This may cause the client fail to reconnect to packet \n\ server |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-2-ENQUEUEFAIL |
2-Critical |
Fail to insert client %ld into pak_client_list at [chars] |
Mutex operation failed in the packet server |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-2-EVENTATTACHFAIL |
2-Critical |
event attach failure |
The packet subsystem encountered an error when \n\ registering for synchronous or asynchronous events. |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-2-EVENTBLOCKFAIL |
2-Critical |
event_block failure |
event block error was encountered when blocking for external events |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-2-EVENTCONTEXTALLOCFAIL |
2-Critical |
event_context_alloc failure |
Failed while allocating the event context |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-2-GETNODENAMEFAIL |
2-Critical |
failed to get node name in pakman server init |
packet manager server unable to retrieve the hostname for node/linecard |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-2-HDRPOOLINITFAIL |
2-Critical |
Packet header pool init failed |
Failed to initialize the packet pool headers |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-2-MEMBLKERROR |
2-Critical |
Memory block 0x%8x is not valid. |
An application to the memory block manager has passed\n\ a memory block that is not valid. |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-2-MEMFREEERROR |
2-Critical |
Memory block 0x%8x has already been freed. |
An application to the memory block manager has attempted\n\ to free or lock a memory block that is not allocated. |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-2-MEMORDINALERROR |
2-Critical |
The memory block manager has detected an ordinal error.\n\ Memory block 0x%8x has an ordinal of 0x%4x and a size of 0x%4x.\n\ Its corresponding lower sibling memory block 0x%8x has\n\ an ordinal of 0x%4x and a size of 0x%4x. |
The lower sibling ordinal should be equal to the\n\ difference between the higher sibling's ordinal and\n\ size. |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-2-MEMTWINBLKERROR |
2-Critical |
An attempt to coalesce memory block 0x%8x with its\n\ sibling memory block 0x%8x has failed because the sibling\n\ block is not valid. |
An attempt to coalesce two memory blocks\n\ has failed because a memory block is not valid. |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-2-NEXTBLOCKERROR |
2-Critical |
The next block after buffer 0x%8x packet 0x%8x has been corrupted. |
- |
- |
- |
|
PACKET-2-PTHREADCREATEFAIL |
2-Critical |
pthread create fail in pakman while creating the [chars] thread |
packet manager server unable to create a new thread |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-2-PTHREADMUTEXFAIL |
2-Critical |
pthread_mutex_init failed on packet mutex. Reason : [chars] |
The packet manager failed to initialize the global mutex |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-2-REDZONEERROR |
2-Critical |
Client process %ld has packet 0x%8x the buffer 0x%8x \n\ has been overrun. |
Data has been written past the end of the buffer causing\n\ memory to be corrupted. |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-2-SHMCREATEFAIL |
2-Critical |
Error in creating the shared buffer mem: [chars] |
Fatal error encountered while creating shared packet buffers |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-2-SHMCTLFAIL |
2-Critical |
Error in shm_ctl: [chars] |
Fatal error encountered while doing the shm_ctl operations on the shared packet memory |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-3-BLKDUMP |
3-Error |
[chars] |
This is just to report general messages in the memory\n\ management code. |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-3-CLNTDISCONN |
3-Error |
Handling disconnect for client [dec] [chars]\n |
- |
- |
- |
|
PACKET-3-CORRUPTPAKHDR |
3-Error |
Corruption in packet header [hec] pid [dec] magic [hec] buffer [hec] caller_pc [hec]\n |
The packet header has become corrupted. |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-3-CORRUPTPAKPOOL |
3-Error |
[chars] Pool [hec] corrupted magic [hec]\n |
The packet pool has failed a consistency check as it \n\ has got corrupted. |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-3-ERRPAKHDR |
3-Error |
Not able to fix corruption in packet header [hec] pid = [dec]\n |
There has been a corruption in the packet header memory\n\ and it cannot be fixed. |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-3-IFINPUTCOUNTERROR |
3-Error |
Packet: %p with linktype:[dec] being punted from process: %ld to process: %ld with out decrementing the input_qcount |
An attempt was made to punt the packet from one process\n\ to another with the input queue flag set. This means that\n\ the input_qcount was not decremented on the interface \n\ where the packet was received. This will lead to input\n\ queue throttling on that interface |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-3-INITFAIL |
3-Error |
Packet server initialization failed. Reason : [chars] |
The packet subsystem was not able to initialize properly |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-3-INITWARNING |
3-Error |
Warning[chars] while initializing the packet process |
- |
- |
- |
|
PACKET-3-PACKETHDRDUMP |
3-Error |
[chars] |
This is just to report general packet header messages. |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-3-PAK_INPUTQ_ERROR |
3-Error |
Packet: %p in process: %ld has PAK_INPUTQ set incorrectly |
A packet outside the iosbase has the input queue \n\ flag set. This means that a packet was punted from \n\ the iosbase to another ION process without decrementing \n\ the input queue count |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-3-RECOVERBLK |
3-Error |
\nBLOCK 0x[hec] IS SUCESSFULLY RECOVERED AFTER CORRUPTION\n |
Corruption was detected in a memory block and it \n\ was posible to recover the block successfully. |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-3-REFCOUNTERROR |
3-Error |
Bad reference count in packet: %p refcount: [dec]. |
An attempt was made to free a packet that\n\ has already been freed |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-3-REINITSHMEM |
3-Error |
Restarting [chars] to reinitialize shared memory because of memory corruption\n |
There has been a memory corruption. Restart the \n\ client to reinitialise shared memory. |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACKET-3-RESTARTFAIL |
3-Error |
Packet server restart failed. Reason : [chars] |
The packet subsystem was not able to restart properly |
packetmgr |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PACTRAC-3-BIG_SERIAL |
3-Error |
serial number [dec] exceeds configured packets [dec] |
A packet serial number was encountered that was larger than than the configured number of packets being traced. |
iosxe-pactrac |
LOG_STD_PACTRAC_ACTION |
|
PACTRAC-3-INVALID_PARM |
3-Error |
encountered invalid parameter |
An invalid parameter was encountered during packet-trace processing. |
iosxe-pactrac |
"Copy the error message exactly as it appears on the console or in the ""system log. Research and attempt to resolve the error using the ""Output Interpreter " OUTPUT_INTERPRETER ". Also perform a ""search of the Bug Toolkit " BUG_TOOLKIT ". If you still require ""assistance open a case with the Technical Assistance Center via the ""Internet " TAC_CASE_OPEN " or contact your Cisco technical support ""representative and provide the representative with the gathered information." |
|
PACTRAC-3-NUM_WRITES |
3-Error |
attempt to write [dec] bytes of path data for id [dec] |
The serial number could not be returned to the serial number pool because the pool is full most likely because a serial number has been returned multiple times. |
iosxe-pactrac |
LOG_STD_PACTRAC_ACTION |
|
PACTRAC-3-POOL_FULL |
3-Error |
unable to return serial number [dec] to pool |
The serial number could not be returned to the serial number pool because the pool is full most likely because a serial number has been returned multiple times. |
iosxe-pactrac |
LOG_STD_PACTRAC_ACTION |
|
PAD-2-INTR |
2-Critical |
[chars] called at interrupt level [hec] |
An internal software error occurred. |
- |
"If this message recurs copy the error message exactly as it\n\ appears and report it to your technical support representative." |
|
PAD-2-PUTSETUP |
2-Critical |
Tty[t-line] buffer already setup |
An internal software error occurred. |
- |
"If this message recurs copy the error message exactly as it\n\ appears and report it to your technical support representative." |
|
PAD-3-GETLINE |
3-Error |
Tty[t-line] bad return code [dec] from x3_getline |
An internal software error occurred. |
- |
"If this message recurs copy the error message exactly as it\n\ appears and report it to your technical support representative." |
|
PAGP_DUAL_ACTIVE-1-RECOVERY |
1-Alert |
PAgP running on [chars] triggered dual-active recovery: active id [enet] received expected [enet] |
Pagp detected dual-active scenario on specified interface and caused switch to go into recovery mode. |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
PAGP_DUAL_ACTIVE-1-RECOVERY |
1-Alert |
PAgP running on [chars] triggered dual-active recovery: active id [enet] received expected [enet] Switch is in recovery mode |
Pagp detected dual-active scenario on specified interface and caused switch to go into recovery mode. |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
PAGP_DUAL_ACTIVE-3-ADD_TLV_FAIL |
3-Error |
Too few bytes for [chars] TLV in PAgP reqd. [dec] got [dec] on port [chars] |
- |
- |
- |
|
PAGP_DUAL_ACTIVE-3-ADD_TLV_FAIL |
3-Error |
Too few bytes for [chars] TLV in PAgP reqd. [dec] got [dec] on port [chars] |
- |
- |
- |
|
PAGP_DUAL_ACTIVE-3-OBJECT_CREATE_FAILED |
3-Error |
Unable to create \[chars]\ |
Unable to create the specified managed object |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
PAGP_DUAL_ACTIVE-3-OBJECT_CREATE_FAILED |
3-Error |
Unable to create \[chars]\ |
Unable to create the specified managed object |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
PAGP_DUAL_ACTIVE-3-PROC_CREATE_FAILED |
3-Error |
Unable to create process \[chars]\ |
Unable to create the specified process |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
PAGP_DUAL_ACTIVE-3-PROC_CREATE_FAILED |
3-Error |
Unable to create process \[chars]\ |
Unable to create the specified process |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
PAGP_DUAL_ACTIVE-3-RECOVERY_TRIGGER |
3-Error |
PAgP running on [chars] has detected a switchover or possible dual-active situation on the neighbor virtual switch. Informing virtual switches of active id change: new id [enet] old id [enet] |
Pagp received new active id on specified interface indicating virtual switches are in a dual-active scenario. Interface is informing virtual switches of this which will cause one switch to go into recovery mode. |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
PAGP_DUAL_ACTIVE-3-RECOVERY_TRIGGER |
3-Error |
PAgP running on [chars] informing virtual switches of dual-active: new active id [enet] old id [enet] |
Pagp received new active id on specified interface indicating virtual switches are in a dual-active scenario. Interface is informing virtual switches of this which will cause one switch to go into recovery mode. |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
PAGP_DUAL_ACTIVE-3-REGISTRY_ADD_ERR |
3-Error |
Failure in adding to [chars] registry |
Could not add a function to the registry |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
PAGP_DUAL_ACTIVE-3-REGISTRY_ADD_ERR |
3-Error |
Failure in adding to [chars] registry |
Could not add a function to the registry |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
PAGP_DUAL_ACTIVE-4-NO_CHNL_GROUP |
4-Warning |
Port [chars] channel group not present while [chars] |
Extraction of the channel group from a link has failed but is expected to be present. This should not occur and may affect functionality depending on where it occurred. |
cat6k-vs-infra |
"This message should not be seen under normal operation. " "If it is appearing it is an indication of a software bug. " "Enter the commands:\n" "<CmdBold>show switch virtual dual-active summary<NoCmdBold>\n" "<CmdBold>show switch virtual dual-active pagp<NoCmdBold>\n" "Retrieve the PAgP packet contents by entering the commands:\n " "<CmdBold>debug condition interface <intfc><NoCmdBold>\n" "<CmdBold>debug pagp packet<NoCmdBold>\n" "and " LOG_STD_SH_TECH_ACTION |
|
PAGP_SWITCH_ISSU-2-GET_BUFFER |
2-Critical |
PAGP SWITCH ISSU client failed to get buffer for message. Error: [dec] [chars] |
PAGP SWITCH 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. |
L2 |
"show logging and show checkpoint client" |
|
PAGP_SWITCH_ISSU-2-INIT |
2-Critical |
PAGP SWITCH ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The PAGP SWITCH 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. |
L2 |
LOG_STD_ACTION |
|
PAGP_SWITCH_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
PAGP SWITCH ISSU client failed to send negotiation message. Error: [dec] [chars] |
The PAGP SWITCH 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. |
L2 |
"show logging and show checkpoint client" |
|
PAGP_SWITCH_ISSU-2-SESSION_ARBITRATE |
2-Critical |
PAGP SWITCH ISSU client failed to register arbitrate callback. Error: [dec] [chars] |
The PAGP SWITCH ISSU client failed to register arbitrate callback. If a problem occurs with the callback registration the standby device cannot be brought up properly. |
L2 |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
PAGP_SWITCH_ISSU-2-SESSION_NEGO |
2-Critical |
PAGP SWITCH ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The PAGP SWITCH 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. |
L2 |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
PAGP_SWITCH_ISSU-2-SESSION_REGISTRY |
2-Critical |
PAGP SWITCH ISSU client failed to register session information. Error: [dec] [chars] |
The PAGP SWITCH ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
L2 |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
PAGP_SWITCH_ISSU-3-INVALID_CAPABILITY |
3-Error |
PAGP SWITCH ISSU client: invalid capability list |
PAGP SWITCH ISSU client observed an error during capability negotiaiton. When this error happens there is a mismatch in the client capability between the active and standby unit. |
L2 |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
PAGP_SWITCH_ISSU-3-INVALID_SESSION |
3-Error |
PAGP SWITCH ISSU client does not have a valid registered session. |
The PAGP SWITCH ISSU client does not have a valid registered session. |
L2 |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
PAGP_SWITCH_ISSU-3-MSG_NOT_OK |
3-Error |
PAGP SWITCH ISSU client 'Message Type [dec]' is not compatible |
The PAGP SWITCH ISSU client received an incompatible message from the peer device. The message cannot be processed. |
L2 |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
PAGP_SWITCH_ISSU-3-MSG_SIZE |
3-Error |
PAGP SWITCH ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The PAGP SWITCH ISSU client failed to calculate the MTU for the specified message. The PAGP SWITCH ISSU client is not able to send the message to the standby device. |
L2 |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
PAGP_SWITCH_ISSU-3-POLICY_NOT_SUPPORTED |
3-Error |
PAGP SWITCH ISSU client does not support Message Type [dec] |
PAGP SWITCH ISSU client received an message type which it does not support. The policy is applied to make the session incompatible. |
L2 |
"show issu session <client_id>" |
|
PAGP_SWITCH_ISSU-3-REJECTED_CAPABILITY |
3-Error |
PAGP SWITCH ISSU client rejected capability '[chars]' |
PAGP SWITCH ISSU client rejected a capability during negotiaiton. When this error happens there is a mismatch in the client capability between the active and standby unit. |
L2 |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
PAGP_SWITCH_ISSU-3-REJECTING_CAPABILITY |
3-Error |
PAGP SWITCH ISSU client rejecting capability '[chars]' |
PAGP SWITCH ISSU client is rejecting a capability during negotiaiton. When this error happens there is a mismatch in the client capability between the active and standby unit. |
L2 |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
PAGP_SWITCH_ISSU-3-SESSION_UNREGISTRY |
3-Error |
PAGP SWITCH ISSU client failed to unregister session information. Error: [dec] [chars] |
The PAGP SWITCH ISSU client failed to unregister session information. |
L2 |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
PAGP_SWITCH_ISSU-3-TRANSFORM_FAIL |
3-Error |
PAGP SWITCH ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The PAGP SWITCH 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 PAGP SWITCH state between the active device and the standby device is not identical. |
L2 |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
PALCI-4-FLOWDB_INSUFFICIENT_MEMORY |
4-Warning |
Allocation of flow database failed due to insufficient memory - [dec] MB. Please increase the memory otherwise the stateful features will not work correctly. |
The allocation of flow database failed as there is not enough memory allocated to the system. The memory needs to be increased for stateful features to work correctly |
isr9k-dp |
"Increase the system memory." |
|
PANGEA_QOS-3-DIFFTBLMAP |
3-Error |
From and To type should be same except if to type is traffic-class discard-class or qos-group for tablemap |
From and To type should be same except if to type is traffic-class discard-class or qos-group for tablemap |
pangea-qos |
"show policy-map" |
|
PANGEA_QOS-3-MIXFILTER |
3-Error |
[chars] [chars] |
The Leaba platfrom does not support MPLS or L2 COS filter with other fitlers |
pangea-qos |
"show policy-map" |
|
PARSE_RC-3-PRC_INTERRUPT |
3-Error |
[chars] |
An internal software error occurred. |
parser |
LOG_STD_ACTION |
|
PARSE_RC-3-PRC_INTERRUPT |
3-Error |
[chars] |
An internal software error occurred. |
parser |
LOG_STD_ACTION |
|
PARSE_RC-3-PRC_INVALID_BLOCK_PTR |
3-Error |
- |
An internal software error occurred. |
parser |
LOG_STD_ACTION |
|
PARSE_RC-3-PRC_INVALID_BLOCK_PTR |
3-Error |
- |
An internal software error occurred. |
parser |
LOG_STD_ACTION |
|
PARSE_RC-3-PRC_INVALID_CSB |
3-Error |
- |
An internal software error occurred. |
parser |
LOG_STD_ACTION |
|
PARSE_RC-3-PRC_INVALID_CSB |
3-Error |
- |
An internal software error occurred. |
parser |
LOG_STD_ACTION |
|
PARSE_RC-3-PRC_LEV_RANGE |
3-Error |
Parser Return Code level range error [dec] |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
PARSE_RC-3-PRC_LEV_RANGE |
3-Error |
Parser Return Code level range error [dec] |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
PARSE_RC-3-PRC_OUT_OF_RANGE_ENUM |
3-Error |
[chars] had value [dec] |
An out-of-range parameter was passed to an internal API. |
parser |
LOG_STD_ACTION |
|
PARSE_RC-3-PRC_OUT_OF_RANGE_ENUM |
3-Error |
[chars] had value [dec] |
An out-of-range parameter was passed to an internal API. |
parser |
LOG_STD_ACTION |
|
PARSE_RC-3-PRC_SUBRCODE_RANGE |
3-Error |
Parser Return Code state range error [dec] |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
PARSE_RC-3-PRC_SUBRCODE_RANGE |
3-Error |
Parser Return Code state range error [dec] |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
PARSE_RC-3-PRC_UNRECOGNIZED_ERROR |
3-Error |
error value `[dec]' is not currently mapped |
An unrecognized error was caught and remapped. |
parser |
LOG_STD_ACTION |
|
PARSE_RC-3-PRC_UNRECOGNIZED_ERROR |
3-Error |
error value `[dec]' is not currently mapped |
An unrecognized error was caught and remapped. |
parser |
LOG_STD_ACTION |
|
PARSE_RC-4-PRC_NON_COMPLIANCE |
4-Warning |
`[chars]' |
An internal software error occurred. |
parser |
LOG_STD_ACTION |
|
PARSE_RC-4-PRC_NON_COMPLIANCE |
4-Warning |
`[chars]' |
An internal software error occurred. |
smartport |
LOG_STD_ACTION |
|
PARSE_RC-6-PRC_DISABLE |
6-Information |
Parser PRC Feature Disabled |
Parser PRC Feature Disabled |
parser |
"LOG_STD_NO_ACTION" |
|
PARSE_RC-6-PRC_ENABLE |
6-Information |
Parser PRC Feature Enabled. PRC logs are displayed for configuration commands alone |
Parser PRC Feature Enabled. PRC logs are displayed for configuration commands alone |
parser |
"LOG_STD_NO_ACTION" |
|
PARSER-2-INTDISABLE |
2-Critical |
Interrupts disabled in mode [chars] by command '[chars]' |
A hardware or software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
PARSER-3-AFSFAIL |
3-Error |
[chars] for command serialization failed. |
This message indicates that the event required for command serialization has failed. |
- |
- |
|
PARSER-3-BADLINK |
3-Error |
bad link point %p |
Software attempted to perform an invalid parser operation. |
- |
"Copy the error message exactly as it appears. Execute a show version " "command and copy the displayed information. Contact your technical " "support representative." |
|
PARSER-3-BADSUBCMD |
3-Error |
Unrecognized subcommand [dec] in [chars] command '[chars]' |
The parser failed an internal software check. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
PARSER-3-CFGLOG_CLI_INITFAILED |
3-Error |
Initialization of the Config Log CLI failed. |
Config Log CLI commands may not be accessible and hence the Config Logger may not be accessible via the IOS CLI. |
- |
"Copy the error message exactly as it appears. Execute a show version " "command and copy the displayed information. Contact your technical support " "representative with this information." |
|
PARSER-3-CFGLOG_EMPTYCMD |
3-Error |
User:[chars] |
The user specified entered an empty command for which a log attempt was made. Normally empty commands will not be logged. |
- |
"Copy the error message exactly as it appears. Execute a show version " "command and copy the displayed information. Execute a \"show cfglog " "user <username listed above> xml detailed\". Contact your technical " "support representative." |
|
PARSER-3-CFGLOG_INCONSISTENT |
3-Error |
User:[chars] command:[chars] |
When logging a command entered on the CLI the Config Logger detected an inconsistency in the log. This inconsistency may result in a failure to log the command. |
- |
"Copy the error message exactly as it appears. Execute a show version " "command and copy the displayed information. Determine if possible " |
|
PARSER-3-CFGLOG_INITFAILED |
3-Error |
Initialization of the Config Log subsystem failed. |
During initialization one or more queues/data structures essential to the config logger could not be set up. As a result the config logger will not be available for use. |
- |
"Copy the error message exactly as it appears. Execute a show version " "command and copy the displayed information. Contact your technical support " "representative with this information." |
|
PARSER-3-CFGLOG_NOMEM |
3-Error |
User:[chars] [chars] |
The command that was entered could not be logged because of a lack of memory. It is possible that the system logger syslog can allocate |
- |
"Attempt to free up memory on the router by stopping nonessential " "processes or unused features that may be running. Once sufficient " "memory is available this message will no longer appear." |
|
PARSER-3-CFGLOG_NOUSER |
3-Error |
Command:[chars] |
Could not determine the user when logging the above command. Hence it could not be saved in the config log. |
- |
"Copy the error message exactly as it appears. Execute a show version " "command and copy the displayed information. Determine if possible " |
|
PARSER-3-CFGLOG_PERSIST_APPLY_CMD_FAILED |
3-Error |
Configuration logger persistency: Applying config command '[chars]' failed. result '[dec]'. |
When applying the command to the running configuration the parser returned an error. |
- |
" Parser encountered an error when the command is applied " " to the running configuration during reload. Verify no" " other process locks the configuration mode during this " " time. The parser could be locked by the HA or SNMP or by " " some other process." |
|
PARSER-3-CFGLOG_PERSIST_DB_OPEN_FAILED |
3-Error |
Configuration logger persistency: opening persist db failed. File '[chars]'. |
The file open for writing/reading persisted commands failed. |
- |
"Check for the file system availablity. The file system " " might have got corrupted. Try formatting the file system." |
|
PARSER-3-CFGLOG_PERSIST_FILESYS_FULL |
3-Error |
Configuration logger persistency: Add command to persistent db failed. File system '[chars]' full. |
When logging a command entered on the CLI into the configuration logger persistent database the Config Logger persistency detected zero bytes free in the file system. |
- |
"Check the space available in the filesystem displayed reported. " "Use 'dir <filesystemname>:' to find out the bytes free. " "Clear out some space for the configuration logger persistency " "feature to continue store the config commands logged in to the " "persistent database." |
|
PARSER-3-CFGLOG_PURGEFAILED |
3-Error |
Purge config log failed. |
Failed to purge some of the config log entries |
- |
"Copy the error message exactly as it appears. Execute a show version " "command and copy the displayed information. Contact your technical support " "representative with this information." |
|
PARSER-3-CFGLOG_RESIZE_FAILED |
3-Error |
Could not resize the config logger to new size:[dec] |
Due to an internal error a request to resize the config log was not carried out. Apart from a failure to resize there should be no change in the behavior of the config logger. |
- |
"Copy the error message exactly as it appears. Execute a show version " "command and copy the displayed information. Contact your technical support " "representative with this information." |
|
PARSER-3-CFGLOG_SESSIONERR |
3-Error |
Could not delete config log session:[dec] for user:[chars]. |
When a user logged out the Config Logger was unable to clean up information about the user's login session. The result might be a memory leak or inability to add new commands to the Config Log. |
- |
"Copy the error message exactly as it appears. Execute a show version " "command and copy the displayed information. Contact your technical support " "representative with this information." |
|
PARSER-3-CREATEINT |
3-Error |
Can't create any more subinterfaces |
The parser failed an internal software check. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
PARSER-3-CSLFAIL |
3-Error |
Semaphore creation for configuration session lock failed |
This message indicates that the semaphore required for configuration session locking has failed. |
- |
- |
|
PARSER-3-NOLINK |
3-Error |
no link_point[dec] in the [chars] [chars] command chain |
The parser failed an internal software check. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
PARSER-3-REGEXP_COMPILE_ERROR |
3-Error |
compile of regular expression failed: \[chars]\ |
Unrecoverable error while parsing |
- |
"Ensure that the system is not low on memory." |
|
PARSER-3-URLOPENFAIL |
3-Error |
cannot open file for redirection '[chars]' |
The destination URL for the redirection cannot be opened for writing. |
- |
"Check for proper Uniform Resource Locator syntax and for write " "permission. Also check for free space and retry" |
|
PARSER-3-WMLFAIL |
3-Error |
Semaphore creation for write memory lock failed |
This message indicates that the semaphore required for write memory locking has failed. |
- |
- |
|
PARSER-4-BADCFG |
4-Warning |
Unexpected end of configuration file.\n |
This message occurs when a configuration is read from the Trivial File Transfer Protocol TFTP server or nonvolatile RAM NVRAM and the end |
- |
"Make sure the configuration is good then execute either a copy " "running-config startup-config command to write the good configuration " "to NVRAM or a copy running-config tftp command to write to a network " "TFTP server." |
|
PARSER-4-BADRANGE |
4-Warning |
Bad range <[dec]-[dec]> for command '[chars]' |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
PARSER-4-BADRANGELONGLONG |
4-Warning |
Bad range <%ld-%ld> for command '[chars]' |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
PARSER-4-INVLDLINE |
4-Warning |
Invalid line in NV generation: [t-line]\n |
The parser failed an internal software check. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
PARSER-4-INVLDNVGEN |
4-Warning |
Invalid function called in NVGEN of '[chars]' |
An error occurred. |
- |
"Copy the error message exactly as it appears. Execute a show version " "command and copy the displayed information. Contact your technical " "support representative." |
|
PARSER-4-INVLDSYNTX |
4-Warning |
Syntax cleanup list updated while not syntax checking. \nFuncPtr / Context [chars] |
Functions were mistakenly called there may be more than listed |
- |
"show version" |
|
PARSER-4-LINKPOINT |
4-Warning |
Parser reached link_point |
The parser failed an internal software check. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
PARSER-4-MULFUNCS |
4-Warning |
unknown test in test_multiple_funcs '[chars]' |
The parser failed an internal software check. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
PARSER-4-MULTIPLEIFS |
4-Warning |
interface_action: multiple ifs present when unit_only set |
The parser failed an internal software check. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
PARSER-4-NUMHELP |
4-Warning |
general_number_short_help: Invalid [chars] number flag |
The parser failed an internal software check. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
PARSER-4-NVGEN |
4-Warning |
nvgen_token called but csb->nvgen not set |
The parser failed an internal software check. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
PARSER-4-PROTOADDR |
4-Warning |
protoaddr_action: Unknown link_type [dec] |
The parser failed an internal software check. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
PARSER-4-SHELL_SYNTAX |
4-Warning |
Shell function: [chars]: Syntax Error: [chars] |
There is a syntax error in the Shell script. |
parser |
"Users are recommended to correct it in the script." |
|
PARSER-5-CFGLOG_LOGGEDCMD |
5-Notice |
User:[chars] logged command:[chars] |
The config logger which logs every CLI command has an option to log messages to syslog - whenever a CLI command is executed this message is printed. |
- |
"This message DOES NOT denote any error condition. It is a part of the " "normal operation of the parser and config logger. If you do not wish " "to see this syslog message type \"no cfglog send to syslog\"." |
|
PARSER-5-CFGLOG_PERSIST_APPLY_ON_RELOAD |
5-Notice |
Apply persisted config cmds on reload switched off |
The switch that controls the persisted commands applied during reload is set to OFF. |
- |
"Verify the rommon variable 'logpersistreload' value from rommon" " prompt. This variable might have been intentionally set to OFF." |
|
PARSER-5-CFGLOG_PERSIST_FILE_LIMIT |
5-Notice |
Configuration logger persistency contains [dec] commands in [chars] file. |
Configuration logger persistency has persisted more commands. Time to do write memory to save all the persisted commands to the startup-config file. |
parser |
"This is a notification message to remind the user to do" " write memory or copy running-config startup-config." |
|
PARSER-5-CFGLOG_PERSIST_OPER_DOWN |
5-Notice |
Configuration logger persistency is enabled but is operationally down |
When Configuration logger persistency is enabled it is operationally down. It becomes operationally up at the next write memory or copy running-config startup-config operation. |
parser |
"Please do write memory or copy running-config startup-config" " to make the feature operationally up. Otherwise the" " commands will not be persisted." |
|
PARSER-5-CFGLOG_PERSIST_OPER_UP |
5-Notice |
Configuration logger persistency is operationally up |
When Configuration logger persistency is enabled it becomes operationally up after the next write memory operation to start persisting commands. |
parser |
"This is a notification message only. No action is required." |
|
PARSER-5-HIDDEN |
5-Notice |
Warning!!! ' [chars]' is a hidden command. Use of this command is not recommended/supported and will be removed in future. |
This message indicates the current cli is hidden command. |
- |
- |
|
PARSER-5-INTERNAL |
5-Notice |
Warning!!! ' [chars]' is an internal command. Use of this command is not recommended/supported. |
This message indicates the current cli is an internal command. |
- |
- |
|
PARSER-6-CLIHOG |
6-Information |
This command by [chars] will not be serialized anymore. |
This message indicates that the command execution might be either time consuming or processing large data structures. Attention required by the CLI owners to set PARSE_DONT_FLAG and protect their data structure else ignore. |
- |
"Please contact the Command Owner to take corrective action." |
|
PARSER-6-CSLOCKCLEARED |
6-Information |
Configuration session lock is cleared by process '[dec]' user '[chars]' from terminal '[dec]' |
Configuration session lock was forcibly released as per the request by either the terminal user or an application or on timeout. |
parser |
"This is a notification message only. No action is required." |
|
PARSER-6-CSLOCKTIMEOUT |
6-Information |
Configuration session lock acquired by application '[chars]' / process '[dec]' is being used for long time. |
Configuration session lock has been acquired and timed out. The lock should be made available for requesting process. |
parser |
"This is a notification message in case of manually acquired lock " " by 'configure terminal lock' command. " "A defect can be filed if any other application is blocking it". |
|
PARSER-6-LI_VIEW_INIT |
6-Information |
LI-View initialised. |
You have successfully initialised LI-View. |
- |
"" |
|
PARSER-6-WMLRETRY |
6-Information |
Write memory lock currently held by pid '[dec]' automatic retry. |
This message indicates that the semaphore required for write memory locking has timed out. |
- |
- |
|
PASSWD-5-AUTH_INVALID_PASSWORD |
5-Notice |
[chars] [chars] Failed authentication |
The credential did not match the configured value when authentication |
passwd |
"No action required" |
|
PASSWD-5-AUTH_INVALID_PASSWORD |
5-Notice |
[chars] [chars] Failed authentication |
The credential did not match the configured value when authentication |
passwd |
"No action required" |
|
PASSWD-5-AUTH_LIFETIME_EXCEEDED |
5-Notice |
[chars] [chars] credential lifetime has expired |
The credential has exceeded the configured lifetime |
passwd |
"No action required" |
|
PASSWD-5-AUTH_LIFETIME_EXCEEDED |
5-Notice |
[chars] [chars] credential lifetime has expired |
The credential has exceeded the configured lifetime |
passwd |
"No action required" |
|
PASSWD-5-AUTH_PRE_EXPIRY_NOTIFY |
5-Notice |
[chars] [chars] The credential is about to expiry |
The credential is within to pre-expireinterval change the credential expires |
passwd |
"No action required" |
|
PASSWD-5-AUTH_PRE_EXPIRY_NOTIFY |
5-Notice |
[chars] [chars] The credential is about to expiry |
The credential is within to pre-expireinterval change the credential expires |
passwd |
"No action required" |
|
PASSWD-5-AUTH_REPEATED_FAILURE |
5-Notice |
[chars] [chars] number of allowed dauthentication failure exceeded |
The number of authentication failures the allowed interval excceeded the configured value |
passwd |
"No action required" |
|
PASSWD-5-AUTH_REPEATED_FAILURE |
5-Notice |
[chars] [chars] number of allowed dauthentication failure exceeded |
The number of authentication failures the allowed interval excceeded the configured value |
passwd |
"No action required" |
|
PASSWD-5-CREDENTIAL_COMPLEXITY_CHECK_FAILED |
5-Notice |
[chars] [chars] credential has failed the complexty check |
The credential may not be as secure since it has failed the complexity check |
passwd |
"No action required" |
|
PASSWD-5-CREDENTIAL_COMPLEXITY_CHECK_FAILED |
5-Notice |
[chars] [chars] credential has failed the complexty check |
The credential may not be as secure since it has failed the complexity check |
passwd |
"No action required" |
|
PASSWD-5-CREDENTIAL_PASSWORD_CHANGE_EXCEED_LIMIT |
5-Notice |
[chars] [chars] the number of changes allowed has been exceeded |
The number of credential changes has exceed the configured number and interval |
passwd |
"No action required" |
|
PASSWD-5-CREDENTIAL_PASSWORD_CHANGE_EXCEED_LIMIT |
5-Notice |
[chars] [chars] the number of changes allowed has been exceeded |
This command syntax has been deprecated. |
passwd |
"Please use the new syntax and update your saved configuration if needed." |
|
PATCH-3-CHANNEL_MISMATCH |
3-Error |
Channel mismatch between [chars] and [chars] |
Channel mismatch when creating patch. |
- |
LOG_STD_ACTION |
|
PATH_VEC-4-LDP |
4-Warning |
ERRMSG_LIMIT_SLOW*15 |
- |
- |
- |
|
Path [chars] changed state to [chars] |
A Sonet high order path changed its state. |
c7600-sip-200 |
"This is a internal software error. Decode the " "traceback and get the output of <CmdBold>show " "controller sonet<NoCmdBold>. Look into this " "output to see if there are any alarms being " "reported at the path level. Check Bug Toolkit " "before calling the TAC. When calling the TAC " "please provide the above information along with " "the output of <CmdBold>show tech<NoCmdBold> " "details" |
- |
- |
|
PATH-3-MPLS_TE_PCALC |
3-Error |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
PATHMGR-2-IPC_INIT |
2-Critical |
IPC message handler registration failure rc [dec] |
The NAT proxy has receive an IPC with an unexpect format/data |
cpp-ucode |
LOG_STD_ACTION |
|
PATHMGR-3-IPC_NORES |
3-Error |
No space for the IPC reply size [dec] |
For a request from upper PATHMGR software stack layers it was not possible to allocate space for a reply for the specified size. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation. |
qfp-pathmgr |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
PATHMGR-3-IPC_OPEN_REPLY |
3-Error |
IPC Open Reply failed request [dec] |
For a request from upper PATHMGR software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation. |
qfp-pathmgr |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
PBR-2-NO_RMAP |
2-Critical |
Cannot create PBR data structures for route-map [chars] |
The PBR manager could not allocate the data structures needed to describe a route-map being used for policy routing. Probably caused by lack of available memory. |
firmware |
"Use a less complicated configuration that " "requires less memory." |
|
PBR-3-INSTALL_FAIL |
3-Error |
Policy route-map [chars] not installed in hardware |
The PBR manager was unable to install the complete route-map in the hardware so this will have to be applied in software. This requires the packets to be forwarded by the CPU. |
firmware |
"Reconfigure the route-map to use a simpler " " configuration. Use the same route-map on " "multiple interfaces if possible" |
|
PBR-3-MERGE_FAIL |
3-Error |
[chars] ACL merge error [dec] on route-map [chars] |
The PBR manager could not complete the merge of the configured route-map into a form suitable for loading into the hardware. The most likely cause is specifying an ACL that is too large or too complex for the system to handle. |
firmware |
"Try specifying a smaller and less complicated " "configuration." |
|
PBR-3-NO_LABEL |
3-Error |
Cannot allocate label for route-map [chars] |
The PBR manager could not allocate a label for this route-map. This means that the hardware cannot be programmed to implement policy routing. There is a limit of 247 labels for policy routing |
firmware |
"Use a less complicated configuration that " "allows label sharing. Use the same route-maps on multiple interfaces if possible" |
|
PBR-3-PBR_CLASSIFY_FAIL |
3-Error |
Dataplane classification error for interface [chars] |
Cisco internal software error. The dataplane was unable to complete processing of a route map due to a classification failure. This is likely due to a data initialization error |
cpp-ucode keyword:pbr |
LOG_STD_ACTION |
|
PBR-3-UNSUPPORTED_RMAP |
3-Error |
Route-map [chars] not supported for Policy-Based Routing |
The route-map attached to an interface for policy routing contains an action that is not supported on this platform. This is a hardware limitation. |
hardware |
"Reconfigure the route-map. Use only 'permit' " "entries and 'set ip next-hop' action in the " "route-map." |
|
PBR-4-CPU_SUPPORTED_ACTION |
4-Warning |
Set action in sequence [dec] of route-map [chars] supported by forwarding to CPU |
The route-map attached to an interface for policy routing contains an action that is not supported in hardware since it contains a 'set interface' 'set ip default next-hop' 'set default interface' or or 'set ip df' actions. This requires the packets to be forwarded by the CPU. |
firmware |
"Reconfigure the route-map. Use only 'set ip " "next-hop' in the route-map if possible." |
|
PBR-4-RETRY_INSTALL |
4-Warning |
Route-map [chars] installed in hardware upon retry |
The PBR manager was able to fit the complete configuration into the hardware. One or more route-maps had previously not been loaded because of lack of space. |
firmware |
LOG_STD_NO_ACTION |
|
PBUF-3-PBUF_MEM_INIT_FAILED |
3-Error |
[chars] |
Failure occurred when attempting to create memory resource |
cpp-ucode |
LOG_STD_ACTION |
|
PBUF-3-PBUF_MEM_REQ_FAILED |
3-Error |
- |
Failure occurred when attempting to request extended packet memory. |
cpp-ucode |
LOG_STD_ACTION |
|
PBUF-3-PBUF_PKT_MEM_CORRUPT |
3-Error |
[hec] [hec] |
Memory corruption detected while freeing extended packet memory |
cpp-ucode |
LOG_STD_ACTION |
|
PBUF-3-PBUF_SH_DRAM_CVT_FAIL |
3-Error |
[chars] |
An attempt to convert a shared DRAM buffer to non-shared failed. |
cpp-ucode |
LOG_STD_ACTION |
|
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" |
|
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" |
|
PCIE-3-PCIE_NODEV |
3-Error |
PRE5 did not find the correct PCIe device ID is 0x[hec]! |
PRE5 did not find correct PCIe devices. |
cr10k5 |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
PCM_TRACER-3-PCMT_CHANNEL_TYPE_NOT_SUPPORTED |
3-Error |
The channel/group type of ds0 [dec] is not supported by PCM Tracer. |
Can't execute this command on the ds0 number specified. |
PCM_TRACER_DDTS_COMPONENT |
"Refer to the user guide for the channel/group type PCM Tracer " "supports." |
|
PCM_TRACER-3-PCMT_NO_ACTIVE_CALL |
3-Error |
No active calls to trace. |
PCM Tracer can be applied only on active calls. |
PCM_TRACER_DDTS_COMPONENT |
"Make sure there is an active call before starting the PCM Tracer." |
|
PCM_TRACER-3-PCMT_NO_CAPTURE_DURATION |
3-Error |
No capture duration configured. |
Capture duration is required for starting the PCM Tracer. |
PCM_TRACER_DDTS_COMPONENT |
"Configure capture duration before starting the PCM Tracer." |
|
PCM_TRACER-3-PCMT_NO_CAPTURE_TDM |
3-Error |
No capture-tdm configured under profile [dec]. |
Capture-tdm is required for starting the PCM Tracer. |
PCM_TRACER_DDTS_COMPONENT |
"Configure capture-tdm before starting the PCM Tracer." |
|
PCM_TRACER-3-PCMT_NO_DEST |
3-Error |
No PCM Tracer capture destination configured. |
Capture destination is required for starting the PCM Tracer. |
PCM_TRACER_DDTS_COMPONENT |
"Configure capture destination before starting the PCM Tracer." |
|
PCM_TRACER-3-PCMT_NO_PROFILE |
3-Error |
No PCM Tracer profile configured. |
Capture profile is required for starting the PCM Tracer. |
PCM_TRACER_DDTS_COMPONENT |
"Configure capture profile before starting the PCM Tracer." |
|
PCM_TRACER-3-PCMT_NOT_SUPPORTED |
3-Error |
PCM Tracer is not supported on slot [dec]. |
Can't execute this command on the slot number specified. |
PCM_TRACER_DDTS_COMPONENT |
"Refer to the user guide for which slot PCM Tracer is supported on." |
|
PCM_TRACER-3-PCMT_RUNNING |
3-Error |
A PCM Tracer session is currently running. |
Can't execute this command since there is a PCM Tracer running now. |
PCM_TRACER_DDTS_COMPONENT |
"Make sure there is no PCM Tracer sesssion running before execute this " "command." |
|
PCM_TRACER-6-PCMT_START |
6-Information |
Starting PCM Trace on channel under profile [dec] |
- |
- |
- |
|
PCM_TRACER-6-PCMT_STOP |
6-Information |
Stopping PCM Trace on channel under profile [dec] |
- |
- |
- |
|
PCM_TRACER-6-PCMT_STOP_FAIL |
6-Information |
Fail to Stop PCM Trace on channel under profile [dec] |
- |
- |
- |
|
PCM_TRACER-6-PCMT_STOP_RUNNING |
6-Information |
Stop PCM capture |
- |
- |
- |
|
PCMCIAFS-3-RESETERR |
3-Error |
PCMCIA disk [dec] [chars] |
PCMCIA disk could not be reset while the system is initiated reload. This will cause a transient disk error disk timeout error when the ROMMON initialization code tries to reads the DIB. This is a transient error and the system will be able to access the disk and continue normal operation. |
- |
LOG_STD_NO_ACTION |
|
PCMCIAFS-4-DFS_FSCK_ERR |
4-Warning |
Error while running fsck on the file [chars]. |
Fsck is running in a loop while walking through the cluster chain of a file and has aborted. |
ata-filesystem |
LOG_STD_DDTS_TAC_DETAILS |
|
PCMCIAFS-5-DFS_CLOSE_ERR |
5-Notice |
Error during close of the file [chars]. [chars] |
An error occured during a file close operation. |
- |
"Enter the <CmdBold>fsck<NoCmdBold> <CmdArg>filesystem prefix:<NoCmdArg> " "command to check and attempt to repair the disk. If this does not " "fix the problem format the disk." |
|
PCMCIAFS-5-DIBERR |
5-Notice |
[dec] [chars] |
The system cannot boot a image from the PCMCIA Flash disk because the Device Information Block is different. The Flash disk can be read by the router but will require formatting by the router before an image can be booted from it. |
- |
"Follow any instructions provided in the error " "message. Before storing a image in the Flash disk " "and trying to boot from this device enter the " "format command to format the flash disk from the " "router. Then copy the desired image to the Flash " "disk and then boot from this device." |
|
PDM-3-POLICY_CONFIG_FAILURE |
3-Error |
Policy Config Failed for Policy id [dec] [chars] |
Trying to configure/program wrong Policy |
- |
"Reconfigure the Policy" |
|
PDM-3-POLICY_DELETE_FAILURE |
3-Error |
Policy Delete Failed for Policy id [dec] |
Trying to delete wrong Policy |
- |
"Unconfigure the Policy again" |
|
PDM-3-POLICY_SYNTAX_FAILURE |
3-Error |
Policy Syntax Failed for Policy id [dec] [chars] |
Trying to configure/program Policy with wrong syntax |
- |
"Reconfigure the Policy with correct syntax" |
|
PDM-3-SERVICE_CONFIG_FAILURE |
3-Error |
Service Config Failed for Service id [dec] |
Trying to configure/program wrong Service |
- |
"Reconfigure the Service" |
|
PDM-3-SERVICE_DELETE_FAILURE |
3-Error |
Service Delete Failed for Service id [dec] |
Trying to delete wrong Service |
- |
"Unconfigure the Service again" |
|
PDM-3-SERVICE_SYNTAX_FAILURE |
3-Error |
Service Syntax Failed for Service id [dec] |
Trying to configure/program Service with wrong syntax |
- |
"Reconfigure the Service with correct syntax" |
|
PDU_SESS_PROXY-2-PROXY_IPC_INIT_FAILED |
2-Critical |
QFP PDU_SESS Proxy IPC interface initialization failure result: [dec]. |
Cisco internal software error. QFP PDU_SESS Proxy initialization detected that the IPC interface initialization failed. QFP PDU_SESS proxy will not be functional while this condition exists. |
qfp-pdu_sess keyword:pdu_sess |
LOG_STD_ACTION |
|
PDU_SESS_PROXY-3-PDU_SESS_MEM_EXTEND_FAILED |
3-Error |
PDU_SESS IPC subtype: [dec] |
Extending memory failed. |
qfp-pdu_sess keyword:pdu_sess |
LOG_STD_ACTION |
|
PDU_SESS_PROXY-3-PDU_SESS_MEM_REQ_FAILED |
3-Error |
PDU_SESS IPC subtype: [dec] |
Requesting more memory failed. |
qfp-pdu_sess keyword:pdu_sess |
LOG_STD_ACTION |
|
PDU_SESS_PROXY-3-PROXY_BAD_MSG |
3-Error |
QFP PDU_SESS Proxy received bad length message type [dec] |
Cisco internal software error. QFP PDU_SESS Proxy received a corrupted message from control plane. This message will be ignored. |
qfp-pdu_sess keyword:pdu_sess |
LOG_STD_ACTION |
|
PDU_SESS_PROXY-3-PROXY_IPC_ALLOC_FAILED |
3-Error |
QFP PDU_SESS Proxy [chars] message lost due to message buffer allocation failure. |
Cisco internal software error. QFP PDU_SESS Proxy message processing detected a message buffer allocation failure. The message is lost as the result of this condition. |
qfp-pdu_sess keyword:pdu_sess |
LOG_STD_ACTION |
|
PDU_SESS_PROXY-3-PROXY_IPC_SEND_FAILED |
3-Error |
QFP PDU_SESS Proxy [chars] message lost due to message sent failure result: [dec]. |
Cisco internal software error. QFP PDU_SESS Proxy message processing detected a message sent failure. The message is lost as the result of this condition. |
qfp-pdu_sess keyword:pdu_sess |
LOG_STD_ACTION |
|
PDU_SESS_PROXY-3-PROXY_NULL_MSG |
3-Error |
QFP PDU_SESS Proxy received null message |
Cisco internal software error. QFP PDU_SESS Proxy received an null message from control plane. This message will be ignored. |
qfp-pdu_sess keyword:pdu_sess |
LOG_STD_ACTION |
|
PDU_SESS_PROXY-4-PROXY_INVALID_MSG |
4-Warning |
QFP PDU_SESS Proxy received invalid message type [dec] |
Cisco internal software error. QFP PDU_SESS Proxy received an invalid message from control plane. This message will be ignored. |
qfp-pdu_sess keyword:pdu_sess |
LOG_STD_ACTION |
|
PDU_SESS_PROXY-4-PROXY_INVALID_MSG_LEN |
4-Warning |
QFP PDU_SESS Proxy IPC invalid length [dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Cisco internal software error. QFP PDU_SESS Proxy received invalid IPC message length from control plane. This message will be ignored. |
qfp-pdu_sess keyword:pdu_sess |
LOG_STD_ACTION |
|
PEERSM-3-LCON |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
PEGA_PTP_ENABLER-3-PEGA_PTP_LICENSE_EULA_NOT_ACCEPTED |
3-Error |
\n********************************************************* \ \nWARNING: PTP License is not yet activated. \ \nPlease configure 'license feature ptp'\ \n*********************************************************\n |
- |
- |
LOG_STD_ACTION |
|
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-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_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>" |
|
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-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-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_MON_ASYNC-3-INIT |
3-Error |
[chars] |
Failure during perf-mon async initialization |
media-mon |
LOG_STD_ACTION |
|
PERF_MON_ASYNC-3-LIST |
3-Error |
Failed to [chars] list [chars] |
A list operation failed. This could be caused by memory corruption |
media-mon |
LOG_STD_ACTION |
|
PERF_MON_ASYNC-3-MEM |
3-Error |
Memory [chars] failed - [chars] |
Memory creation failed during the initialization |
media-mon |
LOG_STD_ACTION |
|
PERF_MON_MENG-3-INIT |
3-Error |
[chars] |
Failure during perf-mon data plane initialization |
media-mon |
LOG_STD_ACTION |
|
PERF_MON_MENG-3-LIST |
3-Error |
Failed to [chars] list [chars] |
A list operation failed. This could be caused by memory corruption |
media-mon |
LOG_STD_ACTION |
|
PERF_MON_MENG-3-MEM |
3-Error |
Memory [chars] failed - [chars] |
Memory operation failure |
media-mon |
LOG_STD_ACTION |
|
PERF_MON_REACT-0-EMERGCLEAR |
0-Emergency |
TCA CLEAR. \nDetailed info: [chars][chars][chars][chars][chars]\n |
A threshold crossing alarm is cleared. The alarm severity is EMERGENT. |
media-mon |
LOG_STD_NO_ACTION |
|
PERF_MON_REACT-0-EMERGSET |
0-Emergency |
TCA RAISE. \nDetailed info: [chars][chars][chars][chars][chars]\n |
A threshold crossing alarm is raised. The alarm severity is EMERGENT. system is unusable. |
media-mon |
LOG_STD_NO_ACTION |
|
PERF_MON_REACT-1-ALERTCLEAR |
1-Alert |
TCA CLEAR. \nDetailed info: [chars][chars][chars][chars][chars]\n |
A threshold crossing alarm is cleared. The alarm severity is ALERT. |
media-mon |
LOG_STD_NO_ACTION |
|
PERF_MON_REACT-1-ALERTSET |
1-Alert |
TCA RAISE. \nDetailed info: [chars][chars][chars][chars][chars]\n |
A threshold crossing alarm is raised. The alarm severity is ALERT. |
media-mon |
LOG_STD_NO_ACTION |
|
PERF_MON_REACT-2-CRITCLEAR |
2-Critical |
TCA CLEAR. \nDetailed info: [chars][chars][chars][chars][chars]\n |
A threshold crossing alarm is cleared. The alarm severity is CRITICAL. |
media-mon |
LOG_STD_NO_ACTION |
|
PERF_MON_REACT-2-CRITSET |
2-Critical |
TCA RAISE. \nDetailed info: [chars][chars][chars][chars][chars]\n |
A threshold crossing alarm is raised. The alarm severity is CRITICAL. |
media-mon |
LOG_STD_NO_ACTION |
|
PERF_MON_REACT-2-INFOCLEAR |
2-Critical |
TCA CLEAR. \nDetailed info: [chars][chars][chars][chars][chars]\n |
A threshold crossing alarm is cleared. The alarm severity is INFO. |
media-mon |
LOG_STD_NO_ACTION |
|
PERF_MON_REACT-2-INFOSET |
2-Critical |
TCA RAISE. \nDetailed info: [chars][chars][chars][chars][chars]\n |
A threshold crossing alarm is raised. The alarm severity is INFO. |
media-mon |
LOG_STD_NO_ACTION |
|
PERF_MON_REACT-3-ERRCLEAR |
3-Error |
TCA CLEAR. \nDetailed info: [chars][chars][chars][chars][chars]\n |
A threshold crossing alarm is cleared. The alarm severity is ERROR |
media-mon |
LOG_STD_NO_ACTION |
|
PERF_MON_REACT-3-ERRSET |
3-Error |
TCA RAISE. \nDetailed info: [chars][chars][chars][chars][chars]\n |
A threshold crossing alarm is raised. The alarm severity is ERROR |
media-mon |
LOG_STD_NO_ACTION |
|
PERF_MON-3-CHUNKCREATE |
3-Error |
Failed to chunk create memory for [chars] |
Unable to chunk create memory chunk |
media-mon |
LOG_STD_ACTION |
|
PERF_MON-3-CHUNKDESTROY |
3-Error |
Failed to chunk destroy memory for [chars] |
Unable to chunk destroy memory chunk |
media-mon |
LOG_STD_ACTION |
|
PERF_MON-3-CHUNKMALLOC |
3-Error |
Failed to malloc chunk memory for [chars] |
Unable to malloc memory chunk malloc failed |
media-mon |
LOG_STD_ACTION |
|
PERF_MON-3-DEFRECCREATE |
3-Error |
Creation of default-record [chars] failed - reason [chars] |
Failed to create system defined default flow-records |
media-mon |
LOG_STD_ACTION |
|
PERF_MON-3-LIST |
3-Error |
Failed to [chars] list [chars] |
A list operation failed. This could be caused by memory corruption |
media-mon |
LOG_STD_ACTION |
|
PERF_MON-3-MEM |
3-Error |
Memory [chars] failed - [chars] |
Memory creation failed during the initialization |
media-mon |
LOG_STD_ACTION |
|
PERF_MON-3-PARSER |
3-Error |
[chars] |
Parser failure. This could due to invalid command or corrupted csb |
media-mon |
LOG_STD_ACTION |
|
PERF_MON-3-RECSETKEY |
3-Error |
Adding key fields for default-record [chars] failed - reason [chars] |
Failed to add key fields for defined default flow-records |
media-mon |
LOG_STD_ACTION |
|
PERF_MON-3-RECSETNONKEY |
3-Error |
Adding non-key fieds for [chars] default-record failed - reason [chars] |
Failed to add non-key fields for defined default flow-records |
media-mon |
LOG_STD_ACTION |
|
PERF_MON-3-RECSETPROP |
3-Error |
Setting property for [chars] default-record failed - reason [chars] |
Failed to set properties for system defined default flow-records |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-CHUNK_INIT |
3-Error |
Chunk is not initialized - [chars] |
Chunk memory is not created or failed to be created |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-CHUNKCREATE |
3-Error |
Failed to chunk create memory for [chars] |
Unable to chunk create memory chunk |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-CHUNKDESTROY |
3-Error |
Failed to chunk destroy memory for [chars] |
Unable to chunk destroy memory chunk |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-CHUNKMALLOC |
3-Error |
Failed to malloc chunk memory for [chars] |
Unable to malloc memory chunk malloc failed |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-CONV_FAILURE |
3-Error |
Conversion failed - [chars] |
Conversion from one format to another has failed |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-DEFRECCREATE |
3-Error |
Creation of default-record [chars] failed - reason [chars] |
Failed to create system defined default flow-records |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-EXP_ATTR |
3-Error |
Failed to set flow attribute for exporter - [chars] |
An error occured when setting flow attribute use to transform match and collect metrics to export message |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-FDEF_NOTIFY |
3-Error |
Failed to register PD flow definition [chars] |
The flow def received from ME or PD is NULL |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-FDEF_TEMP |
3-Error |
Invalid flow definition template - [chars] |
The template was not initialized during system initialization |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-FIELDENA |
3-Error |
Enable fnf field [chars] failed - [chars] |
Failed to enable a field for use with a config |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-FLOW_EXCEED |
3-Error |
The number of flows has exceeded 95%% of the configured maximum flow. [chars]\n |
This is warning message if the flow size exceeds the maximum value |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-FLOW_NONEXCEED |
3-Error |
The number of flows is below 85%% of the configured maximum flow. [chars]\n |
This is info message if the flow size falls below the maximum value |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-FNFPARSERENA |
3-Error |
Enable flow monitor parser failed - [chars] |
Failed to enable performance monitor typed monitor |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-INV_ARG |
3-Error |
The argument is not valid - [chars] |
An internal error occurred. The argument for an internal API is not valid |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-INV_COMMON_MONITOR |
3-Error |
The common monitor ptr is invalid |
An internal error occurred. The common monitor ptr saved in the performance-monitor monitor is NULL |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-INV_MONITOR_TYPE |
3-Error |
The monitor type [dec] is invalid |
An internal error occurred. The monitor type is out of the range |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-INV_POLICY_MAP |
3-Error |
The retrieved policy map is invalide - [chars] |
An internal error occurred. The policy map saved in csb is invalid |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-INV_REACT |
3-Error |
react is not valid - [chars] |
This is an internal error the saved react info is corrupted |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-INV_TARGET |
3-Error |
A target object does not exist - [chars] |
An internal error occurred. Try to access a null target obj |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-INVCMD |
3-Error |
Invalid cmd type [dec] to [chars] |
This is an internal error the command type is invalid |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-INVCRIT |
3-Error |
Invalid react criteria [dec] to [chars] |
This is an internal error the saved react criteria is corrupted |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-INVFIELDTYPE |
3-Error |
Enable fnf field [dec] failed - invalid field type |
Failed to enable a field for use with a config |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-INVMODE |
3-Error |
Invalid performance-monitor configuration mode |
This is an internal error the configuration sub mode is invalid |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-INVMONITOR |
3-Error |
The flow monitor pointer is invalid |
An internal error occurred. The performance-monitor monitor pointer saved in the common monitor is NULL |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-MEMLEAK |
3-Error |
Memory leak detected - [chars] |
A memory leak is detected during media-mon memory handling |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-MMONOBJDUP |
3-Error |
A mmon_obj already exists for policy [chars] class [chars]\n |
A mmon obj already exists in the MMON DB under the same policy and class for CLASS_ADD |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-MMONOBJINV |
3-Error |
A mmon_obj does not exist for policy [chars] class [chars]\n |
Unable to find an existing mmon obj for event CLASS_REMOVE and CLASS_MODIFY |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-MONITOR_CREATE |
3-Error |
Failed to create Monitor at Metering layer. Error - [chars] |
Failed to create monitor at Metering layer for this policy. The error code provides the reason for failure. No statistics will be collected. |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-MONITOR_DELETE |
3-Error |
Failed to delete Monitor at Metering layer. Error - [chars] |
Failed to delete monitor at Metering layer for this policy. The error code provides the reason for failure. |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-MONITOR_SYNC |
3-Error |
Out of sync - [chars] |
This is an internal error the reference count in flow monitor reached negative |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-NOPARENTMMONOBJ |
3-Error |
Internal error target has no parent mmon object |
None valid pointer to mmon obj found in tgt obj for CLASS_REMOVE |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-NULLFLOW |
3-Error |
A flow does not exist |
An internal error occurred. Try to access a null flow |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-NULLHIST |
3-Error |
A history bucket does not exist |
An internal error occurred. Try to access a null history |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-PROC_MSG |
3-Error |
Failed to process received record - [chars] |
Failure during the process of handling the received fnf record |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-RECSETKEY |
3-Error |
Adding key fields for default-record [chars] failed - reason [chars] |
Failed to add key fields for defined default flow-records |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-RECSETNONKEY |
3-Error |
Adding non-key fieds for [chars] default-record failed - reason [chars] |
Failed to add non-key fields for defined default flow-records |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-RECSETPROP |
3-Error |
Setting property for [chars] default-record failed - reason [chars] |
Failed to set properties for system defined default flow-records |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-RESETMODE |
3-Error |
Failed to reset csb vars |
Reset of the csb vars failed due to lack of memory |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-SIB_LINK |
3-Error |
sib member [dec] with [dec] error [chars] |
Failed to link two sibling members in the MMON PD |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_INFRA-3-SIB_UNLINK |
3-Error |
sib member [dec] from [dec] error [chars] |
Failed to unlink two sibling members in the MMON PD |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_METER-3-INITFAIL |
3-Error |
Metering engine initialization fail - [chars]\n |
An internal error occurred. Unable to initialize the performance monitor metering engine |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_METER-3-MONITOR_UNBIND |
3-Error |
Failed to unbind monitor from target. Error - [chars] |
Failed to unbind monitor at Metering layer for this target. The error code provides the reason for failure. |
media-mon |
LOG_STD_ACTION |
|
PERF_TRAFFIC_REACT-0-EMERGCLEAR |
0-Emergency |
TCA CLEAR. \nDetailed info: [chars][chars][chars][chars][chars]\n |
A threshold crossing alarm is cleared. The alarm severity is EMERGENT. |
media-mon |
LOG_STD_NO_ACTION |
|
PERF_TRAFFIC_REACT-0-EMERGSET |
0-Emergency |
TCA RAISE. \nDetailed info: [chars][chars][chars][chars][chars]\n |
A threshold crossing alarm is raised. The alarm severity is EMERGENT. system is unusable. |
media-mon |
LOG_STD_NO_ACTION |
|
PERF_TRAFFIC_REACT-1-ALERTCLEAR |
1-Alert |
TCA CLEAR. \nDetailed info: [chars][chars][chars][chars][chars]\n |
A threshold crossing alarm is cleared. The alarm severity is ALERT. |
media-mon |
LOG_STD_NO_ACTION |
|
PERF_TRAFFIC_REACT-1-ALERTSET |
1-Alert |
TCA RAISE. \nDetailed info: [chars][chars][chars][chars][chars]\n |
A threshold crossing alarm is raised. The alarm severity is ALERT. |
media-mon |
LOG_STD_NO_ACTION |
|
PERF_TRAFFIC_REACT-2-CRITCLEAR |
2-Critical |
TCA CLEAR. \nDetailed info: [chars][chars][chars][chars][chars]\n |
A threshold crossing alarm is cleared. The alarm severity is CRITICAL. |
media-mon |
LOG_STD_NO_ACTION |
|
PERF_TRAFFIC_REACT-2-CRITSET |
2-Critical |
TCA RAISE. \nDetailed info: [chars][chars][chars][chars][chars]\n |
A threshold crossing alarm is raised. The alarm severity is CRITICAL. |
media-mon |
LOG_STD_NO_ACTION |
|
PERF_TRAFFIC_REACT-2-INFOCLEAR |
2-Critical |
TCA CLEAR. \nDetailed info: [chars][chars][chars][chars][chars]\n |
A threshold crossing alarm is cleared. The alarm severity is INFO. |
media-mon |
LOG_STD_NO_ACTION |
|
PERF_TRAFFIC_REACT-2-INFOSET |
2-Critical |
TCA RAISE. \nDetailed info: [chars][chars][chars][chars][chars]\n |
A threshold crossing alarm is raised. The alarm severity is INFO. |
media-mon |
LOG_STD_NO_ACTION |
|
PERF_TRAFFIC_REACT-3-ERRCLEAR |
3-Error |
TCA CLEAR. \nDetailed info: [chars][chars][chars][chars][chars]\n |
A threshold crossing alarm is cleared. The alarm severity is ERROR |
media-mon |
LOG_STD_NO_ACTION |
|
PERF_TRAFFIC_REACT-3-ERRSET |
3-Error |
TCA RAISE. \nDetailed info: [chars][chars][chars][chars][chars]\n |
A threshold crossing alarm is raised. The alarm severity is ERROR |
media-mon |
LOG_STD_NO_ACTION |
|
PETRA_IMSP_CEF-3-NOFIB |
3-Error |
FIB entry is null |
An unexpected condition has occurred which is due to the absence of\n\ a FIB entry structure. |
petra-fwdmgr |
"show ip cef" |
|
PETRA_IMSP_CEF-3-NOFIBIDB |
3-Error |
FIB interface is null |
An unexpected condition has occurred which is due to the absence of\n\ a FIB interface structure. |
petra-fwdmgr |
"show ip cef" |
|
PETRA_IMSP_CEF-3-NOFIBPUSHCNT |
3-Error |
FIB push counter is null |
An unexpected condition has occurred which is due to the absence of\n\ a FIB push counter structure. |
petra-fwdmgr |
"show ip cef" |
|
PETRA_IMSP_CEF-3-NOFIBSB |
3-Error |
FIB SB entry is null |
An unexpected condition has occurred which is due to the absence of\n\ a FIB SB entry structure. |
petra-fwdmgr |
"show ip cef" |
|
PETRA_IMSP_CEF-3-NOFIBTABLE |
3-Error |
FIB table is null |
An unexpected condition has occurred which is due to the absence of\n\ a FIB table structure. |
petra-fwdmgr |
"show ip cef" |
|
PETRA_IMSP_CEF-4-UPDSTATSERR |
4-Warning |
Update CEF statistics error |
An unexpected condition has occurred when updating cef statistics |
petra-fwdmgr |
LOG_STD_ACTION |
|
PF-4-MEM_UNAVAIL |
4-Warning |
Memory was not available to perform the protocol filtering action |
Protocol filtering is unable to operate because of a lack of memory |
- |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
PF-4-PROC_START_ERR |
4-Warning |
Protocol filtering unable to start |
The protocol filtering process was unable to be created for unknown\n\ reasons. |
- |
"Start protocol filtering again in case the condition was transient.\n\ If this still fails reload the device" |
|
PF-4-UNKN_ERR |
4-Warning |
An unknown operational error occurred |
Protocol filtering is unable to operate because an internal operation\n\ generated an error which was not expected to ever happen |
- |
"Because of the unexpected nature of the problem the only recommended\n\ action is to reload the device" |
|
PF-5-SPANDSTOFF |
5-Notice |
Protocol filtering disabled on interface [chars] because it is a span destination |
SWC Sensor Registration failed! |
- |
"This message is for informational purposes only" |
|
PF-5-TRUNKPFOFF |
5-Notice |
Protocol filtering disabled on interface [chars] because it is a trunk |
Protocol filtering does not operate on trunks. The protocol filtering\n\ configuration stays with the trunk port but it has no effect and does\n\ not appear when you show all non-default protocol filters. |
- |
- |
|
PFINIT-1-CONFIG_SYNC_FAIL |
1-Alert |
Sync'ing the [chars] configuration to the standby Router failed. |
CONFIG_SYNC_FAIL_EXPLANATION |
cat6000-ha |
CONFIG_SYNC_FAIL_ACTION |
|
PFINIT-1-CONFIG_SYNC_FAIL_RETRY |
1-Alert |
Sync'ing the [chars] configuration to the standby Router FAILED the file may be already locked by a command like: show config. Will attempt to sync [dec] more time[chars] |
CONFIG_SYNC_FAIL_EXPLANATION |
cat6000-ha |
CONFIG_SYNC_FAIL_ACTION |
|
PFINIT-2-EOBC |
2-Critical |
[chars] |
The PF subsystem could not send IPC bootstap messages to RP. |
cat6000-ha |
LOG_STD_SH_TECH_ACTION |
|
PFINIT-2-IPCREINIT |
2-Critical |
Unable to reinitialzie IPC |
The PF subsystem could not reinitailize IPC. |
cat6000-ha |
LOG_STD_SH_TECH_ACTION |
|
PFINIT-2-IPCSEAT |
2-Critical |
Unable to add/remove IPC seats for [chars] |
The PF subsystem could not add/remove IPC seats. |
cat6000-ha |
LOG_STD_SH_TECH_ACTION |
|
PFINIT-2-NOMEM |
2-Critical |
No memory available for [chars] |
The PF subsystem could not obtain the memory it needed. |
cat6000-ha |
LOG_STD_SH_TECH_ACTION |
|
PFINIT-5-CONFIG_SYNC |
5-Notice |
Sync'ing the [chars] configuration to the standby Router. |
The configuration has been successfully synced to the standby Router |
cat6000-ha |
"This is an informational message. No action is required." |
|
PFINIT-5-CONFIG_SYNC_NOT_SUPPORTED |
5-Notice |
Sync'ing the [chars] configuration to the standby Router is not supported. |
CONFIG_SYNC_FAIL_EXPLANATION |
cat6000-ha |
CONFIG_SYNC_FAIL_ACTION |
|
PFINIT-6-PROC_MAX |
6-Information |
Process-max-value changed from [dec] to [dec] millisecs |
Informational messages regarding change in Process-max-value |
- |
- |
|
PFR_BR-1-ALERT |
1-Alert |
[chars] |
- |
pfr |
"" |
|
PFR_BR-3-INTERNAL_ERROR |
3-Error |
[chars]:[chars] |
- |
pfr |
"" |
|
PFR_BR-4-WARNING |
4-Warning |
[chars] |
- |
pfr |
"" |
|
PFR_BR-5-BR_STATUS_CHANGE |
5-Notice |
[chars] |
- |
pfr |
"" |
|
PFR_BR-5-MC_STATUS_CHANGE |
5-Notice |
MC [chars] is [chars] |
- |
pfr |
"" |
|
PFR_MC-1-ALERT |
1-Alert |
[chars] |
- |
pfr |
"" |
|
PFR_MC-3-INTERNAL_ERROR |
3-Error |
[chars]:[chars] |
- |
pfr |
"" |
|
PFR_MC-3-VERSION_MISMATCH |
3-Error |
[chars] |
- |
pfr |
"" |
|
PFR_MC-3-WARNING |
3-Error |
[chars] |
- |
pfr |
"" |
|
PFR_MC-5-BR_STATUS_CHANGE |
5-Notice |
BR [chars] [chars] |
- |
pfr |
"" |
|
PFR_MC-5-COST_MINIMIZATION |
5-Notice |
[chars] |
- |
pfr |
"" |
|
PFR_MC-5-EXPORT_STATUS_CHANGE |
5-Notice |
[chars] |
- |
pfr |
"" |
|
PFR_MC-5-INTERFACE_STATUS_CHANGE |
5-Notice |
BR [chars] [chars] IF [chars] [chars] |
- |
pfr |
"" |
|
PFR_MC-5-MC_STATUS_CHANGE |
5-Notice |
MC is [chars] |
- |
pfr |
"" |
|
PFR_MC-5-OOP_LINK |
5-Notice |
[chars] |
- |
pfr |
"" |
|
PFR_MC-5-PBR_STATUS_CHANGE |
5-Notice |
[chars] |
- |
pfr |
"" |
|
PFR_MC-5-ROUTE_EVENT |
5-Notice |
[chars] |
- |
pfr |
"" |
|
PFR_MC-5-TOP_TALKER_STATUS |
5-Notice |
[chars] |
- |
pfr |
"" |
|
PFR_MC-6-OOP_ACTIVE_MODE |
6-Information |
[chars] |
- |
pfr |
"" |
|
PFR_MC-6-OOP_PASSIVE_MODE |
6-Information |
[chars] |
- |
pfr |
"" |
|
PFR_MC-6-ROUTE_EVENT_INFO |
6-Information |
[chars] |
- |
pfr |
"" |
|
PG_TCP-3-MSG_ERR |
3-Error |
[chars] |
Error Messages |
pagent |
"try debug command" |
|
PG_TCP-6-MSG_INF |
6-Information |
[chars] |
Program information |
- |
- |
|
PG_TCP-7-MSG_DBG |
7-Debug |
[chars] |
Debug Messages |
- |
- |
|
PGEN_IPC_MSG-2-ALLOC_ERR |
2-Critical |
Unable to allocate IPC message |
- |
- |
- |
|
PGEN_IPC_MSG-2-CREATE_REG_ERR |
2-Critical |
Unable to create Pagent IPC Registry |
- |
- |
- |
|
PGEN_IPC_MSG-2-HWIDB_PG_ALLOC_ERR |
2-Critical |
Unable to allocate hwidb_pg structure |
- |
- |
- |
|
PGEN_IPC_MSG-2-IDBLIST_CREATE_ERR |
2-Critical |
Unable to create SVIP IDB list |
- |
- |
- |
|
PGEN_IPC_MSG-2-NO_HANDLER_ERR |
2-Critical |
No handler found for IPC code %ld |
- |
- |
- |
|
PGEN_IPC_MSG-2-PAK_ALLOC_ERR |
2-Critical |
Unable to allocate download packet structure |
- |
- |
- |
|
PGEN_IPC_MSG-2-PAK_DATA_ALLOC_ERR |
2-Critical |
Unable to allocate download packet data |
- |
- |
- |
|
PGEN_IPC_MSG-2-PG_FASTCOUNT_ERR |
2-Critical |
Unable to stop/start Pagent fastcount |
- |
- |
- |
|
PGEN_IPC_MSG-2-PG_FILTER_LIST_ALLOC_ERR |
2-Critical |
Unable to allocate pg_filter_list structure |
- |
- |
- |
|
PGEN_IPC_MSG-2-PGEN_IPC_REPLAY_END_ALLOC_ERR |
2-Critical |
Unable to allocate IPC message for end of replay |
- |
- |
- |
|
PGEN_IPC_MSG-2-PGEN_IPC_REPLY_ALLOC_ERR |
2-Critical |
Unable to allocate IPC message for reply |
- |
- |
- |
|
PGEN_IPC_MSG-2-PORT_CREATE_ERR |
2-Critical |
Unable to create Pagent IPC port |
- |
- |
- |
|
PGEN_IPC_MSG-2-PORT_LOCATE_ERR |
2-Critical |
Unable to locate [chars] port during registration |
- |
- |
- |
|
PGEN_IPC_MSG-2-PORT_OPEN_ERR |
2-Critical |
Unable to open port: [chars] |
- |
- |
- |
|
PGEN_IPC_MSG-2-PORT_SEND_ERR |
2-Critical |
Unable to send message |
- |
- |
- |
|
PGEN_IPC_MSG-2-SELECT_ALLOC |
2-Critical |
Allocate download selection %ld |
- |
- |
- |
|
PGEN_IPC_MSG-2-SELECT_ALLOC_ERR |
2-Critical |
Unable to allocate select context structure |
- |
- |
- |
|
PGEN_IPC_MSG-2-SELECT_DATA_ALLOC_ERR |
2-Critical |
Unable to allocate download selection data |
- |
- |
- |
|
PGEN_IPC_MSG-2-SELECT_PAK_ALLOC_ERR |
2-Critical |
Unable to allocate download selection packet structure |
- |
- |
- |
|
PGEN_IPC_MSG-2-SELECT_RECV_ERR |
2-Critical |
Received unexpected selection packet |
- |
- |
- |
|
PGEN_IPC_MSG-2-SEQ_LOCATE_ERR |
2-Critical |
Unable to allocate sequence storage |
- |
- |
- |
|
PGEN_VIP_MSG-2-PGEN_VIP_MSG_TEST |
2-Critical |
[chars] |
- |
- |
- |
|
PGEN_VIP_MSG-2-PGEN_VIP_MSG_TRANSMIT_PAK |
2-Critical |
Unable to allocate VIP transmit pak |
- |
- |
- |
|
PGM-3-EXP_TSI_SQN_ERR |
3-Error |
Expiring TSI [chars] has retransmit state |
An expiring PGM TSI has unexpired retransmit state. This can only\n\ occur due to an internal error or due to unfreeable memory. |
ipmulticast |
LOG_STD_REDUCE_ACTION LOG_STD_RECUR_ACTION |
|
PGM-3-PAK_ALLOC_ERR |
3-Error |
Failed to allocate buffer for [chars] |
- |
- |
LOG_STD_REDUCE_ACTION |
|
PGM-3-RTX_STATE_ALLOC_ERR |
3-Error |
Failed to allocate [chars] state |
Resources memory for retransmit state are exhausted\n\msgdef_recommended_action Manually clear all retransmit state |
- |
- |
|
PGM-3-RTX_STATE_FREE_ERR |
3-Error |
Failed to free [chars] state |
Resources memory for retransmit state are not serviceable. |
ipmulticast |
- |
|
PGM-6-ADDR_ERR |
6-Information |
Invalid [chars] address [inet] in [chars] |
Received the packet with invalid address. |
- |
LOG_STD_NO_ACTION |
|
PGM-6-PAK_IIF_FIXUP |
6-Information |
Pak for [inet] received on [inet] fixed input interface |
A PGM packet was recieved on an interface other than the one it was\n\ addressed to. |
- |
LOG_STD_NO_ACTION |
|
PGM-6-PAK_MALFORMED_ERR |
6-Information |
Malformed packet: [chars] |
A PGM packet did not pass the internal sanity check. |
- |
LOG_STD_NO_ACTION |
|
PGM-6-QUEUE_FULL |
6-Information |
Serviced full queue of PGM packets. |
The PGM process is busy either because of excessive retransmit\n\ state or because of excessive traffic. |
- |
LOG_STD_REDUCE_ACTION |
|
PGM-6-TSI_GROUP_CHANGE |
6-Information |
TSI group changed from [inet] to [inet] |
A PGM SPM advertising a new group for the TSI was processed. |
- |
LOG_STD_NO_ACTION |
|
PGM-6-TSI_SOURCE_CHANGE |
6-Information |
TSI source changed from [inet] to [inet] |
A PGM SPM advertising a new source for the TSI was processed. |
- |
LOG_STD_NO_ACTION |
|
PGTT_IPC_MSG-2-ALLOC_ERR |
2-Critical |
Unable to allocate message packet to SECONDARY [dec]. |
- |
- |
- |
|
PGTT_IPC_MSG-2-IPC_MSG_HANDLER_ERR |
2-Critical |
Error handling IPC message from SECONDARY processor. |
- |
- |
- |
|
PGTT_IPC_MSG-2-IPC_PORT_TO_SECONDARY_ERR |
2-Critical |
Unable to open IPC port to SECONDARY slot %ld: [chars]. |
- |
- |
- |
|
PGTT_IPC_MSG-2-PGTT_MSG_DEBUG |
2-Critical |
[chars] |
- |
- |
- |
|
PGTT_IPC_MSG-2-PKTS_ALLOC_ERR |
2-Critical |
PKTS could not allocate message packet to SECONDARY [dec]. |
- |
- |
- |
|
PGTT_IPC_MSG-2-PKTS_COUNT_REPLY_ALLOC_ERR |
2-Critical |
PKTS could not allocate count reply message. |
- |
- |
- |
|
PGTT_IPC_MSG-2-RVT_PRIMARY_CREATE_ERR |
2-Critical |
Unable to create RVT-PRIMARY port. |
- |
- |
- |
|
PHY-4-BADTRANSCEIVER |
4-Warning |
An inappropriate transceiver has been inserted in interface [chars]. |
An inappropriate transceiver is inserted at the interface specified in the error message. This transceiver should not be used in this system. |
firmware |
"Remove the specified transceiver. If this " "transceiver was purchased from Cisco please contact " "Cisco TAC to get the transceiver replaced." |
|
PHY-4-CHECK_SUM_FAILED |
4-Warning |
SFP EEPROM data check sum failed for SFP interface [chars] |
The SFP was identified as a Cisco SFP but the system was unable to read vendor-data information to verify its correctness. |
firmware |
"Remove and reinsert the SFP. If it fails " "again in the same way the SFP may be defective." |
|
PHY-4-EXCESSIVE_ERRORS |
4-Warning |
Excessive FCS data or idle word errors found on interface [chars] |
The system has detected excessive FCS data word or idle word errors on the specified interface. |
firmware |
"Issue the <CmdBold>show interface<noCmdBold> " "command on the specified interface and check for CRC and " "other input errors. If errors are excessive issue the " "<CmdBold>shut<noCmdBold> command followed by the " "<CmdBold>no shut<noCmdBold> command to reset the interface." |
|
PHY-4-MODULE_DUP |
4-Warning |
SFPs in [chars] and in [chars] have duplicate vendor-id and serial numbers |
The SFP was identified as a Cisco SFP but its vendor ID and serial number match that of another SFP on the system. |
firmware |
LOG_STD_ACTION |
|
PHY-4-SFP_NOT_SUPPORTED |
4-Warning |
The SFP in [chars] is not supported |
This SFP type is not supported on this switch. |
firmware |
LOG_STD_ACTION |
|
PHY-4-SFP_PLUS_NOT_SUPPORTED |
4-Warning |
The SFP PLUS in [chars] is not supported |
This SFP PLUS type is not supported on this switch. |
firmware |
LOG_STD_ACTION |
|
PHY-4-UNSUPPORTED_SFP_CARRIER |
4-Warning |
Unsupported SFP carrier module found in [chars] |
The SFP carrier module was identified as an unsupported non-Cisco SFP carrier module. |
firmware |
"Remove the unsupported SFP and procure a " "supported module" |
|
PHY-4-UNSUPPORTED_TRANSCEIVER |
4-Warning |
Unsupported transceiver found in [chars] |
The module was identified as an unsupported non-Cisco transceiver. |
firmware |
LOG_STD_ACTION |
|
PHYSINTFCDOWN-3-MPLS_TE |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
PIM_PROT-3-IDB_CREATE |
3-Error |
Interface Manager error - [chars] in [chars] : [chars] |
Internal error |
ipmulticast |
LOG_STD_RECUR_ACTION |
|
PIM_PROT-3-INTERNAL_ERR |
3-Error |
[chars] |
Internal error |
ipmulticast |
LOG_STD_RECUR_ACTION |
|
PIM_PROT-3-LIST_ERR |
3-Error |
List error in [chars] : [chars] |
Internal error |
ipmulticast |
LOG_STD_RECUR_ACTION |
|
PIM_PROT-3-MSG_SEND_ERR |
3-Error |
[chars] |
An internal error occured while trying to send a message. Events scheduled to happen on reception of the message like deletion of the pim tunnel idb may not take place. |
ipmulticast |
LOG_STD_RECUR_ACTION |
|
PIM_PROT-3-NULL_UNIT |
3-Error |
NULL input pointer parameter for getting register tunnel unit |
A NULL input parameter was specified in a function call to obtain the register tunnel IDB unit number associated with a rendezvous point IP address. The register tunnel for this rendezvous point can not be allocated. |
ipmulticast |
LOG_STD_RECUR_ACTION |
|
PIM_PROT-3-PAK_ERR |
3-Error |
An internal error occured while processing a packet queue |
Managed queue event received without a packet. Internal Error |
ipmulticast |
LOG_STD_RECUR_ACTION |
|
PIM_PROT-3-PROTOCOL_ERR |
3-Error |
[chars] - [chars] : [chars] |
Internal error |
ipmulticast |
LOG_STD_RECUR_ACTION |
|
PIM_PROT-3-RP_INIT |
3-Error |
[chars] in [chars] : [chars] |
Internal error |
ipmulticast |
LOG_STD_RECUR_ACTION |
|
PIM_PROT-3-SHUTDOWN_ERR |
3-Error |
Error in [chars] : [chars] |
Internal error |
ipmulticast |
LOG_STD_RECUR_ACTION |
|
PIM_PROT-3-SRC_UPDATE_ERR |
3-Error |
Error in [chars] : [chars] |
Internal error |
ipmulticast |
LOG_STD_RECUR_ACTION |
|
PIM_PROT-3-TABLE_ERR |
3-Error |
[chars] |
Errors related to PIM table creation and management |
ipmulticast |
LOG_STD_RECUR_ACTION |
|
PIM_PROT-3-WAVL_INIT |
3-Error |
[chars] |
Error initializing the ole WAVL tree |
ipmulticast |
LOG_STD_RECUR_ACTION |
|
PIM_PROT-4-MROUTELIMIT |
4-Warning |
Current count of [dec] exceeds multicast route-limit of [dec] |
The number of multicast routes equals the configured maximum allowed.\n\ New routes cannot be added unless the configuration is changed. |
- |
"If multicast traffic is of any priority among the traffic carried\n\ by this router then use the 'ipv6 multicast route-limit' command to\n\ increase the number of multicast routes.\n\ Otherwise no action is required." |
|
PIM_PROT-4-MROUTELIMIT_ATTEMPT |
4-Warning |
Attempt to exceed multicast route-limit of [dec] |
The number of multicast routes equals the configured maximum allowed.\n\ New routes cannot be added unless the configuration is changed. |
- |
"If multicast traffic is of any priority among the traffic carried\n\ by this router then use the 'ipv6 multicast route-limit' command to\n\ increase the number of multicast routes.\n\ Otherwise no action is required." |
|
PIM_PROT-4-MROUTELIMITWARNING |
4-Warning |
multicast route-limit warning curr [dec] threshold [dec] |
- |
- |
- |
|
PIM_PROT-4-PROTOCOL_WARNING |
4-Warning |
[chars] - [chars] [chars] : [chars] |
Internal protocol inconsistency warning |
ipmulticast |
LOG_STD_NO_ACTION |
|
PIM_PROT-4-SUSPEND_RESUME_INFO |
4-Warning |
Resumed the process/loop but found nothing to be done. |
A loop in PIM code was temporarily suspended to avoid hogging the CPU. When it was time to resume the loop the system found nothing to do so. Possible reasons for this are that a VRF was deleted or an interface was deleted while the loop was suspended. This message is for informational purposes only |
ipmulticast |
LOG_STD_NO_ACTION |
|
PIM_PROT-4-SUSPEND_RESUME_WARNING |
4-Warning |
Failed to resume suspended PIM context. |
A loop in PIM code was temporarily suspended to avoid hogging the CPU. When it was time to resume the loop the system was unable to do so. Possible reasons for this are that a VRF was deleted or an interface was deleted while the loop was suspended. |
ipmulticast |
LOG_STD_NO_ACTION |
|
PIM_PROT-6-IDB_ENABLE |
6-Information |
Interface [chars] does not support multicast not enabled |
PIM not enabled on an interface that does not support mcast |
ipmulticast |
LOG_STD_NO_ACTION |
|
PIM_REG_TUN-3-IDB_ROUTE_DISABLE |
3-Error |
Tunnel Groups: [chars]: [chars] |
The tunnel group component encountered an internal software error |
ip-tunnels |
LOG_STD_ACTION |
|
PIM_REG_TUN-3-NO_POLICY_MAP |
3-Error |
Lookup of rate-limit policymap failed for vrf [chars]. |
When the ip pim register-rate-limit CLI command is entered a rate-limiting policy-map is created. This policy-map is attached to each register tunnel by configuring an output service policy on the tunnel. A policy-map lookup is therefore performed whenever the register-rate-limit command is enabled or disabled. This message is logged as a result of a lookup failure. |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
PIM_REG_TUN-3-PRT_NULL_TINFO |
3-Error |
Register tunnel [chars] has null tinfo. |
Unable to dereference tunnel information. |
ipmulticast |
LOG_STD_DBG_ACTION |
|
PIM_REG_TUN-3-SERVICE_POLICY_FAILURE |
3-Error |
Failed to configure service policy on register tunnel. |
When the ip pim register-rate-limit CLI command is entered a rate-limiting policy-map is created. This policy-map is attached to each register tunnel by configuring an output service policy on the tunnel. This message is logged as a result of a failure to configure an output service policy on a register tunnel. This failure may be due to lack of temporary resources but it may also be caused by platform restrictions on overlapping QoS configurations such as simultaneously having a service policy on a tunnel and on the real interface associated with the tunnel. |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
PIM_REG_TUN-3-UNEXPECTED_TRANSPORT |
3-Error |
Unexpected tunnel transport: [dec]. |
An unexpected tunnel transport was detected. The location where the value was detected and the execution path that lead to it may be obtained from the traceback included in this message. |
ipmulticast |
LOG_STD_SH_TECH_ACTION |
|
PIM_REG_TUN-3-UNNUM_ERR |
3-Error |
Failed to set un-numbered interface for [chars] [chars] |
- |
- |
- |
|
PIM_REG_TUN-6-UNNUM_ERR_STBY |
6-Information |
Failed to set un-numbered interface for [chars] [chars] |
- |
- |
- |
|
PIM-1-INVALID_RP_REG |
1-Alert |
Received Register from router [inet] for group [inet] [inet] not willing to be RP |
A PIM router received a register message from another PIM router that\n thinks it is the rendezvous point. If the router is not configured for\n another rendezvous point it will not accept the register message. |
- |
"Configure all leaf routers first-hop routers to multicast sources\n" |
|
PIM-1-SR_INTERVAL_SETTING_ERR |
1-Alert |
Incompatible SR interval from [inet] on [chars] [dec] != [dec] |
- |
- |
- |
|
PIM-3-MVRF_NULL_PRM |
3-Error |
Null parameter specified for MVRF lookup. |
A function to perform an mvrf lookup by name detected a NULL input parameter. The intended action can not proceed. |
- |
LOG_STD_SH_TECH_ACTION |
|
PIM-3-PMTFINDSMRPINPRM |
3-Error |
Invalid parameter passed while walking the autorp cache to find a group-to-rp mapping for Sparse RP [inet]. parameter: 0x[hec] |
An invalid parameter was specified while walking the\n\ autorp cache to find a Sparse RP match. |
- |
LOG_STD_SH_TECH_ACTION |
|
PIM-3-PRT_ENTRY_HAS_NO_RP |
3-Error |
A request has been issued to remove a PIM register tunnel from multicast entry [chars] [inet] but this entry has no RP address. |
This condition is an indication that the entry's RP address was reset before first removing the register tunnel. This can cause a memory leak because the RP address is the key for looking up the tunnel whose removal has been requested. Without the RP we cannot find the tunnel and decrement its reference count. |
- |
LOG_STD_DBG_ACTION |
|
PIM-3-PRT_INVALID_MODE |
3-Error |
Invalid register tunnel mode [dec]. |
The only valid register tunnel mode values are TUN_MODE_PIM_ENC_IPV4 and TUN_MODE_PIM_DEC_IPV4. |
- |
LOG_STD_DBG_ACTION |
|
PIM-3-REGTUNIDBCREATE |
3-Error |
Tunnel IDB creation for a PIM register [chars] tunnel for RP [inet] failed for vrf [chars]. |
An attempt to create a tunnel IDB for use with a PIM register\n tunnel has failed. The encapsulation or decapsulation tunnel can\n not be created. |
- |
LOG_STD_SH_TECH_ACTION |
|
PIM-3-REGTUNIDBMVRF |
3-Error |
Failed to find the mvrf associated with IDB [chars] |
An attempt to determine the multicast vrf associated with the\n specified IDB failed. The required update of PIM register tunnel\n IDB information can not proceed. |
- |
LOG_STD_SH_TECH_ACTION |
|
PIM-3-REGTUNMDBFLG |
3-Error |
Register tunnel MDB client flag allocation failed. |
An attempt to allocate a client flag position for use in tracking the number of mroutes using each PIM register tunnel has failed. Register tunnels can be allocated but can not deleted. |
- |
LOG_STD_SH_TECH_ACTION |
|
PIM-3-REGTUNMISSING |
3-Error |
[chars] register tunnel entry for RP [inet] missing from tunnel list |
Deletion of a PIM register tunnel entry from a PIM register\n tunnel queue failed because the register tunnel entry wasn't found\n in the register tunnel list. |
- |
LOG_STD_SH_TECH_ACTION |
|
PIM-3-REGTUNMVRF |
3-Error |
NULL mvrf specified in PIM register tunnel creation request for RP [inet] |
An NULL mvrf was specified for creation of\n a PIM register tunnel associated with the specified RP.\n The register tunnel can not be created. |
- |
LOG_STD_SH_TECH_ACTION |
|
PIM-3-REGTUNNOIDB |
3-Error |
No register tunnel IDB found for RP [inet]. Can't execute pending delete |
During an attempt to delete a register tunnel interface that\n is currently in use for at least one mroute olist entry\n the register tunnel entry did not specify a tunnel interface.\n The register tunnel interface can not be deleted. |
- |
LOG_STD_SH_TECH_ACTION |
|
PIM-3-REGTUNPRQ |
3-Error |
Process enqueue for [chars] register tunnel creation failed for RP [inet]. |
An attempt to enqueue a request for PIM register tunnel IDB\n creation failed probably because of a lack of resources. The\n |
- |
LOG_STD_SH_TECH_ACTION |
|
PIM-3-REGTUNQLINK |
3-Error |
Corrupted PIM register [chars] tunnel queue links. Can't add RP [inet] |
Insertion of a new PIM register tunnel entry into a PIM register\n tunnel queue failed. The encapsulation or decapsulation tunnel can\n not be created. |
- |
LOG_STD_SH_TECH_ACTION |
|
PIM-3-REGTUNRP |
3-Error |
NULL RP pointer specified for PIM register tunnel creation. |
The caller passed a NULL pointer instead of providing a valid \n pointer to the RP cache entry for which register tunnel creation\n was requested. The encapsulation or decapsulation tunnel can not\n be created. |
- |
LOG_STD_SH_TECH_ACTION |
|
PIM-3-REGTUNRPMAPMVRF |
3-Error |
NULL mvrf specified in RP mapping notification for RP [inet] |
An NULL mvrf was specified when a PIM RP mapping notification\n\n\ was made. |
- |
LOG_STD_SH_TECH_ACTION |
|
PIM-3-REGTUNSETSRC |
3-Error |
Failed to set PIM [chars] register tunnel IDB source for RP [inet] |
An attempt to set the tunnel source address of a PIM register tunnel\n for the specified RP has failed. The encapsulation or decapsulation\n tunnel can not be created. |
- |
LOG_STD_SH_TECH_ACTION |
|
PIM-3-REGTUNUPMVRF |
3-Error |
NULL mvrf specified in PIM register tunnel entry for RP [inet] |
An NULL mvrf was specified for the PIM register tunnel associated \n\n\ with the specified RP.\n\n\ The register tunnel can not be used for registration. |
- |
LOG_STD_SH_TECH_ACTION |
|
PIM-3-RPDF_NULL_PRM |
3-Error |
Null parameter specified for Bidir RP DF creation. |
A function to create a Bidir RP DF entry detected a NULL input parameter. The RP DF entry can not be created. |
- |
LOG_STD_SH_TECH_ACTION |
|
PIM-3-RPNOREGTUN |
3-Error |
For multicast route [inet] [inet] no register tunnel found |
During an attempt to install a register tunnel interface for a\n new SG multicast route a search in the PIM register encapsulation\n tunnel list failed to find the tunnel entry for the corresponding\n RP. The register tunnel interface can not be added to the multicast\n route. |
- |
LOG_STD_SH_TECH_ACTION |
|
PIM-3-RPNOREGTUNIDB |
3-Error |
For multicast route [inet] [inet] no register tunnel IDB found |
During an attempt to install or uninstall a register tunnel \n interface for an SG multicast route the register tunnel entry for \n the corresponding RP did not specify a tunnel interface.\n The register tunnel interface can not be added to or removed from \n the multicast route. |
- |
LOG_STD_SH_TECH_ACTION |
|
PIM-3-SPURIOUS_MGD_TIMER_EXP_SRC_CHK |
3-Error |
Managed timer wakeup received by the PIM register tunnel creation process with no expired timers. |
The PIM register tunnel creation process received a wakeup for managed timer expiration but the API to obtain the first expired timer returned a NULL pointer. The timer expiration can not be handled. Possible loss of PIM register tunnel functionality including failure of PIM Sparse Mode registration for some multicast groups may occur as a result. |
- |
LOG_STD_SH_TECH_ACTION |
|
PIM-3-TWHEEL_INIT_ERR |
3-Error |
Unable to create PIM timer wheel |
An error occured intializing the PIM timer twheel |
- |
"An error in maintaining the PIM timer wheel occurred." LOG_STD_ACTION |
|
PIM-3-UNEXPECTED_CONDITION_SPMSI |
3-Error |
PIM [dec] A mismatch of the S-PMSI pointer %p/ %p cached in the mdb [inet]/% |
- |
- |
- |
|
PIM-3-UPD_RPR_NULL_PRM |
3-Error |
Null parameter specified for Bidir RP route update. |
A function to perform an update of Bidir RP route information detected a NULL input parameter. The update can not proceed. |
- |
LOG_STD_SH_TECH_ACTION |
|
PIM-4-DEPRECATED_HELLO_TLV |
4-Warning |
Deprecated PIM Hello Option TLV [dec] [chars] from [inet] [chars] |
- |
- |
- |
|
PIM-4-INVALID_RCV_RLOC |
4-Warning |
Invalid Receiver RLOC address family |
Invalid Receiver RLOC address family |
ipmulticast |
LOG_STD_NO_ACTION |
|
PIM-4-INVALID_SRC_REG |
4-Warning |
Received Register from [inet] for [inet] [inet] not willing to be RP |
- |
- |
- |
|
PIM-4-NO_INPUT |
4-Warning |
PIM packet without input interface received from [inet] for [inet] |
An unexpected PIM packet without input interface was received. |
ipmulticast |
"Consider taking note of source and destination present in syslog." LOG_STD_ACTION |
|
PIM-4-NOT_RECOMMENDED_DENSE_MODE |
4-Warning |
PIM Dense Mode is not recommended and needs to be replaced with PIM Sparse Mode |
PIM Dense Mode is not recommended and needs to be replaced with PIM Sparse\n Mode. |
- |
"Configure PIM Sparse Mode" |
|
PIM-4-PIM_INVALID_SB |
4-Warning |
Unexpected access to PIM interface subblock field |
IOS attempts to access the value of a PIM interface field\n\ whose interface subblock is not yet created |
- |
"An inconsistency accessing a PIM interface subblock occurred." LOG_STD_ACTION |
|
PIM-4-RCV_RLOC_ATTR_NOT_PRESENT |
4-Warning |
Receiver RLOC ATTR should be present for PIM J/P with LISP transport |
Receiver RLOC ATTR should be present for PIM J/P with LISP transport |
ipmulticast |
LOG_STD_NO_ACTION |
|
PIM-4-REGTUNNOSRC |
4-Warning |
Some register encap tunnels may not have routable source addresses. |
Repeated attempts to adjust register encap tunnel source were running over time and some tunnels may not have been adjusted. |
- |
LOG_STD_SH_TECH_ACTION |
|
PIM-4-RP_NOT_LOCAL |
4-Warning |
Received * [inet] Join from [inet] for invalid RP [inet]. SDWAN SPT-only is |
A downstream PIM router sent a join message for the shared tree with a rendezvous point IP which is not local. In SDWAN spt-only networks it is expected that the cEdge is the chosen RP. |
- |
"Make sure the cEdge is the chosen RP and If PIM BSR is running " "use appropriate BSR configurations to make cEdge as the elected RP if there" "is a contention." |
|
PIM-4-TRANSPORT_ATTR_NOT_PRESENT |
4-Warning |
Transport ATTR should be present for PIM J/P with LISP transport |
Transport ATTR should be present for PIM J/P with LISP transport. |
ipmulticast |
LOG_STD_NO_ACTION |
|
PIM-4-UNSUPPORTED_LISP_TRANSPORT |
4-Warning |
Unsupported LISP transport |
Unsupported LISP transport |
ipmulticast |
LOG_STD_NO_ACTION |
|
PIM-5-DRCHG |
5-Notice |
DR change from neighbor [inet] to [inet] on interface [chars] |
A PIM neighbor is the new DR on an interface |
- |
LOG_STD_NO_ACTION |
|
PIM-5-NBRCHG |
5-Notice |
neighbor [inet] [chars] on interface [chars] [chars] |
A PIM neighbor has gone UP or DOWN on an interface |
- |
LOG_STD_NO_ACTION |
|
PIM-5-PROXY |
5-Notice |
Deny proxy for [inet] [inet] from neighbor [inet] |
Deny PIM Proxy from neighbor |
- |
LOG_STD_NO_ACTION |
|
PIM-6-INVALID_RP_JOIN |
6-Information |
Received * [inet] Join from [inet] for invalid RP [inet] |
A downstream PIM router sent a join message for the shared tree which\n this router does not want to accept. This behavior indicates that this\n router will let only downstream routers join to a specific rendezvous\n point. |
- |
"Configure all downstream leaf routers to join to the RP that is\n" "allowed by upstream routers toward the validated rendezvous point." |
|
PIM-6-REGTUNNOTDEL |
6-Information |
Some register [chars] tunnels may not have been deleted. |
Maintanance activity to delete unused register tunnels was running over time and some tunnels may not have been deleted. |
- |
LOG_STD_SH_TECH_ACTION |
|
PIMP-2-NOMEM |
2-Critical |
No memory available for [chars] |
Process interrupt mask profiler subsystem could not obtain the memory it needed. |
os |
"Copy the message exactly as it appears and report it " "your technical support representative." |
|
PKI-1-CERT_EXPIRY_ALERT |
1-Alert |
[chars] Certificate belonging to trustpoint [chars] will expire in [dec] Days [dec] hours [dec] mins [dec] secs at [chars]. \n Issuer-name : [chars] \n Subject-name : [chars] \n Serial-number: [chars] \n Auto-Renewal : [chars] |
Alert to indicate that certificate will expire in less than one week. |
pki |
"If auto-enrol feature is not configured re-enrol the certificate " "manually. Else check if any issues with auto-enrol." |
|
PKI-2-CA_SERVER_CERT_EXPIRED |
2-Critical |
[chars] server ceritifcate expired. Cannot enable [chars] server |
CA server certificate expired. |
pki |
"Reconfigure CA server" |
|
PKI-2-CA_SERVER_LABEL_TOO_LONG |
2-Critical |
[chars] server name too long. Reconfigure server with name less than 13 characters. |
CA server name too long. |
pki |
"Reconfigure CA server with less than 13 characters" |
|
PKI-2-CA_SERVER_TP_NOT_PRESENT |
2-Critical |
[chars] server's Trustpoint not available. Check for the trustpoint config. |
CA server's Trustpoint not available. |
pki |
"Check for CA server and Trustpoint configuration presence" |
|
PKI-2-CERT_ENROLL_FAIL |
2-Critical |
Certificate enrollment failed for trustpoint [chars]. \n Reason : [chars] |
Certificate enroll encounter fatal error |
pki |
"Contact the CA administrator." |
|
PKI-2-CERT_RENEW_FAIL |
2-Critical |
Certificate renewal failed for trustpoint [chars] \n Reason : [chars] |
Certificate enroll encounter fatal error |
pki |
"Contact the CA administrator." |
|
PKI-2-CERT_SHADOW_INSTALL_FAIL |
2-Critical |
[chars]. |
Shadow CA/ID certificate installation failed. |
pki |
"Check for the reason for failure and perform necessary steps" |
|
PKI-2-CS_CERT_EXPIRED |
2-Critical |
Certificate server [chars] CA certificate expired. Regenerate CA certificate manaully. |
CS certificate expired. |
pki |
"Regenerate CS certificate." |
|
PKI-2-CS_CERT_GEN_FAIL |
2-Critical |
Certificate server [chars] CA certificate generation failed. Regenerate CA certificate manaully. |
Certificate Server disabled. |
pki |
"Regenerate CS certificate." |
|
PKI-2-CS_CERT_INVALID |
2-Critical |
Certificate server [chars] CA certificate invalid. Regenerate CA certificate manaully. |
CS certificate invalid. |
pki |
"Regenerate CS certificate." |
|
PKI-2-CS_CERT_NOT_PRESENT |
2-Critical |
Certificate server [chars]'s certificate not present. |
Certificate server certificate not present |
pki |
"Regenerate CS certificate." |
|
PKI-2-CS_ISSUER_NAME_INVALID |
2-Critical |
Invalid issuer_name in CS [chars] configuration |
Invalid issuer-name in Certificate Server |
pki |
"Check certificate server configuration and re-configure." |
|
PKI-2-CS_ROLLOVER_FAIL |
2-Critical |
CS Rollover failed. \n Reason : [chars] |
Rollover failed for certificate server |
pki |
"Critical error on rollover." "Certificate Server has to be re-enabled." |
|
PKI-2-CS_SUBJECT_NAME_FAIL |
2-Critical |
Extracting subject name from Server certificate failed |
Extraction of subject failed |
pki |
"Regenerate CS certificate." |
|
PKI-2-MEM_ALLOC_FAIL |
2-Critical |
Memory allocation failure. Number of bytes requested : [dec] |
Memory allocation failed |
pki |
"Check memory left on the device" |
|
PKI-2-NON_AUTHORITATIVE_CLOCK |
2-Critical |
PKI functions can not be initialized until an authoritative time source like NTP can be obtained. |
System clock is not valid. Update the system clock to start with PKI timers |
pki |
"System clock must be configured/Updated." |
|
PKI-2-NON_AUTHORITATIVE_CLOCK_CA |
2-Critical |
CA server cannot be enabled due to non-authoritative system clock. Configure clock/Sync with NTP server. |
System clock is not valid. Update the system clock to start CA server |
pki |
"System clock must be configured/Updated." |
|
PKI-2-PKI_EVENT_LOG |
2-Critical |
PKI Event : [chars] |
PKI Event for both success/failure. |
pki |
"Informational message only. No action needed." |
|
PKI-2-SERVER_KEY_NOT_PRESENT |
2-Critical |
Not able to find CS [chars]'s keypair label [chars]. Check whether keypair [chars] is available on device |
CA server's key-pair not available. |
pki |
"Check for key-pair presence" |
|
PKI-2-SERVER_TP_CREATE_FAIL |
2-Critical |
Not abel to create [chars] server's Trustpoint.Check for CA server config's. |
CA server's Trustpoint not created. |
pki |
"Check for CA server and Trustpoint configuration presence" |
|
PKI-3-AUTOCERTERR |
3-Error |
Auto Certificate reenrollment failed. Cannot retry |
Automatic certificate re-enrollment failed. The router clock my not be set correctly. If the router has a certificate it may be expired. |
pki |
"Check router clock is set correctly" "Make sure the router's cert has not expired" |
|
PKI-3-CERT_ROLLOVER |
3-Error |
Renew/Shadow event has failed for trustpoint : [chars] \n Reason : [chars] |
Renew/Shadow event failed. |
pki |
"Perform manual renewal of certificate to avoid certificate expiry." |
|
PKI-3-CERTIFICATE_INVALID |
3-Error |
Certificate chain validation has failed. |
The certificate is not valid |
pki |
"Check the system clock to see if its set correctly" |
|
PKI-3-CERTIFICATE_INVALID_EXPIRED |
3-Error |
Certificate chain validation has failed. The certificate SN: [chars] has expired. |
The certificate validity period indicates that this certificate has expired |
pki |
"Check the system clock to see if its set correctly" |
|
PKI-3-CERTIFICATE_INVALID_NOT_YET_VALID |
3-Error |
Certificate chain validation has failed. The certificate SN: [chars] is not yet valid |
The certificate validity period indicates that this certificate is not yet valid |
pki |
"Check the system clock to see if its set correctly" |
|
PKI-3-CERTIFICATE_INVALID_UNAUTHORIZED |
3-Error |
Certificate chain validation has failed. Unauthorized |
The certificate is valid but not authorized |
pki |
"Check the system clock to see if its set correctly" |
|
PKI-3-CERTIFICATE_REVOKED |
3-Error |
Certificate chain validation has failed. The certificate SN: [chars] is revoked |
The certificate has been revoked by the CA administrator. |
pki |
"Check the status contact the CA administrator" |
|
PKI-3-CERTPENDERR |
3-Error |
Failed to receive pending certificate during enrollment |
The router's cert remains in a pending state after the maximum number of retries to enroll. |
pki |
"Contact the CA administrator. Then retry the enrollment." |
|
PKI-3-CERTRETFAIL |
3-Error |
Certificate enrollment failed. |
Certificate enrollment transaction failed due to internal error. |
- |
"Contact CE." |
|
PKI-3-CRL_FETCH_FAIL |
3-Error |
CRL fetch for trustpoint [chars] failed \n Reason : [chars] |
The CRL fetch returned something other than success. |
pki |
"Check the CRL manually to see it is correct. " "To see interaction between IOS and the CRL-server " "please turn on <CmdBold>debug crypto pki " "transactions<NoCmdBold>" |
|
PKI-3-CRL_HTTP_FAIL |
3-Error |
CRL Request over http for trustpoint [chars] failed. \n Reason : [chars] |
Receival of CA certificate failed |
pki |
"CA cert download failed" |
|
PKI-3-CRL_INSERT_FAIL |
3-Error |
CRL download for trustpoint \[chars]\ has been discarded. \n Reason : [chars] \n Status : [dec] \n Status String : [chars] |
Inserting and/or verifying the CRL failed. If the trustpoint revocation-check includes the keyword 'none' the transaction will succeed. If revocation- checking is not optional the transaction will fail. |
pki |
"Check the CRL manually to see it is correct. " "To see interaction between IOS and the CRL-server " "please turn on <CmdBold>debug crypto pki " "transactions<NoCmdBold>" |
|
PKI-3-CS_CRIT_STORAGE |
3-Error |
Critical certificate server storage [chars] is inaccessible server disabled. |
Critical certificate server storage is inaccessible server disabled. |
- |
"Make storage accessible or re-configure the storage location" |
|
PKI-3-CS_ROLLOVER_TRIGGER |
3-Error |
CS Rollover event has been triggered for server [chars] |
Rollover triggerred for certificate server |
pki |
"Informational message only. No action needed." |
|
PKI-3-ENROLL_PKCS12 |
3-Error |
Trustpoint [chars] configured as pkcs12 enrollment. SCEP enrollment not supported |
Change the trustpoint configuration to point to enrollment-url |
pki |
"TP configuraiton need to be verified." |
|
PKI-3-GET_CERT_INITIAL |
3-Error |
Failed with GetCertInitial for trustpoint [chars] \n Reason : [chars] |
GetCertInitial encounter fatal error |
pki |
"Contact the CA administrator." |
|
PKI-3-GETCARACERT |
3-Error |
Failed to receive RA/CA certificates. |
Encountered failure when parsing and processing CA/RA certificates |
- |
"Check the status contact the CA administrator" |
|
PKI-3-HOSTNAME_RESOLVE_ERR |
3-Error |
Failed to resolve HOSTNAME/IPADDRESS : [chars] |
Unable to resolve hostname/ip-address |
pki |
"Check network connectivity" |
|
PKI-3-INVALID_INPUT |
3-Error |
The input to the parser command is not correct |
The input to the parser command is not correct |
- |
"Repeat the command." |
|
PKI-3-INVALIDCACERT |
3-Error |
Failed to process CA certificate. |
Failed to process the ca certificate received from ca server. |
pki |
"Use parser command "cr ca auth" and try again." |
|
PKI-3-ISSUER_NAME_NOT_BER |
3-Error |
Issuer name is not BER |
Issuer name is not BER. Check issuer-name |
pki |
"Check issuer-name present/configured" |
|
PKI-3-KEY_CMP_MISMATCH |
3-Error |
Key in the certificate and stored key does not match for Trustpoint-[chars]. |
Public key in the certificate is not the same as the stored key. |
- |
"Make sure that the certificate public key and stored public key are the same." |
|
PKI-3-MUTUALLY_EXCLUSIVE_CONFIG |
3-Error |
'grant auto tp <> and grant auto tp-list <> are mutually exclusive config. \n And cannot be configured at same time. Delete one and then \n configure another. |
CLI configuration failed |
- |
"Issue \"no grant auto tp-list\" command to configure "grant auto tp" Or " "Issue \"no grant auto trustpoint\" command to configure "grant auto tp-list."" |
|
PKI-3-OCSP_CONTENT_MISMATCH |
3-Error |
ocsp content mismatch |
Expected content not matched with formed content |
pki |
"Check ocsp request" |
|
PKI-3-OCSP_FETCH_FAIL |
3-Error |
OCSP fetch failed. \n Reason : [chars] |
OCSP Fetch failed |
pki |
"Enable socket/tcp debugs to check connectivity with ocsp server" |
|
PKI-3-OCSP_RESPONSE_FAIL |
3-Error |
OCSP response from [chars] has been discarded. \n Reason : [chars] |
OCSP response parse failed |
pki |
"Check OCSP response" |
|
PKI-3-OCSP_RESPONSE_STATUS |
3-Error |
OCSP response status failed \n Reason : [chars] |
OCSP response status failed |
pki |
" Check the ocsp request or ocsp server configurations " |
|
PKI-3-PKCS12_IMPORT_FAILURE |
3-Error |
PKCS #12 import failed for trustpoint: [chars]. Reason: [chars] |
A PKCS #12 import got failed |
c3pl |
"No action required. Informational message" |
|
PKI-3-POLLCACERT |
3-Error |
Polling CA certificate ..... |
Polling ca certificate. |
- |
"Check if CA or ldap server is online." |
|
PKI-3-POLLRACERT |
3-Error |
Polling RA certificate ..... |
Polling ra certificate. |
- |
"Check if CA or ldap server is online." |
|
PKI-3-POLLROUTERCERT |
3-Error |
Polling Router certificate for [chars] ..... |
Polling router certificate. |
- |
"Check if CA or ldap server is online." |
|
PKI-3-QUERY_KEY |
3-Error |
Querying key pair failed. |
Querying public key/private key using subject name failed |
- |
"Resubmit enrollment request. Check the subject name." |
|
PKI-3-QUERYCACERT |
3-Error |
Failed to query CA certificate. |
Failed to query ca certificate from ca server. |
- |
"Use parser command "cr ca auth" and try again." |
|
PKI-3-SET_SOCK_VRF_INTERFACE_FAIL |
3-Error |
Failed to set VRF : [chars] to socket interface |
Failed to set VRF to socket |
pki |
"Check configured VRF for trustpoint and set VRF" |
|
PKI-3-SET_SOCKET_OPTION_FAIL |
3-Error |
Failed to set socket option. Option : [chars] |
Failed to set socket option |
pki |
"Enable socket debugs" |
|
PKI-3-SET_SOURCE_INTERFACE_FAIL |
3-Error |
Failed to set source interface for [chars] ip address |
Failed to set source interface |
pki |
"Check configured source interface for trustpoint" |
|
PKI-3-SET_VRF_FAIL |
3-Error |
Failed to set VRF : [chars]. VRF not configured |
Failed to set VRF |
pki |
"Check configured VRF for trustpoint and set VRF" |
|
PKI-3-SOCKET_BIND_FAIL_SOURCE_INTERFACE |
3-Error |
Failed to bind the socket due to source interface ip : [chars] |
Failed to bind socket with source interface |
pki |
"Check configured source interface for trustpoint" |
|
PKI-3-SOCKET_CONNECT_FAIL |
3-Error |
Failed to connect to socket |
Failed to connect socket |
pki |
"Enable socket debugs" |
|
PKI-3-SOCKET_OPEN |
3-Error |
Failed to open socket. |
The failure is caused by socket open |
pki |
"Check tcp/socket debugging message" |
|
PKI-3-SOCKETSEND |
3-Error |
Failed to send out message to CA server. |
The failure is caused by http transaction. |
- |
"Check http connection to the CA server" |
|
PKI-3-SUBJECT_NAME_NOT_BER |
3-Error |
Subject name is not BER |
Subject name is not BER. Check subject-name |
pki |
"Check subject-name present/configured" |
|
PKI-3-UNUSABLE_KEY_USAGE |
3-Error |
Key-usage type '[chars]' for cert with serial number [chars] is not usable. |
The given key-usage type is not usable by IOS. If seen during an import operation this will likely cause the import to fail. Acceptable key-usage types should include Key-encipherment and/or digital-signature. Other key-usage types may be present but will be ignored. |
- |
"Recreate the certificate with Key-encipherment " "digital-signature or both." |
|
PKI-4-AUTOCERTFAILWARN |
4-Warning |
Certificate reenrollment failed. Delaying before retry |
Automatic certificate re-enrollment failed. The router will retry in 6 hours or less depending on the expiration time of the router's certificate. Caution - Router's Certificate may expire soon. |
pki |
"Contact the CA administrator. The router will retry." |
|
PKI-4-CERT_ENROLL_CANCEL |
4-Warning |
Enrollment cancelled for trustpoint : [chars] |
Certificate enroll cancelled by user |
pki |
"Contact the CA administrator." |
|
PKI-4-CERT_ENROLL_RETRY_FAIL |
4-Warning |
Certificate reenrollment has failed after [dec] attempts |
Automatic certificate re-enrollment failed. Caution - Router's Certificate may expire soon. |
pki |
"Contact the CA administrator. Enrollment failed." |
|
PKI-4-CERT_EXPIRY_WARNING |
4-Warning |
[chars] Certificate belonging to trustpoint [chars] will expire in [dec] Days [dec] hours [dec] mins [dec] secs at [chars]. \n Issuer-name : [chars] \n Subject-name : [chars] \n Serial-number: [chars] \n Auto-Renewal : [chars] |
Warning to indicate that certificate is expiring soon. |
pki |
"If auto-enrol feature is not configured re-enrol the certificate " "manually. Else check if any issues with auto-enrol." |
|
PKI-4-CERTIFICATE_INVALID_SUBJECT |
4-Warning |
Certificate has a missing or invalid subject name. |
The certificate subject name attribute must be present and not empty OR The certificate subject alt name extension must be present and include at least one entry. |
pki |
"Examine the offending certificate and re-issue it with a proper subject name." |
|
PKI-4-CRL_LDAP_QUERY |
4-Warning |
An attempt to retrieve the CRL from [chars] using LDAP has failed |
An LDAP query was made to acquire the certificate revocation list but the LDAP server did not respond with the requested information. This is a warning that only applies to the Distribution Point listed. It does not necessarily reflect the overall success or failure of CRL aquistion since a prior or subsequent retrival of the CRL may have succedeed. |
pki |
"Check that the LDAP server is reachable and online." "Verify that the CRL is at the requested location" |
|
PKI-4-CRLHTTPFETCHFAIL |
4-Warning |
CRL Request for trustpoint \[chars]\ returned [dec] [chars] |
The CRL fetch returned something other than success. If the trustpoint revocation-check includes the keyword 'none' the transaction will succeed. If revocation- checking is not optional the transaction will fail. |
pki |
"Verify that the CRL is at the location specified " "in the Certificate and that the server is " "operational. To see interaction between IOS and " "the CRL-server please turn on <CmdBold>debug " "crypto pki transactions<NoCmdBold>" |
|
PKI-4-CS_GRANT_AUTO_CACERT_FAILURE |
4-Warning |
A rollover request for a subordinate CA certificate cannot be auto granted. |
A rollover request for a subordinate CA certificate cannot be authorized and the configured auto grant policy will be ignored. This request will be added to the CS server request queue but will need to be manually granted |
pki |
"Insure that the peer's current sub CA cert is valid." |
|
PKI-4-CS_PUBLISH_STORAGE |
4-Warning |
Publish certificate server storage [chars] is inaccessible. |
Publish certificate server storage is inaccessible. |
- |
"Make storage accessible or re-configure the storage location" |
|
PKI-4-HTTPREDIRECT |
4-Warning |
Maximum Redirection limit of [dec] exceeded trying to retrieve URL [chars] |
While fetching a document via http there were too many redirections and the operation has aborted. If the trustpoint revocation-check includes the keyword 'none' the transaction will succeed. If revocation- checking is not optional the transaction will fail. |
pki |
"Verify that the CRL is at the location specified " "in the Certificate and that the server is " "operational. To see interaction between IOS and " "the CRL-server please turn on <CmdBold>debug " "crypto pki transactions<NoCmdBold>" |
|
PKI-4-NOAUTOSAVE |
4-Warning |
Configuration was modified. Issue \write memory\ to save new certificate |
Auto-Enroll has obtained a new router key pair and certificate. However the running configuration was previously modified. |
- |
"Issue the \"write memory\" command to save the new certificates and keys." |
|
PKI-4-NOCONFIGAUTOSAVE |
4-Warning |
Configuration was modified. Issue \write memory\ to save new IOS PKI configuration |
IOS PKI APIs have generated new PKI configuration. However the running configuration was previously modified. |
- |
"Issue the \"write memory\" command to save the new PKI configuration." |
|
PKI-4-NOSHADOWAUTOSAVE |
4-Warning |
Configuration was modified. Issue \write memory\ to save new IOS CA certificate |
IOS CA Rollover has generated a shadow CA key pair and certificate. However the running configuration was previously modified. |
- |
"Issue the \"write memory\" command to save the new certificates and keys." |
|
PKI-4-OCSP_SERVER_CERT_VALIDATE |
4-Warning |
The OCSP Server [chars]: responder certificate validation failed |
The OCSP server responder certificate validation failed |
pki |
"Check if the configured OCSP server responder certificate" |
|
PKI-4-OCSP_SERVER_NO_RESP |
4-Warning |
The OCSP Server URL [chars] is not reachable or not responding |
The OCSP server is not reachable or is not responding to the OCSP request |
pki |
"Check if the OCSP server is reachable and is receiving the OCSP request" |
|
PKI-4-OCSP_SERVER_RESP_COMP |
4-Warning |
The OCSP Server [chars]: error:responder certificate is peer certificate |
The OCSP responder certificate is peer certificate |
pki |
"Check if the configured OCSP server and responder OCSP server is same or not" |
|
PKI-4-OCSP_SERVER_RESP_DECODE |
4-Warning |
The OCSP Server [chars]: failed to decode OCSP response data |
The OCSP response data decoding is failing |
pki |
"Check if the configured OCSP server response data" |
|
PKI-4-OCSP_SERVER_RESP_DECODE_FAIL |
4-Warning |
The OCSP Server [chars]: failed to decode OCSP response basic data |
The OCSP response data decoding is failing |
pki |
"Check if the configured OCSP server response data" |
|
PKI-4-OCSP_SERVER_RESP_SIGN |
4-Warning |
The OCSP Server [chars]: error:responder invalid signature algorithm |
The OCSP responder has differnt signature algorithm |
pki |
"Check if the configured and responder OCSP server ""same signature algorithm or not" |
|
PKI-4-OCSP_SERVER_RESP_VARIFY |
4-Warning |
The OCSP Server [chars]: failed to verify OCSP response |
The OCSP response verification failed |
pki |
"Check if the configured OCSP server response" |
|
PKI-4-ROUTER_CERT_EXPIRED |
4-Warning |
Router certificate expired cannot re-enroll/retry for enrollment/re-enroll |
Cannot re-enroll/retry for enroll/re-enroll. Caution - Router's Certificate has expired. |
pki |
"Enroll the router manually." |
|
PKI-4-TRUSTPOOL_AUTO_UPDATE_DISABLED |
4-Warning |
Auto-trustpool update is disabled. |
One of the certificates in the trustpool will expire soon. An attmpt to download a new trustpool bundle cannot be attempted since a bundle location is not configured |
pki |
"Either configure the bundle location in the trustpool policy or manually update the " "trustpool bundle." |
|
PKI-4-TRUSTPOOL_CERTIFICATE_SAVE_CHANGE |
4-Warning |
Downloaded Trustpool certificates present prior to image upgrade should be re-downloaded. Issue 'crypto pki trustpool import url <url>' to re-download the certificates. |
Downloaded Trustpool certificates present prior to image upgrade should be re-downlaoded |
pki |
"Before image upgrade clean all the downloaded trustpool certificates. Import them again after image upgrade." |
|
PKI-4-TRUSTPOOL_DOWNLOAD_FAIL |
4-Warning |
Trustpool download requires %llu bytes available free storage %llu bytes is insufficient |
Trustpool download failed Free space in nvram is not sufficient to store Trustpool Certificates. Change the Trustpool policy for its storage |
pki |
"Change the storage policy for Trustpool" |
|
PKI-4-TRUSTPOOL_DOWNLOAD_FAILURE |
4-Warning |
Trustpool Download failed |
Failed to download the trustpool bundle |
pki |
"Enable debugs and obtain the reason for failure" |
|
PKI-4-TRUSTPOOL_EXPIRATION_WARNING |
4-Warning |
The Trustpool will expire in [chars]. |
One of the certificates in the trustpool will expire soon. If a bundle location is configured an auto aupdate will be attempted at predetermined intervals. |
pki |
"If a bundle location is configured in the trustpool policy no further action is required. Otherwise" "manual update of trustpool bundle may be needed." |
|
PKI-5-CERT_ENROLL_RETRY |
5-Notice |
Certificate reenrollment has failed and retry will happen for [dec] attempts |
Automatic certificate re-enrollment failed. We are printing a consolidated message for the maximum number of retry attempts. The router will continue to retry depending on the expiration time of the router's certificate. The retry attempts will be either 999 default or as specified |
pki |
"Contact the CA administrator. The router will retry." |
|
PKI-6-AUTHORITATIVE_CLOCK |
6-Information |
The system clock has been set. |
System clock is valid. |
pki |
"No action. Informational message." |
|
PKI-6-AUTOCERTFAIL |
6-Information |
Certificate reenrollment failed. Delaying before retry |
Automatic certificate enrollment or re-enrollment failed The router will retry in 6 hours or less depending on the expiration time of the router's certificate. |
pki |
"Contact the CA administrator." |
|
PKI-6-AUTOENROLL_KEY_LOCKED |
6-Information |
Auto-enroll failed - RSA keypair is locked |
Auto-enroll attempted to generate a new RSA keypair. However the existing RSA keypair is locked so auto-enroll cannot proceed |
- |
"Auto-enroll will retry the enrollment request" "Make sure the existing RSA keypair is unlocked before the next retry" |
|
PKI-6-AUTOSAVE |
6-Information |
Running configuration saved to NVRAM |
Auto-Enroll has obtained a new router key pair and certificate and has done an automatic \write memory\ to save them. |
- |
"No action required. Informational message" |
|
PKI-6-CERT_ENROLL_AUTO |
6-Information |
Auto initial enrollment for trustpoint [chars] |
Trustpoint enrollment happening automatically. |
pki |
"No action required. Informational message" |
|
PKI-6-CERT_ENROLL_MANUAL |
6-Information |
Manual enrollment for trustpoint [chars] |
Trustpoint enrollment triggerred manaully |
pki |
"No action required. Informational message" |
|
PKI-6-CERT_INSTALL |
6-Information |
[chars] \n Trustpoint : [chars] \n Issuer-name : [chars] \n Subject-name : [chars] \n Serial-number: [chars] \n End-date : [chars] |
A previous certificate enrollment request was received by the Certificate Authority. It has issued the certificate and sent back a copy |
pki |
"Informational message only. No action required." |
|
PKI-6-CERT_REENROLL |
6-Information |
Re-enrollment for trustpoint [chars] |
Trustpoint re-enrollment triggerred manaully |
pki |
"No action required. Informational message" |
|
PKI-6-CERT_RENEW_AUTO |
6-Information |
Auto renewing router certificate of trustpoint [chars] |
Trustpoint certificate will expire soon and is being automatically renewed |
- |
"No action required. Informational message" |
|
PKI-6-CERT_ROLLOVER_ACTIVE |
6-Information |
A rollover ID certificate has been activated under trustpoint [chars] replacing the previous ID certificate. \n Issuer-name : [chars] \n Subject-name : [chars] \n Serial-number: [chars] \n End-date : [chars] |
Rollover ID certificate active |
pki |
"No action needed. Informational mesage only" |
|
PKI-6-CERT_SHADOW_ACTIVE |
6-Information |
[chars] \n Issuer-name : [chars] \n Subject-name : [chars] \n Serial-number: [chars] \n End-date : [chars] |
Shadow CA/ID certificate has been activated. |
pki |
"No action needed. Informational mesage only" |
|
PKI-6-CERT_SHADOW_INSTALL |
6-Information |
[chars] \n Issuer-name : [chars] \n Subject-name : [chars] \n Serial-number: [chars] \n End-date : [chars] |
Shadow CA/ID certificate has been installed. |
pki |
"No action needed. Informational mesage only" |
|
PKI-6-CERTIFSRECV |
6-Information |
Could not receive router's Certificate from file system. |
The router's certificate could not be received from file system. |
pki |
"Verify the enrollment URL and that the router is able to" "read from the file system." |
|
PKI-6-CERTIFSSEND |
6-Information |
Could not send Certificate enrollment request to file system. |
The certificate enrollment request could not be sent to file system. |
pki |
"Verify the enrollment URL and that the router is able to" "write to the file system." |
|
PKI-6-CERTPENDING |
6-Information |
Enter manual authentication ... |
CA server want to manually authenticate the router. |
- |
"Follow a manual authentication procedure." |
|
PKI-6-CERTREJECT |
6-Information |
[chars] |
A previous certificate enrollment request was received by the Certificate Authority. It has rejected the enrollment request. |
pki |
"Contact the Certificate Authority administrator." |
|
PKI-6-CERTRENEWMANUAL |
6-Information |
Please renew the router certificate for trustpoint [chars] |
Trustpoint certificate will expire soon and should be renewed |
- |
"Obtain a new certificate from the Certificate Authority" |
|
PKI-6-CONFIGAUTOSAVE |
6-Information |
Running configuration saved to NVRAM |
IOS PKI APIs have generated new PKI configuration and has done an automatic \write memory\ to save them. |
- |
"No action required. Informational message" |
|
PKI-6-CRLHTTPFETCHREDIR |
6-Information |
CRL Request for trustpoint \[chars]\ returned [dec] [chars] -> [chars] |
The CRL fetch returned a redirect directive. This need not be an error if the file exists at the redirected location. |
pki |
"If no other errors are seen then the CRL was " "fetched from the new location and no action is " "necessary. To see interaction between IOS and " "the CRL-server please turn on <CmdBold>debug " "crypto pki transactions<NoCmdBold>" |
|
PKI-6-CS_DELETE |
6-Information |
Certificate Server is deleted. |
Certificate Server is deleted. |
- |
"No action required. Informational message." |
|
PKI-6-CS_DELETE_TP_KEY |
6-Information |
Trustpoint and key deleted. |
Trustpoint and key used by the Certificate Server are deleted. |
- |
"No action required. Informational message." |
|
PKI-6-CS_DISABLED |
6-Information |
Certificate server now disabled. \n Reason : [chars] |
Certificate server now disabled. |
- |
"No action required. Informational message." |
|
PKI-6-CS_ENABLED |
6-Information |
Certificate server now enabled. |
Certificate server now enabled. |
- |
"No action required. Informational message." |
|
PKI-6-CS_GRANT_AUTO |
6-Information |
All enrollment requests will be automatically granted. |
All enrollment requests will be automatically granted. |
- |
"No action required. Informational message." |
|
PKI-6-CS_GRANT_AUTO_CACERT |
6-Information |
All rollover subordinate CA cert requests will be automatically granted. |
All rollover subordinate CA cert requests will be automatically granted. |
- |
"No action required. Informational message." |
|
PKI-6-CS_GRANT_AUTO_RA |
6-Information |
Enrollment requests coming from known RAs will be automatically granted. |
Enrollment requests coming from known RAs will be automatically granted. |
- |
"No action required. Informational message." |
|
PKI-6-CS_GRANT_AUTO_RACERT |
6-Information |
All rollover RA cert requests will be automatically granted. |
All rollover RA cert requests will be automatically granted. |
- |
"No action required. Informational message." |
|
PKI-6-CS_REJECT_AUTO |
6-Information |
All enrollment requests will be automatically rejected. |
All enrollment requests will be automatically rejected. |
- |
"No action required. Informational message." |
|
PKI-6-CS_ROLLOVER_ACTIVE |
6-Information |
[chars] Rollover certificate has been activated for [chars] replacing the previous [Sub/RA]CA certificate \n Issuer-name : [chars] \n Subject-name : [chars] \n Serial-number: [chars] \n End-date : [chars] |
Rollover certificate activated |
pki |
"Informational message only. No action needed." |
|
PKI-6-CS_ROLLOVER_AVAILABLE |
6-Information |
[Sub/RA]CS Rollover certificate has been generated for [chars] and it will be activated at [chars] \n Issuer-name : [chars] \n Subject-name : [chars] \n Serial-number: [chars] \n End-date : [chars] |
Rollover certificate generated |
pki |
"Informational message only. No action needed." |
|
PKI-6-CSR_FINGERPRINT |
6-Information |
\n CSR Fingerprint MD5 : [chars] \n CSR Fingerprint SHA1: [chars] |
Fingerprint display |
pki |
"Information message" |
|
PKI-6-ECDSA_CERT_WITH_SHA1 |
6-Information |
User has accepted the security implication of using lesser hash strengthSHA1 for the Elliptic Curve Key present in the certificate |
The SHA1 hash algorithm is not recommended for use with the elliptic curve key in this certificate. It is recommended that SHA2 or stronger hash algorithm be used. |
pki |
"Informational message only. No action required." |
|
PKI-6-OCSP_SUCCESS |
6-Information |
OCSP response from [chars] has been successfully processed for \n certificate : [chars] \n Serial-number: [chars] \n Result : [chars] |
OCSP response successfully processed. |
pki |
"Informational message only. No action needed." |
|
PKI-6-PKCS12_EXPORT_SUCCESS |
6-Information |
PKCS #12 Export from trustpoint [chars] was successfully Exported. |
A PKCS #12 has been generated and successfully exported. |
- |
"No action required. Informational message" |
|
PKI-6-PKCS12_IMPORT_SUCCESS |
6-Information |
PKCS #12 import in to trustpoint [chars] successfully imported. |
A PKCS #12 has been successfully imported. |
- |
"No action required. Informational message" |
|
PKI-6-PKI_CRL_DOWNLOADED |
6-Information |
CRL download successful. \n Trustpoint : [chars] \n CDP-URL : [chars] \n Issuer : [chars] |
CRL is downloaded and successfully inserted in the database. Notification for the same is sent to applications registered. |
pki |
"Informational message only. No action required." |
|
PKI-6-SHADOWAUTOSAVE |
6-Information |
Running configuration saved to NVRAM |
IOS CA Rollover has generated a shadow CA key pair and certificate and has done an automatic \write memory\ to save them. |
- |
"No action required. Informational message" |
|
PKI-6-SLA_TRUSTPOINT_CHANGE |
6-Information |
Attempting to override SLA Trustpoint. \n The current running SLA trustpoint config will be retained \n Config-Replace errors corresponding to SLA TrustPoint may be \n ingored. |
PKI Event for both success/failure. |
pki |
"Informational message only. No action needed." |
|
PKI-6-TRUSTPOINT_CREATE |
6-Information |
Trustpoint: [chars] created succesfully |
Trustpoint creation is successful |
pki |
"No action required. Informational message" |
|
PKI-6-TRUSTPOINT_DELETE |
6-Information |
Trustpoint: [chars] deleted succesfully |
Trustpoint deletion is successful |
pki |
"No action required. Informational message" |
|
PKI-6-TRUSTPOOL_AUTO_UPDATE |
6-Information |
Auto-trustpool update in progress from [chars]. |
One of the certificates in the trustpool will expire soon. An attmpt to download a new trustpool bundle is in progress |
pki |
"Since an url has been configured that identifies the location to aquire the trustpool bundle " "then no action is required." |
|
PKI-6-TRUSTPOOL_DOWNLOAD_SUCCESS |
6-Information |
Trustpool Download is successful |
Trustpool Download is successful |
pki |
"No action required. Informational message" |
|
PKT_MANIP-3-ALLOC_FAIL |
3-Error |
retcode [dec] |
A critical failure occurred when trying to obtain packet memory |
cpp-ucode |
LOG_STD_ACTION |
|
PKTLOG-1-PROXY_MEM_APPEND_ERR |
1-Alert |
[dec] [dec] [dec] |
An invalid memory chunk magic was detected in a memory chunk element |
cpp-ucode |
LOG_STD_ACTION |
|
PKTLOG-1-PROXY_MEM_RET_ERR |
1-Alert |
[chars] [dec] [dec] [dec] |
IPC failed and could not return memory |
cpp-ucode |
LOG_STD_ACTION |
|
PKTLOG-2-PROXY_IPC_SET_FAILED |
2-Critical |
[chars] |
Packet logger proxy IPC handler could not be initialized. |
cpp-ucode |
LOG_STD_ACTION |
|
PKTLOG-3-PKTLOG_IPC_SEND_FAILED |
3-Error |
[chars] [chars] |
Transmission of an IPC message by the packet logger failed. ACL and stats lost. |
cpp-ucode |
LOG_STD_ACTION |
|
PKTLOG-3-PROXY_BAD_SUBTYPE |
3-Error |
[dec] |
Invalid subtype was passed to packet logger proxy IPC handler. |
cpp-ucode |
LOG_STD_ACTION |
|
PKTLOG-3-PROXY_IPC_ALLOC_FAILED |
3-Error |
[chars] |
Allocation of an IPC packet buffer by the packet logger proxy failed. |
cpp-ucode |
LOG_STD_ACTION |
|
PKTLOG-3-PROXY_IPC_SEND_FAILED |
3-Error |
[chars] [chars] |
Transmission of an IPC message by the packet logger proxy failed. |
cpp-ucode |
LOG_STD_ACTION |
|
PKTLOG-4-PKTLOG_IPC_ALLOC_FAILED |
4-Warning |
[chars] |
Allocation of an IPC packet buffer by the packet logger failed. |
cpp-ucode |
LOG_STD_ACTION |
|
PKTLOG-4-PROXY_DUP_INIT |
4-Warning |
[chars] |
Duplicate initialization IPC message received for user [dec] client id [dec]. |
cpp-ucode |
LOG_STD_ACTION |
|
PKTLOG-4-PROXY_INVALID_USER_IDX |
4-Warning |
[dec] [dec] |
IPC message contained invalid user index for client id. |
cpp-ucode |
LOG_STD_ACTION |
|
PKTLOG-4-PROXY_IPC_INVALID_MSG_LEN |
4-Warning |
[dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Invalid IPC message length. |
cpp-ucode |
LOG_STD_ACTION |
|
PLATFORM_ACT2-2-SUDI_VALIDATION_FAILED |
2-Critical |
Secure UDI validation failed. [chars] |
Secure UDI validation for the chassis failed. The router failed to authenticate itself |
iosxe-chassismgr |
LOG_STD_ACTION |
|
PLATFORM_BRKOUT-3-BRKOUTCMD_SYNCFAILED |
3-Error |
Failed to send Breakout command to hardware. |
A messages that was sent to the hardware module was not delivered correctly. The failure most likely occurred because of incorrect switch number or non-existing breakout port number specified or a software communication error. |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
PLATFORM_CAPABILITY-4-CALL |
4-Warning |
Fatal Initialization Error - [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
PLATFORM_CAPABILITY-4-INIT |
4-Warning |
Fatal Initialization Error - [chars] |
An internal software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
PLATFORM_CAT2950-3-ASIC_BIST_FAILURE |
3-Error |
\n C2950 BIST failed for memory [chars] count [dec]\n |
During the Power-On Self Test the Built-In memory test on the internal chip memories has failed. This could be due to an ASIC defect. |
- |
LOG_STD_ACTION |
|
PLATFORM_CAT2950-3-ASIC_INIT_FAILURE |
3-Error |
\nAsic driver initialization has failed\n |
One of the ASIC initialization steps has failed. This could be a failure in the PCI configuration setup I2C initialization Build-in self test on the internal chip memories or other miscellaneous initialization steps due to a hardware defect. |
- |
LOG_STD_ACTION |
|
PLATFORM_CAT2950-3-GBP_FAILURE |
3-Error |
\n Unable to initialize the external packet memory \n |
During the switch driver initialization there was an error in the external packet memory initialization. This could be a defect in the ASIC or in the external SDRAM. |
- |
LOG_STD_ACTION |
|
PLATFORM_CAT2950-3-GBP_INIT_FAILURE |
3-Error |
\n GBP currently FULL or UNAVAILABLE. |
During the switch driver initialization an error has been detected in the external packet memory. This could be a defect in the ASIC or in the external SDRAM. |
- |
LOG_STD_ACTION |
|
PLATFORM_CAT2950-3-MEM_COPY_FAILURE |
3-Error |
\n Invalid copy [dec] for table [chars]\n |
This message means that there was an attempt to read or write an invalid copy of the switch internal memory. This is a recoverable error but should not happen. |
- |
LOG_STD_RECUR_ACTION |
|
PLATFORM_CAT2950-3-MEM_INDEX_FAILURE |
3-Error |
\n Invalid index [dec] for table [chars]\n |
This message means that there was an attempt to access an invalid index of the switch internal memory. This is a recoverable error but should not happen. |
- |
LOG_STD_RECUR_ACTION |
|
PLATFORM_CAT2950-3-MEM_INIT_FAILURE |
3-Error |
\n The switch memory resources could not be allocated for [chars] initialization failed |
During the switch driver initialization driver-related memory resources could not be allocated. This could be a hardware defect. |
- |
LOG_STD_ACTION |
|
PLATFORM_CAT2950-3-MEM_READ_FAILURE |
3-Error |
\n Read memory failed for memory [chars] at index [dec]\n |
An attempt to read a valid location in the internal chip memory was failed. This could be due to a hardware defect. |
- |
LOG_STD_RECUR_ACTION |
|
PLATFORM_CAT2950-3-MEM_WRITE_FAILURE |
3-Error |
\n Write memory failed for memory [chars] at index [dec]\n |
An attempt to write to a location in the internal chip memory was failed. This might be cause by writing to a invalid memory location or a defect in the hardware. |
- |
LOG_STD_RECUR_ACTION |
|
PLATFORM_CAT2950-3-MIIM_OP_FAILURE |
3-Error |
\n Unable to read PHY register at addr [hec] for phy id [hec]\n |
This message means that there was a failure to read from or write to a PHY register on the switch. This could be caused by a defect in the MII/GMII interface of the switch. |
- |
LOG_STD_RECUR_ACTION |
|
PLATFORM_CAT2950-3-PCI_FIND_FAILURE |
3-Error |
\n The number of asics expected were [dec] PCI bus scan found [dec]\n |
During the switch driver initialization incorrect number of ASICs were found on the PCI bus or no ASICs with a correct PCI value was found. This could be caused by a system PCI bus defect or incompatible software version running on the switch. |
- |
LOG_STD_ACTION |
|
PLATFORM_CAT2950-3-PCI_INIT_FAILURE |
3-Error |
\n The PCI address space initialization failed |
During the switch driver initialization the PCI address space for the ASIC could not be initialized. This could be a system PCI-bus-related issue. |
- |
LOG_STD_ACTION |
|
PLATFORM_CAT2950-3-PCI_TEST_FAILURE |
3-Error |
\nPCI address space test failedWrote 0x[hec] read 0x[hec] re-read 0x[hec]\n |
During the Power-On Self Test it is found that the PCI address space for the ASIC has not been mapped correctly. This could be a system PCI-bus-related issue. |
- |
LOG_STD_ACTION |
|
PLATFORM_CAT2950-3-REG_READ_FAILURE |
3-Error |
\n Register read failed for register [chars] in [chars]\n |
An attempt to read a valid location in the internal chip register failed. This could be due to a hardware defect. |
- |
LOG_STD_RECUR_ACTION |
|
PLATFORM_CAT2950-3-REG_WRITE_FAILURE |
3-Error |
\n Register write failed for register [chars] in [chars]\n |
An attempt to write to a location in the internal chip register failed. This might be cause by writing to a invalid register location or a defect in the hardware. |
- |
LOG_STD_RECUR_ACTION |
|
PLATFORM_CAT2950-3-SCHAN_OP_FAILURE |
3-Error |
\n S-channel operation timeout for opcode [chars]\n |
This message means that there was a failure to read or write to an ASIC register or a memory location because of an ASIC internal bus failure. |
- |
LOG_STD_RECUR_ACTION |
|
PLATFORM_CAT2950-3-SCHAN_READ_REG_FAILURE |
3-Error |
\n S-channel operation read register failure at addr [hec]\n |
This message means that there was a failure to read a ASIC register which might be caused by an invalid register address or an internal bus failure. |
- |
LOG_STD_RECUR_ACTION |
|
PLATFORM_CAT2950-3-SYSTEM_INFO_FAILURE |
3-Error |
\n The board information could not be read correctlyinitialization failed |
During switch driver initialization there was a failure to read the system board information. This could be a hardware problem. |
- |
LOG_STD_ACTION |
|
PLATFORM_CATALYST2955-3-PORT_NOT_OPERATING |
3-Error |
[chars] [chars] [chars] [chars] |
The port is not operating the startup selftest has failed |
- |
LOG_STD_ACTION |
|
PLATFORM_ENV-1-DUAL_PWR |
1-Alert |
Faulty internal power supply [chars] detected |
Faulty internal power supply detected in two power supplies supported platforms |
firmware |
LOG_STD_ACTION |
|
PLATFORM_ENV-1-EXTERNAL_ALARM_CONTACT_ASSERT |
1-Alert |
Alarm asserted: [chars] |
Error condition detected on external alarm contact |
hardware |
LOG_STD_ACTION |
|
PLATFORM_ENV-1-EXTERNAL_ALARM_CONTACT_ASSERT |
1-Alert |
Alarm asserted: [chars] |
Error condition detected on external alarm contact |
hardware |
LOG_STD_ACTION |
|
PLATFORM_ENV-1-EXTERNAL_ALARM_CONTACT_ASSERT |
1-Alert |
Alarm asserted: [chars] |
Error condition detected on external alarm contact |
hardware |
LOG_STD_ACTION |
|
PLATFORM_ENV-1-EXTERNAL_ALARM_CONTACT_CLEAR |
1-Alert |
Alarm cleared: [chars] |
Error condition cleared on external alarm contact |
hardware |
LOG_STD_ACTION |
|
PLATFORM_ENV-1-EXTERNAL_ALARM_CONTACT_CLEAR |
1-Alert |
Alarm cleared: [chars] |
Error condition cleared on external alarm contact |
hardware |
LOG_STD_ACTION |
|
PLATFORM_ENV-1-EXTERNAL_ALARM_CONTACT_CLEAR |
1-Alert |
Alarm cleared: [chars] |
Error condition cleared on external alarm contact |
hardware |
LOG_STD_ACTION |
|
PLATFORM_ENV-1-FAN |
1-Alert |
Faulty fan[chars] detected |
Faulty fan detected |
firmware |
"If the fault persists replace the fan." |
|
PLATFORM_ENV-1-FAN_NOT_PRESENT |
1-Alert |
Fan is not present |
Fan is not present |
firmware |
"If it is a removable fan insert it back into the " "switch. If fault persists after insertion replace the fan" |
|
PLATFORM_ENV-1-FRU_FAN_OK |
1-Alert |
FRU[chars] fan ok |
FRU fan working ok |
hardware |
LOG_STD_NO_ACTION |
|
PLATFORM_ENV-1-FRU_PS_ACCESS |
1-Alert |
[chars] |
Switch failed to access power supply due to communication problem |
firmware |
"This problem could be transient. If fault " "persists replace the power supply" |
|
PLATFORM_ENV-1-FRU_PS_FAN_FAILED |
1-Alert |
Faulty PS[chars] fan detected |
Power supply fan failure detected |
hardware |
"Replace the faulty fan" |
|
PLATFORM_ENV-1-FRU_PS_FAN_OK |
1-Alert |
PS[chars] fan ok |
Power supply fan working ok |
hardware |
LOG_STD_NO_ACTION |
|
PLATFORM_ENV-1-FRU_PS_OK |
1-Alert |
power supply [dec] is good |
No faults detected on power supply |
hardware |
LOG_STD_NO_ACTION |
|
PLATFORM_ENV-1-FRU_PS_SIGNAL_FAULTY |
1-Alert |
[chars] signal on power supply [dec] is faulty |
The specified signal of power supply is faulty |
hardware |
LOG_STD_ACTION |
|
PLATFORM_ENV-1-FRU_PS_SIGNAL_OK |
1-Alert |
[chars] signal on power supply [dec] is restored |
The specified signal of power supply has been restored |
hardware |
LOG_STD_NO_ACTION |
|
PLATFORM_ENV-1-PLATFORM_FAN_CRITICAL |
1-Alert |
[chars] |
Faulty fansFRU fan or PS fan detected |
hardware |
"Replace the faulty fans and then turn on the system" |
|
PLATFORM_ENV-1-PS_NONPOE |
1-Alert |
Internal Power supply not adequate for inline power |
Internal Power supply not adequate for inline power |
firmware |
"Procure a power supply that can provide adequate" "inline power" |
|
PLATFORM_ENV-1-PWR |
1-Alert |
Internal power supply not supplying power |
Internal power supply is not supplying power because either the cable is removed or the power supply is faulty |
firmware |
"Check the power supply cables and the power " "source. " LOG_STD_RECUR_ACTION |
|
PLATFORM_ENV-1-PWR_RPS |
1-Alert |
Redundant power supply faulty or in standby mode |
Redundant power supply is either faulty or it is in standby mode |
firmware |
"Move the redundant power supply out of standby" " mode and check the cables. Refer to the RPS " "User's Guide for the steps. " LOG_STD_RECUR_ACTION |
|
PLATFORM_ENV-1-RPS_ACCESS |
1-Alert |
[chars] |
RPS communication error detected |
firmware |
LOG_STD_ACTION |
|
PLATFORM_ENV-1-RPS_ACCESS |
1-Alert |
[chars] |
RPS communication error detected |
firmware |
LOG_STD_ACTION |
|
PLATFORM_ENV-1-RPS_BACKING_OFF_INFO |
1-Alert |
[chars] [dec] |
This event indicates RPS is backoff power from port |
hardware |
LOG_STD_ACTION |
|
PLATFORM_ENV-1-RPS_BACKING_UP_INFO |
1-Alert |
[chars] [dec] |
This event indicates RPS is backing up power to port |
hardware |
LOG_STD_ACTION |
|
PLATFORM_ENV-1-RPS_FAN_FAILED |
1-Alert |
[chars] |
RPS fan failure detected |
hardware |
"Disconnect any switches connected to the RPS and " "replace the fan immediately" |
|
PLATFORM_ENV-1-RPS_FAN_FAILED |
1-Alert |
[chars] |
RPS fan failure detected |
hardware |
"Disconnect any switches connected to the RPS and " "replace the fan immediately" |
|
PLATFORM_ENV-1-RPS_OVER_CURRENT |
1-Alert |
[chars] |
RPS overcurrent condition detected |
hardware |
"Unplug the switches that are being backed off" |
|
PLATFORM_ENV-1-RPS_OVER_CURRENT |
1-Alert |
[chars] |
RPS overcurrent condition detected |
hardware |
"Unplug the switches that are being backed off" |
|
PLATFORM_ENV-1-RPS_PS_FAN_FAILED |
1-Alert |
RPS power supply [chars] fan failure detected |
RPS power supply fan failure has been detected |
hardware |
"Disconnect any switches connected to the RPS and " "replace the power supply immediately" |
|
PLATFORM_ENV-1-RPS_PS_FAN_FAILED |
1-Alert |
RPS power supply [chars] fan failure detected |
RPS power supply fan failure has been detected |
hardware |
"Disconnect any switches connected to the RPS and " "replace the power supply immediately" |
|
PLATFORM_ENV-1-RPS_PS_MISMATCH |
1-Alert |
[chars] |
Power supplies inserted in RPS are incompatible |
firmware |
"Remove either one of the power supplies or " "insert compatible power supplies" |
|
PLATFORM_ENV-1-RPS_PS_MISMATCH |
1-Alert |
[chars] |
Power supplies inserted in RPS are incompatible |
firmware |
"Remove either one of the power supplies or " "insert compatible power supplies" |
|
PLATFORM_ENV-1-RPS_PS_SIGNAL_FAULTY |
1-Alert |
[chars] signal on RPS power supply [chars] is faulty |
The specified power supply of RPS has faulty signal |
hardware |
LOG_STD_ACTION |
|
PLATFORM_ENV-1-RPS_PS_SIGNAL_FAULTY |
1-Alert |
[chars] signal on RPS power supply [chars] is faulty |
The specified power supply of RPS has faulty signal |
hardware |
LOG_STD_ACTION |
|
PLATFORM_ENV-1-RPS_PS_THERMAL_CRITICAL |
1-Alert |
RPS power supply [chars] temperature has reached critical threshold |
The power supply inside RPS has reached the critical threshold. RPS cannot function normally |
hardware |
"The external temperature is very high." " Reduce the temperature in the room immediately" |
|
PLATFORM_ENV-1-RPS_PS_THERMAL_CRITICAL |
1-Alert |
RPS power supply [chars] temperature has reached critical threshold |
The power supply inside RPS has reached the critical threshold. RPS cannot function normally |
hardware |
"The external temperature is very high." " Reduce the temperature in the room immediately" |
|
PLATFORM_ENV-1-RPS_STANDBY |
1-Alert |
[chars] |
Faulty RPS detected |
firmware |
LOG_STD_ACTION |
|
PLATFORM_ENV-1-RPS_STANDBY |
1-Alert |
[chars] |
Faulty RPS detected |
firmware |
LOG_STD_ACTION |
|
PLATFORM_ENV-1-RPS_SYS_POWER_BAD |
1-Alert |
[chars] |
RPS system power changed state to bad. It may not provide backup |
hardware |
"Check the power supplies in RPS. If fault " "persists replace the power supply" |
|
PLATFORM_ENV-1-RPS_SYS_POWER_BAD |
1-Alert |
[chars] |
RPS system power changed state to bad. It may not provide backup |
hardware |
"Check the power supplies in RPS. If fault " "persists replace the power supply" |
|
PLATFORM_ENV-1-RPS_SYS_POWER_GOOD |
1-Alert |
[chars] |
RPS system power changed state to good |
hardware |
"LOG_STD_NO_ACTION" |
|
PLATFORM_ENV-1-RPS_SYS_POWER_GOOD |
1-Alert |
[chars] |
RPS system power changed state to good |
hardware |
"LOG_STD_NO_ACTION" |
|
PLATFORM_ENV-1-RPS_THERMAL_CRITICAL |
1-Alert |
RPS temperature has reached critical threshold |
The temperature sensor value inside RPS has reached the critical threshold. RPS cannot function normally |
hardware |
"The external temperature is very high." " Reduce the temperature in the room immediately" |
|
PLATFORM_ENV-1-RPS_THERMAL_CRITICAL |
1-Alert |
RPS temperature has reached critical threshold |
The temperature sensor value inside RPS has reached the critical threshold. RPS cannot function normally |
hardware |
"The external temperature is very high." " Reduce the temperature in the room immediately" |
|
PLATFORM_ENV-1-TEMP |
1-Alert |
Abnormal temperature detected |
Abnormal temperature detected |
firmware |
"Ensure that ambient temperature is not too high in" " the area. If fault persists replace the component" |
|
PLATFORM_ENV-1-THERMAL_CRITICAL |
1-Alert |
Temperature has reached critical threshold |
The temperature sensor value inside the switch has reached the critical threshold. Switch cannot function normally |
hardware |
"The external temperature is very high." " Reduce the temperature in the room immediately" |
|
PLATFORM_ENV-2-RPS_THERMAL_WARNING |
2-Critical |
RPS temperature has reached warning threshold |
The temperature sensor value inside RPS has reached the warning threshold. RPS can function normally until the temperature reaches the critical threshold |
hardware |
"The external temperature is high." " Reduce the temperature in the room" |
|
PLATFORM_ENV-2-RPS_THERMAL_WARNING |
2-Critical |
RPS temperature has reached warning threshold |
The temperature sensor value inside RPS has reached the warning threshold. RPS can function normally until the temperature reaches the critical threshold |
hardware |
"The external temperature is high." " Reduce the temperature in the room" |
|
PLATFORM_ENV-2-THERMAL_WARNING |
2-Critical |
Temperature has reached warning threshold |
The temperature sensor value inside the switch has reached the warning threshold. The switch can function normally untill the temperature reaches the critical threshold |
hardware |
"The external temperature is high." " Reduce the temperature in the room" |
|
PLATFORM_ENV-3-ENV_INIT_FAIL |
3-Error |
Environmental Driver Initialization Error |
The Environmental Driver failed to initialize. There is no way to determine the switch system voltage rail thermal and fan status behavior |
firmware |
"If the fault persists please replace the " "component and/or update the environmental driver." |
|
PLATFORM_ENV-3-GLUE_INIT_FAIL |
3-Error |
Hardware Tracking Driver Initialization Error |
The Hardware Tracking Driver failed to initialize. There is no way to determine the switch FRU power supplies SFP FPGA SPI JTAG and Alarms behavior |
firmware |
"If the fault persists please replace the " "component and/or update the driver." |
|
PLATFORM_ENV-3-GLUE_INTR_NOT_FUNCTIONING |
3-Error |
Hardware Tracking Driver: State Change Detection not functioning |
The Hardware Tracking Driver no longer detects state changes. There is no way to determine the switch FRU power supplies SFP FPGA SPI JTAG and Alarms state change |
firmware |
"Ensure that the ambient temperature is not too high" "in the area. If the fault persists please replace the component and/or " "update the driver." |
|
PLATFORM_ENV-3-ILP_PORT_POST_ERR |
3-Error |
[chars] can't be brought up because it failed POST in Inline Power test. |
An error reported by the Power over Ethernet PoE controller |
hardware |
LOG_STD_SH_TECH_ACTION |
|
PLATFORM_ENV -3-LOOPBACK_PORT_POST_ERR |
3-Error |
[chars] can't be brought up because it failed POST in Loopback test. |
A loopback error detected during POST. |
hardware |
LOG_STD_SH_TECH_ACTION |
|
PLATFORM_ENV-3-MCU_I2C_READ_ERROR |
3-Error |
I2C read failed in MCU and attached devices e.g. Temperature Sensor can't be read. |
MCU I2C rea dfailed. The temperature sensor etc. read failed in MCU. There is no way to determine the switch temperature behavior |
hardware |
"Ensure that the ambient temperature is not too high" "in the area. If the fault persists please replace the component." |
|
PLATFORM_ENV-3-RPS_BACKOFF_FAILED |
3-Error |
[chars] |
RPS is continuing to backup switch even though switch issued a command to backoff |
firmware |
LOG_STD_NO_ACTION |
|
PLATFORM_ENV-3-RPS_BACKOFF_FAILED |
3-Error |
[chars] |
RPS is continuing to backup switch even though switch issued a command to backoff |
firmware |
LOG_STD_NO_ACTION |
|
PLATFORM_ENV-3-RPS_CHANGE_TO_STANDBY |
3-Error |
[chars] |
RPS has changed state to standby. It will no longer backup the switch |
hardware |
"LOG_STD_NO_ACTION" |
|
PLATFORM_ENV-3-RPS_CHANGE_TO_STANDBY |
3-Error |
[chars] |
RPS has changed state to standby. It will no longer backup the switch |
hardware |
"LOG_STD_NO_ACTION" |
|
PLATFORM_ENV-3-RPS_FAULTY_BACKUP |
3-Error |
[chars] |
RPS error condition detected |
firmware |
"This problem could be transient. If fault " "persists remove and reconnect the switch" |
|
PLATFORM_ENV-3-RPS_FAULTY_BACKUP |
3-Error |
[chars] |
RPS error condition detected |
firmware |
"This problem could be transient. If fault " "persists remove and reconnect the switch" |
|
PLATFORM_ENV-3-RPS_POST_FAILED |
3-Error |
[chars] |
RPS POST failure detected |
firmware |
"LOG_STD_NO_ACTION" |
|
PLATFORM_ENV-3-SMB_HW_FAULT |
3-Error |
[chars] 0x%2x |
Faulty Bus State detected |
firmware |
LOG_STD_ACTION |
|
PLATFORM_ENV-3-SMB_RESET_EXCEEDED |
3-Error |
[chars] 0x%02x |
Faulty device detected |
firmware |
LOG_STD_ACTION |
|
PLATFORM_ENV-3-THERMAL_NOT_FUNCTIONING |
3-Error |
Temperature Sensor is not functioning |
The temperature sensor is not functioning There is no way to determine the switch temperature behavior |
hardware |
"Ensure that the ambient temperature is not too high" "in the area. If the fault persists please replace the component and/or " "update the driver." |
|
PLATFORM_ENV-3-VOLTAGE_NOT_FUNCTIONING |
3-Error |
Voltage Rail Sensors are not functioning |
The voltage rail sensors are not functioning There is no way to determine the switch voltage rail behavior |
hardware |
"Ensure that the ambient temperature is not too high" "in the area. If the fault persists please replace the component and/or " "update the driver." |
|
PLATFORM_ENV-5-RPS_THERMAL_NORMAL |
5-Notice |
RPS temperature is within the acceptable limit |
The temperature sensor value inside RPS is within the normal limit |
hardware |
LOG_STD_NO_ACTION |
|
PLATFORM_ENV-5-RPS_THERMAL_NORMAL |
5-Notice |
RPS temperature is within the acceptable limit |
The temperature sensor value inside RPS is within the normal limit |
hardware |
LOG_STD_NO_ACTION |
|
PLATFORM_ENV-5-THERMAL_NORMAL |
5-Notice |
Temperature is within the acceptable limit |
The temperature sensor value inside the switch is within the normal limit |
hardware |
LOG_STD_NO_ACTION |
|
PLATFORM_ENV-6-FRU_FAN_OIR |
6-Information |
FRU FAN [chars] |
FAN inserted or removed |
firmware |
LOG_STD_NO_ACTION |
|
PLATFORM_ENV-6-FRU_PS_OIR |
6-Information |
FRU Power Supply [chars] |
Power Supply inserted or removed |
firmware |
LOG_STD_NO_ACTION |
|
PLATFORM_ENV-6-RPS |
6-Information |
Redundant Power SupplyRPS [chars] |
- |
- |
- |
|
PLATFORM_ENV-6-RPS |
6-Information |
Redundant Power SupplyRPS [chars] |
Redundant Power Supply RPS changed state |
firmware |
LOG_STD_NO_ACTION |
|
PLATFORM_ENV-6-RPS_INFO |
6-Information |
Redundant Power Supply [chars] |
Related info about RPS |
firmware |
LOG_STD_NO_ACTION |
|
PLATFORM_ENV-6-RPS_INFO |
6-Information |
Redundant Power Supply [chars] |
Related info about RPS |
firmware |
LOG_STD_NO_ACTION |
|
PLATFORM_ENV-6-RPS_PRESENCE |
6-Information |
Redundant Power SupplyRPS [chars] |
Redundant Power Supply RPS changed state |
firmware |
LOG_STD_NO_ACTION |
|
PLATFORM_ENV-6-RPS_PS_INSERTED |
6-Information |
[chars] |
Power supply inserted in RPS |
hardware |
"LOG_STD_NO_ACTION" |
|
PLATFORM_ENV-6-RPS_PS_INSERTED |
6-Information |
[chars] |
Power supply inserted in RPS |
hardware |
"LOG_STD_NO_ACTION" |
|
PLATFORM_ENV-6-RPS_PS_REMOVED |
6-Information |
[chars] |
Power supply removed from RPS |
hardware |
"LOG_STD_NO_ACTION" |
|
PLATFORM_ENV-6-RPS_PS_REMOVED |
6-Information |
[chars] |
Power supply removed from RPS |
hardware |
"LOG_STD_NO_ACTION" |
|
PLATFORM_HA-3-CHASSIS_INIT_FAILED |
3-Error |
Failed to initialize QEMU chassis Interface |
Failed to init QEMU chassis interface with platform |
QEMU_DDTS_COMPONENT |
LOG_STD_ACTION |
|
PLATFORM_HA-3-NO_RCSF_PROCESS |
3-Error |
Failed to create process for rcsf deinit |
Failed to create a process |
QEMU_DDTS_COMPONENT |
LOG_STD_ACTION |
|
PLATFORM_HA-3-OIR_INIT |
3-Error |
Failed to register with the OIR Library |
Failed to register with the OIR Library |
QEMU_DDTS_COMPONENT |
LOG_STD_ACTION |
|
PLATFORM_HA-3-OIR_PROCESS_CREATE |
3-Error |
Failed to create OIR process during init |
Failed to create process to do OIR init |
QEMU_DDTS_COMPONENT |
LOG_STD_ACTION |
|
PLATFORM_HA-3-PLATFORM_RELOAD_PEER_FAILED |
3-Error |
Failed to send message to platform to request a peer reload |
Unable to send a message to the platform |
QEMU_DDTS_COMPONENT |
LOG_STD_ACTION |
|
PLATFORM_HA-3-RF_REGISTRATION_FAILED |
3-Error |
Failed to register with RF rc = [dec] |
Failed to register with RF during system initialization |
QEMU_DDTS_COMPONENT |
LOG_STD_ACTION |
|
PLATFORM_HA-3-SLOT_ID_FAILED |
3-Error |
Failed to get the slot ID from OIR Library |
Failed to get the slot ID from OIR Library |
QEMU_DDTS_COMPONENT |
LOG_STD_ACTION |
|
PLATFORM_HA-3-SPI_INIT_FAILED |
3-Error |
Unable to initialize QEMU chassis SPI client |
Failed to init QEMU chassis SPI client |
QEMU_DDTS_COMPONENT |
LOG_STD_ACTION |
|
PLATFORM_HA-3-SPI_NOT_READY |
3-Error |
SPI is not ready cannot communicate with platform |
Unable to communicate to the platform as SPI is not ready |
QEMU_DDTS_COMPONENT |
LOG_STD_ACTION |
|
PLATFORM_HA-3-SPI_PROCESS_CREATE |
3-Error |
Failed to create SPI process during init |
Failed to create process to do SPI init |
QEMU_DDTS_COMPONENT |
LOG_STD_ACTION |
|
PLATFORM_HA-3-SSO_FALLBACK_NOT_SUPPORTED |
3-Error |
Redundancy mode fallback to SSO is not supported |
Cannot fallback to redundancy mode SSO |
QEMU_DDTS_COMPONENT |
LOG_STD_ACTION |
|
PLATFORM_HA-3-TRACE_INIT |
3-Error |
Cannot allocate the trace buffer for [chars] |
Standby switch is being booted in the indicated fallback mode. Additional entries in log will indicate the reason for this action. |
QEMU_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
PLATFORM_HA-3-WATCHED_BOOLEAN_ROLE |
3-Error |
Failed to create watched boolean during init |
Failed to allocate memory for watched boolean |
QEMU_DDTS_COMPONENT |
LOG_STD_ACTION |
|
PLATFORM_HA-3-WATCHED_BOOLEAN_SLOT |
3-Error |
Failed to create watched boolean during init |
Failed to allocate memory for watched boolean |
QEMU_DDTS_COMPONENT |
LOG_STD_ACTION |
|
PLATFORM_HA-4-RELOAD_PEER |
4-Warning |
Reloading the Standby due to [chars] [chars] |
Application on the Active has requested a reload of the Standby. |
QEMU_DDTS_COMPONENT |
LOG_STD_ACTION |
|
PLATFORM_HA-4-RELOAD_PEER_FAILED |
4-Warning |
Failed to reload the Standby due to [chars] [chars] |
- |
QEMU_DDTS_COMPONENT |
LOG_STD_ACTION |
|
PLATFORM_HA-4-RELOAD_SHELF |
4-Warning |
Reloading the shelf due to [chars] [chars] |
Application on the Active has requested a reload of the shelf. |
QEMU_DDTS_COMPONENT |
LOG_STD_ACTION |
|
PLATFORM_HA-4-RELOAD_SHELF_FAILED |
4-Warning |
Failed to reload the shelf due to [chars] [chars] |
- |
QEMU_DDTS_COMPONENT |
LOG_STD_ACTION |
|
PLATFORM_HA-6-REDUNDANCY_MODE |
6-Information |
[chars] supervisor initializing for [chars] mode |
Informational message regarding the redundancy mode of the supervisor |
QEMU_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
PLATFORM_IE9K-3-FCS_ERROR |
3-Error |
[chars] [chars] [chars] [chars] |
The port fcs error threshold max has reached |
- |
LOG_STD_ACTION |
|
PLATFORM_IE9K-3-PORT_LINK_FAULT |
3-Error |
[chars] [chars] [chars] [chars] |
The port link is not coming up the startup selftest has failed |
- |
LOG_STD_ACTION |
|
PLATFORM_IE9K-3-PORT_NOT_FORWARDING |
3-Error |
[chars] [chars] [chars] [chars] |
The port is not forwarding the startup selftest has failed |
- |
LOG_STD_ACTION |
|
PLATFORM_IE9K-3-PORT_NOT_OPERATING |
3-Error |
[chars] [chars] [chars] [chars] |
The port is not operating the startup selftest has failed |
- |
LOG_STD_ACTION |
|
PLATFORM_IE9K-5-PORT_FAST_RETRAIN |
5-Notice |
Port link fast-retraining has happened for [chars] |
The port link fast-retraining has happened for [chars] |
- |
LOG_STD_NO_ACTION |
|
PLATFORM_IMSP-3-FCS_ERROR |
3-Error |
[chars] [chars] [chars] [chars] |
The port fcs error threshold max has reached |
- |
LOG_STD_ACTION |
|
PLATFORM_IMSP-3-PORT_LINK_FAULT |
3-Error |
[chars] [chars] [chars] [chars] |
The port link is not coming up the startup selftest has failed |
- |
LOG_STD_ACTION |
|
PLATFORM_IMSP-3-PORT_NOT_FORWARDING |
3-Error |
[chars] [chars] [chars] [chars] |
The port is not forwarding the startup selftest has failed |
- |
LOG_STD_ACTION |
|
PLATFORM_IMSP-3-PORT_NOT_OPERATING |
3-Error |
[chars] [chars] [chars] [chars] |
The port is not operating the startup selftest has failed |
- |
LOG_STD_ACTION |
|
PLATFORM_IMSP-5-PORT_FAST_RETRAIN |
5-Notice |
Port link fast-retraining has happened for [chars] |
The port link fast-retraining has happened for [chars] |
- |
LOG_STD_NO_ACTION |
|
PLATFORM_IMSP-5-PORT_SEU_EVENT |
5-Notice |
Port SEU Cable discharge event on [chars]. Firmware Download in progress. |
Port SEU Cable discharge event on [chars]. Firmware download in progress. |
- |
LOG_STD_NO_ACTION |
|
PLATFORM_IMSP-5-PORT_SEU_EVENT_FW_DWLD_FAIL |
5-Notice |
Port SEU Cable discharge event on [chars]. Firmware download failed. |
Port SEU Cable discharge event on [chars]. Firmware download failed. |
- |
LOG_STD_NO_ACTION |
|
PLATFORM_IMSP-5-PORT_SEU_EVENT_FW_DWLD_SUCCESS |
5-Notice |
Port SEU Cable discharge event on [chars]. Firmware download successful. |
Port SEU Cable discharge event on [chars]. Firmware download successful. |
- |
LOG_STD_NO_ACTION |
|
PLATFORM_INFRA-3-IOS_DOT1Q_MIN_ERR |
3-Error |
Invalid MTU size. To send 802.1Q [chars] tagged packets configure linux MTU mapped to [chars] as at least [dec]. Ignore if it is a dot1q Native vlan. |
IOS DOT1Q WARNING for minimum MTU size |
gemboa-platform |
LOG_STD_ACTION |
|
PLATFORM_INFRA-4-IOS_DOT1Q_WARNING |
4-Warning |
#if !defined |
- |
- |
- |
|
PLATFORM_INFRA-5-IOS_INTR_EVENT |
5-Notice |
IOS thread interrupt event [dec]. |
IOS thread process interrupt event |
asr1k-iosd-infra |
LOG_STD_ACTION |
|
PLATFORM_INFRA-5-IOS_INTR_EVENT |
5-Notice |
IOS thread interrupt event [dec]. |
IOS thread process interrupt event |
asr1k-iosd-infra |
LOG_STD_ACTION |
|
PLATFORM_INFRA-5-IOS_INTR_HISTORY |
5-Notice |
[[dec]|[dec]] [[dec]:[dec]] [[dec]->[dec]] ra[ l* 0x[hec] l* 0x[hec] ] |
IOS thread process interrupt history |
asr1k-iosd-infra |
LOG_STD_ACTION |
|
PLATFORM_INFRA-5-IOS_INTR_HISTORY |
5-Notice |
[[dec]|[dec]] [[dec]:[dec]] [[dec]->[dec]] ra[ l* 0x[hec] l* 0x[hec] ] |
IOS thread process interrupt history |
asr1k-iosd-infra |
LOG_STD_ACTION |
|
PLATFORM_INFRA-5-IOS_INTR_INVALID_LEVEL |
5-Notice |
IOS thread interrupt level [dec] replaced by [dec] |
An invalid IOS thread interrupt level was used |
asr1k-iosd-infra |
LOG_STD_ACTION |
|
PLATFORM_INFRA-5-IOS_INTR_INVALID_LEVEL |
5-Notice |
IOS thread interrupt level [dec] replaced by [dec] |
An invalid IOS thread interrupt level was used |
asr1k-iosd-infra |
LOG_STD_ACTION |
|
PLATFORM_INFRA-5- IOS_INTR_LIMIT_NOT_SET |
5-Notice |
IOS thread interrupt limit not set |
IOS failed to retrieve interrupt limit |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
PLATFORM_INFRA-5-IOS_INTR_OVER_LIMIT |
5-Notice |
IOS thread disabled interrupt for [dec] msec |
IOS thread process disabled interrupt too long |
asr1k-iosd-infra |
LOG_STD_ACTION |
|
PLATFORM_INFRA-5-IOS_INTR_OVER_LIMIT |
5-Notice |
IOS thread disabled interrupt for Total: [dec] msec utime: [dec] msec stime: [dec] msec. |
IOS thread process disabled interrupt too long |
Respective Platform Component |
LOG_STD_ACTION |
|
PLATFORM_INFRA-5-IOS_INTR_OVER_LIMIT_HIGH_STIME |
5-Notice |
IOS thread blocked due to SYSTEM LEVEL ISSUE for Total: [dec] msec utime: [dec] msec stime: [dec] msec. [chars] |
IOS thread needs to disable interrupt to protect its critical section of the code. But when it locks up the interrupt for too long due to SYSTEM LEVEL ISSUE causing high stime display interrupt over limit warning traceback |
Respective Platform Component |
LOG_STD_ACTION |
|
PLATFORM_INFRA-5-IOS_INTR_OVER_LIMIT_LEGACY |
5-Notice |
IOS thread disabled interrupt for [dec] msec. |
IOS thread process disabled interrupt too long for platforms not supporting syspage |
Respective Platform Component |
LOG_STD_ACTION |
|
PLATFORM_IPSEC_HSEC-3-INVALID_HSEC |
3-Error |
HSEC license not present: IPSec [chars] configuration is rejected |
HSEC license needs to be present on the system |
accsw-p-security |
"show platform" |
|
PLATFORM_IPSEC_HSEC-3-UNAUTHORIZED_HSEC |
3-Error |
[chars] |
SWO with IPSEC but HSEC unauth |
accsw-p-security |
"show platform" |
|
PLATFORM_IPv6_UCAST-3-ADJ |
3-Error |
[chars] |
Platform ipv6 unicast routing adj related error occured |
firmware |
LOG_STD_ACTION |
|
PLATFORM_IPv6_UCAST-3-ADJ_BACKWALK |
3-Error |
[chars] |
Platform ipv6 unicast routing Adj Backwalk related error occured |
firmware |
LOG_STD_ACTION |
|
PLATFORM_IPv6_UCAST-3-ERROR |
3-Error |
[chars] |
Platform ipv6 unicast routing module encountered an error |
firmware |
LOG_STD_ACTION |
|
PLATFORM_IPv6_UCAST-3-FIB |
3-Error |
[chars] |
Platform ipv6 unicast routing prefix related error occured |
firmware |
LOG_STD_ACTION |
|
PLATFORM_IPv6_UCAST-3-INTERFACE |
3-Error |
[chars] |
Platform ipv6 unicast routing interface related error occured |
firmware |
LOG_STD_ACTION |
|
PLATFORM_IPv6_UCAST-3-LB |
3-Error |
[chars] |
Platform ipv6 unicast routing load balance related error occured |
firmware |
LOG_STD_ACTION |
|
PLATFORM_IPv6_UCAST-3-LB_BACKWALK |
3-Error |
[chars] |
Platform ipv6 unicast routing LB Backwalk related error occured |
firmware |
LOG_STD_ACTION |
|
PLATFORM_IPv6_UCAST-3-ND |
3-Error |
[chars] |
Platform ipv6 unicast routing neighbor discovery related error occured |
firmware |
LOG_STD_ACTION |
|
PLATFORM_IPv6_UCAST-3-PROXY |
3-Error |
[chars] |
Platform ipv6 unicast routing ND-Proxy related error occured |
firmware |
LOG_STD_ACTION |
|
PLATFORM_IPv6_UCAST-3-RPC |
3-Error |
[chars] |
Platform ipv6 unicast routing RPC related error occured |
firmware |
LOG_STD_ACTION |
|
PLATFORM_IPv6_UCAST-3-TABLE |
3-Error |
[chars] |
Platform ipv6 unicast routing table related error occured |
firmware |
LOG_STD_ACTION |
|
PLATFORM_IPV6HOST-2-CANNOT_INIT |
2-Critical |
Insufficient resources to initialize platform-specific IPv6 host functionality |
The platform-specific part of the IPv6 host support failed to initialize at boot time. |
- |
"IPv6 cannot be used on this system" |
|
PLATFORM_MATM-3-INVALID_MSG_RECEIVED |
3-Error |
MATM received invalid SPI message. |
A messages that was to be received from the hardware module was not received correctly. Mac address learning/ageing might be impacted as a result. The failure most likely occurred because of a software communication error. |
firmware |
LOG_STD_SH_TECH_ACTION |
|
PLATFORM_MATM-3- INVALID_MSG_RECEIVED |
3-Error |
MATM received invalid SPI message. |
A messages that was to be received from the hardware module was not received correctly. Mac address learning/ageing might be impacted as a result. The failure most likely occurred because of a software communication error. |
firmware |
LOG_STD_SH_TECH_ACTION |
|
PLATFORM_MATM-4-MAC_TABLE_CONSISTENCY |
4-Warning |
MATM consistency checker found mac table to be [chars] on slot [dec] |
MATM consistency checker has received a ACK/NACK from hardware.If the hardware returned NACKthe software and hardware tables are found to be inconsistent. Consistency checker will try to recover from the inconsistent state |
firmware |
LOG_STD_SH_TECH_ACTION |
|
PLATFORM_MATM-4-QUEUE_OVERLIMIT |
4-Warning |
MATM dropped [chars] messages as queue limit has reached. |
Messages received from the hardware module were not processed because an internal queue was full. Mac address learning/aging might be impacted as a result. |
firmware |
LOG_STD_SH_TECH_ACTION |
|
PLATFORM_MATM-4- QUEUE_OVERLIMIT |
4-Warning |
MATM dropped [chars] messages as queue limit has reached. |
Messages received from the hardware module were not processed because an internal queue was full. Mac address learning/aging might be impacted as a result. |
firmware |
LOG_STD_SH_TECH_ACTION |
|
PLATFORM_NCEF-3-ADJ |
3-Error |
[chars] |
Platform nile cef adj related error occured |
firmware |
LOG_STD_ACTION |
|
PLATFORM_NCEF-3-ADJ_BACKWALK |
3-Error |
[chars] |
Platform nile cef Adj Backwalk related error occured |
firmware |
LOG_STD_ACTION |
|
PLATFORM_NCEF-3-ERROR |
3-Error |
[chars] |
Platform nile cef module encountered an error |
firmware |
LOG_STD_ACTION |
|
PLATFORM_NCEF-3-FIB |
3-Error |
[chars] |
Platform nile cef prefix related error occured |
firmware |
LOG_STD_ACTION |
|
PLATFORM_NCEF-3-INTERFACE |
3-Error |
[chars] |
Platform nile cef interface related error occured |
firmware |
LOG_STD_ACTION |
|
PLATFORM_NCEF-3-LB |
3-Error |
[chars] |
Platform nile cef load balance related error occured |
firmware |
LOG_STD_ACTION |
|
PLATFORM_NCEF-3-LB_BACKWALK |
3-Error |
[chars] |
Platform nile cef LB Backwalk related error occured |
firmware |
LOG_STD_ACTION |
|
PLATFORM_NCEF-3-LB_MAP |
3-Error |
[chars] |
Platform nile cef load balance map related error occured |
firmware |
LOG_STD_ACTION |
|
PLATFORM_NCEF-3-NULL_HANDLE |
3-Error |
[chars] |
Platform nile cef null handle error occured |
firmware |
LOG_STD_ACTION |
|
PLATFORM_NCEF-3-TABLE |
3-Error |
[chars] |
Platform nile cef table related error occured |
firmware |
LOG_STD_ACTION |
|
PLATFORM_NETWORK_CLOCK-4-ERROR |
4-Warning |
NULL |
An unexpected condition has occurred. |
me3600-3800-timing |
LOG_STD_ACTION |
|
PLATFORM_PM-0-SPI_FC_FAIL |
0-Emergency |
SPI-FC Failure while sending PM SPI msg[chars]. If:[chars] Msg Type:[chars] Targets: 0x%X spi-fc ec: [dec] |
SPI-FC infra failed to service SPI msg transmit. Possibility coding error error code would help to know the reason for failure |
firmware |
LOG_STD_ACTION |
|
PLATFORM_PM-1-RSC_FAIL |
1-Alert |
[chars] |
Resource allocation failed. May need to reboot the system |
firmware |
LOG_STD_ACTION |
|
PLATFORM_PM-1-SPI_CNCT_FAIL |
1-Alert |
SPI connect call failed. Slot: [dec] SPI RH: 0x%X error code: [dec] |
Failure is due to SPI. System cannot function reliably further. Reboot may help |
firmware |
LOG_STD_ACTION |
|
PLATFORM_PM-2-ASYNC_WAIT_TOUT |
2-Critical |
PM wait for ack timed out: req_id [dec] dest slots:0x%X ack pending from slots 0x%X |
Time out happened while waiting for ack from driver process Possible reasons: \n1. SPI IPC communication failure |
firmware |
LOG_STD_ACTION |
|
PLATFORM_PM-2-BLK_WAIT_TOUT |
2-Critical |
PM wait for ack timed out: If [chars] dest slots:0x%X pending acks from boxes 0x%X |
Time out happened while waiting for ack from driver process Possible reasons: \n1. SPI IPC communication failure |
firmware |
LOG_STD_ACTION |
|
PLATFORM_PM-2-INVAL_IFID |
2-Critical |
Invalid IIF Id: 0x%016llX assigned to if:[chars] |
Port has invalid IIF Id assigned and hence SPI message to driver process FED can fail leaving system in unstable |
firmware |
LOG_STD_ACTION |
|
PLATFORM_PM-2-NOHWIDB |
2-Critical |
IDB does not exist |
HWIDB does not exist during SPAN configuration This would be due to IDB creation issue Please collect history of actions performed before hitting this error for further investigations. |
firmware |
LOG_STD_ACTION |
|
PLATFORM_PM-2-NOIDB |
2-Critical |
No IDB exists for IIF id: 0x%016llX |
IIF Id received in PM SPI msg from driver process FED is invalid and hence convertion to IDB fails. This would be due to interfaces deleted by the time IOSd receives the msgs. Please collect history of actions performed before hitting this error for further investigations. |
firmware |
LOG_STD_ACTION |
|
PLATFORM_PM-2-SPI_ADDMCAST_FAIL |
2-Critical |
Add multicast group member failed. Group Handle: 0x%X remote handle: 0x%X error code:[dec] |
SPI module problem. New handle is not added into multicast group handle. None of PM msgs would go to new switch driver process. Reboot newly added switch |
firmware |
LOG_STD_ACTION |
|
PLATFORM_PM-2-SPI_CHNL_NRDY |
2-Critical |
PM-SPI channel not ready yet slot: [dec] |
PM SPI channel not ready for communication yet. Use CLI 'show platform pm spi-info' to check channel status. If message seen during bootup it indicates system trying to send SPI msgs too early bootup. Missed SPI messages will be lost and system may be in unstable state. Need to reboot to recover from the current state Note: Slot:0 indicates multicast SPI channel |
firmware |
LOG_STD_ACTION |
|
PLATFORM_PM-2-SPISNDFAIL |
2-Critical |
PM SPI msg send failed. If:[chars] Msg Type:[chars] Targets: 0x%X ec: [dec] |
SPI msg send failed on PM SPI channel. Please look at error code ec and check if destination switch |
firmware |
LOG_STD_ACTION |
|
PLATFORM_PM-3-HALF_DUX_COLLISION_EXCEED_THRESHOLD |
3-Error |
Collisions at [chars] exceed threshold. Considered as loop-back. |
The collisions at a half-duplex port exceed the threshold and the port is considered as loop-back. |
firmware |
LOG_STD_NO_ACTION |
|
PLATFORM_PM-3-HOSTACCESSFAIL |
3-Error |
Unable to configure hardware to [chars] host access on [chars]. Port may not behave as expected. |
The system was unable to configure the hardware to set the requested host access policy. There may be insufficient TCAM resources available. |
firmware |
"Stop all traffic issue clear mac-address-table " "dynamic and remove and re-issue the command that failed." |
|
PLATFORM_PM-3-HOSTACCESSFAIL |
3-Error |
Unable to configure hardware to [chars] host access on [chars]. Port may not behave as expected. |
The system was unable to configure the hardware to set the requested host access policy. There may be insufficient TCAM resources available. |
firmware |
"Stop all traffic issue clear mac-address-table " "dynamic and remove and re-issue the command that failed." |
|
PLATFORM_PM-3-IFCOUNTERROR |
3-Error |
Creation of [chars] exceeds the exceeds the maximum limit for the number of interfaces of type [chars] [dec] |
The system supports a limited number of interfaces for each interface type. The user created more than the supported number of interfaces of this type |
firmware |
LOG_STD_ACTION |
|
PLATFORM_PM-3-LOOP_BACK_DETECTED |
3-Error |
Loop-back detected on [chars]. |
Loop-back may be caused accidentally by \ plugging in a balun cable to the port. |
firmware |
"Check the cables. If a balun cable is connected and the " "loopback condition is desired no action is required. " "Otherwise connect the correct cable and bring the port up." |
|
PLATFORM_PM-5-INVAL_PMODE |
5-Notice |
Port Mode: [dec] is not supported type for If:[chars] |
Unsuppoted port mode or invalid config. |
firmware |
LOG_STD_ACTION |
|
PLATFORM_PM-5-NOPC |
5-Notice |
Port cookie pc does not exist for If: [chars] |
Failed to get PM port_data subblock from IDB. Possible reason would be IDB is not supported by PM. If error is seen during bootup and if interfaces is PM supported it indicates trying to get PD prior to PM init completion |
firmware |
LOG_STD_ACTION |
|
PLATFORM_PM-5-NOPD |
5-Notice |
No Port data PD exists for If: [chars] |
Failed to get PM port_data subblock from IDB. Possible reason would be IDB is not supported by PM. If error is seen during bootup and if interfaces is PM supported it indicates trying to get PD prior to PM init completion |
firmware |
LOG_STD_ACTION |
|
PLATFORM_PM-5-OIR_CALLBACK_SYS_NOT_INIT |
5-Notice |
UDLD OIR Callback is invoked ahead of sys init complete |
UDLD OIR Callback is invoked too early. |
accsw-ha-infra |
LOG_STD_ACTION |
|
PLATFORM_PM-5-PDNOTPRESENT |
5-Notice |
No Port data PD exists |
Port data does not exist. This should not happen. If this error is seen during switchover there is a likely race condition in creation/deletion of port data. |
firmware |
LOG_STD_ACTION |
|
PLATFORM_PM-5-UNKNOWN_REQ |
5-Notice |
Ack received for unknown request from driver process FED. |
Ack from driver process is received for the request id which is not in wait queue. This would be due to delayed ack after time out at IOSd. |
firmware |
LOG_STD_ACTION |
|
PLATFORM_PM-6-DIFFERENT_MODULE_INSERTED |
6-Information |
Warning: SFP module inserted in to the interface [chars] differs from the previously inserted one. The port's [chars] configuration will be set to the default. |
A different SFP module has been inserted in the available slot. Previous configured duplex/speed will be set to default. |
firmware |
LOG_STD_NO_ACTION |
|
PLATFORM_PM-6-DOWNSHIFT |
6-Information |
Experienced Channel Quality Impairment on interface [chars] Downshifting Speed to [chars] |
Speed Downshift Detected. |
firmware |
LOG_STD_NO_ACTION |
|
PLATFORM_PM-6-FRULINK_INSERTED |
6-Information |
[chars] uplink module inserted in the switch [dec] slot [dec] |
A FRULink module has been inserted in the available slot. |
firmware |
LOG_STD_NO_ACTION |
|
PLATFORM_PM-6-FRULINK_REMOVED |
6-Information |
[chars] uplink module removed from switch [dec] slot [dec] |
The FRULink module inserted in the available slot has been removed. |
firmware |
LOG_STD_NO_ACTION |
|
PLATFORM_PM-6-FRULINK_UNKNOWN_INSERTED |
6-Information |
Unsupported FRU module inserted in slot [dec] |
The FRULink module inserted in the available slot is not supported. |
firmware |
LOG_STD_NO_ACTION |
|
PLATFORM_PM-6-FRULINK_UNKNOWN_REMOVED |
6-Information |
Unsupported FRU module removed from slot [dec] |
The FRULink module removed from the slot is not supported. |
firmware |
LOG_STD_NO_ACTION |
|
PLATFORM_PM-6-MODULE_ERRDISABLE |
6-Information |
The inserted SFP module with interface name [chars] is not supported |
The SFP module inserted in the available slot has been removed. |
firmware |
LOG_STD_NO_ACTION |
|
PLATFORM_PM-6-MODULE_INSERTED |
6-Information |
SFP module inserted with interface name [chars] |
The SFP module has been inserted in the available slot. |
firmware |
LOG_STD_NO_ACTION |
|
PLATFORM_PM-6-MODULE_REMOVED |
6-Information |
SFP module with interface name [chars] removed |
The SFP module inserted in the available slot has been removed. |
firmware |
LOG_STD_NO_ACTION |
|
PLATFORM_SEC-2-NOHWIDB |
2-Critical |
Software module for [chars] received null HWIDB. |
The security component received null HWIDB. This could be due to IDB creation issue. Please collect history of actions performed before hitting this error for further investigations. |
accsw-security |
LOG_STD_ACTION |
|
PLATFORM_SEC-2-NOIDB |
2-Critical |
Software module for [chars] received null SWIDB. |
The security component received null SWIDB. This could be due to interfaces deleted by the time the function gets called. Please collect history of actions performed before hitting this error for further investigations. |
accsw-security |
LOG_STD_ACTION |
|
PLATFORM_SEC-6-SGACLHIT |
6-Information |
list [chars] [chars] [chars] [inet][dec] -> [inet][dec] SGT [dec] DGT [dec] |
A packet matching the log criteria for the given sg access list was detected. |
accsw-security |
LOG_STD_NO_ACTION |
|
PLATFORM_SNMP-3-COMMAND_WARNING |
3-Error |
The command [[chars]] should not be configured on a stack of switches |
A command that is supported for standalone switches only was entered on a stack of switches. |
firmware |
"Either remove this command from the configuration " "save startup configuration and reload the stack OR " "remove all other stack members from the stack." |
|
PLATFORM_SPAN-5-NOSPANDATA |
5-Notice |
SPAN data not available during reconciliation |
SPAN data not available after switchover for reconciliation. Use CLI 'show monitor' 'show platform monitor-fed' to check if the configuration is intact after switchover. This is not expected please log a defect message seen during bootup it indicates system trying |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-3-INVALID_TOPOLOGY |
3-Error |
Invalid power stack topology observed by switch [dec]. [chars] |
Power stack topology is invalid. The switch is forced to operate in standalone mode |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-BISP |
4-Warning |
Switch [dec] experienced a BISP event |
Switch experienced a Built-in Self Protection event |
firmware |
"This is a notification message only." " No action is required." |
|
PLATFORM_STACKPOWER-4-BISP_NBR_DEAD |
4-Warning |
Switch [dec]'s neighbor experienced a major BISP event |
Switch's neighbor experienced a major Built-in Self-Protection event which caused the switch to shutdown |
firmware |
"This is a notification message only." " No action is required." |
|
PLATFORM_STACKPOWER-4-BISP_POE_OVER_I |
4-Warning |
Switch [dec] experienced a PoE over-current BISP event |
Switch experienced a PoE over-current Built-in Self-Protection event |
firmware |
"This is a notification message only." " No action is required." |
|
PLATFORM_STACKPOWER-4-BISP_POE_PORT |
4-Warning |
Switch [dec] experienced a port BISP event |
Switch experienced a port Built-in Self-Protection event which affected PoE |
firmware |
"This is a notification message only." " No action is required." |
|
PLATFORM_STACKPOWER-4-BISP_PORT_A_SC |
4-Warning |
Switch [dec] experienced a short-circuit BISP event on port 1 |
Switch experienced a short-circuit Built-in Self-Protection event on port 1 |
firmware |
"This is a notification message only." " No action is required." |
|
PLATFORM_STACKPOWER-4-BISP_PORT_B_SC |
4-Warning |
Switch [dec] experienced a short-circuit BISP event on port 2 |
Switch experienced a short-circuit Built-in Self-Protection event on port 2 |
firmware |
"This is a notification message only." " No action is required." |
|
PLATFORM_STACKPOWER-4-CABLE_A_CURRENT_IN |
4-Warning |
Switch [dec] stack power cable 1 inward current is over the limit |
Switch's stack power cable 1 inward current is over the limit of 40 Amperes. Please add a power supply to the switch |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-CABLE_A_CURRENT_OUT |
4-Warning |
Switch [dec] stack power cable 1 outward current is over the limit |
Switch's stack power cable 1 outward current is over the limit of 40 Amperes. Please move a power supply out of the switch |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-CABLE_B_CURRENT_IN |
4-Warning |
Switch [dec] stack power cable 2 inward current is over the limit |
Switch's stack power cable 2 inward current is over the limit of 40 Amperes. Please add a power supply to the switch |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-CABLE_B_CURRENT_OUT |
4-Warning |
Switch [dec] stack power cable 2 outward current is over the limit |
Switch's stack power cable 2 outward current is over the limit of 40 Amperes. Please move a power supply out of the switch |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-GLS_EVENT |
4-Warning |
Switch [dec] experienced a graceful load shed event |
Switch had to shed loads based on a SOC condition |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-HIGH_SKTPWR_CURR_WARN |
4-Warning |
Switch [dec] stack power current is high warning |
Switch's stack power current is high and a power supply failure may result in switch to get disconnect from power stack |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-ILS_EVENT |
4-Warning |
Switch [dec] experienced an immediate load shed event |
Switch had to shed loads based on a PS_FAIL condition |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-INSUFFICIENT_PWR |
4-Warning |
Switch [dec]'s power stack does not have enough power |
Switch's power stack does not have enough power to bring up all the switches in that power stack |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-NEIGHBOR_BISP |
4-Warning |
Switch [dec]'s neighbor switch experienced a BISP event |
A neighbor switch experienced a Built-in Self Protection event |
firmware |
"This is a notification message only." " No action is required." |
|
PLATFORM_STACKPOWER-4-NEIGHBOR_GLS |
4-Warning |
Switch [dec]'s neighbor switch experienced a graceful load shed event |
A neighbor switch had to shed loads based on a SOC condition |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-NEIGHBOR_ILS |
4-Warning |
Switch [dec]'s neighbor switch experienced an immediate load shed event |
A neighbor switch had to shed loads based on a PS_FAIL condition |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-NEIGHBOR_SRLS |
4-Warning |
Switch [dec]'s neighbor switch experienced a system ring load shed event |
A neighbor switch had to shed loads based on loss of a system |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-NEIGHBOR_SSLS |
4-Warning |
Switch [dec]'s neighbor switch experienced a system star load shed event |
A neighbor switch had to shed loads based on loss of a system |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-NEIGHBOR_UVLS |
4-Warning |
Switch [dec]'s neighbor switch experienced an under voltage load shed event |
A neighbor switch had to shed loads based on an under voltage condition |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-POWER_BUDGET |
4-Warning |
Switch [dec] power budget is at least 1000W greater than its local supplies |
Switch's power budget is more than 1000W above its power supplies rated power output. Please insert a power supply in this system |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-POWER_BUDGET_2K |
4-Warning |
Switch [dec] power budget is at least 2000W greater than its local supplies |
Switch's power budget is more than 2000W above its power supplies rated power output. Please insert a power supply in this system |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-PRIO_CONFLICT |
4-Warning |
Switch [dec]'s power stack has conflicting power priorities |
Switch's power priorities are conflicting with power priorities of another switch in the power stack |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-REDUNDANCY_LOSS |
4-Warning |
Switch [dec]'s power stack lost redundancy and is now operating in power sharing mode |
Power stack that this switch is part of has lost redundancy and is now operating in power sharing mode |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-SRLS_EVENT |
4-Warning |
Switch [dec] experienced a system ring load shed event |
Switch had to shed loads based on loss of a system |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-SSLS_EVENT |
4-Warning |
Switch [dec] experienced a system star load shed event |
Switch had to shed loads based on loss of a system |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-TOO_MANY_ERRORS |
4-Warning |
Switch [dec]: Too many errors seen on port [chars] |
Too many errors are seen on switch's stack power port 1/2 |
firmware |
"This is a notification message only." " No action is required." |
|
PLATFORM_STACKPOWER-4-UNBALANCED_PS |
4-Warning |
Switch [dec]'s power stack has unbalanced power supplies |
Switch's power stack has a switch with multiple power supplies while another switch in the same power stack has no power supplies |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-UNDER_BUDGET |
4-Warning |
Switch [dec] does not have sufficient power budget |
Switch's power budget is less than minimum required switch budget |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-UNDER_VOLTAGE |
4-Warning |
Switch [dec] experienced an under voltage condition |
Switch had an under voltage condition on last boot up /shutdown |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-UVLS_EVENT |
4-Warning |
Switch [dec] experienced an under voltage load shed event |
Switch had to shed loads based on an under voltage condition |
firmware |
LOG_STD_ACTION |
|
PLATFORM_STACKPOWER-4-VERSION_MISMATCH |
4-Warning |
Major version mismatch in stack power protocol message on switch [dec] |
Major version mismatch in stack power protocol message is observed on switch [dec] |
firmware |
"This is a notification message only." " No action is required." |
|
PLATFORM_STACKPOWER-6-CABLE_EVENT |
6-Information |
Switch [dec] stack power cable [chars] [chars] |
Switch's stack power cable 1/2 is inserted/removed |
firmware |
"This is a notification message only." " No action is required." |
|
PLATFORM_STACKPOWER-6-LINK_EVENT |
6-Information |
Switch [dec] stack power protocol is up on cable [chars] |
Switch's stack power cable 1/2 is now able to share power |
firmware |
"This is a notification message only." " No action is required." |
|
PLATFORM_SYS-3-NO_HW_ENTROPY |
3-Error |
No hardware entropy file found |
No hardware entropy file was found after waiting for over 500 seconds |
- |
"Collect trace logs from the cmand tams and tamd " "processes to search for the reason behind this" |
|
PLATFORM_SYS-4-IPSEC |
4-Warning |
Feature Mismatched on stack. IPSEC is configured on the stack but newly inserted switch [dec] does not support IPSEC. Please remove the new switch. |
This is a warning message for the user. A feature mismatched in IPSEC. IPSEC is configured on the stack but newly inserted switch does not support IPSEC. Please remove the newly inserted switch. |
- |
"Remove newly inserted switch." |
|
PLATFORM_SYS-4-SDM |
4-Warning |
Unsupported template detected and default template has been loaded |
This is a warning message for the user. An unsupported template was configured on the system and the default template has been loaded. |
- |
"This is a notification message only. " "No action is required." |
|
PLATFORM_SYS-6-UPTIME |
6-Information |
Time taken to initialize system = %-4d seconds |
This is an informational message for the user. This provides the time taken for the system to initialize on boot. The time is actually the time taken by system to finish initialization after kernel Linux is booted |
- |
"This is a notification message only. " "No action is required." |
|
PLATFORM_TAM-2-SUDI_VALIDATION_FAILED |
2-Critical |
Secure UDI validation failed. [chars] |
Secure UDI validation for the module failed. The module failed to authenticate itself |
iosxe-chassismgr |
LOG_STD_ACTION |
|
PLATFORM_THERMAL-1-FAN_CRITICAL |
1-Alert |
Switch [dec]: [chars] |
Faulty fansFRU fan or PS fan detected |
hardware |
"Replace the faulty fans and then turn on the system" |
|
PLATFORM_THERMAL-1-FRU_FAN_DISABLED |
1-Alert |
Switch [dec]: System fan [dec] disabled. Airflow direction for this fan should be [chars] |
FRU fan disabled because majority of fans have different airflow than this fan |
hardware |
"Fan disabled because of airflow direction. Replace the fan that has airflow consitent with other fans in the system" |
|
PLATFORM_THERMAL-1-FRU_FAN_FAILURE |
1-Alert |
Switch [dec]: System fan [dec] failed |
Fan failed |
firmware |
"Replace the fan." |
|
PLATFORM_THERMAL-1-FRU_FAN_FAULTY_OR_REMOVED |
1-Alert |
Switch [dec]: System fan [dec] faulty or removed |
Fan in non-funtional mode |
firmware |
"Need an action" |
|
PLATFORM_THERMAL-1-FRU_FAN_INSERT_OR_RECOVERY |
1-Alert |
Switch [dec]: System fan [dec] inserted or recovered |
Fan in funtional mode |
firmware |
LOG_STD_NO_ACTION |
|
PLATFORM_THERMAL-1-FRU_FAN_INSUFFICIENTFANTRAYSDETECTEDPOWERDOWN |
1-Alert |
Switch [dec]: Too few working fan trays exist and the switch will overheat. If this situation is not resolved by installing [dec] fan trays in a [chars] airflow direction the switch will power down in [dec] minutes |
Insufficient fan trays in the system |
hardware |
"Insert fan." |
|
PLATFORM_THERMAL-1-FRU_FAN_NOT_PRESENT |
1-Alert |
Switch [dec]: System fan [dec] not present |
Fan not present |
firmware |
"Insert fan." |
|
PLATFORM_THERMAL-1-TEMP_NOT_FUNCTIONAL |
1-Alert |
Switch [dec]: Temperature measurement not functioning. Condition may be transient. |
Temperature not detectedi by IOS |
firmware |
"Check that fans are working. Check 'show env temperature' command output. If condition persists contact TAC." |
|
PLATFORM_THERMAL-2-OVERTEMP_SHUTDOWN |
2-Critical |
Switch [dec]: [chars] |
The chassis inside temperature exceeds the max temperature threshold and will be shut down immediately. |
- |
- |
|
PLATFORM_THERMAL-2-UNDERTEMP_SHUTDOWN |
2-Critical |
Switch [dec]: [chars] |
The chassis inside temperature is below the min temperature threshold and will be shut down immediately. |
- |
- |
|
PLATFORM_THERMAL-2-VIOL_SEC_UNAVAILABLE |
2-Critical |
Switch [dec]: [chars] |
The chasfs property for violation second is not present. |
- |
- |
|
PLATFORM_THERMAL-3-OVERTEMP |
3-Error |
Switch [dec]: [chars] |
The chassis inside temperature exceeds the max temperature threshold |
- |
- |
|
PLATFORM_THERMAL-3-UNDERTEMP |
3-Error |
Switch [dec]: [chars] |
The chassis inside temperature is below the min temperature threshold |
- |
- |
|
PLATFORM_THERMAL-4-SECONDARY_OVERTEMP |
4-Warning |
Switch [dec]: [chars] |
The chassis inside temperature exceeds the configured threshold\n\ but less or equal to the max inside temperature |
- |
- |
|
PLATFORM_THERMAL-6-FRU_FAN_OIR |
6-Information |
Switch [dec]: System fan [dec] [chars] |
System fan inserted or removed |
firmware |
LOG_STD_NO_ACTION |
|
PLATFORM_THERMAL-6-FRU_FAN_RECOVERY |
6-Information |
Switch [dec]: System fan [dec] recovered to normal status |
Fan recovered |
firmware |
LOG_STD_NO_ACTION |
|
PLATFORM_THERMAL-6-TEMP_NORMAL |
6-Information |
Switch [dec]: temperature is within the normal limit. |
The temperature sensor value is within the normal limit |
hardware |
LOG_STD_NO_ACTION |
|
PLATFORM_UCAST-3-ADJ |
3-Error |
[chars] |
Platform unicast routing adjacency module encountered an error |
firmware |
LOG_STD_ACTION |
|
PLATFORM_UCAST-3-ARP |
3-Error |
[chars] |
Platform unicast routing arp module encountered an error |
firmware |
LOG_STD_ACTION |
|
PLATFORM_UCAST-3-CEF |
3-Error |
[chars] |
Platform unicast routing cef module encountered an error |
firmware |
LOG_STD_ACTION |
|
PLATFORM_UCAST-3-DYNAMIC |
3-Error |
[chars] |
Platform's dynamic address tracking mechanism encountered an error. |
firmware |
LOG_STD_ACTION |
|
PLATFORM_UCAST-3-ERROR |
3-Error |
[chars] |
An internal platform unicast routing error occurred |
firmware |
LOG_STD_ACTION |
|
PLATFORM_UCAST-3-HSRP |
3-Error |
[chars] |
Platform unicast routing hsrp module encountered an error |
firmware |
LOG_STD_ACTION |
|
PLATFORM_UCAST-3-INTERFACE |
3-Error |
[chars] |
Platform unicast routing interface related error occured |
firmware |
LOG_STD_ACTION |
|
PLATFORM_UCAST-3-LB |
3-Error |
[chars] |
Platform unicast routing loadbalance module encountered an error |
firmware |
LOG_STD_ACTION |
|
PLATFORM_UCAST-3-LB_BACKWALK |
3-Error |
[chars] |
Platform unicast routing backwalk loadbalance module encountered an error |
firmware |
LOG_STD_ACTION |
|
PLATFORM_UCAST-3-NULL_HANDLE |
3-Error |
[chars] |
Platform unicast routing module received a NULL software object handle |
firmware |
LOG_STD_ACTION |
|
PLATFORM_UCAST-3-RPC |
3-Error |
[chars] |
Platform unicast routing rpc module encountered an error |
firmware |
LOG_STD_ACTION |
|
PLATFORM_UCAST-4-PREFIX |
4-Warning |
Prefix [inet]/[dec] could not be programmed into TCAM |
A more specific prefix could not be programmed into TCAM and is covered by a less specific prefix. This could be a temporary condition. If it persists configuring a SDM template which allows higher number of routes may fix this problem. The <cmdBold>show platform ip unicast failed route<nocmdBold> command lists failed prefixes at a given time. |
me3600-me3800-l3 |
LOG_STD_NO_ACTION |
|
PLATFORM-0-MODULE_INSERTED |
0-Emergency |
[chars] module inserted\n |
- |
- |
- |
|
PLATFORM-0-MODULE_REMOVED |
0-Emergency |
[chars] module removed\n |
- |
- |
- |
|
PLATFORM-0-PIN_INSERTED |
0-Emergency |
[chars] pin inserted\n |
- |
- |
- |
|
PLATFORM-0-PIN_REMOVED |
0-Emergency |
[chars] pin removed\n |
- |
- |
- |
|
PLATFORM-0-SLOT_INSERTED |
0-Emergency |
[chars] cover/module inserted\n |
- |
- |
- |
|
PLATFORM-0-SLOT_REMOVED |
0-Emergency |
[chars] cover/module removed\n |
- |
- |
- |
|
PLATFORM-1-CRASH_PCIE |
1-Alert |
ERROR PCIE-[dec]: Fatal error. ERR_DR=0x[hec] ERR_CAPT=0x[hec] ERR_CAPT_R0=0x[hec] ERR_CAPT_R1=0x[hec] ERR_CAPT_R2=0x[hec] ERR_CAPT_R3=0x[hec] |
The system is crashing due to a PCIE hardware error. |
firmware |
LOG_STD_ACTION |
|
PLATFORM-1-CRASHED |
1-Alert |
[chars] |
The system is attempting to display the crash message from the previous crash. |
firmware |
LOG_STD_ACTION |
|
PLATFORM-1-NOSPACE |
1-Alert |
[chars] : no space alarm assert |
bootflash memory exhausted Delete the old file from boot flash to create space |
- |
LOG_STD_NO_ACTION |
|
PLATFORM-3-BACKUP_NVRAM_OPEN_FAIL |
3-Error |
Failed to open backup nvram - [chars]. |
The backup nvram device could not be opened. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
PLATFORM-3-BACKUP_NVRAM_READ_FAIL |
3-Error |
Failed to read backup nvram - [chars]. |
The backup nvram contents could not be read. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
PLATFORM-3-BACKUP_NVRAM_WRITE_FAIL |
3-Error |
Failed to write backup nvram - [chars]. |
Couldn't write into the backup nvram device. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
PLATFORM-3-FPTE_INTF_MODE |
3-Error |
Front-panel ethernet mode configuration is not in sync with INTF_MODE rommon variable value. Please use 'write' command and reboot to fix this. 10G ports will work in default TE mode in this current boot |
Front-panel ethernet mode configuration is not in sync with INTF_MODE rommon variable value. INTF_MODE rommon variable could have been over-written. Please use 'write' command and reboot to fix this. 10G ports will work in default TE mode in this current boot |
- |
LOG_STD_ACTION |
|
PLATFORM-3-GEC_NOMAC |
3-Error |
Can't allocate MAC address for port-channel interface [dec] |
MAC address allocation failed for the port-channel interface specified in the message. This may happen if the port-channel interface exceeds the maximum number of supported port-channel interfaces. |
iosxe-iosd-infra |
LOG_STD_ACTION |
|
PLATFORM-3-HAKPA_FAIL |
3-Error |
RP HA Keepalive failure [chars] |
Standby RP reports missing keepalives from Active. This is indicative of an IPC problem between peer IOSd processes |
iosxe-binos-ha |
LOG_STD_ACTION |
|
PLATFORM-3-HASTATUS_FAIL |
3-Error |
RP switchover [chars] count [dec] |
RP switchover failed to reach active state. The RP will be reset. This is indicative of a IPC problem between IOSd and CMRP |
iosxe-binos-ha |
"Make sure system achieves full redundant state " "after the RP reset. If not reload entire system" |
|
PLATFORM-3-NO_BASEMAC |
3-Error |
Can't retrieve base MAC address |
Base MAC address determination failed at system start. |
- |
LOG_STD_ACTION |
|
PLATFORM-3-NO_HARDWARE_RESOURCES |
3-Error |
Not enough hardware resources. Shutting down [chars] |
Too many vlans and routed ports |
firmware |
"Reduce the total number of vlans and routed ports" "to be less than 1023 . If this configuration" "and connectivity needs to be maintained across" "reboots save the configuration to nvram" |
|
PLATFORM-3-NOMAC |
3-Error |
Can't allocate MAC address for interface [dec]/[dec] |
MAC address allocation failed because of an incorrect slot and\n\ port combination which exceeds the maximum available hardware. |
- |
LOG_STD_ACTION |
|
PLATFORM-3-NOMAC_INTF |
3-Error |
Failed to allocate MAC address for interface [chars] |
MAC address allocation failed for logical interface specified in the message. |
- |
LOG_STD_ACTION |
|
PLATFORM-3-NVRAM_OPEN_FAIL |
3-Error |
Failed to open nvram - [chars]. |
The nvram device could not be opened. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
PLATFORM-3-NVRAM_READ_FAIL |
3-Error |
Failed to read nvram - [chars]. |
The nvram contents could not be read. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
PLATFORM-3-NVRAM_WRITE_FAIL |
3-Error |
Failed to write nvram - [chars]. |
Couldn't write into the nvram device. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
PLATFORM-3-REDMODE_FAIL |
3-Error |
Redundancy mode: [chars] rc [dec] |
Redundancy mode change could not be processed. This is indicative of a IPC problem between IOSd and the peer platform process. |
iosxe-binos-ha |
"Make sure system achieves full redundant state." "If not reload entire system" |
|
PLATFORM-3-RF_PROG_FAIL |
3-Error |
Progression completion notification to chassis management failed [chars] |
Could not notify the completion of the RF progression to the chassis management process. The system will potentially not be in a fully redundant state. |
iosxe-binos-ha |
LOG_STD_ACTION |
|
PLATFORM-3-RF_RELOAD_PEER |
3-Error |
Reload peer notification to chassis management failed [chars] |
Could not notify Reload Peer to the chassis management process. The Standby peer could not be reloaded by the Active. The system will potentially not be in a fully redundant state. |
iosxe-binos-ha |
"Reload peer instance using the available CLI " "commands. If system does not achieve full " "Standby status after that the system must " "be reloaded" |
|
PLATFORM-4-BOOTVAR_NOT_SET |
4-Warning |
Boot variable is not set. Leaving it blank |
- |
- |
- |
|
PLATFORM-4-BOOTVAR_TOO_SMALL |
4-Warning |
Boot variable buffer too small. Leaving it blank |
Boot variable either does not exist or buffer is too small. Not able to set boot variable. Ignoring it. |
asr1k-chassismgr |
LOG_STD_NO_ACTION |
|
PLATFORM-4-HASTATUS_WARN |
4-Warning |
RP HA status warning [chars] |
Standby RP reports peer not present event. This is indicative of a IPC problem between IOSd and CMRP |
iosxe-binos-ha |
LOG_STD_ACTION |
|
PLATFORM-4-LOWSPACE |
4-Warning |
[chars] : low space alarm assert |
bootflash memory is very low Delete the old file from boot flash to create space |
- |
LOG_STD_NO_ACTION |
|
PLATFORM-4-MATM_TBL_OVERFLOW |
4-Warning |
Mac table has reached the maximum limit.Features dependent on Mac table may have an impact. |
Mac Table is full and no space available for new mac address addition. MATM learning and dependent feature functionality may be impacted. |
petra-l2 |
"Make some space available in Mac Table" " to restore mac learning functions." |
|
PLATFORM -4-MEMORYSIZE |
4-Warning |
Active and Standby memory configuration differ by more than 1 GB. Active = %lldKB Standby = %lldKB |
The memory configuration on both the Supervisor is different by more than 1GB. Some of the functionality which is high availability aware and dependent on the memory like IOX will be impacted. |
- |
"Please upgrade/downgrade memory configuration on " "both the Supervisor to match the size" |
|
PLATFORM-4-RELOAD_STANDBY |
4-Warning |
[chars] reload requested by [chars]. Reason [chars] |
Unexpected configuration or states mismatch between Active and Standby RPs. Reloading Standby to synchronize the configuration or states. |
iosxe-binos-ha |
"None. This is expected behavior." |
|
PLATFORM -4-SDM_TEMPLATE |
4-Warning |
Mismatch in SDM templates configured on Active [chars] and Standby [chars] |
The SDM template configured on the two Supervisors are different. Different SDM template would enable different sets of features on the active and standby supervisors. Table sizes configured for the common features may be different. These features will not function properly on switchover from one supervisor to another. |
- |
"Please configure the same SDM template on both Supervisors using " "'sdm prefer <template>' configuration command followed by a reload. " "Supervisors should be brought to hot-standby state and the SDM " "template configured such that the template gets applied to both " "the supervisors. Supervisors can also be brought up as standalone " "and SDM template configured on them one at a time followed by a " "reload." |
|
PLATFORM-4-STATS_COLLECTION |
4-Warning |
Reducing statistics collection interval for SPA [chars] will impact the RP control plane |
MIB statistics for HW counters are sent from CC to RP every 10 seconds by default changing the timer through CLI to send more often will increase RP CPU utilization and result in sending more IPC messages between CC and RP |
iosxe-spa-infra |
LOG_STD_NO_ACTION |
|
PLATFORM-5-CONFIG_RECOVERY |
5-Notice |
IOS Configuration recovery is in progess. |
- |
- |
LOG_STD_NO_ACTION |
|
PLATFORM-5-HALF_DUPLEX |
5-Notice |
half duplex operation discovered on [chars] with [chars] [chars] |
The interface is found to operate in half duplex |
petra-platform |
LOG_STD_ACTION |
|
PLATFORM-5-LOWSPACERECOVER |
5-Notice |
[chars] : low space alarm deassert |
bootflash memory |
- |
LOG_STD_NO_ACTION |
|
PLATFORM-5-RESET_BUTTON |
5-Notice |
Reset Button pressed during boot up. |
- |
- |
LOG_STD_NO_ACTION |
|
PLATFORM-5-TRANSCEIVER_CHECKSUMFAILED |
5-Notice |
Slot=[dec] Port=[dec]: SFP EEPROM data check sum failed |
The SFP was identified as a Cisco SFP but the system was unable to read vendor-data information to verify its correctness. |
petra-platform |
"Remove and reinsert the SFP. If it fails " "again in the same way the SFP may be defective." |
|
PLATFORM-5-TRANSCEIVER_SECURITYCHECKFAIL |
5-Notice |
Slot=[dec] Port=[dec]: SFP Security check failed |
- |
- |
- |
|
PLATFORM-5-TRANSCEIVER_UNSUPPORTED |
5-Notice |
Slot=[dec] Port=[dec]: Unsupported transceiver found |
The module was identified as an unsupported non-Cisco transceiver. |
petra-platform |
LOG_STD_ACTION |
|
PLATFORM-5-TRANSCEIVER_UNSUPPORTED_PORT |
5-Notice |
Slot=[dec] Port=[dec]: Unsupported transceiver for the port found |
This SFP type is not supported on this port. |
petra-platform |
LOG_STD_ACTION |
|
PLATFORM-5-TRANSCEIVER_UNSUPPORTED_SYS |
5-Notice |
Slot=[dec] Port=[dec]: Unsupported transceiver for the switch found |
This SFP type is not supported on this switch. |
petra-platform |
LOG_STD_ACTION |
|
PLATFORM-5-TRANSCEIVERINSERTED |
5-Notice |
Slot=[dec] Port=[dec]: Transceiver has been inserted |
- |
- |
- |
|
PLATFORM-5-TRANSCEIVERREMOVED |
5-Notice |
Slot=[dec] Port=[dec]: Transceiver has been removed |
- |
- |
- |
|
PLATFORM-6-EVENT_LOG |
6-Information |
[chars] |
An entry from the internal event log at reload on the standby RP. This is informational. |
- |
LOG_STD_NO_ACTION |
|
PLATFORM-6-HASTATUS |
6-Information |
RP switchover [chars] |
RP switchover events received by platform code. |
- |
LOG_STD_NO_ACTION |
|
PLATFORM-6-HASTATUS_DETAIL |
6-Information |
RP switchover [chars] count [dec] |
RP switchover events received by platform code. |
- |
LOG_STD_NO_ACTION |
|
PLATFORM-6-MODULE_INSERTED |
6-Information |
[chars] module inserted in slot [dec] [chars] |
The system supports two types of modules a 10GE X2 and a 2 1GE SFP Module in slot 1/2. The module is inserted |
firmware |
LOG_STD_NO_ACTION |
|
PLATFORM-6-MODULE_REMOVED |
6-Information |
[chars] module removed in slot [dec] [chars] |
The system supports two types of modules a 10GE X2 and a 2 1GE SFP Module in slot 1/2. The module is removed |
firmware |
LOG_STD_NO_ACTION |
|
PLATFORM-6-RF_PROG_SUCCESS |
6-Information |
RF state [chars] |
A marker to illuminate when the standby reaches a terminal state. |
iosxe-binos-ha |
LOG_NO_ACTION |
|
PLATFORM-6-SB_INIT_DELAY |
6-Information |
RF progression will be suspended due to standby initialization delay configuration setting. Standby initialization will resume after [dec] seconds |
An informational message about the standby initialization delay configuration. RF progression will be delayed for the configured value. Bulk-sync and other progression events will not happen until after the configured delay value |
- |
LOG_STD_NO_ACTION |
|
PLATFORM-6-SB_INIT_DELAY_END |
6-Information |
RF progression delay timer expired. Standby initialization will now continue |
An informational message about the standby initialization delay configuration. RF progression will now continue since configured delay has expired |
- |
LOG_STD_NO_ACTION |
|
PLATFORM-6-SDM_TEMPLATE_SYNC |
6-Information |
Detected Standby supervisor with different [chars] SDM template |
A mismatch detected in SDM template configuration between Active and standby supervisors. However IOS automatically pushed the SDM template configured on Active Supervisor to Standby to avoid functionality or scale mismatch between Active and Standby supervisors. |
- |
LOG_STD_NO_ACTION |
|
PLATFORM-6-SVL_MGMT_INTF_MISMATCH |
6-Information |
Warning: The management interface is different between active and standby. |
The management interface has been configured differently between active and the standby switch |
- |
LOG_STD_NO_ACTION |
|
PLIM_QOS-3-IOSXE_RP_PLIM_QOS_FAIL |
3-Error |
A software error while configuring the [chars] on slot [dec] |
This error happens when IOS fails to send messages to configure the per slot qos parameters in forwarding plane |
iosxe-qos |
LOG_STD_ACTION |
|
PLOGDRP-3-MSGBIPCBUFFER |
3-Error |
Unable to acquire a BIPC buffer for sending messages. |
A message was to be sent by IOS but no BIPC buffer was available. The message to be sent has been discarded and the associated operation failed. |
iosxe-plog |
LOG_STD_ACTION |
|
PLOGDRP-3-MSGDISPATCHERR |
3-Error |
Error when receiving TDL error message: [chars] |
An unexpected condition in which IOS has received an error during TDL message processing from the Proxy Logger. |
iosxe-plog |
LOG_STD_ACTION |
|
PLOGDRP-3-MSGDISPATCHERR_SIZE |
3-Error |
Received TDL error message is larger than supported size :[dec] |
A TDL message larger than supported has been received and partial message of that is displayed. |
iosxe-plog |
LOG_STD_ACTION |
|
PLOGDRP-3-MSGDISPATCHNULL |
3-Error |
Received NULL TDL message |
An unexpected condition in which IOS has received a NULL TDL message for the Proxy Logger. |
iosxe-plog |
LOG_STD_ACTION |
|
PLOGDRP-3-MSGINVALIDFIELD |
3-Error |
Invalid errmsg field '[chars]' received from the Proxy Logger error [dec] |
An error message received from the Proxy Logger is missing a required field. |
iosxe-plog |
LOG_STD_ACTION |
|
PLOGDRP-4-MSGDISPATCH |
4-Warning |
Unable to dispatch received TDL message '[chars]' from Proxy Logger. LUID: [chars] |
An unexpected condition has occurred while IOS is trying to dispatch to the TDL message handler functions for received TDL messages from Proxy Logger. |
iosxe-plog |
LOG_STD_ACTION |
|
PLT_DBG_SCRIPTS-3-DIR_FAIL |
3-Error |
Failed to create [chars] directory in [chars] filesystem with [chars] error |
Failed to create platform_debug_scripts directory\n\ bootflash |
asr900-layer2-rsp3 |
"Ensure bootflash has sufficient space\n\ verify integrity of the bootflash" |
|
PLT_DBG_SCRIPTS-3-FILE_FAIL |
3-Error |
Failed to create [chars] file with [chars] error |
Failed to create platform_debug_scripts file\n\ bootflash |
asr900-layer2-rsp3 |
"Ensure bootflash has sufficient space\n\ verify integrity of the bootflash" |
|
PLT_DBG_SCRIPTS-3-INVALID_IDB |
3-Error |
Retrieved IDB from parser is invalid |
Failed to write data into the tcl debug script file |
asr900-layer2-rsp3 |
"Contact Cisco TAC\n" |
|
PLT_DBG_SCRIPTS-3-WRITE_FAIL |
3-Error |
Failed to write [dec] bytes in [chars] file |
Failed to write data into the tcl debug script file |
asr900-layer2-rsp3 |
"Ensure bootflash has sufficient space\n\ verify integrity of the bootflash" |
|
PM_AGENT-2-PMA_DOWN |
2-Critical |
PMA is Down.\n |
PMA is Down. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-3-ESON_DOWN |
3-Error |
\n |
Eson is Down. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-3-ESON_UP |
3-Error |
\n |
Eson is Up. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-3-HOP_CHAN_ADD_FAILURE |
3-Error |
PMA_HOP_ID : %lu PMA_DEST_SITE_ID : %lu PMA_REMOTE_IF_ID : %lu PMA_LOCAL_IF_ID : %lu PMA_DSCP : [dec]\n |
A Hop Channel failed to be added. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-3-LOCK_FAIL |
3-Error |
Can't lock pathmgr database: [chars] |
Access to pathmgr data is protected by a locking mechanism. An operation tried to read or write provisioning data but was unable to get control of the lock. |
pathmgr |
"Any Cisco iwan-router or iwan related configuration" "or show commands that you were attempting to " "run may not have succeeded. Please try the operation again.\n\n" "Contact support if this message is seen frequently." |
|
PM_AGENT-3-LOCK_RELEASE_FAIL |
3-Error |
Can't release the lock of pathmgr database: [chars] |
Access to pathmgr data is protected by a locking mechanism. An operation tried to release the acquired read or write lock but was unable to. |
pathmgr |
"Any Cisco iwan-router or iwan related configuration" "or show commands that you were attempting to " "run may not have succeeded. Please try the operation again.\n\n" "Contact support if this message is seen frequently." |
|
PM_AGENT-3-SITE_PREFIX_ADD_ERROR |
3-Error |
[chars] PMA_INSTANCE_ID : [dec] PMA_PFX_ADDR : [chars] PMA_PFX_MSK_LEN : [dec] PMA_PFX_FLAG : [chars]\n |
A Site Prefix is not Added Because of Error. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-3-TC_ADD_UPDATE_ERROR |
3-Error |
TC Add/Update has Error: [chars] PMA_TC_ID :[dec] PMA_SRC_ADDR :[chars] PMA_DST_ADDR :[chars] PMA_DSCP :[dec] //PMA_APP_ID :[dec] //PMA_SPI :[dec] PMA_IS_INTNET :[dec]\n |
A Traffic Class is not Added because of Error. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-5-HA_STATUS_CHANGE |
5-Notice |
[chars] PMA_PMCS_ADDR : [chars]\n |
HA Status has Changed. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-5-HOP_CHAN_STATUS_CHG |
5-Notice |
PMA_HOP_ID : %lu PMA_DEST_SITE_ID : %lu PMA_REMOTE_IF_ID : %lu PMA_LOCAL_IF_ID : %lu PMA_DSCP : [dec] PMA_TX_STATE : [chars] PMA_RX_STATE : [chars]\n |
Hop Channel Reachablity Status Changed. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-5-HOP_CHAN_UPDATE |
5-Notice |
PMA_HOP_ID : %lu PMA_DEST_SITE_ID : %lu PMA_REMOTE_IF_ID : %lu PMA_LOCAL_IF_ID : %lu PMA_DSCP : [dec]\n |
A Hop Channel was Updated. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-5-HOP_CHAN_UPDATE_FAILURE |
5-Notice |
PMA_HOP_ID : %lu PMA_DEST_SITE_ID : %lu PMA_REMOTE_IF_ID : %lu PMA_LOCAL_IF_ID : %lu PMA_DSCP : [dec]\n |
A Hop Channel failed to be updated. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-5-PMA_UP |
5-Notice |
PMA is Up.\n |
PMA is Up. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-5-RLOC_DEREGISTER |
5-Notice |
PMA_INTERFACE_ID : %lu\n |
An Rloc was Deregistered. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-5-RLOC_DOWN |
5-Notice |
PMA_INTERFACE_ID : %lu\n |
An Rloc went Down. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-5-RLOC_IP_ADDR_CHANGE |
5-Notice |
PMA_INTERFACE_ID : %lu PMA_IF_ADDRESS : [chars]\n |
An Rloc IP Address has Changed. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-5-RLOC_PROP_CHANGED |
5-Notice |
PMA_INTERFACE_ID : [dec] PMA_ESON_STATE : [chars]\n |
An Rloc Property has Changed. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-5-RLOC_REGISTER |
5-Notice |
PMA_INTERFACE_ID : %lu\n |
An Rloc was Registered. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-5-RLOC_UP |
5-Notice |
PMA_INTERFACE_ID : %lu\n |
An Rloc came Up. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-5-SITE_PREFIX_UPDATE |
5-Notice |
PMA_TABLE_ID : [dec] PMA_INSTANCE_ID : [dec] PMA_PFX_ADDR : [chars] PMA_PFX_MSK_LEN : [dec] PMA_PFX_FLAG : [chars]\n |
A Site Prefix is Updated. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-5-TC_UPDATE |
5-Notice |
PMA_TC_ID :[dec] PMA_SRC_ADDR :[chars] PMA_DST_ADDR :[chars] PMA_DSCP :[dec] //PMA_APP_ID :[dec] //PMA_SPI :[dec] PMA_OLD_PATH_COUNT :[dec] PMA_NEW_PATH_COUNT :[dec] PMA_IS_INTNET :[dec]\n |
A Path change is made. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-5-TCP_DOWN |
5-Notice |
TCP EVENT. PMA_SITE_ID :[dec] PMA_TENANT_ID :[dec] PMA_DVC_ID :[dec] PMA_TCP_STATUS :[chars] PMA_PMCS_ADDR :[chars]\n |
TCP is Down. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-5-TCP_UP |
5-Notice |
TCP EVENT. PMA_SITE_ID :[dec] PMA_TENANT_ID :[dec] PMA_DVC_ID :[dec] PMA_TCP_STATUS :[chars] PMA_PMCS_ADDR :[chars]\n |
TCP is Up. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-6-HOP_CHAN_ADD |
6-Information |
PMA_HOP_ID : %lu PMA_DEST_SITE_ID : %lu PMA_REMOTE_IF_ID : %lu PMA_LOCAL_IF_ID : %lu PMA_DSCP : [dec]\n |
A Hop Channel was Added. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-6-HOP_CHAN_DELETE |
6-Information |
PMA_HOP_ID : %lu PMA_DEST_SITE_ID : %lu PMA_REMOTE_IF_ID : %lu PMA_LOCAL_IF_ID : %lu PMA_DSCP : [dec]\n |
A Hop Channel was Deleted. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-6-HOP_CHAN_DELETE_FAILURE |
6-Information |
PMA_HOP_ID : %lu PMA_DEST_SITE_ID : %lu PMA_REMOTE_IF_ID : %lu PMA_LOCAL_IF_ID : %lu PMA_DSCP : [dec]\n |
A Hop Channel failed to be deleted. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-7-PREFIX_TO_SITE_ADD |
7-Debug |
PMA_TABLE_ID : [dec] PMA_INSTANCE_ID : [dec] PMA_PFX_ADDR : [chars] PMA_PFX_MSK_LEN : [dec] PMA_PFX_FLAG : [chars]\n |
A Dst Prefix to SiteID is Added. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-7-PREFIX_TO_SITE_DELETE |
7-Debug |
PMA_TABLE_ID : [dec] PMA_INSTANCE_ID : [dec] PMA_PFX_ADDR : [chars] PMA_PFX_MSK_LEN : [dec]\n |
A Dst Prefix to SiteID is Deleted. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-7-PREFIX_TO_SITE_UPDATE |
7-Debug |
PMA_TABLE_ID : [dec] PMA_INSTANCE_ID : [dec] PMA_PFX_ADDR : [chars] PMA_PFX_MSK_LEN : [dec] PMA_PFX_FLAG : [chars]\n |
A Dst Prefix to SiteID is Updated. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-7-SITE_PREFIX_ADD |
7-Debug |
PMA_TABLE_ID : [dec] PMA_INSTANCE_ID : [dec] PMA_PFX_ADDR : [chars] PMA_PFX_MSK_LEN : [dec] PMA_PFX_FLAG : [chars]\n |
A Site Prefix is Added. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-7-SITE_PREFIX_DELETE |
7-Debug |
PMA_TABLE_ID : [dec] PMA_INSTANCE_ID : [dec] PMA_PFX_ADDR : [chars] PMA_PFX_MSK_LEN : [dec] PMA_PFX_FLAG : [chars]\n |
A Site Prefix is Deleted. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-7-SITE_TO_NH_ADD |
7-Debug |
PMA_DEST_SITE_ID : [dec] PMA_HOP_ID : [dec] PMA_HOP_ID : [dec]\n |
A SiteID to NextHop is Added. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-7-SITE_TO_NH_DELETE |
7-Debug |
PMA_DEST_SITE_ID : [dec] PMA_HOP_ID : [dec] PMA_HOP_ID : [dec]\n |
A SiteID to NextHop is Deleted. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-7-SITE_TO_NH_UPDATE |
7-Debug |
PMA_DEST_SITE_ID : [dec] PMA_HOP_ID : [dec] PMA_HOP_ID : [dec]\n |
A SiteID to NextHop is Updated. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-7-TC_ADD |
7-Debug |
PMA_TC_ID :[dec] PMA_SRC_ADDR :[chars] PMA_DST_ADDR :[chars] PMA_DSCP :[dec] //PMA_APP_ID :[dec] //PMA_SPI :[dec] PMA_IS_INTNET :[dec]\n |
A Traffic Class is Added. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-7-TC_AGE_OUT |
7-Debug |
PMA_TC_ID :[dec] PMA_SRC_PFX :[chars] PMA_DST_PFX :[chars] PMA_DSCP :[dec]\n |
A Traffic Class is Aged Out. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-7-TC_DELETE |
7-Debug |
PMA_TC_ID :[dec] PMA_SRC_ADDR :[chars] PMA_DST_ADDR :[chars] PMA_DSCP :[dec] //PMA_APP_ID :[dec] //PMA_SPI :[dec] PMA_IS_INTNET :[dec]\n |
A Traffic Class is Deleted. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-7-TC_REQ |
7-Debug |
PMA_SRC_ADDR :[chars] PMA_DST_ADDR :[chars] PMA_DSCP :[dec] //PMA_APP_ID :[dec] //PMA_SPI :[dec] PMA_IS_INTNET :[dec]\n |
A Traffic Class is Requested. |
pathmgr |
LOG_STD_NO_ACTION |
|
PM_AGENT-7-TEST |
7-Debug |
[chars] |
- |
- |
- |
|
PM_ISSU-3-BUFFER |
3-Error |
Port Manager ISSU client failed to get buffer for message error [dec] |
Port Manager ISSU client failed to get buffer for building\n\ a negotiation message. Hence it can send the negotiation\n\ message to the standby unit. When there is a problem in\n\ the negotiaiton the standby unit can not be brought up. |
pm |
"show logging and show checkpoint client" |
|
PM_ISSU-3-CAP_INVALID_SIZE |
3-Error |
Port Manager ISSU client capability list is empty. |
The Port Manager ISSU client capability exchange list size\n\ is invalid. |
pm |
"show issu capability entries <Client_ID>" |
|
PM_ISSU-3-CAP_NOT_COMPATIBLE |
3-Error |
Port Manager ISSU client capability exchange result incompatible. |
The Port Manager ISSU client capability exchange has negotiated\n\ as incompatible with the peer. |
pm |
"show issu negotiated capability <Session_ID>" |
|
PM_ISSU-3-CAPABILITY |
3-Error |
Port Manager ISSU client [chars] |
Port Manager ISSU client observed an error during capability\n\ negotiaiton. When this error happens there is a mismatch\n\ between the client capability between the active and\n\ standby unit. |
pm |
"show issu capability entries <client_id> and \n\ show issu session <client_id> and \n\ show issu negotiated capability <session_id>" |
|
PM_ISSU-3-INIT |
3-Error |
Port Manager ISSU client initialization failed at [chars] error [chars] |
Port Manager ISSU client could not be initiailzed this will\n\ cause catstrophic failure when ISSU upgrade or downgrade\n\ is performed. |
pm |
LOG_STD_SH_TECH_ACTION |
|
PM_ISSU-3-MSG_NOT_OK |
3-Error |
Port Manager ISSU client message [dec] is not compatible |
Port Manager ISSU client received an incompatible message\n\ from the peer unit. Since the message is not compatible\n\ it can be processed by this unit |
pm |
"show issu message group <client_id> and\n\ show issu session <client_id> and \n\ show issu negotiated version <session_id>" |
|
PM_ISSU-3-MSG_SIZE |
3-Error |
Port Manager ISSU client failed to get the message size for message [dec] |
Port Manager ISSU client failed to calculate message size\n\ for the message specified. The PM ISSU client will not\n\ be able to send message to the standby unit. |
pm |
"show issu message group <client_id> and\n\ show issu session <client_id> and \n\ show issu negotiated version <session_id>" |
|
PM_ISSU-3-POLICY |
3-Error |
Port Manager ISSU client message type [dec] is [chars] |
Port Manager ISSU client received an message type which it\n\ does not support. The policy is applied to make the session\n\ compatible. |
pm |
"show issu session <client_id>" |
|
PM_ISSU-3-SEND_FAILED |
3-Error |
Port Manager ISSU client failed to send a negotiation message error [dec] |
Port Manager ISSU client could not send a session negotiation\n\ message to the peer. When there is a problem in the \n\ negotiation the standby unit can not be brought up. |
pm |
"show logging and show checkpoint client" |
|
PM_ISSU-3-SESSION |
3-Error |
Port Manager ISSU client [chars] |
Port Manager ISSU client observed an error during a session\n\ negotiation with the peer unit. When there is a problem\n\ with the session the standby unit can not be brought up. |
pm |
"show issu capability entries <client_id> and \n\ show issu session <client_id> and \n\ show issu negotiated capability <session_id>" |
|
PM_ISSU-3-SESSION_UNREGISTRY |
3-Error |
Port Manager ISSU client failed to unregister session information. Error: [dec] [chars] |
The Port Manager ISSU client failed to unregister session information. |
pm |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
PM_ISSU-3-TRANSFORM |
3-Error |
Port Manager ISSU client [chars] transform failed error [chars] |
Port Manager ISSU client could not transform the message.\n\ If the transmit transformation failed it means that the\n\ checkpoint message can not be sent to the standby unit.\n\ If the receive transformation failed it means that the\n\ checkpoint message can not be applied on the standby\n\ unit. In both cases the Port Manager state will not\n\ be indentical with the active unit. |
pm |
"show issu session <client_id> and \n\ show issu negotiated version <session_id>" |
|
PM_MODEM_HIST-7-CSM_IC_CALLED_NUM |
7-Debug |
\n[chars]: ISDN incoming called number: [chars] |
This is a tracing message indicating the number of the ISDN\n\ line recieving a call. |
- |
LOG_STD_DBG_ACTION |
|
PM_MODEM_HIST-7-CSM_IC_CALLING_NUM |
7-Debug |
\n[chars]: ISDN incoming caller number: [chars] |
This is a tracing message indicating the number of an incoming\n\ ISDN caller. |
- |
LOG_STD_DBG_ACTION |
|
PM_MODEM_HIST-7-CSM_OC_CALLED_NUM |
7-Debug |
\n[chars]: ISDN outgoing called number: [chars] |
This is a tracing message indicating a dialed ISDN number. |
- |
LOG_STD_DBG_ACTION |
|
PM_MODEM_HIST-7-MODEM_DYNAMIC_EVT |
7-Debug |
\n[chars]: [chars] \n[chars] |
This is a tracing message indicating a dynamic event reported by\n\ the specified modem. |
- |
LOG_STD_DBG_ACTION |
|
PM_MODEM_HIST-7-MODEM_END_CONN_EVT |
7-Debug |
\n[chars]: [chars] \n[chars] |
This is a tracing message indicating an end-connection event\n\ from the specified modem. |
- |
LOG_STD_DBG_ACTION |
|
PM_MODEM_HIST-7-MODEM_ROS_EVT |
7-Debug |
\n[chars]: [chars] \n[chars] |
This is a tracing message indicating a link rate event reported by\n\ the specified modem. |
- |
LOG_STD_DBG_ACTION |
|
PM_MODEM_HIST-7-MODEM_STATE_EVT |
7-Debug |
\n[chars]: [chars] \n%*s State: [chars] |
This is a tracing message indicating a state event reported by\n\ the specified modem. |
- |
LOG_STD_DBG_ACTION |
|
PM_MODEM_HIST-7-MODEM_STATIC_EVT |
7-Debug |
\n[chars]: [chars] \n[chars] |
This is a tracing message indicating a static event reported by\n\ the specified modem. |
- |
LOG_STD_DBG_ACTION |
|
PM_MODEM_HIST-7-PORT_STATE_REACHED_NTF_EVT |
7-Debug |
\n[chars]: [chars] [chars] |
This is a tracing message indicating a link rate event reported by\n\ the specified modem. |
- |
LOG_STD_DBG_ACTION |
|
PM_MODEM_HIST-7-TRACE_HDR |
7-Debug |
\n\nModem [chars] Events Log: |
This is the initial message for the trace of the specified modem.\n\ The modem's stored trace messages will follow. |
- |
LOG_STD_DBG_ACTION |
|
PM_MODEM_HIST-7-UNKNOWN_EVENT |
7-Debug |
\n[chars]: Error in events log |
This is a tracing message indicating a formatting error in the\n\ modem event history. One or more events may be missing from\n\ the trace. |
- |
LOG_STD_DBG_ACTION |
|
PM_MODEM_HIST-7-UNKNOWN_FRAME |
7-Debug |
\n[chars]: Error in events log |
This is a tracing message indicating a formatting error in the\n\ modem event history. One or more events may be missing from\n\ the trace. |
- |
LOG_STD_DBG_ACTION |
|
PM_MODEM_MAINT-1-BADEVENT |
1-Alert |
Invalid modem management [chars] event 0x%02x for modem[chars] |
The modem management facility received an unrecognize event. |
- |
LOG_STD_ACTION |
|
PM_MODEM_MAINT-1-BADMODEM |
1-Alert |
Modem [chars] failed [chars] |
A software or hardware problem has been detected on a modem.\n\ The specific modem and reason are listed in the message. |
- |
LOG_STD_ACTION |
|
PM_MODEM_MAINT-1-INITFAIL |
1-Alert |
Initialization failed. |
Modem maintenance facility initialization failed. |
- |
"Disable Autotest Poweron test and avoid manual back-2-back test." LOG_STD_ACTION |
|
PM_MODEM_MAINT-4-B2BABORT |
4-Warning |
Modems [chars] and [chars] back-to-back test: aborted |
The PM SPE State Machine has run out of event memory. |
port-mgmt |
LOG_STD_ACTION |
|
PM_MODEM_MAINT-4-BADMODEMS |
4-Warning |
Modems [chars] and [chars] failed back-to-back test: [chars] |
The two modems reported in the message failed a back-to-back test.\n\ At least one of them has failed. |
- |
"Perform more back to back tests by pairing the failed modems with\n\ other modems to determine which modem is bad. Check the failed\n\ modems again after performing a power cycle. " LOG_STD_RECUR_ACTION |
|
PM_MODEM_MAINT-5-B2BCONNECT |
5-Notice |
Modems [chars] and [chars] connected in back-to-back test: [chars] |
A back to back test connection has been made between the selected\n\ modems. The test is still in progress. |
- |
LOG_STD_NO_ACTION |
|
PM_MODEM_MAINT-5-B2BINIT |
5-Notice |
Auto Back-to-Back test initiated by [chars] |
This is a tracing message indicating an automatic back-to-back\n\ test was initiated by the specified MICA modem. |
- |
LOG_STD_DBG_ACTION |
|
PM_MODEM_MAINT-5-B2BMODEMS |
5-Notice |
Modems [chars] and [chars] completed back-to-back test: |
The reported modems have passed the back to back test without any\n\ errors. |
- |
LOG_STD_NO_ACTION |
|
PM_MODEM_MAINT-5-MODEM_OK |
5-Notice |
Modem [chars] passed the test |
Tests on the specified modem were successful. |
- |
LOG_STD_NO_ACTION |
|
PM_PVLAN_ISSU-3-BUFFER |
3-Error |
Private Vlan ISSU client failed to get buffer for message error [dec] |
Private Vlan ISSU client failed to get buffer for building\n\ a negotiation message. Hence it can send the negotiation\n\ message to the standby unit. When there is a problem in\n\ the negotiaiton the standby unit can not be brought up. |
c7600-l2 |
"show logging and show checkpoint client" |
|
PM_PVLAN_ISSU-3-CAPABILITY |
3-Error |
Private Vlan ISSU client [chars] |
Private Vlan ISSU client observed an error during capability\n\ negotiaiton. When this error happens there is a mismatch\n\ between the client capability between the active and\n\ standby unit. |
c7600-l2 |
"show issu capability entries <client_id> and \n\ show issu session <client_id> and \n\ show issu negotiated capability <session_id>" |
|
PM_PVLAN_ISSU-3-INIT |
3-Error |
pm_pvlan Client Name ISSU client initialization failed at [chars] error [chars] |
pm_pvlan Client Name ISSU client could not be initiailzed this will\n\ cause catstrophic failure when ISSU upgrade or downgrade\n\ is performed. |
c7600-l2 |
LOG_STD_SH_TECH_ACTION |
|
PM_PVLAN_ISSU-3-MSG_NOT_OK |
3-Error |
Private Vlan ISSU client message [dec] is not compatible |
Private Vlan ISSU client received an incompatible message\n\ from the peer unit. Since the message is not compatible\n\ it can be processed by this unit |
c7600-l2 |
"show issu message group <client_id> and\n\ show issu session <client_id> and \n\ show issu negotiated version <session_id>" |
|
PM_PVLAN_ISSU-3-MSG_SIZE |
3-Error |
Private Vlan ISSU client failed to get the message size for message [dec] |
Private Vlan ISSU client failed to calculate message size\n\ for the message specified. The OIR ISSU client will not\n\ be able to send message to the standby unit. |
c7600-l2 |
"show issu message group <client_id> and\n\ show issu session <client_id> and \n\ show issu negotiated version <session_id>" |
|
PM_PVLAN_ISSU-3-POLICY |
3-Error |
Private Vlan ISSU client message type [dec] is [chars] |
Private Vlan ISSU client received an message type which it\n\ does not support. The policy is applied to make the session\n\ compatible. |
c7600-l2 |
"show issu session <client_id>" |
|
PM_PVLAN_ISSU-3-SEND_FAILED |
3-Error |
Private Vlan ISSU client failed to send a negotiation message error [dec] |
Private Vlan ISSU client could not send a session negotiation\n\ message to the peer. When there is a problem in the \n\ negotiation the standby unit can not be brought up. |
c7600-l2 |
"show logging and show checkpoint client" |
|
PM_PVLAN_ISSU-3-SESSION |
3-Error |
Private Vlan ISSU client [chars] |
Private Vlan ISSU client observed an error during a session\n\ negotiation with the peer unit. When there is a problem\n\ with the session the standby unit can not be brought up. |
c7600-l2 |
"show issu capability entries <client_id> and \n\ show issu session <client_id> and \n\ show issu negotiated capability <session_id>" |
|
PM_PVLAN_ISSU-3-TRANSFORM |
3-Error |
Private Vlan ISSU client [chars] transform failed error [chars] |
Private Vlan ISSU client could not transform the message.\n\ If the transmit transformation failed it means that the\n\ checkpoint message can not be sent to the standby unit.\n\ If the receive transformation failed it means that the\n\ checkpoint message can not be applied on the standby\n\ unit. In both cases the pm_pvlan Client Name state will not\n\ be indentical with the active unit. |
c7600-l2 |
"show issu session <client_id> and \n\ show issu negotiated version <session_id>" |
|
PM-1-INCONSISTENT_PORT_STATE |
1-Alert |
Inconsistent HW/SW port state for [chars]. Please shut/no shut the interface |
The hardware and software port state has become inconsistent. |
pm |
"Enter the <CmdBold>shutdown<CmdBold> command followed by the\n\ <CmdBold>no shutdown<CmdBold> command on the interface specified in\n\ the message." |
|
PM-2-LOW_SP_MEM |
2-Critical |
Switch process available memory is less than [dec] bytes |
Switch Processor available memory dropped to a low level. Possibly\n\ too many Layer 2 VLANs are configured in the system. |
pm |
"Removed features from the system to reduce memory usage." |
|
PM-2-NOMEM |
2-Critical |
Not enough memory available for [chars] |
The Port Manager subsystem could not obtain the memory it needed. |
pm |
LOG_STD_SH_TECH_ACTION |
|
PM-2-VLAN_ADD |
2-Critical |
Failed to add VLAN [dec] - [chars]. |
Failed in adding VLAN to VTP. The reason is stated in the string. |
pm |
LOG_STD_SH_TECH_ACTION |
|
PM-3-ERR_INCOMP_PORT |
3-Error |
[dec]/[dec] is set to inactive because [dec]/[dec] is a [chars] port |
Private host port can't be configured with trunk private promiscuous and span destination port on the same coil. |
- |
"Try to configure the incompatible ports on different coils." |
|
PM-3-INTERNALERROR |
3-Error |
Port Manager Internal Software Error [chars]: [chars]: [dec]: [chars] |
There is an internal software error encountered in the IOS Port Manager. |
pm |
LOG_STD_ACTION |
|
PM-4-BAD_APP_ID |
4-Warning |
an invalid application id [dec] was detected |
An invalid request was detected by the Port Manager. |
pm |
LOG_STD_SH_TECH_ACTION |
|
PM-4-BAD_APP_REQ |
4-Warning |
an invalid [chars] request by the '[chars]' application was detected |
An invalid request was detected by the Port Manager. |
pm |
LOG_STD_SH_TECH_ACTION |
|
PM-4-BAD_CARD_COOKIE |
4-Warning |
an invalid card cookie was detected |
An invalid request was detected by the Port Manager. |
pm |
LOG_STD_SH_TECH_ACTION |
|
PM-4-BAD_CARD_SLOT |
4-Warning |
an invalid card slot [dec] was detected |
An invalid request was detected by the Port Manager. |
pm |
LOG_STD_SH_TECH_ACTION |
|
PM-4-BAD_COOKIE |
4-Warning |
[chars] was detected |
An invalid request was detected by the Port Manager. |
pm |
LOG_STD_SH_TECH_ACTION |
|
PM-4-BAD_HA_ENTRY_EVENT |
4-Warning |
Invalid Host access entry event [dec] is received |
Host access table is entry event is not any of add/delete/update event |
pm |
LOG_STD_SH_TECH_ACTION |
|
PM-4-BAD_PORT_COOKIE |
4-Warning |
an invalid port cookie was detected |
An invalid request was detected by the Port Manager. |
pm |
LOG_STD_SH_TECH_ACTION |
|
PM-4-BAD_PORT_NUMBER |
4-Warning |
an invalid port number [dec] was detected |
An invalid request was detected by the Port Manager. |
pm |
LOG_STD_SH_TECH_ACTION |
|
PM-4-BAD_VLAN_COOKIE |
4-Warning |
an invalid vlan cookie was detected |
An invalid request was detected by the Port Manager. |
pm |
LOG_STD_SH_TECH_ACTION |
|
PM-4-BAD_VLAN_ID |
4-Warning |
an invalid vlan id [dec] was detected |
An invalid request was detected by the Port Manager. |
pm |
LOG_STD_SH_TECH_ACTION |
|
PM-4-EC_MEM_CFG_UNSUPPORTED |
4-Warning |
Port [chars] is etherchannel member port and not supported on [chars] SPAN session as source ports. Removal and Reconfiguration of SPAN session needed |
Etherchannel Member ports are not supported as Local SPAN source |
bigbang-l2 |
"Remove existing SPAN session and Reconfiguration needed" |
|
PM-4-EC_MEM_DST_CFG_UNSUPPORTED |
4-Warning |
Port [chars] is etherchannel member port and not supported on SPAN session as destination port. Removal and Reconfiguration of SPAN session needed |
Etherchannel Member ports are not supported as Local SPAN destination |
bigbang-l2 |
"Remove existing SPAN session and Reconfiguration needed" |
|
PM-4-ERR_DISABLE |
4-Warning |
[chars] error detected on [chars] putting [chars] in err-disable state |
This is a defensive measure that will put the interface in err-disable state when it detects a mis-configuration or mis-behavior . A recovery will be attempted after the configured retry time default 5 minutes. |
pm |
LOG_STD_SH_TECH_ACTION |
|
PM-4-ERR_DISABLE_VP |
4-Warning |
[chars] error detected on [chars] vlan [dec]. Putting in err-disable state. |
This is a defensive measure that will put the virtual port i.e. the port-vlan pair in err-disable state when it detects a mis-configuration or |
pm |
LOG_STD_SH_TECH_ACTION |
|
PM-4-ERR_RECOVER |
4-Warning |
Attempting to recover from [chars] err-disable state on [chars] |
This is an attempt to bring the interface back after taking it down to\n\ err-disable state |
pm |
LOG_STD_SH_TECH_ACTION |
|
PM-4-ERR_RECOVER_VP |
4-Warning |
Attempting to recover from [chars] err-disable state on [chars] vlan [dec]. |
This is an attempt to bring the virtual port back after taking it down to err-disable state |
pm |
LOG_STD_SH_TECH_ACTION |
|
PM-4-EXT_VLAN_INUSE |
4-Warning |
VLAN [dec] currently in use by [chars] |
Port Manager failed to allocate the VLAN for external use as the VLAN\n\ is currently occupied by another feature |
pm |
- |
|
PM-4-EXT_VLAN_NOTAVAIL |
4-Warning |
VLAN [dec] not available in Port Manager |
Port Manager failed to allocate the requested VLAN.\n\ The VLAN is either used as an internal VLAN by other features or the\n\ maximum allowed extended VLANs are already configured. |
pm |
"Try a different VLAN on the device if the limit on maximum allowed\n\ extended VLANs is not yet reached." |
|
PM-4-INACTIVE |
4-Warning |
putting [chars] in inactive state because [chars] |
The Port Manager has been blocked from creating a virtual port for the switch port and VLAN causing the port to be in an inactive state. The reason for this condition is specified in the error message. |
pm |
LOG_STD_SH_TECH_ACTION |
|
PM-4-INT_FAILUP |
4-Warning |
[chars] failed to come up. No internal VLAN available |
Port Manager failed to allocate internal VLAN and thus the interface\n\ cannot come up. |
pm |
"Remove extended range VLAN to free up resouces." |
|
PM-4-INT_VLAN_NOTAVAIL |
4-Warning |
Failed to allocate internal VLAN in Port Manager |
Port Manager failed to find any available internal VLAN |
pm |
"Delete some extened range VLANs created by users or remove some features\n\ that require internal VLAN allocation e.g. routed port" |
|
PM-4-INVALID_HOST_ACCESS_ENTRY |
4-Warning |
Invalid Host access entry type [dec] is received |
Host access entry should be one of configured/dynamic type |
pm |
LOG_STD_SH_TECH_ACTION |
|
PM-4-LIMITS |
4-Warning |
The number of vlan-port instances on [chars] exceeded the recommended limit of [dec] |
- |
- |
"Reduce the number of trunks and VLANs configured in the module " "or switch specified in the error message. Keep the virtual port " "VLAN port count below the recommended limit specified in " "the configuration documentation. Enter the <CmdBold>show " "interface trunk<NoCmdBold> command to see the total number of trunks " "and VLANs." |
|
PM-4-MPLS_MTU_EC_CFG |
4-Warning |
MPLS MTU size [dec] is not supported by one or more ports in channel [chars]. |
Port Manager on Standby discovered that the port state has been \n\ inconsistent for more that 1 second. Inconsistent ports are reactivated\n\ on switchover you will see PORT_BOUNCED message. |
pm |
LOG_STD_NO_ACTION |
|
PM-4-MPLS_MTU_PORT_CFG |
4-Warning |
MPLS MTU size [dec] is not supported by port [chars]. |
The MPLS MTU size configured on the port is larger than the maximum MTU size that can be supported by this port. As a result large packets can be dropped. |
pm |
"Reduce the MPLS MTU size." |
|
PM-4-NO_SUBBLOCK |
4-Warning |
No PM subblock found for [chars] |
Failed to find PM subblock for this interface. |
pm |
LOG_STD_SH_TECH_ACTION |
|
PM-4-PORT_BOUNCED |
4-Warning |
Port [chars] was bounced by [chars]. |
The Port Manager needed to perform a reactivation of a port in the\n\ link down state during a switchover. A port is only reactivated when the\n\ port data structures lack consistency between the active and standby\n\ supervisors. Active ports in the link down state were returned to the\n\ link up state by the reactivation event. |
pm |
LOG_STD_NO_ACTION |
|
PM-4-PORT_CONSISTENT |
4-Warning |
Port [chars] consistency has been restored IDB state: [chars]. |
Port Manager on Standby discovered that port state became consistent \n\ again. |
pm |
LOG_STD_NO_ACTION |
|
PM-4-PVLAN_TYPE_CFG_ERR |
4-Warning |
Failed to set VLAN [dec] to a [chars] VLAN |
Platform failed to set private vlan type. |
pm |
LOG_STD_SH_TECH_ACTION |
|
PM-4-TOO_MANY_APP |
4-Warning |
application '[chars]' exceeded registration limit |
An invalid request was detected by the Port Manager. |
pm |
LOG_STD_SH_TECH_ACTION |
|
PM-4-UNKNOWN_HOST_ACCESS |
4-Warning |
Invalid Host access value [dec] is received |
Host access table is being accesses with an invalalid host access value |
pm |
LOG_STD_SH_TECH_ACTION |
|
PM-4-VMPS_CFG |
4-Warning |
Dynamic access VLAN [dec] same as voice vlan on [chars]. |
Access VLAN on VMPS server is set to same VLAN as voice VLAN on the\n\ port. |
pm |
"Access VLAN assignment on VMPS server should be different from voice\n\ VLAN." |
|
PM-6-EXT_VLAN_ADDITION |
6-Information |
Extended VLAN is not allowed to be configured in VTP CLIENT mode. |
This message will only be seen if you try to configure an extended\n\ VLAN while the switch is in VTP client mode. The configuration will\n\ fail and will not be written to the runnning configuration file but\n\ otherwise switch performance and features will be unaffected. |
pm |
"This is an informational message only no further action is required.\n\ If you need to configure an extended VLAN you must configure the switch\n\ to leave VTP client mode." |
|
PMDWDM-4-TCA |
4-Warning |
[chars]: [chars] [chars] [chars] value %lld threshold %lld [chars] |
The specified PM FEC TCA has been declared or released |
g709-dwdm |
"Recommended action is to repair the source of the alarm." |
|
PMIPV6-5-TUNNELDELETE |
5-Notice |
Deleting the Proxy Mobile IPv6 tunnel [chars] |
The PMIPv6 tunnel is being deleted. |
mipv6 |
"If you suspect this condition contact technical\n\ support representative with the output of show tech" |
|
PMIPV6-5-TUNNELUP |
5-Notice |
Bringing up the Proxy Mobile IPv6 tunnel [chars] |
The PMIPv6 tunnel is being deleted. |
mipv6 |
"If you suspect this condition contact technical\n\ support representative with the output of show tech" |
|
PMOD-3-MSG_ERR |
3-Error |
[chars] |
Error Messages |
pagent |
"try debug command" |
|
PMOD-6-MSG_INF |
6-Information |
[chars] |
Program information |
- |
- |
|
PMOD-7-MSG_DBG |
7-Debug |
[chars] |
Debug Messages |
- |
- |
|
PNNI-2-FLOOD_ERROR |
2-Critical |
[chars] |
- |
- |
- |
|
PNNI-2-NO_INTERNAL_NUMBER |
2-Critical |
Empty Internal Number Stack: [chars] |
An internal software error has occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
PNNI-2-SPF_ERROR |
2-Critical |
Tent List Overflow in [chars] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
PNNI-3-INTERNAL_ERROR |
3-Error |
[chars][chars] [hec] |
An internal software error occurred. The message contains more information that can be used to identify the problem. |
- |
LOG_STD_ACTION |
|
PNNI-3-INVALID_MEM |
3-Error |
Bad address of [chars] [hex] please collect \show atm pnni trace error\ |
An internal software error occurred. |
- |
"Use \"show atm pnni trace error\" to collect more information. " LOG_STD_RECUR_ACTION |
|
PNNI-4-ADDRESS_EXIST |
4-Warning |
Address derived from the switch's prefix by soft PVC manager [chars] clashes with existing address in prefix table |
An PVC port address assignment has collided with an existing address. An address that would have been assigned by this switch has already been assigned by another. |
- |
"If possible assign a new MAC address to the peer system that caused the assignment collision." |
|
PNNI-4-ATM_SYS_ERROR |
4-Warning |
Error: [chars] |
An internal software error occurred. |
- |
"LOG_STD_ACTION" |
|
PNNI-4-BADPACKET |
4-Warning |
Invalid [chars] pkt: [chars] [dec] [dec] |
An invalid packet was received from a network peer. |
- |
"Check the originating device for a cause of the corrupted packets." |
|
PNNI-4-BADROUTEREQ |
4-Warning |
Bad Request from Signaling [hec] |
A source routing request by another network host was corrupted. |
- |
"Check the originating system for a cause of the problem." |
|
PNNI-4-CONFIG_ERROR |
4-Warning |
Configuration Error: [chars] |
This message indicates a configuration error in the PNNI subsystem. The message will display more specific information about the cause of problem. |
- |
"Change the confguration to correct the error." |
|
PNNI-4-DUPLICATE_NODE_ID |
4-Warning |
[chars] [chars] for node [dec] [chars] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
PNNI-6-INFO |
6-Information |
[chars] |
This is an informational message only. |
- |
"Informational messages can be disabled by changing logging level." |
|
PNNI-7-DEBUG |
7-Debug |
[chars] |
This is an informational message only. It is used by Cisco for testing. |
- |
"Informational messages can be disabled by changing logging level." |
|
PNP-3-PNP_CCO_PROFILE_UNCONFIGURED |
3-Error |
CCO Server profile [chars] unconfigured [dec]/[dec] by [chars] |
CCO Server profile unconfigured |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-3-PNP_CCO_SERVER_IP_UNRESOLVED |
3-Error |
CCO server [chars] can't be resolved [dec]/[dec] by [chars] |
CCO server can't be resolved |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-3-PNP_CONFIG_ARCHIVE_NOT_SUPPORTED |
3-Error |
PnP config archive not supported [dec]/[dec] on this platform yet [chars] |
PnP config archive not supported on this platform yet |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-3-PNP_CONFIG_ROLLBACK |
3-Error |
Config [chars] rollback [dec]/[dec] reason [chars] by [chars] |
Config rollback |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-3-PNP_CONFIG_ROLLBACK_NOT_SUPPORTED |
3-Error |
PnP config rollback not supported [dec]/[dec] on this platform yet [chars] |
PnP config rollback not supported on this platform yet |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-3-PNP_DHCP_INVALID_PNP_OPTION_NOTIFIED |
3-Error |
DHCP invalid-PnP option [chars] on interface [chars] notified [dec]/[dec] by [chars] |
DHCP invalid-PnP option notified |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-3-PNP_DOMAIN_NAME_NOT_FOUND |
3-Error |
Domain name not found [dec]/[dec] on [chars] by [chars] |
Domain name not found |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-3-PNP_FILE_COPY_FAILED |
3-Error |
File copied to [chars] failed [dec]/[dec] err=[dec] [[chars]] bps=[dec] [dec] bytes in [dec] ms by [chars] |
File copied failed |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-3-PNP_HTTP_TIMED_OUT |
3-Error |
PnP HTTP timed out [dec]/[dec] on connection to PnP server [chars] |
PnP HTTP timed out on connection to PnP server |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-3-PNP_IMAGE_INSTALL_FAILED |
3-Error |
Image [chars] install failed [dec]/[dec] by [chars] |
Image install failed |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-3-PNP_INTERFACE_STILL_DOWN_NOTIFIED |
3-Error |
Interface [chars] still-down notified [dec]/[dec] by [chars] |
Interface still-down notified |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-3-PNP_SERVER_IP_UNRESOLVED |
3-Error |
PnP server [chars] can't be resolved [dec]/[dec] on interface [chars] by [chars] |
PnP server can't be resolved |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-3-PNP_SERVER_STILL_UNREACHABLE_NOTIFIED |
3-Error |
PnP Server still-unreachable notified [dec]/[dec] by [chars] |
PnP Server still-unreachable notified |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-3-PNP_TLS_TUNNEL_STILL_DOWN_NOTIFIED |
3-Error |
TLS-Tunnel [chars] still-down notified [dec]/[dec] by [chars] |
TLS-Tunnel still-down notified |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-3-PNP_TRUSTPOINT_ROLLBACK |
3-Error |
Trustpoint [chars] rollback [dec]/[dec] reason [chars] by [chars] |
Trustpoint rollback |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-3-PNP_UNABLE_TO_COPY_FILE |
3-Error |
Unable to copy from [chars] to [chars]. Error [chars] |
The file transfer operation failed. |
pnpa |
"Check that the source file exists and the file can be accessed " "from the device that tries to access that file." "Also check that the URL for both source and destination " " are correct." |
|
PNP-6-HTTP_CONNECTED |
6-Information |
PnP Discovery connected to PnP server [chars] |
PnP Discovery is now connected to PnP server |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-HTTP_CONNECTING |
6-Information |
PnP Discovery trying to connect to PnP server [chars] |
PnP Discovery is trying to connect to PnP server |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-NAPP_CONFIG |
6-Information |
Command configured: [chars] |
PnP Discovery profile is now configured |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_4G_CONFIG_FAILED |
6-Information |
PnP 4G Dialer configuration failed after [dec] times |
PnP trying to configure 4G Dialer on a cellular interface but failed |
- |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_BACKOFF_EXCEEDS_WARNING_LIMIT |
6-Information |
Requested PnP Backoff time [dec] exceeds warning limit [dec] in seconds |
PnP Backoff time exceeds warning limit |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_BACKOFF_NOW |
6-Information |
PnP Backoff now for [dec] seconds requested [dec]/[dec] by [chars] |
PnP Backoff time |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_BACKOFF_TERMINATE |
6-Information |
PnP Backoff termination requested [dec]/[dec] by [chars] |
PnP Backoff termination |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_BEST_UDI_UPDATE |
6-Information |
Best UDI [[chars]] identified via [chars] |
Best UDI is identified |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_CCO_SERVER_IP_RESOLVED |
6-Information |
CCO server [chars] resolved to ip [chars] by [chars] |
CCO server ip resolved |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_CDP_FAILED |
6-Information |
Failed to identify Device UDI for CDP [dec]/[dec] |
Failed to identify Device UDI for CDP |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_CDP_UPDATE |
6-Information |
Device UDI [[chars]] identified for CDP |
Device UDI is identified for CDP |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_CFG_REG_IGNORE_STARTUP_IS_SET |
6-Information |
Config register ignore startup config is set PNP won't work |
Config register ignore startup config is set PNP won't work |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_CONFIG_ARCHIVE |
6-Information |
Config [chars] archive [dec]/[dec] by [chars] |
Config archive |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_DHCP_DISABLED_WHEN_NOTIFIED |
6-Information |
DHCP option [chars] on interface [chars] disabled when notified [dec]/[dec] by [chars] |
DHCP option disabled when notified |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_DHCP_NON_PNP_OPTION_NOTIFIED |
6-Information |
DHCP non-PnP option [chars] on interface [chars] notified [dec]/[dec] by [chars] |
DHCP non-PnP option notified |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_DHCP_VALID_PNP_OPTION_NOTIFIED |
6-Information |
DHCP valid-PnP option [chars] on interface [chars] notified [dec]/[dec] by [chars] |
DHCP valid-PnP option notified |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_DISCOVERY_ABORT_ON_CLI |
6-Information |
PnP Discovery abort on CLI input |
PnP Discovery abort on CLI input |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_DISCOVERY_ABORT_ON_VDAEMON |
6-Information |
PnP Discovery abort on vdaemon input |
PnP Discovery has aborted on vdaemon input |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_DISCOVERY_ABORT_ON_VIPTELA_STARTUP |
6-Information |
PnP Discovery abort on Viptela startup config |
PnP Discovery abort on Viptela startup config |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_DISCOVERY_DONE |
6-Information |
PnP Discovery done successfully [chars] profile [chars] via [chars] [chars] |
PnP Discovery done successfully |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_DISCOVERY_NOT_RUNNING |
6-Information |
PNP Discovery is not running |
PNP Discovery is not running |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_DISCOVERY_STARTED |
6-Information |
PnP Discovery started |
PnP Discovery started |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_DISCOVERY_STOPPED |
6-Information |
PnP Discovery stopped [chars] |
PnP Discovery stopped |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_DISCOVERY_STOPPING |
6-Information |
Stopping PnP Discovery. Please do not interrupt |
Stopping PnP Discovery |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_DISCOVERY_WAITING_ON_SDWAN_TRIGGER |
6-Information |
PnP Discovery waiting for SDWAN Trigger |
PnP Discovery waiting for SDWAN Trigger |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_DNS_SERVER_SET |
6-Information |
DNS server [chars] set by [chars] |
DNS server set |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_DOMAIN_NAME_SET |
6-Information |
Domain name [chars] set on [chars] by [chars] |
Domain name set |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_FILE_COPY_DONE |
6-Information |
File copied to [chars] done [dec]/[dec] bps=[dec] [dec] bytes in [dec] ms by [chars] |
File copied done |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_GOOD_UDI_UPDATE |
6-Information |
Good UDI [[chars]] identified via [chars] |
Gest UDI is identified |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_IMAGE_INSTALL_ABORTED_DUE_TO_BUNDLE_MODE |
6-Information |
PNP Image install aborted due to Bundle mode needs Install mode |
PNP Image install aborted due to Bundle mode needs Install mode |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_IMAGE_INSTALL_ABORTED_DUE_TO_MANUAL_BOOT |
6-Information |
PNP Image install aborted due to Manual boot needs Auto boot |
PNP Image install aborted due to Manual boot needs Auto boot |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_IMAGE_INSTALLED_WITH_RELOAD_SCHEDULED |
6-Information |
Image [chars] installed with reload scheduled [dec]/[dec] by [chars] |
Image installed with reload scheduled |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_IMAGE_INSTALLED_WITHOUT_RELOAD |
6-Information |
Image [chars] installed without reload [dec]/[dec] by [chars] |
Image installed without reload |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_IPV4_RESOLVED_BY |
6-Information |
IPv4 resolved on interface [chars] by [chars] |
IPv4 resolved on interface |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_IPV6_RESOLVED_BY |
6-Information |
IPv6 resolved on interface [chars] by [chars] |
IPv6 resolved on interface |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_LOCATION_TAG_CHANGED |
6-Information |
PnP Location Tag Changed [chars] |
PnP Location Tag changed |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_LOCATION_TAG_REMOVED |
6-Information |
PnP Location Tag Removed |
PnP Location Tag removed |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_MODE_CHANGE_FAILED |
6-Information |
Mode change failed. Use CLI to change mode |
Mode change failed |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_MODE_CHANGE_IN_PROGRESS |
6-Information |
Mode change in progress |
Mode change in progress |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_MODE_CHANGE_OK |
6-Information |
Mode change successful device will reload now |
Mode change successful device will reload now |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_MONITOR_ACTION_DONE |
6-Information |
PnP Monitor action #[dec] [chars] done for watched event [chars] notified by [chars] at [chars] reason [chars] |
PnP Monitor action done for watched event |
- |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_MONITOR_ACTION_FAILED |
6-Information |
PnP Monitor action #[dec] [chars] failed for watched event [chars] notified by [chars] at [chars] reason [chars] |
PnP Monitor action failed for watched event |
- |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_MONITOR_EVENT_NOTIFIED |
6-Information |
PnP Monitor event #[dec] [chars] notified by [chars] at [chars] reason [chars] |
PnP Monitor received event notification |
- |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_MONITOR_EVENT_NOTIFIED_WITH_PROGRESS |
6-Information |
PnP Monitor event #[dec] [chars] notified by [chars] at [chars] reason [chars] progress [dec]%% |
PnP Monitor received event notification with progress percentage |
- |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_MONITOR_WATCH_DISABLED |
6-Information |
PnP Monitor event [chars] watch [chars] disabled [dec]/[dec] by [chars] |
PnP Monitor watch disabled |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_MONITOR_WATCH_ENABLED |
6-Information |
PnP Monitor event [chars] watch [chars] enabled [dec]/[dec] by [chars] |
PnP Monitor watch enabled |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_PROFILE_CREATED |
6-Information |
PnP profile [chars] created [dec]/[dec] by [chars] |
PnP profile created |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_PROFILE_DELETED |
6-Information |
PnP profile [chars] deleted [dec]/[dec] by [chars] |
PnP profile created |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_PROVISION_DONE |
6-Information |
PnP Provision done successfully [chars] |
PnP Provision done successfully |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_PROVISION_STATE_NOTIFIED |
6-Information |
PnP Provision state notified [chars] |
PnP Provision state notified |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_PYTHON_SCRIPT_DONE |
6-Information |
Python script [chars] done [dec]/[dec] via [chars] by [chars] |
Python script done |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_REDIRECTION_DONE |
6-Information |
PnP Redirection done [dec] by [chars] |
PnP Redirection done |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_RELOAD_INFO_ENCODED |
6-Information |
Reload reason [chars]-[chars] encoded [dec]/[dec] by [chars] |
Reload reason encoded |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_RELOAD_INFO_STOPPED |
6-Information |
Reload reason [chars]-[chars] stopped by [chars] |
Reload reason stopped |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_RESET_DONE |
6-Information |
PnP reset done |
PnP reset successful |
- |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_RESET_FAILED |
6-Information |
Having problem with PnP reset. Try it later. |
Failed to do PnP reset |
- |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_SAVING_TECH_SUMMARY |
6-Information |
Saving PnP tech summary [chars]... Please wait. Do not interrupt. |
PnP saving tech summary to default disk |
- |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_SCRIPT_STARTED |
6-Information |
Script [chars] started [dec]/[dec] via [chars] by [chars] |
Script started |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_SDWAN_READY |
6-Information |
PnP SDWAN ready [dec] notified by [chars] |
PnP SDWAN ready |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_SDWAN_STARTED |
6-Information |
PnP SDWAN started [dec] via [chars] by [chars] |
PnP SDWAN started |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_SDWAN_STOPPED |
6-Information |
PnP SDWAN stopped [dec] reason [chars] by [chars] |
PnP SDWAN stopped |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_SERVER_IP_RESOLVED |
6-Information |
PnP server [chars] resolved to ip [chars] on interface [chars] by [chars] |
PnP server ip resolved |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_SUDI_UPDATE |
6-Information |
Device SUDI [[chars]] identified |
Device SUDI is identified |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_TCL_SCRIPT_DONE |
6-Information |
TCL script [chars] done [dec]/[dec] via [chars] by [chars] |
TCL script done |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_TECH_SUMMARY_FAILED_TO_SAVE |
6-Information |
Having problems saving PnP tech summary [chars] elapsed time: [dec] seconds. |
Failed to save PnP tech summary to default disk |
pnpa |
"Make sure that the default disk has reasonable free space." " Also never interrupt the PnP tech summary saving in any way e.g." " enable the device console or change any device config or resource." |
|
PNP-6-PNP_TECH_SUMMARY_SAVED_OK |
6-Information |
PnP tech summary [chars] saved successfully elapsed time: [dec] seconds. |
PnP tech summary saved to default disk successfully |
- |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_TECH_SUMMARY_SAVED_WITH_ALARM |
6-Information |
PnP tech summary [chars] saved with alarm [dec]/[dec] elapsed time: [dec] seconds. |
PnP tech summary saved to default disk successfully but with some issues |
pnpa |
"Make sure that all disks can be recursively listed in resonably short time." " Also never interrupt the PnP tech summary saving in any way e.g." " enable the device console or change any device config or resource." |
|
PNP-6-PNP_TLS_TUNNEL_DOWN_NOTIFIED |
6-Information |
TLS-Tunnel [chars] down notified [dec]/[dec] by [chars] |
TLS-Tunnel down notified |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_TLS_TUNNEL_UP_NOTIFIED |
6-Information |
TLS-Tunnel [chars] up notified [dec]/[dec] by [chars] |
TLS-Tunnel down notified |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_TRUSTPOINT_INSTALLED |
6-Information |
Trustpoint [chars] installed from [chars] by [chars] |
Trustpoint installed |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PNP_TRUSTPOOL_INSTALLED |
6-Information |
Trustpool installed from [chars] by [chars] |
Trustpool installed |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-PROFILE_CONFIG |
6-Information |
PnP Discovery profile [chars] configured |
PnP Discovery profile is now configured |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-XMPP_CONNECTED |
6-Information |
PnP Discovery connected to PnP server [chars] port [dec] |
PnP Discovery is now connected to PnP server |
pnpa |
LOG_STD_NO_ACTION |
|
PNP-6-XMPP_CONNECTING |
6-Information |
PnP Discovery trying to connect to PnP server [chars] port [dec] |
PnP Discovery is trying to connect to PnP server |
- |
LOG_STD_NO_ACTION |
|
POLICY_API-3-SBINIT |
3-Error |
Error initializing [chars] subblock data structure. [chars] |
Initialization of the specified subblock data structure could not be accomplished. |
- |
- |
|
POLICY_API-4-POLICYDYNCLR |
4-Warning |
Dynamic policy on intf:[chars] cleared. Static policy in use. |
A dynamic policy was overriding the static policy.\n\ The dynamic policy has been cleared the static policy\n\ is now in effect. |
- |
"No action required." |
|
POLICY_API-4-POLICYOVERIDE |
4-Warning |
Dynamic policy overriding static on intf:[chars] |
Static policy and dynamic policy are configured on the\n\ interface. The dynamic policy will override the static\n\ policy. |
- |
"Remove the static policy config if desired." |
|
POLICY_API-4-POLICYSTATICCLR |
4-Warning |
Static policy on intf:[chars] cleared. Dynamic policy in use. |
A dynamic policy was overriding the static policy.\n\ Static policy has been cleared. |
- |
"No action required." |
|
POLICY_MANAGER-2-INIT_FAILURE |
2-Critical |
Init failure: [chars] |
A problem occurred in the Policy Manager during initialization |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
POLICY_MANAGER-2-NO_FREE_EVENT_BUFFERS |
2-Critical |
Event pool depleted: [chars] |
The event pool has been depleted. There are no free buffers to process event |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
POLICY_MANAGER-3-INVALID_ACTION |
3-Error |
Invalid action |
An invalid Policy Manager action was detected. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
POLICY_MANAGER-3-INVALID_PARAMETERS |
3-Error |
A call to Policy Manager is made with invalid parameters |
A call to Policy Manager was made with one or more invalid parameters |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
POLICY_MANAGER-3-INVALID_SEVERITY |
3-Error |
Invalid event severity 0x[hec] |
The event that was received by the Policy Manager contained an invalid severity and was therefore not processed. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
POLICY_MANAGER-3-NO_FREE_POLICY_IDS |
3-Error |
No more Policy IDs available |
There are no more Policy IDs that can be allocated. The effect of this is that Policy Manager policies can no longer be created. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
POLICY_MANAGER-3-NULL_ACTION_ROUTINE |
3-Error |
NULL action routine invoked |
The Policy Manager attempted to invoke an action which was NULL |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
POLICY_MANAGER-3-PRE_INIT_CALL |
3-Error |
Policy Manager routine called prior to initialization |
The Policy Manager component was called prior to initialization. This could result in vital information being lost. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
POP3_ALG-3-CHUNK_CREATE_FAIL |
3-Error |
- |
POP3 code has detected a cleartext logon attempt in the inspected POP3 connection while secure-login is configured. This command has been rejected. |
cpp-ucode |
"This message is for informational purposed only but may indicate" "a security problem." |
|
PORT_INIT_10G-2-PHY_NOT_READY_TIMEOUT |
2-Critical |
front panel 10G port init error: PHY ready not received within %llu seconds |
front panel 10G interface init failure due to timeout |
cpp-ucode |
LOG_STD_ACTION |
|
PORT_INIT_10G-2-PHY_NOT_READY_TIMEOUT |
2-Critical |
- |
- |
- |
- |
|
PORT_SECURITY-2-PSECURE_VIOLATION |
2-Critical |
Security violation occurred caused by MAC address [enet] on port [chars]. |
An unauthorized device attempted to connect on a secure port. The MAC address of the unauthorized device and the secure port are specified in the error message. |
Port Security |
"Determine the device that attempted to connect on the secure port." "Notify your network system administrator of this condition." |
|
PORT_SECURITY-2-PSECURE_VIOLATION_VLAN |
2-Critical |
Security violation on port [chars] due to MAC address [enet] on VLAN [dec] |
An unauthorized device attempted to connect on a secure trunk port. The MAC address of the unauthorized device and the secure trunk and VLAN are specified in the error message. |
Port Security |
"Determine the device that attempted to connect via the secure trunk " "port. Notify your network system administrator of this condition." |
|
PORT_SECURITY-6-ADDR_ADDFAIL |
6-Information |
Address <[dec]:[enet]> could not be added to [chars] due to [chars]. |
In some rare cases MAC addresses are learnt before all software modules finished initialization and fully functional. In such cases this address may not be known to all modules in the system. |
Port Security |
LOG_STD_NO_ACTION |
|
PORT_SECURITY-6-ADDR_REMOVED |
6-Information |
Address <[dec]:[enet]> exists on port [chars]. It has been removed from port [chars]. |
A routed port has changed to a switched port. An address stored in the previous switched port configuration is now in conflict and has been deleted. |
Port Security |
LOG_STD_NO_ACTION |
|
PORT_SECURITY-6-ADDRESSES_REMOVED |
6-Information |
Maximum system secure address count reached. Some secure addresses configured on port [chars] removed. |
Some configured and sticky MAC addresses on the specified port were removed from the configuration. The number of secure addresses that the system supports was exceeded. This condition occurs only during hot swapping or port-mode changes for example when the port is converted from a L3 to a L2 port. |
- |
- |
|
PORT_SECURITY-6-VLAN_FULL |
6-Information |
Vlan [dec] on port [chars] has reached its limit. Address [enet] has been removed. |
The voice VLAN has become the same as the access VLAN but the number of addresses allowed on the access VLAN has been reached so the address has been deleted. |
Port Security |
LOG_STD_NO_ACTION |
|
PORT_SECURITY-6-VLAN_REMOVED |
6-Information |
VLAN [dec] is no longer allowed on port [chars]. Its port security configuration has been removed. |
A configured VLAN has been excluded either due to port mode change or allowed VLAN list change and is removed from the configuration. |
Port Security |
LOG_STD_NO_ACTION |
|
PORT-6-NULL_OBJ |
6-Information |
Port object [chars] is unavailable. |
Information about this port could not be retrieved. The port may not exist. |
- |
LOG_STD_NO_ACTION |
|
PORT-6-PORT_RECOVERY |
6-Information |
[chars] [chars] |
Recovery has been triggered. Configured action will take place on \n\ the port |
- |
LOG_STD_NO_ACTION |
|
PORT-6-SESSION_RECOVERY |
6-Information |
[chars] [chars] [dec] |
Session recovery has an invalid cause code |
- |
LOG_STD_NO_ACTION |
|
PORT-6-SM_PORT_CLEARED |
6-Information |
[chars] |
The ports will be reset and any active calls on these ports will be terminated |
- |
LOG_STD_NO_ACTION |
|
POS_SPA_FRMR-3-C2_MISMATCH |
3-Error |
The software [dec] and hardware [dec] copy of sonet c2 is detected to |
During Minimal Disruptive Restart the software and hardware copy of the sonet C2 parameter is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic. |
spa-pos-all |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
POS_SPA_FRMR-3-CRC_MISMATCH |
3-Error |
The software [dec] and hardware [dec] copy of crc is detected to be |
During Minimal Disruptive Restart the software and hardware copy of the crc parameter is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic. |
spa-pos-all |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
POS_SPA_FRMR-3-FRAMING_MISMATCH |
3-Error |
The software [dec] and hardware [dec] copy of framing is detected to be |
During Minimal Disruptive Restart the software and hardware copy of the framing parameter is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic. |
spa-pos-all |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
POS_SPA_FRMR-3-LOOPBACK_MISMATCH |
3-Error |
The software [dec] and hardware [dec] copy of loopback is detected |
During Minimal Disruptive Restart the software and hardware copy of the loopback parameter is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic. |
spa-pos-all |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
POS_SPA_FRMR-3-MTU_MISMATCH |
3-Error |
The software [dec] and hardware [dec] copy of mtu is detected to be |
During Minimal Disruptive Restart the software and hardware copy of the mtu is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic. |
spa-pos-all |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
POS_SPA_FRMR-3-NULL_DEV_OBJ |
3-Error |
- |
Pointer to framer device object is NULL. |
spa-pos-all |
LOG_STD_SH_TECH_ACTION |
|
POS_SPA_FRMR-3-RECONCILE_FAILURE |
3-Error |
Framer reconcilation failure for SPA in [dec]/[dec] during Minimal Disruptive Restart. |
During Minimal Disruptive Restart the framer reconcilation error has occured. This indicates an error and the SPA will be reset as normal and will impact traffic. |
spa-pos-all |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
POS_SPA_FRMR-3-RECONFIG_FAILURE |
3-Error |
Framer reconfiguration failed for SPA in [dec]/[dec] with error [dec] during Minimal Disruptive Restart. |
During Minimal Disruptive Restart the framer reconfig error has occured. This indicates an error and the SPA will be reset as normal and will impact traffic. |
spa-pos-all |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
POS_SPA_FRMR-3-RESTART_FAILURE |
3-Error |
Framer restart failed for SPA in [dec]/[dec] with error [dec] during Minimal Disruptive Restart. |
During Minimal Disruptive Restart framer restart error has occured. This indicates an error and the SPA will be reset as normal and will impact traffic. |
spa-pos-all |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
POS_SPA_FRMR-3-S1S0_MISMATCH |
3-Error |
The software [dec] and hardware [dec] copy of sonet S1S0 is detected |
During Minimal Disruptive Restart the software and hardware copy of the sonet S1S0 parameter is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic. |
spa-pos-all |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
POS_SPA_FRMR-3-SCRAMBLE_MISMATCH |
3-Error |
The software [dec] and hardware [dec] copy of scrambling is detected |
During Minimal Disruptive Restart the software and hardware copy of the scrambling parameter is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic. |
spa-pos-all |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
POS_SPA_FRMR-3-TRANSMIT_DELAY_MISMATCH |
3-Error |
The software [dec] and hardware [dec] copy of transmit-delay is |
During Minimal Disruptive Restart the software and hardware copy of the transmit delay parameter is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic. |
spa-pos-all |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
POS_SPA_SPI4-3-RECONFIG_FAILURE |
3-Error |
SPI4 reconfiguration failed for SPA in [dec]/[dec] with error [dec] during Minimal Disruptive Restart. |
During Minimal Disruptive Restart the spi4 reconfig error has occured. This indicates an error and the SPA will be reset as normal and will impact traffic. |
spa-pos-all |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
POS_SPA_SPI4-3-RESTART_FAILURE |
3-Error |
SPI4 restart failed for SPA in [dec]/[dec] with error [dec] during Minimal Disruptive Restart. |
During Minimal Disruptive Restart spi4 restart error has occured. This indicates an error and the SPA will be reset as normal and will impact traffic. |
spa-pos-all |
"Open a case with Cisco Technical Assistance Center for further " "assistance." |
|
POSIX_DPDK-3-HPAGE_MIN |
3-Error |
[dec]MB does not meet [dec]MB minimum memory reservation. Performance may be impacted. |
Cisco internal software error. The dataplane was unable to allocate the minimum number of hugepages. This could be caused by insufficient reservation or hugepages being consumed by other processes. |
cpp-ucode |
LOG_STD_ACTION |
|
POSIX_DPDK-3-NUMA_NODES |
3-Error |
Expected 1 CPU socket detected [dec]. Performance may be impacted. |
Virtual machine configuration issue. The dataplane detected multiple NUMA nodes. This is caused by the guest configuration of the hyper-visor. |
cpp-ucode |
LOG_STD_ACTION |
|
POSIX_FIXUP-4-FIXUP_OCCURRED |
4-Warning |
alignment fixup @ PC=0x[hec] #hits=[dec] fault addr 0x[hec] |
A misalignment was handled by a fixup signal handler |
- |
- |
|
POSIX_FIXUP-4-FIXUP_OCCURRED |
4-Warning |
alignment fixup @ PC=0x%08x #hits=[dec] fault addr 0x%08x |
A misalignment was handled by a fixup signal handler |
- |
- |
|
POSIX_PMD-3-MBUF_REDUCE |
3-Error |
Failed to allocate [dec] packet buffers. Reduced to [dec]. |
Cisco internal software error. The dataplane was unable to allocate the maximum number of packet buffers. This is likely due to memory fragmentation condition. |
cpp-ucode |
LOG_STD_ACTION |
|
POSLC-1-INITFAIL |
1-Alert |
POSLC[dec]/[dec] initialization timeout failure |
LC POS ASIC and framer initialization failed |
poslc |
"Copy the error message exactly as it appears on the \n\ console or in the system log. If you cannot determine \n\ the nature of the error from the error message text \n\ call your Cisco technical support representative and \n\ provide the \n\ representative with the gathered information." |
|
POSLC-3-4302 |
3-Error |
Runaway Skystone 4302 framer [dec] Tx [chars] counter byte=[dec] pkt=[dec]. |
4302 hardware errors |
poslc |
"Copy the error message exactly as it appears on the console \n\ or in the system log. Call your Cisco technical support \n\ representative and provide the representative \n\ with the gathered information." |
|
POSLC-3-APS |
3-Error |
APS[dec] [chars] |
RP deadman timer expired on LC LC is sending LAIS to far end |
poslc |
"Copy the error message exactly as it appears on the console \n\ or in the system log. Call your Cisco technical support \n\ representative and provide the representative \n\ with the gathered information." |
|
POSLC-3-BMAENG |
3-Error |
[chars] POS [chars] [chars][chars]. src=0x[hec] det1=0x[hec] det2=0x[hec] |
POS BMA engine hardware errors |
poslc |
- |
|
POSLC-3-BMAPAR |
3-Error |
[chars] POS [chars]. BMA_DATA[3:0]=0x[hec]. src=0x[hec] det1=0x[hec] det2=0x[hec] |
Parity error occurred on POS asic BMA engine |
poslc |
- |
|
POSLC-3-CORRUPT |
3-Error |
[chars] |
A NULL SERIAL or SONET subblock retrieved while trying to fetch SERIAL or SONET subblock |
poslc osm-pos |
LOG_STD_ACTION |
|
POSLC-3-HWERROR |
3-Error |
[chars] |
The Optical Services Module has encountered a hardware error. |
poslc |
LOG_STD_ACTION |
|
POSLC-3-LINKBADEVT |
3-Error |
Unexpected event woke up LC POS link process. |
LC POS link report process receives an unexpected event |
poslc |
"Copy the error message exactly as it appears on the \n\ console or in the system log. Issue the show subsys \n\ command to gather data that may provide information\n\ to determine the nature of the error. If you cannot \n\ determine the nature of the error from the error \n\ message text or from the show subsys output call your\n\ Cisco technical support representative and provide the \n\ representative with the gathered information." |
|
POSLC-3-LINKNOPRC |
3-Error |
POSLC lcpos_add_process: Unable to create \n\ lcpos_link_report process |
LC POS link report process can not be created |
poslc |
"Copy the error message exactly as it appears on the \n\ console or in the system log. Issue the show subsys \n\ command to gather data that may provide information\n\ to determine the nature of the error. If you cannot \n\ determine the nature of the error from the error \n\ message text or from the show subsys output call your\n\ Cisco technical support representative and provide the \n\ representative with the gathered information." |
|
POSLC-3-LINKPROC |
3-Error |
POSLC lcpos_link_report process: Could not get argument |
LC POS link report process stops working |
poslc |
"Copy the error message exactly as it appears on the \n\ console or in the system log. Issue the show subsys show\n\ memory summary commands to gather data that may provide \n\ information to determine the nature of the error. If you \n\ cannot determine the nature of the error from the error \n\ message text or from the show subsys show memory summary \n\ output call your Cisco technical support representative \n\ and provide the representative with the gathered \n\ information." |
|
POSLC-3-POSENG |
3-Error |
[chars] POS [chars]. [chars] port [dec]. src=0x[hec] det1=0x[hec] det2=0x[hec] |
POS engine hardware errors |
poslc |
- |
|
POSLC-3-PROCESS_CREATEFAIL |
3-Error |
[chars] |
The PoS line card could not create a process required for its operation. This condition might be caused by a resource being unavailable. |
poslc |
LOG_STD_ACTION |
|
POSLC-3-PROCESS_TIMEREVENT |
3-Error |
[chars] |
An unexpected process timer event occurred in the Optical Services Module. |
poslc |
LOG_STD_ACTION |
|
POSLC-3-RXPOSTO |
3-Error |
POSLC[dec]/[dec] RX POS engine shutdown failed |
The software is trying to shutdown the Rx POS engine. POS\n\ engine refuses to shutdown the software timeout |
poslc |
- |
|
POSLC-3-SOP |
3-Error |
[chars] SOP. source=0x[hec] halt_minor0=0x[hec] |
SOP hardware errors |
poslc |
- |
|
POSLC-3-SRAMPAR |
3-Error |
[chars] POS [chars]. [chars]=0x[hec][chars]. src=0x[hec] det1=0x[hec] det2=0x[hec] |
Parity error occurred on POS asic SRAM |
poslc |
- |
|
POSLC-3-TXPOSTO |
3-Error |
POSLC[dec]/[dec] TX POS engine shutdown failed |
The software is trying to shutdown the Tx POS engine. POS \n\ engine refuses to shutdown the software timeout |
poslc |
- |
|
POSLC-3-UNEXPECTED_PROCESSEVENT |
3-Error |
[chars] |
An unexpected process event occurred in the Optical Services Module. |
poslc |
LOG_STD_ACTION |
|
POSLC-3-UNKNOWN_CONTROLLER |
3-Error |
[chars] |
An unknown controller condition was detected by the PoS line card while the controller was being analyzed. |
poslc |
LOG_STD_ACTION |
|
POWER_SUPPLIES-3-PWR_A_FAIL |
3-Error |
Power supply A is not functioning |
Power supply A is present but not functioning |
hardware |
LOG_STD_ACTION |
|
POWER_SUPPLIES-3-PWR_A_FAIL |
3-Error |
Power supply A is not functioning |
Power supply A is present but not functioning |
hardware |
LOG_STD_ACTION |
|
POWER_SUPPLIES-3-PWR_B_FAIL |
3-Error |
Power supply B is not functioning |
Power supply B is present but not functioning |
hardware |
LOG_STD_ACTION |
|
POWER_SUPPLIES-3-PWR_B_FAIL |
3-Error |
Power supply B is not functioning |
Power supply B is present but not functioning |
hardware |
LOG_STD_ACTION |
|
POWER_SUPPLIES-3-PWR_FAIL |
3-Error |
Power supply [chars] is not functioning |
Power supply is present but not functioning |
hardware |
LOG_STD_ACTION |
|
POWER_SUPPLIES-3-PWR_FAIL |
3-Error |
Power supply [chars] is not functioning |
Power supply is present but not functioning |
hardware |
LOG_STD_ACTION |
|
POWER_SUPPLIES-5-PWR_A_OK |
5-Notice |
Power supply A is functioning |
Power supply A is supplying power |
hardware |
LOG_STD_NO_ACTION |
|
POWER_SUPPLIES-5-PWR_A_OK |
5-Notice |
Power supply A is functioning |
Power supply A is supplying power |
hardware |
LOG_STD_NO_ACTION |
|
POWER_SUPPLIES-5-PWR_B_OK |
5-Notice |
Power supply B is functioning |
Power supply B is supplying power |
hardware |
LOG_STD_NO_ACTION |
|
POWER_SUPPLIES-5-PWR_B_OK |
5-Notice |
Power supply B is functioning |
Power supply B is supplying power |
hardware |
LOG_STD_NO_ACTION |
|
POWER_SUPPLIES-5-PWR_OK |
5-Notice |
Power supply [chars] is functioning |
Power supply is supplying power |
hardware |
LOG_STD_NO_ACTION |
|
POWER_SUPPLIES-5-PWR_OK |
5-Notice |
Power supply [chars] is functioning |
Power supply is supplying power |
hardware |
LOG_STD_NO_ACTION |
|
POWERNET_ISSU-3-CAP_INVALID_SIZE |
3-Error |
Powernet ISSU client capability list is empty. |
The Powernet ISSU client capability exchange list size is invalid. |
powernet |
"show issu capability entries <Client_ID>" |
|
POWERNET_ISSU-3-CAP_NOT_COMPATIBLE |
3-Error |
Powernet ISSU client capability exchange result incompatible. |
The Powernet ISSU client capability exchange has negotiated as incompatible with the peer. |
powernet |
"show issu negotiated capability <Session_ID>" |
|
POWERNET_ISSU-3-CAPABILITY |
3-Error |
Powernet ISSU client [chars] |
Powernet ISSU client observed an error during capability negotiation. When this error happens there is a mismatch between the client capability between the active and standby unit. |
powernet |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
POWERNET_ISSU-3-GET_BUFFER |
3-Error |
EnergyWise ISSU client failed to get buffer for message. Error: [dec] [chars] |
EnergyWise 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 negotiaiton the standby device cannot be brought up properly. |
powernet |
"show logging and show checkpoint client" |
|
POWERNET_ISSU-3-INIT |
3-Error |
EnergyWise ISSU client initialization failed to [chars]. Error: [dec] [chars] |
EnergyWise ISSU client could not be initiailzed. 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. |
powernet |
LOG_STD_SH_TECH_ACTION |
|
POWERNET_ISSU-3-INVALID_SESSION |
3-Error |
EnergyWise ISSU client does not have a valid registered session. |
EnergyWise ISSU client does not have a valid registered session. |
powernet |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
POWERNET_ISSU-3-MSG_NOT_OK |
3-Error |
EnergyWise ISSU client 'Message Type [dec]' is not compatible |
EnergyWise ISSU client received an incompatible message from the peer device. The message cannot be processed. |
powernet |
"show issu message group <client_id> and" "show issu session <client_id> and" "show issu negotiated version <session_id>" |
|
POWERNET_ISSU-3-MSG_SIZE |
3-Error |
EnergyWise ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
EnergyWise ISSU client failed to calculate the MTU for the specified message. The EnergyWise ISSU client is not able to send the message to the standby device. |
powernet |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
POWERNET_ISSU-3-SEND_NEGO_FAILED |
3-Error |
EnergyWise ISSU client failed to send negotiation message. Error: [dec] [chars] |
EnergyWise 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 can not be brought up properly. |
powernet |
"show logging and show checkpoint client" |
|
POWERNET_ISSU-3-SESSION_NEGO |
3-Error |
EnergyWise ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The EnergyWise 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. |
powernet |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
POWERNET_ISSU-3-SESSION_REGISTRY |
3-Error |
EnergyWise ISSU client failed to register session information. Error: [dec] [chars] |
EnergyWise ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
powernet |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
POWERNET_ISSU-3-SESSION_UNREGISTRY |
3-Error |
EnergyWise ISSU client failed to unregister session information. Error: [dec] [chars] |
EnergyWise ISSU client failed to unregister session information. |
powernet |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
POWERNET_ISSU-3-TRANSFORM_FAIL |
3-Error |
EnergyWise ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
EnergyWise 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 EnergyWise state between the active device and the standby device is not identical. |
powernet |
"show issu session <client_id> and" "show issu negotiated version <session_id>" |
|
POWR1220-4-INIT_NO_RESPONSE |
4-Warning |
POWR1220 is not responding. The device is [chars] |
POWR1220 device is not responding |
cmts-platform |
"Copy the error message exactly as it appears and report it to your" " technical support" |
|
POWR1220-4-INIT_SEQUENCE_FAILURE |
4-Warning |
POWR1220 sequencing failure happened. The device is [chars] and register values are reg 0x03 0x%02x reg 0x04 0x%02x reg 0x05 0x%02x reg 0x07 0x%02x reg 0x08 0x%02x |
POWR1220 device registers do now show correct values |
cmts-platform |
"Copy the error message exactly as it appears and report it to your" " technical support" |
|
PPCP-3-LOCK |
3-Error |
Can't lock policy provisioning database: [chars] |
Access to stored class-maps policy-maps service-policies and related data is protected by a locking mechanism. An operation tried to read or write provisioning data but was unable to get control of the lock. |
qos-internal |
"Any Cisco Class-based Policy Provisioning Language configuration " "or show commands that you were attempting to " "run may not have succeeded. Please try the operation again.\n\n" "Contact support if this message is seen frequently." |
|
PPCP-6-WAVL |
6-Information |
\n[chars] is not successful |
The specified classmap or policymap insertion or removal was not succcessful. This is an internal software error.\n |
- |
LOG_STD_ACTION |
|
PPM_REQ_FAILED-3-L2VPN |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
PPP-3-MLPFSREENTERED |
3-Error |
Multilink fastsend reentered bundle [chars] [chars] packet discarded |
- |
- |
- |
|
PPP-4-IPXNET |
4-Warning |
mismatched IPX network numbers. Ours = [hec] theirs = [hec] |
The two ends of a serial link have different IPX network numbers. |
- |
"Confirm the configuration of both devices." |
|
PPP-4-NOAPPOINT |
4-Warning |
MLP Bundle [chars] not appointed |
Multilink PPP Bundle was not appointed. Most likely caused by\n\ no memory available |
- |
"Log show memory summary output. Then analyze output to find\n\ possible memory leak" |
|
PPP-4-NOMAC |
4-Warning |
Lex ncp: no free Lex interface found with MAC address [enet] |
This message indicates that a LAN Extender interface could\n\ not be found with the specified MAC address when bringing up\n\ a LAN Extender link. This is a configuration error. |
- |
"Refer to the documentation on configuring a LAN Extender\n\ Interface." |
|
PPPOE_IA-3-GLOBAL_ERROR |
3-Error |
PPPoE IA internal error [chars] |
A software sanity check failed in the PPPoE IA process as described in the output. This happens when the PPPoE IA feature receives a packet with an invalid source interface or source VLAN. PPPoE IA drops the packet but is otherwise unaffected. |
cat4000-me-sw |
"Issue the show running-config show pppoe intermediate-agent info " "and debug pppoe intermediate-agent command to gather more data " "about the error. If necessary contact Cisco technical support " "to help solve the problem." |
|
PPPOE_IA-3-INTERFACE_ERROR |
3-Error |
PPPoE IA internal error Interface [chars] : [chars] |
A software sanity check failed on an interface in the PPPoE IA process. This message is displayed if PPPoE IA received a packet it shouldn't according to the configuration. PPPoE IA drops the packet but is otherwise unaffected. |
cat4000-me-sw |
"Issue the show running-config show pppoe intermediate-agent info " "and debug pppoe intermediate-agent command to gather more data " "about the error. If necessary contact Cisco technical support " "to help solve the problem." |
|
PPPOE_IA-4-ERRDISABLE_WARNING |
4-Warning |
PPPoE IA received [dec] PPPoE packets on interface [chars] |
PPPoE IA detected a PPPoE packet rate limit violation on the specified interface. The interface will be error disabled. |
cat4000-me-sw |
LOG_STD_NO_ACTION " To recover the disabled interface use the " "errdisable recovery cause pppoe-ia-rate-limit command" |
|
PPPOE_IA-4-QUEUE_FULL |
4-Warning |
Fail to enqueue PPPoE packet into processing queue: [chars] the queue is probably full and packet will be dropped. |
PPPoE packets are being received at a much higher rate than PPPoE IA process can handle them. These unhandled PPPoE packets will be dropped to prevent a possible denial of service attack. |
cat4000-me-sw |
LOG_STD_NO_ACTION |
|
PPPOE_IA-4-RATE_LIMIT_EXCEEDED |
4-Warning |
The interface [chars] is receiving more than the threshold set |
PPPoE packets are being received at a much higher rate than the specified threshold. |
cat4000-me-sw |
LOG_STD_NO_ACTION |
|
PPPOE_IA-5-UNTRUSTED_PORT |
5-Notice |
[chars] drop message on untrusted port message type: [chars] MAC sa: [enet] |
PPPoE IA detected types of PPPoE messages that are not allowed on the untrusted interface. A host may be trying to act as a PPPoE server. |
cat4000-me-sw |
LOG_STD_NO_ACTION |
|
PPROT_FSM-3-CHUNK_CREATE |
3-Error |
chunk create failed |
chunk create failed |
g709-dwdm |
LOG_STD_ACTION |
|
PPROT_FSM-3-CREATE_FAIL |
3-Error |
creation failed : [chars] |
creation failed |
g709-dwdm |
LOG_STD_ACTION |
|
PPROT_FSM-3-MALLOC_FAIL |
3-Error |
malloc failed : [chars] |
malloc failed |
g709-dwdm |
LOG_STD_ACTION |
|
PPROT_FSM-3-PROC_ALL_TRANSIT_EVENT |
3-Error |
All events could not be processed in transit queue |
All events could not be processed in transit queue |
g709-dwdm |
LOG_STD_ACTION |
|
PPROT_FSM-3-TRANSIT_EVENT |
3-Error |
Invalid event [dec] while processing transit event queue |
Invalid event while processing transit event queue |
g709-dwdm |
LOG_STD_ACTION |
|
PPROT_FSM-4-FSM_FIND_INFO_FAIL |
4-Warning |
Could not find element if_number [dec] in FSM list |
Could not find element in FSM list |
g709-dwdm |
LOG_STD_ACTION |
|
PPROT_L3_TRIG-3-CHUNK_CREATE |
3-Error |
chunk create failed |
chunk create failed |
g709-dwdm |
LOG_STD_ACTION |
|
PPROT_L3_TRIG-3-INVALID_CLIENT_TYPE |
3-Error |
Invalid client type [dec] from xdr |
invalid client type from xdr |
g709-dwdm |
LOG_STD_ACTION |
|
PPROT_L3_TRIG-3-ISSU_COMP_FAIL |
3-Error |
L3 trigger xdr priority msg not issu compatible |
L3 trigger xdr priority msg not issu compatible |
g709-dwdm |
LOG_STD_ACTION |
|
PPROT_L3_TRIG-3-MALLOC_FAIL |
3-Error |
malloc failed: [chars] |
malloc failed |
g709-dwdm |
LOG_STD_ACTION |
|
PQ3_FE-1-INITFAILP |
1-Alert |
PQ3/FE[dec]/[dec] Init failed at [chars] |
The FE could not allocate a I/O buffer pool. |
- |
"Clear the interface. If the message recurs call your\n\ technical support representative for assistance." |
|
PQ3_FE-1-MACADDRFAIL |
1-Alert |
PQ3/FE[dec]/[dec] Unable to set the Mac-address for the interface |
The FEC could not set the mac address of the interface. |
- |
"Clear the interface. If the message recurs call your\n\ technical support representative for assistance." |
|
PQ3_FE-1-SHOWFAIL |
1-Alert |
PQ3/FE[dec]/[dec] Memory error at [chars] |
The FEC could not allocate memory to display controller. |
- |
"Clear the interface. If the message recurs call your\n\ technical support representative for assistance." |
|
PQ3_FE-2-NOISL |
2-Critical |
Interface [chars] does not support ISL |
The interface cannot be configured as an ISL trunk. |
- |
"Check the configuration." |
|
PQ3_FE-3-OVERFLO |
3-Error |
PQ3/FE[dec]/[dec] Receive overflow |
While receiving a frame the controller chip's local buffer\n\ transmitted insufficient data because data could not be transferred to\n\ DRAM fast enough to keep pace with its input rate. Normally such a\n\ problem is temporary depending on transient peak loads within the\n\ system. |
- |
"The system should recover. No action is required." |
|
PQ3_FE-3-UNDERFLO |
3-Error |
PQ3/FE[dec]/[dec] Transmit underflow |
While transmitting a frame the controller chip's local buffer\n\ received insufficient data because data could not be transferred to the\n\ chip fast enough to keep pace with its output rate. Normally such a\n\ problem is temporary depending on transient peak loads within the\n\ system. |
- |
"The system should recover. No action is required." |
|
PQ3_FE-4-BABBLE |
4-Warning |
PQ3/FE[dec]/[dec] Babble error CSR[dec]=0x%04x |
The transmitter has been on the\n\ channel longer than the time taken to transmit the largest\n\ frame. |
- |
"The system should recover. No action is required." |
|
PQ3_FE-5-EXECOLL |
5-Notice |
PQ3/FE[dec]/[dec] Excessive collision |
Excessive collisions occurred on the Fast Ethernet interface. |
- |
"No action is required." |
|
PQ3_FE-5-LATECOLL |
5-Notice |
PQ3/FE[dec]/[dec] Late collision |
Late collisions occurred on the Fast Ethernet interface. |
- |
"If the interface is Fast Ethernet verify that both\n\ peers are in the same duplex mode. No action is\n\ required." |
|
PQ3_FE-5-LOSTCARR |
5-Notice |
PQ3/FE[dec]/[dec] Lost carrier. Transceiver problem? |
The cable and/or transceiver is not connected. |
- |
"Connect the cable and/or transceiver." |
|
PQ3_TSEC-1-INITFAIL |
1-Alert |
PQ3/FE[dec] Init failed CSR[dec]=0x%04x |
The software failed to initialize/restart an Ethernet/Fast Ethernet interface. |
- |
"Clear the interface. If the message recurs call your\n\ technical support representative for assistance." |
|
PQ3_TSEC-1-INITFAILP |
1-Alert |
PQ3/FE[dec] Init failed at [chars] |
The FEC could not allocate a I/O buffer pool. |
- |
"Clear the interface. If the message recurs call your\n\ technical support representative for assistance." |
|
PQ3_TSEC-1-MEMERR |
1-Alert |
PQ3/FE[dec] Memory error CSR[dec]=0x%04x |
The interface could not access system resources for a\n\ long time. This problem may occur under very heavy loads. |
- |
"The system should recover. No action is required. If the message recurs call\n\ your technical support representative for assistance." |
|
PQ3_TSEC-1-SHOWFAIL |
1-Alert |
PQ3/FE[dec] Memory error at [chars] |
The FEC could not allocate memory to display controller. |
- |
"Clear the interface. If the message recurs call your\n\ technical support representative for assistance." |
|
PQ3_TSEC-2-NOISL |
2-Critical |
Interface [chars] does not support ISL |
The interface cannot be configured as an ISL trunk. |
- |
"Check the configuration." |
|
PQ3_TSEC-3-OVERFLO |
3-Error |
PQ3/FE[dec] Receive overflow |
While receiving a frame the controller chip's local buffer\n\ transmitted insufficient data because data could not be transferred to\n\ DRAM fast enough to keep pace with its input rate. Normally such a\n\ problem is temporary depending on transient peak loads within the\n\ system. |
- |
"The system should recover. No action is required." |
|
PQ3_TSEC-3-OWNERR |
3-Error |
PQ3/FE[dec] Buffer ownership error pak=0x[hec] |
The software detected an error in descriptor ownership. |
- |
"Try a later version of the software. If the message " "recurs call your technical support representative " "for assistance." |
|
PQ3_TSEC-3-UNDERFLO |
3-Error |
PQ3/FE[dec] Transmit underflow |
While transmitting a frame the controller chip's local buffer\n\ received insufficient data because data could not be transferred to the\n\ chip fast enough to keep pace with its output rate. Normally such a\n\ problem is temporary depending on transient peak loads within the\n\ system. |
- |
"The system should recover. No action is required." |
|
PQ3_TSEC-3-UNDERFLO |
3-Error |
PQ3/FE[dec] Transmit underflow |
\ While transmitting a frame the controller chip's local buffer \ received insufficient data because data could not be transferred to the \ chip fast enough to keep pace with its output rate. Normally such a \ problem is temporary depending on transient peak loads within the \ system. |
firmware |
"The system should recover. No action is required." |
|
PQ3_TSEC-4-BABBLE |
4-Warning |
PQ3/FE[dec] Babble error CSR[dec]=0x%04x |
The transmitter has been on the\n\ channel longer than the time taken to transmit the largest\n\ frame. |
- |
"The system should recover. No action is required." |
|
PQ3_TSEC-4-BABBLE |
4-Warning |
PQ3/FE[dec] Babble error CSR[dec]=0x%04x |
The transmitter has been on the \ channel longer than the time taken to transmit the largest \ frame. |
hardware |
"The system should recover. No action is required." |
|
PQ3_TSEC-5-COLL |
5-Notice |
PQ3/FE[dec] Excessive collisions TDR=[dec] TRC=[dec]. |
- |
- |
- |
|
PQ3_TSEC-5-COLL |
5-Notice |
PQ3/FE[dec] Excessive collisions TDR=[dec] TRC=[dec]. |
- |
- |
- |
|
PQ3_TSEC-5-EXCESSCOLL |
5-Notice |
PQ3/FE[dec] Excessive collision |
Ethernet/Fast Ethernet is seeing multiple collisions. This\n\ may occur under heavy loads. |
- |
"The system should recover. No action is\n\ required." |
|
PQ3_TSEC-5-LATECOLL |
5-Notice |
PQ3/FE[dec] Late collision |
Late collisions occurred on the Ethernet/Fast Ethernet interface. |
- |
"If the interface is Fast Ethernet verify that both\n\ peers are in the same duplex mode. For regular\n\ Ethernet the system should recover. No action is\n\ required." |
|
PQ3_TSEC-5-LATECOLL |
5-Notice |
PQ3/FE[dec] Late collision |
Late collisions occurred on the Ethernet/Fast Ethernet interface. |
hardware |
"If the interface is Fast Ethernet verify that both \ peers are in the same duplex mode. For regular \ Ethernet the system should recover. No action is\ required." |
|
PQ3_TSEC-5-LOSTCARR |
5-Notice |
PQ3/FE[dec] Lost carrier. Transceiver problem? |
The cable is not connected to the port. |
- |
"Connect the cable to the port." |
|
PQ3_TSEC-5-LOSTCARR |
5-Notice |
PQ3/FE[dec] Lost carrier. Transceiver problem? |
The cable is not connected to the port. |
hardware |
"Connect the cable to the port." |
|
PQUICC-1-BADHDXFSM |
1-Alert |
PQUICC[dec]/[dec] Unexpected HDX state [dec] event [dec] |
A bad event was detected in the state machine for half duplex\n\ transmission/reception. |
- |
"Copy the error message exactly as it\n\ appears and report it to your technical support representative." |
|
PQUICC-1-CTSLOST |
1-Alert |
PQUICC[dec]/[dec] Clear to Send Lost |
- |
- |
"Check the serial interface cable and/or communication equipment such\n\ as the channel service unit/data service unit CSU/DSU." |
|
PQUICC-1-INITFAIL |
1-Alert |
PQUICC[dec]/[dec] SCC[dec] init failed |
The software failed to initialize/restart a 1T serial card. |
- |
"Clear the serial interface.\n\ If the message recurs call your technical support representative for\n\ assistance." |
|
PQUICC-1-LINEFLAP |
1-Alert |
PQUICC[dec]/[dec] Excessive modem control changes |
- |
- |
"Check the serial interface cable. The error can occur if the cable is\n\ disconnected or has come loose and is picking up noise. If the cable\n\ appears to be connected correctly check the equipment connected to the\n\ cable." |
|
PQUICC-1-NOMEMORY |
1-Alert |
msgtxt_nomemory |
The MPC860/PowerQUICC CPU was unable to access the memory it needs to\n\ carry out its functions. Here are some possible causes.\n\\n\ The network is large requiring a lot of memory for routing tables and\n\ so on.\n\\n\ The router configuration has many features enabled each of which\n\ require a certain amount of memory.\n\\n\ A software error memory leak exists. |
- |
"Reduce system activity to ease the memory demand or upgrade to a\n\ larger memory configuration." |
|
PQUICC-1-QMC_GLOBAL_ERROR |
1-Alert |
PQUICC[dec]/[dec] Global error [hec] in QMC |
One or more of the channels served by the QMC instance encountered\n\ transmitter underflow or receiver overflow or the QMC interrupt\n\ table overflowed. Normally such a problem is temporary depending on \n\ transient peak loads within the system. |
- |
"The system should recover. No action is required." |
|
PQUICC-1-TOOBIG |
1-Alert |
PQUICC[dec]/[dec] packet too big packet size was [dec] bytes |
A packet greater than the assigned MTU of this serial interface\n\ was queued up for transmission. |
- |
"The system should recover. No action is required.\n\ \n\ If the message recurs it may indicate an error\n\ related to data traffic patterns. Copy the error message exactly as it\n\ appears and report it to your technical support representative." |
|
PQUICC-1-TOOSMALL |
1-Alert |
PQUICC[dec]/[dec] packet was less than 2 bytes\n\msgdef_explanation A small packet |
- |
- |
- |
|
PQUICC-1-UNDERFLO |
1-Alert |
PQUICC[dec]/[dec] Transmit underflow |
While transmitting a frame the serial controller chip's local buffer\n\ received insufficient data because data could not be transferred to the\n\ chip fast enough to keep pace with its output rate. Normally such a\n\ problem is temporary depending on transient peak loads within the\n\ system. |
- |
"The system should recover. No action is required." |
|
PQUICC-1-UNEXPECTED_INTERRUPT |
1-Alert |
PQUICC[dec] Unexpected modem-signal interrupt |
The software did not expect to see a modem control signal change\n\ on this type of WIC card interface. |
- |
"Copy the error message exactly as it\n\ appears and report it to your technical support representative." |
|
PQUICC-1-UNKNOWN_WIC |
1-Alert |
PQUICC[dec] WIC card has an unknown ID of 0x[hec] |
The software does not recognize the type of WIC card plugged\n\ into the port module. |
- |
"Check the part number on the WIC card to verify that it is supported\n\ in the IOS release operational on the router or contact\n\ your technical support representative." |
|
PQUICC-1-UNSUPPORTED_CONFIG |
1-Alert |
Slot [dec] has an unsupported combination of ISDN WAN interface cards |
It is not possible to support this type of BRI card in\n\ slot 1 along with another BRI card in slot 0. |
- |
"Remove one of the BRI cards from either slot." |
|
PQUICC-1-WRONG_SLOT |
1-Alert |
PQUICC[dec] BRI card in wrong slot1 |
The BRI card is not supported in WIC slot 0. |
- |
"Power down move the BRI card to the other WIC slot on the\n\ port module and reboot." |
|
PQUICC3-1-BADHDXFSM |
1-Alert |
PQUICC3[dec]/[dec] Unexpected HDX state [dec] event [dec] |
A bad event was detected in the state machine for half duplex\n\ transmission/reception. |
- |
"Copy the error message exactly as it\n\ appears and report it to your technical support representative." |
|
PQUICC3-1-CTSLOST |
1-Alert |
PQUICC3[dec]/[dec] Clear to Send Lost |
- |
- |
"Check the serial interface cable and/or communication equipment such\n\ as the channel service unit/data service unit CSU/DSU." |
|
PQUICC3-1-INITFAIL |
1-Alert |
PQUICC3[dec]/[dec] SCC[dec] init failed |
The software failed to initialize/restart a 1T serial card. |
- |
"Clear the serial interface.\n\ If the message recurs call your technical support representative for\n\ assistance." |
|
PQUICC3-1-LINEFLAP |
1-Alert |
PQUICC3[dec]/[dec] Excessive modem control changes |
- |
- |
"Check the serial interface cable. The error can occur if the cable is\n\ disconnected or has come loose and is picking up noise. If the cable\n\ appears to be connected correctly check the equipment connected to the\n\ cable." |
|
PQUICC3-1-NOMEMORY |
1-Alert |
msgtxt_nomemory |
The MPC8500/PowerQUICC CPU was unable to access the memory it needs to\n\ carry out its functions. Here are some possible causes.\n\\n\ The network is large requiring a lot of memory for routing tables and\n\ so on.\n\\n\ The router configuration has many features enabled each of which\n\ require a certain amount of memory.\n\\n\ A software error memory leak exists. |
- |
"Reduce system activity to ease the memory demand or upgrade to a\n\ larger memory configuration." |
|
PQUICC3-1-QMC_GLOBAL_ERROR |
1-Alert |
PQUICC3[dec]/[dec] Global error [hec] in QMC |
One or more of the channels served by the QMC instance encountered\n\ transmitter underflow or receiver overflow or the QMC interrupt\n\ table overflowed. Normally such a problem is temporary depending on \n\ transient peak loads within the system. |
- |
"The system should recover. No action is required." |
|
PQUICC3-1-TOOBIG |
1-Alert |
PQUICC3[dec]/[dec] packet too big packet size was [dec] bytes |
A packet greater than the assigned MTU of this serial interface\n\ was queued up for transmission. |
- |
"The system should recover. No action is required.\n\ \n\ If the message recurs it may indicate an error\n\ related to data traffic patterns. Copy the error message exactly as it\n\ appears and report it to your technical support representative." |
|
PQUICC3-1-TOOSMALL |
1-Alert |
PQUICC3[dec]/[dec] packet was less than 2 bytes\n\msgdef_explanation A small packet |
- |
- |
- |
|
PQUICC3-1-UNDERFLO |
1-Alert |
PQUICC3[dec]/[dec] Transmit underflow |
While transmitting a frame the serial controller chip's local buffer\n\ received insufficient data because data could not be transferred to the\n\ chip fast enough to keep pace with its output rate. Normally such a\n\ problem is temporary depending on transient peak loads within the\n\ system. |
- |
"The system should recover. No action is required." |
|
PQUICC3-1-UNEXPECTED_INTERRUPT |
1-Alert |
PQUICC3[dec] Unexpected modem-signal interrupt |
The software did not expect to see a modem control signal change\n\ on this interface. |
- |
"Copy the error message exactly as it\n\ appears and report it to your technical support representative." |
|
PQUICC3-1-UNKNOWN_WIC |
1-Alert |
PQUICC3[dec] WIC card has an unknown ID of 0x[hec] |
The software does not recognize the type of WIC card plugged\n\ into the port module. |
- |
"Check the part number on the WIC card to verify that it is supported\n\ in the IOS release operational on the router or contact\n\ your technical support representative." |
|
PQUICC3-1-UNSUPPORTED_CONFIG |
1-Alert |
Slot [dec] has an unsupported combination of ISDN WAN interface cards |
It is not possible to support this type of BRI card in\n\ slot 1 along with another BRI card in slot 0. |
- |
"Remove one of the BRI cards from either slot." |
|
PQUICC3-1-WRONG_SLOT |
1-Alert |
PQUICC3[dec] BRI card in wrong slot1 |
The BRI card is not supported in WIC slot 0. |
- |
"Power down move the BRI card to the other WIC slot on the\n\ port module and reboot." |
|
PQUICC3-3-DDR_ERR |
3-Error |
DDR [dec] [chars] error from memory |
A soft-parity error from the memory has been detected. Normal system operation should continue |
- |
"If there is a regular or sustained occurrence of this message copy" "the error message exactly as it appears and report it to" "technical support representative." |
|
PQUICC3-3-OWNERR |
3-Error |
msgtxt_ownerror |
An internal software error occurred. |
- |
"Call your technical support representative to obtain a software\n\ upgrade." |
|
PQUICC3-3-SPURIOUS_INTERRUPT |
3-Error |
Interface card in slot [dec] generated a spurious interrupt |
Interface card on the router which is not supported by this image\n\ generated a spurious interrupt that can not be handled. |
- |
"No action is required. To avoid seeing this message in the future\n\ remove the unsupported card or use an image that supports it." |
|
PQUICC3-3-UNKNOWN_SCC_TX_VECTOR |
3-Error |
PQUICC3 Unknown TX vector on port [dec] |
An internal software error occurred. |
- |
"Copy the error message exactly as it\n\ appears and report it to your technical support representative." |
|
PQUICC3-3-UNKNOWN_SCCS |
3-Error |
PQUICC3 Incorrect SCC number |
An internal software error occurred. |
- |
"Call your technical support representative to obtain a software\n\ upgrade." |
|
PQUICC-3-OWNERR |
3-Error |
msgtxt_ownerror |
An internal software error occurred. |
- |
"Call your technical support representative to obtain a software\n\ upgrade." |
|
PQUICC-3-SPURIOUS_INTERRUPT |
3-Error |
Interface card in slot [dec] generated a spurious interrupt |
Interface card on the router which is not supported by this image\n\ generated a spurious interrupt that can not be handled. |
- |
"No action is required. To avoid seeing this message in the future\n\ remove the unsupported card or use an image that supports it." |
|
PQUICC-3-UNKNOWN_SCC_TX_VECTOR |
3-Error |
PQUICC Unknown TX vector on port [dec] |
An internal software error occurred. |
- |
"Copy the error message exactly as it\n\ appears and report it to your technical support representative." |
|
PQUICC-3-UNKNOWN_SCCS |
3-Error |
PQUICC Incorrect SCC number |
An internal software error occurred. |
- |
"Call your technical support representative to obtain a software\n\ upgrade." |
|
PROCESS_CREATE_FAILED-3-MPLS_TE_HA |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
PROCESS_KILL-3-MPLS_TE_HA |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
PROCESS-3-LCON |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
PROTECTION-3-CREATE_TDLH_FAILURE |
3-Error |
Failed to create APSd [dec] handle |
Failed to create message handle for APSd communication. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
PROTECTION-3-DISPATCH_INIT_TDLH_FAILURE |
3-Error |
Failed to initialize dispatch path for APSd slot[dec] |
Failed to initialize dispatch path handle for APSd communication. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
PROTECTION-3-DOMAIN_TDLH_FAILURE |
3-Error |
[chars] rc = [dec] |
Failed to bind message handle for APSdcommunication. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
PROTECTION-3-NULL_DATA_STRUCTURE |
3-Error |
[chars] |
A software error occured and driver is not able to retrieve the data structure mentioned in the message. |
asr900-lotr-im |
LOG_STD_ACTION |
|
PROTECTION-3-NULL_PTR |
3-Error |
[chars] |
Failed to initialize. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
PROTECTION-3-PPG_HWID |
3-Error |
group[dec] bay[dec] port[dec] prot_type[dec] msg[chars] |
ppg hwid |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
PROTECTION-3-RESP_FAIL |
3-Error |
msg[chars] retval0x[hec] |
Failure response from APSd. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
PROTECTION-3-SEND_FAIL |
3-Error |
group%llu type[dec] msg[chars] errcode[dec] |
Failed to send message to APSd. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
PROTECTION-3-SEND_FAIL_SHUT |
3-Error |
slot[dec] bay[dec] port[dec] vt[dec] sts[dec] type[dec] msg[chars] errcode[dec] |
Failed to send shut message to APSd. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
PROTECTION-3-SETUP_TDLH_FAILURE |
3-Error |
Failed to set the alloc/free handler for APSd [dec] handle |
Failed to set the alloc/free handler for APSd communication. |
DDTS_COMPONENT |
LOG_STD_SH_TECH_ACTION |
|
PROTECTION-4-SEMAHOG |
4-Warning |
Process [dec] [chars] hogging [chars]! calling proc [dec] [chars] |
- |
- |
- |
|
PRP_MSG-4-PRP_VLANTAG |
4-Warning |
Warning: Please do not configure access mode for PRP interfaces with tagged supervision frames |
Supervision frames will be tagged with vlan id after user configured vlan tag and vlan id access mode will cause confliction on traffic |
iiot-sw-redundancy |
- |
|
PRP_MSG-4-PRP_VLANTAG |
4-Warning |
Warning: Please do not configure access mode for PRP interfaces with tagged supervision frames |
Supervision frames will be tagged with vlan id after user configured vlan tag and vlan id access mode will cause confliction on traffic |
petra-prp |
- |
|
PRP-4-NOMEM |
4-Warning |
Not enough memory available for [chars] |
The PRP could not obtain the memory it needed. |
prp |
LOG_STD_SH_TECH_ACTION |
|
PRST_IFS-3-FILE |
3-Error |
persistent media IFS file error: [chars] |
Persistent media module file system file error |
- |
LOG_STD_ACTION |
|
PRST_IFS-3-FILEMEM |
3-Error |
No memory to update [chars]. Please free some space |
There is no filesystem memory for the system to write an updated version of the persistent variable file. |
- |
"Please free space on the filesystem shown in the error message" " as soon as possible. This will involve deleting existing files" " and/or squeezing the filesystem if the filesystem requires it" " bootflash for example may require it." |
|
PRST_IFS-3-GENERAL |
3-Error |
persistent media IFS general error: [chars] |
Persistent media module file system general error |
- |
LOG_STD_ACTION |
|
PRST_VBL-3-GENERAL |
3-Error |
Persistent general error: [chars] |
Persistent variable general error |
- |
LOG_STD_ACTION |
|
PRST_VBL-3-MEDIA |
3-Error |
Persistent media error: [chars] |
Persistent variable error |
- |
LOG_STD_ACTION |
|
PSECURE_ISSU-2-GET_BUFFER |
2-Critical |
Port Security ISSU client failed to get buffer for message. Error: [dec] [chars] |
The Port Security 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. |
Port Security |
"show logging and show checkpoint client" |
|
PSECURE_ISSU-2-INIT |
2-Critical |
Port Security ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The Port Security 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. |
Port Security |
LOG_STD_ACTION |
|
PSECURE_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
Port Security ISSU client failed to send negotiation message. Error: [dec] [chars] |
The Port Security 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. |
Port Security |
"show logging and show checkpoint client" |
|
PSECURE_ISSU-2-SESSION_NEGO |
2-Critical |
Port Security ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The Port Security 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. |
Port Security |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
PSECURE_ISSU-2-SESSION_REGISTRY |
2-Critical |
Port Security ISSU client failed to register session information. Error: [dec] [chars] |
The Port Security ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
Port Security |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
PSECURE_ISSU-3-INVALID_SESSION |
3-Error |
Port Security ISSU client does not have a valid registered session. |
The Port Security ISSU client does not have a valid registered session. |
Port Security |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
PSECURE_ISSU-3-MSG_NOT_OK |
3-Error |
Port Security ISSU client Message Type [dec] is not compatible |
The Port Security ISSU client received an incompatible message from the peer device. The message cannot be processed. |
Port Security |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
PSECURE_ISSU-3-MSG_SIZE |
3-Error |
Port Security ISSU client failed to get the MTU for Message Type [dec] . Error: [dec] [chars] |
The Port Security ISSU client failed to calculate the MTU for the specified message. The Port Security ISSU client is not able to send the message to the standby device. |
Port Security |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
PSECURE_ISSU-3-SESSION_UNREGISTRY |
3-Error |
Port Security ISSU client failed to unregister session information. Error: [dec] [chars] |
The Port Security ISSU client failed to unregister session information. |
Port Security |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
PSECURE_ISSU-3-TRANSFORM_FAIL |
3-Error |
Port Security ISSU client [chars] transform failed for Message Type [dec] . Error: [dec] [chars] |
The Port Security 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 Port Security state between the active device and the standby device is not identical. |
Port Security |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
PSM-3-BADLABELADD |
3-Error |
Cannot add label - [chars]. |
Unable to create label due to reason given. |
mpls-psm |
LOG_STD_ACTION |
|
PSM-3-CHUNK |
3-Error |
[chars]: [chars] [hec] [hec] |
Parameterized Chunk Manager error occurred |
mpls-psm |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release. If not gather the output of <CmdBold>show version<NoCmdBold> " "<CmdBold>show running-config<NoCmdBold> and <CmdBold>show process memory<NoCmdBold> " "and contact your Cisco technical support representative." |
|
PSM-3-INVALIDPARAM |
3-Error |
Invalid parameter - [chars] |
Calling function has passed an invalid parameter. |
mpls-psm |
LOG_STD_ACTION |
|
PSM-3-ISSU_REG |
3-Error |
ISSU client [chars] [dec] entity [dec] failed ISSU registration: [chars] |
ISSU negotiation failed for this XDR client. |
mpls-psm |
"This error indicates a coding problem. It is an error that will occur" "every time this image is run and requires a code change to fix it." |
|
PSM-3-L2_PATH |
3-Error |
[chars] - path set 0x[hec]%p path [chars] |
Internal error while processing layer 2 path. |
mpls-psm |
LOG_STD_ACTION |
|
PSM-3-NONIPINFO |
3-Error |
Non-ip info: [chars] |
An internal software error occurred. |
mpls-psm |
LOG_STD_ACTION |
|
PSM-3-NOOCE |
3-Error |
Attempt to get labels from OCE failed - [chars]. |
Calling function has provided insufficient information to get labels. |
mpls-psm |
LOG_STD_ACTION |
|
PSM-3-NORESOURCE |
3-Error |
[chars] [dec] |
Resource Failure: [chars] [dec] |
mpls-psm |
LOG_STD_ACTION |
|
PT-3-BADRULEDELETE |
3-Error |
Error deleting ruleset %S [chars]. |
An internal software error occurred. |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
PT-3-BADRULEUNLOCK |
3-Error |
Invalid unlock on ruleset %S [chars]. |
An internal software error occurred. |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
PT-3-BADSCOPERATION |
3-Error |
Invalid [chars] of subcommand [dec] on ruleset %S. |
An internal software error occurred. |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
PT-3-NOOPERATION |
3-Error |
No [chars] operation defined for [chars] parameter [chars]. |
An internal data consistency error has been detected. |
- |
"Call your technical support representative for assistance." |
|
PT-3-PARAMRESULTERR |
3-Error |
PT ruleset %S protocol [chars] parameter [chars] parse error: [chars]. |
The final value of a ruleset's protocol/parameter string could not\n\ be decoded. |
- |
"Review the ruleset elements that set the parameter value to determine\n\ if they need to be modified to generate a valid result." |
|
PT-3-PARAMRESULTINVALID |
3-Error |
PT ruleset %S protocol [chars] parameter [chars] invalid: [chars]. |
A protocol parameter value generated by a ruleset was modified\n\ to be valid for protocol translation operation. |
- |
"Review the ruleset processing for the identified parameter to\n\ determine if it needs to be modified to generate a value that\n\ is for example within the range of values supported for PT." |
|
PT-3-PT_HW_UNAVAIL |
3-Error |
Protocol Tunneling hardware resource not available. [chars] |
Protocol tunneling could not be enabled because no redirect registers are available. Protocol Tunneling requires redirect registers |
cat6000-l2 |
"Disable any applications that uses redirect registers and try" "configuring the Protocol Tunneling again" |
|
PT-3-PT_NO_SWSB |
3-Error |
Protocol Tunneling software subblock not found. [chars] |
The software subblock that is used for protocol tunnelling could not be found for the port specified in the message text. Protocol tunnelling has been disabled on this port. |
cat6000-l2 |
LOG_STD_ACTION |
|
PT-6-INVOPERATION |
6-Information |
An invalid [chars] operation defined for [chars] parameter [chars]. |
A parameter evaluation error was detected for the specified ruleset\n\ operation and line. |
- |
"Call your technical support representative for assistance." |
|
PT-6-RULESETACCESS |
6-Information |
Ruleset [chars] refused an incoming connection due to the access-class. |
An incoming connection attempt that was matched by a\n\ Protocol Translation ruleset has been refused because the source\n\ address failed the ruleset's configured access-class test. |
- |
"The network administrator may need to verify that the ruleset\n\ access-class configuration is appropriate." |
|
PT-6-RULESETLIMIT |
6-Information |
Ruleset [chars] refused an incoming connection due to the max-user limit. |
An incoming connection attempt that would normally be processed\n\ by a Protocol Translation ruleset has been refused because of the\n\ ruleset's configured max-user limit. |
- |
"The network administrator may need to verify that the ruleset\n\ max-user limit is appropriate." |
|
PTCL-4-LDP |
4-Warning |
ERRMSG_NOFLAGS |
- |
- |
- |
|
PTCLREAD-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
PTHREAD_CREATE-3-L2VPN |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
PTP-4-CLK_INV_MASTER_PORT_SELECTED |
4-Warning |
slave clock port [chars] invalid master address [chars] is selected. Action is ignored because of the invalid master clock source. |
A master source address is selected which is either invalid or non-existent in the current list of master source addresses. |
ptp |
LOG_STD_ACTION |
|
PTP-6-CLK_MASTER_PORT_SELECTED |
6-Information |
slave clock port [chars] master address new:[chars] old:[chars] |
A slave port may associate with multiple master port addresses. This message describes the address of the selected master port. |
- |
LOG_STD_NO_ACTION |
|
PTP-6-CLK_STATUS_UPDATE |
6-Information |
Slave clock status changed to [chars] : [chars]. |
Clock status update for the Precision Timing Protocol |
ptp |
LOG_STD_NO_ACTION |
|
PTP-6-IOT_CLK_STATUS_UPDATE |
6-Information |
[domain:[dec]] Clock status changed to [chars] : [chars]. |
Clock status update for the Precision Timing Protocol |
iiot_rtr_timing |
LOG_STD_NO_ACTION |
|
PTRANSFORM-3-PROTO_VER_INCOMPAT |
3-Error |
Version of local Ptransform \nclient [chars] is incompatible with remote version [chars]. |
The protocol versions of the local and remote clients are\n\ incompatible. These clients can not communicate with each\n\ other. |
- |
"Use 'show version' and 'show ptransform clients' to help\n\ verify that the software images are incompatible. Upgrade\n\ the software images on each unit to versions that are \n\ compatible. " LOG_STD_RECUR_ACTION |
|
PUNT_INJECT-2-CAUSE_CFG_ERR |
2-Critical |
[chars] [chars] initialization failed |
Initialization of Punt/Inject cause failed due to invalid configuration parameters |
cpp-ucode |
LOG_STD_ACTION |
|
PUNT_INJECT-3-DROP_POLICY_SKIPPED |
3-Error |
[chars] cause=[dec] output drop policy skipped |
Output drop policy unexpected skipped on punt packet |
cpp-ucode |
LOG_STD_ACTION |
|
PUNT_INJECT-4-PUNT_ABATE |
4-Warning |
Punted packets from the dataplane to the control-plane of type [chars] cause# [dec] [chars] - are no longer being dropped |
- |
- |
- |
|
PUNT_INJECT-4-PUNT_ALERT |
4-Warning |
Punted packets from the dataplane to the control-plane of type [chars] cause# [dec] [chars] - are being dropped |
- |
- |
- |
|
PUNT_INJECT-5-DROP_GLOBAL_POLICER |
5-Notice |
global punt policer drops packet from [chars] |
drop punt packet by global punt policer |
cpp-ucode |
LOG_STD_ACTION |
|
PUNT_INJECT-5-DROP_PUNT_CAUSE |
5-Notice |
punt policer drops packets cause: [chars] 0x[hec] from [chars] [chars] |
- |
- |
- |
|
PUNT_INJECT-5-DROP_PUNT_INTF |
5-Notice |
punt interface policer drop packet from [chars] cause [chars] 0x[hec] |
- |
- |
- |
|
PW_STATUS_LOST-5-XCONNECT |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
PW_STATUS-5-XCONNECT |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
PW_WATCHER-3-NO_RESPONSE_STARTUP_REQ |
3-Error |
Portware Watcher detected a missing modem board startup message for slot [dec]. Resetting the slot |
The slot did not send a startup msg after a given amount of retries\n\ requesting it. This can happen if after a router shelf reload the\n\ feature was not redownloaded with a new image and the NIP_MODEM_MNGR\n\ client's port was not reinitialised correctly and stayed closed. This\n\ should not be considered a critical problem by the customer as\n\ it should not affect the operation of the router. |
- |
"Copy the output of the message as well as a description of events\n\ leading up to the message and open a DDTS." |
|
PW_WATCHER-6-UNEXPECTED_DOWNLOAD |
6-Information |
Portware Watcher detected an unregistered module download in slot [dec] module [dec]. |
This is an informational message indicating that the portware watcher\n\ process had not been initialised with the slot and module information\n\ to monitor the download. This in no way affects the operation of the\n\ module or the system in general and should not be considered a \n\ serious problem. |
- |
"Copy the output of the message as well as a description of events\n\ leading up to the message and open a DDTS." |
|
PW-3-IPC_ALLOC_FAILED |
3-Error |
[chars] |
Allocation of an IPC packet buffer by the pseudo wired feature failed. |
cpp-ucode |
LOG_STD_ACTION |
|
PW-3-IPC_SEND_FAILED |
3-Error |
[chars] |
Transmission of an IPC message by the pseudo wire feature failed. |
cpp-ucode |
LOG_STD_ACTION |
|
PWD_SYNC -2-INITSYS |
2-Critical |
[chars] |
A software error occurred during initialization of the Password Sync RF subsystem |
- |
"Check for sufficient processor memory." LOG_STD_ACTION |
|
PWD_SYNC-3-INVALID_MSG |
3-Error |
Incorrectly formatted message 0x[hec] 0x[hec] received by [chars] |
Inconsistent message data was received from the peer CPU possibly due to an incompatible image version. |
- |
LOG_STD_ACTION |
|
PWD_SYNC-3-NO_BUFFER |
3-Error |
Unable to transmit message type [dec] from [chars] |
A transmit error occurred while sending msg to other CPU due to non-availability of buffer |
- |
LOG_STD_ACTION |
|
PWD_SYNC-3-SUBSYS_COMPAT |
3-Error |
Standby is missing the Password Sync subsystem hence Standby will not have password protection for the privilaged mode. |
Standby CPU software subsystem is older or missing. See message text for software subsystem type. May result in feature losses in the event of a switchover. |
- |
"May require a software upgrade on the Standby CPU. " LOG_STD_ACTION |
|
PWD_SYNC-3-TRANSMIT_ERROR |
3-Error |
Unable to transmit message type [dec] from [chars] |
A transmit error occurred while sending msg to other CPU due to msg translation |
- |
LOG_STD_ACTION |
|
PWD_SYNC-3-UNKNOWN_MSG |
3-Error |
Unknown message type 0x[hec] received by [chars] |
An unknown message type was received from the peer CPU possibly due to an incompatible image version. |
- |
LOG_STD_ACTION |
|
PWD_SYNC-5-UNSUPPORTED_MSG |
5-Notice |
Msgtype [chars] sent by [chars] unsupported by peer. |
Peer responded that it didn't recognize a message sent by this CPU possibly due to a different image version. |
- |
"May require a software upgrade on the Standby CPU. " LOG_STD_ACTION |
|
PWD_SYNC-6-CONSOLE_TIMEOUT_SYNC_MSG |
6-Information |
Console EXEC Timeout successfully synced to Standby |
Active CPU successfully synced console exec timeout to Standby CPU |
- |
LOG_STD_NO_ACTION |
|
PWD_SYNC-6-SYNC_MSG |
6-Information |
Successfully Synced [chars] Password. |
Active CPU successfully synced the password to Standby CPU |
- |
LOG_STD_NO_ACTION |
|
PWD-4-LDP |
4-Warning |
ERRMSG_NOFLAGS |
- |
- |
- |
|
PWDCFG-5-LDP |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
PWDKEYTRUNC-5-LDP |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
PWDRO-5-LDP |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
QA-3-ALLOC |
3-Error |
[chars] |
This is a software error. |
- |
"Copy the error message exactly as it appears. Also copy the output of show version and show cont cbus. Contact your technical support representative." |
|
QA-3-DIAG |
3-Error |
NULL |
This is a diagnostic message. |
- |
"This message appears after a QA error and contains diagnostic information regarding that error. Copy the original QA error message and all the following QA diagnostic error messages exactly as they appear. Also copy the output of show version and show cont cbus. Contact your technical support representative." |
|
QAT15_CRYPTO-0-SELF_TEST_FAILURE |
0-Emergency |
Encryption self-test failed. |
One of the encryption self-tests has failed. The encryption engine is not operable in this state. |
- |
"If the failure persists contact Cisco to " "obtain a replacement IOS image." |
|
QAT15_CRYPTO-1-ALIGN |
1-Alert |
[chars] Alignment failure on packet buffer: 0x%08x |
A software error occurred. The Qat15 driver detected that the buffer is not aligned correctly. |
- |
LOG_STD_ACTION |
|
QAT15_CRYPTO-1-ERROR |
1-Alert |
[chars] |
An error occured in the application using Qat15 crypto Module. |
- |
LOG_STD_ACTION |
|
QAT15_CRYPTO-3-CRYPTO_ENGINE_INIT |
3-Error |
Qat15 crypto failed to register with crypto engine infrastructure. |
Qat15 crypto engine failed to initialize. |
- |
LOG_STD_ACTION |
|
QAT15_CRYPTO-3-INIT |
3-Error |
Qat15 crypto failed to initialize. |
Qat15 crypto engine failed to initialize. |
- |
LOG_STD_ACTION |
|
QAT15_CRYPTO-3-NO_BUFFER |
3-Error |
No buffer to service request. |
The dynamic buffer pool has depleted. Request cannot be serviced. |
- |
LOG_STD_ACTION |
|
QAT15_CRYPTO-3-OVER_SUBSCRIBED |
3-Error |
Cryptographic packet rate temporary exceeded capacity. |
The crypto engine cannot handle the volumne of traffic. Request cannot be serviced. |
- |
LOG_STD_ACTION |
|
QAT15_CRYPTO-3-RING_FULL |
3-Error |
Crypto buffer descriptor ring full. |
The buffer descriptor ring is full. Request cannot be serviced. |
- |
LOG_STD_ACTION |
|
QAT15_CRYPTO-3-UNSUPPORTED |
3-Error |
[chars] not unsupported. |
An unsupported operation was invoked. |
- |
LOG_STD_ACTION |
|
QAT15_CRYPTO-6-SELF_TEST_RESULT |
6-Information |
Self test info: [chars] |
This audit prompt the results of Cryptographical seltftests |
- |
"This message is for information only. No action is " "required." |
|
QATM-2-ASDATA_READ |
2-Critical |
Cannot read TCAM associated data |
Possibly bad hardware |
hardware |
LOG_STD_ACTION |
|
QATM-2-ASDATA_WRITE |
2-Critical |
Cannot write TCAM associated data |
Possibly bad hardware |
hardware |
LOG_STD_ACTION |
|
QATM-2-TCAM_READ |
2-Critical |
Cannot read TCAM |
Possibly bad hardware |
hardware |
LOG_STD_ACTION |
|
QATM-2-TCAM_WRITE |
2-Critical |
Cannot write the TCAM |
Possibly bad hardware |
hardware |
LOG_STD_ACTION |
|
QBM-3-QBM_CONSISTENCY |
3-Error |
QBM internal error: [chars] |
An action attempted by the QoS Bandwidth Manager implementation encountered an unexpected software condition |
qbm |
"Search the Bug Toolkit " BUG_TOOLKIT " for existing bugs and " "upgrade the software if necessary. If there is still a " "problem copy the error message exactly as it appears on the " "console or in the system log. Issue the <CmdBold>show qbm " "client<NoCmdBold> <CmdBold>show qbm pool<NoCmdBold> " "<CmdBold>show running<NoCmdBold> and <CmdBold>show version" "<NoCmdBold> commands to gather data which may help identify " "the nature of the error. Then open a case with the Technical " "Assistance Center via the Internet " TAC_CASE_OPEN " or " "contact your Cisco technical support representative and " "provide the representative with the gathered information." |
|
QEM-3-DISCOVER |
3-Error |
Found [chars] switch processors |
The QEM driver found either no switch processors or more than one. Exactly one is the only supported configuration. |
- |
"Make sure there is only one switch processor." |
|
QFP_ETH-3-VLAN_BIND_XCONN_CONFIG_ERR |
3-Error |
Cannot apply VLAN encap configuration if main interface is configured for xconnect port-forwarding. Check configuration of [chars] remove any xconnect port-forwarding configuration and reapply VLAN encap configuration. |
A main interface set in xconnect port-forwarding mode will reject VLAN encap configurations. |
- |
LOG_STD_NO_ACTION |
|
QFP_FNF-4-FNF_MEM_UPLIMIT_CLEAR |
4-Warning |
Netflow and Flexible Netflow configuration is using %PRIu64 bytes |
Configured Netflow and Flexible Netflow records are now using less than the recomended maximum of total DRAM. |
- |
LOG_STD_NO_ACTION |
|
QFP_FNF-4-FNF_MEM_UPLIMIT_WARN |
4-Warning |
Netflow and Flexible Netflow configuration is using %PRIu64 bytes |
Configured Netflow and Flexible Netflow records are using more than the recomended maximum of total DRAM. |
- |
LOG_STD_NO_ACTION |
|
QFP_MLP-2-BQS_SCRATCH_TOOSMALL |
2-Critical |
QFP BQS Scratch area too small for MLP feature usage size: [dec] need: [dec]. |
Cisco internal software error. QFP MLP initialization detected that the BQS scratch memory area is insufficient for MLP usage. The MLP Bundle interfaces will not be functional while this condition exists. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-2-PROXY_IPC_INIT_FAILED |
2-Critical |
QFP MLP Proxy IPC interface initialization failure result: [dec]. |
Cisco internal software error. QFP MLP initialization detected that the Proxy IPC interface initialization failed. The MLP Bundle interfaces will not be functional while this condition exists. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-EARLY_RX_CLEANUP |
3-Error |
QFP MLP Early Receive cleanup error [chars] |
Cisco internal software error. Multilink Early Receive cleanup could not be performed due to indicated error. This could cause possible QFP memory leak. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-EARLY_RX_INIT |
3-Error |
QFP MLP Early Receive initialization error [chars] |
Cisco internal software error. Multilink Early Receive initialization could not be performed due to indicated error. This could cause possible lost MLP encapsulated packets during member link/bundle bringup and possibly cause the failure to complete member link/bundle initialization. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-INV_PROXY_MSG |
3-Error |
QFP MLP Proxy received invalid Message ID [dec] |
Cisco internal software error. QFP MLP Proxy received an invalid Message ID. This message will be ignored. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-MCMP_INVALID_RX_CLASS |
3-Error |
MLP MCMP suspension class ID [dec] received from the peer |
Possible error on the peer device with PPP Multilink Multiclass MCMP. Received MLP packet contained a MCMP suspension class ID |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-MCMP_TX_ENCAP_SEQ_CFG_ERROR |
3-Error |
MLP QoS encap-sequence [dec] must be less than the number |
User software configuration mismatch with PPP Multilink Multiclass MCMP. User needs to either reduce the highest encap-sequence in |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-MLP_INVALID_EVSI_INTF_STATE |
3-Error |
MLP Link Add/Update receved with invalid EVSI indication for Member Link: [chars] Bundle: [chars] |
Either the user attempted to mix broadband and non-broadband member links on the same bundle or an internal error has occurred processing a configuration update. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-PROXY_B_TX_IDLE_LINK_TRANSITION |
3-Error |
QFP MLP Proxy [chars] [chars] invalid Bundle state [chars] [dec] for |
Cisco internal software error. Multilink Idle-Link transition could not be made due invalid Bundle state at the time of the request. The associated MLP Bundle interface may not be fully functional as a result of this condition. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-PROXY_DUP_LINK_ID |
3-Error |
QFP MLP Proxy [chars] [chars] duplicate Link ID [dec] for interface [chars] |
Cisco internal software error. QFP MLP Proxy message Link Add could not be processed for the indicated interface due use of a given Link ID on multiple member links within the same MLP Bundle. The associated MLP Bundle interface may not be fully functional as a result of this condition. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-PROXY_INV_BUFFER_LIMIT |
3-Error |
QFP MLP Proxy [chars] [chars] indicated an invalid Rx buffer limit |
Cisco internal software error. QFP MLP was provided a invalid Rx buffer limit value. The associated MLP Bundle interface may not be fully functional as a result of this condition. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-PROXY_INV_BUNDLE_STATE |
3-Error |
QFP MLP Proxy [chars] [chars] invalid Bundle state [chars] [dec] for |
Cisco internal software error. QFP MLP Proxy message could not be processed due to the MLP Bundle being in an incorrect state to accept the message. The associated MLP Bundle interface may not be fully functional as a result of this condition. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-PROXY_INV_CLASS_INFO |
3-Error |
QFP MLP Proxy [chars] [chars] invalid Class Info Base: 0x%08x Num: [dec] |
Cisco internal software error. QFP MLP Proxy message contained invalid MLP Class information. The associated MLP Bundle interface may not be fully functional as a result of this condition. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-PROXY_INV_LINK_ID |
3-Error |
QFP MLP Proxy [chars] [chars] invalid Link ID [dec] for interface [chars] |
Cisco internal software error. QFP MLP Proxy message Link Add could not be processed for the indicated interface due to an invalid Link ID. The associated MLP Bundle interface may not be fully functional as a result of this condition. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-PROXY_INV_LINK_STATE |
3-Error |
QFP MLP Proxy [chars] [chars] invalid Link state [chars] [dec] for |
Cisco internal software error. QFP MLP Proxy message could not be processed due to the MLP Link being in an incorrect state to accept the message. The associated MLP Bundle interface may not be fully functional as a result of this condition. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-PROXY_INV_LOST_FRAG_TO |
3-Error |
QFP MLP Proxy [chars] [chars] indicated an invalid lost fragment |
Cisco internal software error. QFP MLP was provided a invalid lost fragment timeout value. The associated MLP Bundle interface may not be fully functional as a result of this condition. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-PROXY_INV_MRRU |
3-Error |
QFP MLP Proxy [chars] [chars] invalid MRRU [dec] for interface [chars] |
Cisco internal software error. QFP MLP Proxy message contained an invalid MLP Bundle MRRU. The associated MLP Bundle interface may not be fully functional as a result of this condition. Possible workaround is to reduce the interface mtu on the Multilink bundle interface on both ends of the connection to 9216 or less and then shut/no shut the Multilink bundle interface to force renegotiation of the MLP MRRU. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-PROXY_INV_RX_TX_INTF_VALUE |
3-Error |
QFP MLP Proxy [chars] [chars] invalid Rx/Tx interface value [dec] for |
Cisco internal software error. QFP MLP Proxy was unable to complete the requested MLP Bundle state change or configuration update due to an invalid interface Rx/Tx designation in the proxy request. The associated MLP Bundle interface may not be fully functional as a result of this condition. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-PROXY_INV_SUB_DEV_ID |
3-Error |
QFP MLP Proxy [chars] [chars] invalid Sub-Device ID [dec] for interface [chars] |
Cisco internal software error. QFP MLP Proxy message Bundle Add could not be processed for the indicated interface due to an invalid Sub-Device ID. The associated MLP Bundle interface may not be fully functional as a result of this condition. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-PROXY_INV_TX_LINK_FRAG_SIZE |
3-Error |
QFP MLP Proxy [chars] [chars] indicated an invalid Tx Link optimal |
Cisco internal software error. QFP MLP Proxy message contained invalid Tx Link optimal fragment size information. The associated MLP Member Link and/or Bundle interface may not be fully functional as a result of this condition. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-PROXY_INV_TX_LINK_WEIGHT |
3-Error |
QFP MLP Proxy [chars] [chars] indicated an invalid Tx Link weight |
Cisco internal software error. QFP MLP Proxy message contained invalid Tx Link weight information. The associated MLP Member Link and/or Bundle interface may not be fully functional as a result of this condition. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-PROXY_IPC_ALLOC_FAIL |
3-Error |
QFP MLP Proxy [chars] response lost due to buffer allocation |
Cisco internal software error. QFP MLP Proxy message processing detected a IPC buffer allocation failure during response processing. The associated MLP interface may not be fully functional as a result of this condition. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-PROXY_LAI_TX_IDLE_LINK_TRANSITION |
3-Error |
QFP MLP Proxy [chars] [chars] invalid Link state [chars] [dec] for |
Cisco internal software error. Multilink Idle-Link transition could not be made due invalid Link state at the time of the request to convert the link to an Idle-Link. The associated MLP Bundle interface may not be fully functional as a result of this condition. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-PROXY_LIA_TX_IDLE_LINK_TRANSITION |
3-Error |
QFP MLP Proxy [chars] [chars] invalid Link state [chars] [dec] for |
Cisco internal software error. Multilink Idle-Link transition could not be made due invalid Link state at the time of the request to convert the Idle-Link to an active link. The associated MLP Bundle interface may not be fully functional as a result of this condition. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-PROXY_NULL_BUNDLE |
3-Error |
QFP MLP Proxy [chars] [chars] NULL Bundle sub-block for interface [dec] |
Cisco internal software error. QFP MLP Proxy was unable to complete the requested MLP Bundle state change or configuration update due to an invalid or uninitialized Bundle sub-block. The associated MLP Bundle interface may not be fully functional as a result of this condition. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-PROXY_NULL_LINK |
3-Error |
QFP MLP Proxy [chars] [chars] NULL Member Link sub-block for |
Cisco internal software error. QFP MLP Proxy was unable to complete the requested MLP Member Link state change or configuration update due to an invalid or uninitialized Member Link sub-block. The associated MLP Member Link interface may not be fully functional as a result of this condition. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-PROXY_SID_UPDATE_COMPLETE_ERROR |
3-Error |
QFP MLP Proxy [chars] SID Update Complete w/o Preceeding Lock |
Cisco internal software error. QFP MLP Proxy message processing detected a Bundle Schedule SID update sequence error. One or more interface schedules could have been affected. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-3-PROXY_SID_UPDATE_LOCK_ERROR |
3-Error |
QFP MLP Proxy [chars] Multiple SID Update Locks to same interface |
Cisco internal software error. QFP MLP Proxy message processing detected a Bundle Schedule SID update sequence error. One or more interface schedules could have been affected. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-4-PROXY_IPC_ALLOC_FAIL2 |
4-Warning |
QFP MLP Proxy [chars] response lost due to buffer allocation |
Cisco internal software error. QFP MLP Proxy message processing detected a IPC buffer allocation failure during proxy response processing. The associated MLP functionality may not be fully functional as a result of this condition. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-4-PROXY_SYNC |
4-Warning |
QFP MLP Proxy [chars] [chars] Bundle/Link sync issue with interface [chars] |
Cisco internal software error. QFP MLP Proxy message processing detected a Bundle-Link state synchronization abnormality. This condition should be cosmetic. Full context of the message will aid in problem isolation. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-4-TX_BUNDLE_FLOWED_OFF |
4-Warning |
QFP MLP Tx Bundle [chars] flowed OFF for an abnormal duration due to one or more congested member links Ticks: [dec] |
Possible Cisco internal software or hardware error. QFP MLP Tx processing detected that a MLP Bundle interface was flowed off for an extended period of time due to a congested member link queue. The associated MLP Bundle interface may not be fully functional as a result of this condition. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-4-TX_BUNDLE_FLOWED_ON |
4-Warning |
QFP MLP Tx Bundle [chars] flowed ON after being flowed OFF for an abnormal duration Ticks: [dec] |
Possible Cisco internal software or hardware error. QFP MLP Tx processing detected that a MLP Bundle interface was flowed off for an extended period of time due to a congested member link queue. The associated MLP Bundle interface may not be fully functional as a result of this condition. |
qfp-mlppp keyword:none |
LOG_STD_ACTION |
|
QFP_MLP-4-TX_BUNDLE_LOOP |
4-Warning |
QFP detected re-entry into MLP Tx Bundle [chars]. |
- |
- |
- |
|
QFP_PLAT-3-PLATFORM_THPUT_INVALID |
3-Error |
Throughput setting [chars]/[chars] %PRIu64 is invalid |
The throughput property is invalid. The forwarding engine cannot operate without a valid throughput. |
qfp-driver |
LOG_STD_DDTS_TAC_DETAILS |
|
QFP_PLAT-3-PLATFORM_THPUT_INVALID |
3-Error |
Throughput setting [chars]/[chars] %PRIu64 is invalid |
The throughput property is invalid. The forwarding engine cannot operate without a valid throughput. |
qfp-driver |
LOG_STD_DDTS_TAC_DETAILS |
|
QFP_PLAT-3-PLATFORM_THPUT_INVALID |
3-Error |
Throughput setting [chars]/[chars] %PRIu64 is invalid |
The throughput property is invalid. The forwarding engine cannot operate without a valid throughput. |
qfp-driver |
LOG_STD_DDTS_TAC_DETAILS |
|
QFP_PLAT-3-PLATFORM_THPUT_MISSING |
3-Error |
Throughput setting [chars]/[chars] is missing |
The throughput property is missing. The forwarding engine cannot operate without a valid throughput. |
qfp-driver |
LOG_STD_DDTS_TAC_DETAILS |
|
QFP_PLAT-3-PLATFORM_THPUT_MISSING |
3-Error |
Throughput setting [chars]/[chars] is missing |
The throughput property is missing. The forwarding engine cannot operate without a valid throughput. |
qfp-driver |
LOG_STD_DDTS_TAC_DETAILS |
|
QFP_PLAT-3-PLATFORM_THPUT_MISSING |
3-Error |
Throughput setting [chars]/[chars] is missing |
The throughput property is missing. The forwarding engine cannot operate without a valid throughput. |
qfp-driver |
LOG_STD_DDTS_TAC_DETAILS |
|
QFP_TUN-3-TUN_MODE_CONFIG_ERR |
3-Error |
Detected unsupported tunnel mode [chars] configuration. |
An unsupported tunnel mode has been configured. |
- |
LOG_STD_NO_ACTION |
|
QFP_XCONNECT-3-XCONNECT_CONFIG_ERR |
3-Error |
Cannot configure xconnect port-forwarding on [chars] if there are subinterfaces present with VLAN encaps. Remove all subinterface configurations before configuring xconnect port-forwarding. |
A main interface cannot be configured for xconnect port-forwarding if subinterfaces with VLAN encaps are present. |
- |
LOG_STD_NO_ACTION |
|
QFPOOR-2-LOWRSRC_PERCENT_CRIT |
2-Critical |
QFP [dec] [chars] at [dec] percent exceeds critical level [dec] |
A QFP resource has dropped below a critical level. |
- |
LOG_STD_NO_ACTION |
|
QFPOOR-4-LOWRSRC |
4-Warning |
QFP [dec] [chars] resource low - [dec] depleted |
A QFP resource has dropped below a critical level. |
- |
LOG_STD_NO_ACTION |
|
QFPOOR-4-LOWRSRC_PERCENT_WARN |
4-Warning |
QFP [dec] [chars] at [dec] percent exceeds warning level [dec] |
A QFP resource has dropped below a critical level. |
- |
LOG_STD_NO_ACTION |
|
QFPOOR-4-TOP_EXMEM_USER |
4-Warning |
EXMEM_USER: [chars] Allocations: [dec] Bytes-Alloc: [dec] Bytes-Total: [dec] |
TOP QFP Exmem user when resource has dropped below a critical level. |
- |
LOG_STD_NO_ACTION |
|
QFPOOR-5-RSRC |
5-Notice |
QFP [dec] [chars] resource recovered - [dec] depleted |
A QFP resource has recovered from the critical level. |
- |
LOG_STD_NO_ACTION |
|
QFPOOR-5-RSRC_PERCENT |
5-Notice |
QFP [dec] [chars] resource recovered - [dec] percent depleted |
A QFP resource has recovered from the critical level. |
- |
LOG_STD_NO_ACTION |
|
QFPPALCI-4-UNEXP_CHIP_REV |
4-Warning |
QFP[dec].[dec] chip [chars] reported unexpected revision 0x%X using [dec].[dec] instead |
The named chip making up part of the QFP engine reported an unexpected chip revision. The system continued running assuming a default revision. |
qfp-driver |
"Monitor the QFP forwarding engine for stability and performance issues." "If you notice anything unusual copy the error message " "exactly as it appears on the console or in the system log. " "Research and attempt to resolve the error using the Output " "Interpreter " OUTPUT_INTERPRETER ". Also perform a search of the Bug " "Toolkit " BUG_TOOLKIT ". If you still require assistance open a case with" " the Technical Assistance Center via the Internet " TAC_CASE_OPEN " or " "contact your Cisco technical support representative and provide the " "representative with the gathered information." |
|
QLLC-3-BAD_XID |
3-Error |
Sna configuration error for [enet]: Lan device is PU2.1 X.25 device is PU2.0 XID Format 1 |
- |
- |
"Check the revision levels on the external equipment and\n\ upgrade them if necessary." |
|
QLLC-3-BADOPCODE |
3-Error |
Opcode [chars] is invalid |
Either remote source-route bridging or local acknowledgment is\n\ configured incorrectly. |
- |
"Verify that remote source-route bridging and local acknowledgment are\n\ configured correctly." |
|
QLLC-3-BADQLLCSTATE |
3-Error |
Bad qllc state - [chars] |
An invalid QLLC primitive was detected. |
- |
"Verify that the partner QLLC device is configured correctly." |
|
QLLC-3-BADRSRBOPCODE |
3-Error |
Bad opcode %04x from [enet] to [enet] |
Either remote source-route bridging is incorrectly configured or the\n\ other RSRB device is down. |
- |
"Verify that remote source-route bridging is configured correctly with\n\ the right version of the IOS software." |
|
QLLC-3-BADSTATE |
3-Error |
Bad qllc state - [chars] - [enet] |
An invalid LLC primitive was detected. |
- |
"Verify that the Token Ring ports and any participating LAN devices are\n\ configured correctly." |
|
QLLC-3-BADSTATEEVENT |
3-Error |
Bad qllc state - [chars] event - [chars] macaddr - [enet] |
The LLC primitive specified placed the router in an invalid state. |
- |
"Verify that the Token Ring ports and any participating LAN devices are\n\ configured correctly." |
|
QLLC-3-DIFFPRTR |
3-Error |
[enet] - Different partner - originally [enet] - now [enet] |
The partner for this QLLC virtual MAC address does not match the MAC\n\ address that was defined with the qllc partner command. |
- |
"Verify that the qllc partner statement in the configuration file is\n\ correct." |
|
QLLC-3-GENERRMSG |
3-Error |
[chars] |
The text string provided with this error message describes the\n\ specific QLLC problem. |
- |
"Follow the instructions that appear with the error message. Copy the\n\ error message exactly as it appears and report it to your technical\n\ support representative." |
|
QLLC-3-IFRAME |
3-Error |
[chars] |
An I-Frame was discarded due to network congestion. |
- |
"Verify that the LAN is not beaconing and that it is not in a congested\n\ state. Copy the error message exactly as it appears and report it to\n\ your technical support representative." |
|
QLLC-3-INCALL_CFG |
3-Error |
Incoming call: No QLLC Service Access Point Configured for x.25 subaddress [chars] |
A remote X.25 device is calling the router for QLLC service using a\n\ subaddress that was not configured by the X.25 routing facility. The\n\ subaddress was not configured for QLLC service. |
- |
"Correct the QLLC configuration. Configure only the subaddress on the\n\ QLLC service not the complete X.121 address that the remote X.25\n\ device uses." |
|
QLLC-3-INCALL_NO_PARTNER |
3-Error |
Incoming call: No partner Mac Address configured - X.25 subaddress [chars] |
There is an incoming call but a connection cannot be initiated \n\ to a partner since no partner is configured in a \qllc dlsw\ \n\ command for QLLC/DLSw+ only. |
- |
"Configure a partner for the incoming calling such as using the \n\ \"qllc dlsw partner\" command." |
|
QLLC-3-LNXNOTFOUND |
3-Error |
lnx_remove_macaddr_hash did not find target lnx |
The qllc srb command was not defined for this interface. |
- |
"Add a valid qllc srb statement for this serial interface." |
|
QLLC-3-NO_QLLCBUFFER |
3-Error |
M bit Reassembly failed - couldn't allocate a packet |
The router ran out of memory to allocate buffers. |
- |
"Make sure that the router configuration is adequate for the service\n\ expected of it. You might want to tune the buffer pools or upgrade to\n\ a larger router. At the very least you will need more memory." |
|
QLLC-3-NO_QSR |
3-Error |
No QLLC Service Access Points defined |
No QLLC services have been configured even though the router will\n\ accept incoming calls for QLLC. |
- |
"Configure the QLLC service required." |
|
QLLC-3-NO_RESOURCE |
3-Error |
Incoming Call: Insufficient resources available |
This message is reporting insufficient system memory. |
- |
"Upgrade the memory." |
|
QLLC-3-NOLLC2 |
3-Error |
Unable to open an llc2 session |
An LLC2 session could not be established with the destination MAC\n\ address. |
- |
"Verify that the qllc partner statement in the configuration file is\n\ correct and that the partner is on the desired LAN." |
|
QLLC-3-NOMACADDR |
3-Error |
No lnx entry for macaddr [enet] |
No virtual MAC address was defined for this interface. |
- |
"Define the virtual MAC address using either the x25 map qllc or the\n\ x25 pvc qllc command." |
|
QLLC-3-NOMEM |
3-Error |
Not enough memory available |
There is not enough memory in the system to complete this request. |
- |
"Add more memory to the router. Otherwise reduce the configuration or\n\ the load on the router." |
|
QLLC-3-NONULLXID |
3-Error |
Couldn't make null xid - [enet] -[enet] |
An attempt to create an IEEE XID failed. |
- |
"Verify that the qllc partner statement in the configuration file is\n\ correct and that the partner is on the desired LAN." |
|
QLLC-3-NOPAKENQ |
3-Error |
Pak enqueue failed |
A packet was not sent to the LAN. |
- |
"Verify that the LAN partner is configured correctly and that the\n\ partner is on the desired LAN." |
|
QLLC-3-NOXID2 |
3-Error |
Couldn't make xid - [enet] -[enet] |
The QLLC XID could not be forwarded to the LAN. |
- |
"Verify that the qllc partner and the qllc xid commands are correct." |
|
QLLC-3-NULLPTR |
3-Error |
[chars] ptr is null |
The specified structure was not configured. |
- |
"Confirm the configuration commands for the structure." |
|
QLLC-3-PARTNER_MISMATCH |
3-Error |
Outgoing call: Partner Mac Address [enet] doesn't match configured partner [enet] |
- |
- |
"Correct the QLLC configuration to match the right partner." |
|
QLLC-3-QLLCMAP_ERR |
3-Error |
Incoming call: QLLC map entry not found |
A software error in the router code occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
QLLC-4-NOQLLC |
4-Warning |
Unable to open qllc session current state is [chars] |
A QLLC session could not be established. |
- |
"Verify that the qllc partner and the qllc xid commands are correct." |
|
QM-4-ACTION_NOT_SUPPORTED |
4-Warning |
Action is not supported in policymap [chars] |
This message means that an action other than the set trust and police policy-map class configuration commands was configured in a policy map. This is a hardware limitation. |
hardware |
"Configure only the supported actions of set trust and police when in " "policy-map class configuration mode." |
|
QM-4-CLASS_NOT_SUPPORTED |
4-Warning |
Classification is not supported in classmap [chars] |
This message means the an unsupported match class-map configuration command was configured in a policy map and attached to an egress interface or that more than one match command was configured. This is a hardware limitation. |
hardware |
"Reconfigure the class map or the policy map. Use only the match ip dscp dscp-list " "class-map configuration command in a policy map that is attached to an egress " "interface. Only one match per class map is supported." |
|
QM-4-HARDWARE_NOT_SUPPORTED |
4-Warning |
Hardware limitation has reached for policymap [chars] |
The policy map configuration has exceeded the limitation of the hardware. You configured more QoS ACL entries than the number specified in the Switch Database Management sdm template. |
hardware |
"Reconfigure the class map or the policy map and reduce the number of QoS ACLs." |
|
QM-4-MATCH_NOT_SUPPORTED |
4-Warning |
Match type is not supported in classmap [chars] |
match ACL match ip dscp and match ip precedence are the match types that are supported |
firmware |
- |
|
QM-4-NOT_SUPPORTED |
4-Warning |
Action '[chars]' is not supported for a policymap attached to output side. |
This message means that a set or trust policy-map class configuration command was configured in a policy map and attached to an egress interface. A warning message is logged and the actions do not take affect. This is a hardware limitation. |
hardware |
"Do not configure a set or trust policy-map class configuration command in a " "policy map and attach it to an egress interface. These policy-map actions " "are supported only on ingress interfaces." |
|
QM-4-POLICER_NOT_SUPPORTED |
4-Warning |
Number of policers has exceeded hardware limitation for policymap [chars] |
The policy map configuration has exceeded the limitation of the hardware. You configured more policers in a policy map by using the police or police aggregate policy-map class configuration command |
hardware |
"Reconfigure the class map or the policy map and reduce the number of policers." |
|
QM-4-POLICING_RATE_NOT_SUPPORTED |
4-Warning |
Policer configuration has exceeded hardware limitation for policymap [chars] |
The policy map configuration has exceeded the limitation of the hardware. You configured a larger policing rate or burst size in a policy map by using the police or police aggregate policy-map class configuration command than supported. |
hardware |
"Reconfigure the class map or the policy map and reduce the policing rate or " "burst size." |
|
QM-4-UNEXPECTED_INTERNAL_QOS_CONDITION |
4-Warning |
Unexpected internal QoS condition. |
This message means that an unexpected internal QoS condition has occurred. QoS debug may be enabled to obtain more information in case the condition recurs. |
firmware |
LOG_STD_ACTION |
|
QOS_CLI_DEPRECATE-4-CUSTOM_QUEUE |
4-Warning |
Custom Queue list on interface has been deprecated. Use equivalent MQC bandwidth command |
The issued interface custom queue list command has been deprecated by the MQC commands.\n |
- |
"Configure a policy with bandwidth and attach to " "the interface\n" |
|
QOS_CLI_DEPRECATE-4-FAIR_QUEUE |
4-Warning |
Fair Queue on interface has been deprecated. Use equivalent MQC fair-queue command |
The issued interface fair queue command has been deprecated by the MQC commands.\n |
- |
"Configure a policy with fair-queue and attach to " "the interface\n" |
|
QOS_CLI_DEPRECATE-4-FR_ADAPTIVE_SHAPE |
4-Warning |
frame relay adaptive-shaping has been deprecated. Use equivalent MQC priority command |
The issued interface shape command has been deprecated by the MQC commands.\n |
- |
"Configure a policy with shape and attach to " "the interface\n" |
|
QOS_CLI_DEPRECATE-4-FR_CBS |
4-Warning |
Frame relay bc command has been deprecated. Use equivalent MQC priority command |
The issued frame-relay bc command has been deprecated by the MQC commands.\n |
- |
- |
|
QOS_CLI_DEPRECATE-4-FR_CIR |
4-Warning |
Frame relay cir command has been deprecated. Use equivalent MQC priority command |
The issued frame-relay cir command has been deprecated by the MQC commands.\n |
- |
- |
|
QOS_CLI_DEPRECATE-4-FR_EBS |
4-Warning |
Frame relay be command has been deprecated. Use equivalent MQC priority command |
The issued frame-relay be command has been deprecated by the MQC commands.\n |
- |
- |
|
QOS_CLI_DEPRECATE-4-FR_IP_RTP_PRIO |
4-Warning |
frame relay ip rtp priority has been deprecated. Use equivalent MQC priority command |
The issued frame-relay interface ip rtp priority command has been deprecated by the MQC commands.\n |
- |
"Configure a policy with priority and attach to " "the interface\n" |
|
QOS_CLI_DEPRECATE-4-FR_THRESH_DE |
4-Warning |
frame relay congestion threshold de command has been deprecated. Use equivalent MQC priority command |
The issued frame-relay congestion threshold de has been deprecated by the MQC commands.\n |
- |
"Configure a policy with MQC and attach to the interface\n" |
|
QOS_CLI_DEPRECATE-4-FR_THRESH_ECN |
4-Warning |
frame relay congestion threshold ecn command has been deprecated. Use equivalent MQC priority command |
The issued frame-relay congestion threshold ecn has been deprecated by the MQC commands.\n |
- |
"Configure a policy with MQC and attach to the interface\n" |
|
QOS_CLI_DEPRECATE-4-FRFECN_ADAPT |
4-Warning |
frame relay fecn-adapt command has been deprecated. Use equivalent MQC priority command |
The issued frame-relay fecn-adapt command has been deprecated by the MQC commands.\n |
- |
"Configure a policy with MQC and attach to the interface\n" |
|
QOS_CLI_DEPRECATE-4-FRVCQ_CUSTOM |
4-Warning |
frame relay custom-queue-list command has been deprecated. Use equivalent MQC bandwidth command |
The issued frame-relay custome-queue command has been deprecated by the MQC commands.\n |
- |
"Configure a policy with bandwidth and attach to " "the interface\n" |
|
QOS_CLI_DEPRECATE-4-FRVCQ_FAIR |
4-Warning |
frame relay fair-queue command has been deprecated. Use equivalent MQC fair-queue command |
The issued frame-relay fair-queue command has been deprecated by the MQC commands.\n |
- |
"Configure a policy with fair-queue and attach to " "the interface\n" |
|
QOS_CLI_DEPRECATE-4-FRVCQ_PRIORITY |
4-Warning |
frame relay priority-group command has been deprecated. Use equivalent MQC priority command |
The issued frame-relay priority-group command has been deprecated by the MQC commands.\n |
- |
"Configure a policy with priority and attach to " "the interface\n" |
|
QOS_CLI_DEPRECATE-4-IP_RTP_PRIO |
4-Warning |
ip rtp priority command on interface has been deprecated. Use equivalent MQC priority command |
The issued interface ip rtp priority command has been deprecated by the MQC commands.\n |
- |
"Configure a policy with priority and attach to " "the interface\n" |
|
QOS_CLI_DEPRECATE-4-IP_RTP_RESV |
4-Warning |
ip rtp reserve command on interface has been deprecated. Use equivalent MQC reserve command. For further information please consult Product Bulletin 580832 Legacy QoS CLI Commands Deprecation |
The issued interface ip rtp reserve command has been deprecated by the MQC commands.\n |
- |
"Configure a policy with reserve and attach to " "the interface\n" |
|
QOS_CLI_DEPRECATE-4-MAX_RESERVED_BW |
4-Warning |
max-reserved-bandwidth on interface has been deprecated |
The issued max-reserved-bandwidth command has been deprecated by the MQC bandwidth command.\n |
- |
"Configure a policy with bandwidth and attach to " "the interface\n" |
|
QOS_CLI_DEPRECATE-4-PRIORITY_LIST |
4-Warning |
priority-list global config mode CLI has been deprecated. Use equivalent MQC priority command. For further information please consult Product Bulletin 580832 Legacy QoS CLI Commands Deprecation |
The issued global config mode priority-list command has been deprecated by the MQC commands.\n |
- |
- |
|
QOS_CLI_DEPRECATE-4-PRIORITY_QUEUE |
4-Warning |
Priority Queue on interface has been deprecated. Use equivalent MQC priority command |
The issued interface priority-group command has been deprecated by the MQC commands.\n |
- |
"Configure a policy with priority and attach to " "the interface\n" |
|
QOS_CLI_DEPRECATE-4-QUEUE_LIST |
4-Warning |
queue-list global config mode CLI has been deprecated. Use equivalent MQC priority command. For further information please consult Product Bulletin 580832 Legacy QoS CLI Commands Deprecation |
The issued global config mode queue-list command has been deprecated by the MQC commands.\n |
- |
- |
|
QOS_CLI_DEPRECATE-4-RANDOM_DETECT |
4-Warning |
Random detect on interface has been deprecated. Use equivalent MQC random-detect command |
The issued interface random detect command has been deprecated by the MQC commands.\n |
- |
- |
|
QOS_CLI_DEPRECATE-4-RANDOM_DETECT_GROUP |
4-Warning |
Random detect group command has been deprecated |
The issued random detect group command has been deprecated by the MQC commands.\n |
- |
- |
|
QOS_CLI_DEPRECATE-4-TRAFFIC_SHAPE |
4-Warning |
Traffic shape on interface has been deprecated. Use equivalent MQC traffic-shape command |
The issued interface traffic shape command has been deprecated by the MQC commands.\n |
- |
"Configure a policy with traffic-shape and attach to " "the interface\n" |
|
QOS-3-ATLEAST_ONE_FAILOVER_ERR |
3-Error |
Fail-over of dynamic interface [chars] failed\n |
Dynamic interface has changed its route out of different physical interface and queueing can not set-up data-sructures for that new physical interface\n |
qos |
"One possibility is that new physical interface already has " "service-policy or some other dynamic interface already has " "queueing data-structures associated with that physical interface " "and conjuction of such service-policies are not allowed. " "Remove one or the other service-policy in that case. If that is " "not the case then contact technical support\n" |
|
QOS-3-BADXDRSLOT |
3-Error |
Invalid XDR slot. Type/len/slot [dec]/[dec]/[chars]. XDR at 0x%08x |
Configured extended burst size is less than the Rate. It is considered to be illegal and has been reset based on the Rate.\n |
qos |
"This is an informational message only." "No action is required.\n" |
|
QOS-3-BLT_INDEX |
3-Error |
Failed to assign index for target/policy/class/action [dec]/[dec]/[dec]/[chars] |
The configuration of queuing has resulted in the failure to generate an internal unique identifier which represents the queue. This is an internal software error. |
qos |
LOG_STD_ACTION |
|
QOS-3-BURST_BC_ERR |
3-Error |
Burst Bc increased to [dec] bytes\n |
If Burst BC is less than the default burst size then Burst Bc is increased to AF_DEAFULT_BURST\n |
- |
"This is informational message. No action is required\n" |
|
QOS-3-CAC_ALLOC_FAILED |
3-Error |
QoS CAC: failed to allocate a cft flow object for interface [chars] srcIP=%Ci dstIP=%Ci srcPort=[dec] dstPort=[dec] L4Prot=[dec] num flows=[dec] |
Cisco internal software error. The dataplane was unable to complete the CAC processing for a flow. This is likely due to processing more flows than CAC's scale limit |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-CAC_ATTACH_FAILED |
3-Error |
QoS CAC: failed to attach cft flow object for interface [chars] srcIP=%Ci dstIP=%Ci srcPort=[dec] dstPort=[dec] L4Prot=[dec] num flows=[dec] |
Cisco internal software error. The dataplane was unable to complete the CAC processing for a flow. This is likely due to a CFT data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-CAC_EXPORT_DROPPED_PKT |
3-Error |
Dropped a packet for QoS CAC when exporting flow records via HSL to the control plane |
Cisco internal software error. The dataplane dropped one or more packets containing QoS CAC export records. This is likely due to over-driving the punt/hsl messaging channel. |
asr1k-qos keyword:none |
LOG_STD_ACTION |
|
QOS-3-CAC_EXPORT_DROPPED_RECORD |
3-Error |
Dropped a flow record for QoS CAC CAC ID [hex] when attempting |
Cisco internal software error. The dataplane dropped one or more flow records for QoS CAC. This is likely due to buffer allocation error and over-driving the punt/hsl messaging channel. |
asr1k-qos keyword:none |
LOG_STD_ACTION |
|
QOS-3-CAC_FLOW_CREATE_FAILED |
3-Error |
QoS CAC: failed to create a flow in the cft for interface [chars] srcIP=%Ci dstIP=%Ci srcPort=[dec] dstPort=[dec] L3Prot=[dec] L4Prot=[dec] |
Cisco internal software error. The dataplane was unable to complete the CAC processing for a flow. This is likely due to processing more flows than the CFT's scale limit |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-CAC_FLOW_LOCK_FAILED |
3-Error |
QoS CAC: failed to get a flow lock for interface [chars] srcIP=%Ci dstIP=%Ci srcPort=[dec] dstPort=[dec] L3Prot=[dec] L4Prot=[dec] |
Cisco internal software error. The dataplane was unable to complete the CAC processing for a flow. This is likely due to a CFT data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-CAC_FLOW_REPORT_FAILED |
3-Error |
QoS CAC: failed to report flow for interface [chars] srcIP=%Ci dstIP=%Ci srcPort=[dec] dstPort=[dec] L3Prot=[dec] L4Prot=[dec] |
Cisco internal software error. The dataplane was unable to complete the CAC processing for a flow. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-CAC_PROXY_MSG_FAIL |
3-Error |
Failure when handling QoS CAC proxy message [chars] |
- |
- |
- |
|
QOS-3-CFGERR |
3-Error |
interface [chars]: configuration failed\n |
Enough memory is not available to configure feature\n |
high-ipqos |
"It is not possible to configure issued command feature unless " |
|
QOS-3-COEX_NOT_ALLWD |
3-Error |
queueing policy at session cannot co-exist with service policy at sub-interface/pvc\n |
There already may be user-defined flat policy or hierarchical policy at the sub-interface/pvc. With existing of such policy no queueing policy is allowed on session\n |
qos |
"Remove the policy attached to the sub-interface/pvc before attaching " "a new policy to a session\n" |
|
QOS-3-COLLISION_COUNT |
3-Error |
[chars] mismatch count [dec] |
The specified type of collision has detected that although there are no collisions present the count of such indicates otherwise. This is an internal software error. |
qos |
LOG_STD_ACTION |
|
QOS-3-COLLISION_DELETE |
3-Error |
[chars] unable to remove index %08X |
The specified type of collision is unable to removed the specified index. This is an internal software error. |
qos |
LOG_STD_ACTION |
|
QOS-3-COLLISION_TYPE |
3-Error |
Type [dec] is invalid for collision [chars] |
The specified type of collision is an invalid value which indicates that there is no support for the generation of an internal identifier. This is an internal software error. |
qos |
LOG_STD_ACTION |
|
QOS-3-DETACH |
3-Error |
Failed to detach [chars] [chars] service policy |
The specified type of service policy has failed to detach itself from the attachment point indicated. The service policy will remain attached although repeated attempts to remove such should fail in a similar manner. |
c3pl |
"show policy-map [type] " "<attachment point>" |
|
QOS-3-GET_CAC_FLOW_OBJECT_FAILED |
3-Error |
QoS CAC: failed to retreive the CAC flow object for interface [chars] srcIP=%Ci dstIP=%Ci srcPort=[dec] dstPort=[dec] L3Prot=[dec] L4Prot=[dec] |
Cisco internal software error. The dataplane was unable to complete the CAC processing for a flow. This is likely due to processing more flows than the CFT's scale limit |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-GET_CAC_INFO_FAILED |
3-Error |
QoS CAC: failed to retreive the CAC config for interface [chars] srcIP=%Ci dstIP=%Ci srcPort=[dec] dstPort=[dec] L3Prot=[dec] L4Prot=[dec] |
Cisco internal software error. The dataplane was unable to complete the CAC processing for a flow. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-HA_BULK_SYNC |
3-Error |
[chars] Failure in completing bulk sync\n |
QoS configuration can't be synced to the standby\n |
- |
"Contact your Cisco technical support representative.\n" |
|
QOS-3-HA_BULK_SYNC_BEFORE_TIMEOUT |
3-Error |
[chars] Failure in completing bulk sync before timeout\n |
The interface bandwidth is more than the total bandwidth that is required for QoS policy on this interface.\n |
- |
"There is no user action required.\n" |
|
QOS-3-HA_COLLISION_INVALID |
3-Error |
Received collision table of type [dec] |
The specified type of collision is an invalid value which indicates that the message received on the standby RP contains erroneous data. This is an internal software error which should result in a reload of the standby RP so that the bulk sync of configuration can be sent once more by the active RP. |
qos |
LOG_STD_ACTION |
|
QOS-3-HA_COLLISION_SIZE |
3-Error |
Received [chars] message total/unit [dec]/[dec] [chars] |
The specified type of collision table has been determined to contain a discrepancy between the total message size and the individual table unit that is being decoded on the standby RP. This is an internal software error which should result in a reload of the standby RP so that the bulk sync of configuration can be sent once more by the active RP. |
qos |
LOG_STD_ACTION |
|
QOS-3-HA_COLLISION_STRING |
3-Error |
Received [chars] message length [dec] for string [chars] |
The specified type of collision table contains an individual unit within the message which has an incorrectly encoded string which is used to represent the collision which is being synced from the active RP. This is an internal software error which should result in a reload of the standby RP so that the bulk sync of configuration can be sent once more by the active RP. |
qos |
LOG_STD_ACTION |
|
QOS-3-HA_GET_ARG_NUM |
3-Error |
[chars] Failure in getting event identification\n |
QoS configuration can't be synced to the standby\n |
- |
"Contact your Cisco technical support representative.\n" |
|
QOS-3-HA_MISMATCH |
3-Error |
Bulk sync failed for [chars] collisions space available [dec] buffer [dec] |
A synchronization attempt between the active and standby RP peers has failed due to the detection of a mismatch in the source and destination sizes of a buffer used in the transport of the collision information to the standby RP. This is an internal software error. |
qos |
LOG_STD_ACTION |
|
QOS-3-HQF_FEA_API_FAIL |
3-Error |
Feature processing API returned NULL pak with INCOMPLETE flag\n |
HQF calls feature processing API to get the next packet from the feature for example Frame-relay fragmentation. The API returns conflicting flags with NULL packet.\n |
qos |
"Check if the system resources e.g. packet buffers are exhausted." " Contact technical support\n" |
|
QOS-3-HQF_QID_ERR |
3-Error |
Maximum number of QoS queues [dec] reached.\n |
The system has run out of QoS queue identifiers and cannot allocate any more until existing queues are freed up.\n |
- |
"Existing QoS configurations will need to be removed to free up" "more queue identifiers. For example remove existing QoS " "service-policy configurations or modify policy-map templates to " "have fewer queueing actions.\n" |
|
QOS-3-HQFNOPAK |
3-Error |
interface [chars]: pak_reparent failed\n |
pak_reparent has been invoked and failed.\n |
- |
"Collect show buffer and show policy interface output and send " "to technical support\n" |
|
QOS-3-HQFPAKREQUEUE |
3-Error |
interface [chars]: pak_requeue_head has been invoked\n |
pak_requeue_head function has been invoked on a packet. |
qos |
"Collect show buffer and show policy interface output and send " "to technical support\n" |
|
QOS-3-HQFPOOLERR |
3-Error |
interface [chars]: failed to allocate hqf particle\n |
The HQF particle pool is empty. It cannot process a router generated packet\n |
- |
"Collect show buffer and show policy interface output and send " "to technical support\n" |
|
QOS-3-INDEX_DELETE |
3-Error |
[chars] unable to remove index %08X |
The specified entity is unable to removed the specified index. This is an internal software error. |
qos |
LOG_STD_ACTION |
|
QOS-3-INDEX_EXISTS |
3-Error |
[chars] attempt to add index %08X [chars] |
The specified entity is unable to add an entry due to the detection of an existing entry with the same index or name. This is an internal software error. |
qos |
"show cce cp id [collisions]" |
|
QOS-3-INVALID_ATM_GROUP_MEMBER_UIDB |
3-Error |
Dropped a flow from ATM interface [chars] due to invalid oup_member_uidb_config |
Cisco internal software error. Fail to get QOS config from ATM input terface due to invalid group_member_uidb_config. |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-INVALID_BQS_QUEUE_INFO |
3-Error |
Drop policy given an invalid scheduling queue/wred [dec]/[dec] |
Cisco internal software error. The dataplane was unable to complete enqueuing a packet. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-INVALID_CAC_PKT_INFO |
3-Error |
QoS CAC: failed to get the CAC packet info for interface [chars] srcIP=%Ci dstIP=%Ci srcPort=[dec] dstPort=[dec] L3Prot=[dec] L4Prot=[dec] |
Cisco internal software error. The dataplane was unable to complete the CAC processing for a packet. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-INVALID_CLASS_QID |
3-Error |
Class Queuing error for interface [chars] qid [dec] |
Cisco internal software error. The dataplane was unable to complete enqueuing a packet. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-INVALID_DEFAULT_JIB_HDR |
3-Error |
Queuing error for interface [chars] |
Cisco internal software error. The dataplane was unable to complete enqueuing a packet. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-INVALID_DEFAULT_QID |
3-Error |
Default Queuing error for interface [chars] qid [dec] |
Cisco internal software error. The dataplane was unable to complete enqueuing a packet. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-INVALID_HIER_EXPORT_CLASS_ID |
3-Error |
Invalid export class ID detected |
Cisco internal software error. The dataplane was unable to complete a hierarchy export on a packet. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-INVALID_HIER_EXPORT_COUNT |
3-Error |
Invalid export count [hec] detected |
Cisco internal software error. The dataplane was unable to complete a hierarchy export on a packet. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-INVALID_MARKER_STATS_INFO |
3-Error |
Invalid address [hec] detected |
Cisco internal software error. The dataplane was unable to complete a statistics update on a packet. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-INVALID_PLTYPE |
3-Error |
No entry found for pltype : [dec] in global service_policy_queue during service-policy deletion.\n |
No entry was found for a pltype when un-queue of a service-policy from global service_policy_queue was undergoing. This will result in freeing a service-policy without un-queuing it from global service_policy_queue. |
c3pl |
"Need to figure out why there was no entry found for a pltype" " in the global service_policy_queue when passed with a" " service-policy while deletion. check the traceback for" " details" |
|
QOS-3-INVALID_POLICY |
3-Error |
queueing policy at session/tunnel can co-exist only with \ class-default shaping policy at sub-interface/pvc\n |
There already may be user-defined flat policy or hierarchical policy at the sub-interface/pvc. With existing of such policy no queueing policy is allowed on session\n |
qos |
"Make sub-interface/pvc based policy just one level policy with only " " class-default\n" |
|
QOS-3-INVALID_Q_ADDRESS |
3-Error |
Invalid Queue address for interface [chars] qaddr [hec] |
Cisco internal software error. The dataplane was unable to complete enqueuing a packet. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-INVALID_QID |
3-Error |
Queuing error for interface [chars] qid [dec] wred [hec] |
Cisco internal software error. The dataplane was unable to complete enqueuing a packet. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-INVALID_STAT_QID |
3-Error |
Stat Queuing error for interface [chars] qid [dec] |
Cisco internal software error. The dataplane was unable to complete enqueuing a packet. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-INVALID_STATS_INFO |
3-Error |
Invalid address [hec] detected |
Cisco internal software error. The dataplane was unable to complete enqueuing a packet. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-INVALID_WRED_THRESH_ADDR |
3-Error |
Wred threshold address is invalid addr [dec] |
Cisco internal software error. The dataplane was unable to complete enqueuing a packet. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-ISSU_COMP |
3-Error |
Failed to exchange capability with peer |
The attempt to negotiate version capabilities and the exhange of the peer support has failed. This indicates that QoS is unable to support a redundant operation with the standby RP peer. |
qos |
LOG_STD_ACTION |
|
QOS-3-ISSU_GTP_CFG_ENHANCE |
3-Error |
GTP-AIC configuration has been detected which is totally different with peer. Delete all GTP-AIC related config to proceed with ISSU/ISSD. After ISSU/ISSD done config GTP-AIC again.\n |
PEER GTP-AIC configuration would be messed up. |
c3pl |
"Manually remove all GTP-AIC configuration and reinitiate " "ISSU/ISSD. \n" |
|
QOS-3-MAIN_SUB_POLICY |
3-Error |
FR fragmentation is not supported with interface or sub-interface based policies \n |
On Cisco 7500 series routers Frame Relay fragmentation is not supported when service policies are configured on the interface or subinterfaces. |
- |
"Remove the service policy configuration under the interface " "or subinterfaces and reissue either the class command from " "Frame-Relay DLCI interface configuration mode or the " "frame-relay fragment command from map-class configuration " "mode. \n" |
|
QOS-3-MULTIPLE_INTERFACES |
3-Error |
Load-sharing mode has changed. \ Queuing functionality may not be supported after this.\n |
Dynamic interface has changed its route out of different physical interface. It might resolve into multiple interfaces for queuing. HQF functionality will get affected.\n |
qos |
"Likely scanario is that CEF is returning multiple paths " "across different interfaces. For those tunnels " "which has queuing features need unique out-going interface " "to resolve queuing hierarchy. " "Common instance is per-prefix load-balancing to per-destination. " "Need to remove offending configurations. " "May also need reload to get the queuing in working state\n" |
|
QOS-3-POLICE_CLASSIFY_FAIL |
3-Error |
Color aware policer classification error for interface [chars] |
Cisco internal software error. The dataplane was unable to complete processing of a service policy due to a classification failure on a color aware policer class. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-POLICE_FAIL_ADDRESS_IN |
3-Error |
dataplane policer error for input interface [chars] [hec] [hec] [hec] [hec] [hec] |
Cisco internal software error. The dataplane was unable to complete processing of a service policy due to a policer failure. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-POLICE_FAIL_ADDRESS_OUT |
3-Error |
dataplane policer error for output interface [chars] [hec] [hec] [hec] [hec] [hec] |
Cisco internal software error. The dataplane was unable to complete processing of a service policy due to a policer failure. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-QOS_CLASSIFY_FAIL |
3-Error |
dataplane classification error for interface [chars] |
Cisco internal software error. The dataplane was unable to complete processing of a service policy due to a classification failure. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-QOS_CLASSIFY_FAIL_CCE_IN |
3-Error |
dataplane classification error for input interface [chars] [hec] [hec] [hec] [hec] |
Cisco internal software error. The dataplane was unable to complete processing of a service policy due to a classification failure. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-QOS_CLASSIFY_FAIL_CCE_OUT |
3-Error |
dataplane classification error for output interface [chars] [hec] [hec] [hec] [hec] |
Cisco internal software error. The dataplane was unable to complete processing of a service policy due to a classification failure. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-QOS_CLASSIFY_FAIL_CHILD_IN |
3-Error |
child dataplane classification error for input interface [chars] |
Cisco internal software error. The dataplane was unable to complete processing of a service policy due to a classification failure. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-QOS_CLASSIFY_FAIL_CHILD_OUT |
3-Error |
child dataplane classification error for output interface [chars] |
Cisco internal software error. The dataplane was unable to complete processing of a service policy due to a classification failure. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-SA_SESSION_FAILOVER_ERR |
3-Error |
Fail-over of dynamic SA session to interface [chars] failed\n |
Dynamic SA session has changed its route out of different physical interface and queueing can not set-up data-sructures for that new physical interface\n |
qos |
"One possibility is that new physical interface already has " "service-policy with queueing configured" "Remove the other service-policy in that case. If that is " "not the case then contact technical support\n" |
|
QOS-3-TARGET_INDEX |
3-Error |
[chars] [chars] service policy attachment failed to assign index |
The configuration of a service policy has resulted in the failure to generate an internal unique identifier which represents the attachment point target of the associated policy map. This is an |
c3pl |
LOG_STD_ACTION |
|
QOS-3-UNASSIGNED |
3-Error |
A [chars] event resulted in an unassigned index for [chars] [chars] |
- |
- |
- |
|
QOS-3-VALID_DEFAULT_QID |
3-Error |
Using Default Queue for interface [chars] qid [dec] |
Cisco internal software error. The dataplane was unable to complete enqueuing a packet. This is likely due to a data initialization error |
cpp-ucode keyword:qos |
LOG_STD_ACTION |
|
QOS-3-VTEMP_MAIN_ERR |
3-Error |
Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the main interface to which the PPP/PPPoE virtual-access interface is bound.\n |
Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the main interface to which the PPP/PPPoE virtual-access interface is bound.\n |
qos |
"Remove the policy attached to the main interface before attaching " "a new policy to a PPP/PPPoE virtual-access interface\n" |
|
QOS-3-VTEMP_MLP_ERR |
3-Error |
A service policy cannot be attached to a PPP virtual-access interface when ppp multilink is enabled. A service policy can be attached to a ppp multilink bundle interface only.\n |
A service policy attached to a virtual-template is usually copied to associated virtual-access interfaces. However if such a virtual-access interface joins a multilink ppp bundle the policy is not attached to the virtual-access interface.\n |
qos |
"This is informational message. No action is required\n" |
|
QOS-3-VTEMP_SUB_ERR |
3-Error |
Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the subinterface to which the PPP/PPPoE virtual-access interface is bound.\n |
Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the subinterface to which the PPP/PPPoE virtual-access interface is bound.\n |
qos |
"Remove the policy attached to the subinterface before attaching " "a new policy to a PPP/PPPoE virtual-access interface\n" |
|
QOS-3-VTEMP_VC_ERR |
3-Error |
Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the vc/pvc to which the PPP/PPPoE virtual-access interface is bound.\n |
Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the vc/pvc to which the PPP/PPPoE virtual-access interface is bound.\n |
qos |
"Remove the policy attached to the vc/pvc before attaching " "a new policy to a PPP/PPPoE virtual-access interface\n" |
|
QOS-3-XDRLEN |
3-Error |
Invalid XDR length. Type [dec][chars]. XDR/buffer len [dec]/[dec] |
An internal software error occured\n |
qos |
LOG_STD_ACTION |
|
QOS-4-DYN_SUSPEND |
4-Warning |
Queueing hierarchy move failed on [chars] suspending policy. |
A forwarding path change has moved the given queue to a new port where its QoS queuing policy cannot be satisfied. This is likely due to a conflicting policy or insufficient bandwidth on the new port or simply that a new port has not yet been calculated. The policy has thus been temporarily suspended. |
- |
LOG_STD_ACTION |
|
QOS-4-FO_IN_USE |
4-Warning |
Releasing feature object with reference count [dec] |
This is an internal software error. A QoS policy feature object has a stale reference. |
qos |
"If the message recurs try to isolate the traffic conditions which " "trigger the message and contact technical support. Provide the output " "from the show tech-support and show policy-map interface commands." |
|
QOS-4-HQUEUE_QLIMIT_VALUE_SYNC_ISSUE |
4-Warning |
The hold-queue value is less than the sum of queue-limit values. \n |
The hold-queue value is less than the queue-limit configured. This will lead to no-buffer drops instead of tail drops |
qos |
"The hold-queue value should be properly adjusted to prevent " "no-buffer drops." |
|
QOS-4-INVALIDBW |
4-Warning |
interface [chars]: Not enough bandwidth to configure service-policy\n |
The issued interface bandwidth is less than the total bandwidth that is required for QoS policy on this interface.\n |
- |
"There is no user action required.\n" |
|
QOS-4-LC_STATS_MSG_DROPPED |
4-Warning |
QoS statistics update message dropped due to [chars]\n |
Changes to QoS counters are sent periodically from linecards to the route processor. One of these statistics update messages was discarded because it was inconsistent or because the route processor ran out of message buffers. The packet and bytes counters for a single service-policy may be underreported by show commands and SNMP queries.\n |
qos |
"This is an informational message only." "No action is required.\n" |
|
QOS-4-QLIMIT_HQUEUE_VALUE_SYNC_ISSUE |
4-Warning |
The sum of all queue-limit value is greater than the hold-queue value. \n |
The hold-queue value is less than the queue-limit configured. This will lead to no-buffer drops instead of tail drops |
qos |
"The hold-queue value should be properly adjusted to prevent " "no-buffer drops." |
|
QOS-4-SERV_FRAG_POLICY |
4-Warning |
\nservice-policy [chars] can't be attached without corresponding service-fragment policy on appropriate target first |
For a fragment policy that is being installed check if parent targets have relevant service-fragment class installed. If not then we can not allow fragment policy installation.\n |
c3pl |
"Check the parent target to add relevant service-fragment class.\n" |
|
QOS-4-WRED_QLIMIT_OUT_OF_SYNC |
4-Warning |
On interface [chars] user-defined wred max threshold higher than default queue-limit \n |
The user defined random-detect is greater that the default queue-limit for this interface. Some of the random-detect configurations will not function properly due to this anomaly. \n |
qos |
"No action required this is user configured behavior and " "user should change the configured random-detect value if this " "message if of concern to them.\n" |
|
QOS-6-ACTIVATE |
6-Information |
Activating service policy [chars] on [chars] in [chars] direction |
The interface bandwidth is more than the total bandwidth that is required for QoS policy on this interface.\n |
- |
"There is no user action required.\n" |
|
QOS-6-ACTIVATE_NOHW |
6-Information |
\nActivating service policy [chars] in [chars] direction |
- |
- |
- |
|
QOS-6-ADAPTIVE_QOS_DISABLED |
6-Information |
Adaptive QoS functionality is disabled. Shaper is reset to upper-bound |
Multiple and consecutive reports from peer are not received. This leads to an assumption that the peer has gone away. |
qos |
"Removal and re-application of policy may be required to re-enable " "the adaptive QoS functionality" |
|
QOS-6-COLLISION_MAX |
6-Information |
Maximum number of collision entries [dec] reached |
The system limit on the number of collision entries used in assigning unique identifiers for policy and class maps et al. has been reached. This indicates that no further configuration of entities which require additional generation of a unique identifier will be possible. |
qos |
LOG_STD_ACTION |
|
QOS-6-DYN_INSTALL |
6-Information |
Installing suspended policy on [chars]. |
IOS is restoring a previously suspended policy. |
qos |
LOG_STD_ACTION |
|
QOS-6-NON_AGG_WRED |
6-Information |
ATM SPA doesn't support true non-aggregate WRED. All non-specified dscp/prec values will be aggregated in default WRED profile |
ATM SPA has limited hardware capability which is not enough to support traditional WRED. ATM SPA would support 'limited' non-aggregate WRED for the specified dscp/prec values maximum of 6 |
- |
"There is no user action required.\n" |
|
QOS-6-POLICY_INST_FAILED |
6-Information |
Service policy installation failed on [chars]. [chars]. policy:[chars] dir:[chars] ptype:[chars] ctype:[chars]\n |
Service policy could not be installed\n |
c3pl |
"This is an informational message only." "No action is required.\n" |
|
QOS-6-POLICY_REM_FAILED |
6-Information |
Service policy remove failed on [chars] policy:[chars] dir:[chars] ptype:[chars] ctype:[chars]\n |
Service policy could not be removed\n |
c3pl |
"This is an informational message only." "No action is required.\n" |
|
QOS-6-RADIO_MULTI_REM |
6-Information |
Remove [chars] policy before removing policy from [chars]\n |
- |
- |
- |
|
QOS-6-RELOAD |
6-Information |
[chars] reloading [chars] |
A synchronization attempt between the active and standby RP peers has failed with the reason indicated. The standby peer is reloaded in an attempt to resynchronize when operating in a stateful redundant mode. |
qos |
LOG_STD_ACTION |
|
QOS-6-SUSPEND |
6-Information |
Suspending service policy [chars] on [chars] in [chars] direction |
The interface bandwidth is less than the total bandwidth that is required for QoS policy on this interface.\n |
c3pl |
"There is no user action required.\n" |
|
QOSMGR-3-ASIC_PROGRAMMING_FAIL |
3-Error |
Fails to program the ASIC for policymap [chars] |
Can not access to HW successfully. |
firmware |
LOG_STD_ACTION |
|
QOSMGR-3-ASIC_PROGRAMMING_FAIL |
3-Error |
Fails to program the ASIC for policymap [chars] |
Can not access to HW successfully. |
firmware |
LOG_STD_ACTION |
|
QOSMGR-3-ASIC_PROGRAMMING_FAIL |
3-Error |
Fails to program the ASIC for policymap [chars] |
Can not access to HW successfully. |
firmware |
LOG_STD_ACTION |
|
QOSMGR-3-ASIC_PROGRAMMING_FAIL |
3-Error |
Fails to program the ASIC for policymap [chars] |
Can not access to HW successfully. |
firmware |
LOG_STD_ACTION |
|
QOSMGR-3-ASIC_PROGRAMMING_FAIL |
3-Error |
Fails to program the ASIC for policymap [chars] |
Can not access to HW successfully. |
firmware |
LOG_STD_ACTION |
|
QOSMGR-3-BANDWIDTH_CHILD_ERROR |
3-Error |
Bandwidth in one of the children class is greater than input bandwidth |
Children class's bandwidth should not be greater |
firmware |
"Either increase input value or decrese erring one" |
|
QOSMGR-3-BANDWIDTH_CHILD_ERROR |
3-Error |
Bandwidth in one of the children class is greater than input bandwidth |
Children class's bandwidth should not be greater |
firmware |
"Either increase input value or decrese erring one" |
|
QOSMGR-3-BANDWIDTH_CHILD_ERROR |
3-Error |
Bandwidth in one of the children class is greater than input bandwidth |
Children class's bandwidth should not be greater |
firmware |
"Either increase input value or decrese erring one" |
|
QOSMGR-3-BANDWIDTH_CHILD_ERROR |
3-Error |
Bandwidth in one of the children class is greater than input bandwidth |
Children class's bandwidth should not be greater |
firmware |
"Either increase input value or decrese erring one" |
|
QOSMGR-3-BANDWIDTH_CHILD_ERROR |
3-Error |
Bandwidth in one of the children class is greater than input bandwidth |
Children class's bandwidth should not be greater |
firmware |
"Either increase input value or decrese erring one" |
|
QOSMGR-3-BANDWIDTH_LEVEL_ERROR |
3-Error |
Bandwidth command not acceptable at interface level |
Hardware does not support bandwidth at physical level |
firmware |
"Do not apply bandwidth command at interface " "level policy" |
|
QOSMGR-3-BANDWIDTH_LEVEL_ERROR |
3-Error |
Bandwidth command not acceptable at interface level |
Hardware does not support bandwidth at physical level |
firmware |
"Do not apply bandwidth command at interface " "level policy" |
|
QOSMGR-3-BANDWIDTH_LEVEL_ERROR |
3-Error |
Bandwidth command not acceptable at interface level |
Hardware does not support bandwidth at physical level |
firmware |
"Do not apply bandwidth command at interface " "level policy" |
|
QOSMGR-3-BANDWIDTH_LEVEL_ERROR |
3-Error |
Bandwidth command not acceptable at interface level |
Hardware does not support bandwidth at physical level |
firmware |
"Do not apply bandwidth command at interface " "level policy" |
|
QOSMGR-3-BANDWIDTH_LEVEL_ERROR |
3-Error |
Bandwidth command not acceptable at interface level |
Hardware does not support bandwidth at physical level |
firmware |
"Do not apply bandwidth command at interface " "level policy" |
|
QOSMGR-3-BANDWIDTH_OVERSUBSCRIBED |
3-Error |
Bandwidth oversubscribed in the interface |
Sum of committed bandwidth at a particular level exceeds the sum total of interface's max bandwidth |
firmware |
"Reduce the committed bandwidth to be less that " "interface's max bandwidth" |
|
QOSMGR-3-BANDWIDTH_OVERSUBSCRIBED |
3-Error |
Bandwidth oversubscribed in the interface |
Sum of committed bandwidth at a particular level exceeds the sum total of interface's max bandwidth |
firmware |
"Reduce the committed bandwidth to be less that " "interface's max bandwidth" |
|
QOSMGR-3-BANDWIDTH_OVERSUBSCRIBED |
3-Error |
Bandwidth oversubscribed in the interface |
Sum of committed bandwidth at a particular level exceeds the sum total of interface's max bandwidth |
firmware |
"Reduce the committed bandwidth to be less that " "interface's max bandwidth" |
|
QOSMGR-3-BANDWIDTH_OVERSUBSCRIBED |
3-Error |
Bandwidth oversubscribed in the interface |
Sum of committed bandwidth at a particular level exceeds the sum total of interface's max bandwidth |
firmware |
"Reduce the committed bandwidth to be less that " "interface's max bandwidth" |
|
QOSMGR-3-BANDWIDTH_OVERSUBSCRIBED |
3-Error |
Bandwidth oversubscribed in the interface |
Sum of committed bandwidth at a particular level exceeds the sum total of interface's max bandwidth |
firmware |
"Reduce the committed bandwidth to be less that " "interface's max bandwidth" |
|
QOSMGR-3-BANDWIDTH_PARENT_ERROR |
3-Error |
Sum of bandwidths is greater than parent class's bandwidth |
Total bandwidth of the classes at the same level exceeds the parent class's bandwidth |
firmware |
"Reduce the bandwidth value" |
|
QOSMGR-3-BANDWIDTH_PARENT_ERROR |
3-Error |
Sum of bandwidths is greater than parent class's bandwidth |
Total bandwidth of the classes at the same level exceeds the parent class's bandwidth |
firmware |
"Reduce the bandwidth value" |
|
QOSMGR-3-BANDWIDTH_PARENT_ERROR |
3-Error |
Sum of bandwidths is greater than parent class's bandwidth |
Total bandwidth of the classes at the same level exceeds the parent class's bandwidth |
firmware |
"Reduce the bandwidth value" |
|
QOSMGR-3-BANDWIDTH_PARENT_ERROR |
3-Error |
Sum of bandwidths is greater than parent class's bandwidth |
Total bandwidth of the classes at the same level exceeds the parent class's bandwidth |
firmware |
"Reduce the bandwidth value" |
|
QOSMGR-3-BANDWIDTH_PARENT_ERROR |
3-Error |
Sum of bandwidths is greater than parent class's bandwidth |
Total bandwidth of the classes at the same level exceeds the parent class's bandwidth |
firmware |
"Reduce the bandwidth value" |
|
QOSMGR-3-BANDWIDTH_PARENT_SHAPE_ERROR |
3-Error |
Sum of bandwidths is greater than parent class's shapePIR |
Total bandwidth of the classes at the same level exceeds the parent class's shapePIR value |
firmware |
"Reduce the bandwidth value" |
|
QOSMGR-3-BANDWIDTH_PARENT_SHAPE_ERROR |
3-Error |
Sum of bandwidths is greater than parent class's shapePIR |
Total bandwidth of the classes at the same level exceeds the parent class's shapePIR value |
firmware |
"Reduce the bandwidth value" |
|
QOSMGR-3-BANDWIDTH_PARENT_SHAPE_ERROR |
3-Error |
Sum of bandwidths is greater than parent class's shapePIR |
Total bandwidth of the classes at the same level exceeds the parent class's shapePIR value |
firmware |
"Reduce the bandwidth value" |
|
QOSMGR-3-BANDWIDTH_PARENT_SHAPE_ERROR |
3-Error |
Sum of bandwidths is greater than parent class's shapePIR |
Total bandwidth of the classes at the same level exceeds the parent class's shapePIR value |
firmware |
"Reduce the bandwidth value" |
|
QOSMGR-3-BANDWIDTH_PARENT_SHAPE_ERROR |
3-Error |
Sum of bandwidths is greater than parent class's shapePIR |
Total bandwidth of the classes at the same level exceeds the parent class's shapePIR value |
firmware |
"Reduce the bandwidth value" |
|
QOSMGR-3-BANDWIDTH_SHAPE_ERROR |
3-Error |
Bandwidth configured is greater than shapePIR of the class |
Bandwidth should not be greater than shape value |
firmware |
"Reduce the bandwidth value to less than" " class's shapePIR value" |
|
QOSMGR-3-BANDWIDTH_SHAPE_ERROR |
3-Error |
Bandwidth configured is greater than shapePIR of the class |
Bandwidth should not be greater than shape value |
firmware |
"Reduce the bandwidth value to less than" " class's shapePIR value" |
|
QOSMGR-3-BANDWIDTH_SHAPE_ERROR |
3-Error |
Bandwidth configured is greater than shapePIR of the class |
Bandwidth should not be greater than shape value |
firmware |
"Reduce the bandwidth value to less than" " class's shapePIR value" |
|
QOSMGR-3-BANDWIDTH_SHAPE_ERROR |
3-Error |
Bandwidth configured is greater than shapePIR of the class |
Bandwidth should not be greater than shape value |
firmware |
"Reduce the bandwidth value to less than" " class's shapePIR value" |
|
QOSMGR-3-BANDWIDTH_SHAPE_ERROR |
3-Error |
Bandwidth configured is greater than shapePIR of the class |
Bandwidth should not be greater than shape value |
firmware |
"Reduce the bandwidth value to less than" " class's shapePIR value" |
|
QOSMGR-3-EFP_SHAPE_RESTRICTION |
3-Error |
EFP policies cannot have shape command at physical level and more than one logical level classes |
Since the HW does not support four level hierarchy EFP policies sit in pseudo level between Physical and Logical level |
firmware |
"Either remove vlan hierarchy in the EFP policy or" " do not configure shape command at physical level" |
|
QOSMGR-3-EFP_SHAPE_RESTRICTION |
3-Error |
EFP policies cannot have shape command at physical level and more than one logical level classes |
Since the HW does not support four level hierarchy EFP policies sit in pseudo level between Physical and Logical level |
firmware |
"Either remove vlan hierarchy in the EFP policy or" " do not configure shape command at physical level" |
|
QOSMGR-3-EFP_SHAPE_RESTRICTION |
3-Error |
EFP policies cannot have shape command at physical level and more than one logical level classes |
Since the HW does not support four level hierarchy EFP policies sit in pseudo level between Physical and Logical level |
firmware |
"Either remove vlan hierarchy in the EFP policy or" " do not configure shape command at physical level" |
|
QOSMGR-3-EFP_SHAPE_RESTRICTION |
3-Error |
EFP policies cannot have shape command at physical level and more than one logical level classes |
Since the HW does not support four level hierarchy EFP policies sit in pseudo level between Physical and Logical level |
firmware |
"Either remove vlan hierarchy in the EFP policy or" " do not configure shape command at physical level" |
|
QOSMGR-3-EFP_SHAPE_RESTRICTION |
3-Error |
EFP policies cannot have shape command at physical level and more than one logical level classes |
Since the HW does not support four level hierarchy EFP policies sit in pseudo level between Physical and Logical level |
firmware |
"Either remove vlan hierarchy in the EFP policy or" " do not configure shape command at physical level" |
|
QOSMGR-3-EGRESS_MARKING_PROFILES_EXHAUSTED |
3-Error |
Egress marking profiles have exceeded the maxinum number [dec] |
No free egress cos marking profile to accommodate the request |
firmware |
"Change config to reuse the existing profiles" |
|
QOSMGR-3-EGRESS_MARKING_PROFILES_EXHAUSTED |
3-Error |
Egress marking profiles have exceeded the maxinum number [dec] |
No free egress cos marking profile to accommodate the request |
firmware |
"Change config to reuse the existing profiles" |
|
QOSMGR-3-EQOS_CXT_EXCEEDED |
3-Error |
Maximum Egress QosContexts consumed in the Bridge-Domain |
Number of Egress QoS vlan matches exceeds the maximum allowed in the Bridge-Domain |
firmware |
"Reduce the number of Egress QoS vlan" " matches in the Bridge-Domain and try again" |
|
QOSMGR-3-EQOS_CXT_EXCEEDED |
3-Error |
Maximum Egress QosContexts consumed in the Bridge-Domain |
Number of Egress QoS vlan matches exceeds the maximum allowed in the Bridge-Domain |
firmware |
"Reduce the number of Egress QoS vlan" " matches in the Bridge-Domain and try again" |
|
QOSMGR-3-EQOS_CXT_EXCEEDED |
3-Error |
Maximum Egress QosContexts consumed in the Bridge-Domain |
Number of Egress QoS vlan matches exceeds the maximum allowed in the Bridge-Domain |
firmware |
"Reduce the number of Egress QoS vlan" " matches in the Bridge-Domain and try again" |
|
QOSMGR-3-EQOS_CXT_EXCEEDED |
3-Error |
Maximum Egress QosContexts consumed in the Bridge-Domain |
Number of Egress QoS vlan matches exceeds the maximum allowed in the Bridge-Domain |
firmware |
"Reduce the number of Egress QoS vlan" " matches in the Bridge-Domain and try again" |
|
QOSMGR-3-EQOS_CXT_EXCEEDED |
3-Error |
Maximum Egress QosContexts consumed in the Bridge-Domain |
Number of Egress QoS vlan matches exceeds the maximum allowed in the Bridge-Domain |
firmware |
"Reduce the number of Egress QoS vlan" " matches in the Bridge-Domain and try again" |
|
QOSMGR-3-INGRESS_MARKING_PROFILES_EXHAUSTED |
3-Error |
Ingress marking profiles have exceeded the maxinum number [dec] |
No free ingress cos marking profile to accommodate the request |
firmware |
"Change config to reuse the existing profiles" |
|
QOSMGR-3-INGRESS_MARKING_PROFILES_EXHAUSTED |
3-Error |
Ingress marking profiles have exceeded the maxinum number [dec] |
No free ingress cos marking profile to accommodate the request |
firmware |
"Change config to reuse the existing profiles" |
|
QOSMGR-3-INGRESS_QOS_HANDLE_EXCEEDED |
3-Error |
Internal Error in resource allocation |
The system is running out of qos-handle to support specified policy-map. |
firmware |
"" |
|
QOSMGR-3-INGRESS_QOS_HANDLE_EXCEEDED |
3-Error |
Internal Error in resource allocation |
The system is running out of qos-handle to support specified policy-map. |
firmware |
"" |
|
QOSMGR-3-INGRESS_QOS_HANDLE_EXCEEDED |
3-Error |
Internal Error in resource allocation |
The system is running out of qos-handle to support specified policy-map. |
firmware |
"" |
|
QOSMGR-3-INGRESS_QOS_HANDLE_EXCEEDED |
3-Error |
Internal Error in resource allocation |
The system is running out of qos-handle to support specified policy-map. |
firmware |
"" |
|
QOSMGR-3-INGRESS_QOS_HANDLE_EXCEEDED |
3-Error |
Internal Error in resource allocation |
The system is running out of qos-handle to support specified policy-map. |
firmware |
"" |
|
QOSMGR-3-INGRESS_QOS_PROFILED_EXCEEDED |
3-Error |
Internal Error in resource allocation |
The system is running out of qos-profiled to support the specified policy-map. |
firmware |
"" |
|
QOSMGR-3-INGRESS_QOS_PROFILED_EXCEEDED |
3-Error |
Internal Error in resource allocation |
The system is running out of qos-profiled to support the specified policy-map. |
firmware |
"" |
|
QOSMGR-3-INGRESS_QOS_PROFILED_EXCEEDED |
3-Error |
Internal Error in resource allocation |
The system is running out of qos-profiled to support the specified policy-map. |
firmware |
"" |
|
QOSMGR-3-INGRESS_QOS_PROFILED_EXCEEDED |
3-Error |
Internal Error in resource allocation |
The system is running out of qos-profiled to support the specified policy-map. |
firmware |
"" |
|
QOSMGR-3-INGRESS_QOS_PROFILED_EXCEEDED |
3-Error |
Internal Error in resource allocation |
The system is running out of qos-profiled to support the specified policy-map. |
firmware |
"" |
|
QOSMGR-3-INGRESS_QOSGROUP_MARKING_PROFILES_EXHAUSTED |
3-Error |
Ingress Exp and qos-group marking profiles have exceeded the maxinum number [dec] |
No free ingress qos-group marking profile to accommodate the request |
firmware |
"Change config to reuse the existing profiles" |
|
QOSMGR-3-INGRESS_QOSGROUP_MARKING_PROFILES_EXHAUSTED |
3-Error |
Ingress Exp and qos-group marking profiles have exceeded the maxinum number [dec] |
No free ingress qos-group marking profile to accommodate the request |
firmware |
"Change config to reuse the existing profiles" |
|
QOSMGR-3-L4OP_ACL_NEQ_CONFLICT |
3-Error |
NEQ L4 operation not supported |
Trying to configure NEQ operation. |
firmware |
"Remove QOS ACL configured on interface." |
|
QOSMGR-3-L4OP_ACL_NEQ_CONFLICT |
3-Error |
NEQ L4 operation not supported |
Trying to configure NEQ operation. |
firmware |
"Remove QOS ACL configured on interface." |
|
QOSMGR-3-L4OP_ACL_PORT_CONFLICT |
3-Error |
Port ranger is already allocated to ACL on this interface.\n QoS policy configruation failed. Remove QoS command from interface[chars] |
ACL configured on this interface uses Port ranger. Remove ACL configuration apply QoS first and then configure ACL |
firmware |
"Remove ACL configured on interface." |
|
QOSMGR-3-L4OP_ACL_PORT_CONFLICT |
3-Error |
Port ranger is already allocated to ACL on this interface.\n QoS policy configruation failed. Remove QoS command from interface[chars] |
ACL configured on this interface uses Port ranger. Remove ACL configuration apply QoS first and then configure ACL |
firmware |
"Remove ACL configured on interface." |
|
QOSMGR-3-L4OP_ACL_RESERVATION_EXHAUSTED |
3-Error |
Port ranger resource reserved for ACL exhausted port expansion used [chars] |
Port ranger is shared between ACL and v6 QOS ACL. ACL reservation exhausted |
firmware |
"Remove ACL configuration or increase reservation through ROMMON variable" " QOS_PORTRANGE_RESOURCE" |
|
QOSMGR-3-L4OP_ACL_RESERVATION_EXHAUSTED |
3-Error |
Port ranger resource reserved for ACL exhausted port expansion used [chars] |
Port ranger is shared between ACL and v6 QOS ACL. ACL reservation exhausted |
firmware |
"Remove ACL configuration or increase reservation through ROMMON variable" " QOS_PORTRANGE_RESOURCE" |
|
QOSMGR-3-L4OP_PORT_RANGE_VCU_PER_PORT_EXCEEDED |
3-Error |
Port range entry on this interface has exceeded maximum permitted 8 operations further l4 match ACE will be ignored[chars] |
Interface already has maximum permitted 8 l4 operations |
firmware |
"Configure only 8 l4 match ACE per interface" |
|
QOSMGR-3-L4OP_PORT_RANGE_VCU_PER_PORT_EXCEEDED |
3-Error |
Port range entry on this interface has exceeded maximum permitted 8 operations further l4 match ACE will be ignored[chars] |
Interface already has maximum permitted 8 l4 operations |
firmware |
"Configure only 8 l4 match ACE per interface" |
|
QOSMGR-3-L4OP_QOS_PORT_CONFLICT |
3-Error |
Port ranger is allocated to QOS on this interface port expansion used for configured ACL [chars] |
IPv6 QOS configured on this interface uses Port ranger |
firmware |
"Remove IPv6 QOS configured on interface." |
|
QOSMGR-3-L4OP_QOS_PORT_CONFLICT |
3-Error |
Port ranger is allocated to QOS on this interface port expansion used for configured ACL [chars] |
IPv6 QOS configured on this interface uses Port ranger |
firmware |
"Remove IPv6 QOS configured on interface." |
|
QOSMGR-3-L4OP_QOS_RESERVATION_EXHAUSTED |
3-Error |
Port ranger resource reserved for QOS exhausted. policy configuration failed \nRemove other IPv6 QOS configuration or increase reservation through ROMMON [chars] |
Port ranger is shared between ACL and v6 QOS ACL. QOS reservation exhausted |
firmware |
"Remove other IPv6 QOS ACL configuration or increase reservation through ROMMON" " QOS_PORTRANGE_RESOURCE" |
|
QOSMGR-3-L4OP_QOS_RESERVATION_EXHAUSTED |
3-Error |
Port ranger resource reserved for QOS exhausted. policy configuration failed \nRemove other IPv6 QOS configuration or increase reservation through ROMMON [chars] |
Port ranger is shared between ACL and v6 QOS ACL. QOS reservation exhausted |
firmware |
"Remove other IPv6 QOS ACL configuration or increase reservation through ROMMON" " QOS_PORTRANGE_RESOURCE" |
|
QOSMGR-3-LABEL_EXHAUST |
3-Error |
Internal Error in resource allocation |
The system is running out of QoS label to support the number of traffic classes in all attached policy-maps. |
firmware |
"Reduce the number of distinctive class-maps matches " "or 'set' actions in attached policy-maps" |
|
QOSMGR-3-LABEL_EXHAUST |
3-Error |
Internal Error in resource allocation |
The system is running out of QoS label to support the number of traffic classes in all attached policy-maps. |
firmware |
"Reduce the number of distinctive class-maps matches " "or 'set' actions in attached policy-maps" |
|
QOSMGR-3-LABEL_EXHAUST |
3-Error |
Internal Error in resource allocation |
The system is running out of QoS label to support the number of traffic classes in all attached policy-maps. |
firmware |
"Reduce the number of distinctive class-maps matches " "or 'set' actions in attached policy-maps" |
|
QOSMGR-3-LABEL_EXHAUST |
3-Error |
Internal Error in resource allocation |
The system is running out of QoS label to support the number of traffic classes in all attached policy-maps. |
firmware |
"Reduce the number of distinctive class-maps matches " "or 'set' actions in attached policy-maps" |
|
QOSMGR-3-LABEL_EXHAUST |
3-Error |
Internal Error in resource allocation |
The system is running out of QoS label to support the number of traffic classes in all attached policy-maps. |
firmware |
"Reduce the number of distinctive class-maps matches " "or 'set' actions in attached policy-maps" |
|
QOSMGR-3-LOGICAL_RESOURCE_EXHAUSTED |
3-Error |
Logical level queuing resource exhausted [chars] |
Maximum resources used |
firmware |
"Free up unused logical level classes" |
|
QOSMGR-3-LOGICAL_RESOURCE_EXHAUSTED |
3-Error |
Logical level queuing resource exhausted [chars] |
Maximum resources used |
firmware |
"Free up unused logical level classes" |
|
QOSMGR-3-LOGICAL_RESOURCE_EXHAUSTED |
3-Error |
Logical level queuing resource exhausted [chars] |
Maximum resources used |
firmware |
"Free up unused logical level classes" |
|
QOSMGR-3-LOGICAL_RESOURCE_EXHAUSTED |
3-Error |
Logical level queuing resource exhausted [chars] |
Maximum resources used |
firmware |
"Free up unused logical level classes" |
|
QOSMGR-3-LOGICAL_RESOURCE_EXHAUSTED |
3-Error |
Logical level queuing resource exhausted [chars] |
Maximum resources used |
firmware |
"Free up unused logical level classes" |
|
QOSMGR-3-MANUAL_SHAPE_EXCEEDS_SPEED |
3-Error |
Invalid policy-map detected during interface speed change |
Shape value in policy exceeds port speed |
firmware |
"Configure lesser shape value which will not " "exceed interface speed" |
|
QOSMGR-3-MANUAL_SHAPE_EXCEEDS_SPEED |
3-Error |
Invalid policy-map detected during interface speed change |
Shape value in policy exceeds port speed |
firmware |
"Configure lesser shape value which will not " "exceed interface speed" |
|
QOSMGR-3-MANUAL_SHAPE_EXCEEDS_SPEED |
3-Error |
Invalid policy-map detected during interface speed change |
Shape value in policy exceeds port speed |
firmware |
"Configure lesser shape value which will not " "exceed interface speed" |
|
QOSMGR-3-MANUAL_SHAPE_EXCEEDS_SPEED |
3-Error |
Invalid policy-map detected during interface speed change |
Shape value in policy exceeds port speed |
firmware |
"Configure lesser shape value which will not " "exceed interface speed" |
|
QOSMGR-3-MANUAL_SHAPE_EXCEEDS_SPEED |
3-Error |
Invalid policy-map detected during interface speed change |
Shape value in policy exceeds port speed |
firmware |
"Configure lesser shape value which will not " "exceed interface speed" |
|
QOSMGR-3-MARKING_PROFILES_EXHAUSTED |
3-Error |
Out of marking profiles to execute command |
No free marking profile to accommodate the request |
firmware |
"Change config to reuse the existing profiles" |
|
QOSMGR-3-MARKING_PROFILES_EXHAUSTED |
3-Error |
Out of marking profiles to execute command |
No free marking profile to accommodate the request |
firmware |
"Change config to reuse the existing profiles" |
|
QOSMGR-3-MAX_QLIMIT_COMMANDS_EXCEEDED |
3-Error |
Exceeding the maximum queue-limit commands per class |
Trying to exceed the maximum queue-limit commands allowed per class |
firmware |
"Try reducing queue-limit commands under the class" |
|
QOSMGR-3-MAX_QLIMIT_COMMANDS_EXCEEDED |
3-Error |
Exceeding the maximum queue-limit commands per class |
Trying to exceed the maximum queue-limit commands allowed per class |
firmware |
"Try reducing queue-limit commands under the class" |
|
QOSMGR-3-MAX_QLIMIT_COMMANDS_EXCEEDED |
3-Error |
Exceeding the maximum queue-limit commands per class |
Trying to exceed the maximum queue-limit commands allowed per class |
firmware |
"Try reducing queue-limit commands under the class" |
|
QOSMGR-3-MAX_QLIMIT_COMMANDS_EXCEEDED |
3-Error |
Exceeding the maximum queue-limit commands per class |
Trying to exceed the maximum queue-limit commands allowed per class |
firmware |
"Try reducing queue-limit commands under the class" |
|
QOSMGR-3-MAX_QLIMIT_COMMANDS_EXCEEDED |
3-Error |
Exceeding the maximum queue-limit commands per class |
Trying to exceed the maximum queue-limit commands allowed per class |
firmware |
"Try reducing queue-limit commands under the class" |
|
QOSMGR-3-MAX_QUALIFIED_QLIMIT_COMMANDS_EXCEEDED |
3-Error |
Exceeding the maximum qualified queue-limit commands per class |
Trying to exceed the maximum qualified queue-limit commands allowed per class |
firmware |
"Try reducing qualified queue-limit commands " "under the class" |
|
QOSMGR-3-MAX_QUALIFIED_QLIMIT_COMMANDS_EXCEEDED |
3-Error |
Exceeding the maximum qualified queue-limit commands per class |
Trying to exceed the maximum qualified queue-limit commands allowed per class |
firmware |
"Try reducing qualified queue-limit commands " "under the class" |
|
QOSMGR-3-MAX_QUALIFIED_QLIMIT_COMMANDS_EXCEEDED |
3-Error |
Exceeding the maximum qualified queue-limit commands per class |
Trying to exceed the maximum qualified queue-limit commands allowed per class |
firmware |
"Try reducing qualified queue-limit commands " "under the class" |
|
QOSMGR-3-MAX_QUALIFIED_QLIMIT_COMMANDS_EXCEEDED |
3-Error |
Exceeding the maximum qualified queue-limit commands per class |
Trying to exceed the maximum qualified queue-limit commands allowed per class |
firmware |
"Try reducing qualified queue-limit commands " "under the class" |
|
QOSMGR-3-MAX_QUALIFIED_QLIMIT_COMMANDS_EXCEEDED |
3-Error |
Exceeding the maximum qualified queue-limit commands per class |
Trying to exceed the maximum qualified queue-limit commands allowed per class |
firmware |
"Try reducing qualified queue-limit commands " "under the class" |
|
QOSMGR-3-MAX_WRED_THRESHOLDS_EXCEEDED |
3-Error |
Exceeding the maximum number of wred thresholds per class |
Trying to exceed the maximum wred thresholds allowed per class |
firmware |
"Try to use not more than two threhshold combination" " under the class" |
|
QOSMGR-3-OUT_OF_RESOURCES |
3-Error |
Out of TCAM/LPM resources to execute command |
Lack of TCAM/LPM resources due to higher resource requirements |
firmware |
"Change config to reduce tcam entry usage" |
|
QOSMGR-3-OUT_OF_TCAM_RESOURCES |
3-Error |
Out of tcam resources to execute command |
Lack of tcam resources due to higher tcam resource requirements |
firmware |
"Change config to reduce tcam entry usage" |
|
QOSMGR-3-OUT_OF_TCAM_RESOURCES |
3-Error |
Out of tcam resources to execute command |
Lack of tcam resources due to higher tcam resource requirements |
firmware |
"Change config to reduce tcam entry usage" |
|
QOSMGR-3-OUT_OF_TCAM_RESOURCES |
3-Error |
Out of tcam resources to execute command |
Lack of tcam resources due to higher tcam resource requirements |
firmware |
"Change config to reduce tcam entry usage" |
|
QOSMGR-3-OUT_OF_TCAM_RESOURCES |
3-Error |
Out of tcam resources to execute command |
Lack of tcam resources due to higher tcam resource requirements |
firmware |
"Change config to reduce tcam entry usage" |
|
QOSMGR-3-POLICER_PROGRAMMING_FAIL |
3-Error |
Fails to program HW policer |
Can not access to HW successfully. |
firmware |
"" |
|
QOSMGR-3-POLICER_PROGRAMMING_FAIL |
3-Error |
Fails to program HW policer |
Can not access to HW successfully. |
firmware |
"" |
|
QOSMGR-3-POLICER_PROGRAMMING_FAIL |
3-Error |
Fails to program HW policer |
Can not access to HW successfully. |
firmware |
"" |
|
QOSMGR-3-POLICER_PROGRAMMING_FAIL |
3-Error |
Fails to program HW policer |
Can not access to HW successfully. |
firmware |
"" |
|
QOSMGR-3-POLICER_PROGRAMMING_FAIL |
3-Error |
Fails to program HW policer |
Can not access to HW successfully. |
firmware |
"" |
|
QOSMGR-3-PRIORITY_LEVEL_ERROR |
3-Error |
Priority command not acceptable at interface level |
Hardware does not support priority at physical level |
firmware |
"Do not apply bandwidth command at interface " "level policy" |
|
QOSMGR-3-PRIORITY_LEVEL_ERROR |
3-Error |
Priority command not acceptable at interface level |
Hardware does not support priority at physical level |
firmware |
"Do not apply bandwidth command at interface " "level policy" |
|
QOSMGR-3-PRIORITY_LEVEL_ERROR |
3-Error |
Priority command not acceptable at interface level |
Hardware does not support priority at physical level |
firmware |
"Do not apply bandwidth command at interface " "level policy" |
|
QOSMGR-3-PRIORITY_LEVEL_ERROR |
3-Error |
Priority command not acceptable at interface level |
Hardware does not support priority at physical level |
firmware |
"Do not apply bandwidth command at interface " "level policy" |
|
QOSMGR-3-PRIORITY_LEVEL_ERROR |
3-Error |
Priority command not acceptable at interface level |
Hardware does not support priority at physical level |
firmware |
"Do not apply bandwidth command at interface " "level policy" |
|
QOSMGR-3-PROFILE_EXHAUST |
3-Error |
No free scheduler profiles available in hardware |
With the new configuration there is no free profile available in the HW this could be because of dissimilar profiles configured at the same hierarchy level |
firmware |
"Change the config value to closest existing config" |
|
QOSMGR-3-PROFILE_EXHAUST |
3-Error |
No free scheduler profiles available in hardware |
With the new configuration there is no free profile available in the HW this could be because of dissimilar profiles configured at the same hierarchy level |
firmware |
"Change the config value to closest existing config" |
|
QOSMGR-3-PROFILE_EXHAUST |
3-Error |
No free scheduler profiles available in hardware |
With the new configuration there is no free profile available in the HW this could be because of dissimilar profiles configured at the same hierarchy level |
firmware |
"Change the config value to closest existing config" |
|
QOSMGR-3-PROFILE_EXHAUST |
3-Error |
No free scheduler profiles available in hardware |
With the new configuration there is no free profile available in the HW this could be because of dissimilar profiles configured at the same hierarchy level |
firmware |
"Change the config value to closest existing config" |
|
QOSMGR-3-PROFILE_EXHAUST |
3-Error |
No free scheduler profiles available in hardware |
With the new configuration there is no free profile available in the HW this could be because of dissimilar profiles configured at the same hierarchy level |
firmware |
"Change the config value to closest existing config" |
|
QOSMGR-3-PROFILES_EXHAUSTED |
3-Error |
Out of rm profiles to execute command |
No free RM profile to accommodate the request |
firmware |
"Change config to reduce or reuse RM profiles" |
|
QOSMGR-3-PROFILES_EXHAUSTED |
3-Error |
Out of rm profiles to execute command |
No free RM profile to accommodate the request |
firmware |
"Change config to reduce or reuse RM profiles" |
|
QOSMGR-3-PROFILES_EXHAUSTED |
3-Error |
Out of rm profiles to execute command |
No free RM profile to accommodate the request |
firmware |
"Change config to reduce or reuse RM profiles" |
|
QOSMGR-3-PROFILES_EXHAUSTED |
3-Error |
Out of rm profiles to execute command |
No free RM profile to accommodate the request |
firmware |
"Change config to reduce or reuse RM profiles" |
|
QOSMGR-3-PROFILES_EXHAUSTED |
3-Error |
Out of rm profiles to execute command |
No free RM profile to accommodate the request |
firmware |
"Change config to reduce or reuse RM profiles" |
|
QOSMGR-3-PROTOCOL_NOT_SUPPORTED_FOR_POLICY |
3-Error |
The configured protocol is not supported in QoS policy |
Configured protocol is not supported for QoS Policy. Traffic will be matched with alternative clas-maps/class-default |
firmware |
" Unconfigure the ACE with unsupported protocol" " detach and re-attach the policy" |
|
QOSMGR-3-PROTOCOL_NOT_SUPPORTED_FOR_POLICY |
3-Error |
The configured protocol is not supported in QoS policy |
Configured protocol is not supported for QoS Policy. Traffic will be matched with alternative clas-maps/class-default |
firmware |
" Unconfigure the ACE with unsupported protocol" " detach and re-attach the policy" |
|
QOSMGR-3-PROTOCOL_NOT_SUPPORTED_FOR_POLICY |
3-Error |
The configured protocol is not supported in QoS policy |
Configured protocol is not supported for QoS Policy. Traffic will be matched with alternative clas-maps/class-default |
firmware |
" Unconfigure the ACE with unsupported protocol" " detach and re-attach the policy" |
|
QOSMGR-3-PROTOCOL_NOT_SUPPORTED_FOR_POLICY |
3-Error |
The configured protocol is not supported in QoS policy |
Configured protocol is not supported for QoS Policy. Traffic will be matched with alternative clas-maps/class-default |
firmware |
" Unconfigure the ACE with unsupported protocol" " detach and re-attach the policy" |
|
QOSMGR-3-QLIMIT_LEVEL_ERROR |
3-Error |
Qlimit command not supported in non-leaf classes |
Trying to configure qlimit in a non leaf class |
firmware |
"Configure qlimit only in leaf classes" |
|
QOSMGR-3-QLIMIT_LEVEL_ERROR |
3-Error |
Qlimit command not supported in non-leaf classes |
Trying to configure qlimit in a non leaf class |
firmware |
"Configure qlimit only in leaf classes" |
|
QOSMGR-3-QLIMIT_LEVEL_ERROR |
3-Error |
Qlimit command not supported in non-leaf classes |
Trying to configure qlimit in a non leaf class |
firmware |
"Configure qlimit only in leaf classes" |
|
QOSMGR-3-QLIMIT_LEVEL_ERROR |
3-Error |
Qlimit command not supported in non-leaf classes |
Trying to configure qlimit in a non leaf class |
firmware |
"Configure qlimit only in leaf classes" |
|
QOSMGR-3-QLIMIT_LEVEL_ERROR |
3-Error |
Qlimit command not supported in non-leaf classes |
Trying to configure qlimit in a non leaf class |
firmware |
"Configure qlimit only in leaf classes" |
|
QOSMGR-3-QLIMIT_PERCENT_ERROR |
3-Error |
qlimit-limit percent is oversubscribed |
qlimit-limit percent is oversubscribed |
firmware |
"Config queue-limit percent appropriately" |
|
QOSMGR-3-QLIMIT_VALUE_OUT_OF_RANGE |
3-Error |
Qlimit value is out of range |
Trying to configure a qlimit value outside the supported range |
firmware |
"Configure qlimit value within supported range" |
|
QOSMGR-3-QLIMIT_VALUE_OUT_OF_RANGE |
3-Error |
Qlimit value is out of range |
Trying to configure a qlimit value outside the supported range |
firmware |
"Configure qlimit value within supported range" |
|
QOSMGR-3-QLIMIT_VALUE_OUT_OF_RANGE |
3-Error |
Qlimit value is out of range |
Trying to configure a qlimit value outside the supported range |
firmware |
"Configure qlimit value within supported range" |
|
QOSMGR-3-QLIMIT_VALUE_OUT_OF_RANGE |
3-Error |
Qlimit value is out of range |
Trying to configure a qlimit value outside the supported range |
firmware |
"Configure qlimit value within supported range" |
|
QOSMGR-3-QLIMIT_VALUE_OUT_OF_RANGE |
3-Error |
Qlimit value is out of range |
Trying to configure a qlimit value outside the supported range |
firmware |
"Configure qlimit value within supported range" |
|
QOSMGR-3-QOSMGR_POLICYMAP_ERROR |
3-Error |
policy-map applied on [chars] is in error condition |
The policy-map applied on the printed target may not work or the stats for that target will not work. |
rsp3-qos |
"Collect the uea_mgr logs" |
|
QOSMGR-3-QOSMGR_POLICYMAP_ERROR |
3-Error |
policy-map applied on [chars] is in error condition |
The policy-map applied on the printed target may not work or the stats for that target will not work. |
rsp3-qos |
"Collect the uea_mgr logs" |
|
QOSMGR-3-QUEUE_EXHAUSTED |
3-Error |
Class level queuing resource exhausted [chars] |
Maximum resources used |
firmware |
"Free up unused class level classes" |
|
QOSMGR-3-QUEUE_EXHAUSTED |
3-Error |
Class level queuing resource exhausted [chars] |
Maximum resources used |
firmware |
"Free up unused class level classes" |
|
QOSMGR-3-QUEUE_EXHAUSTED |
3-Error |
Class level queuing resource exhausted [chars] |
Maximum resources used |
firmware |
"Free up unused class level classes" |
|
QOSMGR-3-QUEUE_EXHAUSTED |
3-Error |
Class level queuing resource exhausted [chars] |
Maximum resources used |
firmware |
"Free up unused class level classes" |
|
QOSMGR-3-QUEUE_EXHAUSTED |
3-Error |
Class level queuing resource exhausted [chars] |
Maximum resources used |
firmware |
"Free up unused class level classes" |
|
QOSMGR-3-QUEUE_FLUSH_FAILED |
3-Error |
Queue-Flush not successful |
Scheduler unable to flush the queue |
firmware |
"Remove any shape configuration for the queue" |
|
QOSMGR-3-QUEUE_FLUSH_FAILED |
3-Error |
Queue-Flush not successful |
Scheduler unable to flush the queue |
firmware |
"Remove any shape configuration for the queue" |
|
QOSMGR-3-QUEUE_FLUSH_FAILED |
3-Error |
Queue-Flush not successful |
Scheduler unable to flush the queue |
firmware |
"Remove any shape configuration for the queue" |
|
QOSMGR-3-QUEUE_FLUSH_FAILED |
3-Error |
Queue-Flush not successful |
Scheduler unable to flush the queue |
firmware |
"Remove any shape configuration for the queue" |
|
QOSMGR-3-QUEUE_FLUSH_FAILED |
3-Error |
Queue-Flush not successful |
Scheduler unable to flush the queue |
firmware |
"Remove any shape configuration for the queue" |
|
QOSMGR-3-SCHEDULER_PROGRAMMING_FAIL |
3-Error |
Fails to program HW scheduler |
Can not access to HW successfully. |
firmware |
"" |
|
QOSMGR-3-SCHEDULER_PROGRAMMING_FAIL |
3-Error |
Fails to program HW scheduler |
Can not access to HW successfully. |
firmware |
"" |
|
QOSMGR-3-SCHEDULER_PROGRAMMING_FAIL |
3-Error |
Fails to program HW scheduler |
Can not access to HW successfully. |
firmware |
"" |
|
QOSMGR-3-SCHEDULER_PROGRAMMING_FAIL |
3-Error |
Fails to program HW scheduler |
Can not access to HW successfully. |
firmware |
"" |
|
QOSMGR-3-SCHEDULER_PROGRAMMING_FAIL |
3-Error |
Fails to program HW scheduler |
Can not access to HW successfully. |
firmware |
"" |
|
QOSMGR-3-SHAPE_BANDWIDTH_PERCENT_ERROR |
3-Error |
Shape - Bandwidth-percent values inconsistent in the hierarchy calculated bandwidth will exceed shape |
Because of this new shape command Bandwidth percent configured in one of children class will get more value than its manually configured shape. Please note that bandwidth percent is calculated from parent's shapePIR |
firmware |
"Either configure higher shape value or " " reduce violating bandwidth-percent value" |
|
QOSMGR-3-SHAPE_BANDWIDTH_PERCENT_ERROR |
3-Error |
Shape - Bandwidth-percent values inconsistent in the hierarchy calculated bandwidth will exceed shape |
Because of this new shape command Bandwidth percent configured in one of children class will get more value than its manually configured shape. Please note that bandwidth percent is calculated from parent's shapePIR |
firmware |
"Either configure higher shape value or " " reduce violating bandwidth-percent value" |
|
QOSMGR-3-SHAPE_BANDWIDTH_PERCENT_ERROR |
3-Error |
Shape - Bandwidth-percent values inconsistent in the hierarchy calculated bandwidth will exceed shape |
Because of this new shape command Bandwidth percent configured in one of children class will get more value than its manually configured shape. Please note that bandwidth percent is calculated from parent's shapePIR |
firmware |
"Either configure higher shape value or " " reduce violating bandwidth-percent value" |
|
QOSMGR-3-SHAPE_BANDWIDTH_PERCENT_ERROR |
3-Error |
Shape - Bandwidth-percent values inconsistent in the hierarchy calculated bandwidth will exceed shape |
Because of this new shape command Bandwidth percent configured in one of children class will get more value than its manually configured shape. Please note that bandwidth percent is calculated from parent's shapePIR |
firmware |
"Either configure higher shape value or " " reduce violating bandwidth-percent value" |
|
QOSMGR-3-SHAPE_BANDWIDTH_PERCENT_ERROR |
3-Error |
Shape - Bandwidth-percent values inconsistent in the hierarchy calculated bandwidth will exceed shape |
Because of this new shape command Bandwidth percent configured in one of children class will get more value than its manually configured shape. Please note that bandwidth percent is calculated from parent's shapePIR |
firmware |
"Either configure higher shape value or " " reduce violating bandwidth-percent value" |
|
QOSMGR-3-SHAPE_CHILD_BANDWIDTH_ERROR |
3-Error |
Bandwidth in one of the children class is greater than input shape value |
Children class's bandwidth should not be higher than input |
firmware |
"Either increase input value or decrese erring one" |
|
QOSMGR-3-SHAPE_CHILD_BANDWIDTH_ERROR |
3-Error |
Bandwidth in one of the children class is greater than input shape value |
Children class's bandwidth should not be higher than input |
firmware |
"Either increase input value or decrese erring one" |
|
QOSMGR-3-SHAPE_CHILD_BANDWIDTH_ERROR |
3-Error |
Bandwidth in one of the children class is greater than input shape value |
Children class's bandwidth should not be higher than input |
firmware |
"Either increase input value or decrese erring one" |
|
QOSMGR-3-SHAPE_CHILD_BANDWIDTH_ERROR |
3-Error |
Bandwidth in one of the children class is greater than input shape value |
Children class's bandwidth should not be higher than input |
firmware |
"Either increase input value or decrese erring one" |
|
QOSMGR-3-SHAPE_CHILD_BANDWIDTH_ERROR |
3-Error |
Bandwidth in one of the children class is greater than input shape value |
Children class's bandwidth should not be higher than input |
firmware |
"Either increase input value or decrese erring one" |
|
QOSMGR-3-SHAPE_CHILD_ERROR |
3-Error |
One of children class's shape config is higher |
Children class's shape should not be higher than current |
firmware |
"Either increase input value or decrese erring one" |
|
QOSMGR-3-SHAPE_CHILD_ERROR |
3-Error |
One of children class's shape config is higher |
Children class's shape should not be higher than current |
firmware |
"Either increase input value or decrese erring one" |
|
QOSMGR-3-SHAPE_CHILD_ERROR |
3-Error |
One of children class's shape config is higher |
Children class's shape should not be higher than current |
firmware |
"Either increase input value or decrese erring one" |
|
QOSMGR-3-SHAPE_CHILD_ERROR |
3-Error |
One of children class's shape config is higher |
Children class's shape should not be higher than current |
firmware |
"Either increase input value or decrese erring one" |
|
QOSMGR-3-SHAPE_CHILD_ERROR |
3-Error |
One of children class's shape config is higher |
Children class's shape should not be higher than current |
firmware |
"Either increase input value or decrese erring one" |
|
QOSMGR-3-SHAPE_PARENT_ERROR |
3-Error |
Shape value is greater than parent class's shape or interface's speed |
Parent class's shape value cannot be smaller than current |
firmware |
"Configure shape value lesser than parent class's" " shape or interface's speed" |
|
QOSMGR-3-SHAPE_PARENT_ERROR |
3-Error |
Shape value is greater than parent class's shape or interface's speed |
Parent class's shape value cannot be smaller than current |
firmware |
"Configure shape value lesser than parent class's" " shape or interface's speed" |
|
QOSMGR-3-SHAPE_PARENT_ERROR |
3-Error |
Shape value is greater than parent class's shape or interface's speed |
Parent class's shape value cannot be smaller than current |
firmware |
"Configure shape value lesser than parent class's" " shape or interface's speed" |
|
QOSMGR-3-SHAPE_PARENT_ERROR |
3-Error |
Shape value is greater than parent class's shape or interface's speed |
Parent class's shape value cannot be smaller than current |
firmware |
"Configure shape value lesser than parent class's" " shape or interface's speed" |
|
QOSMGR-3-SHAPE_PARENT_ERROR |
3-Error |
Shape value is greater than parent class's shape or interface's speed |
Parent class's shape value cannot be smaller than current |
firmware |
"Configure shape value lesser than parent class's" " shape or interface's speed" |
|
QOSMGR-3-SHAPE_UNDERFLOW |
3-Error |
New shape/speed value is less than the total bandwidth configured in the interface |
Shape/speed configured is less than the total bandwidth configured in the interface |
firmware |
"Increase the shape/speed value or reduce " "the bandwidth configured in the child classes" |
|
QOSMGR-3-SHAPE_UNDERFLOW |
3-Error |
New shape/speed value is less than the total bandwidth configured in the interface |
Shape/speed configured is less than the total bandwidth configured in the interface |
firmware |
"Increase the shape/speed value or reduce " "the bandwidth configured in the child classes" |
|
QOSMGR-3-SHAPE_UNDERFLOW |
3-Error |
New shape/speed value is less than the total bandwidth configured in the interface |
Shape/speed configured is less than the total bandwidth configured in the interface |
firmware |
"Increase the shape/speed value or reduce " "the bandwidth configured in the child classes" |
|
QOSMGR-3-SHAPE_UNDERFLOW |
3-Error |
New shape/speed value is less than the total bandwidth configured in the interface |
Shape/speed configured is less than the total bandwidth configured in the interface |
firmware |
"Increase the shape/speed value or reduce " "the bandwidth configured in the child classes" |
|
QOSMGR-3-SHAPE_UNDERFLOW |
3-Error |
New shape/speed value is less than the total bandwidth configured in the interface |
Shape/speed configured is less than the total bandwidth configured in the interface |
firmware |
"Increase the shape/speed value or reduce " "the bandwidth configured in the child classes" |
|
QOSMGR-3-TABLEMAP_EXHAUST |
3-Error |
Internal Error in resource allocation |
The system is running out of table-map resources |
firmware |
"Reduce the number of distinctive class-map " "matches in attached policy-maps" |
|
QOSMGR-3-TABLEMAP_EXHAUST |
3-Error |
Internal Error in resource allocation |
The system is running out of table-map resources |
- |
"Reduce the number of distinctive class-map " "matches in attached policy-maps" |
|
QOSMGR-3-TABLEMAP_MODIFY |
3-Error |
Table-Map modification Error |
Table-Map is being used |
firmware |
"Create a new Table-Map template" "with the different name" |
|
QOSMGR-3-TCAM_EXHAUSTION |
3-Error |
Internal Error in resource allocation |
The system is running out of TCAM entries to support the number of traffic classes in the policy-map. The maximum number of TCAM entries is platform dependent. |
firmware |
"Reduce the number of classes in attached policy-maps" |
|
QOSMGR-3-TCAM_EXHAUSTION |
3-Error |
Internal Error in resource allocation |
The system is running out of TCAM entries to support the number of traffic classes in the policy-map. The maximum number of TCAM entries is platform dependent. |
firmware |
"Reduce the number of classes in attached policy-maps" |
|
QOSMGR-3-TCAM_EXHAUSTION |
3-Error |
Internal Error in resource allocation |
The system is running out of TCAM entries to support the number of traffic classes in the policy-map. The maximum number of TCAM entries is platform dependent. |
firmware |
"Reduce the number of classes in attached policy-maps" |
|
QOSMGR-3-TCAM_EXHAUSTION |
3-Error |
Internal Error in resource allocation |
The system is running out of TCAM entries to support the number of traffic classes in the policy-map. The maximum number of TCAM entries is platform dependent. |
firmware |
"Reduce the number of classes in attached policy-maps" |
|
QOSMGR-3-TCAM_EXHAUSTION |
3-Error |
Internal Error in resource allocation |
The system is running out of TCAM entries to support the number of traffic classes in the policy-map. The maximum number of TCAM entries is platform dependent. |
firmware |
"Reduce the number of classes in attached policy-maps" |
|
QOSMGR-3-TCAM_PROGRAMMING_FAIL |
3-Error |
Fails to program TCAM for policymap [chars] |
Can not access to HW successfully. |
firmware |
LOG_STD_ACTION |
|
QOSMGR-3-TCAM_PROGRAMMING_FAIL |
3-Error |
Fails to program TCAM for policymap [chars] |
Can not access to HW successfully. |
firmware |
LOG_STD_ACTION |
|
QOSMGR-3-TCAM_PROGRAMMING_FAIL |
3-Error |
Fails to program TCAM for policymap [chars] |
Can not access to HW successfully. |
firmware |
LOG_STD_ACTION |
|
QOSMGR-3-TCAM_PROGRAMMING_FAIL |
3-Error |
Fails to program TCAM for policymap [chars] |
Can not access to HW successfully. |
firmware |
LOG_STD_ACTION |
|
QOSMGR-3-TCAM_PROGRAMMING_FAIL |
3-Error |
Fails to program TCAM for policymap [chars] |
Can not access to HW successfully. |
firmware |
LOG_STD_ACTION |
|
QOSMGR-3-TDM_OC_HIERARCHY_UNSUPPORTED |
3-Error |
Only two-level hierarchy is supported on TDM/OC3/OC12 interfaces |
Unsupported QoS hierarchy on TDM/OC3/OC12 interfaces |
firmware |
"Change config to reduce to two-level policy" |
|
QOSMGR-3-TDM_OC_HIERARCHY_UNSUPPORTED |
3-Error |
Only two-level hierarchy is supported on TDM/OC3/OC12 interfaces |
Unsupported QoS hierarchy on TDM/OC3/OC12 interfaces |
firmware |
"Change config to reduce to two-level policy" |
|
QOSMGR-3-TDM_OC_HIERARCHY_UNSUPPORTED |
3-Error |
Only two-level hierarchy is supported on TDM/OC3/OC12 interfaces |
Unsupported QoS hierarchy on TDM/OC3/OC12 interfaces |
firmware |
"Change config to reduce to two-level policy" |
|
QOSMGR-3-TDM_OC_HIERARCHY_UNSUPPORTED |
3-Error |
Only two-level hierarchy is supported on TDM/OC3/OC12 interfaces |
Unsupported QoS hierarchy on TDM/OC3/OC12 interfaces |
firmware |
"Change config to reduce to two-level policy" |
|
QOSMGR-3-UNSUPPORTED_FILTERS |
3-Error |
Installed Policy-map has filters which are not supported.Detach re-configure and attach the policy |
Policy-map has filters which are not supported |
firmware |
"Change config to use only supported filters" " detach and re-attach the policy" |
|
QOSMGR-3-UNSUPPORTED_QLIMIT_UNITS |
3-Error |
Qlimit unit other than usec & byte is not supported |
Trying to configure a qlimit unit other than bytes or usec |
firmware |
"Configure qlimit in terms of bytes or usec" |
|
QOSMGR-3-UNSUPPORTED_QLIMIT_UNITS |
3-Error |
Qlimit unit other than usec & byte is not supported |
Trying to configure a qlimit unit other than bytes or usec |
firmware |
"Configure qlimit in terms of bytes or usec" |
|
QOSMGR-3-UNSUPPORTED_QLIMIT_UNITS |
3-Error |
Qlimit unit other than usec & byte is not supported |
Trying to configure a qlimit unit other than bytes or usec |
firmware |
"Configure qlimit in terms of bytes or usec" |
|
QOSMGR-3-UNSUPPORTED_QLIMIT_UNITS |
3-Error |
Qlimit unit other than usec & byte is not supported |
Trying to configure a qlimit unit other than bytes or usec |
firmware |
"Configure qlimit in terms of bytes or usec" |
|
QOSMGR-3-UNSUPPORTED_QLIMIT_UNITS |
3-Error |
Qlimit unit other than usec & byte is not supported |
Trying to configure a qlimit unit other than bytes or usec |
firmware |
"Configure qlimit in terms of bytes or usec" |
|
QOSMGR-3-UNSUPPORTED_WRED_UNITS |
3-Error |
WRED threshold unit other than usec & byte is not supported |
Trying to configure a WRED threshold unit other than bytes or usec |
firmware |
"Configure WRED threshold in terms of bytes or usec" |
|
QOSMGR-3-WRED_LAVEL_ERROR |
3-Error |
random-detect command not supported in non-leaf classes |
Trying to configure random-detect in a non leaf class |
firmware |
"Configure random-detect only in leaf classes" |
|
QOSMGR-3-WRED_LEVEL_ERROR |
3-Error |
random-deteact command not supported in non-leaf classes |
Trying to configure random-detect in a non leaf class |
firmware |
"Configure random-detect only in leaf classes" |
|
QOSMGR-3-WRED_VALUE_OUT_OF_RANGE |
3-Error |
random-detect value is out of range |
Trying to configure a random-detect value outside the supported range |
firmware |
"Configure qlimit value within supported range" |
|
QOSMGR-4-EGG_AGG_POL_BLOCK_EXCEEDING_HW |
4-Warning |
Number of output child policer's are more than the block size. Configure the block size accordingly [chars] |
The system is running out of policers to support the specified policy-maps. |
firmware |
"Reduce the number of policer usage in attached input policy-maps. " |
|
QOSMGR-4-EGG_AGG_POLICER_EXCEEDING_HW |
4-Warning |
Output Parent policer block size can't be allocated configuration has exceeded hardware limitation for policymap [chars] |
The system is running out of policers to support the specified policy-maps. |
firmware |
"Reduce the number of policer usage in attached input policy-maps. " |
|
QOSMGR-4-GPORT_SCHEDULER_EXCEEDING_HW |
4-Warning |
[chars] has exceeded the hardware limitation |
The system is running out of output queues to support the specified policy-map. |
firmware |
"Remove the EFPs from the interfaces" |
|
QOSMGR-4-GPORT_SCHEDULER_EXCEEDING_HW |
4-Warning |
[chars] has exceeded the hardware limitation |
The system is running out of output queues to support the specified policy-map. |
firmware |
"Remove the EFPs from the interfaces" |
|
QOSMGR-4-IDMGR_RESOURCE_EXCEEDED |
4-Warning |
[chars] has exceeded its maximum number : [dec] |
Max number of FLOW ID allocation has reached |
firmware |
"reduce the number of flow id allocation for the interface" |
|
QOSMGR-4-IDMGR_RESOURCE_EXCEEDED |
4-Warning |
[chars] has exceeded its maximum number : [dec] |
Max number of FLOW ID allocation has reached |
firmware |
"reduce the number of flow id allocation for the interface" |
|
QOSMGR-4-INVALID_POLICYMAP_DUE_NON_QOS_EVENT |
4-Warning |
The policy-map [chars] is detached due to the event [chars]. |
The attached policy-map becomes invalid due to the change of the port speed. |
firmware |
"Change the shaping/bandwidth of the output policy-map and re-attach to the interface ." |
|
QOSMGR-4-INVALID_POLICYMAP_DUE_NON_QOS_EVENT |
4-Warning |
The policy-map [chars] is detached due to the event [chars]. |
The attached policy-map becomes invalid due to the change of the port speed. |
firmware |
"Change the shaping/bandwidth of the output policy-map and re-attach to the interface ." |
|
QOSMGR-4-INVALID_POLICYMAP_DUE_NON_QOS_EVENT |
4-Warning |
The policy-map [chars] is detached due to the event [chars]. |
The attached policy-map becomes invalid due to the change of the port speed. |
firmware |
"Change the shaping/bandwidth of the output policy-map and re-attach to the interface ." |
|
QOSMGR-4-INVALID_POLICYMAP_DUE_NON_QOS_EVENT |
4-Warning |
The policy-map [chars] is detached due to the event [chars]. |
The attached policy-map becomes invalid due to the change of the port speed. |
firmware |
"Change the shaping/bandwidth of the output policy-map and re-attach to the interface ." |
|
QOSMGR-4-INVALID_POLICYMAP_DUE_NON_QOS_EVENT |
4-Warning |
The policy-map [chars] is detached due to the event [chars]. |
The attached policy-map becomes invalid due to the change of the port speed. |
firmware |
"Change the shaping/bandwidth of the output policy-map and re-attach to the interface ." |
|
QOSMGR-4-POLICER_EXCEEDING_HW |
4-Warning |
Policer configuration has exceeded hardware limitation for policymap [chars] |
The system is running out of policers to support the specified policy-maps. |
firmware |
"Reduce the number of policer usage in attached input policy-maps. " |
|
QOSMGR-4-POLICER_EXCEEDING_HW |
4-Warning |
Policer configuration has exceeded hardware limitation for policymap [chars] |
The system is running out of policers to support the specified policy-maps. |
firmware |
"Reduce the number of policer usage in attached input policy-maps. " |
|
QOSMGR-4-POLICER_EXCEEDING_HW |
4-Warning |
Policer configuration has exceeded hardware limitation for policymap [chars] |
The system is running out of policers to support the specified policy-maps. |
firmware |
"Reduce the number of policer usage in attached input policy-maps. " |
|
QOSMGR-4-POLICER_EXCEEDING_HW |
4-Warning |
Policer configuration has exceeded hardware limitation for policymap [chars] |
The system is running out of policers to support the specified policy-maps. |
firmware |
"Reduce the number of policer usage in attached input policy-maps. " |
|
QOSMGR-4-POLICER_EXCEEDING_HW |
4-Warning |
Policer configuration has exceeded hardware limitation for policymap [chars] |
The system is running out of policers to support the specified policy-maps. |
firmware |
"Reduce the number of policer usage in attached input policy-maps. " |
|
QOSMGR-4-POLICER_PROFILE_EXCEEDED |
4-Warning |
Policer profiles have exceeded the maximum number [dec] |
Max number for Qos policer profiles has reached |
firmware |
"Reduce the number of policer usage in attached input policy-maps. " |
|
QOSMGR-4-POLICER_PROFILE_EXCEEDED |
4-Warning |
Policer profiles have exceeded the maximum number [dec] |
Max number for Qos policer profiles has reached |
firmware |
"Reduce the number of policer usage in attached input policy-maps. " |
|
QOSMGR-4-QUEUE_EXCEEDING_HW |
4-Warning |
Queue configuration has exceeded hardware limitation for policymap [chars] |
The system is running out of output queues to support the specified policy-map. |
firmware |
"Reduce the number of the traffic classes in attached output policy-maps." |
|
QOSMGR-4-QUEUE_EXCEEDING_HW |
4-Warning |
Queue configuration has exceeded hardware limitation for policymap [chars] |
The system is running out of output queues to support the specified policy-map. |
firmware |
"Reduce the number of the traffic classes in attached output policy-maps." |
|
QOSMGR-4-QUEUE_EXCEEDING_HW |
4-Warning |
Queue configuration has exceeded hardware limitation for policymap [chars] |
The system is running out of output queues to support the specified policy-map. |
firmware |
"Reduce the number of the traffic classes in attached output policy-maps." |
|
QOSMGR-4-QUEUE_EXCEEDING_HW |
4-Warning |
Number of queues has exceeded the hardware limitation for VOQs |
The system is running out of output queues to support the specified policy-map. |
firmware |
"Remove the EFPs from the interfaces" |
|
QOSMGR-4-QUEUE_EXCEEDING_HW |
4-Warning |
Number of queues has exceeded the hardware limitation for VOQs |
The system is running out of output queues to support the specified policy-map. |
firmware |
"Remove the EFPs from the interfaces" |
|
QOSMGR-4-STATISTICS_FAIL |
4-Warning |
Internal Error in reading statistics |
Can not access to HW to read statistics successfully. |
firmware |
LOG_STD_ACTION |
|
QOSMGR-4-STATISTICS_FAIL |
4-Warning |
Internal Error in reading statistics |
Can not access to HW to read statistics successfully. |
firmware |
LOG_STD_ACTION |
|
QOSMGR-4-STATISTICS_FAIL |
4-Warning |
Internal Error in reading statistics |
Can not access to HW to read statistics successfully. |
firmware |
LOG_STD_ACTION |
|
QOSMGR-4-STATISTICS_FAIL |
4-Warning |
Internal Error in reading statistics |
Can not access to HW to read statistics successfully. |
firmware |
LOG_STD_ACTION |
|
QOSMGR-4-STATISTICS_FAIL |
4-Warning |
Internal Error in reading statistics |
Can not access to HW to read statistics successfully. |
firmware |
LOG_STD_ACTION |
|
QOSMGR-4-VOQ_CONNECTOR_EXCEEDING_HW |
4-Warning |
Number of VOQ connectors has exceeded the hardware limitation for [chars] in asic id : [dec] |
The system is running out of output queues to support the specified policy-map. |
firmware |
"Remove the EFPs from the interfaces" |
|
QOSMGR-4-VOQ_CONNECTOR_EXCEEDING_HW |
4-Warning |
Number of VOQ connectors has exceeded the hardware limitation for [chars] in asic id : [dec] |
The system is running out of output queues to support the specified policy-map. |
firmware |
"Remove the EFPs from the interfaces" |
|
QUICC_ASYNC-3-CTSLOST |
3-Error |
Unit [dec] Clear to Send Lost |
- |
- |
"Check the serial interface cable and/or communication equipment such\n\ as the channel service unit/data service unit CSU/DSU." |
|
QUICC_ETHER-1-INITFAIL |
1-Alert |
msgtxt_initfail |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
QUICC_ETHER-1-LOSTCARR |
1-Alert |
Unit [dec] lost carrier. Transceiver problem? |
The Ethernet 10BaseT cable is unplugged. |
- |
"Connect the 10BaseT Ethernet cable." |
|
QUICC_ETHER-3-UNDERFLO |
3-Error |
Unit [dec] underflow error |
While transmitting a frame the Ethernet controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally such a problem is temporary depending on transient peak loads within the system. |
- |
"The system should recover. No action is required. If the problem recurs it indicates a hardware error that might be related to data traffic patterns. Copy the error message exactly as it appears and report it to your technical support representative." |
|
QUICC_ETHER-5-COLL |
5-Notice |
Unit [dec] excessive collisions. Retry limit [dec] exceeded |
An Ethernet cable is broken or unterminated. |
- |
"Check cables for proper connections termination and so on." |
|
QUICC_ETHER-5-HBEAT |
5-Notice |
Unit [dec] heartbeat check failure |
The Ethernet cable might be too long or there could be too many repeaters such that the delay from one end to the other is too long. The Ethernet cable might be overloaded with too many users. |
- |
"Verify that your Ethernet cable is the correct length and that you do not have too many repeaters in use. If these are not the problem try removing hosts from the Ethernet segment to reduce the load." |
|
QUICC_ETHER-5-LATECOLL |
5-Notice |
Unit [dec] late collision error |
The Ethernet cable might be too long or there could be too many repeaters such that the delay from one end to the other is too long. The Ethernet cable might be overloaded with too many users. |
- |
"Verify that your Ethernet cable is the correct length and that you do not have too many repeaters in use. If these are not the problem try removing hosts from the Ethernet segment to reduce the load." |
|
QUICC_SERIAL-1-INITFAIL |
1-Alert |
msgtxt_initfail |
The serial interface controller of the QUICC chip could not be\n\ initialized or started for operation. There is probably a hardware\n\ problem. |
- |
"Power cycle the system. If the error reoccurs replace the unit." |
|
QUICC_SERIAL-3-CTSLOST |
3-Error |
Unit [dec] Clear to Send Lost |
- |
- |
"Check the serial interface cable and or communication equipment such\n\ as the channel service unit/data service unit CSU/DSU." |
|
QUICC_SERIAL-3-UNDERFLO |
3-Error |
Unit [dec] underflow error |
While transmitting a frame the serial controller chip's local buffer\n\ received insufficient data because data could not be transferred to the\n\ chip fast enough to keep pace with its output rate. Normally such a\n\ problem is temporary depending on transient peak loads within the\n\ system. |
- |
"The system should recover. No action is required.\n\\n\ If the problem reccurs it indicates a hardware error that might be\n\ related to data traffic patterns. Copy the error message exactly as it\n\ appears and report it to your technical support representative." |
|
QUICC_SERIAL-5-LINEFLAP |
5-Notice |
Unit [dec] excessive modem control changes |
- |
- |
"Check the serial interface cable. The error can occur if the cable is\n\ disconnected or has come loose and is picking up noise. If the cable\n\ appears to be connected correctly check the equipment connected to the\n\ cable." |
|
QUICC_SERIAL-5-LOSTCARR |
5-Notice |
Unit [dec] carrier detect signal lost during message reception |
- |
- |
"Check the serial interface cable. The error can occur if the cable is\n\ disconnected." |
|
QUICC-1-NOMEMORY |
1-Alert |
msgtxt_nomemory |
The MC68360/QUICC CPU was unable to access the memory it needs to\n\ carry out its functions. Here are some possible causes.\n\\n\ The network is large requiring a lot of memory for routing tables and\n\ so on.\n\\n\ The router configuration has many features enabled each of which\n\ require a certain amount of memory.\n\\n\ A software error memory leak exists. |
- |
"Reduce system activity to ease the memory demand or upgrade to a\n\ larger memory configuration." |
|
QUICC-3-OWNERR |
3-Error |
msgtxt_ownerror |
An internal software error occurred. |
- |
"Call your technical support representative to obtain a software\n\ upgrade." |
|
QUICC-3-UCODE_REV_UNKN |
3-Error |
Unknown microcode revision number: [dec] |
The MC68360/QUICC CPU was running an unexpected version of microcode.\n\ This could be possible if a new version of the QUICC chip was released\n\ or if a very old version was used in the manufacturing process. This\n\ could also occur if a new version of microcode was released to fix\n\ any bugs |
- |
"A decrease in performance might occur for any async interfaces running\n\ PPP. Call your technical support representative if this is an \n\ issue." |
|
R4K_MP-3-CRASHED |
3-Error |
CPU [dec] has now crashed a total of [dec] times. |
The indicated CPU crashed and has been restarted. |
msw |
LOG_STD_ACTION |
|
R4K_MP-5-DELEGATE_GETBUF |
5-Notice |
Delegated call to 0x[hec] failed out of buffers |
An RPC call to the indicated function failed. |
msw |
LOG_STD_ACTION |
|
RAC-3-RACIPL |
3-Error |
DHCP is already running on interface [chars] |
The interface already has a DHCP originated address via some other system mechanism |
- |
"Verify the system configuration" |
|
RAC-3-RACNOIPL |
3-Error |
Can not find lease information for interface [chars] |
Internal error - DHCP lease information is missing for the interface |
- |
"Report the problem and how it can be reproduced to Cisco TAC" |
|
RAC-3-RACNOQ |
3-Error |
Can't create RAC work queue |
Internal error - probable cause is insufficient memory resources |
- |
"Check available memory." |
|
RADIAN-2-IL_SYNC_ERR |
2-Critical |
[chars] Radian IL sync/align error [chars] |
Radian IL sync or align error with Cobalt4 IL |
cmts-platform-infr |
LOG_STD_ACTION |
|
RADIAN-3-CMIC_FAIL |
3-Error |
Radian [dec] CMIC register [chars] fail for [chars] rc = [dec] |
Radian CMIC register read or write operation failure |
cmts-platform-infr |
LOG_STD_SH_TECH_ACTION |
|
RADIAN-3-IL_INTR_ERR |
3-Error |
Radian slot/unit [dec]/[dec] IL ERR INTR: [chars] |
Radian IL ERROR interrupt occurs |
cmts-platform-infr |
LOG_STD_ACTION |
|
RADIAN-3-INIT_FAIL |
3-Error |
[chars] for slot: [dec] unit: [dec] rc: [dec] |
Radian init failure |
cmts-platform-infr |
LOG_STD_ACTION |
|
RADIAN-3-MMU_INTR_ERR |
3-Error |
Radian slot/unit [dec]/[dec] MMU ERR INTR: [chars] |
Radian MMU ERROR interrupt occurs |
cmts-platform-infr |
LOG_STD_ACTION |
|
RADIAN-3-PE_INTR_ERR |
3-Error |
Radian slot/unit [dec]/[dec] PE ERR INTR: [chars] |
Radian PreEnqueue ERROR interrupt occurs |
cmts-platform-infr |
LOG_STD_ACTION |
|
RADIAN-3-SCHAN_FAIL |
3-Error |
Radian [dec] SCHAN [chars] fail for [chars] rc = [dec] |
Radian S-Channel read or write operation failure |
cmts-platform-infr |
LOG_STD_SH_TECH_ACTION |
|
RADIAN-3-VLI_ACCESS_ERR |
3-Error |
VLI Err: [chars] |
Radian VLI access error |
cmts-platform-infr |
LOG_STD_ACTION |
|
RADIAN-3-VLI_SWITCHOVER_TIMEOUT |
3-Error |
Haba VLI switchover: wait [chars] timeout |
Haba switchover timeout |
cmts-platform-infr |
LOG_STD_ACTION |
|
RADIAN-5-IL_INTR_MSG |
5-Notice |
Radian slot/unit [dec]/[dec] IL INTR: [chars] |
Radian IL minor ERROR interrupt occurs |
cmts-platform-infr |
LOG_STD_ACTION |
|
RADIAN-5-MMU_INTR_MSG |
5-Notice |
Radian slot/unit [dec]/[dec] MMU INTR: [chars] |
Radian MMU minor ERROR interrupt occurs |
cmts-platform-infr |
LOG_STD_ACTION |
|
RADIAN-5-PD0_INTR_MSG |
5-Notice |
Radian slot/unit [dec]/[dec] PD0 INTR: [chars] |
Radian PostDequeue minor ERROR0 interrupt occurs |
cmts-platform-infr |
LOG_STD_ACTION |
|
RADIAN-5-PD1_INTR_MSG |
5-Notice |
Radian slot/unit [dec]/[dec] PD1 INTR: [chars] |
Radian PostDequeue minor ERROR1 interrupt occurs |
cmts-platform-infr |
LOG_STD_ACTION |
|
RADIAN-5-PE_INTR_MSG |
5-Notice |
Radian slot/unit [dec]/[dec] PE INTR: [chars] |
Radian PE minor ERROR interrupt occurs |
cmts-platform-infr |
LOG_STD_ACTION |
|
RADIAN-5-VLI_SWITCHOVER_MSG |
5-Notice |
Haba VLI switchover: [chars] in [dec]ms |
Haba switchover message |
cmts-platform-infr |
LOG_STD_ACTION |
|
RADIAN-5-XLPORT_INTR_MSG |
5-Notice |
Radian slot/unit [dec]/[dec] XLPORT INTR: [chars] |
Radian XLPORT minor ERROR interrupt occurs |
cmts-platform-infr |
LOG_STD_ACTION |
|
RADIO-2-RF_OVERTEMP |
2-Critical |
Radio[dec]/0 ODU [dec]: over temperature [chars] |
Most likely cause is hardware failure or solar heating |
ubr-radiop2p-hw |
"Keep the RF ODU cool" |
|
RADIO-3-SELF_TEST_FAILED |
3-Error |
Radio[dec]/0 failed self-test |
Most likely a hardware failure |
ubr-radiop2p-hw |
"Call tech support" |
|
RADIO-4-BAD_IF_PIC |
4-Warning |
Radio[dec]/0 bad IF PIC version [dec] on IDU |
Most likely a hardware configuration oversite |
ubr-radiop2p-hw |
"Call tech support" |
|
RADIO-4-BAD_RF_PIC |
4-Warning |
Radio[dec]/0 bad RF PIC version [dec] on ODU [dec] |
Most likely a hardware configuration oversite |
ubr-radiop2p-hw |
"Call tech support" |
|
RADIO-4-CHECKSUM_ERR |
4-Warning |
Radio[dec]/0 radio phy eeprom \[chars]\ checksum stored:0x%02x calculated:0x%02x |
Most likely cause is Shut or No Shut command |
ubr7200 |
"Enter the No Shut command" |
|
RADIO-4-DSPHPITIMEOUT |
4-Warning |
Radio[dec]/0 HPI timeout while attempting to access DSP \[chars]\ |
A DSP on the RADIO line card was not granting access to its memory. Most likely cause is a DSP firmware internal error. |
ubr7200 |
LOG_STD_ACTION |
|
RADIO-4-DSPINDERR |
4-Warning |
Radio[dec]/0 Error processing indication from DSP \[chars]\ [chars]:[dec] |
A DSP on the RADIO line card generated an indication message that could not be processed. This can happen when the router is operating under severe traffic load. |
ubr7200 |
LOG_STD_ACTION |
|
RADIO-4-DSPSPURRESP |
4-Warning |
Radio[dec]/0 spurious DSP response from \[chars]\: %08x %08x %08x %08x %08x %08x %08x %08x |
A DSP on the RADIO line card generated a response message unexpectedly. This can happen when the router is operating under severe traffic load. |
ubr7200 |
LOG_STD_ACTION |
|
RADIO-4-DSPULOFLOW |
4-Warning |
Radio[dec]/0 uplink message queue overflow reported by DSP \[chars]\ |
At least one DSP-to-router message was lost due to that DSP's uplink queue being full. This can happen when many thresholds/histograms/timelines are being triggered or expiring at the same time. |
ubr7200 |
"Change thresholds and/or reduce histogram/timeline usage to lower the load on the system" |
|
RADIO-4-FPGADONEPINLOW |
4-Warning |
Radio[dec]/0 DONE pin on FPGA \[chars]\ did not assert after downloading |
The DONE pin of a FPGA device on the RADIO line card did not assert after the downloading of the device. This probably indicates an existing or developing hardware failure. |
ubr7200 |
LOG_STD_ACTION |
|
RADIO-4-FPGAINITPINHIGH |
4-Warning |
Radio[dec]/0 INIT pin on FPGA \[chars]\ asserted during downloading |
The INIT pin of a FPGA device on the RADIO line card asserted midway through the downloading of the device. Most likely cause is corrupted FPGA image. |
ubr7200 |
LOG_STD_ACTION |
|
RADIO-4-FPGAINITPINLOW |
4-Warning |
Radio[dec]/0 INIT pin on FPGA \[chars]\ not asserted when PROG pin asserted |
The INIT pin of a FPGA device on the RADIO line card did not assert when the PROG pin was asserted. This indicates either a faulty FPGA device or software problem resetting it. |
ubr7200 |
LOG_STD_ACTION |
|
RADIO-4-IF_COMM |
4-Warning |
Radio[dec]/0 IDU IF internal serial communication error - [chars] |
Most likely cause is a loose IF baby board |
ubr-radiop2p-hw |
"Replace hardware" |
|
RADIO-4-IF_OSC |
4-Warning |
Radio[dec]/0 Internal [chars] Oscillator out of Lock [chars] |
Most likely cause is vibration or hardware failure |
ubr-radiop2p-hw |
"Replace internal card" |
|
RADIO-4-NEWER_IF_EEPROM |
4-Warning |
Radio[dec]/0 Unsupported IF PIC major eeprom version [dec] on IDU |
IOS should be upgraded to support the new eeprom |
ubr-radiop2p-sw |
LOG_STD_ACTION |
|
RADIO-4-NEWER_RF_EEPROM |
4-Warning |
Radio[dec]/0 Unsupported RF PIC major eeprom version [dec] on ODU [dec] |
LOG_STD_ACTION |
ubr-radiop2p-sw |
"Call tech support - upgrade IOS" |
|
RADIO-4-NO_HWCAP_FIELD |
4-Warning |
Radio[dec]/0 could not find HW Capabilities field in IDPROM |
Most likely cause is an improperly-programmed IDPROM |
ubr7200 |
"Have the IDPROM on the linecard reprogrammed" |
|
RADIO-4-NO_IMAGE |
4-Warning |
[chars][dec]/[dec] Chip \[chars]\: failed to find image given current configuration |
Most likely configured to use external files |
ubr-radiop2p-sw |
"Change configuration to use internal files" |
|
RADIO-4-PHY_REQ |
4-Warning |
Radio[dec]/0 link synchronization [chars]. |
Most likely cause loose ODU cable |
ubr7200 |
"Check all cables" |
|
RADIO-4-PHY_SYNC_FAIL |
4-Warning |
Radio[dec]/0 link synchronization [chars]. |
Most likely cause loose ODU cable |
ubr7200 |
"Check all cables" |
|
RADIO-4-PHY_SYNC_OK |
4-Warning |
Radio[dec]/0 link synchronization acquired. |
Most likely cause is No Shut command |
ubr7200 |
"None" |
|
RADIO-4-PHY_SYNC_REOK |
4-Warning |
Radio[dec]/0 link synchronization re-acquired. |
Most likely cause is No Shut command on remote end |
ubr7200 |
"None" |
|
RADIO-4-RF_AGC |
4-Warning |
Radio[dec]/0 ODU [dec] max transmitter power exceeded [chars] |
Most likely cause is hardware failure |
ubr-radiop2p-hw |
"Replace RF ODU" |
|
RADIO-4-RF_ANTENNA |
4-Warning |
Radio[dec]/0 ODU [dec] is [chars] |
Most likely cause is a disconnected cable |
ubr-radiop2p-hw |
"Check or replace cable from UBR to the Out Door Unit" |
|
RADIO-4-RF_COMM |
4-Warning |
Radio[dec]/0 ODU [dec] serial communication error - [chars] |
Most likely cause is a disconnected cable |
ubr-radiop2p-hw |
"Check or replace cable from UBR to the Out Door Unit" |
|
RADIO-4-RF_OSC |
4-Warning |
Radio[dec]/0 ODU [dec] [chars] Oscillator out of Lock [chars] |
Most likely cause is vibration or hardware failure |
ubr-radiop2p-hw |
"Replace electronics on Out Door Unit" |
|
RADIO-4-RF_TEMP |
4-Warning |
Radio[dec]/0 ODU [dec]: temperature is [dec] degrees C threshold is [dec] degrees C |
Most likely cause is hardware failure or solar heating |
ubr-radiop2p-hw |
"Keep the RF ODU cool" |
|
RADIO-4-RF_VOLT |
4-Warning |
Radio[dec]/0 ODU [dec]: supply voltage out of range [chars] |
Most likely cause is hardware failure |
ubr-radiop2p-hw |
"Replace RF ODU" |
|
RADIO-5-CLEAR_METRICS |
5-Notice |
Radio[dec]/0 link metrics cleared |
User requested the link metrics be cleared |
ubr7200 |
"none" |
|
RADIO-5-CONFIG_HW |
5-Notice |
Radio[dec]/0 hardware does not support requested configuration: [chars] |
Most likely cause is incorrect configuration |
ubr-radiop2p-sw |
"Change the configuration to match the hardware" |
|
RADIO-5-CONFIG_MISMAT |
5-Notice |
Radio[dec]/0 invalid or inconsistent configuration requested [chars] |
Most likely cause is the ARQ settings are not supported by the current radio channel parameters |
ubr7200 |
"Change ARQ settings to allowed values given the current radio channel parameters. You can use the radio arq reset command to do this." |
|
RADIO-5-IMAGE_BAD_CRC |
5-Notice |
[chars][dec]/[dec] detected a bad CRC while downloading image \[chars]\ to chip \[chars]\ |
Most likely a protocol error while downloading |
ubr-radiop2p-sw |
- |
|
RADIO-5-IMAGE_TIMEOUT |
5-Notice |
[chars][dec]/[dec] timeout trying to open image \[chars]\ for chip \[chars]\ |
Most likely a protocol error while opening |
ubr-radiop2p-sw |
- |
|
RADIO-5-LOCAL_IN_SYNC |
5-Notice |
Radio[dec]/0 Link synchronization acquired. |
Phy layer successfully acquired link. |
ubr7200 |
"None" |
|
RADIO-5-LOCAL_NO_CW |
5-Notice |
Radio[dec]/0 Still trying to establish link validate codeword. |
Most likely cause remote system is not transmitting on correct frequency |
ubr7200 |
"No Shut remote system" |
|
RADIO-5-LOCAL_NO_FREQ |
5-Notice |
Radio[dec]/0 Still trying to establish link frequency sync. |
Most likely cause remote system is not transmitting on correct frequency |
ubr7200 |
"No Shut remote system" |
|
RADIO-5-LOCAL_NO_SYNC |
5-Notice |
Radio[dec]/0 Still trying to establish link timing sync. |
Most likely cause remote system is not transmitting. |
ubr7200 |
"No Shut remote system" |
|
RADIO-5-LOCAL_NO_TRANSMIT |
5-Notice |
Radio[dec]/0 ODU saftey interlock is preventing transmission. Check ODU and cables. [chars] |
Most likely cause cable not attached ODU overheated |
ubr7200 |
"Check ODU cable" |
|
RADIO-5-LOCAL_NO_VITERBI |
5-Notice |
Radio[dec]/0 Still trying to establish link viterbi sync. |
Most likely cause remote system is not transmitting on correct frequency |
ubr7200 |
"No Shut remote system" |
|
RADIO-5-METRICS_THRESH |
5-Notice |
Radio[dec]/0 [chars] per [chars] threshold met[dec]>=[dec] |
Most likely cause is a mis-aligned antenna |
ubr7200 |
"Re-align the antennas" |
|
RADIO-5-PHY_RETRY |
5-Notice |
Radio[dec]/0 event %23s in state %15s |
Most likely cause incorrect configuration |
ubr7200 |
"Review configuration and hardware capabilities" |
|
RADIO-5-PHY_SYNC_LOST |
5-Notice |
Radio[dec]/0 Lost link. Check remote transmitter. |
Most likely cause remote system is not transmitting. |
ubr7200 |
"No Shut remote system" |
|
RADIO-5-REMOTE_LOST_SYNC |
5-Notice |
Radio[dec]/0 Remote end reports: [chars] |
Most likely cause cable not attached ODU overheated |
ubr7200 |
"Check ODU cables" |
|
RADIO-5-REMOTE_NO_SYNC |
5-Notice |
Radio[dec]/0 Remote end reports: Unable to acquire link synchronization. |
Most likely cause cable not attached ODU overheated |
ubr7200 |
"Check ODU cables" |
|
RADIO-5-THRESHOLD |
5-Notice |
Radio[dec]/0 [chars] [chars] threshold crossed ODU [dec] |
Most likely cause is a user defined threshold |
ubr7200 |
"none" |
|
RADIO-6-IMAGE_NOT_FOUND |
6-Information |
[chars][dec]/[dec] could not find image \[chars]\ for chip \[chars]\ |
Most likely a typo when set the url of the image |
ubr-radiop2p-sw |
"Try again" |
|
RADIO-6-SELF_TEST_SUCCESS |
6-Information |
Radio[dec]/0 self-test successful |
Passed a self-diagnostic |
ubr-radiop2p-hw |
"This is a good thing" |
|
RADIUS-3-ALLDEADSERVER |
3-Error |
Group [chars]: No active radius servers found. Id [dec]. |
This error message occurs when all the servers configured in a server group are found to be unresponsive. |
aaa |
"Check the network connectivity to the RADIUS " "servers and check that the servers are running." |
|
RADIUS-3-BUFFER_OVERFLOW |
3-Error |
Radius I/O buffer has overflowed |
The given server is not on the global public servers list. This is an internal consistency error |
aaa |
LOG_STD_ACTION |
|
RADIUS-3-CANNOT_OPEN_SOCKET |
3-Error |
Cannot open UDP socket for service [chars] |
The router is unable to open a socket for UDP communications by the indicated service. Most of the time another service might be using the same port. |
aaa |
"Check your configuration to make sure that no " "other services are using the same port. " "If not able to debug the issue enter <CmdBold>show " "running-config<NoCmdBold> and contact your technical " "support representative for assistance." |
|
RADIUS-3-CORRUPTCONTEXT |
3-Error |
Bad Magic pattern in [chars]:0x[hec] magic:0x[hec]! |
The magic pattern imprinted on the internal hash table data structures in RADIUS subsystem is missing and indicates memory corruption. The memory is getting overwritten by a misbehaving process. The traceback and the process information is generated to the result of the error. |
aaa |
"Check bug toolkit on Cisco web-site to look for a " "bug that has symptoms similar to the one occured. " "If there is no entry for the problem you faced " "collect the system message text exactly as it " "appears on the console or in the system log. " "Enter <CmdBold>show tech-support<NoCmdBold> " "command contact your technical support " "representative and provide the representative " "with the gathered information." |
|
RADIUS-3-DATAERROR |
3-Error |
Warning: [chars] |
The given data passed into the Radius subsystem is considered invalid and may result in loss of attributes. |
aaa |
"Please collect traceback and contact your technical " "support representative." |
|
RADIUS-3-FORKFAIL |
3-Error |
Failed to fork process for [chars]. |
Quite likely we ran out of memory. Other explanations are possible. |
aaa |
"If this message recurs enter <CmdBold>show " "tech-support<NoCmdBold> command and call your " "technical support representative for assistance." |
|
RADIUS-3-FORMATLONG |
3-Error |
Format string too long.Maximum allowed length is [dec]. |
The user is attempting to configure a format string with a prefix that is too long. |
aaa |
"Enter a shorter string to configure." |
|
RADIUS-3-IDENTFAIL |
3-Error |
Saving of unique accounting ident aborted. Configuration has been modified. |
The configuration has been modified. We can not save the unique accounting IDENT to nvram. The message is to inform the user that the saving of unique accounting ident is aborted due to the change in configuration. |
aaa |
"Save the configuration and try again. If the error persists " "Enter <CmdBold>show tech-support<NoCmdBold> contact your Cisco " "technical support representative and provide the representative " "with the gathered information for assistance." |
|
RADIUS-3-INVALID_PACKET |
3-Error |
Invalid packet posted to RADIUS. |
Radius not able to process a packet as it in invalid |
aaa |
LOG_STD_NO_ACTION |
|
RADIUS-3-INVALIDFORMAT |
3-Error |
Invalid Nas Port Format: [chars] [chars] |
The user is attempting to configure an incorrect format string. |
aaa |
"Enter a 32 character string using supported " "characters only." |
|
RADIUS-3-IPV4_FIB_SEND_FAILED |
3-Error |
Radius ipv4 send failed due to FIB error. Error code: [dec]. |
Radius not able to send udp packets as fib failed |
aaa |
LOG_STD_NO_ACTION |
|
RADIUS-3-MALLOC_FAILED |
3-Error |
Insufficient memory : [chars]. |
Memory allocation failed due to insufficient memory |
aaa |
LOG_STD_NO_ACTION |
|
RADIUS-3-NOACCOUNTINGRESPONSE |
3-Error |
Accounting message [chars] for session %*s failed to receive Accounting Response. |
Maximum number of retransmissions is exceeded. The network is not accessible or the RADIUS server is down. |
aaa |
"Check the network connectivity to the RADIUS " "servers and check that the servers are running. " "If not able to debug the issue enter <CmdBold>show " "running-config<NoCmdBold> and contact your technical " "support representative for assistance." |
|
RADIUS-3-NOATTRLIST |
3-Error |
No attribute-list passed through parser. |
An internal error has occurred. The reason could be hardware or software. The error appears when no attribute list is passed through the parser. |
aaa |
LOG_STD_ACTION |
|
RADIUS-3-NOHOSTNAME |
3-Error |
Failed to retrieve my hostname. |
Could not find the router's hostname. A hostname needs to be defined since it determines the RADIUS profile we will retrieve. |
aaa |
"Define a hostname on the router's config. " "Refer to the hostname configuration section " "of IOS documentation." |
|
RADIUS-3-NOSERVERS |
3-Error |
No Radius hosts configured or no valid server present in the server group [chars] |
RADIUS is attempting to send a request but there are no hosts configured to which the request is send. |
aaa |
"Configure a host with the 'radius-server' command " "providing the IP address of the server. Refer to " "the radius-server host configuration section of IOS " "documentation." |
|
RADIUS-3-OVERRUN |
3-Error |
Insufficient buffer space [dec] for string value. |
This error occurs due to the insufficient memory allocated to the buffer. The condition could be caused by a software less likely by a hardware. The traceback and process information is generated due to this condition. |
aaa |
"If the error re-occurs check bug toolkit on Cisco web-site " "to look for a bug that has symptoms similar to the " "one occured. If there is no entry for the problem " "you faced collect the system message text exactly " "as it appears on the console or in the system log. " "Enter <CmdBold>show tech-support<NoCmdBold> and contact" "your technical support representative and provide the " "representative with all the information gathered." |
|
RADIUS-3-SECRETDEFINEFAILED |
3-Error |
Key definition ignored. |
The user is attempting to store either a corrupted shared secret or memory allocation failed during secret definition. Any existing shared secret will be preserved. |
aaa |
"Configure a proper secret. Refer to the " "shared secret configuration section for " "RADIUS servers in IOS documentation." |
|
RADIUS-3-SERVERTYPEMISMATCH |
3-Error |
Servers [chars] and [chars] in server group '[chars]' are of different types. |
All the servers in a server group should either be of type standard or non-standard. |
aaa |
"Enter <CmdBold>show running-config<NoCmdBold> " "command and make sure all the RADIUS servers in " "the server group printed above are of the same " "type - either standard or non-standard." |
|
RADIUS-3-SOURCEPORTALLOCERROR |
3-Error |
Warning: Unable to allocate port [dec] |
Unable to allocate a certain port will not have the full range of source ports. This is not supposed to happen contact support. |
aaa |
"Contact support" |
|
RADIUS-3-UNKNOWNAPI |
3-Error |
Unknown API type [dec] |
RADIUS code has been invoked using an unknown API type. This is the result of a bug in the RADIUS subsystem. |
aaa |
"Check bug toolkit on Cisco web-site to look for a " "bug which has symptoms similar to the one occured. " "If there is no entry for the problem you faced " "Please collect traceback and contact your" "technical support representative." |
|
RADIUS-3-ZEROATTRLEN |
3-Error |
Radius attr [dec] len 0 |
An internal error has occurred |
aaa |
LOG_STD_ACTION |
|
RADIUS-4-BADATTRLIST |
4-Warning |
Unable to process attribute list. |
The attribute list is syntactically incorrect. |
aaa |
"Please specify the attribute list as a comma-" "delimited string of integers between 1 and 255." |
|
RADIUS-4-NOATTRLISTDEF |
4-Warning |
Warning: Attribute list [chars] is not defined. |
The given attribute list is not defined. |
aaa |
"Please define the attribute list as soon as " "possible." |
|
RADIUS-4-NOPUBLICSERV |
4-Warning |
Warning: No servers were found in the public server list. |
The given server is not on the global public servers list. This is an internal consistency error. |
aaa |
LOG_STD_ACTION |
|
RADIUS-4-NOSERV |
4-Warning |
Warning: Server [chars]:[dec][dec] is not defined. |
The given server is not globally defined please define it. |
aaa |
"Please define the server. Refer to the" "server configuration section of IOS documentation." |
|
RADIUS-4-NOSERVNAME |
4-Warning |
Warning: Server [chars] is not defined. |
The given server name is not globally defined please define it. |
aaa |
"Please define the server. Refer to the " "new server name configuration section of IOS documentation." |
|
RADIUS-4-RADIUS_ALIVE |
4-Warning |
RADIUS server [chars]:[dec][dec] is being marked alive. |
A RADIUS server that previously was not responding has responded to a new request or the deadtimer has expired. |
aaa |
LOG_STD_NO_ACTION |
|
RADIUS-4-RADIUS_DEAD |
4-Warning |
RADIUS server [chars]:[dec][dec] is not responding. |
The server might not be available to serve request. server has not responded to repeated requests. |
aaa |
"Check for the connectivity to server. " "Check if the RADIUS server is still active. " "If not able to debug the issue enter <CmdBold>show " "running-config<NoCmdBold> and contact your technical " "support representative for assistance." |
|
RADIUS-4-SERVREF |
4-Warning |
Warning: Server [chars]:[dec][dec] is still referenced by server group. |
The server being removed is still referenced by a server group. This message appears when server configuration is removed but in a server group it still exists. |
aaa |
"Please dereference the server from the server group " "as soon as possible. Refer to server group configuration " "section in IOS documentation." |
|
RADIUS-4-SERVREFNAME |
4-Warning |
Warning: Server %S is still referenced by server group. |
The server being removed is still referenced by a server group. This message appears when server configuration is removed but in a server group it still exists. |
aaa |
"Please dereference the server from the " "server group as soon as possible. " "Refer to server group configuration " "section in IOS documentation." |
|
RADIUS-6-GETPOOLS |
6-Information |
Retrieving IP-Pools via user [chars] |
Getting initial IP-Pool definitions from RADIUS using the given user's profile. |
aaa |
"No action required." |
|
RADIUS-6-GETROUTES |
6-Information |
Retrieving static routes in user [chars] |
Getting initial static routes from RADIUS using the given user's profile. |
aaa |
"No action required. The message is " "informatory in nature and tells that it is getting the " "static routes based on user's profile." |
|
RADIUS-6-IDENTSAVE |
6-Information |
Saving config with new acct ident in nvram. |
Saving an accounting ident in nvram. The message is informatory. |
aaa |
"No action required." |
|
RADIUS-6-RESETDEADSERVER |
6-Information |
Group [chars]: Marked alive as Radius server [chars]:[dec][dec] configured. |
RADIUS server is now configured in the server group which was previously marked dead. |
aaa |
"No action required. The message is informatory" "in nature and tells that the dead server is now" "configured and up." |
|
RADIUS-6-SERVERALIVE |
6-Information |
Group [chars]: Radius server [chars]:[dec][dec] is responding again previously dead. |
A RADIUS server which previously was dead has started responding again. |
aaa |
"No action required. This message is " "informatory in nature and tells that the server " "has come up and running." |
|
RADIX-2-INIT |
2-Critical |
No memory for radix initialization: [chars] |
The system ran out of memory during initialization. This should only\n\ occur if an image is too large for the existing dynamic memory. |
mem |
"Use a smaller subset image or upgrade hardware." |
|
RADIX-3-ADDMASK |
3-Error |
Error adding mask entry [chars] |
A software or hardware error occurred. |
Obtain from traceback decode |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
RADIX-3-BADTREE |
3-Error |
Invalid pointer to head of tree 0x[hec] |
A software programming error occurred. |
Obtain from traceback decode |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
RADIX-3-DELETE |
3-Error |
Error deleting trie entry [chars] |
A software programming error occurred. |
Obtain from traceback decode |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
RADIX-3-NOMEMORY |
3-Error |
No memory available [chars] |
The system is out of memory. |
mem |
"Try one of these actions to correct the problem:\n\\n\ Reduce the number of routes accepted by this router.\n\\n\ Upgrade hardware.\n\\n\ Use a smaller subset image on run-from-RAM platforms." |
|
RADIX-4-ORPHAN |
4-Warning |
Orphaned mask [hex] refcount=[dec] at [hex] next=[hex] |
A software error occurred. |
Obtain from traceback decode |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
RADIXTREE-3-LCON |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
RADPROXY-3-INIT |
3-Error |
Initialisation failure [chars] |
An internal error occurred during RP initialisation. |
aaa-protocol |
LOG_STD_ACTION |
|
RADPROXY-3-INVALID_FSM_EVENT |
3-Error |
Received invalid RP event [chars] in state [chars] |
An internal RP error occurred. |
aaa-protocol |
LOG_STD_ACTION |
|
RADPROXY-3-INVALID_FSM_STATE |
3-Error |
Encountered an invalid RP state [dec] in [chars] |
An internal RP error occurred. |
aaa-protocol |
LOG_STD_ACTION |
|
RADPROXY-3-INVALID_MAC |
3-Error |
Received invalid MAC [chars] in [chars] from [inet] with NAS-IP [inet] |
Error occurred on receiving a invalid MAC |
aaa-protocol |
LOG_STD_ACTION |
|
RADPROXY-3-MEMORY_CORRUPT |
3-Error |
RP Memory magic corrupted |
RP memory magic corrupted |
aaa-protocol |
LOG_STD_ACTION |
|
RADPROXY-3-MEMORY_LOW |
3-Error |
Memory low in RP terminating session |
System memory is running low. |
aaa-protocol |
LOG_STD_ACTION |
|
RADPROXY-3-NULL_FSM_CONTEXT |
3-Error |
Encountered a NULL RP context in [chars] |
Encountered a NULL context in RP. |
aaa-protocol |
LOG_STD_ACTION |
|
RADPROXY-3-PROTOCOL_VIOLATION |
3-Error |
RP encountered fatal protocol violation |
Unrecoverable protocol error |
aaa-protocol |
LOG_STD_ACTION |
|
RAI-1-INITSYS |
1-Alert |
[chars] |
The specific message text is supplied by the RAI Subsystem. This indicates an initialization failure. When this occurs RAI is not operational. |
voice-sip |
LOG_STD_ACTION |
|
RAVEN-3-FATAL_ERP_ERROR |
3-Error |
erp_mst_cfg 0x[hec] erp_mst_err_phase 0x[hec] erp_mst_err_addr 0x[hec] |
Fatal Raven ERP interrupt |
cmts-platform |
"Copy the error message exactly as it appears and report it to your" " technical support" |
|
RAVEN-3-FATAL_LCL_BUS_ERROR |
3-Error |
cap_reg 0x[hec] cap_data 0x[hec] cap_access 0x[hec] [chars] transaction |
Fatal Unrecoverable Local Bus error |
cmts-platform |
"Copy the error message exactly as it appears and report it to your" " technical support" |
|
RAVEN-3-FATAL_REC_LCL_BUS_ERROR |
3-Error |
cap_reg 0x[hec] cap_data 0x[hec] cap_access 0x[hec] [chars] transaction |
Fatal Recoverable Local Bus error |
cmts-platform |
"Copy the error message exactly as it appears and report it to your" " technical support" |
|
RAVEN-3-FATAL_REC_RLDRAM_ECC_ERROR |
3-Error |
err_rec_addr 0x[hec] err_rec_data3 0x[hec] err_rec_data2 0x[hec]\n err_rec_data1 0x[hec] err_rec_data0 0x[hec] err_rec_ecc 0x[hec] |
High Priority Raven Single Error Upset interrupt |
cmts-platform |
"Copy the error message exactly as it appears and report it to your" " technical support" |
|
RAVEN-3-PLL_UNEXPECTED_UNLOCK_EVENT |
3-Error |
[chars] unlock |
Low Priority Raven interrupt |
cmts-platform |
"Copy the error message exactly as it appears and report it to your" " technical support" |
|
RAVEN-4-TSS_LOAD_EVENT |
4-Warning |
[chars] event |
RLDRAM interrupt |
cmts-platform |
"Copy the error message exactly as it appears and report it to your" " technical support" |
|
RAVEN-4-TSS_MISMATCH_EVENT |
4-Warning |
[chars] event |
TSS Mismatch interrupt |
cmts-platform |
"Copy the error message exactly as it appears and report it to your" " technical support" |
|
RAVEN-4-TSS_PARITY_EVENT |
4-Warning |
[chars] event |
TSS Parity interrupt |
cmts-platform |
"Copy the error message exactly as it appears and report it to your" " technical support" |
|
RAVEN-5-PLL_NONFATAL_UNLOCK_EVENT |
5-Notice |
[chars] unlock |
Expected PLL unlock |
cmts-platform |
"If this event appears after/close to TCC reload it is expected." "Otherwise copy the error message exactly as it appears and report" " it to your technical support" |
|
RAWSOCKET-3-CLIENT_CONNECTED |
3-Error |
raw-socket tcp client [chars]/[dec] connected on tty [chars] |
- |
wolfeisland-sw |
"This is an informational message only. It occurs\n\ in no shut operation" |
|
RAWSOCKET-3-CLIENT_DISCONNECTED |
3-Error |
raw-socket tcp client [chars]/[dec] disconnected on tty [chars] |
- |
wolfeisland-sw |
"This is an informational message only. It occurs\n\ in shut operation" |
|
RAWSOCKET-3-FPGA_FAIL |
3-Error |
tty [dec] : Failed to set [chars] in FPGA |
The software failed to configure FPGA for serialim\n\ it could be a temporary condition. |
wolfeisland-sw |
"Retry CLI command" LOG_STD_ACTION |
|
RAWSOCKET-3-INIT_FAIL |
3-Error |
Rawsocket failed to start a process |
Rawsocket failed to start a process. |
wolfeisland-sw |
LOG_STD_ACTION |
|
RAWSOCKET-3-MALLOC_FAIL |
3-Error |
Rawsocket malloc error for tty line data structure |
Rawsocket failed to allocate memory for tty line. |
wolfeisland-sw |
LOG_STD_ACTION |
|
RAWSOCKET-3-NULL_IDB |
3-Error |
NULL hardware IDB |
An internal software error occured. \n\ It could be a temporary condition. |
wolfeisland-sw |
"Log DDTS if condition is persistent" LOG_STD_ACTION |
|
RAWSOCKET-3-NULL_INPUT |
3-Error |
NULL Inputs |
An internal software error occured. \n\ It could be a temporary condition. |
wolfeisland-sw |
"Log DDTS if condition is persistent" LOG_STD_ACTION |
|
RAWSOCKET-3-NULL_TTY |
3-Error |
NULL tty line |
An internal software error occured. \n\ It could be a temporary condition. |
wolfeisland-sw |
"Log DDTS if condition is persistent" LOG_STD_ACTION |
|
RAWSOCKET-6-CLIENT_REMOVED |
6-Information |
tty [dec] : raw-socket tcp clients removed |
- |
wolfeisland-sw |
"This is an informational message only. It occurs\n\ in normal operation" |
|
RAWSOCKET-6-SERVER_REMOVED |
6-Information |
tty [dec] : raw-socket tcp server removed |
The raw-socket tcp server is removed when \n\ certain configuration changed. |
wolfeisland-sw |
"This is an informational message only. It occurs\n\ in normal operation" |
|
RBM-0-RBM_EMERG |
0-Emergency |
[chars] |
RBM_INTERNAL_ERROR |
RBM_DDTS_COMPONENT |
LOG_STD_ACTION |
|
RBM-1-RBM_ALERT |
1-Alert |
[chars] |
RBM_INTERNAL_ERROR |
RBM_DDTS_COMPONENT |
LOG_STD_ACTION |
|
RBM-2-RBM_CRIT |
2-Critical |
[chars] |
RBM_INTERNAL_ERROR |
RBM_DDTS_COMPONENT |
LOG_STD_ACTION |
|
RBM-3-RBM_ERR |
3-Error |
[chars] |
RBM_INTERNAL_ERROR |
RBM_DDTS_COMPONENT |
LOG_STD_ACTION |
|
RBM-3-RBM_PARSE_ACE |
3-Error |
Could not parse command for adding ACE '[chars]' to [chars] Role-Based Access List '[chars]' |
An error occured while attempting to add an ACE to a Role-Based Access List. The ACE syntax is most likely incompatible with the type of RBACL. |
RBM_DDTS_COMPONENT |
"Verify the syntax of the ACEs of the RBACL in ACS and the IP protocol versions the RBACL" " applies to." " RBACL ACE syntax could be verified by manually configuring IP/IPv6 RBACL on the system" " within config-rb-acl/config-ipv6rb-acl configuration mode respectively." |
|
RBM-3-RBM_PARSE_CMD |
3-Error |
Could not parse command. See command output and errors below \n[chars] |
An error occured while attempting to parse command. Look for command output and parser errors below this message. |
RBM_DDTS_COMPONENT |
"Follow the recommended action of the additional error messages that follow this message". |
|
RBM-3-RBM_PARSE_RBACL |
3-Error |
Could not parse command for creating [chars] Role-Based Access List '[chars]'\n\t'[chars]' |
An error occured while attempting to create Role-Based Access List |
RBM_DDTS_COMPONENT |
"This error could occur when TrustSec attempts to install RBACL it has acquired from ACS" " while configuration mode is locked exclusively. TrustSec will retry this operation and" " should eventually succeed once configuration mode is no longer locked. If the error occurs" " when the configuration mode is not locked or if the RBACL does not get installed after" " the configuration mode lock is released "LOG_STD_ACTION |
|
RBM-4-RBM_WARNING |
4-Warning |
[chars] |
RBM_INTERNAL_ERROR |
RBM_DDTS_COMPONENT |
LOG_STD_ACTION |
|
RBM-5-RBM_NOTICE |
5-Notice |
[chars] |
Normal but significant conditions |
RBM_DDTS_COMPONENT |
LOG_STD_ACTION |
|
RBM-6-RBM_INFO |
6-Information |
[chars] |
Informational messages |
RBM_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
RBM-6-SGACLHIT |
6-Information |
ingress_interface='[chars]' sgacl_name='[chars]' action='[chars]' protocol='[chars]' src-vrf='[chars]' src-ip='[inet]' src-port='[dec]' dest-vrf='[chars]' dest-ip='[inet]' dest-port='[dec]' sgt='[dec]' dgt='[dec]' logging_interval_hits='% PRIu64 ' |
A packet matching the log criteria for the given sg access list was \ detected. |
- |
LOG_STD_NO_ACTION |
|
RBM-6-SGACLHIT_V6 |
6-Information |
ingress_interface='[chars]' sgacl_name='[chars]' action='[chars]' protocol='[chars]' src-vrf='[chars]' src-ip='%P' src-port='[dec]' dest-vrf='[chars]' dest-ip='%P' dest-port='[dec]' sgt='[dec]' dgt='[dec]' logging_interval_hits='% PRIu64 ' |
A IPv6 packet matching the log criteria for the given sg access list \ was detected. |
- |
LOG_STD_NO_ACTION |
|
RBM-7-RBM_ASSERT |
7-Debug |
Assertion Failure [chars] @[chars]:[dec] : [chars] |
RBM_INTERNAL_PUBLIC_ERROR |
RBM_DDTS_COMPONENT |
LOG_STD_ACTION |
|
RCMD_ALG-3-CHUNK_CREATE_FAIL |
3-Error |
- |
Chunk create failed. RCMD ALG will not be able to finish initialization. |
cpp-ucode |
LOG_STD_ACTION |
|
RCMD_ALG-3-INCOMPATIBLE_HA_MSG_LEN |
3-Error |
rcvd:[hec] expect:[hec] |
Incompatible HA Message Length. RCMD ALG will reject sync data. |
cpp-ucode |
LOG_STD_ACTION |
|
RCMD_ALG-3-INCOMPATIBLE_HA_VERSION |
3-Error |
rcvd:[hec] expect:[hec] |
Incompatible HA Version. RCMD ALG will reject sync data. |
cpp-ucode |
LOG_STD_ACTION |
|
RCMD_ALG-3-INCORRECT_HA_MAGIC |
3-Error |
rcvd:[hec] expect:[hec] |
Incorrect HA MAGIC. RCMD ALG will reject sync data. |
cpp-ucode |
LOG_STD_ACTION |
|
RCMD_ALG-3-INVALID_HA_OPCODE |
3-Error |
rcvd:[hec] expect:[hec] |
Invalid HA opcode. RCMD ALG will reject sync data. |
cpp-ucode |
LOG_STD_ACTION |
|
RCMD_ALG-3-L7_DATA_CREATE_ERROR |
3-Error |
- |
Error during L7 data creation. |
cpp-ucode |
LOG_STD_ACTION |
|
RCMD_ALG-3-PKT_MANIP_FAIL |
3-Error |
- |
Packet manipulation failed.Packet will be dropped. |
cpp-ucode |
LOG_STD_ACTION |
|
RCMD-4-RCMDDNSFAIL |
4-Warning |
DNS hostname/ip address mismatch. [chars] unknown to DNS |
The IP address for an incoming rcmd request is not registered with\n\ DNS. |
- |
"Add the IP address to DNS." |
|
RCMD-4-RCPATTEMPTED |
4-Warning |
Remote copy from [chars] at [chars] denied |
An attempt was made to connect to a router through RCP but the router\n\ was not configured as an RCP server. |
- |
"Configure an RCP server." |
|
RCMD-4-RSHATTEMPTED |
4-Warning |
Remote shell from [chars] at [chars] denied |
An attempt was made to connect to a router through rsh but the router\n\ was not configured as an rsh server. |
- |
"Configure an rsh server." |
|
RE-4-COMPILE_FAILED |
4-Warning |
Compile failed on pattern number [dec] - states [dec] - [chars] |
Triggers when RE memory cannot be allocated. |
ids |
"This message indicates that space for the\n\ specified RE cannot be allocated due to memory limitations." |
|
RECONNECT-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
RECOVERY-3-ATOM_HA |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
RED_MODE-3-CAP_REG |
3-Error |
Red Mode cap reg failed: reason [dec] |
The capabilities of the Red Mode ISSU could not be registered. |
ha-red-mode-client |
"show issu capability <arguments>" |
|
RED_MODE-3-CAPENTRY_REG |
3-Error |
Red Mode Cap Entry [dec] for Entity [dec] Registration failed [chars] |
A capability entry could not be registered for the Red Mode ISSU. |
ha-red-mode-client |
"show issu capability entries" |
|
RED_MODE-3-CAPGROUP_REG |
3-Error |
Red Mode Cap Group [dec] for Entity [dec] Registration failed [chars] |
A capability group could not be registered for the Red Mode ISSU. |
ha-red-mode-client |
"show capability groups" |
|
RED_MODE-3-CAPTYPE_REG |
3-Error |
Red Mode Cap Type for Entity [dec] Registration failed [chars] |
A capability type could not be registered for the Red Mode ISSU. |
ha-red-mode-client |
"show issu capability types" |
|
RED_MODE-3-CLIENT_REG |
3-Error |
Red Mode Client [dec] Registration failed [chars] |
The Red Mode ISSU client could not be registered. |
ha-red-mode-client |
"show issu clients" |
|
RED_MODE-3-CLIENT_REG_FAILED |
3-Error |
Red Mode ISSU client [dec] Client registration failed. [chars] |
The Red Mode ISSU client could not be registered during system initialization. |
ha-red-mode-client |
"show issu clients" |
|
RED_MODE-3-DELAYED_REGISTER |
3-Error |
Delayed registration could not be completed succesfully Operand = [dec] |
The delayed registration operation for the RF-proxy clients could not complete successfully. |
ha-red-mode-client |
LOG_STD_ACTION |
|
RED_MODE-3-ENTITY_REG |
3-Error |
Red Mode Entity [dec] Registration failed [chars] |
The Red Mode ISSU entity could not be registered. |
ha-red-mode-client |
"show issu entities" |
|
RED_MODE-3-GET_BUFFER |
3-Error |
Red Mode ISSU session [dec] failed to get buffer |
Red Mode ISSU failed to get a buffer |
ha-red-mode-client |
"show issu fsm" |
|
RED_MODE-3-INVALID_RF_DOMAIN |
3-Error |
Invalid RF domain [dec] [ [chars] ] |
Invalid RF domain value |
ha-red-mode-client |
- |
|
RED_MODE-3-IPC_AGENT |
3-Error |
[chars] [ [chars] ] |
Failure in the Red Mode IPC agent |
ha-red-mode-client |
- |
|
RED_MODE-3-ISSU_BASE_CLIENT_INCOMP |
3-Error |
One or more ISSU base clients are incompatible fallback to RPR |
incompatible ISSU base client cause red_mode to fallback to RPR |
- |
"Check the console log for the name and ID of incompatible ISSU BASE " "clients" |
|
RED_MODE-3-ISSU_NEGOTIATION |
3-Error |
[chars] [ [chars] ] |
Failure in the Red Mode Client |
ha-red-mode-client |
- |
|
RED_MODE-3-ISSU_RESET_PEER_IMAGE_COMP |
3-Error |
Failed to reset peer image to be compatible |
Failed to reset peer image to be compatible after standby come back up to RPR |
ha-red-mode-client |
"This message is normally seen in conjunction with an ISSU module error " "message. Please examine the associated ISSU message for the reason for " "failure and action to take." |
|
RED_MODE-3-ISSU_SET_BASE_CLIENT_INCOMP |
3-Error |
Failed to set base client incompatibility |
Failed to set base client incompatibility |
- |
"Check the console log for the name and ID of incompatible ISSU BASE " "clients" |
|
RED_MODE-3-MSG_DATAPTR |
3-Error |
Red Mode Client [dec] get msg dataptr failed. Error = [dec] |
The Red Mode ISSU client could not obtain a message data pointer. |
ha-red-mode-client |
"show issu fsm" |
|
RED_MODE-3-MSG_MTU |
3-Error |
Red Mode Client [dec] get msg mtu failed. Error = [dec] |
The Red Mode ISSU client could not obtain message size. |
ha-red-mode-client |
"show issu fsm" |
|
RED_MODE-3-MSG_REG |
3-Error |
Red Mode msg reg failed: reason [dec] |
Messages for the Red Mode ISSU could not be registered. |
ha-red-mode-client |
"show issu message <arguments>" |
|
RED_MODE-3-MSG_SEND |
3-Error |
Red Mode ISSU client for session [dec] failed to send message. Error Code = [chars] |
The Red Mode ISSU client could not send a negotiation message to a peer. |
ha-red-mode-client |
"show issu fsm" |
|
RED_MODE-3-MSGGROUP_REG |
3-Error |
Red Mode Msg Group [dec] for Entity [dec] Registration failed [chars] |
The message group for the Red Mode ISSU could not be registered. |
ha-red-mode-client |
"show issu message groups" |
|
RED_MODE-3-MSGTYPE_REG |
3-Error |
Red Mode Msg Type for Entity [dec] Registration failed [chars] |
The message type for the Red Mode ISSU could not be registered. |
ha-red-mode-client |
"show issu message types" |
|
RED_MODE-3-NO_DEREGISTER |
3-Error |
Could not deregister plugin for redundancy mode [chars] |
At system initialisation the plugin that describes the capabilities of this redundancy mode could not be deregistered with the redundancy mode client. |
ha-red-mode-client |
LOG_STD_ACTION |
|
RED_MODE-3-NO_REGISTER |
3-Error |
Could not register plugin for redundancy mode [chars] |
At system initialisation the plugin that describes the capabilities of this redundancy mode could not be registered with the redundancy mode client. This redundancy mode may not be available as an option from the parser. |
ha-red-mode-client |
LOG_STD_ACTION |
|
RED_MODE-3-NO_REGISTER_IN_DOMAIN |
3-Error |
Could not register plugin for redundancy mode [chars] in domain [dec] |
At system initialisation the plugin that describes the capabilities of this redundancy mode could not be registered with the redundancy mode client in the given domain. This redundancy mode may not be available as an option from the parser. |
ha-red-mode-client |
LOG_STD_ACTION |
|
RED_MODE-3-RED_MODE_MSG_NOT_OK |
3-Error |
Red Mode ISSU msg type [dec] is not ok |
Red Mode ISSU message type has not negotiated correctly |
ha-red-mode-client |
"show message types <Client_ID>" |
|
RED_MODE-3-RED_MODE_START_NEGO_FAILED |
3-Error |
Red Mode ISSU start nego session failed [chars] |
The Red Mode ISSU could not start its negotiation process. |
ha-red-mode-client |
"show issu fsm" |
|
RED_MODE-3-RED_MODE_XFROM_FAIL |
3-Error |
Red Mode ISSU [chars] transformation failed [chars] |
The transformation operation for the Red Mode ISSU message has failed. |
ha-red-mode-client |
"show issu fsm and show issu sessions" |
|
RED_MODE-3-SELECT_MODE |
3-Error |
The mode change to [dec] was unsuccessful rc = [dec] force = [dec] caller = [dec] |
The specified mode change operation did not complete successfully. |
ha-red-mode-client |
LOG_STD_ACTION |
|
RED_MODE-3-SESSION_REG |
3-Error |
Red Mode session for Entity [dec] Registration failed [chars] |
The Red Mode ISSU session could not be registered. |
ha-red-mode-client |
"show issu sessions" |
|
RED_MODE-3-SESSION_UNREG |
3-Error |
Red Mode session [dec] Un-Registration failed [chars] |
The Red Mode ISSU session could not be unregistered. |
ha-red-mode-client |
"show issu sessions" |
|
RED_MODE-4-NO_MODE_IN_CLI |
4-Warning |
Redundancy mode not defined in configuration. Please add to configuratio\n\n |
The redundancy mode is usually defined at the top of the configuration. Until the redundancy mode is read or the end of the configuration is encountered the system will not allow the peer RSC to continue booting. Therefore if the system has to wait until the end of the configuration to discover that the default redundancy mode should be used then system booting times will be extended by the time taken for the RSC to read its configuration. |
ha-red-mode-client |
"Explicitly write the configuration to NVRAM so that the redundancy mode " "is discovered at an early stage." |
|
RED_MODE-4-PROC_CREATE |
4-Warning |
Red Mode process could not be created |
The red mode process could not be created red mode changes may result in IPC hogs. |
ha-red-mode-client |
LOG_STD_ACTION |
|
RED_MODE-4-RPR_PLUS_DEPRECATION |
4-Warning |
\n *********************************************************\n * Warning The redundancy mode RPR+ is being deprecated *\n * and will be removed in future releases. Please change *\n * mode to SSO: *\n * redundancy *\n * mode sso *\n ********************************************************\n |
RPR+ being deprecated |
ha-red-mode-client |
"Please change mode to SSO" |
|
REDUNDANCY_UTILS-3-INVALID_UNIT_DESIGNATION |
3-Error |
An invalid redundancy designation [chars] has been detected. |
The redundancy utility assigns each system a unit designation of either an Active Unit Standby Unit or Other Unit and this designation was found to be invalid in the run-time module associated with the system traceback message. This condition most likely occurred because of a software error. The message text provides more information on the specific nature of the error. |
rep |
LOG_STD_ACTION |
|
REDUNDANCY-2-IPC |
2-Critical |
[chars] [chars] |
- |
ehsa |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
REDUNDANCY-3-CONFIG_SYNC |
3-Error |
[chars] |
A REDUNDANCY config sync error occurred. The details about\n\ what was attempted and what went wrong will be printed. |
ehsa |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
REDUNDANCY-3-EHSAISSU |
3-Error |
[chars] failed with error code [ [chars] ] |
An ISSU related REDUNDANCY error occurred. The details about\n\ what was attempted and what went wrong will be printed. |
ehsa |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
REDUNDANCY-3-FSM |
3-Error |
[chars] |
- |
ehsa |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
REDUNDANCY-3-FSM_ERROR |
3-Error |
[chars] Error Code: [dec] |
- |
ehsa |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
REDUNDANCY-3-GENERAL |
3-Error |
[chars] |
A REDUNDANCY error occurred. The details about\n\ what was attempted and what went wrong will be printed. |
ehsa |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
REDUNDANCY-3-MEMORY_DIFF |
3-Error |
WARNING nonsymetrical configuration:\n Active has [dec]K Standby has [dec]K\n |
The redundant RPs have different memory configurations. |
ehsa |
"The configuation is allowed but discouraged." |
|
REDUNDANCY-3-PEER_MONITOR |
3-Error |
[chars] |
A REDUNDANCY Peer Monitor error occurred. The details about\n\ what was attempted and what went wrong will be printed. |
ehsa |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
REDUNDANCY-3-REDUNDANCY_ALARMS |
3-Error |
[chars] |
A REDUNDANCY Alarm assertions error occurred. The details about\n\ what was attempted and what went wrong will be printed. |
ehsa |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
REDUNDANCY-3-STANDBY_LOST |
3-Error |
Standby processor fault [chars] |
The standby processor is no longer available. |
ehsa |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
REDUNDANCY-3-SWITCHOVER |
3-Error |
RP switchover [chars] |
A REDUNDANCY switchover has occurred. |
ehsa |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
REDUNDANCY-4-PEER_DID_NOT_RESPOND |
4-Warning |
Resetting peer [chars] because it did not respond to verification of HA role. |
The Standby peer has reloaded itself to correct a configuration mismatch between the Active and the Standby. The Standby has detected that it is missing configuration for a line card. This has most likely happened because the Standby was reloaded prior to the new card being inserted. |
ehsa |
LOG_STD_NO_ACTION |
|
REDUNDANCY-4-RELOADING_STANDBY |
4-Warning |
Reloading the Standby [chars] |
The Active has sent a reload IPC request to the Standby peer. If the reload is not successful then the Standby will be power cycled instead. |
ehsa |
LOG_STD_ACTION |
|
REDUNDANCY-5-PEER_MONITOR_EVENT |
5-Notice |
[chars] [chars][chars][dec]\n |
A REDUNDANCY Peer Monitor event occurred and reported. The report should\n\ help to find out the reason for a switch-over. |
ehsa |
"Copy the error message exactly as it appears. Copy down the system's\n\ configuration along with any other relevant information. Contact your\n\ technical support representative for assistance." |
|
REDUNDANCY-5-XCONNECT |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
REDUNDANCY-6-SWITCHOVERTIME |
6-Information |
Time taken to switchover = [dec] milliseconds |
This is how long the Standby peer took to become Active after a failure of the existing Active. |
ehsa |
LOG_STD_NO_ACTION |
|
REG_COMP-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
REG_FAIL-2-MPLS_TE_EXT_FWDG |
2-Critical |
ERRMSG_NOFLAGS |
- |
- |
- |
|
REGISTRATION_FAIL-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
REGISTRY-2-REG_FLAG_DEADLOCK |
2-Critical |
Registry call to [chars] timed out due to deadlock |
- |
remote-registry |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
REGISTRY-2-REG_PARSE_ERROR |
2-Critical |
[chars]: Could not parse notification [chars] : error/no. of items = [dec] |
- |
remote-registry |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
REGISTRY-3-FASTCASE_OUT_OF_BOUNDS |
3-Error |
Attempt made in [chars] to register with out of bounds key. |
In FASTCASE registry the key has to be smaller than the size specified when the registry was created. This message indicates that an attempt was made to register with a key out of bounds. |
- |
"Copy the error message exactly as it appears and report it " "to your technical support representative." |
|
REGISTRY-3-LCON |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
REGISTRY-3-REG_FLAG_ERR |
3-Error |
Invalid combination of registry flag and scheduler control : [chars] |
When process blocking has been disabled either using\n\ raise_interrupt_level or assign_blocking_disabled a remote registry\n\ with flags REG_FLAG_DATA_SAFE/REG_FLAG_PEER has been invoked. |
remote-registry |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
REGISTRY-3-REG_SUSPEND |
3-Error |
Registry of type SUSPEND called when suspends are not allowed. |
When process blocking has been disabled either using\n\ raise_interrupt_level or assign_blocking_disabled\n\ a remote registry of type SUSPEND has been invoked. |
remote-registry |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
REGISTRY-3-REG_XDR |
3-Error |
[chars] |
There was an error while marshalling a parameter to a remote\n\ inter-process registry call |
remote-registry |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
REGISTRY-3-SEQ_LIST_OVERWRITE |
3-Error |
Attempt made to overwrite a set sequence function [chars] |
A single function can be set as a callback for a specified \n\ sequence number for a sequenced list registry. \n\ This message indicates that an attempt to set a new callback has \n\ failed because a callback function has already been set for this \n\ sequence number. |
- |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
REGISTRY-3-STUB_CHK_OVERWRITE |
3-Error |
Attempt made to overwrite a set stub function in [chars]. |
A single function can be set as a callback for when a stub w/ check\n\ registry is invoked. This message indicates that an attempt to\n\ set a new callback has failed because a callback function\n\ has already been set. |
- |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
REMIF-3-BADCMD |
3-Error |
[dec] from [inet] |
- |
- |
"" |
|
REMIF-3-CLOSED |
3-Error |
[chars] has released [chars] |
- |
- |
"" |
|
REMIF-3-DUPOPEN |
3-Error |
[chars] is already open by [chars] |
- |
- |
"" |
|
REMIF-3-IFNONE |
3-Error |
[chars] does not exist. Requested by [chars] |
- |
- |
"" |
|
REMIF-3-INITSYS |
3-Error |
[chars] |
Failed to create remif_udp_process |
- |
"" |
|
REMIF-3-IQUEUE |
3-Error |
input on [chars] |
- |
- |
"" |
|
REMIF-3-NOMEM |
3-Error |
No available memory for [chars] |
- |
- |
"" |
|
REMIF-3-NOSOCKET |
3-Error |
Unable to open UDP input socket |
The requested operation could not be accomplished because of a possible low memory condition. |
- |
- |
|
REMIF-3-OPEN |
3-Error |
[chars] now owns [chars] |
- |
- |
"" |
|
REMIF-3-OQUEUE |
3-Error |
output on [chars] |
- |
- |
"" |
|
REMIF-3-TCPERR |
3-Error |
TCP error status [dec] |
- |
- |
"" |
|
REMOTE_TTY-2-NOMEM |
2-Critical |
Malloc failure for remote-tty [chars] data-structure |
Unable to allocate memory for remote-tty data-structure.\n\ Remote-tty component will not be able to function properly. |
remote-tty |
"show memory summary" |
|
REMOVE_FAIL-4-MPLS_TE_AUTO_TUN |
4-Warning |
ERRMSG_NOFLAGS |
- |
- |
- |
|
REP_ISSU-3-BUFFER |
3-Error |
REP ISSU client failed to get buffer for message error [dec] |
REP ISSU client failed to get buffer for building a negotiation message. Hence it can send the negotiation message to the standby unit. When there is a problem in the negotiation the standby unit can not be brought up. |
rep |
"show logging and show checkpoint client" |
|
REP_ISSU-3-CAPABILITY |
3-Error |
REP ISSU client [chars] |
REP ISSU client observed an error during capability negotiation. When this error happens there is a mismatch between the client capability between the active and standby unit. |
rep |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
REP_ISSU-3-INIT |
3-Error |
REP ISSU client initialization failed at [chars] error [chars] |
REP ISSU client could not be initiailzed this will cause catastrophic failure when ISSU upgrade or downgrade is performed. |
rep |
LOG_STD_SH_TECH_ACTION |
|
REP_ISSU-3-MSG_NOT_OK |
3-Error |
REP ISSU client message [dec] is not compatible |
REP ISSU client received an incompatible message from the peer unit. Since the message is not compatible it can be processed by this unit |
rep |
"show issu message group <client_id> and" "show issu session <client_id> and" "show issu negotiated version <session_id>" |
|
REP_ISSU-3-MSG_SIZE |
3-Error |
REP ISSU client failed to get the message size for message [dec] |
REP ISSU client failed to calculate message size for the message specified. The REP ISSU client will not be able to send message to the standby unit. |
rep |
"show issu message group <client_id> and" "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
REP_ISSU-3-POLICY |
3-Error |
REP ISSU client message type [dec] is [chars] |
REP ISSU client received an message type which it does not support. The policy is applied to make the session compatible. |
rep |
"show issu session <client_id>" |
|
REP_ISSU-3-SEND_FAILED |
3-Error |
REP ISSU client failed to send a negotiation message error [dec] |
REP ISSU client could not send a session negotiation message to the peer. When there is a problem in the negotiation the standby unit can not be brought up. |
rep |
"show logging and show checkpoint client" |
|
REP_ISSU-3-SESSION |
3-Error |
REP ISSU client [chars] |
REP ISSU client observed an error during a session negotiation with the peer unit. When there is a problem with the session the standby unit can not be brought up. |
rep |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
REP_ISSU-3-SESSION_UNREGISTRY |
3-Error |
REP ISSU client failed to unregister session information. Error: [dec] [chars] |
The REP ISSU client failed to unregister session information. |
rep |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
REP_ISSU-3-TRANSFORM |
3-Error |
REP ISSU client [chars] transform failed error [chars] |
REP ISSU client could not transform the message. If the transmit transformation failed it means that the checkpoint message can not be sent to the standby unit. If the receive transformation failed it means that the checkpoint message can not be applied on the standby unit. In both cases the Port Manager state will not be identical with the active unit. |
rep |
"show issu session <client_id> and" "show issu negotiated version <session_id>" |
|
REP-3-NOPPPROC |
3-Error |
Failed to create REP LSL Fast Hello Process |
- |
rep |
- |
|
REP-5-EDGEMISCONFIG |
5-Notice |
Invalid topology. More than two edge ports configured for segment [dec] |
- |
rep |
LOG_STD_ACTION |
|
REPLICATE_OCE-3-REPLICATE_PATH_WALK_FAIL |
3-Error |
[chars] [dec] |
LSM Replicated packets may not be forwarded. |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
REPLICATE_OCE-6-PAK_TOO_SHORT |
6-Information |
Packet too short datagram size [dec] tl [dec] |
An IP packet which is too short was received |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
REQGRP-3-DSPTCHQ |
3-Error |
[chars] |
Disptach IPC queue initialization failure. |
ubr10k-sw |
LOG_STD_ACTION |
|
REQGRP-3-ENQFAIL |
3-Error |
enqueue failed! queue:[chars] size:[dec] |
process enqueue failed. |
ubr10k-sw |
LOG_STD_ACTION |
|
REQGRP-3-IPCTXERR |
3-Error |
IPC send failure: version=V1 msg=[dec] error=[chars] slot [dec]/[dec] |
- |
- |
- |
|
REQGRP-3-NBLKENQFAIL |
3-Error |
[chars] slot [dec]/[dec] |
- |
- |
- |
|
REQGRP-3-NBLKQ |
3-Error |
[chars] |
Nonblocking IPC queue initialization failure. |
ubr10k-sw |
LOG_STD_ACTION |
|
REQGRP-3-NORESP |
3-Error |
No response generated for IPC request [dec] slot [dec]/[dec]: [chars] |
- |
- |
- |
|
REQGRP-3-NOSESSION |
3-Error |
Unable to create client object for client [dec] entity [dec] slot [dec]/[dec]: [chars] |
- |
- |
- |
|
REQGRP-3-REQOP |
3-Error |
IPC request/response [dec] slot [dec]/[dec]: [chars] |
Operational errors while processing an IPC Request. |
ubr10k-sw |
LOG_STD_ACTION |
|
REQGRP-3-RPCREQ |
3-Error |
RPC blocked message for client [dec] entity [dec] slot[dec]/[dec]: [chars] |
- |
- |
- |
|
REQGRP-3-SYSCALL |
3-Error |
System call for command [dec] slot[dec]/[dec] : [chars] Cause: [chars] |
- |
- |
- |
|
REQGRP-3-UNKCONN |
3-Error |
Unknow connection state [dec] from callback for client [dec] entity [dec] slot [dec]/[dec] |
- |
- |
- |
|
REQGRP-4-IPCWATERMARK |
4-Warning |
The size of request queue for slot[dec]/[dec] service type [dec] has exceed the high watermark [dec] |
Several unblocked IPC message are pending in the request queue to get the ack. If the pending message are increasing it may result in the Memory leak. |
ubr10k-sw |
LOG_STD_ACTION |
|
REQGRP-6-CORRUPTIPC |
6-Information |
Corrupted IPC slot = [dec]/[dec] received at Cable[dec]/[dec] |
Some code has cloberred the IPC message |
ubr10k-sw |
LOG_STD_ACTION |
|
REQGRP-6-NBLKEVT_Q_FULL |
6-Information |
Nonblocking IPC event queue full [dec] events |
- |
- |
- |
|
REQGRP-6-UNKLCREQ |
6-Information |
Received unknown IPC request [dec] from [dec]/[dec] |
- |
- |
- |
|
REQGRP-6-UNKVER |
6-Information |
Received IPC with unsupported version [dec] |
- |
- |
- |
|
RESETMGR-3-NOMEM |
3-Error |
Failed to allocate memory to add ID [dec] to table |
Reset Manager was unable to allocate memory to add the unique ID and process name to its table. If this process is restarted on the Active system the Standby system may not be reset due to this error. |
resetmgr |
"show tech" |
|
RESETMGR-3-RESET |
3-Error |
Reset Manager has reset the system due to \'[chars]\' process restart |
Reset Manager stores a set of IDs each one of these IDs uniquely identify a process on the system. If one of these monitored processes is restarted the Standby unit will be reset so that the versioning infrastructure can renegotiate. This is not a software fault the Standby system is being forced to reset by the Reset Manager. |
resetmgr |
LOG_STD_NO_ACTION |
|
RESETMGR-3-RESET_UNKNOWN |
3-Error |
A restarted process could not be identified by its Job ID the Reset Manager has reset the Standby system. |
Reset Manager stores a set of IDs each one of these IDs uniquely identifies a process on the system. A process was restarted but it could not be uniquely identified via it Job ID. It is possible that the restarted process was being monitored by the Reset Manager but since we cannot be sure the Standby system is being reset. This is most likely due to a software fault on the system. |
resetmgr |
LOG_STD_NO_ACTION |
|
RESETMGR-3-SYSMGR_JOBID_LOOKUP |
3-Error |
Failed to get the job ID of the Reset Manger IOS blob from SysMgr |
Reset Manager was unable to get it's job ID same as IOS blob from |
resetmgr |
"show tech" |
|
RESETMGR-4-SYSMGR_PROCNAME_LOOKUP |
4-Warning |
Failed to lookup process name from SysMgr job ID = [dec] |
Reset Manager was unable to get the name of the process with the specified job ID from SysMgr. This is a SysMgr error however the system can continue to operate normally as the process name is only used for reference purposes. |
resetmgr |
"show tech" |
|
RESTART_SHUTDOWN-4-LDP |
4-Warning |
ERRMSG_NOFLAGS |
- |
- |
- |
|
RF_ISSU-3-CAP_REG |
3-Error |
RF cap reg on domain [dec] failed: reason [dec] |
The capabilities of the RF ISSU could not be registered. |
ha-issu-infra |
"show issu capability <arguments>" |
|
RF_ISSU-3-CAP_REG |
3-Error |
RF cap reg on domain [dec] failed: reason [dec] |
The capabilities of the RF ISSU could not be registered. |
ha-issu-infra |
"show issu capability <arguments>" |
|
RF_ISSU-3-CAPENTRY_REG |
3-Error |
RF Cap Entry [dec] for Entity [dec] domain [dec] Registration failed |
A capability entry could not be registered for the RF ISSU. |
ha-issu-infra |
"show issu capability entries" |
|
RF_ISSU-3-CAPENTRY_REG |
3-Error |
RF Cap Entry [dec] for Entity [dec] domain [dec] Registration failed |
A capability entry could not be registered for the RF ISSU. |
ha-issu-infra |
"show issu capability entries" |
|
RF_ISSU-3-CAPGROUP_REG |
3-Error |
RF Cap Group [dec] for Entity [dec] domain [dec] Registration failed |
A capability group could not be registered for the RF ISSU. |
ha-issu-infra |
"show capability groups" |
|
RF_ISSU-3-CAPGROUP_REG |
3-Error |
RF Cap Group [dec] for Entity [dec] domain [dec] Registration failed |
A capability group could not be registered for the RF ISSU. |
ha-issu-infra |
"show capability groups" |
|
RF_ISSU-3-CAPTYPE_REG |
3-Error |
RF Cap Type for Entity [dec] domain [dec] Registration failed |
A capability type could not be registered for the RF ISSU. |
ha-issu-infra |
"show issu capability types" |
|
RF_ISSU-3-CAPTYPE_REG |
3-Error |
RF Cap Type for Entity [dec] domain [dec] Registration failed |
A capability type could not be registered for the RF ISSU. |
ha-issu-infra |
"show issu capability types" |
|
RF_ISSU-3-CLIENT_REG |
3-Error |
RF Client [dec] Registration failed |
The RF ISSU client could not be registered. |
ha-issu-infra |
"show issu clients" |
|
RF_ISSU-3-CLIENT_REG |
3-Error |
RF Client [dec] Registration failed |
The RF ISSU client could not be registered. |
ha-issu-infra |
"show issu clients" |
|
RF_ISSU-3-CLIENT_REG_FAILED |
3-Error |
RF ISSU client [dec] domain [dec] Client registration failed. [chars] |
The RF ISSU client could not be registered during system initialization. |
ha-issu-infra |
"show issu clients" |
|
RF_ISSU-3-CLIENT_REG_FAILED |
3-Error |
RF ISSU client [dec] domain [dec] Client registration failed. [chars] |
The RF ISSU client could not be registered during system initialization. |
ha-issu-infra |
"show issu clients" |
|
RF_ISSU-3-ENTITY_REG |
3-Error |
RF Entity [dec] domain [dec] Registration failed |
The RF ISSU entity could not be registered. |
ha-issu-infra |
"show issu entities" |
|
RF_ISSU-3-ENTITY_REG |
3-Error |
RF Entity [dec] domain [dec] Registration failed |
The RF ISSU entity could not be registered. |
ha-issu-infra |
"show issu entities" |
|
RF_ISSU-3-GET_BUFFER |
3-Error |
RF ISSU session [dec] domain [dec] failed to get buffer |
RF ISSU failed to get a buffer |
ha-issu-infra |
"show issu fsm" |
|
RF_ISSU-3-GET_BUFFER |
3-Error |
RF ISSU session [dec] domain [dec] failed to get buffer |
RF ISSU failed to get a buffer |
ha-issu-infra |
"show issu fsm" |
|
RF_ISSU-3-INVALID_SESSION |
3-Error |
RF ISSU client on domain [dec] does not have a valid registered session. |
The RF ISSU client does not have a valid registered session. |
ha-issu-infra |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
RF_ISSU-3-INVALID_SESSION |
3-Error |
RF ISSU client on domain [dec] does not have a valid registered session. |
The RF ISSU client does not have a valid registered session. |
ha-issu-infra |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
RF_ISSU-3-ISSU_MSG_BAD_PEER_SID |
3-Error |
Inbound ISSU message routed through RF on domain [dec] |
RF has received an invalid ISSU message which will not be processed. |
redundancy-rf |
"show redundancy history reverse" |
|
RF_ISSU-3-ISSU_MSG_BAD_PEER_SID |
3-Error |
Inbound ISSU message routed through RF on domain [dec] |
RF has received an invalid ISSU message which will not be processed. |
redundancy-rf |
"show redundancy history reverse" |
|
RF_ISSU-3-MSG_DATAPTR |
3-Error |
RF Client [dec] domain [dec] get msg dataptr failed. Error = [dec] |
The RF ISSU client could not obtain a message data pointer. |
ha-issu-infra |
"show issu fsm" |
|
RF_ISSU-3-MSG_DATAPTR |
3-Error |
RF Client [dec] domain [dec] get msg dataptr failed. Error = [dec] |
The RF ISSU client could not obtain a message data pointer. |
ha-issu-infra |
"show issu fsm" |
|
RF_ISSU-3-MSG_MTU |
3-Error |
RF Client [dec] domain [dec] get msg mtu failed. Error = [dec] |
The RF ISSU client could not obtain message size. |
ha-issu-infra |
"show issu fsm" |
|
RF_ISSU-3-MSG_MTU |
3-Error |
RF Client [dec] domain [dec] get msg mtu failed. Error = [dec] |
The RF ISSU client could not obtain message size. |
ha-issu-infra |
"show issu fsm" |
|
RF_ISSU-3-MSG_REG |
3-Error |
RF msg reg on domain [dec] failed: reason [dec] |
Messages for the RF ISSU could not be registered. |
ha-issu-infra |
"show issu message <arguments>" |
|
RF_ISSU-3-MSG_REG |
3-Error |
RF msg reg on domain [dec] failed: reason [dec] |
Messages for the RF ISSU could not be registered. |
ha-issu-infra |
"show issu message <arguments>" |
|
RF_ISSU-3-MSG_SEND |
3-Error |
RF ISSU client for session [dec] domain [dec] failed to send message |
The RF ISSU client could not send a negotiation message to a peer. |
ha-issu-infra |
"show issu fsm" |
|
RF_ISSU-3-MSG_SEND |
3-Error |
RF ISSU client for session [dec] domain [dec] failed to send message |
The RF ISSU client could not send a negotiation message to a peer. |
ha-issu-infra |
"show issu fsm" |
|
RF_ISSU-3-MSGGROUP_REG |
3-Error |
RF Msg Group [dec] for Entity [dec] domain [dec] Registration failed |
The message group for the RF ISSU could not be registered. |
ha-issu-infra |
"show issu message groups" |
|
RF_ISSU-3-MSGGROUP_REG |
3-Error |
RF Msg Group [dec] for Entity [dec] domain [dec] Registration failed |
The message group for the RF ISSU could not be registered. |
ha-issu-infra |
"show issu message groups" |
|
RF_ISSU-3-MSGTYPE_REG |
3-Error |
RF Msg Type for Entity [dec] domain [dec] Registration failed |
The message type for the RF ISSU could not be registered. |
ha-issu-infra |
"show issu message types" |
|
RF_ISSU-3-MSGTYPE_REG |
3-Error |
RF Msg Type for Entity [dec] domain [dec] Registration failed |
The message type for the RF ISSU could not be registered. |
ha-issu-infra |
"show issu message types" |
|
RF_ISSU-3-RF_CAP_INVALID_SIZE |
3-Error |
RF ISSU client capability list on domain [dec] is empty. |
RF ISSU capability list size is invalid |
ha-issu-infra |
"show issu capability entires <Client_ID>" |
|
RF_ISSU-3-RF_CAP_INVALID_SIZE |
3-Error |
RF ISSU client capability list on domain [dec] is empty. |
RF ISSU capability list size is invalid |
ha-issu-infra |
"show issu capability entires <Client_ID>" |
|
RF_ISSU-3-RF_CAP_RESULT_INCOMP |
3-Error |
RF ISSU client capability exchange om domain [dec] result incompatible. |
RF ISSU capabilities have negotiated incompatible |
ha-issu-infra |
"show issu negotiated capability <Session_ID>" |
|
RF_ISSU-3-RF_CAP_RESULT_INCOMP |
3-Error |
RF ISSU client capability exchange on domain [dec] result incompatible. |
RF ISSU capabilities have negotiated incompatible |
ha-issu-infra |
"show issu negotiated capability <Session_ID>" |
|
RF_ISSU-3-RF_MSG_NOT_OK |
3-Error |
RF ISSU msg type [dec] for client [dec] on domain [dec] is not ok |
RF ISSU message type has not negotiated correctly |
ha-issu-infra |
"show message types <Client_ID>" |
|
RF_ISSU-3-RF_MSG_NOT_OK |
3-Error |
RF ISSU msg type [dec] for client [dec] on domain [dec] is not ok |
RF ISSU message type has not negotiated correctly |
ha-issu-infra |
"show message types <Client_ID>" |
|
RF_ISSU-3-SESSION_REG |
3-Error |
RF session for Entity [dec] domain [dec] Registration failed |
The RF ISSU session could not be registered. |
ha-issu-infra |
"show issu sessions" |
|
RF_ISSU-3-SESSION_REG |
3-Error |
RF session for Entity [dec] domain [dec] Registration failed |
The RF ISSU session could not be registered. |
ha-issu-infra |
"show issu sessions" |
|
RF_ISSU-3-SESSION_UNREG |
3-Error |
RF session [dec] domain [dec] Un-Registration failed |
The RF ISSU session could not be unregistered. |
ha-issu-infra |
"show issu sessions" |
|
RF_ISSU-3-SESSION_UNREG |
3-Error |
RF session [dec] domain [dec] Un-Registration failed |
The RF ISSU session could not be unregistered. |
ha-issu-infra |
"show issu sessions" |
|
RF_REGISTER_FAILED-3-MPLS_TE_HA |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
RF_UNREGISTER_FAILED-3-MPLS_TE_HA |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
RF-1-SYSTEM_INTEGRITY |
1-Alert |
[chars] |
An automatic switch of activity occurred when it had been disabled. |
CPU |
LOG_STD_ACTION |
|
RF-3-COMMUNICATION |
3-Error |
Communication with the peer CPU has been [chars] |
The status of the peer CPU communication path has changed |
CPU |
LOG_STD_ACTION |
|
RF-3-IPC_PORT |
3-Error |
Unable to [chars] [chars] <[chars]> |
Not able to initialize the RF IPC port to the peer CPU. |
CPU |
LOG_NO_ACTION |
|
RF-3-MALLOC_FAILURE |
3-Error |
[chars] |
Memory allocation failure |
redundancy-rf |
"Gather redundancy-ha_mgr log and send it to TAC" |
|
RF-3-MSG_SEND_FAILURE |
3-Error |
[chars] |
Message send between internal RF modules failed. |
redundancy-rf |
"Gather redundancy-ha_mgr log and send it to TAC" |
|
RF-3-NOTIF_TID |
3-Error |
Notification timer extended for the wrong client cur-client=[dec] req-client=[dec] |
The current RF client has attempted to extend the RF notification timer using a client ID other than its own. This is an internal software error. The message text on the console or in the system log contains the error details such as the current client ID number and the requested client ID number. |
redundancy-rf |
"show redundancy history" |
|
RF-3-NOTIF_TMO |
3-Error |
Notification timer Expired for RF Client: [chars][dec] |
As part of the progression the client had previously indicated to RF that it has work to do by returning RF_OK but it did not complete the work or respond to RF within the notification time. |
redundancy-rf |
"show redundancy history" |
|
RF-3-SIMPLEX_MODE |
3-Error |
The peer CPU has been lost |
The peer CPU absence has been detected |
CPU |
LOG_STD_ACTION |
|
RF-3-STANDBY_RELOAD |
3-Error |
The standby CPU is being reset because [chars] |
See the reported error message for the reason that the peer CPU was reset. This allows recovery from an indeterminate Standby state. |
CPU |
LOG_STD_ACTION |
|
RF-5-RF_RELOAD |
5-Notice |
[chars]. Reason: [chars] |
RF has invoked a reload. |
redundancy-rf |
"show redundancy history reload" |
|
RF-5-RF_TERMINAL_STATE |
5-Notice |
Terminal state reached for [chars] |
RF has reached a terminal state for the operating mode. |
- |
"This is a notification message only. No action is required." |
|
RF-5-SEND_FAIL |
5-Notice |
RF client progression send failure for reason [chars] |
RF has failed to send a client progression to the standby client. |
redundancy-rf |
"show redundancy history" |
|
RF-6-DUPLEX_MODE |
6-Information |
The peer CPU has been detected |
The peer CPU has been detected |
CPU |
LOG_STD_ACTION |
|
RF-6-INHIBIT_SWITCH |
6-Information |
Redundancy client [chars] [chars] manual switchover |
A redundancy client has changed the ability to manually cause a switch of activity. |
CPU |
LOG_NO_ACTION |
|
RFPROXY-2-INIT |
2-Critical |
Initialization failed |
The RF Proxy subsystem failed during its \n\ initialization |
c7600-ha |
LOG_STD_SH_TECH_ACTION |
|
RFPROXY-2-NOMEM |
2-Critical |
No memory available |
The RF Proxy subsystem could not obtain the memory \n\ it needed |
c7600-ha |
LOG_STD_SH_TECH_ACTION |
|
RFPROXY-2-RPC |
2-Critical |
RPC message failure |
The RF Proxy could not send an RPC message. |
c7600-ha |
- |
|
RFS-3-CAPENTRY_REG |
3-Error |
RFS Cap Entry [dec] for Entity [dec] Registration failed |
RFS ISSU Cap Entry registration failed |
- |
"Enter the following commands: show issu capability entries and copy " "the error and send it to TAC. TAC team can contact the file-systems " "team to check why this capability entry failed to register" |
|
RFS-3-CAPGROUP_REG |
3-Error |
RFS Cap Group [dec] for Entity [dec] Registration failed |
RFS ISSU Cap Group registration failed |
- |
"Enter the following commands: show issu capability groups and copy " "the error and send it to TAC. TAC team can contact the file-systems " "team to check why this capability group failed to register" |
|
RFS-3-CAPTYPE_REG |
3-Error |
RFS Cap Type for Entity [dec] Registration failed |
RFS ISSU Cap Type registration failed |
- |
"Enter the following commands: 'show issu capability types' and copy " "the error and send it to TAC. TAC team can contact the file-systems " "team to check why this capability type failed to register" |
|
RFS-3-CLIENT_REG |
3-Error |
RFS Client [dec] Registration failed |
RFS ISSU client registration failed |
- |
"Enter the following command:'show issu client' and " "copy the error and send it to TAC. TAC team can contact the " "file-systems team to check why no uid with this value found " "registered in ISSU Database" |
|
RFS-3-CLIENT_SESSION_REG |
3-Error |
RFS ISSU client shared msg session for entity [dec] registration failed |
RFS ISSU client shared msg session registration failed |
- |
"Enter the following commands: show issu sessions and copy the error " "and send it to TAC. TAC team can contact the file-systems team to " "check why this shared message session failed to register" |
|
RFS-3-CLIENT_SESSION_UNREG |
3-Error |
RFS session [dec] Un-Registration failed |
RFS ISSU client session un-registration failed |
- |
"Enter the following commands: show issu sessions and copy the error " "and send it to TAC. TAC team can contact the file-systems team to " "check why this client session failed to un-register" |
|
RFS-3-CREATE_CLIENT_PORT |
3-Error |
RFS create client port [chars] failed |
RFS ISSU create client port failed |
- |
"Enter the following commands: show ipc port and copy the error and " "send it to TAC. TAC team can contact the file-systems team to check " "why this ipc port could not be created" |
|
RFS-3-CREATE_SERVER_PORT |
3-Error |
RFS create server port [chars] failed |
RFS ISSU create server port failed |
- |
"Enter the following commands: show ipc port and copy the error and " "send it to TAC. TAC team can contact the file-systems team to check " "why this ipc port could not be created" |
|
RFS-3-ENTITY_REG |
3-Error |
RFS Entity [dec] Registration failed |
RFS ISSU entity failed to register with ISSU |
- |
"Enter the following command:'show issu entities' " "and copy the error and send it to TAC. TAC team can contact the " "file-systems team to check why this entity failed to register" |
|
RFS-3-IPC_GET_BUFFER |
3-Error |
RFS issu ipc get buffer failed |
RFS ISSU ipc get buffer failed |
- |
"Enter the following commands:'show proc mem' or 'show buffs' to " "check if memory or buffer is full. shutdown unused tasks or reset " "cards usually can recover those memory leak problem. Copy the error " "and send it to TAC if those actions do not help." |
|
RFS-3-LOCATE_PORT |
3-Error |
RFS locates port [chars] failed |
RFS ISSU locates port failed |
- |
"Enter the following commands: show ipc port and copy the error and " "send it to TAC. TAC team can contact the file-systems team to check " "why this ipc port could not be located" |
|
RFS-3-MSG_GET_NEGO_VER |
3-Error |
RFS Client [dec] get msg negotiated version failed. Error = [dec] |
RFS ISSU client get msg negotiated version failed |
- |
"Enter the following commands: show issu fsm show issu ses and copy " "the error and send it to TAC. TAC team can contact the file-systems " "team to check why get message negotiated version failed" |
|
RFS-3-MSG_INCOMP |
3-Error |
[chars]: msg_type [[dec]] under session [[dec]] is incompatible |
The message types are incompatible under ISSU |
- |
"Enter the following command: \n\ show issu message types 110 \and copy the output and send it to TAC. TAC team can contact the \file-systems team to check why messages are incompatible" |
|
RFS-3-MSG_MTU |
3-Error |
RFS Client [dec] get msg mtu failed. Error = [dec] |
RFS ISSU client get msg mtu failed |
- |
"Enter the following commands: show issu fsm show issu ses and copy " "the error and send it to TAC. TAC team can contact the file-systems " "team to check why get message mtu failed" |
|
RFS-3-MSG_RCV |
3-Error |
RFS Client [dec] on session [dec] to seat [0x[hec]] failed receive |
RFS ISSU client receive msg failed |
- |
"Enter the following commands:show issu sessions and copy the error " "and send it to TAC. TAC team can contact the file-systems team to " "check why receive message for this client failed" |
|
RFS-3-MSG_XMIT |
3-Error |
RFS Client [dec] on session [dec] to seat [0x[hec]] failed send |
RFS ISSU client send msg failed |
- |
"Enter the following commands:show issu sessions and copy the error " "and send it to TAC. TAC team can contact the file-systems team to " "check why send message for this client failed" |
|
RFS-3-MSGGROUP_REG |
3-Error |
RFS Msg Group [dec] for Entity [dec] Registration failed |
RFS ISSU Msg Group registration failed |
- |
"Enter the following commands: 'show issu message groups' \and copy the error and send it to TAC. TAC team can contact the \file-systems team to check why this message group failed to register" |
|
RFS-3-MSGTYPE_REG |
3-Error |
RFS Msg Type for Entity [dec] Registration failed |
RFS ISSU Msg Type registration failed |
- |
"Enter the following commands: " "'show issu entities' 'show issu message types' and copy the error " "and send it to TAC. TAC team can contact the file-systems team to " "check why this message types failed to register" |
|
RFS-3-NEGO_COMP |
3-Error |
RFS nego is not compatible [dec] |
RFS ISSU start shared nego session failed |
- |
"Enter the following commands: 'show issu sessions' and copy the " "error and send it to TAC. TAC team can contact the file-systems " "team to check why this client negotiation session is not compatible" |
|
RFS-3-NEGO_SESSION_REG |
3-Error |
RFS nego session for Entity [dec] Registration failed |
RFS ISSU shared nego session registration failed |
- |
"Enter the following commands: 'show issu sessions' 'show issu " "entities' and copy the error and send it to TAC. TAC team can " "contact the file-systems team to check why this client negotiation " "session failed to register" |
|
RFS-3-NEGO_SESSION_UNREG |
3-Error |
RFS session [dec] Un-Registration failed |
RFS ISSU shared nego session un-registration failed |
- |
"Enter the following commands: 'show issu sessions' and copy the " "error and send it to TAC. TAC team can contact the file-systems " "team to check why this client negotiation session failed to " "un-register" |
|
RFS-3-OPEN_CLIENT_PORT |
3-Error |
RFS open client port [chars] failed. Reason:[chars] |
RFS ISSU open client port failed |
- |
"Enter the following commands: show ipc port and copy the error and " "send it to TAC. TAC team can contact the file-systems team to check " "why this ipc port could not be opened" |
|
RFS-3-OPEN_SERVER_PORT |
3-Error |
RFS open server port [chars] failed |
RFS ISSU open server port failed |
- |
"Enter the following commands: show ipc port and copy the error and " "send it to TAC. TAC team can contact the file-systems team to check " "why this ipc port could not be opened" |
|
RFS-3-RECEIVE_NEGO_FAILED |
3-Error |
RFS receive nego message %p failed |
RFS ISSU receive nego message failed |
- |
"Enter the following commands: 'show issu session' and copy the error " "and send it to TAC. TAC team can contact the file-systems team to " "check why this client negotiation message failed" |
|
RFS-3-RECEIVE_NEGO_NOT_DONE |
3-Error |
RFS receive nego message is not done [dec] |
RFS ISSU receive nego message is not done |
- |
"Enter the following commands: show issu session and copy the error " "and send it to TAC. TAC team can contact the file-systems team to " "check why this client negotiation failed to complete" |
|
RFS-3-REG_PORT |
3-Error |
RFS reg port [dec] failed |
RFS ISSU reg port failed |
- |
"Enter the following commands: show ipc port and copy the error and " "send it to TAC. TAC team can contact the file-systems team to check " "why this port failed to register" |
|
RFS-3-RFS_BOOL_CREATE_ERR |
3-Error |
[chars]. |
The RFS RF client has error in creating watched boolean. |
- |
LOG_STD_ACTION |
|
RFS-3-RFS_ISSU_CLIENT_OR_ENTITY_ID |
3-Error |
RFS ISSU couldnt find client/entity id in peer. |
RFS ISSU couldnt find client/entity id in peer. |
- |
"Enter the following command:'show issu entities' " "and copy the error and send it to TAC. TAC team can contact the " "file-systems team to check why this client/entity id coudlnt find " "in peer" |
|
RFS-3-RFS_ISSU_NEGO_PROCESS |
3-Error |
RFS create rfs_issu_start_port watch boolean failed |
RFS ISSU create nego process failed |
- |
"Enter the following commands:show proc mem and copy the error and " "send it to TAC. TAC team can contact the file-systems team to check " "why this watched boolean could not be created" |
|
RFS-3-RFS_ISSU_START_PORT |
3-Error |
RFS create rfs_issu_start_port watch boolean failed |
RFS ISSU create rfs_issu_start_port watch boolean failed |
- |
"Enter the following commands:show proc mem and copy the error and " "send it to TAC. TAC team can contact the file-systems team to check " "why this watched boolean could not be created" |
|
RFS-3-RFS_ISSU_START_SESSION |
3-Error |
RFS create rfs_issu_start_session watch boolean failed |
RFS ISSU create rfs_issu_start_session watch boolean failed |
- |
"Copy the error and send it to TAC. TAC team can contact the " "file-systems team to check why this ipc port could not be created" |
|
RFS-3-RFS_RF_PROG_ERR |
3-Error |
Failed to send the bulk sync notification done. Error [dec]. |
The RFS RF client failed to send the final bulk sync \notification. |
- |
LOG_STD_ACTION |
|
RFS-3-RFS_RF_PROG_NOT_SENT_ERR |
3-Error |
[chars]. |
The RFS RF client has error in sending client \progression. |
- |
LOG_STD_ACTION |
|
RFS-3-SEND_NEGO_MESSAGE |
3-Error |
RFS send nego message %p failed |
RFS ISSU send nego message failed |
- |
"Enter the following commands: 'show issu session' and copy the error " "and send it to TAC. TAC team can contact the file-systems team to " "check why this client negotiation message failed" |
|
RFS-3-START_NEGO_SESSION |
3-Error |
RFS nego [dec]:[dec] to [[chars]:0x[hec]] failed: [[chars]] |
RFS ISSU start shared nego session failed |
- |
"Enter the following commands: 'show issu sessions' and copy the " "error and send it to TAC. TAC team can contact the file-systems " "team to check why this client negotiation session failed to start" |
|
RFS-3-UNREG_ENTITY |
3-Error |
RFS ISSU Client unreg entity failed. |
RFS ISSU client unreg entity failed |
- |
"Enter the following command:'show issu entities' " "and copy the error and send it to TAC. TAC team can contact the " "file-systems team to check why this entity failed to un-register" |
|
RFSW-3-HELLO_FAIL |
3-Error |
Hello message failed between CMTS and RFSW. \nPlease check the connection between CMTS and RFSW. |
Hello message between CMTS and RFGW failed. |
cmts-redundancy |
"Check the connection between CMTS and RFSW." |
|
RFSW-3-LCSO_FAIL |
3-Error |
Receive a failed LCSO message from RFSW with sequence 0x%04X. |
LCSO command failed to execute in RFSW. |
cmts-redundancy |
"Check the switchcards state in RFSW." |
|
RFSW-3-RELAY_FAIL |
3-Error |
Relay failed for RFSW. |
The relay testing failed. |
cmts-redundancy |
"Check the connection between CMTS and RFSW." |
|
RFSW-6-HELLO_ERROR |
6-Information |
The switchcard in RFSW for slot [dec] group [dec] is in error with the reason [chars]. |
The switchcards in RFSW is in errro |
cmts-redundancy |
"Check the switchcard state of RFSW" |
|
RFSW-6-HELLO_PROTECT |
6-Information |
The protecting state in RFSW is wrong expect [dec] get [dec]. |
The protecting state in RFSW is wrong. |
cmts-redundancy |
"Disable and Enable the configure \"rfswitch auxport enable\"." |
|
RG_AR-3-NOPEER |
3-Error |
Peer does not exist for RG ID = [dec] with error code = [dec] |
- |
- |
- |
|
RG_AR-3-NOPROCESS |
3-Error |
Unable to create process for [chars]. |
Quite likely we ran out of memory. Other explanations are possible. |
rg-infra |
"If this message recurs. Check bug toolkit " "on Cisco website for the issue. If you didn't find " "one Enter <CmdBold>Show tech-support<NoCmdBold> " "command collect all the information and error " "message and report it to your technical support " "representative." |
|
RG_FAULTS-3-NOPROCESS |
3-Error |
Unable to create a new process for [chars]. |
Quite likely we ran out of memory. Other explanations are possible. |
rg-infra |
"If this message recurs. Check bug toolkit " "on Cisco website for the issue. If you didn't find " "one Enter <CmdBold>Show tech-support<NoCmdBold> " "command collect all the information and error " "message and report it to your technical support " "representative." |
|
RG_FAULTS-6- PRICHANGE |
6-Information |
RG Infra RG[[dec]] Priority update. new priority [[dec]] old priority [[dec]] [chars] |
The runtime priority of the group was updated |
rg-infra |
"Look at rg_infra trace for the cause for priority change" |
|
RG_FAULTS-6- PRICONFCHANGE |
6-Information |
RG Infra RG[[dec]] Priority configuration changed. New runtime priority:[[dec]] |
The configured priority changed runtime priority was affected |
rg-infra |
"No action need to be taken" |
|
RG_MEDIA-3-INVALIDPLATFORM |
3-Error |
Unsupported Platform |
The peer platform is unsupported as a RG-pair |
rg-infra |
"Only like platforms can be configured as a RG pair." |
|
RG_MEDIA-3-NOPROCESS |
3-Error |
Unable to create process for [chars]. |
Quite likely we ran out of memory. Other explanations are possible. |
rg-infra |
"If this message recurs. Check bug toolkit " "on Cisco website for the issue. If you didn't find " "one Enter <CmdBold>Show tech-support<NoCmdBold> " "command collect all the information and error " "message and report it to your technical support " "representative." |
|
RG_MEDIA-3-NOSOCKET |
3-Error |
Unable to open socket |
The system was unable to initialize an IP connection for RG Protocol |
rg-infra |
"Make sure that there is at least one interface configured to run " "IP." |
|
RG_MEDIA-3-TIMEREXPIRED |
3-Error |
RG id [dec] Hello Timer Expired. |
This router did not receive hello message from the peer within the configured hold time. This may result in a role change. |
rg-infra |
"Enter <CmdBold>show tech-support<NoCmdBold> " "<CmdBold>show history<NoCmdBold> commands collect " "all the information and error message and report it " "to your technical support representative." |
|
RG_MEDIA-4-BADSEQ |
4-Warning |
Group [dec]: Sequence number larger than expected - indicates packet loss |
Sequence number expected from peer is too big this usually indicates packet loss |
rg-infra |
"Check for connectivity problems between the 2 peers." |
|
RG_PROTOCOL-3-NOPROCESS |
3-Error |
Unable to create process for [chars]. |
Quite likely we ran out of memory. Other explanations are possible. |
rg-infra |
"If this message recurs. Check bug toolkit " "on Cisco website for the issue. If you didn't find " "one Enter <CmdBold>Show tech-support<NoCmdBold> " "command collect all the information and error " "message and report it to your technical support " "representative." |
|
RG_PROTOCOL-3-UNEXPECTEDACTIVE |
3-Error |
RG id [dec] unexpected Active peer [inet] |
- |
rg-infra |
"If this is not a transient state check for connectivity problems " "or inconsistency of rg protocol timer configuration between " "the peers" |
|
RG_PROTOCOL-4-UNEXPECTEDSTANDBY |
4-Warning |
RG id [dec] unexpected Standby peer [inet] |
- |
rg-infra |
"If this is not a transient state check for connectivity problems " "or inconsistency of rg protocol timer configuration between " "the peers" |
|
RG_PROTOCOL-5-ROLECHANGE |
5-Notice |
RG id [dec] role change from [chars] to [chars] |
RG role Init/Standby/Active has been changed |
rg-infra |
LOG_STD_NO_ACTION |
|
RG_TRANSPORT-3-NOPROCESS |
3-Error |
Unable to create process for [chars]. |
Quite likely we ran out of memory. Other explanations are possible. |
rg-infra |
"If this message recurs. Check bug toolkit " "on Cisco website for the issue. If you didn't find " "one Enter <CmdBold>Show tech-support<NoCmdBold> " "command collect all the information and error " "message and report it to your technical support " "representative." |
|
RG_TRANSPORT-3-TRANSFAIL |
3-Error |
Negotiation failure with error code: [dec] |
The query_status in msg is not RG_TRANS_SUCCESS |
rg-infra |
"Make sure that there are no configuration errors." |
|
RG_VP-3-NOPROCESS |
3-Error |
Unable to create process for [chars]. |
Quite likely we ran out of memory. Other explanations are possible. |
rg-infra |
"If this message recurs. Check bug toolkit " "on Cisco website for the issue. If you didn't find " "one Enter <CmdBold>Show tech-support<NoCmdBold> " "command collect all the information and error " "message and report it to your technical support " "representative." |
|
RG_VP-6-BULK_SYNC_DONE |
6-Information |
RG group [dec] BULK SYNC to standby complete. |
Indicagtes Standby bulk sync complete |
rg-infra |
LOG_STD_NO_ACTION |
|
RG_VP-6-STANDBY_READY |
6-Information |
RG group [dec] Standby router is in SSO state |
Indicates standby readiness |
rg-infra |
LOG_STD_NO_ACTION |
|
RIP-3-NOSOCKET |
3-Error |
Unable to open socket |
The requested operation could not be accomplished because of a low\n\ memory condition. |
- |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
RITE-5-ACTIVATE |
5-Notice |
Activated IP traffic export on interface [chars] |
IP traffic export has been enabled on the specified interface |
- |
"None" |
|
RITE-5-DEACTIVATE |
5-Notice |
Deactivated IP traffic export on interface [chars] |
IP traffic export has been disabled on the specified interface |
- |
"None" |
|
RITE-5-MODIFIED |
5-Notice |
Changed IP traffic export outbound interface from [chars] to [chars] |
The outbound interface for IP traffic export has been changed |
- |
"None" |
|
RLC_ISSU_PROCESS_CLI-3-NULL_RED_CONFIG |
3-Error |
Redundancy configuration can not be NULL. |
Redundancy configuration can not be NULL. |
ha-issu-infra |
"Copy the error and send it to TAC.\n\TAC team can contact ISSU infrastruture team to check why redundancy configuration is NULL" |
|
RLC_ISSU_PROCESS_CLI-3-NULL_SLOTINDEX |
3-Error |
slotindex can not be NULL. |
slotindex can not be NULL. |
ha-issu-infra |
"Copy the error and send it to TAC.\n\TAC team can contact ISSU infrastruture team to check why slotindex is NULL" |
|
RLC_ISSU_PROCESS_CLI-3-RLC_ISSU_ERR |
3-Error |
[chars] |
An error occurred while executing Redundanct LC ISSU CLI |
ha-issu-infra |
"Copy the error and send it to TAC.\n\TAC team can contact ISSU infrastruture team to check why this error occurs" |
|
RLC_ISSU_PROCESS-3-NULL_RED_CONFIG |
3-Error |
Redundancy configuration can not be NULL. |
Redundancy configuration can not be NULL. |
ha-issu-infra |
"Copy the error and send it to TAC.\n\TAC team can contact ISSU infrastruture team to check why redundancy configuration is NULL" |
|
RLC_ISSU_PROCESS-3-RLC_ISSU_ERR |
3-Error |
[chars] |
An error occurred while running the Redundanct LC ISSU process |
ha-issu-infra |
"Copy the error and send it to TAC.\n\TAC team can contact ISSU infrastruture team to check why this error occurs" |
|
RLC_ISSU_PROCESS-3-RLC_ISSU_MLC_FSM_ERR |
3-Error |
error processing [chars] event in [chars] state for LC [chars] terminating process |
internal error in RLC ISSU event processing |
ha-issu-infra |
"Copy the error and send it to TAC.\n\TAC team can contact ISSU infrastruture team to check why this error occurs" |
|
RLC_ISSU_PROCESS-3-RLC_ISSU_N1_PLC_FSM_ERR |
3-Error |
error processing [chars] event in [chars] state for LC [chars] terminating process |
internal error in RLC ISSU event processing |
ha-issu-infra |
"Copy the error and send it to TAC.\n\TAC team can contact ISSU infrastruture team to check why this error occurs" |
|
RLC_ISSU_PROCESS-3-RLC_ISSU_N1_PLC_PSLC_ERR |
3-Error |
prepareversion error secondary LC not standby ready for LC [chars] |
the secondary LC failed to become standby ready |
ha-issu-infra |
"Copy the error and send it to TAC.\n\TAC team can contact ISSU infrastruture team to check why this error occurs" |
|
RLC_ISSU_PROCESS-3-RLC_ISSU_N1_PLC_WPLC_ERR |
3-Error |
runversion error primary LC [chars] not standby ready |
the primary LC is not ready for switchover |
ha-issu-infra |
"Copy the error and send it to TAC.\n\TAC team can contact ISSU infrastruture team to check why this error occurs" |
|
RLC_ISSU_PROCESS-3-RLC_ISSU_NOTIF_ERR |
3-Error |
LC ISSU is terminated for due to [chars] use \n\'issu linecard abortversion [chars]' to restore linecard to the original version if necessary |
An error notification was received while running the \n\Redundanct LC ISSU process. The process is stopped |
ha-issu-infra |
"Copy the error and send it to TAC.\n\TAC team can contact ISSU infrastruture team to check why this error occurs" |
|
RLC_ISSU_PROCESS-3-RLC_ISSU_RLD_PLC_FSM_ERR |
3-Error |
error processing [chars] event in [chars] state for LC idx [chars] terminating process |
internal error in RLC ISSU event processing |
ha-issu-infra |
"Copy the error and send it to TAC.\n\TAC team can contact ISSU infrastruture team to check why this error occurs" |
|
RLC_ISSU_PROCESS-4-LCRPVERSION |
4-Warning |
Linecard [chars] and RP have different image versions |
Linecard has different version of image than RP |
ha-issu-infra |
"Use RLC ISSU commands to change these\n\ LCs' images to same version as RP" |
|
RLC_ISSU_PROCESS-4-RLC_ISSU_IMAGE_ERR |
4-Warning |
error loading LC image for LC [chars] |
internal error in loading linecard image |
ha-issu-infra |
"Copy the error and send it to TAC.\n\TAC team can contact ISSU infrastruture team to check why this error occurs" |
|
RLC_ISSU_PROCESS-4-RLC_ISSU_NOT_COMPLETED_WARNING |
4-Warning |
LC ISSU is not finished please issue the next commands to complete LC ISSU |
The steps to complete LC ISSU has not been fully carried\n\out by the operator. The system is left in an intermediate state where some \n\linecards have been upgraded and others have not. This message is to remind\n\the operator that a significant amount of time has passed waiting for \n\the operator to enter the next LC ISSU command. |
ha-issu-infra |
"Enter the next LC ISSU command to continue with\n\LC ISSU which includes commands to perform the operations of prepareversion \n\loadversion runversion acceptversion commitversion or abortversion" |
|
RLC_ISSU_PROCESS-5-RLC_ISSU_NOTIF |
5-Notice |
[chars] |
Linecard notification msg |
ha-issu-infra |
"No action needed" |
|
RLM-3-INIT |
3-Error |
rlm [dec]: [chars][chars]. |
RLM initialization operation fails. |
- |
LOG_STD_ACTION |
|
RLM-4-LINK |
4-Warning |
rlm [dec]: [chars][chars]. |
A warning is given out for a particular RLM link. |
- |
LOG_STD_DBG_ACTION |
|
RLM-4-NOBUF |
4-Warning |
rlm [dec]: cannot get packet buffer for [chars]. |
A rlm link cannot allocate a packet buffer. |
- |
LOG_STD_REDUCE_ACTION |
|
RM-3-BADACCT |
3-Error |
Unknown Accounting type [dec] flag [dec]. |
Get either invalid accounting type or flag |
resource-manager |
LOG_STD_ACTION |
|
RM-3-BADCALL |
3-Error |
Unexpected Call on [chars]. Current state is [dec]. |
A call came in on a line where we think we still have an active call. |
resource-manager |
LOG_STD_ACTION |
|
RM-3-BADRG |
3-Error |
Bad state rg \[chars]\: [dec] |
An internal software error. |
resource-manager |
LOG_STD_ACTION |
|
RM-3-BOUNDARY |
3-Error |
Memory boundary violation |
An internal software error. |
resource-manager |
LOG_STD_ACTION |
|
RM-3-NORESP |
3-Error |
No response-code from local RM |
An internal software error. |
resource-manager |
LOG_STD_ACTION |
|
RM-3-OUTOFBUFFS |
3-Error |
Out of buffers in RM event buffer queue |
An internal software error. |
resource-manager |
LOG_STD_ACTION |
|
RM-3-RGINFO |
3-Error |
[chars]: RG-info conversion failed [dec]. |
An internal software error. |
resource-manager |
LOG_STD_ACTION |
|
RM-3-WAVL |
3-Error |
Wavl error |
An internal software error. |
resource-manager |
LOG_STD_ACTION |
|
RM-3-ZEROVAL |
3-Error |
Uninitialized value being used |
An internal software error. |
resource-manager |
LOG_STD_ACTION |
|
RMFD-3-ERR_LOG |
3-Error |
[chars] |
RMFD Error has occured |
cbr-cmts-infra |
LOG_STD_NO_ACTION |
|
RMFD-4-WARN_LOG |
4-Warning |
[chars] |
Relay warning message |
cbr-cmts-infra |
LOG_STD_NO_ACTION |
|
RMFD-5-NOTICE_LOG |
5-Notice |
[chars] |
Relay notice message |
cbr-cmts-infra |
LOG_STD_NO_ACTION |
|
RMGR-3-OUT_OF_TCAM_IPV4_ROUTE |
3-Error |
Out of tcam resources to execute command |
Number of IPv4 routes installed exceeded supported scale |
firmware |
"Please reduce the number of IPv4 routes configured " "to supported scale" |
|
RMGR-3-OUT_OF_TCAM_IPV4_ROUTE |
3-Error |
Out of tcam resources to execute command |
Number of IPv4 routes installed exceeded supported scale |
asr903-cfc |
"Please reduce the number of IPv4 routes configured " "to supported scale. Clear the table to successfully" " reinstall all entries" |
|
RMGR-3-OUT_OF_TCAM_IPV4_ROUTE |
3-Error |
Out of tcam resources to execute command |
Number of IPv4 routes installed exceeded supported scale |
firmware |
"Please reduce the number of IPv4 routes configured " "to supported scale" |
|
RMGR-3-OUT_OF_TCAM_IPV4_ROUTE |
3-Error |
Out of tcam resources to execute command |
Number of IPv4 routes installed exceeded supported scale |
firmware |
"Please reduce the number of IPv4 routes configured " "to supported scale" |
|
RMGR-3-OUT_OF_TCAM_IPV6_ROUTE |
3-Error |
Out of tcam resources to execute command |
Number of IPv6 routes installed exceeded supported scale |
asr903-cfc |
"Please reduce the number of IPv6 routes configured " "to supported scale. Clear the table to successfully" " reinstall all entries" |
|
RMON-5-FALLINGTRAP |
5-Notice |
Falling threshold has been crossed because the value of [chars] has fallen below the falling-threshold value [dec] |
A Falling Event will be generated.The value of the specified\n\ MIB object has fallen below the falling threshold value as\n\ configured by the <CmdBold>rmon alarm<NoCmdBold> command for\n\ the specified object |
Check the behaviour of the specified MIB object and\n\ investigate the reason for the generation of the trap. |
"Take appropriate action on the specified MIB object." |
|
RMON-5-HCFALLINGTRAP |
5-Notice |
Falling trap is generated because the value of [chars] has fallen below\n\the falling-threshold hc value %llu |
A Falling Trap has been generated.The value of the specified\n\ MIB object has fallen below the falling threshold value as\n\ configured by the <CmdBold>rmon hc-alarms<NoCmdBold> command for\n\ the specified object |
Check the behaviour of the specified MIB object and\n\ investigate the reason for the generation of the trap. |
"Take appropriate action on the specified MIB object." |
|
RMON-5-HCRISINGTRAP |
5-Notice |
Rising trap is generated because the value of [chars] exceeded the\n\rising-threshold hc value %llu |
A Rising Trap has been generated.The value of the specified\n\ MIB object has exceeded the rising threshold value as configured by\n\ the <CmdBold>rmon hc-alarms<NoCmdBold> command for the specified object |
Check the behaviour of the specified MIB object under \n\ observation and investigate the reason for the generation\n\ of the trap. |
"Take appropriate action on the specified object." |
|
RMON-5-RISINGTRAP |
5-Notice |
Rising threshold has been crossed because the value of [chars] exceeded the rising-threshold value [dec] |
A Rising Event will be generated.The value of the specified\n\ MIB object has exceeded the rising threshold value as configured by\n\ the <CmdBold>rmon alarm<NoCmdBold> command for the specified object |
Check the behaviour of the specified MIB object under \n\ observation and investigate the reason for the generation\n\ of the trap. |
"Take appropriate action on the specified object." |
|
ROLLBACK_ISSU-2-GET_BUFFER |
2-Critical |
Rollback ISSU client failed to get buffer for message. Error: [dec] [chars] |
The Rollback 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. |
parser |
"show logging and show checkpoint client" |
|
ROLLBACK_ISSU-2-INIT |
2-Critical |
Rollback ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The Rollback 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. |
parser |
LOG_STD_ACTION |
|
ROLLBACK_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
Rollback ISSU client failed to send negotiation message. Error: [dec] [chars] |
The Rollback 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. |
parser |
"show logging and show checkpoint client" |
|
ROLLBACK_ISSU-2-SESSION_NEGO_FAIL_START |
2-Critical |
Failed to start Rollback ISSU session negotiation. Error: [dec] [chars] |
The Rollback ISSU client failed to start session negotition. If a problem occurs with the ISSU session start the standby device cannot be brought up properly. |
parser |
"show issu session <client_id>" |
|
ROLLBACK_ISSU-2-SESSION_REGISTRY |
2-Critical |
Rollback ISSU client failed to register session information. Error: [dec] [chars] |
The Rollback ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
parser |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ROLLBACK_ISSU-3-INVALID_SESSION |
3-Error |
Rollback ISSU client does not have a valid registered session. |
The Rollback ISSU client does not have a valid registered session. |
parser |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ROLLBACK_ISSU-3-MSG_NOT_OK |
3-Error |
Rollback ISSU client 'Message Type [dec]' is not compatible |
The Rollback ISSU client received an incompatible message from the peer device. The message cannot be processed. |
parser |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
ROLLBACK_ISSU-3-MSG_SIZE |
3-Error |
Rollback ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The Rollback ISSU client failed to calculate the MTU for the specified message. The Rollback ISSU client is not able to send the message to the standby device. |
parser |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
ROLLBACK_ISSU-3-SESSION_UNREGISTRY |
3-Error |
Rollback ISSU client failed to unregister session information. Error: [dec] [chars] |
The Rollback ISSU client failed to unregister session information. |
parser |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
ROLLBACK_ISSU-3-TRANSFORM_FAIL |
3-Error |
Rollback ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The Rollback 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 Rollback state between the active device and the standby device is not identical. |
parser |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
ROUTEMAP_IPC-2-NOMEMORY |
2-Critical |
Alloc fail for route-map ipc buffer |
Unable to malloc a buffer to send route-map configuration down to linecards. |
- |
"Enter a show chunks command and report the output along with" " this error message to your technical support representative." |
|
ROUTEMAP_IPC-2-ROUTEMAPNAMELENEXCEEDED |
2-Critical |
The length of route map name tag is too long |
The length of route map name tag is too long for IPC. The receiver has a 256 character long limit on route map name tag |
- |
"Use a route map name tag with the length of 256 or less characters" |
|
ROUTEMAP-4-BADTRACKOBJECTTYPE |
4-Warning |
can't track this type of object |
Route maps only support STATE type track objects. This object is not a STATE object |
routemap |
"Reconfigure the track object to make it a STATE object." |
|
RP_MLP-3-ADJ_FAIL |
3-Error |
Adjacency walk for [chars] failed |
Adjacency update for the specified multilink interface failed. |
vipmlp |
"Reset the multilink interface by entering the " "<CmdBold>shudown<NoCmdBold> command and then " "the <CmdBold>no shutdown<NoCmdBold> command on the interface. " "If traffic does not resume please collect the output of " "<CmdBold>show adjacency internal<NoCmdBold> and " "<CmdBold>show cef interface internal<NoCmdBold>. " LOG_STD_SH_TECH_ACTION |
|
RP_MLP-3-CFG_FAILED |
3-Error |
Config send to IM failed reason[dec] |
Configuration send to IM failed |
uea-im-tdm |
"" |
|
RP_MLP-3-INCOMPATIBLELINK |
3-Error |
The current config cannot be supported as link[chars] [chars] for bundle [chars] |
When using multilink 1 All the links should be from the same port. |
- |
" Please modify the config as not to violate the restrictions" |
|
RP_MLP-3-INCOMPATIBLELINK |
3-Error |
The current config cannot be supported as link[chars] [chars] for bundle [chars] |
When using multilink 1 All the links should be from the same port. |
uea-im-tdm |
" Please modify the config as not to violate the restrictions" |
|
RP_MLP-3-UNSUPPORTED_MULTILINK |
3-Error |
Multilink interface supported range is 1-65535. Removing Multilink. |
Multilink interface should be within 1-65535 else it is not supported |
vipmlp |
"Configure Multilink interface in the following range:1-65535" |
|
RP_MLP-3-UNSUPPORTED_SERVPOLICY |
3-Error |
Policy map configs will be removed from interface [chars] as it is not supported. |
Interface has unsupported service policy configurations |
- |
"Configure a valid Service Policy under the interface" |
|
RP_MLP-3-UNSUPPORTEDCONFIG |
3-Error |
The current config cannot be supported as [chars] for [chars] |
When using multilink 1 The maximum number of links in the bundle and number of bundles |
- |
" Please modify the config as not to violate the restrictions" |
|
RP_MLP-3-UNSUPPORTEDCONFIG |
3-Error |
The current config cannot be supported as [chars] for [chars] |
When using multilink 1 The maximum number of links in the bundle and number of bundles |
uea-im-tdm |
" Please modify the config as not to violate the restrictions" |
|
RP_MLP-4-BADLINKDECONFIG |
4-Warning |
Bad way of removing member link now perform 'no shut' on both sides of Multilink |
If member link has to be removed from multilink bundle first\n\ remove the multilink configuration from the member link and\n\ then perform no channel-group command on the controller. |
- |
"If the member link is removed from the multilink bundle using\n\ "no channel-group" command perform "no shut" on both sides\n\ of the multilink interface to make it work." |
|
RP_MLP-4-BADLINKDECONFIG |
4-Warning |
Bad way of removing member link now perform 'no shut' on both sides of Multilink |
If member link has to be removed from multilink bundle first\n\ remove the multilink configuration from the member link and\n\ then perform no channel-group command on the controller. |
uea-im-tdm |
"If the member link is removed from the multilink bundle using\n\ "no channel-group" command perform "no shut" on both sides\n\ of the multilink interface to make it work." |
|
RP_MLP-4-CHANGEQUEUEING |
4-Warning |
Change the queueing on the distributed multilink interface [chars] to FCFS |
When using multilink interface in distributed mode the queueing should be FCFS Please remove weighted fair or priority queueing. |
- |
" Please shut the multilink interface and unconfigure fair or priority" " queueing and then unshut the multilink interface" |
|
RP_MLP-4-DLFIATMSERVPOLIABS |
4-Warning |
priority service policy aabsent with DLFIoATM on ATM SPA on Bundle [chars] |
A priority service policy is needed for DLFIoATM on ATM-SPA to be able to do LFI on this interface. |
- |
"Please configure a priority service policy on the virtual template " "interface to enable the ATM SPA to do LFI." |
|
RP_MLP-4-DLFIONELINKSUPPORT |
4-Warning |
Only ONE link should be configured for dLFI bundle!! |
Trying to configure more than ONE link for dLFI bundle interface\n\ which is not supported by dLFIoFR and dLFIoATM. |
- |
"" |
|
RP_MLP-4-MISCONFIGLINK |
4-Warning |
Links across linecards or dCEF disabled giving control to RP |
Trying to add links to a bundle which are spread across linecards \n\ DMLP cant support this so giving control of bundle to RP. |
- |
"" |
|
RP_MLP-4-NODISTMLP |
4-Warning |
Failure downloading MLP bundle [chars] to the LC [dec] |
The bundle is configured to be distributed but for some reasons \n\ we cannot download the MLP config to the LCd. |
- |
"" |
|
RP_MLP-4-PANOTSUPPORTED |
4-Warning |
Adding Link from unsupported PA cant add giving control to RP |
Trying to add links to a bundle from a PA which is not supported\n\ by DMLP so giving control of bundle to RP. |
- |
"" |
|
RP_MLP-5-LEGACYCARD |
5-Notice |
Link[chars] added Bundle[chars] may not be distributed |
Link speed mismatch with other member links of the bundle. If this link become active bundle will not work in distributed mode |
- |
"" |
|
RP_MLP-5-LINKTYPEMISMATCH |
5-Notice |
Link[chars] added Bundle[chars] may not be distributed |
Link speed mismatch with other member links of the bundle. If this link become active bundle will not work in distributed mode |
- |
"" |
|
RP_MLP-5-LINKTYPEMISMATCH |
5-Notice |
Link[chars] cannot be added to Bundle[chars] |
Link speed mismatch with other member links of the bundle. |
- |
"" |
|
RP_MLP-5-SLOTMISMATCH |
5-Notice |
Link[chars] cannot be added to Bundle[chars] as [chars] |
Link should be on same slot as other member links of Bundle. If this link become active bundle will not work in distributed mode |
- |
"" |
|
RP_MLP-5-SLOTMISMATCH |
5-Notice |
Link[chars] cannot be added to Bundle[chars] as [chars] |
Link should be on same slot as other member links of Bundle. |
- |
"" |
|
RP_MLP-5-SPAWARNING |
5-Notice |
Feature support switching to LC based software for [chars] as [chars] |
A link was added to the bundle but it is not on the same bay as other member links of the bundle. The specified link that is not on the same bay has become active and the bundle has been switched to line card-based software support rather than the hardware mode that is supported on FREEDM. |
- |
"Ensure that when a link is added to a bundle " "that it is on the same bay as the other member " "links of the bundle in order to have the MLP " "bundle in hardware mode supported on FREEDM." |
|
RP_MLP-5-SPAWARNING |
5-Notice |
could not add link for bundle [chars] as [chars] |
A link was added to the bundle but it is not on the same bay as other member links of the bundle. |
- |
"Ensure that when a link is added to a bundle " "that it is on the same bay as the other member " "links of the bundle in order to have the MLP " |
|
RP_MLP-6-BAYMISMATCH |
6-Information |
Bay number in message [dec] received [chars] greater than max number [dec] |
Bay number in the message received exceeded max number of bays |
uea-im-tdm |
LOG_STD_RECUR_ACTION |
|
RP_MLP-6-INCOMPATIBLE_LINK_ADD |
6-Information |
Link [chars] added to [chars] belongs to a different bay |
Links added to the bundle must all belong to the same bay |
uea-im-tdm |
LOG_STD_RECUR_ACTION |
|
RPA-3-FLEXIBLE |
3-Error |
[chars] |
This message type is created for all those messages which\n\ have simple ASCII text and does not take any parameter.\n\ Message tells what the problem is. |
resource-grp-mgr |
LOG_STD_ACTION |
|
RPA-3-NO_CAS_ENTRY |
3-Error |
CAS Entry does not exist for slot: [dec] ctrl:[dec] channel:[dec] |
CAS entry does not exist for the given controller and channel. |
resource-grp-mgr |
LOG_STD_ACTION |
|
RPA-3-UNKNOWN_MSG |
3-Error |
Unknown message type [dec] enqueued to RPA CAS Process |
A message type which is not known to RPA CAS process is\n\ enqueued to it's queue. |
resource-grp-mgr |
LOG_STD_ACTION |
|
RPC-3-AUTH |
3-Error |
RPC missing authentication |
marshal_new_auth cannot authenticate |
rpc |
LOG_STD_NO_ACTION |
|
RPC-3-CACHEPERROR |
3-Error |
RPC cache perror: [chars] |
RPC Cache perror |
rpc |
LOG_STD_NO_ACTION |
|
RPC-3-CLNTPERROR |
3-Error |
RPC client perror: [chars] |
RPC Client perror |
rpc |
LOG_STD_NO_ACTION |
|
RPC-3-IOCTL |
3-Error |
RPC ioctl failed |
get_myaddress: ioctl failed |
rpc |
LOG_STD_NO_ACTION |
|
RPC-3-LSEEK |
3-Error |
RPC lseek called on a socket |
pxdrrec_getpos: This shouldn't happen |
rpc |
LOG_STD_NO_ACTION |
|
RPC-3-MALLOC |
3-Error |
RPC malloc failed |
malloc returned NULL |
rpc |
LOG_STD_NO_ACTION |
|
RPC-3-RECVFROM |
3-Error |
RPC recvfrom failed |
pmap_rmt: recvfrom failed: cannot receive broadcast message |
rpc |
LOG_STD_NO_ACTION |
|
RPC-3-SELECT |
3-Error |
RPC select failed |
RPC: cannot call select |
rpc |
LOG_STD_NO_ACTION |
|
RPC-3-SENDTO |
3-Error |
RPC sendto failed |
pmap_rmt: sendto failed: cannot send broadcast message |
rpc |
LOG_STD_NO_ACTION |
|
RPC-3-SETSOCKOPT |
3-Error |
RPC setsockopt failed |
pmap_rmt: setsockopt failed |
rpc |
LOG_STD_NO_ACTION |
|
RPC-3-SOCKET |
3-Error |
RPC can't create socket |
RPC cannot create a socket |
rpc |
LOG_STD_NO_ACTION |
|
RPC-3-SOCKNAME |
3-Error |
RPC can't call getsockname |
svc_create cannot call getsockname |
rpc |
LOG_STD_NO_ACTION |
|
RPC-3-XDRCALLHDR |
3-Error |
RPC fatal header serialization error |
clnt_raw - Fatal header serialization error |
rpc |
LOG_STD_NO_ACTION |
|
RPF-4-RADIXINIT |
4-Warning |
Error initializing the MVRF select radix tree |
An internal software error occurred. |
mcast-vpn |
LOG_STD_SH_TECH_ACTION |
|
RPF-4-RADIXINSERT |
4-Warning |
Error inserting a new entry into the MVRF select radix tree |
An internal software error occurred. |
mcast-vpn |
LOG_STD_SH_TECH_ACTION |
|
RPHY_DB-3-DB_HOG |
3-Error |
MSG_TRACEBACK | MSG_PROCESS |
- |
- |
- |
|
RPHY_DB-3-NEST_LOCK |
3-Error |
MSG_TRACEBACK | MSG_PROCESS |
- |
- |
- |
|
RPHY_DB-3-UNEXPECTED |
3-Error |
MSG_TRACEBACK | MSG_PROCESS |
- |
- |
- |
|
RPHY_DB-4-DB_STARVE |
4-Warning |
Waiting [chars] lock of <[chars]> for [dec] ms |
The IOSd process was waiting for the DB lock for too long |
rphy-infra |
LOG_STD_RPHY_DB_SUP_ACTION |
|
RPL-3-CHUNK_ERROR |
3-Error |
[chars] |
This Error message would be encountered when trying to 1. access chunk or chunk element when they are not valid. 2. lock failure on chunk element. |
rpl |
LOG_STD_ACTION |
|
RPL-3-CHUNK_ERROR |
3-Error |
[chars] |
This Error message would be encountered when trying to 1. access chunk or chunk element when they are not valid. 2. lock failure on chunk element. |
rpl |
LOG_STD_ACTION |
|
RPL-3-CONFIG_ERROR |
3-Error |
RPL [chars] configuration failed: [chars] [chars] code [dec] |
This Error message would be encountered when trying to configure rpl through api. |
rpl |
LOG_STD_ACTION |
|
RPL-3-CONFIG_ERROR |
3-Error |
RPL [chars] configuration failed: [chars] [chars] code [dec] |
This Error message would be encountered when trying to configure rpl through api. |
rpl |
LOG_STD_ACTION |
|
RPL-3-MALFORMEDMSG |
3-Error |
Malformed [chars] received from: %P |
This Error message would be encountered if a malformed RPL Control message is received |
- |
"Informational" |
|
RPL-3-MALFORMEDMSG |
3-Error |
Malformed [chars] received from: %P |
This Error message would be encountered if a malformed RPL Control message is received |
- |
"Informational" |
|
RPLIC-1-REGISTER_STORAGE |
1-Alert |
Register license storage [chars] failed rc [dec] [chars] |
The RP license storage register failed |
APPLICATION |
"Check the RP license details" " If the problem is not fixed by multiple reinstall" " attempts board RMA may be required" |
|
RPLIC-1-REGPERMSTORFAIL |
1-Alert |
Register license permanent storage [chars] failed rc [dec] [chars] |
The RP license storage register failed |
APPLICATION |
"Check the RP license details" " If the problem is not fixed by multiple reinstall" " attempts board RMA may be required" |
|
RPLIC-3-ACTIVATE |
3-Error |
Could not activate [chars] rc [dec] [chars] |
The RP license module activation failed |
APPLICATION |
LOG_STD_DDTS_TAC_DETAILS |
|
RPLIC-3-NULLHWIDB |
3-Error |
Can't get hwidb of slot [dec] port [dec] |
Failed to get hwidb of BH ethernet |
APPLICATION |
LOG_STD_DDTS_TAC_DETAILS |
|
RPLIC-3-REGISTER |
3-Error |
Could not register [chars] rc [dec] [chars] |
The RP license feature register failed |
APPLICATION |
LOG_STD_DDTS_TAC_DETAILS |
|
RPLIC-3-RELEASE |
3-Error |
Failed to release license handle 0x[hec] units [dec] rc [dec] [chars] |
The RP license feature release failed |
APPLICATION |
LOG_STD_DDTS_TAC_DETAILS |
|
RPLIC-3-REQUEST |
3-Error |
Failed to request license feature [chars] units [dec] rc [dec] [chars] |
The RP license feature request failed |
APPLICATION |
LOG_STD_DDTS_TAC_DETAILS |
|
RPLIC-3-STORAGE |
3-Error |
License storage error [chars] |
The RP license storage status is BAD |
APPLICATION |
"Check the RP license details. If the problem is not" " fixed by multiple reinstall attempts board RMA" " may be required" |
|
RPLIC-6-LICGRANT |
6-Information |
No license was granted for [chars] |
License wasn't granted for this TenGigaE |
APPLICATION |
"None" |
|
RPLIC-6-NOSHUT |
6-Information |
[chars] has been no shut |
License no shutdown TenGigaE |
APPLICATION |
"None" |
|
RPLIC-6-SHUT |
6-Information |
Can't noshut [chars] due to insufficient licenses |
Unable to no shut the TenGigaE due to insufficient licenses |
APPLICATION |
"Check number of licenses installed" |
|
RPS-3-DCOUTPUTVOLTFAIL |
3-Error |
System detected Redundant Power System DC Output Voltage failure condition. |
The Redundant Power System experienced a DC Output Voltage failure\n\ condition in one of the power supplies. |
- |
"One of the DC outputs has failed on the Redundant Power Supply. \n\ For 3600 and 2600 Redundant Power supplies "DC Status" LED on the front of \n\ the Power Supply will identify which DC output has failed. For 5300 Redundant\n\ Power Supply "DC OK" LED on the front of the Power Supply will identify \n\ which DC output has failed. When there is a DC failure you need to replace \n\ the Redundant Power Supply." |
|
RPS-3-DCOUTPUTVOLTOK |
3-Error |
Redundant Power System DC Output Voltage condition is now normal |
The Redundant Power System DC Output Voltage is normal. |
- |
"This is an informational message only. No action is required." |
|
RPS-3-FANFAIL |
3-Error |
System detected Redundant Power System FAN FAIL condition. |
The Redundant Power System experienced a Fan failure condition. |
- |
"One of the fans has failed and you should replace the Redundant Power \n\ Supply." |
|
RPS-3-FANOK |
3-Error |
Redundant Power System FAN condition is now normal. |
The Redundant Power System FAN is now normal. |
- |
"The Redundant Power Supply previously detected fan failure\n\ condition which has now cleared." |
|
RPS-3-INPUTVOLTFAIL |
3-Error |
System detected Redundant Power System Input Voltage failure condition. |
The Redundant Power System experienced an Input Voltage failure\n\ in one of the power supplies. |
- |
"One of the AC or DC inputs has failed on the Redundant Power Supply. \n\ For 3600 and 2600 Redundant Power supplies "AC Input" LED on the front \n\ of the Power Supply will identify which AC input has failed. For 5300\n\ AC<->DC Redundant Power Supply "AC OK" LED on the front of the\n\ Power Supply will identify which AC input has failed. For 5300 DC<->DC\n\ Redundant Power Supply "DC Input" LED on the front of the Power Supply \n\ will identify which DC input has failed. Make sure that the AC/DC circuit \n\ in your building is operational verify that the power cord is plugged \n\ into the Redundant Power Supply and make sure that the AC/DC power \n\ switch on the Redundant Power Supply is on." |
|
RPS-3-INPUTVOLTOK |
3-Error |
Redundant Power System Input Voltage condition is now normal |
The Redundant Power System Input Voltage is normal. |
- |
"This is an informational message only. No action is required." |
|
RPS-3-OVERTEMP_OK |
3-Error |
System temperature is now normal. |
The system is operating at a normal temperature. |
- |
"The system previously detected an over temperature condition\n\ which has now cleared. This is most likely due to high ambient \n\ temperature where the router is located." |
|
RPS-3-OVERVOLT |
3-Error |
Redundant Power System detected OVERVOLTAGE condition. |
The Redundant Power System detected OVERVOLTAGE condition. |
- |
"The Redundant Power System detected an over voltage condition." |
|
RPS-3-RPSOK |
3-Error |
Redundant Power System is now normal |
The Redundant Power System experienced multiple failures. This is a \n\ critical condition |
- |
"There are multiple failures on the Redundant Power Supply.\n\ Examine the LEDs on the front of the Redundant Power Supply to \n\ find out which failures it has." |
|
RPS-3-THERMAL |
3-Error |
System detected Redundant Power System THERMAL FAIL condition. |
The Redundant Power System experienced either a Fan failure\n\ or an Over Temperature condition. |
- |
"For 3600 and 2600 Redundant Power supplies look at the "FAN" and \n\ "TEMP" LEDs on the front of Power Supply. If the "FAN" LED is amber \n\ one of the fans has failed and you should replace the Redundant Power \n\ Supply. If the "TEMP" LED is amber the ambient temperature is too \n\ high. For 5300 RPS unit this message is displayed when the ambient\n\ temperature is too high." |
|
RPS-3-THERMOK |
3-Error |
Redundant Power System THERMAL condition is now normal. |
The Redundant Power System THERMAL is now normal. |
- |
"The Redundant Power Supply previously detected an over temperature \n\ condition which has now cleared. This is most likely due to high \n\ ambient temperature where the Redundant Power Supply is located. \n\ A Redundant Power System thermal failure can also be caused by a \n\ fan failure in the Redundant Power Supply." |
|
RPS-3-VOLTOK |
3-Error |
Redundant Power System VOLTAGE is now normal. |
The Redundant Power System voltage is now normal. |
- |
"The Redundant Power System previously detected an over voltage \n\ condition which has now cleared." |
|
RS_TDM-3-TDM_BACKPLANE_CLASH |
3-Error |
Clash in usage for TDM backplane timeslot [dec] |
The TDM backplane timeslot to be allocated is already in use |
as5800 |
"Check the split dial-shelf settings on both router shelves for conflicting setting" |
|
RS_TDM-3-TDM_BADARG |
3-Error |
A TDM function is used with a bad argument: [chars] |
An internal software error has occurred. A TDM function was called with invalid arguments and could not be processed. The invalid arguments are specified at the end of this error message along with any other useful data. |
as5800 |
"Enter the <CmdBold>debug tdm<NoCmdBold> command. If the problem " "recurs copy the error message the trace message and surrounding debug text " "exactly as they appear on the console or in the system log call your Cisco " "technical support representative and provide the representative with " "the gathered information." |
|
RS_TDM-3-TDM_CONFLICT |
3-Error |
TDM split user setting are in conflict: my RS [chars] = [dec] other RS [chars] = [dec] |
The user setting for tdm split on this router shelf is in conflict with the setting on the other router More backplane DS0 are in usethan 2048 DS0 |
as5800 |
"Set the other router dial-shelf split backplane-ds0 to non conflicting setting" |
|
RS_TDM-3-TDM_EXTEND_CLASH |
3-Error |
TDM extended split on Router shelf Clashes to my [chars] other [chars] extended backplane ds0 |
The number of extended backplane ds0 for this router clashes with the other router shelf |
as5800 |
"" |
|
RS_TDM-3-TDM_LEG_CLASH |
3-Error |
TDM legacy split on Router shelf Clashes to my [dec] other [dec] legacy backplane ds0 |
The number of legacy backplane ds0 for this router clashes with the other router shelf |
as5800 |
"" |
|
RS_TDM-3-TDM_NOT_SPLIT_PAIR |
3-Error |
TDM split user setting are not matched pairs my RS [chars] = [dec] ds0 expected other RS [chars] = [dec] ds0 actual other RS [chars] = [dec] ds0 |
The user setting for tdm split on this router shelf is not compatible with the setting on the other router |
as5800 |
"Set the other router dial-shelf split backplane-ds0 to above setting" |
|
RS_TDM-3-TDM_REDUCED_TDM_SPLIT |
3-Error |
TDM split on [chars] Router shelf Reduced to [dec] backplane ds0 |
The number of backplane ds0 for this router has been forced lower |
as5800 |
"" |
|
RS_TDM-3-TDM_UNKNOWN_TS_STATE |
3-Error |
TDM backplane timeslot [dec] is in an unknown state |
The TDM backplane timeslot specified is in an unknown state |
as5800 |
"Check the split dial-shelf settings on both router shelves for conflicting setting" |
|
RSCMSM-3-NO_LIST_CREATED |
3-Error |
\ [chars]: Cannot create interface-based rsc list. |
This failure is due to the list create operation. |
ios-mem |
"Please check the memory at the moment." |
|
RSCMSM-3-NO_SUCH_INTERFACE |
3-Error |
\ [chars]: The interface doesn't exist |
The interface for resource measurement doesn't exist at the time of the operation. |
call-treatment |
"Check the configuration to see if that interface is there" |
|
RSCMSM-5-TEST_ALREADY_RUNNING |
5-Notice |
\ One test is already running. |
there is already one test running at the same time. |
call-treatment |
"Please wait for the completeness of the running test before starting " "another test. " |
|
RSP_ISSU-2-IMG_DNLD_ERROR |
2-Critical |
[chars] |
This is a critical error message about an error that has occurred in Image Predownload while performing the ISSU operations in the system. A message of this type indicates that a failure has occurred during image predownload to VIP while performing an ISSU upgrade. |
issu-7500 |
"Copy the notice exactly as it appears. Check both the active system and " "standby system for messages. Call your technical support representative " "for assistance." |
|
RSP_ISSU-2-IMG_RCV_ERROR |
2-Critical |
[chars] |
This is a critical error message about an error that has occurred in Image Predownload while performing the ISSU operations in the system. A message of this type indicates that a failure has occurred during receiving the VIP image on the active RP while performing an ISSU upgrade. |
issu-7500 |
"Copy the notice exactly as it appears. Check both the active system and " "standby system for messages. Call your technical support representative " "for assistance." |
|
RSP_ISSU-2-IMG_SEND_ERROR |
2-Critical |
[chars] |
This is a critical error message about an error that has occurred in Image Predownload while performing the ISSU operations in the system. A message of this type indicates that a failure has occurred during sending the VIP image from standby RP while performing an ISSU upgrade. |
issu-7500 |
"Copy the notice exactly as it appears. Check both the active system and " "standby system for messages. Call your technical support representative " "for assistance." |
|
RSP_ISSU-2-IPC_ERROR |
2-Critical |
[chars] |
This is a critical error message about an error that has occurred in IPC communication while performing the ISSU operations in the system. A message of this type indicates that a failure has occurred during IPC communication while performing an ISSU upgrade. |
issu-7500 |
"Copy the notice exactly as it appears. Check both the active system and " "standby system for messages. Collect the output of " "<CmdBold>show ipc status<NoCmdBold>. Call your technical support " "representative for assistance and provide him with the information " "collected. " |
|
RSP_ISSU-2-IPC_PORTOPEN_ERROR |
2-Critical |
Failed to open \[chars]\ port. Reason=[chars] |
This is a critical error message about an error that has occurred in IPC communication while performing the ISSU operations in the system. A message of this type indicates that a failure has occurred during opening an IPC port while performing an ISSU upgrade. |
issu-7500 |
"Copy the notice exactly as it appears. Check both the active system and " "standby system for messages. Collect the output of " "<CmdBold>show ipc ports<NoCmdBold>. Call your technical support " "representative for assistance and provide him with the information " "collected. " |
|
RSP_ISSU-2-IPC_SEND_ERROR |
2-Critical |
Failed to send ISSU IPC message [dec] |
This is a critical error message about an error that has occurred in IPC communication while performing the ISSU operations in the system. A message of this type indicates that a failure has occurred during sending an IPC message while performing an ISSU upgrade. |
issu-7500 |
"Copy the notice exactly as it appears. Check both the active system and " "standby system for messages. Call your technical support representative " "for assistance." |
|
RSP_ISSU-3-GET_BUFFER |
3-Error |
[chars] ISSU Client session [dec] failed to get buffer |
RSP HA ISSU Client failed to get a buffer |
issu-7500 |
LOG_STD_REDUCE_ACTION |
|
RSP_ISSU-3-ISSU_CCB_FAIL |
3-Error |
[chars] [dec] |
RSP ISSU CCB Playback System Error. There was a Playback Error encountered in the CCB Playback on the Standby. |
issu-7500 |
"Copy the message exactly as it appears. Check both the active system " "and standby system for messages. Get the output with <CmdBold>debug " "issu ccb-playback<NoCmdBold> enabled and then call your technical " "support representative for assistance." |
|
RSP_ISSU-3-MSG_MTU |
3-Error |
[chars] ISSU Client [dec] get message MTU failed for message [dec]. |
RSP HA ISSU Client get message MTU Maximum Transmission Unit failed |
issu-7500 |
LOG_STD_ACTION |
|
RSP_ISSU-3-MSG_NOT_OK |
3-Error |
[chars] ISSU Client [dec] message type [dec] is not ok |
RSP HA ISSU Client message type has not negotiated correctly |
issu-7500 |
show issu message types <Client_ID> |
|
RSP_ISSU-3-MSG_SEND |
3-Error |
[chars] ISSU Client session [dec] failed to send message |
RSP HA ISSU Client failed to send negotiation message to peer |
issu-7500 |
LOG_STD_ACTION |
|
RSP_ISSU-3-RCV_XFORM_FAIL |
3-Error |
[chars] ISSU Client receive transformation has failed for message [dec] |
RSP HA ISSU Client message receive side transformation has failed |
issu-7500 |
LOG_STD_ACTION |
|
RSP_ISSU-3-SESSION_REG |
3-Error |
[chars] ISSU Client session [dec] registration failed |
RSP HA ISSU Client session registration failed |
issu-7500 |
show issu sessions <Client_ID> |
|
RSP_ISSU-3-SESSION_UNREG |
3-Error |
[chars] ISSU Client session [dec] un-registration failed |
RSP HA ISSU Client session un-registration failed |
issu-7500 |
show issu sessions <Client_ID> |
|
RSP_ISSU-3-VIP_MDR_FAILED |
3-Error |
Slot [dec] has failed to complete MDR. |
This message indicates a problem with minimal disruptive restart functionality on the VIP. The specified slot failed to complete MDR because of a checksum error or an internal crash. |
issu-7500 |
"Verify if the card in the specified slot supports " "MDR. Verify that the card is inserted properly. " "If condition persists gather the output of " "<CmdBold>show tech-support<noCmdBold>. Contact your " "technical support representative with the gathered" "information. " |
|
RSP_ISSU-3-VIP_MDR_NOSTART |
3-Error |
Slot [dec] Couldnt start MDR. |
This is an error message regarding the VIP minimal disruptive restart functionality. This message indicates that given slot has failed to start MDR. |
issu-7500 |
"please verify whether the card in the slot supports " "MDR and whether it is inserted properly in the box. " "Collect the output of <CmdBold>show tech-support<noCmdBold> " "and please call your technical support representative " "for assistance. " |
|
RSP_ISSU-3-XFORM_MALLOC_FAIL |
3-Error |
[chars] ISSU Client malloc [dec] has failed |
RSP HA ISSU Client cannot allocate memory for the data to be transformed and sent across to the peer. Most likely a resource problem within the system. |
issu-7500 |
LOG_STD_REDUCE_ACTION |
|
RSP_ISSU-3-XMIT_XFORM_FAIL |
3-Error |
[chars] ISSU Client transmit transformation has failed for message [dec] |
RSP HA ISSU Client message transmit side transformation has failed |
issu-7500 |
LOG_STD_ACTION |
|
RSP_ISSU-4-ISSU_NO_QUIESCE |
4-Warning |
linecard in slot [dec] is not ISSU quiesced. |
This is an informative message regarding the VIP minimal disruptive restart functionality. This error message indicates that the line card specified in the given slot will get reset during the ISSU process and there will be extended downtime during the upgrade process. |
issu-7500 |
"Please verify whether the line card in the given slot supports " "minimal disruptive restart as per the feature navigator tool. " "If it doesnt then no action is required. Otherwise " "please call your technical support representative " "for assistance. " |
|
RSP_ISSU-4-LC_RESET |
4-Warning |
linecard in slot [dec] will be reset during MDR |
This is an informative message regarding the VIP minimal disruptive restart functionality. This error message indicates that the line card specified in the given slot will get reset during the ISSU process and there will be extended downtime during the upgrade process. |
issu-7500 |
"Please verify whether the line card in the given slot supports " "minimal disruptive restart as per the feature navigator tool. " "If it doesnt then no action is required. Otherwise " "please call your technical support representative " "for assistance. " |
|
RSP_ISSU-5-IMG_DNLD_ABORTED |
5-Notice |
MDR Image download has been aborted. |
This is an informative message regarding the VIP minimal disruptive restart functionality. This message indicates that MDR image download has been aborted. |
issu-7500 |
"If you did not abort the download process gather the " "system messages that preceded this message to help " "the TAC representative diagnose the system condition. " |
|
RSP_ISSU-5-IMG_DNLD_COMPLETE |
5-Notice |
Slot [dec] has received MDR image successfully |
This is an informative message regarding the VIP minimal disruptive restart functionality. This message indicates that the line card specified in the given slot has completed image download. |
issu-7500 |
"The system is behaving normally. No action is required." |
|
RSP_ISSU-5-IMG_DNLD_DONE |
5-Notice |
Image Download process complete. |
This is an informative message regarding the VIP minimal disruptive restart functionality. This message indicates that the image predownload process has been completed. |
issu-7500 |
"The system is behaving normally. No action is required." |
|
RSP_ISSU-5-IMG_DNLD_STARTED |
5-Notice |
MDR Image download has started. |
This is an informative message regarding the VIP minimal disruptive restart functionality. This message indicates that MDR image download has started. |
issu-7500 |
"The system is behaving normally. No action is required." |
|
RSP_ISSU-5-IMG_RCV_DONE |
5-Notice |
Image has been received completely from standby. |
This is an informative message regarding the VIP minimal disruptive restart functionality. This message indicates that the image receive from standby RSP has been completed. |
issu-7500 |
"The system is behaving normally. No action is required." |
|
RSP_ISSU-5-IMG_SEND_DONE |
5-Notice |
Image Send to Active RP is complete |
This is an informative message regarding the VIP minimal disruptive restart functionality. This message indicates that the image send to active RSP has been completed. |
issu-7500 |
"The system is behaving normally. No action is required." |
|
RSP_ISSU-5-VIP_MDR_ABORTED |
5-Notice |
MDR has aborted on slot [dec]. |
This is an informative message regarding the VIP minimal disruptive restart functionality. This message indicates that given slot has aborted MDR preparations. This could have happened if the user has initiated a abortversion command. |
issu-7500 |
"If you did not abort the download process gather the " "system messages that preceded this message to help " "the TAC representative diagnose the system condition. " |
|
RSP_ISSU-5-VIP_MDR_FINISHED |
5-Notice |
Slot [dec] has finished doing MDR. |
This is an informative message regarding the VIP minimal disruptive restart functionality. This message indicates that given slot has finished MDR successfully. |
issu-7500 |
"The system is behaving normally. No action is required." |
|
RSP_ISSU-5-VIP_MDR_READY |
5-Notice |
Slot [dec] is ISSU quiesced and ready to do MDR. |
This is an informative message regarding the VIP minimal disruptive restart functionality. This message indicates that given slot has finished ISSU quiesce and is ready to perform MDR. |
issu-7500 |
"The system is behaving normally. No action is required." |
|
RSP_ISSU-5-VIP_MDR_STARTED |
5-Notice |
Slot [dec] has started doing MDR. |
This is an informative message regarding the VIP minimal disruptive restart functionality. This message indicates that given slot has started MDR successfully. |
issu-7500 |
"The system is behaving normally. No action is required." |
|
RSP_ISSU-6-ISSU_QUIESCED |
6-Information |
Slot [dec] is ISSU quiesced and it will be performing MDR |
The line card in the specified slot has been prepared for minimal disruptive restart. The card will be performing a minimal disruptive restart when a switchover occurs. |
issu-7500 |
"The system is behaving normally. No action is required." |
|
RSP-2-BADCACHE |
2-Critical |
Overrun detected.\n End of MEMD buffer : 0x[hec]\n End of datagram : 0x[hec]\n bufhdr [hec]: %08x %08x %08x %08x\n Flushing Processor Cache |
A packet was processed that was greater in size than the maximum possible MTU size or an illegal buffer header data area was found. |
- |
"Copy the error message exactly as it appears on the console or in the system log enter the show tech-support and show logging commands contact your Cisco technical support representative and provide the representative with the gathered information." |
|
RSP-2-NOMEMORY |
2-Critical |
No memory available for [chars] |
An attempt at memory allocation failed. |
- |
"Try these actions to remedy the problem: Add memory. Disable some features. Apply filtering to decrease the size of system data structures - the routing table for example. In general reduce other system activities to ease memory demands. If conditions warrant upgrade to a larger memory configuration." |
|
RSP-2-QADIAG |
2-Critical |
QA Diagnostic [chars] error at %#08x |
An error occurred during an attempt to access the RSP. |
- |
"Copy the error message exactly as it appears on the console or in the system log enter the show tech-support and show logging commands contact your Cisco technical support representative and provide the representative with the gathered information." |
|
RSP-2-QAERROR |
2-Critical |
[chars] error [chars] at addr %04x [chars]\n |
While the system was attempting to process a hardware queue an error was detected by the QA ASIC. The error could be either a zero link error or a reuse error. A zero link error is caused by an attempt to place in the hardware queue a buffer header with an address of 0x0. A reuse error occurs when the QA ASIC detects or attempts to place in the hardware queue a buffer header that is the same as another buffer header in another hardware queue.\n Either of these errors can occur because of a software or hardware problem with the RSP or a line card. |
- |
"Run the show logging command and see that whether any parity errors were recorded just before the QAERROR error message was received. If any parity error was recorded before the QAERROR a hardware error has occurred. 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. If no parity error was recorded and the problem recurs enter the show tech-support and show logging commands contact your Cisco technical support representative and provide the representative with the output of the commands." |
|
RSP-2-STALL |
2-Critical |
partially inserted or removed IPs on cyBus[dec] |
The RSP detected a stall condition of cbus. Most likely a board is not fully seated in the chassis. A less likely possibility is a hardware problem with the RSP or backplane. |
- |
"Try reseating the boards. Call your technical support representative for assistance if this message persists." |
|
RSP-3-ACCERROR |
3-Error |
[chars] acc %08x had bad value [dec] |
An incorrect value has been written on an accumulator. |
- |
"Copy the error message exactly as it appears and report it to your technical support representative. A micro reload can correct the error condition as a workaround." |
|
RSP-3-BADBUFHDR |
3-Error |
[chars] address [hec] |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
RSP-3-BADHWREV |
3-Error |
[chars] slot [dec] has wrong hardware revision [dec].[dec] |
The hardware in the indicated slot needs to upgraded for operation with the RSP. |
- |
"Upgrade the board." |
|
RSP-3-BADTURBOIPCMSG |
3-Error |
Bad Turbo IPC msg [chars]: msg=[hex] lastmsg=[hex] hdrsize=[hex] size=[hex] |
An error was discovered in an IPC message. |
- |
LOG_STD_ACTION |
|
RSP-3-BENGAL |
3-Error |
Bengal error. [chars] |
System controller Bengal has reported an error/event |
RSP |
"Read error reports. SBE are generally not fatal. Most others are" |
|
RSP-3-ERROR |
3-Error |
NULL |
An internal software error has occurred. The exact nature of the problem is described in the error message. |
- |
"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." |
|
RSP-3-FOREVER |
3-Error |
cmd [dec] to [chars] slot [dec] took [dec] usecs done [hec] |
A command from the RSP to an IP took longer for the system to process than expected. This condition may be caused by a heavily loaded CPU. |
- |
"If this error recurs copy the error message exactly as it appears on the console or in the system log enter the show tech-support and show logging commands contact your Cisco technical support representative and provide the representative with the gathered information." |
|
RSP-3-IDPROM |
3-Error |
Bad or missing ID EEPROM controller type [dec] |
The ID EEPROM on the RSP is missing or bad. |
- |
"This message indicates a manufacturing error. Report this error to your technical support representative." |
|
RSP-3-INVQPTR |
3-Error |
queue=[hex] bufhdr [hec]:\n %08x %08x %08x %08x |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
RSP-3-INVRTN |
3-Error |
Invalid return queue\n next=[hex] hwidb=[hex] type=[hex]\n queue_ptr=[hex] bufhdr_offset=[hex] id=[dec] bcast_id=[dec]\n bufhdr [hec]: %08x %08x %08x %08x |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
RSP-3-INVRTNBCASTID |
3-Error |
Invalid return queue bcast_id=[dec]\n bufhdr [hec]: %08x %08x %08x %08x |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
RSP-3-IP_PANIC |
3-Error |
Panic: [chars] %08x %08x %08x %08x |
The status message handler for the interface processor has detected that the firmware for the interface processor has experienced a critical condition. The name of the affected interface and the first four words of the status message buffer will be displayed along with the message for diagnostics |
- |
"Copy the error message exactly as it appears on the console or in the system log enter the show tech-support and show logging commands contact your Cisco technical support representative and provide the representative with the gathered information." |
|
RSP-3-IPC |
3-Error |
[chars] [chars] |
An IPC error has occurred. The exact nature of the problem is described in the error message. |
- |
"Copy the router configuration along with any other relevant information. 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." |
|
RSP-3-LOVEGIANT |
3-Error |
Card [chars] wants [dec] byte love letters but only got [dec] bytes |
An inconsistency between the microcode and the system code was detected. |
- |
"Report this error to your technical support representative." |
|
RSP-3-LOVENOTE |
3-Error |
[hec] corrupt: %08x %08x %08x %08x |
The event handler at the RSP has detected a status update message from an interface processor but the field in the status message that identifies the associated interface processor is not valid. This condition indicates that the status message is corrupted. This error could occur because of a hardware or a software problem.\n The address of the status message buffer and the first four words of the message will be displayed for diagnostic purposes. |
- |
"Copy the error message exactly as it appears on the console or in the system log enter the show tech-support and show logging commands contact your Cisco technical support representative and provide the representative with the gathered information." |
|
RSP-3-MSDOG |
3-Error |
Master/slave watchdog timed out |
While handling the interrupts from the DBUS FPGA the RSP has detected that the timeout bit in the interrupt status register has been set. This condition indicates that the master RSP no longer controls the CBUS and DBUS. The slave may become active during this time. So the rest of the interrupt handler will not be processed.\n This behavior could be the result of either a hardware or a software problem. |
- |
"Copy the error message exactly as it appears. If this problem recurs copy down the router's configuration along with any other relevant information such as the output of show tech-support and show logging commands. Contact your Cisco technical support representative for assistance and provide him with all the gathered information." |
|
RSP-3-MSFIX |
3-Error |
Fixing [chars] by setting to default [chars] |
The characters shown can be either on the slave RSP setting or on the master RSP setting. The ROM monitor default slave RSP setting is not synchronized with the system configuration file specifications. During bootup the system image detects the mismatch and modifies the ROM monitor setting to conform with these specifications. This mismatch most likely occurred because a new RSP was being installed and booted in a high system availability HSA environmentmsgdef_recommended_action Using the show version or show boot command |
- |
- |
|
RSP-3-MSVERS |
3-Error |
Master has m/s version [dec] slave has m/s version [dec] |
The master and slave are running incompatible software versions with regards to the master/slave exchange process. |
- |
"If the slave image global configuration is used to override the default slave image from the bundle then the slave image is incompatible. Update either the master or slave image to ensure the two are compatible. If the slave is running the image from the bundle execute and record the output of show version show running-config and show controller cbus commands. Report this information and the error message to your technical support representative." |
|
RSP-3-NOIDB |
3-Error |
bad vc [dec] on [chars] |
A chennelized interface driver received a packet on an unconfigured channel. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative along with the output of " "'show tech-support'." |
|
RSP-3-NOMAC |
3-Error |
Can't allocate MAC address for interface [dec]/[dec] |
No MAC address was available for allocation to the specified interface. |
- |
"Report this error to your technical support representative." |
|
RSP-3-NORELOAD |
3-Error |
reload command not allowed on standby RSP |
The <CmdBold>reload<NoCmdBold> command in exec mode is not allowed on thestandby RSP |
rsp |
"Enter the <CmdBold>slave reload<NoCmdBold> commandin exec mode." |
|
RSP-3-NORESTART |
3-Error |
[chars]: unable to schedule restart for output queue |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
RSP-3-NOSTART |
3-Error |
No microcode for [chars] card slot [dec] |
No microcode is defined or available for the specified card. |
- |
"Reconfigure the card to specify an existing microcode file." |
|
RSP-3-PA_INIT |
3-Error |
Malloc to [chars] failed for slot [dec] bay [dec] |
The information structure for the port adapter could not be created. The interfaces on the specified port adapter might no longer be functional. A possible reason for this is a memory allocation failure involving the port adapter. This can occur as a result of insufficient hardware memory or a memory leak. |
rsp |
"Please confirm that the recommended amount of memory is installed " "for the platform. If memory is adequate please get the output of " "<CmdBold>show process memory<NoCmdBold> over time to determine the " "process using increased memory. As an immediate possible solution " "please attempt to reseat the line card. If this condition persists " LOG_STD_SH_TECH_ACTION |
|
RSP-3-RESTART |
3-Error |
NULL |
The cBus buffer memory has been reset and reallocated. The exact nature of the problem is described in the error message. |
- |
- |
|
RSP-3-SLAVE_NVRAM_BUSY |
3-Error |
Slave NVRAM is temporarily busy |
Another process is temporarily locking the slave config. |
- |
"Retry the command that caused the error message. If the error message recurs check for other execs via the show users command. If you know that there are no other users locking the slave nvram then contact your technical support representative for assistance." |
|
RSP-3-SLAVECHANGE |
3-Error |
Slave changed state from [chars] to [chars] |
The slave RSP has undergone a hardware state change. Both the old state and new state are shown. Possible states are nonparticipant slave master unplugged Possible state changes indicated by the above message are any to unplugged unplugged to nonparticipant or slave nonparticipant to slave slave to nonparticipant Any other combination is unexpected. |
- |
- |
|
RSP-3-SLAVECOPYFAILED |
3-Error |
Copy of [chars] failed [chars]. |
- |
- |
- |
|
RSP-3-SLAVEMASTER |
3-Error |
Slave stole mastership |
The master RSP has detected that the slave RSP configuration was changed from slave to master. The old master RSP will reload and become the slave RSP allowing the new master RSP take over. This behavior indicates a software or hardware error. |
- |
"Copy the router configuration along with any other relevant information. Copy the error message exactly as it appears on the console or in the system log enter the show tech-support and show logging commands contact your Cisco technical support representative and provide the representative with the gathered information." |
|
RSP-3-XBUFHDR |
3-Error |
corrupt bufhdr [hec]: %08x %08x %08x %08x |
A miscommunication occurred between the RSP and an IP. |
- |
"Copy the error message exactly as it appears on the console or in the system log enter the show tech-support and show logging commands contact your Cisco technical support representative and provide the representative with the gathered information." |
|
RSP-4-COOKIE |
4-Warning |
Corrupt or missing MAC address cookie\n using random base [enet] |
This message indicates the part containing the MAC addresses allocated to this chassis could not be accessed or was found to be corrupt either due to a hardware problem or manufacturing problem. |
- |
"Report this error to your technical support representative." |
|
RSP-4-CRASHINFO |
4-Warning |
Error saving crashinfo for slot [dec]. Reason: [chars] |
A VIP crashinfo file has not been saved due to the indicated reason. |
rsp |
"If the reason indicates <CmdBold>Out of space" "<NoCmdBold> the bootflash may not have sufficient memory " "to save the crashinfo file. Otherwise open a case with " "the Technical Assistance Center via the Internet at " "www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl " "or contact your Cisco technical support representative " "and provide the representative with the information you " "have gathered. Attach the following information to your " "case in non-zipped plain-text .txt format: the output " |
|
RSP-4-DCEFSWITCHENABLE |
4-Warning |
DCEF switching should be enabled on member links of [chars] |
DCEF should be enabled for Multilink interfaces if required. |
- |
"Go to the multilink interface configuration mode using the <CmdBold>interface multilink multilink# <noCmdBold> command and then enable DCEF on the interface using <CmdBold> ip route-cache distributed<noCmdBold> as per your requirement" |
|
RSP-4-EMPTY_VIPBAYS |
4-Warning |
VIP in slot [dec] was empty and was disabled |
The system failed to copy the specified file to the standbyRSP. |
rsp |
"Ensure that the standby RSP exists and has enoughmemory for the file." |
|
RSP-4-HSA_MEM |
4-Warning |
size mismatch master [dec]MB slave [dec]MB |
Memory size mismatch between Master & Slave RSP. |
- |
"Configure both Master and Slave RSPs to have an equal amount of memory." |
|
RSP-4-HSA_MINMEM |
4-Warning |
[dec]MB required for HSA |
HSA requires a minimum of 24mb of memory. |
- |
"Upgrade your system to meet minimum memory requirements for HSA." |
|
RSP-4-RSPDRAM |
4-Warning |
Insufficient DRAM to adequately run this IOS version. [dec]M is recommended. |
The quantity of RSP DRAM is below the recommended amount. |
- |
"Add DRAM." |
|
RSP-4-SLAVENOTUPDATED |
4-Warning |
Slave configuration not updated for [chars]. |
The configuration on the slave cannot be synced with the master. |
- |
"Ensure that 'slave auto-sync config' is configured and that the slave is active" |
|
RSP-4-SLAVETIME |
4-Warning |
[chars] |
Report this error to your technical support representative. |
- |
- |
|
RSP-5-SLAVEUP |
5-Notice |
Slave changed to state Running Buffer memory state : [chars] |
This is an informational message to indicate that the slave RSP has started running the slave RSP image. This message after the router boots or after the slave reload global configuration command is issued on the master RSP. |
- |
"No action required." |
|
RSP-6-TXSTUCK |
6-Information |
Txacc of Interface [chars] is at [dec]%% of its txlimit |
The specified interface has a low txacc value. This might be a transient condition and harmless if it occurs in periods of high packet traffic. If it occurs more than once in periods of relatively moderate traffic it could indicate a problem Distributed packet switching might be disrupted as a result of this condition. |
RSP |
"If the message recurs during periods of relatively" "moderate traffic this might indicate disruption" "in distributed packet switching. If such a disruption" "occurs use a <CmdBold>microcode reload<NoCmdBold> to" "recover. Open a case with the Technical Assistance Center" "via the Internet at" "www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl" "or contact your Cisco technical support representative" "and provide the representative with the information you" "have gathered. Attach the following information to your" "case in non-zipped plain-text .txt format: the output" |
|
RSRB-3-BADVERSIONFST |
3-Error |
FSTin: [chars]: version mismatch mine [dec] theirs [dec] |
The remote end of a direct serial peer is running the wrong version of\n\ the system software. Either the local end the remote end or both are\n\ not up to date. |
- |
"Call your technical support representative for an update." |
|
RSRB-3-BADVERSIONIF |
3-Error |
IFin: [chars]: version mismatch mine [dec] theirs [dec] |
The remote end of a direct serial peer is running the wrong version of\n\ the system software. Either the local end the remote end or both are\n\ not up to date. |
- |
"Call your technical support representative for an update." |
|
RSRB-3-BADVERSIONTCP |
3-Error |
[chars]: [dec]/[inet]: version mismatch mine [dec] theirs [dec] |
The remote end of a TCP remote peer is running the wrong version of\n\ the system software. Either the local end the remote end or both are\n\ not up to date. |
- |
"Call your technical support representative for an update." |
|
RSRB-3-FSTERR |
3-Error |
[chars]: [chars]: [inet] op [hec] len [dec] trn [dec] |
The remote end of a direct serial RSRB connection detected a\n\ configuration problem or traffic that is not recognized by the\n\ configuration. |
- |
"Examine the configuration on both sides of the serial connection for\n\ possible problems. Examine the traffic being offered for propagation\n\ with respect to the configuration. The destination target ring is\n\ denoted by the value of trn." |
|
RSRB-3-HDRNOVRP |
3-Error |
Peer [inet] HDR no vrp |
An internal software error occurred. |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
RSRB-3-HDRVRP |
3-Error |
Peer [dec]/[inet] HDR vrp state wrong [dec] |
An internal software error occurred. |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
RSRB-3-IFERR |
3-Error |
[chars]: [chars]: [chars] op [hec] len [dec] trn [dec] |
The remote end of a direct serial RSRB connection detected a\n\ configuration problem or traffic that is not recognized by the\n\ configuration. |
- |
"Examine the configuration on both sides of the serial connection for\n\ possible problems. Examine the traffic being offered for propagation\n\ with respect to the configuration. The destination target ring is\n\ denoted by the value of trn." |
|
RSRB-3-NOMEMORY |
3-Error |
Unit [dec] no memory for [chars] |
The requested operation could not be accomplished because of a low\n\ memory condition. |
- |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
RSRB-3-NOTREM |
3-Error |
Null idb and not remote |
An internal software error occurred. |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
RSRB-3-SENDPUNTFST |
3-Error |
[chars]: sent [chars] to [chars] |
The local end of a direct serial RSRB connection detected a\n\ configuration problem or traffic that is not recognized by the\n\ configuration. |
- |
"Examine the configuration on both sides of the serial connection for\n\ possible problems. Examine the traffic being offered for propagation\n\ with respect to the configuration." |
|
RSRB-3-SENDPUNTIF |
3-Error |
[chars]: sent [chars] to [chars] |
The local end of a direct serial RSRB connection detected a\n\ configuration problem or traffic that is not recognized by the\n\ configuration. |
- |
"Examine the configuration on both sides of the serial connection for\n\ possible problems. Examine the traffic being offered for propagation\n\ with respect to the configuration." |
|
RSRB-4-BADLEN |
4-Warning |
Peer [chars] [chars] bad length [dec] trn [dec] |
An internal software error occurred. |
- |
"If either message recurs call your technical support representative\n\ for assistance." |
|
RSRB-4-BADLENIP |
4-Warning |
Peer [dec]/[inet] [chars] bad length [dec] trn [dec] |
An internal software error occurred. |
- |
"If either message recurs call your technical support representative\n\ for assistance." |
|
RSRB-4-BADVRE |
4-Warning |
Bad vre type |
An internal software error occurred. |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
RSRB-4-CONIPST |
4-Warning |
Peer [dec]/[inet] CONN illegal state [dec] |
An internal software error occurred. |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
RSRB-4-CONNILLSTATE |
4-Warning |
Peer [chars] CONN illegal state [dec] |
An internal software error occurred. |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
RSRB-4-CONNSTAT |
4-Warning |
Peer [chars] IFin bad connection state [dec] |
An internal software error occurred. |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
RSRB-4-HDRRECV |
4-Warning |
Peer [dec]/[inet] HDR recv state invalid not empty [dec] |
An internal software error occurred. |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
RSRB-4-ILLPEER |
4-Warning |
Peer [chars] [%-08x] illegal state [dec] |
An internal software error occurred. |
- |
"If either of these messages recur call your technical support\n\ representative for assistance." |
|
RSRB-4-LOCAL |
4-Warning |
Unit [dec] local/vring set simultaneously vrn [dec] |
An internal software error occurred. |
- |
"If either of these messages recur call your technical support\n\ representative for assistance." |
|
RSRB-4-OPTNULL |
4-Warning |
Remopened and t NULL |
An internal software error occurred. |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
RSRB-4-PEERSTAT |
4-Warning |
Peer [chars] wrong state [dec] |
An internal software error occurred. |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
RSRB-4-RNGXFAIL |
4-Warning |
Ring exchange failure resetting peer: [chars] |
The RSRB peer initiation logic failed due to a memory shortage or\n\ congestion condition. |
- |
"The problem should clear and the peers should re-open without operator\n\ intervention." |
|
RSVP_SYNC_ISSU-2-GET_BUFFER |
2-Critical |
RSVP_SYNC ISSU client failed to get buffer for message. Error: [dec] [chars] |
The RSVP_SYNC 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. |
rsvp-sync |
"show logging and show checkpoint client" |
|
RSVP_SYNC_ISSU-2-INIT |
2-Critical |
RSVP_SYNC ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The RSVP_SYNC 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. |
rsvp-sync |
LOG_STD_ACTION |
|
RSVP_SYNC_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
RSVP_SYNC ISSU client failed to send negotiation message. Error: [dec] [chars] |
The RSVP_SYNC 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. |
rsvp-sync |
"show logging and show checkpoint client" |
|
RSVP_SYNC_ISSU-2-SESSION_NEGO |
2-Critical |
RSVP_SYNC ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The RSVP_SYNC 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. |
rsvp-sync |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
RSVP_SYNC_ISSU-2-SESSION_REGISTRY |
2-Critical |
RSVP_SYNC ISSU client failed to register session information. Error: [dec] [chars] |
The RSVP_SYNC ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
rsvp-sync |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
RSVP_SYNC_ISSU-3-CAP_INVALID_SIZE |
3-Error |
RSVP_SYNC ISSU client capability list is empty. |
The RSVP_SYNC ISSU client capability exchange list size is invalid. |
rsvp-sync |
"show issu capability entires <Client_ID>" |
|
RSVP_SYNC_ISSU-3-CAP_NOT_COMPATIBLE |
3-Error |
RSVP_SYNC ISSU client capability exchange result incompatible. |
The RSVP_SYNC ISSU client capability exchange have negotiated as incompatible with the peer. |
rsvp-sync |
"show issu negotiated capability <Session_ID>" |
|
RSVP_SYNC_ISSU-3-INVALID_SESSION |
3-Error |
RSVP_SYNC ISSU client does not have a valid registered session. |
The RSVP_SYNC ISSU client does not have a valid registered session. |
rsvp-sync |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
RSVP_SYNC_ISSU-3-MSG_NOT_COMPATIBLE_WITH_PEER |
3-Error |
'Message Type [dec]' is not supported by RSVP_SYNC ISSU client at peer |
The RSVP_SYNC ISSU client at the peer supervisor is not compatible for this message type. The RSVP_SYNC client will be marked as incompatible with the peer. |
rsvp-sync |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
RSVP_SYNC_ISSU-3-MSG_NOT_OK |
3-Error |
RSVP_SYNC ISSU client 'Message Type [dec]' is not compatible |
The RSVP_SYNC ISSU client received an incompatible message from the peer device. The message cannot be processed. |
rsvp-sync |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
RSVP_SYNC_ISSU-3-MSG_SIZE |
3-Error |
RSVP_SYNC ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The RSVP_SYNC ISSU client failed to calculate the MTU for the specified message. The RSVP_SYNC ISSU client is not able to send the message to the standby device. |
rsvp-sync |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
RSVP_SYNC_ISSU-3-SESSION_UNREGISTRY |
3-Error |
RSVP_SYNC ISSU client failed to unregister session information. Error: [dec] [chars] |
The RSVP_SYNC ISSU client failed to unregister session information. |
rsvp-sync |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
RSVP_SYNC_ISSU-3-TRANSFORM_FAIL |
3-Error |
RSVP_SYNC ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The RSVP_SYNC 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 RSVP_SYNC state between the active device and the standby device is not identical. |
rsvp-sync |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
RSVP-1-RSVP_AUTH_NO_KEYS_LEFT |
1-Alert |
No valid keys left for [inet] |
The router attempted to use a key in an RSVP key chain but discovered\n\ that all the keys in the chain have expired and no other per-neighbor\n\ or per-interface keys are available for the specified neighbor. The\n\ router will continue to use the last key in the chain rather than\n\ revert to an unauthentication condition. However the specified neighbor\n\ router may start discarding RSVP messages at that point and reservations\n\ with that neighbor may eventually time out. |
rsvp |
- |
|
RSVP-2-RSVP_AUTH_KEY_CHAIN_EXPIRED |
2-Critical |
All the keys in chain [chars] have expired - please update the key chain now |
The router attempted to use a key in an RSVP key chain but discovered\n\ that all the keys in the chain have expired. The router will attempt to\n\ to find another suitable key. If no other suitable per-neighbor key can\n\ be found the router will attempt to use key chain configured for the\n\msgdef_recommended_action Update the key chain by updating the text and expiration time |
- |
- |
|
RSVP-3-BAD_RMSG_TIMER |
3-Error |
Inconsistent RSVP reliable message timer |
An error was encountered during validation of the objects in an RSVP \n\ message received by the router. |
rsvp |
LOG_BAD_RSVP_MSG_ACTION LOG_STD_RSVP_ACTION |
|
RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_COOKIE |
3-Error |
[chars] message from [inet] discarded - challenge failed for key ID %*s |
The router sent an RSVP message to challenge the untrusted source to\n\ compute a secure hash on a random piece of data and return the hash\n\ with the same data but the source did not return the expected data.\n\ RSVP discarded the response because the untrusted source may be\n\ unsuccessfully attempting an RSVP challenge response replay attack. |
rsvp |
- |
|
RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_DIGEST |
3-Error |
[chars] message from [inet] discarded - incorrect message digest |
The router received an RSVP message that contained a different secure\n\ hash from the one computed by the router. RSVP discarded the message\n\ because the message may have come from an untrusted source. |
rsvp |
"Check the configuration on the router and the sending system to make\n\ sure they are using the correct security key and secure hash algorithm." |
|
RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_DUP |
3-Error |
[chars] message from [inet] discarded - authentication seq #%llu is a duplicate |
The router received an RSVP message with an authentication sequence\n\ number that has already been seen. RSVP discarded the message because an\n\ untrusted source may be unsuccessfully attempting an RSVP message\n\msgdef_recommended_action If you can verify that the source is trusted |
- |
- |
|
RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_NO_SA |
3-Error |
[chars] message from [inet] discarded: no security association for [inet] - no RSVP security key configured or no memory left. |
The router received an RSVP message that contained a secure hash but\n\ dropped the message because the router was not able to create a security\n\ association for the sending system. |
rsvp |
"Check the configuration on the router to make sure that RSVP has access\n\ to a security key for the sending system. If such a key is configured\n\ then check to see if the router has run out of memory." |
|
RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_WIN |
3-Error |
[chars] message from [inet] discarded - seq #%llu outside authentication window |
The router received an RSVP message whose authentication sequence number\n\ is less than the lower limit of the out-of-order window. RSVP discarded\n\ the message because an untrusted source may be unsuccessfully\n\msgdef_recommended_action It is possible that a trusted source is sending a burst of reordered\n\ RSVP messages that is too large for the authentication window size. If\n\ you can verify that the source is trusted and its messages are being sent\n\ in large reordered bursts |
- |
- |
|
RSVP-3-BAD_RSVP_MSG_RCVD_CHECKSUM |
3-Error |
RSVP Message had a bad checksum: [dec] foo: [dec] |
The router received an RSVP message with the checksum field incorrectly\n\ set. Bad checksums would most likely be caused by packet corruption \n\ outside RSVP. Be aware that corruption reported by RSVP might also be\n\ affecting other protocols on the router and might explain other \n\ unexpected non-RSVP protocol behavior. Please attempt to track down the \n\ source of the corruption. |
rsvp |
LOG_BAD_RSVP_MSG_ACTION LOG_STD_RSVP_ACTION |
|
RSVP-3-BAD_RSVP_MSG_RCVD_OBJ_LEN |
3-Error |
Received a bad RSVP message num objs: [dec] obj len: [dec] msg_len: [dec] |
An error was encountered during validation of the objects in an RSVP \n\ message received by the router. The number of objects in the RSVP message \n\ was found to be greater than the maximum expected number or the size of\n\ an object was found to be smaller than the minimum expected size. |
rsvp |
LOG_BAD_RSVP_MSG_ACTION LOG_STD_RSVP_ACTION |
|
RSVP-3-BAD_RSVP_MSG_RCVD_TYPE |
3-Error |
RSVP Message had a bad type: [dec] |
The router received an incorrect RSVP message. |
rsvp |
"Copy the error message exactly as it appears on the console\n\ or in the system log. Issue the <CmdBold>show tech-support rsvp\n\ <NoCmdBold> command to gather data which may help identify the\n\ nature of the error. Then send this information to your Cisco\n\ technical support representative." |
|
RSVP-3-BAD_RSVP_MSG_RCVD_VER |
3-Error |
RSVP Message had a bad version: [dec] |
The router received an RSVP message with the version field set to an\n\ unexpected value. |
rsvp |
LOG_BAD_RSVP_MSG_ACTION LOG_STD_RSVP_ACTION |
|
RSVP-3-CONSISTENCY |
3-Error |
[chars]: [chars] [chars] [chars] |
An action attempted by the rsvp implementation encountered\n\ an unexpected condition |
rsvp |
"Copy the error message exactly as it appears on the console\n\ or in the system log. Issue the <CmdBold>show tech-support rsvp\n\ <NoCmdBold> command to gather data which may help identify the\n\ nature of the error. Then send this information to your Cisco\n\ technical support representative." |
|
RSVP-3- IP_HDR |
3-Error |
%08x %08x %08x %08x %08x %08x %08x %08x |
This is an auxiliary message to several packet-related messages. It\n\ displays the contents of 8 32-bit words immediately following the start \n\ of the IPv4/v6 header in hex format. To decode the information in the\n\ IPv4 and IPv6 headers please refer to RFCs 791 and 2460. |
rsvp |
"Decode the information in the IPv4 and IPv6 headers to determine the\n\ source of the RSVP message." |
|
RSVP-3- MSG_1 |
3-Error |
%08x %08x %08x %08x %08x %08x %08x %08x |
This is an auxiliary message to several packet-related messages. It\n\ displays the contents of the first 8 32-bit words immediately following\n\ the start of the RSVP header in hex format. To decode the \n\ information in the RSVP header please refer to RFC 2205. |
rsvp |
"If you need additional information about the packet then turn on\n\ <CmdBold>debug ip rsvp dump-messages <msg type> [hex]<NoCmdBold> and try\n\ to capture the bad message. If you use the hex version of this command \n\ you can convert it to pcap format with the offline tool text2pcap and \n\ then view the contents with another offline tool such as ethereal." |
|
RSVP-3- MSG_2 |
3-Error |
%08x %08x %08x %08x %08x %08x %08x %08x |
This is an auxiliary message to several packet-related messages. It\n\ displays the contents of the next 8 32-bit words following those that \n\ are printed by the MSG_1 message above in hex format. To decode\n\ the information in these 32-bit words please refer to RFC 2205. |
rsvp |
"If you need additional information about the packet then turn on\n\ <CmdBold>debug ip rsvp dump-messages <msg type> [hex]<NoCmdBold> and try\n\ to capture the bad message. If you use the hex version of this command \n\ you can convert it to pcap format with the offline tool text2pcap and \n\ then view the contents with another offline tool such as ethereal." |
|
RSVP-3-RSVP_MFI_RECOVERY |
3-Error |
RSVP calculated Recovery Time is longer than TE Rewrite Hold-Time registered with LSD. Some LSPs may not be be recovered. |
TE registered a maximum cutover time with the LSD that is less than\n\ the time it may actually take to recover all LSPs. As a result more\n\ than usual traffic loss may occur on some LSPs during recovery |
rsvp |
"Make note of the number of Checkpointed LSPs in the RSVP HA database by\n\ issuing the command <CmdBold>show ip rsvp high-availability database\n\ internal <NoCmdBold>. This number likely exceeds the hard defined limit\n\ of the number of recoverable LSPs. Provide this information to Cisco\n\ technical support representative." |
|
RSVP-3-RSVP_MSG_AUTH_CHALLENGE_TIMEOUT |
3-Error |
No response to challenge issued to [inet] for key ID %*s |
The router sent an RSVP message to challenge the untrusted source to\n\ compute a secure hash on a random piece of data and return the hash\n\ with the same data but the source did not reply. The source may\n\ have crashed or lost its network connection. However it is also\n\ possible that the source was unsuccessfully attempting to replay\n\msgdef_recommended_action If you can verify that the source is trusted |
- |
- |
|
RSVP-3-RSVP_MSG_AUTH_TYPE_MISMATCH |
3-Error |
[chars] message from [inet] discarded - authentication algorithm mismatch |
The router received an RSVP message from a source that required\n\ authentication but the received message was using the wrong\n\ authentication algorithm. |
rsvp |
"Issue a <CmdBold>show ip rsvp authentication detail <source><NoCmdBold>\n\ command on the router to display the expected algorithm type. Then find\n\ the source and change its configuration to match." |
|
RSVP-4-RSVP_AUTH_DUPLICATE_KEY_ID |
4-Warning |
Key chains [chars] and [chars] contain duplicate key ID [dec] |
An attempt is being made to add a new key identifier to a key chain in\n\ the router configuration but RSVP detected that this identifier is found\n\ in another key chain already assigned to RSVP. Since key identifiers must\n\ be unique across all the key chains used by RSVP RSVP will not use the\n\ keys with this identifier in all such key chains. This could cause RSVP\n\ authentication to fail in some cases. |
rsvp |
"Update the listed key chains so they use different key identifiers." |
|
RSVP-5-CLEAR_COUNTERS |
5-Notice |
Clear RSVP message counters by [chars] |
The RSVP message counters have been cleared |
rsvp |
LOG_STD_NO_ACTION |
|
RSVP-5-NO_MATCH_IF_ID_HOP |
5-Notice |
Received PATH [inet]_[dec]->[inet]_[dec] - |
The interface id in the HOP object does not match any of this node's interfaces. |
rsvp |
"Verify the configuration." |
|
RSVP-5-RSVP_AUTH_KEY_ACL_CHANGE |
5-Notice |
Key chain [chars] [chars] for [inet] because ACL \[chars]\ [chars] |
The ACL specified in the message text associates the key chain specified\n\ in the message text with a set of RSVP neighbors. RSVP uses the specified\n\ key chain to authenticate each RSVP message exchanged with that set of\n\ RSVP neighbors after the association is configured. Subsequently the\n\ specified ACL has been reconfigured such that the key chain association\n\ is no longer valid for one or more RSVP neighbors in the set. This causes\n\ RSVP to search the configuration for another suitable key chain to use\n\ with those neighbors. If no such key chain is found RSVP will no longer\n\ be able to provide authentication for messages exchanged with those RSVP\n\ neighbors. This causes RSVP to discard RSVP messages from that set of\n\ neighbors. Because this may ultimately lead to loss of RSVP functionality\n\ with those neighbors RSVP generates this system message. This system\n\ message may also be generated if the ACL is subsequently changed so that\n\ it re-associates RSVP neighbors with the specified key chain. If RSVP is\n\ not using another key chain for the set of RSVP neighbors specified by\n\ the ACL RSVP will begin using the specified key chain to exchange\n\ authenticated RSVP messages with that set of RSVP neighbors potentially\n\ restoring RSVP functionality with those neighbors. |
rsvp |
"If the ACL change unexpectedly caused authentication to be disabled\n\ or enabled for one or more RSVP neighbors undo the ACL change so that\n\ RSVP authentication is not impacted." |
|
RSVP-5-RSVP_AUTH_ONE_KEY_EXPIRED |
5-Notice |
Key ID [dec] in chain [chars] has expired |
- |
- |
- |
|
RTMGR-3-GENERAL |
3-Error |
[chars] |
An internal software error occurred. |
RTMGR_DDTS_COMPONENT |
LOG_STD_RECUR_ACTION |
|
RTMGR-3-TOPO_AF_ENABLE_ERR |
3-Error |
Failed to enable AF base topology [chars] error [chars] |
An internal software error occurred. |
RTMGR_DDTS_COMPONENT |
LOG_STD_RECUR_ACTION |
|
RTMGR-3-TOPO_AFI_CTX |
3-Error |
Topology address-family [chars] context block is NULL. |
An internal software error occurred. |
RTMGR_DDTS_COMPONENT |
LOG_STD_RECUR_ACTION |
|
RTMGR-3-TOPO_CACHE_ADD_ERROR |
3-Error |
[chars] |
cached topo entry creation failure |
RTMGR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
RTMGR-3-TOPO_CACHE_ERROR |
3-Error |
[chars] |
cached topo failure |
RTMGR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
RTMGR-3-TOPO_CACHE_INIT_ERROR |
3-Error |
[chars] |
cached topo initialization failure |
RTMGR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
RTMGR-3-TOPO_HA_LOCK_IVRF_TOPO |
3-Error |
Acquired a HA lock on an iVRF topology[chars] |
Topology HA lock shouldn't be applied in an iVRF topology |
RTMGR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
RTMGR-3-TOPO_INTF_CTX |
3-Error |
Interface [chars] address-family [chars] topology context is NULL or the function [chars] is not set |
An internal software error occurred. |
RTMGR_DDTS_COMPONENT |
LOG_STD_RECUR_ACTION |
|
RTMGR-3-TOPO_INTF_INV_VRFID |
3-Error |
Interface [chars] with invalid vrfid 0x[hec] |
An internal software error occurred. |
RTMGR_DDTS_COMPONENT |
LOG_STD_RECUR_ACTION |
|
RTMGR-3-TOPO_IPMCAST_BASE_ERR |
3-Error |
Failed to create the base mcast topology in vrf [chars] with error [chars] |
An internal software error occurred. |
RTMGR_DDTS_COMPONENT |
LOG_STD_RECUR_ACTION |
|
RTMGR-3-TOPO_LCKMGR_GET_LOCK_COUNT_ERROR |
3-Error |
Failed to get lock count for topology[chars] |
Topology lock manager get lock count failure |
RTMGR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
RTMGR-3-TOPO_LCKMGR_INIT_ERROR |
3-Error |
[chars] manager init failure |
Topology lock manager initialization failure |
RTMGR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
RTMGR-3-TOPO_PROCESS_INIT_ERROR |
3-Error |
Topology process init failed due to [chars] |
Topology process initialization failed |
RTMGR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
RTMGR-3-TOPO_SUBMODE_ERROR |
3-Error |
Unexpected transition from parser submode '[chars]' |
An error occured while parsing the topology command |
RTMGR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
RTMGR-3-TOPO_SYNC_ERR |
3-Error |
Failed to duplicate active topology on standby rc=[dec] id [hec] [chars] |
An internal software error occurred. |
RTMGR_DDTS_COMPONENT |
LOG_STD_RECUR_ACTION |
|
RTMGR-3-TOPO_UNSUPPORTED_AFI |
3-Error |
Attempt to enable unsupported AFI 0x%X |
An internal software error occurred. |
RTMGR_DDTS_COMPONENT |
LOG_STD_RECUR_ACTION |
|
RTMGR-3-TOPO_UNSUPPORTED_API |
3-Error |
Topology API [chars] is unsupported due to [chars] |
Topology API is unavailable |
RTMGR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
RTMGR-3-TOPO_VRF_ERR |
3-Error |
Topology [chars] address-family [chars] has no VRF entry |
An internal software error occurred. |
RTMGR_DDTS_COMPONENT |
LOG_STD_RECUR_ACTION |
|
RTMGR-3-UNLOCK_ERR |
3-Error |
Attempt to unlock active topology '[chars]' in VRF [chars] [chars] |
An internal software error occurred. |
RTMGR_DDTS_COMPONENT |
LOG_STD_RECUR_ACTION |
|
RTMGR-3-VRF_ERR |
3-Error |
Topology VRF [chars] creation error |
An internal software error occurred. |
RTMGR_DDTS_COMPONENT |
LOG_STD_RECUR_ACTION |
|
RTREE-3-ALLOC_FAIL |
3-Error |
aux [hec] |
A Radix Tree request has caused an out of memory condition |
cpp-ucode |
LOG_STD_ACTION |
|
RTSP_ALG-3-CHUNK_CREATE_FAIL |
3-Error |
- |
Chunk create failed. RTSP ALG will not be able to finish initialization. |
cpp-ucode |
LOG_STD_ACTION |
|
RTSP_ALG-3-CREATE_CALLBACK_ERROR |
3-Error |
- |
Missing L7 data during imprecise channel creation callback. |
cpp-ucode |
LOG_STD_ACTION |
|
RTSP_ALG-3-INCOMPATIBLE_HA_MSG_LEN |
3-Error |
rcvd:[hec] expect:[hec] |
Incompatible HA Message Length. RTSP ALG will reject sync data. |
cpp-ucode |
LOG_STD_ACTION |
|
RTSP_ALG-3-INCOMPATIBLE_HA_VERSION |
3-Error |
rcvd:[hec] expect:[hec] |
Incompatible HA Version. RTSP ALG will reject sync data. |
cpp-ucode |
LOG_STD_ACTION |
|
RTSP_ALG-3-INCORRECT_HA_MAGIC |
3-Error |
rcvd:[hec] expect:[hec] |
Incorrect HA MAGIC. RTSP ALG will reject sync data. |
cpp-ucode |
LOG_STD_ACTION |
|
RTSP_ALG-3-INVALID_HA_OPCODE |
3-Error |
rcvd:[hec] expect:[hec] |
Invalid HA opcode. RTSP ALG will reject sync data. |
cpp-ucode |
LOG_STD_ACTION |
|
RTSP_ALG-3-L7_DATA_CREATE_ERROR |
3-Error |
- |
Error during L7 data creation. |
cpp-ucode |
LOG_STD_ACTION |
|
RTSP_ALG-3-WRITEBACK_ERROR |
3-Error |
- |
Error during writeback. |
cpp-ucode |
LOG_STD_ACTION |
|
RTT-3-AUTO |
3-Error |
Error: [chars] |
An error occured while generating IPSLAs Auto operation. |
rsps-time-rptr |
"Please check the configuration and try again" |
|
RTT-3-EPNOTIFYFAILED |
3-Error |
event type = [chars] client = [chars] reason = [chars] |
Notification for specified type to specified IPSLAs Event Publisher client failed |
rsps-time-rptr |
"This maybe transient system error and the " "notification may work next time. Take the action " " as suggested by the identified client for loss " " of notification." |
|
RTT-3-EPSTARTERROR |
3-Error |
Failed to start IPSLAs Event Publisher |
IPSLAs is unable to start a new process for Event Publisher. Reaction Alert notifications will not work. |
rsps-time-rptr |
LOG_STD_REDUCE_ACTION |
|
RTT-3-EPURFTYPE |
3-Error |
IPSLAs EventPublisher: Unknown reaction filter type for client [chars] |
IPSLAs Event Publisher encountered unknown filter type while sending the reaction alert to specified client Reaction Alert notifications may continue to work for same and other clients. |
rsps-time-rptr |
LOG_STD_REDUCE_ACTION |
|
RTT-3-IPSLA_AQM |
3-Error |
[chars]: [chars] |
This message indicates software error in IPSLA auto qos monitor feature. |
rsps_time_rptr |
"Contact your Cisco technical support representative." |
|
RTT-3-IPSLAINITIALIZEFAIL |
3-Error |
IP SLAs: Failed to initialize IP SLAs functionality will not work |
IP SLAs failed to initialize. This condition is caused by either a timer wheel timer functionality init that failed or a process that could not be created. A likely cause of this condition is that sufficient memory is not available to complete the task. |
rsps-time-rptr |
"Search for resolved software issues using the Bug " "Toolkit at " "http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl." LOG_STD_REDUCE_ACTION |
|
RTT-3-IPSLANEGATIVEVALUE |
3-Error |
IP SLAs[dec]: Negative Value for [chars] |
IP SLAs statistics has generated an error message. |
rsps-time-rptr |
"Contact your Cisco technical support " "representative" |
|
RTT-3-IPSLANOPROCESS |
3-Error |
IP SLAs: Cannot create a new process |
IP SLAs is unable to start a new process and may not be running. |
rsps-time-rptr |
LOG_STD_REDUCE_ACTION |
|
RTT-3-IPSLAPROBENOTFOUND |
3-Error |
IP SLAs: Error deleting the probe |
Trying to delete a probe which does not exist |
rsps-time-rptr |
"Contact your Cisco technical support " "representative" |
|
RTT-3-IPSLARESP_TCP_PORT_IN_USE |
3-Error |
IP SLA Responder: tcp: [chars] - [dec] Port already in use. |
IP SLA Responder is unable to bind the socket as the port specified in the port enable control message is already in use by other application. |
sla |
"This message indicates that the port configured." "in the udp-jitter operation targetting this Responder is already in use " "and it is recommended to reconfigure the tcp operation with a " "different port number." |
|
RTT-3-IPSLARESP_TCP_PORT_IN_USE |
3-Error |
- |
- |
- |
- |
|
RTT-3-IPSLARESP_TCP_PORT_IN_USE |
3-Error |
- |
- |
- |
- |
|
RTT-3-IPSLARESP_TCP_PORT_IN_USE |
3-Error |
- |
- |
- |
- |
|
RTT-3-IPSLARESP_TCP_PORT_IN_USE |
3-Error |
- |
- |
- |
- |
|
RTT-3-IPSLARESP_TCP_PORT_IN_USE |
3-Error |
- |
- |
- |
- |
|
RTT-3-IPSLARESP_TCP_PORT_IN_USE |
3-Error |
- |
- |
- |
- |
|
RTT-3-IPSLARESP_TCP_PORT_IN_USE |
3-Error |
- |
- |
- |
- |
|
RTT-3-IPSLARESP_UDP_PORT_IN_USE |
3-Error |
IP SLA Responder: udp: [chars] - [dec] Port already in use. |
IP SLA Responder is unable to bind the socket as the port specified in the port enable control message is already in use by other application. |
sla |
"This message indicates that the port configured." "in the udp-jitter operation targetting this Responder is already in use " "and it is recommended to reconfigure the udp operation with a " "different port number." |
|
RTT-3-IPSLARESPEVQINITFAIL |
3-Error |
IP SLAs responder initialzation failed |
The IP SLAs responder initialization failed to initialize event queue. Because of this failure the IP SLAs probes on other routers for which this router acts as responder will not work. |
rsps_time_rptr |
"Contact your Cisco technical support representative." |
|
RTT-3-IPSLARESPTWINITFAIL |
3-Error |
IP SLAs responder initialzation failed |
- |
- |
- |
|
RTT-3-IPSLARTPAPPINITFAILED |
3-Error |
IP SLAs rtp operation application process initialzation failed |
The IP SLAs rtp operation application process failed to initialize. Because of this failure the IP SLAs rtp operations will not work. |
rsps_time_rptr |
"Contact your Cisco technical support representative." |
|
RTT-3-IPSLATHRESHOLD |
3-Error |
IP SLAs[dec]: Threshold [chars] for [chars] |
This informational message logs threshold violations in the Service Assurance Agent probes. This messages appears when the <CmdBold>ip sla logging trap<NoCmdBold> command is entered |
rsps-time-rptr |
"If this message is not necessary enter the " "<CmdBold>no ip sla logging trap<NoCmdBold> command to disable " "logging. Otherwise no action is required" |
|
RTT-3-IPSLATWINITFAIL |
3-Error |
IP SLAs: Generic Timer wheel timer functionality failed to initialize |
IP SLAs could not initialize the timer wheel. |
rsps-time-rptr |
"Search for resolved software issues using the Bug " "Toolkit at " "http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl." LOG_STD_REDUCE_ACTION |
|
RTT-3-REACTNOTIFYFAILED |
3-Error |
entry number = [dec] reason = [chars] |
IPSLAs Reaction condition was met for specified operation and one or more IPSLAs Event Publisher clients have registered interest for this condition but the notification for this occurence failed. |
rsps-time-rptr |
"These maybe transient system errors and the " "notification may work next time. Use show ip sla" " event-publisher command to see which clients are " " registered and take action recommended by them." |
|
RTT-3-SAAMPLS |
3-Error |
IP SLA Monitor[dec]: MPLS [chars] Probe [chars] [chars] for destination-address |
This informational message logs violations in the Service Assurance Agent probes. This messages appears when the <CmdBold>ip sla logging trap<NoCmdBold> command is entered |
rsps_time_rptr |
"If this message is not necessary enter the " "<CmdBold>no ip sla logging trap<NoCmdBold> command to disable logging. " "Otherwise no action is required" |
|
RTT-3-XOS_XDM_ERR |
3-Error |
IP SLAs: Cannot create a new xdm instance |
IP SLAs is unable to start a new xdm instance and may not be running. |
sla |
"This message indicates that the system is running " "out of xdm instance and the IPSLAs configured after this message " "may fail. So do not configure any probe after this syslog" |
|
RTT-4-AUTOAPI |
4-Warning |
IPSLAs Auto CFG ERR: [chars][chars] [chars] |
An error occured while configuring IPSLAs Auto parameters. Some or all of your configurations may not have been unset |
rsps-time-rptr |
"Please check the configuration and try again" |
|
RTT-4-AUTOAPIOPER |
4-Warning |
IPSLAs Auto CFG ERR: [chars][chars][[dec]] [chars] |
An error occured while configuring IPSLAs Auto parameters. Some or all of your configurations may not have been unset |
rsps-time-rptr |
"Please check the configuration and try again" |
|
RTT-4-AUTOMEM |
4-Warning |
IPSLAs Auto MEM ERR: [chars][chars] [chars] |
IPSLAs Auto feature failed during memory allocation |
rsps-time-rptr |
"These maybe transient errors please try again" |
|
RTT-4-DuplicateEvent |
4-Warning |
IP SLAs [dec]: Duplicate event received. Event number [dec] |
IP SLAs process has received a duplicate event |
rsps-time-rptr |
"This is only a warning message. If this recurs " "enter the command <CmdBold>show ip sla configuration<NoCmdBld> and " "copy the output of the command. Copy the message 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 along with information about the application " "that is configuring and polling the Service Assurance Agent probes." |
|
RTT-4-EPAPI |
4-Warning |
IPSLAs EP API: [chars] api failed client = [chars] reason = [chars] |
IPSLAs Event Publisher API failed for reason identified |
rsps-time-rptr |
"The error code is reported to API client. Take " "the action recommended by the client identified." |
|
RTT-4-EPINIT |
4-Warning |
IPSLAs Event Publisher Init Failed. Reason = [chars] |
IPSLAs Event Publisher Initialization failed. The system will try to recover by doing the initialization tasks when first client subscribes to IPSLAs events. |
rsps-time-rptr |
LOG_STD_REDUCE_ACTION |
|
RTT-4-INVALIDSRCIPADDR |
4-Warning |
Possible invalid src IP address [inet] configured. |
This message appears when no source IP address is found on the host matching the one specified by the user |
rsps_time_rptr |
"Unconfigure the probe and reconfigure with " "valid source IP address" |
|
RTT-4-IPSLAAUTODISCOAUTHFAIL |
4-Warning |
IP SLAs end point discovery authentication failure for spoke [inet]. |
The IP SLAs responder initialization failed to initialize timerwheel. Because of this failure the IP SLAs probes on other routers for which this router acts as responder will not work. |
rsps_time_rptr |
"Contact your Cisco technical support representative." |
|
RTT-4-IPSLACLOCKNOTSET |
4-Warning |
IP SLAs Probes could not be |
One or more IP SLAs probes could not be scheduled because system clock is not set. |
rsps_time_rptr |
"Ensure that the system clock is functional by using Network Time " "Protocol or another mechanism." |
|
RTT-4-IPSLAENDPOINTDEREGISTER |
4-Warning |
IP SLAs end point de-registered by hub [inet]. |
- |
- |
- |
|
RTT-4-IPSLASCHEDCONFIGFAIL |
4-Warning |
IP SLAs Probe [dec]: [chars] |
The IP SLAs probe could not be scheduled. Either the configured starting time has already ocurred or the starting time is invalid. |
rsps_time_rptr |
"Reschedule the failed probe with a valid start time." |
|
RTT-4-OPER_CLOSS |
4-Warning |
condition [chars] entry number = [dec] |
This message logs connection loss condition in the IPSLAs operations. This message is enabled when the <CmdBold>ip sla monitor logging trap<NoCmdBold> command is entered |
rsps_time_rptr |
"Ensure the the destination for the IPSLAs " "operation is reachable. Also ensure that the IPSLAs responder " "operation is configured on the destination. If you do not want " "to log these messages for IPSLA operations enter the " "<CmdBold>no ip sla monitor logging trap<NoCmdBold> command to " "disable logging." |
|
RTT-4-OPER_PROTOERR |
4-Warning |
Entry number = [dec] Protocol Specific Error [chars] specific code = [dec] |
This message logs protocol specific error condition in the IPSLAs operations. This message is enabled when the <CmdBold>ip sla logging traps<NoCmdBold> command is entered |
sla |
"Ensure that the destination for the IPSLAs " "operation is reachable. Also ensure that the IPSLA responder " "operation is configured on the destination. If you do not want " "to log these messages for IPSLAs operations enter the " "<CmdBold>no ip sla logging traps<NoCmdBold> command to " "disable the logging" |
|
RTT-4-OPER_TIMEOUT |
4-Warning |
condition [chars] entry number = [dec] |
This message logs timeout condition in the IPSLAs operations. This message is enabled when the <CmdBold>ip sla monitor logging trap<NoCmdBold> command is entered |
rsps_time_rptr |
"Ensure that the destination for the IPSLAs " "operation is reachable. If you do not want to log these messages for " "IPSLAs operations enter the " "<CmdBold>no ip sla monitor logging trap<NoCmdBold> command to " "disable the logging" |
|
RTT-4-REACTPARTIALEVENT |
4-Warning |
entry number = [dec] missing data = [chars] |
IPSLAs Reaction Event is missing some interesting data |
rsps-time-rptr |
"This could be because of IPSLAs software error. " "Please collect show ip sla config output and " "report issue to TAC" |
|
RTT-4-SAAGRPSCHEDCONFIGFAIL |
4-Warning |
Group Schedule Entry [dec]: [chars] |
The probes could not be group scheduled. Either the configured starting time has already ocurred or the starting time is invalid. |
rsps_time_rptr |
"Reschedule the group scheduling entry with a valid start time." |
|
RTT-4-SAASCHEDCONFIGFAIL |
4-Warning |
IP SLA Monitor Probe [dec]: [chars] |
The IP SLA Monitor probe could not be scheduled. Either the configured starting time has already ocurred or the starting time is invalid. |
rsps_time_rptr |
"Reschedule the failed probe with a valid start time." |
|
RUDP-3-INIT |
3-Error |
rudp [dec]: [chars][chars]. |
RUDP initialization operation fails. |
- |
LOG_STD_ACTION |
|
RUDP-4-LINK |
4-Warning |
rudp [dec]: [chars][chars]. |
A warning is given out for a particular RUDP link. |
- |
LOG_STD_DBG_ACTION |
|
RUDP-4-NOBUF |
4-Warning |
rudp [dec]: cannot get packet buffer for [chars]. |
A rudp link cannot allocate a packet buffer. |
- |
LOG_STD_REDUCE_ACTION |
|
RXP_MANAGER-3-BADBIND |
3-Error |
illegal bind [dec] [dec] |
illegal bind operation |
- |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release. If not gather the output of <CmdBold>show version<NoCmdBold> " "and <CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
RXP_MANAGER-3-BADINDEX |
3-Error |
bad index value: [chars] [dec] |
index value outside array limits |
- |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release. If not gather the output of <CmdBold>show version<NoCmdBold> " "and <CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
RXP_MANAGER-3-BADTYPE |
3-Error |
[chars] [dec] |
illegal type |
- |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release. If not gather the output of <CmdBold>show version<NoCmdBold> " "and <CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
RXP_MANAGER-3-BADUNBIND |
3-Error |
illegal unbind [dec] [dec] |
illegal bind operation |
- |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release. If not gather the output of <CmdBold>show version<NoCmdBold> " "and <CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
RXP_MANAGER-3-BADVAL |
3-Error |
unexpected value: [chars] [dec] |
unexpected value encountered |
- |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release. If not gather the output of <CmdBold>show version<NoCmdBold> " "and <CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
RXP_MANAGER-3-DEFVEC |
3-Error |
default vectors used: [chars] |
default vector used |
- |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release. If not gather the output of <CmdBold>show version<NoCmdBold> " "and <CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
RXP_MANAGER-3-NULLPTR |
3-Error |
[chars] 0x[hec] |
null pointer |
- |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release. If not gather the output of <CmdBold>show version<NoCmdBold> " "and <CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
RXP_MANAGER-3-REFCOUNT |
3-Error |
bad refcnt: [chars] 0x[hec] |
bad reference count |
- |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release. If not gather the output of <CmdBold>show version<NoCmdBold> " "and <CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
RXP_MANAGER-3-UNINIT |
3-Error |
[chars] [dec] |
uninitialized data structure |
- |
"Refer to the Bug Navigator at www.cisco.com to see if this " "condition has been previously reported and resolved in a " "later release. If not gather the output of <CmdBold>show version<NoCmdBold> " "and <CmdBold>show running-config<NoCmdBold> and contact your Cisco technical " "support representative." |
|
SADB-4-TREE_CORRUPTED |
4-Warning |
SADB : AVL Tree got corrupted |
SADB's one of the AVL Trees got corrupted |
eedge-policy |
LOG_STD_NO_ACTION |
|
SANTANA-3-DS_JIB_ERROR |
3-Error |
DS JIB Santana FPGA Error detected and corrected |
DS JIB Santana FPGA Error corrected |
cmts-infra |
"Contact TAC to collect debug log from the linecard" |
|
SASL-2-FORKFAIL |
2-Critical |
Cannot fork process [chars] |
Attempted to fork a process and failed. |
sasl |
LOG_STD_ACTION |
|
SASL-2-INITFAIL |
2-Critical |
Initialization failed - [chars] |
SASL component initialization failed. |
sasl |
LOG_STD_ACTION |
|
SAT9K_CLT_CFG-3-INT_FAIL |
3-Error |
[chars]:[dec]: Internal Error |
internal error |
- |
LOG_STD_NO_ACTION |
|
SAT9K_CROSS_LINK -3-CROSSLINK_MAP_FAIL |
3-Error |
\n Failure in configuring \crosslink mapping with error code:[dec] |
CROSSLINK mapping for VICL/ICL failed |
- |
- |
|
SAT9K_CROSS_LINK -3-INVLD_ACTION |
3-Error |
Invalid action issued by \host |
- |
- |
- |
|
SAT9K_CROSS_LINK -3-INVLD_EVENT |
3-Error |
Invalid event received |
- |
- |
- |
|
SAT9K_CTRL-3-CTRL_ERR |
3-Error |
Sat9k Controller Error: [chars] |
Sat9k Controller Error |
- |
LOG_STD_ACTION |
|
SAT9K_CTRL-3-SOC_ERR |
3-Error |
Socket [chars] failed for socket id [dec] |
Error during socket operations |
- |
LOG_STD_ACTION |
|
SAT9K_CTRL-3-TOD_ERR |
3-Error |
Sat9k TOD Error: %lu seconds |
Error in Time of Day update |
- |
LOG_STD_ACTION |
|
SAT9K_CTRL-3-XOS_ERR |
3-Error |
Sat9k XOS Error: [chars] |
Sat9k Controller Error during XOS calls |
- |
LOG_STD_ACTION |
|
SAT9K_FEC_CONTROL -3-INVLD_ACTION |
3-Error |
Invalid action issued by \host |
- |
- |
- |
|
SAT9K_FEC_CONTROL -3-INVLD_EVENT |
3-Error |
Invalid event received |
- |
- |
- |
|
SAT9K_FEC_CONTROL -3-LAG_CREATE_FAIL |
3-Error |
\n Failure in creating \port-channel [dec] with error code:[dec] |
LAG CREATE failed |
- |
- |
|
SAT9K_FEC_CONTROL -3-LAG_DELETE_FAIL |
3-Error |
\n Failure in deleting \port-channel [dec] with error code:[dec] |
LAG DELETE failed |
- |
- |
|
SAT9K_FEC_CONTROL -3-LAG_MEMBER_ADD_FAIL |
3-Error |
\n Failure in configuring \lag member Te 1/[dec] for port-channel [dec] with error code:[dec] |
LAG MEMBER ADD failed for given port-channel |
- |
- |
|
SAT9K_FEC_CONTROL -3-LAG_MEMBER_DELETE_FAIL |
3-Error |
\n Failure in deleting \lag member Te 1/[dec] from port-channel [dec] with error code:[dec] |
LAG MEMBER ADD failed for given port-channel |
- |
- |
|
SAT9K_IMG_DOWNLOADER -3-FLASH_BURN_FAIL |
3-Error |
\nFailed to burn image [chars] into flash memory |
Write to flash failed |
- |
- |
|
SAT9K_IMG_DOWNLOADER -3-INVLD_ACTION |
3-Error |
Invalid action issued by host |
- |
- |
- |
|
SAT9K_IMG_DOWNLOADER -3-INVLD_EVENT |
3-Error |
Invalid event received |
- |
- |
- |
|
SAT9K_IMG_DOWNLOADER -3-PROC_CRT_FAIL |
3-Error |
\nFailed to Create Image Download Process |
- |
- |
- |
|
SAT9K_IMG_DOWNLOADER -3-QUEUE_CRT_FAIL |
3-Error |
\nFailed to create watched Boolean for Image Download |
watched Boolean creatation failed |
- |
- |
|
SAT9K_IMG_DOWNLOADER -3-TFTP_READ_FAIL |
3-Error |
\n FTP download failure for [chars] with error code:[dec] |
Download via TFTP failed |
- |
- |
|
SAT9k_IMGR-3-BASE_MAC_GET_FAIL |
3-Error |
[chars] |
Due to internal system error the interface manager process could not retrieve base mac address |
- |
LOG_STD_ACTION |
|
SAT9k_IMGR-3-IMGR_INVALID_CALL |
3-Error |
[chars] |
Call to license processing is not supported on ASR 9000v Satellite |
- |
LOG_STD_ACTION |
|
SAT9k_IMGR-3-IMGR_INVALID_EVENT |
3-Error |
\n Unknown event : Major [dec] Minor [dec] |
Interface statistics poller received an invalid event |
- |
LOG_STD_ACTION |
|
SAT9k_IMGR-3-IMGR_INVALID_PARAM |
3-Error |
[chars] [dec] |
An internal system error occured during an invalid parameter being passed to interface manager |
- |
LOG_STD_ACTION |
|
SAT9k_IMGR-3-IMGR_LIST_CREATE_FAIL |
3-Error |
[chars] |
An internal system error occured during list create operation for AP/ICL |
- |
LOG_STD_ACTION |
|
SAT9k_IMGR-3-IMGR_LIST_FAIL |
3-Error |
[chars] [chars] |
An internal system error occured during list operations for AP/ICL |
- |
LOG_STD_ACTION |
|
SAT9k_IMGR-3-IMGR_NULL_PARAM |
3-Error |
[chars] |
An internal system error occured due to a null parameter passed to interface manager |
- |
LOG_STD_ACTION |
|
SAT9k_IMGR-3-PROC_CRT_FAIL1 |
3-Error |
Sat9k Interface Mgr process could not be started |
Due to internal system error the interface manager process could not be created/initialized |
- |
LOG_STD_ACTION |
|
SAT9k_IMGR-3-PROC_CRT_FAIL2 |
3-Error |
Sat9k Interface Stats process could not be started |
Due to internal system error the interface stats poller process could not be created/initialized. Sat9k might not report statistics correctly |
- |
LOG_STD_ACTION |
|
SAT9k_NOTIF-0-FMEA_ALM |
0-Emergency |
[chars] has been [chars] |
FMEA alarm notification |
- |
LOG_STD_ACTION |
|
SAT9k_NOTIF-1-EQPT_ALM |
1-Alert |
[chars] has been [chars] |
Equipment alarm notification |
- |
LOG_STD_ACTION |
|
SAT9k_NOTIF-1-LINK_ALM |
1-Alert |
[chars] has been [chars] for port [dec] |
Link Fault alarm notification |
- |
LOG_STD_ACTION |
|
SAT9k_NOTIF-1-PORT_ALM |
1-Alert |
[chars] has been [chars] for port [dec] |
Port/Pluggable alarm notification |
- |
LOG_STD_ACTION |
|
SAT9k_NOTIF-2-MEM_ALM |
2-Critical |
[chars] has been [chars] |
Memory alarm notification |
- |
LOG_STD_ACTION |
|
SAT9k_NOTIF-2-UNKNOWN_ALM |
2-Critical |
[chars] has been [chars] |
An Uncategorized alarm notification |
- |
LOG_STD_ACTION |
|
SAT9k_NOTIF-3-PROC_CRT_FAIL |
3-Error |
Sat9k Alarm poller process could not be started |
Due to internal system error the alarm poller process could not be created/initialized. Sat9k might not report alarms/notifications correctly |
- |
LOG_STD_ACTION |
|
SBC_CFG-3-DBE_CONFIG_FAILURE |
3-Error |
An SBC DBE configuration failure has occurred. |
SBC has been unable to apply its DBE configuration. |
sbc-comp |
"Attempt to manually reconfigure the SBC DBE. " LOG_STD_ACTION |
|
SBC_CFG-3-MED_NOT_DEL_V4 |
3-Error |
IPv4 addresses deleted %I %I VRF '[chars]' |
One or more IPv4 addresses of an SBC interface were removed while the SBC was still active. Please remove the media addresses/pools later manually. If the media addresses/pools were associated with a VRF then it will be necessary to remove the media addresses/pools by unconfiguring the SBC. |
sbc-comp |
- |
|
SBC_CFG-3-MED_NOT_DEL_V6 |
3-Error |
IPv6 addresses deleted %P/[dec] VRF '[chars]' |
One or more IPv6 addresses of an SBC interface were removed while the SBC was still active. Please remove the media addresses/pools later manually. If the media addresses/pools were associated with a VRF then it will be necessary to remove the media addresses/pools by unconfiguring the SBC. |
sbc-comp |
- |
|
SBC_CFG-3-SBC_NOT_CONFIG |
3-Error |
SBC is not configured. VOIP LI configuration request failed |
Since SBC is not configured the VOIP LI request is rejected. First configure SBC and then VOIP LI requests will be processed. |
sbc-comp |
- |
|
SBC_CFG-3-SERVICE_CHANGE_COLD_BOOT_FAILED |
3-Error |
Delayed ServiceChange failed. |
SBC has failed to send the delayed ServiceChange message at boot. |
sbc-comp |
"Ensure that the SBC configuration is valid " "and perform a manual SBC Activation." |
|
SBC_CFG-4-BLACKLIST_BLOCKED |
4-Warning |
Source [chars]: blacklisted blocked reason: [chars] |
The source is blacklisted. |
sbc-comp |
- |
|
SBC_CFG-4-BLACKLIST_CLEARED |
4-Warning |
Source [chars]: cleared blacklist event or alert reason: [chars] |
A blacklist event or alert is cleared. |
sbc-comp |
- |
|
SBC_CFG-4-BLACKLIST_CRITICAL |
4-Warning |
Source [chars]: critical blacklist alert reason: [chars] |
A critical blacklist alert has been generated. |
sbc-comp |
- |
|
SBC_CFG-4-BLACKLIST_MAJOR |
4-Warning |
Source [chars]: major blacklist alert reason: [chars] |
A major blacklist alert has been generated. |
sbc-comp |
- |
|
SBC_CFG-4-BLACKLIST_MINOR |
4-Warning |
Source [chars]: minor blacklist alert reason: [chars] |
A minor blacklist alert has been generated. |
sbc-comp |
- |
|
SBC_CFG-4-SERVICE_CHANGE_COLD_BOOT_DELAY_FAILED |
4-Warning |
Failed to delay ServiceChange. |
SBC has failed to start a timer for delaying a ServiceChange message at boot. The ServiceChange message will be sent out without a delay. |
sbc-comp |
"Ensure that SBC has been fully Activated and " "that all requested pinholes have been established. " LOG_STD_ACTION |
|
SBC_CFG-6-SERVICE_CHANGE_COLD_BOOT |
6-Information |
Delay [chars]. |
SBC has been configured to delay sending a ServiceChange message at boot. Upon the delay timer expiring the ServiceChange message will be sent. |
sbc-comp |
"This message is for informational purposes only. " "A ServiceChange message will be sent out once the " "delay timer expires." |
|
SBC_COMP-3-MEMORY_ALERT |
3-Error |
SBC memory congestion level has changed from [chars] to [chars].\n Usage: [dec] of [dec] bytes. |
SBC has reported a processor memory change. |
sbc-comp |
- |
|
SBC_COMP-3-MEMORY_REJ |
3-Error |
SBC is rejecting new INVITES due to memory congestion state.\n Usage: [dec] of [dec] bytes. |
SBC has reported a rejected a new call due to memory state. |
sbc-comp |
- |
|
SBC_HA-3-CONFIG_SYNC |
3-Error |
SBC failed to cache SBC config of size [dec]. |
The SBC module was unable to successfully cache the SBC config on the Standby. The Standby will be unable to write SBC config to NVRAM. |
sbc-ha |
LOG_STD_ACTION |
|
SBC_HA-3-HOLD_PROGRESSION |
3-Error |
SBC RF failed to start the progression holding process. |
The SBC module was unable to successfully start the RF progression holding process. RF progression will resume immediately but if a switchover occurs immediately after the system reaches the Standby Hot redundancy state then some SBC calls may be lost. |
sbc-ha |
LOG_STD_ACTION |
|
SBC_HA-3-ILT_PROC_CREATE |
3-Error |
SBC ILT process creation failed. |
The SBC module was unable to successfully create an SBC process. SBC will not be able to operate in a stateful mode. |
sbc-ha |
LOG_STD_ACTION |
|
SBC_HA-3-ILT_REGISTRATION |
3-Error |
SBC ILT registration failed. |
The SBC module was unable to successfully register for communication with the peer unit. SBC will not be able to operate in a stateful mode. |
sbc-ha |
LOG_STD_ACTION |
|
SBC_HA-3-ILT_STUB |
3-Error |
SBC ILT Stub process creation failed. |
The SBC module was unable to successfully create the ILT Stub process. SBC will not be able to operate in a stateful mode. |
sbc-ha |
LOG_STD_ACTION |
|
SBC_HA-3-INTERNAL |
3-Error |
An internal SBC HA error has been encountered[chars]. |
An internal error has been encountered. |
sbc-ha |
LOG_STD_ACTION |
|
SBC_HA-3-IPC_INIT |
3-Error |
SBC IPC failed to initialise [chars]. |
The SBC IPC module was unable to successfully initialise. SBC may not be able to operate in a stateful mode. |
sbc-ha |
LOG_STD_ACTION |
|
SBC_HA-3-IPC_RMI_INIT |
3-Error |
SBC IPC failed to register with RMI [chars]. |
The SBC IPC module was unable to successfully register with the Resource Manager. SBC may not be able to operate in a stateful mode. |
sbc-ha |
LOG_STD_ACTION |
|
SBC_HA-3-IPC_SEND |
3-Error |
SBC IPC message send failed error [chars]. |
The SBC module was unable to successfully send a message to its peer. SBC will not be able to operate in a stateful mode. |
sbc-ha |
LOG_STD_ACTION |
|
SBC_HA-3-ISSU_CAPENTRY_REGISTRATION |
3-Error |
SBC Cap Entry [dec] for Entity [dec] Registration failed [chars]. |
A capability entry could not be registered for SBC ISSU. SBC will not be able to operate in a stateful mode. |
sbc-ha |
"show issu capability entries" |
|
SBC_HA-3-ISSU_CAPGROUP_REGISTRATION |
3-Error |
SBC Cap Group [dec] for Entity [dec] Registration failed [chars]. |
A capability group could not be registered for SBC ISSU. SBC will not be able to operate in a stateful mode. |
sbc-ha |
"show capability groups" |
|
SBC_HA-3-ISSU_CAPTYPE_REGISTRATION |
3-Error |
SBC Cap Type for Entity [dec] Registration failed [chars]. |
A capability type could not be registered for SBC ISSU. SBC will not be able to operate in a stateful mode. |
sbc-ha |
"show issu capability types" |
|
SBC_HA-3-ISSU_CLIENT_REGISTRATION |
3-Error |
SBC Client [dec] Registration failed [chars]. |
The SBC module was unable to successfully register with the ISSU infrastructure. SBC will not be able to operate in a stateful mode. |
sbc-ha |
"show issu clients" |
|
SBC_HA-3-ISSU_ENTITY_REGISTRATION |
3-Error |
SBC Entity [dec] Registration failed [chars]. |
The SBC ISSU entity could not be registered. SBC will not be able to operate in a stateful mode. |
sbc-ha |
"show issu entities" |
|
SBC_HA-3-ISSU_MSG_MTU |
3-Error |
SBC Client [dec] get msg mtu failed. Error = [dec]. |
The SBC ISSU client could not obtain a message of the required size. |
sbc-ha |
"show issu fsm" |
|
SBC_HA-3-ISSU_MSGGROUP_REGISTRATION |
3-Error |
SBC Msg Group [dec] for Entity [dec] Registration failed [chars]. |
The message group for SBC ISSU could not be registered. SBC will not be able to operate in a stateful mode. |
sbc-ha |
"show issu message groups" |
|
SBC_HA-3-ISSU_MSGTYPE_REGISTRATION |
3-Error |
SBC Msg Type for Entity [dec] Registration failed [chars]. |
The message type for SBC ISSU could not be registered. SBC will not be able to operate in a stateful mode. |
sbc-ha |
"show issu message types" |
|
SBC_HA-3-ISSU_NEGOTIATION |
3-Error |
SBC ISSU negotiation failed. |
The SBC module was unable to successfully negotiate with its peer. SBC will not be able to operate in a stateful mode. |
sbc-ha |
LOG_STD_ACTION |
|
SBC_HA-3-ISSU_REGISTRATION |
3-Error |
SBC ISSU failed to register. |
The SBC module was unable to successfully register with the ISSU infrastructure. SBC will not be able to operate in a stateful mode. |
sbc ha |
LOG_STD_ACTION |
|
SBC_HA-3-ISSU_SESSION_REGISTRATION |
3-Error |
SBC session for Entity [dec] Registration failed [chars]. |
The SBC ISSU session could not be registered. SBC will not be able to operate in a stateful mode. |
sbc-ha |
"show issu sessions" |
|
SBC_HA-3-ISSU_START_NEGOTIATION |
3-Error |
SBC ISSU negotiation failed to start [chars]. |
The SBC module was unable to successfully start negotiatiation with its peer. SBC will not be able to operate in a stateful mode. |
sbc-ha |
"show issu fsm" |
|
SBC_HA-3-ISSU_TRANSFORM |
3-Error |
SBC ISSU [chars] transformation failed [chars]. |
The transformation operation for an SBC ISSU message has failed. |
sbc-ha |
"show issu fsm and show issu sessions" |
|
SBC_HA-3-LARGE_IPS_MSG |
3-Error |
SBC failed to receive large sync message of size [dec]. |
The SBC module was unable to successfully receive a large sync message on the Standby. The Standby will be will not have an identical dynamic state as the Active. |
sbc-ha |
LOG_NO_ACTION |
|
SBC_HA-3-LARGE_IPS_MSG_FAIL |
3-Error |
SBC failed to send large sync message of size [dec]. |
The SBC module was unable to successfully send a large sync message to the Standby because this version of the Standby does not support large messages. The Standby will be will not have an identical dynamic state as the Active. |
sbc-ha |
LOG_NO_ACTION |
|
SBC_HA-3-LARGE_IPS_UNSUPP |
3-Error |
The current version of the SBC Standby does not support the syncing of large SBC contexts |
The current version of the SBC Standby does not support the syncing of large SBC contexts. A context that contains 24 or more media and signaling flows is a large context. It is rare to have such a large context and thus ISSU compatibility has been permitted even though this difference in support exists. Normal SBC High Availability synchronization will continue to operate successfully as long as no contexts contain more than 24 signaling or media flows. Context information beyond 24 flows will not be replicated and thus on RP switchover the Active RP will not have information about all the contexts |
sbc-ha |
LOG_STD_ACTION |
|
SBC_HA-3-NO_SYNC_PROCESS |
3-Error |
SBC RF failed to start the config sync process. |
The SBC module was unable to successfully start the configuration sync process. The Standby will be unable to fully initialise. |
sbc-ha |
LOG_STD_ACTION |
|
SBC_HA-3-RF_CONFIG_SYNC |
3-Error |
SBC RF will not be able to synchronise SBC configuration to the Standby. Failure cause: [chars]. |
The SBC module will not be able to synchronise the SBC config to the Standby. The Standby will be unable to write SBC config to NVRAM. |
sbc-ha |
LOG_STD_ACTION |
|
SBC_HA-3-RF_PROGRESSION |
3-Error |
SBC RF failed to resume RF progression at state [chars]. |
The SBC module was unable to successfully resume RF progression at the noted state. The Standby will be unable to fully initialise. |
sbc-ha |
LOG_STD_ACTION |
|
SBC_HA-3-RF_REGISTRATION |
3-Error |
SBC RF failed to register |
The SBC module was unable to successfully register with the RF infrastructure. SBC will not be able to operate in a stateful mode. |
sbc-ha |
LOG_STD_ACTION |
|
SBC_HA-3-RF_TIMER_EXTENSION_EXPIRY |
3-Error |
SBC RF progression extension timer expired. |
The SBC module's RF progression extension timer expired. RF progression will resume but if a switchover occurs immediately after the system reaches the Standby Hot redundancy state then some SBC calls may be lost. |
sbc-ha |
LOG_STD_ACTION |
|
SBC_HA-3-SBC_B2B_RESTART |
3-Error |
SBC restart has taken longer than expected.\n The SBC will be restarted but may require a \n shut/no shut of the redundancy group in order to\n return to stateful HA with the active router.\n |
SBC process restart timedout may require manual intervention. |
sbc-ha |
"Shut/No shut the standby redundancy group associated with the SBC." LOG_STD_ACTION |
|
SBC_HA-3-SBC_CAC_ENHANCEMENT_CFG |
3-Error |
SBC has detected cac enhancement feature configured\n which may have branch cli \n OR cac-scope adjacency accountcli \n |
Peer SBC does not support cac enhancement feature configuration. |
sbc-ha |
"Manually remove cac enhancement feature configuration " "and reinitiate ISSU." LOG_STD_ACTION |
|
SBC_HA-3-SBC_CODEC_INTERWORK_CFG |
3-Error |
SBC has detected codec configuration which is\n not supported on the peer. SBC cannot proceed as HA client.\n Remove all newly entered codec configuration to proceed\n with ISSU/ISSD.\n |
Peer SBC does not support codec preference variant or interwork configuration. |
sbc-ha |
"Manually remove newly added codec configuration and" " reinitiate ISSU. " LOG_STD_ACTION |
|
SBC_HA-3-SBC_DBL_NA_ALERT_CFG |
3-Error |
SBC has detected blacklist entries configured\n which have reason na-policy-failure\n OR minor major critical alerts which is not supported on the peer.\n SBC cannot proceed as HA client.\n Remove all blacklist entries with this reason or any alerts\n configuration to proceed with ISSU/ISSD.\n |
Peer SBC does not support blacklist reason na-policy-failure or blacklist alerts configuration. |
sbc-ha |
"Manually remove blacklist reason na-policy-failure and " "minor major or critical alerts configuration " "and reinitiate ISSU." LOG_STD_ACTION |
|
SBC_HA-3-SBC_DYNAMIC_CODEC_CFG |
3-Error |
SBC has detected Dynamic Codec configuration which is\n not supported on the peer. SBC cannot proceed as HA client.\n Remove all codec configuration to proceed with ISSU/ISSD.\n |
Peer SBC does not support Dynamic Codec configuration. |
sbc-ha |
"Manually remove Dynamic Codec configuration and reinitiate" " ISSU. " LOG_STD_ACTION |
|
SBC_HA-3-SBC_FLEX_MED_RTG_CFG |
3-Error |
SBC has detected\n flexible media routing configuration. This feature is not supported \n on the peer. SBC cannot proceed as HA client. Remove all \n flexible media routing config from the configuration to proceed with \n ISSU/ISSD.\n |
Peer SBC does not support flexible media routing configuration. |
sbc-ha |
"Manually remove flexible media routing from configuration " "and reinitiate ISSU." LOG_STD_ACTION |
|
SBC_HA-3-SBC_HA_ADMIN_DOMAIN_CFG |
3-Error |
SBC has detected\n an admin-domain configuration. This feature is not supported \n on the peer. SBC cannot proceed as HA client. Remove all \n admin-domain submodes from the configuration to proceed with \n ISSU/ISSD.\n |
Peer SBC does not support admin-domain configuration. |
sbc-ha |
"Manually remove the admin-domain submodes from configuration " "and reinitiate ISSU." LOG_STD_ACTION |
|
SBC_HA-3-SBC_HA_CAC_AVG_PER2_CFG |
3-Error |
SBC has detected\n averaging-period 2 cac configuration. Averaging-period 2 is not\n supported on the peer. SBC cannot proceed as HA client. Remove the\n cac-policy-set averaging-period 2 configuration to proceed with\n ISSU/ISSD.\n |
Peer SBC does not support averaging-period 2 cac configuration. |
sbc-ha |
"Manually remove the cac-policy-set averaging-period 2 configuration " "and reinitiate ISSU." LOG_STD_ACTION |
|
SBC_HA-3-SBC_HA_CAC_AVG_PER2_RATE_CFG |
3-Error |
SBC has detected\n cac-policy-set rate limit configuration for averaging-period 2.\n Averaging-period 2 is not supported on the peer. SBC cannot proceed\n as HA client. Remove the cac-policy-set rate limit configuration \n for averaging-period 2 to proceed with ISSU/ISSD.\n |
Peer SBC does not support cac rate limit configuration for averaging-period 2. |
sbc-ha |
"Manually remove the rate limit commands for averaging-period 2 found " "within the cac-policy-set entry and reinitiate ISSU." LOG_STD_ACTION |
|
SBC_HA-3-SBC_HA_CAC_PRIVACY_SERV_CFG |
3-Error |
SBC has detected\n cac-policy-set privacy-service configuration for a cac entry.\n This enhancement is not supported on the peer. SBC cannot proceed\n as HA client. Remove the cac-policy-set privacy-service related \n configuration to proceed with ISSU/ISSD.\n |
Peer SBC does not support cac-policy-set privacy-service configuration for a cac entry. |
sbc-ha |
"Manually remove the privacy-service related commands configured " "within the cac-policy-set entry and reinitiate ISSU." LOG_STD_ACTION |
|
SBC_HA-3-SBC_HA_CALL_ONA_CFG |
3-Error |
SBC has detected\n first-outbound-na-table configured within a call-policy-set.\n This command is not supported on the peer. SBC cannot proceed\n as HA client. Remove all first-outbound-na-table configuration\n to proceed with ISSU/ISSD.\n |
Peer SBC does not support first-outbound-na-table configuration within a call-policy-set. |
sbc-ha |
"Manually remove the first-outbound-na-table configuration " "and reinitiate ISSU." LOG_STD_ACTION |
|
SBC_HA-3-SBC_HA_PORT_TAG_CFG |
3-Error |
SBC has detected\n an port tag configuration. This feature is not supported \n on the peer. SBC cannot proceed as HA client. Remove all \n port tag from the configuration to proceed with \n ISSU/ISSD.\n |
Peer SBC does not support port tag configuration. |
sbc-ha |
"Manually remove the port tag from configuration " "and reinitiate ISSU." LOG_STD_ACTION |
|
SBC_HA-3-SBC_IMP_NA_EDITSRC_CFG |
3-Error |
SBC has detected number analysis entries that have edit-src actions which are not supported on the peer.\n Remove all edit-src actions from all number analysis entries to proceed with ISSU/D |
Peer SBC does not support edit-src actions in number analysis entries. |
sbc-ha |
"Manually remove edit-src actions from " "all number analysis entries and reinitiate " "ISSU. " LOG_STD_ACTION |
|
SBC_HA-3-SBC_IMP_NA_REGEX_CFG |
3-Error |
SBC has detected number analysis entries that match on text addresses which are not supported on the peer.\n Remove all regex number analysis entries to proceed with ISSU/D |
Peer SBC does not support regex number analysis entries. |
sbc-ha |
"Manually remove regex number analysis entries" " and reinitiate ISSU. " LOG_STD_ACTION |
|
SBC_HA-3-SBC_IMP_NA_SRCANON_CFG |
3-Error |
SBC has detected na-src-name-anonymous number analysis tables which are not supported on the peer.\n Remove all na-src-name-anonymous number analysis tables to proceed with ISSU/D |
Peer SBC does not support na-src-name-anonymous number analysis tables. |
sbc-ha |
"Manually remove all na-src-name-anonymous number" " analysis tables and reinitiate ISSU. " LOG_STD_ACTION |
|
SBC_HA-3-SBC_IMS_RF_CFG |
3-Error |
SBC has detected ims rf configured. SBC cannot proceed now.\n Remove all ims rf config to proceed with ISSU/ISSD.\n |
Peer SBC does not support ims rf configuration. |
sbc-ha |
"Manually remove ims rf configuration and reinitiate ISSU." LOG_STD_ACTION |
|
SBC_HA-3-SBC_IPV6_CFG |
3-Error |
SBC has detected configuration/dynamic state [chars] which is |
Peer SBC does not support IPv6. |
sbc-ha |
"Manually remove IPv6 configuration and reinitiate" " ISSU. " LOG_STD_ACTION |
|
SBC_HA-3-SBC_LRU_CFG |
3-Error |
SBC has detected LRU configured\n SBC cannot proceed now.\n Remove all LRU CONFIG to proceed with ISSU/ISSD.\n |
Peer SBC does not support LRU configuration. |
sbc-ha |
"Manually remove LRU configuration " "and reinitiate ISSU." LOG_STD_ACTION |
|
SBC_HA-3-SBC_MEDIA_ADDRESS_PRESERVE_INIT_NEGO_CFG |
3-Error |
SBC has detected media address preserve init-negotiation configured\n SBC cannot proceed now.\n Remove all media address preserve init-negotiation config to proceed with ISSU/ISSD.\n |
Peer SBC does not support media address preserve init-negotiation configuration. |
sbc-ha |
"Manually remove media address preserve init-negotiation configuration " "and reinitiate ISSU." LOG_STD_ACTION |
|
SBC_HA-3-SBC_MEDIA_BYPASS_NATTAGGEN_CFG |
3-Error |
SBC has detected media bypass auto-nat-tag-gen configured\n SBC cannot proceed now.\n Remove all media bypass auto-nat-tag-gen config to proceed with ISSU/ISSD.\n |
Peer SBC does not support media bypass auto-nat-tag-gen configuration. |
sbc-ha |
"Manually remove media bypass auto-nat-tag-gen configuration " "and reinitiate ISSU." LOG_STD_ACTION |
|
SBC_HA-3-SBC_MESSAGE_EDITING_CFG |
3-Error |
SBC has detected message editing configured\n which may have \sip editor_type editor\\n OR parameter-editor OR header-editor OR method-editor OR body-editor\n OR option-editor which is not supported on the peer.\n SBC cannot proceed as HA client.\n Remove all message editing config to proceed with ISSU/ISSD.\n |
Peer SBC does not support message editing configuration. |
sbc-ha |
"Manually remove message editing configuration " "and reinitiate ISSU." LOG_STD_ACTION |
|
SBC_HA-3-SBC_MSMB_CFG |
3-Error |
SBC has detected Multi SBC Media\n Bypass configuration which is not supported on the peer.\n SBC cannot proceed as HA client.\n Remove all Multi SBC Media Bypass configuration to proceed \n with ISSU/ISSD.\n |
Peer SBC does not support Multi SBC Media Bypass configuration. |
sbc-ha |
"Manually remove Multi SBC Media Bypass configuration " "and reinitiate ISSU." LOG_STD_ACTION |
|
SBC_HA-3-SBC_QOS_DEMARCATION_CFG |
3-Error |
SBC has detected qos demarcation configured\n which may have statistics threshold \n OR g107a factor OR cal_moscqe OR g107 bpl OR g107 ie\n OR qos trap configured which is not supported on the peer.\n SBC cannot proceed as HA client.\n Remove all qos demarcation config to proceed with ISSU/ISSD.\n |
Peer SBC does not support qos demarcation configuration. |
sbc-ha |
"Manually remove qos demarcation configuration " "and reinitiate ISSU." LOG_STD_ACTION |
|
SBC_HA-3-SBC_RG_NO_CLIENT |
3-Error |
SBC was unable to register the RG Client with the RG\n infrastructure for inter-chassis HA.\n |
SBC will not be able to support inter-chassis HA. |
sbc-ha |
LOG_NO_ACTION |
|
SBC_HA-3-SBC_RG_NO_PROCESS |
3-Error |
SBC was unable to start a process used by the RG client\n |
SBC will not be able to support inter-chassis HA. |
sbc-ha |
LOG_NO_ACTION |
|
SBC_HA-3-SBC_RG_NO_SOCKET |
3-Error |
SBC was unable to open a socket for the RG client\n |
SBC will not be able to support inter-chassis HA. |
sbc-ha |
LOG_NO_ACTION |
|
SBC_HA-3-SBC_RG_NO_TRANSPORT |
3-Error |
SBC was unable to register a transport with the RG\n infrastructure for inter-chassis HA.\n |
SBC will not be able to support inter-chassis HA. |
sbc-ha |
LOG_NO_ACTION |
|
SBC_HA-3-SBC_RG_NO_VRF |
3-Error |
SBC VRF mismatch between active and standby please add [chars] |
SBC may fail to fully support SSO |
sbc-ha |
LOG_NO_ACTION |
|
SBC_HA-3-SBC_RG_SOCK_FAIL |
3-Error |
SBC lost connection with RG peer socket failure [chars] len=[dec]\n |
SBC HA may be disabled until peer connection is established. |
sbc-ha |
LOG_NO_ACTION |
|
SBC_HA-3-SBC_RG_VRF_INUSE |
3-Error |
VRF is used by SBC add back or remove from active please add [chars] |
SBC may fail to fully support SSO |
sbc-ha |
LOG_NO_ACTION |
|
SBC_HA-3-SBC_SDP_EDITING_CFG |
3-Error |
SBC has detected sdp editing configured\n which may have script-set OR active-script-set\n OR \test script-set on any adjacency\ configured \n which is not supported on the peer.\n SBC cannot proceed as HA client.\n Remove all sdp editing config to proceed with ISSU/ISSD.\n |
Peer SBC does not support sdp editing configuration. |
sbc-ha |
"Manually remove sdp editing configuration " "and reinitiate ISSU." LOG_STD_ACTION |
|
SBC_HA-3-SBC_SIPS_H323_INTWK_CFG |
3-Error |
SBC has detected SIPS-H323 Interworking configured\n which may have trusted H323 Adjacencies or secure calls\n configured which is not supported on the peer.\n SBC cannot proceed as HA client.\n Remove all SIPS-H323 Interworking config to proceed with ISSU/ISSD.\n |
Peer SBC does not support SIPS-H323 Interworking configuration. |
sbc-ha |
"Manually remove SIPS-H323 Interworking configuration " "and reinitiate ISSU." LOG_STD_ACTION |
|
SBC_HA-3-SBC_SUBSCRIBER_TCP_CFG |
3-Error |
SBC has detected subscriber tcp configured\n which may have subscriber tcp incoming-only configured\n which is not supported on the peer.\n SBC cannot proceed as HA client.\n Remove all subscriber tcp config to proceed with ISSU/ISSD.\n |
Peer SBC does not support susbscriber tcp configuration. |
sbc-ha |
"Manually remove subscriber tcp configuration " "and reinitiate ISSU." LOG_STD_ACTION |
|
SBC_HA-3-SBC_VIA_PASSTHROUGH_CFG |
3-Error |
SBC has detected Via Passthrough configured\n SBC cannot proceed now.\n Remove all Via Passthrough CONFIG to proceed with ISSU/ISSD.\n |
Peer SBC does not support Via Passthrough configuration. |
sbc-ha |
"Manually remove Via Passthrough configuration " "and reinitiate ISSU." LOG_STD_ACTION |
|
SBC_HA-3-SBC_XML_BILLING_CFG |
3-Error |
SBC has detected Xml Billing configuration which is\n not supported on the peer. SBC cannot proceed as HA client.\n Remove all xml billing configuration to proceed with ISSU/ISSD.\n |
Peer SBC does not support Xml Billing configuration. |
sbc-ha |
"Manually remove Xml Billing configuration and reinitiate" " ISSU. " LOG_STD_ACTION |
|
SBC_HA-3-WATCH_PROGRESSION |
3-Error |
SBC RF failed to create progression watch points. |
The SBC module was unable to successfully create the RF progression watch points. RF progression will not be suspended at bulk synchronisation time so some SBC calls may be lost if a switchover occurs immediately after the system reaches the Standby Hot redundancy state. |
sbc-ha |
LOG_STD_ACTION |
|
SBC_HA-4-ISSU_GET_BUFFER |
4-Warning |
SBC ISSU session failed to get buffer. |
The SBC ISSU client failed to get a buffer. Some High-Availability SBC information may be missing from the peer. |
sbc-ha |
"show processes memory" |
|
SBC_MPS-3-ENQUEFAIL |
3-Error |
Enqueue of TDL message failed [chars]. |
- |
- |
- |
|
SBC_MPS-3-INITFAIL |
3-Error |
SBC module initialisation failure: [chars]. |
An unexpected condition has occurred which resulted in the module being unable to initialise. |
asr1k-sbc |
LOG_STD_ACTION |
|
SBC_MPS-3-INTERNAL |
3-Error |
An internal IOSd SBC error has been encountered[chars]. |
An internal error has been encountered. |
asr1k-sbc |
LOG_STD_ACTION |
|
SBC_MPS-3-MAX_RESOURCES |
3-Error |
The maximum resource limit has been reached. |
The system was asked to allocate more resources but the maximum\n\ resource limit had already been reached |
asr1k-sbc |
LOG_STD_ACTION |
|
SBC_MPS-3-UNEXPECTED_TIMOUT |
3-Error |
An unexpected timeout has been encountered by SBC [chars]. |
A timeout was experienced by the IOSd SBC subsystem but no such\n\ timeout should have occurred. The system will ignore the timeout and\n\ continue operating. |
asr1k-sbc |
LOG_STD_ACTION |
|
SBC_MPS-4-MPF_CAPABILITIES |
4-Warning |
SBC MPF Capabilities handling failure. |
SBC has been unable to properly prepare a Media Packet Forwarding capabilities message. SBC may not be able to support select functionality such as transcoding or SRTP. |
asr1k-sbc |
LOG_STD_ACTION |
|
SBC_MPS-4-MPF_SRTP_CAPABILITIES |
4-Warning |
Unable to set SRTP capabilities |
SBC made an attempt to set the platform capabilities with respect to its handling of SRTP streams and was not successful. SRTP streams will not be handled through the SBC. |
asr1k-sbc |
LOG_STD_ACTION |
|
SBC_MPS-4-NEW_MPF_CAPABILITIES |
4-Warning |
New SBC MPF Capabilities handling failure. |
SBC has received a new set of Media Packet Forwarding capabilities from the associated Forwarding Processor that are inconsistent with those already in use. SBC was unable to process these new capabilities online and will automatically restart. |
asr1k-sbc |
LOG_STD_ACTION |
|
SBC_MPS-4-TRANSCODE_MPF_CAPABILITIES |
4-Warning |
Transcoding SBC MPF Capabilities handling failure. |
SBC has been unable to prepare a transcoding supported Media Packet Forwarding capabilities message. SBC will not be able to support transcoding functionality. |
asr1k-sbc |
LOG_STD_ACTION |
|
SBC_MPS-4-UNEXPECTED_PKT |
4-Warning |
An unexpected packet for call [dec] has been received by SBC. |
A packet been received by SBC for the noted call but the call was not\n\ in a correct state to handle it. The system will ignore the packet and\n\ continue operating. |
asr1k-sbc |
LOG_STD_ACTION |
|
SBC_MPS-6-DEACTIVATE_NO_RSP |
6-Information |
SBC deactivate response is considered lost. |
The response for SBC deactivate can get lost due to FP startup or switchover while deactivation is in progress. |
asr1k-sbc |
"SBC can be activated now if needed." |
|
SBC_MPS-6-DEACTIVATE_RESPONSE |
6-Information |
SBC deactivate is complete. |
SBC deactivation can take a while. This happens when SBC deactivation is done in the presence of a lot calls with deactivation-mode set to abort. SBC deactivate is now complete. |
asr1k-sbc |
"SBC can be safely activated now if needed." |
|
SBC_MPS-6-UNEXPECTED_TDL |
6-Information |
An unexpected message [chars] has been received by SBC while in the |
An internal message has been received by SBC but it was not expecting\n\ that message at that particular time. The system will ignore the\n\ message and continue operation. |
asr1k-sbc |
LOG_STD_ACTION |
|
SBC_SPF-3-ENQUEFAIL |
3-Error |
Enqueue of TDL message failed [chars]. |
- |
- |
- |
|
SBC_SPF-3-INTERNAL |
3-Error |
An internal IOSd SBC error has been encountered[chars]. |
An internal error has been encountered. |
iosxe-sbc |
LOG_STD_ACTION |
|
SBC_SPF-3-NOT_FOUND |
3-Error |
An unsolicited message has been received by SBC [chars] [dec] |
- |
- |
- |
|
SBC-2-IPC_INIT |
2-Critical |
IPC message handler registration failure rc [dec] |
Registering an IPC message handler for the SBC feature failed. This will cause the feature not to function. The function |
cpp-sbc |
"This is normally a software issue. " "The consequences are that the SBC feature will not function. " LOG_STD_ACTION |
|
SBC-3-FEAT_DOWN |
3-Error |
Invalid request [chars] while feature down call id [dec] |
While the feature was not active an invalid request was received from another layer of the SBC software stack for the specified call ID. Some requests do not have an associated call ID. For them the displayed call ID is zero. |
cpp-sbc |
"This is a software issue. The consequences " "could be limited to only one or a few calls. " LOG_STD_RECUR_ACTION |
|
SBC-3-FEAT_UP |
3-Error |
Invalid request [chars] while feature up |
While the feature was active an invalid request was received from another layer of the SBC software stack. |
cpp-sbc |
"This is a software issue. " "There are no consequences as this can only have been an Init request " "while the feature was already active. " LOG_STD_RECUR_ACTION |
|
SBC-3-IPC_NORES |
3-Error |
No space for the IPC reply size [dec] |
For a request from upper SBC software stack layers it was not possible to allocate space for a reply for the specified size. The consequence of this could be a stuck call that cannot be established etc. In rare cases this could also affect other operations such as feature activation deactivation modification High-Availability switchover operations. |
cpp-sbc |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
SBC-3-IPC_OPEN_REPLY |
3-Error |
IPC Open Reply failed request [dec] |
For a request from upper SBC software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck call that cannot be established etc. In rare cases this could also affect other operations such as feature activation deactivation modification High-Availability switchover operations. |
cpp-sbc |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
SBC-3-MEM_INIT_FAILED |
3-Error |
Allocation of [chars] memory failed for SBC |
SBC Initialization of channel pool failed. |
cpp-sbc |
LOG_STD_ACTION |
|
SBC-3-NO_RES |
3-Error |
[chars] resource not available for the [chars] request call id [dec] |
The specified software resource was not available or could not be located for the specified request from upper SBC software stack layers for the specified call ID. |
cpp-sbc |
"This is a software issue. The consequences " "are that the specified request could not be performed. " LOG_STD_RECUR_ACTION |
|
SBC-3-PKT_REPLICA_INIT_FAILED |
3-Error |
Register to Generic Packet Replication failed for SBC |
SBC Initialization of packet replication registration failed. |
cpp-sbc |
LOG_STD_ACTION |
|
SBC-3-SSL_APPL_REG_FAILED |
3-Error |
QFP SBC Websocket register to SSL library failed |
Cisco internal software error. QFP SBC WS feature initialization detected that the SSL library registration failed. QFP SBC WS will not be functional while this condition exists. |
cpp-sbc |
LOG_STD_ACTION |
|
SCC-3-XCVR_BAD_ID_HW |
3-Error |
Failed identification test in [dec]/[dec]/[dec]. |
The Transceiver in the specified port has failed authentication. |
spa-infra |
LOG_STD_ACTION |
|
SCCP_ALG-3-CHUNK_CREATE_FAIL |
3-Error |
- |
Chunk create failed. SCCP ALG will not be able to finish initialization. |
cpp-ucode |
LOG_STD_ACTION |
|
SCCP_ALG-3-INCOMPATIBLE_HA_MSG_LEN |
3-Error |
rcvd:[hec] expect:[hec] |
Incompatible HA Message Length. SCCP ALG will reject sync data. |
cpp-ucode |
LOG_STD_ACTION |
|
SCCP_ALG-3-INCOMPATIBLE_HA_VERSION |
3-Error |
rcvd:[hec] expect:[hec] |
Incompatible HA Version. SCCP ALG will reject sync data. |
cpp-ucode |
LOG_STD_ACTION |
|
SCCP_ALG-3-INCORRECT_HA_MAGIC |
3-Error |
rcvd:[hec] expect:[hec] |
Incorrect HA MAGIC. SCCP ALG will reject sync data. |
cpp-ucode |
LOG_STD_ACTION |
|
SCCP_ALG-3-INVALID_HA_OPCODE |
3-Error |
rcvd:[hec] expect:[hec] |
Invalid HA opcode. SCCP ALG will reject sync data. |
cpp-ucode |
LOG_STD_ACTION |
|
SCCP-0-PANIC |
0-Emergency |
[chars] |
Unrecoverable Internal Panic |
sccp |
LOG_STD_ACTION |
|
SCCP-1-ALERT |
1-Alert |
[chars] |
A condition that should be corrected immediately. |
sccp |
LOG_STD_ACTION |
|
SCCP-2-CRITICAL |
2-Critical |
[chars] |
Critical Conditions |
sccp |
LOG_STD_ACTION |
|
SCCP-3-ERROR |
3-Error |
[chars] |
Errors |
sccp |
LOG_STD_ACTION |
|
SCCP-4-WARNING |
4-Warning |
[chars] |
Warning |
sccp |
LOG_STD_ACTION |
|
SCCP-5-NOTICE |
5-Notice |
[chars] |
Notice |
sccp |
LOG_STD_ACTION |
|
SCCP-6-INFO |
6-Information |
[chars] |
Informational |
sccp |
LOG_STD_NO_ACTION |
|
SCHED_TEST-2-EXITHOOK |
2-Critical |
Exit routine invoked for process [chars]. |
- |
- |
- |
|
SCHED_TEST-6-ERRMSG |
6-Information |
This errmsg should print correctly. |
- |
- |
- |
|
SCHED-2-ATTRCMD |
2-Critical |
Attempt to [chars] attribute [chars] on process [dec]. |
Each process has various public and private attributes associated with it. This message indicates that an attempt was made to set or get a private attribute belonging to another process. |
- |
LOG_STD_ACTION |
|
SCHED-2-ATTRVALUE |
2-Critical |
Attempt to set bad [chars] value [hec] on process [dec] |
Each process has various attributes associated with it. This message indicates that an attempt was made to set the specified attribute to an invalid value. |
- |
"Copy the error message exactly as it appears and report it " "to your technical support representative." |
|
SCHED-2-EDISMSCRIT |
2-Critical |
Critical/high priority process [chars] may not dismiss. |
Scheduler was running for a long time and so caused the system to reset |
os |
LOG_STD_RECUR_ACTION |
|
SCHED-2-MESSAGE |
2-Critical |
Key [chars] does not match key [chars] of process [dec] in process_send_message request |
An attempt was made to send a message to a process. The key associated with that process did not match the key in the message. This usually means an incorrect process id was used in the send message request. |
Determine the component by extracting the first word in the first set of parantheses |
- |
|
SCHED-2-NOATTR |
2-Critical |
Attempt to [chars] unknown process attribute [dec]. |
Each process has various attributes associated with it. This message indicates that an attempt was made to set or get a nonexistent process attribute. |
- |
LOG_STD_ACTION |
|
SCHED-2-NOTWATCHTIMER |
2-Critical |
[chars] timer [hec] not being watched. |
A process can register to be notified when various events occur in the\n\ router. This message indicates that an attempt was made to deregister a \n\ timer expiration event that is not currently registered. |
- |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
SCHED-2-QUEUENOTEMPTY |
2-Critical |
Attempt to delete non-empty watched queue [chars] address [hec]. |
A process can register to be notified when various events occur in the\n\ router. This message indicates that an attempt was made to destroy a queue that\n\ still contained items. These items are lost and not returned to free\n\ memory. |
- |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
SCHED-2-SEMNOTLOCKED |
2-Critical |
[chars] attempted to unlock an unlocked semaphore |
Some sections of code use semaphores to protect critical sections of\n\ software. This message indicates that an attempt was made to unlock a\n\ semaphore that was not locked. |
- |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
SCHED-2-SEMUNLOCK |
2-Critical |
[chars] attempted to unlock semaphore owned by [chars] PID: [dec]. |
- |
- |
- |
|
SCHED-2-SETHIGHORCRIT |
2-Critical |
Attempt to set [chars] priority on process [dec] [chars] |
Each process executes at a specified priority level. Higher priority\n\ processes must use the new scheduler primitives while lower priority\n\ processes can use primitives from either the new or old scheduler.\n\ This message indicates that an attempt was made to set the specified priority too\n\ high for a process using old scheduler primitives. |
- |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
SCHED-3-CORRUPT |
3-Error |
Scheduler '[chars]' corrupted by process [chars] expected [hec] found [hec] |
- |
- |
- |
|
SCHED-3-INTSETWAKEUP |
3-Error |
Invalid scheduler action [chars] at interrupt level |
This message indicates that a process_set_wakeup_reasons was attempted from an interrupt handler. |
- |
"If this message recurs call your technical support representative for " "assistance." |
|
SCHED-3-LOSTWAKEUP |
3-Error |
Wakeup information for process [chars] lost maj [hec] min [hec]. |
A process can register to be notified when various events occur in the router. This message indicates that an event for the specified process was lost and that the system might not be functioning correctly. |
- |
- |
|
SCHED-3-PAGEZERO |
3-Error |
Low memory modified by [chars] [hex] = [hex] |
In all Cisco products the first 256 bytes of memory are unused and are\n\ off limits. Newer platforms have hardware to immediately trap reads or\n\ writes to this area. Older platforms periodically check \n\ this memory. This message appears only on older platforms and\n\ indicates that this off-limits memory area was modified. |
- |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
SCHED-3-PRIORITY |
3-Error |
Illegal priority [dec] specified for process [chars]. |
Each process executes at a specified priority level. Higher priority\n\ processes must use the new scheduler primitives while lower priority\n\ processes can use primitives from either the new or old scheduler.\n\ This message indicates that an attempt was made to set the specified process \n\ to a priority level that is not allowed for the type of scheduler\n\ primitives used. |
- |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
SCHED-3-SEMLOCKED |
3-Error |
[chars] attempted to lock a semaphore already locked by itself |
Some sections of code use semaphores to protect critical sections of software. This message indicates that an attempt was made to lock a semaphore that was already locked. |
- |
"Copy the error message exactly as it appears and report it " "to your technical support representative." |
|
SCHED-3-STACKSIZE |
3-Error |
Illegal stack size [dec] specified for process [chars]. |
Each process has its own stack space which must be one of several predefined sizes. This message indicates that an attempt was made to specify an illegal stack size. |
- |
- |
|
SCHED-3-STILLWATCHING |
3-Error |
Process still watching [chars] [chars] |
A process can register to be notified when various events occur in the\n\ router. This message indicates that a process destroyed a set of\n\ events without first individually removing each event in the set. |
- |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
SCHED-3-STILLWATCHINGT |
3-Error |
Process still watching [chars] timer [hec] |
A process can register to be notified when various events occur in the\n\ router. This message indicates that a process destroyed a set of\n\ events without first individually removing each event in the set. |
- |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
SCHED-3-STUCKMTMR |
3-Error |
Sleep with expired managed timer [hec] time %#Ta %TE ago. |
A process can register to be notified when various events occur. This message indicates that a registered timer has expired and its value is unchanged after the process has received control twice. |
- |
- |
|
SCHED-3-STUCKTMR |
3-Error |
Sleep with expired timer [hec] time %#Ta %TE ago. |
A process can register to be notified when various events occur. This message indicates that a registered timer has expired and its value is unchanged after the process has received control twice. |
- |
- |
|
SCHED-3-THRASHING |
3-Error |
Process thrashing on watched [chars]. |
A process can register to be notified when various events occur. This message indicates that the indicated process relinquished control 50 consecutive times and there were still outstanding events to be processed. |
- |
- |
|
SCHED-3-UNEXPECTEDEVENT |
3-Error |
Process received unknown event maj [hec] min [hec]. |
A process can register to be notified when various events occur in the\n\ router. This message indicates that a process received an event it\n\ did not know how to handle. |
- |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
SCHED-3-UNEXPECTEDMESSAGE |
3-Error |
Unknown message [hec] received ptr arg [hec] num arg [hec]. |
A process can register to be notified when various events occur in the\n\ router. This message indicates that a process received a message from\n\ another process that it does not know how to handle. |
- |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
SCHED-3-UNEXPECTEDQUEUE |
3-Error |
Queue event for unknown queue index [dec]. |
A process can register to be notified when various events occur in the\n\ router. This message indicates that a process received a queuing\n\ event for an unknown queue. |
- |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
SCHED-3-UNEXPECTEDTIMER |
3-Error |
Unknown timer expiration timer = [hec] type [dec]. |
A process can register to be notified when various events occur in the\n\ router. This message indicates that a process received a timer\n\ expiration event for an unknown timer. |
- |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
SCHED-4-NO_PREEMPT_CTXT |
4-Warning |
[chars] is preempting [chars] without preemption context. Preemption is [chars] and [chars]. preempted_process_epc = 0x%p |
This message indicates that the IOS scheduler is preparing to schedule a preemptive process but the preempted process does not have a preemption context allocated to it. |
- |
- |
|
SCHED-4-PROCESSTIME |
4-Warning |
Invalid argument [dec] msec for process_set_schedtime |
This message indicates that there was an attempt to change the maximum time a process can run per scheduling to an invalid value. The value should range between 20msec to 200msec |
Determine the component from the process name and the stack trace from the error message |
- |
|
SCHED-5-INT_DISABLED_BEFORE_PREEMPTION |
5-Notice |
Detected interrupts being disabled in preemption handler. schedflag = [dec] forkx = [chars] preempted process = [chars] |
This message indicates that the interrupt enable bit is unexpectedly found to be disabled in preemption handler before servicing the ready to run preemptive processes. |
- |
"If this message recurs just report it your technical support " "representative. However the functionality is not impacted. " |
|
SCHED-7-WATCH |
7-Debug |
Attempt to [chars] uninitialized watched [chars] address [hec]. |
A processes can register to be notified when various events occur. This message indicates that an attempt was made to register for an event without first creating the data structure for that event. |
- |
LOG_STD_RECUR_ACTION |
|
SCP-3-BADVLAN |
3-Error |
Rx'd VLAN [dec] opcode 0x[hec] from the NMP which is not configured. |
The NMP sent a config command for an unconfigured VLAN interface. |
- |
"Configure VLAN interface." |
|
SCP-3-NOPROC |
3-Error |
Cannot create SCP process. |
Insufficient internal resource available to create queue. |
- |
"Check available memory capacity on router." |
|
SCP-3-NOQUEUE |
3-Error |
Cannot create SCP Rx/Tx queue. |
Insufficient internal resource available to create queue. |
- |
"Check available memory capacity on router." |
|
SCP-3-UNKMSG |
3-Error |
Unknown SCP message opcode 0x[hec] received. |
The remote peer sent an SCP message we don't know about. |
- |
"Check software compatibility between peers." |
|
SCRIPT_INSTALL-3-SCRPT_FAILED |
3-Error |
Script execution failed: [chars] |
The script file execution encountered an error and failed. |
script_install |
"This message indicates an internal error in preparing the " "execution of the script. Usually another message with more " "details of the kind of failure is printed on the console. " "Please collect these details and forward to your Cisco " "technical support representative." |
|
SCRIPT_INSTALL-3-SCRPT_TYPE_NOT_MATCHED |
3-Error |
Script file format invalid: [chars] |
The system was able to access and open the script file but file format doesn't contain the expected preamble or the filename doesn't contain the expected extension. The script execution failed as a result of this error. |
script_install |
"Ensure that the script file contains the expected preample " "in order for it to be accepted as a sintalation script." |
|
SCRIPT_INSTALL-3-SCRPT_UNABLE_TO_OPEN_FILE |
3-Error |
Unable to open file [chars] |
The script file cannot be opened. |
script_install |
"Check that the script location exists and the file can be accessed " "from the device that tries to access that file for execution." "this is most likely a setup issue." |
|
SCRIPT_INSTALL-3-SCRPT_UNABLE_TO_READ_FILE |
3-Error |
Unable to read the file [chars] |
The script file cannot be read. |
script_install |
"Check that the script file can be read. " "This checking can be done independent of the device that is trying " "read this file." |
|
SCRIPT_INSTALL-3-SCRPT_UNEXPECTED_FILE_TYPE |
3-Error |
File is not a script file or not containing ASCII text: [chars] |
The script file seems to contain non-ascii text or non-script text. |
script_install |
"The specified file has to be a script file e.g. TCL script file. " "Check the file URL that it points to a script file." |
|
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_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_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." |
|
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_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_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." |
|
SDB_UPDATE-2-LDP |
2-Critical |
ERRMSG_NOFLAGS |
- |
- |
- |
|
SDFLASH-1-DEVICE_DISABLED |
1-Alert |
SDFlash device disabled |
SDFlash device is disabled from the system. Please enable it for correct operation of the switch. |
- |
LOG_STD_ACTION |
|
SDFLASH-6-DEVICE_ENABLED |
6-Information |
SDFlash device enabled |
SDFlash device is enabled in the system. |
- |
LOG_STD_NO_ACTION |
|
SDH-4-SNCP |
4-Warning |
Protection-Group [dec] [chars] [chars] |
There has been a protection switch on the protection group |
- |
"None - normal situation" |
|
SDLC-2-ILLEGSTATE |
2-Critical |
[chars] illegal state for addr %02x [chars][dec] |
An internal SDLC state violation was detected. |
- |
LOG_STD_SH_TECH_ACTION |
|
SDLC-2-NOMEMORY |
2-Critical |
No memory available: [chars] |
The requested operation failed because of a low memory condition. |
- |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
SDLC-2-NOPOINTER |
2-Critical |
AW_SDLC_SEC with no sdllc_llc pointer. |
An error condition occurred during SDLLC initiation. |
- |
"No action is required. The SDLLC session will restart without operator\n\ intervention." |
|
SDLC-3-CONFIGERR |
3-Error |
[chars] addr %02x Sent SNRM received SNRM. Check link station roles. |
A hardware or software error occurred. |
- |
LOG_STD_ACTION |
|
SDLC-3-DLU_ERROR |
3-Error |
[chars] DLU failed to close station %02x before re-opening [chars]/[chars] |
A hardware or software error occurred. |
- |
LOG_STD_ACTION |
|
SDLC-3-NOINPIDB |
3-Error |
Input idb not set |
This is a software error. A frame was given to the SDLC handler to\n\ process but the interface on which the frame arrived is not known. |
- |
LOG_STD_SH_TECH_ACTION |
|
SDLC-3-NULLPAK |
3-Error |
Interface [chars] NULL packet ptr rvr [dec] vs [dec] vr [dec] |
An internal software error occurred in the router's SDLC processing\n\ system. |
- |
LOG_STD_SH_TECH_ACTION |
|
SDLC-4-BADFRAME |
4-Warning |
[chars] Received bad SDLC [chars]frame address %02x control %2X |
A hardware or software error occurred. |
- |
LOG_STD_ACTION |
|
SDLC-4-CTRLBAD |
4-Warning |
Interface [chars] Invalid control field |
A bad SDLC frame was received. |
- |
"If this message recurs check the SDLC serial line and the devices\n\ attached to it." |
|
SDLC-4-DROPPED |
4-Warning |
Dropped SDLC packet from SDLC hold queue |
An SDLC frame had to be dropped from the output hold queue usually\n\ because of excessive congestion on the output link. |
- |
"If this message occurs frequently determine why your SDLC link is\n\ being overloaded with data and resolve the cause typically by either\n\ increasing bandwidth to your SDLC line or reducing the load on your\n\ link." |
|
SDLC-4-FRAMEERR |
4-Warning |
Interface [chars] Frame error: CF [hex] VS [dec] [chars] VR [dec] Reason [hex] |
A FRMR frame was received. This can be due to a noisy serial line an\n\ overloaded SDLC device or corrupted data. |
- |
"If this message recurs service the serial line and the devices\n\ attached to it." |
|
SDLC-4-INFOBAD |
4-Warning |
Interface [chars] Info field not permitted |
A bad SDLC frame was received. |
- |
"If this message recurs check the SDLC serial line and the\n\ devices attached to it." |
|
SDLC-4-INVLDGRPCFG |
4-Warning |
Interface [chars] ignoring group-poll mismatch UPOLL %02x |
A hardware or software error occurred. |
- |
LOG_STD_ACTION |
|
SDLC-4-INVNR |
4-Warning |
Interface [chars] Invalid NR value |
A bad SDLC frame was received. |
- |
"If this message recurs check the SDLC serial line and the\n\ devices attached to it." |
|
SDLC-4-N1TOOBIG |
4-Warning |
Interface [chars] N1 too large |
An information frame was received from the other end of the SDLC link\n\ that was larger than allowed with the N1 parameter on this link. |
- |
"Either increase the value of the N1 parameter for this interface on\n\ the router or reduce the size of the maximum information frame sent by\n\ the other end of the link." |
|
SDLC-4-NOUA |
4-Warning |
[chars] addr %02x received command %02x in response to SNRM expected UA |
The router received a frame other than a UA in response to a SNRM. |
- |
"Check the end station to see if the SNA stack is up and running." |
|
SDLC-4-SDLC_ERR |
4-Warning |
SDLC_ERROR with no poll |
A protocol error was detected on a secondary station but FRMR could\n\ not be sent because the station did not own the poll bit. This message\n\ indicates either poor line conditions or a faulty SDLC\n\ implementation. |
- |
"If this message recurs run traces on the SDLC line. Copy the error\n\ message exactly as it appears and report it to your technical support\n\ representative." |
|
SDLC-4-XID_NOMATCH |
4-Warning |
[chars] XID mismatch for %02x. CONNECTION REJECTED |
- |
- |
"This is a security feature. Additional information is displayed to\n\ help trace the source of the rejected XID. If the message is\n\ undesirable simply remove the XID statement from the router\n\ configuration." |
|
SDLC-5-INVLDGRPPOLL |
5-Notice |
Interface [chars] not configured for group-poll frame received %02x |
An unnumbered poll UP was received with the wrong group poll\n\msgdef_recommended_action Make sure the group poll address configured on the router matches the\n\ one configured in the physical unit macro |
- |
- |
|
SDLC-6-XID_DISPLAY |
6-Information |
sa [enet] da [enet] ss [hec] ds [hec] [%02x%02x%02x%02x] |
This message supplies the information for the received and rejected\n\ XID. |
- |
"See the "SDLC-6-XID_NOMATCH" error message." |
|
SDLC-6-XID_FORMAT |
6-Information |
Unsupported XID format received format [dec] |
- |
- |
"See the "SDLLC-6-XID_NOMATCH" error message." |
|
SDLLC-5-ACT_LINK |
5-Notice |
SDLLC: [chars] LINK address %02x ACTIVATED: [chars] |
An SDLLC media conversion session was activated. |
- |
LOG_STD_NO_ACTION |
|
SDLLC-5-DACT_LINK |
5-Notice |
SDLLC: [chars] LINK address %02x DEACTIVATED: [chars] |
An SDLLC media conversion session was deactivated. If deactivation is\n\ a result of an error condition this message will include a reason. |
- |
"If the message does not include a description of an error the\n\ deactivation was normal and the message is for information only. If the\n\ message does include a description of an error begin problem analysis.\n\ Determine whether session loss is related to LLC2 timers by issuing the\n\ debug llc2-err command. If the problem is related to LLC2 timers\n\ consider using SDLLC with the local acknowledgment feature. Copy the\n\ error message exactly as it appears and report it to your technical\n\ support representative." |
|
SDP-3-CONFIG_PTR_ERROR |
3-Error |
Received invalid config pointer from application. Unable to process. |
The SDP library application has an invalid configuration pointer. The SDP library is therefore unable to handle the request that it received. The configuration of the application will not be as expected and SDP parsing errors may result even for valid SDPs. |
voice-sdp |
LOG_STD_ACTION |
|
SDP-3-CONFIG_PTR_ERROR |
3-Error |
Received invalid config pointer from application. Unable to process. |
The SDP library application has an invalid configuration pointer. The SDP library is therefore unable to handle the request that it received. The configuration of the application will not be as expected and SDP parsing errors may result even for valid SDPs. |
voice-sdp |
LOG_STD_ACTION |
|
SDP-3-INTERNAL |
3-Error |
[chars] |
An internal software error has occurred. |
voice-sdp |
LOG_STD_SH_TECH_ACTION |
|
SDP-3-INTERNAL |
3-Error |
[chars] |
An internal software error has occurred. |
voice-sdp |
LOG_STD_SH_TECH_ACTION |
|
SDP-3-SDP_PTR_ERROR |
3-Error |
Received invalid SDP pointer from application. Unable to process. |
The SDP library application has an invalid SDP pointer. The SDP library is therefore unable to handle the request that it received. SDP parsing or build errors may result. |
voice-sdp |
LOG_STD_ACTION |
|
SDP-3-SDP_PTR_ERROR |
3-Error |
Received invalid SDP pointer from application. Unable to process. |
The SDP library application has an invalid SDP pointer. The SDP library is therefore unable to handle the request that it received. SDP parsing or build errors may result. |
voice-sdp |
LOG_STD_ACTION |
|
SDVT-2-IPC_FAILURE |
2-Critical |
SDVT-IPC message [chars] handler failed rc [dec] |
An IPC message handler for the SDVT feature failed. This will cause the feature to not function. |
cedge-appqoe |
LOG_STD_ACTION |
|
SDVT-2-IPC_INIT_FAILED |
2-Critical |
SDVT-IPC message handler registration failure rc [dec] |
Registering an IPC message handler for the SDVT feature failed. This will cause the feature to not function. |
cedge-appqoe |
LOG_STD_ACTION |
|
SDVT-2-SDVT_HEALTH_CHANGE |
2-Critical |
Service node %Ci changed state from [chars] => [chars] [dec] for channel [chars] |
Service node has changed health status\n |
cpp-ucode |
LOG_STD_ACTION |
|
SDVT-2-SDVT_HEALTH_DOWN |
2-Critical |
Service node %Ci is down for channel [chars]. Current Health: [chars] Previous Health: [chars] |
Service node has changed status to Down\n |
cpp-ucode |
LOG_STD_ACTION |
|
SDVT-3-FEAT_DOWN |
3-Error |
SDVT-Invalid request [chars] [dec] while feature is down |
While the feature was not active an invalid request was received from another layer of the SDVT software stack. |
cedge-appqoe |
LOG_STD_RECUR_ACTION |
|
SDVT-3-IPC_INVALID_MSG |
3-Error |
SDVT-Invalid request [dec] |
We received an invalid message from another layer of the SDVT software stack. |
cedge-appqoe |
LOG_STD_RECUR_ACTION |
|
SDVT-3-IPC_INVALID_MSG_LEN |
3-Error |
SDVT-Invalid IPC length [dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Invalid IPC message length |
cedge-appqoe |
LOG_STD_ACTION |
|
SDVT-3-IPC_NORES |
3-Error |
SDVT-No space for the IPC reply size [dec] request [dec] |
For a request from upper SDVT software stack layers it was not possible to allocate space for a reply for the specified size. |
cedge-appqoe |
LOG_STD_RECUR_ACTION |
|
SDVT-3-IPC_OPEN_REPLY |
3-Error |
SDVT-IPC Open Reply failed request [dec] |
For a request from upper SDVT software stack layers it was not possible to open the reply buffer. |
cedge-appqoe |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
SDVT-3-IPC_SEND_FAILED |
3-Error |
SDVT-IPC [chars] [dec] send failed [dec] |
IPC message send failure |
cedge-appqoe |
LOG_STD_ACTION |
|
SDVT-3-SDVT_COND_DEBUG_REG_FAILED |
3-Error |
Failed to initialize Conditional Debugging for SDVT |
A non-fatal error occurred when attempting to Register/Initialize\n conditional debugging. |
qfp-ucode |
LOG_STD_ACTION |
|
SDVT-5-SDVT_HEALTH_UP |
5-Notice |
Service node %Ci is up for channel [chars]. Current Health: [chars] Previous Health: [chars] |
Service node has changed status to Green\n |
cpp-ucode |
LOG_STD_ACTION |
|
SDVXLAN-3-VXLAN_TUN_FULL |
3-Error |
Auto-tunnel ID is running out now |
All the vxlan auto-tunnel ID through the tunnel range was used no more id available |
SDVXLAN_COMPONENT |
"If the auto-tunnel ID is running out " "will need to config the auto-tunnel range to expand it" |
|
SDWAN_PROXY-2-PROXY_IPC_INIT_FAILED |
2-Critical |
QFP SDWAN Proxy IPC interface initialization failure result: [dec]. |
Cisco internal software error. QFP SDWAN Proxy initialization detected that the IPC interface initialization failed. QFP SDWAN proxy will not be functional while this condition exists. |
qfp-sdwan keyword:sdwan |
LOG_STD_ACTION |
|
SDWAN_PROXY-2-SDWAN_MSG_PROXYINIT_FAILURE |
2-Critical |
SDWAN - Failed to register IPC message handler result code [dec] |
QFP SDWAN feature failed to register an IPC message handler for communication with control plane. This will cause the featue not to function. |
SDWAN_COMP_NAME |
LOG_STD_ACTION |
|
SDWAN_PROXY-3-PROXY_BAD_MSG |
3-Error |
QFP SDWAN Proxy received bad length message type [dec] |
Cisco internal software error. QFP SDWAN Proxy received a corrupted message from control plane. This message will be ignored. |
qfp-sdwan keyword:sdwan |
LOG_STD_ACTION |
|
SDWAN_PROXY-3-PROXY_IPC_ALLOC_FAILED |
3-Error |
QFP SDWAN Proxy [chars] message lost due to message buffer allocation failure. |
Cisco internal software error. QFP SDWAN Proxy message processing detected a message buffer allocation failure. The message is lost as the result of this condition. |
qfp-sdwan keyword:sdwan |
LOG_STD_ACTION |
|
SDWAN_PROXY-3-PROXY_IPC_SEND_FAILED |
3-Error |
QFP SDWAN Proxy [chars] message lost due to message sent failure result: [dec]. |
Cisco internal software error. QFP SDWAN Proxy message processing detected a message sent failure. The message is lost as the result of this condition. |
qfp-sdwan keyword:sdwan |
LOG_STD_ACTION |
|
SDWAN_PROXY-3-SDWAN_MEM_EXTEND_FAILED |
3-Error |
SDWAN IPC subtype: [dec] |
Extending memory failed. |
qfp-sdwan keyword:sdwan |
LOG_STD_ACTION |
|
SDWAN_PROXY-3-SDWAN_MEM_REQ_FAILED |
3-Error |
SDWAN IPC subtype: [dec] |
Requesting more memory failed. |
qfp-sdwan keyword:sdwan |
LOG_STD_ACTION |
|
SDWAN_PROXY-3-SDWAN_MSG_PROXY_ALLOC_FAILURE |
3-Error |
SDWAN - Failed to get [dec] bytes space for IPC reply message |
QFP ET-Anallytics feature detected buffer allocation failure while sending reply to a message from another layer of SDWAN feature's software stack. |
SDWAN_COMP_NAME |
LOG_STD_ACTION |
|
SDWAN_PROXY-3-SDWAN_MSG_PROXY_DEBUG_REG_FAILED |
3-Error |
- |
SDWAN Conditional Debugging Registration failed. |
SDWAN_COMP_NAME |
LOG_STD_ACTION |
|
SDWAN_PROXY-3-SDWAN_MSG_PROXY_INVALID_MSGLEN |
3-Error |
SDWAN - Received an invalid length IPC message |
QFP SDWAN feature received an incorrect length of IPC message from anoter layer of SDWAN feature's software stack m_enum [dec] m_subtype [dec] m_len [dec] m_flags 0x[hec] m_source [dec]. |
SDWAN_COMP_NAME |
LOG_STD_ACTION |
|
SDWAN_PROXY-3-SDWAN_MSG_PROXY_IPCSEND_FAIL |
3-Error |
SDWAN - Failed to send IPC message result code [dec] |
QFP SDWAN feature failed to send IPC message to another layer of SDWAN feature's software stack. |
SDWAN_COMP_NAME |
LOG_STD_ACTION |
|
SDWAN_PROXY-3-SDWAN_MSG_PROXY_OPENREPLY_FAIL |
3-Error |
SDWAN - Failed to open reply message part of IPC packet |
QFP SDWAN feature failed to open message part of IPC packet while sending a reply to another layer of SDWAN feature's software stack. |
SDWAN_COMP_NAME |
LOG_STD_ACTION |
|
SDWAN_PROXY-3-SDWAN_MSG_PROXY_UNKNOWN_IPCMSG |
3-Error |
SDWAN - Received an unknown type code [dec] IPC message |
QFP SDWAN feature received an unknown message from another layer of SDWAN feature's software stack. |
SDWAN_COMP_NAME |
LOG_STD_RECUR_ACTION |
|
SDWAN_PROXY-3-SDWAN_PROXY_HSL_ADD_DEST_FAILED |
3-Error |
- |
SDWAN HSL add destination failed. |
cpp-ucode |
LOG_STD_ACTION |
|
SDWAN_PROXY-3-SDWAN_PROXY_HSL_BIND_FAILED |
3-Error |
- |
SDWAN HSL bind failed. |
cpp-ucode |
LOG_STD_ACTION |
|
SDWAN_PROXY-3-SDWAN_PROXY_HSL_BIND_TEMPLATE_FAILED |
3-Error |
[dec] |
SDWAN HSL bind tempalte failed at given index. |
cpp-ucode |
LOG_STD_ACTION |
|
SDWAN_PROXY-3-SDWAN_PROXY_HSL_CREATE_FAILED |
3-Error |
- |
SDWAN HSL creation failed. |
cpp-ucode |
LOG_STD_ACTION |
|
SDWAN_PROXY-3-SDWAN_PROXY_HSL_ENABLE_FAILED |
3-Error |
- |
SDWAN HSL enable failed. |
cpp-ucode |
LOG_STD_ACTION |
|
SDWAN_PROXY-3-SDWAN_PROXY_HSL_MOD_CFG_FAILED |
3-Error |
- |
SDWAN HSL modify configuration failed. Currently only support rec_timeout |
cpp_ucode |
LOG_STD_ACTION |
|
SDWAN_PROXY-3-SDWAN_PROXY_HSL_MOD_DEST_FAILED |
3-Error |
- |
SDWAN HSL modify destination failed. |
cpp_ucode |
LOG_STD_ACTION |
|
SDWAN_PROXY-3-SDWAN_PROXY_HSL_PRE_SEND_HANDLER_FAILED |
3-Error |
- |
SDWAN HSL pre send handler registration failed. |
cpp-ucode |
LOG_STD_ACTION |
|
SDWAN_PROXY-4-PROXY_INVALID_MSG |
4-Warning |
QFP SDWAN Proxy received invalid message type [dec] |
Cisco internal software error. QFP SDWAN Proxy received an invalid message from control plane. This message will be ignored. |
qfp-sdwan keyword:sdwan |
LOG_STD_ACTION |
|
SDWAN_PROXY-4-PROXY_INVALID_MSG_LEN |
4-Warning |
QFP SDWAN Proxy IPC invalid length [dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Cisco internal software error. QFP SDWAN Proxy received invalid IPC message length from control plane. This message will be ignored. |
qfp-sdwan keyword:sdwan |
LOG_STD_ACTION |
|
SDWAN_PROXY-4-PROXY_IPC_INVALID_MSG_LEN |
4-Warning |
[dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Invalid SDWAN IPC message length. |
cpp-ucode |
LOG_STD_ACTION |
|
SEC_LOGIN-1-QUIET_MODE_ON |
1-Alert |
Still timeleft for watching failures is %lu secs [user: [chars]] [Source: [chars]] [localport: [dec]] [Reason: [chars]] [ACL: [chars]] at [chars] |
Quiet Mode is ON. No request for connection is accepted other than allowed by the Access List if configured for the blocking period. Else an implicity *deny all* login's will be in force |
os |
"As all the requests from other sources are blocked check ACL and add" "any source addr. if needed." |
|
SEC_LOGIN-3-INIT_FAILED |
3-Error |
Secure Login Initialization failed. [chars] |
Initialization of Secure Login Subsystem failed |
os |
- |
|
SEC_LOGIN-4-LOGIN_FAILED |
4-Warning |
Login failed [user: [chars]] [Source: [chars]] [localport: [dec]] [Reason: [chars]] at [chars] |
Invalid User Name or Password is given from terminal. |
os |
"A notification to indicate that login failed" |
|
SEC_LOGIN-4-WEBUI_LOGIN_FAILED |
4-Warning |
Login failed [user: [chars]] [Source: [chars]] [Reason: [chars]] at [chars] |
Invalid User Name or Password is given from terminal for WEBUI. |
os |
"A notification to indicate that WEBUI login failed" |
|
SEC_LOGIN-5-LOGIN_SUCCESS |
5-Notice |
Login Success [user: [chars]] [Source: [chars]] [localport: [dec]] at [chars] |
A successful login happened with the device. |
os |
"A notification that login succeeded." |
|
SEC_LOGIN-5-QUIET_MODE_OFF |
5-Notice |
Quiet Mode is OFF because [chars] at [chars] |
Quiet Mode is OFF. Router now operates in normal connection processing mode |
os |
"A notification that the device now operates in " "normal connection processing mode and the reason why it switched " "mode is also indicated with the notification." |
|
SEC_LOGIN-5-WEBLOGIN_SUCCESS |
5-Notice |
Login Success [user: [chars]] [Source: [chars]] at [chars] |
A successful login happened with the device. |
os |
"A notification that login succeeded." |
|
SEC-2-NOOPT |
2-Critical |
Box secured no option on internal packet |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
SEC-2-NOTSEC |
2-Critical |
First opt in tcb not BASIC security |
An internal software error occurred. |
- |
"If this message recurs contact your technical support\n\ representative." |
|
SEC-2-SECINS |
2-Critical |
Security opt in tcb not SECINSERT |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
SEC-3-NOMAX |
3-Error |
No default for NLESO defined |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
SEC-4-SHELFCTLRTELOPT |
4-Warning |
malformed option on vty[t-line] [chars][chars][chars][dec] len [dec] [chars] |
A packet containing shelf controller telnet options was malformed. Options were ignored or truncated. |
- |
LOG_STD_NO_ACTION |
|
SEC-4-TOOMANY |
4-Warning |
Box secured too many options on internal packet |
No room for all desired IP header options. Packet discarded. |
- |
"Configure for fewer IP header options." |
|
SEC-6-IPACCESSLOGDP |
6-Information |
list [chars] [chars] [chars] [inet] [chars]-> [inet] [dec]/[dec] %llu packet[chars] [chars] |
A packet matching the log criteria for the given access list was\n\ detected. |
- |
LOG_STD_NO_ACTION |
|
SEC-6-IPACCESSLOGNP |
6-Information |
list [chars] [chars] [dec] [inet] [chars]-> [inet] %llu packet[chars] [chars] |
A packet matching the log criteria for the given access list was\n\ detected. |
- |
LOG_STD_NO_ACTION |
|
SEC-6-IPACCESSLOGP |
6-Information |
list [chars] [chars] [chars] [inet][dec] [chars]-> [inet][dec] %llu packet[chars] [chars] |
A packet matching the log criteria for the given access list was\n\ detected. |
- |
LOG_STD_NO_ACTION |
|
SEC-6-IPACCESSLOGRL |
6-Information |
access-list logging rate-limited or missed [dec] packet[chars] |
Some packet matching logs were missed because the access list log \n\messages were rate-limited or no access list log buffers were available. |
- |
LOG_STD_NO_ACTION |
|
SEC-6-IPACCESSLOGRP |
6-Information |
list [chars] [chars] [chars] [inet] [chars]-> [inet] %llu packet[chars] [chars] |
A packet matching the log criteria for the given access list was\n\detected. |
- |
LOG_STD_NO_ACTION |
|
SEC-6-IPACCESSLOGS |
6-Information |
list [chars] [chars] [inet] %llu packet[chars] [chars] |
A packet matching the log criteria for the given access list was\n\ detected. |
- |
LOG_STD_NO_ACTION |
|
SEND-5-LCON |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
SENSORMGR-3-NOMEM |
3-Error |
Sensor manger failed to allocate memory : [chars] |
The sensor manager was not able to add a new threshold node to its database. |
sensor-mgr |
"TBD" |
|
SEP-3-MEMORY |
3-Error |
[chars] |
Sep subsystem has experienced a problem gettting the required\n\ memory to complete this operation. |
sep |
"Check system memory for other memory allocation errors and contact\n\ Technical support for problem resolution. In the absence of IOS errors\n\ upgrading the memory in the network device may be required." |
|
SEQNO_SYNC_FAILED-3-L2VPN |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
SERIAL_12IN1-1-CLOCKRATE |
1-Alert |
[chars]:Link has been brought [chars] due to clock rate change threshold configured = [dec] received clock rate = [dec] |
The received clock rate is changed from below the threshold\n\ configured to above or vice versa.. |
spa-4t |
"Check the received clock rate from the provider end and the " "clockrate threshold configuration if the clock rate goes " "below the threshold configured interface is brought down" |
|
SERIAL_12IN1-1-CLOCKRATE |
1-Alert |
[chars]:Link has been brought [chars] due to clock rate change threshold configured = [dec] received clock rate = [dec] |
The received clock rate is changed from below the threshold\n\ configured to above or vice versa.. |
spa-4t |
"Check the received clock rate from the provider end and the" " clockrate threshold configuration if the clock rate goes" " below the threshold configured interface is brought down" |
|
SERIAL_12IN1-3-SPI4_ERR |
3-Error |
SPA [dec]/[dec]: [chars] was encountered. Intr status: 0x[hec]\n |
The SPA driver detected a Hardware error condition on the SPA card. This might result in improper operation. |
- |
"The SPA driver has encountered a Hardware error on the SPA's SPI4 bus. " "Please power down and reseat the indicated SPA card. " "If the condition persists copy the error message exactly as " "it appears. Next research and attempt to resolve the issue using " "the SPA hardware troubleshooting documentation as well as the tools " "and utilities provided at " "http://www.cisco.com/public/support/tac/tools.shtml. If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " TAC_CASE_OPEN " or contact your Cisco technical support representative and provide " "the representative with the information you have gathered. Be sure to " "attach to your case the output of the <CmdBold>show logging<NoCmdBold> " "<CmdBold>show monitor event-log spa all<NoCmdBold> and " "<CmdBold>show tech-support<NoCmdBold> commands your troubleshooting " "logs and the specific error message." |
|
SERIAL_12IN1-3-SPI4_HW_ERR |
3-Error |
SPA [dec]/[dec]: [chars] was encountered.\n |
The SPA driver detected a Hardware error condition on the SPA card. This might result in improper operation. |
- |
"The SPA driver has encountered a Hardware error on the SPA's SPI4 bus." "Please power down and reseat the indicated SPA card. " "If the condition persists copy the error message exactly as " "it appears. Next research and attempt to resolve the issue using " "the SPA hardware troubleshooting documentation as well as the tools " "and utilities provided at " "http://www.cisco.com/public/support/tac/tools.shtml. If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a 'show tech-support' to " "your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
SERIAL_12IN1-3-SW_ERR |
3-Error |
[chars]: A software error was encountered at [chars]: [chars]\n |
The SPA driver detected a software error condition on the SPA card. This might result in improper operation. |
spa-4t |
"The SPA driver has encountered a software error." "Please power down and reseat the indicated SPA card. " "Copy the error message exactly as it appears and " "open a case with the Technical Assistance Center " "via the Internet at " TAC_CASE_OPEN " or contact your Cisco technical support representative and provide " "the representative with the information you have gathered. Be sure to " "attach to your case the output of the <CmdBold>show logging<NoCmdBold> " "<CmdBold>show monitor event-log spa all<NoCmdBold> and " "<CmdBold>show tech-support<NoCmdBold> commands your troubleshooting " "logs and the specific error message." |
|
SERIAL_12IN1-3-SW_ERR |
3-Error |
[chars]: A software error was encountered at [chars]: [chars]\n |
The SPA driver detected a software error condition on the SPA card. This might result in improper operation. |
- |
"The SPA driver has encountered a software error." "Please power down and reseat the indicated SPA card. " "Copy the error message exactly as it appears and" "open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a 'show tech-support' to " "your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
SERIAL_12IN1-3-SW_ERR_1 |
3-Error |
[chars]: A software error was encountered at [chars]: [chars] 0x[hec]\n |
The SPA driver detected a software error condition on the SPA card. This might result in improper operation. |
spa-4t |
"The SPA driver has encountered a software error." "Please power down and reseat the indicated SPA card. " "Copy the error message exactly as it appears and " "open a case with the Technical Assistance Center " "via the Internet at " TAC_CASE_OPEN " or contact your Cisco technical support representative and provide " "the representative with the information you have gathered. Be sure to " "attach to your case the output of the <CmdBold>show logging<NoCmdBold> " "<CmdBold>show monitor event-log spa all<NoCmdBold> and " "<CmdBold>show tech-support<NoCmdBold> commands your troubleshooting " "logs and the specific error message." |
|
SERIAL_12IN1-3-SW_ERR_1 |
3-Error |
[chars]: A software error was encountered at [chars]: [chars] 0x[hec]\n |
The SPA driver detected a software error condition on the SPA card. This might result in improper operation. |
- |
"The SPA driver has encountered a software error." "Please power down and reseat the indicated SPA card. " "Copy the error message exactly as it appears and" "open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a 'show tech-support' to " "your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
SERIAL_12IN1-3-SW_ERR_2 |
3-Error |
[chars]: A software error was encountered at [chars]: [chars] 0x[hec]/0x[hec]\n |
The SPA driver detected a software error condition on the SPA card. This might result in improper operation. |
spa-4t |
"The SPA driver has encountered a software error." "Please power down and reseat the indicated SPA card. " "Copy the error message exactly as it appears and " "open a case with the Technical Assistance Center " "via the Internet at " TAC_CASE_OPEN " or contact your Cisco technical support representative and provide " "the representative with the information you have gathered. Be sure to " "attach to your case the output of the <CmdBold>show logging<NoCmdBold> " "<CmdBold>show monitor event-log spa all<NoCmdBold> and " "<CmdBold>show tech-support<NoCmdBold> commands your troubleshooting " "logs and the specific error message." |
|
SERIAL_IM-3-ANALYZE_FAILURE |
3-Error |
Failed to analyze object for slot [dec]/[dec] spa_type [dec]. [chars]. |
Failed to analyze an Interface Module object. |
wolfeisland-sw |
LOG_STD_SH_TECH_ACTION |
|
SERIAL_IM-3-CREATION_FAILURE |
3-Error |
Failed to create object for slot [dec]/[dec] spa_type [dec]. |
Failed to create an Interface Module object. |
wolfeisland-sw |
LOG_STD_SH_TECH_ACTION |
|
SERIAL_IM-3-PLUGIN_INIT |
3-Error |
Plugin init failed for slot [dec]/[dec]. Action: [chars]. |
Plugin init failed UEA |
wolfeisland-sw |
LOG_STD_SH_TECH_ACTION |
|
SERIAL_IM-3-PLUGIN_START |
3-Error |
Plugin start failed for slot [dec]/[dec]. Action: [chars] |
Pointer to a UEA object is NULL. |
wolfeisland-sw |
LOG_STD_SH_TECH_ACTION |
|
SERVER_CLOCK_SYNC-3-BADREQ |
3-Error |
bad request - [chars] - from client - [chars] |
An internal software error occurred. |
os |
"If this message recurs copy it exactly as it appears and report\n\ it to your technical support representative." |
|
SERVER_CLOCK_SYNC-3-CREATEBOOL |
3-Error |
watched boolean creation failure. bool [chars] |
An internal software error occurred. |
os |
"If this message recurs copy it exactly as it appears and report\n\ it to your technical support representative." |
|
SERVER_CLOCK_SYNC-3-LISTCREATE |
3-Error |
list creation failure |
An internal software error occurred. |
os |
"If this message recurs copy it exactly as it appears and report\n\ it to your technical support representative." |
|
SERVER_CLOCK_SYNC-3-LOCATE |
3-Error |
could not locate port [chars] |
An internal software error occurred. |
os |
"If this message recurs copy it exactly as it appears and report\n\ it to your technical support representative." |
|
SERVER_CLOCK_SYNC-3-PORTCREATE |
3-Error |
cannot create port [chars] due to [chars] |
An internal software error occurred. |
os |
"If this message recurs copy it exactly as it appears and report\n\ it to your technical support representative." |
|
SERVER_CLOCK_SYNC-3-PORTOPEN |
3-Error |
cannot open port [chars] due to [chars] |
An internal software error occurred. |
os |
"If this message recurs copy it exactly as it appears and report\n\ it to your technical support representative." |
|
SERVER_CLOCK_SYNC-3-PORTREG |
3-Error |
cannot register port [chars] due to [chars] |
An internal software error occurred. |
os |
"If this message recurs copy it exactly as it appears and report\n\ it to your technical support representative." |
|
SERVICE_CHAIN-3-ALLOC_FAILED |
3-Error |
Allocation of [chars] memory failed for Service Chaining feature |
Allocation of memory by the Service Chaining feature microcode failed. The name of the memory chunk is specified in the message. This indicates a software failure |
iosxe-servicechain |
LOG_STD_ACTION |
|
SERVICE_CHAIN-3-PKT_REPLICA_INIT_FAILED |
3-Error |
Failed to register with generic packet replication for Service Chaining feature |
Service Chaining initialization of packet replication registration failed. |
iosxe-servicechain |
LOG_STD_ACTION |
|
SERVICE_CONTROLLER-3-HA_BULK_SYNC_FAIL |
3-Error |
rg [dec] |
There was a failure such that service controller bulk sync did not occur |
service-controller |
LOG_STD_ACTION |
|
SERVICE_CONTROLLER-3-HA_INVALID_STATE |
3-Error |
state [dec] |
An invalid HA state was received from the HA infrastructure. |
service-controller |
LOG_STD_ACTION |
|
SERVICE_GROUP-3-SG_CREATION_ERROR |
3-Error |
An error is detected when creating Service Group [dec] [chars] |
An error was detected when creating a service group. The failure most likely occurred because of a software error. |
ether-infra |
"Please copy the error message exactly as it appears and report it " "to your technical support representative." |
|
SERVICE_GROUP-3-SG_DELETION_ERROR |
3-Error |
An error is detected when deleting Service Group [dec] [chars] |
An error was detected when deleting a service group. The failure most likely occurred because of the group is not configured or a software error. |
ether-infra |
"If the group is configured please copy the error message exactly " "as it appears and report it to your technical support " "representative." |
|
SERVICE_GROUP-3-SG_INTERNAL_ERROR |
3-Error |
Service Group detected an internal error [chars] [dec] |
An internal error was detected by the service group software. |
ether-infra |
"Please copy the error message exactly as it appears and report it " "to your technical support representative." |
|
SERVICE_GROUP-3-SG_IPC_TRANSMIT_FAILED |
3-Error |
Service Group IPC message transmission failure [chars] |
An error was detected when transmitting an IPC message between route processor and linecard. The failure most likely occurred because of a software error. The message output identifies the type of error that occurred. |
ether-infra |
"This could be a transient error. If this error persists " "copy the error message exactly as it appears and report it " "to your technical support representative." |
|
SERVICE_MODULE-0-INITFAILURE |
0-Emergency |
Unit [chars] - failed to create data structures used for module-access |
The CSU/DSU driver failed to allocate memory for its data structures.\n\ This is a catastrophic error. The system has crashed. |
low-serial |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SERVICE_MODULE-0-INITWICFAILURE |
0-Emergency |
Unit [chars] - failed to download properly |
The CSU/DSU driver detected a checksum error while downloading WIC firmware. |
low-serial |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SERVICE_MODULE-3-LOOPDOWNFAILED |
3-Error |
Unit [chars] - WARNING - Loopdown of remote unit failed |
A remote CSU is looping pings/test patterns back to the system. This\n\ error could be triggered if the user disabled loopbacks on the remote\n\ CSU after placing the remote CSU into remote loopback. |
low-serial |
"Execute a clear command on the remote CSU." |
|
SERVICE_MODULE-4-ACCESSERROR |
4-Warning |
Unit [chars] reports register access error - [chars] |
This message indicates that the T1 module supplied a bad register\n\ address. It might be due to having a new version of the module\n\ operating with an old Cisco IOS software image. |
low-serial |
"Update the Cisco IOS software image on the system. If this does not\n\ solve the problem copy the error message exactly as it appears and\n\ report it to your technical support representative." |
|
SERVICE_MODULE-4-ALARMFAILURE |
4-Warning |
Unit [chars] - Could not access alarm status - disabling alarm processing |
The system issued an alarm interrupt but could not read the alarm\n\ status register from the module. This caused the system to disable\n\ alarm processing. |
low-serial |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SERVICE_MODULE-4-BADTYPE |
4-Warning |
Unit [chars] - reports incompatible module type [dec] against router hw detect |
A register read request returned an identity for a module which was\n\ not the same as the identity reported by the router hardware pinout. |
low-serial |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SERVICE_MODULE-4-COMMANDFAILED |
4-Warning |
Unit [chars] not ready/responding after register [dec] access command issued |
The system did not receive a ready signal within the allotted time\n\ after writing to the command register. |
low-serial |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SERVICE_MODULE-4-INTERBYTETIMEOUT |
4-Warning |
Unit [chars] - timed out while [chars] byte [dec] of [dec] length register [dec] |
The module took more than two seconds to respond between bytes. |
low-serial |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SERVICE_MODULE-4-NOTREADY |
4-Warning |
Unit [chars] not ready for register access |
The module was waiting for a ready status before executing a\n\ read/write request. The system reported a not ready status for 5\n\ seconds. This caused the module to terminate the read/write request. |
low-serial |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SERVICE_MODULE-4-OLDIMAGE |
4-Warning |
Unit [chars] - router image older than module version - access errors may be seen |
The Cisco IOS software image does not recognize the PROM software\n\ version number on the module. The system displays this message if the\n\ PROM has been upgraded to a new version but the Cisco IOS software\n\ image has not been upgraded. |
low-serial |
"Upgrade the Cisco IOS software image." |
|
SERVICE_MODULE-4-REPEATEDRESET |
4-Warning |
Unit [chars] - giving up after [dec] repeated resets couldn't bring module up again |
The software issued several clear service-module requests to the\n\ module. The module did not respond to these requests. |
low-serial |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SERVICE_MODULE-4-REQUESTOVERLOAD |
4-Warning |
Unit [chars] - module request overload - lock access timeout |
The system employs a Cisco IOS scheduler semaphore object to ensure\n\ mutually exclusive access across software threads to the CSU/DSU. This\n\ message indicates that a thread had to wait for more than 5 seconds on\n\ this semaphore. |
low-serial |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SERVICE_MODULE-4-RESETFAILURE |
4-Warning |
Unit [chars] - failed to create reset process - non-default module configuration may be lost |
To execute a reset the Cisco IOS software needs to initiate a\n\ separate process. The Cisco IOS software did not have sufficient memory\n\ to create this separate process. The module came up in an initialized\n\ state with the default configuration. The user defined configuration\n\ may have been lost. |
low-serial |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SERVICE_MODULE-4-UNKNOWNALARM |
4-Warning |
Unit [chars] reports unknown network alarms - alarm status reg = [hec] |
A recent version of the module operating with an old Cisco IOS\n\ software image did not recognize an alarm condition. |
low-serial |
"Update the Cisco IOS software image on the system. If this does not\n\ solve the problem copy the error message exactly as it appears and\n\ report it to your technical support representative." |
|
SERVICE_MODULE-4-WICNOTREADY |
4-Warning |
Unit [chars] not ready for next command |
The module was waiting for the current request to be processed\n\ before sending the next request. The current request has been in progress\n\ for more than 3 seconds. |
low-serial |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SERVICE_MODULE-5-LOOPDOWNREMOTE |
5-Notice |
Unit [chars] - Remote loopback test cancelled |
A hardware or software error occurred. |
low-serial |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative for assistance." |
|
SERVICE_MODULE-5-LOOPUPFAILED |
5-Notice |
Unit [chars] - Loopup of remote unit failed |
This notification message indicates that the loopback on the remote\n\ unit failed. The failure may indicate that the network connection is\n\ broken or that loopbacks are disabled at the other side. |
low-serial |
"Check that the router is connected to the network. Enable "loopbacks"\n\ on the remote unit. If the problem persists copy the error message\n\ exactly as it appears and report it to your technical support\n\ representative." |
|
SERVICE_MODULE-5-LOOPUPREMOTE |
5-Notice |
Unit [chars] - Remote unit placed in loopback |
This notification message indicates that the user executed a loopback\n\ command on the remote unit. The remote unit is now in loopback. |
low-serial |
"No action is required." |
|
SERVICE_MODULE-5-RESET |
5-Notice |
Reset of Unit [chars] issued |
This message indicates that the module was reset. |
low-serial |
"No action is required." |
|
SFF8472_FLOAT-3-INTERNAL_ERROR |
3-Error |
[chars] |
The SFF8472 floating point subsystem encountered an internal\n\ software error. The error message contains text which can be used\n\ to help identify the nature of the problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
SFF8472-2-NOMEM |
2-Critical |
Not enough memory available for [chars] |
There has been a threshold violation as specified in the message.\n\ If the violation has occured only during bootup/OIR/link up/down\n\ you may ignore the message. Otherwise the violations in optical\n\ tx/rx power are most likely due to incompatible/defective\n\ optical components or too long/short optical cables. It may also\n\ be due to faulty transceiver. |
- |
LOG_STD_SH_TECH_ACTION |
|
SFF8472-3-INTERNAL_ERROR |
3-Error |
[chars] |
The SFF8472 subsystem encountered an internal software\n\ error. The error message contains text which can be used\n\ to help identify the nature of the problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
SFF8472-3-READ_ERROR |
3-Error |
[chars] |
There was an error reading digital optical monitoring information\n\ from the transceiver at the specified interface. |
- |
"Please try removing and reinserting the transceiver.\n\ If it still does not work please replace the transceiver." |
|
SFF8472-3-UNEXPECTEDEVENT |
3-Error |
Process received unknown event maj [hec] min [hec]. |
A process can register to be notified when various events occur in the\n\ router. This message indicates that a process received an event it\n\ did not know how to handle. |
- |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
SFP_SECURITY-4-DUPLICATE_SN |
4-Warning |
SFP interface [chars] has the same serial number as another SFP interface |
The SFP was identified as a Cisco SFP but its serial number matches that of another interface on the system. |
firmware |
"Cisco SFPs are assigned unique serial numbers. " "Verify that the SFP " "was obtained from Cisco or a supported vendor" |
|
SFP_SECURITY-4-ID_MISMATCH |
4-Warning |
Identification check failed for SFP interface [chars] |
The SFP was identified as a Cisco SFP but the system was unable to verify its identity |
firmware |
"Check the list of supported SFPs for this version " "of the system software. An upgrade may be required " "for newer SFPs. Otherwise verify that the SFP " "was obtained from Cisco or a supported vendor" |
|
SFP_SECURITY-4-SFP_INTERR |
4-Warning |
Internal error occurred in setup for SFP interface [chars] |
The system could not allocate resources or had some other problem in the setup for the specified SFP interface. |
firmware |
"Reload the system. If the problem persists " "contact TAC." |
|
SFP_SECURITY-4-UNRECOGNIZED_VENDOR |
4-Warning |
SFP interface [chars] manufactured by an unrecognized vendor |
The SFP was identified as a Cisco SFP but the system was unable to match its manufacturer with one on the known list of Cisco SFP vendors |
firmware |
"Check the list of supported SFPs for this version " "of the system software. An upgrade may be required " "for newer SFPs." |
|
SFP_SECURITY-4-VN_DATA_CRC_ERROR |
4-Warning |
SFP interface [chars] has bad crc |
The SFP was identified as a Cisco SFP but it does not have valid crc in the eeprom data. |
firmware |
"Check the list of supported SFPs for this version " "of the system software. An upgrade may be required " "for newer SFPs. Even if unrecognized the SFP " "may still operate properly perhaps with limited " "functionality." |
|
SFP-3-EEPROM_DUP_ERR |
3-Error |
SFP on ports [chars] and [chars] have duplicate serial numbers |
The GBIC/SFP was identified as a Cisco GBIC but its vendor id and serial number match that of another GBIC on the system. |
- |
"Report to Cisco tech support." |
|
SFP-3-NOT_COMPATIBLE |
3-Error |
Detected for SFP module in [chars] module disabled |
The SFP 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. |
- |
"Replace the module with a compatible SFP." |
|
SFP-3-NOT_SUPPORTED |
3-Error |
Detected for SFP module in [chars] module disabled |
The SFP 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. |
- |
"Replace the module with a cisco supported SFP." |
|
SFP-3-SFP_UNINITIALIZED |
3-Error |
[chars] SFP inserted in port [dec] error status [dec] |
SFP inserted initialization failed |
cmts-platform |
"If not expected copy the error message exactly as it " "appears and report it to your technical support" |
|
SFP-3-SW_ERR |
3-Error |
SFP Driver error: [chars] sfp [dec] errcode [dec] |
Internal error in SFP driver |
- |
"Copy the error message exactly as it appears and report it to your" " technical support" |
|
SFP-3-SW_I2C_ERR |
3-Error |
SFP Driver i2c error: [chars] sfp [dec] addr 0x[hec] errcode [dec] |
i2c Access error to SFP device |
cmts-platform |
"Copy the error message exactly as it appears and report it to your" " technical support" |
|
SFP-4-EEPROM_CRC_ERR |
4-Warning |
EEPROM checksum error for SFP in [chars] |
The SFP in the port specified in the error message has invalid EEPROM data. |
- |
"Remove the SFP from the specified port." |
|
SFP-4-EEPROM_READ_ERR |
4-Warning |
Error in reading SFP serial ID in [chars] |
Error when reading SFP type from EEPROM |
- |
"Please remove SFP from this Port" |
|
SFP-4-EEPROM_SECURITY_ERR |
4-Warning |
SFP in [chars] failed security check |
The SFP in the port specified in the error message has invalid EEPROM data. |
- |
"Remove the SFP from the specified port." |
|
SFP-4-REMOVED |
4-Warning |
SFP module removed from [chars] |
The online insertion and removal OIR facility detected the |
- |
LOG_STD_NO_ACTION |
|
SFP-5-SFP_MISSING |
5-Notice |
[chars] SFP missing from port [dec] |
SFP removed |
cmts-platform |
"If not expected copy the error message exactly as it " "appears and report it to your technical support" |
|
SFP-5-SFP_OK |
5-Notice |
[chars] SFP inserted in port [dec] |
SFP inserted |
- |
"If not expected copy the error message exactly as it" " appears and report it to your technical support" |
|
SFP-6-INSERTED |
6-Information |
SFP module inserted in [chars] |
The online insertion and removal OIR facility detected a |
- |
LOG_STD_NO_ACTION |
|
SGBP-1-AUTHFAILED |
1-Alert |
Member [chars] failed authentication |
This message is generated only when SGBP hellos or errors\n\ debugging is enabled. This indicates that an attempted\n\ peer connection ended in authentication failure. A peer may be\n\ misconfigured. Or this could indicate an attempted security\n\ breach. |
- |
"Check if the peer is correctly configured.\n\ If there is a chance your network is under attack obtain\n\ knowledgeable assistance. " LOG_STD_ACTION |
|
SGBP-1-DIFFERENT |
1-Alert |
Rcv [chars]'s addr [inet] is different from the hello's addr [inet] |
The internally-configured address for an SGBP member does not\n\ match the address of the host that tried to authenticate as\n\ that member. The configuration is incorrect on either this\n\ system or the other member - they must agree. |
- |
"Determine which configuration is in error and fix it." |
|
SGBP-1-DUPLICATE |
1-Alert |
Rcv Duplicate bundle [chars] is found on member [chars] |
This message is generated only when SGBP hellos or errors\n\ debugging is enabled. This indicates that a duplicate bundle\n\ was received from the same peer more than once. The duplicate\n\ was discarded. |
- |
LOG_STD_RECUR_ACTION |
|
SGBP-1-MISSCONF |
1-Alert |
Possible misconfigured member [chars] using [inet] |
This message is generated only when SGBP hellos or error\n\ debugging is enabled. This indicates a configuration error.\n\ Either this router has an incorrect IP address listed for\n\ the peer or the peer is using an incorrect IP address. |
- |
"Find and correct the configuraton error." |
|
SGBP-1-NOTAUTH |
1-Alert |
Rcv Connection request by non-authenticated member [chars] |
- |
- |
- |
|
SGBP-1-UNKNOWNHELLO |
1-Alert |
Rcv Hello message from non-group member using [inet] |
This message is generated only when SGBP hellos or error\n\ debugging is enabled. An SGBP Hello message was received\n\ from a host that is not a member of the SGBP group\n\ and discarded. |
- |
- |
|
SGBP-3-INVALID |
3-Error |
MQ message with [chars] |
This message is generated only when SGBP error debugging is\n\ enabled. An invalid message was received and discarded. |
- |
"This probably indicates an error in network media or\n\ a peer which is generating erroneous packets." |
|
SGBP-3-INVALIDADDR |
3-Error |
Stack group [chars] IP address [inet] |
The current configuration does not allow a local IP address to be \n\ configured using <cmdBold>sgbp member <address><noCmdBold>. Any\n\ local address is automatically removed fro the SGBP group. |
sgbp |
"Do not configure <cmdBold>sgbp member <address><noCmdBold> \n\ using a local IP address." |
|
SGBP-3-INVALIDB |
3-Error |
[chars] for bundle \'[chars]\' -- [chars] |
An internal software error has occurred. |
- |
LOG_STD_ACTION |
|
SGBP-3-INVFIELD |
3-Error |
[chars] field type [hex] has [chars] [dec] expected [dec] |
This message indicates that an SGBP request from a peer\n\ contained invalid or corrupt data. |
- |
"Check the peer equipment or network media for any problems." |
|
SGBP-3-PEERERROR |
3-Error |
Peer [inet] [chars] during \'PB [chars]\' state for bundle [chars] |
An internal software error has occurred. |
- |
LOG_STD_ACTION |
|
SGBP-3-UNEXP |
3-Error |
MQ [chars] from [inet] for query [dec]:[dec] bundle [chars] bid [dec] state [chars] |
This message is generated only when SGBP error debugging is\n\ enabled. The SGBP connection has entered an unexpected state\n\ possibly due to a software error. |
- |
LOG_STD_ACTION |
|
SGBP-3-UNKNOWN |
3-Error |
[inet] not known |
This message is generated only when SGBP error debugging is\n\ enabled. An SGBP connection was attempted by a host which was\n\ not recognized as a peer. The connection was not accepted. |
- |
"Depending on the network topology and firewalling SGBP connection\n\ attempts from a non-peer host could indicate probing and attempts to\n\ breach security. If there is a chance your network is under\n\ attack obtain knowledgeable assistance. " LOG_STD_ACTION |
|
SGBP-3-UNKNOWNEVENT |
3-Error |
Event [hex] from peer at [inet] |
This message is generated only when SGBP error debugging is\n\ enabled. An invalid event occurred which probably\n\ indicates an internal software error. |
- |
"LOG_STD_ACTION" |
|
SGBP-3-UNKNOWNPEER |
3-Error |
Event [hex] from peer at [inet] |
This message is generated only when SGBP error debugging is\n\ enabled. An SGBP event came from a network host which was not\n\ recognizable as an SGBP peer. The event was discarded. |
- |
"Check if a network media error could have corrupted the address\n\ or if peer equipment is malfunctioning to generate corrupted\n\ packets.\n\ Depending on the network topology and firewalling SGBP packets\n\ from a non-peer host could indicate probing and attempts to\n\ breach security. If there is a chance your network is under\n\ attack obtain knowledgeable assistance. " LOG_STD_ACTION |
|
SGBP-5-ARRIVING |
5-Notice |
New peer event for member [chars] |
This message is generated only when SGBP event debugging is\n\ enabled. An SGBP peer joined the group. |
- |
LOG_STD_NO_ACTION |
|
SGBP-5-LEAVING |
5-Notice |
Member [chars] leaving group [chars] |
This message is generated only when SGBP event debugging is\n\ enabled. An SGBP peer has left the group. |
- |
LOG_STD_NO_ACTION |
|
SGBP-5-SHUTDOWN |
5-Notice |
[chars] |
This message is generated only when SGBP event debugging is\n\ enabled. A process involved in SGBP was terminated\n\ upon completion of its work. |
- |
LOG_STD_NO_ACTION |
|
SGBP-5-STARTUP |
5-Notice |
[chars] |
This message is generated only when SGBP event debugging is\n\ enabled. An process involved in SGBP was started. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-ACTIVE |
7-Debug |
Member [chars] State -> Active |
This message is generated only when SGBP errors or events\n\ debugging is enabled. This indicates that a link to another\n\ SGBP member has completed the interactions to set it up and is\n\ now entering the active state. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-AUTHOK |
7-Debug |
Member [chars] State -> AuthOK |
This message is generated only when SGBP errors or events\n\ debugging is enabled. A message was received from another SGBP\n\ member indicating that an authentication attempt to that member\n\ succeeded. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-CANCEL |
7-Debug |
Local query #[dec]:[dec] for bundle [chars] |
This message is generated only when SGBP query debugging is\n\ enabled. It provides information about queries in progress. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-CHALLENGE |
7-Debug |
Send Hello Challenge to [chars] group [chars] |
This message is generated only when SGBP hellos debugging\n\ is enabled. This indicates that an authentication challenge\n\ was sent to a peer. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-CHALLENGED |
7-Debug |
Rcv Hello Challenge message from member [chars] using [inet] |
This message is generated only when SGBP hellos debugging\n\ is enabled. This indicates that an authentication challenge\n\ was received from a peer. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-CLOSE |
7-Debug |
Closing pipe for member [chars] |
This message is generated only when SGBP event debugging is\n\ enabled. An interprocess communication link was closed. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-DONE |
7-Debug |
Query #[dec] for bundle [chars] count [dec] master is [chars] |
This message is generated only when SGBP event debugging is\n\ enabled. It indicates that a peer timed out while closing a\n\ query. The connection has been dropped. |
- |
"Check the peer equipment and network media for problems." |
|
SGBP-7-DUPL |
7-Debug |
Duplicate local query #[dec] for [chars] count [dec] ourbid [dec] |
This message is generated only when SGBP query debugging is\n\ enabled. It provides information about queries in progress. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-EQUAL |
7-Debug |
[dec] equal highest bids randomly select bid# [dec] |
This message is generated only when SGBP query debugging is\n\ enabled. It provides information about queries in progress. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-HANGUP |
7-Debug |
I am a forward-only member can't forward bundle [chars] hangup |
This message is generated only when SGBP query event and/or\n\ error debugging is enabled. This indicates a routine change of\n\ role for the router in its SGBP interactions with its peers. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-KEEPALIVE |
7-Debug |
Sending Keepalive to [chars] retry=[dec] |
This message is generated only when SGBP hellos debugging is enabled.\n\ It indicates that a keepalive message was send to an SGBP member. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-KEEPALIVE_TIMEOUT |
7-Debug |
Keepalive timeout on [chars] |
This message is generated only when SGBP hellos debugging is enabled.\n\ It indicates that keepalive messages were not answered so the pipe\n\ to an SGBP member has been closed. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-MQ |
7-Debug |
[chars] [hex] for query [dec]:[dec] bundle [chars] bid [dec] len [dec] |
This message is generated only when SGBP error debugging is\n\ enabled. This message indicates that an SGBP query has been\n\ received. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-MQB |
7-Debug |
\tBundle: [chars]\tState: [chars]\tOurBid: %03d |
This message is part of a list of debug states displayed at the\n\ request of the operator. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-NEWL |
7-Debug |
Local query #[dec] for [chars] count [dec] ourbid [dec] |
This message is generated only when SGBP query debugging is\n\ enabled. It provides information about queries in progress. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-NEWP |
7-Debug |
Peer query #[dec] for [chars] count [dec] peerbid [dec] ourbid [dec] |
This message is generated only when SGBP query debugging is\n\ enabled. It provides information about queries in progress. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-NORESP |
7-Debug |
Failed to respond to [chars] group [chars] may not have password |
An authentication challenge was received but there was no\n\ information available to respond to it. This probably\n\ indicates a configuration error a missing password. |
- |
"Refer to the documentation to configure a username\n\ with the same name as the SGBP group." |
|
SGBP-7-PB |
7-Debug |
\t[inet]\tState: [chars]\tBid: %03d Retry: [dec] |
This message is part of a list of debug states displayed at the\n\ request of the operator. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-RCVD |
7-Debug |
MQ [chars] from [inet] for query [dec]:[dec] bundle [chars] bid [dec] prot[chars] |
This message is generated only when SGBP message debugging is\n\ enabled. It indicates that an SGBP packet was received. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-RCVINFO |
7-Debug |
Received Info Addr = [inet] Reference = [hex] |
This message is generated only when SGBP hellos debugging is enabled.\n\ It indicates that data was received by a listener process. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-RESPONSE |
7-Debug |
Send Hello Response to [chars] group [chars] |
This message is generated only when SGBP hellos debugging\n\ is enabled. This indicates that a response to an authentication\n\ challenge was sent to a peer. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-RESPONSED |
7-Debug |
Rcv Hello Response message from member [chars] using [inet] |
This message is generated only when SGBP hellos debugging\n\ is enabled. This indicates that a response to an authentication\n\ challenge was received from a peer. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-SENDAUTHOK |
7-Debug |
Send Hello Authentication OK to member [chars] using [inet] |
This message is generated only when SGBP hellos debugging is enabled.\n\ A message was send or re-sent to another SGBP member indicating\n\ that an authentication attempt from that member succeeded. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-SENDINFO |
7-Debug |
Send Info Addr to [chars] |
This message is generated only when SGBP hellos debugging is enabled.\n\ It indicates that data was sent by the listener process in response\n\ to received data. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-SENT |
7-Debug |
MQ [chars] to [inet] for query [dec]:[dec] bundle [chars] bid [dec] prot[chars] len [dec] |
This message is generated only when SGBP message debugging is\n\ enabled. It indicates that an SGBP packet was sent. |
- |
LOG_STD_NO_ACTION |
|
SGBP-7-WAITINFO |
7-Debug |
Member [chars] State -> WaitInfo |
- |
- |
- |
|
SGCP-2-INTERNAL_CRITICAL |
2-Critical |
[chars] |
The SGCP subsystem encountered an internal software\n\ error. The error message contains text which can be used\n\ to help identify the nature of the problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
SGCP-3-INTERNAL_ERROR |
3-Error |
[chars] |
The SGCP subsystem encountered an internal software\n\ error. The error message contains text which can be used\n\ to help identify the nature of the problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
SGCP-4-INTERNAL_WARNING |
4-Warning |
[chars] |
The SGCP subsystem encountered an internal software\n\ error. The error message contains text which can be used\n\ to help identify the nature of the problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
SGPM-3-PACL_NAME_TOO_LONG |
3-Error |
The pacl name [chars]-[chars] is too long it exceeds the maximum length |
Too many acl entries have made the pacl name exceed the maximum supported length |
policy |
LOG_STD_ACTION |
|
SGPM-3-POLICY_CTX_ACTIVE |
3-Error |
Active policy context %X has bad magic %X. |
The magic number in the active policy context is wrong. |
policy |
LOG_STD_ACTION |
|
SGPM-3-POLICY_CTX_POISONED |
3-Error |
Policy context %X has bad magic %X. |
The magic number in the policy context is wrong. |
policy |
LOG_STD_ACTION |
|
SGPM-3-POLICY_RULE_SERVICE_CONFIG_ERROR |
3-Error |
Service [chars] is configured incorrectly |
In policy rule the service is configured incorrectly then a service-failed event will be thrown. |
policy |
LOG_STD_ACTION |
|
SHDSL-1-EFM_BOND |
1-Alert |
[chars] CPE-CO configuration mismatch detected for link:[dec]. |
If CPE is configured in efm bonding and CO is configured in plain 2wire then link will come-up in plain 2-wire. Since CPE is configured in efm bonding CPE will ignore link up event |
- |
"Correct either CPE or CO's configuration" |
|
SHDSL-1-FWDNLD |
1-Alert |
[chars] [chars]. |
An attempt to download firmware for SHDSL card failed. This interface cannot be used. |
- |
LOG_STD_ACTION |
|
SHDSL-1-INFO |
1-Alert |
SHDSL[dec]/[dec]/[dec]: [chars]. |
Info on SHDSL card. |
- |
LOG_STD_ACTION |
|
SHDSL-1-INIT |
1-Alert |
SHDSL[dec]/[dec]/[dec]: [chars]. |
An attempt to initialize the SHDSL NIM failed. This module cannot be used |
- |
LOG_STD_ACTION |
|
SHDSL-1-NGIO_DROP |
1-Alert |
Command dropped since phy re-init is in progress. |
If ngio_drop_messages is set then the messages are dropped in host |
- |
"Wait till the phy reinit is complete" |
|
SHDSL-1-TCLAYER |
1-Alert |
SHDSL[dec]/[dec]/[dec]: [chars] [dec]. |
if CPE-CO modeATM/EFM configuration is improper |
- |
"Change the modeATM to EFM or EFM to ATMconfiguration" |
|
SHDSL-3-EFM_FRAME_SIZE |
3-Error |
[chars] [chars]. |
An attempt to change the maximum frame size in EFM bonding scenario has failed. |
- |
LOG_STD_ACTION |
|
SHDSL-3-FIRMWARE |
3-Error |
[chars] [chars] |
Error occured in the SHDSL module firmware. |
- |
LOG_STD_ACTION |
|
SHDSL-3-NOMEM |
3-Error |
SHDSL [chars] malloc failed : out of memory |
The router does not have enough memory installed to run this SHDSL feature |
- |
LOG_STD_ACTION |
|
SHDSL-3-PHY_FWDNLD_FAIL |
3-Error |
[chars] [chars] could be incomplete or corrupted or not present in [chars] |
Error occured in the SHDSL Phy firmware download. |
- |
"Use correct firmware package file" |
|
SHDSL-4-ERRORINT |
4-Warning |
Error interrupt: [chars] received |
A spurious event happened for the SHDSL card. |
- |
LOG_STD_ACTION |
|
SHDSL-5-DYING_GASP |
5-Notice |
Power failure at CPE detected at link no [dec]. |
CPE has gone down because of power failure. |
- |
LOG_STD_NO_ACTION |
|
SHDSL-6-DSLGROUP_UPDOWN |
6-Information |
[chars] dsl-group [dec] state changed to [chars]. |
DSL Group state is changed. |
- |
LOG_STD_NO_ACTION |
|
SHDSL-6-EFM_ACT_LINK_CHANGE |
6-Information |
[chars] EFM Group [dec] has [dec] active links active link bitmap is [hex]. |
Active Links were added or removed from the Group changing its bandwidth. |
- |
LOG_STD_NO_ACTION |
|
SHDSL-6-EFM_BOND_LINK_RATE_CHANGE |
6-Information |
[chars] EFM Link[dec] bandwidth is changed. |
SHDSL link is trained to a different rate EFM bonding group. |
- |
LOG_STD_NO_ACTION |
|
SHDSL-6-PHY_FWDNLD |
6-Information |
[chars] [chars] [chars] |
Info about status of SHDSL Phy firmware download. |
- |
LOG_STD_NO_ACTION |
|
SHELF-3-DISCOVER_SOCKET_OPEN |
3-Error |
socket open failed |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
SHELF-5-AUTH_FAILED |
5-Notice |
MD5 digest does not match SDP packet received from [inet] rejected |
A SDP hello packet was received from shelf which is not trusted. |
- |
"Either specify the correct SDP password and/or destination on the\n\ shelf from which this message was received" |
|
SHELF-6-HELLO_PROCESS_START |
6-Information |
Shelf hello process has started. |
This is an informational message only. An internal system controller\n\ process was started. |
- |
"Informational messages can be disabled by changing logging level." |
|
SHELF-6-HELLO_PROCESS_STOP |
6-Information |
Shelf hello process has been stopped. |
This is an informational message only. An internal system controller\n\ process completed its work. |
- |
"Informational messages can be disabled by changing logging level." |
|
SHELF-6-SYSCTLR_ESTABLISHED |
6-Information |
Configured via system controller located at [inet] |
This is an informational message only. Configuration information\n\ was received from a system controller. |
- |
"Informational messages can be disabled by changing logging level." |
|
SHELL_ISSU-2-COPY_SHELL_INIT_TO_STANDBY |
2-Critical |
Failed to copy the shell init file [chars] to standby |
If the shell init file is not copied to standby the shell init file CLI will not be applied to maintain the consistancy between active and standby. |
parser |
"Try manually copy a file to standby to see if it's" " a filesystem issue. It could be a space issue in the" " standby disk" |
|
SHELL_ISSU-2-GET_BUFFER |
2-Critical |
Shell ISSU client failed to get buffer for message. Error: [dec] [chars] |
The Shell 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. |
parser |
"show logging and show checkpoint client" |
|
SHELL_ISSU-2-INIT |
2-Critical |
Shell ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The Shell 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. |
parser |
LOG_STD_ACTION |
|
SHELL_ISSU-2-SAVE_TRIGGER_FOR_REAPPLY |
2-Critical |
Failed to add trigger to the re-apply queue. Trigger: [chars] Env: [chars] |
Triggers that failed to get applied during ISSU must be saved and then re-applied after ISSU completes. |
parser |
"Manually re-apply the trigger after ISSU completes" |
|
SHELL_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
Shell ISSU client failed to send negotiation message. Error: [dec] [chars] |
The Shell 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. |
parser |
"show logging and show checkpoint client" |
|
SHELL_ISSU-2-SESSION_NEGO_FAIL_START |
2-Critical |
Failed to start Shell ISSU session negotiation. Error: [dec] [chars] |
The Shell ISSU client failed to start session negotition. If a problem occurs with the ISSU session start the standby device cannot be brought up properly. |
parser |
"show issu session <client_id>" |
|
SHELL_ISSU-2-SESSION_REGISTRY |
2-Critical |
Shell ISSU client failed to register session information. Error: [dec] [chars] |
The Shell ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
parser |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
SHELL_ISSU-3-INVALID_SESSION |
3-Error |
Shell ISSU client does not have a valid registered session. |
The Shell ISSU client does not have a valid registered session. |
parser |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
SHELL_ISSU-3-MSG_NOT_OK |
3-Error |
Shell ISSU client 'Message Type [dec]' is not compatible |
The Shell ISSU client received an incompatible message from the peer device. The message cannot be processed. |
parser |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
SHELL_ISSU-3-MSG_SIZE |
3-Error |
Shell ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The Shell ISSU client failed to calculate the MTU for the specified message. The Shell ISSU client is not able to send the message to the standby device. |
parser |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
SHELL_ISSU-3-SESSION_UNREGISTRY |
3-Error |
Shell ISSU client failed to unregister session information. Error: [dec] [chars] |
The Shell ISSU client failed to unregister session information. |
parser |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
SHMWIN-3-FREE_FAILURE |
3-Error |
Failure while freeing memory in function [chars] |
An attempt was made to free memory that has already been freed or is not within the address space of the current process |
OS |
"LOG_STD_ACTION " |
|
SHMWIN-6-ALLOC_FAILURE |
6-Information |
Insufficient memory |
There was a failure while returning physical memory to the system |
OS |
"LOG_STD_ACTION " |
|
SHMWIN-6-CORE_NOT_ENABLED |
6-Information |
In function [chars] The core has not been enabled to get more physical memory |
The core has not been enabled |
OS |
"LOG_STD_ACTION" |
|
SHMWIN-6-EXCEEDED_MAX_SIZE |
6-Information |
In function [chars] The requested memory size exceeded the window size |
The memory requested in this window exceeded the window size |
OS |
"LOG_STD_ACTION" |
|
SHMWIN-6-EXCEEDED_MAX_USERS |
6-Information |
In function [chars] The maximum number of users for a shared window has been exceeded |
The maximum number of users for a shared window has been exceeded |
OS |
"LOG_STD_ACTION " |
|
SHMWIN-6-INCONSISTENCY |
6-Information |
Inconsistent state in window |
Inconsistent state in window |
OS |
"LOG_STD_ACTION" |
|
SHMWIN-6-INVALID_ARGS |
6-Information |
One or more invalid arguments have been passed to the function [chars] |
One or more invalid arguments have been passed to the shared memory api's |
OS |
"LOG_STD_ACTION " |
|
SHMWIN-6-INVALID_PARAM |
6-Information |
An invalid parameter has been passed to the function [chars] |
One or more invalid parameters have been passed to the shared memory api's |
OS |
"LOG_STD_ACTION" |
|
SHMWIN-6-MAX_WINDOWS_EXCEEDED |
6-Information |
In function [chars] process has exceeded the maximum number of windows that can be opened by it |
Exceeded maximum number of windows that can be opened by a process |
OS |
"LOG_STD_ACTION" |
|
SHMWIN-6-MEM_COLLISION |
6-Information |
In function [chars] the requested memory space collides with the memory space of other windows |
Memory space collision |
OS |
"LOG_STD_ACTION" |
|
SHMWIN-6-MUTEX_ERROR |
6-Information |
An internal mutex error has occured in the function [chars] |
An error has been encountered in the locking or unlocking of the shared memory mutex |
OS |
"LOG_STD_ACTION" |
|
SHMWIN-6-NOT_SUPPORTED |
6-Information |
The option passed to function [chars] is not supported |
This option is not supported |
OS |
"LOG_STD_ACTION" |
|
SHMWIN-6-PTHREAD_MUTEX_LOCK_FAILED |
6-Information |
An internal mutex error has been encountered in function [chars] |
A process which has obtained the access mutex has not released it as yet |
OS |
"LOG_STD_ACTION " |
|
SHMWIN-6-PTHREAD_MUTEX_UNLOCK_FAILED |
6-Information |
An internal mutex error has been encountered in function [chars] |
An internal mutex error has been enountered |
OS |
"LOG_STD_ACTION " |
|
SHMWIN-6-SHMEM_FAILURE |
6-Information |
The function [chars] Could not access shared memory |
Could not access shared memory |
OS |
"LOG_STD_ACTION" |
|
SHMWIN-6-SYS_LOCK_CREATE_FAILED |
6-Information |
The lock creation for the shared memory failed in function [chars] |
Lock creation for the shared memory failed |
OS |
"LOG_STD_ACTION " |
|
SHMWIN-6-SYS_LOCK_FAILED |
6-Information |
In function [chars] The process was unable to lock the shared memory against other processes |
The process was unable to lock the shared memory against other users |
OS |
"LOG_STD_ACTION " |
|
SHMWIN-6-SYS_UNLOCK_FAILED |
6-Information |
In function [chars] The process was unable to unlock the shared memory |
The shared memory could not be unlocked due to an internal error |
OS |
"LOG_STD_ACTION " |
|
SHMWIN-6-VIRT_MAP_FAILURE |
6-Information |
In function [chars] Could not reserve virtual memory |
Could not reserve virtual memory |
OS |
"LOG_STD_ACTION" |
|
SHMWIN-6-WINDOW_EXCEEDED_MAX_POOLS |
6-Information |
The maximum number of pools has been exceeded in function [chars] |
The maximum number of pools has been exceeded |
OS |
"LOG_STD_ACTION" |
|
SHMWIN-7-PHYS_MAP_FAILURE |
7-Debug |
In function [chars] Failed to map physical memory |
Failed to map physical memory |
OS |
"LOG_STD_ACTION " |
|
SHMWIN-7-UNLINK_ERROR |
7-Debug |
An internal error occurred while unlinking in function [chars] |
An internal error occurred while unlinking |
OS |
"LOG_STD_ACTION " |
|
SHUTDOWN_REQUEST_FAIL-6-LDP |
6-Information |
ERRMSG_NOFLAGS |
- |
- |
- |
|
SHUTDOWN_REQUEST_FAILED-3-L2VPN |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
SHUTDOWN-6-L2VPN |
6-Information |
ERRMSG_NOFLAGS |
- |
- |
- |
|
SIBYTE-0-ADDRESS_TRAP |
0-Emergency |
Address trap: [dec] occurred on physical address: 0x%llx at EPC: 0x[hec] ERR_EPC: 0x[hec] |
A previously defined address trap has occurred. |
debug |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
SIBYTE-0-MISDIRECTED_INTERRUPT |
0-Emergency |
A misdirected interrupt occurred with int_mask: 0x[hec] |
A misdirected interrupt occurred. |
debug |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
SIBYTE-0-UNCORRECTABLE_ECC_ERR |
0-Emergency |
An uncorrectable ECC error has occurred A_BUS_L2_ERRORS: 0x%llx A_BUS_MEMIO_ERRORS: 0x%llx A_SCD_BUS_ERR_STATUS: 0x%llx |
An uncorrectable ECC error has occurred. |
debug |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
SIBYTE-2-SB_MAC_FATAL |
2-Critical |
Fatal Error on mac [dec] 0x%016llx |
A fatal error occurred on a MAC interface |
procyon |
LOG_STD_ACTION |
|
SIBYTE-3-CORRECTABLE_ECC_ERR |
3-Error |
A correctable ECC error has occurred A_BUS_L2_ERRORS: 0x%llx A_BUS_MEMIO_ERRORS: 0x%llx A_SCD_BUS_ERR_STATUS: 0x%llx |
A correctable ECC error has occurred. |
debug |
"Copy the error message exactly as it appears and report it to your technical support representative." |
|
SIBYTE-3-SB_MAC_ERROR |
3-Error |
Unrecognized error on mac [dec] 0x%016llx |
Unrecognized error on MAC interface |
procyon |
LOG_STD_ACTION |
|
SIBYTE-3-SB_RX_FIFO_OVRFL |
3-Error |
RX FIFO overflow on mac [dec] count: %lld |
- |
- |
- |
|
SIBYTE-3-SB_RX_FIFO_UNDRFL |
3-Error |
RX FIFO underflow on mac [dec] count: %lld |
- |
- |
- |
|
SIBYTE-3-SB_SPURIOUS_INT |
3-Error |
Spurious interrupt level [dec] |
A spurious interrupt was received |
procyon |
LOG_STD_ACTION |
|
SIBYTE-3-SB_TX_FIFO_OVRFL |
3-Error |
TX FIFO overflow on mac [dec] count: %lld |
- |
- |
- |
|
SIBYTE-3-SB_TX_FIFO_UNDRFL |
3-Error |
TX FIFO underflow on mac [dec] count: %lld |
- |
- |
- |
|
SIBYTE-3-SB_UNEXPECTED_INT |
3-Error |
Unexpected interrupt at level [dec] 0x%016llx |
An unexpected interrupt was received |
procyon |
LOG_STD_ACTION |
|
SIBYTE-3-SB_UNINITIALIZED_INT |
3-Error |
Uninitialized interrupt 0x%016llx |
An uninitialized interrupt was received |
procyon |
LOG_STD_ACTION |
|
SIBYTE-4-SB_EXCESS_COLL |
4-Warning |
Excessive collisions on mac [dec] count: %lld |
- |
- |
- |
|
SIBYTE-4-SB_LATE_COLL |
4-Warning |
Late collision on mac [dec] count: %lld |
- |
- |
- |
|
SIBYTE-5-SB_OUT_OF_RX_DSCR_CH0 |
5-Notice |
Out of RX descriptors on mac [dec] - channel 0 count: %lld |
- |
- |
- |
|
SIBYTE-5-SB_OUT_OF_RX_DSCR_CH1 |
5-Notice |
Out of RX descriptors on mac [dec] - channel 1 count: %lld |
- |
- |
- |
|
SIBYTE-6-SB_RMON_OVRFL |
6-Information |
RMON register [dec] overflow on mac [dec] |
An RMON statistics register has been wrapped around |
procyon |
LOG_STD_NO_ACTION |
|
SIGNAL_OCE-3-SOCE |
3-Error |
Failed to [chars] signal oce [chars][chars] |
An internal software error occurred. |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
SIGNAL_OCE-3-SOCE_SB_OPERATION_FAILED |
3-Error |
Failed to [chars] subblock on [chars] |
An internal software error occurred. |
OCE_DDTS_COMPONENT |
LOG_STD_ACTION |
|
SIGNAL-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
SIGNALLERINIT-3-MPLS_TE |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
SIGNATURE-3-ABORT_OPER |
3-Error |
%%ERROR: Aborting [chars]. |
The system is aborting the specified operation because it failed to verify a valid signature in the image file. |
security |
"Attempt to restart the operation by using an image file " "with a valid signature. A valid signature ensures the " "integrity of the image." |
|
SIGNATURE-3-CONTINUE_OPER |
3-Error |
%%ERROR: Continuing Operation [chars] in spite of failure. |
Although the system failed to verify a valid signature in the image file the user decided to continue the specified operation. A valid signature ensures the integrity of the image. |
security |
- |
|
SIGNATURE-3-DELETE_FAILED |
3-Error |
%%ERROR: Unable to auto delete file [chars]. Remove file manually |
The specified Cisco IOS Software image file contains an invalid signature but automatic deletion of the file has failed. A valid signature ensures the integrity of the image. |
security |
"Delete the file by entering the <CmdBold>delete<NoCmdBold> command." |
|
SIGNATURE-3-NOT_ABLE_TO_PROCESS |
3-Error |
%%ERROR: Not able to process Signature in [chars]. |
An unknown error occurred when the system attempted to process the signature in the specified image file. A valid signature ensures the integrity of the image. |
security |
"Do not use this file. The file might be corrupted or " "modified. Attempt to copy the file again or download " "the file again from the http://www.cisco.com page before " "copying it. If you continue to get this error message " "open a case with the Technical Assisstance Center via the " "Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl " "contact your Cisco technical support representative with the " "information you have gathered." |
|
SIGNATURE-3-NOT_VALID |
3-Error |
%%ERROR: Signature not valid for file [chars]. |
The specified Cisco IOS Software image has an invalid signature. A valid signature ensures the integrity of the image. |
security |
"Do not use this file. The file might be corrupted or " "modified. Attempt to copy the file again or download " "the file again from the http://www.cisco.com page before " "copying it. If you continue to get this error message " "open a case with the Technical Assisstance Center via the " "Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl " "contact your Cisco technical support representative with the " "information you have gathered." |
|
SIGNATURE-4-NOT_PRESENT |
4-Warning |
%%WARNING: Signature not found in file [chars]. |
The specified image file does not have a signature. Only Cisco IOS Software images in Executable and Linkable format are signed. Releases that do not support the image verification feature do not contain a signature in the image file. If you enter <CmdBold>verify<NoCmdBold> <CmdBold>copy<NoCmdBold> or <CmdBold>reload<NoCmdBold> command and the specified file is not a Cisco IOS Software image in Executable and Linkable format or of an earlier release the system displays this warning message because the file does not have a signature. A valid signature ensures the integrity of the image. |
security |
\" to see if the image that you are " "using supports the image verification feature." |
|
SIGNATURE-4-UNKNOWN |
4-Warning |
%%WARNING: Found unknown signature type 0x[hec] in file [chars]\n Skipping the signature. |
If the desired image belongs to a later release than the running image the desired image might have a newer signature type. A valid signature ensures the integrity of the image. |
security |
\" to see if a signature of the type " "specified was added." |
|
SIGSM-1-BAD_VAR_ERR |
1-Alert |
Out of range variable index [dec] [chars] |
There is a fault in a default template or the user has provided a custom template that refers to a variable that is outside the range of cas-custom variables |
as |
LOG_STD_ACTION |
|
SIGSM-1-EVENT_ERR |
1-Alert |
Unexpected event |
An error in the signalling state machine |
as |
LOG_STD_ACTION |
|
SIGSM-1-NO_TEMPLATE_ERR |
1-Alert |
No static template found for slot [dec] port [dec] with parameters provided |
The sigsm could not find a matching static template with the same parameters as the controller being used |
cas |
LOG_STD_ACTION |
|
SIGSM-3-NOMEMORY |
3-Error |
MSG_TRACEBACK|MSG_PROCESS |
- |
- |
- |
|
SIP_ALG-3-CHUNK_CREATE_FAIL |
3-Error |
- |
Chunk create failed. SIP ALG will not be able to finish initialization. |
cpp-ucode |
LOG_STD_ACTION |
|
SIP_ALG-3-CREATE_CALLBACK_ERROR |
3-Error |
- |
Missing L7 data during imprecise channel creation callback. |
cpp-ucode |
LOG_STD_ACTION |
|
SIP_ALG-3-L7_DATA_CREATE_ERROR |
3-Error |
- |
Error during L7 data creation. |
cpp-ucode |
LOG_STD_ACTION |
|
SIP_ALG-3-WRITEBACK_ERROR |
3-Error |
- |
Error during writeback. |
cpp-ucode |
LOG_STD_ACTION |
|
SIP-1-LICENSING |
1-Alert |
[chars] |
SIP Service for Eval license status |
voice-sip |
LOG_STD_ACTION |
|
SIP-2-SILENT_DISCARD |
2-Critical |
Silent Discard [chars] |
Request received from Untrusted Host. |
voice-sip |
"Block the request from untrusted host at network layer" |
|
SIP-2-TLS_HANDSHAKE_FAILED |
2-Critical |
TLS handshake failure - remote_addr=[chars] remote_port=[dec] |
TLS handshake failed |
voice-sip |
LOG_STD_ACTION |
|
SIP-3-BADPAIR |
3-Error |
Unexpected [chars] [dec] [chars] in state [dec] [chars] substate [dec] [chars] |
The SIP state machine has encountered an error while processing an event or timer. |
voice-sip |
LOG_STD_SH_TECH_ACTION |
|
SIP-3-CONSTRUCT |
3-Error |
Error encountered while trying to construct a \[dec] [chars]\ [chars] message |
An error was encountered while attempting to construct a SIP request or response message. If malloc errors where also seen then that is most likely the root of the problem. If no memory allocation errors have occurred then this may be an internal problem. |
voice-sip |
"If there were memory allocation errors at the" "same time as this error then this error can be ignored. Otherwise: " LOG_STD_SH_TECH_ACTION |
|
SIP-3-CPUCAC |
3-Error |
Call rejected due to CAC based on CPU usage sent response [dec] |
CPU usage CAC has rejected the call due to configured cpu-avg|cpu-5sec threshold being exceeded. |
voice-sip |
LOG_STD_SH_TECH_ACTION |
|
SIP-3-DIALPEERBWCAC |
3-Error |
Calling number [chars] called number [chars] dial-peer [dec] used bandwidth [dec] available bandwidth [dec] requested bandwidth [dec] call state [chars] |
Bandwidth CAC has rejected the call/media renegotiation due to configured dial-peer bandwidth threshold being exceeded |
voice-sip |
LOG_STD_SH_TECH_ACTION |
|
SIP-3-DIGITEND |
3-Error |
Missing digit end event for \'[chars]\' for call ID [chars] |
A digit begin event was detected without a matching digit end. This is most likely an internal error which is self correcting the NOTIFY for the digit has been transmitted. |
voice-sip |
LOG_STD_ACTION |
|
SIP-3-DIGITQFULL |
3-Error |
Unable to queue DTMF digit. Queue full. size: [dec] |
A request to queue a DTMF digit was rejected because the DTMF queue is full. A 5xx server error has been returned. This error may indicate that a flood of DTMF digit requests from an external SIP application for a specific call has been recieved in a very short period of time. |
voice-sip |
LOG_STD_NO_ACTION |
|
SIP-3-FORKING_CODEC |
3-Error |
No forking codecs configured for dial-peer [dec] the forked m-lines will be rejected. Forking codecs are [chars] |
Media forking requests which arrive in an INVITE message are identified by multiple media lines m-lines in the SDP. Each media line defines a |
voice-sip |
"Modify the dial-peer configuration to include one " "of the forking codecs listed using either the codec command or the " "voice-class codec command." |
|
SIP-3-INSV_ERROR |
3-Error |
Error encountered while trying to bring the SIP component into service |
During bootup of the gateway each of the Service Provider Interfaces SPIs are brought into service. The SIP SPI creates several processes |
voice-sip |
LOG_STD_RECUR_ACTION |
|
SIP-3-INTBWCAC |
3-Error |
Calling number [chars] called number [chars] dial-peer [dec] interface [chars] used bandwidth [dec] available bandwidth [dec] requested bandwidth [dec] call state [chars] |
Bandwidth CAC has rejected the call/media renegotiation due to configured interface bandwidth threshold being exceeded. |
voice-sip |
LOG_STD_SH_TECH_ACTION |
|
SIP-3-INTCALLCAC |
3-Error |
Call rejected due to CAC based on number of calls on the interface sent response [dec] |
Interface-calls CAC has rejected the call due to configured int-calls threshold being exceeded. |
voice-sip |
LOG_STD_SH_TECH_ACTION |
|
SIP-3-INTERNAL |
3-Error |
[chars] |
- |
- |
- |
|
SIP-3-INVALID |
3-Error |
Invalid [chars] [dec] |
An internal software error has occurred. |
voice-sip |
LOG_STD_SH_TECH_ACTION |
|
SIP-3-LIST_ERROR |
3-Error |
Unable to create list for [chars] |
Failure to create a list generally indicates that the router is out of memory either due to a memory leak or insufficient memory. If the error was generated soon after a reload its more likely that the router doesn't have enough memory. If the router has been running for a while a memory leak is more likely. The SIP component is not properly initialized and SIP calls may not complete properly. |
voice-sip |
show process memory |
|
SIP-3-MAXCONNCAC |
3-Error |
Call rejected due to CAC based on maximum number of connections on dial-peer [dec] sent response [dec] |
Maximum number of connections CAC has rejected the call due to configured max-conn threshold being exceeded. |
voice-sip |
LOG_STD_SH_TECH_ACTION |
|
SIP-3-MEMCAC |
3-Error |
Call rejected due to CAC based on Memory usage sent response [dec] |
Memory usage CAC has rejected the call due to configured io-mem|proc-mem|total-mem threshold being exceeded. |
voice-sip |
LOG_STD_SH_TECH_ACTION |
|
SIP-3-NOGETSTRUCT |
3-Error |
No data structure passed to MIB API subsystem. |
The SNMP Agent MIB subsystem for this MIB did not pass any data structure to the MIB API subsystem for the proper retrieval of the requested object data. Processing of the GET operation cannot continue. |
voice-sip |
LOG_STD_ACTION |
|
SIP-3-NOMATCH |
3-Error |
Unable to find matching CCB for ccCallID [dec] |
An internal error was encountered while trying to match a call ID with a call control block |
voice-sip |
LOG_STD_SH_TECH_ACTION |
|
SIP-3-NORESOURCE |
3-Error |
No resources for [chars] |
An error was encountered while trying to obtain memory resources for an internal queue or table. If malloc errors where also seen then that is most likely the root of the problem. If no memory allocation errors have occurred then this may be an internal problem. |
voice-sip |
"If there were memory allocation errors at the" "same time as this error then this error can be ignored. Otherwise: " LOG_STD_SH_TECH_ACTION |
|
SIP-3-NOSETDATA |
3-Error |
No SET data passed to MIB API subsystem. |
The SNMP Agent MIB subsystem for this MIB did not pass any data to the MIB API subsystem for the proper assignment of values to the internal data structures of the object. Processing of the SET operation cannot continue. |
voice-sip |
LOG_STD_ACTION |
|
SIP-3-PASSWORD_REKEY_FAILED |
3-Error |
Failed to encrypt type 6 password after master key change. Password [chars] will become unusable |
Type 6 password encryption failed after master key change |
voice-sip |
LOG_STD_ACTION |
|
SIP-3-PTIME |
3-Error |
Unsupported Ptime value [dec] using minimum Ptime value of [dec] on CallID [dec] Codec=[chars] |
Unsupported Ptime value negotiated |
voice-sip |
LOG_STD_SH_TECH_ACTION |
|
SIP-3-QUEUE_ERROR |
3-Error |
Unable to enqueue event [chars] [dec] to a process watched queue. Current size: [dec] max size: [dec] |
- |
- |
- |
|
SIP-3-STREAM_SERVICE |
3-Error |
[dec] [chars] |
SIP Trunk Registration status |
voice-sip |
LOG_STD_SH_TECH_ACTION |
|
SIP-3-TOTCALLCAC |
3-Error |
Call rejected due to CAC based on Total-calls sent response [dec] |
Total-calls CAC has rejected the call due to configured total-calls threshold being exceeded. |
voice-sip |
LOG_STD_SH_TECH_ACTION |
|
SIP-3-UNKNOWNOBJ |
3-Error |
MIB object [chars].[dec] is not known by MIB API subsystem. |
The MIB object specified in the SNMP GET PDU has been correctly identified by the SNMP Agent infrastructure but was not correctly identified by the subsystem responsible for the MIB. Processing of the GET operation cannot continue. The SNMP Agent infrastructure and subsystem responsible for the MIB under normal conditions will always be synchronized to the same set of MIB objects that is the same version of the MIB. This condition indicates |
voice-sip |
LOG_STD_ACTION |
|
SIP-3-UNSUPPORTED |
3-Error |
[chars] |
An internal software error has occurred. |
voice-sip |
LOG_STD_SH_TECH_ACTION |
|
SIP-4-MAXSDP |
4-Warning |
SIP message sent with maximum SDP. |
An SIP protocol message containing the maximum allowable SDP size has been sent. If the desired SDP was greater than the maximum size limit the SDP has been truncated at the limit. If the desired SDP was equal to the maximum size limit no truncation has occurred. This warning may indicate that an SIP request containing an unusually large SDP has been received from an external SIP application for a specific call resulting in an SIP response with the maximum SDP. |
voice-sip |
LOG_STD_NO_ACTION |
|
SIP-4-WEAK_PASSWORD_TYPE |
4-Warning |
Command has been added to the configuration using a type [dec] password. However type [dec] passwords will soon be deprecated. Migrate to a supported password type [dec] |
Password encryption type deprecated. New password type to be used |
voice-sip |
LOG_STD_ACTION |
|
SIP-5-BIND_LINE_STATUS |
5-Notice |
bind line proto status |
Informational message on bind line proto |
voice-sip |
LOG_STD_NO_ACTION |
|
SIP-5-DIALPEER_STATUS |
5-Notice |
VoIP dial-Peer <[dec]> is [chars] |
VoIP dial-peer's operational status is changed |
voice-sip |
"If the dial-peer status is busyout the session target configured " "under the dial-peer is not reachable" |
|
SIP-5-EVENT_TRACE_PATH_ERR |
5-Notice |
Event Trace Dump PATH \[chars]\ not accesible. Verify credentials directory path and network connectivity. Correct the Error and reconfigure Dump-file |
Event Trace Dump-file Location not accessible |
ipipgw |
"Correct the accesibility Error and reconfigure" |
|
SIP-5-REPORTING |
5-Notice |
Reported use of [dec] CUBE_T_VGW TDM-SIP sessions |
VGW entitlement status |
voice-sip |
LOG_STD_ACTION |
|
SIP-5-TLS_CONNECTION |
5-Notice |
[chars] |
TLS connection is successful or failed |
voice-sip |
LOG_STD_SH_TECH_ACTION |
|
SIP-6-IGNORE |
6-Information |
Unexpected [chars] [dec] [chars] in state [dec] [chars] substate [dec] [chars] |
The SIP state machine has encountered an error while processing an event or timer. |
voice-sip |
LOG_STD_SH_TECH_ACTION |
|
SIP-6-LONG_DUR_CALL_DETECTED |
6-Information |
Long Duration Call is detected [chars]\n |
The call is active for configured duration of long call |
voice-sip |
LOG_STD_ACTION |
|
SIPSPA-3-BAD_IFCOMTYPE |
3-Error |
Bad ifcom message type=[dec] |
The Route Processor passed down a message that the software was not prepared to handle. |
c7600-sip-common |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SIPSPA-3-BADCMD |
3-Error |
[chars]: Unsupported command [dec] arg0=[hex] arg1=[hex] arg2=[hex] |
The Route Processor passed down a command that the software was not prepared to handle. |
c7600-sip-common |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SIPSPA-3-BADINT |
3-Error |
Attempted to access HWIDB for port [dec] |
The Linecard attempted to access the HWIDB associated with a non-existent port. |
c7600-sip-common |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SIPSPA-3-CMDNOINT |
3-Error |
HWIDB Null for command [dec] arg=[hex] |
The Route Processor passed down a command that the software was unprepared to handle. |
c7600-sip-common |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SIPSPA-3-DEVICE_ERROR |
3-Error |
subSlot [dec] spatype 0x[hec]. Device error: [chars] |
An error related to a device on the SPA is detected. |
SIP_DDTS_COMP |
LOG_STD_SH_TECH_ACTION |
|
SIPSPA-3-EFC_CHAN_ERR |
3-Error |
EFC error - interface [chars] vc [dec] anyphy [dec] err_code [dec] : [chars] |
Failed to configure efc channel/parameters |
SIP_DDTS_COMP |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance " LOG_STD_ACTION |
|
SIPSPA-3-FCI_NOT_SET |
3-Error |
Bay [dec]: [chars]: FCI type not set |
An FCI type of zero was detected |
c7600-sip-common |
LOG_STD_ACTION |
|
SIPSPA-3-HWIDB_FAILURE |
3-Error |
Creation: port [dec] vc [dec] |
Failed to create a hwidb. |
SIP_DDTS_COMP |
LOG_STD_SH_TECH_ACTION |
|
SIPSPA-3-INVALID_ANYPHY |
3-Error |
Bay [dec] - Invalid anyphy number [dec] for vc [dec] |
Interface has invalid anyphy mumber |
spa-ser-common |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance open a case with the Technical Assistance " "Center via the Internet at " " http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a 'show tech-support' to " "your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
SIPSPA-3-IPCALLOCFAIL |
3-Error |
Failed to allocate IPC buffer [chars] |
The Linecard failed to allocate a buffer for communication with the Route Processor. |
c7600-sip-common |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SIPSPA-3-IPCSENDFAIL |
3-Error |
Failed to send IPC message [chars] |
The Linecard failed to send a message to the Route Processor. |
c7600-sip-common |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SIPSPA-3-ISR_RC_ERROR |
3-Error |
ISR return code out of range. rc=[dec] |
The ISR error return code is out of range. |
SIP_DDTS_COMP |
LOG_STD_SH_TECH_ACTION |
|
SIPSPA-3-LINKREC_ERROR |
3-Error |
Link record error - Bay [dec] vc [dec] error code [dec] |
Error processing link record structure |
spa-ser-common |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance open a case with the Technical Assistance " "Center via the Internet at " " http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a 'show tech-support' to " "your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
SIPSPA-3-MESSAGE_ERROR |
3-Error |
Bay [dec]: [chars] |
An unexpected error has occurred. |
SIP_DDTS_COMP |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance " LOG_STD_ACTION |
|
SIPSPA-3-MSGTOOBIG |
3-Error |
Message length exceeds max [dec] bytes |
The Linecard attempted to send too large a message to the Route Processor. |
c7600-sip-common |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SIPSPA-3-NODISPATCH |
3-Error |
Dispatch vector Null cmd=[dec] dintf=[dec] |
No command dispatch vector was found for the specified interface. |
c7600-sip-common |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SIPSPA-3-POWER |
3-Error |
Bay [dec] 12V power is [chars] |
SPA 12V power fault indicator |
SIP_DDTS_COMP |
LOG_STD_ACTION |
|
SIPSPA-3-SONET_CLOCK_FAILED |
3-Error |
SPA Sonet clock has failed status = 0x%08x |
The SPA SONET clock has failed. SPAs that rely on the SPA SONET clock for proper operation such as POS and ATM will be affected. |
c7600-sip-common |
"If the SPA Sonet clock does not recover perform an " "OIR. "LOG_STD_RECUR_ACTION |
|
SIPSPA-3-SONET_CLOCK_RECOVERED |
3-Error |
SPA Sonet clock has recovered status = 0x%08x |
SPA Sonet clock has recovered |
c7600-sip-common |
LOG_STD_NO_ACTION |
|
SIPSPA-3-SPI4_CONFIG_FAILURE |
3-Error |
Bay [dec] spi4 configuration failure error [dec] |
Failed to configure SPI4 interface |
SIP_DDTS_COMP |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance " LOG_STD_ACTION |
|
SIPSPA-3-SPI4_INIT_FAILURE |
3-Error |
Bay [dec] initialization failure |
Failed to create SPI4 subblock |
SIP_DDTS_COMP |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance " LOG_STD_ACTION |
|
SIPSPA-4-MAX_BANDWIDTH |
4-Warning |
Total SPA bandwidth exceeds line card capacity of %lu Mbps |
The total bandwidth of SPAs exceeds the rated capacity of this line card. |
SIP_DDTS_COMP |
"Refer to the line card guidelines for the maximum allowed" "aggregated SPA bandwidth for the line card" |
|
SIPSPA-4-MAX_BANDWIDTH_NS |
4-Warning |
Total SPA bandwidth exceeds line card capacity installed combination of SPA interfaces is not supported |
The total bandwidth of SPAs exceeds the rated capacity of this line card. |
SIP_DDTS_COMP |
"Refer to the line card guidelines for the maximum allowed" "aggregated SPA bandwidth for the line card" |
|
SIPSPA-4-SPABUS |
4-Warning |
Bay [dec] [chars] failed. sz=[dec] rd_par=[dec] noresp=[dec] err_l=[dec] addr=0x[hec] data=0x[hec] parity=0x[hec] deadman=[dec] |
SPABUS has reported an error. |
SIP_DDTS_COMP |
LOG_STD_ACTION |
|
SIPSPA-4-SPABUS2 |
4-Warning |
Bay [dec] [chars] failed. sz=[dec] rd_par=[dec] noresp=[dec] absent=[dec] err_l=[dec] addr=0x[hec] data=0x[hec] parity=0x[hec] deadman=[dec] |
SPABUS has reported an error. |
SIP_DDTS_COMP |
LOG_STD_ACTION |
|
SIPSPA-4-SPI_PORT_LIMIT_EXCEEDED |
4-Warning |
SPI port limit exceeded [chars] in [chars] has been powered down. |
The total number of SPI ports required exceeds the capacity of this line card. |
SIP_DDTS_COMP |
"Refer to the line card guidelines for SPA combinations supported" "by this line card" |
|
SIPSPA-6-ERRORRECOVER |
6-Information |
A Hardware or Software error occurred on [chars]. Reason : [chars] Automatic Error recovery initiated. No further intervention required. |
An error occurred in one of the devices recovery would be attempted. If recovery succeeds no further messages would be logged and no intervention would be required. |
c7600-sip-common |
LOG_STD_RECUR_ACTION |
|
SIPSPA-6-OIR |
6-Information |
Bay [dec] [chars] changed to [chars] |
SPA OIR Sequence |
SIP_DDTS_COMP |
LOG_STD_NO_ACTION |
|
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-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-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-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-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-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>" |
|
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-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-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-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-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_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-3-INTERNAL |
3-Error |
Internal error [chars] |
An internal software error occurred. |
sisf |
LOG_STD_ACTION |
|
SISF-3-INTERNAL |
3-Error |
Internal error [chars] |
An internal software error occurred. |
sisf |
LOG_STD_ACTION |
|
SISF-4-BT_TIMER |
4-Warning |
BT Timer [chars] |
Configured timer value is out of range defined for \n Wireless SISF |
sisf |
"Configure BT stale lifetimer between 300 and 86400 seconds \n\ and for other timers between 1 - 86400 seconds" |
|
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-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-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-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-IP_THEFT |
4-Warning |
IP Theft [chars] |
A duplicate IP address has been detected IP theft and blocked |
sisf |
"If the existing entry is REACHABLE in the binding table \n\ and it moved to a new port \n\ consider reducing the REACHABLE timer \n\ otherwise it is either an attack or a configuration \n\ 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-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 |
sisf |
"If the existing entry is REACHABLE in the binding table \n\ and it moved to a new port \n\ consider reducing the REACHABLE timer \n\ otherwise it is either an attack or a configuration \n\ 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_THEFT |
4-Warning |
MAC Theft [chars] |
A duplicate MAC address has been detected MAC theft and blocked |
sisf |
"If the existing entry is REACHABLE in the binding table \n\ and it moved to a new port \n\ consider reducing the REACHABLE timer \n\ otherwise it is either an attack or a configuration \n\ 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-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 that \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-RANDOM_MAC_COLLISION |
4-Warning |
Random MAC collision [chars] |
Two devices with random MACs generated the same MAC address. \n\ The second device has been rejected. |
sisf |
"The second device will need to regenerate its random MAC." |
|
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-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-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_CHANGED |
6-Information |
Entry changed [chars] |
An entry was changed in the binding table |
sisf |
"This is an informationnal message" |
|
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_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_DELETED |
6-Information |
Entry deleted [chars] |
An entry was created 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-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. \n\ Or some of this client addresses are \n\ stale and you could clear them" |
|
SKINNYMAIN-4-KEYPADFAST |
4-Warning |
Keypad messages from the phone [dec] are too fast |
The inter digit interval is too short. Each digit may not be processed properly |
cme-callcontrol |
"Please configure keypad-normalize for the phone" |
|
SKINNYSECURESERVICE-3-NOINIT |
3-Error |
Can't initialize Secure Skinny server |
Internal problems with initializing ports for the Secure Skinny server |
ios-callmgr |
"Make sure the Skinny secure server port is available on the local machine." |
|
SKINNYSECURESERVICE-3-NOMEM |
3-Error |
Can't initialize memory for Secure Skinny server |
Insufficient Memory for Secure Skinny server |
ios-callmgr |
"Increase amount of available memory" |
|
SKINNYSECURESERVICE-3-NOPROC |
3-Error |
Could not start Skinny Secure Server |
Internal Problem in process creation |
ios-callmgr |
"None" |
|
SKINNYSECURESERVICE-3-NOSOCKETS |
3-Error |
Max Number of Skinny Secure Server sockets exceeded: too many IP phones |
There are too many skinny Secure server clients requesting service |
ios-callmgr |
"Reduce number of Secure IP phones requesting service" |
|
SKINNYSECURESERVICE-6-TLS_EVAL_FREE_ERROR |
6-Information |
Error encountered on release TLS signaling tunnels. |
Error encountered on release TLS signaling tunnels. |
xformers-csl |
"Please install the Permanent license" |
|
SKINNYSECURESERVICE-6-TLS_EVAL_LIMIT |
6-Information |
The TLS signaling tunnels usage exceeds the license limit. |
The TLS signal tunnels usage exceeds the license limit. |
xformers-csl |
"Please install the Permanent license" |
|
SKINNYSERVER-3-NOINIT |
3-Error |
Can't initialize Skinny server |
Internal problems with initializing ports for the Skinny server |
ios-callmgr |
"Make sure the Skinny server port is available on the local machine." |
|
SKINNYSERVER-3-NOMEM |
3-Error |
Can't initialize memory for Skinny server |
Insufficient Memory for Skinny server |
ios-callmgr |
"Increase amount of available memory" |
|
SKINNYSERVER-3-NOSOCKETS |
3-Error |
Max Number of Skinny Server sockets exceeded: too many IP phones |
There are too many skinny server clients requesting service |
ios-callmgr |
"Reduce number of IP phones requesting service" |
|
SLAB_ALLOC-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
SLAB_CREATE-2-LDP |
2-Critical |
ERRMSG_NOFLAGS |
- |
- |
- |
|
SLB_DFP-4-BAD_LEN |
4-Warning |
Agent [inet]:[dec] - Invalid message length - [dec] |
Too many errors reading message header from SLB DFP Agent |
slb |
LOG_STD_RECUR_ACTION |
|
SLB_DFP-4-BAD_MSG |
4-Warning |
Agent [inet]:[dec] - Unknown message type [dec] vector [dec] |
An unknown message type received from SLB DFP Agent |
slb |
"An unknown message can be caused by a connection " "error between DFP Manager and Agent. Try to restart DFP Agent by unconfiguring " "and reconfiguring it to see if it fixes the connection error." |
|
SLB_DFP-4-BAD_SEND |
4-Warning |
Agent [inet]:[dec] - Send failed |
An attempt to send a message to the SLB DFP Agent has failed. |
slb |
"Verify that the DFP Agent is reachable via " "ping or traceroute. Verify that the DFP Agent on the server is running." LOG_STD_RECUR_ACTION |
|
SLB_DFP-4-BIG_MSG |
4-Warning |
Agent [inet]:[dec] - Message length [dec] too big |
A message from the SLB DFP Agent exceeds the allowable maximum size. |
slb |
"A message exceeding allowable maximum size can " "be caused by a connection error between DFP Manager and Agent. Try to " "restart DFP Agent by unconfiguring and reconfiguring it to see if it fixes " |
|
SLB_DFP-4-BIG_VEC |
4-Warning |
Agent [inet]:[dec] - Message type [dec] vector [dec] too big |
A message from the SLB DFP Agent exceeds the allowable maximum size. |
slb |
"A message exceeding allowable maximum size can " "be caused by a connection error between DFP Manager and Agent. Try to " "restart DFP Agent by unconfiguring and reconfiguring it to see if it fixes " |
|
SLB_DFP-4-CON_FAIL |
4-Warning |
Agent [inet]:[dec] - Socket_connect failed |
Socket_connect to SLB DFP Agent failed |
slb |
LOG_STD_RECUR_ACTION |
|
SLB_DFP-4-KEEP_ALV |
4-Warning |
Agent [inet]:[dec] - Have not received keep alive |
The system has not received a keepalive message from the SLB DFP Agent. |
slb |
"Verify that the DFP Agent is reachable via " "ping or traceroute. Verify that the DFP Agent on the server is running." LOG_STD_RECUR_ACTION |
|
SLB_DFP-4-NO_PARSE |
4-Warning |
Agent [inet]:[dec] - Could not parse message |
Could not parse message from SLB DFP Agent |
slb |
LOG_STD_RECUR_ACTION |
|
SLB_DFP-4-READ_ERR |
4-Warning |
Agent [inet]:[dec] - Too many read errors |
Too many errors reading message header from SLB DFP Agent |
slb |
LOG_STD_RECUR_ACTION |
|
SLB_DFP-4-RECONN_MGR |
4-Warning |
Manager [inet] is reconnecting |
The SLB Manager is reconnecting without disconnecting |
slb |
LOG_STD_RECUR_ACTION |
|
SLB_DFP-4-SOCK_ERR |
4-Warning |
Agent [inet]:[dec] - Socket_recv error [dec] |
Socket_recv error receiving message from SLB DFP Agent |
slb |
LOG_STD_RECUR_ACTION |
|
SLB_DFP-4-SOCK_OPN |
4-Warning |
Agent [inet]:[dec] - Socket alreay open |
The system tried to open Socket to SLB DFP Agent that is already open. |
slb |
"If the problem persists unconfigure and " "reconfigure SLB DFP. " LOG_STD_RECUR_ACTION |
|
SLB_DFP-4-UKN_CON |
4-Warning |
Agent [inet]:[dec] - Unknown connection state [dec] |
Unknown connection state processing SLB DFP timer |
slb |
LOG_STD_RECUR_ACTION |
|
SLB_DFP-4-UNEXPECTED |
4-Warning |
Unexpected error: [chars] |
An unexpected error occurred while performing SLB DFP operation |
slb |
LOG_STD_RECUR_ACTION |
|
SLB_DFP-4-UNK_TYPE |
4-Warning |
Agent [inet]:[dec] - Unknown message type [dec] |
Message from SLB DFP Agent has unknown type |
slb |
LOG_STD_RECUR_ACTION |
|
SLB_KAP-3-BIND_FAIL |
3-Error |
SLB Keep Alive Application Protocol Socket_bind failed for Port:[dec] |
SLB Keep Alive Application Protocol process attempts to bind a socket port failed |
slb |
LOG_STD_RECUR_ACTION |
|
SLB_KAP-4-UNEXPECTED |
4-Warning |
Unexpected error: [chars] |
An unexpected error occurred while performing SLB Keep Alive Application Protocol operation |
slb |
LOG_STD_RECUR_ACTION |
|
SLB-4-CF |
4-Warning |
Unexpected error: [chars] |
An unexpected error occurred in SLB slave replication |
slb |
LOG_STD_RECUR_ACTION |
|
SLB-4-CF_BULK |
4-Warning |
[chars] |
An unexpected error occurred in SLB slave replication bulk sync |
slb |
LOG_STD_RECUR_ACTION |
|
SLB-4-CF_IPC |
4-Warning |
Slave replication messages are creating a backlog in IPC. Some SLB objects may not be synchronized. |
Due to IPC resource contention SLB was unable to replicate all objects. |
slb |
LOG_STD_RECUR_ACTION |
|
SLB-4-CF_NUM |
4-Warning |
Unexpected error: [chars] [dec] |
An unexpected error occurred in SLB slave replication |
slb |
LOG_STD_RECUR_ACTION |
|
SLB-4-CF_RATE |
4-Warning |
Overrun of SLB's slave replication rate some SLB objects may not be synchronized. |
Due to a high connection rate SLB was unable to replicate all objects. |
slb |
LOG_STD_RECUR_ACTION |
|
SLB-4-IF_REMOVED |
4-Warning |
Access interface removed: [chars] [chars] being set to outofservice. |
An interface being referenced in slb access configuration has been removed. The vserver or firewallfarms referencing this interface will brought outofservice. |
slb |
LOG_STD_RECUR_ACTION |
|
SLB-4-PROBE |
4-Warning |
Probe [chars] for [inet]:[dec] [chars] |
An error occured during SLB probe operation |
slb |
LOG_STD_REDUCE_ACTION |
|
SLB-4-UNEXPECTED |
4-Warning |
Unexpected error: [chars] |
An unexpected error occurred while performing SLB operation |
slb |
LOG_STD_RECUR_ACTION |
|
SLB-4-VRF_REMOVED |
4-Warning |
Access VRF removed: [chars] [chars] being set to outofservice. Access VRF \n\ configuration has been removed. |
An VRF being referenced in slb access configuration has been\n\ removed. The vserver or firewallfarms referencing this VRF will \n\ brought outofservice. The access VRF configuration will be removed. |
slb |
LOG_STD_RECUR_ACTION |
|
SLB-6-REAL |
6-Information |
Real [chars] [chars] has changed state to [chars] |
Informational message whenever a real server changes its state to/from OPERATIONAL: possible causes might be e.g. testing probe testing maxconns |
slb |
LOG_STD_NO_ACTION |
|
SLBSCPU-3-BADTYPE |
3-Error |
Unknown type of indication [hec] |
Microcode is sending bad indication type. |
slb |
LOG_STD_RECUR_ACTION |
|
SLBSCPU-3-NOCFGDWLD |
3-Error |
Unable to request initial config download from main CPU. |
After initialization SLB CPU requests main CPU to send configuration readfrom NVRAM. This message is generated when a failure occurs in communication. |
slb |
LOG_STD_RECUR_ACTION |
|
SLBSCPU-3-NOPROC |
3-Error |
Cannot create SLB SCPU Process |
Error occurred during initialization of SLB process on SLB CPU |
slb |
LOG_STD_RECUR_ACTION |
|
SLBSCPU-3-NOREQ |
3-Error |
Failed to get request packet for ICC |
Error occurred during communication between SLB CPU |
slb |
LOG_STD_RECUR_ACTION |
|
SLBSCPU-3-NORESP |
3-Error |
Did not receive ICC response |
Error occurred during communication between SLB CPU |
slb |
LOG_STD_RECUR_ACTION |
|
SLBSCPU-6-CFGDWLD |
6-Information |
Request [dec] initial config download from main CPU. |
After initialization SLB CPU requests main CPU to send configuration readfrom NVRAM. This message is indicates a request was sent. |
slb |
"" |
|
SLIP-2-BADQUOTE |
2-Critical |
Impossible quoted character [hec] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
SLIP-2-BADSTATE |
2-Critical |
Impossible input state [hec] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
SLOT_FPD-3-GETHWVER_FAILED |
3-Error |
Failed to get [chars] hardware revision number in Slot [dec]. |
Failed to get the board's revision number. |
- |
"Check module seating and module status. " "Re-insert the module. Contact TAC if this message is seen again." |
|
SLOT_FPD-3-GETVER_FAILED |
3-Error |
Failed to get FPD version for FPD=[dec] in Slot [dec]: [chars]. |
Failed to get FPD version due to either IPC problem or operation error. The card will be disabled. |
- |
"Check module seating and module status. " "Ensure compatibility among FPD and IOS by comparing output of command " "<CmdBold>show hw-module slot fpd<NoCmdBold> with IOS Release Notes. " "Obtain IOS version by command <CmdBold>show version<NoCmdBold>." |
|
SLOT_FPD-3-SUBBLOCK |
3-Error |
Failed to [chars] FPD subblock in Slot [dec]. |
Failed to create delete or populate a FPD subblock due to operation error. |
- |
LOG_STD_ACTION |
|
SLOT_FPD-3-UPGRADE_FAILED |
3-Error |
Failed to upgrade FPD for slot [dec] [chars]. |
The FPD image upgrade operation failed. The cause could be a wrong image file error in accessing fpga storage physical interrupt such as power failure or card removal. Depending on the slot type and error cause the card could be in an unusable state. Normally the system automatically reattempts the upgrade and shuts the card after repeated failures. |
- |
"Do not interrupt the system while an FPD " "upgrade is in progress. Obtain the matching FPD package. Refer " "to IOS Release Notes for more information on obtaining the correct " "FPD package for the card. Review the output of the RP FPD logs." |
|
SLOT_FPD-4-UPGRADE_STATE |
4-Warning |
[chars] on slot [dec]. |
Display the upgrade state |
- |
LOG_STD_RECUR_ACTION |
|
SLOT_SYNC -2-INITSYS |
2-Critical |
[chars] |
A software error occurred during initialization of the Interface Sync RF subsystem |
- |
"Check for sufficient processor memory." LOG_STD_ACTION |
|
SLOT_SYNC-3-INVALID_MSG |
3-Error |
Incorrectly formatted message 0x[hec] 0x[hec] received by [chars] |
Inconsistent message data was received from the peer CPU possibly due to an incompatible image version. |
- |
LOG_STD_ACTION |
|
SLOT_SYNC-3-NO_BUFFER |
3-Error |
Unable to transmit message type [dec] from [chars] |
A transmit error occurred while sending msg to other CPU due to non-availability of buffer |
- |
LOG_STD_ACTION |
|
SLOT_SYNC-3-RECV_BAD_SUBCARD_COUNT |
3-Error |
Received a slot sync message with subcard count as [dec] for slot [dec] |
A slot sync message with bad subcard count is being recvd |
- |
LOG_STD_ACTION |
|
SLOT_SYNC-3-SEND_BAD_SUBCARD_COUNT |
3-Error |
Sending a slot sync message with subcard count as [dec] for slot [dec] |
A slot sync message with bad subcard count is being sent |
- |
LOG_STD_ACTION |
|
SLOT_SYNC-3-TRANSMIT_ERROR |
3-Error |
Unable to transmit message type [dec] from [chars] |
A transmit error occurred while sending msg to other CPU due to msg translation |
- |
LOG_STD_ACTION |
|
SLOT_SYNC-3-UNKNOWN_MSG |
3-Error |
Unknown message type 0x[hec] received by [chars] |
An unknown message type was received from the peer CPU possibly due to an incompatible image version. |
- |
LOG_STD_ACTION |
|
SLOT_SYNC-5-UNSUPPORTED_MSG |
5-Notice |
Msgtype [chars] sent by [chars] unsupported by peer. |
Peer responded that it didn't recognize a message sent by this CPU possibly due to a different image version. |
- |
"May require a software upgrade on the Standby CPU. " LOG_STD_ACTION |
|
SLOTDUMP-3-CORE_DUMP_ERROR |
3-Error |
Core dump error slot [dec]: [chars] |
An error occured during a core dump of slot |
- |
"None." |
|
SM_CREATE-2-LDP |
2-Critical |
ERRMSG_NOFLAGS |
- |
- |
- |
|
SM-3-LDP |
3-Error |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
SM-4-BADEVENT |
4-Warning |
Event '[chars]' is invalid for the current state '[chars]': [chars] [chars] |
An attempt was made to post an event to a state machine that is invalid \n\ for the current state. |
sm |
LOG_STD_SH_TECH_ACTION |
|
SM-4-BADEVENT |
4-Warning |
Event '[chars]' is invalid for the current state '[chars]': [chars] [chars] |
An attempt was made to post an event to a state machine that is invalid \ for the current state. |
sm |
LOG_STD_SH_TECH_ACTION |
|
SM-4-INIT |
4-Warning |
Internal error while initializing state machine '[chars]' state '[chars]': [chars] |
An attempt was made to initialize an invalid state machine. |
sm |
LOG_STD_SH_TECH_ACTION |
|
SM-4-INIT |
4-Warning |
Internal error while initializing state machine '[chars]' state '[chars]': [chars] |
An attempt was made to initialize an invalid state machine. |
sm |
LOG_STD_SH_TECH_ACTION |
|
SM-4-INIT |
4-Warning |
- |
- |
- |
- |
|
SM-4-PERSIST |
4-Warning |
Persistent event '[chars]' did not leave the current state '[chars]': [chars] [chars] |
An attempt was made to post a persistent event to a state machine that\n\ would cause an infinite loop in the current state. |
sm |
LOG_STD_SH_TECH_ACTION |
|
SM-4-PERSIST |
4-Warning |
Persistent event '[chars]' did not leave the current state '[chars]': [chars] [chars] |
An attempt was made to post a persistent event to a state machine that \ would cause an infinite loop in the current state. |
sm |
LOG_STD_SH_TECH_ACTION |
|
SM-4-STOPPED |
4-Warning |
Event '[chars]' ignored because the state machine is stopped: [chars] [chars] |
An attempted was made to post an event to a state machine that has\n\ already been stopped. |
sm |
LOG_STD_SH_TECH_ACTION |
|
SM-4-STOPPED |
4-Warning |
Event '[chars]' ignored because the state machine is stopped: [chars] [chars] |
An attempted was made to post an event to a state machine that has \ already been stopped. |
sm |
LOG_STD_SH_TECH_ACTION |
|
SMANRP-3-BADREPLYJOBID |
3-Error |
Incorrect command reply job id %llu origin [chars] expecting %llu |
- |
- |
- |
|
SMANRP-3-CMDBUILD |
3-Error |
Interactive command directive [dec] of [dec] failed |
In processing a CLI command one of the instructions returned through the Shell Manager could not be turned into an interactive command for remote execution. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
SMANRP-3-CMDCONNECT |
3-Error |
Connection to local interactive relay failed: [chars] |
Connecting to the local relay for an interactive command failed due to the reason indicated in the error message. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
SMANRP-3-CMDSEND |
3-Error |
Send interactive command to relay failed: [chars] |
Sending the interactive command string to the local relay after the connection was established failed by the reason indicated in the error message. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
SMANRP-3-CMDTOOLONG |
3-Error |
Interactive command too long |
Instructions for command execution would result in creation of a command string that is beyond the maximum size. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
SMANRP-3-INVALIDCONNHANDLE |
3-Error |
Invalid connection handle [dec] referenced during command execution. |
The execution of a CLI command which must communicate with Shell Manager for command execution has referenced a connection handle that is invalid. The CLI command execution will have failed. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
SMANRP-3-MSGBIPCBUFFER |
3-Error |
Unable to acquire a BIPC buffer for sending messages. |
A message was to be sent by IOS but no BIPC buffer was available. The message to be sent has been discarded and the associated operation failed. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
SMANRP-3-MSGBIPCCONNERR |
3-Error |
Unable to register with the BIPC subsystem for connections to Shell Manager |
IOS Shell Manager client code could not register with the BIPC communications infrastructure in order to establish a connection with the Shell Manager. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
SMANRP-3-MSGBIPCERR |
3-Error |
Unable to process received BIPC messages from Shell Manager error: [chars] |
An unexpected condition has occurred while IOS trying to process a received BIPC message from Shell Manager. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
SMANRP-3-MSGBUILDERROR |
3-Error |
Error [dec] building TDL message '[chars]' to send to the Shell Manager: [chars] |
An unexpected condition has occurred while IOS is building a TDL message to send to the Shell Manager |
iosxe-shellmgr |
LOG_STD_ACTION |
|
SMANRP-3-MSGCRFTRELOADERROR |
3-Error |
Error sending CRFT capture on reload message. |
IOS failed to successfully complete the CRFT reload archive operation. |
polaris-crft |
LOG_STD_ACTION |
|
SMANRP-3-MSGDISPATCH |
3-Error |
Unable to dispatch received TDL message '[chars]' from Shell Manager. LUID: [chars] |
An unexpected condition has occurred while IOS is trying to dispatch\n\ to the TDL message handler functions for received TDL messages from \n\ Shell Manager. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
SMANRP-3-MSGDISPATCHNULL |
3-Error |
Received NULL TDL message |
An unexpected condition in which IOS has received a NULL TDL \n\ message from Shell Manager. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
SMANRP-3-MSGENQUEUEERROR |
3-Error |
Error queueing TDL message '[chars]' to send to the Shell Manager |
An unexpected condition has occurred when IOS attempted to queue a TDL message to send to the Shell Manager |
iosxe-shellmgr |
LOG_STD_ACTION |
|
SMANRP-3-MSGERROR |
3-Error |
Error [dec] handling a received TDL message '[chars]' from the Shell Manager: [chars] |
An unexpected condition has occurred while IOS is processing a TDL message received from the Shell Manager |
iosxe-shellmgr |
LOG_STD_ACTION |
|
SMANRP-3-MSGINVALIDFIELDINT |
3-Error |
Invalid field '[chars]' in TDL message '[chars]' received: value '[dec]' from the Shell Manager |
A message with an invalid field value was received from the Shell Manager |
iosxe-shellmgr |
LOG_STD_ACTION |
|
SMANRP-3-MSGINVALIDFIELDSTR |
3-Error |
Invalid field '[chars]' value '[chars]' in TDL message '[chars]' received from the Shell Manager |
A message with an invalid field value was received from the Shell Manager |
iosxe-shellmgr |
LOG_STD_ACTION |
|
SMANRP-3-MSGMARSHALERROR |
3-Error |
Error '[dec]' marshaling TDL message '[chars]' to send to the Shell Manager |
An unexpected condition has occurred while IOS is marshaling TDL message to send to the Shell Manager |
iosxe-shellmgr |
LOG_STD_ACTION |
|
SMANRP-3-MSGMISSINGFIELD |
3-Error |
Missing field '[chars]' in TDL message '[chars]' received from the Shell Manager |
A message missing a required field was received from the Shell Manager |
iosxe-shellmgr |
LOG_STD_ACTION |
|
SMANRP-3-SET_ACCESS_FAIL |
3-Error |
Installing LIIN interface access control failed |
This error happens when the Shell Manager shim failed to set the access control function for the LIIN possibly due to IOS out of memory or corruption. Interactive commands will not work. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
SMANRP-3-SMAN_HANDLER_QUEUE_NOTEMPTY |
3-Error |
Dynamic command handler exited foreground process with non-empty queue |
The dynamic command handler which dispatches commands to the shell manager has exited without proper cleanup. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
SMANRP-3-SMAN_INIT_CONN_FAIL |
3-Error |
Shell Manager client connection pool initialization failed: Unable to request creation of [dec] of [dec] connections. |
The Shell Manager client has failed to create all of its connections to Shell Manager. Ability to execute some CLI commands will be severely restricted or non-existent. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
SMANRP-3-SMAN_INIT_DC_TDL_FAIL |
3-Error |
Shell Manager client initialization failed: Unable to initialize messaging: [chars] |
The Shell Manager client has failed to initialize the infrastructure for messaging with the Shell Manager. Ability to execute some CLI commands will be severely restricted or non-existent. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
SMANRP-3-SMAN_INIT_WQ_FAIL |
3-Error |
Shell Manager client connection handler initialization failed: Unable to create [dec] of [dec] receiving queues. |
The Shell Manager client has failed to create all of its receiving queues. Ability to execute some CLI commands will be severely restricted or non-existent. |
iosxe-shellmgr |
LOG_STD_ACTION |
|
SMANRP-6-SMSTATUS |
6-Information |
Shell Manager is [chars] |
The current status of Shell Manager. |
- |
LOG_STD_NO_ACTION |
|
SMC-2-BAD_ID_HW |
2-Critical |
Failed Identification Test in [chars] [[dec]/[dec]]\n\n\ The module in [chars] in this router may not be a genuine \n\ Cisco product. Cisco warranties and support programs only\n\ apply to genuine Cisco products. If Cisco determines that\n\ your insertion of non-Cisco memory WIC cards AIM cards \n\ Network Modules SPA cards GBICs or other modules into a \n\ Cisco product is the cause of a support issue Cisco may \n\ deny support under your warranty or under a Cisco support \n\ program such as SmartNet.\n\n |
Hardware in the specified location could not be identified as \n\ a genuine Cisco product |
c2800 |
"Contact TAC" LOG_STD_RECUR_ACTION |
|
SMC-2-FAILED_ID_HW |
2-Critical |
Failed Identification Test in [chars] [[dec]/[dec]]\n |
There was a problem while identifying Hardware in the specified\n\ location. |
c2800 |
"Contact TAC" LOG_STD_RECUR_ACTION |
|
SMC-2-PROTO_HW |
2-Critical |
Module [chars] is a registered proto-type for Cisco Lab |
Hardware in the specified location is a proto-type module that came\n\ from a Cisco Lab |
c2800 |
"Contact TAC" LOG_STD_RECUR_ACTION |
|
SMF-4-INVALID_ACTION |
4-Warning |
failed to create SMF entry for [enet] on [chars] with result %08x |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
SMRP-2-ASSERTFAILED |
2-Critical |
SMRP assertion failed: [chars] |
The software detected an inconsistency. This is considered a serious\n\ error. The router attempts to continue but SMRP processing may be\n\ impaired. |
- |
"Copy the error message exactly as it appears noting any SMRP problems\n\ that you are experiencing and report it to your technical support\n\ representative." |
|
SMRP-5-NEIGHBORDOWN |
5-Notice |
[chars]: SMRP neighbor down - [chars] |
SMRP cannot be started on an interface that is running\n\ pre-FDDITalk. |
- |
"Use FDDITalk on the FDDI ring if possible." |
|
SMRP-5-PORTDOWN |
5-Notice |
[chars]: SMRP port down - [chars] |
An SMRP port is down and is no longer operational. |
- |
"Notification message only. No action required." |
|
SMRP-6-NEIGHBORUP |
6-Information |
[chars]: SMRP neighbor up - [chars] |
A neighboring SMRP router has appeared. |
- |
"Notification message only. No action required." |
|
SMRP-6-PORTUP |
6-Information |
[chars]: SMRP port up - [chars] |
An SMRP port has come up. |
- |
"Notification message only. No action required." |
|
SMRP-7-DEBUGMSG |
7-Debug |
SMRP Debug: [chars] |
This message is generated by some debug commands to provide additional\n\ information about conditions in SMRP. |
- |
"If you are experiencing problems in SMRP these messages should be\n\ provided along with any other information in a report to your\n\ technical support representative." |
|
SMTP_ALG-3-SMTP_CHUNK_CREATE_FAIL |
3-Error |
- |
Triggers on an invalid SMTP command in the SMTP connection. This message indicates that a suspicious violation was detetected that may be an attack to the mail server system. |
cpp-ucode |
"This is unusual traffic and may warrant investigation." |
|
SNAPSHOT-2-BADSTATE |
2-Critical |
Bad state for Snapshot block [chars][[dec]] location [dec] |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SNAPSHOT-2-TOOMANYDIALERS |
2-Critical |
Exceeded maximum dialer interfaces to watch. Ignoring [chars] |
Snapshot is being used over more than 100 DDR interfaces. |
- |
"Do not use snapshot over more than 100 DDR interfaces." |
|
SNASW-3-APPN_LOG_1 |
3-Error |
PROBLEM - %lu - SNA Switch could not allocate necessary storage [chars] |
SNA Switch could not allocate necessary storage.\n\ Some operation will fail. See other logs/verbs. |
snasw |
- |
|
SNASW-3-ASM_LOG_0 |
3-Error |
PROBLEM - %lu - Received BIND request directed at this node with unrecognized secondary LU name [chars] |
- |
snasw |
"Correct primary LU configuration." |
|
SNASW-3-ASM_LOG_11 |
3-Error |
PROBLEM - %lu - Received BIND request with badly formed secondary LU name [chars] |
Received BIND request with badly formed secondary LU name.\n\ This may indicate an interoperability problem.\n\ Session activation will fail with the specified sense code. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-ASM_LOG_12 |
3-Error |
PROBLEM - %lu - Received BIND request where network ID of secondary LU does not match local network ID [chars] |
Received BIND request where network identifier of secondary LU\n\ does not match local network identifier.\n\ Session activation will fail with the specified sense code. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-ASM_LOG_19 |
3-Error |
PROBLEM - %lu - Received BIND using LFSID that is already in use [chars] |
- |
snasw |
"If problem is persistent or occurs frequently contact\n\ support with details of the problem." |
|
SNASW-3-ASM_LOG_2 |
3-Error |
PROBLEM - %lu - Insufficient storage to generate an Alert [chars] |
Insufficient storage to generate Alert to report a BIND\n\ segmentation or pacing error.\n\ The Alert will not be sent. |
snasw |
- |
|
SNASW-3-ASM_LOG_22 |
3-Error |
PROBLEM - %lu - Session control request received with invalid LFSID [chars] |
- |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-ASM_LOG_24 |
3-Error |
PROBLEM - %lu - Failed to initialize address space instance [chars] |
Insufficient storage to create a local form session identifier\n\ routing table for a link station.\n\ Link activation will fail. |
snasw |
- |
|
SNASW-3-ASM_LOG_27 |
3-Error |
PROBLEM - %lu - Detected fatal BIND or UNBIND protocol error [chars] |
- |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-ASM_LOG_28 |
3-Error |
PROBLEM - %lu - Received BIND IPM on link where adaptive BIND pacing not supported [chars] |
Received BIND IPM on link where adaptive BIND pacing is not\n\ supported. This may indicate an interoperability problem.\n\ BIND IPM will be discarded. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-ASM_LOG_3 |
3-Error |
PROBLEM - %lu - Insufficient storage to process received BIND request [chars] |
Insufficient storage to process received BIND request.\n\ The BIND will be rejected with the specified sense code. |
snasw |
- |
|
SNASW-3-ASM_LOG_4 |
3-Error |
PROBLEM - %lu - ACTPU ACTLU DACTPU or DACTLU received on link on which dependent LUs are not supported [chars] |
ACTPU ACTLU DACTPU or DACTLU received over a link on which\n\ dependent LUs are not supported. This may indicate an\n\ interoperability problem.\n\ Request will be rejected with the specified sense code. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-ASM_LOG_5 |
3-Error |
PROBLEM - %lu - Branch Network Node received BIND request with badly formed RSCV [chars] |
A Branch Network Node has received a BIND request with a badly\n\ formed RSCV. This may indicate an interoperability problem.\n\ Session activation will fail. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-ASM_LOG_6 |
3-Error |
PROBLEM - %lu - Badly-formed BIND request rejected by SNA Switch [chars] |
SNA Switch received and rejected a badly-formed BIND request.\n\ This may indicate an interoperability problem.\n\ Session activation will fail. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-ASM_LOG_7 |
3-Error |
PROBLEM - %lu - BIND received with the next hop in the RSCV set to the local node again [chars] |
SNA Switch received a BIND request with a badly formatted\n\ RSCV. The CP name for the next hop in the RSCV is this local\n\ node again. Sesion activation will fail. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-ASSERT |
3-Error |
Assertion failure : '[chars]' from [chars] line [dec] |
- |
- |
- |
|
SNASW-3-BAD_MSG_NAME |
3-Error |
Invalid message name specified for sna\sw msg-trap |
An invalid message name was supplied on a snasw msg-trap command. |
snasw |
"Reissue the command with a valid message name." |
|
SNASW-3-CLS_LOG_0 |
3-Error |
PROBLEM - %lu - Could not validate process handle [chars] |
CLS has passed SNA Switch a DLC packet but SNA Switch does not have a valid\n\ handle to invoke the correct SNA process. The CLS message has been \n\ discarded. |
snasw |
"Dump traces and contact the Cisco TAC." |
|
SNASW-3-CLSIBadPrimitive |
3-Error |
CLSI bad primitive type header= [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
SNASW-3-CLSIBadReturnCode |
3-Error |
CLSI bad return code: [dec] header= [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
SNASW-3-CLSIFailure |
3-Error |
SNASW failed to process CLSI message header= [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
SNASW-3-CS_LOG_0 |
3-Error |
PROBLEM - %lu - An active link station has failed [chars] |
An active link station has failed.\n\ The link and any sessions using it will be deactivated |
snasw |
"Attempt to restart the link. If the problem persists inspect\n\ the log for problems or exceptions logged by the DLC which give\n\ more specific reasons for the failure and follow the actions\n\ specified by those logs. Otherwise run a trace on the\n\ specified port or link station to find the reason for the\n\ failure." |
|
SNASW-3-CS_LOG_1 |
3-Error |
PROBLEM - %lu - XID exchange count exceeds activation limit [chars] |
The number of XIDs received during link activation exceeded\n\ the limit defined for the port. This could indicate an XID\n\ protocol error or an excessively unreliable physical media.\n\ The sense data gives more information about the error.\n\ 083E0001 - the limit was exceeded while exchanging\n\ prenegotiation or negotiation XIDs\n\ 0809003A - the limit was exceeded while exchanging NULL XIDs.\n\ Link activation will fail. |
snasw |
"Retry the activation. If SNA Switch is still\n\ unable to activate the link station run a trace on the link\n\ station or port to diagnose the problem." |
|
SNASW-3-CS_LOG_10 |
3-Error |
PROBLEM - %lu - Link to host not configured [chars] |
An unexpected SET_MODE ie. received before XID exchange had\n\ completed was received from an adjacent host and there was not\n\msgdef_recommended_action Define a link station |
- |
- |
|
SNASW-3-CS_LOG_11 |
3-Error |
PROBLEM - %lu - Parallel TGs not supported to this adjacent node [chars] |
Attempted to activate more than one TG to an adjacent node that\n\ does not support parallel TGs.\n\ Link activation will fail. |
snasw |
"Modify the configuration so that there is only one link station\n\ defined to the specified adjacent node. Alternatively\n\ several links to the adjacent node can be defined but only one\n\ can be active concurrently." |
|
SNASW-3-CS_LOG_13 |
3-Error |
PROBLEM - %lu - Conflicting requirements for error recovery link is not HPR-capable [chars] |
Conflicting requirements for error recovery between the local\n\ node and a partner node when attempting to activate a link that\n\ is HPR-capable.\n\ Link will activate but will not be HPR-capable. |
snasw |
"To allow HPR protocols to be used on the link the local and\n\ partner nodes must be able to accommodate the other's error\n\ recovery requirement. At the minimum this will require\n\ reconfiguration but may not always be possible." |
|
SNASW-3-CS_LOG_17 |
3-Error |
PROBLEM - %lu - DLC failed [chars] |
A DLC has ended abnormally.\n\ All ports and link stations defined on the DLC will be\n\ inoperative. |
snasw |
- |
|
SNASW-3-CS_LOG_2 |
3-Error |
PROBLEM - %lu - XID exchange count exceeds nonactivation limit [chars] |
The number of XIDs received during non-activation exchange\n\ exceeded the limit defined for the port. This could indicate\n\ an XID protocol error or an excessively unreliable physical\n\ media.\n\ Non-activation XID exchange will fail and the link will be\n\ deactivated. |
snasw |
"Run a trace on the link station or port to diagnose the\n\ problem and contact support with trace information." |
|
SNASW-3-CS_LOG_22 |
3-Error |
PROBLEM - %lu - Unable to deactivate port [chars] |
Unable to deactivate port.\n\ snasw stop port will fail port may not restart successfully. |
snasw |
"If required attempt to restart the port. If this fails look\n\ for DLC specific logs giving more information on the reason\n\ for the failure." |
|
SNASW-3-CS_LOG_24 |
3-Error |
PROBLEM - %lu - Unrecoverable DLC failure [chars] |
Unrecoverable DLC failure.\n\ The DLC will be destroyed and all ports and link stations\n\ defined on the DLC will be inoperative. |
snasw |
- |
|
SNASW-3-CS_LOG_3 |
3-Error |
PROBLEM - %lu - Insufficient storage to activate link [chars] |
Insufficient storage to activate link.\n\ Link activation will fail. |
snasw |
- |
|
SNASW-3-CS_LOG_30 |
3-Error |
PROBLEM - %lu - Incoming call rejected because port link-activation limits exceeded [chars] |
An incoming call was rejected because the port link-activation\n\ limits would be exceeded.\n\ The link activation will fail. |
snasw |
"If possible increase the port link-activation limits." |
|
SNASW-3-CS_LOG_31 |
3-Error |
PROBLEM - %lu - The CP name on an XID3 received from adjacent node is different to that expected [chars] |
The CP name on an XID3 received from an adjacent node is\n\ different to that expected.\n\ The link activation will fail. |
snasw |
"If the received adjacent CP name is correct correct the link\n\ station configuration using snasw link. Depending on other\n\ aspects of the link station definition the CP name check\n\ can be disabled by issuing snasw link with the adj_cp_name field\n\ set to all zeros." |
|
SNASW-3-CS_LOG_32 |
3-Error |
PROBLEM - %lu - The node ID on an XID3 received from a back-level node is different to that expected [chars] |
The node ID on an XID3 received from a back level node is\n\ different to that expected.\n\ The link activation will fail. |
snasw |
"If the received node ID is correct correct the link station\n\ configuration using snasw link. Depending on other aspects of\n\ the link station definition the node ID check can be disabled\n\ by issuing snasw link with the adj_node_id field set to all\n\ zeros." |
|
SNASW-3-CS_LOG_33 |
3-Error |
PROBLEM - %lu - The node type indicated on an XID3 received from an adjacent node is different to that expected [chars] |
The node type indicated on an XID3 received from an adjacent\n\ node is different to that expected.\n\ The link activation will fail. |
snasw |
"If the received node type is correct correct the link station\n\ configuration using snasw link. Depending on other aspects of\n\ the link station definition the node type check can be disabled\n\ by issuing snasw link with the adj_node_type field set to\n\ NAP_LEARN_NODE." |
|
SNASW-3-CS_LOG_34 |
3-Error |
PROBLEM - %lu - Both sent and received XIDs indicate the same non-negotiable link station role [chars] |
Both sent and received XIDs indicate the same non-negotiable\n\ link station role.\n\ The link activation will fail. |
snasw |
"Either correct the local port definition or the remote\n\ definition so that the link station roles are complementary\n\ or at least one link station is negotiable." |
|
SNASW-3-CS_LOG_4 |
3-Error |
PROBLEM - %lu - Link to back-level LEN node not configured [chars] |
An XID3 from an adjacent back-level LEN node ie. not carrying\n\ a network name control vector was received and there was not a\n\msgdef_recommended_action Define a link station |
- |
- |
|
SNASW-3-CS_LOG_5 |
3-Error |
PROBLEM - %lu - Link to host not configured correctly host is not a Type 2.1 node [chars] |
Link to host not configured correctly that is\n\ configured as a link to a Type 2.1 node.\n\msgdef_recommended_action Redefine |
- |
- |
|
SNASW-3-CS_LOG_51 |
3-Error |
PROBLEM - %lu - Intra-node session support ended abnormally [chars] |
Intra-node session support ended abnormally. This should only\n\ occur because of a shortage of available storage.\n\ Any active intranode sessions will fail and no more intra-node\n\ sessions will be activatable. |
snasw |
- |
|
SNASW-3-CS_LOG_54 |
3-Error |
PROBLEM - %lu - Insufficient storage to generate link Alert [chars] |
Insufficient storage to generate link Alert.\n\ Alert will not be sent. |
snasw |
- |
|
SNASW-3-CS_LOG_6 |
3-Error |
PROBLEM - %lu - XID protocol error during activation exchange [chars] |
- |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-CS_LOG_62 |
3-Error |
PROBLEM - %lu - Failed to create DLC [chars] |
A DLC could not be started either because of insufficient\n\ resources or because the specified DLC type is not supported.\n\ The DLC is inoperative. |
snasw |
"If the DLC type is supported then either decrease the system\n\ load for example by reducing the number of active sessions\n\ or make more storage available to SNA Switch." |
|
SNASW-3-CS_LOG_63 |
3-Error |
PROBLEM - %lu - Pre-defined TG number does not match that sent by adjacent node [chars] |
The specified link station is configured with a pre-defined TG\n\ number but the adjacent node has sent a different non-zero\n\ TG number.\n\ Link activation will fail. |
snasw |
"Correct mismatched TG number configuration at this node using\n\ snasw link or at adjacent node." |
|
SNASW-3-CS_LOG_64 |
3-Error |
PROBLEM - %lu - Adjacent node sent a TG number that was pre-assigned to another LS [chars] |
Adjacent node has attempted to use a TG number for this link\n\ which is already pre-defined on another link station.\n\ Link activation will fail. |
snasw |
"Correct mismatched TG number configuration at this node using\n\ snasw link or at adjacent node." |
|
SNASW-3-CS_LOG_65 |
3-Error |
PROBLEM - %lu - Adjacent node sent a TG number that was already in use by another LS [chars] |
Adjacent node has attempted to use a TG number for this link\n\ which is already in use by another link station. This may\n\ indicate an interoperability problem.\n\ Link activation will fail. |
snasw |
"Run a trace on the link station or port to get more diagnostic\n\ information on the problem and contact support with the log\n\ and trace." |
|
SNASW-3-CS_LOG_67 |
3-Error |
PROBLEM - %lu - Insufficient storage to update topology database with link station [chars] |
Insufficient storage to update topology database with link\n\ station information.\n\ Topology will be inconsistent which may result in unexpected\n\ session activation failures typically with sense codes\n\ 8014xxxx 0806002B or 08500001. |
snasw |
- |
|
SNASW-3-CS_LOG_68 |
3-Error |
PROBLEM - %lu - Insufficient storage to update topology database with connection network [chars] |
Insufficient storage to update topology database with\n\ connection network information.\n\ Topology will be inconsistent which may result in unexpected\n\ session activation failures typically with sense codes\n\ 8014xxxx 0806002B or 08500001. |
snasw |
- |
|
SNASW-3-CS_LOG_69 |
3-Error |
PROBLEM - %lu - Insufficient storage to enable intra-node sessions [chars] |
Insufficient storage to enable intra-node sessions.\n\ Intra-node session cannot be activated. |
snasw |
- |
|
SNASW-3-CS_LOG_7 |
3-Error |
PROBLEM - %lu - No free TG numbers [chars] |
No free TG numbers between this node and the specified adjacent\n\ node. This should only occur if there are already 236 parallel\n\ TGs between this node and the adjacent node.\n\ Link activation will fail. |
snasw |
"Re-configuring the network to reduce the number of parallel TGs\n\ between this node and the specified adjacent node." |
|
SNASW-3-CS_LOG_8 |
3-Error |
PROBLEM - %lu - XID protocol error during non-activation exchange [chars] |
XID protocol error during non-activation exchange. This may\n\ indicate an interoperability problem between this node and the\n\ adjacent node. The sense codes are as follows.\n\ 0809003A - received a null XID when an activation XID\n\ format 3 was expected\n\ 0809003B - received a null XID when a nonactivation XID\n\ format 3 was expected\n\ 0809003E - activation XID received when non-activation XID\n\ expected\n\ 0809003F - adjacent node initiated a secondary-initiated\n\ non-activation XID exchange on a link that does\n\ not support secondary-initiated non-activation XID\n\ exchanges\n\ 08090042 - nonactivation exchange initiation indicator not\n\ set when expected\n\ 0809004E - received a non-null XID from a secondary NRM\n\ link station when a null XID was expected\n\ 10160002 - adjacent node has been inconsistent in its setting\n\ of ACTPU suppression indicator\n\ 10160008 - adjacent node has been inconsistent in its setting\n\ of networking capabilities\n\ 1016000B - adjacent node attempted to change TG number during\n\ nonactivation exchange to a TG number that was\n\ already in use\n\ 10160019 - adjacent node has attempted to change its CP name\n\ when CP-CP sessions supported on link station or\n\ link station not quiesced\n\ The link will be deactivated. |
snasw |
"Run a trace on the link station or port to obtain more\n\ diagnostic information on the problem. Contact support with\n\ details of the log and trace." |
|
SNASW-3-CS_LOG_9 |
3-Error |
PROBLEM - %lu - Link to host not configured correctly host is not a DSPU [chars] |
Link to host not configured correctly that is\n\ configured as a link to a DSPU.\n\msgdef_recommended_action Redefine |
- |
- |
|
SNASW-3-CS2_LOG_9 |
3-Error |
PROBLEM - %lu - DLC failure during creation [chars] |
The DLC has returned inconsistent data during creation\n\ The DLC will be destroyed and all ports and link stations\n\ defined on the DLC will be inoperative. |
snasw |
"Run a trace on the DLC and contact support with the log and\n\ trace information." |
|
SNASW-3-DEBUG_LOG_0 |
3-Error |
PROBLEM - %lu - SNA Switch DEBUG log [chars] |
SNA Switch Debug log. |
snasw |
"Report to SNA Switch technical support." |
|
SNASW-3-DLCBadMessage |
3-Error |
DLC unrecognized message header= [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
SNASW-3-DLCFailure |
3-Error |
SNASW failed to process DLC message header= [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
SNASW-3-DLCInvalidFsmState |
3-Error |
Invalid Input=[chars] to SNASW [chars] [hec] with OldState=[chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
SNASW-3-DLCPortFailure |
3-Error |
Port [chars] activation failed: [chars] |
An error was received from CLS. Typically indicates a configuration error. |
- |
LOG_STD_RECUR_ACTION |
|
SNASW-3-DLUR_LOG_11 |
3-Error |
PROBLEM - %lu - Received PLU-SLU BIND request with duplicate FQPCID [chars] |
Received PLU-SLU BIND request with duplicate FQPCID.\n\ Session activation will fail with the specified sense code.\n\ 083B0002 |
snasw |
"Report the problem to support running a trace on the specified\n\ link if more diagnostics are required." |
|
SNASW-3-DLUR_LOG_2 |
3-Error |
PROBLEM - %lu - REQACTPU rejected [chars] |
DLUS rejects REQACTPU with given sense code.\n\ An SSCP-PU session with the given DLUS will not be activated.\n\ If a backup DLUS is configured for the PU DLUR will attempt\n\ to activate the PU via the backup DLUS. |
snasw |
"Examine sense code and retry activation if appropriate." |
|
SNASW-3-DLUR_LOG_25 |
3-Error |
PROBLEM - %lu - A new DSPU has activated with the same node ID and CP name as an existing DSPU [chars] |
- |
snasw |
"Change the node ID or CP name on one of the DSPUs." |
|
SNASW-3-DS_LOG_1 |
3-Error |
PROBLEM - %lu - Network search not started because it would exceed the maximum number of concurrent locates supported by this node [chars] |
Network search not started because it would exceed the maximum\n\ number of concurrent locates supported by this node.\n\ Session activation will fail with the specified sense code. |
snasw |
"Collect trace and report the problem to support." |
|
SNASW-3-DS_LOG_11 |
3-Error |
PROBLEM - %lu - Received registration or deletion request from an unknown end node [chars] |
Received a registration or deletion request from an unknown\n\ end node. This may indicate an interoperability problem but\n\ is not considered fatal.\n\ The registration request is discarded. |
snasw |
"None." |
|
SNASW-3-DS_LOG_12 |
3-Error |
PROBLEM - %lu - Insufficient storage to register resources owned by a served end node [chars] |
Insufficient storage to register resources owned by a served\n\ end node.\n\ The specified resource will not be registered and the\n\ registration request rejected. Network searches for the\n\msgdef_recommended_action Either decrease the system load |
- |
- |
|
SNASW-3-DS_LOG_13 |
3-Error |
PROBLEM - %lu - Resource registration failure: resource already registered [chars] |
Failed to register resource for a served end node because the\n\ resource is already registered but with a different parent\n\ resource. This typically occurs when the same LU is defined\n\ on two or more end nodes.\n\ The registration request is rejected which may result in\n\ other resources not being registered and subsequent network\n\ search failures. |
snasw |
"Remove or rename the LU on one of the end nodes." |
|
SNASW-3-DS_LOG_14 |
3-Error |
PROBLEM - %lu - Registration failure notification received from network node server is badly formed [chars] |
Registration failure GDS variable received from the network\n\ node server is badly formed. This may indicate an\n\ interoperability problem.\n\ CP-CP sessions to node will be deactivated. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-DS_LOG_15 |
3-Error |
PROBLEM - %lu - Link/session failure while registering resources with network node server [chars] |
Link or session failure while registering resources with the\n\ network node server.\n\ CP-CP sessions to node will be deactivated. |
snasw |
"This log flags the fact that a registration request was\n\ disrupted by the link or session failure. Other more specific\n\ logs give details on the reasons for the failure and the\n\ appropriate actions." |
|
SNASW-3-DS_LOG_17 |
3-Error |
PROBLEM - %lu - Protocol error while registering resources with network node server [chars] |
Protocol error while registering resources with the network\n\ node server.\n\ CP-CP sessions to node will be deactivated. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-DS_LOG_21 |
3-Error |
PROBLEM - %lu - Served end node attempted to delete a home directory entry [chars] |
A served end node attempted to delete a directory entry that is\n\ defined as a home entry at this node. This normally occurs\n\ when snasw location has been used to define LUs owned by served\n\ end or LEN nodes. The Delete request is rejected with the\n\ specified sense code. |
snasw |
"Use no snasw location to remove the home entry from the directory." |
|
SNASW-3-DS_LOG_23 |
3-Error |
PROBLEM - %lu - Served end node attempted to delete a resource it doesn't own [chars] |
Served end node attempted to delete a resource when it was not\n\ registered as the owner of the resource. This may indicate an\n\ interoperability problem.\n\ The Delete request is rejected with the specified sense code.\n\ This may cause the end node to deactivate CP-CP sessions. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-DS_LOG_24 |
3-Error |
PROBLEM - %lu - Received Register/Delete GDS variable containing format errors [chars] |
Received a Register or Delete GDS variable from a served\n\ end node which contained format errors. Sense codes are as\n\ follows.\n\ 08950000 - GDS variable or control vector length error.\n\ 10140080 - invalid control vector\n\ Register or delete attempt is rejected. The resources\n\ specified will not be registered |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-DS_LOG_26 |
3-Error |
PROBLEM - %lu - Unable to register resources because this node is not authorised at the network node server [chars] |
- |
snasw |
"Modify the network node server configuration to\n\ consider this node authorised." |
|
SNASW-3-DS_LOG_27 |
3-Error |
PROBLEM - %lu - Unable to register resources because the network node server's directory is full [chars] |
A resource registration failed because the network node\n\ server's directory is full. This may indicate a shortage of\n\ storage at the network node or a configured upper bound on\n\ the size of it's directory.\n\ No further resource registration will occur until CP-CP\n\ sessions are deactivated and reestablished. |
snasw |
"Increase the size of the directory at the network server. This\n\ may be a simple configuration change or it may require freeing\n\ up storage by reducing the load at the server." |
|
SNASW-3-DS_LOG_28 |
3-Error |
PROBLEM - %lu - Resource registration failed because the resource conflicted with an existing entry in the network node's directory [chars] |
A resource registration failed because the resource conflicted\n\ with existing resources in the network node server's\n\ directory. This most commonly occurs when two LUs with the\n\ same name are defined on two different end nodes being served\n\ by the same network node. It may also occur if the network\n\ node has a home directory entry defined for the same resource.\n\ Registration of the resource in question will fail other\n\ resources should still be registered correctly. |
snasw |
"Check the network node's directory for the duplicate entry. If\n\ it is a home entry then remove the home entry from the\n\ directory. If it is a registered entry owned by a different\n\ end node redefine the LU to use a different name." |
|
SNASW-3-DS_LOG_29 |
3-Error |
PROBLEM - %lu - Resource registration failed because network node server detected a protocol error in the Register request [chars] |
A resource registration failed because the network node server\n\ detected a protocol error in the Register request. This may\n\ indicate an interoperability problem.\n\ Registration of the resource in question will fail other\n\ resources should still be registered correctly. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-DS_LOG_3 |
3-Error |
PROBLEM - %lu - Received badly formed Locate from an adjacent node [chars] |
Received badly formed Locate from an adjacent node. This may\n\ indicate an interoperability problem. Sense codes are as\n\ follows.\n\ 1010B080 - missing command parameters control vector in\n\ Found GDS variable\n\ 10140080 - GDS variable or control vector length error\n\ 1014A082 - missing search argument directory entry in Find\n\ GDS variable\n\ CP-CP sessions with adjacent node will be deactivated with the\n\ specified sense code. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-DS_LOG_30 |
3-Error |
PROBLEM - %lu - Resource registration failed with an unknown sense code [chars] |
A resource registration failed with an unknown sense code.\n\ This may indicate an interoperability problem.\n\ No further resource registration will occur until CP-CP\n\ sessions are deactivated and reestablished. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-DS_LOG_31 |
3-Error |
PROBLEM - %lu - Delete failure reply received with sense code that is unrecoverable [chars] |
Delete reply received with a sense code that is unrecoverable.\n\ CP-CP sessions to node will be deactivated. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-DS_LOG_32 |
3-Error |
PROBLEM - %lu - Unable to correlate received Register or Delete reply to a directory entry [chars] |
Directory Error Correlator returned on a Register or Delete\n\ reply cannot be correlated to a directory entry. This is\n\ considered a protocol error and may indicate an\n\ interoperability problem.\n\ CP-CP sessions to node will be deactivated. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-DS_LOG_33 |
3-Error |
PROBLEM - %lu - Unable to delete resources because this node is not authorised at the network node server [chars] |
- |
snasw |
"Modify the network node server configuration to\n\ consider this node authorised." |
|
SNASW-3-DS_LOG_4 |
3-Error |
PROBLEM - %lu - Insufficient storage to process Locate received from adjacent node [chars] |
Insufficient storage to process Locate received from adjacent\n\ node.\n\ CP-CP sessions with the adjacent node will be deactivated this\n\ avoids possible deadlocks. |
snasw |
- |
|
SNASW-3-DS_LOG_40 |
3-Error |
PROBLEM - %lu - Locate received from adjacent node exceeded the maximum number of concurrent locates supported by this node [chars] |
Locate received from adjacent node exceeded the maximum number\n\ of concurrent locates supported by this node.\n\ CP-CP sessions with the adjacent node will be deactivated this\n\ avoids possible deadlocks. |
snasw |
- |
|
SNASW-3-DS_LOG_41 |
3-Error |
PROBLEM - %lu - Insufficient storage to start a network search [chars] |
Insufficient storage to start a network search.\n\ Session activation will fail with the specified sense code. |
snasw |
"Make more resource available to SNA Switch." |
|
SNASW-3-DS_LOG_42 |
3-Error |
PROBLEM - %lu - CP-CP sessions deactivated while directed Locate outstanding [chars] |
CP-CP sessions deactivated while directed Locate in process.\n\ Session activation may fail. |
snasw |
"This log simply flags the fact that a session failure impacted\n\ a pending directed Locate. Other more specific logs give\n\ reasons for the session failure and appropriate actions." |
|
SNASW-3-DS_LOG_9 |
3-Error |
PROBLEM - %lu - Insufficient storage for CP-CP sessions [chars] |
Insufficient storage for CP-CP sessions.\n\ CP-CP sessions will be deactivated with the specified sense\n\ code. |
snasw |
- |
|
SNASW-3-DS2_LOG_1 |
3-Error |
PROBLEM - %lu - Inaccurate directory entry held for this LU [chars] |
A directed locate for this LU has been tried but the LU was\n\ not recognised at the end node stored in the directory.\n\ The directory entry is removed and a broadcast locate is sent\n\ instead. |
snasw |
"None." |
|
SNASW-3-DS2_LOG_5 |
3-Error |
PROBLEM - %lu - LEN LU registration failed because the LU name is already registered as the child of a different CP [chars] |
Node is configured to register LEN LU names when BINDs from\n\ LEN nodes are passed through us. In this case registration\n\ failed due to a resource name conflict. The LU name is already\n\ registered as the child of a different CP.\n\ Registration of the resource in question will fail so sessions\n\ to the LEN LU cannot be started except by the LEN itself.\n\ Other resources should still be registered correctly. |
snasw |
"Check the network node's directory for the duplicate entry. If\n\ it is a home entry then remove the home entry from the\n\ directory. If it is a registered entry owned by a different\n\ end node redefine the LU to use a different name." |
|
SNASW-3-EVENT |
3-Error |
[chars] |
Informational event |
snasw |
"None - informational only" |
|
SNASW-3-HPR_LOG_2 |
3-Error |
PROBLEM - %lu - Unable to activate RTP connection [chars] |
Unable to activate RTP Connection\n\ In certain situations the origin may retry activation. |
snasw |
"Examine sense code and retry activation if appropriate." |
|
SNASW-3-HPR_LOG_20 |
3-Error |
PROBLEM - %lu - Remote node supplied a corrupted RSCV: the next hop is the local CP [chars] |
An HPR Route Setup RU has been received with an RSCV that gives\n\ the local node as the next ANR hop. This is invalid. Therefore\n\ the remote node is sending invalid protocol data. |
snasw |
"Report error to remote end." |
|
SNASW-3-HS_LOG_8 |
3-Error |
PROBLEM - %lu - EXPD RU received while previous expedited data remains to be processed [chars] |
An EXPD RU has been received while previous expedited data\n\ remains to be processed.\n\ The session will be deactivated with the specified sense code.\n\ 200F0000 |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-LDLC_IP_LOG_12 |
3-Error |
PROBLEM - %lu - The IPDLC UDP stub process has abended - SNAP IPDLC will abend [chars] |
The UDP stub process has abended.\n\ IPDLC will abend itself. All links using SNAP-IPDLC will\n\ fail. SNAP-IPDLC will fail. |
snasw |
" Check for the UDP/IP problem that caused the UDP stub to\n\ abend. If the reason cannot be determined gather full trace\n\ and contact support." |
|
SNASW-3-LM_LOG_12 |
3-Error |
PROBLEM - %lu - Insufficient storage to activate LU-SSCP session for LU type 012 or 3 as SSCP [chars] |
Insufficient storage to activate LU-SSCP session for LU type\n\ 012 or 3.\n\ ACTLU request will not be sent. |
snasw |
- |
|
SNASW-3-LM_LOG_13 |
3-Error |
PROBLEM - %lu - Insufficient storage to activate LU type 012 or 3 PLU-SLU session as SLU [chars] |
Insufficient storage to activate LU type 012 or 3 PLU-SLU\n\ session.\n\ BIND request will be rejected with the specified sense code. |
snasw |
- |
|
SNASW-3-LM_LOG_14 |
3-Error |
PROBLEM - %lu - Insufficient storage to activate LU-SSCP session for LU type 012 or 3 as LU [chars] |
Insufficient storage to activate LU-SSCP session for LU type\n\ 012 or 3.\n\ ACTLU request will not be rejected with the specified sense\n\ code. |
snasw |
- |
|
SNASW-3-LM_LOG_15 |
3-Error |
PROBLEM - %lu - A BIND request received by an LU type 012 or 3 was rejected by SNA Switch because it failed parameter checks [chars] |
- |
snasw |
"If possible investigate the configuration of the system that\n\ sent the BIND request.\n\ If a configuration error is found then correct it otherwise\n\ contact support with details of the problem." |
|
SNASW-3-LM_LOG_16 |
3-Error |
PROBLEM - %lu - A BIND request received by an LU type 012 or 3 was rejected by an application connected to SNA Switch [chars] |
A BIND request received by an LU type 012 or 3 was rejected\n\ by an application connected to SNA Switch.\n\ BIND request will be rejected with the specified sense code.\n\ PLU-SLU session is not activated. |
snasw |
- |
|
SNASW-3-LM_LOG_17 |
3-Error |
PROBLEM - %lu - A BIND request received by an LU type 012 or 3 was rejected by SNA Switch because the application connection was not open [chars] |
A BIND request received by an LU type 012 or 3 was rejected\n\ because the application connection was not open. This may be\n\ caused by a normal window condition or it may indicate that the\n\ system that sent the BIND request is incorrectly configured or\n\ is defective.\n\ BIND request will be rejected with the specified sense code.\n\ PLU-SLU session is not activated. |
snasw |
"Investigate the cause of the problem. If it indicates that the\n\ system that sent the BIND request is incorrectly configured\n\ then correct the configuration error. If it appears that the\n\ system is defective then contact support with details of the\n\ problem." |
|
SNASW-3-LM_LOG_19 |
3-Error |
PROBLEM - %lu - An UNBIND RSP was received at a secondary LU [chars] |
An UNBIND RSP was received at a secondary LU. This is illegal\n\ SNA as no UNBIND RQ was sent.\n\ The UNBIND RSP is dropped. |
snasw |
"The session may not be coming down properly. Check that\n\ dependent LU applications are correctly replying to all\n\ signals. Otherwise contact support with details of the\n\ problem." |
|
SNASW-3-LM_LOG_4 |
3-Error |
PROBLEM - %lu - Insuffcient storage to dyamically define dependent LU with host [chars] |
Insufficient storage to dynamically define dependent LU with\n\ host.\n\ LU-SSCP session will not be activated. |
snasw |
- |
|
SNASW-3-LM_LOG_5 |
3-Error |
PROBLEM - %lu - Insufficient storage to BIND LU type 012 or 3 PLU-SLU session as PLU [chars] |
Insufficient storage to BIND LU type 012 or 3 PLU-SLU\n\ session.\n\ BIND request will not be sent. |
snasw |
- |
|
SNASW-3-MIBQueryFailure |
3-Error |
Query [chars] failed. NOF primary rc=[hec] secondary rc=[hec]. |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
SNASW-3-MIBRegisterFailure |
3-Error |
[chars] Indication [hec] failed. NOF primary rc=[hec] secondary rc=[hec]. |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
SNASW-3-MIBTrapFailure |
3-Error |
Trap failed. [chars] MIB OID=[chars] index OID=[chars]. |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
SNASW-3-MS_LOG_22 |
3-Error |
PROBLEM - %lu - Error message received reporting invalid format of our MDS_MUs [chars] |
MS Capabilities received an error message reporting a format\n\ error on an MDS_MU our node supposedly sent.\n\ The error message will be logged however no further action\n\ can be taken. Ignoring the message may lead to further\n\ unexpected occurrences. |
snasw |
"Contact support with details of the problem" |
|
SNASW-3-NOF_LOG_10 |
3-Error |
PROBLEM - %lu - Insufficient storage to process ACTLU [chars] |
Insufficient storage to process received ACTLU\n\ LU-SSCP session will not be started an ACTLU -ve response with\n\ the specified sense code is sent. |
snasw |
- |
|
SNASW-3-NOF_LOG_11 |
3-Error |
PROBLEM - %lu - ACTLU received for LU which is not defined locally and implicit LU definition is not supported [chars] |
ACTLU received for LU which is not defined locally and\n\ implicit LU definition is not supported. This typically\n\ indicates a mismatch between this node and the host\n\ configuration.\n\ LU-SSCP session is not activated ACTLU is rejected with the\n\ specified sense code. |
snasw |
"Remove the LU from the host configuration." |
|
SNASW-3-NOF_LOG_3 |
3-Error |
PROBLEM - %lu - Insufficient storage to start SNA Switch [chars] |
Insufficient storage to start SNA Switch.\n\ SNA Switch was not started. |
snasw |
"Make more storage available to SNA Switch." |
|
SNASW-3-NOF_LOG_7 |
3-Error |
PROBLEM - %lu - Failed to dynamically load TP [chars] |
Failed to dynamically load an APPC transaction program or CPI-C\n\ application.\n\ The received Attach will be failed with the specified sense\n\ code. |
snasw |
"Collect trace and report the problem to support." |
|
SNASW-3-PC_LOG_10 |
3-Error |
PROBLEM - %lu - Insufficient storage to start link inactivity timer [chars] |
Insufficient storage to start link-inactivity timer.\n\ Limited resource link will not be automatically deactivated. |
snasw |
- |
|
SNASW-3-PC_LOG_11 |
3-Error |
PROBLEM - %lu - Unable to forward an HPR NLP - insufficient storage [chars] |
Insufficient storage to forward HPR Network Layer Packet.\n\ NLP will be discarded. If this error occurs frequently it may\n\ cause RTP connections to path-switch or fail altogether. |
snasw |
- |
|
SNASW-3-PC_LOG_12 |
3-Error |
PROBLEM - %lu - Insufficient storage to register ANR label [chars] |
Insufficient storage to register ANR label.\n\ HPR traffic using this ANR label will not be routed correctly\n\ which may cause RTP connections to path-switch or fail\n\ altogether. |
snasw |
- |
|
SNASW-3-PD_NBA_LOG_0 |
3-Error |
Handle was not freed |
- |
- |
- |
|
SNASW-3-PD_NBA_LOG_20 |
3-Error |
Memory block still in use at termination time |
- |
- |
- |
|
SNASW-3-PD_NBA_LOG_21 |
3-Error |
Memory management inconsistency |
- |
- |
- |
|
SNASW-3-PD_NBA_LOG_22 |
3-Error |
Memory management inconsistency |
- |
- |
- |
|
SNASW-3-PD_NBA_LOG_23 |
3-Error |
Memory management inconsistency |
- |
- |
- |
|
SNASW-3-PD_NBA_LOG_24 |
3-Error |
Memory management inconsistency |
- |
- |
- |
|
SNASW-3-PD_NBA_LOG_25 |
3-Error |
Memory management inconsistency |
- |
- |
- |
|
SNASW-3-PS_LOG_1 |
3-Error |
PROBLEM - %lu - Attach rejected because requested conversation type not supported by requested transaction program [chars] |
Attach rejected because the specified conversation type is not\n\ supported by the specified transaction program. This may be\n\ a mismatch in the capabilities of the originating transaction\n\ program and the destination transaction program or it may\n\ simply be a configuration error.\n\ The Attach will be rejected. |
snasw |
"Check the conversation type or types supported by the specified\n\ transaction program and check that this matches the\n\ conversation type supported defined for the transaction program.\n\ If they match or the transaction program is not defined there\n\ is a mismatch between the originating and destination transaction\n\ programs." |
|
SNASW-3-PS_LOG_10 |
3-Error |
PROBLEM - %lu - Attach rejected because requested conversation duplex type not supported by requested transaction program [chars] |
Attach rejected because the specified conversation duplex type\n\ is not supported by the specified transaction program. This\n\ may be a mismatch in the capabilities of the originating\n\ transaction program and the destination transaction program or\n\ it may simply be a configuration error.\n\ Possible sense codes are as follows.\n\ 10086034 Half-duplex Attach not supported by TP\n\ 08640003 Full-duplex Attach not supported by TP\n\ The Attach will be rejected. |
snasw |
"Check the conversation duplex type or types supported by the\n\ specified transaction program and check that this matches the\n\ conversation type supported defined for the transaction program.\n\ If they match or the transaction program is not defined there\n\ is a mismatch between the originating and destination transaction\n\ programs." |
|
SNASW-3-PS_LOG_3 |
3-Error |
PROBLEM - %lu - Conversation ended by protocol error [chars] |
The session being used by a conversation has been deactivated\n\ because of a protocol error causing the conversation to fail.\n\ The conversation will be terminated either by an APPC\n\ primary_rc of NAP_CONV_FAILURE_NO_RETRY or a CPI-C return_code\n\ of CM_RESOURCE_FAILURE_NO_RETRY. |
snasw |
"This log gives information on which TPs and conversation have\n\ been affected by a protocol error on a session. Other more\n\ specific problem or exception logs give more information on the\n\ protocol error. Use the Session identifier to correlate this\n\ log with other related logs." |
|
SNASW-3-PS_LOG_4 |
3-Error |
PROBLEM - %lu - Conversation ended by session outage [chars] |
The session being used by a conversation has been deactivated\n\ because of a session outage causing the conversation to fail.\n\ The conversation will be terminated either by an APPC\n\ primary_rc of NAP_CONV_FAILURE_RETRY or a CPI-C return_code of\n\ CM_RESOURCE_FAILURE_RETRY. |
snasw |
"This log gives information on which TPs and conversation have\n\ been affected by a session outage. Other more specific\n\ problem or exception logs give more information on the reason\n\ for the session outage. Use the Session identifier to\n\ correlate this log with other related logs." |
|
SNASW-3-RM_LOG_0 |
3-Error |
PROBLEM - %lu - Insufficient storage to start TP instance and conversation requested by received Attach [chars] |
Insufficient storage to start the transaction program instance\n\ and conversation requested by a received Attach FMH5.\n\msgdef_recommended_action Either decrease the system load |
- |
- |
|
SNASW-3-RM_LOG_14 |
3-Error |
PROBLEM - %lu - Deactivating session because of insufficient storage [chars] |
Deactivating session because of insufficient storage.\n\ SNA Switch will deactivate the session. |
snasw |
- |
|
SNASW-3-RM_LOG_15 |
3-Error |
PROBLEM - %lu - Insufficient storage to initiate session activation requested by [MC_]ALLOCATE or CMALLC [chars] |
Insufficient storage to initiate session activation requested\n\ by ALLOCATE MC_ALLOCATE or CMALLC.\n\ [MC_]ALLOCATE will fail with primary_rc of NAP_ALLOCATION_ERROR\n\ and secondary_rc of NAP_ALLOCATION_FAILURE_NO_RETRY.\n\ CMALLC will fail with return_code of\n\ CM_ALLOCATION_FAILURE_NO_RETRY |
snasw |
- |
|
SNASW-3-RM_LOG_22 |
3-Error |
PROBLEM - %lu - LU-LU verification failed. [chars] |
LU-LU verification failed. The partner LU has sent an incorrect\n\ response to a challenge sent by a local LU. This is either a\n\ security attack or a defect in the software at the partner LU\n\ location.\n\ The session will be deactivated. |
snasw |
"Check the identity of the partner LU. If this is a defect in\n\ the software at the partner LU location then contact support." |
|
SNASW-3-RM_LOG_3 |
3-Error |
PROBLEM - %lu - Insufficient storage to start conversation requested by [MC_]ALLOCATE or CMALLC [chars] |
Insufficient storage to start a new conversation requested by\n\ ALLOCATE MC_ALLOCATE or CMALLC.\n\ [MC_]ALLOCATE will fail with primary_rc of\n\ NAP_UNEXPECTED_SYSTEM_ERROR or\n\ CMALLC with fail with return_code of CM_PRODUCT_SPECIFIC_ERROR |
snasw |
- |
|
SNASW-3-RM_LOG_37 |
3-Error |
PROBLEM - %lu - LU-LU verification protocol error [chars] |
LU-LU verification protocol error. This may indicate an\n\ interoperability problem.\n\ The session will be deactivated with the specified sense code. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-RM_LOG_42 |
3-Error |
PROBLEM - %lu - Failed to activate a new session since this would exceed LU or mode session limit [chars] |
SNA Switch was unable to activate a new session because the\n\ maximum session limit specified for the mode or the local LU\n\ would be exceeded.\n\ ALLOCATE MC_ALLOCATE or CMALLC verbs will either fail or hang\n\ waiting for a session to become free. |
snasw |
"Wait for a session to become free and retry or use a different\n\ mode." |
|
SNASW-3-RM_LOG_43 |
3-Error |
PROBLEM - %lu - Insufficient storage to start TP instance requested by TP_STARTED [chars] |
Insufficient storage to start the transaction program instance\n\ requested by TP_STARTED.\n\ If other instances of the same transaction program are active\n\ SNA Switch will queue the TP_STARTED waiting for one of them to\n\ become free. Otherwise the TP_STARTED verb will fail with\n\ primary_rc of NAP_UNEXPECTED_SYSTEM_ERROR. |
snasw |
- |
|
SNASW-3-RM_LOG_44 |
3-Error |
PROBLEM - %lu - Insufficient storage to initiate automatic session activation [chars] |
Insufficient storage to initiate automatic session activation.\n\ Fewer active sessions will be available on the specified mode\n\ which may cause application delays or failures. |
snasw |
- |
|
SNASW-3-RM_LOG_45 |
3-Error |
PROBLEM - %lu - Insufficient storage to initiate session activation requested by ACTIVATE_SESSION [chars] |
Insufficient storage to initiate session activation requested\n\ by ACTIVATE_SESSION verb.\n\ ACTIVATE_SESSION will fail with NAP_ACTIVATION_FAIL_NO_RETRY |
snasw |
- |
|
SNASW-3-RM_LOG_46 |
3-Error |
PROBLEM - %lu - Bracket protocol error [chars] |
Bracket protocol error. This may indicate a problem in the\n\ partner LU. The sense codes are as follows.\n\ 20080000 - partner LU attempted to start bracket after\n\ sending BIS\n\ 20030000 - partner LU attempted to start bracket after local\n\ LU had BID for session successfully or\n\ unexpected RTR request received\n\ 20100000 - Received negative response to BID with sense code\n\ 088B0000 from a partner LU who supports parallel\n\ sessions or\n\ BIS protocol error\n\ The session will be deactivated with the specified sense code. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-RM_LOG_47 |
3-Error |
PROBLEM - %lu - Attach protocol error [chars] |
Attach protocol error. This may indicate a problem in the\n\ partner LU. The sense codes are as follows\n\ 080F6051 - Attach security protocol violation\n\ 10086011 - LUW identifier format error or\n\ LUW identifier not specified when sync level is\n\ syncpt\n\ 10086040 - sync level not supported by session or\n\ already-verified not accepted from partner LU\n\ 10086031 - PIP not allowed by TP\n\ The session will be deactivated with the specified sense code. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-RM_LOG_48 |
3-Error |
PROBLEM - %lu - Attach rejected because security information invalid [chars] |
Attach rejected because security information invalid. This\n\ indicates an attempt to access a secure TP by an unknown user\n\ or a known user who has specified an incorrect password.\n\ The Attach will be rejected. |
snasw |
"Use the information in the log to locate the attempted security\n\ violation." |
|
SNASW-3-RM_LOG_49 |
3-Error |
PROBLEM - %lu - Attach rejected because requested sync level not supported by requested transaction program [chars] |
Attach rejected because the specified sync level is not\n\ supported by the specified transaction program. This may be\n\ a mismatch in the capabilities of the originating transaction\n\ program and the destination transaction program or it may\n\ simply be a configuration error.\n\ The Attach will be rejected. |
snasw |
"Check the sync level supported by the specified transaction\n\ program and check that it matches the sync_level defined for\n\ the transaction program. If they match or the transaction\n\ program is not defined there is a mismatch between the\n\ originating and destination transaction programs." |
|
SNASW-3-RM_LOG_50 |
3-Error |
PROBLEM - %lu - Attach rejected because requested TP is temporarily disabled [chars] |
Attach rejected because the specified TP is temporarily\n\ disabled.\n\ The Attach will be rejected. |
snasw |
"This condition is not currently supported by SNA Switch so this\n\ log should not occur." |
|
SNASW-3-RM_LOG_51 |
3-Error |
PROBLEM - %lu - Attach rejected because requested TP is permanently disabled [chars] |
Attach rejected because the specified TP is permanently\n\ disabled. This should only occur if an application has\n\ explicitly disabled the transaction program.\n\ The Attach will be rejected. |
snasw |
"Collect trace and contact support." |
|
SNASW-3-RM_LOG_52 |
3-Error |
PROBLEM - %lu - Failed to activate a new session because mode name was not recognized [chars] |
SNA Switch was unable to activate a new session because the\n\ mode name specified was not recognized.\n\ ALLOCATE MC_ALLOCATE or CMALLC verbs will fail. |
snasw |
"Check the mode name." |
|
SNASW-3-RM_LOG_53 |
3-Error |
PROBLEM - %lu - Attach rejected because security information not specified [chars] |
Attach rejected because security information not specified.\n\ This indicates an attempt to access a secure TP without\n\ specifying a user ID or password.\n\ The Attach will be rejected. |
snasw |
"Use the information in the log to locate the security mismatch" |
|
SNASW-3-RM_LOG_54 |
3-Error |
PROBLEM - %lu - Bracket protocol error [chars] |
BIS protocol error. This may indicate a problem in the\n\ partner LU. The sense code is always set to 20100000.\n\ The session will be deactivated with the specified sense code. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-RM2_LOG_0 |
3-Error |
PROBLEM - %lu - CP-CP session deactivated because of excessive delay [chars] |
An adjacent node has not responded within a reasonable period\n\ to a request on a CP-CP session. SNA Switch will deactivate\n\ CP-CP sessions with this adjacent node.\n\ CP-CP sessions are deactivated with the sense code 08640002. |
snasw |
"Contact the supplier of the adjacent node." |
|
SNASW-3-SCM_LOG_0 |
3-Error |
PROBLEM - %lu - ISR session activation failed - ISR session limit reached [chars] |
- |
snasw |
"Collect trace and report the problem to support." |
|
SNASW-3-SCM_LOG_1 |
3-Error |
PROBLEM - %lu - Protocol error in received ISR BIND request [chars] |
Protocol error in received ISR BIND request. This may indicate\n\ an interoperability problem. Sense codes are as follows.\n\ 08350008 - secondary-to-primary staging indicator incorrect\n\ 0835000C - primary-to-secondary staging indicator incorrect\n\ 10010024 - unextended non-LU6.2 BIND\n\ 10020000 - BIND RU length error\n\ ISR session activation will fail with the specified sense code. |
snasw |
"Report the problem to support running a trace on the specified\n\ link if more diagnostics are required." |
|
SNASW-3-SCM_LOG_11 |
3-Error |
PROBLEM - %lu - Received ISR BIND request with duplicate FQPCID [chars] |
Received ISR BIND request with duplicate FQPCID.\n\ ISR session activation will fail with the specified sense code.\n\ 083B0002 |
snasw |
"Report the problem to support running a trace on the specified\n\ link if more diagnostics are required." |
|
SNASW-3-SCM_LOG_12 |
3-Error |
PROBLEM - %lu - Protocol error in received ISR BIND request [chars] |
Protocol error in received ISR BIND response. This may\n\ indicate an interoperability problem. Sense codes are as\n\ follows.\n\ 08350007 - control vectors included indicator incorrect\n\ 08350008 - secondary-to-primary staging indicator incorrect\n\ 0835000C - primary-to-secondary staging indicator incorrect\n\ 086F0000 - BIND response length inconsistent\n\ 10010024 - unextended non-LU6.2 BIND response\n\ 10020000 - BIND RU length error\n\ ISR session activation will fail with the specified sense code. |
snasw |
"Report the problem to support running a trace on the specified\n\ link if more diagnostics are required." |
|
SNASW-3-SCM_LOG_13 |
3-Error |
PROBLEM - %lu - ISR is unable to support requested RU size [chars] |
ISR is unable to support RU size requested on non-negotiable\n\ BIND request or response. Sense codes are as follows.\n\ 0835000A - maximum secondary send RU size is larger than that\n\ supported by ISR\n\ 0835000B - maximum primary send RU size is larger than that\n\ supported by ISR\n\ ISR session activation will fail with the specified sense code. |
snasw |
"Collect trace and report the problem to support." |
|
SNASW-3-SCM_LOG_14 |
3-Error |
PROBLEM - %lu - ISR is unable to support requested pacing window size [chars] |
ISR is unable to support fixed receive pacing window requested\n\ on non-negotiable BIND request or response. Sense codes are as\n\ follows.\n\ 08350009 - maximum primary send window size is larger than\n\ that supported by ISR\n\ 0835000D - maximum secondary send window size is larger than\n\ that supported by ISR\n\ ISR session activation will fail with the specified sense code. |
snasw |
"Collect trace and report the problem to support." |
|
SNASW-3-SCM_LOG_15 |
3-Error |
PROBLEM - %lu - Insufficient storage to activate ISR session [chars] |
Insufficient storage to activate ISR session\n\ ISR session activation will fail with the specified sense code\n\ 08120014. |
snasw |
- |
|
SNASW-3-SCM_LOG_16 |
3-Error |
PROBLEM - %lu - Slow session activation detected [chars] |
A session activation was started but has not completed after\n\ a significant time. |
snasw |
"If the session does not become active contact support with details of\n\ this log. " |
|
SNASW-3-SCM_LOG_3 |
3-Error |
PROBLEM - %lu - Unable to identify or activate the next hop of an ISR session [chars] |
Unable to identify or activate the next hop of an ISR session.\n\ ISR session activation will fail with the specified sense code. |
snasw |
"This log is preceded by other logs giving more specific reasons\n\ for the failure. Follow the actions given in those logs." |
|
SNASW-3-SCM_LOG_4 |
3-Error |
PROBLEM - %lu - Fatal error detected in ISR session [chars] |
ISR detected a fatal error in an intermediate session.\n\ The ISR session will be deactivated with the specified sense\n\ code. |
snasw |
"This log should be preceded by a log 536 or 537. Follow the\n\ actions given in those logs." |
|
SNASW-3-SCM_LOG_5 |
3-Error |
PROBLEM - %lu - ISR session failure because of link outage or error [chars] |
ISR session failed because of link outage or error.\n\ The ISR session will be deactivated with the specified sense\n\ code. |
snasw |
"This log gives information on which ISR sessions are affected\n\ by a link outage or error. Preceding logs give more specific\n\ information about the reason for the link outage or error." |
|
SNASW-3-SCM_LOG_6 |
3-Error |
PROBLEM - %lu - Unable to assign LFSID to secondary stage of ISR session [chars] |
- |
snasw |
"This log gives information on which ISR session is affected by\n\ a failure in the LFSID table management. Preceding logs give\n\ more detail on the reason for the failure." |
|
SNASW-3-SM_LOG_0 |
3-Error |
PROBLEM - %lu - Insufficient storage to define LU type 6.2 [chars] |
Insufficient storage to define a new LU type 6.2. |
snasw |
- |
|
SNASW-3-SM_LOG_1 |
3-Error |
PROBLEM - %lu - Fatal error detected on LU6.2 session [chars] |
Fatal error detected on LU6.2 session.\n\ Session will be deactivated with specified sense code. |
snasw |
- |
|
SNASW-3-SM_LOG_10 |
3-Error |
PROBLEM - %lu - Format error in received LU6.2 BIND request [chars] |
Format error in received LU6.2 BIND request. Sense codes are\n\ as follows.\n\ 0835xxxx - parameter error at offset xxxx in BIND RU\n\ 088C6000 - FQPCID not included in extended BIND\n\ 083B0000 - invalid FQPCID format\n\ Session activation will fail with specified sense code. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-SM_LOG_11 |
3-Error |
PROBLEM - %lu - Format error in received LU6.2 BIND response [chars] |
Format error in received LU6.2 BIND response. Sense codes are\n\ as follows.\n\ 0835xxxx - parameter error at offset xxxx in BIND RU\n\ Session activation will fail with specified sense code. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-SM_LOG_12 |
3-Error |
PROBLEM - %lu - LU-mode session limit exceeded [chars] |
LU-mode session limit exceeded. This problem normally should\n\ not occur since the session limits are negotiated with a CNOS\n\ exchange prior to sessions being activated. However this\n\ log can also be caused by a normal race condition when the\n\ session limits are reset or when this node has been restarted\n\ after having previously had sessions with this partner LU.\n\ Session activation will fail with specified sense code. |
snasw |
"If problem persists check the session limits and active\n\ session counts on the specified local LU partner LU." |
|
SNASW-3-SM_LOG_14 |
3-Error |
PROBLEM - %lu - Detected consistency errors in received BIND request [chars] |
Detected consistency errors in received BIND request. This\n\ may indicate an interoperability problem. Sense codes are as\n\ follows.\n\ 0835xxxx - parameter error at offset xxxx in BIND RU\n\ 080F6051 - security error\n\ Session activation will fail with specified sense code. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-SM_LOG_15 |
3-Error |
PROBLEM - %lu - Detected consistency errors in received BIND response [chars] |
Detected consistency errors in received BIND response. This\n\ may indicate an interoperability problem. Sense codes are as\n\ follows\n\ 0835xxxx - parameter error at offset xxxx in BIND RU\n\ 080F6051 - security error\n\ Session will be deactivated with specified sense code. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-SM_LOG_16 |
3-Error |
PROBLEM - %lu - Format error in received UNBIND request [chars] |
Format error in received UNBIND request. This may indicate an\n\ interoperability problem. Sense codes are as follows.\n\ 0835xxxx - parameter error at offset xxxx in UNBIND RU\n\ 0895xxyy - format error in control vector where xx is key of\n\ control vector and yy is offset into control\n\ vector of byte in error\n\ 10020000 - RU length error\n\ None session will still be deactivated. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-SM_LOG_2 |
3-Error |
PROBLEM - %lu - BIND or +RSPBIND specifies duplex support which is different from that for existing sessions [chars] |
- |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-SM_LOG_31 |
3-Error |
PROBLEM - %lu - Insufficient storage to activate LU-SSCP session [chars] |
Insufficient storage to activate LU-SSCP session.\n\ ACTLU will be rejected with specified sense code. |
snasw |
- |
|
SNASW-3-SM_LOG_33 |
3-Error |
PROBLEM - %lu - Insufficient storage to reassemble received BIND response [chars] |
Insufficient storage to reassemble received BIND response.\n\ Session will be deactivated with the specified sense code. |
snasw |
- |
|
SNASW-3-SM_LOG_34 |
3-Error |
PROBLEM - %lu - Badly formed partner LU name in received BIND request [chars] |
Partner LU name on received BIND request is badly formed.\n\ Session activation will fail with the specified sense code. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-SM_LOG_35 |
3-Error |
PROBLEM - %lu - Unrecognized mode name in received BIND request [chars] |
Mode name on received BIND request is unrecognized.\n\ Session activation will fail with the specified sense code. |
snasw |
"Modify the partner LU configuration so it does not\n\ attempt to use the unrecognized mode." |
|
SNASW-3-SM_LOG_36 |
3-Error |
PROBLEM - %lu - Unable to activate session to single session partner LU because there is an active session on another mode [chars] |
Unable to activate session to single session partner LU\n\ because there is already an active session on another mode.\n\ This usually indicates contention between two or more APPC\n\ transaction programs or CPI-C applications for the same\n\ dependent LU6.2.\n\ Session activation will fail with specified sense code which\n\ may cause ALLOCATE MC_ALLOCATE or CMALLC requests to fail. |
snasw |
"Collect trace and report the problem to support." |
|
SNASW-3-SM_LOG_41 |
3-Error |
PROBLEM - %lu - FQPCID collision on received BIND request [chars] |
FQPCID collision. The FQPCID specified on a received BIND\n\ request matches the FQPCID being used for an existing active\n\ session. This can be caused by a collision in the hashing\n\ algorithm used to generate an FQPCID or it may indicate a\n\ problem in the node generating the FQPCID.\n\ Session activation will fail with specified sense code. |
snasw |
"If problem is persistent or occurs often contact support with\n\ details of the problem." |
|
SNASW-3-SM_LOG_42 |
3-Error |
PROBLEM - %lu - Session identifier collision on received BIND request [chars] |
Session identifier collision. The session identifier specified\n\ on a received BIND request matches the session identifier being\n\ an existing active session.\n\ Session activation will fail with specified sense code. |
snasw |
"If problem is persistent or occurs often contact support with\n\ details of the problem." |
|
SNASW-3-SM_LOG_45 |
3-Error |
PROBLEM - %lu - LU-LU verification protocol mismatch. [chars] |
LU-LU verification protocol mismatch. The partner LU has\n\ requested that the basic protocol is used when the local LU\n\ runs only the enhanced protocol with the partner LU. The local\n\ LU may be configured to run only the enhanced protocol with the\n\ partner LU or it may be configured to run either protocol with\n\ the partner LU and has determined that the partner LU can run\n\ the enhanced protocol. This is either\n\ i a mismatch in configuration\n\msgdef_recommended_action Check the identity of the partner LU. If the problem is\n\ |
- |
- |
|
SNASW-3-SM_LOG_46 |
3-Error |
PROBLEM - %lu - LU-LU verification failed. [chars] |
LU-LU verification failed. The partner LU has sent an incorrect\n\ response to a challenge sent by a local LU. This is either a\n\ mismatch in configuration or a security attack.\n\ Session activation will fail. |
snasw |
- |
|
SNASW-3-SM_LOG_47 |
3-Error |
PROBLEM - %lu - LU-LU verification protocol failed. [chars] |
Duplicate random data received. A list is kept of all random\n\ data sent as challenges by the local LU. Receiving duplicate\n\ random data from a partner LU should be a rare event and is\n\ evidence of a security attack.\n\ Session activation will fail. |
snasw |
- |
|
SNASW-3-SM_LOG_48 |
3-Error |
PROBLEM - %lu - BIND-RSP request received in response to a BIND request [chars] |
- |
snasw |
"If the sense code indicates a configuration error check for\n\ inconsistencies between the configuration at the local LU and\n\ the configuration at the partner LU. If the configuration is\n\ consistent and the problem persists contact support with\n\ details of the problem." |
|
SNASW-3-SM_LOG_5 |
3-Error |
PROBLEM - %lu - Insufficient storage to activate LU6.2 session [chars] |
Insufficient storage to activate LU6.2 session.\n\ Session activation will fail with the specified sense code. |
snasw |
- |
|
SNASW-3-SS_LOG_16 |
3-Error |
PROBLEM - %lu - CP capabilities exchange failed because of contention winner CP-CP session failure [chars] |
CP capabilities exchange failed because of contention winner\n\ CP-CP session failure.\n\ Contention loser CP-CP session will be deactivated. SNA Switch\n\ will attempt to reactivate CP-CP sessions with this adjacent\n\ CP. |
snasw |
"This log flags the fact that a CP-CP session failed. Other\n\ logs give more details on the reason for the session failure\n\ eg. insufficient resources link failure." |
|
SNASW-3-SS_LOG_5 |
3-Error |
PROBLEM - %lu - CP capabilities exchange failed because of contention loser CP-CP session failure [chars] |
CP capabilities exchange failed because of contention loser\n\ CP-CP session failure.\n\ Contention winner CP-CP session will be deactivated. SNA Switch\n\ will attempt to reactivate CP-CP sessions with this adjacent\n\ CP. |
snasw |
"This log flags the fact that a CP-CP session failed. Other\n\ logs give more details on the reason for the session failure\n\ eg. insufficient resources link failure." |
|
SNASW-3-SS_LOG_7 |
3-Error |
PROBLEM - %lu - Insufficient storage to generate Alert CPSS003 [chars] |
Insufficient storage to generate Alert CPSS003 protocol error\n\ in received BIND or LOCATE.\n\msgdef_recommended_action Either decrease the system load |
- |
- |
|
SNASW-3-SS_LOG_8 |
3-Error |
PROBLEM - %lu - CP capabilities exchange failed because of protocol error [chars] |
CP capabilities exchange has failed because of protocol error.\n\ This may indicate an interoperability problem. Sense codes are\n\ as follows.\n\ 08060030 - CP capabilities requested by unknown CP\n\ 08210002 - CP capabilities requested on other than CPSVCMG\n\ mode\n\ 08150007 - CP capabilities requested when CP-CP session\n\ already established\n\ 08B60000 - CP-CP sessions not supported by adjacent node\n\ 08090039 - CP transaction error\n\ CP-CP sessions with the specified adjacent node will be\n\ deactivated. SNA Switch will not attempt to reactivate CP-CP\n\ sessions with this adjacent CP. |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-SS_LOG_9 |
3-Error |
PROBLEM - %lu - Protocol error in CP capabilities exchange [chars] |
- |
snasw |
"Contact support with details of the problem." |
|
SNASW-3-TNTL_LOG_1 |
3-Error |
PROBLEM - %lu - Invalid internal state detected [chars] |
A software error has caused a bad internal state to be\n\ detected. Potential loss of function - refer to other problem logs for\n\ actual effect. |
snasw |
"Shut down and restart" |
|
SNASW-3-TRACE |
3-Error |
Diagnostic trace record too large for configured buffer. Buffer ID [hec] |
A cyclic trace buffer could not be resized due to insufficient\n\ memory. The previously allocated buffer if any will continue\n\ to be used. |
snasw |
"Reconfigure a smaller buffer-size for the specified buffer type." |
|
SNASW-3-TS_LOG_13 |
3-Error |
PROBLEM - %lu - Failed to send alert due to insufficient memory [chars] |
Insufficient Memory was available to send an Alert.\n\ The Host will not see an Alert. The alert number below\n\ identifies the alert\n\ 1 - CPDB001\n\ 2 - CPDB002\n\ 3 - CPDB003\n\ 46 - CPDB004\n\ 57 - CPDB005\n\ The alerts are detailed in the Management Services Reference\n\ C30-3346\n\msgdef_recommended_action Either decrease the system load |
- |
- |
|
SNASW-4-APPN_LOG_0 |
4-Warning |
EXCEPTION - %lu - SNA Switch could not allocate necessary storage [chars] |
SNA Switch could not allocate necessary storage.\n\ Some operation may fail. See other logs. |
snasw |
- |
|
SNASW-4-APPN_LOG_2 |
4-Warning |
EXCEPTION - %lu - SNA Switch cryptography call failed possibly due to missing password [chars] |
A call from SNA Switch to perform a cryptographic operation\n\ failed.\n\ Session activation will fail or an active session will end\n\ abnormally with the given sense code or some other action will\n\ fail. More information may appear in subsequent logs. |
snasw |
"Check following logs for evidence of failed session activation.\n\ If this is evident check MODE LS or INTERNAL PU definitions\n\ for cryptographic support. Check that any passwords necessary\n\ have been defined.\n\ If this problem occurs intermittently or with sessions already\n\ active with the same PLU SLU and mode then make more storage\n\ available to SNA Switch." |
|
SNASW-4-ASM_LOG_15 |
4-Warning |
EXCEPTION - %lu - Insufficient storage to deactivate link [chars] |
Insufficient storage to deactivate a link.\n\ The link will not be deactivated |
snasw |
- |
|
SNASW-4-ASM_LOG_18 |
4-Warning |
EXCEPTION - %lu - Unable to correlate received BIND response [chars] |
Unable to correlate received BIND response. This is a normal\n\ race condition caused by a BIND being followed immediately\n\ by an UNBIND for the same session.\n\ BIND response is discarded. |
snasw |
"None." |
|
SNASW-4-ASM_LOG_25 |
4-Warning |
EXCEPTION - %lu - Unable to extend local form session identifier routing table [chars] |
Unable to extend local form session identifier routing table.\n\ Session activation will fail with the specified sense code. |
snasw |
- |
|
SNASW-4-ASM_LOG_26 |
4-Warning |
EXCEPTION - %lu - Independent LU session deactivated because LU deleted [chars] |
An independent LU-LU session has been deactivated because the\n\ local LU has been deleted.\n\ None. |
snasw |
"None." |
|
SNASW-4-ASM_LOG_29 |
4-Warning |
EXCEPTION - %lu - Dependent LU session deactivated because LU deleted [chars] |
A dependent LU-LU session has been deactivated because the\n\ LU has been deleted.\n\ None. |
snasw |
"None." |
|
SNASW-4-CH_LOG_0 |
4-Warning |
EXCEPTION - %lu - LU type 012 or 3 format error [chars] |
LU type 012 or 3 format error. This may indicate an\n\ interoperability problem.\n\ The PIU containing the error is discarded. |
snasw |
"Contact support with details of the problem" |
|
SNASW-4-CH_LOG_1 |
4-Warning |
EXCEPTION - %lu - LU type 012 or 3 session ended abnormally because of insufficient storage [chars] |
LU type 012 or 3 session ended abnormally because of\n\ insufficient storage.\n\ Session will be deactivated with the specified sense code. |
snasw |
- |
|
SNASW-4-CH_LOG_2 |
4-Warning |
EXCEPTION - %lu - LU type 012 or 3 session ended abnormally while receiving data [chars] |
LU type 012 or 3 session ended abnormally while receiving\n\ data.\n\ Session will be deactivated with the specified sense code. |
snasw |
"Contact support with details of the problem." |
|
SNASW-4-CH_LOG_3 |
4-Warning |
EXCEPTION - %lu - LU type 012 or 3 session ended abnormally because of invalid application data [chars] |
LU type 012 or 3 session ended abnormally because of\n\ invalid data received from application.\n\ Session will be deactivated with the specified sense code. |
snasw |
"Contact support with details of the problem." |
|
SNASW-4-CH_LOG_4 |
4-Warning |
EXCEPTION - %lu - Application sent invalid Data message [chars] |
LU type 012 or 3 application sent invalid Data message.\n\ Status Acknowledge NACK-2 sent to application. |
snasw |
"Investigate the error in the application." |
|
SNASW-4-CH_LOG_5 |
4-Warning |
EXCEPTION - %lu - Application sent invalid Status Control message [chars] |
LU type 012 or 3 application sent invalid Status Control\n\ message.\n\ Status Control NACK-2 sent to application. |
snasw |
"Investigate the error in the application." |
|
SNASW-4-CH_LOG_6 |
4-Warning |
EXCEPTION - %lu - Application sent invalid Acknowledgment or Status message [chars] |
LU type 012 or 3 application sent invalid Acknowledgment or\n\ Status message.\n\ Status Error sent to application. |
snasw |
"Investigate the error in the application." |
|
SNASW-4-CH_LOG_8 |
4-Warning |
EXCEPTION - %lu - Insufficient storage to report RTM statistics to Host [chars] |
Insufficient storage to report RTM statistics to host.\n\ RTM statistics displayed by host will be inconsistent. |
snasw |
- |
|
SNASW-4-CH_LOG_9 |
4-Warning |
EXCEPTION - %lu - Insufficient storage to report RTM status to application [chars] |
Insufficient storage to report RTM status to application.\n\ RTM statistics reported and displayed by application may be\n\ inconsistent. |
snasw |
- |
|
SNASW-4-CH2_LOG_0 |
4-Warning |
EXCEPTION - %lu - CRV exchange failed on a PLU-SLU session. The session will fail [chars] |
CRV exchange failed. This indicates the cryptography keys\n\ configured at this LU and the partner LU are inconsistent.\n\ Session will be deactivated with the specified sense code\n\ 08350001. |
snasw |
- |
|
SNASW-4-CH2_LOG_1 |
4-Warning |
EXCEPTION - %lu - Protocol error during CRV exchange [chars] |
Protocol error during CRV exchange. This indicates a possible\n\ interoperability problem. Sense codes are as follows.\n\ 20090000 - CRV request received from secondary LU or\n\ CRV response received from primary LU or\n\ CRV not received when expected\n\ 10020000 - CRV RU too short\n\ 400F0000 - CRV with FI not set\n\ 400B0000 - CRV chain indicators not set to BC EC\n\ 40140000 - CRV not RQD1\n\ 40110000 - CRV not expedited\n\ 40150000 - CRV with QRI not set\n\ 40080000 - CRV with PI set\n\ 400C0000 - CRV request with BBI EBI or CEBI set\n\ 400D0000 - CRV request with CDI set\n\ 40100000 - CRV request with CSI set to CODE1\n\ 40160000 - CRV request with EDI set\n\ 40170000 - CRV request with PDI set\n\ 40130000 - CRV response RTI and SDI inconsistent\n\ Session will be deactivated with specified sense code. |
snasw |
- |
|
SNASW-4-CH2_LOG_2 |
4-Warning |
EXCEPTION - %lu - Insufficient storage to initialise half session [chars] |
Insufficient storage to initialise the half session.\n\ The half session will fail to activate with the specified sense\n\ code. |
snasw |
- |
|
SNASW-4-CPUUsage |
4-Warning |
SNASw process type 0x[hec] ran for %lu ms processing IPS of type 0x[hec] address 0x%lx |
A process within SNA Switch ran for an unexpectedly\n\ long time. |
- |
LOG_STD_RECUR_ACTION |
|
SNASW-4-CS_LOG_12 |
4-Warning |
EXCEPTION - %lu - Insufficient storage to perform orderly link deactivation link deactivated immediate instead [chars] |
Insufficient storage to perform orderly link deactivation\n\ performing immediate deactivation instead.\n\ None. |
snasw |
- |
|
SNASW-4-CS_LOG_14 |
4-Warning |
EXCEPTION - %lu - Insufficient storage to update ANR routing tables following deactivation of an HPR-capable link [chars] |
Insufficient storage to update ANR routing tables following\n\ deactivation of an HPR-capable link.\n\ The node may not be able to free resources that are no longer\n\ required but will otherwise operate normally. |
snasw |
- |
|
SNASW-4-CS_LOG_15 |
4-Warning |
EXCEPTION - %lu - Insufficient storage to update ANR routing tables following activation of an HPR-capable link [chars] |
Insufficient storage to update ANR routing tables following\n\ activation of an HPR-capable link.\n\ HPR traffic using this ANR label will not be routed correctly\n\ which may cause RTP connections to path-switch or fail\n\ altogether. |
snasw |
- |
|
SNASW-4-CS_LOG_19 |
4-Warning |
EXCEPTION - %lu - Insufficient storage to forward Alert generated by DLC [chars] |
Insufficient storage to forward Alert generated by DLC.\n\ Alert will be discarded. |
snasw |
- |
|
SNASW-4-CS_LOG_25 |
4-Warning |
EXCEPTION - %lu - Link not configured for automatic activation or last stopped non-automatically [chars] |
A session or application required SNA Switch to automatically\n\ activate a link station but the link station was not\n\ configured to be automatically activated or was last stopped\n\ non-automatically.\n\ The session or application will fail with the specified sense\n\ code. |
snasw |
- |
|
SNASW-4-CS_LOG_26 |
4-Warning |
EXCEPTION - %lu - Unable to activate link station because owning port is not active [chars] |
- |
snasw |
"If possible increase the port link-activation limits.\n\ Otherwise check the consistency of the network topology." |
|
SNASW-4-CS_LOG_27 |
4-Warning |
EXCEPTION - %lu - Unable to find requested link [chars] |
- |
snasw |
"Check the consistency of the network topology." |
|
SNASW-4-CS_LOG_28 |
4-Warning |
EXCEPTION - %lu - Unable to activate dynamic link station because owning port is not active [chars] |
- |
snasw |
"If possible increase the port activation limits. Otherwise\n\ check the consistency of the network topology." |
|
SNASW-4-CS_LOG_29 |
4-Warning |
EXCEPTION - %lu - Unable to find requested connection network [chars] |
- |
snasw |
"Check the consistency of the network topology." |
|
SNASW-4-CS_LOG_35 |
4-Warning |
EXCEPTION - %lu - Unable to activate link station because port total link-activation limit reached [chars] |
- |
snasw |
"Check the consistency of the network topology." |
|
SNASW-4-CS_LOG_36 |
4-Warning |
EXCEPTION - %lu - Unable to activate link station because port outbound link-activation limit reached [chars] |
- |
snasw |
"Check the consistency of the network topology." |
|
SNASW-4-CS_LOG_37 |
4-Warning |
EXCEPTION - %lu - Unable to activate dynamic link station because port total link-activation limit reached [chars] |
- |
snasw |
"Check the consistency of the network topology." |
|
SNASW-4-CS_LOG_38 |
4-Warning |
EXCEPTION - %lu - Unable to activate dynamic link station because port outbound link-activation limit reached [chars] |
- |
snasw |
"Check the consistency of the network topology." |
|
SNASW-4-CS_LOG_43 |
4-Warning |
EXCEPTION - %lu - Unable to find requested link [chars] |
A locally initiated dependent session activation request\n\ required SNA Switch to automatically activate a link to a\n\ specified PU name but SNA Switch was unable to identify the\n\ a link to the PU. This problem indicates an inconsistent local\n\ configuration which is transient and is caused by a recent\n\ modification.\n\ The session activation request will fail with the specified\n\ sense code. |
snasw |
"Check the consistency of the local configuration link\n\ definitions can be viewed using show snasw link." |
|
SNASW-4-CS_LOG_52 |
4-Warning |
EXCEPTION - %lu - Unable to find requested connection network [chars] |
- |
snasw |
"Check the consistency of the network topology." |
|
SNASW-4-CS_LOG_61 |
4-Warning |
EXCEPTION - %lu - Unable to start requested CP-CP sessions with adjacent node [chars] |
The specified link is configured to support CP-CP sessions but\n\ these sessions could not be started. This could either be\n\ because the remote node is not configured to support CP-CP\n\ sessions on this link or because both the local and remote\n\ nodes are End Nodes and hence CP-CP sessions are not allowed\n\ to be started.\n\ CP-CP sessions will not be established. |
snasw |
"Correct the configuration mismatch either by removing CP-CP\n\ sessions support from the local connection definition or by\n\ adding it to the adjacent node's connection definition." |
|
SNASW-4-CS2_LOG_10 |
4-Warning |
EXCEPTION - %lu - Link activation retry limit reached [chars] |
An automatic retry link station is still inactive after the\n\ maximum allowed number of retries.\n\ The link station will remain inactive awaiting operator\n\ intervention. In the mean time the activation of any sessions\n\ relying on this link station will fail. |
snasw |
"Check surrounding logs for link activation failures. Check the\n\ configuration of the link station. Check the state of the\n\ adjacent node. Issue snasw start link to retry activation." |
|
SNASW-4-CS2_LOG_11 |
4-Warning |
EXCEPTION - %lu - A request to activate a connection network TG was rejected because the local and destination link addresses were incompatible [chars] |
SNA Switch cannot start a link to an adjacent node over a\n\ connection network TG because the link address on the\n\ local node is not compatible with the link address on the\n\ adjacent node.\n\ The session will fail with the specified sense code. |
snasw |
"Check the local and destination link addresses." |
|
SNASW-4-CS2_LOG_12 |
4-Warning |
EXCEPTION - %lu - A request to activate a connection network TG was rejected because a defined link was already active between the local and destination address and multiple links are not supported [chars] |
SNA Switch cannot start a link to an adjacent node over a\n\ connection network TG because the DLC does not support mutiple\n\ links between the local and destination addresses.\n\ The session will fail with the specified sense code. |
snasw |
"Check the local and destination link addresses." |
|
SNASW-4-CS2_LOG_2 |
4-Warning |
EXCEPTION - %lu - Link activation race detected - local node responsible for disconnect [chars] |
A link activation race was detected on an ATM port. The local\n\ node is responsible for resolving this race.\n\ The local node will disconnect its link. The remote node's link\n\ activation request will succeed. |
snasw |
"This is a normal race condition - no action is required." |
|
SNASW-4-CS2_LOG_25 |
4-Warning |
EXCEPTION - %lu - Insufficient resources to unregister adjacent LEN [chars] |
- |
snasw |
"Ensure sufficient resources are available to SNA Switch and then\n\ re-cycle the link to the required state." |
|
SNASW-4-CS2_LOG_26 |
4-Warning |
EXCEPTION - %lu - Invalid TG descriptor received from DLUS [chars] |
An invalid TG descriptor was received from a DLUS.\n\ The PU will not be activated. |
snasw |
"Check the configuration of the DLUS named by this log. Contact\n\ support with details of the problem." |
|
SNASW-4-CS2_LOG_27 |
4-Warning |
EXCEPTION - %lu - A DLUS-defined downstream DLUR-served link could not be defined [chars] |
A DLUS-defined downstream DLUR-served link could not be defined\n\ because either:\n\ - the specified port does not exist\n\ - there is an existing link station to the same destination\n\ address.\n\ The PU will not be activated. |
snasw |
"Correct the configuration." |
|
SNASW-4-CS2_LOG_28 |
4-Warning |
EXCEPTION - %lu - A DLUS-defined downstream DLUR-served link failed to activate [chars] |
A DLUS-defined downstream link failed to activate.\n\ The PU will not be activated. |
snasw |
"Check that the named port is active. Check that the downstream\n\ node at the given address is powered on. Check surrounding\n\ logs for reasons that the named LS has not activated. Check\n\ the configuration of the DLUS." |
|
SNASW-4-CS2_LOG_29 |
4-Warning |
EXCEPTION - %lu - DLUS-defined DSPU name clashes with locally-defined DSPU name [chars] |
A DLUS-defined DSPU name clashes with the locally-defined DSPU\n\ name of a different PU.\n\ An implicit link will fail. The ACTPU for the DSPU connected\n\ over this link will be rejected. |
snasw |
"Reconfigure this node or the DLUS to remove the clash in the\n\ use of this PU name. If the DLUS and the DLUR use the same PU\n\ name then they must apply this name to the same PU." |
|
SNASW-4-CS2_LOG_3 |
4-Warning |
EXCEPTION - %lu - Link activation race detected - adjacent node responsible for disconnect [chars] |
A link activation race was detected on an ATM port. The remote\n\ node is responsible for resolving this race.\n\ The local node will send a negotiation error CV indicating that\n\ the remote link activation request should fail. The local\n\ node's link activation request will succeed. |
snasw |
"This is a normal race condition - no action is required." |
|
SNASW-4-CS2_LOG_30 |
4-Warning |
EXCEPTION - %lu - Insufficient information to create a DLUS-defined link to a DLUR DSPU [chars] |
Insufficient information to create a DLUS-defined link.\n\ A PU will not be activated. The ACTPU for the named PU will\n\ be rejected with the given sense code. |
snasw |
- |
|
SNASW-4-CS2_LOG_4 |
4-Warning |
EXCEPTION - %lu - PORT_BANDWIDTH_UPDATE status = QUIESCING received [chars] |
- |
snasw |
"If possible increase the bandwidth available to the local\n\ port." |
|
SNASW-4-CS2_LOG_5 |
4-Warning |
EXCEPTION - %lu - PORT_BANDWIDTH_UPDATE status = OK received [chars] |
- |
snasw |
"To avoid future problems with bandwidth shortage increase\n\ the bandwidth available to the local port." |
|
SNASW-4-DLUR_LOG_1 |
4-Warning |
EXCEPTION - %lu - UNBIND could not be correlated to DLUR-served LU [chars] |
- |
snasw |
"None." |
|
SNASW-4-DLUR_LOG_10 |
4-Warning |
EXCEPTION - %lu - Failed to contact a DLUS for PU. Retry count exceeded. [chars] |
The DLUR has failed to contact either the DLUS or the backup/\n\ default DLUSs after the configured number of retries.\n\ Contact is not made with the DLUS. |
snasw |
"Check earlier logs for causes of individual failures to contact\n\ Host. Resolve any problems or increase the timeout or retry\n\ count and try again.\n\ " |
|
SNASW-4-DLUR_LOG_14 |
4-Warning |
EXCEPTION - %lu - An attempt to activate a persistent pipe to a DLUS has failed [chars] |
DLUR has requested a persistent pipe to a DLUS but the DLUS\n\ does not support persistent pipes.\n\ The sense codes are as follows.\n\ 088E0009 - the DLUR has failed the pipe activation because it\n\ requires all pipes to be persistent.\n\ 08A0000C - the DLUS has failed the pipe activation because\n\ there is no PU needing service.\n\ The attempt to activate a persistent pipe to the DLUS will\n\ fail. |
snasw |
"If the DLUR is unable to contact a different DLUS that does\n\ support persistent pipes then the following should be\n\ considered.\n\ If the sense code is 088E0009 then DLUR requirement for\n\ persistent pipes could be removed.\n\ Otherwise the DLUS must be upgraded to support persistent\n\ pipes." |
|
SNASW-4-DLUR_LOG_15 |
4-Warning |
EXCEPTION - %lu - A DLUS has sent an ACTPU without a PU name [chars] |
A DLUS has sent an ACTPU without a PU name.\n\ The ACTPU will be rejected with the specified sense code. PU\n\ activation will not continue. |
snasw |
"Check the status of the named DLUS. Check that it is correctly\n\ configured. Optionally reconfigure SNA Switch to use a\n\ different DLUS." |
|
SNASW-4-DLUR_LOG_16 |
4-Warning |
EXCEPTION - %lu - A DLUS has sent an ACTPU with a PU name that is already in use [chars] |
A DLUS has sent an ACTPU with a PU name that is already in use.\n\ The ACTPU will be rejected with the specified sense code. PU\n\ activation will not continue. |
snasw |
"Reconfigure the DLUS or the DLUR to use different PU names.\n\ If the DLUS and the DLUR use the same PU name then they must\n\ apply the name to the same PU." |
|
SNASW-4-DLUR_LOG_17 |
4-Warning |
EXCEPTION - %lu - A DLUS has sent an ACTPU with a PU name different from the name in the last ACTPU received for the same DSPU. [chars] |
A DLUS has sent an ACTPU with a PU name that is different to\n\ the PU name in the last ACTPU received for the same DSPU.\n\ The PU name of this implicit or DLUS-defined DSPU will change\n\ its name to the name from this new ACTPU. |
snasw |
- |
|
SNASW-4-DLUR_LOG_18 |
4-Warning |
EXCEPTION - %lu - Failed to contact one or both of the default DLUS when attempting to activate a persistent pipe required by a DLUS-dependent port. The retry count is exceeded. [chars] |
The DLUR has failed to contact either the default primary DLUS\n\ or the default backup DLUS or both after the configured number\n\ of retries when attempting to activate a persistent pipe\n\ required to enable a DLUS-dependent port.\n\ The DLUS-dependent port is not enbaled. |
snasw |
"Check earlier logs for causes of individual failures to contact\n\ Host. Resolve any problems or increase the timeout or retry\n\ count and try again." |
|
SNASW-4-DLUR_LOG_20 |
4-Warning |
EXCEPTION - %lu - Invalid MU type received by DLUR [chars] |
An invalid MU type has been received by DLUR from an internal\n\ or downstream PU.\n\ None the invalid MU will be discarded. |
snasw |
"If this is an internal PU then contact support with details of\n\ this log. If this is a downstream PU then contact the supplier\n\ of the downstream node." |
|
SNASW-4-DLUR_LOG_21 |
4-Warning |
EXCEPTION - %lu - Different PUs have LUs whose names clash [chars] |
Two LUs of the same name exist under different PUs. One is\n\ already activated and DLUS has attempted to activate the other.\n\ The second LU will not be activated. |
snasw |
"Rename one of the LUs with a unique network name." |
|
SNASW-4-DLUR_LOG_22 |
4-Warning |
EXCEPTION - %lu - PU not found for REQACTPU RSP or REQDACTPU [chars] |
A REQACTPU RSP or REQDACTPU has been recevied and the node has\n\ not been able to correlate it to a PU_CB.\n\ The REQDACTPURSP will be discarded. |
snasw |
"Contact the supplier of the DLUS with details of this log." |
|
SNASW-4-DLUR_LOG_23 |
4-Warning |
EXCEPTION - %lu - A REQACTPU RSP has not been received. Possible hung PU problem [chars] |
A REQACTPU RSP has not been received for this PU and it appears\n\ the PU is hung.\n\ There will be no further action taken |
snasw |
"If this is an internal PU then contact support with details of\n\ this log. If this is a downstream PU then contact the supplier\n\ of the downstream node." |
|
SNASW-4-DLUR_LOG_5 |
4-Warning |
EXCEPTION - %lu - CPSVRMGR pipe session failure [chars] |
- |
snasw |
"If a pipe with backup DLUS is not initiated automatically\n\ manually restart any required PUs" |
|
SNASW-4-DLUR_LOG_8 |
4-Warning |
EXCEPTION - %lu - Inconsistent DLUS Names [chars] |
Inconsistent DLUS Names.\n\ The Host has requested the activation of a Downstream link to\n\ a PU by sending an ACTPU. The link is configured to request\n\ a different DLUS.\n\ The DLUS initiating the activation is used. |
snasw |
- |
|
SNASW-4-DLUR_LOG_9 |
4-Warning |
EXCEPTION - %lu - Protocol Error from DLUS Host: RU Size too large for SSCP Session [chars] |
Protocol Error from DLUS. Received an RU too large for SSCP\n\ Session. This is typically due to the SSCP sending too large\n\ a LOGON Screen.\n\ The Data is thrown away. |
snasw |
"If you are expecting an SSCP LOGON screen enter your LOGON\n\ command as usual.\n\ " |
|
SNASW-4-DS_LOG_10 |
4-Warning |
EXCEPTION - %lu - CP-CP sessions deactivated while broadcast Locate outstanding [chars] |
CP-CP sessions deactivated while broadcast Locate in process.\n\ Session activation may fail. |
snasw |
"This log simply flags the fact that a session failure impacted\n\ a pending broadcast Locate. Other more specific logs give\n\ reasons for the session failure and appropriate actions." |
|
SNASW-4-DS_LOG_18 |
4-Warning |
EXCEPTION - %lu - Locate search timed out [chars] |
- |
snasw |
"Verify that there are no nodes in the network with a single\n\ CP-CP session active to an adjacent node." |
|
SNASW-4-DS_LOG_2 |
4-Warning |
EXCEPTION - %lu - Locate search failed: search error [chars] |
- |
snasw |
"Retry the session activation. If the problem persists\n\ contact support with details of the problem." |
|
SNASW-4-DS_LOG_22 |
4-Warning |
EXCEPTION - %lu - Served end node attempted to delete a non-existant directory entry [chars] |
A served end node attempted to delete a directory entry that\n\ does not exist. This is normally caused by a network race\n\ condition causing the Delete request to arrive when the\n\ resource has not been registered.\n\ The Delete request is rejected with the specified sense code. |
snasw |
"None." |
|
SNASW-4-DS_LOG_34 |
4-Warning |
EXCEPTION - %lu - Delete request failed because the resource was not found or not removable [chars] |
A Delete request failed either because the entry was defined\n\ as a home entry at the network node server or because the\n\ resource was not found. Neither error is severe and will\n\ not affect future registration and deletion or other aspects\n\ of network operation.\n\ Delete attempt has failed further deletion and registration\n\ will continue unaffected. |
snasw |
"None." |
|
SNASW-4-DS_LOG_35 |
4-Warning |
EXCEPTION - %lu - Register GDS variable received with an invalid resource name [chars] |
Invalid resource name in received register request.\n\ Register request will fail. |
snasw |
"Contact support with details of the problem." |
|
SNASW-4-DS_LOG_36 |
4-Warning |
EXCEPTION - %lu - Central Resource Registration failure [chars] |
Central Resource Registration failure.\n\ Network performance may degrade because of additional broadcast\n\ Locate searches. |
snasw |
"None." |
|
SNASW-4-DS_LOG_37 |
4-Warning |
EXCEPTION - %lu - Central Resource Registration failure: invalid correlator received [chars] |
Central Resource Registration failure and invalid correlator\n\ received.\n\ Network performance may degrade because of additional broadcast\n\ Locate searches. |
snasw |
"None." |
|
SNASW-4-DS_LOG_44 |
4-Warning |
EXCEPTION - %lu - CP-CP sessions established with end node: invalid directory entry removed [chars] |
CP-CP sessions have been established with an adjacent end node\n\ which was previously defined using snasw location.\n\ The invalid directory definitions for the end node and any of\n\ its LUs will be removed. |
snasw |
"Do not configure the invalid entries in future." |
|
SNASW-4-DS_LOG_5 |
4-Warning |
EXCEPTION - %lu - Received Locate with no Find GDS variable [chars] |
Received Locate with no Find GDS variable.\n\ None the Locate is discarded. |
snasw |
"None." |
|
SNASW-4-DS2_LOG_0 |
4-Warning |
EXCEPTION - %lu - Insufficient resources to unregister adjacent LEN [chars] |
- |
snasw |
"Ensure sufficient resources are available to SNA Switch and then\n\ re-cycle the link to the required state." |
|
SNASW-4-DS2_LOG_2 |
4-Warning |
EXCEPTION - %lu - Failed to register resource with NNS/CDS [chars] |
Failed to allocate memory for storage of resource in the\n\ register list.\n\ Registration will not take place immediately. |
snasw |
"None." |
|
SNASW-4-DS2_LOG_3 |
4-Warning |
EXCEPTION - %lu - Received a Locate reply with an invalid RSCV [chars] |
A locate reply was received that contained an invalid RSCV.\n\ The locate request that solicited the reply may be failed. |
snasw |
"Contact support with details of the problem." |
|
SNASW-4-DS2_LOG_4 |
4-Warning |
EXCEPTION - %lu - Insufficient resources to register adjacent LEN LU [chars] |
Branch Network node has insufficient resources to register\n\ an adjacent LEN node's LU\n\ The directory of this node and/or that of its NNS may become\n\ inconsistent in that the LEN LU will not be registered when\n\ it should be. Thus session activation to the LEN LU may fail\n\ when a link to it is active |
snasw |
"Ensure sufficient resources are available to SNA Switch and then\n\ re-cycle the link to the required state." |
|
SNASW-4-DS2_LOG_6 |
4-Warning |
EXCEPTION - %lu - Duplicate FQPCID prevents start of network search [chars] |
A LOCATE message received with duplicate PCID. This could\n\ occur if two LEN nodes send BINDs to SNA Switch at the same\n\ time and with the same PCID. Session activation will fail\n\ with the specified sense code. |
snasw |
"None. The downstream box should retry the session activation\n\ using a different PCID." |
|
SNASW-4-DS2_LOG_7 |
4-Warning |
EXCEPTION - %lu - Adjacent node registered an Associated Resource which was not an ENCP [chars] |
The local node is a Branch Network Node or Network Node and a\n\ downstream node registered an Associated Resource that was not\n\ an ENCP resource. |
snasw |
"None the node will force the resource type to be ENCP." |
|
SNASW-4-HPR_LOG_0 |
4-Warning |
EXCEPTION - %lu - HPR Route Setup RU received with format errors [chars] |
An HPR Route Setup RU has been received with format errors\n\ The message cannot be processed and will be discarded. |
snasw |
"Report error to remote end." |
|
SNASW-4-HPR_LOG_1 |
4-Warning |
EXCEPTION - %lu - Unable to correlate HPR Route Setup RU [chars] |
Unable to correlate HPR Route Setup Reply\n\ The message cannot be processed and will be discarded. |
snasw |
"Report error to remote end." |
|
SNASW-4-HPR_LOG_10 |
4-Warning |
EXCEPTION - %lu - Local node has received a HPR Route Setup RU that it cannot forward because the next hop is not HPR-capable so is acting as the new destination [chars] |
- |
snasw |
"None." |
|
SNASW-4-HPR_LOG_11 |
4-Warning |
EXCEPTION - %lu - The local node is acting as the new destination for a backed-out Route Setup [chars] |
- |
snasw |
"None." |
|
SNASW-4-HPR_LOG_12 |
4-Warning |
EXCEPTION - %lu - A Route Setup has been backed out from the orignal destination to the new destination [chars] |
- |
snasw |
"None." |
|
SNASW-4-HPR_LOG_13 |
4-Warning |
EXCEPTION - %lu - A Route Setup Reply has been received with the backout sense code HPR will not be used for this session [chars] |
The local node has received an HPR Route Setup Reply with\n\ the backout sense code. The Route Setup has failed because the\n\ destination node does not support RTP. No intermediate node\n\ supports RTP and was able to become the new destination.\n\ The Route Setup has failed and HPR will not be used for the\n\ session that is being activated.\n\ This is a normal event when a node in the route has an\n\ auto-activateable link to a node that does not support RTP or\n\ HPR. |
snasw |
"None." |
|
SNASW-4-HPR_LOG_14 |
4-Warning |
EXCEPTION - %lu - Local node is the destination of a HPR Route Setup RU but does not support RTP so is replying with the backout sense code [chars] |
- |
snasw |
"None." |
|
SNASW-4-HPR_LOG_15 |
4-Warning |
EXCEPTION - %lu - Remote NCE has restarted so disconnect this RTP connection with previous instance of that NCE [chars] |
A connection setup NLP has been received from a remote NCE\n\ which has shut down and restarted. An RTP connection still\n\ exists from that NCE before it shut down.\n\ The old RTP connection will be disconnected |
snasw |
"None." |
|
SNASW-4-HPR_LOG_16 |
4-Warning |
EXCEPTION - %lu - Unable to activate Route Setup RTP connection [chars] |
Unable to activate a Route Setup RTP Connection during\n\ processing of a Route Setup request.\n\ The Route Setup request will fail with the sense code shown.\n\ The next Route Setup request will trigger another attempt\n\ to activate the Route Setup RTP Connection. |
snasw |
- |
|
SNASW-4-HPR_LOG_17 |
4-Warning |
EXCEPTION - %lu - Connection Setup NLP rejected because it specified unsupported Topic ID [chars] |
A Connection Setup NLP was rejected because it specified the\n\ CP-CP session or Route Setup Topic ID but was received on a TG\n\ which does not support the Control Flows over RTP Tower.\n\ The CP-CP session or Route Setup RTP Connection will fail with\n\ sense code HA0010017. |
snasw |
"Contact support with details of the problem." |
|
SNASW-4-HPR_LOG_18 |
4-Warning |
EXCEPTION - %lu - HPR Route Setup RU received with existing FQPCID [chars] |
An HPR Route Setup RU has been received with an FQPCID that\n\ matches an existing route.\n\ The message will be rejected and the route not established. |
snasw |
"Report error to remote end." |
|
SNASW-4-HPR_LOG_3 |
4-Warning |
EXCEPTION - %lu - Link failure caused HPR route setup request to be dropped [chars] |
Link failure between this node and source of Route Setup req\n\ The route setup request is dropped by this node.\n\ The partner node on that link should generate -ve reply. |
snasw |
"Investigate link failure." |
|
SNASW-4-HPR_LOG_4 |
4-Warning |
EXCEPTION - %lu - HPR manager failed to obtain memory to send indication [chars] |
HPR manager failed to get memory to send an RTP\n\ indication.\n\ The data_lost flag will be set in the next indication\n\ successfully sent. |
snasw |
"Investigate memory shortage." |
|
SNASW-4-HPR_LOG_5 |
4-Warning |
EXCEPTION - %lu - NLP received with format errors [chars] |
An NLP has been received with format errors\n\ The message cannot be processed and will be discarded. |
snasw |
"Report error to remote end." |
|
SNASW-4-HPR_LOG_6 |
4-Warning |
EXCEPTION - %lu - NLP received for RTP connection which no longer exists [chars] |
An NLP has been received for an RTP connection which no\n\ longer exists\n\ The message cannot be processed and will be discarded. |
snasw |
"Report error to remote end." |
|
SNASW-4-HPR_LOG_8 |
4-Warning |
EXCEPTION - %lu - Connection Setup NLP received for previous NCE instance [chars] |
A connection setup NLP has been received specifying a\n\ previous instance of this NCE. The NCE must have been\n\ shut down and restarted since processing the Route Setup\n\ request\n\ No RTP connection can be started so the NLP will be discarded. |
snasw |
"Report error to remote end." |
|
SNASW-4-HPR_LOG_9 |
4-Warning |
EXCEPTION - %lu - Local node has received a HPR Route Setup RU that it cannot forward because the next hop is not HPR-capable so is replying with the backout sense code [chars] |
- |
snasw |
"None." |
|
SNASW-4-HS_LOG_0 |
4-Warning |
EXCEPTION - %lu - CRV exchange failed [chars] |
CRV exchange failed. This indicates the cryptography keys\n\ configured at this LU and the partner LU are inconsistent.\n\ Session will be deactivated with the specified sense code\n\ 08350001. |
snasw |
- |
|
SNASW-4-HS_LOG_1 |
4-Warning |
EXCEPTION - %lu - LU6.2 session state error [chars] |
LU6.2 session state error. This may indicate an\n\ interoperability problem. Sense codes are as follows.\n\ 20020000 - chaining sequence error\n\ 20030000 - bracket state error\n\ 20040000 - received normal flow request when half-duplex\n\ flip-flop state not receive\n\ 200A0000 - immediate request mode violated by partner LU\n\ 200B0000 - queued response indicator invalid\n\ 200E0000 - unexpected SIGNAL response\n\ 200F0000 - received unexpected response or received EXPD RU\n\ before previous EXPD RU has been acknowledged\n\ 20120000 - unexpected sense code on negative response\n\ 40040000 - received RQE BB CEB chain from contention loser\n\ 40110000 - RU category of response doesn't match request\n\ 40120000 - request code of response doesn't match request\n\ 40210000 - QRI setting on response doesn't match request\n\ The session will be deactivated with the specified sense code. |
snasw |
- |
|
SNASW-4-HS_LOG_3 |
4-Warning |
EXCEPTION - %lu - MU format errors [chars] |
LU6.2 session format error. This may indicate an\n\ interoperability problem. Sense codes are as follows.\n\ 080F6051 - security error FMH12 error\n\msgdef_recommended_action Use information on the session deactivated problem log |
- |
- |
|
SNASW-4-HS_LOG_4 |
4-Warning |
EXCEPTION - %lu - LU6.2 response correlation error [chars] |
LU6.2 response correlation error. This may indicate an\n\ interoperability problem. Sense codes are as follows.\n\ 200E0000 - uncorrelated positive response or\n\ uncorrelated RTR response\n\ Session will be deactivated with the specified sense code. |
snasw |
- |
|
SNASW-4-HS_LOG_5 |
4-Warning |
EXCEPTION - %lu - LU6.2 session ended abnormally - insufficient storage [chars] |
LU6.2 session ended abnormally because of insufficient storage.\n\ Session will be deactivated with the specified sense code. |
snasw |
- |
|
SNASW-4-HS_LOG_6 |
4-Warning |
EXCEPTION - %lu - Protocol error during CRV exchange [chars] |
Protocol error during CRV exchange. This indicates a possible\n\ interoperability problem. Sense codes are as follows.\n\ 20090000 - CRV request received from secondary LU or\n\ CRV response received from primary LU or\n\ CRV not received when expected\n\ 10020000 - CRV RU too short\n\ 400F0000 - CRV with FI not set\n\ 400B0000 - CRV chain indicators not set to BC EC\n\ 40140000 - CRV not RQD1\n\ 40110000 - CRV not expedited\n\ 40150000 - CRV with QRI not set\n\ 40080000 - CRV with PI set\n\ 400C0000 - CRV request with BBI EBI or CEBI set\n\ 400D0000 - CRV request with CDI set\n\ 40100000 - CRV request with CSI set to CODE1\n\ 40160000 - CRV request with EDI set\n\ 40170000 - CRV request with PDI set\n\ 40130000 - CRV response RTI and SDI inconsistent\n\ Session will be deactivated with specified sense code. |
snasw |
- |
|
SNASW-4-HS_LOG_7 |
4-Warning |
EXCEPTION - %lu - SIGNAL RU received on full-duplex conversation [chars] |
An incoming SIGNAL RU has been received on a full-duplex\n\ conversation.\n\ The session will be deactivated with the specified sense code.\n\ 10030004 |
snasw |
"Contact support with details of the problem." |
|
SNASW-4-HS_LOG_9 |
4-Warning |
EXCEPTION - %lu - Insufficient storage to initialise half session [chars] |
Insufficient storage to initialise the half session.\n\ The half session will fail to activate with the specified sense\n\ code. |
snasw |
- |
|
SNASW-4-LDLC_CTRL_LOG_0 |
4-Warning |
EXCEPTION - %lu - Unable to create a new LDLC_CTRL instance [chars] |
Unable to create a new LDLC_CTRL instance.\n\ Link activation cannot continue. This will result in the\n\ failure of an outbound link activation attempt or the rejection\n\ of an inbound link activation. |
snasw |
"Check surrounding logs for evidence of buffer congestion. If\n\ buffer congestion is causing this failure either decrease the\n\ system load or make more resources available to LDLC." |
|
SNASW-4-LDLC_CTRL_LOG_1 |
4-Warning |
EXCEPTION - %lu - LDLC command frame retry limit exceeded [chars] |
LDLC command frame retry limit exceeded.\n\ Link activation will fail or an active link will be brought\n\ down. |
snasw |
"Check connectivity to remote address" |
|
SNASW-4-LDLC_CTRL_LOG_2 |
4-Warning |
EXCEPTION - %lu - LDLC link reported inoperative by underlying media [chars] |
LDLC link reported inoperative by underlying media.\n\ Link activation will fail or an active link will be brought\n\ down. |
snasw |
"Check for faults at the supplied destination address. Check\n\ for faults and error conditions in the underlying drivers and\n\ media. Check for connectivity in the underlying media. Check\n\ for outages on the connection path. Check all your wires are\n\ still plugged in." |
|
SNASW-4-LDLC_DATA_LOG_0 |
4-Warning |
EXCEPTION - %lu - Unrecognised NHDR routing instruction [chars] |
Unrecognised NHDR routing instruction.\n\ This packet cannot be routed by LDLC and will be discarded.\n\ Data may be lost. This may indicate an interoperability\n\ problem. |
snasw |
"Check surrounding logs for other evidence of interoperability\n\ problems. If failures or problems occur gather trace of the\n\ protocol flows then report this problem to support." |
|
SNASW-4-LDLC_DATA_LOG_1 |
4-Warning |
EXCEPTION - %lu - Unrecognised LDLC RU identifier [chars] |
Unrecognised LDLC RU identifier.\n\ This packet cannot be processed by LDLC and will be discarded.\n\ Link activation may fail. Link deactivation may fail. Data\n\ may be lost. This may indicate an interoperability problem. |
snasw |
"Check surrounding logs for other evidence of interoperability\n\ problems. If failures or problems occur gather trace of the\n\ protocol flows then report this problem to support." |
|
SNASW-4-LDLC_DATA_LOG_2 |
4-Warning |
EXCEPTION - %lu - Unable to grant credit [chars] |
Unable to grant credit\n\ LDLC is unable to grant further send credit. |
snasw |
"Check surrounding logs for evidence of buffer congestion. If\n\ buffer congestion is causing this failure either decrease the\n\ system load or make more resources available to LDLC." |
|
SNASW-4-LDLC_IP_LOG_0 |
4-Warning |
EXCEPTION - %lu - IPDLC failed to allocate necessary storage [chars] |
IPDLC could not allocate necessary storage.\n\ Some operation may fail. See other logs. |
snasw |
- |
|
SNASW-4-LDLC_IP_LOG_1 |
4-Warning |
EXCEPTION - %lu - IPDLC failed to request a posting [chars] |
IPDLC failed to request a posting.\n\ Link activation may fail or data transmission may be delayed. |
snasw |
- |
|
SNASW-4-LDLC_IP_LOG_10 |
4-Warning |
EXCEPTION - %lu - Unable to activate IPDLC port [chars] |
Unable to activate an IPDLC port.\n\ This will result in the failure of a port activation attempt.\n\ No further IPDLC operation will be possible until a port is\n\ activated successfully. |
snasw |
" - Check surrounding logs for evidence of buffer congestion.\n\ If buffer congestion is causing this failure either\n\ decrease system load or make more resources available to\n\ IPDLC.\n\ - Ensure that the necessary facilities are available for the\n\ UDP interface to operate correctly.\n\ - Check that valid DLC specific configuration data was\n\ provided to IPDLC at define time." |
|
SNASW-4-LDLC_IP_LOG_11 |
4-Warning |
EXCEPTION - %lu - Unable to activate IPDLC link [chars] |
Unable to activate an IPDLC link.\n\ Link activation cannot continue. This will result in the\n\ failure of an outbound link activation attempt or the\n\ rejection of an inbound link activation. |
snasw |
" - Check surrounding logs for evidence of buffer congestion.\n\ If buffer congestion is causing this failure either\n\ decrease system load or make more resources available to\n\ IPDLC.\n\ - Ensure that the necessary facilities are available for the\n\ UDP interface to operate correctly.\n\ - Check that valid DLC specific configuration data was\n\ provided to SNAP-IPDLC at define time." |
|
SNASW-4-LDLC_IP_LOG_2 |
4-Warning |
EXCEPTION - %lu - IPDLC failed to grow a link hash table [chars] |
IPDLC failed to grow a link hash table.\n\ Data transmission rates may be marginally degraded. |
snasw |
- |
|
SNASW-4-LDLC_IP_LOG_3 |
4-Warning |
EXCEPTION - %lu - IPDLC failed to create a UDP stub [chars] |
IPDLC failed to create a UDP stub.\n\ Port activation will fail. |
snasw |
- |
|
SNASW-4-LDLC_IP_LOG_4 |
4-Warning |
EXCEPTION - %lu - IPDLC's UDP stub has failed to initialise [chars] |
IPDLC has created a UDP stub but the UDP stub failed to\n\ initialise successfully.\n\ Port activation will fail. |
snasw |
" Check surrounding logs and other diagnostics for reports of a\n\ failure from a UDP stub process." |
|
SNASW-4-LM_LOG_18 |
4-Warning |
EXCEPTION - %lu - An LU-SSCP session activation attempt failed because the SSCP was not suitable [chars] |
An ACTLU was received for an LU from the wrong SSCP.\n\ The ACTLU is rejected with sense code 084B0000 i.e. the LU\n\ activation attempt fails. |
snasw |
- |
|
SNASW-4-LM_LOG_6 |
4-Warning |
EXCEPTION - %lu - Insufficient storage to send RTM statistics to host [chars] |
Insufficient storage to send RTM statistics to host.\n\ RTM statistics displayed by host will be inconsistent. |
snasw |
- |
|
SNASW-4-LM_LOG_7 |
4-Warning |
EXCEPTION - %lu - Insufficient storage to report RTM status to application [chars] |
Insufficient storage to report RTM status to application.\n\ RTM statistics reported and displayed by application may be\n\ inconsistent. |
snasw |
- |
|
SNASW-4-LM2_LOG_0 |
4-Warning |
EXCEPTION - %lu - CRV exchange failed on a PLU-SLU session. The session will fail. [chars] |
CRV exchange failed. This indicates the cryptography keys\n\ configured at this LU and the partner LU are inconsistent.\n\ Session will be deactivated with the specified sense code\n\ 08350001. |
snasw |
"Correct the mismatch in cryptography keys." |
|
SNASW-4-LM2_LOG_1 |
4-Warning |
EXCEPTION - %lu - A conventional half-session has aborted. [chars] |
Critical buffer shortage or protocol error or CRV exchange\n\ protocol error. This indicates a possible interoperability\n\ problem. Sense codes for CRV exchange errors are as follows.\n\\n\ 20090000 - CRV request received from secondary LU or\n\ CRV response received from primary LU or\n\ CRV not received when expected\n\ 10020000 - CRV RU too short\n\ 400F0000 - CRV with FI not set\n\ 400B0000 - CRV chain indicators not set to BC EC\n\ 40140000 - CRV not RQD1\n\ 40110000 - CRV not expedited\n\ 40150000 - CRV with QRI not set\n\ 40080000 - CRV with PI set\n\ 400C0000 - CRV request with BBI EBI or CEBI set\n\ 400D0000 - CRV request with CDI set\n\ 40100000 - CRV request with CSI set to CODE1\n\ 40160000 - CRV request with EDI set\n\ 40170000 - CRV request with PDI set\n\ 40130000 - CRV response RTI and SDI inconsistent\n\\n\ Session will be deactivated with specified sense code. |
snasw |
"If surrounding logs indicate critical congestion decrease the\n\ system load or make more resources available to SNA Switch.\n\ Otherwise contact support with details of the problem." |
|
SNASW-4-MS_LOG_10 |
4-Warning |
EXCEPTION - %lu - Alert/Resolution received and cannot be sent [chars] |
Memory failure in trying to allocate space to route a back-\n\ level alert or resolution to the parent MS process.\n\ The alert or resolution will not be sent. It is logged here. |
snasw |
- |
|
SNASW-4-MS_LOG_12 |
4-Warning |
EXCEPTION - %lu - Memory shortage in verb processing [chars] |
The system was unable to allocate control block space to\n\ process an incoming verb.\n\ The verb will not be processed and it will be returned to\n\ the sending application with a primary return code of\n\ NAP_UNEXPECTED_SYSTEM_ERROR. |
snasw |
- |
|
SNASW-4-MS_LOG_13 |
4-Warning |
EXCEPTION - %lu - Memory shortage in trying to send an alert [chars] |
The system was unable to allocate memory needed to send an\n\ alert.\n\ The alert will not be sent however the sense code of the\n\ alert will be logged. |
snasw |
- |
|
SNASW-4-MS_LOG_14 |
4-Warning |
EXCEPTION - %lu - Memory shortage in MDS_MU processing [chars] |
The system was unable to needed memory for processing an\n\ MDS_MU.\n\ The MDS_MU will not be processed. If the MDS_MU originated at\n\ the local node the SEND_MDS_MU verb containing the MDS_MU will\n\ be returned to the sending application noting the error. If the\n\ MDS_MU did not originate from the local node an error message\n\ will be returned to the originating application. |
snasw |
- |
|
SNASW-4-MS_LOG_15 |
4-Warning |
EXCEPTION - %lu - Correlator clash detected in MDS_MU processing [chars] |
A correlation error was detected while processing an MDS_MU.\n\ The MDS_MU will not be processed. If the MDS_MU originated at\n\ the local node the SEND_MDS_MU verb containing the MDS_MU will\n\ be returned to the sending application noting the error. If the\n\ MDS_MU did not originate from the local node an error message\n\ will be returned to the originating application. An error\n\ message may also be sent to other applications if they are\n\ affected by the correlation clash. |
snasw |
"User should reissue the SEND_MDS_MU but with a correct\n\ correlator value." |
|
SNASW-4-MS_LOG_16 |
4-Warning |
EXCEPTION - %lu - Insufficient storage to pass Alert data to registered Alert handler [chars] |
Insufficient storage to pass Alert to registered Alert Handler.\n\ The alert will not be sent however it will be logged. |
snasw |
- |
|
SNASW-4-MS_LOG_17 |
4-Warning |
EXCEPTION - %lu - Following alert failed to be sent to focal point [chars] |
The system received a send failure for an alert stored on the\n\ send alert queue. No held alert function is available to\n\ store the alert until another focal point is established.\n\ alert to the alert handler.\n\ The alert will not be sent however it will be logged. |
snasw |
"None." |
|
SNASW-4-MS_LOG_18 |
4-Warning |
EXCEPTION - %lu - Error on alert send not correlated with entries on send alert queue [chars] |
The system was unable to correlate an error received on an\n\ alert send with the alerts stored in the send alert queue.\n\ The send alert queue is either too small and the original alert\n\ has been deleted or a previous error prevented the alert from\n\ being held on the queue.\n\ The alert will not be sent to the focal point. |
snasw |
"Investigate whether prior memory shortage caused alert\n\ not to be held on the queue." |
|
SNASW-4-MS_LOG_23 |
4-Warning |
EXCEPTION - %lu - MS Capabilities unable to send request due to memory shortage [chars] |
MS Capabilities failed to get space to send a message.\n\ The message will not be sent. If the intended message was\n\ a request for focal point services MS will pursue focal point\n\ services alternatively. If the intended message was to revoke\n\ a previous focal point the message will not be sent. The node\n\ will still appear in the focal point's sphere of control list. |
snasw |
- |
|
SNASW-4-MS_LOG_24 |
4-Warning |
EXCEPTION - %lu - Error message received at MS Capabilities delivery failure [chars] |
MS Capabilities received an error message. This is assumed\n\ to be the result of a send failure.\n\ The error message received will be logged so that send failure\n\ types can be examined. MS capabilities will take appropriate\n\ recovery action if the failed send effects the focal point\n\ table. |
snasw |
"Contact support with details of the problem." |
|
SNASW-4-MS_LOG_27 |
4-Warning |
EXCEPTION - %lu - Memory Failure in MDS creation sequence [chars] |
MDS failed to get needed memory during the creation sequence.\n\ The MDS creation will fail. |
snasw |
- |
|
SNASW-4-MS_LOG_28 |
4-Warning |
EXCEPTION - %lu - Insufficient storage to process received MS Capabilities information [chars] |
Insufficient storage to processed received MS Capabilities\n\ information.\n\ The category for which this failure occurred will be reset. |
snasw |
- |
|
SNASW-4-MS_LOG_29 |
4-Warning |
EXCEPTION - %lu - Parsing error found in MDS_MU header [chars] |
MDS received an MDS_MU that it could not parse correctly.\n\ An alert will be raised. If the MDS_MU originated from a\n\ local application the SEND_MDS_MU will be returned with\n\ the return codes NAP_PARAMETER_CHECK and\n\ NAP_INVALID_MDS_MU_FORMAT. |
snasw |
"Investigate syntax of MDS_MU sent correct syntax and reissue\n\ the SEND_MDS_MU." |
|
SNASW-4-MS_LOG_3 |
4-Warning |
EXCEPTION - %lu - Insufficient storage to deliver MDS_MU to a registered application [chars] |
Insufficient storage to deliver MDS_MU to a registered\n\ application.\n\ The MU will be returned to the sender indicating a resource\n\ shortage error. |
snasw |
- |
|
SNASW-4-MS_LOG_31 |
4-Warning |
EXCEPTION - %lu - Insufficient storage to queue Alert/Resolution for error correlation [chars] |
Insufficient storage to queue alert or resolution for error\n\ correlation\n\ The alert or resolution will not be queued and thus if an\n\ error message regarding the failure to send this alert or\n\ resolution is received MDS will be unable to correlate it. If\n\ the alert or resolution is sent successfully no further\n\ problems will result. |
snasw |
- |
|
SNASW-4-MS_LOG_32 |
4-Warning |
EXCEPTION - %lu - MDS unable to get memory to send TP_ENDED [chars] |
MDS unable to get buffer to send TP_ENDED for SEND_TP.\n\ TP_ENDED will not be sent. |
snasw |
- |
|
SNASW-4-MS_LOG_33 |
4-Warning |
EXCEPTION - %lu - MDS unable to get memory for SNASVCMG session list entry [chars] |
MDS unable to get memory for a SNASVCMG session control block.\n\ The control block will not be obtained. |
snasw |
- |
|
SNASW-4-MS_LOG_34 |
4-Warning |
EXCEPTION - %lu - Unexpected what_received in MDS Transaction Program [chars] |
An MDS Transaction Program received an unexpected what_received.\n\ The transaction program will re-initialize. The MDS_MU that was\n\ being sent will be returned to the originator if the error\n\ was detected at the originating node or the originator will\n\ be notified of the send failure via an error message. |
snasw |
"Investigate cause of unexpected what_received." |
|
SNASW-4-MS_LOG_36 |
4-Warning |
EXCEPTION - %lu - Following locally originated MSCAPS message failed to be sent [chars] |
The system received a send failure for a local MS capabilities\n\ originated message.\n\ MS capabilities will treat the send failure as a loss of\n\ connectivity to the partner node. If focal point relationships\n\ are affected then MS capabilities will take appropriate\n\ recovery action. |
snasw |
"Investigate cause of failed send." |
|
SNASW-4-MS_LOG_37 |
4-Warning |
EXCEPTION - %lu - MS unable to allocate space for link control block [chars] |
The system was unable to allocate resource to set up a\n\ link control block for a received PU_STATUS message.\n\ The active link will be treated as unknown by MS. Any messages\n\ received over the link will be returned as undeliverable.\n\ Any TRANSFER_MS_DATA or SEND_MDS_MUs received from applications\n\ specifying the link in the PU_STATUS will be returned with\n\ link_name unknown. |
snasw |
- |
|
SNASW-4-MS_LOG_5 |
4-Warning |
EXCEPTION - %lu - Memory shortage in processing signal [chars] |
The system was unable to allocate memory to process an incoming\n\ TRANSFER_MS_DATA or SEND_MDS_MU or register signal.\n\ The signal will be returned to the sender noting the resource\n\ shortage error. |
snasw |
- |
|
SNASW-4-MS_LOG_6 |
4-Warning |
EXCEPTION - %lu - MS unable to add time stamp and/or product set id [chars] |
The system was unable to add the product set id or the date\n\ time stamp requested due to either memory shortage or the\n\ addition causing an NMVT to exceed maximum size.\n\ Additions will not be made to the signal. |
snasw |
- |
|
SNASW-4-MS_LOG_8 |
4-Warning |
EXCEPTION - %lu - Memory shortage preventing data log [chars] |
The system was unable to allocate memory and was thus unable\n\ to log data supplied by the user.\n\ The data will not be logged. |
snasw |
- |
|
SNASW-4-MS_LOG_9 |
4-Warning |
EXCEPTION - %lu - Unrecognized signal received from application [chars] |
A signal was received which was unrecognized and could not\n\ be returned to the sender.\n\ The signal memory will be freed. |
snasw |
"Check that issued signals are acceptable according to the\n\ API specification." |
|
SNASW-4-NOF_LOG_15 |
4-Warning |
EXCEPTION - %lu - An LU-SSCP session activation attempt failed because the SSCP was not suitable [chars] |
An ACTLU was received for an LU from the wrong SSCP.\n\ The ACTLU is rejected with sense code 084B0000 i.e. the LU\n\ activation attempt fails. |
snasw |
- |
|
SNASW-4-PC_LOG_0 |
4-Warning |
EXCEPTION - %lu - Unable to route intra-node session data [chars] |
Unable to route intra-node session data. This usually\n\ indicates a race condition when an intra-node session is\n\ deactivating.\n\ None. |
snasw |
"None." |
|
SNASW-4-PC_LOG_14 |
4-Warning |
EXCEPTION - %lu - Received a frame with a badly formed transmission header or a frame that is too small to be a valid SNA frame [chars] |
Received a frame with a badly formed transmission header or a\n\ frame that is too small to be a valid SNA frame.\n\ The invalid frame will be discarded. An alert is generated. |
snasw |
"None." |
|
SNASW-4-PC_LOG_15 |
4-Warning |
EXCEPTION - %lu - Unable to correlate DLC credit for MLTG link [chars] |
Unable to correlate DLC credit for MLTG link.\n\ Probably none. This exception will occur during a window\n\ condition in normal link deactivation. |
snasw |
"If several instances of this log appear and also poor RTP\n\ connection performance is observed investigate further by\n\ querying link stations which are members of MLTGs.\n\ Unexpectedly low quantities of data sent over a link may\n\ indicate problems with DLC credit. Contact support with\n\ details of the problem including trace of signals sent to and\n\ from the DLCs underlying the affected links." |
|
SNASW-4-PC_LOG_16 |
4-Warning |
EXCEPTION - %lu - Link failure because too many outgoing packets are queued for transmission [chars] |
A remote node is not processing information fast enough and is\n\ causing large queues to form on this node.\n\ Link failure. |
snasw |
"Check the error logs on the remote node that this link is\n\ connected to." |
|
SNASW-4-PC_LOG_17 |
4-Warning |
EXCEPTION - %lu - Link failure because too many outgoing packets are queued for transmission [chars] |
A remote node is not processing information fast enough and is\n\ causing large queues to form on this node.\n\ Link failure. |
snasw |
"Check the error logs on the remote nodes that this MLTG is\n\ connected to." |
|
SNASW-4-PC_LOG_4 |
4-Warning |
EXCEPTION - %lu - Insufficient storage to generate Alert [chars] |
Insufficient storage to generate Alert to report invalid\n\ received data.\n\ Alert is not generated. |
snasw |
- |
|
SNASW-4-PC_LOG_5 |
4-Warning |
EXCEPTION - %lu - Unable to route inter-node session data [chars] |
Unable to route inter-node session data. This usually\n\ indicates a race condition when an inter-node session is\n\ deactivating.\n\ None. |
snasw |
"None." |
|
SNASW-4-PC_LOG_9 |
4-Warning |
EXCEPTION - %lu - Unable to forward an HPR NLP - unknown ANR label [chars] |
- |
snasw |
"Use show snasw link to look for an active HPR-capable link with the\n\ specified ANR label. If there is one then the problem has\n\ been caused by a storage shortage. Either decrease the system\n\ load for example by reducing the number of active sessions\n\ or make more storage available to SNA Switch." |
|
SNASW-4-PS_LOG_11 |
4-Warning |
EXCEPTION - %lu - Entry could not be added to signed-on-to list sending PV sign-on Attach. [chars] |
The local LU failed to add an entry into the signed-on-to list\n\ when sending a PV sign-on Attach FMH-5 due to resource\n\msgdef_recommended_action Either decrease the system load |
- |
- |
|
SNASW-4-PS_LOG_12 |
4-Warning |
EXCEPTION - %lu - Unable to process Sign-Off verb due to resource shortage. [chars] |
The local LU was unable to process a Sign-Off verb issued by a\n\ local TP due to resorce shortage.\n\ The Sign-Off request will fail and any entries in the\n\ signed-on-to and sign-on-from lists will remain valid. |
snasw |
- |
|
SNASW-4-PS_LOG_13 |
4-Warning |
EXCEPTION - %lu - SNA Switch detected a mapped conversation protocol error on an APPC mapped conversation [chars] |
SNA Switch detected a mapped conversation protocol error on an\n\ APPC mapped conversation.\n\ The conversation will be terminated either by an APPC\n\ primary_rc of NAP_CONV_FAILURE_NO_RETRY or a CPI-C return_code\n\ of CM_RESOURCE_FAILURE_NO_RETRY. The partner TP will fail the\n\ conversation with an APPC primary_rc of NAP_DEALLOCATE_ABEND or\n\ a CPI-C return_code of CM_DEALLOCATE_ABEND. The session will\n\ not be deactivated. |
snasw |
"Report the protocol error to partner LU support. If additional\n\ diagnostic information is required run a link trace the\n\ session identifier can be used to correlate this log to other\n\ logs which contain the appropriate link station name." |
|
SNASW-4-PS_LOG_14 |
4-Warning |
EXCEPTION - %lu - SNA Switch detected a mapped conversation protocol error on an APPC mapped conversation [chars] |
SNA Switch received an error data GDS variable on an APPC mapped\n\ conversation.\n\ The conversation will be terminated either by an APPC\n\ primary_rc of NAP_CONV_FAILURE_NO_RETRY or a CPI-C return_code\n\ of CM_RESOURCE_FAILURE_NO_RETRY. The partner TP will fail the\n\ conversation with an APPC primary_rc of NAP_DEALLOCATE_ABEND or\n\ a CPI-C return_code of CM_DEALLOCATE_ABEND. The session will\n\ not be deactivated. |
snasw |
"Report the protocol error to partner LU support. If additional\n\ diagnostic information is required run a link trace the\n\ session identifier can be used to correlate this log to other\n\ logs which contain the appropriate link station name." |
|
SNASW-4-PS_LOG_15 |
4-Warning |
EXCEPTION - %lu - An LU received an aping with data size greater than the maximum allowed [chars] |
An LU received an aping with data length greater than the\n\ maximum allowed.\n\ The conversation will be terminated with primary_rc of\n\ DEALLOC_ABEND. |
snasw |
"Report the error. SNA Switch LUs should not be apinged with a\n\ data size greater than the defined maximum." |
|
SNASW-4-PS_LOG_5 |
4-Warning |
EXCEPTION - %lu - Protocol error detected on conversation [chars] |
- |
snasw |
"Report the protocol error to partner LU support. If additional\n\ diagnostic information is required run a link trace the\n\ session identifier can be used to correlate this log to other\n\ logs which contain the appropriate link station name." |
|
SNASW-4-PS_LOG_7 |
4-Warning |
EXCEPTION - %lu - Error data received from partner LU. [chars] |
The partner TP issued a SEND_ERROR or DEALLOCATE verb\n\ specifying error data.\n\ an error state was generated by the partner TP.\n\ The specified TP will experience a problem. Subsequent\n\ recovery or termination of the conversation will be determined\n\ by the applications. |
snasw |
"Check that both the local TP and the partner TP exist are\n\ correctly named and are working properly." |
|
SNASW-4-PS_LOG_8 |
4-Warning |
EXCEPTION - %lu - Error data sent to partner LU. [chars] |
The local TP issued a SEND_ERROR or DEALLOCATE verb specifying\n\ error data.\n\ The specified TP will experience a problem. Subsequent\n\ recovery or termination of the conversation will be determined\n\ by the applications. |
snasw |
"Check that both the local TP and the partner TP exist are\n\ correctly named and are working properly." |
|
SNASW-4-PU_LOG_2 |
4-Warning |
EXCEPTION - %lu - Insufficient storage to send RTM statistics to host [chars] |
Insufficient storage to send RTM statistics to host.\n\ RTM statistics displayed by host will be inconsistent. |
snasw |
- |
|
SNASW-4-RM_LOG_13 |
4-Warning |
EXCEPTION - %lu - APPC Transaction Program or CPI-C application has ended abnormally with active conversations [chars] |
An APPC transaction program or CPI-C application has ended\n\ abnormally with active conversations. This usually indicates\n\ an error in the application.\n\ SNA Switch will deactivate all sessions currently being used by\n\ the application. |
snasw |
"Run a trace on the APPC API or the CPI-C API to see the\n\ sequence of verbs causing the problem." |
|
SNASW-4-RM_LOG_23 |
4-Warning |
EXCEPTION - %lu - Insufficient storage to deactivate limited resource session [chars] |
Insufficient storage to deactivate limited resource session.\n\ The limited resource session will not be deactivated although\n\ it may be deactivated later. This could result in limited\n\msgdef_recommended_action Either decrease the system load |
- |
- |
|
SNASW-4-RTP_LOG_10 |
4-Warning |
EXCEPTION - %lu - LFSID in use moving on to next one. [chars] |
An LFSID was found to be in use so SNA Switch is using a different one. |
snasw |
"If this log appears frequently inform your support contact." |
|
SNASW-4-RTP_LOG_2 |
4-Warning |
EXCEPTION - %lu - RTP Connection has disconnected [chars] |
The RTP Connection has disconnected due to an error\n\ Sessions using the connection will fail |
snasw |
"Investigate the cause of the error" |
|
SNASW-4-RTP_LOG_3 |
4-Warning |
EXCEPTION - %lu - Remote end of RTP Connection has disconnected [chars] |
The RTP Connection has disconnected due to an error\n\ Sessions using the connection will fail |
snasw |
"Investigate the cause of the error" |
|
SNASW-4-RTP_LOG_4 |
4-Warning |
EXCEPTION - %lu - RTP connection has timed-out [chars] |
he RTP Connection has timed out\n\ The node will attempt to path-switch |
snasw |
"Investigate the cause of the error" |
|
SNASW-4-RTP_LOG_5 |
4-Warning |
EXCEPTION - %lu - RTP connection dropped due to local link failure [chars] |
- |
snasw |
"Investigate the cause of the link failure" |
|
SNASW-4-RTP_LOG_7 |
4-Warning |
EXCEPTION - %lu - Path-switch failure [chars] |
RTP connection has failed to path-switch\n\ The RTP connection will be disconnected |
snasw |
"Investigate the cause of the error" |
|
SNASW-4-RTP_LOG_8 |
4-Warning |
EXCEPTION - %lu - Segmented NLP received on Route Setup RTP connection [chars] |
A Route Setup RTP Connection RTP process received a segmented\n\ NLP. This is an error because all NLPs received should contain\n\ Route Setup GDS data which should never be segmented.\n\ The NLP will be dropped. |
snasw |
"Contact support with details of the problem." |
|
SNASW-4-RTP_LOG_9 |
4-Warning |
EXCEPTION - %lu - RTP connection has timed-out [chars] |
A Route Setup RTP Connection has timed out waiting for status\n\ from the adjacent node.\n\ The RTP Connection will be failed. |
snasw |
"Investigate the cause of the error at the adjacent node." |
|
SNASW-4-RTP2_LOG_0 |
4-Warning |
EXCEPTION - %lu - RTP Connection is path-switching to a much longer path [chars] |
An RTP connection is path-switching to a much longer path than\n\ it started with. Much more room is needed in each packet for\n\ routing information than was originally planned.\n\ Performance across this RTP connection may degrade since some\n\ packets may have to be segmented. |
snasw |
"If performance degradation is noticed reactivate failed links\n\ then issue the 'PATH_SWITCH' verb." |
|
SNASW-4-RTP2_LOG_1 |
4-Warning |
EXCEPTION - %lu - Invalid ARB support received from remote node [chars] |
A value for ARB support that the local node does not support\n\ has been received in an ARB setup segment. The remote node\n\ has not completed the ARB negotiation correctly. This\n\ is a protocol error.\n\ The connection will be deactivated. |
snasw |
"Investigate the cause of the error at the adjacent node." |
|
SNASW-4-SC_LOG_1 |
4-Warning |
EXCEPTION - %lu - Protocol error detected in PIU on intermediate session [chars] |
SNA Switch detected a protocol error in an PIU received on an\n\ intermediate session. This typically indicates a problem on\n\ an adjacent node. The sense codes are as follows.\n\ 10010003 - invalid IPM format\n\ 10020000 - RU length error\n\ 10030000 - CLEAR request on secondary stage or\n\ CLEAR response on primary stage\n\ 20110000 - sender has overrun pacing window or\n\ PI not set on first RU of window\n\ 20110001 - unexpected IPM\n\ 20110002 - PI set on other than first RU in window\n\ 20110003 - invalid pacing response\n\ 80070000 - segment error\n\ The intermediate session will be deactivated. |
snasw |
"Report the problem in the adjacent node to support running a\n\ trace on the specified link if more diagnostics are required" |
|
SNASW-4-SC_LOG_2 |
4-Warning |
EXCEPTION - %lu - Deactivating intermediate session because of insufficient storage [chars] |
Deactivating intermediate session because of insufficient\n\ storage.\n\ The intermediate session will be deactivated. |
snasw |
- |
|
SNASW-4-SCM_LOG_7 |
4-Warning |
EXCEPTION - %lu - Unable to correlate BIND response received during ISR session activation [chars] |
Unable to correlate BIND response received during ISR session\n\ activation.\n\ None. This is a normal race condition caused by a BIND request\n\ being immediately followed by an UNBIND request for the same\n\ session. |
snasw |
"None." |
|
SNASW-4-SCM_LOG_8 |
4-Warning |
EXCEPTION - %lu - Unable to correlate UNBIND request received for an ISR session [chars] |
- |
snasw |
"None." |
|
SNASW-4-SM_LOG_13 |
4-Warning |
EXCEPTION - %lu - BIND race with single-session partner LU - partner LU has lost race [chars] |
BIND race with single-session partner LU. This is a normal\n\ network race condition. The race is resolved in favour of the\n\ LU with the higher name. In this case the partner LU lost the\n\ race.\n\ Session activation will fail with specified sense code. |
snasw |
"None." |
|
SNASW-4-SM_LOG_18 |
4-Warning |
EXCEPTION - %lu - Unable to correlate received BIND response [chars] |
- |
snasw |
"None." |
|
SNASW-4-SM_LOG_20 |
4-Warning |
EXCEPTION - %lu - Unable to correlate received INIT-SELF response or NOTIFY request [chars] |
- |
snasw |
"None." |
|
SNASW-4-SM_LOG_21 |
4-Warning |
EXCEPTION - %lu - Unable to correlate received UNBIND request [chars] |
- |
snasw |
"None." |
|
SNASW-4-SM_LOG_30 |
4-Warning |
EXCEPTION - %lu - Received ACTLU when LU already active [chars] |
ACTLU received when LU already active.\n\ ACTLU will be rejected with specified sense code. |
snasw |
"Run a trace on the link station corresponding to the specified\n\ PU name. Contact host support with details of the problem." |
|
SNASW-4-SM_LOG_32 |
4-Warning |
EXCEPTION - %lu - Unable to activate a new session since it would exceed the LU-mode session limit [chars] |
Unable to activate a new session since it would exceed the\n\ LU-mode session limits. This problem is a normal race\n\ condition and so should occur infrequently.\n\ Session activation will fail with specified sense code which\n\ may cause ALLOCATE MC_ALLOCATE or CMALLC requests to fail. |
snasw |
"None." |
|
SNASW-4-SM_LOG_39 |
4-Warning |
EXCEPTION - %lu - An LU-SSCP session activation attempt failed because the SSCP was not suitable [chars] |
An ACTLU was received for an LU from the wrong SSCP.\n\ The ACTLU is rejected with sense code 084B0000 i.e. the LU\n\ activation attempt fails. |
snasw |
- |
|
SNASW-4-SM_LOG_40 |
4-Warning |
EXCEPTION - %lu - LU-mode session limit exceeded - BIND race [chars] |
LU-mode session limit exceeded - BIND race. This is normal\n\ race condition caused by both the local LU and partner LU\n\ attempting to activate the last session on the mode\n\ simultaneously. The race will be resolved in favour of the\n\ node with the higher name. In this case the partner LU has\n\ lost the race.\n\ Session activation will fail with specified sense code. |
snasw |
"None." |
|
SNASW-4-SM_LOG_49 |
4-Warning |
EXCEPTION - %lu - UNBIND request received in response to a BIND request [chars] |
UNBIND request received in response to a BIND request. This may\n\ indicate a configuration error or a protocol error.\n\\n\ Common sense codes which typically indicate a configuration\n\ error or a normal race condition include\n\ 0805xxxx - the session could not be activated as session\n\ activation limits have been reached\n\ 08060014 - the partner LU is not known\n\ 0806xxxx - the BIND specified a resource which is not known\n\ 080Fxxxx - security authorization failed\n\ 0821xxxx - the BIND supplied an invalid session parameter\n\ 0835xxxx - parameter error in BIND RU at offset xxxx\n\\n\ Other sense codes include\n\ 0812xxxx - session activation failed due to resource shortage\n\ at the remote node\n\ 083Bxxxx - invalid PCID in BIND RU\n\ 0852xxxx - duplicate session activation request\n\ 0861xxxx - invalid COS name in BIND RU\n\ 088Cxxxx - control vector or subfield missing from BIND RU\n\ 0895xxxx - BIND RU contained a control vector that was in\n\ error\n\ 0896xxxx - BIND RU contained a control vector that was too\n\ long\n\ Session activation will fail with the specified sense code. |
snasw |
"If the sense code indicates a configuration error check for\n\ inconsistencies between the configuration at the local LU and\n\ the configuration at the partner LU. If the configuration is\n\ consistent and the problem persists contact support with\n\ details of the problem." |
|
SNASW-4-SM_LOG_6 |
4-Warning |
EXCEPTION - %lu - Abnormal UNBIND request received [chars] |
Abnormal UNBIND request received. This may indicate a\n\ configuration error or a protocol error.\n\ The session will fail with the specified sense code. |
snasw |
"If the sense code indicates a configuration error check for\n\ inconsistencies between the configuration at the local LU and\n\ the configuration at the partner LU. If the configuration is\n\ consistent and the problem persists contact support with\n\ details of the problem." |
|
SNASW-4-SM2_LOG_0 |
4-Warning |
EXCEPTION - %lu - Standard compression levels used [chars] |
- |
snasw |
"None." |
|
SNASW-4-SM2_LOG_1 |
4-Warning |
EXCEPTION - %lu - Failed to adjust a buffer pool [chars] |
The desired number of buffers could not be reserved for a\n\ buffer pool.\n\ The receive pacing window size for the session will not\n\ increase as fast as configured. |
snasw |
- |
|
SNASW-4-SS_LOG_13 |
4-Warning |
EXCEPTION - %lu - Retrying CP-CP session activation after failure [chars] |
Retrying CP-CP session establishment after error.\n\ None. |
snasw |
"None." |
|
SNASW-4-SS_LOG_17 |
4-Warning |
EXCEPTION - %lu - CP-CP sessions established between network nodes in different networks [chars] |
CP-CP sessions established between two network nodes in\n\ different networks.\n\ CP-CP sessions will be deactivated with the specified sense\n\ code. |
snasw |
"None." |
|
SNASW-4-SS_LOG_19 |
4-Warning |
EXCEPTION - %lu - Insufficient resources to register LU on adjacent LEN [chars] |
Branch Network node has insufficient resources to register an\n\ LU on an adjacent LEN node.\n\ The LU resource may not be put into the directory and may not\n\ be accessible to other resources. |
snasw |
- |
|
SNASW-4-SS_LOG_20 |
4-Warning |
EXCEPTION - %lu - Automatic retry of CP-CP sessions on a timer has failed [chars] |
The node failed to start a timer in order to retry CP-CP\n\ sessions to a Network Node Server.\n\ The node will not automatically attempt to activate CP-CP\n\ sessions and so may be left with no CP-CP sessions at all or\n\ CP-CP sessions with a node that is not the best available.\n\ CP-CP sessions will however be retried in the normal way when\n\ a local application needs them or a new link activates. |
snasw |
"None if CP-CP sessions are not required or if the administrator\n\ is happy with the existing Network Node Server. If the\n\ administrator wants to start CP-CP sessions they can be started\n\ manually." |
|
SNASW-4-SS_LOG_4 |
4-Warning |
EXCEPTION - %lu - Network Node server not required [chars] |
- |
snasw |
"None." |
|
SNASW-4-TC_LOG_0 |
4-Warning |
EXCEPTION - %lu - Session pacing error [chars] |
Session pacing error. This may indicate an interoperability\n\ problem. Sense codes are as follows.\n\ 20110000 - sender has overrun pacing window or\n\ PI not set on first RU of window\n\ 20110001 - unexpected IPM\n\ 20110002 - PI set on other than first RU in window\n\ 20110003 - invalid pacing response\n\ 10010003 - invalid IPM format\n\ The session will be deactivated with the specified sense code. |
snasw |
- |
|
SNASW-4-TC_LOG_1 |
4-Warning |
EXCEPTION - %lu - Session segmentation error [chars] |
Session segmentation error. This may indicate an\n\ interoperability problem. Sense codes are as follows.\n\ 80070000 - segmenting error\n\ 80070001 - segmentation not supported on this link\n\ The session will be deactivated with the specified sense code. |
snasw |
- |
|
SNASW-4-TC_LOG_2 |
4-Warning |
EXCEPTION - %lu - RU length error [chars] |
RU length error. This may indicate an\n\ interoperability problem. Sense codes are as follows.\n\ 10020000 - RU length error\n\ The session will be deactivated with the specified sense code. |
snasw |
- |
|
SNASW-4-TNBM_LOG_0 |
4-Warning |
EXCEPTION - %lu - The Buffer Manager Monitor could not allocate necessary resource [chars] |
The Buffer Manager Monitor could not allocate necessary\n\ resource.\n\ The Buffer Manager will fail to operate and detect congestion\n\ conditions or relief from congestion possibly leading to the\n\ node locking up. |
snasw |
"Shutdown and restart the node." |
|
SNASW-4-TNBM_LOG_1 |
4-Warning |
EXCEPTION - %lu - Insufficient storage to create new buffer pool [chars] |
- |
snasw |
"Investigate memory shortage and system load." |
|
SNASW-4-TNBM_LOG_2 |
4-Warning |
EXCEPTION - %lu - Insufficient buffers to create new buffer pool [chars] |
- |
snasw |
"Investigate buffer shortage and system load." |
|
SNASW-4-TNBM_LOG_3 |
4-Warning |
EXCEPTION - %lu - Critical buffer congestion [chars] |
The Buffer Manager Monitor detected critical buffer congestion\n\ SNA Switch will throttle back session traffic by withholding\n\ pacing responses or resetting pacing windows on adaptive-paced\n\ sessions until the congestion has reduced. |
snasw |
"This condition can occur if the node receives a\n\ large sudden burst of data traffic on several sessions. The\n\ condition should clear itself automatically but if it occurs\n\ frequently it may indicate the node is routing more sessions\n\ than it can handle efficiently with the available buffer\n\ storage. Reduce the number of sessions through the router." |
|
SNASW-4-TNBM_LOG_4 |
4-Warning |
EXCEPTION - %lu - Buffer congestion relieved [chars] |
Buffer congestion relieved. SNA Switch will stop throttling\n\ back session traffic. If the congestion eases further SNA\n\ Switch will start to increase pacing windows on adaptively\n\ paced sessions. |
snasw |
"None" |
|
SNASW-4-TNBM_LOG_5 |
4-Warning |
EXCEPTION - %lu - Critical buffer congestion detected while attempting to relieve congestion [chars] |
The Buffer Manager detected critical buffer congestion while\n\ attempting to relieve a previous congestion condition.\n\ SNA Switch will throttle back session traffic by withholding\n\ pacing responses or resetting pacing windows on adaptive-paced\n\ sessions until the congestion has reduced. |
snasw |
"This condition can occur if the node receives a\n\ large sudden burst of data traffic on several sessions. The\n\ condition should clear itself automatically but if it occurs\n\ frequently it may indicate the node is routing more sessions\n\ than it can handle efficiently with the available buffer\n\ storage. Reduce the number of sessions through the router." |
|
SNASW-4-TNBM_LOG_6 |
4-Warning |
EXCEPTION - %lu - Insufficient storage to request posting [chars] |
Insufficient storage to request posting\n\ The component using the Buffer Manager may fail to operate\n\ or lock up. See other logs for effects. |
snasw |
"Investigate memory shortage and system load." |
|
SNASW-4-TNTL_LOG_0 |
4-Warning |
EXCEPTION - %lu - Implicit alias space wrapped [chars] |
The space for implicit aliases has wrapped. There is a very\n\ slight possibility of duplicate aliases. |
snasw |
"Shut down and restart to avoid any conflict." |
|
SNASW-4-TS_LOG_0 |
4-Warning |
EXCEPTION - %lu - Unable to generate session route : unknown COS name [chars] |
A Class of Service name specified for a session activation\n\ could not be associated with a valid COS.\n\ A session activation will fail with the specified sense code. |
snasw |
"Ensure no mode-to-COS mapping tables at the origin node or its\n\ network node server use the unrecognised COS." |
|
SNASW-4-TS_LOG_1 |
4-Warning |
EXCEPTION - %lu - Unable to generate session route - no suitable TGs from origin node [chars] |
No suitable TG could be found from the origin end node to the\n\ backbone network for the class of service specified for a\n\ session activation. This may be caused by a temporary link\n\ failure between the origin node and a network node.\n\ A session activation will fail with the specified sense code. |
snasw |
"First check for a link failure at the origin node that explains\n\ the route failure. If no link failure is found either\n\ - change the mode-to-COS mapping on the origin node or its\n\ network node server to use a different class of service or\n\ - reconfigure the network to ensure there is a usable route\n\ from the origin node to the backbone network for example by\n\ defining and/or activating another link from the origin node\n\ to a network node." |
|
SNASW-4-TS_LOG_2 |
4-Warning |
EXCEPTION - %lu - Unable to generate session route - no suitable TGs to destination node [chars] |
No suitable TG could be found from the backbone network to the\n\ destination end node for the class of service specified for a\n\ session activation. This may be caused by a temporary link\n\ failure between the destination node and a network node.\n\ A session activation will fail with the specified sense code. |
snasw |
"First check for a link failure at the destination node that\n\ explains the route failure. If no link failure is found\n\ either\n\ - change the mode-to-COS mapping on the origin node or its\n\ network node server to use a different class of service or\n\ - reconfigure the network to ensure there is a useable route\n\ from the destination node to the backbone network for\n\ example by defining and/or activating another link from the\n\ destination node to a network node." |
|
SNASW-4-TS_LOG_6 |
4-Warning |
EXCEPTION - %lu - Unable to generate session route to adjacent node [chars] |
No suitable TG could be found for a session activation to an\n\ adjacent node for the given Class of Service. This may be\n\ caused by a link failure.\n\ A session activation will fail with the specified sense code. |
snasw |
"Check for a link failure that explains the failure.\n\ If no link failure is found reconfigure the network to ensure\n\ there is a useable link between this node and the specified\n\ adjacent node." |
|
SNASW-4-TS_LOG_7 |
4-Warning |
EXCEPTION - %lu - Unable to generate session route - RSCV truncated [chars] |
- |
snasw |
"Reconfigure the network to ensure there is a short enough\n\ route between the origin and destination nodes." |
|
SNASW-6-CS_LOG_39 |
6-Information |
INFO - %lu - Link station to host started [chars] |
A non-APPN link station to an upstream host has been\n\ successfully started. |
snasw |
"None" |
|
SNASW-6-CS_LOG_40 |
6-Information |
INFO - %lu - Link station to DSPU started [chars] |
A non-APPN link station to a downstream PU has been\n\ successfully started. |
snasw |
"None" |
|
SNASW-6-CS_LOG_41 |
6-Information |
INFO - %lu - Link station to host stopped [chars] |
A non-APPN link station to an upstream host has been\n\ successfully stopped. |
snasw |
"None" |
|
SNASW-6-CS_LOG_42 |
6-Information |
INFO - %lu - Link station to DSPU stopped [chars] |
A non-APPN link station to a downstream PU has been\n\ successfully stopped. |
snasw |
"None" |
|
SNASW-6-CS_LOG_44 |
6-Information |
INFO - %lu - SNA Switch link started [chars] |
An SNA Switch link has been successfully started. |
snasw |
"None" |
|
SNASW-6-CS_LOG_55 |
6-Information |
INFO - %lu - HPR-capable SNA Switch link started [chars] |
An SNA Switch link has been successfully started on a node\n\ that supports HPR. |
snasw |
"None" |
|
SNASW-6-CS_LOG_56 |
6-Information |
INFO - %lu - SNA Switch link stopped [chars] |
An SNA Switch link has been successfully stopped. |
snasw |
"None" |
|
SNASW-6-CS_LOG_57 |
6-Information |
INFO - %lu - DLC started [chars] |
A DLC has been successfully started. |
snasw |
"None" |
|
SNASW-6-CS_LOG_58 |
6-Information |
INFO - %lu - DLC stopped [chars] |
A DLC has been successfully stopped. |
snasw |
"None" |
|
SNASW-6-CS_LOG_59 |
6-Information |
INFO - %lu - Port started [chars] |
A Port has been successfully started. |
snasw |
"None" |
|
SNASW-6-CS_LOG_60 |
6-Information |
INFO - %lu - Port stopped [chars] |
A Port has been successfully stopped. |
snasw |
"None" |
|
SNASW-6-CS_LOG_66 |
6-Information |
INFO - %lu - Adjacent node has changed its CP name [chars] |
An adjacent node has changed its CP name. |
snasw |
"None" |
|
SNASW-6-CS2_LOG_0 |
6-Information |
INFO - %lu - Implicit link limit on port reached [chars] |
An implicit dynamic or discovery link could not be activated\n\ because the implicit link limit defined on the port has been\n\ reached or exceeded.\n\ The link type being activated is:\n\ 1 - dynamic\n\ 3 - implicit\n\ 4 - discovery |
snasw |
"None" |
|
SNASW-6-DLUR_LOG_12 |
6-Information |
INFO - %lu - A pipe to a DLUS has activated [chars] |
A pipe to a DLUS has activated. |
snasw |
"None" |
|
SNASW-6-DLUR_LOG_13 |
6-Information |
INFO - %lu - A pipe to a DLUS has deactivated [chars] |
A pipe to a DLUS has deactivated. |
snasw |
"None" |
|
SNASW-6-DLUR_LOG_19 |
6-Information |
INFO - %lu - Deactivating a persistent pipe because it is not required [chars] |
The DLUR is deactivating a persistent pipe because it is not\n\ required to keep it active. |
snasw |
"None" |
|
SNASW-6-DLUR_LOG_24 |
6-Information |
INFO - %lu - A PU previously logged as possibly hung is no longer possibly hung [chars] |
A PU that had previously been logged as hung is now not\n\ believed to be hung.\n\ There will be no further action taken |
snasw |
"None." |
|
SNASW-6-DS_LOG_38 |
6-Information |
INFO - %lu - Central Directory Server located [chars] |
Central Directory Server located. |
snasw |
"None" |
|
SNASW-6-DS_LOG_43 |
6-Information |
INFO - %lu - Locate search failed: LU not found [chars] |
A network search for which this node was the originator or the\n\ network node server failed to locate the target LU. This may\n\ be caused by the target LU name being incorrect the target\n\ system being inoperative or by link errors in the backbone of\n\ the network.\n\ Session activation will fail with the specified sense code. |
snasw |
"If the target LU name is correct check that the system the\n\ LU is defined on is active. If the system is active check\n\ the topology of the network to ensure that the target system\n\ or its network node server is reachable from this node." |
|
SNASW-6-LDLC_DEBUG_LOG_0 |
6-Information |
INFO - %lu - Link activation race has occurred [chars] |
Link activation race has occurred\n\ Link activation will complete but the routes may be different\n\ in each direction. No other effect will be noticeable. |
snasw |
"None." |
|
SNASW-6-LDLC_IP_LOG_9 |
6-Information |
INFO - %lu - Invalid IP address specified for a IPDLC link [chars] |
Invalid IP address specified for a IPDLC link.\n\ The link will fail to start. |
snasw |
" Correct the configuration. These settings are supplied in the\n\ address information passed to SNA Switch on snasw link." |
|
SNASW-6-LM_LOG_0 |
6-Information |
INFO - %lu - An LU-SSCP session has been activated for LU type 012 or 3 [chars] |
An LU-SSCP session has been activated. |
snasw |
"None" |
|
SNASW-6-LM_LOG_1 |
6-Information |
INFO - %lu - A PLU-SLU session has been activated for LU type 012 or 3 [chars] |
A PLU-SLU session has been activated. |
snasw |
"None" |
|
SNASW-6-LM_LOG_2 |
6-Information |
INFO - %lu - An LU-SSCP session has been deactivated for LU type 012 or 3 [chars] |
An LU-SSCP session has been deactivated. |
snasw |
"None" |
|
SNASW-6-LM_LOG_3 |
6-Information |
INFO - %lu - A PLU-SLU session has been deactivated for LU type 012 or 3 [chars] |
A PLU-SLU session has been deactivated. |
snasw |
"None" |
|
SNASW-6-MS_LOG_7 |
6-Information |
INFO - %lu - Alert data logged [chars] |
TRANSFER_MS_DATA/SEND_MDS_MU data has arrived. |
snasw |
"None" |
|
SNASW-6-NOF_LOG_2 |
6-Information |
INFO - %lu - Node started [chars] |
Node has been successfully started. |
snasw |
"None" |
|
SNASW-6-NOF_LOG_4 |
6-Information |
INFO - %lu - Node stopped [chars] |
Node has been successfully stopped. |
snasw |
"None" |
|
SNASW-6-PS_LOG_9 |
6-Information |
INFO - %lu - Processed APING from partner LU. [chars] |
An APING from the partner LU has been processed successfully. |
snasw |
"None" |
|
SNASW-6-PU_LOG_0 |
6-Information |
INFO - %lu - A PU-SSCP session has been activated [chars] |
A PU-SSCP session has been activated. |
snasw |
"None" |
|
SNASW-6-PU_LOG_1 |
6-Information |
INFO - %lu - A PU-SSCP session has been deactivated [chars] |
A PU-SSCP session has been deactivated. |
snasw |
"None" |
|
SNASW-6-RM_LOG_27 |
6-Information |
INFO - %lu - Session limits changed [chars] |
The session limits for a local LU partner LU and mode have\n\ changed. The termination count indicates the number of\n\ sessions SNA Switch will deactivate as a result of the change\n\ in session limits. |
snasw |
"None" |
|
SNASW-6-RTP_LOG_0 |
6-Information |
INFO - %lu - RTP Connection has connected [chars] |
The RTP Connection has connected |
snasw |
"None" |
|
SNASW-6-RTP_LOG_1 |
6-Information |
INFO - %lu - RTP Connection has disconnected [chars] |
The RTP Connection has disconnected normally |
snasw |
"None" |
|
SNASW-6-RTP_LOG_6 |
6-Information |
INFO - %lu - Successful path-switch [chars] |
he RTP Connection has successfully switched paths |
snasw |
"None" |
|
SNASW-6-SCM_LOG_10 |
6-Information |
INFO - %lu - ISR Session Deactivated [chars] |
An ISR Session has been deactivated |
snasw |
"None" |
|
SNASW-6-SCM_LOG_9 |
6-Information |
INFO - %lu - ISR Session Activated [chars] |
An ISR Session has been activated |
snasw |
"None" |
|
SNASW-6-SM_LOG_37 |
6-Information |
INFO - %lu - LU6.2 session activated [chars] |
An LU6.2 session has been activated. |
snasw |
"None" |
|
SNASW-6-SM_LOG_38 |
6-Information |
INFO - %lu - LU6.2 session deactivated [chars] |
An LU6.2 session has been deactivated. |
snasw |
"None" |
|
SNASW-6-SM_LOG_43 |
6-Information |
INFO - %lu - An LU-SSCP session has been activated for LU type 6.2 [chars] |
An LU-SSCP session has been activated. |
snasw |
"None" |
|
SNASW-6-SM_LOG_44 |
6-Information |
INFO - %lu - An LU-SSCP session has been deactivated for LU type 6.2 [chars] |
An LU-SSCP session has been deactivated. |
snasw |
"None" |
|
SNASW-6-SS_LOG_11 |
6-Information |
INFO - %lu - Adjacent CP contacted [chars] |
Adjacent CP contacted. |
snasw |
"None" |
|
SNASW-6-SS_LOG_12 |
6-Information |
INFO - %lu - CP-CP sessions established [chars] |
CP-CP sessions have been successfully established with the\n\ adjacent node. |
snasw |
"None" |
|
SNASW-6-SS_LOG_18 |
6-Information |
INFO - %lu - CP-CP sessions deactivated [chars] |
CP-CP sessions to the adjacent node have been deactivated. |
snasw |
"None" |
|
SNMP_BULKSTAT-3-NO_MEMORY |
3-Error |
Memory not available for [chars] for [chars] |
Data Collection or Transfer could not be successfully carried out because of lack of memory. |
dcm |
LOG_STD_REDUCE_ACTION |
|
SNMP_BULKSTAT-3-NO_MEMORY |
3-Error |
Memory not available for [chars] for [chars] |
Data Collection or Transfer could not be successfully carried out because of lack of memory. |
snmp |
LOG_STD_REDUCE_ACTION |
|
SNMP_BULKSTAT-3-REMOTE_FILE_WRITE_ERR |
3-Error |
File Write failed for the remote file [chars] |
Username or password specified in the error message might\n\ not have the required privileges to write a file to the \n\ network management station specified in the error message\n\ or the destination directory specified in the error message\n\ is invalid. |
dcm |
"Ensure that the user name and password in the network \n\ management station address has the necessary privileges \n\ to write to the destination directory." |
|
SNMP_BULKSTAT-3-REMOTE_FILE_WRITE_ERR |
3-Error |
File Write failed for the remote file [chars] |
Username or password specified in the error message might not have the required privileges to write a file to the network management station specified in the error message or the destination directory specified in the error message is invalid. |
snmp |
"Ensure that the user name and password in the network " "management station address has the necessary privileges " "to write to the destination directory." |
|
SNMP_BULKSTAT-3-TOOSMALL_BUFFER |
3-Error |
Buffer size is insufficient to accommodate even the header part for [chars] |
The buffer size is insufficient to accommodate the header \n\ for the bulk data file. The header contains the schema \n\ definitions of all the configured schemas. |
dcm |
"Increase the maximum buffer size using the \n\ <CmdBold>buffer-size<NoCmdBold> size-of-buffer command \n\ where size-of-buffer is the increased buffer size." |
|
SNMP_BULKSTAT-3-TOOSMALL_BUFFER |
3-Error |
Buffer size is insufficient to accommodate even the header part for [chars] |
The buffer size is insufficient to accommodate the header for the bulk data file. The header contains the schema definitions of all the configured schemas. |
snmp |
"Increase the maximum buffer size using the " "<CmdBold>buffer-size<NoCmdBold> size-of-buffer command " "where size-of-buffer is the increased buffer size." |
|
SNMP_BULKSTAT-4-BUFFER_OVERFLOW |
4-Warning |
Buffer size too small to accommodate data for one collection\n\ interval for [chars] |
The bulk data file is too large for the configured buffer \n\ size for a single transfer interval. Data collection will \n\ continue in another new buffer of the configured size and \n\ the collected buffer will be transferred to the configured \n\ destination. |
dcm |
"Increase the maximum buffer size using the \n\ <CmdBold>buffer-size<NoCmdBold> size-of-buffer command \n\ where size-of-buffer is the increased buffer size." |
|
SNMP_BULKSTAT-4-BUFFER_OVERFLOW |
4-Warning |
Buffer size too small to accommodate data for one collection interval for [chars] |
The bulk data file is too large for the configured buffer size for a single transfer interval. Data collection will continue in another new buffer of the configured size and the collected buffer will be transferred to the configured destination. |
snmp |
"Increase the maximum buffer size using the " "<CmdBold>buffer-size<NoCmdBold> size-of-buffer command " "where size-of-buffer is the increased buffer size." |
|
SNMP_BULKSTAT-4-PRI_URL_UNREACHABLE |
4-Warning |
Primary network management station is unreachable for [chars] |
The Collected Bulk data file could not be successfully \n\ transferred to the primary network management station address\n\ specified in the error message. This condition can occur \n\ because the primary network management address is not \n\ configured or the configured primary network management \n\ station address is unreachable. If a secondary network \n\ management station address is configured the collected bulk \n\ data file will be sent to the secondary network management \n\ station address. |
dcm |
"Ensure that the primary network management station address \n\ is configured. If the primary network management station \n\ address is configured check the connectivity to the\n\ destination indicated by the primary network management\n\ station address specified in the error message." |
|
SNMP_BULKSTAT-4-PRI_URL_UNREACHABLE |
4-Warning |
Primary network management station is unreachable for [chars] |
The Collected Bulk data file could not be successfully transferred to the primary network management station address specified in the error message. This condition can occur because the primary network management address is not configured or the configured primary network management station address is unreachable. If a secondary network management station address is configured the collected bulk data file will be sent to the secondary network management station address. |
snmp |
"Ensure that the primary network management station address " "is configured. If the primary network management station " "address is configured check the connectivity to the " "destination indicated by the primary network management " " station address specified in the error message." |
|
SNMP_BULKSTAT-4-SEC_URL_UNREACHABLE |
4-Warning |
Secondary network management station is unreachable for [chars] |
The collected bulk data file could not be successfully \n\ transferred to the secondary network management station \n\ address destination specified in the error message. This \n\ condition can occur because the secondary network management \n\ station address is not configured or the configured secondary\n\ network management station address is unreachable. If a \n\ retention interval is not configured the bulk data file \n\ will be immediately deleted. If a retention interval is \n\ configured retries will be attempted for the configured \n\ number of times. |
dcm |
"Check the connectivity to destination indicated by secondary\n\ network management station address indicated in the error\n\ message" |
|
SNMP_BULKSTAT-4-SEC_URL_UNREACHABLE |
4-Warning |
Secondary network management station is unreachable for [chars] |
The collected bulk data file could not be successfully transferred to the secondary network management station address destination specified in the error message. This condition can occur because the secondary network management station address is not configured or the configured secondary network management station address is unreachable. If a retention interval is not configured the bulk data file will be immediately deleted. If a retention interval is configured retries will be attempted for the configured number of times. |
snmp |
"Check the connectivity to destination indicated by secondary " "network management station address indicated in the error " "message" |
|
SNMP_CONTEXT_MAPPING-3-TOPO_NOT_BASE |
3-Error |
Multi Topology un-aware component is accessing a non base topology [chars] topoid [dec] |
A software component that is not multi topology aware is\n\ accessing a non base topology. When this happens the result\n\ is un-predictable. |
Determine the component from the stack trace which indicates\n\ which subsystem is causing this error. Search for\n\ similiar DDTS reports and open a DDTS. |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
SNMP_FILL-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
SNMP_ION-2-PTHREADMUTEXFAIL |
2-Critical |
pthread_mutex_init failed on snmp mutex. Reason : [chars] |
The snmp subagent failed to initialize the global mutex |
ion |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SNMP_ION-3-IFMIB_SHM_FAIL |
3-Error |
IF-MIB could not attach/create shared memory region |
The IF-MIB maintains a part of its data structure in shared\n\ memory. In the process of creating/attaching/initializing\n\ this shared memory region a failure was detected. |
Determine the component from the stack trace which indicates\n\ which subsystem is attempting to generate a trap. Search for\n\ similiar DDTS reports and open a DDTS. |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
SNMP_ION-3-MIB_REG_FAIL |
3-Error |
MIB could not be registered with master agent |
When a MIB is loaded in ION the OIDs are registered with the\n\ master agent. A failure was detected in this registration\n\ process |
Determine the component from the stack trace which indicates\n\ which subsystem is attempting to generate a trap. Search for\n\ similiar DDTS reports and open a DDTS. |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
SNMP_MGR-3-BADAGETIMER |
3-Error |
Unexpected age timer found on session %0x |
An internal timer was found running when it should not have been. |
snmp |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative. Disable the SNMP manager via\n\ the no snmp-server manager command. Then re-enable it via the\n\ snmp-server manager command. This should effectively reset all of\n\ the internal structures." |
|
SNMP_MGR-3-BADINFORMTRANSPORT |
3-Error |
Unknown inform transport type: [chars] |
This SNMP inform destination uses an unknown transport type.\n\ Inform notifications cannot be sent to this destination. |
snmp |
"Copy the error message and the output from 'show techsupport' exactly\n\ as it appears and report it to your technical support representative." |
|
SNMP_MGR-3-BADOP |
3-Error |
Unknown operation code [dec] |
An SNMP PDU delivered to the SNMP manager contains an unknown\n\ operation code. |
snmp |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SNMP_MGR-3-BADPDUTYPE |
3-Error |
Received unknown PDU type: [dec] |
The SNMP manager was delivered a PDU of an unknown type. |
snmp |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SNMP_MGR-3-BADTRANSPORT |
3-Error |
Unknown transport type: [dec] |
The SNMP manager was delivered a PDU from an unknown transport type. |
snmp |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SNMP_MGR-3-BADUSECOUNT |
3-Error |
Corrupted use counter found on session %0x |
A cached SNMP session structure appears to have been corrupted. |
snmp |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative. Disable the SNMP manager via\n\ the no snmp-server manager command. Then re-enable it via the\n\ snmp-server manager command. This should effectively reset all of\n\ the internal structures." |
|
SNMP_MGR-3-MISSINGHOST |
3-Error |
Cannot locate information on SNMP informs host: [inet] |
A table entry for the mentioned SNMP informs destination cannot\n\ be found. As a result inform notifications will not be sent to\n\ this destination. |
snmp |
"Run the 'show snmp host' and 'show snmp' commands. Copy the error\n\ message and output from the show commands exactly as they appear\n\ and report it to your technical support representative.\n\ Deleting and re-adding the informs destination via the\n\ 'snmp-server host' configuration command may clear the condition.\n\ Otherwise reloading the system may be necessary." |
|
SNMP_MGR-3-MISSINGHOSTIPV6 |
3-Error |
Cannot locate information on SNMP informs host: %P |
A table entry for the mentioned SNMP informs destination cannot\n\ be found. As a result inform notifications will not be sent to\n\ this destination. |
snmp |
"Run the 'show snmp host' and 'show snmp' commands. Copy the error\n\ message and output from the show commands exactly as they appear\n\ and report it to your technical support representative.\n\ Deleting and re-adding the informs destination via the\n\ 'snmp-server host' configuration command may clear the condition.\n\ Otherwise reloading the system may be necessary." |
|
SNMP_MGR-3-NOPROC |
3-Error |
Failed to create SNMP Manager process |
The SNMP manager process was unable to initialize. This is most\n\ likely due to a lack of memory. |
snmp |
"Copy the error message exactly as it appears and report it to\n\ your technical support representative. Use the show memory\n\ command to examine the amount of available memory. If free\n\ memory is low you may need to reconfigure and/or reload the\n\ system." |
|
SNMP_MGR-3-RESPDROP |
3-Error |
Insufficient memory to handle response to request id [dec] |
An SNMP response PDU was received but there was not enough\n\ memory available in order to cache the response and return it\n\ to the original requesting IOS application. |
snmp |
"If this was only a transient problem the original SNMP request\n\ will likely be resent another SNMP response will be returned\n\ and delivered to the original requesting IOS application. If\n\ this message repeats then you will need to free up some memory\n\ in order for the SNMP manager to function. Use show memory to\n\ verify whether available memory is low. You may need to reconfigure\n\ and/or reload the system in order to free up some memory. Otherwise\n\ you can disable the SNMP manager functionality via the no\n\ snmp-server manager command." |
|
SNMP_MGR-3-SESSIONINUSE |
3-Error |
Attempt to destroy session %0x that is still in use |
An attempt was made to remove a cached SNMP session structure\n\ however it appears that the session is still in use and therefore\n\ should not be removed. |
snmp |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SNMP_MGR-4-BADAUTHTYPE |
4-Warning |
Unsupported SNMP authorization type: [dec] |
An unknown SNMP authorization type was found. This may result in\n\ the inability of the SNMP manager functionality to correctly send\n\ and/or receive SNMP messages to/from a particular SNMP agent. |
snmp |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SNMP_MGR-4-BADRESPONSESTATUS |
4-Warning |
Unknown response status code: [dec] |
The SNMP Manager process received an internal response with an\n\ unknown status code. |
snmp |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SNMP_MGR-4-EMPTYQUEUE |
4-Warning |
Input queue is empty |
The SNMP Manager process was notified that it needs to process\n\ it's input queue. But when the queue was examined it was found\n\ to be empty. |
snmp |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SNMP_MGR-4-NOCANCEL |
4-Warning |
Unable to cancel a previously sent inform request. |
The number of unacknowledged inform requests in-flight has reached\n\ the configured maximum limit. In order to make available resources\n\ for sending out a new inform request one of these older inform\n\ requests must be cancelled. The algorithm used to choose the most\n\ appropriate inform to cancel has failed to choose any. The new inform\n\ that was to be sent will be dropped instead. |
snmp |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SNMP_MGR-4-NOTENABLED |
4-Warning |
SNMP Manager not enabled requested by [chars] |
An IOS application is attempting to make use of the SNMP manager's\n\ services. However the SNMP manager functionality has not been\n\ enabled. |
- |
"If you wish to enable the SNMP manager services you may do so via\n\ the 'snmp-server manager' config command. Otherwise the IOS\n\ application that is requesting these services is given in the\n\ message. Disable or reconfigure this application such that it no\n\ longer tries to make SNMP manager requests." |
|
SNMP_MIB_ISSU-2-GET_BUFFER |
2-Critical |
SNMP MIB ISSU client failed to get buffer for message. Error: [dec] [chars] |
The SNMP MIB 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. |
snmp |
"show logging and show checkpoint client" |
|
SNMP_MIB_ISSU-2-INIT |
2-Critical |
SNMP MIB ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The SNMP MIB 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. |
snmp |
LOG_STD_ACTION |
|
SNMP_MIB_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
SNMP MIB ISSU client failed to send negotiation message. Error: [dec] [chars] |
The SNMP MIB 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. |
snmp |
"show logging and show checkpoint client" |
|
SNMP_MIB_ISSU-2-SESSION_NEGO |
2-Critical |
SNMP MIB ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The SNMP MIB 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. |
snmp |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
SNMP_MIB_ISSU-2-SESSION_REGISTRY |
2-Critical |
SNMP MIB ISSU client failed to register session information. Error: [dec] [chars] |
The SNMP MIB ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
snmp |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
SNMP_MIB_ISSU-3-CAP_INVALID_SIZE |
3-Error |
SNMP MIB ISSU client capability list is empty. |
The SNMP MIB ISSU client capability exchange list size is invalid. |
snmp |
"show issu capability entires <Client_ID>" |
|
SNMP_MIB_ISSU-3-CAP_NOT_COMPATIBLE |
3-Error |
SNMP MIB ISSU client capability exchange result incompatible. |
The SNMP MIB ISSU client capability exchange have negotiated as incompatible with the peer. |
snmp |
"show issu negotiated capability <Session_ID>" |
|
SNMP_MIB_ISSU-3-INVALID_SESSION |
3-Error |
SNMP MIB ISSU client does not have a valid registered session. |
The SNMP MIB ISSU client does not have a valid registered session. |
snmp |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
SNMP_MIB_ISSU-3-MSG_NOT_OK |
3-Error |
SNMP MIB ISSU client 'Message Type [dec]' is not compatible |
The SNMP MIB ISSU client received an incompatible message from the peer device. The message cannot be processed. |
snmp |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
SNMP_MIB_ISSU-3-MSG_SIZE |
3-Error |
SNMP MIB ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The SNMP MIB ISSU client failed to calculate the MTU for the specified message. The SNMP MIB ISSU client is not able to send the message to the standby device. |
snmp |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
SNMP_MIB_ISSU-3-SESSION_UNREGISTRY |
3-Error |
SNMP MIB ISSU client failed to unregister session information. Error: [dec] [chars] |
The SNMP MIB ISSU client failed to unregister session information. |
snmp |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
SNMP_MIB_ISSU-3-TRANSFORM_FAIL |
3-Error |
SNMP MIB ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The SNMP MIB 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 SNMP MIB state between the active device and the standby device is not identical. |
snmp |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
SNMP-3-AUTHFAIL |
3-Error |
Authentication failure for SNMP req from host [inet] |
An SNMP request was sent to this host which was not properly\n\ authenticated. |
none |
"Make sure that the community/user name used in the SNMP req\n\ has been configured on the router." |
|
SNMP-3-AUTHFAILIPV6 |
3-Error |
Authentication failure for SNMP request from host %P |
An SNMP request was sent by this host which was not properly\n\ authenticated. |
none |
"Make sure that the community/user name used in the SNMP req\n\ has been configured on the router." |
|
SNMP-3-BADIFINDEXTABLE |
3-Error |
The file nvram:ifIndex-table is corrupt. |
The file is not in the expected format. |
snmp |
"If possible please delete the file." |
|
SNMP-3-BADOID |
3-Error |
Attempt to generate an invalid object identifier |
A valid object identifier must contain at least two subidentifiers.\n\ An attempt was made to generate an object identifier whose size\n\ was less than two. |
Determine the component from the stack trace which indicates\n\ which subsystem is attempting to generate invalid object\n\ identifiers. Search for similiar DDTS reports and open a DDTS. |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
SNMP-3-BADVALUE |
3-Error |
Maximum number of index supported is 20 |
An SNMP trap contains some number of MIB objects and the size\n\ of the instance identifier for these objects is restricted. This\n\ message indicates that an attempt was made to generate an SNMP\n\ trap containing a MIB object whose size exceeded this limit. |
snmp |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
SNMP-3-CPUHOG |
3-Error |
Processing [chars] of [chars] |
SNMP took too much time processing a request. |
Determine the component from the debug output which indicates\n\ which subsystem is processing a request. Search for similiar DDTS\n\ reports and open a DDTS. |
"If feasible use the <bold>debug snmp packet<nobold> command to determine the\n\ contents of the SNMP request that is causing the message. Copy the\n\ error message exactly as it appears and report it along with any\n\ debug output to your technical support representative." |
|
SNMP-3-DUPLICATE_IFINDEX |
3-Error |
[chars] has [dec] duplicate ifIndices. |
ifIndex-table file is corrupt. Ignoring duplicate entries. |
snmp |
"If ifIndex-table is not needed please delete the file from nvram." |
|
SNMP-3-DVR_DUP_REGN_ERR |
3-Error |
Attempt for dupe regn with SNMP IM by driver having ifIndex [dec] and ifDescr [chars] |
Driver is attempting to register an idb with the interface manager while there is already an interface with the same ifIndex and ifDescr BUT different idb registered. This would lead into the problem that interface counters shown by snmp would not work properly for this particular interface. |
Component owner of the driver |
"Fix the duplicate registration in driver level." |
|
SNMP-3-DVR_DUP_REGN_WARNING |
3-Error |
Attempt for dupe regn with SNMP IM by driver having ifIndex [dec] and ifDescr [chars] |
Driver is attempting to register the same idb with the interface manager while it's already registered. This is just a warning message and handled by snmp. |
Component owner of the driver |
"Fix the duplicate registration in driver level." |
|
SNMP-3-DYNSYNCFAIL |
3-Error |
Snmp Dynamic Sync Failed for [chars] = [chars] |
One of the SNMP MIB Dynamic Syncsync of Snmp SET to standby failed. |
Determine the component from the OIDs printed as part of the message\n\ for which dynamic sync has failed.\n\ Search for similiar DDTS reports and open a DDTS. |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
SNMP-3-FILEOPENFAILED |
3-Error |
Could not open [chars]. |
The ifIndex-table is not accesible and hence the facility for ifindex persistence may not be available. |
snmp |
"Please debug using the debug ifs file command." |
|
SNMP-3-FILESTATFAILED |
3-Error |
Could not get information for file [chars]. |
The ifIndex-table is not accesible and hence the facility for ifindex persistence may not be available. |
snmp |
"Please debug using the debug ifs file command." |
|
SNMP-3-IFINDEXTABLE_DECOMPRESSFAILED |
3-Error |
The file nvram:ifIndex-table.gz could not be decompressed. |
There is either insufficient memory to compress it or the nvram space is insufficient or some other reason. |
snmp |
"If possible please delete the file." |
|
SNMP-3-IFINDEXTABLEFILEINTWOFORMATS |
3-Error |
ifIndex-table is present in two formats. |
Both nvram:ifIndex-table and nvram:ifIndex-table.gz are present. |
snmp |
"No action is necessary." |
|
SNMP-3-INCORRECT_SIZE_FOR_NVRAM |
3-Error |
Size should be > 0 but it is [dec]. |
There is some initialization problem in software. |
snmp |
"Ideally you should never see this message. If you do please report it at the earliest convenience." |
|
SNMP-3-INPUT_QFULL_ERR |
3-Error |
Packet dropped due to input queue full |
Snmp packet dropped due to input queue full error |
snmp |
- |
|
SNMP-3-INTERRUPT_CALL_ERR |
3-Error |
[chars] function cannot be called from interrupt handler |
This message indicates that a call has been made to the function from\n\ an interrupt handler. This is not permitted because it will fail and \n\ device will reboot down the stack in malloc call. |
snmp |
"If this messages recurs copy it exactly as it appears and report\n\ it to your technical support representative." |
|
SNMP-3-ISSU_ERR |
3-Error |
[chars] |
Error happens when doing ISSU Versioning Operation |
snmp |
"Report this message to technical support" |
|
SNMP-3-LICENSE_CHECK_FAILURE |
3-Error |
Bad OID License check failure while executing snmp-server view [chars] [chars] [chars] |
This message indicates that snmp-server view command for a TAP MIB has failed as a result of missing License requirements. |
- |
"Please re-add the missing/failed configuration " "adhering to the License requirement to avoid inconsistency " "in the configuration." |
|
SNMP-3-MAX_TRAPS_EXCEED_ERR |
3-Error |
Maximum number of traps exceeded the maximum allowed in the current sync-message to STANDBY |
This message indicates the number of SNMP traps defined exceeded the maximum we can accomodate in a checkpoint sync-message. You the developer need to increase SNMP_SYNC_BITMASK_MAX to a higher value. Please check smci_rf_status_event for further details. |
snmp |
"Developers will never see this error message." |
|
SNMP-3-NON_POSITIVE_IFINDEX |
3-Error |
[chars] has [dec] non-positive ifIndices. |
ifIndex-table file has some invalid entries that have non-positive\n\ ifIndex values. Ignoring invalid entries. |
snmp |
"If ifIndex-table is not needed please delete the file from nvram." |
|
SNMP-3-SYNCFAIL |
3-Error |
SNMP MIB Sync Failure: [chars] |
One of the SNMP MIB Sync to standby failed. |
Determine the mib component from the stack trace which indicates\n\ which MIB sync failure is generating this message.\n\ Search for similiar DDTS reports and open a DDTS. |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
SNMP-3-TOOMANYIFINDICES |
3-Error |
Some ifindices might not be persisted. |
There are too many ifindices and the system is unable to persist all of them. |
snmp |
"Most likely this is a system limitation and there is no workaround." |
|
SNMP-3-TRAPBLOCK |
3-Error |
Attempt to generate SNMP trap from a process with blocking disabled |
During processing a process with blocking disabled attempted to\n\ generate an SNMP trap which would block. This is not allowed. |
Determine the component from the stack trace which indicates\n\ which subsystem is attempting to generate a trap. Search for\n\ similiar DDTS reports and open a DDTS. |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
SNMP-3-TRAPINTR |
3-Error |
Attempt to generate SNMP trap from interrupt level |
During the processing of an interrupt the code attempted to\n\ generate an SNMP trap. This is not allowed. |
Determine the component from the stack trace which indicates\n\ which subsystem is attempting to generate a trap. Search for\n\ similiar DDTS reports and open a DDTS. |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
SNMP-4-HIGHCPU |
4-Warning |
Process exceeds [dec]ms threshold [dec]ms IOS quantum for [chars] of [chars]--result [chars] |
SNMP took more than the warning threshold processing a var-binding. |
Determine the component from the debug output which indicates\n\ which subsystem is processing a request. Search for similiar DDTS\n\ reports and/or based on the impact of the processing time \n\ determine if this is a bug. |
"If feasible use the <bold>debug snmp packet<nobold> command to determine the\n\ contents of the SNMP request that is causing the message. Copy the\n\ error message exactly as it appears and report it along with any\n\ debug output to your technical support representative. Some MIB \n\ objects require a relatively large amount of time to process. \n\ MIB objects in the multi-variable-binding are processed one by one. \n\ If possible MIB objects appearing in this message should NOT be \n\ retrieved using multi-variable-binding SNMP PDUs." |
|
SNMP-4-IFINDEXPERS_INTERNAL_ERROR |
4-Warning |
An internal error occurred in ifindex persistence code. |
There is an unexpected internal error in ifindex persistence software. |
snmp |
"" |
|
SNMP-4-NOENGINEID |
4-Warning |
Remote snmpEngineID for [inet] not found when creating user: [chars] |
- |
snmp |
"\n\ Configure the remote snmpEngineID and reconfigure the user.\n\ If the problem persists copy the error message exactly as it\n\ appears and report it to your technical support representative." |
|
SNMP-4-NOENGINEIDV6 |
4-Warning |
Remote snmpEngineID for %P not found when creating user: [chars] |
- |
snmp |
"Configure the remote snmpEngineID and reconfigure the user.\n\ If the problem persists copy the error message exactly as it\n\ appears and report it to your technical support representative." |
|
SNMP-4-NOFLASH |
4-Warning |
Reading snmpEngineBoots from flash failed |
An attempt to read the snmpEngineBoots file from flash failed.\n\ Most likely this means that the flash card does not exist on\n\ the router. This message should appear only when the router is\n\ reloaded. |
snmp |
"\n\ Check if installing a flash card makes the message go away.\n\ If a flash card exists already it may be full. Try erasing\n\ flash and reloading the router. If after these steps the problem\n\ persists copy the error message exactly as it appears and report\n\ it to your technical support representative." |
|
SNMP-4-TRAPDROP |
4-Warning |
[chars] |
An attempt was made to generate an SNMP trap but the trap\n\ could not be sent because of the reason given in this message.\n\ Most likely this message means that the SNMP traps process is\n\ not running. |
snmp |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative. Use the <bold>show process<nobold>\n\ command to determine whether the SNMP traps process is running.\n\ If it is not running reload the system. If after reloading\n\ the SNMP traps process is still not running there may not be\n\ enough memory for it to run." |
|
SNMP-5-CHASSISALARM |
5-Notice |
Chassis Alarm Trap: tmpAlarm[chars] minorAlarm[chars] and/or majorAlarm[chars] |
This message shows the SNMP agent sends out the Chassis Alarm On/Off Traps to the engine ID of the remote agent or SNMP manager because the corresponding chassis alarm is on/off. |
snmp |
"" |
|
SNMP-5-COLDSTART |
5-Notice |
SNMP agent on host [chars] is undergoing a cold start |
The snmp server underwent a coldstart. |
none |
"Notification message only. No action required." |
|
SNMP-5-LINK_DOWN |
5-Notice |
LinkDown:Interface [chars] changed state to down |
The state of the Interface is changed to down. |
none |
"" |
|
SNMP-5-LINK_UP |
5-Notice |
LinkUp:Interface [chars] changed state to up |
SNMP agent generated view length greater than that allowed by definition so the view name was truncated to fit the defined maximum view name length. |
snmp |
"Make sure your trap group and view names are setup appropriately. " "You can override with 'snmp-server group' command. Notify Cisco " "that this needs to be fixed." |
|
SNMP-5-MODULERESET |
5-Notice |
[chars] object has been set to 'reset' for [chars]=[dec] from IP address [chars]. |
The SNMP server has reset a module. |
none |
"Notification message only. No action required." |
|
SNMP-5-MODULETRAP |
5-Notice |
Module [dec] [[chars]] Trap |
This message shows the SNMP agent sends out the Module Up/Down Traps to the engine ID of the remote agent or SNMP manager because the corresponding module is up/down. |
snmp |
"" |
|
SNMP-5-SNMP_SET_BLOCKED |
5-Notice |
SNMP SET Operation is blocked on STANDBY |
This message indicates that on a platform where standby monitoring is enabled SET would be blocked to avoid any config changes on the device from the user. |
none |
"Do not execute SET on standby " |
|
SNMP-5-WARMSTART |
5-Notice |
SNMP agent on host [chars] is undergoing a warm start |
The snmp server underwent a warmstart. |
none |
"Notification message only. No action required." |
|
SNMP-6-AUTHPROTOCOLMD5 |
6-Information |
Authentication protocol md5 support will be deprecated in future |
Authentication protocol support MD5 will be removed for SNMPV3 user creation in SNMP in future |
snmp |
"Notification message only. No action required." |
|
SNMP-6-PRIVPROTOCOLDES |
6-Information |
Privacy protocol [chars] support will be deprecated in future |
Privacy protocol support DES and 3DES will be removed for SNMPV3 user creation in future |
snmp |
"Notification message only. No action required." |
|
SNP_RP-3-ADD_FILTER |
3-Error |
Error in adding filter to list: [chars] |
An unexpected condition has occurred while IOS is trying to add a new filter to the list of traps to be forwarded to the DMI subsystem |
polaris-dmi-infra |
LOG_STD_ACTION |
|
SNP_RP-3-SNMP_TRAP_SEND |
3-Error |
Error in forwarding SNMP trap to confd: [chars] |
An unexpected condition has occurred while IOS is trying to forward an SNMP trap to the DMI subsystem |
polaris-dmi-infra |
LOG_STD_ACTION |
|
SNP_RP-3-UPDATE_FILTER_RESULTS |
3-Error |
Error in retrieving trap filter list: [chars] |
The number of trap filters that can be configured in the cisco-ia YANG model is limited. Please check the limit in the model and reduce the number of trap filters configured. |
polaris-dmi-infra |
LOG_STD_ACTION |
|
SNP_RP-3-UPDATE_FILTERS |
3-Error |
Error in updating trap filter list: [chars] |
An unexpected condition has occurred while IOS is trying to update the list of trap filters from the cisco-ia model |
polaris-dmi-infra |
LOG_STD_ACTION |
|
SNP_RP-3-UPDATE_PROCESS |
3-Error |
Error in creating cisco-ia update process |
Could not create IOS process to update the cisco-ia model |
polaris-dmi-infra |
LOG_STD_ACTION |
|
SONET-3-ALARMTIMERFAIL |
3-Error |
[chars] |
Alarm timer monitor process creation failed |
- |
LOG_STD_DDTS_TAC_DETAILS |
|
SONET-3-APSCOMM |
3-Error |
[chars]: [chars] |
APS errors related to failure of working-protect communication |
- |
LOG_STD_ACTION |
|
SONET-3-APSCOMMCHANGE |
3-Error |
[chars]: Link to [chars] channel reverts to PGP protocol version [dec] |
APS has reverted to a different version of the PGP protocol between working and protect routers. |
- |
"None - information only." |
|
SONET-3-APSCOMMEST |
3-Error |
[chars]: Link to [chars] channel established - PGP protocol version [dec] |
APS has established connectivity between working and protect routers. |
- |
"None - information only." |
|
SONET-3-APSCOMMLOST |
3-Error |
[chars]: Link to [chars] channel lost |
Connectivity between Working and Protect has been lost. APS operation can continue in degraded mode. |
- |
"Restore connectivity between working and protect routers." |
|
SONET-3-APSEVENT |
3-Error |
[chars]: APS event type error: event [dec] undefined |
APS software has malfunctioned |
- |
LOG_STD_ACTION |
|
SONET-3-APSHAHOLDTIME |
3-Error |
[chars]: [chars] |
Messages issued by HA APS when PGP holdtime is adjusted |
- |
"None - information only." |
|
SONET-3-APSNCHN |
3-Error |
APS Local request [dec] has no corresponding channel number |
APS software has malfunctioned. |
- |
LOG_STD_ACTION |
|
SONET-3-APSNOINTFC |
3-Error |
APS No interfaces available for IP connection |
APS requires an out-of-band path for inter-router communication. |
- |
"Configure an out-of-band path for inter-router APS " "communication" |
|
SONET-3-APSSYNCSECONDARY |
3-Error |
[dec]/[dec]: No hwidb |
New secondary RP unable to find device descriptor block corresponding to slot/unit specified by primary RP. |
- |
LOG_STD_ACTION |
|
SONET-3-BADAUTH |
3-Error |
[chars]: APS Bad authentication from [inet] |
APS software has detected unauthorized message. |
- |
"This message could result from improper configuration " "unauthorized access or packet corruption." LOG_STD_ACTION |
|
SONET-3-BADTCA |
3-Error |
TCA signal [dec] is invalid |
TCA software has malfunctioned. |
- |
LOG_STD_DDTS_TAC_DETAILS |
|
SONET-3-BADTCATH |
3-Error |
TCA threshold [dec] is not supported |
The specific TCA threshold is not supported |
- |
LOG_STD_DDTS_TAC_DETAILS |
|
SONET-3-DELAYTIMER |
3-Error |
[chars] |
Delay timer creation failure |
- |
LOG_STD_DDTS_TAC_DETAILS |
|
SONET-3-MISVER |
3-Error |
[chars]: APS version mismatch.\n\t WARNING: Loss of Working-Protect link can deselect both\n\t protect and working interfaces. [chars] router requires\n\t software upgrade for full protection. |
APS software has detected that either the working or protect router requires software upgrade. APS operation can continue prior to the upgrade. |
- |
"Upgrade specified router." |
|
SONET-3-NOBUFFER |
3-Error |
No buffer available for sending APS message |
No data buffer was available for sending APS message. |
- |
LOG_STD_RECUR_ACTION |
|
SONET-3-NOSOCKET |
3-Error |
Unable to open socket |
APS system unable to open a socket for communication purposes |
- |
LOG_STD_ACTION |
|
SONET-4-ALARM |
4-Warning |
[chars]: [chars] [chars] |
The specified SONET Alarm has been declared or released. |
- |
"Recommended action is to repair the source of the alarm." |
|
SONET-4-APSMM |
4-Warning |
[chars]: APS mode mismatch - [chars] |
There has been a unidirectional/bidirectional mismatch detected by the APS system |
- |
"It is recommended that the router configuration match the " "provisioned circuit." |
|
SONET-4-UPSR |
4-Warning |
Protection-Group [dec] [chars] [chars] |
There has been a protection switch on the protection group |
- |
"None - normal situation" |
|
SONET-6-APSMANPRO |
6-Information |
Manual APS switchover initiated for [chars] |
APS manual switchover is initialted |
- |
"None - normal situation." |
|
SONET-6-APSREFL |
6-Information |
[chars]: Remote reflection of APS status now [chars] |
APS software has detected a change in the reflected local APS status |
- |
"None - normal situation." |
|
SONET-6-APSREMSWI |
6-Information |
[chars]: Remote APS status now [chars] |
APS software has detected a change in the APS status of the remote interface |
- |
"None - normal situation." |
|
SONETIFMIB-3-NULLPTR |
3-Error |
NULL pointer at step = [dec] |
Attempted to initialize ifAlias for VT using a NULL pointer. |
- |
"LOG_STD_NO_ACTION" |
|
SONETIFMIB-3-OUTOFBOUND |
3-Error |
Out of bound values path=[dec]/tug2=[dec]/e1=[dec] |
Invalid values used while determining the ifAlias |
- |
"LOG_STD_NO_ACTION" |
|
SONETMIB-1-DELETE |
1-Alert |
could not delete interface if_index=[dec] |
The specified interface was not successfully dequeued. |
- |
LOG_STD_NO_ACTION |
|
SONETMIB-1-LOSTUPDATE |
1-Alert |
Lost raw stats update for if_index=[dec] |
- |
- |
"" |
|
SONETMIB-1-MALLOCNEW |
1-Alert |
Malloc failed for new interface=[dec] |
Unable to allocate enough memory to create SONET MIB structure\n\ for new interface. |
- |
LOG_STD_NO_ACTION |
|
SONETMIB-3-NULLCFGPTR |
3-Error |
NULL SONET MIB config pointer if_index=[dec] |
Attempted to initialize the SONET MIB using a NULL pointer. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SP_MONITOR-3-PEER_EXCEPTION |
3-Error |
SP_MONITOR peer has failed due to exception reset SP proc [[dec]/[dec]] |
SP_MONITOR messages have failed on the peer processor and\n\ the SP proc would be reset. |
- |
LOG_STD_NO_ACTION |
|
SP_MONITOR-3-PEER_FAILED |
3-Error |
SP_MONITOR peer process has failed to receive heartbeats reset SP proc [[dec]/[dec]] |
SP_MONITOR messages have failed on the peer process and\n\ the SP proc would be reset. |
- |
LOG_STD_NO_ACTION |
|
SP_MONITOR-3-TIMED_OUT |
3-Error |
SP_MONITOR messages have failed resetting [chars] [[dec]/[dec]] |
SP_MONITOR messages have failed and the SP proc would be reset. |
- |
LOG_STD_NO_ACTION |
|
SP_MONITOR-6-NOT_HEARD |
6-Information |
SP_MONITOR messages have not been heard for [dec] seconds [[dec]/[dec]] |
SP_MONITOR messages have not been heard for a significant amount of time. It\n\ is likely that a timeout will occur soon which will reset the SP processor. |
- |
LOG_STD_NO_ACTION |
|
SP-5-LDP |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
SPA_ATM_ENABLER-3-SPA_ATM_LICENSE_EULA_NOT_ACCEPTED |
3-Error |
\n********************************************************* \ \nWARNING: SPA ATM License is not yet activated. \ \nPlease configure 'license feature atm'\ \nand accept the EULA to activate the license. \ \n*********************************************************\n |
EULA is not accepted for the license |
ios-licensing-atg |
LOG_STD_ACTION |
|
SPA_BILBO-3-DPIDX_LKUP_ERR |
3-Error |
Failed to retrieve datapath identifier for interface [chars] |
The SPA driver is not able to retrieve the datapath identifier for the interface specified in the message. This indicates a software error. |
asr900-lotr-im |
LOG_STD_NO_ACTION |
|
SPA_BILBO-3-ID_ALLOC_ERR |
3-Error |
failed to allocate ID for TDM IM |
Failed to allocate ID for TDM IM. |
asr900-lotr-im |
LOG_STD_ACTION |
|
SPA_BILBO-3-ID_INIT |
3-Error |
failed to initialize TDM IM ID table |
Failed to initialize TDM IM ID table. |
asr900-lotr-im |
LOG_STD_ACTION |
|
SPA_BILBO-3-MSG_ENQUEUE_ERROR |
3-Error |
[chars] |
Failed to enqueue a message. |
asr900-lotr-im |
LOG_STD_ACTION |
|
SPA_BILBO-3-NULL_DATA_STRUCTURE |
3-Error |
[chars] |
A software error occured and SPA driver is not able to retrieve the data structure mentioned in the message. |
asr900-lotr-im |
LOG_STD_ACTION |
|
SPA_BILBO-3-NULL_SPA_PTR |
3-Error |
- |
The pointer to an SPA value is of a null value. |
spa-bilbot3-ds3 |
LOG_STD_SH_TECH_ACTION |
|
SPA_BILBO-3-PROCESS_FAIL |
3-Error |
process creation failed for [chars] |
The Periodic one second process creation failed. This indicates a software error. |
asr900-lotr-im |
LOG_STD_ACTION |
|
SPA_BILBO-3-TDL_SEND_FAIL |
3-Error |
common_str_empty_str |
Failed to send TDL message. |
asr900-lotr-im |
LOG_STD_ACTION |
|
SPA_BILBO-3-UNSUPPORTED_DATA |
3-Error |
common_str_empty_str |
A software error occured and SPA driver encounterd unsupported data mentioned in the message |
asr900-lotr-im |
LOG_STD_ACTION |
|
SPA_BILBO-3-VLAN_ID_NONZERO |
3-Error |
VLAN identifier is not zero before allocation for interface [chars] |
The SPA driver is seeing non zero VLAN identifier before allocating new vlan identifier for the interface specified in the message. This indicates a software error. |
asr900-lotr-im |
LOG_STD_NO_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-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-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_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_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_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-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-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-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-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_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_CHOC_DSX-3-AUTODNR |
3-Error |
[chars] failed for slot [dec] bay [dec] |
AUTODNR/USNDNR process has failed. The SPA and SIP are out of synchronization. This condition indicates a software error. |
spa-ct3-ds0 for CT3 spa-choc3-ds0 for CHOC-3/STM-1 |
LOG_STD_ACTION |
|
SPA_CHOC_DSX-3-BAD_SIZE_ERR |
3-Error |
SPA [dec]/[dec]: [dec] [chars] events on HDLC Controller were encountered. The SPA is being restarted.\n |
The SPA driver detected an error event on the HDLC controller. |
spa-ser-te1 for T1/E1 spa-ct3-ds0 for CT3 and spa-choc3-ds0 for CHOC-3/STM-1 |
"The SPA driver has encountered an error event on the SPA card. " "If the condition persists copy the error message exactly as " "it appears. Next research and attempt to resolve the issue using " "the SPA hardware troubleshooting documentation as well as the tools " "and utilities provided at " "http://www.cisco.com/public/support/tac/tools.shtml. If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a <CmdBold>tech-support<NoCmdBold> " "to your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
SPA_CHOC_DSX-3-COR_MEM_ERR |
3-Error |
SPA [dec]/[dec]: [dec] correctable [chars] memory errors encountered.\n |
The SPA driver detected a correctable memory error on the SPA card. |
spa-ser-te1 for T1/E1 spa-ct3-ds0 for CT3 and spa-choc3-ds0 for CHOC-3/STM-1 |
"The SPA has encountered a correctable memory error on the SPA card. " "The error has been corrected and normal processing should continue. " "The hexadecimal memory address of the most recent error is specified " "in the message text on the console or in the system log. " "If the condition persists or other errors are indicated for the SPA " "copy the error message exactly as it appears. Then power down and " "reseat the indicated SPA card. Next research and attempt " "to resolve the issue using the SPA hardware troubleshooting " "documentation as well as the tools and utilities provided at " "http://www.cisco.com/public/support/tac/tools.shtml. If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a <CmdBold>tech-support<NoCmdBold> " "to your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
SPA_CHOC_DSX-3-DPIDX_LKUP_ERR |
3-Error |
Failed to retrieve datapath identifier for interface [chars] |
The SPA driver is not able to retrieve the datapath identifier for the interface specified in the message. This indicates a software error. |
asr900-tdm-combo |
LOG_STD_NO_ACTION |
|
SPA_CHOC_DSX-3-EFC_ERROR |
3-Error |
EFC ERROR: [chars] - [chars] [dec] |
The SPA Extended Flow Control encountered an error |
spa-ct3-ds0 for CT3 spa-choc3-ds0 for CHOC-3/STM-1 |
LOG_STD_SH_TECH_ACTION |
|
SPA_CHOC_DSX-3-HDLC_CTRL_ERR |
3-Error |
SPA [dec]/[dec]: [dec] [chars] events on HDLC Controller were encountered. |
The SPA driver detected an error event on the HDLC Controller. |
spa-ser-te1 for T1/E1 spa-ct3-ds0 for CT3 and spa-choc3-ds0 for CHOC-3/STM-1 |
"The SPA driver has encountered an error event on the SPA card. " "If the condition persists copy the error message exactly as " "it appears. Next research and attempt to resolve the issue using " "the SPA hardware troubleshooting documentation as well as the tools " "and utilities provided at " "http://www.cisco.com/public/support/tac/tools.shtml. If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a <CmdBold>tech-support<NoCmdBold>" "to your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
SPA_CHOC_DSX-3-INVALID_IF_TYPE |
3-Error |
Invalid SPA type [dec] on [chars]. Port Number = [dec]. |
The software can not recognize the interface type |
spa-ct3-ds0 for CT3 spa-choc3-ds0 for CHOC-3/STM-1 |
LOG_STD_ACTION |
|
SPA_CHOC_DSX-3-INVLIAD_IF_INDEX |
3-Error |
Invalid interface index [dec] on slot/bay:[dec]/[dec]. Min. Index = [dec]. MAx. Index = [dec]. |
The index is not valid for the interface specified in the error message. |
spa-ct3-ds0 for CT3 spa-choc3-ds0 for CHOC-3/STM-1 |
LOG_STD_ACTION |
|
SPA_CHOC_DSX-3-LINK_TABLE_ERR |
3-Error |
[chars]: Could not create link table error [dec] |
Error creating link record table. Interfaces may not come up / pass traffic. |
spa-ser-te1 for T1/E1 spa-ct3-ds0 for CT3 and spa-choc3-ds0 for CHOC-3/STM-1 |
"If the ports on the SPA are not operating as expected power down and" "reseat the indicated SPA card. " "If the error messages persists copy the error message exactly as " "it appears. Next research and attempt to resolve the issue using " "the SPA hardware troubleshooting documentation as well as the tools " "and utilities provided at " "http://www.cisco.com/public/support/tac/tools.shtml. If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a <CmdBold>tech-support<NoCmdBold> " "to your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
SPA_CHOC_DSX-3-NODESTROYSUBBLOCK |
3-Error |
The [chars] subblock named [chars] was not removed |
IDB sub-blocks could not be removed during the unprovisioning of a channel. This condition indicates a software error. |
spa-ct3-ds0 for CT3 spa-choc3-ds0 for CHOC-3/STM-1 |
LOG_STD_ACTION |
|
SPA_CHOC_DSX-3-NULL_DATA_STRUCTURE |
3-Error |
Failed to create [chars] on slot/bay:[dec]/[dec]. Port Number = [dec]. |
The software resource can not be allocated for this hardware |
spa-ct3-ds0 for CT3 spa-choc3-ds0 for CHOC-3/STM-1 |
LOG_STD_ACTION |
|
SPA_CHOC_DSX-3-NULL_SPA_PTR |
3-Error |
- |
The pointer to an SPA value is of a null value. |
spa-ct3-ds0 for CT3 spa-choc3-ds0 for CHOC-3/STM-1 |
LOG_STD_SH_TECH_ACTION |
|
SPA_CHOC_DSX-3-NULL_VIRT_SPA_PTR |
3-Error |
[chars] |
Pointer to virtual SPA object is NULL in card prot grp. |
asr900-dsx-cp |
LOG_STD_SH_TECH_ACTION |
|
SPA_CHOC_DSX-3-PERIODIC_PROCESS |
3-Error |
[chars]: periodic process error [chars]. |
The SPA driver detected an error with the periodic processing routine. |
spa-ser-te1 |
"If the ports on the SPA are not operating as expected take it out of " "service by issuing command <CmdBold>hw-module subslot " "<noCmdBold><CmdArg>slot#/bay#<noCmdArg><CmdBold> stop<NoCmdBold> " "followed by <CmdBold>hw-module subslot " "<noCmdBold><CmdArg>slot#/bay#<noCmdArg><CmdBold> start<NoCmdBold> for " "the indicated SPA card. If the error messages persists copy the error " "message exactly as it appears. Next research and attempt to resolve the " "issue using the SPA hardware troubleshooting documentation as well as " "the tools and utilities provided at " "http://www.cisco.com/public/support/tac/tools.shtml. If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative." |
|
SPA_CHOC_DSX-3-PROCESS_FAIL |
3-Error |
process creation failed in [chars] spa type [chars] for [chars] |
The Periodic one second process creation failed. This indicates a software error. |
asr900-tdm-combo |
LOG_STD_ACTION |
|
SPA_CHOC_DSX-3-SEMAHOG |
3-Error |
SPA on [chars]: Semaphore Hog was encountered.Hogged by process [chars]\n |
The semaphore used by the IPC communication between host and the SPA was hogged by one process. This behavior would cause other processes fail to send commands down to the SPA. This might result improper operation. |
- |
"Please first stop all the traffic on the SPA and then " "reload the configuration by doing shut/no shut on " "the controllers. If the problem persists please power cycle the SPA. " "If the condition persists copy the error message exactly as " "it appears. Next research and attempt to resolve the issue using " "the SPA hardware troubleshooting documentation as well as the Bug Tookit " "on the Cisco web-site. If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a <CmdBold>tech-support<NoCmdBold> " "to your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
SPA_CHOC_DSX-3-SPA_CMD_RETURN_ERR |
3-Error |
SPA command [chars] return error [dec] |
The SPA returned an error status for a host command |
spa-ct3-ds0 for CT3 spa-choc3-ds0 for CHOC-3/STM-1 |
LOG_STD_SH_TECH_ACTION |
|
SPA_CHOC_DSX-3-SPA_CMD_SEND_ERR |
3-Error |
Failed to send [chars] command to SPA |
The host failed to send a command to SPA |
spa-ct3-ds0 for CT3 spa-choc3-ds0 for CHOC-3/STM-1 |
LOG_STD_SH_TECH_ACTION |
|
SPA_CHOC_DSX-3-SPA_SW_ERR |
3-Error |
SPA on [chars]: [chars] Software error was encountered.\n |
The SPA driver detected a Software error condition on the SPA card. This might result improper operation. |
- |
"The SPA driver has encountered a Software error. " "Please first reload the configuration by doing shut/no shut on " "the controllers. If the problem persists please power cycle the SPA. " "If the condition persists copy the error message exactly as " "it appears. Next research and attempt to resolve the issue using " "the Bug Toolkit on the Cisco web-site. If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a <CmdBold>tech-support<NoCmdBold> " "to your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
SPA_CHOC_DSX-3-SPI4_HW_ERR |
3-Error |
SPA on [chars]: [chars] Hardware error was encountered.\n |
The SPA driver detected a Hardware error condition on the SPA card. This might result in improper operation. |
- |
"The SPA driver has encountered a Hardware error on the SPA's SPI4 bus. " "Please power down and reseat the indicated SPA card. " "If the condition persists copy the error message exactly as " "it appears. Next research and attempt to resolve the issue using " "the SPA hardware troubleshooting documentation as well as the tools " "and utilities provided at " "http://www.cisco.com/public/support/tac/tools.shtml. If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a <CmdBold>tech-support<NoCmdBold> " "to your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
SPA_CHOC_DSX-3-T1CFG_ERROR |
3-Error |
Interface [chars] T3 [dec] T1 [dec] config command error cmd [dec] arg [dec] retval [dec] |
A command sent from the system to a linecard has failed. |
spa-ct3-ds0 for CT3 spa-choc3-ds0 for CHOC-3/STM-1 |
LOG_STD_SH_TECH_ACTION |
|
SPA_CHOC_DSX-3-T3CFG_ERROR |
3-Error |
Interface [chars] T3 [dec] config command error cmd [dec] arg [dec] retval [dec] |
A command sent from the system to a linecard has failed. |
spa-ct3-ds0 for CT3 spa-choc3-ds0 for CHOC-3/STM-1 |
LOG_STD_SH_TECH_ACTION |
|
SPA_CHOC_DSX-3-UNCOR_MEM_ERR |
3-Error |
SPA [dec]/[dec]: [dec] uncorrectable [chars] memory errors encountered.\n |
The SPA driver detected an uncorrectable memory error condition on the SPA card. Packet corruption may result. |
spa-ser-te1 for T1/E1 spa-ct3-ds0 for CT3 and spa-choc3-ds0 for CHOC-3/STM-1 |
"The SPA driver has encountered an uncorrectable memory error on the SPA " "card. The hexadecimal memory address of the most recent error is " "specified in the message text on the console or in the system log. " "Please power down and reseat the indicated SPA card. " "If the condition persists copy the error message exactly as " "it appears. Next research and attempt to resolve the issue using " "the SPA hardware troubleshooting documentation as well as the tools " "and utilities provided at " "http://www.cisco.com/public/support/tac/tools.shtml. If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a <CmdBold>tech-support<NoCmdBold> " "to your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
SPA_CHOC_DSX-3-UNCOR_PARITY_ERR |
3-Error |
SPA [dec]/[dec]: [dec] [chars] parity errors encountered.\n |
The SPA driver detected an uncorrectable parity error condition on the SPA card. Packet corruption may result. |
spa-ser-te1 for T1/E1 spa-ct3-ds0 for CT3 and spa-choc3-ds0 for CHOC-3/STM-1 |
"Please power down and reseat the indicated SPA card. " "If the condition persists copy the error message exactly as " "it appears. Next research and attempt to resolve the issue using " "the SPA hardware troubleshooting documentation as well as the tools " "and utilities provided at " "http://www.cisco.com/public/support/tac/tools.shtml. If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a <CmdBold>tech-support<NoCmdBold> " "to your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
SPA_CHOC_DSX-3-UNKNOWN_CMD |
3-Error |
Unknown [chars] command recieved on slot/bay:[dec]/[dec]. Command Type = [dec] |
An unknown command was recieved by the SPA card carrier |
spa-ct3-ds0 for CT3 spa-choc3-ds0 for CHOC-3/STM-1 |
LOG_STD_ACTION |
|
SPA_CHOC_DSX-3-VCCFG_ERROR |
3-Error |
Interface [chars] config command error cmd [dec] arg [dec] retval [dec] |
A command sent from the system to a linecard has failed. |
spa-ct3-ds0 for CT3 spa-choc3-ds0 for CHOC-3/STM-1 |
"This is an internal software error. Decode the " "traceback and get the output of the <CmdBold>show " "logging<NoCmdBold> command on RP and SIP and check " "if there are any errors being reported. Try to " "recreate the problem to see if there is a " "consistant method to recreate. Check the Bug " "Toolkit before contacting TAC. When contacting TAC " "provide the above information along with the " "output of the <CmdBold>show tech-support<NoCmdBold> " "command." |
|
SPA_CHOC_DSX-4-UNPROV_FAIL |
4-Warning |
Interface [chars] unprovisioning failed: [chars] |
The system failed to respond to an unprovisioning command. A hidden VLAN could not be deleted within a 2 second timeout window. This condition may be caused by a system that is too busy or by a FIB IPC failure. The line card driver code will attempt to delete the hidden VLAN. |
spa-ct3-ds0 for CT3 spa-choc3-ds0 for CHOC-3/STM-1 |
"If processing continues normally no action is required. If " "system operation is adversely affected " LOG_STD_ACTION |
|
SPA_CHOC_DSX-5-CHNL_GRP_ADD |
5-Notice |
Channel Group created on the interface [chars]\n |
Channel Group created on the serial interface. |
asr900-3g-ms |
LOG_STD_ACTION |
|
SPA_CHOC_DSX-5-CHNL_GRP_DEL |
5-Notice |
Channel Group delete from the interface [chars]\n |
Channel Group deleted from the serial interface. |
asr900-3g-ms |
LOG_STD_ACTION |
|
SPA_CHOCX_CWRP-1-ALLOCFAIL |
1-Alert |
OC3/STM1 [dec]/[dec] [chars] allocation failure |
CHOCX controller or channel memory allocation failure |
c7600-sip-200 |
"This is a internal software error. Decode the " "traceback. Enable <CmdBold>debug hw-module subslot " "<slot>/<bay> oir plugin<NoCmdBold> when the problem " "is happening. Check Bug Toolkit before calling the " "TAC. When calling the TAC please provide the above" "information along with output of <CmdBold>show " "logging<NoCmdBold> and the output of <CmdBold>show " "tech<NoCmdBold> details." |
|
SPA_CHOCX_CWRP-3-APS_CMD_FAIL |
3-Error |
Failed to send APS command [hec] to [chars] retcode [hec] |
APS command sending failed |
c7600-sip-200 |
"This is a internal software error. If this " "error happened while configuring APS try " "reconfiguring the interface. If the error " "persists or occurred during normal operation " "decode the traceback and " LOG_STD_ACTION |
|
SPA_CHOCX_CWRP-3-CORRUPT |
3-Error |
Corrupt configuration unsupported [chars] [dec] encountered |
The OC3/STM1 RP driver running configuration is corrupt |
c7600-sip-200 |
"This is a internal software error. Decode the " "traceback and get the output of <CmdBold>show " "running-config<NoCmdBold>. Check Bug Toolkit " "before calling the TAC. When calling the TAC " "please provide the above information along with " "the output of <CmdBold>show tech<NoCmdBold> " "details" |
|
SPA_CHOCX_CWRP-3-FRR_ERROR |
3-Error |
Error in handling FRR: [chars] [chars] [hec] [hec] |
Error in FRR processing |
c7600-sip-common |
"This is a internal software error. If this " "error happened while configuring FRR try " "reconfiguring the interface. If the error " "persists or occurred during normal operation " "decode the traceback and " LOG_STD_ACTION |
|
SPA_CHOCX_CWRP-3-NULL_SUBBLOCK |
3-Error |
Null ssb for [chars] |
The hwidb subblock is NULL |
c7600-sip-200 |
"This is a internal software error. Decode the " "traceback and get the output of <CmdBold>show " "running-config<NoCmdBold>. Check Bug Toolkit " "before calling the TAC. When calling the TAC " "please provide the above information along with " "the output of <CmdBold>show running<NoCmdBold> " "and <CmdBold>show tech<NoCmdBold> details." |
|
SPA_CHOCX_CWRP-3-PLUGIN_ERR |
3-Error |
[chars] |
The RP plugin encountered an error during one of the Plugin calls |
c7600-sip-200 |
"This is a internal software error. Decode the " "traceback. Enable <CmdBold>debug hw-module subslot " "<slot>/<bay> oir plugin<NoCmdBold> when the problem " "is happening. Check Bug Toolkit before calling the " "TAC. When calling the TAC please provide the above " "information along with the output of <CmdBold>show " "logging<NoCmdBold> and the output of <CmdBold>show " "tech<NoCmdBold> details." |
|
SPA_CHOCX_CWRP-3-TIMEOUT |
3-Error |
Interface [chars]: [chars] |
The CHOCX RP driver queries the LC for SONET information the LC didn't reply. |
c7600-sip-200 |
"This is a internal software error. Decode the " "traceback. Enable <CmdBold>debug hw-module subslot " "<slot>/<bay> command<NoCmdBold>. Check Bug Toolkit " "before calling the TAC. When calling the TAC " "please provide the above information along with the " "output of <CmdBold>show logging<NoCmdBold> and the " "output of <CmdBold>show tech<NoCmdBold details." |
|
SPA_CHOCX_CWRP-5-DEF_SUBRATE |
5-Notice |
[chars] [chars] |
Remote subrate configuration changed |
c7600-sip-200 |
"Inform the network operator that subrate " "configuration changed by remote end" |
|
SPA_CHOCX_CWRP-5-PATH_UPDOWN |
5-Notice |
Path [chars] changed state to [chars] |
A Sonet high order path changed its state. |
c7600-sip-200 |
"This is a internal software error. Decode the " "traceback and get the output of <CmdBold>show " "controller sonet<NoCmdBold>. Look into this " "output to see if there are any alarms being " "reported at the path level. Check Bug Toolkit " "before calling the TAC. When calling the TAC " "please provide the above information along with " "the output of <CmdBold>show tech<NoCmdBold> " "details" |
|
SPA_CHOCX_CWRP-5-T3_UPDOWN |
5-Notice |
T3 [chars] changed state to [chars] |
A T3 within STS1 changed its state. |
c7600-sip-200 |
"This is a internal software error. Decode the " "traceback and get the output of <CmdBold>show " "controller sonet<NoCmdBold>. Look into this " "output to see if there are any alarms being " "reported at the T3 level. Check Bug Toolkit " "before calling the TAC. When calling the TAC " "please provide the above information along with " "the output of <CmdBold>show tech<NoCmdBold> " "details" |
|
SPA_CHOCX_MCPRP-1-ALLOCFAIL |
1-Alert |
OC3/STM1 [dec]/[dec] [chars] allocation failure |
CHOCX controller or channel memory allocation failure |
asr1k-spa-chstm1 |
"This is a internal software error. Decode the " "traceback. Enable <CmdBold>debug hw-module subslot " "<slot>/<bay> oir plugin<NoCmdBold> when the problem " "is happening. Check Bug Toolkit before calling the " "TAC. When calling the TAC please provide the above" "information along with output of <CmdBold>show " "logging<NoCmdBold> and the output of <CmdBold>show " "tech<NoCmdBold> details." |
|
SPA_CHOCX_MCPRP-3-APS_CMD_FAIL |
3-Error |
Failed to send APS command [hec] to [chars] retcode [hec] |
APS command sending failed |
asr1k-spa-chstm1 |
"This is a internal software error. If this " "error happened while configuring APS try " "reconfiguring the interface. If the error " "persists or occurred during normal operation " "decode the traceback and " LOG_STD_ACTION |
|
SPA_CHOCX_MCPRP-3-CORRUPT |
3-Error |
Corrupt configuration unsupported [chars] [dec] encountered |
The OC3/STM1 RP driver running configuration is corrupt |
asr1k-spa-chstm1 |
"This is a internal software error. Decode the " "traceback and get the output of <CmdBold>show " "running-config<NoCmdBold>. Check Bug Toolkit " "before calling the TAC. When calling the TAC " "please provide the above information along with " "the output of <CmdBold>show tech<NoCmdBold> " "details" |
|
SPA_CHOCX_MCPRP-3-FRR_ERROR |
3-Error |
Error in handling FRR: [chars] [chars] [hec] [hec] |
Error in FRR processing |
asr1k-spa-chstm1 |
"This is a internal software error. If this " "error happened while configuring FRR try " "reconfiguring the interface. If the error " "persists or occurred during normal operation " "decode the traceback and " LOG_STD_ACTION |
|
SPA_CHOCX_MCPRP-3-NULL_SUBBLOCK |
3-Error |
Null ssb for [chars] |
The hwidb subblock is NULL |
asr1k-spa-chstm1 |
"This is a internal software error. Decode the " "traceback and get the output of <CmdBold>show " "running-config<NoCmdBold>. Check Bug Toolkit " "before calling the TAC. When calling the TAC " "please provide the above information along with " "the output of <CmdBold>show running<NoCmdBold> " "and <CmdBold>show tech<NoCmdBold> details." |
|
SPA_CHOCX_MCPRP-3-PLUGIN_ERR |
3-Error |
[chars] |
The RP plugin encountered an error during one of the Plugin calls |
asr1k-spa-chstm1 |
"This is a internal software error. Decode the " "traceback. Enable <CmdBold>debug hw-module subslot " "<slot>/<bay> oir plugin<NoCmdBold> when the problem " "is happening. Check Bug Toolkit before calling the " "TAC. When calling the TAC please provide the above " "information along with the output of <CmdBold>show " "logging<NoCmdBold> and the output of <CmdBold>show " "tech<NoCmdBold> details." |
|
SPA_CHOCX_MCPRP-3-TIMEOUT |
3-Error |
Interface [chars]: [chars] |
The CHOCX RP driver queries the LC for SONET information the LC didn't reply. |
asr1k-spa-chstm1 |
"This is a internal software error. Decode the " "traceback. Enable <CmdBold>debug hw-module subslot " "<slot>/<bay> command<NoCmdBold>. Check Bug Toolkit " "before calling the TAC. When calling the TAC " "please provide the above information along with the " "output of <CmdBold>show logging<NoCmdBold> and the " "output of <CmdBold>show tech<NoCmdBold details." |
|
SPA_CHOCX_MCPRP-5-DEF_SUBRATE |
5-Notice |
[chars] [chars] |
Remote subrate configuration changed |
asr1k-spa-chstm1 |
"Inform the network operator that subrate " "configuration changed by remote end" |
|
SPA_CHOCX_MCPRP-5-PATH_UPDOWN |
5-Notice |
Path [chars] changed state to [chars] |
A Sonet high order path changed its state. |
asr1k-spa-chstm1 |
"This is a internal software error. Decode the " "traceback and get the output of <CmdBold>show " "controller sonet<NoCmdBold>. Look into this " "output to see if there are any alarms being " "reported at the path level. Check Bug Toolkit " "before calling the TAC. When calling the TAC " "please provide the above information along with " "the output of <CmdBold>show tech<NoCmdBold> " "details" |
|
SPA_CHOCX_MCPRP-5-T3_UPDOWN |
5-Notice |
T3 [chars] changed state to [chars] |
A T3 within STS1 changed its state. |
asr1k-spa-chstm1 |
"This is a internal software error. Decode the " "traceback and get the output of <CmdBold>show " "controller sonet<NoCmdBold>. Look into this " "output to see if there are any alarms being " "reported at the T3 level. Check Bug Toolkit " "before calling the TAC. When calling the TAC " "please provide the above information along with " "the output of <CmdBold>show tech<NoCmdBold> " "details" |
|
SPA_CHOCX_W2RP-1-ALLOCFAIL |
1-Alert |
- |
- |
- |
- |
|
SPA_CHOCX_W2RP-3-APS_CMD_FAIL |
3-Error |
- |
- |
- |
- |
|
SPA_CHOCX_W2RP-3-CORRUPT |
3-Error |
- |
- |
- |
- |
|
SPA_CHOCX_W2RP-3-FRR_ERROR |
3-Error |
- |
- |
- |
- |
|
SPA_CHOCX_W2RP-3-NULL_SUBBLOCK |
3-Error |
- |
- |
- |
- |
|
SPA_CHOCX_W2RP-3-PLUGIN_ERR |
3-Error |
[chars] |
The RP plugin encountered an error during one of the Plugin calls |
c7600-sip-200 |
"This is a internal software error. Decode the " "traceback. Enable <CmdBold>debug hw-module subslot " "<slot>/<bay> oir plugin<NoCmdBold> when the problem " "is happening. Check Bug Toolkit before calling the " "TAC. When calling the TAC please provide the above " "information along with the output of <CmdBold>show " "logging<NoCmdBold> and the output of <CmdBold>show " "tech<NoCmdBold> details." |
|
SPA_CHOCX_W2RP-3-TIMEOUT |
3-Error |
- |
- |
- |
- |
|
SPA_CHOCX_W2RP-5-DEF_SUBRATE |
5-Notice |
[chars] [chars] |
Remote subrate configuration changed |
c7600-sip-200 |
"Inform the network operator that subrate " "configuration changed by remote end" |
|
SPA_CHOCX_W2RP-5-PATH_UPDOWN |
5-Notice |
- |
- |
- |
- |
|
SPA_CHOCX_W2RP-5-T3_UPDOWN |
5-Notice |
T3 [chars] changed state to [chars] |
A T3 within STS1 changed its state. |
c7600-sip-200 |
"This is a internal software error. Decode the " "traceback and get the output of <CmdBold>show " "controller sonet<NoCmdBold>. Look into this " "output to see if there are any alarms being " "reported at the T3 level. Check Bug Toolkit " "before calling the TAC. When calling the TAC " "please provide the above information along with " "the output of <CmdBold>show tech<NoCmdBold> " "details" |
|
SPA_CHOCX-3-CHOCX_NAMESTRING_ERROR |
3-Error |
failed to get [chars] namestring |
Error in retrieving namestring of a specified Controller/IDB |
asr900-tdm-combo |
"This is a internal software error. If the error persists or occurred " "during normal operation decode the traceback and " LOG_STD_ACTION |
|
SPA_CHOCX-3-CORRUPT |
3-Error |
Corrupt configuration unsupported [chars] [dec] encountered |
The OC3/STM1 RP driver running configuration is corrupted. |
spa-choc3-ds0 |
SPA_CHOCX_INTERNAL_SW_ERROR_ACTION |
|
SPA_CHOCX-3-CREATE_FAIL |
3-Error |
Failed to create [chars] : slot/bay:[dec]/[dec] |
The channelized SPA controller descriptor block creation failed. Check the amount of available system memory. |
spa-choc3-ds0 |
LOG_STD_SH_TECH_ACTION |
|
SPA_CHOCX-3-ERROR |
3-Error |
Failed to create for [chars] : slot/bay:[dec]/[dec] |
The channelized SPA controller encountered an error. |
spa-choc3-ds0 |
"Check the memory availabe in system and " LOG_STD_SH_TECH_ACTION |
|
SPA_CHOCX-3-FATAL_ERROR |
3-Error |
Fatal error for [chars] : slot/bay:[dec]/[dec] |
The channelized SPA controller encountered a fatal error. |
spa-choc3-ds0 |
LOG_STD_SH_TECH_ACTION |
|
SPA_CHOCX-3-FRR_ERROR |
3-Error |
Error in handling FRR: [chars] [chars] [hec] [hec] |
Error in FRR processing. |
spa-choc3-ds0 |
"This is a internal software error. If this error happened while " "configuring FRR try reconfiguring the interface. If the error " "persists or occurred during normal operation decode the traceback " "and " LOG_STD_ACTION |
|
SPA_CHOCX-3-INTFC_FAILED |
3-Error |
Channel provisioning failed for [chars] |
Channel could not be provisioned on SPA for this interface interface corresoponding to that channel has been moved to down state. If this interface was provisoned using the user interface then it may not appear in the interface list. |
spa-choc3-ds0 |
SPA_CHOCX_INTERNAL_SW_ERROR_ACTION |
|
SPA_CHOCX-3-INVALID_SPA_TYPE |
3-Error |
Invalid SPA type : slot/bay:[dec]/[dec] spa_type=[dec]. |
The channelized SPA type cannot be recognized by the version of Cisco IOS software currently running on the system. |
spa-choc3-ds0 |
"Upgrade your system to a version of Cisco IOS software that supports " "this SPA type." |
|
SPA_CHOCX-3-NULL |
3-Error |
[chars] |
The NULL pointer was detected when getting the data structure. |
spa-choc3-ds0 |
SPA_CHOCX_ENABLE_DEBUG_ACTION |
|
SPA_CHOCX-3-NULL_INSTANCE |
3-Error |
Null [chars] instance for [chars] : slot/bay:[dec]/[dec] |
The instance pointer is NULL when getting data structure. |
spa-choc3-ds0 |
SPA_CHOCX_INTERNAL_SW_ERROR_ACTION |
|
SPA_CHOCX-3-NULL_SUBBLOCK |
3-Error |
Null ssb for [chars] |
The hwidb subblock is NULL. |
spa-choc3-ds0 |
SPA_CHOCX_INTERNAL_SW_ERROR_ACTION |
|
SPA_CHOCX-3-RETURN_ERROR |
3-Error |
Return error for [chars]: return_value=[dec] |
Return error code received. |
spa-choc3-ds0 |
SPA_CHOCX_INTERNAL_SW_ERROR_ACTION |
|
SPA_CHOCX-3-SONET_ALARM_PROC_ERR |
3-Error |
[chars] Error has occurred while processing in the sonet alarm-proc |
Either free/create of the memory failed in SONET alarm proc |
- |
- |
|
SPA_CHOCX-3-UNKNOWN_OPTION |
3-Error |
Received unknown [chars]: option=[dec] |
Unknown option received. |
spa-choc3-ds0 |
SPA_CHOCX_INTERNAL_SW_ERROR_ACTION |
|
SPA_CHOCX-3-XFP_UNSUPPORTED |
3-Error |
[dec]/[dec]/[dec]: [chars] detected/inserted is not supported |
Unsupported XFP has been detected or inserted in a port in Channelized SPA. |
spa-choc3-ds0 |
"Remove the unsupported XFP/SFP and replace it with supported one." |
|
SPA_CHOCX-5-CEM_COUNT_WARNING |
5-Notice |
With Scaled CEM recommended value of LDP discovery timeout is 180 seconds before SSO. Current Scale: [dec] |
User Recommendation |
- |
- |
|
SPA_CHOCX-5-DEF_SUBRATE |
5-Notice |
[chars] [chars] |
Remote subrate configuration changed. |
spa-choc3-ds0 |
"Inform the network operator that subrate configuration was changed " "by remote end." |
|
SPA_CHOCX-6-SONET_ALARM |
6-Information |
[chars] [chars] [chars] [chars] [chars] |
This message is generated whenever a sonet alarm is |
- |
LOG_STD_NO_ACTION |
|
SPA_CHOCX-6-XFP_OK |
6-Information |
[dec]/[dec]/[dec]: [chars] detected/inserted |
XFP has been detected or inserted in a port in Channelized SPA. |
spa-choc3-ds0 |
"This is a information message no action required" |
|
SPA_CHOCX-6-XFP_REMOVED |
6-Information |
[dec]/[dec]/[dec] |
XFP removed from a port in Channelized SPA |
spa-choc3-ds0 |
"This is a information message no action required" |
|
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-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-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-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-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_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_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-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-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-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-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-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-5-CANTGET |
5-Notice |
Cannot get SPA client IPC port |
SPA console sub-block is not initialized properly. |
- |
LOG_STD_ACTION |
|
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-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-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-CANTSET |
5-Notice |
Cannot set 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-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-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_CT3-3-INVALID_SPA_TYPE |
3-Error |
Invalid SPA type : slot/bay:[dec]/[dec] spa_type=[dec]. |
The Channelized T3 SPA type cannot be recognized by the version of Cisco IOS software currently running on the system. |
spa-ct3-ds0 |
"Upgrade your system to the latest version of Cisco " "IOS software in your release train. If you require " "further assistance " LOG_STD_SH_TECH_ACTION |
|
SPA_CT3-3-PROCESS_FAIL |
3-Error |
process creation failed for [chars] |
A command could not be processed because of a process creation failure. |
spa-ct3-ds0 |
LOG_STD_ACTION |
|
SPA_CT3-3-SUBRATE_FPGA_DL_FAILED |
3-Error |
[chars]: Failed to download the subrate FPGA image. |
The indicated SPA was not able to download the subrate FPGA image during card initialization sequence. The image might be corrupted and the system will try to recover from this error by upgrading the image. |
spa-ct3-ds0 |
"If the system cannot recover from this error automatically after a few " "attempts it will power-off the affected SPA. In this case copy the " "error message exactly as it appears and gather the output of the " "<CmdBold>show hw-module subslot<NoCmdBold> <CmdArg>slot/subslot<NoCmdArg>" " <CmdBold>fpd<NoCmdBold> and <CmdBold>show hw-module subslot<NoCmdBold> " "<CmdArg>slot/subslot<NoCmdArg> <CmdBold>oir<NoCmdBold> commands then " "contact your technical support representative with the gathered " "information." |
|
SPA_CT3-5-DEF_SUBRATE |
5-Notice |
[chars] [chars] |
Remote subrate configuration changed |
spa-ct3-ds0 |
"Inform the network operator that subrate " "configuration changed by remote end" |
|
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-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_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_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_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_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_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_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_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_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_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_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_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-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-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_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_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_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_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_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_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_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_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_DENETHOR-3-DPIDX_LKUP_ERR |
3-Error |
Failed to retrieve datapath identifier for interface [chars] |
The SPA driver is not able to retrieve the datapath identifier for the interface specified in the message. This indicates a software error. |
asr900-lotr-im |
LOG_STD_NO_ACTION |
|
SPA_DENETHOR-3-ID_ALLOC_ERR |
3-Error |
failed to allocate ID for TDM IM |
Failed to allocate ID for TDM IM. |
asr900-lotr-im |
LOG_STD_ACTION |
|
SPA_DENETHOR-3-ID_INIT |
3-Error |
failed to initialize TDM IM ID table |
Failed to initialize TDM IM ID table. |
asr900-lotr-im |
LOG_STD_ACTION |
|
SPA_DENETHOR-3-MSG_ENQUEUE_ERROR |
3-Error |
[chars] |
Failed to enqueue a message. |
asr900-lotr-im |
LOG_STD_ACTION |
|
SPA_DENETHOR-3-NULL_DATA_STRUCTURE |
3-Error |
[chars] |
A software error occured and SPA driver is not able to retrieve the data structure mentioned in the message. |
asr900-lotr-im |
LOG_STD_ACTION |
|
SPA_DENETHOR-3-PROCESS_FAIL |
3-Error |
process creation failed for [chars] |
The Periodic one second process creation failed. This indicates a software error. |
asr900-lotr-im |
LOG_STD_ACTION |
|
SPA_DENETHOR-3-TDL_SEND_FAIL |
3-Error |
common_str_empty_str |
Failed to send TDL message. |
asr900-lotr-im |
LOG_STD_ACTION |
|
SPA_DENETHOR-3-UNSUPPORTED_DATA |
3-Error |
common_str_empty_str |
A software error occured and SPA driver encounterd unsupported data mentioned in the message |
asr900-lotr-im |
LOG_STD_ACTION |
|
SPA_DENETHOR-3-VLAN_ID_NONZERO |
3-Error |
VLAN identifier is not zero before allocation for interface [chars] |
The SPA driver is seeing non zero VLAN identifier before allocating new vlan identifier for the interface specified in the message. This indicates a software error. |
asr900-lotr-im |
LOG_STD_NO_ACTION |
|
SPA_DSPRM-3-DSPALARM |
3-Error |
Received alarm indication from dsp [dec]/[dec]/[dec]. |
Operational error detected in DSP. |
spa-dsp |
"Reload the SPA card and if the problem persists " LOG_STD_ACTION |
|
SPA_DSPRM-3-DSPALARMINFO |
3-Error |
[chars] |
DSP Alarm Data |
spa-dsp |
"Reload the SPA card and if the problem persists " LOG_STD_ACTION |
|
SPA_DSPRM-3-INSUFFICIENT |
3-Error |
Insufficient memory for [chars] |
Insufficient memory for SPA-DSP DSPRM operation |
spa-dsp |
"Enter the <CmdBold>show memory summary<NoCmdBold> command to attempt to\n\ determine the cause of the error. " LOG_STD_REDUCE_ACTION |
|
SPA_DSPRM-5-RESTART |
5-Notice |
DSP [dec]/[dec]/[dec] is restarted |
DSP device restarted |
- |
LOG_STD_NO_ACTION |
|
SPA_DSPRM-5-UPDOWN |
5-Notice |
DSP [dec]/[dec]/[dec] is [chars] |
DSP device changed state up/down |
- |
LOG_STD_NO_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-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-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-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-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-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-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-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-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-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-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-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-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-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-SW_ERROR |
3-Error |
NULL |
- |
spa-infra |
LOG_STD_ACTION |
|
SPA_EEPROM-3-SW_ERROR |
3-Error |
NULL |
- |
spa-infra |
LOG_STD_ACTION |
|
SPA_EEPROM-3-SW_ERROR |
3-Error |
NULL |
- |
spa-infra |
LOG_STD_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-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-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-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-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-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-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-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-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_ELBORON-3-CORRUPT |
3-Error |
Corrupt configuration unsupported [chars] [dec] encountered |
The OC3/STM1 RP driver running configuration is corrupted. |
asr900-tdm-combo |
SPA_ELBORON_INTERNAL_SW_ERROR_ACTION |
|
SPA_ELBORON-3-CREATE_FAIL |
3-Error |
Failed to create [chars] : slot/bay:[dec]/[dec] |
The channelized SPA controller descriptor block creation failed. Check the amount of available system memory. |
asr900-tdm-combo |
LOG_STD_SH_TECH_ACTION |
|
SPA_ELBORON-3-DCC_FAILURE |
3-Error |
Failed to retrieve DCC info for [dec]/[dec]/[dec] |
\n The DCC info could not be retrieved |
asr900-tdm-combo |
SPA_ELBORON_INTERNAL_SW_ERROR_ACTION |
|
SPA_ELBORON-3-ERROR |
3-Error |
Failed to create for [chars] : slot/bay:[dec]/[dec] |
The 1Z 8S SPA/IM controller encountered an error. |
asr900-tdm-combo |
"Check the memory availabe in system and " LOG_STD_SH_TECH_ACTION |
|
SPA_ELBORON-3-FATAL_ERROR |
3-Error |
Fatal error for [chars] : slot/bay:[dec]/[dec] |
The channelized SPA controller encountered a fatal error. |
asr900-tdm-combo |
LOG_STD_SH_TECH_ACTION |
|
SPA_ELBORON-3-FRR_ERROR |
3-Error |
Error in handling FRR: [chars] [chars] [hec] [hec] |
Error in FRR processing. |
asr900-tdm-combo |
"This is a internal software error. If this error happened while " "configuring FRR try reconfiguring the interface. If the error " "persists or occurred during normal operation decode the traceback " "and " LOG_STD_ACTION |
|
SPA_ELBORON-3-INTFC_FAILED |
3-Error |
Channel provisioning failed for [chars] |
Channel could not be provisioned on SPA for this interface interface corresoponding to that channel has been moved to down state. If this interface was provisoned using the user interface then it may not appear in the interface list. |
asr900-tdm-combo |
SPA_ELBORON_INTERNAL_SW_ERROR_ACTION |
|
SPA_ELBORON-3-INVALID_MAX_VC |
3-Error |
for[chars] |
invalid max vc for IM |
asr900-tdm-combo |
LOG_STD_SH_TECH_ACTION |
|
SPA_ELBORON-3-INVALID_SPA_TYPE |
3-Error |
Invalid SPA type : slot/bay:[dec]/[dec] spa_type=[dec]. |
The channelized SPA type cannot be recognized by the version of Cisco IOS software currently running on the system. |
asr900-tdm-combo |
"Upgrade your system to a version of Cisco IOS software that supports " "this SPA type." |
|
SPA_ELBORON-3-NULL |
3-Error |
[chars] |
The NULL pointer was detected when getting the data structure. |
asr900-tdm-combo |
SPA_ELBORON_ENABLE_DEBUG_ACTION |
|
SPA_ELBORON-3-NULL_CDB |
3-Error |
payload CDB is NULL for [dec]/[dec]/[dec] |
The payload cdb for the port is Null. |
asr900-tdm-combo |
SPA_ELBORON_INTERNAL_SW_ERROR_ACTION |
|
SPA_ELBORON-3-NULL_ETH_SUBBLOCK |
3-Error |
Ethernet subblock is null for [dec]/[dec] |
The ethernet subblock is NULL |
asr900-tdm-combo |
SPA_ELBORON_INTERNAL_SW_ERROR_ACTION |
|
SPA_ELBORON-3-NULL_INSTANCE |
3-Error |
Null [chars] instance for slot/bay/port:[dec]/[dec]/[dec] |
The instance pointer is NULL when getting data structure. |
asr900-tdm-combo |
SPA_ELBORON_INTERNAL_SW_ERROR_ACTION |
|
SPA_ELBORON-3-NULL_OPTICS_CDB |
3-Error |
Optic CDB is NULL for [dec]/[dec]/[dec] |
The optics cdb for the port is Null. |
asr900-tdm-combo |
SPA_ELBORON_INTERNAL_SW_ERROR_ACTION |
|
SPA_ELBORON-3-NULL_OPTICS_HWIDB |
3-Error |
Optic HWIDB is NULL for [dec]/[dec]/[dec] |
The optics hwidb for the port is Null. |
asr900-tdm-combo |
SPA_ELBORON_INTERNAL_SW_ERROR_ACTION |
|
SPA_ELBORON-3-NULL_SPA_PTR |
3-Error |
- |
Pointer to a SPA object is NULL. |
asr900-tdm-combo |
LOG_STD_SH_TECH_ACTION |
|
SPA_ELBORON-3-NULL_SUBBLOCK |
3-Error |
Null ssb for [chars] |
The hwidb subblock is NULL. |
asr900-tdm-combo |
SPA_CHOCX_INTERNAL_SW_ERROR_ACTION |
|
SPA_ELBORON-3-NULL_VC_INST |
3-Error |
for[chars] |
Pointer to VC INST is NULL. |
asr900-tdm-combo |
LOG_STD_SH_TECH_ACTION |
|
SPA_ELBORON-3-RETURN_ERROR |
3-Error |
Return error for [chars]: return_value=[dec] |
Return error code received. |
asr900-tdm-combo |
SPA_ELBORON_INTERNAL_SW_ERROR_ACTION |
|
SPA_ELBORON-3-UNKNOWN_OPTION |
3-Error |
Received unknown [chars]: option=[dec] |
Unknown option received. |
asr900-tdm-combo |
SPA_ELBORON_INTERNAL_SW_ERROR_ACTION |
|
SPA_ELBORON-5-DEF_SUBRATE |
5-Notice |
[chars] [chars] |
Remote subrate configuration changed. |
asr900-tdm-combo |
"Inform the network operator that subrate configuration was changed " "by remote end." |
|
SPA_ELBORON-5-SPA_MODE_IS |
5-Notice |
spa_mode of [dec]/[dec] is [chars] |
\n spa_mode is |
asr900-tdm-combo |
SPA_ELBORON_INTERNAL_SW_ERROR_ACTION |
|
SPA_ELBORON-6-XFP_OK |
6-Information |
[dec]/[dec]/[dec]: [chars] detected/inserted |
XFP has been detected or inserted in a port in Channelized SPA. |
asr900-tdm-combo |
"This is a information message no action required" |
|
SPA_EOMER-3-CORRUPT |
3-Error |
Corrupt configuration unsupported [chars] [dec] encountered |
The OC3/STM1 RP driver running configuration is corrupted. |
asr900-tdm-combo |
SPA_EOMER_INTERNAL_SW_ERROR_ACTION |
|
SPA_EOMER-3-CREATE_FAIL |
3-Error |
Failed to create [chars] : slot/bay:[dec]/[dec] |
The channelized SPA controller descriptor block creation failed. Check the amount of available system memory. |
asr900-tdm-combo |
LOG_STD_SH_TECH_ACTION |
|
SPA_EOMER-3-DCC_FAILURE |
3-Error |
Failed to retrieve DCC info for [dec]/[dec]/[dec] |
\n The DCC info could not be retrieved |
asr900-tdm-combo |
SPA_EOMER_INTERNAL_SW_ERROR_ACTION |
|
SPA_EOMER-3-ERROR |
3-Error |
Failed to create for [chars] : slot/bay:[dec]/[dec] |
The SPA/IM controller encountered an error. |
asr900-tdm-combo |
"Check the memory availabe in system and " LOG_STD_SH_TECH_ACTION |
|
SPA_EOMER-3-FATAL_ERROR |
3-Error |
Fatal error for [chars] : slot/bay:[dec]/[dec] |
The channelized SPA controller encountered a fatal error. |
asr900-tdm-combo |
LOG_STD_SH_TECH_ACTION |
|
SPA_EOMER-3-FRR_ERROR |
3-Error |
Error in handling FRR: [chars] [chars] [hec] [hec] |
Error in FRR processing. |
asr900-tdm-combo |
"This is a internal software error. If this error happened while " "configuring FRR try reconfiguring the interface. If the error " "persists or occurred during normal operation decode the traceback " "and " LOG_STD_ACTION |
|
SPA_EOMER-3-INTFC_FAILED |
3-Error |
Channel provisioning failed for [chars] |
Channel could not be provisioned on SPA for this interface interface corresoponding to that channel has been moved to down state. If this interface was provisoned using the user interface then it may not appear in the interface list. |
asr900-tdm-combo |
SPA_EOMER_INTERNAL_SW_ERROR_ACTION |
|
SPA_EOMER-3-INVALID_MAX_VC |
3-Error |
for[chars] |
invalid max vc for IM |
asr900-tdm-combo |
LOG_STD_SH_TECH_ACTION |
|
SPA_EOMER-3-INVALID_SPA_TYPE |
3-Error |
Invalid SPA type : slot/bay:[dec]/[dec] spa_type=[dec]. |
The channelized SPA type cannot be recognized by the version of Cisco IOS software currently running on the system. |
asr900-tdm-combo |
"Upgrade your system to a version of Cisco IOS software that supports " "this SPA type." |
|
SPA_EOMER-3-NULL |
3-Error |
[chars] |
The NULL pointer was detected when getting the data structure. |
asr900-tdm-combo |
SPA_EOMER_ENABLE_DEBUG_ACTION |
|
SPA_EOMER-3-NULL_CDB |
3-Error |
payload CDB is NULL for [dec]/[dec]/[dec] |
The payload cdb for the port is Null. |
asr900-tdm-combo |
SPA_EOMER_INTERNAL_SW_ERROR_ACTION |
|
SPA_EOMER-3-NULL_DATA_STRUCTURE |
3-Error |
[chars] |
A software error occured and SPA driver is not able to retrieve the data structure mentioned in the message. |
asr900-lotr-im |
LOG_STD_ACTION |
|
SPA_EOMER-3-NULL_ETH_SUBBLOCK |
3-Error |
Ethernet subblock is null for [dec]/[dec] |
The ethernet subblock is NULL |
asr900-tdm-combo |
SPA_EOMER_INTERNAL_SW_ERROR_ACTION |
|
SPA_EOMER-3-NULL_INSTANCE |
3-Error |
Null [chars] instance for slot/bay/port:[dec]/[dec]/[dec] |
The instance pointer is NULL when getting data structure. |
asr900-tdm-combo |
SPA_EOMERINTERNAL_SW_ERROR_ACTION |
|
SPA_EOMER-3-NULL_OPTICS_CDB |
3-Error |
Optic CDB is NULL for [dec]/[dec]/[dec] |
The optics cdb for the port is Null. |
asr900-tdm-combo |
SPA_EOMER_INTERNAL_SW_ERROR_ACTION |
|
SPA_EOMER-3-NULL_OPTICS_HWIDB |
3-Error |
Optic HWIDB is NULL for [dec]/[dec]/[dec] |
The optics hwidb for the port is Null. |
asr900-tdm-combo |
SPA_EOMER_INTERNAL_SW_ERROR_ACTION |
|
SPA_EOMER-3-NULL_SPA_PTR |
3-Error |
- |
Pointer to a SPA object is NULL. |
asr900-tdm-combo |
LOG_STD_SH_TECH_ACTION |
|
SPA_EOMER-3-NULL_SUBBLOCK |
3-Error |
Null ssb for [chars] |
The hwidb subblock is NULL. |
asr900-tdm-combo |
SPA_CHOCX_INTERNAL_SW_ERROR_ACTION |
|
SPA_EOMER-3-NULL_VC_INST |
3-Error |
for[chars] |
Pointer to VC INST is NULL. |
asr900-tdm-combo |
LOG_STD_SH_TECH_ACTION |
|
SPA_EOMER-3-RETURN_ERROR |
3-Error |
Return error for [chars]: return_value=[dec] |
Return error code received. |
asr900-tdm-combo |
SPA_EOMER_INTERNAL_SW_ERROR_ACTION |
|
SPA_EOMER-3-UNKNOWN_OPTION |
3-Error |
Received unknown [chars]: option=[dec] |
Unknown option received. |
asr900-tdm-combo |
SPA_EOMER_INTERNAL_SW_ERROR_ACTION |
|
SPA_EOMER-5-DEF_SUBRATE |
5-Notice |
[chars] [chars] |
Remote subrate configuration changed. |
asr900-tdm-combo |
"Inform the network operator that subrate configuration was changed " "by remote end." |
|
SPA_EOWYN-3-CORRUPT |
3-Error |
Corrupt configuration unsupported [chars] [dec] encountered |
The OC3/STM1 RP driver running configuration is corrupted. |
asr900-tdm-combo |
SPA_EOWYN_INTERNAL_SW_ERROR_ACTION |
|
SPA_EOWYN-3-CREATE_FAIL |
3-Error |
Failed to create [chars] : slot/bay:[dec]/[dec] |
The channelized SPA controller descriptor block creation failed. Check the amount of available system memory. |
asr900-tdm-combo |
LOG_STD_SH_TECH_ACTION |
|
SPA_EOWYN-3-DCC_FAILURE |
3-Error |
Failed to retrieve DCC info for [dec]/[dec]/[dec] |
\n The DCC info could not be retrieved |
asr900-tdm-combo |
SPA_EOWYN_INTERNAL_SW_ERROR_ACTION |
|
SPA_EOWYN-3-ERROR |
3-Error |
Failed to create for [chars] : slot/bay:[dec]/[dec] |
The 1Z 8S SPA/IM controller encountered an error. |
asr900-tdm-combo |
"Check the memory availabe in system and " LOG_STD_SH_TECH_ACTION |
|
SPA_EOWYN-3-FATAL_ERROR |
3-Error |
Fatal error for [chars] : slot/bay:[dec]/[dec] |
The channelized SPA controller encountered a fatal error. |
asr900-tdm-combo |
LOG_STD_SH_TECH_ACTION |
|
SPA_EOWYN-3-FRR_ERROR |
3-Error |
Error in handling FRR: [chars] [chars] [hec] [hec] |
Error in FRR processing. |
asr900-tdm-combo |
"This is a internal software error. If this error happened while " "configuring FRR try reconfiguring the interface. If the error " "persists or occurred during normal operation decode the traceback " "and " LOG_STD_ACTION |
|
SPA_EOWYN-3-INTFC_FAILED |
3-Error |
Channel provisioning failed for [chars] |
Channel could not be provisioned on SPA for this interface interface corresoponding to that channel has been moved to down state. If this interface was provisoned using the user interface then it may not appear in the interface list. |
asr900-tdm-combo |
SPA_EOWYN_INTERNAL_SW_ERROR_ACTION |
|
SPA_EOWYN-3-INVALID_MAX_VC |
3-Error |
for[chars] |
invalid max vc for IM |
asr900-tdm-combo |
LOG_STD_SH_TECH_ACTION |
|
SPA_EOWYN-3-INVALID_SPA_TYPE |
3-Error |
Invalid SPA type : slot/bay:[dec]/[dec] spa_type=[dec]. |
The channelized SPA type cannot be recognized by the version of Cisco IOS software currently running on the system. |
asr900-tdm-combo |
"Upgrade your system to a version of Cisco IOS software that supports " "this SPA type." |
|
SPA_EOWYN-3-NULL |
3-Error |
[chars] |
The NULL pointer was detected when getting the data structure. |
asr900-tdm-combo |
SPA_EOWYN_ENABLE_DEBUG_ACTION |
|
SPA_EOWYN-3-NULL_CDB |
3-Error |
payload CDB is NULL for [dec]/[dec]/[dec] |
The payload cdb for the port is Null. |
asr900-tdm-combo |
SPA_EOWYN_INTERNAL_SW_ERROR_ACTION |
|
SPA_EOWYN-3-NULL_ETH_SUBBLOCK |
3-Error |
Ethernet subblock is null for [dec]/[dec] |
The ethernet subblock is NULL |
asr900-tdm-combo |
SPA_EOWYN_INTERNAL_SW_ERROR_ACTION |
|
SPA_EOWYN-3-NULL_INSTANCE |
3-Error |
Null [chars] instance for slot/bay/port:[dec]/[dec]/[dec] |
The instance pointer is NULL when getting data structure. |
asr900-tdm-combo |
SPA_EOWYN_INTERNAL_SW_ERROR_ACTION |
|
SPA_EOWYN-3-NULL_OPTICS_CDB |
3-Error |
Optic CDB is NULL for [dec]/[dec]/[dec] |
The optics cdb for the port is Null. |
asr900-tdm-combo |
SPA_EOWYN_INTERNAL_SW_ERROR_ACTION |
|
SPA_EOWYN-3-NULL_OPTICS_HWIDB |
3-Error |
Optic HWIDB is NULL for [dec]/[dec]/[dec] |
The optics hwidb for the port is Null. |
asr900-tdm-combo |
SPA_EOWYN_INTERNAL_SW_ERROR_ACTION |
|
SPA_EOWYN-3-NULL_SPA_PTR |
3-Error |
- |
Pointer to a SPA object is NULL. |
asr900-tdm-combo |
LOG_STD_SH_TECH_ACTION |
|
SPA_EOWYN-3-NULL_SUBBLOCK |
3-Error |
Null ssb for [chars] |
The hwidb subblock is NULL. |
asr900-tdm-combo |
SPA_CHOCX_INTERNAL_SW_ERROR_ACTION |
|
SPA_EOWYN-3-NULL_VC_INST |
3-Error |
for[chars] |
Pointer to VC INST is NULL. |
asr900-tdm-combo |
LOG_STD_SH_TECH_ACTION |
|
SPA_EOWYN-3-RETURN_ERROR |
3-Error |
Return error for [chars]: return_value=[dec] |
Return error code received. |
asr900-tdm-combo |
SPA_EOWYN_INTERNAL_SW_ERROR_ACTION |
|
SPA_EOWYN-3-UNKNOWN_OPTION |
3-Error |
Received unknown [chars]: option=[dec] |
Unknown option received. |
asr900-tdm-combo |
SPA_EOWYN_INTERNAL_SW_ERROR_ACTION |
|
SPA_EOWYN-5-DEF_SUBRATE |
5-Notice |
[chars] [chars] |
Remote subrate configuration changed. |
asr900-tdm-combo |
"Inform the network operator that subrate configuration was changed " "by remote end." |
|
SPA_EOWYN-5-SPA_MODE_IS |
5-Notice |
spa_mode of [dec]/[dec] is [chars] |
\n spa_mode is |
asr900-tdm-combo |
SPA_EOWYN_INTERNAL_SW_ERROR_ACTION |
|
SPA_EOWYN-6-XFP_OK |
6-Information |
[dec]/[dec]/[dec]: [chars] detected/inserted |
XFP has been detected or inserted in a port in Channelized SPA. |
asr900-tdm-combo |
"This is a information message no action required" |
|
SPA_ETHER_INTERNAL_IF-3-ETHER_INTERNAL_IF_SW_ERR |
3-Error |
NULL |
The module driver detected a software error condition on the module card. This might result in improper operation. |
lebowski-o2 |
"The module driver has encountered a software error. Power down and " "reseat the indicated module card. If the problem persists copy the " "error message exactly as it appears in the console and open a case " "with the Technical Assistance Center via the Internet at " TAC_CASE_OPEN " or contact your " "Cisco technical support representative and provide the representative " "with the information you have gathered. Be sure to attach to your case " "the output of the <CmdBold>show logging<NoCmdBold> " "<CmdBold>show monitor event-trace spa all<NoCmdBold> and " "<CmdBold>show tech-support<NoCmdBold> commands your troubleshooting " "logs and the specific error message." |
|
SPA_ETHER-1-ALLOCFAIL |
1-Alert |
Subslot [dec]/[dec] [chars] allocation failure [chars] |
The router has failed to allocate sufficient memory for a software module\n\ on the Ethernet SPA located in the specified subslot. The error message\n\ indicates the modular services card slot the SPA subslot the SPA type and\n\ the name of the software module. |
spa-eth-fe |
"Perform OIR of the SPA located in the specified subslot. Before removing\n\ the SPA enter the <CmdBold>hw-module subslot stop<NoCmdBold> command.\n\ Remove the SPA wait 5 seconds and reinsert the SPA into the MSC. Enter\n\ the <CmdBold>show memory summary<NoCmdBold> command to attempt to\n\ determine the cause of the error. Reduce system activity to reduce memory\n\ demands. If conditions warrant upgrade to a larger memory configuration.\n\ If you require further assistance " LOG_STD_REDUCE_ACTION |
|
SPA_ETHER-3-HW_ERROR |
3-Error |
Subslot [dec]/[dec] [chars] Hardware device error [chars] detected reactivating |
An internal hardware device error has occurred on the Ethernet SPA. The\n\ error message indicates the modular services card slot the SPA subslot\n\ the SPA type and the name of the hardware device. The SPA has been\n\ deactivated and reactivated to resolve the problem. If the error occurs\n\ more than five times within an hour no further attempts to reactivate the\n\ SPA will be made. This message is likely due to an unrecoverable hardware\n\ failure |
spa-eth-fe |
"Perform OIR of the SPA located in the specified subslot. Before removing\n\ the SPA enter the <CmdBold>hw-module subslot stop<NoCmdBold> command.\n\ Remove the SPA wait 5 seconds and reinsert the SPA into the MSC. If the\n\ problem persists copy the error message text exactly as it appears on the\n\ console or in the system log enter the <CmdBold>show diag<NoCmdBold>\n\ command contact your Cisco technical support representative and provide\n\ the representative with the gathered information." |
|
SPA_ETHER-3-INITFAIL |
3-Error |
Subslot [dec]/[dec] [chars] initialization failure [chars] |
The initialization of an internal device on the Ethernet SPA in the\n\ specified subslot has failed. The error message indicates the modular\n\ services card slot the SPA subslot the SPA type and the name of the\n\ device that failed to initialize. The message also provides the interface\n\ name and other details about the error. |
spa-eth-fe |
"Copy the error message text exactly as it appears on the console or in the\n\ system log enter the <CmdBold>show tech-support<NoCmdBold> command\n\ contact your Cisco technical support representative and provide the\n\ representative with the gathered information." |
|
SPA_ETHER-3-INVALID_PORT |
3-Error |
Subslot [dec]/[dec] [chars] Incorrect port number [dec] specified for SPA |
An internal error has been encountered by the Ethernet software driver for\n\ the SPA. The error message indicates the modular services card slot the\n\ SPA subslot the SPA type and the invalid interface port number. This\n\ problem is caused by a software caveat. |
spa-eth-fe |
"Copy the error message text exactly as it appears on the console or in the\n\ system log enter the <CmdBold>show tech-support<NoCmdBold> command\n\ contact your Cisco technical support representative and provide the\n\ representative with the gathered information." |
|
SPA_ETHER-3-SEND_MSG |
3-Error |
Subslot [dec]/[dec] [chars] Failed to notify driver process about a line state change in one of the SPA interfaces |
A line state change has occurred on one of the interface ports on the\n\ Ethernet SPA. The error message indicates the modular services card slot\n\ the SPA subslot and the SPA type. Information to identify which interface\n\ port is affected on the SPA is not available. The affected interface might\n\ not function properly. |
spa-eth-fe |
"Perform OIR of the SPA located in the specified subslot. Before removing\n\ the SPA enter the <CmdBold>hw-module subslot stop<NoCmdBold> command.\n\ Remove the SPA wait 5 seconds and reinsert the SPA into the MSC. Enter\n\ the <CmdBold>show memory summary<NoCmdBold> command to attempt to\n\ determine the cause of the error. Reduce system activity to reduce memory\n\ demands. If conditions warrant upgrade to a larger memory configuration.\n\ If you require further assistance " LOG_STD_REDUCE_ACTION |
|
SPA_ETHER-3-SFP_EEPROM_READ_FAIL |
3-Error |
[chars] [chars] initialization failure [chars] |
The pluggable transceiver module SFP on the Ethernet SPA could not be |
spa-eth-ge-2 |
"Try re-inserting the pluggable transceiver module SFP again into the " |
|
SPA_ETHER-3-SFP_SEC_FAIL |
3-Error |
[chars] [chars] initialization failure [chars] |
The pluggable transceiver module SFP on the Ethernet SPA could not |
spa-eth-ge-2 |
"Try replacing the pluggable transceiver module SFP with a Cisco " |
|
SPA_ETHER-3-SPI4_NOT_IN_SYNC |
3-Error |
Subslot [dec]/[dec] [chars] SPI4 internal interface is not synchronized with the\n\ modular services card for the SPA located in the specified subslot. |
The SPI4 internal path between the modular services card and the SPA is\n\ not synchronized. The error message indicates the modular services card\n\ slot the SPA subslot and the SPA type. This error indicates that either\n\ the SPA is not properly inserted into the MSC or a hardware failure has\n\ occurred on the SPA. |
spa-eth-fe |
"Perform OIR of the SPA located in the specified subslot. Before removing\n\ the SPA enter the <CmdBold>hw-module subslot stop<NoCmdBold> command.\n\ Remove the SPA wait 5 seconds and reinsert the SPA into the MSC. If the\n\ problem persists copy the error message text exactly as it appears on the\n\ console or in the system log enter the <CmdBold>show\n\ tech-support<NoCmdBold> command contact your Cisco technical support\n\ representative and provide the representative with the gathered\n\ information." |
|
SPA_ETHER-3-TCAM_ACCESS_FAILURE |
3-Error |
Subslot [dec]/[dec] [chars] Failure in accessing the TCAM device [chars] status = 0x[hec] |
Access to the TCAM device on the SPA has failed. The error message\n\ indicates the modular services card slot the SPA subslot and the SPA type.\n\ This error indicates a hardware failure. |
spa-eth-fe |
"Perform OIR of the SPA located in the specified subslot. Before removing\n\ the SPA enter the <CmdBold>hw-module subslot stop<NoCmdBold> command.\n\ Remove the SPA wait 5 seconds and reinsert the SPA into the MSC. If the\n\ problem persists copy the error message text exactly as it appears on the\n\ console or in the system log enter the <CmdBold>show\n\ tech-support<NoCmdBold> command contact your Cisco technical support\n\ representative and provide the representative with the gathered\n\ information." |
|
SPA_ETHER-3-TCAM_INST_CREATE_FAIL |
3-Error |
Subslot [dec]/[dec] [chars] Failed to create the TCAM management instance status = 0x[hec] |
The SPA failed to create the internal data structure needed to manage TCAM\n\ entries. The error message indicates the modular services card slot the\n\ SPA subslot and the SPA type. This error indicates a software caveat. |
spa-eth-fe |
"Copy the error message text exactly as it appears on the console or in the\n\ system log enter the <CmdBold>show tech-support<NoCmdBold> command\n\ contact your Cisco technical support representative and provide the\n\ representative with the gathered information." |
|
SPA_ETHER-3-TCAM_MAC_DA_TABLE_ACCESS_FAILURE |
3-Error |
Subslot [dec]/[dec] [chars] Failure in accessing the TCAM destination MAC address table [chars] |
Access to the TCAM destination MAC address table for the SPA interface\n\ failed. The error message indicates the modular services card slot the\n\ SPA subslot the SPA type and the affected interface number. This error\n\ indicates either a software caveat or a hardware failure. |
spa-eth-fe |
"Perform OIR of the SPA located in the specified subslot. Before removing\n\ the SPA enter the <CmdBold>hw-module subslot stop<NoCmdBold> command.\n\ Remove the SPA wait 5 seconds and reinsert the SPA into the MSC. If the\n\ problem persists copy the error message text exactly as it appears on the\n\ console or in the system log enter the <CmdBold>show\n\ tech-support<NoCmdBold> command contact your Cisco technical support\n\ representative and provide the representative with the gathered\n\ information." |
|
SPA_ETHER-3-TCAM_MAC_DA_TABLE_INVALID |
3-Error |
Subslot [dec]/[dec] [chars] Destination MAC address filter table is invalid for interface [dec] |
The internal data structure used by the SPA for managing the destination\n\ MAC address filtering for an interface port is invalid. This error message\n\ indicates the modular services card slot the SPA subslot the SPA type and\n\ the interface port. This error indicates a software caveat. |
spa-eth-fe |
"Copy the error message text exactly as it appears on the console or in the\n\ system log enter the <CmdBold>show tech-support<NoCmdBold> command\n\ contact your Cisco technical support representative and provide the\n\ representative with the gathered information." |
|
SPA_ETHER-3-TCAM_VLAN_TABLE_ACCESS_FAILURE |
3-Error |
Subslot [dec]/[dec] [chars] Failure in accessing the TCAM VLAN address table [chars] |
Access to the TCAM VLAN table for the SPA failed. The error message\n\ indicates the modular services card slot the SPA subslot the SPA type and\n\ the affected interface. This error indicates either a software caveat or a\n\ hardware failure. |
spa-eth-fe |
"Perform OIR of the SPA located in the specified subslot. Before removing\n\ the SPA enter the <CmdBold>hw-module subslot stop<NoCmdBold> command.\n\ Remove the SPA wait 5 seconds and reinsert the SPA into the MSC. If the\n\ problem persists copy the error message text exactly as it appears on the\n\ console or in the system log enter the <CmdBold>show\n\ tech-support<NoCmdBold> command contact your Cisco technical support\n\ representative and provide the representative with the gathered\n\ information." |
|
SPA_ETHER-3-TCAM_VLAN_TABLE_INVALID |
3-Error |
Subslot [dec]/[dec] [chars] VLAN filter table is invalid for interface [dec] |
The internal data structure used by the SPA to manage the VLAN filtering\n\ is invalid. The SPA supports a separate VLAN table per interface. The\n\ error message indicates the modular services card slot the SPA subslot\n\ the SPA type and the affected interface. This error indicates a software\n\ caveat. |
spa-eth-fe |
"Copy the error message text exactly as it appears on the console or in the\n\ system log enter the <CmdBold>show tech-support<NoCmdBold> command\n\ contact your Cisco technical support representative and provide the\n\ representative with the gathered information." |
|
SPA_ETHER-4-BAY_NOT_FOUND |
4-Warning |
Subslot [dec]/[dec] [chars] Failed to get the bay information |
Unable to retrieve a software data structure for the subslot. The error\n\ message indicates the modular services card slot the affected subslot and\n\ the SPA type. This error indicates a software caveat. |
spa-eth-fe |
"Copy the error message text exactly as it appears on the console or in the\n\ system log enter the <CmdBold>show tech-support<NoCmdBold> command\n\ contact your Cisco technical support representative and provide the\n\ representative with the gathered information." |
|
SPA_ETHER-4-NOPROCESS |
4-Warning |
Subslot [dec]/[dec] [chars] creation of [chars] process failed |
The creation of an IOS process to manage the SPA failed. The error message\n\ indicates the modular services card slot the SPA subslot the SPA type and\n\ the name of the process. This error message will be accompanied by an IOS\n\ error message that will give more information about the cause for this\n\ failure. |
spa-eth-fe |
"Enter the <CmdBold>show memory summary<NoCmdBold> command to attempt to\n\ determine the cause of the error. Reduce system activity to reduce memory\n\ demands. If conditions warrant upgrade to a larger memory configuration.\n\ If you require further assistance " LOG_STD_REDUCE_ACTION |
|
SPA_ETHER-4-TCAM_MAC_DA_TABLE_FULL |
4-Warning |
Subslot [dec]/[dec] [chars] Destination MAC address filter table is full for interface [dec] MAC address = [enet] mask = [enet] |
The TCAM destination MAC address table for an interface on the SPA is\n\ full. The SPA supports a separate MAC table per interface. The error\n\ message indicates the modular services card slot the SPA subslot the SPA\n\ type the affected interface and the MAC address. The specified MAC\n\ address will not be added to the TCAM table. |
spa-eth-fe |
"Try to remove some of the registered MAC addresses for the interface by\n\ changing the interface configuration. To verify the MAC addresses currently\n\ in use by an interface enter the <CmdBold>show controllers<NoCmdBold>\n\ command." |
|
SPA_ETHER-4-TCAM_VLAN_TABLE_FULL |
4-Warning |
Subslot [dec]/[dec] [chars] VLAN filter table is full for interface [dec] VLAN identifier = [dec] |
The TCAM VLAN filter table for an interface on the SPA is full. The SPA\n\ supports a separate VLAN table per interface. The error message indicates\n\ the modular services card slot the SPA subslot the SPA type the affected\n\ interface and the VLAN entry that failed. The specified VLAN identifier\n\ will not be added to the TCAM table. |
- |
"Try to remove some of the registered VLANs for the interface by changing\n\ the interface configuration. To verify the VLAN IDs currently in use by an\n\ interface enter the <CmdBold>show controllers<NoCmdBold> command." |
|
SPA_ETHER-4-TEMPERATURE_READ_FAIL |
4-Warning |
Subslot [dec]/[dec] [chars] Failed to read current temperature from sensor [dec] status = 0x[hec] |
The current temperature reading on the SPA cannot be determined. The\n\ error message indicates the modular services card slot the SPA subslot and\n\ the SPA type. This error indicates a hardware failure. |
spa-eth-fe |
"Perform OIR of the SPA located in the specified subslot. Before removing\n\ the SPA enter the <CmdBold>hw-module subslot stop<NoCmdBold> command.\n\ Remove the SPA wait 5 seconds and reinsert the SPA into the MSC. If the\n\ problem persists copy the error message text exactly as it appears on the\n\ console or in the system log enter the <CmdBold>show\n\ tech-support<NoCmdBold> command contact your Cisco technical support\n\ representative and provide the representative with the gathered\n\ information." |
|
SPA_ETHER-4-VOLTAGE_READ_FAIL |
4-Warning |
Subslot [dec]/[dec] [chars] Failed to read the current voltage for [chars] supply |
The current voltage reading for the SPA voltage supply cannot be\n\ determined. The error message indicates the modular services card slot\n\ the SPA subslot the SPA type and the identification of the voltage supply.\n\ This error indicates a hardware failure. |
spa-eth-fe |
"Perform OIR of the SPA located in the specified subslot. Before removing\n\ the SPA enter the <CmdBold>hw-module subslot stop<NoCmdBold> command.\n\ Remove the SPA wait 5 seconds and reinsert the SPA into the MSC. If the\n\ problem persists copy the error message text exactly as it appears on the\n\ console or in the system log enter the <CmdBold>show\n\ tech-support<NoCmdBold> command contact your Cisco technical support\n\ representative and provide the representative with the gathered\n\ information." |
|
SPA_ETHER-6-TCAM_VLAN_FILTERING_DISABLED |
6-Information |
Subslot [dec]/[dec] [chars] TCAM VLAN filter table is full disabling VLAN filtering for interface [dec] |
VLAN filtering for the specified interface has been disabled because the VLAN table is full. This means that the SPA will transmit frames destined for any VLAN ID to the route processor. The SPA supports a separate VLAN table per interface. The error message indicates the modular services card slot the SPA subslot the SPA type and the affected interface. |
spa-eth-fe |
"To verify the VLAN IDs that are currently in use by an interface enter " "the <CmdBold>show controllers<NoCmdBold> command. You can remove " "some of the existing VLANs from the interface configuration to " "reactivate VLAN filtering on the indicated interface." |
|
SPA_ETHER-6-TCAM_VLAN_FILTERING_ENABLED |
6-Information |
Subslot [dec]/[dec] [chars] Enabling VLAN filtering for interface [dec] |
VLAN filtering for the specified interface is enabled. The SPA supports a separate VLAN table per interface. The error message indicates the modular services card slot the SPA subslot the SPA type and the affected interface. |
spa-eth-fe |
"VLAN filtering has been reactivated and the VLAN table is no longer " "full. This means that the SPA will transmit frames to the route " "processor only for those VLAN IDs configured on the specified interface." "To verify the VLAN IDs that are currently in use by an interface " "enter the <CmdBold>show controllers<NoCmdBold> command." |
|
SPA_FANTRAY_COMBO_NOT_SUPPORTED-2-INVALID_COMBINATION |
2-Critical |
SPA : [chars] at bay [dec] is not supported with fan [chars] |
- |
- |
- |
|
SPA_FPD-2-PWR_NO_OK |
2-Critical |
SPA POWER OK signal is not asserted for [chars] in [chars] for FPD upgrade. |
The check for SPA POWER OK signal assertion failed. This might indicate a HW problem with the SPA. |
spa-infra-fpd |
"Contact your Cisco technical support " "representative to have the SPA replaced." |
|
SPA_FPD-2-PWR_NO_OK |
2-Critical |
SPA POWER OK signal is not asserted for [chars] in [chars] for FPD upgrade. |
The check for SPA POWER OK signal assertion failed. This might indicate a HW problem with the SPA. |
spa-infra-fpd |
"Contact your Cisco technical support " "representative to have the SPA replaced." |
|
SPA_FPD-3-ADM106X_EEPROM_READ_ERROR |
3-Error |
[chars]: Failed to read the content of ADM106x [chars] EEPROM section - [chars] |
The read operation to ADM106x is performed through C2W serial interface from SPA carrier card the indicated failure might be caused by busy C2W serial interface. |
spa-infra-fpd |
"Retry the same operation again later. If the " "problem persists remove the configuration of the SPA before trying " "again the operation." |
|
SPA_FPD-3-ADM106X_EEPROM_READ_ERROR |
3-Error |
[chars]: Failed to read the content of ADM106x [chars] EEPROM section - [chars] |
The read operation to ADM106x is performed through C2W serial interface from SPA carrier card the indicated failure might be caused by busy C2W serial interface. |
spa-infra-fpd |
"Retry the same operation again later. If the " "problem persists remove the configuration of the SPA before trying " "again the operation." |
|
SPA_FPD-3-ADM106X_EEPROM_VERIFY_ERROR |
3-Error |
[chars]: Verification of write operation failed in ADM106x [chars] EEPROM section for address 0x[hec] - read value '0x[hec]' expected value '0x[hec]'. |
The verification of the write operation has found a mismatch on the EEPROM data. The problem might be an indication of aging effect on the device that cannot longer hold written data. |
spa-infra-fpd |
"Retry the upgrade operation again later. If the " "problem persists replace the SPA." |
|
SPA_FPD-3-ADM106X_EEPROM_VERIFY_ERROR |
3-Error |
[chars]: Verification of write operation failed in ADM106x [chars] EEPROM section for address 0x[hec] - read value '0x[hec]' expected value '0x[hec]'. |
The verification of the write operation has found a mismatch on the EEPROM data. The problem might be an indication of aging effect on the device that cannot longer hold written data. |
spa-infra-fpd |
"Retry the upgrade operation again later. If the " "problem persists replace the SPA." |
|
SPA_FPD-3-ADM106X_EEPROM_WRITE_ERROR |
3-Error |
[chars]: Failed to write new configuration into ADM106x [chars] EEPROM section - [chars] |
The write operation to ADM106x is performed through C2W serial interface from SPA carrier card the indicated failure might be caused by busy C2W serial interface. |
spa-infra-fpd |
"Retry the upgrade operation again later. If the " "problem persists remove the configuration of the SPA before trying " "again the upgrade operation." |
|
SPA_FPD-3-ADM106X_EEPROM_WRITE_ERROR |
3-Error |
[chars]: Failed to write new configuration into ADM106x [chars] EEPROM section - [chars] |
The write operation to ADM106x is performed through C2W serial interface from SPA carrier card the indicated failure might be caused by busy C2W serial interface. |
spa-infra-fpd |
"Retry the upgrade operation again later. If the " "problem persists remove the configuration of the SPA before trying " "again the upgrade operation." |
|
SPA_FPD-3-ADM106X_READ_VER_ERROR |
3-Error |
[chars]: Failed to read version info from ADM106x device - [chars] |
The read operation to ADM106x is performed through C2W serial interface from SPA carrier card the indicated failure might be caused by busy C2W serial interface. |
spa-infra-fpd |
"Try to reload the SPA with <CmdBold>hw-module subslot<NoCmdBold> " "<CmdArg>slot#/subslot#<NoCmdArg> <CmdBold>reload<NoCmdBold> command " "to correct the failure. If problem persists move the SPA to another " "bay of the carrier card." |
|
SPA_FPD-3-ADM106X_READ_VER_ERROR |
3-Error |
[chars]: Failed to read version info from ADM106x device - [chars] |
The read operation to ADM106x is performed through C2W serial interface from SPA carrier card the indicated failure might be caused by busy C2W serial interface. |
spa-infra-fpd |
"Try to reload the SPA with <CmdBold>hw-module subslot<NoCmdBold> " "<CmdArg>slot#/subslot#<NoCmdArg> <CmdBold>reload<NoCmdBold> command " "to correct the failure. If problem persists move the SPA to another " "bay of the carrier card." |
|
SPA_FPD-3-GETVER_FAILED |
3-Error |
[chars]: Failed to get FPD version for \[chars]\ ID=[dec]: [chars]. |
Failed to get FPD version due to either IPC problem or operation error. The card will be disabled. |
spa-infra-fpd |
"Check SPA seating and SPA status. " "Ensure compatibility among FPD IOS and possible SPA " "firmware by comparing output of command " "<CmdBold>show hw-module subslot fpd<NoCmdBold> with IOS " "Release Notes. Obtain IOS version by command " "<CmdBold>show version<NoCmdBold>." |
|
SPA_FPD-3-GETVER_FAILED |
3-Error |
[chars]: Failed to get FPD version for \[chars]\ ID=[dec]: [chars]. |
Failed to get FPD version due to either IPC problem or operation error. The card will be disabled. |
spa-infra-fpd |
"Check SPA seating and SPA status. " "Ensure compatibility among FPD IOS and possible SPA " "firmware by comparing output of command " "<CmdBold>show hw-module subslot fpd<NoCmdBold> with IOS " "Release Notes. Obtain IOS version by command " "<CmdBold>show version<NoCmdBold>." |
|
SPA_FPD-3-IHEX_PARSE_ERROR |
3-Error |
NULL |
- |
spa-infra-fpd |
LOG_STD_ACTION |
|
SPA_FPD-3-IHEX_PARSE_ERROR |
3-Error |
NULL |
- |
spa-infra-fpd |
LOG_STD_ACTION |
|
SPA_FPD-3-JTAG_ERR |
3-Error |
[chars]: Failed to program a [chars] FPD image file. Error code 0x%02x. |
While attempting to program a SPA FPGA via JTAG bus an error occurs. It could be caused by an outdated carrier card FPGA or SPA connection. It may also flag an internal software error. |
spa-infra-fpd |
"Retry the upgrade after reseating SPA. " "Verify carrier card FPGA is current. Copy exact the error " "message and report to TAC." |
|
SPA_FPD-3-JTAG_ERR |
3-Error |
[chars]: Failed to program a [chars] FPD image file. Error code 0x%02x. |
While attempting to program a SPA FPGA via JTAG bus an error occurs. It could be caused by an outdated carrier card FPGA or SPA connection. It may also flag an internal software error. |
spa-infra-fpd |
"Retry the upgrade after reseating SPA. " "Verify carrier card FPGA is current. Copy exact the error " "message and report to TAC." |
|
SPA_FPD-3-PWR_OFF_FAILED |
3-Error |
Failed to power-off [chars] in [chars] for FPD offline upgrade within [dec] seconds. |
The power-off operation of the indicated SPA failed within the number of specified seconds. This might indicate that the time used to wait for SPA to power-off is not long enough which can happen if the SPA has a lot of interfaces configured. |
spa-infra-fpd |
"Retry the upgrade operation again later. If the " "problem persists remove the configuration of the SPA before trying " "again the upgrade operation." |
|
SPA_FPD-3-PWR_OFF_FAILED |
3-Error |
Failed to power-off [chars] in [chars] for FPD offline upgrade within [dec] seconds. |
The power-off operation of the indicated SPA failed within the number of specified seconds. This might indicate that the time used to wait for SPA to power-off is not long enough which can happen if the SPA has a lot of interfaces configured. |
spa-infra-fpd |
"Retry the upgrade operation again later. If the " "problem persists remove the configuration of the SPA before trying " "again the upgrade operation." |
|
SPA_FPD-3-SMM665_CONF_WRITE_ERROR |
3-Error |
[chars]: Failed to write new configuration into SMM665 device. |
The write operation to SMM665 is performed through C2W serial interface from SPA carrier card the indicated failure might be caused by busy C2W serial interface. |
spa-infra-fpd |
"Retry the upgrade operation again later. If the " "problem persists remove the configuration of the SPA before trying " "again the upgrade operation." |
|
SPA_FPD-3-SMM665_CONF_WRITE_ERROR |
3-Error |
[chars]: Failed to write new configuration into SMM665 device. |
The write operation to SMM665 is performed through C2W serial interface from SPA carrier card the indicated failure might be caused by busy C2W serial interface. |
spa-infra-fpd |
"Retry the upgrade operation again later. If the " "problem persists remove the configuration of the SPA before trying " "again the upgrade operation." |
|
SPA_FPD-3-SW_ERROR |
3-Error |
NULL |
- |
spa-infra-fpd |
LOG_STD_ACTION |
|
SPA_FPD-3-SW_ERROR |
3-Error |
NULL |
- |
spa-infra-fpd |
LOG_STD_ACTION |
|
SPA_FPD-3-UPGRADE_FAILED |
3-Error |
[chars]: Failed to upgrade FPD [chars]. |
The FPD image upgrade operation failed. This error is specific to the SPA. The cause could be a wrong image file error in accessing fpga storage physical interrupt such as power failure or card removal. Depending on SPA type and error cause the card could be in an unusable status. Normally the system automatically reattempts the upgrade and shuts the card after repeated failures. |
spa-infra-fpd |
"Do not interrupt the system while an FPD " "upgrade is in progress. Obtain the matching FPD package. Refer " "to IOS Release Notes for more information on obtaining the correct " "FPD package for the SPA. Review the output of the RP FPD logs." |
|
SPA_FPD-3-UPGRADE_FAILED |
3-Error |
[chars]: Failed to upgrade FPD [chars]. |
The FPD image upgrade operation failed. This error is specific to the SPA. The cause could be a wrong image file error in accessing fpga storage physical interrupt such as power failure or card removal. Depending on SPA type and error cause the card could be in an unusable status. Normally the system automatically reattempts the upgrade and shuts the card after repeated failures. |
spa-infra-fpd |
"Do not interrupt the system while an FPD " "upgrade is in progress. Obtain the matching FPD package. Refer " "to IOS Release Notes for more information on obtaining the correct " "FPD package for the SPA. Review the output of the RP FPD logs." |
|
SPA_FPD-4-UPGRADE_ABORTED |
4-Warning |
[chars]: Upgrade aborted for \[chars]\ ID=[dec] - [chars] |
The upgrade operation for the FPD image was aborted because the provided image cannot be used by the driver to perform the image programming operation. |
spa-infra-fpd |
"Make sure that the provide FPD image package for " "the FPD upgrade operation is a valid one for the Cisco IOS release in " "use. This can be verified with the <CmdBold>show upgrade fpd package " "default<NoCmdBold> command to display the required FPD image package " "version for the IOS image." |
|
SPA_FPD-4-UPGRADE_ABORTED |
4-Warning |
[chars]: Upgrade aborted for \[chars]\ ID=[dec] - [chars] |
The upgrade operation for the FPD image was aborted because the provided image cannot be used by the driver to perform the image programming operation. |
spa-infra-fpd |
"Make sure that the provide FPD image package for " "the FPD upgrade operation is a valid one for the Cisco IOS release in " "use. This can be verified with the <CmdBold>show upgrade fpd package " "default<NoCmdBold> command to display the required FPD image package " "version for the IOS image." |
|
SPA_FPD-6-IMG_CORRUPTION |
6-Information |
[chars]: FPD image corruption detected for \[chars]\ ID=[dec] forcing upgrade |
The software detected corruption on a FPD image and it is triggering the FPD automatic upgrade mechanism to correct the problem. |
spa-infra-fpd |
"No Action is required." |
|
SPA_FPD-6-IMG_CORRUPTION |
6-Information |
[chars]: FPD image corruption detected for \[chars]\ ID=[dec] forcing upgrade |
The software detected corruption on a FPD image and it is triggering the FPD automatic upgrade mechanism to correct the problem. |
spa-infra-fpd |
"No Action is required." |
|
SPA_GE_DWDM-3-DWDM_ERROR |
3-Error |
[chars] |
SPA driver detected an error in the DWDM init routine |
spa-eth-10ge |
"The SPA driver has detected problem with DWDM init routine." "If the ports on the SPA are not operating as expected power down and" "reseat the indicated SPA card. " "If the error messages persists copy the error message exactly as " "it appears. Next research and attempt to resolve the issue using " "the SPA hardware troubleshooting documentation as well as the tools " "and utilities provided at " "http://www.cisco.com/public/support/tac/tools.shtml. If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a 'show tech-support' to " "your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
SPA_GE_DWDM-3-MALLOC_FAILED |
3-Error |
[chars] |
The SPA driver detected a memory error on the SPA card |
spa-eth-10ge |
"Reload the card and if the problem " "persists call the TAC" |
|
SPA_GE_DWDM-3-NULL_DATA_STRUCTURE |
3-Error |
[chars] [dec] [dec] |
The SPA driver detected NULL data during DWDM initialization |
spa-eth-10ge |
"Reload the SPA card and if the problem " "persists contact your technical support representative" |
|
SPA_GE_DWDM-3-PLL_NOT_LOCKED |
3-Error |
[chars] not locked after \ [dec] retries [hex] |
The SPA driver failed to initialize the PLL |
spa-eth-10ge |
"The SPA driver has detected problem with DWDM init routine." "If the ports on the SPA are not operating as expected power down and" "reseat the indicated SPA card. " "If the error messages persists copy the error message exactly as " "it appears. Next research and attempt to resolve the issue using " "the SPA hardware troubleshooting documentation as well as the tools " "and utilities provided at " "http://www.cisco.com/public/support/tac/tools.shtml. If you still " "require assistance open a case with the Technical Assistance Center " "via the Internet at " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a 'show tech-support' to " "your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
SPA_GE_DWDM-3-SFP_DETECT |
3-Error |
[chars] |
The SPA driver did not detect a Cu-SFP for the port |
spa-eth-10ge |
"Please plugin a CISCO compliant SFP in the " "corresponding port and retry the command" |
|
SPA_GE_DWDM-3-UT2_SPA |
3-Error |
[chars] |
The SPA driver did not detect a UT2 transponder module |
spa-eth-10ge |
"Check if the SPA is a DWDM SPA before " "executing the command" |
|
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 |
|
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 |
|
SPA_IPSEC-3-BOOT_FAIL |
3-Error |
[chars]: [chars]. |
The SPA failed to boot up for the specified reason |
spa-ipsec-2g |
LOG_STD_RECUR_ACTION |
|
SPA_IPSEC-3-BRDTYPE |
3-Error |
Incorrect jacket card board type [dec] detected. |
Board type does not belong to either C7600-SSC-400 or C7600-SSC-600 |
spa-ipsec-2g |
"LOG_STD_RECUR_ACTION" |
|
SPA_IPSEC-3-OVERRIDE |
3-Error |
[chars]: Overriding bundled firmware with ssc[dec]-[chars]. |
Used specified file instead of bundled file. This is a debugging feature. |
spa-ipsec-2g |
LOG_STD_NO_ACTION |
|
SPA_IPSEC-3-PROC_FAIL |
3-Error |
[chars]: [chars] Process creation failed. |
Can not allocate memory for specified process. |
spa-ipsec-2g |
LOG_STD_RECUR_ACTION |
|
SPA_IPSEC-3-PWRCYCLE |
3-Error |
SPA [dec]/[dec] is being power-cycled |
The SPA has stopped responding to keep-alive polling from carrier card. The SPA has been power-cycled. |
spa-ipsec-2g |
"Once the SPA is back online retrieve the crashdump data that " "was saved on the Bootflash of the supervisor." LOG_STD_RECUR_ACTION |
|
SPA_IPSEC-3-SKIP_SPI |
3-Error |
[chars]: Skipping SPI Init. |
SPI Initialization will be skipped. This is a debugging feature. |
ws-ipsec-3 |
LOG_STD_NO_ACTION |
|
SPA_IPSEC-3-SPA_BUS |
3-Error |
[chars]: SPA Bus timeout. |
There was a timeout trying to access the SPA. Please reseat the board and try again. |
spa-ipsec-2g |
LOG_STD_RECUR_ACTION |
|
SPA_LNM-2-REMEXCEED |
2-Critical |
Interface [chars] noise exceeded above removal threshold |
Noise on the link has exceeded above the threshold value configured for link removal |
- |
"This link requires administrative attention" |
|
SPA_LNM-2-REMEXCEEDLASTLINK |
2-Critical |
Interface [chars] Last link in bundle noise exceeded above removal threshold |
Noise on the link has exceeded above the threshold value configured for link removal. However this link is the last link in the multilink bundle and it is not removed from the service. |
- |
"This link requires administrative attention" |
|
SPA_LNM-2-REMFAILED |
2-Critical |
Interface [chars] failed to remove link from bundle |
Noise on the link has exceeded above the threshold value configured for link removal. However this link is not removed from the MLP bundle |
- |
"No Action required" |
|
SPA_LNM-2-REMIMPROVE |
2-Critical |
Interface [chars] noise improved below removal threshold |
Noise on the link has improved and is below the threshold value configured for link removal |
- |
"No Action required" |
|
SPA_LNM-2-REMOVE |
2-Critical |
Interface [chars] removed from bundle. Noise exceeded above remove threshold |
Noise on the link has crossed the threshold value configured for link removal. This link is taken out of the MLP bundle. This is critical status for the link. This link is under monitoring state and will be added to the bundle again when the noise level is below the configured value. |
- |
"This link requires administrative attention" |
|
SPA_LNM-2-RESTORE |
2-Critical |
Interface [chars] restored to bundle. Noise improved below removal threshold |
Noise on the link has improved below the threshold value configured for link removal. This link is restored back to MLP bundle. |
- |
"No action required" |
|
SPA_LNM-2-RESTOREFAILED |
2-Critical |
Interface [chars] failed to restore link to the bundle |
Noise on the link has improved and is below the threshold value configured for link removal. However the link restore back to the MLP bundle failed |
- |
"No Action required" |
|
SPA_LNM-3-GENEVENT |
3-Error |
[chars] |
An Error has occured in the link noise monitoring |
- |
"Copy the error message exactly as it appears " "and report it to your technical support representative" |
|
SPA_LNM-3-MAJWARNEXCEED |
3-Error |
Interface [chars] noise exceeded above major warning threshold |
Noise on the link has exceeded above the threshold value configured for major warning level |
- |
"This link requires administrative attention" |
|
SPA_LNM-3-MAJWARNIMPROVE |
3-Error |
Interface [chars] noise improved below major warning threshold |
Noise on the link has improved and is below the threshold value configured for major warning level |
- |
"No action required" |
|
SPA_LNM-3-MINWARNEXCEED |
3-Error |
Interface [chars] noise exceeded above minor warning threshold |
Noise on the link has exceeded above the threshold value configured for minor warning level |
- |
"This link requires administrative attention" |
|
SPA_LNM-3-MINWARNIMPROVE |
3-Error |
Interface [chars] noise improved below minor warning threshold |
Noise on the link has improved and is below the threshold value configured for minor warning level |
- |
"No action required" |
|
SPA_LNM-5-DISABLED |
5-Notice |
Interface [chars] noise monitoring disabled for [chars] |
Link Noise Monitoring has been disabled on the specified T1/E1 interface |
- |
"This is an information message to" "notify that Link Noise Monitoring has been disabled on the T1/E1 link." "No user action is required." |
|
SPA_LNM-5-ENABLED |
5-Notice |
Interface [chars] noise monitoring enabled for [chars] |
Link Noise Monitoring has been enabled on the specified T1/E1 interface |
- |
"This is an information message to" "notify that Link Noise Monitoring has been enabled on the T1/E1 link." "No user action is required." |
|
SPA_LOTR-3-CORRUPT |
3-Error |
Corrupt configuration unsupported [chars] [dec] encountered |
The OC3/STM1 RP driver running configuration is corrupted. |
asr900-tdm-combo |
SPA_LOTR_INTERNAL_SW_ERROR_ACTION |
|
SPA_LOTR-3-CREATE_FAIL |
3-Error |
Failed to create [chars] : slot/bay:[dec]/[dec] |
The channelized SPA controller descriptor block creation failed. Check the amount of available system memory. |
asr900-tdm-combo |
LOG_STD_SH_TECH_ACTION |
|
SPA_LOTR-3-DCC_FAILURE |
3-Error |
Failed to retrieve DCC info for [dec]/[dec]/[dec] |
\n The DCC info could not be retrieved |
asr900-tdm-combo |
SPA_LOTR_INTERNAL_SW_ERROR_ACTION |
|
SPA_LOTR-3-ERROR |
3-Error |
Failed to create for [chars] : slot/bay:[dec]/[dec] |
The 1Z 8S SPA/IM controller encountered an error. |
asr900-tdm-combo |
"Check the memory availabe in system and " LOG_STD_SH_TECH_ACTION |
|
SPA_LOTR-3-FATAL_ERROR |
3-Error |
Fatal error for [chars] : slot/bay:[dec]/[dec] |
The channelized SPA controller encountered a fatal error. |
asr900-tdm-combo |
LOG_STD_SH_TECH_ACTION |
|
SPA_LOTR-3-FRR_ERROR |
3-Error |
Error in handling FRR: [chars] [chars] [hec] [hec] |
Error in FRR processing. |
asr900-tdm-combo |
"This is a internal software error. If this error happened while " "configuring FRR try reconfiguring the interface. If the error " "persists or occurred during normal operation decode the traceback " "and " LOG_STD_ACTION |
|
SPA_LOTR-3-INTFC_FAILED |
3-Error |
Channel provisioning failed for [chars] |
Channel could not be provisioned on SPA for this interface interface corresoponding to that channel has been moved to down state. If this interface was provisoned using the user interface then it may not appear in the interface list. |
asr900-tdm-combo |
SPA_LOTR_INTERNAL_SW_ERROR_ACTION |
|
SPA_LOTR-3-INVALID_MAX_VC |
3-Error |
for[chars] |
invalid max vc for IM |
asr900-tdm-combo |
LOG_STD_SH_TECH_ACTION |
|
SPA_LOTR-3-INVALID_SPA_TYPE |
3-Error |
Invalid SPA type : slot/bay:[dec]/[dec] spa_type=[dec]. |
The channelized SPA type cannot be recognized by the version of Cisco IOS software currently running on the system. |
asr900-tdm-combo |
"Upgrade your system to a version of Cisco IOS software that supports " "this SPA type." |
|
SPA_LOTR-3-NULL |
3-Error |
[chars] |
The NULL pointer was detected when getting the data structure. |
asr900-tdm-combo |
SPA_LOTR_ENABLE_DEBUG_ACTION |
|
SPA_LOTR-3-NULL_CDB |
3-Error |
payload CDB is NULL for [dec]/[dec]/[dec] |
The payload cdb for the port is Null. |
asr900-tdm-combo |
SPA_LOTR_INTERNAL_SW_ERROR_ACTION |
|
SPA_LOTR-3-NULL_ETH_SUBBLOCK |
3-Error |
Ethernet subblock is null for [dec]/[dec] |
The ethernet subblock is NULL |
asr900-tdm-combo |
SPA_LOTR_INTERNAL_SW_ERROR_ACTION |
|
SPA_LOTR-3-NULL_INSTANCE |
3-Error |
Null [chars] instance for slot/bay/port:[dec]/[dec]/[dec] |
The instance pointer is NULL when getting data structure. |
asr900-tdm-combo |
SPA_LOTR_INTERNAL_SW_ERROR_ACTION |
|
SPA_LOTR-3-NULL_OPTICS_CDB |
3-Error |
Optic CDB is NULL for [dec]/[dec]/[dec] |
The optics cdb for the port is Null. |
asr900-tdm-combo |
SPA_LOTR_INTERNAL_SW_ERROR_ACTION |
|
SPA_LOTR-3-NULL_OPTICS_HWIDB |
3-Error |
Optic HWIDB is NULL for [dec]/[dec]/[dec] |
The optics hwidb for the port is Null. |
asr900-tdm-combo |
SPA_LOTR_INTERNAL_SW_ERROR_ACTION |
|
SPA_LOTR-3-NULL_SPA_PTR |
3-Error |
- |
Pointer to a SPA object is NULL. |
asr900-tdm-combo |
LOG_STD_SH_TECH_ACTION |
|
SPA_LOTR-3-NULL_SUBBLOCK |
3-Error |
Null ssb for [chars] |
The hwidb subblock is NULL. |
asr900-tdm-combo |
SPA_CHOCX_INTERNAL_SW_ERROR_ACTION |
|
SPA_LOTR-3-NULL_VC_INST |
3-Error |
for[chars] |
Pointer to VC INST is NULL. |
asr900-tdm-combo |
LOG_STD_SH_TECH_ACTION |
|
SPA_LOTR-3-RETURN_ERROR |
3-Error |
Return error for [chars]: return_value=[dec] |
Return error code received. |
asr900-tdm-combo |
SPA_LOTR_INTERNAL_SW_ERROR_ACTION |
|
SPA_LOTR-3-UNKNOWN_OPTION |
3-Error |
Received unknown [chars]: option=[dec] |
Unknown option received. |
asr900-tdm-combo |
SPA_LOTR_INTERNAL_SW_ERROR_ACTION |
|
SPA_LOTR-5-DEF_SUBRATE |
5-Notice |
[chars] [chars] |
Remote subrate configuration changed. |
asr900-tdm-combo |
"Inform the network operator that subrate configuration was changed " "by remote end." |
|
SPA_LOTR-5-SPA_MODE_IS |
5-Notice |
spa_mode of [dec]/[dec] is [chars] |
\n spa_mode is |
asr900-tdm-combo |
SPA_LOTR_INTERNAL_SW_ERROR_ACTION |
|
SPA_LOTR-6-XFP_OK |
6-Information |
[dec]/[dec]/[dec]: [chars] detected/inserted |
XFP has been detected or inserted in a port in Channelized SPA. |
asr900-tdm-combo |
"This is a information message no action required" |
|
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_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_NAM-3-NAM_SW_ERR |
3-Error |
NULL |
The SPA driver detected a software error condition on the SPA card. This might result in improper operation. |
spa-nam |
"The SPA driver has encountered a software error." "Please power down and reseat the indicated SPA card. " "Copy the error message exactly as it appears and " "open a case with the Technical Assistance Center " "via the Internet at " TAC_CASE_OPEN " or contact your Cisco technical support representative and provide " "the representative with the information you have gathered. Be sure to " "attach to your case the output of the <CmdBold>show logging<NoCmdBold> " "<CmdBold>show monitor event-log spa all<NoCmdBold> and " "<CmdBold>show tech-support<NoCmdBold> commands your troubleshooting " "logs and the specific error message." |
|
SPA_NGIO_ETHER_INTERNAL-3-SW_ERR |
3-Error |
NULL |
The module driver detected a software error condition on the module card. This might result in improper operation. |
lebowski-o2 |
"The module driver has encountered a software error." "Please power down and reseat the indicated module card. " "Copy the error message exactly as it appears and " "open a case with the Technical Assistance Center " "via the Internet at " TAC_CASE_OPEN " or contact your Cisco technical support representative and provide " "the representative with the information you have gathered. Be sure to " "attach to your case the output of the <CmdBold>show logging<NoCmdBold> " "<CmdBold>show monitor event-log module all<NoCmdBold> and " "<CmdBold>show tech-support<NoCmdBold> commands your troubleshooting " "logs and the specific error message." |
|
SPA_NGIO_UCSE-0-APP_MSG_EMER |
0-Emergency |
NULL |
The application running on the service module has encountered an emergency error. |
canisng-xe |
UCSE_APP_MSG_STD_ACTION |
|
SPA_NGIO_UCSE-1-APP_MSG_ALERT |
1-Alert |
NULL |
The application running on the service module has issued an alert. |
canisng-xe |
UCSE_APP_MSG_STD_ACTION |
|
SPA_NGIO_UCSE-2-APP_MSG_CRIT |
2-Critical |
NULL |
The application running on the service module has encountered a critical error. |
canisng-xe |
UCSE_APP_MSG_STD_ACTION |
|
SPA_NGIO_UCSE-2-CONFIGFAILED |
2-Critical |
UCSE Module [chars] \[chars]\ configuration failed |
The indicated configuration for the UCSE Module interface has failed. |
canisng-xe |
LOG_STD_RECUR_ACTION |
|
SPA_NGIO_UCSE-3-APP_MSG_ERR |
3-Error |
NULL |
The application running on the service module has encountered an error. |
canisng-xe |
UCSE_APP_MSG_STD_ACTION |
|
SPA_NGIO_UCSE-3-APP_RESET |
3-Error |
Application on UCSE Module [chars] has failed and requested a UCSE Module reset. |
The application running on the service module failed and as a result the UCSE Module will be restarted in order to recover from the communication failure with host. |
canisng-xe |
LOG_STD_NO_ACTION |
|
SPA_NGIO_UCSE-3-APP_STATUS |
3-Error |
Application on UCSE Module [chars] is [chars] |
The Application running on the service module has changed state. |
canisng-xe |
LOG_STD_NO_ACTION |
|
SPA_NGIO_UCSE-3-HW_ERR |
3-Error |
[chars]: A Hardware device error was detected by [chars] trying to recover the module by reload. |
An internal hardware device error has occurred on the module. The error message indicates the slot the module subslot the module type and the name of the hardware device. The module has been deactivated and reactivated to resolve the problem. If the error occurs more than five times within an hour no further attempts to reactivate the module will be made. This message is likely due to an unrecoverable hardware failure. |
canisng-xe |
"Perform OIR of the module located in the specified subslot. Before" " removing the module enter the <CmdBold>hw-module subslot" " stop<NoCmdBold> command. Remove the module wait 5 seconds and" " reinsert the module into the slot. If the problem persists copy " "the error message text exactly as it appears on the console or in " "the system log enter the <CmdBold>show diag <NoCmdBold> command " "contact your Cisco technical support representative and provide the " "representative with the gathered information." |
|
SPA_NGIO_UCSE-3-NGIO_MSG_VER_MISMATCH |
3-Error |
UCSE [chars] is using incorrect NGIO message version expected version = [dec] current version = [dec]. Please update |
UCSE SW is running with a software version that doesn't use the same NGIO message header version. This could happen if the wrong version of the software package for the module was installed in the system. |
canisng-xe |
"Find the appropriate software package for the module based on the " "Cisco IOS software version that the system is running. Follow the " "installation documentation that corresponds to your software version " "and platform to properly install the software package and correct the " "problem." |
|
SPA_NGIO_UCSE-3-PASSWORDRESET |
3-Error |
UCSE Module [chars] password reset [chars][chars] |
The password reset of the service module failed or is not supported. |
canisng-xe |
LOG_STD_RECUR_ACTION |
|
SPA_NGIO_UCSE-3-SE_RESET |
3-Error |
UCSE Module [chars] will be reset to recover from failure [chars]. |
The module is restarting to recover from the communication failure with host. |
canisng-xe |
LOG_STD_NO_ACTION |
|
SPA_NGIO_UCSE-3-SHUTDOWN_FAILED |
3-Error |
UCSE Module [chars] shutdown failed to be executed. |
The UCSE Module did not yet respond to the shutdown request. This is probably due to a bug. |
canisng-xe |
LOG_STD_NO_ACTION |
|
SPA_NGIO_UCSE-3-SPA_CPU_ERR |
3-Error |
[chars]: module CPU HW errors: [chars] |
An internal hardware device error has occurred on the module CPU. The error message indicates the modular card slot the module subslot the module type and the name of the hardware device. The module has been deactivated and reactivated to resolve the problem. If the error occurs more than five times within an hour no further attempts to reactivate the module will be made. This message is likely due to an unrecoverable hardware failure |
canisng-xe |
"If the module does not recover automatically perform OIR of the module " "located in the specified subslot. Before removing the module enter the " "<CmdBold>hw-module subslot stop<NoCmdBold> command. Remove the module " "wait 5 seconds and reinsert the module into the slot. If the problem " "persists copy the error message text exactly as it appears on the " "console or in the system log enter the <CmdBold>show tech-support" "<NoCmdBold> command contact your Cisco technical support representative " "and provide the representative with the gathered information." |
|
SPA_NGIO_UCSE-3-SW_ERR |
3-Error |
NULL |
The module driver detected a software error condition on the module card. This might result in improper operation. |
canisng-xe |
"The module driver has encountered a software error." "Please power down and reseat the indicated module card. " "Copy the error message exactly as it appears and " "open a case with the Technical Assistance Center " "via the Internet at " TAC_CASE_OPEN " or contact your Cisco technical support representative and provide " "the representative with the information you have gathered. Be sure to " "attach to your case the output of the <CmdBold>show logging<NoCmdBold> " "<CmdBold>show monitor event-log module all<NoCmdBold> and " "<CmdBold>show tech-support<NoCmdBold> commands your troubleshooting " "logs and the specific error message." |
|
SPA_NGIO_UCSE-4-APP_MSG_WARN |
4-Warning |
NULL |
The application running on the service module has issued a warning message. |
canisng-xe |
UCSE_APP_MSG_STD_ACTION |
|
SPA_NGIO_UCSE-4-BADPLATFORMINFO |
4-Warning |
UCSE Module [chars] platform information not received correctly. |
The platform and service module hardware information was not received correctly. |
canisng-xe |
LOG_STD_RECUR_ACTION |
|
SPA_NGIO_UCSE-5-APP_MSG_NOTICE |
5-Notice |
NULL |
The application running on the service module has issued a notice. |
canisng-xe |
"Refer to the software application documentation for more information." |
|
SPA_NGIO_UCSE-5-NEWPASSWORD |
5-Notice |
UCSE Module [chars] password changed to '[chars]'. |
The password of the service module was changed. |
canisng-xe |
LOG_STD_NO_ACTION |
|
SPA_NGIO_UCSE-5-RESTORE_EXT_IP |
5-Notice |
UCSE Module [chars] \ ucse ext ip address\ restored. |
The UCSE Module external IP address was restored after the system verified that the interface IP address changed. There are certain configuration requirements for the UCSE Module IP address and the default gateway IP address with the module interface IP address. The system has verified these requirements and restored the external IP address. |
canisng-xe |
LOG_STD_NO_ACTION |
|
SPA_NGIO_UCSE-5-RESTORE_IP |
5-Notice |
UCSE Module [chars] \UCSE Module ip address\ restored. |
The UCSE Module IP address was restored after the system verified that the interface IP address changed. There are certain configuration requirements for the service-engine IP address and the default gateway IP address with the module interface IP address. The system has verified these requirements and restored the IP address. |
canisng-xe |
LOG_STD_NO_ACTION |
|
SPA_NGIO_UCSE-5-RESTORED_DEF_GW |
5-Notice |
UCSE Module [chars] \UCSE ip default-gateway\ restored. |
The UCSE Module default gateway IP address was restored after the system verified that the interface IP address was changed. There are certain configuration requirements for the UCSE Module IP address and the default gateway IP address with the module interface IP address. The system has verified that the IP address for the UCSE Module IP default gateway is still on the same subnet as the UCSE Module IP address and therefore the default-gateway configuration is restored. |
canisng-xe |
LOG_STD_NO_ACTION |
|
SPA_NGIO_UCSE-5-SHUTDOWN_BUTTON |
5-Notice |
UCSE Module [chars] shutdown button was pressed shutdown initiated. |
The Shutdown button on the module was pressed and shutdown initiated. |
canisng-xe |
LOG_STD_NO_ACTION |
|
SPA_NGIO_UCSE-5-SHUTDOWN_DONE |
5-Notice |
UCSE Module [chars] shutdown complete |
The shutdown of the UCSE Module was completed. |
canisng-xe |
LOG_STD_NO_ACTION |
|
SPA_NGIO_UCSE-5-SHUTDOWN_NOT_DONE |
5-Notice |
UCSE Module [chars] shutdown was not done in a proper fashion: Reseating the module may corrupt the hard disk. |
The module was not properly shutdown before removal of the module. This could result in the corruption of the hard disk on the module. |
canisng-xe |
LOG_STD_NO_ACTION |
|
SPA_NGIO_UCSE-5-UNCONFIGURE_DEF_GW |
5-Notice |
UCSE Module [chars] \UCSE ip default-gateway\ unconfigured. |
The UCSE Module default gateway IP is unconfigured as interface IP address changed. |
canisng-xe |
LOG_STD_NO_ACTION |
|
SPA_NGIO_UCSE-5-UNCONFIGURE_EXT_IP |
5-Notice |
UCSE Module [chars] \UCSE Module ext ip address\ unconfigured. |
The UCSE Module external IP address is unconfigured as interface IP address changed. |
canisng-xe |
LOG_STD_NO_ACTION |
|
SPA_NGIO_UCSE-5-UNCONFIGURE_IP |
5-Notice |
UCSE Module [chars] \UCSE Module ip address\ unconfigured. |
The UCSE Module IP address is unconfigured as interface IP address changed. |
canisng-xe |
LOG_STD_NO_ACTION |
|
SPA_NGIO_UCSE-6-APP_MSG_INFO |
6-Information |
NULL |
The application running on the service module has issued a informational message. |
canisng-xe |
"Refer to the software application documentation for more information." |
|
SPA_NGIO_UCSE-7-APP_MSG_DEBUG |
7-Debug |
NULL |
The application running on the service module has displayed a debug message. |
canisng-xe |
"Refer to the software application documentation for more information." |
|
SPA_OBFL-3-APP_CONTEXT |
3-Error |
SPA OBFL Application Context is NULL |
The SPA Callback routine doesnt have valid OBFL Application context |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OBFL-3-APP_ENABLE |
3-Error |
[chars]: Failed to enable the [chars] application with OBFL INFRA |
SPA Failed to register the application with OBFL INFRA |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OBFL-3-APPLICATION |
3-Error |
SPA OBFL [chars] Application initialization failed for [chars] |
The SPA could not initialize OBFL Application |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OBFL-3-BAY_FAILED |
3-Error |
[chars]: Failed to get the bay slot [dec] bay [dec] |
Getting the SPA structure is failed for the slot/bay combination. |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OBFL-3-DEV_ADDR |
3-Error |
[chars]: SPA Blackbox EEPROM base address is NULL |
SPA specific code returned NULL for Blackbox EEPROM base address |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OBFL-3-DEVICE_DISABLE |
3-Error |
[chars]: Failed to disable the SPA OBFL Device |
Failed to disable the SPA OBFL device during OIR |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OBFL-3-DEVICE_ENABLE |
3-Error |
[chars]: Failed to enable the SPA OBFL device |
SPA OBFL failed to register the device with OBFL Infra |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OBFL-3-EEPROM_FAILED |
3-Error |
[chars]: Failed to read the [chars] from EEPROM |
Failed to read the particular details from SPA IDPROM. |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OBFL-3-ENV_ENQUEUE |
3-Error |
[chars]: Failed to enqueue the Enviornment event |
SPA OBFL Failed to enqueue the enviornment event to OBFL Infra. |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OBFL-3-ENV_FVT_FAILED |
3-Error |
[chars]: Enviornment Function Vector table is empty for [chars] monitoring |
Failed to get the enviornment vector table for the SPA |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OBFL-3-ENV_UDI |
3-Error |
[chars]: SPA OBFL Enviornment UDI structure is NULL |
OBFL Enviornment UDI structure is NULL for the SPA |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OBFL-3-ERASE_FAILED |
3-Error |
[chars]: Failed to erase the Blackbox EEPROM Address 0x[hec] offset 0x[hec] size 0x[hec] |
Erasing the Blackbox EEPROM failed. |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OBFL-3-ERRMSG_REG |
3-Error |
[chars]: Failed to register Errmsg Facility |
Failed to register the SPA OBFL errmsg facility with OBFL Infra |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OBFL-3-MALLOC_FAILED |
3-Error |
[chars]: Failed to allocate memory for [chars] |
Failed to allocate memeory for the SPA OBFL feature |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OBFL-3-OBFL_DEVINFO |
3-Error |
SPA OBFL Devinfo is NULL |
The SPA Callback routine doesnt have valid OBFL Devinfo |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OBFL-3-PLATFORM_VECTOR |
3-Error |
SPA OBFL Platform Vector Function is NULL |
The SPA doesnt have platform vector function |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OBFL-3-READ_FAILED |
3-Error |
[chars]: Failed to read the Blackbox EEPROM Address 0x[hec] offset 0x[hec] size 0x[hec] |
Reading the Blackbox EEPROM failed. |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OBFL-3-READ_SENSOR_FAILED |
3-Error |
[chars]: Failed to read the [chars] from sensor [dec] |
Failed to read the enviornment sensors |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OBFL-3-RESET_REASON_FAIL |
3-Error |
[chars]: Failed to get the SPA reset reason from RP due to IPC [chars]. |
SPA OBFL failed to get the SPA reset reason from RP. |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OBFL-3-SIZE_TOOBIG |
3-Error |
Size + Offset is beyond EEPROM boundary. Offset 0x[hec] size 0x[hec] |
The SPA Callback routine doesnt have valid EEPROM read/write bytes |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OBFL-3-SPA_NOTFOUND |
3-Error |
SPA Plugin failed slot [dec] bay [dec] |
Getting the SPA Plugin structure is failed. |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OBFL-3-SPA_OBFL_INFO |
3-Error |
[chars]: Failed to get the SPA OBFL [chars] info |
Failed to get the SPA OBFL info structure |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OBFL-3-VOLT_LIMIT_TABLE_FAILED |
3-Error |
[chars]: Failed to get the voltage limit table |
Failed to get voltage limit table for the SPA |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OBFL-3-WRITE_FAILED |
3-Error |
[chars]: Failed to write the Blackbox EEPROM Address 0x[hec] offset 0x[hec] size 0x[hec] |
Writing to Blackbox EEPROM failed. |
spa-obfl |
LOG_STD_ACTION |
|
SPA_OIR_STATE_CHANGE-2-OOS_AU_MEA |
2-Critical |
SPA [chars] in subslot 0/[dec] state transitioned to [chars]. |
The state transitioned to out of service \ autonomous and mismatch. An improper equipment \ is provisioned or inserted in the bay. |
asr900-csl |
LOG_STD_NO_ACTION |
|
SPA_OIR_STATE_CHANGE-2-OOS_AUMA_MEA_MT |
2-Critical |
SPA N/A in subslot 0/[dec] state transitioned to [chars]. |
The state transitioned to out of service \ autonomous management - mismatch and maintenance \ because the entity has been manually removed from \ service for a maintenance activity. Also the card \ may be inserted in the wrong slot. |
asr900-csl |
LOG_STD_NO_ACTION |
|
SPA_OIR_STATE_CHANGE-2-OOS_AUMA_UAS_MEA |
2-Critical |
SPA [chars] in subslot 0/[dec] state transitioned to [chars]. |
- |
asr900-csl |
LOG_STD_NO_ACTION |
|
SPA_OIR_STATE_CHANGE-6-EMPTY |
6-Information |
SPA [chars] in subslot 0/[dec] state transitioned to [chars]. |
The state is in empty since the subslot is \ neither provisioned nor is it phsically \ populated with any interface module. |
asr900-csl |
LOG_STD_NO_ACTION |
|
SPA_OIR_STATE_CHANGE-6-IS_NR |
6-Information |
SPA [chars] in subslot 0/[dec] state transitioned to [chars]. |
The state transitioned to in-service and \ normal. It is fully operational and shall \ provide provisioned functions. |
asr900-csl |
LOG_STD_NO_ACTION |
|
SPA_OIR_STATE_CHANGE-6-OOS_AU_FLT |
6-Information |
SPA [chars] in subslot 0/[dec] state transitioned to [chars]. |
The state transitioned to out of service \ autonomous - fault condition. |
asr900-csl |
LOG_STD_NO_ACTION |
|
SPA_OIR_STATE_CHANGE-6-OOS_AU_SWDL |
6-Information |
SPA [chars] in subslot 0/[dec] state transitioned to [chars]. |
The state transitioned to out of service \ autonomous and software download. |
asr900-csl |
LOG_STD_NO_ACTION |
|
SPA_OIR_STATE_CHANGE-6-OOS_AU_UEQ |
6-Information |
SPA N/A in subslot 0/[dec] state transitioned to [chars]. |
The state transitioned to out of service autonomous \ because the card is not physically present. |
asr900-csl |
LOG_STD_NO_ACTION |
|
SPA_OIR_STATE_CHANGE-6-OOS_AUMA_FLT_MT |
6-Information |
SPA [chars] in subslot 0/[dec] state transitioned to [chars]. |
The state transitioned to out of service \ autonomous management - unequipped and \ unassigned because the card is neither \ physically present nor provisioned in the database. |
asr900-csl |
LOG_STD_NO_ACTION |
|
SPA_OIR_STATE_CHANGE-6-OOS_AUMA_SWDL_MT |
6-Information |
SPA [chars] in subslot 0/[dec] state transitioned to [chars]. |
The state transitioned to out of service \ autonomous - software download and maintenance. \ The entity had been manually removed from \ for a maintenance activity. |
asr900-csl |
LOG_STD_NO_ACTION |
|
SPA_OIR_STATE_CHANGE-6-OOS_AUMA_UAS |
6-Information |
SPA [chars] in subslot 0/[dec] state transitioned to [chars]. |
The state transitioned to out of service \ autonomous management - unassigned because \ the card is not provisioned in the database. |
asr900-csl |
LOG_STD_NO_ACTION |
|
SPA_OIR_STATE_CHANGE-6-OOS_AUMA_UEQ_MT |
6-Information |
SPA [chars] in subslot 0/[dec] state transitioned to [chars]. |
The state transitioned to out of service \ autonomous - unequipped and maintenance. \ The card is not physically present. The entity \ has been manually removed from service for a \ maintenance activity. |
asr900-csl |
LOG_STD_NO_ACTION |
|
SPA_OIR_STATE_CHANGE-6-OOS_MA_MT |
6-Information |
SPA [chars] in subslot 0/[dec] state transitioned to [chars]. |
The state transitioned to out of service \ management. The entity had been manually \ removed from service for a maintenance activity \ but still performs its provisioned functions. |
asr900-csl |
LOG_STD_NO_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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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_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_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_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-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-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-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-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-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-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-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-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_PLIM-3-ERRMSG |
3-Error |
[chars] [chars] |
The error message in parentheses was logged by the SPA. |
- |
SPA_STD_SH_TECH_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_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-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-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-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-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-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-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-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-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-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-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-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-INIT_PORT |
3-Error |
[chars] PLIM client IPC port has not been initialized. |
- |
spa-ser-infra |
show ipc status |
|
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-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-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-SW_ERROR |
3-Error |
NULL |
- |
spa-ser-infra |
LOG_STD_ACTION |
|
SPA_PLIM-3-SW_ERROR |
3-Error |
NULL |
- |
spa-ser-infra |
LOG_STD_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-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-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_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-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-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-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_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_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_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-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-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-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-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-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-3-ENV_INIT |
3-Error |
[chars]: Environment monitoring initialization 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-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-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-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-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-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_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-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-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-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-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-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-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_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_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_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_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-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-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_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_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_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-IOFPGA_CREATE |
3-Error |
[chars]: Device IOFPGA creation failed. |
Can not allocate memory for IOFPGA structure. |
- |
LOG_STD_REDUCE_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-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-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-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-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-NULL_SPA_PTR |
3-Error |
- |
Pointer to a SPA object is NULL. |
spa-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-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-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-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-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-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-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-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_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_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-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-SPI4_INIT |
3-Error |
[chars]: SPI4 initializaion failed. |
- |
- |
LOG_STD_SH_TECH_ACTION |
|
SPA_PLUGIN-3-SPI4_INIT |
3-Error |
[chars]: SPI4 initializaion failed. |
- |
- |
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-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-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 |
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_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-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-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-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_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_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-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-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-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-6-FIRMWARE_APPS_DOWNLOADING |
6-Information |
[chars]: Downloading SPA firmware application [chars]... |
Downloading SPA firmware application . |
- |
"None. Information only." |
|
SPA_PLUGIN-6-FIRMWARE_APPS_DOWNLOADING |
6-Information |
[chars]: Downloading SPA firmware application [chars]... |
Downloading SPA firmware application . |
- |
"None. Information only." |
|
SPA_PLUGIN-6-FIRMWARE_DOWNLOADING |
6-Information |
[chars]: Downloading SPA firmware [chars]... |
Downloading SPA firmware. |
- |
"None. Information only." |
|
SPA_PLUGIN-6-FIRMWARE_DOWNLOADING |
6-Information |
[chars]: Downloading SPA firmware [chars]... |
Downloading SPA firmware. |
- |
"None. Information only." |
|
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-6-SPI4_SYNC |
6-Information |
[chars]: SPI4 bus synchronization achieved. |
SPI4 bus between modular services card and SPA is synchronized. |
- |
"None. Information only." |
|
SPA_SE1-3-APPL_BOOT_ERR |
3-Error |
[chars]: Application boot error detected [chars] with error [chars] error code = 0x[hec]. |
Service SPA application error was detected during booting of the SPA. |
spa-butler-all |
BUTLER_APPBOOT_ERROR_STD_ACTION |
|
SPA_SE1-3-APPL_BOOT_TIMEOUT |
3-Error |
[chars]: Timeout booting application image. |
Initialization of service SPA timed out during booting of the sipspawmak9 sub-package. The system will attempt to reload the SPA to recover from the failure. |
spa-butler-all |
BUTLER_APPBOOT_ERROR_STD_ACTION |
|
SPA_SE1-3-BOOTFLASH_DEBUG_MODE |
3-Error |
Service engine [chars] has been booted in bootflash debug mode. This is an engineering use only mode and some or all of the SPA functions could be disabled. |
The SPA was booted with <CmdBold>test hw-module subslot<NoCmdBold> <CmdArg>bay_num<NoCmdArg> <CmdBold>bootflash debug enable<NoCmdBold> configured. Disable this mode and reload the SPA for normal SPA operation. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SE1-3-CHECK_SPA_CONNECTOR |
3-Error |
[chars]: SPI4 error was detected during bootup automatic reload operation will be attempted for recovering the SPA. Please make sure that the SPA is secured properly in the SIP slot. |
SPI4 error has occurred during SPA bootup. The SPA has been deactivated and reactivated to resolve the problem. If the error occurs more than five times within an hour no further attempts to reactivate the SPA will be made. This message is likely due to bad connection of the SPA connector with the SIP slot. |
spa-butler-all |
"Pull out and reinsert the SPA to make secure connection " "with the SIP slot. Before removing the SPA make sure to stop the SPA " "by entering the <CmdBold>hw-module subslot<NoCmdBold> <CmdArg>slot#/" "subslot#<NoCmdArg> <CmdBold>stop<NoCmdBold> command. Remove the SPA " "wait 5 seconds and reinsert the SPA into the SIP. If the problem " "persists check for physical damage in the connector of both SPA and " "SIP. If no damage is visible then copy the error message exactly as it " "appears and gather the output from the <CmdBold>show hw-module subslot" "<NoCmdBold> <CmdArg>bay_num<NoCmdArg> <CmdBold>tech-support<NoCmdBold> " "command from the SIP console then contact your Cisco technical support " "representative with the gathered information." |
|
SPA_SE1-3-CHECKING_DISK |
3-Error |
[chars]: Disk is being checked because of previous unclean shutdown of the SPA or mount count limit reached. Boot time will take longer because of this operation e.g. 5 to 7 minute for a 250GB disk. |
Checking of the disk file system is being performed to correct any error due to unclean shutdown of the SPA. Make sure that the SPA is properly shutdown before removing it from the system to prevent file system corruption. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SE1-3-DEFAULT_APPL_BOOT_TIMEOUT |
3-Error |
[chars]: Timeout booting the default application image will attempt to boot the helper image. |
Initialization of service SPA timed out during booting of the default application image the system will attempt to recover from the failure by trying to boot the helper image. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SE1-3-DISK_CHECK_ERROR |
3-Error |
[chars]: Disk file system check error detected manual execution of disk checking operation will be required to correct this problem. The SPA will continue operating with reduced disk space. |
An error was detected during automatic checking operation of disk file system integrity. The affected disk partition won't be mounted and this will prevent the SPA from operating under normal conditions. The ability to store error logging on the disk might not be available and any debugging information could be lost after a SPA reload. Performance of the SPA might also get affected because of the reduced memory storage. |
spa-butler-all |
BUTLER_DISK_FS_ERROR_STD_ACTION |
|
SPA_SE1-3-DISK_CHECKING_TIMEOUT |
3-Error |
[chars]: Timeout checking the disk after more than [dec] seconds. Another attempt to check the disk will be done after the SPA reload. |
The disk checking operation has not completed in the expected time frame. To recover from possible disk checking failure the SPA will be reloaded to allow a retry of the disk checking operation. |
spa-butler-all |
BUTLER_DISK_FS_ERROR_STD_ACTION |
|
SPA_SE1-3-DISK_MOUNT_ERROR |
3-Error |
[chars]: Disk mount error detected manual execution of disk checking operation might be required to correct this problem. The SPA will continue operating with reduced disk space. |
Error were detected during mounting operation of disk partition. The affected disk partition won't be mounted this will prevent the SPA from operating at normal condition. Capability to store error logging on the disk might not be available and any debugging information could be lost after SPA reload. Performance of the SPA might also get affected because of the reduced memory storage. |
spa-butler-all |
BUTLER_DISK_FS_ERROR_STD_ACTION |
|
SPA_SE1-3-DISK_NOT_PRESENT |
3-Error |
[chars]: Cannot detect the presence of disk drive on the SPA. Please check for loose cable connection to the drive. The SPA will continue operating without the disk. |
The disk was not detected by the SPA during bootup and this will prevent the SPA from operating under normal conditions. The ability to store error logging on the disk will not be available and any debugging information will be lost after a SPA reload. Performance of the SPA might also get affected because of reduced memory storage. |
spa-butler-all |
BUTLER_DISK_STATE_ERROR_STD_ACTION |
|
SPA_SE1-3-DISK_UNFORMATTED |
3-Error |
[chars]: The disk drive on the SPA it is not formatted. The SPA cannot use an unformatted disk. Please follow instructions in the Cisco IOS installation and configuration guide to perform the manual format operation. The SPA will continue operating without the disk. |
The disk was not formatted and this will prevent the SPA from operating under normal conditions. The ability to store error logging on the disk will not be available and any debugging information will be lost after a SPA reload. Performance of the SPA might also get affected because of the reduced memory storage. |
spa-butler-all |
"Follow the instructions on the Cisco IOS installation and configuration " "guide to format the disk drive to correct this problem." |
|
SPA_SE1-3-DISK_UNKNOWN_STATE |
3-Error |
[chars]: The disk drive on the SPA is in a unknown operational state. Check for a loose cable connection to the drive. The SPA will continue operating without the disk. |
The disk was in an unknown operational state during SPA bootup and this will prevent the SPA from operating under normal conditions. The ability to store error logging on the disk will not be available and any debugging information will be lost after a SPA reload. Performance of the SPA might also get affected because of the reduced memory storage. |
spa-butler-all |
BUTLER_DISK_STATE_ERROR_STD_ACTION |
|
SPA_SE1-3-HELPER_BOOT_ERR |
3-Error |
[chars]: Helper image boot error detected [chars] error code = 0x[hec]. |
Service SPA helper image error was detected during booting of the SPA. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SE1-3-MAINTENANCE_MODE |
3-Error |
Service engine [chars] has been booted in maintenance mode. This is an engineering use only mode and some or all of the SPA functions could be disabled. |
The SPA was booted with <CmdBold>test hw-module subslot<NoCmdBold> <CmdArg>subslot#<NoCmdArg> <CmdBold>maintenance-mode enable<NoCmdBold> configured. Disable this mode and reload the SPA for normal SPA operation |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SE1-3-MEM_CPU_BIST_ERR |
3-Error |
[chars]: CPU BIST failure detected with error [chars] error code = 0x[hec]. |
The service SPA CPU Build-In Self Test BIST to check memory used |
- |
BUTLER_MEM_ERROR_STD_ACTION |
|
SPA_SE1-3-MEM_INIT_ERR |
3-Error |
[chars]: memory init failure occurred [chars] with error [chars] error code = 0x[hec]. |
The service SPA memory initialization procedure failed. |
- |
BUTLER_MEM_ERROR_STD_ACTION |
|
SPA_SE1-3-ROMMON_BOOT_ERR |
3-Error |
[chars]: ROMMON boot error detected [chars] - [chars] |
Service SPA ROMMON error was detected during booting of the SPA. The system will attempt to reload the SPA to recover from the failure. |
spa-butler-all |
BUTLER_ROMMON_ERROR_STD_ACTION |
|
SPA_SE1-3-ROMMON_BOOT_TIMEOUT |
3-Error |
[chars]: Timeout booting ROMMON image in [chars] state [chars] - [chars] |
Initialization of service SPA timed out during booting of the ROMMON image the system will now attempt to reload the SPA to recover from the failure. |
spa-butler-all |
BUTLER_ROMMON_ERROR_STD_ACTION |
|
SPA_SE1-3-ROMMON_IMG_RECOVER |
3-Error |
[chars]: ROMMON boot failed recovering ROMMON image with backup copy. |
A service SPA ROMMON error was detected during booting of the SPA. An attempt to re-program the ROMMON image will be performed to recover from this failure. This problem could have been caused by a previous interruption of the ROMMON FPD upgrade operation. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SE1-3-ROMMON_SPI4SYNC_TIMEOUT |
3-Error |
[chars]: Timeout getting SPI4 sync from ROMMON |
Initialization of the service SPA timed out after failing to get SPI4 sync. The system will attempt to reload the SPA to recover from the failure. |
spa-butler-all |
BUTLER_ROMMON_ERROR_STD_ACTION |
|
SPA_SE1-3-SKIPPED_DISK_MOUNT |
3-Error |
[chars]: Disk mounting operation has been skipped for manual disk repair operation. Please follow the procedures on hardware configuration guide on how to enter into service engine console to continue with the disk repair operation. |
The SPA was configured to not mount the disk after a reload operation. This is the initial step to prepare the SPA for manual disk repair operation. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SE1-3-SW_ERR |
3-Error |
NULL |
The SPA driver detected a software error condition on the SPA card. This might result in improper operation. |
spa-butler-all |
"The SPA driver has encountered a software error. Power down and reseat " "the indicated SPA card. If the problem persists copy the error message " "exactly as it appears on the console and open a case with the Technical " "Assistance Center via the Internet at " TAC_CASE_OPEN " or contact your " "Cisco technical support representative and provide the representative " "with the information you have gathered. Be sure to attach to your case " "the output of the <CmdBold>show logging<NoCmdBold> " "<CmdBold>show monitor event-log spa all<NoCmdBold> and " "<CmdBold>show tech-support<NoCmdBold> commands your troubleshooting " "logs and the specific error message." |
|
SPA_SE1-3-SYSINIT_FAILURE |
3-Error |
[chars]: System init failure was detected during bootup - [chars]. SPA will be disabled because of this failure. |
A failure was detected during system bootup of the SPA. The SPA has been deactivated because of the problem. |
spa-butler-all |
"Copy the error message exactly as it appears on the console and gather " "the output from the <CmdBold>show hw-module subslot<NoCmdBold> <CmdArg>" "bay_num<NoCmdArg> <CmdBold>tech-support<NoCmdBold> command from the " "SIP console. Contact your Cisco technical support representative with " "the gathered information." |
|
SPA_SE1-5-BOOTING_DEFAULT_APPL |
5-Notice |
[chars]: booting the default application image. |
The service SPA is booting the default application image from disk. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SE1-5-BOOTING_HELPER |
5-Notice |
[chars]: booting the helper image. |
The service SPA is booting the helper image from bootflash. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SE1-5-BOOTING_HOST_IMAGE |
5-Notice |
[chars]: booting application image downloaded from host. |
The service SPA is booting the default application image from disk. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SE1-5-NO_APPL_IN_DISK |
5-Notice |
[chars]: no application image was found in disk drive. |
The disk driver in service SPA doesn't have a valid application image. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SE1-5-NO_VALID_PARTITION |
5-Notice |
[chars]: no valid partition was found in disk drive [chars] error code = 0x[hec]. |
The disk driver in service SPA doesn't have valid partition. |
spa-butler-all |
"Follow the instructions on the Cisco IOS installation and configuration " "guide to format the disk drive to correct this problem." |
|
SPA_SERIAL_IM-3-DPIDX_LKUP_ERR |
3-Error |
Failed to retrieve datapath identifier for interface [chars] |
The SPA driver is not able to retrieve the datapath identifier for the interface specified in the message. This indicates a software error. |
wolfeisland-sw |
LOG_STD_NO_ACTION |
|
SPA_SERIAL_IM-3-IM_LIMIT_EXCEEDED |
3-Error |
The system supports a maximum of two serial Interface Modules. Additional modules will not be operational. Check the output of 'show platform' for details. |
Failed to create tty. |
wolfeisland-sw |
LOG_STD_ACTION |
|
SPA_SERIAL_IM-3-INVALID_TXRX |
3-Error |
[chars] doesn't support different tx speed [dec] and rx speed [dec] |
The software does not support different tx speed and rx speed |
wolfeisland-sw |
"Configure the tx speed and rx speed to be equivalent." |
|
SPA_SERIAL_IM-3-MSG_ENQUEUE_ERROR |
3-Error |
[chars] |
Failed to enqueue a message. |
wolfeisland-sw |
LOG_STD_ACTION |
|
SPA_SERIAL_IM-3-NULL_DATA_STRUCTURE |
3-Error |
NULL pointer detected: [chars] |
A software error occured and SPA driver is not able to retrieve the data structure mentioned in the message. |
wolfeisland-sw |
LOG_STD_ACTION |
|
SPA_SERIAL_IM-3-PROCESS_FAIL |
3-Error |
process creation failed for [chars] |
The Periodic one second process creation failed. This indicates a software error. |
wolfeisland-sw |
LOG_STD_ACTION |
|
SPA_SERIAL_IM-3-SERIAL_SUBBLOCK_ALLOC_FAIL |
3-Error |
Failed to create serial subblock at : [chars]: [chars]\n |
Failed to create serial subblock |
wolfeisland-sw |
LOG_STD_ACTION |
|
SPA_SERIAL_IM-3-TDL_SEND_FAIL |
3-Error |
[chars] |
Failed to send TDL message. |
wolfeisland-sw |
LOG_STD_ACTION |
|
SPA_SERIAL_IM-3-UNKNOWN_ENCAP |
3-Error |
unknown encap type [dec] in serial pak handler |
A software error occured and SPA driver encounterd unknown encapsulation mentioned in the message |
wolfeisland-sw |
LOG_STD_ACTION |
|
SPA_SERIAL_IM-3-UNSUPPORTED_DATA |
3-Error |
common_str_empty_str |
A software error occured and SPA driver encounterd unsupported data mentioned in the message |
wolfeisland-sw |
LOG_STD_ACTION |
|
SPA_SERIAL_IM-3-UNSUPPORTED_SPA_TYPE |
3-Error |
Unsupported spa type: [dec] |
Failed to create an interface hwidb. |
wolfeisland-sw |
LOG_STD_ACTION |
|
SPA_SERIAL_IM-3-VLAN_ID_NONZERO |
3-Error |
VLAN identifier is not zero before allocation for interface [chars] |
The SPA driver is seeing non zero VLAN identifier before allocating new vlan identifier for the interface specified in the message. This indicates a software error. |
wolfeisland-sw |
LOG_STD_NO_ACTION |
|
SPA_SRVCS_ENGINE-0-APP_MSG_EMER |
0-Emergency |
NULL |
The application running on the service SPA has encountered an emergency error. |
spa-butler-all |
SE_APP_MSG_STD_ACTION |
|
SPA_SRVCS_ENGINE-1-APP_MSG_ALERT |
1-Alert |
NULL |
The application running on the service SPA has issued an alert. |
spa-butler-all |
SE_APP_MSG_STD_ACTION |
|
SPA_SRVCS_ENGINE-2-APP_MSG_CRIT |
2-Critical |
NULL |
The application running on the service SPA has encountered a critical error. |
spa-butler-all |
SE_APP_MSG_STD_ACTION |
|
SPA_SRVCS_ENGINE-2-CONFIGFAILED |
2-Critical |
Service Engine [chars] \[chars]\ configuration failed |
The indicated configuration for the service-engine interface has failed. |
spa-butler-all |
LOG_STD_RECUR_ACTION |
|
SPA_SRVCS_ENGINE-3-APP_MSG_ERR |
3-Error |
NULL |
The application running on the service SPA has encountered an error. |
spa-butler-all |
SE_APP_MSG_STD_ACTION |
|
SPA_SRVCS_ENGINE-3-APP_RESET |
3-Error |
Application on service engine [chars] has failed and requested a service engine reset. |
The application running on the service SPA failed and as a result the service engine will be restarted in order to recover from the communication failure with host. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SRVCS_ENGINE-3-APP_STATUS |
3-Error |
Application on service engine [chars] is [chars] |
The Application running on the service SPA has changed state. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SRVCS_ENGINE-3-HW_ERR |
3-Error |
[chars]: A Hardware device error was detected by [chars] trying to recover the SPA by reload. |
An internal hardware device error has occurred on the services SPA. The error message indicates the SIP slot the SPA subslot the SPA type and the name of the hardware device. The SPA has been deactivated and reactivated to resolve the problem. If the error occurs more than five times within an hour no further attempts to reactivate the SPA will be made. This message is likely due to an unrecoverable hardware failure. |
spa-butler-all |
"Perform OIR of the SPA located in the specified subslot. Before removing " "the SPA enter the <CmdBold>hw-module subslot stop<NoCmdBold> command. " "Remove the SPA wait 5 seconds and reinsert the SPA into the SIP. If " "the problem persists copy the error message text exactly as it appears " "on the console or in the system log enter the <CmdBold>show diag" "<NoCmdBold> command contact your Cisco technical support representative " "and provide the representative with the gathered information." |
|
SPA_SRVCS_ENGINE-3-PASSWORDRESET |
3-Error |
Service Engine [chars] password reset [chars][chars] |
The password reset of the service SPA failed or is not supported. |
spa-butler-all |
LOG_STD_RECUR_ACTION |
|
SPA_SRVCS_ENGINE-3-RBCP_MSG_VER_MISMATCH |
3-Error |
Service Engine [chars] is using incorrect RBCP message version expected version = [dec] current version = [dec]. Please update |
The service engine is running with a software version that doesn't use the same RBCP message header version. This could happen if the wrong version of the software package for the SPA was installed in the system. |
spa-butler-all |
"Find the appropriate software package for the SPA based on the " "Cisco IOS software version that the system is running. Follow the " "installation documentation that corresponds to your software version " "and platform to properly install the software package and correct the " "problem." |
|
SPA_SRVCS_ENGINE-3-SE_RESET |
3-Error |
Service engine [chars] will be reset to recover from failure [chars]. |
The service SPA is restarting to recover from the communication failure with host. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SRVCS_ENGINE-3-SHUTDOWN_FAILED |
3-Error |
Service Engine [chars] shutdown failed to be executed. |
The service engine did not yet respond to the shutdown request. This is probably due to a bug. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SRVCS_ENGINE-3-SPA_CPU_ERR |
3-Error |
[chars]: SPA CPU HW errors: [chars] |
An internal hardware device error has occurred on the Services SPA CPU. The error message indicates the modular services card slot the SPA subslot the SPA type and the name of the hardware device. The SPA has been deactivated and reactivated to resolve the problem. If the error occurs more than five times within an hour no further attempts to reactivate the SPA will be made. This message is likely due to an unrecoverable hardware failure |
spa-butler-all |
"If the SPA does not recover automatically perform OIR of the SPA " "located in the specified subslot. Before removing the SPA enter the " "<CmdBold>hw-module subslot stop<NoCmdBold> command. Remove the SPA " "wait 5 seconds and reinsert the SPA into the SIP. If the problem " "persists copy the error message text exactly as it appears on the " "console or in the system log enter the <CmdBold>show tech-support" "<NoCmdBold> command contact your Cisco technical support representative " "and provide the representative with the gathered information." |
|
SPA_SRVCS_ENGINE-3-SW_ERR |
3-Error |
NULL |
The SPA driver detected a software error condition on the SPA card. This might result in improper operation. |
spa-butler-all |
"The SPA driver has encountered a software error." "Please power down and reseat the indicated SPA card. " "Copy the error message exactly as it appears and " "open a case with the Technical Assistance Center " "via the Internet at " TAC_CASE_OPEN " or contact your Cisco technical support representative and provide " "the representative with the information you have gathered. Be sure to " "attach to your case the output of the <CmdBold>show logging<NoCmdBold> " "<CmdBold>show monitor event-log spa all<NoCmdBold> and " "<CmdBold>show tech-support<NoCmdBold> commands your troubleshooting " "logs and the specific error message." |
|
SPA_SRVCS_ENGINE-4-APP_MSG_WARN |
4-Warning |
NULL |
The application running on the service SPA has issued a warning message. |
spa-butler-all |
SE_APP_MSG_STD_ACTION |
|
SPA_SRVCS_ENGINE-4-BADPLATFORMINFO |
4-Warning |
Service Engine [chars] platform information not received correctly. |
The platform and service SPA hardware information was not received correctly. |
spa-butler-all |
LOG_STD_RECUR_ACTION |
|
SPA_SRVCS_ENGINE-5-APP_MSG_NOTICE |
5-Notice |
NULL |
The application running on the service SPA has issued a notice. |
spa-butler-all |
"Refer to the software application documentation for more information." |
|
SPA_SRVCS_ENGINE-5-NEWPASSWORD |
5-Notice |
Service Engine [chars] password changed to '[chars]'. |
The password of the service SPA was changed. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SRVCS_ENGINE-5-RESTORE_EXT_IP |
5-Notice |
Service Engine [chars] \service-engine ext ip address\ restored. |
The service-engine external IP address was restored after the system verified that the interface IP address changed. There are certain configuration requirements for the service-engine IP address and the default gateway IP address with the SPA interface IP address. The system has verified these requirements and restored the external IP address. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SRVCS_ENGINE-5-RESTORE_IP |
5-Notice |
Service Engine [chars] \service-engine ip address\ restored. |
The service-engine IP address was restored after the system verified that the interface IP address changed. There are certain configuration requirements for the service-engine IP address and the default gateway IP address with the SPA interface IP address. The system has verified these requirements and restored the IP address. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SRVCS_ENGINE-5-RESTORED_DEF_GW |
5-Notice |
Service Engine [chars] \service-engine ip default-gateway\ restored. |
The service-engine default gateway IP address was restored after the system verified that the interface IP address was changed. There are certain configuration requirements for the service-engine IP address and the default gateway IP address with the SPA interface IP address. The system has verified that the IP address for the service-engine IP default gateway is still on the same subnet as the service-engine IP address and therefore the default-gateway configuration is restored. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SRVCS_ENGINE-5-SHUTDOWN_BUTTON |
5-Notice |
Service engine [chars] shutdown button was pressed shutdown initiated. |
The Shutdown button on the SPA was pressed and shutdown initiated. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SRVCS_ENGINE-5-SHUTDOWN_DONE |
5-Notice |
Service engine [chars] shutdown complete |
The shutdown of the service engine was completed. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SRVCS_ENGINE-5-SHUTDOWN_NOT_DONE |
5-Notice |
Service Engine [chars] shutdown was not done in a proper fashion: Reseating the SPA may corrupt the hard disk. |
The SPA was not properly shutdown before removal of the SPA. This could result in the corruption of the hard disk on the SPA. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SRVCS_ENGINE-5-UNCONFIGURE_DEF_GW |
5-Notice |
Service Engine [chars] \service-engine ip default-gateway\ unconfigured. |
The service-engine default gateway IP is unconfigured as interface IP address changed. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SRVCS_ENGINE-5-UNCONFIGURE_EXT_IP |
5-Notice |
Service Engine [chars] \service-engine ext ip address\ unconfigured. |
The service-engine external IP address is unconfigured as interface IP address changed. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SRVCS_ENGINE-5-UNCONFIGURE_IP |
5-Notice |
Service Engine [chars] \service-engine ip address\ unconfigured. |
The service-engine IP address is unconfigured as interface IP address changed. |
spa-butler-all |
LOG_STD_NO_ACTION |
|
SPA_SRVCS_ENGINE-6-APP_MSG_INFO |
6-Information |
NULL |
The application running on the service SPA has issued a informational message. |
spa-butler-all |
"Refer to the software application documentation for more information." |
|
SPA_SRVCS_ENGINE-7-APP_MSG_DEBUG |
7-Debug |
NULL |
The application running on the service SPA has displayed a debug message. |
spa-butler-all |
"Refer to the software application documentation for more information." |
|
SPA_SRVCS_IF-3-SRVCS_IF_SW_ERR |
3-Error |
NULL |
The SPA driver detected a software error condition on the SPA card. This might result in improper operation. |
spa-butler-all |
"The SPA driver has encountered a software error. Power down and reseat " "the indicated SPA card. If the problem persists copy the error message " "exactly as it appears in the console and open a case with the Technical " "Assistance Center via the Internet at " TAC_CASE_OPEN " or contact your " "Cisco technical support representative and provide the representative " "with the information you have gathered. Be sure to attach to your case " "the output of the <CmdBold>show logging<NoCmdBold> " "<CmdBold>show monitor event-log spa all<NoCmdBold> and " "<CmdBold>show tech-support<NoCmdBold> commands your troubleshooting " "logs and the specific error message." |
|
SPA_T3E3-3-LOVEFAIL |
3-Error |
[chars]: failed to send [chars] love letter |
A love letter status or configuration message could not be sent. |
spa-ser-t3e3 |
LOG_STD_SH_TECH_ACTION |
|
SPA_T3E3-3-MSGERR |
3-Error |
Illegal message type [dec] received for Interface [chars] |
An unknown message was received by RP. |
spa-ser-t3e3 |
LOG_STD_SH_TECH_ACTION |
|
SPA_T3E3-3-NO_SSB |
3-Error |
[chars]: Failed to get serial subblock. |
Serial subblock pointer is NULL. Internal software error. |
spa-ser-t3e3 |
LOG_STD_SH_TECH_ACTION |
|
SPA_T3E3-3-SSBINIT |
3-Error |
[chars]: Fail to initialize serial IDB |
Most common reason is lack of system memory. Earlier messages might indicate memory allocation failures. |
spa-ser-t3e3 |
LOG_STD_SH_TECH_ACTION |
|
SPA_T3E3-3-SUBRATE_FPGA_LOAD_FAILED2 |
3-Error |
[chars] Programming [chars] subrate FPGA failed. The FPGA image is corrupted. FPD upgrade has been attempted. SPA is shut. |
The indicated subrate FPGA image is corrupted even after FPD upgrade. The SPA is disabled until this problem is corrected. |
spa-ser-t3e3 |
"Verify the correctness of the FPD Image Package. Note that the FPD " "Image Package used in the upgrade should match the running Cisco IOS " "release. This can be verified by the use of <CmdBold>show upgrade " "fpd package default<NoCmdBold> command." |
|
SPA_T3E3-4-SUBRATE_FPGA_LOAD_FAILED |
4-Warning |
[chars] Programming [chars] subrate FPGA failed. The FPGA image is corrupted. One upgrade attempt is made. |
The indicated subrate FPGA image is corrupted and programming of FPGA failed. One upgrade attempt will be made to recover from the failure. |
- |
"Automatically upgrade the subrate FPGA image uses default FPD " "Image Package. The package should match the running Cisco IOS " "release. This can be verified by the use of <CmdBold>show upgrade " "fpd package default<NoCmdBold> command. If subrate FPGA failure " "persists after upgrade SPA is disabled. Ensure the package file " "is intact." |
|
SPA_T3E3-5-BERT |
5-Notice |
Interface [chars] BERT [chars] |
The spa t3e3 driver processed a BERT task. |
spa-ser-t3e3 |
"None this is just a notification upon completion of a BERT task." |
|
SPA_T3E3-5-DEF_SUBRATE |
5-Notice |
[chars] [chars] |
Remote subrate configuration changed |
spa-ser-t3e3 |
"Inform the network operator that subrate configuration changed by\n\ remote end" |
|
SPA_T3E3-5-MSG_ENQUEUE_ERR |
5-Notice |
[chars]: Unable to enqueue message to T3E3 SPA process |
The T3E3 SPA process message queue is full. |
- |
"Copy the error message exactly as it appears collect the output " "of 'show tech-support' command immediately and report it to your " "technical support representative." |
|
SPA_T3E3-5-MSG_QUEUE_ERR |
5-Notice |
[chars]: T3E3 process message queue not initialized. |
The T3E3 process message queue is not ready. |
- |
"Copy the error message exactly as it appears collect the output " "of 'show tech-support' command immediately and report it to your " "technical support representative." |
|
SPA_T3E3-5-MSG_UNEXPECTED_ERR |
5-Notice |
[chars]: Unexpected SPA message [dec]. |
SPA has been removed but still there are outstanding events. |
- |
"If the CPU utilization is high try to reduce the CPU utilization" |
|
SPA_TDMIM-3-ATM_IF_CREATE |
3-Error |
ATM interface creation on [chars] controller failed |
ATM interface creation on a controller failed. This indicates a software error. |
uea-im-tdm |
LOG_STD_ACTION |
|
SPA_TDMIM-3-ATM_LICENSE_NOT_ACTIVATED |
3-Error |
\nATM License is not yet activated. \ \nPlease configure 'license feature atm' \ \nand accept the EULA to activate the license.\n |
Failed to start ATM services as feature license is not installed or activated |
uea-im-tdm |
LOG_STD_ACTION |
|
SPA_TDMIM-3-DPIDX_LKUP_ERR |
3-Error |
Failed to retrieve datapath identifier for interface [chars] |
The SPA driver is not able to retrieve the datapath identifier for the interface specified in the message. This indicates a software error. |
uea-im-tdm |
LOG_STD_NO_ACTION |
|
SPA_TDMIM-3-ID_ALLOC_ERR |
3-Error |
failed to allocate ID for TDM IM |
Failed to allocate ID for TDM IM. |
uea-im-tdm |
LOG_STD_ACTION |
|
SPA_TDMIM-3-ID_INIT |
3-Error |
failed to initialize TDM IM ID table |
Failed to initialize TDM IM ID table. |
uea-im-tdm |
LOG_STD_ACTION |
|
SPA_TDMIM-3-MSG_ENQUEUE_ERROR |
3-Error |
[chars] |
Failed to enqueue a message. |
uea-im-tdm |
LOG_STD_ACTION |
|
SPA_TDMIM-3-NULL_DATA_STRUCTURE |
3-Error |
[chars] |
A software error occured and SPA driver is not able to retrieve the data structure mentioned in the message. |
uea-im-tdm |
LOG_STD_ACTION |
|
SPA_TDMIM-3-PROCESS_FAIL |
3-Error |
process creation failed for [chars] |
The Periodic one second process creation failed. This indicates a software error. |
uea-im-tdm |
LOG_STD_ACTION |
|
SPA_TDMIM-3-TDL_SEND_FAIL |
3-Error |
common_str_empty_str |
Failed to send TDL message. |
uea-im-tdm |
LOG_STD_ACTION |
|
SPA_TDMIM-3-UNSUPPORTED_DATA |
3-Error |
common_str_empty_str |
A software error occured and SPA driver encounterd unsupported data mentioned in the message |
uea-im-tdm |
LOG_STD_ACTION |
|
SPA_TDMIM-3-VLAN_ID_NONZERO |
3-Error |
VLAN identifier is not zero before allocation for interface [chars] |
The SPA driver is seeing non zero VLAN identifier before allocating new vlan identifier for the interface specified in the message. This indicates a software error. |
uea-im-tdm |
LOG_STD_NO_ACTION |
|
SPA_UCSE_IF-3-UCSE_IF_SW_ERR |
3-Error |
NULL |
The module driver detected a software error condition on the module card. This might result in improper operation. |
canisng-xe |
"The module driver has encountered a software error. Power down and " "reseat the indicated module card. If the problem persists copy the " "error message exactly as it appears in the console and open a case " "with the Technical Assistance Center via the Internet at " TAC_CASE_OPEN " or contact your " "Cisco technical support representative and provide the representative " "with the information you have gathered. Be sure to attach to your case " "the output of the <CmdBold>show logging<NoCmdBold> " "<CmdBold>show monitor event-trace spa all<NoCmdBold> and " "<CmdBold>show tech-support<NoCmdBold> commands your troubleshooting " "logs and the specific error message." |
|
SPA_WMA-3-WMA_SW_ERR |
3-Error |
NULL |
The SPA driver detected a software error condition on the SPA card. This might result in improper operation. |
spa-wma |
"The SPA driver has encountered a software error." "Please power down and reseat the indicated SPA card. " "Copy the error message exactly as it appears and " "open a case with the Technical Assistance Center " "via the Internet at " TAC_CASE_OPEN " or contact your Cisco technical support representative and provide " "the representative with the information you have gathered. Be sure to " "attach to your case the output of the <CmdBold>show logging<NoCmdBold> " "<CmdBold>show monitor event-log spa all<NoCmdBold> and " "<CmdBold>show tech-support<NoCmdBold> commands your troubleshooting " "logs and the specific error message." |
|
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-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-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_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_OVR |
0-Emergency |
[chars] slot/bay [dec]/[dec] temperature too high on sensor [dec] [dec]C |
MSG_SPA_TEMP_HIGH_EXP SPA shutdown has been overridden by configuration |
- |
MSG_SPA_TEMP_HIGH_ACTION |
|
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-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-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-1-AUTHENTICATION_FAIL |
1-Alert |
IM authentication failed for slot/bay [dec]/[dec] |
This Module may not have been manufactured by Cisco or with Cisco's authorization. This product may contain software that was copied in violation of Cisco's license terms. If your use of this product is the cause of a support issue Cisco may deny operation of the product support under your warranty or under a Cisco technical support program such as Smartnet. Please contact Cisco's Technical Assistance Center for more information. |
iomd-infra |
LOG_STD_ACTION |
|
SPA-1-DB_AUTHENTICATION_FAIL |
1-Alert |
Module daughter board authentication failed for slot/bay/board [dec]/[dec]/[dec] |
This daughter board may not have been manufactured by Cisco or with Cisco's authorization. This product may contain software that was copied in violation of Cisco's license terms. If your use of this product is the cause of a support issue Cisco may deny operation of the product support under your warranty or under a Cisco technical support program such as Smartnet. Please contact Cisco's Technical Assistance Center for more information. |
esg-io-infra |
LOG_STD_ACTION |
|
SPA-2-CELBRN_FPGA_MBE_MEMORY_FAIL |
2-Critical |
CELBRNFPGA Multi Bit Error in RAM memory for slot/bay [dec]/[dec] Fatal failure. Reloading the IM |
Soft errors are unintended changes to the values stored in SRAM’s configuration memory of FPGA caused by ionizing radiation. Please refer ‘Soft Error Mitigation Controller’ product guide PG036 for more information. Please contact Cisco's Technical Assistance Center for more information. |
spa-infra |
LOG_STD_ACTION |
|
SPA-2-CEMFPGA_MBE_MEMORY_FAIL |
2-Critical |
CEMFPGA Multi Bit Error in RAM memory for slot/bay [dec]/[dec] Fatal failure. Reloading the IM |
Soft errors are unintended changes to the values stored in SRAM’s configuration memory of FPGA caused by ionizing radiation. Please refer ‘Soft Error Mitigation Controller’ product guide PG036 for more information. Please contact Cisco's Technical Assistance Center for more information. |
spa-infra |
LOG_STD_ACTION |
|
SPA-2-IOFPGA_MBE_MEMORY_FAIL |
2-Critical |
IOFPGA Multi Bit Error in RAM memory for slot/bay [dec]/[dec] Fatal failure. Reloading the IM |
Soft errors are unintended changes to the values stored in SRAM’s configuration memory of FPGA caused by ionizing radiation. Please refer ‘Soft Error Mitigation Controller’ product guide PG036 for more information. Please contact Cisco's Technical Assistance Center for more information. |
spa-infra |
LOG_STD_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-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-2-TEMP_CRITICAL |
2-Critical |
[chars] slot/bay [dec]/[dec] temperature too high on sensor [dec] [dec]C. |
MSG_SPA_TEMP_HIGH_EXP Please correct immediately. |
- |
MSG_SPA_TEMP_HIGH_ACTION |
|
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_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_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-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-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-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-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-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-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-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-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-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_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_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-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-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-3-INITFAIL |
3-Error |
Initialization error |
A failure occurred during the initialization. |
spa-infra |
LOG_STD_REDUCE_ACTION |
|
SPA-3-INITFAIL |
3-Error |
Initialization error |
A failure occurred during the initialization. |
spa-infra |
LOG_STD_REDUCE_ACTION |
|
SPA-3-INITFAIL |
3-Error |
Initialization error |
A failure occurred during the initialization. |
spa-infra |
LOG_STD_REDUCE_ACTION |
|
SPA-3-MSG_PARSE_FAILURE |
3-Error |
Failed to parse incoming message from [chars] |
An incoming control message from an IO module failed to get parsed and as a result failed to get handled by the control process running on the host platform. This error message could occur when the software running on the module is incompatible with the host. A solution is to update the module software with a version that is the same or compatible with |
see tac details |
LOG_STD_ACTION |
|
SPA-3-SW_ERROR |
3-Error |
NULL |
- |
spa-infra |
LOG_STD_ACTION |
|
SPA-3-SW_ERROR |
3-Error |
NULL |
- |
spa-infra |
LOG_STD_ACTION |
|
SPA-3-SW_ERROR |
3-Error |
NULL |
- |
spa-infra |
LOG_STD_ACTION |
|
SPA-3-TEMP_SHUTDOWN |
3-Error |
[chars] slot/bay [dec]/[dec] temperature too high on sensor [dec] [dec]C. |
MSG_SPA_TEMP_HIGH_EXP The SPA has been shut down. |
- |
MSG_SPA_TEMP_HIGH_ACTION |
|
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-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-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-4-TEMP_SHUTDOWN_NONFATAL |
4-Warning |
[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_WARNING |
4-Warning |
[chars] temperature too high on sensor [dec] [dec]C. |
MSG_SPA_TEMP_HIGH_EXP |
- |
MSG_SPA_TEMP_HIGH_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-4-TEMP_WARNING |
4-Warning |
[chars] slot/bay [dec]/[dec] temperature too high on sensor [dec] [dec]C. |
MSG_SPA_TEMP_HIGH_EXP |
- |
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-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-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-VOLT_SHUTDOWN_NONFATAL |
4-Warning |
[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-5-CELBRN_FPGA_SBE_MEMORY_FAIL |
5-Notice |
CELBRNFPGA Single Bit Error in RAM memory for slot/bay [dec]/[dec] Auto Recovering the failure. |
Soft errors are unintended changes to the values stored in SRAM’s configuration memory of FPGA caused by ionizing radiation. Please refer ‘Soft Error Mitigation Controller’ product guide PG036 for more information. Please contact Cisco's Technical Assistance Center for more information. |
spa-infra |
LOG_STD_ACTION |
|
SPA-5-CEMFPGA_SBE_MEMORY_FAIL |
5-Notice |
CEMFPGA Single Bit Error in RAM memory for slot/bay [dec]/[dec] Auto Recovering the failure. |
Soft errors are unintended changes to the values stored in SRAM’s configuration memory of FPGA caused by ionizing radiation. Please refer ‘Soft Error Mitigation Controller’ product guide PG036 for more information. Please contact Cisco's Technical Assistance Center for more information. |
spa-infra |
LOG_STD_ACTION |
|
SPA-5-IOFPGA_SBE_MEMORY_FAIL |
5-Notice |
IOFPGA Single Bit Error in RAM memory for slot/bay [dec]/[dec] Auto Recovering the failure. |
Soft errors are unintended changes to the values stored in SRAM’s configuration memory of FPGA caused by ionizing radiation. Please refer ‘Soft Error Mitigation Controller’ product guide PG036 for more information. Please contact Cisco's Technical Assistance Center for more information. |
spa-infra |
LOG_STD_ACTION |
|
SPACP-3-BUFFER |
3-Error |
[chars]: Failed to allocate buffer for SPACP message. |
Can not allocate memory for SPACP message. |
spa-ipsec-2g |
LOG_STD_RECUR_ACTION |
|
SPACP-3-CREATE |
3-Error |
[chars]: SPA Bus Device creation failed. |
Can not allocate memory for SPA Bus structure. |
spa-ipsec-2g |
LOG_STD_RECUR_ACTION |
|
SPACP-3-INIT |
3-Error |
[chars]: Failed to initialize SPACP. [chars]. |
SPACP messaging could not be initialized because of the reason specific in the message text. |
spa-ipsec-2g |
LOG_STD_RECUR_ACTION |
|
SPACP-3-OPCODE |
3-Error |
[chars]: SPACP opcode 0x%04x unknown. |
A failure occurred when sending a command to the SPA indicated in the error message. |
spa-ipsec-2g |
SPA_CEMA_FAIL_ACTION |
|
SPACP-3-SEND |
3-Error |
[chars]: Failed to send SPACP message. |
Failed to send a message to the SPA. |
spa-ipsec-2g |
LOG_STD_RECUR_ACTION |
|
SPAN-3-MEM_UNAVAIL |
3-Error |
Memory was not available to perform the SPAN operation |
Unable to perform a SPAN operation because of a lack of memory |
- |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
SPAN-3-REDIR_HW_UNAVAIL |
3-Error |
Redirect hardware resource not available [chars] |
The system could not allocate resource for redirecting BPDUs. A possible cause of this condition is that all available redirect registers in PFC are used by other features. |
cat6000-l2 |
"Free up a redirect register in PFC by unconfiguring features " "that use redirect registers and retry allowing BPDUs for " "SPAN servicemodules. If Protocol Tunneling is configured " "on any ports then remove Protocol Tunneling configuration " "from all ports to free up one redirect register." |
|
SPAN-3-SESS_HW_UNAVAIL |
3-Error |
SPAN hardware resource not available [chars] |
The system could not allocate a SPAN hardware resource for the feature specified in the error message. A possible cause of this condition is that all available SPAN source sessions are already in use. The system can be configured with a maximum of two SPAN source sessions or one RSPAN source session |
- |
"Remove one of the existing SPAN or RSPAN source sessions " "and retry the operation." |
|
SPAN-3-UNKN_ERR |
3-Error |
An internal error occurred during a SPAN operation. |
SPAN detected an error in its internal operation. |
- |
"The error might be transient in which case trying the SPAN operation\n\ again might be successful. If this fails the switch might need to be\n\ reloaded for the desired operation to complete." |
|
SPAN-3-UNKN_ERR_PORT |
3-Error |
An internal error occurred when configuring SPAN on port [chars] |
SPAN detected an error in its internal operation. |
- |
"The error might be transient in which case trying the SPAN operation\n\ again might be successful. If this fails the switch might need to be\n\ reloaded for the desired operation to complete." |
|
SPAN-5-ERSPAN_ADJ_TUNNEL |
5-Notice |
ERSPAN Destination behind a tunnel. Shutting down session [dec] |
The next hop to the IP Address specified as the ERSPAN destination lies behind a tunnel. This configuration is not supported. ERSPAN session is shut down when such configuration is detected |
cat6000-l2 |
"Specify another IP address as the ERSPAN destination which " "does not have tunnel as the next-hop adjacency." |
|
SPAN-5-PKTCAP_START |
5-Notice |
Packet capture session [dec] started |
Packet capture is activated by user or after the scheduled time |
cat6000-l2 |
"Stop the capture when it is not required. You can change the rate of " "packets reaching CPU for capturing by configuring the rate-limit value " "in the monitor session type capture config mode. Protocol packets may " "get dropped if the capture traffic rate is high." |
|
SPAN-5-PKTCAP_STOP |
5-Notice |
Packet capture session [dec] ended [chars] [dec] packets captured |
Packet capture is stopped. This will happen if the capture buffer is full or if user stops the capture or if capture timeout happens. |
cat6000-l2 |
"Packet capture is stopped. You can export the capture buffer using " "the 'monitor capture <id> export buffer <url>' command. Buffer can " "be dislayed on the console also. Delete the capture session if it " "is no longer required." |
|
SPAN-6-SPAN_EGRESS_REPLICATION_MODE_CHANGE |
6-Information |
Span Egress HW Replication Mode Change Detected. Current replication mode for session [chars] is [chars] |
When auto detection of egress span replication mode is enabled the system will transition any available sessions to centralized mode when an distributed egress span incapable linecard is inserted. The system will transition back the available sessions to distributed egress span mode when the last distributed egress span incapable linecard is removed |
7600-l2 |
"To prevent a session switching back to distributed egress span" "modeuse the command monitor session egress replication-mode" "centralized" |
|
SPANTREE_FAST-7-PORT_FWD_UPLINK |
7-Debug |
[chars] [chars] moved to Forwarding UplinkFast. |
- |
- |
- |
|
SPANTREE_VLAN_SHIM-2-MAX_INSTANCE |
2-Critical |
Platform limit of [dec] STP instances exceeded. No instance created for [chars] port [chars]. |
- |
- |
- |
|
SPANTREE_VLAN_SHIM-3-ADD_REGISTRY_FAILED |
3-Error |
Subsystem [chars] fails to add callback function [chars] |
Other subsystem must have mistakenly add its own callback functions. This syslog is for debugging purpose. |
stp |
LOG_STD_NO_ACTION |
|
SPANTREE_VLAN_SW-2-MAX_INSTANCE |
2-Critical |
Platform limit of [dec] STP instances exceeded. No instance created for [chars] port [chars]. |
- |
- |
- |
|
SPANTREE-2-BLOCK_BPDUGUARD |
2-Critical |
Received BPDU on port [chars] with BPDU Guard enabled. Disabling port. |
A BPDU was received in the interface specified in the error message that has the spanning tree BPDU Guard feature enabled. As a result the interface was administratively shut down. |
pvst |
"Either remove the device sending BPDUs or disable the BPDU Guard " "feature. The BPDU Guard feature can be locally configured on the " "interface or globally configured on all ports that have portfast " " enabled. After the conflict has been resolved reenable the " "interface by entering the <CmdBold>no shutdown<NoCmdBold> command " "in interface configuration mode." |
|
SPANTREE-2-BLOCK_BPDUGUARD_VP |
2-Critical |
Received BPDU on port [chars] vlan [dec] with BPDU Guard enabled. Disabling vlan. |
A BPDU was received on the interface and vlan specified in the error message. The spanning tree BPDU Guard feature was enabled and configured to shutdown the vlan. As a result the vlan was placed in the error-disabled state. |
pvst |
"Either remove the device sending BPDUs or disable the BPDU Guard " "feature. The BPDU Guard feature can be locally configured on the " "interface or globally configured on all ports that have portfast " "enabled. After the conflict has been resolved reenable the " "interface/vlan by entering the <CmdBold>clear errdisable<NoCmdBold> " "command." |
|
SPANTREE-2-BLOCK_PVID_LOCAL |
2-Critical |
Blocking [chars] on [chars]. Inconsistent local vlan. |
The spanning tree port associate with the listed spanning tree instance and interface will be held in spanning tree blocking state until the Port VLAN ID PVID inconsistency is resolved. The listed spanning tree |
pvst |
"Verify that the configuration of the native VLAN id is consistent " "on the interfaces on each end of the 802.1Q trunk connection. " "Once corrected spanning tree will automatically unblock the interfaces " "as appropriate." |
|
SPANTREE-2-BLOCK_PVID_PEER |
2-Critical |
Blocking [chars] on [chars]. Inconsistent peer vlan. |
The spanning tree port associate with the listed spanning tree instance and interface will be held in spanning tree blocking state until the port VLAN Id PVID inconsistency is resolved. The listed spanning tree |
pvst |
"Verify that the configuration of the native VLAN id is consistent " "on the interfaces on each end of the 802.1Q trunk connection. " "Once corrected spanning tree will automatically unblock the interfaces " "as appropriate." |
|
SPANTREE-2-BRIDGE_ASSURANCE_BLOCK |
2-Critical |
Bridge Assurance blocking port [chars][chars]. |
BPDUs were not received from a neighboring switch on the interface that has spanning tree Bridge Assurance configured. As a result the interface was moved to the spanning tree Blocking state |
cosmos |
"Either disable Bridge Assurance configuration on the interface or " "make sure that the interface is connected to a L2 switch/bridge device" |
|
SPANTREE-2-BRIDGE_ASSURANCE_UNBLOCK |
2-Critical |
Bridge Assurance unblocking port [chars][chars]. |
The interface listed in the message has been restored to normal spanning tree state after receiving BPDUs from the neighboring L2 switch/bridge |
stp |
LOG_STD_NO_ACTION |
|
SPANTREE-2-CHNL_MISCFG |
2-Critical |
Detected loop due to etherchannel misconfiguration of [chars] [chars] |
A loop caused the misconfiguration of a channel group has been detected. An example of such a misconfiguration would be where the ports on one side of the etherchannel either aren't configured to be in the channel or failed to bundle for some reason while the other side has successfully bundled the ports into the etherchannel |
stp |
"Determine which local ports are involved using the command " "<CmdBold>show interfaces status err-disabled<noCmdBold> and then check " "etherchannel configuration on the remote device using the command " "<CmdBold>show etherchannel summary<noCmdBold> on the remote device. " "Once the configuration is corrected do " "<CmdBold>shutdown / no shutdown<noCmdBold> on the associated " "port-channel interface." |
|
SPANTREE-2-LOOPGUARD_BLOCK |
2-Critical |
Loop guard blocking port [chars] on [chars]. |
The spanning tree message age timer has expired because and no BPDUs were received from the designated bridge. Since this condition could be caused by an unidirectional link failure the interface is put into blocking state and marked as loop guard inconsistent in order to prevent possible loops from being created |
loopguard |
- |
|
SPANTREE-2-LOOPGUARD_CONFIG_CHANGE |
2-Critical |
Loop guard [chars] on port [chars]. |
The spanning tree loopguard configuration for the listed interface has been changed. If enabled the interface will be put into blocking state and marked as loopguard inconsistent when the message age timer expires because no BPDU were received from the designated bridge. This feature is mainly used to detect unidirectional links |
loopguard |
"Verify that this is the desired configuration for the listed interface." "Correct it if this is not the desired configuration otherwise no further " "action is required." |
|
SPANTREE-2-LOOPGUARD_UNBLOCK |
2-Critical |
Loop guard unblocking port [chars] on [chars]. |
The listed interface has received a BPDU and therefore if the inconsistency was due to an unidirectional link failure now the problem is not there anymore. The loop guard inconsistency is cleared for the interface which is taken out of the blocking state if appropriate. |
loopguard |
LOG_STD_NO_ACTION |
|
SPANTREE-2-NOMEM |
2-Critical |
Memory Allocation Failure - [chars]: [chars] |
The system could not allocate the memory that is required for the STP feature. This condition might indicate that more memory must be installed on the system. |
stp |
show tech-support and show logging |
|
SPANTREE-2-PVST_PEER_BLOCK |
2-Critical |
PVST+ peer detected on port [chars] |
PVST+ BPDUs are detected on the listed interface when MSTP PVST+ |
stp |
"Please make sure the PVST+ switch is removed from the network or " "enable the MSTP PVST Simulation feature." |
|
SPANTREE-2-PVST_PEER_UNBLOCK |
2-Critical |
Unblocking port [chars] |
The listed interface is no longer receiving the PVST+ BPDUs. The inconsistency is cleared and the interface returns to normal operation. |
stp |
LOG_STD_NO_ACTION |
|
SPANTREE-2-PVSTSIM_FAIL |
2-Critical |
Blocking [chars] port [chars]: Inconsitent [chars] PVST BPDU received on VLAN [dec] claiming root [dec]:[enet] |
When a MST switch is connected to a PVST+ switch the CIST MST00 |
stp |
"When STP is converging after a new switch or switch port is added" "to the topology this condition may happen transiently. The port" "unblocks automatically in such cases. If the port remains blocked" "identify the root bridge as reported in the message and configure" "a worse or better priority for the VLAN spanning tree consistent" "with the CIST role on the port of the MST switch. There could be more" "inconsistencies than the message indicates and the port will" "not recover until all such inconsistencies are cleared." "If you cannot determine which other VLANs have inconsistencies disable" "and reenable the port. This message will appear again and specify another" "VLAN with inconsistencies to be fixed. Repeat this process until all" "inconsistencies on all VLANs are cleared." |
|
SPANTREE-2-PVSTSIM_OK |
2-Critical |
PVST Simulation inconsistency cleared on port [chars]. |
The listed interface is no longer receiving PVST BPDUs advertising an information inconsistent with the CIST port information. The PVST Simulation Inconsistency is cleared and the interface returns to normal operation |
stp |
LOG_STD_NO_ACTION |
|
SPANTREE-2-RECV_1Q_NON_1QTRUNK |
2-Critical |
Received 802.1Q BPDU on non 802.1Q trunk [chars] [chars]. |
The listed interface on which a SSTP BPDU was received was in trunk mode but not using 802.1Q encapsulation. |
pvst |
"Verify that the configuration and operational state of the listed " "interface and that of the interface to which it is connected have " "the same mode access vs trunk. If mode is trunk verify the same " |
|
SPANTREE-2-RECV_BAD_TLV |
2-Critical |
Received SSTP BPDU with bad TLV on [chars] [chars]. |
The list interface received a SSTP BPDU that was missing the VLAN id tag. The BPDU is discarded. |
pvst |
LOG_STD_RECUR_ACTION |
|
SPANTREE-2-RECV_PVID_ERR |
2-Critical |
Received BPDU with inconsistent peer vlan id [dec] on [chars] [chars]. |
The listed interface received a SSTP BPDU that is tagged with a VLAN id that does not match the VLAN id on which the BPDU was received. This occurs when the native VLAN is not consistently configured on both ends of a 802.1Q trunk. |
pvst |
"Verify that the configuration of the native VLAN id is consistent " "on the interfaces on each end of the 802.1Q trunk connection. " "Once corrected spanning tree will automatically unblock the interfaces " "as appropriate." |
|
SPANTREE-2-ROOTGUARD_BLOCK |
2-Critical |
Root guard blocking port [chars] on [chars]. |
A BPDU was received on the listed interface which advertizes a superior spanning tree root bridge to that currently in use. The interface is put into blocking state and marked as root guard inconsistent in order to prevent a suboptimal spanning tree topology to form. |
rootguard |
"Issue the <CmdBold>show spanning-tree inconsistentports<noCmdBold> " "command to review the list of interfaces with root guard inconsistencies." "Determine why devices connected to the listed ports are sending " "BPDUs with a superior root bridge and take action to prevent further " "occurances. Once the bogus BPDUs have been stopped the interfaces will " "automatically recover and resume normal operation." "Make sure that it is appropriate to have root guard enabled on the " "interface." |
|
SPANTREE-2-ROOTGUARD_CONFIG_CHANGE |
2-Critical |
Root guard [chars] on port [chars]. |
The spanning tree root guard configuration for the listed interface has been changed. If enabled any BPDU received on ths interface which advertizes a superior spanning tree root bridge to that already in use will cause the interface to be put into blocking state and marked as root guard inconsistent. |
rootguard |
"Verify that this is the desired configuration for the listed interface." "Correct it if this is not the desired configuration otherwise no further " "action is required." |
|
SPANTREE-2-ROOTGUARD_UNBLOCK |
2-Critical |
Root guard unblocking port [chars] on [chars]. |
The listed interface is no longer receiving BPDUs advertizing a superior root bridge. The root guard inconsistency is cleared for the interface and then it is taken out of the blocking state if appropriate. |
rootguard |
LOG_STD_NO_ACTION |
|
SPANTREE-2-UNBLOCK_CONSIST_PORT |
2-Critical |
Unblocking [chars] on [chars]. Port consistency restored. |
The Port VLAN ID and/or Port Type inconsistencies have been resolved and spanning tree will now unblock the listed interface of the listed spanning tree instance as appropriate. |
pvst |
LOG_STD_NO_ACTION |
|
SPANTREE-3-BAD_PORTNUM_SIZE |
3-Error |
Rejected an attempt to set the port number field size to [dec] bits valid range is [dec] to [dec] bits. |
The spanning tree port identifier is a 16 bit wide field that is by default divided evenly between port priority and port number each sub field being 8 bits wide. This allows the port number field to represent port numbers between 1 and 255. However on systems with greater than 255 ports the size of port number portion of the port id must be increased to support the greater number of ports. This is done by the STP subsystem at system init time since the maximum number of ports on a particular platform will not change. This error would only occur due to an error in the platform specific code which caused it to request more or less |
stp |
"show version" |
|
SPANTREE-3-ERR_NO_UNIDIR_EDGE |
3-Error |
[chars]: Portfast disabled reverting to bidirectional mode |
Because UCP is for edge ports only portfast must be configured. This messageis typically seen when spanning-tree portfast is enabled on a port thenauthentication control-direction is set to inbound unidirectional and then |
stp |
"Re-enable portfast on the edge port. This will re-enable unidirectional""authentication control." |
|
SPANTREE-3-PORT_SELF_LOOPED |
3-Error |
[chars] disabled.- received BPDU src mac [enet] |
The source MAC address contained in a BPDU received on the listed interface matches the MAC address assigned to that interface This indicates the possibility that a port is looped back to itself possibly due to a diagnostic cable being plugged in. The interface will be administratively shutdown. |
stp |
"Check the interface configuration and any cable plugged into the " "interface. Once problem resolved re-enable interface by doing a " "no shutdown in the interface configuration." |
|
SPANTREE-3-PRESTD_NEIGH |
3-Error |
pre-standard MST interaction not configured [chars]. Please configure: |
The switch has received a pre-standard MST BPDU on a port that is not configured for pre-standard MST BPDU transmission. The switch will automatically adjust its mode of operation on this port and will start sending pre-standard BPDUs. However this auto-detection of pre-standard neighbors is not 100% accurate and it is recommended to configure explicitly the port for pre-standard MST BPDU transmission. This warning message will only be display once. |
stp |
"Configure 'spanning-tree mst pre-standard' on all the ports" "that are connected to switches running Cisco's pre-standard version " "of MST. It is recommended to migrate all the switches in the network to" "the IEEE standard MST version when it is possible." |
|
SPANTREE-4-PORT_NOT_FORWARDING |
4-Warning |
[chars] [chars] [chars] [chars] |
The port is not forwarding packets i.e it is not in a forwarding state |
- |
LOG_STD_ACTION |
|
SPANTREE-5-EXTENDED_SYSID |
5-Notice |
Extended SysId [chars] for type [chars] |
The extended system id feature has either enabled or disabled for the given type of spanning tree. If enabled the spanning tree instance identifier is stored in the lower portion of the bridge id priority field and this will cause the allowed values for the bridge priority to be limited to the range of 0 to 61440 in increments of 4096. If disabled the bridge id priority field consists entirely of the configured priority but some spanning tree features may not be available on a given platform i.e. 4096 vlan support. On some |
stp |
LOG_STD_NO_ACTION |
|
SPANTREE-5-ROOTCHANGE |
5-Notice |
Root Changed for [chars] [dec]: New Root Port is [chars]. New Root Mac Address is [enet] |
The Root has changed for an instance of spanning tree |
stp |
LOG_STD_NO_ACTION |
|
SPANTREE-5-TOPOTRAP |
5-Notice |
Topology Change Trap for [chars] [dec] |
A trap has been generated to indicate the change in topology |
stp |
LOG_STD_NO_ACTION |
|
SPANTREE-6-PORT_STATE |
6-Information |
Port [chars] instance [dec] moving from [chars] to [chars] |
The Spanning-Tree port has changed state. |
cosmos |
LOG_STD_NO_ACTION |
|
SPANTREE-6-PORTADD_ALL_VLANS |
6-Information |
[chars] added to all Vlans |
The interface has been added to all Vlans |
stp |
LOG_STD_NO_ACTION |
|
SPANTREE-6-PORTDEL_ALL_VLANS |
6-Information |
[chars] deleted from all Vlans |
The interface has been deleted from all Vlans |
stp |
LOG_STD_NO_ACTION |
|
SPANTREE-7-BLOCK_PORT_TYPE |
7-Debug |
Blocking [chars] on [chars]. Inconsistent port type. |
The listed interface is being held in spanning tree blocking state until the port type inconsistency is resolved. |
pvst |
"Verify that the configuration and operational state of the listed " "interface and that of the interface to which it is connected have " "the same mode access vs trunk. If mode is trunk verify the same " |
|
SPANTREE-7-PORTDEL_SUCCESS |
7-Debug |
[chars] deleted from Vlan [dec] |
The interface has been deleted from Vlan |
stp |
LOG_STD_NO_ACTION |
|
SPANTREE-7-RECV_1Q_NON_TRUNK |
7-Debug |
Received 802.1Q BPDU on non trunk [chars] [chars]. |
A SSTP BPDU was received on the listed interface that was not operationally a trunk. |
pvst |
"Verify that the configuration and operational state of the listed " "interface and that of the interface to which it is connected have " "the same mode access vs trunk. If mode is trunk verify the same " |
|
SPARC-3-DOWN |
3-Error |
SPARC process is not responding [chars] |
Failed to init calltracker record table. |
CallTracker |
"Disable calltracker first [no calltracker enable] enable it again." |
|
SPAWBCMTS-2-CARD_UP_DOWN |
2-Critical |
Card [chars] in bay [dec]/[dec]/[dec] is [chars]. |
Card up/down |
cmts-vpa |
LOG_STD_ACTION |
|
SPAWBCMTS-3-HWINITFAILED |
3-Error |
Error while initializing wideband group interface [chars] |
Wideband group interface initialization error |
cmts-vpa |
LOG_STD_ACTION |
|
SPAWBCMTS-3-INVALIDDATA |
3-Error |
Invalid information [chars] received by wideband software routine |
Wideband SPA software module was passed invalid information |
cmts-vpa |
LOG_STD_ACTION |
|
SPAWBCMTS-3-SPAHANDLERFAIL |
3-Error |
The SPA was unable to process/handle the received data |
Wideband SPA was unable to process/handle the received data |
cmts-vpa |
LOG_STD_ACTION |
|
SPAWBCMTS-4-SFP_INCOMP_REMOVE |
4-Warning |
[chars] the incompatible [chars] SFP removed from port [dec] |
SFP incompatible removed |
- |
- |
|
SPAWBCMTS-4-SFP_INCOMPATIBLE |
4-Warning |
[chars] [chars] SFP inserted in port [dec] incompatible with [chars] mode |
SFP incompatible with current mode |
- |
- |
|
SPAWBCMTS-4-SFP_INTERNAL |
4-Warning |
[chars] [chars] SFP inserted in port [dec]. \n\NOTE: This type of SFP is not officially supported. You configured \service \internal\ so enabled for lab test.\nIf this is not your intent please \disable the configuration and oir the SFP. |
SFP not supported offically. |
- |
- |
|
SPAWBCMTS-4-SFP_LINK_LOST |
4-Warning |
[chars] port [dec] link changed state to down |
Link status is down on SPA SFP |
cmts-vpa |
LOG_STD_ACTION |
|
SPAWBCMTS-4-SFP_LINK_OK |
4-Warning |
[chars] port [dec] link changed state to up |
Link status is up on SPA SFP |
cmts-vpa |
LOG_STD_ACTION |
|
SPAWBCMTS-4-SFP_MISSING |
4-Warning |
[chars] [chars] SFP missing from port [dec] |
SFP missing from SPA |
cmts-vpa |
LOG_STD_ACTION |
|
SPAWBCMTS-4-SFP_NOTSUPPORTED |
4-Warning |
[chars] [chars] SFP inserted in port [dec] is not supported and disabled |
SFP is not supported and disabled. |
cmts-vpa |
LOG_STD_ACTION |
|
SPAWBCMTS-4-SFP_OK |
4-Warning |
[chars] [chars] SFP inserted in port [dec] |
SFP inserted into the SPA |
cmts-vpa |
LOG_STD_ACTION |
|
SPAWBCMTS-4-SFP_UNINITIALIZED |
4-Warning |
[chars] [chars] SFP inserted in port [dec] failed initialization |
SFP initialization failed |
cmts-vpa |
LOG_STD_ACTION |
|
SPAWBCMTS-5-SWITCHOVER_PRI |
5-Notice |
primary portport 0 will be active for [chars] |
TenGigaEth link is being restored for primary port |
cmts-vpa |
"if not expected check secondary port in SPA" |
|
SPAWBCMTS-5-SWITCHOVER_SEC |
5-Notice |
secondary portport 1 will be active for [chars] |
TenGigaEth link is lost for primary port |
cmts-vpa |
"if not expected check secondary port in SPA" |
|
SPE2488-3-INITERR |
3-Error |
spe2488 chip initialization failed errcode=[dec]: [chars] |
required resources unavailable. |
osm-choc-ds3 |
"Reinsert the linecard. If still fails do\n\ 'test cwtlc show seeprom red' swap hardware and\n\ copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SPE2488-3-PARAERR |
3-Error |
spe2488 API failed errcode=[dec]: p1=[dec] p2=[dec] [chars] |
wrong parameters passed in when calling an API |
osm-choc-ds3 |
LOG_STD_ACTION |
|
SPE2488-3-POLLTO |
3-Error |
spe2488 indirect poll timeout. addr:[hex] |
hardware problem |
osm-choc-ds3 |
LOG_STD_ACTION |
|
SPE2488-3-PROVERR |
3-Error |
spe2488 channel provisioning failed slice:[dec] ch:[dec]: [chars] |
required resources unavailable. |
osm-choc-ds3 |
LOG_STD_ACTION |
|
SPE2488-3-RESETERR |
3-Error |
spe2488 chip reset failed errcode=[dec]: [chars] |
required resources unavailable. |
osm-choc-ds3 |
"REinsert the linecard.\n\ Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SPE2488-3-UNPROVERR |
3-Error |
spe2488 channel unprovisioning failed slice:[dec] ch:[dec]: [chars] |
required resources unavailable. |
osm-choc-ds3 |
LOG_STD_ACTION |
|
SPE-3-MSMGR_REGISTRATION_ERR |
3-Error |
Failed to register [chars] with Modem Service Manager |
Port Management failed to register with Modem Service Manager. |
- |
LOG_STD_NO_ACTION |
|
SPE-3-PM_DB_NO_MEM |
3-Error |
Failed to allocate [chars] for slot [dec] |
Port Management failed to allocate memory to create slot object. |
- |
LOG_STD_NO_ACTION |
|
SPE-3-PM_DIRECT_MODEM_QUERY_ERR |
3-Error |
Failed to find the response buffer for modem [chars] command |
Modem direct query responses could not find buffer to send data to router shelf. |
- |
LOG_STD_NO_ACTION |
|
SPE-3-PM_SLOT_NO_MODULES |
3-Error |
Database reported 0 modules for slot [dec] |
The card in this slot should contain multiple modules. However the database indicates that there are none. |
- |
LOG_STD_NO_ACTION |
|
SPE-3-SM_CRASHED |
3-Error |
SPE [chars] crashed |
The firmware running on the SPE aborted. |
- |
LOG_STD_NO_ACTION |
|
SPE-3-SM_DOWNLOAD_FAILED |
3-Error |
SPE [chars] is BAD - [chars]. |
The SPE failed to download and it will be marked BAD. |
- |
LOG_STD_NO_ACTION |
|
SPE-3-SM_POST_FAILED |
3-Error |
SPE [chars] is BAD. |
The SPE failed the POST and it will be marked BAD. |
- |
LOG_STD_NO_ACTION |
|
SPE-3-SM_RESPONSE_NO_MEM |
3-Error |
SPE SM out of response buffers |
The PM SPE State Machine has run out of response event memroy. |
port-mgmt |
LOG_STD_ACTION |
|
SPE-3-ST_API_ERR |
3-Error |
PM failed to create [chars]. |
Port Management failed to initialize the CSM event processing component. |
- |
LOG_STD_ACTION |
|
SPE-3-ST_EVENT_NO_MEM |
3-Error |
PM ST failed to create [chars]. |
Port Management failed to allocate dynamic chunk memory for event logging. |
port-mgmt |
LOG_STD_ACTION |
|
SPE-4-SPE_ACT_SESS_WARN |
4-Warning |
Active session count = [dec]. Country code not set |
Country code cannot be set on a system with active sessions. |
- |
LOG_STD_NO_ACTION |
|
SPE-4-SPE_CONFIG_WARN |
4-Warning |
Country Code Trunk card mismatch for. |
A Country Code was configured that may not work with the trunk Card. |
- |
LOG_STD_NO_ACTION |
|
SPE4X155-3-INITERR |
3-Error |
Chip initialization failed errcode=[dec]: [chars] |
required resources unavailable. |
osm-choc-ds0 |
"Reinsert the linecard. If still fails do\n\ 'test cwtlc show seeprom red' swap hardware and\n\ copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SPE4X155-3-PDDBERROR |
3-Error |
Pointer to device structure is invalid |
Software error occured. |
osm-choc-ds0 |
LOG_STD_ACTION |
|
SPE4X155-3-PDDBNULL |
3-Error |
Pointer to device structure is 0 |
Software error occured. |
osm-choc-ds0 |
LOG_STD_ACTION |
|
SPE-6-NULL_OBJ |
6-Information |
SPE object [chars] is unavailable. |
Information about this SPE could not be retrieved. The SPE may not exist. |
- |
LOG_STD_NO_ACTION |
|
SPE-6-SM_BUSIEDOUT |
6-Information |
SPE [chars] busiedoutmaintenance will be allowed |
The SPE is taken out of service temporarily. Maintanence activities can still be performed. |
- |
LOG_STD_NO_ACTION |
|
SPE-6-SM_CLEARED |
6-Information |
SPE [chars] Cleared |
The SPE will be re-downloaded with the configured firmware. |
- |
LOG_STD_NO_ACTION |
|
SPE-6-SM_DEFER_DOWNLOAD |
6-Information |
SPE [chars] : Firmware download deferred |
Firmware download for the SPE is postponed due to active calls. |
- |
LOG_STD_NO_ACTION |
|
SPE-6-SM_SHUTDOWN |
6-Information |
SPE [chars] shutdown |
The SPE is taken out of service. Maintenance activities cannot be performed. |
- |
LOG_STD_NO_ACTION |
|
SPE-6-SM_START_DOWNLOAD |
6-Information |
SPE [chars] : Firmware download initiated |
Firmware download for the SPE is initiated. |
- |
LOG_STD_NO_ACTION |
|
SPE-6-SPE_DNLD_MAINT |
6-Information |
[chars] [chars] |
Download maintenance is running and information |
- |
LOG_STD_NO_ACTION |
|
SPE-6-SPE_DNLD_MAINT_PROCESS |
6-Information |
[chars] |
Download maintenance process information |
- |
LOG_STD_NO_ACTION |
|
SR-3-SR_GB_CREATE_ERR |
3-Error |
Error Creating SR GB start [dec] end [dec] |
Error creating sr gb |
ribinfra |
LOG_STD_RECUR_ACTION |
|
SR-3-SR_GBLB_RESERVE_ERR |
3-Error |
Error Reserving SR label range start [dec] end [dec] rc [dec] |
Error reserving default sr blocks |
ribinfra |
LOG_STD_RECUR_ACTION |
|
SR-3-SR_INTERNAL_ERR |
3-Error |
[chars] |
SR_INT_ERR_EXPLANATION |
ribinfra |
LOG_STD_RECUR_ACTION |
|
SR-3-SR_LB_CREATE_ERR |
3-Error |
Error Creating SR LB start [dec] end [dec] |
Error creating sr lb |
ribinfra |
LOG_STD_RECUR_ACTION |
|
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. |
- |
LOG_STD_ACTION |
|
SR-3-SR_POLICY_UNLOCK_FREE |
3-Error |
Policy reference decrease on freed policy |
Policy reference decrease on freed policy need to investigate |
sr-policy-mgr |
"This error message need to be reported and addressed by IOS XE SR team" |
|
SR-3-SR_POLICY_UNLOCK_NO_REQ |
3-Error |
Policy ref decreased to 0 without explicit destroy |
Policy reference decreased to 0 without explicit destroy need to investigate |
sr-policy-mgr |
"This error message need to be reported and addressed by IOS XE SR team" |
|
SR-4-SR_POLICY_REF_DBG_MAX |
4-Warning |
Policy ref log max entries [dec] reached |
Policy reference debug log max entries reached need to enlarge depth or optimize code |
sr-policy-mgr |
"This error message need to be reported and addressed by IOS XE SR team with show segment-routing traffic-eng policy all internal output" |
|
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-6-SR_LABEL_RANGE_LOG |
6-Information |
Segment Routing MPLS [chars] |
Segment Routing MPLS Label Range Insufficient |
ribinfra |
LOG_STD_RECUR_ACTION |
|
SR-6-SR_STATE_LOG |
6-Information |
Segment Routing MPLS [chars] |
Segment Routing MPLS State |
ribinfra |
LOG_STD_RECUR_ACTION |
|
SRC-3-AFOVEN_ERROR |
3-Error |
Attempt to enable [chars] protection autofailover on interface [chars] when port status is [hec] |
Software attempt at enabling autofailover port status is not good |
- |
LOG_STD_ACTION |
|
SRC-3-LC_APS_INTF_FAULT |
3-Error |
SRC detected a APS interface fault for line card in slot [dec] |
SRC detected a APS interface fault |
- |
LOG_STD_ACTION |
|
SRC-3-LC_APS_INTF_INIT_FAULT |
3-Error |
SRC-LRC APS interface could not be initialized for line card in slot [dec] |
SRC detected a APS interface fault |
- |
LOG_STD_ACTION |
|
SRC-3-LC_APS_TIMEOUT |
3-Error |
SRC detected keep alive timeout on APS intferace for slot [dec] |
SRC detected a APS keep alive timeout fault |
- |
LOG_STD_ACTION |
|
SRC-3-LC_CMI_INTF_FAULT |
3-Error |
SRC detected a CMI interface fault for line card in slot [dec] |
SRC detected a CMI interface fault |
- |
LOG_STD_ACTION |
|
SRC-3-LC_CMI_TIMEOUT |
3-Error |
SRC detected keep alive timeout on CMI intferace for slot [dec] |
SRC detected a CMI keep alive timeout fault |
- |
LOG_STD_ACTION |
|
SRC-3-LC_REG_READ_FAIL |
3-Error |
Register read failed for slot [dec] addr 0x[hec] due to [chars] |
SRC unable to read line card register |
- |
LOG_STD_ACTION |
|
SRC-3-LC_REG_WRITE_FAIL |
3-Error |
Register write failed for slot [dec] addr 0x[hec] due to [chars] |
SRC unable to write line card register |
- |
LOG_STD_ACTION |
|
SRCP_APP-2-INTERNAL_CRITICAL |
2-Critical |
[chars] |
- |
- |
LOG_STD_SH_TECH_ACTION |
|
SRCP_APP-3-INTERNAL_ERROR |
3-Error |
[chars] |
- |
- |
LOG_STD_SH_TECH_ACTION |
|
SRCP_APP-4-INTERNAL_WARNING |
4-Warning |
[chars] |
- |
- |
LOG_STD_SH_TECH_ACTION |
|
SRCP_APP-6-DNS_QUEUE_FAILED |
6-Information |
Failed to create DNS message watched queue\n |
Failed to create DNS message watched queue. |
ios-voice |
"Check the size of free memory to make sure there is enough memory." |
|
SRCP_APP-6-PROCESS_CREATION_FAILED |
6-Information |
Cannot create SRCP application process\n |
Failed to create the SRCP application process. |
ios-voice |
"Check the size of free memory to make sure there is enough memory." |
|
SRCP_APP-6-SOCKET_OPEN_FAILED |
6-Information |
Failed to open UDP port for SRCP\n |
Failed to open UDP port for the SRCP process. |
ios-voice |
"Check if any other application use the same UDP port number 2427." |
|
SRCP_APP-6-SYS_QUEUE_FAILED |
6-Information |
Failed to create SRCP system message watched queue\n |
Failed to create SRCP system message watched queue. |
ios-voice |
"Check the size of free memory to make sure there is enough memory." |
|
SRP-1-WRAPPING_PROCESS_LOCKED |
1-Alert |
[chars] The wrap/unwrap state-change process is locked |
A wrap/unwrap state change process has not come to an end on time. |
- |
"If message is periodic issue a \"shut\" and \"no shut\" on the interface." |
|
SRP-3-DUP_MAC_ADDR |
3-Error |
[chars] : Duplicate mac addresses in topology |
The topology contains 1 or more duplicate mac addresses |
- |
"Identify duplicate address and correct configuration." |
|
SRP-3-FALSE_VAL_ALARM |
3-Error |
[chars] - error in [chars] |
FALSE value returned. Some features/commands may not work properly |
srp |
"Please Contact Cisco Systems TAC support" |
|
SRP-3-NULL_P_ALARM |
3-Error |
Dereferencing NULL pointer [chars] in [chars] |
NULL pointer error condition exists. Some features/commands may not work properly |
srp |
"Please Contact Cisco Systems TAC support" |
|
SRP-3-RING_ID_ERROR |
3-Error |
[chars] : Rx side [chars] Tx side of fiber originates on side [chars] |
The fiber on the specified side is remotely connected \nto the wrong side |
- |
"Verify that each side A is connected to side B" "\nand each side B is connected to side A." |
|
SRP-3-SINGLE_NODE_TOPO |
3-Error |
[chars] : Single node in topology |
The topology discovery resulted in a single node being found |
- |
"This can be due to duplicated mac addresses." "\nIdentify mac address of interface and ensure it is not" "\nduplicated on other nodes." "\nIf the node is in loopback disregard this message." |
|
SRP-4-ALARM |
4-Warning |
[chars] Side [chars] [chars] |
A physical line error condition exists on the indicated network |
srp |
"Diagnose and repair the physical error" |
|
SRP-4-RAC_ALARM |
4-Warning |
[chars] Side [chars] [chars] |
A physical error condition detected at the indicated RAC |
srp |
"Diagnose and repair the physical error" |
|
SRP-4-SRR_STATE_CHANGE |
4-Warning |
[chars] SRR usage changed [chars] |
SRR ring usage is changed using Inner Outer or Both rings. |
- |
"Diagnose the cause of the ring usage change." |
|
SRP-4-SRR_VER_MISSMATCH |
4-Warning |
[chars] SRR version missmatch detected. |
Different SRR version received from other nodes. |
- |
"Update the IOS image on all nodes of the ring to the same SRR version" |
|
SRP-4-WRAP_STATE_CHANGE |
4-Warning |
[chars] [chars] on side [chars] [chars] |
The specified side of the interface is wrapped or unwrapped. |
- |
"Diagnose the cause of the wrap." |
|
SRPMIB-3-FALSE_VAL_ALARM |
3-Error |
[chars] - error in [chars] |
FALSE value returned. Some features/commands may not work properly |
srpmib |
"Please Contact Cisco Systems TAC support" |
|
SRPMIB-3-NULL_P_ALARM |
3-Error |
Dereferencing NULL pointer [chars] in [chars] |
NULL pointer error condition exists. Some feature/command may not work properly |
srpmib |
"Please Contact Cisco Systems TAC support" |
|
SRW-7-BAD_SRW_DATA |
7-Debug |
Bad SRW data %08x |
An internal software error occurred. |
ribinfra |
LOG_STD_RECUR_ACTION |
|
SRW-7-BAD_SRW_MAGIC |
7-Debug |
Bad SRW magic %08x @ %08x |
An internal software error occurred. |
ribinfra |
LOG_STD_RECUR_ACTION |
|
SRW-7-SRW_ERROR |
7-Debug |
[chars]: [hec] [hec] [dec] [dec] [dec] [dec] [hec] |
An internal software error occurred. |
ribinfra |
LOG_STD_RECUR_ACTION |
|
SRW-7-SRW_ERROR2 |
7-Debug |
[chars]: [hec] [hec] [dec] [dec] [dec] [dec] [hec] [hec] [hec] [hec] [dec] |
An internal software error occurred. |
ribinfra |
LOG_STD_RECUR_ACTION |
|
SRW-7-SRW_ERROR3 |
7-Debug |
[chars]: [hec] [hec] [dec] [dec] [dec] [dec] [hec] [hec] [hec] [dec] [hec] [dec] |
An internal software error occurred. |
ribinfra |
LOG_STD_RECUR_ACTION |
|
SSE-2-BOGUSEQ |
2-Critical |
SSE bogus equal branch [hex] [hex] [dec] [hec] |
An internal inconsistency in the data structures used by the SSE occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
SSE-2-HUNG |
2-Critical |
SSE hung -- [chars] |
The SSE is hung. |
- |
"Reboot the SSE." |
|
SSE-2-HWFAILURE |
2-Critical |
SSE hardware failure -- [chars] code [hex] |
A hardware error occurred indicating an unexpected condition on the silicon switch processor SSP board. |
- |
"It might be necessary to replace the SSP. " LOG_STD_SH_TECH_ACTION |
|
SSE-2-MEMERROR |
2-Critical |
SSE memory failure address [hex]\n expected [hex] got [hex] |
A hardware error occurred indicating memory failure on the silicon switch processor SSP board. |
- |
"It might be necessary to replace the SSP. " LOG_STD_SH_TECH_ACTION |
|
SSE-2-NESTADDR |
2-Critical |
SSE nested addresses detected protocol [dec] [inet] |
An internal inconsistency in the data structures used by the SSE occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
SSE-2-NOMATCH |
2-Critical |
SSE delete didn't end at a match node type [chars] value [dec] address [inet] bytecount [dec] high [dec] state [dec] |
An internal inconsistency in the data structures used by the SSE occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
SSE-2-NOMEMORY |
2-Critical |
No memory available for [chars] |
An operation could not be accomplished because of a low memory condition. |
- |
"Reduce other system activity to ease memory demands. If conditions warrant upgrade to a larger memory configuration." |
|
SSE-2-NOTZERO |
2-Critical |
program memory does not start at zero |
A hardware error occurred indicating an unexpected condition on the silicon switch processor SSP board. |
- |
"It might be necessary to replace the SSP. " LOG_STD_SH_TECH_ACTION |
|
SSE-2-SWFAILURE |
2-Critical |
SSE software failure -- [chars] [hex] |
A software failure occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
SSE-3-BADMEMORY |
3-Error |
SSE memory failure detected orig [hex] [hex] tested [hex] [hex] |
A memory error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
SSE-3-COMPERR |
3-Error |
SSE compilation failure -- [chars] |
A software failure occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
SSFP_TPOP-4-CONF_ADD |
4-Warning |
TPoP SSFP is Configured \ on interface [chars]\n |
TPoP SSFP is Configured |
- |
"None - normal situation" |
|
SSFP_TPOP-4-CONF_DEL |
4-Warning |
TPoP SSFP is Unconfigured on \ interface [chars]\n |
TPoP SSFP is Unconfigured |
- |
"None - normal situation" |
|
SSFP_TPOP-4-CONF_ERROR_ADD |
4-Warning |
Failed to Configure TPoP \ on interface [chars]\n |
Failed to configure TPoP |
- |
"None - normal situation" |
|
SSFP_TPOP-4-CONF_ERROR_DEL |
4-Warning |
Failed to Unconfigure TPoP \ on interface [chars]\n |
Failed to unconfigure TPoP |
- |
"None - normal situation" |
|
SSFP_TPOP-4-CONF_EXIST |
4-Warning |
Port Type is already \ configured on this interface [chars].\n \ %%Remove the existing TPoP configuration and try again.\n |
TPoP configuration is already present. |
- |
"None - normal situation" |
|
SSFP_VCOP-4-CONF_ADD |
4-Warning |
VCoP SSFP is Configured \ on interface [chars]\n |
VCoP SSFP is Configured |
- |
"None - normal situation" |
|
SSFP_VCOP-4-CONF_DEL |
4-Warning |
VCoP SSFP is Unconfigured on \ interface [chars]\n |
VCoP SSFP is Unconfigured |
- |
"None - normal situation" |
|
SSFP_VCOP-4-CONF_ERROR_ADD |
4-Warning |
Failed to Configure VCoP \ on interface [chars]\n |
Failed to configure VCoP |
- |
"None - normal situation" |
|
SSFP_VCOP-4-CONF_ERROR_DEL |
4-Warning |
Failed to Unconfigure VCoP \ on interface [chars]\n |
Failed to unconfigure VCoP |
- |
"None - normal situation" |
|
SSFP_VCOP-4-CONF_EXIST |
4-Warning |
Port Type is already \ configured on this interface [chars].\n \ %%Remove the existing VCoP configuration and try again.\n |
VCoP configuration is already present. |
- |
"None - normal situation" |
|
SSFP_VCOP-4-DEV_INS |
4-Warning |
VCoP SSFP is Inserted into [chars]\n |
VCoP SSFP is Inserted |
- |
"None - normal situation" |
|
SSFP_VCOP-4-DEV_REM |
4-Warning |
VCoP SSFP is Removed from [chars]\n |
VCoP SSFP is Removed |
- |
"None - normal situation" |
|
SSFPD-3-BACKWARD_INCOMPATIBLE |
3-Error |
Upgrade failed for Smart SFP in bay [dec] port [dec] PP backward incompatible with Titan |
Smart SFP upgrade fail notification. This is a software error. |
- |
LOG_STD_SH_TECH_ACTION |
|
SSFPD-3-CN_NOT_MANAGEABLE |
3-Error |
Upgrade failed for Smart SFP in bay [dec] port [dec] CN not manageable |
Smart SFP upgrade fail notification. This is a software error. |
- |
LOG_STD_SH_TECH_ACTION |
|
SSFPD-3-UPGRADE_FAILED |
3-Error |
Upgrade failed for Smart SFP in bay [dec] port [dec] |
Smart SFP upgrade fail notification. This is a software error. |
- |
LOG_STD_SH_TECH_ACTION |
|
SSFPD-6-NO_CONTENT_CHANGE |
6-Information |
Skipping upgrade for for Smart SFP in bay [dec] port [dec] Smart SFP already running same version |
Smart SFP upgrade fail notification. This is a software error. |
- |
LOG_STD_SH_TECH_ACTION |
|
SSFPD-6-NOT_DISCOVERED |
6-Information |
Skipping upgrade for Smart SFP in bay [dec] port [dec] discovery incomplete |
Smart SFP upgrade fail notification. This could be a software/Hardware error. |
- |
LOG_STD_SH_TECH_ACTION |
|
SSFPD-6-SKIP_VCOP_SW_VER_CMD |
6-Information |
Skipping CLI command as smart SFP upgrade already in progress Retry once upgrade completed |
Skipping SFP software version command during upradation. This is not a software error. |
- |
LOG_STD_SH_TECH_ACTION |
|
SSFPD-6-UPGRADE_COMPLETE |
6-Information |
Upgrade for Smart SFP in bay [dec] port [dec] complete |
Smart SFP upgrade complete notification. This is not a software error. |
- |
LOG_STD_SH_TECH_ACTION |
|
SSFPD-6-UPGRADE_IN_PROGRESS |
6-Information |
Skipping upgrade for for Smart SFP in bay [dec] port [dec] Smart SFP upgrade already in progress |
Smart SFP upgrade fail notification. This is not a software error. |
- |
LOG_STD_SH_TECH_ACTION |
|
SSFPD-6-UPGRADE_REQUIRED |
6-Information |
PP version Upgrade required for Smart SFP in bay [dec] port [dec]. Use 'upgrade hw-programmable ssfp slot <logical-slot> bay <bay-number> port <port-number>' cli for upgrade |
Smart SFP upgrade fail notification. This is not a software error. |
- |
LOG_STD_SH_TECH_ACTION |
|
SSFPD-6-UPGRADE_STARTED |
6-Information |
Upgrade started for Smart SFP in bay [dec] port [dec] |
Smart SFP upgrade start notification. This is not a software error. |
- |
LOG_STD_SH_TECH_ACTION |
|
SSH-3-AUTH_METH_ERR |
3-Error |
Server does not support password or keyboard-interactive authentication |
No common supported authentication methods exist |
- |
- |
|
SSH-3-BAD_PACK_LEN |
3-Error |
Bad packet length [dec] |
Bad packet length packet decompose failed |
ssh |
LOG_STD_ACTION |
|
SSH-3-BIG_NUM_BIG |
3-Error |
Big num error: Cannot handle big num of size [dec] |
Key operations tried to retrieve a big num of too large a value |
ssh |
LOG_STD_ACTION |
|
SSH-3-BUFF_GET_FAIL |
3-Error |
Tried to get more bytes than in SSH Buffer |
Tried to retrieve more data than actually present in the buffer |
ssh |
LOG_STD_ACTION |
|
SSH-3-BUFF_LEN_EXCD |
3-Error |
Buffer Length exceeded |
Tried to allocate or append a buffer beyond its maximum length |
ssh |
LOG_STD_ACTION |
|
SSH-3-CIPH_INIT_FAIL |
3-Error |
Cipher initialization failed |
Cipher initialization failed failed to set new keys |
ssh |
LOG_STD_ACTION |
|
SSH-3-DH_GEX_RANGE_OUT |
3-Error |
Server has chosen DH group size which is not in range [dec] !< [dec] !< [dec] DH Group Exchange key negotiation failed |
Server must choose DH group size which falls between client sent min/max |
ssh |
"If this message recurs contact your technical support representative." |
|
SSH-3-DH_RANGE_FAIL |
3-Error |
Client DH key range mismatch with [chars] configured DH key on server |
DH Range mismatch with min/max configured DH key on server DH negotiation failed |
ssh |
LOG_STD_ACTION |
|
SSH-3-DH_SECRET_FAIL |
3-Error |
DH shared secret computation failed status [dec] |
DH secret value computation failed this is required in DH negotiation cannot move on hence aborting |
ssh |
LOG_STD_ACTION |
|
SSH-3-DH_SIZE |
3-Error |
DH public key size > DH group key size[dec] |
DH negotiation failed due to size mismatch between public key size and group size |
ssh |
LOG_STD_ACTION |
|
SSH-3-ECDSA_SIGN_FAIL |
3-Error |
Signature [chars] failed status [dec] |
ECDSA Signature verification failed |
ssh |
LOG_STD_ACTION |
|
SSH-3-HOSTKEY_FAIL |
3-Error |
Cannot load hostkey |
Hostkey load has failed causing dh key negotiations to fail |
ssh |
LOG_STD_ACTION |
|
SSH-3-IDLE_TIMEOUT |
3-Error |
Idle timeout due to no response from the remote machine |
No response from the remote machine |
ssh |
LOG_STD_ACTION |
|
SSH-3-INCOMP_DH |
3-Error |
Incompatible DH Proposal from Server |
Incompatible DH proposal received from server cannot proceed |
ssh |
LOG_STD_ACTION |
|
SSH-3-INV_CONN |
3-Error |
Invalid Connection Block |
Invalid Connection Block |
ssh |
LOG_STD_ACTION |
|
SSH-3-INV_MOD |
3-Error |
Invalid modulus length |
Invalid modulus length |
- |
- |
|
SSH-3-KEX_NOT_SUPP |
3-Error |
Unsupported key exchange method: [dec] |
The key exchange type proposed is not supported by IOS SSH. Kindly check the SSH settings to verify the group used. |
ssh |
"Kindly check the SSH settings to verify the " "key exchange method used. Or contact your technical support " "representative for any help" |
|
SSH-3-KEX_SHORT |
3-Error |
Kex proposal too short |
Key exchange failed as the kex proposal was too short |
ssh |
LOG_STD_ACTION |
|
SSH-3-KEY_GEN_FAIL |
3-Error |
DH key generation failed. Status [dec] |
DH key generation failed |
ssh |
LOG_STD_ACTION |
|
SSH-3-KEYPAIR |
3-Error |
Attempt to generate server keys failed - error code: [chars] |
Server RSA key-pair could not be generated. |
ssh |
"If this message recurs contact your technical support representative." |
|
SSH-3-LOCAL_RST |
3-Error |
Local Reset happened due to line termination/disconnection |
Line termination or request for a disconnection |
ssh |
LOG_STD_ACTION |
|
SSH-3-NO_CHANNEL |
3-Error |
Non-existent channel [dec] |
Non-existent channel id received |
ssh |
LOG_STD_ACTION |
|
SSH-3-NO_DH_GRP |
3-Error |
Non Standard DH Group aborting key exchange |
Non standard DH group sent hence aborting key exchange kindly verify your SSH parameters |
ssh |
"Kindly check the SSH settings to check the key " "exchange group used. Or contact your technical " "support representative for further help" |
|
SSH-3-NO_KEX |
3-Error |
No Kex cannot rekey |
Rekey failed failed to get kex information |
ssh |
LOG_STD_ACTION |
|
SSH-3-NO_MATCH |
3-Error |
No matching [chars] found: client [chars] server [chars] |
The specified entity cipher or mac or comp algo etc was not found please check the corresponding parameter and try again |
ssh |
"If you believe you are incorrectly receiving this " "message please contact your " "technical support representative" |
|
SSH-3-NO_USERAUTH |
3-Error |
No auth method configured for SSH [chars]. Incoming connection from [chars] tty = [dec] dropped |
At least one auth method should be configured for SSH server |
ssh |
"Please configure at least one auth method. " "If this message recurs contact your technical support representative." |
|
SSH-3-NOMEMORY |
3-Error |
Memory allocation failed. |
A Malloc has failed during SSH execution |
ssh |
"System seems to be running low on memory if this " "message recurs please contact your technical " "support representative" |
|
SSH-3-NOT_SUPP |
3-Error |
Matching [chars] not supported: [chars] |
The specified entity cipher or mac or comp algo etc is not supported by IOS SSH |
ssh |
"If you believe you are incorrectly receiving " "this message please contact " "your technical support representative" |
|
SSH-3-PACK_CORR_PAD |
3-Error |
Corrupted padlen [dec] on input |
Packet with corrupted padd length received causing packet decompose to fail |
ssh |
LOG_STD_ACTION |
|
SSH-3-PACK_INTEG_ERROR |
3-Error |
Packet integrity error [dec] bytes remaining from [chars] |
Packet error incorrect amount of data received |
ssh |
LOG_STD_ACTION |
|
SSH-3-PACK_PADD_ERR |
3-Error |
Padding error: needed [dec] bytes block size [dec] bytes mod= [dec] |
Padding error packet decompose failed |
ssh |
LOG_STD_ACTION |
|
SSH-3-PACK_SND_FAIL |
3-Error |
Packet send failed |
A packet send failed within ssh code |
ssh |
LOG_STD_ERROR |
|
SSH-3-PRIVATEKEY |
3-Error |
Unable to retrieve RSA private key for [chars] |
RSA private key does not exist or is corrupted. |
ssh |
"If this message recurs contact your technical support representative." |
|
SSH-3-PROC_MISMATCH |
3-Error |
SSH [chars] Incorrect process waiting for event. Process name: [chars] |
An incorrect process has entered ssh wait for event ideally only SSH Process on the server or Exec process on the client are allowed to wait for event through ssh |
ssh |
"No action necessary - informational message" |
|
SSH-3-RANDOM_GEN_FAIL |
3-Error |
Unable to generate random number |
Random number generation error |
ssh |
"If this message recurs contact your technical support representative." |
|
SSH-3-RSA_SIGN_FAIL |
3-Error |
Signature [chars] failed status [dec] |
RSA Signature creation/verification failed |
ssh |
LOG_STD_ACTION |
|
SSH-3-SER_NOT_DEF |
3-Error |
ServerHostKey not defined in SSH Server Database |
Server Host key is not present in SSH Server Database causing host key verification to fail |
ssh |
LOG_STD_ACTION |
|
SSH-3-SER_VAL_FAIL |
3-Error |
ServerHostKey Validation failed. Key Mismatch |
ServerHostKey Validation failed. Key Mismatch |
ssh |
LOG_STD_ACTION |
|
SSH-3-SERVER_AUTH_METH_ERR |
3-Error |
Server does not support/Configured with '[chars]' Authentication method |
No common supported authentication methods exist |
ssh |
LOG_STD_ACTION |
|
SSH-3-STRING_NULL |
3-Error |
Tried to append NULL string to buffer |
A function tried to append a NULL string to buffer or packet which shouldn't happen |
ssh |
LOG_STD_ACTION |
|
SSH-4-DEATTACK |
4-Warning |
CRC-32 compensation attack detected src [inet] dst [inet] attack thwarted. Connection is closed. |
CRC-32 compensation vulnerability allows an attacker to execute arbitrary commands on the SSH server or otherwise subvert an encrypted SSH channel with arbitrary data. for more information on this attack see http://www.core-sdi.com/english/ssh |
ssh |
"No action necessary - attack has been thwarted" |
|
SSH-4-SSH2_UNEXPECTED_MSG |
4-Warning |
Unexpected message type has arrived. Terminating the connection from [chars] |
SSH Session closure warning on receiving an inappropriate message from the peer |
ssh |
"If this message recurs contact your technical support representative." |
|
SSH-5-DISABLED |
5-Notice |
SSH [dec].[dec] has been disabled |
The SSH protocol has been disabled for connections |
ssh |
"No action necessary - informational message" |
|
SSH-5-ENABLED |
5-Notice |
SSH [dec].[dec] has been enabled |
The SSH protocol has been enabled for connections |
ssh |
"No action necessary - informational message" |
|
SSH-5-SSH_CLOSE |
5-Notice |
SSH Session from [chars] tty = [dec] for user '[chars]' |
The SSH Session closure information |
ssh |
"No action necessary - informational message" |
|
SSH-5-SSH_COMPLIANCE_VIOLATION_ENCR_ALGO |
5-Notice |
SSH Encryption Algorithm compliance violation detected. Kindly note that the usage of Algorithm type '[chars]' will be deprecated in the upcoming releases.Please configure alternate encryption algorithms to avoid service impact. |
SSH user is hereby informed about the impending deprecation of the encryption algorithm that is currently employed and is advised to effect the required configuration changes to avoid the possibility of service impact in the future. |
ssh |
"This is an informational message and can be " "dismissed. At the same time it is highly recommended that the user " "makes required configuration changes at the earliest to avoid service " "impacts upon software upgrades." |
|
SSH-5-SSH_COMPLIANCE_VIOLATION_PK_ALGO |
5-Notice |
SSH Public-key Algorithm compliance violation detected.Kindly note that weaker Public-key Algorithm '[chars]' will be disabled by-default in the upcoming releases.Please configure more stronger PK algorithms to avoid service impact. |
SSH user is hereby informed about the impending removal of public key algorithm from default PK list that is currently employed and is advised to effect the required configuration changes to avoid the possibility of service impact in the future. |
ssh |
"This is an informational message and can be " "dismissed. At the same time it is highly recommended that the user " "makes required configuration changes at the earliest to avoid service " "impacts upon software upgrades." |
|
SSH-5-SSH_COMPLIANCE_VIOLATION_RSA_KEY_SIZE |
5-Notice |
SSH RSA Key Size compliance violation detected. Kindly note that the usage of keys smaller than [dec] bits will be deprecated in the upcoming releases. Please revise your key configuration accordingly to avoid service impact. |
SSH user is hereby informed about the impending deprecation of the RSA key size that is currently employed and is advised to effect the required configuration changes to avoid the possibility of service impact in the future. |
ssh |
"This is an informational message and can be " "dismissed. At the same time it is highly recommended that the user " "makes required configuration changes at the earliest to avoid service " "impacts upon software upgrades." |
|
SSH-5-SSH_SESSION |
5-Notice |
SSH Session request from [chars] tty = [dec] using crypto cipher '[chars]' [chars] |
The SSH session request information |
ssh |
"No action necessary - informational message" |
|
SSH-5-SSH_USERAUTH |
5-Notice |
User '[chars]' authentication for SSH Session from [chars] tty = [dec] |
The SSH user authentication status information |
ssh |
"No action necessary - informational message" |
|
SSH-5-SSH2_CLOSE |
5-Notice |
SSH2 Session from [chars] tty = [dec] for user '[chars]' |
The SSH Session closure information |
ssh |
"No action necessary - informational message" |
|
SSH-5-SSH2_SESSION |
5-Notice |
SSH2 Session request from [chars] tty = [dec] using crypto cipher '[chars]' hmac '[chars]' [chars] |
The SSH session request information |
ssh |
"No action necessary - informational message" |
|
SSH-5-SSH2_USERAUTH |
5-Notice |
User '[chars]' authentication for SSH2 Session from [chars] tty = [dec] |
The SSH user authentication status information |
ssh |
"No action necessary - informational message" |
|
SSL-3-SSL_REC_HDR_BUF_OVERFLOW |
3-Error |
QFP SSL record header buffer overflow |
Cisco internal software error. QFP SSL record processing detected header buffer overflow condition. The SSL connection will not be functional while this condition exists. |
qfp-ssl keyword:none |
LOG_STD_ACTION |
|
SSL-3-SSL_STUB |
3-Error |
QFP SSL [chars] feature executes stub entry in [chars] direction |
Cisco internal software error. QFP SSL feature stub entry got executed. The packet will be dropped. |
qfp-ssl keyword:none |
LOG_STD_ACTION |
|
SSLVPN_PROXY-2-PROXY_IPC_INIT_FAILED |
2-Critical |
QFP SSLVPN Proxy IPC interface initialization failure result: [dec]. |
Cisco internal software error. QFP SSLVPN Proxy initialization detected that the IPC interface initialization failed. QFP SSLVPN proxy will not be functional while this condition exists. |
qfp-ssl keyword:sslvpn |
LOG_STD_ACTION |
|
SSLVPN_PROXY-3-PROXY_BAD_MSG |
3-Error |
QFP SSLVPN Proxy received bad length message type [dec] |
Cisco internal software error. QFP SSLVPN Proxy received a corrupted message from control plane. This message will be ignored. |
qfp-ssl keyword:sslvpn |
LOG_STD_ACTION |
|
SSLVPN_PROXY-3-PROXY_CRYPTO_CTX_MEM_REQ_FAIL |
3-Error |
QFP SSLVPN Proxy failed to repleneish crypto context memory. |
Cisco internal software error. QFP SSLVPN Proxy message processing detected leaking of crypto context memory condition. QFP SSLVPN will not be functional properly while this condition exist. |
qfp-ssl keyword:sslvpn |
LOG_STD_ACTION |
|
SSLVPN_PROXY-3-PROXY_INV_MSG |
3-Error |
QFP SSLVPN Proxy received invalid message type [dec] |
Cisco internal software error. QFP SSLVPN Proxy received an invalid message from control plane. This message will be ignored. |
qfp-ssl keyword:sslvpn |
LOG_STD_ACTION |
|
SSLVPN_PROXY-3-PROXY_IPC_ALLOC_FAILED |
3-Error |
QFP SSLVPN Proxy [chars] message lost due to message buffer allocation failure. |
Cisco internal software error. QFP SSLVPN Proxy message processing detected a message buffer allocation failure. The message is lost as the result of this condition. |
qfp-ssl keyword:sslvpn |
LOG_STD_ACTION |
|
SSLVPN_PROXY-3-PROXY_IPC_SEND_FAILED |
3-Error |
QFP SSLVPN Proxy [chars] message lost due to message sent failure result: [dec]. |
Cisco internal software error. QFP SSLVPN Proxy message processing detected a message sent failure. The message is lost as the result of this condition. |
qfp-ssl keyword:sslvpn |
LOG_STD_ACTION |
|
SSLVPN_PROXY-3-PROXY_SSL_CTX_MEM_REQ_FAIL |
3-Error |
QFP SSLVPN Proxy failed to repleneish SSL context memory. |
Cisco internal software error. QFP SSLVPN Proxy message processing detected leaking of SSL context memory condition. QFP SSLVPN will not be functional properly while this condition exist. |
qfp-ssl keyword:sslvpn |
LOG_STD_ACTION |
|
SSLVPN_PROXY-4-PROXY_CRYPTO_CTX_REQ_FAIL |
4-Warning |
QFP SSLVPN Proxy failed to replenish hardware context handles. |
Cisco internal software error. QFP SSLVPN Proxy message processing detected out-of-resource condition and cannot replenish hardware context handles. QFP SSLVPN will not be functional properly while this conidtion exist. |
qfp-ssl keyword:sslvpn |
LOG_STD_ACTION |
|
SSLVPN-1-LICENSE_EXPIRED |
1-Alert |
IOS SSLVPN evaluation license has expired |
IOS SSLVPN evaluation license has expired and a new license needs to be obtained. Existing user sessions will continue till they are closed and no new sessions will be allowed. |
ssl-vpn |
"Please visit http://www.cisco.com/go/sslvpn for instructions on how " "to obtain a IOS SSLVPN license" |
|
SSLVPN-3-LICENSE_NO_LICENSE |
3-Error |
No valid license is available to use IOS SSLVPN service |
IOS SSLVPN service is a licensed feature on this platform. It will not be functional until a valid license is installed. |
ssl-vpn |
"Please visit http://www.cisco.com/go/sslvpn for instructions on how " "to obtain a IOS SSLVPN license" |
|
SSLVPN-3-SSL_APPL_REG_FAILED |
3-Error |
QFP SSLVPN registers to SSL library failed |
Cisco internal software error. QFP SSLVPN feature initialization detected that the SSL library registration failed. QFP SSLVPN will not be functional while this condition exists. |
qfp-ssl keyword:sslvpn |
LOG_STD_ACTION |
|
SSLVPN-3-SSLVPN_CTX_CLOSE_FAILED |
3-Error |
QFP SSLVPN failed to close SSLVPN context: [%-#016llx] Close request reason: [chars] |
Cisco internal software error. QFP SSLVPN feature failed to close an SSLVPN context. |
qfp-ssl keyword:sslvpn |
LOG_STD_ACTION |
|
SSLVPN-3-SSLVPN_CTX_PUNT_FAILED |
3-Error |
QFP SSLVPN failed to send [chars] for context: [%-#016llx] to control plane |
Cisco internal software error. QFP SSLVPN featre failed to send a message to control plane. |
qfp-ssl keyword:sslvpn |
LOG_STD_ACTION |
|
SSLVPN-3-SSLVPN_SOCKET_ACTION_FAILED |
3-Error |
QFP SSLVPN failed to [chars] socket [hec] [[chars]err [dec]] |
Cisco internal software error. QFP SSLVPN feature failed to accomplish socket action. |
qfp-ssl keyword:sslvpn |
LOG_STD_ACTION |
|
SSLVPN-3-SSLVPN_STUB |
3-Error |
QFP SSLVPN [chars] feature executes stub entry in [chars] direction |
Cisco internal software error. QFP SSLVPN feature stub entry got executed. The packet will be dropped. |
qfp-ssl keyword:sslvpn |
LOG_STD_ACTION |
|
SSLVPN-3-SSLVPN_STUB_DATA_MSG_LOST |
3-Error |
QFP SSLVPN stub function failed to transmit data message size: [dec]. |
- |
- |
- |
|
SSLVPN-3-SSLVPN_STUB_TW_MEM_LEAK |
3-Error |
QFP SSLVPN feature leaks timing wheel memory |
Cisco internal software error. QFP SSLVPN feature allocates unused timing wheel memory size: [dec] |
qfp-ssl keyword:sslvpn |
LOG_STD_ACTION |
|
SSLVPN-4-LICENSE_COUNT_EXCEEDS_MAX_LIMIT |
4-Warning |
License count of currently installed license exceeds the maximum supported sessions on this platform |
License count of currently installed license exceeds the maximum supported sessions on this platform. Excess count will not be utilized. |
ssl-vpn |
"Please collect the output of show license detail command and " "contact your technical support representative." |
|
SSLVPN-5-HTTP_REQUEST_NOT_AUTHORIZED |
5-Notice |
vw_ctx: [chars] vw_gw: [chars] remote_ip: [inet] status: HTTP request without login cookie resource: [chars] |
This message indicates that HTTP request doesn't have valid login cookie and is not authorized to access the resource |
- |
LOG_STD_NO_ACTION |
|
SSLVPN-5-LOGIN_AUTH_FAILED |
5-Notice |
vw_ctx: [chars] vw_gw: [chars] remote_ip: [inet] user_name: [chars] Failed to contact authentication server |
This message indicates that user session is terminated due to reason indicated |
- |
LOG_STD_NO_ACTION |
|
SSLVPN-5-LOGIN_AUTH_PASSED |
5-Notice |
vw_ctx: [chars] vw_gw: [chars] remote_ip: [inet] user_name: [chars] Authentication successful user logged in |
This message indicates that login authentication succeeded for user |
- |
LOG_STD_NO_ACTION |
|
SSLVPN-5-SSL_TLS_CONNECT_OK |
5-Notice |
vw_ctx: [chars] vw_gw: [chars] i_vrf: [dec] f_vrf: [dec] status: SSL/TLS connection successful with remote at [inet]:[dec] |
This message indicates that SSL/TLS handshake with peer was successful |
- |
LOG_STD_NO_ACTION |
|
SSLVPN-5-SSL_TLS_ERROR |
5-Notice |
vw_ctx: [chars] vw_gw: [chars] i_vrf: [dec] f_vrf: [dec] status: SSL/TLS connection error with remote at [inet]:[dec] |
This message indicates that SSL/TLS connection has encountered error this normally means that either handshake failed or protocol error occured during life-time of the connection |
- |
"Check certificate and trustpoint configuration in global config mode" "as well as under webvpn gateway" |
|
SSLVPN-5-SSLVPN_SESS_SSL_TLS_ERROR |
5-Notice |
vw_ctx: [chars] vw_gw: [chars] i_vrf [dec] f_vrf [dec] status:SSL/TLS connection error with remote at [inet]:[dec] |
This message indicates that SSL/TLS connection has encountered error. This normally means that either handshake failed or protocol error occured during life-time of the connection. |
qfp-ssl keyword:sslvpn |
LOG_STD_ACTION |
|
SSLVPN-5-SSLVPNMGR_ERROR |
5-Notice |
[chars] [chars] |
SSLVPN Manager error. |
- |
LOG_STD_NO_ACTION |
|
SSLVPN-5-UPDOWN |
5-Notice |
sslvpn [chars] : [chars] changed state to [chars] |
sslvpn service state changed. |
- |
LOG_STD_NO_ACTION |
|
SSLVPN-6-INVALID_RADIUS_CONFIGURATION |
6-Information |
Radius configured [chars] \[chars]\ does not exist |
A Tunneling user has logged out from the given gateway/context |
- |
"The information is used to track user logout events. No" " action is required." |
|
SSLVPN-6-LICENSE_NO_FREE_COUNT |
6-Information |
All avaiable SSLVPN session licenses are in use |
All SSLVPN sessions avaialable per current license are in use. Hence no additional user sessions can be allowed. |
ssl-vpn |
"To support more users additional license needs to be purchased. " "Please visit http://www.cisco.com/go/sslvpn for instructions on how " "to obtain a IOS SSLVPN license" |
|
SSLVPN-6-RADIUS_ATTRIBUTE_TOO_LONG |
6-Information |
Attribute length [dec] is longer than buffer size [dec] |
This message indicates that the attribute configured on the Radius server is longer than the allocated buffer size and will be ignored. |
- |
"Reconfigure the radius attribute with the appropriate length" |
|
SSLVPN-6-WEBVPN_APP_ACL_NET |
6-Information |
The request source ip: [inet] destion ip : [inet] from user [chars] is [chars] by ACL |
This message indicates that a Single Sign On session creation failed for the user. Session creation can fail for various reasons such as DNS lookup failure timeouts and retry attempts exceeded |
- |
"The information is used to track Single Sign On events. No" " action is required." |
|
SSLVPN-6-WEBVPN_APP_ACL_URL |
6-Information |
The request scheme: [chars] host : [chars] port : [dec] path : [chars] |
A request is matched with application ACL. |
- |
LOG_STD_NO_ACTION |
|
SSO_UNSUPPORTED-3-MPLS_TE_HA |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
SSP-3-DATACREATEFAIL |
3-Error |
Creation of required data structures failed. |
SSP will not operate properly due to abnormal initialization of required data structures. |
ipsec-ha |
"Reload the device. If the error persists contact " "your technical service representative" |
|
SSP-3-EXCEEDMAXDOI |
3-Error |
SSP maximum DOI exceeded. |
The configuration has exceeded the maximum number of SSP clients allowed on this device at any one time. |
ipsec-ha |
"Please verify your configuration and reduce the " "number of SSP clients running at the same time. If a large number of SSP " "clients is required contact your technical service representative." |
|
SSP-3-NOSTART |
3-Error |
SSP could not initialize. |
The SSP process could not successfully initialize. This may be due to unusual protocol startup times in certain topologies. |
ipsec-ha |
"Ensure that your IP redundancy mechanism HSRP " "config is valid and than all protocols have started. Configure SSP once " "more. If the error recurs contact your technical service advisor." |
|
SSP-3-SRVSOCKCREATEFAIL |
3-Error |
SSP socket creation failed. |
The SSP process could not establish a socket connection with the SSP peer. This is likely to occur in either of two situations the device is under extreme load or it is misconfigured. |
ipsec-ha |
"Verify that the SSP configuration is valid. " "Configure SSP to use a different port number. Reduce the load on the " "device." |
|
SSP-4-CANNOTRUNVER |
4-Warning |
SSP version %-2d.%3d was requested but is not supported in this image. |
The version of SSP requested by the active device is not available in this image. SSP will not run on this device until it is upgraded or the active is downgraded. |
ipsec-ha |
"Verify that all SSP peers are running compatible " "images and that the configuration on each device is as intended." |
|
SSP-4-GROUPCREATEFAIL |
4-Warning |
The SSP group could not be created. |
The maximum number of SSP groups has been reached. |
ipsec-ha |
"This is not an error situation. Only one SSP " "group is permitted at one time." |
|
SSP-4-MISMATCHEDVERRECV |
4-Warning |
Wrong version on received packet. |
The SSP version information in a received packet does not match what is currently running on this device. |
ipsec-ha |
"Verify the configuration of all the SSP peers. " "Ensure all peers are running the correct image." |
|
SSP-5-DISABLED |
5-Notice |
SSP entering disabled state. |
SSP has entered its disabled state. This is normal under many circumstances. For example when the SSP configuration is changed or when a tracked interface is shut down or fails. |
ipsec-ha |
"If this change occurred because of failure on " "the active peer eliminate the cause of failure and reload the failed " "device." |
|
SSP-6-ACTIVE |
6-Information |
SSP entering active state. |
SSP has entered its active state. This is normal. |
ipsec-ha |
"No action needed." |
|
SSP-6-IPREDGRPADD |
6-Information |
An IP Redundancy group listed in the SSP config has been added to this device. |
This is normal. The device may now become the active or the standby if no other configuration items are missing. |
ipsec-ha |
"No action needed." |
|
SSP-6-IPREDGRPDEL |
6-Information |
An IP Redundancy group listed in the SSP config has been removed from this device. |
This is normal. The device may not become the active or the standby if any configuration items are missing. |
policy |
LOG_STD_ACTION |
|
SSP-6-STANDBY |
6-Information |
SSP entering standby state. |
SSP has entered its standby state. This is normal. |
ipsec-ha |
"No action needed." |
|
SSSMGR-3-DYNAMIC_UPDATE_NOT_SUPPORTED |
3-Error |
[[dec]] Dynamic session updates not allowed on this [chars] session. It is an unsupported configuration. |
Updates on these sessions not supported. This is an unsupported configuration. |
sss |
LOG_STD_ACTION |
|
SSSMGR-3-ERROR_RESOURCE_OVERFLOW |
3-Error |
Resource overflow |
A fixed size system resource has been exceeded. |
sss |
LOG_STD_ACTION |
|
SSSMGR-3-INFO_TYPE_NO_COPY_VECTOR |
3-Error |
info type has no copy vector [dec]. |
An internal SSS Manager error occurred. |
sss |
LOG_STD_ACTION |
|
SSSMGR-3-INIT |
3-Error |
Initialisation failure [chars] |
An internal SSS Manager error occurred. |
sss |
LOG_STD_ACTION |
|
SSSMGR-3-INVALID_FSM_STATE |
3-Error |
Encountered an invalid SSS Mgr state [dec] in [chars] |
An internal SSS Manager error occurred. |
sss |
LOG_STD_ACTION |
|
SSSMGR-3-INVALID_INFO_TYPE |
3-Error |
Received an INVALID info type value [dec]. |
An internal SSS Manager error occurred. |
sss |
LOG_STD_ACTION |
|
SSSMGR-3-INVALID_SERVICE_TYPE |
3-Error |
Received an INVALID service type [dec][chars]. |
- |
- |
- |
|
SSSMGR-3-MEMORY_LOW |
3-Error |
Memory low [dec] times disconnecting session |
Required memory is running low. |
sss |
LOG_STD_ACTION |
|
SSSMGR-3-NULL_FSM_CONTEXT |
3-Error |
Encountered a NULL SSS Mgr context in [chars] |
Encountered a NULL context in SSS Manager. |
sss |
LOG_STD_ACTION |
|
SSSMGR-3-NULL_INFO_STRING |
3-Error |
Received a NULL info string value. |
An internal SSS Manager error occurred. |
sss |
LOG_STD_ACTION |
|
SSSMGR-3-RESOURCE_OVERFLOW |
3-Error |
Resource overflow |
A fixed size system resource has been exceeded. |
sss |
LOG_STD_ACTION |
|
SSSMGR-3-SBINIT |
3-Error |
Error initializing [chars] subblock data structure. [chars] |
Initialization of the specified subblock data structure could not be accomplished. |
sss |
LOG_STD_ACTION |
|
SSSMGR-3-UNEXPECTED_MSG |
3-Error |
Encountered an unexpected message: [chars] |
Encountered an unexpected message. |
sss |
LOG_STD_ACTION |
|
SSSMGR-3-UNEXPECTED_SIP_INFO |
3-Error |
Encountered an unexpected SIP info: [chars] |
Encountered an unexpected SIP info. |
sss |
LOG_STD_ACTION |
|
SSSMGR-3-UNSUPPORTED_CFG |
3-Error |
Unsupported configuration detected: [uid: [dec]] [chars] |
Unsupported configuration detected. |
sss |
LOG_STD_ACTION |
|
SSSMGR-4-WARN_RESOURCE_ABOVE_WM |
4-Warning |
Resource above watermark |
A fixed size system resource is above watermark. |
sss |
LOG_STD_ACTION |
|
SSSMGR-5-BB_LICENSE_PROCUREMENT_FAILURE |
5-Notice |
Failed to procure %lu BroadBand licenses |
- |
sss |
LOG_STD_ACTION |
|
SSSMGR-5-BB_LICENSE_PROCUREMENT_SUCCESS |
5-Notice |
Successfully procured %lu BroadBand licenses |
- |
sss |
LOG_STD_ACTION |
|
SSSMGR-5-BB_LICENSE_RELEASE_FAILURE |
5-Notice |
Failed to release all BroadBand licenses |
- |
sss |
LOG_STD_ACTION |
|
SSSMGR-5-BB_LICENSE_RELEASE_SUCCESS |
5-Notice |
Successfully released all BroadBand licenses |
- |
sss |
LOG_STD_ACTION |
|
SSSMGR-5-BB_LICENSE_REQUEST_SENT |
5-Notice |
Broadband license request sent for %lu license with configured license count %lu |
- |
sss |
LOG_STD_ACTION |
|
SSSMGR-5-IFCFG_NOTALLWED_IN_SVC |
5-Notice |
Interface-config not allowed at service config level ignoring |
Interface-config attribute is not allowed while in a service profile. It is only supported in user profiles. |
sss |
"Remove interface-config attribute from the service profile and " "reconfigure using a user profile." |
|
SSSMGR-5-UNSUPPORTED_CFG_NOTICE |
5-Notice |
Unsupported configuration detected [chars] |
The value of the specified configuration parameter was out of range. This is not considered an error as the value was adjusted to be within the supported range. Update the configuration source to a value within the supported range to avoid this message. |
sss |
LOG_STD_NO_ACTION |
|
STARTTHREAD-1-LDP |
1-Alert |
ERRMSG_NOFLAGS |
- |
- |
- |
|
STATE_FAILURE-3-MPLS_TE_HA |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
STILE_CLIENT-4-MAX_LINK_TOUCH_CLEAR |
4-Warning |
NBAR number of [chars] has declined below its threshold links are available for [chars]. |
After NBAR was in links shortage the number of links has declined below its threshold. New traffic flows will be classified properly |
qfp-nbar |
LOG_STD_NO_ACTION |
|
STILE_CLIENT-4-MAX_LINK_TOUCH_WARN |
4-Warning |
NBAR number of [chars] threshold is reached can't allocate more memory for [chars]. |
Because of non-availability of flow links new traffic flows may not be classified properly |
qfp-nbar |
LOG_STD_NO_ACTION |
|
STILE_CLIENT-4-NBAR_ACTIVATION_FAILED |
4-Warning |
NBAR activation process has failed with errcode [dec]. |
Activation of NBAR has failed. the cause is provided through the error code from cerrno.h |
qfp-nbar |
LOG_STD_NO_ACTION |
|
STILE_CLIENT-4-NBAR_GENERAL_FAILED |
4-Warning |
An error occured with errcode [dec]. |
An error occured will not handle the messages wait for deactivate the cause is provided through the error code from cerrno.h |
qfp-nbar |
LOG_STD_NO_ACTION |
|
STILE_CLIENT-4-NBAR_MEMORY_BOUNDARY_TOUCH_CLEAR |
4-Warning |
NBAR memory utilization has declined below its threshold memory is available for [chars]. |
After NBAR was in memory shortage memory utilization has declined below its threshold New traffic flows will be classified properly |
qfp-nbar |
LOG_STD_ACTION |
|
STILE_CLIENT-4-NBAR_MEMORY_BOUNDARY_TOUCH_WARN |
4-Warning |
NBAR reached maximum configured memory utilization. Can't allocate more memory for [chars]. |
Because of NBAR memory shortage new flows may not be classified properly |
qfp-nbar |
LOG_STD_ACTION |
|
STILE_CLIENT-4-NBAR_NOT_ENOUGH_STATIC_MEMORY |
4-Warning |
NBAR does not have enough memory to be activated. |
System does not have enough free memory to allow activation of NBAR |
qfp-nbar |
LOG_STD_NO_ACTION |
|
STILE_CLIENT-4-SYS_FREE_MEMORY_LOW_WATERMARK_TOUCH_CLEAR |
4-Warning |
System free memory has increased above its lower watermark memory is available for [chars]. |
After system memory was in shortage free memory has increased above its lower watermark New traffic flows will be classified properly |
qfp-nbar |
LOG_STD_ACTION |
|
STILE_CLIENT-4-SYS_FREE_MEMORY_LOW_WATERMARK_TOUCH_WARN |
4-Warning |
System free memory has reached its lower watermark. Can't allocate more memory for [chars]. |
Because of system memory shortage new flows may not be classified properly |
qfp-nbar |
LOG_STD_ACTION |
|
STILE_PROXY-3-IPC_NORES |
3-Error |
No space for the IPC reply size [dec] |
For a request from upper STILE software stack layers it was not possible to allocate space for a reply for the specified size. The consequence of this could be a stuck binding that cannot be established etc. In rare cases this could also affect other operations such as feature activation. |
cpp-ucode |
"This is normally a software issue. " LOG_STD_ACTION |
|
STILE_PROXY-3-IPC_OPEN_REPLY |
3-Error |
IPC Open Reply failed request [dec] |
For a request from upper STILE software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck binding that cannot be established etc. In rare cases this could also affect other operations such as feature activation. |
cpp-ucode |
"This is normally a software issue. " LOG_STD_ACTION |
|
STILE_PROXY-3-IPC_UNHANDLED |
3-Error |
type [dec] |
An unknown message was received by the STILE Client Proxy. |
cpp-ucode |
LOG_STD_ACTION |
|
STILE_PROXY-3-PROXY_IPC_SEND_FAILED |
3-Error |
IPC send msg for [chars] [dec] failed |
IPC failed to reply |
cpp-ucode |
LOG_STD_ACTION |
|
STILE_PROXY-3-PROXY_SLINK_MEM_EXTEND_FAILED |
3-Error |
- |
Increasing of stile slink pool failed. |
cpp-ucode |
LOG_STD_ACTION |
|
STILE_PROXY-3-SLINK_MEM_REQ_FAILED |
3-Error |
- |
IPC Failure occurred when attempting to request more stile link memory. |
cpp-ucode |
LOG_STD_ACTION |
|
STILE-3-NBAR_DEBUG_REG_FAILED |
3-Error |
[dec] |
NBAR Conditional debugging registration failed. |
- |
- |
|
STILE-3-PDL_DEBUG |
3-Error |
Action action_print is supported only in pdl debug mode. Text = [chars] Value = 0x[hec] |
print action output |
cpp-ucode |
LOG_STD_ACTION |
|
STILE-3-VM_ERRORS |
3-Error |
STILE VM traceback with cause: *[chars]* please see FP log for more information |
- |
qfp-nbar |
- |
|
STILE-4-STATIC_SLINK_ALLOC_FAILED |
4-Warning |
Memory resources exhausted to configure custom/sub protocol |
This message indicates that current user configuration could not be\n activated because of unavailability of memory resources.\n The NBAR cannot classify packets for this new protocol configured. |
cpp-ucode |
"The memory resource exhausion is happening because too many port range\n" "based protocols are configured by the user.\n" "Recommended action is to avoid very large range of ports." |
|
STORM_CONTROL-2-SHUTDOWN |
2-Critical |
Storm control shut down [chars] |
Excessive traffic has been detected on a port that has been configured to be shutdown if a storm event is detected. |
- |
"Once the source of the packet storm has been fixed reenable " "the port using port configuration command." |
|
STORM_CONTROL-3-FILTERED |
3-Error |
A [chars] storm detected on [chars]. A packet filter action has been applied on the interface. |
The amount of traffic detected on the interface exceeded the configured threshold values. The system is filtering excess traffic when packet is received. Packet traffic is not being forwarded by the system. |
- |
"Determine and fix the root cause of the excessive" "traffic on the interface." |
|
STORM_CONTROL-3-SHUTDOWN |
3-Error |
A packet storm was detected on [chars]. The interface has been disabled. |
The amount of traffic detected on the interface exceeded the configured threshold values. Since the interface was configured to be shutdown if a packet storm event is detected it has been placed in error disable state. |
- |
"If automatic recovery is preferred the error disable recovery" "mechanism can be used. Determine and fix the root cause of" "the excessive traffic on the interface" |
|
STORM_CONTROL-3-TRAP |
3-Error |
A packet storm was detected on [chars]. Sending SNMP trap. |
The amount of traffic detected on the interface exceeded the configured threshold values. Since the interface was configured to send SNMP trap if a packet storm event is detected it has has generated the trap. |
- |
"Determine and fix the root cause of the excessive traffic on the" " interface." |
|
STORM_CONTROL-5-ABATED |
5-Notice |
A [chars] storm abated on [chars]. Packet filter does not apply on the interface. |
The amount of traffic on the interface is below the configured threshold values. The system is not filtering traffic when packet is received. Packet traffic is being forwarded by the system. |
- |
"No need further action" |
|
STP_ISSU-2-GET_BUFFER |
2-Critical |
STP ISSU client failed to get buffer for message. Error: [dec] [chars] |
STP 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. |
L2 |
"show logging and show checkpoint client" |
|
STP_ISSU-2-INIT |
2-Critical |
STP ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The STP 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. |
L2 |
LOG_STD_ACTION |
|
STP_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
STP ISSU client failed to send negotiation message. Error: [dec] [chars] |
The STP 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. |
L2 |
"show logging and show checkpoint client" |
|
STP_ISSU-2-SESSION_ARBITRATE |
2-Critical |
STP ISSU client failed to register arbitrate callback. Error: [dec] [chars] |
The STP ISSU client failed to register arbitrate callback. If a problem occurs with the callback registration the standby device cannot be brought up properly. |
L2 |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
STP_ISSU-2-SESSION_NEGO |
2-Critical |
STP ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The STP 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. |
L2 |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
STP_ISSU-2-SESSION_REGISTRY |
2-Critical |
STP ISSU client failed to register session information. Error: [dec] [chars] |
The STP ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
L2 |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
STP_ISSU-3-INVALID_CAPABILITY |
3-Error |
STP ISSU client: invalid capability list |
STP ISSU client observed an error during capability negotiaiton. When this error happens there is a mismatch in the client capability between the active and standby unit. |
L2 |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
STP_ISSU-3-INVALID_SESSION |
3-Error |
STP ISSU client does not have a valid registered session. |
STP ISSU client does not have a valid registered session. |
L2 |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
STP_ISSU-3-MSG_NOT_OK |
3-Error |
STP ISSU client 'Message Type [dec]' is not compatible |
The STP ISSU client received an incompatible message from the peer device. The message cannot be processed. |
L2 |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
STP_ISSU-3-MSG_SIZE |
3-Error |
STP ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The STP ISSU client failed to calculate the MTU for the specified message. The STP ISSU client is not able to send the message to the standby device. |
L2 |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
STP_ISSU-3-POLICY_NOT_SUPPORTED |
3-Error |
STP ISSU client does not support Message Type [dec] |
STP ISSU client received an message type which it does not support. The policy is applied to make the session incompatible. |
L2 |
"show issu session <client_id>" |
|
STP_ISSU-3-REJECTED_CAPABILITY |
3-Error |
STP ISSU client rejected capability '[chars]' |
STP ISSU client rejected a capability during negotiaiton. When this error happens there is a mismatch in the client capability between the active and standby unit. |
L2 |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
STP_ISSU-3-REJECTING_CAPABILITY |
3-Error |
STP ISSU client rejecting capability '[chars]' |
STP ISSU client is rejecting a capability during negotiaiton. When this error happens there is a mismatch in the client capability between the active and standby unit. |
L2 |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
STP_ISSU-3-SESSION_UNREGISTRY |
3-Error |
STP ISSU client failed to unregister session information. Error: [dec] [chars] |
The STP ISSU client failed to unregister session information. |
L2 |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
STP_ISSU-3-TRANSFORM_FAIL |
3-Error |
STP ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The STP 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 STP state between the active device and the standby device is not identical. |
L2 |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
STUN-2-NOBUF |
2-Critical |
Interface [chars] no buffer available to [chars] |
A memory shortage existed at the time that the configuration command was issued. This condition is rare and under normal conditions temporary. |
- |
"Reconfigure the STUN group. If memory shortages persist call your " "Cisco technical support representative for assistance." |
|
STUN-2-NOMEMORY |
2-Critical |
No memory available: [chars] |
The requested operation failed because of a low memory condition. |
- |
"Reduce other system activity to ease memory demands. If conditions " "warrant upgrade to a larger memory configuration." |
|
STUN-2-NOTGI |
2-Critical |
Please remove and redefine protocol group [dec] |
An internal error occurred. The configuration is irregular. |
- |
"Remove and reconfigure the STUN protocol group. Record the " "configuration and call your Cisco technical support " "representative for assistance." |
|
STUN-3-BADCONN |
3-Error |
CONN: bad connection [dec] peer: [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
STUN-3-BADLENOP |
3-Error |
[chars]: bad len or unknown op op [dec] len [dec] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
STUN-3-BADMAGIC |
3-Error |
[chars]: wrong magic mine [hec] theirs [hec] [dec] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
STUN-3-BADMAGICTCP |
3-Error |
[chars]: peer [chars] wrong magic mine [hec] theirs [hec] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
STUN-3-BADPASSIVEOPEN |
3-Error |
passive open from [inet][dec] -> [dec] failed |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
STUN-3-CONNILLSTATE |
3-Error |
CONN: Peer [chars] illegal state [dec] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
STUN-3-NOINPIDB |
3-Error |
Input idb not set |
A software or hardware error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
STUN-3-SENDPUNT |
3-Error |
[chars]: sent [chars] to [chars] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
STUN-3-SENDPUNTTCP |
3-Error |
[chars]: sent [chars] to [[dec]][inet] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
STUN-4-DUPROUTE |
4-Warning |
Cannot define duplicate route on the\n\ same group |
This route command is defined on another interface belonging to the same group. Cannot define duplicate route on the same group |
- |
"Consider defining a new group and moving this " "interface onto that group" |
|
STUN-4-ERR |
4-Warning |
[chars]: [chars]: [chars] op [hec] len [dec] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
STUN-4-PEERSTATE |
4-Warning |
Peer [chars] wrong state [dec] [dec] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
STUN-6-CONNOPENFAIL |
6-Information |
CONN: peer [chars] open failed [chars] [[dec]] |
An attempt to connect to a remote TCP STUN peer failed. |
- |
"Verify that the remote peer is accessible from this router that it is " "running software capable of supporting STUN and that it is configured " "correctly." |
|
STUN-6-OPENED |
6-Information |
[chars]: peer [chars] opened [previous state [chars]] |
A connection attempt to a remote peer completed successfully OPENED PASSIVE-OPEN or is in the process of being opened OPENING. This is |
- |
LOG_STD_NO_ACTION |
|
STUN-6-OPENING |
6-Information |
CONN: opening peer [chars] [dec] |
A connection attempt to a remote peer completed successfully OPENED PASSIVE-OPEN or is in the process of being opened OPENING. This is |
- |
LOG_STD_NO_ACTION |
|
STUN-6-PASSIVEOPEN |
6-Information |
passive open [inet][dec] -> [dec] |
A connection attempt to a remote peer completed successfully OPENED PASSIVE-OPEN or is in the process of being opened OPENING. This is |
- |
LOG_STD_NO_ACTION |
|
STUN-6-PEERSHUTDOWN |
6-Information |
shutting down peer [chars] on [chars] |
A connection to a remote peer is being shut down. This is typically the result of user intervention in STUN reconfiguration or disabling. This is good expected behavior. |
- |
LOG_STD_NO_ACTION |
|
STUN-6-RECONNECT |
6-Information |
PHDR: reconnect from peer [chars] |
A remote peer reestablished a connection to this router. |
- |
LOG_STD_NO_ACTION |
|
STUN-6-TCPFINI |
6-Information |
peer [chars] closed [previous state [chars]] |
A remote peer closed a STUN connection with this router. |
- |
"Examine the other router to see why it closed this connection with " "this peer. This can be caused by normal events such as " "reconfiguration." |
|
STUN-6-TCPPEERSHUT |
6-Information |
[chars] [chars] [inet][dec] |
This route closed a STUN connection with a remote peer. |
- |
"Examine this router to see why it closed this connection with this " "peer. This can be caused by normal events such as " "reconfiguration." |
|
SUBSYS-2-BADCLASS |
2-Critical |
Bad subsystem class [dec] - ignoring subsystem |
A software consistency check failed. |
Determine the component from the subsystem displayed in the error message. |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SUBSYS-2-BADSEQUENCE |
2-Critical |
Subsystem [chars] has cross-class sequence for [chars] |
A software or hardware error occurred. |
Determine the component from the subsystem displayed in the error message. |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SUBSYS-2-BADVERSION |
2-Critical |
Bad subsystem version number [dec] - ignoring subsystem |
A software consistency check failed. |
Determine the component from the subsystem displayed in the error message. |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SUBSYS-2-MISMATCH |
2-Critical |
Kernel and subsystem version differ [dec].[dec] - ignoring subsystem |
A software consistency check failed. |
Determine the component from the subsystem displayed in the error message. |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SUBSYS-2-NOTFOUND |
2-Critical |
Subsystem [chars] needs subsystem [chars] to start |
A software consistency check failed. |
Determine the component from the subsystem that is in need as displayed in the error message. |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SUBSYS-2-RECURSION |
2-Critical |
Maximum sequence depth exceeded [dec] by [chars] |
A software or hardware error occurred. |
os |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SUBSYS-3-NOAPIHOOK |
3-Error |
The API [chars] has no lookup hook for subsystems. |
This process uses the named API but the process initialization\n\ code could not find the subsystem-initialization hook for this API.\n\ Process initialization cannot proceed without all hooks being present. |
build |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative along with output from\n\ 'show tech'." |
|
SUBSYS-3-PAGEZERO |
3-Error |
The [chars] class subsystem [chars] was being initialized. |
In all Cisco products the first 256 bytes of memory is unused and off\n\ limits. Newer platforms have hardware to immediately trap reads or\n\ writes to this area. Older platforms periodically perform checks on\n\ this memory. This message appears only on older platforms and\n\ indicates that this off limits memory area was modified. |
Determine the component from the process name displayed in the\n\ error message. |
"Copy the error message exactly as it appears and report it\n\ to your technical support representative." |
|
SUBSYS-3-UNORDERED |
3-Error |
The subsys class [dec][chars] has no initialization order. |
The specified class subsystem has an unknown initialization order. |
os |
"Copy the error message exactly as it appears and report it " "to your technical support representative along with output from " "'show tech'." |
|
SUBSYS-4-MALLOC |
4-Warning |
Class [chars] subsys [chars] bytes [dec] malloc [dec] |
This message is only for tracking malloc/free in a subsys init. |
- |
"For development debugging only." |
|
SUDI-1-INTERNAL_ERROR |
1-Alert |
[chars] |
Secure UDI encountered an internal error. |
petra-platform |
"If this occurs the switch failed to authenticate itself. " "Please contact Cisco's Technical Assistance Center for more " "information." |
|
SUDI-1-VALIDATION_ERROR |
1-Alert |
[chars] |
[chars] Secure UDI validation failed. |
petra-platform |
"If this occurs the switch failed to authenticate itself. " "Please contact Cisco's Technical Assistance Center for more " "information." |
|
SUDI-5-VALIDATION_CHECK |
5-Notice |
[chars] |
- |
- |
- |
|
SUDI-5-VALIDATION_SUCCESS |
5-Notice |
[chars] |
- |
- |
- |
|
SUMATRA_TIMING-3-MSGDISPATCH |
3-Error |
Unable to dispatch received TDL message from TIMING daemon |
An unexpected condition has occurred while IOS was trying to dispatch a TDL message received from TIMING daemon. |
iiot_rtr_timing |
LOG_STD_ACTION |
|
SUMATRA_TIMING-3-MSGINITFAIL |
3-Error |
Failed to initalize required TIMING resource: [chars] |
During the initialization of the resources required by TIMING a failure occured. This has prevented TIMING from being activated. |
iiot_rtr_timing |
LOG_STD_ACTION |
|
SUNRPC_ALG-3-CHUNK_CREATE_FAIL |
3-Error |
- |
Chunk create failed. Sun RPC ALG will not be able to finish initialization. |
cpp-ucode |
LOG_STD_ACTION |
|
SUNRPC_ALG-3-L7_DATA_CREATE_ERROR |
3-Error |
- |
Error during L7 data creation. |
cpp-ucode |
LOG_STD_ACTION |
|
SW_DA-1-DETECTION |
1-Alert |
detected dual-active condition[chars] |
The specified dual-active method detected a dual-active scenario and caused switch to go into recovery mode. |
dual-active |
LOG_STD_NO_ACTION |
|
SW_DA-1-RECOVERY |
1-Alert |
Dual-active condition detected: Starting recovery-mode all non-VSL interfaces have been shut down |
A dual-active situation has occurred due to VSL going down. The VSL has become inactive and both chassis have taken over the role of the active virtual switch. To fix this condition the standby virtual switch has become active and taken control of the network. All non-VSL interfaces on the original active virtual switch will be errdisabled or shut down. |
dual-active |
"Attempt to determine the reason why VSL has gone down and " "correct it. Once VSL has been re-established the original " "active virtual switch will reload." |
|
SW_DA-1-VSL_RECOVERED |
1-Alert |
VSL has recovered during dual-active situation: Reloading switch [dec] |
The VSL between the two active virtual switches in a dual-active situation has gone up. The virtual switch in recovery mode must be reloaded to re-enable all non-VSL interfaces which were shut down when the dual-active situation was first entered. |
dual-active |
LOG_STD_NO_ACTION |
|
SW_DA-3-DA_APPLY_IP_FAILED |
3-Error |
Unable to set recovery IP address on [chars] |
The switch was unable to set IP address of management interface\n\ to the IP configured for recovery. |
dual-active |
LOG_STD_NO_ACTION |
|
SW_DA-3-DA_CAPTURE_CONFIG_FAILED |
3-Error |
Unable to capture IP address configured on [chars] |
The switch was unable to capture config of management interface\n\ as part of changing IP address on interface to the IP configured\n\ for recovery. |
dual-active |
LOG_STD_NO_ACTION |
|
SW_DA-3-DA_CLEAR_IP_FAILED |
3-Error |
Unable to clear IP address configured on [chars] |
The switch was unable to clear IP address of management interface\n\ as part of changing IP address on interface to the IP configured\n\ for recovery. |
dual-active |
LOG_STD_NO_ACTION |
|
SW_DA-3-DA_INIT_FAILED |
3-Error |
Unable to initialize dual-active detection/recovery \[chars]\ |
The switch was unable to setup dual-active detection/recovery system.\n\ The result is that dual-active detection/recovery may not work. |
dual-active |
LOG_STD_NO_ACTION |
|
SW_DA-3-DA_JOB_FAILED |
3-Error |
Unable to handle dual-active recovery : [chars] |
The switch was unable to handle dual-active recovery job. This could \n\ be because the job handler does not exist or sending a message to \n\ the recovery job handler failed. |
dual-active |
LOG_STD_NO_ACTION |
|
SW_DA-3-DA_LOOPBACK_SHUTDOWN_FAILED |
3-Error |
Unable to shutdown loopback interface : [chars] [chars] |
The switch was unable to handle shutdown of loopback interface while\n\ the switch is in recovery mode. This could be because the job handler\n\ does not exist or sending a message to the job handler\n\ failed. |
dual-active |
LOG_STD_NO_ACTION |
|
SW_DA-3-DA_RELOAD_FAILED |
3-Error |
Unable to reload the chassis : [chars] |
The switch was unable to reload the chassis while\n\ the switch is in recovery mode. This could be because the job handler\n\ does not exist or sending a message to the job handler\n\ failed. |
dual-active |
LOG_STD_NO_ACTION |
|
SW_DAI-4-ACL_DENY |
4-Warning |
%ld Invalid ARPs [chars] on [chars] vlan [dec].[[enet]/[chars]/[enet]/[chars]/[clock]] |
- |
arp-inspection |
LOG_STD_NO_ACTION |
|
SW_DAI-4-DHCP_SNOOPING_DENY |
4-Warning |
%ld Invalid ARPs [chars] on [chars] vlan [dec].[[enet]/[chars]/[enet]/[chars]/[clock]] |
The switch has received ARP packets considered invalid by ARP inspection.\n\ The packets are bogus and their presence may be an indication of \n\ man-in-the-middle attacks being attempted in the network. This message\n\ is logged when the senders ip and mac binding for the received vlan \n\ is not present in the dhcp snooping database. |
arp-inspection |
LOG_STD_NO_ACTION |
|
SW_DAI-4-INVALID_ARP |
4-Warning |
%ld Invalid ARPs [chars] on [chars] vlan [dec].[[enet]/[chars]/[enet]/[chars]/[clock]] |
The switch has received ARP packets considered invalid by ARP inspection.\n\ The packets are bogus and they do not pass one or more of source mac or \n\ destination mac or IP validation checks or are otherwise invalid. |
arp-inspection |
LOG_STD_NO_ACTION |
|
SW_DAI-4-PACKET_BURST_RATE_EXCEEDED |
4-Warning |
[dec] packets received in [dec] seconds on [chars]. |
The switch has received the given number of ARP packets in the specified\n\ burst interval. The interface is errdisabled when the switch receives\n\ packets at a rate higher than the configured packet rate every second \n\ over the configured burst interval. The message is logged just before\n\ the interface is err-disabled and if the configured burst interval is\n\ more than a second. |
arp-inspection |
LOT_STD_NO_ACTION |
|
SW_DAI-4-PACKET_RATE_EXCEEDED |
4-Warning |
[dec] packets received in [dec] milliseconds on [chars]. |
The switch has received the given number of ARP packets in the given\n\ duration on the given interface. This message is logged just before \n\ the port is err-disabled because of exceeded packet rate. And this\n\ message is logged when the burst interval is set to 1 second. |
arp-inspection |
LOT_STD_NO_ACTION |
|
SW_DAI-4-SPECIAL_LOG_ENTRY |
4-Warning |
%ld Invalid ARP packets [[clock]] |
The switch has received ARP packets considered invalid by ARP inspection.\n\ The packets are bogus and their presence may be an indication of \n\ man-in-the-middle attacks being attempted in the network.\n\ This message differs from other messages in that while the other\n\ can be used to provide as much information of the packet as possible\n\ this message is used as a catch all message when the rate of incoming\n\ packets exceed DAI logging rate. |
arp-inspection |
LOT_STD_NO_ACTION |
|
SW_DAI-6-ACL_PERMIT |
6-Information |
%ld ARPs [chars] on [chars] vlan [dec].[[enet]/[chars]/[enet]/[chars]/[clock]] |
The switch has received ARP packets that have been permitted as a\n\ result of ACL match. |
arp-inspection |
LOG_STD_NO_ACTION |
|
SW_DAI-6-ARP_PROBE_PERMIT |
6-Information |
%ld ARPs [chars] on [chars] vlan [dec].[[enet]/[inet]/[enet]/[inet]/[clock]] |
This message is logged when an ARP packet with a sender IP address of 0.0.0.0 has been permitted. These packets are used as ARP probes by various network devices. These messages are not logged by default but only when arp-probe logging is enabled. |
arp-inspection |
LOG_STD_NO_ACTION |
|
SW_DAI-6-DHCP_SNOOPING_PERMIT |
6-Information |
%ld ARPs [chars] on [chars] vlan [dec].[[enet]/[chars]/[enet]/[chars]/[clock]] |
The switch has received ARP packets that have been permitted as a\n\ result of senders IP and MAC address match against the dhcp snooping\n\ database for the received vlan. |
arp-inspection |
LOG_STD_NO_ACTION |
|
SW_MACAUTH-4-UNAUTH_MAC |
4-Warning |
Unauthenticated MAC [enet] on port [chars] |
The switch has received an unauthenticated MAC address on the specified\n\ port. |
mac-authentication |
LOG_STD_NO_ACTION |
|
SW_MACAUTH-5-CLEAR_TABLE |
5-Notice |
MAC Authentication Table Cleared |
MAC Authentication Table was cleared. |
mac-authentication |
LOG_STD_NO_ACTION |
|
SW_MACAUTH-5-MAC_AUTHENTICATED |
5-Notice |
MAC [enet] was authenticated |
The switch has received a cli to authenticate a MAC. |
mac-authentication |
LOG_STD_NO_ACTION |
|
SW_MACAUTH-5-MACAUTH_ENADSA |
5-Notice |
MAC Authentication [chars] |
MAC Authentication was just enabled/disabled |
mac-authentication |
LOG_STD_NO_ACTION |
|
SW_MATM-4-MACFLAP_NOTIF |
4-Warning |
Host [enet] in [chars] [dec] is flapping between port [chars] and port [chars] |
The system has found the specified host moving between the specified ports. |
- |
"Check the network for possible loops." |
|
SW_MATM-4-WIRELESS_MAC_MOVE_DENY_NOTIF |
4-Warning |
Host [enet] moving from Port [chars] to Port [chars] as wired entry not allowed |
The system has found the specified host moving between the specified ports. The host transition from wireless to wired not allowed. |
sw-matm mac-table |
"Check that this move does not happen too often" |
|
SW_MATM-4-WIRELESS_MAC_MOVE_NOTIF |
4-Warning |
Host [enet] moving from Port [chars] to Port [chars] as wireless entry |
The system has found the specified host moving between the specified ports. The host transitioned from wired to wireless. |
- |
"Check that this move does not happen too often" |
|
SW_MGR-3-CM_ERROR |
3-Error |
Connection Manager Error - [chars]. |
A Segment Switch Connection Manager error occurred. |
- |
LOG_STD_ACTION |
|
SW_MGR-3-CM_ERROR_CLASS |
3-Error |
Connection Manager Error: Class [chars]: - [chars]. |
A Segment Switch Connection Manager error occurred. |
- |
LOG_STD_ACTION |
|
SW_MGR-3-CM_ERROR_FEATURE |
3-Error |
Connection Manager Feature Error: [chars] - [chars]. |
- |
- |
- |
|
SW_MGR-3-CM_ERROR_FEATURE_CLASS |
3-Error |
Connection Manager Feature Error: Class [chars]: [chars] - [chars]. |
- |
- |
- |
|
SW_MGR-3-FHM_ERROR |
3-Error |
SSM Feature Handler Manager Error - [chars]. |
A Feature Handler Manager error occurred. |
- |
LOG_STD_ACTION |
|
SW_MGR-3-INVALID_HANDLE |
3-Error |
Segment Manager Error - Invalid [chars] handle - [dec]. |
A Connection Manager error occurred due to a invalid handle. |
- |
LOG_STD_ACTION |
|
SW_MGR-3-INVALID_SEGMENT |
3-Error |
Segment Switch Manager Error - Invalid segment - [chars]. |
A Segment Switch Manager error occurred due to a invalid segment. |
- |
LOG_STD_ACTION |
|
SW_MGR-3-SM_ERROR |
3-Error |
Segment Manager Error - [chars]. |
A Segment Manager error occurred. |
- |
LOG_STD_ACTION |
|
SW_MGR-3-SSM_SEG_ISSU |
3-Error |
SSM Segment ISSU: [chars] not supported. |
ISSU of this SSM Segment is not supported. |
- |
LOG_STD_NO_ACTION |
|
SW_MGR-3-XDRREGISTRATION |
3-Error |
XDR failed to register [chars] client due to [chars] |
Failure to register the said XDR client. |
- |
LOG_STD_NO_ACTION |
|
SW_VLAN_ISSU-2-GET_BUFFER |
2-Critical |
Switch Vlan ISSU client failed to get buffer for message. Error: [dec] [chars] |
The Switch Vlan 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. |
sw-vlan |
"show logging and show checkpoint client" |
|
SW_VLAN_ISSU-2-INIT |
2-Critical |
Switch Vlan ISSU client initialization failed to [chars]. Error: [dec] [chars] |
The Switch Vlan 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. |
sw-vlan |
LOG_STD_ACTION |
|
SW_VLAN_ISSU-2-SEND_NEGO_FAILED |
2-Critical |
Switch Vlan ISSU client failed to send negotiation message. Error: [dec] [chars] |
The Switch Vlan 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. |
sw-vlan |
"show logging and show checkpoint client" |
|
SW_VLAN_ISSU-2-SESSION_NEGO |
2-Critical |
Switch Vlan ISSU client encountered unexpected client nego_done. Error: [dec] [chars] |
An ISSU-compliant client transitions through a series of internal states. The Switch Vlan 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. |
sw-vlan |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
SW_VLAN_ISSU-2-SESSION_REGISTRY |
2-Critical |
Switch Vlan ISSU client failed to register session information. Error: [dec] [chars] |
The Switch Vlan ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly. |
sw-vlan |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
SW_VLAN_ISSU-3-CAP_INVALID_SIZE |
3-Error |
Switch Vlan ISSU client capability list is empty. |
The Switch Vlan ISSU client capability exchange list size is invalid. |
sw-vlan |
"show issu capability entires <Client_ID>" |
|
SW_VLAN_ISSU-3-CAP_NOT_COMPATIBLE |
3-Error |
Switch Vlan ISSU client capability exchange result incompatible. |
The Switch Vlam ISSU client capability exchange have negotiated as incompatible with the peer. |
sw-vlan |
"show issu negotiated capability <Session_ID>" |
|
SW_VLAN_ISSU-3-DOWNGRADE_NOT_ALLOWED_WITH_VTPV3 |
3-Error |
VTP version [dec] is configured in vlan.dat file. Device cannot be downgraded to an image that does not support this VTP version. |
The VTP version is not saved in startup or running config. It is stored in vlan.dat file. If vlan.dat file content is copied from some other source or if the pre-requisites for 'VTP version 3' is removed from the system via CLI and then the system is re-started the efective VTP version differs from the one stored in the file. |
sw-vlan |
"Please use 'vtp version' CLI to re-configure VTP version." |
|
SW_VLAN_ISSU-3-INVALID_SESSION |
3-Error |
Switch Vlan ISSU client does not have a valid registered session. |
The Switch Vlan ISSU client does not have a valid registered session. |
sw-vlan |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
SW_VLAN_ISSU-3-MSG_NOT_COMPATIBLE_WITH_PEER |
3-Error |
'Message Type [dec]' is not supported by Switch Vlan ISSU client at peer |
The Switch Vlan ISSU client at the peer supervisor is not compatible for this message type. The Switch Vlan client will be marked as incompatible with the peer. |
sw-vlan |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
SW_VLAN_ISSU-3-MSG_NOT_OK |
3-Error |
Switch Vlan ISSU client 'Message Type [dec]' is not compatible |
The Switch Vlan ISSU client received an incompatible message from the peer device. The message cannot be processed. |
sw-vlan |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
SW_VLAN_ISSU-3-MSG_SIZE |
3-Error |
Switch Vlan ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars] |
The Switch Vlan ISSU client failed to calculate the MTU for the specified message. The Switch Vlan ISSU client is not able to send the message to the standby device. |
sw-vlan |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
SW_VLAN_ISSU-3-SESSION_UNREGISTRY |
3-Error |
Switch Vlan ISSU client failed to unregister session information. Error: [dec] [chars] |
The Switch Vlan ISSU client failed to unregister session information. |
sw-vlan |
"show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
SW_VLAN_ISSU-3-TRANSFORM_FAIL |
3-Error |
Switch Vlan ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars] |
The Switch Vlan 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 Switch Vlan state between the active device and the standby device is not identical. |
sw-vlan |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
SW_VLAN-3-IIF_ID_ALLOC_FAILED |
3-Error |
IIF_ID alloc failed for vlan [dec] due to memory allocation failure. Some features will not work. |
The system is low on memory due to which IIF-ID allocation failed. This results in failure to apply polices such as QoS and Security acls on this vlan. |
sw-vlan |
LOG_STD_REDUCE_ACTION "Once memory is available shutdown the vlan and then unshut the vlan" |
|
SW_VLAN-3-IIF_ID_REGISTRATION_FAILED |
3-Error |
IIF_ID registration failed for vlan [dec] due to memory allocation failure. Some features will not work. Vlan has been shutdown |
The system is low on memory due to which IIF-ID registration failed. This results in failure to apply polices such as QoS and Security acls on this vlan. If vlan exists it is shutdown. If vlan doesn't exist then it will be shutdown when it is created. |
sw-vlan |
LOG_STD_REDUCE_ACTION "Once memory is available run 'no shutdown' on the vlan" |
|
SW_VLAN-3-MALLOC_FAIL |
3-Error |
Failed to allocate [dec] bytes |
Memory allocation failed. |
sw-vlan |
LOG_STD_SH_TECH_ACTION |
|
SW_VLAN-3-VLAN_PM_NOTIFICATION_FAILURE |
3-Error |
VLAN Manager synchronization failure with Port Manager over [chars] |
Due to lack of ready pool space the VLAN manager dropped a notification\n\ from the Port Manager as indicated by the message. |
sw-vlan vtp pm |
LOG_STD_ACTION |
|
SW_VLAN-3-VTP_PROTOCOL_ERROR |
3-Error |
VTP protocol code internal error: [chars] |
VTP protocol code encountered an unexpected error will processing\n\ configuration request packet or timer expiration. |
sw-vlan vtp |
LOG_STD_SH_TECH_ACTION |
|
SW_VLAN-4-BAD_PM_VLAN_COOKIE_RETURNED |
4-Warning |
VLAN manager unexpectedly received a bad PM VLAN cookie from the Port\n\ Manager VLAN indicated: [dec] |
The VLAN manager received an upcall from the Port Manager containing a\n\ VLAN cookie which translated to a bad VLAN number. |
sw-vlan pm |
LOG_STD_SH_TECH_ACTION |
|
SW_VLAN-4-BAD_STARTUP_VLAN_CONFIG_FILE |
4-Warning |
Failed to configure VLAN from startup-config. Fallback to use VLAN configuration file from non-volatile memory |
VLAN software failed to use VLAN configuration from startup-config\n\ file. It will fallback to use the binary VLAN configuration file\n\ in non-volatile memory. |
sw-vlan |
LOG_STD_NO_ACTION |
|
SW_VLAN-4-BAD_VLAN_CONFIGURATION_FILE |
4-Warning |
VLAN configuration file contained incorrect verification word: 0x[hec] |
The VLAN configuration file read by the VLAN manager did not begin with\n\ correct value which would indicate a valid VLAN configuration file. Thus\n\ it has been rejected. |
sw-vlan ifs |
LOG_STD_ACTION |
|
SW_VLAN-4-BAD_VLAN_CONFIGURATION_FILE_VERSION |
4-Warning |
VLAN configuration file contained unknown file version: [dec] |
The VLAN configuration file read by the VLAN manager contained an\n\ unrecognized file version number. This may indicate an attempt to\n\ regress to an older version of the VLAN manager software. |
sw-vlan ifs |
LOG_STD_ACTION |
|
SW_VLAN-4-BAD_VLAN_DOMAIN_NAME_LENGTH |
4-Warning |
VLAN configuration file contained incorrect domain name length: [dec] |
The VLAN configuration file read by the VLAN manager did not contain a valid domain name length. Thus it has been rejected. |
sw-vlan ifs |
"Please provision VTP domain name again" |
|
SW_VLAN-4-BAD_VLAN_PASSWORD_LENGTH |
4-Warning |
VLAN configuration file contained incorrect VTP password length: [dec] |
The VLAN configuration file read by the VLAN manager did not contain a valid VTP password length. Thus it has been rejected. |
sw-vlan ifs |
"Please provision VTP password again" |
|
SW_VLAN-4-BAD_VLAN_TIMER_ACTIVE_VALUE |
4-Warning |
Encountered incorrect VLAN timer active value: [chars] |
Due to a software error a VLAN timer was dectected active when it\n\ should have been inactive or inactive when it should have been active. |
sw-vlan vtp |
LOG_STD_ACTION |
|
SW_VLAN-4-EXT_VLAN_INTERNAL_ERROR |
4-Warning |
Extended VLAN manager received an internal error [dec] from [chars]: [chars] |
An unexpected error code was received by the VLAN Manager from the \n\ extended VLAN configuration software. |
sw-vlan |
LOG_STD_SH_TECH_ACTION |
|
SW_VLAN-4-EXT_VLAN_INVALID_DATABASE_DATA |
4-Warning |
Extended VLAN manager received bad data of type [chars]: value [dec] from \n\ function [chars] |
Invalid data was received by the extended VLAN Manager from an extended\n\ VLAN configuration database routine. |
sw-vlan |
LOG_STD_SH_TECH_ACTION |
|
SW_VLAN-4-IFS_FAILURE |
4-Warning |
VLAN manager encountered file operation error: call = [chars] / file = [chars] / code = [dec] [chars] / bytes transfered = [dec] |
The VLAN manager received an unexpected error return from a IOS file\n\ system call. |
sw-vlan ifs |
LOG_STD_ACTION |
|
SW_VLAN-4-NO_PM_COOKIE_RETURNED |
4-Warning |
VLAN manager unexpectedly received a null [chars] type cookie from the Port\n\ Manager data reference: [chars] |
The VLAN manager queried the Port Manager for a reference cookie but\n\ received a NULL pointer instead. |
sw-vlan pm |
LOG_STD_SH_TECH_ACTION |
|
SW_VLAN-4-STARTUP_EXT_VLAN_CONFIG_FILE_FAILED |
4-Warning |
Failed to configure extended range VLAN from startup-config. Error [chars] |
VLAN software failed to use extended VLAN configuration from\n\ startup-config file. All extended range VLANs configuration will be lost\n\ after system boot up. |
sw-vlan |
LOG_STD_NO_ACTION |
|
SW_VLAN-4-VLAN_CREATE_FAIL |
4-Warning |
Failed to create VLANs [chars]: [chars] |
The VLANs specified in the error message could not be created. The VLAN manager called an VLAN database routine to create one or more VLANs but the Port Manager failed the VLAN creation requests. A possible cause of this error is that the VLANs already exist in the Port Manager as internal VLANs. |
sw-vlan |
"Check the internal VLAN usage using 'show vlan internal usage' command. " "Unconfigure the feature which occupies the internal VLAN and retry " "the VLAN creation operation." LOG_STD_SH_TECH_ACTION |
|
SW_VLAN-4-VLANMGR_INVALID_DATABASE_DATA |
4-Warning |
VLAN MANAGER received bad data of type [chars]: value [dec] from function [chars] |
Invalid data was received by the VLAN MANAGER from a VLAN configuration database routine. |
sw-vlan |
LOG_STD_SH_TECH_ACTION |
|
SW_VLAN-4-VTP_DB_SIZE_CHECK_FAILED |
4-Warning |
The [chars] VTP database of length [dec] cannot be supported by the system |
The VTP database size is more than what the system can support. |
sw-vlan |
"Reduce the database size by decreasing the configuration parameters " "example reduce the size of vlan-names" |
|
SW_VLAN-4-VTP_FLOOD_ERROR |
4-Warning |
Primary server request failed\nPrimary server can only change once \n\ every [dec] seconds |
VTP takeover packet received within takeover rate limit |
sw-vlan vtp |
LOG_STD_SH_TECH_ACTION |
|
SW_VLAN-4-VTP_INTERNAL_ERROR |
4-Warning |
VLAN manager received an internal error [dec] from vtp function [chars]: [chars] |
An unexpected error code was received by the VLAN Manager from the VTP\n\ configuration software. |
sw-vlan vtp |
LOG_STD_SH_TECH_ACTION |
|
SW_VLAN-4-VTP_INVALID_DATABASE_DATA |
4-Warning |
VLAN manager received bad data of type [chars]: value [dec] from vtp database\n\ function [chars] |
Invalid data was received by the VLAN Manager from a VTP configuration\n\ database routine. |
sw-vlan vtp |
LOG_STD_SH_TECH_ACTION |
|
SW_VLAN-4-VTP_INVALID_EVENT_DATA |
4-Warning |
VLAN manager received bad data of type [chars]: value [dec] while being called\n\ to handle a [chars] event |
Invalid data was received by the VLAN Manager from the VTP configuration\n\ software. |
sw-vlan vtp |
LOG_STD_SH_TECH_ACTION |
|
SW_VLAN-4-VTP_PRIMARY_SERVER_CHG |
4-Warning |
[enet] has become the primary server for the [chars] VTP feature |
The primary server status has changed and the indicated device has become the primary server for the indicated VTP feature. |
sw-vlan |
LOG_STD_NO_ACTION |
|
SW_VLAN-4-VTP_SEM_BUSY |
4-Warning |
VTP semaphore is unavailable for function [chars]. Semaphore locked by [chars] |
The VTP database is currently locked by another task and is not available.\n\ Users should retry the operation sometime later. |
sw-vlan vtp |
LOG_STD_SH_TECH_ACTION |
|
SW_VLAN-4-VTP_USER_NOTIFICATION |
4-Warning |
VTP protocol user notification: [chars] |
VTP protocol code encountered an unusual diagnostic situation which the\n\ user should be made aware of. |
sw-vlan vtp |
LOG_STD_ACTION |
|
SW_VLAN-6-OLD_CONFIG_FILE_READ |
6-Information |
Old version [dec] VLAN configuration file detected and read OK. Version [dec]\n\ files will be written in the future. |
VLAN software detected an old version of the VLAN configuration file\n\ format. It was able to interpret the file with no problems but will\n\ create files using the new format in the future. |
sw-vlan vtp |
LOG_STD_NO_ACTION |
|
SW_VLAN-6-VLAN_DAT_CACHE_EXISTS |
6-Information |
Unexpected vlan.dat cache exists. Removing the cache and continuing the sync with new set. |
vlan.dat file is synced to the STANDBY via one or more checkpoint message from ACTIVE. The sequence number for each such set of checkpoint messages starts with 1. These messages are cached at the STANDBY till the end-of-set indication is received. Here the STANDBY received a checkpoint message with a size that does not fit the size of cache specified in the checkpoint message with sequence number 1. Please report it to Customer Support. |
sw-vlan |
LOG_STD_SH_TECH_ACTION |
|
SW_VLAN-6-VTP_DOMAIN_NAME_CHG |
6-Information |
VTP domain name changed to [chars]. |
The VTP domain name was changed through configuration to the name\n\ specified in the message. A management domain is the naming scope\n\ of a VLAN name. Each VLAN has a name that is unique within the\n\ management domain. |
sw-vlan vtp |
LOG_STD_NO_ACTION |
|
SW_VLAN-6-VTP_MODE_CHANGE |
6-Information |
VLAN manager changing device mode from [chars] to [chars]. |
Some switch devices must automatically change VTP device modes upon\n\ receipt of a VLAN configuration database containing more than a set\n\ number of VLANs depending on the device. This message indicates that\n\ such a spontaneous conversion has occurred what the previous mode was\n\ and what the current mode is. |
sw-vlan vtp |
LOG_STD_NO_ACTION |
|
SW_VLAN-6-VTP_PRUNING_CHANGE |
6-Information |
VTP Operational Pruning [chars]. |
VTP operational pruning changed. This can happen due to admin pruning change VTP mode changes or VTP config propagation. 'show vtp status' output can be looked up to find the reason for this change. |
sw-vlan vtp |
"Check 'show vtp status' output to find the reason for this change." LOG_STD_NO_ACTION |
|
SW56-1-INITSYS |
1-Alert |
[chars] |
Failed SW56 Initialization. Most likely because lacking of memory |
as |
"The amount of memory available in the router may not be " "sufficient." LOG_STD_ACTION |
|
SW56-3-ERR_MSGQ |
3-Error |
[chars] |
Failed to send message to internal software process |
as |
LOG_STD_ACTION |
|
SWC-3-SWC_HA_INIT_FAILURE |
3-Error |
Failed to register with RF rc = [dec] |
Message HA message received from peer node |
- |
"This message is for informational purposes only" |
|
SWITCH_L2M-3-ALLOC_FAILED |
3-Error |
Allocation of [chars] memory failed for SWITCH_L2M feature in QFP |
Allocation of memory by the QFP SWITCH_L2M feature microcode failed. The name of the memory chunk is specified in the message. This indicates a software failure |
qfp-switch-infra |
LOG_STD_ACTION |
|
SWITCH_L2M-3-INIT_FAILED |
3-Error |
Initialization of the SVI feature in QFP failed |
Initialization of the SWITCH_L2M feature in the QFP failed. This indicates a software failure. |
qfp-switch-infra |
LOG_STD_ACTION |
|
SWITCH_L2M-3-PKT_REPLICA_INIT_FAILED |
3-Error |
Failed to register with generic packet replication for SWITCH_L2M feature in QFP |
SWITCH_L2M initialization of packet replication registration failed. |
qfp-switch-infra |
LOG_STD_ACTION |
|
SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED |
5-Notice |
[chars] detected on port [chars] port's configured trust state is now operational. |
Trusted Boundary detected a device matching the trusted device setting for the port and so has modified the port's trust state. |
- |
LOG_STD_NO_ACTION |
|
SWITCH_QOS_TB-5-TRUST_DEVICE_LOST |
5-Notice |
[chars] no longer detected on port [chars] operational port trust state is now untrusted. |
Trusted Boundary lost contact with a trusted device and so has set the port's trust state to untrusted. |
- |
LOG_STD_NO_ACTION |
|
SWITCH_SPAN_ISSU-3-BUFFER |
3-Error |
span switch ISSU client failed to get buffer for message error [dec] |
span switch ISSU client failed to get buffer for building a negotiation message. Hence it can send the negotiation message to the standby unit. When there is a problem in the negotiation the standby unit can not be brought up. |
c7600-l2 |
"show logging and show checkpoint client" |
|
SWITCH_SPAN_ISSU-3-CAPABILITY |
3-Error |
span switch ISSU client [chars] |
span switch ISSU client observed an error during capability negotiation. When this error happens there is a mismatch between the client capability between the active and standby unit. |
c7600-l2 |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
SWITCH_SPAN_ISSU-3-INIT |
3-Error |
span switch ISSU client initialization failed at [chars] error [chars] |
span switch ISSU client could not be initiailzed this will cause catastrophic failure when ISSU upgrade or downgrade is performed. |
c7600-l2 |
LOG_STD_SH_TECH_ACTION |
|
SWITCH_SPAN_ISSU-3-MSG_NOT_OK |
3-Error |
span switch ISSU client message [dec] is not compatible |
span switch ISSU client received an incompatible message from the peer unit. Since the message is not compatible it can be processed by this unit |
c7600-l2 |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
SWITCH_SPAN_ISSU-3-MSG_SIZE |
3-Error |
span switch ISSU client failed to get the message size for message [dec] |
span switch ISSU client failed to calculate message size for the message specified. The span switch ISSU client will not be able to send message to the standby unit. |
c7600-l2 |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
SWITCH_SPAN_ISSU-3-POLICY |
3-Error |
span switch ISSU client message type [dec] is [chars] |
span switch ISSU client received an message type which it does not support. The policy is applied to make the session compatible. |
c7600-l2 |
"show issu session <client_id>" |
|
SWITCH_SPAN_ISSU-3-SEND_FAILED |
3-Error |
span switch ISSU client failed to send a negotiation message error [dec] |
span switch ISSU client could not send a session negotiation message to the peer. When there is a problem in the negotiation the standby unit can not be brought up. |
c7600-l2 |
"show logging and show checkpoint client" |
|
SWITCH_SPAN_ISSU-3-SESSION |
3-Error |
span switch ISSU client [chars] |
span switch ISSU client observed an error during a session negotiation with the peer unit. When there is a problem with the session the standby unit can not be brought up. |
c7600-l2 |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated " "capability <session_id>" |
|
SWITCH_SPAN_ISSU-3-TRANSFORM |
3-Error |
span switch ISSU client [chars] transform failed error [chars] |
span switch ISSU client could not transform the message. If the transmit transformation failed it means that the checkpoint message can not be sent to the standby unit. If the receive transformation failed it means that the checkpoint message can not be applied on the standby unit. In both cases the span switch state will not be identical with the active unit. |
c7600-l2 |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
SWPORT_PROXY-2-PROXY_IPC_INIT_FAILED |
2-Critical |
QFP SWPORT Proxy IPC interface initialization failure result: [dec]. |
Cisco internal software error. QFP SWPORT Proxy initialization detected that the IPC interface initialization failed. QFP SWPORT proxy will not be functional while this condition exists. |
qfp-swport keyword:swport |
LOG_STD_ACTION |
|
SWPORT_PROXY-3-PROXY_BAD_MSG |
3-Error |
QFP SWPORT Proxy received bad length message type [dec] |
Cisco internal software error. QFP SWPORT Proxy received a corrupted message from control plane. This message will be ignored. |
qfp-swport keyword:swport |
LOG_STD_ACTION |
|
SWPORT_PROXY-3-PROXY_IPC_ALLOC_FAILED |
3-Error |
QFP SWPORT Proxy [chars] message lost due to message buffer allocation failure. |
Cisco internal software error. QFP SWPORT Proxy message processing detected a message buffer allocation failure. The message is lost as the result of this condition. |
qfp-swport keyword:swport |
LOG_STD_ACTION |
|
SWPORT_PROXY-3-PROXY_IPC_SEND_FAILED |
3-Error |
QFP SWPORT Proxy [chars] message lost due to message sent failure result: [dec]. |
Cisco internal software error. QFP SWPORT Proxy message processing detected a message sent failure. The message is lost as the result of this condition. |
qfp-swport keyword:swport |
LOG_STD_ACTION |
|
SWPORT_PROXY-3-SWPORT_MEM_EXTEND_FAILED |
3-Error |
SWPORT IPC subtype: [dec] |
Extending memory failed. |
qfp-swport keyword:swport |
LOG_STD_ACTION |
|
SWPORT_PROXY-3-SWPORT_MEM_REQ_FAILED |
3-Error |
SWPORT IPC subtype: [dec] |
Requesting more memory failed. |
qfp-swport keyword:swport |
LOG_STD_ACTION |
|
SWPORT_PROXY-4-PROXY_INVALID_MSG |
4-Warning |
QFP SWPORT Proxy received invalid message type [dec] |
Cisco internal software error. QFP SWPORT Proxy received an invalid message from control plane. This message will be ignored. |
qfp-swport keyword:swport |
LOG_STD_ACTION |
|
SWPORT_PROXY-4-PROXY_INVALID_MSG_LEN |
4-Warning |
QFP SWPORT Proxy IPC invalid length [dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Cisco internal software error. QFP SWPORT Proxy received invalid IPC message length from control plane. This message will be ignored. |
qfp-swport keyword:swport |
LOG_STD_ACTION |
|
SWPORT-3-ALLOC_FAILED |
3-Error |
Allocation of [chars] memory failed for SWPORT feature in QFP |
Allocation of memory by the QFP SWPORT feature microcode failed. The name of the memory chunk is specified in the message. This indicates a software failure |
qfp-swport |
LOG_STD_ACTION |
|
SWPORT-3-INIT_FAILED |
3-Error |
Initialization of the SWPORT feature in QFP failed |
Initialization of the SWPORT feature in the QFP failed. This indicates a software failure. |
qfp-swport |
LOG_STD_ACTION |
|
SWPORT-4-MAC_CONFLICT |
4-Warning |
Dynamic mac %04X.%04X.%04X from [chars] conflict with [chars] please check the network topology and make sure there is no loop. |
When eWLC receives a packet whose src MAC in the outer ethernet header \n is eWLC SVI's MAC or is a wireless client's MAC this warning message \n is printed |
qfp-swport |
"In most cases this warning message indicates a L2 loop connection \n" "in the network please check the network topology and make sure \n" "there is no loop" |
|
SYNCE_SPA_INFO-6-NETSYNC_UNCONF_SOURCE |
6-Information |
CLOCK LOCK is [chars] for [chars] interface which is not selected as source to synchronize chassis. |
INFORMATION Message: CLOCK LOCK is Cleared/Asserted for interface which is not configure as a source |
spa-synce-all |
"No further action required. This is source monitor " "INFORMATION message not an error Message." |
|
SYS-0-USERLOG_EMERG |
0-Emergency |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-0-USERLOG_EMERG |
0-Emergency |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-0-USERLOG_EMERG |
0-Emergency |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-0-USERLOG_EMERG |
0-Emergency |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-0-USERLOG_EMERG |
0-Emergency |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-0-USERLOG_EMERG |
0-Emergency |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-1-CCA_SYS_ERR |
1-Alert |
CCA Detected System Error code = [dec] |
CCA has detected a severe system software error. This condition is usually caused by one of the components using CCA or by the interaction among components using CCA. |
os |
LOG_STD_ACTION |
|
SYS-1-CCA_SYS_ERR |
1-Alert |
CCA Detected System Error code = [dec] |
CCA has detected a severe system software error. This condition is usually caused by one of the components using CCA or by the interaction among components using CCA. |
os |
LOG_STD_ACTION |
|
SYS-1-CCA_SYS_ERR |
1-Alert |
CCA Detected System Error code = [dec] |
CCA has detected a severe system software error. This condition is usually caused by one of the components using CCA or by the interaction among components using CCA. |
os |
LOG_STD_ACTION |
|
SYS-1-CCA_SYS_ERR |
1-Alert |
CCA Detected System Error code = [dec] |
CCA has detected a severe system software error. This condition is usually caused by one of the components using CCA or by the interaction among components using CCA. |
os |
LOG_STD_ACTION |
|
SYS-1-CCA_SYS_ERR |
1-Alert |
CCA Detected System Error code = [dec] |
CCA has detected a severe system software error. This condition is usually caused by one of the components using CCA or by the interaction among components using CCA. |
os |
LOG_STD_ACTION |
|
SYS-1-CCA_SYS_ERR |
1-Alert |
CCA Detected System Error code = [dec] |
CCA has detected a severe system software error. This condition is usually caused by one of the components using CCA or by the interaction among components using CCA. |
os |
LOG_STD_ACTION |
|
SYS-1-CPUFALLINGTHRESHOLD |
1-Alert |
Threshold: [chars] CPU UtilizationTotal/Intr [dec]%%/[dec]%%. |
CPU usage has returned to normal after crossing over from a threshold of high usage. Any process that was disabled during the period of high CPU use can now be enabled. |
- |
"No action is required." |
|
SYS-1-CPUFALLINGTHRESHOLD |
1-Alert |
Threshold: [chars] CPU UtilizationTotal/Intr [dec]%%/[dec]%%. |
CPU usage has returned to normal after crossing over from a threshold of high usage. Any process that was disabled during the period of high CPU use can now be enabled. |
- |
"No action is required." |
|
SYS-1-CPUFALLINGTHRESHOLD |
1-Alert |
Threshold: [chars] CPU UtilizationTotal/Intr [dec]%%/[dec]%%. |
CPU usage has returned to normal after crossing over from a threshold of high usage. Any process that was disabled during the period of high CPU use can now be enabled. |
- |
"No action is required." |
|
SYS-1-CPUFALLINGTHRESHOLD |
1-Alert |
Threshold: [chars] CPU UtilizationTotal/Intr [dec]%%/[dec]%%. |
CPU usage has returned to normal after crossing over from a threshold of high usage. Any process that was disabled during the period of high CPU use can now be enabled. |
- |
"No action is required." |
|
SYS-1-CPUFALLINGTHRESHOLD |
1-Alert |
Threshold: [chars] CPU UtilizationTotal/Intr [dec]%%/[dec]%%. |
CPU usage has returned to normal after crossing over from a threshold of high usage. Any process that was disabled during the period of high CPU use can now be enabled. |
- |
"No action is required." |
|
SYS-1-CPUFALLINGTHRESHOLD |
1-Alert |
Threshold: [chars] CPU UtilizationTotal/Intr [dec]%%/[dec]%%. |
CPU usage has returned to normal after crossing over from a threshold of high usage. Any process that was disabled during the period of high CPU use can now be enabled. |
- |
"No action is required." |
|
SYS-1-CPURISINGTHRESHOLD |
1-Alert |
Threshold: [chars] CPU UtilizationTotal/Intr: [dec]%%/[dec]%% |
The system is experiencing high CPU usage possibly from a process that is using too much CPU. This condition demands immediate attention or packets or calls may be dropped. |
- |
"Enter the <CmdBold>show processes CPU<NoCmdBold>" " command to determine the CPU hogging process" " that is causing this condition and if possible" " disable the activity that is causing the" " CPU hog condition so that CPU" " utilization is reduced." |
|
SYS-1-CPURISINGTHRESHOLD |
1-Alert |
Threshold: [chars] CPU UtilizationTotal/Intr: [dec]%%/[dec]%% |
The system is experiencing high CPU usage possibly from a process that is using too much CPU. This condition demands immediate attention or packets or calls may be dropped. |
- |
"Enter the <CmdBold>show processes CPU<NoCmdBold>" " command to determine the CPU hogging process" " that is causing this condition and if possible" " disable the activity that is causing the" " CPU hog condition so that CPU" " utilization is reduced." |
|
SYS-1-CPURISINGTHRESHOLD |
1-Alert |
Threshold: [chars] CPU UtilizationTotal/Intr: [dec]%%/[dec]%% |
The system is experiencing high CPU usage possibly from a process that is using too much CPU. This condition demands immediate attention or packets or calls may be dropped. |
- |
"Enter the <CmdBold>show processes CPU<NoCmdBold>" " command to determine the CPU hogging process" " that is causing this condition and if possible" " disable the activity that is causing the" " CPU hog condition so that CPU" " utilization is reduced." |
|
SYS-1-CPURISINGTHRESHOLD |
1-Alert |
Threshold: [chars] CPU UtilizationTotal/Intr: [dec]%%/[dec]%% |
The system is experiencing high CPU usage possibly from a process that is using too much CPU. This condition demands immediate attention or packets or calls may be dropped. |
- |
"Enter the <CmdBold>show processes CPU<NoCmdBold>" " command to determine the CPU hogging process" " that is causing this condition and if possible" " disable the activity that is causing the" " CPU hog condition so that CPU" " utilization is reduced." |
|
SYS-1-CPURISINGTHRESHOLD |
1-Alert |
Threshold: [chars] CPU UtilizationTotal/Intr: [dec]%%/[dec]%% |
The system is experiencing high CPU usage possibly from a process that is using too much CPU. This condition demands immediate attention or packets or calls may be dropped. |
- |
"Enter the <CmdBold>show processes CPU<NoCmdBold>" " command to determine the CPU hogging process" " that is causing this condition and if possible" " disable the activity that is causing the" " CPU hog condition so that CPU" " utilization is reduced." |
|
SYS-1-CPURISINGTHRESHOLD |
1-Alert |
Threshold: [chars] CPU UtilizationTotal/Intr: [dec]%%/[dec]%% |
The system is experiencing high CPU usage possibly from a process that is using too much CPU. This condition demands immediate attention or packets or calls may be dropped. |
- |
"Enter the <CmdBold>show processes CPU<NoCmdBold>" " command to determine the CPU hogging process" " that is causing this condition and if possible" " disable the activity that is causing the" " CPU hog condition so that CPU" " utilization is reduced." |
|
SYS-1-IPAM_INIT_FAIL |
1-Alert |
IPAM Initialization Failure code = [dec] |
IPAM has detected an initialization failure. This condition is\n\ usually caused by a software error during IPAM initialization. |
ipam |
LOG_STD_ACTION |
|
SYS-1-LOGGING_PER_SPACE_FULL |
1-Alert |
Logging persistent unconfigured as space is full. device-name: [chars] threshold-cap: %lld free: %lld |
Automatically unconfigure logging persistent behaviour when there is no space left on the persistent storage. |
syslog |
"Common Criteria CC v.3.1 certification requirement force to halt " |
|
SYS-1-LOGGING_THRESHOLD_EXCEEDED |
1-Alert |
Logging persistent unconfigured as threshold capacity is exceeded. device-name: [chars] threshold-cap: %lld logging-persistent size: %lld free: %lld |
Automatically unconfigure logging persistent behaviour when threshold capacity is exceeded on the persistent storage. |
syslog |
"Common Criteria CC v.3.1 certification requirement force to halt the" |
|
SYS-1-LOGGING_WRITE_ERR |
1-Alert |
Logging persistent unconfigured as write error occur while writing to the persistent logging file [chars] |
Automatically unconfigure logging persistent behaviour when write error occurs on the persistent storage. |
syslog |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-1-OVERTEMP |
1-Alert |
System detected OVERTEMPERATURE condition.\n Please resolve cooling problem immediately!\n |
The environmental monitor detected a high-temperature condition. |
none |
"Make sure that the room temperature is not too high and that air flow " "to the card is not blocked. If this condition persists the " "environmental monitor might shut down the system. Call your technical " "support representative for assistance if necessary." |
|
SYS-1-OVERTEMP |
1-Alert |
System detected OVERTEMPERATURE condition.\n Please resolve cooling problem immediately!\n |
The environmental monitor detected a high-temperature condition. |
none |
"Make sure that the room temperature is not too high and that air flow " "to the card is not blocked. If this condition persists the " "environmental monitor might shut down the system. Call your technical " "support representative for assistance if necessary." |
|
SYS-1-OVERTEMP |
1-Alert |
System detected OVERTEMPERATURE condition.\n Please resolve cooling problem immediately!\n |
The environmental monitor detected a high-temperature condition. |
none |
"Make sure that the room temperature is not too high and that air flow " "to the card is not blocked. If this condition persists the " "environmental monitor might shut down the system. Call your technical " "support representative for assistance if necessary." |
|
SYS-1-OVERTEMP |
1-Alert |
System detected OVERTEMPERATURE condition.\n Please resolve cooling problem immediately!\n |
The environmental monitor detected a high-temperature condition. |
none |
"Make sure that the room temperature is not too high and that air flow " "to the card is not blocked. If this condition persists the " "environmental monitor might shut down the system. Call your technical " "support representative for assistance if necessary." |
|
SYS-1-OVERTEMP |
1-Alert |
System detected OVERTEMPERATURE condition.\n Please resolve cooling problem immediately!\n |
The environmental monitor detected a high-temperature condition. |
none |
"Make sure that the room temperature is not too high and that air flow " "to the card is not blocked. If this condition persists the " "environmental monitor might shut down the system. Call your technical " "support representative for assistance if necessary." |
|
SYS-1-OVERTEMP |
1-Alert |
System detected OVERTEMPERATURE condition.\n Please resolve cooling problem immediately!\n |
The environmental monitor detected a high-temperature condition. |
none |
"Make sure that the room temperature is not too high and that air flow " "to the card is not blocked. If this condition persists the " "environmental monitor might shut down the system. Call your technical " "support representative for assistance if necessary." |
|
SYS-1-USERLOG_ALERT |
1-Alert |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-1-USERLOG_ALERT |
1-Alert |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-1-USERLOG_ALERT |
1-Alert |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-1-USERLOG_ALERT |
1-Alert |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-1-USERLOG_ALERT |
1-Alert |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-1-USERLOG_ALERT |
1-Alert |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-2-ALREADYFREE |
2-Critical |
Buffer [hec] already in free pool [chars] |
A block of memory at the indicated location is corrupt and/or has been erroneously freed twice. |
os |
"If this message recurs copy it exactly as it appears and the output " "of 'show buffer address <number>' for the given address as well as " "'show buffer pool <name> dump' for the given pool. Report it to your " "technical support representative." |
|
SYS-2-ALREADYFREE |
2-Critical |
Buffer [hec] already in free pool [chars] |
A block of memory at the indicated location is corrupt and/or has been erroneously freed twice. |
os |
"If this message recurs copy it exactly as it appears and the output " "of 'show buffer address <number>' for the given address as well as " "'show buffer pool <name> dump' for the given pool. Report it to your " "technical support representative." |
|
SYS-2-ALREADYFREE |
2-Critical |
Buffer [hec] already in free pool [chars] |
A block of memory at the indicated location is corrupt and/or has been erroneously freed twice. |
os |
"If this message recurs copy it exactly as it appears and the output " "of 'show buffer address <number>' for the given address as well as " "'show buffer pool <name> dump' for the given pool. Report it to your " "technical support representative." |
|
SYS-2-ALREADYFREE |
2-Critical |
Buffer [hec] already in free pool [chars] |
A block of memory at the indicated location is corrupt and/or has been erroneously freed twice. |
os |
"If this message recurs copy it exactly as it appears and the output " "of 'show buffer address <number>' for the given address as well as " "'show buffer pool <name> dump' for the given pool. Report it to your " "technical support representative." |
|
SYS-2-ALREADYFREE |
2-Critical |
Buffer [hec] already in free pool [chars] |
A block of memory at the indicated location is corrupt and/or has been erroneously freed twice. |
os |
"If this message recurs copy it exactly as it appears and the output " "of 'show buffer address <number>' for the given address as well as " "'show buffer pool <name> dump' for the given pool. Report it to your " "technical support representative." |
|
SYS-2-ALREADYFREE |
2-Critical |
Buffer [hec] already in free pool [chars] |
A block of memory at the indicated location is corrupt and/or has been erroneously freed twice. |
os |
"If this message recurs copy it exactly as it appears and the output " "of 'show buffer address <number>' for the given address as well as " "'show buffer pool <name> dump' for the given pool. Report it to your " "technical support representative." |
|
SYS-2-ASSERTION_FAILED |
2-Critical |
Assertion failed: \[chars]\ |
An internal state consistency check failed. Correct operation cannot be guaranteed and the system has been halted. |
- |
LOG_STD_ACTION |
|
SYS-2-ASSERTION_FAILED |
2-Critical |
Assertion failed: \[chars]\ |
An internal state consistency check failed. Correct operation cannot be guaranteed and the system has been halted. |
- |
LOG_STD_ACTION |
|
SYS-2-ASSERTION_FAILED |
2-Critical |
Assertion failed: \[chars]\ |
An internal state consistency check failed. Correct operation cannot be guaranteed and the system has been halted. |
- |
LOG_STD_ACTION |
|
SYS-2-ASSERTION_FAILED |
2-Critical |
Assertion failed: \[chars]\ |
An internal state consistency check failed. Correct operation cannot be guaranteed and the system has been halted. |
- |
LOG_STD_ACTION |
|
SYS-2-ASSERTION_FAILED |
2-Critical |
Assertion failed: \[chars]\ |
An internal state consistency check failed. Correct operation cannot be guaranteed and the system has been halted. |
- |
LOG_STD_ACTION |
|
SYS-2-ASSERTION_FAILED |
2-Critical |
Assertion failed: \[chars]\ |
An internal state consistency check failed. Correct operation cannot be guaranteed and the system has been halted. |
- |
LOG_STD_ACTION |
|
SYS-2-BAD_BM_ARG |
2-Critical |
Invalid BM index boolean used as argument [dec] |
An illegal boolean manager index argument was referenced |
idb |
"Copy the error message exactly as it appears and report it to" " your technical support representative." |
|
SYS-2-BAD_BM_ARG |
2-Critical |
Invalid BM index boolean used as argument [dec] |
An illegal boolean manager index argument was referenced |
idb |
"Copy the error message exactly as it appears and report it to" " your technical support representative." |
|
SYS-2-BAD_BM_ARG |
2-Critical |
Invalid BM index boolean used as argument [dec] |
An illegal boolean manager index argument was referenced |
idb |
"Copy the error message exactly as it appears and report it to" " your technical support representative." |
|
SYS-2-BAD_BM_ARG |
2-Critical |
Invalid BM index boolean used as argument [dec] |
An illegal boolean manager index argument was referenced |
idb |
"Copy the error message exactly as it appears and report it to" " your technical support representative." |
|
SYS-2-BAD_BM_ARG |
2-Critical |
Invalid BM index boolean used as argument [dec] |
An illegal boolean manager index argument was referenced |
idb |
"Copy the error message exactly as it appears and report it to" " your technical support representative." |
|
SYS-2-BAD_BM_ARG |
2-Critical |
Invalid BM index boolean used as argument [dec] |
An illegal boolean manager index argument was referenced |
idb |
"Copy the error message exactly as it appears and report it to" " your technical support representative." |
|
SYS-2-BAD_BM_NAME |
2-Critical |
Invalid BM name |
An illegal name string was registered with the BM |
idb |
"Copy the error message exactly as it appears and report it to" " your technical support representative." |
|
SYS-2-BAD_BM_NAME |
2-Critical |
Invalid BM name |
An illegal name string was registered with the BM |
idb |
"Copy the error message exactly as it appears and report it to" " your technical support representative." |
|
SYS-2-BAD_BM_NAME |
2-Critical |
Invalid BM name |
An illegal name string was registered with the BM |
idb |
"Copy the error message exactly as it appears and report it to" " your technical support representative." |
|
SYS-2-BAD_BM_NAME |
2-Critical |
Invalid BM name |
An illegal name string was registered with the BM |
idb |
"Copy the error message exactly as it appears and report it to" " your technical support representative." |
|
SYS-2-BAD_BM_NAME |
2-Critical |
Invalid BM name |
An illegal name string was registered with the BM |
idb |
"Copy the error message exactly as it appears and report it to" " your technical support representative." |
|
SYS-2-BAD_BM_NAME |
2-Critical |
Invalid BM name |
An illegal name string was registered with the BM |
idb |
"Copy the error message exactly as it appears and report it to" " your technical support representative." |
|
SYS-2-BADALIGNMENT |
2-Critical |
Bad alignment : [dec] |
System requests a alignment which is not a power of 2 |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-BADBUFFER |
2-Critical |
Attempt to use [chars] buffer as [chars] ptr= [hec] pool= [hec] |
A hardware or software error occurred. An inconsistency was encountered while processing a packet buffer. |
- |
"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." |
|
SYS-2-BADBUFFER |
2-Critical |
Attempt to use [chars] buffer as [chars] ptr= [hec] pool= [hec] |
A hardware or software error occurred. An inconsistency was encountered while processing a packet buffer. |
- |
"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." |
|
SYS-2-BADBUFFER |
2-Critical |
Attempt to use [chars] buffer as [chars] ptr= [hec] pool= [hec] |
A hardware or software error occurred. An inconsistency was encountered while processing a packet buffer. |
- |
"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." |
|
SYS-2-BADBUFFER |
2-Critical |
Attempt to use [chars] buffer as [chars] ptr= [hec] pool= [hec] |
A hardware or software error occurred. An inconsistency was encountered while processing a packet buffer. |
- |
"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." |
|
SYS-2-BADBUFFER |
2-Critical |
Attempt to use [chars] buffer as [chars] ptr= [hec] pool= [hec] |
A hardware or software error occurred. An inconsistency was encountered while processing a packet buffer. |
- |
"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." |
|
SYS-2-BADBUFFER |
2-Critical |
Attempt to use [chars] buffer as [chars] ptr= [hec] pool= [hec] |
A hardware or software error occurred. An inconsistency was encountered while processing a packet buffer. |
- |
"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." |
|
SYS-2-BADLIST |
2-Critical |
Regular expression access check with bad list [dec] |
This message indicates that a pointer to an access list is invalid. |
- |
"The event that caused this message to be issued should not " "have occured. It can mean that one or more data structures " "have been overwritten. If this message recurs and you decide " "to report it to your technical representative you should " "copy the text of the message exactly as it appears and " "include the associated stack trace." "\n\n Since access list corruption may have occurred " "a technical representative should verify that access " "lists are functioning corectly." |
|
SYS-2-BADLIST |
2-Critical |
Regular expression access check with bad list [dec] |
This message indicates that a pointer to an access list is invalid. |
- |
"The event that caused this message to be issued should not " "have occured. It can mean that one or more data structures " "have been overwritten. If this message recurs and you decide " "to report it to your technical representative you should " "copy the text of the message exactly as it appears and " "include the associated stack trace." "\n\n Since access list corruption may have occurred " "a technical representative should verify that access " "lists are functioning corectly." |
|
SYS-2-BADLIST |
2-Critical |
Regular expression access check with bad list [dec] |
This message indicates that a pointer to an access list is invalid. |
- |
"The event that caused this message to be issued should not " "have occured. It can mean that one or more data structures " "have been overwritten. If this message recurs and you decide " "to report it to your technical representative you should " "copy the text of the message exactly as it appears and " "include the associated stack trace." "\n\n Since access list corruption may have occurred " "a technical representative should verify that access " "lists are functioning corectly." |
|
SYS-2-BADLIST |
2-Critical |
Regular expression access check with bad list [dec] |
This message indicates that a pointer to an access list is invalid. |
- |
"The event that caused this message to be issued should not " "have occured. It can mean that one or more data structures " "have been overwritten. If this message recurs and you decide " "to report it to your technical representative you should " "copy the text of the message exactly as it appears and " "include the associated stack trace." "\n\n Since access list corruption may have occurred " "a technical representative should verify that access " "lists are functioning corectly." |
|
SYS-2-BADLIST |
2-Critical |
Regular expression access check with bad list [dec] |
This message indicates that a pointer to an access list is invalid. |
- |
"The event that caused this message to be issued should not " "have occured. It can mean that one or more data structures " "have been overwritten. If this message recurs and you decide " "to report it to your technical representative you should " "copy the text of the message exactly as it appears and " "include the associated stack trace." "\n\n Since access list corruption may have occurred " "a technical representative should verify that access " "lists are functioning corectly." |
|
SYS-2-BADLIST |
2-Critical |
Regular expression access check with bad list [dec] |
This message indicates that a pointer to an access list is invalid. |
- |
"The event that caused this message to be issued should not " "have occured. It can mean that one or more data structures " "have been overwritten. If this message recurs and you decide " "to report it to your technical representative you should " "copy the text of the message exactly as it appears and " "include the associated stack trace." "\n\n Since access list corruption may have occurred " "a technical representative should verify that access " "lists are functioning corectly." |
|
SYS-2-BADPID |
2-Critical |
Bad pid [dec] for tty [t-line] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-BADPID |
2-Critical |
Bad pid [dec] for tty [t-line] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-BADPID |
2-Critical |
Bad pid [dec] for tty [t-line] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-BADPID |
2-Critical |
Bad pid [dec] for tty [t-line] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-BADPID |
2-Critical |
Bad pid [dec] for tty [t-line] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-BADPID |
2-Critical |
Bad pid [dec] for tty [t-line] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-BADPOOL |
2-Critical |
Attempt to use buffer with corrupt pool pointer ptr= [hec] pool= [hec] |
An memory management function attempted an operation that could not be performed due to invalid memory pool descriptors. |
- |
- |
|
SYS-2-BADPOOL |
2-Critical |
Attempt to use buffer with corrupt pool pointer ptr= [hec] pool= [hec] |
An memory management function attempted an operation that could not be performed due to invalid memory pool descriptors. |
- |
- |
|
SYS-2-BADPOOL |
2-Critical |
Attempt to use buffer with corrupt pool pointer ptr= [hec] pool= [hec] |
An memory management function attempted an operation that could not be performed due to invalid memory pool descriptors. |
- |
- |
|
SYS-2-BADPOOL |
2-Critical |
Attempt to use buffer with corrupt pool pointer ptr= [hec] pool= [hec] |
An memory management function attempted an operation that could not be performed due to invalid memory pool descriptors. |
- |
- |
|
SYS-2-BADPOOL |
2-Critical |
Attempt to use buffer with corrupt pool pointer ptr= [hec] pool= [hec] |
An memory management function attempted an operation that could not be performed due to invalid memory pool descriptors. |
- |
- |
|
SYS-2-BADPOOL |
2-Critical |
Attempt to use buffer with corrupt pool pointer ptr= [hec] pool= [hec] |
An memory management function attempted an operation that could not be performed due to invalid memory pool descriptors. |
- |
- |
|
SYS-2-BADPOOLMAGIC |
2-Critical |
Attempt to use pool pointer with corrupt header pool= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-BADPOOLMAGIC |
2-Critical |
Attempt to use pool pointer with corrupt header pool= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-BADPOOLMAGIC |
2-Critical |
Attempt to use pool pointer with corrupt header pool= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-BADPOOLMAGIC |
2-Critical |
Attempt to use pool pointer with corrupt header pool= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-BADPOOLMAGIC |
2-Critical |
Attempt to use pool pointer with corrupt header pool= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-BADPOOLMAGIC |
2-Critical |
Attempt to use pool pointer with corrupt header pool= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-BADSHARE |
2-Critical |
Bad refcount in [chars] ptr=[hec] count=[hec] |
A reference count is used to track the usage of many data structures. A function increments the count when it begins to use a structure and decrements it when it finishes. When the count becomes zero the data structure is freed. This message indicates that when the count was accessed it was found to be negative which means that the data structure will not be freed until the system is reloaded. |
- |
- |
|
SYS-2-BADSHARE |
2-Critical |
Bad refcount in [chars] ptr=[hec] count=[hec] |
A reference count is used to track the usage of many data structures. A function increments the count when it begins to use a structure and decrements it when it finishes. When the count becomes zero the data structure is freed. This message indicates that when the count was accessed it was found to be negative which means that the data structure will not be freed until the system is reloaded. |
- |
- |
|
SYS-2-BADSHARE |
2-Critical |
Bad refcount in [chars] ptr=[hec] count=[hec] |
A reference count is used to track the usage of many data structures. A function increments the count when it begins to use a structure and decrements it when it finishes. When the count becomes zero the data structure is freed. This message indicates that when the count was accessed it was found to be negative which means that the data structure will not be freed until the system is reloaded. |
- |
- |
|
SYS-2-BADSHARE |
2-Critical |
Bad refcount in [chars] ptr=[hec] count=[hec] |
A reference count is used to track the usage of many data structures. A function increments the count when it begins to use a structure and decrements it when it finishes. When the count becomes zero the data structure is freed. This message indicates that when the count was accessed it was found to be negative which means that the data structure will not be freed until the system is reloaded. |
- |
- |
|
SYS-2-BADSHARE |
2-Critical |
Bad refcount in [chars] ptr=[hec] count=[hec] |
A reference count is used to track the usage of many data structures. A function increments the count when it begins to use a structure and decrements it when it finishes. When the count becomes zero the data structure is freed. This message indicates that when the count was accessed it was found to be negative which means that the data structure will not be freed until the system is reloaded. |
- |
- |
|
SYS-2-BADSHARE |
2-Critical |
Bad refcount in [chars] ptr=[hec] count=[hec] |
A reference count is used to track the usage of many data structures. A function increments the count when it begins to use a structure and decrements it when it finishes. When the count becomes zero the data structure is freed. This message indicates that when the count was accessed it was found to be negative which means that the data structure will not be freed until the system is reloaded. |
- |
- |
|
SYS-2-BADSTACK |
2-Critical |
Process [chars] has trashed stack old size [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-BADSTACK |
2-Critical |
Process [chars] has trashed stack old size [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-BADSTACK |
2-Critical |
Process [chars] has trashed stack old size [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-BADSTACK |
2-Critical |
Process [chars] has trashed stack old size [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-BADSTACK |
2-Critical |
Process [chars] has trashed stack old size [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-BADSTACK |
2-Critical |
Process [chars] has trashed stack old size [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-BLOCKHUNG |
2-Critical |
Task hung with blocking disabled value = 0x[hec]. |
The indicated process has exceeded the time limit for which it may relinquish control with blocking disabled. |
Determine the component from the stack trace displayed in the error message. Use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. Choose the DDTS component associated with the routine that called the scheduler. |
"This message may be a result of high loads. If it recurs " "copy the text exactly as it appears and report it along " "with the associated stack trace to your technical support " "representative." |
|
SYS-2-BLOCKHUNG |
2-Critical |
Task hung with blocking disabled value = 0x[hec]. |
The indicated process has exceeded the time limit for which it may relinquish control with blocking disabled. |
Determine the component from the stack trace displayed in the error message. Use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. Choose the DDTS component associated with the routine that called the scheduler. |
"This message may be a result of high loads. If it recurs " "copy the text exactly as it appears and report it along " "with the associated stack trace to your technical support " "representative." |
|
SYS-2-BLOCKHUNG |
2-Critical |
Task hung with blocking disabled value = 0x[hec]. |
The indicated process has exceeded the time limit for which it may relinquish control with blocking disabled. |
Determine the component from the stack trace displayed in the error message. Use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. Choose the DDTS component associated with the routine that called the scheduler. |
"This message may be a result of high loads. If it recurs " "copy the text exactly as it appears and report it along " "with the associated stack trace to your technical support " "representative." |
|
SYS-2-BLOCKHUNG |
2-Critical |
Task hung with blocking disabled value = 0x[hec]. |
The indicated process has exceeded the time limit for which it may relinquish control with blocking disabled. |
Determine the component from the stack trace displayed in the error message. Use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. Choose the DDTS component associated with the routine that called the scheduler. |
"This message may be a result of high loads. If it recurs " "copy the text exactly as it appears and report it along " "with the associated stack trace to your technical support " "representative." |
|
SYS-2-BLOCKHUNG |
2-Critical |
Task hung with blocking disabled value = 0x[hec]. |
The indicated process has exceeded the time limit for which it may relinquish control with blocking disabled. |
Determine the component from the stack trace displayed in the error message. Use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. Choose the DDTS component associated with the routine that called the scheduler. |
"This message may be a result of high loads. If it recurs " "copy the text exactly as it appears and report it along " "with the associated stack trace to your technical support " "representative." |
|
SYS-2-BLOCKHUNG |
2-Critical |
Task hung with blocking disabled value = 0x[hec]. |
The indicated process has exceeded the time limit for which it may relinquish control with blocking disabled. |
Determine the component from the stack trace displayed in the error message. Use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. Choose the DDTS component associated with the routine that called the scheduler. |
"This message may be a result of high loads. If it recurs " "copy the text exactly as it appears and report it along " "with the associated stack trace to your technical support " "representative." |
|
SYS-2-CCA_INT_ERR |
2-Critical |
CCA Detected Logic Error code = [dec] |
CCA has detected a severe internal logic error. This condition is usually caused by one of the components using CCA or by the interaction among components using CCA. |
os |
LOG_STD_ACTION |
|
SYS-2-CCA_INT_ERR |
2-Critical |
CCA Detected Logic Error code = [dec] |
CCA has detected a severe internal logic error. This condition is usually caused by one of the components using CCA or by the interaction among components using CCA. |
os |
LOG_STD_ACTION |
|
SYS-2-CCA_INT_ERR |
2-Critical |
CCA Detected Logic Error code = [dec] |
CCA has detected a severe internal logic error. This condition is usually caused by one of the components using CCA or by the interaction among components using CCA. |
os |
LOG_STD_ACTION |
|
SYS-2-CCA_INT_ERR |
2-Critical |
CCA Detected Logic Error code = [dec] |
CCA has detected a severe internal logic error. This condition is usually caused by one of the components using CCA or by the interaction among components using CCA. |
os |
LOG_STD_ACTION |
|
SYS-2-CCA_INT_ERR |
2-Critical |
CCA Detected Logic Error code = [dec] |
CCA has detected a severe internal logic error. This condition is usually caused by one of the components using CCA or by the interaction among components using CCA. |
os |
LOG_STD_ACTION |
|
SYS-2-CCA_INT_ERR |
2-Critical |
CCA Detected Logic Error code = [dec] |
CCA has detected a severe internal logic error. This condition is usually caused by one of the components using CCA or by the interaction among components using CCA. |
os |
LOG_STD_ACTION |
|
SYS-2-CERF_ABORT |
2-Critical |
[chars] |
This message is emitted when a cache error has occured but an attempt to recover has been aborted |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CERF_ABORT |
2-Critical |
[chars] |
This message is emitted when a cache error has occured but an attempt to recover has been aborted |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CERF_ABORT |
2-Critical |
[chars] |
This message is emitted when a cache error has occured but an attempt to recover has been aborted |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CERF_ABORT |
2-Critical |
[chars] |
This message is emitted when a cache error has occured but an attempt to recover has been aborted |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CERF_ABORT |
2-Critical |
[chars] |
This message is emitted when a cache error has occured but an attempt to recover has been aborted |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CERF_ABORT |
2-Critical |
[chars] |
This message is emitted when a cache error has occured but an attempt to recover has been aborted |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CFORKBADFUNCT |
2-Critical |
Can't create process with start address = [hec] |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CFORKBADFUNCT |
2-Critical |
Can't create process with start address = [hec] |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CFORKBADFUNCT |
2-Critical |
Can't create process with start address = [hec] |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CFORKBADFUNCT |
2-Critical |
Can't create process with start address = [hec] |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CFORKBADFUNCT |
2-Critical |
Can't create process with start address = [hec] |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CFORKBADFUNCT |
2-Critical |
Can't create process with start address = [hec] |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CFORKLEV |
2-Critical |
Process creation of [chars] failed at level [dec]. |
An internal software error occurred. |
Determine the component from the process name displayed in the\n\ error message. |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CFORKLEV |
2-Critical |
Process creation of [chars] failed at level [dec]. |
An internal software error occurred. |
Determine the component from the process name displayed in the\n\ error message. |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CFORKLEV |
2-Critical |
Process creation of [chars] failed at level [dec]. |
An internal software error occurred. |
Determine the component from the process name displayed in the\n\ error message. |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CFORKLEV |
2-Critical |
Process creation of [chars] failed at level [dec]. |
An internal software error occurred. |
Determine the component from the process name displayed in the\n\ error message. |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CFORKLEV |
2-Critical |
Process creation of [chars] failed at level [dec]. |
An internal software error occurred. |
Determine the component from the process name displayed in the\n\ error message. |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CFORKLEV |
2-Critical |
Process creation of [chars] failed at level [dec]. |
An internal software error occurred. |
Determine the component from the process name displayed in the\n\ error message. |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CFORKMEM |
2-Critical |
Process creation of [chars] failed no memory. |
Insufficient memory was available to create a process either while trying to support additional features or due to a memory leak. |
mem-suspect |
"A memory leak may be the cause if the system has been running for a " "while without changing its configuration. If you suspect a leak then " "copy this message exactly as it appears and report it to your technical " "support representative. Otherwise ensure that more memory is available " "to support the additional features." |
|
SYS-2-CFORKMEM |
2-Critical |
Process creation of [chars] failed no memory. |
Insufficient memory was available to create a process either while trying to support additional features or due to a memory leak. |
mem-suspect |
"A memory leak may be the cause if the system has been running for a " "while without changing its configuration. If you suspect a leak then " "copy this message exactly as it appears and report it to your technical " "support representative. Otherwise ensure that more memory is available " "to support the additional features." |
|
SYS-2-CFORKMEM |
2-Critical |
Process creation of [chars] failed no memory. |
Insufficient memory was available to create a process either while trying to support additional features or due to a memory leak. |
mem-suspect |
"A memory leak may be the cause if the system has been running for a " "while without changing its configuration. If you suspect a leak then " "copy this message exactly as it appears and report it to your technical " "support representative. Otherwise ensure that more memory is available " "to support the additional features." |
|
SYS-2-CFORKMEM |
2-Critical |
Process creation of [chars] failed no memory. |
Insufficient memory was available to create a process either while trying to support additional features or due to a memory leak. |
mem-suspect |
"A memory leak may be the cause if the system has been running for a " "while without changing its configuration. If you suspect a leak then " "copy this message exactly as it appears and report it to your technical " "support representative. Otherwise ensure that more memory is available " "to support the additional features." |
|
SYS-2-CFORKMEM |
2-Critical |
Process creation of [chars] failed no memory. |
Insufficient memory was available to create a process either while trying to support additional features or due to a memory leak. |
mem-suspect |
"A memory leak may be the cause if the system has been running for a " "while without changing its configuration. If you suspect a leak then " "copy this message exactly as it appears and report it to your technical " "support representative. Otherwise ensure that more memory is available " "to support the additional features." |
|
SYS-2-CFORKMEM |
2-Critical |
Process creation of [chars] failed no memory. |
Insufficient memory was available to create a process either while trying to support additional features or due to a memory leak. |
mem-suspect |
"A memory leak may be the cause if the system has been running for a " "while without changing its configuration. If you suspect a leak then " "copy this message exactly as it appears and report it to your technical " "support representative. Otherwise ensure that more memory is available " "to support the additional features." |
|
SYS-2-CHUNK_FAST |
2-Critical |
Chunk infra detected a system error. Error Type:[chars] Chunk:%p Flags:0x[hec] Name:[chars] |
An internel error has occured in chunk infra which forced a system crash. Contact cisco TAC with the exact error message and 'show tech-support' output. |
mem |
LOG_STD_SH_TECH_ACTION |
|
SYS-2-CHUNKBADELESIZE |
2-Critical |
Chunk element size is zero or more than 64k for [chars]size : %lu |
Chunk manager cannot function properly with big chunk elements |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKBADELESIZE |
2-Critical |
Chunk element size is more than 64k for [chars] |
Chunk manager cannot function properly with big chunk elements |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKBADELESIZE |
2-Critical |
Chunk element size is more than 64k for [chars] |
Chunk manager cannot function properly with big chunk elements |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKBADELESIZE |
2-Critical |
Chunk element size is more than 64k for [chars] |
Chunk manager cannot function properly with big chunk elements |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKBADELESIZE |
2-Critical |
Chunk element size is more than 64k for [chars] |
Chunk manager cannot function properly with big chunk elements |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKBADELESIZE |
2-Critical |
Chunk element size is more than 64k for [chars] |
Chunk manager cannot function properly with big chunk elements |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKBADFREEMAGIC |
2-Critical |
Bad free magic number in chunk header chunk [hec] data [hec] chunk_freemagic [hec] |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBADFREEMAGIC |
2-Critical |
Bad free magic number in chunk header chunk [hec] data [hec] chunk_freemagic [hec] |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBADFREEMAGIC |
2-Critical |
Bad free magic number in chunk header chunk [hec] data [hec] chunk_freemagic [hec] |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBADFREEMAGIC |
2-Critical |
Bad free magic number in chunk header chunk [hec] data [hec] chunk_freemagic [hec] |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBADFREEMAGIC |
2-Critical |
Bad free magic number in chunk header chunk [hec] data [hec] chunk_freemagic [hec] |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBADFREEMAGIC |
2-Critical |
Bad free magic number in chunk header chunk [hec] data [hec] chunk_freemagic [hec] |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBADMAGIC |
2-Critical |
Bad magic number in chunk header chunk [hec] data [hec] chunkmagic [hec] chunk_freemagic [hec] |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBADMAGIC |
2-Critical |
Bad magic number in chunk header chunk [hec] data [hec] chunkmagic [hec] chunk_freemagic [hec] |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBADMAGIC |
2-Critical |
Bad magic number in chunk header chunk [hec] data [hec] chunkmagic [hec] chunk_freemagic [hec] |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBADMAGIC |
2-Critical |
Bad magic number in chunk header chunk [hec] data [hec] chunkmagic [hec] chunk_freemagic [hec] |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBADMAGIC |
2-Critical |
Bad magic number in chunk header chunk [hec] data [hec] chunkmagic [hec] chunk_freemagic [hec] |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBADMAGIC |
2-Critical |
Bad magic number in chunk header chunk [hec] data [hec] chunkmagic [hec] chunk_freemagic [hec] |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBADPOOLSIZE |
2-Critical |
Bad poolsize returned by the system : [dec] |
System returns a non-optimal pool size. Need to change pool sizes |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKBADPOOLSIZE |
2-Critical |
Bad poolsize returned by the system : [dec] |
System returns a non-optimal pool size. Need to change pool sizes |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKBADPOOLSIZE |
2-Critical |
Bad poolsize returned by the system : [dec] |
System returns a non-optimal pool size. Need to change pool sizes |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKBADPOOLSIZE |
2-Critical |
Bad poolsize returned by the system : [dec] |
System returns a non-optimal pool size. Need to change pool sizes |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKBADPOOLSIZE |
2-Critical |
Bad poolsize returned by the system : [dec] |
System returns a non-optimal pool size. Need to change pool sizes |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKBADPOOLSIZE |
2-Critical |
Bad poolsize returned by the system : [dec] |
System returns a non-optimal pool size. Need to change pool sizes |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKBADREFCOUNT |
2-Critical |
Bad chunk reference count chunk [hec] data [hec] refcount [hec] alloc pc [hec]. |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBADREFCOUNT |
2-Critical |
Bad chunk reference count chunk [hec] data [hec] refcount [hec] alloc pc [hec]. |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBADREFCOUNT |
2-Critical |
Bad chunk reference count chunk [hec] data [hec] refcount [hec] alloc pc [hec]. |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBADREFCOUNT |
2-Critical |
Bad chunk reference count chunk [hec] data [hec] refcount [hec] alloc pc [hec]. |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBADREFCOUNT |
2-Critical |
Bad chunk reference count chunk [hec] data [hec] refcount [hec] alloc pc [hec]. |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBADREFCOUNT |
2-Critical |
Bad chunk reference count chunk [hec] data [hec] refcount [hec] alloc pc [hec]. |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBADROOTCHUNKPTR |
2-Critical |
Bad root chunk pointer in chunk header chunk 0x[hec] data 0x[hec] root chunk ptr 0x[hec] |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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 along " "with the ouput of the <CmdBold>show running-config<NoCmdBold> and " "<CmdBold>show tech-support<NoCmdBold> commands. " "Save any crashinfo or crashdump files. " "If the router has crashed and was not configured to reload " "automatically the router will need to be reloaded manually." |
|
SYS-2-CHUNKBOUNDS |
2-Critical |
Could not find the sibling to allocate memory from. Chunk [chars] total free [dec] inuse [dec]. |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBOUNDS |
2-Critical |
Could not find the sibling to allocate memory from. Chunk [chars] total free [dec] inuse [dec]. |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBOUNDS |
2-Critical |
Could not find the sibling to allocate memory from. Chunk [chars] total free [dec] inuse [dec]. |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBOUNDS |
2-Critical |
Could not find the sibling to allocate memory from. Chunk [chars] total free [dec] inuse [dec]. |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBOUNDS |
2-Critical |
Could not find the sibling to allocate memory from. Chunk [chars] total free [dec] inuse [dec]. |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBOUNDS |
2-Critical |
Could not find the sibling to allocate memory from. Chunk [chars] total free [dec] inuse [dec]. |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKBOUNDSIB |
2-Critical |
Error noticed in the sibling of the chunk 0x[hec] head_chunk 0x[hec] chunk name [chars] data 0x[hec] Chunk index : [dec] Chunk real max : [dec] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CHUNKBOUNDSIB |
2-Critical |
Error noticed in the sibling of the chunk [chars] Chunk index : [dec] Chunk real max : [dec] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CHUNKBOUNDSIB |
2-Critical |
Error noticed in the sibling of the chunk [chars] Chunk index : [dec] Chunk real max : [dec] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CHUNKBOUNDSIB |
2-Critical |
Error noticed in the sibling of the chunk [chars] Chunk index : [dec] Chunk real max : [dec] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CHUNKBOUNDSIB |
2-Critical |
Error noticed in the sibling of the chunk [chars] Chunk index : [dec] Chunk real max : [dec] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CHUNKBOUNDSIB |
2-Critical |
Error noticed in the sibling of the chunk [chars] Chunk index : [dec] Chunk real max : [dec] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CHUNKDELAYSIB |
2-Critical |
Error noticed in freeing up of delayed siblings for chunk [chars] 0x[hec]. Delayed sibling free queue size : [dec] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SYS-2-CHUNKDOUBLEFREE |
2-Critical |
Attempt to free a free chunk element. Chunk : %lx Head Chunk : %lx Chunk Name : [chars] Data : %lx Alloc : %lx Dealloc : %lx |
An attempt was made to free a chunk element which is already free. |
- |
- |
|
SYS-2-CHUNKEXPANDFAIL |
2-Critical |
Could not expand chunk pool for [chars]. No memory available |
There is not enough processor memory left to grow this chunk pool. |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKEXPANDFAIL |
2-Critical |
Could not expand chunk pool for [chars]. No memory available |
There is not enough processor memory left to grow this chunk pool. |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKEXPANDFAIL |
2-Critical |
Could not expand chunk pool for [chars]. No memory available |
There is not enough processor memory left to grow this chunk pool. |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKEXPANDFAIL |
2-Critical |
Could not expand chunk pool for [chars]. No memory available |
There is not enough processor memory left to grow this chunk pool. |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKEXPANDFAIL |
2-Critical |
Could not expand chunk pool for [chars]. No memory available |
There is not enough processor memory left to grow this chunk pool. |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKEXPANDFAIL |
2-Critical |
Could not expand chunk pool for [chars]. No memory available |
There is not enough processor memory left to grow this chunk pool. |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKFREE |
2-Critical |
Attempted to free nonchunk memory chunk [hec] data [hec]. |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKFREE |
2-Critical |
Attempted to free nonchunk memory chunk [hec] data [hec]. |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKFREE |
2-Critical |
Attempted to free nonchunk memory chunk [hec] data [hec]. |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKFREE |
2-Critical |
Attempted to free nonchunk memory chunk [hec] data [hec]. |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKFREE |
2-Critical |
Attempted to free nonchunk memory chunk [hec] data [hec]. |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKFREE |
2-Critical |
Attempted to free nonchunk memory chunk [hec] data [hec]. |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKINCONSIS |
2-Critical |
Inconsistant counters for chunk : [chars] total free [dec]/[dec] total sibs [dec]/[dec] total alloc [dec]/[dec] |
System returns a non-optimal pool size. Need to change pool sizes |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKINCONSIS |
2-Critical |
Inconsistant counters for chunk : [chars] total free [dec]/[dec] total sibs [dec]/[dec] total alloc [dec]/[dec] |
System returns a non-optimal pool size. Need to change pool sizes |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKINCONSIS |
2-Critical |
Inconsistant counters for chunk : [chars] total free [dec]/[dec] total sibs [dec]/[dec] total alloc [dec]/[dec] |
System returns a non-optimal pool size. Need to change pool sizes |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKINCONSIS |
2-Critical |
Inconsistant counters for chunk : [chars] total free [dec]/[dec] total sibs [dec]/[dec] total alloc [dec]/[dec] |
System returns a non-optimal pool size. Need to change pool sizes |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKINCONSIS |
2-Critical |
Inconsistant counters for chunk : [chars] total free [dec]/[dec] total sibs [dec]/[dec] total alloc [dec]/[dec] |
System returns a non-optimal pool size. Need to change pool sizes |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKINCONSIS |
2-Critical |
Inconsistant counters for chunk : [chars] total free [dec]/[dec] total sibs [dec]/[dec] total alloc [dec]/[dec] |
System returns a non-optimal pool size. Need to change pool sizes |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKINVALIDHDR |
2-Critical |
Invalid chunk header type [dec] for chunk [hec] data [hec] |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKINVALIDHDR |
2-Critical |
Invalid chunk header type [dec] for chunk [hec] data [hec] |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKINVALIDHDR |
2-Critical |
Invalid chunk header type [dec] for chunk [hec] data [hec] |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKINVALIDHDR |
2-Critical |
Invalid chunk header type [dec] for chunk [hec] data [hec] |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKINVALIDHDR |
2-Critical |
Invalid chunk header type [dec] for chunk [hec] data [hec] |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKINVALIDHDR |
2-Critical |
Invalid chunk header type [dec] for chunk [hec] data [hec] |
An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent but there could be a hardware problem with memory. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-CHUNKINVALIDOPR |
2-Critical |
[chars] Chunk : %lx Chunk Name : [chars] Flags : %lu |
An operation intended for a type of chunk is used for a different type of chunk. |
- |
- |
|
SYS-2-CHUNKNOMEMORY |
2-Critical |
* Could not allocate chunks for [chars]. No memory |
* A software error occurred. |
- |
* "Copy the error message exactly as it appears and report it to " * "your technical support representative." |
|
SYS-2-CHUNKNOMEMORY |
2-Critical |
* Could not allocate chunks for [chars]. No memory |
* A software error occurred. |
- |
* "Copy the error message exactly as it appears and report it to " * "your technical support representative." |
|
SYS-2-CHUNKNOMEMORY |
2-Critical |
* Could not allocate chunks for [chars]. No memory |
* A software error occurred. |
- |
* "Copy the error message exactly as it appears and report it to " * "your technical support representative." |
|
SYS-2-CHUNKNOMEMORY |
2-Critical |
* Could not allocate chunks for [chars]. No memory |
* A software error occurred. |
- |
* "Copy the error message exactly as it appears and report it to " * "your technical support representative." |
|
SYS-2-CHUNKNOMEMORY |
2-Critical |
* Could not allocate chunks for [chars]. No memory |
* A software error occurred. |
- |
* "Copy the error message exactly as it appears and report it to " * "your technical support representative." |
|
SYS-2-CHUNKNOMEMORY |
2-Critical |
* Could not allocate chunks for [chars]. No memory |
* A software error occurred. |
- |
* "Copy the error message exactly as it appears and report it to " * "your technical support representative." |
|
SYS-2-CHUNKNOROOT |
2-Critical |
Root chunk need to be specified for [hec] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKNOROOT |
2-Critical |
Root chunk need to be specified for [hec] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKNOROOT |
2-Critical |
Root chunk need to be specified for [hec] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKNOROOT |
2-Critical |
Root chunk need to be specified for [hec] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKNOROOT |
2-Critical |
Root chunk need to be specified for [hec] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKNOROOT |
2-Critical |
Root chunk need to be specified for [hec] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-CHUNKPARTIAL |
2-Critical |
Attempted to destroy partially full chunk chunk [hec]. |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CHUNKPARTIAL |
2-Critical |
Attempted to destroy partially full chunk chunk 0x[hec] chunk name: \[chars]\. |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CHUNKPARTIAL |
2-Critical |
Attempted to destroy partially full chunk chunk 0x[hec] chunk name: \[chars]\. |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CHUNKPARTIAL |
2-Critical |
Attempted to destroy partially full chunk chunk 0x[hec] chunk name: \[chars]\. |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CHUNKPARTIAL |
2-Critical |
Attempted to destroy partially full chunk chunk 0x[hec] chunk name: \[chars]\. |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CHUNKPARTIAL |
2-Critical |
Attempted to destroy partially full chunk chunk 0x[hec] chunk name: \[chars]\. |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CHUNKSIBLINGDEST |
2-Critical |
Attempted to destroy a sibling chunk [hec] [chars]. |
- |
- |
- |
|
SYS-2-CHUNKSIBLINGDEST |
2-Critical |
Attempted to destroy a sibling chunk [hec] [chars]. |
- |
- |
- |
|
SYS-2-CHUNKSIBLINGDEST |
2-Critical |
Attempted to destroy a sibling chunk [hec] [chars]. |
- |
- |
- |
|
SYS-2-CHUNKSIBLINGDEST |
2-Critical |
Attempted to destroy a sibling chunk [hec] [chars]. |
- |
- |
- |
|
SYS-2-CHUNKSIBLINGDEST |
2-Critical |
Attempted to destroy a sibling chunk [hec] [chars]. |
- |
- |
- |
|
SYS-2-CHUNKSIBLINGDEST |
2-Critical |
Attempted to destroy a sibling chunk [hec] [chars]. |
- |
- |
- |
|
SYS-2-CHUNKSIBLINGS |
2-Critical |
Attempted to destroy chunk with siblings chunk [hec]. |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CHUNKSIBLINGS |
2-Critical |
Attempted to destroy chunk with siblings chunk [hec]. |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CHUNKSIBLINGS |
2-Critical |
Attempted to destroy chunk with siblings chunk [hec]. |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CHUNKSIBLINGS |
2-Critical |
Attempted to destroy chunk with siblings chunk [hec]. |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CHUNKSIBLINGS |
2-Critical |
Attempted to destroy chunk with siblings chunk [hec]. |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CHUNKSIBLINGS |
2-Critical |
Attempted to destroy chunk with siblings chunk [hec]. |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-CONFIG_DOWNFAIL |
2-Critical |
Generated configuration not backward compatible |
The router has been configured to generate nonvolatile memory using the commands of an older software version. The current configuration of the router contains a command that cannot be saved using only the older command set. |
none |
"Allow the router to save the configuration using the command set of " "the current software version or remove the commands that cannot be " "saved using the older command set." |
|
SYS-2-CONFIG_DOWNFAIL |
2-Critical |
Generated configuration not backward compatible |
The router has been configured to generate nonvolatile memory using the commands of an older software version. The current configuration of the router contains a command that cannot be saved using only the older command set. |
none |
"Allow the router to save the configuration using the command set of " "the current software version or remove the commands that cannot be " "saved using the older command set." |
|
SYS-2-CONFIG_DOWNFAIL |
2-Critical |
Generated configuration not backward compatible |
The router has been configured to generate nonvolatile memory using the commands of an older software version. The current configuration of the router contains a command that cannot be saved using only the older command set. |
none |
"Allow the router to save the configuration using the command set of " "the current software version or remove the commands that cannot be " "saved using the older command set." |
|
SYS-2-CONFIG_DOWNFAIL |
2-Critical |
Generated configuration not backward compatible |
The router has been configured to generate nonvolatile memory using the commands of an older software version. The current configuration of the router contains a command that cannot be saved using only the older command set. |
none |
"Allow the router to save the configuration using the command set of " "the current software version or remove the commands that cannot be " "saved using the older command set." |
|
SYS-2-CONFIG_DOWNFAIL |
2-Critical |
Generated configuration not backward compatible |
The router has been configured to generate nonvolatile memory using the commands of an older software version. The current configuration of the router contains a command that cannot be saved using only the older command set. |
none |
"Allow the router to save the configuration using the command set of " "the current software version or remove the commands that cannot be " "saved using the older command set." |
|
SYS-2-CONFIG_DOWNFAIL |
2-Critical |
Generated configuration not backward compatible |
The router has been configured to generate nonvolatile memory using the commands of an older software version. The current configuration of the router contains a command that cannot be saved using only the older command set. |
none |
"Allow the router to save the configuration using the command set of " "the current software version or remove the commands that cannot be " "saved using the older command set." |
|
SYS-2-CZIP_ERROR |
2-Critical |
Error: [chars] |
A software Error occurred while decompressing the Image. The actual error is within the string of the error message. |
os |
LOG_STD_SH_TECH_ACTION |
|
SYS-2-EXCEPTIONDUMP |
2-Critical |
System Crashed Writing Core.... |
The system has crashed because of an exception A core is being generated |
- |
LOG_STD_ACTION |
|
SYS-2-EXCEPTIONDUMP |
2-Critical |
System Crashed Writing Core.... |
The system has crashed because of an exception A core is being generated |
- |
LOG_STD_ACTION |
|
SYS-2-EXCEPTIONDUMP |
2-Critical |
System Crashed Writing Core.... |
The system has crashed because of an exception A core is being generated |
- |
LOG_STD_ACTION |
|
SYS-2-EXCEPTIONDUMP |
2-Critical |
System Crashed Writing Core.... |
The system has crashed because of an exception A core is being generated |
- |
LOG_STD_ACTION |
|
SYS-2-EXCEPTIONDUMP |
2-Critical |
System Crashed Writing Core.... |
The system has crashed because of an exception A core is being generated |
- |
LOG_STD_ACTION |
|
SYS-2-EXCEPTIONDUMP |
2-Critical |
System Crashed Writing Core.... |
The system has crashed because of an exception A core is being generated |
- |
LOG_STD_ACTION |
|
SYS-2-EXMEMFREE |
2-Critical |
Free a non allocated ptr [hec] size [dec]. |
Trying to free a memory which not all of it marked as allocated. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-EXMEMFREE |
2-Critical |
Free a non allocated ptr [hec] size [dec]. |
Trying to free a memory which not all of it marked as allocated. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-EXMEMFREE |
2-Critical |
Free a non allocated ptr [hec] size [dec]. |
Trying to free a memory which not all of it marked as allocated. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-EXMEMFREE |
2-Critical |
Free a non allocated ptr [hec] size [dec]. |
Trying to free a memory which not all of it marked as allocated. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-EXMEMFREE |
2-Critical |
Free a non allocated ptr [hec] size [dec]. |
Trying to free a memory which not all of it marked as allocated. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-EXMEMFREE |
2-Critical |
Free a non allocated ptr [hec] size [dec]. |
Trying to free a memory which not all of it marked as allocated. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-EXMEMINIT |
2-Critical |
EXMEM [dec]: [chars] |
The requested external memory allocator failed to be initialized. reasons are not clear. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-EXMEMINIT |
2-Critical |
EXMEM [dec]: [chars] |
The requested external memory allocator failed to be initialized. reasons are not clear. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-EXMEMINIT |
2-Critical |
EXMEM [dec]: [chars] |
The requested external memory allocator failed to be initialized. reasons are not clear. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-EXMEMINIT |
2-Critical |
EXMEM [dec]: [chars] |
The requested external memory allocator failed to be initialized. reasons are not clear. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-EXMEMINIT |
2-Critical |
EXMEM [dec]: [chars] |
The requested external memory allocator failed to be initialized. reasons are not clear. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-EXMEMPARAM |
2-Critical |
Bad parameter [dec] when calling to the allocator utility |
Illegal parameter is used when called to allocator. may represent data some corruption. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-EXMEMPARAM |
2-Critical |
Bad parameter [dec] when calling to the allocator utility |
Illegal parameter is used when called to allocator. may represent data some corruption. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-EXMEMPARAM |
2-Critical |
Bad parameter [dec] when calling to the allocator utility |
Illegal parameter is used when called to allocator. may represent data some corruption. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-EXMEMPARAM |
2-Critical |
Bad parameter [dec] when calling to the allocator utility |
Illegal parameter is used when called to allocator. may represent data some corruption. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-EXMEMPARAM |
2-Critical |
Bad parameter [dec] when calling to the allocator utility |
Illegal parameter is used when called to allocator. may represent data some corruption. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-EXMEMPARAM |
2-Critical |
Bad parameter [dec] when calling to the allocator utility |
Illegal parameter is used when called to allocator. may represent data some corruption. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-FREEBAD |
2-Critical |
Attempted to free memory at [hec] not part of buffer pool |
An attempt was made to free memory but the request could not be completed due to an invalid memory data structure |
- |
- |
|
SYS-2-FREEBAD |
2-Critical |
Attempted to free memory at [hec] not part of buffer pool |
An attempt was made to free memory but the request could not be completed due to an invalid memory data structure |
- |
- |
|
SYS-2-FREEBAD |
2-Critical |
Attempted to free memory at [hec] not part of buffer pool |
An attempt was made to free memory but the request could not be completed due to an invalid memory data structure |
- |
- |
|
SYS-2-FREEBAD |
2-Critical |
Attempted to free memory at [hec] not part of buffer pool |
An attempt was made to free memory but the request could not be completed due to an invalid memory data structure |
- |
- |
|
SYS-2-FREEBAD |
2-Critical |
Attempted to free memory at [hec] not part of buffer pool |
An attempt was made to free memory but the request could not be completed due to an invalid memory data structure |
- |
- |
|
SYS-2-FREEBAD |
2-Critical |
Attempted to free memory at [hec] not part of buffer pool |
An attempt was made to free memory but the request could not be completed due to an invalid memory data structure |
- |
- |
|
SYS-2-FREEFREE |
2-Critical |
Attempted to free unassigned memory at %lx alloc %lx dealloc %lx |
An attempt was made to free memory at the indicated location. The memory could not be freed because it was not allocated. |
- |
- |
|
SYS-2-FREEFREE |
2-Critical |
Attempted to free unassigned memory at %lx alloc %lx dealloc %lx |
An attempt was made to free memory at the indicated location. The memory could not be freed because it was not allocated. |
- |
- |
|
SYS-2-FREEFREE |
2-Critical |
Attempted to free unassigned memory at %lx alloc %lx dealloc %lx |
An attempt was made to free memory at the indicated location. The memory could not be freed because it was not allocated. |
- |
- |
|
SYS-2-FREEFREE |
2-Critical |
Attempted to free unassigned memory at %lx alloc %lx dealloc %lx |
An attempt was made to free memory at the indicated location. The memory could not be freed because it was not allocated. |
- |
- |
|
SYS-2-FREEFREE |
2-Critical |
Attempted to free unassigned memory at %lx alloc %lx dealloc %lx |
An attempt was made to free memory at the indicated location. The memory could not be freed because it was not allocated. |
- |
- |
|
SYS-2-FREEFREE |
2-Critical |
Attempted to free unassigned memory at %lx alloc %lx dealloc %lx |
An attempt was made to free memory at the indicated location. The memory could not be freed because it was not allocated. |
- |
- |
|
SYS-2-GETBUF |
2-Critical |
Bad getbuffer bytes= [dec] |
The software requested a buffer that is larger than the largest configured buffer size or it requested a negative-sized buffer. |
Determine the component from the stack trace and process name displayed in the error message. \n\nUse Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. If the stack trace indicates that the buffer code was called from an interrupt handler use the interrupt handler to determine the DDTS component. Otherwise use the process name to determine the DDTS component. |
- |
|
SYS-2-GETBUF |
2-Critical |
Bad getbuffer bytes= [dec] |
The software requested a buffer that is larger than the largest configured buffer size or it requested a negative-sized buffer. |
Determine the component from the stack trace and process name displayed in the error message. \n\nUse Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. If the stack trace indicates that the buffer code was called from an interrupt handler use the interrupt handler to determine the DDTS component. Otherwise use the process name to determine the DDTS component. |
- |
|
SYS-2-GETBUF |
2-Critical |
Bad getbuffer bytes= [dec] |
The software requested a buffer that is larger than the largest configured buffer size or it requested a negative-sized buffer. |
Determine the component from the stack trace and process name displayed in the error message. \n\nUse Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. If the stack trace indicates that the buffer code was called from an interrupt handler use the interrupt handler to determine the DDTS component. Otherwise use the process name to determine the DDTS component. |
- |
|
SYS-2-GETBUF |
2-Critical |
Bad getbuffer bytes= [dec] |
The software requested a buffer that is larger than the largest configured buffer size or it requested a negative-sized buffer. |
Determine the component from the stack trace and process name displayed in the error message. \n\nUse Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. If the stack trace indicates that the buffer code was called from an interrupt handler use the interrupt handler to determine the DDTS component. Otherwise use the process name to determine the DDTS component. |
- |
|
SYS-2-GETBUF |
2-Critical |
Bad getbuffer bytes= [dec] |
The software requested a buffer that is larger than the largest configured buffer size or it requested a negative-sized buffer. |
Determine the component from the stack trace and process name displayed in the error message. \n\nUse Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. If the stack trace indicates that the buffer code was called from an interrupt handler use the interrupt handler to determine the DDTS component. Otherwise use the process name to determine the DDTS component. |
- |
|
SYS-2-GETBUF |
2-Critical |
Bad getbuffer bytes= [dec] |
The software requested a buffer that is larger than the largest configured buffer size or it requested a negative-sized buffer. |
Determine the component from the stack trace and process name displayed in the error message. \n\nUse Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. If the stack trace indicates that the buffer code was called from an interrupt handler use the interrupt handler to determine the DDTS component. Otherwise use the process name to determine the DDTS component. |
- |
|
SYS-2-GETBUFFFAIL |
2-Critical |
[chars] buffer allocation [dec] bytes failed from [hex] |
- |
- |
- |
|
SYS-2-GETBUFFFAIL |
2-Critical |
[chars] buffer allocation [dec] bytes failed from [hex] |
- |
- |
- |
|
SYS-2-GETBUFFFAIL |
2-Critical |
[chars] buffer allocation [dec] bytes failed from [hex] |
- |
- |
- |
|
SYS-2-GETBUFFFAIL |
2-Critical |
[chars] buffer allocation [dec] bytes failed from [hex] |
- |
- |
- |
|
SYS-2-GETBUFFFAIL |
2-Critical |
[chars] buffer allocation [dec] bytes failed from [hex] |
- |
- |
- |
|
SYS-2-GETBUFFFAIL |
2-Critical |
[chars] buffer allocation [dec] bytes failed from [hex] |
- |
- |
- |
|
SYS-2-IMMORTAL |
2-Critical |
Attempt to shut down management process [dec] [chars]. |
An attempt was made to shut down the specified management\n\ process. Management processes must not be shut down as long as the\n\ router remains up. |
Determine the component from the stack trace displayed in the error message. Use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. Choose the DDTS component associated with the routine that called the process_kill. |
- |
|
SYS-2-IMMORTAL |
2-Critical |
Attempt to shut down management process [dec] [chars]. |
An attempt was made to shut down the specified management process. Management processes must not be shut down as long as the\n\ router remains up. |
Determine the component from the stack trace displayed in the error message. Use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. Choose the DDTS component associated with the routine that called the process_kill. |
- |
|
SYS-2-IMMORTAL |
2-Critical |
Attempt to shut down management process [dec] [chars]. |
An attempt was made to shut down the specified management process. Management processes must not be shut down as long as the\n\ router remains up. |
Determine the component from the stack trace displayed in the error message. Use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. Choose the DDTS component associated with the routine that called the process_kill. |
- |
|
SYS-2-IMMORTAL |
2-Critical |
Attempt to shut down management process [dec] [chars]. |
An attempt was made to shut down the specified management process. Management processes must not be shut down as long as the\n\ router remains up. |
Determine the component from the stack trace displayed in the error message. Use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. Choose the DDTS component associated with the routine that called the process_kill. |
- |
|
SYS-2-IMMORTAL |
2-Critical |
Attempt to shut down management process [dec] [chars]. |
An attempt was made to shut down the specified management process. Management processes must not be shut down as long as the\n\ router remains up. |
Determine the component from the stack trace displayed in the error message. Use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. Choose the DDTS component associated with the routine that called the process_kill. |
- |
|
SYS-2-IMMORTAL |
2-Critical |
Attempt to shut down management process [dec] [chars]. |
An attempt was made to shut down the specified management process. Management processes must not be shut down as long as the\n\ router remains up. |
Determine the component from the stack trace displayed in the error message. Use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. Choose the DDTS component associated with the routine that called the process_kill. |
- |
|
SYS-2-INLIST |
2-Critical |
Buffer in list ptr= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-INLIST |
2-Critical |
Buffer in list ptr= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-INLIST |
2-Critical |
Buffer in list ptr= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-INLIST |
2-Critical |
Buffer in list ptr= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-INLIST |
2-Critical |
Buffer in list ptr= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-INLIST |
2-Critical |
Buffer in list ptr= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-INLIST1 |
2-Critical |
Buffer in list ptr= [hec] caller= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-INLIST1 |
2-Critical |
Buffer in list ptr= [hec] caller= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-INLIST1 |
2-Critical |
Buffer in list ptr= [hec] caller= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-INLIST1 |
2-Critical |
Buffer in list ptr= [hec] caller= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-INLIST1 |
2-Critical |
Buffer in list ptr= [hec] caller= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-INLIST1 |
2-Critical |
Buffer in list ptr= [hec] caller= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-INPUT_GETBUF |
2-Critical |
Bad getbuffer bytes= [dec] for interface= [chars] |
The software requested a buffer that is larger than the largest configured buffer size or it requested a negative-sized buffer. |
Determine the component from the stack trace and process name displayed in the error message. \n\nUse Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. If the stack trace indicates that the buffer code was called from an interrupt handler use the interrupt handler to determine the DDTS component. Otherwise use the process name to determine the DDTS component. |
LOG_STD_ACTION |
|
SYS-2-INPUT_GETBUF |
2-Critical |
Bad getbuffer bytes= [dec] for interface= [chars] |
The software requested a buffer that is larger than the largest configured buffer size or it requested a negative-sized buffer. |
Determine the component from the stack trace and process name displayed in the error message. \n\nUse Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. If the stack trace indicates that the buffer code was called from an interrupt handler use the interrupt handler to determine the DDTS component. Otherwise use the process name to determine the DDTS component. |
LOG_STD_ACTION |
|
SYS-2-INPUT_GETBUF |
2-Critical |
Bad getbuffer bytes= [dec] for interface= [chars] |
The software requested a buffer that is larger than the largest configured buffer size or it requested a negative-sized buffer. |
Determine the component from the stack trace and process name displayed in the error message. \n\nUse Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. If the stack trace indicates that the buffer code was called from an interrupt handler use the interrupt handler to determine the DDTS component. Otherwise use the process name to determine the DDTS component. |
LOG_STD_ACTION |
|
SYS-2-INPUT_GETBUF |
2-Critical |
Bad getbuffer bytes= [dec] for interface= [chars] |
The software requested a buffer that is larger than the largest configured buffer size or it requested a negative-sized buffer. |
Determine the component from the stack trace and process name displayed in the error message. \n\nUse Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. If the stack trace indicates that the buffer code was called from an interrupt handler use the interrupt handler to determine the DDTS component. Otherwise use the process name to determine the DDTS component. |
LOG_STD_ACTION |
|
SYS-2-INPUT_GETBUF |
2-Critical |
Bad getbuffer bytes= [dec] for interface= [chars] |
The software requested a buffer that is larger than the largest configured buffer size or it requested a negative-sized buffer. |
Determine the component from the stack trace and process name displayed in the error message. \n\nUse Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. If the stack trace indicates that the buffer code was called from an interrupt handler use the interrupt handler to determine the DDTS component. Otherwise use the process name to determine the DDTS component. |
LOG_STD_ACTION |
|
SYS-2-INPUT_GETBUF |
2-Critical |
Bad getbuffer bytes= [dec] for interface= [chars] |
The software requested a buffer that is larger than the largest configured buffer size or it requested a negative-sized buffer. |
Determine the component from the stack trace and process name displayed in the error message. \n\nUse Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. If the stack trace indicates that the buffer code was called from an interrupt handler use the interrupt handler to determine the DDTS component. Otherwise use the process name to determine the DDTS component. |
LOG_STD_ACTION |
|
SYS-2-INPUTQ |
2-Critical |
INPUTQ set but no IDB ptr=[hec] |
This message is issued when an attempt is made to alter the input queue count for a packet that should not be counted. |
- |
- |
|
SYS-2-INPUTQ |
2-Critical |
INPUTQ set but no IDB ptr=[hec] |
This message is issued when an attempt is made to alter the input queue count for a packet that should not be counted. |
- |
- |
|
SYS-2-INPUTQ |
2-Critical |
INPUTQ set but no IDB ptr=[hec] |
This message is issued when an attempt is made to alter the input queue count for a packet that should not be counted. |
- |
- |
|
SYS-2-INPUTQ |
2-Critical |
INPUTQ set but no IDB ptr=[hec] |
This message is issued when an attempt is made to alter the input queue count for a packet that should not be counted. |
- |
- |
|
SYS-2-INPUTQ |
2-Critical |
INPUTQ set but no IDB ptr=[hec] |
This message is issued when an attempt is made to alter the input queue count for a packet that should not be counted. |
- |
- |
|
SYS-2-INPUTQ |
2-Critical |
INPUTQ set but no IDB ptr=[hec] |
This message is issued when an attempt is made to alter the input queue count for a packet that should not be counted. |
- |
- |
|
SYS-2-INSCHED |
2-Critical |
[chars] within scheduler |
- |
Determine the component from the stack trace displayed in the error message. Then use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. |
- |
|
SYS-2-INSCHED |
2-Critical |
[chars] within scheduler |
- |
Determine the component from the stack trace displayed in the error message. Then use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. |
- |
|
SYS-2-INSCHED |
2-Critical |
[chars] within scheduler |
- |
Determine the component from the stack trace displayed in the error message. Then use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. |
- |
|
SYS-2-INSCHED |
2-Critical |
[chars] within scheduler |
- |
Determine the component from the stack trace displayed in the error message. Then use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. |
- |
|
SYS-2-INSCHED |
2-Critical |
[chars] within scheduler |
- |
Determine the component from the stack trace displayed in the error message. Then use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. |
- |
|
SYS-2-INSCHED |
2-Critical |
[chars] within scheduler |
- |
Determine the component from the stack trace displayed in the error message. Then use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. |
- |
|
SYS-2-INTSCHED |
2-Critical |
'[chars]' at level [dec] [chars] |
The scheduler was entered from an interrupt service routine ISR. |
Determine the component from the stack trace and process name displayed in the error message. Then use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. If the stack trace indicates that the scheduler was called from an interrupt handler choose the DDTS component based on the interrupt handler. Otherwise use the process name to determine the DDTS component. |
- |
|
SYS-2-INTSCHED |
2-Critical |
'[chars]' at level [dec] |
The scheduler was entered from an interrupt service routine ISR. |
Determine the component from the stack trace and process name displayed in the error message. Then use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. If the stack trace indicates that the scheduler was called from an interrupt handler choose the DDTS component based on the interrupt handler. Otherwise use the process name to determine the DDTS component. |
- |
|
SYS-2-INTSCHED |
2-Critical |
'[chars]' at level [dec] |
The scheduler was entered from an interrupt service routine ISR. |
Determine the component from the stack trace and process name displayed in the error message. Then use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. If the stack trace indicates that the scheduler was called from an interrupt handler choose the DDTS component based on the interrupt handler. Otherwise use the process name to determine the DDTS component. |
- |
|
SYS-2-INTSCHED |
2-Critical |
'[chars]' at level [dec] |
The scheduler was entered from an interrupt service routine ISR. |
Determine the component from the stack trace and process name displayed in the error message. Then use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. If the stack trace indicates that the scheduler was called from an interrupt handler choose the DDTS component based on the interrupt handler. Otherwise use the process name to determine the DDTS component. |
- |
|
SYS-2-INTSCHED |
2-Critical |
'[chars]' at level [dec] |
The scheduler was entered from an interrupt service routine ISR. |
Determine the component from the stack trace and process name displayed in the error message. Then use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. If the stack trace indicates that the scheduler was called from an interrupt handler choose the DDTS component based on the interrupt handler. Otherwise use the process name to determine the DDTS component. |
- |
|
SYS-2-INTSCHED |
2-Critical |
'[chars]' at level [dec] |
The scheduler was entered from an interrupt service routine ISR. |
Determine the component from the stack trace and process name displayed in the error message. Then use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. If the stack trace indicates that the scheduler was called from an interrupt handler choose the DDTS component based on the interrupt handler. Otherwise use the process name to determine the DDTS component. |
- |
|
SYS-2-INVALID_FEATURE_INDEX |
2-Critical |
Feature index [dec] is not within the defined feature array boundary. |
An inconsistency was detected while looking up for feature index. It is software error because of wrong enumeration of feature index. |
none |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-INVALID_FEATURE_INDEX |
2-Critical |
- |
- |
- |
- |
|
SYS-2-INVALID_FEATURE_INDEX |
2-Critical |
- |
- |
- |
- |
|
SYS-2-INVALID_FEATURE_INDEX |
2-Critical |
- |
- |
- |
- |
|
SYS-2-LINEPROCDEAD |
2-Critical |
Killing process [chars] associated with line [dec] |
A process associated with a tty line was killed by another process. The line may go dead |
exec |
"If this messages recurs copy it exactly as it appears " "and report it to your technical support representative." |
|
SYS-2-LINEPROCDEAD |
2-Critical |
Killing process [chars] associated with line [dec] |
A process associated with a tty line was killed by another process. The line may go dead |
exec |
"If this messages recurs copy it exactly as it appears " "and report it to your technical support representative." |
|
SYS-2-LINEPROCDEAD |
2-Critical |
Killing process [chars] associated with line [dec] |
A process associated with a tty line was killed by another process. The line may go dead |
exec |
"If this messages recurs copy it exactly as it appears " "and report it to your technical support representative." |
|
SYS-2-LINEPROCDEAD |
2-Critical |
Killing process [chars] associated with line [dec] |
A process associated with a tty line was killed by another process. The line may go dead |
exec |
"If this messages recurs copy it exactly as it appears " "and report it to your technical support representative." |
|
SYS-2-LINEPROCDEAD |
2-Critical |
Killing process [chars] associated with line [dec] |
A process associated with a tty line was killed by another process. The line may go dead |
exec |
"If this messages recurs copy it exactly as it appears " "and report it to your technical support representative." |
|
SYS-2-LINEPROCDEAD |
2-Critical |
Killing process [chars] associated with line [dec] |
A process associated with a tty line was killed by another process. The line may go dead |
exec |
"If this messages recurs copy it exactly as it appears " "and report it to your technical support representative." |
|
SYS-2-LINKED |
2-Critical |
Bad [chars] of [hec] in queue [hec] |
An internal software error occurred. |
Determine the component from the stack trace and process name\n\ displayed in the error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. If the stack trace indicates that the\n\ buffer code was called from an interrupt handler use the interrupt\n\ handler to determine the DDTS component. Otherwise use the process\n\ name to determine the DDTS component. |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-LINKED |
2-Critical |
Bad [chars] of [hec] in queue [hec] |
An internal software error occurred. |
Determine the component from the stack trace and process name\n\ displayed in the error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. If the stack trace indicates that the\n\ buffer code was called from an interrupt handler use the interrupt\n\ handler to determine the DDTS component. Otherwise use the process\n\ name to determine the DDTS component. |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-LINKED |
2-Critical |
Bad [chars] of [hec] in queue [hec] |
An internal software error occurred. |
Determine the component from the stack trace and process name\n\ displayed in the error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. If the stack trace indicates that the\n\ buffer code was called from an interrupt handler use the interrupt\n\ handler to determine the DDTS component. Otherwise use the process\n\ name to determine the DDTS component. |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-LINKED |
2-Critical |
Bad [chars] of [hec] in queue [hec] |
An internal software error occurred. |
Determine the component from the stack trace and process name\n\ displayed in the error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. If the stack trace indicates that the\n\ buffer code was called from an interrupt handler use the interrupt\n\ handler to determine the DDTS component. Otherwise use the process\n\ name to determine the DDTS component. |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-LINKED |
2-Critical |
Bad [chars] of [hec] in queue [hec] |
An internal software error occurred. |
Determine the component from the stack trace and process name\n\ displayed in the error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. If the stack trace indicates that the\n\ buffer code was called from an interrupt handler use the interrupt\n\ handler to determine the DDTS component. Otherwise use the process\n\ name to determine the DDTS component. |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-LINKED |
2-Critical |
Bad [chars] of [hec] in queue [hec] |
An internal software error occurred. |
Determine the component from the stack trace and process name\n\ displayed in the error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. If the stack trace indicates that the\n\ buffer code was called from an interrupt handler use the interrupt\n\ handler to determine the DDTS component. Otherwise use the process\n\ name to determine the DDTS component. |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-LOWMEMIO |
2-Critical |
Low-memory debug exception limit=[dec] free=[dec] |
The router is configured to crash when total available IO memory drops below a specified threshold. That threshold has been reached. This may have occurred due to a memory leak or from supporting additional features. |
mem |
"If you suspect a memory leak " "copy the message exactly as it appears and " "report it to your technical support representative. " "Otherwise you may need to add memory " "or reduce the number of features you are trying to " "support." |
|
SYS-2-LOWMEMIO |
2-Critical |
Low-memory debug exception limit=[dec] free=[dec] |
The router is configured to crash when total available IO memory drops below a specified threshold. That threshold has been reached. This may have occurred due to a memory leak or from supporting additional features. |
mem |
"If you suspect a memory leak " "copy the message exactly as it appears and " "report it to your technical support representative. " "Otherwise you may need to add memory " "or reduce the number of features you are trying to " "support." |
|
SYS-2-LOWMEMIO |
2-Critical |
Low-memory debug exception limit=[dec] free=[dec] |
The router is configured to crash when total available IO memory drops below a specified threshold. That threshold has been reached. This may have occurred due to a memory leak or from supporting additional features. |
mem |
"If you suspect a memory leak " "copy the message exactly as it appears and " "report it to your technical support representative. " "Otherwise you may need to add memory " "or reduce the number of features you are trying to " "support." |
|
SYS-2-LOWMEMIO |
2-Critical |
Low-memory debug exception limit=[dec] free=[dec] |
The router is configured to crash when total available IO memory drops below a specified threshold. That threshold has been reached. This may have occurred due to a memory leak or from supporting additional features. |
mem |
"If you suspect a memory leak " "copy the message exactly as it appears and " "report it to your technical support representative. " "Otherwise you may need to add memory " "or reduce the number of features you are trying to " "support." |
|
SYS-2-LOWMEMIO |
2-Critical |
Low-memory debug exception limit=[dec] free=[dec] |
The router is configured to crash when total available IO memory drops below a specified threshold. That threshold has been reached. This may have occurred due to a memory leak or from supporting additional features. |
mem |
"If you suspect a memory leak " "copy the message exactly as it appears and " "report it to your technical support representative. " "Otherwise you may need to add memory " "or reduce the number of features you are trying to " "support." |
|
SYS-2-LOWMEMIO |
2-Critical |
Low-memory debug exception limit=[dec] free=[dec] |
The router is configured to crash when total available IO memory drops below a specified threshold. That threshold has been reached. This may have occurred due to a memory leak or from supporting additional features. |
mem |
"If you suspect a memory leak " "copy the message exactly as it appears and " "report it to your technical support representative. " "Otherwise you may need to add memory " "or reduce the number of features you are trying to " "support." |
|
SYS-2-LOWMEMPROC |
2-Critical |
Low-memory debug exception limit=[dec] free=[dec] |
The router is configured to crash when total available processor memory drops below a specified threshold. That threshold has been reached. This may have occurred due to a memory leak or from supporting additional features. |
mem |
"If you suspect a memory leak copy the message exactly as it appears and " "report it to your technical support representative. Otherwise you may " "need to add memory or reduce the number of features you are trying to " "support." |
|
SYS-2-LOWMEMPROC |
2-Critical |
Low-memory debug exception limit=[dec] free=[dec] |
The router is configured to crash when total available processor memory drops below a specified threshold. That threshold has been reached. This may have occurred due to a memory leak or from supporting additional features. |
mem |
"If you suspect a memory leak copy the message exactly as it appears and " "report it to your technical support representative. Otherwise you may " "need to add memory or reduce the number of features you are trying to " "support." |
|
SYS-2-LOWMEMPROC |
2-Critical |
Low-memory debug exception limit=[dec] free=[dec] |
The router is configured to crash when total available processor memory drops below a specified threshold. That threshold has been reached. This may have occurred due to a memory leak or from supporting additional features. |
mem |
"If you suspect a memory leak copy the message exactly as it appears and " "report it to your technical support representative. Otherwise you may " "need to add memory or reduce the number of features you are trying to " "support." |
|
SYS-2-LOWMEMPROC |
2-Critical |
Low-memory debug exception limit=[dec] free=[dec] |
The router is configured to crash when total available processor memory drops below a specified threshold. That threshold has been reached. This may have occurred due to a memory leak or from supporting additional features. |
mem |
"If you suspect a memory leak copy the message exactly as it appears and " "report it to your technical support representative. Otherwise you may " "need to add memory or reduce the number of features you are trying to " "support." |
|
SYS-2-LOWMEMPROC |
2-Critical |
Low-memory debug exception limit=[dec] free=[dec] |
The router is configured to crash when total available processor memory drops below a specified threshold. That threshold has been reached. This may have occurred due to a memory leak or from supporting additional features. |
mem |
"If you suspect a memory leak copy the message exactly as it appears and " "report it to your technical support representative. Otherwise you may " "need to add memory or reduce the number of features you are trying to " "support." |
|
SYS-2-LOWMEMPROC |
2-Critical |
Low-memory debug exception limit=[dec] free=[dec] |
The router is configured to crash when total available processor memory drops below a specified threshold. That threshold has been reached. This may have occurred due to a memory leak or from supporting additional features. |
mem |
"If you suspect a memory leak copy the message exactly as it appears and " "report it to your technical support representative. Otherwise you may " "need to add memory or reduce the number of features you are trying to " "support." |
|
SYS-2-MADVISEFAIL |
2-Critical |
Madvise failed memory at [hec]. |
An attempt was made to create secure mempool but it failed. |
os |
"This is a notification message only. No action is required." |
|
SYS-2-MALLOCFAIL |
2-Critical |
Memory allocation of [dec] bytes failed from [hex] alignment [dec] \n Pool: [chars] Free: [dec] Cause: [chars] \nAlternate Pool: [chars] Free: [dec] Cause: [chars] \n |
The requested memory allocation is not available from the specified memory pool. The current system configuration network environment or possibly a software error may have exhausted or fragmented the router's memory. |
mem-suspect |
"If you suspect a software error copy the error message exactly as it " "appears on the console or in the system log contact your technical support" "representativeand provide the representative with the gathered information. " "Otherwise you may need to add more memory or reduce the number of " "features you are trying to support." |
|
SYS-2-MALLOCFAIL |
2-Critical |
Memory allocation of [dec] bytes failed from [hex] alignment [dec] \n Pool: [chars] Free: [dec] Cause: [chars] \nAlternate Pool: [chars] Free: [dec] Cause: [chars] \n |
The requested memory allocation is not available from the specified memory pool. The current system configuration network environment or possibly a software error may have exhausted or fragmented the router's memory. |
mem-suspect |
"If you suspect a software error copy the error message exactly as it " "appears on the colsole or in the system log contact your technical support" "representativeand provide the representative with the gathered information. " "Otherwise you may need to add more memory or reduce the number of " "features you are trying to support." |
|
SYS-2-MALLOCFAIL |
2-Critical |
Memory allocation of [dec] bytes failed from [hex] alignment [dec] \n Pool: [chars] Free: [dec] Cause: [chars] \nAlternate Pool: [chars] Free: [dec] Cause: [chars] \n |
The requested memory allocation is not available from the specified memory pool. The current system configuration network environment or possibly a software error may have exhausted or fragmented the router's memory. |
mem-suspect |
"If you suspect a software error copy the error message exactly as it " "appears on the colsole or in the system log contact your technical support" "representativeand provide the representative with the gathered information. " "Otherwise you may need to add more memory or reduce the number of " "features you are trying to support." |
|
SYS-2-MALLOCFAIL |
2-Critical |
Memory allocation of [dec] bytes failed from [hex] alignment [dec] \n Pool: [chars] Free: [dec] Cause: [chars] \nAlternate Pool: [chars] Free: [dec] Cause: [chars] \n |
The requested memory allocation is not available from the specified memory pool. The current system configuration network environment or possibly a software error may have exhausted or fragmented the router's memory. |
mem-suspect |
"If you suspect a software error copy the error message exactly as it " "appears on the colsole or in the system log contact your technical support" "representativeand provide the representative with the gathered information. " "Otherwise you may need to add more memory or reduce the number of " "features you are trying to support." |
|
SYS-2-MALLOCFAIL |
2-Critical |
Memory allocation of [dec] bytes failed from [hex] alignment [dec] \n Pool: [chars] Free: [dec] Cause: [chars] \nAlternate Pool: [chars] Free: [dec] Cause: [chars] \n |
The requested memory allocation is not available from the specified memory pool. The current system configuration network environment or possibly a software error may have exhausted or fragmented the router's memory. |
mem-suspect |
"If you suspect a software error copy the error message exactly as it " "appears on the colsole or in the system log contact your technical support" "representativeand provide the representative with the gathered information. " "Otherwise you may need to add more memory or reduce the number of " "features you are trying to support." |
|
SYS-2-MALLOCFAIL |
2-Critical |
Memory allocation of [dec] bytes failed from [hex] alignment [dec] \n Pool: [chars] Free: [dec] Cause: [chars] \nAlternate Pool: [chars] Free: [dec] Cause: [chars] \n |
The requested memory allocation is not available from the specified memory pool. The current system configuration network environment or possibly a software error may have exhausted or fragmented the router's memory. |
mem-suspect |
"If you suspect a software error copy the error message exactly as it " "appears on the colsole or in the system log contact your technical support" "representativeand provide the representative with the gathered information. " "Otherwise you may need to add more memory or reduce the number of " "features you are trying to support." |
|
SYS-2-MAX_IDB_BM_EXCEEDED |
2-Critical |
BM bit allocation limit exceeded |
The BM has exhausted all of the bits available for allocation |
idb |
"Copy the error message exactly as it appears and report it to" " your technical support representative." |
|
SYS-2-MAX_IDB_BM_EXCEEDED |
2-Critical |
BM bit allocation limit exceeded |
The BM has exhausted all of the bits available for allocation |
idb |
"Copy the error message exactly as it appears and report it to" " your technical support representative." |
|
SYS-2-MAX_IDB_BM_EXCEEDED |
2-Critical |
BM bit allocation limit exceeded |
The BM has exhausted all of the bits available for allocation |
idb |
"Copy the error message exactly as it appears and report it to" " your technical support representative." |
|
SYS-2-MAX_IDB_BM_EXCEEDED |
2-Critical |
BM bit allocation limit exceeded |
The BM has exhausted all of the bits available for allocation |
idb |
"Copy the error message exactly as it appears and report it to" " your technical support representative." |
|
SYS-2-MAX_IDB_BM_EXCEEDED |
2-Critical |
BM bit allocation limit exceeded |
The BM has exhausted all of the bits available for allocation |
idb |
"Copy the error message exactly as it appears and report it to" " your technical support representative." |
|
SYS-2-MAX_IDB_BM_EXCEEDED |
2-Critical |
BM bit allocation limit exceeded |
The BM has exhausted all of the bits available for allocation |
idb |
"Copy the error message exactly as it appears and report it to" " your technical support representative." |
|
SYS-2-MMAP |
2-Critical |
mmap failed for size [dec] bytes Caller PC 0x[hec] errno [dec] |
Failed to allocate memory for the requested size. The memory could not be mapped because there is no memory. |
- |
- |
|
SYS-2-MMAP |
2-Critical |
mmap failed for size [dec] bytes Caller PC 0x[hec] errno [dec] |
Failed to allocate memory for the requested size. The memory could not be mapped because there is no memory. |
- |
- |
|
SYS-2-MMAP |
2-Critical |
mmap failed for size [dec] bytes Caller PC 0x[hec] errno [dec] |
Failed to allocate memory for the requested size. The memory could not be mapped because there is no memory. |
- |
- |
|
SYS-2-MMAP |
2-Critical |
mmap failed for size [dec] bytes Caller PC 0x[hec] errno [dec] |
Failed to allocate memory for the requested size. The memory could not be mapped because there is no memory. |
- |
- |
|
SYS-2-MMAP |
2-Critical |
mmap failed for size [dec] bytes Caller PC 0x[hec] errno [dec] |
Failed to allocate memory for the requested size. The memory could not be mapped because there is no memory. |
- |
- |
|
SYS-2-MMAP |
2-Critical |
mmap failed for size [dec] bytes Caller PC 0x[hec] errno [dec] |
Failed to allocate memory for the requested size. The memory could not be mapped because there is no memory. |
- |
- |
|
SYS-2-MUNMAP |
2-Critical |
Could not return memory Neutrino via munmap at %lx size [dec] errno [dec] |
Failued to unmap memory memory at the indicated location. The memory could not be unmapped because it was allocated via mmap. |
- |
- |
|
SYS-2-MUNMAP |
2-Critical |
Could not return memory Neutrino via munmap at %lx size [dec] errno [dec] |
Failued to unmap memory memory at the indicated location. The memory could not be unmapped because it was allocated via mmap. |
- |
- |
|
SYS-2-MUNMAP |
2-Critical |
Could not return memory Neutrino via munmap at %lx size [dec] errno [dec] |
Failued to unmap memory memory at the indicated location. The memory could not be unmapped because it was allocated via mmap. |
- |
- |
|
SYS-2-MUNMAP |
2-Critical |
Could not return memory Neutrino via munmap at %lx size [dec] errno [dec] |
Failued to unmap memory memory at the indicated location. The memory could not be unmapped because it was allocated via mmap. |
- |
- |
|
SYS-2-MUNMAP |
2-Critical |
Could not return memory Neutrino via munmap at %lx size [dec] errno [dec] |
Failued to unmap memory memory at the indicated location. The memory could not be unmapped because it was allocated via mmap. |
- |
- |
|
SYS-2-MUNMAP |
2-Critical |
Could not return memory Neutrino via munmap at %lx size [dec] errno [dec] |
Failued to unmap memory memory at the indicated location. The memory could not be unmapped because it was allocated via mmap. |
- |
- |
|
SYS-2-MUTEXLOCKFAIL |
2-Critical |
pthread_mutex_lock failed for [chars] |
The thread failed in pthread_mutex_lock while trying to acquire a mutex. |
mem-suspect |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-MUTEXLOCKFAIL |
2-Critical |
pthread_mutex_lock failed for [chars] |
The thread failed in pthread_mutex_lock while trying to acquire a mutex. |
mem-suspect |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-MUTEXLOCKFAIL |
2-Critical |
pthread_mutex_lock failed for [chars] |
The thread failed in pthread_mutex_lock while trying to acquire a mutex. |
mem-suspect |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-MUTEXLOCKFAIL |
2-Critical |
pthread_mutex_lock failed for [chars] |
The thread failed in pthread_mutex_lock while trying to acquire a mutex. |
mem-suspect |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-MUTEXLOCKFAIL |
2-Critical |
pthread_mutex_lock failed for [chars] |
The thread failed in pthread_mutex_lock while trying to acquire a mutex. |
mem-suspect |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-MUTEXLOCKFAIL |
2-Critical |
pthread_mutex_lock failed for [chars] |
The thread failed in pthread_mutex_lock while trying to acquire a mutex. |
mem-suspect |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-NOBLOCK |
2-Critical |
[chars] with blocking disabled. |
A process attempted to relinquish control with blocking disabled. |
Determine the component from the stack trace displayed in the error message. Use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. Choose the DDTS component associated with the routine that called the scheduler. |
- |
|
SYS-2-NOBLOCK |
2-Critical |
[chars] with blocking disabled. |
A process aattempted to relinquish control with blocking disabled. |
Determine the component from the stack trace displayed in the error message. Use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. Choose the DDTS component associated with the routine that called the scheduler. |
- |
|
SYS-2-NOBLOCK |
2-Critical |
[chars] with blocking disabled. |
A process aattempted to relinquish control with blocking disabled. |
Determine the component from the stack trace displayed in the error message. Use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. Choose the DDTS component associated with the routine that called the scheduler. |
- |
|
SYS-2-NOBLOCK |
2-Critical |
[chars] with blocking disabled. |
A process aattempted to relinquish control with blocking disabled. |
Determine the component from the stack trace displayed in the error message. Use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. Choose the DDTS component associated with the routine that called the scheduler. |
- |
|
SYS-2-NOBLOCK |
2-Critical |
[chars] with blocking disabled. |
A process aattempted to relinquish control with blocking disabled. |
Determine the component from the stack trace displayed in the error message. Use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. Choose the DDTS component associated with the routine that called the scheduler. |
- |
|
SYS-2-NOBLOCK |
2-Critical |
[chars] with blocking disabled. |
A process aattempted to relinquish control with blocking disabled. |
Determine the component from the stack trace displayed in the error message. Use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. Choose the DDTS component associated with the routine that called the scheduler. |
- |
|
SYS-2-NOMEMFRGIO |
2-Critical |
Memory fragmentation check debug exception fragment size [dec] |
The router is configured to crash when the largest available contiguous IO memory block drops below a specified threshold. That threshold has been reached. This may have occurred due to excessive memory thrashing or from supporting additional features. |
mem |
"If you suspect memory thrashing " "copy the message exactly as it appears " "and report it to your technical support representative. Otherwise " "you may need to add memory or reduce the number of features you are " "trying to support." |
|
SYS-2-NOMEMFRGIO |
2-Critical |
Memory fragmentation check debug exception fragment size [dec] |
The router is configured to crash when the largest available contiguous IO memory block drops below a specified threshold. That threshold has been reached. This may have occurred due to excessive memory thrashing or from supporting additional features. |
mem |
"If you suspect memory thrashing " "copy the message exactly as it appears " "and report it to your technical support representative. Otherwise " "you may need to add memory or reduce the number of features you are " "trying to support." |
|
SYS-2-NOMEMFRGIO |
2-Critical |
Memory fragmentation check debug exception fragment size [dec] |
The router is configured to crash when the largest available contiguous IO memory block drops below a specified threshold. That threshold has been reached. This may have occurred due to excessive memory thrashing or from supporting additional features. |
mem |
"If you suspect memory thrashing " "copy the message exactly as it appears " "and report it to your technical support representative. Otherwise " "you may need to add memory or reduce the number of features you are " "trying to support." |
|
SYS-2-NOMEMFRGIO |
2-Critical |
Memory fragmentation check debug exception fragment size [dec] |
The router is configured to crash when the largest available contiguous IO memory block drops below a specified threshold. That threshold has been reached. This may have occurred due to excessive memory thrashing or from supporting additional features. |
mem |
"If you suspect memory thrashing " "copy the message exactly as it appears " "and report it to your technical support representative. Otherwise " "you may need to add memory or reduce the number of features you are " "trying to support." |
|
SYS-2-NOMEMFRGIO |
2-Critical |
Memory fragmentation check debug exception fragment size [dec] |
The router is configured to crash when the largest available contiguous IO memory block drops below a specified threshold. That threshold has been reached. This may have occurred due to excessive memory thrashing or from supporting additional features. |
mem |
"If you suspect memory thrashing " "copy the message exactly as it appears " "and report it to your technical support representative. Otherwise " "you may need to add memory or reduce the number of features you are " "trying to support." |
|
SYS-2-NOMEMFRGIO |
2-Critical |
Memory fragmentation check debug exception fragment size [dec] |
The router is configured to crash when the largest available contiguous IO memory block drops below a specified threshold. That threshold has been reached. This may have occurred due to excessive memory thrashing or from supporting additional features. |
mem |
"If you suspect memory thrashing " "copy the message exactly as it appears " "and report it to your technical support representative. Otherwise " "you may need to add memory or reduce the number of features you are " "trying to support." |
|
SYS-2-NOMEMFRGPROC |
2-Critical |
Memory fragmentation check debug exception fragment size [dec] |
The router is configured to crash when the largest available contiguous processor memory block drops below a specified threshold. That threshold has been reached. This may have occurred due to excessive memory thrashing or from supporting additional features. |
mem |
"If you suspect memory thrashing copy the message exactly as it appears " "and report it to your technical support representative. Otherwise " "you may need to add memory or reduce the number of features you are " "trying to support." |
|
SYS-2-NOMEMFRGPROC |
2-Critical |
Memory fragmentation check debug exception fragment size [dec] |
The router is configured to crash when the largest available contiguous processor memory block drops below a specified threshold. That threshold has been reached. This may have occurred due to excessive memory thrashing or from supporting additional features. |
mem |
"If you suspect memory thrashing copy the message exactly as it appears " "and report it to your technical support representative. Otherwise " "you may need to add memory or reduce the number of features you are " "trying to support." |
|
SYS-2-NOMEMFRGPROC |
2-Critical |
Memory fragmentation check debug exception fragment size [dec] |
The router is configured to crash when the largest available contiguous processor memory block drops below a specified threshold. That threshold has been reached. This may have occurred due to excessive memory thrashing or from supporting additional features. |
mem |
"If you suspect memory thrashing copy the message exactly as it appears " "and report it to your technical support representative. Otherwise " "you may need to add memory or reduce the number of features you are " "trying to support." |
|
SYS-2-NOMEMFRGPROC |
2-Critical |
Memory fragmentation check debug exception fragment size [dec] |
The router is configured to crash when the largest available contiguous processor memory block drops below a specified threshold. That threshold has been reached. This may have occurred due to excessive memory thrashing or from supporting additional features. |
mem |
"If you suspect memory thrashing copy the message exactly as it appears " "and report it to your technical support representative. Otherwise " "you may need to add memory or reduce the number of features you are " "trying to support." |
|
SYS-2-NOMEMFRGPROC |
2-Critical |
Memory fragmentation check debug exception fragment size [dec] |
The router is configured to crash when the largest available contiguous processor memory block drops below a specified threshold. That threshold has been reached. This may have occurred due to excessive memory thrashing or from supporting additional features. |
mem |
"If you suspect memory thrashing copy the message exactly as it appears " "and report it to your technical support representative. Otherwise " "you may need to add memory or reduce the number of features you are " "trying to support." |
|
SYS-2-NOMEMFRGPROC |
2-Critical |
Memory fragmentation check debug exception fragment size [dec] |
The router is configured to crash when the largest available contiguous processor memory block drops below a specified threshold. That threshold has been reached. This may have occurred due to excessive memory thrashing or from supporting additional features. |
mem |
"If you suspect memory thrashing copy the message exactly as it appears " "and report it to your technical support representative. Otherwise " "you may need to add memory or reduce the number of features you are " "trying to support." |
|
SYS-2-NOMEMORY |
2-Critical |
No memory available for [chars] [dec] |
An operation could not be accomplished because of a low-memory condition. The current system configuration network environment or possibly a software error might have exhausted or fragmented the router's memory. |
mem-suspect |
"Reduce other system activity to ease memory demands. If conditions " "warrant upgrade to a configuration that has more memory." |
|
SYS-2-NOMEMORY |
2-Critical |
No memory available for [chars] [dec] |
An operation could not be accomplished because of a low-memory condition. The current system configuration network environment or possibly a software error might have exhausted or fragmented the router's memory. |
mem-suspect |
"Reduce other system activity to ease memory demands. If conditions " "warrant upgrade to a configuration that has more memory." |
|
SYS-2-NOMEMORY |
2-Critical |
No memory available for [chars] [dec] |
An operation could not be accomplished because of a low-memory condition. The current system configuration network environment or possibly a software error might have exhausted or fragmented the router's memory. |
mem-suspect |
"Reduce other system activity to ease memory demands. If conditions " "warrant upgrade to a configuration that has more memory." |
|
SYS-2-NOMEMORY |
2-Critical |
No memory available for [chars] [dec] |
An operation could not be accomplished because of a low-memory condition. The current system configuration network environment or possibly a software error might have exhausted or fragmented the router's memory. |
mem-suspect |
"Reduce other system activity to ease memory demands. If conditions " "warrant upgrade to a configuration that has more memory." |
|
SYS-2-NOMEMORY |
2-Critical |
No memory available for [chars] [dec] |
An operation could not be accomplished because of a low-memory condition. The current system configuration network environment or possibly a software error might have exhausted or fragmented the router's memory. |
mem-suspect |
"Reduce other system activity to ease memory demands. If conditions " "warrant upgrade to a configuration that has more memory." |
|
SYS-2-NOMEMORY |
2-Critical |
No memory available for [chars] [dec] |
An operation could not be accomplished because of a low-memory condition. The current system configuration network environment or possibly a software error might have exhausted or fragmented the router's memory. |
mem-suspect |
"Reduce other system activity to ease memory demands. If conditions " "warrant upgrade to a configuration that has more memory." |
|
SYS-2-NOPROCESS |
2-Critical |
No such process [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-NOPROCESS |
2-Critical |
No such process [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-NOPROCESS |
2-Critical |
No such process [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-NOPROCESS |
2-Critical |
No such process [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-NOPROCESS |
2-Critical |
No such process [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-NOPROCESS |
2-Critical |
No such process [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-NOTDEAD |
2-Critical |
Killing process [chars] pid [dec] again |
An internal software error occurred. |
os-scheduler |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-NOTDEAD |
2-Critical |
Killing process [chars] pid [dec] again |
An internal software error occurred. |
os-scheduler |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-NOTDEAD |
2-Critical |
Killing process [chars] pid [dec] again |
An internal software error occurred. |
os-scheduler |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-NOTDEAD |
2-Critical |
Killing process [chars] pid [dec] again |
An internal software error occurred. |
os-scheduler |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-NOTDEAD |
2-Critical |
Killing process [chars] pid [dec] again |
An internal software error occurred. |
os-scheduler |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-NOTDEAD |
2-Critical |
Killing process [chars] pid [dec] again |
An internal software error occurred. |
os-scheduler |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-NOTIOSTASK |
2-Critical |
[chars] from outside IOS task context |
An IOS reschedule request was made from code that is not running in the context of an IOS task -- from an interrupt handler the scheduler itself or a service pthread within the IOS process. |
Determine the component from the stack trace displayed in the\n\ error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-NOTIOSTASK |
2-Critical |
[chars] from outside IOS task context |
An IOS reschedule request was made from code that is not running in the context of an IOS task -- from an interrupt handler the scheduler itself or a service pthread within the IOS process. |
Determine the component from the stack trace displayed in the\n\ error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-NOTIOSTASK |
2-Critical |
[chars] from outside IOS task context |
An IOS reschedule request was made from code that is not running in the context of an IOS task -- from an interrupt handler the scheduler itself or a service pthread within the IOS process. |
Determine the component from the stack trace displayed in the\n\ error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-NOTIOSTASK |
2-Critical |
[chars] from outside IOS task context |
An IOS reschedule request was made from code that is not running in the context of an IOS task -- from an interrupt handler the scheduler itself or a service pthread within the IOS process. |
Determine the component from the stack trace displayed in the\n\ error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-NOTIOSTASK |
2-Critical |
[chars] from outside IOS task context |
An IOS reschedule request was made from code that is not running in the context of an IOS task -- from an interrupt handler the scheduler itself or a service pthread within the IOS process. |
Determine the component from the stack trace displayed in the\n\ error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-NOTIOSTASK |
2-Critical |
[chars] from outside IOS task context |
An IOS reschedule request was made from code that is not running in the context of an IOS task -- from an interrupt handler the scheduler itself or a service pthread within the IOS process. |
Determine the component from the stack trace displayed in the\n\ error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-NOTQ |
2-Critical |
[chars] didn't find [hec] in queue [hec] |
An internal software error occurred. |
Determine the component from the stack trace and process name\n\ displayed in the error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. If the stack trace indicates that the\n\ buffer code was called from an interrupt handler use the interrupt\n\ handler to determine the DDTS component. Otherwise use the process\n\ name to determine the DDTS component. |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-NOTQ |
2-Critical |
[chars] didn't find [hec] in queue [hec] |
An internal software error occurred. |
Determine the component from the stack trace and process name\n\ displayed in the error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. If the stack trace indicates that the\n\ buffer code was called from an interrupt handler use the interrupt\n\ handler to determine the DDTS component. Otherwise use the process\n\ name to determine the DDTS component. |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-NOTQ |
2-Critical |
[chars] didn't find [hec] in queue [hec] |
An internal software error occurred. |
Determine the component from the stack trace and process name\n\ displayed in the error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. If the stack trace indicates that the\n\ buffer code was called from an interrupt handler use the interrupt\n\ handler to determine the DDTS component. Otherwise use the process\n\ name to determine the DDTS component. |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-NOTQ |
2-Critical |
[chars] didn't find [hec] in queue [hec] |
An internal software error occurred. |
Determine the component from the stack trace and process name\n\ displayed in the error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. If the stack trace indicates that the\n\ buffer code was called from an interrupt handler use the interrupt\n\ handler to determine the DDTS component. Otherwise use the process\n\ name to determine the DDTS component. |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-NOTQ |
2-Critical |
[chars] didn't find [hec] in queue [hec] |
An internal software error occurred. |
Determine the component from the stack trace and process name\n\ displayed in the error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. If the stack trace indicates that the\n\ buffer code was called from an interrupt handler use the interrupt\n\ handler to determine the DDTS component. Otherwise use the process\n\ name to determine the DDTS component. |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-NOTQ |
2-Critical |
[chars] didn't find [hec] in queue [hec] |
An internal software error occurred. |
Determine the component from the stack trace and process name\n\ displayed in the error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. If the stack trace indicates that the\n\ buffer code was called from an interrupt handler use the interrupt\n\ handler to determine the DDTS component. Otherwise use the process\n\ name to determine the DDTS component. |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-NULLCHUNK |
2-Critical |
[chars] operation on Null Chunk |
Chunk manager cannot allocate memory from NULL chunks |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-NULLCHUNK |
2-Critical |
Memory requested from Null Chunk |
Chunk manager cannot allocate memory from NULL chunks |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-NULLCHUNK |
2-Critical |
Memory requested from Null Chunk |
Chunk manager cannot allocate memory from NULL chunks |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-NULLCHUNK |
2-Critical |
Memory requested from Null Chunk |
Chunk manager cannot allocate memory from NULL chunks |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-NULLCHUNK |
2-Critical |
Memory requested from Null Chunk |
Chunk manager cannot allocate memory from NULL chunks |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-NULLCHUNK |
2-Critical |
Memory requested from Null Chunk |
Chunk manager cannot allocate memory from NULL chunks |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-2-NV_BAD_PTR |
2-Critical |
Bad NVRAM pointer. NV Header values are nv: 0x%p .textbase: 0x%p .textsize: [dec] .magic: 0x%X .checksum: 0x%X .system_version: [dec] .textptr: 0x%p v1_ptr: 0x%p .priv: 0x%p |
- |
nvram |
LOG_STD_SH_TECH_ACTION |
|
SYS-2-PAK_SUBBLOCK_ALREADY |
2-Critical |
[dec] |
This message indicates an error in attempting to allocate a pak subblock. A subblock was already associated with the packet. |
- |
- |
|
SYS-2-PAK_SUBBLOCK_ALREADY |
2-Critical |
[dec] |
This message indicates an error in attempting to allocate a pak subblock. A subblock was already associated with the packet. |
- |
- |
|
SYS-2-PAK_SUBBLOCK_ALREADY |
2-Critical |
[dec] |
This message indicates an error in attempting to allocate a pak subblock. A subblock was already associated with the packet. |
- |
- |
|
SYS-2-PAK_SUBBLOCK_ALREADY |
2-Critical |
[dec] |
This message indicates an error in attempting to allocate a pak subblock. A subblock was already associated with the packet. |
- |
- |
|
SYS-2-PAK_SUBBLOCK_ALREADY |
2-Critical |
[dec] |
This message indicates an error in attempting to allocate a pak subblock. A subblock was already associated with the packet. |
- |
- |
|
SYS-2-PAK_SUBBLOCK_ALREADY |
2-Critical |
[dec] |
This message indicates an error in attempting to allocate a pak subblock. A subblock was already associated with the packet. |
- |
- |
|
SYS-2-PAK_SUBBLOCK_BADSIZE |
2-Critical |
[dec] |
This message indicates an error in attempting to allocate a pak subblock. The requested size is larger than the maximum registered subblock size. |
- |
- |
|
SYS-2-PAK_SUBBLOCK_BADSIZE |
2-Critical |
[dec] |
This message indicates an error in attempting to allocate a pak subblock. The requested size is larger than the maximum registered subblock size. |
- |
- |
|
SYS-2-PAK_SUBBLOCK_BADSIZE |
2-Critical |
[dec] |
This message indicates an error in attempting to allocate a pak subblock. The requested size is larger than the maximum registered subblock size. |
- |
- |
|
SYS-2-PAK_SUBBLOCK_BADSIZE |
2-Critical |
[dec] |
This message indicates an error in attempting to allocate a pak subblock. The requested size is larger than the maximum registered subblock size. |
- |
- |
|
SYS-2-PAK_SUBBLOCK_BADSIZE |
2-Critical |
[dec] |
This message indicates an error in attempting to allocate a pak subblock. The requested size is larger than the maximum registered subblock size. |
- |
- |
|
SYS-2-PAK_SUBBLOCK_BADSIZE |
2-Critical |
[dec] |
This message indicates an error in attempting to allocate a pak subblock. The requested size is larger than the maximum registered subblock size. |
- |
- |
|
SYS-2-PAK_SUBBLOCK_SETSIZE |
2-Critical |
[dec] |
This message indicates an error in startup code to register a pak subblock size. An attempt was made to register a size after the subblock chunk pool had been initialized. This problem is caused by software initialization order. |
- |
- |
|
SYS-2-PAK_SUBBLOCK_SETSIZE |
2-Critical |
[dec] |
This message indicates an error in startup code to register a pak subblock size. An attempt was made to register a size after the subblock chunk pool had been initialized. This problem is caused by software initialization order. |
- |
- |
|
SYS-2-PAK_SUBBLOCK_SETSIZE |
2-Critical |
[dec] |
This message indicates an error in startup code to register a pak subblock size. An attempt was made to register a size after the subblock chunk pool had been initialized. This problem is caused by software initialization order. |
- |
- |
|
SYS-2-PAK_SUBBLOCK_SETSIZE |
2-Critical |
[dec] |
This message indicates an error in startup code to register a pak subblock size. An attempt was made to register a size after the subblock chunk pool had been initialized. This problem is caused by software initialization order. |
- |
- |
|
SYS-2-PAK_SUBBLOCK_SETSIZE |
2-Critical |
[dec] |
This message indicates an error in startup code to register a pak subblock size. An attempt was made to register a size after the subblock chunk pool had been initialized. This problem is caused by software initialization order. |
- |
- |
|
SYS-2-PAK_SUBBLOCK_SETSIZE |
2-Critical |
[dec] |
This message indicates an error in startup code to register a pak subblock size. An attempt was made to register a size after the subblock chunk pool had been initialized. This problem is caused by software initialization order. |
- |
- |
|
SYS-2-PRIVCFG_DECRYPT_FAILURE |
2-Critical |
[chars] |
An error was encountered by the private config decryption |
none |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-PRIVCFG_ENCRYPT_FAILURE |
2-Critical |
[chars] |
An error was encountered by the private config encryption |
none |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-2-QCOUNT |
2-Critical |
Bad [chars] [hec] count [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-QCOUNT |
2-Critical |
Bad [chars] [hec] count [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-QCOUNT |
2-Critical |
Bad [chars] [hec] count [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-QCOUNT |
2-Critical |
Bad [chars] [hec] count [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-QCOUNT |
2-Critical |
Bad [chars] [hec] count [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-QCOUNT |
2-Critical |
Bad [chars] [hec] count [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-RUNTIME_CAPABILITY_NOT_SET |
2-Critical |
Capability value [chars] needed by Feature [chars] is not defined.\n |
An inconsistency was detected while looking up for capability on which feature functionality depends upon. It is software error because platform/branch using the feature should provide a override value for feature capability . |
none |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-2-SELFLINKED |
2-Critical |
Buffer [hec] linked to itself in free pool [chars] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SELFLINKED |
2-Critical |
Buffer [hec] linked to itself in free pool [chars] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SELFLINKED |
2-Critical |
Buffer [hec] linked to itself in free pool [chars] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SELFLINKED |
2-Critical |
Buffer [hec] linked to itself in free pool [chars] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SELFLINKED |
2-Critical |
Buffer [hec] linked to itself in free pool [chars] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SELFLINKED |
2-Critical |
Buffer [hec] linked to itself in free pool [chars] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SEMSCHED |
2-Critical |
'[chars]' |
The scheduler was entered with mempool semaphore held. |
Determine the component from the stack trace and process name displayed in the error message. Then use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. If the stack trace indicates that the scheduler was called with mempool semaphore held choose the DDTS component based on the process name displayed. |
- |
|
SYS-2-SHARED |
2-Critical |
Attempt to return buffer with sharecount [dec] ptr= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SHARED |
2-Critical |
Attempt to return buffer with sharecount [dec] ptr= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SHARED |
2-Critical |
Attempt to return buffer with sharecount [dec] ptr= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SHARED |
2-Critical |
Attempt to return buffer with sharecount [dec] ptr= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SHARED |
2-Critical |
Attempt to return buffer with sharecount [dec] ptr= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SHARED |
2-Critical |
Attempt to return buffer with sharecount [dec] ptr= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SHARED1 |
2-Critical |
Attempt to return buffer with sharecount [dec] ptr= [hec] caller= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SHARED1 |
2-Critical |
Attempt to return buffer with sharecount [dec] ptr= [hec] caller= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SHARED1 |
2-Critical |
Attempt to return buffer with sharecount [dec] ptr= [hec] caller= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SHARED1 |
2-Critical |
Attempt to return buffer with sharecount [dec] ptr= [hec] caller= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SHARED1 |
2-Critical |
Attempt to return buffer with sharecount [dec] ptr= [hec] caller= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SHARED1 |
2-Critical |
Attempt to return buffer with sharecount [dec] ptr= [hec] caller= [hec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SIGNUM |
2-Critical |
Process aborted on invalid signal signum = [dec]. |
An attempt was made to send an invalid signal to another process. |
- |
"If this message occurs more than once report this message " "to your technical support representative." |
|
SYS-2-SIGNUM |
2-Critical |
Process aborted on invalid signal signum = [dec]. |
An attempt was made to send an invalid signal to another process. |
- |
"If this message occurs more than once report this message " "to your technical support representative." |
|
SYS-2-SIGNUM |
2-Critical |
Process aborted on invalid signal signum = [dec]. |
An attempt was made to send an invalid signal to another process. |
- |
"If this message occurs more than once report this message " "to your technical support representative." |
|
SYS-2-SIGNUM |
2-Critical |
Process aborted on invalid signal signum = [dec]. |
An attempt was made to send an invalid signal to another process. |
- |
"If this message occurs more than once report this message " "to your technical support representative." |
|
SYS-2-SIGNUM |
2-Critical |
Process aborted on invalid signal signum = [dec]. |
An attempt was made to send an invalid signal to another process. |
- |
"If this message occurs more than once report this message " "to your technical support representative." |
|
SYS-2-SIGNUM |
2-Critical |
Process aborted on invalid signal signum = [dec]. |
An attempt was made to send an invalid signal to another process. |
- |
"If this message occurs more than once report this message " "to your technical support representative." |
|
SYS-2-SIGPENDING |
2-Critical |
Multiple Signals are sent to a process [dec] |
An internal software error occurred. |
os |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SIGPENDING |
2-Critical |
Multiple Signals are sent to a process [dec] |
An internal software error occurred. |
os |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SIGPENDING |
2-Critical |
Multiple Signals are sent to a process [dec] |
An internal software error occurred. |
os |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SIGPENDING |
2-Critical |
Multiple Signals are sent to a process [dec] |
An internal software error occurred. |
os |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SIGPENDING |
2-Critical |
Multiple Signals are sent to a process [dec] |
An internal software error occurred. |
os |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SIGPENDING |
2-Critical |
Multiple Signals are sent to a process [dec] |
An internal software error occurred. |
os |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SNMP0IDX |
2-Critical |
Attempt to [chars] snmpidb with if_index of 0 |
A software error occurred. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-2-SNMP0IDX |
2-Critical |
Attempt to [chars] snmpidb with if_index of 0 |
A software error occurred. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-2-SNMP0IDX |
2-Critical |
Attempt to [chars] snmpidb with if_index of 0 |
A software error occurred. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-2-SNMP0IDX |
2-Critical |
Attempt to [chars] snmpidb with if_index of 0 |
A software error occurred. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-2-SNMP0IDX |
2-Critical |
Attempt to [chars] snmpidb with if_index of 0 |
A software error occurred. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-2-SNMP0IDX |
2-Critical |
Attempt to [chars] snmpidb with if_index of 0 |
A software error occurred. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-2-SPEC |
2-Critical |
Trying to set unknown special character [dec] to [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SPEC |
2-Critical |
Trying to set unknown special character [dec] to [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SPEC |
2-Critical |
Trying to set unknown special character [dec] to [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SPEC |
2-Critical |
Trying to set unknown special character [dec] to [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SPEC |
2-Critical |
Trying to set unknown special character [dec] to [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SPEC |
2-Critical |
Trying to set unknown special character [dec] to [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-2-SYSMEMINFO |
2-Critical |
System Memory: %luK total %luK used %luK free |
This is an auxiliary message to several memory-related messages. It\n\ provides system memory information usage. |
- |
"This message provides additional information only. Copy the error \n\ message exactly as it appears and report it to your technical support \n\ representative as part of a previously printed error message." |
|
SYS-2-SYSMEMINFO |
2-Critical |
System Memory: %luK total %luK used %luK free |
This is an auxiliary message to several memory-related messages. It\n\ provides system memory information usage. |
- |
"This message provides additional information only. Copy the error \n\ message exactly as it appears and report it to your technical support \n\ representative as part of a previously printed error message." |
|
SYS-2-SYSMEMINFO |
2-Critical |
System Memory: %luK total %luK used %luK free |
This is an auxiliary message to several memory-related messages. It\n\ provides system memory information usage. |
- |
"This message provides additional information only. Copy the error \n\ message exactly as it appears and report it to your technical support \n\ representative as part of a previously printed error message." |
|
SYS-2-SYSMEMINFO |
2-Critical |
System Memory: %luK total %luK used %luK free |
This is an auxiliary message to several memory-related messages. It\n\ provides system memory information usage. |
- |
"This message provides additional information only. Copy the error \n\ message exactly as it appears and report it to your technical support \n\ representative as part of a previously printed error message." |
|
SYS-2-SYSMEMINFO |
2-Critical |
System Memory: %luK total %luK used %luK free |
This is an auxiliary message to several memory-related messages. It\n\ provides system memory information usage. |
- |
"This message provides additional information only. Copy the error \n\ message exactly as it appears and report it to your technical support \n\ representative as part of a previously printed error message." |
|
SYS-2-SYSMEMINFO |
2-Critical |
System Memory: %luK total %luK used %luK free |
This is an auxiliary message to several memory-related messages. It\n\ provides system memory information usage. |
- |
"This message provides additional information only. Copy the error \n\ message exactly as it appears and report it to your technical support \n\ representative as part of a previously printed error message." |
|
SYS-2-USERLOG_CRIT |
2-Critical |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only. " |
|
SYS-2-USERLOG_CRIT |
2-Critical |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only. " |
|
SYS-2-USERLOG_CRIT |
2-Critical |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only. " |
|
SYS-2-USERLOG_CRIT |
2-Critical |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only. " |
|
SYS-2-USERLOG_CRIT |
2-Critical |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only. " |
|
SYS-2-USERLOG_CRIT |
2-Critical |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only. " |
|
SYS-2-WATCHDOG |
2-Critical |
Process aborted on watchdog timeout process = [chars].[chars] |
The indicated process ran for too long without relinquishing control. The system killed it as a runaway process. |
- |
- |
|
SYS-2-WATCHDOG |
2-Critical |
Process aborted on watchdog timeout process = [chars].[chars] |
The indicated process ran for too long without relinquishing control. The system killed it as a runaway process. |
- |
- |
|
SYS-2-WATCHDOG |
2-Critical |
Process aborted on watchdog timeout process = [chars].[chars] |
The indicated process ran for too long without relinquishing control. The system killed it as a runaway process. |
- |
- |
|
SYS-2-WATCHDOG |
2-Critical |
Process aborted on watchdog timeout process = [chars].[chars] |
The indicated process ran for too long without relinquishing control. The system killed it as a runaway process. |
- |
- |
|
SYS-2-WATCHDOG |
2-Critical |
Process aborted on watchdog timeout process = [chars].[chars] |
The indicated process ran for too long without relinquishing control. The system killed it as a runaway process. |
- |
- |
|
SYS-2-WATCHDOG |
2-Critical |
Process aborted on watchdog timeout process = [chars].[chars] |
The indicated process ran for too long without relinquishing control. The system killed it as a runaway process. |
- |
- |
|
SYS-2-WRONGPOOL |
2-Critical |
Buffer [hec] found in pool [hec] should be in pool [hec] |
A software error occurred. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-2-WRONGPOOL |
2-Critical |
Buffer [hec] found in pool [hec] should be in pool [hec] |
A software error occurred. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-2-WRONGPOOL |
2-Critical |
Buffer [hec] found in pool [hec] should be in pool [hec] |
A software error occurred. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-2-WRONGPOOL |
2-Critical |
Buffer [hec] found in pool [hec] should be in pool [hec] |
A software error occurred. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-2-WRONGPOOL |
2-Critical |
Buffer [hec] found in pool [hec] should be in pool [hec] |
A software error occurred. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-2-WRONGPOOL |
2-Critical |
Buffer [hec] found in pool [hec] should be in pool [hec] |
A software error occurred. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-3-ABRUPTTERM |
3-Error |
Abrupt termination of tty session for [chars] [t-line] |
An internal software error occurred. |
os |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-ABRUPTTERM |
3-Error |
Abrupt termination of tty session for [chars] [t-line] |
An internal software error occurred. |
os |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-ABRUPTTERM |
3-Error |
Abrupt termination of tty session for [chars] [t-line] |
An internal software error occurred. |
os |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-ABRUPTTERM |
3-Error |
Abrupt termination of tty session for [chars] [t-line] |
An internal software error occurred. |
os |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-ABRUPTTERM |
3-Error |
Abrupt termination of tty session for [chars] [t-line] |
An internal software error occurred. |
os |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-ABRUPTTERM |
3-Error |
Abrupt termination of tty session for [chars] [t-line] |
An internal software error occurred. |
os |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-BAD_GLIBC_BUF_FREE |
3-Error |
A glibc buffer is freed in IOS buffer blockmagic: 0x[hec] flags 0x[hec] |
A software error occurred. A glibc buffer is freed into IOS buffer pool. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BAD_RESET |
3-Error |
Questionable reset of process [dec] on tty[t-line]\n |
A process was reset without giving it a chance to clean itself up. |
exec |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BAD_RESET |
3-Error |
Questionable reset of process [dec] on tty[t-line]\n |
A process was reset without giving it a chance to clean itself up. |
exec |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BAD_RESET |
3-Error |
Questionable reset of process [dec] on tty[t-line]\n |
A process was reset without giving it a chance to clean itself up. |
exec |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BAD_RESET |
3-Error |
Questionable reset of process [dec] on tty[t-line]\n |
A process was reset without giving it a chance to clean itself up. |
exec |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BAD_RESET |
3-Error |
Questionable reset of process [dec] on tty[t-line]\n |
A process was reset without giving it a chance to clean itself up. |
exec |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BAD_RESET |
3-Error |
Questionable reset of process [dec] on tty[t-line]\n |
A process was reset without giving it a chance to clean itself up. |
exec |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BAD_TRIPCOUNT |
3-Error |
Traversed block count crossed the maximum possible count[dec]/[dec] in |
A software error occurred. Value of tripcount has been zero or less which is harmful. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADBLOCK |
3-Error |
Bad block pointer [hec] |
A block of memory at the indicated location is corrupt. An internal check of memory block pointers indicates an inconsistency. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload then the router will " "need to reloaded manually." |
|
SYS-3-BADBLOCK |
3-Error |
Bad block pointer [hec] |
A block of memory at the indicated location is corrupt. An internal check of memory block pointers indicates an inconsistency. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to auotmatically reload then the router will " "need to reloaded manually." |
|
SYS-3-BADBLOCK |
3-Error |
Bad block pointer [hec] |
A block of memory at the indicated location is corrupt. An internal check of memory block pointers indicates an inconsistency. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to auotmatically reload then the router will " "need to reloaded manually." |
|
SYS-3-BADBLOCK |
3-Error |
Bad block pointer [hec] |
A block of memory at the indicated location is corrupt. An internal check of memory block pointers indicates an inconsistency. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to auotmatically reload then the router will " "need to reloaded manually." |
|
SYS-3-BADBLOCK |
3-Error |
Bad block pointer [hec] |
A block of memory at the indicated location is corrupt. An internal check of memory block pointers indicates an inconsistency. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to auotmatically reload then the router will " "need to reloaded manually." |
|
SYS-3-BADBLOCK |
3-Error |
Bad block pointer [hec] |
A block of memory at the indicated location is corrupt. An internal check of memory block pointers indicates an inconsistency. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to auotmatically reload then the router will " "need to reloaded manually." |
|
SYS-3-BADDISP |
3-Error |
Bad disposal code [hec] in [chars] |
An invalid status code has been passed to a buffer deletion routine. The buffer will be correctly returned to the free pool but will not be correctly counted in the per-protocol statistics. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADDISP |
3-Error |
Bad disposal code [hec] in [chars] |
An invalid status code has been passed to a buffer deletion routine. The buffer will be correctly returned to the free pool but will not be correctly counted in the per-protocol statistics. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADDISP |
3-Error |
Bad disposal code [hec] in [chars] |
An invalid status code has been passed to a buffer deletion routine. The buffer will be correctly returned to the free pool but will not be correctly counted in the per-protocol statistics. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADDISP |
3-Error |
Bad disposal code [hec] in [chars] |
An invalid status code has been passed to a buffer deletion routine. The buffer will be correctly returned to the free pool but will not be correctly counted in the per-protocol statistics. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADDISP |
3-Error |
Bad disposal code [hec] in [chars] |
An invalid status code has been passed to a buffer deletion routine. The buffer will be correctly returned to the free pool but will not be correctly counted in the per-protocol statistics. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADDISP |
3-Error |
Bad disposal code [hec] in [chars] |
An invalid status code has been passed to a buffer deletion routine. The buffer will be correctly returned to the free pool but will not be correctly counted in the per-protocol statistics. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADFREEMAGIC |
3-Error |
Corrupt free block at [hec] magic %08x |
A block of memory at the indicated location is corrupt. An inconsistency was detected while checking the free memory area. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-3-BADFREEMAGIC |
3-Error |
Corrupt free block at [hec] magic %08x |
A block of memory at the indicated location is corrupt. An inconsistency was detected while checking the free memory area. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-3-BADFREEMAGIC |
3-Error |
Corrupt free block at [hec] magic %08x |
A block of memory at the indicated location is corrupt. An inconsistency was detected while checking the free memory area. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-3-BADFREEMAGIC |
3-Error |
Corrupt free block at [hec] magic %08x |
A block of memory at the indicated location is corrupt. An inconsistency was detected while checking the free memory area. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-3-BADFREEMAGIC |
3-Error |
Corrupt free block at [hec] magic %08x |
A block of memory at the indicated location is corrupt. An inconsistency was detected while checking the free memory area. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-3-BADFREEMAGIC |
3-Error |
Corrupt free block at [hec] magic %08x |
A block of memory at the indicated location is corrupt. An inconsistency was detected while checking the free memory area. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-3-BADFREEPTRS |
3-Error |
Bad [chars] pointer [hec] at [hec] [chars] = [hec] |
A pointer in the block header at the indicated location is corrupt. An inconsistensy was detected in the free memory pool. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-3-BADFREEPTRS |
3-Error |
Bad [chars] pointer [hec] at [hec] [chars] = [hec] |
A pointer in the block header at the indicated location is corrupt. An inconsistensy was detected in the free memory pool. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-3-BADFREEPTRS |
3-Error |
Bad [chars] pointer [hec] at [hec] [chars] = [hec] |
A pointer in the block header at the indicated location is corrupt. An inconsistensy was detected in the free memory pool. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-3-BADFREEPTRS |
3-Error |
Bad [chars] pointer [hec] at [hec] [chars] = [hec] |
A pointer in the block header at the indicated location is corrupt. An inconsistensy was detected in the free memory pool. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-3-BADFREEPTRS |
3-Error |
Bad [chars] pointer [hec] at [hec] [chars] = [hec] |
A pointer in the block header at the indicated location is corrupt. An inconsistensy was detected in the free memory pool. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-3-BADFREEPTRS |
3-Error |
Bad [chars] pointer [hec] at [hec] [chars] = [hec] |
A pointer in the block header at the indicated location is corrupt. An inconsistensy was detected in the free memory pool. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-3-BADLINKTYPE |
3-Error |
* Unexpected linktype [dec] |
* A software error occurred. |
udp |
* "Copy the error message exactly as it appears and report it to your " * "technical support representative." |
|
SYS-3-BADLINKTYPE |
3-Error |
* Unexpected linktype [dec] |
* A software error occurred. |
udp |
* "Copy the error message exactly as it appears and report it to your " * "technical support representative." |
|
SYS-3-BADLINKTYPE |
3-Error |
* Unexpected linktype [dec] |
* A software error occurred. |
udp |
* "Copy the error message exactly as it appears and report it to your " * "technical support representative." |
|
SYS-3-BADLINKTYPE |
3-Error |
* Unexpected linktype [dec] |
* A software error occurred. |
udp |
* "Copy the error message exactly as it appears and report it to your " * "technical support representative." |
|
SYS-3-BADLINKTYPE |
3-Error |
* Unexpected linktype [dec] |
* A software error occurred. |
udp |
* "Copy the error message exactly as it appears and report it to your " * "technical support representative." |
|
SYS-3-BADLINKTYPE |
3-Error |
* Unexpected linktype [dec] |
* A software error occurred. |
udp |
* "Copy the error message exactly as it appears and report it to your " * "technical support representative." |
|
SYS-3-BADLIST_DESTROY |
3-Error |
Removed a non-empty list[hec] name: [chars] having %lu elements |
A non-empty list should not be destroyed. If it happens there is a possibility that all elements enqueued into the list will never be deallocated. This message reports that an non-empty list got destroyed. |
Determine the component from the stack trace and process name displayed in the error message. |
LOG_STD_ACTION |
|
SYS-3-BADLIST_DESTROY |
3-Error |
Removed a non-empty list[hec] name: [chars] having %lu elements |
A non-empty list should not be destroyed. If it happens there is a possibility that all elements enqueued into the list will never be deallocated. This message reports that an non-empty list got destroyed. |
Determine the component from the stack trace and process name displayed in the error message. |
LOG_STD_ACTION |
|
SYS-3-BADLIST_DESTROY |
3-Error |
Removed a non-empty list[hec] name: [chars] having %lu elements |
A non-empty list should not be destroyed. If it happens there is a possibility that all elements enqueued into the list will never be deallocated. This message reports that an non-empty list got destroyed. |
Determine the component from the stack trace and process name displayed in the error message. |
LOG_STD_ACTION |
|
SYS-3-BADLIST_DESTROY |
3-Error |
Removed a non-empty list[hec] name: [chars] having %lu elements |
A non-empty list should not be destroyed. If it happens there is a possibility that all elements enqueued into the list will never be deallocated. This message reports that an non-empty list got destroyed. |
Determine the component from the stack trace and process name displayed in the error message. |
LOG_STD_ACTION |
|
SYS-3-BADLIST_DESTROY |
3-Error |
Removed a non-empty list[hec] name: [chars] having %lu elements |
A non-empty list should not be destroyed. If it happens there is a possibility that all elements enqueued into the list will never be deallocated. This message reports that an non-empty list got destroyed. |
Determine the component from the stack trace and process name displayed in the error message. |
LOG_STD_ACTION |
|
SYS-3-BADLIST_DESTROY |
3-Error |
Removed a non-empty list[hec] name: [chars] having %lu elements |
A non-empty list should not be destroyed. If it happens there is a possibility that all elements enqueued into the list will never be deallocated. This message reports that an non-empty list got destroyed. |
Determine the component from the stack trace and process name displayed in the error message. |
LOG_STD_ACTION |
|
SYS-3-BADMAGIC |
3-Error |
Corrupt block at [hec] magic %08x |
The free memory pool is corrupt. An inconsistensy was detected in the free memory pool. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-3-BADMAGIC |
3-Error |
Corrupt block at [hec] magic %08x |
The free memory pool is corrupt. An inconsistensy was detected in the free memory pool. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-3-BADMAGIC |
3-Error |
Corrupt block at [hec] magic %08x |
The free memory pool is corrupt. An inconsistensy was detected in the free memory pool. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-3-BADMAGIC |
3-Error |
Corrupt block at [hec] magic %08x |
The free memory pool is corrupt. An inconsistensy was detected in the free memory pool. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-3-BADMAGIC |
3-Error |
Corrupt block at [hec] magic %08x |
The free memory pool is corrupt. An inconsistensy was detected in the free memory pool. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-3-BADMAGIC |
3-Error |
Corrupt block at [hec] magic %08x |
The free memory pool is corrupt. An inconsistensy was detected in the free memory pool. |
- |
"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. " "Save any crashinfo or crashdump files. If the router has crashed and " "was not configured to automatically reload the router will " "need to be reloaded manually." |
|
SYS-3-BADPARAM |
3-Error |
Function [chars]: value [hex] passed in parameter [chars] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADPARAM |
3-Error |
Function [chars]: value [hex] passed in parameter [chars] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADPARAM |
3-Error |
Function [chars]: value [hex] passed in parameter [chars] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADPARAM |
3-Error |
Function [chars]: value [hex] passed in parameter [chars] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADPARAM |
3-Error |
Function [chars]: value [hex] passed in parameter [chars] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADPARAM |
3-Error |
Function [chars]: value [hex] passed in parameter [chars] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADPRINT |
3-Error |
Process has no associated tty in [chars]. |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADPRINT |
3-Error |
Process has no associated tty in [chars]. |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADPRINT |
3-Error |
Process has no associated tty in [chars]. |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADPRINT |
3-Error |
Process has no associated tty in [chars]. |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADPRINT |
3-Error |
Process has no associated tty in [chars]. |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADPRINT |
3-Error |
Process has no associated tty in [chars]. |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADPROCESS |
3-Error |
Bad process ID [dec] when [chars] process table |
An internal software error occurred. |
os-scheduler |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADPROCESS |
3-Error |
Bad process ID [dec] when [chars] process table |
An internal software error occurred. |
os-scheduler |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADPROCESS |
3-Error |
Bad process ID [dec] when [chars] process table |
An internal software error occurred. |
os-scheduler |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADPROCESS |
3-Error |
Bad process ID [dec] when [chars] process table |
An internal software error occurred. |
os-scheduler |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADPROCESS |
3-Error |
Bad process ID [dec] when [chars] process table |
An internal software error occurred. |
os-scheduler |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADPROCESS |
3-Error |
Bad process ID [dec] when [chars] process table |
An internal software error occurred. |
os-scheduler |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADPTRVAL |
3-Error |
Bad pointer value [chars] = [hec] in function [chars] |
Corrupted pointer value is encountered. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-BADPTRVAL |
3-Error |
Bad pointer value [chars] = [hec] in function [chars] |
Corrupted pointer value is encountered. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-BADPTRVAL |
3-Error |
Bad pointer value [chars] = [hec] in function [chars] |
Corrupted pointer value is encountered. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-BADPTRVAL |
3-Error |
Bad pointer value [chars] = [hec] in function [chars] |
Corrupted pointer value is encountered. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-BADPTRVAL |
3-Error |
Bad pointer value [chars] = [hec] in function [chars] |
Corrupted pointer value is encountered. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-BADPTRVAL |
3-Error |
Bad pointer value [chars] = [hec] in function [chars] |
Corrupted pointer value is encountered. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-BADREFCOUNT |
3-Error |
Bad reference count at [hec] refcount [hec] |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-3-BADREFCOUNT |
3-Error |
Bad reference count at [hec] refcount [hec] |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-3-BADREFCOUNT |
3-Error |
Bad reference count at [hec] refcount [hec] |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-3-BADREFCOUNT |
3-Error |
Bad reference count at [hec] refcount [hec] |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-3-BADREFCOUNT |
3-Error |
Bad reference count at [hec] refcount [hec] |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-3-BADREFCOUNT |
3-Error |
Bad reference count at [hec] refcount [hec] |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
SYS-3-BADRESID |
3-Error |
Clock hardware returned bad residual [dec]. |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADRESID |
3-Error |
Clock hardware returned bad residual [dec]. |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADRESID |
3-Error |
Clock hardware returned bad residual [dec]. |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADRESID |
3-Error |
Clock hardware returned bad residual [dec]. |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADRESID |
3-Error |
Clock hardware returned bad residual [dec]. |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADRESID |
3-Error |
Clock hardware returned bad residual [dec]. |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-BADTREEPARAM |
3-Error |
Bad parameter for [chars] passed to tree library function. |
This message indicates that a pointer passed to a tree library function is invalid. |
- |
LOG_STD_SH_TECH_ACTION |
|
SYS-3-BADTREEPARAM |
3-Error |
Bad parameter for [chars] passed to tree library function. |
This message indicates that a pointer passed to a tree library function is invalid. |
- |
LOG_STD_SH_TECH_ACTION |
|
SYS-3-BADTREEPARAM |
3-Error |
Bad parameter for [chars] passed to tree library function. |
This message indicates that a pointer passed to a tree library function is invalid. |
- |
LOG_STD_SH_TECH_ACTION |
|
SYS-3-BADTREEPARAM |
3-Error |
Bad parameter for [chars] passed to tree library function. |
This message indicates that a pointer passed to a tree library function is invalid. |
- |
LOG_STD_SH_TECH_ACTION |
|
SYS-3-BADTREEPARAM |
3-Error |
Bad parameter for [chars] passed to tree library function. |
This message indicates that a pointer passed to a tree library function is invalid. |
- |
LOG_STD_SH_TECH_ACTION |
|
SYS-3-BADTREEPARAM |
3-Error |
Bad parameter for [chars] passed to tree library function. |
This message indicates that a pointer passed to a tree library function is invalid. |
- |
LOG_STD_SH_TECH_ACTION |
|
SYS-3-CERF_RECOVER |
3-Error |
[chars] |
This message is emitted when there has been a full recovery after a cache error |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-CERF_RECOVER |
3-Error |
[chars] |
This message is emitted when there has been a full recovery after a cache error |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-CERF_RECOVER |
3-Error |
[chars] |
This message is emitted when there has been a full recovery after a cache error |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-CERF_RECOVER |
3-Error |
[chars] |
This message is emitted when there has been a full recovery after a cache error |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-CERF_RECOVER |
3-Error |
[chars] |
This message is emitted when there has been a full recovery after a cache error |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-CERF_RECOVER |
3-Error |
[chars] |
This message is emitted when there has been a full recovery after a cache error |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-CFG_AT_RELOAD |
3-Error |
System reloading unable to complete startup configuration update |
Startup configuration updation is already in progress and reload has been called either from interrupt level or with all interrupts disabled. Reload can not suspend to let startup configuration updation get completed. Startup configuration may get corrupted. |
none |
"This is a notification message only. No action is required." |
|
SYS-3-CFG_AT_RELOAD |
3-Error |
System reloading unable to complete startup configuration update |
Startup configuration updation is already in progress and reload has been called either from interrupt level or with all interrupts disabled. Reload can not suspend to let startup configuration updation get completed. Startup configuration may get corrupted. |
none |
"This is a notification message only. No action is required." |
|
SYS-3-CFG_AT_RELOAD |
3-Error |
System reloading unable to complete startup configuration update |
Startup configuration updation is already in progress and reload has been called either from interrupt level or with all interrupts disabled. Reload can not suspend to let startup configuration updation get completed. Startup configuration may get corrupted. |
none |
"This is a notification message only. No action is required." |
|
SYS-3-CFG_AT_RELOAD |
3-Error |
System reloading unable to complete startup configuration update |
Startup configuration updation is already in progress and reload has been called either from interrupt level or with all interrupts disabled. Reload can not suspend to let startup configuration updation get completed. Startup configuration may get corrupted. |
none |
"This is a notification message only. No action is required." |
|
SYS-3-CFG_AT_RELOAD |
3-Error |
System reloading unable to complete startup configuration update |
Startup configuration updation is already in progress and reload has been called either from interrupt level or with all interrupts disabled. Reload can not suspend to let startup configuration updation get completed. Startup configuration may get corrupted. |
none |
"This is a notification message only. No action is required." |
|
SYS-3-CFG_AT_RELOAD |
3-Error |
System reloading unable to complete startup configuration update |
Startup configuration updation is already in progress and reload has been called either from interrupt level or with all interrupts disabled. Reload can not suspend to let startup configuration updation get completed. Startup configuration may get corrupted. |
none |
"This is a notification message only. No action is required." |
|
SYS-3-CHUNK_NO_EXMEM |
3-Error |
No handler to [chars] external memory. |
An attempt was made to allocate or free a chunk of external memory but no handler for managing external memory was registered. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-CHUNK_NO_EXMEM |
3-Error |
No handler to [chars] external memory. |
An attempt was made to allocate or free a chunk of external memory but no handler for managing external memory was registered. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-CHUNK_NO_EXMEM |
3-Error |
No handler to [chars] external memory. |
An attempt was made to allocate or free a chunk of external memory but no handler for managing external memory was registered. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-CHUNK_NO_EXMEM |
3-Error |
No handler to [chars] external memory. |
An attempt was made to allocate or free a chunk of external memory but no handler for managing external memory was registered. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-CHUNK_NO_EXMEM |
3-Error |
No handler to [chars] external memory. |
An attempt was made to allocate or free a chunk of external memory but no handler for managing external memory was registered. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-CHUNK_NO_EXMEM |
3-Error |
No handler to [chars] external memory. |
An attempt was made to allocate or free a chunk of external memory but no handler for managing external memory was registered. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-CONFIG_NO_PRIVATE |
3-Error |
No space remaining to save private config |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-CONFIG_NO_PRIVATE |
3-Error |
No space remaining to save private config |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-CONFIG_NO_PRIVATE |
3-Error |
No space remaining to save private config |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-CONFIG_NO_PRIVATE |
3-Error |
No space remaining to save private config |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-CONFIG_NO_PRIVATE |
3-Error |
No space remaining to save private config |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-CONFIG_NO_PRIVATE |
3-Error |
No space remaining to save private config |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-CONFIG_NV_DATA |
3-Error |
Variable [chars] not set properly in the routine [chars]. |
The write of the nonvolatile configuration failed because an internal variable was not set properly. |
- |
"If this messages occurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-CONFIG_NV_DATA |
3-Error |
Variable [chars] not set properly in the routine [chars]. |
The write of the nonvolatile configuration failed because an internal variable was not set properly. |
- |
"If this messages occurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-CONFIG_NV_DATA |
3-Error |
Variable [chars] not set properly in the routine [chars]. |
The write of the nonvolatile configuration failed because an internal variable was not set properly. |
- |
"If this messages occurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-CONFIG_NV_DATA |
3-Error |
Variable [chars] not set properly in the routine [chars]. |
The write of the nonvolatile configuration failed because an internal variable was not set properly. |
- |
"If this messages occurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-CONFIG_NV_DATA |
3-Error |
Variable [chars] not set properly in the routine [chars]. |
The write of the nonvolatile configuration failed because an internal variable was not set properly. |
- |
"If this messages occurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-CONFIG_NV_DATA |
3-Error |
Variable [chars] not set properly in the routine [chars]. |
The write of the nonvolatile configuration failed because an internal variable was not set properly. |
- |
"If this messages occurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-CPUHOG |
3-Error |
Task is running for [dec]msecs more than [dec]msecs [dec]/[dec] |
The indicated process ran too long without relinquishing the processor. Each process should run for a small amount of time and then relinquish the CPU so that other processes can run. This problem can be caused by many things like traffic or system load hardware or operational configuration a configuration change initialization of many interfaces cards or ports for example a high momentary error rate a sustained abnormal |
If this error occurs in conjunction with a TIMERHOG message \n\ report the two errors together and use the component obtained \n\ for the TIMERHOG message. |
"If you suspect a software error copy the error message exactly as it " "appears on the console or in the system log contact your technical support" "representative and provide the representative with the gathered information." |
|
SYS-3-CPUHOG |
3-Error |
Task is running for [dec]msecs more than [dec]msecs [dec]/[dec] |
The indicated process ran too long without relinquishing the processor. Each process should run for a small amount of time and then relinquish the CPU so that other processes can run. This problem can be caused by many things like traffic or system load hardware or operational configuration a configuration change initialization of many interfaces cards or ports for example a high momentary error rate a sustained abnormal |
If this error occurs in conjunction with a TIMERHOG message \n\ report the two errors together and use the component obtained \n\ for the TIMERHOG message. |
"If you suspect a software error copy the error message exactly as it " "appears on the colsole or in the system log contact your technical support" "representative and provide the representative with the gathered information." |
|
SYS-3-CPUHOG |
3-Error |
Task is running for [dec]msecs more than [dec]msecs [dec]/[dec] |
The indicated process ran too long without relinquishing the processor. Each process should run for a small amount of time and then relinquish the CPU so that other processes can run. This problem can be caused by many things like traffic or system load hardware or operational configuration a configuration change initialization of many interfaces cards or ports for example a high momentary error rate a sustained abnormal |
If this error occurs in conjunction with a TIMERHOG message \n\ report the two errors together and use the component obtained \n\ for the TIMERHOG message. |
"If you suspect a software error copy the error message exactly as it " "appears on the colsole or in the system log contact your technical support" "representative and provide the representative with the gathered information." |
|
SYS-3-CPUHOG |
3-Error |
Task is running for [dec]msecs more than [dec]msecs [dec]/[dec] |
The indicated process ran too long without relinquishing the processor. Each process should run for a small amount of time and then relinquish the CPU so that other processes can run. This problem can be caused by many things like traffic or system load hardware or operational configuration a configuration change initialization of many interfaces cards or ports for example a high momentary error rate a sustained abnormal |
If this error occurs in conjunction with a TIMERHOG message \n\ report the two errors together and use the component obtained \n\ for the TIMERHOG message. |
"If you suspect a software error copy the error message exactly as it " "appears on the colsole or in the system log contact your technical support" "representative and provide the representative with the gathered information." |
|
SYS-3-CPUHOG |
3-Error |
Task is running for [dec]msecs more than [dec]msecs [dec]/[dec] |
The indicated process ran too long without relinquishing the processor. Each process should run for a small amount of time and then relinquish the CPU so that other processes can run. This problem can be caused by many things like traffic or system load hardware or operational configuration a configuration change initialization of many interfaces cards or ports for example a high momentary error rate a sustained abnormal |
If this error occurs in conjunction with a TIMERHOG message \n\ report the two errors together and use the component obtained \n\ for the TIMERHOG message. |
"If you suspect a software error copy the error message exactly as it " "appears on the colsole or in the system log contact your technical support" "representative and provide the representative with the gathered information." |
|
SYS-3-CPUHOG |
3-Error |
Task is running for [dec]msecs more than [dec]msecs [dec]/[dec] |
The indicated process ran too long without relinquishing the processor. Each process should run for a small amount of time and then relinquish the CPU so that other processes can run. This problem can be caused by many things like traffic or system load hardware or operational configuration a configuration change initialization of many interfaces cards or ports for example a high momentary error rate a sustained abnormal |
If this error occurs in conjunction with a TIMERHOG message \n\ report the two errors together and use the component obtained \n\ for the TIMERHOG message. |
"If you suspect a software error copy the error message exactly as it " "appears on the colsole or in the system log contact your technical support" "representative and provide the representative with the gathered information." |
|
SYS-3-CRASHINFOINITFAIL |
3-Error |
Crashinfo subsys initialization did not add registry \n\ crashinfo_get_default_file_name.\n |
In order to figure out the device which the crashinfo writes to the crashinfo subsys has to add the registry crashinfo_get_default_file_name. |
- |
"Use Topic to search for a similar DDTS. If you find none write " "a DDTS for this problem. This SHOULD never happen - it is an " "indication of a bug elsewhere in the code." |
|
SYS-3-CRASHINFOINITFAIL |
3-Error |
Crashinfo subsys initialization did not add registry \n\ crashinfo_get_default_file_name.\n |
In order to figure out the device which the crashinfo writes to the crashinfo subsys has to add the registry crashinfo_get_default_file_name. |
- |
"Use Topic to search for a similar DDTS. If you find none write " "a DDTS for this problem. This SHOULD never happen - it is an " "indication of a bug elsewhere in the code." |
|
SYS-3-CRASHINFOINITFAIL |
3-Error |
Crashinfo subsys initialization did not add registry \n\ crashinfo_get_default_file_name.\n |
In order to figure out the device which the crashinfo writes to the crashinfo subsys has to add the registry crashinfo_get_default_file_name. |
- |
"Use Topic to search for a similar DDTS. If you find none write " "a DDTS for this problem. This SHOULD never happen - it is an " "indication of a bug elsewhere in the code." |
|
SYS-3-CRASHINFOINITFAIL |
3-Error |
Crashinfo subsys initialization did not add registry \n\ crashinfo_get_default_file_name.\n |
In order to figure out the device which the crashinfo writes to the crashinfo subsys has to add the registry crashinfo_get_default_file_name. |
- |
"Use Topic to search for a similar DDTS. If you find none write " "a DDTS for this problem. This SHOULD never happen - it is an " "indication of a bug elsewhere in the code." |
|
SYS-3-CRASHINFOINITFAIL |
3-Error |
Crashinfo subsys initialization did not add registry \n\ crashinfo_get_default_file_name.\n |
In order to figure out the device which the crashinfo writes to the crashinfo subsys has to add the registry crashinfo_get_default_file_name. |
- |
"Use Topic to search for a similar DDTS. If you find none write " "a DDTS for this problem. This SHOULD never happen - it is an " "indication of a bug elsewhere in the code." |
|
SYS-3-CRASHINFOINITFAIL |
3-Error |
Crashinfo subsys initialization did not add registry \n\ crashinfo_get_default_file_name.\n |
In order to figure out the device which the crashinfo writes to the crashinfo subsys has to add the registry crashinfo_get_default_file_name. |
- |
"Use Topic to search for a similar DDTS. If you find none write " "a DDTS for this problem. This SHOULD never happen - it is an " "indication of a bug elsewhere in the code." |
|
SYS-3-CRITMEM |
3-Error |
[chars] |
An attempt to allow or disallow a process from using memory that has been reserved for critical purposes has failed. The location of the failure is specified in the error message. This condition could possibly be caused by a software error. |
mem-suspect |
"Copy the error message and the traceback messages exactly as they appear " "on the console or in the system log contact your technical support " "representative and provide the representative with the gathered " "information." |
|
SYS-3-CRITMEM |
3-Error |
[chars] |
An attempt to allow or disallow a process from using memory that has been reserved for critical purposes has failed. The location of the failure is specified in the error message. This condition could possibly be caused by a software error. |
mem-suspect |
"Copy the error message and the traceback messages exactly as they appear " "on the colsole or in the system log contact your technical support " "representative and provide the representative with the gathered " "information." |
|
SYS-3-CRITMEM |
3-Error |
[chars] |
An attempt to allow or disallow a process from using memory that has been reserved for critical purposes has failed. The location of the failure is specified in the error message. This condition could possibly be caused by a software error. |
mem-suspect |
"Copy the error message and the traceback messages exactly as they appear " "on the colsole or in the system log contact your technical support " "representative and provide the representative with the gathered " "information." |
|
SYS-3-CRITMEM |
3-Error |
[chars] |
An attempt to allow or disallow a process from using memory that has been reserved for critical purposes has failed. The location of the failure is specified in the error message. This condition could possibly be caused by a software error. |
mem-suspect |
"Copy the error message and the traceback messages exactly as they appear " "on the colsole or in the system log contact your technical support " "representative and provide the representative with the gathered " "information." |
|
SYS-3-CRITMEM |
3-Error |
[chars] |
An attempt to allow or disallow a process from using memory that has been reserved for critical purposes has failed. The location of the failure is specified in the error message. This condition could possibly be caused by a software error. |
mem-suspect |
"Copy the error message and the traceback messages exactly as they appear " "on the colsole or in the system log contact your technical support " "representative and provide the representative with the gathered " "information." |
|
SYS-3-CRITMEM |
3-Error |
[chars] |
An attempt to allow or disallow a process from using memory that has been reserved for critical purposes has failed. The location of the failure is specified in the error message. This condition could possibly be caused by a software error. |
mem-suspect |
"Copy the error message and the traceback messages exactly as they appear " "on the colsole or in the system log contact your technical support " "representative and provide the representative with the gathered " "information." |
|
SYS-3-DMPMEM |
3-Error |
%08x: %08x %08x %08x %08x %08x %08x |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-DMPMEM |
3-Error |
%08x: %08x %08x %08x %08x %08x %08x |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-DMPMEM |
3-Error |
%08x: %08x %08x %08x %08x %08x %08x |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-DMPMEM |
3-Error |
%08x: %08x %08x %08x %08x %08x %08x |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-DMPMEM |
3-Error |
%08x: %08x %08x %08x %08x %08x %08x |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-DMPMEM |
3-Error |
%08x: %08x %08x %08x %08x %08x %08x |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-DUP_TIMER |
3-Error |
Same tty[t-line] in linewatch_timers type [dec] |
A tty appeared twice in a timer list where it should have only appeared once. |
exec |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-DUP_TIMER |
3-Error |
Same tty[t-line] in linewatch_timers type [dec] |
A tty appeared twice in a timer list where it should have only appeared once. |
exec |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-DUP_TIMER |
3-Error |
Same tty[t-line] in linewatch_timers type [dec] |
A tty appeared twice in a timer list where it should have only appeared once. |
exec |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-DUP_TIMER |
3-Error |
Same tty[t-line] in linewatch_timers type [dec] |
A tty appeared twice in a timer list where it should have only appeared once. |
exec |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-DUP_TIMER |
3-Error |
Same tty[t-line] in linewatch_timers type [dec] |
A tty appeared twice in a timer list where it should have only appeared once. |
exec |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-DUP_TIMER |
3-Error |
Same tty[t-line] in linewatch_timers type [dec] |
A tty appeared twice in a timer list where it should have only appeared once. |
exec |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-GD_STACKERR |
3-Error |
Unknown stack. Process: [chars]\n |
An internal error occurred when running the memory leak detector |
mem |
"Copy the error message exactly as it appears on the console or in the" " system log and look up the message in the Bug Toolkit at:" " http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you are" " unable to resolve the issue using Bug Toolkit please issue a" " \"show tech\" and contact your technical support representative" " with the gathered information." |
|
SYS-3-GD_STACKERR |
3-Error |
Unknown stack. Process: [chars]\n |
An internal error occurred when running the memory leak detector |
mem |
"Copy the error message exactly as it appears on the console or in the" " system log and look up the message in the Bug Toolkit at:" " http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you are" " unable to resolve the issue using Bug Toolkit please issue a" " \"show tech\" and contact your technical support representative" " with the gathered information." |
|
SYS-3-GD_STACKERR |
3-Error |
Unknown stack. Process: [chars]\n |
An internal error occurred when running the memory leak detector |
mem |
"Copy the error message exactly as it appears on the console or in the" " system log and look up the message in the Bug Toolkit at:" " http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you are" " unable to resolve the issue using Bug Toolkit please issue a" " \"show tech\" and contact your technical support representative" " with the gathered information." |
|
SYS-3-GD_STACKERR |
3-Error |
Unknown stack. Process: [chars]\n |
An internal error occurred when running the memory leak detector |
mem |
"Copy the error message exactly as it appears on the console or in the" " system log and look up the message in the Bug Toolkit at:" " http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you are" " unable to resolve the issue using Bug Toolkit please issue a" " \"show tech\" and contact your technical support representative" " with the gathered information." |
|
SYS-3-GD_STACKERR |
3-Error |
Unknown stack. Process: [chars]\n |
An internal error occurred when running the memory leak detector |
mem |
"Copy the error message exactly as it appears on the console or in the" " system log and look up the message in the Bug Toolkit at:" " http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you are" " unable to resolve the issue using Bug Toolkit please issue a" " \"show tech\" and contact your technical support representative" " with the gathered information." |
|
SYS-3-GD_STACKERR |
3-Error |
Unknown stack. Process: [chars]\n |
An internal error occurred when running the memory leak detector |
mem |
"Copy the error message exactly as it appears on the console or in the" " system log and look up the message in the Bug Toolkit at:" " http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you are" " unable to resolve the issue using Bug Toolkit please issue a" " \"show tech\" and contact your technical support representative" " with the gathered information." |
|
SYS-3-HARIKARI |
3-Error |
Process [chars] top-level routine exited |
An internal software error occurred |
Determine the component from the process name displayed in the error message. |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-HARIKARI |
3-Error |
Process [chars] top-level routine exited |
An internal software error occurred |
Determine the component from the process name displayed in the error message. |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-HARIKARI |
3-Error |
Process [chars] top-level routine exited |
An internal software error occurred |
Determine the component from the process name displayed in the error message. |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-HARIKARI |
3-Error |
Process [chars] top-level routine exited |
An internal software error occurred |
Determine the component from the process name displayed in the error message. |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-HARIKARI |
3-Error |
Process [chars] top-level routine exited |
An internal software error occurred |
Determine the component from the process name displayed in the error message. |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-HARIKARI |
3-Error |
Process [chars] top-level routine exited |
An internal software error occurred |
Determine the component from the process name displayed in the error message. |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-HTIMER_EXPAND |
3-Error |
timer heap at 0x[hec] needed to expand but hasn't |
A timer heap should have expanded but has not |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-HTIMER_EXPAND |
3-Error |
timer heap at 0x[hec] needed to expand but hasn't |
A timer heap should have expanded but has not |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-HTIMER_EXPAND |
3-Error |
timer heap at 0x[hec] needed to expand but hasn't |
A timer heap should have expanded but has not |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-HTIMER_EXPAND |
3-Error |
timer heap at 0x[hec] needed to expand but hasn't |
A timer heap should have expanded but has not |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-HTIMER_EXPAND |
3-Error |
timer heap at 0x[hec] needed to expand but hasn't |
A timer heap should have expanded but has not |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-HTIMER_EXPAND |
3-Error |
timer heap at 0x[hec] needed to expand but hasn't |
A timer heap should have expanded but has not |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-HTIMER_INIT |
3-Error |
heap timer at 0x[hec] has not been initialized |
A heap timer has not been initialized |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-HTIMER_INIT |
3-Error |
heap timer at 0x[hec] has not been initialized |
A heap timer has not been initialized |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-HTIMER_INIT |
3-Error |
heap timer at 0x[hec] has not been initialized |
A heap timer has not been initialized |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-HTIMER_INIT |
3-Error |
heap timer at 0x[hec] has not been initialized |
A heap timer has not been initialized |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-HTIMER_INIT |
3-Error |
heap timer at 0x[hec] has not been initialized |
A heap timer has not been initialized |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-HTIMER_INIT |
3-Error |
heap timer at 0x[hec] has not been initialized |
A heap timer has not been initialized |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-HTIMER_STATE |
3-Error |
heap timer at 0x[hec] in state [dec] |
A heap timer has not been initialized |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-HTIMER_STATE |
3-Error |
heap timer at 0x[hec] in state [dec] |
A heap timer has not been initialized |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-HTIMER_STATE |
3-Error |
heap timer at 0x[hec] in state [dec] |
A heap timer has not been initialized |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-HTIMER_STATE |
3-Error |
heap timer at 0x[hec] in state [dec] |
A heap timer has not been initialized |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-HTIMER_STATE |
3-Error |
heap timer at 0x[hec] in state [dec] |
A heap timer has not been initialized |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-HTIMER_STATE |
3-Error |
heap timer at 0x[hec] in state [dec] |
A heap timer has not been initialized |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-IMAGE_TOO_BIG |
3-Error |
'[chars]' is too large for available memory [dec] bytes. |
The allocated memory for the image is too small to hold the image file. |
- |
"Increase the amount of memory available in the router by booting " "with a smaller image not enabling non-essential sub-systems " "or upgrading the installed memory. Call your technical " "support representative for assistance." |
|
SYS-3-IMAGE_TOO_BIG |
3-Error |
'[chars]' is too large for available memory [dec] bytes. |
The allocated memory for the image is too small to hold the image file. |
- |
"Increase the amount of memory available in the router by booting " "with a smaller image not enabling non-essential sub-systems " "or upgrading the installed memory. Call your technical " "support representative for assistance." |
|
SYS-3-IMAGE_TOO_BIG |
3-Error |
'[chars]' is too large for available memory [dec] bytes. |
The allocated memory for the image is too small to hold the image file. |
- |
"Increase the amount of memory available in the router by booting " "with a smaller image not enabling non-essential sub-systems " "or upgrading the installed memory. Call your technical " "support representative for assistance." |
|
SYS-3-IMAGE_TOO_BIG |
3-Error |
'[chars]' is too large for available memory [dec] bytes. |
The allocated memory for the image is too small to hold the image file. |
- |
"Increase the amount of memory available in the router by booting " "with a smaller image not enabling non-essential sub-systems " "or upgrading the installed memory. Call your technical " "support representative for assistance." |
|
SYS-3-IMAGE_TOO_BIG |
3-Error |
'[chars]' is too large for available memory [dec] bytes. |
The allocated memory for the image is too small to hold the image file. |
- |
"Increase the amount of memory available in the router by booting " "with a smaller image not enabling non-essential sub-systems " "or upgrading the installed memory. Call your technical " "support representative for assistance." |
|
SYS-3-IMAGE_TOO_BIG |
3-Error |
'[chars]' is too large for available memory [dec] bytes. |
The allocated memory for the image is too small to hold the image file. |
- |
"Increase the amount of memory available in the router by booting " "with a smaller image not enabling non-essential sub-systems " "or upgrading the installed memory. Call your technical " "support representative for assistance." |
|
SYS-3-INTPRINT |
3-Error |
Illegal printing attempt from interrupt level. |
An internal software error occurred. |
Determine the component from the stack trace and process name\n\ displayed in the error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. If the stack trace indicates that the\n\ buffer code was called from an interrupt handler use the interrupt\n\ handler to determine the DDTS component. Otherwise use the process\n\ name to determine the DDTS component. |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-INTPRINT |
3-Error |
Illegal printing attempt from interrupt level. |
An internal software error occurred. |
Determine the component from the stack trace and process name\n\ displayed in the error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. If the stack trace indicates that the\n\ buffer code was called from an interrupt handler use the interrupt\n\ handler to determine the DDTS component. Otherwise use the process\n\ name to determine the DDTS component. |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-INTPRINT |
3-Error |
Illegal printing attempt from interrupt level. |
An internal software error occurred. |
Determine the component from the stack trace and process name\n\ displayed in the error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. If the stack trace indicates that the\n\ buffer code was called from an interrupt handler use the interrupt\n\ handler to determine the DDTS component. Otherwise use the process\n\ name to determine the DDTS component. |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-INTPRINT |
3-Error |
Illegal printing attempt from interrupt level. |
An internal software error occurred. |
Determine the component from the stack trace and process name\n\ displayed in the error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. If the stack trace indicates that the\n\ buffer code was called from an interrupt handler use the interrupt\n\ handler to determine the DDTS component. Otherwise use the process\n\ name to determine the DDTS component. |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-INTPRINT |
3-Error |
Illegal printing attempt from interrupt level. |
An internal software error occurred. |
Determine the component from the stack trace and process name\n\ displayed in the error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. If the stack trace indicates that the\n\ buffer code was called from an interrupt handler use the interrupt\n\ handler to determine the DDTS component. Otherwise use the process\n\ name to determine the DDTS component. |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-INTPRINT |
3-Error |
Illegal printing attempt from interrupt level. |
An internal software error occurred. |
Determine the component from the stack trace and process name\n\ displayed in the error message. \n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. If the stack trace indicates that the\n\ buffer code was called from an interrupt handler use the interrupt\n\ handler to determine the DDTS component. Otherwise use the process\n\ name to determine the DDTS component. |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-INTUNWEDGE |
3-Error |
%llu packets where forcefully unwedged %llu packets were forcefully deallocated |
This is an auxiliary message to indicate that packet buffers were\n forcefully deallcoated/unaccounted from interfaces through CLI. |
Include this error message in any other DDTS that was written for\n any other problems reported on this router after leak debugging\n was configured. |
"This message is to explicitly notify that packets were forcefully\n" "deallocated/unaccounted. If the router is facing other problems\n" "for which you are contacting your technical support representative\n" "copy this error message to as it appears and provide this information\n" "too." |
|
SYS-3-INUSEFREE |
3-Error |
Block [hec] on free list [dec] in use |
A memory management function attempted to allocate the indicated block from a list of free blocks. However the block was found to be already in use. |
- |
- |
|
SYS-3-INUSEFREE |
3-Error |
Block [hec] on free list [dec] in use |
A memory management function attempted to allocate the indicated block from a list of free blocks. However the block was found to be already in use. |
- |
- |
|
SYS-3-INUSEFREE |
3-Error |
Block [hec] on free list [dec] in use |
A memory management function attempted to allocate the indicated block from a list of free blocks. However the block was found to be already in use. |
- |
- |
|
SYS-3-INUSEFREE |
3-Error |
Block [hec] on free list [dec] in use |
A memory management function attempted to allocate the indicated block from a list of free blocks. However the block was found to be already in use. |
- |
- |
|
SYS-3-INUSEFREE |
3-Error |
Block [hec] on free list [dec] in use |
A memory management function attempted to allocate the indicated block from a list of free blocks. However the block was found to be already in use. |
- |
- |
|
SYS-3-INUSEFREE |
3-Error |
Block [hec] on free list [dec] in use |
A memory management function attempted to allocate the indicated block from a list of free blocks. However the block was found to be already in use. |
- |
- |
|
SYS-3-INVMEMINT |
3-Error |
Invalid memory action [chars] at interrupt level |
This message indicates that a memory allocation or deallocation was attempted from an interrupt handler. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-INVMEMINT |
3-Error |
Invalid memory action [chars] at interrupt level |
This message indicates that a memory allocation or deallocation was attempted from an interrupt handler. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-INVMEMINT |
3-Error |
Invalid memory action [chars] at interrupt level |
This message indicates that a memory allocation or deallocation was attempted from an interrupt handler. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-INVMEMINT |
3-Error |
Invalid memory action [chars] at interrupt level |
This message indicates that a memory allocation or deallocation was attempted from an interrupt handler. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-INVMEMINT |
3-Error |
Invalid memory action [chars] at interrupt level |
This message indicates that a memory allocation or deallocation was attempted from an interrupt handler. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-INVMEMINT |
3-Error |
Invalid memory action [chars] at interrupt level |
This message indicates that a memory allocation or deallocation was attempted from an interrupt handler. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-INVMEMPID |
3-Error |
Invalid pid [dec] in block: [hec] |
There has been attempt to allocate memory on behalf of an invalid process. |
mem |
- |
|
SYS-3-INVMEMPID |
3-Error |
Invalid pid [dec] in block: [hec] |
There has been attempt to allocate memory on behalf of an invalid process. |
mem |
- |
|
SYS-3-INVMEMPID |
3-Error |
Invalid pid [dec] in block: [hec] |
There has been attempt to allocate memory on behalf of an invalid process. |
mem |
- |
|
SYS-3-INVMEMPID |
3-Error |
Invalid pid [dec] in block: [hec] |
There has been attempt to allocate memory on behalf of an invalid process. |
mem |
- |
|
SYS-3-INVMEMPID |
3-Error |
Invalid pid [dec] in block: [hec] |
There has been attempt to allocate memory on behalf of an invalid process. |
mem |
- |
|
SYS-3-INVMEMPID |
3-Error |
Invalid pid [dec] in block: [hec] |
There has been attempt to allocate memory on behalf of an invalid process. |
mem |
- |
|
SYS-3-LOGGER_COUNT_STOP_CHUNK |
3-Error |
System cannot release chunk memory.\n |
The system was not able to destroy a previously allocated chunk of memory. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-LOGGER_COUNT_STOP_CHUNK |
3-Error |
System cannot release chunk memory.\n |
The system was not able to destroy a previously allocated chunk of memory. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-LOGGER_COUNT_STOP_CHUNK |
3-Error |
System cannot release chunk memory.\n |
The system was not able to destroy a previously allocated chunk of memory. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-LOGGER_COUNT_STOP_CHUNK |
3-Error |
System cannot release chunk memory.\n |
The system was not able to destroy a previously allocated chunk of memory. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-LOGGER_COUNT_STOP_CHUNK |
3-Error |
System cannot release chunk memory.\n |
The system was not able to destroy a previously allocated chunk of memory. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-LOGGER_COUNT_STOP_CHUNK |
3-Error |
System cannot release chunk memory.\n |
The system was not able to destroy a previously allocated chunk of memory. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-LOGGER_DROPPED |
3-Error |
System dropped [dec] console debug messages.\n |
Debugging or informational messages are being generated faster than they can be displayed on the console. The messages can not be guaranteed to be seen so this message replaces the lost messages. |
- |
"Consider using conditional debugging or turning off console logging." |
|
SYS-3-LOGGER_DROPPED |
3-Error |
System dropped [dec] console debug messages.\n |
Debugging or informational messages are being generated faster than they can be displayed on the console. The messages can not be guaranteed to be seen so this message replaces the lost messages. |
- |
"Consider using conditional debugging or turning off console logging." |
|
SYS-3-LOGGER_DROPPED |
3-Error |
System dropped [dec] console debug messages.\n |
Debugging or informational messages are being generated faster than they can be displayed on the console. The messages can not be guaranteed to be seen so this message replaces the lost messages. |
- |
"Consider using conditional debugging or turning off console logging." |
|
SYS-3-LOGGER_DROPPED |
3-Error |
System dropped [dec] console debug messages.\n |
Debugging or informational messages are being generated faster than they can be displayed on the console. The messages can not be guaranteed to be seen so this message replaces the lost messages. |
- |
"Consider using conditional debugging or turning off console logging." |
|
SYS-3-LOGGER_DROPPED |
3-Error |
System dropped [dec] console debug messages.\n |
Debugging or informational messages are being generated faster than they can be displayed on the console. The messages can not be guaranteed to be seen so this message replaces the lost messages. |
- |
"Consider using conditional debugging or turning off console logging." |
|
SYS-3-LOGGER_DROPPED |
3-Error |
System dropped [dec] console debug messages.\n |
Debugging or informational messages are being generated faster than they can be displayed on the console. The messages can not be guaranteed to be seen so this message replaces the lost messages. |
- |
"Consider using conditional debugging or turning off console logging." |
|
SYS-3-LOGGER_FLUSHED |
3-Error |
System was paused for %TE to ensure console debugging output.\n |
Debugging or informational messages are being generated faster than they can be displayed on the console. In order to guarantee that they can be seen the rest of the system was paused until the console output catches up. This can break time-critical behavior such as maintaining an ISDN link. |
- |
"Consider using conditional debugging turning off console logging " "or using the \"no logging console guaranteed\" command or turning " "off link-state messages for some interfaces" |
|
SYS-3-LOGGER_FLUSHED |
3-Error |
System was paused for %TE to ensure console debugging output.\n |
Debugging or informational messages are being generated faster than they can be displayed on the console. In order to guarantee that they can be seen the rest of the system was paused until the console output catches up. This can break time-critical behavior such as maintaining an ISDN link. |
- |
"Consider using conditional debugging turning off console logging " "or using the \"no logging console guaranteed\" command or turning " "off link-state messages for some interfaces" |
|
SYS-3-LOGGER_FLUSHED |
3-Error |
System was paused for %TE to ensure console debugging output.\n |
Debugging or informational messages are being generated faster than they can be displayed on the console. In order to guarantee that they can be seen the rest of the system was paused until the console output catches up. This can break time-critical behavior such as maintaining an ISDN link. |
- |
"Consider using conditional debugging turning off console logging " "or using the \"no logging console guaranteed\" command or turning " "off link-state messages for some interfaces" |
|
SYS-3-LOGGER_FLUSHED |
3-Error |
System was paused for %TE to ensure console debugging output.\n |
Debugging or informational messages are being generated faster than they can be displayed on the console. In order to guarantee that they can be seen the rest of the system was paused until the console output catches up. This can break time-critical behavior such as maintaining an ISDN link. |
- |
"Consider using conditional debugging turning off console logging " "or using the \"no logging console guaranteed\" command or turning " "off link-state messages for some interfaces" |
|
SYS-3-LOGGER_FLUSHED |
3-Error |
System was paused for %TE to ensure console debugging output.\n |
Debugging or informational messages are being generated faster than they can be displayed on the console. In order to guarantee that they can be seen the rest of the system was paused until the console output catches up. This can break time-critical behavior such as maintaining an ISDN link. |
- |
"Consider using conditional debugging turning off console logging " "or using the \"no logging console guaranteed\" command or turning " "off link-state messages for some interfaces" |
|
SYS-3-LOGGER_FLUSHED |
3-Error |
System was paused for %TE to ensure console debugging output.\n |
Debugging or informational messages are being generated faster than they can be displayed on the console. In order to guarantee that they can be seen the rest of the system was paused until the console output catches up. This can break time-critical behavior such as maintaining an ISDN link. |
- |
"Consider using conditional debugging turning off console logging " "or using the \"no logging console guaranteed\" command or turning " "off link-state messages for some interfaces" |
|
SYS-3-LOGGER_FLUSHING |
3-Error |
System pausing to ensure console debugging output.\n |
Debugging or informational messages are being generated faster than they can be displayed on the console. In order to guarantee that they can be seen the rest of the system is paused until the console output catches up. This can break time-critical behavior such as maintaining an ISDN link. |
- |
"Consider using conditional debugging turning off console logging " "or using the \"no logging console guaranteed\" command or turning " "off link-state messages for some interfaces" |
|
SYS-3-LOGGER_FLUSHING |
3-Error |
System pausing to ensure console debugging output.\n |
Debugging or informational messages are being generated faster than they can be displayed on the console. In order to guarantee that they can be seen the rest of the system is paused until the console output catches up. This can break time-critical behavior such as maintaining an ISDN link. |
- |
"Consider using conditional debugging turning off console logging " "or using the \"no logging console guaranteed\" command or turning " "off link-state messages for some interfaces" |
|
SYS-3-LOGGER_FLUSHING |
3-Error |
System pausing to ensure console debugging output.\n |
Debugging or informational messages are being generated faster than they can be displayed on the console. In order to guarantee that they can be seen the rest of the system is paused until the console output catches up. This can break time-critical behavior such as maintaining an ISDN link. |
- |
"Consider using conditional debugging turning off console logging " "or using the \"no logging console guaranteed\" command or turning " "off link-state messages for some interfaces" |
|
SYS-3-LOGGER_FLUSHING |
3-Error |
System pausing to ensure console debugging output.\n |
Debugging or informational messages are being generated faster than they can be displayed on the console. In order to guarantee that they can be seen the rest of the system is paused until the console output catches up. This can break time-critical behavior such as maintaining an ISDN link. |
- |
"Consider using conditional debugging turning off console logging " "or using the \"no logging console guaranteed\" command or turning " "off link-state messages for some interfaces" |
|
SYS-3-LOGGER_FLUSHING |
3-Error |
System pausing to ensure console debugging output.\n |
Debugging or informational messages are being generated faster than they can be displayed on the console. In order to guarantee that they can be seen the rest of the system is paused until the console output catches up. This can break time-critical behavior such as maintaining an ISDN link. |
- |
"Consider using conditional debugging turning off console logging " "or using the \"no logging console guaranteed\" command or turning " "off link-state messages for some interfaces" |
|
SYS-3-LOGGER_FLUSHING |
3-Error |
System pausing to ensure console debugging output.\n |
Debugging or informational messages are being generated faster than they can be displayed on the console. In order to guarantee that they can be seen the rest of the system is paused until the console output catches up. This can break time-critical behavior such as maintaining an ISDN link. |
- |
"Consider using conditional debugging turning off console logging " "or using the \"no logging console guaranteed\" command or turning " "off link-state messages for some interfaces" |
|
SYS-3-LOGGINGHOST_CONNECTFAIL |
3-Error |
Unable to setup connection with host [chars] port [dec] |
Unable to setup a connection with specified server or hostvrf check weather the syslog host is reachable |
os-logging |
LOG_STD_NO_ACTION |
|
SYS-3-LOGGINGHOST_FAIL |
3-Error |
Logging to host [chars] port [dec] failed \n |
Logging syslog messages to specified server or host failed please check if the host is configured properly and reachable |
os-logging |
LOG_STD_NO_ACTION |
|
SYS-3-MEMLITE |
3-Error |
Free lite called for non lite chunk by '%p' |
Memory lite error: free_lite_internal is passed a non lite chunk |
mem |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
SYS-3-MEMSEMFAIL |
3-Error |
Mempool semaphore creation failed for [chars] |
This message indicates that the semaphore creation for the specified mempool failed. |
- |
- |
|
SYS-3-MEMSEMFAIL |
3-Error |
Mempool semaphore creation failed for [chars] |
This message indicates that the semaphore creation for the specified mempool failed. |
- |
- |
|
SYS-3-MEMSEMFAIL |
3-Error |
Mempool semaphore creation failed for [chars] |
This message indicates that the semaphore creation for the specified mempool failed. |
- |
- |
|
SYS-3-MEMSEMFAIL |
3-Error |
Mempool semaphore creation failed for [chars] |
This message indicates that the semaphore creation for the specified mempool failed. |
- |
- |
|
SYS-3-MEMSEMFAIL |
3-Error |
Mempool semaphore creation failed for [chars] |
This message indicates that the semaphore creation for the specified mempool failed. |
- |
- |
|
SYS-3-MEMSEMFAIL |
3-Error |
Mempool semaphore creation failed for [chars] |
This message indicates that the semaphore creation for the specified mempool failed. |
- |
- |
|
SYS-3-MEMSUSPENDDISALLOW |
3-Error |
[chars] called with request to suspend when it cannot suspend |
A process which is currently in a state where it cannot relinquish the CPU invoked a memory management function that can relinquish control of the CPU |
Determine the component from the stack trace displayed in the error message. Use Topic to search for a similar DDTS. If you find none submit a DDTS for this problem. Choose the DDTS component associated with the routine that called the memory management function |
- |
|
SYS-3-MGDTIMER |
3-Error |
[chars][chars] timer = [hec]. |
This message indicates an error in a system timer. The problem can be caused either by software or by hardware. |
- |
- |
|
SYS-3-MGDTIMER |
3-Error |
[chars][chars] timer = [hec]. |
This message indicates an error in a system timer. The problem can be caused either by software or by hardware. |
- |
- |
|
SYS-3-MGDTIMER |
3-Error |
[chars][chars] timer = [hec]. |
This message indicates an error in a system timer. The problem can be caused either by software or by hardware. |
- |
- |
|
SYS-3-MGDTIMER |
3-Error |
[chars][chars] timer = [hec]. |
This message indicates an error in a system timer. The problem can be caused either by software or by hardware. |
- |
- |
|
SYS-3-MGDTIMER |
3-Error |
[chars][chars] timer = [hec]. |
This message indicates an error in a system timer. The problem can be caused either by software or by hardware. |
- |
- |
|
SYS-3-MGDTIMER |
3-Error |
[chars][chars] timer = [hec]. |
This message indicates an error in a system timer. The problem can be caused either by software or by hardware. |
- |
- |
|
SYS-3-MGDTMRRUN |
3-Error |
TTY[t-line]: Managed Timers [chars] still running |
One or more managed timers for a TTY that is deleted are still running. |
- |
LOG_STD_ACTION |
|
SYS-3-MGDTMRRUN |
3-Error |
TTY[t-line]: Managed Timers [chars] still running |
One or more managed timers for a TTY that is deleted are still running. |
- |
LOG_STD_ACTION |
|
SYS-3-MGDTMRRUN |
3-Error |
TTY[t-line]: Managed Timers [chars] still running |
One or more managed timers for a TTY that is deleted are still running. |
- |
LOG_STD_ACTION |
|
SYS-3-MGDTMRRUN |
3-Error |
TTY[t-line]: Managed Timers [chars] still running |
One or more managed timers for a TTY that is deleted are still running. |
- |
LOG_STD_ACTION |
|
SYS-3-MGDTMRRUN |
3-Error |
TTY[t-line]: Managed Timers [chars] still running |
One or more managed timers for a TTY that is deleted are still running. |
- |
LOG_STD_ACTION |
|
SYS-3-MGDTMRRUN |
3-Error |
TTY[t-line]: Managed Timers [chars] still running |
One or more managed timers for a TTY that is deleted are still running. |
- |
LOG_STD_ACTION |
|
SYS-3-MSGLOST |
3-Error |
[dec] messages lost because of queue overflow |
A software error occurred. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-3-MSGLOST |
3-Error |
[dec] messages lost because of queue overflow |
A software error occurred. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-3-MSGLOST |
3-Error |
[dec] messages lost because of queue overflow |
A software error occurred. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-3-MSGLOST |
3-Error |
[dec] messages lost because of queue overflow |
A software error occurred. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-3-MSGLOST |
3-Error |
[dec] messages lost because of queue overflow |
A software error occurred. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-3-MSGLOST |
3-Error |
[dec] messages lost because of queue overflow |
A software error occurred. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-3-NOELEMENT |
3-Error |
[chars]:Ran out of buffer elements for enqueue |
The process was unable to enqueue data as it ran out of buffer elements. |
- |
"Copy the error message exactly as it appears also get the " "output of show buffers and report it to your technical support " "representative." |
|
SYS-3-NOELEMENT |
3-Error |
[chars]:Ran out of buffer elements for enqueue |
The process was unable to enqueue data as it ran out of buffer elements. |
- |
"Copy the error message exactly as it appears also get the " "output of show buffers and report it to your technical support " "representative." |
|
SYS-3-NOELEMENT |
3-Error |
[chars]:Ran out of buffer elements for enqueue |
The process was unable to enqueue data as it ran out of buffer elements. |
- |
"Copy the error message exactly as it appears also get the " "output of show buffers and report it to your technical support " "representative." |
|
SYS-3-NOELEMENT |
3-Error |
[chars]:Ran out of buffer elements for enqueue |
The process was unable to enqueue data as it ran out of buffer elements. |
- |
"Copy the error message exactly as it appears also get the " "output of show buffers and report it to your technical support " "representative." |
|
SYS-3-NOELEMENT |
3-Error |
[chars]:Ran out of buffer elements for enqueue |
The process was unable to enqueue data as it ran out of buffer elements. |
- |
"Copy the error message exactly as it appears also get the " "output of show buffers and report it to your technical support " "representative." |
|
SYS-3-NOELEMENT |
3-Error |
[chars]:Ran out of buffer elements for enqueue |
The process was unable to enqueue data as it ran out of buffer elements. |
- |
"Copy the error message exactly as it appears also get the " "output of show buffers and report it to your technical support " "representative." |
|
SYS-3-NULLIDB |
3-Error |
Null IDB in [chars] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-NULLIDB |
3-Error |
Null IDB in [chars] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-NULLIDB |
3-Error |
Null IDB in [chars] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-NULLIDB |
3-Error |
Null IDB in [chars] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-NULLIDB |
3-Error |
Null IDB in [chars] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-NULLIDB |
3-Error |
Null IDB in [chars] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-NV_BOOTVAR_PARSE |
3-Error |
Failed to parse boot command:[chars] Error:[dec] |
Boot configuration failed to parse when copied to startup-config. Most likely reason would be syntax errors in the boot configuration. |
none |
"Decode the traceback and check configuration file for the boot " "commands. Boot commands are sandwiched between boot-start-marker " "and boot-end-marker" |
|
SYS-3-NZREFCNT |
3-Error |
Block [hec] on free list [dec] with refcount [dec] |
A block of memory in the free pool is actually in use. The message indicates the number of processes using the memory block. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-NZREFCNT |
3-Error |
Block [hec] on free list [dec] with refcount [dec] |
A block of memory in the free pool is actually in use. The message indicates the number of processes using the memory block. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-NZREFCNT |
3-Error |
Block [hec] on free list [dec] with refcount [dec] |
A block of memory in the free pool is actually in use. The message indicates the number of processes using the memory block. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-NZREFCNT |
3-Error |
Block [hec] on free list [dec] with refcount [dec] |
A block of memory in the free pool is actually in use. The message indicates the number of processes using the memory block. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-NZREFCNT |
3-Error |
Block [hec] on free list [dec] with refcount [dec] |
A block of memory in the free pool is actually in use. The message indicates the number of processes using the memory block. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-NZREFCNT |
3-Error |
Block [hec] on free list [dec] with refcount [dec] |
A block of memory in the free pool is actually in use. The message indicates the number of processes using the memory block. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-OVERRUN |
3-Error |
Block overrun at [hec] red zone %08x |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-OVERRUN |
3-Error |
Block overrun at [hec] red zone %08x |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-OVERRUN |
3-Error |
Block overrun at [hec] red zone %08x |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-OVERRUN |
3-Error |
Block overrun at [hec] red zone %08x |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-OVERRUN |
3-Error |
Block overrun at [hec] red zone %08x |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-OVERRUN |
3-Error |
Block overrun at [hec] red zone %08x |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-OVFPRINT |
3-Error |
Overflow in [chars] chars [dec] buffer size [dec] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-OVFPRINT |
3-Error |
Overflow in [chars] chars [dec] buffer size [dec] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-OVFPRINT |
3-Error |
Overflow in [chars] chars [dec] buffer size [dec] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-OVFPRINT |
3-Error |
Overflow in [chars] chars [dec] buffer size [dec] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-OVFPRINT |
3-Error |
Overflow in [chars] chars [dec] buffer size [dec] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-OVFPRINT |
3-Error |
Overflow in [chars] chars [dec] buffer size [dec] |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-PROCSEMFAIL |
3-Error |
Process semaphore creation for preemptive processes failed. |
Creation of process function semaphore to protect the critical section of process create routine failed. The semaphore creation can fail if there isnt enough chunk memory to create the event structure. |
os |
- |
|
SYS-3-PROCSEMFAIL |
3-Error |
Process semaphore creation for preemptive processes failed. |
Creation of process function semaphore to protect the critical section of process create routine failed. The semaphore creation can fail if there isnt enough chunk memory to create the event structure. |
os |
- |
|
SYS-3-PROCSEMFAIL |
3-Error |
Process semaphore creation for preemptive processes failed. |
Creation of process function semaphore to protect the critical section of process create routine failed. The semaphore creation can fail if there isnt enough chunk memory to create the event structure. |
os |
- |
|
SYS-3-PROCSEMFAIL |
3-Error |
Process semaphore creation for preemptive processes failed. |
Creation of process function semaphore to protect the critical section of process create routine failed. The semaphore creation can fail if there isnt enough chunk memory to create the event structure. |
os |
- |
|
SYS-3-PROCSEMFAIL |
3-Error |
Process semaphore creation for preemptive processes failed. |
Creation of process function semaphore to protect the critical section of process create routine failed. The semaphore creation can fail if there isnt enough chunk memory to create the event structure. |
os |
- |
|
SYS-3-PROCSEMFAIL |
3-Error |
Process semaphore creation for preemptive processes failed. |
Creation of process function semaphore to protect the critical section of process create routine failed. The semaphore creation can fail if there isnt enough chunk memory to create the event structure. |
os |
- |
|
SYS-3-RGADDFAIL |
3-Error |
Couldn't add process process pid [dec] to resource group [hec]\n Cause: [chars] |
An attempt to create a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGADDFAIL |
3-Error |
Couldn't add process process pid [dec] to resource group [hec]\n Cause: [chars] |
An attempt to create a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGADDFAIL |
3-Error |
Couldn't add process process pid [dec] to resource group [hec]\n Cause: [chars] |
An attempt to create a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGADDFAIL |
3-Error |
Couldn't add process process pid [dec] to resource group [hec]\n Cause: [chars] |
An attempt to create a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGADDFAIL |
3-Error |
Couldn't add process process pid [dec] to resource group [hec]\n Cause: [chars] |
An attempt to create a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGADDFAIL |
3-Error |
Couldn't add process process pid [dec] to resource group [hec]\n Cause: [chars] |
An attempt to create a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGCREATEFAIL |
3-Error |
Resource group creation failed\nCause: [chars] |
An attempt to create a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGCREATEFAIL |
3-Error |
Resource group creation failed\nCause: [chars] |
An attempt to create a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGCREATEFAIL |
3-Error |
Resource group creation failed\nCause: [chars] |
An attempt to create a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGCREATEFAIL |
3-Error |
Resource group creation failed\nCause: [chars] |
An attempt to create a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGCREATEFAIL |
3-Error |
Resource group creation failed\nCause: [chars] |
An attempt to create a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGCREATEFAIL |
3-Error |
Resource group creation failed\nCause: [chars] |
An attempt to create a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGDELEFAIL |
3-Error |
Couldn't delete process process pid [dec] from resource group\n \nCause: [chars] |
An attempt to remove a process from a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGDELEFAIL |
3-Error |
Couldn't delete process process pid [dec] from resource group\n \nCause: [chars] |
An attempt to remove a process from a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGDELEFAIL |
3-Error |
Couldn't delete process process pid [dec] from resource group\n \nCause: [chars] |
An attempt to remove a process from a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGDELEFAIL |
3-Error |
Couldn't delete process process pid [dec] from resource group\n \nCause: [chars] |
An attempt to remove a process from a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGDELEFAIL |
3-Error |
Couldn't delete process process pid [dec] from resource group\n \nCause: [chars] |
An attempt to remove a process from a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGDELEFAIL |
3-Error |
Couldn't delete process process pid [dec] from resource group\n \nCause: [chars] |
An attempt to remove a process from a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGDESTFAIL |
3-Error |
Couldn't destroy resource group [hec]\nCause: [chars] |
An attempt to destroy a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGDESTFAIL |
3-Error |
Couldn't destroy resource group [hec]\nCause: [chars] |
An attempt to destroy a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGDESTFAIL |
3-Error |
Couldn't destroy resource group [hec]\nCause: [chars] |
An attempt to destroy a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGDESTFAIL |
3-Error |
Couldn't destroy resource group [hec]\nCause: [chars] |
An attempt to destroy a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGDESTFAIL |
3-Error |
Couldn't destroy resource group [hec]\nCause: [chars] |
An attempt to destroy a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGDESTFAIL |
3-Error |
Couldn't destroy resource group [hec]\nCause: [chars] |
An attempt to destroy a resource group failed at the indicated location |
- |
- |
|
SYS-3-RGMEMEXCEED |
3-Error |
\nLimit Exceeded: [chars] Holding: %lu Requested:%lu bytes |
A resource group has requested for more memory than the configured limit at the indicated location |
The component to which the offending resource group belongs. |
- |
|
SYS-3-RGMEMEXCEED |
3-Error |
\nLimit Exceeded: [chars] Holding: %lu Requested:%lu bytes |
A resource group has requested for more memory than the configured limit at the indicated location |
The component to which the offending resource group belongs. |
- |
|
SYS-3-RGMEMEXCEED |
3-Error |
\nLimit Exceeded: [chars] Holding: %lu Requested:%lu bytes |
A resource group has requested for more memory than the configured limit at the indicated location |
The component to which the offending resource group belongs. |
- |
|
SYS-3-RGMEMEXCEED |
3-Error |
\nLimit Exceeded: [chars] Holding: %lu Requested:%lu bytes |
A resource group has requested for more memory than the configured limit at the indicated location |
The component to which the offending resource group belongs. |
- |
|
SYS-3-RGMEMEXCEED |
3-Error |
\nLimit Exceeded: [chars] Holding: %lu Requested:%lu bytes |
A resource group has requested for more memory than the configured limit at the indicated location |
The component to which the offending resource group belongs. |
- |
|
SYS-3-RGMEMEXCEED |
3-Error |
\nLimit Exceeded: [chars] Holding: %lu Requested:%lu bytes |
A resource group has requested for more memory than the configured limit at the indicated location |
The component to which the offending resource group belongs. |
- |
|
SYS-3-RGOPFAIL |
3-Error |
Requested memory thresholding operation on resource group failed\n Resource Group handle: [hec] Cause: [chars] |
The message indicates that an request to Set/Get memory thresholding data or enable/disable thresholding failed in the indicated location |
The component that issued the request |
- |
|
SYS-3-RGOPFAIL |
3-Error |
Requested memory thresholding operation on resource group failed\n Resource Group handle: [hec] Cause: [chars] |
The message indicates that an request to Set/Get memory thresholding data or enable/disable thresholding failed in the indicated location |
The component that issued the request |
- |
|
SYS-3-RGOPFAIL |
3-Error |
Requested memory thresholding operation on resource group failed\n Resource Group handle: [hec] Cause: [chars] |
The message indicates that an request to Set/Get memory thresholding data or enable/disable thresholding failed in the indicated location |
The component that issued the request |
- |
|
SYS-3-RGOPFAIL |
3-Error |
Requested memory thresholding operation on resource group failed\n Resource Group handle: [hec] Cause: [chars] |
The message indicates that an request to Set/Get memory thresholding data or enable/disable thresholding failed in the indicated location |
The component that issued the request |
- |
|
SYS-3-RGOPFAIL |
3-Error |
Requested memory thresholding operation on resource group failed\n Resource Group handle: [hec] Cause: [chars] |
The message indicates that an request to Set/Get memory thresholding data or enable/disable thresholding failed in the indicated location |
The component that issued the request |
- |
|
SYS-3-RGOPFAIL |
3-Error |
Requested memory thresholding operation on resource group failed\n Resource Group handle: [hec] Cause: [chars] |
The message indicates that an request to Set/Get memory thresholding data or enable/disable thresholding failed in the indicated location |
The component that issued the request |
- |
|
SYS-3-SOCKUNKN |
3-Error |
Unknown socket protocol [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-SOCKUNKN |
3-Error |
Unknown socket protocol [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-SOCKUNKN |
3-Error |
Unknown socket protocol [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-SOCKUNKN |
3-Error |
Unknown socket protocol [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-SOCKUNKN |
3-Error |
Unknown socket protocol [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-SOCKUNKN |
3-Error |
Unknown socket protocol [dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-TCLSETFAIL |
3-Error |
cannot set TCL interpreter variable '[chars]' to '[chars]' : '[chars]' |
The value could not be passed to the TCL interpreter |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-TCLSETFAIL |
3-Error |
cannot set TCL interpreter variable '[chars]' to '[chars]' : '[chars]' |
The value could not be passed to the TCL interpreter |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-TCLSETFAIL |
3-Error |
cannot set TCL interpreter variable '[chars]' to '[chars]' : '[chars]' |
The value could not be passed to the TCL interpreter |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-TCLSETFAIL |
3-Error |
cannot set TCL interpreter variable '[chars]' to '[chars]' : '[chars]' |
The value could not be passed to the TCL interpreter |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-TCLSETFAIL |
3-Error |
cannot set TCL interpreter variable '[chars]' to '[chars]' : '[chars]' |
The value could not be passed to the TCL interpreter |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-TCLSETFAIL |
3-Error |
cannot set TCL interpreter variable '[chars]' to '[chars]' : '[chars]' |
The value could not be passed to the TCL interpreter |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-TIMERHOG |
3-Error |
Timer callback ran long PC = [hec]. |
The indicated callback routine ran for too long without relinquishing the processor. |
Determine the component from the callback routine address displayed in\n\ the error message. Use Topic to search for a similar DDTS. If you \n\ find none write a DDTS for this problem. |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-3-TIMERHOG |
3-Error |
Timer callback ran long PC = [hec]. |
The indicated callback routine ran for too long without relinquishing the processor. |
Determine the component from the callback routine address displayed in\n\ the error message. Use Topic to search for a similar DDTS. If you \n\ find none write a DDTS for this problem. |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-3-TIMERHOG |
3-Error |
Timer callback ran long PC = [hec]. |
The indicated callback routine ran for too long without relinquishing the processor. |
Determine the component from the callback routine address displayed in\n\ the error message. Use Topic to search for a similar DDTS. If you \n\ find none write a DDTS for this problem. |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-3-TIMERHOG |
3-Error |
Timer callback ran long PC = [hec]. |
The indicated callback routine ran for too long without relinquishing the processor. |
Determine the component from the callback routine address displayed in\n\ the error message. Use Topic to search for a similar DDTS. If you \n\ find none write a DDTS for this problem. |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-3-TIMERHOG |
3-Error |
Timer callback ran long PC = [hec]. |
The indicated callback routine ran for too long without relinquishing the processor. |
Determine the component from the callback routine address displayed in\n\ the error message. Use Topic to search for a similar DDTS. If you \n\ find none write a DDTS for this problem. |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-3-TIMERHOG |
3-Error |
Timer callback ran long PC = [hec]. |
The indicated callback routine ran for too long without relinquishing the processor. |
Determine the component from the callback routine address displayed in\n\ the error message. Use Topic to search for a similar DDTS. If you \n\ find none write a DDTS for this problem. |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-3-TIMERNEG |
3-Error |
Cannot start timer [hex] with negative offset [dec]. |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-TIMERNEG |
3-Error |
Cannot start timer [hex] with negative offset [dec]. |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-TIMERNEG |
3-Error |
Cannot start timer [hex] with negative offset [dec]. |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-TIMERNEG |
3-Error |
Cannot start timer [hex] with negative offset [dec]. |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-TIMERNEG |
3-Error |
Cannot start timer [hex] with negative offset [dec]. |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-TIMERNEG |
3-Error |
Cannot start timer [hex] with negative offset [dec]. |
An internal software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-3-TIMEZONE_INVALID |
3-Error |
Invalid timezone name |
The timezone string entered is not valid. The string\n\ should be minimum of more than three letters and should\n\ only contain alphabets |
os |
- |
|
SYS-3-UNWEDGEDISABLED |
3-Error |
Policy map [chars] has been removed.\n Leak debugging on interface [chars] disabled. |
This is error message indicates that the policy-map configured as\n filter in an interface for leak debugging has been removed without\n disabling the filter in the interface. |
mem |
"If the filter is required on the interface for debugging leaks\n" "reconfigure the policy-map and reconfigure the interface for\n" "leak debugging" |
|
SYS-3-URLREADFAIL |
3-Error |
cannot open file for reading '[chars]' |
The URL for the cannot be opened for reading. |
- |
"Check for proper Uniform Resource Locator syntax and for read " "permission and retry." |
|
SYS-3-URLREADFAIL |
3-Error |
cannot open file for reading '[chars]' |
The URL for the cannot be opened for reading. |
- |
"Check for proper Uniform Resource Locator syntax and for read " "permission and retry." |
|
SYS-3-URLREADFAIL |
3-Error |
cannot open file for reading '[chars]' |
The URL for the cannot be opened for reading. |
- |
"Check for proper Uniform Resource Locator syntax and for read " "permission and retry." |
|
SYS-3-URLREADFAIL |
3-Error |
cannot open file for reading '[chars]' |
The URL for the cannot be opened for reading. |
- |
"Check for proper Uniform Resource Locator syntax and for read " "permission and retry." |
|
SYS-3-URLREADFAIL |
3-Error |
cannot open file for reading '[chars]' |
The URL for the cannot be opened for reading. |
- |
"Check for proper Uniform Resource Locator syntax and for read " "permission and retry." |
|
SYS-3-URLREADFAIL |
3-Error |
cannot open file for reading '[chars]' |
The URL for the cannot be opened for reading. |
- |
"Check for proper Uniform Resource Locator syntax and for read " "permission and retry." |
|
SYS-3-URLWRITEFAIL |
3-Error |
redirection url write failed '[chars]' |
Redirection of output to URL failed. |
- |
"Check for free space on destination URL and retry." |
|
SYS-3-URLWRITEFAIL |
3-Error |
redirection url write failed '[chars]' |
Redirection of output to URL failed. |
- |
"Check for free space on destination URL and retry." |
|
SYS-3-URLWRITEFAIL |
3-Error |
redirection url write failed '[chars]' |
Redirection of output to URL failed. |
- |
"Check for free space on destination URL and retry." |
|
SYS-3-URLWRITEFAIL |
3-Error |
redirection url write failed '[chars]' |
Redirection of output to URL failed. |
- |
"Check for free space on destination URL and retry." |
|
SYS-3-URLWRITEFAIL |
3-Error |
redirection url write failed '[chars]' |
Redirection of output to URL failed. |
- |
"Check for free space on destination URL and retry." |
|
SYS-3-URLWRITEFAIL |
3-Error |
redirection url write failed '[chars]' |
Redirection of output to URL failed. |
- |
"Check for free space on destination URL and retry." |
|
SYS-3-USERLOG_ERR |
3-Error |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-3-USERLOG_ERR |
3-Error |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-3-USERLOG_ERR |
3-Error |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-3-USERLOG_ERR |
3-Error |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-3-USERLOG_ERR |
3-Error |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-3-USERLOG_ERR |
3-Error |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-3-WRONGFREELIST |
3-Error |
Block [hec] size [dec] on wrong free list [dec] [dec] |
A freed buffer was placed on the wrong list of free buffers. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-WRONGFREELIST |
3-Error |
Block [hec] size [dec] on wrong free list [dec] [dec] |
A freed buffer was placed on the wrong list of free buffers. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-WRONGFREELIST |
3-Error |
Block [hec] size [dec] on wrong free list [dec] [dec] |
A freed buffer was placed on the wrong list of free buffers. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-WRONGFREELIST |
3-Error |
Block [hec] size [dec] on wrong free list [dec] [dec] |
A freed buffer was placed on the wrong list of free buffers. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-WRONGFREELIST |
3-Error |
Block [hec] size [dec] on wrong free list [dec] [dec] |
A freed buffer was placed on the wrong list of free buffers. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-3-WRONGFREELIST |
3-Error |
Block [hec] size [dec] on wrong free list [dec] [dec] |
A freed buffer was placed on the wrong list of free buffers. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-4-ADD_STACK |
4-Warning |
Invalid index [dec] for additional stack size request. |
The index passed should of less than the enum E_MAX_ADD_STACK_SIZE value equal to or higher than the enum is an invalid index. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-4-CHUNK_PP_CREATEDESTROY |
4-Warning |
A chunk is created or destroyed from pseudo-preemption context. Chunk name : [chars] |
Creating or destroying chunks from pseudo-preemption context is not allowed. |
- |
"Copy the error message exactly as it appears and " "report it to your technical support representative." |
|
SYS-4-CHUNKSIBLINGSEXCEED |
4-Warning |
Number of siblings in a chunk has gone above the threshold. Threshold:[dec] Sibling-Count:[dec] Chunk:0x[hec] Name:[chars] |
Number of siblings in a chunk with no header has gone above the default/configured threshold configured using <cmdBold>memory chunk siblings threshold<nocmdBold> <cmdArgs>count<nocmdArgs> |
- |
LOG_STD_SH_TECH_ACTION |
|
SYS-4-CHUNKSIBLINGSEXCEED |
4-Warning |
Number of siblings in a chunk has gone above the threshold. Threshold:[dec] Sibling-Count:[dec] Chunk:0x[hec] Name:[chars] |
Number of siblings in a chunk with no header has gone above the default/configured threshold configured using <cmdBold>memory chunk siblings threshold<nocmdBold> <cmdArgs>count<nocmdArgs> |
- |
LOG_STD_SH_TECH_ACTION |
|
SYS-4-CHUNKSIBLINGSEXCEED |
4-Warning |
Number of siblings in a chunk has gone above the threshold. Threshold:[dec] Sibling-Count:[dec] Chunk:0x[hec] Name:[chars] |
Number of siblings in a chunk with no header has gone above the default/configured threshold configured using <cmdBold>memory chunk siblings threshold<nocmdBold> <cmdArgs>count<nocmdArgs> |
- |
LOG_STD_SH_TECH_ACTION |
|
SYS-4-CHUNKSIBLINGSEXCEED |
4-Warning |
Number of siblings in a chunk has gone above the threshold. Threshold:[dec] Sibling-Count:[dec] Chunk:0x[hec] Name:[chars] |
Number of siblings in a chunk with no header has gone above the default/configured threshold configured using <cmdBold>memory chunk siblings threshold<nocmdBold> <cmdArgs>count<nocmdArgs> |
- |
LOG_STD_SH_TECH_ACTION |
|
SYS-4-CHUNKSIBLINGSEXCEED |
4-Warning |
Number of siblings in a chunk has gone above the threshold. Threshold:[dec] Sibling-Count:[dec] Chunk:0x[hec] Name:[chars] |
Number of siblings in a chunk with no header has gone above the default/configured threshold configured using <cmdBold>memory chunk siblings threshold<nocmdBold> <cmdArgs>count<nocmdArgs> |
- |
LOG_STD_SH_TECH_ACTION |
|
SYS-4-CHUNKSIBLINGSEXCEED |
4-Warning |
Number of siblings in a chunk has gone above the threshold. Threshold:[dec] Sibling-Count:[dec] Chunk:0x[hec] Name:[chars] |
Number of siblings in a chunk with no header has gone above the default/configured threshold configured using <cmdBold>memory chunk siblings threshold<nocmdBold> <cmdArgs>count<nocmdArgs> |
- |
LOG_STD_SH_TECH_ACTION |
|
SYS-4-CONFIG_NEWER |
4-Warning |
Configuration from version [dec].[dec] may not be correctly understood |
The software detected that the configuration saved in memory was written by a newer version of software. There might be commands saved in memory that are not implemented by the older software version. |
none |
"Examine all the messages printed while the router was " "booting. For each message about an unknown command determine " "whether that feature is required. If so upgrade to a " "newer version of software that supports that feature." |
|
SYS-4-CONFIG_NEWER |
4-Warning |
Configuration from version [dec].[dec] may not be correctly understood |
The software detected that the configuration saved in memory was written by a newer version of software. There might be commands saved in memory that are not implemented by the older software version. |
none |
"Examine all the messages printed while the router was " "booting. For each message about an unknown command determine " "whether that feature is required. If so upgrade to a " "newer version of software that supports that feature." |
|
SYS-4-CONFIG_NEWER |
4-Warning |
Configuration from version [dec].[dec] may not be correctly understood |
The software detected that the configuration saved in memory was written by a newer version of software. There might be commands saved in memory that are not implemented by the older software version. |
none |
"Examine all the messages printed while the router was " "booting. For each message about an unknown command determine " "whether that feature is required. If so upgrade to a " "newer version of software that supports that feature." |
|
SYS-4-CONFIG_NEWER |
4-Warning |
Configuration from version [dec].[dec] may not be correctly understood |
The software detected that the configuration saved in memory was written by a newer version of software. There might be commands saved in memory that are not implemented by the older software version. |
none |
"Examine all the messages printed while the router was " "booting. For each message about an unknown command determine " "whether that feature is required. If so upgrade to a " "newer version of software that supports that feature." |
|
SYS-4-CONFIG_NEWER |
4-Warning |
Configuration from version [dec].[dec] may not be correctly understood |
The software detected that the configuration saved in memory was written by a newer version of software. There might be commands saved in memory that are not implemented by the older software version. |
none |
"Examine all the messages printed while the router was " "booting. For each message about an unknown command determine " "whether that feature is required. If so upgrade to a " "newer version of software that supports that feature." |
|
SYS-4-CONFIG_NEWER |
4-Warning |
Configuration from version [dec].[dec] may not be correctly understood |
The software detected that the configuration saved in memory was written by a newer version of software. There might be commands saved in memory that are not implemented by the older software version. |
none |
"Examine all the messages printed while the router was " "booting. For each message about an unknown command determine " "whether that feature is required. If so upgrade to a " "newer version of software that supports that feature." |
|
SYS-4-CONFIG_NOLOCK |
4-Warning |
The configuration could not be locked |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it " "to your technical support representative." |
|
SYS-4-CONFIG_NOLOCK |
4-Warning |
The configuration could not be locked |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it " "to your technical support representative." |
|
SYS-4-CONFIG_NOLOCK |
4-Warning |
The configuration could not be locked |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it " "to your technical support representative." |
|
SYS-4-CONFIG_NOLOCK |
4-Warning |
The configuration could not be locked |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it " "to your technical support representative." |
|
SYS-4-CONFIG_NOLOCK |
4-Warning |
The configuration could not be locked |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it " "to your technical support representative." |
|
SYS-4-CONFIG_NOLOCK |
4-Warning |
The configuration could not be locked |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it " "to your technical support representative." |
|
SYS-4-CONFIG_NV_NEED_OVERRUN |
4-Warning |
Non config data present at the end of nvram needs to be overwritten to fit the configuration into nvram |
The software detected that the non config data files occupying the end of nvram need to be overwritten to fit the configuration. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. |
- |
"Compress the configuration and store or copy to flash as appropriate" |
|
SYS-4-CONFIG_NV_NEED_OVERRUN |
4-Warning |
Non config data present at the end of nvram needs to be overwritten to fit the configuration into nvram |
The software detected that the non config data files occupying the end of nvram need to be overwritten to fit the configuration. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. |
- |
"Compress the configurtion and store or copy to flash as appropriate" |
|
SYS-4-CONFIG_NV_NEED_OVERRUN |
4-Warning |
Non config data present at the end of nvram needs to be overwritten to fit the configuration into nvram |
The software detected that the non config data files occupying the end of nvram need to be overwritten to fit the configuration. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. |
- |
"Compress the configurtion and store or copy to flash as appropriate" |
|
SYS-4-CONFIG_NV_NEED_OVERRUN |
4-Warning |
Non config data present at the end of nvram needs to be overwritten to fit the configuration into nvram |
The software detected that the non config data files occupying the end of nvram need to be overwritten to fit the configuration. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. |
- |
"Compress the configurtion and store or copy to flash as appropriate" |
|
SYS-4-CONFIG_NV_NEED_OVERRUN |
4-Warning |
Non config data present at the end of nvram needs to be overwritten to fit the configuration into nvram |
The software detected that the non config data files occupying the end of nvram need to be overwritten to fit the configuration. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. |
- |
"Compress the configurtion and store or copy to flash as appropriate" |
|
SYS-4-CONFIG_NV_NEED_OVERRUN |
4-Warning |
Non config data present at the end of nvram needs to be overwritten to fit the configuration into nvram |
The software detected that the non config data files occupying the end of nvram need to be overwritten to fit the configuration. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. |
- |
"Compress the configurtion and store or copy to flash as appropriate" |
|
SYS-4-CONFIG_NV_NEED_TRUNCATE |
4-Warning |
Configuration needs to be truncated to fit into nvram |
The software detected that the configuration is to be truncated to fit in the nvram. There was not enough space to save the compressed configuration |
- |
"Save the configuration to flash if the platform supports " "\"boot config nvbypass\" command." |
|
SYS-4-CONFIG_NV_NEED_TRUNCATE |
4-Warning |
Configuration needs to be truncated to fit into nvram |
The software detected that the configuration is to be truncated to fit in the nvram. There was not enough space to save the compressed configuration |
- |
"Save the configuration to flash if the platform supports " "\"boot config nvbypass\" command." |
|
SYS-4-CONFIG_NV_NEED_TRUNCATE |
4-Warning |
Configuration needs to be truncated to fit into nvram |
The software detected that the configuration is to be truncated to fit in the nvram. There was not enough space to save the compressed configuration |
- |
"Save the configuration to flash if the platform supports " "\"boot config nvbypass\" command." |
|
SYS-4-CONFIG_NV_NEED_TRUNCATE |
4-Warning |
Configuration needs to be truncated to fit into nvram |
The software detected that the configuration is to be truncated to fit in the nvram. There was not enough space to save the compressed configuration |
- |
"Save the configuration to flash if the platform supports " "\"boot config nvbypass\" command." |
|
SYS-4-CONFIG_NV_NEED_TRUNCATE |
4-Warning |
Configuration needs to be truncated to fit into nvram |
The software detected that the configuration is to be truncated to fit in the nvram. There was not enough space to save the compressed configuration |
- |
"Save the configuration to flash if the platform supports " "\"boot config nvbypass\" command." |
|
SYS-4-CONFIG_NV_NEED_TRUNCATE |
4-Warning |
Configuration needs to be truncated to fit into nvram |
The software detected that the configuration is to be truncated to fit in the nvram. There was not enough space to save the compressed configuration |
- |
"Save the configuration to flash if the platform supports " "\"boot config nvbypass\" command." |
|
SYS-4-CONFIG_NV_OVERRUN |
4-Warning |
Non config data present at the end of nvram is corrupted |
The software detected that the configuration saved into nvram has overlaid a part of the nvram occupied by non config data files.Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. |
- |
"Compress the configuration and store or copy to flash as appropriate" |
|
SYS-4-CONFIG_NV_OVERRUN |
4-Warning |
Non config data present at the end of nvram is corrupted |
The software detected that the configuration saved into nvram has overlaid a part of the nvram occupied by non config data files.Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. |
- |
"Compress the configurtion and store or copy to flash as appropriate" |
|
SYS-4-CONFIG_NV_OVERRUN |
4-Warning |
Non config data present at the end of nvram is corrupted |
The software detected that the configuration saved into nvram has overlaid a part of the nvram occupied by non config data files.Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. |
- |
"Compress the configurtion and store or copy to flash as appropriate" |
|
SYS-4-CONFIG_NV_OVERRUN |
4-Warning |
Non config data present at the end of nvram is corrupted |
The software detected that the configuration saved into nvram has overlaid a part of the nvram occupied by non config data files.Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. |
- |
"Compress the configurtion and store or copy to flash as appropriate" |
|
SYS-4-CONFIG_NV_OVERRUN |
4-Warning |
Non config data present at the end of nvram is corrupted |
The software detected that the configuration saved into nvram has overlaid a part of the nvram occupied by non config data files.Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. |
- |
"Compress the configurtion and store or copy to flash as appropriate" |
|
SYS-4-CONFIG_NV_OVERRUN |
4-Warning |
Non config data present at the end of nvram is corrupted |
The software detected that the configuration saved into nvram has overlaid a part of the nvram occupied by non config data files.Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. |
- |
"Compress the configurtion and store or copy to flash as appropriate" |
|
SYS-4-CONFIG_NV_TRUNCATE |
4-Warning |
Truncated configuration to %ld bytes from %ld bytes |
The software detected that the configuration saved into nvram has been truncated. There was not enough space to save the compressed configuration. |
- |
"Save the configuration to flash if the platform supports " " \"boot config\" command." |
|
SYS-4-CONFIG_NV_TRUNCATE |
4-Warning |
Truncated configuration to %ld bytes from %ld bytes |
The software detected that the configuration saved into nvram has been truncated. There was not enough space to save the compressed configuration. |
- |
"Save the configuration to flash if the platform supports " " \"boot config\" command." |
|
SYS-4-CONFIG_NV_TRUNCATE |
4-Warning |
Truncated configuration to %ld bytes from %ld bytes |
The software detected that the configuration saved into nvram has been truncated. There was not enough space to save the compressed configuration. |
- |
"Save the configuration to flash if the platform supports " " \"boot config\" command." |
|
SYS-4-CONFIG_NV_TRUNCATE |
4-Warning |
Truncated configuration to %ld bytes from %ld bytes |
The software detected that the configuration saved into nvram has been truncated. There was not enough space to save the compressed configuration. |
- |
"Save the configuration to flash if the platform supports " " \"boot config\" command." |
|
SYS-4-CONFIG_NV_TRUNCATE |
4-Warning |
Truncated configuration to %ld bytes from %ld bytes |
The software detected that the configuration saved into nvram has been truncated. There was not enough space to save the compressed configuration. |
- |
"Save the configuration to flash if the platform supports " " \"boot config\" command." |
|
SYS-4-CONFIG_NV_TRUNCATE |
4-Warning |
Truncated configuration to %ld bytes from %ld bytes |
The software detected that the configuration saved into nvram has been truncated. There was not enough space to save the compressed configuration. |
- |
"Save the configuration to flash if the platform supports " " \"boot config\" command." |
|
SYS-4-CONFIG_RESOLVE_FAILURE |
4-Warning |
System config parse from [chars] failed |
The configuration file from the URL specified in the error message could not be read. |
- |
"Enter the <CmdBold>no service config<NoCmdBold> " "command to disable autoloading of configuration files " "OR investigate why the tftp load is failing." |
|
SYS-4-CONFIG_RESOLVE_FAILURE |
4-Warning |
System config parse from [chars] failed |
The configuration file from the URL specified in the error message could not be read. |
- |
"Enter the <CmdBold>no service config<NoCmdBold> " "command to disable autoloading of configuration files " "OR investigate why the tftp load is failing." |
|
SYS-4-CONFIG_RESOLVE_FAILURE |
4-Warning |
System config parse from [chars] failed |
The configuration file from the URL specified in the error message could not be read. |
- |
"Enter the <CmdBold>no service config<NoCmdBold> " "command to disable autoloading of configuration files " "OR investigate why the tftp load is failing." |
|
SYS-4-CONFIG_RESOLVE_FAILURE |
4-Warning |
System config parse from [chars] failed |
The configuration file from the URL specified in the error message could not be read. |
- |
"Enter the <CmdBold>no service config<NoCmdBold> " "command to disable autoloading of configuration files " "OR investigate why the tftp load is failing." |
|
SYS-4-CONFIG_RESOLVE_FAILURE |
4-Warning |
System config parse from [chars] failed |
The configuration file from the URL specified in the error message could not be read. |
- |
"Enter the <CmdBold>no service config<NoCmdBold> " "command to disable autoloading of configuration files " "OR investigate why the tftp load is failing." |
|
SYS-4-CONFIG_RESOLVE_FAILURE |
4-Warning |
System config parse from [chars] failed |
The configuration file from the URL specified in the error message could not be read. |
- |
"Enter the <CmdBold>no service config<NoCmdBold> " "command to disable autoloading of configuration files " "OR investigate why the tftp load is failing." |
|
SYS-4-CPURESRISING |
4-Warning |
[chars][chars] is seeing [chars] cpu util [dec]%% at [chars] level more than the configured [chars] limit [dec] %% |
The system is experiencing high CPU usage possibly from a process that is using too much CPU. This condition demands immediate attention or packets or calls may be dropped. CPURESRISING notifications should be matched with the corresponding CPURESFALLING/CPURESUNAPPLY notification. |
- |
"No action is required" |
|
SYS-4-CPURESRISING |
4-Warning |
[chars][chars] is seeing [chars] cpu util [dec]%% at [chars] level more than the configured [chars] limit [dec] %% |
The system is experiencing high CPU usage possibly from a process that is using too much CPU. This condition demands immediate attention or packets or calls may be dropped. CPURESRISING notifications should be matched with the corresponding CPURESFALLING/CPURESUNAPPLY notification. |
- |
"No action is required" |
|
SYS-4-CPURESRISING |
4-Warning |
[chars][chars] is seeing [chars] cpu util [dec]%% at [chars] level more than the configured [chars] limit [dec] %% |
The system is experiencing high CPU usage possibly from a process that is using too much CPU. This condition demands immediate attention or packets or calls may be dropped. CPURESRISING notifications should be matched with the corresponding CPURESFALLING/CPURESUNAPPLY notification. |
- |
"No action is required" |
|
SYS-4-CPURESRISING |
4-Warning |
[chars][chars] is seeing [chars] cpu util [dec]%% at [chars] level more than the configured [chars] limit [dec] %% |
The system is experiencing high CPU usage possibly from a process that is using too much CPU. This condition demands immediate attention or packets or calls may be dropped. CPURESRISING notifications should be matched with the corresponding CPURESFALLING/CPURESUNAPPLY notification. |
- |
"No action is required" |
|
SYS-4-CPURESRISING |
4-Warning |
[chars][chars] is seeing [chars] cpu util [dec]%% at [chars] level more than the configured [chars] limit [dec] %% |
The system is experiencing high CPU usage possibly from a process that is using too much CPU. This condition demands immediate attention or packets or calls may be dropped. CPURESRISING notifications should be matched with the corresponding CPURESFALLING/CPURESUNAPPLY notification. |
- |
"No action is required" |
|
SYS-4-CPURESRISING |
4-Warning |
[chars][chars] is seeing [chars] cpu util [dec]%% at [chars] level more than the configured [chars] limit [dec] %% |
The system is experiencing high CPU usage possibly from a process that is using too much CPU. This condition demands immediate attention or packets or calls may be dropped. CPURESRISING notifications should be matched with the corresponding CPURESFALLING/CPURESUNAPPLY notification. |
- |
"No action is required" |
|
SYS-4-DUAL_MESSAGE |
4-Warning |
SNMP system message request [dec] denied because of pending job |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-4-DUAL_MESSAGE |
4-Warning |
SNMP system message request [dec] denied because of pending job |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-4-DUAL_MESSAGE |
4-Warning |
SNMP system message request [dec] denied because of pending job |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-4-DUAL_MESSAGE |
4-Warning |
SNMP system message request [dec] denied because of pending job |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-4-DUAL_MESSAGE |
4-Warning |
SNMP system message request [dec] denied because of pending job |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-4-DUAL_MESSAGE |
4-Warning |
SNMP system message request [dec] denied because of pending job |
A software error occurred. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-4-EXMALLOCFAIL |
4-Warning |
External memory allocation of [dec] bytes failed from EXMEM [dec] |
The requested memory allocation is not available from the specified memory pool. The current system configuration network environment or possibly a software error might have exhausted or fragmented the router's memory. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-4-EXMALLOCFAIL |
4-Warning |
External memory allocation of [dec] bytes failed from EXMEM [dec] |
The requested memory allocation is not available from the specified memory pool. The current system configuration network environment or possibly a software error might have exhausted or fragmented the router's memory. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-4-EXMALLOCFAIL |
4-Warning |
External memory allocation of [dec] bytes failed from EXMEM [dec] |
The requested memory allocation is not available from the specified memory pool. The current system configuration network environment or possibly a software error might have exhausted or fragmented the router's memory. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-4-EXMALLOCFAIL |
4-Warning |
External memory allocation of [dec] bytes failed from EXMEM [dec] |
The requested memory allocation is not available from the specified memory pool. The current system configuration network environment or possibly a software error might have exhausted or fragmented the router's memory. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-4-EXMALLOCFAIL |
4-Warning |
External memory allocation of [dec] bytes failed from EXMEM [dec] |
The requested memory allocation is not available from the specified memory pool. The current system configuration network environment or possibly a software error might have exhausted or fragmented the router's memory. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-4-EXMALLOCFAIL |
4-Warning |
External memory allocation of [dec] bytes failed from EXMEM [dec] |
The requested memory allocation is not available from the specified memory pool. The current system configuration network environment or possibly a software error might have exhausted or fragmented the router's memory. |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-4-FREEMEMLOW |
4-Warning |
Top Allocator Name: [chars] PC: [chars] Size: [dec] Count: [dec] Largest block: %-9lu |
The memory pool specified in the error message is experiencing a low-memory condition. The amount of free memory available in the specified memory pool has dropped below the configured low-memory limit. |
- |
"No action is required" |
|
SYS-4-FREEMEMLOW |
4-Warning |
Free Memory has dropped below low watermark\nPool: [chars] Free: %lu Threshold: %lu\n |
The memory pool specified in the error message is experiencing a low-memory condition. The amount of free memory available in the specified memory pool has dropped below the configured low-memory limit. |
- |
"No action is required" |
|
SYS-4-FREEMEMLOW |
4-Warning |
Free Memory has dropped below low watermark\nPool: [chars] Free: %lu Threshold: %lu\n |
The memory pool specified in the error message is experiencing a low-memory condition. The amount of free memory available in the specified memory pool has dropped below the configured low-memory limit. |
- |
"No action is required" |
|
SYS-4-FREEMEMLOW |
4-Warning |
Free Memory has dropped below low watermark\nPool: [chars] Free: %lu Threshold: %lu\n |
The memory pool specified in the error message is experiencing a low-memory condition. The amount of free memory available in the specified memory pool has dropped below the configured low-memory limit. |
- |
"No action is required" |
|
SYS-4-FREEMEMLOW |
4-Warning |
Free Memory has dropped below low watermark\nPool: [chars] Free: %lu Threshold: %lu\n |
The memory pool specified in the error message is experiencing a low-memory condition. The amount of free memory available in the specified memory pool has dropped below the configured low-memory limit. |
- |
"No action is required" |
|
SYS-4-FREEMEMLOW |
4-Warning |
Free Memory has dropped below low watermark\nPool: [chars] Free: %lu Threshold: %lu\n |
The memory pool specified in the error message is experiencing a low-memory condition. The amount of free memory available in the specified memory pool has dropped below the configured low-memory limit. |
- |
"No action is required" |
|
SYS-4-GD_DATAUNRELIABLE |
4-Warning |
Update to memory leak detector on free of 0x[hec] failed CLI output is unreliable\n |
managed chunk malloc to store the range that is freed while memory leak detector is in progress failed. Hence memory leak detector will not be updated of this free and this can be reported as leak which is false. |
mem |
"Ignore the output of \"show memory debug leaks..\" if system is in low " "memory condition else perform a bug toolkit search on the web for " "existing bugs related to this error message if none found contact TAC " "for this problem providing \"show version\" and " "\"show memory statistics\" output." |
|
SYS-4-GD_DATAUNRELIABLE |
4-Warning |
Update to memory leak detector on free of 0x[hec] failed CLI output is unreliable\n |
managed chunk malloc to store the range that is freed while memory leak detector is in progress failed. Hence memory leak detector will not be updated of this free and this can be reported as leak which is false. |
mem |
"Ignore the output of \"show memory debug leaks..\" if system is in low " "memory condition else perform a bug toolkit search on the web for " "existing bugs related to this error message if none found contact TAC " "for this problem providing \"show version\" and " "\"show memory statistics\" output." |
|
SYS-4-GD_DATAUNRELIABLE |
4-Warning |
Update to memory leak detector on free of 0x[hec] failed CLI output is unreliable\n |
managed chunk malloc to store the range that is freed while memory leak detector is in progress failed. Hence memory leak detector will not be updated of this free and this can be reported as leak which is false. |
mem |
"Ignore the output of \"show memory debug leaks..\" if system is in low " "memory condition else perform a bug toolkit search on the web for " "existing bugs related to this error message if none found contact TAC " "for this problem providing \"show version\" and " "\"show memory statistics\" output." |
|
SYS-4-GD_DATAUNRELIABLE |
4-Warning |
Update to memory leak detector on free of 0x[hec] failed CLI output is unreliable\n |
managed chunk malloc to store the range that is freed while memory leak detector is in progress failed. Hence memory leak detector will not be updated of this free and this can be reported as leak which is false. |
mem |
"Ignore the output of \"show memory debug leaks..\" if system is in low " "memory condition else perform a bug toolkit search on the web for " "existing bugs related to this error message if none found contact TAC " "for this problem providing \"show version\" and " "\"show memory statistics\" output." |
|
SYS-4-GD_DATAUNRELIABLE |
4-Warning |
Update to memory leak detector on free of 0x[hec] failed CLI output is unreliable\n |
managed chunk malloc to store the range that is freed while memory leak detector is in progress failed. Hence memory leak detector will not be updated of this free and this can be reported as leak which is false. |
mem |
"Ignore the output of \"show memory debug leaks..\" if system is in low " "memory condition else perform a bug toolkit search on the web for " "existing bugs related to this error message if none found contact TAC " "for this problem providing \"show version\" and " "\"show memory statistics\" output." |
|
SYS-4-GD_DATAUNRELIABLE |
4-Warning |
Update to memory leak detector on free of 0x[hec] failed CLI output is unreliable\n |
managed chunk malloc to store the range that is freed while memory leak detector is in progress failed. Hence memory leak detector will not be updated of this free and this can be reported as leak which is false. |
mem |
"Ignore the output of \"show memory debug leaks..\" if system is in low " "memory condition else perform a bug toolkit search on the web for " "existing bugs related to this error message if none found contact TAC " "for this problem providing \"show version\" and " "\"show memory statistics\" output." |
|
SYS-4-GLOBALBUFEXCEED |
4-Warning |
Buffer usage has gone above global buffer [chars] threshold \nconfigured [dec] Current usage :[dec]\n |
global buffer usage has gone above the configured limit. This violation can happen because of all the entities which use buffers in the system. GLOBALBUFEXCEED notifications should be matched with the corresponding GLOBALBUFRECOVER/GLOBALBUFUNAPPLY notification. |
rmi |
"No action is required" |
|
SYS-4-GREEDY_REGEXP |
4-Warning |
[chars] while processing the input regular expression. Aborting processing use alternate regular expression. Input regular expression: \[chars]\ |
Regular expression processing limitation: Certain regular expressions require huge stack space for processing or can lead to processing timeouts. We abort processing such regular expressions and print this message to avoid stack overflow/unexpected reload. |
os |
"The regular expression specified leads to stack overflow/processing " "timeout of the indicated process. Recommended to use a different " "regular expression." |
|
SYS-4-GREEDY_REGEXP |
4-Warning |
[chars] while processing the input regular expression. Aborting processing use alternate regular expression. Input regular expression: \[chars]\ |
Regular expression processing limitation: Certain regular expressions require huge stack space for processing or can lead to processing timeouts. We abort processing such regular expressions and print this message to avoid stack overflow/unexpected reload. |
os |
"The regular expression specified leads to stack overflow/processing " "timeout of the indicated process. Recommended to use a different " "regular expression." |
|
SYS-4-GREEDY_REGEXP |
4-Warning |
[chars] while processing the input regular expression. Aborting processing use alternate regular expression. Input regular expression: \[chars]\ |
Regular expression processing limitation: Certain regular expressions require huge stack space for processing or can lead to processing timeouts. We abort processing such regular expressions and print this message to avoid stack overflow/unexpected reload. |
os |
"The regular expression specified leads to stack overflow/processing " "timeout of the indicated process. Recommended to use a different " "regular expression." |
|
SYS-4-GREEDY_REGEXP |
4-Warning |
[chars] while processing the input regular expression. Aborting processing use alternate regular expression. Input regular expression: \[chars]\ |
Regular expression processing limitation: Certain regular expressions require huge stack space for processing or can lead to processing timeouts. We abort processing such regular expressions and print this message to avoid stack overflow/unexpected reload. |
os |
"The regular expression specified leads to stack overflow/processing " "timeout of the indicated process. Recommended to use a different " "regular expression." |
|
SYS-4-GREEDY_REGEXP |
4-Warning |
[chars] while processing the input regular expression. Aborting processing use alternate regular expression. Input regular expression: \[chars]\ |
Regular expression processing limitation: Certain regular expressions require huge stack space for processing or can lead to processing timeouts. We abort processing such regular expressions and print this message to avoid stack overflow/unexpected reload. |
os |
"The regular expression specified leads to stack overflow/processing " "timeout of the indicated process. Recommended to use a different " "regular expression." |
|
SYS-4-GREEDY_REGEXP |
4-Warning |
[chars] while processing the input regular expression. Aborting processing use alternate regular expression. Input regular expression: \[chars]\ |
Regular expression processing limitation: Certain regular expressions require huge stack space for processing or can lead to processing timeouts. We abort processing such regular expressions and print this message to avoid stack overflow/unexpected reload. |
os |
"The regular expression specified leads to stack overflow/processing " "timeout of the indicated process. Recommended to use a different " "regular expression." |
|
SYS-4-INVALID_IMAGE |
4-Warning |
Running invalid image for platform! |
The software image being run is for a different hardware architecture. This problem can occur on a Cisco 1003 Cisco 1004 or Cisco 1005. The Cisco 1003 and Cisco 1004 use a different image from the Cisco 1005. |
none |
"Install the correct software image." |
|
SYS-4-INVALID_IMAGE |
4-Warning |
Running invalid image for platform! |
The software image being run is for a different hardware architecture. This problem can occur on a Cisco 1003 Cisco 1004 or Cisco 1005. The Cisco 1003 and Cisco 1004 use a different image from the Cisco 1005. |
none |
"Install the correct software image." |
|
SYS-4-INVALID_IMAGE |
4-Warning |
Running invalid image for platform! |
The software image being run is for a different hardware architecture. This problem can occur on a Cisco 1003 Cisco 1004 or Cisco 1005. The Cisco 1003 and Cisco 1004 use a different image from the Cisco 1005. |
none |
"Install the correct software image." |
|
SYS-4-INVALID_IMAGE |
4-Warning |
Running invalid image for platform! |
The software image being run is for a different hardware architecture. This problem can occur on a Cisco 1003 Cisco 1004 or Cisco 1005. The Cisco 1003 and Cisco 1004 use a different image from the Cisco 1005. |
none |
"Install the correct software image." |
|
SYS-4-INVALID_IMAGE |
4-Warning |
Running invalid image for platform! |
The software image being run is for a different hardware architecture. This problem can occur on a Cisco 1003 Cisco 1004 or Cisco 1005. The Cisco 1003 and Cisco 1004 use a different image from the Cisco 1005. |
none |
"Install the correct software image." |
|
SYS-4-INVALID_IMAGE |
4-Warning |
Running invalid image for platform! |
The software image being run is for a different hardware architecture. This problem can occur on a Cisco 1003 Cisco 1004 or Cisco 1005. The Cisco 1003 and Cisco 1004 use a different image from the Cisco 1005. |
none |
"Install the correct software image." |
|
SYS-4-LOGGING_PERSISTENT_OVERRUN |
4-Warning |
Logging persistent command exceeded its size. Oldest logging-persistent file was deleted file name: [chars]. |
The Common Criteria CC certification requires a log message to indicate when logging persistent command exceeded the specified size limit and the old messages were overwritten. |
os-logging |
"This message is for information however the " "user may consider to increase logging-persistent size or to " "delete old logging persistent files." |
|
SYS-4-LOGGING_THRESHOLD_CHANGED |
4-Warning |
Logging persistent exceeded the threshold value and its space is full. The threshold capacity was changed to the default value. Oldest logging-persistent files will be deleted. |
This log message to indicate when logging persistent command exceeded the specified size limitthreshold value and the old messages were overwritten. |
syslog |
"This message is for information however the " "user may consider to increase logging-persistent size or to " "delete old logging persistent files." |
|
SYS-4-NV_BLOCK_INITFAIL |
4-Warning |
Unable to initialize the geometry of nvram |
The software detected that it failed to initialize the nvram block geometry a part of the nvram to host non config data files. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. This may happen when the entire nvram is packed with the configuration and the newer version of software which supports this feature could not find the minimum room in the nvram to initialize block file system. |
- |
"Reduce the configurations in the nvram atleast by 2K" |
|
SYS-4-NV_BLOCK_INITFAIL |
4-Warning |
Unable to initialize the geometry of nvram |
The software detected that it failed to initialize the nvram block geometry a part of the nvram to host non config data files. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. This may happen when the entire nvram is packed with the configuration and the newer version of software which supports this feature could not find the minimum room in the nvram to initialize block file system. |
- |
"Reduce the configurations in the nvram atleast by 2K" |
|
SYS-4-NV_BLOCK_INITFAIL |
4-Warning |
Unable to initialize the geometry of nvram |
The software detected that it failed to initialize the nvram block geometry a part of the nvram to host non config data files. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. This may happen when the entire nvram is packed with the configuration and the newer version of software which supports this feature could not find the minimum room in the nvram to initialize block file system. |
- |
"Reduce the configurations in the nvram atleast by 2K" |
|
SYS-4-NV_BLOCK_INITFAIL |
4-Warning |
Unable to initialize the geometry of nvram |
The software detected that it failed to initialize the nvram block geometry a part of the nvram to host non config data files. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. This may happen when the entire nvram is packed with the configuration and the newer version of software which supports this feature could not find the minimum room in the nvram to initialize block file system. |
- |
"Reduce the configurations in the nvram atleast by 2K" |
|
SYS-4-NV_BLOCK_INITFAIL |
4-Warning |
Unable to initialize the geometry of nvram |
The software detected that it failed to initialize the nvram block geometry a part of the nvram to host non config data files. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. This may happen when the entire nvram is packed with the configuration and the newer version of software which supports this feature could not find the minimum room in the nvram to initialize block file system. |
- |
"Reduce the configurations in the nvram atleast by 2K" |
|
SYS-4-NV_BLOCK_INITFAIL |
4-Warning |
Unable to initialize the geometry of nvram |
The software detected that it failed to initialize the nvram block geometry a part of the nvram to host non config data files. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. This may happen when the entire nvram is packed with the configuration and the newer version of software which supports this feature could not find the minimum room in the nvram to initialize block file system. |
- |
"Reduce the configurations in the nvram atleast by 2K" |
|
SYS-4-NV_CHKSUM |
4-Warning |
An nvram checksum is already in progress |
An interrupt service routine attempted to perform a checksum on the nvram contents and found the resource in use. |
nvram |
- |
|
SYS-4-NV_CHKSUM |
4-Warning |
An nvram checksum is already in progress |
An interrupt service routine attempted to perform a checksum on the nvram contents and found the resource in use. |
nvram |
- |
|
SYS-4-NV_CHKSUM |
4-Warning |
An nvram checksum is already in progress |
An interrupt service routine attempted to perform a checksum on the nvram contents and found the resource in use. |
nvram |
- |
|
SYS-4-NV_CHKSUM |
4-Warning |
An nvram checksum is already in progress |
An interrupt service routine attempted to perform a checksum on the nvram contents and found the resource in use. |
nvram |
- |
|
SYS-4-NV_CHKSUM |
4-Warning |
An nvram checksum is already in progress |
An interrupt service routine attempted to perform a checksum on the nvram contents and found the resource in use. |
nvram |
- |
|
SYS-4-NV_CHKSUM |
4-Warning |
An nvram checksum is already in progress |
An interrupt service routine attempted to perform a checksum on the nvram contents and found the resource in use. |
nvram |
- |
|
SYS-4-NV_INVALID_BOOTUP |
4-Warning |
Nvram is invalid. Attempting to read and apply '[chars]' anyway |
Nvram is corrupted. But still try to read startup-config as this was the behavior in 12.3T for platforms like c1700. |
nvram |
"Verify whether the box was powercycled or crash " "was triggered prior to this message. Issue 'show tech' command" |
|
SYS-4-NV_NOLOCK |
4-Warning |
Failed to acquire an nvram lock |
An interrupt service routine's attempt to acquire a semaphore lock failed |
- |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
SYS-4-PUPDATECLOCK |
4-Warning |
Periodic Clock update with ROMMON failed because size left in ROMMON %lu size needed %lu error code %ld |
This message indicates that the periodic update of the clock to ROMMON failed. This would indicate that the router when restarted may have past clock values |
os |
"Drop to rommon and clear unwanted rommon variable entries" |
|
SYS-4-REGEXP |
4-Warning |
[chars]. |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-4-REGEXP |
4-Warning |
[chars]. |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-4-REGEXP |
4-Warning |
[chars]. |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-4-REGEXP |
4-Warning |
[chars]. |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-4-REGEXP |
4-Warning |
[chars]. |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-4-REGEXP |
4-Warning |
[chars]. |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-4-RELOAD_ATTEMPT |
4-Warning |
Attempt via SNMP failed system shutdown not configured |
SNMP cannot be used to reload the router unless this functionality has been previously configured. This message reports that an attempt to reload the router failed because SNMP reloads are not currently configured on the router. |
none |
"This is a notification message only. No action is required." |
|
SYS-4-RELOAD_ATTEMPT |
4-Warning |
Attempt via SNMP failed system shutdown not configured |
SNMP cannot be used to reload the router unless this functionality has been previously configured. This message reports that an attempt to reload the router failed because SNMP reloads are not currently configured on the router. |
none |
"This is a notification message only. No action is required." |
|
SYS-4-RELOAD_ATTEMPT |
4-Warning |
Attempt via SNMP failed system shutdown not configured |
SNMP cannot be used to reload the router unless this functionality has been previously configured. This message reports that an attempt to reload the router failed because SNMP reloads are not currently configured on the router. |
none |
"This is a notification message only. No action is required." |
|
SYS-4-RELOAD_ATTEMPT |
4-Warning |
Attempt via SNMP failed system shutdown not configured |
SNMP cannot be used to reload the router unless this functionality has been previously configured. This message reports that an attempt to reload the router failed because SNMP reloads are not currently configured on the router. |
none |
"This is a notification message only. No action is required." |
|
SYS-4-RELOAD_ATTEMPT |
4-Warning |
Attempt via SNMP failed system shutdown not configured |
SNMP cannot be used to reload the router unless this functionality has been previously configured. This message reports that an attempt to reload the router failed because SNMP reloads are not currently configured on the router. |
none |
"This is a notification message only. No action is required." |
|
SYS-4-RELOAD_ATTEMPT |
4-Warning |
Attempt via SNMP failed system shutdown not configured |
SNMP cannot be used to reload the router unless this functionality has been previously configured. This message reports that an attempt to reload the router failed because SNMP reloads are not currently configured on the router. |
none |
"This is a notification message only. No action is required." |
|
SYS-4-RESBUFEXCEED |
4-Warning |
Resource user[chars] [chars] has exceeded the buffer [chars] threshold. configured [dec] Current usage :[dec]\n |
The Resource User specified in the error message has violated the configured threshold. Its buffer usage has gone above the threshold. RESBUFEXCEED notifications should be matched with the corresponding RESBUFRECOVER/RESBUFUNAPPLY notification. |
rmi |
"No action is required" |
|
SYS-4-RESGLOBALBUFEXCEED |
4-Warning |
Buffer usage has gone above buffer [chars] threshold configured by resource user[chars] [chars]\n configured [dec] Current usage :[dec]\n |
The global buffer usage has gone above the threshold of the RU specified in the error message. RESGLOBALBUFEXCEED notifications should be matched with the corresponding RESGLOBALBUFRECOVER/ RESGLOBALBUFUNAPPLY notification. |
rmi |
"No action is required" |
|
SYS-4-RESGLOBALBUFRECOVER |
4-Warning |
Buffer usage has gone below buffer [chars] threshold configured by resource user[chars] [chars]\n configured [dec] Current usage :[dec]\n |
The global buffer usage has gone below the threshold of the RU specified in the error message. |
rmi |
"No action is required" |
|
SYS-4-RESGLOBALBUFUNAPPLY |
4-Warning |
Global Buffer usage for resource user[chars] [chars] is no longer monitored for [chars] threshold.\n |
The global buffer usage configured by the Resource User specified in the error message is no longer monitored for the specified threshold. The corresponding policy is revoked |
rmi |
"No action is required" |
|
SYS-4-RESGLOBALMEMEXCEED |
4-Warning |
Global Memory has exceeded the [chars] threshold configure by resource user [chars]\n Pool: [chars] Used: %lu Threshold: %lu\n |
The memory pool specified in the error message is experiencing a low-memory condition. The amount of free memory available in the specified memory pool has dropped below the configured low-memory limit. RESGLOBALMEMEXCEED notifications should be matched with the corresponding RESGLOBALMEMRECOVER/RESGLOBALMEMUNAPPLY notification. |
rmi |
"No action is required" |
|
SYS-4-RESGLOBALMEMRECOVER |
4-Warning |
Global Memory has recovered after exceeding the [chars] threshold configure by resource user [chars]\n Pool: [chars] Used: %lu Threshold: %lu\n |
The memory pool specified in the error message has recovered from a low-memory condition and the free memory in that pool is now above the configured low-memory limit. |
rmi |
"No action is required" |
|
SYS-4-RESGLOBALMEMUNAPPLY |
4-Warning |
Global Memory Usage for resource user [chars] is no longer monitored for [chars] threshold. Pool: [chars]\n |
The memory pool specified in the error message configured by the specified Resource User is no longer monitored for low-memory condition. The corresponding policy is revoked |
rmi |
"No action is required" |
|
SYS-4-RESMEMEXCEED |
4-Warning |
Resource user [chars] has exceeded the [chars] memory threshold\nPool: [chars] Used: %lu Threshold: %lu \n |
The memory pool specified in the error message is experiencing a low-memory condition. The amount of free memory available in the specified memory pool has dropped below the configured low-memory limit. RESMEMEXCEED notifications should be matched with the corresponding RESMEMRECOVER/RESMEMUNAPPLY notification. |
rmi |
"No action is required" |
|
SYS-4-SDB_SANITY_ERR |
4-Warning |
sanity check failed for string [chars] |
The owner of this string must have freed their structure without letting the string database know |
os-logging |
"No action is required" |
|
SYS-4-SNMP_HOSTCONFIGSET |
4-Warning |
SNMP hostConfigSet request. Loading configuration from [inet] |
SNMP is reading the host configuration from a network host. |
none |
"This is a notification message only. No action is required." |
|
SYS-4-SNMP_HOSTCONFIGSET |
4-Warning |
SNMP hostConfigSet request. Loading configuration from [inet] |
SNMP is reading the host configuration from a network host. |
none |
"This is a notification message only. No action is required." |
|
SYS-4-SNMP_HOSTCONFIGSET |
4-Warning |
SNMP hostConfigSet request. Loading configuration from [inet] |
SNMP is reading the host configuration from a network host. |
none |
"This is a notification message only. No action is required." |
|
SYS-4-SNMP_HOSTCONFIGSET |
4-Warning |
SNMP hostConfigSet request. Loading configuration from [inet] |
SNMP is reading the host configuration from a network host. |
none |
"This is a notification message only. No action is required." |
|
SYS-4-SNMP_HOSTCONFIGSET |
4-Warning |
SNMP hostConfigSet request. Loading configuration from [inet] |
SNMP is reading the host configuration from a network host. |
none |
"This is a notification message only. No action is required." |
|
SYS-4-SNMP_HOSTCONFIGSET |
4-Warning |
SNMP hostConfigSet request. Loading configuration from [inet] |
SNMP is reading the host configuration from a network host. |
none |
"This is a notification message only. No action is required." |
|
SYS-4-SNMP_NETCONFIGSET |
4-Warning |
SNMP netConfigSet request. Loading configuration from [inet]. |
SNMP is reading the network configuration from a network host. |
none |
"This is a notification message only. No action is required." |
|
SYS-4-SNMP_NETCONFIGSET |
4-Warning |
SNMP netConfigSet request. Loading configuration from [inet]. |
SNMP is reading the network configuration from a network host. |
none |
"This is a notification message only. No action is required." |
|
SYS-4-SNMP_NETCONFIGSET |
4-Warning |
SNMP netConfigSet request. Loading configuration from [inet]. |
SNMP is reading the network configuration from a network host. |
none |
"This is a notification message only. No action is required." |
|
SYS-4-SNMP_NETCONFIGSET |
4-Warning |
SNMP netConfigSet request. Loading configuration from [inet]. |
SNMP is reading the network configuration from a network host. |
none |
"This is a notification message only. No action is required." |
|
SYS-4-SNMP_NETCONFIGSET |
4-Warning |
SNMP netConfigSet request. Loading configuration from [inet]. |
SNMP is reading the network configuration from a network host. |
none |
"This is a notification message only. No action is required." |
|
SYS-4-SNMP_NETCONFIGSET |
4-Warning |
SNMP netConfigSet request. Loading configuration from [inet]. |
SNMP is reading the network configuration from a network host. |
none |
"This is a notification message only. No action is required." |
|
SYS-4-SNMP_WRITENET |
4-Warning |
SNMP WriteNet request. Writing current configuration to [inet] |
SNMP is writing the current configuration to a network host. |
none |
"These are notification messages only. No action is required." |
|
SYS-4-SNMP_WRITENET |
4-Warning |
SNMP WriteNet request. Writing current configuration to [inet] |
SNMP is writing the current configuration to a network host. |
none |
"These are notification messages only. No action is required." |
|
SYS-4-SNMP_WRITENET |
4-Warning |
SNMP WriteNet request. Writing current configuration to [inet] |
SNMP is writing the current configuration to a network host. |
none |
"These are notification messages only. No action is required." |
|
SYS-4-SNMP_WRITENET |
4-Warning |
SNMP WriteNet request. Writing current configuration to [inet] |
SNMP is writing the current configuration to a network host. |
none |
"These are notification messages only. No action is required." |
|
SYS-4-SNMP_WRITENET |
4-Warning |
SNMP WriteNet request. Writing current configuration to [inet] |
SNMP is writing the current configuration to a network host. |
none |
"These are notification messages only. No action is required." |
|
SYS-4-SNMP_WRITENET |
4-Warning |
SNMP WriteNet request. Writing current configuration to [inet] |
SNMP is writing the current configuration to a network host. |
none |
"These are notification messages only. No action is required." |
|
SYS-4-THRESHOLD |
4-Warning |
Free Memory has dropped below low watermark. Pool: [chars] Free: %lu Threshold: %lu |
The memory pool specified in the error message is experiencing a low-memory condition. The amount of free memory available in the specified memory pool has dropped below the configured low-memory limit. |
- |
"No action is required" |
|
SYS-4-THRESHOLD_TK |
4-Warning |
Free Memory has dropped below low watermark. Pool: [chars] Free: %lu Threshold: %lu Tracekey: [chars] |
The memory pool specified in the error message is experiencing a low-memory condition. The amount of free memory available in the specified memory pool has dropped below the configured low-memory limit. |
- |
"No action is required" |
|
SYS-4-USERLOG_WARNING |
4-Warning |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-4-USERLOG_WARNING |
4-Warning |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-4-USERLOG_WARNING |
4-Warning |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-4-USERLOG_WARNING |
4-Warning |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-4-USERLOG_WARNING |
4-Warning |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-4-USERLOG_WARNING |
4-Warning |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-4-VRF_TABLE_INIT_WARNING |
4-Warning |
[chars] |
The number of VRF's obtained from the platform is zero |
os-logging |
"If the registry is not populated for the subsystem " "is not in the image then the return value will be " "FALSE" |
|
SYS-5-CONFIG |
5-Notice |
Configured from [chars] |
The router's configuration was changed. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-CONFIG |
5-Notice |
Configured from [chars] |
The router's configuration was changed. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-CONFIG |
5-Notice |
Configured from [chars] |
The router's configuration was changed. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-CONFIG |
5-Notice |
Configured from [chars] |
The router's configuration was changed. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-CONFIG |
5-Notice |
Configured from [chars] |
The router's configuration was changed. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-CONFIG |
5-Notice |
Configured from [chars] |
The router's configuration was changed. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-CONFIG_C |
5-Notice |
Running-config file is [chars] |
The router's configuration was changed. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-CONFIG_I |
5-Notice |
Configured from [chars] by [chars] |
The write of the system running configuration failed. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-5-CONFIG_I |
5-Notice |
Configured from [chars] by [chars] |
The write of the system running configuration failed. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-5-CONFIG_I |
5-Notice |
Configured from [chars] by [chars] |
The write of the system running configuration failed. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-5-CONFIG_I |
5-Notice |
Configured from [chars] by [chars] |
The write of the system running configuration failed. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-5-CONFIG_I |
5-Notice |
Configured from [chars] by [chars] |
The write of the system running configuration failed. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-5-CONFIG_I |
5-Notice |
Configured from [chars] by [chars] |
The write of the system running configuration failed. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-5-CONFIG_NV |
5-Notice |
Nonvolatile storage configured from [chars] |
The configuration was written successfully. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-CONFIG_NV |
5-Notice |
Nonvolatile storage configured from [chars] |
The configuration was written successfully. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-CONFIG_NV |
5-Notice |
Nonvolatile storage configured from [chars] |
The configuration was written successfully. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-CONFIG_NV |
5-Notice |
Nonvolatile storage configured from [chars] |
The configuration was written successfully. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-CONFIG_NV |
5-Notice |
Nonvolatile storage configured from [chars] |
The configuration was written successfully. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-CONFIG_NV |
5-Notice |
Nonvolatile storage configured from [chars] |
The configuration was written successfully. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-CONFIG_NV_I |
5-Notice |
Nonvolatile storage configured from [chars] by [chars] |
The write of the nonvolatile configuration failed. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-5-CONFIG_NV_I |
5-Notice |
Nonvolatile storage configured from [chars] by [chars] |
The write of the nonvolatile configuration failed. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-5-CONFIG_NV_I |
5-Notice |
Nonvolatile storage configured from [chars] by [chars] |
The write of the nonvolatile configuration failed. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-5-CONFIG_NV_I |
5-Notice |
Nonvolatile storage configured from [chars] by [chars] |
The write of the nonvolatile configuration failed. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-5-CONFIG_NV_I |
5-Notice |
Nonvolatile storage configured from [chars] by [chars] |
The write of the nonvolatile configuration failed. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-5-CONFIG_NV_I |
5-Notice |
Nonvolatile storage configured from [chars] by [chars] |
The write of the nonvolatile configuration failed. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-5-CONFIG_P |
5-Notice |
Configured programmatically by process [chars] from [chars] as [chars] |
The router's configuration was changed programmatically. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-CONFIG_R |
5-Notice |
Config Replace is [chars] |
The router's configuration was changed. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-FIFOBUS_ERR |
5-Notice |
Flow-control threshold on module [dec] has exceeded the default value. Threshold will be set to lower value |
The FIFO threshold values are monitored for flow-control. When the threshold value exceeds the default the value is set to new lower value |
Cat6000-env |
LOG_STD_NO_ACTION |
|
SYS-5-FIFOBUS_ERR |
5-Notice |
Flow-control threshold on module [dec] has exceeded the default value. Threshold will be set to lower value |
The FIFO threshold values are monitored for flow-control. When the threshold value exceeds the default the value is set to new lower value |
Cat6000-env |
LOG_STD_NO_ACTION |
|
SYS-5-FIFOBUS_ERR |
5-Notice |
Flow-control threshold on module [dec] has exceeded the default value. Threshold will be set to lower value |
The FIFO threshold values are monitored for flow-control. When the threshold value exceeds the default the value is set to new lower value |
Cat6000-env |
LOG_STD_NO_ACTION |
|
SYS-5-FIFOBUS_ERR |
5-Notice |
Flow-control threshold on module [dec] has exceeded the default value. Threshold will be set to lower value |
The FIFO threshold values are monitored for flow-control. When the threshold value exceeds the default the value is set to new lower value |
Cat6000-env |
LOG_STD_NO_ACTION |
|
SYS-5-FIFOBUS_ERR |
5-Notice |
Flow-control threshold on module [dec] has exceeded the default value. Threshold will be set to lower value |
The FIFO threshold values are monitored for flow-control. When the threshold value exceeds the default the value is set to new lower value |
Cat6000-env |
LOG_STD_NO_ACTION |
|
SYS-5-FIFOBUS_ERR |
5-Notice |
Flow-control threshold on module [dec] has exceeded the default value. Threshold will be set to lower value |
The FIFO threshold values are monitored for flow-control. When the threshold value exceeds the default the value is set to new lower value |
Cat6000-env |
LOG_STD_NO_ACTION |
|
SYS-5-FREEMEMLOW_NOTIFY |
5-Notice |
Top memory allocators could not be displayed currently at low memory situation refer show memory output/crashinfo file. |
IOSD memory consumption exceeded 90% Top memory allocator could not be displayed. Top allocators can be found from show memory output or crashinfo file. |
mem |
"No action is required" |
|
SYS-5-FREEMEMRECOVER |
5-Notice |
Free Memory has recovered above low watermark Pool: [chars] Free: %lu freemem_lwm: %lu |
The memory pool specified in error message has recovered from a low-memory condition and free memory in that pool is now above the configured low-memory limit in the system . |
- |
"No action is required" |
|
SYS-5-FREEMEMRECOVER |
5-Notice |
Free Memory has recovered above low watermark\nPool: [chars] Free: %lu Threshold: %lu\n |
The memory pool specified in the error message has recovered from a low-memory condition and the free memory in that pool is now above the configured low-memory limit. |
- |
"No action is required" |
|
SYS-5-FREEMEMRECOVER |
5-Notice |
Free Memory has recovered above low watermark\nPool: [chars] Free: %lu Threshold: %lu\n |
The memory pool specified in the error message has recovered from a low-memory condition and the free memory in that pool is now above the configured low-memory limit. |
- |
"No action is required" |
|
SYS-5-FREEMEMRECOVER |
5-Notice |
Free Memory has recovered above low watermark\nPool: [chars] Free: %lu Threshold: %lu\n |
The memory pool specified in the error message has recovered from a low-memory condition and the free memory in that pool is now above the configured low-memory limit. |
- |
"No action is required" |
|
SYS-5-FREEMEMRECOVER |
5-Notice |
Free Memory has recovered above low watermark\nPool: [chars] Free: %lu Threshold: %lu\n |
The memory pool specified in the error message has recovered from a low-memory condition and the free memory in that pool is now above the configured low-memory limit. |
- |
"No action is required" |
|
SYS-5-FREEMEMRECOVER |
5-Notice |
Free Memory has recovered above low watermark\nPool: [chars] Free: %lu Threshold: %lu\n |
The memory pool specified in the error message has recovered from a low-memory condition and the free memory in that pool is now above the configured low-memory limit. |
- |
"No action is required" |
|
SYS-5-GLOBALBUFRECOVER |
5-Notice |
Buffer usage has gone below global buffer [chars] threshold\nconfigured [dec] Current usage :[dec]\n |
global buffer usage has gone below the configured limit. This is the indication of recovery |
rmi |
"No action is required" |
|
SYS-5-GLOBALBUFUNAPPLY |
5-Notice |
Global Buffer usage is no longer monitored for [chars] threshold\n |
Global buffer usage is no longer monitored for the specified threshold. The corresponding policy is revoked |
rmi |
"No action is required" |
|
SYS-5-GLOBALMEMEXCEED |
5-Notice |
Global Memory has exceeded the [chars] threshold\nPool: [chars] Used: %lu Threshold: %lu\n |
The memory pool specified in the error message has exceeded the global memory threshold configured.the memory consumed in that pool has exceeded the configured limit. GLOBALMEMEXCEED notificatons should be matched with the corresponding GLOBALMEMRECOVER/GLOBALMEMUNAPPLY notification. |
rmi |
"No action is required" |
|
SYS-5-GLOBALMEMRECOVER |
5-Notice |
Global Memory has recovered after exceeding [chars] threshold\n Pool: [chars] Used: %lu Threshold: %lu\n |
The memory pool specified in the error message has recovered from a low-memory condition and the memory consumed in that pool is now below the configured limit. |
rmi |
"No action is required" |
|
SYS-5-GLOBALMEMUNAPPLY |
5-Notice |
Global Memory usage is no longer monitored for [chars] threshold. Pool: [chars]\n |
The memory pool specified in the error message is no longer monitored for low-memory condition. The corresponding policy is revoked |
rmi |
"No action is required" |
|
SYS-5-LOG_CONFIG_CHANGE |
5-Notice |
[chars] |
The user has changed the syslog logging configuration. |
os-logging |
LOG_STD_NO_ACTION |
|
SYS-5-LOGGING_START |
5-Notice |
Logging enabled - [chars] \n |
Syslog logging has been enabled by the user. From now on syslog messages will be delivered to all configured destinations. |
os-logging |
LOG_STD_NO_ACTION |
|
SYS-5-LOGGING_STOP |
5-Notice |
Logging disabled - [chars] \n |
Syslog logging has been disabled by the user from now on syslog message will not be received by the syslog servers or hosts will not be receiving the syslog messages |
os-logging |
LOG_STD_NO_ACTION |
|
SYS-5-OUTSETUP |
5-Notice |
Configuration file [chars] accepted aborting setup |
A configuration was accepted over the network so the setup session will be aborted. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-OUTSETUP |
5-Notice |
Configuration file [chars] accepted aborting setup |
A configuration was accepted over the network so the setup session will be aborted. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-OUTSETUP |
5-Notice |
Configuration file [chars] accepted aborting setup |
A configuration was accepted over the network so the setup session will be aborted. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-OUTSETUP |
5-Notice |
Configuration file [chars] accepted aborting setup |
A configuration was accepted over the network so the setup session will be aborted. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-OUTSETUP |
5-Notice |
Configuration file [chars] accepted aborting setup |
A configuration was accepted over the network so the setup session will be aborted. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-OUTSETUP |
5-Notice |
Configuration file [chars] accepted aborting setup |
A configuration was accepted over the network so the setup session will be aborted. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-PRIV_AUTH_FAIL |
5-Notice |
Authentication to privilege level [dec] failed by [chars][chars] |
- |
os-logging |
"This is a notification message only. No action is required. " "To disable this particular logging feature issue the " "<CmdBold>no logging userinfo<NoCmdBold> command from the " "global configuration mode." |
|
SYS-5-PRIV_AUTH_FAIL |
5-Notice |
Authentication to Privilage level [dec] failed by[chars][chars] |
- |
os-logging |
"This is a notification message only. No action is required. " "To disable this particular logging feature issue the " "<CmdBold>no logging userinfo<NoCmdBold> command from the " "global configuration mode." |
|
SYS-5-PRIV_AUTH_FAIL |
5-Notice |
Authentication to Privilage level [dec] failed by[chars][chars] |
- |
os-logging |
"This is a notification message only. No action is required. " "To disable this particular logging feature issue the " "<CmdBold>no logging userinfo<NoCmdBold> command from the " "global configuration mode." |
|
SYS-5-PRIV_AUTH_FAIL |
5-Notice |
Authentication to Privilage level [dec] failed by[chars][chars] |
- |
os-logging |
"This is a notification message only. No action is required. " "To disable this particular logging feature issue the " "<CmdBold>no logging userinfo<NoCmdBold> command from the " "global configuration mode." |
|
SYS-5-PRIV_AUTH_FAIL |
5-Notice |
Authentication to Privilage level [dec] failed by[chars][chars] |
- |
os-logging |
"This is a notification message only. No action is required. " "To disable this particular logging feature issue the " "<CmdBold>no logging userinfo<NoCmdBold> command from the " "global configuration mode." |
|
SYS-5-PRIV_AUTH_FAIL |
5-Notice |
Authentication to Privilage level [dec] failed by[chars][chars] |
- |
os-logging |
"This is a notification message only. No action is required. " "To disable this particular logging feature issue the " "<CmdBold>no logging userinfo<NoCmdBold> command from the " "global configuration mode." |
|
SYS-5-PRIV_AUTH_PASS |
5-Notice |
Privilege level set to [dec] by[chars][chars] |
- |
os-logging |
"This is a notification message only. No action is required. " "To disable this particular logging feature issue the " "<CmdBold>no logging userinfo<NoCmdBold> command from the " "global configuration mode." |
|
SYS-5-PRIV_AUTH_PASS |
5-Notice |
Privilege level set to [dec] by[chars][chars] |
- |
os-logging |
"This is a notification message only. No action is required. " "To disable this particular logging feature issue the " "<CmdBold>no logging userinfo<NoCmdBold> command from the " "global configuration mode." |
|
SYS-5-PRIV_AUTH_PASS |
5-Notice |
Privilege level set to [dec] by[chars][chars] |
- |
os-logging |
"This is a notification message only. No action is required. " "To disable this particular logging feature issue the " "<CmdBold>no logging userinfo<NoCmdBold> command from the " "global configuration mode." |
|
SYS-5-PRIV_AUTH_PASS |
5-Notice |
Privilege level set to [dec] by[chars][chars] |
- |
os-logging |
"This is a notification message only. No action is required. " "To disable this particular logging feature issue the " "<CmdBold>no logging userinfo<NoCmdBold> command from the " "global configuration mode." |
|
SYS-5-PRIV_AUTH_PASS |
5-Notice |
Privilege level set to [dec] by[chars][chars] |
- |
os-logging |
"This is a notification message only. No action is required. " "To disable this particular logging feature issue the " "<CmdBold>no logging userinfo<NoCmdBold> command from the " "global configuration mode." |
|
SYS-5-PRIV_AUTH_PASS |
5-Notice |
Privilege level set to [dec] by[chars][chars] |
- |
os-logging |
"This is a notification message only. No action is required. " "To disable this particular logging feature issue the " "<CmdBold>no logging userinfo<NoCmdBold> command from the " "global configuration mode." |
|
SYS-5-PRIV_I |
5-Notice |
Privilege level set to [dec] by[chars][chars] |
- |
os-logging |
"This is a notification message only. No action is required. " "To disable this particular logging feature issue the " "<CmdBold>no logging userinfo<NoCmdBold> command from the " "global configuration mode." |
|
SYS-5-PRIV_I |
5-Notice |
Privilege level set to [dec] by[chars][chars] |
- |
os-logging |
"This is a notification message only. No action is required. " "To disable this particular logging feature issue the " "<CmdBold>no logging userinfo<NoCmdBold> command from the " "global configuration mode." |
|
SYS-5-PRIV_I |
5-Notice |
Privilege level set to [dec] by[chars][chars] |
Switchcards in RFSW has been inserted/removed. |
cmts-redundancy |
"." |
|
SYS-5-PRIV_I |
5-Notice |
Privilege level set to [dec] by[chars][chars] |
- |
os-logging |
"This is a notification message only. No action is required. " "To disable this particular logging feature issue the " "<CmdBold>no logging userinfo<NoCmdBold> command from the " "global configuration mode." |
|
SYS-5-PRIV_I |
5-Notice |
Privilege level set to [dec] by[chars][chars] |
- |
os-logging |
"This is a notification message only. No action is required. " "To disable this particular logging feature issue the " "<CmdBold>no logging userinfo<NoCmdBold> command from the " "global configuration mode." |
|
SYS-5-PRIV_I |
5-Notice |
Privilege level set to [dec] by[chars][chars] |
- |
os-logging |
"This is a notification message only. No action is required. " "To disable this particular logging feature issue the " "<CmdBold>no logging userinfo<NoCmdBold> command from the " "global configuration mode." |
|
SYS-5-RELOAD |
5-Notice |
Reload requested[chars] |
A reload or restart was requested. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-RELOAD |
5-Notice |
Reload requested[chars] |
A reload or restart was requested. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-RELOAD |
5-Notice |
Reload requested[chars] |
A reload or restart was requested. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-RELOAD |
5-Notice |
Reload requested[chars] |
A reload or restart was requested. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-RELOAD |
5-Notice |
Reload requested[chars] |
A reload or restart was requested. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-RELOAD |
5-Notice |
Reload requested[chars] |
A reload or restart was requested. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-RESBUFRECOVER |
5-Notice |
Resource user[chars] [chars] has recovered after exceeding the buffer [chars] threshold. configured [dec] Current usage :[dec]\n |
The Resource User specified in the error message has recovered from the high buffer usage. Its usage has gone below the threshold |
rmi |
"No action is required" |
|
SYS-5-RESBUFUNAPPLY |
5-Notice |
Buffer Usage of resource user[chars] [chars] is no longer monitored for the [chars] threshold.\n |
The Resource User specified in the error message is no longer monitored for high buffer usage. The corresponding policy is revoked |
rmi |
"No action is required" |
|
SYS-5-RESMEMRECOVER |
5-Notice |
Resource user [chars] has recovered after exceeding the [chars] memory threshold\nPool: [chars] Used: [dec] Threshold :[dec] \n |
The memory pool specified in the error message is recovering from a low-memory condition. The amount of free memory available in the specified memory pool has recovered above the configured low-memory limit. |
rmi |
"No action is required" |
|
SYS-5-RESMEMUNAPPLY |
5-Notice |
Memory usage of Resource user [chars] is no longer monitored for [chars] threshold. Pool: [chars]\n |
The memory pool specified in the error message is no longer monitored for low-memory condition as configured by the Resource User specified. The corresponding policy is revoked. |
rmi |
"No action is required" |
|
SYS-5-RESTART |
5-Notice |
System restarted --\n[chars] |
A reload or restart was requested. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-RESTART |
5-Notice |
System restarted --\n[chars] |
A reload or restart was requested. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-RESTART |
5-Notice |
System restarted --\n[chars] |
A reload or restart was requested. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-RESTART |
5-Notice |
System restarted --\n[chars] |
A reload or restart was requested. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-RESTART |
5-Notice |
System restarted --\n[chars] |
A reload or restart was requested. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-RESTART |
5-Notice |
System restarted --\n[chars] |
A reload or restart was requested. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-SCHEDULED_RELOAD |
5-Notice |
Reload requested for [chars] |
A scheduled reload has been requested for the router. |
none |
"No action is required." |
|
SYS-5-SCHEDULED_RELOAD |
5-Notice |
Reload requested for [chars] |
A scheduled reload has been requested for the router. |
none |
"No action is required." |
|
SYS-5-SCHEDULED_RELOAD |
5-Notice |
Reload requested for [chars] |
A scheduled reload has been requested for the router. |
none |
"No action is required." |
|
SYS-5-SCHEDULED_RELOAD |
5-Notice |
Reload requested for [chars] |
A scheduled reload has been requested for the router. |
none |
"No action is required." |
|
SYS-5-SCHEDULED_RELOAD |
5-Notice |
Reload requested for [chars] |
A scheduled reload has been requested for the router. |
none |
"No action is required." |
|
SYS-5-SCHEDULED_RELOAD |
5-Notice |
Reload requested for [chars] |
A scheduled reload has been requested for the router. |
none |
"No action is required." |
|
SYS-5-SCHEDULED_RELOAD_CANCELLED |
5-Notice |
Scheduled reload cancelled at [chars] |
A scheduled reload that was requested for the router has been cancelled. |
none |
"No action is required." |
|
SYS-5-SCHEDULED_RELOAD_CANCELLED |
5-Notice |
Scheduled reload cancelled at [chars] |
A scheduled reload that was requested for the router has been cancelled. |
none |
"No action is required." |
|
SYS-5-SCHEDULED_RELOAD_CANCELLED |
5-Notice |
Scheduled reload cancelled at [chars] |
A scheduled reload that was requested for the router has been cancelled. |
none |
"No action is required." |
|
SYS-5-SCHEDULED_RELOAD_CANCELLED |
5-Notice |
Scheduled reload cancelled at [chars] |
A scheduled reload that was requested for the router has been cancelled. |
none |
"No action is required." |
|
SYS-5-SCHEDULED_RELOAD_CANCELLED |
5-Notice |
Scheduled reload cancelled at [chars] |
A scheduled reload that was requested for the router has been cancelled. |
none |
"No action is required." |
|
SYS-5-SCHEDULED_RELOAD_CANCELLED |
5-Notice |
Scheduled reload cancelled at [chars] |
A scheduled reload that was requested for the router has been cancelled. |
none |
"No action is required." |
|
SYS-5-SWITCHOVER |
5-Notice |
Switchover requested[chars] |
A switchover was requested. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-SWITCHOVER |
5-Notice |
Switchover requested[chars] |
A switchover was requested. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-SWITCHOVER |
5-Notice |
Switchover requested[chars] |
A switchover was requested. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-SWITCHOVER |
5-Notice |
Switchover requested[chars] |
A switchover was requested. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-SWITCHOVER |
5-Notice |
Switchover requested[chars] |
A switchover was requested. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-SWITCHOVER |
5-Notice |
Switchover requested[chars] |
A switchover was requested. |
none |
"This is a notification message only. No action is required." |
|
SYS-5-TABLEERR |
5-Notice |
[chars] table [chars] damaged: [chars]. |
An internal table entry became corrupt. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-5-TABLEERR |
5-Notice |
[chars] table [chars] damaged: [chars]. |
An internal table entry became corrupt. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-5-TABLEERR |
5-Notice |
[chars] table [chars] damaged: [chars]. |
An internal table entry became corrupt. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-5-TABLEERR |
5-Notice |
[chars] table [chars] damaged: [chars]. |
An internal table entry became corrupt. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-5-TABLEERR |
5-Notice |
[chars] table [chars] damaged: [chars]. |
An internal table entry became corrupt. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-5-TABLEERR |
5-Notice |
[chars] table [chars] damaged: [chars]. |
An internal table entry became corrupt. |
- |
"Copy the message exactly as it appears and report it your technical " "support representative." |
|
SYS-5-USERLOG_NOTICE |
5-Notice |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-5-USERLOG_NOTICE |
5-Notice |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-5-USERLOG_NOTICE |
5-Notice |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-5-USERLOG_NOTICE |
5-Notice |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-5-USERLOG_NOTICE |
5-Notice |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-5-USERLOG_NOTICE |
5-Notice |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-6-BADSHAREINFO |
6-Information |
[chars] packet [hec] has a zero reference count freeing pid = [hec] \n\ freeing pc = [hec] [chars]. |
Provides additional information about original freer of packet. |
- |
- |
|
SYS-6-BADSHAREINFO |
6-Information |
[chars] packet [hec] has a zero reference count freeing pid = [hec] \n\ freeing pc = [hec] [chars]. |
Provides additional information about original freer of packet. |
- |
- |
|
SYS-6-BADSHAREINFO |
6-Information |
[chars] packet [hec] has a zero reference count freeing pid = [hec] \n\ freeing pc = [hec] [chars]. |
Provides additional information about original freer of packet. |
- |
- |
|
SYS-6-BADSHAREINFO |
6-Information |
[chars] packet [hec] has a zero reference count freeing pid = [hec] \n\ freeing pc = [hec] [chars]. |
Provides additional information about original freer of packet. |
- |
- |
|
SYS-6-BADSHAREINFO |
6-Information |
[chars] packet [hec] has a zero reference count freeing pid = [hec] \n\ freeing pc = [hec] [chars]. |
Provides additional information about original freer of packet. |
- |
- |
|
SYS-6-BADSHAREINFO |
6-Information |
[chars] packet [hec] has a zero reference count freeing pid = [hec] \n\ freeing pc = [hec] [chars]. |
Provides additional information about original freer of packet. |
- |
- |
|
SYS-6-BLKINFO |
6-Information |
[chars]blk [hec] words [dec] alloc [hec] [chars] dealloc [hec] rfcnt [hec] |
This is an auxiliary message to several memory-related messages. It provides a formatted display of some of the information in the header of a corrupted data block. |
Include this error message in the DDTS that was written for\n\ the previously printed error message. |
"This message provides additional information only. Copy the error " "message exactly as it appears and report it to your technical support " "representative as part of the previously printed error message." |
|
SYS-6-BLKINFO |
6-Information |
[chars]blk [hec] words [dec] alloc [hec] [chars] dealloc [hec] rfcnt [hec] |
This is an auxiliary message to several memory-related messages. It provides a formatted display of some of the information in the header of a corrupted data block. |
Include this error message in the DDTS that was written for\n\ the previously printed error message. |
"This message provides additional information only. Copy the error " "message exactly as it appears and report it to your technical support " "representative as part of the previously printed error message." |
|
SYS-6-BLKINFO |
6-Information |
[chars]blk [hec] words [dec] alloc [hec] [chars] dealloc [hec] rfcnt [hec] |
This is an auxiliary message to several memory-related messages. It provides a formatted display of some of the information in the header of a corrupted data block. |
Include this error message in the DDTS that was written for\n\ the previously printed error message. |
"This message provides additional information only. Copy the error " "message exactly as it appears and report it to your technical support " "representative as part of the previously printed error message." |
|
SYS-6-BLKINFO |
6-Information |
[chars]blk [hec] words [dec] alloc [hec] [chars] dealloc [hec] rfcnt [hec] |
This is an auxiliary message to several memory-related messages. It provides a formatted display of some of the information in the header of a corrupted data block. |
Include this error message in the DDTS that was written for\n\ the previously printed error message. |
"This message provides additional information only. Copy the error " "message exactly as it appears and report it to your technical support " "representative as part of the previously printed error message." |
|
SYS-6-BLKINFO |
6-Information |
[chars]blk [hec] words [dec] alloc [hec] [chars] dealloc [hec] rfcnt [hec] |
This is an auxiliary message to several memory-related messages. It provides a formatted display of some of the information in the header of a corrupted data block. |
Include this error message in the DDTS that was written for\n\ the previously printed error message. |
"This message provides additional information only. Copy the error " "message exactly as it appears and report it to your technical support " "representative as part of the previously printed error message." |
|
SYS-6-BLKINFO |
6-Information |
[chars]blk [hec] words [dec] alloc [hec] [chars] dealloc [hec] rfcnt [hec] |
This is an auxiliary message to several memory-related messages. It provides a formatted display of some of the information in the header of a corrupted data block. |
Include this error message in the DDTS that was written for\n\ the previously printed error message. |
"This message provides additional information only. Copy the error " "message exactly as it appears and report it to your technical support " "representative as part of the previously printed error message." |
|
SYS-6-BOOT_MESSAGES |
6-Information |
Messages above this line are from the boot loader.\n |
At least one informational or error message was printed by the boot loader. |
- |
"If the system image was loaded no action is recommended. If the " "system image did not load as configured send a log file and " "configuration information to your technical support representative." |
|
SYS-6-BOOT_MESSAGES |
6-Information |
Messages above this line are from the boot loader.\n |
At least one informational or error message was printed by the boot loader. |
- |
"If the system image was loaded no action is recommended. If the " "system image did not load as configured send a log file and " "configuration information to your technical support representative." |
|
SYS-6-BOOT_MESSAGES |
6-Information |
Messages above this line are from the boot loader.\n |
At least one informational or error message was printed by the boot loader. |
- |
"If the system image was loaded no action is recommended. If the " "system image did not load as configured send a log file and " "configuration information to your technical support representative." |
|
SYS-6-BOOT_MESSAGES |
6-Information |
Messages above this line are from the boot loader.\n |
At least one informational or error message was printed by the boot loader. |
- |
"If the system image was loaded no action is recommended. If the " "system image did not load as configured send a log file and " "configuration information to your technical support representative." |
|
SYS-6-BOOT_MESSAGES |
6-Information |
Messages above this line are from the boot loader.\n |
At least one informational or error message was printed by the boot loader. |
- |
"If the system image was loaded no action is recommended. If the " "system image did not load as configured send a log file and " "configuration information to your technical support representative." |
|
SYS-6-BOOT_MESSAGES |
6-Information |
Messages above this line are from the boot loader.\n |
At least one informational or error message was printed by the boot loader. |
- |
"If the system image was loaded no action is recommended. If the " "system image did not load as configured send a log file and " "configuration information to your technical support representative." |
|
SYS-6-BOOTTIME |
6-Information |
Time taken to reboot after reload = %-4d seconds |
This is an informational message for the user. This provides the time taken for the router to come up after reload or crash. The time is actually the difference between the last crash and a successive boot. If autoboot was not set and router is in rommon for a long time then the reload time shown could be large. |
- |
"No action required." |
|
SYS-6-BOOTTIME |
6-Information |
Time taken to reboot after reload = %-4d seconds |
This is an informational message for the user. This provides the time taken for the router to come up after reload or crash. The time is actually the difference between the last crash and a successive boot. If autoboot was not set and router is in rommon for a long time then the reload time shown could be large. |
- |
"No action required." |
|
SYS-6-BOOTTIME |
6-Information |
Time taken to reboot after reload = %-4d seconds |
This is an informational message for the user. This provides the time taken for the router to come up after reload or crash. The time is actually the difference between the last crash and a successive boot. If autoboot was not set and router is in rommon for a long time then the reload time shown could be large. |
- |
"No action required." |
|
SYS-6-BOOTTIME |
6-Information |
Time taken to reboot after reload = %-4d seconds |
This is an informational message for the user. This provides the time taken for the router to come up after reload or crash. The time is actually the difference between the last crash and a successive boot. If autoboot was not set and router is in rommon for a long time then the reload time shown could be large. |
- |
"No action required." |
|
SYS-6-BOOTTIME |
6-Information |
Time taken to reboot after reload = %-4d seconds |
This is an informational message for the user. This provides the time taken for the router to come up after reload or crash. The time is actually the difference between the last crash and a successive boot. If autoboot was not set and router is in rommon for a long time then the reload time shown could be large. |
- |
"No action required." |
|
SYS-6-BOOTTIME |
6-Information |
Time taken to reboot after reload = %-4d seconds |
This is an informational message for the user. This provides the time taken for the router to come up after reload or crash. The time is actually the difference between the last crash and a successive boot. If autoboot was not set and router is in rommon for a long time then the reload time shown could be large. |
- |
"No action required." |
|
SYS-6-CLOCKUPDATE |
6-Information |
System clock has been updated from [chars] to [chars] configured from [chars] by [chars]. |
This message indicates that the system clock has been modified. |
- |
"This is informational message." |
|
SYS-6-CLOCKUPDATE |
6-Information |
System clock has been updated from [chars] to [chars] configured from [chars] by [chars]. |
This message indicates that the system clock has been modified. |
- |
"This is informational message." |
|
SYS-6-CLOCKUPDATE |
6-Information |
System clock has been updated from [chars] to [chars] configured from [chars] by [chars]. |
This message indicates that the system clock has been modified. |
- |
"This is informational message." |
|
SYS-6-CLOCKUPDATE |
6-Information |
System clock has been updated from [chars] to [chars] configured from [chars] by [chars]. |
This message indicates that the system clock has been modified. |
- |
"This is informational message." |
|
SYS-6-CLOCKUPDATE |
6-Information |
System clock has been updated from [chars] to [chars] configured from [chars] by [chars]. |
This message indicates that the system clock has been modified. |
- |
"This is informational message." |
|
SYS-6-CLOCKUPDATE |
6-Information |
System clock has been updated from [chars] to [chars] configured from [chars] by [chars]. |
This message indicates that the system clock has been modified. |
- |
"This is informational message." |
|
SYS-6-CPURESFALLING |
6-Information |
[chars][chars] is no longer seeing [chars] high cpu at [chars] level for the configured [chars] limit [dec]%% current value [dec]%% |
CPU usage has returned to normal after crossing over from a threshold of high usage. Any process that was disabled during the period of high CPU use can now be enabled. |
- |
"No action is required" |
|
SYS-6-CPURESFALLING |
6-Information |
[chars][chars] is no longer seeing [chars] high cpu at [chars] level for the configured [chars] limit [dec]%% current value [dec]%% |
CPU usage has returned to normal after crossing over from a threshold of high usage. Any process that was disabled during the period of high CPU use can now be enabled. |
- |
"No action is required" |
|
SYS-6-CPURESFALLING |
6-Information |
[chars][chars] is no longer seeing [chars] high cpu at [chars] level for the configured [chars] limit [dec]%% current value [dec]%% |
CPU usage has returned to normal after crossing over from a threshold of high usage. Any process that was disabled during the period of high CPU use can now be enabled. |
- |
"No action is required" |
|
SYS-6-CPURESFALLING |
6-Information |
[chars][chars] is no longer seeing [chars] high cpu at [chars] level for the configured [chars] limit [dec]%% current value [dec]%% |
CPU usage has returned to normal after crossing over from a threshold of high usage. Any process that was disabled during the period of high CPU use can now be enabled. |
- |
"No action is required" |
|
SYS-6-CPURESFALLING |
6-Information |
[chars][chars] is no longer seeing [chars] high cpu at [chars] level for the configured [chars] limit [dec]%% current value [dec]%% |
CPU usage has returned to normal after crossing over from a threshold of high usage. Any process that was disabled during the period of high CPU use can now be enabled. |
- |
"No action is required" |
|
SYS-6-CPURESFALLING |
6-Information |
[chars][chars] is no longer seeing [chars] high cpu at [chars] level for the configured [chars] limit [dec]%% current value [dec]%% |
CPU usage has returned to normal after crossing over from a threshold of high usage. Any process that was disabled during the period of high CPU use can now be enabled. |
- |
"No action is required" |
|
SYS-6-CPURESUNAPPLY |
6-Information |
[chars][chars] is no longer monitoring [chars] cpu at [chars] level for the configured [chars] limit. |
CPU usage is no loger monitored for the configured threshold level mentioned in the error message The corresponding policy is revoked. |
- |
"No action is required" |
|
SYS-6-CPURESUNAPPLY |
6-Information |
[chars][chars] is no longer monitoring [chars] cpu at [chars] level for the configured [chars] limit. |
CPU usage is no loger monitored for the configured threshold level mentioned in the error message The corresponding policy is revoked. |
- |
"No action is required" |
|
SYS-6-CPURESUNAPPLY |
6-Information |
[chars][chars] is no longer monitoring [chars] cpu at [chars] level for the configured [chars] limit. |
CPU usage is no loger monitored for the configured threshold level mentioned in the error message The corresponding policy is revoked. |
- |
"No action is required" |
|
SYS-6-CPURESUNAPPLY |
6-Information |
[chars][chars] is no longer monitoring [chars] cpu at [chars] level for the configured [chars] limit. |
CPU usage is no loger monitored for the configured threshold level mentioned in the error message The corresponding policy is revoked. |
- |
"No action is required" |
|
SYS-6-CPURESUNAPPLY |
6-Information |
[chars][chars] is no longer monitoring [chars] cpu at [chars] level for the configured [chars] limit. |
CPU usage is no loger monitored for the configured threshold level mentioned in the error message The corresponding policy is revoked. |
- |
"No action is required" |
|
SYS-6-CPURESUNAPPLY |
6-Information |
[chars][chars] is no longer monitoring [chars] cpu at [chars] level for the configured [chars] limit. |
CPU usage is no loger monitored for the configured threshold level mentioned in the error message The corresponding policy is revoked. |
- |
"No action is required" |
|
SYS-6-INVALID_BOOTTIME |
6-Information |
Time since last reboot not available |
This is an informational message for the user. The time taken for the router to come up after OIR is not available. |
- |
"No action required." |
|
SYS-6-INVALID_BOOTTIME |
6-Information |
Time since last reboot not available |
This is an informational message for the user. The time taken for the router to come up after OIR is not available. |
- |
"No action required." |
|
SYS-6-INVALID_BOOTTIME |
6-Information |
Time since last reboot not available |
This is an informational message for the user. The time taken for the router to come up after OIR is not available. |
- |
"No action required." |
|
SYS-6-INVALID_BOOTTIME |
6-Information |
Time since last reboot not available |
This is an informational message for the user. The time taken for the router to come up after OIR is not available. |
- |
"No action required." |
|
SYS-6-INVALID_BOOTTIME |
6-Information |
Time since last reboot not available |
This is an informational message for the user. The time taken for the router to come up after OIR is not available. |
- |
"No action required." |
|
SYS-6-INVALID_BOOTTIME |
6-Information |
Time since last reboot not available |
This is an informational message for the user. The time taken for the router to come up after OIR is not available. |
- |
"No action required." |
|
SYS-6-LAST_RELOAD_BY_MEM_PRESSURE_CPU |
6-Information |
Last reload was triggered because CPU Usage due to Memory Pressure exceeds threshold |
This is an informational message for the user to indicate the reason behind the last reload which was triggered by forcefully crashing top N memory intensive processes because system encountered low-memory pressure. By looking at the core-files developer may be able to narrow down the cause of the memory depletion. |
- |
"This is a notification message only. No action is required." |
|
SYS-6-LOGGING_BUGINF |
6-Information |
Logging of buginf debugs was [chars] |
All calls to debugging have been disabled in Cisco IOS software as a result the user entering the <CmdBold>no logging buginf<NoCmdBold> command. This command is used to avoid a situation where a large amount of debugging calls might overload the processor CPU hog condition. This |
os-logging |
"This is an informational message only. No action is required." |
|
SYS-6-LOGGING_BUGINF |
6-Information |
Logging of buginf debugs was [chars] |
All calls to debugging have been disabled in Cisco IOS software as a result the user entering the <CmdBold>no logging buginf<NoCmdBold> command. This command is used to avoid a situation where a large amount of debugging calls might overload the processor CPU hog condition. This |
os-logging |
"This is an informational message only. No action is required." |
|
SYS-6-LOGGING_BUGINF |
6-Information |
Logging of buginf debugs was [chars] |
All calls to debugging have been disabled in Cisco IOS software as a result the user entering the <CmdBold>no logging buginf<NoCmdBold> command. This command is used to avoid a situation where a large amount of debugging calls might overload the processor CPU hog condition. This |
os-logging |
"This is an informational message only. No action is required." |
|
SYS-6-LOGGING_BUGINF |
6-Information |
Logging of buginf debugs was [chars] |
All calls to debugging have been disabled in Cisco IOS software as a result the user entering the <CmdBold>no logging buginf<NoCmdBold> command. This command is used to avoid a situation where a large amount of debugging calls might overload the processor CPU hog condition. This |
os-logging |
"This is an informational message only. No action is required." |
|
SYS-6-LOGGING_BUGINF |
6-Information |
Logging of buginf debugs was [chars] |
All calls to debugging have been disabled in Cisco IOS software as a result the user entering the <CmdBold>no logging buginf<NoCmdBold> command. This command is used to avoid a situation where a large amount of debugging calls might overload the processor CPU hog condition. This |
os-logging |
"This is an informational message only. No action is required." |
|
SYS-6-LOGGING_BUGINF |
6-Information |
Logging of buginf debugs was [chars] |
All calls to debugging have been disabled in Cisco IOS software as a result the user entering the <CmdBold>no logging buginf<NoCmdBold> command. This command is used to avoid a situation where a large amount of debugging calls might overload the processor CPU hog condition. This |
os-logging |
"This is an informational message only. No action is required." |
|
SYS-6-LOGGING_MOVE |
6-Information |
User [chars] has activated the logging persistent move command. |
The Common Criteria CC certification requires a log message to |
os-logging |
"This message is for information only. No action is required." |
|
SYS-6-LOGGINGHOST_STARTSTOP |
6-Information |
Logging to host [chars][chars][chars][chars] |
Syslog logging to specified server or hostvrf has started or stopped |
os-logging |
LOG_STD_NO_ACTION |
|
SYS-6-LOGGINGHOST_STARTSTOP |
6-Information |
Logging to host [chars][chars][chars][chars] |
Syslog logging to specified server or hostvrf has started or stopped |
os-logging |
LOG_STD_NO_ACTION |
|
SYS-6-LOGGINGHOST_STARTSTOP |
6-Information |
Logging to host [chars][chars][chars][chars] |
Syslog logging to specified server or hostvrf has started or stopped |
os-logging |
LOG_STD_NO_ACTION |
|
SYS-6-LOGGINGHOST_STARTSTOP |
6-Information |
Logging to host [chars][chars][chars][chars] |
Syslog logging to specified server or hostvrf has started or stopped |
os-logging |
LOG_STD_NO_ACTION |
|
SYS-6-LOGGINGHOST_STARTSTOP |
6-Information |
Logging to host [chars][chars][chars][chars] |
Syslog logging to specified server or hostvrf has started or stopped |
os-logging |
LOG_STD_NO_ACTION |
|
SYS-6-LOGGINGHOST_STARTSTOP |
6-Information |
Logging to host [chars][chars][chars][chars] |
Syslog logging to specified server or hostvrf has started or stopped |
os-logging |
LOG_STD_NO_ACTION |
|
SYS-6-LOGOUT |
6-Information |
User [chars] has exited tty session [dec][chars] |
A user has closed a tty session normally using the exit CLI command. |
os |
"This message is for information only. " "No action is required." |
|
SYS-6-MEMDUMP |
6-Information |
[hex]: [hex] [hex] [hex] [hex] |
This is an auxiliary message to several memory-related messages. It provides a raw display of the information in the header of a corrupted data block. |
Include this error message in the DDTS that was written for\n\ the previously printed error message. |
"This message provides additional information only. Copy the error " "message exactly as it appears and report it to your technical support " "representative as part of the previously printed error message." |
|
SYS-6-MEMDUMP |
6-Information |
[hex]: [hex] [hex] [hex] [hex] |
This is an auxiliary message to several memory-related messages. It provides a raw display of the information in the header of a corrupted data block. |
Include this error message in the DDTS that was written for\n\ the previously printed error message. |
"This message provides additional information only. Copy the error " "message exactly as it appears and report it to your technical support " "representative as part of the previously printed error message." |
|
SYS-6-MEMDUMP |
6-Information |
[hex]: [hex] [hex] [hex] [hex] |
This is an auxiliary message to several memory-related messages. It provides a raw display of the information in the header of a corrupted data block. |
Include this error message in the DDTS that was written for\n\ the previously printed error message. |
"This message provides additional information only. Copy the error " "message exactly as it appears and report it to your technical support " "representative as part of the previously printed error message." |
|
SYS-6-MEMDUMP |
6-Information |
[hex]: [hex] [hex] [hex] [hex] |
This is an auxiliary message to several memory-related messages. It provides a raw display of the information in the header of a corrupted data block. |
Include this error message in the DDTS that was written for\n\ the previously printed error message. |
"This message provides additional information only. Copy the error " "message exactly as it appears and report it to your technical support " "representative as part of the previously printed error message." |
|
SYS-6-MEMDUMP |
6-Information |
[hex]: [hex] [hex] [hex] [hex] |
This is an auxiliary message to several memory-related messages. It provides a raw display of the information in the header of a corrupted data block. |
Include this error message in the DDTS that was written for\n\ the previously printed error message. |
"This message provides additional information only. Copy the error " "message exactly as it appears and report it to your technical support " "representative as part of the previously printed error message." |
|
SYS-6-MEMDUMP |
6-Information |
[hex]: [hex] [hex] [hex] [hex] |
This is an auxiliary message to several memory-related messages. It provides a raw display of the information in the header of a corrupted data block. |
Include this error message in the DDTS that was written for\n\ the previously printed error message. |
"This message provides additional information only. Copy the error " "message exactly as it appears and report it to your technical support " "representative as part of the previously printed error message." |
|
SYS-6-MTRACE |
6-Information |
[chars]: addr pc\n ADDRPC ADDRPC ADDRPC ADDRPC \n ADDRPC ADDRPC ADDRPC ADDRPC |
This is an auxiliary message to several memory-related messages. It provides the address of the memory block and the calling program counter for the last eight blocks allocated and for the last eight blocks freed. |
Include this error message in the DDTS that was written for\n\ the previously printed error message. |
"This message provides additional information only. Copy the error " "message exactly as it appears and report it to your technical support " "representative as part of a previously printed error message." |
|
SYS-6-MTRACE |
6-Information |
[chars]: addr pc\n ADDRPC ADDRPC ADDRPC ADDRPC \n ADDRPC ADDRPC ADDRPC ADDRPC |
This is an auxiliary message to several memory-related messages. It provides the address of the memory block and the calling program counter for the last eight blocks allocated and for the last eight blocks freed. |
Include this error message in the DDTS that was written for\n\ the previously printed error message. |
"This message provides additional information only. Copy the error " "message exactly as it appears and report it to your technical support " "representative as part of a previously printed error message." |
|
SYS-6-MTRACE |
6-Information |
[chars]: addr pc\n ADDRPC ADDRPC ADDRPC ADDRPC \n ADDRPC ADDRPC ADDRPC ADDRPC |
This is an auxiliary message to several memory-related messages. It provides the address of the memory block and the calling program counter for the last eight blocks allocated and for the last eight blocks freed. |
Include this error message in the DDTS that was written for\n\ the previously printed error message. |
"This message provides additional information only. Copy the error " "message exactly as it appears and report it to your technical support " "representative as part of a previously printed error message." |
|
SYS-6-MTRACE |
6-Information |
[chars]: addr pc\n ADDRPC ADDRPC ADDRPC ADDRPC \n ADDRPC ADDRPC ADDRPC ADDRPC |
This is an auxiliary message to several memory-related messages. It provides the address of the memory block and the calling program counter for the last eight blocks allocated and for the last eight blocks freed. |
Include this error message in the DDTS that was written for\n\ the previously printed error message. |
"This message provides additional information only. Copy the error " "message exactly as it appears and report it to your technical support " "representative as part of a previously printed error message." |
|
SYS-6-MTRACE |
6-Information |
[chars]: addr pc\n ADDRPC ADDRPC ADDRPC ADDRPC \n ADDRPC ADDRPC ADDRPC ADDRPC |
This is an auxiliary message to several memory-related messages. It provides the address of the memory block and the calling program counter for the last eight blocks allocated and for the last eight blocks freed. |
Include this error message in the DDTS that was written for\n\ the previously printed error message. |
"This message provides additional information only. Copy the error " "message exactly as it appears and report it to your technical support " "representative as part of a previously printed error message." |
|
SYS-6-MTRACE |
6-Information |
[chars]: addr pc\n ADDRPC ADDRPC ADDRPC ADDRPC \n ADDRPC ADDRPC ADDRPC ADDRPC |
This is an auxiliary message to several memory-related messages. It provides the address of the memory block and the calling program counter for the last eight blocks allocated and for the last eight blocks freed. |
Include this error message in the DDTS that was written for\n\ the previously printed error message. |
"This message provides additional information only. Copy the error " "message exactly as it appears and report it to your technical support " "representative as part of a previously printed error message." |
|
SYS-6-NOBRIDGE |
6-Information |
Bridging software not present |
Your system is not configured to be a bridge. |
none |
"Configure the bridging software." |
|
SYS-6-NOBRIDGE |
6-Information |
Bridging software not present |
Your system is not configured to be a bridge. |
none |
"Configure the bridging software." |
|
SYS-6-NOBRIDGE |
6-Information |
Bridging software not present |
Your system is not configured to be a bridge. |
none |
"Configure the bridging software." |
|
SYS-6-NOBRIDGE |
6-Information |
Bridging software not present |
Your system is not configured to be a bridge. |
none |
"Configure the bridging software." |
|
SYS-6-NOBRIDGE |
6-Information |
Bridging software not present |
Your system is not configured to be a bridge. |
none |
"Configure the bridging software." |
|
SYS-6-NOBRIDGE |
6-Information |
Bridging software not present |
Your system is not configured to be a bridge. |
none |
"Configure the bridging software." |
|
SYS-6-PRIVCFG_DECRYPT_SUCCESS |
6-Information |
[chars] |
Private config decryption successful |
none |
"This is an informational message." |
|
SYS-6-PRIVCFG_ENCRYPT_SUCCESS |
6-Information |
[chars] |
Private config encryption successful |
none |
"This is an informational message." |
|
SYS-6-PROCINFO |
6-Information |
Process [chars] just finished executing |
This message is an auxiliary to the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages. It identifies the process or process fragment that was executing when the error occurred. |
- |
"Copy this messages exactly as it appears and report it along with " "the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages to your " "technical support representative." |
|
SYS-6-PROCINFO |
6-Information |
Process [chars] just finished executing |
This message is an auxiliary to the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages. It identifies the process or process fragment that was executing when the error occurred. |
- |
"Copy this messages exactly as it appears and report it along with " "the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages to your " "technical support representative." |
|
SYS-6-PROCINFO |
6-Information |
Process [chars] just finished executing |
This message is an auxiliary to the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages. It identifies the process or process fragment that was executing when the error occurred. |
- |
"Copy this messages exactly as it appears and report it along with " "the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages to your " "technical support representative." |
|
SYS-6-PROCINFO |
6-Information |
Process [chars] just finished executing |
This message is an auxiliary to the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages. It identifies the process or process fragment that was executing when the error occurred. |
- |
"Copy this messages exactly as it appears and report it along with " "the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages to your " "technical support representative." |
|
SYS-6-PROCINFO |
6-Information |
Process [chars] just finished executing |
This message is an auxiliary to the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages. It identifies the process or process fragment that was executing when the error occurred. |
- |
"Copy this messages exactly as it appears and report it along with " "the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages to your " "technical support representative." |
|
SYS-6-PROCINFO |
6-Information |
Process [chars] just finished executing |
This message is an auxiliary to the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages. It identifies the process or process fragment that was executing when the error occurred. |
- |
"Copy this messages exactly as it appears and report it along with " "the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages to your " "technical support representative." |
|
SYS-6-READ_BOOTFILE_FAIL |
6-Information |
[chars] [chars].\n |
A configured boot system command failed. |
- |
"If a system image was eventually loaded no action is recommended. If " "the system image did not load as configured send a log file and " "configuration information to your technical support representative." |
|
SYS-6-READ_BOOTFILE_FAIL |
6-Information |
[chars] [chars].\n |
A configured boot system command failed. |
- |
"If a system image was eventually loaded no action is recommended. If " "the system image did not load as configured send a log file and " "configuration information to your technical support representative." |
|
SYS-6-READ_BOOTFILE_FAIL |
6-Information |
[chars] [chars].\n |
A configured boot system command failed. |
- |
"If a system image was eventually loaded no action is recommended. If " "the system image did not load as configured send a log file and " "configuration information to your technical support representative." |
|
SYS-6-READ_BOOTFILE_FAIL |
6-Information |
[chars] [chars].\n |
A configured boot system command failed. |
- |
"If a system image was eventually loaded no action is recommended. If " "the system image did not load as configured send a log file and " "configuration information to your technical support representative." |
|
SYS-6-READ_BOOTFILE_FAIL |
6-Information |
[chars] [chars].\n |
A configured boot system command failed. |
- |
"If a system image was eventually loaded no action is recommended. If " "the system image did not load as configured send a log file and " "configuration information to your technical support representative." |
|
SYS-6-READ_BOOTFILE_FAIL |
6-Information |
[chars] [chars].\n |
A configured boot system command failed. |
- |
"If a system image was eventually loaded no action is recommended. If " "the system image did not load as configured send a log file and " "configuration information to your technical support representative." |
|
SYS-6-READ_BOOTFILE_SKIP |
6-Information |
boot system [chars] command is skipped\n |
A configured boot system command is skipped. Either the system experienced a crash while loading this image in the last attempt or the filename is not properly specified. Subsequent boot system commands will be tried |
- |
"Replace the failed boot system image with a good one. There could be " "various reasons that this specified image failed for example the image " "might be with a bad checksum." |
|
SYS-6-READ_BOOTFILE_SKIP |
6-Information |
boot system [chars] command is skipped\n |
A configured boot system command is skipped. Either the system experienced a crash while loading this image in the last attempt or the filename is not properly specified. Subsequent boot system commands will be tried |
- |
"Replace the failed boot system image with a good one. There could be " "various reasons that this specified image failed for example the image " "might be with a bad checksum." |
|
SYS-6-READ_BOOTFILE_SKIP |
6-Information |
boot system [chars] command is skipped\n |
A configured boot system command is skipped. Either the system experienced a crash while loading this image in the last attempt or the filename is not properly specified. Subsequent boot system commands will be tried |
- |
"Replace the failed boot system image with a good one. There could be " "various reasons that this specified image failed for example the image " "might be with a bad checksum." |
|
SYS-6-READ_BOOTFILE_SKIP |
6-Information |
boot system [chars] command is skipped\n |
A configured boot system command is skipped. Either the system experienced a crash while loading this image in the last attempt or the filename is not properly specified. Subsequent boot system commands will be tried |
- |
"Replace the failed boot system image with a good one. There could be " "various reasons that this specified image failed for example the image " "might be with a bad checksum." |
|
SYS-6-READ_BOOTFILE_SKIP |
6-Information |
boot system [chars] command is skipped\n |
A configured boot system command is skipped. Either the system experienced a crash while loading this image in the last attempt or the filename is not properly specified. Subsequent boot system commands will be tried |
- |
"Replace the failed boot system image with a good one. There could be " "various reasons that this specified image failed for example the image " "might be with a bad checksum." |
|
SYS-6-READ_BOOTFILE_SKIP |
6-Information |
boot system [chars] command is skipped\n |
A configured boot system command is skipped. Either the system experienced a crash while loading this image in the last attempt or the filename is not properly specified. Subsequent boot system commands will be tried |
- |
"Replace the failed boot system image with a good one. There could be " "various reasons that this specified image failed for example the image " "might be with a bad checksum." |
|
SYS-6-RESERVE_MEMORY_CREATED |
6-Information |
Reserve memory is being created |
A portion of memory is reserved exclusively for console |
- |
"The console access is made available even in low memory " "condition. User can collect the details like tech-support " "for further diagnosis" |
|
SYS-6-RESERVE_MEMORY_CREATED |
6-Information |
Reserve memory is being created |
A portion of memory is reserved exclusively for console |
- |
"The console access is made available even in low memory " "condition. User can collect the details like tech-support " "for further diagnosis" |
|
SYS-6-RESERVE_MEMORY_CREATED |
6-Information |
Reserve memory is being created |
A portion of memory is reserved exclusively for console |
- |
"The console access is made available even in low memory " "condition. User can collect the details like tech-support " "for further diagnosis" |
|
SYS-6-RESERVE_MEMORY_CREATED |
6-Information |
Reserve memory is being created |
A portion of memory is reserved exclusively for console |
- |
"The console access is made available even in low memory " "condition. User can collect the details like tech-support " "for further diagnosis" |
|
SYS-6-RESERVE_MEMORY_CREATED |
6-Information |
Reserve memory is being created |
A portion of memory is reserved exclusively for console |
- |
"The console access is made available even in low memory " "condition. User can collect the details like tech-support " "for further diagnosis" |
|
SYS-6-RESERVE_MEMORY_CREATED |
6-Information |
Reserve memory is being created |
A portion of memory is reserved exclusively for console |
- |
"The console access is made available even in low memory " "condition. User can collect the details like tech-support " "for further diagnosis" |
|
SYS-6-SCRIPTING_TCL_INVALID_OR_MISSING_SIGNATURE |
6-Information |
[chars] cannot run the signed TCL script. |
The TCL script being run has either an unmatched trustpoint name or a missing or a corrupted trustpoint name |
tcl-bleeding |
"Either re-sign the TCL script with a proper trustpoint name or " "use crypto pki authenticate tcl to add the desired trustpoint name." "Then rerun the TCL script." |
|
SYS-6-SCRIPTING_TCL_SECURE_TRUSTPOINT |
6-Information |
[chars] cannot verify signed TCL script. |
The TCL script being run is lacking either scripting tcl secure-mode or trustpoint being configured first |
tcl-bleeding |
"Configure the missing scripting tcl secure-mode or " "scripting tcl trustpoint name <name>. Then rerun the TCL script." |
|
SYS-6-SHOW_LOGGING |
6-Information |
User [chars] has activated the show [chars] command. |
The Common Criteria CC certification requires a log message to indicate when a user activates the show logging persistent command. |
os-logging |
"This message is for information only. No action is required." |
|
SYS-6-STACKLOW |
6-Information |
Stack for [chars] [chars] running low [dec]/[dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-6-STACKLOW |
6-Information |
Stack for [chars] [chars] running low [dec]/[dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-6-STACKLOW |
6-Information |
Stack for [chars] [chars] running low [dec]/[dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-6-STACKLOW |
6-Information |
Stack for [chars] [chars] running low [dec]/[dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-6-STACKLOW |
6-Information |
Stack for [chars] [chars] running low [dec]/[dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-6-STACKLOW |
6-Information |
Stack for [chars] [chars] running low [dec]/[dec] |
An internal software error occurred. |
- |
"If this messages recurs copy it exactly as it appears and report " "it to your technical support representative." |
|
SYS-6-STARTUP_CONFIG_IGNORED |
6-Information |
System startup configuration is ignored based on the configuration register setting. |
The configuration register was set to ignore the system startup configuration. |
- |
"If the system should ignore the startup configuration no action " "is required. If the system should boot with the startup configuration " "saved in the NVRAM change the configuration register value." |
|
SYS-6-STARTUP_CONFIG_IGNORED |
6-Information |
System startup configuration is ignored based on the configuration register setting. |
The configuration register was set to ignore the system startup configuration. |
- |
"If the system should ignore the startup configuration no action " "is required. If the system should boot with the startup configuration " "saved in the NVRAM change the configuration register value." |
|
SYS-6-STARTUP_CONFIG_IGNORED |
6-Information |
System startup configuration is ignored based on the configuration register setting. |
The configuration register was set to ignore the system startup configuration. |
- |
"If the system should ignore the startup configuration no action " "is required. If the system should boot with the startup configuration " "saved in the NVRAM change the configuration register value." |
|
SYS-6-STARTUP_CONFIG_IGNORED |
6-Information |
System startup configuration is ignored based on the configuration register setting. |
The configuration register was set to ignore the system startup configuration. |
- |
"If the system should ignore the startup configuration no action " "is required. If the system should boot with the startup configuration " "saved in the NVRAM change the configuration register value." |
|
SYS-6-STARTUP_CONFIG_IGNORED |
6-Information |
System startup configuration is ignored based on the configuration register setting. |
The configuration register was set to ignore the system startup configuration. |
- |
"If the system should ignore the startup configuration no action " "is required. If the system should boot with the startup configuration " "saved in the NVRAM change the configuration register value." |
|
SYS-6-STARTUP_CONFIG_IGNORED |
6-Information |
System startup configuration is ignored based on the configuration register setting. |
The configuration register was set to ignore the system startup configuration. |
- |
"If the system should ignore the startup configuration no action " "is required. If the system should boot with the startup configuration " "saved in the NVRAM change the configuration register value." |
|
SYS-6-TESTINFO |
6-Information |
Scheduler test [hex] for [chars] just executed |
This message is an auxiliary to the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages. It identifies the process or process fragment that was executing when the error occurred. |
Determine the component from the address of the scheduler test routine\n\ displayed in the error message.\n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. |
"Copy this message exactly as it appears and report it along with the " "SYS-3-OVERRUN and SYS-3-BADMAGIC error messages to your technical " "support representative." |
|
SYS-6-TESTINFO |
6-Information |
Scheduler test [hex] for [chars] just executed |
This message is an auxiliary to the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages. It identifies the process or process fragment that was executing when the error occurred. |
Determine the component from the address of the scheduler test routine\n\ displayed in the error message.\n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. |
"Copy this message exactly as it appears and report it along with the " "SYS-3-OVERRUN and SYS-3-BADMAGIC error messages to your technical " "support representative." |
|
SYS-6-TESTINFO |
6-Information |
Scheduler test [hex] for [chars] just executed |
This message is an auxiliary to the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages. It identifies the process or process fragment that was executing when the error occurred. |
Determine the component from the address of the scheduler test routine\n\ displayed in the error message.\n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. |
"Copy this message exactly as it appears and report it along with the " "SYS-3-OVERRUN and SYS-3-BADMAGIC error messages to your technical " "support representative." |
|
SYS-6-TESTINFO |
6-Information |
Scheduler test [hex] for [chars] just executed |
This message is an auxiliary to the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages. It identifies the process or process fragment that was executing when the error occurred. |
Determine the component from the address of the scheduler test routine\n\ displayed in the error message.\n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. |
"Copy this message exactly as it appears and report it along with the " "SYS-3-OVERRUN and SYS-3-BADMAGIC error messages to your technical " "support representative." |
|
SYS-6-TESTINFO |
6-Information |
Scheduler test [hex] for [chars] just executed |
This message is an auxiliary to the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages. It identifies the process or process fragment that was executing when the error occurred. |
Determine the component from the address of the scheduler test routine\n\ displayed in the error message.\n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. |
"Copy this message exactly as it appears and report it along with the " "SYS-3-OVERRUN and SYS-3-BADMAGIC error messages to your technical " "support representative." |
|
SYS-6-TESTINFO |
6-Information |
Scheduler test [hex] for [chars] just executed |
This message is an auxiliary to the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages. It identifies the process or process fragment that was executing when the error occurred. |
Determine the component from the address of the scheduler test routine\n\ displayed in the error message.\n\ Use Topic to search for a similar DDTS. If you find none write\n\ a DDTS for this problem. |
"Copy this message exactly as it appears and report it along with the " "SYS-3-OVERRUN and SYS-3-BADMAGIC error messages to your technical " "support representative." |
|
SYS-6-TTY_EXPIRE_TIMER |
6-Information |
[chars] expired tty [dec] [inet] user [chars] |
The maximum inactivity time has been reached for the tty session as configured by the exec-timeout CLI configuration command. The session has expired. |
os |
"This message is for information only. No action is" " required." |
|
SYS-6-USERLOG_INFO |
6-Information |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-6-USERLOG_INFO |
6-Information |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-6-USERLOG_INFO |
6-Information |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-6-USERLOG_INFO |
6-Information |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-6-USERLOG_INFO |
6-Information |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-6-USERLOG_INFO |
6-Information |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-6-USING_RESERVE_MEMORY |
6-Information |
Reserve memory is being used |
The reserved memory is being used by the console |
- |
"The system is low in memory. The reserved memory will be " "used only by the console process. Please take a techsupport " "so that the reason for low memory can be found" |
|
SYS-6-USING_RESERVE_MEMORY |
6-Information |
Reserve memory is being used |
The reserved memory is being used by the console |
- |
"The system is low in memory. The reserved memory will be " "used only by the console process. Please take a techsupport " "so that the reason for low memory can be found" |
|
SYS-6-USING_RESERVE_MEMORY |
6-Information |
Reserve memory is being used |
The reserved memory is being used by the console |
- |
"The system is low in memory. The reserved memory will be " "used only by the console process. Please take a techsupport " "so that the reason for low memory can be found" |
|
SYS-6-USING_RESERVE_MEMORY |
6-Information |
Reserve memory is being used |
The reserved memory is being used by the console |
- |
"The system is low in memory. The reserved memory will be " "used only by the console process. Please take a techsupport " "so that the reason for low memory can be found" |
|
SYS-6-USING_RESERVE_MEMORY |
6-Information |
Reserve memory is being used |
The reserved memory is being used by the console |
- |
"The system is low in memory. The reserved memory will be " "used only by the console process. Please take a techsupport " "so that the reason for low memory can be found" |
|
SYS-6-USING_RESERVE_MEMORY |
6-Information |
Reserve memory is being used |
The reserved memory is being used by the console |
- |
"The system is low in memory. The reserved memory will be " "used only by the console process. Please take a techsupport " "so that the reason for low memory can be found" |
|
SYS-7-ESMSHUTDOWN |
7-Debug |
ESM shutdown |
The Embedded Syslog Manager has been shut down |
- |
LOG_STD_NO_ACTION |
|
SYS-7-ESMSHUTDOWN |
7-Debug |
ESM shutdown |
The Embedded Syslog Manager has been shut down |
- |
LOG_STD_NO_ACTION |
|
SYS-7-ESMSHUTDOWN |
7-Debug |
ESM shutdown |
The Embedded Syslog Manager has been shut down |
- |
LOG_STD_NO_ACTION |
|
SYS-7-ESMSHUTDOWN |
7-Debug |
ESM shutdown |
The Embedded Syslog Manager has been shut down |
- |
LOG_STD_NO_ACTION |
|
SYS-7-ESMSHUTDOWN |
7-Debug |
ESM shutdown |
The Embedded Syslog Manager has been shut down |
- |
LOG_STD_NO_ACTION |
|
SYS-7-ESMSHUTDOWN |
7-Debug |
ESM shutdown |
The Embedded Syslog Manager has been shut down |
- |
LOG_STD_NO_ACTION |
|
SYS-7-NV_BLOCK_INIT |
7-Debug |
Initialized the geometry of nvram |
Initialized the nvram block geometry a part of the nvram to host non config data files. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. |
- |
"" |
|
SYS-7-NV_BLOCK_INIT |
7-Debug |
Initialized the geometry of nvram |
Initialized the nvram block geometry a part of the nvram to host non config data files. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. |
- |
"" |
|
SYS-7-NV_BLOCK_INIT |
7-Debug |
Initialized the geometry of nvram |
Initialized the nvram block geometry a part of the nvram to host non config data files. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. |
- |
"" |
|
SYS-7-NV_BLOCK_INIT |
7-Debug |
Initialized the geometry of nvram |
Initialized the nvram block geometry a part of the nvram to host non config data files. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. |
- |
"" |
|
SYS-7-NV_BLOCK_INIT |
7-Debug |
Initialized the geometry of nvram |
Initialized the nvram block geometry a part of the nvram to host non config data files. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. |
- |
"" |
|
SYS-7-NV_BLOCK_INIT |
7-Debug |
Initialized the geometry of nvram |
Initialized the nvram block geometry a part of the nvram to host non config data files. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. |
- |
"" |
|
SYS-7-NVRAM_INIT_WAIT_TIME |
7-Debug |
Waited [dec] seconds for NVRAM to be available |
The amount of time spent waiting during bootup before NVRAM was available. |
- |
"This is a debug message." |
|
SYS-7-USERLOG_DEBUG |
7-Debug |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-7-USERLOG_DEBUG |
7-Debug |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-7-USERLOG_DEBUG |
7-Debug |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-7-USERLOG_DEBUG |
7-Debug |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-7-USERLOG_DEBUG |
7-Debug |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYS-7-USERLOG_DEBUG |
7-Debug |
Message from tty[t-line]user id: [chars]: [chars] |
A user has used the 'send log' command to include a message on the configured logging destinations. Such messages can be used to help tag where user-initiated events occur during debugging. The severity level might have been changed by the user. |
- |
"This message is informational only." |
|
SYSCTLR-3-BAD_CALL |
3-Error |
Invalid parameter/mangled pointer\n routine: [chars] file: [chars] line: [dec] |
An internal software error occurred. |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
SYSCTLR-3-DISCOVER_SOCKET_BIND |
3-Error |
socket bind failed |
An internal software error occurred. |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
SYSCTLR-3-DISCOVER_SOCKET_OPEN |
3-Error |
socket open failed |
An internal software error occurred. |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
SYSCTLR-3-DUPLICATE_SHELF |
3-Error |
SDP packet with duplicate shelf-id [dec] received from [chars]already discovered \shelf located at [chars] |
Two shelves with same shelf-id are configured in the system. |
- |
"Change the shelf-id for one of the shelf." |
|
SYSCTLR-3-HMON_SETUP_FAILED |
3-Error |
Health monitoring setup failed on shelf_id [dec]\n |
Health monitor failed to setup the monitoring command on that particular shelf |
- |
"" |
|
SYSCTLR-3-INVALID_SDP_VERSION |
3-Error |
SDP packet received by system controller containted invalid version number. |
Check that shelf is running compatible version of SDP |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
SYSCTLR-3-SDP_TIMER_ERROR |
3-Error |
No context associated with the expired SDP timer |
An internal software error occurred. |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
SYSCTLR-3-SHELF_MSGFAIL |
3-Error |
Unable to send message [dec] to process with pid [dec]. |
Most likely the performance collector process has terminated. |
- |
"" |
|
SYSCTLR-3-SHELF_PROTO |
3-Error |
Shelf id protocol error |
An internal software error occurred. |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
SYSCTLR-4-HMON_POLL |
4-Warning |
Local time [chars]\n [chars] on shelfid [dec] is not active resetting monitor_type [dec]\n |
Health monitor setup commands polling information.\n\ If you see this message shows up every ten minutes that\n\ means health monitor is not able to set that corresponding \n\ entry on that shelf. |
- |
"" |
|
SYSCTLR-4-SDP_TIMEOUT |
4-Warning |
Hello packet from shelf [dec] not received shelf removed. |
No SDP hello packets were received from the particular shelf this could indicate that particular router shelf is down or is mis-configured. |
- |
"" |
|
SYSCTLR-4-SHELF_CONF_CHANGED |
4-Warning |
Configuration for the shelf [dec] located [inet] changed |
SDP protocol on system controller has detected that a particular shelf configuration has changed. |
- |
"" |
|
SYSCTLR-4-SHELF_RELOAD |
4-Warning |
Shelf [dec] located [inet] reloaded |
SDP protocol on system controller has detected that a particular shelf has reload. |
- |
"" |
|
SYSCTLR-4-SHELF_REMOVE |
4-Warning |
Shelf [dec] located at address [inet] removed. |
SDP protocol on system controller didn't receive hello packets from particular shelf. |
- |
"" |
|
SYSCTLR-4-SNMP_NOT_RESPONDING |
4-Warning |
Shelf [dec] not reachable via SNMP |
Shelf indicated above is not responding to SNMP requests. |
- |
"Check the snmp configuration for the above shelf and also check correct \n\community string is specified in configuration command system-controller \n\community on the system controller." |
|
SYSCTLR-5-AUTH_FAILED |
5-Notice |
MD5 digest does not match SDP packet received from [inet] rejected |
A SDP hello packet was received from shelf which is not trusted. |
- |
"Either specify the correct SDP password and/or destination on the\n\ shelf from which this message was received" |
|
SYSCTLR-6-BAD_IP_ADDR |
6-Information |
Found Shelf [dec] with an invalid IP address [chars] |
System Controller found a Shelf with an invalid ip address |
- |
"Check the IP address set on the Shelf" |
|
SYSCTLR-6-SHELF_ADD |
6-Information |
Shelf [dec] discovered located at address [inet] |
SDP protocol on system controller has detected a particular shelf. |
- |
"" |
|
SYSCTLR-6-SHELF_RESTORED |
6-Information |
Communication with shelf [dec] located at address [inet] |
SDP protocol on system controller has detected a particular shelf. |
- |
"" |
|
SYSLOG_SERVER-3-CREATE_ERR |
3-Error |
Failed to create a Syslog file. |
Failed to create a Syslog file. |
- |
"There is probably no PCMCIA disk on slot0\n\ on the System Controller. Please check to see if it is not a\n\ PCMCIA Flash" |
|
SYSLOG_SERVER-3-ILLEGAL_FS |
3-Error |
Illegal file system [chars]. |
Illegal file system. |
- |
"" |
|
SYSLOG_SERVER-3-MFS_MAX |
3-Error |
Failed to add Syslog file [chars] maximum Syslog files [dec]. |
Exceeded the maximum Syslog files allowed. |
- |
"" |
|
SYSLOG_SERVER-3-OPEN_FILE_ERR |
3-Error |
Failed to open [chars].[dec] syslog file. |
Failed to open a syslog file.One or more of the subfiles may\n\ have been deleted or there is no PCMCIA disk |
- |
"You may not be having a PCMCIA disk in slot0\n\ on the System Controller. Please check to see if it is not a \n\ PCMCIA Flash. If one or more of the subfiles is missing then\n\ they will be automatically restored when the current file reaches\n\ its capacity and gets archived" |
|
SYSLOG_SERVER-3-PARSING_ERR |
3-Error |
Parsing file error. |
The Router is not configured to timestamp all the log messages |
- |
"Please configure your router with appropriate\n\ commands to timestamp the log messages. Eg: service timestamps" |
|
SYSLOG_SERVER-3-READ_ERR |
3-Error |
Failed to read a file. |
Failed to read a file. |
- |
"" |
|
SYSLOG_SERVER-3-UNKNOWN_NAME |
3-Error |
Unknown command or device name or unable to find device address. |
Unknown command or device name or unable to find device address. |
- |
"" |
|
SYSLOG_SERVER-3-WRITE_ERR |
3-Error |
Failed to write a syslog file. |
Failed to write a syslog file. |
- |
"" |
|
SYSLOG_SERVER-4-DUP_FILE |
4-Warning |
Syslog file [[chars]] exists. |
You may have issued a directory name that already exists on the\n\ PCMCIA disk. |
- |
"Please check to see if the directory name \n\ you supplied already exists on the PCMCIA disk and re-enter\n\ a different one" |
|
SYSLOG_SERVER-4-FILE_CORRUPTED |
4-Warning |
syslog records do not appear to be timestamped. |
This may be a result of not turning the service timestamp\n\ command. |
- |
"Please turn the service timestamps log datetime\n\ command on your router. This will cause the system to timestamp\n\ debugging or logging messages.Use atleast datetime." |
|
SYSLOG_SERVER-4-NO_CONFIG_CHANGE |
4-Warning |
No configuration change. |
There is no configuration change to the syslog-server |
- |
"" |
|
SYSLOG_SERVER-4-NO_MEM |
4-Warning |
No memory left. |
No memory left. |
- |
"The System Controller is running very low on\n\ memory." |
|
SYSLOG_SERVER-4-NO_MOBIUS |
4-Warning |
No syslog file. |
No syslog file. |
- |
"" |
|
SYSLOGD-3-DROPPED_MESSAGES |
3-Error |
A total of %lu messages have been dropped by the syslog daemon due to [chars]\n |
Either a large number of messages have been sent to syslogd before it has had the opportunity to process them in which case this most likely indicates a bug in the sending process. Or there was insufficient memory available in order to handle the message |
syslog |
LOG_STD_ACTION |
|
SYSMGR_SRV_QUERY-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
SYSMGT_RPC-3-IPC_ERROR |
3-Error |
SYSMGT RPC - IPC [chars] [chars] failed [chars] |
System Management Remote Procedure Call operation failure. Request for\n\ information from the CIP card will not be processed. |
- |
LOG_STD_ACTION |
|
SYSMGT_RPC-3-NETMGT_EVENT |
3-Error |
SYSMGT RPC - NETMGT Event: [chars] [dec] |
System Management Remote Procedure Call Network management event error\n\ detected. |
- |
LOG_STD_ACTION |
|
SYSMGT_RPC-3-RPC_ERROR |
3-Error |
SYSMGT RPC - RPC [chars] [chars] failed [chars] [dec] |
System Management Remote Procedure Call operation failure. Request for\n\ information from the CIP card will not be processed. |
- |
LOG_STD_SH_TECH_ACTION |
|
SYSTEM_CONTROLLER-3-COR_MEM_ERR |
3-Error |
Correctable DRAM memory error. Count [dec] log %08x |
A correctable error in system DRAM occurred:normal operation continues. |
msfc2 |
"No action needed if additional DRAM errors do not occur." |
|
SYSTEM_CONTROLLER-3-DUMP |
3-Error |
System controller Global Registers Dump |
Information regarding the internal state of system controller |
msfc2 |
LOG_STD_ACTION |
|
SYSTEM_CONTROLLER-3-ERROR |
3-Error |
Error condition detected: [chars] |
Information regarding an error condition detected by the system controller:normal operation continues |
msfc2 |
LOG_STD_RECUR_ACTION |
|
SYSTEM_CONTROLLER-3-FATAL |
3-Error |
An unrecoverable error has been detected. The system is being reset. |
The system controller has detected an unrecoverable error condition. |
msfc2 |
LOG_STD_ACTION |
|
SYSTEM_CONTROLLER-3-INFO1 |
3-Error |
[chars]=0x[hec] |
Information regarding the internal state of system controller |
msfc2 |
LOG_STD_ACTION |
|
SYSTEM_CONTROLLER-3-INFO2 |
3-Error |
[chars]=0x%08x0x%08x |
Information regarding the internal state of system controller |
msfc2 |
LOG_STD_ACTION |
|
SYSTEM_CONTROLLER-3-MISTRAL_RESET |
3-Error |
System Controller is reset:Normal Operation continues |
The system controller is being reset : Message rate limited |
msfc2 |
"show ibc" |
|
SYSTEM_CONTROLLER-3-MORE_COR_ERR |
3-Error |
[chars] [dec] correctable DRAM memory errors in previous hour |
Multiple correctable errors have occurred in system DRAM |
- |
"Reboot system at next convenient time. If error persists after reboot" " call your Cisco technical support representative to arrange repairs." |
|
SYSTEM_CONTROLLER-3-RESET |
3-Error |
Resetting system controller due to [chars] |
The system controller is being reset due to internal errors |
msfc2 |
LOG_STD_ACTION |
|
SYSTEM_CONTROLLER-3-THRESHOLD |
3-Error |
Mistral interrupt count is [dec] Supervisor will reset on hitting threshold [dec]. |
The system controller has detected an unrecoverable error condition. But since this is a standalone supervisior we merely reset the controller instead of reloading the supervisor. Once the count of the mistral error interrupts hits the threshold value the supervisor will be reloaded. The default threshold value is 5 |
msfc2 |
LOG_STD_ACTION |
|
TAC-3-PICKCTX |
3-Error |
No pick-context |
The context to pick the next server has disappeared. |
tacacs |
LOG_STD_ACTION |
|
TAC-3-SECRETDEFINEFAILED |
3-Error |
Key definition ignored. |
The user is attempting to store either a corrupted shared secret or memory allocation failed during secret definition. Any existing shared secret will be preserved. |
aaa |
"Configure a proper secret." |
|
TAC-3-SERVCONF |
3-Error |
Server config failure: [chars] |
The server configuration failed |
aaa |
"Please configure the server properly" |
|
TAC-3-SERVINT |
3-Error |
[chars] |
This is an internal software error. |
aaa |
LOG_STD_ACTION |
|
TAC-3-SERVNO |
3-Error |
Server [chars] is not configured |
The server is not configured |
aaa |
"Please configure a server before un-configuring it" |
|
TAC-3-XTACACL |
3-Error |
[chars]: accesslist 0x[hec] out of range for \[chars]\ |
The TACACS facility created a message that contains an accesslist which is not a valid accesslist out of bounds. |
tacacs |
"If this message recurs call your technical support representative for " "assistance." |
|
TAC-4-NOTIMEOUT |
4-Warning |
Warning: This command has been deprecated in favor of the line-command \timeout login response\ |
This command is deprecated and should no longer be used. Instead the line-command <CmdBold>timeout login response<noCmdBold> now provides this functionality |
aaa |
"Use the line-command <CmdBold>timeout user-response<noCmdBold>" |
|
TAC-4-SERVREF |
4-Warning |
Warning: Server [chars]:[dec] is still referenced by server group. |
The server being removed is still referenced by a server group |
aaa |
"Please dereference the server from the server group " "as soon as possible." |
|
TAC-4-SERVREFNAME |
4-Warning |
Warning: Server [chars] is still referenced by server group. |
The server being removed is still referenced by a server group |
aaa |
"Please dereference the server from the server group " "as soon as possible." |
|
TAC-4-UNEXREP |
4-Warning |
Reply for non-existent request [dec] on queue |
The TACACS facility received a message it was not expecting. This may occur when a TACACS server sends duplicate responses or when it responds to a request that has already timed out. It also may be due to an internal software problem. |
- |
"If this message recurs call your technical support representative for " "assistance." |
|
TAC-6-SENDTMO |
6-Information |
Send type [dec] to [inet] timed out |
A background TACACS notification enabled with the command tacacs notify was not acknowledged by the TACACS server processor within the |
- |
"Check the TACACS server and the network attached to it." |
|
TAC-6-SERVDEP |
6-Information |
tacacs-server host CLI will be deprecated soon. Please move to tacacs server <name> CLI |
Migration from tacacs-server host CLI to tacacs server <name> CLI |
aaa |
"Please try to use new CLI" |
|
TAGATM_BAD_RANGE-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
TAGATM_NOMEM-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
TAR_FS-3-IMAGE_FILE_INVALID |
3-Error |
[chars] file not found in archive |
The Tar File System could not locate the relevant tar element inside the archive |
os |
"Check whether the Archive is complete and not corrupted or of" " the wrong format. If the problem could" " be recreated with <CmdBold>debug ifs file<NoCmdBold> turned" " on it could help in quick identification of the problem." " Collect the output of <CmdBold>archive tar" " /table<NoCmdBold> <CmdArg>archive-name<NoCmdArg> if it is a" " pure tar archive or <CmdBold>show image contents file<NoCmdBold>" " <CmdArg>archive-name<NoCmdArg> if the archive is a system image" |
|
TBRIDGE-4-BAD_ENCAP |
4-Warning |
Unexpected encapsulation received on [chars] [chars] |
The transparent bridging driver received a packet with\n\ unrecognizable encapsulation. The packet had to be discarded. |
- |
"This could indicate a network media error or that a protocol\n\ which is newer than this version of the Cisco IOS software is\n\ being used. If it is believed that the dropped packets are of\n\ a real protocol upgrade to a new version of the software which\n\ handles it." |
|
TBRIDGE-4-BADXMAC |
4-Warning |
XMACACCESS: Invalid extended access list [dec] |
This is a configuration problem. The specified extended access\n\ list either does not exist or contains an error. |
- |
"Correct the configuration problem." |
|
TBRIDGE-4-BTELIMITREACHED |
4-Warning |
MAC-address table size limit %lu entries reached |
The total number of bridge MAC-address table entries across all bridge \n\ groups has reached the configured maximum limit. |
- |
"Check the bridge tables to determine the origin of the bridge MAC-address \n\ table entries. Check the network configuration and ensure that the entries \n\ are as expected. Use the bridge mac-address-table limit <n> configuration \n\ command to either increase the maximum limit or to disable limit-checking \n\ altogether." |
|
TBRIDGE-4-GIANT |
4-Warning |
Giant received on [chars] [dec] exceeds [dec]\n DA [enet] SA [enet] [0x%08x] |
- |
- |
"Use the address and packet information provided to trace the source of\n\ these packets and reduce its MTU to conform to the standard for the\n\ given media." |
|
TBRIDGE-4-INVALIDMEDIA |
4-Warning |
[chars] received on [chars] - invalid media for transparent bridging |
Transparent bridging was configured on an interface that does not\n\ support it. |
- |
"Remove transparent bridging from the configuration on the specified\n\ interface." |
|
TBRIDGE-4-NOVCDROP |
4-Warning |
Destination VC unknown for packet |
A transparently bridged packet destined for an ATM interface cannot be\n\ fully addressed. |
- |
"Clear the bridge table to force re-learning of all addresses." |
|
TBRIDGE-4-NOVCFLOOD |
4-Warning |
No VC's configured for bridging on [chars] |
An ATM interface was configured for transparent bridging without also\n\ specifying the associated virtual circuits. |
- |
"Configure the required virtual circuits on the specified interface." |
|
TBRIDGE-4-SMF_ACTION |
4-Warning |
invalid action found for [enet] on [chars] - %08x |
A software or hardware error occurred. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
TBRIDGE-4-VCPAKDROP |
4-Warning |
Subscriber SA [enet] moved or loop between circuits [dec] and [dec] |
A subscriber bridged packet dropped because potential circuit loop\n\ or roaming host at subscriber end of network. |
- |
"Clear bridge table. If problem persists it is not a roaming host but\n\ a loop between virtual circuits at subscriber end of network. Take\n\ looping virtual circuits out of service and/or shut the software\n\ interface they are on while subscriber is contacted to remove loop\n\ condition at subscriber end of network." |
|
TCAM_MGR-3-BAD_FIRST_DYN_REGION |
3-Error |
[dec] |
- |
- |
"" |
|
TCAM_MGR-3-BAD_LAST_DYN_REGION |
3-Error |
[dec] |
- |
- |
"" |
|
TCAM_MGR-3-INTERNAL_ERROR |
3-Error |
[chars] [chars] [dec] |
- |
- |
"" |
|
TCAM_MGR-3-INVALID_OPERATION |
3-Error |
[chars] [dec] |
- |
- |
"" |
|
TCAM_MGR-3-INVALID_REG_TYPE |
3-Error |
[chars] [dec] |
- |
- |
"" |
|
TCAM_MGR-3-MALLOC_FAIL |
3-Error |
[chars] [chars] |
- |
- |
"" |
|
TCAM_MGR-3-OP_FAIL |
3-Error |
[chars] failed for application [chars] application entry [hec] with [chars] error |
- |
- |
"" |
|
TCAM_MGR-3-UNUSUAL_BUG_WARNING |
3-Error |
[chars] mbu [hec] free_array_index [dec] region_id [dec] |
- |
- |
"" |
|
TCMSP-3-CAPABILITYMISMATCH |
3-Error |
voice port [chars]: call connection id [0x[hec] 0x[hec] 0x[hec] 0x[hec]] |
There was a capabilities mismatch between the two call legs. capabilities are negotiated between call legs for CODEC VAD and FAX rate. |
ios-voice |
"Check that the dial peer configuration is appropriate for the interface in question. Also check that and configuration on the interface is correct." |
|
TCMSP-3-DOCALLHISFAIL |
3-Error |
\ntcmsp_do_call_history: [chars] |
Allocate or insert an active TCMSP call record into call history list failed. |
ios-voice |
"No action is required." |
|
TCMSP-3-DSP_TIMEOUT |
3-Error |
DSP timeout on event 0x[hec]: DSP ID=0x[hec]: [chars] call mode=[dec] |
Timeout on DSP response. |
ios-voice |
"The DSP has been automatically reset. If problem persists contact" "your technical support representative" |
|
TCMSP-3-DSPALARM |
3-Error |
DSP ID 0x[hec]: status=0x[hec] message=0x[hec] text=[chars] |
The DSP reported a fatal error. All calls on the DSP were dropped and a DSP reload was attempted. |
ios-voice |
"Verify that the DSP reloaded properly by attempting to place a call on the affected voice port. Contact your technical support representative include the full text of the error message." |
|
TCMSP-3-FSM_ERROR |
3-Error |
[chars] |
Internal Finite State Machine Error. |
ios-voice |
"Contact your technical support representative include the full text of the error message." |
|
TCMSP-3-MSGSNDFAIL |
3-Error |
channel:[chars] DSP ID:0x[hec] Message ID:0x[hec] |
A message could not be sent to the DSP. The call continued but may have experienced problems. |
ios-voice |
"Verify that the DSP is still functioning properly by attempting to place a call on the affected voice port. Contact your technical support representative include the full text of the error message." |
|
TCMSP-3-NOEVENT |
3-Error |
no free event structure available from [chars] for DSP message |
There were no event structures remaining in the system pools to alert the router of a voice or signaling event. |
ios-voice |
"Check that the voice port for which the event was reported is still operational. If not clear the voice port." |
|
TCMSP-3-TCMSP_BLOCK |
3-Error |
tcmsp_call_block allocate failed |
RBTreeCreate failed. |
ios-voice |
"Add more memory" |
|
TCMSP-3-TCMSP_CALL_DISC_FAILED |
3-Error |
TCMSP call disconnect failed. channel id [chars] ret [dec] |
TCMSP call disconnect could not be successfully passed and it may result hung calls. |
ios-voice |
"Contact your technical support representative. Report the configuration and full text of the error message." |
|
TCMSP-3-TCMSP_HAIRPIN_FAILED |
3-Error |
Call hairpinning failed. cdb 0x[hec] dst_cdb 0x[hec] dst_call_id [dec] |
A DSP-less call could not be hairpinned. |
ios-voice |
"Under heavy traffic this failure may happen because no TDM resources wereavailable. Contact your technical support representative include the full text of the error message." |
|
TCMSP-3-TCMSP_HAIRPIN_NOTPOSSIBLE |
3-Error |
Call can't be hairpinned. cdb 0x[hec] dst_cdb 0x[hec] dst_call_id [dec] |
A DSP-less call could not be hairpinned. |
ios-voice |
"Check the dial-peer configuration." |
|
TCMSP-3-TCMSP_HAIRPINN |
3-Error |
hairpin peer cdb does not exist cdb 0x[hec] dst_call_id [dec] |
A hairpin call setup failed because the other call leg does not exist. |
ios-voice |
"Contact your technical support representative. Report the configuration and the full text of the error message." |
|
TCMSP-4-FSM_BAD_EVENT |
4-Warning |
Invalid FSM Input on channel [chars]: state=[chars] event=[dec] |
Internal state machine illegal input. This message represents an internal software fault and may manifest itself as dropped or hung calls. |
ios-voice |
"Contact your field service representative if indication is coincident " "with dropped or hung calls." |
|
TCP_PROXY-2-PROXY_IPC_INIT_FAILED |
2-Critical |
QFP TCP Proxy IPC initialization failure result: [dec]. |
Cisco internal software error. QFP TCP Proxy initialization detected that the IPC interface initialization failed. QFP TCP proxy will not be functional while this condition exists. |
qfp-tcp keyword:none |
LOG_STD_ACTION |
|
TCP_PROXY-3-PROXY_BAD_MSG |
3-Error |
CPP TCP Proxy received bad length message type [dec] |
Cisco internal software error. CPP TCP Proxy received a corrupted message from control plane. This message will be ignored. |
qfp-tcp keyword:none |
LOG_STD_ACTION |
|
TCP_PROXY-3-PROXY_DEBUG_REG_FAILED |
3-Error |
- |
TCP Conditional Debugging registration failed. |
qfp-tcp keyword:none |
LOG_STD_ACTION |
|
TCP_PROXY-3-PROXY_INV_MSG |
3-Error |
CPP TCP Proxy received invalid message type [dec] |
Cisco internal software error. CPP TCP Proxy received an invalid message type from control plane. This message will be ignored. |
qfp-tcp keyword:none |
LOG_STD_ACTION |
|
TCP_PROXY-3-PROXY_IPC_ALLOC_FAILED |
3-Error |
CPP TCP Proxy [chars] message lost due to message buffer allocation failure. |
Cisco internal software error. CPP TCP Proxy message processing detected a message buffer allocation failure. The message is lost as the result of this condition. |
qfp-tcp keyword:none |
LOG_STD_ACTION |
|
TCP_PROXY-3-PROXY_IPC_CHUNK_FAILED |
3-Error |
CPP TCP Proxy chunk memory failure [dec] |
Cisco internal software error. QFP TCP Proxy chunk memory allocation detected failure. QFP TCP proxy will not be functional while this condition exists. |
qfp-tcp keyword:none |
LOG_STD_ACTION |
|
TCP_PROXY-3-PROXY_IPC_SEND_FAILED |
3-Error |
CPP TCP Proxy [chars] message lost due to message sent failure result: [dec]. |
Cisco internal software error. CPP TCP Proxy message processing detected a message sent failure. The message is lost as the result of this condition. |
qfp-tcp keyword:none |
LOG_STD_ACTION |
|
TCP-2-ACCEPT |
2-Critical |
Callback failed to accept connection from [chars][dec] to [chars][dec] -- |
An internal software error occurred. |
tcp |
"If this message recurs copy it down exactly as it appears and\n" "contact your technical support representative for assistance." |
|
TCP-2-BADQUEUE |
2-Critical |
Multiple entry for packet [hec] |
An internal software error occurred. |
tcp |
"If this message recurs copy it down exactly as it appears and\n" "contact your technical support representative for assistance." |
|
TCP-2-BADREFCNT |
2-Critical |
Tty[t-line]: Bad refcnt for packet 0x[hec] during retransmit [chars][dec] to [chars][dec] state [dec] |
An internal software error occurred. |
tcp |
"If this message recurs copy it down exactly as it appears and\n" "contact your technical support representative for assistance." |
|
TCP-2-BADTCBREFCNT |
2-Critical |
Bad TCB refcount: TCB 0x[hec] refcnt [dec] |
An internal software error occurred |
tcp |
"If this message recurs copy it down exactly as it appears and\n" "contact your technical support representative for assistance." |
|
TCP-2-BUFFER |
2-Critical |
Tty[t-line] buffering bug |
An internal software error occurred. |
tcp |
"If this message recurs contact your technical support " "representative." |
|
TCP-2-HALFCLOSE |
2-Critical |
Tty[t-line] tcp_putbyte write disabled |
TCP received a packet from a user application after the connection\n was already halfclosed. |
tcp |
"Determine which TCP application is still sending after\n" "the connection was halfclosed." |
|
TCP-2-INVALIDTCPENCAPS |
2-Critical |
Invalid TCB encaps pointer: 0x[hec] |
An invalid TCP ENCAPS is used. |
tcp |
"If this message recurs copy it down exactly as it appears and\n" "contact your technical support representative for assistance." |
|
TCP-2-NOTREADY |
2-Critical |
[chars] called but TCP not initialized |
An internal software error occurred. |
tcp |
"If this message recurs copy the message exactly as it appears and\n" "contact your technical support." |
|
TCP-2-PUTBYTE |
2-Critical |
Tty[t-line] tcp_putbyte with blocking disabled |
An internal software error occurred. |
tcp |
"If this message recurs contact your technical support " "representative." |
|
TCP-3-BADMSS |
3-Error |
Incorrect mss [dec] observed |
MSS Maximum Segment Size became incorrect. TCP cannot guarantee\n |
tcp |
"This message occurs please check the interface MTU and increase\n" "it accordingly. If doing this a few times does not help please\n" "contact your technical support representative for assistance." |
|
TCP-3-FORKFAIL |
3-Error |
Failed to start a process to negotiate options. |
Failed to create a process to handle requests from\n client. It could be because of Insufficient memory. |
tcp |
"Free up some memory." |
|
TCP-3-NOTFOUND |
3-Error |
Connection info for [inet]:[dec] => [inet]:[dec] not found. |
The TCP Intercept code was searching its database for information\n for a particular connection but this information was not found. |
tcp |
"If this message recurs copy it down exactly as it appears and\n" "contact your technical support representative for assistance." |
|
TCP-3-TCBHASHSIZE |
3-Error |
Failed to get tcb hash size from RFD Assigning default value [dec]. |
Failed to get tcb hash size from RFD file using RFD APIs. |
os |
"Contact your technical support representative" " for assistance." |
|
TCP-3-TCP_REG_FAILED |
3-Error |
QFP TCP registers failed |
Cisco internal software error. QFP TCP feature initialization detected that registration failed. QFP TCP will not be functional while this condition exists. |
qfp-tcp keyword:tcp |
LOG_STD_ACTION |
|
TCP-4-INVALIDTCB |
4-Warning |
Invalid TCB pointer: 0x[hec] |
An invalid TCB is used. |
tcp |
"If this message recurs copy it down exactly as it appears and\n" "contact your technical support representative for assistance." |
|
TCP-6-AOKEYEXPIRED |
6-Information |
TCP AO Key expired for connection from [chars][dec] to [chars][dec] tableid - [dec] |
TCP Key specified in Authentication Option has expired on the receiver. |
tcp |
"Configure the TCP key with a valid send/accept lifetime." "If this message recurs copy it down exactly as it appears and\n" "contact your technical support representative for assistance." |
|
TCP-6-AOKEYRECVEXPIRED |
6-Information |
TCP AO Keychain [chars] key [dec] accept lifetime expired |
TCP Authentication Option key has expired. |
tcp |
"Configure the TCP key with a valid accept lifetime." "If this message recurs copy it down exactly as it appears and\n" "contact your technical support representative for assistance." |
|
TCP-6-AOKEYSENDEXPIRED |
6-Information |
TCP AO Keychain [chars] key [dec] send lifetime expired |
TCP Authentication Option key has expired. |
tcp |
"Configure the TCP key with a valid send lifetime." "If this message recurs copy it down exactly as it appears and\n" "contact your technical support representative for assistance." |
|
TCP-6-AOMISMATCH |
6-Information |
TCP AO MAC Mismatch for connection from [chars][dec] to [chars][dec] tableid - [dec] |
TCP Authentication Option MAC did not match between endpoints. |
tcp |
"Configure the TCP key on each end of the connection with the" " same key-string and algorithm and corresponding send/recv ids." "If this message recurs copy it down exactly as it appears and\n" "contact your technical support representative for assistance." |
|
TCP-6-AOMISSING |
6-Information |
TCP Authentication Option not found for connection from [chars][dec] to [chars][dec] tableid - [dec] |
TCP Authentication Option missing on connection. |
tcp |
"Check BGP/LDP/SXP configuration on each peer" " to make sure TCP AO is configured." "If this message recurs copy it down exactly as it appears and\n" "Contact your technical support representative for assistance." |
|
TCP-6-AONOCURRKEY |
6-Information |
No TCP AO Current key configured |
No TCP Authentication Option Current Key configured on the TCB. |
tcp |
"Configure the TCP key chain with valid key and associate with the application." "If this message recurs copy it down exactly as it appears and\n" "contact your technical support representative for assistance." |
|
TCP-6-AONONEXTKEY |
6-Information |
No TCP AO Next key configured |
No TCP Authentication Option Next Key configured on the TCB. |
tcp |
"Configure the TCP key chain with valid key and associate with the application." "If this message recurs copy it down exactly as it appears and\n" "contact your technical support representative for assistance." |
|
TCP-6-AONOSPACE |
6-Information |
Insufficient space for AO option |
Insufficient space for Auth option AO. This should not happen as\n |
tcp |
"Try unconfiguring TCP options if any and check if this error\n" "message goes away. Also copy it down exactly as it appears and\n" "contact your technical support representative for assistance." |
|
TCP-6-AOROLLOVER |
6-Information |
TCP AO Keychain [chars] rollover from key [dec] to key [dec] |
TCP AO Key chain is rolling over to a new key. |
tcp |
"No action required." |
|
TCP-6-BADAUTH |
6-Information |
[chars] MD5 digest from [chars][dec] to [chars][dec][chars] tableid - [dec] |
The system received a TCP packet with an invalid MD5 authentication\n digest on a connection endpoint. The message ends with the string\n \ |
- |
- |
|
TCP-6-INTERCEPT |
6-Information |
[chars] count [dec]/[dec] 1 min [dec] |
The TCP Intercept code has changed state. |
tcp |
"This message is for informational purposes but it may indicate\n" "a security problem." |
|
TCP-6-INTERCEPTHASH |
6-Information |
Unable to allocate memory for TCP Intercept hash table |
An internal software error occured |
tcp |
"Contact your technical support representative for assistance." |
|
TCP-6-MD5NOSPACE |
6-Information |
Insufficient space for MD5 option |
Insufficient space for MD5 option. This should not happen as\n MD5 option when requested needs to be honored and also given\n preference over other TCP options. |
tcp |
"Try unconfiguring TCP options if any and check if this error\n" "message goes away. Also copy it down exactly as it appears and\n" "contact your technical support representative for assistance." |
|
TCP-6-NOBUFF |
6-Information |
TTY[t-line] no buffer available |
An internal software error occurred. |
tcp |
"Copy the error message exactly as it appears and report it to your\n" "technical support representative." |
|
TCP-6-TOOBIG |
6-Information |
Tty[t-line] too many bytes of options [dec] |
An internal software error occurred. |
tcp |
"Copy the error message exactly as it appears and report it to your\n" "technical support representative." |
|
TDM_CLOCK_SYNCHRONIZATION-4-TDMCLK_CHANGE |
4-Warning |
\nTDM frame clock source transitioned from\n\ Priority [dec] [chars] [chars] to Priority [dec] [chars] [chars]\n |
This warning message indicates a change in the clock source. |
- |
"No action required." |
|
TDM_CLOCK_SYNCHRONIZATION-4-TDMCLK_LOST_LOCK |
4-Warning |
\nTDM frame clock [chars] lost lock - clock source failed.\n |
The clock source has failed. |
- |
"If alternate source is available it will be used." |
|
TDM_CLOCK_SYNCHRONIZATION-4-TDMCLK_STATE_CHG |
4-Warning |
\nTDM frame clock state change state: [chars] \n |
This debug message indicates a clock state change |
- |
"No action required." |
|
TDM_CLOCK_SYNCHRONIZATION-4-TDMCLK_STATE_ERR |
4-Warning |
\nTDM frame clock state error state: [chars] event: [chars]\n |
This warning message indicates a invalid clock event |
- |
"No action required." |
|
TDM-1-TDM_INITFAIL |
1-Alert |
Slot [dec] TDM init failure:\nstream [dec] channel [dec] channel register 0x[hec] control register 0x[hec]. |
A TDM port failed to be initialized. \n\ The error message specifies which port. This is possibly due to\n\ a hardware failure. |
- |
LOG_STD_ACTION |
|
TDM-1-TDM_MB_INITFAIL |
1-Alert |
Motherboard TDM init failure:\nstream [dec] channel [dec] channel register 0x[hec] control register 0x[hec]. |
A TDM port on the system motherboard failed to be initialized.\n\ The error message specifies which port. This is possibly due to\n\ a hardware failure. |
- |
LOG_STD_ACTION |
|
TDM-3-TDM_BADUNIT |
3-Error |
Slot [dec] bad board ID 0x[hec] detected. |
The specified board returned an ID that was not recognized by\n\ the operating system. This could be due to a hardware failure\n\ reporting an incorrect ID or because this software predates the\n\ hardware. |
- |
LOG_STD_ACTION |
|
TDM-4-TDM_BAD_CONNECT |
4-Warning |
Bad connection requested: slot [dec] stream [dec] channel [dec] to slot [dec] stream [dec] channel [dec]. |
The TDM cross-connect that was requested was not possible.\n\ This is probably because one of the devices either does not exist\n\ or is not properly configured for TDM. |
- |
"Check the command for errors and the ports for correct configuration\n\ before trying again. Note that the \"type\" option of the \"tdm-group\"\n\ command only applies if the \"mode cas\" command is enabled.\n\ If configuring cross-connect pass-through from UIO serial\n\ port 0 or 1 to a controller the \"encapsulation clear-channel\"\n\ command must be configured on the serial port. " |
|
TEMPLATE-3-TEMPLATE_FAIL |
3-Error |
[chars] template [chars] binding to [chars] failed due to [chars] CLI failure. |
Template binding failed due to failure status returned by binding. |
- |
- |
|
TEMPLATE-4-TEMPLATE_NOEXIST |
4-Warning |
Applying non-existent template [chars] will result in its creation programatically. This functionality will soon be deprecated. Please make sure template is created on device before it is applied by session. |
Applying an undefined template to an interface results in the creation and application of a new empty template of given name |
- |
- |
|
TEMUX84-3-BSWAITERR |
3-Error |
temux84 Byte-Sync indirect access failed [chars] |
hardware busy bit not cleared |
osm-ct3 for CT3osm-choc-ds0 for CHOC-12 |
LOG_STD_ACTION |
|
TEMUX84-3-RTTBWAITERR |
3-Error |
temux84 RTTB indirect access failed [chars] |
hardware busy bit not cleared |
osm-ct3 for CT3osm-choc-ds0 for CHOC-12 |
LOG_STD_ACTION |
|
TEMUX84-3-SBIWAITERR |
3-Error |
temux84 SBI indirect access failed [chars] |
hardware busy bit not cleared |
osm-ct3 for CT3osm-choc-ds0 for CHOC-12 |
LOG_STD_ACTION |
|
TEMUX84-3-T1E1WAITERR |
3-Error |
temux84 T1E1 indirect access failed [chars] |
hardware busy bit not cleared |
osm-ct3 for CT3osm-choc-ds0 for CHOC-12 |
LOG_STD_ACTION |
|
TEMUX84-3-T3E3PMONERR |
3-Error |
temux84 T3E3 PMON update failed [chars] |
JIB3-US FA interrupt |
ubr10k-sw |
"Copy the error message exactly as it appears and report it to your " "technical support" |
|
TENSRFSM-3-INVEVENT |
3-Error |
Invalid event_id 0x%X |
state machine invalid event |
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-INVSTATE |
3-Error |
Invalid current state 0x%X |
state machine invalid state |
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-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-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-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 |
|
TENSRFSM-3-NOPROCID |
3-Error |
Unable to launch TE NSR FSM Process. |
state machine transition process launch failure |
mpls-te |
LOG_STD_ACTION |
|
TENSRFSM-3-NULLMACH |
3-Error |
Invalid machine pointer 0x%X |
state machine invalid pointer |
mpls-te |
LOG_STD_ACTION |
|
TENSRFSM-3-NULLMACH |
3-Error |
Invalid machine pointer 0x%X |
state machine invalid pointer |
mpls-te |
LOG_STD_ACTION |
|
TFTP_ALG-3-ALG_STATE_CREATE_FAIL |
3-Error |
- |
Get/create ALG state failed. TFTP ALG will not be able to process packets. |
cpp-ucode |
LOG_STD_ACTION |
|
TFTP-7-GLEAN_DISABLED |
7-Debug |
ARP gleaning from TFTP has been disabled. |
The ARP gleaning from TFTP has been disabled. |
- |
"If you want ARP gleaning from TFTP do ip arp gleaning tftp." |
|
THREAD-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
THREADEXIT-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
THREAT_DEFENSE_PROXY-3-PROXY_IPC_INIT_FAILED |
3-Error |
[dec] |
IPC handler initialization failed. |
cpp-ucode |
LOG_STD_ACTION |
|
THREAT_DEFENSE_PROXY-3-PROXY_MEM_EXTEND_FAILED |
3-Error |
- |
Extending memory failed. |
cpp-ucode |
LOG_STD_ACTION |
|
THREAT_DEFENSE_PROXY-4-PROXY_IPC_INVALID_MSG |
4-Warning |
[dec] |
Invalid IPC message |
cpp-ucode |
LOG_STD_ACTION |
|
THREAT_DEFENSE_PROXY-4-PROXY_IPC_INVALID_MSG_LEN |
4-Warning |
[dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Invalid IPC message length. |
cpp-ucode |
LOG_STD_ACTION |
|
THREAT_DEFENSE-3-DESTROY_CHUNK_FAILED |
3-Error |
- |
Destroy chunk failed. |
cpp-ucode |
LOG_STD_ACTION |
|
THREAT_DEFENSE-3-VTCP_INIT_FAILED |
3-Error |
- |
Initialization of VTCP failed. |
cpp-ucode |
LOG_STD_ACTION |
|
THREAT_DEFENSE-4-TD_ERM_AVERAGE_THREAT |
4-Warning |
Event Rate Monitoring: Average threat identified. Zone [[chars]] event type [[chars]] average [[dec]] configured threshold [[dec]] |
Event Rate Monitoring: Average threat identified |
cpp-ucode |
LOG_STD_ACTION |
|
THREAT_DEFENSE-4-TD_ERM_BURST_THREAT |
4-Warning |
Event Rate Monitoring: Burst threat identified. Zone [[chars]] event type [[chars]] configured threshold [[dec]] |
Event Rate Monitoring: Burst threat identified |
cpp-ucode |
LOG_STD_ACTION |
|
TID_HA-3-ISSU_ERR |
3-Error |
[chars]: [chars] [chars] |
There was an error during an ISSU versioning operation |
mpls-vpn |
LOG_STD_ACTION |
|
TID_HA-3-ISSUERR |
3-Error |
[chars] [chars] |
There was an error during an ISSU versioning operation |
mpls-vpn |
LOG_STD_ACTION |
|
TID_HA-3-ISSUERRCF |
3-Error |
[chars] checkpoint code [dec] |
There was an error during an ISSU versioning operation due to an error in the checkpoint facility |
mpls-vpn |
LOG_STD_ACTION |
|
TID_HA-3-ISSUERRSESS |
3-Error |
Invalid session type [dec] |
Invalid session type |
mpls-vpn |
LOG_STD_ACTION |
|
TID_HA-3-RXFAIL_TOPO |
3-Error |
[chars] type [dec] version [dec] flags [hec] action [dec] topoid 0x[hec] vrfid 0x[hec] afi [dec] name '[chars]' |
Error while receiving a topo add message |
mpls-vpn |
LOG_STD_ACTION |
|
TID_HA-3-RXFAIL_TYPE |
3-Error |
[chars] @[hec] type [dec] len [dec] |
Unrecognized message type |
mpls-vpn |
LOG_STD_ACTION |
|
TID_HA-3-RXFAIL1 |
3-Error |
[chars] |
Error while receiving a tableid synchronization message |
mpls-vpn |
LOG_STD_ACTION |
|
TID_HA-3-RXFAIL2 |
3-Error |
[chars] type [dec] version [dec] flags [hec] |
Error while receiving a tableid synchronization message |
mpls-vpn |
LOG_STD_ACTION |
|
TID_HA-3-RXFAIL3 |
3-Error |
[chars] type [dec] version [dec] flags [hec] application [dec] action [dec] tableid [dec] name '[chars]' |
Error while receiving a tableid synchronization message |
mpls-vpn |
LOG_STD_ACTION |
|
TID_HA-3-SYNCFAIL |
3-Error |
[chars] |
Internal tableid information may have not been synced to the standby unit correctly |
mpls-vpn |
"Reload the standby unit. If the error condition perists copy the " "error message exactly as it appears and contact your technical " "support representative" |
|
TID_HA-3-SYNCFAILCF |
3-Error |
[chars] checkpoint code [dec] |
Internal tableid information may have not been synced to the standby unit correctly due to an error in the checkpoint facility |
mpls-vpn |
"Reload the standby unit. If the error condition perists copy the " "error message exactly as it appears and contact your technical support " "representative" |
|
TID_HA-3-TXFAIL |
3-Error |
[chars] name '[chars]' tableid [dec] action [dec] |
Failed to send internal tableid information |
mpls-vpn |
LOG_STD_ACTION |
|
TID_HA-3-TXFAILCF |
3-Error |
[chars] name '[chars]' tableid [dec] action [dec] checkpoint code [dec] |
Failed to send internal tableid information due to an error in the checkpoint facility |
mpls-vpn |
LOG_STD_ACTION |
|
TID_HA-7-ISSU_INFO |
7-Debug |
[chars]: [chars] [chars] |
ISSU versioning operation |
mpls-vpn |
LOG_STD_ACTION |
|
TIME-2-HB_START_FAILED |
2-Critical |
timer services failed to start |
The timer services could not be started because GPM allocation failed |
cpp-ucode |
LOG_STD_ACTION |
|
TIME-2-TIMESTAMP_BAD_CLOCK |
2-Critical |
%llu |
Unsupported PPE core clock frequency. |
cpp-ucode |
LOG_STD_ACTION |
|
TIME-3-HB_SEQ_FAIL |
3-Error |
expected seq_num 0x[hec] rcvd seq_num 0x[hec] |
The timer services had exceeded the maximum number of timer heartbeat sequence number errors. |
cpp-ucode |
LOG_STD_ACTION |
|
TIMER-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
TLSCLIENT-3-START_FAIL |
3-Error |
Failed to send start BINOS TLS client message to host-if. |
This message indicates that we failed to send start BINOS TLS client message to host-if. |
- |
"Retry no shut on the TLS config block." |
|
TLSCLIENT-3-STOP_FAIL |
3-Error |
Failed to send shut BINOS TLS client message to host-if. |
This message indicates that we failed to send shut BINOS TLS client message to host-if. |
- |
"Retry shut on the TLS config block." |
|
TLSCLIENT-5-REKEY_CONN_FAILURE |
5-Notice |
Rekey failed for Session [%p] to TLSGW [[chars]] |
This message indicates that the Rekey for the tunnel to the tlsgw failed. |
- |
"Either the server is down or the connectivity to the server" " is broken" |
|
TLSCLIENT-5-TLSCLIENT_BINOS |
5-Notice |
TLS Client is BINOS based |
This message indicates that TLS client is BINOS based |
- |
LOG_STD_NO_ACTION |
|
TLSCLIENT-5-TLSCLIENT_IOS |
5-Notice |
TLS Client is IOS based |
This message indicates that TLS client is IOS based |
- |
LOG_STD_NO_ACTION |
|
TLSCLIENT-5-UPDOWN |
5-Notice |
Session [%p] to TLSGW: [[chars]] is [chars] |
TLS Tunnel service state changed. |
- |
LOG_STD_NO_ACTION |
|
TLV-3-GET |
3-Error |
Reading data type [dec] |
An expected field in the TLV buffer was either missing or malformed |
- |
LOG_STD_RECUR_ACTION |
|
TLV-3-UPDATE |
3-Error |
Unable to write type [dec] |
An attempt to update a TLV entry failed. |
- |
LOG_STD_RECUR_ACTION |
|
TMQ-3-NOTFOUND |
3-Error |
TMQ Attempt to delete entry not in queue |
An attempt was made to delete an entry not in the queue. |
- |
"Advisory message only. No action required." |
|
TN-2-BADCONN |
2-Critical |
Bad conn pointer [hex] closing all connections on terminal line [dec] |
An internal software error occurred. |
- |
"If any message recurs call your technical support representative\n" "for assistance." |
|
TN-2-BADLOGIN |
2-Critical |
Bad login string pointer [hex] |
An internal software error occurred. |
- |
"If any message recurs call your technical support representative\n" "for assistance." |
|
TN3270-2-INP_OVF1 |
2-Critical |
Input Buffer overflow |
- |
- |
"Copy this error message exactly as it appears and contact your\n\ technical support representative for assistance." |
|
TN-3-BADSTATE |
3-Error |
Illegal state [dec] |
An internal software error occurred. |
- |
"If any message recurs call your technical support representative " "for assistance." |
|
TN-3-READLINE |
3-Error |
Unknown return code [dec] from telnet_readline |
An internal software error occurred. |
- |
"If any message recurs call your technical support representative " "for assistance." |
|
TOPN_COUNTERS-4-MEM_UNAVAIL |
4-Warning |
Memory was not available for handling the TopN request |
The system is unable to handle the TopN request because of lack of memory. |
- |
"Reduce other system activity to ease memory demands. If conditions warrant upgrade to a larger memory configuration." |
|
TOPN_COUNTERS-5-AVAILABLE |
5-Notice |
TopN report [dec] is available |
The specified report is ready and can be viewed by the users. |
- |
LOG_STD_NO_ACTION |
|
TOPN_COUNTERS-5-DELETED |
5-Notice |
TopN report [dec] deleted by [chars] |
The specified report has been deleted by the specified user. |
- |
LOG_STD_NO_ACTION |
|
TOPN_COUNTERS-5-KILLED |
5-Notice |
TopN report [dec] task killed by [chars] [chars] |
The system was in the process of generating the specified report but the specified user terminated the report before its completion. |
- |
LOG_STD_NO_ACTION |
|
TOPN_COUNTERS-5-NOPORTS |
5-Notice |
No interfaces in the system match the interface type for the generation of the topN report [dec] |
There were no interfaces in the system which matched the interface type selected in the specified report. |
- |
LOG_STD_NO_ACTION |
|
TOPN_COUNTERS-5-STARTED |
5-Notice |
TopN collection for report [dec] started by [chars] |
The TopN report that was requested by the specified user starts with the specified report number. |
- |
LOG_STD_NO_ACTION |
|
TPLUS-3-FORKFAIL |
3-Error |
Failed to fork process for [chars]. |
Quite likely we ran out of memory. Other explanations are possible. |
tplus |
"If this message recurs call your technical support representative for assistance." |
|
TPLUS -3-UNKNOWNTYPE |
3-Error |
TPLUS: 0x%X Unknown Request type [dec]. |
Unknown request type in client request |
tplus |
LOG_STD_ACTION |
|
TR-2-NOMEMORY |
2-Critical |
Unit [dec] no memory for [chars] |
The requested operation could not be accomplished because of a low\n\ memory condition. |
- |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
TR-2-PANIC |
2-Critical |
Unit [dec] panic %-08x %-08x %-08x |
The Token Ring monitor firmware detected a fatal error that indicates\n\ an impending interface failure. |
- |
LOG_STD_ACTION_CRIT |
|
TR-2-PANICINF |
2-Critical |
Unit [dec] PI %-08x %-08x %-08x %-08x %-08x %-08x |
This message is similar to the %TR-3-PANIC error message but\n\ indicates a nonfatal error. This message appears in very unusual\n\ situations that should not arise in normal operation. |
- |
LOG_STD_SH_TECH_ACTION |
|
TR-2-PANICTYPE |
2-Critical |
Unit [dec] [chars] error |
This message is similar to the %TR-3-PANIC error message but\n\ indicates a nonfatal error. This message appears in very unusual\n\ situations that should not arise in normal operation. |
- |
LOG_STD_SH_TECH_ACTION |
|
TR-3-ADPCHK |
3-Error |
Interface [chars] adapter check error non-fatal%04x %04x %04x %04x |
The Token Ring monitor firmware detected a non-fatal error on the\n\ interface card. |
- |
"Issue a clear interface command. If this message recurs call your\n\ technical support representative for assistance." |
|
TR-3-ADPCHKFATAL |
3-Error |
Interface [chars] adapter check error fatal %04x %04x %04x %04x |
The Token Ring monitor firmware detected a fatal error on the\n\ interface card. |
- |
"Issue a clear interface command. If this message recurs call your\n\ technical support representative for assistance. You may need to \n\ replace the interface card " |
|
TR-3-BADBRDGPARMS |
3-Error |
Unit [dec] bad bridge parameters: bridge_num=[dec] max_rd=[dec]\nthisring=[dec] targetring=[dec] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
TR-3-BADBUFFSIZE |
3-Error |
Unit [dec] bad buffersize = [dec] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
TR-3-BADFIRM |
3-Error |
Unit [dec] Tokenring firmware download failed\n got [hex] expected [hex] at address 0x%04x.%04x |
An internal software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
TR-3-BADFIRMTYPE |
3-Error |
Unit [dec] bad firmware type code during [chars]. type=[hex] fw=[hex] |
An internal software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
TR-3-BADFUNC |
3-Error |
Unit [dec] bad functional address=0x%08x ring mode=0x%08x |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
TR-3-BADMUL |
3-Error |
[chars]: Can't set address to a multicast [enet] |
An attempt was made to set the Token Ring interface MAC address to a\n\ reserved multicast address. |
- |
"Check your configuration. Make sure that your XNS and/or Novell Token\n\ Ring addresses have not inadvertently been set to reserved multicast\n\ addresses." |
|
TR-3-BADRNGNUM |
3-Error |
Unit [dec] ring number [dec] doesn't match established number [dec]. |
The number you have configured for the local ring does not match the\n\ value currently in use on the ring. |
- |
"Check the configuration to make sure you used the correct ring number.\n\ If it is correct confirm the configuration of all other bridges on the\n\ ring to make sure they are using the same ring number." |
|
TR-3-BADSTART |
3-Error |
Unit [dec] Start completion and wrong idb state - state= [dec] |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
TR-3-BADUNIT |
3-Error |
Bad unit number [dec] |
This error message pertains only to the IGS. When displayed it\n\ indicates that the system cannot find the chipset registers where it\n\ expects them to be. This is most likely a hardware error. |
- |
"If this message recurs call your technical support representative for\n\ assistance. It will be necessary to determine the hardware unit\n\ configuration." |
|
TR-3-DIAGFAIL |
3-Error |
Interface [chars] failed init diags 0x%04x [chars] |
The microcode attempted to run its diagnostics on the chip and\n\ failed. |
- |
"Issue a clear interface command. " LOG_STD_RECUR_ACTION |
|
TR-3-INITFAIL |
3-Error |
Unit [dec] init failed. result code=[hex] error code=[hex] |
The Token Ring hardware failed to initialize properly. |
- |
LOG_STD_SH_TECH_ACTION |
|
TR-3-INTFAIL |
3-Error |
Unit [dec] interface failure: [hex] [hex] [hex] idb state [dec] |
The Token Ring Monitor firmware detected a fatal error due either to\n\ an internal software problem or to a hardware failure. |
- |
LOG_STD_SH_TECH_ACTION |
|
TR-3-MODEFAIL |
3-Error |
Unit [dec] change mode failed. result code=[hex] error code=[hex] |
An internal hardware or software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
TR-3-NOFIRM |
3-Error |
Unit [dec] no TMS380 firmware present. eagle=[hex] magic=[hex] |
An internal hardware or software error occurred. |
- |
LOG_STD_SH_TECH_ACTION |
|
TR-3-OPENFAIL |
3-Error |
Unit [dec] open failed: [chars] [chars] |
The Token Ring interface was unable to insert itself into the ring.\n\ This is an indication of a busy or broken ring. The first character\n\ string in this error message indicates the stage of initialization at\n\ which the error occurred and the second describes the error. |
- |
"Try to open the interface again. This generally can be accomplished by\n\ issuing the clear interface tokenring command. If the error message\n\ recurs call your Cisco technical support representative for\n\ assistance." |
|
TR-3-OPENFAIL2 |
3-Error |
Unit [dec] open failed: check the lobe cable DB-9 connection. |
The Token Ring interface was unable to insert itself into the ring\n\ and the error code returned indicates a wiring problem. |
- |
"Check the cable connecting the router to the Token Ring MAU and try\n\ to open the interface again. This generally can be accomplished by\n\ issuing the clear interface tokenring command. " LOG_STD_RECUR_ACTION |
|
TR-3-RESETFAIL |
3-Error |
Unit [dec] reset failed error code %-08x. |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
TR-3-SETBRIDGEFAIL |
3-Error |
Unit [dec] set bridge failed code [hex]. |
- |
- |
LOG_STD_SH_TECH_ACTION |
|
TR-3-SETFUNFAIL |
3-Error |
Unit [dec] set functional address failed code [hex]. |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
TR-3-SETGRPFAIL |
3-Error |
Unit [dec] set group address failed code [hex]. |
An internal software error occurred. |
- |
LOG_STD_RECUR_ACTION |
|
TR-3-WIREFAULT |
3-Error |
Unit [dec] wire fault: check the lobe cable MAU connection. |
The Token Ring hardware is reporting a wire fault condition. |
- |
"Check the cable connecting the router to the Token Ring media\n\ attachment unit MAU." |
|
TR-6-STATE |
6-Information |
[chars]: Ring Status: [chars] |
This message is displayed when the Token Ring's status changed as\n\ determined by the chipset. This information also is used to\n\ automatically determine whether the interface is still usable to\n\ propagate network traffic. |
- |
LOG_STD_NO_ACTION |
|
TR-6-STATRING |
6-Information |
TR[dec]: Ring Status: [chars] [chars] |
This message is displayed when the Token Ring's status changed as\n\ determined by the chipset. This information also is used to\n\ automatically determine whether the interface is still usable to\n\ propagate network traffic. The meaning of each status code is shown in\n\ the \Token Ring Status Codes\ Table.\n\\n\ Code Explanation Fatal\n\ 0x8000 Signal loss Yes\n\ 0x4000 Hard error Yes\n\ 0x2000 Soft error No\n\ 0x1000 Transmit beacon Yes\n\ 0x0800 Lobe wire fault Yes\n\ 0x0400 Auto removal error Yes\n\ 0x0100 Receive request removed Yes\n\ 0x0080 Counter overflow No\n\ 0x0040 Single station No\n\ 0x0020 Ring recovery No\n\ |
- |
"Check the Token Ring for the indicated condition." |
|
TRACEBACK_ERR_REC-7-MAX_UNIQUE_TRACEBACKS |
7-Debug |
The error: [dec] in function [chars] in the file [chars]:[dec] in process: [chars] was not recorded by the traceback error recording library under user: [chars]. |
The Library can only store so many error tracebacks and this number had been reached so all future attempts to store error tracebacks will print syslogs. |
os |
"Please clear the tracebacks for the user above. Is it " "recommended that the detailed show command is collected before " "clearing the data." |
|
TRACEKEY_TEST-3-TRACEKEY |
3-Error |
This is a simulated message for errmsg: test_errno=[dec] [chars]: |
- |
- |
- |
|
TRACEKEY_TEST-3-TRACEKEY |
3-Error |
This is a simulated message for errmsg: test_errno=[dec] [chars]: |
- |
- |
- |
|
TRACK-3-ERROR |
3-Error |
Internal error [chars] |
An internal software error occurred. |
fhrp: track |
LOG_STD_ACTION |
|
TRACK-4-WARN |
4-Warning |
Internal warning [chars] |
An internal software warning occurred. |
fhrp: track |
LOG_STD_ACTION |
|
TRACK-6-INFO |
6-Information |
Internal info [chars] |
An internal software information message occurred. |
fhrp: track |
LOG_STD_ACTION |
|
TRACK-6-STATE |
6-Information |
[chars] |
The Tracked object has changed state. |
fhrp: track |
LOG_STD_NO_ACTION |
|
TRANGE-2-NOMEMORY |
2-Critical |
Alloc fail for time-range config buffer. Disabling distributed mode on lc |
Unable to malloc a buffer to send time-range configuration down to linecards. |
- |
"Enter a show chunks command and report the output along with this error message to your technical support representative." |
|
TRANGE-2-WRONGREQUEST |
2-Critical |
Invalid request to allocate chunk of size [dec] |
We only allow time-range chunks of max size TRANGE_LARGE_CHUNK_SZ |
- |
" " |
|
TRANGE-2-WRONGSIZE |
2-Critical |
Incorrect length trange ipc xdr of len=[dec] received |
The RP sent a time-range config message of the wrong size |
- |
"Report this error message to your tech support representative." |
|
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-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-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-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-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-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-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." |
|
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." |
|
TRANSCEIVER-3-DRLX_100M_UP |
3-Error |
[chars] Dual rate transceiver may have come up wrongly with 100M speed |
Dual rate transceiver which supports both 1G/100M may have wrongly detected 100M as the operational speed |
- |
"Please try \"shut\" and \"no shut\" on the interface once" |
|
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-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-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-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-INTERNAL_ERROR |
3-Error |
[chars] |
This message indicates that the number of dynamically learned ARP entries complete or incomplete has exceeded a preconfigured threshold indicating a possible misconfiguration or DOS attack. |
- |
"First inspect the ARP entries on the affected interface. If they " "are valid entries either increase the configured log threshold or " "reconfigure the network to reduce ARP peers. " "If they are invalid entries there is a possible DOS attack " "on the system." |
|
TRANSCEIVER-3-NOT_ALLOWED_ONLINE |
3-Error |
Detected for transceiver module in [chars] module disabled |
The transceiver module for the interface specified in the error message is a restricted transceiver type and is not allowed online in the current configuration for that module. As a result of the error the module is disabled. |
spa-infra |
"Replace the module with a supported transceiver or modify the " "configuration to allow the current transceiver. If the problem " "persists LOG_STD_ACTION." |
|
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_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_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_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_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-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-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-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-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-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_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-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-RPC_FAILED |
3-Error |
Application error rc = [dec]: |
The system failed to retrieve the information required to execute\n\ the comand |
- |
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_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_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_PROCESSING_ERROR |
3-Error |
Transceiver RPC error: [chars] |
Non Fatal error occured in processing an RPC messsage. |
spa-infra |
show version |
|
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_PROCESSING_ERROR |
3-Error |
Transceiver RPC error: [chars] |
Non Fatal error occured in processing an RPC messsage. |
spa-infra |
show version |
|
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-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-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-UNSUPPORTED_XCVR |
3-Error |
Transceiver type GLC-GE-100FX is not supported on SPA-8xGE-V2 |
Transceiver type GLC-GE-100FX is not supported on SPA-8xGE-V2 |
- |
"Consult the documentation and ensure supported " "transceivers are plugged into the SPA" |
|
TRANSCEIVER-3-UNSUPPORTED_XCVR_TYPE |
3-Error |
Transceiver type [chars] is not supported on [chars] |
The transceiver module for the interface specified in the error message is not compatible with the interface. |
spa-infra |
"Consult the documentation and ensure supported " "transceivers are plugged into the SPA" |
|
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-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-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-6-INSERTED_QSA_SFP |
6-Information |
transceiver module inserted in QSA [chars] |
The online insertion and removal OIR facility detected a |
spa-infra |
LOG_STD_NO_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-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-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-REMOVED_QSA_SFP |
6-Information |
Transceiver module removed from QSA [chars] |
The online insertion and removal OIR facility detected the |
spa-infra |
LOG_STD_NO_ACTION |
|
TRANSCEIVER-6-UNSUPPORTED_MODE |
6-Information |
Transceiver module [chars] going in err-disabled state |
The online insertion and removal OIR facility detected the |
spa-infra |
LOG_STD_NO_ACTION |
|
TRANSPORT-3-INIT_FAILED |
3-Error |
Transport map collection initialization failed\n |
The system was unable to allocate memory for storing transport maps. Configuration of transport maps will be unavailable. |
transport |
show memory |
|
TRUNK_CLOCK-3-NOMEMORY |
3-Error |
Failed to allocate memory for the clocks |
The clock switching software has failed to allocate memory\n\ while adding a clock. |
as |
LOG_STD_NO_ACTION |
|
TRUNK_CLOCK-6-BAD_CLOCKS |
6-Information |
There are no good clocks in the system. Remain in HOLDOVER mode |
The clock selection algorithm has failed to select any clock as \n\ the TDM primary clock. |
as |
LOG_STD_NO_ACTION |
|
TRUNK_CLOCK-6-EXTERNAL |
6-Information |
Switching to the user configured external clock on motherboard |
The TDM primary clock is switching from the default clock to the\n\ user configured external clock in motherboard. |
as |
LOG_STD_NO_ACTION |
|
TRUNK_CLOCK-6-FREERUN |
6-Information |
Switching to the user configured freerunning clock on motherboard |
The TDM primary clock is switching from the default clock to the\n\ user configured free running clock in motherboard. |
as |
LOG_STD_NO_ACTION |
|
TRUNK_CLOCK-6-SWITCH |
6-Information |
Switching to the clock on slot [dec] port [dec] priority [dec] as the current primary has gone bad |
The TDM primary clock has switched to a backup clock coming in \n\ via the specified trunk as the current primary clock has gone\n\ bad. |
as |
LOG_STD_NO_ACTION |
|
TRUNK_CLOCK-6-TRUNK |
6-Information |
Switching to the user configured trunk clock on slot [dec] port [dec] priority [dec] |
The TDM primary clock is switching from the default clock to the\n\ user configured trunk clock. |
as |
LOG_STD_NO_ACTION |
|
TRUNK-3-BADCARDTYPE |
3-Error |
Unknown type 0x[hec] in shelf [dec] slot [dec] |
An internal software error occurred. An attempt was made to\n\ reference a shelf number larger than the installed maximum. |
- |
LOG_STD_ACTION |
|
TRUNK-3-BADCLOCK |
3-Error |
selected clock on slot [dec] port [dec] is bad.Accepting the config. |
The clock status as reported by the framer is bad. Either no cable\n\ is plugged in or the port is indeed bad. Configuration is accepted\n\ and as soon as the port in reference turns good it will be \n\ applied. |
- |
"If user is configuring the clocks configuration in advance while\n\ there is no card in the corresponding slot or no cable is plugged\n\ in yet and if he is aware of this fact then there is no action that\n\ needs to be taken. Otherwise choosing another good clock and\n\ troubleshooting the bad clock from the port in reference is \n\ receommended." |
|
TRUNK-3-BADFW |
3-Error |
Invalid framer firmware code file. |
The software has detected an invalid framer firmware image that\n\ cannot be downloaded. |
- |
LOG_STD_ACTION |
|
TRUNK-3-BADMSG |
3-Error |
Bad doorbell message type to framer: [dec] |
An invalid or undefined message type was sent to the framer\n\ processor. |
- |
LOG_STD_ACTION |
|
TRUNK-3-DROP |
3-Error |
T1 Port [dec] on slot [dec] is now in drop-insert mode. |
The user has dropped a T1 port on a CT3 card by pressing the \n\ pushbutton on the CT3 card. This is a disruptive action in that\n\ any existing calls will be dropped. |
- |
"" |
|
TRUNK-3-HBEAT |
3-Error |
No longer receiving heartbeats from framer CPU. |
Communication from the framer processor to the trunk card processor\n\ has stopped. The framer processor is no longer passing status to\n\ the trunk card processor nor accepting messages from the trunk card \n\ processor. |
- |
LOG_STD_ACTION |
|
TRUNK-3-INITFAIL |
3-Error |
Trunk card initialization failed due to: [chars] |
The memory buffer for message passing between the trunk card and\n\ framer processors has been exhausted. Either the messages are not\n\ being picked up or are being generated too quickly. |
- |
LOG_STD_ACTION |
|
TRUNK-3-MSGTMOUT |
3-Error |
Timed out waiting for framer CPU to respond. |
The framer processor did not reply to the read request during a\n\ specified amount of time. |
- |
"" |
|
TRUNK-3-NODROP |
3-Error |
T1 Port [dec] on slot [dec] taken out of drop-insert mode. |
The user has restored a T1 port on a CT3 card by pressing the \n\ pushbutton on the CT3 card. This port was earlier dropped by\n\ the user and has now been taken out of dropped mode. |
- |
"" |
|
TRUNK-3-NOMEM |
3-Error |
Insufficient memory for slot: [dec] in shelf: [dec] |
This message indicates that the router's memory was exhausted while\n\ allocating memory for use with the specified slot and shelf. |
- |
LOG_STD_REDUCE_ACTION |
|
TSP-3-CAPABILITYMISMATCH |
3-Error |
voice port [chars]: call connection id [0x[hec] 0x[hec] 0x[hec] 0x[hec]] |
There was a capabilities mismatch between the two call legs. capabilities are negotiated between call legs for CODEC VAD and FAX rate. |
- |
"Check that the dial peer configuration is appropriate for the interface " "in question. Also check that and configuration on the interface is " "correct." |
|
TSP-3-DSPALARM |
3-Error |
voice port [chars]: status=0x[hec] message=0x[hec] |
The DSP reported a fatal error. All calls on the DSP were dropped and a DSP reload was attempted. |
- |
"Verify that the DSP reloaded properly by attempting to place a call " "on the affected voice port. Contact your technical support " "representative include the full text of the error message." |
|
TSP-3-FSM_ERROR |
3-Error |
[chars] |
Internal Finite State Machine Error. |
- |
"Contact your technical support representative include the full text of\n\ the error message." |
|
TSP-3-NOEVENT |
3-Error |
no free event structure available from [chars] for DSP message |
There were no event structures remaining in the system pools to alert the router of a voice or signaling event. |
- |
"Check that the voice port for which the event was reported is " "still operational. If not clear the voice port." |
|
TSP-5-PRI |
5-Notice |
[chars] at slot [dec] unit [dec] channel [dec] |
A PRI signalling channel is added/deleted to TSP's inventory of signalling channels. |
- |
"This is a notification message only. " "No action is required." |
|
TTY-3-AUTOCONFIG |
3-Error |
TTY[t-line]: Modem auto-configuration failed |
Modem auto-configuration failed either because the modem rejected\n\ the configuration string or because of a timeout. An attempt\n\ should be made to apply the configuration string mannually. |
- |
LOG_STD_ACTION |
|
TTY-3-NOPROCESS |
3-Error |
Cannot create [chars] process |
Failed creating the process. |
- |
LOG_STD_ACTION |
|
TTYDRIVER-2-NOBRKPAK |
2-Critical |
Unable to allocate break block from I/O mem |
The router does not have enough I/O memory for buffers. |
- |
"Consider adding more shared memory. " LOG_STD_ACTION |
|
TTYDRIVER-2-NOBRKPAK |
2-Critical |
Unable to allocate break block from I/O mem |
- |
- |
- |
|
TTYDRIVER-2-NOBUF |
2-Critical |
Unable to allocate [dec] I/O buffers |
A buffer memory shortage existed at the time that the configuration\n\ command was issued. This condition is rare and under normal\n\ conditions temporary. |
- |
LOG_STD_RECUR_ACTION |
|
TTYDRIVER-2-NOBUF |
2-Critical |
Unable to allocate [dec] I/O buffers |
- |
- |
- |
|
TTYDRIVER-2-NOBUFPOOL_ASYNC |
2-Critical |
Unable to create buffer pool for async. mode interface |
There is not enough memory for a per channel control block\n\ of the async TTY driver. |
- |
LOG_STD_REDUCE_ACTION |
|
TTYDRIVER-2-NOBUFPOOL_ASYNC |
2-Critical |
Unable to create buffer pool for async. mode interface |
- |
- |
- |
|
TTYDRIVER-2-NOMEM |
2-Critical |
Unable to allocate [dec] byte status block |
The async TTY driver was unable to create an internal structure\n\ due to a low-memory condition. |
- |
LOG_STD_REDUCE_ACTION |
|
TTYDRIVER-2-NOMEM |
2-Critical |
Unable to allocate [dec] byte status block |
- |
- |
- |
|
TTYDRIVER-3-BADENCAP |
3-Error |
Unknown encapsulation on interface [chars] |
A software error occurred resulting in an unknown encapsulation\n\ type on the interface specified by the error message. |
- |
LOG_STD_ACTION |
|
TTYDRIVER-3-NOPARTS |
3-Error |
No particles available to set up for output on tty [chars] |
A software error occurred resulting in an unexpected exhaustion\n\ of the pool of data buffers used by the modem drivers. |
- |
LOG_STD_ACTION |
|
TTYDRIVER-3-NOTXPART |
3-Error |
Non-zero outcount but no transmit particle on tty [chars] |
A software error occurred resulting in an invalid state for the\n\ RTS modem signal |
- |
LOG_STD_ACTION |
|
TTYDRIVER-3-UNKNOWN_PORT_ARCH_TYPE |
3-Error |
Unknown port type [dec] |
A software error occurred due to an unrecognised port type |
- |
LOG_STD_ACTION |
|
TUN-3-6RD |
3-Error |
[chars]: [chars] |
The tunnel 6RD feature encountered an internal software error |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-3-API_ARGS |
3-Error |
unexpected arguments: [chars] [chars] |
A public tunnel component api was driven with arguments outside the expected boundaries. |
ip-tunnels |
LOG_STD_ACTION |
|
TUN-3-CM1 |
3-Error |
[chars] |
The tunnel classification module encountered an internal software error |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-3-CM2 |
3-Error |
[chars] [dec] |
The tunnel classification module encountered an internal software error |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-3-DECAP_OCE |
3-Error |
[chars] [chars] |
An internal software error occurred in the tunnel subsystem which is responsible for building forwarding for the purposes of decapsulation |
- |
LOG_STD_ACTION |
|
TUN-3-DECAP_TINFO |
3-Error |
[chars] [chars] |
An internal software error occurred in the tunnel subsystem which is responsible for driving forwarding based on the tinfo configuration |
- |
LOG_STD_ACTION |
|
TUN-3-ENDPOINT_ERROR |
3-Error |
[chars] [chars] |
An internal software error occurred when manipulating the tunnel\n\ endpoint database |
TUNNEL_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
TUN-3-ENDPOINT_STORE |
3-Error |
Operation [chars] failed for [chars] |
Manipulation of the tunnel endpoint store failed. |
ip-tunnels |
LOG_STD_ACTION |
|
TUN-3-GROUPS |
3-Error |
Tunnel Groups: [chars]: [chars] |
The tunnel group component encountered an internal software error |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-3-ILLEGAL_ARGS |
3-Error |
Illegal arguments - [chars] |
An internal software error occurred. |
- |
LOG_STD_ACTION |
|
TUN-3-L3VPN_ENCAP_IP_PROFILE |
3-Error |
L3VPN Encap IP : [chars]: [chars] |
The L3VPN Encap IP component encountered an internal software error |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-3-L3VPN_GROUP |
3-Error |
Tunnel L3VPN Groups: [chars]: [chars] |
The tunnel group component encountered an internal software error |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-3-MTUCONFIGEXCEEDSL2MTU_IPV4 |
3-Error |
[chars] IPv4 MTU configured [dec] exceeds tunnel maximum MTU [dec] |
An IPv4 MTU value is configured on the tunnel interface and this value\n\ exceeds the tunnel's maximum MTU. This message is typically observed\n\ when the tunnel header size changes or when the MTU of the underlying\n\ exit interface changes. As a result of either the tunnel maximum MTU\n\ can change. This message can also be observed when using an IPv6\n\ tunnel to carry IPv4 since IPv4 MTU config in this case allows for a\n\ value to be configured that is greater than the tunnel's maximum MTU.\n\ As a result of any of these conditions packets may be dropped. |
TUNNEL_DDTS_COMPONENT |
"If a specific IPv4 MTU value is not required it is recommended that\n\ you leave the value at the default by typing <CmdBold>no ip mtu\n\ <NoCmdBold> on the tunnel interface. If a specific value is required\n\ it is recommended that you check the interface MTU value from the\n\ <CmdBold>show interface tunnel<NoCmdBold> command and adjust\n\ <CmdBold>ip mtu<NoCmdBold> on the tunnel interface to be lower than or\n\ equal to this." |
|
TUN-3-MTUCONFIGEXCEEDSL2MTU_IPV6 |
3-Error |
[chars] IPv6 MTU configured [dec] exceeds tunnel maximum MTU [dec] |
An IPv6 MTU value is configured on the tunnel interface and this value\n\ exceeds the tunnel's maximum MTU. This message is typically observed\n\ when the tunnel header size changes or when the MTU of the underlying\n\ exit interface changes. As a result of either the tunnel maximum MTU\n\ can change. This message can also be observed when using an IPv6\n\ tunnel to carry IPv6 since IPv6 MTU config in this case allows for a\n\ value to be configured that is greater than the tunnel's maximum MTU.\n\ As a result of any of these conditions packets may be dropped. |
TUNNEL_DDTS_COMPONENT |
"If a specific IPv6 MTU value is not required it is recommended that\n\ you leave the value at the default by typing <CmdBold>no ipv6 mtu\n\ <NoCmdBold> on the tunnel interface. If a specific value is required\n\ it is recommended that you check the interface MTU value from the\n\ <CmdBold>show interface tunnel<NoCmdBold> command and adjust\n\ <CmdBold>ipv6 mtu<NoCmdBold> on the tunnel interface to be lower than\n\ or equal to this." |
|
TUN-3-MULTI_KEYS_INFO |
3-Error |
[chars] [chars] |
Manipulation of the tunnel keys database failed. |
ip-tunnels |
LOG_STD_ACTION |
|
TUN-3-MULTI_KEYS_INFO_ERROR |
3-Error |
[chars] [dec] |
Manipulation of the tunnel keys database failed\n\ because of incorrect idb_index. |
ip-tunnels |
LOG_STD_ACTION |
|
TUN-3-OTV_GROUP |
3-Error |
Tunnel OTV Groups: [chars]: [chars] |
The tunnel group component encountered an internal software error |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-3-SIA_GROUP |
3-Error |
Tunnel SIA Groups: [chars]: [chars] |
The tunnel group component encountered an internal software error |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-3-TERM_ADJ |
3-Error |
Terminal adjacency [chars][chars][chars] |
An internal software error occurred. |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-3-TUN_DBG |
3-Error |
TUN_DBG: [chars] [chars] |
An internal software error occurred. |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-3-TUN_HA |
3-Error |
Tunnel HA: [chars] |
Tunnel HA encountered an internal software error |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-3-TUN_SB |
3-Error |
TUN_SB: [chars][chars][chars] |
An internal software error occurred. |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-3-TUN_SIDB2TUNS |
3-Error |
[chars]: [chars] |
An internal software error occurred. |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-3-TUNTO |
3-Error |
Operation: [chars] Action: [chars] Reason: [chars] |
The tunnel-to module encountered an internal software error |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-3-WCCP_GROUP |
3-Error |
Tunnel WCCP Groups: [chars]: [chars] |
The tunnel group component encountered an internal software error |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-4-L3VPN_ENCAP_IP_SRC_DEL |
4-Warning |
L3VPN Encap IP : [chars]: [chars] |
The user configuration change results in a warning. This message is typically printed when the user tries to delete a loopback interface and the loopback interface is configured as the source interface of the L3VPN encap IP profile |
TUNNEL_DDTS_COMPONENT |
"It is recommended that the user removes the loopback interface as the source interface of the L3vpn encap ip profile before deleting the loopback interface." |
|
TUN-4-MTUCONFIGEXCEEDSTRMTU_IPV4 |
4-Warning |
[chars] IPv4 MTU configured [dec] exceeds tunnel transport MTU [dec] |
- |
TUNNEL_DDTS_COMPONENT |
"If a specific IPv4 MTU value is not required it is recommended that\n\ you leave the value at the default by typing <CmdBold>no ip mtu\n\ <NoCmdBold> on the tunnel interface. If a specific value is required\n\ it is recommended that you check the tunnel transport MTU value from\n\ the <CmdBold>show interface tunnel<NoCmdBold> command and adjust\n\ <CmdBold>ip mtu<NoCmdBold> on the tunnel interface to be lower than or\n\ equal to this." |
|
TUN-4-MTUCONFIGEXCEEDSTRMTU_IPV6 |
4-Warning |
[chars] IPv6 MTU configured [dec] exceeds tunnel transport MTU [dec] |
- |
TUNNEL_DDTS_COMPONENT |
"If a specific IPv6 MTU value is not required it is recommended that\n\ you leave the value at the default by typing <CmdBold>no ipv6 mtu\n\ <NoCmdBold> on the tunnel interface. If a specific value is required\n\ it is recommended that you check the tunnel transport MTU value from\n\ the <CmdBold>show interface tunnel<NoCmdBold> command and adjust\n\ <CmdBold>ipv6 mtu<NoCmdBold> on the tunnel interface to be lower than\n\ or equal to this." |
|
TUN-4-MTUCONFIGLESSTHAN_MINIPV4MTU |
4-Warning |
[chars] IPv4 MTU [dec] is lesser than the minimum IP MTU [dec] fragmentation may occur |
The IPv4 MTU value calculated on the tunnel interface is less than\n\ the minimum IP MTU. The MTU of the underlying exit interface of the\n\ tunnel is too small. As a result fragmentation of the transport packet\n\ may occur before this goes out of the underlying exit interface. |
TUNNEL_DDTS_COMPONENT |
"If a specific MTU value is not required for the exit interface it is\n\ recommended that you leave the value at the default by typing\n\ <CmdBold>no mtu <NoCmdBold> on the exit interface. If a specific value\n\ is required it is recommended that you check the MTU value from\n\ the <CmdBold>show interface <NoCmdBold> command for the exit interface\n\ and adjust <CmdBold>mtu<NoCmdBold> on the tunnel exit to be higher than\n\ this." |
|
TUN-4-MTUDEFAULTEXCEEDSL2MTU_IPV4 |
4-Warning |
[chars] transport MTU [dec] exceeds [chars] configured IPv4 MTU [dec] fragmentation may occur |
A default MTU value has been configured on the tunnel and this\n\ value exceeds the underlying physical interface MTU. As a result\n\ fragmentation of the transport packet may occur before this goes out\n\ of the underlying exit interface. |
TUNNEL_DDTS_COMPONENT |
"If possible increase the size of the IPv4 MTU on the underlying\n\ physical interface using <CmdBold>ip mtu<NoCmdBold>." |
|
TUN-4-UDLR_IDB_ERROR |
4-Warning |
UDLR [chars] - [chars] |
An error was encountered on a udlr interface |
TUNNEL_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
TUN-5-6RD_INFO |
5-Notice |
[chars]: [chars] |
6RD configuration has been removed as it is not compatible with the\n\ new sub-mode |
TUNNEL_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
TUN-5-HW_IF_INDEX_ILLEGAL |
5-Notice |
Attempt to create tunnel interface for [chars] with illegal index: [dec] |
Creation of tunnel interface failed. |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-5-IGNOREICMP6MTU |
5-Notice |
[chars] ignoring received ICMP6 Type 2 Code 0 due to pmtud min-mtu setting |
- |
TUNNEL_DDTS_COMPONENT |
"If you want the ICMP6 packet to be accepted and to be used to decrease\n\ the tunnel MTU then use the <CmdBold>tunnel path-mtu-discovery min-mtu\n\ <NoCmdBold> command to decrease the minimum mtu allowed. The min-mtu\n\ specified is the minimum tunnel payload mtu allowed.\n\ Use the <CmdBold>show interface tunnel<NoCmdBold> command to view the\n\ current path mtu discovery settings." |
|
TUN-5-IGNOREICMPMTU |
5-Notice |
[chars] ignoring received ICMP Type 3 Code 4 due to pmtud min-mtu setting |
- |
TUNNEL_DDTS_COMPONENT |
"If you want the ICMP packet to be accepted and to be used to decrease\n\ the tunnel MTU then use the <CmdBold>tunnel path-mtu-discovery min-mtu\n\ <NoCmdBold> command to decrease the minimum mtu allowed. The min-mtu\n\ specified is the minimum tunnel payload mtu allowed.\n\ Use the <CmdBold>show interface tunnel<NoCmdBold> command to view the\n\ current path mtu discovery settings." |
|
TUN-5-INIT_ERROR |
5-Notice |
A critical error [chars]occurred during initialization |
Creation of tunnel subsystem failed. |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-5-L3VPN_IP_PROFILE_DELETE |
5-Notice |
l3vpn encap ip profile [chars] deleted |
l3vpn encap ip profile is deleted |
TUNNEL_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
TUN-5-MPLS_TE |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
TUN-5-RECURDOWN |
5-Notice |
[chars] temporarily disabled due to recursive routing |
- |
TUNNEL_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
TUN-5-RECURDOWN_SRC |
5-Notice |
[chars] linestate down recursive source interface next output [chars] |
Whilst evaluating tunnel linestate we revisted a source interface. |
ip-tunnels |
LOG_STD_ACTION |
|
TUN-5-TUN_DB_IF |
5-Notice |
Operation on tunnel interface table failed for [chars] - [chars] |
Manipulation of the tunnel interface table failed. |
ip-tunnels |
LOG_STD_ACTION |
|
TUN-5-TUN_HWIDB_DELETE |
5-Notice |
Failed to delete hwidb for Tunnel [dec] index [dec] |
Deletion of tunnnel interface failed. |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-5-TUN_HWIDB_LIST_DELETE |
5-Notice |
Failed to delete [chars] from tunnel hwidb list |
Deletion of tunnnel from hwidb list failed. |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-5-TUN_HWIDB_LIST_INSERT |
5-Notice |
Failed to add [chars] to tunnel hwidb list |
Insertion of tunnnel to hwidb list failed. |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-5-TUN_HWIDB_RECYCLE |
5-Notice |
Failed to recycle hwidb for Tunnel [dec] index [dec] |
Recycling of tunnnel interface failed. |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-5-TUN_INTF_STATE_RESET |
5-Notice |
Failed to reset tunnel interface state for [chars] |
Reset of tunnnel interface failed. |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-5-TUN_LIST_CREATE |
5-Notice |
Failed to create tunnel list [chars] |
Creation of tunnel list failed. |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-5-TUN_SWIDB_DELETE |
5-Notice |
Failed to delete swidb for Tunnel [dec] index [dec] |
Deletion of tunnnel interface failed. |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-5-TUN_SWIDB_RECYCLE |
5-Notice |
Failed to recycle swidb for Tunnel [dec] index [dec] |
Recycling of tunnnel interface failed. |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-5-TUN_TABLE |
5-Notice |
Operation [chars] on tunnel table failed for [chars] - [chars] |
Manipulation of the tunnel table failed. |
ip-tunnels |
LOG_STD_ACTION |
|
TUN-5-TUN_UNIT_LIST_DELETE |
5-Notice |
Failed to delete entry unit [dec] to tunnel unit list |
Deletion from tunnnel unit failed. |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUN-5-TUN_UNIT_LIST_INSERT |
5-Notice |
Failed to add entry unit [dec] to tunnel unit list |
Insertion of tunnnel unit failed. |
TUNNEL_DDTS_COMPONENT |
LOG_STD_ACTION |
|
TUNNELKILL-3-MPLS_TE |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
TUNSS-3-PROTECTION_PROCESS_FAIL |
3-Error |
Failed to create tunnel security process |
We failed to start a processes necessary to do tunnel protection. |
tunnel |
LOG_STD_ACTION |
|
TUNSS-3-TUN_API_ARGS |
3-Error |
unexpected arguments: [chars] [chars] |
This API should be used only for a tunnel interface. |
tunnel |
LOG_STD_ACTION |
|
TUNSS-6-PROTECTION_BAD_TUN_MODE |
6-Information |
Tunnel mode [chars] not supported by tunnel protection. Protection removed. |
The chosen tunnel mode is not supported by tunnel protection interfaces so protection has been turned off and removed. |
tunnel |
"Unless protection is desired on this interface no " "action is required. If protection is desired a " "crypto-map must be used instead." |
|
TVI_PROXY-2-TVI_MSG_PROXYINIT_FAILURE |
2-Critical |
ET-Analytics - Failed to register IPC message handler result code [dec] |
QFP ET-Analytics feature failed to register an IPC message handler for communication with control plane. This will cause the featue not to function. |
TVI_COMP_NAME |
LOG_STD_ACTION |
|
TVI_PROXY-3-PROXY_HSL_ADD_DEST_FAILED |
3-Error |
- |
HSL add destination failed. |
cpp-ucode |
LOG_STD_ACTION |
|
TVI_PROXY-3-PROXY_HSL_BIND_FAILED |
3-Error |
- |
HSL bind failed. |
cpp-ucode |
LOG_STD_ACTION |
|
TVI_PROXY-3-PROXY_HSL_BIND_TEMPLATE_FAILED |
3-Error |
[dec] |
HSL bind tempalte failed at given index. |
cpp-ucode |
LOG_STD_ACTION |
|
TVI_PROXY-3-PROXY_HSL_CREATE_FAILED |
3-Error |
- |
HSL creation failed. |
cpp-ucode |
LOG_STD_ACTION |
|
TVI_PROXY-3-PROXY_HSL_ENABLE_FAILED |
3-Error |
- |
HSL enable failed. |
cpp-ucode |
LOG_STD_ACTION |
|
TVI_PROXY-3-PROXY_HSL_MODIFY_DEST_FAILED |
3-Error |
- |
HSL modify destination failed. |
cpp-ucode |
LOG_STD_ACTION |
|
TVI_PROXY-3-PROXY_HSL_MODIFY_FAILED |
3-Error |
- |
HSL modification failed. |
cpp-ucode |
LOG_STD_ACTION |
|
TVI_PROXY-3-TVI_MSG_PROXY_ALLOC_FAILURE |
3-Error |
ET-Analytics - Failed to get [dec] bytes space for IPC reply message |
QFP ET-Anallytics feature detected buffer allocation failure while sending reply to a message from another layer of ET-Analytics feature's software stack. |
TVI_COMP_NAME |
LOG_STD_ACTION |
|
TVI_PROXY-3-TVI_MSG_PROXY_DEBUG_REG_FAILED |
3-Error |
- |
ET-Analytics Conditional Debugging Registration failed. |
TVI_COMP_NAME |
LOG_STD_ACTION |
|
TVI_PROXY-3-TVI_MSG_PROXY_INVALID_MSGLEN |
3-Error |
ET-Analytics - Received an invalid length IPC message |
QFP ET-Analytics feature received an incorrect length of IPC message from anoter layer of ET-Analytics feature's software stack m_enum [dec] m_subtype [dec] m_len [dec] m_flags 0x[hec] m_source [dec]. |
TVI_COMP_NAME |
LOG_STD_ACTION |
|
TVI_PROXY-3-TVI_MSG_PROXY_IPCSEND_FAIL |
3-Error |
ET-Analytics - Failed to send IPC message result code [dec] |
QFP ET-Analytics feature failed to send IPC message to another layer of ET-Analytics feature's software stack. |
TVI_COMP_NAME |
LOG_STD_ACTION |
|
TVI_PROXY-3-TVI_MSG_PROXY_OPENREPLY_FAIL |
3-Error |
ET-Analytics - Failed to open reply message part of IPC packet |
QFP ET-Analytics feature failed to open message part of IPC packet while sending a reply to another layer of ET-Analytics feature's software stack. |
TVI_COMP_NAME |
LOG_STD_ACTION |
|
TVI_PROXY-3-TVI_MSG_PROXY_UNKNOWN_IPCMSG |
3-Error |
ET-Analytics - Received an unknown type code [dec] IPC message |
QFP ET-Analytics feature received an unknown message from another layer of ET-Analytics feature's software stack. |
TVI_COMP_NAME |
LOG_STD_RECUR_ACTION |
|
TVI_PROXY-4-PROXY_HSL_ALREADY_INIT |
4-Warning |
- |
HSL logger already initialized |
cpp-ucode |
LOG_STD_ACTION |
|
TVI_PROXY-4-PROXY_HSL_NOT_INIT |
4-Warning |
[dec] |
HSL logger not initialized |
cpp-ucode |
LOG_STD_ACTION |
|
TVI_PROXY-4-PROXY_IPC_INVALID_MSG_LEN |
4-Warning |
[dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Invalid ET-Analytics IPC message length. |
cpp-ucode |
LOG_STD_ACTION |
|
TXCONN-3-BADLICENSEKEY |
3-Error |
Bad license key configured for Transaction Connection. |
The license key configured with the txconn license configuration\n\ command is not valid. |
txconn |
"Check that the license key was entered correctly in the txconn\n\ license configuration command. Refer to the txconn feature documentation\n\ for information on how to obtain a valid license key." |
|
TXCONN-3-BADMODE |
3-Error |
Unknown mode '[chars]' configured for server [chars] |
The mode configured for the txconn server was rejected by the\n\ remote database server. |
txconn |
"Contact your SNA network administrator to determine the correct\n\ name of the mode to use to connect to DB2 on the remote database\n\ server." |
|
TXCONN-3-BADRLU |
3-Error |
Bad remote LU '[chars]' configured for server [chars] |
The remote LU configured for the txconn server is incorrect. |
txconn |
"Contact your SNA network administrator to determine the correct\n\ name of the remote LU for DB2 on the remote database server. Be sure to\n\ check that the SNA network name is correct as well as the LU name." |
|
TXCONN-3-INVALIDTRANS |
3-Error |
Bad Transaction ID flushing out request for client [inet] connected server [chars] killing connection. |
Bad input stream. |
txconn |
"This is an informational message. " LOG_STD_NO_ACTION |
|
TXCONN-3-NOSESSION |
3-Error |
Out of resource cannot create transaction for client [inet] connected server [chars] killing connection. |
The router is out of memory. |
txconn |
"This is an informational message. " LOG_STD_NO_ACTION |
|
TXCONN-3-TXEXCEPTION |
3-Error |
Exception [chars] from transaction [chars] to [chars] from client [inet] |
An unexpected transaction error occurred. |
txconn |
LOG_STD_ACTION " If possible also provide the output of the debug txconn data\n\ command and an SNA line trace between the router and the remote\n\ database server for the period during which this message appeared." |
|
TXCONN-3-UNEXPECTEDREQ |
3-Error |
Unexpected client data flushing out the request for client [inet] connected server [chars]. |
Bad input stream. |
txconn |
"This is an informational message. " LOG_STD_NO_ACTION |
|
TXCONN-5-CONNIDLETIMEOUT |
5-Notice |
Client [inet] connected to server [chars] has timed out after %TE. |
The client was idle for too long and the idle timeout configured\n\ for the txconn server expired. |
txconn |
"This is an informational message only. " LOG_STD_NO_ACTION |
|
TXCONN-5-SECFAIL |
5-Notice |
APPC security failed client [inet] using userid '[chars]' for server [chars] |
The userid and/or password passed in by the client were rejected by\n\ the remote database server. |
txconn |
"This is an informational message only. " LOG_STD_NO_ACTION |
|
TXCONN-5-TARGETDOWN |
5-Notice |
CICS server [chars] has become unavailable. Recovery is in progress. |
A CICS server for a configured destination has become unavailable. All client\n\ connections to this server will be rejected until it becomes available again. |
txconn |
"This is an informational message only. " LOG_STD_NO_ACTION |
|
TXCONN-5-TARGETUP |
5-Notice |
CICS server [chars] is now available. |
A CICS server that was previously unavailable has become available. All client\n\ connections to this server will now be accepted. |
txconn |
"This is an informational message only. " LOG_STD_NO_ACTION |
|
TXCONN-5-TRANSIDLETIMEOUT |
5-Notice |
Transaction [hec] of Client [inet] connected to server [chars] has timed out after %TE. |
The transaction was idle for too long and the idle timeout configured\n\ for the txconn server expired. |
txconn |
"This is an informational message only. " LOG_STD_NO_ACTION |
|
UBR10K_CLC_GE-3-SW_CTRL_ERR |
3-Error |
slot [dec]/[dec] controller [dec]: [chars] |
software error in CLC GigE interface |
ubr10k-sw |
LOG_STD_ACTION |
|
UBR10K_CLC_GE-3-SW_SLOT_ERR |
3-Error |
slot [dec]/[dec]: [chars] |
software error in CLC GigE interface |
ubr10k-sw |
LOG_STD_ACTION |
|
UBR10K_REDUNDANCY-3-CHKPT_INTERNAL |
3-Error |
Internal PRE checkpointing error [[chars]] |
An internal error occurred within the PRE checkpointing code |
ubr10k-pre-redundancy |
LOG_STD_ACTION |
|
UBR10K_REDUNDANCY-3-CREATEFAIL |
3-Error |
UBB10K HA Entity CF rcv process create failed |
Failed to create the ubr10k HA entity checkpoint receive process |
ubr10k-pre-redundancy |
LOG_STD_ACTION |
|
UBR10K_REDUNDANCY-4-MSGVERSION |
4-Warning |
Incompatible message version with slot [dec] |
There is incompatibility between the the message version being sent by the line card and the message version used by the RP. This type of incompatibility could happen if the RP and Schooner line card are using different IOS versions due to an RP oir event |
ubr10k-pre-redundancy |
"A microcode reload will solve the problem. " |
|
UBR10K_REDUNDANCY-4-RP_HA_STDBY_INCONSISTENT |
4-Warning |
Standby PRE dropping inconsistent sync messages [chars] [chars]. |
An inconsistency was detected within the PRE config/data sync code. This can occur under normal situations if a cable linecard is reset while the standby PRE is still coming up. Further debugging can be turned on to dump contents of inconsistency sync packets |
ubr10k-pre-redundancy |
LOG_STD_ACTION |
|
UBR10K-0-CLI_CMD |
0-Emergency |
CMTS[dec]/[dec] [chars] failed |
Most likely S/W failure |
ubr10k-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR10K-0-CLI_CONFIG |
0-Emergency |
CMTS[dec]/[dec]/[dec] schrp_cli_cmd failed in [chars] |
Most likely S/W failure |
ubr10k-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR10K-0-LCPOWEREDOFF |
0-Emergency |
Linecard Slot [dec]/[dec] device has reached critical temperature [dec] Linecard powered off Critical Threshold [dec] Last Temperature [dec] |
Linecard temperature value is critical |
ubr10k-sw |
LOG_STD_ACTION |
|
UBR10K-0-SNMP_SET_IPC |
0-Emergency |
Schooner SNMP SET[dec]/[dec] [chars] failed |
SNMP SET failed due to either IPC failure or line card SET failed |
ubr10k-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR10K-1-CLCRESET |
1-Alert |
line card reset slot [dec]/[dec] |
Recover from MC16S HW initialization failure. |
ubr10k-sw |
"If it happens to non-MC16S CLC copy the error message exactly as it " "appears and report it to your technical support representative." |
|
UBR10K-1-INITFAIL |
1-Alert |
Schooner subsystem init fails:[chars] |
Schooner System initialization failure. |
ubr10k-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR10K-1-INVALID_DIVHDR |
1-Alert |
Invalid diversion hdr on pkt: cause [dec] channel 0x[hec] length [dec] |
RP received a corrupt diverted packet from the cable linecard |
ubr10k-sw |
"Capture the logs and contact the TAC." |
|
UBR10K-1-INVALIDPRIMSID |
1-Alert |
Dropping punted pkt from sid [dec] prim sid [dec] src [enet] hw [chars] |
RP received a diverted packet with invalid primary sid from the cable linecard |
ubr10k-sw |
"Capture the logs and contact the TAC." |
|
UBR10K-1-INVALIDSID |
1-Alert |
Dropping punted pkt from sid [dec] src [enet] hw [chars] |
RP received a corrupt diverted packet from the cable linecard |
ubr10k-sw |
"Capture the logs and contact the TAC." |
|
UBR10K-1-IPCFAIL |
1-Alert |
Schooner subsystem IPC init fails for interface [chars] on [chars]: in [chars] |
Schooner System IPC initialization failure. |
ubr10k-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR10K-1-JTAG_POWCYCLE |
1-Alert |
Power cycle slot [dec]/[dec] |
Recover from 2020 power sequency error. |
ubr10k-sw |
"If it happens continuously copy the error message exactly as it " "appears and report it to your technical support representative. " "If it stops after one or a few power cycles " "the HW is recovered fully." |
|
UBR10K-1-POWCYCLE |
1-Alert |
Power cycle slot [dec]/[dec] |
Recover from MC16S HW initialization failure. |
ubr10k-sw |
"If it happens to non-MC16S CLC copy the error message exactly as it" " appears and report it to your technical support representative." |
|
UBR10K-1-SNMP_GETINDEX_FAIL |
1-Alert |
Cannot get SNMP physical Index for [chars] |
Schooner System initialization failure. |
ubr10k-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR10K-1-SNMP_SENDCMD_FAIL |
1-Alert |
Error sending command type [dec] which [dec] |
Schooner System initialization failure. |
ubr10k-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR10K-1-SNMP_SENDINFO_FAIL |
1-Alert |
Error sending SNMP info to [chars] |
Schooner System initialization failure. |
ubr10k-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR10K-1-UNKEVT |
1-Alert |
Schooner subsystem unknown event:[dec] in [chars] for interface [chars] |
Schooner System receive unknown event type. |
ubr10k-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR10K-1-UNKREQ |
1-Alert |
Schooner subsystem unknown request:[dec] |
Schooner System received unknown request type. |
ubr10k-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR10K-1-UNKVECT |
1-Alert |
Schooner subsystem unknown vector:[dec] |
Schooner System received unknown vector. |
ubr10k-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR10K-2-CLI_UNSUPPORTED_CMD |
2-Critical |
cable modem <ipaddr/macaddr> cmd not supported in Schooner |
Currently unsupported command |
ubr10k-sw |
"" |
|
UBR10K-3-CFRNOINDEX |
3-Error |
Classifier control block index allocation failure |
The system has run out of PXF resources to set up any new packet classifier state |
ubr10k-sw |
"This would typically happen only on a very overloaded system. So the only " "way out is to remove CMs from this system" |
|
UBR10K-3-CFRNOMACRWIP |
3-Error |
Invalid IP address mapping for of CPE [enet] belonging to CM [enet] |
Due to an inconsistency between the PXF FIB and the RP CPE data structures the packet classification state cannot be setup correctly |
ubr10k-sw |
"Try to force the CPE to get an IP address again. Also gather information " "about the cable modem and file a bug" |
|
UBR10K-3-CNNR_DSYNC |
3-Error |
Dynamic sync failed for [chars]:U[dec] connector mapping expect:[dec] current:[dec] cause:[chars] |
URM failed to sync connector-receiver mapping from active RP to stby RP. |
ubr10k-sw |
"clear and re-configure the connector command for the affected MD:US." "Or reload stby RP" |
|
UBR10K-3-FPSUBINIT |
3-Error |
Unable to create subinterface [chars] for hw interface [chars] in the fast path |
The system was unable to create the cable subinterface data structures in the fast path |
ubr10k-sw |
"Gather information about running configuration and amount of memory " "in the system and file a bug" |
|
UBR10K-3-IRONBUS_BAD_CHECKSUM |
3-Error |
Bad checksum in ironbus IPC packetexpected 0x[hec] actual 0x[hec]. |
- |
- |
- |
|
UBR10K-3-QALLOCFAIL |
3-Error |
Failure to allocate QoS queue for service flow %lu on [chars] MAC_addr [enet] |
The system has run out of PXF queues |
ubr10k-sw |
"This would typically happen only on a very overloaded system. So the only " "way out is to remove CMs from this system" |
|
UBR10K-3-QALLOCFAIL_INFO |
3-Error |
Failure to allocate QoS queue: [chars] |
The system has run out of PXF queues providing additional debugging information |
ubr10k-sw |
"This would typically happen only on a very overloaded system. So the only " "way out is to remove CMs from this system" |
|
UBR10K-3-QALLOCFAIL_MCAST |
3-Error |
Failure to allocate MQoS queue for service flow %lu on [chars] Group [chars] Source [chars] |
The system has run out of PXF queues |
ubr10k-sw |
"This would typically happen only on a very overloaded system. So the only " "way out is to remove CMs from this system" |
|
UBR10K-3-ROMMON_UPDATE_ERROR |
3-Error |
Linecard Slot [dec]/[dec] update error: [chars] |
Linecard ROMMON update error. |
ubr10k-sw |
"Capture the logs and contact the TAC." "If persistent replace the card" |
|
UBR10K-3-ROMMON_VERSION_ERROR |
3-Error |
Linecard Slot [dec]/[dec] version error: [chars] |
Failed to find bundled or programmed ROMMON version. |
ubr10k-sw |
"Capture the logs and contact the TAC." "If persistent replace the card" |
|
UBR10K-3-UTIL_CARD_UNINITIALIZED_ERROR |
3-Error |
Util card [dec] uninitialized |
- |
- |
- |
|
UBR10K-3-VOLTABNORMAL |
3-Error |
The PEM [dec] voltage value [dec] is abnormal |
Chassis voltage value is abnormal |
ubr10k-sw |
LOG_STD_ACTION |
|
UBR10K-4-HW_ASSIST_WDOG_FAILURE |
4-Warning |
Send lchung packet to Card[dec]/[dec] failed |
send lchung packet to line card failure maybe due to low buffer |
ubr10k-sw |
LOG_STD_ACTION |
|
UBR10K-4-HW_ASSIST_WDOG_TIMEOUT |
4-Warning |
Card[dec]/[dec] HW assist watchdog timeout\n |
PRE send LCHung packet to Line card in extend time maybe HW assist watchdog not supported in Line card or disabled. |
ubr10k-sw |
LOG_STD_ACTION |
|
UBR10K-4-INVALID_PKT_FILTER_GROUP |
4-Warning |
Invalid [chars]_filter_group [dec] IP_addr = [inet] |
CM-config-file specifies a filter-group greater than the platform maximum |
ubr10k-sw |
"Capture the logs and contact the TAC." |
|
UBR10K-4-MSGVERSION |
4-Warning |
Incompatible message version with slot [dec] |
There is incompatibility between the the message version being sent by the line card and the message version used by the RP. This type of incompatibility could happen if the RP and Schooner line card are using different IOS versions due to an RP oir event |
ubr10k-sw |
"A microcode reload will solve the problem. " |
|
UBR10K-4-ROMMON_UPDATE_MUTED |
4-Warning |
Linecard Slot [dec]/[dec] ROMMON update is temporarily disabled due to a limit on unsuccessful attempts. The card may not have the latest firmware |
ROMMON update is temporarily blocked to prevent multiple reloads |
ubr10k-sw |
"Wait 10 min reset the linecard to restart ROMMON upgrade" "Capture the logs and contact the TAC." |
|
UBR10K-4-ROMMON_UPDATE_POSTFALPOS_MUTED |
4-Warning |
Linecard Slot [dec]/[dec] ROMMON update from [dec] to [dec] is temporarily disabled due to a limit on consequtive attempts. The card may not have the latest firmware |
ROMMON update is temporarily blocked to prevent multiple reloads |
ubr10k-sw |
"Wait 10 min reset the linecard to restart ROMMON upgrade" "Capture the logs and contact the TAC." |
|
UBR10K-5-CNNR_DSYNC_NOTICE |
5-Notice |
Dynamic sync notice for [chars]:U[dec] connector mapping expect:[dec] current:[dec] cause:[chars] |
URM connector-receiver mapping from active RP to stby RP notice no service impact |
ubr10k-sw |
"This is only a notice no service impact" |
|
UBR10K-5-ROMMON_UPDATE_DONE |
5-Notice |
ROMMON update [chars] for slot [dec]/[dec] |
Linecard ROMMON update done. |
ubr10k-sw |
LOG_STD_ACTION |
|
UBR10K-5-ROMMON_UPDATE_START |
5-Notice |
ROMMON [chars] from version [dec] to version [dec] started for slot [dec]/[dec] |
Linecard ROMMON upgrade start. |
ubr10k-sw |
LOG_STD_ACTION |
|
UBR10K-6-ACFE_REJECTION |
6-Information |
ACFE has rejected QoS queue for service flow %lu on [chars] MAC_addr [enet] min_rate [dec] kbps rej_code [dec] |
ACFE has rejected this CIR flow due to heavy CIR reservation on this or adjacent interfaces |
ubr10k-sw |
"This would typically happen only on a very overloaded interface." "If it persists on an interface try to provision more RF channels" |
|
UBR10K-6-ACFE_REJECTION_MCAST |
6-Information |
ACFE has rejected QoS queue for service flow %lu on [chars] Group [chars] Source [chars] min_rate [dec] kbps rej_code [dec] |
ACFE has rejected this CIR flow due to heavy CIR reservation on this or adjacent interfaces |
ubr10k-sw |
"This would typically happen only on a very overloaded interface." "If it persists on an interface try to provision more RF channels" |
|
UBR10K-6-CM_INCONSISTENCY |
6-Information |
CM state inconsistency [enet]msgp [enet] sid [dec] [dec] mac state [dec] hwidb [chars] |
Received INIT_CM for an online CM Copy the message and report to your technical support representative |
ubr10k-sw |
LOG_STD_ACTION |
|
UBR10K-6-COMPAT_IGNORED |
6-Information |
OIR compatibility is disabled because [chars] |
OIR compatibility is disabled because of a conflict with another feature. |
ubr10k-sw |
"Disable OIR compatability or the conflicting feature." |
|
UBR10K-6-COMPAT_NEW_CARD |
6-Information |
The [chars] in slot [dec]/[dec] has been replaced by a [chars]. |
A line card has been replaced by a compatible line card. |
ubr10k-sw |
"This is not an error." |
|
UBR10K-6-COMPAT_NO_CFG |
6-Information |
OIR compatibility does not support the [chars] in slot [dec]/[dec]. [chars] |
A line card that is supported by the OIR compatibility feature is not not supported in the specified slot/subslot. |
ubr10k-sw |
"This is most likely a software problem and should be reported to development. OIR compatibility for the given slot/subslot should be disabled until the problem is resolved." |
|
UBR10K-6-COMPAT_SHUTDOWN_CARD |
6-Information |
Failed to restore the configuration for [chars]. |
A CMTS interface has been placed in the shutdown state by the OIR-compatibility feature because a saved configuration could not be used on a compatible line card. This will happen during an OIR operation if the replacement card provides only a subset of the functionality of the original card and the previous card was configured for features that are not backward compatible. |
ubr10k-sw |
"Manually reconfigure the interface to match the line card's capability." |
|
UBR10K-6-DS_SFID_INCONSISTENCY |
6-Information |
DS-SF found: SFID [dec] type [dec] MAC [enet][enet] prim_sid [dec][dec] |
The RP and LC have different downstream service-flows for the same SFID. The problem should resolve by itself. If it persists report to your technical support representative |
ubr10k-sw |
LOG_STD_ACTION |
|
UBR10K-6-DSD_SRV_FLOW_ERROR |
6-Information |
SFID found: SFID [dec] type [dec] MAC [enet][enet] prim_sid [dec][dec] |
The RP and LC have different service-flows for the same SFID. The problem should resolve by itself. If it persists report to your technical support representative |
ubr10k-sw |
LOG_STD_ACTION |
|
UBR10K-6-HCCP_CM_INCONSISTENCY |
6-Information |
CM sync received [enet]msgp [enet] sid [dec] [dec] mac state [dec] hwidb [chars] |
Received sync message on secondary PRE for mismatched entry This problem should resolve by itself. If it persists report to your technical support representative |
ubr10k-sw |
LOG_STD_ACTION |
|
UBR10K-6-STATESYNC |
6-Information |
Redundancy state synchronization failure slot [dec]/[dec] - [chars] |
A failure occurred in trying to synchronize GE state information |
ubr10k-sw |
LOG_STD_RECUR_ACTION |
|
UBR10K-6-STDBY_CM_INCONSISTENCY |
6-Information |
CM sync received [enet]msgp [enet] sid [dec] [dec] mac state [dec] hwidb [chars] |
Received sync message on secondary PRE for mismatched entry This problem should resolve by itself. If it persists report to your technical support representative |
ubr10k-sw |
LOG_STD_ACTION |
|
UBR10K-6-US_SFID_INCONSISTENCY |
6-Information |
US-SF found: SFID [dec] type [dec] sid [dec][dec] MAC [enet][enet] prim_sid [dec][dec] |
The RP and LC have different upstream service-flows for the same SFID. The problem should resolve by itself. If it persists report to your technical support representative |
ubr10k-sw |
LOG_STD_ACTION |
|
UBR10KTCC-1-BADCLK |
1-Alert |
Cable Line Card [dec]/[dec] reports Bad Clock Status for [chars] card in [dec]/1 |
Error in the clock received on the BackPlane |
ubr10k-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative. " "Check output of 'show clc-clk-status' command" |
|
UBR10KTCC-1-LCLOSC |
1-Alert |
Cable Line Card [dec]/[dec] using the local oscillator |
Error in the clock received on the BackPlane |
ubr10k-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR10KTCC-1-NOTCC |
1-Alert |
No working TCC card available in the system |
There is no TCC card or there could be some failure in the MTSS of the TCC card and it is put under maintanence |
ubr10k-sw |
"Replace TCC card" |
|
UBR10KTCC-1-SWTCHERR |
1-Alert |
Unable to switch TCC card configuration. Other card is not present or in Maintenance |
Other card is not present or in Maintenance state |
ubr10k-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR10KTCC-2-BADTCC |
2-Critical |
TCC card in [dec]/1 put under maintenance due to: [chars] |
There could be some failure in the MTSS of the TCC card |
ubr10k-sw |
"Replace TCC card" |
|
UBR10KTCC-2-LOS |
2-Critical |
Loss of signal with clock reference TCC in [chars] card [dec]/[dec] |
The TCC card clock reference was lost |
ubr10k-sw |
"Check reference source" |
|
UBR10KTCC-3-BLKCMD |
3-Error |
Schooner System IPC failure for TCC card |
c10k_card_send_blocking_cmd failed |
ubr10k-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR10KTCC-3-DTIERR |
3-Error |
DTI interface Error code [dec] function [chars] |
Error return value on call of DTI component function |
ubr10k-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR10KTCC-3-EVNTLEN |
3-Error |
TCC card Event internal error [chars] [dec] [dec] |
Internal Event error in TCC card |
ubr10k-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR10KTCC-4-BADCLK_STANDBY_TCC |
4-Warning |
No available external clock reference on the standby DTCC card [dec]/[dec] |
The TCC card clock reference is lost or bad |
ubr10k-sw |
"Check reference source on the standby DTCC card" |
|
UBR10KTCC-4-DTCC_CLOCK_WARNING |
4-Warning |
Active DTCC in slot [dec]/[dec] doesn't have the latest firmware 0x[hec]. This may impact system behavior in selected clock mode\n |
Active DTCC doesn't have the latest firmware |
ubr10k-sw |
"If CMTS doesn't contain dual DTCC cards then the " "firmware will not be auto-upgraded. \n" "Do manual upgrade using 'cable clock update'" |
|
UBR10KTCC-4-DTCC_OLD_FW |
4-Warning |
DTCC slot [dec]/[dec] FPGA upgrade needed. Card is outdated and cannot be auto-upgraded. Main EPLD version is 0x[hec] minimum requirement is 0x[hec]\n |
The DTCC card has old firmware and cannot be upgraded |
ubr10k-sw |
"Replace TCC card" |
|
UBR10KTCC-4-DTCC_OLD_HW |
4-Warning |
DTCC slot [dec]/[dec] FPGA upgrade needed. Card is outdated and cannot be auto-upgraded. H/W revision is 0x[hec] minimum requirement is 0x[hec]\n |
The DTCC card has old hardware and cannot be upgraded |
ubr10k-sw |
"Replace TCC card" |
|
UBR10KTCC-4-OIRERR |
4-Warning |
TCC OIR state machine warning: attempt to restart working card\n |
OIR Start is called twice back-to-back |
ubr10k-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR10KTCC-5-ACTIVE_TCC |
5-Notice |
[chars] card [dec]/[dec] is active with [chars] as clock reference |
The TCC Card became active |
ubr10k-sw |
"Information only" |
|
UBR10KTCC-5-DTCC_UPGRADE |
5-Notice |
DTCC card in slot [dec]/[dec] will be upgraded from 0x[hec] to version 0x[hec]. PLEASE DO NOT INTERRUPT DURING THE UPGRADE PROCESS. Estimated upgrade time [dec] minutes.\n |
DTCC upgrade information |
ubr10k-sw |
"None" |
|
UBR10KTCC-5-DTISLOT |
5-Notice |
DTCC slot [dec]/[dec]: card role changed to [chars]\n |
Change in role of TCC slot |
ubr10k-sw |
"Check DTI link/cable" |
|
UBR10KTCC-6-CHG_CLK_REF |
6-Information |
Clock reference source set to [chars] for [chars] card [dec]/[dec] by process [chars] |
Three reasons for the change in clock reference. 1 LOS of previous source reference for TCCplus card |
ubr10k-sw |
"Check reference source TCCplus Information onlyDTCC" |
|
UBR10KTCC-6-DTIPORTCLIENT |
6-Information |
DTCC slot [dec]/[dec] port [dec] DTI client status changed to [chars] [chars]\n |
Change in client status of DTI port |
ubr10k-sw |
"Check DTI link/cable" |
|
UBR10KTCC-6-DTIPORTPHYS |
6-Information |
DTCC slot [dec]/[dec] port [dec] DTI physical status changed: Link status:[chars] frame error rate: [chars]\n |
Change in frame error rate or link status of DTI link |
ubr10k-sw |
"Check DTI link/cable" |
|
UBR10KTCC-6-DTIPORTSERVER |
6-Information |
DTCC slot [dec]/[dec] port [dec] DTI server status changed to [chars] external clock source: [chars]\n |
Change in server status of DTI port |
ubr10k-sw |
"Check DTI link/cable" |
|
UBR7200-0-CPUCARD |
0-Emergency |
CMTS[dec]/[dec] Init failed CSR[dec]=0x%04x. |
Most likely Hardware failure |
ubr7200 |
"Replace defective Line Card" |
|
UBR7200-0-CPUCARD |
0-Emergency |
CMTS[dec]/[dec] Init failed CSR[dec]=0x%04x. |
Most likely Hardware failure |
ubr7200 |
"Replace defective Line Card" |
|
UBR7200-0-LOWPOWERCPU |
0-Emergency |
uBR requires CPU card type NPE150 or higher |
NPE100 is not supported in uBR |
ubr7200 |
"Upgrade CPU card to NPE150 or higher" |
|
UBR7200-0-TEMPHIGH |
0-Emergency |
[chars] measured at [chars] is too high: shutdown temperature [chars] |
Current temperature exceeds the max shutdown temperature |
ubr7200 |
"Determine cause of the high temperature and correct if possible." |
|
UBR7200-0-TEMPHIGH |
0-Emergency |
[chars] measured at [chars] is too high: shutdown temperature [chars] |
Current temperature exceeds the max shutdown temperature |
ubr7200 |
"Determine cause of the high temperature and correct if possible." |
|
UBR7200-0-TEST_CABLE |
0-Emergency |
CMTS[dec]/[dec]/[dec] schrp_cli_cmd function failed in [chars] |
Most likely S/W failure |
ubr7200-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR7200-0-VOLTHIGH |
0-Emergency |
[chars] measured at [chars] is too high: shutdown voltage [chars] |
Current voltage exceeds the max shutdown voltage |
ubr7200 |
"Determine cause of the high voltage and correct if possible." |
|
UBR7200-0-VOLTHIGH |
0-Emergency |
[chars] measured at [chars] is too high: shutdown voltage [chars] |
Current voltage exceeds the max shutdown voltage |
ubr7200 |
"Determine cause of the high voltage and correct if possible." |
|
UBR7200-0-VOLTLOW |
0-Emergency |
[chars] measured at [chars] is too low: shutdown voltage [chars] |
Current voltage exceeds the min shutdown voltage |
ubr7200 |
"Determine cause of the low voltage and correct if possible." |
|
UBR7200-0-VOLTLOW |
0-Emergency |
[chars] measured at [chars] is too low: shutdown voltage [chars] |
Current voltage exceeds the min shutdown voltage |
ubr7200 |
"Determine cause of the low voltage and correct if possible." |
|
UBR7200-1-DISCOVER |
1-Alert |
Only found [dec] interfaces on bay [dec] shutting down bay |
Most likely system or hardware failure |
ubr7200 |
"Replace Line Card" |
|
UBR7200-1-DISCOVER |
1-Alert |
Only found [dec] interfaces on bay [dec] shutting down bay |
Most likely system or hardware failure |
ubr7200 |
"Replace Line Card" |
|
UBR7200-2-CMTS_INDEX_TABLE_FULL |
2-Critical |
[chars] Index table full - req [dec]/[dec]/[dec]:[dec] if_idx [dec] sid [dec] no-elem [dec] [[chars]]\n |
The specified Index table is full. This indicates a likely software defect in one of the applications that use this index. Please run show tech to collect additional debug information. |
ubr7200 |
"Please copy the error message exactly as it appears on the console or in the " "system log contact your technical support representativeand provide the " "representative with the gathered information. " |
|
UBR7200-2-CPE_MGMT_IDX_ERR |
2-Critical |
Index out of range during CPE MGMT data decoding |
\nThe index is out of range during CPE MGMT HCCP data decoding. |
ubr7200 |
"Contact Cisco with this log message" |
|
UBR7200-2-CPE_MGMT_IDX_ERR |
2-Critical |
Index out of range during CPE MGMT data decoding |
\nThe index is out of range during CPE MGMT HCCP data decoding. |
ubr7200 |
"Contact Cisco with this log message" |
|
UBR7200-2-LOG_CON_SYS_CRIT |
2-Critical |
[chars] logging console level to [dec] from [dec] Rate-limit level [dec] [chars]. |
Logging console restricted during critical situations |
ubr7200 |
"Please run 'show logging' to view all sys-logged messages" |
|
UBR7200-2-LOG_CON_SYS_CRIT |
2-Critical |
[chars] logging console level to [dec] from [dec] Rate-limit level [dec] [chars]. |
Logging console restricted during critical situations |
ubr7200 |
"Please run 'show logging' to view all sys-logged messages" |
|
UBR7200-2-NOMEMORY |
2-Critical |
Failure to create new IPv6 entry %P |
Unable to malloc a buffer to create a new entry to add Ipv6 addr |
cmts-platform |
"Enter a show chunks command and report the output along with this " "error message to your technical support representative." |
|
UBR7200-2-NOMEMORY |
2-Critical |
Failure to create new IPv6 entry %P |
Unable to malloc a buffer to create a new entry to add Ipv6 addr |
cmts-platform |
"Enter a show chunks command and report the output along with this " "error message to your technical support representative." |
|
UBR7200-2-NULL_SRC_ERR |
2-Critical |
HCCP Copy IPv6 addresses has NULL source |
\nHCCP IPv6 copy function has been sent NULL src address list. |
ubr7200 |
"Contact Cisco with this log message" |
|
UBR7200-3-ACFE_FAILURE |
3-Error |
[chars] |
A failure occurred in ACFE algoirhtm module |
cmts-qos |
LOG_STD_ACTION |
|
UBR7200-3-ACFE_FAILURE |
3-Error |
[chars] |
A failure occurred in ACFE algoirhtm module |
cmts-qos |
LOG_STD_ACTION |
|
UBR7200-3-ALARM_ERROR |
3-Error |
[chars] |
General error information. |
ubr7200 |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR7200-3-ALARM_ERROR |
3-Error |
[chars] |
General error information. |
ubr7200 |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR7200-3-AUTH_INVALID_INVALID_KEY_SEQUENCE_NUMBER |
3-Error |
<132>CMTS[DOCSIS]:<66030206> Auth Invalid - Invalid Key Sequence Number. CM Mac Addr <[enet]> |
Auth Invalid-Invalid Key Sequence Number\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-AUTH_INVALID_INVALID_KEY_SEQUENCE_NUMBER |
3-Error |
<132>CMTS[DOCSIS]:<66030206> Auth Invalid - Invalid Key Sequence Number. CM Mac Addr <[enet]> |
Auth Invalid-Invalid Key Sequence Number\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-AUTH_INVALID_MESSAGE_AUTHENTICATION_FAILURE |
3-Error |
<132>CMTS[DOCSIS]:<66030207> Auth Invalid - MessageKey Request Authentication Failure . CM Mac Addr <[enet]> |
Auth Invalid Message Authentication Failure\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-AUTH_INVALID_MESSAGE_AUTHENTICATION_FAILURE |
3-Error |
<132>CMTS[DOCSIS]:<66030207> Auth Invalid - MessageKey Request Authentication Failure . CM Mac Addr <[enet]> |
Auth Invalid Message Authentication Failure\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-AUTH_INVALID_NO_INFORMATION |
3-Error |
<132>CMTS[DOCSIS]:<66030202> Auth Invalid - No Information. CM Mac Addr <[enet]> |
Auth Invalid No Information\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-AUTH_INVALID_NO_INFORMATION |
3-Error |
<132>CMTS[DOCSIS]:<66030202> Auth Invalid - No Information. CM Mac Addr <[enet]> |
Auth Invalid No Information\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-AUTH_INVALID_UNAUTHORIZED_CM |
3-Error |
<132>CMTS[DOCSIS]:<66030203> Auth Invalid - Unauthorized CM. CM Mac Addr <[enet]> |
Auth Invalid Unauthorized CM\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-AUTH_INVALID_UNAUTHORIZED_CM |
3-Error |
<132>CMTS[DOCSIS]:<66030203> Auth Invalid - Unauthorized CM. CM Mac Addr <[enet]> |
Auth Invalid Unauthorized CM\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-AUTH_INVALID_UNSOLICITED |
3-Error |
<132>CMTS[DOCSIS]:<66030205> Auth Invalid - Unsolicited. CM Mac Addr <[enet]> |
Auth Invalid Unsolicited\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-AUTH_INVALID_UNSOLICITED |
3-Error |
<132>CMTS[DOCSIS]:<66030205> Auth Invalid - Unsolicited. CM Mac Addr <[enet]> |
Auth Invalid Unsolicited\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-AUTH_REJECT_NO_INFORMATION |
3-Error |
<132>CMTS[DOCSIS]:<66030102> Auth Reject - No Information . CM Mac Addr <[enet]> |
Auth Reject No Information\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-AUTH_REJECT_NO_INFORMATION |
3-Error |
<132>CMTS[DOCSIS]:<66030102> Auth Reject - No Information . CM Mac Addr <[enet]> |
Auth Reject No Information\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-AUTH_REJECT_PERMANENT_AUTHORIZATION_FAILURE |
3-Error |
<132>CMTS[DOCSIS]:<66030108> Auth Reject - Permanent Authorization Failure . CM Mac Addr <[enet]> |
Auth Reject Permanent Authorization Failure\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-AUTH_REJECT_PERMANENT_AUTHORIZATION_FAILURE |
3-Error |
<132>CMTS[DOCSIS]:<66030108> Auth Reject - Permanent Authorization Failure . CM Mac Addr <[enet]> |
Auth Reject Permanent Authorization Failure\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-AUTH_REJECT_TOD_NOT_ACQUIRED |
3-Error |
<132>CMTS[DOCSIS]:<66030109> Auth Reject - Time of Day not acquired . CM Mac Addr <[enet]> |
CM Auth Rejected. TOD not acquired. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-AUTH_REJECT_TOD_NOT_ACQUIRED |
3-Error |
<132>CMTS[DOCSIS]:<66030109> Auth Reject - Time of Day not acquired . CM Mac Addr <[enet]> |
CM Auth Rejected. TOD not acquired. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-AUTH_REJECT_UNAUTHORIZED_CM |
3-Error |
<132>CMTS[DOCSIS]:<66030103> Auth Reject - Unauthorized CM . CM Mac Addr <[enet]> |
Auth Reject Unauthorized CM\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-AUTH_REJECT_UNAUTHORIZED_CM |
3-Error |
<132>CMTS[DOCSIS]:<66030103> Auth Reject - Unauthorized CM . CM Mac Addr <[enet]> |
Auth Reject Unauthorized CM\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-AUTH_REJECT_UNAUTHORIZED_SAID |
3-Error |
<132>CMTS[DOCSIS]:<66030104> Auth Reject - Unauthorized SAID. CM Mac Addr <[enet]> |
Auth Reject Unauthorized SAID\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-AUTH_REJECT_UNAUTHORIZED_SAID |
3-Error |
<132>CMTS[DOCSIS]:<66030104> Auth Reject - Unauthorized SAID. CM Mac Addr <[enet]> |
Auth Reject Unauthorized SAID\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-BADARPDELETE |
3-Error |
Tried to remove arp entry for [inet] that is not dynamic |
Tried to delete non-dynamic arp entry - possible spoof attempt |
ubr7200 |
"Look for possible CMTS IP address spoofing attempt" |
|
UBR7200-3-BADARPDELETE |
3-Error |
Tried to remove arp entry for [inet] that is not dynamic |
Tried to delete non-dynamic arp entry - possible spoof attempt |
ubr7200 |
"Look for possible CMTS IP address spoofing attempt" |
|
UBR7200-3-BADARPREPLY |
3-Error |
Interface [chars] ARP reply from invalid source. Expected SID=[dec] Actual SID=[dec] |
There might be a spoofing attempt going on |
ubr7200 |
"Look for possible spoofing attempt" |
|
UBR7200-3-BADARPREQUEST |
3-Error |
Interface [chars] ARP request from invalid source on [chars]. IP=[inet] MAC=[enet]\n Expected SID=[dec] Actual SID=[dec] |
This is a proxyed ARP reply or a spoofing attempt received on the CMTS upstream. |
ubr7200 |
"Look for possible proxyed ARP reply or spoofing attempt" |
|
UBR7200-3-BADFFTINTERRUPT |
3-Error |
BCM3138 chip [dec] dma interrupt error. |
FFT dma interrupt error occured. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-BADFFTINTERRUPT |
3-Error |
BCM3138 chip [dec] dma interrupt error. |
FFT dma interrupt error occured. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-BADFFTSTATE |
3-Error |
BCM3138 chip [dec] is in wrong state [dec] expected state [dec] |
Impossible state has been reached. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-BADFFTSTATE |
3-Error |
BCM3138 chip [dec] is in wrong state [dec] expected state [dec] |
Impossible state has been reached. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-BADUSPORT |
3-Error |
Interface [chars] U[dec] invalid highest port number is U[dec] |
Upstream port number must be valid. |
ubr7200 |
"Redo command with valid upstream port number." |
|
UBR7200-3-BADUSPORT |
3-Error |
Interface [chars] U[dec] invalid highest port number is U[dec] |
Upstream port number must be valid. |
ubr7200 |
"Redo command with valid upstream port number." |
|
UBR7200-3-BPI_ENFORCE |
3-Error |
Blocking CPE=[enet] CM=[enet] sid [dec] interface [chars]: CPE blocked |
CMTS glean function received blocked cpe mac addr |
ubr7200 |
"Check for bpi-plus-policy: CPE blocked mac addr" |
|
UBR7200-3-BPI_ERR |
3-Error |
[chars] [dec] [dec] [dec] |
BPI Error \n |
ubr10000 |
LOG_STD_NO_ACTION |
|
UBR7200-3-BPI_ERR_DOCSIS |
3-Error |
[chars] [enet] [dec] [dec] |
BPI DMP Error \n |
ubr7200 |
"Check BPI DMP Module" |
|
UBR7200-3-BPI_ERR_UMP |
3-Error |
[chars] [enet] [dec] [dec] |
BPI UMP Error \n |
ubr7200 |
"Check BPI UMP Module" |
|
UBR7200-3-BPI_UNINITIALIZED |
3-Error |
<133>CMTS[DOCSIS]:<0> BPI has not yet initialized |
The root certificates and crypto library is being initialized. CM Mac Addr <[enet]>\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-BRIDGE_DELETE |
3-Error |
Interface [chars] error in deleting address [dec] from host tables |
An internal software error occurred during CMTS tables management |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-BUN_MCAST_INIT |
3-Error |
Unable to allocate memory for bundle multicast initialization. |
An internal software error occured |
ubr7200-sw |
"Copy the error message exactly as it appears and report it to your " "technical support respresentative." |
|
UBR7200-3-BUN_MCAST_INIT |
3-Error |
Unable to allocate memory for bundle multicast initialization. |
An internal software error occured |
cbr-application |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-BUN_MCAST_NOFREE_MAC |
3-Error |
Fail to allocate free Bundle Multicast Map Entry for Bundle:[dec] Group:[inet] Source:[inet] IDB:[chars] |
An internal software error occured |
ubr7200-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR7200-3-BUN_MCAST_NOFREE_MAC |
3-Error |
Fail to allocate free Bundle Multicast Map Entry for Bundle:[dec] Group:[inet] Source:[inet] IDB:[chars] |
An internal software error occured |
cbr-application |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-BUN_MCAST_REV_MAP_ERR |
3-Error |
Unable to find the Multicast Mapped Entry from reverse-mapping table for Bundle: [dec] MAC:[enet] |
An internal software error occured |
ubr7200-sw |
"Copy the error message exactly as it appears and report it to your " "technical support respresentative." |
|
UBR7200-3-BUN_MCAST_REV_MAP_ERR |
3-Error |
Unable to find the Multicast Mapped Entry from reverse-mapping table for Bundle: [dec] MAC:[enet] |
An internal software error occured |
cbr-application |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-CHASSIS |
3-Error |
Unknown chassis model. |
Data stored in midplane is bad or incomplete. |
ubr7200 |
"Contact technical support to update your system." |
|
UBR7200-3-CHASSIS |
3-Error |
Unknown chassis model. |
Data stored in midplane is bad or incomplete. |
ubr7200 |
"Contact technical support to update your system." |
|
UBR7200-3-CM_CERTIFICATE_ERROR |
3-Error |
<132>CMTS[DOCSIS]:<66030111> CM Certificate Error. CM Mac Addr <[enet]> |
CM Certificate error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-CM_CERTIFICATE_ERROR |
3-Error |
<132>CMTS[DOCSIS]:<66030111> CM Certificate Error. CM Mac Addr <[enet]> |
CM Certificate error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-CM_CERTIFICATE_FORMAT_ERROR |
3-Error |
<133>CMTS[DOCSIS]: CM Certificate Format Error |
CM Certificate Format Error \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-CM_CERTIFICATE_FORMAT_ERROR |
3-Error |
<133>CMTS[DOCSIS]: CM Certificate Format Error |
CM Certificate Format Error \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-CM_CERTIFICATE_SELF_VERFICATION_ERROR |
3-Error |
<133>CMTS[DOCSIS]:<0> CM Certificate Self-Verfication Error |
CM Certificate Self-Verfication Error \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-CM_CERTIFICATE_SELF_VERFICATION_ERROR |
3-Error |
<133>CMTS[DOCSIS]:<0> CM Certificate Self-Verfication Error |
CM Certificate Self-Verfication Error \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-CMTS_QUACK_FAIL_ERR |
3-Error |
[chars] |
This LC requires programmed Quack IDPROM. |
ubr10000 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-CMTS_QUACK_FAIL_ERR |
3-Error |
[chars] |
This LC requires programmed Quack IDPROM. |
ubr10000 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-CMTS_RCC_CREATION_FAILURE |
3-Error |
RCC creation failure - ID [dec] owner [chars] host [chars] |
RCC creation failed due to list insert failure. |
cmts-docsis |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-CMTS_RCC_CREATION_FAILURE |
3-Error |
RCC creation failure - ID [dec] host [chars] |
RCC creation failed due to list insert failure. |
cmts-docsis |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-CMTS_TCC_RNG_INVALID_SB |
3-Error |
TCC RNG on Interface [chars] with invalid SB for CM [enet] |
TCC RNG could not get a valid subblock for the interface that the CM is ranged on. SW Bug. |
ubr10000 |
LOG_STD_NO_ACTION |
|
UBR7200-3-CMTS_TCC_RNG_INVALID_SB |
3-Error |
TCC RNG on Interface [chars] with invalid SB for CM [enet] |
TCC RNG could not get a valid subblock for the interface that the CM is ranged on. SW Bug. |
ubr10000 |
LOG_STD_NO_ACTION |
|
UBR7200-3-CNNR_INVALID |
3-Error |
Connector [dec] and receiver [dec] are not on the same device |
The software tries to map an upstream connector on one device to a phy receiver on another device. If this happens in normal operation not through test command it is most likely a |
ubr7200 |
LOG_STD_ACTION |
|
UBR7200-3-CONFIG |
3-Error |
Exceeds [dec] [chars] |
The total bandwidth of fast and medium bandwidth port adapters exceed the rated capacity of this system. |
ubr7200 |
"Refer to the configuration guidelines for the maximum allowed " "high and medium bandwidth port adapters for the system." |
|
UBR7200-3-CONFIG |
3-Error |
Exceeds [dec] [chars] |
The total bandwidth of fast and medium bandwidth port adapters exceed the rated capacity of this system. |
ubr7200 |
"Refer to the configuration guidelines for the maximum allowed " "high and medium bandwidth port adapters for the system." |
|
UBR7200-3-DBDSPDEAD |
3-Error |
AWACS Slot [dec] is dead |
Daughter board DSP hungs |
ubr7200 |
"Reload image if still fail replace defective daughter board" |
|
UBR7200-3-DBDSPDEAD |
3-Error |
AWACS Slot [dec] is dead |
Daughter board DSP hungs |
ubr7200 |
"Reload image if still fail replace defective daughter board" |
|
UBR7200-3-DBDSPDOWNLOADERR1 |
3-Error |
DSP FAILED TO RESPOND TO INIT_DOWNLOAD CMD. |
Failed initiating DSP downloading |
ubr7200 |
"Reload image if still fail replace defective daughter board" |
|
UBR7200-3-DBDSPDOWNLOADERR1 |
3-Error |
DSP FAILED TO RESPOND TO INIT_DOWNLOAD CMD. |
Failed initiating DSP downloading |
ubr7200 |
"Reload image if still fail replace defective daughter board" |
|
UBR7200-3-DBDSPDOWNLOADERR2 |
3-Error |
Failed downloading. |
Failed DSP downloading |
ubr7200 |
"Reload image if still fail replace defective daughter board" |
|
UBR7200-3-DBDSPDOWNLOADERR2 |
3-Error |
Failed downloading. |
Failed DSP downloading |
ubr7200 |
"Reload image if still fail replace defective daughter board" |
|
UBR7200-3-DBDSPDOWNLOADERR3 |
3-Error |
FAILED DOWNLOADING OF DSP FW DUE TO CHECKSUM FAILURE. |
Failed last step of DSP downloading |
ubr7200 |
"Reload image if still fail replace defective daughter board" |
|
UBR7200-3-DBDSPDOWNLOADERR3 |
3-Error |
FAILED DOWNLOADING OF DSP FW DUE TO CHECKSUM FAILURE. |
Failed last step of DSP downloading |
ubr7200 |
"Reload image if still fail replace defective daughter board" |
|
UBR7200-3-DBDSPDOWNLOADPASS1 |
3-Error |
INIT DOWNLOAD OF DSP F/W PASS. |
The DSP firmware download initiation was successful |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-DBDSPDOWNLOADPASS1 |
3-Error |
INIT DOWNLOAD OF DSP F/W PASS. |
The DSP firmware download initiation was successful |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-DBDSPDOWNLOADPASS2 |
3-Error |
DOWNLOAD OF DSP F/W SUCCESS. |
The DSP firmware download was successful |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-DBDSPDOWNLOADPASS2 |
3-Error |
DOWNLOAD OF DSP F/W SUCCESS. |
The DSP firmware download was successful |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-DBDSPDOWNLOADPASS3 |
3-Error |
END DOWNLOAD OF DSP F/W SUCCESS. |
The DSP firmware end download was successful |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-DBDSPDOWNLOADPASS3 |
3-Error |
END DOWNLOAD OF DSP F/W SUCCESS. |
The DSP firmware end download was successful |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-DBDSPERR1 |
3-Error |
DSP SRAM failed |
Daughter board hardware failure |
ubr7200 |
"Replace defective daughter board" |
|
UBR7200-3-DBDSPERR1 |
3-Error |
DSP SRAM failed |
Daughter board hardware failure |
ubr7200 |
"Replace defective daughter board" |
|
UBR7200-3-DBDSPERR2 |
3-Error |
DSP SRAM semaphore failed |
Daughter board hardware failure |
ubr7200 |
"Replace defective daughter board" |
|
UBR7200-3-DBDSPERR2 |
3-Error |
DSP SRAM semaphore failed |
Daughter board hardware failure |
ubr7200 |
"Replace defective daughter board" |
|
UBR7200-3-DBDSPERR3 |
3-Error |
DSP side dual-port SRAM failed |
Daughter board hardware failure |
ubr7200 |
"Replace defective daughter board" |
|
UBR7200-3-DBDSPERR3 |
3-Error |
DSP side dual-port SRAM failed |
Daughter board hardware failure |
ubr7200 |
"Replace defective daughter board" |
|
UBR7200-3-DBDSPERR4 |
3-Error |
DSP FLASH memory failed |
Daughter board hardware failure |
ubr7200 |
"Replace defective daughter board" |
|
UBR7200-3-DBDSPERR4 |
3-Error |
DSP FLASH memory failed |
Daughter board hardware failure |
ubr7200 |
"Replace defective daughter board" |
|
UBR7200-3-DBDSPERR5 |
3-Error |
DSP failed to respond to Host Handshake |
Daughter board hardware failure |
ubr7200 |
"Replace defective daughter board" |
|
UBR7200-3-DBDSPERR5 |
3-Error |
DSP failed to respond to Host Handshake |
Daughter board hardware failure |
ubr7200 |
"Replace defective daughter board" |
|
UBR7200-3-DBDSPERR6 |
3-Error |
Switching to backup dsp image failed |
Daughter board hardware failure |
ubr7200 |
"Replace defective daughter board" |
|
UBR7200-3-DBDSPERR6 |
3-Error |
Switching to backup dsp image failed |
Daughter board hardware failure |
ubr7200 |
"Replace defective daughter board" |
|
UBR7200-3-DBDSPERR7 |
3-Error |
Switching again to regular dsp image failed |
Daughter board regular image corruption failure |
ubr7200 |
"Replace with BACKUP image" |
|
UBR7200-3-DBDSPERR7 |
3-Error |
Switching again to regular dsp image failed |
Daughter board regular image corruption failure |
ubr7200 |
"Replace with BACKUP image" |
|
UBR7200-3-DBDSPIDERR |
3-Error |
DSP id read 0x[hec]expect 0x[hec] |
Daughter board hardware failure |
ubr7200 |
"Replace defective daughter board" |
|
UBR7200-3-DBDSPIDERR |
3-Error |
DSP id read 0x[hec]expect 0x[hec] |
Daughter board hardware failure |
ubr7200 |
"Replace defective daughter board" |
|
UBR7200-3-DBFPGADLERR |
3-Error |
[chars] |
XILINX FPGA download failure |
ubr7200 |
"Reload image if still fail replace defective line card" |
|
UBR7200-3-DBFPGADLERR |
3-Error |
[chars] |
XILINX FPGA download failure |
ubr7200 |
"Reload image if still fail replace defective line card" |
|
UBR7200-3-DBFPGAERR |
3-Error |
XILINX not up reset reg is 0x[hec] |
Daughter board hardware failure |
ubr7200 |
"Replace defective daughter board" |
|
UBR7200-3-DBFPGAERR |
3-Error |
XILINX not up reset reg is 0x[hec] |
Daughter board hardware failure |
ubr7200 |
"Replace defective daughter board" |
|
UBR7200-3-DBPLX9050ERR |
3-Error |
Plx9050 id read 0x[hec]expect 0x[hec] |
Daughter board hardware failure |
ubr7200 |
"Replace defective daughter board" |
|
UBR7200-3-DBPLX9050ERR |
3-Error |
Plx9050 id read 0x[hec]expect 0x[hec] |
Daughter board hardware failure |
ubr7200 |
"Replace defective daughter board" |
|
UBR7200-3-DBPLX9080ERR |
3-Error |
Plx9080 id read 0x[hec]expect 0x[hec] |
Daughter board hardware failure |
ubr7200 |
"Replace defective daughter board" |
|
UBR7200-3-DBPLX9080ERR |
3-Error |
Plx9080 id read 0x[hec]expect 0x[hec] |
Daughter board hardware failure |
ubr7200 |
"Replace defective daughter board" |
|
UBR7200-3-DDC_INVALID_HASHTYPE |
3-Error |
The hash type [dec] for hash id [dec] is invalid |
Software does not recognize the configured hash type |
ddc |
"Copy the error message exactly as it appears " "and report it to your technical services representative" |
|
UBR7200-3-DDC_INVALID_HASHTYPE |
3-Error |
The hash type [dec] for hash id [dec] is invalid |
Software does not recognize the configured hash type |
ddc |
"Copy the error message exactly as it appears " "and report it to your technical services representative" |
|
UBR7200-3-DDC_INVALID_STATICMAP |
3-Error |
The node [dec] for mac-address [enet] exceeds maximum configured nodes |
A mapping specified by the oui-map or mac-map commands exceeds the configured number of participant nodes |
ddc |
"Fix configuration" |
|
UBR7200-3-DDC_INVALID_STATICMAP |
3-Error |
The node [dec] for mac-address [enet] exceeds maximum configured nodes |
A mapping specified by the oui-map or mac-map commands exceeds the configured number of participant nodes |
ddc |
"Fix configuration" |
|
UBR7200-3-DDC_UNEXPECTED_NODES |
3-Error |
The number of nodes [dec] is invalid |
The number of nodes is either smaller or greater than the limits supported by the platform |
ddc |
"Copy the error message exactly as it appears " "and report it to your technical services representative" |
|
UBR7200-3-DDC_UNEXPECTED_NODES |
3-Error |
The number of nodes [dec] is invalid |
The number of nodes is either smaller or greater than the limits supported by the platform |
ddc |
"Copy the error message exactly as it appears " "and report it to your technical services representative" |
|
UBR7200-3-DHCP_IP_ASSIGN_ERROR |
3-Error |
IP address [inet] for the host [enet] is already assigned to CM [enet]. |
There might be DHCP server configuration error. |
ubr7200 |
"Check DHCP server configuration" |
|
UBR7200-3-DISCOVER_FAIL |
3-Error |
[chars] |
Unable to discover physical entity |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-DISCOVER_FAIL |
3-Error |
[chars] |
Unable to discover physical entity |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-DIV_BY_ZERO_ERROR |
3-Error |
Divide by zero attempted error [chars] |
An internal software error occurred. |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-DIV_BY_ZERO_ERROR |
3-Error |
Divide by zero attempted error [chars] |
An internal software error occurred. |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-DMIC_FAIL |
3-Error |
Dynamic secrete failure CM [enet] on [chars] is [chars]. |
Dynamic secrete failed corresponding CM is rejected/marked/locked. |
cmts-docsis |
LOG_STD_NO_ACTION |
|
UBR7200-3-DOCSIS_SYNC_SF |
3-Error |
cminstp is NULL: [chars]. |
No valid cminstp is found for sid referenced in this checkpoint msg message will be dropped |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-DOCSIS_SYNC_SF |
3-Error |
cminstp is NULL: [chars]. |
No valid cminstp is found for sid referenced in this checkpoint msg message will be dropped |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-DS_FLOW_INCONSIST_WB_INFO |
3-Error |
DS Flow Error: [chars] [enet] prim_rfid [dec] sfid [dec] wb_mode [dec] forw_chid [dec] [chars] |
- |
- |
- |
|
UBR7200-3-DS_FLOW_INCONSIST_WB_INFO |
3-Error |
DS Flow Error: [chars] [enet] prim_rfid [dec] sfid [dec] wb_mode [dec] forw_chid [dec] [chars] |
An internal software error occurred. |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-DS_FLOW_INCONSIST_WB_INFO |
3-Error |
DS Flow Error: [chars] [enet] prim_rfid [dec] sfid [dec] wb_mode [dec] forw_chid [dec] [chars] |
- |
- |
- |
|
UBR7200-3-DS_FLOW_INCONSIST_WB_INFO |
3-Error |
DS Flow Error: [chars] [enet] prim_rfid [dec] sfid [dec] wb_mode [dec] forw_chid [dec] [chars] |
An internal software error occurred. |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-DSG_HBEAT_FAILED |
3-Error |
Interface [chars] failed to send hbeat packet for vendor [chars] |
An internal software error occurred. |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-DSX_DUP_TRANSC_SAME_ID |
3-Error |
[chars] Err: [enet] [dec] [chars]/[chars] [dec]/[dec] [dec]/[dec] |
Duplicated DSX transaction with the same ID. |
cbr-application |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-ENVM_FAN_OVERLOAD |
3-Error |
Fan Tray overloaded fail to support the linecard at slot [dec] |
The cooling power provided by the routers's fans is lower than \n\ some LCs in chassis required. |
- |
"Replace the fan as soon as possible or the system may shut itself \n\ down or fail to operate properly." |
|
UBR7200-3-ENVM_FAN_OVERLOAD |
3-Error |
Fan Tray overloaded fail to support the linecard at slot [dec] |
The cooling power provided by the routers's fans is lower than \n\ some LCs in chassis required. |
- |
"Replace the fan as soon as possible or the system may shut itself \n\ down or fail to operate properly." |
|
UBR7200-3-FLOW_ERR |
3-Error |
Flow error sfid [dec] sid [dec] CM Mac address <[enet]> |
An internal software error occurred. |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-FLOW_ERR |
3-Error |
Flow error sfid [dec] sid [dec] CM Mac address <[enet]> |
An internal software error occurred. |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-FPSUBINIT |
3-Error |
Unable to create subinterface [chars] for hw interface [chars] |
The system was unable to create the cable subinterface data structures |
ubr7200 |
"Gather information about running configuration and amount of memory " "in the system and file a bug" |
|
UBR7200-3-FPSUBINIT |
3-Error |
Unable to create subinterface [chars] for hw interface [chars] |
The system was unable to create the cable subinterface data structures |
ubr7200 |
"Gather information about running configuration and amount of memory " "in the system and file a bug" |
|
UBR7200-3-GRD_HCCP_RECOVER |
3-Error |
Wideband-Cable[dec]/[dec]/[dec]:[dec] not recovered after switchover |
After a switchover or revert where the modular-host for a SPA becomes active on the standby a wideband interface on that SPA is not recovered. This is most likely due to a software problem. |
cmts-redundancy |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-GRD_HCCP_RECOVER |
3-Error |
Wideband-Cable[dec]/[dec]/[dec]:[dec] not recovered after switchover |
After a switchover or revert where the modular-host for a SPA becomes active on the standby a wideband interface on that SPA is not recovered. This is most likely due to a software problem. |
cmts-redundancy |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-GRD_HCCP_REMOVE |
3-Error |
Wideband-Cable[dec]/[dec]/[dec]:[dec] not removed |
When the modular-host configuration for a SPA is removed a wideband interface on that SPA is not removed. This is most likely due to a software problem. |
cmts-redundancy |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-GRD_HCCP_REMOVE |
3-Error |
Wideband-Cable[dec]/[dec]/[dec]:[dec] not removed |
When the modular-host configuration for a SPA is removed a wideband interface on that SPA is not removed. This is most likely due to a software problem. |
cmts-redundancy |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-HOST_DB_CORRUPTED |
3-Error |
Host database corrupted under interface [chars] for MAC [enet] sid [dec] ip [inet]. |
CMTS host database corruption. |
ubr7200 |
"Contact Cisco TAC" |
|
UBR7200-3-HOTLISTMAC |
3-Error |
Investigating MAC=[enet] sid [dec] interface [chars]: MAC blocked |
CMTS glean function received blocked mac addr |
ubr7200 |
"Check for spoofing: CPE using blocked mac addr" |
|
UBR7200-3-HUNGFFTSTATE |
3-Error |
BCM3138 chip [dec] is not idle for [dec] retries |
BCM3138 FFT processor stuck |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-HUNGFFTSTATE |
3-Error |
BCM3138 chip [dec] is not idle for [dec] retries |
BCM3138 FFT processor stuck |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-I2CERR |
3-Error |
[chars] |
ERROR while accessing the i2c bus |
ubr7200 |
"Error has occured while accessing the internal bus." |
|
UBR7200-3-I2CERR |
3-Error |
[chars] |
ERROR while accessing the i2c bus |
ubr7200 |
"Error has occured while accessing the internal bus." |
|
UBR7200-3-I2CUPXERR |
3-Error |
[chars] |
ERROR while accessing the Upconverter |
ubr7200 |
"Error occured while accesing the upconverter." |
|
UBR7200-3-I2CUPXERR |
3-Error |
[chars] |
ERROR while accessing the Upconverter |
ubr7200 |
"Error occured while accesing the upconverter." |
|
UBR7200-3-IDB_MISMATCH |
3-Error |
DHCP IP Address Assign Mismatch MAC [enet] on [chars] assigned to [chars] with [inet] |
A DHCP server assignment error |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-INTERCEPT |
3-Error |
Interface [chars] Failed to send intercept packet to server [inet]:[dec] |
An internal software error occurred. |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-INTERCEPT |
3-Error |
Interface [chars] Failed to send intercept packet to server [inet]:[dec] |
An internal software error occurred. |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-INVALID_BP_CONFIGURATION_SETTING_VALUE |
3-Error |
<132>CMTS[DOCSIS]:<66010200> Invalid BP Configuration Setting Value for TLV type [dec]. CM MAC Addr <[enet]> |
Invalid BP Configuration Setting Value \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-INVALID_BP_CONFIGURATION_SETTING_VALUE |
3-Error |
<132>CMTS[DOCSIS]:<66010200> Invalid BP Configuration Setting Value for TLV type [dec]. CM MAC Addr <[enet]> |
Invalid BP Configuration Setting Value \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-INVALID_INVOKE_FROM_ISR |
3-Error |
Invalid [chars] from interrupt level [dec] |
Invalid operation from ISR context. Possible recurrence of CSCek63728 |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-INVALID_INVOKE_FROM_ISR |
3-Error |
Invalid [chars] from interrupt level [dec] |
Invalid operation from ISR context. Possible recurrence of CSCek63728 |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-INVALID_US_CHID |
3-Error |
Invalid Upstream Channel ID |
An internal software error occurred. |
cmts-docsis |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-INVALID_US_CHID |
3-Error |
Invalid Upstream Channel ID |
An internal software error occurred. |
cmts-docsis |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-INVALIDSID |
3-Error |
CR10K_REQ_API_DHCP_CLEAR: Invalid sid [dec] for mac address [enet] |
There might be an IPC problem |
ubr7200 |
"Look for possible spoofing attempt" |
|
UBR7200-3-IPCRECVERR |
3-Error |
Internal RP-CLC/CLC-CLC IPC receive error from [dec]/[dec] |
Internal IPC receive error\n |
ubr10000 |
LOG_STD_NO_ACTION |
|
UBR7200-3-IPDR_BUFFER_ERR |
3-Error |
unable to alloc buffer because percent of free memory is [dec] which is below [dec] |
The IPDR feature requires memory to hold record. Since insufficient memory it might result in lost IPDR data |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-IPDR_BUFFER_ERR |
3-Error |
unable to alloc buffer because percent of free memory is [dec] which is below [dec] |
The IPDR feature requires memory to hold record. Since insufficient memory it might result in lost IPDR data |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-IPDR_FILESYS_FULL |
3-Error |
File [chars] cannot be created/written since filesystem is full. |
The IPDR feature requires a file to be written to filesystem. Since filesystem is full it might result in lost IPDR data. |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-IPDR_FILESYS_FULL |
3-Error |
File [chars] cannot be created/written since filesystem is full. |
The IPDR feature requires a file to be written to filesystem. Since filesystem is full it might result in lost IPDR data. |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-IPDR_GET_MACDOMAIN_ERR |
3-Error |
[chars] |
The IPDR CM_US failed to get MAC domain by docsIf3CmtsCmRegStatusId. |
ubr10000 |
"Ignore this IPDR record collecting records at next interval." |
|
UBR7200-3-IPDR_GET_MACDOMAIN_ERR |
3-Error |
The IPDR CM-US failed to get MAC domain with slot[[dec]] subslot[[dec]] slotunit[[dec]]. |
The IPDR CM-US failed to get MAC domain by docsIf3CmtsCmRegStatusId. |
ubr7200 |
"Ignore this IPDR record collecting " "records at next interval." |
|
UBR7200-3-IPDR_SFLOG_FILE_ERR |
3-Error |
The IPDR failed to handle file: [chars] |
The IPDR failed to handle file |
ubr7200 |
"Check the file system " |
|
UBR7200-3-IPV4ADDRERR |
3-Error |
Host with invalid IPv4 address. Primary Interface [chars] Input Interface [chars] MAC = [enet] IP = [inet] |
Most likely a sw error of the packet sender |
ubr7200 |
"Check the modem and subscriber" |
|
UBR7200-3-IPV6ADDRERR |
3-Error |
Host with invalid IPv6 address. Primary Interface [chars] Input Interface [chars] MAC = [enet] IP = %P |
Most likely a sw error of the packet sender |
ubr7200 |
"Check the modem and subscriber" |
|
UBR7200-3-IPV6SOCKETFAIL |
3-Error |
IPv6 TFTP server socket |
Could not open the IPv6 TFTP server socket |
ubr7200 |
"Make sure the /"ip tftp-server /" CLI is not configured" |
|
UBR7200-3-IPV6SOCKETFAIL |
3-Error |
IPv6 TFTP server socket |
Could not open the IPv6 TFTP server socket |
ubr7200 |
"Make sure the /"ip tftp-server /" CLI is not configured" |
|
UBR7200-3-JIB_Q_LENGTH_PHS_ERR_DETECTED |
3-Error |
JIB Upstream Queue Length or PHS Rule Failure Detected. |
- |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-JIB_Q_LENGTH_PHS_ERR_DETECTED |
3-Error |
JIB Upstream Queue Length or PHS Rule Failure Detected. |
- |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-KEY_REJECT_NO_INFORMATION |
3-Error |
<132>CMTS[DOCSIS]:<66050102> Key Reject - No Information. CM Mac Addr <[enet]> |
Key Reject No Information\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-KEY_REJECT_NO_INFORMATION |
3-Error |
<132>CMTS[DOCSIS]:<66050102> Key Reject - No Information. CM Mac Addr <[enet]> |
Key Reject No Information\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-KEY_REJECT_UNAUTHORIZED_SAID |
3-Error |
<132>CMTS[DOCSIS]:<66050103> Key Reject - Unauthorized SAID. CM Mac Addr <[enet]> |
Key Reject Unauthorized SAID\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-KEY_REJECT_UNAUTHORIZED_SAID |
3-Error |
<132>CMTS[DOCSIS]:<66050103> Key Reject - Unauthorized SAID. CM Mac Addr <[enet]> |
Key Reject Unauthorized SAID\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-L2VPNMAXLIMIT |
3-Error |
L2VPN XCONNECT PW max limit of [dec] pseudo-wires reached. |
L2VPN XCONNECT PW max limit of pseudo-wires reached. |
cmts-application |
"Cannot configure anymore pseudo-wires" |
|
UBR7200-3-L2VPNMAXLIMIT |
3-Error |
L2VPN XCONNECT PW max limit of [dec] pseudo-wires reached. |
L2VPN XCONNECT PW max limit of pseudo-wires reached. |
cmts-application |
"Cannot configure anymore pseudo-wires" |
|
UBR7200-3-L2VPNNOTSUPPORTED |
3-Error |
L2 VPN ATM-VC mapping not currently supported on mc28u card. CM MAC [enet]. |
ATM-VC mapping configured for a cable modem on an mc28u card. |
TLS |
"Disable the L2 VPN ATM- VC mapping on mc28u cards." |
|
UBR7200-3-LB_IF_DISABLED |
3-Error |
Disabled interface [chars] |
Load balancing disabled the interface because it could not move modems from or to it. |
loadbalance |
"Check RF path for failure. " "Check if upstream and/or downstream channels are combined " "as expected" |
|
UBR7200-3-LB_IF_DISABLED |
3-Error |
Disabled interface [chars] |
Load balance disabled the interface because this could not move any modem in and out of it. |
cbr-application |
"Check if any modem can be online with this interface " "then check the path of RF channel " "and check if upstream and downstream channels are associated " "as expected in topology" |
|
UBR7200-3-LB_MODEM_FAILED |
3-Error |
Failed to move modem [enet] from [chars] to [chars]. |
Load balancing failed to move a modem from one interface to another. |
loadbalance |
"Check RF path for failure. " "Check if upstream and/or downstream channels are combined " "as expected" |
|
UBR7200-3-LB_MODEM_FAILED |
3-Error |
Failed to move modem [enet] from [chars] to [chars]. |
Load balance failed to move the modem from one interface to another. |
cbr-application |
"Check if any other modem can be online with this interface " "then check the path of RF channel " "and check if upstream and downstream channels are associated " "as expected in topology" |
|
UBR7200-3-LB_STALE_PENDING_CM |
3-Error |
This is a pre-exist pending entry print info to debug further... [enet] action 0x[hec]:0x[hec] client [dec]:[dec] src_upd_already [dec] |
Stale Pending CM Exist |
loadbalance |
"Contact Cisco TAC" |
|
UBR7200-3-LB_STALE_PENDING_CM |
3-Error |
This is a pre-exist pending entry detailed information as: [enet] action 0x[hec]:0x[hec] client [dec]:[dec] count update flag [dec] |
Stale pending CM exist |
cbr-application |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-MACADDRERR |
3-Error |
DHCP Msg with non unicast MAC address. Master Interface [chars] Input Interface [chars] SID = [dec] MAC = [enet] |
Most likely sw error |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-MACADDRERR |
3-Error |
Upstream packet from host with non unicast MAC address. Primary Interface [chars] Input Interface [chars] SID = [dec] MAC = [enet] |
Most likely a sw error of the packet sender |
ubr7200 |
"Check the modem and subscriber" |
|
UBR7200-3-MANUFACTURE_CA_CM_CERTIFICATE_FORMAT_ERROR |
3-Error |
<133>CMTS[DOCSIS]: CM MAC Addr <[enet]> on Interface [chars] U[dec] : [chars] |
Manufacture CA Certificate Format Error \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-MANUFACTURE_CA_CM_CERTIFICATE_FORMAT_ERROR |
3-Error |
<133>CMTS[DOCSIS]: CM MAC Addr <[enet]> on Interface [chars] U[dec] : [chars] |
Manufacture CA Certificate Format Error \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-MAP_REJECT_NOT_AUTH_DS_TRAFFIC |
3-Error |
<132>CMTS[DOCSIS]:<66060509> Map Reject - Not Authorized for requested downstream traffic flow. CM Mac Addr <[enet]> |
Map Reject - Not Authorized for requested downstream traffic flow \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-MAP_REJECT_NOT_AUTH_DS_TRAFFIC |
3-Error |
<132>CMTS[DOCSIS]:<66060509> Map Reject - Not Authorized for requested downstream traffic flow. CM Mac Addr <[enet]> |
Map Reject - Not Authorized for requested downstream traffic flow \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-MAPPED_TO_EXISTING_SAID |
3-Error |
<132>CMTS[DOCSIS]:<66060600> Mapped to existing SAID. CM Mac Addr <[enet]> |
Mapped to existing SAID\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-MAPPED_TO_EXISTING_SAID |
3-Error |
<132>CMTS[DOCSIS]:<66060600> Mapped to existing SAID. CM Mac Addr <[enet]> |
Mapped to existing SAID\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-MAPPED_TO_NEW_SAID |
3-Error |
<132>CMTS[DOCSIS]:<66060700> Mapped to new SAID. CM Mac Addr <[enet]> |
Mapped to new SAID \n |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-3-MAPPED_TO_NEW_SAID |
3-Error |
<132>CMTS[DOCSIS]:<66060700> Mapped to new SAID. CM Mac Addr <[enet]> |
Mapped to new SAID \n |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-3-MAX_DS_SF_ERROR |
3-Error |
Maximum limit for downstream service-flows reached |
The number of DS service-flows cannot exceed 50 |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-MAX_DS_SF_ERROR |
3-Error |
Maximum limit for downstream service-flows reached |
The number of DS service-flows cannot exceed 50 |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-MAX_DYN_DS_SF_ERROR |
3-Error |
Maximum limit for dynamic downstream service-flows reached |
The number of dynamic DS service-flows cannot exceed 31 |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-3-MCAST_DA_TO_DSID_DUPLICATED |
3-Error |
DA [enet] to DSID table duplicated when operation [chars] DSID [dec] on |
Multicast DA_TO_DSID table in LC should be unique for DA on a interface. |
ubr7200 |
"Reconfigure DSG configure in the mac domain" " to refesh all DSG configure in the interface." |
|
UBR7200-3-METERING_NOFILESYS_SFLOG |
3-Error |
No file system can be used for sflog file. |
Cannot found a suitable file system to store sflog file. |
ubr7200 |
"Please check whether disk0: or disk1:" " are ready or full." |
|
UBR7200-3-MIC_CALC_FAIL |
3-Error |
MIC calculation failed for CM [enet] on [chars]. |
MIC validation failed for given CM's registration data. |
cmts-docsis |
LOG_STD_NO_ACTION |
|
UBR7200-3-MISSING_BP_CONFIGURATION_SETTING_TLV |
3-Error |
<132>CMTS[DOCSIS]:<66010100> Missing BP Configuration Setting TLV. TLV Type <[enet]> |
Missing BP Configuration Setting TLV \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-MONITOR |
3-Error |
Interface [chars] Failed to send monitored packets |
An internal software error occurred. |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-MONITOR |
3-Error |
Interface [chars] Failed to send monitored packets |
An internal software error occurred. |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-MONITOR_ACCESS_FILTER |
3-Error |
Null access list |
An internal software error occurred. |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-MONITOR_ACCESS_FILTER |
3-Error |
Null access list |
An internal software error occurred. |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-MONITOR_EMPTY |
3-Error |
Unable to allocate packet with rx_type = [dec] |
An internal software error occurred. |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-MONITOR_EMPTY |
3-Error |
Unable to allocate packet with rx_type = [dec] |
An internal software error occurred. |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-NEG_PENDING |
3-Error |
NEGATIVE DECREMENT OF PENDING STATS on [chars] for [enet] |
An internal software error occurred. |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-NEG_PENDING |
3-Error |
Negative decrement of pending stats on [chars] for [enet] |
An internal software error occurred. |
cbr-application |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-NOFORK |
3-Error |
Could not start Spectrum Management process |
An internal software error occurred. |
ubr7200 |
"LOG_STD_SH_TECH_ACTION" |
|
UBR7200-3-NOFORK |
3-Error |
Could not start Spectrum Management process |
An internal software error occurred. |
ubr7200 |
"LOG_STD_SH_TECH_ACTION" |
|
UBR7200-3-NOMAC |
3-Error |
Can't allocate MAC address for interface [dec]/[dec] |
Your system is out of available MAC addresses. |
ubr7200 |
"Contact technical support." |
|
UBR7200-3-NOMAC |
3-Error |
Can't allocate MAC address for interface [dec]/[dec] |
Your system is out of available MAC addresses. |
ubr7200 |
"Contact technical support." |
|
UBR7200-3-NOMEM |
3-Error |
[chars] |
An internal software error occurred. |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-NOMEM |
3-Error |
[chars] |
An internal software error occurred. |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-NOMORESIDS |
3-Error |
Maximum number of SIDS have been allocated for interface [chars]: CM [enet]: SID container info: start [dec] end [dec] |
The Maxmium number of SIDS has reached |
ubr7200 |
"Assign Cable Modem to another Line Card" |
|
UBR7200-3-NOMORESIDS |
3-Error |
Maximum number of SIDS have been allocated for interface [chars]: CM [enet]: SID container info: start [dec] end [dec] |
The Maxmium number of SIDS has reached |
ubr7200 |
"Assign Cable Modem to another Line Card" |
|
UBR7200-3-NOTCMTS |
3-Error |
Device reported [hex] |
Most likely hardware failure |
ubr7200 |
"Replace defective hardware" |
|
UBR7200-3-NOTCMTS |
3-Error |
Device reported [hex] |
Most likely hardware failure |
ubr7200 |
"Replace defective hardware" |
|
UBR7200-3-NULLHWIDB |
3-Error |
A Null hwidb prevents the acl update for a modem's associated hosts MAC [enet] SID [dec] |
A failure occurred in trying to update acl for a modem's associated host |
ubr10000 |
"Copy the error message exactly as it appears and report it to your" "technical support representative." |
|
UBR7200-3-NULLHWIDB |
3-Error |
A Null hwidb prevents the acl update for a modem's associated hosts MAC [enet] SID [dec] |
A failure occurred in trying to update acl for a modem's associated host |
ubr10000 |
LOG_STD_NO_ACTION |
|
UBR7200-3-NULLIDBTTSVTBL |
3-Error |
A Null sw idb prevents pxf src-vfy tables from being updated MAC [enet] SID [dec] |
A failure occurred in trying to update pxf src-vfy tables |
ubr10000 |
"Copy the error message exactly as it appears and report it to your" "technical support representative." |
|
UBR7200-3-NULLIDBTTSVTBL |
3-Error |
A Null sw idb prevents pxf src-vfy tables from being updated MAC [enet] SID [dec] |
A failure occurred in trying to update pxf src-vfy tables |
ubr10000 |
"Copy the error message exactly as it appears and report it to your" "technical support representative." |
|
UBR7200-3-NULLMAPPTR |
3-Error |
Cannot send maps as current_map ptr is NULL\n ds->[hec]current_map->[hec]: [chars] |
This is an internal error or may indicate a memory problem. |
ubr7200 |
"Check your available memory. If necessary " "add more memory to the system." |
|
UBR7200-3-NULLMAPPTR |
3-Error |
Cannot send maps as current_map ptr is NULL\n ds->[hec]current_map->[hec]: [chars] |
This is an internal error or may indicate a memory problem. |
ubr7200 |
"Check your available memory. If necessary " "add more memory to the system." |
|
UBR7200-3-OFDMA_IUC_CHANGE_ERR |
3-Error |
OFDMA IUC change error: cm [enet] [chars] |
RPD DPIC TE interface and controller number mismatch. |
cbr-cmts-infra |
LOG_STD_ACTION |
|
UBR7200-3-OWNERR |
3-Error |
CMTS[dec]/[dec] Buffer ownership error pak=0x[hec]. |
Most likely hardware failure |
ubr7200 |
"Replace defective board" |
|
UBR7200-3-OWNERR |
3-Error |
CMTS[dec]/[dec] Buffer ownership error pak=0x[hec]. |
Most likely hardware failure |
ubr7200 |
"Replace defective board" |
|
UBR7200-3-PA_REM_ENQFAIL |
3-Error |
Enqueue of message failed slot [dec] |
Enqueue of a PA removal message to an event queue failed |
ubr7200 |
LOG_STD_ACTION |
|
UBR7200-3-PA_REM_ENQFAIL |
3-Error |
Enqueue of message failed slot [dec] |
Enqueue of a PA removal message to an event queue failed |
ubr7200 |
LOG_STD_ACTION |
|
UBR7200-3-PA_REM_GENERAL |
3-Error |
[chars] |
A general failure occured in the operation of the PA removal event state machine as defined by the failure string |
ubr7200 |
LOG_STD_ACTION |
|
UBR7200-3-PA_REM_GENERAL |
3-Error |
[chars] |
A general failure occured in the operation of the PA removal event state machine as defined by the failure string |
ubr7200 |
LOG_STD_ACTION |
|
UBR7200-3-PA_REM_PCI_ERROR |
3-Error |
PCI error address = 0x[hec]\n |
An unexpected PCI error happened |
ubr7200 |
LOG_STD_ACTION |
|
UBR7200-3-PA_REM_PCI_ERROR |
3-Error |
PCI error address = 0x[hec]\n |
An unexpected PCI error happened |
ubr7200 |
LOG_STD_ACTION |
|
UBR7200-3-PKTCBL_INVALID_GATE_ID |
3-Error |
if_index_db is null index = [dec] gid = [dec] |
PacketCable encounters invalid gate id to look up from its DB |
packetcable |
"SW code path errors" |
|
UBR7200-3-PKTCBL_INVALID_GATE_ID |
3-Error |
if_index_db is null index = [dec] gid = [dec] |
PacketCable encounters invalid gate id to look up from its DB |
packetcable |
"SW code path errors" |
|
UBR7200-3-REMOVE_OVERLAP_ENTRY |
3-Error |
\nREMOVE OVERLAP ENTRY:[chars] Found MAC:[enet] from:[chars] MAC:[enet] IP:[inet] IPv6:%P SID:[dec] found sid:[dec] ptr_sid:[dec] |
Remove stale entry overlap check error |
cmts |
"Check the bucket info of CM/CPE." "Copy the error message exactly as it appears" "and report it to your technical support representative." |
|
UBR7200-3-RP_INVALIDSID_ASSIGN |
3-Error |
Invalid SID assignment for interface: [chars] CM: [enet] |
Invalid SID assignment by RP |
ubr7200 |
"Contact Cisco TAC" |
|
UBR7200-3-RP_INVALIDSID_ASSIGN |
3-Error |
Invalid SID assignment for interface: [chars] CM: [enet] |
Invalid SID assignment by RP |
ubr7200 |
"Contact Cisco TAC" |
|
UBR7200-3-SA_MAP_UNSUPPORTED_CRYPTO_SUITE |
3-Error |
<132>CMTS[DOCSIS]:<66060200> Unsupported Crypto Suite. CM Mac Addr <[enet]> |
Unsupported Crypto Suite\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-SA_MAP_UNSUPPORTED_CRYPTO_SUITE |
3-Error |
<132>CMTS[DOCSIS]:<66060200> Unsupported Crypto Suite. CM Mac Addr <[enet]> |
Unsupported Crypto Suite\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-SEMCREATEFAIL |
3-Error |
Unable to create the semaphore |
Unable to create the semaphore for non-blocking UPX access |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-SEMCREATEFAIL |
3-Error |
Unable to create the semaphore |
Unable to create the semaphore for non-blocking UPX access |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-SEMLOCKFAIL |
3-Error |
Unable to lock the semaphore |
Unable to lock the semaphore for non-blocking UPX access |
ubr7200 |
"Unable to read the Upconverter status Try again" |
|
UBR7200-3-SEMLOCKFAIL |
3-Error |
Unable to lock the semaphore |
Unable to lock the semaphore for non-blocking UPX access |
ubr7200 |
"Unable to read the Upconverter status Try again" |
|
UBR7200-3-SIDERRORDCC |
3-Error |
Tried to allocate New SID %D during DCC CM rebuild for interface [chars]: CM [enet]: SID container info: start [dec] end [dec] |
Allocate SID during DCC CM rebuild |
ubr7200 |
"Assign Cable Modem to another interface" |
|
UBR7200-3-SIDERRORHCCP |
3-Error |
Tried to allocate New SID during Failover for interface [chars]: CM [enet]: SID container info: start [dec] end [dec] |
Allocate SID during Failover |
ubr7200 |
"Assign Cable Modem to another Line Card" |
|
UBR7200-3-SIDERRORHCCP |
3-Error |
Tried to allocate New SID during Failover for interface [chars]: CM [enet]: SID container info: start [dec] end [dec] |
Allocate SID during Failover |
ubr7200 |
"Assign Cable Modem to another Line Card" |
|
UBR7200-3-SLOTS |
3-Error |
Number of slots in chassis is undefined. |
Data stored in midplane is bad or incomplete. |
ubr7200 |
"Contact technical support to update your system." |
|
UBR7200-3-SLOTS |
3-Error |
Number of slots in chassis is undefined. |
Data stored in midplane is bad or incomplete. |
ubr7200 |
"Contact technical support to update your system." |
|
UBR7200-3-SNMPMALLOC |
3-Error |
no sufficient memory for sorted table index [dec] allocated %lu unallocated %lu |
There is no enough memory to allocate for AVL tree |
ubr7200 |
"No action needed." |
|
UBR7200-3-SNMPMALLOC |
3-Error |
no sufficient memory for sorted table index [dec] allocated %lu unallocated %lu |
There is no enough memory to allocate for AVL tree |
ubr7200 |
"No action needed." |
|
UBR7200-3-SPIERRNRD |
3-Error |
SPI PENDING NO READ DATA[chars]: spistat=0x%02x chid=0x%02x cmd=0x%02x |
Read error on PHY chip serial communications bus. |
ubr7200 |
"Line card is defective replace it." |
|
UBR7200-3-SPIERRNRD |
3-Error |
SPI PENDING NO READ DATA[chars]: spistat=0x%02x chid=0x%02x cmd=0x%02x |
Read error on PHY chip serial communications bus. |
ubr7200 |
"Line card is defective replace it." |
|
UBR7200-3-SPIERRR |
3-Error |
SPI PENDING READ ERROR[chars]: spistat=0x%02x chid=0x%02x cmd=0x%02x |
Read error on PHY chip serial communications bus. |
ubr7200 |
"Line card is defective replace it." |
|
UBR7200-3-SPIERRR |
3-Error |
SPI PENDING READ ERROR[chars]: spistat=0x%02x chid=0x%02x cmd=0x%02x |
Read error on PHY chip serial communications bus. |
ubr7200 |
"Line card is defective replace it." |
|
UBR7200-3-SPIERRRBS |
3-Error |
SPI BUS READ 0x%02x BYTES SHORT[chars]: spistat=0x%02x chid=0x%02x |
Read error on PHY chip serial communications bus. |
ubr7200 |
"Line card is defective replace it." |
|
UBR7200-3-SPIERRRBS |
3-Error |
SPI BUS READ 0x%02x BYTES SHORT[chars]: spistat=0x%02x chid=0x%02x |
Read error on PHY chip serial communications bus. |
ubr7200 |
"Line card is defective replace it." |
|
UBR7200-3-SPIERRW |
3-Error |
SPI PENDING WRITE ERROR[chars]: spistat=0x%02x chid=0x%02x cmd=0x%02x |
Write error on PHY chip serial communications bus. |
ubr7200 |
"Line card is defective replace it." |
|
UBR7200-3-SPIERRW |
3-Error |
SPI PENDING WRITE ERROR[chars]: spistat=0x%02x chid=0x%02x cmd=0x%02x |
Write error on PHY chip serial communications bus. |
ubr7200 |
"Line card is defective replace it." |
|
UBR7200-3-SPIERRW_CHID |
3-Error |
Invalid Channel ID[chars]: chid=0x%02x cmd=0x%02x regaddr=0x%02x |
An internal software error occurred. |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-SPIERRW_CHID |
3-Error |
Invalid Channel ID[chars]: chid=0x%02x cmd=0x%02x regaddr=0x%02x |
An internal software error occurred. |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-3-SPOOFEDIP |
3-Error |
Rejecting IP=[inet] [chars] sid [dec]: Address configured on [chars] |
CMTS glean function received overlapping ip address info |
ubr7200 |
"Check for spoofing: CPE may be using CMTS IP addr" |
|
UBR7200-3-SPOOFEDIP |
3-Error |
Rejecting IP=[inet] [chars] sid [dec]: Address configured on [chars] |
CMTS glean function received overlapping ip address info |
ubr7200 |
"Check for spoofing: CPE may be using CMTS IP addr" |
|
UBR7200-3-SPOOFEDMAC |
3-Error |
Investigating MAC=[enet] [chars] sid [dec]: Original MAC on sid [dec] [chars] |
CMTS glean function received overlapping mac address info |
ubr7200 |
"Check for spoofing: CPE may be reusing mac addr" |
|
UBR7200-3-SPOOFEDMAC |
3-Error |
Investigating MAC=[enet] [chars] sid [dec]: Original MAC on sid [dec] [chars] |
CMTS glean function received overlapping mac address info |
ubr7200 |
"Check for spoofing: CPE may be reusing mac addr" |
|
UBR7200-3-SUBDB_CPE_NO_CM |
3-Error |
CM doesn't exist when CPE is online on corresponding SID [chars] mac [enet] sid [dec] hwidb [chars] |
CM doesn't exist when CPE is online on corresponding SID |
ubr7200 |
"Contact TAC support and report the error message." |
|
UBR7200-3-SUBDB_FREE_IN_ISR |
3-Error |
Unexpected freeing Subscriber Data in interrupt context host_mac [enet] hwidb [chars] |
Unexpected freeing CMTS Subscriber DB data in interrupt context |
ubr7200 |
"Contact TAC support and report the error message." |
|
UBR7200-3-SUBDB_INIT_FAILURE |
3-Error |
CMTS Subscriber DB initialization failed [chars] [chars] [chars] |
CMTS Subscriber DB initialization failed |
ubr7200 |
"Contact TAC support and report the error message." |
|
UBR7200-3-TEK_INVALID_INVALID_KEY_SEQUENCE_NUMBER |
3-Error |
<132>CMTS[DOCSIS]:<66050206> TEK Invalid - Invalid Key Sequence Number . CM Mac Addr <[enet]> |
TEK Invalid - Invalid Key Sequence Number\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-TEK_INVALID_INVALID_KEY_SEQUENCE_NUMBER |
3-Error |
<132>CMTS[DOCSIS]:<66050206> TEK Invalid - Invalid Key Sequence Number . CM Mac Addr <[enet]> |
TEK Invalid - Invalid Key Sequence Number\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-TEK_INVALID_NO_INFORMATION |
3-Error |
<132>CMTS[DOCSIS]:<66050203> TEK Invalid - No Information. CM Mac Addr <[enet]> |
TEK Invalid No Information\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-TEK_INVALID_NO_INFORMATION |
3-Error |
<132>CMTS[DOCSIS]:<66050203> TEK Invalid - No Information. CM Mac Addr <[enet]> |
TEK Invalid No Information\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-TOOMANY_RANGEDSIDS |
3-Error |
CMTS-HCCP [chars]: Actual Rcvd ranged list sync sids [dec] # of sids saved [dec] |
Size of Ranged List Sync Message received. |
ubr7200 |
"Reduce the Number of Cable Modem Sids pre i/f" |
|
UBR7200-3-TOOMANY_RANGEDSIDS |
3-Error |
CMTS-HCCP [chars]: Actual Rcvd ranged list sync sids [dec] # of sids saved [dec] |
Size of Ranged List Sync Message received. |
ubr7200 |
"Reduce the Number of Cable Modem Sids pre i/f" |
|
UBR7200-3-UBRIPCRECVERR |
3-Error |
Internal RP-CLC/CLC-CLC IPC receive error from [dec]/[dec] |
Internal IPC receive error\n |
ubr10000 |
LOG_STD_NO_ACTION |
|
UBR7200-3-UBRIPCSENDERR |
3-Error |
Internal RP-CLC/CLC-CLC IPC send error from [dec]/[dec] |
Internal IPC send error\n |
ubr10000 |
LOG_STD_NO_ACTION |
|
UBR7200-3-UCDPROCERR |
3-Error |
CMTS UCD processing failed on [chars] U[dec] lch_state [dec] err [dec] retry [dec] |
UCD update error |
cmts-infra |
"Check the system CPU load and reset the upstream" |
|
UBR7200-3-UCDPROCERR |
3-Error |
CMTS UCD processing failed on [chars] U[dec] lch_state [dec] err [dec] retry [dec] |
UCD update error |
cmts-infra |
"Check the system CPU load and reset the upstream" |
|
UBR7200-3-UNASSIGNEDSID |
3-Error |
CR10K_REQ_API_DHCP_CLEAR: Unassigned sid [dec] for mac address [enet] sid found [dec] |
There might be an IPC problem |
ubr7200 |
"Look for possible spoofing attempt" |
|
UBR7200-3-UNEXPECTED |
3-Error |
[chars] |
The specified operation failed. |
- |
LOG_STD_NO_ACTION |
|
UBR7200-3-UNEXPECTED |
3-Error |
[chars] |
The specified operation failed. |
- |
LOG_STD_NO_ACTION |
|
UBR7200-3-UNSUPPORTED_CRYPTO_SUITE |
3-Error |
<132>CMTS[DOCSIS]:<66030300> Unsupported Crypto Suite. CM Mac Addr <[enet]> |
Unsupported Crypto Suite\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-UNSUPPORTED_CRYPTO_SUITE |
3-Error |
<132>CMTS[DOCSIS]:<66030300> Unsupported Crypto Suite. CM Mac Addr <[enet]> |
Unsupported Crypto Suite\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-WB_BPI_ERR |
3-Error |
[chars]: [dec] [dec] [dec] |
WB BPI Error \n |
ubr10000 |
LOG_STD_NO_ACTION |
|
UBR7200-3-WRONG3138CHIP |
3-Error |
BCM3138 current chip [dec] desired chip [dec] |
Wrong BCM3138 chip has been selected. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-WRONG3138CHIP |
3-Error |
BCM3138 current chip [dec] desired chip [dec] |
Wrong BCM3138 chip has been selected. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-3-ZEROIP_AND_MAC |
3-Error |
Error: Both IP & mac addr are zero sent to CMTS add entry routine: [chars] SID [dec]! |
IPC message seems to have been clobbered. |
ubr7200 |
"Contact Cisco with this log message" |
|
UBR7200-3-ZEROIPV6 |
3-Error |
Error: IPv6 addr is zero sent to CMTS add entry routine: [chars] SID [dec] [enet]! |
IPC message seems to have been clobbered. |
ubr7200 |
"Contact Cisco with this log message" |
|
UBR7200-3-ZEROMAC |
3-Error |
Error: Mac addr is zero sent to CMTS [chars]: [chars] IP [inet] SID [dec]! |
Miscreant client detected. |
ubr7200 |
"Contact Cisco with this log message" |
|
UBR7200-3-ZEROMAC_IPV6 |
3-Error |
Error: mac addr is zero sent to CMTS add entry routine: [chars] SID [dec] %P! |
IPC message seems to have been clobbered. |
ubr7200 |
"Contact Cisco with this log message" |
|
UBR7200-3-ZOMBIESID |
3-Error |
SID [dec] macaddr [enet] us_channel_id [dec] rng_list_id [dec] ds_time_stamp %llu rngpoll_timeout %llu now %lu last_ranging %lu stn_mtn=[dec] cont_mtn=[dec] pending=[dec]. |
SID instance didn't get cleanup after modem is gone. |
ubr7200 |
"Call TAC and show him/her the log." |
|
UBR7200-3-ZOMBIESID |
3-Error |
SID [dec] macaddr [enet] us_channel_id [dec] rng_list_id [dec] ds_time_stamp %llu rngpoll_timeout %llu now %lu last_ranging %lu stn_mtn=[dec] cont_mtn=[dec] pending=[dec]. |
SID instance didn't get cleanup after modem is gone. |
ubr7200 |
"Call TAC and show him/her the log." |
|
UBR7200-4-BAD_MAX_DOWNSTREAM_BITRATE_UNSUPPORTED_SETTING |
4-Warning |
<133>CMTS[DOCSIS]:<73011201> Bad Max DS Bit Rate Unsupported Setting. CM Mac Addr <[enet]> |
REG REQ : Bad Max DS Bit Rate Unsupported Setting.\n |
ubr7200 |
"Check the Config File Parameters" |
|
UBR7200-4-BAD_MAX_DOWNSTREAM_BITRATE_UNSUPPORTED_SETTING |
4-Warning |
<133>CMTS[DOCSIS]:<73011201> Bad Max DS Bit Rate Unsupported Setting. CM Mac Addr <[enet]> |
REG REQ : Bad Max DS Bit Rate Unsupported Setting.\n |
ubr7200 |
"Check the Config File Parameters" |
|
UBR7200-4-BAD_MAX_UPSTREAM_BITRATE_UNSUPPORTED_SETTING |
4-Warning |
<133>CMTS[DOCSIS]:<73011301> Bad Max US Bit Rate - Unsupported Setting. CM Mac Addr <[enet]> |
REG REQ : Bad Max US Bit Rate - Unsupported Setting.\n |
ubr7200 |
"Check the Config File Parameters" |
|
UBR7200-4-BAD_MAX_UPSTREAM_BITRATE_UNSUPPORTED_SETTING |
4-Warning |
<133>CMTS[DOCSIS]:<73011301> Bad Max US Bit Rate - Unsupported Setting. CM Mac Addr <[enet]> |
REG REQ : Bad Max US Bit Rate - Unsupported Setting.\n |
ubr7200 |
"Check the Config File Parameters" |
|
UBR7200-4-BAD_NETWORK_ACCESS_CONFIGURATION |
4-Warning |
<133>CMTS[DOCSIS]:<73010800> Network Access has Invalid Parameter. CM Mac Addr <[enet]> |
REG REQ : Network Access has Invalid Parameter.\n |
ubr7200 |
"Check the Config File Parameters" |
|
UBR7200-4-BAD_NETWORK_ACCESS_CONFIGURATION |
4-Warning |
<133>CMTS[DOCSIS]:<73010800> Network Access has Invalid Parameter. CM Mac Addr <[enet]> |
REG REQ : Network Access has Invalid Parameter.\n |
ubr7200 |
"Check the Config File Parameters" |
|
UBR7200-4-BAD_REGISTRATION |
4-Warning |
Cable modem [enet] on interface [chars] when [chars] attempted re-registration with different QoS |
Modem sent a registration request when already registered with a different QoS |
ubr7200 |
"Modem could be attempting theft of service" |
|
UBR7200-4-BAD_REGISTRATION |
4-Warning |
Cable modem [enet] on interface [chars] when [chars] attempted re-registration with different QoS |
Modem sent a registration request when already registered with a different QoS |
ubr7200 |
"Modem could be attempting theft of service" |
|
UBR7200-4-BAD_UPSTREAM_CHANNEL_OVERLOAD |
4-Warning |
<133>CMTS[DOCSIS]:<73010700> Bad US CH -Overload. CM Mac Addr <[enet]> |
REG REQ : Bad US CH -Overload.\n |
ubr7200 |
"Check the Upstream Frequency" |
|
UBR7200-4-BAD_UPSTREAM_CHANNEL_OVERLOAD |
4-Warning |
<133>CMTS[DOCSIS]:<73010700> Bad US CH -Overload. CM Mac Addr <[enet]> |
REG REQ : Bad US CH -Overload.\n |
ubr7200 |
"Check the Upstream Frequency" |
|
UBR7200-4-BADCFGFILE |
4-Warning |
Modem config file [chars] at [inet]: [chars] |
Configuration file for the cable modem has problems |
ubr7200 |
"Make sure the config file is proper" |
|
UBR7200-4-BADCFGFILE |
4-Warning |
Modem config file [chars] at [inet]: [chars] |
Configuration file for the cable modem has problems |
ubr7200 |
"Make sure the config file is proper" |
|
UBR7200-4-BADCFGFILE_V6 |
4-Warning |
Modem config file [chars] at %P: [chars] |
Configuration file for the cable modem has problems |
ubr7200 |
"Make sure the config file is proper" |
|
UBR7200-4-BADCFGFILE_V6 |
4-Warning |
Modem config file [chars] at %P: [chars] |
Configuration file for the cable modem has problems |
ubr7200 |
"Make sure the config file is proper" |
|
UBR7200-4-BADTXOFFSET |
4-Warning |
Bad timing offset %ld detected for cable modem [enet] sid [hec] cm status [hec] dcc [chars] skip_reg [chars]. |
The cable modem is not using the correct starting offset during initial ranging. This causes a zero negative timing offset to be recorded by the CMTS for this modem. The CMTS internal algorithms that rely on the |
ubr7200 |
"Locate the cable modem based on MAC address and report initial " "timing offset problem to the CM vendor" |
|
UBR7200-4-BLZE_HM_TEST |
4-Warning |
Blaze HM testcase failed. Blaze indices allocated for MD host [dec]/[dec] on the Guardian [dec]/[dec] : [dec] Blaze indices in use on the MD Host: [dec] |
The blaze indices have not been deallocated on the Guardian |
ubr10000 |
LOG_STD_NO_ACTION |
|
UBR7200-4-BLZE_HM_TEST |
4-Warning |
Blaze HM testcase failed. Blaze indices allocated for MD host [dec]/[dec] on the Guardian [dec]/[dec] : [dec] Blaze indices in use on the MD Host: [dec] |
The blaze indices have not been deallocated on the Guardian |
ubr10000 |
LOG_STD_NO_ACTION |
|
UBR7200-4-BPI_WARNING |
4-Warning |
[chars]: SID=[dec] KeySeq=0x[hec] Cable Interface <[chars]> |
BPI Warning \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-BPI_WARNING |
4-Warning |
[chars]: SID=[dec] KeySeq=0x[hec] Cable Interface <[chars]> |
BPI Warning \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-CACHE_ENGINE_WARNING |
4-Warning |
Warning: [chars] - [dec] |
Cache engine warning message. |
snmpPerf |
"." |
|
UBR7200-4-CACHE_ENGINE_WARNING |
4-Warning |
Warning: [chars] - [dec] |
Cache engine warning message. |
snmpPerf |
"." |
|
UBR7200-4-CLASSIFIER_ERROR |
4-Warning |
CM MAC: [chars] Classifier direction: [chars] Param code: [dec] Confirm code: [dec] |
Looks like issue while admitting/activating Classifier |
ubr7200 |
"Please look for DOCSIS message logs followed for more details" |
|
UBR7200-4-CLASSIFIER_ERROR |
4-Warning |
CM MAC: [chars] Classifier direction: [chars] Param code: [dec] Confirm code: [dec] |
Looks like issue while admitting/activating Classifier |
ubr7200 |
"Please look for DOCSIS message logs followed for more details" |
|
UBR7200-4-CLK_HWFAULT |
4-Warning |
Hardware Fault in Clockcard |
Hardware fault in Clockcard |
ubr7200 |
"Replace clock card" |
|
UBR7200-4-CLK_HWFAULT |
4-Warning |
Hardware Fault in Clockcard |
Hardware fault in Clockcard |
ubr7200 |
"Replace clock card" |
|
UBR7200-4-CM_NP_RF_FAILURE |
4-Warning |
CM <[enet]> on host interface <[chars]> reported NP RF <[dec]> failure modular-cable <[chars]> CM's NP RFs <[chars]> |
CMTS is configured to run script via Embedded Event Manager to handle the Cable Modem NP RF failure. |
ubr7200 |
"Verify that Cable Modem is not experienceing wideband connectivity." |
|
UBR7200-4-CM_NP_RF_FAILURE |
4-Warning |
CM <[enet]> on host interface <[chars]> reported NP RF <[dec]> failure modular-cable <[chars]> CM's NP RFs <[chars]> |
CMTS is configured to run script via Embedded Event Manager to handle the Cable Modem NP RF failure. |
cbr-application |
"Verify that Cable Modem is not experienceing wideband connectivity." |
|
UBR7200-4-CM_SF_DSID_INCONSISTENT |
4-Warning |
DSID [dec] BG: [dec] assigned to SF:[dec] already. DSID invalid on CM-[enet] |
DSID assigned to SF not valid any longer. SW Bug |
ubr10000 |
"Copy the error message exactly as it appears " "and report it to your technical services representative" |
|
UBR7200-4-CM_SF_DSID_INCONSISTENT |
4-Warning |
DSID [dec] BG: [dec] assigned to SF:[dec] already. DSID invalid on CM-[enet] |
DSID assigned to SF not valid any longer. SW Bug |
ubr10000 |
"Copy the error message exactly as it appears " "and report it to your technical services representative" |
|
UBR7200-4-CMLOCKED |
4-Warning |
Cable Modem [enet] in [chars] locked due to [chars] theft of service |
Configuration file for the cable modem has problems |
ubr7200 |
"Cable modem attempted to steal service" |
|
UBR7200-4-CMLOCKED |
4-Warning |
Cable Modem [enet] in [chars] locked due to [chars] theft of service |
Configuration file for the cable modem has problems |
ubr7200 |
"Cable modem attempted to steal service" |
|
UBR7200-4-CMMARKED |
4-Warning |
Cable Modem [enet] in [chars] attempted theft of service |
Configuration file for the cable modem has problems |
ubr7200 |
"Cable modem attempted to steal service" |
|
UBR7200-4-CMMARKED |
4-Warning |
Cable Modem [enet] in [chars] attempted theft of service |
Configuration file for the cable modem has problems |
ubr7200 |
"Cable modem attempted to steal service" |
|
UBR7200-4-CMNOPRIMSF |
4-Warning |
CM [enet] does not have any primary service flows |
This CM has no primary service flows |
ubr7200 |
"For Informational Purposes Only" |
|
UBR7200-4-CMNOPRIMSF |
4-Warning |
CM [enet] does not have any primary service flows |
This CM has no primary service flows |
ubr7200 |
"NO action is required" |
|
UBR7200-4-CMTS_IPV6_DROPPING_DHCPV6REQ_FOR_FAIL_IN_LLA_AUTOFIX |
4-Warning |
Dropping DHCPv6 request \nbecause CMTS has not received NS DAD for link-local address from this \nclient and failed to create a new link-local entry for MAC <[enet]> IPv6 <%P> |
\nDropping DHCPv6 request because CMTS has not received NS DAD for link-local address and CMTS failed to add the link-local to client db |
ubr7200 |
"Check the client and subscriber" |
|
UBR7200-4-CMTS_IPV6_LLA_FAILED_DAD |
4-Warning |
<133>CMTS[DOCSIS]:<68001301> IPv6 Link-local address has failed DAD. Addr <[enet]> |
IPv6 Link-Local has failed DAD.\n |
ubr7200 |
"Check the modem and subscriber" |
|
UBR7200-4-CMTS_IPV6_LLA_FAILED_DAD |
4-Warning |
<133>CMTS[DOCSIS]:<68001301> IPv6 Link-local address has failed DAD. Addr <[enet]> |
IPv6 Link-Local has failed DAD.\n |
ubr7200 |
"Check the modem and subscriber" |
|
UBR7200-4-CMTS_IPV6_RX_DAD_BUT_MDD_ISV4 |
4-Warning |
CMTS ND Proxy code see an NS when CMTS is MDD is v4 only bailing out and not\n accepting this NS message from modem with MAC [enet] |
CMTS is not supposed to receive an IPv6 DAD when MDD is set to v4\n |
ubr7200 |
"Check the modem and subscriber" |
|
UBR7200-4-CMTS_IPV6_RX_DHCPV6_WITH_BADADDR |
4-Warning |
DHCPv6 request received with a bad src IPv6 \naddr. IP <%P> msg <[chars]> |
DHCPv6 request received with a bad src IPv6 addr dropping the req\n |
ubr7200 |
"Check the modem and subscriber" |
|
UBR7200-4-CMTS_IPV6_RX_DHCPV6_WITH_BADADDR |
4-Warning |
DHCPv6 request received with a bad src IPv6 \naddr. IP <%P> msg <[chars]> |
DHCPv6 request received with a bad src IPv6 addr dropping the req\n |
ubr7200 |
"Check the modem and subscriber" |
|
UBR7200-4-CMTS_IPV6_RX_DHCPV6_WITH_MISCONFIG |
4-Warning |
DHCPv6 reply received \nwith a IPv6 address that does not match the bundle config\nReceived IPv6 address that matches [chars] expected [chars] |
DHCPv6 reply received a IPv6 addr that does not match the bundle config dropping the req\n |
ubr7200 |
"Check the bundle config and provisioning system" |
|
UBR7200-4-CMTS_OIR_INACTIVE_WITHOUT_L2VPN_UNCONFIGURED |
4-Warning |
Card on [dec]/[dec] with l2vpn \[chars]\ command should be taken care of before plugging different type of card or executing \no card\ command. |
Card is configured with cable l2vpn commands please take care of these configurations before plugging different type of card or executing \no card\ command. |
cmts-application |
"." |
|
UBR7200-4-CMTS_OIR_INACTIVE_WITHOUT_L2VPN_UNCONFIGURED |
4-Warning |
Card on [dec]/[dec] with l2vpn \[chars]\ command should be taken care of before plugging different type of card or executing \no card\ command. |
Card is configured with cable l2vpn commands please take care of these configurations before plugging different type of card or executing \no card\ command. |
cmts-application |
"." |
|
UBR7200-4-CMTS_RF_POWER_ADJUST |
4-Warning |
rf-power adjusted to [dec] dBmV to meet upconvertor requirement. |
This card has an upconvertor that has different limits on rf-power. rf-power has been adjusted to meet these limits. |
ubr10000 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-CMTS_RF_POWER_ADJUST |
4-Warning |
rf-power adjusted to [dec] dBmV to meet upconvertor requirement. |
This card has an upconvertor that has different limits on rf-power. rf-power has been adjusted to meet these limits. |
ubr10000 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-COOKIE |
4-Warning |
Corrupt or missing MAC address cookie\n using random base [enet] |
Data stored in midplane is bad. |
ubr7200 |
"Contact technical support to update your system." |
|
UBR7200-4-COOKIE |
4-Warning |
Corrupt or missing MAC address cookie\n using random base [enet] |
Data stored in midplane is bad. |
ubr7200 |
"Contact technical support to update your system." |
|
UBR7200-4-COS_INVALID_ID_OUT_OF_RANGE |
4-Warning |
<133>CMTS[DOCSIS]:<73011100> Bad Class of Service. Invalid Class ID or out of range. CM Mac Addr <[enet]> |
Bad Class of Service. Invalid Class ID or out of range. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-COS_INVALID_ID_OUT_OF_RANGE |
4-Warning |
<133>CMTS[DOCSIS]:<73011100> Bad Class of Service. Invalid Class ID or out of range. CM Mac Addr <[enet]> |
Bad Class of Service. Invalid Class ID or out of range. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-COS_UNSUPPORTED_CLASS |
4-Warning |
<133>CMTS[DOCSIS]:<73011000> Bad Class of Service- Unsupported class. CM Mac Addr <[enet]> |
Registration Failed Bad Class of Service-Unsupported class\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-COS_UNSUPPORTED_CLASS |
4-Warning |
<133>CMTS[DOCSIS]:<73011000> Bad Class of Service- Unsupported class. CM Mac Addr <[enet]> |
Registration Failed Bad Class of Service-Unsupported class\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-CRL_NOT_RESPONDING |
4-Warning |
<132>CMTS[DOCSIS]:<66030400> Failed to retrieve CRL from [chars] |
CRL not available\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-CRL_NOT_RESPONDING |
4-Warning |
<132>CMTS[DOCSIS]:<66030400> Failed to retrieve CRL from [chars] |
CRL not available\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DCC_ACK_REJ_UNKNOWN_TRANSACTION_ID |
4-Warning |
<133>CMTS[DOCSIS]:<67040300> DCC-ACK rejected unknown transaction ID. CM Mac Addr <[enet]> |
DCC-ACK rejected unknown transaction ID |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-DCC_ACK_REJ_UNKNOWN_TRANSACTION_ID |
4-Warning |
<133>CMTS[DOCSIS]:<67040300> DCC-ACK is rejected - Unknown transaction ID. CM MAC addr <[enet]> |
DCC-ACK is rejected because of unknown transaction ID |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DCC_NO_RESOURCE_ON_TARGET |
4-Warning |
DCC [enet] aborted. No resource available on target [chars] U[dec] |
No resource available on target channel for the DCC transaction |
ddc |
"Check target channel utilization" |
|
UBR7200-4-DCC_NO_RESOURCE_ON_TARGET |
4-Warning |
DCC [enet] is aborted - No resource available on target [chars] U[dec] |
No resource available on target channel for the DCC transaction |
cbr-application |
"Check target channel utilization" |
|
UBR7200-4-DCC_REJ_20_DISABLE |
4-Warning |
<133>CMTS[DOCSIS]:<67021900> DCC rejected 2.0 mode disabled. CM Mac Addr <[enet]> |
DCC rejected 2.0 mode disabled |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-DCC_REJ_20_DISABLE |
4-Warning |
<133>CMTS[DOCSIS]:<67021900> DCC is rejected - DOCSIS 2.0 mode is disabled. CM MAC addr <[enet]> |
DCC is rejected because DOCSIS 2.0 mode is disabled |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DCC_REJ_AUTHENTICATION_FAILURE |
4-Warning |
<133>CMTS[DOCSIS]:<67021100> DCC rejected authentication failure. CM Mac Addr <[enet]> |
DCC rejected authentication failure |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-DCC_REJ_AUTHENTICATION_FAILURE |
4-Warning |
<133>CMTS[DOCSIS]:<67021100> DCC is rejected - Authentication failure. CM MAC addr <[enet]> |
DCC is rejected because of authentication failure |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DCC_REJ_DUPLICATE_REF_ID_INDEX |
4-Warning |
<133>CMTS[DOCSIS]:<67021500> DCC rejected duplicate SF reference-ID or index in message. CM Mac Addr <[enet]> |
DCC rejected duplicate SF reference-ID or index in message |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-DCC_REJ_DUPLICATE_REF_ID_INDEX |
4-Warning |
<133>CMTS[DOCSIS]:<67021500> DCC is rejected - Duplicated service flow reference-ID or index in message. CM MAC addr <[enet]> |
DCC is rejected because duplicated service flow reference-ID or index exists in message |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DCC_REJ_MSG_SYNTAX_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<67021700> DCC rejected message syntax error. CM Mac Addr <[enet]> |
DCC rejected message syntax error |
ubr7200 |
"Check the TLV and parameters set while sending the DCC-REQ" |
|
UBR7200-4-DCC_REJ_MSG_SYNTAX_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<67021700> DCC is rejected - Message syntax error. CM MAC addr <[enet]> |
DCC is rejected because of message syntax error |
cbr-application |
"Check the TLV and parameters setting while sending the DCC request message" |
|
UBR7200-4-DCC_REJ_MSG_TOO_BIG |
4-Warning |
<133>CMTS[DOCSIS]:<67021800> DCC rejected message too big. CM Mac Addr <[enet]> |
DCC rejected message too big |
ubr7200 |
"Mimimize the msg length to be less than 1536" |
|
UBR7200-4-DCC_REJ_MSG_TOO_BIG |
4-Warning |
<133>CMTS[DOCSIS]:<67021800> DCC is rejected - Message length too big. CM MAC addr <[enet]> |
DCC is rejected because message length is too big |
cbr-application |
"Mimimize the message length to be less than 1536" |
|
UBR7200-4-DCC_REJ_MULTIPLE_ERRORS |
4-Warning |
<133>CMTS[DOCSIS]:<67021200> DCC rejected multiple errors. CM Mac Addr <[enet]> |
DCC rejected multiple errors |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-DCC_REJ_MULTIPLE_ERRORS |
4-Warning |
<133>CMTS[DOCSIS]:<67021200> DCC is rejected - Multiple errors. CM MAC addr <[enet]> |
DCC is rejected because of multiple errors |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DCC_REJ_PARAMETER_INVALID_CONTEXT |
4-Warning |
<133>CMTS[DOCSIS]:<67021600> DCC rejected parameter invalid for context. CM Mac Addr <[enet]> |
DCC rejected parameter invalid for contex |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-DCC_REJ_PARAMETER_INVALID_CONTEXT |
4-Warning |
<133>CMTS[DOCSIS]:<67021600> DCC is rejected - Invalid parameter for context. CM MAC addr <[enet]> |
DCC is rejected because of invalid parameter for contex |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DCC_REJ_PERMANENT_DCC_NOT_SUPPORTED |
4-Warning |
<133>CMTS[DOCSIS]:<67020800> DCC rejected permanent - DCC not supported. CM Mac Addr <[enet]> |
DCC rejected permanent - DCC not supported |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-DCC_REJ_PERMANENT_DCC_NOT_SUPPORTED |
4-Warning |
<133>CMTS[DOCSIS]:<67020800> DCC is rejected permanently - DCC not supported. CM MAC addr <[enet]> |
DCC is rejected permanently because DCC is not supported |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DCC_REJ_REQUIRED_PARAMETER_NOT_PRESENT |
4-Warning |
<133>CMTS[DOCSIS]:<67021000> DCC rejected required parameter not present. CM Mac Addr <[enet]> |
DCC rejected required parameter not present |
ubr7200 |
"Double check the parameters while sending the DCC-REQ" |
|
UBR7200-4-DCC_REJ_REQUIRED_PARAMETER_NOT_PRESENT |
4-Warning |
<133>CMTS[DOCSIS]:<67021000> DCC is rejected - Required parameter not present. CM MAC addr <[enet]> |
DCC is rejected because required parameter is not present |
cbr-application |
"Double check the parameters while sending the DCC request message" |
|
UBR7200-4-DCC_REJ_SRV_FLOW_NOT_FOUND |
4-Warning |
<133>CMTS[DOCSIS]:<67020900> DCC rejected service flow not found. CM Mac Addr <[enet]> |
DCC rejected service flow not found |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-DCC_REJ_SRV_FLOW_NOT_FOUND |
4-Warning |
<133>CMTS[DOCSIS]:<67020900> DCC is rejected - Service flow not found. CM MAC addr <[enet]> |
DCC is rejected because service flow was not found |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DCC_REJ_UNSPECIFIED_REASON |
4-Warning |
<133>CMTS[DOCSIS]:<67020700> DCC rejected unspecified reason. CM Mac Addr <[enet]> |
DCC rejected unspecified reason |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-DCC_REJ_UNSPECIFIED_REASON |
4-Warning |
<133>CMTS[DOCSIS]:<67020700> DCC is rejected - Unspecified reason. CM MAC addr <[enet]> |
DCC is rejected because of unspecified reason |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DCC_REQ_ABORT_NO_COMM_NEW_UPSTREAM_CHANNEL |
4-Warning |
<133>CMTS[DOCSIS]:<67020600> DCC aborted unable to communicate on new upstream channel. CM Mac Addr <[enet]> |
DCC aborted unable to communicate on new upstream channel |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-DCC_REQ_ABORT_NO_COMM_NEW_UPSTREAM_CHANNEL |
4-Warning |
<133>CMTS[DOCSIS]:<67020600> DCC is aborted - Unable to communicate on new upstream channel. CM MAC addr <[enet]> |
DCC is aborted unable to communicate on new upstream channel |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DCC_REQ_ARRIVE_NEW |
4-Warning |
<133>CMTS[DOCSIS]:<67020300> DCC arrive new. CM Mac Addr <[enet]> |
DCC arrive new |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-DCC_REQ_ARRIVE_NEW |
4-Warning |
<133>CMTS[DOCSIS]:<67020300> DCC arrives new channel. CM MAC addr <[enet]> |
DCC arrives new channel |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DCC_REQ_DEPART_OLD |
4-Warning |
<133>CMTS[DOCSIS]:<67020200> DCC depart old. CM Mac Addr <[enet]> |
DCC depart old |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-DCC_REQ_DEPART_OLD |
4-Warning |
<133>CMTS[DOCSIS]:<67020200> DCC departs old channel. CM MAC addr <[enet]> |
DCC departs old channel |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DCC_REQ_REJ_ALREADY |
4-Warning |
<133>CMTS[DOCSIS]:<67020100> DCC rejected already there. CM Mac Addr <[enet]> |
DCC rejected already there |
ubr7200 |
"Wait until the transaction ends.Otherwise try another channel ID to move the modem " |
|
UBR7200-4-DCC_REQ_REJ_ALREADY |
4-Warning |
<133>CMTS[DOCSIS]:<67020100> DCC is rejected - CM MAC address <[enet]> already on destination. |
DCC is rejected because CM MAC address is already on destination |
cbr-application |
"Wait until the transaction ends. Otherwise try to move the modem on another channel." |
|
UBR7200-4-DCC_RSP_NOT_RCV_NEW_CHANNEL |
4-Warning |
<133>CMTS[DOCSIS]:<67030200> DCC-RSP not received on new channel. CM Mac Addr <[enet]> |
DCC-RSP not received on new channel |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-DCC_RSP_NOT_RCV_NEW_CHANNEL |
4-Warning |
<133>CMTS[DOCSIS]:<67030200> DCC response was unreceived on new channel. CM MAC addr <[enet]> |
DCC response was unreceived on new channel |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DCC_RSP_NOT_RCV_OLD_CHANNEL |
4-Warning |
<133>CMTS[DOCSIS]:<67030100> DCC-RSP not received on old channel. CM Mac Addr <[enet]> |
DCC-RSP not received on old channel |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-DCC_RSP_NOT_RCV_OLD_CHANNEL |
4-Warning |
<133>CMTS[DOCSIS]:<67030100> DCC response was unreceived on old channel. CM MAC addr <[enet]> |
DCC response was unreceived on old channel |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DCC_RSP_REJ_AUTHENTICATION_FAILURE |
4-Warning |
<133>CMTS[DOCSIS]:<67030500> DCC-RSP rejected authentication failure. CM Mac Addr <[enet]> |
DCC-RSP rejected authentication failure |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-DCC_RSP_REJ_AUTHENTICATION_FAILURE |
4-Warning |
<133>CMTS[DOCSIS]:<67030500> DCC Response is rejected - Authentication failure. CM MAC addr <[enet]> |
DCC response is rejected because of authentication failure |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DCC_RSP_REJ_MSG_SYNTAX_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<67030600> DCC-RSP rejected message syntax error. CM Mac Addr <[enet]> |
DCC-RSP rejected message syntax error |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-DCC_RSP_REJ_MSG_SYNTAX_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<67030600> DCC Response is rejected - Message syntax error. CM MAC addr <[enet]> |
DCC response is rejected because of message syntax error |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DCC_RSP_REJ_UNKNOWN_TRANSACTION_ID |
4-Warning |
<133>CMTS[DOCSIS]:<67030400> DCC-RSP rejected unknown transaction ID. CM Mac Addr <[enet]> |
DCC-RSP rejected unknown transaction ID |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-DCC_RSP_REJ_UNKNOWN_TRANSACTION_ID |
4-Warning |
<133>CMTS[DOCSIS]:<67030400> DCC Response is rejected - Unknown transaction ID. CM MAC addr <[enet]> |
DCC response is rejected because of unknown transaction ID |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DCC_RSP_REJ_UNSPECIFIED_REASON |
4-Warning |
<133>CMTS[DOCSIS]:<67030300> DCC-RSP rejected unspecified reason. CM Mac Addr <[enet]> |
DCC-RSP rejected unspecified reason |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-DCC_RSP_REJ_UNSPECIFIED_REASON |
4-Warning |
<133>CMTS[DOCSIS]:<67030300> DCC Response is rejected - Unspecified reason. CM MAC addr <[enet]> |
DCC response is rejected because of unspecified reason |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DDC_CFG_HASHID |
4-Warning |
Hash id [dec] does not exist in global configuration |
A hash id is configured for a cable interface but is not defined globally |
ddc |
"Fix configuration" |
|
UBR7200-4-DDC_CFG_HASHID |
4-Warning |
Hash id [dec] does not exist in global configuration |
A hash id is configured for a cable interface but is not defined globally |
ddc |
"Fix configuration" |
|
UBR7200-4-DDC_GENERAL_ERROR |
4-Warning |
Error: [chars] |
Catchall error message for DDC |
ddc |
"Copy the error message exactly as it appears " "and report it to your technical services representative" |
|
UBR7200-4-DDC_GENERAL_ERROR |
4-Warning |
Error: [chars] |
Catchall error message for DDC |
ddc |
"Copy the error message exactly as it appears " "and report it to your technical services representative" |
|
UBR7200-4-DDC_LIST_ERROR |
4-Warning |
DDC list error |
DDC failed to create or add element to list |
ddc |
"Copy the error message exactly as it appears " "and report it to your technical services representative" |
|
UBR7200-4-DDC_LIST_ERROR |
4-Warning |
DDC list error |
DDC failed to create or add element to list |
ddc |
"Copy the error message exactly as it appears " "and report it to your technical services representative" |
|
UBR7200-4-DDC_MESSAGE_ERROR |
4-Warning |
DDC message error. type [dec] |
DDC failed to send interprocess or IPC message |
ddc |
"Copy the error message exactly as it appears " "and report it to your technical services representative" |
|
UBR7200-4-DDC_MESSAGE_ERROR |
4-Warning |
DDC message error. type [dec] |
DDC failed to send interprocess or IPC message |
ddc |
"Copy the error message exactly as it appears " "and report it to your technical services representative" |
|
UBR7200-4-DDC_NODE_ID_ERROR |
4-Warning |
Node id mismatch NPE: [dec] linecard: [dec] |
Node id's on NPE subinterface is different than on linecard |
ddc |
"Copy the error message exactly as it appears " "and report it to your technical services representative" |
|
UBR7200-4-DDC_NODE_ID_ERROR |
4-Warning |
Node id mismatch NPE: [dec] linecard: [dec] |
Node id's on NPE subinterface is different than on linecard |
ddc |
"Copy the error message exactly as it appears " "and report it to your technical services representative" |
|
UBR7200-4-DDC_PROT_FREQ_ERROR |
4-Warning |
DS frequency not configured for the protect target node [dec] |
DS frequencies are not configured for all protect targets |
ddc |
"Fix configuration" |
|
UBR7200-4-DDC_PROT_FREQ_ERROR |
4-Warning |
DS frequency not configured for the protect target node [dec] |
DS frequencies are not configured for all protect targets |
ddc |
"Fix configuration" |
|
UBR7200-4-DDC_SEMAPHORE_ERROR |
4-Warning |
DDC semaphore released when it was not taken |
DDC semaphore was not take when release was requested |
ddc |
"Copy the error message exactly as it appears " "and report it to your technical services representative" |
|
UBR7200-4-DDC_SEMAPHORE_ERROR |
4-Warning |
DDC semaphore released when it was not taken |
DDC semaphore was not take when release was requested |
ddc |
"Copy the error message exactly as it appears " "and report it to your technical services representative" |
|
UBR7200-4-DDC_UNEXPECTED_EVENT_ERROR |
4-Warning |
DDC unexpected event error [dec] |
DDC received an unexpected or unsupported event |
ddc |
"Copy the error message exactly as it appears " "and report it to your technical services representative" |
|
UBR7200-4-DDC_UNEXPECTED_EVENT_ERROR |
4-Warning |
DDC unexpected event error [dec] |
DDC received an unexpected or unsupported event |
ddc |
"Copy the error message exactly as it appears " "and report it to your technical services representative" |
|
UBR7200-4-DDC_UNEXPECTED_MESSAGE_ERROR |
4-Warning |
DDC unexpected message error [dec] |
DDC received an unexpected or unsupported message |
ddc |
"Copy the error message exactly as it appears " "and report it to your technical services representative" |
|
UBR7200-4-DDC_UNEXPECTED_MESSAGE_ERROR |
4-Warning |
DDC unexpected message error [dec] |
DDC received an unexpected or unsupported message |
ddc |
"Copy the error message exactly as it appears " "and report it to your technical services representative" |
|
UBR7200-4-DHCP_ACK_MISMATCH_CM |
4-Warning |
Not update cm state for DHCP ACK Expected CM [enet] ip [inet] found CM [enet] ip [inet] new ip [inet] |
Found a wrong CM during update DHCP ACK |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DHCP_PAK_TOO_SHORT |
4-Warning |
DHCP packet is too short from [inet] to [inet] UDP length [dec] |
A DHCP packet which is too short was received |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DHCPLQSIDMISMATCH |
4-Warning |
Source Verify of pkt from host [enet] [inet] sid [dec] does not match LQ Relay Info from server [inet] for CM [enet] sid [dec] on interface [chars] |
SID of packet does not match sid of mac addr in relay-agent info from DHCP server. |
ubr7200 |
"Manually verify lease info on DHCP server against current " "sid of the host." |
|
UBR7200-4-DHCPV6LQSIDMISMATCH |
4-Warning |
Source Verify of pkt from host [enet] %P sid [dec] does not match LQ Relay Info from server %P for CM [enet] sid [dec] on interface [chars] |
SID of packet does not match sid of mac addr in relay-agent info from DHCPv6 server. |
ubr7200 |
"Manually verify lease info on DHCPv6 server against current " "sid of the host." |
|
UBR7200-4-DIAG_LOG_FULL_REACHED |
4-Warning |
[DOCSIS]:<86000300>Docs Diag Log reaches max size |
Docs Diag Log Notification: log size reaches max size |
ubr7200 |
- |
|
UBR7200-4-DIAG_LOG_FULL_REACHED |
4-Warning |
[DOCSIS]:<86000300>Docs Diag Log reaches max size |
Docs Diag Log Notification: log size reaches max size |
ubr7200 |
- |
|
UBR7200-4-DIAG_LOG_HIGH_THRSHLD_REACHED |
4-Warning |
[DOCSIS]:<86000100>Docs Diag Log exceeds high threshold |
Docs Diag Log Notification :log size exceeds high threshold |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-DIAG_LOG_HIGH_THRSHLD_REACHED |
4-Warning |
[DOCSIS]:<86000100>Docs Diag Log exceeds high threshold |
Docs Diag Log Notification :log size exceeds high threshold |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-DOWNSTREAM_FREQUENCY_FORMAT_INVALID |
4-Warning |
<133>CMTS[DOCSIS]:<73010500> Bad DS FREQ - Format Invalid. CM Mac Addr <[enet]> |
REG REQ : Bad DS FREQ - Format Invalid .\n |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-DOWNSTREAM_FREQUENCY_FORMAT_INVALID |
4-Warning |
<133>CMTS[DOCSIS]:<73010500> Bad DS FREQ - Format Invalid. CM Mac Addr <[enet]> |
REG REQ : Bad DS FREQ - Format Invalid .\n |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-DOWNSTREAM_FREQUENCY_NOT_IN_USE |
4-Warning |
<133>CMTS[DOCSIS]:<73010501> Bad DS FREQ - Not in use. CM Mac Addr <[enet]> |
REG REQ : Bad DS FREQ - Not in use.\n |
ubr7200 |
"Please Check the Config File Frequency" |
|
UBR7200-4-DOWNSTREAM_FREQUENCY_NOT_IN_USE |
4-Warning |
<133>CMTS[DOCSIS]:<73010501> Bad DS FREQ - Not in use. CM Mac Addr <[enet]> |
REG REQ : Bad DS FREQ - Not in use.\n |
ubr7200 |
"Please Check the Config File Frequency" |
|
UBR7200-4-DOWNSTREAM_FREQUENCY_NOT_MULTIPLE_OF_62500 |
4-Warning |
<133>CMTS[DOCSIS]:<73010502> Bad DS FREQ - Not multiple of 62500. CM Mac Addr <[enet]> |
REG REQ : Bad DS FREQ - Not multiple of 62500.\n |
ubr7200 |
"Please Check the Config File Frequency" |
|
UBR7200-4-DOWNSTREAM_FREQUENCY_NOT_MULTIPLE_OF_62500 |
4-Warning |
<133>CMTS[DOCSIS]:<73010502> Bad DS FREQ - Not multiple of 62500. CM Mac Addr <[enet]> |
REG REQ : Bad DS FREQ - Not multiple of 62500.\n |
ubr7200 |
"Please Check the Config File Frequency" |
|
UBR7200-4-DSA_ABORTED_NO_ACK |
4-Warning |
<133>CMTS[DOCSIS]:<83020101> Service Add Aborted - No ACK. CM Mac Addr <[enet]> |
DSX Aborted No ACK \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_ABORTED_NO_ACK |
4-Warning |
<133>CMTS[DOCSIS]:<83020101> Service Add is aborted - No ACK. CM MAC addr <[enet]> |
DSX is aborted because no ACK \n |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_ACK_REJECTED_INVALID_TRANSACTION_ID |
4-Warning |
<133>CMTS[DOCSIS]:<83020100> Service Add Response rejected - Invalid transaction ID. CM Mac Addr <[enet]> |
ACK Rejected invalid transaction ID \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_ACK_REJECTED_INVALID_TRANSACTION_ID |
4-Warning |
<133>CMTS[DOCSIS]:<83020100> Service Add Response is rejected - Invalid transaction ID. CM MAC addr <[enet]> |
ACK is rejected because of invalid transaction ID \n |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_ADD_ABORTED |
4-Warning |
<133>CMTS[DOCSIS]:<83000108> Service Add rejected - Add aborted. CM Mac Addr <[enet]> |
CM DSA msg rejected. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_ADD_ABORTED |
4-Warning |
<133>CMTS[DOCSIS]:<83000108> Service Add is rejected - Add aborted. CM MAC addr <[enet]> |
CM DSA message is rejected. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_AUTH_FAILURE |
4-Warning |
<133>CMTS[DOCSIS]:<83000120> Service Add rejected - Authorization failure. CM Mac Addr <[enet]> |
CM DSA rejected because of an authorization failure. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_AUTH_FAILURE |
4-Warning |
<133>CMTS[DOCSIS]:<83000120> Service Add is rejected - Authorization failure. CM MAC addr <[enet]> |
CM DSA is rejected because of an authorization failure. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_CLASSIFIER_ANOTHER_FLOW |
4-Warning |
<133>CMTS[DOCSIS]:<83000117> Service Add rejected - Classifier for another flow . CM Mac Addr <[enet]> |
CM DSA rejected because classifier is for another flow. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_CLASSIFIER_ANOTHER_FLOW |
4-Warning |
<133>CMTS[DOCSIS]:<83000117> Service Add is rejected - Classifier for another flow. CM MAC addr <[enet]> |
CM DSA is rejected because classifier is for another flow. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_CLASSIFIER_EXISTS |
4-Warning |
<133>CMTS[DOCSIS]:<83000111> Service Add rejected - Classifier exists. CM Mac Addr <[enet]> |
CM DSA rejected due to classifier already exists. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_CLASSIFIER_EXISTS |
4-Warning |
<133>CMTS[DOCSIS]:<83000111> Service Add is rejected - Classifier exists. CM MAC addr <[enet]> |
CM DSA is rejected because classifier already exists. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_CLASSIFIER_NOT_FOUND |
4-Warning |
<133>CMTS[DOCSIS]:<83000110> Service Add rejected - Classifier not found. CM Mac Addr <[enet]> |
CM DSA rejected due to classifier not found. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_CLASSIFIER_NOT_FOUND |
4-Warning |
<133>CMTS[DOCSIS]:<83000110> Service Add is rejected - Classifier not found. CM MAC addr <[enet]> |
CM DSA is rejected because classifier was not found. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_DUPLICATE_REF_ID_INDEX |
4-Warning |
<133>CMTS[DOCSIS]:<83000114> Service Add rejected duplicate reference-ID or index in message . CM Mac Addr <[enet]> |
CM DSA rejected because duplicate ref ID or index. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_DUPLICATE_REF_ID_INDEX |
4-Warning |
<133>CMTS[DOCSIS]:<83000114> Service Add is rejected - Duplicated reference-ID or index in message. CM MAC addr <[enet]> |
CM DSA is rejected because of duplicated reference ID or index. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_HEADER_SUPPR_SETTING_NOT_SUPPORTED |
4-Warning |
<133>CMTS[DOCSIS]:<83000105> Service Add rejected - Header suppression setting not supported . CM Mac Addr <[enet]> |
Header suppression setting not supported\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_HEADER_SUPPR_SETTING_NOT_SUPPORTED |
4-Warning |
<133>CMTS[DOCSIS]:<83000105> Service Add is rejected - Header suppression setting not supported. CM MAC addr <[enet]> |
Header suppression setting is not supported\n |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_HMAC_AUTHENTICATION_FAILURE |
4-Warning |
<133>CMTS[DOCSIS]:<83000101> Service Add rejected - HMAC Authentication Failure. CM Mac Addr <[enet]> |
HMAC Authentication Failure \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_HMAC_AUTHENTICATION_FAILURE |
4-Warning |
<133>CMTS[DOCSIS]:<83000101> Service Add is rejected - HMAC authentication failure. CM MAC addr <[enet]> |
HMAC Authentication Failure \n |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_MAJOR_CLASSIFIER_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83000122> Service Add rejected - Major classifier error. CM Mac Addr <[enet]> |
CM DSA rejected because of a major classifier error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_MAJOR_CLASSIFIER_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83000122> Service Add is rejected - Major classifier error. CM MAC addr <[enet]> |
CM DSA is rejected because of a major classifier error. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_MAJOR_MULTIPLE_ERRORS |
4-Warning |
<133>CMTS[DOCSIS]:<83000124> Service Add rejected - Multiple major errors. CM Mac Addr <[enet]> |
CM DSA rejected because of multiple major errors. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_MAJOR_MULTIPLE_ERRORS |
4-Warning |
<133>CMTS[DOCSIS]:<83000124> Service Add is rejected - Multiple major errors. CM MAC addr <[enet]> |
CM DSA is rejected because of multiple major errors. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_MAJOR_PHS_RULE_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83000123> Service Add rejected - Major PHS rule error. CM Mac Addr <[enet]> |
CM DSA rejected because of a major PHS rule error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_MAJOR_PHS_RULE_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83000123> Service Add rejected - Major PHS rule error. CM MAC addr <[enet]> |
CM DSA is rejected because of a major PHS rule error. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_MAJOR_SRV_FLOW_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83000121> Service Add rejected - Major service flow error. CM Mac Addr <[enet]> |
CM DSA rejected becasue of a major service flow error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_MAJOR_SRV_FLOW_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83000121> Service Add is rejected - Major service flow error. CM MAC addr <[enet]> |
CM DSA is rejected because of a major service flow error. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_MSG_SYNTAX_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83000125> Service Add rejected - Message syntax error. CM Mac Addr <[enet]> |
CM DSA rejected because of a message syntax error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_MSG_SYNTAX_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83000125> Service Add is rejected - Message syntax error. CM MAC addr <[enet]> |
CM DSA is rejected because of message syntax error. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_MSG_TOO_BIG |
4-Warning |
<133>CMTS[DOCSIS]:<83000126> Service Add rejected - Message too big. CM Mac Addr <[enet]> |
CM DSA rejected becasue the msg was to big. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_MSG_TOO_BIG |
4-Warning |
<133>CMTS[DOCSIS]:<83000126> Service Add is rejected - Message too big. CM MAC addr <[enet]> |
CM DSA is rejected because message length was too big. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_MULTIPLE_DOWNSTREAM_FLOW |
4-Warning |
<133>CMTS[DOCSIS]:<83000116> Service Add rejected - Multiple downstream flow . CM Mac Addr <[enet]> |
CM DSA rejected because mulitple DS flows. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_MULTIPLE_DOWNSTREAM_FLOW |
4-Warning |
<133>CMTS[DOCSIS]:<83000116> Service Add is rejected - Multiple downstream flow. CM MAC addr <[enet]> |
CM DSA is rejected because of mulitple DS flows. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_MULTIPLE_ERRORS |
4-Warning |
<133>CMTS[DOCSIS]:<83000109> Service Add rejected - Multiple errors. CM Mac Addr <[enet]> |
CM DSA rejected due to multilpe errors. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_MULTIPLE_ERRORS |
4-Warning |
<133>CMTS[DOCSIS]:<83000109> Service Add is rejected - Multiple errors. CM MAC addr <[enet]> |
CM DSA is rejected due to multilpe errors. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_MULTIPLE_UPSTREAM_FLOW |
4-Warning |
<133>CMTS[DOCSIS]:<83000115> Service Add rejected - Multiple upstream flow . CM Mac Addr <[enet]> |
CM DSA rejected because muliptle US flows. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_MULTIPLE_UPSTREAM_FLOW |
4-Warning |
<133>CMTS[DOCSIS]:<83000115> Service Add is rejected - Multiple upstream flow. CM MAC addr <[enet]> |
CM DSA is rejected because of muliptle US flows. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_PARAMETER_INVALID_CONTEXT |
4-Warning |
<133>CMTS[DOCSIS]:<83000119> Service Add rejected - Parameter invalid for context. CM Mac Addr <[enet]> |
CM DSA rejected because a parameter is invalid for the context. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_PARAMETER_INVALID_CONTEXT |
4-Warning |
<133>CMTS[DOCSIS]:<83000119> Service Add is rejected - Parameter invalid for context. CM MAC addr <[enet]> |
CM DSA is rejected because parameter is invalid for the context. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_PERMANENT_ADMINISTRATIVE |
4-Warning |
<133>CMTS[DOCSIS]:<83000103> Service Add rejected - Permanent Administrative. CM Mac Addr <[enet]> [chars] |
Permanent Administrative \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_PERMANENT_ADMINISTRATIVE |
4-Warning |
<133>CMTS[DOCSIS]:<83000103> Service Add is rejected - Permanent administrative.CM MAC addr <[enet]> [chars] |
Permanent administrative \n |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_PHS_RULE_ANOTHER_FLOW |
4-Warning |
<133>CMTS[DOCSIS]:<83000118> Service Add rejected - PHS rule for another flow . CM Mac Addr <[enet]> |
CM DSA rejected becasue PHS rule if for another flow. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_PHS_RULE_ANOTHER_FLOW |
4-Warning |
<133>CMTS[DOCSIS]:<83000118> Service Add is rejected - PHS rule for another flow. CM MAC addr <[enet]> |
CM DSA is rejected because PHS rule is for another flow. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_PHS_RULE_EXISTS |
4-Warning |
<133>CMTS[DOCSIS]:<83000113> Service Add rejected - PHS rule exists. CM Mac Addr <[enet]> |
CM DSA rejected because the PHS rule already exists. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_PHS_RULE_EXISTS |
4-Warning |
<133>CMTS[DOCSIS]:<83000113> Service Add is rejected - PHS rule exists. CM MAC addr <[enet]> |
CM DSA is rejected because the PHS rule already exists. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_PHS_RULE_NOT_FOUND |
4-Warning |
<133>CMTS[DOCSIS]:<83000112> Service Add rejected - PHS rule not found . CM Mac Addr <[enet]> |
CM DSA rejected because the PHS rule was not found. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_PHS_RULE_NOT_FOUND |
4-Warning |
<133>CMTS[DOCSIS]:<83000112> Service Add is rejected - PHS rule not found. CM MAC addr <[enet]> |
CM DSA is rejected because the PHS rule was not found. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_REQUIRED_PARAMETER_NOT_PRESENT |
4-Warning |
<133>CMTS[DOCSIS]:<83000104> Service Add rejected - Required parameter not present. CM Mac Addr <[enet]> |
Required parameter not present\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_REQUIRED_PARAMETER_NOT_PRESENT |
4-Warning |
<133>CMTS[DOCSIS]:<83000104> Service Add is rejected - Required parameter not present. CM MAC addr <[enet]> |
Required parameter is not present\n |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_RSP_ABORTED_NO_RSP |
4-Warning |
<133>CMTS[DOCSIS]:<83010101> Service Add aborted - No RSP . CM Mac Addr <[enet]> |
CM DSA aborted. No response. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_RSP_ABORTED_NO_RSP |
4-Warning |
<133>CMTS[DOCSIS]:<83010101> Service Add is aborted - No response. CM MAC addr <[enet]> |
CM DSA is aborted because no response. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_RSP_INVALID_TRANSACTION_ID |
4-Warning |
<133>CMTS[DOCSIS]:<83010100> Service Add response rejected - Invalid Transaction ID . CM Mac Addr <[enet]> |
CM DSA response is rejected because of invalid transation ID. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_RSP_INVALID_TRANSACTION_ID |
4-Warning |
<133>CMTS[DOCSIS]:<83010100> Service Add Response is rejected - Invalid transaction ID. CM MAC addr <[enet]> |
CM DSA response is rejected because of invalid transation ID. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_RSP_REJECT_MAJOR_CFR_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83010115> Service Add Response rejected - Major classifier error. CM Mac Addr <[enet]> |
CM DSA RSP rejected because of a major classifier error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_RSP_REJECT_MAJOR_CFR_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83010115> Service Add Response is rejected - Major classifier error. CM MAC addr <[enet]> |
CM DSA response is rejected because of a major classifier error. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_RSP_REJECT_MAJOR_PHS_RULE_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83010116> Service Add Response rejected - Major PHS Rule error. CM Mac Addr <[enet]> |
CM DSA RSP rejected because of a major PHS rule error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_RSP_REJECT_MAJOR_PHS_RULE_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83010116> Service Add Response is rejected - Major PHS rule error. CM MAC addr <[enet]> |
CM DSA response is rejected because of a major PHS rule error. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_RSP_REJECT_MSG_TOO_BIG |
4-Warning |
<133>CMTS[DOCSIS]:<83010118> Service Add Response rejected - Message too big. CM Mac Addr <[enet]> |
CM DSA RSP rejected becasue the msg was to big. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_RSP_REJECT_MSG_TOO_BIG |
4-Warning |
<133>CMTS[DOCSIS]:<83010118> Service Add Response is rejected - Message length too big. CM MAC addr <[enet]> |
CM DSA response is rejected because message length was too big. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_RSP_REJECT_PARAM_INVALID_FOR_CONTEXT |
4-Warning |
<133>CMTS[DOCSIS]:<83010113> Service Add Response rejected - Parameter invalid for context. CM Mac Addr <[enet]> |
CM DSA RSP rejected because a parameter is invalid for the context |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_RSP_REJECT_PARAM_INVALID_FOR_CONTEXT |
4-Warning |
<133>CMTS[DOCSIS]:<83010113> Service Add Response is rejected - Invalid parameter for context. CM MAC addr <[enet]> |
CM DSA response is rejected because of invalid parameter for context |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_RSP_REJECT_PHS_RULE_EXISTS |
4-Warning |
<133>CMTS[DOCSIS]:<83010110> Service Add Response rejected - PHS rule exists. CM Mac Addr <[enet]> |
CM DSA is rejected because the PHS rule already exists. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_RSP_REJECT_PHS_RULE_EXISTS |
4-Warning |
<133>CMTS[DOCSIS]:<83010110> Service Add Response is rejected - PHS rule exists. CM MAC addr <[enet]> |
CM DSA response is rejected because the PHS rule already exist. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_RSP_REJECT_REQD_PARAM_NOT_PRESENT |
4-Warning |
<133>CMTS[DOCSIS]:<83010106> Service Add Response rejected - Required parameter not present. CM Mac Addr <[enet]> |
CM DSA RSP is rejected because the required parameter is not present. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_RSP_REJECT_REQD_PARAM_NOT_PRESENT |
4-Warning |
<133>CMTS[DOCSIS]:<83010106> Service Add Response is rejected - Required parameter not present. CM MAC addr <[enet]> |
CM DSA response is rejected because the required parameter is not present. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_RSP_REJECT_UNRECOGNIZED_CONFIGURATION_SETTING |
4-Warning |
<133>CMTS[DOCSIS]:<83010105> Service Add Response rejected - Unrecognized configuration setting. CM Mac Addr <[enet]> |
CM DSA RSP is rejected because of unrecognized configuration setting. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_RSP_REJECT_UNRECOGNIZED_CONFIGURATION_SETTING |
4-Warning |
<133>CMTS[DOCSIS]:<83010105> Service Add Response is rejected - Unrecognized configuration setting. CM MAC addr <[enet]> |
CM DSA response is rejected because of unrecognized configuration setting. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_SERVICE_FLOW_EXISTS |
4-Warning |
<133>CMTS[DOCSIS]:<83000106> Service Add rejected Service flow exists . CM Mac Addr <[enet]> |
CM DSA rejected. Service flow exists. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_SERVICE_FLOW_EXISTS |
4-Warning |
<133>CMTS[DOCSIS]:<83000106> Service Add rejected - Service flow exists. CM MAC addr <[enet]> |
CM DSA is rejected because service flow exists. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_TEMP_DCC |
4-Warning |
<133>CMTS[DOCSIS]:<83000127> Service Add rejected - Temporary DCC . CM Mac Addr <[enet]> |
CM DSA rejected due to a tmp DCC. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_TEMP_NO_RESOURCE |
4-Warning |
<133>CMTS[DOCSIS]:<83000102> Service Add rejected - Temporary no resource. CM Mac Addr <[enet]> [chars] |
CM DSA message rejected due to no rousources. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_TEMP_NO_RESOURCE |
4-Warning |
<133>CMTS[DOCSIS]:<83000102> Service Add is rejected - Temporary no resource.CM MAC addr <[enet]> [chars] |
CM DSA message is rejected due to no resources. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_UNRECOGNIZED_CONFIGURATION_SETTING |
4-Warning |
<133>CMTS[DOCSIS]:<83000101> Service Add rejected - Unrecognized Configuration Setting. CM Mac Addr <[enet]> |
Unrecognized Configuration Setting \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_UNRECOGNIZED_CONFIGURATION_SETTING |
4-Warning |
<133>CMTS[DOCSIS]:<83000101> Service Add is rejected - Unrecognized configuration setting. CM MAC addr <[enet]> |
Unrecognized configuration setting \n |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_UNSPECIFIED_REASON |
4-Warning |
<133>CMTS[DOCSIS]:<83000100> Service Add rejected - Unspecified reason. CM Mac Addr <[enet]> |
Unspecified reason \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSA_UNSPECIFIED_REASON |
4-Warning |
<133>CMTS[DOCSIS]:<83000100> Service Add is rejected - Unspecified reason. CM MAC addr <[enet]> |
Unspecified reason \n |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_ABORTED_NO_ACK |
4-Warning |
<133>CMTS[DOCSIS]:<83020201> Service Change Aborted - No ACK. CM Mac Addr <[enet]> |
DSX Aborted No ACK \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_ABORTED_NO_ACK |
4-Warning |
<133>CMTS[DOCSIS]:<83020201> Service Change is aborted - No ACK. CM MAC addr <[enet]> |
DSX is aborted because no ACK \n |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_ACK_REJECTED_INVALID_TRANSACTION_ID |
4-Warning |
<133>CMTS[DOCSIS]:<83020200> Service Change ACK Rejected - Invalid transaction ID. CM Mac Addr <[enet]> |
ACK Rejected invalid transaction ID \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_ACK_REJECTED_INVALID_TRANSACTION_ID |
4-Warning |
<133>CMTS[DOCSIS]:<83020200> Service Change ACK is rejected - Invalid transaction ID. CM MAC addr <[enet]> |
ACK is rejected because of invalid transaction ID \n |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_AUTH_FAILURE |
4-Warning |
<133>CMTS[DOCSIS]:<83000220> Service Change rejected - Authorization failure. CM Mac Addr <[enet]> |
CM DSC rejected because authorizatio failure. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_AUTH_FAILURE |
4-Warning |
<133>CMTS[DOCSIS]:<83000220> Service Change is rejected - Authorization failure. CM MAC addr <[enet]> |
CM DSC is rejected because authorization failed. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_CLASSIFIER_ANOTHER_FLOW |
4-Warning |
<133>CMTS[DOCSIS]:<83000217> Service Change rejected - Classifier for another flow . CM Mac Addr <[enet]> |
CM DSC rejected because classifier is for another flow. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_CLASSIFIER_ANOTHER_FLOW |
4-Warning |
<133>CMTS[DOCSIS]:<83000217> Service Change rejected - Classifier for another flow. CM MAC addr <[enet]> |
CM DSC is rejected because classifier is for another flow. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_CLASSIFIER_EXISTS |
4-Warning |
<133>CMTS[DOCSIS]:<83000211> Service Change rejected - Classifier exists. CM Mac Addr <[enet]> |
CM DSC rejected because classifier exists. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_CLASSIFIER_EXISTS |
4-Warning |
<133>CMTS[DOCSIS]:<83000211> Service Change is rejected - Classifier exists. CM MAC addr <[enet]> |
CM DSC is rejected because classifier has been exist. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_CLASSIFIER_NOT_FOUND |
4-Warning |
<133>CMTS[DOCSIS]:<83000210> Service Change rejected - Classifier not found. CM Mac Addr <[enet]> |
CM DSC rejected because of classifier not found. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_CLASSIFIER_NOT_FOUND |
4-Warning |
<133>CMTS[DOCSIS]:<83000210> Service Change is rejected - Classifier not found. CM MAC addr <[enet]> |
CM DSC is rejected because classifier is not found. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_DUPLICATE_REF_ID_INDEX |
4-Warning |
<133>CMTS[DOCSIS]:<83000214> Service Change rejected - Duplicate reference-ID or index in message . CM Mac Addr <[enet]> |
CM DSC rejected because duplicate ref ID or index. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_DUPLICATE_REF_ID_INDEX |
4-Warning |
<133>CMTS[DOCSIS]:<83000214> Service Change is rejected - Duplicated reference-ID or index in message. CM MAC addr <[enet]> |
CM DSC is rejected because of duplicated reference ID or index. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_HEADER_SUPPR_SETTING_NOT_SUPPORTED |
4-Warning |
<133>CMTS[DOCSIS]:<83000207> Service Change rejected - Header suppression setting not supported . CM Mac Addr <[enet]> |
Header suppression setting not supported\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_HEADER_SUPPR_SETTING_NOT_SUPPORTED |
4-Warning |
<133>CMTS[DOCSIS]:<83000207> Service Change is rejected - Header suppression setting not supported. CM MAC addr <[enet]> |
Header suppression setting is not supported\n |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_HMAC_AUTHENTICATION_FAILURE |
4-Warning |
<133>CMTS[DOCSIS]:<83000208> Service Change rejected - HMAC Auth Failure. CM Mac Addr <[enet]> |
HMAC Authentication Failure \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_HMAC_AUTHENTICATION_FAILURE |
4-Warning |
<133>CMTS[DOCSIS]:<83000208> Service Change is rejected - HMAC authorization failure. CM MAC addr <[enet]> |
HMAC Authentication Failure \n |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_MAJOR_CLASSIFIER_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83000222> Service Change rejected - Major classifier error. CM Mac Addr <[enet]> |
CM DSC rejected because classifier error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_MAJOR_CLASSIFIER_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83000222> Service Change is rejected - Major classifier error. CM MAC addr <[enet]> |
CM DSC is rejected because major classifier error. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_MAJOR_MULTIPLE_ERRORS |
4-Warning |
<133>CMTS[DOCSIS]:<83000224> Service Change rejected - Multiple major errors. CM Mac Addr <[enet]> |
CM DSC rejected because mulitple errors. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_MAJOR_MULTIPLE_ERRORS |
4-Warning |
<133>CMTS[DOCSIS]:<83000224> Service Change is rejected - Multiple major errors. CM MAC addr <[enet]> |
CM DSC is rejected because of mulitple major errors. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_MAJOR_PHS_RULE_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83000223> Service Change rejected - Major PHS rule error. CM Mac Addr <[enet]> |
CM DSC rejected because PHS rule error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_MAJOR_PHS_RULE_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83000223> Service Change is rejected - Major PHS rule error. CM MAC addr <[enet]> |
CM DSC is rejected because major PHS rule error. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_MAJOR_SRV_FLOW_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83000221> Service Change rejected - Major service flow error. CM Mac Addr <[enet]> |
CM DSC rejected because service flow error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_MAJOR_SRV_FLOW_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83000221> Service Change is rejected - Major service flow error. CM MAC addr <[enet]> |
CM DSC is rejected because service flow error. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_MSG_SYNTAX_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83000225> Service Change rejected - Message syntax error. CM Mac Addr <[enet]> |
CM DSC rejected because message syntax error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_MSG_SYNTAX_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83000225> Service Change is rejected - Message syntax error. CM MAC addr <[enet]> |
CM DSC is rejected because message syntax error. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_MSG_TOO_BIG |
4-Warning |
<133>CMTS[DOCSIS]:<83000226> Service Change rejected - Message too big. CM Mac Addr <[enet]> |
CM DSC rejected because message to big. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_MSG_TOO_BIG |
4-Warning |
<133>CMTS[DOCSIS]:<83000226> Service Change is rejected - Message too big. CM MAC addr <[enet]> |
CM DSC is rejected because message length is too big. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_MULTIPLE_DOWNSTREAM_FLOW |
4-Warning |
<133>CMTS[DOCSIS]:<83000216> Service Change rejected - Multiple downstream flow . CM Mac Addr <[enet]> |
CM DSC rejected because mulitple DS flows. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_MULTIPLE_DOWNSTREAM_FLOW |
4-Warning |
<133>CMTS[DOCSIS]:<83000216> Service Change is rejected - Multiple downstream flow. CM MAC addr <[enet]> |
CM DSC is rejected because of mulitple DS flows. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_MULTIPLE_ERRORS |
4-Warning |
<133>CMTS[DOCSIS]:<83000209> Service Change rejected - Multiple errors . CM Mac Addr <[enet]> |
CM DSC rejected because of mulitple errors. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_MULTIPLE_ERRORS |
4-Warning |
<133>CMTS[DOCSIS]:<83000209> Service Change is rejected - Multiple errors. CM MAC addr <[enet]> |
CM DSC is rejected because mulitple errors have already occurred. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_MULTIPLE_UPSTREAM_FLOW |
4-Warning |
<133>CMTS[DOCSIS]:<83000215> Service Change rejected - Multiple upstream flow . CM Mac Addr <[enet]> |
CM DSC rejected because multiple US flows. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_MULTIPLE_UPSTREAM_FLOW |
4-Warning |
<133>CMTS[DOCSIS]:<83000215> Service Change is rejected - Multiple upstream flow. CM MAC addr <[enet]> |
CM DSC is rejected because of multiple US flows. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_PARAMETER_INVALID_CONTEXT |
4-Warning |
<133>CMTS[DOCSIS]:<83000219> Service Change rejected - Parameter invalid for context. CM Mac Addr <[enet]> |
CM DSC rejected because parameter invalid for context. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_PARAMETER_INVALID_CONTEXT |
4-Warning |
<133>CMTS[DOCSIS]:<83000219> Service Change rejected - Invalid parameter for context. CM MAC addr <[enet]> |
CM DSC rejected because of invalid parameter for context. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_PERMANENT_ADMINISTRATIVE |
4-Warning |
<133>CMTS[DOCSIS]:<83000203> Service Change rejected - Permanent Administrative. CM Mac Addr <[enet]> [chars] |
Permanent Administrative \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_PERMANENT_ADMINISTRATIVE |
4-Warning |
<133>CMTS[DOCSIS]:<83000203> Service Change is rejected - Permanent administrative. CM MAC addr <[enet]> [chars] |
Permanent administrative \n |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_PHS_RULE_ANOTHER_FLOW |
4-Warning |
<133>CMTS[DOCSIS]:<83000218> Service Change rejected - PHS rule for another flow . CM Mac Addr <[enet]> |
CM DSC rejected because PHS rule is for another flow. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_PHS_RULE_ANOTHER_FLOW |
4-Warning |
<133>CMTS[DOCSIS]:<83000218> Service Change is rejected - PHS rule for another flow. CM MAC addr <[enet]> |
CM DSC is rejected because PHS rule is for another flow. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_PHS_RULE_EXISTS |
4-Warning |
<133>CMTS[DOCSIS]:<83000213> Service Change rejected - PHS rule exists. CM Mac Addr <[enet]> |
CM DSC rejected because PHS rule exists. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_PHS_RULE_EXISTS |
4-Warning |
<133>CMTS[DOCSIS]:<83000213> Service Change is rejected - PHS rule exists. CM MAC addr <[enet]> |
CM DSC is rejected because PHS rule exists. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_PHS_RULE_NOT_FOUND |
4-Warning |
<133>CMTS[DOCSIS]:<83000212> Service Change rejected - PHS rule not found . CM Mac Addr <[enet]> |
CM DSC rejected because PHS rule not found. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_PHS_RULE_NOT_FOUND |
4-Warning |
<133>CMTS[DOCSIS]:<83000212> Service Change is rejected - PHS rule not found. CM MAC addr <[enet]> |
CM DSC is rejected because PHS rule can't be found. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_REQUESTOR_NOT_OWNER |
4-Warning |
<133>CMTS[DOCSIS]:<83000204> Service Change rejected - Requestor Not Owner Of Service Flow . CM Mac Addr <[enet]> |
Requestor Not Owner Of Service Flow\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_REQUESTOR_NOT_OWNER |
4-Warning |
<133>CMTS[DOCSIS]:<83000204> Service Change is rejected - Requestor not the owner of service flow. CM MAC addr <[enet]> |
Requestor is not the owner of service flow\n |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_REQUIRED_PARAMETER_NOT_PRESENT |
4-Warning |
<133>CMTS[DOCSIS]:<83000206> Service Change rejected - Required parameter not present. CM Mac Addr <[enet]> |
Required parameter not present\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_REQUIRED_PARAMETER_NOT_PRESENT |
4-Warning |
<133>CMTS[DOCSIS]:<83000206> Service Change is rejected - Required parameter not present. CM MAC addr <[enet]> |
Required parameter is not present\n |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_ABORTED_NO_RSP |
4-Warning |
<133>CMTS[DOCSIS]:<83010201> Service Change aborted - No RSP . CM Mac Addr <[enet]> |
CM DSC aborted due to no response. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_ABORTED_NO_RSP |
4-Warning |
<133>CMTS[DOCSIS]:<83010201> Service Change is aborted - No response. CM MAC addr <[enet]> |
CM DSC is aborted because no response. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_INVALID_TRANSACTION_ID |
4-Warning |
<133>CMTS[DOCSIS]:<83010200> Service Change response rejected - Invalid Transaction ID . CM Mac Addr <[enet]> |
CM DSC response rejected because of an invalid transation ID. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_INVALID_TRANSACTION_ID |
4-Warning |
<133>CMTS[DOCSIS]:<83010200> Service Change Response is rejected - Invalid transaction ID. CM MAC addr <[enet]> |
CM DSC response is rejected because of an invalid transation ID. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_PARAMETER_INVALID_CONTEXT |
4-Warning |
<133>CMTS[DOCSIS]:<83010211> Service Change Response rejected - Invalid parameter for context. CM Mac Addr <[enet]> |
CM DSC RSP rejected because of invalid parameter for context. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_PARAMETER_INVALID_CONTEXT |
4-Warning |
<133>CMTS[DOCSIS]:<83010211> Service Change Response is rejected - Invalid parameter for context. CM MAC addr <[enet]> |
CM DSC response is rejected because of invalid parameter for context. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_REJECT_AUTHORIZATION_FAILURE |
4-Warning |
<133>CMTS[DOCSIS]:<83010202> Service Change Response rejected - HMAC Auth failure. CM Mac Addr <[enet]> |
CM DSA RSP rejected because of an authorization failure. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_REJECT_AUTHORIZATION_FAILURE |
4-Warning |
<133>CMTS[DOCSIS]:<83010202> Service Change Response is rejected - HMAC authorization failure. CM MAC addr <[enet]> |
CM DSA response is rejected because of authorization failure. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_REJECT_DUPLC_REF_ID_OR_INDEX |
4-Warning |
<133>CMTS[DOCSIS]:<83010210>Service Change Response rejected - Duplicated reference-ID or index in message. CM Mac Addr <[enet]> |
CM DSC RSP rejected because duplicate ref ID or index. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_REJECT_DUPLC_REF_ID_OR_INDEX |
4-Warning |
<133>CMTS[DOCSIS]:<83010210>Service Change Response is rejected - Duplicated reference-ID or index in message. CM MAC addr <[enet]> |
CM DSC response is rejected because of duplicated refrence ID or index. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_REJECT_MAJOR_CFR_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83010212> Service Change Response rejected - Major classifier error. CM Mac Addr <[enet]> |
CM DSC RSP rejected because of a major classifier error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_REJECT_MAJOR_CFR_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83010212> Service Change Response is rejected - Major classifier error. CM MAC addr <[enet]> |
CM DSC response is rejected because of a major classifier error. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_REJECT_MAJOR_PHS_RULE_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83010213> Service Change Response rejected - Major PHS rule error. CM Mac Addr <[enet]> |
CM DSC RSP is rejected because of a major PHS error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_REJECT_MAJOR_PHS_RULE_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83010213> Service Change Response is rejected - Major PHS rule error. CM MAC addr <[enet]> |
CM DSC response is rejected because of a major PHS error. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_REJECT_MSG_SYNTAX_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83010203> Service Change Response rejected - Message syntax error. CM Mac Addr <[enet]> |
CM DSC RSP rejected because of a message syntax error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_REJECT_MSG_SYNTAX_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83010203> Service Change Response is rejected - Message syntax error. CM MAC addr <[enet]> |
CM DSC response is rejected because of a message syntax error. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_REJECT_MSG_TOO_BIG |
4-Warning |
<133>CMTS[DOCSIS]:<83010215> Service Change Response rejected - Message too big. CM Mac Addr <[enet]> |
CM DSC RSP rejected becasue the msg was to big. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_REJECT_MSG_TOO_BIG |
4-Warning |
<133>CMTS[DOCSIS]:<83010215> Service Change Response is rejected - Message too big. CM MAC addr <[enet]> |
CM DSC response is rejected because message length was too big. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_REJECT_PHS_RULE_EXISTS |
4-Warning |
<133>CMTS[DOCSIS]:<83010209> Service Change Response rejected - PHS rule exists. CM Mac Addr <[enet]> |
CM DSC RSP rejected because of a major PHS rule error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_REJECT_PHS_RULE_EXISTS |
4-Warning |
<133>CMTS[DOCSIS]:<83010209> Service Change Response is rejected - PHS rule exists. CM MAC addr <[enet]> |
CM DSC response is rejected because of a major PHS rule error. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_REJECT_REQD_PARAM_NOT_PRESENT |
4-Warning |
<133>CMTS[DOCSIS]:<83010206> Service Change Response rejected - Required parameter not present. CM Mac Addr <[enet]> |
CM DSC RSP is rejected because the required parameter is not present. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_REJECT_REQD_PARAM_NOT_PRESENT |
4-Warning |
<133>CMTS[DOCSIS]:<83010206> Service Change Response is rejected - Required parameter not present. CM MAC addr <[enet]> |
CM DSC response is rejected because the required parameter not present. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_UNRECOGNIZED_CONFIGURATION_SETTING |
4-Warning |
<133>CMTS[DOCSIS]:<83010205> Service Change Response rejected - Unrecognized configuration setting. CM Mac Addr <[enet]> |
CM DSC RSP reject because of unrecognized configuration setting. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_RSP_UNRECOGNIZED_CONFIGURATION_SETTING |
4-Warning |
<133>CMTS[DOCSIS]:<83010205> Service Change response is rejected - Unrecognized configuration setting. CM MAC addr <[enet]> |
CM DSC response is rejected because of unrecognized configuration setting. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_SERVICE_FLOW_NOT_FOUND |
4-Warning |
<133>CMTS[DOCSIS]:<83000205> Service Change rejected - Service Flow Not Found. CM Mac Addr <[enet]> |
Service Flow Not Found\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_SERVICE_FLOW_NOT_FOUND |
4-Warning |
<133>CMTS[DOCSIS]:<83000205> Service Change is rejected - Service flow not found. CM MAC addr <[enet]> |
Service flow is not found\n |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_TEMP_DCC |
4-Warning |
<133>CMTS[DOCSIS]:<83000227> Service Change rejected - Temporary DCC . CM Mac Addr <[enet]> |
CM DSC rejected because temp dcc. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_TEMP_NO_RESOURCE |
4-Warning |
<133>CMTS[DOCSIS]:<83000202> Service Change rejected - Temporary no resource. CM Mac Addr <[enet]> [chars] |
CM DSC rejected due to no resource. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_TEMP_NO_RESOURCE |
4-Warning |
<133>CMTS[DOCSIS]:<83000202> Service Change is rejected - Temporary no resource. CM MAC addr <[enet]> [chars] |
CM DSC is rejected because of no resource. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_UNRECOGNIZED_CONFIGURATION_SETTING |
4-Warning |
<133>CMTS[DOCSIS]:<83000201> Service Change Rejected - Unrecognized Configuration Setting. CM Mac Addr <[enet]> |
Unrecognized Configuration Setting \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_UNRECOGNIZED_CONFIGURATION_SETTING |
4-Warning |
<133>CMTS[DOCSIS]:<83000201> Service Change is rejected - Unrecognized configuration setting. CM MAC addr <[enet]> |
Unrecognized configuration setting \n |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_UNSPECIFIED_REASON |
4-Warning |
<133>CMTS[DOCSIS]:<83000200> Service Change rejected - Unspecified reason. CM Mac Addr <[enet]> |
Unspecified reason \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSC_UNSPECIFIED_REASON |
4-Warning |
<133>CMTS[DOCSIS]:<83000200> Service Change is rejected - Unspecified reason. CM MAC addr <[enet]> |
Unspecified reason \n |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSD_HMAC_AUTHENTICATION_FAILURE |
4-Warning |
<133>CMTS[DOCSIS]:<83000303> Service Delete rejected - HMAC Auth Failure. CM Mac Addr <[enet]> |
HMAC Authentication Failure \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSD_HMAC_AUTHENTICATION_FAILURE |
4-Warning |
<133>CMTS[DOCSIS]:<83000303> Service Delete is rejected - HMAC authorization failure. CM MAC addr <[enet]> |
HMAC authentication failure \n |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSD_MSG_SYNTAX_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83000304> Service Delete rejected - Message Syntax Error. CM Mac Addr <[enet]> |
CM DSD rejected becuase of message syntax error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSD_MSG_SYNTAX_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<83000304> Service Delete is rejected - Message syntax error. CM MAC addr <[enet]> |
CM DSD is rejected because of message syntax error. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSD_REQUESTOR_NOT_OWNER |
4-Warning |
<133>CMTS[DOCSIS]:<83000301> Service Delete rejected - Requestor Not Owner of service flow. CM Mac Addr <[enet]> |
Requestor Not Owner\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSD_REQUESTOR_NOT_OWNER |
4-Warning |
<133>CMTS[DOCSIS]:<83000301> Service Delete is rejected - Requestor not the owner of service flow. CM MAC addr <[enet]> |
Requestor is not the owner of service flow\n |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSD_RSP_REJECTED_INVALID_TRANSACTION_ID |
4-Warning |
<133>CMTS[DOCSIS]:<83010300> Service Delete Response rejected - Invalid transaction ID. CM Mac Addr <[enet]> |
DSD Response rejectedinvalid transaction ID\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSD_RSP_REJECTED_INVALID_TRANSACTION_ID |
4-Warning |
<133>CMTS[DOCSIS]:<83010300> Service Delete Response is rejected - Invalid transaction ID. CM MAC addr <[enet]> |
DSD response is rejected because of invalid transaction ID\n |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSD_SERVICE_FLOW_NOT_FOUND |
4-Warning |
<133>CMTS[DOCSIS]:<83000302> Service Delete rejected - Service Flow Not Found. CM Mac Addr <[enet]> |
Service Flow Not Found\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSD_SERVICE_FLOW_NOT_FOUND |
4-Warning |
<133>CMTS[DOCSIS]:<83000302> Service Delete is rejected - Service flow not found. CM MAC addr <[enet]> |
Service flow was not found\n |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSD_UNSPECIFIED_REASON |
4-Warning |
<133>CMTS[DOCSIS]:<83000300> Service Delete rejected - Unspecified reason . CM Mac Addr <[enet]> |
Unspecified reason \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSD_UNSPECIFIED_REASON |
4-Warning |
<133>CMTS[DOCSIS]:<83000300> Service Delete is rejected - Unspecified reason. CM MAC addr <[enet]> |
Unspecified reason \n |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSID_DUPLICATE |
4-Warning |
Duplicate DSID [dec]/[dec]/[dec]: [dec] detected |
Detected an attempt to enqueue a duplicate DSID. SW Bug |
ubr10000 |
"Copy the error message exactly as it appears " "and report it to your technical services representative" |
|
UBR7200-4-DSID_DUPLICATE |
4-Warning |
Duplicate DSID [dec]/[dec]/[dec]: [dec] detected |
Detected an attempt to enqueue a duplicate DSID. SW Bug |
ubr10000 |
"Copy the error message exactly as it appears " "and report it to your technical services representative" |
|
UBR7200-4-DSX_MSG_ERROR |
4-Warning |
CM MAC: [chars] MSG type: [chars] Error code: [dec] MSG: [chars]. |
Received invalid DSX message. |
ubr7200 |
"Please turn on debug to see detailed DSX messages." |
|
UBR7200-4-DSX_MSG_ERROR |
4-Warning |
CM MAC: [chars] MSG type: [chars] Error code: [dec] MSG: [chars]. |
Received invalid DSX message. |
cbr-application |
"Please turn on debug to see more detailed DSX messages." |
|
UBR7200-4-DSX_RESTORE_CFR_STATE_FAILED |
4-Warning |
DSX restore cfr state fail. Attempted to restore state. CM Mac Addr <[enet]> |
DSX restore cfr state fail. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSX_RESTORE_CFR_STATE_FAILED |
4-Warning |
DSX restore classifier state fail when try to restore state. CM MAC addr <[enet]> |
DSX restore classifier state fail. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSX_RESTORE_INVALID_CFRID |
4-Warning |
DSX restore cfr state found invalid cfrid. CM Mac Addr <[enet]> |
DSX restore cfr state found invalid cfrid. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DSX_RESTORE_INVALID_CFRID |
4-Warning |
Invalid classifier ID was found when DSX restore classifier state. CM MAC addr <[enet]> |
DSX restore classifier state because invalid classifier ID was found. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-DUPIPV6_SIDMISMATCH |
4-Warning |
Duplicate IPv6 Address %P in [chars] Sid [dec] MAC:[enet]. Dup Original Sid [dec] |
Duplicate IPv6 Address found with different sid. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DUPIPV6_SIDMISMATCH |
4-Warning |
Duplicate IPv6 Address %P in [chars] Sid [dec] MAC:[enet]. Dup Original Sid [dec] |
Duplicate IPv6 Address found with different sid. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-DUPLICATEMAC |
4-Warning |
Cable modem [enet] is online on both interface [chars] and interface [chars]. |
The cable modem has been detected on two interfaces. |
ubr7200 |
"Check for cable modems with duplicate MAC addresses." |
|
UBR7200-4-DUPLICATEMAC |
4-Warning |
Cable modem [enet] is online on both interface [chars] and interface [chars]. |
The cable modem has been detected on two interfaces. |
ubr7200 |
"Check for cable modems with duplicate MAC addresses." |
|
UBR7200-4-ENVM_PS_OVERLOAD |
4-Warning |
Power supply may be overloaded to support the line card installed in slot [dec] |
The power supply may be insufficient to support the number of line \n\ cards installed in the system under certain operation conditions \n\ like high temperature and high voltage margining. |
- |
"Upgrade the power supply as soon as possible or the system may \n\ fail to operation properly under some certain operation conditions." |
|
UBR7200-4-ENVM_PS_OVERLOAD |
4-Warning |
Power supply may be overloaded to support the line card installed in slot [dec] |
The power supply may be insufficient to support the number of line \n\ cards installed in the system under certain operation conditions \n\ like high temperature and high voltage margining. |
- |
"Upgrade the power supply as soon as possible or the system may \n\ fail to operation properly under some certain operation conditions." |
|
UBR7200-4-FAILED_DS_SID_LOOKUP |
4-Warning |
Failed to find host in DS on int [chars] with SID # [dec] IP = [inet] MAC = [enet] |
Failed to process Lease-Query response for host |
ubr7200 |
"Check if host is provisioned on dhcp server." |
|
UBR7200-4-GRD_UNAVAIL |
4-Warning |
Unable to reach Card [dec]/[dec] for Modular-host services |
The Guardian card is down or the IPC to the Guardian card is down |
ubr10000 |
"Make sure the card selected to be Modular-host is " "operational or change the relevant Modular-host config to" "use an operational card." |
|
UBR7200-4-GRD_UNAVAIL |
4-Warning |
Unable to reach Card [dec]/[dec] for Modular-host services |
The Guardian card is down or the IPC to the Guardian card is down |
ubr10000 |
"Make sure the card selected to be Modular-host is " "operational or change the relevant Modular-host config to" "use an operational card." |
|
UBR7200-4-HEADER_SUPPRESSION_SETTING_NOT_SUPPORTED |
4-Warning |
<133>CMTS[DOCSIS]:<73020105> REG REQ rejected Header suppression setting not supported. CM Mac Addr <[enet]> |
Header suppression setting not supported\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-HEADER_SUPPRESSION_SETTING_NOT_SUPPORTED |
4-Warning |
<133>CMTS[DOCSIS]:<73020105> REG REQ rejected Header suppression setting not supported. CM Mac Addr <[enet]> |
Header suppression setting not supported\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-INVALID_COS_CONFIGURATION |
4-Warning |
<133>CMTS[DOCSIS]:<73010900> Bad Class of Service- Invalid Configuration. CM Mac Addr <[enet]> |
Registration Failed Bad Class of Service\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-INVALID_COS_CONFIGURATION |
4-Warning |
<133>CMTS[DOCSIS]:<73010900> Bad Class of Service- Invalid Configuration. CM Mac Addr <[enet]> |
Registration Failed Bad Class of Service\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-INVALID_MAX_DOWNSTREAM_BIT_FORMAT |
4-Warning |
<133>CMTS[DOCSIS]:<73011200> Bad Max DS bit - Invalid format. CM Mac Addr <[enet]> |
Registration Failed Bad Max Downstream bit has invalid format.\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-INVALID_MAX_DOWNSTREAM_BIT_FORMAT |
4-Warning |
<133>CMTS[DOCSIS]:<73011200> Bad Max DS bit - Invalid format. CM Mac Addr <[enet]> |
Registration Failed Bad Max Downstream bit has invalid format.\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-INVALID_MAX_UPSTREAM_BIT_FORMAT |
4-Warning |
<133>CMTS[DOCSIS]:<73011300> Bad Max US Bit - Invalid format. CM Mac Addr <[enet]> |
Registration Failed Bad Max Upstream bit Rate has invalid format.\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-INVALID_MAX_UPSTREAM_BIT_FORMAT |
4-Warning |
<133>CMTS[DOCSIS]:<73011300> Bad Max US Bit - Invalid format. CM Mac Addr <[enet]> |
Registration Failed Bad Max Upstream bit Rate has invalid format.\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-INVALID_MAX_UPSTREAM_BURST_FORMAT |
4-Warning |
<133>CMTS[DOCSIS]:<73011600> Bad Max US CH Transmit Burst Configuration setting - Invalid format. CM Mac Addr <[enet]> |
CM Max US channel transmit burst type invalid format. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-INVALID_MAX_UPSTREAM_BURST_FORMAT |
4-Warning |
<133>CMTS[DOCSIS]:<73011600> Bad Max US CH Transmit Burst Configuration setting - Invalid format. CM Mac Addr <[enet]> |
CM Max US channel transmit burst type invalid format. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-INVALID_MIN_UPSTREAM_CHANNEL_BIT_RATE_FORMAT |
4-Warning |
<133>CMTS[DOCSIS]:<73011500> Bad Guaranteed MIN US Channel bit Rate Configuration setting - Invalid format. CM Mac Addr <[enet]> |
Guaranteed Minimum Upstream Rate format invalid. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-INVALID_MIN_UPSTREAM_CHANNEL_BIT_RATE_FORMAT |
4-Warning |
<133>CMTS[DOCSIS]:<73011500> Bad Guaranteed MIN US Channel bit Rate Configuration setting - Invalid format. CM Mac Addr <[enet]> |
Guaranteed Minimum Upstream Rate format invalid. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-INVALID_MODEM_CONFIGURATION_SETTING_FORMAT |
4-Warning |
<133>CMTS[DOCSIS]:<73011700> Invalid Modem Capabilities configuration setting . CM Mac Addr <[enet]> |
CM Capabilities config value contains an invalid format. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-INVALID_MODEM_CONFIGURATION_SETTING_FORMAT |
4-Warning |
<133>CMTS[DOCSIS]:<73011700> Invalid Modem Capabilities configuration setting . CM Mac Addr <[enet]> |
CM Capabilities config value contains an invalid format. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-INVALID_SID |
4-Warning |
<133>CMTS[DOCSIS]:<73010200> REG REQ has Invalid SID or not in use. CM Mac Addr <[enet]> |
REG REQ has Invalid SID or not in use\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-INVALID_SID |
4-Warning |
<133>CMTS[DOCSIS]:<73010200> REG REQ has Invalid SID or not in use. CM Mac Addr <[enet]> |
REG REQ has Invalid SID or not in use\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-INVALID_UNASSIGNED_UPSTREAM_CHANNEL |
4-Warning |
<133>CMTS[DOCSIS]:<73010600> Bad US CH - Invalid or Unassigned. CM Mac Addr <[enet]> |
REG REQ : Bad US CH - Invalid or Unassigned.\n |
ubr7200 |
"Please Check the upstream Channel Frequency" |
|
UBR7200-4-INVALID_UNASSIGNED_UPSTREAM_CHANNEL |
4-Warning |
<133>CMTS[DOCSIS]:<73010600> Bad US CH - Invalid or Unassigned. CM Mac Addr <[enet]> |
REG REQ : Bad US CH - Invalid or Unassigned.\n |
ubr7200 |
"Please Check the upstream Channel Frequency" |
|
UBR7200-4-INVALID_UPSTREAM_PRIORITY_FORMAT |
4-Warning |
<133>CMTS[DOCSIS]:<73011400> Bad US Priority Configuration - Invalid format. CM Mac Addr <[enet]> |
Registration Failed Upstream Priority Format has invalid format. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-INVALID_UPSTREAM_PRIORITY_FORMAT |
4-Warning |
<133>CMTS[DOCSIS]:<73011400> Bad US Priority Configuration - Invalid format. CM Mac Addr <[enet]> |
Registration Failed Upstream Priority Format has invalid format. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-IPDR_CPETYPE_ENQ_ERR |
4-Warning |
Enqueue error for CPETYPE event. [chars] Q size [dec] |
Too many IPDR CPETYPE events generated in a moment |
ubr10000 |
"If there are a lot of memory leaks" " do PRE switchover." |
|
UBR7200-4-L2VPN_CMIM_ERROR |
4-Warning |
ERROR: CM [enet] [chars] Top Level CMIM TLV does not exclude eCM |
Top Level CMIM TLV does not exclude eCM |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_CMIM_ERROR |
4-Warning |
ERROR: CM [enet] [chars] Top Level CMIM TLV does not exclude eCM |
Top Level CMIM TLV does not exclude eCM |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_DS_CFR_VPNID_ERROR |
4-Warning |
ERROR: CM [enet] [chars] Matching TopLevel L2VPNID not found for DS-CFR |
Matching TopLevel L2VPNID not found for DS-CFR |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_DS_CFR_VPNID_ERROR |
4-Warning |
ERROR: CM [enet] [chars] Matching TopLevel L2VPNID not found for DS-CFR |
Matching TopLevel L2VPNID not found for DS-CFR |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_DUPLICATE_VLANID_ERROR |
4-Warning |
ERROR: CM [enet] [chars] Multiple L2VPN TLV with same vlanid at top level |
Multiple L2VPN TLV with same vlanid at top level |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_DUPLICATE_VLANID_ERROR |
4-Warning |
ERROR: CM [enet] [chars] Multiple L2VPN TLV with same vlanid at top level |
Multiple L2VPN TLV with same vlanid at top level |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_ERROR_BPI_NOT_ENABLED |
4-Warning |
L2VPN enabled without enabling BPI+ or 1.0 CM [enet] [chars] |
Encryption not enabled for L2VPN CM |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_ERROR_BPI_NOT_ENABLED |
4-Warning |
L2VPN enabled without enabling BPI+ or 1.0 CM [enet] [chars] |
Encryption not enabled for L2VPN CM |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_MPLS_BKUP_DISABLE_CFG_ERR |
4-Warning |
ERROR: CM [enet] [chars] Bkup disable delay and never disable bkup both configured |
Both TLVs cannot be configured |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_MPLS_BKUP_DISABLE_CFG_ERR |
4-Warning |
ERROR: CM [enet] [chars] Bkup disable delay and never disable bkup both configured |
Both TLVs cannot be configured |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_MPLS_BKUP_EXCEEDED |
4-Warning |
ERROR: CM [enet] [chars] Too many backup peers |
Too many backup peers |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_MPLS_BKUP_EXCEEDED |
4-Warning |
ERROR: CM [enet] [chars] Too many backup peers |
Too many backup peers |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_MPLS_BKUP_PRIO_ERR |
4-Warning |
ERROR: CM [enet] [chars] Incorect or missing priority for backup peer |
Priority incorrect or missing for backup peer |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_MPLS_BKUP_PRIO_ERR |
4-Warning |
ERROR: CM [enet] [chars] Incorect or missing priority for backup peer |
Priority incorrect or missing for backup peer |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_MPLS_PWTYPE_ERROR |
4-Warning |
ERROR: CM [enet] [chars] MPLS PW TYPE TLV invalid at top level |
MPLS PW TYPE TLV invalid at top level |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_MPLS_PWTYPE_ERROR |
4-Warning |
ERROR: CM [enet] [chars] MPLS PW TYPE TLV invalid at top level |
MPLS PW TYPE TLV invalid at top level |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_MPLSPEER_ERROR |
4-Warning |
ERROR: CM [enet] [chars] MPLS PEER IPADDR TLV invalid at top level |
MPLS PEER IPADDR TLV invalid at top level |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_MPLSPEER_ERROR |
4-Warning |
ERROR: CM [enet] [chars] MPLS PEER IPADDR TLV invalid at top level |
MPLS PEER IPADDR TLV invalid at top level |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_MPLSPEERNAME_LEN_ERROR |
4-Warning |
ERROR: CM [enet] [chars] MPLSPEERNAME TLV length invalid |
MPLSPEERNAME TLV length invalid |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_MPLSPEERNAME_LEN_ERROR |
4-Warning |
ERROR: CM [enet] [chars] MPLSPEERNAME TLV length invalid |
MPLSPEERNAME TLV length invalid |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_MULTIPLE_VPNID_ERROR |
4-Warning |
ERROR: CM [enet] [chars] Multiple L2VPN TLV with same vpnid at top level |
Multiple L2VPN TLV with same vpnid at top level |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_MULTIPLE_VPNID_ERROR |
4-Warning |
ERROR: CM [enet] [chars] Multiple L2VPN TLV with same vpnid at top level |
Multiple L2VPN TLV with same vpnid at top level |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_NSI_DUPLICATE_ERROR |
4-Warning |
ERROR: CM [enet] [chars] VLANID and MPLSPEER TLV both present at top level |
VLANID and MPLSPEER TLV both present at top level |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_NSI_DUPLICATE_ERROR |
4-Warning |
ERROR: CM [enet] [chars] VLANID and MPLSPEER TLV both present at top level |
VLANID and MPLSPEER TLV both present at top level |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_NSI_MISSING_ERROR |
4-Warning |
ERROR: CM [enet] [chars] VLANID or MPLSPEER TLV missing at top level |
VLANID or MPLSPEER TLV missing at top level |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_NSI_MISSING_ERROR |
4-Warning |
ERROR: CM [enet] [chars] VLANID or MPLSPEER TLV missing at top level |
VLANID or MPLSPEER TLV missing at top level |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_TLVERR |
4-Warning |
L2VPN XCONNECT PW Cable Modem CM config file TLV Error. |
L2VPN XCONNECT PW TLV Error VCID or SAII or TAII not valid |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_TLVERR |
4-Warning |
L2VPN XCONNECT PW Cable Modem CM config file TLV Error. |
L2VPN XCONNECT PW TLV Error VCID or SAII or TAII not valid |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_US_SFLOW_VPNID_ERROR |
4-Warning |
ERROR: CM [enet] [chars] Matching TopLevel L2VPNID not found for US-SF |
Matching TopLevel L2VPNID not found for US-SF |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_US_SFLOW_VPNID_ERROR |
4-Warning |
ERROR: CM [enet] [chars] Matching TopLevel L2VPNID not found for US-SF |
Matching TopLevel L2VPNID not found for US-SF |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_VCID_OR_TAII_SAII_MISSING_ERROR |
4-Warning |
ERROR: CM [enet] [chars] VCID or TAII & SAII TLV missing or out-of-range |
VCID or TAII & SAII TLV missing or out-of-range |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_VCID_OR_TAII_SAII_MISSING_ERROR |
4-Warning |
ERROR: CM [enet] [chars] VCID or TAII & SAII TLV missing or out-of-range |
VCID or TAII & SAII TLV missing or out-of-range |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_VPNID_MISSING_ERROR |
4-Warning |
ERROR: CM [enet] [chars] VPNID TLV missing at top level |
VPNID TLV missing at top level |
cmts-application |
"Check CM config file" |
|
UBR7200-4-L2VPN_VPNID_MISSING_ERROR |
4-Warning |
ERROR: CM [enet] [chars] VPNID TLV missing at top level |
VPNID TLV missing at top level |
cmts-application |
"Check CM config file" |
|
UBR7200-4-LB_CM_LIST_DUP_ENTRY |
4-Warning |
CM [enet] on CM List 0x[hec] group [dec] |
Duplicate entry in cm list exists. No Operational Impact. |
loadbalance |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-LB_CM_LIST_DUP_ENTRY |
4-Warning |
Duplicated CM [enet] in CM List 0x[hec] group [dec] |
Duplicated entries in CM lists. No operational impact. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-LB_CM_LIST_MISMATCH_ENTRY |
4-Warning |
CM [enet] on CM List 0x[hec] group [dec] action [dec] |
Entry in CM list seen at different position than expected . There is no operational impact |
loadbalance |
"Please copy the error message exactly as it appears on the console or in the " "system log contact your technical support representativeand provide the " "representative with the gathered information. " |
|
UBR7200-4-LB_CM_LIST_MISMATCH_ENTRY |
4-Warning |
CM [enet] on CM List 0x[hec] group [dec] action [dec] not matched the |
Entry in CM list seen at different position than expected . There is no operational impact |
cbr-application |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-4-LB_CM_WITH_INVALID_GROUP_ID |
4-Warning |
The CM [enet] MD [chars] LBLoad Balance group [dec] is not found in load balance database |
The CM is assigned to an invalid load-balance group. No operational impact. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-LB_COUNT_OUT_OF_RANGE |
4-Warning |
Grp [dec] MD [chars] [chars] Chan [dec] CM [enet] [chars] Counter Out of Range value [dec] New State [chars] Old [dec] Skip Reason [chars] |
LB modem counter decrements out of range. |
loadbalance |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-LB_COUNT_OUT_OF_RANGE |
4-Warning |
LBLoad Balance Counter out of range: group [dec] MD [chars] [chars] chan [dec] CM [enet] |
LB modem counter is out of decrements range. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-4-LOCAL_MTU_LESS_THAN_REMOTE_MTU |
4-Warning |
Local MTU [dec] is lower than remote MTU [dec] PW cannot come up. |
Local MTU is lower than remote MTU PW cannot come up |
cmts-application |
"Check the peer MTU" |
|
UBR7200-4-MACBLKSIZE |
4-Warning |
Unknown MAC address block size. |
Data stored in midplane is bad or incomplete. |
ubr7200 |
"Contact technical support to update your system." |
|
UBR7200-4-MACBLKSIZE |
4-Warning |
Unknown MAC address block size. |
Data stored in midplane is bad or incomplete. |
ubr7200 |
"Contact technical support to update your system." |
|
UBR7200-4-MCAST_ADMISSION_CONTROL_FAILURE |
4-Warning |
Multicast Service flow creation failed - group [chars] source [chars] host Interface [chars] |
service flow creation failure due to admission control check. |
ubr7200 |
"Adjust the min-rate parameter mentioned" " as part of the service class" |
|
UBR7200-4-MCAST_ADMISSION_CONTROL_FAILURE |
4-Warning |
Multicast Service flow creation failed - group [chars] source [chars] host Interface [chars] |
service flow creation failure due to admission control check. |
cbr-application |
"Adjust the min-rate parameter mentioned" " as part of the service class" |
|
UBR7200-4-MCAST_DB_MAX_LIMIT_REACHED |
4-Warning |
Multicast DB full new entry not created - max [dec] group [chars] source [chars] fwd Interface [chars] bundle [chars] |
Multicast explicit tracking DB entry creation failed due to max limit reached |
ubr7200 |
"Reduce Static IGMP multicast config or wait for" "Dynamic IGMP OR PCMM multicast clients to leave" |
|
UBR7200-4-MCAST_DB_MAX_LIMIT_REACHED |
4-Warning |
Multicast DB full new entry not created - max [dec] group [chars] source [chars] fwd Interface [chars] bundle [chars] |
Multicast explicit tracking DB entry creation failed due to max limit reached |
cbr-application |
"Reduce Static IGMP multicast config or wait for" "Dynamic IGMP OR PCMM multicast clients to leave" |
|
UBR7200-4-MCAST_DBC_FAILED_BLOCKED_CM |
4-Warning |
CM [enet] failed to join [chars] [chars] on Interface [chars] [chars] due |
Multicast DBC failed for the CM because of system busy or too high channel change rate for the CM. |
ubr7200 |
"Lower channel change rate for the" "CM or check whether system CPU are too busy." |
|
UBR7200-4-MCAST_SID_MAX_LIMIT_REACHED |
4-Warning |
Multicast SID full new entry not created - max [dec] Bundle Interface [chars] |
Multicast sid allocation failed due to max mcast sid limit reached |
cbr-application |
"Remove multicast qos or " "change single mqos to aggregate mqos" |
|
UBR7200-4-METERING_NOFILESYS_SFLOG |
4-Warning |
No file system [chars] can be used for sflog file. |
Cannot find a suitable file system to store sflog file. |
ubr7200 |
"Please check whether tmp disk" " is ready or full." |
|
UBR7200-4-MIN_UPSTREAM_CHANNEL_BIT_RATE_EXCEEDS_MAX |
4-Warning |
<133>CMTS[DOCSIS]:<73011501> Bad Guaranteed Min US Channel Bit Rate Configuration setting - Exceed Max US Bit Rate. CM Mac Addr <[enet]> |
CM MIN Upstream Channel Bit Rate exceeds maximum value. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-MIN_UPSTREAM_CHANNEL_BIT_RATE_EXCEEDS_MAX |
4-Warning |
<133>CMTS[DOCSIS]:<73011501> Bad Guaranteed Min US Channel Bit Rate Configuration setting - Exceed Max US Bit Rate. CM Mac Addr <[enet]> |
CM MIN Upstream Channel Bit Rate exceeds maximum value. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-MIN_UPSTREAM_CHANNEL_BITRATE_OUT_OF_RANGE |
4-Warning |
<133>CMTS[DOCSIS]:<73011502> Bad Guaranteed Min US CH Bit rate Configuration setting - Out of Range. CM Mac Addr <[enet]> |
REG REQ : Bad Guaranteed Min US CH Bit rate Configuration setting - Out of Range.\n |
ubr7200 |
"Check the Config File Parameters" |
|
UBR7200-4-MIN_UPSTREAM_CHANNEL_BITRATE_OUT_OF_RANGE |
4-Warning |
<133>CMTS[DOCSIS]:<73011502> Bad Guaranteed Min US CH Bit rate Configuration setting - Out of Range. CM Mac Addr <[enet]> |
REG REQ : Bad Guaranteed Min US CH Bit rate Configuration setting - Out of Range.\n |
ubr7200 |
"Check the Config File Parameters" |
|
UBR7200-4-MISMATCH_BP_CONFIGURATION_SETTING_VALUE |
4-Warning |
<132>CMTS[DOCSIS]: Misconfigured BPI Setting: gracetime Type [dec] is longer than 50%% of lifetime. CM MAC Addr <[enet]> |
Misconfigured BPI Configuration Setting Value \n |
ubr7200 |
"Please inspect the configuration file" |
|
UBR7200-4-MISMATCH_BP_CONFIGURATION_SETTING_VALUE |
4-Warning |
<132>CMTS[DOCSIS]: Misconfigured BPI Setting: gracetime Type [dec] is longer than 50%% of lifetime. CM MAC Addr <[enet]> |
Misconfigured BPI Configuration Setting Value \n |
ubr7200 |
"Please inspect the configuration file" |
|
UBR7200-4-MISMATCH_BP_REVOCATION_TIMEOUT_VALUE |
4-Warning |
<132>CMTS[DOCSIS]: Misconfigured BPI Setting: [chars] Type [dec] is longer than revocation timeout value. CM MAC Addr <[enet]> |
Misconfigured BPI Configuration Setting Value \n |
ubr7200 |
"Please inspect the configuration file" |
|
UBR7200-4-MISMATCH_BP_REVOCATION_TIMEOUT_VALUE |
4-Warning |
<132>CMTS[DOCSIS]: Misconfigured BPI Setting: [chars] Type [dec] is longer than revocation timeout value. CM MAC Addr <[enet]> |
Misconfigured BPI Configuration Setting Value \n |
ubr7200 |
"Please inspect the configuration file" |
|
UBR7200-4-MTA_REQ_ON_NON_HA_DS |
4-Warning |
MTA Modem [enet] in [chars] to come online on a non-HA capable DS |
CMTS can not move the MTA to a DS that is HA capable after 3 trials |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-MTA_REQ_ON_NON_HA_DS |
4-Warning |
MTA Modem [enet] in [chars] to come online on a non-HA capable DS |
CMTS can not move the MTA to a DS that is HA capable after 3 trials |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-NB_MCAST_BPI_EXCEED_WAR |
4-Warning |
[[chars] [chars]] BPI:More than [dec] mcast sessions joined for CM [enet] ignored |
NB mcast BPI warning \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-NO_RANGING_REQUESTS |
4-Warning |
<133>CMTS[DOCSIS]:<82010100> No Ranging Requests received from POLLED CM Mac Addr <[enet]> CMTS generated polls |
No Ranging Requests received from POLLED CM CMTS generated polls\n |
ubr7200 |
"Please look for possible noise or other RF plant " "problems on the upstream channel" |
|
UBR7200-4-NO_RANGING_REQUESTS |
4-Warning |
<133>CMTS[DOCSIS]:<82010100> No Ranging Requests received from POLLED CM Mac Addr <[enet]> CMTS generated polls |
No Ranging Requests received from POLLED CM CMTS generated polls\n |
ubr7200 |
"Please look for possible noise or other RF plant " "problems on the upstream channel" |
|
UBR7200-4-NO_RNG_REQ_TIMEOUT_SID |
4-Warning |
<133>CMTS[DOCSIS]:<82010400> Failed to receive Periodic RNG-REQ from modem [chars] timing-out SID |
Failed to receive Periodic RNG-REQ from modem SID X timing-out SID\n |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-NO_RNG_REQ_TIMEOUT_SID |
4-Warning |
<133>CMTS[DOCSIS]:<82010400> Failed to receive Periodic RNG-REQ from modem [chars] timing-out SID |
Failed to receive Periodic RNG-REQ from modem SID X timing-out SID\n |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-NOCFGFILE |
4-Warning |
Cannot read modem config file [chars] from [inet]: [chars] |
Configuration file for the cable modem cannot be read |
ubr7200 |
"Make sure the config file is accesable to the CMTS" |
|
UBR7200-4-NOCFGFILE |
4-Warning |
Cannot read modem config file [chars] from [inet]: [chars] |
Configuration file for the cable modem cannot be read |
ubr7200 |
"Make sure the config file is accesable to the CMTS" |
|
UBR7200-4-NOCFGFILE_V6 |
4-Warning |
Cannot read modem config file [chars] from %P: [chars] |
Configuration file for the cable modem cannot be read |
ubr7200 |
"Make sure the config file is accesable to the CMTS" |
|
UBR7200-4-NOCFGFILE_V6 |
4-Warning |
Cannot read modem config file [chars] from %P: [chars] |
Configuration file for the cable modem cannot be read |
ubr7200 |
"Make sure the config file is accesable to the CMTS" |
|
UBR7200-4-NOCPUVER |
4-Warning |
Invalid CPU ID assuming revision 1 |
CPU Revision ID is unreadable. |
ubr7200 |
"Update CPU board." |
|
UBR7200-4-NOCPUVER |
4-Warning |
Invalid CPU ID assuming revision 1 |
CPU Revision ID is unreadable. |
ubr7200 |
"Update CPU board." |
|
UBR7200-4-NOTLEARNABLE |
4-Warning |
New CPE [enet] behind modem [enet] on interface [chars] is ignored: [chars]. Count [dec] |
The CPE is not learnable due to provisioning. |
ubr7200 |
"Provisioning failure. Please check configuration" |
|
UBR7200-4-NOTLEARNABLE |
4-Warning |
New address of CPE [enet] behind modem [enet] on interface [chars] is ignored: [chars]. Count [dec] |
The CPE is not learnable due to provisioning. |
ubr7200 |
"Provisioning failure. Please check configuration" |
|
UBR7200-4-NUMIPV6ADDR_ERR |
4-Warning |
DECODE of HCCP TLV for IPV6 has incorrect number of IPv6 addresses = [dec] |
\nFailure in encoding of number of IPV6 addrs TLV in HCCPmessage |
ubr7200 |
"Check the clients on the CM for number of IPv6 addresses" |
|
UBR7200-4-OACKERROR |
4-Warning |
TFTP Option Negotiation Error for [chars] file at [inet]: [chars] |
TFTP OACK packet is malformed or wrong options appended |
ubr7200 |
"Make sure TFTP Server supports TFTP Options" |
|
UBR7200-4-OACKERROR |
4-Warning |
TFTP Option Negotiation Error for [chars] file at [inet]: [chars] |
TFTP OACK packet is malformed or wrong options appended |
ubr7200 |
"Make sure TFTP Server supports TFTP Options" |
|
UBR7200-4-OACKERROR_V6 |
4-Warning |
TFTP Option Negotiation Error for [chars] file at %P: [chars] |
TFTP OACK packet is malformed or wrong options appended |
ubr7200 |
"Make sure TFTP Server supports TFTP Options" |
|
UBR7200-4-OACKERROR_V6 |
4-Warning |
TFTP Option Negotiation Error for [chars] file at %P: [chars] |
TFTP OACK packet is malformed or wrong options appended |
ubr7200 |
"Make sure TFTP Server supports TFTP Options" |
|
UBR7200-4-OCSP_NOT_RESPONDING |
4-Warning |
<132>CMTS[DOCSIS]:<66030401> Failed to retrieve OCSP status |
OCSP not available\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-OCSP_NOT_RESPONDING |
4-Warning |
<132>CMTS[DOCSIS]:<66030401> Failed to retrieve OCSP status |
OCSP not available\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-OUT_OF_RANGE_CONFIG_FILE_PARAMETERS |
4-Warning |
<133>CMTS[DOCSIS]:<73011800> Configuration file contains parameter with the value outside of the range. CM Mac Addr <[enet]> |
CM config file parameter contains an out of range parameter. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-OUT_OF_RANGE_CONFIG_FILE_PARAMETERS |
4-Warning |
<133>CMTS[DOCSIS]:<73011800> Configuration file contains parameter with the value outside of the range. CM Mac Addr <[enet]> |
CM config file parameter contains an out of range parameter. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-OUT_OF_RANGE_MAX_UPSTREAM_BURST |
4-Warning |
<133>CMTS[DOCSIS]:<73011601> Bad Max US CH Transmit Burst Configuration setting - Out of Range. CM Mac Addr <[enet]> |
CM Max US channel transmit burst setting out of range. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-OUT_OF_RANGE_MAX_UPSTREAM_BURST |
4-Warning |
<133>CMTS[DOCSIS]:<73011601> Bad Max US CH Transmit Burst Configuration setting - Out of Range. CM Mac Addr <[enet]> |
CM Max US channel transmit burst setting out of range. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-OUT_OF_RANGE_US_PRIORITY_CONFIGURATION |
4-Warning |
<133>CMTS[DOCSIS]:<73011401> Bad US Priority Configuration - Setting out of Range. CM Mac Addr <[enet]> |
Out of Range US Traffic Priority Value. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-OUT_OF_RANGE_US_PRIORITY_CONFIGURATION |
4-Warning |
<133>CMTS[DOCSIS]:<73011401> Bad US Priority Configuration - Setting out of Range. CM Mac Addr <[enet]> |
Out of Range US Traffic Priority Value. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-OVERLAP_IPV4 |
4-Warning |
MAC [enet] on interface [chars] SID [dec] attempting to use [inet]. This address is already in use by MAC [enet] on interface [chars] SID [dec] |
There might be an IPv4 spoofing attempt going on. |
ubr7200 |
"Look for possible spoofing attempt" |
|
UBR7200-4-OVERLAP_IPV6 |
4-Warning |
MAC [enet] on interface [chars] SID [dec] attempting to use %P. This address is already in use by MAC [enet] on interface [chars] SID [dec] |
There might be an IPv6 spoofing attempt going on. |
ubr7200 |
"Look for possible spoofing attempt" |
|
UBR7200-4-OVERLAPIP |
4-Warning |
Interface [chars] IP address [inet] %P from MAC [enet] is already in use on [chars]. SID = [dec] |
There might be a spoofing attempt going on. |
ubr7200 |
"Look for possible spoofing attempt" |
|
UBR7200-4-OVERLAPIP_CM |
4-Warning |
Interface [chars] IP address [inet] %P assigned to CM [enet] has been reassigned. |
There might be DHCP server configuration error. |
ubr7200 |
"Check DHCP server configuration" |
|
UBR7200-4-OVERLAPIP_CM_CPE |
4-Warning |
Interface [chars] SID [dec] IP address [inet] %P assigned to CM [enet] is being reassigned to its CPE [enet]. |
There might be DHCP server configuration error. |
ubr7200 |
"Check DHCP server configuration" |
|
UBR7200-4-PHS_ERROR |
4-Warning |
CM MAC: [chars] PHS_ERROR Param code: [dec] Confirm code: [dec] |
Looks like issue with PHS header |
ubr7200 |
"Please look for DOCSIS message logs followed for more details" |
|
UBR7200-4-PHS_ERROR |
4-Warning |
CM MAC: [chars] PHS_ERROR Param code: [dec] Confirm code: [dec] |
Looks like issue with PHS header |
ubr7200 |
"Please look for DOCSIS message logs followed for more details" |
|
UBR7200-4-RECALLED_NPE |
4-Warning |
Old version NPE-175/225 with Rev = 0x%02x system controller. Contact upgrades-info@cisco.com for replacement |
NPE board has been recalled due to an errata in the system controller chip. |
ubr7200 |
"Replace NPE-175/225 Board" |
|
UBR7200-4-RECALLED_NPE |
4-Warning |
Old version NPE-175/225 with Rev = 0x%02x system controller. Contact upgrades-info@cisco.com for replacement |
NPE board has been recalled due to an errata in the system controller chip. |
ubr7200 |
"Replace NPE-175/225 Board" |
|
UBR7200-4-REG_ACK_REJ_BAD_RCC |
4-Warning |
<133>CMTS[DOCSIS]:<73030208> REG ACK rejected bad rcc. CM Mac Addr <[enet]> |
CM Reg Ack message bad rcc. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_ACK_REJ_BAD_RCC |
4-Warning |
<133>CMTS[DOCSIS]:<73030208> REG ACK rejected bad rcc. CM Mac Addr <[enet]> |
CM Reg Ack message bad rcc. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_ACK_REJ_MSG_SYNTAX_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<73030300> REG ACK rejected message syntax error. CM Mac Addr <[enet]> |
CM Reg Ack message syntax error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_ACK_REJ_MSG_SYNTAX_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<73030300> REG ACK rejected message syntax error. CM Mac Addr <[enet]> |
CM Reg Ack message syntax error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_ACK_REJ_UNSPECIFIED |
4-Warning |
<133>CMTS[DOCSIS]:<73030200> REG ACK rejected unspecified reason. CM Mac Addr <[enet]> |
CM Reg Ack message rejected. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_ACK_REJ_UNSPECIFIED |
4-Warning |
<133>CMTS[DOCSIS]:<73030200> REG ACK rejected unspecified reason. CM Mac Addr <[enet]> |
CM Reg Ack message rejected. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REJ_AUTH_FAIL_CMTS_MIC_INVALID |
4-Warning |
<133>CMTS[DOCSIS]:<73000500> Registration rejected authentication failure: CMTS MIC invalid. CM Mac Addr <[enet]> |
Registration rejected authentication failure: CMTS MIC invalid\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REJ_AUTH_FAIL_CMTS_MIC_INVALID |
4-Warning |
<133>CMTS[DOCSIS]:<73000500> Registration rejected authentication failure: CMTS MIC invalid. CM Mac Addr <[enet]> |
Registration rejected authentication failure: CMTS MIC invalid\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REJ_AUTH_FAIL_TLV_PARAMS_MISMATCH |
4-Warning |
<133>CMTS[DOCSIS]:<73000501>Registration authentication failure: REG REQ rejected TLV parameters do not match learned config file TLV parameters. CM Mac Addr <[enet]> |
REG REQ TLV parameters do not match learned config fileTLV parameters\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REJ_AUTH_FAIL_TLV_PARAMS_MISMATCH |
4-Warning |
<133>CMTS[DOCSIS]:<73000501>Registration authentication failure: REG REQ rejected TLV parameters do not match learned config file TLV parameters. CM Mac Addr <[enet]> |
REG REQ TLV parameters do not match learned config fileTLV parameters\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_AUTH_FAILURE |
4-Warning |
<133>CMTS[DOCSIS]:<73020109> REG REQ rejected - Authorization failure . CM Mac Addr <[enet]> |
CM Registration Request Authorization failure. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_AUTH_FAILURE |
4-Warning |
<133>CMTS[DOCSIS]:<73020109> REG REQ rejected - Authorization failure . CM Mac Addr <[enet]> |
CM Registration Request Authorization failure. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_DS_SELECTION_FAIL |
4-Warning |
DS Selection failed for Cable Modem [enet] in [chars] |
CMTS cannot proceed with handling modem's Registration Request |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_DS_SELECTION_FAIL |
4-Warning |
DS Selection failed for Cable Modem [enet] in [chars] |
CMTS cannot proceed with handling modem's Registration Request |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_DUPLICATE_REF_ID_INDEX |
4-Warning |
<133>CMTS[DOCSIS]:<73020107> REG REQ rejected duplicate reference-ID or index in message . CM Mac Addr <[enet]> |
CM Registration Request message contains a duplicate ID or index. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_DUPLICATE_REF_ID_INDEX |
4-Warning |
<133>CMTS[DOCSIS]:<73020107> REG REQ rejected duplicate reference-ID or index in message . CM Mac Addr <[enet]> |
CM Registration Request message contains a duplicate ID or index. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_INVALID_MAC_HEADER |
4-Warning |
<133>CMTS[DOCSIS]:<73010100> REG REQ has Invalid MAC header. CM Mac Addr <[enet]> |
REG REQ has Invalid MAC header \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_INVALID_MAC_HEADER |
4-Warning |
<133>CMTS[DOCSIS]:<73010100> REG REQ has Invalid MAC header. CM Mac Addr <[enet]> |
REG REQ has Invalid MAC header \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_MAJOR_CLASSIFIER_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<73020111> REG REQ rejected - Major classifier error . CM Mac Addr <[enet]> |
CM Registration Request classifier error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_MAJOR_CLASSIFIER_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<73020111> REG REQ rejected - Major classifier error . CM Mac Addr <[enet]> |
CM Registration Request classifier error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_MAJOR_MULTIPLE_ERRORS |
4-Warning |
<133>CMTS[DOCSIS]:<73020113> REG REQ rejected - Multiple major errors. CM Mac Addr <[enet]> |
CM Registration Request mulitiple errors. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_MAJOR_MULTIPLE_ERRORS |
4-Warning |
<133>CMTS[DOCSIS]:<73020113> REG REQ rejected - Multiple major errors. CM Mac Addr <[enet]> |
CM Registration Request mulitiple errors. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_MAJOR_PHS_RULE_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<73020112> REG REQ rejected - Major PHS rule error . CM Mac Addr <[enet]> |
CM Registration Request PHS rule error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_MAJOR_PHS_RULE_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<73020112> REG REQ rejected - Major PHS rule error . CM Mac Addr <[enet]> |
CM Registration Request PHS rule error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_MAJOR_SRV_FLOW_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<73020110> REG REQ rejected - Major service flow error . CM Mac Addr <[enet]> |
CM Registration Request service flow error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_MAJOR_SRV_FLOW_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<73020110> REG REQ rejected - Major service flow error . CM Mac Addr <[enet]> |
CM Registration Request service flow error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_MSG_SYNTAX_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<73020114> REG REQ rejected - Message syntax error . CM Mac Addr <[enet]> |
CM Registration Request syntax error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_MSG_SYNTAX_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<73020114> REG REQ rejected - Message syntax error . CM Mac Addr <[enet]> |
CM Registration Request syntax error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_MSG_TOO_BIG |
4-Warning |
<133>CMTS[DOCSIS]:<73020116> REG REQ rejected - Message too big. CM Mac Addr <[enet]> |
CM Registration Request message to large. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_MSG_TOO_BIG |
4-Warning |
<133>CMTS[DOCSIS]:<73020116> REG REQ rejected - Message too big. CM Mac Addr <[enet]> |
CM Registration Request message to large. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_MULTIPLE_ERRORS |
4-Warning |
<133>CMTS[DOCSIS]:<73020106> REG REQ rejected - Multiple errors. CM Mac Addr <[enet]> |
CM Registration Request msg contains multile errors. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_MULTIPLE_ERRORS |
4-Warning |
<133>CMTS[DOCSIS]:<73020106> REG REQ rejected - Multiple errors. CM Mac Addr <[enet]> |
CM Registration Request msg contains multile errors. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_PARAM_INVALID |
4-Warning |
<133>CMTS[DOCSIS]:<73020108> REG REQ rejected parameter invalid for context. CM Mac Addr <[enet]> |
CM Registration Request conatins a invalide parameter for context. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_PARAM_INVALID |
4-Warning |
<133>CMTS[DOCSIS]:<73020108> REG REQ rejected parameter invalid for context. CM Mac Addr <[enet]> |
CM Registration Request conatins a invalide parameter for context. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_PERMANENT_ADMINISTRATIVE |
4-Warning |
<133>CMTS[DOCSIS]:<73020103> REG REQ rejected - Permanent administrative . CM Mac Addr <[enet]> |
REG REQ rejected - Permanent administrative. \n |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-REG_REQ_PERMANENT_ADMINISTRATIVE |
4-Warning |
<133>CMTS[DOCSIS]:<73020103> REG REQ rejected - Permanent administrative . CM Mac Addr <[enet]> |
REG REQ rejected - Permanent administrative. \n |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-4-REG_REQ_PRIM_SRV_FLOW_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<73020115> REG REQ rejected - Primary service flow error. CM Mac Addr <[enet]> |
CM Registration Request primary service flow error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_PRIM_SRV_FLOW_ERROR |
4-Warning |
<133>CMTS[DOCSIS]:<73020115> REG REQ rejected - Primary service flow error. CM Mac Addr <[enet]> |
CM Registration Request primary service flow error. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_TEMPORARY_NO_RESOURCE |
4-Warning |
<133>CMTS[DOCSIS]:<73020102> REG REQ rejected - temporary no resource . CM Mac Addr <[enet]> |
REG REQ rejected - temporary no resource . \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_TEMPORARY_NO_RESOURCE |
4-Warning |
<133>CMTS[DOCSIS]:<73020102> REG REQ rejected - temporary no resource . CM Mac Addr <[enet]> |
REG REQ rejected - temporary no resource . \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_UNRECOGNIZED_CONFIGURATION_SETTING |
4-Warning |
<133>CMTS[DOCSIS]:<73020101> REG REQ rejected - Unrecognized configuration setting. CM Mac Addr <[enet]> |
REG REQ rejected - Unrecognized configuration setting . \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REG_REQ_UNRECOGNIZED_CONFIGURATION_SETTING |
4-Warning |
<133>CMTS[DOCSIS]:<73020101> REG REQ rejected - Unrecognized configuration setting. CM Mac Addr <[enet]> |
REG REQ rejected - Unrecognized configuration setting . \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REGISTRATION_ABORT_NO_REG_ACK |
4-Warning |
<133>CMTS[DOCSIS]:<73030100> REG aborted no REG-ACK. CM Mac Addr <[enet]> |
CM Reg aborted. No CM REG_ACK message. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REGISTRATION_ABORT_NO_REG_ACK |
4-Warning |
<133>CMTS[DOCSIS]:<73030100> REG aborted no REG-ACK. CM Mac Addr <[enet]> |
CM Reg aborted. No CM REG_ACK message. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REGISTRATION_BEFORE_TFTP |
4-Warning |
Registration request unexpected: Cable Modem did not attempt TFTP. Registration Rejected. CM Mac Addr <[enet]> |
Registration request unexpected: Cable Modem did not attempt TFTP\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REGISTRATION_BEFORE_TFTP |
4-Warning |
Registration request unexpected: Cable Modem did not attempt TFTP. Registration Rejected. CM Mac Addr <[enet]> |
Registration request unexpected: Cable Modem did not attempt TFTP\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REGISTRATION_BEFORE_TFTP_MARK |
4-Warning |
Registration request unexpected: Cable Modem did not attempt TFTP. Modem marked with #. CM Mac Addr <[enet]> |
Registration request unexpected: Cable Modem did not attempt TFTP\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REGISTRATION_BEFORE_TFTP_MARK |
4-Warning |
Registration request unexpected: Cable Modem did not attempt TFTP. Modem marked with #. CM Mac Addr <[enet]> |
Registration request unexpected: Cable Modem did not attempt TFTP\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REMOTE_BACKUP_MTU_NOT_EQL_PRIMARY |
4-Warning |
Remote backup MTU [dec] is not equal to primary [dec] cannot set up the backup PW |
Remote backup MTU is not equal to primary |
cmts-application |
"Keep same mtu for the primary peer and secondary peer" |
|
UBR7200-4-REQUIRED_PARAMETER_NOT_PRESENT |
4-Warning |
<133>CMTS[DOCSIS]:<73020104> REG REQ rejected Required parameter not present. CM Mac Addr <[enet]> |
Required parameter not present\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REQUIRED_PARAMETER_NOT_PRESENT |
4-Warning |
<133>CMTS[DOCSIS]:<73020104> REG REQ rejected Required parameter not present. CM Mac Addr <[enet]> |
Required parameter not present\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REQUIRED_TLV_ABSENT |
4-Warning |
<133>CMTS[DOCSIS]:<73010400> REG REQ missed Required TLV's. CM Mac Addr <[enet]> |
REG REQ missed Required TLV's \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-REQUIRED_TLV_ABSENT |
4-Warning |
<133>CMTS[DOCSIS]:<73010400> REG REQ missed Required TLV's. CM Mac Addr <[enet]> |
REG REQ missed Required TLV's \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-RETRIES_EXHAUSTED_POLL_CM |
4-Warning |
<133>CMTS[DOCSIS]:<82010200> Retries exhausted for polled CM Mac Addr <[enet]>. After 16 R101.0 errors. |
Retries exhausted for polled CM . After 16 R101.0 errors.Note: this is different from R102.0 in that it was able to try i.e. got REQ's but failed to Range properly.\n |
ubr7200 |
"Please look for possible noise or other RF plant " "problems on the upstream channel" |
|
UBR7200-4-RETRIES_EXHAUSTED_POLL_CM |
4-Warning |
<133>CMTS[DOCSIS]:<82010200> Retries exhausted for polled CM Mac Addr <[enet]>. After 16 R101.0 errors. |
Retries exhausted for polled CM . After 16 R101.0 errors.Note: this is different from R102.0 in that it was able to try i.e. got REQ's but failed to Range properly.\n |
ubr7200 |
"Please look for possible noise or other RF plant " "problems on the upstream channel" |
|
UBR7200-4-SERVICE_FLOW_ERROR |
4-Warning |
CM MAC: [chars] Service flow direction: [chars] Param code: [dec] Confirm code: [dec] |
Looks like issue while admitting/activating Service flow |
ubr7200 |
"Please look for DOCSIS message logs followed for more details" |
|
UBR7200-4-SERVICE_FLOW_ERROR |
4-Warning |
CM MAC: [chars] Service flow direction: [chars] Param code: [dec] Confirm code: [dec] |
Looks like issue while admitting/activating Service flow |
ubr7200 |
"Please look for DOCSIS message logs followed for more details" |
|
UBR7200-4-SERVICE_FLOW_INDEX_ERROR |
4-Warning |
[chars] [dec]/[dec] nb_unique_index: [dec] SFID: [dec] index: [dec] flow-chid: [dec] wb-mode: [dec] dsid: [dec] cm [enet] |
Looks like issue while allocating remote downstream index |
ubr7200 |
"Please see show cable modem pri and " "show int cx/y/z service-flow for more details" |
|
UBR7200-4-SERVICE_FLOW_INDEX_ERROR |
4-Warning |
[chars] [dec]/[dec] nb_unique_index: [dec] SFID: [dec] index: [dec] flow-chid: [dec] wb-mode: [dec] dsid: [dec] cm [enet] |
Looks like issue while allocating remote downstream index |
ubr7200 |
"Please see show cable modem pri and " "show int cx/y/z service-flow for more details" |
|
UBR7200-4-SERVICE_FLOW_ZERO_BLAZE_INDEX_ERROR |
4-Warning |
spa_num: [dec] spa_if_num: [dec] nb_unique_index: [dec] lc_slot: [dec] lc_subslot: [dec] SFID: [dec] Blaze index: [dec] |
Looks like issue while allocating remote downstream blaze index |
ubr7200 |
"Please see show cable modem and " "show int cx/y/z service-flow for more details" |
|
UBR7200-4-SERVICE_FLOW_ZERO_BLAZE_INDEX_ERROR |
4-Warning |
spa_num: [dec] spa_if_num: [dec] nb_unique_index: [dec] lc_slot: [dec] lc_subslot: [dec] SFID: [dec] Blaze index: [dec] |
Looks like issue while allocating remote downstream blaze index |
ubr7200 |
"Please see show cable modem and " "show int cx/y/z service-flow for more details" |
|
UBR7200-4-SERVICE_PERMANENTLY_UNAVAILABLE |
4-Warning |
<133>CMTS[DOCSIS]:<73000403> Service unavailable - Permanent. CM Mac Addr <[enet]> |
Service Permanently unavailable\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-SERVICE_PERMANENTLY_UNAVAILABLE |
4-Warning |
<133>CMTS[DOCSIS]:<73000403> Service unavailable - Permanent. CM Mac Addr <[enet]> |
Service Permanently unavailable\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-SERVICE_TEMPORARILY_UNAVAILABLE |
4-Warning |
<133>CMTS[DOCSIS]:<73000402> Service unavailable - Temporarily unavailable. CM Mac Addr <[enet]> |
Registration Failed Service temporarily not available \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-SERVICE_TEMPORARILY_UNAVAILABLE |
4-Warning |
<133>CMTS[DOCSIS]:<73000402> Service unavailable - Temporarily unavailable. CM Mac Addr <[enet]> |
Registration Failed Service temporarily not available \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-SERVICE_UNAVAIL_OTHER |
4-Warning |
<133>CMTS[DOCSIS]:<73000400> Service unavailable - Other. CM Mac Addr <[enet]> |
Registration Failed :Service Unavailable \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-SERVICE_UNAVAIL_OTHER |
4-Warning |
<133>CMTS[DOCSIS]:<73000400> Service unavailable - Other. CM Mac Addr <[enet]> |
Registration Failed :Service Unavailable \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-SIDERRORDCC |
4-Warning |
Tried to allocate new SID [dec] during DCC CM rebuild for interface [chars]: CM [enet]: SID container info: start [dec] end [dec] |
Allocate SID during DCC CM rebuild |
cbr-application |
"Assign Cable Modem to another interface" |
|
UBR7200-4-SIDWITHOUTCM |
4-Warning |
SID [dec] not bound to any CM. |
This SID does not have a valid CM database pointer |
ubr7200 |
"For Informational Purposes Only" |
|
UBR7200-4-SIDWITHOUTCM |
4-Warning |
SID [dec] not bound to any CM. |
This SID does not have a valid CM database pointer |
ubr7200 |
"NO action is required" |
|
UBR7200-4-SPECMGMTGRP |
4-Warning |
Spectrum group [dec] with discrete frequency is not fully supported on interface [chars] |
The spectrum management group is not fully supported |
ubr7200 |
"Suggest convert discrete frequency to frequency band in the group" |
|
UBR7200-4-SPECMGMTGRP |
4-Warning |
Spectrum group [dec] with discrete frequency is not fully supported on interface [chars] |
The spectrum management group is not fully supported |
ubr7200 |
"Suggest convert discrete frequency to frequency band in the group" |
|
UBR7200-4-STALE_IPV4_DB_FOUND |
4-Warning |
When update IPv4 DB entry for [enet] to ip [inet] tableid [dec] Found stale entry for [inet] tableid [dec] is cm [dec] mac [enet] |
Subscriber IPv4 DB entry for CM have not been cleaned |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-SUBDB_CLEANUP_CM |
4-Warning |
Free all Subscriber DB entries for CM [enet] hwidb [chars] ip [inet] tableid [dec] prim sid [dec] sidp %p |
Subscriber DB entries for CM have not been cleaned previously clean them now. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-TEMPLATE_LKUP_ERROR |
4-Warning |
CM MAC: [enet] Sid: [dec] Act_Qos: [dec] |
Problem while looking up qos template |
ubr7200 |
"LOG_STD_SH_TECH_ACTION" |
|
UBR7200-4-TEMPLATE_LKUP_ERROR |
4-Warning |
CM MAC: [enet] Sid: [dec] Act_Qos: [dec] |
Problem while looking up qos template |
ubr7200 |
"LOG_STD_SH_TECH_ACTION" |
|
UBR7200-4-TFTP_DATA_LEN_ERROR |
4-Warning |
The length of TFTP DATA packet exceeded negotiated/default block size of [dec] while downloading [chars] from [inet] |
TFTP DATA packet received exceeded its negotiated/default block size |
ubr7200 |
"Make sure that the block size of the TFTP DATA packets" "does not exceed the negotiated/default block size" |
|
UBR7200-4-TFTP_DATA_LEN_ERROR |
4-Warning |
The length of TFTP DATA packet exceeded negotiated/default block size of [dec] while downloading [chars] from [inet] |
TFTP DATA packet received exceeded its negotiated/default block size |
ubr7200 |
"Make sure that the block size of the TFTP DATA packets" "does not exceed the negotiated/default block size" |
|
UBR7200-4-TLV56_CONFLICT_CHANNEL_SET |
4-Warning |
Confilct with TLV56 and channel set. Either remove TLV56 from the CM config file or adjust the power plant. CM Mac Addr <[enet]> may go offline due to high power. |
Registration Failed Check TLV56 Configuration Setting\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-TLV56_CONFLICT_CHANNEL_SET |
4-Warning |
Confilct with TLV56 and channel set. Either remove TLV56 from the CM config file or adjust the power plant. CM Mac Addr <[enet]> may go offline due to high power. |
Registration Failed Check TLV56 Configuration Setting\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-UCC_RSP_NOT_RCV_ON_CHANNEL_ID |
4-Warning |
<133>CMTS[DOCSIS]:<67010100> UCC-RSP not received on previous channel ID. CM Mac Addr <[enet]> |
- |
ubr7200 |
"Connect DOCSIS compliant Cable Modem" |
|
UBR7200-4-UCC_RSP_NOT_RCV_ON_CHANNEL_ID |
4-Warning |
<133>CMTS[DOCSIS]:<67010100> UCC-RSP was not received on previous channel ID. CM MAC addr <[enet]> |
- |
cbr-application |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-4-UCC_RSP_RCV_INVALID_CHANNEL_ID |
4-Warning |
<133>CMTS[DOCSIS]:<67010200> UCC-RSP received with invalid channel ID. CM Mac Addr <[enet]> |
- |
ubr7200 |
"Enable <cmdBold>debug cable ucc<noCmdBold> at CMTS " "and make sure that CMTS sends UCC-REQ with correct " "channel ID. If CMTS is not sending the correct " "channel ID report the problem" |
|
UBR7200-4-UCC_RSP_RCV_INVALID_CHANNEL_ID |
4-Warning |
<133>CMTS[DOCSIS]:<67010200> UCC-RSP was received with invalid channel ID. CM MAC addr <[enet]> |
- |
cbr-application |
"Enable <cmdBold>debug cable ucc<noCmdBold> at CMTS " "and make sure that CMTS sends UCC-REQ with correct " "channel ID. If CMTS is not sending the correct " "channel ID report the problem" |
|
UBR7200-4-UCC_RSP_RCV_INVALID_CHANNEL_ID_NEW |
4-Warning |
<133>CMTS[DOCSIS]:<67010300> UCC-RSP received with invalid channel ID on new channel. CM Mac Addr <[enet]> |
- |
ubr7200 |
"Connect DOCSIS compliant Cable Modem" |
|
UBR7200-4-UCC_RSP_RCV_INVALID_CHANNEL_ID_NEW |
4-Warning |
<133>CMTS[DOCSIS]:<67010300> UCC-RSP was received with invalid channel ID on new channel. CM MAC addr <[enet]> |
- |
cbr-application |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-4-UNABLE_TO_RANGE_CM |
4-Warning |
<133>CMTS[DOCSIS]:<82010300> Unable to Successfully Range CM Mac Addr <[enet]>. Retries Exhausted. |
Unable to Successfully Range CM Retries Exhausted.\n |
ubr7200 |
"CM reinitialize its MAC interface and attempt to reregister." " check the cable plant for potentialnoise or other RF problems" " Check the configuration of the cable interface on the CMTS " " that is servicing this cable modem to ensure that the interface" " is enabled and properly configured" |
|
UBR7200-4-UNABLE_TO_RANGE_CM |
4-Warning |
<133>CMTS[DOCSIS]:<82010300> Unable to Successfully Range CM Mac Addr <[enet]>. Retries Exhausted. |
Unable to Successfully Range CM Retries Exhausted.\n |
ubr7200 |
"CM reinitialize its MAC interface and attempt to reregister." " check the cable plant for potentialnoise or other RF problems" " Check the configuration of the cable interface on the CMTS " " that is servicing this cable modem to ensure that the interface" " is enabled and properly configured" |
|
UBR7200-4-UNKNOWNSID |
4-Warning |
SID cannot be resolved from the leasequery reply for IP [inet]\n interface [chars] mac [enet] sid [dec] for DHCPACK |
Relay-agent option might not be configured. |
ubr7200 |
"Make sure relay-agent option is configured. Also " "make sure save-relay-agent-data is enabled on CNR." |
|
UBR7200-4-UNRECOGNIZED_CONFIGURATION_SETTING |
4-Warning |
<133>CMTS[DOCSIS]:<73000401> Service unavailable - Unrecognized configuration setting. CM Mac Addr <[enet]> |
Registration Failed Unrecognized Configuration Setting\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-UNRECOGNIZED_CONFIGURATION_SETTING |
4-Warning |
<133>CMTS[DOCSIS]:<73000401> Service unavailable - Unrecognized configuration setting. CM Mac Addr <[enet]> |
Registration Failed Unrecognized Configuration Setting\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-UNSPECIFIED_REASON |
4-Warning |
<133>CMTS[DOCSIS]:<73020100> REG REQ rejected Unspecified Reason . CM Mac Addr <[enet]> |
Unspecified Reason \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-UNSPECIFIED_REASON |
4-Warning |
<133>CMTS[DOCSIS]:<73020100> REG REQ rejected Unspecified Reason . CM Mac Addr <[enet]> |
Unspecified Reason \n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-UPSTREAM_CHANNEL_CHANGE_WITH_REG_REQ |
4-Warning |
<133>CMTS[DOCSIS]:<73010601> Bad US CH -Change followed with RE- Registration REQ. CM Mac Addr <[enet]> |
REG REQ : Bad US CH -Change followed with RE- Registration REQ .\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-UPSTREAM_CHANNEL_CHANGE_WITH_REG_REQ |
4-Warning |
<133>CMTS[DOCSIS]:<73010601> Bad US CH -Change followed with RE- Registration REQ. CM Mac Addr <[enet]> |
REG REQ : Bad US CH -Change followed with RE- Registration REQ .\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-4-VERSION_MISMATCH |
4-Warning |
Midplane data version mismatch. |
Data stored in midplane is out of date and needs update. |
ubr7200 |
"Contact technical support to update your system." |
|
UBR7200-4-VERSION_MISMATCH |
4-Warning |
Midplane data version mismatch. |
Data stored in midplane is out of date and needs update. |
ubr7200 |
"Contact technical support to update your system." |
|
UBR7200-5-ATTRIBUTE_CHANGE_CONFLICT |
5-Notice |
<133>CMTS[DOCSIS]:<75010100> Attribute Masks for SF SFID %lu do not |
Change in provisioned attribute mask causes mismatch |
ubr10000 |
"Modify provisioned attributes such that it meets " "requirements" |
|
UBR7200-5-ATTRIBUTE_CHANGE_CONFLICT |
5-Notice |
<133>CMTS[DOCSIS]:<75010100> Attribute Masks for SF SFID %lu do not |
Change in provisioned attribute mask causes mismatch |
ubr10000 |
"Modify provisioned attributes such that it meets " "requirements" |
|
UBR7200-5-AUTHFAIL |
5-Notice |
Authentication failed for Cable Modem [enet] on interface [chars][chars] |
The registration of this modem failed due to an invalid MIC string or use of stale/spoofed tftp config file information by the modem |
ubr7200 |
"Make sure the shared secret in the configuration file " "matches the shared secret configured in the ubr7200. " "If the shared secrets match take action against the modem that is " "possibly spoofing storing and replaying its old config file." |
|
UBR7200-5-BADMNCSMSG |
5-Notice |
Invalid DOCSIS Message Type [dec] received from the CM [enet] for interface [chars] |
- |
- |
- |
|
UBR7200-5-BADMNCSMSG |
5-Notice |
Invalid DOCSIS Message Type [dec] received from the CM [enet] for interface [chars] |
- |
- |
- |
|
UBR7200-5-BPKMDROPEXCESS |
5-Notice |
CMTS deleted excessive [chars] Requests Cable Modem [enet] with Sid [dec] |
Cable Modem did excessive BPKM requests. |
ubr7200 |
"Check modem interface configuration for privacy mandatory " "or noise on the plant." |
|
UBR7200-5-BPKMDROPEXCESS |
5-Notice |
CMTS deleted excessive [chars] Requests Cable Modem [enet] with Sid [dec] |
Cable Modem did excessive BPKM requests. |
ubr7200 |
"Check modem interface configuration for privacy mandatory " "or noise on the plant." |
|
UBR7200-5-CLASSFAIL |
5-Notice |
Registration failed for Cable Modem [enet] on interface [chars][chars]: [chars] |
The registration of this modem failed due to an invalid or unsupported Class of Service setting. |
ubr7200 |
"Make sure the Class of Service fields in the configuration file " "are set correctly." |
|
UBR7200-5-CLASSFAIL |
5-Notice |
Registration failed for Cable Modem [enet] on interface [chars][chars]: [chars] |
The registration of this modem failed due to an invalid or unsupported Class of Service setting. |
ubr7200 |
"Make sure the Class of Service fields in the configuration file " "are set correctly." |
|
UBR7200-5-CLEAR_ARP_INTERFACE |
5-Notice |
Clearing all ARP entries for interface [chars] |
All the entries have been cleared |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-CLEAR_ARP_INTERFACE |
5-Notice |
Clearing all ARP entries for interface [chars] |
All the entries have been cleared |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-CLEAR_ARP_TABLE |
5-Notice |
Clearing all ARP entries |
All the entries have been cleared |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-CLEAR_ARP_TABLE |
5-Notice |
Clearing all ARP entries |
All the entries have been cleared |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-CLONED_CM_DETECTED |
5-Notice |
Cloned CM with MAC address [enet] connection attempt rejected on [chars] U[dec] |
There might be a hacking attempt going on. |
ubr7200 |
"Look for possible hacking attempt" |
|
UBR7200-5-CLONED_CM_DETECTED |
5-Notice |
Cloned CM with MAC address [enet] connection attempt rejected on [chars] U[dec] |
There might be a hacking attempt going on. |
ubr7200 |
"Look for possible hacking attempt" |
|
UBR7200-5-DBDSPRECOVER1 |
5-Notice |
Trying to switch to backup dsp image |
Trying to recover DSP using backup image |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-DBDSPRECOVER1 |
5-Notice |
Trying to switch to backup dsp image |
Trying to recover DSP using backup image |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-DBDSPRECOVER2 |
5-Notice |
Switching to backup dsp image succeeded |
Switching to backup dsp image succeeded |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-DBDSPRECOVER2 |
5-Notice |
Switching to backup dsp image succeeded |
Switching to backup dsp image succeeded |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-DBDSPRECOVER3 |
5-Notice |
Recovering and switching back to regular dsp image succeeded |
DSP recover operation using backup image succeeded |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-DBDSPRECOVER3 |
5-Notice |
Recovering and switching back to regular dsp image succeeded |
DSP recover operation using backup image succeeded |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-DBDSPUP |
5-Notice |
Handshake DSP is successful after [dec] ms delay |
DSP is up and running |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-DBDSPUP |
5-Notice |
Handshake DSP is successful after [dec] ms delay |
DSP is up and running |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-DIAG_LOG_LOW_THRSHLD_REACHED |
5-Notice |
[DOCSIS]:<86000200>Docs Diag Log reaches low threshold |
Docs Diag Log Notification :log size reaches low threshold |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-5-DIAG_LOG_LOW_THRSHLD_REACHED |
5-Notice |
[DOCSIS]:<86000200>Docs Diag Log reaches low threshold |
Docs Diag Log Notification :log size reaches low threshold |
ubr7200 |
"LOG_STD_NO_ACTION" |
|
UBR7200-5-EAEREJECT |
5-Notice |
EAE registration rejected CM [enet] on Interface [chars] |
CM registration rejected to force EAE policy. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-EAEREJECT |
5-Notice |
EAE registration rejected CM [enet] on Interface [chars] |
CM registration rejected to force EAE policy. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-EXCESSIVE_SAV_GROUP_IDS |
5-Notice |
More than 1 SAV Group ID in registration request for CM MAC <[enet]>. Ignoring the excessive group ids |
There may be more than 1 SAV Group IDs specified in the in the configuration file\n |
ubr7200 |
"Please inspect the configuration file" |
|
UBR7200-5-EXCESSIVE_SAV_GROUP_IDS |
5-Notice |
More than 1 SAV Group ID in registration request for CM MAC <[enet]>. Ignoring the excessive group ids |
There may be more than 1 SAV Group IDs specified in the in the configuration file\n |
ubr7200 |
"Please inspect the configuration file" |
|
UBR7200-5-EXCESSIVE_SAV_PREFIXES |
5-Notice |
More than [dec] SAV prefixes in the registration request for CM MAC <[enet]>. Ignoring the excessive prefixes |
There are excessive number of SAV prefixes in the configuration file\n |
ubr7200 |
"Please inspect the configuration file" |
|
UBR7200-5-EXCESSIVE_SAV_PREFIXES |
5-Notice |
More than [dec] SAV prefixes in the registration request for CM MAC <[enet]>. Ignoring the excessive prefixes |
There are excessive number of SAV prefixes in the configuration file\n |
ubr7200 |
"Please inspect the configuration file" |
|
UBR7200-5-EXPIREDBPITIMEOUT |
5-Notice |
CMTS deleted BPI [chars] expired Cable Modem [enet] with Sid [dec] |
Expired cable modem deleted to enforce CM go through BPI authorization. |
ubr7200 |
"Check modem interface configuration for privacy mandatory " "or noise on the plant." |
|
UBR7200-5-EXPIREDBPITIMEOUT |
5-Notice |
CMTS deleted BPI [chars] expired Cable Modem [enet] with Sid [dec] |
Expired cable modem deleted to enforce CM go through BPI authorization. |
ubr7200 |
"Check modem interface configuration for privacy mandatory " "or noise on the plant." |
|
UBR7200-5-KEEPALIVE |
5-Notice |
Keepalive shutting down interface [chars]. |
No activity detected within the Keepalive timeout period on the interface. |
ubr7200 |
"Check RF path for failure." |
|
UBR7200-5-KEEPALIVE |
5-Notice |
Keepalive shutting down interface [chars]. |
No activity detected within the Keepalive timeout period on the interface. |
ubr7200 |
"Check RF path for failure." |
|
UBR7200-5-MACTSSLDERR |
5-Notice |
CMTS MAC TGC load pulse error sync-pulse interval [dec] |
MAC FPGA TGC load pulse generation error |
ubr7200 |
"Replace defective Line Card" |
|
UBR7200-5-MACTSSLDERR |
5-Notice |
CMTS MAC TGC load pulse error sync-pulse interval [dec] |
MAC FPGA TGC load pulse generation error |
ubr7200 |
"Replace defective Line Card" |
|
UBR7200-5-MALFORMED_MODEM_TLV |
5-Notice |
PARSER-ERR: Next TLV type=[dec] steps beyond end of TLV block.\n\t |
Malformed TLV found in parsing\n |
ubr7200 |
"Please check if the modem's behavior is correct" |
|
UBR7200-5-MALFORMED_MODEM_TLV |
5-Notice |
PARSER-ERR: Next TLV type=[dec] steps beyond end of TLV block.\n\t |
Malformed TLV found in parsing\n |
ubr7200 |
"Please check if the modem's behavior is correct" |
|
UBR7200-5-MAXCPE_IP |
5-Notice |
Interface [chars] CPE IPs [dec] Max CPE IPs [dec] over limit. New host with MAC [enet] on SID [dec] CM [enet] is ignored. |
- |
- |
- |
|
UBR7200-5-MAXHOST |
5-Notice |
Interface [chars] New host with IP address [inet] and MAC [enet] on SID [dec] CM [enet] is ignored in [chars] path. |
- |
- |
- |
|
UBR7200-5-MAXHOST |
5-Notice |
Interface [chars] New host with MAC [enet] on SID [dec] CM [enet] is ignored: [chars]. Count [dec] |
- |
- |
- |
|
UBR7200-5-NOMULTIPLEUPSTREAMS |
5-Notice |
Upstream Channel Change not valid for interface [chars] |
The software does not support this command for this interface |
ubr7200 |
"Please use this command on a multiple upstream Line card" |
|
UBR7200-5-NOMULTIPLEUPSTREAMS |
5-Notice |
Upstream Channel Change not valid for interface [chars] |
The software does not support this command for this interface |
ubr7200 |
"Please use this command on a multiple upstream Line card" |
|
UBR7200-5-NOTIMPLMENTEDMNCSMSG |
5-Notice |
Not implemented DOCSIS MESSAGE received from a Cable Modem\n for interface [chars] |
This uBR does not support this type of message. The system may be connected to a non-compliant modem. |
ubr7200 |
"This message is informational only. To be sure there is no problem " "you may contact technical support." |
|
UBR7200-5-OVERLIMIT |
5-Notice |
Interface [chars]\n Current total reservation of [dec] bps on Port U[dec] exceeds its\n maximum configured reservation limit of [dec] bps.\n |
The currently reserved capacity on the upstream channel\n already exceeds the virtual reservation capacity of that\n upstream channel based on configured subscription level limit.\n |
ubr7200 |
"Need to load balance modems requesting reserved upstream rate on\n" "some other upstream channel or increase the subscription level\n" "limit on current upstream channel at increasing risk of not being\n" "able to guarantee the individual reserved rates for modems if this\n" "upstream channel is already oversubscribed beyond raw capacity\n" |
|
UBR7200-5-OVERLIMIT |
5-Notice |
Interface [chars]\n Current total reservation of [dec] bps on Port U[dec] exceeds its\n maximum configured reservation limit of [dec] bps.\n |
The currently reserved capacity on the upstream channel\n already exceeds the virtual reservation capacity of that\n upstream channel based on configured subscription level limit.\n |
ubr7200 |
"Need to load balance modems requesting reserved upstream rate on\n" "some other upstream channel or increase the subscription level\n" "limit on current upstream channel at increasing risk of not being\n" "able to guarantee the individual reserved rates for modems if this\n" "upstream channel is already oversubscribed beyond raw capacity\n" |
|
UBR7200-5-TEKREQTIMEOUT |
5-Notice |
CMTS deleted BPI Cable Modem [enet] because traffic not encrypted |
Cable modem deleted to force modem to request TEK. |
ubr7200 |
"Check upsteam utilization to ensure bandwidth available for TEK " "request. Noise on the plant can cause this also." |
|
UBR7200-5-TEKREQTIMEOUT |
5-Notice |
CMTS deleted BPI Cable Modem [enet] because traffic not encrypted |
Cable modem deleted to force modem to request TEK. |
ubr7200 |
"Check upsteam utilization to ensure bandwidth available for TEK " "request. Noise on the plant can cause this also." |
|
UBR7200-5-TIMESCH |
5-Notice |
Time scheduled event spectrum group [dec] [chars] |
A time scheduled reconfiguration event occurred on an interface. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-TIMESCH |
5-Notice |
Time scheduled event spectrum group [dec] [chars] |
A time scheduled reconfiguration event occurred on an interface. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-TRAFSHAPBADTIMER |
5-Notice |
Bad timer expiry in downstream traffic shaper process Timer [hec] |
An unknown downstream traffic shaper timer has expired. |
ubr7200 |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR7200-5-TRAFSHAPBADTIMER |
5-Notice |
Bad timer expiry in downstream traffic shaper process Timer [hec] |
An unknown downstream traffic shaper timer has expired. |
ubr7200 |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR7200-5-TRAFSHAPNOCREAT |
5-Notice |
Unable to create downstream traffic shaping queues |
A possible memory error has occurred which is preventing the software from creating downstream traffic shapping queues. |
ubr7200 |
"Gather information about running configuration and amount of memory " "in the system and report it to your technical support representative." |
|
UBR7200-5-TRAFSHAPNOCREAT |
5-Notice |
Unable to create downstream traffic shaping queues |
A possible memory error has occurred which is preventing the software from creating downstream traffic shapping queues. |
ubr7200 |
"Gather information about running configuration and amount of memory " "in the system and report it to your technical support representative." |
|
UBR7200-5-TRAFSHAPPROCFAIL |
5-Notice |
Unable to fork downstream shaper process |
A possible memory error has occurred which is preventing the software from creating the downstream shaper process. |
ubr7200 |
"Gather information about running configuration and amount of memory " "in the system and report it to your technical support representative." |
|
UBR7200-5-TRAFSHAPPROCFAIL |
5-Notice |
Unable to fork downstream shaper process |
A possible memory error has occurred which is preventing the software from creating the downstream shaper process. |
ubr7200 |
"Gather information about running configuration and amount of memory " "in the system and report it to your technical support representative." |
|
UBR7200-5-UCDCCCERR |
5-Notice |
CMTS UCD failed to update CCC on [chars] U[dec] lch_state [dec] |
UCD update CCC error |
cmts-infra |
"Check the lch_state reset the upstream if necessary" |
|
UBR7200-5-UCDCCCERR |
5-Notice |
CMTS UCD failed to update CCC on [chars] U[dec] lch_state [dec] |
UCD update CCC error |
cmts-infra |
"Check the lch_state reset the upstream if necessary" |
|
UBR7200-5-UNAUTHSIDTIMEOUT |
5-Notice |
CMTS deleted BPI unauthorized Cable Modem [enet] |
Unauthorized cable modem deleted to enforce CM go through BPI authorization. |
ubr7200 |
"Check modem interface configuration for privacy mandatory " "or errors in tftp configuration file." |
|
UBR7200-5-UNAUTHSIDTIMEOUT |
5-Notice |
CMTS deleted BPI unauthorized Cable Modem [enet] |
Unauthorized cable modem deleted to enforce CM go through BPI authorization. |
ubr7200 |
"Check modem interface configuration for privacy mandatory " "or errors in tftp configuration file." |
|
UBR7200-5-UNREGSIDTIMEOUT |
5-Notice |
CMTS deleted unregistered Cable Modem [enet] |
Unregistered cable modem deleted to avoid unaccounted bandwidth usage. |
ubr7200 |
"Check modem i/f config for registration bypass " "or errors in tftp config file." |
|
UBR7200-5-UNREGSIDTIMEOUT |
5-Notice |
CMTS deleted unregistered Cable Modem [enet] |
Unregistered cable modem deleted to avoid unaccounted bandwidth usage. |
ubr7200 |
"Check modem i/f config for registration bypass " "or errors in tftp config file." |
|
UBR7200-5-UPDOWN |
5-Notice |
Interface [chars] U[chars] changed state to [chars] |
The upstream port was brought up or down. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-UPDOWN |
5-Notice |
Interface [chars] U[chars] changed state to [chars] |
The upstream port was brought up or down. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-USCONTEND |
5-Notice |
Interface [chars] U[dec] frequency hop ended at [dec].%03u MHz |
At least one modem came back online. This message logs the abort of frequency hop. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-USCONTEND |
5-Notice |
Interface [chars] U[dec] frequency hop ended at [dec].%03u MHz |
At least one modem came back online. This message logs the abort of frequency hop. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-USCONTHOP |
5-Notice |
Interface [chars] U[dec] frequency hop started |
All modems just went offline. This message logs the start of frequency hop. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-USCONTHOP |
5-Notice |
Interface [chars] U[dec] frequency hop started |
All modems just went offline. This message logs the start of frequency hop. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-USCWCHG |
5-Notice |
Interface [chars] U[chars] channel width changed to [dec] kHz |
The upstream channel width was changed. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-USCWCHG |
5-Notice |
[chars] channel width changed to [dec] kHz |
The upstream channel width was changed. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-USFREQCHG |
5-Notice |
Interface [chars] U[chars] changed to Freq [dec].%03u MHz |
The upstream channel frequency was changed. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-USFREQCHG |
5-Notice |
Interface [chars] U[chars] changed to Freq [dec].%03u MHz |
The upstream channel frequency was changed. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-USIPLCHG |
5-Notice |
Interface [chars] U[dec] input power level changed to [dec] dBmV |
The upstream channel input power level was changed. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-USIPLCHG |
5-Notice |
[chars] input power level changed to [dec] dBmV |
The upstream channel input power level was changed. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-USIPLFIX |
5-Notice |
Interface [chars] U[dec] input power level fixed at [dec] dBmV |
Setting the upstream frequency to a fixed value caused the upstream input power level to assume a fixed value. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-USIPLFIX |
5-Notice |
Interface [chars] U[dec] input power level fixed at [dec] dBmV |
Setting the upstream frequency to a fixed value caused the upstream input power level to assume a fixed value. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-USIPLINVALID |
5-Notice |
Interface [chars] U[dec] input power level is outside of valid range due to channel width change |
The upstream channel input power level is invalid. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-USIPLINVALID |
5-Notice |
Interface [chars] U[dec] input power level is outside of valid range due to channel width change |
The upstream channel input power level is invalid. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-USJIB3NBC |
5-Notice |
Interface [chars] U[dec] INFO: receives collision no burst |
A collision happens on an upstream channel |
ubr7200 |
"If consistently offending modems/channel can be found by" "test cable jib3us show intr-logs 1 on LC console" "and show cable modem on the interface" |
|
UBR7200-5-USJIB3NBC |
5-Notice |
Interface [chars] U[dec] INFO: receives collision no burst |
A collision happens on an upstream channel |
ubr7200 |
"If consistently offending modems/channel can be found by" "test cable jib3us show intr-logs 1 on LC console" "and show cable modem on the interface" |
|
UBR7200-5-USMODCHANGE |
5-Notice |
Interface [chars] U[dec] dynamic modulation changed to [chars] |
Dynamic modulation change from QAM to QPSK and vice-versa. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-USMODCHANGE |
5-Notice |
[chars] dynamic modulation changed to [chars] |
Dynamic modulation change from QAM to QPSK and vice-versa. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-USMODCHANGE_WARN |
5-Notice |
Interface [chars] U[dec] new profile [dec] is [chars] than old profile [dec] |
Print warning message about the increase or decrease in through-put |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-USMODCHANGE_WARN |
5-Notice |
Interface [chars] U[dec] new profile [dec] is [chars] than old profile [dec] |
Print warning message about the increase or decrease in through-put |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-USMODINVALID |
5-Notice |
Protect Interface [chars] U[dec] using default profile [dec] because modulation profile is undefined. |
This means that Modulation Profile was not defined on Protect UBR7200 |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-5-USPHY_BAD_INTR |
5-Notice |
USPHY with physical channel [dec] gets too many error interrupts |
US PHY or MAC chips on the LC get into a bad state and SW can not recover it |
ubr7200 |
"Collect show tech and then power cycle the Line card." "If problem does not recover contact Cisco for support" |
|
UBR7200-5-USPHY_BAD_INTR |
5-Notice |
USPHY with physical channel [dec] gets too many error interrupts |
US PHY or MAC chips on the LC get into a bad state and SW can not recover it |
ubr7200 |
"Collect show tech and then power cycle the Line card." "If problem does not recover contact Cisco for support" |
|
UBR7200-5-USPHYTSSDISC |
5-Notice |
PHY TSS discontinuous on [chars] U[dec] old<T [hec] M [hec] F [hec]> new<T [hec] M [hec] F %4x> start<T [hec] M [hec] F %4x> mac<T [hec] M [hec] F %4x> tgc/frame [hec] mslot/frame [hec] |
PHY TSS error |
cmts-infra |
"If the problem is persistent modify minislot size and reset the upstream" |
|
UBR7200-5-USPHYTSSDISC |
5-Notice |
PHY TSS discontinuous on [chars] U[dec] old<T [hec] M [hec] F [hec]> new<T [hec] M [hec] F %4x> start<T [hec] M [hec] F %4x> mac<T [hec] M [hec] F %4x> tgc/frame [hec] mslot/frame [hec] |
PHY TSS error |
cmts-infra |
"If the problem is persistent modify minislot size and reset the upstream" |
|
UBR7200-5-USPHYTSSLATE |
5-Notice |
PHY late TSS on [chars] U[dec] MAC [hec] phy <last [hec] curr [hec]> tgc/frame [hec] |
late PHY TSS SNAPSHOT messages are received |
cmts-infra |
"This is an internal failure and not necessarily problematic" |
|
UBR7200-5-USPHYTSSLATE |
5-Notice |
PHY late TSS on [chars] U[dec] MAC [hec] phy <last [hec] curr [hec]> tgc/frame [hec] |
late PHY TSS SNAPSHOT messages are received |
cmts-infra |
"This is an internal failure and not necessarily problematic" |
|
UBR7200-5-USTSSMISMATCH |
5-Notice |
MAC-PHY TSS mismatch [chars] U[dec]: MAC<T [hec] M [hec] F [hec]> PHY<T [hec] M [hec] F [hec]> Old-PHY<T [hec] M [hec] F [hec]> start<T [hec] M [hec] F [hec]> curr [hec] tgc/fame [hec] mslots/fame [hec] |
Mis-matched MAC-PHY TSS is detected |
cmts-infra |
"This is an internal failure and not necessarily problematic" |
|
UBR7200-5-USTSSMISMATCH |
5-Notice |
MAC-PHY TSS mismatch [chars] U[dec]: MAC<T [hec] M [hec] F [hec]> PHY<T [hec] M [hec] F [hec]> Old-PHY<T [hec] M [hec] F [hec]> start<T [hec] M [hec] F [hec]> curr [hec] tgc/fame [hec] mslots/fame [hec] |
Mis-matched MAC-PHY TSS is detected |
cmts-infra |
"This is an internal failure and not necessarily problematic" |
|
UBR7200-5-USTSSNOTALIGNED |
5-Notice |
MAC-PHY TSS on [chars] U[dec] not at frame boundary MAC<T [hec] M [hec] F [hec]> start <T [hec] M [hec] F [chars]> current<T [hec]> tgc/frame [hec] mslot/frame [hec] |
PHY TSS is not sampled at frame boundary |
cmts-infra |
"This is an internal failure and not necessarily problematic" |
|
UBR7200-5-USTSSNOTALIGNED |
5-Notice |
MAC-PHY TSS on [chars] U[dec] not at frame boundary MAC<T [hec] M [hec] F [hec]> start <T [hec] M [hec] F [chars]> current<T [hec]> tgc/frame [hec] mslot/frame [hec] |
PHY TSS is not sampled at frame boundary |
cmts-infra |
"This is an internal failure and not necessarily problematic" |
|
UBR7200-5-WIDEBAND_AUTORESET |
5-Notice |
Reset total [dec] wideband capable cable modems which registered in |
wideband autoreset feature reset wideband capable cable modems which registered in narrow band mode. |
cmts-docsis |
LOG_STD_NO_ACTION |
|
UBR7200-6-ACFE_NOTIFICATION |
6-Information |
[chars] |
A special event happened in ACFE algorithm module |
cmts-qos |
LOG_STD_NO_ACTION |
|
UBR7200-6-ACFE_NOTIFICATION |
6-Information |
[chars] |
A special event happened in ACFE algorithm module |
cmts-qos |
LOG_STD_NO_ACTION |
|
UBR7200-6-ACTIVE |
6-Information |
Cable clock [chars] reference active |
The clock reference became active |
ubr7200 |
"Informational only" |
|
UBR7200-6-ACTIVE |
6-Information |
Cable clock [chars] reference active |
The clock reference became active |
ubr7200 |
"Informational only" |
|
UBR7200-6-ALARM_INFO |
6-Information |
[chars] [chars] [chars] [chars] [chars] |
Alarm assertion or deassertion information. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-ALARM_INFO |
6-Information |
[chars] [chars] [chars] [chars] [chars] |
Alarm assertion or deassertion information. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-BADIPASSIGNMENT |
6-Information |
[chars] dropped : Interface [chars] Mac [enet] SID [dec] L3_Interface [chars] \n IP [inet] already assigned to MAC=[enet] Interface [chars] SID [dec] |
There might be an incorrect DHCP assignment going on. |
ubr7200 |
"Look for possible DHCP server misconfiguration" |
|
UBR7200-6-BADIPSOURCE |
6-Information |
Interface [chars] IP packet from invalid source. IP=[inet] MAC=[enet] Expected SID=[dec] Actual SID=[dec] |
There might be a spoofing attempt going on. |
ubr7200 |
"Look for possible spoofing attempt" |
|
UBR7200-6-BADIPSOURCE |
6-Information |
Interface [chars] IP packet from invalid source. IP=[inet] MAC=[enet] Expected SID=[dec] Actual SID=[dec] |
There might be a spoofing attempt going on. |
ubr7200 |
"Look for possible spoofing attempt" |
|
UBR7200-6-BADIPSOURCE_BUNDLE |
6-Information |
Interface [chars] IP packet from invalid source. IP=[inet] MAC=[enet] Expected Interface=[chars] SID=[dec] Actual Interface=[chars] SID=[dec] |
There might be a spoofing attempt going on. |
ubr7200 |
"Look for possible spoofing attempt" |
|
UBR7200-6-BADTXOFFSET |
6-Information |
Bad timing offset %ld detected for cable modem [enet] sid [hec] cm status [hec] dcc [chars] skip_reg [chars]. |
The cable modem is not using the correct starting offset during initial ranging. This causes a zero negative timing offset to be recorded by the CMTS for this modem. The CMTS internal algorithms that rely on the |
ubr7200 |
"Locate the cable modem based on MAC address and report initial " "timing offset problem to the CM vendor" |
|
UBR7200-6-CACHE_ENGINE_BUF_FULL |
6-Information |
Max. cache buffer has been reached! |
Max. cache buffer has been reached. cache engine service for current request is denied. |
snmpPerf |
"." |
|
UBR7200-6-CACHE_ENGINE_BUF_FULL |
6-Information |
Max. cache buffer has been reached! |
Max. cache buffer has been reached. cache engine service for current request is denied. |
snmpPerf |
"." |
|
UBR7200-6-CGD_AUTO_DCID_PARSE_ERROR |
6-Information |
Parse error during sync newly assigned automatic DCID \n\ while running CGD command. |
A parse error has occured while trying to sync the newly assigned DCID to standby PRE. |
ubr7200 |
"Remove and attempt to add the channel set again." |
|
UBR7200-6-CGD_AUTO_DCID_PARSE_ERROR |
6-Information |
Parse error during sync newly assigned automatic DCID \n\ while running CGD command. |
A parse error has occured while trying to sync the newly assigned DCID to standby PRE. |
ubr7200 |
"Remove and attempt to add the channel set again." |
|
UBR7200-6-CGD_AUTO_DCID_UNAVAILABLE |
6-Information |
Unable to assign an automatic Channel ID for channel in MAC Domain [chars] and Fiber Node [dec] |
Unable to assign an automatic Channel ID for the newly added channel in the MAC Domain. See show cable fiber-node to see channel ID assignments in the Fiber-Node. |
- |
"Attempt to manually resolve channel ID conflict by disabling " "automatic DCID assignment." |
|
UBR7200-6-CGD_AUTO_DCID_UNAVAILABLE |
6-Information |
Unable to assign an automatic channel ID for channel in the FN and MD for downstream [dec]/[dec]/[dec]:[dec] in FN [dec] \n |
Unable to assign an automatic Channel ID for the newly added channel in the MAC Domain. See show cable fiber-node to see channel ID assignments in the Fiber-Node. |
- |
"Attempt to manually resolve channel ID conflict by disabling " "automatic DCID assignment." |
|
UBR7200-6-CM_OFFLINE_WITH_DUP_MPLSPEER_VCID |
6-Information |
MPLS PEER [inet] VCID [dec] in use sending CM [enet] offline |
MPLS PEER & VCID is in use. Send offline message to CM. |
cmts-application |
"Check L2VPN MPLS PEER & VCID specified in CM configuration file" |
|
UBR7200-6-CM_OFFLINE_WITH_DUP_MPLSPEER_VCID |
6-Information |
MPLS PEER [inet] VCID [dec] in use sending CM [enet] offline |
MPLS PEER & VCID is in use. Send offline message to CM. |
cmts-application |
"Check L2VPN MPLS PEER & VCID specified in CM configuration file" |
|
UBR7200-6-CM_OFFLINE_WITH_L2VPN_NOT_ENABLE |
6-Information |
DOCSIS L2VPN not enabled sending CM [enet] offline |
Cable Modem is configured with L2VPN but CMTS L2VPN isn't enabled. Send offline message to CM. |
cmts-application |
"Configure \"cable l2-vpn-service xconnect nsi dot1q interface ..\" and " " \"cable l2-vpn-service nsi dot1q\" commands." |
|
UBR7200-6-CM_OFFLINE_WITH_L2VPN_NOT_ENABLE |
6-Information |
DOCSIS L2VPN not enabled sending CM [enet] offline |
Cable Modem is configured with L2VPN but CMTS L2VPN isn't enabled. Send offline message to CM. |
cmts-application |
"Configure \"cable l2-vpn-service xconnect nsi dot1q interface ..\" and " " \"cable l2-vpn-service nsi dot1q\" commands." |
|
UBR7200-6-CM_OFFLINE_WITH_LEGACY_TLS_CONFIGURED |
6-Information |
Already configured for legacy TLS sending CM [enet] offline |
Legacy TLS is already configured. Send offline message to CM. |
cmts-application |
"Check CMTS configuration for legacy TLS with this CM" |
|
UBR7200-6-CM_OFFLINE_WITH_LEGACY_TLS_CONFIGURED |
6-Information |
Already configured for legacy TLS sending CM [enet] offline |
Legacy TLS is already configured. Send offline message to CM. |
cmts-application |
"Check CMTS configuration for legacy TLS with this CM" |
|
UBR7200-6-CM_OFFLINE_WITH_MPLS_L2VPN_NOT_ENABLE |
6-Information |
DOCSIS MPLS L2VPN not enabled sending CM [enet] offline |
Cable Modem is configured with L2VPN but CMTS MPLS L2VPN isn't enabled. Send offline message to CM. |
cmts-application |
"Configure \"cable l2-vpn-service xconnect nsi mpls\" command." |
|
UBR7200-6-CM_OFFLINE_WITH_MPLS_L2VPN_NOT_ENABLE |
6-Information |
DOCSIS MPLS L2VPN not enabled sending CM [enet] offline |
Cable Modem is configured with L2VPN but CMTS MPLS L2VPN isn't enabled. Send offline message to CM. |
cmts-application |
"Configure \"cable l2-vpn-service xconnect nsi mpls\" command." |
|
UBR7200-6-CM_OFFLINE_WITH_NO_FREE_VPNID |
6-Information |
No free VPNIDs remaining sending CM [enet] offline |
There aren't any free VPNIDs. Send offline message to CM. |
cmts-application |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-6-CM_OFFLINE_WITH_NO_FREE_VPNID |
6-Information |
No free VPNIDs remaining sending CM [enet] offline |
There aren't any free VPNIDs. Send offline message to CM. |
cmts-application |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-6-CM_OFFLINE_WITH_UNRESOLVED_MPLSPEER_NAME |
6-Information |
Unable to resolve MPLS NAME [chars] VCID [dec] sending CM [enet] offline |
Unable to resolve MPLS NAME via DNS. Send offline message to CM. |
cmts-application |
"Check L2VPN MPLS PEERNAME specified in CM configuration file" "Or DNS configuration and setup" |
|
UBR7200-6-CM_OFFLINE_WITH_UNRESOLVED_MPLSPEER_NAME |
6-Information |
Unable to resolve MPLS NAME [chars] VCID [dec] sending CM [enet] offline |
Unable to resolve MPLS NAME via DNS. Send offline message to CM. |
cmts-application |
"Check L2VPN MPLS PEERNAME specified in CM configuration file" "Or DNS configuration and setup" |
|
UBR7200-6-CM_OFFLINE_WITH_VLANID_USED |
6-Information |
VLANID [dec] on [chars] in use sending CM [enet] offline |
VLANID is in use. Send offline message to CM. |
cmts-application |
"Check L2VPN VLANID specified in CM configuration file" |
|
UBR7200-6-CM_OFFLINE_WITH_VLANID_USED |
6-Information |
VLANID [dec] on [chars] in use sending CM [enet] offline |
VLANID is in use. Send offline message to CM. |
cmts-application |
"Check L2VPN VLANID specified in CM configuration file" |
|
UBR7200-6-CM_RNG_CLASS_ID_UNMATCH |
6-Information |
US that CM [enet] send Initial Rng Req has unmatched Channel Class ID0x[hec] with CM's Ranging Class ID0x[hec]\n |
CM's Ranging Class ID doesn't match the the Channel Class ID of its upstream but it may be expected due to CM received a DCC/DBC... or CM config file included extended Ranging Class ID\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-CM_RNG_CLASS_ID_UNMATCH |
6-Information |
US that CM [enet] send Initial Rng Req has unmatched Channel Class ID0x[hec] with CM's Ranging Class ID0x[hec]\n |
CM's Ranging Class ID doesn't match the the Channel Class ID of its upstream but it may be expected due to CM received a DCC/DBC... or CM config file included extended Ranging Class ID\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-CMMOVED |
6-Information |
Cable modem [enet] has been moved from interface [chars] to interface [chars]. |
The cable modem has been detected ranging on a new interface. |
ubr7200 |
"Informational only" |
|
UBR7200-6-CMMOVED |
6-Information |
Cable modem [enet] has been moved from interface [chars] to interface [chars]. |
The cable modem has been detected ranging on a new interface. |
ubr7200 |
"Informational only" |
|
UBR7200-6-CMTS_CM_DB_ACCESS_DENIAL_ERROR |
6-Information |
[chars] try to access CM [enet] when prim sid is deleted |
access cable modem after prim sid is not allowed |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-CMTS_CM_DB_CM_ADD_ERROR |
6-Information |
[chars] CM [enet] cminstp %p prim_sid [dec] prim sidinstp %p check failed when add to DB |
cable modem check error when add to DB |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-CMTS_CM_DB_CM_SID_INCONSISTENCY_ERROR |
6-Information |
CM_DB's mac_domain [chars] \n cminstp's mac_domain [chars] CM_DB's cminstp %p current cminstp %p CM_DB's sidinstp %p current sidinstp %p\n CM_DB's mac_addr [enet] cminstp's mac_addr [enet] sidinstp's mac_addr [enet]\n CM_DB's prim_sid [dec] cminstp's prim_sid [dec] sidinstp's prim_sid [dec] |
find cable modem's info is consistent with prim sid |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-CMTS_CM_DB_DELETE_TIMING_ERROR |
6-Information |
[chars] CMTS delete CM [enet] cminstp %p but prim_sid [dec] prim_sidinstp %p is not deleted |
CM deletion should not before prim_sid deletion |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-CMTS_CM_DB_SID_CHECK_ERROR |
6-Information |
[chars] CM_DB: PRIM_SID ERROR CM [enet] cminstp->prim_sid [dec] \n sidinstp->prim_sid [dec] sidinstp->sidinstp [dec] |
PRIM SID check error whe add to CM DB |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-CMTS_CM_DB_SID_DUPLICATE_ERROR |
6-Information |
[chars] multiple prim_sid assignment for CM [enet] previous prim_sid [dec] current prim_sid [dec] |
prim SID already exist when CMTS try to assign a new SID to cable modem |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-CMTS_MD_IDX_OUT_OF_RANGE_ERROR |
6-Information |
Mac Domain Index [dec] is out of range. |
Mac Domain Index is out of range. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-CMTS_MD_IDX_OUT_OF_RANGE_ERROR |
6-Information |
Mac Domain Index [dec] is out of range. |
Mac Domain Index is out of range. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-CMTS_SLOT_OUT_OF_RANGE_ERROR |
6-Information |
Slot [dec]/Subslot [dec]/MD [dec] is out of range. |
Slot/subslot is out of range. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-CMTS_SLOT_OUT_OF_RANGE_ERROR |
6-Information |
Slot [dec]/Subslot [dec]/MD [dec] is out of range. |
Slot/subslot is out of range. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-CNNR_NORCVR |
6-Information |
No upstream receiver available in connector group [dec]-[dec] for C[dec]/[dec]/[dec]/U[dec] to connector [dec] mapping |
All upstream receivers for the connector group have been used |
ubr7200 |
"Remove some upstream mapping to connectors in the connector group." |
|
UBR7200-6-CNNR_NOSHR |
6-Information |
Failed to map C[dec]/[dec]/[dec]/U[dec] to connector [dec] already mapped by C[dec]/[dec]/[dec]/U[dec]. |
Some connectors do not support frequency stacking. They can only be mapped by one upstream at a time. This may happen on MC28 cards. |
ubr7200 |
"Remove the existing mapping on the connector." |
|
UBR7200-6-CNNR_NOXC |
6-Information |
Failed to map C[dec]/[dec]/[dec]/U[dec] to connector [dec] clear connector [dec] [dec] mapping first. |
Some 2x2 upstream PHY chips don't support XC crossed connector->receiver mapping C0->R1 + C1->R0. The connector |
ubr7200 |
"Remove all the existing mappings from the two " "connectors of the chip and reprovision the wanted " "mappings. This will rearrang the mappings as " "straight mapping C0->R0 + C1->R1. " |
|
UBR7200-6-COMPAT_NEW_CARD |
6-Information |
The old card <[chars]> is replaced by new card <[chars]> in slot [dec]. |
OIR: card replacement |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-COMPAT_NEW_CARD |
6-Information |
The old card <[chars]> is replaced by new card <[chars]> in slot [dec]. |
OIR: card replacement |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-COMPAT_SHUTDOWN_CARD |
6-Information |
Failed to restore the configuration for [chars]. |
OIR-compatiblity configuration restore failed |
ubr7200 |
"Configure the interface manually" |
|
UBR7200-6-COMPAT_SHUTDOWN_CARD |
6-Information |
Failed to restore the configuration for [chars]. |
OIR-compatiblity configuration restore failed |
ubr7200 |
"Configure the interface manually" |
|
UBR7200-6-CONFIG_EXIT |
6-Information |
Exiting config mode by [chars] since Port Adapter in slot [dec] removed |
The user was configuring a port adapter which was either removed from the system or if an mc28u card was reset. Therefore the configuration mode is invalid and terminated by IOS |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-CONFIG_EXIT |
6-Information |
Exiting config mode by [chars] since Port Adapter in slot [dec] removed |
The user was configuring a port adapter which was either removed from the system or if an mc28u card was reset. Therefore the configuration mode is invalid and terminated by IOS |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-CPE_MOVED_FROM_WRONG_SID_CHAIN |
6-Information |
CPE [enet] was moved from SID Chain [dec] to [dec] from [chars] of the chain |
The CMTS automatically corrected a condition where the CPE was in the wrong SID chain. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-CPE_MOVED_FROM_WRONG_SID_CHAIN |
6-Information |
CPE [enet] was moved from SID Chain [dec] to [dec] from [chars] of the chain |
The CMTS automatically corrected a condition where the CPE was in the wrong SID chain. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-CREATE_MAUTH_PROF |
6-Information |
<132>CMTS[DOCSIS]:<89010300> Multicast Profile [chars] created for CM Mac [enet]. |
CMTS automatically creates an IP Multicast Profile |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-CREATE_MAUTH_PROF |
6-Information |
<132>CMTS[DOCSIS]:<89010300> Multicast Profile [chars] created for CM Mac [enet]. |
CMTS automatically creates an IP Multicast Profile |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-6-DBDSPDOWNLOADDONE |
6-Information |
Downloading dsp code completed |
Downloading dsp code completed |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-DBDSPDOWNLOADDONE |
6-Information |
Downloading dsp code completed |
Downloading dsp code completed |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-DBDSPDOWNLOADSTART |
6-Information |
Downloading dsp code initiated |
Downloading dsp code started |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-DBDSPDOWNLOADSTART |
6-Information |
Downloading dsp code initiated |
Downloading dsp code started |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-DBDSPVERSION |
6-Information |
Current DSP version : [dec] DSP flash version : [dec] |
The current code version and the version DSP booted up with |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-DBDSPVERSION |
6-Information |
Current DSP version : [dec] DSP flash version : [dec] |
The current code version and the version DSP booted up with |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-DDC_CFG_HASHFILTER_REMOVED |
6-Information |
Hash-filter [dec] not present in global config - Filter removed from [chars]\n |
The hash-filter was removed from the global config while the card was not present in the chassis therefore the corresponding interface hash filter is removed from the config |
ddc |
LOG_STD_NO_ACTION |
|
UBR7200-6-DDC_CFG_HASHFILTER_REMOVED |
6-Information |
Hash-filter [dec] not present in global config - Filter removed from [chars]\n |
The hash-filter was removed from the global config while the card was not present in the chassis therefore the corresponding interface hash filter is removed from the config |
ddc |
LOG_STD_NO_ACTION |
|
UBR7200-6-DDC_CFG_TARGET_REMOVED |
6-Information |
Redundancy target invalid - removed from [chars]\n |
The router's my_id was config removed while the card was not present in the chassis therefore the redundancy target cli is removed from the interface |
ddc |
LOG_STD_NO_ACTION |
|
UBR7200-6-DDC_CFG_TARGET_REMOVED |
6-Information |
Redundancy target invalid - removed from [chars]\n |
The router's my_id was config removed while the card was not present in the chassis therefore the redundancy target cli is removed from the interface |
ddc |
LOG_STD_NO_ACTION |
|
UBR7200-6-DIFFENCADJUST |
6-Information |
Differential-encoding is disabled on interface [chars] upstream [chars] it is only supported for QPSK or QAM16. |
Differential-encoding is only supported for QPSK or QAM16. |
ubr7200 |
"Informational only" |
|
UBR7200-6-DIFFENCADJUST |
6-Information |
Differential-encoding is disabled on interface [chars] upstream [chars] it is only supported for QPSK or QAM16. |
Differential-encoding is only supported for QPSK or QAM16. |
ubr7200 |
"Informational only" |
|
UBR7200-6-DOCSIS_SID_DELETE_IPC_ERROR |
6-Information |
RP try to delete cm from LC's host_db mac [enet] sid [dec] host_hdl flag [hec] device_class [chars] |
RP send IPC to LC to delete cm from LC's host_db which is not allowed. RP may treat a CM as CPE\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-DPON_CLC_GLOBAL |
6-Information |
Enabling DPON for MAC domain MD: [chars] implicitly enables DPON for all other |
- |
- |
- |
|
UBR7200-6-DPON_CLC_GLOBAL |
6-Information |
Enabling DPON for MAC domain MD: [chars] implicitly enables DPON for all other |
- |
- |
- |
|
UBR7200-6-DRVMP |
6-Information |
Midplane TDM clock reference defaults to Clockcard |
Clockcard primary reference is from midplane TDM clock |
ubr7200 |
"Informational only" |
|
UBR7200-6-DRVMP |
6-Information |
Midplane TDM clock reference defaults to Clockcard |
Clockcard primary reference is from midplane TDM clock |
ubr7200 |
"Informational only" |
|
UBR7200-6-DSG_ALL_TUNNEL_REMOVED |
6-Information |
all DSG tunnels are removed on interface [chars] and it's subinterfaces |
DSG is disabled on the interface |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-DSPRIMARYSFIDCONFLICT |
6-Information |
Assigned ds primary sfid [dec] conflicts with existing ds primary sfid [dec] for Cable modem [enet] on interface [chars] |
The assigned downstream primary SFID conflicts with the existing downstream primary SFID for the cable modem. |
ubr7200 |
"Informational only" |
|
UBR7200-6-DSPRIMARYSFIDCONFLICT |
6-Information |
Assigned ds primary sfid [dec] conflicts with existing ds primary sfid [dec] for Cable modem [enet] on interface [chars] |
The assigned downstream primary SFID conflicts with the existing downstream primary SFID for the cable modem. |
ubr7200 |
"Informational only" |
|
UBR7200-6-DUAL_CLEANUP_ATTEMPT |
6-Information |
Second cleanup for modem |
A modem entry was attempted to be cleaned up twice |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-6-DUAL_CLEANUP_ATTEMPT |
6-Information |
Second cleanup for modem |
A modem entry was attempted to be cleaned up twice |
ubr7200 |
LOG_STD_SH_TECH_ACTION |
|
UBR7200-6-FECKBYTEADJUST |
6-Information |
[chars] burst's FEC K BYTE in mod profile [dec] is adjusted to [dec] bytes. |
The FEC K bytes in the burst profile adjusted to a valid value. |
ubr7200 |
"Informational only" |
|
UBR7200-6-FECKBYTEADJUST |
6-Information |
[chars] burst's FEC K BYTE in mod profile [dec] is adjusted to [dec] bytes. |
The FEC K bytes in the burst profile adjusted to a valid value. |
ubr7200 |
"Informational only" |
|
UBR7200-6-FREERUN |
6-Information |
Cable clock in Freerun mode |
Clockcard is in free run mode |
ubr7200 |
"Informational only" |
|
UBR7200-6-FREERUN |
6-Information |
Cable clock in Freerun mode |
Clockcard is in free run mode |
ubr7200 |
"Informational only" |
|
UBR7200-6-GRDIDX_LOG |
6-Information |
DS [dec]/[dec]/[dec] Index [dec] DSID 0x[hec] SID [dec] SF_BU [dec] FW [chars] [dec]/[dec]/[dec]:[dec] MD Ca[dec]/[dec]/[dec] [chars] [chars] |
Debug message for Guardian index operations |
ubr10000 |
LOG_STD_NO_ACTION |
|
UBR7200-6-GRDIDX_LOG |
6-Information |
DS [dec]/[dec]/[dec] Index [dec] DSID 0x[hec] SID [dec] SF_BU [dec] FW [chars] [dec]/[dec]/[dec]:[dec] MD Ca[dec]/[dec]/[dec] [chars] [chars] |
Debug message for Guardian index operations |
ubr10000 |
LOG_STD_NO_ACTION |
|
UBR7200-6-GUARDSYMLENADJUST |
6-Information |
[chars] burst's guard symbol length in mod profile [dec] is adjusted to [dec] symbols. |
The guard symbol length in the burst profile adjusted to a valid value. |
ubr7200 |
"Informational only" |
|
UBR7200-6-GUARDSYMLENADJUST |
6-Information |
[chars] burst's guard symbol length in mod profile [dec] is adjusted to [dec] symbols. |
The guard symbol length in the burst profile adjusted to a valid value. |
ubr7200 |
"Informational only" |
|
UBR7200-6-HOLDOVER |
6-Information |
Cable clock in Holdover mode |
Clockcard switched to holdover mode |
ubr7200 |
"Check reference source" |
|
UBR7200-6-HOLDOVER |
6-Information |
Cable clock in Holdover mode |
Clockcard switched to holdover mode |
ubr7200 |
"Check reference source" |
|
UBR7200-6-HOTLISTMAC |
6-Information |
Investigating MAC=[enet] sid [dec] interface [chars]: MAC blocked |
CMTS glean function received blocked mac addr |
ubr7200 |
"Check for spoofing: CPE using blocked mac addr" |
|
UBR7200-6-INTERNAL_XCONNECT_INTERFACE_ERROR |
6-Information |
Unable to create internal xconnect bundle interface |
Unable to find free bundle interface for l2vpn xconnect function |
cmts-application |
"Free one bundle interface for internal l2vpn xconnect function" |
|
UBR7200-6-INTERNAL_XCONNECT_INTERFACE_ERROR |
6-Information |
Unable to create internal xconnect bundle interface |
Unable to find free bundle interface for l2vpn xconnect function |
cmts-application |
"Free one bundle interface for internal l2vpn xconnect function" |
|
UBR7200-6-LB_INTERVAL_UNSUITABLE |
6-Information |
The interval value [dec] for LBG [chars] is too small or too big. |
The recommanded interval value is between 10 to 300. |
loadbalance |
- |
|
UBR7200-6-LB_MODEM_SUCCESS |
6-Information |
Succeeded to move modem [enet] from [chars] to [chars]. |
Load balancing succeeded to move a modem from one interface to another. |
loadbalance |
"LOG_STD_NO_ACTION" |
|
UBR7200-6-LB_RFCH_SET_OVERLAP |
6-Information |
Rf-channel sets overlap in LBG [chars]. |
Detect RF channel sets overlap in this Docsis LBG. It will cause D3.0 dynamic LB algorithm may not work optimally. |
loadbalance |
- |
|
UBR7200-6-LB_RFCH_SIZE_EXCEED |
6-Information |
Rf-channel size in LBG [chars] exceeds the limit maximum [dec] |
The rf-channel size in LBG exceeds the limit. It will cause D3.0 dynamic LB algorithm may not work optimally. |
loadbalance |
- |
|
UBR7200-6-LCHDIFFENCADJUST |
6-Information |
Differential-encoding is disabled on interface [chars] upstream [chars] it should be supported by all active logical channels. |
Differential-encoding should be supported on all logical channels. |
ubr7200 |
"Informational only" |
|
UBR7200-6-LCHDIFFENCADJUST |
6-Information |
Differential-encoding is disabled on interface [chars] upstream [chars] it should be supported by all active logical channels. |
Differential-encoding should be supported on all logical channels. |
ubr7200 |
"Informational only" |
|
UBR7200-6-LOS |
6-Information |
Cable clock [chars] reference Loss of Signal |
The clock reference was lost |
ubr7200 |
"Check reference source" |
|
UBR7200-6-LOS |
6-Information |
Cable clock [chars] reference Loss of Signal |
The clock reference was lost |
ubr7200 |
"Check reference source" |
|
UBR7200-6-MACCLTCLR |
6-Information |
Enable mac mgmt msg processing on [chars]. |
The RP has reenabled the sending of DOCSIS MAC-layer messages on the cable interfaces after an N+1 switchover. |
ubr7200 |
"No action needed." |
|
UBR7200-6-MACCLTCLR |
6-Information |
Enable mac mgmt msg processing on [chars]. |
The RP has reenabled the sending of DOCSIS MAC-layer messages on the cable interfaces after an N+1 switchover. |
ubr7200 |
"No action needed." |
|
UBR7200-6-MAP_REJECT_DS_TRAFFIC_FLOW_NOT_MAPPED |
6-Information |
<132>CMTS[DOCSIS]:<66060510> Map Reject - Downstream traffic flow not mapped to BPI+SAID. CM Mac Addr <[enet]> |
Map Reject - Downstream traffic flow not mapped to BPI+SAID\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-MAP_REJECT_DS_TRAFFIC_FLOW_NOT_MAPPED |
6-Information |
<132>CMTS[DOCSIS]:<66060510> Map Reject - Downstream traffic flow not mapped to BPI+SAID. CM Mac Addr <[enet]> |
Map Reject - Downstream traffic flow not mapped to BPI+SAID\n |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-MAP_UPSTREAM_BW_ALLOCATION |
6-Information |
<135>CMTS[DOCSIS]:<77000100> A transmit opportunity was missed because MAP arrived too late |
A transmit opportunity was missed because MAP arrived too late \n |
ubr7200 |
"If the problem persists with a particular cable modem " "reboot the cable modem and check for possible hardware or" "software problems with that cable modem If this problem " "occurs with many cable modemscheck the cable plant for " "RF transmission and noise ingress problems." |
|
UBR7200-6-MAP_UPSTREAM_BW_ALLOCATION |
6-Information |
<135>CMTS[DOCSIS]:<77000100> A transmit opportunity was missed because MAP arrived too late |
A transmit opportunity was missed because MAP arrived too late \n |
ubr7200 |
"If the problem persists with a particular cable modem " "reboot the cable modem and check for possible hardware or" "software problems with that cable modem If this problem " "occurs with many cable modemscheck the cable plant for " "RF transmission and noise ingress problems." |
|
UBR7200-6-MCAST_IPC_HEADER_ADD_FAILURE |
6-Information |
Multicast IPC header could not be added for source [chars] group [chars] fwd interface [chars] |
Multicast IPC header could not be added |
ubr7200 |
LOG_STD_ACTION |
|
UBR7200-6-MCAST_IPC_HEADER_ADD_FAILURE |
6-Information |
Multicast IPC header could not be added for source [chars] group [chars] fwd interface [chars] |
Multicast IPC header could not be added |
cbr-application |
LOG_STD_ACTION |
|
UBR7200-6-MCAST_SESS_NOT_AUTH |
6-Information |
<132>CMTS[DOCSIS]:<89010200> Multicast session [chars] is not authorized for CM [enet] |
Default configured action for IGMP Join is denied or the matching session rule's action is denied or the maximium session limit for the modem has been reached. |
ubr7200 |
LOG_STD_NO_ACTION |
|
UBR7200-6-MCAST_SESS_NOT_AUTH |
6-Information |
<132>CMTS[DOCSIS]:<89010200> Multicast session [chars] is not authorized for CM [enet] |
Default configured action for IGMP Join is denied or the matching session rule's action is denied or the maximium session limit for the modem has been reached. |
cbr-application |
LOG_STD_NO_ACTION |
|
UBR7200-6-MD_DS_SG_DCID_CONFLICT |
6-Information |
Downstream channel IDs conflict in mac-domain of [chars] |
At least two channels in the mac-domain have the same downstream channel ID. See show cable fiber-node to see channel ID assignments |
- |
"Change the downstream channel ID." |
|
UBR7200-6-MD_DS_SG_DCID_CONFLICT |
6-Information |
Downstream channel IDs conflict in mac-domain of [chars] |
At least two channels in the mac-domain have the same downstream channel ID. See show cable fiber-node to see channel ID assignments |
- |
"Change the downstream channel ID." |
|
UBR7200-6-MDIDX_LOG |
6-Information |
GRD [dec]/[dec] Index [dec] SID [dec] SF [dec] FW [chars] [dec]/[dec]/[dec]:[dec] MD [chars] [chars] [chars] |
Debug message for MAC Domain index operations |
ubr10000 |
LOG_STD_NO_ACTION |
|
UBR7200-6-MDIDX_LOG |
6-Information |
GRD [dec]/[dec] Index [dec] SID [dec] SF [dec] FW [chars] [dec]/[dec]/[dec]:[dec] MD [chars] [chars] [chars] |
Debug message for MAC Domain index operations |
ubr10000 |
LOG_STD_NO_ACTION |
|
UBR7200-6-MQOS |
6-Information |
Power supply may be overloaded to support the line card installed in slot [dec] |
The power supply may be insufficient to support the number of line \n\ cards installed in the system under certain operation conditions \n\ like high temperature and high voltage margining. |
- |
"Upgrade the power supply as soon as possible or the system may \n\ fail to operation properly under some certain operation conditions." |
|
UBR7200-6-MQOS |
6-Information |
Power supply may be overloaded to support the line card installed in slot [dec] |
The power supply may be insufficient to support the number of line \n\ cards installed in the system under certain operation conditions \n\ like high temperature and high voltage margining. |
- |
"Upgrade the power supply as soon as possible or the system may \n\ fail to operation properly under some certain operation conditions." |
|
UBR7200-6-PKTCBL_COPS_CONNECTION_DOWN |
6-Information |
Cops connection: IP addr: [inet] Handle: 0x[hec] went down Error code: [dec] |
Cops connection went down |
packetcable |
"Check cops connection" |
|
UBR7200-6-PKTCBL_COPS_CONNECTION_DOWN |
6-Information |
Cops connection: IP addr: [inet] Handle: 0x[hec] went down Error code: [dec] |
Cops connection went down |
packetcable |
"Check cops connection" |
|
UBR7200-6-PKTCBL_COPS_CONNECTION_UP |
6-Information |
Cops connection: IP addr: [inet] Handle: 0x[hec] is up |
Cops connection is up |
packetcable |
LOG_STD_NO_ACTION |
|
UBR7200-6-PKTCBL_COPS_CONNECTION_UP |
6-Information |
Cops connection: IP addr: [inet] Handle: 0x[hec] is up |
Cops connection is up |
packetcable |
LOG_STD_NO_ACTION |
|
UBR7200-6-PREAMLENADJUST |
6-Information |
[chars] burst's preamble length in mod profile [dec] is adjusted to [dec] bits. |
The preamble length in the burst profile adjusted to a valid value. |
ubr7200 |
"Informational only" |
|
UBR7200-6-PREAMLENADJUST |
6-Information |
[chars] burst's preamble length in mod profile [dec] is adjusted to [dec] bits. |
The preamble length in the burst profile adjusted to a valid value. |
ubr7200 |
"Informational only" |
|
UBR7200-6-PREAMLENCHECK |
6-Information |
preamble length exceeds total of 128 byte. |
The preamble length exceeds total of 128 byte. |
ubr7200 |
"Informational only" |
|
UBR7200-6-PREAMLENCHECK |
6-Information |
preamble length exceeds total of 128 byte. |
The preamble length exceeds total of 128 byte. |
ubr7200 |
"Informational only" |
|
UBR7200-6-REFLOCK |
6-Information |
Cable clock locked to [chars] reference |
Clockcard locked onto clock source |
ubr7200 |
"Informational only" |
|
UBR7200-6-REFLOCK |
6-Information |
Cable clock locked to [chars] reference |
Clockcard locked onto clock source |
ubr7200 |
"Informational only" |
|
UBR7200-6-RF_CHAN_DCID_CONFLICT |
6-Information |
The downstream channel id's conflict for [chars] rf-channel [dec]\n could not be resolved by automatic DCID assignment.\n |
Auto DCID assignment fails to assign valid DCID for a specific channel\n See \show cable fiber-node\ for detail channel ID assignments |
- |
"Check fiber node and downstream channel " "configuration." |
|
UBR7200-6-RSINTRLVBLKSIZEADJUST |
6-Information |
[chars] burst's RS interleave block size in mod profile [dec] is adjusted to [dec] bytes. |
The RS interleave block size in the burst profile adjusted to a valid value. |
ubr7200 |
"Informational only" |
|
UBR7200-6-RSINTRLVBLKSIZEADJUST |
6-Information |
[chars] burst's RS interleave block size in mod profile [dec] is adjusted to [dec] bytes. |
The RS interleave block size in the burst profile adjusted to a valid value. |
ubr7200 |
"Informational only" |
|
UBR7200-6-RSINTRLVDEPTHADJUST |
6-Information |
[chars] burst's RS interleave depth in mod profile [dec] is adjusted to [dec]. |
The RS interleave depth in the burst profile adjusted to a valid value. |
ubr7200 |
"Informational only" |
|
UBR7200-6-RSINTRLVDEPTHADJUST |
6-Information |
[chars] burst's RS interleave depth in mod profile [dec] is adjusted to [dec]. |
The RS interleave depth in the burst profile adjusted to a valid value. |
ubr7200 |
"Informational only" |
|
UBR7200-6-RSINTRLVDISABLED |
6-Information |
[chars] burst's RS interleaver in mod profile [dec] is auto disabled. |
The RS interleaver in the burst profile is auto disabled. |
ubr7200 |
"Informational only" |
|
UBR7200-6-RSINTRLVDISABLED |
6-Information |
[chars] burst's RS interleaver in mod profile [dec] is auto disabled. |
The RS interleaver in the burst profile is auto disabled. |
ubr7200 |
"Informational only" |
|
UBR7200-6-SRCMP |
6-Information |
Cable Clock primary reference is midplane TDM clock |
Clockcard primary reference is from midplane TDM clock |
ubr7200 |
"Informational only" |
|
UBR7200-6-SRCMP |
6-Information |
Cable Clock primary reference is midplane TDM clock |
Clockcard primary reference is from midplane TDM clock |
ubr7200 |
"Informational only" |
|
UBR7200-6-USPRIMARYSFIDCONFLICT |
6-Information |
Assigned us primary sfid [dec] conflicts with existing us primary sfid [dec] for Cable modem [enet] on interface [chars] |
The assigned upstream primary SFID conflicts with the existing upstream primary SFID for the cable modem. |
ubr7200 |
"Informational only" |
|
UBR7200-6-USPRIMARYSFIDCONFLICT |
6-Information |
Assigned us primary sfid [dec] conflicts with existing us primary sfid [dec] for Cable modem [enet] on interface [chars] |
The assigned upstream primary SFID conflicts with the existing upstream primary SFID for the cable modem. |
ubr7200 |
"Informational only" |
|
UBR7200-7-PHY_CLK_MIS_DET_MSG |
7-Debug |
Clock misalignment detected on phy [dec]:\nIOS det count=[dec] bad DV count=[dec] total DV count=[dec] old cal data=0x%02x new cal data=0x%02x\n[chars] |
A phy clock misalignment has been detected and corrected. |
ubr10000 |
LOG_STD_NO_ACTION |
|
UBR7200-7-PHY_CLK_MIS_DET_MSG |
7-Debug |
Clock misalignment detected on phy [dec]:\nIOS det count=[dec] bad DV count=[dec] total DV count=[dec] old cal data=0x%02x new cal data=0x%02x\n[chars] |
A phy clock misalignment has been detected and corrected. |
ubr10000 |
LOG_STD_NO_ACTION |
|
UBR7200IPC-0-CLI_CONFIG |
0-Emergency |
CMTS[dec]/[dec]/[dec] schrp_cli_cmd failed in [chars] |
Most likely S/W failure |
ubr7200-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR7200IPC-1-DISCOVER_ENET |
1-Alert |
Failed to init Ethernet device [dec] |
The software could not initialize |
ubr7200-sw |
"Power down reseat the interface card " "and reboot. If the message recurs call your " "technical support representative for assistance." |
|
UBR7200IPC-1-DISCOVER_SAR |
1-Alert |
Failed to init SAR device [dec] |
The software could not initialize |
ubr7200-sw |
"Power down reseat the interface card " "and reboot. If the message recurs call your " "technical support representative for assistance." |
|
UBR7200IPC-1-SNMP_GETINDEX_FAIL |
1-Alert |
Cannot get SNMP physical Index for [chars] |
LC System initialization failure. |
ubr7200-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR7200IPC-1-UNKEVT |
1-Alert |
Subsystem unknown event:[dec] in [chars] for interface [chars] |
Subsystem received unknown event type. |
ubr7200-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR7200IPC-2-BADINTERFACE |
2-Critical |
Out of range Card interface [dec] on slot [dec] |
The software specified an out-of-range card interface. |
ubr7200-sw |
LOG_STD_ACTION |
|
UBR7200IPC-2-BADRSRCNUM |
2-Critical |
Invalid resource number from PXF [dec]. PLEASE REPORT THIS! |
The PXF hardware diversion path specified a bad resource number. |
ubr7200-sw |
LOG_STD_ACTION |
|
UBR7200IPC-2-BADSLOT |
2-Critical |
Out of range card slot index[dec] |
The software specified an out-of-range card slot index. |
ubr7200-sw |
LOG_STD_ACTION |
|
UBR7200IPC-2-BADSLOTSUBSLOT |
2-Critical |
Out of range card slot/subslot pair[dec]/[dec] |
The software specified an out-of-range card slot/subslot pair. |
ubr7200-sw |
LOG_STD_ACTION |
|
UBR7200IPC-2-CARDRECUR |
2-Critical |
Recursive loop while getting the daughtercard info for card type [dec] |
While getting the daughter card info for the chassismib the platform snmp code goes into an infinite loop. |
ubr7200-sw |
LOG_STD_ACTION |
|
UBR7200IPC-2-CARDTYPEERROR |
2-Critical |
card in slot [[dec]/[dec]] is of incorrect type 0x[hec] |
The card is of wrong type allowed in that slot |
ubr7200-sw |
LOG_STD_ACTION |
|
UBR7200IPC-2-CLI_UNSUPPORTED_CMD |
2-Critical |
cable modem <ipaddr/macaddr> cmd not supported on MC28U |
Currently unsupported command |
ubr7200-sw |
LOG_STD_NO_ACTION |
|
UBR7200IPC-3-CLI_CMD |
3-Error |
[dec]/[dec]: CLI cmd failed in function [chars] |
Most likely S/W failure |
ubr7200-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR7200IPC-3-CLI_IPC_MALLOC |
3-Error |
Memory allocation request failed in [chars] |
Couldn't allocate memory for distributed CLI operation |
ubr7200-sw |
"Use the show memory command to analyze memory usage." |
|
UBR7200IPC-3-DEACTIVATED |
3-Error |
card in slot [[dec]/[dec]] disabled. |
The card is being deactivated. |
ubr7200-sw |
LOG_STD_SH_TECH_ACTION |
|
UBR7200IPC-3-INITFAIL |
3-Error |
[chars] - initialization of interface failed |
Initialization of the specified interface failed. |
ubr7200-sw |
LOG_STD_SH_TECH_ACTION |
|
UBR7200IPC-3-IPCERR |
3-Error |
IPC message error [dec] |
Error from IOS IPC layer on linecard Port API port |
ubr7200-sw |
LOG_STD_ACTION |
|
UBR7200IPC-3-IPCFAIL |
3-Error |
[chars]: IPC command [chars] to interface failed in [chars] |
System IPC initialization failure. |
ubr7200-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR7200IPC-3-IPCOPENFAIL |
3-Error |
slot [dec]: could not open IPC port for port id %08x |
IPC port open to mcu card failed - indicates that the card is down or there is a transient failure |
ubr7200-sw |
LOG_STD_ACTION |
|
UBR7200IPC-3-LC_DEFOBJ |
3-Error |
Default linecard object invoked for type [dec] |
The default card IPC API object was invoked since there was no registered handler for that object |
ubr7200-sw |
LOG_STD_ACTION |
|
UBR7200IPC-3-LC_OBJERR |
3-Error |
[chars] |
A card IPC API object is not supported |
ubr7200-sw |
LOG_STD_ACTION |
|
UBR7200IPC-3-NOACK |
3-Error |
Access to [chars] temperature sensor failed |
Accesses to chassis temperature sensor failed. |
ubr7200-sw |
LOG_STD_SH_TECH_ACTION |
|
UBR7200IPC-3-PLUGIN_UNKNOWN |
3-Error |
Unknown card type [hec] in slot [dec]/[dec]. |
The card in the specified slot is not a known type. |
ubr7200-sw |
LOG_STD_ACTION |
|
UBR7200IPC-3-UNEXP_INTR |
3-Error |
Interrupt [chars] not expected masking off |
An interrupt of a certain type was signalled but the interrupt handler for this type of interrupt is not yet installed. |
ubr7200-sw |
"This problem should be self-correcting but indicates either " "a hardware or a software defect. If it's a hardware defect " "further problems are to be expected. If it's a software " "problem certain types of error and alarm conditions may be " "left undetected.\n" "Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBR7200IPC-4-MSGVERSION |
4-Warning |
Incompatible message version with slot [dec] |
There is incompatibility between the the message version being sent by the line card and the message version used by the RP/NPE. This type of incompatibility could happen if the RP/NPE and line card are using different IOS versions due to an RP/NPE oir event |
ubr7200-sw |
"A microcode reload will solve the problem. " |
|
UBR7200IPC-4-PCIVALID |
4-Warning |
PCI activation failed slot [dec] 0x[hec] |
The system received an invalid PCI signal from the port adapter. This is probably due to a hardware failure. |
ubr7200-sw |
"Refer to the configuration guidelines for the maximum allowed " "high and medium bandwidth port adapters for the system." |
|
UBR7200IPC-4-TEST |
4-Warning |
Test command no. [dec] executed by user |
Test command is executed by user. |
ubr7200-sw |
LOG_STD_NO_ACTION |
|
UBR7200IPC-6-CM_INCONSISTENCY |
6-Information |
CM state inconsistency [enet]msgp [enet] sid [dec] [dec] mac state [dec] hwidb [chars] |
Received INIT_CM for an online CM Copy the message and report to your technical support representative |
ubr7200-sw |
LOG_STD_ACTION |
|
UBR900-3-RESET_CONFIG_FILE_WATCHDOG_EXPIRED |
3-Error |
Cable Interface Reset due to config file watchdog timer |
Cable Interface Reset due to config file watchdog timer expiration\n |
- |
"" |
|
UBR900-3-RESET_DHCP_WATCHDOG_EXPIRED |
3-Error |
Cable Interface Reset due to DHCP watchdog timer expiration |
Cable Interface Reset due to dhcp watchdog timer expiration\n |
- |
"" |
|
UBR900-3-RESET_LOSS_OF_SYNC |
3-Error |
T05.0 Loss of Sync. Missed 5 in a row after having SYNCd at one time |
Cable Interface Reset due to loss of sync\n |
- |
"" |
|
UBR900-3-RESET_PRIVACY_WATCHDOG_EXPIRED |
3-Error |
Cable Interface Reset due to privacy watchdog timer |
Cable Interface Reset due to privacy watchdog timer expiration\n |
- |
"" |
|
UBR900-3-RESET_T2_EXPIRED |
3-Error |
R01.0 No Maintenance Broadcasts for Ranging opportunities received T2 timeout |
Cable Interface Reset due to t2 timeout\n |
- |
"" |
|
UBR900-3-RESET_T3_RETRIES_EXHAUSTED |
3-Error |
R03.0 Ranging Request Retries exhausted |
Cable Interface Reset due to t3 timeout\n |
- |
"" |
|
UBR900-3-RESET_T4_EXPIRED |
3-Error |
R04.0 Received Response to Broadcast Maintenance Request But no Unicast Maintenance opportunities received. T4 timeout. |
Cable Interface Reset due to t4 timeout\n |
- |
"" |
|
UBR900-3-RESET_T6_RETRIES_EXHAUSTED |
3-Error |
Cable Interface Reset due to t6 timeout |
Cable Interface Reset due to t6 timeout\n |
- |
"" |
|
UBR900-3-T3_RETRIES_EXHAUSTED_II |
3-Error |
R06.0 Started Unicast Maintenance Ranging no Response received. T3 time-out. |
Cable Interface Reset due to t3 timeout\n |
- |
"" |
|
UBR900-3-T3_TIMEOUT_I |
3-Error |
R02.0 No Ranging Response received T3 timeout |
t3 timeout\n |
- |
"" |
|
UBR900-3-T3_TIMEOUT_II |
3-Error |
R05.0 Started Unicast Maintenance Ranging no Response received. T3 time-out. |
Cable Interface Reset due to t3 timeout\n |
- |
"" |
|
UBR900-3-TOD_FAILED_TIMER_EXPIRED |
3-Error |
TOD failed but Cable Interface proceeding to operational state |
TOD failed but Cable Interface proceeding to operational state\n |
- |
"" |
|
UBR900-4-CORRUPT_SYSTEM_IMAGE |
4-Warning |
Modem System Image is corrupt. New image upgrade required |
Modem System Image is corrupt. New image upgrade required\n |
- |
"" |
|
UBR900-4-CORRUPT_SYSTEM_IMAGE_UPGRADING |
4-Warning |
Modem System Image is corrupt. Image upgrade reinitiated. |
Modem System Image is corrupt. Image upgrade reinitiated.\n |
- |
"" |
|
UBR900-4-DHCP_REQ_INFO_NOT_SUPPORTED |
4-Warning |
D03.0 Requested Info not supported |
Requested info not supported |
- |
"" |
|
UBR900-4-DHCP_RSP_OUT_OF_SPEC |
4-Warning |
D03.1 DHCP response doesn't contain ALL the valid fields as described in the RF spec Appendix C.1 |
response doesn't contain ALL the valid fields as described in the RF spec Appendix C.1 |
- |
"" |
|
UBR900-4-FAILED_TO_ACQUIRE_FEC |
4-Warning |
T02.0 Failed to acquire FEC framing. Error stats? Retry [dec]'s [dec] of bad frames |
Failed to acquire FEC framing |
- |
"" |
|
UBR900-4-FAILED_TO_ACQUIRE_MAC_FRAMING |
4-Warning |
T03.0 Failed to acquire MAC framing. Error stats? Retry [dec]'s [dec] of bad frames |
- |
- |
"" |
|
UBR900-4-FAILED_TO_ACQUIRE_MPEG2 |
4-Warning |
T2.1 Acquired FEC framing. Failed to acquire MPEG2 Sync. Retry [dec]`s |
Acquired FEC framing. Failed to acquire MPEG2 sync. |
- |
"" |
|
UBR900-4-FAILED_TO_ACQUIRE_SYNC |
4-Warning |
T01.0 Failed to acquire QAM/QPSK symbol timing. Error stats? Retry [dec]'s |
Failed to acquire QAM/QPSK symbol timing\n |
- |
"" |
|
UBR900-4-FAILED_TO_RECEIVE_SYNC |
4-Warning |
T04.0 Failed to Receive MAC SYNC frame within time-out period |
Failed to Receive MAC SYNC frame within time-out period |
- |
"" |
|
UBR900-4-INVALID_TOD |
4-Warning |
D04.0 Time of Day none set or invalid data |
Time of Day none set or invalid data |
- |
"" |
|
UBR900-4-INVALID_UCD |
4-Warning |
U02.0 UCD invalid or channel unusable |
Invalid UCD or channel unusable |
- |
"" |
|
UBR900-4-MAP_ARRIVED_TOO_LATE |
4-Warning |
M01.0 A transmit opportunity was missed because the MAP arrived too late |
A transmit opportunity was missed because the MAP arrived too late |
- |
"" |
|
UBR900-4-NO_UCD_RCVD |
4-Warning |
U01.0 No UCD's received. Time-out |
No UCD's Received. Time-out |
- |
"" |
|
UBR900-4-REINIT_MAC |
4-Warning |
R07.0 Unicast Ranging Received Abort Response. Reinitializing MAC. |
Unicast Ranging Received Abort Response. Reinitializing MAC. |
- |
"" |
|
UBR900-4-TFTP_FAILED_2 |
4-Warning |
D07.0 TFTP Request Failed OUT OF ORDER packets |
TFTP Request Failed OUT OF ORDER packets |
- |
"" |
|
UBR900-4-TFTP_FAILED_3 |
4-Warning |
D08.0 TFTP complete but failed Message Integrity CheckMIC |
TFTP complete but failed Message Integrity CheckMIC |
- |
"" |
|
UBR900-4-TFTP_NO_RSP |
4-Warning |
D05.0 TFTP Request sent No Response/No Server. |
TFTP Request sent No Response/No Server |
- |
"" |
|
UBR900-4-TFTP_RQ_FAILED_1 |
4-Warning |
D06.0 TFTP Request Failed configuration file NOT FOUND |
TFTP Request Failed configuration file NOT FOUND |
- |
"" |
|
UBR900-4-TOD_NO_RSP |
4-Warning |
D04.1 Time of Day request sent no Response received |
Time of Day request sent no Response received |
- |
"" |
|
UBR900-4-TOD_RSP_INVALID |
4-Warning |
D04.2 Time of Day Response received but invalid data/format |
Time of Day Response received but invalid data/format |
- |
"" |
|
UBR900-4-UCC_REQ_INVALID |
4-Warning |
C01.0 UCC-REQ received with invalid or out of range US Channel ID. |
UCC-REQ received with invalid or out of range US Channel ID |
- |
"" |
|
UBR900-4-UCD_INVALID_OR_OUT_OF_ORDER_CCC |
4-Warning |
U05.0 UCD received with invalid or out of order Configuration Change Count |
UCD received with invalid or out of order Configuration Change Count |
- |
"" |
|
UBR900-4-UNBALE_TO_TX_UCC_RSP |
4-Warning |
C02.0 UCC-REQ received unable to send UCC-RSP no TX opportunity. |
UCC-REQ received unable to send UCC-RSP no TX opportunity. |
- |
"" |
|
UBR900-4-US_CHANNEL_PARM_NOT_SET |
4-Warning |
U06.0 US Channel wide parameters not set before Burst Descriptors |
US Channel wide parameters not set before Burst Descriptors |
- |
"" |
|
UBR900-4-VALID_UCD_AND_SYNC_NO_MAPS |
4-Warning |
U04.0 UCD and SYNC are valid No MAPS for THIS channel |
UCD and SYNC are valid No MAPS for THIS channel |
- |
"" |
|
UBR900-4-VALID_UCD_NO_SYNC |
4-Warning |
U03.0 UCD valid But no SYNC received. TIMED OUT. |
UCD valid But not SYNC received. TIMED OUT. |
- |
"" |
|
UBR900-6-IMAGE_UPGRADE_FAILED_IMAGE_CHECK |
6-Information |
System Image Upgrade FAILED due to unrecognizable or corrupt image.\n |
System Image Upgrade FAILED due to unrecognizable or corrupt image.\n |
- |
"" |
|
UBR900-6-IMAGE_UPGRADE_FAILED_TFTP |
6-Information |
System Image Upgrade FAILED due to excessive TFTP failures.\n |
System Image Upgrade FAILED due to excessive TFTP failures.\n |
- |
"" |
|
UBR900-6-IMAGE_UPGRADE_INITIATED |
6-Information |
System Image Upgrade initiated |
System Image Upgraded has been initiated.\n |
- |
"" |
|
UBR900-6-IMAGE_UPGRADE_INTERRUPTED |
6-Information |
System Image Upgrade interrupted during transfer. Upgrade reinitiated\n |
System Image Upgrade interrupted during transfer. Upgrade reinitiated\n |
- |
"" |
|
UBR900-6-IMAGE_UPGRADE_SUCCESSFUL |
6-Information |
System Image Upgrade Complete. |
System Image Upgrade Complete.\n |
- |
"" |
|
UBR900-6-IMAGE_UPSTREAM_POWER_HIGH |
6-Information |
Upstream Power required at modem registration near maximum\n |
Upstream Power required at modem registration near maximum\n |
- |
"" |
|
UBR900-6-NO_DHCP_OFFER |
6-Information |
D01.0 Discover sent no offer received No available DHCP Server |
D01.0 Discover sent no offer received No available DHCP Server |
- |
"" |
|
UBR900-6-NO_DHCP_RESPONSE |
6-Information |
D02.0 Request sent no Response |
Request sent no Response |
- |
"" |
|
UBR900-6-SYNC_LOST_AND_REACQUIRED |
6-Information |
Downstream Sync lock lost and reacquired before timeout expired\n |
Downstream Sync lock lost and reacquired before timeout expired\n |
- |
"" |
|
UBR900-6-UNDEFINED_HDR_RECEIVED |
6-Information |
Mac Messages received with undefined header\n |
Mac Messages received with undefined header\n |
- |
"" |
|
UBR900-7-RNG_REQ_TRANSMITTED |
7-Debug |
Periodic ranging request message transmitted. |
Periodic ranging message transmitted |
- |
"" |
|
UBR900-7-RNG_RSP_MSG_RCVD |
7-Debug |
Periodic ranging response message received. |
Periodic ranging response message received |
- |
"" |
|
UBRCCE-0-CLI_CONFIG |
0-Emergency |
CMTS[dec]/[dec]/[dec] schrp_cli_cmd failed in [chars] |
Most likely S/W failure |
ubrcce-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UBRCCE-6-CM_INCONSISTENCY |
6-Information |
CM state inconsistency [enet]msgp [enet] sid [dec] [dec] mac state [dec] hwidb [chars] |
Received INIT_CM for an online CM Copy the message and report to your technical support representative |
ubrcce-sw |
LOG_STD_ACTION |
|
UBRCCE-6-DS_SFID_INCONSISTENCY |
6-Information |
DS-SF found: SFID [dec] type [dec] MAC [enet][enet] prim_sid [dec][dec] |
The RP and LC have different downstream service-flows for the same SFID. The problem should resolve by itself. If it persists report to your technical support representative |
ubr10k-sw |
LOG_STD_ACTION |
|
UBRCCE-6-DSD_SRV_FLOW_ERROR |
6-Information |
SFID found: SFID [dec] type [dec] MAC [enet][enet] prim_sid [dec][dec] |
The RP and LC have different service-flows for the same SFID. The problem should resolve by itself. If it persists report to your technical support representative |
ubr10k-sw |
LOG_STD_ACTION |
|
UBRCCE-6-HA_CM_INCONSISTENCY |
6-Information |
CM sync received [enet]msgp [enet] sid [dec] [dec] mac state [dec] hwidb [chars] |
Received sync message on secondary SUP for mismatched entry This problem should resolve by itself. If it persists report to your technical support representative |
ubrcce-sw |
LOG_STD_ACTION |
|
UBRCCE-6-RCC_WB_INCONSISTENCY |
6-Information |
[chars] RCC-[dec] [chars] mismatch with DSBG-[dec] [chars] |
Receive chanel set in RCC is mismatch with the Wideband. |
ubrcce-sw |
LOG_STD_ACTION |
|
UBRCCE-6-STDBY_CM_INCONSISTENCY |
6-Information |
CM sync received [enet]msgp [enet] sid [dec] [dec] mac state [dec] hwidb [chars] |
Received sync message on secondary SUP for mismatched entry This problem should resolve by itself. If it persists report to your technical support representative |
ubrcce-sw |
LOG_STD_ACTION |
|
UBRCCE-6-US_SFID_INCONSISTENCY |
6-Information |
US-SF found: SFID [dec] type [dec] sid [dec][dec] MAC [enet][enet] prim_sid [dec][dec] |
The RP and LC have different upstream service-flows for the same SFID. The problem should resolve by itself. If it persists report to your technical support representative |
ubr10k-sw |
LOG_STD_ACTION |
|
UBRIFCON-3-NOPROC |
3-Error |
Unable to create the if-console background process |
The system wants to create a background process to handle if-console data from the line cards but is unsuccessful. |
ubr10k-sw |
"Gather information about the number of processes running and " "amount of memory in the system and file a bug." |
|
UBRIFCON-3-NOQUEUE |
3-Error |
Unable to create the if-console background queue |
The system wants to create a background process queue to handle if-console data from the line cards but is unsuccessful. |
ubr10k-sw |
"Gather information about the number of processes running and " "amount of memory in the system and file a bug." |
|
UBRLCCOREDUMP-2-EOM |
2-Critical |
Cannot allocation memory for [chars]\n |
The system cannot allocate memory for the coredump subsystem. |
ubr10k-sw |
"Add more memory." |
|
UBRLCCOREDUMP-3-BADCLOSE |
3-Error |
Can't close slave core socket for slot [dec]/[dec] |
The system just finished dumping a core file from a line card. It tried to close this file on the remote system and failed. |
ubr10k-sw |
"Debug network connections and user priviledges." |
|
UBRLCCOREDUMP-3-BADOPEN |
3-Error |
Can't open slave core socket for slot [dec]/[dec] |
The system wants to dump a core file to a remote sytem but it is unable to open the remote file |
ubr10k-sw |
"Check to make sure the remote system is accessable and the " "protocol is set up correctly." |
|
UBRLCCOREDUMP-3-BADSLOTNUMBER |
3-Error |
Refusing dump because card slot number is out of bounds for card [dec]/[dec]. |
The NPE/PRE card has refused this dump because slot number is out of bounds. |
ubr10k-sw |
"Check IPC debug message for malformed packet" |
|
UBRLCCOREDUMP-3-BADWRITE |
3-Error |
Can't write [chars] to slave core socket for slot [dec]/[dec] |
The system is trying to write a core dump file to a remote sytem. The file was opened and an error occurred during a write to the file |
ubr10k-sw |
"Check network and disk space available." |
|
UBRLCCOREDUMP-3-ILLMSG |
3-Error |
Coredump message received from slot [dec]/[dec] not in dump state\n |
- |
- |
- |
|
UBRLCCOREDUMP-3-ILLNVGEN |
3-Error |
Illegal call to cr10k_rp_lc_cfg_coredump_nvgen |
The NVGEN routine was called but nvgen was not set. |
ubr10k-sw |
"Gather information about the processes running on this platform " "and the traceback and file a bug." |
|
UBRLCCOREDUMP-3-ILLTD |
3-Error |
Testdump only valid on line cards not allowed on PREs\n |
You cannot run a line card coredump test for an PRE. |
ubr10k-sw |
"Do not do this." |
|
UBRLCCOREDUMP-3-NOMSG |
3-Error |
No message on queue |
A core dump message from a line card that the should not be dumping core arrived at the PRE. |
ubr10k-sw |
"Gather information about the state of linecards and file a bug." |
|
UBRLCCOREDUMP-3-NOPROC |
3-Error |
Unable to create data handler process |
The system wants to write a core dump file to a remote system but it is unable to start a process to dump the file. |
ubr10k-sw |
"Gather information about the number of processes running and " "amount of memory in the system and file a bug." |
|
UBRLCCOREDUMP-3-NOQUEUE |
3-Error |
Cannot create queue to receive dump packets for slot [dec]/[dec] |
The system is trying to write a core dump file to a remote sytem. It could not create a queue to hold dump data coming from the line cards. |
ubr10k-sw |
"Add memory." |
|
UBRLCCOREDUMP-3-REFUSAL |
3-Error |
Refusing [chars] dump for card [dec]/[dec]. |
The PRE/NPE card has refused this dump because CLI is not configured for it or file access voilation on the tftp server. |
ubr10k-sw |
"Check exception-slave CLI on NPE" |
|
UBRLCCOREDUMP-3-TOOLONGFILENAME |
3-Error |
Filename for coredump file is too long for slot [dec]/[dec] |
Filename is too long for core dump file |
ubr10k-sw |
"Reduce the length of coredump filename string via CLI" |
|
UBRLCCOREDUMP-4-TIMEOUT |
4-Warning |
[chars] major [dec] minor [dec] |
The system is trying to write a core dump file but the PRE timed out waiting for data from the line card. |
ubr10k-sw |
"Gather information about the line card and file a bug." |
|
UBRLCCOREDUMP-6-LERP |
6-Information |
Cannot configure linecard exceptions for [chars] PRE |
The exception linecard commands can only be used to configure exceptions on a line card. PRE are not allowed. |
ubr10k-sw |
"Use the exception command without linecard to configure PRE core dumps." |
|
UBRSNMP-0-SNMP_SET_IPC |
0-Emergency |
Schooner SNMP SET[dec]/[dec] [chars] failed |
SNMP SET failed due to either IPC failure or line card SET failed |
ubr7200-sw |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UC_SAF-3-COMM_DECODE_ERR |
3-Error |
[chars] while decoding [chars] |
Error occurred while trying to decode the SAF advertisement |
voice-saf |
"Turn on error debugs and re-publish the specified " "instance. Based on the information in the error logs check and correct " "the configuration on the remote publisher" |
|
UC_SAF-3-COMM_ENCODE_ERR |
3-Error |
[chars] while encoding element [chars] |
Error occurred while trying to encode the client supplied data |
voice-saf |
"Modify the element that failed to encode using " "client's configuration clis" |
|
UC_SAF-3-COMM_FWDR_ERR |
3-Error |
[chars] for operation [chars] on instance [[dec].[dec].[dec].[dec]] sub-service [[dec]] for client [[chars]] on channel [[dec]] |
Error occurred while trying to request an action from SAF Forwarder |
voice-saf |
"If the failure is due to lack of memory then check the size of" " free memory to make sure there is enough memory to run SAF service. " "If the error is due to mismatch between client and forwarder then" " undo the current operation and retry. " "If the error is due to publish data is too large then reduce the amount of" " data to be advertised and retry" |
|
UC_SAF-3-COMM_FWDR_REG_ERR |
3-Error |
[chars] for operation [chars] for client [[chars]] on channel [[dec]] |
Error occurred while trying to request an action from SAF Forwarder |
voice-saf |
"If the failure is due to lack of memory then check the size of" " free memory to ensure there is enough memory to run SAF service. " "If the failure is due to invalid AS or vrouter name check the values" "configured in the client with those of the Forwarder. " "If the error is due to mismatch between client and forwarder then" " undo the current operation and retry" |
|
UC_SAF-3-COMM_INT_ERR |
3-Error |
Internal error occurred: [chars] |
- |
voice-saf |
"If the error is due to lack of memory check the size of free memory" " to make sure there is enough to run SAF service" |
|
UC_SAF-3-COMM_NOTIFY_ERR |
3-Error |
[chars] for operation [chars] on instance [[dec].[dec].[dec].[dec]] sub-service [[dec]] for client [[chars]] on channel [[dec]] |
Error occurred while acting upon a notification from SAF Forwarder |
voice-saf |
"If the failure is due to lack of memory then check the size of" " free memory to make sure there is enough memory to run SAF service. " "If the error is due to invalid data received in the SAF advertisement " "turn on error debugs and re-publish the service from the specified " "instance. Based on the information in the error debugs check and correct " "the configuration on the remote publisher" |
|
UC_SAF-3-COMM_OUTOFSYNC_ERR |
3-Error |
[chars] error occurred with client [[chars]] on channel[[dec]] |
COMM process is out of sync with client |
voice-saf |
"Disable/delete the channel and retry the operation. " "If that does not help then shutdown and restart the " "client's SAF service" |
|
UC_SAF-3-VSAF_CLIENT_COMM_QUEUE_ERROR |
3-Error |
Unable to enqueue uc-comm event [chars] [dec] to process watched queue |
- |
- |
- |
|
UC_SAF-3-VSAF_CLIENT_INSV_ERR |
3-Error |
Could not bring voice saf client in service\n |
Failed to instantiate client abstraction or initialization/ registration with other support modules has failed while voice service saf command was executed |
voice-saf |
"Check the size of free memory to make sure there is enough memory " "to run SAF service" |
|
UC_SAF-3-VSAF_CLIENT_INTERNAL |
3-Error |
[chars] |
An internal software error has occurred |
voice-saf |
LOG_STD_SH_TECH_ACTION |
|
UC_SAF-3-VSAF_CLIENT_PROCESS_CONTROL_ERR |
3-Error |
Client process event loop detected - [chars] |
Invalid state or unexpected events detected at the client manager process execution |
voice-saf |
LOG_STD_ACTION |
|
UC_SAF-3-VSAF_CLIENT_SUBS_NOTIFICATION_ERROR |
3-Error |
Error while adding or updating subscription notification from instance [dec]:[dec].[dec].[dec].[dec] |
Subscription notification received from the specified instance could not be added in the database. This could be because none of the advertised patterns were found to be valid or trunk-route parameters were invalid or the SAF DN database was already full. |
voice-saf |
"If the error is due to invalid advertisement " "turn on error debugs and re-publish the specified instance. " "Based on the error logs check and correct the configuration " "on the remote publisher " |
|
UC_SAF-3-VSAF_CLIENT_TASK_BAG_ERROR |
3-Error |
Error while performing task bag [chars] corresponding to task event [dec] job. |
A transient object that carries task parameters could not be instantiated or is corrupted. This may result in improper execution of the associated task which inturn can affect the ongoing operation. |
voice-saf |
"Check the size of free memory to make sure there is enough memory." |
|
UC_SAF-3-VSAF_CLIENT_TASK_QUEUE_ERROR |
3-Error |
Unable to enqueue task event [chars] [dec] to process watched queue |
- |
- |
- |
|
UC_SAF-6-COMM_CHANNEL_UNREG |
6-Information |
[chars] for client [[chars]] on channel [[dec]] could not be completed because channel was unregistered |
The most likely reason could be that the forwarder sent REGISTRATION notification message to UC SAF COMM process which causes the channel to be unregistered. Any messages from VSAF client in the interim for that channel will fail |
voice-saf |
"Take the necessary steps to re-instate the vrouter" " configurations. Then do shut followed by no shut " "on VSAF channel cli" |
|
UC_SAF-6-VSAF_CHANNEL_REGISTER |
6-Information |
Client channel id [dec] is [chars]\n |
Configured voice saf operational state |
voice-saf |
"If the channel went down unintentionally it is probably " "due to misconfiguration resulting in error. Check if the " "configured channel arguments matches those under router " "eigrp command level. Do shut/no shut under the channel " "to reset the voice saf channel operations" |
|
UC_SAF-6-VSAF_SERVICE_PUBLISH_INVALID_PROFILE |
6-Information |
Attempted publish of service [chars] [dec] with tag [dec] failed due to invalid |
The user or system triggered service advertisement failed due to the detection of invalid or incomplete profile. |
voice-saf |
"Please check for the completeness of the service profile " "constructs. If they look ok pls check the status of the " "interfaces used under the trunk-route profile session " "parameters." |
|
UC_SAF-6-VSAF_SERVICE_WITHDRAWN_INVALID_PROFILE |
6-Information |
Service [chars] [dec] with inst-id <[dec].[dec].[dec].[dec]> has been withdrawn due to |
Withdrawal of service triggered due to change in state of configured profile. |
voice-saf |
"If the service was unintentionaly withdrawn it was probably " "due to certain critical parameters missing in the profile or " "if the state of the hardware used in the profile is down. " "Say ip interface state used in the trunk-route is down. " "Please verify and re-do the publish command from the config or " "exec level." |
|
UCODE-3-BADCHKSUM |
3-Error |
Bad checksum in [chars] found 0x[hec] expected 0x[hec] |
- |
- |
"Reload the microcode. If the message recurs call your technical\n\ support representative for assistance." |
|
UCODE-3-BADHWVER |
3-Error |
Ucode file [chars] requires [chars] version [dec].x hardware |
A mismatch was detected during an attempt to load a microcode file\n\ into an interface processor. The hardware requires a different version\n\ than the one specified. |
- |
"Use the required microcode version." |
|
UCODE-3-HDRCORRUPT |
3-Error |
Ucode header corrupted in [chars] found 0x[hec] expected 0x[hec] |
- |
- |
"Reload the microcode. If the message recurs call your technical\n\ support representative for assistance." |
|
UCODE-3-IPCBUFFAIL |
3-Error |
Unable to obtain IPC resources |
- |
- |
"Certain interface processors will not load properly. Try the reload\n\ command again. If this message recurs call your technical support\n\ representative for assistance." |
|
UCODE-3-IPCINITFAIL |
3-Error |
Unable to initialize IPC [chars] services |
- |
- |
"Certain Interface Processors will not load properly. The router must\n\ be reloaded to clear the problem." |
|
UCODE-3-IPCINVALID |
3-Error |
Invalid IPC request [dec] received from [hec] |
- |
- |
"Verify that the proper revisions of code are selected." |
|
UCODE-3-LDFAIL |
3-Error |
Unable to download ucode from [chars] in slot [dec] trying [chars] ucode |
For some reason the microcode file specified by the configuration is\n\ not suitable for downloading or another error occurred. The onboard\n\ ROM microcode will be loaded so the interface can remain\n\ operational. |
- |
"Attempt to reload the microcode. If the message recurs call your\n\ technical support representative for assistance." |
|
UCODE-3-NOBUF |
3-Error |
Unable to allocate memory for ucode buffer |
A buffer is required to decompress microcode before loading it into an\n\ interface processor. This buffer could not be allocated for some\n\ reason. |
- |
"Copy the message exactly as it appears and report it your technical\n\ support representative." |
|
UCODE-3-NOFILE |
3-Error |
Ucode file [chars] not found system ucode loaded in slot [dec] |
The file specified by the configuration was not found in Flash. The\n\ onboard ROM microcode will be loaded so the interface can remain\n\ operational. |
- |
"Use show flash to determine if the file is located in Flash. If the\n\ file is there attempt to reload the microcode. If the message recurs\n\ call your technical support representative for assistance." |
|
UCODE-3-NOMEMORY |
3-Error |
Unable to allocate memory during microcode reload |
An attempt at memory allocation failed while downloading microcode \n\ to Interface processor. |
- |
"Copy the message exactly as it appears and report it your technical\n\ support representative." |
|
UCODE-3-NOROM |
3-Error |
Invalid attempt to load ROM ucode in slot [dec] |
Some interface processors cannot load microcode from ROM. |
- |
"Remove the erroneous configuration statement." |
|
UCODE-3-RDFAIL |
3-Error |
Unable to read ucode file [chars] from flash |
For some reason the microcode file was not read from Flash. Flash\n\ might be locked by another process or otherwise unavailable. |
- |
"Use the show flash command to determine whether Flash is in use and\n\ issue another microcode reload when Flash is free. If the message\n\ recurs call your technical support representative for assistance." |
|
UCODE-3-SRCTYPE |
3-Error |
Invalid Ucode source type [dec] |
Microcode source type as specified is not supported on the\n\ given platform |
- |
"Verify that the proper revisions of code are selected." |
|
UCODE-3-TOOBIG |
3-Error |
File [chars] at length [dec] is too long for buffer size [dec] |
The file is too large for the buffer. The onboard ROM microcode will\n\ be loaded. |
- |
"If the error message recurs after the onboard ROM microcode is loaded\n\ call your technical support representative for assistance." |
|
UCODE-3-VERSIONCK |
3-Error |
Inappropriate version [dec].[dec] for [chars] |
An attempt was made to load an inappropriate version of microcode. |
- |
"Copy the message exactly as it appears and report it your technical\n\ support representative." |
|
UCODE-3-WRONGHARD |
3-Error |
[chars] is [chars] ucode not [chars] microcode/hardware mismatch |
The specified microcode file is for a different interface processor\n\ than specified in the configuration. The user has made a configuration\n\ error. The onboard ROM microcode will be loaded. |
- |
"Reenter your microcode configuration command after confirming the\n\ interface type and reload the microcode." |
|
UCODE-5-OBSOLETE |
5-Notice |
FDDI unit [dec] has obsolete microcode: please upgrade it |
This message occurs when an FDDI interface processor is found running\n\ microcode that does not support microcode CMT which is required for\n\ all software releases from 10.2 on. |
- |
"Upgrade the microcode on the interface processor." |
|
UDEV-3-UDEVPERMS |
3-Error |
An invalid permissions value [chars] was found in a udev file |
The udev files for a particular filesystem contain a description the file system. If the permissions attribute is not recognized then this file system may run with incorrect permissions. |
iosxe-chassismgr |
LOG_STD_NO_ACTION |
|
UDLD-3-UDLD_IDB_ERROR |
3-Error |
UDLD error handling [chars] interface: [chars] |
A softare error occurred in UDLD processing associated with a specific\n\ interface. |
udld |
LOG_STD_SH_TECH_ACTION |
|
UDLD-3-UDLD_INTERNAL_ERROR |
3-Error |
UDLD internal error: [chars] |
A softare sanity check failed in the course of UDLD processing. |
udld |
LOG_STD_SH_TECH_ACTION |
|
UDLD-3-UDLD_INTERNAL_IF_ERROR |
3-Error |
UDLD internal error interface [chars]: [chars] |
A softare sanity check failed in the course of UDLD processing. |
udld |
LOG_STD_SH_TECH_ACTION |
|
UDLD-4-UDLD_PORT_DISABLED |
4-Warning |
UDLD disabled interface [chars] [chars] detected |
An interface was disabled because UDLD protocol detected the cause\n\ indicated on the interface indicated. Cause is likely due to bad\n\ interface hardware or cable misconfiguration. User should investigate. |
udld |
LOG_STD_SH_TECH_ACTION |
|
UDLD-4-UDLD_PORT_FAILURE |
4-Warning |
UDLD failure reported per user request interface [chars] [chars] detected. |
An interface failure was reported because UDLD protocol detected the cause\n\ indicated on the interface. Cause is likely due to bad interface hardware\n\ or cable misconfiguration. Interface not err-disabled as user choose to\n\ see error-report. User should investigate and take action. |
udld |
LOG_STD_SH_TECH_ACTION |
|
UDLD-6-UDLD_PORT_RESET |
6-Information |
UDLD reset interface [chars] |
A port which had been disabled for UDLD has been reset. |
udld |
LOG_STD_SH_TECH_ACTION |
|
UDP-7-GLEAN_DISABLED |
7-Debug |
ARP gleaning from UDP has been disabled. |
The ARP gleaning from UDP has been disabled. |
- |
"If you want ARP gleaning from UDP do ip arp gleaning udp." |
|
UDP-7-NO_OUTINTF |
7-Debug |
No output interface for pkts received on [chars] forwarding from [inet] to [inet] |
Output interface is NULL while forwarding UDP packets |
- |
"LOG_STD_ACTION" |
|
UEA_CHOC_DSX-3-NULL_SPA_PTR |
3-Error |
- |
The pointer to a SPA value is of a null value. |
uea-im-tdm |
LOG_STD_SH_TECH_ACTION |
|
UEA_IDMGR-3-RESERVE_FAIL |
3-Error |
IDMGR ID [chars] Failure func [chars] line [dec] Feat [dec] ID [dec] |
IDMGR API failed |
rsp3-infra |
"Please fix it" |
|
UEA_IDMGR-3-RESERVE_FAIL |
3-Error |
IDMGR ID [chars] Failure func [chars] line [dec] Feat [dec] ID [dec] |
IDMGR API failed |
dominica-infra |
"Please fix it" |
|
UEA_IM-3-CREATE_TDLH_FAILURE |
3-Error |
Failed to create SPA [dec]/[dec] handle |
Failed to create message handle for SPA communication. |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-3-CREATE_TDLMSG_FAILURE |
3-Error |
Failed to create [chars] message for [chars]. |
Failed to create/allocate necessary TDL message for SPA communication. |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-3-CREATION_FAILURE |
3-Error |
slot=[dec] subslot=[dec] spa_type=0x[hec] lc_type=0x[hec]. |
Failed to create a SPA object. |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-3-DIAG_CONFIG |
3-Error |
[chars] did not complete [dec]/[dec] |
An error has occured during diagnostic test. |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-3-DISPATCH_INIT_TDLH_FAILURE |
3-Error |
Failed to initialize dispatch path for SPA [dec]/[dec] handle |
Failed to initialize dispatch path handle for SPA communication. |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-3-DOMAIN_TDLH_FAILURE |
3-Error |
[chars] rc = [dec] |
Failed to bind message handle for SPA communication. |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-3-GET_ATTR_FAILURE |
3-Error |
Failed to get attribute pointer |
Failed to get SPA attribute information. |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-3-INVALID_CPU_NUM |
3-Error |
cpu= [dec] max cpu = [dec] |
An invalid CPU number is specified in one of the internal APIs. |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-3-INVALID_IF_INDEX |
3-Error |
index= [dec] spaType=0x[hec] slot [dec] subSlot [dec] slotunit [dec] vc [dec] |
Index for the interface is not valid. |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-3-INVALID_INDX_RANGE |
3-Error |
index1= [dec] index2= [dec] maxIndex= [dec] |
An invalid index range is specified in one of the internal APIs. |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-3-INVALID_RP_SLOT_NUM |
3-Error |
slot= [dec] max slot = [dec] |
An invalid RP slot number is specified in one of the internal APIs. |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-3-INVALID_SLOT_NUM |
3-Error |
slot= [dec] max slot = [dec] |
An invalid slot number is specified in one of the internal APIs. |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-3-INVALID_SLOTUNIT_NUM |
3-Error |
cardwide-port = [dec] max cardwide-port = [dec] |
An invalid cardwide-port number is specified in one of the internal APIs. |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-3-INVALID_SPA_TDL_CCAPI_USAGE |
3-Error |
- |
Incorrect usage of an internal API that should only be used on CC. |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-3-INVALID_SUBSLOT_NUM |
3-Error |
subslot= [dec] max subslot = [dec] |
An invalid subslot number is specified in one of the internal APIs. |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-3-IPC_FAILURE |
3-Error |
IPC failure while [chars] |
An error has occurred while prepareing or sending an IPC message. |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-3-MEM_ALLOC_ERROR |
3-Error |
[chars] |
Memory allocation error. |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-3-NULL_SPA_PTR |
3-Error |
- |
Pointer to a SPA object is NULL. |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-3-NULL_VFT |
3-Error |
[chars] virtual function table is not initialized. spaType=0x[hec] |
A required function table is not initialized |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-3-NULL_VFUNC |
3-Error |
[chars] vector is not initialized. spaType=0x[hec] |
A required function vector is not initialized |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-3-POWER_CYCLE |
3-Error |
[chars] occurred on Shared Port Adapter [dec]/[dec] |
An error has occurred which will cause the \n\ Shared Port Adapter to be power cycled |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-3-SENDCFGFAIL |
3-Error |
Failed to send configuration for [chars] to carrier-card for subslot=[dec]/[dec] |
Sending configuration failed. |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-3-SETUP_TDLH_FAILURE |
3-Error |
Failed to set the alloc/free handler for SPA [dec]/[dec] handle |
Failed to set the alloc/free handler for SPA communication. |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-3-SPA_CREATION_FAILURE |
3-Error |
slot=[dec] subslot=[dec] PID=[chars] lc_type=0x[hec]. |
Failed to create a SPA object. |
asr1k-io-internal |
LOG_STD_SH_TECH_ACTION |
|
UEA_IM-6-TDLMSG_INCOMPATIBLE |
6-Information |
Failed to copy message [chars] to buffer not allowed for current domain. |
Failure to marshal a message indicates an incompatibility with the intended recipient. |
asr1k-spa-infra |
LOG_STD_SH_TECH_ACTION |
|
UEA_INFO-3-MAX_TDM_PW_PER_IM_EXCEEDED |
3-Error |
TDM PWs configured on SPA[chars] subslot [dec]/[dec] exceeds |
Number of TDMoMPLS intd labels exceeded supported scale |
- |
"Please reduce the number of TDM PW's per Port to supported scale" |
|
UEA_INFO-3-MAX_TDM_PW_PER_PORT_EXCEEDED |
3-Error |
TDM PWs configured on SPA[chars] Interface [chars] |
Number of TDMoMPLS intd labels exceeded supported scale |
- |
"Please reduce the number of TDM PW's per Port to supported scale" |
|
UEA_IOMD_SPA-1-AUTHENTICATION_FAIL |
1-Alert |
IM authentication failed for slot/bay [dec]/[dec] |
This Module may not have been manufactured by Cisco or with Cisco's authorization. This product may contain software that was copied in violation of Cisco's license terms. If your use of this product is the cause of a support issue Cisco may deny operation of the product support under your warranty or under a Cisco technical support program such as Smartnet. Please contact Cisco's Technical Assistance Center for more information. |
iomd-infra |
LOG_STD_ACTION |
|
UEA_IOMD_SPA-3-APS_CFG_FAIL |
3-Error |
Failed to configure APS on [chars]: [chars]. |
The SPA driver failed to configure APS on an interface. |
asr900-im |
LOG_STD_ACTION |
|
UEA_IOMD_SPA-3-APS_PGP_FAIL |
3-Error |
APS PGP Message send failed toslot/tobay [dec]: [dec]. |
APS PGP between working and protect has failed |
asr900-im |
LOG_STD_ACTION |
|
UEA_IOMD_SPA-3-BAD_IFCOMTYPE |
3-Error |
Bad ifcom message type=[dec] |
- |
asr900-im |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
UEA_IOMD_SPA-3-BADMALUCMD |
3-Error |
Unsupported MALU command [dec] arg=[hex] pascb=[hex] |
- |
asr900-im |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
UEA_IOMD_SPA-3-BADMALUCMD2 |
3-Error |
Unsupported MALU cmd/arg0=0x%04x%04x arg1arg2=0x%04x%04x hwidb=[chars] |
- |
asr900-im |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
UEA_IOMD_SPA-3-BADSWITCHOVER |
3-Error |
[chars]: Invalid HA event detected: [chars] |
HA switch over event comes before finishing inialization. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_IOMD_SPA-3-C2W_MAIN_INIT_FAIL |
3-Error |
Failed to initialize SPA main c2w bus for subslot [dec] status = [dec] |
The SPA driver is not able to initialize SPA main c2w. This indicates a hardware error. |
asr900-im |
LOG_STD_NO_ACTION |
|
UEA_IOMD_SPA-3-CMDNOINT |
3-Error |
HWIDB Null for command [dec] port [hex] |
The Route Processor passed down a port number that is unknown on the\n\ carrier card. |
asr900-im |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
UEA_IOMD_SPA-3-DEVICE_ERROR |
3-Error |
subSlot [dec] spatype 0x[hec]. Device error: [chars] |
An error related to a device on the SPA is detected. |
asr900-im |
LOG_STD_SH_TECH_ACTION |
|
UEA_IOMD_SPA-3-EFC_CHAN_ERR |
3-Error |
EFC error - interface [chars] vc [dec] anyphy [dec] err_code [dec] : [chars] |
Failed to configure efc channel/parameters |
asr900-im |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance " LOG_STD_ACTION |
|
UEA_IOMD_SPA-3-EFC_FC_MAP_FAIL |
3-Error |
Failed to update EFC flow control identifier for interface [chars] status = [dec] |
The SPA driver is not able to update the datapath EFC flow control identifier for the interface specified in the message. This indicates a hardware error. |
asr900-im |
LOG_STD_NO_ACTION |
|
UEA_IOMD_SPA-3-EFC_PROV_FAIL |
3-Error |
Failed to provision EFC for interface [chars] status = [dec] |
The SPA driver is not able to provision EFC for the interface specified in the message. This indicates a hardware error. |
asr900-im |
LOG_STD_NO_ACTION |
|
UEA_IOMD_SPA-3-EFC_UNPROV_FAIL |
3-Error |
Failed to unprovision EFC for VC [chars] status = [dec] |
The SPA driver is not able to unprovision EFC for the interface specified in the message. This indicates a hardware error. |
asr900-im |
LOG_STD_NO_ACTION |
|
UEA_IOMD_SPA-3-FAST_NOTIFY_ERROR |
3-Error |
Failed to send fast notification to [chars] for [chars] [chars]. |
The SPA driver failed to deliver a fast notification. |
asr900-im |
LOG_STD_ACTION |
|
UEA_IOMD_SPA-3-FCI_NOT_SET |
3-Error |
Bay [dec] - FCI type not set |
An FCI type of zero was detected |
asr900-im |
LOG_STD_ACTION |
|
UEA_IOMD_SPA-3-FRR_CFG_FAIL |
3-Error |
Failed to configure fast reroute on [chars]: [chars]. |
The SPA driver failed to configure fast rerouting on an interface. |
asr900-im |
LOG_STD_ACTION |
|
UEA_IOMD_SPA-3-HWIDB_FAILURE |
3-Error |
Creation: port [dec] vc [dec] |
Failed to create a hwidb. |
asr900-im |
LOG_STD_SH_TECH_ACTION |
|
UEA_IOMD_SPA-3-INITFAIL |
3-Error |
Initialization error |
A failure occurred during the initialization. |
Obtain from traceback. |
LOG_STD_REDUCE_ACTION |
|
UEA_IOMD_SPA-3-INVALID_ANYPHY |
3-Error |
Bay [dec] - Invalid anyphy number [dec] for vc [dec] |
Interface has invalid anyphy mumber |
asr900-im |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance open a case with the Technical Assistance " "Center via the Internet at " " http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a 'show tech-support' to " "your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
UEA_IOMD_SPA-3-INVALID_IF |
3-Error |
Attempted to access HWIDB for port [dec] on slot [dec] subSlot [dec] |
The UEA attempted to access the HWIDB associated with\n\ a non-existent port. |
asr900-im |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
UEA_IOMD_SPA-3-IPCALLOCFAIL |
3-Error |
Failed to allocate IPC buffer [chars] |
The SPA failed to allocate a buffer for communication with\n\ the Route Processor UEA-RP. |
asr900-im |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
UEA_IOMD_SPA-3-IPCPORT |
3-Error |
Failed to [chars] IPC port '[chars]' error [chars] |
The Linecard failed to create a port for\n\ communication with the Route Processor UEA-RP. |
asr900-im |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
UEA_IOMD_SPA-3-IPCPORTFAIL |
3-Error |
Failed to open IPC port '[chars]' [chars] with error [chars] |
The RP failed to open a port for communication with a SPA\n\ module. |
asr900-im |
LOG_STD_ACTION |
|
UEA_IOMD_SPA-3-IPCSENDFAIL |
3-Error |
Failed to send IPC message [chars] |
The Linecard failed to send a message to the\n\ Route Processor UEA-RP. |
asr900-im |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
UEA_IOMD_SPA-3-ISR_RC_ERROR |
3-Error |
ISR return code out of range. rc=[dec] |
The ISR error return code is out of range. |
asr900-im |
LOG_STD_SH_TECH_ACTION |
|
UEA_IOMD_SPA-3-LINKREC_ERROR |
3-Error |
Link record error - Bay [dec] vc [dec] error code [dec] |
Error processing link record structure |
asr900-im |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance open a case with the Technical Assistance " "Center via the Internet at " " http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a 'show tech-support' to " "your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
UEA_IOMD_SPA-3-LVLTRTOOBIG |
3-Error |
Loveletter length exceeds max [dec] bytes |
The UEA IOMD attempted to send a large message to the\n\ Route Processor UEA-RP. |
asr900-im |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
UEA_IOMD_SPA-3-MESSAGE_ERROR |
3-Error |
Bay [dec]: [chars] |
An unexpected error has occurred. |
asr900-im |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance " LOG_STD_ACTION |
|
UEA_IOMD_SPA-3-NETCLK_FAIL |
3-Error |
Failed to [chars] SPA reference clock on [chars] |
The SPA driver is not able to correctly configure the SPA reference clock on the specified interface. This indicates a hardware error. |
asr900-im |
LOG_STD_NO_ACTION |
|
UEA_IOMD_SPA-3-NODISPATCH |
3-Error |
Dispatch vector Null cmd=[dec] dintf=[dec] |
No command dispatch vector was found for the specified interface. |
asr900-im |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
UEA_IOMD_SPA-3-POWER |
3-Error |
Bay [dec] 12V power is [chars] |
SPA 12V power fault indicator |
asr900-im |
LOG_STD_ACTION |
|
UEA_IOMD_SPA-3-SONET_CLOCK_FAILED |
3-Error |
SPA Sonet clock has failed status = 0x%08x |
The SPA SONET clock has failed. SPAs that rely on the SPA SONET clock for proper operation such as POS and ATM will be affected. |
asr900-im |
"If the SPA Sonet clock does not recover perform an " "OIR. "LOG_STD_RECUR_ACTION |
|
UEA_IOMD_SPA-3-SONET_CLOCK_RECOVERED |
3-Error |
SPA Sonet clock has recovered status = 0x%08x |
SPA Sonet clock has recovered |
asr900-im |
LOG_STD_NO_ACTION |
|
UEA_IOMD_SPA-3-SPA_CTRL_EFC_CONFIG_FAILURE |
3-Error |
Subslot spa controller EFC configuration failure error [dec] |
Failed to configure SPA controller EFC |
asr900-im |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance " LOG_STD_ACTION |
|
UEA_IOMD_SPA-3-SPA_CTRL_INIT_FAILURE |
3-Error |
Subslot [dec] spa controller initialisation failure error [dec] |
Failed to initialise SPA controller |
asr900-im |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance " LOG_STD_ACTION |
|
UEA_IOMD_SPA-3-SPA_INTF_ID_CC_ALLOC_FAILED |
3-Error |
Failed to allocate interface identifiers for SPA [chars] |
Failed to get CC buffer and flow control identifiers for the SPA in the specified subslot Traffic cannot flow through the SPA under this failure condition. This can happen if the system runs out of available identifiers. |
asr900-im |
"Try to reduce the number of interfaces" "configured in the system either by physically removing the SPAs" "or by changing the system configuration" |
|
UEA_IOMD_SPA-3-SPI4_CONFIG_FAILURE |
3-Error |
Bay [dec] spi4 configuration failure error [dec] |
Failed to configure SPI4 interface |
asr900-im |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance " LOG_STD_ACTION |
|
UEA_IOMD_SPA-3-SPI4_INIT_FAILURE |
3-Error |
Bay [dec] initialization failure |
Failed to create SPI4 subblock |
asr900-im |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance " LOG_STD_ACTION |
|
UEA_IOMD_SPA-3-SPI4_NOTSYNC |
3-Error |
[chars]: Can not synchronize SPI4 bus host: src [chars]in sync sink [chars]in sync spa: src [chars]in sync sink [chars]in sync. |
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. |
- |
"Ensure that the SPA is properly seated " "in its subslot and reseat it if required." |
|
UEA_IOMD_SPA-3-UEAIPCALLOCFAIL |
3-Error |
Failed to allocate Common IPC buffer [chars] |
The Carrier Card failed to allocate a buffer for\n\ communication with the Route Processor. |
asr900-im |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
UEA_IOMD_SPA-4-BADPOINTER |
4-Warning |
Function [chars] detected an invalid [chars] pointer of %08lX ignoring |
A software error has occurred this message is displayed when \n\ an invalid pointer is detected. |
- |
"LOG_STD_SH_TECH_ACTION" |
|
UEA_IOMD_SPA-4-MAX_BANDWIDTH |
4-Warning |
Total SPA bandwidth exceeds line card capacity of %lu Mbps |
The total bandwidth of SPAs exceeds the rated capacity of this line card. |
asr900-im |
"Refer to the line card guidelines for the maximum allowed" "aggregated SPA bandwidth for the line card" |
|
UEA_IOMD_SPA-4-MAX_BANDWIDTH_NS |
4-Warning |
Total SPA bandwidth exceeds line card capacity full utilization of installed SPA interfaces is not supported |
The total bandwidth of SPAs exceeds the rated capacity of this line card. |
asr900-im |
"Refer to the line card guidelines for the maximum allowed" "aggregated SPA bandwidth for the line card" |
|
UEA_IOMD_SPA-4-SPABUS |
4-Warning |
Subslot [dec] [chars] SPA BUS access failed. timeout=[dec] err=[dec] par=[dec] err_c=0x[hec] addr=0x%08x data =0x[hec] |
SPABUS has reported an error. |
asr900-im |
LOG_STD_ACTION |
|
UEA_IOMD_SPA-4-SPABUS2 |
4-Warning |
Subslot [dec] SPA BUS access failed. No SPA present error |
SPABUS has reported an error. |
asr900-im |
LOG_STD_ACTION |
|
UEA_IOMD_SPA-6-LOGGERMSGTOOBIG |
6-Information |
Logger message length [dec] bytes exceeds the maximum allowed size |
The carrier card attempted to send a large message to the Route Processor |
asr900-im |
LOG_STD_ACTION |
|
UEA_IOMD_SPA-6-OIR |
6-Information |
Bay [dec] [chars] changed to [chars] |
SPA OIR Sequence |
asr900-im |
LOG_STD_NO_ACTION |
|
UEA_IPSEC_LIC-3-DISABLE_REBOOT_REQUIRED |
3-Error |
Reboot is required to disable IPSec license. Use 'write' command to make 'no license feature ipsec' available after reboot. |
UEA IPsec license disable will take effect on next reboot |
uea_ipsec |
LOG_STD_NO_ACTION |
|
UEA_IPSEC_LIC-3-ENABLE_REBOOT_REQUIRED |
3-Error |
Reboot is required to enable IPSec license. Use 'write' command to make 'license feature ipsec' available after reboot. |
UEA IPsec license enable will take effect on next reboot |
uea_ipsec |
LOG_STD_NO_ACTION |
|
UEA_IPSEC_LIC-3-NPE_IMAGE |
3-Error |
This command is not supported in an NPE image |
IPsec license cannot be enabled/disabled in an NPE image! |
uea_ipsec |
LOG_STD_NO_ACTION |
|
UEA_IPSEC_LIC-3-UNAVAILABLE_RESOURCES |
3-Error |
Some system resources are not available due to incorrect IPsec license configuration. Please reboot for proper functioning of the system |
Some system resources were reserved at bootup for IPsec feature due to incorrect IPsec license configuration. Reboot is needed to resolve this problem. |
uea_ipsec |
LOG_STD_NO_ACTION |
|
UEA_OIR-3-SPA_MISMATCH |
3-Error |
SPA [chars] mismatch in subslot 0/[dec] |
During the router operation we check if the inserted IM is matching with the IM type that was configured on the subslot. If not a mismatch event is said to have occured. |
asr900-csl |
LOG_STD_ACTION |
|
UEA_PTP_ENABLER-3-UEA_PTP_LICENSE_EULA_NOT_ACCEPTED |
3-Error |
\n********************************************************* \ \nWARNING: PTP License is not yet activated. \ \nPlease configure 'license feature ptp'\ \n*********************************************************\n |
- |
- |
LOG_STD_ACTION |
|
UEA_SPA_MODE-6-UEA_SPA_MODE_CHG |
6-Information |
SPA[chars] mode changed from [chars] to [chars] at subslot 0/[dec] |
SPA Operating mode has been changed. SPA will be reloaded now. |
asr900-csl |
LOG_STD_NO_ACTION |
|
UEA_SPA-3-CREATE_TDLH_FAILURE |
3-Error |
Failed to create SPA [dec]/[dec] handle |
Failed to create message handle for SPA communication. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-CREATE_TDLMSG_FAILURE |
3-Error |
Failed to create [chars] message for [chars]. |
Failed to create/allocate necessary TDL message for SPA communication. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-CREATION_FAILURE |
3-Error |
slot=[dec] subslot=[dec] spa_type=0x[hec] lc_type=0x[hec]. |
Failed to create a SPA object. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-DIAG_CONFIG |
3-Error |
[chars] did not complete [dec]/[dec] |
An error has occured during diagnostic test. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-DISPATCH_INIT_TDLH_FAILURE |
3-Error |
Failed to initialize dispatch path for SPA [dec]/[dec] handle |
Failed to initialize dispatch path handle for SPA communication. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-DOMAIN_TDLH_FAILURE |
3-Error |
[chars] rc = [dec] |
Failed to bind message handle for SPA communication. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-INVALID_CPU_NUM |
3-Error |
cpu= [dec] max cpu = [dec] |
An invalid CPU number is specified in one of the internal APIs. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-INVALID_DATA_INSTANCE |
3-Error |
interface type [chars] slot [dec] port [dec] vc [dec] : [chars] |
Data required to support the interface is not available. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-INVALID_HANDLE |
3-Error |
Failed to get a valid IPC handle for type [dec] slot [dec] subslot [dec]. |
The client handle was found to be NULL for the given type/slot/subslot. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-INVALID_IF_INDEX |
3-Error |
index= [dec] spaType=0x[hec] slot [dec] subSlot [dec] slotunit [dec] vc [dec] |
Index for the interface is not valid. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-INVALID_INDX_RANGE |
3-Error |
index1= [dec] index2= [dec] maxIndex= [dec] |
An invalid index range is specified in one of the internal APIs. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-INVALID_RP_SLOT_NUM |
3-Error |
slot= [dec] max slot = [dec] |
An invalid RP slot number is specified in one of the internal APIs. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-INVALID_SLOT_NUM |
3-Error |
slot= [dec] max slot = [dec] |
An invalid slot number is specified in one of the internal APIs. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-INVALID_SLOTUNIT_NUM |
3-Error |
cardwide-port = [dec] max cardwide-port = [dec] |
An invalid cardwide-port number is specified in one of the internal APIs. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-INVALID_SPA_TDL_CCAPI_USAGE |
3-Error |
- |
Incorrect usage of an internal API that should only be used on CC. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-INVALID_SUBSLOT_NUM |
3-Error |
subslot= [dec] max subslot = [dec] |
An invalid subslot number is specified in one of the internal APIs. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-IPC_FAILURE |
3-Error |
IPC failure while [chars] |
An error has occurred while prepareing or sending an IPC message. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-MEM_ALLOC_ERROR |
3-Error |
[chars] |
Memory allocation error. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-NULL_SPA_PTR |
3-Error |
- |
Pointer to a SPA object is NULL. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-NULL_VFT |
3-Error |
[chars] virtual function table is not initialized. spaType=0x[hec] |
A required function table is not initialized |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-NULL_VFUNC |
3-Error |
[chars] vector is not initialized. spaType=0x[hec] |
A required function vector is not initialized |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-POWER_CYCLE |
3-Error |
[chars] occurred on Shared Port Adapter [dec]/[dec] |
An error has occurred which will cause the \n\ Shared Port Adapter to be power cycled |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-SENDCFGFAIL |
3-Error |
Failed to send configuration for [chars] to carrier-card for subslot=[dec]/[dec] |
Sending configuration failed. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-SETUP_TDLH_FAILURE |
3-Error |
Failed to set the alloc/free handler for SPA [dec]/[dec] handle |
Failed to set the alloc/free handler for SPA communication. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-SPA_CREATION_FAILURE |
3-Error |
slot=[dec] subslot=[dec] PID=[chars] lc_type=0x[hec]. |
Failed to create a SPA object. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-3-UNSUPPORTED_DATA |
3-Error |
Data conversion error [chars] 0x%X |
An internal software error has occured when converting the data specified in the message from one representation to another. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_SPA-6-TDLMSG_INCOMPATIBLE |
6-Information |
Failed to copy message [chars] to buffer not allowed for current domain. |
Failure to marshal a message indicates an incompatibility with the intended recipient. |
- |
LOG_STD_SH_TECH_ACTION |
|
UEA_TDM_IM-3-NULL_UEA_PTR |
3-Error |
- |
Pointer to a UEA object is NULL. |
uea-im-tdm |
LOG_STD_SH_TECH_ACTION |
|
UEA_TDM_IM-3-PLUGIN_INIT |
3-Error |
Plugin init failed. UEA object [chars] Action [chars]. |
Plugin init failed UEA |
uea-im-tdm |
LOG_STD_SH_TECH_ACTION |
|
UEA_TDM_IM-3-UEA_CREATION_FAILURE |
3-Error |
slot=[dec] subslot=[dec] spa_type = [dec] PID=[chars] |
Failed to create a UEA object. |
uea-im-tdm |
LOG_STD_SH_TECH_ACTION |
|
UEA_TDM_IM-6-EEPROM_PROG_FAILED |
6-Information |
EEPROM programming FAILED for IM |
IM EEPROM programming was unsuccessful allowing module to boot |
- |
LOG_STD_NO_ACTION |
|
UEA_TDM_IM-6-EEPROM_PROG_PASSED |
6-Information |
EEPROM programming passed for IM |
IM EEPROM was programmed successfully attempting IM reset |
- |
LOG_STD_NO_ACTION |
|
UEA_UPPER_APP-3-MEM_FAILURE |
3-Error |
Not enought memory for [chars] |
Failed to create a UEA object. |
uea-im-tdm |
LOG_STD_SH_TECH_ACTION |
|
UEA_UPPER_APP-3-NULL_PTR |
3-Error |
- |
Pointer to a UEA object is NULL. |
uea-im-tdm |
LOG_STD_SH_TECH_ACTION |
|
UEA_UPPER_APP-3-TDM_ENCAP |
3-Error |
Unsupported Encap : [dec] |
TDM Configuration failed |
uea-im-tdm |
LOG_STD_SH_TECH_ACTION |
|
UEA_UPPER_APP-3-WINIPC_FAILURE |
3-Error |
WinIPC failed : command [chars] |
WinIPC Failed |
uea-im-tdm |
LOG_STD_SH_TECH_ACTION |
|
UFAST_MCAST_SW-3-PROC_START_ERROR |
3-Error |
No process available for transmitting UplinkFast packets. |
UplinkFast packets will not be transmitted as the process could\n\ not be created. |
- |
"UplinkFast will not work unless you reload. If this problem persists \n\ even after reload please contact your Cisco Technical Support\n\ representative with the configuration and technical support\n\ information." |
|
UFAST_MCAST_SW-4-MEM_NOT_AVAILABLE |
4-Warning |
No memory is available for transmitting UplinkFast packets on\n\ Vlan [dec]. |
UplinkFast packets will not be transmitted on Vlan [dec] due to a\n\ lack of memory. |
- |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
UI-3-IPC_ALLOC |
3-Error |
module type [dec] subtype [dec] |
IPC packet allocation failed for UI reply. Sender will not get reply |
cpp-ucode |
LOG_STD_ACTION |
|
UI-3-REPLY |
3-Error |
module type [dec] subtype [dec] |
A UI reply message failed in the IPC send. Sender will not get reply |
cpp-ucode |
LOG_STD_ACTION |
|
UI-6-NOHANDLER |
6-Information |
module type [dec] subtype [dec] |
A UI message was received containing an unrecognized module type or module subtype |
cpp-ucode |
LOG_STD_ACTION |
|
UMBRELLA-3-UMBRELLA_HA_INIT_FAILURE |
3-Error |
Failed to register with RF rc = [dec] |
Organization does not exists |
xe-opendns-conn |
"Reactivtae Umbrella license" |
|
UNAWAKABLE-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
UNEXPECTEDEVENT-3-LDP_SCHED |
3-Error |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
UNEXPECTEDEVENT-3-MPLS_TE_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 |
|
UNEXPECTEDMESSAGE-3-MPLS_TE_SCHED |
3-Error |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
UNEXPECTEDQUEUE-3-MPLS_TE_SCHED |
3-Error |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
UNEXPECTEDTIMER-3-LDP_SCHED |
3-Error |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
UNEXPECTEDTIMER-3-MPLS_TE_SCHED |
3-Error |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
UNIQ_ADDR-3-DUPL_IPV4 |
3-Error |
A duplicate IPv4 address has been detected [chars] = [inet] already in use by [chars]/[chars] |
An access-accept message has been parsed which includes an IPv4 address that already exists in the database. This usually means that the RADIUS server has mistakenly returned an IPv4 address it has returned before. |
- |
"In the RADIUS server check to see why it is" " returning duplicate IPv4 addresses to the BNG router. At the BNG" " router issue the command 'show ppp all' to see all ppp sessions" " as well as their IP addresses. Useful debugging command are" " 'debug ppp unique address' 'debug radius' and 'debug aaa" "accouting'." |
|
UNIQ_ADDR-3-DUPL_IPV6_DEL_PREF |
3-Error |
A duplicate delegated IPv6 prefix has been detected [chars] = %P already in use by [chars]/[chars] |
An access-accept message has been parsed which includes a delegated IPv6 prefix that already exists in the database. This usually meansthat the RADIUS server has mistakenly returned a delegated IPv6 prefix it has returned before. |
- |
"In the RADIUS server check to see why it is" " returning duplicate delegated IPv6 prefixes to the BNG router." " At the BNG router issue the command 'show ppp all' to see all" " ppp sessions as well as their IP addresses. Useful debugging" " command are 'debug ppp unique address' 'debug radius' and" " 'debug aaa accouting'." |
|
UNIQ_ADDR-3-DUPL_IPV6_PREF |
3-Error |
A duplicate IPv6 prefix has been detected [chars] = %P already in use by [chars]/[chars] |
An access-accept message has been parsed which includes an IPv6 prefix that already exists in the database. This usually means that the RADIUS server has mistakenly returned an IPv6 prefix it has returned before. |
- |
"In the RADIUS server check to see why it is" "returning duplicate IPv6 prefixes to the BNG router. At the BNG" "router issue the command 'show ppp all' to see all ppp sessions" " as well as their IP addresses. Useful debugging command are" " 'debug ppp unique address' 'debug radius' and 'debug aaa" " accouting'." |
|
UNIX_BPD-3-HWIDB_ERR |
3-Error |
[chars]: [dec] |
HWIDB Lookup Error |
UNIX_BPD_DDTS_COMPONENT |
LOG_STD_ACTION |
|
UNIX_BPD-3-PKT_ERR |
3-Error |
[chars]: [chars] |
Packet Not Available |
UNIX_BPD_DDTS_COMPONENT |
LOG_STD_ACTION |
|
UNIX_IFUTIL-3-PAK_ERR |
3-Error |
Pak not available [chars]: [chars] |
The running configuration was too big to be synced |
UNIX_BPD_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
UNIX_IFUTIL-3-POOL_ERR |
3-Error |
[chars] Pool Creation Error for hwidb: [chars] |
POOL Creation Error |
UNIX_BPD_DDTS_COMPONENT |
LOG_STD_ACTION |
|
UNIX_SPA-3-CREATION_FAILURE |
3-Error |
slot=[dec] subslot=[dec] spa_type=0x[hec] lc_type=0x[hec]. |
Failed to create a SPA object. |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIX_SPA-3-DIAG_CONFIG |
3-Error |
[chars] did not complete [dec]/[dec] |
An error has occured during diagnostic test. |
c7600-field-diag |
LOG_STD_SH_TECH_ACTION |
|
UNIX_SPA-3-INVALID_DATA_INSTANCE |
3-Error |
interface type [chars] slot [dec] port [dec] vc [dec] : [chars] |
Data required to support the interface is not available. |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIX_SPA-3-INVALID_IF_INDEX |
3-Error |
index= [dec] spaType=0x[hec] slot [dec] subSlot [dec] slotunit [dec] vc [dec] |
Index for the interface is not valid. |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIX_SPA-3-INVALID_INDX_RANGE |
3-Error |
index1= [dec] index2= [dec] maxIndex= [dec] |
Invalid index range. |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIX_SPA-3-INVALID_SLOT_NUM |
3-Error |
slot= [dec] max slot = [dec] |
Invalid slot number. |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIX_SPA-3-INVALID_SLOTUNIT_NUM |
3-Error |
cardwide-port = [dec] max cardwide-port = [dec] |
Invalid cardwide-port number. |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIX_SPA-3-IPC_FAILURE |
3-Error |
IPC failure while [chars] |
An error has occurred while prepareing or sending an IPC message. |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIX_SPA-3-MEM_ALLOC_ERROR |
3-Error |
[chars] |
Memory allocation error. |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIX_SPA-3-NULL_HWIDB |
3-Error |
[chars] called with NULL hwidb |
A NULL hwidb is encountered |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIX_SPA-3-NULL_SPA_PTR |
3-Error |
- |
Pointer to a SPA object is NULL. |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIX_SPA-3-NULL_VFT |
3-Error |
[chars] virtual function table is not initialized. spaType=0x[hec] |
A required function table is not initialized |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIX_SPA-3-NULL_VFUNC |
3-Error |
[chars] vector is not initialized. spaType=0x[hec] |
A required function vector is not initialized |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIX_SPA-3-POWER_CYCLE |
3-Error |
[chars] occurred on Shared Port Adapter [dec]/[dec] |
An error has occurred which will cause the \n\ Shared Port Adapter to be power cycled |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIX_SPA-3-SENDCFGFAIL |
3-Error |
Failed to send configuration for [chars] to carrier-card for subslot=[dec]/[dec] |
Sending configuration failed. |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIX_SPA-3-SPA_CREATION_FAILURE |
3-Error |
slot=[dec] subslot=[dec] PID=[chars] lc_type=0x[hec]. |
Failed to create a SPA object. |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIX_SPA-3-SPA_SB_CREATION_FAILURE |
3-Error |
Failed to create SPA SB |
Failed to create a SPA subblock. |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIX_SPA-3-UNSUPPORTED_DATA |
3-Error |
Data conversion error [chars] 0x%X |
An internal software error has occured when converting the data specified in the message from one representation to another. |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIXLC_SPA-3-C2W_MAIN_INIT_FAIL |
3-Error |
Failed to initialize SPA main c2w bus for subslot [dec] status = [dec] |
The SPA driver is not able to initialize SPA main c2w. This indicates a hardware error. |
diou |
LOG_STD_NO_ACTION |
|
UNIXLC_SPA-3-CMDNOINT |
3-Error |
HWIDB Null for command [dec] port [hex] |
The Route Processor passed down a port number that is unknown on the\n\ carrier card. |
diou |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
UNIXLC_SPA-3-DEVICE_ERROR |
3-Error |
subSlot [dec] spatype 0x[hec]. Device error: [chars] |
An error related to a device on the SPA is detected. |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIXLC_SPA-3-EFC_CHAN_ERR |
3-Error |
EFC error - interface [chars] vc [dec] anyphy [dec] err_code [dec] : [chars] |
Failed to configure efc channel/parameters |
diou |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance " LOG_STD_ACTION |
|
UNIXLC_SPA-3-EFC_FC_MAP_FAIL |
3-Error |
Failed to update EFC flow control identifier for interface [chars] status = [dec] |
The SPA driver is not able to update the datapath EFC flow control identifier for the interface specified in the message. This indicates a hardware error. |
diou |
LOG_STD_NO_ACTION |
|
UNIXLC_SPA-3-EFC_PROV_FAIL |
3-Error |
Failed to provision EFC for interface [chars] status = [dec] |
The SPA driver is not able to provision EFC for the interface specified in the message. This indicates a hardware error. |
diou |
LOG_STD_NO_ACTION |
|
UNIXLC_SPA-3-EFC_UNPROV_FAIL |
3-Error |
Failed to unprovision EFC for VC [chars] status = [dec] |
The SPA driver is not able to unprovision EFC for the interface specified in the message. This indicates a hardware error. |
diou |
LOG_STD_NO_ACTION |
|
UNIXLC_SPA-3-FCI_NOT_SET |
3-Error |
Bay [dec] - FCI type not set |
An FCI type of zero was detected |
c7600-sip-common |
LOG_STD_ACTION |
|
UNIXLC_SPA-3-HWIDB_FAILURE |
3-Error |
Creation: port [dec] vc [dec] |
Failed to create a hwidb. |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIXLC_SPA-3-INVALID_ANYPHY |
3-Error |
Bay [dec] - Invalid anyphy number [dec] for vc [dec] |
Interface has invalid anyphy mumber |
spa-ser-common |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance open a case with the Technical Assistance " "Center via the Internet at " " http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a 'show tech-support' to " "your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
UNIXLC_SPA-3-INVALID_IF |
3-Error |
Attempted to access HWIDB for port [dec] on slot [dec] subSlot [dec] |
The IOU attempted to access the HWIDB associated with\n\ a non-existent port. |
diou |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
UNIXLC_SPA-3-ISR_RC_ERROR |
3-Error |
ISR return code out of range. rc=[dec] |
The ISR error return code is out of range. |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIXLC_SPA-3-LINKREC_ERROR |
3-Error |
Link record error - Bay [dec] vc [dec] error code [dec] |
Error processing link record structure |
spa-ser-common |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance open a case with the Technical Assistance " "Center via the Internet at " " http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact " "your Cisco technical support representative. Be sure to provide the " "the information you have gathered and a 'show tech-support' to " "your support representative or attach it to your case in non-zipped " "plain text format .txt." |
|
UNIXLC_SPA-3-MESSAGE_ERROR |
3-Error |
Bay [dec]: [chars] |
An unexpected error has occurred. |
diou |
"Seach for resolved software issues using the Bug " "Toolkit at " "http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance " LOG_STD_ACTION |
|
UNIXLC_SPA-3-NETCLK_FAIL |
3-Error |
Failed to [chars] SPA reference clock on [chars] |
The SPA driver is not able to correctly configure the SPA reference clock on the specified interface. This indicates a hardware error. |
diou |
LOG_STD_NO_ACTION |
|
UNIXLC_SPA-3-NULL_SPA_BAY |
3-Error |
- |
Pointer to object for bay [dec] is NULL. |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIXLC_SPA-3-POWER |
3-Error |
Bay [dec] 12V power is [chars] |
SPA 12V power fault indicator |
diou |
LOG_STD_ACTION |
|
UNIXLC_SPA-3-SONET_CLOCK_FAILED |
3-Error |
SPA Sonet clock has failed status = 0x%08x |
The SPA SONET clock has failed. SPAs that rely on the SPA SONET clock for proper operation such as POS and ATM will be affected. |
c7600-sip-common |
"If the SPA Sonet clock does not recover perform an " "OIR. "LOG_STD_RECUR_ACTION |
|
UNIXLC_SPA-3-SONET_CLOCK_RECOVERED |
3-Error |
SPA Sonet clock has recovered status = 0x%08x |
SPA Sonet clock has recovered |
c7600-sip-common |
LOG_STD_NO_ACTION |
|
UNIXLC_SPA-3-SPA_CTRL_EFC_CONFIG_FAILURE |
3-Error |
Subslot spa controller EFC configuration failure error [dec] |
Failed to configure SPA controller EFC |
diou |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance " LOG_STD_ACTION |
|
UNIXLC_SPA-3-SPA_CTRL_INIT_FAILURE |
3-Error |
Subslot [dec] spa controller initialisation failure error [dec] |
Failed to initialise SPA controller |
diou |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance " LOG_STD_ACTION |
|
UNIXLC_SPA-3-SPI4_CONFIG_FAILURE |
3-Error |
Bay [dec] spi4 configuration failure error [dec] |
Failed to configure SPI4 interface |
diou |
"Seach for resolved software issues using the Bug " "Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance " LOG_STD_ACTION |
|
UNIXLC_SPA-3-SPI4_INIT_FAILURE |
3-Error |
Bay [dec] initialization failure |
Failed to create SPI4 subblock |
diou |
"Seach for resolved software issues using the Bug " "Toolkit at " "http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. " "If you still require assistance " LOG_STD_ACTION |
|
UNIXLC_SPA-3-UNIXIPCALLOCFAIL |
3-Error |
Failed to allocate Common IPC buffer [chars] |
The Carrier Card failed to allocate a buffer for\n\ communication with the Route Processor. |
diou |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
UNIXLC_SPA-4-MAX_BANDWIDTH |
4-Warning |
Total SPA bandwidth exceeds line card capacity of %lu Mbps |
The total bandwidth of SPAs exceeds the rated capacity of this line card. |
diou |
"Refer to the line card guidelines for the maximum allowed" "aggregated SPA bandwidth for the line card" |
|
UNIXLC_SPA-4-MAX_BANDWIDTH_NS |
4-Warning |
Total SPA bandwidth exceeds line card capacity full utilization of installed SPA interfaces is not supported |
The total bandwidth of SPAs exceeds the rated capacity of this line card. |
diou |
"Refer to the line card guidelines for the maximum allowed" "aggregated SPA bandwidth for the line card" |
|
UNIXLC_SPA-4-SPABUS |
4-Warning |
Subslot [dec] [chars] SPA BUS access failed. timeout=[dec] err=[dec] par=[dec] err_c=0x[hec] addr=0x%08x data =0x[hec] |
SPABUS has reported an error. |
diou |
LOG_STD_ACTION |
|
UNIXLC_SPA-4-SPABUS2 |
4-Warning |
Subslot [dec] SPA BUS access failed. No SPA present error |
SPABUS has reported an error. |
diou |
LOG_STD_ACTION |
|
UNIXLC_SPA-6-OIR |
6-Information |
Bay [dec] [chars] changed to [chars] |
SPA OIR Sequence |
diou |
LOG_STD_NO_ACTION |
|
UNIXRP_SPA-3-CI_UPDATE_FAIL |
3-Error |
Failed to update connection identifier for interface [chars] |
The SPA driver is not able to update the datapath connection identifier for the interface specified in the message. This indicates a software error. |
diou |
LOG_STD_NO_ACTION |
|
UNIXRP_SPA-3-DPIDX_LKUP_FAIL |
3-Error |
Failed to retrieve datapath identifier for interface [chars] |
The SPA driver is not able to retrieve the datapath identifier for the interface specified in the message. This indicates a software error. |
diou |
LOG_STD_NO_ACTION |
|
UNIXRP_SPA-3-FLOWID_ALLOC_FAIL |
3-Error |
Failed to allocate a flow control identifier for interface [chars] |
The SPA driver is not able to allocate the datapath flow control identifier for the interface specified in the message. This indicates a software error. |
diou |
LOG_STD_NO_ACTION |
|
UNIXRP_SPA-3-FLOWID_RELEASE_FAIL |
3-Error |
Failed to release a flow control identifier for interface [chars] status = [dec] |
The SPA driver is not able to release the datapath flow control identifier for the interface specified in the message. This indicates a software error. |
diou |
LOG_STD_NO_ACTION |
|
UNIXRP_SPA-3-HWIDB_FAILURE |
3-Error |
Creation: slot [dec] subSlot [dec] port [dec] vc [dec] |
Failed to create an interface hwidb. |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIXRP_SPA-3-HWIDB_INIT_FAIL |
3-Error |
Failed to initialize data structure for SPA port [dec]/[dec]/[dec] |
A SPA driver was not able to properly initialize a data structure mentioned in the message. This indicates a software error. |
diou |
LOG_STD_NO_ACTION |
|
UNIXRP_SPA-3-INVALID_PORT_NUM |
3-Error |
slot=[dec] port=[dec] hwidbType=0x[hec] max_port_num=[dec] LCtype=0x[hec] |
The port number is out of range. |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIXRP_SPA-3-IPCALLOCFAIL |
3-Error |
Failed to allocate IPC buffer [chars] |
The RP failed to allocate a buffer for communication with a SPA |
diou |
LOG_STD_ACTION |
|
UNIXRP_SPA-3-MAX_SPA |
3-Error |
Power to IPSEC-SPA-2G in [chars] is denied because it has exceeded the number allowed[dec] |
The number of IPSEC-SPA-2G in a chassis is limited. This message is displayed when the number of IPSEC-SPA-2G in the chassis has exceeded this limit. |
diou |
"Use only the number of supported IPSEC-SPA-2G" |
|
UNIXRP_SPA-3-NO_HOST_INFO |
3-Error |
slot [dec] subSlot [dec] spaType 0x[hec] |
Failed to get information about the host linecard. |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIXRP_SPA-3-NULL_DATA_STRUCTURE |
3-Error |
NULL |
A SPA driver is not able to retrieve the data structure mentioned in the message. This indicates a software error. |
diou |
LOG_STD_NO_ACTION |
|
UNIXRP_SPA-3-NULL_HWIDB_SPA_BAY_PORT |
3-Error |
HWIDB not found: slot [dec] bay [dec] port [dec] |
A NULL hwidb is encountered |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIXRP_SPA-3-NULL_SPA_BAY |
3-Error |
- |
Pointer to object for slot [dec] bay [dec] is NULL. |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIXRP_SPA-3-SPA_NO_HOST_INFO |
3-Error |
slot [dec] subSlot [dec] PID [chars] |
Failed to get information about the host linecard. |
diou |
LOG_STD_SH_TECH_ACTION |
|
UNIXRP_SPA-3-VC_PROV_FAIL |
3-Error |
Failed to provision interface [chars] |
The SPA driver is not able to provision the interface specified in the message. Verify that the SPA hardware is not provisioned above the supported limit. Otherwise this indicates a hardware error. |
diou |
LOG_STD_NO_ACTION |
|
UNIXRP_SPA-4-SPA_CMD_NO_RESP |
4-Warning |
[chars]: No response for interface configuration command [dec] |
A timeout occurred while RP was waiting for a response from line card. This may happen due to line card CPU being too busy to respond to the command. |
diou |
LOG_STD_NO_ACTION |
|
UNIXRP_SPA-4-SPA_RESP_CMD_MISMATCH |
4-Warning |
[chars]: Expecting response to interface configuration command [dec] but received response to command [dec]. |
An internal synchronization error occurred while configuring the interface. The configuration may not have succeeded. |
diou |
"Check that the running configuration for the " "interface is correct. If this message occurred on the standby try " "reloading the standby to ensure that its configuration is in sync. " "If this message is repeatable please " LOG_STD_SH_TECH_ACTION |
|
UNIXRP_SPA-6-CARDRELOAD |
6-Information |
Module [dec] reload due to SPA insert in [dec]/[dec]. |
When inserting a SPA on this carrier card the card is reset. |
- |
LOG_STD_NO_ACTION |
|
UNIXRP-3-CARDERR |
3-Error |
[chars] |
An IPC card has registered itself to the IPC master twice. The card\n\ malfunctioned and its IPC is not active. |
UNIXRP_DDTS_COMPONENT |
LOG_STD_ACTION |
|
UNIXRP-3-IPCERR |
3-Error |
[chars] [dec] |
IPC slot error |
UNIXRP_DDTS_COMPONENT |
LOG_STD_ACTION |
|
UNIXRP-3-SEATERR |
3-Error |
[chars] [dec] [chars] |
Failed to create IPC seat for line card |
UNIXRP_DDTS_COMPONENT |
LOG_STD_ACTION |
|
UNKNOWN_EVENT-3-MPLS_TE_EXT_FWDG |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
UNKNOWN_SHUTDOWN-6-LDP |
6-Information |
ERRMSG_NOFLAGS |
- |
- |
- |
|
UNKNOWNCAP-5-LDP |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
UNSUPPORTED_LINK_TYPE-2-MPLS_TE |
2-Critical |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
UPDATE-3-ATOM_HA |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
URLF-3-ALLOW_MODE |
3-Error |
[chars]Connection to all the URL filter servers are down and the allow mode is '[chars]' |
This messages indicates that connection to all the URL filter servers are down. If allow mode is 'on' the router will pass all the http traffic otherwise it will drop the http traffic and close the TCP connection |
ios-firewall |
"The network administrator can possibly check whether the URL filter " "server WebSense/N2H2 is down and restart it if required. If it " |
|
URLF-3-MAX_REQ |
3-Error |
[chars]The number of pending request exceeds the maximum limit [dec] |
This message indicates that the number of requests pending in the router for URL authentication from URL filter server exceeds the maximum limit. In this case the http request will be dropped |
ios-firewall |
"This message is just for informational purpose" |
|
URLF-3-RESOURCE_ALLOC_FAILED |
3-Error |
The resource allocation failed for URL filter subsystem |
This message indicates that the URLF feature is not able to allocate memory for various data structures |
ios-firewall |
"The router is running out of memory disable " "the features that are not used or check if something goes wrong" |
|
URLF-3-SERVER_DOWN |
3-Error |
[chars]Connection to the URL filter server [inet] is down |
This messages indicates that a connection between the router and a url filter server is down. If more than one servers are configured the router will make use of other servers for URL authentication otherwise it will check whether allow mode is 'on' or 'off'. If allow mode is 'on' the router will pass all the packets otherwise it will drop all the packet and close the TCP connection. |
ios-firewall |
"The network administrator can possibly check whether the URL filter " "server WebSense/N2H2 is down and restart it if required. If it " |
|
URLF-3-URL_TOO_LONG |
3-Error |
[chars]URL sent from [inet] is too long more than [dec] bytes possibly |
The URL parsed from http GET request is too long it could possibly be a fake packet so the packet will be dropped |
ios-firewall |
"This could be a fake packet sent by the attackers" |
|
URLF-4-SITE_BLOCKED |
4-Warning |
[chars]Access denied for the site '[chars]' client [inet]:[dec] server [inet]:[dec] |
This message indicates that all underlying URLs of the specified domain are blocked |
ios-firewall |
"This indicates that an user has made an attempt to browse a " "forbidden site" |
|
URLF-4-URL_BLOCKED |
4-Warning |
[chars]Access denied URL '[chars]' client [inet]:[dec] server [inet]:[dec] |
This message indicates that access to the requested URL is denied and the corresponding TCP connection is closed |
ios-firewall |
"This indicates that an user has made an attempt to browse a " "forbidden site" |
|
URLF-5-SERVER_UP |
5-Notice |
[chars]Connection to an URL filter server[inet] is made the router is |
This message indicates that at least one connection is up between router and a URL filter server. System is leaving out of allow mode |
ios-firewall |
"This is just an informational message" |
|
URLF-6-SITE_ALLOWED |
6-Information |
[chars]Client [inet]:[dec] accessed server [inet]:[dec] |
This message indicates that all URLs belongs to the server are allowed to be passed with out URL filter servers authentication |
ios-firewall |
"This message is just for informational purpose it can be used " "to keep track of number of GET request that are sent from client " "to server" |
|
URLF-6-URL_ALLOWED |
6-Information |
[chars]Access allowed for URL '[chars]' client [inet]:[dec] server [inet]:[dec] |
This message indicates that the http GET request sent from client is allowed to be transmitted to http server |
ios-firewall |
"This is just an informational message" |
|
USB_HOST_STACK-2-USB_NO_MEMORY |
2-Critical |
Memory allocation failure: [chars]. |
Unable to allocate memory for USB stack structures. |
usb-driver |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
USB_HOST_STACK-3-USB_FLASH_READY_TEST_FAILED |
3-Error |
USB flash failed to pass 'Ready' test. |
The USB Flash memory failed diagnostic testing. The Flash memory could not enter the Ready state and was not registered in the file system. |
usb-driver |
"Remove the device and reinsert it again. If the problem persists" "please search Bug Toolkit on the Cisco web site for" "bugs related to your version of software. If you do" "not find an existing bug please open a TAC case and" "provide 'show version' 'show running' and 'show usb device'" |
|
USB_HOST_STACK-3-USB_HOST_SYS_ERROR |
3-Error |
A USB host controller sys error happened[hec] [hec]. |
This is an informational message sent when a system error happened on the the host controller. USB host controller resetted |
usb-hcd |
LOG_STD_NO_ACTION |
|
USB_HOST_STACK-5-USB_ENUM_FAIL_ADDRFULL |
5-Notice |
Failed to enumerate a USB device as the address pool is full. |
The USB address pool is full. |
usb-driver |
"The number of inserted devices might have exceeded the platform limit. Remove the other devices that are not in use. And remove and insert this device again." |
|
USB_HOST_STACK-5-USB_ENUM_FAIL_GETDESCR |
5-Notice |
Failed to enumerate a USB device as not able to read the device's description. |
Unable to read Device descriptor information from the device |
usb-driver |
"The device may be faulty." |
|
USB_HOST_STACK-5-USB_ENUM_FAIL_NOPOWER |
5-Notice |
Failed to enumerate a USB device as the device's power requirement[dec] mA is more than the available port power[dec] mA |
The device's power requirement exceeds the available port power. |
usb-driver |
"Refer platform specific documents on the maximum power provided on USB ports." |
|
USB_HOST_STACK-5-USB_ENUM_FAIL_SETADDR |
5-Notice |
Failed to enumerate a USB device as not able to do set device's address. |
The setting of USB address to the device failed. |
usb-driver |
"The device may be faulty." |
|
USB_HOST_STACK-5-USB_ENUM_UNSUPPORTED_DEVICE |
5-Notice |
Unsupported device inserted. Host id [dec] Device Addr [dec]. |
The device is not supported on the platform/image. |
usb-driver |
"This device is not supported. Use \"show usb device\" to see " "the device information. Check the image and see whether the " "image supports the device." |
|
USB_HOST_STACK-5-USB_NO_HUB_SUPPORT |
5-Notice |
USB Hub is not supported. |
USB Hub is not supported on the platform. |
usb-driver |
"Do not use USB Hub since it is not a supported device." |
|
USB_HOST_STACK-6-USB_DEVICE_CONNECTED |
6-Information |
A [chars] USB device has been inserted in port [dec]. |
This is an informational message sent when an interrupt is generated to the USB controller upon device insertion. |
usb-hcd |
LOG_STD_NO_ACTION |
|
USB_HOST_STACK-6-USB_DEVICE_DISCONNECTED |
6-Information |
A USB device has been removed from port [dec]. |
This is an informational message sent when an interrupt is generated to the USB controller upon device removal. |
usb-hcd |
LOG_STD_NO_ACTION |
|
USB_HOST_STACK-6-USB_FLASH_READY_TEST_TIME |
6-Information |
USB flash 'Ready' test time over [dec] seconds. |
The USB Flash memory has taken a time equal to or more than 75% of the maximum time allotted for it to pass the diagnostic testing and enter the Ready state. |
usb-driver |
LOG_STD_NO_ACTION |
|
USB_PRINTER-3-FAIL_TO_CREATE_SCHEDULER |
3-Error |
Could not create a job scheduler for [chars]. |
USB Printer could not create a scheduler process. This condition indicates that memory resources are being exhausted. |
print-server |
"Please check memory usage " " and report it to TAC." |
|
USB_PRINTER-3-FAIL_TO_CREATE_WATCHED_BOOLEAN |
3-Error |
Could not create a watched boolean for [chars]. |
USB Printer could not create a watched boolean. This condition indicates that memory resources are being exhausted. |
print-server |
"Please check memory usage " " and report it to TAC." |
|
USB_PRINTER-3-FAIL_TO_GET_APP_HANDLE |
3-Error |
Could not get application handle for printer [chars]. |
Could not get application handle from the USB stack. |
print-server |
"Remove this printer and insert it again." |
|
USB_PRINTER-3-NO_PAPER |
3-Error |
Could not create job since there is no paper in printer [chars]. |
Could not create job because of lack of paper. |
print-server |
"Please put paper in the tray and re-submit job." |
|
USB_PRINTER-3-PRINTER_IN_ERROR |
3-Error |
Could not create job since printer [chars] is in error. |
Could not create job because port status command returned error. |
print-server |
"Try rebooting printer once. If problem still persists report to TAC." |
|
USB_PRINTER-3-USB_PRINTER_OBJECT_FAIL |
3-Error |
Could not create printer object for [chars]. |
Could not create the printer object. |
print-server |
"Remove this printer and insert it again." |
|
USB_PRINTER-6-USB_PRINTER_INSERTED |
6-Information |
USB Printer inserted: [chars]. |
A USB Printer has been detected. |
print-server |
"Informational message only. No action required." |
|
USB_PRINTER-6-USB_PRINTER_REMOVED |
6-Information |
USB Printer removed: [chars]. |
A USB Printer has been removed. |
print-server |
"Informational message only. No action required." |
|
USB_TOKEN_FILESYS-3-ASYNC_IO_ERROR_CREATING_DIRECTORY |
3-Error |
Error creating directory: dir [chars] ret code [hec] [chars]. |
Token Asynchronous I/O process failed to create a directory in USB token device. |
usb-token-filesys |
"Report the error message to your technical representative " "along with the output of 'show usb' 'show usb controller' and " "'show file system' commands." |
|
USB_TOKEN_FILESYS-3-ASYNC_IO_ERROR_CREATING_FILE |
3-Error |
Error creating file: file [chars] ret code [hec] [chars]. |
Token Asynchronous I/O process failed to create a file in USB token device. |
usb-token-filesys |
"Report the error message to your technical representative " "along with the output of 'show usb' 'show usb controller' and " "'show file system' commands." |
|
USB_TOKEN_FILESYS-3-ASYNC_IO_ERROR_DECODE_OP_CODE |
3-Error |
Unrecognized I/O Op-code: [dec]. |
Token Asynchronous I/O process could not decode the Op-code in an I/O request. |
usb-token-filesys |
"Report the error message to your technical representative " "along with the output of 'show usb' 'show usb controller' and " "'show file system' commands." |
|
USB_TOKEN_FILESYS-3-ASYNC_IO_ERROR_WRITING_FILE |
3-Error |
Error writing file: file [chars] ret code [hec] [chars]. |
Token Asynchronous I/O process encountered I/O write failure. |
usb-token-filesys |
"Report the error message to your technical representative " "along with the output of 'show usb' 'show usb controller' and " "'show file system' commands." |
|
USB_TOKEN_FILESYS-3-ASYNC_IO_FAIL_TO_GET_ARGUMENT |
3-Error |
Token Asynchronous I/O: Could not get argument. |
Token Asynchronous I/O process failed to retrieve argument. |
usb-token-filesys |
"Report the error message to your technical representative " "along with the output of 'show usb' 'show usb controller' and " "'show file system' commands." |
|
USB_TOKEN_FILESYS-3-ASYNC_IO_FAIL_TO_REQUEUE_REQUEST |
3-Error |
Token Asynchronous I/O: failing to requeue an I/O request. |
Token Asynchronous I/O process failed to requeue an I/O request. |
usb-token-filesys |
"Report the error message to your technical representative " "along with the output of 'show usb' 'show usb controller' and " "'show file system' commands." |
|
USB_TOKEN_FILESYS-3-ASYNC_IO_UNEXPECTED_EVENT |
3-Error |
Token Asynchronous I/O: Unexpected Event [dec]. |
Token Asynchronous I/O process received an unexpected event. |
usb-token-filesys |
"Report the error message to your technical representative " "along with the output of 'show usb' 'show usb controller' and " "'show file system' commands." |
|
USB_TOKEN_FILESYS-3-FAIL_TO_BUILD_MFD |
3-Error |
USB Token File System failed to build MFD... |
USB Token File System failed to build the Master File Directory MFD database. |
usb-token-filesys |
"Remove this token and insert it again. " "If the problem still persists report the error message to your " "technical representative along with the output of 'show usb' " "'show usb controller' and 'show file system' commands." |
|
USB_TOKEN_FILESYS-3-FAIL_TO_CREATE_TALKER |
3-Error |
Token File System callback: failed to create token talker token name [chars] status [dec]. |
USB Token File System failed to establish connection with USB Token Device Driver. |
usb-token-filesys |
"Remove and insert this token again. " "If the problem still persists report the error message to your " "technical representative along with the output of 'show usb' " "'show usb controller' and 'show file system' commands." |
|
USB_TOKEN_FILESYS-3-FAIL_TO_CREATE_WATCHED_BOOLEAN |
3-Error |
Could not create a watched boolean! |
USB Token File System could not create a watched boolean. This condition indicates that memory resources are being exhausted. |
usb-token-filesys |
"Reduce other system activities to ease memory demands or remove " "any token device that is not in use to free up some memory." |
|
USB_TOKEN_FILESYS-3-FAIL_TO_DESTROY_TALKER |
3-Error |
Token File System callback: failed to destroy token talker token name [chars] status [dec]. |
USB Token File System failed to destroy the connection with USB Token Device Driver. |
usb-token-filesys |
"Insert and remove this token again. " "If the problem still persists report the error message to your " "technical representative along with the output of 'show usb' " "'show usb controller' and 'show file system' commands." |
|
USB_TOKEN_FILESYS-3-FAIL_TO_REGISTER_WITH_IFS |
3-Error |
Failed to register USB Token File System with IFS. |
The process of registering USB Token File System with IOS File System IFS did not succeed. |
usb-token-filesys |
"Remove this token and insert it again. " "If the problem still persists report the error message to your " "technical representative along with the output of 'show usb' " "'show usb controller' and 'show file system' commands." |
|
USB_TOKEN_FILESYS-3-MAX_TOKENS_INSERTED |
3-Error |
The number of tokens exceeded the maximum that can be supported by USB Token File System. |
Maximum number of tokens that can be supported by USB Token File System are already inserted. |
usb-token-filesys |
"Remove the other tokens that are not in use. " "And remove and insert this token again. " "If the problem still persists report the problem to your " "technical representative along with the output of 'show usb' " "'show usb controller' and 'show file system' commands." |
|
USB_TOKEN_FILESYS-3-MFD_FORWARD_INCOMPATIBLE |
3-Error |
Unable to understand MFD database of version [dec].[dec]. |
The version of the Master File Directory MFD database stored |
usb-token-filesys |
"Upgrade the USB Token File System by reloading " "the router with a higher version of IOS software." |
|
USB_TOKEN_FILESYS-3-UNKNOWN_TOKEN_EVENT |
3-Error |
Token File System callback: unknown event [dec]. |
USB Token File System callback function received an unknown event from USB Token Device Driver. |
usb-token-filesys |
"Check USB ports to see if the token device is inserted or removed " "correctly. If the problem still persists report the error message " "to your technical representative along with the output of 'show usb' " "'show usb controller' and 'show file system' commands." |
|
USB_TOKEN_FILESYS-6-REGISTERED_WITH_IFS |
6-Information |
USB Token File System [chars] is registered... |
USB Token File System registered successfully. |
usb-token-filesys |
"Informational message only. No action required." |
|
USB_TOKEN_FILESYS-6-REGISTERING_WITH_IFS |
6-Information |
Registering USB Token File System [chars]: might take a while... |
Registering USB Token File System is being registered. |
usb-token-filesys |
"Informational message only. No action required." |
|
USB_TOKEN_FILESYS-6-USB_TOKEN_INSERTED |
6-Information |
USB Token device inserted: [chars]. |
A USB Token device has been detected. |
usb-token-filesys |
"Informational message only. No action required." |
|
USB_TOKEN_FILESYS-6-USB_TOKEN_REMOVED |
6-Information |
USB Token device removed: [chars]. |
A USB Token device has been removed. |
usb-token-filesys |
"Informational message only. No action required." |
|
USB_TOKEN-3-USB_TOKEN_MAX_TOKENS_INSERTED |
3-Error |
Unavailable USB Security Token slot |
Maximum number of tokens that can be supported are already inserted |
usb-token |
"Remove the other tokens that are not in use. And remove and insert this token again." |
|
USB_TOKEN-3-USB_TOKEN_MSG_FAILURE |
3-Error |
Failure in handling USB Security Token insertion/removal event |
Retrieving Token insertion/removal message failed in Token Daemon |
usb-token |
"Remove the token and insert it back. If the problem still persists\n\ report the problem to your technical support representative along\n\ with the output of \"show usb device\" \"show usb controller\" and\n\ \"show file systems\" commands." |
|
USB_TOKEN-3-USB_TOKEN_NOMEM |
3-Error |
No available memory for [chars] |
Memory allocation failure. |
usb-token |
"Reduce other system activity to ease memory demands. If conditions\n\ warrant upgrade to a larger memory configuration." |
|
USB_TOKEN-3-USB_TOKEN_SEMCREATE_FAILURE |
3-Error |
Failure in creating USB Security Token semaphore |
Watched semaphore creation failed |
usb-token |
"Report the problem to your technical support representative along\n\ with the output of \"show usb device\" and \"show usb controller\" commands." |
|
USB-3-USB_OC |
3-Error |
USB over-current at source 0x[hec]. |
USB interface over-current error. |
cr10k5 |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
USBFLASH0-1-DEVICE_DISABLED |
1-Alert |
usbflash0 device disabled |
usbflash0: is disabled from the system. |
- |
LOG_STD_ACTION |
|
USBFLASH0-6-DEVICE_ENABLED |
6-Information |
usbflash0 device enabled |
usbflash0: is enabled in the system. |
- |
LOG_STD_NO_ACTION |
|
USBFLASH1-1-DEVICE_DISABLED |
1-Alert |
usbflash1 device disabled |
usbflash1: is disabled from the system. |
- |
LOG_STD_ACTION |
|
USBFLASH1-6-DEVICE_ENABLED |
6-Information |
usbflash1 is enabled |
usbflash1: is enabled in the system. |
- |
LOG_STD_NO_ACTION |
|
USBFLASH-3-DEVOPEN |
3-Error |
[chars] [chars] |
An application handle for the usb flash could not be retrieved. |
- |
"Please search Bug Toolkit on the Cisco web site for" "bugs related to your version of software. If you do" "not find an existing bug please open a TAC case and" "provide 'show version' & 'show running'" |
|
USBFLASH-3-DEVSTARTSTOP |
3-Error |
[chars] [chars] |
The usb flash device could not be stopped and restarted. |
- |
"Please search Bug Toolkit on the Cisco web site for" "bugs related to your version of software. If you do" "not find an existing bug please open a TAC case and" "provide 'show version' & 'show running'" |
|
USBFLASH-3-IFSCREATE |
3-Error |
[chars] [chars] |
The usb flash device could not be registered with the internal file system. |
- |
"Please search Bug Toolkit on the Cisco web site for" "bugs related to your version of software. If you do" "not find an existing bug please open a TAC case and" "provide 'show version' & 'show running'" |
|
USBFLASH-4-FORMAT |
4-Warning |
[chars] [chars] |
The usb flash device does not have a recognizable format There are unexpected values in the partition table or boot sector This device needs formatting in the router before use. |
- |
"Follow any instructions provided in the error " "message before storing any file to this USB flash device" |
|
USBFLASH-5-CHANGE |
5-Notice |
[chars] [chars] |
A USB device has been inserted/removed |
- |
LOG_STD_NO_ACTION |
|
USBFLASH-5-DIBERR |
5-Notice |
USB Flash device [chars] [chars] |
The system cannot boot a image from the USB Flash device because the Device Information Block is different. The USB Flash device can be read by the router but will require formatting by the router before an image can be booted from it. |
- |
"Follow any instructions provided in the error " "message. Before storing a image in the USB Flash device " "and trying to boot from this device enter the " "format command to format the flash device from the " "router. Then copy the desired image to the Flash " "device and then boot from this device." |
|
UTD-1-UTD_HEALTH_CHANGE |
1-Alert |
Service node changed state [chars] => [chars] [dec] |
Service node and changed health status\n |
cpp-ucode |
LOG_STD_ACTION |
|
UTD-2-IPC_FAILURE |
2-Critical |
UTD-IPC message [chars] handler failed rc [dec] |
An IPC message handler for the UTD feature failed. This will cause the feature to not function. |
qfp-utd |
LOG_STD_ACTION |
|
UTD-2-IPC_INIT_FAILED |
2-Critical |
UTD-IPC message handler registration failure rc [dec] |
Registering an IPC message handler for the UTD feature failed. This will cause the feature to not function. |
qfp-utd |
LOG_STD_ACTION |
|
UTD-3-FEAT_CTX_DOWN |
3-Error |
UTD-Invalid request [chars] [dec] while context is down |
While the feature context was not active an invalid request was received from another layer of the UTD software stack. |
qfp-utd |
LOG_STD_RECUR_ACTION |
|
UTD-3-FEAT_DOWN |
3-Error |
UTD-Invalid request [chars] [dec] while feature is down |
While the feature was not active an invalid request was received from another layer of the UTD software stack. |
qfp-utd |
LOG_STD_RECUR_ACTION |
|
UTD-3-IPC_INVALID_MSG |
3-Error |
UTD-Invalid request [dec] |
We received an invalid message from another layer of the UTD software stack. |
qfp-utd |
LOG_STD_RECUR_ACTION |
|
UTD-3-IPC_INVALID_MSG_LEN |
3-Error |
UTD-Invalid IPC length [dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Invalid IPC message length |
qfp-utd |
LOG_STD_ACTION |
|
UTD-3-IPC_NORES |
3-Error |
UTD-No space for the IPC reply size [dec] request [dec] |
For a request from upper UTD software stack layers it was not possible to allocate space for a reply for the specified size. |
qfp-utd |
LOG_STD_RECUR_ACTION |
|
UTD-3-IPC_OPEN_REPLY |
3-Error |
UTD-IPC Open Reply failed request [dec] |
For a request from upper UTD software stack layers it was not possible to open the reply buffer. |
qfp-utd |
"This is normally a software issue. " LOG_STD_RECUR_ACTION |
|
UTD-3-IPC_SEND_FAILED |
3-Error |
UTD-IPC [chars] [dec] send failed [dec] |
IPC message send failure |
qfp-utd |
LOG_STD_ACTION |
|
UTD-3-PROXY_HSL_ADD_DEST_FAILED |
3-Error |
- |
HSL adding export destination failed. |
qfp-utd |
LOG_STD_ACTION |
|
UTD-3-PROXY_HSL_BIND_FAILED |
3-Error |
- |
HSL binding to session failed. |
- |
LOG_STD_ACTION |
|
UTD-3-PROXY_HSL_BIND_TEMPLATE_FAILED |
3-Error |
[dec] |
HSL bind template failed at given index. |
qfp-utd |
LOG_STD_ACTION |
|
UTD-3-PROXY_HSL_CREATE_FAILED |
3-Error |
- |
HSL creation failed. |
qfp-utd |
LOG_STD_ACTION |
|
UTD-3-UTD_COND_DEBUG_REG_FAILED |
3-Error |
Failed to initialize Conditional Debugging for UTD |
A non-fatal error occurred when attempting to Register/Initialize\n conditional debugging. |
qfp-ucode |
LOG_STD_ACTION |
|
UTD-3-UTD_TLS_POLICY_CLASSIFY_PKT_FAIL |
3-Error |
UTD TLS policy classify packet fail |
Failed to classify packet according to UTD TLS policy\n |
cpp-ucode |
"1 Run the following command and see if TCAM memory utilization is full\n" |
|
UTD-4-UTD_DIVERT_DROP_PKT |
4-Warning |
Diversion: VPATH decapsulation dropped packet from vrf [chars] [chars] [inet]:[dec] => [inet]:[dec] proto [chars] due to [dec] [chars] ident [dec] [chars] |
- |
- |
- |
|
UTD-4-UTD_ENCAPS_DROP_PKT |
4-Warning |
Diversion: VPATH encapsulation dropped packet from vrf [chars] [chars] [inet]:[dec] => [inet]:[dec] proto [chars] due to [dec] [chars] ident [dec] [chars] |
- |
- |
- |
|
UTD-4-UTD_INSPECT_DROP_PKT |
4-Warning |
Inspection: Dropped packet from vrf [chars] [chars] [inet]:[dec] => [inet]:[dec] proto [chars] due to [dec] [chars] ident [dec] [chars] |
- |
- |
- |
|
UTD-5-UTD_POLICY_DROP_PKT |
5-Notice |
Policy: Dropped packet from vrf [chars] [chars] [inet]:[dec] => [inet]:[dec] proto [chars] due to [dec] [chars] ident [dec] [chars] |
- |
- |
- |
|
UTD-5-UTD_POLICY_NAT_DROP_PKT |
5-Notice |
NAT packet drop |
Packet dropped by NAT during UTD policy phase\n |
qfp-ucode |
LOG_STD_ACTION |
|
UTD-6-UTD_DF_BLACKLIST_MATCH |
6-Information |
UTD WebFilter Domain Blacklist [**] [Domain: [chars]] [Matched Pattern: [chars]] {[chars]} [inet]:[dec] -> [inet]:[dec] |
DNS domain matched to one of the configured blacklist patterns\n |
cpp-ucode |
LOG_STD_NO_ACTION |
|
UTD-6-UTD_DF_WHITELIST_MATCH |
6-Information |
UTD WebFilter Domain Whitelist [**] [Domain: [chars]] [Matched Pattern: [chars]] {[chars]} [inet]:[dec] -> [inet]:[dec] |
DNS domain matched to one of the configured whitelist patterns\n |
cpp-ucode |
LOG_STD_NO_ACTION |
|
UTIL-0-ITEMLIST_RESIZE |
0-Emergency |
An attempt was made to resize an itemlist but not enough memory is available |
An attempt was made to resize itemlist memory to be larger than the memory available. Itemlists are often used when showing interface statistics. This event is unexpected and may be an indication of memory corruption. |
- |
"Note any recent commands that may have triggered this error. " "Copy the error message and traceback exactly as it appears " "and report it to your technical support representative." |
|
UTIL-3-DLL |
3-Error |
Data structure error -- [chars] |
A software error occurred resulting in data structure inconsistency. |
os |
"Copy the error message exactly as it appears and report it to your " "technical support representative." |
|
UTIL-3-IDTREE_NOTRACE |
3-Error |
[chars] |
A software error occurred resulting in a data structure\n\ inconsistency. |
xconnect |
LOG_STD_ACTION |
|
UTIL-3-IDTREE_TRACE |
3-Error |
[chars] |
A software error occurred resulting in a data structure\n\ inconsistency. |
xconnect |
LOG_STD_ACTION |
|
UTIL-3-RADIXTREE |
3-Error |
Data structure error--[chars] |
A software error occurred resulting in a data structure\n\ inconsistency. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative. Ask for their assistance in obtaining\n\ a version of code with the error fixed." |
|
UTIL-3-RANGEINCON |
3-Error |
internal inconsistency [dec] [hec] |
A fatal software error occurred. |
os |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
UTIL-3-RANGENULLINPUT |
3-Error |
null pointer input to range function |
An attempt was made to access a range function with a NULL pointer.\n\ The range list creation failed. |
- |
"Review the error log for a corresponding malloc failed message. Copy\n\ the error message exactly as it appears and report it to your\n\ technical support representative." |
|
UTIL-3-TREE |
3-Error |
Data structure error--[chars] |
A software error occurred resulting in a data structure\n\ inconsistency. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative. Ask for their assistance in obtaining\n\ a version of code with the error fixed." |
|
UTIL-6-RANDOM |
6-Information |
A pseudo-random number was generated twice in succession |
A pseudo-random number generator produced the same number twice\n\ in succession. |
- |
"Under normal circumstances a pseudo-random number generator will\n\ occasionally produce the same number twice in succession and this\n\ is not a problem. However if this message occurs frequently the \n\ system should be manually reloaded. If the message is persistent \n\ across reloads copy the error message exactly as it appears and \n\ report it to your technical support representative." |
|
VASI-2-DB_ALLOC_FAIL |
2-Critical |
VASI pair db allocation failed |
VASI pair database error. Memory chunk creation for VASI pair database has failed. |
asr1k-vasi |
"Check for accurate memory management. " "Perform memory leak checks " "and look for memory corruption causes. " "Execute 'show proc memory' command." |
|
VASI-2-DB_DELETE_FAIL |
2-Critical |
VASI pair db entry delete for interface [chars] failed |
VASI pair database error. Removal of entry from VASI database has failed. |
asr1k-vasi |
"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. " |
|
VASI-2-DB_DESTROY_FAIL |
2-Critical |
VASI pair database destroy failed |
VASI pair database error. Memory chunk destroy has failed for VASI pair database. |
asr1k-vasi |
"Check for accurate memory management. " "Perform memory leak checks " "and look for memory corruption causes. " "Execute show proc memory command." |
|
VASI-2-DB_ENTRY_ALLOC_FAIL |
2-Critical |
VASI pair db entry allocation for interface [chars] failed |
VASI pair database error. Memory chunk allocation for VASI pair database entry has failed. |
asr1k-vasi |
"Check for accurate memory management. " "Perform memory leak checks and " "look for memory corruption causes. " "Execute 'show proc memory' command." |
|
VASI-2-DB_ENTRY_FREE_FAIL |
2-Critical |
VASI pair entry free failed |
VASI pair database error. Memory chunk free of VASI pair database entry has failed. |
asr1k-vasi |
"Check for accurate memory management. " "Perform memory leak checks " "and look for memory corruption causes. " "Execute 'show proc memory' command." |
|
VASI-2-DB_INSERT_FAIL |
2-Critical |
VASI pair db entry add for interface [chars] failed |
VASI pair database error. Insertion of a new entry into VASI pair database has failed. |
asr1k-vasi |
"Check for accurate memory management. " "Perform memory leak checks " "look for memory corruption causes " "verify correct database management. " "Execute 'show proc memory' command." |
|
VCMS-4-CPE_RECORD_FAIL |
4-Warning |
Creation of CPE record failed |
The proxy was unable to create CPE record due to possible memory failure |
- |
- |
|
VCMS-4-CPE_RECORD_FAIL |
4-Warning |
Creation of CPE record failed |
The proxy was unable to create CPE record due to possible memory failure |
- |
- |
|
VCMS-4-MODEM_RECORD_FAIL |
4-Warning |
Creation of Modem record failed |
The proxy was unable to create Modem record due to possible memory failure |
cmts-tools |
"Check CMTS memory failures" |
|
VCMS-4-MODEM_RECORD_FAIL |
4-Warning |
Creation of Modem record failed |
The proxy was unable to create Modem record due to possible memory failure |
cmts-tools |
"Check CMTS memory failures" |
|
VCMS-4-PAKPOOL_BUF_ERR |
4-Warning |
Bad buffer length: [dec] |
The VCMS pakpool buffer was insufficient in size |
cmts-tools |
"Create a DTTS to report/investigate issue." |
|
VCMS-4-PAKPOOL_FAIL |
4-Warning |
Packet pool full |
The VCMS pakpool was unable to allocate a packet |
cmts-tools |
"Check Proxy memory leaks" |
|
VCMS-4-PAKPOOL_FAIL |
4-Warning |
Packet pool full |
The VCMS pakpool was unable to allocate a packet |
cmts-tools |
"Check Proxy memory leaks" |
|
VCMS-4-VCMS_CONNECTION |
4-Warning |
Client connection received for a Linecard [dec]-[dec] already connected |
This linecard is already connected to another VCMS simulator |
cmts-tools |
" Disconnect the first Simulator before attempting" " a new connection" |
|
VCMS-4-VCMS_CONNECTION |
4-Warning |
Client connection received for a Linecard [dec]-[dec] already connected |
This linecard is already connected to another VCMS simulator |
cmts-tools |
" Disconnect the first Simulator before attempting" " a new connection" |
|
VCMS-4-VCMS_CONNECTION_LOSS |
4-Warning |
Connection to simulator lost clearing interfaces for Slot [dec]-[dec] |
The VCMS simulator has disconnected from the CMTS |
cmts-tools |
"LOG_STD_NO_ACTION" |
|
VCMS-4-VCMS_CONNECTION_LOSS |
4-Warning |
Connection to simulator lost clearing interfaces for Slot [dec]-[dec] |
The VCMS simulator has disconnected from the CMTS |
cmts-tools |
"LOG_STD_NO_ACTION" |
|
VCMS-4-VCMS_INTERFACE_NOT_READY |
4-Warning |
Interface not ready |
The VCMS simulator is trying to bring modems on an interface that is not up or ready. |
cmts-tools |
"LOG_STD_NO_ACTION" |
|
VCMS-4-VCMS_INTERFACE_NOT_READY |
4-Warning |
Interface not ready |
The VCMS simulator is trying to bring modems on an interface that is not up or ready. |
cmts-tools |
"LOG_STD_NO_ACTION" |
|
VCMS-4-VCMS_INVALID_INTERFACE |
4-Warning |
Invalid interface Id received from the simulator |
The simulator sent a message with interface ID |
cmts-tools |
"Check the simulator code for possible issues" |
|
VCMS-4-VCMS_INVALID_INTERFACE |
4-Warning |
Invalid interface Id received from the simulator |
The simulator sent a message with interface ID |
cmts-tools |
"Check the simulator code for possible issues" |
|
VCMS-4-VCMS_INVALID_SIZE |
4-Warning |
Invalid message size received from the simulator |
The simulator sent a message with longer than expected packet size |
cmts-tools |
"Check the simulator code for possible issues" |
|
VCMS-4-VCMS_INVALID_SIZE |
4-Warning |
Invalid message size received from the simulator |
The simulator sent a message with longer than expected packet size |
cmts-tools |
"Check the simulator code for possible issues" |
|
VCMS-4-VCMS_INVALID_US_CHAN_ID |
4-Warning |
Invalid US channel id received from the simulator |
The simulator sent a message with invalid US channel id |
cmts-tools |
"Check the simulator code for possible issues" |
|
VCMS-4-VCMS_LC_FWD_AGT_CONNECTION |
4-Warning |
Linecard already connected to fwd agent |
The VCMS simulator is already connected to a linecard via forwarding agent. |
cmts-tools |
"LOG_STD_NO_ACTION" |
|
VCMS-4-VCMS_LC_FWD_AGT_CONNECTION |
4-Warning |
Linecard already connected to fwd agent |
The VCMS simulator is already connected to a linecard via forwarding agent. |
cmts-tools |
"LOG_STD_NO_ACTION" |
|
VCMS-4-VCMS_LC_INBAND_CONNECTION |
4-Warning |
Linecard already connected via Inband Channel |
The VCMS simulator is already connected to a linecard via Toaster Inband channel. |
cmts-tools |
"LOG_STD_NO_ACTION" |
|
VCMS-4-VCMS_LC_INBAND_CONNECTION |
4-Warning |
Linecard already connected via Inband Channel |
The VCMS simulator is already connected to a linecard via Toaster Inband channel. |
cmts-tools |
"LOG_STD_NO_ACTION" |
|
VCMS-5-VCMS_CONNECTION_INIT |
5-Notice |
Simulator version [dec].[dec] from [inet] port [dec] interacting with interface [dec] |
The VCMS simulator has started interacting with this interface |
cmts-tools |
"LOG_STD_NO_ACTION" |
|
VCMS-5-VCMS_CONNECTION_INIT |
5-Notice |
Simulator version [dec].[dec] from [inet] port [dec] interacting with interface [dec] |
The VCMS simulator has started interacting with this interface |
cmts-tools |
"LOG_STD_NO_ACTION" |
|
VCMS-5-VCMS_MAJOR_VER_MISMATCH |
5-Notice |
Error:VCMS connection attempt from client with major version [dec] but expected [dec] |
The VCMS simulator major version mismatch |
cmts-tools |
"LOG_STD_NO_ACTION" |
|
VCMS-5-VCMS_MAJOR_VER_MISMATCH |
5-Notice |
Error:VCMS connection attempt from client with major version [dec] but expected [dec] |
The VCMS simulator major version mismatch |
cmts-tools |
"LOG_STD_NO_ACTION" |
|
VCMS-5-VCMS_MINOR_VER_MISMATCH |
5-Notice |
Warning:VCMS connection attempt from client with minor version [dec] but expected [dec] |
The VCMS simulator mminor version mismatch |
cmts-tools |
"Check CMTS memory failures" |
|
VCMS-5-VCMS_MINOR_VER_MISMATCH |
5-Notice |
Warning:VCMS connection attempt from client with minor version [dec] but expected [dec] |
The VCMS simulator mminor version mismatch |
cmts-tools |
"Check CMTS memory failures" |
|
VDD-3-NULL_CB |
3-Error |
Supplied [chars] control block is NULL. [chars] |
An NULL control block was passed internally in the software as part of an operation to read or write to the required register or memory address. As a consequence the operation could not be processed and the address contents is now out of sync with what it should be if the operation was a write or an incorrect value returned if the operation was a read. |
- |
LOG_STD_ACTION |
|
VDD-3-NULL_SPACE_CB |
3-Error |
Supplied [chars] space control block is NULL. [chars] |
An NULL space control block was passed internally in the software as part of an operation to read or write to the required address. As a consequence the operation could not be processed and the address contents is now out of sync with what it should be if the operation was a write or an incorrect value returned if the operation was a read. |
- |
LOG_STD_ACTION |
|
VDD-3-SIZE_TOO_LARGE |
3-Error |
An attempt was made to create a [chars] of size [dec] bits. \[chars]\. The maximum size supported is [dec] bits. Operation aborted. |
The virtual device driver architecture only supports a maximum as indicated by the message. A request to create an entry greater in size than the limit has been made which is not possible to process. The consequence is that the entry will not be created leading to loss of data the entry was supposed to maintain. |
- |
LOG_STD_ACTION |
|
VDSL_DAEMON-3-FIRMWARE_WARN |
3-Error |
Need to reload IOS for VDSL PHY firmware file change to take effect |
The old phy firmware is used until IOS is reload |
- |
LOG_STD_ACTION |
|
VDSL_DAEMON-3-FPGA_FAIL |
3-Error |
VDSL FPGA Download failed. |
The VDSL module hardware may be bad |
- |
LOG_STD_ACTION |
|
VDSL_DAEMON-3-INITFAIL |
3-Error |
VDSL Daemon [chars] init failed. |
The VDSL module hardware may be bad |
- |
LOG_STD_ACTION |
|
VDSL_DAEMON-3-INVALID_DS |
3-Error |
Daemon [chars] invalid vdsl instance. |
Encounter an invalid vdsl instance |
- |
LOG_STD_ACTION |
|
VDSL_DAEMON-3-MALLOCFAIL |
3-Error |
There is not enough main memory for the new VDSL [chars] firmware images on flash |
The router failed to malloc a buffer for the firmware images\n\on the flash. More DRAM is required for the feature which allows specific\n\VDSL firmware images on the flash to replace the VDSL firmware images\n\embedded in IOS. |
- |
LOG_STD_ACTION |
|
VDSL_DAEMON-3-MODEMRESET |
3-Error |
VDSL Modem reset. [chars] |
The VDSL module is under reset. |
- |
LOG_STD_RECUR_ACTION |
|
VDSL_DAEMON-3-NOMEM |
3-Error |
VDSL Daemon [chars] malloc failed : out of memory |
The router does not have enough memory installed to run this \n\VDSL/ADSL feature |
- |
LOG_STD_ACTION |
|
VDSL_DAEMON-3-NOPROC |
3-Error |
VDSL Daemon [chars] SM create event process failed |
The router does not have enough memory run this VDSL/ADSL feature |
- |
LOG_STD_ACTION |
|
VDSL_DAEMON-3-VDSL_CMD_ADD_FAIL |
3-Error |
VDSL [chars] add failed. |
adding a command exceeds the maximum number of commands allowed |
- |
LOG_STD_ACTION |
|
VDSL_DAEMON-3-VDSL_LINE_UPDOWN |
3-Error |
Controller [chars] line [dec] changed state to [chars] |
VDSL Line changed state |
- |
LOG_STD_ACTION |
|
VDSL_DAEMON-4-INVALID_CDB |
4-Warning |
Invalid daemon [chars] controller [chars]. |
Encounter an invalid daemon cdb instance. |
- |
"nothing" |
|
VDSL_DAEMON-4-MODE_SWITCH |
4-Warning |
Please save the configuration and reload the Router due to the ATM-PTM mode change on vdsl 0 controller |
Operating mode switch between ATM and PTM mode require reload |
- |
"LOG_STD_ACTION" |
|
VDSL_DAEMON-4-QUEUE_EMPTY |
4-Warning |
Daemon [chars] configuration queue is empty. |
program is unable to send a message to the queue process. |
- |
"nothing" |
|
VDSL_DAEMON-4-TRAINMODE_NOT_SUPPORTED |
4-Warning |
[chars] transport mode is not supported on [chars]. |
Only ATM is supported on ADSL and PTM/Ethernet is supported on VDSL2. |
- |
"Change DSLAM profile to select the correct mode for CPE" |
|
VDSL_SFP_MGR-4-DUMP_DELT_DONE |
4-Warning |
Dump DELT info done on interface [chars] |
Dump DELT information of SFP is done. |
- |
"LOG_STD_ACTION" |
|
VDSL_SFP_MGR-4-DUMP_DELT_START |
4-Warning |
Dump DELT info started on interface [chars] |
Dump DELT information of SFP is started |
- |
"LOG_STD_ACTION" |
|
VDSL_SFP_MGR-4-DUMP_DONE |
4-Warning |
Dump internal info done please shut/no shut on interface [chars] to recover |
Dump internal information of SFP is done need to reset SFP |
- |
"LOG_STD_ACTION" |
|
VDSL_SFP_MGR-4-DUMP_START |
4-Warning |
Dump internal info started on interface [chars] |
Dump internal information of SFP is started |
- |
"LOG_STD_ACTION" |
|
VDSL_SFP_MGR-4-DYING_GASP_ARMED |
4-Warning |
Dying Gasp Armed on interface [chars] SFP |
Dying gasp ready to function if power off now |
- |
"LOG_STD_ACTION" |
|
VDSL_SFP_MGR-4-DYING_GASP_DISARMED |
4-Warning |
Dying Gasp Disarmed on interface [chars] SFP |
Dying gasp disabled |
- |
"LOG_STD_ACTION" |
|
VFC-1-ERROR_INTR |
1-Alert |
[chars] Error interrupt occured type = 0x[hec]. |
The DMA engine cannot get to the PCI bus to read descriptors. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
VFC-1-INCORRECT_DSP_ID |
1-Alert |
VFC in slot [dec]: Incorrect [dec] DSP-ID passed by SPI. |
The DSP ID provided by the SPI for download is not valid. |
- |
" Call your technical support representative for assistance." |
|
VFC-1-INVALID_CONFIGURATION |
1-Alert |
vfc[dec] vfc cards has an invalid configuration. |
The software did recognized more dsp interface port than it can \n\ support on this card. |
- |
"Check the part number on the VIC card to see if it is supported\n\ in the version of IOS operational on the router or contact\n\ your technical support representative." |
|
VFC-1-NO_DSPM |
1-Alert |
vfc[dec] No dsp module has been found. |
The software did not find any of DSP module plugged\n\ into the voice card. |
- |
"Check the part number on the dspm card to see if it is supported\n\ in the version of IOS operational on the router or contact\n\ your technical support representative." |
|
VFC-1-NO_RING_DESCRIPTORS |
1-Alert |
No more ring descriptors available on [dec] slot. |
The VFC driver cannot queue messages onto Rossini dma engine for transmit. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative. Reset the DSP's on this port \n\ module." |
|
VFC-1-NODPMEMORY |
1-Alert |
VFC [dec]/[dec] vfc dual-ported memory unavailable. |
The router or access server could not allocate dual-ported memory for the\n\ descriptors. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
VFC-1-TOOBIG |
1-Alert |
[hec] packetsize [dec] too big. |
A packet greater than the 256 bytes received on this interface. |
- |
"The system should recover. No action is required.\n\ \n\ If the problem reccurs it indicates an error that might be\n\ related to data traffic patterns. Copy the error message exactly as it\n\ appears and report it to your technical support representative." |
|
VFC-1-UNKNOWN_DSPM |
1-Alert |
vfc[dec] vfc dspm daughter card has an unknown id of [hec] |
The software did not recognize the type of DSP module \n\ plugged into the voice card. |
- |
"Check the part number on the dspm card to see if it is supported\n\ in the version of IOS operational on the router or contact\n\ your technical support representative." |
|
VFC-3-ERROR_ANALYZE |
3-Error |
[chars] Error analyzing the device in slot [dec]. |
The feature card in this slot could not be recognized. |
- |
"Power down reinsert voice feature card and reboot.\n\ If message recurs call your technical support representative for\n\ assistance." |
|
VFC-3-ERROR_INIT_BLDR |
3-Error |
[chars] Unable to download the Boot loader firmware ret = 0x[hec] |
Error initializing the DSP with the bootloader firmware. |
- |
" Power down reinsert Port Module and reboot.\n\ If message recurs call your technical support representative for\n\ assistance." |
|
VFC-3-ERROR_INIT_OVERLAY |
3-Error |
[chars] Unable to download the Application overlay firmware. Status returned 0x[hec] |
Error initializing the DSP with the application/overlay firmware. |
- |
" Power down reinsert Port Module and reboot.\n\ If message recurs call your technical support representative for\n\ assistance." |
|
VFC-3-INCORRECT_ID |
3-Error |
VFC in slot [dec]: PCI device not supported. |
A interface controller device did not report correct device\n\ ID |
- |
"Power down reinsert Port Module and reboot.\n\ If message recurs call your technical support representative for\n\ assistance." |
|
VFI_REDUNDANCY_STATUS_CHANGED-5-VFI |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
VFI_STATUS_CHANGED-5-VFI |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
VFI-3-ILLEGAL |
3-Error |
[chars] |
An illegal event has been processed by the xconnect subsystem. |
vpls |
LOG_STD_NO_ACTION |
|
VFI-4-CONFIG |
4-Warning |
[chars] |
Invalid VFI configuration data passed. |
vpls |
LOG_STD_NO_ACTION |
|
VFI-6-VFI_STATUS_CHANGED |
6-Information |
Status of VFI [chars] changed from [chars] to [chars] |
VFI status has changed |
vpls |
LOG_STD_NO_ACTION |
|
VIDB-3-FORKFAIL |
3-Error |
Failed to fork process for [chars]. |
Quite likely we ran out of memory. Other explanations are possible. |
idb |
LOG_STD_ACTION |
|
VIDB-3-FREETIMENOTSET |
3-Error |
Value not specified for vidb forcible free time by platform. |
Platform has requested for delayed vidb recycling support but hasn't specified any value for forcible free time. |
Log DDTS against platform. |
LOG_STD_ACTION |
|
VIDEO-3-RF_POSTCONFIG_TIMEOUT |
3-Error |
missing one or more client's RF_POSTCONFIG |
Missing RF_POSTCONFIG done from at least one client |
cbr-video-cp |
"Check if any client has crashed" |
|
VIDEO-3-RF_STBY_BULK_SYNC_TIMEOUT |
3-Error |
Video standby-bulk-sync timed out |
Missing RF_BULK_SYNC done from at least one client |
cbr-video-cp |
"Check if any client is hang or crashed" |
|
VINES-2-BADPARAM |
2-Critical |
[chars] called with [chars] parameter set to [chars] |
One of the VINES lookup functions was called with an illegal\n\ argument. |
vines |
"Copy the message exactly as it appears do a memory dump up to\n\ 128 bytes and the location specified in the error message and report \n\ this information to your technical support representative." |
|
VINES-2-BADTIMER |
2-Critical |
RTP timer for [chars] was found disabled and was reset |
An internal interface timer is not running. This condition usually\n\ occurs after an interface is reset. |
vines |
"No action is required. The system automatically restarts the timer." |
|
VINES-2-CACHEFAILED |
2-Critical |
Cannot build cache entry [dec] bytes for [v-name] on [chars] |
VINES fast switching detected that the packet destined to a given\n\ address did not have proper encapsulation information or its\n\ encapsulation size was too large to fit into the cache. |
vines |
"Verify that the VINES encapsulation and interface-specific mappings\n\ for the interface concerned are properly configured. Copy the \n\ message exactly as it appears and report it your technical\n\ support representative." |
|
VINES-2-CACHEUNSUPP |
2-Critical |
Caching of [chars] not supported on [chars] |
The cache population routing for VINES fast switching was called for\n\ an interface that does not support VINES fast switching. |
vines |
"Copy the message exactly as it appears and report it your technical\n\ support representative. If other encapsulation types are available\n\ on the interface try using them. If this problem is not limited to \n\ one or two destinations but rather occurs with all traffic\n\ using the interface diable VINES fast switching for the\n\ interface until you have identified the real cause of the problem." |
|
VINES-2-CONSISTENCY |
2-Critical |
Error [chars] |
The VINES code ran into a situation that should not happen. For\n\ example an IPC port number needs to be allocated but all 65535 port\n\ numbers are currently in use. Another possible cause is that VINES \n\ attempted to add a cache entry but had no path associated with the \n\ destination address. This may cause temporary slow performance to \n\ only those stations that have experienced this inconsistency \n\ until complete cache entries are added. However connectivity\n\ should not be lost because all data traffic can still be routed \n\ vvia process-level switching. |
vines |
"Copy the message exactly as it appears and report it your technical\n\ support representative. If the warning message is about IPC port \n\ number depletion use the show vines ipc command to check how many \n\ IPC ports are currently in use by which services and determine\n\ whether the IPC connections are all legitimate. To release IPC ports \n\ issue the clear vines ipc command. If the warning message is about\n\ vines cache entries provide the contents of the vines route cache\n\ neighbor and route tables immediately after the error messages \n\ appeared. If the problem persists issue the clear vines\n\ cache command and monitor the router if the situation improves." |
|
VINES-2-CORRUPTENTRY |
2-Critical |
Detected a corrupted entry in the [chars] table |
The VINES code detected that an internal table entry was corrupted. |
vines |
"Copy the message exactly as it appears and report it your technical\n\ support representative. If possible clear the VINES\n\ routing table or neighbor table depending on the table in which the\n\ corrupted entry was observed. This will result in a temporary\n\ loss of connectivity until the routing or neighbor table is rebuilt." |
|
VINES-2-DUPADDR |
2-Critical |
Duplicate address detected on interface [chars] |
The router detected that its VINES address is being used by another\n\ router. |
vines |
"To identify the other router that is using this address manually\n\ inspect each router's configuration. When you have identified\n\ the router with the duplicate address issue the vines routing\n\ recompute command on both routers or issue the enable vines routing \n\ command specifying specify a unique address. If one of the routers \n\ does not support the recompute keyword disable VINES on that router \n\ issue the write terminal command to save the configuration to memory \n\ reboot the router and then enter the vines routing command with\n\ a unique vines address on the offending routers until each router has\n\ a unique address." |
|
VINES-2-ENCAPFAILED |
2-Critical |
Encapsulation failed for [v-name] via [v-name] on [chars] |
VINES fast switching encountered an encapsulation failure\n\ when building a cache entry for a neighbor. |
vines |
"Examine your configuration for causes of the encapsulation failure.\n\ Look for missing map statements interfaces that have gone down and so\n\ on. If this error results in lost connectivity disable vines fast\n\ switching by issuing the no vines route-cache command. Because\n\ disabling fast switching will slow network perform you should\n\ issue the vines route-cache command to re-enable fast switching\n\ as soon as you have identified the cause of the problem. If you\n\ cannot identify the cause contact your technical support\n\ representative. Provide the output of the show vines cache\n\ show vines neighbor and show vines route commands for the\n\ destination address and neighboring routers you are using. Also\n\ provide the output of the show interface and show vinces\n\ interface commands for the incoming and outgoing interfaces." |
|
VINES-2-INVALIDPATH |
2-Critical |
Bad [chars] in path for neighbor entry %z |
While searching the neighbor table the code determined that a pointer\n\ that should point to a VINES path structure actually points to some\n\ other structure. |
vines |
"Copy the message exactly as it appears and report it your technical\n\ support representative. If possible clear the VINES\n\ neighbor table. This will result in a temporary loss of connectivity\n\ until all neighbors and routes are relearned." |
|
VINES-2-INVALIDROUTE |
2-Critical |
Bad [chars] in route for server entry %Z |
While searching the routing table the code determined that a pointer\n\ that should point to a VINES route structure actually points to some\n\ other structure. |
vines |
"Copy the message exactly as it appears and report it your technical\n\ support representative. If possible clear the VINES\n\ routing table. This will result in a temporary loss of connectivity\n\ until all routes are relearned." |
|
VINES-2-NOBUFFERS |
2-Critical |
No buffers available for [chars] |
There were no buffers available to send a VINES service query\n\ or reply. |
vines |
"Examine your system's memory and buffer capacity and compare\n\ it with current usage. If you notice a substantial discrepancy\n\ monitor your system for possible memory leaks or buffer drainage\n\ and report the problem to your technical support representative\n\ along with the output of the show memory show memory processor\n\ show buffers show buffers assigned and show buffers old commands." |
|
VINES-2-NOVENCAP |
2-Critical |
Encapsulation failed on [chars] for address [v-name] |
The VINES code tried to send a packet on an interface that does not\n\ have a new encapsulation routine for outbound packets. |
vines |
"Toggle the problematic interface by issuing the interface shut and\n\ no shut commands and then issue the no vines metric and vines metric\n\ command see if the problem goes away. If the problem persists copy\n\ the message exactly as it appears and report it your technical\n\ support representative. If possible turn on and provide\n\ interface- specific debug traces particularly for VINES activities." |
|
VINES-6-FNNOTFOUND |
6-Information |
[chars] service [chars] routine missing [chars] vector |
There is an inconsistency in the static VINES data structures for\n\ handling application-layer packets. |
vines |
"Turn on VINES service level debugging for the service reported\n\ in the error message and copy the debug traces and the error\n\ message exactly as they appear and report them to your technical\n\ support representative." |
|
VINES-6-IPCNOROUTINE |
6-Information |
IPC port [dec] registered without an upcall [chars] |
There is an inconsistency in the active VINES data structure for\n\ handling IPC data messages. A message was received for a port that\n\ should have a listener but the listener routine cannot be found. |
vines |
"Examine the IPC ports currently supported on the router\n\ by issuing the show vines ipc command and see whether the reported\n\ IPC port is indeed not active. Copy the message exactly as it\n\ appears and report it to your technical support representative\n\ along with the output of the debug vines ipc command." |
|
VINES-6-RPCNOSERVICE |
6-Information |
IPC port [dec] registered without a service |
There is an inconsistency in the active VINES data structure for\n\ handling Net RPC messages. A message was received for a port that\n\ should have a service description but that service description cannot\n\ be found. |
vines |
"Enter the show vines ipc command and see whether the reported IPC\n\ port has a registered service. Copy the message exactly as it\n\ appears and report it to your technical support representative\n\ if possible along with output of the debug vines netrpc command." |
|
VINES-6-RTNNOTFOUND |
6-Information |
[chars] service [chars] routine not found while [chars] |
There is an inconsistency in the active VINES service description data\n\ structures. A service handler routine cannot find the description of\n\ its own service. |
vines |
"Copy the message exactly as it appears and report it your technical\n\ support representative. In addition provide the output of the show\n\ vines service command and debug vines service traces for the\n\ service reported in the error message." |
|
VIPMLP-2-NOINTERLEAVE |
2-Critical |
[chars] Interleave not configured due \n\ to Insufficient memory |
Interleave not configured due to Insufficient memory. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
VIPMLP-2-NOVC |
2-Critical |
[chars]: packet received for non-existent VC [dec] |
Virtual channel encapsulation is corrupted. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
VIRT_SERVICE-3-ACTIVATE_FAIL |
3-Error |
Failed to send virtual service [chars] activate message |
During the creation and transmission of the virtual service activate TDL message a failure occurred. The message was not successfully sent and therefore the virtual service was not activated. |
vman |
LOG_STD_ACTION |
|
VIRT_SERVICE-3-DEACTIVATE_FAIL |
3-Error |
Failed to send virtual service [chars] deactivate message |
During the creation and transmission of the virtual service deactivate TDL message a failure occurred. The message was not successfully sent and therefore the virtual service was not deactivated. |
vman |
LOG_STD_ACTION |
|
VIRT_SERVICE-3-INIT_FAIL |
3-Error |
Failed to initialize required virtual service object: [chars] |
During the initialization of the resources required for the virtual service feature a memory allocation failure occurred. This has prevented the virtual service feature from being enabled. |
vman |
LOG_STD_ACTION |
|
VIRT_SERVICE-3-INVALID_APPLIANCE_TIMEOUT |
3-Error |
A response timeout occurred for an invalid virtual service |
An unexpected condition occurred where the virtual service context pointer in the expired timer was set to NULL. |
vman |
LOG_STD_ACTION |
|
VIRT_SERVICE-3-INVALID_RF_MSG |
3-Error |
Received an invalid RF message type from peer |
An unexpected condition occurred where an invalid message type was detected. |
vman |
LOG_STD_ACTION |
|
VIRT_SERVICE-3-PKG_PATH |
3-Error |
Failed to [chars] required by virtual service [chars] |
Specified package definition file was not found following a switchover. |
vman |
LOG_STD_ACTION |
|
VIRT_SERVICE-3-PKG_PATH_ACTIVATE |
3-Error |
Failed to [chars]. Virtual service [chars] will not be activated |
Specified package definition file was not found following a switchover. Unable to activate virtual service without specified package definition file present. |
vman |
LOG_STD_ACTION |
|
VIRT_SERVICE-3-RESET |
3-Error |
Virtual service [chars] reset |
An unexpected condition has occurred where Virt-manager has reported that it detected the named virtual service reset. This virtual service is not configured to be activated and as such no attempt to reactivate it will be made. |
vman |
LOG_STD_ACTION |
|
VIRT_SERVICE-3-RESPONSE_TIMEOUT |
3-Error |
Virtual service [chars] timed out waiting for a response from Virt-manager |
Failed to receive a response message from Virt-manager for last activation operation performed on the named virtual service. The virtual service activation state was marked as deactivated. |
vman |
LOG_STD_ACTION |
|
VIRT_SERVICE-3-ROMMON_UNSUPPORTED |
3-Error |
ROM monitor configuration does not support virtualization |
Virtualization is not supported by the current ROM monitor configuration. Verify both the ROM monitor version and ROM monitor variable ENABLE_VTX are correct to enable virtualization. |
vman |
LOG_STD_ACTION |
|
VIRT_SERVICE-3-SEND_RF_MSG |
3-Error |
Failed to send RF message to peer - [chars] |
An unexpected condition occurred where an attempt to send an RF message to peer failed. |
vman |
LOG_STD_ACTION |
|
VIRT_SERVICE-3-STBY_PKG_PATH |
3-Error |
Failed to [chars] required by virtual service [chars] on standby |
Specified package definition file was not found on standby. Configuration was accepted. Copy package definition file to standby at earliest convenience. |
vman |
LOG_STD_ACTION |
|
VIRT_SERVICE-3-STBY_ROMMON_UNSUPPORTED |
3-Error |
Standby ROM monitor configuration does not support virtualization |
Virtualization is not supported by the current ROM monitor configuration on the standby. Verify both the ROM monitor version and ROM monitor variable ENABLE_VTX are correct to enable virtualization. |
vman |
LOG_STD_ACTION |
|
VIRT_SERVICE-3-UNKNOWN_APPLIANCE_TIMEOUT |
3-Error |
A response timeout occurred for unknown virtual service [chars] |
A response timeout occurred for a virtual service that is no longer in the virtual service database. |
vman |
LOG_STD_ACTION |
|
VIRT_SERVICE-3-UNKNOWN_RF_MSG |
3-Error |
Received an unknown RF message type [dec] from peer |
An unexpected condition occurred where an unknown timer event was detected. |
vman |
LOG_STD_ACTION |
|
VIRT_SERVICE-3-UNKNOWN_TIMEOUT_TYPE |
3-Error |
A response timeout occurred for an unknown timeout type [dec] |
An unexpected condition occurred where an unknown timeout type was detected. |
vman |
LOG_STD_ACTION |
|
VIRT_SERVICE-3-UNKNOWN_TIMER_EVENT |
3-Error |
A timer event occurred for an unknown timer event [dec] |
An unexpected condition occurred where an unknown timer event was detected. |
vman |
LOG_STD_ACTION |
|
VIRT_SERVICE-3-UNPROVISION_FAIL |
3-Error |
[chars]: [chars] |
During the unprovision of the named virtual service an unexpected failure occurred. |
vman |
LOG_STD_ACTION |
|
VIRT_SERVICE-3-UPGRADE_TIMEOUT |
3-Error |
Virtual service [chars] timed out waiting for a package upgrade response from Virt-manager |
Failed to receive a response message from Virt-manager for last upgrade operation performed on the named virtual service. |
vman |
LOG_STD_ACTION |
|
VIRT_SERVICE-4-SWITCHOVER_ACTIVATE |
4-Warning |
Virtual service [chars] will not be activated following a switchover |
Following a switchover this virtual service will not be activated as there is an issue with its package definition file. Copy package definition file to standby at earliest convenience. |
vman |
LOG_STD_ACTION |
|
VIRT_SERVICE-5-ACTIVATION_STATE |
5-Notice |
[chars] [chars] |
The activation state of the named virtual service has changed as notified by Virt-manager. |
vman |
LOG_STD_ACTION |
|
VIRT_SERVICE-5-INSTALL_STATE |
5-Notice |
[chars] [chars] |
The installation state of the named virtual service has changed as notified by Virt-manager. |
vman |
LOG_STD_ACTION |
|
VIRT_SERVICE-5-RESET_REACTIVATE |
5-Notice |
Virtual service [chars] reset and will be reactivated |
Virt-manager has reported that it detected the named virtual service reset. An attempt will be name to reactivate this virtual service. |
vman |
LOG_STD_ACTION |
|
VLAN_PORT-3-IIF_ID_ALLOC_FAILED |
3-Error |
IIF_ID alloc failed for vlan-port: Port [chars] in Vlan [dec] due to memory allocation failure. Some features will not work. |
The system is low on memory due to which IIF-ID allocation failed. This results in failure to apply polices such as QoS on this vlan-port. |
vlan-port |
LOG_STD_REDUCE_ACTION "Once memory is available unconfigure and reconfigure the vlan on the" "port" |
|
VLAN_PORT-3-IIF_ID_REGISTRATION_FAILED |
3-Error |
IIF_ID registration failed for vlan-port: Port [chars] in Vlan [dec] due to memory allocation failure. Some features will not work. Vlan-port is errdisabled |
The system is low on memory due to which IIF-ID registration failed. This results in failure to apply polices such as QoS on this vlan-port. If port is carrying the vlan vlan-port is errdisabled. |
sw-vlan |
LOG_STD_REDUCE_ACTION "Once memory is available " "run 'clear errdisable interface <intf> vlan <vlanId>' " "or run 'shutdown' followed by 'no shutdown' on the port." |
|
VLAN-3-INTERFACE_NOT_PRESENT |
3-Error |
The [chars] link [chars] does not exist. Sub-interface: [chars] VLAN-Id: [dec] |
This message appears when the below command is issued under port-channel sub-interface with the unknown |
vlan |
"Verify if the interface shows up using the " "command - show ip int brief. \n Please insert " "the card in case it is removed and run " "the command again once the card comes up." |
|
VLAN-3-XDRLEN |
3-Error |
Invalid XDR length. Type [dec] [chars]. XDR/buffer len [dec]/[dec] |
- |
- |
- |
|
VLAN-5-PRIMARY_LINK_NOT_IN_EC |
5-Notice |
Warning: VLAN [dec]'s main interface is not the channel group of primary=[chars]\nPer-VLAN manual load-balancing will not take effect until channel-group is configured under the\n primary interface. |
The interface configured as primary is not a memberlink in the port channel. |
vlan |
"Verify the configuration." |
|
VLAN-5-SECONDARY_LINK_NOT_IN_EC |
5-Notice |
Warning: VLAN [dec]'s main interface is not the channel group of secondary=[chars]\nPer-VLAN manual load-balancing will not take effect until channel-group is configured under the\n secondary interface. |
The interface configured as secondary is not a memberlink in the port channel. |
vlan |
"Verify the configuration." |
|
VOICE_ELOG-3-DUMPFAIL |
3-Error |
Could not dump to remote file - [chars] [chars]. Error=[dec][chars] |
Fail to dump event log to the remote file |
ios-voice |
"Check network connectivity setup and configuration of the protocol" |
|
VOICE_ELOG-3-INIT_FAIL |
3-Error |
Initialization fails - [chars]. |
Fail to initialize event logger system |
ios-voice |
"Check availability of router resource such as memory" |
|
VOICE_ELOG-3-MSGDROPPED |
3-Error |
[dec] messages failed to be written in event log client id:[chars] dump url:[chars]. |
Failed to save event message to the log |
ios-voice |
"Check availability of system memory and " "error for dumping event log if configured" |
|
VOICE_ELOG-4-MEM_USAGE_HI_WATERMARK |
4-Warning |
System memory on high usage [dec]/100. Stopping processing |
System is low on memory so throttle control is applied on\n\ event logger system and it will turn on again when remaining\n\ memory is above high water mark |
ios-voice |
"Ensure that the gateway has the recommended amount of memory for\n\ this IOS feature set and version or scale down usage such as disabling FTP\n\ dump enable event log only for specific application etc." |
|
VOICE_ELOG-5-MEM_USAGE_LO_WATERMARK |
5-Notice |
System memory usage [dec]/100 is below low watermark now. |
System memory is back high so throttle control is removed. |
ios-voice |
"" |
|
VOICE_FILE_ACCT-1-ALLMODE_FAIL |
1-Alert |
All modes of file accounting have failed - [chars]. |
All modes of file accounting failed need to fixed right away in order to not to lose accounting information |
ios-voice |
"Fix the link issues any for ftp link/flash issues then reset file accounting using file-acct reset" |
|
VOICE_FILE_ACCT-3-DUMPFAIL |
3-Error |
Could not dump to remote file - [chars] [chars]. Error=[dec][chars] |
Fail to dump event log to the remote file |
ios-voice |
"Check network connectivity setup and configuration of the protocol" |
|
VOICE_FILE_ACCT-3-INIT_FAIL |
3-Error |
Initialization fails - [chars]. |
Fail to initialize event logger system |
ios-voice |
"Check availability of router resource such as memory" |
|
VOICE_FILE_ACCT-3-MSGDROPPED |
3-Error |
[dec] messages failed to be written in event log client id:[chars] dump url:[chars]. |
Failed to save event message to the log |
ios-voice |
"Check availability of system memory and " "error for dumping event log if configured" |
|
VOICE_FILE_ACCT-4-MEM_USAGE_HI_WATERMARK |
4-Warning |
System memory on high usage [dec]/100. Stopping processing |
System is low on memory so throttle control is applied on\n\ event logger system and it will turn on again when remaining\n\ memory is above high water mark |
ios-voice |
"Ensure that the gateway has the recommended amount of memory for\n\ this IOS feature set and version or scale down usage such as disabling FTP\n\ dump enable event log only for specific application etc." |
|
VOICE_FILE_ACCT-5-MEM_USAGE_LO_WATERMARK |
5-Notice |
System memory usage [dec]/100 is below low watermark now. |
System memory is back high so throttle control is removed. |
ios-voice |
"" |
|
VOICE_HA-1-INTERFACE_DOWN |
1-Alert |
[chars] RG[[dec]] [chars]. |
Interface went down |
voice-ha |
- |
|
VOICE_HA-1-SELF_STATE_PROTECTED |
1-Alert |
[chars] RG[[dec]] [chars]. |
VOICE HA functionality has been disabled in this router due to call checkpointing failure. |
voice-ha |
" Router need immediate reload." |
|
VOICE_HA-2-BULK_SYNC_ERR |
2-Critical |
[chars]. |
VOICE HA INFRA encountered a bulk-sync error. |
voice-ha |
"Collect requested data/traceback and forward to the " "voice-ha component." |
|
VOICE_HA-2-SWITCHOVER_IND |
2-Critical |
[chars]. |
VOICE HA detected a failover transition on the STANDBY to become the new ACTIVE. |
voice-ha |
"Verify calls on the new ACTIVE. " "Peer needs to be in STANDBY mode " "before the next failover." |
|
VOICE_HA-2-SYM_DATA_COLLECT_ERR |
2-Critical |
UC-INFRA HA module [chars] reported DATA COLLECT failure CID:[dec] with error code [dec]. |
Specified HA module reported error during call leg data collection. |
- |
"Collect requested data/traceback and forward to the " "appropriate DDTS-component/module owner " "of the specified HA module for investigation." |
|
VOICE_HA-2-SYM_DATA_RECREATE_ERR |
2-Critical |
UC-INFRA HA module [chars] reported RECREATE failure CID:[dec] with error code [dec]. |
Specified HA module reported error during call leg re-create. |
- |
"Collect requested data/traceback and forward to the " "appropriate DDTS-component/module owner " "of the specified HA module for investigation." |
|
VOICE_HA-3-DATA_COLLECT_ERR |
3-Error |
[chars]: HA Module [chars] reported DATA COLLECT failure mainst ID:[dec] CID:[dec]. |
Specified HA module reported error during call leg data collection. |
- |
"Collect requested data and forward to the " "appropriate DDTS-component/module owner " "of the specified HA module for investigation." |
|
VOICE_HA-3-DATA_RECREATE_ERR |
3-Error |
[chars]: HA Module [chars] reported [chars] RECREATE failure mainst ID:[dec] CID:[dec]. |
Specified HA module reported error during call leg re-create. |
- |
"Collect requested data and forward to the " "appropriate DDTS-component/module owner " "of the specified HA module for investigation." |
|
VOICE_HA-5-PEER_STATE_PROTECTED |
5-Notice |
[chars] RG[[dec]]. HA functionality disabled for Voice. |
VOICE HA functionality is disabled on the peer. due to call checkpointing failure. |
voice-ha |
"Peer Router need immediate reload." |
|
VOICE_HA-5-PEER_STATE_READY |
5-Notice |
[chars] RG[[dec]] VOICE HA Peer exiting from PROTECTED state. |
VOICE HA functionality is enabled on peer. |
voice-ha |
- |
|
VOICE_HA-7-STATUS |
7-Debug |
[chars]. |
VOICE HA INFRA info/status messages. |
voice-ha |
"None" |
|
VOICE_IEC-3-EXT |
3-Error |
Externally-generated Internal Error Code received: [dec].[dec].[dec].[dec].[dec].[dec] |
Some external entity has initiated the termination of a voice call. It has signalled its Internal Error Code to this gateway to be reported in the accounting record for this call. In addition it is being reported through syslog because of the <CmdBold>voice iec syslog<NoCmdBold> configuration. |
ios-voice |
"Refer to the IEC Error Message Decoder at " "http://www.cisco.com/univercd/cc/td/doc/product/voice/vtgemd.htm " "and enter the IEC or enter the <CmdBold>show voice iec " "description<NoCmdBold> <CmdArg>IECvalue<NoCmdArg> command with " "<CmdArg>IECvalue<NoCmdArg> being the value of the IEC that was " "received for more information on the details of this error. It " "is possible some debugging actions might also indicate the cause " "of the error." |
|
VOICE_IEC-3-GK |
3-Error |
[chars]: Internal Error [chars]: IEC=[dec].[dec].[dec].[dec].[dec].[dec] on \n GUID [chars] \n confid [chars] |
An internally-detected error has caused a voice call to be released or terminated. An Internal Error Code IEC has been |
voice-h323 |
"Refer to the IEC Error Message Decoder at " "http://www.cisco.com/univercd/cc/td/doc/product/voice/vtgemd.htm " "and enter the IEC or enter the <CmdBold>show voice iec " "description<NoCmdBold> <CmdArg>IECvalue<NoCmdArg> command with " "<CmdArg>IECvalue<NoCmdArg> being the value of the IEC that was " "received for more information on the details of this error. It " "is possible some debugging actions might also indicate the cause " "of the error." |
|
VOICE_IEC-3-GW |
3-Error |
[chars]: Internal Error [chars]: IEC=[dec].[dec].[dec].[dec].[dec].[dec] on callID [dec] [chars] |
An internally-detected error has caused a voice call to be released or terminated. An Internal Error Code IEC has been |
ios-voice |
"Refer to the IEC Error Message Decoder at " "http://www.cisco.com/univercd/cc/td/doc/product/voice/vtgemd.htm " "and enter the IEC or enter the <CmdBold>show voice iec " "description<NoCmdBold> <CmdArg>IECvalue<NoCmdArg> command with " "<CmdArg>IECvalue<NoCmdArg> being the value of the IEC that was " "received for more information on the details of this error. It " "is possible some debugging actions might also indicate the cause " "of the error." |
|
VOICE_RC-5-DSP_REMOVED |
5-Notice |
DSP ID:[dec] removed from service after [dec] reset within [dec] minutes |
Notification message. |
- |
"dsp might be badopy the error message exactly\n\as it appears and report it to your technical support representative" |
|
VOICE_RC-5-DSP_RESET |
5-Notice |
DSP ID:[dec] reset |
Notification message. |
- |
"IOS reset dsp due to possible dsp error" |
|
VOICE_UTIL-3-NORAWMSG |
3-Error |
no free raw msg structure available from [chars] for signaling message |
There were no rawmsg structures remaining in the system pools to alert the\n\ router of a voice or signaling event. |
ios-voice |
"Check that the voice port for which the event was reported is\n\ still operational. If not clear the voice port." |
|
VOIP_RTP-3-DSCPVIOLATION |
3-Error |
[chars] |
- |
voice-rtp |
"Please check your configuration." |
|
VOIP_RTP-3-MEDIABWVIOLATION |
3-Error |
[chars] |
- |
voice-rtp |
"Please check your configuration." |
|
VOIP_RTP-4-VQM_HALT_ALL |
4-Warning |
System one-minute CPU has reached [dec]%% - Video quality monitoring is halted for all calls. |
Because system one-minute CPU usage has reached a high percentage DSPFarm video quality monitoring service is disabled for all calls which includes on-going calls that were being monitored as well as new calls that are configured to be monitored. |
cube-vqm |
"Check the system CPU and find out the cause of the " "high CPU. Video quality monitoring service should " "not have a significant impact on CPU usage." |
|
VOIP_RTP-4-VQM_HALT_NEW |
4-Warning |
System one-minute CPU has reached [dec]%% - Video quality monitoring is not enabled for new calls. |
Because system one-minute CPU usage has reached a high percentage DSPFarm video quality monitoring service is disabled for new calls that are configured to be monitored. Existing calls that are already monitored are not impacted. |
cube-vqm |
"Check the system CPU and find out the cause of the " "high CPU. Video quality monitoring service should " "not have a significant impact on CPU usage." |
|
VOIP_RTP-5-VQM_RESUME |
5-Notice |
System one-minute CPU is lowered to [dec]%% - Resuming video quality monitoring for all calls. |
Because system one-minute CPU usage has decreased from a high percentage DSPFarm video quality monitoring service is enabled again for all calls which includes on-going calls whose monitoring was halted as well as new calls that are configured to be monitored. |
cube-vqm |
"N/A. This message is purely informational." |
|
VOIP_RTP-6-MEDIA_LOOP |
6-Information |
[chars]\n |
- |
voice-rtp |
"Please check your configuration." |
|
VOIPAAA-3-LOW_CPU_RESOURCE |
3-Error |
VOIPAAA: System running on high cpu usage.\n\ Accounting for callID=[dec] is rejected.\n |
The system does not have sufficient CPU resources\n\ to accept a new call. Any further VoIP AAA requests\n\ will be rejected |
voice-aaa |
"Ensure that the call setup rate is within the supported capacity of\n\ this gateway." |
|
VOIPAAA-5-VOIP_CALL_HISTORY |
5-Notice |
\CallLegType [dec] \ConnectionId [hec][hec][hec][hec] \SetupTime [chars] \PeerAddress %*s \PeerSubAddress %*s \DisconnectCause %*s \DisconnectText %*s \ConnectTime [chars] \DisconnectTime [chars] \CallOrigin %ld \ChargedUnits [dec] \InfoType %ld \TransmitPackets [dec] \TransmitBytes [dec] \ReceivePackets [dec] \ReceiveBytes [dec] |
Call history detail output is used in simple accounting. The ASCII comma\n\ delimited output can be stored using syslogd and passed on to other\n\ billing and/or processing software on a server. |
- |
"" |
|
VOIPAAA-5-VOIP_FEAT_HISTORY |
5-Notice |
\[chars] |
Call feature detail output is used in feature accounting. \n\ This captures multiple feature invokations on a given legthis\n\ can be used for accounting |
- |
"" |
|
VOIPFIB-3-BADIDB |
3-Error |
Invalid IDB: Slot [dec] Channel [dec] |
An internal software error occurred. |
voip_fib |
LOG_STD_SH_TECH_ACTION |
|
VOIPFIB-3-INVALIDSESSION |
3-Error |
Invalid VoIP Session |
An internal software error occurred. |
voip_fib |
LOG_STD_SH_TECH_ACTION |
|
VOIPFIB-3-NODSPINFO |
3-Error |
Failed to get DSP info |
An internal software error occurred. |
voip_fib |
LOG_STD_SH_TECH_ACTION |
|
VOIPFIB-3-NOMEM |
3-Error |
[chars] [dec] [dec] |
An internal software error occurred. |
voip_fib |
LOG_STD_SH_TECH_ACTION |
|
VOIPFIB-3-SBINIT |
3-Error |
Error initializing [chars] subblock data structure. [chars] |
Initialization of the specified subblock data structure could not be accomplished. |
voip_fib |
LOG_STD_ACTION |
|
VPA-1-RPTFAIL |
1-Alert |
[chars] failed to send report [dec] at [chars] - line [dec] |
The port adaptor failed to send a report from vip. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
VPA-3-BADVC |
3-Error |
[chars] [dec]/[dec] got bad VC packet \n%08x %08x %08x %08x %08x %08x %08x %08x |
An interface received a packet with bad VC encapsulation. \n\ This indicates either a software or hardware problem. |
- |
LOG_STD_SH_TECH_ACTION |
|
VPA-3-CMDFAIL |
3-Error |
[chars] Command Failed at [chars] - line [dec] arg [dec] |
The port adaptor failed to process a command. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
VPA-3-FWCRASH |
3-Error |
Firmware for VPA in bay [dec] crashed with exception [hex]\n |
The port adaptor firmware has crashed. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
VPA-3-INITFAIL |
3-Error |
VPA bay [dec] Init Failed at [chars] - line [dec] arg [hec] |
The port adaptor failed to complete hardware initialization. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
VPA-3-TDMFAIL |
3-Error |
VPA-TDM access failed at [chars] - line [dec] arg1=0x%08xarg2=0x%08x |
The port adaptor failed to access TDM switch. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
VPA-3-TSBUSY |
3-Error |
VPA bay [dec] TDM timeslot is busy: ST=[dec]/TS=[dec] |
The port adaptor failed to grand a cross connect setup request. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
VPA-3-TSNONBUSY |
3-Error |
VPA bay [dec] TDM timeslot is non busy: ST=[dec]/TS=[dec] |
The port adaptor failed to grand a cross connect teardown request. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
VPA-3-UNEXPEVENT |
3-Error |
VPA bay [dec] received an unexpected event=[hec] |
The port adaptor received an unexpected event from firmware. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
VPA-5-TXVFULL |
5-Notice |
VPA bay [dec] Voice tx ring is full: dma_done=[dec] last_dma_done=[dec] |
- |
- |
- |
|
VPA-6-NODATA |
6-Information |
Data call is not supported on [chars]. |
Data call is not supported in this version of IOS. |
- |
"Remove data call configuration/setup." |
|
VPA-6-NOTDMBP |
6-Information |
No TDM backplane is supported on slot [dec]. |
Cannot cross connect ds0 inter slot without the TDM backplane. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
VPA-6-NOTSUPPORT |
6-Information |
Voice PA is not supported in this platform. |
The port adaptor is not supported in this platform. |
- |
"Copy the error message exactly as it appears and report it to your\n\ technical support representative." |
|
VPA-6-RXDFILLFAIL |
6-Information |
VPA bay [dec] Data rx ring refill failed: rxd_fill_fail=[dec] |
- |
- |
- |
|
VPA-6-RXVFILLFAIL |
6-Information |
VPA bay [dec] Voice rx ring refill failed: rxv_fill_fail=[dec] |
- |
- |
- |
|
VPDN-3-DROP_ADDR_MISMATCH |
3-Error |
[chars] |
The remote server changed its address. |
vpdn |
"Change initiate-to configuration at the LAC to point to the exact IP " "address LNS will use" |
|
VPDN-3-IP_SWITCH_ERR |
3-Error |
l2x ip switching vector not installed |
Platform dependent l2x ip cef switching module is missing. |
vpdn |
"" |
|
VPDN-3-NORESOURCE |
3-Error |
[chars] [chars][chars] no resources for user [chars][chars][chars] |
The NAS/LAC or HGW/LNS is out of resources for the forwarding of a VPDN user. |
vpdn |
"" |
|
VPDN-4-REFUSED |
4-Warning |
Session for [chars] Refused status = [hec] |
The remote server refused this session. |
- |
"Check configuration on the HG or LNS" |
|
VPDN-4-SESSIONERROR |
4-Warning |
[chars] [chars][chars] unable to terminate user [chars][chars][chars] |
The HGW/LNS was unable to complete the forwarding of the VPDN user due to an internal error. This error may be resource related or configuration related. A reason string may be present to indicate the point of failure. |
vpdn |
"Check the configuration on the HGW/LNS" |
|
VPDN-5-NOIDB |
5-Notice |
[chars] [chars][chars] unable to terminate user [chars] |
The HGW/LNS is out of resources to create sessions for VPDN forwarded users in particular it has reached the maximum number of interfaces allowed on the router. |
vpdn |
"" |
|
VPDN-5-UNREACH |
5-Notice |
[chars] [chars][chars] is unreachable |
The NAS/LAC or HGW/LNS has timed out attempting to establish a tunnel connection to a HGW/LNS or NAS/LAC. This may be due to network or authentication/authorization issues. |
vpdn |
"Check configuration on the NAS/LAC or HGW/LNS check network " "connectivity between the NAS/LAC and HGW/LNS. Check if the tunnel " "setup needs to have a different source IP address from that of " "the NAS/LAC." |
|
VPDN-6-AUTHENERR |
6-Information |
[chars] [chars][chars] cannot authenticate for [chars] [chars] [chars][chars][chars] |
The NAS/LAC or HGW/LNS is unable to locate a AAA server for the purposes of authenticating the user or tunnel. An error of this type indicates that the router was unable to establish a network connection with the designated/configured server. A reason string may also be present to provide further information. |
vpdn |
"Check AAA configuration on the NAS/LAC or HGW/LNS and network " "connectivity to the AAA servers." |
|
VPDN-6-AUTHENFAIL |
6-Information |
[chars] [chars][chars] [chars]authentication failure [chars]for [chars] [chars] [chars][chars][chars] |
The NAS/LAC or HGW/LNS has failed to authenticate a user or a tunnel or the HGW/LNS has failed authentication with the client which initiated the session. For authentication failures of the user or tunnel a reason string should be present which will indicate the point of failure. When a client fails to authenticate the HGW a reason string may be present depending upon the point of failure. |
vpdn |
"Check username configuration on the NAS/LAC or HGW/LNS and possibly " "even the client if the HGW/LNS is failing authentication removing " "the negotiation of outbound authentication is one possible solution " "i.e. only authenticate the user in the inbound direction.\n" "If AAA is applicable check AAA configuration on the NAS/LAC or " "HGW/LNS and network connectivity to the AAA servers." |
|
VPDN-6-AUTHORERR |
6-Information |
[chars] [chars][chars] cannot authorize for [chars] [chars] [chars][chars][chars] |
The NAS/LAC or HGW/LNS is unable to locate a AAA server for the purposes of authorizing the user or tunnel. An error of this type indicates that the router was unable to establish a network connection with the designated/configured server. A reason string may also be present to provide further information. |
vpdn |
"Check AAA configuration on the NAS/LAC or HGW/LNS and network " "connectivity to the AAA servers." |
|
VPDN-6-AUTHORFAIL |
6-Information |
[chars] [chars][chars] [chars]authorization failure for [chars] [chars] [chars][chars][chars] |
The NAS/LAC or HGW/LNS has failed to authorize a user or a tunnel. A reason string may be present to indicate the point of failure. |
vpdn |
"Check authorization configuration on the NAS/LAC or HGW/LNS. If AAA " "is applicable check network connectivity to the AAA servers." |
|
VPDN-6-CLOSED |
6-Information |
[chars] [chars][chars] closed [chars] [chars] [chars][chars][chars] |
The remote server typically the HGW/LNS closed this session. The reason for the closure is encoded in a hexadecimal format and corresponds to the particular protocol descriptions i.e. for L2F the values are documented in section 4.4.5 of the Internet Draft. A description string may also be present which describes the closure reason. |
vpdn |
"Check configuration on the NAS/LAC or HGW/LNS" |
|
VPDN-6-DOWN |
6-Information |
[chars] [chars][chars] changed state to down [chars] [chars] [chars][chars][chars] |
The remote server typically the HGW/LNS closed this tunnel. The\n\ reason for the closure is encoded in a decimal format which\n\ corresponds to the particular protocol descriptions i.e. for L2F\n\ the values are documented in section 4.4.5 of the Internet Draft.\n\ A description string may also be present which describes the\n\ closure reason. |
vpdn |
"Check configuration on the NAS/LAC or HGW/LNS" |
|
VPDN-6-MAX_SESS_EXCD |
6-Information |
[chars] [chars][chars] has exceeded configured local session-limit and rejected [chars] [chars] [chars][chars][chars] |
The NAS/LAC or HGW/LNS has refused this session since the configured\n\ maximum VPDN session limit has been reached. |
vpdn |
"" |
|
VPDN-6-QUEUED_PACKET_INFO |
6-Information |
UnsetQ reached msg alert threshold. local_cc_id=[dec] unsentQ=[dec] resendQ=[dec] max_unsentQ=[dec] max_resendQ=[dec] |
UsentQ size has reached the message alert threshold. Message alert threshold can be configured through CLI 'vpdn queuesize-alert <num>'. |
vpdn |
"" |
|
VPDN-6-RESIZE |
6-Information |
Updated [chars] MID table size to [dec] |
The NAS/LAC or HGW/LNS has altered the size of the session table through command line configuration. |
- |
"" |
|
VPDN-6-SOFTSHUT |
6-Information |
[chars] [chars][chars] has turned on softshut and rejected [chars] [chars] [chars][chars][chars] |
The NAS/LAC or HGW/LNS can no longer accept new connection when\n\ softshut has been turned on. Existing session will continue until\n\ termination. |
vpdn |
"" |
|
VPDN-6-TIMEOUT |
6-Information |
[chars] [chars][chars] disconnected [chars] [chars] [chars][chars][chars] |
The NAS/LAC or HGW/LNS has disconnected the user due to the expiration of a timer this may be e.g. PPP negotiation related or an absolute timeout for the session. |
vpdn |
"" |
|
VPDN-6-TUNNEL_IN_RESYNC |
6-Information |
[chars] [chars] [chars] tunnel is in HA resync reject [chars] [chars] [chars] |
The tunnel towards the peer is still in High Availability HA |
vpdn |
"It is normal for this to occur during tunnel High Availability HA " |
|
VPDN-6-VPDN_DEADCACHE_EVENT |
6-Information |
LSG dead cache entry [inet] [chars] |
A dead cache entry status is changed in the VPDN Load Sharing Group LSG table. The event could be 'Added' where a LSG entry |
vpdn |
"" |
|
VPLS_NP_CLIENT-3-INFO |
3-Error |
[chars] |
VPLS NP Client failed to initialize properly which will result in\n\ improper operation of Any Transport Over MPLS feature |
c7600-sip-400-clnt |
"Try to reload the IOS image on the affected card or platform. If the\n\ error persists record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
VPLS_NP_CLIENT-3-NOMEM |
3-Error |
[chars] |
VPLS NP Client failed to initialize properly which will result in\n\ improper operation of Any Transport Over MPLS feature |
c7600-sip-400-clnt |
"This error may indicate that more memory must be installed on the\n\ affected card or platform in order to service all the features and\n\ related entities enabled via the configuration.\n\\n\ Try to reload the IOS image on the affected card or platform. If the\n\ error persists record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
VPLS_NP_CLIENT-4-WARN |
4-Warning |
[chars] [dec] [chars] |
Entry could not be added because:\n\ 1. Entry passed is invalid. |
c7600-sip-400-clnt |
"Try to reload the IOS image on the affected card or platform. If the\n\ error persists record the output from the following commands:\n\\n\ <Bullet><par><Bold>show tech <NoBold>\n\ <Bullet><par><Bold>show log <NoBold>\n\ <Body><par>Provide this information to your technical support\n\ representative." |
|
VPLS-3-INVALID_ENCAP |
3-Error |
[chars]: [chars] mpls label: [dec] |
Invalid encap type for VPLS processed packet. |
cpp-ucode |
LOG_STD_ACTION |
|
VPN_HW-0-SELF_TEST_FAILURE |
0-Emergency |
Hardware Crypto self-test failed [chars] |
One of the Hardware Crypto self-tests has failed. The Crypto engine is not operable in this state. |
- |
"If the failure persists contact Cisco to " "replace the hardware." |
|
VPN_HW-1-ALIGN |
1-Alert |
Slot: [dec] - Alignment failure on packet buffer: 0x%08x |
A software error occurred. The VPN hardware accelerator driver has detected that the buffer is not aligned correctly. |
vpn_hw |
"Copy the error message exactly as it appears and report it to " "your Cisco technical support representative." |
|
VPN_HW-1-ERROR |
1-Alert |
slot: [dec] - [chars] |
An error occured in the application using VPN_HW. |
vpn_hw |
"Copy the error message exactly as it appears and report it to " "your technical support representative." |
|
VPN_HW-1-HEARTBEAT |
1-Alert |
VPN Module in slot: [dec]: Keepalive lost. |
The VPN hardware accelerator seems to have stopped operating. |
vpn_hw |
"Reboot your router. If this message recurs copy the error message " "exactly as it appears on the console or in the system log contact " "your Cisco techincal support representative and provide the representative " "with the gathered information." |
|
VPN_HW-1-INITFAIL |
1-Alert |
Slot [dec]: [chars] |
The VPN hardware accelerator driver failed to initialize the accelerator at the slot specified in the error message at the specified point. This event will negatively impact encryption performance. User should reload router. |
vpn_hw |
LOG_STD_ACTION |
|
VPN_HW-1-NOMEMORY |
1-Alert |
[chars] creation failed for slot [dec] |
The VPN_HW driver in its initialization phase could not allocate memory for the data structure that is specified in the error message. |
vpn_hw |
"Reduce other system activity to ease memory demands. If conditions " "warrant upgrade to a larger memory configuration. If this " "message recurs copy the error message exactly as it appears on the console " "or in the system log contact your Cisco techincal support " "representative and provide the representative with the gathered information." |
|
VPN_HW-1-OWNER |
1-Alert |
slot: [dec]: [chars] packet buffer pak=0x%08x |
A software or hardware error occurred. The VPN hardware accelerator driver has detected that the buffer ring is in an inconsistent and unrecoverable state. |
vpn_hw |
LOG_STD_ACTION |
|
VPN_HW-1-PACKET_ERROR |
1-Alert |
slot: [dec] Packet Encryption/Decryption error [chars] |
An unexpected error occurred during the encryption or decryption\n\ of a packet. |
- |
"This message can occur occasionally during normal operation of the " "system. It may occur during the transition to a new session key for " "a Security Association. In such cases no action is required. However " "if it happens frequently or is associated with traffic disruption then " "note of the status value and contact a Cisco representative. The " "VPN hardware accelerator will most likely need to be replaced." |
|
VPN_HW-1-TOOBIG |
1-Alert |
Slot: [dec] - [chars] received a packet with size [dec]. |
Software supports upto **** MTU |
vpn_hw |
LOG_STD_ACTION |
|
VPN_HW-1-UNSUPP |
1-Alert |
VPN Module in slot: [dec]: [chars] %08x. |
This revision or version of the VPN hardware accelerator in the slot specified in the error message is not supported. |
vpn_hw |
"Verify the VPN hardware adapter is the proper hardware level and software " "revision for the running version of IOS. If it is " "copy the error message exactly as it appears and report it to " "your Cisco technical support representative." |
|
VPN_HW-3-MULTDEV |
3-Error |
Cannot support more than one Encryption AIMs |
A second Encryption AIM was discovered present in the system. The\n\ Encryption AIM software only supports a single Encryption AIM. All\n\ other Encryption AIMs installed will be ignored. |
- |
"Remove one of the Encryption AIMs installed in your system." |
|
VPN_HW-6-FIPSFAIL |
6-Information |
FIPS test_id [dec][chars] Test Failure will be induced |
The FIPS test was forced to fail from ROMMON |
- |
"Do not set FIPS_FAIL via rommon if fips failure test is not desired" |
|
VPN_HW-6-INFO |
6-Information |
slot: [dec] [chars] |
This is informational message from VPN hardware accelerator driver. |
vpn_hw |
"This is informational message from VPN_HW. This occurs " "in normal operation. No action is required." |
|
VPN_HW-6-INFO_LOC |
6-Information |
Crypto engine: [chars] [chars] |
This is informational message from VPN hardware accelerator driver. |
vpn_hw |
"This is informational message from VPN_HW. This occurs " "in normal operation. No action is required." |
|
VPN_HW-6-SHUTDOWN |
6-Information |
[chars] shutting down |
The specified VPN_HW is shutting down. It may have been physically removed. |
vpn_hw |
"This is an informational message only. It occurs " "in normal operation." |
|
VQPCLIENT-2-CHUNKFAIL |
2-Critical |
Could not allocate memory for VQP |
An error occurred when the system tried to allocate memory for the VQP client. |
dynamic_vlan |
LOG_STD_ACTION |
|
VQPCLIENT-2-DENY |
2-Critical |
Host [enet] denied on interface [chars] |
The VMPS has denied access for the given host MAC address to the specified interface. |
dynamic_vlan |
"No action is normally required. If you feel that " "the host should have been allowed access then the " "configuration on the VMPS should be checked." |
|
VQPCLIENT-2-INITFAIL |
2-Critical |
Platform-specific VQP initialization failed. Quitting |
An error occurred during initialization of the VQPC platform-specific code. |
dynamic_vlan |
LOG_STD_ACTION |
|
VQPCLIENT-2-IPSOCK |
2-Critical |
Could not obtain IP socket |
An error occurred when the system attempted to open an IP socket to the VMPS. |
dynamic_vlan |
LOG_STD_RECUR_ACTION |
|
VQPCLIENT-2-PROCFAIL |
2-Critical |
Could not create process for VQP. Quitting |
An error occurred while creating a process for the VQP client. |
dynamic_vlan |
LOG_STD_ACTION |
|
VQPCLIENT-2-SHUTDOWN |
2-Critical |
Interface [chars] shutdown by VMPS |
The VMPS has directed that the specified interface be shut down. |
dynamic_vlan |
"No action is normally required. If you feel that " "the port should not have been shut down then the " "configuration on the VMPS should be checked." |
|
VQPCLIENT-2-TOOMANY |
2-Critical |
Interface [chars] shutdown by active host limit |
The system has shut down the specified interface because too many hosts have requested access to that port. |
dynamic_vlan |
"To reactivate the port remove the excess hosts " "and issue a no shut command to the interface." |
|
VQPCLIENT-3-IFNAME |
3-Error |
Invalid interface [chars] in response |
The VMPS has sent an unsolicited response with an unknown interface name |
dynamic_vlan |
"Check the VMPS configuration." |
|
VQPCLIENT-3-THROTTLE |
3-Error |
Throttling VLAN change on [chars] |
An attempt was made to change the vlan assignment for the specified interface more often than once every 10 seconds. The vlan change is denied. |
dynamic_vlan |
"No action is normally required. If the message " "recurs check the VMPS configuration. Verify " "that unexpected hosts are not connected to " "the port." |
|
VQPCLIENT-3-VLANNAME |
3-Error |
Invalid VLAN [chars] in response |
The VMPS has specified a vlan name that is unknown to the switch. |
dynamic_vlan |
"Make sure that the vlan exists on the switch. " "Check the VMPS configuration." |
|
VQPCLIENT-4-IPADDR |
4-Warning |
Main IP address on [chars] was deleted |
- |
dynamic_vlan |
- |
|
VQPCLIENT-7-DELETING |
7-Debug |
Freeing deleted saved responses |
- |
dynamic_vlan |
- |
|
VQPCLIENT-7-NEXTSERV |
7-Debug |
Trying next VMPS %I |
The system has lost connectivity with the current VMPS and is switching to the next server in its list. |
dynamic_vlan |
LOG_STD_DBG_ACTION |
|
VQPCLIENT-7-PROBE |
7-Debug |
Probing primary server %I |
The system is trying to reestablish connectivity with the primary VMPS at the given IP address. |
dynamic_vlan |
LOG_STD_DBG_ACTION |
|
VQPCLIENT-7-RECONF |
7-Debug |
Reconfirming VMPS responses |
The switch is reconfirming all responses with the VMPS |
dynamic_vlan |
LOG_STD_DBG_ACTION |
|
VQPCLIENT-7-STARTUP |
7-Debug |
Starting VQP client |
- |
dynamic_vlan |
- |
|
VQPCLIENT-7-STOPPING |
7-Debug |
Stopping VQP client |
- |
dynamic_vlan |
- |
|
VRFS-3-SBINIT |
3-Error |
Error initializing [chars] subblock data structure. [chars] |
Initialization of the specified subblock data structure could not be accomplished. |
VRFS_DDTS_COMPONENT |
LOG_STD_ACTION |
|
VRFS-3-SBNOFN |
3-Error |
Missing [chars] subblock [chars] function for [chars] |
Functions for distributing this subblock are missing from the image. |
VRFS_DDTS_COMPONENT |
LOG_STD_ACTION |
|
VRRP_LOG_CFG_WARN-4-VRRPV3_LOG |
4-Warning |
ERRMSG_NOFLAGS |
- |
- |
- |
|
VRRP_LOG_ERROR-3-VRRPV3_LOG |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
VRRP_LOG_INFO-6-VRRPV3_LOG |
6-Information |
ERRMSG_NOFLAGS |
- |
- |
- |
|
VRRP_LOG_STATE-5-VRRPV3_LOG |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
VRRP_LOG_WARN-4-VRRPV3_LOG |
4-Warning |
ERRMSG_NOFLAGS |
- |
- |
- |
|
VRRP-3-ERROR |
3-Error |
Internal error [chars] |
An internal software error occurred. |
fhrp: vrrp |
LOG_STD_ACTION |
|
VRRP-4-BADAUTH |
4-Warning |
Bad authentication from [inet] group [dec] type [dec] |
Two routers participating in VRRP disagree on authentication |
vrrp |
"Use the vrrp authentication command to repair the VRRP authentication\n\ discrepancy between the local system and the one whose IP address\n\ is reported." |
|
VRRP-4-BADAUTHTYPE |
4-Warning |
Bad authentication from [inet] group [dec] type [dec] expected [dec] |
Two routers participating in VRRP disagree on the valid authentication type. |
vrrp |
"Use the vrrp authentication command to repair the VRRP authentication\n\ discrepancy between the local system and the one whose IP address\n\ is reported." |
|
VRRP-4-CFG_WARN |
4-Warning |
[chars] |
- |
- |
LOG_STD_NO_ACTION |
|
VRRP-4-WARN |
4-Warning |
Internal warning [chars] |
An internal software warning occurred. |
fhrp: vrrp |
LOG_STD_ACTION |
|
VRRP-6-INFO |
6-Information |
Internal info [chars] |
An internal software information message occurred. |
fhrp: vrrp |
LOG_STD_ACTION |
|
VRRP-6-STATE |
6-Information |
[chars] |
The VRRP router has changed state. |
- |
LOG_STD_NO_ACTION |
|
VRRP-6-STATECHANGE |
6-Information |
[chars] Grp [dec] state [chars] -> [chars] |
The VRRP router has changed state |
vrrp |
LOG_STD_NO_ACTION |
|
VRRS_LOG_ERROR-3-VRRS_LOG |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
VRRS_LOG_INFO-6-VRRS_LOG |
6-Information |
ERRMSG_NOFLAGS |
- |
- |
- |
|
VRRS_LOG_STATE-5-VRRS_LOG |
5-Notice |
ERRMSG_NOFLAGS |
- |
- |
- |
|
VRRS_LOG_WARN-4-VRRS_LOG |
4-Warning |
ERRMSG_NOFLAGS |
- |
- |
- |
|
VRRS-3-ACCTFORKFAIL |
3-Error |
Failed to start accounting process. Accounting-off records may not be sent. |
Failed to create the accounting process. |
fhrp |
"Free up some memory." |
|
VRRS-3-ERROR |
3-Error |
Internal error [chars] |
An internal software error occurred. |
fhrp: vrrs |
LOG_STD_ACTION |
|
VRRS-4-WARN |
4-Warning |
Internal warning [chars] |
An internal software warning occurred. |
fhrp: vrrs |
LOG_STD_ACTION |
|
VRRS-6-INFO |
6-Information |
Internal info [chars] |
An internal software information message occurred. |
fhrp: vrrs |
LOG_STD_ACTION |
|
VRRS-6-STATE |
6-Information |
[chars] |
The VRRS router has changed state. |
- |
LOG_STD_NO_ACTION |
|
VSLP_ISSU-3-CAP_RESULT_INCOMPAT |
3-Error |
VSLP ISSU client capability exchange result incompatible. |
VSLP ISSU client capability exchange result incompatible |
vslp |
"show issu negotiated capability <Session_ID>" |
|
VSLP_ISSU-3-INIT |
3-Error |
VSLP ISSU client initialization failed at [chars] error [chars] |
VSLP ISSU client could not be initiailzed this will cause catstrophic failure when ISSU upgrade or downgrade is performed. |
vslp |
LOG_STD_SH_TECH_ACTION |
|
VSLP_ISSU-3-INTERNAL |
3-Error |
An internal error occurred: [chars] |
An unexpected sowftware error during the specified operation |
vslp |
LOG_STD_NO_ACTION |
|
VSLP_ISSU-3-INVALID_PROC_EVENT |
3-Error |
Got event [dec]:[dec] |
The process was woken up with an invalid event |
vslp |
LOG_STD_NO_ACTION |
|
VSLP_ISSU-3-ISSU_ERROR |
3-Error |
[chars] failed with error code [dec] for peer [enet] |
ISSU API failed to do some operation for VSLP layer The message includes the error code from ISSU library |
vslp |
show issu fsm |
|
VSLP_ISSU-3-MSG_NOT_OK |
3-Error |
VSLP ISSU client message [chars] is not compatible |
VSLP ISSU client received an incompatible message from the peer unit. Since the message is not compatible it cannot be processed by this unit |
vslp |
"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
VSLP_ISSU-3-NEGO_FAILED |
3-Error |
VSLP ISSU start nego session with peer [enet] with error code [chars] |
The VSLP ISSU could not start its negotiation process. |
vslp |
"show issu fsm" |
|
VSLP_ISSU-3-NULL_ENTRY |
3-Error |
Null [chars] entry in [chars] |
A NULL entry was passed in the specified operation |
vslp |
LOG_STD_NO_ACTION |
|
VSLP_ISSU-3-PROC_CREATE_FAILED |
3-Error |
Unable to create process \[chars]\ |
Unable to create the specified process because of unknown reasons |
vslp |
LOG_STD_NO_ACTION |
|
VSLP_ISSU-3-QUEUE_CREATE_FAILED |
3-Error |
Unable to create watched queue \[chars]\ |
Unable to create the specified watched queue because of unknown reasons |
vslp |
LOG_STD_NO_ACTION |
|
VSLP_ISSU-3-RX_BAD_INTERFACE |
3-Error |
Incorrect port [dec]/[dec] for received packet |
An VSLP ISSU packet was received that has incorrect received packet info. This could mean either that a VSLP ISSU packet was received from an interface on which VSLP is not enabled. The packet was dropped |
vslp |
LOG_STD_NO_ACTION |
|
VSLP_ISSU-3-RX_QUEUE_FAIL |
3-Error |
Unable to enqueue received packet for processing |
An internal error occurred that prevented a packet from being enqueued to the packet processing queue for processing. The packet was dropped |
vslp |
LOG_STD_NO_ACTION |
|
VSLP_ISSU-3-SEND_FAILED |
3-Error |
VSLP ISSU client failed to send a negotiation message |
VSLP ISSU client could not send a session negotiation message to the peer. When there is a problem in the negotiation the peer switch unit can not be brought up as standby causing to have two active switches in the system. |
vslp |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
VSLP_ISSU-3-SESSION |
3-Error |
VSLP ISSU client [chars] |
VSLP ISSU client observed an error during a session negotiation with the peer unit. When there is a problem with the session the peer switch can not be brought up as standby causing to have two active switches in the system. |
vslp |
"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>" |
|
VSLP_ISSU-3-TRANSFORM |
3-Error |
VSLP ISSU client [chars] transform failed for [chars] message error [chars] |
VSLP ISSU client could not transform the message. If the transmit transformation failed it means that the VSLP message can not be sent to the standby unit. If the receive transformation failed it means that the VSLP message can not be processed on the standby unit. |
vslp |
"show issu session <client_id> and " "show issu negotiated version <session_id>" |
|
VSLP-2-VSL_DOWN |
2-Critical |
[chars]\n |
VSL STATUS CHANGED to DOWN with more detail status |
vsl |
LOG_STD_NO_ACTION |
|
VSLP-3-ICC_ERR |
3-Error |
[chars] |
Failure during the ICC operation |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-3-ISSU_ERROR |
3-Error |
[chars] |
VSLP failed to do an ISSU operation |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-PKT |
3-Error |
VSLP packet error: [chars] |
VSLP packet error for the reason described |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-PKT_CREATE |
3-Error |
Can't create packet: [chars] |
VSLP packet can't be created due to the reason described |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-PKT_RX |
3-Error |
Can't process the received packet: [chars] |
VSLP packet can't be processed due to the reason described |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-PKT_TX |
3-Error |
Can't send packet: [chars] |
VSLP packet can't be sent due to the reason described |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-REGISTRY_ADD_ERR |
3-Error |
Failure in adding to [chars] registry |
Could not add a function to the registry |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-3-RRP_ERR_MSG |
3-Error |
[chars] |
VSLP Role resolution protocol detected an error |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-3-RRP_INSTANCE_OUT_OF_BOUNDS |
3-Error |
Instance value [dec] is outside the expected range |
The instance value received is out of bounds |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-3-RRP_INVALID_INSTANCE |
3-Error |
Instance value [dec] is invalid |
The instance value corresponds to an invalid instance |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-3-RRP_MEMORY_ALLOC_ERR |
3-Error |
Instance:[dec] Peer:[dec]: No memory available for [chars] |
VSLP could not obtain the memory it needs |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-3-RRP_PEER_INFO_ERR |
3-Error |
Instance:[dec] Peer:[dec]: Peer [chars] |
RRP encountered an error associated with this peer |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-3-RRP_PEER_INSTANCE_ERROR |
3-Error |
Instance:[dec] Peer:[dec] Up:[dec] Valid:[dec] Switch:[dec] Role:[chars] PeerRole:[chars]: [chars] |
An error occured pertaining the instance and peer group specified |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-3-RRP_PEER_SUP_PSLOT_ERR |
3-Error |
save_rrp_tlv_data->peer_sup_pslot:[dec] my_sup_pslot:[dec] |
RRP detected difference in peer supervisor pslot |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-3-RRP_RESERVED_PEER_ERR |
3-Error |
Instance:[dec] Peer:[dec]: Reserved peer [dec] [chars] |
RRP detected an error related to reserved peer |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-3-RRP_SESSION_ID_ERR |
3-Error |
Instance:[dec] Peer:[dec]: Session id mismatch. Expected [dec] got [dec] |
VSLP Role Resolution protocol detected an session id mismatch |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-3-RRP_SLOT_PORT_ERR |
3-Error |
Slot:[dec] Port:[dec]: [chars] |
RRP detected an error related to a slot and port |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-3-RRP_TIMER_CREATE_FAIL |
3-Error |
Instance:[dec] Peer:[dec]: Unable to create RRP timer |
RRP timer creation failed for the particular instance and peer |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-RRP_UNEXPECTED_ROLE |
3-Error |
Unexpected roles. Local role = [chars] Peer role = [chars] |
VSLP Role resolution protocol determined inconsistent role information |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-3-RRP_VALUE_ERR |
3-Error |
[chars]: [dec] |
VSLP Role resolution protocol encountered an unknown value |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_BOOLEAN_CREATE_FAILED |
3-Error |
Unable to create watched boolean \[chars]\ |
Unable to create the specified watched boolean due to unknown reasons |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_INST_INVALID_CAP |
3-Error |
Invalid capability [dec] for VSLP instance [dec] |
A VSLP capability was requested that is beyond the current list of supported capabilities |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_INST_OUT_OF_RANGE_CREATE |
3-Error |
Cannot create VSLP instance [dec] |
Unable to create a VSLP instance for the switch id since it is not within the acceptable range |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_INST_OUT_OF_RANGE_DESTROY |
3-Error |
Cannot destroy VSLP instance [dec] |
Unable to destroy the given VSLP instance since it is not witihn the acceptable range |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_LMP_DOMAIN_MISMATCH |
3-Error |
Domain ID in probe packet from peer [dec] is not the same as local Domain ID [dec]. The packet was dropped. |
Virtual switch domain id in probe packet from peer is not the same as the local domain id. The packet was dropped |
vslp |
"Investigate and correct this misconfiguration" |
|
VSLP-3-VSLP_LMP_FAIL_REASON |
3-Error |
[chars]: [chars] |
This message gives the reason for a link to leave LMP operational state |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_LMP_FLAG_SET |
3-Error |
Incorrect flag value 0x[hec] on port [dec]/[dec] |
This is an unexpected value for the flag field of a VSL link. This is due to an internal software error |
vslp |
"show vslp lmp summary and " "show vslp lmp fsm" |
|
VSLP-3-VSLP_LMP_FSM_INVALID_TIMER |
3-Error |
Invalid timer [dec] for port [dec]/[dec] in [chars] operation |
A timer event happened but the timer type was invalid |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_LMP_FSM_NULL_CTXT |
3-Error |
NULL context for FSM action [chars] |
An FSM action routine was invoked but with a NULL context argument |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_LMP_FSM_TIMER_BAD_CTXT |
3-Error |
Invalid or NULL context for timer [dec] in [chars] operation |
A timer event happened but the FSM infrastructure passed to the handler a context pointer that is currently not in use or is NULL |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_LMP_INVALID_PROC_EVENT |
3-Error |
Got event [dec]:[dec] |
The process was woken up with an invalid event |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_LMP_MAX_PGS |
3-Error |
Cannot create more thatn [dec] LMP peer groups |
For some reason the number of LMP peer groups has reacehed the maximum per LMP instance |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_LMP_MAX_PORTS |
3-Error |
Cannot configure more than [dec] ports |
Unable to configure LMP on a port because the maximum number of ports per LMP instance has been reached |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_LMP_PG_CREATE_FAIL |
3-Error |
Unable to create PG [enet] for port [dec]/[dec] |
- |
- |
- |
|
VSLP-3-VSLP_LMP_PG_GET_FAIL |
3-Error |
Unable to get PG [enet] for port [dec]/[dec] |
- |
- |
- |
|
VSLP-3-VSLP_LMP_PG_INCONSISTENT |
3-Error |
PG [enet]:[dec] should have [dec] links but none found |
A link has left a peer group that seems to have more links but none were found |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_LMP_PG_NO_CTRL_LINK |
3-Error |
No control link for preferred PG [dec] |
A peer group has been set as the preferred PG but it has no control link |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_LMP_PG_OUT_OF_RANGE |
3-Error |
Peer group [dec] is out of range |
A peer group has been passed to some API that is out of range |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_LMP_RX_BAD_FIRST_TLV |
3-Error |
Bad first TLV [dec] in received packet on port [dec]/[dec] |
- |
- |
- |
|
VSLP-3-VSLP_LMP_RX_BAD_INTERFACE |
3-Error |
Incorrect port [dec]/[dec] for received packet |
An LMP packet was received that has incorrect received packet info. This could mean either that an LMP packet was received from an interface on which VSLP is not enabled. The packet was dropped |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_LMP_RX_BAD_TLV_COUNT |
3-Error |
Bad TLV count in received packet [dec] |
- |
- |
- |
|
VSLP-3-VSLP_LMP_RX_PLATFORM_REJECT |
3-Error |
Platform TLV rejected for receieved [chars] packet |
One or more platform TLVs were rejected in the received packet. The packet was dropped |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_LMP_RX_QUEUE_FAIL |
3-Error |
Unable to enqueue received packet for processing |
An internal error occurred that prevented a packet from being enqueued to the packet processing queue for processing. The packet was dropped |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_LMP_RX_XFORM |
3-Error |
Failed to transform received [chars] packet |
Failed to do ISSU transformation on the received packet. The packet was dropped |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_LMP_SAME_SWITCH_ID |
3-Error |
Switch id in probe packet is the same as the local switch id [dec]. The packet was dropped. |
Switch id in probe packet from peer is the same as the local switch id. The packet was dropped |
vslp |
"Investigate and correct this misconfiguration" |
|
VSLP-3-VSLP_NULL_ENTRY |
3-Error |
Null [chars] entry in [chars] operation |
A NULL entry was passed in the specified operation |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_PROC_CREATE_FAILED |
3-Error |
Unable to create process \[chars]\ |
Unable to create the specified process because of unknown reasons |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_QUEUE_CREATE_FAILED |
3-Error |
Unable to create watched queue \[chars]\ |
Unable to create the specified watched queue because of unknown reasons |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_REGISTRY_ADD_FAIL |
3-Error |
[chars] registry addition failed |
Failed to add to the the given registry during initialization |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_THREAD_CREATE_FAILURE |
3-Error |
tid [dec]/intvl [dec]: [chars] |
VSLP tx thread creation failed for the specified reason |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-3-VSLP_THREAD_FAILURE |
3-Error |
tid [dec]: [chars] |
General VSLP tx thread failure occurred for the specified reason |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-4-ASIC_DUMP |
4-Warning |
[chars] |
VSL physical link was up and role was not resolved in RRP |
vsl |
LOG_STD_NO_ACTION |
|
VSLP-4-VSL_PREEMPT_TIMER |
4-Warning |
Preempt timer configured to [dec] minutes. Standby will takeover as active in [dec] minutes |
- |
- |
- |
|
VSLP-5-RRP_ACTIVE_PEER_DOWN |
5-Notice |
Communication to active peer went down. Triggering switchover... |
Role resolution protocol got an indication that communication to active peer has gone down. This will in turn trigger a switchover |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-5-RRP_MSG |
5-Notice |
[chars] |
Role resolution protocol event |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-5-RRP_NO_PEER |
5-Notice |
No VSLP peer found. Resolving role as Active |
VSLP could not communicate with any peer. Hence continuing to boot up as active |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-5-RRP_PEER_TIMEOUT |
5-Notice |
VSLP peer timer expired without detecting peer. Resolving role as Active |
Role resolution protocol could not communicate with any peer Before peer timer expiry. Hence continuing to boot up as active |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-5-RRP_PREEMPT |
5-Notice |
[chars] \n\tSwitch [dec]: Priority [dec]: Preempt [chars]\n \tSwitch [dec]: Priority [dec]: Preempt [chars]\n |
Display preemption configuration |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-5-RRP_PREEMPT_IGNORE |
5-Notice |
[chars] |
Ignore preemption configuration due to unsaved configs |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-5-RRP_ROLE_RESOLVED |
5-Notice |
Role resolved as [chars] by VSLP |
Role resolution protocol communicated with peer and resolved role |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-5-RRP_RT_CFG_CHG |
5-Notice |
Configured [chars] value is different from operational value.\n Change will take effect after config is saved and switch [dec] is reloaded.\n |
Role resolution protocol configuration changes by user |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-5-RRP_UNSAVED_CONFIG |
5-Notice |
Ignoring system reload since there are unsaved configurations.\n Please save the relevant configurations |
Role resolution protocol got an indication that we need to reload the system due to role change from active to standby. But the box has some unsaved configurations which will be lost. Hence the user must save relevant configurations. |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-5-RRP_WR_MEM_PROGRESS |
5-Notice |
Ignoring system reload since config save operation is in progress.\n Please wait till the configs are saved |
Role resolution protocol got an indication that we need to reload the system due to role change from active to standby. Since the config save is in progress box will not be reloaded. |
cat6k-vs-infra |
LOG_STD_NO_ACTION |
|
VSLP-5-VSL_UP |
5-Notice |
[chars]\n |
VSL STATUS CHANGED to UP with more detail status |
vsl |
LOG_STD_NO_ACTION |
|
VSLP-6-ACTIVE |
6-Information |
[chars] |
Informational messages regarding the state of the Virtual Switch active supervisor |
vslp |
LOG_STD_NO_ACTION |
|
VSLP-6-STANDBY |
6-Information |
[chars] |
Informational messages regarding the state of the Virtual Switch standby supervisor |
vslp |
LOG_STD_NO_ACTION |
|
VTCP-3-VTCP_CREATE_CB_MALLOC_FAILED |
3-Error |
- |
Malloc failed during VTCP create callback. |
cpp-ucode |
LOG_STD_ACTION |
|
VTSP-2-H320_MATCH_CALL_QUEUE_ERROR |
2-Critical |
Memory corruption is found on H.320 Primary Call Match Data Queue. Queue Size=[dec] |
Failed to match an H.320 primary call for an incoming call due to memory curruption. |
ios-voice |
"Contact your technical support representative. Report the configuration\n\ and full text of the error message." |
|
VTSP-3-CAPABILITYMISMATCH |
3-Error |
voice port [chars]: call connection id [0x[hec] 0x[hec] 0x[hec] 0x[hec]] |
There was a capabilities mismatch between the two call legs.\n\ capabilities are negotiated between call legs for CODEC VAD and\n\ FAX rate. |
ios-voice |
"Check that the dial peer configuration is appropriate for the interface\n\ in question. Also check that and configuration on the interface is\n\ correct." |
|
VTSP-3-DOCALLHISFAIL |
3-Error |
\nvtsp_do_call_history: [chars] |
Allocate or insert an active VTSP call record into call history list failed. |
ios-voice |
"No action is required." |
|
VTSP-3-DSP_TIMEOUT |
3-Error |
DSP timeout on channel [chars] event 0x[hec]: DSP ID=0x[hec]: [chars] call mode=[dec] |
Timeout on DSP response. |
ios-voice |
"The DSP has been automatically reset. If problem persists contact" "your technical support representative" |
|
VTSP-3-DSPALARM |
3-Error |
channel [chars] DSP ID 0x[hec]: status=0x[hec] message=0x[hec] text=[chars] |
The DSP reported a fatal error. All calls on the DSP were dropped\n\ and a DSP reload was attempted. |
ios-voice |
"Verify that the DSP reloaded properly by attempting to place a call\n\ on the affected voice port. Contact your technical support\n\ representative include the full text of the error message." |
|
VTSP-3-FSM_ERROR |
3-Error |
[chars] |
Internal Finite State Machine Error. |
ios-voice |
"Contact your technical support representative include the full text of\n\ the error message." |
|
VTSP-3-MSGSNDFAIL |
3-Error |
channel:[chars] DSP ID:0x[hec] Message ID:0x[hec] |
A message could not be sent to the DSP. The call continued but may\n\ have experienced problems. |
ios-voice |
"Verify that the DSP is still functioning properly by attempting\n\ to place a call on the affected voice port. Contact your technical\n\ support representative include the full text of the error message." |
|
VTSP-3-NOEVENT |
3-Error |
no free event structure available from [chars] for DSP message |
There were no event structures remaining in the system pools to alert the\n\ router of a voice or signaling event. |
ios-voice |
"Check that the voice port for which the event was reported is\n\ still operational. If not clear the voice port." |
|
VTSP-3-VTSP_BLOCK |
3-Error |
vtsp_call_block allocate failed |
VTSP call block allocation failed. |
ios-voice |
"Add more memory" |
|
VTSP-3-VTSP_CALL_DISC_FAILED |
3-Error |
VTSP call disconnect failed. channel id [chars] ret [dec] |
VTSP call disconnect could not be successfully passed and it may result\n\ hung calls. |
ios-voice |
"Contact your technical support representative. Report the configuration\n\ and full text of the error message." |
|
VTSP-3-VTSP_CALL_INFO_CHUNK |
3-Error |
VTSP callInfo chunk creation failed. |
Creation of VTSP callInfo chunk failed due to lack of memory. |
voice-sig-digital |
"Add more memory." |
|
VTSP-3-VTSP_DB_ERR |
3-Error |
vtsp_call_block database error |
Internal VTSP call block database error. This message represents an internal software fault and may manifest itself as dropped or hung calls. |
ios-voice |
"Contact your technical support representative include the full text of\n\ the error message." |
|
VTSP-3-VTSP_HAIRPIN_FAILED |
3-Error |
Call hairpinning failed. cdb 0x[hec] dst_cdb 0x[hec] dst_call_id [dec] |
A DSP-less call could not be hairpinned. |
ios-voice |
"Under heavy traffic this failure may happen because no TDM resources were\n\available. Contact your technical support representative include the full text of the error message." |
|
VTSP-3-VTSP_HAIRPIN_NOTPOSSIBLE |
3-Error |
Call can't be hairpinned. cdb 0x[hec] dst_cdb 0x[hec] dst_call_id [dec] |
A DSP-less call could not be hairpinned. |
ios-voice |
"Check the dial-peer configuration." |
|
VTSP-3-VTSP_HAIRPINN |
3-Error |
hairpin peer cdb does not exist cdb 0x[hec] dst_call_id [dec] |
A hairpin call setup failed because the other call leg does not exist. |
ios-voice |
"Contact your technical support representative. Report the configuration and the full text of the error message." |
|
VTSP-4-FSM_BAD_EVENT |
4-Warning |
Invalid FSM Input on channel [chars]: state=[chars] event=[dec] |
Internal state machine illegal input. This message represents an internal software fault and may manifest itself as dropped or hung calls. |
ios-voice |
"Contact your field service representative if indication is coincident " "with dropped or hung calls." |
|
VTSP-4-VTSP_PLAR_TIE_FAILED |
4-Warning |
VTSP connection plar tie set up failed. channel id [chars] cause [dec] |
Connection plar tie set up failed for non-normal reason |
ios-voice |
"Contact your technical support representative. Report the configuration\n\ and full text of the error message." |
|
VTSP-6-LONG_DUR_CALL_DETECTED |
6-Information |
Long Duration Call is detected [chars]\n |
The call is active for configured duration of long call |
ios-voice |
LOG_STD_ACTION |
|
VTSP-6-UNKNOWN_EXT_AGENT_RESET_ATTEMPT |
6-Information |
Request to reset an uknown external agent ID [dec] attempted. |
A request to reset an external agent eg H323 Gatekeeper or MGCP CA etc |
ios-voice |
LOG_STD_ACTION |
|
VUDI-3-INCONSISTENT_VUDI |
3-Error |
[serial number: [chars]] [vUDI: [chars]] [chars] |
vUDI inconsistency is detected between the license file in this VM and nvram configuration |
virt-infra |
LOG_STD_NO_ACTION |
|
VUDI-4-ABNORMAL_EVENT |
4-Warning |
[serial number: [chars]] [vUDI: [chars]] [chars] |
Abnormal vUDI condition occurs. vUDI subsystem is not working under normal flow |
virt-infra |
LOG_STD_NO_ACTION |
|
VUDI-6-EVENT |
6-Information |
[serial number: [chars]] [vUDI: [chars]] [chars] |
Normal vUDI event in system initialization |
virt-infra |
LOG_STD_NO_ACTION |
|
VUDI-6-UPGRADE_ERROR |
6-Information |
Product upgrade detected. Unable to determine previous product id - Defaulting to [chars] for licensing |
Upgrade vUDI error in system initialization |
virt-infra |
LOG_STD_SH_TECH_ACTION |
|
VUDI-6-UPGRADE_EVENT |
6-Information |
Product upgrade detected. Using previous product id [chars] for licensing |
Upgrade vUDI event in system initialization |
virt-infra |
LOG_STD_NO_ACTION |
|
VXE_CINCO_IF_ADDR-3-ADDR_UPDATE |
3-Error |
VXE Cinco interface: [chars] address [chars] to linux [chars] failed with error [dec] |
The interface IP address program to kernel interface failed.. BinOS application which need IOSd IP address may not work. |
picasso-infra |
LOG_STD_ACTION |
|
VXE_CINCO_IF_ADDR-6-ADDR_VRFID_UPDATE |
6-Information |
VXE Cinco interface: [chars] address [chars] to linux [chars] not programmed for vrf_id [dec] |
The interface IP address program to kernel interface not programmed.. BinOS application should only use global IP address for now. |
- |
- |
|
VXE_CLOUD_HA-3-FAILED |
3-Error |
VXE Cloud HA BFD state transitioned [chars] node [dec] event [chars] failed |
The BFD state transitioned but failed to perform route replacement |
vxe-iosd-infra |
LOG_STD_ACTION |
|
VXE_CLOUD_HA-3-INIT |
3-Error |
VXE Cloud HA [chars] failed |
Memory allocated is not enough |
iosxe-mibs |
LOG_STD_ACTION |
|
VXE_CLOUD_HA-4-NOTCFGD |
4-Warning |
VXE Cloud HA BFD is enabled but [chars] node [dec] not fully configured flags=0x[hec] |
The BFD state transitioned but not all Cloud paramerters were configured |
vxe-iosd-infra |
LOG_STD_NO_ACTION |
|
VXE_CLOUD_HA-6-BFDCONFIG |
6-Information |
VXE BFD peer [inet] configuration [chars] from [chars] |
The BFD configuration was removed while cloud HA is still configured |
vxe-iosd-infra |
LOG_STD_NO_ACTION |
|
VXE_CLOUD_HA-6-BFDCONFIGV6 |
6-Information |
VXE BFD peer [chars] configuration [chars] from [chars] |
The BFD configuration was removed while cloud HA is still configured |
vxe-iosd-infra |
LOG_STD_NO_ACTION |
|
VXE_CLOUD_HA-6-BFDEVENT |
6-Information |
VXE BFD peer [inet] interface [chars] transitioned to down |
The BFD interface transitioned to down triggering a VXE Cloud HA event. |
vxe-iosd-infra |
LOG_STD_NO_ACTION |
|
VXE_CLOUD_HA-6-SUCCESS |
6-Information |
VXE Cloud HA BFD state transitioned [chars] node [dec] event [chars] successful |
The BFD state transitioned and successfull performed the route replacement |
vxe-iosd-infra |
LOG_STD_ACTION |
|
VXE_CLOUD_HTTP-4-METERING_API_HEADER_CREATION_FAILURE |
4-Warning |
Failed to create header and payload for metering request with role credentials [dec] |
- |
- |
- |
|
VXE_CLOUD_HTTP-4-METERING_API_INIT_FAILURE |
4-Warning |
Could not initialize metering HTTP |
- |
- |
- |
|
VXE_CLOUD_HTTP-4-METERING_API_POST_FAILURE |
4-Warning |
HTTP API Failure posting metering data failed with api_status: [dec]! |
- |
- |
- |
|
VXE_CLOUD_HTTP-4-METERING_API_REQUEST_FAILURE |
4-Warning |
AWS httpc_send_request failed [hex]\nURL=[chars]\n |
- |
- |
- |
|
VXE_CLOUD_HTTP-4-METERING_API_RESPONSE_FAILURE |
4-Warning |
HTTP error posting metering data with status code: [dec] and response data: [chars] |
- |
- |
- |
|
VXE_CLOUD_HTTP-4-METERING_DATA_FILE_FAILURE |
4-Warning |
Could not open data file in role credentials[dec]: [chars] |
- |
- |
- |
|
VXE_CLOUD_HTTP-4-METERING_GET_ROLE_FAILURE |
4-Warning |
HTTP API Failure getting role name |
- |
- |
- |
|
VXE_CLOUD_HTTP-4-METERING_GET_ROLE_FAILURE_RESP |
4-Warning |
HTTP error getting role name: [dec] |
- |
- |
- |
|
VXE_CLOUD_HTTP-4-METERING_OPEN_HEADER_FILE_FAILURE |
4-Warning |
Could not open header file in role credentials[dec]: [chars] |
- |
- |
- |
|
VXE_CLOUD_HTTP-4-METERING_PAYLOAD_FAILURE |
4-Warning |
Could not create request payload |
- |
- |
- |
|
VXE_CLOUD_HTTP-4-METERING_ROLE_FAILURE |
4-Warning |
HTTP API Failure getting role credentials with api status: [dec] |
- |
- |
- |
|
VXE_CLOUD_HTTP-4-METERING_ROLE_RESPONSE_FAILURE |
4-Warning |
HTTP API Failure getting role credentials with api status: [dec] and response data: [chars] |
- |
- |
- |
|
VXE_CLOUD_HTTP-4-METERING_URL_FAILURE |
4-Warning |
Could not open metering url in role credentials[dec]: [chars] |
- |
- |
- |
|
VXE_CLOUD_IMAGE-3-THROUGHPUT |
3-Error |
Unexpected read value of desired throughput - [dec] kbps |
- |
- |
- |
|
VXE_CLOUD_IMAGE-4-PAYG_NOT_SUPPORTED |
4-Warning |
Pay-as-you-goPAYG is not supported in controller mode.You will be billed hourly as long as this VM is up.To Prevent this Either switch to Auto mode where PAYG is supported or switch to a BYOL instance |
- |
- |
- |
|
VXE_CLOUD_IMAGE-6-CLOUD_IMAGE |
6-Information |
System being booted in [chars] mode |
- |
- |
- |
|
VXE_CLOUD_METERING-3-CONF_FAILED |
3-Error |
Configuration failed for Metering Service |
- |
csr1k-cloud |
- |
|
VXE_CLOUD_METERING-4-METERING_FLAG |
4-Warning |
[chars] |
- |
- |
- |
|
VXE_CLOUD_METERING-4-OUT_OF_COMPLIANCE_EXCEEDED_GRACE_PERIOD |
4-Warning |
[chars] |
- |
- |
- |
|
VXE_CLOUD_METERING-4-OUTSTANDING_HRS_WARNING |
4-Warning |
[chars] |
- |
- |
- |
|
VXE_CLOUD_METERING-4-PERSISTENT_FAILURE |
4-Warning |
Failed to set partial hr gbytes: [chars] with error: [dec] |
- |
- |
- |
|
VXE_CLOUD_METERING-4-PERSISTENT_FAILURE_OOC |
4-Warning |
Set persistent failed to set out of compliance [chars] hrs with error: [dec] |
- |
- |
- |
|
VXE_CLOUD_METERING-4-VARIANT_NOT_FOUND |
4-Warning |
Match not found. Variant is: [chars]\n |
- |
- |
- |
|
VXE_CLOUD_METERING-6-COMPLIANT |
6-Information |
[chars] |
- |
- |
- |
|
VXE_CLOUD_METERING-6-OUT_OF_COMPLIANCE |
6-Information |
[chars] |
- |
- |
- |
|
VXE_CLOUD_METERING-6-OUTSTANDING_HRS_INFO |
6-Information |
You have outstanding metering charges from a previous boot! We will try to restore your compliance in the next hour! You have been out-of-compliance for [dec] hours! Throughput will be restricted after [dec] hours! |
- |
- |
- |
|
VXE_CLOUD_METERING-6-OUTSTANDING_HRS_REACHABILITY_INFO |
6-Information |
[chars] |
- |
- |
- |
|
VXE_CLOUD_METERING-6-OUTSTANDING_HRS_RELOAD_INFO |
6-Information |
[chars] |
- |
- |
- |
|
VXE_CLOUD_METERING-6-PARTIAL_HR_OOC |
6-Information |
Partial hour usage from previous boot will be treated as out-of-compliance until we've been able to report it. The partial hour value has been added to any outstanding OOC value which is now: [dec]ll. We will try to report this to AWS in the next hour to restore compliance! |
- |
- |
- |
|
VXE_CLOUD_METERING-6-TEST_MODE |
6-Information |
[chars] |
- |
- |
- |
|
VXE_MEMORY_UPGRADE-3-CONF_FAILED |
3-Error |
Configuration of memory failed. |
An error occurred when memory configuration was attempted. |
iosxe-csl |
- |
|
VXE_MEMORY_UPGRADE-3-SETUP_FAILED |
3-Error |
Memory upgrade setup failed. Memory upgrade operations may not be successful. |
An error occurred when licensing tried to setup the memory upgrade |
iosxe-csl |
- |
|
VXE_METERING-3-CONFIG_FAILED |
3-Error |
Configuration failed.Failed to initialize metering service Falling back to limited throughput |
Failed to initialize metering service |
iosxe-csl |
- |
|
VXE_RELOAD-6-UDI_CHANGE |
6-Information |
Smart License Authorization Code is not already installed on the device. vManage UUID will be used as SN in license UDI for vManage HSeck9 management. System is about to reload to accommodate the UDI change. This is an expected reload by design. No action is required from the user |
If Smart License Authorization Code is not installed prior to the release where vManage starts managing HSeck9 then the device will use vManage UUID as SN in license UDI since vManage is not aware of platform SN. Reload is required since the platform returns device UDI to infra initially UDI is cached and cannot be changed dynamically and later determines UUID |
csr1kv-csl |
- |
|
VXE_THROUGHPUT-2-LOW_THROUGHPUT |
2-Critical |
System throughput set to low default level 1000 kbps system performance can be severely impacted. Please install a valid license configure the boot level and reload to switch to a higher throughput |
No valid Active license |
iosxe-csl |
- |
|
VXE_THROUGHPUT-2-LOW_THROUGHPUT_LICENSE_GRACE_PERIOD_END |
2-Critical |
Grace period has expired. System throughput set to default level [dec]00 kbps system performance can be severely impacted. Please install a valid license to configure a higher throughput |
No valid license installed. Register with smart account and request a license using 'platform hardware throughput level MB <>' CLI |
csr1kv-csl |
- |
|
VXE_THROUGHPUT-3-CONF_FAILED |
3-Error |
Configuration failed. Installed license does not support the throughput level. Please install the valid license |
An error occurred when the throughput configuration was attempted. |
- |
- |
|
VXE_THROUGHPUT-3-EULA_NOT_ACCEPTED |
3-Error |
The EULA has to be accepted prior to throughput configuration. |
Users need to accept EULA to activate the license |
iosxe-csl |
"Accept EULA for throughput license" |
|
VXE_THROUGHPUT-3-INVALID_CONFIG |
3-Error |
Throughput level was not set or an invalid throughput level was selected. |
The configured throughput level is unknown |
iosxe-csl |
- |
|
VXE_THROUGHPUT-3-NOT_SUPORRT_LEVEL |
3-Error |
Memory license can only be used in premium level. Please configure license boot level to premium |
Users has configured extra memory but CSR boots up in the level that does not support memory licenses. |
iosxe-csl |
- |
|
VXE_THROUGHPUT-3-RELOAD_REQUIRED |
3-Error |
The transition from smart licensing mode to CSL mode needs a reload |
We don't support the transition from smart licensing mode to CSL mode on the fly. A reload is required in this case |
iosxe-csl |
- |
|
VXE_THROUGHPUT-3-SETUP_FAILED |
3-Error |
Throughput upgrade license set up failed |
An error occurred when setting up the throughput upgrade licenses. |
iosxe-csl |
- |
|
VXE_THROUGHPUT-6-AUTOSCALE_EVAL_EXPIRED |
6-Information |
Autoscale evaluation period has expired |
Autoscale evaluation period has expired. |
csr1kv-csl |
- |
|
VXE_THROUGHPUT-6-CLI_RESTRICTED_EVAL_LICENSE_EXPIRED |
6-Information |
System is in feature restricted mode due to evaluation license expiry. Configuration CLIs have been blocked. nvram:startup-config is write protected read-only. |
System is in feature restricted mode due to evaluation license expiry. Configuration CLIs have been blocked. nvram:startup-config is write protected read-only. |
csr1kv-csl |
- |
|
VXE_THROUGHPUT-6-CLI_RESTRICTED_LICENSE_COMM_FAILED |
6-Information |
System is in feature restricted mode due to communication fault to license server. Configuration CLIs have been blocked. nvram:startup-config is write protected read-only. |
System is in feature restricted mode due to communication fault to license server. Configuration CLIs have been blocked. nvram:startup-config is write protected read-only. |
iosxe-csl |
- |
|
VXE_THROUGHPUT-6-CLI_RESTRICTED_LICENSE_EXPIRE |
6-Information |
System is in feature restricted mode due to license expiry. Configuration CLIs have been blocked. nvram:startup-config is write protected read-only. |
System is in feature restricted mode due to license expiry. Configuration CLIs have been blocked. nvram:startup-config is write protected read-only. |
iosxe-csl |
- |
|
VXE_THROUGHPUT-6-CSL_TO_SL |
6-Information |
Transition to Smart license mode if there were Active CSL licenses prior to the transition please convert them to smart licenses |
Transition to Smart license mode if there were Active CSL licenses prior to the transition please convert them to smart licenses |
iosxe-csl |
- |
|
VXE_THROUGHPUT-6-EXTENDED_EVAL_EXPIRED |
6-Information |
Extended evaluation period expired |
Extended 90 day evaluation period expired. |
csr1kv-csl |
- |
|
VXE_THROUGHPUT-6-EXTENDED_EVAL_START |
6-Information |
Entering extended evaluation period |
System running configured features in extended 90 day evaluation period which begins immediately after standard 90 day smart agent eval expires. |
csr1kv-csl |
- |
|
VXE_THROUGHPUT-6-LEVEL |
6-Information |
Throughput level has been set to [dec]00 kbps |
Throughput level has been set to a number |
iosxe-csl |
- |
|
VXE_THROUGHPUT-6-LOWER_THROUGHPUT |
6-Information |
Lower throughput is chosen because of the higher priority base license |
If there is no configuration or the configuration could not be met premium has higher priority than advance and than standard. |
iosxe-csl |
- |
|
VXE_THROUGHPUT-6-THROUGHPUT_LICENSE_GRACE_PERIOD_MSG |
6-Information |
Grace period will expire in [dec] days and system throughput will be set to default level [dec]00kbps on expiration so system performance can be severely impacted. Valid license must be installed to avoid throughput being throttled. |
System throughput will be set to default level on expiration of grace period and system performance can be severely impacted. Valid license must be installed to avoid throughput being throttled. |
csr1kv-csl |
- |
|
VXE_VNIC_IF-3-HOT_FAIL |
3-Error |
vNIC ethernet hot processing failed - [chars] |
vNIC hot add or remove event processing failed. |
vxe-iosd-infra |
LOG_STD_ACTION |
|
VXE_VNIC_IF-3-MSGINITERROR |
3-Error |
VXE vNIC interface command: [chars] failed: [dec] for [chars] |
The vNIC ethernet interface subsystem has failed to communicate with the infrastructure for port Configuration of vNIC ethernet. |
vxe-iosd-infra |
LOG_STD_ACTION |
|
VXE_VNIC_IF-3-PERSINITERROR |
3-Error |
Duplicate mac address in the VXE vNIC interface persistent name table: [enet] |
There are two vNIC configured with the same mac address. This could cause inconsistency with the interface persistent. |
vxe-iosd-infra |
LOG_STD_ACTION |
|
VXE_VNIC_IF-3-PROCESS_CREATE_FAIL |
3-Error |
vNIC ethernet [chars] process creation failed |
Can not create IOS process for vNIC ethernet statistics |
vxe-iosd-infra |
LOG_STD_ACTION |
|
VXE_VNIC_IF-4-DRIVER_DEPRECATED |
4-Warning |
Interface with address [chars] using deprecated [chars] driver. |
Interfaces using an deprecated driver will not be supported in the next release. |
csr1kv-ethernet |
LOG_STD_ACTION |
|
VXE_VNIC_IF-4-DRIVER_NOT_SUPPORTED |
4-Warning |
Ignoring interface with address [chars] using unsupported [chars] driver. |
Interfaces using an unsupported driver will not be configured. |
csr1kv-ethernet |
LOG_STD_ACTION |
|
VXE_VNIC_IF-4-INTF_CONFIG_LOST |
4-Warning |
Address [enet] previously used for [chars] interface configuration not restored. |
An interface was added to the system using the same MAC address but different device driver so the previous interface configuration is lost. |
csr1kv-ethernet |
LOG_STD_ACTION |
|
VXE_VNIC_IF-4-UNITS_EXHAUSTED |
4-Warning |
Unable to assign vNIC unit number to interface with address [enet]. All vNIC unit numbers have been assigned. |
All vNIC unit numbers have been assigned and no more vNICs may be added. |
vxe-iosd-infra |
LOG_STD_ACTION |
|
VXE_VNIC_IF-4-UNITS_RESERVED |
4-Warning |
Unable to assign vNIC unit number to interface with address [enet]. Reload to re-use reserved unit numbers. |
Unit numbers for previously removed vNICs are being reserved for re-use if the vNICs are re-added. Reloading the system should allow the new vNIC to be assigned a unit number. |
vxe-iosd-infra |
LOG_STD_ACTION |
|
VXE_VNIC_IF-4-VXE_INSTANCE_ID_CHANGED |
4-Warning |
Router's cloud metadata based instance id changed from [chars] to [chars] |
Router's instance id is changed so it may trigger UDI invalidation. |
csr1k-cloud |
LOG_STD_ACTION |
|
VXE_VNIC_IF-5-MSG_LCN_WARN |
5-Notice |
VXE vNIC interface: [chars] disabled due to the expired license |
The vNIC ethernet interface disabled due to expired license. |
vxe-iosd-infra |
LOG_STD_ACTION |
|
VXE_VNIC_IF-6-INTF_CONFIG_RESTORED |
6-Information |
Address [enet] previously used for [chars] interface configuration restored. |
An interface was added to the system using the same MAC address and device driver so the previous interface configuration is restored. |
csr1kv-ethernet |
LOG_STD_ACTION |
|
VXE_VNIC_IF-6-RING_CONF_FAILED |
6-Information |
Configurating ring entries failed |
An error occurred when the ring size configuration was attempted. |
ultra-ethernet |
LOG_STD_ACTION |
|
VXE_VNIC_IF-6-VXE_UUID_CHANGED |
6-Information |
Router UUID changed from [chars] to [chars] |
Router UUID is changed so persistent interface data is not used. |
ultra-ethernet |
LOG_STD_ACTION |
|
VXE_VNIC_IF-6-VXE_UUID_INVALID |
6-Information |
Router has invalid or no UUID |
Router UUID is invalid or not preset persistent interface data is not used. |
ultra-ethernet |
LOG_STD_ACTION |
|
WANPHY-4-WANALARM |
4-Warning |
[chars]: [chars] [chars] |
The specified WANPHY Alarm has been declared or cleared. |
c7600-es-platform |
"Recommended action is to repair the source of the alarm." |
|
WARMUPGRADE-3-CHECKSUM |
3-Error |
[chars] image checksum mismatch. |
The checksum of the image in memory is different from the expected \n\ checksum |
os |
"Check whether the image file is complete and uncorrupted" |
|
WARMUPGRADE-3-DECOMPRESS |
3-Error |
Image file decompression failure. |
Warm upgrade could not decompress the image file |
os |
"Check whether the image file is complete and uncorrupted" |
|
WARMUPGRADE-3-FILE |
3-Error |
Image file open/read failure. |
Warm upgrade could not open or read from the image file specified |
os |
"Check whether the specified image is present at the desired location " "and has the required read permissions. If the location is remote " "check whether the connectivity is there." |
|
WARMUPGRADE-3-FORMAT |
3-Error |
Unknown image file format. |
Warm upgrade could not recognize the format of the image file |
os |
"Check whether the specified image is a valid IOS executable in\n\ a supported format. Check release notes for supported formats" |
|
WARMUPGRADE-3-SIZE |
3-Error |
[chars] image size mismatch. |
The size of the image in memory is different from the expected size |
os |
"Check whether the image file is complete and uncorrupted" |
|
WARNING-4-OF_AGENT |
4-Warning |
ERRMSG_NOFLAGS |
- |
- |
- |
|
WBCMTS_GIGE-4-LINK_ERROR |
4-Warning |
[chars] |
error in Gige link state update protocol |
cmts-vpa |
LOG_STD_ACTION |
|
WCCP-1-SERVICELIST |
1-Alert |
Failed to derive service [chars][chars][chars] from service-list [chars] |
The WCCP Access Control List used to define the specified closed service has been modified and can no longer be used to create the service. The service has been marked as inactive. Either change the configuration to an Open service or update the ACL to correctly identify the desired service |
wccp |
"Update the service-list ACL to correctly define the desired service" |
|
WCCP-1-SERVICELOST |
1-Alert |
Service [chars][chars][chars] lost on WCCP client [chars] |
WCCP has lost the service associated the specified WCCP client |
wccp |
"Verify the operation of the specified WCCP client" |
|
WCCP-3-BADACE |
3-Error |
Service [chars][chars][chars] invalid access-list entry seq:[dec] reason:[chars] |
- |
- |
- |
|
WCCP-3-CAP_API_DEF |
3-Error |
Failed to set WCCP platform parameter defaults 0x%X [chars] |
The platform failed to set the WCCP platform parameter defaults. |
wccp |
LOG_STD_ACTION |
|
WCCP-3-CAP_API_GET |
3-Error |
Failed to get WCCP platform parameter [dec] [chars] |
The platform failed to read a WCCP platform parameter. |
wccp |
LOG_STD_ACTION |
|
WCCP-3-CAP_API_INI |
3-Error |
Failed to initialize WCCP platform parameter [dec] |
Initialization of a WCCP platform parameter failed. |
wccp |
LOG_STD_ACTION |
|
WCCP-3-CAP_API_SET |
3-Error |
Failed to set WCCP platform parameter [dec] to [dec] [chars] |
The platform failed to modify a WCCP platform parameter. |
wccp |
LOG_STD_ACTION |
|
WCCP-3-MASKACLMERGE |
3-Error |
Mask/ACL merge failed for the service [chars] VRF [chars] service Id [dec] |
An internal error indicating that the Mask/ACL merge has failed |
wccp |
LOG_STD_ACTION |
|
WCCP-3-SBADDFAIL |
3-Error |
Unable to add [chars] WCCP subblock on interface [chars] |
An internal error indicating that the WCCP process was unable to attach interface specific service information |
wccp |
"Ensure that there is enough memory available for all processes" |
|
WCCP-3-SBCREATEFAIL |
3-Error |
Unable to allocate [chars] WCCP subblock on interface [chars] |
An internal error indicating that the WCCP process was unable to allocate memory to hold interface specific service information |
wccp |
"Ensure that there is enough memory available for all processes" |
|
WCCP-3-SBINIT |
3-Error |
Error initializing [chars] WCCP subblock data structure. [chars] |
Initialization of the specified subblock data structure could not be accomplished. |
wccp |
LOG_STD_ACTION |
|
WCCP-3-SIFIGNORED |
3-Error |
source-interface [chars] ignored [chars] |
The configured source interface has been ignored whilst determining the WCCP router ID. |
wccp |
"Use the indicated reason message to determine why WCCP refused to use " "the configured interface as its router ID." |
|
WCCP-5-SERVICEFOUND |
5-Notice |
Service [chars][chars][chars] acquired on WCCP client [chars] |
WCCP has acquired a service on the specified WCCP client |
wccp |
LOG_STD_NO_ACTION |
|
WCCP-5-SERVICEMISMATCH |
5-Notice |
Service [chars][chars][chars] mismatched on WCCP client [chars] |
WCCP has rejected a mismatched service on the specified WCCP client |
wccp |
"Amend the WCCP service definition" |
|
WCM_WRP_IPC-3-SESSION_RCV_FAIL |
3-Error |
WCM RF proxy IPC session receive [chars] fails reason [chars] |
IPC session receive end encounters failure |
polaris-infra |
LOG_STD_ACTION |
|
WCM_WRP_IPC-3-SESSION_REG_FAIL |
3-Error |
WCM RF proxy IPC session registration fails with erro code 0x[hec] |
IPC session registration failure |
polaris-infra |
LOG_STD_ACTION |
|
WCM_WRP_IPC-3-SESSION_SEND_FAIL |
3-Error |
WCM RF proxy IPC session send [chars] fails - error code ox[hec] |
IPC session transmit side encounters failure |
polaris-infra |
LOG_STD_ACTION |
|
WCM_WRP_IPC-3-TDL_INIT_FAIL |
3-Error |
WCM RF proxy TDL Library initialization failed.rc=[dec] |
TDL library initialization failure |
polaris-infra |
LOG_STD_ACTION |
|
WCM_WRP_IPC-6-RF_RELAY_INFO |
6-Information |
WCM RF proxy relay RF information: type 0x[hec] value 0x[hec] |
Display the content that WCM RF proxy relays to WCM |
polaris-infra |
LOG_STD_ACTION |
|
WCM_WRP_IPC-6-SESSION_STATUS |
6-Information |
WCM RF proxy IPC session status: [chars] |
Display the WCM RF proxy IPC session status information |
polaris-infra |
LOG_STD_ACTION |
|
WCM_WRP-3-INVALID_CLIENT_ID |
3-Error |
WCM RF proxy received RF [chars] callback with wrong client ID [dec] |
IOS RF infrastructure callback client ID argument is invalid |
polaris-infra |
LOG_STD_ACTION |
|
WCM_WRP-3-RF_ADD_CLIENT_FAIL |
3-Error |
WCM RF proxy RF client add fails return code=[dec] |
IOS RF infrastructure add as RF client fails |
polaris-infra |
LOG_STD_ACTION |
|
WLCLIENT_IPSG_PROXY-2-PROXY_IPC_INIT_FAILED |
2-Critical |
QFP WLCLIENT IPSG Proxy IPC interface initialization failure result: [dec]. |
Cisco internal software error. QFP WLCLIENT IPSG Proxy initialization detected that the IPC interface initialization failed. QFP WLCLIENT IPSG proxy will not be functional while this condition exists. |
qfp-swport keyword:swport |
LOG_STD_ACTION |
|
WLCLIENT_IPSG_PROXY-3-PROXY_BAD_MSG |
3-Error |
QFP WLCLIENT IPSG Proxy received bad length message type [dec] |
Cisco internal software error. QFP WLCLIENT IPSG Proxy received a corrupted message from control plane. This message will be ignored. |
qfp-swport keyword:swport |
LOG_STD_ACTION |
|
WLCLIENT_IPSG_PROXY-3-PROXY_IPC_ALLOC_FAILED |
3-Error |
QFP WLCLIENT IPSG Proxy [chars] message lost due to message buffer allocation failure. |
Cisco internal software error. QFP WLCLIENT IPSG Proxy message processing detected a message buffer allocation failure. The message is lost as the result of this condition. |
qfp-swport keyword:swport |
LOG_STD_ACTION |
|
WLCLIENT_IPSG_PROXY-3-PROXY_IPC_SEND_FAILED |
3-Error |
QFP WLCLIENT IPSG Proxy [chars] message lost due to message sent failure result: [dec]. |
Cisco internal software error. QFP WLCLIENT IPSG Proxy message processing detected a message sent failure. The message is lost as the result of this condition. |
qfp-swport keyword:swport |
LOG_STD_ACTION |
|
WLCLIENT_IPSG_PROXY-3-WLS_IPSG_MEM_EXTEND_FAILED |
3-Error |
WLCLIENT IPSG IPC subtype: [dec] |
Extending memory failed. |
qfp-swport keyword:swport |
LOG_STD_ACTION |
|
WLCLIENT_IPSG_PROXY-3-WLS_IPSG_MEM_REQ_FAILED |
3-Error |
WLCLIENT IPSG IPC subtype: [dec] |
Requesting more memory failed. |
qfp-swport keyword:swport |
LOG_STD_ACTION |
|
WLCLIENT_IPSG_PROXY-4-PROXY_INVALID_MSG |
4-Warning |
QFP WLCLIENT IPSG Proxy received invalid message type [dec] |
Cisco internal software error. QFP WLCLIENT IPSG Proxy received an invalid message from control plane. This message will be ignored. |
qfp-swport keyword:swport |
LOG_STD_ACTION |
|
WLCLIENT_IPSG_PROXY-4-PROXY_INVALID_MSG_LEN |
4-Warning |
QFP WLCLIENT IPSG Proxy IPC invalid length [dec]:[dec] len [dec] flags 0x[hec] source [dec] |
Cisco internal software error. QFP WLCLIENT IPSG Proxy received invalid IPC message length from control plane. This message will be ignored. |
qfp-swport keyword:swport |
LOG_STD_ACTION |
|
WLS_FQDN_PROXY-3-PROXY_IPC_INIT_FAILED |
3-Error |
[dec] |
IPC handler initialization failed. |
cpp-ucode |
LOG_STD_ACTION |
|
WLS_FQDN_PROXY-4-PROXY_IPC_INVALID_MSG |
4-Warning |
[hec] |
Received an invalid IPC messages subtype. |
cpp-ucode |
LOG_STD_ACTION |
|
WPM-3-WDB_ADD_FB |
3-Error |
Target of type [dec] failed to be created in WDB |
Target can not be created in WDB |
- |
LOG_STD_ACTION |
|
WPM-3-WPM_NODE_CREATE |
3-Error |
Create WPM FB node for Target type [dec] failed in WDB |
Can not create WPM FB Node in WDB |
- |
LOG_STD_ACTION |
|
WPM-3-WPM_RECONCILE_ABORT |
3-Error |
QoS HA reconcilation aborted due to timer event |
QoS HA reconcilation aborted due to timer event |
- |
LOG_STD_ACTION |
|
WSMA-3-DHCP_OP43_PROCESS_FAILED |
3-Error |
PROCESSING FAILED |
The processing of WSMA DHCP Option 43 message failed. |
- |
"Need to verify the WSMA DHCP option 43 message is in correct format.\n\ If not correct it and send this message again." |
|
WSMA-5-DHCP_OP43_PROCESS_DONE |
5-Notice |
PROCESSING DONE |
The processing of WSMA DHCP Option 43 message succeeded. |
- |
"None." |
|
WSMAN-3-INVALID_TRUSTPOINT |
3-Error |
\ Trustpoint associated with HTTP is either invalid or does not exist |
This message indicates that Trustpoint attached to the HTTP is not valid or it does not exist. Ideally there is a need to create Trustpoint first and then attach to the HTTP process. Incase Trustpoint is created later then there is a need to restart HTTPS server |
ng-web-infra |
"Configure a valid trustpoint and attach it to HTTP" |
|
X25-2-ILLP4 |
2-Critical |
Interface [chars] Illegal state [chars] when P4 |
An internal software error occurred. |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
X25-3-ADDRESSBAD |
3-Error |
Interface [chars] x25 address [chars] subaddress [chars] is too long |
This message occurs when a subaddress is configured. When this\n\ subaddress is combined with the interface's X.121 address the total\n\ address exceeds the limit of 15 characters. |
- |
"Reconfigure the subaddress so that this does not happen." |
|
X25-3-BADCONFIG |
3-Error |
Interface [chars] X.25 [chars] current config. retained |
- |
- |
- |
|
X25-3-BADCONFIGATTEMPT |
3-Error |
Attempt to [chars]. |
The user attempted an illegal configuration. |
- |
"The error will indicate what illegal action was attempted.\n\ The user should check their configuration and if necesarry\n\ contact technical support representative for assistance." |
|
X25-3-COMPERR |
3-Error |
Interface [chars] LCI [dec] low-level stac compression error |
A Stacker compression algorithm internal error or shortage of buffer\n\ space was encountered during a compression operation. This should never\n\ happen. |
- |
"Report the error to your technical support representative." |
|
X25-3-ERR_SUBST_XOT_DNS_DEST |
3-Error |
Error substituting regular expression for XOT DNS destination pattern |
This message occurs when the regular expression substitute utility fails to arrive at X.25 hostname pattern to be sent to DNS for address resolution |
- |
"Correct the X.25 route command's DNS substitution pattern" |
|
X25-3-INTIMEQ |
3-Error |
Interface [chars] LCN [dec] already in timer queue new time %#Ta |
An internal software error occurred. |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
X25-3-INVCFGID |
3-Error |
[dec] is not a valid X.25 configuration ID |
This message occurs when an invalid configuration id is used |
- |
LOG_STD_ACTION |
|
X25-3-NOLCI |
3-Error |
Interface [chars] Delete: lci [dec] not found in [chars] table |
An internal software error occurred. |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
X25-3-NOTFINDBH |
3-Error |
Can't find bfe host address [inet] to delete |
An internal software error occurred. |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
X25-3-PROFILENO |
3-Error |
profile [chars] does not exist |
This message occurs when an X.25 interface is configured to use\n\ an X.25 profile that does not exist |
- |
"Create and configure the x25 profile using x25 profile <name>\n\ global subcommand before referencing the profile." |
|
X25-3-PVCBAD |
3-Error |
Interface [chars] PVC [dec] [chars] |
A switched PVC cannot be connected. The final [chars] text string in\n\ the message represents the state of the PVC. These text strings can\n\ also appear in show x25-vc output. For more information refer to the\n\ show x25-vc documentation in the Router Products Command Reference\n\ publication. |
- |
"Validate the configuration of the PVCs at both ends of the connection\n\ and reconfigure them if necessary." |
|
X25-3-SIZEBAD |
3-Error |
Interface [chars] LCI [dec] Decompression size error |
An internal software error occurred. The PBP header has an\n\ uncompressed packet size field. Each uncompressed packet size is\n\ checked against this field. |
- |
"Contact your technical support representative for assistance." |
|
X25-3-SYNCBAD |
3-Error |
Interface [chars] LCI [dec] Decompression sync error. expected [dec] got [dec] |
An internal software error occurred. The PBP header has a sync field.\n\ The sync field 8 bits is checked on each received packet. |
- |
"Contact your technical support representative for assistance." |
|
X25-3-TRUNCATE_ALT_XOT_DNS_DEST |
3-Error |
Truncating excess XOT addresses [dec] returned by DNS |
- |
- |
- |
|
X25-3-UNKNOWNPROT |
3-Error |
[chars] : Unable to identify lower layer protocol |
IDB is not using X25 and IDB is not capable of supporting CMNS. |
- |
"Check your hardware configuration or contact your technical support\n\ representative for assistance." |
|
X25-3-VERSIONBAD |
3-Error |
Interface [chars] LCI [dec] Compression Version mismatch expected [hec] received [hec] |
An internal software error occurred. The PBP header has a mismatched\n\ version field. The version is checked on each received packet. |
- |
"Copy the message exactly as it appears and report it your technical\n\ support representative." |
|
X25-3-X25DEENCINV |
3-Error |
[chars] |
This message occurs when deconfiguring X.25 service. |
- |
LOG_STD__ACTION |
|
X25-3-X25ENCINV |
3-Error |
[chars] |
This message occurs when configuring an X.25 service. |
- |
LOG_STD_ACTION |
|
X25-3-X25INT |
3-Error |
Interface [chars] X.25 internal error [chars] |
This is a general message covering numerous internal X25\n\ error conditions. The message text contains additional\n\ details that can be used to identify the problem. |
- |
LOG_STD_RECUR_ACTION |
|
X25-3-X25NOCFG |
3-Error |
Profile is not configured |
This message occurs when an X.25 interface is configued to use\n\ an X.25 profile that isn't configured |
- |
"Configure the x25 profile using x25 profile <name>\n\ global subcommand before referencing the profile." |
|
X25-3-X25NOTAVAIL |
3-Error |
[chars] : Lower layer protocol is not available |
The required lower layer service is unavailable. |
- |
"Check your configuration or contact your technical support\n\ representative for assistance." |
|
X25-3-XOTINT |
3-Error |
XOT internal error [chars] |
This is a general message covering numerous internal error\n\ conditions related to XOT. The message text contains additional\n\ details that can be used to identify the problem. |
- |
- |
|
X25-3-XOTPROTOCOL |
3-Error |
XOT protocol error from [inet]: [chars] |
- |
- |
"If this message recurs call your technical support representative for\n\ assistance." |
|
X25-4-BADMBIT |
4-Warning |
Interface [chars] VC [dec] partial data packet has M-bit set |
This message occurs when a virtual circuit is set up using the default\n\ maximum packet sizes but the DTE and DCE are not configured with the\n\ same default values. A packet was received that had the M-bit set\n\ signifying that more data follows but the packet did not carry the\n\ maximum number of bytes allowed. Such partial data packets must have\n\ the M-bit cleared. The resulting loss of a message boundary might cause\n\ problems for the data recipient. |
- |
"Verify the default flow control parameters of the DTE and the DCE. If\n\ this message recurs call your technical support representative for\n\ assistance." |
|
X25-4-BADUPCALL |
4-Warning |
Interface [chars] Unexpected call [chars] from LLC2 |
An internal software error occurred. |
- |
"If any of these messages recur call your technical support\n\ representative for assistance." |
|
X25-4-BFEIP |
4-Warning |
Warning: IP address is missing or incompatible with BFE mode |
An interface configured for X.25 BFE mode does not have an\n\ IP address configured or the IP address does not conform to \n\ BFE requirements so cannot be mapped to an X.121 address. |
- |
"Please configure a valid Class A IP address for the interface \n\ or remove the 'bfe' option from the 'encapsulation x25' command \n\ for the interface." |
|
X25-4-DEBUG_LCI |
4-Warning |
LCI deleted at interrupt time |
The interface's default packet sizes or outgoing packet size facility\n\ values are too large to be carried by Link Access Procedure Balanced\n\ LAPB. |
- |
[chars] packet sizes [dec]/[dec] too large |
|
X25-4-PARTIALMAP |
4-Warning |
Interface [chars] [chars] encapsulation call from [chars] partially mapped to [chars] |
- |
- |
"Modify the configuration of the router or the far host to match the\n\ encapsulation method used." |
|
X25-4-VCLOSTSYNC |
4-Warning |
Interface [chars] VC [dec] TCP connection [chars] |
An X.25 circuit that is being tunneled over a TCP connection between\n\ routers was cleared ungracefully. The last [chars] text string in the\n\ message can take one of two forms. If the text string is \closed\n\ unexpectedly |
- |
- |
|
X25-4-XOTPVCDUPLICATE |
4-Warning |
Duplicated remote PVC data for {[chars] pvc [dec]} and {[chars] pvc [dec]} |
This message identifies two local XOT PVCs that are defined using\n\ duplicate specifications for the connecting remote XOT PVC. |
- |
- |
|
X25-5-CALL_RECORD |
5-Notice |
[chars] |
This message contains X.25 call record information. |
x25 |
LOG_STD_NO_ACTION |
|
X25-5-NOBUF |
5-Notice |
Interface [chars] LCI [dec] [chars] |
- |
- |
"If this message occurs frequently you may need to modify the buffer\n\ pool. Copy the message exactly as it appears and report it your\n\ technical support representative." |
|
X25-5-PBPDBIT |
5-Notice |
Interface [chars] LCI [dec] PBP Compression does not support X25 D bit |
Compression is not enabled because D-bit support is configured for the\n\ LCI. |
- |
"Reconfigure without D-bit support or do not attempt to run with\n\ compression." |
|
X25-5-PBPHOLDQ |
5-Notice |
Interface [chars] LCI [dec] X25 Hold queue needs to be at least default size |
An attempt was made to configure the X.25 hold queue to less than the\n\ minimum value. |
- |
"Configure the X.25 hold queue to be ten or more." |
|
X25-5-PBPNOEND |
5-Notice |
Interface [chars] LCI [dec] End system not configured for X25 PBP |
A compression or decompression operation was attempted by a router\n\ other than an end router. Only end routers can perform compression and\n\ decompression. |
- |
"Reconfigure the routers so that only the end routers in the network\n\ perform compression and decompression." |
|
X25-5-UPDOWN |
5-Notice |
Interface [chars] - DLCI [dec] X.25 packet layer state changed to [chars] |
The state of the X.25 context associated with the DLCI changed |
fr |
"Notification message only. No action required" |
|
X25-7-DIAGEVENT |
7-Debug |
Interface [chars] X.25 diagnostic event [chars] lci [dec][chars] |
- |
- |
- |
|
X25-7-DIAGRX |
7-Debug |
Interface [chars] X.25 Diagnostic received [chars][chars] |
- |
- |
- |
|
X40G_LOWQ-5-MAX_QUEUE_LIMIT_EXCEEDED |
5-Notice |
Number of queues [dec] for the Low queue sub-block exceeded the |
More queues cannot be created on the interface since the number of low queues created in the system exceeds the maximum allowed limit of 16. |
c7600-es-platform |
"This is just a informational message and the configuration should fail " "to apply on the interface. Please check the output of show platform lowq" "for more information" |
|
X40G-2-TCAM_MGR_CRIT_ERR |
2-Critical |
GTM ERROR: [chars] [dec] |
X40G TCAM critical error |
c7600-es-platform |
LOG_STD_SH_TECH_ACTION |
|
X40G-3-TCAM_MGR_ERR |
3-Error |
GTM ERROR: [chars] [dec] |
X40G TCAM MGR interaction error |
c7600-es-platform |
LOG_STD_SH_TECH_ACTION |
|
X40G-3-TCAM_MGR_HW_ERR |
3-Error |
GTM HW ERROR: [chars] [dec] [[dec]:%05x] |
X40G TCAM hardware error |
c7600-es-platform |
LOG_STD_SH_TECH_ACTION |
|
X40G-3-TCAM_MGR_HW_PERR |
3-Error |
GTM HW ERROR: [chars] [dec] |
X40G TCAM interface parity error |
c7600-es-platform |
LOG_STD_SH_TECH_ACTION |
|
X40G-4-TCAM_MGR_ALLOC_ERR |
4-Warning |
[chars] NP [dec] Region Id [dec] |
NP TCAM entry allocation failure |
c7600-es-platform |
"remote command module " "<module#> sh platform software xtcammgr instance <NP#> info" |
|
X40G-5-TCAM_MGR_INFO |
5-Notice |
[chars] |
X40G TCAM driver error |
c7600-es-platform |
LOG_STD_SH_TECH_ACTION |
|
XCCTSP_VOICE-3-ADDINTRFFAIL |
3-Error |
The Voice Telephony Service Provider has rejected our\n\ request to add this voice interface [dec]/[dec]:[dec] |
The voice software was unable to report a new signaling\n\ interface to the Voice Telephony Service Provider |
xcc |
LOG_STD_SH_TECH_ACTION |
|
XCCTSP_VOICE-3-MALLOC |
3-Error |
No memory is available to build any internal data \n\ structure for the voice software. |
The voice software was unable allocate memory to build \n\ any internal data structures. The system may be \n\ out of memory. |
xcc |
LOG_STD_SH_TECH_ACTION |
|
XCCTSP_VOICE-3-NOMEM |
3-Error |
No memory is available to build the voice interface [dec]:[dec] |
The voice software was unable allocate memory to build \n\ a voice interface data structure. The system may be \n\ out of memory. |
xcc |
LOG_STD_SH_TECH_ACTION |
|
XCCTSP_VOICE-3-NOSDB |
3-Error |
No signaling data block is available to build the\n\ voice interface[dec]/[dec]:[dec] or DSP may not be present |
The voice software was unable to obtain a signaling data\n\ block from the Voice Telephony Service Provider. \n\ The system may be out of memory. |
xcc |
LOG_STD_SH_TECH_ACTION |
|
XCCTSP_VOICE-3-NOTDMCHNL |
3-Error |
XCCTSP failed to get a free dsp tdm channel from the DSP\n\ Resource Manager DSPRM to handle an incoming call |
The voice software was unable to obtain the tdm channel \n\ for a free dsp from the DSP Resource Manager. All of \n\ the dsp's have been used to process calls or have\n\ been taken out of service. |
xcc |
LOG_STD_SH_TECH_ACTION |
|
XCCTSP_VOICE-3-NOVOICEVDEV |
3-Error |
Cannot find the voice data block which matches\n\ an asynchronous response for a call. |
Internal software fault. Contact your field service representative \n\ if this message is coincident with dropped calls. |
xcc |
LOG_STD_SH_TECH_ACTION |
|
XCCTSP_VOICE-3-OUTOFRANGE_CTRL |
3-Error |
Going out of range for controller number for the slot\n\ subslot [dec] ctrl_num [dec] |
Internal software fault. Contact your field service representative |
xcc |
LOG_STD_SH_TECH_ACTION |
|
XCCTSP_VOICE-3-UNDEFDSX0 |
3-Error |
Undefined dsx0 interface for controller[dec] |
The dsx0 interface for the specified controller\n\ is not defined but the voice software use it. |
xcc |
"Internal software fault. Contact your field service representative \n\ if this message is coincident with dropped calls." |
|
XCCTSP_VOICE-3-UNDEFVOICEINTRF |
3-Error |
Invalid voice interface slot/controller:group[dec]/[dec]:[dec] |
The voice interface defined by controller:group is not\n\ yet defined within the voice software but attempts were\n\ made to use this interface. |
xcc |
"Internal software fault. Contact your field service \n\ representative if this message is coincident with \n\ dropped calls." |
|
XCONNECT-3-CONFIG |
3-Error |
[chars] |
An invalid xconnect configuration or an error in processing xconnect configuration has occurred. |
xconnect |
LOG_STD_NO_ACTION |
|
XCONNECT-3-ILLEGAL |
3-Error |
[chars] |
An illegal event has been processed by the xconnect subsystem. |
xconnect |
LOG_STD_NO_ACTION |
|
XCONNECT-4-VC_TYPE_INCOMPATIBLE |
4-Warning |
The 'vc type' command on pseudowire [chars]:[dec] is incompatible with xconnect [chars] ignored |
The 'vc type' command is only intended to be used with VPLS. Use the 'interworking' command on xconnects in order to specify the type of VC for VPWS. |
xconnect |
"Unconfigure the 'vc type' command from the " "pseudowire interface or template and configure" "'interworking' on the xconnect." |
|
XCONNECT-5-PW_STATUS |
5-Notice |
[chars] |
An event has occurred that has caused the pseudowire to change status |
xconnect |
LOG_STD_NO_ACTION |
|
XCONNECT-5-PW_STATUS_LOST |
5-Notice |
[chars] |
The system is dropping PW_STATUS messages because the status queue is full |
xconnect |
LOG_STD_NO_ACTION |
|
XCONNECT-5-REDUNDANCY |
5-Notice |
[chars] |
An event has occurred that has caused the xconnect redundancy facility to generate a switchover event to the specified backup member |
xconnect |
LOG_STD_NO_ACTION |
|
XCVR-3-UNKNOWN_SFP_INSERTED |
3-Error |
Unknown SFP inserted [chars] |
Unknown SFP inserted |
- |
LOG_STD_ACTION |
|
XDM_CREATE-3-ATOM_TRANS |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
XDM_CREATE-3-VFI |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
XDM_CREATE-3-XCONNECT |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
XDR_COMM-3-MPLSOAM |
3-Error |
ERRMSG_FLAG_TRACEBACK |
- |
- |
- |
|
XDR-2- XDRDISABLEREQUEST |
2-Critical |
Peer in slot [chars] requested to be disabled due to: [chars]. Disabling linecard |
Due to some error condition the linecard has requested to be disabled |
XDR_DDTS_COMPONENT |
"Execute \"clear xdr linecard\" from the RP followed by " "\"clear xdr channel\" on the linecard in question to clear the " "error condition. If the problem persists get the output of " "\"show monitor event-trace xdr all\" from the RP and the linecard in " "question and report it to your technical support representative." |
|
XDR-2- XDRLCDISABLEREQUEST |
2-Critical |
Client [chars] requested to be disabled. [chars] |
Due to some error condition the linecard has requested to be disabled |
XDR_DDTS_COMPONENT |
"Execute \"clear xdr linecard\" from the RP followed by " "\"clear xdr channel\" on the linecard in question to clear the " "error condition. If the problem persists get the output of " "\"show monitor event-trace xdr all\" from the RP and the linecard in " "question and report it to your technical support representative." |
|
XDR-3- BADSEQVAL |
3-Error |
Incorrect maximum sequence calculated [dec] was [dec] for slot [chars] |
Internal software error. May result in unpredictable behaviour. |
XDR_DDTS_COMPONENT |
"show xdr linecard" |
|
XDR-3- BYPASSFOFNEGO |
3-Error |
Bypassing FOF ISSU client [chars] [dec] nego for XDR client [chars] slot [chars] |
This XDR client has a dependency on another ISSU client due to having foreign-owned-fields. As the ISSU client that owns the foreign-owned fields is not in the image the XDR client will not wait for that client to finish ISSU negotiation. Appearance of this error message indicates that work is required to add the missing client to the image. |
XDR_DDTS_COMPONENT |
"Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-3- CLIENTISSU_FOF_NEGOFAIL |
3-Error |
ISSU negotiation failed for FOF client [dec] for peer [chars] ISSU peer [dec] |
ISSU negotiation failed for a client which has registered ISSU FOF client dependencies. The dependent clients on this and the remote slot cannot interoperate in SSO mode. Syncing of information to/from this slot will not happen for this and the dependent clients. See output of \show xdr multicast\ for full details. |
XDR_DDTS_COMPONENT |
"Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-3- CLIENTISSU_FOF_REGERROR |
3-Error |
ISSU client [chars] [dec] entity [dec] message [dec] [chars] |
This ISSU client has a message containing a foreign field owned by another client and failed to register this dependency. |
XDR_DDTS_COMPONENT |
"This error indicates a potential coding problem. It is an error that " "may occur every time this image is run and may require a code change " "to fix it." |
|
XDR-3- CLIENTISSU_NEGOFAIL |
3-Error |
ISSU negotiation failed for XDR client [chars] slot [chars] reason: [chars] |
ISSU negotiation failed. This XDR client on this and the remote slot cannot interoperate in SSO mode. Syncing of information to/from this slot will not happen for this and dependent clients. See output of show xdr multicast for full details. |
XDR_DDTS_COMPONENT |
"Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-3- CLIENTISSU_NEGOREGERROR |
3-Error |
XDR client [chars] failed ISSU negotiation result notification registration for ISSU client [chars] [dec] reason: [chars] |
This client has dependency on the succesful ISSU negotiation of another client and failed to register this dependency |
XDR_DDTS_COMPONENT |
"This error indicates a potential coding problem. It is an error that " "may occur every time this image is run and may require a code change " "to fix it." |
|
XDR-3- CLIENTISSU_NEGOUNREGERROR |
3-Error |
Failed to unregister ISSU negotiation result notification registration for ISSU client [chars] [dec] reason: [chars] |
This client has dependency on the succesful ISSU negotiation of another client and failed to unregister this dependency when not required. |
XDR_DDTS_COMPONENT |
"This error indicates a potential coding problem. It is an error that " "may occur every time this image is run and may require a code change " "to fix it." |
|
XDR-3- CLIENTISSU_PUSHFAIL |
3-Error |
Attempting to push send XDR message [chars] to slots [chars] via XDR client |
Internal error. May result in unpredictable behaviour. |
XDR_DDTS_COMPONENT |
"Get the output of \"show xdr multicast\" \"show xdr client all\" and " "\"show issu message types [XDR client ISSU ID]\". " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-3- CLIENTISSU_REGERROR |
3-Error |
ISSU client [chars] [dec] entity [dec] failed ISSU registration: [chars] |
ISSU negotiation failed for this XDR client. |
XDR_DDTS_COMPONENT |
"This error indicates a coding problem. It is an error that will occur" "every time this image is run and requires a code change to fix it." |
|
XDR-3- CLIENTISSUBADGROUP |
3-Error |
New m/cast group slots [chars] has multiple members before nego complete. |
- |
- |
- |
|
XDR-3- CLIENTISSUBADNEGOMSG |
3-Error |
Unexpected nego msg - slot [chars] XDR client [chars] ctxt [dec] |
XDR has received a negotiation message unexpectedly as this client is either not ISSU aware or has already completed negotiation for this slot. This is likely a precursor to unpredictable behaviour for this client. |
XDR_DDTS_COMPONENT |
"Get the output of \"show xdr multicast\" \"show xdr client all\" and " "\"show issu message types [XDR client ISSU ID]\". " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-3- CLIENTISSUNEGATIVEPADDING |
3-Error |
Negative padding for [chars] slots [chars] msg [dec] padded: [dec] unpadded: [dec] |
- |
- |
- |
|
XDR-3- CLIENTISSUNEGONOTDONE |
3-Error |
Attempting to push send XDR message [dec] to slots [chars] for [chars] before nego |
Internal error. May result in unpredictable behaviour. |
XDR_DDTS_COMPONENT |
"Get the output of \"show xdr multicast\" \"show xdr client all\" and " "\"show issu message types [XDR client ISSU ID]\". " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-3-CLIENTISSUNOMSGGRP |
3-Error |
Cannot determine ISSU message group for slot [dec]. Unknown [chars] |
Not able to determine the set of ISSU messages to be used between local and remote slot due to not being able to determine linecard type for one or other slot. This might be due to a new linecard type. |
XDR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
XDR-3- CLIENTISSUSENDFAILED |
3-Error |
Can't send XDR client ISSU nego msg: reason [chars] slot [chars] XDR client [chars] |
XDR has failed to send an ISSU negotiation message for the given client. The slot will be marked as ISSU-unaware and communication with this slot will proceed on that basis. However this is likley to lead to unpredictable behaviour. |
XDR_DDTS_COMPONENT |
"Get the output of \"show xdr multicast\" \"show xdr client all\" and " "\"show issu message types [XDR client ISSU ID]\". " "Also copy the message exactly as it appears and report it to your " "technical support representative." |
|
XDR-3- CLIENTISSUSTARTNEGOFAIL |
3-Error |
Can't start nego: reason [chars] slot [chars] XDR client [chars] sid [dec] |
XDR has failed to start ISSU negotiation with the remote slot for the reason given. The slot will be marked as ISSU-unaware and communication with this slot will proceed on that basis. However this is likley to lead to unpredictable behaviour. |
XDR_DDTS_COMPONENT |
"Get the output of \"show xdr multicast\" \"show xdr client all\" and " "\"show issu message types [XDR client ISSU ID]\". " "Also copy the message exactly as it appears and report it to your " "technical support representative." |
|
XDR-3- DATA_TOO_LARGE |
3-Error |
Data length [dec] exceeds limit of [dec] bytes |
An attempt was made by a client to send XDR data that was over the given length limit which caused the send to fail. |
XDR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
XDR-3- FRAG_CLIENT_NOT_ALLOWED |
3-Error |
Received an XDR fragment from client [chars] slot [chars] which is not allowed to send fragments |
Certain clients are restricted by XDR from fragmenting their data yet such a fragment was received received. |
XDR_DDTS_COMPONENT |
LOG_STD_ACTION |
|
XDR-3- ILLEGAL_CAP_TYPE |
3-Error |
Illegal ISSU capability type [dec] for XDR client [chars] |
Capability type requested is invalid. The named XDR client may not function as expected. |
XDR_DDTS_COMPONENT |
"Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-3- ILLEGAL_CAP_VALUE_CHANGE |
3-Error |
ISSU capabilities for peers running same IOS version must be supported. |
Basic assumption is that all peers running the same IOS version as the active RP will support the same ISSU capabilities as the active RP. This is an attempt to mark one such peer as not supporting all capabilities. This will break assumptions in XDR ISSU code and cannot be allowed. The traceback will indicate the offending XDR client. |
XDR_DDTS_COMPONENT |
"Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-3- ISSU_ENUM_ERROR |
3-Error |
Enum for [chars] [chars] component is not ISSU-compliant: [chars] |
The given enumeration is not ISSU-compliant for the reason given. Unpredictable behaviour will result when interoperating with different IOS versions. |
XDR_DDTS_COMPONENT |
"This requires a code fix before the image can be shipped or ISSU will be " "broken." |
|
XDR-3- ISSU_NEGOFAIL |
3-Error |
ISSU negotiation failed for XDR slot [chars] reason: [chars] |
ISSU negotiation failed. XDR on this and the remote slot cannot interoperate. Syncing of information to/from this slot for all XDR clients will not be allowed. |
XDR_DDTS_COMPONENT |
"Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-3- ISSUBADREGPARAMS |
3-Error |
XDR client [chars] trying to register with incomplete ISSU support. |
This client does not properly support ISSU and will be registered as not supporting ISSU. |
XDR_DDTS_COMPONENT |
"We cannot allow a client to register with partial ISSU support so it will " "be registered without it. Please report this message to your technical " "support representative." |
|
XDR-3- ISSUCAPNEGOFAIL |
3-Error |
XDR client [chars] failed to [chars] capability/ies due to [chars] |
Internal software error - capability negotiation failed unexpectedly. |
XDR_DDTS_COMPONENT |
"Copy the message exactly as it appears and report it to your technical " "support representative" |
|
XDR-3- ISSUINITFAIL |
3-Error |
Unable to register XDR ISSU [chars] reason: [chars] |
Unable to register the given XDR ISSU parameter due to the reason given. This will stop ISSU working for this client and may lead to unpredictable behaviour. |
XDR_DDTS_COMPONENT |
"Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-3- MISMATCHED_ISSU_CAPABILITY_INFO |
3-Error |
[chars]: [chars] |
ISSU-aware XDR clients may have capabilities to negotiate. They can ask XDR to manage the state of these but must provide all relevant supporting functions to do so. In this case the given client has not done so. |
XDR_DDTS_COMPONENT |
"Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-3- MSGSIZEFAIL |
3-Error |
The IPC message size is out of bounds The ipc_msg_size is : [dec] while the maximum size we can handle is the XDR_IPC_BUFFER_SIZE : [dec] . |
The size of the IPC message that was received is out of bounds |
XDR_DDTS_COMPONENT |
"We were not meant to get the IPC message we did. The size of the IPC " "message is larger than the maximum size that can be handled. " "This is probably due to communication incompatibility issues between the " "active and the standby RPs. " "Please report it to your technical support representative." |
|
XDR-3- NONINCRSEQ |
3-Error |
Non-increasing maximum sequence [dec] was [dec] received from slot [chars] |
- |
- |
- |
|
XDR-3-ONINT |
3-Error |
Invalid operation [chars] at interrupt level by XDR client [chars] |
Invalid operation at interrupt level |
XDR_DDTS_COMPONENT |
"Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-3- PRIOCLIENTISSU_NEGOFAIL |
3-Error |
ISSU negotiation failed for XDR client [chars] slot [chars] reason: [chars] |
ISSU negotiation failed for a core XDR client. XDR on this and the remote slot cannot interoperate in SSO mode. Syncing of information to/from this slot will not happen for any XDR client. |
XDR_DDTS_COMPONENT |
"Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-3- PULLSENDFAIL |
3-Error |
Sending data for pull client [chars] to [chars] failed due to slots [chars] not being in group 0x[hec] of slots [chars] |
- |
- |
- |
|
XDR-3- XDRIPC |
3-Error |
XDR IPC error on multicast-group 0x[hec] due to [chars]. |
A general IPC related error occurred which may prevent transfer of data to other peers using the IPC mechanism |
XDR_DDTS_COMPONENT |
"Get the output of \"show xdr multicast\" immediately after this error. " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-3- XDRMCAST_PEER_BINDING |
3-Error |
XDR peer [chars] bind to group [chars] was bound to [chars]: [chars] |
- |
- |
- |
|
XDR-3- XDRMCASTGRPINVALID |
3-Error |
Invalid XDR multicast group for slots [chars]: [chars] |
- |
- |
- |
|
XDR-3- XDRMCASTJOIN |
3-Error |
Attempt to join [chars] to [chars] failed because client [chars] returned an error |
Internal error. May result in unpredictable behaviour. |
XDR_DDTS_COMPONENT |
"Get the output of \"show xdr multicast\" \"show xdr client all\" and " "\"show monitor event-trace xdr all\". " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-3- XDRMCASTJOINREQ |
3-Error |
Client [chars] returned an invalid response to a join request for groups [chars] and [chars] |
Internal error. May result in unpredictable behaviour. |
XDR_DDTS_COMPONENT |
"Get the output of \"show xdr multicast\" \"show xdr client all\" and " "\"show monitor event-trace xdr all\". " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-3- XDRNOMEM |
3-Error |
XDR failed to allocate memory during [chars] creation. |
Allocation of memory by the XDR subsystem failed. This may result in an unpredictable behavior of XDR |
XDR_DDTS_COMPONENT |
"Make sure that there is enough memory for the operations being performed " "by your machine. " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-3- XDROOS |
3-Error |
Received an out of sequence IPC message. Expected [dec] but got [dec] from slot [chars]. |
An out of sequence IPC message was received |
XDR_DDTS_COMPONENT |
"We weren't meant to get the IPC message we did. From this point onwards " "IPC can't be relied on. " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-4-FAILATTEMPTOPENIPCPORT |
4-Warning |
Attempt to open the IPC ports failed. [chars] |
XDR failed an attempt to open the IPC port to communicate to the specified peer |
XDR_DDTS_COMPONENT |
LOG_STD_NO_ACTION |
|
XDR-6- CLIENTISSUBADRCVTFM |
6-Information |
Failed to rcv_transform message - from slot [chars] XDR client [chars] context [dec] |
Cannot perform ISSU receive transform. This is likely due to a failure in negotiation earlier or when one side of an ISSU-enabled XDR connection is out of sync with the other. |
XDR_DDTS_COMPONENT |
"Get the output of \"show xdr multicast\" \"show xdr client all\" and " "\"show issu message types [XDR client ISSU ID]\". " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-6- CLIENTISSUBADTXTFM |
6-Information |
Failed to xmit_transform message - to slot [chars] XDR client [chars] context [dec] |
Cannot perform ISSU transmit transform. This is likely due to a failure in negotiation earlier or when one side of an ISSU-enabled XDR connection is out of sync with the other. |
XDR_DDTS_COMPONENT |
"Get the output of \"show xdr multicast\" \"show xdr client all\" and " "\"show issu message types [XDR client ISSU ID]\". " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-6- CLIENTISSUUNREG |
6-Information |
Failed to unregister session - XDR client [chars] slot [chars] reason [chars] |
Unable to unregister this session. This will likely cause problems when reregistering and should be reported. |
XDR_DDTS_COMPONENT |
"Get the output of \"show xdr multicast\" \"show xdr client all\" and " "\"show issu message types [XDR client ISSU ID]\". " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-6- CLIENTNOTREGONRP |
6-Information |
Client [chars] has registered on slot [chars] before RP. |
XDR client has registered on non-RP card before RP card. If this has occurred while toggling the client's registration status rapidly then it may be a transient problem and will resolve itself. If not then the client's status may be unpredictable and ISSU negotiation if platform is ISSU-aware may not take place correctly. |
XDR_DDTS_COMPONENT |
"Verify whether the client's registration status is the same on both " "the RP and the card on which the problem is reported by comparing " "the output of 'show xdr client all' to see if the client is present or " "absent in BOTH. If so and no other error messages have been seen " "then this is a transient issue and no further action is required. " "Otherwise copy the message exactly as it appears and report it to " "your technical support representative." |
|
XDR-6- ISSUBADRCVTFM |
6-Information |
Failed to rcv_transform message - slot [chars] reason: [chars] |
Unable to perform ISSU transform on incoming XDR header. Message will be ignored |
XDR_DDTS_COMPONENT |
"Get the output of \"show xdr multicast\" \"show xdr client all\" and " "\"show issu message types [XDR client ISSU ID]\". " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-6- ISSUBADTXTFM |
6-Information |
Failed to xmit_transform message - slot [chars] reason [chars] |
Unable to perform ISSU transform on outgoing XDR header. Message will be ignored |
XDR_DDTS_COMPONENT |
"Get the output of \"show xdr multicast\" \"show xdr client all\" and " "\"show issu message types [XDR client ISSU ID]\". " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-6- ISSUCLIENTABSENT |
6-Information |
XDR client [chars] absent on slot [chars]. Client functionality may be affected. |
The remote slot doesn't support this ISSU client. The software will handle this by reducing client functionality locally to continue in SSO mode or by forcing the remote peer into RPR mode as apprporiate. This is expected behaviour in ISSU-capable systems. |
XDR_DDTS_COMPONENT |
"No action required. This message just indicates that certain " "functionality may be reduced due to running different images together." |
|
XDR-6- XDRINVALIDHDR |
6-Information |
XDR for client [chars] dropped slots:[chars] from slot:[chars] context:[dec] length:[dec] |
The XDR message was dropped for the reason given. |
XDR_DDTS_COMPONENT |
"If the failure was due to an invalid context for the CEF push client " "and occurred during an ISSU upgrade then it may be safely ignored. " "Otherwise: " LOG_STD_ACTION |
|
XDR-6- XDRINVALIDHDRISSU |
6-Information |
XDR ISSU negotiation message for client [chars] dropped |
The XDR ISSU negotiation message was dropped for the reason given. |
XDR_DDTS_COMPONENT |
"If the message occurred during an ISSU upgrade then it may be " "safely ignored. Otherwise: " LOG_STD_ACTION |
|
XDR-6- XDRIPCPEER |
6-Information |
XDR IPC error occurred for peer in slot [chars] due to [chars][chars]. |
A general IPC related error occurred which may prevent transfer of data to other peers using the IPC mechanism |
XDR_DDTS_COMPONENT |
"Get the output of \"show xdr multicast\" and \"show xdr linecard\" " "immediately after this error. Copy the message exactly as it appears " "and report it to your technical support representative." |
|
XDR-6- XDRMCASTINIT |
6-Information |
XDR mcast subsystem initilisation error: [chars] |
XDR non functional. |
XDR_DDTS_COMPONENT |
"A failure occured which prohibits the XDR client from registering with " "the core. " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XDR-6- XDRREGISTRATION |
6-Information |
XDR failed to register [chars] client due to [chars] |
Failure to register the said XDR client. |
XDR_DDTS_COMPONENT |
"A failure occured which prohibits the XDR client from registering with " "the core. " "Copy the message exactly as it appears and report it to your technical " "support representative." |
|
XIPC-3-LDP |
3-Error |
ERRMSG_NOFLAGS |
- |
- |
- |
|
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-4-CLIENT_ERR_RSP |
4-Warning |
Received error response [dec] [chars] from client [chars]/[chars] |
- |
- |
- |
|
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 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 |
- |
- |
- |
- |
|
XMPP-3-MEMORY |
3-Error |
[chars] |
XMPP subsystem has experienced a problem gettting the required\n\ memory to complete this operation. |
xmpp |
"Check system memory for other memory allocation errors and contact\n\ Technical support for problem resolution. In the absence of IOS errors\n\ upgrading the memory in the network device may be required." |
|
XOS-7-XOS_DM_DISPATCH |
7-Debug |
xos_dm_dispatch API cannot be called that does not own the XDM xdm pid: [dec] current pid: [dec] |
The xos_dm_dispatch API was called by a process that is not the owner of \n that XDM. Only process that create the XDM instance can own it. |
infra-xoslib |
"Please check your code and avoid invoking this API in a different process \n" "context." |
|
XOS-7-XOS_DM_DISPATCH |
7-Debug |
xos_dm_dispatch API cannot be called that does not own the XDM xdm pid: [dec] current pid: [dec] |
The xos_dm_dispatch API was called by a process that is not the owner of \n that XDM. Only process that create the XDM instance can own it. |
infra-xoslib |
"Please check your code and avoid invoking this API in a different process \n" "context." |
|
XOS-7-XOS_DM_WAIT |
7-Debug |
xos_dm_wait API cannot be called by a process that does not own the XDM xdm pid: [dec] current pid: [dec] |
The xos_dm_wait API was called by a process that is not the owner of that \n XDM. Only process that create the XDM instance can own it. |
infra-xoslib |
"Please check your code and avoid invoking this API in a different process \n" "context." |
|
XOS-7-XOS_DM_WAIT |
7-Debug |
xos_dm_wait API cannot be called by a process that does not own the XDM xdm pid: [dec] current pid: [dec] |
The xos_dm_wait API was called by a process that is not the owner of that \n XDM. Only process that create the XDM instance can own it. |
infra-xoslib |
"Please check your code and avoid invoking this API in a different process \n" "context." |
|
XOS-7-XOS_DM_XDISPATCH |
7-Debug |
xos_dm_xdispatch API cannot be called that does not own the XDM xdm pid: [dec] current pid: [dec] |
The xos_dm_xdispatch API was called by a process that is not the owner of \n that XDM. Only process that create the XDM instance can own it. |
infra-xoslib |
"Please check your code and avoid invoking this API in a different process \n" "context." |
|
XOS-7-XOS_DM_XDISPATCH |
7-Debug |
xos_dm_xdispatch API cannot be called that does not own the XDM xdm pid: [dec] current pid: [dec] |
The xos_dm_xdispatch API was called by a process that is not the owner of \n that XDM. Only process that create the XDM instance can own it. |
infra-xoslib |
"Please check your code and avoid invoking this API in a different process \n" "context." |
|
XOS-7-XOS_ONINT |
7-Debug |
XOS APIs cannot be called in a interrupt path |
An XOS API was called in the interrupt path this is currently not supported. |
infra-xoslib |
"Please check your code and avoid using this API in the interrupt path" |
|
XOS-7-XOS_ONINT |
7-Debug |
XOS APIs cannot be called in a interrupt path |
An XOS API was called in the interrupt path this is currently not supported. |
infra-xoslib |
"Please check your code and avoid using this API in the interrupt path" |
|
XOS-7-XOS_STUCK_TMR |
7-Debug |
XOS timer expired earlier than expected expiration time tree:%p time:[dec].[dec] |
The XOS timer handler was invoked earlier than expiration value of the \n timer |
infra-xoslib |
"Please check expiration timer value set on the timer. Also some OS \n" "infrastructures can roundup expiration time so that timer handler gets \n" "invoked earlier than expected " |
|
XOS-7-XOS_STUCK_TMR |
7-Debug |
XOS timer expired earlier than expected expiration time tree:%p time:[dec].[dec] |
The XOS timer handler was invoked earlier than expiration value of the \n timer |
infra-xoslib |
"Please check expiration timer value set on the timer. Also some OS \n" "infrastructures can roundup expiration time so that timer handler gets \n" "invoked earlier than expected " |
|
XXX-3-SBINIT |
3-Error |
Error initializing [chars] subblock data structure. [chars] |
Initialization of the specified subblock data structure could not be accomplished. |
flexible-netflow |
LOG_STD_ACTION |
|
YANG_INFRA-3-DISABLE_ONEP |
3-Error |
Error disabling onep |
An error has occurred when attempting to disable onep. |
polaris-dmi-infra |
LOG_STD_ACTION |
|
YANG_INFRA-3-ENABLE_ONEP |
3-Error |
Error enabling onep |
An error has occurred when attempting to enable onep. |
polaris-dmi-infra |
LOG_STD_ACTION |
|
ZONE-4-API |
4-Warning |
Zone [chars] [chars][chars] [chars] failed to notify the data plane |
The notification of a zone operation has failed to update the data\n\ plane and as such the application of the zone information within the\n\ object will not be applied to the data plane. It is also possible\n\ that the common classification may fail to locate and bind to the\n\ zone rendering the configuration inconsistent in terms of\n\ application. |
zone |
show memory |
|
ZONE-4-LICENSE |
4-Warning |
License smart enable and zone-license enable should be enabled first |
The notification indicates that zone smart license\n\ should be enabled |
zone |
show running |
|
ZONE-6-CONFIG |
6-Information |
Zone security [chars] is removed due to VRF config change on interface [chars] |
The notification of a zone is removed from an interface\n\ due to a vrf is removed from the interface |
zone |
show running |
|
- |
4-Warning |
fmt \static message_stats * fac ## _ ## name ## _stat_redir_ptr |
- |
- |
- |
|
- |
4-Warning |
fmt |
- |
- |
- |
|
- |
4-Warning |
fmt |
- |
- |
- |
|
- |
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" |
|
- |
5-Notice |
- |
Two devices with random MACs generated the same MAC address. \n\ The second device has been rejected. |
SISF_COMP_NAME |
"The second device will need to regenerate its random MAC." |
|
- |
6-Information |
authentication packet received on sessions with invalid config |
authentication only supported for multihop BFD sessions |
bfd |
LOG_STD_ACTION |
|
- |
6-Information |
packet received failed authentication |
packet authentication failed |
bfd |
LOG_STD_ACTION |
|
- |
6-Information |
Could not allocate valid session handle |
session handle not allocated |
bfd |
LOG_STD_ACTION |
|
- |
4-Warning |
fmt \static message_stats * fac ## _ ## name ## _stat_redir_ptr |
- |
- |
- |
|
- |
4-Warning |
fmt |
- |
- |
- |
|
- |
4-Warning |
fmt |
- |
- |
- |
|
- |
5-Notice |
fmt \static message_stats * fac ## _ ## name ## _stat_redir_ptr |
- |
- |
- |
|
- |
5-Notice |
fmt \extern const struct message_ msg_ ## fac ## _ ## name |
- |
- |
- |
|
- |
3-Error |
fmt \ syslog_ |
- |
- |
- |
|
- |
3-Error |
\ fmt |
- |
- |
- |
|
- |
3-Error |
- |
BULKSTAT Service Enabled |
SRVNAME_BULKSTAT |
SYSLOGDOC_NO_ACTION |
|
- |
3-Error |
- |
BULKSTAT Service Disabled |
SRVNAME_BULKSTAT |
SYSLOGDOC_NO_ACTION |
|
- |
3-Error |
- |
DCM_CORE Service nabled |
SRVNAME_DCM_CORE |
SYSLOGDOC_NO_ACTION |
|
- |
3-Error |
- |
DCM_CORE Service Disabled |
SRVNAME_DCM_CORE |
SYSLOGDOC_NO_ACTION |
|
- |
3-Error |
- |
DCM_CLI_DP Service nabled |
SRVNAME_DCM_CLI_DP |
SYSLOGDOC_NO_ACTION |
|
- |
3-Error |
- |
DCM_CLI_DP Service Disabled |
SRVNAME_DCM_CLI_DP |
SYSLOGDOC_NO_ACTION |
|
- |
3-Error |
- |
DCM_SNMP_DP Service nabled |
SRVNAME_DCM_SNMP_DP |
SYSLOGDOC_NO_ACTION |
|
- |
3-Error |
- |
DCM_SNMP_DP Service Disabled |
SRVNAME_DCM_SNMP_DP |
SYSLOGDOC_NO_ACTION |
|
- |
3-Error |
fmt \local_errmsg_t msg_ ## fac ## _ ## name = { #name |
- |
- |
- |
|
- |
3-Error |
fmt \extern C local_errmsg_t msg_ ## fac ## _ ## name |
- |
- |
- |
|
- |
4-Warning |
fmt \extern const struct message_ msg_ ## fac ## _ ## name |
- |
- |
- |
|
- |
4-Warning |
fmt \static message_stats_ptr fac ## _ ## name ## _stat_redir_ptr __crb_sysrgn |
- |
- |
- |
|
- |
4-Warning |
fmt |
- |
- |
- |
|
- |
4-Warning |
fmt |
- |
- |
- |
|
- |
3-Error |
fmt \static message_stats * fac ## _ ## name ## _stat_redir_ptr |
- |
- |
- |
|
- |
3-Error |
fmt \extern const struct message_ msg_ ## fac ## _ ## name |
- |
- |
- |
Additional References
Technical Assistance
When the recommended action of an error message advises that you contact Cisco technical support, open a case with the Cisco Technical Assistance Center (TAC).
|
Description |
Link |
|---|---|
|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. |
Feedback