dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
14037
share rss forum feed

xdrag

join:2005-02-18
North York, ON

Tons of disconnects everyday on Cable, T3 timeouts

Hey guys,

I want to get some public opinion on this since teksavvy still haven't responded to my thread in the direct support. One of my lines is getting tons of random disconnects. The modem light would go off and the modem would have to "reconnect". I tested the router and then when i checked the logs of the modem, there's lots of T3 time-outs. Any ideas? SB5101

2012-05-28 00:41:19 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2012-05-28 00:41:08 3-Critical R002.0 No Ranging Response received - T3 time-out (US 4)
2012-05-28 00:40:55 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2012-05-28 00:40:45 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC
2012-05-28 00:39:52 6-Notice M572.0 Rng Rsp Abort Status - Reinitialize MAC...
2012-05-28 00:39:52 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC
2012-05-28 00:23:28 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2012-05-28 00:23:17 3-Critical R002.0 No Ranging Response received - T3 time-out (US 3)
2012-05-28 00:22:59 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2012-05-28 00:22:44 3-Critical R002.0 No Ranging Response received - T3 time-out (US 1)
2012-05-28 00:22:37 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC
2012-05-28 00:22:08 3-Critical R002.0 No Ranging Response received - T3 time-out (US 4)
2012-05-28 00:21:53 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC
2012-05-28 00:21:34 3-Critical R002.0 No Ranging Response received - T3 time-out (US 3)
2012-05-28 00:21:14 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2012-05-28 00:20:51 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC
2012-05-28 00:20:33 3-Critical R002.0 No Ranging Response received - T3 time-out (US 3)
2012-05-28 00:20:21 3-Critical R002.0 No Ranging Response received - T3 time-out (US 1)
2012-05-28 00:20:15 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC
2012-05-28 00:19:50 3-Critical R002.0 No Ranging Response received - T3 time-out (US 4)
2012-05-28 00:19:21 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2012-05-28 00:18:47 3-Critical R002.0 No Ranging Response received - T3 time-out (US 1)
2012-05-28 00:18:40 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC
2012-05-28 00:18:21 3-Critical R002.0 No Ranging Response received - T3 time-out (US 4)
2012-05-28 00:18:08 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC
2012-05-28 00:17:47 3-Critical R002.0 No Ranging Response received - T3 time-out (US 3)
2012-05-28 00:17:41 6-Notice M572.0 Rng Rsp Abort Status - Reinitialize MAC...
2012-05-28 00:17:41 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC
2012-05-28 00:11:49 6-Notice M571.1 Ethernet link up - ready to pass packets
2012-05-28 00:11:47 6-Notice M571.4 Ethernet link dormant - not currently active
2012-05-28 00:11:31 6-Notice M571.1 Ethernet link up - ready to pass packets
2012-05-28 00:11:15 6-Notice M571.4 Ethernet link dormant - not currently active
2012-05-28 00:11:05 6-Notice M571.1 Ethernet link up - ready to pass packets
2012-05-28 00:10:23 6-Notice M571.4 Ethernet link dormant - not currently active
2012-05-28 00:09:51 6-Notice M571.1 Ethernet link up - ready to pass packets
2012-05-28 00:09:37 6-Notice M571.4 Ethernet link dormant - not currently active
2012-05-28 00:08:21 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2012-05-28 00:08:12 3-Critical R002.0 No Ranging Response received - T3 time-out (US 3)
2012-05-28 00:08:05 6-Notice M572.0 Rng Rsp Abort Status - Reinitialize MAC...
2012-05-28 00:08:05 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC
2012-05-28 00:06:45 6-Notice M571.1 Ethernet link up - ready to pass packets
2012-05-28 00:06:07 6-Notice M571.4 Ethernet link dormant - not currently active
2012-05-28 00:05:21 6-Notice M571.1 Ethernet link up - ready to pass packets
2012-05-28 00:04:07 6-Notice M571.4 Ethernet link dormant - not currently active
2012-05-28 00:00:35 6-Notice M571.1 Ethernet link up - ready to pass packets
2012-05-28 00:00:21 6-Notice M571.4 Ethernet link dormant - not currently active
2012-05-27 23:56:58 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2012-05-27 23:56:45 3-Critical R002.0 No Ranging Response received - T3 time-out (US 3)
2012-05-27 23:56:37 6-Notice M572.0 Rng Rsp Abort Status - Reinitialize MAC...
2012-05-27 23:56:37 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC
2012-05-27 23:56:04 6-Notice M571.1 Ethernet link up - ready to pass packets
2012-05-27 23:56:02 6-Notice M571.4 Ethernet link dormant - not currently active
2012-05-27 23:55:44 6-Notice M571.1 Ethernet link up - ready to pass packets
2012-05-27 23:55:28 6-Notice M571.4 Ethernet link dormant - not currently active
2012-05-27 23:55:12 6-Notice M571.1 Ethernet link up - ready to pass packets
2012-05-27 23:54:56 6-Notice M571.4 Ethernet link dormant - not currently active
2012-05-27 23:54:10 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2012-05-27 23:54:07 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
2012-05-27 23:53:37 3-Critical R002.0 No Ranging Response received - T3 time-out (US 3)
2012-05-27 23:53:29 6-Notice M572.0 Rng Rsp Abort Status - Reinitialize MAC...
2012-05-27 23:53:29 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC


eruntalon

join:2007-10-18

I just started getting the same thing here in London, maybe 30 minutes ago. Just refuses to connect now.


pennyarcade

join:2010-12-07
North York, ON
reply to xdrag

Hey xdrag, any updates on this issue? I'm getting the same thing (I posted on teksavvy direct) here at Yonge/Finch. I noticed it only happens in the evening. My connection's fine in the morning.


webfors

join:2006-10-03
Kanata, ON

1 recommendation

reply to xdrag

Same problem here with the fallowfield POI with both a DCM475 (STAC.02.08) and DCM476 (STAC.02.31). This is *not* a cable modem issue. Do not waste your time and money on trying different modems.

The "No Ranging Response received - T3 time-out" entries are directly responsible for the power cycle your modem goes through, which is natural since it's trying to re-establish a successful signal with the CMTS after several failed attempts.

I have had this issue for months and it has come to a head now and is starting to interfere with my ability to run a home office.



JoJoBlue

join:2009-12-08
Scarborough, ON
reply to xdrag

I've had this happen to me maybe a year ago. It lasted for a few weeks, and Teksavvy wasn't able to do much. Then it just got better on its own. Unfortunately, no one was ever able to figure out what the problem was, or what resolved it.


webfors

join:2006-10-03
Kanata, ON

1 recommendation

reply to xdrag

Exactly, not a modem issue. Here's an interesting read:

»volpefirm.com/docsis-101/docsis1···tenance/


xdrag

join:2005-02-18
North York, ON

4 edits
reply to xdrag

Click for full size
I opened a ticket with TSI. We'll see what happens. It's been going on for a few weeks and it's getting worse. Maybe rogers broke something while upgrading their network. I'll post a image of my signal page. The upstream power is a bit high but that's all the wrong i can see.

There's another thread going on on T3 timeouts and DCM problems. I'm using a SB5101 so i'm not sure if it's modem related at all. My connection never disconnected up until recently. I feel part of the network is just poorly run on Rogers/TSI. I have a SB6120 on my other connection so when i have time I'll swap it out to see if it's really a modem issue.

Correction: 2 other threads. If people haven't already opened a ticket, they should and maybe we can force rogers to look deeper into this issue.

webfors

join:2006-10-03
Kanata, ON

Yes, open a ticket and post in the teksavvy direct forum. Get as much exposure as you can and tickets opened with Rogers. This is *not* a modem issue IMO. The more reports Rogers gets the better chance we'll see a line tech in the area checking for impairments.



JoJoBlue

join:2009-12-08
Scarborough, ON
reply to xdrag

said by xdrag:

I opened a ticket with TSI. We'll see what happens. It's been going on for a few weeks and it's getting worse. Maybe rogers broke something while upgrading their network. I'll post a image of my signal page. The upstream power is a bit high but that's all the wrong i can see.

There's another thread going on on T3 timeouts and DCM problems. I'm using a SB5101 so i'm not sure if it's modem related at all. My connection never disconnected up until recently. I feel part of the network is just poorly run on Rogers/TSI. I have a SB6120 on my other connection so when i have time I'll swap it out to see if it's really a modem issue.

Correction: 2 other threads. If people haven't already opened a ticket, they should and maybe we can force rogers to look deeper into this issue.

I also use the SB5101. I've never switched modems. Since the problem went away on its own, I doubt it's a problem with the modem.

spiderman168

join:2012-06-02
reply to xdrag

i don't know how true this is but i heard rogers was constantly sending a hit to reboot everyone's modem. this is actually nuisance because it cuts off my voice over IP calls....


pennyarcade

join:2010-12-07
North York, ON
reply to xdrag

So the problem has not come back for 3 days.

