cc/td/doc/product/cable
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Cisco Cable CPE Error Messages
System Message Overview
Cisco Cable CPE System Messages

Cisco Cable CPE Error Messages


This document describes the cable-specific system messages generated by the following Cisco cable CPE devices:

This document contains the following major sections:

System Message Overview

Cisco cable CPE devices generate system messages to inform the operator of significant events. This document describes only those system messages that are specific to the Cisco cable CPE devices. For the other system messages that can be generated, see the Cisco IOS System Error Messages, Cisco IOS Release 12.2 document, at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122sup/122sems/index.htm

System messages begin with a percent sign (%) and are structured as follows:

%FACILITY-SUBFACILITY-SEVERITY-MNEMONIC: Message-text

System messages contain the following components:

Table 1   Error Message Severity Levels

Level   Class  Description 

0

Emergency

The system has become unusable and requires immediate attention. This problem might also be affecting other parts of the network.

1

Alert

Some type of system or connection failure has occurred and requires immediate attention.

2

Critical

An error occurred that requires immediate attention to avoid system or connection failure.

3

Error

An error condition occurred that requires attention to resolve. Failure to address this problem will result in some type of system or connection failure in the near future.

4

Warning

A condition occurred that indicates attention is needed in near future to avoid potential problems. Failure to address this problem could result in some type of system or connection failure later on.

5

Notice

A situation occurred that is normal but is significant enough that system administrators might want to notice.

6

Informational

An information message that might or might not be significant to the system administrators.

7

Debug

Messages that appear only while debugging is turned on.

For example, the following message is generated when a Cisco cable modem attempts to register using Baseline Privacy Interface (BPI) encryption, but the request is rejected by the CMTS:

CMBPKM-1-KEYREJECT: Key request rejected by CMTS: [chars] 

When the message is actually generated, it includes the reason why the CMTS rejected the registration request. In this particular case, the cable modem did not register using a valid service identifier (SID):

129.CABLEMODEM.CISCO: Oct 27 10:58:45: %CMBPKM-1-KEYREJECT: Key request rejected by CMTS: Unauthorized SID

Cisco Cable CPE System Messages

This section lists the system messages generated by Cisco cable CPE devices. The messages are listed alphabetically, first according to the facility portion of the error message, and then according to the mnemonic portion of the error message.

CMBPKM

This section describes messages related to the operation of Baseline Privacy Interface (BPI) key management (BPKM) for BPI and BPI+ encryption.

%CMBPKM-1-AUTHREJECT: Authorization request rejected by CMTS: [chars]

If the problem persists, ensure that all of the TLV 17 configuration fields (BLP Config Settings) are present in the DOCSIS configuration file that is being downloaded by the cable modem—this set of TLV fields is required to be present when cable modems are registering using BPI encryption, even when each field is configured with the default settings.

Also verify that TLV 29 (Privacy Enable) has been set to 1 (Enable) in the DOCSIS configuration file being downloaded by the cable modem enables BPI configuration. When a CMTS requires BPI or BPI+ encryption, the CMTS cannot allow the cable modem to register without enabling this encryption.

If registering as a DOCSIS 1.1 or DOCSIS 2.0 cable modem using BPI+ encryption, verify that the cable modem is configured with a proper digital certificate that has not expired. If necessary, see the document, Upgrading the DOCSIS Certificates in Cisco uBR905/uBR925 Cable Access Routers and CVA122 Cable Voice Adapters.

Verify that the cable modem is downloading the proper DOCSIS configuration file. Also verify that the time-of-day on the CMTS is properly configured. Verify that the CMTS can communicate with the authentication servers at the headend, and that the servers are configured to allow BPI access for this cable modem.

%CMBPKM-1-KEYREJECT: Key request rejected by CMTS: [chars]

Also verify that the lifetime of the specified key is at least 10 seconds longer than the grace time setting. If the key's lifetime expires before the cable modem can renew the key, the CMTS can reject future key requests and require the cable modem to completely reregister.

CM_DSPRM

This section describes system messages related to the digital signal processors (DSP) used for the Voice-over-IP (VoIP) ports on the Cisco uBR924 and Cisco uBR925 cable access routers, and on the Cisco CVA122 Cable Voice Adapter.

