22 11, 2011
  • DOCSIS Xpert Protocol Analyzer

Fresh Tech | DOCSIS Protocol Analyzer – Can’t stop a good idea!

2021-08-18T10:13:29-04:00November 22nd, 2011|

When I first heard rumor that a knew company had a DOCSIS protocol analyzer floating around I had to see it! With full disclosure, many of you know that after 10 years in RF and fiber-optic transport equipment, I spent a few years designing, marketing and selling DOCSIS protocol analyzers. More specifically I focused on making them available to cable operators because I knew they could detect really difficult to isolate problems. Averna know owns the technology from my Sigtek days, so it is nice to see a new competitor in the space. What's more is that its nice to see this competitor at SCTE Cable-Tec Expo who is interested in cable operator's issues.

1 11, 2011

Piedmont Chapter DOCSIS 3.0 Training

2021-08-24T08:53:15-04:00November 1st, 2011|

John Downey and Brady Volpe will be speaking on November 2, 2011 at the Piedmont SCTE Chapter about DOCSIS 3.0 Troubleshooting, Implementation,  and Planning.  This is the first speaking engagement under my new consulting company The Volpe Firm, Inc., so I am truly vendor neutral and will be to field questions on any topic. Also, for those of you who will be at Cable-Tec Expo, I will be speaking on Advanced DOCSIS 3.0 Troubleshooting in the Plant.  My presentation is on Wednesday November 16th and offered at the following times and locations:

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

11 09, 2011
  • DOCSIS 3.0 Speaking Engagements

DOCSIS 3.0 Speaking Engagements

2011-09-11T18:04:11-04:00September 11th, 2011|

See me present at IBBS's symposium during September 13-14, 2011 or Cable-Tec Expo during November 15-17, 2011 on DOCSIS 3.0 test equipment and troubleshooting.

9 09, 2011
  • DOCSIS 3.0 cable modems transmitting 52.2 dBmV

Why are my DOCSIS 3.0 cable modems transmitting at 52.2 dBmV?

2021-08-18T09:53:33-04:00September 9th, 2011|

A recent question from a reader provided an interesting response - the answer: maximum transmit power is 52.2 dBmV for DOCSIS 3.0 cable modems under certain conditions. The answer is very simple. They were transmitting at their maximum transmit level. That being in a 16-QAM modulation with four bonded upstream channels.

24 06, 2011
  • docsis t1, t2, t3 and t4 timeout

DOCSIS T1, T2, T3, and T4 Timeout Descriptions

2022-06-20T20:55:33-04:00June 24th, 2011|

This is a handy summary of the various timeout errors you will find in a DOCSIS network. T3 and T4 timeouts are described in much more detail elswhere in this blog, however this post provides a high level overview of the various timeouts as a reference.

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:

7 07, 2010

DOCSIS 3.0 Tutorial – Basic Protocol 1

2021-08-18T09:58:46-04:00July 7th, 2010|

Now that we have established the two primary architectures available in DOCSIS 3.0, I-CMTS and M-CMTS (thought hybrids do exist), and the hardware components of these architectures, it is time to delve into the protocol of the DOCSIS specifications that make up DOCSIS 3.0. There are five primary specifications that I will be drawing upon from here on out listed below and located in my document library and also on the CableLabs website.

26 06, 2010

DOCSIS 3.0 Tutorial – M-CMTS Architecture

2021-11-24T09:41:52-05:00June 26th, 2010|

In this article I am going to further explore the M-CMTS in order to describe two import elements of DOCSIS 3.0 network, the edge-Quadrature Amplitude Modulator or EQAM and the DOCSIS Timing Interface Specification Server or DOCSIS Timing Server. Before I cover these components I will show how they are integrated with the M-CMTS architecture.

Go to Top