3000 Old Alabama Road Suite 119-434, Alpharetta, GA 30022-8555404-424-8202info@volpefirm.com

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

Post 123 of 154
DOCSIS T1, T2, T3 and T4 timeouts

DOCSIS T1, T2, T3 & T4 Timeouts

This is a handy summary of the various T1, T2, T3 and T4 timeout errors you will find in a DOCSIS network.  T3 and T4 timeouts are described in much more detail elsewhere in this blog, however this post provides a high level overview of the various timeouts as a reference.  Thanks to baranek110 for the tutorial located on Cable-Modem’s Blog.

T1 Timeout ( No UCD’s received )

Explanation: The cable modem has not received any periodic Upstream Channel Descriptor (UCD) messages from the CMTS within the timeout period. This error message is DOCSIS event message is U01.0, Upstream Channel Descriptor.

T2 Timeout ( No Maintenance Broadcasts for Ranging opportunities received )

Explanation: The cable modem did not receive a broadcast maintenance opportunity in which to transmit a Ranging Request (RNG-REQ) within the T2 timeout period (approximately 10 seconds). The cable modem is resetting its cable interface and restarting the registration process. This error message is DOCSIS event message is R01.0, Ranging Request.

T3 Timeout ( Ranging Request Retries Exhausted )

Explanation: The cable modem has sent 16 Ranging Request (RNG-REQ) messages without receiving a Ranging Response (RNG-RSP) message in reply from the CMTS. The cable modem is therefore resetting its cable interface and restarting the registration process. This typically is caused by noise on the upstream that causes the loss of MAC-layer messages. Noise could also raise the signal-to-noise ratio (SNR) on the upstream to a point where the cable modem’s power level is insufficient to transmit any messages. If the cable modem cannot raise its upstream transmit power level to a level that allows successful communication within the maximum timeout period, it resets its cable interface and restarts the registration process. This error message is DOCSIS event message is R03.0, Ranging Request.

T4 Timeout ( Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received )

Explanation: The cable modem did not received a station maintenance opportunity in which to transmit a Ranging Request (RNG-REQ) message within the T4 timeout period (30 to 35 seconds). The cable modem is resetting its cable interface and restarting the registration process. Typically, this indicates an occasional, temporary loss of service, but if the problem persists, check for possible service outages or maintenance activity on this particular headend system. This error message is DOCSIS event message is R04.0, Ranging Request.

T6 Timeout ( Cable Interface Reset )

Explanation: The cable modem has sent 3 Registration Requests (REG-REQ) to the CMTS without receiving a Registration Response (REG-RSP) within the T6 timeout period (3 seconds). The cable modem is therefore resetting its cable interface and restarting the registration process

This problem can also occur if the DOCSIS configuration file is corrupt, or if it contains a large number of vendor-specific information fields (VSIF). If the configuration file contains a large amount of VSIF information, the cable modem might generate a Registration Request (REG-REQ) that exceeds the maximum size of DOCSIS MAC-layer management messages (1514 bytes plus the header). The CMTS considers this an invalid MAC-layer management message and drops it, without replying.

Limited Time – Want a DOCSIS 3.0 Cable Modem Registration with T3 & T4 Timeouts Poster?

Mr. Volpe has over 25 years of communications industry experience. He is focused on the cable and telecom industry with deep technical and business skills. Mr. Volpe is currently the president and chief technologist of the Volpe Firm and holds an MSEE with honors.

Twitter LinkedIn Google+ 

, , , , , , ,

22 comments:

cabs06/28/2011 at 19:24Reply

Are we sure if a T3 timeout message is seen in the logs, that this correlates to a reboot of the modem (restart of the registration process)? I’ve seen plenty modems with a T3 timeout, but no other entries in the modem log to indicate a re-registration, or/and a change in the uptime at the CMTS.
T4′s yes, but not T3′s…

confused….

Brady06/28/2011 at 21:31Reply

Hey cabs,