%CM_DSPRM-6-NODSPRMEVENTS: DSPRM event unavailable
%CM_DSPRM-6-INTERNALERROR: DSPRM internal error[ [chars]:[dec] ]
%CM_DSPRM-6-NOIOSBUFFERS: IOS buffer pool unavailable [ [chars]:[dec] ]
%CM_DSPRM-6-NOIOSMEMORY: IOS memory unavailable [ [chars]:[dec] ]

CM_MONITOR

This section describes system messages related to the operation of the Cable Monitor tool, which is a web-based diagnostic tool that provides easy access to the router's configuration and status information, without requiring access to the router's command line interface (CLI).

%CM_MONITOR-6-DNS_KILL: Terminating DNS process
%CM_MONITOR-6-DNS_RESP: Sending DNS response to [int] (request was for [int])
%CM_MONITOR-6-DNS_STAR: Starting DNS process

DSPDD

This section describes system messages related to the device driver for the digital signal processors (DSP) used for the Voice-over-IP (VoIP) ports on the Cisco uBR924 and Cisco uBR925 cable access routers, and on the Cisco CVA122 Cable Voice Adapter.

%DSPDD-1-DSPFWFAILURE: DSPRM internal error[ [chars]:[dec] ]
%DSPDD-1-INTERNALERROR: DSPRM internal error[ [chars]:[dec] ]
%DSPDD-1-NOIOSBUFFERS: IOS buffer pool unavailable [ [chars]:[dec] ]
%DSPDD-1-NOIOSMEMORY: IOS memory unavailable [ [chars]:[dec] ]

POTS

This section describes the system messages related to the interface between Voice-over-IP ports and the Plain Old Telephony Server (POTS) system on the Cisco uBR924 and Cisco uBR925 cable access routers, and on the Cisco CVA122 Cable Voice Adapter.

%POTS-1-NULL_COMMON_PTR: null CSM/POTS Driver common pointer
%POTS-1-NOMEMORY: Unit [dec], no memory for [chars]
%POTS-3-INVALID_PORT: port [int], Ignoring activation, port number is invalid

For Cisco cable modems, configure TLV 43 (VSIF), sub-TLV 10 (Number of Phone Lines) to set the number of phone lines. For example, the complete TLV to configure the cable modem for two phone lines would be 43-08-08-03-00-00-0C-10-01-02. This translates to:

43-08—VSIF TLV with a length of 8 bytes.

08-03-00-00-0C—Vendor ID sub-TLV, with a length of 3 bytes and a value of 00.00.0C (Cisco).

10-01-02—Number of phones sub-TLV, with a length of 1 byte and a value of 2 (2 phones).

%POTS-3-INVALID_EVENT: Port [int], Event [int] finite state machine error
%POTS-3-VDEV_INIT_ERROR: Port [int] device initialization failure
%POTS-3-PROCESS_EVENT_ERROR: POTS subsystem unexpected event [int].
%POTS-3-FSM_ERROR: POTS finite state machine error [chars].
%POTS-3-QUEUE_EMPTY: POTS empty process message [chars].
%POTS-3-UNSUPPORTED_COUNTRY: CODEC driver doesn't support country [chars].
%POTS-3-UNSUPPORTED_RX_LOSS: CODEC driver only supports input loss values of -6 and 0, not [dec]
%POTS-3-UNSUPPORTED_TX_GAIN: CODEC driver only supports output gain values of 6 and 0, not [dec]
%POTS-3-UNSUPPORTED_SIGNAL_TYPE: Interface only supports loop start.
%POTS-3-UNSUPPORTED_OPTION: Interface does not support this option.
%POTS-3-UNSUPPORTED_RING_FREQ: CODEC driver only supports ring frequency values of 20, 25, and 50 Hz, not [dec]

UBR900

This section lists the CMTS system messages for Cisco cable CPE devices. These system messages use the error codes specified in Appendix I, Error Codes and Messages, of the DOCSIS 1.0 RF specification (ANSI/SCTE 22-1 2002).

