cancel
Showing results for 
Search instead for 
Did you mean: 

Has My SB5100 Finally Bit The Dust?

Frazzled
I'm a Reliable Contributor

The modem has been disconnecting and reconnecting for the past several hours. I have spoken with two CSRs from Rogers. The first scheduled a service call, but the tech cannot come until next Monday. The second recommended exchanging the modem because there was no general area problem.

 

Here are my logs from the modem as of today. Any comments or suggestions as to what is going on?

 

2013-09-11 19:20:00 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.2013-09-11 19:19:49 3-Critical R002.0 No Ranging Response received - T3 time-out 2013-09-11 19:19:43 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2013-09-11 19:19:38 3-Critical R002.0 No Ranging Response received - T3 time-out 2013-09-11 19:19:27 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC 2013-09-11 19:19:03 3-Critical R002.0 No Ranging Response received - T3 time-out 2013-09-11 19:18:40 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC 2013-09-11 19:18:21 3-Critical R002.0 No Ranging Response received - T3 time-out 2013-09-11 19:18:15 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC 2013-09-11 19:17:54 3-Critical R002.0 No Ranging Response received - T3 time-out 2013-09-11 19:17:47 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2013-09-11 19:17:47 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC 2013-09-11 19:17:30 3-Critical R002.0 No Ranging Response received - T3 time-out 2013-09-11 19:16:48 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC 2013-09-11 19:16:28 3-Critical R002.0 No Ranging Response received - T3 time-out 2013-09-11 19:16:21 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC 2013-09-11 19:16:03 3-Critical R002.0 No Ranging Response received - T3 time-out 2013-09-11 19:15:58 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2013-09-11 19:15:57 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC 2013-09-11 19:15:39 3-Critical R002.0 No Ranging Response received - T3 time-out 2013-09-11 19:15:05 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC 2013-09-11 19:14:44 3-Critical R002.0 No Ranging Response received - T3 time-out 2013-09-11 19:14:35 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC 2013-09-11 19:14:14 3-Critical R002.0 No Ranging Response received - T3 time-out 2013-09-11 19:14:09 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC 2013-09-11 19:13:51 3-Critical R002.0 No Ranging Response received - T3 time-out 2013-09-11 19:13:20 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC 2013-09-11 19:13:02 3-Critical R002.0 No Ranging Response received - T3 time-out 2013-09-11 19:12:57 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC 2013-09-11 19:12:40 3-Critical R002.0 No Ranging Response received - T3 time-out 2013-09-11 19:12:15 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC 2013-09-11 19:11:57 3-Critical R002.0 No Ranging Response received - T3 time-out 2013-09-11 19:11:47 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC 2013-09-11 19:11:28 3-Critical R002.0 No Ranging Response received - T3 time-out 2013-09-11 19:11:24 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC 2013-09-11 19:11:03 3-Critical R002.0 No Ranging Response received - T3 time-out 2013-09-11 19:10:56 3-Critical R007.0 Unicast Ranging Received Abort Response - Re- initializing MAC

 

 

***edited labels***

2 REPLIES 2

Re: Has My SB5100 Finally Bit The Dust?

Gdkitty
Resident Expert
Resident Expert

That looks like the normal error which the gateways get, when they do the dropped connection.

 

I know with the SB modems that the TIPA providers on rogers have, were having MAJOR issues with the D3 SB ones, and there had to be a firmware push out for it.


Wondering if there is the same sort of thing/issue, with the older SB modems as well? Might be worth seeing if they have a firmware update for it?

Re: Has My SB5100 Finally Bit The Dust?

Frazzled
I'm a Reliable Contributor

Thanks for the reply Gdkitty! I kept seeing the word "critical" and figured there was something seriously wrong with our modem. Yet today, it is working 100% with no disconnects at all. It makes you wonder why Rogers could not do more to look into the issue instead of just telling you to go and exchange the modem for a new one!

We Want Your Opinion
Would you be interested in becoming a Community Testing Lab member?
Topic Stats
  • 2 replies
  • 912 views
  • 0 Likes
  • 2 in conversation