You are absolutely correct. Depending on the cable modem manufacturer and it’s version of firmware, it will display T3 timeout messages when the cable modem does not receive a Range Response (RNG-RSP) from the CMTS within 200 msec of sending a Range Request (RNG-REQ). The T3 errors are an early alert system of potential bigger problems to come. When you have a modem actually reset due to T3 timeouts, it is the CMTS reaching a pre-determined threshold of x-number of T3 timeout errors. Typically this will be about 10-12 consecutive T3 timeouts, but this will vary based upon CMTS vendor, IOS, plant configurations, etc. The reason it is 10-12 is because that is amount of time it takes to exceed the required 20 second (10 * 200 ms=20 sec) CMTS threshold for not receiving a RNG-RSP. The DOCSIS spec requires 35 seconds, but CMTS vendors are more conservative. There is another blog post that contains additional information on T3 and T4 timeouts at http://bradyvolpe.com/docsis-101/docsis101_station-maintenance/

-Brady

Carl Thomas09/06/2011 at 05:57Reply

Thanks for the offer on Twitter.

The MSO have been overbuilding the area to upgrade it from 550/30 to 1000/85 network. Since they did that I’ve seen this error message once a day, non-service affecting:

Tue Sep 06 08:14:34 2011 Critical (3) UCD invalid or channel unusable;CM-MAC=a0:21:b7:12:3d:5c;CMTS-MAC=00:30:b8:d0:ac:c0;CM-QOS=1.1;CM-VER=3.0;

This also corresponds with power levels being rather changed, upstream tx power has dropped by 14dBmV and downstream rx has increased by 7dBmV.

Downstream Channels
Lock Status Modulation Channel ID Max Raw Bit Rate Frequency Power SNR Docsis/EuroDocsis locked
Locked QAM256 38 55616000 Kbits/sec 299000000 Hz 12.1 dBmV 40.2 dB Hybrid
Locked QAM256 39 55616000 Kbits/sec 307000000 Hz 11.9 dBmV 40.2 dB Hybrid
Locked QAM256 40 55616000 Kbits/sec 315000000 Hz 11.5 dBmV 39.7 dB Hybrid
Locked QAM256 41 55616000 Kbits/sec 323000000 Hz 10.9 dBmV 39.5 dB Hybrid

Upstream Channels
Lock Status Modulation Channel ID Max Raw Bit Rate Frequency Power
Locked TDMA 2 10240 Kbits/sec 25800000 Hz 34.5 dBmV

Cableco believe no configuration changes have been made, so according to them there isn’t, say, a 2nd upstream channel added to the service group above 30MHz which I can’t lock to due to being RF limited.

Any thoughts welcome – as there’s no service impact with either that message or the power levels the MSO will not give me a service call and it’d be rude to ask really.

I’m curious about the message though, it seems not particularly well documented and is usually linked to downstream impediments corrupting the UCD which I can’t see any evidence of.

Thanks!

Brady09/09/2011 at 08:16Reply

