Cisco IOS CMTS Cable System Messages Guide
Chapter 3: Cisco uBR10012 Router Error Messages
Downloads: This chapterpdf (PDF - 464.0KB) The complete bookPDF (PDF - 2.58MB) | Feedback

Cisco uBR10012 Router Error Messages

Table Of Contents

Cisco uBR10012 Router Error Messages

BARIUM

C10KCHKPT

C10KGE

C10KJACKET

CLCAPPLICATION

CLCCCF520

CLCPLATFORM

CR10KLCCOREDUMP, UBRLCDUMP

IPRT

LCINFO

NETWORK_RP_API

RED

REQGRP

SANTANA

SPAWBCMTS

UBR10K

UBR10K_CLC_GE

UBR10K_REDUNDANCY

UBR10KTCC

UBRIFCON

UBRLCIFCON

WBCMTS_GIGE


Cisco uBR10012 Router Error Messages


This chapter lists the system error messages that are unique to the Cisco uBR10012 router. The messages are organized according to their FACILITY value, which indicates the subsystem on the Cisco uBR10012 router that is generating the message:

BARIUM

C10KCHKPT

C10KGE

C10KJACKET

CLCAPPLICATION

CLCCCF520

CLCPLATFORM

CR10KLCCOREDUMP, UBRLCDUMP

IPRT

LCINFO

NETWORK_RP_API

RED

REQGRP

SPAWBCMTS

UBR10K

UBR10K_CLC_GE

UBR10K_REDUNDANCY

UBR10KTCC

UBRIFCON

UBRLCIFCON

WBCMTS_GIGE


Tip Within each section, the messages are listed alphabetically, according to their MNEMONIC value.


BARIUM

This section describes error messages about the Barium hardware, which is the ASIC on the line cards that provides a high-speed interface to the backplane on the Cisco uBR10012 router, moving data between the backplane and packet memory.

%BARIUM-3-ERRINTR: Barium error interrupt detected intr_status=0x[hex].

Explanation    The Cisco IOS software detected an error in the Barium ASIC or driver software.

Recommended Action    Reset the line card with the hw-module reset command. If the problem continues, reset the card using the cable power off and cable power on commands. If the problem persists, verify that you are using released software on the Cisco CMTS. If so, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%BARIUM-3-NOTBARIUM: Slot [dec] device ID seen as [hex], expected [hex]

Explanation    The Cisco IOS software could not recognize the Barium ASIC on the specified card. This could indicate a transient software error, that the card has been incorrectly programmed at the factory, or a hardware failure on the card.

Recommended Action    Remove and reinsert the card. If that does not resolve the problem, reset the line card with the hw-module reset command. If the problem continues, reset the card using the cable power off and cable power on commands. If the problem persists, power down the system, remove and reinsert the card, and then reboot. If the problem continues, replace the card.

%BARIUM-3-OWNERR: [chars] packet buffer, Buffer ownership error, pak=0x[hex].

Explanation    The Cisco IOS software detected an error in the ownership descriptor in the specified packet that was processed by the Barium ASIC. This typically indicates either a transient software error or a hardware problem.

Recommended Action    Reset the line card with the hw-module reset command. If the problem continues, reset the card using the cable power off and cable power on commands. If the problem persists, remove and reinsert the card. If that does not resolve the problem, replace the card.

C10KCHKPT

This section describes system error messages that are related to the Checkpoint Facility (CF) subsystem, which manages the passing of messages from the Active to Standby interfaces, and which also handles sequencing and throttling, as needed during redundancy operations.

%C10KCHKPT-3-ADD_CLIENT: [chars]: chkpt_add_client error, client_id [dec] rc 
[dec] 

Explanation    The checkpoint client registration 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%C10KCHKPT-3-GET_BUFFER: [chars]: chkpt_get_buffer error, rc [dec] 

Explanation    The checkpoint buffer allocation 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%C10KCHKPT-3-GET_DATA_PTR: [chars]: chkpt_get_data_ptr error, ([chars]) 

Explanation    The checkpoint data pointer 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%C10KHHCT3-4-LINECARDFAILURE : LC reloaded in subslot [dec]/[dec] due to [chars] 

Explanation    The line card is reloaded.

Recommended Action    If this message recurs, 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/cgi-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.

%C10KCHKPT-3-SEND_MSG_BLOCKED: [chars]: chkpt_send_msg_blocked error, rc [dec] 

Explanation    The checkpoint "send blocked" message 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%C10KCHKPT-3-SEND_MSG_NONBLOCKED: [chars]: chkpt_send_msg_nonblocked error, rc 
[dec] 

Explanation    The checkpoint "send non-blocked" message 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%C10KCHKPT-3-STATUS_CALLBACK: [chars]: chkpt status callback received unexpected 
status code [dec] 

Explanation    The checkpoint status callback received unexpected code.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

C10KGE

This section describes Gigabit Ethernet subsystem messages.

%C10KGE-6-STATESYNC: Redundancy state synchronization failure slot [dec]/[dec] - 
([chars]) 

Explanation    A failure occurred while trying to synchronize GE redundancy state information.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

C10KJACKET

This section describes system messages pertaining to the session initiation protocol (SIP) jacket card.

%C10KJACKET-6-BAYINIT: Bay [dec] failed to initialize for jacket in slot [dec] 

Explanation    The SPA Bay data structures failed during initialization or activation.

Recommended Action    If this message recurs, 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%C10KJACKET-6-BAYMISMATCH: Bay number in message ([dec]) received ([chars]) 
greater than max number [dec] 

Explanation    The bay number in the message received exceeded the maximum number of bays.

Recommended Action    If this message recurs, 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%C10KJACKET-4-MSGVERSION: Incompatible message version with slot [dec] 

Explanation    The message version being sent by the line card is incompatible with the message version used by the RP.

Recommended Action    A microcode reload will solve the problem.

%C10KJACKET-6-SLOTMISMATCH: Slot number in message ([dec]) received ([chars]) 

Explanation    The slot number in the message received did not match the plug-in slot number.

Recommended Action    If this message recurs, 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%C10KJACKET-6-UNKNOWN: Unknown message ([dec]) received ([chars]) on slot [dec] 

Explanation    An unknown message was received from the line card.

Recommended Action    If this message recurs, 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

CLCAPPLICATION

This section describes system messages related to applications like DOCSIS that run on the cable line cards.

%CLCAPPLICATION-6-INCONSISTENTGATEDB: Gate entry, bin [dec], off [dec], is in use 
by [dec]. It will be replaced by [dec]. 

