Tag Archives: docsis tutorial

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.

DOCSIS 3.0 | Partial Service

DOCSIS 3.0 Partial Service

Partial Service is a new term encountered in the DOCSIS 3.0 MULPI specification and realized in field deployments of DOCSIS 3.0 cable modems using upstream bonding. This was a topic that I touched on in this years SCTE Cable-Tec Expo, but will explore in greater detail in this article. Partial service can be considered a feature because the cable modem will stay online even when one or more upstream transmit channels goes offline.

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

IPv6 and PC Provisioning in a DOCSIS Network

DOCSIS DHCP IP Provisioining

With IPv6 on the way in a number of MSO (Multi-System Operator) networks, I have received numerous questions lately about how home devices such as routers and PCs attached to DOCSIS cable modems will get their IP addresses. Will cable operators suddenly start issuing IPv6 IP addresses to their customers? Will you as a subscriber need to upgrade your equipment to support IPv6? Or does the cable modem act as a Network Address Translation (NAT) device and hand-out IP address to each device attached to it? These are some very good questions and the answers are addressed in the DOCSIS specification as I will outline.

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.

Fringe – President’s Day Topics

In case you have some free time on President’s Day, here are of couple of things for you to take a look at.
On the DOCSIS side, once you have had your dose of tutorials here, head over to the DOCSIS Help Forums at http://www.docsishelp.com/forums . Learn about Alice. While many of you are here to learn about DOCSIS, you may want to take an opportunity to find out the latest in educational software training out of Carnegie Mellon University (CMU). If you got excited about Alice, you may want to take the time to learn about one of the key creators of Alice, Randy Pausch.

DOCSIS 3.0 Tutorial – DOCSIS Does IPv6

DOCSIS 3.0 Cable Modems Support IPv6

Everyone is familiar with Internet Protocol version 4 (IPv4) addresses. You probably even set them up in your home network, such as 192.168.1.1 IPv4 is described in IETF publication RFC 791 (September 1981), which replaced the previous version RFC 760, dating back to January 1980. So its safe to say that IPv4 has been around for some time and serving us quite well. New in DOCSIS 3.0 has support for IPv6. Why do we need this new version? IPv6 has a vastly larger address space than IPv4. This results from the use of a 128-bit address, whereas IPv4 uses only 32 bits. Believe it or not, major cable operators are running out IP address. This is due to more customers, not just for cable modems, but also for set top boxes and VoIP eMTAs. Further, deployed in cable networks are IP devices such as power supplies with embedded cable modems for monitoring voltage, temperature, current and more. All networks are getting more IP devices requiring more and more IP addresses, so the 2128 addresses allocated in IPv4 are no longer sufficient and we turn to the 3.4×1038 addresses provided in IPv6.

DOCSIS 3.0 Tutorial – Upstream Channel Bonding

DSAM DOCSIS 3.0 Throughput Test

The focus of this article will be on the mechanics of upstream channel bonding and how it works more from a DOCSIS protocol perspective. Much more detailed information can be found in the DOCSIS 3.0 MULPIv3.0 document located in the Library, but this will provide a high level overview for the layman who is curious about the basics. First lets understand that it is the cable modem that is doing the channel bonding, remember in the upstream the cable modem transmits data to the CMTS. Per DOCSIS 3.0, the CM can bond from one to four channels in the upstream as coordinated by the CMTS. The CM is always under control by the CMTS.

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:

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