Tag Archives: troubleshooting

Advanced Troubleshooting in a DOCSIS 3.0 Plant

DOCSIS 3.0 Advanced Troubleshooting

If you missed the SCTE Cable-Tec 2011, I am making available my presentation and white paper on Advanced Troubleshooting in a DOCSIS 3.0 Plant. Each speaker had only 20 minutes to cover topics that could easily last hours, so the presentations are understandably brief. Below you will find my presentation in “Slideshare” for online viewing as well as a fully downloadable PowerPoint version. The PowerPoint version also has reader notes attached at the bottom of each slide which you may find useful. In addition, the animations work a little better in the downloadable version.

DOCSIS 3.0 | Impaired Service

DOCSIS 3.0 Impaired Service

“Impaired Service” in which case one or more bonded upstream channels are impacted by upstream RF impairments while other bonded channels are not. Since subscriber data is striped (that is broken into pieces and spread across each upstream channel and then re-assembled by the CMTS), some of the data will be lost or have errors while other data will not. Subscribers will most likely notice an impaired condition as upstream data rates slow down due to TCP/IP transmissions and/or VoIP, gaming, teleconferencing and other real-time applications will be noticeably impacted.

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

DOCSIS Xpert Protocol Analyzer

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.

Piedmont Chapter DOCSIS 3.0 Training

John Downey and I 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. More details on the Piedmont Chapter

Cable Modems Stuck? | init(r1), init(r2)…

Cable Modems Stuck in init(r1) init(r2)

Many of us have been there before – one or more cable modems 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, also known

DOCSIS 3.0 Speaking Engagements

DOCSIS 3.0 Speaking Engagements

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.

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

DOCSIS 3.0 Cable Modem Maximum Transmit Power

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.

DOCSIS 101: T1,T2,T3, & T4 Timeout Descriptions

DOCSIS T1, T2, T3 and T4 timeouts

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.

Hacking DOCSIS Cable Modems

Hacking DOCSIS Cable Modems

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:

Speeding Upstream – Part II

This article will focus more specifically on DOCSIS 3.0 issues that will occur as you are deploying DOCSIS 3.0 or post -deployment.

bradyvolpe.com is Stephen Fry proof thanks to caching by WP Super Cache