Explanation    This message appears when the PacketCable gate database on a cable interface line card and the gate database on the processor card are not the same. This indicates that the cable interface line card did not properly clean up its database, which in current Cisco IOS releases usually occurs after an N+1 HCCP switchover. After the switchover, the line card begins reusing these gates for new calls, displaying this message for each gate that was in effect at the time of the switchover.

Recommended Action    This message is expected after an N+1 HCCP switchover, during which existing PacketCable voice calls could be terminated. New PacketCable calls, however, can be made without problem. If this message appears without a switchover occurring, copy the error messages that appear, and use the show packetcable gate summary and the show tech-support commands to collect information about the problem. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

CLCCCF520

The following are the Cisco uBRMC5X20 line card error messages.

%CLCCCF520-6-BADJIBACCESS : [chars]: CCF can not access JIB2 FPGA to set/reset segment on table at [hex] for chan [dec] sid [dec]

Explanation    One of the three parameters must be invalid to set JIB2 segment on table.

Recommended Action    If this message recurs, 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/cgi-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.

%CLCCCF520-6-BADPAK : [chars]: CCF service flow [dec] seg_info has valid pak and pak hold flag is not set.

Explanation    CCF seg_info->pak is not NULL but hold flag is not set when a new segment is received.

Recommended Action    If this message recurs, 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/cgi-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.

%CLCCCF520-6-CCFDRAIN : [chars]: Too many hold segments [dec] [[dec]] force flush.

Explanation    The hardware sends traffic burst or segment missing ahead of CCF happened.

Recommended Action    If this message recurs, 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/cgi-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.

%CLCCCF520-6-CCFFLOW : [chars]: Service flow [dec] updating CCF rule table from interrupt context.

Explanation    CCF rule update should be routed from the process. The request is bridged through CCF process.

Recommended Action    If this message recurs, 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/cgi-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.

CLCPLATFORM

This section describes system messages related to the cable line card platform software.

%CLCPLATFORM-3-DDR_ERROR : [chars] = [hex]

Explanation    DDR single or multiple bit errors occurred.

Recommended Action    If this message recurs, 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%CLCPLATFORM-3-ERRRPLCCFGSYNC: HCCP [dec] [dec] [chars] rp-lc configure sync 
error: [chars]. 

Explanation    There is a problem synchronizing the HCCP RP and line card configuration.

Recommended Action    If this message recurs, 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%CLCPLATFORM-3-LBC_ERROR : [chars] = [hex] 

Explanation    LOCAL BUS error occurred when accessing a device.

Recommended Action    If this message recurs, 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%CLCPLATFORM-3-LBC_ERROR_MSG: LBC status register = [hex] and LBC transfer error 
attributes register = [hex] 

Explanation    LOCAL BUS error occurred when accessing a device and these are the status and transfer error attributes register.

Recommended Action    If this message recurs, 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%CLCPLATFORM-3-NOMEM: [chars] 

Explanation    System memory is full and is not available for allocation.

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/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, issue the show tech-support command to gather data that may help identify the nature of the error and 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.

%CLCPLATFORM-3-UNKNOWPLAT: Unknown Platform ID, [dec].

Explanation    The Cisco uBR10012 router does not recognize the line card that is in the specified slot.

Recommended Action    Verify that you are using released software on the Cisco uBR10012 router that supports this particular line card. If so, reset the line card with the hw-module reset command, or using the cable power off and cable power on commands. If the problem persists, copy the error message exactly as it appears, and use the show tech-support command to collect information about the problem. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%CLCPLATFORM-6-L2C_SBECC: Single-bit ecc occured in L2Cache - total errors - 
sbecc: [dec] multi-sbecc: [dec] l2captdatahi: [hex], l2captdatalo: [hex] 
l2erraddr: [hex], l2erreaddr: [hex] l2errattr: [hex], l2captecc: [hex] l2errdet: 
[hex] 

Explanation    Single-bit correctable error has occurred in L2Cache

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/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, issue the show tech-support command to gather data that may help identify the nature of the error and 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.

CR10KLCCOREDUMP, UBRLCDUMP

This section describes error messages generated by the subsystem that manages core dumps for line cards in the Cisco uBR10012 router. These messages can appear with either the facility of CR10KLCCOREDUMP or UBRLCDUMP.

%CR10KLCCOREDUMP-3-BADCLOSE: Can't close slave core socket for slot [dec]/[dec] 
%UBRLCCOREDUMP-3-BADCLOSE: Can't close slave core socket for slot [dec]/[dec]

Explanation    The system just finished dumping a core file from a line card. It tried to close this file on the remote system and failed.

Recommended Action    Debug the card's network connections and examine user privileges.

%CR10KLCCOREDUMP-3-BADOPEN: Can't open slave core socket for slot [dec]/[dec] 
%UBRLCCOREDUMP-3-BADOPEN: Can't open slave core socket for slot [dec]/[dec]

Explanation    The system wants to dump a core file to a remote system, but it is unable to open the remote file.

Recommended Action    Check to make sure the remote system is accessible and the protocol is set up correctly.

%UBRLCDUMP-3-BADSLOTNUMBER: Refusing dump because card slot number is out of 
bounds for card [dec]/[dec].

Explanation    The PRE processor has refused this coredump because the slot number of the requested card is out of bounds.

Recommended Action    Enable IPC debug messages and check for malformed packets.

%CR10KLCCOREDUMP-3-BADWRITE: Can't write [chars] to slave core socket for slot 
[dec]/[dec] 
%UBRLCCOREDUMP-3-BADWRITE: Can't write [chars] to slave core socket for slot [dec]/[dec]

Explanation    The system is trying to write a core dump file to a remote system. The file was opened, but an error occurred during a write to the file.

Recommended Action    Verify that disk space is available on the remote server. Use the ping command to verify that the PRE module has network connectivity to the remote server.

%UBRLCDUMP-3-CRASHINFO_DUMP: System Crashed, Trying to send Crashinfo first to 
remote server....

Explanation    The system crashed because of an exception error, but a crashinfo file is being generated before the system restarts.

Recommended Action    Verify that you are using released software on the Cisco CMTS. If so, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%CR10KLCCOREDUMP-2-EOM: Cannot allocation memory for [chars] 
%UBRLCCOREDUMP-2-EOM: Cannot allocation memory for [chars]

Explanation    The system cannot allocate memory for the core dump subsystem.

Recommended Action    Display the running configuration with the show running-config command, and look for any commands that might be allocating large amounts of memory for specific buffers, such as the logging buffered command. Add more memory to the PRE module.