Hi Carl,
From your OUI of a0:21:b7 I can tell that you have a Netgear cable modem ver. 3.0, which is a DOCSIS 3.0 modem that supports DOCSIS and Euro-DOCSIS. It supports downstream channel bonding for up to four (4) channels and upstream channel bonding for up to four (4) channels. So it’s not a bad modem.
It looks like your running on a Euro-DOCSIS plant with 8 MHz channel spacing. The downstream appears to be fine based upon the modem’s log file and channel setup. You have probably noticed an increase in downstream power level due to the re-build and re-balance of the plant to 1 GHz. If they did a good job, you should have a cleaner downstream with less issues than in the 550 MHz plant.
On the upstream, it sounds like they are bonding two upstream channels, one at 25.8 MHz and one above 30 MHz. The error message you are getting, “Critical (3) UCD invalid or channel unusable…” is your cable modem stating that either the UCD has told the cable modem to lock to a channel it cannot physically lock to or the channel is not usable due to physical impairments. Since the Netgear is DOCSIS 3.0 compliant, we know that it will go up to 85 MHz, so 30 MHz should be no problem, therefore we can rule out a bad UCD. So that leaves us with an impaired channel.
When a cable modem fails to lock to one or more upstream bonded channels, this is called “Partial Service”. In a partial service situation, the CMTS will notice that the cable modem has a subset of the channels transmitting and issue transmit opportunities (MAPs) only for the working channels. In your case that is the channel at 25.8 MHz. So you will not notice any loss of data because the CMTS will not allow your modem to transmit data on the missing channel. This is a very nice feature in DOCSIS 3.0, because one or more bonded channels can go down in a DOCSIS 3.0 modem yet the subscriber will never know the difference unless the upstream is near maximum throughput capacity.
Now should the cable operator ignore this? Not for the long term. One of your bonded channels is down, but your service is not interrupted – for now. Your cable provider does need to ultimately troubleshoot and resolve the root cause to get your modem (and any others) out of a partial service condition. There is an impairment in the plant. DOCSIS 3.0 is able to mask the impairment from the subscriber, but it does not make the impairment go away. So the operator has some temporary breathing room to fix the impairment. Should another impairment arise around 25.8 MHz, then you will be out of service altogether.
So I recommend that you ask your cable operator what is their timeline to get your second bonded channel back online. Keep in mind that they may have many larger fires to fight right now and this may be a much lower priority, but it should still be on their to-do-list.
-Brady

denden11/10/2011 at 17:55Reply

Hi Brady,

Can you explain a little the concepts and messaging behind Partial Service and how they are implemented on the CMTS. I believe its CM messaging that alerts the CMTS to impaired services or missing channels is this correct ?

Any help on understanding this would be great :-)

Den .

Brady11/21/2011 at 16:33Reply

Hi Den,

I just did a short presentation at SCTE’s Cable-Tec Expo 2011 on Partial and Impaired Service this past week. Please give me some time to catch up as I will be writing a full article on the two issues that impact DOCSIS 3.0 cable modems during upstream channel bonding.

-Brady

gabriel burdan11/11/2011 at 11:38Reply

Hi Brady
I have some questions regarding modem logs.How is possible to “translate” all messages and to be able to troubleshoot calls from customers.

Thanks

Map Reject – Not Authorized for Requested Downstream Traffic Flow (EC=7);CM-MAC=e4:48:c7:6b:7e:d6;CMTS-MAC=00:17:10:01:98:93;CM-QOS=1.1;CM-VER=3.0;
SYNC Timing Synchronization failure – Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e4:48:c7:6b:7e:d6;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
YNC Timing Synchronization failure – Failed to acquire FEC framing;CM-MAC=e4:48:c7:6b:7e:d6;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
SYNC Timing Synchronization failure – Failed to acquire QAM/QPSK symbol timing I have 3345 messages on a modem

Brady11/21/2011 at 16:40Reply

Hi Gabi,

I am glad you are asking the question. I can’t answer your question in the body of this post, but I will put together a future article to address your question. A couple of articles back I asked if my audience wanted me to further elaborate on errors beyond the physical (PHY) layer and your response is just what I was looking for. If you have additional cable modem logs, please send them to brady.volpe [at] volpefirm.com and I can add these to the future article.

BTW, I did notice the “MAP Reject – Not Authorized for Requested Downstream Traffic Flow” error in your log above. You likely have a VoIP session that is failing to tear down the Dynamic QoS or a hacker that is creating that error message. If you get that frequently and are sure it is not a hacker, confirm your Dynamic Service Flows have an auto timeout on them.

-Brady

Moh03/01/2012 at 17:47Reply

Hey Brady,

First, I would like to express how much I appreciate your DOCSIS tutorials and website content in general. The explanation is detailed and very helpful.
On the same token, would like to know why a phone modem(MTA), in the provisioning stage, would start and scan for the wrong downstream frequencies:
1-DS for the CMTS is set to freq 657MHz
2-Modem starts scanning at 687, 693,… all the way to 1110MHz.
How do you explain that issue causing intermittent phone and high speed data issue?
The return spectrum is showing a very minor noise floor but not enough to cause any problems.

Brady03/02/2012 at 09:36Reply