%UBR900-4-CORRUPT_SYSTEM_IMAGE: Modem System Image is corrupt. New image upgrade required
%UBR900-4-CORRUPT_SYSTEM_IMAGE_UPGRADING: Modem System Image is corrupt. Image upgrade reinitiated.
%UBR900-4-DHCP_REQ_INFO_NOT_SUPPORTED: D03.0 Requested Info not supported
%UBR900-4-DHCP_RSP_OUT_OF_SPEC: D03.1 DHCP response doesn't contain ALL the valid fields as described in the RF spec Appendix C.1

The required fields include the following. These fields must be present in the DHCP response and contain valid information:

The following fields are optional:

%UBR900-4-FAILED_TO_ACQUIRE_FEC: T02.0 Failed to acquire FEC framing. Error stats? Retry [dec]'s [dec] of bad frames
%UBR900-4-FAILED_TO_ACQUIRE_MAC_FRAMING: T03.0 Failed to acquire MAC framing. Error stats? Retry [dec]'s [dec] of bad frames
%UBR900-4-FAILED_TO_ACQUIRE_MPEG2: T2.1 Acquired FEC framing. Failed to acquire MPEG2 Sync. Retry [dec]\Qs
%UBR900-4-FAILED_TO_ACQUIRE_SYNC: T01.0 Failed to acquire QAM/QPSK symbol timing. Error stats? Retry [dec]'s
%UBR900-4-FAILED_TO_RECEIVE_SYNC: T04.0 Failed to Receive MAC SYNC frame within time-out period
%UBR900-6-IMAGE_UPGRADE_FAILED_FLASH_CHECK: System Image Upgrade FAILED - Image Size = [dec], Flash Size = [dec].
%UBR900-6-IMAGE_UPGRADE_FAILED_IMAGE_CHECK: System Image Upgrade FAILED due to unrecognizable or corrupt image.

If the image is the correct one for your cable modem, use the copy tftp flash command to download it again from the TFTP server. If the problem persists, download the image again from the Cisco Software Center and copy it again to the TFTP server. If this does not correct the problem, try another Cisco IOS software image, or copy the error message exactly as it appears, and ask your Cisco technical support representative to verify that the software that is on Cisco.com is a valid image file.

%UBR900-6-IMAGE_UPGRADE_FAILED_TFTP: System Image Upgrade FAILED due to excessive TFTP failures.
%UBR900-6-IMAGE_UPGRADE_INITIATED: System Image Upgrade initiated
%UBR900-6-IMAGE_UPGRADE_INTERRUPTED: System Image Upgrade interrupted during transfer. Upgrade reinitiated
%UBR900-6-IMAGE_UPGRADE_SUCCESSFUL: System Image Upgrade Complete.
%UBR900-6-IMAGE_UPSTREAM_POWER_HIGH: Upstream Power required at modem registration near maximum
%UBR900-4-INVALID_TOD: D04.0 Time of Day, none set or invalid data
%UBR900-4-INVALID_UCD: U02.0 UCD invalid or channel unusable
%UBR900-4-MAP_ARRIVED_TOO_LATE: M01.0 A transmit opportunity was missed because the MAP arrived too late
%UBR900-6-NO_DHCP_OFFER: D01.0 Discover sent no offer received, No available DHCP Server
%UBR900-6-NO_DHCP_RESPONSE: D02.0 Request sent, no Response
%UBR900-4-NO_UCD_RCVD: U01.0 No UCD's received. Time-out
%UBR900-4-REINIT_MAC: R07.0 Unicast Ranging Received Abort Response. Reinitializing MAC.
%UBR900-3-RESET_CONFIG_FILE_WATCHDOG_EXPIRED: Cable Interface Reset due to config file watchdog timer
%UBR900-3-RESET_DHCP_WATCHDOG_EXPIRED: Cable Interface Reset due to DHCP watchdog timer expiration
%UBR900-3-RESET_LOSS_OF_SYNC: T05.0 Loss of Sync. (Missed 5 in a row, after having SYNCd at one time)
%UBR900-3-RESET_PRIVACY_WATCHDOG_EXPIRED: Cable Interface Reset due to privacy watchdog timer
%UBR900-3-RESET_T2_EXPIRED: R01.0 No Maintenance Broadcasts for Ranging opportunities received, T2 timeout
%UBR900-3-RESET_T3_RETRIES_EXHAUSTED: R03.0 Ranging Request Retries exhausted
%UBR900-3-RESET_T4_EXPIRED: R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received. T4 timeout.
%UBR900-3-RESET_T6_RETRIES_EXHAUSTED: Cable Interface Reset due to t6 timeout

