Table Of Contents
Cisco CMTS Router System Messages
UBR7100, UBR7200, and UBR10000
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
•
•
•
•
•
•
•
•
•
•
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 firstExplanation 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 ARP error messages.
%ARP-3-ARPINVALIDEENTRY : ARP system internal error. Returns NULL arp entry on nodeUnrecognized format ` %p'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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
C10K_IEDGE
The following are Cisco 10000 iEdge messages.
%C10K_IEDGE-5-IEDGE_POLICY_WRITE_FAIL : Could not write iEdge_policy [chars] into pxfExplanation This event occurred during microcode reload writing the iEdge policy to the PXF failed. The sessions using this policy may be affected.
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. 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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
CFIB
The following are Constellation Forward Information Base (FIB) messages.
%CFIB-3-CFIB_UNEXPECTED : Unexpected CFIB conditionExplanation An error occurred where an unexpected condition was observed in the Constellation FIB code.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
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 APIExplanation A checkpoint client has attempted 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-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. Reload the microcode on the affected line cards. 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.
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 recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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 reloadedExplanation 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 mismatchExplanation 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 recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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 recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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 recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
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 Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl). Also perform a search of the Bug Toolkit (http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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-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, board the RMA.
%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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-6-LICENSE_ENFORCE : Linecard [int]/[int] set to mode [chars]
Explanation License information is applied.
Recommended Action No action is needed.
%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 of the CLC and check the LED.
%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-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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CMTS_LIC-3-NULL_LICENSE_INFO : Line Card [int]/[int] license info is NULL!
Explanation An unexpected NULL pointer has occurred.
Recommended Action Check the line card license details.
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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CR10K_DIAG-5-RU_OLDBUFF_HOLD : IO-Buff-Hoard Monitor: [chars]
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
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 processExplanation 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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
ETSEC
The following are ETSEC controller messages.
%ETSEC-2-EXCEPTION : Fatal Error, Interface [chars] not transmitting
Explanation The software detected critical error and recovery failed, resulting in a system crash.
Recommended Action Collect the crashinfo files, system logs and console messages.
%ETSEC-3-RECOVER_TX : Interface [chars] TX workaround invokedExplanation 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.
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.
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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
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-BADINTERPKT: Received an unexpected pkt in [chars] SYNC_QExplanation The HCCP Cisco uBR10012 received a packet meant for a Cisco uBR7200 or cable line card.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl). Also perform a search of the Bug Toolkit (http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-NOINTFC: No interfaces available for IP connection.Explanation The HCCP protocol requires an out-of-band path for its inter-router communication, using an interface that is not part of a HCCP group.
Recommended Action Create a path between the two routers that is not part of the HCCP group. Typically, this should be a direct connection, but could also be accomplished by using a routed network connection.
%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-3-SNMPFAIL: Grp [dec] [chars]: failed to initialize SNMP.Explanation The indicated member of the specified group failed to initialize the SNMP subsystem and create an SNMP message.
Recommended Action Verify that the SNMP configuration on the CMTS is correct. 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-BADPATYPE: Grp [dec] Mbr [dec] [chars]: peer is not identical.Explanation The indicated member of the specified group has detected that the Working and Protect interfaces are not identical cards. Identical hardware must be used for the Working and Protect cards, otherwise a problem might happen, depending on the circumstances. For example, a Cisco uBR-MC16S card can be protected by a Cisco uBR-MC16C card, but only if the Cisco uBR-MC16S card is not using any advanced spectrum management features (which are not supported on the Cisco uBR-MC16C).
Recommended Action Verify that the Working and Protect interfaces are using identical hardware.
%HCCP-4-BADVER: Grp [dec] Mbr [dec] [chars]: bad version [chars] detected.Explanation The indicated member of the specified group has detected an invalid HCCP version number. This could indicate a mismatch between the Cisco IOS software that is running on the processor card and the interface cards.
Recommended Action Reset the interface, or perform an OIR of the Working and Protect cards to ensure that they are using the proper version of the Cisco IOS software. 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-NOSUBIF: Grp [dec] [dec] [chars]: [chars].[dec] is not found.Explanation The indicated member of the specified group has detected that the Protect interface is not configured with the same sub-interfaces as the Protect interface.
Recommended Action Reconfigure the Protect interface so that it has a matching sub-interface configuration with the Working interface.
%HCCP-4-PEER_CRASH: Received crash notification from [dec]Explanation The peer router has sent a sync message indicating that it has crashed. Any working interfaces on that router that have been configured with protect interfaces on another router are being switched over.
Recommended Action Determine the cause of the peer router's crash.
%HCCP-4-STATICSYNC_FAILURE: HCCP [dec] [chars]: Aborting Static Sync because [chars].Explanation The HCCP static synchronization failed because of errors during the synchronization process.
Recommended Action Enter hccp resync in the command line interface.
%HCCP-5-ACTIVE: Grp [dec] Mbr [dec] [chars]: change state from standby to active: [chars]Explanation The indicated member of the specified HCCP group has changed its state from standby to active because it received the indicated message.
Recommended Action No action is needed (except to verify that connectivity has been preserved).
%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 connectivity has been preserved).
%HCCP-5-FAILURE: Grp [dec] Mbr [dec] [chars]: received failure notice-[chars].Explanation The indicated member of the specified group has been notified that the indicated failure or switchover has occurred.
Recommended Action Check the source of the failure to determine the cause. Check the console log for other system error messages that might identify the source problem.
%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-NOSWITCHOVER: Grp [dec] Mbr [dec] [chars]: ignored switchover or failover notice.Explanation The indicated member of the specified group has ignored a switchover notice because it either has no knowledge of the indicated peer, or because a switchover has just occurred and other switchovers are ignored until after the system has stabilized during the wait-to-restore period.
Recommended Action No action is needed, except that if this occurred during a switchover, you might want to check the channel switch for a possible channel failure.
%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-STATICSYNC: Grp [dec] Mbr [dec] [chars]: receiving static sync.Explanation The indicated member of the specified group has received a RESYNC message and is starting to receive static SYNC messages.
Recommended Action No action is needed (except to verify that connectivity has been preserved).
%HCCP-5-SWITCHOVER: Grp [dec] Mbr [dec] [chars]: switching over.Explanation The indicated member of the specified group is switching over with its peer.
Recommended Action No action is required, except to investigate why the switchover is occurring.
%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-5-SWITCHREQ: Grp [dec] Mbr [dec] [chars]: requested switchover, retry [dec].Explanation The indicated member of the specified group is sending a switchover request.
Recommended Action No action is required, except to investigate why the switchover is occurring.
%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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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-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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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.
HQF
This section describes error messages generated for the Hierarchal Queuing Framework (HQF) Toaster Mapper.
%HQF_MAP_TT-3-EREVENT: [chars]-MSG_TRACEBACKExplanation 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:
–
–
%HQF_MAP_TT-3-HQF: [chars]-MSG_TRACEBACKExplanation 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:
–
–
%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 ATM VPs or MLPoA links, 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_FASTExplanation 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 FailureExplanation 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:
–
–
%MCE_HQF_NP_CLIENT-3-ALLEXISTS: [chars]-NP Client Previously Defined Software ElementExplanation 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:
–
–
%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:
–
–
%MCE_HQF_NP_CLIENT-3-HQF_NP_CLIENT_GENERAL: [chars]-MSG_TRACEBACK-error detectedExplanation 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:
–
–
%MCE_HQF_NP_CLIENT-3-INITFAIL: [chars]-NP Client Initialization FailedExplanation 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:
–
–
%MCE_HQF_NP_CLIENT-3-MAXEXCEED: [chars]-NP Client Max Services ExceededExplanation 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:
–
–
%MCE_HQF_NP_CLIENT-3-METADATA: [chars]-failedExplanation 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:
–
–
%MCE_HQF_NP_CLIENT-3-NOMEM: [chars]-Memory Allocation FailureExplanation 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:
–
–
%MCE_HQF_NP_CLIENT-3-NOTFOUND: [chars]-NP Client Software Element Not FoundExplanation 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:
–
–
%MCE_HQF_NP_CLIENT-3-NOTSUP: [chars]-NP Client Feature Not SupportedExplanation 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:
–
–
%MCE_HQF_NP_CLIENT-3-NPUNKNOWN: [chars]-NP Client Unsupported NPExplanation 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:
–
–
IFDAMP
The following are Interface Dampening messages.
%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.
IOS_LICENSE
The following are IOS License messages.
%IOS_LICENSE-3-FAILED : [chars]
Explanation The IOS licensing subsystem failed to watch request from the remote show subsys license commands.
Recommended Action Capture the error message and forward it to the appropriate licensing component.
%IOS_LICENSE-3-IPC_FAILED : [chars] failed with an error = [chars]
Explanation The IPC calls in the IOS licensing subsystem failed.
Recommended Action Capture the error message and forward it to the appropriate licensing component.
%IOS_LICENSE-2-NO_LICENSE : No valid license available to run any feature
Explanation The IOS licensing subsystem could not get a valid license to run any feature on the router.
Recommended Action Run the show license command to view the list of available feature in the 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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOS_LICENSE-2-NO_MEM : No memory available for [chars]
Explanation The IOS licensing subsystem could not obtain the required memory it needed.
Recommended Action If this error message recurs, attempt to reduce memory usage by reducing the number of router features, or interfaces, enabled. Alternatively, add more memory.
To display total memory usage for a router enter show memory summary at the privileged command line prompt. To display buffer usage enter show buffers at the prompt.%IOS_LICENSE-3-RTTYS_FAILED : [chars] failed
Explanation The RTTYS calls in the IOS licensing subsystem failed.
Recommended Action Capture the error message and forward it to the appropriate licensing component.
%IOS_LICENSE-3-UNKNOWN_MSG_TYPE : an unknown message type was received, dropping it, msg_type = [dec]
Explanation IOS licensing subsystem received an unknown message type which it does not recognizes or support.
Recommended Action Capture the error message and forward it to the appropriate licensing component.
IOS_LICENSE_IMAGE_APPLICATION
The following are IOS License Image Application messages.
%IOS_LICENSE_IMAGE_APPLICATION-3-FAILED : [chars]
Explanation The IOS licensing subsystem failed.
Recommended Action Capture the error message and forward it to the appropriate licensing component.
%IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_CONFIG : EULA must be accepted for license level = [chars]
Explanation Reissue the command from an interactive terminal.
Recommended Action No action is required.
%IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL : Module name = [chars] Next reboot level = [chars] and License = [chars]
Explanation This is an informational message to display the change in the next reboot license level.
Recommended Action No action is required.
%IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL_CONFIG : Please issue 'license boot' config command to make extension license ([chars]) available for use.
Explanation This is an informational message that indicates that to make extension license available to support image level, licensing image level needs to be configured.
Recommended Action No action is required.
%IOS_LICENSE_IMAGE_APPLICATION-6-NO_LICENSE : [chars] [chars].
Explanation There is no valid license available on the Cisco uBR10012 router.
Recommended Action If this message recurs, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOS_LICENSE_IMAGE_APPLICATION-3-UNKNOWN_EVENT : [chars]
Explanation The IOS image licensing subsystem received an event which it does not understand or recognize.
Recommended Action Capture the error message and forward it to the appropriate licensing component.
%IOS_LICENSE_IMAGE_APPLICATION-3-UNKNOWN_VERSION: [chars]
Explanation The IOS image licensing subsystem received an event for an unknown version of a feature.
Recommended Action Capture the error message and forward it to the appropriate licensing component.
IP
This section describes error messages generated for the Internet Protocol (IP).
%IP-3-NOOUTINTF: Output interface not available. source address: [IP_address], destination address: [IP_address], routing type: %uExplanation 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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.
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-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:
–
–
–
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-3-CARDERR: [chars]Explanation This message indicates an IPC card has registered itself to the IPC master twice. The card malfunctioned and its IPC is not active.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl). Also perform a search of the Bug Toolkit (http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.
%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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPCGRP-3-CREATE_FAIL: [chars] [chars]Explanation The IPC port creation on the route processor (RP) card has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl). Also perform a search of the Bug Toolkit (http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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 bufferExplanation 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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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-3-EXECCMDMSG: Incorrect msg size (size=[integer])Explanation The size of the REXEC-On IPC message is wrong.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl). Also perform a search of the Bug Toolkit (http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or 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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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-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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-3-NULLMSG: Null [chars] ipc messageExplanation An empty IPC message is received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl). Also perform a search of the Bug Toolkit (http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPCGRP-3-NULLREXECCMD: Received empty ipc rexec cmd messageExplanation The REXEC-On IPC command has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl). Also perform a search of the Bug Toolkit (http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or 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-REXEC: [chars]Explanation The REXEC-On IPC command has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl). Also perform a search of the Bug Toolkit (http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.
%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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.
%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.
%IPCMON-3-PROFCRASH: IPC keepalive not received for at least [dec] seconds, forcing crash
Explanation An IPC keepalive message was not received for a predetermined amount of time.
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. 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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPCMON-6-PROFHDR: IPC Keepalive not received for [dec] seconds
Explanation CPU profiling header.
Recommended Action No action is required.
%IPCMON-6-PROFINTLEV: Int Level:[chars]
Explanation CPU interrupt level profiling data.
Recommended Action No action is required.
%IPCMON-6-PROFLASTPC: Last PC:[chars]
Explanation CPU last PC profiling data.
Recommended Action No action is required.
%IPCMON-6-PROFSTART: IPC Keepalive not received, CPU profiling started
Explanation IPC keepalive messages stopped being received.
Recommended Action No action is required.
%IPCMON-6-PROFSTOP: IPC Keepalive received, CPU profiling stopped
Explanation An IPC keepalive message was received. CPU profiling has been stopped.
Recommended Action No action is required.
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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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 IDPROMExplanation 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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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 missingExplanation 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] secExplanation 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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center online (http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl), 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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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 failedExplanation 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] rejectedExplanation 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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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 nullExplanation 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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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] failedExplanation 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.
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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
MCU, MCUCLC, MCUFSM
The following system error messages concern the operation of the Cisco uBR-MC16U/X and Cisco uBR-MC28U/X cable interface line cards.
•
•
•
MCU
%MCU-1-CONFIGNOTETHER: Cannot configure any of the IPC ethernet interfacesExplanation 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 bayExplanation 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-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-6-HWREV: Slot [dec]: HW revision is [dec]Explanation An informational message that displays the current hardware revision for the Cisco uBR-MC16U/X or Cisco uBR-MC28U/X cable interface line card.
Recommended Action No action is needed.
%MCU-6-OLDHWREV: Slot [dec]: HW revision is below 1.8 - board should be upgradedExplanation The Cisco uBR-MC16U/X or Cisco uBR-MC28U/X cable interface line card in the indicated slot has a pre-release hardware revision. The card must be at hardware revision 1.8 or above to be able to run current Cisco IOS software.
Recommended Action Contact your Cisco technical support representative to arrange for the Cisco uBR-MC28U/X card to be upgraded to the proper hardware revision.
%MCU-5-RESET: MCU port adapter was in slot [dec] was resetExplanation 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 network processing engine (NPE) PCI data interface has been enabled or disabled, as indicated.
Recommended Action No action is needed.
%MCUCLC-3-PCIANALYZE: PCI device ([dec]) initialization failedExplanation 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-1-CARD_LOADING: Card in slot ([dec]) booting: [chars], size [dec] bytes, version [hex], checksum [hex]Explanation The indicated cable interface line card is loading and booting the indicated microcode software image. This typically should happen only during system initialization and during OIR of 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-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 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 processExplanation 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.
MLSCEF
MLS hardware error messages:
%MLSCEF-2-FIB_TCAM_WRITE_INCONSISTENCY : FIB TCAM Mismatch for [chars]: Index: [dec]
Expected: Entry: [hex]-[hex]-[hex]
Hardware: Entry: [hex]-[hex]-[hex]
Explanation Possible problem in writing to the specified FIB TCAM entry.
Recommended Action Collect show mls cef hardware and show mls cef log and show ver command outputs.
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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
%NICKEL10G-3-N10GERRS: [chars]
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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
PXF_QOS
The following are Parallel eXpress Forwarding (PXF) Quality of Service (QoS)-related messages.
%PXF_QOS-3-WS_QOS_L2C_TOO_MANY_L2_LKP_TBLS : Too many possible PXF QoS layer 2 lookup tables.(reached [int] tables). Can not add more.PXF QoS layer 2 classification will not function correctly.Explanation PXF QoS Layer 2 Classification: the resulted PXF QoS layer 2 lookup tables exceeds system limitation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
SNMP
This section describes error messages generated for the Simple Network Management Protocol.
SNMP-5-LINK_DOWN: LinkDown:Interface [chars] changed state to downExplanation 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 upExplanation The state of the interface is changed to up.
Recommended Action No action is required.
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
%UBR7100-6-ACTIVE
%UBR7200-6-ACTIVE
%UBR10000-6-ACTIVE: Cable clock [chars] reference activeExplanation The clock reference has become active.
Recommended Action No action is needed.
%UBR7100-3-ALARM_ERROR
%UBR7200-3-ALARM_ERROR
%UBR10000-3-ALARM_ERROR: [chars]Explanation General error information.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl). Also perform a search of the Bug Toolkit (http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://tools.cisco.com/ServiceRequestTool/create/launch.do), or contact your Cisco technical support representative and provide the representative with the gathered information.
%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 MasksExplanation 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.shtmlOtherwise, 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 dynamicExplanation 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.
%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 beExplanation 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 QoSExplanation 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:
–
–
–
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 tablesExplanation 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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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 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-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 entriesExplanation 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 cardExplanation 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 ErrorExplanation 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 ErrorExplanation 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 serviceExplanation 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 serviceExplanation 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 flowsExplanation 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] offlineExplanation 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.
%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] removedExplanation 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 deadExplanation 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 completedExplanation 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 initiatedExplanation 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 failedExplanation 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 failedExplanation 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 failedExplanation 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 failedExplanation 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 HandshakeExplanation 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 failedExplanation 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 failedExplanation 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 imageExplanation 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 succeededExplanation 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 succeededExplanation 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 delayExplanation 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 receivedExplanation 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 failureExplanation 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 errorExplanation 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 IDExplanation 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 reasonExplanation 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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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 failureExplanation 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 foundExplanation 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 messageExplanation 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 errorExplanation 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 bigExplanation 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 errorsExplanation 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 contextExplanation 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 supportedExplanation 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 foundExplanation 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 presentExplanation 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 foundExplanation 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 reasonExplanation 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 channelExplanation 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 channelExplanation 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 channelExplanation 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 newExplanation 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 oldExplanation 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 thereExplanation 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 channelExplanation 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 channelExplanation 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 failureExplanation 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 errorExplanation 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 IDExplanation 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 reasonExplanation 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 configurationExplanation 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 invalidExplanation 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 errorExplanation 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 takenExplanation 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 bayExplanation 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.
Error Message %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 ClockcardExplanation 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 a valid service flow. 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 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 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 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_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 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 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-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 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-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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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 Correct the classifier errors and reissue the request. 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-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. 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_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 because the message request 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 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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://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 subinterfacesExplanation 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 fai
