dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1
share rss forum feed


HiVolt
Premium
join:2000-12-28
Toronto, ON
kudos:21
Reviews:
·TekSavvy DSL
·TekSavvy Cable
reply to TwiztedZero

Re: [Cable] Modem is not part of the Continuum. Intermittant SB6

said by TwiztedZero:

I'm not too worried about 64QAM, that'll come when they fix the node I'm on eventually, theres got to be hundreds of nodes all thru a single POI so this, I don't expect will happen overnight.

It's not all about the local node... My Node was all fixed up and switched to 4x64QAM way back in April or so, then a few months ago I was switched to the Comstock POI, and I've been on 4x16QAM ever since... Its probably further up the line in my case...
--



sbrook
Premium,Mod
join:2001-12-14
Ottawa
kudos:13

Waimea, your problem is NOT the same. You were getting T3 timeouts, which are distinctly different from T4 timeouts which merovingian gets.



Waimea

join:2010-06-30
Toronto, ON

I noticed that they were T4 timeouts as opposed to the T3s I had. I'm no network specialist but I've been following this thing pretty closely since rogers started mucking about with the bonding. I can't help but suspect that there is some correlation between both, namely that the cmts isn't responding back to the modem and causing the reset in the cable interface.

I'm sure most of you are familiar with these by now but it doesn't hurt to post them again:

T3 ( 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 ( 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.


Source: »volpefirm.com/blog/docsis-101/do···iptions/

Both cite Ranging request as the initial source of the issue. for T3, the modem doesn't get a response after multiple tries and then resets; with T4s the modem doesn't even get a chance to send the ranging request.

Both instances could be caused by signal noise or something that prevents the CMTS from talking to the modem. Or Am I reading it wrong?

edit: To Merovingian, I don't think you can have any effect on who shows up from Rogers, lke they say in french tu vas devoir prendre ton mal en patience until you get a good one. altough one of the techs did tell me that you could escalate it after a few tries to get a more senior level tech in there. Can't quite recall what he called it though.

--
Proud Teksavvy customer since 2007



sbrook
Premium,Mod
join:2001-12-14
Ottawa
kudos:13
Reviews:
·TekSavvy Cable
·WIND Mobile

T3 timeouts are very common during the modem restart process if there's a line problem, since ranging is an integral part of that process.

T4 timeouts occur during operation and result in a modem restart and hence ranging.

IF there were a line issue, even an intermittent one, one would expect with all those T4s causing rebstarts, a T3 timeout would occur during the restart.



TwiztedZero
Nine Zero Burp Nine Six
Premium
join:2011-03-31
Toronto, ON
kudos:5

Lots of line noise is my wild guess of the day. Starts around 8am sometimes a little later - and goes on all day long then near to or just after 2am *poof* everything stablizes until the next morning. Ofc thru some of those overnight hours theres the random odd reboot but its steady enough then to stay in irc or do a little streaming. This past weekend its been next to impossible to do that during the daytime hours. Its almost like theres some kind of interference on my line someplace along the way.

Ofc we know most regular people are sleeping and such during the overnight hours so that does indicate its the line someplace.

Its done this ofc three or four times while I typed this short post. Gives you an idea how dismal it is eh?
--
You see there is only one constant. One universal. It is the only real truth. Causality. Action, reaction. Cause and effect.
Twitter:Merv Chat:irc.teksavvy.ca