Hi Moh,

The cable modem’s scan table is determined by the modem manufacturer. Normally scan tables begin around the mid-400 MHz to 500 MHz and go up. I have also seen cable modems that start at high frequencies and go down, however so it really depends upon the cable modem manufacturer. Also, scan tables are set (at least in the US) based on HRC (harmonically related carriers) which is the typical North America channel line up. Then they “should” start checking the IRC (inter-harmonically related carrier) channel table. If you are using the IRC channel spacing, this could take longer.

You can work with your modem vendor and have them create a special firmware build for your system if you are having issues with your channel plan, but I do recommend against special firmwares as this takes you out of the normal build process.

As for the intermittent phone and high speed data issues – I don’t believe there is any relationship between downstream channel scanning and your intermittent issue. Once the cable modem has found the downstream channel and registered with the CMTS, it should not have to re-scan again. It is my opinion that you have another issue going on outside of downstream channel scan. Even though your return spectrum looks good, that does not mean there are not underlying problems. Many problems can exists that will not show up on a spectrum analyzer.

-Brady

Antonio03/27/2012 at 17:32Reply

Hello i found this site and i wanted to ask a question i am geting T3 and T4 timeouts that are rebooting my modem a couple of times a day.. Do you know what can be causing them…

Logs:R02.0 NO RANGING RESPONCE RECEIVED T3 TIMEOUT THEN T05.0 SYNC TIMING SYNCHRONIZATION FAILURE LOSS OF SYNC THEN CABLE MODEM REBOOT DUE TO T4 TIMEOUT….

Nancy Roberts07/18/2012 at 22:13Reply

This a very informative blog. This could help me know more on the various time-outs that usually happens. Hope you could feature another relevant issues on Broadband stuffs. Thanks!

Marc King09/15/2012 at 09:08Reply

It is very rare to meet certain reviews as entertaining and as educative as this site.It only proves that everything is in detailed and is one of the best reliable resources that an individual can learned through reading both the article itself and that users has encountered certain circumstances during configurations wherein perfectly answered by Brady. [ cable modem guide (dot) org ]

dawn09/07/2013 at 14:28Reply

Just wanted to say thank you so much for this post! Stating the explanations more simply at first makes it easier to grasp the complexities as you learn more. Somehow, today is the first time I’ve stumbled upon your site and I’m excited to finally have a resource to learn a bit more about my modem! Seems that kind of information is lacking online (or Google hasn’t gotten around to indexing them properly yet…). Anyway, your site is in my bookmarks now so I can go through the tutorials later on so I can finally have a better understanding of that portion of my home network! Now, to finally find something to better explain the technical aspects of data transfer through my router– then I’d be set! :)

Thanks again!!!!

Rob T11/25/2013 at 19:53Reply

Why is it that when the cable tech replaced my mdm with a new mdm, and the cleaned noise from my lines and said it was good that I still see T3′s on the mdm. (288 in 5 hours.) To hit on that my Phone mdm is located directly next to it on the same 2 way splitter and has only seen 44 T3′s over a course of 45 day? Im curious to know what would cause the internet mdm to timeout that much, but my phone mdm consistently stays tough with much fewer timeouts. It is really frustrating and affecting my buffering when streaming movies! errr. Thanks, Rob T

Brady Volpe11/29/2013 at 13:40Reply

Hi Rob,

Its likely that your voice modem is on a different frequency and/or modulation that is less susceptible to the upstream impairments that your data modem is. This is quite common for voice modems to be put on frequencies and use more robust modulations. So you are seeing less T3 timeouts on the voice modem. This is good for the voice modem and you because you are likely experiencing better phone quality than if your voice modem was on the data modem.

-Brady

Rob T11/30/2013 at 13:56Reply

Thank for responding to my concerns.What steps could I take to resolve the internet issues? I’m glad that the voice is working well, but I’m really concerned about fixing the mdms issue for internet. Do you think it could be a cmts issue with the provider or even a bad drop. Im just pondering ideas. If the voice mdm is solid could the drop still be the problem? Id like some insite in this. Could it even be utilization contention from the amount of bandwith in the neighborhood… Please let me know what you think. Thanks!