I had a ticket on the direct forums, where they replied and said that they can issue a service call to Rogers. I'm going to sit and wait to see if the problem comes back.

I have an SB5101 and my speeds are back to normal.



tonytoronto

join:2007-10-31
Toronto, ON

I had similar issue with t3 and t4's timeouts that ended up being a bad connector (corrosion) at the pole, Roger tech fixed and was good for a few months. Back to same deal, less T3 times than before but way more disconnects, loosing upstream channel again. Rogers tech left me his cell in case there was issue, so i talked to him today, seems like my area is a mess. I'm trying to get ticket open with Teksavvy.
Keep a eye on your upstream signal, if gets close to 55-56 the modem will T4 and reboot, that usually indicates signal problem (wiring, connectors, rogers end)



Waimea

join:2010-06-30
Toronto, ON
reply to xdrag

I started having the same problem too a few months ago and it's directly related to the upstream bonding.

The connection drops for 5 10 minutes at a time and without fail every time one of the upstream channels shows aborted with no ranging response in the logs.

Strangely I lost bonding completely about two weeks ago and was on one channel until yesterday. During that time there were no issues with the connection. As soon as the bonding came back yesterday the problem started again.

I opened a ticket with teksavvy and they requested a rogers tech to come have a look. I don't have high hopes because I think this must be related to rogers equipment at the node level or even deeper in the network but we'll see what comes out of it.

we really need to highlight this in bigger so that the folks at teksavvy can bring this up at a higher level with rogers.
--
Proud Teksavvy customer since 2007


pennyarcade

join:2010-12-07
North York, ON

1 edit
reply to xdrag

hmmm, started up again. I'm going to ask teksavvy to call a tech

EDIT: I plugged the modem into a different outlet and it is pretty solid now. Still going to have the tech come in though


xdrag

join:2005-02-18
North York, ON
reply to pennyarcade

said by pennyarcade:

So the problem has not come back for 3 days.

I had a ticket on the direct forums, where they replied and said that they can issue a service call to Rogers. I'm going to sit and wait to see if the problem comes back.

I have an SB5101 and my speeds are back to normal.

Disconnects stopped for the last 4-5 days. I've been monitoring my connection and no random disconnects except for a few hours on tuesday at around noon.

webfors

join:2006-10-03
Kanata, ON

Same here. I swapped out my DCM476 with a DCM475 with stac 2.16. No reboots for the past 3 days. It's looking up. Could be all the changes with channel bonding in my area, compounded by a flaky stac 2.31 on the DCM476.

I hope this trend continues.


webfors

join:2006-10-03
Kanata, ON

5+ days of no reboots. I take it back where I said it wasn't a modem issue... since obviously in this case it was.


pennyarcade

join:2010-12-07
North York, ON
reply to xdrag

so the tech switched the connectors at my home as well as the node and the problems went away and hasn't come back for 2 weeks.

I did NOT change the modem.


junglee

join:2004-05-26
North York, ON

I too have been getting this multiple times a day. The way I was able to keep the reboots away for a couple of days was to do a factory reset on the modem and then reboot it. It keeps SB6120 alive for about 2 to 3 days and then the reboots start again.

I'm in the process of getting a new modem to swap with my SB6120 to see if it's the line or the modem.

I too suspect it's the line since my modem has been rock solid in the near past..


pennyarcade

join:2010-12-07
North York, ON
reply to xdrag

updating my status:

I had more t3 timeouts and got another tech to come and take a look. Apparently, our area has old wiring and it degraded beyond acceptable limits and that we need to install new line. Rogers installed new cable (first in the air, and then came back and installed it in the ground, no charge) and now the connection is a LOT more reliable. Apart from the odd disconnect, the connection has been a lot more stable.


aingaran

join:2002-01-24
Scarborough, ON
reply to xdrag

I'm having the T3 timeouts on the WebSTAR DPC2100R2 in Scarborough.

I guess I'm going to have to call in a Rogers tech.



audiokaos

@wind.ca
reply to xdrag

Happened to me in Ajax as well at about 4:30 today. Disconnected, still waiting on it to be fixed. Tech believes it to be a Robbers provisioning issue..:(



Kev
TekSavvy.com
Premium
join:2005-06-12
canada
Reviews:
·TekSavvy Cable
·TekSavvy DSL

said by audiokaos :

Happened to me in Ajax as well at about 4:30 today. Disconnected, still waiting on it to be fixed. Tech believes it to be a Robbers provisioning issue..:(

It's about the same time for me as well. It is still dead for 15hrs+ now.
--
Teksavvy.com + 300GB Bandwidth awesomeness!