Cisco IOS CMTS Cable System Messages Guide
Chapter 2: Cisco CMTS Router System Messages
Downloads: This chapterpdf (PDF - 1.92MB) The complete bookPDF (PDF - 2.58MB) | Feedback

Cisco CMTS Router System Messages

Table Of Contents

Cisco CMTS Router System Messages

AAAA

ALARM

ARP

ATA

AUTORP

BCM

C10K

C10KATM

C10KEHSA

C10KEVENTMGR

C10K_IEDGE

CFIB

CHASSIS

CHKPT

CI

CLCENVM

CLCJIB

CLCOBFL

CLCRMN

CLCSNMP

CLNT

CMTS_LIC

COBALT

CORABI

CR10K_DIAG

CR10KBH

CWAN_SPA

DHCPV6R

DOT1X

DS

DSG

DTSEC

ESM20

ETSEC

FABRIC_INTF

FILESYS

FM

FMEA

FPD_MGMT

GE_LINK

GENERAL

HA_EM

HCCP

HDSPA

HQF

I2C

IGMP

IFDAMP

IFMGR

IP

IPC

IPCGRP

IPCMON

IPCOIR

JIB3_US_FAUNA

JIB3_US_FL

JIBREAD

L2TP

LC

LCD_DISPLAY

LICENSE

LTC

MCT1E1

MCU, MCUCLC, MCUFSM

MCU

MCUCLC

MCUFSM

MLS

MPLS_ADJ_SB

MROUTE

NICKEL10G

OCE

OBFL

PA_REM

PARSER

PCIE

PIM

PORT_SECURITY

POWER1220

PQUICC3

PXF

QOS

RADIAN

RAVEN

RFS

RFSW

RPLIC

RTT

SFP

SNMP

SPAWBCMTS

SW_WDOG

SYS

UBR7100, UBR7200, and UBR10000

UBR10K

UBR7200IPC

UBRSNMP

UPCONV

USB

USB_HOST_STACK


Cisco CMTS Router System Messages


This chapter lists the CMTS system messages for the Cisco uBR7100 series, Cisco uBR7200 series, and Cisco uBR10012 routers. The messages are listed alphabetically, first according to the facility portion of the message, and then according to the mnemonic portion of the message.

AAAA

ALARM

ARP

ATA

AUTORP

BCM

C10K

C10KATM

C10KEHSA

C10KEVENTMGR

C10K_IEDGE

CFIB

CHASSIS

CHKPT

CI

CLCENVM

CLCJIB

CLCOBFL

CLCRMN

CLCSNMP

CLNT

CMTS_LIC

COBALT

CORABI

CR10K_DIAG

CR10KBH

CWAN_SPA

DHCPV6R

DOT1X

DS

DSG

DTSEC

ESM20

ETSEC

FABRIC_INTF

FILESYS

FM

FMEA

FPD_MGMT

GE_LINK

GENERAL

HA_EM

HCCP

HDSPA

HQF

I2C

IGMP

IFDAMP

IFMGR

IP

IPC

IPCGRP

IPCMON

IPCOIR

JIB3_US_FAUNA

JIB3_US_FL

JIBREAD

L2TP

LC

LCD_DISPLAY

LICENSE

LTC

MCT1E1

MCU, MCUCLC, MCUFSM

MLS

MPLS_ADJ_SB

MROUTE

NICKEL10G

OCE

OBFL

PA_REM

PARSER

PCIE

PIM

PORT_SECURITY

POWER1220

PQUICC3

PXF

QOS

RADIAN

RAVEN

RFS

RFSW

RPLIC

RTT

SFP

SNMP

SPAWBCMTS

SW_WDOG

SYS

UBR7100, UBR7200, and UBR10000

UBR10K

UBR7200IPC

UBRSNMP

UPCONV

USB

USB_HOST_STACK

AAAA

The following are TACACS+ Authentication, Authorization, and Accounting security messages.

%AAAA-4-NOCACHEPROC : The aaa cache process is not created. Please configure aaa 
cache profile first 

Explanation    The AAA cache was listed in a method-list without defining it earlier.

Recommended Action    Define the cache profile before using it.

ALARM

This section describes system error messages that are related to alarms.

%ALARM-3-CLEAR: [chars] [chars] [chars] [chars] [chars] 

Explanation    The alarm has been cleared.

Recommended Action    No action is required.

%ALARM-6-ENTITY_INFO: [chars] [chars] [chars] [chars] [chars] 

Explanation    This is entity alarm assertion or deassertion information.

Recommended Action    No action is required.

%ALARM-3-NOMEM: OUT of Memory: [chars] 

Explanation    System is running low on memory.

Recommended Action    Copy the error message and get the show tech output data that may help identify the nature of the error. Reboot the system. If it is the line card, reboot of the line card alone would be sufficient.

ARP

The following are the Address Resolution Protocol (ARP) error messages.

%ARP-3-ARPINVALIDEENTRY : ARP system internal error. Returns NULL arp entry on 
node 

Explanation    An internal software error has occurred in ARP subsystem, and the router returns a NULL ARP entry.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%ARP-4-NULL_SRC_MAC: NULL MAC address from [IP_address] on [chars] 

Explanation    Application or peer tried to insert an entry with a null source MAC address.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%ARP-5-STCKYARPOVR: Attempt to overwrite Sticky ARP entry: [IP_address], hw: 
[enet] by hw: [enet] 

Explanation    Multiple stations configured with same IP in Private VLAN. Possible case of IP address stealing.

Recommended Action    Change the IP address of one of the two systems.

ATA

The following are the system error messages related to Advanced Technology Attachment (ATA):

%ATA-3-ATA_STATUS_ERROR: Error occurred while querying the status of ATA device. 
Return: [dec], stat_reg: [hex] 

Explanation    An error occurred while querying the status of an ATA device. No response was received from the device.

Recommended Action    Replace the new ATA device and retry the operation. If the problem persists, enable the file system operation logs using the debug ifs file, debug ifs fs and debug ifs verbose commands. Collect the output of the show tech-support command. Contact your Cisco technical support representative and provide the representative with the gathered information.

%ATA-6-ATA_STATUS_TIMEOUT: Timeout occurred while querying the status of ATA 
device. Status returned :[hex], event: [dec] 

Explanation    A time-out occurred while querying the status of ATA device.

Recommended Action    Replace the new ATA device and retry the operation. If the problem persists, enable the file system operation logs using the debug ifs file, debug ifs fs and debug ifs verbose commands. Collect the output of the show tech-support command. Contact your Cisco technical support representative and provide the representative with the gathered information.

AUTORP

The following are the Multicast Rendezvous Point system error messages:

%AUTORP-4-PAK_ERR: AutoRP [chars] packet is received on interface [chars] with 
Source address=[IP_address], Destination address=[IP_address], TTL=[int], IP 
length=[int] Datagram size/UDP length=[int] 

Explanation    The AutoRP packet was received with wrong packet length. The packet has been dropped as it may be a malformed packet.

Recommended Action    No action is required.

%AUTORP-6-RP_MAPPING_IDB_DEL: AutoRP RP-MAPPING IDB [chars] is deleted 

Explanation    The configured RP-mapping idb has been deleted.

Recommended Action    No action is needed.

BCM

The following are BCM controller error messages:

%BCM3142-5-ACK_OV: Mg[int]/[int] ACK window overflow @ seq [int] ([int]) 

Explanation    A BCM3142 request ACK has been lost.

Recommended Action    No action is needed.

%BCM3142-4-APP_SEMA_TIMEOUT: Mg[int]:[int] Semaphore timeout seq [int] 

Explanation    Upstream PHY driver client is unable to create semaphore causing time out.

Recommended Action    Verify if there is a possible packet loss on the control plane.

%BCM5396-3-BAD_MODEL_ID: Unexpected model id: [hex] 

Explanation    The model ID of the part is not correct.

Recommended Action    Verify if there is any possible error with RAVEN or GigE switch.

%BCM3142-3-CFC_INT: Mg[int] Rcvr [int]: CFC interrupt [hex] received from BCM3142, 
resend [hex] 

Explanation    A receiver CFC interrupt has been received from the BCM3142 device.

Recommended Action    Reset the cable upstream interface using the shutdown and no shutdown commands.

%BCM3142-3-EGRESS_DROP: Mg[int]: Egress drop interrupt, A=[hex] ([int]), B=[hex] 
([int]) 

Explanation    An egress packet drop interrupt has been received from the BCM3142 device. Packets were dropped by the BCM3142 egress engine.

Recommended Action    This is a non-fatal software memory error. No action is needed.

%BCM3142-3-GEN_INIT_FAIL: Driver init has failed: [chars] 

Explanation    The Mg driver initialization has failed due to the specified error.

Recommended Action    Check if there is any possible hardware problem.

%BCM3142-2-INITFAILED: Mg[dec]: [chars] ([dec]) 

Explanation    The BCM3142 device initialization has failed.

Recommended Action    Reset/reload the line card and monitor for replacement. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%BCM3142-2-INITFAILED_DEST: Mg[dec]: [chars]:[dec] ([dec]) 

Explanation    The Mg device initialization has failed

Recommended Action    Check the affected upstreams and perform reload. If the problem 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%BCM3142-3-INT_ACKERR: Mg[int] failed to send ack for interrupt [hex], channel 
[int], mask [hex] resend [hex] 

Explanation    Cisco CMTS has failed to send interrupt ACK message.

Recommended Action    No action is needed if the interrupt does not re-occur. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%BCM3142-3-INTERNAL: Mg[int]/[int]: [chars] ([dec], [hex]) 

Explanation    An internal Mg driver error has been encountered.

Recommended Action    Check for proper upstream operation and perform reload. 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 v 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%BCM3142-3-INT_NOIDB: Mg[int] Rcvr [int]: No idb for interrupt type [hex] sta 
[hex] received from BCM3142 

Explanation    IDB has not been received from the BCM3142 device for the specified receiver interrupt.

Recommended Action    Reset the cable upstream interface using the shutdown and no shutdown commands

%BCM3142-3-INT_NOMEM: Mg[int] Rcvr [int]: No chunk mem to handle interrupt type 
[hex] sta [hex] received from BCM3142 

Explanation    An internal software error has 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%BCM3142-3-LATE_MAP_FLUSH_INT: Mg[int] Rcvr [int] lch [int]: LATE_MAP_FLUSH 
interrupt received from BCM3142, reg_mask_lo [hex], reg_mask_hi [hex], reg_count 
[int], resend_mask_lo [hex], resend_mask_hi [hex], resend_count [int] 

Explanation    A receiver LATE_MAP_FLUSH interrupt was received from the BCM3142.

Recommended Action    Shut and unshut the upstream.

%BCM5396-3-MDIO_TIMEOUT: MDIO Timeout [chars] 

Explanation    No response has been received from the GigE switch MDIO interface.

Recommended Action    Investigate possible Raven MDIO interface.

%BCM5396-3-MODEL_ID: Failed to read model id 

Explanation    Failed to read a register via MDIO interface.

Recommended Action    Verify if there is any possible error with RAVEN or GigE switch.

%BCM3142-2-MIPSINITFAILED: Mg[dec]: [chars] record [int] 

Explanation    Mg MIPS initialization has failed.

Recommended Action    Reset the line card to attempt recovery and monitor for card replacement. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%BCM3142-3-MPI_INT: Mg[int] Rcvr [int]: MPI interrupt [hex] received from BCM3142, 
resend [hex] 

Explanation    A receiver MAC -PHY Interface (MPI) interrupt has been received from the BCM3142 device.

Recommended Action    Reset the cable upstream interface using the shutdown and no shutdown commands.

%BCM3142-3-NACK: Mg[int]/[int]: NACK received, seqNo [int], error [hex] 

Explanation    BCM3142 has sent a NACK to the Register Processor (RegProc) message. RegProc is the control plane protocol for the Mg.

Recommended Action    An internal software error has occurred. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%BCM3142-4-NB_GAIN: Digital gain for [chars]:[dec] is set to the [chars] limit 

Explanation    Inside Mg, each channel has a digital amplifier. Its gain is set based on calibration data, and parameters (freq, qam, bw) of all the active channels frequency stacked in the same connector. This error message indicates that the calculated gain is out o f range due to mis-configuration.

Recommended Action    Correct the misconfiguration. Reduce configuration deviation among active channels sharing the same connector. The configuration parameters include power-level, channel-width, frequency, and modulation. If the problem still persists (that is, if you still get the messages), it is either a cable, connector or hardware issue. If the issue is not repeated after the cable interface line card switchover, it may be a cable, connector, or hardware issue.

%BCM3142-5-NO_ACK: Mg[int]/[int] NO ACK for seq [int] ([int]) 

Explanation    A register write is not acknowledged.

Recommended Action    This is an internal failure, a control frame was likely lost. No action is needed.

%BCM3142-3-NOBUFF: The [chars] message cache is empty 

Explanation    The Mg message cache is empty and as a result an incoming message may be dropped. This issue occurs due to a possible memory leak.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%BCM3142-2-ONINT: Invalid operation at int level: [chars] Mg[int]/[int], addr 
[hex] 

Explanation    An upstream PHY application interface has attempted a blocking read at interrupt level.

Recommended Action    This is an internal software error. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%BCM3142-3-PGA_ERR: card [dec]/[dec] US PGA [dec] set failure: wr=[hex] rd=[hex] 

Explanation    Failed to set PGA register.

Recommended Action    This is a possible hardware failure. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%BCM3142-4-PGA_GAIN: PGA gain for connector [dec] is set to the [chars] limit 

Explanation    Each front panel upstream connector has a PGA. Its gain is set based on calibration data, and parameters (freq, qam, bw) of all the active channels frequency stacked in this connector. This error message indicates that due to mis-configuration the calculated gain value is out of range.

Recommended Action    Correct the misconfiguration. If the problem still persists (that is, if you still get the messages), it is either a cable, connector or hardware issue. If the issue is not repeated after the cable interface line card switchover, it may be a cable, connector, or hardware issue.

%BCM3142-3-READ_ERR: Mg[int]/[int]: Read error @ addr [hex], status [int] 

Explanation    An error occurred while reading from the BCM3142 device.

Recommended Action    An internal software error has occurred. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%BCM3142-3-READ_ERR_SEQ: Mg[int]/[int]: Read error seq [int], status [int] 

Explanation    An error occurred while reading from the BCM3142 device.

Recommended Action    An internal software error has occurred. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%BCM5396-3-READ_TIMEOUT: Timeout waiting for read (pg [dec], addr [dec], len 
[dec]) 

Explanation    Failed to read a page register via MDIO interface.

Recommended Action    Verify if there is any possible error with RAVEN or GigE switch.

%BCM3142-3-SEMA_TIMEOUT: (Mg[int]) MIPS [chars] semaphore not cleared ([hex]) 

Explanation    BCM3142 MIPS bootrom semaphore is not cleared.

Recommended Action    BCM3142 MIPS processor may be hung or possible control plane issue. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%BCM3142-5-SEQ_ERROR: Mg[int]/[int] Sequence Error @ [int] 

Explanation    A sequence error has been reported by the BCM3142 registration process.

Recommended Action    An internal software error has occurred due to loss of control frame. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%BCM3142-5-SEQ_MISMATCH: Mg[dec]/[dec]: Response ID mismatch, exp seqId [dec] read 
[dec] 

Explanation    An out of order control message has been received by the PMI driver.

Recommended Action    Reset the line card if the problem persists.

%BCM3142-4-SIDTABLE: Mg[dec]: Failed to update SID [int], chan [int]/[int] 

Explanation    DOCSIS SID table add or delete operation failed.

Recommended Action    Delete the cable modem and monitor recovery.

%BCM3142-3-SPI_ERR: Mg[int]: SPI error, [chars] 

Explanation    An error occurred while accessing BCM3142 device via SPI bus.

Recommended Action    An internal software error has occurred. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%BCM3142-3-SPI_READ_ERR: Mg[int]: SPI Read error @ addr [hex], status [int] 

Explanation    An error occurred while reading from the BCM3142 device via SPI bus.

Recommended Action    An internal software error has occurred. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%BCM3142-3-SPI_WRITE_ERR: Mg[int]: SPI Write error @ addr [hex], status [int] 

Explanation    An error occurred while writing to the BCM3142 device via SPI bus.

Recommended Action    An internal software error has occurred. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%BCM3142-3-TFC_INT: Mg[int] Rcvr [int]: TFC interrupt [hex] received from BCM3142, 
resend [hex] 

Explanation    A receiver TFC interrupt has been received from the BCM3142 device.

Recommended Action    Reset the cable upstream interface using the shutdown and no shutdown commands

%BCM3142-3-TGC_SYNCPULSE_FAILED: BCM3142 Failed to detect sync-pulse, interval 
[dec], [chars] 

Explanation    The BCM3142 device has failed to detect RAVEN sync-pulse.

Recommended Action    An internal software error has occurred. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%BCM3142-3-TGC_VERIFYFAILED: Mg[int] TGC-verify not sampled at frame-sync pulse 
[hex], intvl [hex], retCode [dec] 

Explanation    The BCM3142 device has failed to verify TGC sync-pulse.

Recommended Action    An internal software error has occurred. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%BCM3142-4-TIMEOUT: (Mg[int]/[int]) Timeout waiting for response, seqNo [int]. 

Explanation    No response is received from the upstream PHY interface.

Recommended Action    Check if there is a possible packet loss on the BCM3142 device control plane.

%BCM3142-3-TRUNCATED: Mg[int]/[int]: Response seqId [dec] truncated [dec] bytes. 

Explanation    User buffer memory was insufficient to hold response.

Recommended Action    An internal software error has occurred. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%BCM3142-5-UNEXPECTED_ACK: Mg[int]/[int] Unexpected ACK for seq [int] ([int]) 

Explanation    An unexpected ACK message was received for a frame that was not in the window.

Recommended Action    This is an internal software error with no known cause. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%BCM5396-3-WRITE_TIMEOUT: Timeout waiting for write (pg [dec], addr [dec], len 
[dec]) 

Explanation    Failed to read a page register via MDIO interface.

Recommended Action    Verify if there is any possible error with RAVEN or GigE switch.

C10K

The following are C10K error messages:

%C10K-3-EEPROM_ERROR: [chars] on subslot [int]/[int] 

Explanation    Unable to read or write EEPROM.

Recommended Action    Issue the show diag command. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%C10K-3-MEM_SBE_MANY_NO_SWITCHOVER: Multiple memory single-bit ECC errors, no 
redundant PRE initiated to switchover. 

Explanation    The system has experienced multiple recent memory single-bit ECC errors. A redundant PRE is not available and hence the system does not switch over to use it.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%C10K-3-MEM_SBE_MANY_SWITCHOVER: Multiple memory single-bit ECC errors, 
switchover to redundant PRE initiated. 

Explanation    The system has experienced multiple recent memory single-bit ECC errors. A redundant PRE is available and hence the system switches over to use it.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%C10K-3-NOMAC: Can't allocate MAC address for interface [slot]/[subslot]/[port] 

Explanation    Exceeding MAC allocation limit.

Recommended Action    Remove unnecessary interfaces.

%C10K_QOS_GENERAL-2-POLICY_MAP_ID_CORRUPTION: Invalid Policy-map Id 

Explanation    The policy-map ID is corrupt.

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). Run the show pxf cpu qos vcci number command to gather data that might help identify the nature of the error. Also perform a search of the Bug Toolkit (http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%C10K-3-QUACK_FAIL_ERR: The PRE module of this router may not be a genuine 
Cisco product 

Explanation    Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco PRE into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program such as SmartNet.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%C10K_BBA_SESSION-5-KAEVENT: [chars] ([dec]) 

Explanation    PXF is unable to create ppp echo reply messages. The session should still be functional. In some cases, this is an expected behavior. For example, when the magic number for a session is 0.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%C10K_TOASTER-3-DIVPATTERN: !!Invalid Hex Pattern, use only hex characters: 
[chars]!! 

Explanation    Invalid Hex pattern.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

C10KATM

The following are Cisco10000 ATM subsystem messages:

%C10KATM-3-CHANNEL_ID: channel-id set to 0x0 for(VCD=[dec]) on Interface [chars], 
traffic over this vc may fail (Cause of the failure: [chars]) 

Explanation    This message occurs when the platform fails to set a proper channel-id in 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

C10KEHSA

The following are Cisco10000 ESHA subsystem messages:

%C10KEHSA-3-STANDBY_CPUHOG: CPUHOG on Remote PRE! Proc: "[chars]", PID: [dec], 
[chars] 

Explanation    A high CPU utilization is observed on the remote PRE.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%C10KEHSA-4-STANDBY_FORCED_CRASH: Force remote PRE crash for keepalive timeout 

Explanation    This error message is observed when the remote PRE does not respond to EHSA keepalive message, and hence is forced crashed by local PRE.

Recommended Action    Check for crashinfo file in the PRE and issue the show tech-support command to gather data that may help identify the nature of the error. 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.

%C10KEHSA-3-STANDBY_FORCED_RESET: Force remote PRE reset 

Explanation    This is observed when the remote PRE was reset since it did not crash after it received crash command from local PRE.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

C10KEVENTMGR

The following are Event Manager subsystem messages:

 
    
    
   

%C10KEVENTMGR-4-IRONBUS_FAULT : [chars], Restarting Ironbus

Explanation    Ironbus fault has occurred, restarting ironbus

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%C10KEVENTMGR-4-IRONBUS_SUCCESS: [chars], Restart Successful 

Explanation    Ironbus fault has occurred and Ironbus restarted successfully.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%C10KEVENTMGR-3-MINOR_FAULT: [chars] 

Explanation    A threshold for a minor event has been reached.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

C10K_IEDGE

The following are Cisco 10000 iEdge messages.

C10K_IEDGE-5-IEDGE_COUNTER_MSG: TC ACL [chars], VCCI [int]l, 

Explanation    This event occurred because in some data path ucode has not taken care of header length. Monitor the type of traffic for this session. Accounting for this session may be affected.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%C10K_IEDGE-5-IEDGE_POLICY_WRITE_FAIL : Could not write iEdge_policy [chars] into 
pxf 

Explanation    This event occurred during microcode reload writing the iEdge policy to the PXF failed. The sessions using this policy may be affected.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

CFIB

The following are Constellation Forward Information Base (FIB) messages.

%CFIB-3-CFIB_UNEXPECTED : Unexpected CFIB condition 

Explanation    An error occurred where an unexpected condition was observed in the Constellation FIB 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

CHASSIS

%CHASSIS-6-EJECT_BUTTON: [chars] eject button is being screwed on/off.

Explanation    One or both of the screws on the PRE5 front panel is not tightened.

Recommended Action    Tighten the screws before using the levers to pivot the PRE5 in and out of the chassis. Also, check if the screws are broken. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CHASSIS-3-OPERATION_FORBIDDEN: [chars] and try again. 

Explanation    There are two screws and two levers on the PRE5 front panel. When both levers are pulled out or the plugin-card-protect [enable | disable] command is used, the software modules protected may fail. That is, write or erase based on the bootflash chip.

Recommended Action    Unscrew and then tighten the two screws on the PRE5.

%CHASSIS-4-READALERTRESERR: MAX1668 [dec] read alert response address error 

Explanation    MAX1668 read alert response address failed.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

CHKPT

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.

%CHKPT-4-DISABLED: Check Pointing is disabled. Client [chars] should not be 
calling any CF API

Explanation    A checkpoint client has attempted to send an inter-process communication (IPC) message after redundancy operations have been disabled. This can be due to lost IPC messages or delays in synchronization, which will eventually resolve themselves.

Recommended Action    No action is required.

%CHKPT-4-DUPID: Duplicate checkpoint client ID ([dec]).

Explanation    A checkpoint client is using a client ID that is already assigned to another client. This could be due to a synchronization delay, which typically will resolve itself.

Recommended Action    No action is required.

%CHKPT-3-ILLEGAL: ILLEGAL call to CF API on ([chars]) by ([chars]).

Explanation    A severe software error occurred with the Checkpoint Facility subsystem.

Recommended Action    Verify that the CMTS is running released software. 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.

%CHKPT-4-INVALID: Invalid checkpoint client ID ([dec]).

Explanation    A checkpoint client is using an old or stale client ID. This could be due to a synchronization delay, which typically will resolve itself.

Recommended Action    No action is required.

%CHKPT-3-IPCPORT: Unable to create IPC port on ([chars]). 

Explanation    A severe checkpoint error occurred because the system was unable to allocate the resources needed to create a communications port for the Interprocess Communications (IPC) channel needed to transmit messages.

Recommended Action    Verify that the CMTS is running released software. 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.

%CHKPT-3-IPCSESSION: Unable to open an IPC session for communicating with 
([chars]). rc= [dec]

Explanation    A severe checkpoint error occurred because the system was unable to establish an Interprocess Communications (IPC) session between interfaces, which is needed to transmit messages.

Recommended Action    Verify that the CMTS is running released software. 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.

%CHKPT-3-NOMEM: Unable allocate resource for CF on ([chars]).

Explanation    A severe checkpoint error occurred because the system was unable to allocate the resources (typically memory) on the indicated interface, as needed to create an Interprocess Communications (IPC) channel needed to transmit messages.

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 the CMTS is running released software. 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.

%CHKPT-3-RFREG: Unable to register checkpoint as client of RF.

Explanation    A severe checkpoint error occurred because the system was unable to register with the redundancy facility (RF) so that it could begin the transmission of IPC messages between interfaces.

Recommended Action    Verify that the CMTS is running released software. 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.

%CHKPT-4-SENDFAILED: Checkpointing send failed client ([dec])

Explanation    A checkpoint client failed in an attempt to send an IPC message after redundancy operations have been disabled. This can be due to lost IPC messages or delays in synchronization, which will eventually resolve themselves.

Recommended Action    No action is required.

%CHKPT-3-UNKNOWNMSG: Unknown message received from peer on standby for client 
([dec]).

Explanation    A severe software error occurred with the Checkpoint Facility subsystem. This might indicate a Cisco IOS software mismatch between the Active and Standby interfaces, or between a line card and the PRE module.

Recommended Action    Verify that the CMTS is running released software. 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.

CI

The following are the CI messages:

%CI-1-COBALTTEMPCRITICAL: Cobalt temperature CRITICAL limit exceeded 

Explanation    Cobalt temperature critical limit has been exceeded. The system will automatically shut down in two minutes.

Recommended Action    Check if the fan tray is working fine and the circumstance temperature. The system will power off automatically if the critical alert lasts for 2 minutes. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CI-3-COBALTTEMPMAJOR: Cobalt temperature major limit exceeded 

Explanation    Cobalt temperature major limit has been exceeded.

Recommended Action    Check if the fan tray is working fine and the circumstance temperature. The system will power off automatically if the critical alert lasts for 2 minutes. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CI-3-COBALTTEMPMINOR: Cobalt temperature minor limit exceeded 

Explanation    Cobalt temperature minor limit has been exceeded.

Recommended Action    Check if the fan tray is working fine and the circumstance temperature. The system will power off automatically if the critical alert lasts for 2 minutes. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CI-6-COBALTTEMPOK: Cobalt temperature normal 

Explanation    Temperature of Cobalt is normal.

Recommended Action    No action is required.

%CI-1-FPINLETTEMPCRITICAL: FP Board Inlet temperature CRITICAL limit exceeded 

Explanation    FP board air intake temperature critical limit has been exceeded. The system will automatically shut down in two minutes.

Recommended Action    Check if the fan tray is working fine and the circumstance temperature. The system will power off automatically if the critical alert lasts for 2 minutes. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CI-3-FPINLETTEMPMAJOR: FP board Inlet temperature major limit exceeded 

Explanation    FP board air intake temperature major limit has been exceeded.

Recommended Action    Check if the fan tray is working fine and the circumstance temperature. The system will power off automatically if the critical alert lasts for 2 minutes. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CI-3-FPINLETTEMPMINOR: FP Board Inlet temperature minor limit exceeded 

Explanation    FP board air intake temperature minor limit has been exceeded.

Recommended Action    Check if the fan tray is working fine and the circumstance temperature. The system will power off automatically if the critical alert lasts for 2 minutes. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CI-6-FPINLETTEMPOK: FP Board Inlet temperature normal 

Explanation    Temperature of the FP board intake temperature is normal.

Recommended Action    No action is required.

%CI-1-FPOUTLET1TEMPCRITICAL: FP Board Outlet1 temperature CRITICAL limit exceeded 

Explanation    FP board air outlet1 temperature critical limit has been exceeded. The system will automatically shut down in two minutes.

Recommended Action    Check if the fan tray is working fine and the circumstance temperature. The system will power off automatically if the critical alert lasts for 2 minutes. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CI-3-FPOUTLET1TEMPMAJOR: FP Board Outlet1 temperature major limit exceeded 

Explanation    FP board air outlet1 temperature major limit has been exceeded.

Recommended Action    Check if the fan tray is working fine and the circumstance temperature. The system will power off automatically if the critical alert lasts for 2 minutes. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CI-3-FPOUTLET1TEMPMINOR: FP Board Outlet1 temperature minor limit exceeded 

Explanation    FP board air outlet1 temperature minor limit has been exceeded.

Recommended Action    Check if the fan tray is working fine and the circumstance temperature. The system will power off automatically if the critical alert lasts for 2 minutes. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CI-6-FPOUTLET1TEMPOK: FP Board Outlet1 temperature normal 

Explanation    Temperature of the FP board outlet1 air is normal.

Recommended Action    No action is required.

%CI-1-FPOUTLET2TEMPCRITICAL: FP Board Outlet2 temperature CRITICAL limit exceeded 

Explanation    FP board air outlet2 temperature critical limit has been exceeded. The system will automatically shut down in two minutes.

Recommended Action    Check if the fan tray is working fine and the circumstance temperature. The system will power off automatically if the critical alert lasts for 2 minutes. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CI-3-FPOUTLET2TEMPMAJOR: FP Board Outlet2 temperature major limit exceeded 

Explanation    FP board air outlet2 temperature major limit has been exceeded.

Recommended Action    Check if the fan tray is working fine and the circumstance temperature. The system will power off automatically if the critical alert lasts for 2 minutes. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CI-3-FPOUTLET2TEMPMINOR: FP Board Outlet2 temperature minor limit exceeded 

Explanation    FP board air outlet2 temperature minor limit has been exceeded.

Recommended Action    Check if the fan tray is working fine and the circumstance temperature. The system will power off automatically if the critical alert lasts for 2 minutes. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CI-6-FPOUTLET2TEMPOK: FP Board Outlet2 temperature normal 

Explanation    Temperature of the FP board outlet2 air is normal.

Recommended Action    No action is required.

%CI-1-RTCBATTLOW: RTC Battery Low 

Explanation    The chassis RTC battery is low.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CI-6-RTCBATTOK: RTC Battery is normal 

Explanation    Chassis RTC Battery is normal.

Recommended Action    No action is required.

%CI-1-TITANTEMPCRITICAL: Titan temperature CRITICAL limit exceeded 

Explanation    Titan temperature critical limit has been exceeded. The system will automatically shut down in two minutes.

Recommended Action    Check if the fan tray is working fine and the circumstance temperature. The system will power off automatically if the critical alert lasts for 2 minutes. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CI-3-TITANTEMPMAJOR: Titan temperature major limit exceeded 

Explanation    Titan temperature major limit has been exceeded.

Recommended Action    Check if the fan tray is working fine and the circumstance temperature. The system will power off automatically if the critical alert lasts for 2 minutes. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CI-3-TITANTEMPMINOR: Titan temperature minor limit exceeded 

Explanation    Titan temperature minor limit has been exceeded.

Recommended Action    Check if the fan tray is working fine and the circumstance temperature. The system will power off automatically if the critical alert lasts for 2 minutes. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CI-6-TITANTEMPOK: Titan temperature normal 

Explanation    Temperature of Titan is normal.

Recommended Action    No action is required.

CLCENVM

The following are the line card environment messages:

%CLCENVM-6-TEMPNORMAL: [slot]/[subslot]: [chars] temperature is normal 

Explanation    This message notifies that the sensor temperature is normal.

Recommended Action    No action is needed.

%CLCENVM-4-TEMPTHRESHOLDEXCEED: [slot]/[subslot]: [chars] temperature [chars] 
limit ([dec] degC) exceeded at temperature [dec] degC and power [dec].[dec] watts 

Explanation    Sensor temperature threshold is crossed.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

CLCJIB

This section lists system error messages generated by the JIB subsystem on the Cisco uBR10012 router and Broadband Processing Engine (BPE) cable interface line cards, such as the Cisco uBR-MC5X20S, Cisco uBR-MC16U/X, and Cisco uBR-MC28U/X cards. The JIB is a custom-designed processor that performs DOCSIS MAC-layer processing, such as DOCSIS encapsulation, BPI encryption, CRC generation, concatenation, fragmentation, and payload header suppression (PHS).

The following messages are generated when the JIB processor receives a bad MAC-layer packet over the main data bus on the Cisco CMTS router.

%CLCJIB-6-BADJIBHDR: [chars]: JIB [dec] DS[dec] Iron bus error packet (count 
[dec]) [chars] 

Explanation    The JIB processor dropped the specified DOCSIS MAC-layer packet because the packet contained an error or was invalid. This message displays the first part of the dropped packet.

Recommended Action    Occasional bad packets are expected during normal operation. If the bad packets are all coming from the same cable modem, verify that the cable modem is running DOCSIS-qualified software. If the problem persists, verify that the CMTS is running released software. 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.

%CLCJIB-6-BADJIBPKT: [chars] 

Explanation    The JIB processor dropped the specified DOCSIS MAC-layer packet because the packet contained an error or was invalid. This message displays the second part of the dropped packet. For the header portion of the packet, as well as the downstream on which it was received, see the previous %CLCJIB-6-BADJIBHDR error message.

Recommended Action    Occasional bad packets are expected during normal operation. If the bad packets are all coming from the same cable modem, verify that the cable modem is running DOCSIS-qualified software. If the problem persists, verify that the CMTS is running released software. 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.

%CLCJIB-6-QDBWRMISMATCH : JIB [dec] chan [dec] sid [dec] Queue-depth BW Req type 
mismatch 

Explanation    The received request type does not match the message type.

Recommended Action    If this message occurs, 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CLCJIB-6-RAMCECCERR: DOCSIS MAC correctable SDRAM/SSRAM ECC Error Counts: [dec] 
[dec] 

Explanation    The DOCSIS MAC experienced correctable synchronous dynamic random-access memory (SDRAM) or synchronous static random-access memory (SSRAM) ECC error counts.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CLCJIB-6-RINGSTUCK: [chars]: JIB[[dec]] Tx ring is full, stuck and could not be 
cleaned up. 

Explanation    JIB Tx ring may be stuck because head shadow pointers are NULL.

Recommended Action    Reset the line card. If the cable line card is not registering modems even after a card reset, then 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%CLCJIB-0-SDRAMUECCERR:DOCSIS MAC detected uncorrectable SDRAM ECC Error.

Explanation    The DOCSIS MAC experienced an uncorrectable SDRAM ECC 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

CLCJIB-0-SSRAMUECCERR:DOCSIS MAC detected uncorrectable SSRAM ECC Error.

Explanation    The DOCSIS MAC experienced an uncorrectable synchronous static random-access memory (SSRAM) ECC 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CLCJIB-6-TSLOAD: JIB [dec] timestamp is reloaded 

Explanation    The JIB timestamp is reloaded from the TCC card when repeated mismatched timestamps are detected.

Recommended Action    If the error messages are printed out continuously, it could be the indication of some sort of hardware problem.

1. If one JIB on a line card indicates a mismatch but the other two JIBs do not, it could be a broken JIB or a bad timestamp connection to that JIB.

2. If all three JIBs indicate the mismatches (or more than one), it could indicate a line card-level connection problem to the TCC card.

3. If JIBs on multiple line cards indicate mismatches, it is likely a TCC card problem of some sort.

%CLCJIB-6-TSMISMATCH: JIB [dec] timestamp mismatch 

Explanation    The JIB on a line card indicates a mismatch timestamp from the TCC card. Once it detects repeated mismatched timestamps, the timestamp will be reloaded from the clock card to bring the JIB back in sync.

Recommended Action    If the error messages are printed out continuously, it could be the indication of some sort of hardware problem.

1. If one JIB on a line card indicates a mismatch but the other two JIBs do not, it could be a broken JIB or a bad timestamp connection to that JIB.

2. If all three JIBs indicate the mismatches (or more than one), it could indicate a line card-level connection problem to the TCC card.

3. If JIBs on multiple line cards indicate mismatches, it is likely a TCC card problem of some sort.

CLCOBFL

The following are the cable line card on board failure logging (OBFL) error messages.

%CLCOBFL-6-CLCOBFLINIT : CLC OBFL ([dec]/[dec]):[chars] OBFL initialization 
failed 

Explanation    An OBFL initialization error occurred.

Recommended Action    If this message occurs, 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CLCOBFL-6-CLCOBFLSENSORACCESS : CLC OBFL ([dec]/[dec]):[chars] sensor access 
failure for sensor [chars] (ID: [dec]) 

Explanation    An OBFL sensor access error occurred.

Recommended Action    If this message occurs, 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CLCOBFL-6-CLCOBFLSTORAGEACCESS : CLC OBFL ([dec]/[dec]):[chars] operation on 
OBFL storage failed with error code [dec], OBFL address: [hex], num bytes: [dec] 

Explanation    An OBFL flash access error occurred.

Recommended Action    If this message occurs, 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

CLCRMN

The following are cable line card ReMan module error messages.

%CLCRMN-3-DSPHY : DS-Phy returned error: [chars] : port [dec] Chan [dec] Val [dec] 
Error [dec] 

Explanation    Downstream PHY driver returned error to ReMan module. It could be a software error or hardware failure.

Recommended Action    Enable ds-phy error debug to collect more details of the error. Check for any additional error message reported by ds-phy module.

CLCSNMP

This section lists system error messages generated by the SNMP process on the CMTS Cable Line Card (CLC).

%CLCSNMP-3-TRAPQFULL: SNMP trap pending queue is full.

Explanation    An SNMP trap generated on the CLC was dropped because the process tried to enqueue the trap to a pending queue, which was full. This condition occurred because the IPC was down or the SNMP information and the CLC were not synchronized.

Recommended Action    Verify that the CMTS is operating normally. Use the show process command to display the currently running processes and check whether any of the processes are overusing resources. If necessary, reboot the CMTS or add additional memory to the processor card. If the problem 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

CLNT

This section describes system error messages generated by the Cable Router Client (CLNT) subsystem.

%CR10K_CLNT-3-CR10K_ASSERT_FAILED: Assert failed at line [dec] from func [chars] 
in file [chars]

Explanation    A global level assert failure has been detected.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CR10K_CLNT-3-CR10K_CLNT_ASSERT_FAILED: Assert failed at line [dec] from func 
[chars] in file [chars] for client [dec]

Explanation    A client level assert failure has been detected.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

CMTS_LIC

This section lists system error messages generated by the CMTS Cable Line Card.

%CMTS_LIC-3-APPLY_DS_FAILED: Applying downstream license failed 

Explanation    Unable to apply the downstream license.

Recommended Action    This is an internal error. Check the license and report to TAC.

%CMTS_LIC-3-APPLY_US_FAILED: Applying upstream license failed 

Explanation    Unable to apply the upstream license

Recommended Action    This is an internal error. Check the license and report to TAC.

%CMTS_LIC-1-BAD_LICENSE_STORAGE : License Storage Error on Linecard [int]/[int] 

Explanation    The line card license storage status is BAD.

Recommended Action    Check the line card license details. If the problem is not fixed by multiple reinstall attempts, RMA the board.

%CMTS_LIC-6-CHAN_NOSHUTFAIL: [chars] channel [int] no shut is not allowed due to 
insufficient licenses 

Explanation    Unable to execute the no shutdown command on the channels due to insufficient licenses.

Recommended Action    This is an internal software error, verify the number of licenses installed.

%CMTS_LIC-6-CHANNEL_NO_SHUTDOWN: [chars] channel [int] has been restored to no 
shut 

Explanation    Previously shutdown channels are restored to no shutdown state.

Recommended Action    No action is needed.

%CMTS_LIC-6-CHANNEL_SHUTDOWN: [chars] channel [int] has been shutdown due to 
insufficient licenses 

Explanation    Channels are shutdown due to insufficient licenses.

Recommended Action    This is an internal software error, verify the number of licenses installed.

%CMTS_LIC-3-CSB_FAIL : [chars] failed for [chars] 

Explanation    An attempt to parse a license related command failed.

Recommended Action    Check the line card license details and if this message recurs, 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.

%CMTS_LIC-3-INVALID_LIC_INFO : License Info Buffer is empty for [int]/[int] 

Explanation    The license information buffer received or created from the line card is empty.

Recommended Action    Check the line card license details at the line card.

%CMTS_LIC-3-LCD_PROCESS_CREATE_FAIL: Could not create Update LCD process on 
Linecard [int]/[int] 

Explanation    The line card license LCD update process creation 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%CMTS_LIC-3-LICENSE_ACTIVFAIL: Could not activate license module on Linecard 
[int]/[int] 

Explanation    The line card license module activation 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%CMTS_LIC-3-LIC_LED_ERROR : Unable to set Downstream Density LED 

Explanation    The Cisco IOS software was unable to set the Downstream Density LED.

Recommended Action    Try online removal and insertion (OIR) of the line card and check the LED.

%CMTS_LIC-3-LICENSE_SEATNAME_ERROR: Unable to get slotid from [chars] 

Explanation    Unable to get slot-id.

Recommended Action    Check the license, if it is incorrect try reloading the linecard. If the problem 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%CMTS_LIC-3-LIC_WDC_ALLOCATION_ERROR : Unable to allocate memory for WDC memory 
storage 

Explanation    The Cisco IOS software was unable to allocate memory for WDC memory.

Recommended Action    Run the command again at a later time.

%CMTS_LIC-4-LICENSE_PENDING: License enforcement pending for Linecard [int]/[int] 

Explanation    The line card license enforcement will be delayed until the line card transitions to active.

Recommended Action    No action is required.

%CMTS_LIC-6-LICENSE_ENFORCE : Linecard [int]/[int] set to mode [chars] 

Explanation    License information is applied.

Recommended Action    No action is needed.

%CMTS_LIC-3-NULL_HWIDB : Function [chars] invoked with hwidb NULL 

Explanation    An unexpected HWIDB NULL pointer has occurred.

Recommended Action    Check the license and if the problem still persists, 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.

%CMTS_LIC-3-NULL_LICENSE_INFO : Line Card [int]/[int] license info is NULL! 

Explanation    An unexpected NULL pointer has occurred.

Recommended Action    Reload the line card. If the problem 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%CMTS_LIC-6-OUT_OF_RANGE: LC [int]/[int], [chars] is already [int] 

Explanation    License counters have reached boundary condition.

Error Message    This is an internal software error. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your 
Cisco technical support representative and provide the representative with the 
gathered information.
%CMTS_LIC-3-PROTECT_INVALID: Protect linecard [int]/[int] has lower license than 
the configured working 

Explanation    Protect line card has lower license than the working, thus the HCCP configuration is now invalid for the protect line card.

Recommended Action    Upgrade the license on the protect line card.

%CMTS_LIC-3-WORKING_INVALID: Working linecard [int]/[int] has higher license than 
the configured protect 

Explanation    Working line card has higher license than the protect, thus the HCCP configuration is now invalid for the working line card.

Recommended Action    Upgrade the license on the protect line card, or downgrade the license on the working line card.

%CMTS_LIC-3-WORKING_PARTIAL: Working Linecard [int]/[int] License has been 
restricted. Please upgrade Protect Linecard License first and then reload working 
for complete fulfillment 

Explanation    The working line card license is now restricted because the working line card license is higher than the protect line card license.

Recommended Action    Upgrade the license on the protect line card and then reload the working line card.

COBALT

The following are COBALT error messages.

%COBALT-2-RP_CONTEXT_INJECT : RP injecting packet with context bit set. Packet 
will be dropped. 

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%COBALT-3-COBERR: Cobalt [chars]. 

Explanation    Cobalt generated an error.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

CORABI

%CORABI-3-FATAL_N10G_ERP_ERROR: ERP errors: [chars], ERP error data: [hex] ERP 
error phase: [hex], ERP error addr: [hex] 

Explanation    Fatal Corabi N10G ERP interrupt is encountered.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%CORABI-3-FATAL_N10G_FAULT: N10G fault reported 

Explanation    Fatal Corabi N10G Fault interrupt is encountered.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

CR10K_DIAG

The following are CR10K_DIAG error messages.

%CR10K_DIAG-3-LLQDROP : LLQ Drops on [chars], new_drops:[dec] total_drops:[dec] 

Explanation    The health monitoring code has detected drops on the low latency queue of the specified interface. This is not expected behavior. The interface should be monitored to determine if drops continue to increase.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CR10K_DIAG-3-MEMLEAK : MemLeak Monitor: [chars] [chars] 

Explanation    The health monitoring code has detected potential memory leaks in the local IOS sub-system. This is not an expected behavior.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CR10K_DIAG-5-DIAG_LOOP_ETSEC: eTSEC loopback failure, [chars] 

Explanation    A loopback between eTSEC1 and eTSEC2 failed.

Recommended Action    Monitor the failed line card for excessive failures.

%CR10K_DIAG-5-DIAG_LOOP_MG: US PHY [int] loopback failure, [chars] ([int]) 

Explanation    Failed to loop back frame from CPU -> PHY -> JIB3 US -> CPU.

Recommended Action    Monitor the failed line card for excessive failures.

%CR10K_DIAG-5-DIAG_LOOP_RXERR: US PHY [int] loopback discrepency detected frames 
tx [dec], rx [dec], err [hex] 

Explanation    Failed to loop back one or more frames.

Recommended Action    Monitor the failed line card for excessive failures.

%CR10K_DIAG-5-DIAG_LOOP_SEQ: US PHY [int] loopback failed, unexpected seq [dec], 
exp [dec] 

Explanation    Failed to loop back one or more frames.

Recommended Action    Monitor the failed line card for excessive failures.

%CR10K_DIAG-5-PXFOVERSUB: PXF utilization is [dec]%, system is close to be 
overloaded. 

Explanation    Health Monitoring has detected that the sytem is about to be oversubscribed.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

CR10KBH

%CR10KBH-1-INITFAIL: [chars], initialization failure 

Explanation    Backhaul Ethernet hardware initialization failed.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CR10KBH-3-INVALID_DATA_INSTANCE: interface type [chars], slot [dec] subunit 
[dec] vc [dec] : [chars] 

Explanation    Data required to support the interface is not available.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CR10KBH-3-MAXADDR: [chars], total addresses greater than [chars] 

Explanation    The number of addresses in the address filter is too large.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CR10KBH-6-RADIAN_MACACCT_FULL: MAC accounting entries full for Radian in slot 
[chars] 

Explanation    Radian has a maximum of 256 ingress and 256 egress MAC accounting entries

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CR10KBH-3-RADIAN_VLANTCAM_EXCEEDED: [chars] vlanid [dec] Radian VLAN TCAM table 
full 

Explanation    Radian has a maximum of 4K vlan tcam entries.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%CR10KBH-3-SFPP_BAD_HW: Interface [chars], TenGigabit Ethernet module (SFP+) has 
bad HW 

Explanation    TenGigabit Ethernet SFP+ module can not be read. CRC error or tx fault.

Recommended Action    Insert a new TenGigabit Ethernet SFP+ module into the backhaul interface.

%CR10KBH-3-SFPP_MISSING: Interface [chars], TenGigabit ethernet module (SFP+) 
missing 

Explanation    TenGigabit Ethernet SFP+ module was removed from the backhaul interface.

Recommended Action    Insert a TenGigabit Ethernet SFP+ module into the backhaul interface.

%CR10KBH-3-SFPP_NON_TENGIGE: Interface [chars], Inserted module not TenGigabit 
ethernet module (SFP+) 

Explanation    A module inserted into the backhaul interface is not a TenGigabit Ethernet SFP+ module.

Recommended Action    Insert a TenGigabit Ethernet SFP+ module into the backhaul interface.

%CR10KBH-6-SFPP_OK: Interface [chars], 10GBASE-[chars] TenGigabit ethernet module 
(SFP+) inserted 

Explanation    TenGigabit Ethernet SFP+ module was inserted into the backhaul interface

Recommended Action    No action is required.

%CR10KBH-3-SFPP_SECURITY_FAIL: Interface [chars], TenGigabit Ethernet module 
(SFP+) is not CISCO approved 

Explanation    TenGigabit Ethernet SFP+ module has failed cisco-EEPROM security check.

Recommended Action    Insert an approved vendor SFP+ module into the backhaul interface.

%CR10KBH-3-SFPP_SPURIOUS: Interface [chars], TenGigabit Ethernet module (SFP+) is 
a duplicate spurious 

Explanation    TenGigabit Ethernet SFP+ module with duplicate vendor and serial number.

Recommended Action    Insert an approved vendor SFP+ module into the backhaul interface.

%CR10KBH-3-WIRING_ERR: Wrong wiring detected at [chars] interconnect 
port(portnum: [dec]), please correct it in order to use PRE5 10GE backhaul port 

Explanation    Local interconnect port link status mismatches with remote interconnect port link status.

Recommended Action    Use cable fiber to connect the corresponding interconnect ports between active and standby. Verify:
(1) If interconnect port is incorrectly used as backhaul port to connect to the up-link device.
(2) If the corresponding interconnect ports are not connected in order. That is, connect interconnect port n (n:0~3) on the active PRE with interconnect port n (n:0~3) on the standby PRE.

CWAN_SPA

The following are Constellation WAN ATM SPA error messages.

%CWAN_SPA-3-INTR_THROTTLE: Interface [chars] MAC interrupt was throttled. 
Reenabling MAC interrupts via one sec spa process

Explanation    MAC interrupt burst has occurred on one of the interfaces on the link daughter card. The error message indicates that a throttling mechanism has been applied to this port to avoid any operational damage that could be provoked by this event. The cause for this problem could be bad transceiver, highly frequent flapping optical signals, or mismatched path signals (for example, receiving 10GBASE-W signal on 10 gigabit ethernet LAN interface) and others.

Recommended Action    Check the interface configuration and received signal characteristics. Also verify the XFP transceiver and receive signal path to determine the 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

DHCPV6R

The following are DHCPV6R messages:

%DHCPV6R-3-INVALID_USR_LINKADDR: Invalid user specified link-address [IPv6 Address] idb [chars] in ipv6 dhcp relay CLI. Removng user specified invalid address from the CLI. 

Explanation    Invalid link address has been provisioned in the IPv6 relay destination CLI.

Recommended Action    Reduce other system activity to ease memory demands. If required, upgrade to a larger memory configuration.

%DHCPV6R-3-INVALID_USR_SRCADDR: Invalid user specified source-address [IPv6 Address] idb [chars] in ipv6 dhcp relay CLI. Removing user specified invalid address from the CLI and auto-computing source with SAS. 

Explanation    Invalid source address has been provisioned in the IPv6 relay destination CLI.

Recommended Action    Reduce other system activity to ease memory demands. If required, upgrade to a larger memory configuration.

DOT1X

The following are 802.1X authorization messages:

%DOT1X_ISSU-6-SESSION_NEGO_DELAYED: dot1x ISSU client takes [dec] milisec to 
complete 

Explanation    The 802.1X ISSU client is taking more than 30 seconds to complete ISSU negotiation.

Recommended Action    No action is needed.

DS

The following are downstream system messages:

%DS_PHY-3-RM_JIB_IF_ERROR: Remora hw reset failure - [chars] 

Explanation    Hardware reset of the DS PHY interface 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

DSG

The following are DSG messages:

%DSG-6-CFR_APPLIED: classifier <[dec]> is applied successfully 

Explanation    The classifier has been applied successfully.

Recommended Action    No action is required.

%DSG-5-CFR_CONFLICT: classifier <[dec]> is put into conflict state because of 
errors 

Explanation    The classifier has already been applied but you cannot update the classifier with changed destination IP address or source IP address because of errors. Hence, the classifier is assigned conflict state.

Recommended Action    No action is required.

%DSG-5-CFR_NOT_APPLIED: classifier <[dec]> cannot be applied because of errors 

Explanation    The classifier cannot be applied because of errors.

Recommended Action    No action is required.

%DSG-5-CFRRMTUNNEL: cfr [dec] becomes unresolved, it will be removed from the 
tunnel it belongs to 

Explanation    The cfr is unresolved and it has been removed from the tunnel it belongs to.

Recommended Action    No action is required.

%DSG-6-CFR_UPDATED: classifier <[dec]> is updated 

Explanation    The classifier has been updated.

Recommended Action    No action is required.

%DSG-5-DSG_INFO_DB_LOOKUP_FAILURE: Failed to find the entry from the DSG Info DB 
for ([chars], [chars], [chars]) 

Explanation    DSG Info DB lookup failed.

Recommended Action    No action is required.

%DSG-5-IDENTICAL_CFR: cfr [dec] and [dec] are identical 

Explanation    Both CFRs are identical.

Recommended Action    No action is required.

%DSG-5-ILLEGAL_MCASTADDR: IP address <[IP_address]> is not a multicast address or 
is a reserved multicast address 

Explanation    IP address is not a multicast address or is a reserved multicast address.

Recommended Action    No action is required.

%DSG-5-ILLEGAL_SOURCEADDR: IP address <[IP_address]> is an illegal source address 

Explanation    IP address is an illegal source address.

Recommended Action    No action is required.

%DSG-5-MAC_ADDR: cfr [dec] and cfr [dec] have the same destination IP address 
[IP_address], but different MAC addresses [enet] and [enet] 

Explanation    Both CFRs have same destination IP address but different MAC addresses.

Recommended Action    No action is required.

%DSG-5-NAME_CHANGED: hostname <[chars]> is changed from <[IP_address]> to 
<[IP_address]> 

Explanation    IP address of a hostname is changed.

Recommended Action    No action is required.

%DSG-6-NAME_RESOLVED: hostname <[chars]> is resolved as <[IP_address]> 

Explanation    DNS query for a hostname is successful.

Recommended Action    No action is required.

%DSG-5-NAME_UNRESOLVED: hostname <[chars]> cannot be resolved 

Explanation    DNS query for a hostname is not successful.

Recommended Action    No action is required.

%DSG-5-SEMAPHORE_ERROR: failed to obtain the DSG semaphore 

Explanation    Failed to get the semaphore.

Recommended Action    No action is required.

%DSG-5-SOURCE_LEN: cfr [dec]: source IP address [IP_address] and source prefix 
length [dec] don't match 

Explanation    The source IP address and source prefix length of the CFR does not match.

Recommended Action    No action is required.

%DSG-5-SSM_SOURCE_PREFIX: destination IP address is <[IP_address]> in SSM range, 
source IP address prefix length must be [dec] 

Explanation    The destination IP address is in SSM range and the source IP address prefix length must be dec.

Recommended Action    No action is required.

%DSG-5-SSM_SOURCE_ZERO: destination IP address is <[IP_address]> in SSM range, 
source IP address cannot be zero 

Explanation    The destination IP address is in SSM range and the source IP address cannot be zero.

Recommended Action    No action is required.

%DSG-5-STATICJOINERR: cfr [dec] cannot be enabled, because there already exists a 
non-DSG static join for (S, [IP_address]) or (*, [IP_address]) in interface 
[chars] 

Explanation    The CFR cannot be enabled because a non-DSG static join already exists for the multicast group.

Recommended Action    No action is required.

DTSEC

%dtsec-3-BAD_GBIC_EEPROM: [chars] - GBIC contains a bad EEPROM 

Explanation    Interface contains a GBIC with a bad EEPROM and the link is down.

Recommended Action    Ensure the GBIC type is compatible with the interface. Verify that the GBIC was obtained from Cisco or a supported vendor.

%dtsec-1-BAD_IDB: Invalid Interface Descriptor Block 

Explanation    The driver tried to fetch the IDB interface but failed.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%dtsec-1-BAD_PARTICLE: Problem getting particle size 

Explanation    The driver was unable to get the particle size for this interface.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%dtsec-1-BAD_POOL: Could not init buffer pools 

Explanation    The driver failed to get a pool of buffers from IOS.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%dtsec-1-BAD_STRUCT: Could not initialize structure 

Explanation    The driver failed to initialize a structure.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%dtsec-3-DUPLICATE: [chars] - duplicate GBIC 

Explanation    The GBIC module for the interface specified in the error message is a duplicate of another GBIC in the system. Both modules are disabled.

Recommended Action    Remove the duplicate module. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%dtsec-1-INITFAIL_NOMEM: [chars], initialization failed, no buffer memory 

Explanation    The Ethernet port initialization failed due to insufficient memory.

Recommended Action    The router requires more packet memory. Consider an upgrade. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%dtsec-2-NOISL: Interface [chars] does not support ISL 

Explanation    ISL is not supported on the specified interface hardware.

Recommended Action    No action is required.

%dtsec-3-NOT_SUPPORTED: [chars] - unsupported GBIC 

Explanation    The GBIC module for the interface specified in the error message is not a Cisco approved module. The module is disabled.

Recommended Action    Replace the module with a Cisco approved GBIC module. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%dtsec-3-TOOBIG: [chars], packet too big ([dec]), from [enet] 

Explanation    The interface detected a packet larger than what is defined by MTU.

Recommended Action    Check other station MTU setting. No action is required.

%dtsec-3-UNKNOWN_GBIC: [chars] - Unknown GBIC type 

Explanation    Link is down because the interface contains unknown GBIC type.

Recommended Action    Ensure that the GBIC type is compatible with the interface. Verify that the GBIC was obtained from Cisco or an approved vendor.

ESM20

The following are ESM20 line card messages:

%ESM20-5-PEBOARD_RECOVERY: Recovering from FPGA initialization failure on PE Board 
Slot:[dec]. 

Explanation    Some ESM20 boards exhibit a condition in which certain FPGAs on the PE boards like ACLFPGA, PEFPGA fail to initialize. The issue is seen because of timing characteristic exhibited by power supply device on the card.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

ETSEC

The following are ETSEC controller messages.

%ETSEC-1-BAD_IDB: Invalid Interface Descriptor Block 

Explanation    The driver fails while trying to fetch the Interface Descriptor Block (IDB) of the interface.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%ETSEC-1-BAD_INIT_IDB: Fail to initialize IDB eTSEC port [dec] 

Explanation    The IDB has failed to initialize.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%ETSEC-1-BAD_PAK_ALLOCATION: Unable to acquire pak system resources. 

Explanation    The driver fails to allocate pak memory.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%ETSEC-1-BAD_POOL: Could not create the buffer pools 

Explanation    The driver has failed to create the buffer pool.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%ETSEC-3-BAD_INIT_PARSER: Fail to initialize eTSEC parser 

Explanation    The eTSEC parser has failed to initialize.

Recommended Action    Reload the Cisco CMTS router. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%ETSEC-3-ERROR_INT_CAUSE: eTSEC event error: [chars] 

Explanation    An eTSEC error event has 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%ETSEC-2-EXCEPTION : Fatal Error, Interface [chars] not transmitting 

Explanation    The software detected critical error and recovery failed, resulting in a system crash.

Explanation    Collect the crashinfo files, system logs and console messages.

%ETSEC-3-NO_SYNC: ETSEC Port [dec] :TX/RX clock sync not achieved : Register Value 
:[hex] 

Explanation    The software could not detect RX/TX sync lock.

Recommended Action    The system needs to crash to recover. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%ETSEC-4-PAK_TOO_BIG: PAK TOO BIG interface [chars] size [dec] 

Explanation    The egress packet is too big for the interface.

Recommended Action    If this message occurs, 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%ETSEC-3-RECOVER_TX : Interface [chars] TX workaround invoked 

Explanation    The software detected the interface was not transmitting packets. The workaround patch has been invoked.

Recommended Action    No action is required.

%ETSEC-3-RESTART : Interface [chars] Restarted Due to [chars] Error 

Explanation    The software detected critical error and etsec driver was restarted to restore EoBC traffic flow.

Recommended Action    The system will recover. No action is required.

FABRIC_INTF

This section describes system error messages generated by the fabric interface ASIC.

%FABRIC_INTF_ASIC-5-FABRICSYNC_REQ: Fabric ASIC [dec]: Fabric sync requested 
after [dec] sync errors on serial channel [dec] 

Explanation    The line card requested that the supervisor engine resynchronize its fabric interface ASIC.

Recommended Action    No action is required.

FILESYS

%FILESYS_RFS-4-RFS_REQUEST_TIMEOUT: Timeout has occurred while executing the RFS 
request on file [chars] [[dec]]. 

Explanation    Timeout occured at the client side while executing an RFS request sent to the server.

Recommended Action    No action is required.

FM

The following are Feature Manager (FM) messages:

%FM-4-TCAM_MASK: Hardware TCAM MASK entry capacity exceeded 

Explanation    The hardware TCAM has exhausted its available storage and does not have the capacity to store all configured ACLs.

Recommended Action    If the ACL merge algorithm is currently BDD, storage space can be freed by changing the merge algorithm to ODM. Perform the following steps to change the merge algorithm to ODM:

1. Execute the show fm summary command to determine the current merge algorithm.

2. Execute the mls aclmerge algorithm odm command to change the merge algorithm from BDD to ODM

3. Enter the mls tcam priority command to prioritize interfaces for hardware switching.

4. Attempt to share the same ACLs across multiple interfaces in order to reduce TCAM resource contention.

5. If Server Load Balancing is configured, enter the mls ip slb search wildcard rp command to reduce the amount of TCAM space used by Server Load Balancing. After entering the command, Server Load Balancing will increase its utilization of the Route Processor.

%FM-4-TCAM_ENTRY: Hardware TCAM entry capacity exceeded

Explanation    The hardware TCAM has exhausted its available storage.

FMEA

The following are FMEA (Failure Mode and Effects Analysis) messages:

%FMEA-4-DS_JIB_ERRLOG: DS JIB Santana FPGA Err log [chars] [chars] 

Explanation    Downstream JIB Santana FPGA FMEA log error.

Recommended Action    No action is needed. This is a minor non-fatal recoverable failure event.

FPD_MGMT

This section describes system error messages generated by the FPD image.

%FPD_MGMT-4-CFG_NOT_SYNCED : Failed to sync "[chars]" command to standby: [chars] 

Explanation    A FPD configuration command failed to get synchronized to standby route processor due to the indicated error condition.

Recommended Action    Re-configure the command with a file system that is supported on both standby and active RP. To find out if a specific file system is also supported on standby RP, the dir ? command can be used to display a list of file system supported on both standby and active RP.

GE_LINK

The following are the Gigabit Ethernet link messages:

%GE_LINK-5-AUTONEGOTIATION: Waiting for completed A/N in GE pair [dec] primary 
port 

Explanation    Switchover is deferred as the auto negotiation has not completed.

Recommended Action    If the problem persists, check the peer Gigabit Ethernet port.

%GE_LINK-3-MDIO_ERR: [chars] error for controller [dec] port [dec] 

Explanation    Error in accessing the GigE Transceiver.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%GE_LINK-6-PHY_EVENT: PHY [chars] event detected for phy [dec] port [dec] 

Explanation    Link Event is detected for the non-SFP port of GigE Transceiver.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%GE_LINK-3-SW_ERR: [chars] error in GE pair [dec] port [dec] 

Explanation    This is an internal 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%GE_LINK-4-SWITCHOVER_ERR: switchover to primary port in GE pair is suppressed due 
to port instability 

Explanation    Switchover is temporarily suppressed due to flapping GE primary link.

Recommended Action    Verify the GE link.

%GE_LINK-5-SWITCHOVER_PRI: primary port set active for GE pair [dec] 

Explanation    GE link is restored for the primary port.

Recommended Action    If you are not expecting this error, check for the secondary port in GE pair.

%GE_LINK-5-SWITCHOVER_SEC: secondary port set active for GE pair [dec] 

Explanation    GE link is lost for the primary port

Recommended Action    If you are not expecting this error, check the secondary port in GE pair.

%GE_LINK-5-UPDOWN: Link status is [chars] for GE pair [dec] port [dec] 

Explanation    Link Status Change is detected for GigE Transceiver.

Recommended Action    If you are not expecting this error, check the GigE link.

GENERAL

This section lists system error messages generated by the C10K route processor subsystem.

%GENERAL-3-MRI_DELETE_ERR: [chars] 

Explanation    MRI deletion failed at route processor.

Recommended Action    No action is required.

HA_EM

This section lists system error messages generated by the High Availability (HA) Embedded Event Manager (EEM.)

%HA_EM-4-FMPD_NO_ACTION: No action configured for applet test_applet

Explanation    No action has been configured for this applet.

Recommended Action    Configure at least one action for this applet.

%HA_EM-6-FMS_SWITCH_HARDWARE: fh_io_msg: Policy has requested a hardware switchover

Explanation    An EEM policy requested that a hardware switchover occur.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%HA_EM-7-FMS_SWITCH_FAIL: fh_switch_hardware: The system is unable to switch to 
standby processor. Switchover cancelled.

Explanation    Switchovers must occur when STANDBY is available and ready.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

HCCP

This section lists system error messages generated by the Hot Connection to Connection Protocol (HCCP) redundancy subsystem.

%HCCP-3-BADCHAN: Grp [dec] Mbr [dec] [chars]: channel switch "[chars]" failed, 
retries exhausted. 

Explanation    The indicated member of the specified HCCP group has been notified of a failure in its channel switch.

Recommended Action    Verify the connections between the channel switch and CMTS. Verify that the channel switch is online and functioning.

%HCCP-3-BADMSG: Grp [dec] Mbr [dec] [chars]: received wrong type of 
message-[chars].

Explanation    The indicated member of the specified group received an inappropriate HCCP message for its current state of Working or Protect.

Recommended Action    Check the configuration of both the Working and Protect interfaces. In particular, check that one interface is configured as the Working interface, and the other is configured as the Protect interface.

%HCCP-3-BADSTATE: [chars] Grp [dec], inconsistent state!!

Explanation    The indicated member of the specified group has detected an HCCP state inconsistency in the indicated interface after a switchover. This typically happens because the interface is not in the state that the processor expects it to be, perhaps because the interface did not properly respond to the latest configuration commands.

Recommended Action    Reset the indicated interface to resynchronize the interfaces. If this problem occurs frequently, upgrade to Cisco IOS Release 12.2(11)BC3 or a later 12.2 BC release.

%HCCP-3-CFG_FAIL: Configuration failed. [chars] 

Explanation    An error occurred during configuration.

Recommended Action    If you see this message during line card switch over or revert back, compare the working card and protect card configuration to identify the failed command parse. 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). Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%HCCP-3-CFR_LIST: Remove an element before destroy [chars]: cfrid=[int], 
direction=[int], state=[dec], ip_sadd=[IP_address], 
ip_daddr=[IP_address],dest_macaddr=[enet], src_macaddr=[enet], ip_prot=[int], 
eport=[int] 

Explanation    An element from interdb cfr_list was removed before destroying the list.

Recommended Action    Reset the system.

%HCCP-3-CONFIGSYNC_ERROR: Enable config-sync when it is not disabled 

Explanation    The software is trying to enable the already enabled (set to 0) HCCP internal flag "configsync".

Recommended Action    Reset the system.

%HCCP-3-CTRL_PLANE_READY: HCCP ctrl plane for [chars] member [dec] is ready. 

Explanation    HCCP control plane is ready to receive lc2rp(line card to route processor) sync for the group(s) in the list.

Recommended Action    No action needed.

%HCCP-3-DATA_PLANE_READY: HCCP data plane for [chars] member [dec] is ready. 

Explanation    HCCP lc2rp sync for the group(s) in list is completed.

Recommended Action    No action needed.

%HCCP-3-INVALID_PROTECT: ERROR!LC-RED: License of protect card [int]/[int] is 
incompatible with working card [int]/[int]. 

Explanation    The protect line card license is incompatible with the working line card.

Recommended Action    Upgrade the license on the protect line card.

%HCCP-3-MISS_CTRLPLANE_READY: HCCP [chars] member [dec]: Ctrl Plane Ready is 
missed because [chars] 

Explanation    HCCP control plane ready is missed due to control plane error or message missed.

Recommended Action    Check the status of the control plane.

%HCCP-3-MISS_DATAPLANE_READY: HCCP [chars] member [dec]: Data Plane Ready is 
missed because [chars] 

Explanation    HCCP data plane ready is missed due to data plane error or message missed.

Recommended Action    Check the status of the data plane.

%HCCP-3-MISS_STATICSYNC_DONE: HCCP [chars] member [dec]: Static Sync Done is 
missed because [chars], Redo static sync through CLI. 

Explanation    HCCP static sync could not be performed because switchover occurred, or the STATICSYNCDONE message was missed.

Recommended Action    Perform static sync through CLI.

%HCCP-3-OUT_OF_ORDER_LC_MSG: HCCP slot [dec] member [dec] status [chars]: NULL 
hp/mp encountered. 

Explanation    HCCP software has detected that the messages are out of order.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%HCCP-3-OUT_OF_ORDER_LC2RP: Grp [dec] Mbr [dec] status [chars]: Received LC to RP 
sync in standby state.

Explanation    The indicated member of the specified group has received an HCCP SYNC message, instructing it to synchronize its configuration with the processor card. The interface has rejected the message because the interface is in the standby state. This can indicate either a software failure, or that the Working and Protect interfaces are out of sync.

Recommended Action    Verify that both interfaces are installed and configured. Verify the CMTS is running released software. 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.

%HCCP-3-OUT_OF_ORDER_MSG: Grp [dec] Mbr [dec] status [chars]: NULL hp encountered.

Explanation    The indicated member of the specified group has received HCCP messages that are out of their proper order. This can indicate either a software failure, or that the Working and Protect interfaces are out of sync.

Recommended Action    Verify that both interfaces are installed and configured. Verify the CMTS is running released software. Upgrade to Cisco IOS Release 12.2(11)BC3 or later 12.2 BC release. If the problem persists, use the show interface cable key sid and show interface cable key mac commands to collect information about the cable modem with the problem. You can also turn on BPI+ debugging using the debug cable privacy and debug cable bpi commands.

%HCCP-3-PROTECTING_TOO_MANY: Grp [dec] Mbr [dec] status [chars]: Protecting too 
many Workings.

Explanation    The indicated member of the specified group has detected that the Protect interface has been configured to protect too many Working interfaces.

Recommended Action    Reconfigure the Protect interface so that it is protecting fewer Working interfaces. In particular, verify that the same Protect interface is not protecting multiple interfaces on the same cable interface line card (because if the Working card goes down, the Protect interface will be able to replace only one of the Working interfaces). If this is already the case, verify that the CMTS is running released software. If the problem persists, use the show interface cable key sid and show interface cable key mac commands to collect information about the cable modem with the problem. You can also turn on BPI+ debugging using the debug cable privacy and debug cable bpi commands.

%HCCP-4-NOREVERT: Grp [dec] Mbr [dec]: Revert operation cancelled.

Explanation    The indicated HCCP group member did not attempt to revert back to the Working interface. A possible reason for this could be that keepalive messages to the Working interface were not returned, indicating a keepalive failure or a possible disconnection of the cables.

Recommended Action    Check the upstream and downstream coaxial cables to the Working interface have not been disconnected or cut. Check the configuration of the interface and ensure that keepalives have not been disabled using the no keepalive command. If necessary and if possible, perform an OIR on the Working Interface card, removing it and reinserting it. After fixing the problem, you can either wait for the protect interface to revert to the working interface, or you can perform a manual revert using the hccp switch command.

%HCCP-4-NOSWOVER: HCCP [chars] Mbr [dec]: switchover is not triggered because 
[chars]. 

Explanation    HCCP line card member will not attempt to revert back to the working interface.

Recommended Action    This issue may have occurred because last switchover is not finished. Ensure that the current HCCP is in warm state.

%HCCP-4-PEERBUSY: HCCP [chars] member [dec] Switchover aborted. Protect [chars] 
is already ACTIVE for member [dec]. 

Explanation    HCCP software has detected that the protect line card is already in Active state for another working line card.

Recommended Action    Release the protect line card by reverting back to the other working line card and perform this switchover again.

%HCCP-5-CHANOFF: Grp [dec] Mbr [dec] [chars]: turning off channel.

Explanation    The indicated member of the specified group has turned off its channel switch.

Recommended Action    No action is needed (except to verify that connectivity has been preserved).

%HCCP-5-CHANON: Grp [dec] Mbr [dec] [chars]: turning on channel.

Explanation    The indicated member of the specified group has turned on its channel switch.

Recommended Action    No action is needed (except to verify that peer relinquishes the channel).

%HCCP-5-HELLO: Grp [dec] Mbr [dec] [chars]: HCCP Hello caused state transition. 

Explanation    The indicated Protect interface of the specified group received an internal Hello message from the Working interface, but the message indicates that the operational states of the Working and Protect interfaces are inconsistent.

Recommended Action    No action is needed, because the two interfaces will transition to the appropriate states.

%HCCP-5-HELLO_ACK: Grp [dec] Mbr [dec] [chars]: HCCP Hello ACK initiating 
switchover. 

Explanation    The indicated Protect interface of the specified group received an internal Hello Acknowledgement message from the Working interface, but the message indicates that the operational states of the Working and Protect interfaces are inconsistent.

Recommended Action    No action is needed, because the two interfaces will transition to the appropriate states.

%HCCP-5-HOLDTIMER: Grp [dec] Mbr [dec] [chars]: HCCP Hold Timer Expired. 

Explanation    The internal hold timer used by the HCCP system has expired, without the required message being sent or received by the indicated interface. This typically indicates that one or more HCCP messages was lost, probably because the CMTS processor has run out of resources, such as memory, or that the processor is at or near 100 percent utilization and cannot process all of the HCCP messages.

Recommended Action    Verify that the CMTS is operating normally. Use the show process command to display the currently running processes and whether any of the processes are overusing resources. If necessary, reboot the CMTS or add additional memory to the processor card.

%HCCP-5-LC_ACTIVE: HCCP [chars] Mbr [dec] [chars]: change state to active due to: 
[chars]. 

Explanation    HCCP line card member has notified that it has changed to active, and a reason is given.

Recommended Action    Make sure peer relinquishes the channel.

%HCCP-5-LC_STANDBY: HCCP [chars] Mbr [dec] [chars]: change state to standby due 
to: [chars]. 

Explanation    HCCP line card member has notified that it has changed to standby, and a reason is given.

Recommended Action    Ensure that the peer controls the channel.

%HCCP-5-STANDBY: Grp [dec] Mbr [dec] [chars]: change state from active to standby: 
[chars] 

Explanation    The indicated member of the specified group has changed from active to standby because it received the indicated message.

Recommended Action    No action is needed (except to verify that connectivity has been preserved).

%HCCP-5-SWITCHOVERREADY: Grp [dec] Mbr [dec] [chars]: ready to switchover.

Explanation    The indicated member of the specified group is ready to switchover again because its wait-to-restore timer has expired. This timer begins counting down after a switchover, so that another switchover cannot occur until the current switchover has completed. When this timer has expired, it indicates that the system has stabilized and is ready to complete another switchover if needed.

Recommended Action    No action is required.

%HCCP-6-HCCP_CHAN_RFSW_SNMP_ERROR: [chars] error: [chars]. 

Explanation    There were problems with SNMP in the HCCP channel 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%HCCP-6-HCCP_CHAN_RFSW_SNMP_INFO: [chars]: [chars]. 

Explanation    Status of SNMP response to set cmd to rfswitch

Recommended Action    If the response is "Fail", check connectivity to the RF Switch, and telnet to check RF switch status.

%HCCP-6-IGNORE_MD_UP: The member [chars] [dec][[dec]] is already up, ignore 
repeated event. 

Explanation    The mac domain is already active, ignore the repeated up events.

Recommended Action    The indicated member of the specified HCCP group has been notified of a failure in its channel switch.

%HCCP-6-LC_RPLC_CFGSYNC_CONFIG: HCCP [dec] [dec] [chars]: LC [chars] 

Explanation    The attempted HCCP line card configuration recovery failed because the last rplc_cfgsync configuration was not successful.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%HCCP-6-LC_RPLC_CFGSYNC_CONFIG_PARSER: Parser Error: [dec] 

Explanation    The attempted HCCP line card configuration recovery had a parser 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%HCCP-6-LC_RPLC_CFGSYNC_CONFIG_RECOVER: HCCP [dec] [dec] [chars]: LC [chars] 
rplc_cfgsync configuration recover is succeed. 

Explanation    The attempted HCCP line card configuration recovery succeeded.

Recommended Action    No action is needed.

%HCCP-6-STATICSYNC_COMPLETED: HCCP static sync for [chars] member [dec] is 
completed in [dec] ms. 

Explanation    HCCP static sync for the group(s) in list is completed.

Recommended Action    No action is needed.

HDSPA

%HDSPA_LIC-3-BOOLTIMEOUT: Fail to wait for boolean [chars] 

Explanation    The boolean was not set to true before timeout.

Recommended Action    Please check the process that set this boolean.

%HDSPA_LIC-3-CSB_FAIL: [chars] failed for [chars] 

Explanation    An attempt to parse a license-related CLI failed.

Recommended Action    Check the HDSPA license details and contact your Cisco technical support representative and provide the representative with the gathered information.

%HDSPA_LIC-5-EXCEED_HW_CAP: DS_License installed([dec]) on a single HDSPA exceeds 
the max hardware capability([dec]). 

Explanation    More number of licenses than required or usable. This could happen after license rehost.

Recommended Action    Transfer the excess licenses to another PRE.

%HDSPA_LIC-5-EXCESS_LIC: Installed license count([int]) exceeds hardware 
capability([int]) 

Explanation    More number of licenses than required or usable.

Recommended Action    If excess number of licenses was obtained intentionally or due to RMA, transfer the excess SPA_DS_License licenses to another PRE. Else, contact your Cisco technical support representative.

%HDSPA_LIC-3-FLASHERROR: [chars] 

Explanation    Unexpected flash error occured.

Recommended Action    Check SPA license flash.

%HDSPA_LIC-6-NOSHUT: [chars] channel [int] has been restored to no shut 

Explanation    Restored previously shut down channels to no shut state.

Recommended Action    No action is required.

%HDSPA_LIC-6-NOSHUTFAIL: [chars] channel [int] no shut is not allowed due to 
insufficient licenses 

Explanation    Unable to no shut the channel due to insufficient number of licenses.

Recommended Action    Check the number of licenses installed.

%HDSPA_LIC-6-OUT_OF_RANGE: SPA [int]/[int] [chars] is already [int] 

Explanation    License counters have reached boundary condition. Internal error.

Recommended Action    Check license and contact your Cisco technical support representative and provide the representative with the gathered information.

%HDSPA_LIC-6-SHUT: [chars] channel [int] has been shutdown due to insufficient 
licenses 

Explanation    Unable to no shut the Channel due to insufficient number of licenses.

Recommended Action    Check the number of licenses installed.

HQF

This section describes error messages generated for the Hierarchal Queuing Framework (HQF) Toaster Mapper.

%HQF_MAP_TT-3-EREVENT: [chars]-MSG_TRACEBACK

Explanation    A software programming error for the HQF Toaster Table (TT) Network Processor (NP) Mapper was detected.

Recommended Action    This software programming error is not considered fatal to the operation of the TT NPs. The software is designed to detect and report the error condition. If the error persists, reset the device, record the output from the following commands, and provide this information to your technical support representative:

show tech

show log

%HQF_MAP_TT-3-HQF: [chars]-MSG_TRACEBACK

Explanation    A software programming error for the HQF TT NP Mapper was detected.

Recommended Action    This software programming error is not considered critical to the operation of the TT NPs. The software is designed to detect and report the error condition. If the error persists, reset the device, record the output from the following commands, and provide this information to your technical support representative:

show tech

show log

%HQF_MAP_TT-6-HQF_INFO_OVERSUBSCRIPTION_CLEARED: [chars]

Explanation    The HQF oversubscription condition on the interface has cleared.

Recommended Action    No action is required.

%HQF_MAP_TT-6-HQF_INFO_OVERSUBSCRIPTION_DETECTED: [chars]

Explanation    The router configuration has resulted in an oversubscription at the HQF level. Oversubscription can occur because of shaping in a parent policy-map, bandwidth being reserved for other policy-maps, or a combination of all of the above.

Recommended Action    The router automatically modifies its configuration to deal with oversubscription. However, if this condition is unexpected, verify the configuration to make the appropriate changes.

%HQF_MAP_TT-4-HQF_WARN_RL_1S: [chars]- MSGDEF_LIMIT_FAST

Explanation    A warning was generated in the HQF TT NP Mapper because the router has not been configured properly.

Recommended Action    Verify the router configuration to make sure it is within the system limits.

%HQF_MAP_TT-3-NOMEM:[chars]-Memory Allocation Failure

Explanation    The HQF TT NP Mapper could not allocate the required memory to all the features and related entities enabled via the configuration.

Recommended Action    This error indicates that more memory is required to service all the features and related entities enabled via the configuration. Try to reload the IOS image. If the error persists, record the output from the following commands, and provide this information to your technical support representative:

show tech

show log

%MCE_HQF_NP_CLIENT-3-ALLEXISTS: [chars]-NP Client Previously Defined Software 
Element

Explanation    The NP Client has detected a previously defined software element.

Recommended Action    Try to reload the IOS image on the affected card or platform. If the error persists, record the output from the following commands, and provide this information to your technical support representative:

show tech

show log

%MCE_HQF_NP_CLIENT-2-FATAL: [chars]-MSG_TRACEBACK|MSG_PROCESS-NP 
Client-[decimal]

Explanation    The NP Client software detected a critical programming error.

Recommended Action    If the error persists, record the output from the following commands, and provide this information to your technical support representative:

show tech

show log

%MCE_HQF_NP_CLIENT-3-HQF_NP_CLIENT_GENERAL: [chars]-MSG_TRACEBACK-error detected

Explanation    A software programming error for the HQF NP Client was detected.

Recommended Action    This software programming error is not considered critical to the operation of TT NPs. The software is designed to detect and report the error condition. If the error persists, reset the affected device, record the output from the following commands, and provide this information to your technical support representative:

show tech

show log

%MCE_HQF_NP_CLIENT-3-INITFAIL: [chars]-NP Client Initialization Failed

Explanation    The NP Client could not initialize the required memory to service one or more Network Processors.

Recommended Action    This error indicates that an incompatibility exists between the NP firmware and the associate IOS image. Try to reload the IOS image on the card or platform. If the error persists, record the output from the following commands, and provide this information to your technical support representative:

show tech

show log

%MCE_HQF_NP_CLIENT-3-MAXEXCEED: [chars]-NP Client Max Services Exceeded

Explanation    The maximum number of NP Client services has been exceeded.

Recommended Action    Change the router configuration to reduce the number of services configured. If the error persists, record the output from the following commands, and provide this information to your technical support representative:

show tech

show log

%MCE_HQF_NP_CLIENT-3-METADATA: [chars]-failed

Explanation    Processing of the metadata for the specified Network Processor (NP) failed. The specified Network Processor cannot operate.

Recommended Action    Try to reload the NP microcode. If the error persists, record the output from the following commands, and provide this information to your technical support representative:

show tech

show log

%MCE_HQF_NP_CLIENT-3-NOMEM: [chars]-Memory Allocation Failure

Explanation    The NP Client could not allocate the required memory to service one or more Network Processors.

Recommended Action    This error indicates that more memory must be installed on the card or platform to service all the features and related entities enabled via the configuration. Try to reload the IOS image on the affected card or platform. If the error persists, record the output from the following commands, and provide this information to your technical support:

show tech

show log

%MCE_HQF_NP_CLIENT-3-NOTFOUND: [chars]-NP Client Software Element Not Found

Explanation    The NP Client could not locate a required software element.

Recommended Action    Try to reload the IOS image on the card or platform. If the error persists, record the output from the following commands, and provide this information to your technical support representative:

show tech

show log

%MCE_HQF_NP_CLIENT-3-NOTSUP: [chars]-NP Client Feature Not Supported

Explanation    The NP Client does not support the specified feature.

Recommended Action    Verify that the correct IOS image is loaded on the card or platform for the configured features. If the error persists, record the output from the following commands, and provide this information to your technical support representative:

show tech

show log

%MCE_HQF_NP_CLIENT-3-NPUNKNOWN: [chars]-NP Client Unsupported NP

Explanation    The NP Client detected an unsupported NP.

Recommended Action    Verify that the correct IOS image is loaded on the affected card or platform for the configured features. If the error persists, record the output from the following commands, and provide this information to your technical support representative:

show tech

show log

I2C

%I2C-3-ACCESS_ERR: I2C access error ([chars]) for device [dec] 

Explanation    I2C device initialization 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%I2C-3-CONFIG_ERR: I2C config failure ([chars]) for device [dec] value [hex] 

Explanation    I2C device configuration 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%I2C-5-LTC4306: sanity check failed: device [hex] channel [dec] action [chars] 
retry [dec] read back [hex] 

Explanation    Sanity check 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

IGMP

%IGMP-3-NO_DNS_SERVER: No DNS server is configured. DNS-based SSM mapping should 
be disabled if no DNS server is configured. 

Explanation    There is no DNS server present. Processing IGMP packets may be delayed if the DNS-lookup is done continuously.

Recommended Action    Disable DNS-based SSM mapping if there is no DNS-server present in the network. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%IGMP-3-QUERY_INT_MISMATCH: Received a non-matching query interval [dec], from 
querier address [IP_address] 

Explanation    The IGMP version has a mismatch between routers.

Recommended Action    Configure both the interfaces with the same IGMP version. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%IGMP-4-NO_INPUT: IGMP packet without input interface received from [IP_address] 
for [IP_address] 

Explanation    An unexpected IGMP packet without input interface was received.

Recommended Action    Copy the source and destination information in the syslog. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

IFDAMP

%IFDAMP-5-UPDOWN : interface [chars] update [chars] state to [chars], interface 
is [chars]suppressed 

Explanation    The dampening interface state is changed.

Recommended Action    No action is required.

%IFDAMP-5-ZERODELAY : dampening reuse timer is updated with 0 delay time 

Explanation    Inconsistency of dampening reuse timer wheel.

Recommended Action    No action is required.

IFMGR

The following are Interface Manager messages.

%IFMGR-3-DUP_IFINDEX : Duplicate ifIndex ([dec]) found for ifDescr "[chars]"; 
exists in ifTable for ifDescr "[chars]". 

Explanation    Interfaces have same ifIndex in IF-MGR assigned list. The second interface registered with IF-MGR will be assigned with new index.

Recommended Action    1. No Action, if ifIndex persist is not required. 2. Reload the standby RP, if ERR msg is observed only in the standby RP. 3. Reload the router with the proper ifindex-table and IOS version.

IP

%IP-3-NOOUTINTF: Output interface not available. source address: [IP_address], 
destination address: [IP_address], routing type: %u

Explanation    The output interface for the packet is 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

IPC

%IPC-6-KEEPALIVE: Rcvd keepalive from seat [hex] msglen=[dec] 

Explanation    An IPC Keepalive message is being sent every 10 seconds.

Recommended Action    This is normal behavior.

IPCGRP

This section describes error messages generated by the subsystem that manages interprocess communications (IPC) messages with the Gigabit Route Processor (GRP) on the PRE1 module on the Cisco uBR10012 router. Some of these messages can also appear on a Cisco uBR7246VXR router that is using a Broadband Processing Engine (BPE) cable interface line card, such as the Cisco uBR-MC16U/X and Cisco uBR-MC28U/X cards.

These IPC messages control the traffic that is passed between the processor card and line cards, as well as provide CEF forwarding information, traffic statistics, and management and control information.

%IPCGRP-2-LC_LC_BPFE_ERROR: LC backplane fast ethernet to [dec]/[dec] is down for 
[dec] polling intervals

Explanation    LC to LC fast ethernet link is down between the given line cards.

Recommended Action    Perform the following steps:

1. Execute the show controllers FastEthernet command and collect the output.

2. Execute the test cable etsec loopback bpfe command in that order, multiple times, from the line card which is affected.

3. With this gathered information 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.

%IPCGRP-2-LC_LC_IPC_ERROR: LC IPC connection to [dec]/[dec] is down for [dec] 
polling intervals on the backplane fast ethernet 

Explanation    LC to LC IPC is not established between the given line cards

Recommended Action    Perform the following steps:

1. Execute the show controllers FastEthernet command and collect the output.

2. Execute the test cable etsec loopback bpfe command in that order, multiple times, from the line card which is affected.

3. Ensure that the debug cr10k-clc ipc is turned on.

4. Execute the show cable oir-log command and collect the logs and output.

5. With this gathered information 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.

%IPCGRP-3-CR10KIPC_INITFAIL: CR10K CLC IPC UP Retries Exhausted 

Explanation    The platform IPC layer is taking a long time to initialize.

Recommended Action    Report this occurrence to engineering. Use the topic to search for a similar DDTS. If you could not find a similar DDTS, write a DDTS for this problem.

%IPCGRP-6-BADCRDST: Unknown line card OIR state, [dec].

Explanation    The specified line card was found in an invalid OIR state. The valid OIR states are as follows:

NONE—The line card is initializing.

BOOTED—The line card has booted its Cisco IOS software image and is initiating IPC communications with the processor module.

ALIVE—The line card has initialized and communicating with the PRE1 module.

An known OIR state could indicate that the line card is not running the same Cisco IOS software release as the processor module, and that the processor module is sending IPC messages that are not recognized by the line card.

Recommended Action    Verify that you are running released software on the Cisco CMTS. If so, reload the line card using the microcode reload command or by removing and reinserting the line card. If the problem persists, reload the processor module.

%IPCGRP-6-BADCRDTYP: The PRE thinks the line card has a type other than the actual 
type, actual [dec], PRE [dec]. 

Explanation    The processor module lists the specified card as being a different type of card than its actual type. This could occur during an OIR process, when a card of one type is being replaced by a card of another type, or during initial boot when the PRE1 module is attempting to download a software image to the line card.

Recommended Action    No action is needed as the processor module automatically restarts the initialization for the line card. If the problem persists, remove and reinsert the line card. Verify that you are running released software on the Cisco CMTS.

%IPCGRP-6-BADIMGCKSUM: The downloaded image has a bad checksum, required 0x[hex], 
actual 0x[hex] 

Explanation    A line card downloaded a software image that had a bad checksum. Typically, the line card images are integrated into the Cisco IOS software for the router, and a bad checksum would indicate a transient problem on the network between the processor module and the line card, which should not happen. This problem might occur if a new image is being manually downloaded to the line card, or if the image file itself has been corrupted before the transfer.

Recommended Action    No action is needed, typically because the card will reattempt the download. If the problem persists, reload the Cisco IOS software on the router to force the line cards to reload the card images that are part of that particular image.

%IPCGRP-6-BARENBDISAB: Barium interface [chars]

Explanation    The Barium interface, which is the ASIC that provides the interface between a line card and the Cisco uBR10012 backplane, has been either enabled or disabled.

Recommended Action    No action is needed, because this is a normal part of the initialization or OIR process.

%IPCGRP-6-CLCREBOOT: Cable Linecards reset due to "[chars]". 

Explanation    This message is generated by the PRE when one or all line cards have been reloaded.

Recommended Action    No action is needed.

%IPCGRP-3-CMDOP: IPC command [integer] (slot[integer]/[integer]): [chars]

Explanation    This message indicates the specified IPC command processing operational error occurred with the specified line card.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%IPCGRP-6-DNLDOK: The image download was successful. 

Explanation    A line card has successfully downloaded its software image from the processor module.

Recommended Action    No action is needed.

%IPCGRP-6-DNLDOVRUN: The image download has overrun the buffer 

Explanation    The line card downloaded a software image from the processor module, but the image overran the card's image buffer. This could indicate that the wrong image was downloaded to the line card, or a potential hardware problem with the card's memory buffers.

Recommended Action    No action is needed as the line card automatically restarts the download. If the problem persists, verify that you are using released software on the Cisco CMTS that supports this particular line card. If necessary, reload the Cisco IOS software on the router to force the line cards to reload the card images that are part of that particular image.

%IPCGRP-6-DNLDTOOLARG: The PRE is attempting to download an image bigger than the 
line cards buffer, available [dec], dnld size [dec].

Explanation    A line card requested a download of a software image that is larger than the card's available buffer size.

Recommended Action    Remove and reinsert the line card. If this does not correct the problem, verify that you are using a released version of the line card and not a prototype with less memory. Verify that you are running released software on the Cisco CMTS that supports this particular line card.

%IPCGRP-3-ENQFAIL: enqueue failed! queue:[chars] size:[dec] 

Explanation    The process_enqueue 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%IPCGRP-3-ERROR: [chars]: [chars]

Explanation    An IPC error is detected.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%IPCGRP-3-EVENTOP: Event [integer] from slot[integer]/[integer]: [chars]

Explanation    An IPC event processing operational error has occurred with the specified line card.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%IPCGRP-3-EVTOP: IPC event [integer] (slot[integer]/[integer]): [chars] 

Explanation    An IPC event processing operational error has occurred with the specified line card.

Recommended Action    Verify that you are using released software on the Cisco CMTS. If using BPI+ encryption, verify that you are using at least Cisco IOS Release 12.2(8)BC1 or later software. 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.

%IPCGRP-6-IBENBDISAB: IronBus interface [chars] Primary [chars] 

Explanation    The IronBus interface has been enabled or disabled.

%IPCGRP-3-IBENBFAIL: IronBus interface [chars] Primary [chars] 

Explanation    The Iron Bus interface enable failed.

Recommended Action    Check the Backplane connectivity.

%IPCGRP-6-IGNOREDNLD: Ignoring new downloaded image. 

Explanation    The line card successfully downloaded a new software image but is not using that image, because the line card is already up and running using another software image. The line card must be manually reloaded to force it to use the new image.

Recommended Action    No action is needed. To force the line card to use the new image, reload the line card.

%IPCGRP-6-INTENBDISAB: Interface [chars] 

Explanation    The interface has been enabled or disabled, typically as part of a card's initialization or OIR routines.

Recommended Action    No action is needed.

%IPCGRP-3-INVALID_PARAMS: Invalid interface([integer]/[integer]/[integer])

Explanation    An invalid interface has been addressed by the corresponding IPC message.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%IPCGRP-3-INVNUM: [chars] ([integer])

Explanation    The IPC application tried to send a message that was larger than what the IPC could handle. The message was not transmitted.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%IPCGRP-6-LCREBOOT: LC Reset due to "[chars]". 

Explanation    This message is generated by the line card that it is being reset.

Recommended Action    No action is needed.

%IPCGRP-6-LINKLOOP_IPC_RECOVER: Exceeds LC max IPC reconnect tolerate time, link 
loop received, will connect to PRE-[chars], current primary: PRE-[chars] 

Explanation    During PRE switchover, the line card tries to connect to the new active PRE through two ways; one through primary signal change and the other is through link loop packet. This message indicates that the line card chooses IPC re-connection through link loop method when the link loop is received earlier than primary signal change. This is not an error.

Recommended Action    No action is required.

%IPCGRP-3-MSGERR: [chars] ([integer])

Explanation    The slave IPC cannot register or exchange messages with the master.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%IPCGRP-3-NBLKCMD: [chars]

Explanation    The non-blocking IPC command queue 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%IPCGRP-6-NBLKCMD_Q_FULL: Nonblocking IPC command queue full ([dec] commands)

Explanation    The non-blocking IPC command queue was full and flushed to avoid buffer starvation.

Recommended Action    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.

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

Explanation    The non-blocking IPC event queue was filled with IPC messages, so the processor module flushed all entries out of the buffer to ensure that current traffic can be processed. This message could occasionally occur during periods of heavy network usage.

Recommended Action    No action is needed. If this situation occurs frequently, verify that all line cards are operational and are not in a locked state that is causing them to repeatedly generate the same IPC messages. Also verify that the processor module is not running at or near 100 percent CPU usage, causing it to be unable to process the IPC messages as they arrive.

%IPCGRP-3-NBLKQ: [chars] 

Explanation    The line card could not create a non-blocking event, message, or reply queue, or it could not create a process for non-blocking events. This typically indicates a memory problem or software error on the line card.

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.

%IPCGRP-6-NBLKRSP_Q_FULL: Nonblocking IPC response queue full ([dec] responses) 

Explanation    The non-blocking IPC response queue was filled with IPC messages, so the processor module flushed all entries out of the buffer to ensure that current traffic can be processed. This message could occasionally occur during periods of heavy network usage.

Recommended Action    No action is needed. If this situation occurs frequently, verify that all line cards are operational and are not in a locked state that is causing them to repeatedly generate the same IPC messages. Also verify that the processor module is not running at or near 100 percent CPU usage, causing it to be unable to process the IPC messages as they arrive.

%IPCGRP-6-NOAPIDAT: Unable to acquire port data for the API port. 

Explanation    The processor module could not determine the port ID to be used for IPC messages with the specified line card. This could indicate that the line card failed to complete the initial IPC handshaking with the processor module. This could also indicate a possible software problem on the line card, such as a buffer memory leak.

Recommended Action    No action is needed if you are running current released Cisco IOS software on the Cisco CMTS, because the processor module automatically reloads the line card. If the problem persists, remove and reinsert the line card. If this does not fix the problem, reload or power-cycle the Cisco CMTS.

%IPCGRP-6-NOAPIPORT: No API port ID for, [chars] 

Explanation    The processor module could not determine the port ID to be used for IPC messages with the specified line card. This could indicate that the line card failed to complete the initial IPC handshaking with the GRP on the processor module. This could also indicate a possible software problem on the line card, such as a buffer memory leak.

Recommended Action    No action is needed if you are running current released Cisco IOS software on the Cisco CMTS, because the processor module automatically reloads the line card. Otherwise, upgrade to the latest Cisco IOS image. If the problem persists, remove and reinsert the line card. If this does not fix the problem, reload or power-cycle the Cisco CMTS.

%IPCGRP-6-NOBPEHWIDB: Can't find the HW IDB for the BPE interface. 

Explanation    The processor module could not find the interface for the Backplane Ethernet, which is required for communication with the line cards. The system is therefore initiating a crash. This could indicate either a software error or a hardware problem.

Recommended Action    Verify that you are using released software on the Cisco CMTS. If so, try removing and reinserting the processor module. If that does not correct the problem, try replacing the processor module. 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.

%IPCGRP-3-NOHWIDB: Cannot find hwidb for interface([integer]/[integer])

Explanation    The interface identifier does not exist for the interface addressed by the corresponding IPC message.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%IPCGRP-6-NOINBND: Unable to create "[chars]" port, error [dec].  

Explanation    The line card could not create the inbound API port for IPC messages with the processor module.

Recommended Action    Verify that you are using released software on the Cisco CMTS. If so, try removing and reinserting the line card. If the problem continues, 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.

%IPCGRP-6-NOIPCPAK: Unable to get an available, empty IPC packet buffer. 

Explanation    The line card could not obtain a free packet buffer for IPC messages from its memory pool. This typically indicates a memory problem or software error on the line card.

Recommended Action    Verify that you are using released software on the Cisco CMTS. If so, try removing and reinserting the line card. If the problem continues, 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.

%IPCGRP-6-NOKEEP: Too long since a keepalive was received from the PRE. 

Explanation    The timer expired while waiting for a keepalive from the PRE.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%IPCGRP-6-NOMSGSND: Unable to send an IPC message, error [dec]. 

Explanation    The line card is reporting that the specified error occurred during an attempt to send an IPC message to the processor module.

Recommended Action    No action is needed if this error occurs only occasionally. Otherwise, verify that you are using released software on the Cisco CMTS. If so, try removing and reinserting the line card. If the problem continues, 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.

%IPCGRP-3-NOMSTR: Unable to open the IPC master UDP port. 

Explanation    The line card is unable to open the UDP port that it uses to communicate with the IPC master.

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.

%IPCGRP-6-NOOPENAPI: Unable to open the line card API IPC port, error [dec]. 

Explanation    The line card cannot determine the port number to be used for IPC messages.

Recommended Action    No action is needed, because the line card restarts its IPC subprocess. If the problem persists, verify that you are using released software on the Cisco CMTS. If so, try removing and reinserting the line card. If the problem continues, 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.

%IPCGRP-6-NOPROC: Unable to create IPC message dispatch process.

Explanation    The line card could not start the IPC message receive process. This typically indicates a memory problem or software error on the line card.

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, try removing and reinserting the line card. If the problem continues, 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.

%IPCGRP-6-NOQLOOP: Unable to queue a received link-loop backplane ethernet 
keepalive. 

Explanation    The line card cannot queue a received keepalive packet to the packet queue. This typically indicates a memory problem or software error on the line card.

Recommended Action    Verify that you are using released software on the Cisco CMTS. If so, try removing and reinserting the line card. If the problem continues, 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.

%IPCGRP-6-NOSLOT: Unknown slot number.

Explanation    The line card is unable to determine its slot number in the chassis. This message can appear during an OIR operation or during system initialization. This could indicate a transient error condition, or a potential hardware problem with the line card or chassis.

Recommended Action    No action is needed as the line card reinitializes itself. If the problem persists, try removing and reinserting the line card. Also try moving the line card to another slot. If that corrects the problem, it could indicate a problem with that particular slot in the Cisco uBR10012 chassis.

%IPCGRP-6-NOTBHLPR: The PRE wants to download a card image.

Explanation    The processor module is attempting to download an image to a line card, but the line card has refused the download because it is not running in the boothelper state.

Recommended Action    Verify that you are running released software on the Cisco CMTS. Verify that the line card is a production version of the card. If so, reload the processor module with the hw-module reset pre command, or power cycle the router.

If the problem is with a Broadband Processing Engine (BPE) cable interface line card (Cisco uBR-MC16U/X, Cisco uBR-MC28U/X, Cisco uBR-MC5X20S/U), verify that you are running Cisco IOS Release 12.2(15)BC2 or later release on the Cisco CMTS.

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.

%IPCGRP-6-RESTART: Restart OIR fsm due to [chars]. 

Explanation    The OIR finite state machine (FSM) is being restarted, because of the specified reason.

Recommended Action    If this message occurs after an N+1 HCCP switchover, no action is needed as this is expected behavior. Otherwise, look at the console log for other system messages that could indicate a potential problem. Verify that you are running released software on the Cisco CMTS. If you have configured N+1 HCCP redundancy on the cable interfaces, and this message did not occur after a switchover, verify that you are running at least Cisco IOS Release 12.2(15)BC2 or later release.

%IPCGRP-3-SEATERR: [chars] ([integer])

Explanation    The ID associated with an IPC card is either missing, duplicated, or cannot be created.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%IPCGRP-6-SKIP_IPC_RECOVER: Linkloop mechanism has chosen PRE-[chars] previously, 
skip duplicate IPC recovery 

Explanation    During PRE switchover, the line card tries to connect to the new active PRE through two ways; one through primary signal change and the other is through link loop packet. This message indicates that the line card has reconnected using the link loop method and hence skip primary signal change to avoid duplicate IPC setup with active PRE. This is not an error.

Recommended Action    No action is required.

%IPCGRP-6-SLOTID: Slot ID is [dec]/[dec]

Explanation    This is slot ID of the line card.

Recommended Action    No action is needed.

%IPCGRP-3-SLOTPAR: Slot ID parity error. 

Explanation    The slot ID or subslot ID for the line card that the line card received from the backplane Ethernet is invalid (either 0 or -1). This could indicate either a software error, or a potential hardware problem with the backplane slot or the line card.

Recommended Action    Verify that you are running released software on the Cisco CMTS. Try removing and reinserting the line card. Try replacing the line card. Try moving the line card to another slot. If that corrects the problem, there could be a hardware problem with the original slot in the chassis.

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.

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

Explanation    An error occurred with an IPC kernel system call on the specific card. If the specified error is a time-out error, this could indicate a possible hardware problem with that card, or it could also indicate a possible software error, such as memory corruption. This could also indicate a failure on the TCC+ card on a Cisco uBR10012 router.

Recommended Action    Verify that you are using released software on the Cisco CMTS. If this problem occurred during an OIR or the line card, or during a shutdown or no shutdown of the card, verify that you are running at least Cisco IOS Release 12.2(11)BC2 or later. If possible, upgrade to the latest version of Cisco IOS software.

Also look in the console log for any other error messages. In particular, if any messages indicate a failure on the TCC+ card, the problem could be that the Cisco uBR10012 router does not have a working TCC+ card installed. Verify that at least one TCC+ card is installed in the chassis. If so, try replacing it.

If the error is a time-out error, verify that you are using a production version of the specified line card. If so, try replacing the specified card.

If the problem continues, 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.

%IPCGRP-6-UCODEVER: Reported microcode version, [dec]. 

Explanation    This message reports the version of microcode that is running on the line card.

Recommended Action    No action is needed.

%IPCGRP-6-UNKLCCMD: Received unknown command from CRE ([dec]) 

Explanation    The line card received an unknown line card command. This typically indicates that the line card is not running the same Cisco IOS software release as the processor module, and that the PRE1 module is sending IPC messages that are not recognized by the line card.

Recommended Action    Verify that you are running released software on the Cisco CMTS. If so, reload the line card using the microcode reload command or by removing and reinserting the line card.

%IPCGRP-6-UNKWOBJ: Unknown IPC object received, [dec] 

Explanation    An recognized or unsupported IPC object has been received. This typically indicates that the line card and processor module are not running the same releases of Cisco IOS software, and the card with the latest version of software is sending IPC messages that are not recognized by the other card.

Recommended Action    Verify that you are running released software on the Cisco CMTS. If so, reload the line card using the microcode reload command or by removing and reinserting the line card.

%IPCGRP-6-UNKWOPCODE: Unknown IPC message opcode, [dec] 

Explanation    An IPC message was received with an unknown opcode. This typically indicates that the line card and processor module are not running the same releases of Cisco IOS software, and the card with the latest version of software is sending IPC messages that are not recognized by the other card.

Recommended Action    Verify that you are running released software on the Cisco CMTS. If so, reload the line card using the microcode reload command or by removing and reinserting the line card.

%IPCGRP-6-UNKWSUBTYP: Unknown SET message subtype, [dec] 

Explanation    A SET type of IPC message was received with an unknown subtype. This typically indicates that the line card and processor module are not running the same releases of Cisco IOS software, and the card with the latest version of software is sending IPC messages that are not recognized by the other card.

Recommended Action    Verify that you are running released software on the Cisco CMTS. If so, reload the line card using the microcode reload command or by removing and reinserting the line card.

IPCMON

The following are Interprocess Communication (IPC) monitoring error messages.

 
    
   
: IPC BPE interface is reset by BPE monitor 

Explanation    BPE monitor detects no packets RX or TX onIPC BPE interface. Reset the interface to recover.

Recommended Action    No action is needed.

IPCOIR

This section describes the UBR7200 IPC State Machine error messages.

%IPCOIR-3-BADIPHOST: Bad IP address or host name [chars]

Explanation    The IP address or the host name is incorrect or unknown.

Recommended Action    Check the IP address or hostname.

%IPCOIR-3-BADLCAPI: Incorrect API message version 0x[hex]

Explanation    The line card and IOS images are out of phase.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%IPCOIR-3-BADMESSVER: Incorrect message version obj 0x[hex] op 0x[hex] version 
0x[hex]

Explanation    The line card and IOS images are out of phase.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%IPCOIR-3-BOGUSCARD: Bogus cardtype [dec]

Explanation    The card type is unknown to the software.

Recommended Action    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.

%IPCOIR-3-CARD_BADIDPROM: Card in slot [dec]/[dec] has an invalid card type in 
IDPROM

Explanation    This message indicates the IDPROM line card is not programmed or 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%IPCOIR-3-CARDCRASH: Card crashed in slot [dec]/[dec].

Explanation    The IPC message is reporting that a wrong version is received from an operational card.

Recommended Action    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.

%IPCOIR-5-CARD_DETECTED: Card type [chars] (0x[hex]) in slot [dec]/[dec]

Explanation    A card has been detected in the indicated slot.

Recommended Action    No action is needed.

%IPCOIR-3-CARD_GET_VERSION_RESPONSE: Unsolicited response from slot 
[integer]/[integer], oir_state = [chars]

Explanation    An unexpected message is received from a line card.

Recommended Action    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.

%IPCOIR-5-CARD_LOADING: Loading card in slot [integer]/[integer]

Explanation    A line card is being downloaded with MD5 checksum data.

Recommended Action    No action is needed.

%IPCOIR-3-CARD_UNSUPPORTED: Unsupported card type (0x[hex]) in slot [dec]/[dec].

Explanation    The line card is not supported by this version of IOS.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%IPCOIR-2-CARD_UP_DOWN: Card in slot [dec]/[dec] is [chars]. Notifying [chars] 
driver.

Explanation    This message notifies the line card status (up or down).

Recommended Action    No action is needed.

%IPCOIR-2-CREATEFAIL: Could not create [chars]

Explanation    The specified resource could not be created.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%IPCOIR-3-CRE_INIT_FAIL: Unable to initialize PRE ports.

Explanation    The PRE plug-in init sequence 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%IPCOIR-3-FLASHFAIL: Could not load [chars]

Explanation    The image is inaccessible.

Recommended Action    Check the filename.

%IPCOIR-3-HHCARDTYPECONFLICT: card 1gigethernet-hh-1 in slot [1/0]

Explanation    The HH card type conflicts with the TCC Util card or the BP of the UBR10000 chassis.

Recommended Action    Remove the conflicting card type from the slot or subslot and shutdown the chassis.

%IPCOIR-3-IMAGEVERSION: Image version stamp missing

Explanation    The loaded image does not contain a recognizable version stamp.

Recommended Action    Replace the image with known good bits, and try again.

%IPCOIR-4-IPC_GET_MSG_BUF: Get IPC msg buf failed [dec] time(s): slot 
[integer]/[integer] - retry in [dec] sec

Explanation    The IOS IPC buffer pool is temporarily empty.

Recommended Action    Install more processor SDRAM in the PRE.

%IPCOIR-3-IPC_GET_MSG_BUF_FAIL: Unable to get an IPC msg buffer in [dec] tries: 
slot [integer]/[integer]

Explanation    An empty IOS IPC buffer pool has occurred for a sustained period of time.

Recommended Action    Install more processor SDRAM in the PRE.

%IPCOIR-3-KEEPALIVE: A keepalive timeout occurred on slot [dec]/[dec]. Last 
process: [chars] (4ms time = [integer]ms), Intr. Busy Count: [integer], Sched Flag 
Count: [integer]

Explanation    The line card has stopped responding to keepalive polls while in the RUN state.

Recommended Action    Monitor the line card for a persistent problem. If the problem 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%IPCOIR-3-LC4MS: The watchdog timer on slot [integer]/0 has stopped.

Explanation    The line card has stopped servicing the watchdog timer.

Recommended Action    This condition may be temporary or may be caused by a crash. Check the line card's bootflash for crashinfo files and monitor the line card for a watchdog time-out.

%IPCOIR-3-LCCRASH: The card in slot [dec]/[dec] has crashed. Cause Register: 
0x[hex]0x[hex], Signal: 0u[decimal]

Explanation    The line card in the specified slot has crashed.

Recommended Action    Wait for the line card to come online, then connect to the remote console and extract the crashinfo file from the bootflash. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). If you still require assistance, open a case with the Technical Assistance Center online (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative.

%IPCOIR-6-LCWAITINFO: CLC [dec]/[dec]> [chars]

Explanation    The network processing engine (NPE) OIR handler received a console error message from a distributed line card while in the crashwait state. The handler enters this state when it detects a Keepalive time-out on a distributed line card. During the crash wait period, the line card is expected to collect and store the crash information. At the end of the wait period, the NPE will reload the line card. During this time it is possible that the line card would try to send error messages to its console. Normally, these messages would be sent to the NPE using the logger. However, during the wait period, the IPC link between the NPE and the line card will be down and hence the OIR debug code provides a rudimentary method of collecting and displaying these error messages.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%IPCOIR-3-LOADER_DNLD_NOBUF: Buffer allocation failed

Explanation    The buffer downloader could not allocate a message buffer.

Recommended Action    Reboot the chassis.

%IPCOIR-3-LOADER_DNLD_REJECT: Buffer download to slot [integer]/[integer] 
rejected

Explanation    The line card buffer download server rejected the download.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%IPCOIR-3-LOADER_IPC_FAIL: IPC failed ([chars]) [chars] slot [integer]/[integer]

Explanation    An unexpected error has been reported by the IOS IPC protocol.

Recommended Action    Ensure that the indicated card is plugged in.

%IPCOIR-3-LOADER_SERVER_FAIL: Remote server refused to load slot 
[integer]/[integer]

Explanation    The specified line card cannot be loaded. Loading of the line card will be attempted again.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%IPCOIR-2-NULL_PTR: [chars]: pointer is null

Explanation    An unexpected NULL pointer has occurred.

Recommended Action    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.

%IPCOIR-3-PLUGIN_INIT_FAIL: Unable to create driver plug-in in slot [dec]/[dec]

Explanation    A valid line card driver plug-in creation on the PRE has failed due to a memory allocation error or the line card driver initialization.

Recommended Action    Switch over to the standby PRE module, if any memory allocation error is causing the system to be unstable. If the standby PRE module is not available, reload the chassis. If this does not solve the problem, 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.

%IPCOIR-2-PLUGIN_PREANALYZE_FAIL: Unable to pre-analyze driver plug-in in slot 
[dec]/[dec].

Explanation    The interface initialization of the line card driver has failed. This error might occur if the interface objects are not created or the Parallel eXpress Forwarding (PXF) table for an interface is not correctly set up. This error generally occurs with the shared port adaptor (SPA) driver and Spumoni and Saratoga jacket cards.

Recommended Action    Check for incompatible card types. In case of a Spumoni driver, make sure that the driver is configured with the correct card type, slot, and subslot.

%IPCOIR-4-REPEATMSG: IPC handle already exists for [dec]/[dec]

Explanation    The IPC communication between the NPE and a line card is already set up.

Recommended Action    Reload the specified line card. If this does not solve the problem, 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%IPCOIR-3-STATE_MACHINE_BUG: card_oir_loading() called, should never happen, 
recovering.

Explanation    An internal software error has occurred.

Recommended Action    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.

%IPCOIR-3-STATE_MACHINE_BUG2: card_oir_insert_card: already have 0x[hex], 
removing.

Explanation    An internal software error has occurred.

Recommended Action    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.

%IPCOIR-3-TFTPFAIL: TFTP of [chars] from [chars] failed

Explanation    The image is inaccessible.

Recommended Action    Check the file permissions, and the network connectivity.

%IPCOIR-3-TIMEOUT: Time-out waiting for a response from slot [integer]/[integer].

Explanation    The NPE has lost connection with the line card. The line card might have crashed.

Recommended Action    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.

%IPCOIR-3-WRONGCARDTYPE: Wrong card type in slot [integer]/[integer].

Explanation    The IPC message is reporting that a wrong card type is received from an operational card.

Recommended Action    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.

%IPCOIR-5-NEW_IMAGE_MATCH_TYPE: Identical image - cards of type ([chars]) not 
re-loaded 

Explanation    The specified line card type is not reloaded because of identical images.

Recommended Action    No action is required.

JIB3_US_FAUNA

The following are JIB3 upstream Fauna messages:

%JIB3_US_FAUNA-3-JIB3_US_FATAL_INT: [chars] event; register value [hex] 

Explanation    Fatal JIB3-US interrupt is encountered.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%JIB3_US_FAUNA-3-JIB3_US_FAUNA_PARTIAL_RESET: [chars] PR HW Recovery; Status: 
[hex] [hex] [hex] [hex] 

Explanation    JIB3-US FAUNA interrupt.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%JIB3_US_FAUNA-3-JIB3_US_SEU_INT: [chars] event; Data [hex] 

Explanation    JIB3-US Single Bit SEU Event is encountered.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%JIB3_US_FAUNA-3-JIB3_US_FAUNA_PARTIAL_RESET_START: [chars] event; Status: [hex] 

Explanation    JIB3-US FA interrupt.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

JIB3_US_FL

The following are JIB3 upstream Flora messages:

%JIB3_US_FL-3-JIB3_US_DOUBLE_BIT_ECC_ADDR_LOG: [chars] ; The multi-bit ecc error 
address is [hex] 

Explanation    Multi bit ECC Error.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%JIB3_US_FL-3-JIB3_US_DOUBLE_BIT_ECC_DATA_LOG: Data: [chars] ; Data value [hex] 

Explanation    Multi bit ECC Error.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%JIB3_US_FL-3-JIB3_US_FATAL_INT: [chars] event; register value [hex] 

Explanation    Fatal JIB3-US interrupt is encountered.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%JIB3_US_FL-3-JIB3_US_PHY_PARTIAL_RESET: [chars] PHY PR HW Recovery; Status: 
[hex] 

Explanation    JIB3-US Flora interrupt.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%JIB3_US_FL-3-JIB3_US_SEU_INT: [chars] event; Data [hex] 

Explanation    JIB3-US Single Bit SEU Event

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%JIB3_US_FL-3-JIB3_US_PHY_PARTIAL_RESET_START: [chars] event; Status: [hex] 

Explanation    JIB3-US FL interrupt.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

JIBREAD

The following are JIBREAD messages:

%JIBREAD-3-BUFFERERR: Buffer([dec]) cannot accommodate data([dec]) 

Explanation    Data requested from RP is larger than allocated 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%JIBREAD-3-READFAIL: Error reading [chars] record 

Explanation    Failed to read the requested data from JIB.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

L2TP

The following are L2TP system messages:

%L2TP-3-CRITICAL : %s 

Explanation    An critical event has been processed by the L2TP subsystem.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%L2TP-3-ILLEGAL : [chars]: [chars] 

Explanation    An illegal event has been processed by the L2TP subsystem.

Recommended Action    No action is required.

%L2TP-5-IGNOREICMPMTU : Ignoring received ICMP Type 3 Code 4, due to pmtu min or 
max setting 

Explanation    An ICMP Type 3 Code 4 (fragmentation needed and DF set) packet has been received. This packet has specified a Next-Hop MTU that is smaller or greater than the current minimum or maximum path MTU discovery mtu value. The ICMP packet has been ignored and the MTU has not been changed.

Recommended Action    If you want the ICMP packet to be accepted and used to decrease or increase the MTU then use the vpdn pmtu min command to decrease the minimum MTU allowed and enter the vpdn pmtu max command to increase the maximum MTU that is allowed. The minimum value specified is the minimum MTU that is allowed, and the maximum value specified is the maximum MTU that is allowed.

LC

The following are line card error messages:

%LC-4-ALLOCFAIL: Line Card in slot [dec], resource allocation failure while 
[chars] 

Explanation    The router has failed to allocate sufficient memory for a software module on the POS Line Card located in the specified slot. The error message indicates the Line Card slot.

Recommended Action    Perform OIR of the Line Card located in the specified slot. Remove the Line Card, wait 5 seconds, and reinsert the LC into the slot. Enter the show memory summary command to attempt to determine the cause of the error. Reduce system activity to reduce memory demands. If conditions warrant, upgrade to a larger memory configuration. If you require further assistance, contact your Cisco technical support representative and provide the representative with the gathered information.

LCD_DISPLAY

The following are LCD display error messages:

%LCD_DISPLAY-3-CHAR_ERROR: Invalid character 

Explanation    This character is not supported by card LCD

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%LCD_DISPLAY-4-INPUT_ERROR: Invalid input DS [dec] US [dec] channels 

Explanation    Wrong number of downstream or upstream channels.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%LCD_DISPLAY-4-STATUS_ERROR: Invalid status 

Explanation    Invalid status bit.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

LICENSE

%LICENSE-1-EXPIRING: License for feature US_License 1.0 will expire in 5 minutes

Explanation    The current in-use license is a temporary license that is going to expire

Recommended Action    Install an equivalent permanent license to make sure there are no service disruptions. Use http://www.cisco.com/go/license portal to obtain a permanent license from a PAK. Contact TAC if further assistance is required.

LTC

The following are the LTC error messages:

%LTC2978-4-CML_FAULT: Communication Fault is reported by LTC2978. [chars] 

Explanation    LTC2978 reported communication fault.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%LTC2978-4-LOG_CLEAR_MAX_RETRIES: Tried [dec] times to read transfer status after 
clearing log for 2978-[dec] and the read was unsuccessful 

Explanation    Log clear operation did not work for LTC2978.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%LTC2978-4-LOG_RESTORE_MAX_RETRIES: Tried [dec] times to read log data after log 
restore for 2978-[dec] and the read was unsuccessful 

Explanation    Log restore operation did not work for LTC2978.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%LTC2978-4-LTC2978_ALERT: LTC2978(power fault monitor) open drain alert for device 
#[dec], raven low misc interrupt status:[hex] 

Explanation    Interrupt from LTC2978.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%LTC2978-5-POWER_FAILURE: Power failure happened in previous power cycle. Check 
OBFL logs for details. 

Explanation    LTC2978 recorded power failure in previous power cycle.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%LTC2978-5-TEMPERATURE_FAULT: Temperature Fault is reported by LTC2978. [chars] 

Explanation    LTC2978 reported Temperature Fault.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support along with the temperature values reported by MAX1668 using test cable envm temp dump [1|2|3] command on LC console.

%LTC2978-4-VIN_FAULT: Input Voltage Fault is reported by LTC2978. [chars] 

Explanation    LTC2978 reported input voltage fault.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%LTC2978-4-VOUT_FAULT: Output Voltage Fault is reported by LTC2978. [chars] 

Explanation    LTC2978 reported output voltage fault.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

MCT1E1

The following are T1/E1 messages.

%MCT1E1-3-AUTODNR: [chars] failed for slot [dec] bay [dec] err [dec] 

Explanation    AUTODNR/USNDNR process failed causing a software error. The SPA and line card are out of sync.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%MCT1E1-3-TIMEOUT: 
[chars]: [chars] failed: [dec], state: [dec], ml_id: [dec] progress: [dec]

Explanation    Timeout error observed.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

MCU, MCUCLC, MCUFSM

The following system error messages concern the operation of the Cisco uBR-MC16U/X, Cisco uBR-MC28U/X, and Cisco uBR-MC88V cable interface line cards.

MCU—These error message display information about the Cisco uBR-MC16U/X or Cisco uBR-MC28U/X or Cisco uBR-MC88V cable interface card's hardware or initialization problems.

MCUCLC—These error messages display information about errors that have occurred during the operation of the Cisco IOS software on the Cisco uBR-MC16U/X, Cisco uBR-MC28U/X, and Cisco uBR-MC88V cable interface card.

MCUFSM—These error messages display information about unexpected events that have occurred with the finite state machine (FSM) that operates on the Cisco uBR-MC16U/X, Cisco uBR-MC28U/X, and Cisco uBR-MC88V cable interface card to control online insertion and removal (OIR) operations.

MCU

%MCU-3-LEGACY_IN_MC88V_CHASSIS: Non-MC88V card enabled in MC88V chassis slot 
[dec]. 

Explanation    When an MC88V card is present in a chassis, non-MC88V cards are not allowed in the chassis.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%MCU-3-MC88V_IN_LEGACY_CHASSIS: MC88V card enabled in Non-MC88V chassis slot 
[dec]. 

Explanation    When Non-MC88V card exists in a chassis, Cisco uBR-MC88V card should not be allowed in that chassis.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%MCU-6-LEGACY_NOT_SUPPORTED: Non-MC88V card is not supported in a MC88V chassis. 

Explanation    A Non-Cisco uBR-MC88V card is not allowed in the Cisco uBR-MC88V chassis.

Recommended Action    No action is needed.

%MCU-6-MC88V_NOT_SUPPORTED: MC88V card is not supported in a Non-MC88V chassis. 

Explanation    A Non-Cisco uBR-MC88V card is not allowed in the Cisco uBR-MC88V chassis.

Recommended Action    No action is needed.

%IPCMON-6-BPERST %MCU_MEM_DDR-1-AC_ERR: DDR automatic calibration error detected at [hex]

Explanation    This error is set if the memory controller detects an error during its training sequence. This kind of an error is not one that the double data rate (DDR) control should not report under its normal operating conditions and when it does, it most probably indicates a malfunctioning DDR module, that needs replacement.

Recommended Action    Replace the DIMM card. If the issue persists, replace the cable interface line card.

%MCU_MEM_DDR-0-MS_ERR: DDR Memory Select error detected at [hex] 

Explanation    This error is detected if the address from the memory request does not fall into any of the enabled, programmed chip select address ranges. This could be a DDR configuration error or some application is trying to access an address for which the target is DDR, but it is not within the configured address range.

Recommended Action    Replace the DIMM card. If the issue persists, replace the cable interface line card.

%MCU_MEM_ECC-1-BADADDR_MBE: Invalid MBE dram address: [hex] latched by ECC Ctrl 

Explanation    The address latched by the Error Correction Code (ECC) control when detecting an multi-bit memory error (MBE) is not a valid dynamic random access memory (DRAM) address. This kind of an error is not one that the ECC control should not report under its normal operating conditions and when it does, it most probably indicates a malfunctioning ECC control that needs replacement.

Recommended Action    Replace the DIMM card. If the issue persists, replace the cable interface line card.

%MCU_MEM_ECC-2-BADADDR_SBE: Invalid ECC SBE dram address: [hex] latched by ECC 
Ctrl 

Explanation    The address latched by the ECC control when detecting a SBE is not a valid DRAM address. This kind of an error is not one that the ECC control should not report under its normal operating conditions and when it does, it most probably indicates a malfunctioning ECC control that needs replacement.

Recommended Action    No action is required. This is a single-bit memory error, and the memory controller can correct it.

%MCU_MEM_ECC-2-MBE: Multiple bit error detected at [hex] 

Explanation    A multi-bit uncorrectable error was detected on a CPU read from DRAM.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%MCU_MEM_ECC-3-SBE: Single bit error detected and corrected at [hex] 

Explanation    A single-bit correctable error was detected on a read from DRAM. The show ecc command can be used to dump single-bit errors logged so far.

Recommended Action    No action is required. This is a single-bit memory error, and the memory controller can correct it.

%MCU_MEM_ECC-3-SYNDROME_MBE: 8-bit Syndrome for the detected Multi-bit error: [hex]

Explanation    The 8-bit syndrome was detected for the multi-bit error. This value does not indicate the exact positions of the bits in error but can be used to approximate their positions.

Recommended Action    Replace the DIMM or cable interface line card.

%MCU_PHOENIX_FPGA-3-BCM_IF_ERR: BCM_IF Error: [hex] 

Explanation    A Phoenix BCM_IF fatal error is observed.

Recommended Action    Replace the cable interface line card.

%MCU_PHOENIX_FPGA-3-CHANNEL_ERROR: Error channel: [dec] with mask [hex]. 

Explanation    This error occurs when the channel added to the channel mask is not the same as the channel selected to operate.

Recommended Action    Replace the cable interface line card.

%MCU_PHOENIX_FPGA-3-DCM_LOCK: DCM Lock Error: [chars]: [dec] 

Explanation    A digital clock manager (DCM) lock error is observed.

Recommended Action    Replace the cable interface line card.

%MCU_PHOENIX_FPGA-3-DCM_LOSTLOCK_FESR: [chars] lost lock fatal error 

Explanation    A Phoenix DCM lost lock fatal error is observed.

Recommended Action    Replace the cable interface line card.

%MCU_PHOENIX_FPGA-3-FA_ERP_ERR: Fauna ERP_MST error: [hex] 

Explanation    A Phoenix FA_ERP_MST error is observed.

Recommended Action    Replace the cable interface line card.

%MCU_PHOENIX_FPGA-3-FFT_IF_ERR: FFT_IF Error: [hex] 

Explanation    A Phoenix FFT_IF fatal error is observed.

Recommended Action    Replace the cable interface line card.

%MCU_PHOENIX_FPGA-3-FL_ERP_ERR: Flora ERP_MST error: [hex] 

Explanation    A Phoenix FL_ERP_MST error is observed.

Recommended Action    Replace the cable interface line card.

%MCU_PHOENIX_FPGA-3-KW_ERP_ERR: Kawad ERP_MST error: [hex] 

Explanation    A Phoenix KW_ERP_MST error is observed.

Recommended Action    Replace the cable interface line card.

%MCU_PHOENIX_FPGA-3-RANGE_ERROR: Unknown [chars]: [dec] exceed the normal 
range([dec],[dec]). 

Explanation    This error occurs when the module exceeds the normal range when trying to set/select a module.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%MCU_PHOENIX_FPGA-3-SPI_TIMEOUT: Timeout waiting for [chars] to finish. 

Explanation    A serial peripheral interface (SPI) timeout is observed.

Recommended Action    Replace the cable interface line card.

%MCU_PLATFORM-0-IO_TIMEOUT: [chars] = [hex] 

Explanation    An input or output (IO) timeout occurs while accessing a device.

Recommended Action    Replace the cable interface line card.

%MCU_PLATFORM-3-IO_TIMEOUT_MSG: [chars] = [hex] 

Explanation    The status register shows an IO timeout message while accessing a device.

Recommended Action    Replace the cable interface line card.

%MCU_PLATFORM-3-UNEXPECTED_INTR: Un-expected spurious interrupt [chars].

Explanation    An unexpected spurious interrupt is received by interrupt handler.

Recommended Action    Replace the cable interface line card.

%MCU_PLL_UNLOCK-3-MCU_PLL_NOT_LOCKED: [chars] is not locked.

Explanation    A PLL Not Locked error is observed.

Recommended Action    Replace the cable interface line card.

%MCU_QUACK-3-MCU_QUACK_IDPROM_ERROR: Quack [chars] [chars] fail.

Explanation    The quack operation has failed as indicated by the failure string.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%MCU_RAKE_CPLD-3-RAKE_FPGA_DOWNLOAD_ERROR: [chars] 

Explanation    An error is observed while downloading image to the FPGA.

Recommended Action    Replace the cable interface line card.

%MCU_RAKE_CPLD-3-RAKE_FPGA_ERP_DCM_LOST_ERROR: Detect [chars] FPGA DCM lost 
error. 

Explanation    A DCM lost error is observed on the Kawad, Fauna or Flora FPGA.

Recommended Action    Replace the cable interface line card.

%MCU_RAKE_CPLD-3-RAKE_FPGA_ERP_DCM_NOT_LOCK_ERROR: Detect [chars] FPGA DCM not 
lock error. 

Explanation    A DCM not lock error is observed on the Kawad, Fauna or Flora FPGA.

Recommended Action    Replace the cable interface line card.

%MCU_RAKE_CPLD-3-RAKE_FPGA_ERP_PLL_NOT_LOCK_ERROR: Detect Kawad ERP PLL not lock 
error. 

Explanation    An ERR PLL not lock error is observed on the Kawad or FPGA.

Recommended Action    Replace the cable interface line card.

%MCU_RAKE_CPLD-3-RAKE_FPGA_LB_DCM_NOT_LOCK_ERROR: Detect Kawad LB DCM not lock 
error. 

Explanation    An LB DCM not lock error is observed on the Kawad or FPGA.

Recommended Action    Replace the cable interface line card.

%MCU_RAKE_CPLD-3-RAKE_FPGA_SEU_ERROR: Detect [chars] FPGA SEU error. 

Explanation    A SEU error is observed on the Kawad, Fauna or Flora FPGA.

Recommended Action    Replace the cable interface line card.

%MCU_RAKE_CPLD-3-RAKE_RANGE_ERROR: Unknown [chars]: [dec] exceed the normal 
range([dec],[dec]). 

Explanation    This error is observed when the module exceeds the normal range while trying to set/select a module.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%MCU_UPX-3-UPX_BOOTUP_ERR: UPX bootup failed 

Explanation    An up-converter (UPX) bootup error is observed.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%MCU_UPX-6-UPX_CURRENT_INFO: Current Sensor [dec] Measurement = [dec] mA

Explanation    Logs the current information of the UPX.

Recommended Action    No action is required.

%MCU_UPX-6-UPX_CURRENT_LIMIT: Current Sensor [dec] Alarm Upper Limit = [dec] mA, 
Lower Limit = [dec] mA

Explanation    Logs the current limit of the UPX.

Recommended Action    No action is required.

%MCU_UPX-6-UPX_ENV_STATUS: UPX Environment Monitor Status:

Explanation    Logs the environment status of the UPX.

Recommended Action    No action is required.

%MCU_UPX-3-UPX_ERR: [chars] 

Explanation    An UPX generic error is detected.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%MCU_UPX-3-UPX_FAILOVER_DETAIL: UPX failover event: [chars] 

Explanation    A detailed information of the UPX failover event.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%MCU_UPX-3-UPX_FAILOVER_ERR: UPX failover event detected

Explanation    An UPX failover event is detected.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%MCU_UPX-6-UPX_INFO: [chars]

Explanation    UPX generic information.

Recommended Action    No action is required.

%MCU_UPX-3-UPX_SPI_ERR: UPX SPI cmd error, cmd: [chars] 

Explanation    An UPX SPI command error is observed.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%MCU_UPX-6-UPX_THERMAL_INFO: Thermal Sensor [dec] Measurement = [dec] Celsius

Explanation    Logs the thermal information of the UPX.

Recommended Action    No action is required.

%MCU_UPX-6-UPX_THERMAL_LIMIT: Thermal Sensor [dec] Alarm Upper Limit = [dec] 
Celsius, Lower Limit = [dec] Celsius

Explanation    Log the upper thermal limit of the UPX.

Recommended Action    No action is required.

%MCU_UPX-6-UPX_VOLTAGE_INFO: Voltage Sensor [dec] Measurement = [dec] mV

Explanation    Logs the voltage information of the UPX.

Recommended Action    No action is required.

%MCU_UPX-6-UPX_VOLTAGE_LIMIT: Voltage Sensor [dec] Alarm Upper Limit = [dec] mV, 
Lower Limit = [dec] mV

Explanation    Logs the voltage limit of the UPX.

Recommended Action    No action is required.

%MCU_US-6-US_NO_CALIB_DATA: Fail to retrieve calibration data, default data is 
applied. 

Explanation    The calibration data is not present or corrupted.

Recommended Action    No action is required.

%MCU_US-3-US_PHY_ERR: Upstream channel [dec] is experiencing unexpected state, 
need recovery. 

Explanation    There is error assert in upstream PHY chip.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%MCU_US-6-US_PHY_SPI_DONE_INTR_NOT_SUPPORT: Unexpected Upstream Phy interrupt, 
status:[hex] 

Explanation    A SPI done interrupt occurs, however it is disabled on Cisco uBR-MC88V platform.

Recommended Action    No action is required.

%MCU_US-3-US_PHY_SPI_FAIL: SPI transaction failed when programing PHY chip [dec]. 

Explanation    The PHY chip cannot be configured as it would impact the serviceability of the chip.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%MCU-1-CONFIGNOTETHER: Cannot configure any of the IPC ethernet interfaces 

Explanation    The internal Ethernet interfaces on the cable interface line card, which are used for interprocess communications (IPC) with the main processor, cannot be configured.

Recommended Action    Remove and reinsert the specified cable interface line card. Verify that you are running released software on the CMTS. 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.

%MCU-1-DISCOVER: Cannot initialize bay [dec], shutting down bay 

Explanation    The Cisco CMTS router could not initialize the indicated backplane bay and is shutting down the bay to prevent possible hardware problems.

Recommended Action    Remove and reinsert the Cisco uBR-MC16U/X or Cisco uBR-MC28U/X card. If the problem persists, reload the Cisco CMTS router.

%MCU-3-EREVENT: slot ([dec]):([chars]) 

Explanation    The cable interface line card in the indicated slot experienced the indicated error event or failure.

Recommended Action    Remove and reinsert the specified cable interface line card. Verify that you are running released software on the CMTS. 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.

%MCU-3-ERR_BUFFER_LEN: Buffer size ([int]) is too big to DMA to line card 

Explanation    When data is moved by direct memory access (DMA) from the NPE (Network Process Engine) to a line card, the data buffer length must not exceed the maximum buffer size of the line card. This message indicates a software error.

Recommended Action    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, and upgrade to the new IOS with the fix for this error.

%MCU-3-GENERAL: [chars] 

Explanation    The cable interface line card in the indicated slot experienced a general failure, as defined by the failure string.

Recommended Action    Remove and reinsert the specified cable interface line card. Verify that you are running released software on the CMTS. 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.

%MCU-3-MC88V_IN_LEGACY_CHASSIS: MC88V card enabled in Non-MC88V chassis slot 
[dec]. 

Explanation    The Cisco uBR-MC88V line card is not allowed in the router if a non-MC88V line card exists in the chassis.

Recommended Action    Remove or disable the non-MC88V line card and reboot the CMTS.

%MCU-3-LEGACY_IN_MC88V_CHASSIS: Non-MC88V card enabled in MC88V chassis slot 
[dec]. 

Explanation    A non-MC88V line card is not allowed in the router if a Cisco uBR-MC88V line card exists in the chassis.

Recommended Action    Remove or disable the non-mc88v line card in the chassis and reboot the CMTS.

%MCU-6-HWREV: Slot [dec]: HW revision is [dec] 

Explanation    Hardware revision.

Recommended Action    No action is required.

%MCU-6-MC88V_NOT_SUPPORTED: MC88V card is not supported in a Non-MC88V chassis. 

Explanation    The Cisco uBR-MC88V line card is not allowed in the router if a non-MC88V line card exists in the chassis.

Recommended Action    No action is required.

%MCU-6-OLDHWREV: Slot [dec]: HW revision is below 1.8 - board should be upgraded 

Explanation    Old hardware revision is not supported.

Recommended Action    No action is required. This indicates a faulty cable line card.

%MCU-6-LEGACY_NOT_SUPPORTED: Non-MC88V card is not supported in a MC88V chassis. 

Explanation    A non-MC88V line card is not allowed in the router if a Cisco uBR-MC88V line card exists in the chassis.

Recommended Action    No action is required.

%MCU-5-RESET: MCU port adapter was in slot [dec] was reset 

Explanation    The indicated cable interface line card was reset, either by a user manually resetting the card from the command-line interface (CLI), or by the system.

Recommended Action    No action is needed.

MCUCLC

%MCUCLC-3-EREVENT: [chars] 

Explanation    The cable interface line card in the indicated slot experienced a general failure, as defined by the failure string.

Recommended Action    Verify that you are running released software on the CMTS. 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.

%MCUCLC-3-NOTMCU: PCI device ID seen as [hex], expected [hex] 

Explanation    The Cisco IOS software could not recognize the SiByte chips on the cable interface line card. This could indicate a faulty or incomplete initialization of the cable interface line card.

Recommended Action    Power down the Cisco CMTS router, remove and reinsert the cable interface line card, and reboot. If the message reoccurs, verify that you are running released software on the CMTS. Issue the show tech-support command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative and provide the representative with the gathered information.

%MCUCLC-6-PCIENBDISAB: NPE PCI data interface [[dec]]: [chars]

Explanation    The NPE peripheral component interconnect (PCI) data interface has been enabled/disabled.

Recommended Action    No action is required.

%MCUCLC-3-PCIANALYZE: PCI device ([dec]) initialization failed 

Explanation    The PCI device initialization failed on the cable interface line card. This typically indicates a system fault with the card.

Recommended Action    Remove and reinsert the specified cable interface line card. Verify that you are running released software on the CMTS. If the problem persists, contact your Cisco technical support representative to arrange for the Cisco uBR-MC16U/X or Cisco uBR-MC28U/X card to be upgraded or replaced.

%MCUCLC-3-UNKEVENT: [chars]: [dec] 

Explanation    The Cisco IOS software received an unknown event from the cable interface line card. This could indicate that the Cisco IOS software release that is running on the cable interface line card is not the same release that is running on the Cisco CMTS router.

Recommended Action    Verify that you are running released software on the CMTS. Remove and reinsert the cable interface line card to force it to reload its Cisco IOS software. If the problem persists, 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.

MCUFSM

%MCUFSM-3-BADSLOT: Invalid slot [dec] in function [chars] 

Explanation    The cable interface line card received an invalid slot number as part of an interprocess communications message.

Recommended Action    Verify that you are running released software on the CMTS. 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.

%MCUFSM-3-ENQFAIL: Enqueue of message failed slot ([dec]), major event ([dec]) 

Explanation    The indicated cable interface line card could not enqueue an OIR message to the proper event queue, typically because of insufficient memory resources.

Recommended Action    Issue the show processes memory sorted command to locate which process is consuming too much memory. 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 running released software on the CMTS. 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.

%MCUFSM-3-FSMEXECUTE: slot [dec]: fsm execution failed ([dec]) 

Explanation    The finite state machine that operates on the indicated cable interface line card encountered the general failure that is indicated by the failure string.

Recommended Action    Verify that you are running released software on the CMTS. 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.

%MCUFSM-3-GENERAL: [chars] 

Explanation    The finite state machine operating in the software encountered the general failure indicated by the failure string.

Recommended Action    Verify that you are running released software on the CMTS. 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.

%MCUFSM-3-LOADEXIST: slot [dec]: previous download process 

Explanation    A previous download process exists on the indicated cable interface line card, and a new download cannot start until this previous process terminates.

Recommended Action    Remove and reinsert the indicated cable interface line card. Verify that you are running released software on the CMTS. 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.

%MCUFSM-3-OPENERR: slot [dec]: failed to open file [chars] 

Explanation    The cable interface line card failed to open the indicated microcode software file for download to the card.

Recommended Action    Verify that you are running released software on the CMTS. 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.

%MCUFSM-3-UNKNOWN: card type is unknown for slot ([dec]) in [chars] 

Explanation    The OIR finite state machine could not identify the card that is in the indicated slot.

Recommended Action    Verify that you are running released software on the CMTS. 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.

MLS

The following are the MLS system messages:

%MLS_RATE-4-ENABLING_FIB_GLEAN_RECEIVE: [chars] will be subject to the output ACLs 
of the input VLAN 

Explanation    When FIB glean or FIB receive rate limiters are enabled, adjacency redirect is used. The router performs an egress lookup on the incoming interface and the result is applied on the incoming 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%MLS_RATE-4-OVERWRITING_PORTSEC_DEFAULT: Port security rate limiter was set to 
non-default value. 

Explanation    The default port security rate value is overwritten.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

MPLS_ADJ_SB

The following are the MPLS error messages:

%MPLS_ADJ_SB-4-NO_BACKUP_INTF: [chars] - ifnum [dec] 

Explanation    Backup interface cannot be programmed.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

MROUTE

The following are the MROUTE error messages:

%MROUTE-3-IGMP_LATE_PROCESS_ERR: IGMP process is not up yet 

Explanation    An error occurred while accessing IGMP process watched queue.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%MROUTE-4-SNMP_RADIX_ERR: Failed to [chars] snmp node [chars] snmp radix tree for 
multicast group (*, [IP_address]). 

Explanation    An error occured while adding or deleting SNMP nodes in SNMP radix tree when mroute is created or deleted.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

NICKEL10G

The following are the Nickel 10G ASIC error messages.

%NICKEL10G-3-N10GERRD: [chars]: [chars] - [dec]

Explanation    A Nickel10g non-fatal generic error is observed.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%NICKEL10G-3-N10GERRDD: [chars]: [chars] - [dec], [dec]

Explanation    A Nickel10g non-fatal error is observed.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%NICKEL10G-3-N10GERREVT: [chars] - ERR EVENT [chars], port [dec]

Explanation    Non fatal errors occurred on Nickel10g.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%NICKEL10G-3-N10GERRS: [chars]

Explanation    A Nickel10g non-fatal generic error is observed. Nickel10g driver is either not instantiated or initialization 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

 
    
    
   

%NICKEL10G-3-N10GERRSEND : [chars] - ERR EVENT [chars], port [dec] reporting to PRE

Explanation    Fatal errors occurred on Nickel10g.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

 
    
    
   

%NICKEL10G-3-N10GERRSSUSPEND : Too many Nickel10g ERR EVENTS [dec], suspending reporting

Explanation    Too many errors reported on Nickel10g.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

 
    
    
   

%NICKEL10G-3-N10GFIBNR : FIB is not Running, reporting it to PRE

Explanation    FIB is not in RUNNING state.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

 
    
    
   

%NICKEL10G-3-N10GINVIRB : [chars]

Explanation    Invalid Ironbus mode [dec], defaulting to QUAD.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

 
    
    
   

%NICKEL10G-3-N10GNOTUP : N10G is not operationally up

Explanation    Nickel10g is not operationally up.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

 
    
    
   

%NICKEL10G-3-N10GPREMISMATCH : PRE-A/B mismatch in N10G - driver:[dec], fpga:[dec]

Explanation    PRE-A/B mismatch in N10G driver.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%NICKEL10G-3-N10GSPIFAIL: N10G-Waxbill SPI link is out of sync 

Explanation    N10G-Waxbill SPI is out of sync, check LC crashdump.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

OCE

The following are OCE messages:

%OCE-3-GENERAL: [chars] 

Explanation    An internal software error has 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

OBFL

The following are OBFL messages:

%OBFL-6-OBFLSENSORACCESS: PRE5 OBFL: [chars] sensor access failure for sensor 
[chars](ID:[dec]) 

Explanation    PRE5 OBFL sensor access error.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%OBFL-6-OBFLSTORAGECCESS: PRE5 OBFL: [chars] operation on OBFL storage failed,OBFL 
address: [hex], num bytes: [dec] 

Explanation    PRE5 OBFL flash access error.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

PA_REM

The following are port adapter (PA) related messages.

%PA_REM_GENERAL: PA removal event FSM error messages 

Explanation    A general failure occurred in the operation of the PA removal event.

Recommended Action    Verify that you are running released software on the CMTS. 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.

%PA_REM_ENQFAIL: Enqueue of message failed slot

Explanation    Enqueue of a PA removal message to an event queue failed.

Recommended Action    Verify that you are running released software on the CMTS. 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.

%PA_REM_PCI_ERROR: PCI error address = 

Explanation    An unexpected PCI error has occurred.

Recommended Action    .Verify that you are running released software on the CMTS. 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.

PARSER

The following are parser error messages:

%PARSER-4-INVLDSYNTX: Syntax cleanup list updated while not syntax checking. 
FuncPtr / Context [chars] 

Explanation    Functions were mistakenly called, there may be more than listed

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

PCIE

%PCIE-3-PCIE_NODEV: PRE5 did not find the correct PCIe device, ID is [hex]! 

Explanation    PRE5 did not find correct PCIe devices.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

PIM

The following are the PIM error messages:

%PIM-4-NO_INPUT: PIM packet without input interface received from [IP_address] for 
[IP_address] 

Explanation    An unexpected PIM packet without input interface was received.

Recommended Action    Copy the source and destination information in the syslog. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%PIM_PROT-4-PROTOCOL_WARNING: [chars] - [chars] [chars] : [chars] 

Explanation    Internal protocol inconsistency warning.

Recommended Action    No action is needed.

PORT_SECURITY

The following are the port security error messages:

%PORT_SECURITY-4-PORTSEC_RATELIMIT_DISABLED: Layer 2 port security rate limiter 
disabled while port security enabled. 

Explanation    This message is seen when layer 2 port security rate limiter is disabled by user while port security is enabled.

Recommended Action    Configure the mls rate-limit layer2 port-security 6000 10 command.

%PORT_SECURITY-4-PORTSEC_RATELIMIT_FAIL: Fail to set port security rate limiter 
when enabling port security. 

Explanation    This failure occurs when port security is enabled.

Recommended Action    Configure the mls rate-limit layer2 port-security 6000 10 command. It may be necessary to remove an existing layer 2 rate limiter.

POWER1220

The following are the POWER error messages:

%POWR1220-4-INIT_NO_RESPONSE: POWR1220 is not responding. The device is [chars] 

Explanation    POWR1220 device is not responding.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%POWR1220-4-INIT_SEQUENCE_FAILURE: POWR1220 sequencing failure happened. The 
device is [chars] and register values are reg 0x03 [hex] reg 0x04 [hex] reg 0x05 
[hex] reg 0x07 [hex] reg 0x08 [hex] 

Explanation    POWR1220 device registers do now show correct values.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

PQUICC3

%PQUICC3-3-DDR_ERR: DDR [dec] [chars] error from memory 

Explanation    A soft-parity error from the memory has been detected. Normal system operation should continue.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

PXF

The following are the Parallel eXpress Forwarding (PXF) error messages:

 
    
   
: IB Stuck Pause Request Error in slot[dec]/subslot[dec]: 
status reg @ [hex] = 0x [hex] 

Explanation    Ironbus stuck pause request error is encountered.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%PXF_NICKEL-4-IRONBUS_IB_EVT: Nickel IB Event: IB Link ib_index:[[dec]], status: 
addr[[hex]] val[[hex]] 

Explanation    Nickel IB Event 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%PXF_NICKEL-2-IRONBUS_PLL_ERR: Titan ironbus slot[[dec]] subslot[[dec]] rx pll 
lock failed!

Explanation    Nickel PLL lock failed.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%PXF_QOS-3-QOS_SPKT_HANDLER_CANNOT_CREATE: Cannot create [chars] process 

Explanation    Insufficient memory on RP prevented creation of the QoS statistics packet handling process. All statistics packets will have to be handled at interrupt-level.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%PXF_QOS-3-QOS_SPKT_RESOURCE_FAIL: Cannot allocate a critical resource for 
[chars] process 

Explanation    Insufficient memory on RP prevented allocation of a critical resource for the QoS statistics packet handling process. All statistics packets will have to be handled at interrupt-level.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

QOS

The following are the QoS system messages:

%QOS-4-FO_IN_USE: Releasing feature object with reference count [dec] 

Explanation    This is an internal software error. A QoS policy feature object has a stale reference.

Recommended Action    If the message re-occurs, try to isolate the traffic conditions which trigger the message. 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

RADIAN

%RADIAN-3-CMIC_FAIL: Radian [dec], CMIC register [chars] fail for [chars], rc = 
[dec] 

Explanation    Radian CMIC register read or write operation failure.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%RADIAN-3-IL_INTR_ERR: Radian slot/unit [dec]/[dec] IL ERR INTR: [chars] 

Explanation    Radian IL ERROR interrupt.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%RADIAN-5-IL_INTR_MSG: Radian slot/unit [dec]/[dec] IL INTR: [chars] 

Explanation    Radian IL minor ERROR interrupt.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%RADIAN-2-IL_SYNC_ERR: [chars] Radian IL sync/align error, [chars] 

Explanation    Radian IL sync or align error with Cobalt4 IL.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%RADIAN-3-INIT_FAIL: [chars] for slot: [dec], unit: [dec], rc: [dec] 

Explanation    Radian init failure.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%RADIAN-3-MMU_INTR_ERR: Radian slot/unit [dec]/[dec] MMU ERR INTR: [chars] 

Explanation    Radian MMU ERROR interrupt.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%RADIAN-5-MMU_INTR_MSG: Radian slot/unit [dec]/[dec] MMU INTR: [chars] 

Explanation    Radian MMU minor ERROR interrupt.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%RADIAN-5-PD0_INTR_MSG: Radian slot/unit [dec]/[dec], PD0 INTR: [chars] 

Explanation    Radian PostDequeue minor ERROR0 interrupt.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%RADIAN-5-PD1_INTR_MSG: Radian slot/unit [dec]/[dec], PD1 INTR: [chars] 

Explanation    Radian PostDequeue minor ERROR1 interrupt.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%RADIAN-3-PE_INTR_ERR: Radian slot/unit [dec]/[dec], PE ERR INTR: [chars] 

Explanation    Radian PreEnqueue ERROR interrupt.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

 
    
   
: Radian slot/unit [dec]/[dec], PE INTR: [chars] 

Explanation    Radian PE minor ERROR interrupt.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%RADIAN-3-SCHAN_FAIL: Radian [dec], SCHAN [chars] fail for [chars], rc = [dec] 

Explanation    Radian S-Channel read or write operation failure.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%RADIAN-3-VLI_ACCESS_ERR: VLI Err: [chars] 

Explanation    Radian VLI access error.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%RADIAN-5-VLI_SWITCHOVER_MSG: Haba VLI switchover: [chars] in [int]ms 

Explanation    Haba switchover message.

Recommended Action    No action is required.

%RADIAN-3-VLI_SWITCHOVER_TIMEOUT: Haba VLI switchover: wait [chars] timeout 

Explanation    Haba switchover timeout.

Recommended Action    No action is required.

%RADIAN-5-XLPORT_INTR_MSG: Radian slot/unit [dec]/[dec], XLPORT INTR: [chars] 

Explanation    Radian XLPORT minor ERROR interrupt.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

RAVEN

Raven is a hardware FPGA on the Cisco uBR-MC3GX60V line card. The following are the Raven error messages:

%RAVEN-3-FATAL_ERP_ERROR: erp_mst_cfg [hex] erp_mst_err_phase [hex], 
erp_mst_err_addr [hex] 

Explanation    Fatal Raven ERP interrupt.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RAVEN-3-FATAL_EVENT: [chars] event; register value [hex] 

Explanation    Fatal Raven interrupt.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RAVEN-3-FATAL_LCL_BUS_ERROR: cap_reg [hex] cap_data [hex], cap_access [hex], 
[chars] transaction 

Explanation    Fatal unrecoverable local bus error is encountered.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RAVEN-3-FATAL_REC_EVENT: [chars] event; register value [hex] 

Explanation    Fatal Recoverable Raven interrupt.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RAVEN-3-FATAL_REC_LCL_BUS_ERROR: cap_reg [hex] cap_data [hex], cap_access [hex], 
[chars] transaction 

Explanation    Fatal recoverable local bus error.

Explanation    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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RAVEN-3-FATAL_REC_RLDRAM_ECC_ERROR: err_rec_addr [hex], err_rec_data3 [hex], 
err_rec_data2 [hex]err_rec_data1 [hex], err_rec_data0 [hex], err_rec_ecc [hex] 

Explanation    Fatal Recoverable RLDRAM ECC 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RAVEN-4-HIGH_PRIORITY_EVENT: [chars] event; register value [hex] 

Explanation    High Priority Raven interrupt

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RAVEN-4-HIGH_PRIORITY_SEU_EVENT: SEU Controller Error Detect event ; seu status 
[hex] 

Explanation    High Priority Raven Single Error Upset interrupt

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RAVEN-4-LOW_PRIORITY_EVENT: [chars] event; register value [hex] 

Explanation    Low Priority Raven interrupt

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RAVEN-5-PLL_NONFATAL_UNLOCK_EVENT: [chars] unlock 

Explanation    Expected Phase Locked Loop (PLL) unlock

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RAVEN-3-PLL_UNEXPECTED_UNLOCK_EVENT: [chars] unlock 

Explanation    Unexpected PLL unlock.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RAVEN-4-RLDRAM_EVENT: [chars] event; status [hex] 

Explanation    RLDRAM interrupt

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RAVEN-4-TSS_LOAD_EVENT: [chars] event 

Explanation    Transport Streams (TSS) load interrupt.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RAVEN-4-TSS_MISMATCH_EVENT: [chars] event 

Explanation    TSS mismatch interrupt.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RAVEN-4-TSS_PARITY_EVENT: [chars] event 

Explanation    TSS Parity interrupt. This error occurs due to an old DTCC firmware or if the DTI server is not synchronized.

Recommended Action    If the DTI server is not synchronized, reset the time and synchronize the DTI server or verify the DTCC firmware version using the show controller clock | in EPLD command.
If the version is 0xEE or lower, upgrade the DTCC firware using the test cable dtcc upgrade command. After the update is complete, verify the firmware version.

RFS

The following are RF Switch system messages:

%RFS-3-RFS_BOOL_CREATE_ERR: [chars]. 

Explanation    The RF switch RF client has error in creating watched boolean.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RFS-3-RFS_RF_PROG_ERR: [chars] [dec]. 

Explanation    The RF switch RF client has 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%RFS-3-RFS_RF_PROG_NOT_SENT_ERR: [chars]. 

Explanation    The RF switch RF client has error in sending client progression.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

RFSW

The following are RFSW error messages:

%RFSW-3-LCSO_FAIL: Receive a failed LCSO message from RFSW with sequence [hex]. 

Explanation    LCSO command failed to execute on RF switch.

Recommended Action    Check the switchcards state on RF Switch.

%RFSW-3-RELAY_FAIL: Relay failed for RFSW. 

Explanation    The relay testing for the RF switch failed.

Recommended Action    Check the connection between CMTS and RF switch.

%RFSW-6-HELLO_ERROR: The switchcard in RFSW for slot [dec], group [dec] is in error 
with the reason [chars]. 

Explanation    The switchcard in the RF switch is in error state.

Recommended Action    Check the switchcard state of the RF switch.

%RFSW-6-HELLO_PROTECT: The protecting state in RFSW is wrong (expect [dec], get 
[dec]). 

Explanation    The protecting state in the RF switch is wrong.

Recommended Action    Disable and the re-enable the rfswitch auxport enable command configuration.

%RFSW-6-SWITCHCARD_CHANGE: Switchcards in RFSW is changed: inserted:[chars], 
removed:[chars]; The related group bitmap is [chars] 

Explanation    Switchcards in RF switch has been inserted/removed.

Recommended Action    No action is needed.

RPLIC

%RPLIC-3-ACTIVATE: Could not activate [chars], rc [int] [chars] 

Explanation    The RP license module activation failed.

Recommended Action    Reload the PRE. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%RPLIC-6-LICGRANT: No license was granted for [chars] 

Explanation    License was not granted for this TenGigabit Ethernet.

Recommended Action    Check the available license count. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%RPLIC-6-NOSHUT: [chars] has been no shut 

Explanation    TenGigabit Ethernet license is in no shut state.

Recommended Action    No action is required.

%RPLIC-3-NULLHWIDB: Can't get hwidb of slot [dec] port [dec] 

Explanation    Failed to get hwidb of the backhaul ethernet.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%RPLIC-3-REGISTER: Could not register [chars], rc [int] [chars] 

Explanation    The RP license feature register failed.

Recommended Action    Reload the PRE. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%RPLIC-1-REGISTER_STORAGE: Register license storage [chars] failed, rc [int] 
[chars] 

Explanation    The RP license storage register failed.

Recommended Action    Check the RP license details. If the problem is not fixed by multiple reinstall attempts, board RMA may be required.

%RPLIC-1-REGPERMSTORFAIL: Register license permanent storage [chars] failed, rc 
[int] [chars] 

Explanation    The RP license storage register failed.

Recommended Action    Check the RP license details. If the problem is not fixed by multiple reinstall attempts, board RMA may be required.

%RPLIC-3-RELEASE: Failed to release license handle [hex] units [int], rc [int] 
[chars] 

Explanation    The RP license feature release failed.

Recommended Action    Reload the PRE. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%RPLIC-3-REQUEST: Failed to request license feature [chars] units [int], rc [int] 
[chars] 

Explanation    The RP license feature request failed.

Recommended Action    Reload the PRE. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%RPLIC-6-SHUT: [chars] remains in down state due to insufficient licenses 

Explanation    Unable to bring up the TenGigabit Ethernet due to insufficient number of licenses.

Recommended Action    Check the number of licenses installed.

%RPLIC-3-STORAGE: License storage error, [chars] 

Explanation    The RP license storage status is BAD.

Recommended Action    Check the RP license details. If the problem is not fixed by multiple reinstall attempts, board RMA may be required.

RTT

The following are RTT error messages:

%RTT-4-OPER_CLOSS: condition [chars], entry number = [dec] 

Explanation    This message logs connection loss condition in the IPSLAs operations. This message is enabled when the ip sla monitor logging trap command is entered.

Recommended Action    Ensure that the destination for the IPSLAs operation is reachable. Also ensure that the IPSLAs responder operation is configured on the destination. If you do not want to log these messages for IPSLA operations, enter the no ip sla monitor logging trap command to disable logging.

%RTT-4-OPER_TIMEOUT: condition [chars], entry number = [dec] 

Explanation    This message logs timeout condition in the IPSLAs operations. This message is enabled when the ip sla monitor logging trap command is entered.

Recommended Action    Ensure that the destination for the IPSLAs operation is reachable. If you do not want to log these messages for IPSLAs operations, enter the no ip sla monitor logging trap command to disable logging.

%RTT-3-SAATWINITFAIL: IP SLAs: Generic Timer wheel timer functionality failed to 
initialize 

Explanation    IP SLAs failed to initialize the timer wheel.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

SFP

The following are SFP error messages:

%SFP-5-SFP_MISSING: [chars] SFP missing from port [dec] 

Explanation    SFP has been removed.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%SFP-5-SFP_OK: [chars] SFP inserted in port [dec] 

Explanation    SFP has been inserted.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%SFP-3-SFP_UNINITIALIZED: [chars] SFP inserted in port [dec], error status [dec] 

Explanation    The SFP is inserted, however, 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%SFP-3-SW_ERR: SFP Driver error: [chars] (sfp [dec] errcode [dec]) 

Explanation    Internal error in the SFP driver.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%SFP-3-SW_I2C_ERR: SFP Driver i2c error: [chars] (sfp [dec] addr [hex] errcode 
[dec]) 

Explanation    IIC controller Access error to SFP device.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

SNMP

This section describes error messages generated for the Simple Network Management Protocol.

SNMP-5-LINK_DOWN: LinkDown:Interface [chars] changed state to down

Explanation    The state of the interface is changed to down.

Recommended Action    Check the network link to ensure that the link to the interface is connected.

SNMP-5-LINK_UP: LinkUp:Interface [chars] changed state to up

Explanation    The state of the interface is changed to up.

Recommended Action    No action is required.

SPAWBCMTS

%SPAWBCMTS-4-SFP_INCOMPATIBLE: [chars], [chars] SFP inserted in port [dec] 
incompatible with [chars] mode 

Explanation    SFP incompatible with current mode.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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-5-SWITCHOVER_PRI: primary port(port 0) will be active for [chars] 

Explanation    TenGigabit Ethernet link is being restored for the primary port.

Recommended Action    Check the secondary port on the SPA.

%SPAWBCMTS-5-SWITCHOVER_SEC: secondary port(port 1) will be active for [chars] 

Explanation    TenGigabit Ethernet link is lost for the primary port.

Recommended Action    Check the secondary port on the SPA.

SW_WDOG

The following are software watchdog error messages:

%SW_WDOG-4-MONITOR_STATE_DEBOUNCE: SW Watchdog moved to DEBOUNCE state 

Explanation    System State Logging is being debounced.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%SW_WDOG-4-MONITOR_STATE_LOG: SW Watchdog moved to LOG state, last IPC timestamp 
[time-stamp] 

Explanation    System state logging has been enabled.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%SW_WDOG-4-MONITOR_STATE_PAUSE: SW Watchdog moved to PAUSE state 

Explanation    System State logging has been paused.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%SW_WDOG-3-SW_WDOG_IPC_RECOVER: SW Watchdog detected IPC link down, but it 
recovered 

Explanation    No interprocess communication (IPC) link was detected by the software watchdog, however the IPC link recovered before the crash threshold was reached.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.

%SW_WDOG-3-SW_WDOG_TIMEOUT: SW Watchdog failed to detect IPC link up 

Explanation    No IPC link was detected by the software watchdog.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

SYS

This section describes error messages generated for the system.

%SYS-3-LOGGER_DROPPED: System dropped [decimal] console debug messages.

Explanation    Debugging or informational messages are rapidly generated and cannot be displayed on the console.

Recommended Action    To reduce the number of debugging or informational messages that are displayed, use conditional debugging and turn off the console logging. Enter the no logging console guaranteed command, or turn off link-state messages for some other interfaces.

UBR7100, UBR7200, and UBR10000

This section lists the CMTS system error messages and DOCSIS error messages that are common to the Cisco uBR7100 series, Cisco uBR7200 series, and Cisco uBR10012 routers. Most of these error messages will appear on all CMTS platforms, but some error messages appear only for one or two platforms.


Note The FACILITY name of the newly added common messages in Cisco IOS Release 12.2(33)SCA does not indicate %UBR7100 or %UBR10000 as the CMTS platform even if the messages are applicable to those platforms. For example, in the case of the %UBR7200-6-BADIPASSIGNMENT error message, the same message is displayed for uBR7100 and uBR10000 CMTS platforms without changing the FACILITY name to %UBR7100-6-BADIPASSIGNMENT or %UBR10000-6-BADIPASSIGNMENT.


%UBR10000-3-ACFE_FAILURE: [char]

Explanation    ACFE has detected invalid states.

Recommended Action    If the problem persists, disable ACFE. Capture the logs and contact the TAC.

%UBR10000-6-ACFE_NOTIFICATION: BG [int] of cluster [int] on Modular-Cable 
[dec]/[dec]/[dec] is oversubscribed by [int] kbps

Explanation    ACFE has detected that committed rate may be oversubscribed, probably due to system configuration change or HA events; ACFE is trying to recover.

Recommended Action    If ACFE cannot recover by itself, revert the latest configuration change, or remove some CIR flows on the bonding group. If the problem persists, capture the logs and contact the TAC.

%UBR10000-6-ACFE_NOTIFICATION: BG [int] of cluster [int] on Modular-Cable 
[dec]/[dec]/[dec] has recovered from oversubscription

Explanation    The system was oversubscribed but ACFE has covered the situation.

Recommended Action    No action is required.

%UBR7100-6-ACTIVE
%UBR7200-6-ACTIVE
%UBR10000-6-ACTIVE: Cable clock [chars] reference active

Explanation    The clock reference has become active.

Recommended Action    No action is needed.

%UBR10000-6-ACFE_REJECTION: ACFE has rejected QoS queue for service flow [int] on 
[char], MAC_addr [hex], min_rate [int] kbps, rej_code [char] 

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

Recommended Action    This problem would typically happen only on a highly overloaded interface. If the problem persists on an interface, try to provision more RF channels.

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

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

Recommended Action    This problem would typically happen only on a highly overloaded interface. If the problem persists on an interface, try to provision more RF channels.

%UBR7100-3-ALARM_ERROR
%UBR7200-3-ALARM_ERROR
%UBR10000-3-ALARM_ERROR: [chars]

Explanation    Entity alarm entity creation fails error message.

Recommended Action    Check the error message, diagnostic information, and the cable RP/CLC LED to check whether the entity is available, and what is its status and any issue. Be careful that when frequency stacking is used, facility alarm cannot reflect the real entity's issue by design. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%UBR7100-6-ALARM_INFO
%UBR7200-6-ALARM_INFO
%UBR10000-6-ALARM_INFO: [chars][chars][chars][chars][chars]

Explanation    Alarm assertion or deassertion information.

Recommended Action    This message is informational only.

%UBR7200-5-ATTRIBUTE_CHANGE_CONFLICT: <133>CMTS[DOCSIS]:<75010100> Attribute 
Masks for SF (SFID %lu) do not satisfy the provisioned Attribute Masks

Explanation    A change in the provisioned attribute mask causes a mismatch.

Recommended Action    Modify the provisioned attributes so that they meet requirements.

%UBR7100-5-AUTHFAIL
%UBR7200-5-AUTHFAIL
%UBR10000-5-AUTHFAIL: Authorization failed for Cable Modem [enet] on interface [chars]

Explanation    The registration of this modem has failed because of an invalid MIC string, or because the cable modem used a stale or spoofed DOCSIS configuration file.

Recommended Action    Ensure that the shared secret that is in the configuration file matches the shared secret that is configured in the cable modem. If the shared secrets match, take action against the cable modem that is possibly spoofing, storing, and replaying its DOCSIS configuration file.

%UBR7100-3-AUTH_INVALID_INVALID_KEY_SEQUENCE_NUMBER 
%UBR7200-3-AUTH_INVALID_INVALID_KEY_SEQUENCE_NUMBER
%UBR10000-3-AUTH_INVALID_INVALID_KEY_SEQUENCE_NUMBER: <132>CMTS[DOCSIS]:<66030206> Auth Invalid - Invalid Key Sequence Number. CM Mac Addr <[enet]>

Explanation    The specified cable modem failed to register with BPI+ authorization because it presented an invalid key sequence number (KSN).

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software. If the problem persists, use the show interface cable key sid and show interface cable key mac commands to collect information about the cable modem with the problem. You can also turn on BPI+ debugging using the debug cable privacy and debug cable bpi commands.

%UBR7100-3-AUTH_INVALID_MESSAGE_AUTHENTICATION_FAILURE 
%UBR7200-3-AUTH_INVALID_MESSAGE_AUTHENTICATION_FAILURE
%UBR10000-3-AUTH_INVALID_MESSAGE_AUTHENTICATION_FAILURE: <132>CMTS[DOCSIS]:<66030207> Auth Invalid - Message(Key Request) Authentication Failure. CM Mac Addr <[enet]>

Explanation    The specified cable modem failed to register with BPI+ authorization because it presented an invalid key request message. The cable modem is expected to reattempt authorization.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software. If the problem persists, use the show interface cable key sid and show interface cable key mac commands to collect information about the cable modem with the problem. You can also turn on BPI+ debugging using the debug cable privacy and debug cable bpi commands.

%UBR7100-3-AUTH_INVALID_NO_INFORMATION 
%UBR7200-3-AUTH_INVALID_NO_INFORMATION
%UBR10000-3-AUTH_INVALID_NO_INFORMATION: <132>CMTS[DOCSIS]:<66030202> Auth Invalid - No Information. CM Mac Addr <[enet]>

Explanation    The specified cable modem failed to register with BPI+ authorization because it did not present the required information in its request message. The cable modem is expected to reattempt authorization.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software. If the problem persists, use the show interface cable key sid and show interface cable key mac commands to collect information about the cable modem with the problem. You can also turn on BPI+ debugging using the debug cable privacy and debug cable bpi commands.

%UBR7100-3-AUTH_INVALID_UNAUTHORIZED_CM 
%UBR7200-3-AUTH_INVALID_UNAUTHORIZED_CM
%UBR10000-3-AUTH_INVALID_UNAUTHORIZED_CM: <132>CMTS[DOCSIS]:<66030203> Auth Invalid - Unauthorized CM. CM Mac Addr <[enet]>

Explanation    The specified cable modem failed to register with BPI+ authorization because this cable modem is not authorized to use the cable network. The cable modem should not attempt to reregister.

Recommended Action    No action needed if this cable modem is correctly marked as unauthorized. Otherwise, check the provisioning software to make sure the MAC address for this cable modem is entered correctly.

%UBR7100-3-AUTH_INVALID_UNSOLICITED 
%UBR7200-3-AUTH_INVALID_UNSOLICITED
%UBR10000-3-AUTH_INVALID_UNSOLICITED: <132>CMTS[DOCSIS]:<66030205> Auth Invalid - Unsolicited. CM Mac Addr <[enet]>

Explanation    The specified cable modem failed to register with BPI+ authorization because this cable modem sent an unsolicited request for authorization. The cable modem is expected to reattempt authorization.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software. If the problem persists, use the show interface cable key sid and show interface cable key mac commands to collect information about the cable modem with the problem. You can also turn on BPI+ debugging using the debug cable privacy and debug cable bpi commands.

%UBR7100-3-AUTH_REJECT_NO_INFORMATION 
%UBR7200-3-AUTH_REJECT_NO_INFORMATION
%UBR10000-3-AUTH_REJECT_NO_INFORMATION: <132>CMTS[DOCSIS]:<66030102> Auth Reject - No Information. CM Mac Addr <[enet]>

Explanation    The specified cable modem failed to register with BPI+ authorization because it did not present the required information in its request message. The cable modem is expected to reattempt authorization.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software. If the problem persists, use the show interface cable key sid and show interface cable key mac commands to collect information about the cable modem with the problem. You can also turn on BPI+ debugging using the debug cable privacy and debug cable bpi commands.

%UBR7100-3-AUTH_REJECT_PERMANENT_AUTHORIZATION_FAILURE 
%UBR7200-3-AUTH_REJECT_PERMANENT_AUTHORIZATION_FAILURE
%UBR10000-3-AUTH_REJECT_PERMANENT_AUTHORIZATION_FAILURE: <132>CMTS[DOCSIS]:<66030108> Auth Reject - Permanent Authorization Failure. CM Mac Addr <[enet]>

Explanation    The specified cable modem failed to register with BPI+ authorization because the CMTS has permanently rejected this cable modem, instructing it not to attempt reauthorization. This could also occur because the cable modem attempted to register with an invalid manufacturer's digital certificate. The certificate could contain an invalid signature, or the current date and time are outside of the certificate's valid operating range.

Recommended Action    Use the show clock on the CMTS to verify that the date and time on the CMTS are set correctly. If the date and time are not correct, use the clock set command to set it to the current date and time, and then use the clock update-calendar command to update the internal clock.

If the CMTS clock is correct, check that the cable modem contains a valid manufacturer's certificate. If necessary, upgrade the cable modem's software and reboot the cable modem. Verify that the cable modem was made from a known manufacturer and that the CMTS has a valid CA certificate for that manufacturer. Also verify that the cable modem is presenting a valid digital certificate.

Otherwise, verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. If the problem persists, use the show interface cable key sid and show interface cable key mac commands to collect information about the cable modem with the problem. You can also turn on BPI+ debugging using the debug cable privacy and debug cable bpi commands.

%UBR7100-3-AUTH_REJECT_UNAUTHORIZED_CM 
%UBR7200-3-AUTH_REJECT_UNAUTHORIZED_CM
%UBR10000-3-AUTH_REJECT_UNAUTHORIZED_CM: <132>CMTS[DOCSIS]:<66030103> Auth Reject - Unauthorized CM. CM Mac Addr <[enet]>

Explanation    The specified cable modem failed to register with BPI+ authorization because this cable modem is not authorized to use the cable network. The cable modem should not attempt to reregister.

Recommended Action    No action needed if this cable modem is correctly marked as unauthorized. Otherwise, check the provisioning software to make sure the MAC address for this cable modem is entered correctly.

%UBR7100-3-AUTH_REJECT_UNAUTHORIZED_SAID 
%UBR7200-3-AUTH_REJECT_UNAUTHORIZED_SAID
%UBR10000-3-AUTH_REJECT_UNAUTHORIZED_SAID: <132>CMTS[DOCSIS]:<66030104> Auth Reject - Unauthorized SAID. CM Mac Addr <[enet]>

Explanation    The specified cable modem failed to register with BPI+ authorization because it did not present a valid Security Association ID (SAID) in its request message. The cable modem is expected to reattempt authorization.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. If the Cisco CMTS is running Cisco IOS Release 12.2(8)BC1 or later release, and if this cable modem is running DOCSIS 1.0 software, verify that its DOCSIS configuration file includes option 17, Baseline Privacy Configuration settings. (For information on configuring the option 17 settings, see the Tech Note, Auth Reject-Unauthorized SAID Error Messages and BPI Configuration Changes, at the following URL:

http://www.cisco.com/en/US/tech/tk86/tk168/technologies_tech_note09186a0080094eb3.shtml

Otherwise, verify that the CMTS is running released software. If the problem persists, use the show interface cable key sid and show interface cable key mac commands to collect information about the cable modem with the problem. You can also turn on BPI+ debugging using the debug cable privacy and debug cable bpi commands.

%UBR7100-3-AUTH_REJECT_TOD_NOT_ACQUIRED 
%UBR7200-3-AUTH_REJECT_TOD_NOT_ACQUIRED
%UBR10000-3-AUTH_REJECT_TOD_NOT_ACQUIRED: <132>CMTS[DOCSIS]:<66030109> Auth Reject - Time of Day not acquired. CM Mac Addr <[enet]>

Explanation    The specified cable modem failed to register with BPI+ authorization because it did not acquire the current date and time from a Time-of-Day (ToD) server. The cable modem uses the current time to verify its BPI+ digital certificates.

Recommended Action    Verify that the ToD server is online and operational. Also verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software. If the problem persists, use the show interface cable key sid and show interface cable key mac commands to collect information about the cable modem with the problem. You can also turn on BPI+ debugging using the debug cable privacy and debug cable bpi commands.

%UBR7100-3-BADARPDELETE 
%UBR7200-3-BADARPDELETE
%UBR10000-3-BADARPDELETE: Tried to remove arp entry for [IP_address] that is not dynamic

Explanation    A request was made to delete a non-dynamic ARP entry, which typically means an IP address was being replaced by a new device. This in turn could indicate a possible spoofing attempt, in which a user is taking IP addresses that are normally assigned by the DHCP server and statically assigning them to their own CPE devices. This situation can also occur when a partial ARP entry exists for a cable modem (such as might happen when you ping a cable modem that was previously online but has since been shut down, or occasionally during an N+1 (1:n) HCCP switchover).

Recommended Action    Look for a possible CMTS IP address spoofing attempt. Also verify that the DHCP server is not assigning the same IP address as both a statically and a dynamically assigned address. If this problem persists, try enabling either the cable arp command or the cable source-verify dhcp command, or both, on the cable interface.

%UBR7100-3-BADARPREPLY
%UBR7200-3-BADARPREPLY
%UBR10000-3-BADARPREPLY: Interface [chars], ARP reply from invalid source. Expected SID=[dec], Actual SID=[dec]

Explanation    The indicated cable interface received an ARP reply with an IP address that is associated with another cable interface. This can indicate possible IP address spoofing.

Recommended Action    Look for evidence of a spoofing attempt. If this error occurs after a clear arp command is issued, verify that the cable source-verify command has been configured on the cable interface so that the ARP replies can be learned correctly.

%UBR7100-3-BADARPREQUEST
%UBR7200-3-BADARPREQUEST
%UBR10000-3-BADARPREQUEST: Interface [chars], ARP request from invalid source. IP=[IP_address], MAC=[enet], Expected SID=[dec], Actual SID=[dec]

Explanation    The indicated cable interface received an ARP request with an IP address that is associated with another cable interface. This can indicate possible IP address spoofing.

Recommended Action    Look for evidence of a spoofing attempt. For more information, see the cable source-verify command.

Recommended Action   

%UBR7100-4-BADCFGFILE
%UBR7200-4-BADCFGFILE
%UBR10000-4-BADCFGFILE: Modem config file [chars] at [integer]: [chars]

Explanation    The DOCSIS configuration file for the cable modem failed its CMTS MIC verification, either because the MIC is missing or because the CMTS MIC failed verification with the shared secret or secondary shared secrets that have been configured for the cable interface. This message will occur when the dynamic secret feature is enabled on the cable interface with the cable dynamic-secret command.

Recommended Action    Verify that the DOCSIS configuration file for the cable modem has been created using the correct shared secret value. Also verify that the DHCP server is specifying the proper configuration file for this cable modem, and that the configuration file on the TFTP server is the correct one. If all of these are correct, check for a possible theft-of-service attempt by a user attempting to upload a modified DOCSIS configuration file into the operator's TFTP server.

%UBR7100-4-BADCFGFILE_V6
%UBR7200-4-BADCFGFILE_V6
%UBR10000-4-BADCFGFILE_V6: Modem config file [chars] at v6 IP_address: [chars]

Explanation    The DOCSIS configuration file for the cable modem could not perform the CMTS Message Integrity Check (MIC) either because the MIC is missing or because the CMTS MIC failed verification with the shared secret or secondary shared secrets that have been configured for the cable interface. This message will occur when the dynamic secret feature is enabled on the cable interface with the cable dynamic-secret command.

Recommended Action    Verify that the DOCSIS configuration file for the cable modem has been created using the correct shared secret value. Also verify that the configuration files specified on the DHCP server and the TFTP server are correct. If all of these are correct, check for a possible theft-of-service attempt by a user attempting to upload a modified DOCSIS configuration file into the operator's TFTP server.

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

Explanation    The Cisco uBR10012 PRE module received an error in the clock on the backplane from the TCC+ card in the indicated slot. This typically indicates that the primary TCC+ card encountered an error and was put into the maintenance state, and that the redundant TCC+ card has been activated and is now the primary TCC+ card.

Recommended Action    Reinstall or replace the TCC+ card that is reporting the error. 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.

%UBR7100-3-BADFFTINTERRUPT
%UBR7200-3-BADFFTINTERRUPT
%UBR10000-3-BADFFTINTERRUPT: BCM3138 chip [dec] dma interrupt error.

Explanation    Some cable interface line cards use the Broadcom BCM3138 burst receiver to perform a Fast Fourier Transform (FFT) for digital spectrum analysis, and the card should perform only one FFT operation at a time. This error message indicates that the indicated BCM3138 chip was not idle while another chip was performing an FFT operation, which indicates a DMA interrupt error occurred. This is likely a software error, but it could also indicate a hardware fault in rare cases.

Recommended Action    Verify that you are running released software on the CMTS. 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.

%UBR7100-3-BADFFTSTATE
%UBR7200-3-BADFFTSTATE
%UBR10000-3-BADFFTSTATE: BCM3138 chip [dec] is in wrong state [dec], expected state [dec]

Explanation    Some cable interface line cards use the Broadcom BCM3138 burst receiver to perform a Fast Fourier Transform (FFT) for digital spectrum analysis, and the card should perform only one FFT operation at a time. This error message indicates that the indicated BCM3138 chip was not in the correct state for the current FFT operation, which theoretically should never happen. This is likely a software error, but it could also indicate a hardware fault in rare cases.

Recommended Action    Verify that you are running released software on the CMTS. 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.

%UBR7100-3-BADFFTSTATE2
%UBR7200-3-BADFFTSTATE2
%UBR10000-3-BADFFTSTATE2: BCM3138 chip [dec] is not idle when it should be

Explanation    Some cable interface line cards use the Broadcom BCM3138 burst receiver to perform a Fast Fourier Transform (FFT) for digital spectrum analysis, and the card should perform only one FFT operation at a time. This error message indicates that the indicated BCM3138 chip did not have data available when it signaled that data was available, which theoretically should never happen. This is likely a software error, but it could also indicate a hardware fault in rare cases.

Recommended Action    Verify that you are running released software on the CMTS. 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.

%UBR7100-6-BADIPASSIGNMENT
%UBR7200-6-BADIPASSIGNMENT
%UBR10000-6-BADIPASSIGNMENT:[chars] dropped: Interface [chars] Mac [enet] SID [integer] L3_Interface [chars]
IP [IP_address] already assigned to MAC=[enet], Interface [chars] SID [integer],

Explanation    An incorrect DHCP assignment might have occurred.

Recommended Action    Verify that the DHCP server configuration is correct.

%UBR7100-3-BADIPSOURCE
%UBR7200-3-BADIPSOURCE
%UBR10000-3-BADIPSOURCE: Interface [chars], IP packet from invalid source. IP=[IP_address], MAC=[enet], Expected SID=[dec], Actual SID=[dec]

Explanation    The indicated cable interface received a packet with an IP address that is associated with another cable interface. This can be the result of a possible IP address spoofing attempt as it indicates that the CM or CPE device is using an IP address that was not properly assigned by the provider's DHCP servers.

Recommended Action    Look for evidence of a spoofing attempt. For more information, see the cable source-verify command. Also verify that the CMTS is not using static ARP addresses, using the arp ip-address mac-address command, as this could cause problems if the IP address ever moves to another device.

%UBR7100-3-BADIPSOURCE_BUNDLE
%UBR7200-3-BADIPSOURCE_BUNDLE
%UBR10000-3-BADIPSOURCE_BUNDLE: Interface [chars], IP packet from invalid source. IP=[IP_address], MAC=[enet], Expected Interface=[chars] SID=[dec], Actual Interface=[chars] SID=[dec]

Explanation    The indicated cable interface received a packet with an IP address that is associated with another cable interface bundle. This can be the result of a possible IP address spoofing attempt as it indicates that the CM or CPE device is using an IP address that was not properly assigned by the provider's DHCP servers.

Recommended Action    Look for evidence of a spoofing attempt. For more information, see the cable source-verify command. Also verify that the CMTS is not using static ARP addresses, using the arp ip-address mac-address command, as this could cause problems if the IP address ever moves to another device.

%UBR7100-6-BADIPSOURCE_SUBNET
%UBR7200-6-BADIPSOURCE_SUBNET
%UBR10000-6-BADIPSOURCE_SUBNET: Interface [chars], IP packet from invalid source. IP=[IP_address], MAC=[enet], Expected SID=[dec], Actual SID=[dec]

Explanation    The indicated cable interface received a packet with an IP address that is associated with another cable interface subnet. This can be the result of a possible IP address spoofing attempt as it indicates that the CM or CPE device is using an IP address that was not properly assigned by the provider's DHCP servers. This can also occur if a CPE device fails to obtain an IP address through DHCP and defaults to the hardcoded IP address built into its operating system (usually this is an IP address in the 169.254.0.0 subnet).

Recommended Action    Look for evidence of a spoofing attempt. For more information, see the cable source-verify command. If this is a CPE device, check that it is configured correctly to use DHCP addressing. If necessary, have the customer release and renew the IP address on the CPE device. Also verify that the CMTS is not using static ARP addresses, using the arp ip-address mac-address command, as this could cause problems if the IP address ever moves to another device.

%UBR7100-5-BADMNCSMSG
%UBR7200-5-BADMNCSMSG
%UBR10000-5-BADMNCSMSG: Invalid DOCSIS Message received from a Cable Modem for interface [chars]

Explanation    A cable modem sent a DOCSIS message that is invalid for this CMTS. This usually occurs because the cable modem is not DOCSIS-compliant.

Recommended Action    Locate the cable modem that sent this message and replace it with a DOCSIS-compliant modem. Verify that the cable modem is using a valid DOCSIS configuration file.

%UBR7100-4-BAD_NETWORK_ACCESS_CONFIGURATION 
%UBR7200-4-BAD_NETWORK_ACCESS_CONFIGURATION
%UBR10000-4-BAD_NETWORK_ACCESS_CONFIGURATION: <133>CMTS[DOCSIS]:<73010800> Network Access has Invalid Parameter. CM Mac Addr <[enet]>

Explanation    A registration request from the specified cable modem included an invalid value for the Network Access parameter. This parameter controls whether the CPE devices attached to the cable modem can access the cable network, and its only valid values can be either 0 (CPE devices are not allowed network access) or 1 (CPE devices are allowed to access the network).

Recommended Action    Check the DOCSIS configuration file being used by this cable modem and ensure that the Network Access parameter is set to either 0 or 1. No other values are allowed.

%UBR7100-4-BAD_REGISTRATION 
%UBR7200-4-BAD_REGISTRATION
%UBR10000-4-BAD_REGISTRATION: Cable modem [enet] on interface [chars] when [chars] attempted re-registration with different QoS

Explanation    The indicated cable modem sent a registration request, but the CMTS shows that a modem with this MAC address is already registered and online with a different QoS profile. This could occur if a user has hacked a cable modem to change its MAC address. This could also possibly occur after the CMTS performs an HCCP switchover of a cable interface, and a cable modem on that interface sent a registration request message during a loss-of-sync period.

Recommended Action    If an HCCP switchover did occur, check the indicated cable modem for non-DOCSIS-compliant software. Otherwise, check for a possible theft-of-service attack where a user has hacked a cable modem to give it a different MAC address that is a duplicate of an existing modem.

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

Explanation    The active TCC+ card in the indicated slot was put in maintenance mode.The redundant TCC+ card (if installed) has become the active, primary TCC+ card. Possible reasons for the card being put in maintenance mode include:

Holdover rcvd by Active/Backup Card—Possibly a hardware fault.

Bad Clock reported by CLC(s)—The cable interface line cards are reporting that the clock signal that is being received by the TCC+ card is invalid.

TRU Loss of Sync—The TCC+ card has lost synchronization with its clock signal.

Recommended Action    Reinstall or replace the TCC+ card that is reporting the error. 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.

%UBR7100-4-BADTXOFFSET
%UBR7200-4-BADTXOFFSET
%UBR10000-4-BADTXOFFSET: Bad timing offset [dec] detected for cable modem [enet].

Explanation    The cable modem is not using the correct starting offset during initial ranging, causing a zero, negative timing offset to be recorded by the CMTS for this modem. The CMTS internal algorithms that rely on the timing offset parameter will not analyze any modems that do not use the correct starting offset. The modems may not be able to function, depending on their physical location on the cable plant.

Recommended Action    Locate the cable modem based on the MAC address and report the initial timing offset problem to the cable modem vendor. Replace the unit with a DOCSIS-compliant cable modem.

%UBR7100-3-BADUSPORT
%UBR7200-3-BADUSPORT
%UBR10000-3-BADUSPORT: Interface [chars] Port U[dec] invalid, highest port number is U[dec]

Explanation    The specified upstream port number was invalid.

Recommended Action    Reenter the command using a valid upstream port number. Upstream port numbers start with 0 and will end with the value given in this message.

%UBR7100-4-BPI_WARNING
%UBR7200-4-BPI_WARNING
%UBR10000-4-BPI_WARNING: [chars]: SID=[dec], KeySeq=[dec], Cable Interface <[chars]>

Explanation    The CMTS received an invalid traffic exchange key (TEK) key sequence value from a cable modem on the specified cable interface. This could occur if one or more MAC-layer messages have been lost, if the cable modem is not properly configured for BPI operations, or if a software error has occurred.

Recommended Action    If this message occurs only occasionally, it can be ignored. Otherwise, check that the cable modem is using a proper DOCSIS configuration file. This message can also appear if the cable modem is not running DOCSIS-certified software, particularly if the error message indicates that an invalid TEK was received from the cable modem. Verify that the cable modem is running current software that conforms to the DOCSIS standard.

If this message 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. Contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR7100-3-BRIDGE_DELETE
%UBR7200-3-BRIDGE_DELETE: Interface [chars], error in deleting address [dec] from host tables

Explanation    An internal software error occurred during CMTS tables management. This error can occur occasionally if a CPE device has been statically assigned the same IP address as another device.

Recommended Action    Verify that all CPE devices are assigned the proper IP addresses. Otherwise, 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.

%UBR7100-3-BUN_MCAST_NOFREE_MAC
%UBR7200-3-BUN_MCAST_NOFREE_MAC
%UBR10000-3-BUN_MCAST_NOFREE_MAC: Fail to allocate free Bundle Multicast Map Entry for Bundle:[decimal] Group:[IP_address] Source:[IP_address]IDB:[chars]

Explanation    An internal software 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%UBR7100-3-BUN_MCAST_REV_MAP_ERR
%UBR7200-3-BUN_MCAST_REV_MAP_ERR
%UBR10000-3-BUN_MCAST_REV_MAP_ERR: Unable to find the Multicast Mapped Entry from reverse-mapping table for Bundle:[decimal] MAC:[enet]

Explanation    An internal software 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%UBR7100-3-BURSTINUSE
%UBR7200-3-BURSTINUSE
%UBR10000-3-BURSTINUSE: Can not remove Burst Profile. Burst Profile is in use.

Explanation    The burst profile cannot be removed because the currently defined modulation profiles use the specified burst profile.

Recommended Action    Remove any modulation profiles that use this burst profile and reenter the command.

%UBR7100-6-CACHE_ENGINE_BUF_FULL
%UBR7200-6-CACHE_ENGINE_BUF_FULL
%UBR10000-6-CACHE_ENGINE_BUF_FULL: Max. cache buffer has been reached.

Explanation    The cache buffer has reached its limit. The cache engine service for the current request is denied.

Recommended Action    This message is informational only.

%UBR7100-4-CACHE_ENGINE_WARNING
%UBR7200-4-CACHE_ENGINE_WARNING
%UBR10000-4-CACHE_ENGINE_WARNING: Warning: [chars] - [decimal].

Explanation    Cache engine warning message.

Recommended Action    Run the show snmp user command to see cache engine buffer usage and check with SNMP client to figure out what table is being queried. After 5 seconds retry the failed query to see whether it can recover.

%UBR7100-3-CHASSIS
%UBR7200-3-CHASSIS
%UBR10000-3-CHASSIS: Unknown chassis model.

Explanation    Data stored in the midplane is defective or incomplete.

Recommended Action    Contact your Cisco technical support representative to update your system.

%UBR7100-5-CLASSFAIL
%UBR7200-5-CLASSFAIL
%UBR10000-5-CLASSFAIL: Registration failed for Cable Modem [enet] on interface [chars][chars]: [chars]

Explanation    The registration of the specified modem has failed because the specified reason. Common reasons for seeing this error message would be an invalid or unsupported class of service (CoS) setting, or the upstream port would be oversubscribed if this modem came online.

Recommended Action    If the reason given for the failure indicates an invalid CoS setting, ensure that the CoS fields in the modem's DOCSIS configuration file are set correctly. If the problem is that the upstream is oversubscribed, look at how the cable upstream admission-control command has been configured for the upstream, and change the configuration if needed. If the problem persists, check for a possible theft-of-service attack.

%UBR7100-5-CLEAR_ARP_INTERFACE
%UBR7200-5-CLEAR_ARP_INTERFACE
%UBR10000-5-CLEAR_ARP_INTERFACE: Clearing all ARP entries for interface [chars]

Explanation    All the ARP entries have been cleared for the interface.

Recommended Action    No action is needed.

%UBR7100-5-CLEAR_ARP_TABLE
%UBR7200-5-CLEAR_ARP_TABLE
%UBR10000-5-CLEAR_ARP_TABLE: Clearing all ARP entries

Explanation    All the ARP entries have been cleared.

Recommended Action    No action is needed.

%UBR7100-4-CLK_HWFAULT
%UBR7200-4-CLK_HWFAULT
%UBR10000-4-CLK_HWFAULT: Hardware Fault in Clock card

Explanation    A hardware fault is detected in the clock card.

Recommended Action    Replace the clock card.

%UBR7100-5-CLONED_CM_DETECTED
%UBR7200-5-CLONED_CM_DETECTED
%UBR10000-5-CLONED_CM_DETECTED:Cloned CM with MAC address [enet] connection attempt rejected on [chars] U[decimal]

Explanation    A hacking attempt might have occurred.

Recommended Action    Look for possible hacking attempt.

%UBR7100-3-CM_CERTIFICATE_ERROR 
%UBR7200-3-CM_CERTIFICATE_ERROR
%UBR10000-3-CM_CERTIFICATE_ERROR: <132>CMTS[DOCSIS]:<66030111> CM Certificate Error. CM Mac Addr <[enet]>

Explanation    The specified cable modem presented an invalid BPI+ CM certificate during registration.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software and contains valid X.509 digital certificates. If the problem persists, use the show interface cable key sid and show interface cable key mac commands to collect information about the cable modem with the problem. You can also turn on BPI+ debugging using the debug cable privacy and debug cable bpi commands.

%UBR7100-3-CM_CERTIFICATE_FORMAT_ERROR 
%UBR7200-3-CM_CERTIFICATE_FORMAT_ERROR
%UBR10000-3-CM_CERTIFICATE_FORMAT_ERROR: <133>CMTS[DOCSIS]: CM Certificate Format Error

Explanation    The specified cable modem presented an invalid BPI+ CM certificate during registration. The format of the certificate does not match that specified in the BPI+ specification.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software and contains valid X.509 digital certificates. If the problem persists, use the show interface cable key sid and show interface cable key mac commands to collect information about the cable modem with the problem. You can also turn on BPI+ debugging using the debug cable privacy and debug cable bpi commands.

%UBR7100-3-CM_CERTIFICATE_SELF_VERFICATION_ERROR 
%UBR7200-3-CM_CERTIFICATE_SELF_VERFICATION_ERROR
%UBR10000-3-CM_CERTIFICATE_SELF_VERFICATION_ERROR: <133>CMTS[DOCSIS]:<0> CM Certificate Self-Verification Error

Explanation    The specified cable modem presented an invalid BPI+ CM certificate during registration. The certificate cannot be successfully verified.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software and contains valid X.509 digital certificates. If the problem persists, use the show interface cable key sid and show interface cable key mac commands to collect information about the cable modem with the problem. You can also turn on BPI+ debugging using the debug cable privacy and debug cable bpi commands.

%UBR7100-3-CM_INCONST
%UBR7200-3-CM_INCONST
%UBR10000-3-CM_INCONST: CM state inconsistency [enet] (msgp [enet]) with sid [dec] ([dec]) on hwidb [chars]

Explanation    The CMTS received an initialization request for a cable modem that is already online. Typically, this means that the cable interface card and PRE module have different MAC-layer states for this particular cable modem, probably because of interprocess communication (IPC) messages that were lost during an HCCP redundancy switchover from one cable interface card to another. If you are also seeing %UBR10K-3-QUEUEFULL error messages, this means that the management queue on the CMTS became full and some messages were dropped, and the CMTS could have missed the messages informing it that one or more CMs changed state or went offline.

Recommended Action    No action is needed because the CMTS will synchronize its internal databases by marking the cable modem offline, and then the cable modem will automatically re-register after a short time-out period. If the problem repeats, 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.

%UBR7100-4-CMLOCKED
%UBR7200-4-CMLOCKED
%UBR10000-4-CMLOCKED: Cable Modem [enet] in [char] attempted theft of service

Explanation    The cable modem's DOCSIS configuration file did not contain a Message Integrity Check (MIC) value that corresponds with the proper dynamic shared secret that was used to encode it. The CMTS has therefore assigned a restrictive quality of service (QoS) configuration to this cable modem to limit its access to the network. The CMTS has also locked the cable modem, so that the modem must be offline for 24 hours before it will be permitted reregister and obtain normal service (assuming it is DOCSIS-compliant and using a valid DOCSIS configuration file).

Recommended Action    This error message appears when the cable dynamic-secret lock command has been applied to a cable interface to enable the dynamic shared secret feature for the DOCSIS configuration files on that cable interface. The cable modem has been allowed to register and come online, but with a QoS configuration that is limited to a maximum rate of 10 kbps for both the upstream and downstream flows. Check to ensure that this cable modem is not running old software that caches the previously-used configuration file. Also check for a possible theft-of-service attempt by a user attempting to download a modified DOCSIS configuration file from a local TFTP server. The CM cannot reregister until it has been offline, without attempting to register, for 24 hours, or you have manually cleared the lock using the clear cable modem lock command.

%UBR7100-4-CMMARKED
%UBR7200-4-CMMARKED
%UBR10000-4-CMMARKED: Cable Modem [enet] in [chars] attempted theft of service

Explanation    The cable modem's DOCSIS configuration file did not contain a Message Integrity Check (MIC) value that corresponds with the proper dynamic shared secret that was used to encode it. The CMTS has allowed this modem to register and come online, but has marked it in the show cable modem displays with an exclamation point (!) so that the situation can be investigated.

Recommended Action    This error message appears when the cable dynamic-secret mark command has been applied to a cable interface to enable the dynamic shared secret feature for the DOCSIS configuration files on that cable interface. Check to ensure that this cable modem is not running old software that caches the previously-used configuration file. Also check for a possible theft-of-service attempt by a user attempting to download a modified DOCSIS configuration file from a local TFTP server.

%UBR7100-6-CMMOVED
%UBR7200-6-CMMOVED
%UBR10000-6-CMMOVED: Cable modem [enet] has been moved from interface [chars] to interface [chars].

Explanation    The cable modem has been detected ranging on a new interface, indicating that it has been moved from one interface to the new interface.

Recommended Action    No action is needed.

%UBR7100-4-CMNOPRIMSF 
%UBR7200-4-CMNOPRIMSF
%UBR10000-4-CMNOPRIMSF: CM [enet] does not have any primary service flows

Explanation    This cable modem has no primary service flows, which will prevent it from communicating on the cable network.

Recommended Action    No action is needed if the cable modem continues the registration process and successfully registers. Otherwise, reboot the cable modem. If the problem persists, verify that the DOCSIS configuration file being used by the cable modem is valid. If necessary, replace the cable modem with a known working cable modem.

%UBR7100-6-CM_OFFLINE_WITH_L2VPN_NOT_ENABLE 
%UBR7200-6-CM_OFFLINE_WITH_L2VPN_NOT_ENABLE
%UBR10000-6-CM_OFFLINE_WITH_L2VPN_NOT_ENABLE: DOCSIS L2VPN not enabled, sending CM [enet] offline

Explanation    The cable modem is configured with L2VPN, but the CMTS L2VPN is not enabled. The CMTS is sending an offline message to CM.

Recommended Action    Configure the CMTS L2VPN using the cable l2-vpn-service default-nsi command.

%UBR7100-6-CM_OFFLINE_WITH_LEGACY_TLS_CONFIGURED 
%UBR7200-6-CM_OFFLINE_WITH_LEGACY_TLS_CONFIGURED
%UBR10000-6-CM_OFFLINE_WITH_LEGACY_TLS_CONFIGURED: Already configured for legacy TLS, sending CM [enet] offline.

Explanation    The system is sending offline messages to CM because the legacy TLS is already configured.

Recommended Action    Check CMTS configuration for the legacy TLS that has already been configured with the cable modem.

%UBR7100-6-CM_OFFLINE_WITH_NO_FREE_VPNID 
%UBR7200-6-CM_OFFLINE_WITH_NO_FREE_VPNID
%UBR10000-6-CM_OFFLINE_WITH_NO_FREE_VPNID: No free VPNIDs remaining, sending CM [enet] offline.

Explanation    New VPNIDs are not available for allocation as the total number of VPNIDs has reached its limit in the CMTS. The CMTS is sending an offline message to CM.

Recommended Action    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.

%UBR7100-6-CM_OFFLINE_WITH_VLANID_USED 
%UBR7200-6-CM_OFFLINE_WITH_VLANID_USED
%UBR10000-6-CM_OFFLINE_WITH_VLANID_USED: VLANID [integer] on [chars] in use, sending CM [enet] offline.

Explanation    This VLANID is already being used in the system. The CMTS is sending an offline message to CM.

Recommended Action    Check the L2VPN VLANID specified in the CM configuration file.

%UBR7200-4-CM_SF_DSID_INCONSISTENT: DSID [decimal] assigned to SF:[decimal] 
already. DSID invalid on CM-[enet]

Explanation    The Downstream Service Identifier (DSID) assigned to the Service Flow (SF) is not valid any longer.

Recommended Action    Copy the error message exactly as it appears and report it to your technical services representative.

%UBR7100-4-CMTS_OIR_INACTIVE_WITHOUT_L2VPN_UNCONFIGURED 
%UBR7200-4-CMTS_OIR_INACTIVE_WITHOUT_L2VPN_UNCONFIGURED
%UBR10000-4-CMTS_OIR_INACTIVE_WITHOUT_L2VPN_UNCONFIGURED: Card on [decimal]/[decimal] with l2vpn \[chars]\ command should be taken care of before plugging a different type of card or executing \no card\ command.

Explanation    A line card is configured with L2VPN before the online insertion and removal (OIR) operation.

Recommended Action    Remove the L2VPN setup using the DOCSIS configuration file.

%UBR10K-3-CNNR_DSYNC: Dynamic sync failed for [chars]:U[dec] connector mapping, 
expect:[dec] current:[dec] cause:[chars] 

Explanation    URM failed to synchronize connector-receiver mapping from active route processor (RP) to standby RP.

Recommended Action    Clear and re-configure the connector command for the affected upstream mac domain or reload the standby RP.

%UBR7100-3-CONFIG
%UBR7200-3-CONFIG
%UBR10000-3-CONFIG: Exceeds [dec] [chars]

Explanation    The total bandwidth of fast and medium bandwidth port adapters exceeds the rated capacity of this system.

Recommended Action    Refer to the configuration guidelines for the maximum allowed high and medium bandwidth port adapters for the system.

%UBR7100-6-CONFIG_EXIT
%UBR7200-6-CONFIG_EXIT
%UBR10000-6-CONFIG_EXIT: Exiting config mode by [chars] since Port Adapter in slot [dec] removed

Explanation    The user was using CLI commands to configure a port adapter card or cable interface line card, at the same time that the card was removed from the system. This message could also appear if the user was configuring a Broadband Processing Engine, such as the Cisco uBR-MC28U/X, at the same time that the card was reset. Because the configuration was interrupted and the card no longer exists in the system, the Cisco IOS software terminated the configuration mode.

Recommended Action    Reinsert the port adapter card or cable interface line card, and reenter the configuration commands.

%UBR7100-4-COOKIE
%UBR7200-4-COOKIE
%UBR10000-4-COOKIE: Corrupt or missing MAC address cookie using random base [enet]

Explanation    Data stored in the midplane is defective.

Recommended Action    Contact your Cisco technical support representative to update your system.

%UBR7100-4-COS_INVALID_ID_OUT_OF_RANGE 
%UBR7200-4-COS_INVALID_ID_OUT_OF_RANGE
%UBR10000-4-COS_INVALID_ID_OUT_OF_RANGE: <133>CMTS[DOCSIS]:<73011100> Bad Class of Service. Invalid Class ID or out of range. CM Mac Addr <[enet]>

Explanation    The specified cable modem requested a class of service (CoS) that either does not exist or the Class ID is outside of the valid range of 1 through 16.

Recommended Action    Verify that the DOCSIS configuration file being used by the cable modem contains valid CoS information.

%UBR7100-4-COS_UNSUPPORTED_CLASS 
%UBR7200-4-COS_UNSUPPORTED_CLASS
%UBR10000-4-COS_UNSUPPORTED_CLASS: <133>CMTS[DOCSIS]:<7301100> Bad Class of Service- Unsupported class. CM Mac Addr <[enet]>

Explanation    The specified cable modem could not register because it requested an unsupported class of service (CoS).

Recommended Action    Verify that the DOCSIS configuration file being used by the cable modem contains valid CoS information.

%UBR7100-0-CPUCARD
%UBR7200-0-CPUCARD
%UBR10000-0-CPUCARD: CMTS([dec]/[dec]), Init failed, CSR[dec]=[hex].

Explanation    A hardware failure involving the line card has occurred.

Recommended Action    Replace the defective line card.

%UBR7200-3-DBDSPDEAD
%UBR10000-3-DBDSPDEAD: AWACS Slot [dec] is dead

Explanation    The digital signal processor (DSP) on the daughter card of the Cisco uBR-MC16S cable interface line card has paused or stopped.

Recommended Action    Reload the image. If this message recurs, replace the defective daughter card.

%UBR7200-6-DBDSPDOWNLOADDONE
%UBR10000-6-DBDSPDOWNLOADDONE: Downloading dsp code completed

Explanation    The downloading of the digital signal processor (DSP) code on the daughter card of the Cisco uBR-MC16S cable interface line card has been completed.

Recommended Action    No action is needed.

%UBR7200-3-DBDSPDOWNLOADERR1
%UBR10000-3-DBDSPDOWNLOADERR1: DSP FAILED TO RESPOND TO INIT_DOWNLOAD CMD.

Explanation    The download to the digital signal processor (DSP) daughter card on the Cisco uBR-MC16S cable interface line card has failed to initiate.

Recommended Action    Reload the image. If this message recurs, replace the defective daughter card.

%UBR7200-3-DBDSPDOWNLOADERR2
%UBR10000-3-DBDSPDOWNLOADERR2: Failed downloading.

Explanation    The download to the digital signal processor (DSP) daughter card on the Cisco uBR-MC16S cable interface line card has failed. Possible causes are corrupted data or a time-out during the download.

Recommended Action    Reload the image. If this message recurs, replace the defective daughter card.

%UBR7200-3-DBDSPDOWNLOADERR3
%UBR10000-3-DBDSPDOWNLOADERR3: FAILED DOWNLOADING OF DSP FW DUE TO CHECKSUM FAILURE.

Explanation    The last step of the digital signal processor (DSP) download on the daughter card of the Cisco uBR-MC16S cable interface line card has failed because the checksum of the downloaded code does not match the proper value.

Recommended Action    Reload the image. If this message recurs, replace the defective daughter card.

%UBR7200-3-DBDSPDOWNLOADPASS1
%UBR10000-3-DBDSPDOWNLOADPASS1: INIT DOWNLOAD OF DSP F/W PASS.

Explanation    The digital signal processor (DSP) code has successfully started to download to the daughter card on the Cisco uBR-MC16S cable interface line card.

Recommended Action    No action is needed.

%UBR7200-3-DBDSPDOWNLOADPASS2
%UBR10000-3-DBDSPDOWNLOADPASS2: DOWNLOAD OF DSP F/W SUCCESS.

Explanation    The digital signal processor (DSP) code was successfully downloaded to the daughter card on the Cisco uBR-MC16S cable interface line card.

Recommended Action    No action is needed.

%UBR7200-3-DBDSPDOWNLOADPASS3
%UBR10000-3-DBDSPDOWNLOADPASS3: END DOWNLOAD OF DSP F/W SUCCESS.

Explanation    The daughter card on the Cisco uBR-MC16S cable interface line card verified the checksum on the digital signal processor (DSP) code that was downloaded to it and has begun initializing itself with the new code.

Recommended Action    No action is needed.

%UBR7200-6-DBDSPDOWNLOADSTART
%UBR10000-6-DBDSPDOWNLOADSTART: Downloading dsp code initiated

Explanation    The digital signal processor (DSP) code has started to download on the daughter card on the Cisco uBR-MC16S cable interface line card.

Recommended Action    No action is needed.

%UBR7200-3-DBDSPERR1
%UBR10000-3-DBDSPERR1: DSP SRAM failed

Explanation    The daughter card on the Cisco uBR-MC16S cable interface line card has failed because of memory problems.

Recommended Action    Replace the defective daughter card.

%UBR7200-3-DBDSPERR2
%UBR10000-3-DBDSPERR2: DSP SRAM semaphore failed

Explanation    A hardware failure involving the daughter card on the Cisco uBR-MC16S cable interface line card has occurred.

Recommended Action    Replace the defective daughter card.

%UBR7200-3-DBDSPERR3
%UBR10000-3-DBDSPERR3: DSP side dual-port SRAM failed

Explanation    A hardware failure involving the daughter card on the Cisco uBR-MC16S cable interface line card has occurred.

Recommended Action    Replace the defective daughter card.

%UBR7200-3-DBDSPERR4
%UBR10000-3-DBDSPERR4: DSP FLASH memory failed

Explanation    A hardware failure involving the daughter card on the Cisco uBR-MC16S cable interface line card has occurred.

Recommended Action    Replace the defective daughter card.

%UBR7200-3-DBDSPERR5
%UBR10000-3-DBDSPERR5: DSP failed to respond to Host Handshake

Explanation    The digital signal processor (DSP) on the daughter card on the Cisco uBR-MC16S cable interface line card successfully initialized, but a hardware failure occurred during the initialization routines with the main card.

Recommended Action    Replace the defective daughter card.

%UBR7200-3-DBDSPERR6
%UBR10000-3-DBDSPERR6: Switching to backup dsp image failed

Explanation    A hardware failure involving the daughter card on the Cisco uBR-MC16S cable interface line card has occurred.

Recommended Action    Replace the defective daughter card.

%UBR7200-3-DBDSPERR7
%UBR10000-3-DBDSPERR7: Switching again to regular dsp image failed

Explanation    A hardware failure has corrupted the digital signal processor (DSP) code on the daughter card on the Cisco uBR-MC16S cable interface line card.

Recommended Action    Reboot the Cisco uBR-MC16S cable interface line card. If the problem persists, replace the defective daughter card.

%UBR7200-3-DBDSPIDERR
%UBR10000-3-DBDSPIDERR: DSP id read [hex],expect [hex]

Explanation    A hardware failure involving the daughter card on the Cisco uBR-MC16S cable interface line card has occurred.

Recommended Action    Replace the defective daughter card.

%UBR7200-5-DBDSPRECOVER1
%UBR10000-5-DBDSPRECOVER1: Trying to switch to backup dsp image

Explanation    The cable line card is attempting to recover the digital signal processor (DSP) by using the backup image.

Recommended Action    No action is needed.

%UBR7200-5-DBDSPRECOVER2
%UBR10000-5-DBDSPRECOVER2: Switching to backup dsp image succeeded

Explanation    The cable modem has successfully switched to the backup digital signal processor (DSP) image.

Recommended Action    No action is needed.

%UBR7200-5-DBDSPRECOVER3
%UBR10000-5-DBDSPRECOVER3: Recovering and switching back to regular dsp image succeeded

Explanation    The digital signal processor (DSP) recovery using the backup image has succeeded. The Cisco uBR-MC16S cable interface line card is now using the regular DSP image.

Recommended Action    No action is needed.

%UBR7200-5-DBDSPUP
%UBR10000-5-DBDSPUP: Handshake DSP is successful after [dec] ms delay

Explanation    The digital signal processor (DSP) on the Cisco uBR-MC16S cable interface line card is up and running.

Recommended Action    No action is needed.

%UBR7200-6-DBDSPVERSION
%UBR10000-6-DBDSPVERSION: Current DSP version: [dec], DSP flash version: [dec]

Explanation    This message displays the current code version and the version with which the digital signal processor (DSP) used to boot up (Flash version).

Recommended Action    No action is needed.

%UBR7100-3-DBFPGADLERR
%UBR7200-3-DBFPGADLERR
%UBR10000-3-DBFPGADLERR: [chars]

Explanation    The specific download error occurred on the XILINK FPGA gate array. This could indicate a transmission error occurred, or it could indicate a hardware fault.

Recommended Action    Reload the software image. If the failure continues, replace the defective line card.

%UBR7100-3-DBFPGAERR
%UBR7200-3-DBFPGAERR
%UBR10000-3-DBFPGAERR: XILINX not up, reset reg is [hex]

Explanation    A hardware failure involving the daughter card has occurred.

Recommended Action    Replace the defective daughter card.

%UBR7100-3-DBPLX9050ERR
%UBR7200-3-DBPLX9050ERR
%UBR10000-3-DBPLX9050ERR: Plx9050 id read [hex],expect [hex]

Explanation    A hardware failure involving the daughter card has occurred.

Recommended Action    Replace the defective daughter card.

%UBR7100-3-DBPLX9080ERR
%UBR7200-3-DBPLX9080ERR
%UBR10000-3-DBPLX9080ERR: Plx9080 id read [hex],expect [hex]

Explanation    A hardware failure involving the daughter card has occurred.

Recommended Action    Replace the defective daughter card.

%UBR7100-4-DCC_ACK_NOT_RECV 
%UBR7200-4-DCC_ACK_NOT_RECV
%UBR10000-4-DCC_ACK_NOT_RECV: <133>CMTS[DOCSIS]:<67040100> DCC-ACK not received

Explanation    The CM reports that it did not receive a Dynamic Channel Change acknowledge (DCC-ACK) message from the CMTS, which should have sent it to acknowledge the cable modem's DCC response (DCC-RSP) message.

Recommended Action    No action is needed. If this problem persists with a single cable modem, verify that this cable modem is DOCSIS 1.1-compliant. If this problem persists with multiple cable modems, the DCC_ACK messages might be getting lost due to noise or other RF plant issues.

%UBR7100-4-DCC_ACK_REJ_AUTHENTICATION_FAILURE 
%UBR7200-4-DCC_ACK_REJ_AUTHENTICATION_FAILURE
%UBR10000-4-DCC_ACK_REJ_AUTHENTICATION_FAILURE: <133>CMTS[DOCSIS]:<67040400> DCC-ACK rejected authentication failure

Explanation    The CMTS sent a Dynamic Channel Change acknowledge (DCC-ACK) message to the cable modem, which rejected it with a confirmation code of reject-authentication-failure(11) because the message contained an invalid HMAC-digest or Message Integrity Check (MIC) value.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS.

%UBR7100-4-DCC_ACK_REJ_MSG_SYNTAX_ERROR
%UBR7200-4-DCC_ACK_REJ_MSG_SYNTAX_ERROR
%UBR10000-4-DCC_ACK_REJ_MSG_SYNTAX_ERROR: <133>CMTS[DOCSIS]:<67040500> DCC-ACK rejected message syntax error

Explanation    The CMTS sent a Dynamic Channel Change acknowledge (DCC-ACK) message to the cable modem, which rejected it with a confirmation code of reject-message-syntax-error(204) because its format does not conform to the DOCSIS 1.1 specification. A common error is that a TLV in the message has the wrong length.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that you are running released software on the CMTS.

%UBR7100-4-DCC_ACK_REJ_UNKNOWN_TRANSACTION_ID 
%UBR7200-4-DCC_ACK_REJ_UNKNOWN_TRANSACTION_ID
%UBR10000-4-DCC_ACK_REJ_UNKNOWN_TRANSACTION_ID: <133>CMTS[DOCSIS]:<67040300> DCC-ACK rejected unknown transaction ID

Explanation    The CMTS sent a Dynamic Channel Change acknowledge (DCC-ACK) message to the cable modem, which rejected it with a confirmation code of reject-unknown-transaction-id(10) because the cable modem did not recognize its Transaction ID as belonging to a transaction currently being processed.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS.

%UBR7100-4-DCC_ACK_REJ_UNSPECIFIED_REASON 
%UBR7200-4-DCC_ACK_REJ_UNSPECIFIED_REASON
%UBR10000-4-DCC_ACK_REJ_UNSPECIFIED_REASON: <133>CMTS[DOCSIS]:<67040200> DCC-ACK rejected unspecified reason

Explanation    The CMTS sent a Dynamic Channel Change acknowledge (DCC-ACK) to the cable modem, which rejected it with a confirmation code of reject-other(1) because of an error that does not match any of the other confirmation codes.

Recommended Action    No action is needed. If the problem persists, verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software.

%UBR7100-4-DCC_NO_RESOURCE_ON_TARGET 
%UBR7200-4-DCC_NO_RESOURCE_ON_TARGET
%UBR10000-4-DCC_NO_RESOURCE_ON_TARGET: DCC [enet] aborted. No resource available on target [chars] U[decimal]

Explanation    No resource is available on the target channel for the dynamic channel change (DCC) transaction.

Recommended Action    Check target channel utilization.

%UBR10000-4-DCC_REJ_20_DISABLE: <133>CMTS[DOCSIS]:<67021900> DCC rejected 2.0 
mode disabled.

Explanation    The Dynamic Channel Change request (DCC-REQ) is rejected because the DOCSIS 2.0 mode has been disabled.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%UBR7100-4-DCC_REJ_AUTHENTICATION_FAILURE 
%UBR7200-4-DCC_REJ_AUTHENTICATION_FAILURE
%UBR10000-4-DCC_REJ_AUTHENTICATION_FAILURE: <133>CMTS[DOCSIS]:<67021100> DCC rejected authentication failure

Explanation    The Dynamic Channel Change request (DCC-REQ) has been rejected with a confirmation code of reject-authentication-failure(11) because the message contained an invalid HMAC-digest or Message Integrity Check (MIC) value.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS.

%UBR7100-4-DCC_REJ_CLASSIFIER_NOT_FOUND 
%UBR7200-4-DCC_REJ_CLASSIFIER_NOT_FOUND
%UBR10000-4-DCC_REJ_CLASSIFIER_NOT_FOUND: <133>CMTS[DOCSIS]:<67021300> DCC rejected classifier not found

Explanation    The Dynamic Channel Change request (DCC-REQ) has been rejected with a confirmation code of reject-classifier-not-found(14) because the requested packet classifier ID is invalid or does not exist.

Recommended Action    Reissue the command with a valid packet classifier ID. Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS.

%UBR7100-4-DCC_REJ_DUPLICATE_REF_ID_INDEX 
%UBR7200-4-DCC_REJ_DUPLICATE_REF_ID_INDEX
%UBR10000-4-DCC_REJ_DUPLICATE_REF_ID_INDEX: <133>CMTS[DOCSIS]:<67021500> DCC rejected duplicate DCC Request reference-ID or index in message

Explanation    The Dynamic Channel Change request (DCC-REQ) was rejected with a confirmation code of reject-duplicate-reference-ID-or-index-in-message(18) because the message used a service flow reference, classifier reference, service flow ID (SFID), or classifier ID twice in an illegal way.

Recommended Action    Reissue the command with a valid service flow. Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS.

%UBR7100-4-DCC_REJ_MSG_SYNTAX_ERROR 
%UBR7200-4-DCC_REJ_MSG_SYNTAX_ERROR
%UBR10000-4-DCC_REJ_MSG_SYNTAX_ERROR: <133>CMTS[DOCSIS]:<67021700> DCC rejected message syntax error

Explanation    The Dynamic Channel Change request (DCC-REQ) was rejected with a confirmation code of reject-message-syntax-error(204) because its format does not conform to the DOCSIS 1.1 specification. A common error is that a TLV in the message has the wrong length.

Recommended Action    Reissue the command with a valid DCC-REQ message. Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that you are running released software on the CMTS.

%UBR7100-4-DCC_REJ_MSG_TOO_BIG 
%UBR7200-4-DCC_REJ_MSG_TOO_BIG
%UBR10000-4-DCC_REJ_MSG_TOO_BIG: <133>CMTS[DOCSIS]:<67021800> DCC rejected message too big

Explanation    The Dynamic Channel Change request (DCC-REQ) was rejected with a confirmation code of reject-message-too-big(206) because the message needed to respond to the request would exceed the maximum allowable length.

Recommended Action    Reissue the command with a valid DCC-REQ message. Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS.

%UBR7100-4-DCC_REJ_MULTIPLE_ERRORS 
%UBR7200-4-DCC_REJ_MULTIPLE_ERRORS
%UBR10000-4-DCC_REJ_MULTIPLE_ERRORS: <133>CMTS[DOCSIS]:<67021200> DCC rejected multiple errors

Explanation    The Dynamic Channel Change request (DCC-REQ) was rejected with a confirmation code of reject-multiple-errors(13) because the request message had multiple errors in it.

Recommended Action    Reissue the command with a valid DCC-REQ message. Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS.

%UBR7100-4-DCC_REJ_PARAMETER_INVALID_CONTEXT 
%UBR7200-4-DCC_REJ_PARAMETER_INVALID_CONTEXT
%UBR10000-4-DCC_REJ_PARAMETER_INVALID_CONTEXT: <133>CMTS[DOCSIS]:<67021600> DCC rejected parameter invalid for context

Explanation    The Dynamic Channel Change request (DCC-REQ) was rejected with a confirmation code of reject-parameter-invalid-for-context(23) because the message contained at least one parameter that was invalid for the TLV in which it was used.

Recommended Action    Reissue the command with a valid DCC-REQ message. Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS.

%UBR7100-4-DCC_REJ_PERMANENT_DCC_NOT_SUPPORTED 
%UBR7200-4-DCC_REJ_PERMANENT_DCC_NOT_SUPPORTED
%UBR10000-4-DCC_REJ_PERMANENT_DCC_NOT_SUPPORTED: <133>CMTS[DOCSIS]:<67020800> DCC rejected permanent - DCC not supported

Explanation    The cable modem has permanently rejected the Dynamic Channel Change request (DCC-REQ) with a confirmation code of reject-permanent/reject-admin(4) because it does not support dynamic channel changes.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. If this cable modem is running DOCSIS 1.1 software, verify that its DCC Support parameter is set to 1 to enable the DCC feature.

%UBR7100-4-DCC_REJ_PHS_RULE_NOT_FOUND 
%UBR7200-4-DCC_REJ_PHS_RULE_NOT_FOUND
%UBR10000-4-DCC_REJ_PHS_RULE_NOT_FOUND: <133>CMTS[DOCSIS]:<67021400> DCC rejected PHS rule not found

Explanation    The Dynamic Channel Change request (DCC-REQ) was rejected with a confirmation code of reject-PHS-rule-not-found(16) because the message specified a service flow ID and classifier ID combination for which no PHS rule exists.

Recommended Action    Reissue the command with valid parameters. Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS.

%UBR7100-4-DCC_REJ_REQUIRED_PARAMETER_NOT_PRESENT 
%UBR7200-4-DCC_REJ_REQUIRED_PARAMETER_NOT_PRESENT
%UBR10000-4-DCC_REJ_REQUIRED_PARAMETER_NOT_PRESENT: <133>CMTS[DOCSIS]:<67021000> DCC rejected required parameter not present

Explanation    The Dynamic Channel Change request (DCC-REQ) was rejected with a confirmation code of reject-required-parameter-not-present(8) because at least one required parameter was not present in the message.

Recommended Action    Reissue the command with all required parameters. In particular, if BPI+ is being used, specify a proper key sequence number and HMAC-digest value. Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS.

%UBR7100-4-DCC_REJ_SRV_FLOW_NOT_FOUND 
%UBR7200-4-DCC_REJ_SRV_FLOW_NOT_FOUND
%UBR10000-4-DCC_REJ_SRV_FLOW_NOT_FOUND: <133>CMTS[DOCSIS]:<67020900> DCC rejected service flow not found

Explanation    The Dynamic Channel Change request (DCC-REQ) was rejected with a confirmation code of reject-service-flow-not-found(6) because the requested service flow does not exist.

Recommended Action    Reissue the command with a valid service flow. Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS.

%UBR7100-4-DCC_REJ_UNSPECIFIED_REASON 
%UBR7200-4-DCC_REJ_UNSPECIFIED_REASON
%UBR10000-4-DCC_REJ_UNSPECIFIED_REASON: <133>CMTS[DOCSIS]:<67020700> DCC rejected unspecified reason

Explanation    The Dynamic Channel Change request (DCC-REQ) was rejected with a confirmation code of reject-other(1) because of an error that does not match any of the other confirmation codes.

Recommended Action    No action is needed. If the problem persists, verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software.

%UBR7100-4-DCC_REQ_ABORT_NO_ACQ_NEW_DWSTREAM_CHANNEL 
%UBR7200-4-DCC_REQ_ABORT_NO_ACQ_NEW_DWSTREAM_CHANNEL
%UBR10000-4-DCC_REQ_ABORT_NO_ACQ_NEW_DWSTREAM_CHANNEL: <133>CMTS[DOCSIS]:<67020400> DCC aborted unable to acquire new downstream channel

Explanation    The cable modem has aborted the Dynamic Channel Change request (DCC-REQ) because it could not range on the new downstream channel that was specified in the DCC-REQ message. The cable modem will return to its original downstream channel.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS. Investigate the downstream for possible noise ingress or other RF plant problems.

%UBR7100-4-DCC_REQ_ABORT_NO_COMM_NEW_UPSTREAM_CHANNEL 
%UBR7200-4-DCC_REQ_ABORT_NO_COMM_NEW_UPSTREAM_CHANNEL
%UBR10000-4-DCC_REQ_ABORT_NO_COMM_NEW_UPSTREAM_CHANNEL: <133>CMTS[DOCSIS]:<67020600> DCC aborted unable to communicate on new upstream channel

Explanation    The cable modem has aborted the Dynamic Channel Change request (DCC-REQ) because it could not acquire the new upstream channel that was specified in the DCC-REQ message. The cable modem returns to its original upstream channel.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS. Investigate for possible noise ingress or other RF plant problems.

%UBR7100-4-DCC_REQ_ABORT_NO_UCD_NEW_UPSTREAM_CHANNEL 
%UBR7200-4-DCC_REQ_ABORT_NO_UCD_NEW_UPSTREAM_CHANNEL
%UBR10000-4-DCC_REQ_ABORT_NO_UCD_NEW_UPSTREAM_CHANNEL: <133>CMTS[DOCSIS]:<67020500> DCC aborted no UCD for new upstream channel

Explanation    The Dynamic Channel Change request (DCC-REQ) was cancelled because no Upstream Channel Descriptor (UCD) was supplied for a new upstream channel.

Recommended Action    Reissue the command with a valid UCD or without specifying an upstream channel change. Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS.

%UBR7100-4-DCC_REQ_ARRIVE_NEW 
%UBR7200-4-DCC_REQ_ARRIVE_NEW
%UBR10000-4-DCC_REQ_ARRIVE_NEW: <133>CMTS[DOCSIS]:<67020300> DCC arrive new

Explanation    The Dynamic Channel Change request (DCC-REQ) has been logged with a confirmation code of arrive(181) to indicate that the cable modem has performed the channel change and has arrived at the new channel.

Recommended Action    No action is needed.

%UBR7100-4-DCC_REQ_DEPART_OLD 
%UBR7200-4-DCC_REQ_DEPART_OLD
%UBR10000-4-DCC_REQ_DEPART_OLD: <133>CMTS[DOCSIS]:<67020200> DCC depart old

Explanation    The Dynamic Channel Change request (DCC-REQ) has been logged with a confirmation code of depart(180) to indicate that the cable modem is on the old channel and is about to jump to the new channel.

Recommended Action    No action is needed.

%UBR7100-4-DCC_REQ_REJ_ALREADY 
%UBR7200-4-DCC_REQ_REJ_ALREADY
%UBR10000-4-DCC_REQ_REJ_ALREADY: <133>CMTS[DOCSIS]:<67020100> DCC rejected already there

Explanation    The Dynamic Channel Change request (DCC-REQ) has been rejected with a confirmation code of reject-already-there(182) because the CMTS has asked the cable modem to move to a channel that it is already using.

Recommended Action    No action is needed.

%UBR7100-4-DCC_RSP_NOT_RCV_NEW_CHANNEL 
%UBR7200-4-DCC_RSP_NOT_RCV_NEW_CHANNEL
%UBR10000-4-DCC_RSP_NOT_RCV_NEW_CHANNEL: <133>CMTS[DOCSIS]:<67030200> DCC-RSP not received on new channel

Explanation    The CMTS has not received a Dynamic Channel Change response (DCC-RSP) message from the cable modem on the new upstream channel.

Recommended Action    No action is needed if the cable modem was instructed to reinitialize its MAC interface, in which case it will not send a DCC-RSP message. Otherwise, Verify that the cable modem is running DOCSIS 1.1-certified software.

%UBR7100-4-DCC_RSP_NOT_RCV_OLD_CHANNEL 
%UBR7200-4-DCC_RSP_NOT_RCV_OLD_CHANNEL
%UBR10000-4-DCC_RSP_NOT_RCV_OLD_CHANNEL: <133>CMTS[DOCSIS]:<67030100> DCC-RSP not received on old channel

Explanation    The CMTS has not received a Dynamic Channel Change response (DCC-RSP) message from the cable modem on the old upstream channel.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software. Only DOCSIS 1.1 cable modems support DCC messages.

%UBR7100-4-DCC_RSP_REJ_AUTHENTICATION_FAILURE 
%UBR7200-4-DCC_RSP_REJ_AUTHENTICATION_FAILURE
%UBR10000-4-DCC_RSP_REJ_AUTHENTICATION_FAILURE: <133>CMTS[DOCSIS]:<67030500> DCC-RSP rejected authentication failure

Explanation    The CMTS has rejected the Dynamic Channel Change response (DCC-RSP) message with a confirmation code of reject-authentication-failure(11) because the message contained an invalid HMAC-digest or Message Integrity Check (MIC) value.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software. Only DOCSIS 1.1 cable modems support DCC messages.

%UBR7100-4-DCC_RSP_REJ_MSG_SYNTAX_ERROR 
%UBR7200-4-DCC_RSP_REJ_MSG_SYNTAX_ERROR
%UBR10000-4-DCC_RSP_REJ_MSG_SYNTAX_ERROR: <133>CMTS[DOCSIS]:<67030600> DCC-RSP rejected message syntax error

Explanation    The CMTS has rejected the Dynamic Channel Change response (DCC-RSP) message with a confirmation code of reject-message-syntax-error(204) because its format does not conform to the DOCSIS 1.1 specification. A common error is that a TLV in the message has the wrong length.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that you are running released software on the CMTS.

%UBR7100-4-DCC_RSP_REJ_UNKNOWN_TRANSACTION_ID 
%UBR7200-4-DCC_RSP_REJ_UNKNOWN_TRANSACTION_ID
%UBR10000-4-DCC_RSP_REJ_UNKNOWN_TRANSACTION_ID: <133>CMTS[DOCSIS]:<67030400> DCC-RSP rejected unknown transaction ID

Explanation    The CMTS has rejected the Dynamic Channel Change response (DCC-RSP) message sent by the cable modem with a confirmation code of reject-unknown-transaction-id(10) because it did not recognize the Transaction ID as belonging to a transaction currently being processed.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS.

%UBR7100-4-DCC_RSP_REJ_UNSPECIFIED_REASON 
%UBR7200-4-DCC_RSP_REJ_UNSPECIFIED_REASON
%UBR10000-4-DCC_RSP_REJ_UNSPECIFIED_REASON: <133>CMTS[DOCSIS]:<67030300> DCC-RSP rejected unspecified reason

Explanation    The CMTS has rejected the Dynamic Channel Change response (DCC-RSP) message sent by the cable modem with a confirmation code of reject-other(1) because of an error that does not match any of the other confirmation codes.

Recommended Action    No action is needed. If the problem persists, verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software.

%UBR7100-6-DDC_CFG_HASHFILTER_REMOVED
%UBR7200-6-DDC_CFG_HASHFILTER_REMOVED
%UBR10000-6-DDC_CFG_HASHFILTER_REMOVED: Hash-filter [dec] not present in global config - Filter removed from [chars]

Explanation    The specified hash filter was removed from the global configuration, and because the associated cable interface line card was not present in the chassis, the hash filter configuration was also removed from that cable interface line card configuration.

Recommended Action    No action is needed.

%UBR7100-4-DDC_CFG_HASHID
%UBR7200-4-DDC_CFG_HASHID
%UBR10000-4-DDC_CFG_HASHID: Hash id [dec] does not exist in global configuration

Explanation    The specified hash ID for the DOCSIS Dual-Channel (DDC) configuration is configured on a cable interface, but it is not configured globally, so that the router cannot map the appropriate OUI or MAC IDs appropriately.

Recommended Action    Configure the hash ID globally, using the cable redundancy hashfilter command in global configuration mode.

%UBR7100-6-DDC_CFG_TARGET_REMOVED
%UBR7200-6-DDC_CFG_TARGET_REMOVED
%UBR10000-6-DDC_CFG_TARGET_REMOVED: Redundancy target invalid - removed from [chars]

Explanation    The router's MY ID configuration was removed from the configuration, but the associated cable interface line card was not present in the chassis, so the associated redundancy configuration is also removed from that card's interface configuration.

Recommended Action    No action is needed.

%UBR7100-4-DDC_GENERAL_ERROR
%UBR7200-4-DDC_GENERAL_ERROR
%UBR10000-4-DDC_GENERAL_ERROR: Error: [chars]

Explanation    The DOCSIS Dual-Channel (DDC) configuration generated the specified error.

Recommended Action    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. Contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR7100-3-DDC_INVALID_HASHTYPE
%UBR7200-3-DDC_INVALID_HASHTYPE
%UBR10000-3-DDC_INVALID_HASHTYPE: The hash type [dec] for hash id [dec] is invalid

Explanation    The specified hash ID in the DOCSIS Dual-Channel (DDC) configuration has an invalid configuration.

Recommended Action    Verify the DDC configuration on the router. If the configuration appears correct, 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. Contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR7100-3-DDC_INVALID_STATICMAP
%UBR7200-3-DDC_INVALID_STATICMAP
%UBR10000-3-DDC_INVALID_STATICMAP: The node [dec] for mac-address [enet] exceeds maximum configured nodes.

Explanation    The configuration for the DOCSIS Dual-Channel (DDC) contains an Organization Unique Identifier (OUI) or MAC address mapping that specifies a DCC node number outside of the valid range (from 1 to 3).

Recommended Action    Check the configuration to verify that all of the appropriate downstreams have been configured for the DDC feature, and that the number of configured downstreams is not outside of the valid range. If the configuration appears correct, 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. Contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR7100-4-DDC_LIST_ERROR
%UBR7200-4-DDC_LIST_ERROR
%UBR10000-4-DDC_LIST_ERROR: DDC list error

Explanation    The DOCSIS Dual-Channel (DDC) software was unable to create a list or add an element to a list. This typically is due to a lack of resources, such as memory, or a failure of the interprocess communication (IPC) subsystem to send the required list control messages.

Recommended Action    Display the current processor usage using the show proc command, and look for any processes that might be monopolizing the processor time. 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.

%UBR7100-4-DDC_MESSAGE_ERROR
%UBR7200-4-DDC_MESSAGE_ERROR
%UBR10000-4-DDC_MESSAGE_ERROR: DDC message error. type [dec]

Explanation    The DOCSIS Dual-Channel (DDC) software was unable to send the specified interprocess communication (IPC) messages. This could be due to a lack of resources, such as memory, or due to the processor being at or near 100 percent utilization.

Recommended Action    Display the current processor usage using the show proc command, and look for any processes that might be monopolizing the processor time. 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.

%UBR7100-4-DDC_NODE_ID_ERROR
%UBR7200-4-DDC_NODE_ID_ERROR
%UBR10000-4-DDC_NODE_ID_ERROR: Node id mismatch NPE: [dec] linecard: [dec]

Explanation    The node ID on the NPE subinterface is different than what is configured on the cable interface line card.

Recommended Action    Verify that the configuration is correct. 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. Contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR7100-4-DDC_PROT_FREQ_ERROR
%UBR7200-4-DDC_PROT_FREQ_ERROR
%UBR10000-4-DDC_PROT_FREQ_ERROR: DS frequency not configured for the protect target node [dec]

Explanation    A downstream frequency is not configured on the specified target node.

Recommended Action    Configure a downstream frequency on the appropriate downstream.

%UBR7100-4-DDC_SEMAPHORE_ERROR
%UBR7200-4-DDC_SEMAPHORE_ERROR
%UBR10000-4-DDC_SEMAPHORE_ERROR: DDC semaphore released when it was not taken

Explanation    A DOCSIS Dual-Channel (DDC) semaphore flag was released, but the flag was not locked at the time. This indicates either that an unexpected situation or that a software error occurred.

Recommended Action    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. Contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR7100-4-DDC_UNEXPECTED_EVENT_ERROR
%UBR7200-4-DDC_UNEXPECTED_EVENT_ERROR
%UBR10000-4-DDC_UNEXPECTED_EVENT_ERROR: DDC unexpected event error [dec]

Explanation    The DOCSIS Dual-Channel (DDC) software encountered an unexpected or unsupported event. This indicates either that an unexpected situation or that a software error occurred.

Recommended Action    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. Contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR7100-4-DDC_UNEXPECTED_MESSAGE_ERROR
%UBR7200-4-DDC_UNEXPECTED_MESSAGE_ERROR
%UBR10000-4-DDC_UNEXPECTED_MESSAGE_ERROR: DDC unexpected message error [dec]

Explanation    The DOCSIS Dual-Channel (DDC) software received an unexpected or unsupported message. This indicates either that an unexpected situation or that a software error occurred.

Recommended Action    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. Contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR7100-3-DDC_UNEXPECTED_NODES
%UBR7200-3-DDC_UNEXPECTED_NODES
%UBR10000-3-DDC_UNEXPECTED_NODES: The number of nodes [dec] is invalid.

Explanation    The configuration for the DOCSIS Dual-Channel (DDC) is outside of the valid range (from 1 to 3).

Recommended Action    Check the configuration to verify that all of the appropriate downstreams have been configured for the DDC feature, and that the number of configured downstreams is not outside of the valid range. If the configuration appears correct, 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. Contact your Cisco technical support representative and provide the representative with the gathered information.

%UBR7100-4-DHCPLQSIDMISMATCH
%UBR7200-4-DHCPLQSIDMISMATCH
%UBR10000-4-DHCPLQSIDMISMATCH: Source Verify of pkt from host [enet] [IP_address] sid [integer] does not match LQ Relay Info from server [IP_address] for CM [enet] sid [integer] on interface [chars]

Explanation    The service identifier (SID) of the packet does not match the SID of MAC address in relay-agent information from the DHCP server.

Recommended Action    Manually verify lease information on the DHCP server against the current SID of the host.

%UBR7100-6-DIFFENCADJUST 
%UBR7200-6-DIFFENCADJUST
%UBR10000-6-DIFFENCADJUST: Differential-encoding is disabled on interface [chars] upstream [dec], it is only supported for QPSK or QAM16.

Explanation    The specified interface has been configured for differential encoding, which is supported only for QPSK and 16-QAM modulations. Because the interface has also been configured for a modulation profile of 8-QAM, 32-QAM, or 64-QAM modulation, the differential encoding has been disabled.

Recommended Action    No action is needed.

%UBR7100-1-DISCOVER
%UBR7200-1-DISCOVER
%UBR10000-1-DISCOVER: Only found [dec] interfaces on bay [dec], shutting down bay

Explanation    A hardware or software error involving the line card has occurred.

Recommended Action    Replace the line card.

%UBR7100-3-DIV_BY_ZERO_ERROR
%UBR7200-3-DIV_BY_ZERO_ERROR
%UBR10000-3-DIV_BY_ZERO_ERROR: Divide by zero attempted error [chars]

Explanation    An internal software error has occurred.

Recommended Action    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.

%UBR7100-3-DOCSIS_SYNC_SF
%UBR7200-3-DOCSIS_SYNC_SF
%UBR10000-3-DOCSIS_SYNC_SF: cminstp is NULL: [chars]

Explanation    No valid cminstp is found for SID referenced in this checkpoint message. The message will be dropped.

Recommended Action    No action is needed.

%UBR7100-4-DOWNSTREAM_FREQUENCY_FORMAT_INVALID 
%UBR7200-4-DOWNSTREAM_FREQUENCY_FORMAT_INVALID
%UBR10000-4-DOWNSTREAM_FREQUENCY_FORMAT_INVALID: <133>CMTS[DOCSIS]:<73010500> Bad DS FREQ - Format Invalid. CM Mac Addr <[enet]>

Explanation    The cable modem sent a registration request message that contained an invalid value for the downstream frequency parameter.

Recommended Action    Check the DOCSIS configuration file that this cable modem is using and correct any errors. Reboot the cable modem. If the problem persists, it could indicate a possible theft-of-service attack by someone using a modified configuration file.

%UBR10000-4-DOWNSTREAM_FREQUENCY_NOT_MULTIPLE_OF_62500: 
<133>CMTS[DOCSIS]:<73010502> Bad DS FREQ - Not multiple of 62500. CM Mac Addr 
[enet]

Explanation    A registration request (REG-REQ) is rejected because the downstream frequency is not a multiple of 62500.

Recommended Action    Check the frequency in the router configuration file.

%UBR7100-6-DRVMP
%UBR7200-6-DRVMP
%UBR10000-6-DRVMP: Midplane TDM clock reference defaults to Clockcard

Explanation    The clock card primary reference is from the midplane TDM clock.

Recommended Action    No action is needed.

%UBR7100-4-DSA_ABORTED_NO_ACK 
%UBR7200-4-DSA_ABORTED_NO_ACK
%UBR10000-4-DSA_ABORTED_NO_ACK: <133>CMTS[DOCSIS]:<83020101> Service Add Aborted - No ACK. CM Mac Addr <[enet]>

Explanation    The Dynamic Service Add request (DSA-REQ) was abandoned because the CMTS did not receive a DSA acknowledgement (DSA-ACK) message from the cable modem after sending a DSA response (DSA-RSP) message.

Recommended Action    No action is needed.

%UBR7100-4-DSA_ACK_REJECTED_INVALID_TRANSACTION_ID 
%UBR7200-4-DSA_ACK_REJECTED_INVALID_TRANSACTION_ID
%UBR10000-4-DSA_ACK_REJECTED_INVALID_TRANSACTION_ID: <133>CMTS[DOCSIS]:<83020100> Service Add Response rejected - Invalid transaction ID. CM Mac Addr <[enet]>");

Explanation    The Dynamic Service Add request (DSA-REQ) was abandoned because the DSA acknowledgement (DSA-ACK) from the indicated cable modem did not contain a transaction ID that matches those for any outstanding DSA requests for this cable modem. The message was rejected with a confirmation code of reject-unknown-transaction-id(10).

Recommended Action    The cable modem should retry the request. If the problem persists, verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software.

%UBR7100-4-DSA_ADD_ABORTED 
%UBR7200-4-DSA_ADD_ABORTED
%UBR10000-4-DSA_ADD_ABORTED: <133>CMTS[DOCSIS]:<83000108> Service Add rejected - Add aborted. CM Mac Addr <[enet]>

Explanation    The Dynamic Service Add request (DSA-REQ) has been rejected with a confirmation code of reject-add-aborted(12) because the initiator of the request has cancelled it.

Recommended Action    No action is needed.

%UBR7100-4-DSA_AUTH_FAILURE 
%UBR7200-4-DSA_AUTH_FAILURE
%UBR10000-4-DSA_AUTH_FAILURE: <133>CMTS[DOCSIS]:<83000120> Service Add rejected - Authorization failure. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-authorization-failure(24) because the request was rejected by the DOCSIS authorization module.

Recommended Action    Verify that the cable modem is properly configured for BPI+ operations.

%UBR7100-4-DSA_CLASSIFIER_ANOTHER_FLOW 
%UBR7200-4-DSA_CLASSIFIER_ANOTHER_FLOW
%UBR10000-4-DSA_CLASSIFIER_ANOTHER_FLOW: <133>CMTS[DOCSIS]:<83000117> Service Add rejected - Classifier for another flow. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-classifier-for-another-service-flow(21) because this packet classifier is already being used for a different service flow than the one specified in the request.

Recommended Action    The cable modem should retry the DSA request.

%UBR7100-4-DSA_CLASSIFIER_EXISTS 
%UBR7200-4-DSA_CLASSIFIER_EXISTS
%UBR10000-4-DSA_CLASSIFIER_EXISTS: <133>CMTS[DOCSIS]:<83000111> Service Add rejected - Classifier exists. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-classifier-exists(15) because the requested packet classifier already exists.

Recommended Action    The cable modem should retry the request.

%UBR7100-4-DSA_CLASSIFIER_NOT_FOUND 
%UBR7200-4-DSA_CLASSIFIER_NOT_FOUND
%UBR10000-4-DSA_CLASSIFIER_NOT_FOUND: <133>CMTS[DOCSIS]:<83000110> Service Add rejected - Classifier not found. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-classifier-not-found(14) because the requested packet classifier ID is invalid or does not exist.

Recommended Action    Reissue the command with a valid packet classifier ID. Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that you are running released software on the CMTS.

%UBR7100-4-DSA_DUPLICATE_REF_ID_INDEX 
%UBR7200-4-DSA_DUPLICATE_REF_ID_INDEX
%UBR10000-4-DSA_DUPLICATE_REF_ID_INDEX: <133>CMTS[DOCSIS]:<83000114> Service Add rejected duplicate reference-ID or index in message. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-duplicate-reference-ID-or-index-in-message(18) because the message used a service flow reference, classifier reference, service flow ID (SFID), or classifier ID twice in an illegal way.

Recommended Action    Reissue the command with single service flow reference, serviceflow ID reference, Classifier reference and Classifier ID reference. Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that you are running released software on the CMTS.

%UBR7100-4-DSA_HEADER_SUPPR_SETTING_NOT_SUPPORTED 
%UBR7200-4-DSA_HEADER_SUPPR_SETTING_NOT_SUPPORTED
%UBR10000-4-DSA_HEADER_SUPPR_SETTING_NOT_SUPPORTED: <133>CMTS[DOCSIS]:<83000105> Service Add rejected - Header suppression setting not supported. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-header-suppression(9) because the requested Packet Header Suppression (PHS) configuration cannot be supported for some reason.

Recommended Action    Verify the PHS rule and reissue the command. Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software.

%UBR7100-4-DSA_HMAC_AUTHENTICATION_FAILURE 
%UBR7200-4-DSA_HMAC_AUTHENTICATION_FAILURE
%UBR10000-4-DSA_HMAC_AUTHENTICATION_FAILURE: <133>CMTS[DOCSIS]:<83000101> Service Add rejected - HMAC Authentication Failure. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-authentication-failure(11) because the message contained an invalid HMAC-digest or Message Integrity Check (MIC) value.

Recommended Action    Verify that the cable modem is properly configured for BPI+ operations.

%UBR7100-4-DSA_MAJOR_CLASSIFIER_ERROR 
%UBR7200-4-DSA_MAJOR_CLASSIFIER_ERROR
%UBR10000-4-DSA_MAJOR_CLASSIFIER_ERROR: <133>CMTS[DOCSIS]:<83000122> Service Add rejected - Major classifier error. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-major-classifier-error(201) because the request either did not have a classifier reference, or because it did not specify both a classifier ID and a service flow ID (SFID). These classifier errors were the only major errors in the request.

Recommended Action    Correct the classifier errors and reissue the request. Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software.

%UBR7100-4-DSA_MAJOR_MULTIPLE_ERRORS 
%UBR7200-4-DSA_MAJOR_MULTIPLE_ERRORS
%UBR10000-4-DSA_MAJOR_MULTIPLE_ERRORS: <133>CMTS[DOCSIS]:<83000124> Service Add rejected - Multiple major errors. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-major-multiple-errors(203) because the request included more than one major error with service flows, classifiers, and PHS rules.

Recommended Action    Reissue the command with a valid DSA-REQ message. Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that you are running released software on the CMTS.

%UBR7100-4-DSA_MAJOR_PHS_RULE_ERROR 
%UBR7200-4-DSA_MAJOR_PHS_RULE_ERROR
%UBR10000-4-DSA_MAJOR_PHS_RULE_ERROR: <133>CMTS[DOCSIS]:<83000123> Service Add rejected - Major PHS rule error. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a reject-major-PHS-rule-error(202) because the request did not contain both a service flow reference/ID and a classifier reference/ID. The PHS errors were the only major errors in the request.

Recommended Action    Verify the PHS rule and reissue the command. Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software.

%UBR7100-4-DSA_MAJOR_SRV_FLOW_ERROR 
%UBR7200-4-DSA_MAJOR_SRV_FLOW_ERROR
%UBR10000-4-DSA_MAJOR_SRV_FLOW_ERROR: <133>CMTS[DOCSIS]:<83000121> Service Add rejected - Major service flow error. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-major-service-flow(200) because the request did not contain either a service flow reference or service flow ID in a service flow TLV. The service flow errors were the only major errors in the request.

Recommended Action    Reissue the command with valid serviceflow reference/ID. Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that you are running released software on the Cisco CMTS.

%UBR7100-4-DSA_MSG_SYNTAX_ERROR 
%UBR7200-4-DSA_MSG_SYNTAX_ERROR
%UBR10000-4-DSA_MSG_SYNTAX_ERROR: <133>CMTS[DOCSIS]:<83000125> Service Add rejected - Message syntax error. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-message-syntax-error(204) because its format does not conform to the DOCSIS 1.1 specification. A common error is that a TLV in the message has the wrong length.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that you are running released software on the CMTS.

%UBR7100-4-DSA_MSG_TOO_BIG 
%UBR7200-4-DSA_MSG_TOO_BIG
%UBR10000-4-DSA_MSG_TOO_BIG: <133>CMTS[DOCSIS]:<83000126> Service Add rejected - Message too big. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-message-too-big(206) because the message needed to respond to the request would exceed the maximum allowable length.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that you are running released software on the CMTS.

%UBR7100-4-DSA_MULTIPLE_DOWNSTREAM_FLOW 
%UBR7200-4-DSA_MULTIPLE_DOWNSTREAM_FLOW
%UBR10000-4-DSA_MULTIPLE_DOWNSTREAM_FLOW: <133>CMTS[DOCSIS]:<83000116> Service Add rejected - Multiple downstream flow. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-multiple-downstream-flows(20) because it requested two or more downstream service flows.

Recommended Action    A single DSA-REQ message can include at most one request for a service flow in each direction (for example, one downstream service flow, one upstream service flow, or one downstream and one upstream service flow). Verify that the cable modem is running DOCSIS 1.1-certified software and is sending the proper DSA messages. Verify that the CMTS is running released software.

%UBR7100-4-DSA_MULTIPLE_ERRORS 
%UBR7200-4-DSA_MULTIPLE_ERRORS
%UBR10000-4-DSA_MULTIPLE_ERRORS: <133>CMTS[DOCSIS]:<83000109> Service Add rejected - Multiple errors. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-multiple-errors(13) because the request message had multiple errors in it.

Recommended Action    Reissue the command with a valid DSA-REQ message. Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS.

%UBR7100-4-DSA_MULTIPLE_UPSTREAM_FLOW 
%UBR7200-4-DSA_MULTIPLE_UPSTREAM_FLOW
%UBR10000-4-DSA_MULTIPLE_UPSTREAM_FLOW: <133>CMTS[DOCSIS]:<83000115> Service Add rejected - Multiple upstream flow. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-multiple-upstream-service-flows(19) because it requested two or more upstream service flows.

Recommended Action    A single DSA-REQ message can include at most one request for a service flow in each direction (for example, one downstream service flow, one upstream service flow, or one downstream and one upstream service flow). Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software.

%UBR7100-4-DSA_PARAMETER_INVALID_CONTEXT 
%UBR7200-4-DSA_PARAMETER_INVALID_CONTEXT
%UBR10000-4-DSA_PARAMETER_INVALID_CONTEXT: <133>CMTS[DOCSIS]:<83000119> Service Add rejected - Parameter invalid for context. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-parameter-invalid-for-context(23) because the message contained at least one parameter that was invalid for the TLV in which it was used.

Recommended Action    Verify the TLV used in the DSA-REQ and reissue the command. The cable modem should retry the request. Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that you are running released software on the CMTS.

%UBR7100-4-DSA_PERMANENT_ADMINISTRATIVE 
%UBR7200-4-DSA_PERMANENT_ADMINISTRATIVE
%UBR10000-4-DSA_PERMANENT_ADMINISTRATIVE: <133>CMTS[DOCSIS]:<83000103> Service Add rejected - Permanent Administrative. CM Mac Addr <[enet]>

Explanation    The DSA request was rejected with a confirmation code of reject-permanent/reject-admin(4) because the policy, configuration, or capabilities of the CMTS or cable modem do not allow this particular request.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software. If necessary, change to the DOCSIS configuration file for this cable modem to allow the requests. Verify that the CMTS is running released software. If necessary, change the CMTS configuration to allow this request.

%UBR7100-4-DSA_PHS_RULE_ANOTHER_FLOW 
%UBR7200-4-DSA_PHS_RULE_ANOTHER_FLOW
%UBR10000-4-DSA_PHS_RULE_ANOTHER_FLOW: <133>CMTS[DOCSIS]:<83000118> Service Add rejected - PHS rule for another flow. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-PHS-for-another-service-flow(22) because the request includes a Packet Header Suppression (PHS) rule that is reserved for a service flow other than the one being requested.

Recommended Action    Verify the PHS rule and the associated service flow reference, and reissue the command. Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software.

%UBR7100-4-DSA_PHS_RULE_EXISTS 
%UBR7200-4-DSA_PHS_RULE_EXISTS
%UBR10000-4-DSA_PHS_RULE_EXISTS: <133>CMTS[DOCSIS]:<83000113> Service Add rejected - PHS rule exists. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-PHS-rule-exists(17) because the request contains a Service ID and classifier ID combination for which a Packet Header Suppression (PHS) rule already exists.

Recommended Action    Verify the PHS rule and the associated service flow reference, and reissue the command. Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software.

%UBR7100-4-DSA_PHS_RULE_NOT_FOUND 
%UBR7200-4-DSA_PHS_RULE_NOT_FOUND
%UBR10000-4-DSA_PHS_RULE_NOT_FOUND: <133>CMTS[DOCSIS]:<83000112> Service Add rejected - PHS rule not found. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-PHS-rule-not-found(16) because the message specified a service flow ID and classifier ID combination for which no PHS rule exists.

Recommended Action    Reissue the command with valid parameters. Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS.

%UBR7100-4-DSA_REQUIRED_PARAMETER_NOT_PRESENT 
%UBR7200-4-DSA_REQUIRED_PARAMETER_NOT_PRESENT
%UBR10000-4-DSA_REQUIRED_PARAMETER_NOT_PRESENT: <133>CMTS[DOCSIS]:<83000104> Service Add rejected - Required parameter not present. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-required-parameter-not-present(8) because at least one required parameter was not present in the message.

Recommended Action    Reissue the command with all required parameters. In particular, if BPI+ is being used, specify a proper key sequence number and HMAC-digest value. Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS.

%UBR7100-4-DSA_RSP_ABORTED_NO_RSP 
%UBR7200-4-DSA_RSP_ABORTED_NO_RSP
%UBR10000-4-DSA_RSP_ABORTED_NO_RSP: <133>CMTS[DOCSIS]:<83010101> Service Add aborted - No RSP. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-add-aborted(12) because the cable modem did not provide a DSA response (DSA-RSP) message within the time-out period.

Recommended Action    No action is needed.

%UBR7100-4-DSA_RSP_INVALID_TRANSACTION_ID 
%UBR7200-4-DSA_RSP_INVALID_TRANSACTION_ID
%UBR10000-4-DSA_RSP_INVALID_TRANSACTION_ID: <133>CMTS[DOCSIS]:<83010100> Service Add response rejected - Invalid Transaction ID. CM Mac Addr <[enet]>

Explanation    The Dynamic Service Add request (DSA-REQ) was abandoned because the DSA response (DSA-RSP) from the indicated cable modem did not contain a transaction ID that matches those for any outstanding DSA requests for this cable modem. The message was rejected with a confirmation code of reject-unknown-transaction-id(10).

Recommended Action    The cable modem should retry the request. If the problem persists, verify that the cable modem is running DOCSIS 1.1-certified software and is sending the proper DSA messages. Verify that you are running released software on the CMTS.

%UBR10000-4-DSA_RSP_REJECT_MAJOR_CFR_ERROR: <133>CMTS[DOCSIS]:<83010115>Service 
Add Response rejected - Major classifier error. CM Mac Addr [enet]

Explanation    The Cable Modem Dynamic Service Addition Response (CM DSA RSP) is rejected because of a major classifier 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%UBR10000-4-DSA_RSP_REJECT_MAJOR_PHS_RULE_ERROR: 
<133>CMTS[DOCSIS]:<83010116>Service Add Response rejected -Major PHS Rule error. 
CM Mac Addr [enet]

Explanation    The CM DSA RSP is rejected because of a major Payload Header Suppression (PHS) rule 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%UBR10000-4-DSA_RSP_REJECT_MSG_TOO_BIG: <133>CMTS[DOCSIS]:<83010118>Service Add 
Response rejected - Message too big. CM Mac Addr [enet]

Explanation    The CM DSA RSP is rejected because the message is too long.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%UBR10000-4-DSA_RSP_REJECT_PARAM_INVALID_FOR_CONTEXT: 
<133>CMTS[DOCSIS]:<83010113>Service Add Response rejected -Parameter invalid for 
context. CM Mac Addr [enet]

Explanation    The CM DSA RSP is rejected because a parameter is invalid for the context.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%UBR10000-4-DSA_RSP_REJECT_REQD_PARAM_NOT_PRESENT: 
<133>CMTS[DOCSIS]:<83010106>Service Add Response rejected -Required parameter not 
present. CM Mac Addr [enet]

Explanation    The CM DSA RSP is rejected because the required parameter is not present.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%UBR10000-4-DSA_RSP_REJECT_UNRECOGNIZED_CONFIGURATION_SETTING: 
<133>CMTS[DOCSIS]:<83010105>Service Add Response rejected Unrecognized 
configuration setting. CM Mac Addr [enet]

Explanation    The CM DSA RSP is rejected because of an unrecognized configuration setting.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%UBR7100-4-DSA_SERVICE_FLOW_EXISTS 
%UBR7200-4-DSA_SERVICE_FLOW_EXISTS
%UBR10000-4-DSA_SERVICE_FLOW_EXISTS: <133>CMTS[DOCSIS]:<83000106> Service Add rejected Service flow exists. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-service-flow-exists(7) because the service flow to be added already exists.

Recommended Action    No action is needed.

%UBR7100-4-DSA_TEMP_DCC 
%UBR7200-4-DSA_TEMP_DCC
%UBR10000-4-DSA_TEMP_DCC: <133>CMTS[DOCSIS]:<83000127> Service Add rejected - Temporary DCC. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add response (DSA-RSP) with a confirmation code of reject-temporary-DCC(25) because the requested services are not currently available on the current channels.

Recommended Action    The cable modem should wait for the CMTS to send a Dynamic Channel Change request (DCC-REQ) and then again request the services after completing the channel change. If the CMTS does not send a DCC-REQ, the cable modem should wait for the T14 timer to expire before sending another request for these services.

%UBR7100-4-DSA_TEMP_NO_RESOURCE 
%UBR7200-4-DSA_TEMP_NO_RESOURCE
%UBR10000-4-DSA_TEMP_NO_RESOURCE: <133>CMTS[DOCSIS]:<83000102> Service Add rejected - Temporary no resource. CM Mac Addr <[enet]>

Explanation    The Dynamic Service Add request (DSA-REQ) has been rejected with a confirmation code of reject-temporary/reject-resource(3) because either the cable modem or CMTS has temporarily run out of a needed resource, such as memory or available SIDs.

Recommended Action    The cable modem should wait and retry the request at a later time. If necessary, reboot the cable modem to reinitialize its resources.

%UBR7100-4-DSA_UNRECOGNIZED_CONFIGURATION_SETTING 
%UBR7200-4-DSA_UNRECOGNIZED_CONFIGURATION_SETTING
%UBR10000-4-DSA_UNRECOGNIZED_CONFIGURATION_SETTING: <133>CMTS[DOCSIS]:<83000101> Service Add rejected - Unrecognized Configuration Setting. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-unrecognized-configuration-setting(2) because it included an unknown TLV, or a TLV with a value that is outside of the allowable range.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software.

%UBR7100-4-DSA_UNSPECIFIED_REASON 
%UBR7200-4-DSA_UNSPECIFIED_REASON
%UBR10000-4-DSA_UNSPECIFIED_REASON: <133>CMTS[DOCSIS]:<83000100> Service Add rejected - Unspecified reason. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Add request (DSA-REQ) with a confirmation code of reject-other(1) because of an error that does not match any of the other confirmation codes.

Recommended Action    No action is needed. If the problem persists, verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software.

%UBR7100-4-DSC_ABORTED_NO_ACK 
%UBR7200-4-DSC_ABORTED_NO_ACK
%UBR10000-4-DSC_ABORTED_NO_ACK: <133>CMTS[DOCSIS]:<83020201> Service Change Aborted - No ACK. CM Mac Addr <[enet]>

Explanation    The Dynamic Service Change request (DSC-REQ) was abandoned because the CMTS did not receive a DSC acknowledgement (DSC-ACK) message from the cable modem after sending a DSC response (DSC-RSP) message.

Recommended Action    No action is needed.

%UBR7100-4-DSC_ACK_REJECTED_INVALID_TRANSACTION_ID 
%UBR7200-4-DSC_ACK_REJECTED_INVALID_TRANSACTION_ID
%UBR10000-4-DSC_ACK_REJECTED_INVALID_TRANSACTION_ID: <133>CMTS[DOCSIS]:<83020200> Service Change ACK Rejected - Invalid transaction ID. CM Mac Addr <[enet]>");

Explanation    The Dynamic Service Change request (DSC-REQ) was abandoned because the DSC acknowledgement (DSC-ACK) from the indicated cable modem did not contain a transaction ID that matches those for any outstanding DSC requests for this cable modem. The message was rejected with a confirmation code of reject-unknown-transaction-id(10).

Recommended Action    The cable modem should retry the request. If the problem persists, verify that the cable modem is running DOCSIS 1.1-certified software and is sending the proper DSC messages. Verify that you are running released software on the CMTS.

%UBR7100-4-DSC_AUTH_FAILURE 
%UBR7200-4-DSC_AUTH_FAILURE
%UBR10000-4-DSC_AUTH_FAILURE: <133>CMTS[DOCSIS]:<83000220> Service Change rejected - Authorization failure. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change request (DSC-REQ) with a confirmation code of reject-authorization-failure(24) because the request was rejected by the DOCSIS authorization module.

Recommended Action    Verify that the cable modem is properly configured for BPI+ operations.

%UBR7100-4-DSC_CLASSIFIER_ANOTHER_FLOW 
%UBR7200-4-DSC_CLASSIFIER_ANOTHER_FLOW
%UBR10000-4-DSC_CLASSIFIER_ANOTHER_FLOW: <133>CMTS[DOCSIS]:<83000217> Service Change rejected - Classifier for another flow. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change request (DSC-REQ) with a confirmation code of reject-classifier-for-another-service-flow(21) because this packet classifier is already being used for a different service flow than the one specified in the request.

Recommended Action    The cable modem should retry the request.

%UBR7100-4-DSC_CLASSIFIER_EXISTS 
%UBR7200-4-DSC_CLASSIFIER_EXISTS
%UBR10000-4-DSC_CLASSIFIER_EXISTS: <133>CMTS[DOCSIS]:<83000211> Service Change rejected - Classifier exists. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change request (DSC-REQ) with a confirmation code of reject-classifier-exists(15) because the requested packet classifier already exists.

Recommended Action    The cable modem should retry the request.

%UBR7100-4-DSC_CLASSIFIER_NOT_FOUND 
%UBR7200-4-DSC_CLASSIFIER_NOT_FOUND
%UBR10000-4-DSC_CLASSIFIER_NOT_FOUND: <133>CMTS[DOCSIS]:<83000210> Service Change rejected - Classifier not found. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change request (DSC-REQ) with a confirmation code of reject-classifier-not-found(14) because the requested packet classifier ID is invalid or does not exist.

Recommended Action    Reissue the command with a valid packet classifier ID. Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS.

%UBR7100-4-DSC_DUPLICATE_REF_ID_INDEX 
%UBR7200-4-DSC_DUPLICATE_REF_ID_INDEX
%UBR10000-4-DSC_DUPLICATE_REF_ID_INDEX: <133>CMTS[DOCSIS]:<83000214> Service Change rejected - Duplicate reference-ID or index in message. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the Dynamic Service Change request (DSC-REQ) with a confirmation code of reject-duplicate-reference-ID-or-index-in-message(18) because the message used a service flow reference, classifier reference, service flow ID (SFID), or classifier ID twice in an illegal way.

Recommended Action    Reissue the command with a valid service flow. Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS.

%UBR7100-4-DSC_HEADER_SUPPR_SETTING_NOT_SUPPORTED 
%UBR7200-4-DSC_HEADER_SUPPR_SETTING_NOT_SUPPORTED
%UBR10000-4-DSC_HEADER_SUPPR_SETTING_NOT_SUPPORTED: <133>CMTS[DOCSIS]:<83000207> Service Change rejected - Header suppression setting not supported. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change request (DSC-REQ) with a confirmation code of reject-header-suppression(9) because the requested Packet Header Suppression (PHS) configuration cannot be supported for some reason.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software.

%UBR7100-4-DSC_HMAC_AUTHENTICATION_FAILURE 
%UBR7200-4-DSC_HMAC_AUTHENTICATION_FAILURE
%UBR10000-4-DSC_HMAC_AUTHENTICATION_FAILURE: <133>CMTS[DOCSIS]:<83000208> Service Change rejected - HMAC Auth Failure. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change request (DSC-REQ) with a confirmation code of reject-authentication-failure(11) because the message contained an invalid HMAC-digest or Message Integrity Check (MIC) value.

Recommended Action    Verify that the cable modem is properly configured for BPI+ operations.

%UBR7100-4-DSC_MAJOR_CLASSIFIER_ERROR 
%UBR7200-4-DSC_MAJOR_CLASSIFIER_ERROR
%UBR10000-4-DSC_MAJOR_CLASSIFIER_ERROR: <133>CMTS[DOCSIS]:<83000222> Service Change rejected - Major classifier error. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change request (DSC-REQ) with a confirmation code of reject-major-classifier-error(201) because the request either did not have a classifier reference, or because it did not specify both a classifier ID and a service flow ID (SFID). These classifier errors were the only major errors in the request.

Recommended Action    Include the classifier reference/identifier and a service flow identifier under the Classifier Parameters in the Dynamic Change Action TLV. Verify that the cable modem is running DOCSIS 1.1-certified software and is sending the proper DSA messages. Verify that the CMTS is running a released software.

%UBR7100-4-DSC_MAJOR_MULTIPLE_ERRORS 
%UBR7200-4-DSC_MAJOR_MULTIPLE_ERRORS
%UBR10000-4-DSC_MAJOR_MULTIPLE_ERRORS: <133>CMTS[DOCSIS]:<83000224> Service Change rejected - Multiple major errors. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change request (DSC-REQ) with a confirmation code of reject-major-multiple-errors(203) because the request included more than one major error with service flows, classifiers, and PHS rules.

Recommended Action    Reissue the command with a valid DSC-REQ message by performing these steps:

1. Include a "service flow reference or SFID in the service flow encoding" to correct the service flow major error.

2. Include a "classifier reference, or a classifier ID and a Service Flow ID" to correct the classifier major error.

3. Include a "service flow reference/identifier, a classifier reference/identifier, and PHS rule" to correct the PHS rules error.

%UBR7100-4-DSC_MAJOR_PHS_RULE_ERROR 
%UBR7200-4-DSC_MAJOR_PHS_RULE_ERROR
%UBR10000-4-DSC_MAJOR_PHS_RULE_ERROR: <133>CMTS[DOCSIS]:<83000223> Service Change rejected - Major PHS rule error. CM Mac Addr <[enet]>

Explanation    The DSC request was rejected with a reject-major-PHS-rule-error(202) because the DSC REQ message did not have both - a Service Flow Reference/Identifier and a Classifier Reference/Identifier. The PHS rule major errors were the only major errors.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software.

%UBR7100-4-DSC_MAJOR_SRV_FLOW_ERROR 
%UBR7200-4-DSC_MAJOR_SRV_FLOW_ERROR
%UBR10000-4-DSC_MAJOR_SRV_FLOW_ERROR: <133>CMTS[DOCSIS]:<83000221> Service Change rejected - Major service flow error. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change request (DSC-REQ) with a confirmation code of reject-major-service-flow(200) because the request did not contain either a service flow reference or service flow ID in a service flow TLV. The service flow errors were the only major errors in the request.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software.

%UBR7100-4-DSC_MSG_SYNTAX_ERROR 
%UBR7200-4-DSC_MSG_SYNTAX_ERROR
%UBR10000-4-DSC_MSG_SYNTAX_ERROR: <133>CMTS[DOCSIS]:<83000225> Service Change rejected - Message syntax error. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change request (DSC-REQ) with a confirmation code of reject-message-syntax-error(204) because its format does not conform to the DOCSIS 1.1 specification. A common error is that a TLV in the message has the wrong length.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that you are running released software on the CMTS.

%UBR7100-4-DSC_MSG_TOO_BIG 
%UBR7200-4-DSC_MSG_TOO_BIG
%UBR10000-4-DSC_MSG_TOO_BIG: <133>CMTS[DOCSIS]:<83000226> Service Change rejected - Message too big. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change request (DSC-REQ) with a confirmation code of reject-message-too-big(206) because the message needed to respond to the request would exceed the maximum allowable length.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS.

%UBR7100-4-DSC_MULTIPLE_DOWNSTREAM_FLOW 
%UBR7200-4-DSC_MULTIPLE_DOWNSTREAM_FLOW
%UBR10000-4-DSC_MULTIPLE_DOWNSTREAM_FLOW: <133>CMTS[DOCSIS]:<83000216> Service Change rejected - Multiple downstream flow. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change request (DSC-REQ) with a confirmation code of reject-multiple-downstream-flows(20) because it requested two or more downstream service flows.

Recommended Action    A single DSC-REQ message can include at most one request for a service flow in each direction (for example, one downstream service flow, one upstream service flow, or one downstream and one upstream service flow). Verify that the cable modem is running DOCSIS 1.1-certified software and is sending the proper DSC messages. Verify that the CMTS is running released software.

%UBR7100-4-DSC_MULTIPLE_ERRORS 
%UBR7200-4-DSC_MULTIPLE_ERRORS
%UBR10000-4-DSC_MULTIPLE_ERRORS: <133>CMTS[DOCSIS]:<83000209> Service Change rejected - Multiple errors. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change request (DSC-REQ) with a confirmation code of reject-multiple-errors(13) because the request message had multiple errors in it.

Recommended Action    Reissue the command with a valid DSC-REQ message. Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS.

%UBR7100-4-DSC_MULTIPLE_UPSTREAM_FLOW 
%UBR7200-4-DSC_MULTIPLE_UPSTREAM_FLOW
%UBR10000-4-DSC_MULTIPLE_UPSTREAM_FLOW: <133>CMTS[DOCSIS]:<83000215> Service Change rejected - Multiple upstream flow. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change request (DSC-REQ) with a confirmation code of reject-multiple-upstream-service-flows(19) because it requested two or more upstream service flows.

Recommended Action    A single DSC-REQ message can include at most one request for a service flow in each direction (for example, one downstream service flow, one upstream service flow, or one downstream and one upstream service flow). Verify that the cable modem is running DOCSIS 1.1-certified software and is sending the proper DSC messages. Verify that the CMTS is running released software.

%UBR7100-4-DSC_PARAMETER_INVALID_CONTEXT 
%UBR7200-4-DSC_PARAMETER_INVALID_CONTEXT
%UBR10000-4-DSC_PARAMETER_INVALID_CONTEXT: <133>CMTS[DOCSIS]:<83000219> Service Change rejected - Parameter invalid for context. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change request (DSC-REQ) with a confirmation code of reject-parameter-invalid-for-context(23) because the message contained at least one parameter that was invalid for the TLV in which it was used.

Recommended Action    The cable modem should retry the request. If the problem persists, verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software.

%UBR7100-4-DSC_PERMANENT_ADMINISTRATIVE 
%UBR7200-4-DSC_PERMANENT_ADMINISTRATIVE
%UBR10000-4-DSC_PERMANENT_ADMINISTRATIVE: <133>CMTS[DOCSIS]:<83000203> Service Change rejected - Permanent Administrative. CM Mac Addr <[enet]>

Explanation    The Dynamic Service Change request (DSC-REQ) was rejected with a confirmation code of reject-permanent/reject-admin(4) because the policy, configuration, or capabilities of the CMTS or cable modem do not allow this particular request.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software. If necessary, change to the DOCSIS configuration file for this cable modem to allow the requests. Verify that the CMTS is running released software. If necessary, change the CMTS configuration to allow this request.

%UBR7100-4-DSC_PHS_RULE_ANOTHER_FLOW 
%UBR7200-4-DSC_PHS_RULE_ANOTHER_FLOW
%UBR10000-4-DSC_PHS_RULE_ANOTHER_FLOW: <133>CMTS[DOCSIS]:<83000218> Service Change rejected - PHS rule for another flow. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change request (DSC-REQ) with a confirmation code of reject-PHS-for-another-service-flow(22) because the request includes a Packet Header Suppression (PHS) rule that is reserved for a service flow other than the one being requested.

Recommended Action    The cable modem should retry the request. Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software.

%UBR7100-4-DSC_PHS_RULE_EXISTS 
%UBR7200-4-DSC_PHS_RULE_EXISTS
%UBR10000-4-DSC_PHS_RULE_EXISTS: <133>CMTS[DOCSIS]:<83000213> Service Change rejected - PHS rule exists. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change request (DSC-REQ) with a confirmation code of reject-PHS-rule-exists(17) because the request contains a Service ID and classifier ID combination for which a Packet Header Suppression (PHS) rule already exists.

Recommended Action    The cable modem should retry the request. Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software.

%UBR7100-4-DSC_PHS_RULE_NOT_FOUND 
%UBR7200-4-DSC_PHS_RULE_NOT_FOUND
%UBR10000-4-DSC_PHS_RULE_NOT_FOUND: <133>CMTS[DOCSIS]:<83000212> Service Change rejected - PHS rule not found. CM Mac Addr <[enet]>

Explanation    The Dynamic Service Change request (DSC-REQ) was rejected with a confirmation code of reject-PHS-rule-not-found(16) because the message specified a service flow ID and classifier ID combination for which no PHS rule exists.

Recommended Action    Reissue the command with valid parameters. Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS.

%UBR7100-4-DSC_REQUESTOR_NOT_OWNER 
%UBR7200-4-DSC_REQUESTOR_NOT_OWNER
%UBR10000-4-DSC_REQUESTOR_NOT_OWNER: <133>CMTS[DOCSIS]:<83000204> Service Change rejected - Requestor Not Owner Of Service Flow. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change request (DSC-REQ) with a confirmation code of reject-not-owner(5) because the cable modem is not associated with this particular service flow.

Recommended Action    No action is needed. If the problem persists, verify that the cable modem is running DOCSIS 1.1-certified software. Also investigate the possibility that this is a spoofing or theft-of-service attack.

%UBR7100-4-DSC_REQUIRED_PARAMETER_NOT_PRESENT 
%UBR7200-4-DSC_REQUIRED_PARAMETER_NOT_PRESENT
%UBR10000-4-DSC_REQUIRED_PARAMETER_NOT_PRESENT: <133>CMTS[DOCSIS]:<83000206> Service Change rejected - Required parameter not present. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change request (DSC-REQ) with a confirmation code of reject-required-parameter-not-present(8) because at least one required parameter was not present in the message.

Recommended Action    Reissue the command with all required parameters. In particular, if BPI+ is being used, specify a proper key sequence number and HMAC-digest value. Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that you are running released software on the CMTS.

%UBR7100-4-DSC_RSP_ABORTED_NO_RSP 
%UBR7200-4-DSC_RSP_ABORTED_NO_RSP
%UBR10000-4-DSC_RSP_ABORTED_NO_RSP: <133>CMTS[DOCSIS]:<83010201> Service Change aborted - No RSP. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change request (DSC-REQ) because the cable modem did not provide a DSC response (DSC-RSP) message within the time-out period.

Recommended Action    No action is needed.

%UBR7100-4-DSC_RSP_INVALID_TRANSACTION_ID 
%UBR7200-4-DSC_RSP_INVALID_TRANSACTION_ID
%UBR10000-4-DSC_RSP_INVALID_TRANSACTION_ID: <133>CMTS[DOCSIS]:<83010200> Service Change response rejected - Invalid Transaction ID. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change response (DSC-RSP) because it did not contain a transaction ID that matches those for any outstanding DSC requests for this cable modem. The message was rejected with a confirmation code of reject-unknown-transaction-id(10).

Recommended Action    The cable modem should retry the request. If the problem persists, verify that the cable modem is running DOCSIS 1.1-certified software and is sending the proper DSC messages. Verify that you are running released software on the CMTS.

%UBR10000-4-DSC_RSP_REJECT_AUTHORIZATION_FAILURE: 
<133>CMTS[DOCSIS]:<83010202>Service Change Response rejected - HMAC Auth failure 
CM Mac Addr [enet]

Explanation    The Cable Modem Dynamic Service Change Response (CM DSC RSP) is rejected because of an authorization failure.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%UBR10000-4-DSC_RSP_REJECT_DUPLC_REF_ID_OR_INDEX: 
<133>CMTS[DOCSIS]:<83010210>Service Change Response rejected - Duplicated 
reference-ID or index in message. CM Mac Addr [enet]

Explanation    The CM DSC RSP is rejected because of a duplicate reference ID or index.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%UBR10000-4-DSC_RSP_REJECT_MAJOR_CFR_ERROR: <133>CMTS[DOCSIS]:<83010212>Service 
Change Response rejected - Major classifier error. CM Mac Addr [enet]

Explanation    The CM DSC RSP is rejected because of a major classifier 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%UBR10000-4-DSC_RSP_REJECT_MAJOR_PHS_RULE_ERROR: 
<133>CMTS[DOCSIS]:<83010213>Service Change Response rejected - Major PHS rule 
error. CM Mac Addr [enet]

Explanation    The CM DSC RSP is rejected because of a major PHS 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%UBR10000-4-DSC_RSP_REJECT_MSG_SYNTAX_ERROR: <133>CMTS[DOCSIS]:<83010203>Service 
Change Response rejected - Message syntax error. CM Mac Addr [enet]

Explanation    The CM DSC RSP is rejected because of a message syntax 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%UBR10000-4-DSC_RSP_REJECT_MSG_TOO_BIG: <133>CMTS[DOCSIS]:<83010215>Service 
Change Response rejected - Message too big. CM Mac Addr [enet]

Explanation    The CM DSC RSP is rejected because the message is too long.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%UBR10000-4-DSC_RSP_REJECT_PHS_RULE_EXISTS: <133>CMTS[DOCSIS]:<83010209>Service 
Change Response rejected - PHS rule exists.CM Mac Addr [enet]

Explanation    The CM DSC RSP is rejected because a PHS rule exists.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%UBR10000-4-DSC_RSP_REJECT_REQD_PARAM_NOT_PRESENT: 
<133>CMTS[DOCSIS]:<83010206>Service Change Response rejected - Required parameter 
not present.CM Mac Addr [enet]

Explanation    The CM DSC RSP is rejected because the required parameter is not present.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%UBR10000-4-DSC_RSP_UNRECOGNIZED_CONFIGURATION_SETTING: 
<133>CMTS[DOCSIS]:<83010205>Service Change Response rejected - Unrecognized 
configuration setting. CM Mac Addr [enet].

Explanation    The CM DSC RSP is rejected because of an unrecognized configuration setting.

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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%UBR7100-4-DSC_SERVICE_FLOW_NOT_FOUND 
%UBR7200-4-DSC_SERVICE_FLOW_NOT_FOUND
%UBR10000-4-DSC_SERVICE_FLOW_NOT_FOUND: <133>CMTS[DOCSIS]:<83000205> Service Change rejected - Service Flow Not Found. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change request (DSC-REQ) with a confirmation code of reject-service-flow-not-found(6) because the requested service flow does not exist.

Recommended Action    No action is needed. If the problem persists, verify that the cable modem is running DOCSIS 1.1-certified software and is sending the proper DSC messages. Verify that the CMTS is running released software.

%UBR7100-4-DSC_TEMP_DCC 
%UBR7200-4-DSC_TEMP_DCC
%UBR10000-4-DSC_TEMP_DCC: <133>CMTS[DOCSIS]:<83000227> Service Change rejected - Temporary DCC. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change response (DSC-RSP) with a confirmation code of reject-temporary-DCC(25) because the requested services are not currently available on the current channels.

Recommended Action    The cable modem should wait for the CMTS to send a Dynamic Channel Change request (DCC-REQ) and then again request the services after completing the channel change. If the CMTS does not send a DCC-REQ, the cable modem should wait for the T14 timer to expire before sending another request for these services.

%UBR7100-4-DSC_TEMP_NO_RESOURCE 
%UBR7200-4-DSC_TEMP_NO_RESOURCE
%UBR10000-4-DSC_TEMP_NO_RESOURCE: <133>CMTS[DOCSIS]:<83000202> Service Change rejected - Temporary no resource. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change response (DSC-RSP) with a confirmation code of reject-temporary/reject-resource(3) because either the cable modem or CMTS has temporarily run out of a needed resource, such as memory or available SIDs.

Recommended Action    The cable modem should wait and retry the request at a later time. If necessary, reboot the cable modem to reinitialize its resources.

%UBR7100-4-DSC_UNRECOGNIZED_CONFIGURATION_SETTING 
%UBR7200-4-DSC_UNRECOGNIZED_CONFIGURATION_SETTING
%UBR10000-4-DSC_UNRECOGNIZED_CONFIGURATION_SETTING: <133>CMTS[DOCSIS]:<83000201> Service Change Rejected - Unrecognized Configuration Setting. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change request (DSC-REQ) with a confirmation code of reject-unrecognized-configuration-setting(2) because it included an unknown TLV, or a TLV with a value outside of the allowable range.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software.

%UBR7100-4-DSC_UNSPECIFIED_REASON 
%UBR7200-4-DSC_UNSPECIFIED_REASON
%UBR10000-4-DSC_UNSPECIFIED_REASON: <133>CMTS[DOCSIS]:<83000200> Service Change rejected - Unspecified reason. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Change request (DSC-REQ) with a confirmation code of reject-other(1) because of an error that does not match any of the other confirmation codes.

Recommended Action    No action is needed. If the problem persists, verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software.

%UBR7100-4-DSD_HMAC_AUTHENTICATION_FAILURE 
%UBR7200-4-DSD_HMAC_AUTHENTICATION_FAILURE
%UBR10000-4-DSD_HMAC_AUTHENTICATION_FAILURE: <133>CMTS[DOCSIS]:<83000303> Service Delete rejected - HMAC Auth Failure. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Delete request (DSD-REQ) with a confirmation code of reject-authentication-failure(11) because the message contained an invalid HMAC-digest or Message Integrity Check (MIC) value.

Explanation    Verify that the cable modem is properly configured for BPI+ operations.

%UBR7100-4-DSD_MSG_SYNTAX_ERROR 
%UBR7200-4-DSD_MSG_SYNTAX_ERROR
%UBR10000-4-DSD_MSG_SYNTAX_ERROR: <133>CMTS[DOCSIS]:<83000304> Service Delete rejected - Message Syntax Error. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Delete request (DSD-REQ) with a confirmation code of reject-message-syntax-error(204) because its format does not conform to the DOCSIS 1.1 specification. A common error is that a TLV in the message has the wrong length.

Recommended Action    Verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that you are running released software on the CMTS.

%UBR7100-4-DSD_REQUESTOR_NOT_OWNER 
%UBR7200-4-DSD_REQUESTOR_NOT_OWNER
%UBR10000-4-DSD_REQUESTOR_NOT_OWNER: <133>CMTS[DOCSIS]:<83000301> Service Delete rejected - Requestor Not Owner of service flow. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Delete request (DSD-REQ) with a confirmation code of reject-not-owner(5) because the cable modem is not associated with this particular service flow.

Recommended Action    No action is needed. If the problem persists, verify that the cable modem is running DOCSIS 1.1-certified software. Also investigate the possibility that this is a spoofing or theft-of-service attack.

%UBR7100-4-DSD_RSP_REJECTED_INVALID_TRANSACTION_ID 
%UBR7200-4-DSD_RSP_REJECTED_INVALID_TRANSACTION_ID
%UBR10000-4-DSD_RSP_REJECTED_INVALID_TRANSACTION_ID: <133>CMTS[DOCSIS]:<83010300> Service Delete Response rejected - Invalid transaction ID. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the Dynamic Service Delete response (DSD-RSP) from the indicated cable modem because it did not contain a transaction ID that matches those for any outstanding DSD requests for this cable modem. The message was rejected with a confirmation code of reject-unknown-transaction-id(10).

Recommended Action    The cable modem should retry the request. If the problem persists, verify that the cable modem is running DOCSIS 1.1-certified software and is sending the proper DSD messages. Verify that you are running released software on the CMTS.

%UBR7100-4-DSD_SERVICE_FLOW_NOT_FOUND 
%UBR7200-4-DSD_SERVICE_FLOW_NOT_FOUND
%UBR10000-4-DSD_SERVICE_FLOW_NOT_FOUND: <133>CMTS[DOCSIS]:<83000302> Service Delete rejected - Service Flow Not Found. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Delete request (DSD-REQ) with a confirmation code of reject-service-flow-not-found(6) because the requested service flow does not exist.

Recommended Action    No action is needed. If the problem persists, verify that the cable modem is running DOCSIS 1.1-certified software and is sending the proper DSC messages. Verify that the CMTS is running released software.

%UBR7100-4-DSD_UNSPECIFIED_REASON 
%UBR7200-4-DSD_UNSPECIFIED_REASON
%UBR10000-4-DSD_UNSPECIFIED_REASON: <133>CMTS[DOCSIS]:<83000300> Service Delete rejected - Unspecified reason. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's Dynamic Service Delete request (DSD-REQ) with a confirmation code of reject-other(1) because of an error that does not match any of the other confirmation codes.

Recommended Action    No action is needed. If the problem persists, verify that the cable modem is running DOCSIS 1.1-certified software and is using a valid DOCSIS configuration file. Verify that the CMTS is running released software.

%UBR7100-6-DSG_ALL_TUNNEL_REMOVED 
%UBR7200-6-DSG_ALL_TUNNEL_REMOVED: All DSG tunnels are removed on interface [chars] and its subinterfaces

Explanation    An operator has disabled the DOCSIS Set-top Gateway (DSG) on the indicated cable interface and its subinterfaces, using the no cable dsg command.

Recommended Action    No action is needed.

UBR7100-3-DSG_HBEAT_FAILED
UBR7200-3-DSG_HBEAT_FAILED: Interface [chars] failed to send hbeat packet for vendor [chars]

Explanation    The DSG subsystem did not send a keepalive message (heartbeat packet) as expected for the particular vendor's DSG tunnel on the indicated cable interface or subinterface. When DSG keepalive messages are enabled, the system sends one keepalive message each second. After 30 DSG keepalives are missed, the Cisco CMTS may suspend DSG operations on the cable interface.

Recommended Action    Verify that DSG operations are enabled on the interface, using the cable dsg cable interface command. Verify that keepalive messages are required for your DSG network. If they are not, disable the keepalive messages, using the no cable dsg keepalive global configuration command. If the problem persists, verify that you are running released software on the Cisco CMTS. Gather information about the amount of memory in the system, and 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.

%UBR7100-6-DSPRIMARYSFIDCONFLICT
%UBR7200-6-DSPRIMARYSFIDCONFLICT
%UBR10000-6-DSPRIMARYSFIDCONFLICT: Assigned ds primary sfid [decimal] conflicts with existing ds primary sfid [decimal] for Cable modem [enet] on interface [chars]

Explanation    The assigned downstream primary Service Flow ID (SFID) conflicts with the existing downstream primary SFID for the cable modem.

Recommended Action    This message is informational only.

%UBR7100-4-DSX_MSG_ERROR
%UBR7200-4-DSX_MSG_ERROR
%UBR10000-4-DSX_MSG_ERROR: MSG type: [chars], Error code: [decimal]

Explanation    Received an invalid DSX message.

Recommended Action    Turn on debug to see details of the DSX message.

%UBR7100-4-DSX_RESTORE_CFR_STATE_FAILED
%UBR7200-4-DSX_RESTORE_CFR_STATE_FAILED
%UBR10000-4-DSX_RESTORE_CFR_STATE_FAILED: DSX restore cfr state fail. Attempted to restore state. CM Mac Addr <[enet]>

Explanation    DSX attempt to restore the CFR state failed.

Recommended Action    No action is needed.

%UBR7100-4-DSX_RESTORE_INVALID_CFRID
%UBR7200-4-DSX_RESTORE_INVALID_CFRID
%UBR10000-4-DSX_RESTORE_INVALID_CFRID: DSX restore cfr state found invalid cfrid. CM Mac Addr <[enet]>

Explanation    An invalid CFRID is found in the DSX restore CFR state.

Recommended Action    No action is needed.

%UBR7100-6-DUAL_CLEANUP_ATTEMPT
%UBR7200-6-DUAL_CLEANUP_ATTEMPT
%UBR10000-6-DUAL_CLEANUP_ATTEMPT: Second cleanup for modem

Explanation    The CMTS router attempted twice to clean up a modem entry.

Recommended Action    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.

%UBR7100-4-DUPLICATEMAC
%UBR7200-4-DUPLICATEMAC
%UBR10000-4-DUPLICATEMAC: Cable modem [enet] is online on both interface [chars] and interface [chars].

Explanation    The specified cable modem has been detected on two interfaces. This message indicates that two cable modems are using the same MAC address. This could be a theft-of-service or MAC address spoofing attempt.

Recommended Action    Check for cable modems with duplicate MAC addresses.

%UBR7200-3-ENVM_FAN_OVERLOAD: Fan Tray overloaded, fail to support the linecard 
at slot [dec]

Explanation    The cooling power provided by the fans of the router is lower than the requirement of some line cards in the chassis.

Recommended Action    Replace the fan immediately. Otherwise, the system may shut down or fail to operate properly.

%UBR7200-4-ENVM_PS_OVERLOAD: Power supply may be overloaded to support the line 
card installed in slot [dec]

Explanation    The power supply may be insufficient to support the number of line cards installed in the system under certain operation conditions like high temperature and high voltage margining.

Recommended Action    Upgrade the power supply immediately. Otherwise, the system may fail to work properly under certain operating conditions.

%UBR7100-4-FAILED_DS_SID_LOOKUP
%UBR7200-4-FAILED_DS_SID_LOOKUP
%UBR10000-4-FAILED_DS_SID_LOOKUP: Failed to find host in DS on int [chars] with SID [decimal], IP = [IP_address], MAC = [enet]

Explanation    The CMTS router has failed to process the Lease-Query response.

Recommended Action    Check if the host is provisioned on the DHCP server.

%UBR7100-6-FECKBYTEADJUST
%UBR7200-6-FECKBYTEADJUST
%UBR10000-6-FECKBYTEADJUST: [char] burst's FEC K BYTE in mod profile [dec] is adjusted to [dec]

Explanation    The configuration for the indicated profile (either in the configuration file or from a CLI command) specified an incorrect value for the FEC parameter, so the CMTS adjusted the FEC parameter to a minimum valid value for the profile.

Recommended Action    No action is needed.

%UBR7100-3-FLOW_ERR
%UBR7200-3-FLOW_ERR
%UBR10000-3-FLOW_ERR: Flow error sfid [decimal] sid [decimal] CM Mac address <[enet]>

Explanation    An internal software error has occurred.

Recommended Action    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.

%UBR7100-6-FORCE_QOS_CMD_FAILED
%UBR7200-6-FORCE_QOS_CMD_FAILED
%UBR10000-6-FORCE_QOS_CMD_FAILED: Unable to switch modem [chars] to QoS profile [dec].

Explanation    A user gave the cable modem qos profile command to change the quality of service (QoS) profile for the indicated cable modem, but the Cisco CMTS router could not change the modem to the specified profile. This could be due to an incorrect cable modem or invalid QoS profile being specified with the command, or it could also be because the current QoS profile on the cable modem was not created on the Cisco CMTS. The cable modem qos profile command has an effect only when the profile that it specifies and the original QoS profile on the cable modem have been created already on the Cisco CMTS, using the cable qos profile command.

Recommended Action    Verify that the correct cable modem was specified in the cable modem qos profile command. Also use the show cable qos profile and show cable modem registration commands to verify that the modem's current QoS profile and the new QoS profile have been created on the Cisco CMTS. If the problem persists, enable QoS debugging using the debug cable interface verbose and debug cable qos commands to determine why the profile change is failing.

%UBR7100-3-FPSUBINIT
%UBR7200-3-FPSUBINIT
%UBR10000-3-FPSUBINIT: Unable to create subinterface [chars] for hw interface [chars]

Explanation    The system was unable to create the specified subinterface on the specified interface, because it could not create the necessary internal subinterface data structures.

Recommended Action    Verify that you are running released software on the Cisco CMTS. Gather information about the amount of memory in the system, and 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.

%UBR7100-6-FREERUN
%UBR7200-6-FREERUN
%UBR10000-6-FREERUN: Cable clock in Freerun mode

Explanation    The clock card is in free-run mode.

Recommended Action    No action is needed.

%UBR7100-6-GUARDADJUST
%UBR7200-6-GUARDADJUST
%UBR10000-6-GUARDADJUST: [chars] burst's guard time in mod profile [dec] is adjusted to [dec] symbols.

Explanation    The burst guard time for the specified modulation profile on the specified interface has been adjusted to the indicated value.

Recommended Action    No action is needed.

%UBR7100-6-GUARDSYMLENADJUST
%UBR7200-6-GUARDSYMLENADJUST
%UBR10000-6-GUARDSYMLENADJUST: [chars] burst's guard symbol length in modulation profile [dec] is adjusted to the operable value of [dec] symbols.

Explanation    The CMTS has adjusted the guard symbol length in the indicated burst profile to the valid value.

Recommended Action    No action is required.

%UBR7100-4-HEADER_SUPPRESSION_SETTING_NOT_SUPPORTED
%UBR7200-4-HEADER_SUPPRESSION_SETTING_NOT_SUPPORTED
%UBR10000-4-HEADER_SUPPRESSION_SETTING_NOT_SUPPORTED: <133>CMTS[DOCSIS]: <73020105> Registration rejected, Header suppression setting not supported. CM Mac Addr [enet]

Explanation    The CMTS rejected a cable modem's registration request with a confirmation code of reject-header-suppression(9) because the requested Packet Header Suppression (PHS) configuration cannot be supported for some reason.

Recommended Action    Check the DOCSIS configuration file being used by this cable modem and correct any errors in the PHS fields. Verify that the cable modem is running DOCSIS 1.1-certified software. Verify that the CMTS is running released software.

%UBR7100-6-HOLDOVER
%UBR7200-6-HOLDOVER
%UBR10000-6-HOLDOVER: Cable clock in Holdover mode

Explanation    The clock card has switched to holdover mode.

Recommended Action    Check the reference source.

%UBR7200-3-HOTLISTMAC
%UBR10000-3-HOTLISTMAC: Investigating MAC=%e sid %d interface %s: MAC blocked

Explanation    The Cisco CMTS glean function received a blocked MAC address. This warning indicates that an untrusted MAC address is sending messages to the Cisco CMTS.

Recommended Action    Check for spoofing. Look for the CPE that is using the blocked MAC address. Remove the CPE device that sends too many messages. 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%UBR7100-3-HUNGFFTSTATE
%UBR7200-3-HUNGFFTSTATE
%UBR10000-3-HUNGFFTSTATE: BCM3138 chip [dec] is not idle for [dec] retries

Explanation    Some cable interface line cards use the Broadcom BCM3138 burst receiver to perform a Fast Fourier Transform (FFT) for digital spectrum analysis, and the card should perform only one FFT operation at a time. This error message indicates that the software repeatedly checked to see if the specified BCM3138 chip was idle and available for the next FFT operation, but that the chip never became available. The software assumes that the chip entered a hung state and so resets the chip.

Recommended Action    No action is needed unless this error occurs repeatedly. If so, verify that you are running released software on the CMTS. 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.

%UBR7100-4-HWFAULT
%UBR7200-4-HWFAULT
%UBR10000-4-HWFAULT: Hardware Fault in Clockcard

Explanation    A hardware error involving the clock card has occurred.

Recommended Action    Replace the clock card.

%UBR7100-3-I2CERR 
%UBR7200-3-I2CERR
%UBR10000-3-I2CERR: [chars].

Explanation    An error has occurred while accessing the internal bus.

Recommended Action    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. If modems are falling offline with the error, try online insertion and removal (OIR) of the line card to recover the service.

%UBR7100-3-I2CUPXERR 
%UBR7200-3-I2CUPXERR
%UBR10000-3-I2CUPXERR: [chars].

Explanation    An error has occurred while accessing the Upconverter.

Recommended Action    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. If modems are falling offline with the error, try online insertion and removal (OIR) of the line card to recover the service.

%UBR7100-3-IDB_MISMATCH 
%UBR7200-3-IDB_MISMATCH
%UBR10000-3-IDB_MISMATCH: DHCP IP Address Assign Mismatch MAC [enet] on [chars] assigned to [chars] with [IP_address]

Explanation    A DHCP server assignment error has occurred.

Recommended Action    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.

%UBR7100-3-INTERCEPT
%UBR7200-3-INTERCEPT
%UBR10000-3-INTERCEPT: Interface [chars], Failed to send intercept packet to server [IP_address]:[dec]

Explanation    An internal software error has occurred.

Recommended Action    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.

%UBR7100-3-INVALID_BP_CONFIGURATION_SETTING_VALUE
%UBR7200-3-INVALID_BP_CONFIGURATION_SETTING_VALUE
%UBR10000-3-INVALID_BP_CONFIGURATION_SETTING_VALUE: <132>CMTS[DOCSIS]:<66010200> Invalid BP Configuration Setting Value for TLV type [dec]. CM MAC Addr [enet]

Explanation    The CMTS rejected the cable modem's registration request (REG-REQ) because it presented a bad value for the BPI configuration field in its configuration file.

Recommended Action    Check the DOCSIS configuration file that this cable modem is using and correct any errors. Reboot the cable modem. If the problem persists, it could indicate a possible theft-of-service attack by someone using a modified configuration file.

%UBR7100-4-INVALID_COS_CONFIGURATION
%UBR7200-4-INVALID_COS_CONFIGURATION
%UBR10000-4-INVALID_COS_CONFIGURATION: <133>CMTS[DOCSIS]:<73010900> Bad Class of Service - Invalid Configuration. CM Mac Address [enet]

Explanation    The CMTS rejected the cable modem's registration request (REG-REQ) because it presented a bad class of service (CoS) in its configuration file.

Recommended Action    Check the DOCSIS configuration file that this cable modem is using and correct any errors. Reboot the cable modem. If the problem persists, it could indicate a possible theft-of-service attack by someone using a modified configuration file.

%UBR7100-3-INVALID_INVOKE_FROM_ISR
%UBR7200-3-INVALID_INVOKE_FROM_ISR
%UBR10000-3-INVALID_INVOKE_FROM_ISR: Invalid [chars] from interrupt level [decimal]

Explanation    An invalid operation has occurred from the ISR context with a possible recurrence of CSCek63728.

Recommended Action    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.

%UBR7100-4-INVALID_MAX_DOWNSTREAM_BIT_FORMAT
%UBR7200-4-INVALID_MAX_DOWNSTREAM_BIT_FORMAT
%UBR10000-4-INVALID_MAX_DOWNSTREAM_BIT_FORMAT: <133>CMTS[DOCSIS]:<73011200> Bad Max DS bit - Invalid format. CM Mac Addr [enet]

Explanation    The CMTS rejected the cable modem's registration request (REG-REQ) because it presented an invalid maximum downstream bitrate value.

Recommended Action    Check the DOCSIS configuration file that this cable modem is using and correct any errors. Reboot the cable modem.

%UBR7100-4-INVALID_MAX_UPSTREAM_BIT_FORMAT 
%UBR7200-4-INVALID_MAX_UPSTREAM_BIT_FORMAT
%UBR10000-4-INVALID_MAX_UPSTREAM_BIT_FORMAT: <133>CMTS[DOCSIS]:<73011300> Bad Max US Bit - Invalid format. CM Mac Addr <[enet]>

Explanation    The CMTS rejected the cable modem's registration request (REG-REQ) because its maximum upstream bitrate is not in the proper format.

Recommended Action    Check the DOCSIS configuration file that this cable modem is using and correct any errors. Reboot the cable modem. If the problem persists, it could indicate a possible theft-of-service attack by someone using a modified configuration file.

%UBR7100-4-INVALID_MAX_UPSTREAM_BURST_FORMAT
%UBR7200-4-INVALID_MAX_UPSTREAM_BURST_FORMAT
%UBR10000-4-INVALID_MAX_UPSTREAM_BURST_FORMAT: <133>CMTS[DOCSIS]:<73011600> Bad Max US CH Transmit Burst Configuration setting - Invalid format. CM Mac Addr [enet]

Explanation    The CMTS rejected the cable modem's registration request (REG-REQ) because it presented an invalid value for the maximum upstream channel transmit burst field.

Recommended Action    Check the DOCSIS configuration file that this cable modem is using and correct any errors. Reboot the cable modem. If the problem persists, it could indicate a possible theft-of-service attack by someone using a modified configuration file.

%UBR7100-4-INVALID_MIN_UPSTREAM_CHANNEL_BIT_RATE_FORMAT
%UBR7200-4-INVALID_MIN_UPSTREAM_CHANNEL_BIT_RATE_FORMAT
%UBR10000-4-INVALID_MIN_UPSTREAM_CHANNEL_BIT_RATE_FORMAT: <133>CMTS[DOCSIS]<73011501> Bad Guaranteed MIN US Channel bit Rate Configuration setting - Invalid format. CM Mac Addr [enet]

Explanation    The CMTS rejected the cable modem's registration request (REG-REQ) because it presented an invalid value for the guaranteed minimum upstream channel bitrate field.

Recommended Action    Check the DOCSIS configuration file that this cable modem is using and correct any errors. Reboot the cable modem. If the problem persists, it could indicate a possible theft-of-service attack by someone using a modified configuration file.

%UBR7100-4-INVALID_MODEM_CONFIGURATION_SETTING_FORMAT
%UBR7200-4-INVALID_MODEM_CONFIGURATION_SETTING_FORMAT
%UBR10000-4-INVALID_MODEM_CONFIGURATION_SETTING_FORMAT: <133>CMTS[DOCSIS]:<73011700> Invalid Modem Capabilities configuration setting. CM Mac Addr [enet]

Explanation    The CMTS rejected the cable modem's registration request (REG-REQ) with a confirmation code of reject-invalid-modem-capabilities(207) because it presented an invalid value for the capabilities field.

Recommended Action    Check the DOCSIS configuration file that this cable modem is using and correct any errors. In particular, look for an invalid combination of modem capabilities, or capabilities that are inconsistent with the services requested in the REG-REQ message. Reboot the cable modem.

%UBR7100-3-INVALIDSID
%UBR7200-3-INVALIDSID
%UBR10000-3-INVALIDSID: [chars]: Invalid sid [dec] for mac address [enet]

Explanation    The indicated cable modem is using an invalid SID.

Recommended Action    Check for possible IP address spoofing. Reboot this cable modem.

%UBR7100-3-INVALIDSIDPOSITION 
%UBR7200-3-INVALIDSIDPOSITION
%UBR10000-3-INVALIDSIDPOSITION: Invalid SID ([dec]) position for interface [chars]: CM [enet]: Is used by CM [enet] SFID [dec] SID [dec]. SID container info: start [dec] end [dec]

Explanation    The cable interface could not assign the new Service ID (SID) because it is already in use. This typically indicates a software error, in which a cable interface had old SID information that was not completely cleaned out before. This might happen during an HCCP switchover when the router was unable to completely synchronize the two cable interface line cards before the switchover occurred.

Recommended Action    The cable interface probably has run out of available resources or has reached its maximum SID allocation of 8191 SIDs. Assign new cable modems to other cable interfaces.

%UBR7100-4-INVALID_SID
%UBR7200-4-INVALID_SID
%UBR10000-4-INVALID_SID: <133>CMTS[DOCSIS]:<73010200> REG REQ has Invalid SID or not in use. CM Mac Addr [enet]

Explanation    The specified cable modem sent a registration request (REG-REQ) message with a SID that is either out of range or that the CMTS has not yet issued.

Recommended Action    Check the DOCSIS configuration file that this cable modem is using and correct any errors. Reboot the cable modem.

%UBR10000-4-INVALID_UNASSIGNED_UPSTREAM_CHANNEL: <133>CMTS[DOCSIS]:<73010600> 
Bad US CH - Invalid or Unassigned. CM Mac Addr [enet]

Explanation    A REG-REQ is rejected because the upstream channel is either invalid or unassigned.

Recommended Action    Check the upstream channel frequency.

%UBR7100-4-INVALID_UPSTREAM_PRIORITY_FORMAT
%UBR7200-4-INVALID_UPSTREAM_PRIORITY_FORMAT
%UBR10000-4-INVALID_UPSTREAM_PRIORITY_FORMAT: <133>CMTS[DOCSIS]:<73011400> Bad US Priority Configuration - Invalid format. CM Mac Addr [enet]

Explanation    The CMTS rejected the cable modem's registration request (REG-REQ) because it presented an invalid value for the upstream priority field.

Recommended Action    Check the DOCSIS configuration file that this cable modem is using and correct any errors. Reboot the cable modem.

%UBR7200-3-IONOTSUPPORTEDBYLOADER: I/O Controller (type [dec]) is not supported 
by this boot loader. The I/O Controller network interfaces will be unavailable. 

Explanation    The I/O controller specified is not supported by the boot loader and therefore, the network interfaces cannot be used during the boot.

Recommended Action    If a specified I/O Controller support is needed in the boot loader, you may need an enhanced boot image (-kboot-) or need to configure your router to use a full image as the boot loader.

%UBR7100-3-IPV6SOCKETFAIL 
%UBR7200-3-IPV6SOCKETFAIL
%UBR10000-3-IPV6SOCKETFAIL: IPv6 TFTP server socket

Explanation    The CMTS router could not open the IPv6 TFTP server socket.

Recommended Action    Make sure that the ip tftp-server command is not configured in the CMTS.

%UBR7100-5-KEEPALIVE 
%UBR7200-5-KEEPALIVE
%UBR10000-5-KEEPALIVE: Keepalive shutting down interface [chars].

Explanation    No activity detected within the Keepalive time-out period on the interface.

Recommended Action    Check the RF path for noise or other failure.

%UBR7100-3-KEY_REJECT_NO_INFORMATION
%UBR7200-3-KEY_REJECT_NO_INFORMATION
%UBR10000-3-KEY_REJECT_NO_INFORMATION: <132>CMTS[DOCSIS]:<66050102> Key Reject No Information, CM Mac Address [enet]

Explanation    The CMTS rejected the cable modem's attempt to register for BPI or BPI+ encryption.

Recommended Action    Check the key configuration on the CMTS and cable modem.

%UBR7100-3-KEY_REJECT_UNAUTHORIZED_SAID
%UBR7200-3-KEY_REJECT_UNAUTHORIZED_SAID
%UBR10000-3-KEY_REJECT_UNAUTHORIZED_SAID: <132>CMTS[DOCSIS]:<66050103> Key Reject Unauthorized SAID. CM Mac Addr [enet]

Explanation    The CMTS rejected the cable modem's attempt to register for BPI or BPI+ encryption because the CM presented an unauthorized Security Authorization ID (SAID).

Recommended Action    Check the BPI configuration on the CMTS and cable modem.

%UBR7200-3-L2VPNNOTSUPPORTED: L2 VPN ATM-VC mapping not currently supported on 
mc28u cards. CM MAC %e. 

Explanation    The Cisco uBR-MC28U/X cable interface line card does not support the Transparent LAN Service over Cable feature (which is enabled using the cable l2-vpn-service atm-vc command), but the cable vc-map command has been used to map traffic from a cable modem that is using the Cisco uBR-MC28U/X card.

Recommended Action    Disable the Transparent LAN Service over Cable feature for the specified cable modem that is using the Cisco uBR-MC28U/X card, using the no cable vc-map command. If a later Cisco IOS Release is available for the Cisco uBR7246VXR router, check to see if this restriction has been removed, and if so, upgrade the Cisco IOS software on the router.

%UBR7100-3-LB_IF_DISABLED
%UBR7200-3-LB_IF_DISABLED
%UBR10000-3-LB_IF_DISABLED: Disabled interface [chars]

Explanation    The CMTS load-balancing subsystem disabled the indicated cable interface, because it could not move cable modems either to it or from it.

Recommended Action    Verify that the interface is connected and passing traffic. Also look for any possible RF noise problems. Check the cable load-balance group configuration to ensure that the interface's load-balance group contains only those interfaces that are combined in the same node and share the same physical connectivity (which is required when interfaces are part the same load-balance group).

%UBR7100-4-LB_MODEM_FAILED
%UBR7200-4-LB_MODEM_FAILED
%UBR10000-4-LB_MODEM_FAILED: Failed to move modem [enet] from [chars] to [chars].

Explanation    The CMTS was trying to load-balance the two indicated interfaces, but was unable to move the specified cable modem from its current interface to the new interface after five attempts.

Recommended Action    Verify that both interfaces are connected and passing traffic. Also look for any possible RF noise problems. Check the cable load-balance group configuration to ensure that the two downstreams or upstreams are combined in the same node and share the same physical connectivity (which is required when interfaces are part the same load-balance group).

%UBR7100-6-LIST_ERR
%UBR7200-6-LIST_ERR: [chars] [dec]

Explanation    This is informational only.

Recommended Action    No action is needed.

%UBR7100-6-LOS
%UBR7200-6-LOS
%UBR10000-6-LOS: Cable clock [chars] reference Loss of Signal

Explanation    The clock reference was lost.

Recommended Action    Check the reference source.

%UBR7200-0-LOWPOWERCPU: uBR requires CPU card type NPE150 or higher 

Explanation    The NPE-100 processor is not supported for the Cisco uBR7200 series router.

Recommended Action    Upgrade the CPU card to an NPE150 or higher processor.

%UBR7100-3-MACADDRERR 
%UBR7200-3-MACADDRERR
%UBR10000-3-MACADDRERR: DHCP Msg with non unicast MAC address. Master Interface [chars] Input Interface [chars] SID = [dec] MAC = [enet]

Explanation    An internal software error may have occurred.


Note In one case, this system message is not derived from a software error. Any broadcast address, multicast address or zero MAC source address triggers such messages to reflect an error in the DHCP packet received. A hexadecimal SID value of all Fs is shown when the Cisco CMTS is unable to map a MAC address to a particular cable modem. There is no software error in this case.


Recommended Action    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:

%UBR7100-4-MACBLKSIZE
%UBR7200-4-MACBLKSIZE
%UBR10000-4-MACBLKSIZE: Unknown MAC address block size.

Explanation    The data stored in the midplane is bad or incomplete.

Recommended Action    Contact your Cisco technical support representative to update your system.

%UBR10000-4-MCAST_DB_MAX_LIMIT_REACHED: Multicast DB full, new entry not created. 

Explanation    The CMTS currently only supports up to 5000 multicast replications (source, group, forwarding interface) globally. This message is to notify user that the 5000 limit has reached and it will no longer accept new replication. This will not affect existing subscribers or replications.

Recommended Action    The CMTS will again accept new replications once the count drops below the 5000 limit (for example, when subscriber removes replications).

%UBR7100-6-MACCLTCLR: Enable mac mgmt msg processing on [chars] 
%UBR7200-6-MACCLTCLR: Enable mac mgmt msg processing on [chars]
%UBR10000-6-MACCLTCLR: Enable mac mgmt msg processing on [chars]

Explanation    The Cisco CMTS suspends the sending of DOCSIS MAC-layer messages on a cable interface when it begins an N+1 (1:n) switchover to prevent the possible loss or duplication of these messages and their responses during the switchover process. After the switchover, the processor reenables the sending of the DOCSIS MAC-layer messages on the interface to resume normal operations.

Recommended Action    No action is needed. In software releases prior to Cisco IOS Release 12.2(15)BC2, this message could appear for slots without an installed line card, or for cable interface line cards that do not have any cable modems that are currently online. If so, this message can be ignored, or you can upgrade the Cisco CMTS to Cisco IOS Release 12.2(15)BC2 or later release.

%UBR7100-3-MANUFACTURE_CA_CM_CERTIFICATE_FORMAT_ERROR
%UBR7200-3-MANUFACTURE_CA_CM_CERTIFICATE_FORMAT_ERROR
%UBR10000-3-MANUFACTURE_CA_CM_CERTIFICATE_FORMAT_ERROR: <133>CMTS[DOCSIS]: Manufacture CA Certificate Format Error

Explanation    The cable modem attempted to register with an invalid manufacturer's digital certificate. The certificate could contain an invalid signature, or the current date and time are outside of the certificate's valid operating range.

Recommended Action    Use the show clock on the CMTS to verify that the date and time on the CMTS are set correctly. If the date and time are not correct, and if you are using an Network Time Protocol (NTP) or Simple Network Time Protocol (SNTP) time-of-day server, verify that the server is operational and reachable. If you are not using a time-of-day server, use the clock set command to set it to the current date and time, and then use the clock update-calendar command to update the internal clock. If the CMTS clock is correct, check that the cable modem contains a valid manufacturer's certificate. If necessary, upgrade the cable modem's software and reboot the cable modem.

%UBR7100-3-MAP_REJECT_DS_TRAFFIC_FLOW_NOT_MAPPED
%UBR7200-3-MAP_REJECT_DS_TRAFFIC_FLOW_NOT_MAPPED
%UBR10000-3-MAP_REJECT_DS_TRAFFIC_FLOW_NOT_MAPPED: <132>CMTS[DOCSIS]:<66060510> Map Reject - Downstream traffic flow not mapped to BPI+SAID, CM Mac Addr [enet]

Explanation    The CMTS rejected a MAP request from a cable modem because its downstream service flow is not mapped to an existing SAID, as required for BPI+ encryption.

Recommended Action    If the problem persists, reboot the cable modem and check the cable modem for possible hardware or software problems.

%UBR7100-3-MAP_REJECT_NOT_AUTH_DS_TRAFFIC
%UBR7200-3-MAP_REJECT_NOT_AUTH_DS_TRAFFIC
%UBR10000-3-MAP_REJECT_NOT_AUTH_DS_TRAFFIC: <132>CMTS[DOCSIS]:<66060509> Map Reject - Not Authorized for requested downstream traffic flow. CM Mac Addr [enet]

Explanation    The CMTS rejected a MAP request from a cable modem because it is not authorized for the requested downstream service flow.

Recommended Action    Reboot the cable modem. If the problem persists, check for a possible theft-of-service attack.

%UBR7100-6-MAP_UPSTREAM_BW_ALLOCATION
%UBR7200-6-MAP_UPSTREAM_BW_ALLOCATION
%UBR10000-6-MAP_UPSTREAM_BW_ALLOCATION: A transmit opportunity was missed because MAP arrived too late

Explanation    A cable modem missed an opportunity to transmit on the upstream because its bandwidth request MAC message arrived too late.

Recommended Action    This problem is expected to occur occasionally in normal networks. If the problem persists with a particular cable modem, reboot the cable modem, and check for possible hardware or software problems with that cable modem. If this problem occurs with many cable modems, check the cable plant for RF transmission and noise ingress problems.

%RADIAN-5-PE_INTR_MSG %UBR7100-3-MAPPED_TO_EXISTING_SAID
%UBR7200-3-MAPPED_TO_EXISTING_SAID
%UBR10000-3-MAPPED_TO_EXISTING_SAID: <132>CMTS[DOCSIS]:<66060600> Mapped to existing SAID, CM Mac Addr [enet]

Explanation    A cable modem is joining a multicast group that is already encrypted using a multicast Security Association ID (SAID).

Recommended Action    No action is required. This message is expected and indicates that there are multiple multicast receivers for this multicast stream.

%UBR10000-3-MAPPED_TO_NEW_SAID: <132>CMTS[DOCSIS]:<66060700> Mapped to new SAID.  
CM Mac Addr [enet]

Explanation    A cable modem is joining a multicast group that is newly mapped to a multicast SAID.

Recommended Action    No action is required. This message is expected and indicates that there is a multicast receiver for this new multicast stream.

%UBR7100-6-MAXBUSRTADJUST
%UBR7200-6-MAXBUSRTADJUST
%UBR10000-6-MAXBUSRTADJUST: [char] burst's maximum burst size in mod profile [dec] is adjusted to [dec] mini-slots.

Explanation    The guard burst size for the specified modulation profile on the indicated interface has been changed to the specified value.

Recommended Action    No action is needed.

%UBR7100-3-MAX_DS_SF_ERROR
%UBR7200-3-MAX_DS_SF_ERROR
%UBR10000-3-MAX_DS_SF_ERROR: Maximum limit for downstream service-flows reached.

Explanation    The total number of downstream Service Flows cannot exceed 50.

Recommended Action    No action is needed.

%UBR7100-5-MAXHOST
%UBR7200-5-MAXHOST
%UBR10000-5-MAXHOST: Interface [chars], New host with IP address [IP_address] and MAC [enet] on SID [dec] (CM [enet]) is ignored.

Explanation    The maximum number of devices that can be attached to the specified cable modem has been exceeded. Therefore, the device with the specified IP address will not be allowed to come online.

Recommended Action    No action is needed. If the problem persists, contact the user of this particular cable modem and inform them of the maximum number of hosts for their cable modem.


Tip This condition can occur, even when the "Number of CPE IPs" field displayed by the show cable modem mac-address verbose command indicates that the maximum number of hosts has not yet been reached. This can occur if one or more hosts has an IP address that is not yet known to the Cisco CMTS router.


%UBR7100-4-MIN_UPSTREAM_CHANNEL_BIT_RATE_EXCEEDS_MAX
%UBR7200-4-MIN_UPSTREAM_CHANNEL_BIT_RATE_EXCEEDS_MAX
%UBR10000-4-MIN_UPSTREAM_CHANNEL_BIT_RATE_EXCEEDS_MAX: <133>CMTS[DOCSIS]:<73011501> Bad Guaranteed Min US Channel Bit Rate Configuration setting - Exceed Max US Bit Rate. CM Mac Addr [enet]

Explanation    The CMTS rejected the cable modem's registration request because its guaranteed minimum upstream channel bitrate field is greater than the maximum upstream bitrate field.

Recommended Action    Check the DOCSIS configuration file that this cable modem is using and correct any errors. Reboot the cable modem. If the problem persists, it could indicate a possible theft-of-service attack by someone using a modified configuration file.

%UBR10000-4-MIN_UPSTREAM_CHANNEL_BITRATE_OUT_OF_RANGE: 
<133>CMTS[DOCSIS]:<73011502> Bad Guaranteed Min US CH Bit rate Configuration 
setting - Out of Range. CM Mac Addr [enet]

Explanation    A REG-REQ is rejected because the minimum upstream channel bitrate has been set out of range.

Recommended Action    Check the parameters in the router configuration file.

%UBR7100-3-MISSING_BP_CONFIGURATION_SETTING_TLV
%UBR7200-3-MISSING_BP_CONFIGURATION_SETTING_TLV
%UBR10000-3-MISSING_BP_CONFIGURATION_SETTING_TLV: <132>CMTS[DOCSIS]:<66010100> Missing BP Configuration Setting TLV, TLV Type [enet]

Explanation    The cable modem did not include the BPI or BPI+ field in its registration request.

Recommended Action    Check the DOCSIS configuration file that this cable modem is using and correct any errors. Reboot the cable modem. If the problem persists, it could indicate a problem with this particular cable modem, or a possible theft-of-service attack by someone using a modified configuration file.

%UBR7100-3-MONITOR 
%UBR7200-3-MONITOR
%UBR10000-3-MONITOR: Interface [chars], Failed to send monitored packets

Explanation    An internal software error occurred.

Recommended Action    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.

%UBR7100-3-MONITOR_ACCESS_FILTER 
%UBR7200-3-MONITOR_ACCESS_FILTER
%UBR10000-3-MONITOR_ACCESS_FILTER: Null access list

Explanation    An internal software error occurred.

Recommended Action    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.

%UBR7100-3-MONITOR_EMPTY 
%UBR7200-3-MONITOR_EMPTY
%UBR10000-3-MONITOR_EMPTY: Unable to allocate packet with rx_type = [dec]

Explanation    An internal software error occurred.

Recommended Action    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.

%UBR7100-3-NEG_PENDING
%UBR7200-3-NEG_PENDING
%UBR10000-3-NEG_PENDING: NEGATIVE DECREMENT OF PENDING STATS

Explanation    An internal software 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://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs). 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.

%UBR7100-4-NOCFGFILE
%UBR7200-4-NOCFGFILE
%UBR10000-4-NOCFGFILE: Cannot read modem config file [chars] from [integer]: [chars]

Explanation    The CMTS could not obtain the DOCSIS configuration file for this cable modem from the TFTP server. This message will occur when the dynamic secret feature is enabled on the cable interface with the cable dynamic-secret command.

Recommended Action    Verify that the CMTS has network connectivity with the TFTP server, and that the specified DOCSIS configuration file is available on the TFTP server. Check that the DHCP server is correctly configured to send the proper configuration filename in its DHCP response to the cable modem. Also verify that the DOCSIS configuration file is correctly formatted.

This problem could also occur if the TFTP server is offline or is overloaded to the point where it cannot respond promptly to new requests. It might also be seen if the interface between the CMTS and TFTP server is not correctly configured and flaps excessively.


Note This error indicates a problem with the provisioning system outside of the Cisco CMTS. Disabling the Dynamic Shared Secret feature will not clear the fault, nor will it allow cable modems to come online. You must first correct the problem with the pro