%UBRLCDUMP-3-FAILEDMEMALLOC: Unable to allocate memory to read crashinfo from 
flash.

Explanation    The system failed to open the most recent crashinfo file in Flash memory because it could not allocate sufficient memory for the file's buffers.

Recommended Action    Display the running configuration with the show running-config command, and look for any commands that might be allocating large amounts of memory for specific buffers, such as the logging buffered command. Verify that you are using released software on the Cisco CMTS. If so, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%CR10KLCCOREDUMP-3-ILLMSG: Coredump message received from slot [dec]/[dec] (not 
in dump state)
%UBRLCCOREDUMP-3-ILLMSG: Coredump message received from slot [dec]/[dec] (not in dump state)

Explanation    A core dump message arrived at the PRE module from a line card that is not in a coredump state and therefore should not be dumping core.

Recommended Action    Gather information about the state of line cards and file a bug.

%CR10KLCCOREDUMP-3-ILLNVGEN: Illegal call to cr10k_rp_lc_cfg_coredump_nvgen 
%UBRLCCOREDUMP-3-ILLNVGEN: Illegal call to cr10k_rp_lc_cfg_coredump_nvgen

Explanation    The NVGEN routine was called, but nvgen was not set.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%CR10KLCCOREDUMP-3-ILLTD: Testdump only valid on line cards (not allowed on PREs) 
%UBRLCCOREDUMP-3-ILLTD: Testdump only valid on line cards (not allowed on PREs)

Explanation    You cannot run a line card coredump test on a PRE module.

Recommended Action    Do not use these commands on the PRE module, but only on line cards.

%CR10KLCCOREDUMP-6-LERP: Cannot configure linecard exceptions for [chars] PRE 
%UBRLCCOREDUMP-6-LERP: Cannot configure linecard exceptions for [chars] PRE

Explanation    The exception linecard commands can only be used to configure exceptions on a line card, not on a PRE module.

Recommended Action    Use the exception command without specifying a linecard to configure core dumps for the PRE module.

%CR10KLCCOREDUMP-3-NOMSG: No message on queue 
%UBRLCCOREDUMP-3-NOMSG: No message on queue

Explanation    A core dump message from a line card that should not be dumping core arrived at the PRE module.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%CR10KLCCOREDUMP-3-NOPROC: Unable to create data/handling process 
%UBRLCCOREDUMP-3-NOPROC: Unable to create data/handling process

Explanation    The system wants to write a core dump file to a remote system but it is unable to start a process to dump the file.

Recommended Action    Display the running configuration with the show running-config command, and look for any commands that might be allocating large amounts of memory for specific buffers, such as the logging buffered command. Gather information about the number of processes running and amount of memory in the system and file a bug.

%CR10KLCCOREDUMP-3-NOPROC: Unable to create core dump process 
%UBRLCDUMP-3-NOPROC: Unable to create core dump process

Explanation    The system tried to write a core dump file to a remote system but it could not start a process to dump the file.

Recommended Action    Display the running configuration with the show running-config command, and look for any commands that might be allocating large amounts of memory for specific buffers, such as the logging buffered command. Gather information about the number of processes running and amount of memory in the system and file a bug.

%CR10KLCCOREDUMP-3-NOQUEUE: Cannot create queue to receive dump packets for slot 
[dec]/[dec] 
%UBRLCCOREDUMP-3-NOQUEUE: Cannot create queue to receive dump packets for slot [dec]/[dec]

Explanation    The system is trying to write a core dump file to a remote system. It could not create a queue to hold dump data coming from the line cards.

Recommended Action    Display the running configuration with the show running-config command, and look for any commands that might be allocating large amounts of memory for specific buffers, such as the logging buffered command. Add memory.

%UBRLCDUMP-3-OPENFLASHFILE: Unable to open flash crashinfo file on bootflash to 
READ: [chars] 

Explanation    The system failed to open the most recent crashinfo file in Flash memory.

Recommended Action    Verify that you are using released software on the Cisco CMTS. If so, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%UBRLCDUMP-3-READFLASHFILE: Unable to read flash crashinfo file. 

Explanation    The system failed to read the most recent crashinfo file in Flash memory.

Recommended Action    Verify that you are using released software on the Cisco CMTS. If so, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%UBRLCDUMP-3-REFUSAL: Refusing core dump for card [dec]/[dec]. 

Explanation    The PRE processor card has refused this dump for the particular card because the exception-slave command was not configured for this card. This message could also be displayed if the TFTP server refused the file transfer because of insufficient file access rights.

Recommended Action    Check that the proper exception-slave command has been given on the PRE processor. Verify that the destination directory and file on the TFTP server are configured with read-write access rights.

%UBRLCDUMP-3-SIZEFLASHFILE: Unable to get size of flash crashinfo file.

Explanation    The system was unable to obtain the size of the most recent crashinfo file in Flash memory.

Recommended Action    Verify that you are using released software on the Cisco CMTS. If so, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%CR10KLCCOREDUMP-4-TIMEOUT: [chars] (major [dec], minor [dec]) 
%UBRLCCOREDUMP-4-TIMEOUT: [chars] (major [dec], minor [dec])

Explanation    The system is trying to write a core dump file, but the PRE module timed out waiting for data from the line card.

Recommended Action    Gather information about the line card and file a bug.

%UBRLCDUMP-3-TOOLONGFILENAME: Filename for coredump file is too long for slot 
[dec]/[dec]. 

Explanation    The filename given in the exception-slave command is too long for the core dump file.

Recommended Action    Use the exception-slave command to specify a new coredump filename that has a maximum filename length, including path, to 32 characters or less.

IPRT

This section describes system messages related to IP Routing.

%IPRT-3-BADRFREG: Unable to register IP Routing as a client of RF. 

Explanation    This is a severe IP Routing NSF error.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

LCINFO

The following are line card crash information subsystem error messages that have been added for the Cisco uBR10012 router. Other LCINFO error messages are documented in the main Cisco IOS System Error Messages documentation set.

%LCINFO-3-NOLCHANGPROC: Failed creating line card hang cure process

Explanation    The system could not create a hang cure process for checking prolonged down states on the line card, which should not occur during normal operations. This failure should occur only during initialization, and if it occurs during other times, it is probably due to a software defect or hardware failure.

Recommended Action    Reboot the system. If the condition continues on subsequent reloads of the system, verify that you are running released software on the Cisco uBR10012 router. If this does not resolve the problem, upgrade the router to the latest Cisco IOS Release 12.2 BC release. If the problem persists, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%LCINFO-4-LCHUNG: Slot [ [dec]/[dec] ] down on last [dec] checks. HW RESET # [dec] 

