21 09, 2011
  • Cable Modems Stuck in init(r1) init(r2)

Cable Modems init(r1) init(r2) Why are they stuck?

2021-08-20T09:21:27-04:00September 21st, 2011|

Cable Modems init(r1) init(r2),  DOCSIS Cable Modems going offline? DOCSIS Cable Modems init(r1) init(r2) are stuck or offline! Many of us have been there before - one or more DOCSIS cable modems init(r1) init(r2) stuck in one of numerous "init()" conditions - how do we interpret these messages and what do we do? A recent reader wrote in and had just this problem. DOCSIS cable modems going offline and getting stuck in "R1" or "R2"  condition, or Cable Modems init(r1) init(r2), because these are the status conditions displayed on the DOCSIS CMTS

1 08, 2010
  • Hacking DOCSIS Cable Modems

Hacking DOCSIS Cable Modems

2021-08-17T13:18:52-04:00August 1st, 2010|

Fundamental Precautions You Should Take to Secure Your Network DOCSIS security wholes are a serious problem, even if you are a major MSO (Multiple System Operator). Recently a reader contacted me and said that theft of service, especially uncapping cable modems via hacking, was still impacting his network. Not surprisingly, one vendor's CMTS was able to ward off the hacker's while another vendor's CMTS was unable to prevent the uncapping and subsequent theft of service. I will protect the vendor's identities because I believe that the CMTS is the first line of defense. Vendors have put into place very effective, CMTS specific techniques, such as Cisco's TFTP-Enforce which prohibits a cable modem from registering and coming on line if there is no matching TFTP traffic through the CMTS preceding the registration attempt. But often individual techniques are "hacked" (such as in the TFTP-Enforce bypass method found on hacker sites). What this indicates is that any reliance on a single point or method of hack-proofing your network WILL NOT WORK. You must implement a layered approach consisting of a number of CMTS, DHCP, TFTP and potentially SNMP and Kerbos related methods. The later would apply for MTAs and set top boxes. For now we will just focus on cable modems and the realm of CMTSs and DHCP/TFTP servers. Here are is the bare minimum of what you should be doing:

2 10, 2009

Speeding Upstream – Part I

2021-08-18T10:19:55-04:00October 2nd, 2009|

The first part of this article (in CT's March 2009 issue) discussed downstream potential issues, while this one focuses on the potential issues associated with upstream deployments. In particular, this article covers the critical upstream areas that one should be aware of when getting ready to deploy or already deploying DOCSIS 3.0.

3 03, 2009
  • DOCSIS Station Maintenance

DOCSIS and Cable Modems – How it works :: Station Maintenance

2021-08-17T15:43:18-04:00March 3rd, 2009|

While the UCD provides the language of the DOCSIS network, the Station Maintenance messaging is the proverbial "heartbeat" of the DOCSIS network. A station maintenance session consists of a Range Request sent from a cable and a Range Response sent by the CMTS. The CMTS analyzes the signal quality of the Range Request message and sends back any necessary RF adjustments in the Range Response message. This "handshake" between every cable modem and the CMTS must occur once every 30 seconds as dictated by the DOCSIS specification.

16 02, 2009

Troubleshooting DOCSIS – VoIP Impairments > Delay & Jitter

2021-08-17T15:54:55-04:00February 16th, 2009|

In this blog I will address delay and jitter as they pertain to VoIP in a DOCSIS network.  Delay, jitter and packet loss are the three primary impairment in a VoIP network, but packet loss was addressed in my Troubleshooting DOCSIS - VoIP Impairments > Packet Loss blog. After packet loss, delay is the second most disruptive impairment in VoIP networks.  The effects of delay to the caller generally appear as echo and talker overlap. In PSTN communications, echo can arise as acoustic echo between the mouthpiece and

15 02, 2009

Troubleshooting DOCSIS – VoIP Impairments > Packet Loss

2021-08-17T15:45:30-04:00February 15th, 2009|

In this blog I am going to focus on VoIP packet loss, which is just one of the three (3) primary types of VoIP impairments that are present in a DOCSIS network. I will cover many RF and IP terms in this blog that I have not discussed in my previous tutorials, not to worry! This terminology is all fodder for future blogs. :-) To review, the three fundamental impairments which impact call quality of VoIP communications are as follows: * Packet Loss – The complete or partial loss of a packet containing actual voice payload. * Delay – The time a packet takes to traverse the space between the source and destination of a voice call. The space is comprised of both the physical distance the data must travel in addition to the active network routing and switching elements, which contribute additional delay. * Jitter – The variance of inter-packet arrival time from one transmitted packet to the next sequential packet.

13 02, 2009

Troubleshooting DOCSIS – VoIP Impairments

2023-02-18T10:49:47-05:00February 13th, 2009|

In this blog I am going to digress for a moment from my standard DOCSIS 101 tutorial and spend a little time on DOCSIS troubleshooting basics, especially with respect to Voice-over-Internet Protocol (VoIP). I am doing this as due to many offline questions specific to this topic. Don't worry, though I may start to inter-mix some troubleshooting blogs now and again, just check the DOCSIS 101 page to stay on top of the latest DOCSIS tutorial blogs.

Go to Top