dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
4434
share rss forum feed

ablatt

join:2001-08-03
Toronto, ON

DPC3825 'Ranging - no Response Received' every night

For a couple of weeks, I've been getting one of these each day in my DOCSIS Log, usually in the early morning.

"Tue Jun 26 04:54:21 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ..."

Is Rogers doing something every night? I don't suspect the DPC3825 is failing since it is usually just once a day?

By the way my DPC3825 has the Nov 8, 2011 firmware.


engineered

join:2005-02-18
York, ON
Reviews:
·Rogers Hi-Speed

I'm having similar issues. I'm in downtown Toronto near Jane/Dundas. Where are you located?
Are you still having the issues? Mine only started July 10.

Here's an interesting post. »communityforums.rogers.com/t5/fo···9/page/4
Here's my modem details... same as yours.
Model: Cisco DPC3825
Hardware Revision: 1.0
Bootloader Revision: 2.3.0_R3
Current Software Revision: dpc3825-v302r125533-111108a-ROG
Firmware Name: dpc3825-v302r125533-111108a-ROG.bin
Firmware Build Time: Nov 8 18:12:42 2011

Here's the log from my modem.
Time ID Level Description
Wed Jul 18 03:02:31 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Tue Jul 17 07:02:55 2012 68010300 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M...
Tue Jul 17 07:01:21 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Mon Jul 16 19:44:08 2012 84020300 Warning (5) MDD message timeout;CM-MAC=00:23:be:e1:56:7c;CMTS-MAC=00:1b:5...
Mon Jul 16 19:44:08 2012 84020200 Warning (5) Lost MDD Timeout;CM-MAC=00:23:be:e1:56:7c;CMTS-MAC=00:1b:54:c...
Mon Jul 16 19:20:07 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Mon Jul 16 07:02:55 2012 68010300 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M...
Mon Jul 16 06:58:49 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Jul 15 20:03:54 2012 84020300 Warning (5) MDD message timeout;CM-MAC=00:23:be:e1:56:7c;CMTS-MAC=00:1b:5...
Sun Jul 15 20:03:54 2012 84020200 Warning (5) Lost MDD Timeout;CM-MAC=00:23:be:e1:56:7c;CMTS-MAC=00:1b:54:c...
Sun Jul 15 19:33:28 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Jul 15 07:02:55 2012 68010300 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M...
Sun Jul 15 07:01:15 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sat Jul 14 07:02:55 2012 68010300 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M...
Sat Jul 14 06:29:35 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Fri Jul 13 07:02:55 2012 68010300 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M...
Fri Jul 13 06:29:02 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Tue Jul 10 20:52:46 2012 84020300 Warning (5) MDD message timeout;CM-MAC=00:23:be:e1:56:7c;CMTS-MAC=00:1b:5...
Tue Jul 10 20:52:46 2012 84020200 Warning (5) Lost MDD Timeout;CM-MAC=00:23:be:e1:56:7c;CMTS-MAC=00:1b:54:c...
Tue Jul 10 20:40:15 2012 84000400 Critical (3) SYNC Timing Synchronization failure - Failed to receive MAC S...
Tue Jul 10 20:40:12 2012 84020300 Warning (5) MDD message timeout;CM-MAC=00:23:be:e1:56:7c;CMTS-MAC=00:1b:5...
Tue Jul 10 20:40:12 2012 84020200 Warning (5) Lost MDD Timeout;CM-MAC=00:23:be:e1:56:7c;CMTS-MAC=00:1b:54:c...
Tue Jul 10 20:40:06 2012 84020300 Warning (5) MDD message timeout;CM-MAC=00:23:be:e1:56:7c;CMTS-MAC=00:1b:5...
Tue Jul 10 20:40:06 2012 84020200 Warning (5) Lost MDD Timeout;CM-MAC=00:23:be:e1:56:7c;CMTS-MAC=00:1b:54:c...
Tue Jul 10 16:49:30 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Tue Jul 10 01:29:10 2012 68000100 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=00:23:b...
Tue Jul 10 01:28:57 2012 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=00:23:be:e1...
Tue Jul 10 01:28:47 2012 84000100 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Tue Jul 10 01:28:28 2012 84000200 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Tue Jul 10 01:27:11 2012 84000100 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Tue Jul 10 01:27:00 2012 84000200 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Tue Jul 10 01:26:58 2012 84000100 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Tue Jul 10 01:26:33 2012 84000200 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Tue Jul 10 01:26:29 2012 84000100 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Tue Jul 10 01:25:48 2012 84000200 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Tue Jul 10 01:25:47 2012 84000100 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Tue Jul 10 01:25:43 2012 84000200 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Tue Jul 10 01:25:39 2012 84000100 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Tue Jul 10 01:25:12 2012 84000200 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Tue Jul 10 01:24:28 2012 84000100 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...

Downstream Channels
Power Level: Signal to Noise Ratio:
Channel 1: 3.0 dBmV 40.1 dB
Channel 2: 2.9 dBmV 39.4 dB
Channel 3: 2.9 dBmV 39.7 dB
Channel 4: 3.1 dBmV 40.8 dB
Channel 5: 3.4 dBmV 41.1 dB
Channel 6: 4.0 dBmV 40.9 dB
Channel 7: 4.3 dBmV 40.4 dB
Channel 8: 4.4 dBmV 39.9 dB

Upstream Channels
Power Level:
Channel 1: 43.9 dBmV
Channel 2: 44.6 dBmV
Channel 3: 44.1 dBmV
Channel 4: 44.1 dBmV


ablatt

join:2001-08-03
Toronto, ON

I'm in Toronto near Spadina and Eglinton.

Mine stopped doing it on July 7th.

It never caused any issues for me, just seemed unusual. Perhaps related to maintenance in the area?



Last Parade

join:2002-10-07
Port Colborne, ON
Reviews:
·Start Communicat..
reply to engineered

There's not a lot that's interesting here. The logs usually only give you information when things aren't working right; they don't tell you about when they do work. MDD is not a critical parameter (it probably found it eventually anyway), and the DHCP warnings about invalid fields is usually shown when there are DHCP options sent that the modem doesn't recognize (and thus ignores).

The maintenance ranging requests are to happen every 30 seconds per the DOCSIS standard. The modem asks the CMTS if it should adjust its power, the CMTS replies with power adjustments. If the modem never receives a reply to one of these, it generates the T3 error in the logs. This can be due to over-selling or low upstream.


engineered

join:2005-02-18
York, ON
Reviews:
·Rogers Hi-Speed

I should mention that the symptoms I'm experiencing are dropped packets and extremely slow speeds like 2mbps instead of 25mbps.
Even youtube on 240p won't stream properly.
Pinging tests show between 2-8% dropped packets.
Rebooting my modem seems to improve things, but not completely.


DJ411

join:2009-12-31
reply to ablatt

I also get this no ranging thing. I thought it was causing my internet to crash all the time. Got someone coming in tomorrow. Hopefully something gets fixed.


trog

join:2001-03-25
Scarborough, ON
reply to engineered

I was seeing something similar the other day and called in to Rogers. After trying a few things with them and still seeing the issues (ie removing my router and connecting straight to the DPC 3825) the tech said he was seeing packet loss internal to the device, and he proceeded to reflash it.

Since then no issues at all.


engineered

join:2005-02-18
York, ON

It happened to me last week again. Called Rogers tech and they said the whole area was out and there was nothing they could do. I just had to wait a few hours while their techs fix their hardware.