Explanation    The PRE module generates this error message when it detects that a line card has been hung and unresponsive for more than 150 seconds, and has therefore issued a hardware reset for that slot. This can occur when the line card becomes hung in a Cisco IOS operation and is not able to recover, or when the ROMMON gets stuck during the TFTP bootload.

Recommended Action    This will occur if you remove all working TCC+ cards from the Cisco uBR10012 chassis—you must have at least one working TCC+ card in the system for the cable interface line cards to function correctly. If the router does have at least one working TCC+ card, verify that the line card is fully inserted into the card slot, and if necessary, remove and reinsert the line card. If the problem seems related to access lists, verify that you are running Cisco IOS Release 12.2(8)BC2 or later released software on the router. If the problem persists, check the memory on the line card for possible failure or error, and replace the memory as necessary. If the problem continues, replace the line card, and report this problem with as much information as possible about the line card.

NETWORK_RP_API

This section describes messages related to the network redundancy feature API.

%NETWORK_RP_API-6-IDB_TRANSITIONS_PENDING: Switchover terminated with [dec] 
transitions pending after there was no transition activity for [dec] seconds 

Explanation    The system terminated the switchover IDB transition phase with a number of IDB transitions still pending, because no switchover related IDB transitions were logged during the specified time interval. Some connected routes may experience a temporary loss of traffic.

Recommended Action    No action is required.

RED

This section describes system messages related to redundancy.

%RED-3-CHKPTADDCLIENT: Check Point Client [dec] Add  Failed - [dec] 

Explanation    The checkpoint message client 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RED-3-CHKPTALLOC: Check Point Message Allocation Failed - [dec] 

Explanation    The checkpoint buffer allocation 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RED-3-CHKPTGETDATAPTR: Check Point Get Data Pointer Failed 

Explanation    The checkpoint message had an internal error with the data pointer.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RED-3-CHKPTINVALIDDATA: Check Point Client has invalid data 

Explanation    The checkpoint message had invalid data.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RED-3-CHKPTMSGCOPY: Check Point Message Copy Failed 

Explanation    The checkpoint message copy had an internal error.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RED-3-CHKPTMSGSIZE: Check Point Message Size is Zero! 

Explanation    The checkpoint message size is zero.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RED-3-CHKPTRIMRCSACTIVE: Check Point RIM RCS ACTIVE Failed 

Explanation    The checkpoint process had an RIM RCS active error.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RED-3-CHKPTSENDFAIL: Check Point Message Send - Unsuccessful delivery 

Explanation    The checkpoint message send was unsuccessful.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RED-3-CHKPTSENDMSG: Check Point Message Send  Failed - [dec] 

Explanation    The checkpoint message send 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RED-3-DATADECODE: Decode Data Descriptor for data type Failed 

Explanation    The Decode Data descriptor 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RED-3-DATAENCODE: Encode Data Descriptor for data type  [chars] Failed 

Explanation    The Encode Data Descriptor 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RED-5-REDCHANGE: EHSA Register changed Prev - [hex]h, Current - [hex]h 

Explanation    The Peer RP was changed through the EHSA Register.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RED_MODE-3-NO_DEREGISTER: Could not deregister plugin for redundancy mode [chars] 

Explanation    At system initialization, the plug-in that describes the capabilities of this redundancy mode could not be deregistered with the redundancy mode client.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RED_MODE-4-NO_MODE_IN_CLI: Redundancy mode not defined in configuration. Please 
add to configuration 

Explanation    The redundancy mode was not defined at the top of the configuration. Therefore, the system boot will take longer. The system reads through the configuration to attempt to find the redundancy mode, after which it will determine that the default redundancy mode should be used.

Recommended Action    Explicitly write the configuration to NVRAM, so the redundancy mode is discovered at an early stage.

%RED_MODE-3-NO_REGISTER: Could not register plugin for redundancy mode [chars] 

Explanation    At system initialization, the plug-in that describes the capabilities of this redundancy mode could not be registered with the redundancy mode client. This redundancy mode may not be available as an option from the parser.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%REDUNDANCY-3-FSM_ERROR: [chars], Error Code: [dec] 

Explanation    A REDUNDANCY Finite State Machine (FSM) error occurred.

Recommended Action    Copy the system configuration along with any other relevant information. If this message recurs, 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

REQGRP

This section describes the error messages generated by the Request Interprocess Communication subsystem that is running on the line cards.

%REQGRP-3-DSPTCHQ: [chars]

Explanation    The initialization of the dispatch IPC queue 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

If the error happens on cable interface line card, try to reset the line card. If the error happens on RP, try to do a PRE switchover.

%REQGRP-6-NBLKEVT_Q_FULL: Nonblocking IPC event queue full ([dec] events)

Explanation    The non-blocking IPC event queue is filled up and flushed to avoid buffer starvation.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%REQGRP-3-NBLKQ: [chars]

