Introduction
This document describes the cable modem online states in the Cisco 900 and 7200 Series Universal Broadband Routers (uBR) and why they fail setup.
Prerequisites
Requirements
You must have a basic understanding of the DOCSIS protocol and of the Cisco IOS® software command line on uBR series routers.
Components Used
The information in this document is based on Cisco uBR7200 and uBR900 cable modem termination system (CMTS) and DOCSIS-compliant cable modems.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
Conventions
Refer to Cisco Technical Tips Conventions for more information on document conventions.
Background Information
This document explains cable modem online states in the Cisco 900 and 7200 Series Universal Broadband Routers (uBR), and it explains the reason why they fail setup. Information on the states appear after you issue the show cable modem command.
The show cable modem Sample Output
sniper#show cable modem
Interface Prim Online Timing Rec QoS CPE IP address MAC address
Sid State Offset Power
Cable2/0/U0 11 online 2287 0.25 5 0 10.1.1.25 0050.7366.2223
Cable2/0/U0 12 online 2812 0.25 5 0 10.1.1.28 0001.9659.4415
Cable2/0/U0 13 online 2810 -0.50 5 0 10.1.1.20 0030.96f9.65d9
Cable2/0/U0 14 online 2290 0.50 5 0 10.1.1.26 0050.7366.2221
Cable2/0/U0 15 online 2292 0.25 5 0 10.1.1.30 0050.7366.1fb9
Cable2/0/U0 16 online 2815 0.00 5 0 10.1.1.27 0001.9659.4461
Understand Online States
The tables in this section show the possible values for the MAC state field.
Registration and Provision Status Conditions
| MAC State Value |
Description |
| init(r1) |
The cable modem (CM) sent initial ranging. |
| init(r2) |
The CM is ranging. The CMTS received initial ranging from the CM and has sent radio frequency (RF) power, timing offset, and frequency adjustments to the CM. |
| init(rc) |
Ranging has completed.
Note: If a CM appears to be stuck in this state, it could be that the CM is able to communicate successfully on the cable network but the upstream is at capacity and does not have any additional bandwidth to allow the CM to finish registration and come online. Either manually move one or more CMs to other upstreams or issue the cable load-balance group commands to enable load balancing on the upstream.
|
| init(d) |
The DHCP request was received. This also indicates that the first IP broadcast packet has been received from the CM. |
| init(i) |
The cable modem has received the DHCPOFFER reply from the DHCP server that has assigned an IP address to the modem, but the modem has not yet replied with a DHCPREQUEST message to request that particular IP address, nor has it sent an IP packet with that IP address.
Note: If a CM appears to be stuck in this state, the CM has likely received the DHCPOFFER reply from the DHCP server, but this reply can have contained one or more invalid options for that particular CM.
|
| init(o) |
The CM has begun to download the option file (DOCSIS configuration file) with the Trivial File Transfer Protocol (TFTP), as specified in the DHCP response. If the CM remains in this state, it indicates that the download has failed. |
| init(t) |
Time-of-day (ToD) exchange has started. |
| resetting |
The CM is reset and can soon restart the registration process. |
Non-Error Status Conditions
| MAC State Value |
Description |
| cc(r1) |
The CM had registered and was online, but has received a Downstream Channel Change (DCC) or an Upstream Channel Change (UCC) request message from the CMTS. The CM has begun to move to the new channel, and the CMTS has received the CM’s initial ranging on the new downstream or upstream channel. At the MAC layer, the CM is considered offline because it has not yet passed traffic on the new channel, but this state does not trigger the flap-list counters. |
| cc(r2) |
This state must track cc(r1); and it indicates that the CM has finished its initial ranging on the new channel and is currently performing continuous ranging on the new channel. At the MAC layer, the CM is considered offline because it has not yet passed traffic on the new channel, but this state does not trigger the flap-list counters. |
| offline |
The CM is considered offline (disconnected or powered down). |
| online |
The CM has registered and is enabled to pass data on the network. |
| online(d) |
CM registered, but network access for CPE devices that use this CM has been disabled through the DOCSIS configuration file. The CM does not forward traffic to or from the CPE devices, but the CMTS can continue to communicate with the CM with DOCSIS messages and IP traffic (such as SNMP commands).
Note: If BPI was enabled in the DOCSIS configuration file sent to the CM, assume that the CM is with BPI encryption, unless other messages show that the BPI negotiation and key assignments have failed.
|
| online(pkd) |
The CM registered, but network access for CPE devices that use this CM has been disabled through the DOCSIS configuration file. In addition, BPI is enabled and the key-encrypting key (KEK) is assigned.
Note: This state is equivalent to the online(d) online(pk) states.
|
| online(ptd) |
The CM registered, but network access for CPE devices that use this CM has been disabled through the DOCSIS configuration file. In addition, BPI is enabled and the traffic encryption key (TEK) is assigned. BPI encryption is now performed.
Note: This state is equivalent to the online(d) and online(pt) states.
|
| online(pk) |
The CM registered, BPI is enabled, and the KEK is assigned. |
| online(pt) |
The CM registered, BPI is enabled, and the TEK is assigned. BPI encryption is now performed.
Note: If network access was disabled in the DOCSIS configuration file sent to the CM, then the network disabled status takes precedence, and the MAC status field showsonline(d)instead ofonline(pt), even when BPI encryption is enabled and operational.
|
|
Note: If an exclamation point (!) appears in front of one of the online states, it indicates that the cable dynamic-secret command has been used with either the markor rejectoption, and that the cable modem has failed the dynamic secret authentication check.
|
| expire(pk) |
The CM registered, BPI is enabled, and the KEK was assigned; but the current KEK expired before the CM could successfully renew a new KEK value. |
| expire(pkd) |
The CM registered, but network access for CPE devices that use this CM has been disabled through the DOCSIS configuration file. In addition, BPI is enabled and the KEK was assigned; but the current KEK expired before the CM could successfully renew a new KEK value.
Note: This state is equivalent to theonline(d)andexpire(pk)states.
|
| expire(pt) |
The CM registered, BPI is enabled, and the TEK was assigned; but the current TEK expired before the CM could successfully renew a new KEK value. |
| expire(ptd) |
The CM registered, but network access for CPE devices that use this CM has been disabled through the DOCSIS configuration file. In addition, BPI is enabled and the TEK was assigned; but the current TEK expired before the CM could successfully renew a new KEK value.
Note:This state is equivalent to theonline(d)andexpire(pt)states.
|
Error Status Conditions
| MAC State Value |
Description |
| reject(m) |
The CM attempted to register, but registration was refused due to a bad Message Integrity Check (MIC) value. This also could indicate that the shared secret in the DOCSIS configuration file does not match the value that is configured on the CMTS with the cable shared-secret command. In Cisco IOS Software Release 12.1(11b)EC1 and 12.2(8)BC2 or later releases, this could also indicate that the cable tftp-enforce command has been used to require that a CM attempt a TFTP download of the DOCSIS configuration file before it registers, but the CM did not do so. |
| reject(c) |
The CM attempted to register, but registration was refused due to a a number of possible errors:
- The CM attempted to register with a minimum guaranteed upstream bandwidth that would exceed the limits imposed by the cable upstream admission-control command.
- The CM has been disabled because of a security violation.
- A bad class of service (CoS) value in the DOCSIS configuration file.
- The CM attempted to create a new CoS configuration but the CMTS is not configured to permit such changes.
- The CM failed the timestamp check for its DOCSIS configuration file. (This could indicate a possible theft-of-service attempt, or a problem with the synchronization of the clocks on the CM and CMTS.)
|
| reject(pk) |
The KEK key assignment is rejected and BPI encryption has not been established. |
| reject(pkd) |
The CM registered, but network access for CPE devices that use this CM has been disabled through the DOCSIS configuration file. In addition, BPI encryption was not established because KEK key assignment was rejected.
Note: This state is equivalent to theonline(d)andreject(pk)states.
|
| reject(pt) |
The TEK key assignment is rejected and BPI encryption has not been established. |
| reject(ptd) |
The CM registered, but network access for CPE devices that use this CM has been disabled through the DOCSIS configuration file. In addition, BPI encryption was not established because TEK key assignment was rejected.
Note: This state is equivalent to theonline(d)andreject(pt)states.
|
|
Note: In Cisco IOS Software Release 12.1(20)EC, 12.2(15)BC1, and earlier, when network access is disabled in the DOCSIS configuration file sent to the CM, the network disabled status takes precedence, and the MAC status field showsonline(d)even if BPI encryption fails. Issue the show cable modem mac-address command to confirm whether BPI is enabled or disabled for a particular cable modem.
|
| reject(ts) |
The CM attempted to register, but registration failed because the TFTP server timestamp in the CM registration request did not match the timestamp maintained by the CMTS. This can indicate that the CM attempted to register when it replayed an old DOCSIS configuration file used throughtout a prior registration attempt. |
| reject(ip) |
The CM attempted to register, but registration failed because the IP address in the CM request did not match the IP address that the TFTP server recorded when it sent the DOCSIS configuration file to the CM. IP spoofing could occur. |
| reject(na) |
The CM attempted to register, but registration failed because the CM did not send a Registration-Acknowledgement (REG-ACK) message in reply to the Registration-Response (REG-RSP) message sent by the CMTS. A Registration-NonAcknowledgement (REG-NACK) is assumed. |
|
Note:T he cable modem cannot transmit or receive Internet Protocol (IP) traffic when in areject(xx)state. The maximum data rate is fixed at 1 KBit/sec in each direction. CMTS discards all packets.
|
Related Information
Feedback