Mia01/30/2014 at 15:19Reply

Hi Rob,

Thanks for your interest. Unless you are the cable operator there really isn’t a lot you can do. From your post it sounds as if you are a end user. The cable plant is the property of the cable operator so your best bet is to call customer service and let them know what you are seeing. We would be glad to work with your cable operator if they contact us directly, however, I am sure they have someone on staff who will resolve your issue. If not they can call us.

Best

Rob T01/31/2014 at 07:46Reply

I am a service technician for a major cable company. Trying to get to the bottom of this, any useful help???

Brady Volpe01/31/2014 at 09:50Reply

Hi Rob,

You definitely have some complicated issues. Its often difficult to determine when subscribers are asking questions and technicians are asking them and we don’t want to pit subscribers against their providers as I’m sure you can appreciate. I believe that it is really quite difficult for us to resolve your technical challenges in a forum environment without diving more deeply into your specific network as it is possible that we could give you bad advice rather than the solution. We would be happy to work with you under our professional services to understand more.

-Brady

Rob T02/05/2014 at 17:59Reply

Thanks You

MARCELO SANCHEZ05/30/2014 at 11:58Reply

Estimado Braddy este log esta teniendo mi cablemodem que se supone que esta tratando de hacer ??
critical 29-May-2014 05:33 29-May-2014 05:39 4 TFTP failed – request sent – No Response
critical 29-May-2014 05:39 29-May-2014 05:44 17 No Ranging Response received – T3 time-out
critical 29-May-2014 05:44 29-May-2014 05:44 1 Init RANGING Critical Ranging Request Retries exhausted
critical 29-May-2014 05:48 29-May-2014 05:48 1 Init RANGING Critical Ranging Request Retries exhausted
critical 29-May-2014 05:44 29-May-2014 05:48 17 No Ranging Response received – T3 time-out
critical 29-May-2014 05:48 29-May-2014 05:53 17 No Ranging Response received – T3 time-out
critical 29-May-2014 05:53 29-May-2014 05:53 1 Init RANGING Critical Ranging Request Retries exhausted
critical 29-May-2014 05:54 29-May-2014 05:54 2 No Ranging Response received – T3 time-out
critical 29-May-2014 05:54 29-May-2014 05:54 1 DHCP WARNING – Non-critical field invalid in response.
warning 29-May-2014 06:15 29-May-2014 06:15 3 Map Reject – Not Authorized for Requested Downstream Traffic Flow (EC=7)
warning 29-May-2014 06:24 29-May-2014 06:24 1 DHCP RENEW WARNING – Field invalid in response
warning 29-May-2014 06:26 29-May-2014 07:25 4 Map Reject – Not Authorized for Requested Downstream Traffic Flow (EC=7)
critical 29-May-2014 07:32 29-May-2014 07:38 4 TFTP failed – request sent – No Response
critical 29-May-2014 07:38 29-May-2014 07:38 1 DHCP WARNING – Non-critical field invalid in response.
warning 29-May-2014 08:22 29-May-2014 11:39 9 Map Reject – Not Authorized for Requested Downstream Traffic Flow (EC=7)
warning 29-May-2014 14:00 29-May-2014 14:00 3 Map Reject – Not Authorized for Requested Downstream Traffic Flow (EC=7)
critical 29-May-2014 14:55 29-May-2014 14:55 1 Started Unicast Maintenance Ranging – No Response received – T3 time-out
warning 29-May-2014 15:00 29-May-2014 15:00 1 Map Reject – Not Authorized for Requested Downstream Traffic Flow (EC=7)
critical 29-May-2014 15:28 29-May-2014 15:56 3 SYNC Timing Synchronization failure – Failed to receive MAC SYNC frame within time-out period
warning 29-May-2014 16:00 30-May-2014 04:52 14 Map Reject – Not Authorized for Requested Downstream Traffic Flow (EC=7)

Menu