Explanation    Non-blocking IPC related queue or process 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). Also perform a search of the Bug Toolkit (http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

If the error occurs on the cable interface line card, try to reset the line card to restore normalcy. If the error happens on RP, try to do a PRE switchover to restore normalcy.

%REQGRP-3-NOSESSION: Unable to create client object for client [dec], entity [dec] 
(slot [dec]/[dec]): [chars]

Explanation    The CMTS has failed to create a Cisco uBR10012 router IPC session object.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%REQGRP-3-REQOP: IPC request/response [int] (slot [int]/[int]): [chars]

Explanation    Operational errors occurred while processing an IPC request or response.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%REQGRP-3-SYSCALL: System call for command [int] (slot[int]/[int]) : [chars] 
(Cause: [chars])

Explanation    An IPC kernel system call error has occurred.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%REQGRP-3-UNKCONN: Unknown connection state [dec] from callback for client [dec], 
entity [dec] (slot [dec]/[dec])

Explanation    An unsupported connection state has been received in callback. This is a software error.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%REQGRP-6-UNKLCREQ: Received unknown IPC request ([dec]) from [dec]/[dec]

Explanation    An unknown line card request was received.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%REQGRP-6-UNKVER: Received IPC with unsupported version, ([dec])

Explanation    The version of the request is newer than supported.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

SANTANA

The following are SANTANA messages:

%SANTANA-3-DS_JIB_ERROR: DS JIB Santana FPGA Error detected and corrected 

Explanation    DS JIB Santana FPGA error was corrected.

Recommended Action    If this message recurs, 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

SPAWBCMTS

This section describes system messages pertaining to the Wideband SPA.

%SPAWBCMTS-3-HWINITFAILED: Error while initializing wideband group interface 
[chars] 

Explanation    A Wideband group interface initialization error has occurred.

Recommended Action    Remove the SPA from the bay and re-insert it again into the same bay or a different bay in the jacket card and check whether the SPA is coming online after a while using the show controller modular-cable slot/subslot/bay brief command.

%SPAWBCMTS-3-INVALIDDATA: Invalid information [chars] received by wideband 
software routine 

Explanation    The Wideband SPA software module was passed invalid information.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%SPAWBCMTS-4-SFP_LINK_LOST: [chars], port [dec] link changed state to down 

Explanation    The link status is down on the SPA SFP interface.

Recommended Action    This error message is displayed when the SPA gigabit ethernet link goes down. However, you can check the SFP and the fiber cable for any faults.

%SPAWBCMTS-4-SFP_LINK_OK: [chars], port [dec] link changed state to up 

Explanation    Link status is up on the SPA Small Form Factor Pluggable (SFP) interface.

Recommended Action    This error message is displayed when the SPA gigabit ethernet link becomes active. No action is required.

%SPAWBCMTS-4-SFP_MISSING: [chars], [chars] SFP missing from port [dec] 

Explanation    The Small Form-Factor Pluggable (SFP) module is missing from the SPA interface.

Recommended Action    This error message is displayed when the SPA gigabit ethernet SFP is removed. Check whether the SFP is present. If it is already installed, remove and reinsert it firmly.

%SPAWBCMTS-4-SFP_OK: [chars], [chars] SFP inserted in port [dec] 

Explanation    The Small Form-Factor Pluggable (SFP) module is inserted into the SPA interface.

Recommended Action    This error message is displayed when you insert the SPA gigabit ethernet SFP. No action is required.

%SPAWBCMTS-3-SPAHANDLERFAIL: The SPA was unable to process/handle the received 
data 

Explanation    The wideband SPA was unable to process or handle the received data.

Recommended Action    Remove the SPA from the bay and re-insert it again into the same bay or a different bay in the jacket card and check whether the SPA is coming online, after a while using the show controller modular-cable slot/subslot/bay brief command.

UBR10K

The messages in this section are generated by systems that are running on the main processor in the Cisco uBR10012 router.

%UBR10K-0-CLI_CMD: CMTS([dec]/[dec]), [chars] failed 

Explanation    This message most likely indicates a software failure.

Recommended Action    Verify that you are running released software on the Cisco uBR10012 router. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10K-0-CLI_CONFIG: CMTS([dec]/[dec]/[dec]), schrp_cli_cmd failed in [chars] 

Explanation    This message most likely indicates a software failure.

Recommended Action    Verify that you are running released software on the Cisco uBR10012 router. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10K-2-CLI_UNSUPPORTED_CMD: cable modem <ipaddr/macaddr> cmd not supported in 
Schooner 

Explanation    The Cisco uBR10012 router does not support the cable device access-group, cable host access-group, and cable modem access-group commands. The other forms of these commands are supported only in Cisco IOS Release 12.2(4)BC1 or later software releases.

Recommended Action    No action is needed.

%UBR10K-4-HW_ASSIST_WDOG_FAILURE: Send lchung packet to Card([dec]/[dec]) failed 

Explanation    Sending lchung packet to line card failed due to low buffer.

Recommended Action    If this message recurs, 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10K-4-HW_ASSIST_WDOG_TIMEOUT: Card([dec]/[dec]) HW assist watchdog timeout

Explanation    PRE is sending lchung packet to line card in extended time. This could be because the hardware assist watchdog is not supported on the line card or is disabled.

Recommended Action    If this message recurs, 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10K-4-ROMMON_UPDATE_POSTFALPOS_MUTED: Linecard Slot [dec]/[dec] ROMMON update 
from [dec] to [dec] is temporarily disabled due to a limit on consequtive attempts. 
The card may not have the latest firmware 

Explanation    ROMMON update is temporarily blocked to prevent multiple reloads.

Recommended Action    Wait 10 minutes and then reset the line card to restart ROMMON upgrade. Capture the logs. 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10K-6-ACFE_REJECTION: ACFE has rejected QoS queue for service flow [int] on 
[chars], MAC_addr [enet], min_rate [int] kbps, rej_code [dec] 

Explanation    ACFE has rejected this CIR flow due to heavy CIR reservation on this or adjacent interfaces.

Recommended Action    This issue occurs mostly on a highly overloaded interface. If it persists on an interface, provision more RF channels.

%UBR10K-6-ACFE_REJECTION_MCAST: ACFE has rejected QoS queue for service flow [int] 
on [chars], Group [chars], Source [chars], min_rate [int] kbps, rej_code [dec] 

Explanation    ACFE has rejected this CIR flow due to heavy CIR reservation on this or adjacent interfaces.

Recommended Action    This issue occurs mostly on a highly overloaded interface. If it persists on an interface, provision more RF channels.

%UBR10K-6-CM_INCONSISTENCY: CM state inconsistency [enet](msgp [enet]), sid [dec] 
([dec]), mac state [dec], hwidb [chars]

Explanation    The CMTS received INIT_CM for an online CM. The line card and the processor card have different CM states.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10K-6-COMPAT_IGNORED: OIR compatibility is disabled because [chars]

Explanation    OIR compatibility is disabled because of a conflict with another feature. The OIR compatibility is not supported in this configuration.

Recommended Action    Disable the OIR compatibility or the conflicting feature.

%UBR10K-6-COMPAT_NO_CFG: OIR compatibility does not support the [chars] in slot 
[dec]/[dec]. [chars]

Explanation    A line card that is supported by the OIR compatibility feature is not supported in the specified slot or subslot.

Recommended Action    This is most likely a software problem. The OIR compatibility for the given slot or subslot should be disabled until the problem is resolved.

%UBR10K-3-FPSUBINIT: Unable to create subinterface [chars] for hw interface 
[chars] in the fast path 

Explanation    The system was unable to create the cable subinterface data structures in the fast path on the processor.

Recommended Action    Verify that you are running the latest version of released Cisco IOS software, and upgrade to the latest Cisco IOS 12.2 BC release, as necessary. If the problem persists, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error, especially the running configuration and amount of memory. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10K-1-INITFAIL: Schooner subsystem init fails:([chars]) 

Explanation    The Cisco uBR10012 subsystem could not initialize. This message most likely indicates a software error.

Recommended Action    Verify that you are running released software on the Cisco uBR10012 router. If so, reload the processor card. Otherwise, upgrade to the latest Cisco IOS Release 12.2 BC software release. If this does not resolve the problem, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10K-1-INVALID_DIVHDR: Invalid diversion hdr on pkt: cause [dec], channel 
0x[hex], length [dec] 

Explanation    The processor received a corrupt diverted packet from the cable interface line card.

Recommended Action    Verify that you are running released software on the Cisco uBR10012 router. If so, reload the processor card. Otherwise, upgrade to the latest Cisco IOS Release 12.2 BC software release. If this does not resolve the problem, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10K-1-INVALIDPRIMSID: Dropping punted pkt from sid [dec] prim sid [dec] src 
[enet] hw [chars] 

Explanation    The processor received a corrupt packet from the indicated source address and cable interface line card. This packet was dropped because it referenced an invalid primary service ID (SID).

Recommended Action    Verify that you are running released software on the Cisco uBR10012 router. If so, reload the processor card. Otherwise, upgrade to the latest Cisco IOS Release 12.2 BC software release. If this does not resolve the problem, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10K-1-INVALIDSID: Dropping punted pkt from sid [dec] src [enet] hw [chars] 

Explanation    The processor received a corrupt packet from the indicated source address and cable interface line card. This packet was dropped because it referenced an invalid service ID (SID).

Recommended Action    Verify that you are running released software on the Cisco uBR10012 router. If so, reload the processor card. Otherwise, upgrade to the latest Cisco IOS Release 12.2 BC software release. If this does not resolve the problem, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10K-1-JTAG_POWCYCLE: Power cycle slot [dec]/[dec] 

Explanation    Recover from 2020 power sequency error. This error message is observed when there is a power cycle request issued for a line card during initialization of the bcm3140 US-Phy.

Recommended Action    If it stops after one or a few power cycles, the hardware is recovered fully. If this error is observed continuously, 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/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, issue the show tech-support command to gather data that may help identify the nature of the error and 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.

%UBR10K-0-LCPOWEREDOFF: Linecard Slot [dec]/[dec] device has reached critical 
temperature [dec], Linecard powered off, Critical Threshold [dec] Last Temperature 
[dec] 

Explanation    Line card temperature value is critical.

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/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, issue the show tech-support command to gather data that may help identify the nature of the error and 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.

%UBR10K-4-MSGVERSION: Incompatible message version with slot [dec] 

Explanation    This message indicates an incompatibility between the message version being sent by the line card and the message version used by the processor card. This type of incompatibility could happen if the processor card and line card are using different versions of the Cisco IOS software, which typically would occur because of an OIR of the main processor card.

Recommended Action    Use the microcode reload command to reload the microcode on the processor.

%UBR10K-3-QALLOCFAIL: Failure to allocate QoS queue for service flow [dec], CM 
[enet] 

Explanation    The system has run out of PXF queues for processing service flows.

Recommended Action    Display the running configuration with the show running-config command, and look for any commands that might be allocating large amounts of memory for specific buffers, such as the logging buffered command. Increase memory on the processor card. If that is not possible or does not help, reduce the number of cable modems using this router.

%UBR10K-1-POWCYCLE: Power cycle slot [dec]/[dec] 

Explanation    The system put the indicated Cisco uBR-MC16S cable interface line card through a power cycle so that it could recover from a hardware initialization failure. This could happen during an HCCP N+1 (1:n) switchover, for example.

Recommended Action    If this persists with a Cisco uBR-MC16S card, replace the card. If this happens to another type of line card, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10K-0-SNMP_SET_IPC: Schooner SNMP SET([dec]/[dec]), [chars] failed 

Explanation    An SNMP SET operation failed, either because of an interprocess communications (IPC) failure or because of a line card failure.

Recommended Action    Remove and reinsert the indicated line card. If this does not correct the problem, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10K-1-UNKEVT: Schooner subsystem unknown event:([dec]) in [chars], for 
interface [chars] 

Explanation    The processor on the Cisco uBR10012 router received an unknown event type.

Recommended Action    This could happen if a line card was using newer Cisco IOS software than the processor card. If so, upgrade the router to the latest Cisco IOS software release and reload the router. If this does not correct the problem, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10K-1-UNKREQ: Schooner subsystem unknown request:([dec]) 

Explanation    The processor on the Cisco uBR10012 router received an unknown request type.

Recommended Action    This could happen if a line card was using newer Cisco IOS software than the processor card. If so, upgrade the router to the latest Cisco IOS software release and reload the router. If this does not correct the problem, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10K-1-UNKVECT: Schooner subsystem unknown vector:([dec]) 

Explanation    The processor on the Cisco uBR10012 router received an unknown vector type.

Recommended Action    This could happen if a line card was using newer Cisco IOS software than the processor card. If so, upgrade the router to the latest Cisco IOS software release and reload the router. If this does not correct the problem, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10K-3-VOLTABNORMAL: The PEM [dec] voltage value [dec] is abnormal 

Explanation    The Cisco uBR10012 router is measuring abnormal voltage coming into the chassis from the Power Entry module (PEM).

Recommended Action    Check the power source that is providing power to the PEMs to ensure the source is providing the correct voltage. If the power source is providing the proper voltage, replace the indicated PEM. If this does not correct the problem, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10K-6-HCCP_CM_INCONSISTENCY: CM sync received [enet](msgp [enet]), sid [dec] 
([dec]), mac state [dec], hwidb [chars] 

Explanation    A synchronization message on the secondary PRE was received for a mismatched entry.

Recommended Action    This problem should resolve by itself. If it persists, 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10K-4-INVALID_PKT_FILTER_GROUP: Invalid [chars]_filter_group [int], IP_addr = 
[IP_address] 

Explanation    An invalid packet filter group is specified in the CM configuration file.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10K-6-STATESYNC: Redundancy state synchronization failure slot [dec]/[dec] - 
([chars]) 

Explanation    An error has occurred while trying to synchronize GE state information.

Recommended Action    If this message recurs, c.opy 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10K-6-STDBY_CM_INCONSISTENCY: CM sync received [enet](msgp [enet]), sid [dec] 
([dec]), mac state [dec], hwidb [chars] 

Explanation    A synchronization message was received for a mismatched entry in its cable modem database.

Recommended Action    This problem should resolve by itself. This can be verified by examining the output of show interface cable<x/y/z> modem 0 rp | include mac-address on the secondary PRE console and comparing its output with that of show interface cable<x/y/z> modem 0 rp | include <mac-address> on the primary PRE console. If a mismatch is found between the two outputs, 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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

UBR10K_CLC_GE

The following are line card GigE interface error messages:

%UBR10K_CLC_GE-3-SW_CTRL_ERR: slot [dec]/[dec] controller [dec]: [chars] 

Explanation    Internal software error in cable interface line card GigE interface.

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/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, issue the show tech-support command to gather data that may help identify the nature of the error and 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.

%UBR10K_CLC_GE-3-SW_SLOT_ERR: slot [dec]/[dec]: [chars] 

Explanation    Internal software error in cable interface line card GigE interface.

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/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, issue the show tech-support command to gather data that may help identify the nature of the error and 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.

UBR10K_REDUNDANCY

The messages in this section describe errors that occur during the operation of Route Processor Redundancy Plus (RPR+) redundancy on the Cisco uBR10012 universal broadband router.

%UBR10K_REDUNDANCY-3-CHKPT_INTERNAL: Internal PRE checkpointing error [chars]

Explanation    An internal software error occurred within the PRE module's Checkpoint Facility (CF) code, which handles the messaging between the PRE module and the line cards.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Issue the show cable clock and show tech-support commands to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10K_REDUNDANCY-4-MSGVERSION: Incompatible message version with slot [dec] 

Explanation    This message indicates an incompatibility between the message version being sent by the line card and the message version used by the PRE module processor card. This type of incompatibility could happen if the processor card and line card are using different versions of the Cisco IOS software, which typically would occur because of an OIR of the main processor card.

Recommended Action    Reload the microcode on the line card to resolve the problem.

%UBR10K_REDUNDANCY-4-RP_HA_STDBY_INCONSISTENT: Standby PRE dropping inconsistent 
sync messages, [chars] [chars] 

Explanation    An inconsistency was detected within the PRE configuration and data synchronization code. This can occur under normal situations if a cable line card is reset while the standby PRE is still coming up. Further debugging can be turned on to dump contents of inconsistent packets.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

UBR10KTCC

The messages in this section concern the operation of the Timing Communication Control Plus (TCC+) card.

%UBR10KTCC-5-ACTIVE_TCC: TCCplus card [dec]/[dec] is active with [chars] as clock 
reference 

Explanation    The indicated TCC+ or DTCC card became active.

Recommended Action    No action is needed.

%UBR10KTCC-1-BADCLK: Cable Line Card [dec]/[dec] reports Bad Clock Status for 
TCCplus card in [dec]/1 

Explanation    An error occurred in the clock signal when it was received on the BackPlane.

Recommended Action    Check that the reference sources are correctly plugged into the proper connectors on the TCC+ or DTCC card. Verify that the reference sources are providing a valid signal. If this does not correct the problem, replace the TCC+ or DTCC card. If the problem persists, copy the error message exactly as it appears on the console or in the system log. Issue the show cable clock and show tech-support commands to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10KTCC-4-BADCLK_STANDBY_TCC: No available external clock reference on the 
standby DTCC card 

Explanation    The clock status of the standby DTCC reference is lost or bad.

Recommended Action    Check that the reference sources are correctly plugged into the proper connectors on the DTCC card. Verify that the reference sources are providing a valid signal. If this does not correct the problem, replace the DTCC card.

If the problem persists, copy the error message exactly as it appears on the console or in the system log. Issue the show cable clock and show tech-support commands to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10KTCC-1-BADTCC: TCCplus card in [dec]/1 put under maintenance due to: [chars] 

Explanation    The system detected a possible hardware problem with the indicated TCC+ or DTCC card and put the card into maintenance mode.

Recommended Action    Remove the indicated TCC+ or DTCC card and reinstall it. If this does not correct the problem, replace the TCC+ or DTCC card. This error message can occasionally occur when the TCC+ or DTCC card is manually reset using the hw-module reset command. If so, upgrade the Cisco uBR10012 router to Cisco IOS Release 12.2(8)BC1 or a later release.

%UBR10KTCC-1-BLKCMD: Schooner System IPC failure for TCCplus card 

Explanation    A blocking command sent to the TCC+ or DTCC card failed. This typically indicates that the TCC+ or DTCC card was not fully initialized and ready when the processor sent the command to it.

Recommended Action    This error message can occasionally occur during system power-on and reset, or when the TCC+ or DTCC card is manually reset using the hw-module reset command. If this is the case, the error message can be ignored as long as the system is operational. If the message occurs repeatedly at other times, remove the indicated TCC+ or DTCC card and reinstall it. Also, upgrade the Cisco uBR10012 router to Cisco IOS Release 12.2(11)BC2 or later release. If this does not correct the problem, replace the TCC+ or DTCC card.

If the problem persists, copy the error message exactly as it appears on the console or in the system log. Issue the show cable clock and show tech-support commands to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10KTCC-6-CHG_CLK_REF: Clock reference source changed to [chars], TCCplus card 
[dec]/[dec] 

Explanation    The clock reference source has been changed, either because
1) LOS of previous source reference (for TCC+ card).
2) Primary / Secondary external reference (T1) of TCC+ active card is now available.
3) Manual mode configuration command for DTCC card.