This problem can also occur if the DOCSIS configuration file is corrupt, or if it contains a large number of vendor-specific information fields (VSIF). If the configuration file contains a large amount of VSIF information, the cable modem might generate a Registration Request (REG-REQ) that exceeds the maximum size of DOCSIS MAC-layer management messages (1514 bytes plus the header). The CMTS considers this an invalid MAC-layer management message and drops it, without replying.

%UBR900-7-RNG_REQ_TRANSMITTED: Periodic ranging request message transmitted.
%UBR900-7-RNG_RSP_MSG_RCVD: Periodic ranging response message received.
%UBR900-6-SYNC_LOST_AND_REACQUIRED: Downstream Sync lock lost, and reacquired before timeout expired
%UBR900-3-T3_TIMEOUT_I: R02.0 No Ranging Response received, T3 timeout
%UBR900-3-T3_TIMEOUT_II: R05.0 Started Unicast Maintenance Ranging no Response received. T3 time-out.
%UBR900-3-T3_RETRIES_EXHAUSTED_II: R06.0 Started Unicast Maintenance Ranging no Response received. T3 time-out.
%UBR900-4-TFTP_FAILED_2: D07.0 TFTP Request Failed, OUT OF ORDER packets
%UBR900-4-TFTP_FAILED_3: D08.0 TFTP complete, but failed Message Integrity Check(MIC)

Tip If you are also using a Cisco CMTS, you can use the cable shared-secret, cable dynamic-secret, and cable tftp-enforce commands to ensure that cable modems download a valid DOCSIS configuration file only from authorized TFTP servers at the headend.

%UBR900-4-TFTP_NO_RSP: D05.0 TFTP Request sent, No Response/No Server.

Tip It is possible that this message could indicate that a user is attempting to redirect the cable modem to a local TFTP server, so as to download a customized DOCSIS configuration file that would allow a theft-of-service attack. If you are also using a Cisco CMTS, you can use the cable shared-secret, cable dynamic-secret, and cable tftp-enforce commands to ensure that cable modems download a valid DOCSIS configuration file only from authorized TFTP servers at the headend.

%UBR900-4-TFTP_RQ_FAILED_1: D06.0 TFTP Request Failed, configuration file NOT FOUND

If this message constantly occurs, it could indicate that a user is attempting a theft-of-server attack by sending their own DHCP response that substitutes other filenames, in an attempt to find a configuration file that would provide a better quality class of service. Check the logs on the TFTP server to verify that the cable modem is trying to download only the DOCSIS configuration file that it is authorized to use.

%UBR900-3-TOD_FAILED_TIMER_EXPIRED: TOD failed, but Cable Interface proceeding to operational state
%UBR900-4-TOD_NO_RSP: D04.1 Time of Day request sent no Response received
%UBR900-4-TOD_RSP_INVALID: D04.2 Time of Day Response received but invalid data/format
%UBR900-4-UCC_REQ_INVALID: C01.0 UCC-REQ received with invalid or out of range US Channel ID.
%UBR900-4-UCD_INVALID_OR_OUT_OF_ORDER_CCC: U05.0 UCD received with invalid or out of order Configuration Change Count
%UBR900-4-UNABLE_TO_TX_UCC_RSP: C02.0 UCC-REQ received unable to send UCC-RSP, no TX opportunity.
%UBR900-6-UNDEFINED_HDR_RECEIVED: Mac Messages received with undefined header
%UBR900-4-US_CHANNEL_PARM_NOT_SET: U06.0 US Channel wide parameters not set before Burst Descriptors
%UBR900-4-VALID_UCD_AND_SYNC_NO_MAPS: U04.0 UCD and SYNC are valid, No MAPS for THIS channel
%UBR900-4-VALID_UCD_NO_SYNC: U03.0 UCD valid, But no SYNC received. TIMED OUT.



hometocprevnextglossaryfeedbacksearchhelp
Posted: Thu Oct 23 11:53:00 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.