-
12.3 T System Message Guide
-
System Message Overview
-
AAA through BSTUN messages
-
C10K through CALL_CONTROL messages
-
CALLRECORD through CPOS messages
-
CRYPTO through DMA messages
-
DNET through ENVM messages
-
ENVMON through FDM_HA messages
-
FECPM through GT96K_TDM messages
-
GTP through HEALTH_MONITOR messages
-
HHM through IPSECV6 messages
-
IPV6 through MICA messages
-
MIPC through NP_VPD messages
-
NRP through PIF messages
-
PIM through PVDM2 messages
-
PXF through RPM_BULK messages
-
RPM_CONN_MGMT through SEC_LOGIN messages
-
SENSOR through SWITCH_IF messages
-
SWITCHOVER through Y88E8K messages
-
Glossary of Acronyms
-
Table Of Contents
SWITCHOVER Messages
The following are line card switchover-related messages.
Error Message%SWITCHOVER-2-LCFAILED : [chars] (slot [dec]): [chars]
Explanation The line card in the specified slot encountered problems during RP failover. This problem is a result of a hardware or software error. If the problem is severe, the line card will be automatically deactivated and restarted.
Recommended Action If the line card fails to restart or if this message is seen multiple times, copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command, with slot-number being the slot number of the affected card. Remove the line card and place it in a different slot. If the line card fails to initialize in the new slot, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SWITCHOVER-3-LCRESET : [chars] Line card reset during RP switchover (slot [dec]) (Line card CPLD Reset Register = [hex]
Explanation The line card in the specified slot was reset during an RP failover operation. If RP redundancy mode is configured as an RPR+ or SSO type, the line card should not be reset when there is an RP switchover. This condition is a result of a hardware or software error. The line card has been automatically deactivated and restarted.
Recommended Action If the line card fails to restart or if this message is seen multiple times, copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command, with slot-number being the slot number of the affected card. Remove the line card and place it in a different slot. If the line card fails to initialize in the new slot, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SWITCHOVER-6-LC_RPRPLUS_UNAWARE : Line card (type [hex]) in slot [dec] is not RPRPLUS mode aware
Explanation The line card in the specified slot does not support the configured RP redundancy mode. This line card will be reset and reinitialized during an RP failover operation.
Recommended Action This is an informational message only. No action is required.
SYS Messages
The following are operating system messages.
Error Message%SYS-3-BADLIST_DESTROY : Removed a non-empty list([hex], name: [chars]), having [int] elements
Explanation 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 a non-empty list got destroyed.
Recommended Action 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 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYS-6-BADSHAREINFO : [chars] packet [hex] has a zero reference count, freeing pid = [hex], freeing pc = [hex] [chars].
Explanation Provides additional information about original freer of packet.
Recommended Action If this messages recurs, copy it exactly as it appears; include the stack trace; and report it to your technical support representative.
Error Message%SYS-6-CLOCKUPDATE : System clock has been updated from [chars] to [chars], configured from [chars] by [chars].
Explanation The system clock has been modified.
Recommended Action No action is required.
Error Message%SYS-1-CPUFALLINGTHRESHOLD : Threshold: [chars] CPU Utilization(Total/Intr) [dec]%/[dec]%.
Explanation CPU usage has returned to normal after crossing a threshold from high usage. Any process that was disabled during the period of high CPU use can now be enabled.
Recommended Action No action is required.
Error Message%SYS-3-CPUHOG : Task is running for ([dec])msecs, more than ([dec])msecs ([dec]/[dec]),process = [chars].[chars]
Explanation The specified process ran for too long without relinquishing the processor. Each process should run for only a small amount of time before relinquishing the processor so that other processes can run. This problem can be caused by many conditions such as traffic, system load, hardware, operational configuration, a configuration change, initialization of many interfaces, a high momentary error rate, or a sustained abnormal condition.
Recommended Action If you suspect a software error, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Recommended Action and report it to your technical support representative.
Error Message%SYS-6-CPURESFALLING : [chars][chars] is no longer seeing [chars] high cpu at [chars] level for the configured [chars] limit [int]%, current value [int]%
Explanation 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.
Recommended Action No action is required.
Error Message%SYS-4-CPURESRISING : [chars][chars] is seeing [chars] cpu util [int]% at [chars] level more than the configured [chars] limit [int] %
Explanation 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.
Recommended Action No action is required .
Error Message%SYS-1-CPURISINGTHRESHOLD : Threshold: [chars] CPU Utilization(Total/Intr): [dec]%/[dec]%, Top 3 processes(Pid/Util): [dec]/[dec]%, [dec]/[dec]%, [dec]/[dec]%
Explanation The system is experiencing high CPU usage, possibly because of a process that is using too much CPU. This condition demands immediate attention, or packets or calls may be dropped.
Recommended Action Enter the show processes CPU command to determine the process that is causing this high CPU (CPU hog) condition and, if possible, disable the activity that is causing the CPU hog condition so that CPU utilization is reduced.
Error Message%SYS-3-CRITMEM : [chars]
Explanation 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.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SYS-7-ESMSHUTDOWN : ESM shutdown
Explanation The embedded syslog manager has shut down.
Recommended Action No action is required.
Error Message%SYS-4-FREEMEMLOW : Free Memory has dropped below low watermark
Pool: [chars] Free: [int] freemem_lwm: [int]\nExplanation 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.
Recommended Action No action is required.
Error Message%SYS-5-FREEMEMRECOVER : Free Memory has recovered above low watermark
Pool: [chars] Free: [int] freemem_lwm: [int]\nExplanation 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.
Recommended Action No action is required.
Error Message%SYS-3-GD_STACKERR : Unknown stack. Process: [chars]\n
Explanation An internal error occurred while the garbage detector was being run.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SYS-4-GLOBALBUFEXCEED : Buffer usage has gone above global buffer [chars] threshold configured [dec] Current usage :[dec]
Explanation Global buffer usage has gone above the configured limit. This violation can happen because of all the entities in the system that use buffers.
Recommended Action No action is required.
Error Message%SYS-5-GLOBALBUFRECOVER : Buffer usage has gone below global buffer [chars] threshold configured [dec] Current usage :[dec]
Explanation global buffer usage has gone below the configured limit. This is the indication of recovery
Recommended Action No action is required
Error Message%SYS-5-GLOBALMEMEXCEED : Global Memory has exceeded the [chars] threshold Pool: [chars] Used: [int] Threshold: [int]
Explanation The memory pool specified in the error message has exceeded the configured global memory threshold. The memory consumed in that pool has exceeded the configured limit.
Recommended Action No action is required
Error Message%SYS-5-GLOBALMEMRECOVER : Global Memory has recovered after exceeding [chars] threshold Pool: [chars] Used: [int] Threshold: [int]
Explanation 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.
Recommended Action No action is required.
Error Message%SYS-2-IMMORTAL : Attempt to shut down management process [dec] ([chars]).
Explanation An attempt was made to shut down the specified management process.
Recommended Action Copy the message exactly as it appears on the console or in the system log, including the stack trace. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands, the stack trace, and your pertinent troubleshooting logs.
Error Message%SYS-2-INPUT_GETBUF : Bad getbuffer, bytes= [dec], for interface= [chars]
Explanation The software requested a buffer that is larger than the largest configured buffer size, or requested a buffer with a negative size.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SYS-3-INVMEMPID : Invalid pid [dec] in block: [hex]
Explanation An attempt has been made to allocate memory on behalf of an invalid process.
Recommended Action Copy the message exactly as it appears on the console or in the system log, including the stack trace. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands, the stack trace, and your pertinent troubleshooting logs.
Error Message%SYS-6-LOGGERSTART : Logger process started
Explanation The logger process has been initialized and started.
Recommended Action No action is required.
Error Message%SYS-6-LOGGING_BUGINF : Logging of buginf debugs was [chars]
Explanation All calls to debugging have been disabled in Cisco IOS software because the user entered the no logging buginf command. This command is used to avoid a situation where a large amount of debugging calls might overload the processor (CPU hog condition). This condition differs from the use of the undebug all command in that all debugging calls have been disabled in the Cisco IOS software. No debug reporting is available, even if debugging is enabled. Note that even though debugging has been completely disabled in the system, other message reporting, including error reporting, is still available.
Recommended Action This is an informational message only. No action is required.
Error Message%SYS-6-LOGGINGHOST_STARTSTOP : Logging to host [IP_address] [chars] [chars]
Explanation Syslog logging to the specified server or host has started or stopped.
Recommended Action No action is required.
Error Message%SYS-3-MEMLITE : Free lite called for non lite chunk by [p]
Explanation An error involving the "memory lite" component has occurred. The "free_lite_internal" process passed a chunk that is not a memory lite chunk.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SYS-4-NV_CHKSUM_INTR : An nvram checksum is already in progress; the nvram checksum from interrupt cannot be serviced
Explanation An interrupt service routine attempted to perform a checksum on the NVRAM contents and found that the resource is in use.
Recommended Action No action is required unless the command failed. If the command failed, reenter the command.
Error Message%SYS-5-PRIV_AUTH_FAIL : Authentication to Privilage level [dec] failed by[chars][chars]
Explanation The system could not change to privileged mode. The associated privilege level, user ID, and line information will be logged.
Recommended Action This is a notification message only. No action is required. To disable this particular logging feature, enter the no logging userinfo command in global configuration mode.
Error Message%SYS-5-PRIV_AUTH_PASS : Privilege level set to [dec] by[chars][chars]
Explanation The privileged mode has been enabled or the privilege level has been changed. The associated privilege level, user ID, and line information will be logged.
Recommended Action This is a notification message only. No action is required. To disable this particular logging feature, enter the no logging userinfo command in global configuration mode.
Error Message%SYS-4-PUPDATECLOCK : Periodic Clock update with ROMMON failed, because size left in ROMMON ([int]), size needed ([int]), error code ([dec])
Explanation The periodic update of the clock to ROMmon has failed. This condition indicates that the router when restarted might have old clock values.
Recommended Action Change to ROMmon mode and clear unwanted ROMmon variable entries.
Error Message%SYS-4-RESBUFEXCEED : Resource user[chars] [chars] has exceeded the buffer [chars] threshold. configured [dec] Current usage :[dec]
Explanation The Resource User specified in the error message has violated the configured threshold. Its buffer usage has gone above the threshold.
Recommended Action No action is required.
Error Message%SYS-5-RESBUFRECOVER : Resource user[chars] [chars] has recovered after exceeding the buffer [chars] threshold. configured [dec] Current usage :[dec]
Explanation The Resource User specified in the error message has recovered from the high buffer usage. Its usage has gone below the threshold.
Recommended Action No action is required.
Error Message%SYS-4-RESGLOBALBUFEXCEED : Buffer usage has gone above buffer [chars] threshold configured by resource user[chars] [chars] configured [dec] Current usage :[dec]
Explanation The global buffer usage has gone above the threshold of the RU specified in the error message.
Recommended Action No action is required.
Error Message%SYS-4-RESGLOBALBUFRECOVER : Buffer usage has gone below buffer [chars] threshold configured by resource user[chars] [chars]configured [dec] Current usage :[dec]
Explanation The global buffer usage has gone below the threshold of the RU specified in the error message.
Recommended Action No action is required.
Error Message%SYS-4-RESGLOBALMEMEXCEED : Global Memory has exceeded the [chars] threshold configure by resource user [chars]Pool: [chars] Used: [int] Threshold: [int]
Explanation 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.
Recommended Action No action is required.
Error Message%SYS-4-RESGLOBALMEMRECOVER : Global Memory has recovered after exceeding the [chars] threshold configure by resource user [chars]Pool: [chars] Used: [int] Threshold: [int]
Explanation 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.
Recommended Action No action is required.
Error Message%SYS-4-RESMEMEXCEED : Resource user [chars] has exceeded the [chars] memory threshold Pool: [chars] Used: [dec] Threshold :[dec]
Explanation 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.
Recommended Action No action is required.
Error Message%SYS-5-RESMEMRECOVER : Resource user [chars] has recovered after exceeding the [chars] memory threshold Pool: [chars] Used: [dec] Threshold :[dec]
Explanation 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.
Recommended Action No action is required.
Error Message%SYS-3-RGADDFAIL : Couldn't add process process pid [dec] to resource group [hex],
Cause: [chars]Explanation An attempt to create a resource group has failed at the indicated location. This message indicates either a logic error in the issuing component, or a low memory condition as specified in the cause.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SYS-3-RGCREATEFAIL : Resource group creation failed,\n Cause: [chars]
Explanation An attempt to create a resource group has failed at the indicated location. This message indicates either a logic error in the issuing component or a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Gather the associated stack trace. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SYS-3-RGDELEFAIL : Couldn't delete process process pid [dec] from resource group
\n Cause: [chars]Explanation An attempt to remove a process from a resource group failed at the indicated location. This message indicates a logic error in the issuing component.
Recommended Action Gather the associated stack trace. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SYS-3-RGDESTFAIL : Couldn't destroy resource group [hex],\n Cause: [chars]
Explanation An attempt to destroy a resource group failed at the indicated location. This message indicates a logic error in the issuing component.
Recommended Action Gather the associated stack trace. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SYS-3-RGMEMEXCEED : \n Limit Exceeded: [chars] Holding: [int] Requested:[int] bytes
Explanation A resource group has requested more memory than the configured limit at the indicated location.
Recommended Action .Verify that the limit is correct. Determine whether the router is the target of an DoS attack or if it is heavily stressed. Gather the associated stack trace. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SYS-3-RGOPFAIL : Requested memory thresholding operation on resource group failed
Resource Group handle: [hex], Cause: [chars]Explanation A request to set or get memory thresholding data or to enable or disable thresholding has failed in the indicated location. This message indicates a logic error in the issuing component specified in the cause.
Recommended Action Gather the associated stack trace. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SYS-5-SWITCHOVER : Switchover requested
Explanation A switchover has been requested.
Recommended Action This is an informational message only. No action is required.
Error Message%SYS-3-TCLSETFAIL : cannot set TCL interpreter variable '[chars]' \n to '[chars]' : '[chars]'
Explanation A specified value could not be passed to the TCL interpreter.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SYS-3-URLREADFAIL : cannot open file for reading '[chars]' \n
Explanation The specified URL cannot be opened for reading.
Recommended Action Check for proper URL syntax and for read permission, and retry.
Error Message%SYS-5-VIEW_AUTH_FAIL : Authentication to View [chars] failed by[chars][chars]
Explanation The system could not change to view mode. The associated privilege level, user ID, and line information will be logged.
Recommended Action This is a notification message only. No action is required. To disable this particular logging feature, enter the no logging userinfo command in global configuration mode.
Error Message%SYS-5-VIEW_AUTH_PASS : View set to [chars] by[chars][chars]
Explanation The view mode has been enabled or the view level has been changed. The associated privilege level, user ID, and line information will be logged.
Recommended Action This is a notification message only. No action is required. To disable this particular logging feature, issue the no logging userinfo command in global configuration mode.
Error Message%SYS-2-WATCHDOG : Process aborted on watchdog timeout, process = [chars].[chars]
Explanation The specified process has run for too long without relinquishing the processor. The system has shut down the process.
Recommended Action This message can be related to a combination of system load and configuration.
Gather the associated stack trace. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.SYSTEM_HM Messages
The following are system health monitor messages.
Error Message%SYSTEM_HM-3-ZERO_SYSTEM_HEALTH_RULE_CREATION_ERR : Zero system health rule creation failed due to [chars], error [dec]
Explanation The system level health monitor rule (zero_system_health_rule) could not be created.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
TAC Messages
The following are Terminal Access Controller Access Control System (TACACS) protocol messages.
Error Message%TAC-3-SECRETDEFINEFAILED : Key definition ignored.
Explanation Either the user tried to store a corrupted shared secret or memory allocation failed during secret definition. Any existing shared secrets are preserved.
Recommended Action Configure a proper secret.
TAGCOS Messages
The following are Tag distribution and control messages.
Error Message%TAGCOS-3-MEMORY_EXHAUST : [chars]
Explanation Memory could not be allocated for tag CoS classes. This condition could be caused by excessive fragmentation or insufficient memory because of high system activity or a memory leak.
Recommended Action Reduce other system activity if possible. Disable dCEF and enable CEF on all interfaces on this line card. If this message persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show running-config, show version, and show tech-support mpls commands and your pertinent troubleshooting logs.
Error Message%TAGCOS-3-PREFIX : [chars] [IP_address][IP_netmask]
Explanation One of the following conditions has occurred:
–
Storage could not be allocated for a tag CoS prefix or classes.
–
–
Recommended Action Reduce other system activity if possible. Enter the clear ip route command for the reported prefix. If this message persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show running-config, show version, and show tech-support mpls commands and your pertinent troubleshooting logs.
TCATM Messages
The following are ATM tag control messages.
Error Message%TCATM-3-BADINSERT : [IP_address][IP_netmask] x[hex] to [hex]
Explanation An internal inconsistency was detected when an attempt was made to insert an item in a list.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show running-config, show version, and show tech-support mpls commands and your pertinent troubleshooting logs.
Error Message%TCATM-3-BADSTATE : [IP_address][IP_netmask] [chars] [chars]->[chars][chars]
Explanation The ATM tag control facility uses a table-driven state machine to keep track and transition a TVC through various states. A state transition occurs when a TVC receives one of many possible events. This message has been received because a TVC has received an event that it did not expect while in this state. The system can continue to operate, but may lose the TVC that generated this message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show running-config, show version, and show tech-support mpls commands and your pertinent troubleshooting logs.
Error Message%TCATM-4-INTERFACE : Request bind interface [chars] same as output interface for [IP_address][IP_netmask]
Explanation The incoming interface of a request bind PIE is the same as the next-hop interface for the prefix. This condition may be caused by a transient routing loop during a routing protocol convergence operation, or a permanent routing loop due to a misconfiguration. As a side effect, the tag VC requests at the upstream neighbor will remain in a "BindWait" state until the situation clears up.
Recommended Action If the situation persists, check the configuration and network paths for the relevant prefix. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show running-config, show version and show tech-support mpls commands and your pertinent troubleshooting logs.
Error Message%TCATM-4-NOTAGIP : Tag switching disabled on [chars]
Explanation Tag switching is not enabled on the specified interface. Tag VCI requests and advertising will be rejected. As a side effect, the VCI requests at the upstream device can remain in a "BindWait" state until tag switching is reenabled on this interface.
Recommended Action Check to see if tag switching needs to be enabled on the specified interface. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show running-config, show version, and show tech-support mpls commands and your pertinent troubleshooting logs.
Error Message%TCATM-3-NOTRUNNING : ATM-TAGCONTROL is not running
Explanation An attempt to request or to create a binding has failed. The ATM tag control system could not be initialized. The probable cause of these conditions is either a misconfiguration or low system memory.
Recommended Action Reduce other system activity if possible. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show running-config, show version and show tech-support mpls commands and your pertinent troubleshooting logs.
Error Message%TCATM-3-OFFLIST : [IP_address][IP_netmask] [hex] not on list [hex][chars]
Explanation An internal inconsistency was detected. An attempt was made to remove from a list an item that was not on the list.
Recommended Action Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show running-config, show version, and show tech-support mpls commands and your pertinent troubleshooting logs.
Error Message%TCATM-3-ONLIST : [IP_address][IP_netmask] [hex] on list [hex][chars]
Explanation An internal inconsistency was detected when an attempt was made to add to a list an item that was already on the list.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show running-config, show version, and show tech-support mpls commands and your pertinent troubleshooting logs.
Error Message%TCATM-3-PROCESS : process not created
Explanation An attempt to create the ATM tag control process has failed. The probable cause of this condition is insufficient memory.
Recommended Action Reduce other system activity if possible. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show running-config, show version, and show tech-support mpls commands and your pertinent troubleshooting logs.
Error Message%TCATM-3-UNEXPECTEDBIND : Interface [chars] received unexpected bind for [IP_address][IP_netmask]
Explanation An unexpected bind was received for a prefix. This message appears only when a memory resource allocation failure has prevented a peer at the near end from informing the neighbor to release the bind. The system will continue, but the downstream neighbor could be holding a binding for which there is no matching VCI at the near end.
Recommended Action Reduce other system activity if possible. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show running-config, show version, and show tech-support mpls commands and your pertinent troubleshooting logs.
TCMIPC Messages
The following are Toaster-RP IPC-related messages.
Error Message%TMCIPC-4-DUP : Received a duplicated IPC record for [chars] with seq #:[dec].\n
Explanation The sequence number of the received record is the same as that of the previous received IPC message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
TCMSP Messages
The following are messages relating to call control for telephony-style hardware interfaces.
Error Message%TCMSP-3-CAPABILITYMISMATCH : voice port [chars]: call connection id [[hex] [hex] [hex] [hex]]
Explanation A mismatch in capabilities occurred between the two call legs. Capabilities are negotiated between call legs for codec, VAD and fax rate.
Recommended Action Check to see that the dial peer configuration is appropriate for the interface in question. Also check to see that the configuration on the interface is correct.
Error Message%TCMSP-3-DOCALLHISFAIL : \ntcmsp_do_call_history: [chars]
Explanation An active TCMSP call record could not be allocated or inserted into the call history list.
Recommended Action No action is required.
Error Message%TCMSP-3-DSPALARM : DSP ID [hex]: status=[hex] message=[hex] text=[chars]
Explanation The DSP has reported a fatal error. All calls on the DSP were dropped, and a DSP reload was attempted.
Recommended Action Verify that the DSP reloaded properly by attempting to place a call on the affected voice port. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TCMSP-3-DSP_TIMEOUT : DSP timeout on event [hex]: DSP ID=[hex]: [chars] (call mode=[dec])
Explanation A timeout occurred while the system was waiting for the DSP to respond.
Recommended Action The DSP has been automatically reset. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TCMSP-4-FSM_BAD_EVENT : Invalid FSM Input on channel [chars]: state=[chars] event=[dec]
Explanation An internal state machine has received illegal input. This message represents an internal software fault and may manifest itself as dropped or hung calls.
Recommended Action If this condition is causing dropped or hung calls, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TCMSP-3-FSM_ERROR : [chars]
Explanation An internal finite state machine error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TCMSP-3-MSGSNDFAIL : channel:[chars] DSP ID:[hex] Message ID:[hex]
Explanation A message could not be sent to the DSP. The call continued but may have experienced problems.
Recommended Action Verify that the DSP is still functioning properly by attempting to place a call on the affected voice port. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TCMSP-3-NOEVENT : no free event structure available from [chars] for DSP message
Explanation There were no event structures remaining in the system pools to alert the router of a voice or signaling event.
Recommended Action Check to see that the voice port for which the event was reported is still operational. If not, clear the voice port.
Error Message%TCMSP-3-TCMSP_BLOCK : tcmsp_call_block allocate failed
Explanation An "RBTreeCreate" operation has failed.
Recommended Action Add more memory.
Error Message%TCMSP-3-TCMSP_CALL_DISC_FAILED : TCMSP call disconnect failed. channel id [chars], ret [dec]
Explanation A TCMSP call disconnect could not be successfully passed. This condition may result in hung calls.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TCMSP-3-TCMSP_HAIRPIN_FAILED : Call hairpinning failed. cdb [hex], dst_cdb [hex], dst_call_id [dec]
Explanation A call that is not using DSP could not be hairpinned. Under heavy traffic, this failure may occur when no TDM resources are available.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TCMSP-3-TCMSP_HAIRPINN : hairpin peer cdb does not exist, cdb [hex], dst_call_id [dec]
Explanation A hairpin call setup failed because the other call leg does not exist.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TCMSP-3-TCMSP_HAIRPIN_NOTPOSSIBLE : Call can't be hairpinned. cdb [hex], dst_cdb [hex], dst_call_id [dec]
Explanation A call that is not using DSP could not be hairpinned.
Recommended Action Check the configuration of the dial peer.
TCP Messages
The following are Transmission Control Protocol messages.
Error Message%TCP-6-MD5NOSPACE : Insufficient space for MD5 option
Explanation There was insufficient space for the MD5 option. This condition should not occur, because the MD5 option, when requested, is required and is given preference over other TCP options.
Recommended Action Unconfigure other TCP options to make space for the MD5 option. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
TDM Messages
The following are Time-Division Multiplexing messages.
Error Message%TDM-6-TDM_CLOCK_SYNC : TDM clock aligned with PLL output.
Explanation The TDM clock is forced to align with the PLL output.
Recommended Action No action is required.
Error Message%TDM-4-TDM_CLOCK_SYNC_SKIPPED : Slot [dec] TDM clock sync skipped.
Explanation The TDM clock sync for this DFC is skipped.
Recommended Action This is a debug message only. No action is required.
TFIB Messages
The following are Tag Forwarding Information Base messages.
Error Message%TFIB-7-NONDB : Null ndb value passed to TFIB [chars]
Explanation An unexpected operation occurred on the Tag Forwarding Information Base.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TFIB-7-NOPATH : No fib_path at index [dec] for [IP_address][IP_netmask]
Explanation An unexpected operation occurred on the Tag Forwarding Information Base.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TFIB-2-NULLADJ : [chars]
Explanation An unexpected operation has occurred on the Tag Forwarding Information Base.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
TOASTER_CP Messages
The following are toaster-based coprocessor assist messages.
Error Message%TOASTER_CP-3-EREVENT : [chars] at [chars]:[dec]
Explanation A pointer with a null value failed or the function returned a code check during sanity testing.
Recommended Action Follow the instructions, if any, provided in the message text. If you require further assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TOASTER_CP-6-OUT_OF_RESOURCES : [chars] cannot utilize Co-Processor. Co-Processor limited to [dec] interfaces.
Explanation The PXF coprocessor can perform a hardware assist function only on the number of interfaces that are displayed in the error message.
Recommended Action Deconfigure PPP multiplexing and demultiplexing or RTP header compression on one or more interfaces to free coprocessor resources.
TOASTER_IPC Messages
The following are toaster interprocess communication messages.
Error Message%TOASTER_IPC-3-BAD_TIMEOUT : Invalid timeout parameter (Requested timeout in msec: [dec] - MIN: [dec], MAX [dec]).
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TOASTER_IPC-3-NO_RES : Could not allocate resource: [chars]
Explanation The named resource could not be allocated, possibly during system initialization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TOASTER_IPC-3-NO_STATE : Attempt to pass a bad message to the Toaster.
Explanation A pointer with a null value or an invalid message buffer was detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TOASTER_IPC-3-TOO_LONG : Invalid message length.
Explanation An IPC message that is longer than the configured MTU size has been received.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
TRUNK Messages
The following are E1/T1 trunk card messages.
Error Message%TRUNK-3-BADCARDTYPE : Unknown card type [hex] in slot [dec]
Explanation The card in the specified slot was not recognized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TRUNK-3-BADLOGICALIDX : Received invalid logical DS0 index of 0; 1-based logical indices expected
Explanation An invalid logical DS0 index was passed down to the platform's channelized code. This code expects logical DS0 indexing to be 1-based.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TRUNK-3-INVALIDPORT : Invalid [chars] port [dec] Range 0 to [dec]
Explanation An invalid port number has been received in the message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
TRUNK_DFC Messages
The following are trunk dial feature card messages.
Error Message%TRUNK_DFC-1-CT3HWVER : H/W Version of the CT3 in slot [dec] is too old
Explanation Requires CT3 with H/W Version 3.00 (Board Revision E) and above.
Recommended Action 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 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
TUN Messages
The following are tunnel messages.
Error Message%TUN-5-IGNOREICMPMTU : [chars] ignoring received ICMP Type 3 Code 4, due to pmtud min-mtu setting
Explanation An ICMP Type 3 Code 4 (fragmentation needed and DF set) packet has been received. This packet has specified a Next-Hop MTU smaller than the tunnel current minimum path MTU discovery MTU value. The ICMP packet has been ignored and the MTU of the tunnel has not been changed.
Recommended Action If you want the ICMP packet to be accepted and to be used to decrease the tunnel MTU then use the tunnel path-mtu-discovery min-mtu command to decrease the minimum mtu allowed. The min-mtu specified is the minimum tunnel payload mtu allowed. Use the show interface tunnel command to view the current path mtu discovery settings.
Error Message%TUN-5-TUN_TABLE : Operation [chars] on tunnel table failed for [chars] - [chars]
Explanation Manipulation of the tunnel table has failed.
Recommended Action 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 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
TURBORSC Messages
The following are marvel Route Switch Controller messages.
Error Message%TURBORSC-0-BUS_ERR_BLK : A cacheable access was blocked, bus error address: [hex], bus error data: [hex]
Explanation The specified address is mapped to multiple devices. The system is reloading.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TURBORSC-0-BUS_ERR_ILL_ADDR : An illegal address access detected on IO-Bus, bus error address: [hex], bus error data:[hex]
Explanation An illegal address access error has been detected on the I/O bus. The system is reloading.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TURBORSC-0-BUS_ERR_MULT : Address is mapped to multiple devices, bus error address: [hex], bus error data: [hex]
Explanation An address is mapped to multiple devices, the system is reloading.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TURBORSC-0-BUS_ERR_PARITY : A parity error detected on IO-Bus, bus error address: [hex], bus error data: [hex]
Explanation A parity error is detected on the IO-Bus, the system is reloading.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TURBORSC-0-BUS_ERR_TIMEOUT : Timeout has occurred on IO-Bus, bus error address: [hex], bus error data: [hex]
Explanation A timeout has occurred on the I/O bus. The system is reloading.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TURBORSC-0-BUS_ERR_UNKNOWN : Unexpected bus error, generic bus status register: [hex], bus error address: [hex], bus error data: [hex]
Explanation An unknown bus error has been detected. The system is reloading.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TURBORSC-0-UNCORRECTABLE_ECC_ERR : An uncorrectable ECC error detected, A_BUS_L2_ERRORS: [hex], A_BUS_MEMIO_ERRORS: [hex], A_SCD_BUS_ERR_STATUS: [hex]
Explanation An uncorrectable ECC error has occurred. The system is reloading.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
TWOBT Messages
The following are WS 2BT protocol driver messages.
Error Message%TWOBT-3-FSMERROR : [chars]: Error encountered (fsm rc [dec])
Explanation An error involving the driver for the 2-bit protocol finite state machine has occurred. This is not a fatal error. A retry operation should correct the condition.
Recommended Action If this message is seen repeatedly, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TWOBT-3-FSMINVALID : [chars]: Invalid fsm state ([chars]) (state [dec])
Explanation An error involving the driver for the 2-bit protocol finite state machine occurred while the protocol was being negotiated. This is not a fatal error. A retry operation should correct the condition.
Recommended Action If this message is seen repeatedly, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TWOBT-3-HWTIMER : Failed to allocate hardware timer
Explanation The driver for the 2-bit protocol finite state machine was unable to allocate a hardware timer that it requires for operation. An error has occurred while the protocol was being negotiated. This error will cause the 2-bit protocol to malfunction and cause higher layer applications that use this communication mechanism to fail.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
USB_HOST_STACK Messages
The following are USB host stack messages.
Error Message%USB_HOST_STACK-6-USB_DEVICE_CONNECTED : A [chars] USB device has been inserted in port [dec].
Explanation This is an informational message sent when an interrupt is generated to the USB controller upon device insertion.
Recommended Action No action is required.
Error Message%USB_HOST_STACK-6-USB_DEVICE_DISCONNECTED : A USB device has been removed from port [dec].
Explanation This is an informational message sent when an interrupt isgenerated to the USB controller upon device removal.
Recommended Action No action is required.
Error Message%USB_HOST_STACK-5-USB_ENUM_FAIL_ADDRFULL : Failed to enumerate a USB device as the address pool is full.
Explanation The USB address pool is full.
Recommended Action The number of inserted devices might have exceeded the platform limit. Remove the other devices that are not in use. Remove and insert this device again.
Error Message%USB_HOST_STACK-5-USB_ENUM_FAIL_GETDESCR : Failed to enumerate a USB device as not able to read the device's description.
Explanation Unable to read device descriptor information from the device.
Recommended Action The device may be faulty.
Error Message%USB_HOST_STACK-5-USB_ENUM_FAIL_NOPOWER : Failed to enumerate a USB device as the device's power requirement([dec] mA) is more than the available port power([dec] mA)
Explanation The device's power requirement exceeds the available port power.
Recommended Action Refer to platform specific documents on the maximum power provided on USB ports.
Error Message%USB_HOST_STACK-5-USB_ENUM_FAIL_SETADDR : Failed to enumerate a USB device as not able to do set device's address.
Explanation The setting of USB address to the device failed.
Recommended Action The device may be faulty.
Error Message%USB_HOST_STACK-5-USB_ENUM_UNSUPPORTED_DEVICE : Unsupported device inserted. Host id [dec], Device Addr [dec].
Explanation The device is not supported on the platform or image.
Recommended Action This device is not supported. Enter the show usb device command to see the device information. Check the image and see whether the image supports the device.
Error Message%USB_HOST_STACK-3-USB_FLASH_READY_TEST_FAILED : USB flash failed to pass 'Ready' test.
Explanation The USB Flash memory has failed diagnostic testing. The Flash memory could not enter the Ready state and was not registered in the file system.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show version, show running-config, and show usb device commands to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%USB_HOST_STACK-6-USB_FLASH_READY_TEST_TIME : USB flash 'Ready' test time over [dec] seconds.
Explanation The USB Flash memory has taken a time equal to or greater than 75% of the maximum time allotted for it to pass the diagnostic testing and enter the Ready state.
Recommended Action No action is required.
Error Message%USB_HOST_STACK-5-USB_NO_HUB_SUPPORT : USB Hub is not supported.
Explanation The USB Hub is not supported on the platform.
Recommended Action Do not use the USB Hub because it is not a supported device.
Error Message%USB_HOST_STACK-2-USB_NO_MEMORY : Memory allocation failure: [chars].
Explanation Unable to allocate memory for USB stack structures.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
USB_TOKEN Messages
The following are USB security token messages.
Error Message%USB_TOKEN-3-USB_TOKEN_MAX_TOKENS_INSERTED : Unavailable USB Security Token slot
Explanation The maximum number of tokens that can be supported are already inserted.
Recommended Action Remove the other tokens that are not in use, and remove and reinsert this token.
Error Message%USB_TOKEN-3-USB_TOKEN_MSG_FAILURE : Failure in handling USB Security Token insertion/removal event
Explanation The Retrieving Token insertion or removal message has failed in the token daemon.
Recommended Action Remove and reinsert the token. If the message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show usb device, show usb controller, and show file system commands to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%USB_TOKEN-3-USB_TOKEN_NOMEM : No available memory for [chars]
Explanation There has been a memory allocation failure.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%USB_TOKEN-3-USB_TOKEN_SEMCREATE_FAILURE : Failure in creating USB Security Token semaphore
Explanation A watched semaphore creation has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show usb device and show usb controller commands to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
USB_TOKEN_FILESYS Messages
The following are USB token files system messages.
Error Message%USB_TOKEN_FILESYS-3-ASYNC_IO_ERROR_CREATING_DIRECTORY : Error creating directory: dir [chars], ret code [hex], [chars].
Explanation The token asynchronous I/O process has failed to create a directory in the USB token device.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show usb, show usb controller, and show file system commands to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%USB_TOKEN_FILESYS-3-ASYNC_IO_ERROR_CREATING_FILE : Error creating file: file [chars], ret code [hex], [chars].
Explanation The token asynchronous I/O process has failed to create a file in USB token device.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show usb, show usb controller, and show file system commands to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%USB_TOKEN_FILESYS-3-ASYNC_IO_ERROR_DECODE_OP_CODE : Unrecognized I/O Op-code: [dec].
Explanation The token asynchronous I/O process could not decode the Op-code in an I/O request.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show usb, show usb controller, and show file system commands to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%USB_TOKEN_FILESYS-3-ASYNC_IO_ERROR_WRITING_FILE : Error writing file: file [chars], ret code [hex], [chars].
Explanation The token asynchronous I/O process has encountered an I/O write failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show usb, show usb controller, and show file system commands to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%USB_TOKEN_FILESYS-3-ASYNC_IO_FAIL_TO_GET_ARGUMENT : Token Asynchronous I/O: Could not get argument.
Explanation The token asynchronous I/O process has failed to retrieve an argument.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show usb, show usb controller, and show file system commands to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%USB_TOKEN_FILESYS-3-ASYNC_IO_FAIL_TO_REQUEUE_REQUEST : Token Asynchronous I/O: failing to requeue an I/O request.
Explanation The token asynchronous I/O process has failed to requeue an I/O request.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show usb, show usb controller, and show file system commands to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%USB_TOKEN_FILESYS-3-ASYNC_IO_UNEXPECTED_EVENT : Token Asynchronous I/O: Unexpected Event [dec].
Explanation The token asynchronous I/O process has received an unexpected event.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show usb, show usb controller, and show file system commands to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%USB_TOKEN_FILESYS-3-FAIL_TO_BUILD_MFD : USB Token File System failed to build MFD...
Explanation The USB token file system has failed to build the Master File Directory (MFD) database.
Recommended Action Remove this token and reinsert it. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show usb, show usb controller, and show file system commands to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%USB_TOKEN_FILESYS-3-FAIL_TO_CREATE_TALKER : Token File System callback: failed to create token talker, token name [chars], status [dec].
Explanation The USB Token file system failed to establish a connection with the USB token device driver.
Recommended Action Remove this token and reinsert it. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show usb, show usb controller, and show file system commands to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%USB_TOKEN_FILESYS-3-FAIL_TO_CREATE_WATCHED_BOOLEAN : Could not create a watched boolean!
Explanation The USB token file system could not create a watched boolean. This condition indicates that memory resources are being exhausted.
Recommended Action Reduce other system activities to ease memory demands or remove any token device that is not in use to free up some memory.
Error Message%USB_TOKEN_FILESYS-3-FAIL_TO_DESTROY_TALKER : Token File System callback: failed to destroy token talker, token name [chars], status [dec].
Explanation The USB token file system has failed to destroy the connection with the USB token device driver.
Recommended Action Remove this token and reinsert it. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show usb, show usb controller, and show file system commands to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%USB_TOKEN_FILESYS-3-FAIL_TO_REGISTER_WITH_IFS : Failed to register USB Token File System with IFS.
Explanation The process of registering the USB token file system with the IOS File System (IFS) did not succeed. the IFS provides a common user interface to all users of file system functionality regardless of the differences among file systems.
Recommended Action Remove this token and reinsert it. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show usb, show usb controller, and show file system commands to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%USB_TOKEN_FILESYS-3-MAX_TOKENS_INSERTED : The number of tokens exceeded the maximum that can be supported by USB Token File System.
Explanation The maximum number of tokens that can be supported by the USB Token File System have been inserted.
Recommended Action Remove the other tokens that are not in use. Remove this token and reinsert it. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show usb, show usb controller, and show file system commands to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%USB_TOKEN_FILESYS-3-MFD_FORWARD_INCOMPATIBLE : Unable to understand MFD database of version [dec].[dec].
Explanation The version of the Master File Directory (MFD) database stored in the token device is a later version than the running USB token file system can support or understand.
Recommended Action Upgrade the USB token file system by reloading the router with a later version of IOS software.
Error Message%USB_TOKEN_FILESYS-6-REGISTERED_WITH_IFS : USB Token File System [chars] is registered...
Explanation The USB token file system has registered successfully.
Recommended Action This is an informational message only. No action is required.
Error Message%USB_TOKEN_FILESYS-6-REGISTERING_WITH_IFS : Registering USB Token File System [chars]: might take a while...
Explanation The USB token file system is being registered.
Recommended Action This is an informational message only. No action is required.
Error Message%USB_TOKEN_FILESYS-3-UNKNOWN_TOKEN_EVENT : Token File System callback: unknown event [dec].
Explanation The USB token file system callback function received an unknown event from the USB token device driver.
Recommended Action Check the USB ports to see if the token device is inserted or removed correctly. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show usb, show usb controller, and show file system commands to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%USB_TOKEN_FILESYS-6-USB_TOKEN_INSERTED : USB Token device inserted: [chars].
Explanation A USB token device has been detected.
Recommended Action This is an informational message only. No action is required.
Error Message%USB_TOKEN_FILESYS-6-USB_TOKEN_REMOVED : USB Token device removed: [chars].
Explanation A USB token device has been removed.
Recommended Action This is an informational message only. No action is required.
USBFLASH Messages
The following are USB flash device messages.
Error Message%USBFLASH-5-CHANGE : [chars] [chars]
Explanation A USB device has been inserted or removed.
Recommended Action No action is required.
Error Message%USBFLASH-3-DEVOPEN : [chars] [chars]
Explanation An application handle for the USB flash could not be retrieved.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%USBFLASH-3-DEVSTARTSTOP : [chars] [chars]
Explanation The USB flash device could not be stopped and restarted.
Recommended Action PleCopy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%USBFLASH-5-DIBERR : USB Flash device [chars] [chars]
Explanation 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.
Recommended Action 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.
Error Message%USBFLASH-4-FORMAT : [chars] [chars]
Explanation The USB flash device does not have a recognizable formatThere are unexpected values in the partition table or boot sectorThis device needs formatting in the router before use.
Recommended Action Follow any instructions provided in the error message before storing any file to this USB flash device
Error Message%USBFLASH-3-IFSCREATE : [chars] [chars]
Explanation The USB flash device could not be registered with the internal file system.
Recommended Action Please search Bug Toolkit on the Cisco web site forbugs related to your version of software. If you do not find an existing bug, please open a TAC case and provide the output of the show version and show running-config commands.
TWO_GIGE Messages
The following are 2-port Gigabit Ethernet subsystem messages.
Error Message%TWO_GIGE-3-GEMAXADDR : [chars], expected [hex], actual [hex]
Explanation Too many MAC addresses are in the filter table.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TWO_GIGE-3-GEMISMATCH : [chars], expected [hex], actual [hex]
Explanation PCI initialization for common Gigabit Ethernet (C_GIGE) has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TWO_GIGE-3-HW_FAULT : 2GIGE HW error, [chars], error_code=[hex]
Explanation A two-port Gigabit Ethernet operation error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TWO_GIGE-3-IDBINITFAIL : 2GIGE IDBs create failed
Explanation The create IDBs request for the 2-port Gigabit Ethernet interface module has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TWO_GIGE-3-IMAGEDOWNLOADFAIL : 2GIGE fpga image download failed, [chars]
Explanation The download of the FPGA image for the 2-port Gigabit Ethernet interface module has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TWO_GIGE-3-INITFAIL : 2GIGE initialization failed, [chars]
Explanation The initialization for the common Gigabit Ethernet (C_GIGE) has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TWO_GIGE-3-INTERNAL : 2GIGE internal error, [chars]
Explanation An internal error has occurred within the 2-port Gigabit Ethernet interface module.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TWO_GIGE-3-MAJOR_FAULT : 2GIGE unrecoverable error, [chars], error_code=[hex]
Explanation A 2-port Gigabit Ethernet operation error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TWO_GIGE-3-MIBINITFAIL : 2GIGE MIB initialization failed, [chars]
Explanation The MIB initialization for the common Gigabit Ethernet (C_GIGE) has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%TWO_GIGE-6-UNKNOWN : Unknown message ([dec]) received ([chars]) from interface [chars]
Explanation An unknown message has been received from the back card.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
UTIL Messages
The following are utility messages.
Error Message%UTIL-0-ITEMLIST_RESIZE : An attempt was made to resize an itemlist but not enough memory is available
Explanation An attempt was made to resize the item list memory to be larger than the available memory. Item lists are often used when interface statistics are shown. This event is unexpected, and may be an indication of memory corruption.
Recommended Action Note any recent commands that may have triggered this error. Copy the message and traceback exactly as they appear on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
VIP Messages
The following are Versatile Interface Processor messages.
Error Message%VIP-3-DRAM_RENOWRITE_BUSERR : DRAM Reno ASIC write bus error:Error address = [hex], [chars].
Explanation A Reno data-transfer-specific ASIC write bus error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
VIPMLP Messages
The following are multilink PPP messages.
Error Message%VIPMLP-2-NOINTERLEAVE : [chars] Interleave not configured due to Insufficient memory
Explanation The interleave function could not be configured due to insufficient memory.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs
VOICE_ELOG Messages
The following are voice event logger messages.
Error Message%VOICE_ELOG-3-DUMPFAIL : Could not dump to remote file - [chars] [chars]. Error=[dec]([chars])
Explanation The event log could not be downloaded to the remote file.
Recommended Action Check the network connectivity, setup, and configuration of the protocol.
Error Message%VOICE_ELOG-3-INIT_FAIL : Initialization fails - [chars].
Explanation The event logger system could not be initialized.
Recommended Action Check the availability of router resources, such as memory.
Error Message%VOICE_ELOG-4-MEM_USAGE_HI_WATERMARK : System memory on high usage ([dec]/100). Stopping processing new event log for now.
Explanation The system is low on memory. Throttle control has been applied on the event logger system. The new event will continue processing when sufficient memory becomes available.
Recommended Action Ensure that the gateway has the recommended amount of memory for this Cisco IOS feature set and version, or reduce other system activity to ease memory demands, such as disabling the FTP dump or enabling the event log for specific applications only.
Error Message%VOICE_ELOG-5-MEM_USAGE_LO_WATERMARK : System memory usage ([dec]/100) is below low watermark now. Resume processing new event log
Explanation Sufficient memory is now available. Throttle control has been removed.
Recommended Action No action is required.
Error Message%VOICE_ELOG-3-MSGDROPPED : [dec] messages failed to be written in event log (client id:[chars], dump url:[chars]).
Explanation The event message could not be saved to the log.
Recommended Action Check that sufficient system memory is available, and check for errors involving the dump event log if error logging has been configured.
VOICE_IEC Messages
The following are voice internal error code (IEC) messages.
Error Message%VOICE_IEC-3-EXT : Externally-generated Internal Error Code received: [dec].[dec].[dec].[dec].[dec].[dec]
Explanation An external entity has initiated the termination of a voice call. It has signaled its internal error code (IEC) to this gateway, to be reported in the accounting record for this call. This condition is being reported by the system logger (syslog) because of the configuration as specified by the voice iec syslog command.
Recommended Action To display more information on the details of this error, enter the show voice iec description IECvalue command, with IECvalue being the value of the IEC that was received. Debugging actions might also indicate the cause of the error.
Error Message%VOICE_IEC-3-GW : [chars]: Internal Error ([chars]): IEC=[dec].[dec].[dec].[dec].[dec].[dec] on callID [dec] [chars]
Explanation An internally detected error has caused a voice call to be released or terminated. An internal error code (IEC) has been generated to report the error. This IEC will be logged in the accounting record for this call. This condition is being reported by the system logger (syslog) because of the configuration as specified by the voice iec syslog command.
Recommended Action To display more information on the details of this error, enter the show voice iec description IECvalue command, with IECvalue being the value of the IEC that was received. Debugging actions might also indicate the cause of the error.
Error Message%VPN_HW-1-INITFAIL : Slot [dec]: [chars]
Explanation The VPN hardware accelerator driver has failed to initialize the accelerator at the slot specified in the error message at the specified point. This event will negatively impact encryption performance.
Recommended Action Reload the router. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
VOICE_RC Messages
The following are MC3810 voice resource subsystem messages.
Error Message%VOICE_RC-5-DSP_REMOVED : DSP ID:[dec] removed from service after [dec] reset within [dec] minutes
Explanation This is a notification message. This message indicates that the DSP might have failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%VOICE_RC-5-DSP_RESET : DSP ID:[dec] reset
Explanation This is a notification message. This message indicates that there has been a DSP reset of the Cisco IOS software because of a possible DSP error.
Recommended Action Unavailable.
VPDN Messages
The following are Virtual Private Dialup Networking messages.
Error Message%VPDN-5-IGNOREICMPMTU : Ignoring received ICMP Type 3 Code 4, due to pmtu min or max setting
Explanation An ICMP Type 3 Code 4 (fragmentation needed and DF set) packet has been received. This packet has specified a next-hop MTU that is smaller or greater than the current minimum or maximum path MTU discovery value. The ICMP packet has been ignored and the MTU has not been changed.
Recommended Action If you want the ICMP packet to be accepted and used to decrease or increase the MTU, then use the vpdn pmtu min command to decrease the minimum MTU that is allowed and enter the vpdn pmtu max 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.
Error Message%VPDN-3-IP_SWITCH_ERR : l2x ip switching vector not installed
Explanation The platform-dependent L2X IP CEF switching module is missing.
Recommended Action Unavailable.
VPN_HW Messages
The following are VPN hardware accelerator messages.
Error Message%VPN_HW-1-ALIGN : Slot: [dec] - Alignment failure on packet buffer: [hex]
Explanation A software error has occurred. The VPN hardware accelerator driver has detected that the buffer is not aligned correctly.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%VPN_HW-1-ERROR : slot: [dec] - [chars]
Explanation An error occurred in the application that is using the VPN hardware accelerator driver.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%VPN_HW-6-FIPSFAIL : FIPS test_id [dec]([chars]) Test Failure will be induced
Explanation The FIPS test was forced to fail from ROMMON.
Recommended Action Do not set FIPS_FAIL via ROMMON if the fips failure test is not desired.
Error Message%VPN_HW-1-HEARTBEAT : VPN Module in slot: [dec]: Keepalive lost.
Explanation The VPN hardware accelerator appears to have stopped operating.
Recommended Action Reboot your router. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%VPN_HW-6-INFO : slot: [dec] [chars]
Explanation This is an informational message from the VPN hardware accelerator driver.
Recommended Action This message occurs in normal operation. No action is required.
Error Message%VPN_HW-6-INFO_LOC : Crypto engine: [chars] [chars]
Explanation This is an informational message from the VPN hardware accelerator driver.
Recommended Action This is an informational message from the VPN hardware. The driver is operating normally. No action is required.
Error Message%VPN_HW-1-INITFAIL : Slot [dec]: [chars]
Explanation The VPN hardware accelerator driver failed to initialize the accelerator at the slot specified in the error message at the specified point.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%VPN_HW-3-MULTDEV : Cannot support more than one Encryption AIMs
Explanation A second Encryption AIM module is present in the system. The Encryption AIM software supports only a single Encryption AIM. All other Encryption AIMs that are installed will be ignored.
Recommended Action Remove one of the Encryption AIMs that is installed in your system.
Error Message%VPN_HW-1-NOMEMORY : [chars] creation failed for slot [dec]
Explanation The VPN hardware accelerator driver, during its initialization phase, could not allocate memory for the data structure that is specified in the error message.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%VPN_HW-1-OWNER : slot: [dec]: [chars] packet buffer, pak=[hex]
Explanation A software or hardware error has occurred. The VPN hardware accelerator driver has detected that the buffer ring is in an inconsistent and unrecoverable state.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%VPN_HW-1-PACKET_ERROR : slot: [dec] Packet Encryption/Decryption error, [chars]
Explanation An unexpected error occurred while a packet was being encrypted or decrypted.
Recommended Action This message can occur occasionally during normal operation of the system. It may occur while the system is transitioning 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 the status value 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. The VPN hardware accelerator will most likely need to be replaced.
Error Message%VPN_HW-6-SHUTDOWN : [chars] shutting down
Explanation The specified VPN hardware accelerator is shutting down. It may have been physically removed.
Recommended Action This is an informational message only. It occurs in normal operation. No action is required.
Error Message%VPN_HW-1-TOOBIG : Slot: [dec] - [chars] received a packet with size [dec].
Explanation A packet was received that is larger than the configured MTU.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%VPN_HW-1-UNSUPP : VPN Module in slot: [dec]: [chars] ([hex]).
Explanation This revision or version of the VPN hardware accelerator in the slot specified in the error message is not supported.
Recommended Action Verify that the VPN hardware adapter is the proper hardware level and software revision for the version of Cisco IOS software that is operational on your system. If it is, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
VSAT Messages
The following are satellite module messages.
Error Message%VSAT-1-BACKUPFAIL : Backup failed for module [chars] - Cause: [chars]
Explanation Backup mode for the satellite interface has failed to initialize. This condition indicates a failure to initialize a socket for backup communications to the satellite hub. If the satellite backup configuration is correct, the cause is likely a problem with internal software coding.
Recommended Action Verify proper configuration of backup parameters on the satellite interface. 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 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%VSAT-3-BADCONFIG : Initial configuration parameter not accepted on [chars]
Explanation The satellite module did not accept a configuration parameter. This is usually because the version of the internal software on the module is not compatible with the Cisco IOS software running on the router. This error might also indicate a problem with internal software coding.
Recommended Action Verify that the satellite module firmware and the Cisco IOS software are compatible and up to date. 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 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%VSAT-2-FW_ERROR : Firmware on module [chars] reported the following error: [chars]
Explanation The firmware on the satellite module reported an urgent error. This error might indicate a problem with internal software coding.
Recommended Action Enter the debug satellite all command to enable further debug output. 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 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%VSAT-6-HSRP_STANDBY : [chars] module set to [chars] state due to an HSRP event
Explanation The satellite standby state was changed due to an HSRP status change on the monitored IP redundancy group. This is for information only and is not an error. When VSATs are connected in a Y cable formation for configuration as part of an HSRP IP redundancy group, one module must be set as active, and the others as standby. To avoid transmit interference, the non-active satellite modules are set to standby mode. Standby mode ceases all inbound activity on the satellite link and puts the module in an inactive state.
Recommended Action No action is required.
Error Message%VSAT-1-INITFAIL : NM slot [dec]: Device [dec] initialization failed
Explanation The initialization of the Satellite network module has failed.
Recommended Action Power down, reseat the interface card, and reboot the system. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%VSAT-6-PIMINCOMPADDR : The IP address configured on [chars] requires a manually configured IP address for the satellite module
Explanation This message is informational and a reminder that further configuration may be required. For the satellite service module to automatically configure its own IP address, the value of the IP address on the satellite interface must yield a remainder of 2 when divided by 4. The value entered requires "service-module ip address" to be entered manually. Automatic configuration assures that PIM and other features work correctly. Manual configuration must be done carefully to activate all features. For example, for PIM to work properly, the IP addresses and masks between the satellite interface and the satellite service module interface must be specifically defined. The interface must be configured with a large subnet that includes all the VSATs in the satellite network. The service module must be configured with a /30 subnet. To the service module, all VSATs are on separate subnets so it does routing between the VSATs as its software requires. The router sees all VSATs as on the same subnet, so the VSATs can establish PIM neighbors. The service module needs to be a lower IP address than the router so that IGMP works properly. Hence the requirement that the IP address on the router be the higher of the two host addresses available on the /30 network.
Recommended Action Configure the "service-module ip address" to complete the manually configured IP address on the satellite module.
Error Message%VSAT-5-RESTORE_IP : [chars] "service-module ip address" restored
Explanation The service-module IP address has been restored because the interface IP address changed. The new interface IP address is now on the same subnet as the previous address, so the compatible service-module IP address has been restored from the internal copy that was saved previously.
Recommended Action No action is required.
Error Message%VSAT-5-STANDBY_MODE : [chars] module configured for standby mode
Explanation The satellite module is configured to boot up in standby mode. This will keep the module inactive unless it is activated by an HSRP IP redundancy group change. This condition is normal during operation of satellite modules configured as part of an HSRP IP redundancy group, and serves as a reminder that the module will be inactive until an HSRP change occurs.
Recommended Action If standby HSRP operation is not desired, removing the HSRP IP redundancy group configuration will clear the condition.
Error Message%VSAT-5-UNCONFIGURE_IP : [chars] "service-module ip address" unconfigured
Explanation The service-module IP address has been unconfigured because the interface IP address changed. The new IP address is not in the same subnet as the previous one, or the interface IP address has been unconfigured. The service-module IP address is internally saved so that if the IP address is later changed back to the same subnet, the service-module IP address is automatically restored.
Recommended Action No action is required.
VSI_M Messages
The following are Virtual Switch Interface (VSI) master messages.
Error Message%VSI_M-6-ABOVEWATERMARK : VSI Master input queue goes above high water mark
Explanation The VSI master queue depth is approaching its high-water mark.
Recommended Action If this message is observed in the log frequently during network operations, consider changing the VSI session message window size to a lower value by entering the label-control-protocol vsi window-size command.
Error Message%VSI_M-6-BELOWWATERMARK : VSI Master input queue goes below high water mark
Explanation The VSI master queue depth is approaching its low-water mark.
Recommended Action If this message is observed in the log frequently during network operations, consider changing the VSI session message window size to a lower value by entering the label-control-protocol vsi window-size command.
Error Message%VSI_M-2-CFG_FAILED : [chars]
Explanation The VSI Master configuration has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config, show version, show controllers vsi descriptor, show controllers vsi status, show controllers vsi session, and show logging commands to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%VSI_M-6-NEGETIVECNT : [chars] falls below zero
Explanation An internal error has occurred.
Recommended Action No action is required.
Error Message%VSI_M-2-NOMEM : [chars] failed because of low memory
Explanation A memory allocation failure has occurred in the VSI master module.
Recommended Action Increase the hardware memory of the router.
Error Message%VSI_M-6-STATECHANGE : (session [dec] on [chars]) event [chars], state [chars] -> [chars]
Explanation A VSI sessions has changed its state from or to an "established" or "resync" state.
Recommended Action No action is required.
Error Message%VSI_M-5-UPDELAY : [dec]-seconds delay of VSI instance (control if [chars]) creation [chars]
Explanation A VSI instance creation delay either has begun or has ended. The message text describes the change.
Recommended Action No action is necessary.
VSTATS Messages
The following are voice statistics push data messages.
Error Message%VSTATS-6-IEC : SEQ=[int]:\n[chars]
Explanation The text data has been pushed out as an internal error code.
Recommended Action If one large message has been chopped into multiple segments, reorder the statistics text data with the given sequence (SEQ) number. The text data can be parsed or uploaded to be processed in a more elegant form.
Error Message%VSTATS-6-VCSR : SEQ=[int]:
[chars]Explanation The text data has been pushed out as a voice call statistics record.
Recommended Action If one large message is chopped into multiple segments, reorder the statistics text data with the given sequence (SEQ) number. The text data can be parsed or uploaded to be processed in a more elegant form.
VTSP Messages
The following are Voice Telephony security parameter index (SPI) messages.
Error Message%VTSP-6-UNKNOWN_EXT_AGENT_RESET_ATTEMPT : Request to reset an uknown external agent (ID [dec]) attempted. Attempt ignored.\n
Explanation The Cisco IOS software is unable to process a request to reset an external agent (such as H323 Gatekeeper or the MGCP CA). A failed attempt of this type is not a router error. However, it does indicate that the external agent did not received a reset request.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%VTSP-4-VTSP_PLAR_TIE_FAILED : VTSP connection plar tie set up failed. channel id [chars], cause [dec]
Explanation A connection PLAR tie setup has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
WARMUPGRADE Messages
The following are warm upgrade feature messages.
Error Message%WARMUPGRADE-3-CHECKSUM : [chars] image size mismatch.
Explanation The checksum of the image in memory is different from the expected checksum.
Recommended Action Check to see whether the image file is complete and uncorrupted.
Error Message%WARMUPGRADE-3-DECOMPRESS : Image file decompression failure.
Explanation A warm upgrade could not decompress the image file.
Recommended Action Check to see whether the image file is complete and uncorrupted.
Error Message%WARMUPGRADE-3-FILE : Image file open/read failure.
Explanation A warm upgrade could not open or read from the specified image file.
Recommended Action Check to see whether the specified image is present at the desired location and that it has the required read permissions.
Error Message%WARMUPGRADE-3-FORMAT : Unknown image file format.
Explanation A warm upgrade could not recognize the format of the image file.
Recommended Action Check to see whether the specified image is a valid Cisco IOS software executable image and is in a supported format. Check the release notes for supported formats.
Error Message%WARMUPGRADE-3-SIZE : [chars] image size mismatch.
Explanation The size of the image in memory is different from the expected size.
Recommended Action Check to see whether the image file is complete and uncorrupted.
WCCP Messages
The following are Web Cache Communication Protocol (WCCP) messages.
Error Message%WCCP-3-NOMEMORY : Unable to allocate message buffer, WCCP V[dec] closing down
Explanation The WCCP process was unable to allocate enough memory to hold incoming protocol messages.
Recommended Action Ensure that there is enough memory available for all processes.
Error Message%WCCP-3-NOSOCKET : Unable to open cache discovery socket, WCCP V[dec] closing down
Explanation The WCCP process was unable to open the UDP socket that is used to listen for protocol messages from caches.
Recommended Action Ensure that the IP configuration is correct and that at least one IP address is configured.
Error Message%WCCP-3-SBADDFAIL : Unable to add WCCP subblock on interface [chars]
Explanation The WCCP process was unable to attach interface specific service information.
Recommended Action Ensure that there is enough memory available for all processes.
Error Message%WCCP-3-SBCREATEFAIL : Unable to allocate WCCP subblock on interface [chars]
Explanation The WCCP process was unable to allocate memory to hold interface specific service information.
Recommended Action Ensure that there is enough memory available for all processes.
WIC_AM Messages
The following are WIC-AM modem initialization messages.
Error Message%WIC_AM-3-WIC_AM_BAD_SPEED : The modem line only supports a speed of 115200.
Explanation The WIC supports only 115200 bps. There is no need to change this speed because the connection between the DTE and the DCE is local, within the WIC.
Error Message%WIC_AM-3-WIC_AM_BAD_STOPBIT : Cannot set stop bits for this async interface.
Explanation The WIC interface supports only 1 stop bit.There is no need to change this because the connection between the DTE and the DCE is local,within the WIC.
WLCCP_WDS Messages
The following are Wireless LAN Context Control Protocol (WLCCP) for WDS messages.
Error Message%WLCCP_WDS-3-MAX_AP_REACHED : Cannot Authenticate AP as MAX Number [dec] of APs Reached
Explanation The WDS on this platform cannot support any more access points.
Recommended Action No action is required.
Error Message%WLCCP_WDS-6-PREV_VER_AP : A previous version of AP is detected
Explanation A previous version of an access point has been detected.
Recommended Action No action is required.
Error Message%WLCCP_WDS-6-REPEATER_STOP : WLCCP WDS on Repeater unsupported, WDS is disabled
Explanation WDS is not supported on a repeater.
Recommended Action No action is required.
WSHTF Messages
The following are HT_FPGA data plane driver messages.
Error Message%WSHTF-3-FPGA_DLL : [chars]
Explanation The software could not initialize the line card packet forwarding controller. This condition could be a hardware failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%WSHTF-1-INITFAIL_NOBUF : [chars], buffer replacement failed, no buffers available
Explanation The HT-FPGA data plane driver could not secure replacement buffers for packet reception. This condition indicates either insufficient router memory or a software module that is not releasing receive buffers back to the driver in a timely fashion.
Recommended Action If this condition is caused by insufficient router memory, consider a memory upgrade. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%WSHTF-3-NOTHTFPGA : Device ID seen as [hex], expected [hex]. Bus number [hex] device number [hex].
Explanation The software could not recognize the data plane chip.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%WSHTF-1-RESFAIL : [chars] [dec]
Explanation The HT-FPGA data plane driver failed to get resources to attach its data structures to the global table. This condition indicates that the system is running low on memory.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show memory summary command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%WSHTF-3-TOOBIG : attempt to send giant packet on [chars] ([dec] bytes from [hex], max allowed [dec])
Explanation A process inside the router is attempting to send an oversized packet.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
WSIPC Messages
The following are Windstar IPC messages.
Error Message%WSIPC-1-ALLOCFAIL : [dec]/[dec] [chars] allocation failure
Explanation A memory allocation failure has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%WSIPC-3-CARDERR : [chars]
Explanation An IPC card has registered itself to the active IPC twice. The card malfunctioned and its IPC is not active.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%WSIPC-3-CMDOP : IPC command [int] (slot[int]/[int]): [chars]
Explanation IPC command processing operational errors have occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%WSIPC-3-CREATE_FAIL : [chars] [chars]
Explanation A IPC port could not be created on the RP.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%WSIPC-3-ERROR : [chars] (slot [dec]): [chars]
Explanation An IPC error has been detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%WSIPC-3-EVENTOP : Event [int] from slot[int]: [chars]
Explanation IPC event processing operational errors have occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%WSIPC-3-GETBUF : [chars]
Explanation Packet buffers could not be obtained.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%WSIPC-3-INVNUM : [chars] ([int])
Explanation The IPC application tried to send a message that was larger than IPC could process. The message was not transmitted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%WSIPC-3-MSGERR : [chars] ([int])
Explanation The standby IPC cannot register with the active IPC. The standby IPC cannot exchange messages with the active IPC.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%WSIPC-3-NBLKCMD : [chars]
Explanation A nonblocking IPC command queue could not be initialized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%WSIPC-3-NOHWIDB : Cannot find hwidb for interface([int]/[int])
Explanation The interface identifier does not exist for the interface that is addressed by the corresponding IPC message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%WSIPC-3-NULLMSG : Null [chars] ipc message
Explanation An unexpected empty IPC message was received.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%WSIPC-3-PORT : port ([chars]) already exists
Explanation The port to be created already exists.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%WSIPC-3-PORTOP : For port ([chars]): [chars] fails (cause: [chars])
Explanation A IPC kernel port-related system call failure has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%WSIPC-3-RESTART : [chars]
Explanation An error was detected during a line card IPC reinitialization after an RP switchover. This condition can occur because the system is operating under heavy traffic when an RP is being switched over. If the line card software cannot proceed after this error, the line card will be deactivated and restarted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%WSIPC-3-SEATERR : [chars] ([int])
Explanation The ID associated with an IPC card either ismissing, is duplicated, or cannot be created.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%WSIPC-3-SYSCALL : System call for command [int] (port [int]/[int]) : [chars] (Cause: [chars])
Explanation An IPC kernel system call error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
XCCTSP_VOICE Messages
The following are External Call Control Telephony Service Provider messages.
Error Message%XCCTSP_VOICE-3-OUTOFRANGE_CTRL : Going out of range for controller number for the slot \n subslot [dec], ctrl_num [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
XDSLWIC Messages
The following are driver messages for xDSL on the Cisco 2600 series and 3600 series of routers.
Error Message%XDSLWIC-3-DYING_GASP : [chars]: The remote CPE is about to loose power
Explanation Power loss messages have been received from the remote CPE.
Recommended Action Repair the local power supply for the remote CPE.
Error Message%XDSLWIC-3-E1T1_INITFAILURE : Slot [dec], Unit [dec] initialization failure - [chars]
Explanation The E1T1 driver detected an error while initializing.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%XDSLWIC-3-FIRMWARE_DOWNLOAD_FAILURE : XDSLWIC R FPGA download fails. failure counts = [char].
Explanation The FPGA load might be bad.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%XDSLWIC-3-FIRMWARE_VERSION_CHECK_FAILURE : Failed XDLSWIC FPGA version check; expected [hex]; got [hex] at location [hex]
Explanation The FPGA load might have failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%XDSLWIC-1-INITFAIL : XDSLWIC([dec]/[dec]), Init failed, CSR[dec]=[hex].
Explanation The xDSL WIC hardware might be bad, or there might be no memory left in the system.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Y88E8K Messages
The following are 88E8000 E/FE/GE controller messages.
Error Message%Y88E8K-1-ACCESS_FAILED : Unable to access Y88E8K chip
Explanation During driver initialization, the Y88E8K chip was unable to be accessed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%Y88E8K-1-BAD_IDB : Invalid Interface Descriptor Block
Explanation The driver tried to fetch the interface's IDB and failed.
Recommended Action Software bug - open a case with Development Engineering. 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 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Recommended Action This is a software bug. Open a case with Development Engineering. Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%Y88E8K-1-BAD_MEDIA : Unknown media-type in subblock
Explanation The media-type specified in the driver subblock is invalid.
Recommended Action This is a software bug. Open a case with Development Engineering. Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%Y88E8K-1-BAD_PARTICLE : Problem getting particle size
Explanation The driver was unable to get the particle size for this interface.
Recommended Action This is a software bug. Open a case with Development Engineering. Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%Y88E8K-1-BAD_PLUGIN : Plugin function table incomplete or missing
Explanation The driver could not access the PA's specific function table.
Recommended Action This is a software bug. Open a case with Development Engineering. Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%Y88E8K-1-BAD_POOL : Could not init buffer pools
Explanation The driver failed to get a pool of buffers from IOS.
Recommended Action This is a software bug. Open a case with Development Engineering. Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%Y88E8K-1-BAD_SB_NOMEM : [chars] - Cannot create IDB subblock due to insufficient memory
Explanation There was insufficent system memory to create the subblock.
Recommended Action The router requires more main memory. 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 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%Y88E8K-1-BAD_STRUCT : Could not initialize structure
Explanation The driver failed to initialize a structure.
Recommended Action This is a software bug. Open a case with Development Engineering. Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%Y88E8K-1-BAD_SUBBLOCK : [chars] - Could not install or use y88e8k IDB subblock
Explanation An internal IOS error has prevented the IDB subblock from being installed or used.
Recommended Action This is a software bug. Open a case with Development Engineering. Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%Y88E8K-1-DISCOVER : Only found [dec] interfaces on bay [dec], shutting down bay
Explanation A possible hardware error has resulted in too few interfaces being discovered.
Recommended Action 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 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%Y88E8K-3-ERRINT : [chars], error interrupt
Explanation The y88e8k controller has signaled an error condition.
Recommended Action 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 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%Y88E8K-3-GE_MAC_HW_ERROR : [chars]:Hardware Error, [chars]
Explanation There was an error in the GE MAC controler.
Recommended Action 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 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%Y88E8K-3-I2C_ERROR : [chars]
Explanation There was an error in the I2C transaction.
Recommended Action 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 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%Y88E8K-3-I2C_READ_TIMEOUT : Read from I2C device failed
Explanation A read transaction from the I2C has timed out.
Recommended Action 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 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%Y88E8K-3-I2C_WRITE_TIMEOUT : Write to I2C device failed
Explanation A write transaction to the I2C has timed out.
Recommended Action 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 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%Y88E8K-1-IDBTYPE_UNK : Unknown IDBTYPE while starting Y88E8K
Explanation The IDBTYPE in the interface's instance structure is undefined for this driver.
Recommended Action This is a software bug. Open a case with Development Engineering. Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%Y88E8K-3-ILP_MSG_TIMEOUT_ERROR : [chars]: EtherSwitch Service Module RBCP ILP messages timeout
Explanation RBCP messages related to Inline Power were not received within the configured time limit. The RBCP link has been set to down. The power budget on the router and Etherswitch Service Module may not be consistent or phones waiting for power may not be powered on. Check the Service Module status or the configuration of the internal link.
Recommended Action 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 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%Y88E8K-3-ILPM_Y88E8K : Bay [int], device number [int]
Explanation Inline power initialization has failed
Recommended Action 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 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%Y88E8K-1-INITFAIL_NOMEM : [chars], initialization failed, no buffer memory
Explanation The Ethernet port initialization has failed due to insufficient memory.
Recommended Action The router requires more packet memory; consider an upgrade. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%Y88E8K-1-INITFAIL_RBCP : [chars], initialization failed, unable to start RBCP
Explanation The RBCP protocol initialization has failed
Recommended Action Power down, reseat the network module, and reboot the system. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%Y88E8K-1-INVALID_SPEED : Ethernet speed is invalid
Explanation An invalid speed was found while trying to set the speed for Y88E8K.
Recommended Action 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 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%Y88E8K-1-MODE_INVALID : Unknown or invalid chip mode (GMII/STBI)
Explanation The driver subblock contains an invalid or undefined chip operating mode (SMII or STBI mode).
Recommended Action This is a software bug. Open a case with Development Engineering. Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%Y88E8K-2-NOISL : Interface [chars] does not support ISL
Explanation ISL is not supported on the specified interface's hardware.
Recommended Action No action is required.
Error Message%Y88E8K-3-NOTY88E8K : Bay [int], device number [int]: unknown device ([hex])
Explanation The PA does not contain a Yukon 88E8000 controller chip.
Recommended Action 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 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%Y88E8K-3-PHY_BUSY : [chars]:PHY is busy, [chars] failed
Explanation There was an error while accessing PHY.
Recommended Action 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 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%Y88E8K-1-RESET : MAC Still in Reset
Explanation An attempt was made to access the MAC while it was in reset.
Recommended Action 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 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%Y88E8K-3-SMI_IDLE : [chars]:SMI is in IDLE state
Explanation SMI should not be in idle state after an operation is requested.
Recommended Action 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 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%Y88E8K-1-START_FAILED : Unable to start Y88E8K chip
Explanation After initialization, the Y88E8K chip failed to start.
Recommended Action 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 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%Y88E8K-3-TOOBIG : [chars], packet too big ([dec]), src [enet], dst [enet]
Explanation The interface detects a packet that is larger than is defined by the MTU.
Recommended Action Check the other station's MTU setting. No action is required.
Error Message%Y88E8K-3-UNKNOWN_PHY : Interface [chars] has an unsupported PHY
Explanation The specified interface has an unsupported PHY chip on the board.
Recommended Action 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 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.