Recommended Action    Check reference source (TCC+) and Information only (DTCC) cards.

%UBR10KTCC-4-DTCC_CLOCK_WARNING: Active DTCC in slot [dec]/[dec] doesn't have the 
latest firmware [hex]. This may impact system behavior in selected clock mode

Explanation    Active DTCC card does not have the latest firmware

Recommended Action    If Cisco CMTS does not contain dual DTCC cards, then the firmware will not be auto-upgraded. Perform the manual upgrade using the cable clock update command.

%UBR10KTCC-4-DTCC_OLD_FW: DTCC slot [dec]/[dec] FPGA upgrade needed. Card is 
outdated and cannot be auto-upgraded. Main EPLD version is [hex] (minimum 
requirement is [hex]) 

Explanation    The DTCC card has old firmware and cannot be upgraded.

Recommended Action    Replace the TCC card.

%UBR10KTCC-4-DTCC_OLD_HW: DTCC slot [dec]/[dec] FPGA upgrade needed. Card is 
outdated and cannot be auto-upgraded. H/W revision is [hex] (minimum requirement 
is [hex]) 

Explanation    The DTCC card has old hardware and cannot be upgraded.

Recommended Action    Replace the TCC card

%UBR10KTCC-5-DTCC_UPGRADE: DTCC card in slot [dec]/[dec] will be upgraded from 
[hex] to version [hex]. PLEASE DO NOT INTERRUPT DURING THE UPGRADE PROCESS. 
Estimated upgrade time [dec] minutes.

Explanation    DTCC card upgrade information.

Recommended Action    No action is needed.

%UBR10KTCC-3-DTIERR: DTI interface Error code [dec] function [chars] 

Explanation    An error value is returned when the DTI component function is invoked.

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/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, issue the show tech-support command to gather data that may help identify the nature of the error and 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.

%UBR10KTCC-6-DTIPORTCLIENT: DTCC slot [dec]/[dec] port [dec] DTI client status 
changed to [chars] [chars] 

Explanation    There is a change in the client status of DTI port.

Recommended Action    Check the DTI link/cable.

%UBR10KTCC-6-DTIPORTPHYS: DTCC slot [dec]/[dec] port [dec] DTI physical status 
changed: Link status:[chars], frame error rate: [chars] 

Explanation    There is a change in the frame error rate or link status of DTI link.

Recommended Action    Check the DTI link/cable.

%UBR10KTCC-6-DTIPORTSERVER: DTCC slot [dec]/[dec] port [dec] DTI server status 
changed to [chars], external clock source: [chars] 

Explanation    There is a change in the server status of DTI port.

Recommended Action    Check the DTI link/cable.

%UBR10KTCC-5-DTISLOT: DTCC slot [dec]/[dec]: card role changed to [chars] 

Explanation    There is a change in the role of TCC slot.

Recommended Action    Check the DTI link/cable

%UBR10KTCC-3-EVNTLEN: TCCplus card Event internal error, [chars] [dec] [dec] 

Explanation    The TCC+ or DTCC card is reporting an internal event error, indicating a possible software fault.

Recommended Action    This error message can occasionally occur during system power-on and reset. If the message occurs at other times, reinstall or replace the timing card. If this does not correct the problem, upgrade the Cisco uBR10012 router to Cisco IOS Release 12.2(11)BC2 for TCC+ card or to (12.3(23)BC2 or 12.2(33)SCB or a later release for DTCC card.

If the problem persists, copy the error message exactly as it appears on the console or in the system log. Issue the show cable clock and show tech-support commands to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10KTCC-1-LCLOSC: Cable Line Card [dec]/[dec] using the local oscillator 

Explanation    An error occurred in the clock signal when it was received on the BackPlane.

Recommended Action    Check that the reference sources are correctly plugged into the proper connectors on the TCC+ or DTCC card. Verify that the reference sources are providing a valid signal. If this does not correct the problem, replace the TCC+ or DTCC card. If the problem persists, copy the error message exactly as it appears on the console or in the system log. Issue the show cable clock and show tech-support commands to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR10KTCC-2-LOS: Loss of signal with clock reference [chars] in TCCplus card 
[dec]/[dec] 

Explanation    The clock reference source coming into the TCC+ or DTCC card was lost.

Recommended Action    Check that the reference sources are correctly plugged into the proper connectors on the TCC+ or DTCC card. Verify that the reference sources are providing a valid signal. If this does not correct the problem, replace the TCC+ or DTCC card.

%UBR10KTCC-1-NOTCC: No working TCCplus card available in the system 

Explanation    No TCC+ or DTCC card has been installed in the system. If a TCC+ or DTCC card is installed, the system might have put the card into maintenance mode because of a hardware problem. This message can also occasionally appear during a switchover of PRE-2 modules, when the secondary PRE-1 module misses the initial keepalive message from the active TCC+ or DTCC card.

Recommended Action    If this message appears only during switchovers, it can be ignored. Alternatively, upgrade the Cisco uBR10012 router to Cisco IOS Release 12.2(11)BC2 for TCC+ card or to (12.3(23)BC2 or 12.2(33)SCB or a later release for DTCC card, which include an enhancement to the switchover timers to ensure the keepalive message from the TCC+ or DTCC card is not missed.

Otherwise, use the show cable clock command to verify whether a TCC+ or DTCC card is installed and operational. The Cisco uBR10012 router requires at least one working TCC+ or DTCC card for normal operations, so install at least one TCC+ or DTCC card in the chassis. If a TCC+ or DTCC card is installed, remove it and reinstall it. Verify that the router is running Cisco IOS Release 12.2(11)BC2 for TCC+ card or to (12.3(23)BC2 or 12.2(33)SCB or a later release for DTCC card. If this does not correct the problem, replace the TCC+ or DTCC card. If possible, install redundant TCC+ or DTCC cards to avoid this problem in the future.

%UBR10KTCC-4-OIRERR: TCC OIR state machine warning: attempt to restart working 
card

Explanation    Online insertion and removal (OIR) start is called twice, one after the other.

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/cgi-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.

%UBR10KTCC-1-SWTCHERR: Unable to switch TCCplus card configuration. Other card is 
not present or in Maintenance 

Explanation    The system encountered a failure in the active TCC+ or DTCC card and attempted to switch to the backup TCC+ or DTCC card, but the second card is either not present or is already in maintenance mode.

Recommended Action    Remove and reinsert the TCC+ or DTCC cards. If this does not correct the problem, replace at least one TCC+ or DTCC card. If other error messages indicate a clock reference problem, check that the reference sources are correctly plugged into the proper connectors on the TCC+ or DTCC card. Also, verify that the reference sources are providing a valid signal. If the problem persists, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

UBRIFCON

The messages in this section are generated by the subsystem that generates the processes for a console session on the Cisco uBR10012 router.

%UBRIFCON-3-NOPROC: Unable to create the if-console background process 

Explanation    The system was unable to create a background process to handle the interface console data from the line cards.

Recommended Action    Display the running configuration with the show running-config command, and look for any commands that might be allocating large amounts of memory for specific buffers, such as the logging buffered command. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error, especially the number of processes and memory usage. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

%UBRIFCON-3-NOQUEUE: Unable to create the if-console background queue 

Explanation    The system was unable to create a background process queue to handle the interface console data from the line cards.

Recommended Action    Display the running configuration with the show running-config command, and look for any commands that might be allocating large amounts of memory for specific buffers, such as the logging buffered command. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error, especially the number of processes and memory usage. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.

UBRLCIFCON

This section describes the system messages pertaining to crash or coredump processing.

%UBRLCIFCON-3-NOPROC: Unable to create if-console process.

Explanation    The if-console process could not be started.

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/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

WBCMTS_GIGE

The following are wideband CMTS GigE interface error messages:

%WBCMTS_GIGE-4-LINK_ERROR: [chars] 

Explanation    Error is encountered in the GigE link state update protocol.

Recommended Action    If it stops after one or a few power cycles, the hardware is recovered fully. If this error is observed continuously, 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/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, issue the show tech-support command to gather data that may help identify the nature of the error and 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.